Nastar Network Optimization User Guide (V600R015C00 - 03) (PDF) - EN PDF

Nastar
V600R015C00
Network Optimization User Guide

Issue
03
Date
2015-07-30
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 03 (2015-07-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Nastar
About This Document
About This Document
Overview
This document describes how to use the Nastar functions. The Nastar is a system that performs
localization and analysis of quality-related problems on the radio network, for example, GSM/
GPRS/EDGE, UMTS/HSUPA/HSDPA, LTE, and PS Core. This system supports multi-user
operations and multiple types of radio performance analysis. It provides a basic supporting
platform for thorough radio network analysis and problem localization.
Product Version
The following table lists the product versions related to this document.
Product Name
Product Version
Nastar
V600R015C00
Intended Audience
This document is intended for:
l
Network optimization engineers
System administrators
Change History
03 (2015-07-30)
This issue is the third official release of Nastar V600R015.
Compared with Issue 02 (2015-06-30) for V600R015C00, 03 (2015-07-30) for V600R015C00
includes the following changes.
Issue 03 (2015-07-30)

ii
Nastar
About This Document
Section
Change Descriptin
6.1.3 Process of LTE Coverage Analysis
Add
Added basic subscription LOGGED
MDT event information.
6.2.3 Process of LTE Cell Performance

Analysis
6.3.3 Process of LTE Terminal Analysis
6.4.3 Process of LTE Network Geographic
Observation
Service Operations
Modified
l Modified the document to support
SRAN11.0.
l Modified the document to support
ERAN11.0.
l Modified the document to support PS
13.0.
02 (2015-06-30)
This issue is the second official release of Nastar V600R015.
Compared with Issue 01 (2015-05-30) for V600R015C00, 02 (2015-06-30) for V600R015C00
includes the following changes.
Section
Change Descriptin
Description optimized.
01 (2015-05-30)
This issue is the first official release of Nastar V600R015.
Compared with Draft A (2015-04-28) of Nastar V600R015, this issue does not incorporate any
changes.
Draft A (2015-04-28)
This is a draft for V600R015C00.
Compared with Issue 05 (2014-02-14) for V600R014C00, Draft A (2015-04-20) for
V600R015C00 includes the following changes.
Issue 03 (2015-07-30)

iii
Nastar
About This Document
Section
Change Descriptin
4.10 Complaint Analysis Support
Modified
Added the information about KQI
analysis based on UGW internal data
sources in complaint analysis support in
the PS Core and LTE/PS Core scenarios.
Parameters for Viewing PS Core VIP Analysis

- VoLTE Results
Add
Parameters for Viewing PS Core VIP
Analysis - VoLTE Results
3.3.4 Configuring OSS Information
Modified
Added the information about the RAN
SAU (RH2288) obtains the CHR or MR
data of RNCs or BSCs on a UMTS or
GSM network from the Trace Server.
Configuring SAU or LTE SAU Information

2.1 Position in Networking
Managing VIP Subscribers
Modified
Added the following involved
informations:
VIP subscription will be issued
automatically again after the VIP group is
changed.
Modified
informations:
Automatic access to eNodeBs and Delete
eNodeBs in batches.
3.5.2 Basic Subscription of Analysis Data
Modified
informations:
Disable eNodeB subscription in batches.
Issue 03 (2015-07-30)

iv
Nastar
Contents
Contents
About This Document.....................................................................................................................ii
1 About This Help............................................................................................................................1
1.1 Intended Audience..........................................................................................................................................................2
1.2 Conventions....................................................................................................................................................................2
2 Nastar Overview............................................................................................................................4
2.1 Position in Networking...................................................................................................................................................5
2.2 Analysis Data Sources....................................................................................................................................................8
2.2.1 Data Sources for Nastar GSM Analysis......................................................................................................................8
2.2.2 Data Sources for Nastar UMTS Analysis..................................................................................................................10
2.2.3 Data Sources for Nastar LTE Analysis......................................................................................................................13
2.2.4 Data Sources for Nastar PS Core Analysis................................................................................................................17
2.3 Product Functions.........................................................................................................................................................19
2.4 Technical Specifications...............................................................................................................................................22
2.5 Basic Concept/Glossary................................................................................................................................................25
2.6 Guide to the Document.................................................................................................................................................28
3 Nastar Quick Start.......................................................................................................................29

3.1 Nastar Operation Process..............................................................................................................................................31
3.2 Login In to the Nastar...................................................................................................................................................33
3.2.1 Logging In to the Nastar Client.................................................................................................................................33
3.2.2 Interface Description: Nastar Client..........................................................................................................................35
3.2.3 Interface Description: Geographic Observation Results...........................................................................................36
3.3 Configuring OSS and NE Information.........................................................................................................................48
3.3.1 Configuration Procedures..........................................................................................................................................48
3.3.2 Preparations for OSS and NE Information Configuration.........................................................................................50
3.3.3 Configuring eSAU Information.................................................................................................................................55
3.3.4 Configuring OSS Information...................................................................................................................................59
3.3.5 Configuring NE Information on the RAN Side.........................................................................................................69
3.3.6 Configuring NE Information on the CN Side............................................................................................................81
3.3.7 Setting the Vendor Type of EPCs (MMEs) (Optional).............................................................................................86
3.3.8 Configuring Relationships Between HSSs and eNodeBs (Optional)........................................................................87
3.3.9 Configuring the Anonymous Policy..........................................................................................................................88
Issue 03 (2015-07-30)

Nastar
Contents
3.4 Preparing Basic Data....................................................................................................................................................92

3.4.1 Introduction to Basic Data.........................................................................................................................................92
3.4.2 Checking the Integrity of Configuration Data...........................................................................................................97
3.4.3 Preparing Engineering Parameters............................................................................................................................98
3.4.4 Preparing the Map File (Optional)...........................................................................................................................114
3.4.5 Managing NE Groups..............................................................................................................................................118
3.4.6 Managing VIP Groups or VIP Users (VIP Analysis)..............................................................................................123
3.4.7 Managing Terminal Information (Terminal Analysis)............................................................................................135
3.4.8 Managing Information About Data Service Servers (PS Service)..........................................................................141
3.4.9 Managing PS Core Knowledge Bases (Optional)...................................................................................................143
3.4.10 Setting a Mailbox and Address List for Sending Analysis Reports (Optional).....................................................145
3.4.11 Setting Location Parameters for Geographic Observation (Optional)..................................................................148
3.4.12 PS Core Cell Information Management................................................................................................................150
3.5 Subscribing to Analysis Data.....................................................................................................................................154
3.5.1 Basics of Data Subscription.....................................................................................................................................154
3.5.2 Basic Subscription of Analysis Data.......................................................................................................................157
3.5.3 Application Subscription of Analysis Data.............................................................................................................163
3.6 Checking the Integrity of Analysis Data....................................................................................................................167
3.7 Creating an Analysis Task..........................................................................................................................................169
3.8 Querying Analysis Results.........................................................................................................................................175
3.9 Viewing Geographic Analysis Results (Optional).....................................................................................................176
3.10 Exporting Analysis Reports......................................................................................................................................177
3.11 Periodically Deleting Analysis Data.........................................................................................................................178
3.12 FAQs.........................................................................................................................................................................179
3.12.1 How Do I Enable the LTE Automatic Subscription Function...............................................................................179
3.12.2 What Can I Do If the Subscription Is Longer Than Expected?.............................................................................180
3.12.3 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption
Key....................................................................................................................................................................................180
3.12.4 Supporting Historical Data Analysis on a Changed NE........................................................................................182
3.12.5 Nastar Fails to Identify Information in Non-Specified Languages.......................................................................183
3.12.6 Why Cannot the Nastar Client Be Displayed Again?............................................................................................184
3.12.7 What Do I Do if the System Displays Login U2000/M2000 Failed When a Nastar Basic Data Subscription
Task Fails?........................................................................................................................................................................184
3.12.8 Failed NE Version Upgrade Causes Failures in Subscribing to Basic Data for Some Themes............................185
3.12.9 Data Subscription Failures in Some Themes Due to the Reconstruction of Existing RNCs into RNC In Pools
..........................................................................................................................................................................................186
3.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?..................188
3.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%?..........................................................................................................................188
3.12.12 What Do I Do When the Nastar Client Does Not Respond to the Querying of a Created Task?.......................189
3.12.13 What Do I Do When NE Names in the NE Tree Are Different from Those in the NE Details Area?...............189
3.12.14 Handling NE Data Processing Timeout When Tasks Fail to Be Created in the Nastar......................................190
Issue 03 (2015-07-30)

vi
Nastar
Contents
4 GSM Network Optimization..................................................................................................191

4.1 GSM MR Analysis.....................................................................................................................................................193
4.1.1 Basics of GSM MR Analysis...................................................................................................................................193
4.1.2 Preparations for GSM MR Analysis........................................................................................................................199
4.1.3 Process of GSM MR Analysis.................................................................................................................................200
4.1.4 Reference for GSM MR Analysis Interface............................................................................................................208
4.1.5 Reference for GSM MR Analysis Parameters.........................................................................................................215
4.2 GSM Frequency Analysis...........................................................................................................................................340
4.2.1 Basics of GSM Frequency Analysis........................................................................................................................340
4.2.2 Preparations for GSM Frequency Analysis.............................................................................................................349
4.2.3 Process of GSM Frequency Analysis......................................................................................................................350
4.2.4 Reference for GSM Frequency Analysis Interface..................................................................................................362
4.2.5 Reference for GSM Frequency Analysis Parameters..............................................................................................370
4.3 GSM Neighboring Cell Analysis................................................................................................................................416
4.3.1 Basics of GSM Neighboring Cell Analysis.............................................................................................................416
4.3.2 Preparations for GSM Neighboring Cell Analysis..................................................................................................422
4.3.3 Process of GSM Neighboring Cell Analysis...........................................................................................................424
4.3.4 Reference for GSM Neighboring Cell Analysis Interface.......................................................................................435
4.3.5 Reference for GSM Neighboring Cell Analysis Parameters...................................................................................443
4.4 GSM/UMTS Neighboring Cell Analysis...................................................................................................................506
4.4.1 Basics of GSM/UMTS Neighboring Cell Analysis.................................................................................................507
4.4.2 Preparations for GSM/UMTS Neighboring Cell Analysis......................................................................................512
4.4.3 Process of GSM/UMTS Neighboring Cell Analysis...............................................................................................514
4.4.4 Reference for GSM/UMTS Neighboring Cell Analysis Interface..........................................................................522
4.4.5 Reference for GSM/UMTS Neighboring Cell Analysis Parameters.......................................................................527
4.5 GSM Uplink Interference Analysis............................................................................................................................564
4.5.1 Basics of GSM Uplink Interference Analysis.........................................................................................................564
4.5.2 Preparations for GSM Uplink Interference Analysis...............................................................................................569
4.5.3 Process of GSM Uplink Interference Analysis........................................................................................................570
4.5.4 Interface Description: GSM Uplink Interference Analysis.....................................................................................577
4.5.5 Parameters for Viewing GSM Uplink Interference Analysis Results.....................................................................579
4.6 GSM Terminal Analysis.............................................................................................................................................589
4.6.1 Basics of GSM Terminal Analysis..........................................................................................................................589
4.6.2 Preparations for GSM Terminal Analysis...............................................................................................................594
4.6.3 Process of GSM Terminal Analysis........................................................................................................................595
4.6.4 Interface Description: GSM Terminal Analysis......................................................................................................606
4.6.5 Parameters for Viewing GSM Terminal Analysis Results......................................................................................614
4.7 GSM Cell Performance Analysis...............................................................................................................................649
4.7.1 Basics of GSM Cell Performance Analysis.............................................................................................................650
4.7.2 Preparations for GSM Cell Performance Analysis..................................................................................................654
4.7.3 Process of GSM Cell Performance Analysis...........................................................................................................655
Issue 03 (2015-07-30)

vii
Nastar
Contents
4.7.4 Interface Description: GSM Cell Performance Analysis.........................................................................................667

4.7.5 Parameters for Viewing GSM Cell Performance Analysis Results........................................................................669
4.8 GSM Network Geographic Observation....................................................................................................................700
4.8.1 Basics of GSM Network Geographic Observation..................................................................................................700
4.8.2 Preparations for GSM Network Geographic Observation.......................................................................................705
4.8.3 Process of GSM Network Geographic Observation................................................................................................707
4.8.4 Interface Description: GSM Network Geographic Observation.............................................................................720
4.8.5 Parameters for Viewing GSM Network Geographic Observation Results.............................................................724
4.9 VIP Analysis...............................................................................................................................................................733
4.9.1 Basics of VIP Analysis............................................................................................................................................734
4.9.2 Preparations for VIP Analysis.................................................................................................................................747
4.9.3 Process of VIP Analysis..........................................................................................................................................760
4.9.4 Reference for VIP Analysis Interface......................................................................................................................783
4.9.5 Reference for VIP Analysis Parameters (GSM)......................................................................................................797
4.9.6 Reference for VIP Analysis Parameters (UMTS)...................................................................................................907
4.9.7 Reference for VIP Analysis Parameters (LTE).....................................................................................................1105
4.9.8 Reference for VIP Analysis Parameters (PS Core)...............................................................................................1149
4.9.9 FAQ: How Do I Set the LTE All-Signaling Switch to On?..................................................................................1217
4.10 Complaint Analysis Support...................................................................................................................................1218
4.10.1 Basics of Complaint Analysis Support................................................................................................................1219
4.10.2 Preparations for Complaint Analysis Support.....................................................................................................1230
4.10.3 Process of Complaint Analysis Support..............................................................................................................1244
4.10.4 Reference for Complaint Analysis Support Interface..........................................................................................1262
4.10.5 Reference for Complaint Analysis Support Parameters (GSM)..........................................................................1304
4.10.6 Reference for Complaint Analysis Support Parameters (UMTS).......................................................................1475
4.10.7 Reference for Complaint Analysis Support Parameters (LTE)...........................................................................1668
4.10.8 Reference for Complaint Analysis Support Parameters (PS Core).....................................................................1738
4.10.9 Reference for Complaint Analysis Support Parameters (Combined Analysis)...................................................2027
4.10.10 Appendix: Exception Cause Classification / Key Signaling.............................................................................2037
5 UMTS Network Optimization..............................................................................................2093

5.1 UMTS Coverage Analysis........................................................................................................................................2096
5.1.1 Basics of UMTS Coverage Analysis.....................................................................................................................2096
5.1.2 Preparations for UMTS Coverage Analysis..........................................................................................................2100
5.1.3 Process of UMTS Coverage Analysis...................................................................................................................2100
5.1.4 Interface Description: UMTS Coverage Analysis.................................................................................................2107
5.1.5 Parameters for Viewing UMTS Coverage Analysis Results.................................................................................2111
5.2 UMTS Intra-Frequency Neighboring Cell Analysis................................................................................................2116
5.2.1 Basics of UMTS Intra-Frequency Neighboring Cell Analysis..............................................................................2117
5.2.2 Preparations for UMTS Intra-Frequency Neighboring Cell Analysis...................................................................2122
5.2.3 Process of UMTS Intra-Frequency Neighboring Cell Analysis............................................................................2124
5.2.4 Interface Description: UMTS Intra-Frequency Neighboring Cell Analysis..........................................................2130
Issue 03 (2015-07-30)

viii
Nastar
Contents
5.2.5 Parameters for Viewing UMTS Intra-frequency Neighboring Cell Analysis Results..........................................2134
5.3 UMTS/GSM Neighboring Cell Analysis.................................................................................................................2157
5.3.1 Basics of UMTS/GSM Neighboring Cell Analysis...............................................................................................2157
5.3.2 Preparations for UMTS/GSM Neighboring Cell Analysis....................................................................................2162
5.3.3 Process of UMTS/GSM Neighboring Cell Analysis.............................................................................................2163
5.3.4 Reference for UMTS/GSM Neighboring Cell Analysis Interface........................................................................2171
5.3.5 Reference for UMTS/GSM Neighboring Cell Analysis Parameters.....................................................................2177
5.4 UMTS Inter-Frequency Neighboring Cell Analysis................................................................................................2213
5.4.1 Basics of UMTS Inter-Frequency Neighboring Cell Analysis..............................................................................2214
5.4.2 Preparations for UMTS Inter-Frequency Neighboring Cell Analysis...................................................................2218
5.4.3 Process of UMTS Inter-Frequency Neighboring Cell Analysis............................................................................2219
5.4.4 Interface Description: UMTS Inter-Frequency Neighboring Cell Analysis..........................................................2227
5.4.5 Parameters for Viewing UMTS Inter-frequency Neighboring Cell Analysis Results..........................................2231
5.5 UMTS Pilot Pollution Analysis................................................................................................................................2255
5.5.1 Basics of UMTS Pilot Pollution Analysis.............................................................................................................2255
5.5.2 Preparations for UMTS Pilot Pollution Analysis..................................................................................................2259
5.5.3 Process of UMTS Pilot Pollution Analysis...........................................................................................................2261
5.5.4 Interface Description: UMTS Pilot Pollution Analysis.........................................................................................2267
5.5.5 Parameters for Viewing UMTS Pilot Pollution Analysis Results.........................................................................2272
5.6 UMTS Uplink Interference Analysis........................................................................................................................2305
5.6.1 Basics of UMTS Uplink Interference Analysis.....................................................................................................2305
5.6.2 Preparations for UMTS Uplink Interference Analysis..........................................................................................2308
5.6.3 Process of UMTS Uplink Interference Analysis...................................................................................................2309
5.6.4 Interface Description: UMTS Uplink Interference Analysis.................................................................................2315
5.6.5 Parameters for Viewing UMTS Uplink Interference Analysis Results.................................................................2316
5.7 UMTS Terminal Analysis........................................................................................................................................2321
5.7.1 Basics of UMTS Terminal Analysis......................................................................................................................2322
5.7.2 Preparations for UMTS Terminal Analysis...........................................................................................................2326
5.7.3 Process of UMTS Terminal Analysis....................................................................................................................2328
5.7.4 Interface Description: UMTS Terminal Analysis..................................................................................................2343
5.7.5 Parameters for Viewing UMTS Terminal Analysis Results.................................................................................2350
5.8 UMTS Cell Performance Analysis...........................................................................................................................2423
5.8.1 Basics of UMTS Cell Performance Analysis........................................................................................................2424
5.8.2 Preparations for UMTS Cell Performance Analysis.............................................................................................2428
5.8.3 Process of UMTS Cell Performance Analysis......................................................................................................2429
5.8.4 Interface Description: UMTS Cell Performance Analysis....................................................................................2450
5.8.5 Parameters for Viewing UMTS Cell Performance Analysis Results....................................................................2452
5.8.6 FAQ: What Do I Do When NE Objects Are Missing from the Analysis Results?...............................................2541
5.9 UMTS Network Geographic Observation................................................................................................................2542
5.9.1 Basics of UMTS Network Geographic Observation.............................................................................................2542
5.9.2 Preparations for UMTS Network Geographic Observation..................................................................................2547
Issue 03 (2015-07-30)

ix
Nastar
Contents
5.9.3 Process of UMTS Network Geographic Observation...........................................................................................2549

5.9.4 Interface Description: UMTS Network Geographic Observation.........................................................................2559
5.9.5 Parameters for Viewing UMTS Network Geographic Observation Results.........................................................2563
5.10 VIP Analysis...........................................................................................................................................................2586
5.10.1 Basics of VIP Analysis........................................................................................................................................2587
5.10.2 Preparations for VIP Analysis.............................................................................................................................2600
5.10.3 Process of VIP Analysis......................................................................................................................................2613
5.10.4 Reference for VIP Analysis Interface..................................................................................................................2636
5.10.5 Reference for VIP Analysis Parameters (UMTS)...............................................................................................2650
5.10.6 Reference for VIP Analysis Parameters (GSM)..................................................................................................2848
5.10.7 Reference for VIP Analysis Parameters (LTE)...................................................................................................2958
5.10.8 Reference for VIP Analysis Parameters (PS Core).............................................................................................3002
5.10.9 FAQ: How Do I Set the LTE All-Signaling Switch to On?................................................................................3070
5.11 Complaint Analysis Support...................................................................................................................................3071
5.11.1 Basics of Complaint Analysis Support................................................................................................................3072
5.11.2 Preparations for Complaint Analysis Support.....................................................................................................3083
5.11.3 Process of Complaint Analysis Support..............................................................................................................3097
5.11.4 Reference for Complaint Analysis Support Interface..........................................................................................3115
5.11.5 Reference for Complaint Analysis Support Parameters (UMTS).......................................................................3157
5.11.6 Reference for Complaint Analysis Support Parameters (GSM)..........................................................................3350
5.11.7 Reference for Complaint Analysis Support Parameters (LTE)...........................................................................3522
5.11.8 Reference for Complaint Analysis Support Parameters (PS Core).....................................................................3592
5.11.9 Reference for Complaint Analysis Support Parameters (Combined Analysis)...................................................3881
5.11.10 Appendix: Exception Cause Classification / Key Signaling.............................................................................3891
6 LTE Network Optimization...................................................................................................3947

6.1 LTE Coverage Analysis............................................................................................................................................3949
6.1.1 Basics of LTE Coverage Analysis.........................................................................................................................3949
6.1.2 Preparations for LTE Coverage Analysis..............................................................................................................3953
6.1.3 Process of LTE Coverage Analysis.......................................................................................................................3955
6.1.4 Interface Description: LTE Coverage Analysis.....................................................................................................3968
6.1.5 Parameters for Viewing LTE Coverage Analysis Results.....................................................................................3973
6.2 LTE Cell Performance Analysis...............................................................................................................................3976
6.2.1 Basics of LTE Cell Performance Analysis............................................................................................................3976
6.2.2 Preparations for LTE Cell Performance Analysis.................................................................................................3981
6.2.3 Process of LTE Cell Performance Analysis..........................................................................................................3983
6.2.4 Interface Description: LTE Cell Performance Analysis........................................................................................3994
6.2.5 Parameters for Viewing LTE Cell Performance Analysis Results........................................................................3998
6.3 LTE Terminal Analysis............................................................................................................................................4030
6.3.1 Basics of LTE Terminal Analysis.........................................................................................................................4031
6.3.2 Preparations for LTE Terminal Analysis...............................................................................................................4035
6.3.3 Process of LTE Terminal Analysis........................................................................................................................4037
Issue 03 (2015-07-30)

Nastar
Contents
6.3.4 Interface Description: LTE Terminal Analysis.....................................................................................................4048

6.3.5 Parameters for Viewing LTE Terminal Analysis Results.....................................................................................4054
6.4 LTE Network Geographic Observation....................................................................................................................4098
6.4.1 Basics of LTE Network Geographic Observation.................................................................................................4098
6.4.2 Preparations for LTE Network Geographic Observation......................................................................................4104
6.4.3 Process of LTE Network Geographic Observation...............................................................................................4107
6.4.4 Interface Description: LTE Network Geographic Observation.............................................................................4121
6.4.5 Parameters for Viewing LTE Network Geographic Observation Results.............................................................4126
6.5 VIP Analysis.............................................................................................................................................................4133
6.5.1 Basics of VIP Analysis..........................................................................................................................................4133
6.5.2 Preparations for VIP Analysis...............................................................................................................................4147
6.5.3 Process of VIP Analysis........................................................................................................................................4160
6.5.4 Reference for VIP Analysis Interface....................................................................................................................4183
6.5.6 Reference for VIP Analysis Parameters (GSM)....................................................................................................4241
6.5.7 Reference for VIP Analysis Parameters (UMTS).................................................................................................4351
6.6 Complaint Analysis Support.....................................................................................................................................4618
6.6.1 Basics of Complaint Analysis Support..................................................................................................................4619
6.6.2 Preparations for Complaint Analysis Support.......................................................................................................4630
6.6.3 Process of Complaint Analysis Support................................................................................................................4644
6.6.4 Reference for Complaint Analysis Support Interface............................................................................................4662
6.6.5 Reference for Complaint Analysis Support Parameters (LTE).............................................................................4703
6.6.6 Reference for Complaint Analysis Support Parameters (GSM)............................................................................4772
6.6.7 Reference for Complaint Analysis Support Parameters (UMTS).........................................................................4943
6.6.8 Reference for Complaint Analysis Support Parameters (PS Core).......................................................................5136
6.6.9 Reference for Complaint Analysis Support Parameters (Combined Analysis).....................................................5426
6.6.10 Appendix: Exception Cause Classification / Key Signaling...............................................................................5436
6.6.11 FAQ: Why Are CHRs Related to RRC Connection Setup Failures Not Displayed in LTE Complaint Analysis
Support Results?.............................................................................................................................................................5491
7 PS Core Network Optimization............................................................................................5493

7.1 PS Core Terminal Analysis......................................................................................................................................5495
7.1.1 Basics of PS Core Terminal Analysis....................................................................................................................5495
7.1.2 Preparations for PS Core Terminal Analysis.........................................................................................................5500
7.1.3 Process of PS Core Terminal Analysis..................................................................................................................5504
7.1.4 Interface Description: PS Core Terminal Analysis...............................................................................................5511
7.1.5 Parameters for PS Terminal Core Analysis...........................................................................................................5516
7.2 Root Cause Analysis for PS Core Performance Problems.......................................................................................5550
7.2.1 Basics of Root Cause Analysis for PS Core Performance Problems....................................................................5550
7.2.2 Preparations for Root Cause Analysis for PS Core Performance Problems..........................................................5556
Issue 03 (2015-07-30)

xi
Nastar
Contents
7.2.3 Process of Root Cause Analysis for PS Core Performance Problems...................................................................5560

7.2.4 Interface Summary for Results of Root Cause Analysis on PS Core Performance Problems..............................5571
7.2.5 Parameters for Root Cause Analysis for PS Core Performance Problems............................................................5581
7.2.6 Appendix: Procedure Types (Root Cause Analysis for PS Core Performance Problems)....................................5589
7.3 VIP Analysis.............................................................................................................................................................5674
7.3.1 Basics of VIP Analysis..........................................................................................................................................5674
7.3.2 Preparations for VIP Analysis...............................................................................................................................5687
7.3.3 Process of VIP Analysis........................................................................................................................................5700
7.3.4 Reference for VIP Analysis Interface....................................................................................................................5723
7.3.6 Reference for VIP Analysis Parameters (GSM)....................................................................................................5805
7.3.7 Reference for VIP Analysis Parameters (UMTS).................................................................................................5915
7.4 Complaint Analysis Support.....................................................................................................................................6159
7.4.1 Basics of Complaint Analysis Support..................................................................................................................6159
7.4.2 Preparations for Complaint Analysis Support.......................................................................................................6170
7.4.3 Process of Complaint Analysis Support................................................................................................................6185
7.4.4 Reference for Complaint Analysis Support Interface............................................................................................6203
7.4.5 Reference for Complaint Analysis Support Parameters (PS Core).......................................................................6245
7.4.6 Reference for Complaint Analysis Support Parameters (GSM)............................................................................6534
7.4.7 Reference for Complaint Analysis Support Parameters (UMTS).........................................................................6706
7.4.8 Reference for Complaint Analysis Support Parameters (LTE).............................................................................6899
7.4.9 Reference for Complaint Analysis Support Parameters (Combined Analysis).....................................................6969
7.4.10 Appendix: Exception Cause Classification / Key Signaling...............................................................................6978
8 System Management...............................................................................................................7034
8.1 Common Client Settings...........................................................................................................................................7036
8.1.1 Logging In to or Exiting the Nastar Client............................................................................................................7036
8.1.2 Setting the Level of Logs Recorded by the Client.................................................................................................7039
8.1.3 Changing the Password of the Current User.........................................................................................................7039
8.1.4 Getting to Know the Client GUI............................................................................................................................7040
8.1.5 Customizing the Client GUI Effect.......................................................................................................................7059
8.1.6 Locking the Client.................................................................................................................................................7065
8.1.7 Unlocking the Client..............................................................................................................................................7066
8.1.8 Broadcast Messages...............................................................................................................................................7067
8.1.9 Setting the Alert upon Network Disconnections...................................................................................................7069
8.1.10 Managing the Nastar License..............................................................................................................................7069
8.1.11 Selecting More Secure Network Protocols..........................................................................................................7075
8.1.12 Querying the System Time..................................................................................................................................7075
8.1.13 GUI Reference.....................................................................................................................................................7075
8.1.14 FAQs about the Client Operations.......................................................................................................................7098
Issue 03 (2015-07-30)

xii
Nastar
Contents
8.2 Security Management...............................................................................................................................................7107

8.2.1 Getting to Know the Concepts of Nastar Security................................................................................................7107
8.2.2 Managing User Rights...........................................................................................................................................7111
8.2.3 Security Policy Management.................................................................................................................................7160
8.2.4 Managing Passwords and Locking Clients............................................................................................................7170
8.2.5 Setting Nastar Data Transmission Security...........................................................................................................7175
8.2.6 Monitoring Nastar Users.......................................................................................................................................7179
8.2.7 GUIs and Parameters for Security Management...................................................................................................7181
8.2.8 Appendix...............................................................................................................................................................7240
8.2.9 FAQs About Authorization...................................................................................................................................7242
8.3 Digital Certificate Management...............................................................................................................................7244
8.3.1 Getting to Know Digital Certificates.....................................................................................................................7244
8.3.2 Configuring Digital Certificates............................................................................................................................7246
8.3.3 Updating Digital Certificates.................................................................................................................................7255
8.3.4 Obtaining the Certificate Revocation List.............................................................................................................7255
8.3.5 Reference of the Certificate Authentication Management GUI............................................................................7256
8.4 Log Management......................................................................................................................................................7265
8.4.1 Getting to Know Log Management.......................................................................................................................7265
8.4.2 Managing Nastar Operation Logs..........................................................................................................................7270
8.4.3 Managing Nastar System Logs..............................................................................................................................7276
8.4.4 Managing Nastar Security Logs............................................................................................................................7282
8.4.5 Setting Nastar Log Templates...............................................................................................................................7287
8.4.6 Setting Nastar Log Forwarding.............................................................................................................................7289
8.4.7 Managing Log Data...............................................................................................................................................7297
8.4.8 Reference of the Log Management GUI...............................................................................................................7301
8.5 Fault Management....................................................................................................................................................7338
8.5.1 Getting to Know Fault Management.....................................................................................................................7338
8.5.2 Overview of Fault Operations...............................................................................................................................7346
8.5.3 Setting Fault Monitoring Rules.............................................................................................................................7347
8.5.4 Setting Fault Monitoring Attributes......................................................................................................................7359
8.5.5 Monitoring Network Alarms.................................................................................................................................7369
8.5.6 Routine Maintenance.............................................................................................................................................7390
8.5.7 GUIs and Parameters for Fault Management........................................................................................................7399
8.5.8 FAQs About Fault Management............................................................................................................................7540
8.6 Monitoring the Nastar Server...................................................................................................................................7542
8.6.1 Setting the Monitoring Parameters........................................................................................................................7542
8.6.2 Setting the Monitoring Parameters of the xSAU...................................................................................................7546
8.6.3 Monitoring the Status of the Nastar Server...........................................................................................................7548
8.6.4 Monitoring the Status of the xSAU.......................................................................................................................7553
8.6.5 Distributing xSAU System Monitoring Results....................................................................................................7555
8.6.6 Monitoring the System's Network Connections....................................................................................................7556
Issue 03 (2015-07-30)

xiii
Nastar
Contents
8.6.7 Interface Reference for System Monitoring..........................................................................................................7558

8.7 Integrated Task Management...................................................................................................................................7587
8.7.1 Getting to Know Integrated Task Management.....................................................................................................7587
8.7.2 Customizing the Interface for Managing Scheduled Tasks...................................................................................7592
8.7.3 Creating User Scheduled Tasks.............................................................................................................................7592
8.7.4 Managing Scheduled Tasks...................................................................................................................................7594
8.7.5 Viewing Scheduled Tasks.....................................................................................................................................7598
8.7.6 GUIs and Parameters for Integrated Task Management........................................................................................7599
8.8 Managing Adapter Packages....................................................................................................................................7612
8.8.1 Delivering an Adapter Package.............................................................................................................................7613
8.8.2 Rolling Back an Adapter Package.........................................................................................................................7614
8.8.3 Viewing Log Information About Adapter Packages.............................................................................................7615
8.9 Managing Analysis Data..........................................................................................................................................7616
8.9.1 Checking the Integrity of Analysis Data...............................................................................................................7616
8.9.2 Periodically Deleting Analysis Data......................................................................................................................7618
9 Nastar Alarm Reference.........................................................................................................7620

9.1 ALM-33 The Server Is Disconnected from the Database........................................................................................7624
9.2 ALM-34 The Disk Usage Is Too High (Warning)...................................................................................................7625
9.3 ALM-35 The Disk Usage Is Too High (Minor).......................................................................................................7629
9.4 ALM-36 The Disk Usage Is Too High (Major).......................................................................................................7632
9.5 ALM-37 The Disk Usage Is Too High (Critical).....................................................................................................7635
9.6 ALM-38 The database process is abnormal.............................................................................................................7638
9.7 ALM-39 The database had exception logs...............................................................................................................7640
9.8 ALM-40 The ESN of the server does not match that in the license file...................................................................7642
9.9 ALM-42 The Database Usage Is Too High (Warning)............................................................................................7643
9.10 ALM-43 The Database Usage Is Too High (Minor)..............................................................................................7646
9.11 ALM-44 The Database Usage Is Too High (Major)..............................................................................................7650
9.12 ALM-45 The Database Usage Is Too High (Critical)............................................................................................7654
9.13 ALM-47 Memory Usage of Service Is Too High...................................................................................................7658
9.14 ALM-50 Task execution failure alarm...................................................................................................................7660
9.15 ALM-51 The temporary Feature field of the Nastar license file expires...............................................................7661
9.16 ALM-52 The temporary Feature field of the Nastar license file enters to the default state ..................................7663
9.17 ALM-53 High log space usage for the database.....................................................................................................7664
9.18 ALM-54 The swap Usage Is High..........................................................................................................................7665
9.19 ALM-55 Nastar License Consumption Reaches or Exceeds the Preset Threshold................................................7668
9.20 ALM-56 Users Having Not Logged In for an Excessively Long Time.................................................................7670
9.21 ALM-109 Network Device Failure........................................................................................................................7671
9.22 ALM-111 The Network Cable Is Disconnected.....................................................................................................7672
9.23 ALM-116 The Master Server Cannot Communicate with the Slave Server..........................................................7676
9.24 ALM-123 The Digital Certificate Is to Expire.......................................................................................................7678
9.25 ALM-124 The Digital Certificate Has Expired......................................................................................................7679
Issue 03 (2015-07-30)

xiv
Nastar
Contents
9.26 ALM-129 The Digital Certificate Is Invalid...........................................................................................................7680

9.27 ALM-151 The CPU Usage Is High........................................................................................................................7681
9.28 ALM-152 The Nastar Service Is Terminated Abnormally.....................................................................................7684
9.29 ALM-153 The Number of Login Attempts Reaches the Maximum......................................................................7686
9.30 ALM-154 The Memory Usage Is Too High...........................................................................................................7687
9.31 ALM-294 Expired Nastar License File..................................................................................................................7690
9.32 ALM-295 Nastar License File in Default State......................................................................................................7691
9.33 ALM-296 The NE Capacity Reached the Threshold Alarm..................................................................................7692
9.34 ALM-297 The Nastar License Expired..................................................................................................................7693
9.35 ALM-298 The User in the SMManagers Group Changes a User's Password........................................................7694
9.36 ALM-299 An Nastar User Is Added to the Administrators, SMManagers or Sub Domain User Group...............7695
9.37 ALM-801 Nastar License Beyond Limitation........................................................................................................7695
9.38 ALM-50001 Subrack Environment Low Temperature (Major).............................................................................7697
9.39 ALM-50002 Subrack Environment Low Temperature (Critical)...........................................................................7699
9.40 ALM-50004 Subrack Environment High Temperature (Major)............................................................................7702
9.41 ALM-50005 Subrack Environment High Temperature (Critical)..........................................................................7705
9.42 ALM-50007 Board Low Voltage (Major)..............................................................................................................7708
9.43 ALM-50008 Board Low Voltage (Critical)............................................................................................................7710
9.44 ALM-50010 Board High Voltage (Major).............................................................................................................7713
9.45 ALM-50011 Board High Voltage (Critical)...........................................................................................................7716
9.46 ALM-50013 CPU Kernel Overheated....................................................................................................................7718
9.47 ALM-50014 Lower Handle Opened.......................................................................................................................7721
9.48 ALM-50015 Upper Handle Opened.......................................................................................................................7723
9.49 ALM-50026 Abnormal Network Interfaces Used for Data Synchronization Between the Active and Standby SMMs
........................................................................................................................................................................................7724
9.50 ALM-50027 The SMM Is Not Properly Inserted...................................................................................................7726
9.51 ALM-50040 ATAE PDB Abnormal......................................................................................................................7728
9.52 ALM-50042 ATAE Low Fan Speed (Critical).......................................................................................................7732
9.53 ALM-50044 ATAE Fan Assembly Failure (Major)...............................................................................................7734
9.54 ALM-50045 ATAE Fan Assembly Failure (Critical)............................................................................................7738
9.55 ALM-50047 ATAE Board Failure (Minor)............................................................................................................7741
9.56 ALM-50048 ATAE Board Failure (Major)............................................................................................................7744
9.57 ALM-50050 ATAE Subrack SMM Board Failure (Minor)...................................................................................7747
9.58 ALM-50051 ATAE Subrack SMM Board Failure (Major)...................................................................................7752
9.59 ALM-50054 ATAE Fan Assembly Failure............................................................................................................7756
9.60 ALM-50055 ATAE Subrack Power Supply Failure..............................................................................................7757
9.61 ALM-50056 ATAE PEM's IPMB One-Sided Connection.....................................................................................7759
9.62 ALM-50057 ATAE SMM Board Failover Failure.................................................................................................7762
9.63 ALM-50058 ATAE Data File Damaged................................................................................................................7766
9.64 ALM-50059 ATAE LSW Board BASE Port Failure.............................................................................................7768
9.65 ALM-50060 ATAE OSMU Board NTP Failure....................................................................................................7771
9.66 ALM-50065 ATAE Board Power-Off...................................................................................................................7772
Issue 03 (2015-07-30)

xv
Nastar
Contents
9.67 ALM-50066 ATAE Board Is Not Present..............................................................................................................7773

9.68 ALM-50067 ATAE LSW Board FABRIC Port Failure.........................................................................................7775
9.69 ALM-90001 CPU Fault..........................................................................................................................................7777
9.70 ALM-90002 Memory Fault....................................................................................................................................7778
9.71 ALM-90003 Hard Disk Fault.................................................................................................................................7780
9.72 ALM-90004 Power Supply Fault...........................................................................................................................7781
9.73 ALM-90005 Fan Fault............................................................................................................................................7782
9.74 ALM-90006 RAID Fault........................................................................................................................................7784
9.75 ALM-90007 CPU Excessively High CPU Temperature........................................................................................7785
9.76 ALM-90008 Excessively High RAID Temperature...............................................................................................7786
9.77 ALM-90009 Excessively High Temperature at Air Intake Vents..........................................................................7787
9.78 ALM-90113 Failure to Obtain Hardware Information...........................................................................................7789
10 Glossary...................................................................................................................................7790
Issue 03 (2015-07-30)

xvi
Nastar
1 About This Help
About This Help
About This Chapter

This Help provides you with the basic contents of the Help and the skills of using the Help. Thus,
you can conveniently obtain the information you need.
1.1 Intended Audience
The help is intended for network planning engineers, field engineers, system engineers, and
network operators.
1.2 Conventions
The conventions enable you to understand the help better.
Issue 03 (2015-07-30)

Nastar
1 About This Help
1.1 Intended Audience

The help is intended for network planning engineers, field engineers, system engineers, and
network operators.
1.2 Conventions
The conventions enable you to understand the help better.
Symbol Conventions
Symbol
Description
Indicates a potentially hazardous situation that, if not avoided, may
cause equipment damage, data loss, performance degradation, or
unexpected results.
Provides additional information to emphasize or supplement
important points of the main text.
GUI Conventions
Convention
Description
Boldface
Buttons, menus, parameters, tab pages, windows, and dialog box

titles are in boldface. For example, click OK.
>
Multi-level menus are separated by >. For example, choose File >
New > Folder. In this operation, File is the main menu, New is the
submenu of File, and Folder is the submenu of New.
Other Conventions
1.
The OK and Apply buttons

The OK and Apply buttons may be displayed in the same dialog box.
l OK: to make the modifications take effect and to close the dialog box.
l Apply: to make the modifications take effect but not to close the dialog box.
In the help, if both buttons exist, only the operations on the OK button are described.
2.
The Default button

Default: to restore all settings to the state after initial installation.
3.
Multiple accesses to an operation

An operation usually has multiple accesses. The help describes only one or two accesses
that are commonly used.
Issue 03 (2015-07-30)

Nastar
4.
1 About This Help
References for operations

l Simple references are described in Caution or Note in the operation procedure.
l Complex references are provided in the links of Related tasks, Related concepts, or
Related reference on the current page.
l Links are provided in the page that contains the Parent topic.
Issue 03 (2015-07-30)

Nastar
2 Nastar Overview
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.
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.
2.2 Analysis Data Sources
This section introduces the data sources used by each analysis function of the Nastar.
2.3 Product Functions
This section lists the analysis functions provided by the Nastar for the GSM, UMTS, LTE, and
PS Core networks.
2.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.
2.5 Basic Concept/Glossary
This section describes the basic concepts used in this document.
2.6 Guide to the Document
This section describes the intended audience, task type, and objective of each type of scenarios.
Issue 03 (2015-07-30)

Nastar
2 Nastar Overview

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.
Position in Networking (Obtain UMTS/GSM NE data from the SAU board)

In the Nastar system, the RAN SAU (RH2288) obtains the MR and CHR data of RNCs and
BSCs on a UMTS or GSM network from the SAU board. Figure 2-1 shows the Nastar position
in the scenario.
Figure 2-1 Nastar position
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.
Position in Networking (Obtain UMTS/GSM NE data from the Trace Server)

In the Nastar system, the RAN SAU (RH2288) obtains the MR and CHR data of RNCs and
BSCs on a UMTS or GSM network from the Trace Server. Figure 2-2 shows the Nastar position
in the scenario.
Issue 03 (2015-07-30)

Nastar
2 Nastar Overview
Figure 2-2 Nastar position
The communication between different units on the network is based on the TCP/IP protocol.
The Nastar server, eSAU, RAN SAU, 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.
Function of Each Unit

Table 2-1 describes the function of each unit.
Table 2-1 Description of the functional units
Issue 03 (2015-07-30)
System
Functional
Unit
Description
Radio
access
network
(RAN)
GBSS
Refers to the functional entity of the radio access network

(RAN) in GSM. The GBSS consists of the BTS and BSC.
It provides CS and PS data on the GSM RAN side for the
Nastar system.
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.

Nastar
System
Core
Network
(CN)
Network
manageme
nt system
2 Nastar Overview
Functional
Unit
Description
E-UTRAN
Refers to the functional entity of the RAN in LTE. The EUTRAN consists of the eNodeB. It provides data on the EUTRAN side for the Nastar system to analyze.
Serving GPRS
support node
(SGSN)
The SGSN is a functional unit at the CN. It provides PS

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

on the CN side for the Nastar system.
Mobility
management
entity (MME)
The MME provides data on the LTE RAN side for the
Nastar system to analyze.
U2000/M2000
A uniform management platform of Huawei mobile

networks. It manages the mobile NEs manufactured by
Huawei. It provides performance data, configuration data,
and alarm data for the Nastar system.
Trace Server
The LTE SAU obtains the eNodeB data on an LTE network

from the Trace Server.
The RAN SAU (RH2288) uses the Trace Server to obtain
the CHR and MR data of the RNCs and BSCs on a UMTS
or GSM network.
For details about Trace Server, see U2000/M2000 Trace
Server User Guide on U2000/M2000 Product
Documentation.
Nastar
system
SAU
The service aware unit (SAU) is an optional component of

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
Issue 03 (2015-07-30)
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.

Nastar
System
2 Nastar Overview
Functional
Unit
Description
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
aware unit
(eSAU)
The eSAU is a mandatory component of the Nastar system

for data aggregation. It is deployed at the OSS as an ATAE
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.
2.2 Analysis Data Sources

This section introduces the data sources used by each analysis function of the Nastar.
2.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 2-3 shows the sources of the Nastar analysis data on the network.
Issue 03 (2015-07-30)

Nastar
2 Nastar Overview
Figure 2-3 Data sources for Nastar GSM analysis
Table 2-2 describes the data sources for Nastar analysis.

Table 2-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
to Nastar
analysis
GSM performance data
The data is obtained from the U2000/M2000 and

used for GSM MR analysis, GSM frequency
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 03 (2015-07-30)

Nastar
2 Nastar Overview
Function
NOTE
Personal
data is used
during
Nastar
service
provision
and
maintenanc
e. You must
abide by
local laws,
regulations,
and
company
policies and
take
effective
measures to
protect
subscriber
data.
Related
information
can be
anonymized
to protect
user
privacy.
Neighboring GSM cell

measurement data

used for GSM frequency analysis and neighboring
cell analysis.
GSM uplink interference

data

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

GSM geographic observation.
GSM
complaint
analysis
support
data

GSM complaint analysis support, optional.
GSM
geographic
observatio
n data

GSM geographic observation.
GSM
terminal
analysis
data

GSM terminal analysis.
GSM
complaint
analysis
support
data

GSM complaint analysis support.
GSM VIP
analysis
data

GSM VIP analysis.
GSM cell
performanc
e analysis
data

GSM cell performance analysis.
GSM
CHR data
2.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.
Issue 03 (2015-07-30)

10
Nastar
2 Nastar Overview
Figure 2-4 Data sources for Nastar UMTS analysis

Table 2-3 Data sources for Nastar UMTS analysis
Function
UMTS configuration data

UMTS Engineering Parameters

antennas.
observation of analysis results. The parameters
are essential for the geographic observation
function, but optional for other functions.
Data related
to Nastar
analysis
Issue 03 (2015-07-30)
MR data
UMTS
coverage
data

UMTS coverage analysis.
UMTS
pilot
pollution
analysis
data

UMTS pilot pollution analysis.

11
Nastar
2 Nastar Overview

NOTE
Personal
data is used
during
Nastar
service
provision
and
maintenanc
e. You must
abide by
local laws,
regulations,
and
company
policies and
take
effective
measures to
protect
subscriber
data.
Related
information
can be
anonymized
to protect
user
privacy.
Issue 03 (2015-07-30)
Function
UMTS
intrafrequency
neighborin
g cell
analysis
data

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

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

UMTS/GSM neighboring cell analysis.
UMTS
geographic
observatio
n data

UMTS geographic observation.
UMTS
terminal
analysis
data

UMTS terminal analysis.
Received
total
wideband
power
(RTWP)
data
UMTS
uplink
interferenc
e analysis
data

used for UMTS uplink interference analysis.
CHR data
UMTS
geographic
observatio
n data

UMTS geographic observation.
UMTS
terminal
analysis
data

UMTS terminal analysis.

12
Nastar
2 Nastar Overview
Function
UMTS
complaint
analysis
support
data

UMTS complaint analysis support.
UMTS VIP
analysis
data

UMTS VIP analysis.
UMTS cell
performan
ce analysis
data

UMTS cell performance analysis.
2.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
3GPP-based LTE Data Sources
Mapping between Nastar- and 3GPP-based LTE data sources
Nastar-based LTE Data Sources

Figure 2-5 shows the sources for Nastar analysis data on an LTE network.
Figure 2-5 Sources for Nastar analysis data (LTE)
Issue 03 (2015-07-30)

13
Nastar
2 Nastar Overview
Table 2-4 describes the sources for Nastar analysis data on an LTE network.
Table 2-4 Sources for Nastar analysis data (LTE)
Data Source
Function
LTE configuration data

LTE engineering parameters

antennas.
observation of analysis results. The parameters are
essential for the geographic observation function,
but optional for other functions.
Data related
to Nastar
analysis
NOTE
Personal
data is used
during
Nastar
service
provision
and
maintenanc
e. You must
abide by
local laws,
regulations,
and
company
policies and
take
effective
measures to
protect
subscriber
data.
Related
information
can be
anonymized
to protect
user
privacy.
Issue 03 (2015-07-30)
eNodeB
CHR data:
The data is
also
referred to
as cell
trace data.
LTE
coverage
analysis
data
The data is used for LTE coverage analysis. It is

uploaded to the LTE SAU through the Trace
Server.
LTE
network
geographic
observatio
n data
The data is used for LTE network geographic

observation. It is uploaded to the LTE SAU
through the Trace Server.
LTE
terminal
analysis
data
The data is used for LTE terminal analysis. It is

Server.
LTE
complaint
analysis
support
data
The data is used for LTE complaint analysis

support. It is uploaded to the LTE SAU through
the Trace Server.
LTE VIP
analysis
data
The data is used for LTE VIP analysis. It is

Server.
LTE cell
performanc
e analysis
data
The data is used for LTE cell performance

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

14
Nastar
2 Nastar Overview
Data Source
Function
eNodeB
singlesubscriber
allsignaling
data
LTE VIP
analysis
data
The data is used for LTE VIP analysis. It contains

all-signaling information for the analysis of
important VIP subscribers and is uploaded to the
LTE SAU through the Trace Server.
MME
CHR data
LTE
terminal
analysis
data
The data is used for LTE terminal analysis. It

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

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

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

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

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
Subscriber complaint
Malfunctioning UE
Checking radio coverage
Testing a new feature
Fine-tuning and optimization of algorithms/procedures
Analyzing drop calls in E-UTRAN
Periodical sampling of network performance
Trace Objects
Issue 03 (2015-07-30)

15
Nastar
2 Nastar Overview
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.
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.
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.
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
Issue 03 (2015-07-30)
Nastar-based
LTE Data
Sources
Trace Capability
eNodeB CHR
data: The data
is also referred
to as cell trace
data.
Cell trace data at the medium level
N/A
Trace objects: devices

Trace level: medium

16
Nastar
2 Nastar Overview
Nastar-based
LTE Data
Sources
Trace Capability
eNodeB singlesubscriber
trace data
Single-subscriber trace data at the

maximum level
l eRAN3.X (BTS3900
V100R005C00/
V100R005C01): 20 UEs/
eNodeBs
Trace objects: single subscribers

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
data
Regardless of the trace levels and

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.
N/A
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.
2.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.
Issue 03 (2015-07-30)

17
Nastar
2 Nastar Overview
Figure 2-6 Data sources for Nastar PS core analysis

Table 2-5 Data sources for Nastar PS core analysis
Issue 03 (2015-07-30)
Function
SGSN/MME
CHR data
PS core
terminal
analysis data
The data is obtained from a PS SAU and used for PS core

terminal analysis.
PS core
complaint
analysis
support

complaint analysis support.
PS core VIP
analysis data

VIP analysis.

18
Nastar
2 Nastar Overview
Function
NOTE
Personal
data is used
during
Nastar
service
provision
and
maintenance
. You must
abide by
local laws,
regulations,
and
company
policies and
take
effective
GGSN/SAEmeasures to
GW
CHR
protect
subscriber
data
data. Related
information
can be
anonymized
to protect
user privacy.
Data for root

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

complaint analysis support.
PS core VIP
analysis data

VIP analysis.
Data for root

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

This section lists the analysis functions provided by the Nastar for the GSM, UMTS, LTE, and
PS Core networks.
Issue 03 (2015-07-30)
Scenario
Function
Description
Networ
k
Basic
network
optimizati
on
Coverage
analysis,
also called
MR analysis
on the GSM
network
The information about the radio links involved in a

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

19
Nastar
Scenario
2 Nastar Overview
Function
Description
Networ
k
Neighborin
g cell
analysis
This function is performed to analyze neighboring

cells based on the MRs of the actual calls of all the
subscribers in the test cell. It supports the analysis of
defined and undefined neighboring cells. It helps to
identify and handle the problems, including
redundant and missing neighboring cell
configuration of a cell and improper priorities of
neighboring cells. In addition, it can be performed to
solve network service quality problems caused by
redundant or missing neighboring cell configuration.
GSM/
UMTS
In addition to intra-RAT neighboring cell analysis,

such as neighboring GSM cell analysis, UMTS intrafrequency 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 03 (2015-07-30)
Uplink
interference
analysis
This function is performed to analyze whether the

values of the main and diversity Received Signal
Strength Indicators (RSSIs) of the transmit and
receive channels of a BTS are normal. Based on the
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.
GSM/
UMTS
Frequency
analysis
This function is performed to evaluate the impact of

GSM frequency planning and analyze the cells and
Absolute Radio Frequency Channel Numbers
(ARFCNs) experiencing severe interference on the
current network. If cells and ARFCNs experiencing
server interference are detected during 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.
GSM

20
Nastar
Scenario
Network
analysis
User
assurance
Issue 03 (2015-07-30)
2 Nastar Overview
Function
Description
Networ
k
Pilot
pollution
analysis
The network systems based on the code division

multiple access (CDMA) technology are selfinterfered 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.
UMTS
Network
geographic
observation
Through the geographic display and statistical

analysis of network coverage, network traffic, and
network KPIs, the Nastar helps operators to detect
network problems, therefore reducing drive test
costs.
GSM/
UMTS/
LTE
TDD/
LTE
FDD
Cell
performanc
e analysis
Through the cell performance analysis, the Nastar

obtains the data of abnormal calls in problematic
cells, displays the data in comprehensive
presentation modes, analyzes the causes of abnormal
calls, and therefore helps network OM personnel
locate cell problems.
GSM/
UMTS/
LTE
TDD/
LTE
FDD
Root cause
analysis for
performanc
e problems
The root cause analysis function enables the Nastar

to collect statistics about signaling procedures on the
CN and to perform further analysis of possible causes
for procedure exceptions. This helps network
optimization engineers locate network problems and
improve O&M efficiency.
PS Core
Complaint
analysis
support
Whenever mobile subscribers encounter networkrelated problems, they lodge a complaint with the
operators. After receiving the complaint, the
operator can perform this function to obtain the user
call event records pertaining to the mobile user
concerned. Then, the operator can analyze the cause
of the problem and then locate and solve the problem.
This helps to improve the efficiency of handling
complaints, therefore improving user satisfaction.
GSM/
UMTS/
LTE
TDD/
LTE
FDD/PS
Core

21
Nastar
Scenario
2 Nastar Overview
Function
Description
Networ
k
VIP
analysis
This function is performed to filter the call records

of VIP subscribers from the user call event records
of the entire network and obtain the KPIs of the voice
and data services of VIP subscribers. The KPIs
include call drop rate, call setup duration, and
forward and reverse data rate. By monitoring the
service quality of VIP subscribers daily, the Nastar
operators can find out the potential complaints of
VIP subscribers and solve them in advance to ensure
that network problems do not arise. This helps to
provide better services for the VIP subscribers and
improve their satisfaction.
GSM/
UMTS/
LTE
TDD/
LTE
FDD/PS
Core
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
analysis
Terminal
analysis
Users can collect statistics of KPIs such as call drop

rate, access success rate, and handover success rate
based on terminal models from the user call event
record data of the entire network. The Nastar can
compare the performance data of the terminals and
provide useful reference information for network
operation and troubleshooting.
GSM/
UMTS/
LTE
TDD/
LTE
FDD/PS
Core
2.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.
Issue 03 (2015-07-30)

22
Nastar
2 Nastar Overview
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
Issue 03 (2015-07-30)
Default Value
GSM
UMTS
LTE
Average
number of
TRXs in a
cell
Average
number of
cells under a
controller
200 BSCs
1500 RNCs
3 eNodeBs
Average
number of
neighboring
cells of a
cell
32
32
32
Average cell
coverage
radius
500 meters
500 meters
500 meters
Number of
networklevel IMEITAC entries
100,000
100,000
100,000

23
Nastar
Parameter
2 Nastar Overview
Default Value
GSM
UMTS
LTE
Average
number of
IMEI-TAC
entries of a
cell per day
100
100
100
Total
number of
networklevel
subscribers
2,500,000
8,000,000
2,000,000
GSM
UMTS
LTE
Average
number of
BHCA per
subscriber
10
10
Average
traffic per
subscriber
in busy
hours
20mErl
20mErl
Busy-hour
percentage
coefficient
0.4
0.4
0.6
Percentage
of active
subscribers
in busy
hours
0.5
0.5
0.5
Average
number of
CS services
per
subscriber
in busy
hours
Default Traffic Model

Parameter
Issue 03 (2015-07-30)
Default Value

24
Nastar
Parameter
2 Nastar Overview
Default Value
GSM
UMTS
LTE
Average
number of
PS services
per
subscriber
in busy
hours
10
Average
number of
active cells
per
subscriber
in busy
hours
Average
number of
active cells
per
subscriber
per day
18
18
Percentage
of abnormal
calls
0.3
0.3
0.1
2.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 03 (2015-07-30)

25
Nastar
2 Nastar Overview
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 eventbased 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
Issue 03 (2015-07-30)
MCC refers to the mobile country code of a mobile subscriber.

26
Nastar
2 Nastar Overview
MNC refers to the mobile network code, that is, the PLMN code of a mobile subscriber.
PLMN refers to the public land mobile network.
MSIN refers to the mobile subscriber identification number.
NMSI refers to the national mobile subscriber identification 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.
Final assembly code (FAC): consists of two digits and is used to identify a vendor.
Serial Number (SNR): consists of six digits and is used to uniquely identify an MS when
the TAC and FAC of two MSs are the same.
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.
Site layers are generated when the engineering parameter files are imported, such as base
station layer.
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 03 (2015-07-30)

27
Nastar
2 Nastar Overview
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.
2.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.
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 03 (2015-07-30)

28
Nastar
3 Nastar Quick Start
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.
3.1 Nastar Operation Process
This section describes the operation process for network optimization by using Nastar and each
involved procedure.
3.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.
3.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.
3.4 Preparing Basic Data
This section describes how to collect basic data including configuration data, engineering
parameters, and map information before analyzing data.
3.5 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.
3.6 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.
Issue 03 (2015-07-30)

29
Nastar
3.7 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.
3.8 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.
3.9 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.
3.10 Exporting Analysis Reports
This section describes how to export the analysis reports as files.
3.11 Periodically Deleting Analysis Data
This section describes how to periodically delete analysis data. When the preset storage duration
for analysis data expires, the Nastar automatically deletes overdue analysis data on the Nastar
server and in the eSAU database. This ensures that the Nastar is running properly.
3.12 FAQs
This section describes the problems and solutions to the FAQs when using the Nastar, and also
provides methods for common operations.
Issue 03 (2015-07-30)

30
Nastar
3.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 3-1 shows the flowchart. For details, see Table 3-1.
Issue 03 (2015-07-30)

31
Nastar
Figure 3-1 Nastar operation process
Table 3-1 Operation procedures for network optimization by using Nastar
Issue 03 (2015-07-30)
No.
Procedure
Description
(1)
Start
3.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)
Prepar
ation
phase
Configuring
OSS and NE
Information
Users must configure OSS and NE information before the

Nastar can collect data. The OSS, eSAU, SAU, LTE SAU,
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.

32
Nastar
No.
Procedure
(3)
Description
Preparing
Basic Data
Before obtaining the data for analysis, users must collect

some basic data for analysis such as the configuration data,
engineering parameters, and map information.
Subscribing
to Analysis
Data
Before starting a theme analysis, users must turn on the

data switch of a required NE by using the data subscription
function. Once the data switch of the NE is turned on, the
Nastar can successfully collect the required data from the
NE for analysis.
Check the
Integrity of
Analysis
Data
Check that the Nastar has imported the data for analysis
into the database. The purpose is to ensure that an analysis
task can be processed normally.
Creating an
Analysis
Task
After an analysis task is created, the Nastar retrieves the

performance data of the desired NE from the database for
analysis.
(7)
View the
Analysis
Result
After the analysis is complete, users can view the analysis

result. The analysis result can be used as a basis for
network optimization.
(8)
Exporting
Analysis
Reports
You can export the analysis results into Excel files.
(4)
Data
acquisi
tion
phase
(5)
(6)
Analys
is
phase
3.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.
3.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.
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 03 (2015-07-30)

33
Nastar
Context
l
The default port number of the server is 31039. Do not change it in normal conditions.
Otherwise, you cannot log in to the Nastar client.
The Nastar server provides the default user account Nastar. The Nastar user has all operation
rights, and the password is Changeme_123 by default. After you successfully log in to the
Nastar client for the first time, change the password in time.
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.
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.
If you never use your new account to log in to the Nastar client, the Nastar does not disable
or delete the new account.
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.
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:
on the right of Server drop-down list.
1.
Click
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 03 (2015-07-30)

34
Nastar
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.
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.
3.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 3-2 shows the client GUI.
For details of the areas in the interface, see 8.1.4 Getting to Know the Client GUI.
Issue 03 (2015-07-30)

35
Nastar
Figure 3-2 Client GUI
1: Menu bar
2: Toolbar
3: Navigation tree
4: Output pane
5: Window bar
6: Task list pane
7: Task result pane
8: Status bar
3.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
. The Geographic Observation window is displayed.

In the Nastar main window, click
In this window, you can check the geographic distribution of sites on the network, or check
analysis results of added themes.
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.
Issue 03 (2015-07-30)

36
Nastar
Window
Figure 3-3 shows the Geographic Observation window.
Figure 3-3 Geographic Observation window
NOTE
If a counter in the left pane is gray after it is clicked, no counter data is available.
N Item
o
.
Description
Toolbar
Provides icons for you to perform operations. For detailed operations, see
Buttons on the toolbar.
Layer
navigati
on tree
Site
Layer
node
Before performing a geographic observation analysis, you have

to click
to load site layers. Currently, the Nastar allows you
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 03 (2015-07-30)

37
Nastar
N Item
o
.
Description
Polygon
Areas
node
By drawing a polygon, you can further analyze only desired areas.

All created polygons are displayed under the Polygon Areas
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.
to save the
l Saving cells as an NE group: You can click
cells in a polygon as an NE group. These cells can be used
directly during theme analysis and are highlighted in the
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 03 (2015-07-30)

38
Nastar
N Item
o
.
Description
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
Shortcut menus and parameters supported by counters vary according to
themes. You can log in to the Nastar client to view details.
Issue 03 (2015-07-30)

39
Nastar
N Item
o
.
Description
The display effects of themes are different:
Chart
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

legend.
. For coloring description, see the
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
details
area
Displays contribution values of the top 5 cells related to a selected grid under
a counter. In addition:
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 gridcell 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
the table content.
to filter
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 03 (2015-07-30)

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

in area 1. In the displayed Layer Management dialog box, click
l 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.
Informa
tion
area
This area does not display any information when it is opened for the first time.
You can select desired objects to view related information:
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
Issue 03 (2015-07-30)
Functio
n
Descrip
tion
Operation
Imports
a map
file.
For detailed operations, see Importing Map Files.

41
Nastar
Button
Functio
n
Descrip
tion
Operation
Loads
site
informat
ion.
Site information is displayed in the Geographic Observation

window. Before you load site information, ensure that engineering
parameters have been imported into the Nastar. For detailed
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
layers.
Click
on the toolbar. In the displayed Layer Management
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
hides a
legend.
Moves a
map.
Selects
objects.
Issue 03 (2015-07-30)
Click
on the toolbar to open the legend and view the counter
value range mapped to each color.
You can also reset the legend in the Layer Management dialog
box.
Click
on the toolbar, move the pointer to the map and drag the
map to the required direction.
Click
on the toolbar and click an object on the map to select it.

42
Nastar
Button
Functio
n
Descrip
tion
Measure
s the
distance.
Operation
1. Click
on the toolbar.
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.
or
Zooms
in or out
a map.
Views
the
panoram
ic scene
of a map.
Refreshe
s a map.
Saves a
map.
Click
on the toolbar to zoom in the map or click
out the map.
to zoom
NOTE
You can scroll the mouse wheel forward or backward to zoom in or out the
map.
Click
on the toolbar. The Nastar displays all the objects in the
You can click

on the menu bar to re-execute operations that are
not responded to and to refresh maps.
1. Click
on the toolbar. The Save dialog box is displayed.
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 03 (2015-07-30)

43
Nastar
Button
Functio
n
Descrip
tion
Operation
Draws a
polygon.
You can draw a polygon for hot spots to filter multiple cells or grids.
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.
l At least one cell must be contained in the polygon. Otherwise, the
polygon is not displayed in the Polygon Areas in the navigation tree.
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 03 (2015-07-30)

44
Nastar
Button
Functio
n
Descrip
tion
Operation
Filters
cells.
You can optimize only cells by filtering cells based on specified

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 Cell Group Definition dialog
box is displayed.
b. Select a value for Network System.
c. Select a matched area in the Polygon Areas.
3. Match Cells.
l Click Match Configuration. The Nastar matches the
engineering parameter information about a cell with the
configuration data of the cell in the matched areas. If the
matching for a cell is successful, the cell is displayed in the
Match Results in the right pane. If the matching for a cell
fails, the cell is displayed in the Match Configuration in the
left pane.
l Select or deselect a cell from Match Results.
l Click Highlight, and the selected cell in the Match
Results is highlighted in the middle of the Geographic
Observation window.
l Click Cancel Highlight, the highlight of the selected cell in
the Match Results is canceled.
l 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.
l Click Close to exit the Cell Group Definition dialog box.
Issue 03 (2015-07-30)

45
Nastar
Button
Functio
n
Descrip
tion
Searches
for cells.
Operation
1. Click
on the toolbar or use the shortcut key Ctrl+F. The
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
multiple
windows
.
Select two to four counters in the layer navigation tree and click
on the toolbar. The Nastar displays the layers mapped to the
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
grid data.
1. Click
on the toolbar. The Export Data dialog box is
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 03 (2015-07-30)

46
Nastar
Button
Functio
n
Descrip
tion
Exports
Google
Earth
data.
Operation
1. Click
on the toolbar. The Export Data dialog box is
displayed.
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.
NOTE
After the export is successful, open the Google Earth data file in .kmz format
using the Google Earth software. You are advised to set the default program
for opening .kmz files to the Google Earth software.
Issue 03 (2015-07-30)

47
Nastar
Button
Functio
n
Descrip
tion
Operation
Imports
points.
The Nastar allows users to import vector points of specified

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.
3.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.
3.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 3-4 on the Nastar client.
Issue 03 (2015-07-30)

48
Nastar
Figure 3-4 Configuration procedures
Table 3-2 Configuration procedures
Issue 03 (2015-07-30)
Configur
ation
Scenario
No.
Step
Description
Preparatio
ns for OSS
and NE
Informatio
n
Configurat
ion
3.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.
Configuri
ng
informatio
n about
a.1
Configuring
eSAU information
In this step, configure the IP address, port

number, and FTP information of the server
running the eSAU software.

49
Nastar
Configur
ation
Scenario
No.
Step
Description
NEs on the
radio
access
network
(RAN)
side
a.2
Configuring OSS
information
In this step, configure the IP address, software

version, networking mode, and FTP information
of the OSS server.
a.3
Selecting RAN
NEs managed by
an OSS
In this step, select the RAN NEs managed by an

OSS, such as BSC, RNC, and eNodeB.
a.4
Setting SAU or
LTE SAU
information.
In this step, configure the SAU or LTE SAU

information before you use the analysis function
of the SAU or LTE SAU board.
b.1
Configuring
eSAU information
In this step, configure the IP address, port

number, and FTP information of the server
running the eSAU software.
b.2
Configuring OSS
information
In this step, configure the IP address, software

version, networking mode, and FTP information
of the OSS server.
b.3
Selecting CN NEs
managed by an
OSS
In this step, select the CN NEs managed by an

OSS, such as serving GPRS support node
(SGSN).
b.4
Setting PS SAU
information.
In this step, configure the PS SAU information

before you use the analysis function of the CN
network.
Configuri
ng
informatio
n about
NEs on the
core
network
(CN) side
3.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 3-3.
Table 3-3 Pre-configuration checklist
Scenario
Required Information
Configuring eSAU
information
Information about the server running the eSAU software, including:

l IP address of the server
l User name, password, and port number for the FTP service of the
server
Issue 03 (2015-07-30)

50
Nastar
Scenario
Configuring OSS
information
Information about the OSS system within the analysis area,

including:
l Version number and networking scheme
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
NEs on the RAN side
Information about the SAU, including:

l IP address and port information of the SAU board for the GSM
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 03 (2015-07-30)

51
Nastar
Scenario
Configuring
information about
NEs on the CN side
Information about the serving GPRS support node (SGSN/MME)

within the analysis area, including:
l IP address of the PS SAU server for SGSN/MME
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.
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.
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 3-4.
Issue 03 (2015-07-30)

52
Nastar
Table 3-4 Operation permissions

Operation
Permissio
n
GUI-based
Navigation Path
Purpose
OSS Version
Nastar
Collection
Task
Manageme
nt
Security > Security

Management >
Operation Rights >
Network
Management
Application >
Operation > Data
Collection
Management under
a user or user group
Used for invoking the

CORBA interface of the
DccTool and for creating,
deleting, and modifying
Nastar-related collection
tasks in the following
themes: GSM uplink
interference analysis and
UMTS uplink interference
analysis.
U2000/M2000
V200R013C00 or
later
OSS Tool
Collection
Task
Manageme
nt
Security > Security

Management >
Operation Rights >
Network
Management
Application >
Operation > Data
Collection
Management under
Used for using the DccTool

to create data collection tasks
through the centralized task
management function of the
U2000 in the following
themes: GSM uplink
interference analysis and
UMTS uplink interference
analysis.
Send MML
to NE
Security > Security

Management >
Operation Rights >
Network
Management
Application >
Operation > Data
Collection
Management under
Used for issuing MML

commands to NEs through
the DccTool in all themes.
Security > Security

Management >
Operation Rights >
Network
Management
Application >
Operation > Data
Collection
Management under
Used for invoking the

CORBA interface of the
DccTool to obtain the basic
U2000 information (for
example, the FTP, version,
and DccTool version) in all
themes.
Query OSS
Basic Info
Issue 03 (2015-07-30)
U2000/M2000
V200R013C00 or
later
U2000/M2000
V200R013C00 or
later

U2000/M2000
V200R013C00 or
later
53
Nastar
Operation
Permissio
n
Collect NE
PM Data
Collect NE
Signal Data
RAN Pool
Manageme
nt
Issue 03 (2015-07-30)
GUI-based
Navigation Path
Purpose
OSS Version
Security > Security

Management >
Operation Rights >
Network
Management
Application >
Operation > Data
Collection
Management under
Used for setting performance

counters and objects for NEs
and exporting the
performance results of NEs
(for example, NodeBs) that
do not support file interfaces
in the following themes:
GSM neighboring cell
analysis, GSM frequency
analysis, GSM MR analysis,
and GSM/UMTS
neighboring cell analysis.
U2000/M2000
V200R013C00 or
later
Security > Security

Management >
Operation Rights >
Network
Management
Application >
Operation > Data
Collection
Management under
Used for collecting NE

signaling data through the
DccTool in all LTE themes.
U2000/M2000
V200R013C00 or
later
Used for obtaining the Trace

Server information during
the configuration of the OSS
information. The Nastar user
can obtain the Trace Server
information from the U2000.
U2000
V200R014C00CP
2102 and later
V200R014
versions or
V200R015C00SP
C200 and later
V200R015
versions
Security > Security

Management >
Operation Rights >
Network
Management
Application >
Operation >
System Operation
> Configuration
Management under
Used for modifying RNC

pools and BSC pools in all
themes.

U2000/M2000
V200R013C00 or
later
54
Nastar
Operation
Permissio
n
RAN Pool
Manageme
nt Browser
Task
Manageme
nt
3.
GUI-based
Navigation Path
Purpose
Security > Security

Management >
Operation Rights >
Network
Management
Application >
Operation >
System Operation
> Configuration
Management under
Used for querying RNC

pools and BSC pools in all
themes.
Security > Security

Management >
Operation Rights >
Network
Management
Application >
Operation >
System
Maintenance >
Task Management
under a user or user
group
Used for viewing tasks in the

window for centralized task
management in all themes.
OSS Version
U2000/M2000
V200R013C00 or
later
U2000/M2000
V200R013C00 or
later
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
Account
Command Groups to Be Bound to the User

Account
BSC6900 GSM, BSC6900 UMTS,

BSC6900 GU, BSC6910 GSM,
BSC6910 UMTS, BSC6910 GU and
BTS3900
G_0, G_1, G_2, G_3 and G_21
3.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.
Issue 03 (2015-07-30)

55
Nastar
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.
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

firstly,
The eSAU modification window will be

displayed. Please perform Step 2.
You modify the configured eSAU

information,
1. Click eSAU in the navigation tree in the OSS

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 3-5.
Issue 03 (2015-07-30)

56
Nastar
Figure 3-5 OSS Information Management window
Table 3-5 describes basic eSAU server information.

Table 3-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 3-6 describes eSAU FTP information.
Table 3-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 03 (2015-07-30)

57
Nastar
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 3-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 3-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.
Issue 03 (2015-07-30)
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.

58
Nastar
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.
3.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.
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 3.3.2 Preparations
for OSS and NE Information Configuration.
You have obtained U2000/M2000 system information, such as the IP address and the
network mode. For details, see Table 3-8, Table 3-9 and Table 3-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 03 (2015-07-30)

59
Nastar
Procedure
Step 2 Click NE Management in the navigation tree in the OSS Information Management window,
as shown in Figure 3-6.
Figure 3-6 NE Management navigation tree
You can use Alt+R to refresh the NEs displayed in the NE Management.
Step 3 Click Create OSS in the lower-right of the window. The window shown in Figure 3-7 is
displayed.
Figure 3-7 OSS information
Issue 03 (2015-07-30)

60
Nastar
Step 4 Set basic OSS information by referring to Table 3-8.

Table 3-8 Basic OSS information
Param
eter
Description
Mandator
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

and the Nastar.
Mandatory
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
k Mode
Networking mode of the U2000/M2000, which includes:
Mandatory
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
IP address of the U2000/M2000 server.
Mandatory
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 Enabling the Communication Between the
Nastar Server and the U2000/M2000 Server with an NAT
Device Available (PC Server, Optional) in Commissioning
Guide for the corresponding server model.
Issue 03 (2015-07-30)
Port
Port number used for logging in to the U2000/M2000 server.

Generally, the port number is 10511.
Mandatory
User
Name
Name of the user for logging in to the U2000/M2000 client.
Mandatory

61
Nastar
Param
eter
Description
Mandator
y/
Optional
Passwor
d
Password of the user for logging in to the U2000/M2000 client.
Mandatory
Internal
IP
IP address for the communication between the U2000/M2000 and

the OM network.
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.
Optional
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
Availab
le
Set the U2000/M2000 and the Nastar mode of communication for

SSL. By default, the secure communication mode (SSL) is selected.
Communication modes of the U2000/M2000 include SSL, Both,
and Common. The Nastar communication modes need to be set
based on the U2000/M2000 communication mode.
Mandatory
l When the U2000/M2000 communication mode is SSL, the

Nastar communication mode must also be set to SSL.
l When the U2000/M2000 communication mode is Both, the
Nastar communication mode can be set to SSL or non-SSL.
l When the U2000/M2000 communication mode is Common, the
Nastar communication mode must be set to non-SSL.
l When the Nastar communicates with U2000/M2000 in SSL
mode, both SSL port and non-SSL port must be opened on the
firewall. When the Nastar communicates with U2000/M2000 in
non-SSL mode, only non-SSL port must be opened on the
firewall. For more information, see Nastar Communication
Matrix
NOTICE
l If you need to change the communication mode, also change it on the
eSAU server. Otherwise, the basic subscription issuing fails. For details
about how to change the communication mode on the eSAU server, see
3.12.7 What Do I Do if the System Displays Login U2000/M2000
Failed When a Nastar Basic Data Subscription Task Fails?.
l 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.)
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.
Issue 03 (2015-07-30)

62
Nastar
Param
eter
Description
Mandator
y/
Optional
Descrip
tion
Description information.
Optional
Step 5 Set OSS FTP information by referring to Table 3-9.

Table 3-9 OSS FTP information
Param
eter
Description
Mandatory/
Optional
User
Name
Name of the user for connecting to the FTP service on the U2000/
M2000.
Mandatory
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
rd
Mandatory
Port
Mandatory
Mode
Transfer mode of the FTP server, consisting of Passive and

Active.
Mandatory
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
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 03 (2015-07-30)

63
Nastar
Param
eter
Description
Mandatory/
Optional
Protoco
l
l SFTP: encrypted FTP transfer, which requires the support from

the FTP server. You must select this protocol if the operating
system of the U2000/M2000 server connected to the Nastar has
been hardened.
Mandatory
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.

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
l When the Trace Server and U2000/M2000 are co-deployed on a SUN or HP minicomputer, the Nastar
is not supported.
l 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.
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 3-10.

Table 3-10 Slave server FTP information
Issue 03 (2015-07-30)
Param
eter
Description
Mandato
ry/
Optional
Server
IP
IP address of the slave server.
Mandator
y

64
Nastar
Param
eter
Description
Mandato
ry/
Optional
NAT
IP
Configure the slave server IP address that has been translated

using NAT.
Optional
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
User
Name
Name of the user for connecting to the FTP service on the slave
server. The default user name is ftpuser.
Mandator
y
FTP
Passw
ord
Mandator
y
Port
Mandator
y
Mode

Active.
Mandator
y
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.
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 03 (2015-07-30)

65
Nastar
Param
eter
Description
Mandato
ry/
Optional
Protoc
ol
l SFTP: encrypted FTP transfer, which requires the support

from the FTP server. You must select this protocol if the
operating system of the U2000/M2000 server connected to
the Nastar has been hardened.
Mandator
y
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
l If the U2000/M2000 is deployed in an ATAE cluster system, the
l If the U2000/M2000 is deployed on an IBM server, the operating
system is hardened upon factory delivery.

l 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 3-11.
NOTE
l You can use Alt+G to obtain the Trace Server version and the FTP information.
l You can use Alt+A to add the Trace Server information.
Configure the Trace Server information in the following scenarios:

l When the LTE theme analysis is used.
l When the RAN SAU (RH2288) obtains the CHR or MR data of RNCs or BSCs on a UMTS
or GSM network from the Trace Server.
NOTE
l When you configure Trace Server information, ensure Nastar can connect to the Trace Server device
normally.
l When the Trace Server and U2000/M2000 are co-deployed on a SUN or HP minicomputer, the Nastar is
not supported.
l When you configure Trace Server information, Version is set to the Trace Server version that the system
automatically obtains from the Trace Server. Only Trace Server V200R15C10 supports you to configure
the RAN SAU (RH2288) obtaining the CHR or MR data of RNCs or BSCs on a UMTS or GSM network
from the Trace Server.
Issue 03 (2015-07-30)

66
Nastar
Table 3-11 Trace Server FTP information

Param
eter
Description
Mandatory/
optional
Server
IP
IP address of the Trace Server.
Mandatory
FTP
User
Name
Name of the user for connecting to the FTP service on the Trace
Server.
Mandatory
FTP
Passwo
rd
Mandatory
Port
Mandatory
Mode

Active.
Mandatory
The user for connecting to the FTP service on the Trace Server is
ftpuser.
l Passive mode: The client sends a connection request to the FTP

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
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 03 (2015-07-30)

67
Nastar
Param
eter
Description
Mandatory/
optional
Protoco
l
l SFTP: encrypted FTP transfer, which requires the support from

the FTP server. You must select this protocol if the operating
system of the Trace Server connected to the Nastar has been
hardened.
Mandatory
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

NOTE
The FTP protocol has security risks. You are advised to use security
protocols, such as SFTP and FTPS.
Step 8 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.
Modify OSS information.

1.
In the navigation tree, select a node to be modified and click Modify.
2.
Modify OSS information.
3.
Click OK.
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.
Issue 03 (2015-07-30)
In the displayed dialog box, click OK.

68
Nastar
3.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 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 3-8.
Figure 3-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.
Issue 03 (2015-07-30)

69
Nastar
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 3.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.
Select LTE NEs and right-click and choose Select NE from the shortcut menu.
2.
In the Select NE window, choose Advanced > eNodeB Management Group Settings.
The eNodeB Management Group Settings dialog box is displayed.
3.
Select the eNodeB Management Group and the NEs to be added to the group.
,
,
, or
to select NEs. You can click a singlel Click
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.
4.
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
Group column.
following a selected LTE NE in the eNodeB Management
Step 7 Click OK.

----End
Follow-up Procedure
l
Issue 03 (2015-07-30)

70
Nastar
NOTE
Refresh.
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.
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.
NOTICE
l Basic data subscription and application data subscription needs 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.

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.
Issue 03 (2015-07-30)

71
Nastar
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.
In the RNC in Pool scenario, add NEs one by one. In other scenarios, hold down
the Ctrl key to select multiple NEs.
6.
l
Click OK.
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.
Modify the description of the NEs managed by the OSS.

1.
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.
Delete NEs managed by the OSS.

NOTE
l Disable the subscription information about NEs before deleting them.

l After the Nastar delivers NE subscription, the Nastar does not support disabling of the NE subscription
information if NE FDN and NE Name of the NEs are changed at the same time. As a result, the NEs
specified by the parameters cannot be deleted. If this occurs, contact Huawei technical support.
For example, if NE FDN and NE Name of an NE are changed from NE FDN1 and NE Name1 to
NE FDN2 and NE Name2 on the M2000/U2000 respectively, the Nastar does not support disabling
of the NE subscription information and the NE cannot be deleted.
1.
Managementwindow.
2.
On the RAN NE List tab page, select an NE managed by the OSS.
3.
Click Modify SAU > Delete SAU to delete the NE.
4.
Click OK.

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
Issue 03 (2015-07-30)
You have selected an NE.

72
Nastar
You have obtained related SAU information.

NOTE
l (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 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.
When RAN SAUs (RH2288) obtain MR and CHR data of BSCs and RNCs from the Trace
Server, each RAN SAU (RH2288) can be connected to a maximum of five BSCs and RNCs.
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.
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.
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.
For a newly added NE, after setting the SAU, you must turn on the anonymization switch
again. For detailed operations, see Setting the Nastar Non-Anonymization Data Analysis
Switch.
Context
Procedure
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 3-9.
Issue 03 (2015-07-30)

73
Nastar
Figure 3-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 03 (2015-07-30)

74
Nastar
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.
NOTICE
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.
Data Source indicates the mode in which the SAU obtains data. When the SAU obtains
data from the Trace Server, set this parameter to Trace Server. In other scenarios, use the
default value Common.
NOTICE
When the value of Data Source is changed from Common to Trace Server, the historical
data saved on the SAU board will be lost.
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 hours. 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.
Issue 03 (2015-07-30)

75
Nastar
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
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.
Automatic access to eNodeBs

Periodic automatic access to eNodeBs
1.
In the RAN NE List window, select an LTE node and right-click it.
2.
Choose Set Periodic Automatic NE Access from the shortcut menu to display the
Set Periodic Automatic NE Access dialog box.
3.
Configure parameters shown in Table 3-12 as required.

Table 3-12 Parameter description
4.
Parameter
Description
Value Range
Enable automatic access
Indicates whether
automatic access to
eNodeBs is allowed.
Access at
Indicates the time when

periodic automatic
access to eNodeBs is
triggered. By default, the
Nastar system
automatically connects
to eNodeBs at 02:00 in
the morning for the first
time.
00:00 to 24:00
eNodeB management
group
Indicates the eNodeB

group that supports
automatic access.
eNodeB group that has

been created in the
Nastar system. For
details, see Configuring
LTE eNodeB
Management Group
(Optional).
Click OK.
Immediate automatic access to eNodeBs

1.
Issue 03 (2015-07-30)
76
Nastar
2.
Choose Set Immediate Automatic NE Access from the shortcut menu to display
the Set Immediate Automatic NE Access dialog box.
3.
Configure parameters shown in Table 3-13 as required.

Table 3-13 Parameter description
Parameter
Description
Value Range
eNodeB management
group
Indicates the eNodeB

group that supports
automatic access.
eNodeB group that has

been created in the
Nastar system. For
details, see Configuring
LTE eNodeB
Management Group
(Optional).
NOTE
l Upon first login, the Nastar system allows only user admin to set automatic access to eNodeBs. Before
setting automatic access to eNodeBs, contact the administrator to change user rights.
l After NEs are migrated to another OSS, the Nastar does not support the eNodeB automatic access
function.
l You can perform the following operation to enable or disable the NE automatic access function:
Modify the following configuration file: /opt/nastar/server/Galaxy/bundles/
com.huawei.galaxy.framework.neaccessmanager.impl/conf/
AutoAddNE.properties AUTOADDNE_PERIOD_SWITCH=0 (set the value to 0
if you want to enable the function, and set it to 1 if you want to
disable the function).
If the value is set to 0, Set Periodic Automatic NE Access, Set Immediate Automatic NE Access,
Export Doubtful Invalid eNodeBs, and Import deleted eNodeBs are displayed when you select an
LTE node and right-click it. If the value is set to 1, these items are not displayed.
Delete eNodeBs in batches.

1.
2.
Choose Export Doubtful Invalid eNodeBs from the shortcut menu to export the
information about doubtful NEs to be deleted from the specified eNdoeB group.
3.
Delete the information about valid eNodeBs from the exported results based on the
actual situation and keep only the information about eNodeBs to be deleted.
4.
5.
Choose Import deleted eNodeBs from the shortcut menu to import the invalid
eNodeB list file. In this way, invalid eNodeBs are deleted in batches.
NOTE
l Before importing the invalid eNodeB list file, you can use it to disable subscription to invalid
eNodeBs.
l If batch deletion fails, the system exports the list of NEs that fail to be deleted by default so that
users can view the failure cause and delete such NEs in batches again.
Issue 03 (2015-07-30)
View information about the collection and import of configuration data in the Log Info
area. Table 3-14 lists the parameters.
77
Nastar
Table 3-14 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.
Configuring LTE eNodeB Management Group (Optional)

This section describes how to added a newly accessed eNodeB to a specified eNodeB
management group. By doing this, the Nastar system can automatically set SAU for the eNodeB,
collect and import configuration data, set user rights for the eNodeB, and issue basic subscription
and application subscription tasks.
Prerequisites
l
You have completed LTE NE configurations. For detailed operations, see Selecting RAN
NEs Managed by an OSS.
You are authorized for LTE eNodeB management group operations.
Issue 03 (2015-07-30)

78
Nastar
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 Nastar system
will automatically perform the following operations:
l
Setting an SAU for the newly accessed eNodeB
Collect and import configuration data for the newly accessed eNodeB
Setting user rights for the eNodeB
The Nastar periodically scans newly access eNodeBs and automatically 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. If you add eNodeB(a) that belongs to group A to group B, the Nastar automatically
deletes eNodeB(a) from group A.
Procedure
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.
l Click
,
,
, or
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.
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
Issue 03 (2015-07-30)
Modify the NEs managed by the eNodeB management group.

79
Nastar
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.
View the automatic operation rights list of the eNodeB management group and NEs.
1.
2.
group and click Query Auto Operation List.
Delete the NEs managed by the eNodeB management group.

1.
2.
group and click Delete.
3.
In the displayed Confirm dialog box, click Yes.
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.
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.
Configure SAU information by physical RNC.
Perform theme analysis by logical RNC. The analysis results are also displayed by logical
RNC.
Procedure
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 3-10.
Issue 03 (2015-07-30)

80
Nastar
Figure 3-10 RNC In Pool tab page
----End
3.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.
Prerequisites
You have created an OSS system.
Procedure
OSS node.
Step 3 Click the PS Core NE List tab in the right pane, as shown in Figure 3-11.
Issue 03 (2015-07-30)

81
Nastar
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
icon to select an NE or multiple NEs at a time, or a double-arrow icon to select all NEs.
l In the RNC in Pool scenario, add NEs one by one; in other scenarios, hold down the Ctrl
key 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 3.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 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.
Issue 03 (2015-07-30)

82
Nastar
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 3.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 3.3.2 Preparations for OSS and NE Information Configuration.
Step 7 Click OK.
NOTE
On PS Core networks, after you click OK, the Nastar checks whether the license consumption of managed
NEs exceeds the license capacity. If yes, The number of subscribers attached to the USN reaches the
upper threshold of the license. The upgrade of the license is recommended. is displayed, and NEs
cannot be added. In such case, delete some NEs so that NEs can be properly added.
----End
Follow-up Procedure
l
NOTE
Refresh.
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.
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 03 (2015-07-30)
1.
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.
83
Nastar
5.
Select NEs you want to migrate.

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.
,
,
, or
to select NEs. You can click a
Click
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.
l
Click OK.
Modify NEs managed by an OSS system.

1.
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.
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.
Prerequisites
l
You have selected NEs.
You have obtained relevant Sign/User PS SAU information .
Before you set the IP address of LTE SAU, stop the subscription first.
Procedure
Issue 03 (2015-07-30)

84
Nastar
OSS node.
Step 3 Click the PS Core NE List tab in the right pane, as shown in Figure 3-12.
Step 4 Set the Sign/User 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 3-15 LTE SAU information
SAU
Parameter
Description
Sign/User PS SAU
SAU IP
IP address of the Sign/User

PS SAU server for SGSN/
MME or GGSN/SAE-GW.
SAU Port
Port number of the Sign/

User PS SAU server for
SGSN/MME or GGSN/
SAE-GW. The default port
number is 30030 and the
default SSL port number is
30130.
SSL Port
Issue 03 (2015-07-30)

85
Nastar
SAU
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 resubscribed 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
3.3.7 Setting the Vendor Type of EPCs (MMEs) (Optional)

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
Issue 03 (2015-07-30)

86
Nastar
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.
You have disabled all the basic subscription and application subscription of an LTE
network.
You have confirmed the vendor type of the EPCs (MMEs) to be accessed by the Nastar.
Only an account in the Administrators group can set the vendor type.
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 Huawei MMEs or Ericsson MME.
l Other vendor: indicates that the Nastar accesses other third-party MMEs except Huawei
MMEs and Ericsson MME.
l HUAWEI + Other vendor: indicates that the Nastar accesses Huawei, Ericsson MME and
other third-party MMEs at the same time.
l Non-interconnection: indicates that the Nastar does not access MMEs and obtains the
STMSI information from eNodeBs. It applies when the network optimization is based on the
STMSI rather than SIMSI.
NOTE
When EPC (MME) Vendor is set to Non-interconnection, the Nastar supports LTE complaint analysis
and cell performance analysis, but not LTE VIP analysis and LTE Terminal analysis.
Step 3 Click OK.

Step 4 Re-deliver the basic subscription and application subscription of an LTE network.
----End
3.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.
You have confirmed the HSSs serving involved eNodeBs.
You have obtained information about the OSS (U2000/M2000) that manages each HSS.
Issue 03 (2015-07-30)

87
Nastar
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 3.3.4 Configuring OSS Information.
Step 2 Add an HSS.
1.
Choose Maintenance > OSS Information Management.
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
3.3.9 Configuring the Anonymous Policy

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 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.
Issue 03 (2015-07-30)

88
Nastar
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.
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.
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.
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 > SingleOSS >
M2000-Common > iManager U2000-M at http://support.huawei.com.
----End
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.
You have configured OSS and NE information. For detailed operations, see 3.3.5
Configuring NE Information on the RAN Side.
Check that you have the operation rights to manage Anonymity Key Management.
Issue 03 (2015-07-30)

89
Nastar
Context
l
Only user admin or users in the administrators group have the rights to manage
Anonymity Key Management.
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.
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.
You need to reset the non-anonymization data analysis switch after you change or add OSS
and NE configuration.
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 ServiceSmartCare > Network Optimization
Service > GENEX Mobile Manager >
HMACUtil
Issue 03 (2015-07-30)

90
Nastar
Option
Description
The OSS anonymization switch is turned

off.
By default, the non-anonymization data

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 nonanonymized data analysis switch:
1. Choose Security > Anonymity Key
Management.
2. In the displayed Anonymity Key
Management window, click NonAnonymization 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 3-16 describes the State of the data anonymization switch:
Table 3-16 Switch status description
Issue 03 (2015-07-30)
Status
Description
ON
The data anonymization switch of the

U2000 is turned on.

91
Nastar
3.
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.
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 checks the data anonymization switch of the U2000 every 30 minutes. The update
time is the check end time. You can select Show all records to view all historical cipher key
information.
----End
3.4 Preparing Basic Data

This section describes how to collect basic data including configuration data, engineering
parameters, and map information before analyzing data.
3.4.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 3-17 describes basic data related to the Nastar.
Issue 03 (2015-07-30)

92
Nastar
Table 3-17 Basic data

Da
ta
Ty
pe
M
an
dat
or
y
or
Op
tio
nal
Description
Co
nfi
gur
ati
on
dat
a
Ma
nda
tor
y
Function: Configuration data contains the basic information for network

optimization, which is used for the Nastar to correctly retrieve data of each cell
from data sources.
En
gin
eer
ing
par
am
ete
rs
Op
tio
nal
Ma
p
file
s
Op
tio
nal
Acquisition means: The Nastar automatically retrieves the configuration data

from a specific path of the U2000/M2000 or OMC after users have configured
the OSS information on the Nastar.
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.
Function: Engineering parameters, which contain basic information for network
optimization such as the longitude and latitude of a site, antenna azimuth, and tilt
angle, help Nastar to achieve accurate geographic display.
Acquisition means: Contact the onsite administrator.
Data format: Engineering parameter files in .xls, .xlsx, or .csv format are
available.
Function: Electronic maps help Nastar to achieve accurate geographic display

for desired regions.
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 covert the map files in wor or tab format to those in sxwu format by using the
map conversion function provided by Nastar.
NE
gro
up
inf
or
ma
tio
n
Issue 03 (2015-07-30)
Op
tio
nal
Function: Users can group NEs to facilitate analysis on site. You must create NE
groups during LTE analysis (excluding complaint analysis) and can create NE
groups for other radio access technologies (RATs) as required.
Acquisition means: Users can create NE groups on their own needs or by
selecting NEs of specific regions in the GIS window.
Data format: NE group information files in .xls, .xlsx, or .csv format can be
imported and exported.

93
Nastar
Issue 03 (2015-07-30)
Da
ta
Ty
pe
M
an
dat
or
y
or
Op
tio
nal
Description
Ter
mi
nal
inf
or
ma
tio
n
Op
tio
nal
Function: The terminal information, such as the model, radio access technology
(RAT), and vendor, is used during terminal analysis.
Data format: Terminal information files in .xls, .xlsx, or .csv format can be
imported and exported.

94
Nastar
Da
ta
Ty
pe
M
an
dat
or
y
or
Op
tio
nal
Description
VI
P
inf
or
ma
tio
n
Op
tio
nal
Function: The VIP information, such as a

specific VIP and its IMSI, is used during
VIP analysis.
Co
mp
lai
nin
g
sub
scr
ibe
r
inf
or
ma
tio
n
Op
tio
nal
Acquisition means: Contact the onsite

administrator.
NOTE
Generally, you obtain the IMSI and
MSISDN of a VIP subscriber and enter
them into the Nastar.
Data format: VIP files in .csv format can

be imported and exported.
Function: The complaining subscriber
information, such as the complainer, its
IMSI/MSISDN, peer MSISDN of the
complainer, or time and location
information about the complaint, is used
during complaint analysis.
Acquisition means: Contact the onsite
administrator.
Data format: The IMSI, MSISDN, or peer
MSISDN in .xls, .xlsx, or .csv format can
be imported. You can also export existing
subscriber information to files
in .xls, .xlsx, or .csv format.
If telecom operators have high

requirements for subscriber
information security and the
anonymization policy is enabled on the
network where the Nastar is deployed,
all subscriber information such as
IMSI, MSISDN, and IMEI contained
in the analysis data will be encrypted.
To protect the security-sensitive
subscriber information, 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
Software Center > Tool > Mini-tool
Software > Core Network Product
Line > Wireless-OSS > iManager
M2000-II > HMACUtil to obtain the
tool to encrypt subscriber information.
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 3.12.3
Troubleshooting Problems Caused
by Change of the Subscriber Identity
Anonymization Switch or the
Encryption Key.
Issue 03 (2015-07-30)

95
Nastar
Da
ta
Ty
pe
M
an
dat
or
y
or
Op
tio
nal
Description
Ma
ilb
ox
inf
or
ma
tio
n
Op
tio
nal
Function: The mailbox information, such as the mailboxes of the sender and
recipient, is used during automatic analysis report sending. It is currently used
only for VIP analysis and the PS Core root cause analysis.
Kn
ow
led
ge
bas
es
Op
tio
nal

Data format: Address books in .xls, .xlsx, or .csv format can be imported and
exported.
Function: 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.
Acquisition means: The system already exists this information by default. If you
need to upgrade, contact the Huawei engineers.
Data format: Files in .xls, .xlsx, or .csv format can be imported and exported.
Issue 03 (2015-07-30)
Lo
cat
ion
par
am
ete
rs
Op
tio
nal
Da
ta
ser
vic
e
ser
ver
s
inf
or
ma
tio
n
Op
tio
nal
Function: You can minimize the distortion of geographic observation data by

properly setting parameters based on the areas on the sphere.
Acquisition means: 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. If you need to modify, set it.
Data format: None.
Function: The data service servers information is used during VIP analysis for
analyzing the servers.
Data format: Files in .xls, .xlsx, or .csv format can be imported and exported.

96
Nastar
Da
ta
Ty
pe
M
an
dat
or
y
or
Op
tio
nal
Description
Cu
sto
m
Da
ta
So
urc
e
Op
tio
nal
Function: The Custom Data Source provides cell information for PS Core
performance root cause analysis and enables the Nastar to display cell information
for TopN cell and procedure delay analysis.
Acquisition means: Contact the onsite administrator. If you need to modify, set
it.
Data format: Files in .xlsx format can be imported.
3.4.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.
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 hours. 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 collect
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.
Issue 03 (2015-07-30)
Importing: When detecting the configuration data, the system will import it to the database
automatically.
97
Nastar
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 unavailable.
NOTE
l When you query data about multiple eNodeBs, by default, detailed data about the first eNodeB is
displayed in the query results.
l Cell Name and eNodeB Name of deactivated cells are displayed.
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.
3.4.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.
Issue 03 (2015-07-30)

98
Nastar
Prerequisites
You have obtained the engineering parameter file, and the file format and engineering parameter
fields contained in the file meet the Nastar requirement.
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 10,000 records, this file cannot be imported.
Therefore, you are advised to convert an .xls file to the .csv format before importing it.
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.)
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.
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
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.
Issue 03 (2015-07-30)

99
Nastar
The column headers marked with the * character must be configured. Otherwise, the import
operation is not allowed.
l If you need to modify an incorrectly configured column header, right-click the column
header, clear the check box next to the original header, and then reconfigure the header.
l The engineering parameters must meet the following restrictions in different network
systems. For details, see Table 3-18. Otherwise, the engineering parameter file cannot be
imported into the database.
For details of the mandatory parameters and the range, see Appendix: Engineering
Table 3-18 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

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

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 import status and time by viewing the progress bar. If the progress bar is green, the
import is successful. If the progress bar is red, the import fails.
l During engineering parameter import, the Nastar checks the synchronization status of all NEs. If
synchronization fails for an NE, the Nastar displays a message, stating 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.
Issue 03 (2015-07-30)

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

correct
Click Close.
The imported engineering parameter data is

abnormal.
The data that fails to be imported is

highlighted in red. In this case, perform either
of the following operations:
l Click Export Failed Records.
The system exports the error records to a
file. You can modify error data and then
complete the import operation.
l Click Close to complete the import
operation.
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.
l
Set a file name and specify the save path and file type in the displayed Save dialog
box, and then click Save.
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 03 (2015-07-30)

101
Nastar
Prerequisites
l
Configuration data is imported. For details, see 3.4.2 Checking the Integrity of
Configuration Data.
Engineering parameter data is imported. For details, see Importing Engineering

Parameters.
Procedure
Step 1 Double-click System Function > Engineering Parameter Management from the navigation
tree in the Analysis Task Management window.
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
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 03 (2015-07-30)

102
Nastar
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 3-19 describes the parameters are updated.
Table 3-19 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.
For details about UMTS engineering parameters, see UMTS Engineering Parameters.
For details about LTE engineering parameters, see LTE Engineering Parameters.
GSM Engineering Parameters

Table 3-20 describes GSM engineering parameters supported by the Nastar.
Issue 03 (2015-07-30)

103
Nastar
Table 3-20 GSM engineering parameters

Parameter
Description
Value Range
Optional/
Mandatory
BSCName
Indicates the name of a

BSC.
l String
Mandatory

site.
l String

cell.
l String
Indicates the mobile

country code.
l Integer
Indicates the mobile

network code.
l Integer
Indicates the location

area code of a cell.
l Integer
Indicates the cell identity.
l Integer
SiteName
CellName
MCC
MNC
LAC
CI
l Value range:
[0,64]
Optional
l Value range:
[0,64]
Mandatory
l Value range:
[0,64]
Mandatory
l Value range:
[000,999]
Mandatory
l Value range:
[000,999]
Mandatory
l Value range:
[0,65535]
Mandatory
l Value range:
[0,65535]
Indicates the broadcast
control channel.
l Integer
Indicates the base station

color code.
l Integer
Indicates the network

color code.
l Integer
Longitude
Indicates the longitude

where a cell is located.
Value range:
[-180.000000,180.00
0000]
Mandatory
Latitude
Indicates the latitude

where a cell is located.
Value range:
[-90.000000,90.0000
00]
Mandatory
BCCH
BCC
NCC
Issue 03 (2015-07-30)
Mandatory
l Value range:
[0,1024]
Mandatory
l Value range: [0,7]

Mandatory
l Value range: [0,7]

104
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
Azimuth
Indicates the azimuth of

an antenna.
Value range:
[0.00,360.00]
Mandatory
Outdoor
Indicates whether a cell is

an outdoor cell.
l No: indoor cell
Optional
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.
used, ensure that the
values in this
column are not
empty.
Issue 03 (2015-07-30)

105
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
Sectorization

a directional cell.
l Omni:
omnidirectional
cell
Optional
l Sectorize:
directional 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.
not used, delete this
column.
used, ensure that the
values in this
column are not
empty.
TCH
Indicates the traffic

channel.
l Value range:
[0,255]
Optional
l TCH ARFCNs
must be separated
by semicolon.
AntHeight
MechTilt
ElecTilt
AntVendor
Issue 03 (2015-07-30)
Indicates the antenna

height.
l Integer

mechanical tilt.
l Integer

electrical tilt.
l Integer

vendor.
l String
Optional
l Value range:
[0,65535]
Optional
l Value range:
[-90.0,90.0]
Optional
l Value range:
[-90.0,90.0]
Optional
l Value range:
[0,32]

106
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
AntType

type.
l String
Optional
Indicates the site type.
l String
SiteType
l Value range:
[0,32]
Optional
l Value range:
[0,32]
PrimaryAnt
Indicates whether an
antenna is the main
antenna.
l No: diversity
antenna
Optional
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.
Click GSM Engineering Parameter Template and obtain the GSM engineering parameter
template in .csv format.
UMTS Engineering Parameters

Table 3-21 describes UMTS engineering parameters supported by the Nastar.
Table 3-21 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 03 (2015-07-30)

107
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
NodeBID
Indicates the ID of a NodeB.
l Integer
Mandatory
l Value range:
[0,65535]
NodeBName
CellID

NodeB.
l String
Indicates the ID of a cell.
l Integer
Mandatory
l Value range:
[0,64]
Mandatory
l Value range:
[0,65535]
CellName
Indicates the name of a cell.
l String
Mandatory
l Value range:
[0,64]
Indicates the location area
code of a cell.
l Integer
Indicates the routing area code

of a cell.
l Integer
UARFCNDo
wnlink
Indicates the downlink

UARFCN of a cell.
l Integer
UARFCNUpl
ink
Indicates the uplink UARFCN

of a cell.
l Integer
PSC
Indicates the primary

scrambling code of a cell.
l Integer
Longitude
Indicates the longitude where

a cell is located.
Value range:
[-180.000000,180.0
00000]
Mandatory
Latitude
Indicates the latitude where a

cell is located.
Value range:
[-90.000000,90.000
000]
Mandatory
Azimuth
Indicates the azimuth of an

antenna.
Value range:
[0,360]
Mandatory
LAC
RAC
Issue 03 (2015-07-30)
Optional
l Value range:
[0,65535]
Optional
l Value range:
[0,65535]
Mandatory
l Value range:
[0,65535]
Optional
l Value range:
[0,65535]
Mandatory
l Value range:
[0,511]

108
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
Outdoor
Indicates whether a cell is an

outdoor cell.
l No: indoor cell
Optional
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 03 (2015-07-30)

109
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
Sectorization
Indicates whether a cell is a

directional cell.
l Omni:
omnidirectional
cell
Optional
l Sectorize:
directional 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.
SAC
AntHeight
Indicates the service area code

of a cell.
l Integer
Indicates the antenna height.
l Integer
Optional
l Value range:
[0,65535]
Optional
l Value range:
[0,65535]
MechTilt
ElecTilt
AntType

mechanical tilt.
l Integer

electrical tilt.
l Integer
Indicates the antenna type.
l String
Optional
l Value range:
[-90.0,90.0]
Optional
l Value range:
[-90.0,90.0]
Optional
l Value range:
[0,32]
Issue 03 (2015-07-30)

110
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
AntVendor
Indicates the antenna vendor.
l String
Optional
l Value range:
[0,32]
SiteType
l String
Optional
l Value range:
[0,32]
Click UMTS Engineering Parameter Template and obtain the UMTS engineering parameter
template in .csv format.
LTE Engineering Parameters

Table 3-22 describes LTE engineering parameters supported by the Nastar.
Table 3-22 LTE engineering parameters
Parameter
Description
Value Range
Optional/
Mandatory
eNodeBName
Indicates the name of an

eNodeB.
l String
Mandatory
Indicates the name of a site.
l String
SiteName
l Value range:
[0,64]
Optional
l Value range:
[0,64]
CellName
Indicates the name of a cell.
l String
Mandatory
l Value range:
[0,64]
eNodeBID
SectorID
Indicates the ID of an
eNodeB.
l Integer
Indicates the ID of a sector.
l Integer
Mandatory
l Value range:
[0,1048575]
Optional
l Value range:
[0,65535]
LocalCellID
Indicates the ID of a local cell.
l Integer
Optional
l Value range:
[0,255]
Issue 03 (2015-07-30)

111
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
CellID
Indicates the ID of a cell.
l Integer
Mandatory
l Value range:
[0,65535]
Indicates the ID of a physical
cell.
l Integer
Indicates the tracking area

code of a cell.
l Integer
Longitude
Indicates the longitude where

a cell is located.
Value range:
[-180.000000,180.0
00000]
Mandatory
Latitude
Indicates the latitude where a

cell is located.
Value range:
[-90.000000,90.000
000]
Mandatory
Azimuth
Indicates the azimuth of an

antenna.
Value range:
[0,360]
Mandatory
AntHeight
Indicates the antenna height.
l Integer
Optional
PhyCellID
TAC
Mandatory
l Value range:
[0,503]
Optional
l Value range:
[0,65535]
l Value range:
[0,65535]
MechTilt
ElecTilt
AntVendor

mechanical tilt.
l Integer

electrical tilt.
l Integer
Indicates the antenna vendor.
l String
Optional
l Value range:
[-90.0,90.0]
Optional
l Value range:
[-90.0,90.0]
Optional
l Value range:
[0,32]
AntType
Indicates the antenna type.
l String
Optional
l Value range:
[0,32]
Issue 03 (2015-07-30)

112
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
Outdoor
Indicates whether a cell is an

outdoor cell.
l No: indoor cell
Optional
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
DLEARFCN
OnAir
SiteType
Indicates the uplink ARFCN

of the UTRAN.
l Integer
Indicates the downlink

ARFCN of the UTRAN.
l Integer

enabled.
l String
l String
Optional
l Value range:
[0,65535]
Mandatory
l Value range:
[0,65535]
Optional
l Value range:
YES, NO.
Optional
l Value range:
[0,32]
Issue 03 (2015-07-30)

113
Nastar
Parameter
Description
Value Range
Optional/
Mandatory
Sectorization
Indicates whether a cell is a

directional cell.
l Omni:
omnidirectional
cell
Optional
l Sectorize:
directional 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.
Click LTE Engineering Parameter Template and obtain the LTE engineering parameter template
in .csv format.
3.4.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 3-13.
Issue 03 (2015-07-30)

114
Nastar
Figure 3-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.
You have downloaded Google Earth from website http://www.google.com/ and installed
it on the PC.
Context
The principles for displaying the Nastar data on the Google Earth are as follows:
l
After the engineering parameters are read, the geographic data is displayed on the scale of
2,600 meters at heights and with the last cell in the engineering parameter list being in the
center by default.
The Nastar data can be displayed on the Google Earth synchronously. The geographic data
is displayed on the scale of 2,600 meters at heights with the selected cell being in the center.
NOTICE
l
The description of operations related to the Google Earth is not provided in this document.
You must follow the terms and conditions of Google Maps when performing GIS analysis.
l For details about the terms of use, see Google Maps/Earth Additional Terms of
Service.
l For details about the purchase agreement, see Google Maps API for Business Purchase Agreement.
Issue 03 (2015-07-30)

115
Nastar
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.
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
home page of the Google Earth
It indicates that the system fails to

automatically read the Nastar engineering
parameters.
This problem may be caused by the low
speed of loading the Google Earth
components. In this case, you need to
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.
Issue 03 (2015-07-30)

116
Nastar
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.
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
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.
l Before importing a SXWU map file, you must verify that the SXWU map file exists in the directory for
saving map files. If such a file does not exist, the import fails.
Issue 03 (2015-07-30)

117
Nastar
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.
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
3.4.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 3.3
Configuring OSS and NE Information.
Context
l
The system supports a maximum of 100 NE groups.
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 3-23. The sequence for matching each column must be the
same as that in the following example.
Issue 03 (2015-07-30)

118
Nastar
Table 3-23 Examples of NE group files

NE
Grou
p
Nam
e
BSC
Nam
e
Cell
Nam
e
LAC
CI
Creator
Creatio
n Time
Note
Group
1
12121
21212
2014010
1
NA
Group
2
21212
12121
2014010
1
NA
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.
NOTE
Cell Name and eNodeB Name of deactivated cells are not displayed.
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 3-24 describes the parameter settings.
Issue 03 (2015-07-30)

119
Nastar
Table 3-24 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.
4.
l
Click OK.
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.
l
Click OK.
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.
Issue 03 (2015-07-30)

120
Nastar
No.
Procedure
Step
Opening
the map
window
On the toolbar of the main window, click

Observation window is displayed.
Drawing a
polygon to
define the
area to be
filtered
1. Click
. The Geographic
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.
l At least one cell must be contained in the polygon. Otherwise, the
polygon is not displayed in the Polygon Areas in the navigation
tree.
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
Issue 03 (2015-07-30)
Setting
filtering
criteria to
filter the
cells in the
defined
area and
with the
specified
network
system and
engineerin
g parameter
fields
1. Click
on the toolbar. The Cell Group Definition dialog
box is displayed.
2. Select a value for Network System.
3. Select a matched area in the Polygon Areas.

121
Nastar
No.
Procedure
Step
Saving the
filtered
cells as an
NE group
1. Click Save As NE Group. The Save As NE group dialog box

is displayed.
2. Set NE Group Name and add remarks.
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
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

the property of an NE group
1. Click Modify/View.
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 3-24.
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.
Issue 03 (2015-07-30)

122
Nastar
If...
Then...
You need to delete an NE

group
1. Click Delete.
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

Group
1. Click Export.
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.
3.4.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 3-14 shows the relationship between VIP groups and VIP users.
Issue 03 (2015-07-30)

123
Nastar
Figure 3-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.
A VIP group can be configured with multiple VIP users. A VIP user can be configured in
multiple VIP groups.
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.
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 3-25 describes the technical specifications of the VIP group and the VIP user.
Issue 03 (2015-07-30)

124
Nastar
Table 3-25 Technical specifications for VIP group management 1

Item
Task Management Capacity
Number of allowed VIP

groups
<= 1,000
Number of allowed VIP

subscribers
<= 30,000
Number of VIP groups to

which one VIP subscriber
can belong
<= 30
where the number of important VIP subscribers is less than or

equal to 500.
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 3-26.
Table 3-26 Technical specifications for VIP group management 2
Network
Type
Earliest NE Version
Supported
Number of Important VIP Subscribers

That Support Signaling Tracing Analysis
GSM
l CS domain: GBSS11.0
(BSC6900
V900R011C00)
<= 500/BSC
l PS domain: GBSS14.0
(BSC6900
V900R014C00)
UMTS
Issue 03 (2015-07-30)
RAN13.0 (BSC6900
V900R013C00)
<= 100/RNC
RAN16.0 (BSC6900
V900R016C00)
<= 500/RNC
LTE
eRAN6.0 (LTE3900
V100R008C00)
<= 500/HSS
Multi-RAT
networks
<= 500/NE

125
Nastar
Managing VIP Groups

This section describes how to group multiple VIP subscribers into a VIP group for guarantee
management. You need to create VIP groups and then add VIP subscribers to the VIP groups.
A VIP group contains at least one VIP subscriber.
Prerequisites
For details about how to configure management permissions of VIP groups, see Operation and
Maintenance > Nastar Operation Right References in the product documentation.
Context
You can create a VIP group using either of the following methods:
l
Create a VIP group directly
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
3-27. The column sequence must be the same as that in the following example, which is
the same as that on the Nastar.
Table 3-27 Sample VIP group file
No.
Group Name
Number of
Members
Description
Group 1
50
Secondary department
director of ** Group
Group 2
100
Project manager of ** Group
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.
Issue 03 (2015-07-30)

126
Nastar
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 3-27.
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 subscribers 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 subscribers from the existing VIP subscriber list, and click
OK.
If the required VIP subscriber is unavailable in the existing VIP subscriber list, click
New or Import to create a VIP subscriber. For detailed parameter descriptions, see
Managing VIP Subscribers.
4.
Click OK.
----End
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.
Issue 03 (2015-07-30)

127
Nastar
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 subscriber to the
VIP group.
l Click New to create a VIP subscriber and then add
it to the VIP group.
l Click Delete to delete a VIP subscriber that has been
added to the VIP group.
NOTICE
l Issue the subscription task for related GSM and UMTS
themes again after VIP subscribers in a VIP group are
updated so that the VIP subscription function is not
affected.
l If you attempt to delete a VIP subscriber 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 subscriber can be analyzed only after the VIP
subscriber is grouped into VIP groups. Therefore, if the
VIP subscriber you want to delete belongs only to the
current VIP group, you will not be allowed to delete the
VIP subscriber.
l For LTE, after class of VIP subscribers in the VIP group
are modified, VIP subscription needs to be issued again
because the VIP group is changed. Are you sure you
want to allow the Nastar to automatically issue VIP
subscription? is displayed. If you click Yes, the Nastar
automatically issues VIP subscription for related LTE
themes.
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 subscriber belongs only to the current VIP group
cannot be deleted.
View a VIP group
Issue 03 (2015-07-30)
Double-click a VIP group to view the detailed

information.

128
Nastar
If you need to...
Then...
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
For details about how to configure management permissions of VIP groups, see Operation
and Maintenance > Nastar Operation Right References in the product documentation.
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.
You have obtained VIP subscriber information, including the MSISDN, IMSI, and
subscriber class.
NOTE
Generally, you obtain the IMSI and MSISDN of a VIP subscriber and enter them into the Nastar.
If telecom operators have high requirements for subscriber information security and the anonymization
policy is enabled on the network where the Nastar is deployed, all subscriber information such as IMSI,
MSISDN, and IMEI contained in the analysis data will be encrypted. To protect the security-sensitive
subscriber information, 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 Software Center > Tool > Mini-tool Software > Core Network
Product Line > Wireless-OSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt
subscriber information.
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 3.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.
Create VIP subscribers by importing a file. The Nastar allows you to import and export
VIP subscriber files in CSV, XLS, or XLSX format.
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.
Issue 03 (2015-07-30)

129
Nastar
The VIP subscriber file you want to import must include the following fields as shown in
Table 3-28. The column sequence must be the same as that in the following example, which
is the same as that on the Nastar.
Table 3-28 Sample VIP subscriber file
No.
Alia
s
Phone
Numbe
r
CC
IMSI
Class
VIP
Group
Descri
ption
a1
135****
****
86
123*******
**124
Importan
t
A,B
User a
b2
130****
****
86
123*******
**125
Commo
n
User b
c3
131****
****
86
123*******
**126
Commo
n
A,B,C
User c
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 User tab.

Step 3 Create VIP subscribers and add them to VIP groups.
If you need to...
Then...
Create a VIP subscriber directly
1. Click New. The Create VIP User dialog box

is displayed.
2. Set VIP subscriber information.
If the asterisk (*) is present on the right of a
parameter, the setting of this parameter is
mandatory. Table 3-29 lists the detailed
parameter descriptions.
3. Click OK.
The new VIP subscriber is displayed on the
VIP User tab page.
Issue 03 (2015-07-30)

130
Nastar
If you need to...
Then...
Create VIP subscribers by importing a

file
1. Click Import. The Open dialog box is

displayed.
2. Select a VIP subscriber file.
The Nastar allows you to import and export
VIP subscriber files in CSV, XLS, or XLSX
format. For details about the requirements for
a VIP subscriber file, see Table 3-28.
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 subscribers are displayed
on the VIP User tab page.
Table 3-29 VIP subscriber information parameters

Parameter
Description
Alias
Name alias of a VIP subscriber, which is not the real name of the subscriber.
Function: The VIP subscriber alias, together with the subscriber ID
automatically allocated by the system in the VIP analysis results, uniquely
identify a subscriber.
Value range:
l The name contains a maximum of 8 digits.
l Only digits allowed.
l The name must not be empty.
l The name can be duplicate. Therefore, one subscriber can have multiple
MSISDNs.
Issue 03 (2015-07-30)

131
Nastar
Parameter
Description
IMSI
IMSI of a VIP subscriber.

Function:
l The system can collect the analysis data from the network through the
IMSI information.
l You can perform RAN VIP analysis and combined RAN and PS Core
VIP analysis based only on IMSIs. However, you can perform PS Core
VIP analysis based on MSISDNs (default) or IMSIs.
Value range:
l When the anonymization 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 anonymization 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 and A-F.
l The IMSI must be unique and maps the MSISDN. One MSISDN maps
only one IMSI.
l PS Core VIP analysis can be performed based only on MSISDNs instead
of IMSIs, and therefore you do not need to set IMSIs. Select Do not set
IMSI (only for PS Core), and each IMSI will be displayed as all Fs.
Issue 03 (2015-07-30)

132
Nastar
Parameter
Description
MSISDN
Mobile phone number of a VIP subscriber, which consists of the country

code and national mobile number.
Function:
l In the VIP group management function, it facilities the maintenance of
VIP information.
l PS Core VIP analysis can be performed based on MSISDNs (default)
or IMSIs.
Value range:
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.
l The MSISDN must be unique and maps the IMSI. One IMSI maps only
one MSISDN.
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 allsignaling 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 03 (2015-07-30)

133
Nastar
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
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.
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

subscriber
On the VIP User tab page, right-click the VIP subscriber list and
choose Search from the shortcut menu. Enter a keyword to quickly
find a VIP subscriber.
Modify a VIP
subscriber
1. Select a VIP subscriber, and click Modify/View. The Modify/

View VIP User window is displayed.
2. Set one or multiple fields among User Name, Phone Number,
CC, Class, Description, and VIP Group.
NOTE
l The IMSI of a VIP subscriber cannot be modified.
l The level of a VIP subscriber for whom subscription is enabled
cannot be modified.
3. Click OK.
Add or delete the VIP
group to which a VIP
subscriber belongs
1. Click Modify/View.
2. In the Modify/View VIP User dialog box, click the buttons to
add or delete the VIP group where a VIP subscriber belongs.
NOTE
l If subscription operation has been performed on the VIP group that you
are deleting, the system will display a message, indicating that the VIP
group cannot be deleted until you cancel the subscription operation.
l For LTE, after the VIP group to which a VIP subscriber belongs is added
or deleted, VIP subscription needs to be issued again because the VIP
group is changed. Are you sure you want to allow the Nastar to
automatically issue VIP subscription? is displayed. If you click Yes,
the Nastar automatically issues VIP subscription for related LTE themes.
Issue 03 (2015-07-30)

134
Nastar
If you need to...
Then...
Import VIP
subscribers
Click Import.
Export VIP
subscribers
Click Export.
Delete VIP
subscribers
1. Select a VIP subscriber record or press Ctrl to select multiple

VIP subscriber records and click Delete.
If a selected XLS or XLSX file contains multiple sheets, the system

displays information prompting you to select the sheet to be
imported.
The Nastar allows you to import and export VIP subscriber files in
CSV, XLS, or XLSX format.

NOTE
The VIP subscriber for whom subscription is enabled cannot be deleted.
Save VIP subscribers
On the VIP User tab page, right-click the VIP subscriber list and
choose Save As from the shortcut menu.
3.4.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.
You have obtained the terminal information.
The system supports a maximum number of terminal types: 100,000.
You can create a terminal type using either of the following methods:
Context
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
3-30.
Issue 03 (2015-07-30)

135
Nastar
Table 3-30 Sample terminal type file
IMEITAC
Vendo
r
Termi
nal
Model
Chip
Model
Termi
nal
Type
Data
Transf
er
Termi
nal
Techn
ology
Suppo
rt WiFi
123XX
XXX
Huawei
U8800
msm72
30
Cell
phone
GPRS/
EDGE/
HSDPA
WCDM
A
Support
123XX
XXX
Huawei
U8660
msm76
27
Cell
phone
GPRS/
EDGE/
HSDPA
WCDM
A
Support
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.
NOTE
l To prevent Huawei asset information from disclosure, use AES-128 to encrypt exported files
for the terminal type library maintained for Huawei PS Core. 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.
l .tac file is encrypted terminal types, import the type library for terminal export, the export
file will be empty.
Table 3-31 shows a sample terminal attribute file.

Table 3-31 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 03 (2015-07-30)

136
Nastar
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 3-32.

If the asterisk (*) is present on the right of a parameter, the setting of this parameter is
mandatory.
Table 3-32 Terminal type parameters
Parameter
Description
Optional/
Mandatory
IMEI-TAC
Indicates the first eight digits of the International Mobile

Equipment Identity (IMEI) that identifies the type of a
terminal.
Mandatory
Vendor
Indicates the vendor of a terminal.
Mandatory
Terminal
Model
Indicates the model of a terminal.
Mandatory
Chip Model
Indicates the chip model.
Optional
Terminal
Technology
Indicates the technology the terminal supports. The

default technologies include GSM, WCDMA, TDSCDMA, GSM/WCDMA, GSM/TD-SCDMA, and
LTE.
Optional
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 03 (2015-07-30)

137
Nastar
Parameter
Description
Optional/
Mandatory
Data
Transfer
Indicates the PS transfer mode the terminal supports.

The default PS transmission modes include GPRS/
EDGE, GPRS/EDGE/HSDPA, and GPRS/EDGE/
HSPA.
Optional

Terminal
Type
Indicates the type of a terminal. The default terminal

types include Feature Phone, Smartphone, Data
Card, Wireless Landline, Family Gateway.
Optional

Support WiFi
3.
Indicates that whether the terminal supports Wi-Fi.
Optional
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 03 (2015-07-30)

138
Nastar
If you need to...
Then...
Define a terminal attribute l Create a terminal attribute directly.

1. In the Terminal Type Management window, rightclick 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, rightclick 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
terminal attribute
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. 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
attribute and its
value
Only user-defined terminal attributes can be modified.

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. 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 03 (2015-07-30)

139
Nastar
If you need to...
Then...
Delete a terminal
attribute and its
value
Only user-defined terminal attributes can be deleted.

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
attribute and its
value

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
type information
1. In the Terminal Type Management window, select a terminal type,

and click Modify/View. The Terminal Type ManagementModify/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
types
1. In the Terminal Type Management window, select one or multiple

terminal types, and click Delete.
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

information
1. In the Terminal Type Management window, set the filter condition

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 03 (2015-07-30)

140
Nastar
If you need to...
Then...
Export the
terminal type
information and
save the
information in
a .csv, .xls, or .xlsx
file
1. In the Terminal Type Management window, select one or multiple

terminal types, and click Export.
2. Set the file name and specify the save path and file type. Then, click
Save.
3.4.8 Managing Information About Data Service Servers (PS

Service)
This section describes how to configure the information about data service servers, such as the
IP address and port number. You can analyze servers for PS services, such as obtaining the TopN
servers with the highest traffic.
Prerequisites
l
You are authorized to manage the information about data service servers.
You have obtained the information about a data service server, including the IP address
and port number.
Context
A maximum of 50000 servers can be managed.
Use either of the folloiwng methods to configure the information about a data service server:
l
Directly configure the information about a data service server.
Configure the information about a data service server by importing files. You can import
and export data service server files in .csv, .xls, and .xlsx formats.
A data service server file to be imported must contain the following fields: Server IP,
Server Name, Port, Service Name, and Remark, as shown in Table 3-33. The column
sequence must be the same as that in the following example.
Table 3-33 Example of a data service server file
Issue 03 (2015-07-30)
Server IP
Server
Name
Port
Service
Name
Remark
10.25.75.13
3
Huawei A
Service
21
FTP service
10.33.64.11
0
Huawei B
Service
443
HTTPS service

141
Nastar
Procedure
Step 1 Double-click System Function > Data Service Server Management in the navigation tree of
the Analysis Task Management window.
NOTE
You can also choose System Function > Data Service Server Management from the navigation tree of
the Analysis Task Management window and right-click Open. The Data Service Server
Step 2 Configure the information about a data service server.

If You Need to...
Then...
Directly configure the

information about a data
service server.
1. Click New. The New Data Service Server dialog box is

displayed.
2. Set Server IP, Server Name, Port, Service Name, and
Remark. Table 3-34 lists parameter settings.
If the asterisk (*) is present on the right of a parameter, the
setting of this parameter is mandatory.
3. Click OK.
The configured information about a data service server is
displayed in the Data Service Server Management
window.
Configure the information 1. Click Import. The Open dialog box is displayed.
about a data service server 2. Select a data service server file.
by importing files.
You can import and export data service server files
in .csv, .xls, and .xlsx formats. Table 3-33 lists the
requirements for data service server files.
3. Click Open.
If a file contains multiple worksheets, a dialog box is
displayed for you to select the worksheet to be imported.
The imported information about a data service server is
displayed in the Data Service Server Management
window.
Table 3-34 Settings of data service server parameters

Parameter
Description
Server IP
IP address of a data service server. For example, 10.25.75.133. A maximum

of 15 characters are allowed.
Server Name
Name of a data service server. A maximum of 64 characters are allowed.

NOTE
In analysis object selection area on the left of the window that displays the active
server analysis results for GSM VIP analysis, no information is displayed following
the colon for the IP address of the selected Server object if this parameter is not set.
Issue 03 (2015-07-30)

142
Nastar
Parameter
Description
Port
Port number of a data service server for a service. The value ranges from
0 to 65534.
Service Name
Name of a service running on a data service server. A maximum of 64

characters are allowed.
Remark
Description of a data service server.
----End
Follow-up Procedure
In the Data Service Server Management window, select a data service server record and
perform related operations as required.
If You Need to ...
Then...
Search for a data service server.
In the Data Service Server Management window,

press Ctrl+F. In the displayed Search dialog box, enter
keywords to quickly locate the data service server.
Modify the information about a data

service server.
Click Modify/View to re-set the parameters of a data

service server.
Export the information about a data

service server.
Click Export.
Delete the information about a data

service server.
Click Delete.
View the information about a data

service server.
Click Modify/View to view the parameters of a data

service server.
3.4.9 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
Issue 03 (2015-07-30)
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.
143
Nastar
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.
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 3-35.
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.
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
3-35.
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.
Issue 03 (2015-07-30)

144
Nastar
Table 3-35 Parameters recorded in the knowledge bases

Parameter
Description
Optional/
Mandatory
Cause
Hexadecimal value, which is the unique identifier of a

record.
Mandatory
l Cause value range for SGSN/MME: 0x0 to 0xFFFF

l Cause value range for GGSN/SAE-GW: 0x0 to
0xFFFFFFFF
Failure cause
description
Description of a failure cause.
Mandatory
Solution
Solutions to failures. You can solve problems by

referring to this description.
Mandatory
Note
Remarks. Knowledge bases apply to any NE versions.

If there are differences between failure cause
description and solutions, you are advised to add
remarks.
Optional
----End
Follow-up Procedure
If you need to...
Then...
Delete a record
Select one or more records and click Delete.
Export records in
batches
Click Export and set the name of the file you want to import. The
Nastar then exports all existing records.
Restore default
settings
Click Resume. The Nastar restores the default knowledge base

information during initial Nastar installation.
3.4.10 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.
You have obtained the addressee information.
Issue 03 (2015-07-30)

145
Nastar
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.
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 3-36. The match sequence of
columns is specified and automatic matching of columns is not supported.
Table 3-36 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 (.).
Procedure
l
Do as follows to set the mailbox for sending analysis reports:

1.
Log into the Nastar client.
2.
Choose Maintenance > Email Settings. The Email Settings window is displayed.
3.
Set the parameters for the mailbox in Table 3-37.

Table 3-37 Parameters for setting the mailbox for sending analysis reports
Parameter
Description
SMTP Host Name or

Address
Address of the sending email server.
Send Email Address
Issue 03 (2015-07-30)
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.
Email address of the sender.

146
Nastar
Parameter
Description
Max attachment size

(MB)
Maximum size of the files attached to the email.

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.
You can use Space bar to select Is it required to
authenticate.
4.
l
User Name
User name used to log in to the email sending server.
Password
Password used to log in to the email sending server.
Click OK.
Do as follows to set the address list for sending analysis reports:

1.
Choose Maintenance > Auto-Distribution User Management. The AutoDistribution User Management window is displayed.
2.
Click New. The New User window is displayed.

You can click Import to add users.
3.
Set the parameters for the mailbox in Table 3-38.

Table 3-38 Parameter for setting the addressee
4.
Parameter
Description
User Name
User name of the addressee.
Email
Email address of the addressee.
Remarks
Description of the User to be sent.
Click OK.
----End
Issue 03 (2015-07-30)

147
Nastar
3.4.11 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).
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.
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 3-39.
Issue 03 (2015-07-30)

148
Nastar
Table 3-39 Historical origin parameters

Parameter
Description
No.
Number of the historical origin.
Delivered On
Time when the origin was delivered.
Origin
Delivery Mode
Mode for delivering the origin, including:

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
Follow-up Procedure
View logs in the Log Info area. For detailed log parameters, see Table 3-40.
Issue 03 (2015-07-30)
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.

149
Nastar
Set Function, Severity, and Condition, enter keywords, and then click Filter to filter out
desired logs.
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.
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.
3.4.12 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.
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 3-15 PS Core Cell Information Management Interface
1: Window that displays cell information in a list
Issue 03 (2015-07-30)

2: Button area
150
Nastar
Table 3-41 Interface functions
Issue 03 (2015-07-30)
No.
Item
Description
(1)
Window that displays cell

information in a list
Displays information about

all cells in a list.

151
Nastar
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.
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.
XLSX format.
For details about parameter
definition specifications, see
Specifications of data
source parameters for cell
information management.
Issue 03 (2015-07-30)

152
Nastar
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.
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 3-42 Specifications of data source parameters for cell information management
Parameter
Value Range
Description
Mandatory or
Optional
MCC
[000,999]
Country code of a
specified mobile
subscriber
Mandatory
Network code of the

public land mobile
network (PLMN) to
which a specified
mobile subscriber
belongs
Mandatory
NOTE
Each MCC is
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.
MNC
[000,999]
NOTE
Each MNC is
centrally processed
into a 3-digit
number on the CN.
During cell
information import
or creation, 0s are
added at the
beginning of an
MNC if the length
of the MNC is less
than 3.
Issue 03 (2015-07-30)
LAC
[0X0,0XFFFF]
Location area code of

a specified cell
Mandatory
CI
[0X0,0XFFFF]
Identity of a specified
cell
Mandatory (the value

of this parameter is set
to SAC on a UMTS
network)
Description
200 characters
Descriptive
information of a
specified cell
Optional

153
Nastar
NOTE
Each RAT supports a maximum of 100,000 cells.
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
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.
3.5 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.
3.5.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.
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 Appendix: List of Data Subscription Function of All the Analysis
Function.
Issue 03 (2015-07-30)

154
Nastar
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.
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 3-16 shows the application scenarios for the two roles to use the analysis data subscription
function.
Figure 3-16 Application scenarios of the data subscription function
Issue 03 (2015-07-30)

155
Nastar
Table 3-43 Scenario description of the data subscription function

User
Applica
tion
Scenari
o
Description
Example
Admin
istrator
Initial
configura
tion
If the administrator uses the

Nastar for the first time, the
administrator needs to collect
information about the NEs on the
managed network and the Nastar
functions to be used. Then, the
administrator turns on the data
switches of NEs for each analysis
theme in batches.
Managed network: networks A

and B.
The administrator can obtain

information for routine
maintenance in the following
ways:
Routine
maintena
nce
Involved theme: VIP analysis.

The administrator selects all the
cells on networks A and B, and
sets the data switch status of all
cells for the VIP analysis to ON in
batches by using the basic
subscription function. The
administrator can also set the VIP
objects and NE objects by using
the application subscription
function.
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 03 (2015-07-30)

156
Nastar
User
Applica
tion
Scenari
o
Description
Example
Comm
on
users
Routine
Query
Before creating an analysis task, a

common user needs to check
whether the data subscription
status on the live network meets
analysis requirements. If the data
subscription status does not meet
analysis requirements, the
common user needs to submit an
application to the administrator
for turning on certain switches.
A common user in network A

finds that the data switch of cell a
for the VIP analysis is in the
OFF state, which does not meet
analysis requirements. Therefore,
the common user submits an
application to the administrator
for turning on this switch.
After receiving the application,
the administrator sets the data
switch status of cell a for the VIP
analysis to ON.
3.5.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.
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 3.3 Configuring OSS and NE
Information.
Configuration data has been imported. For details, see 3.4.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 03 (2015-07-30)

157
Nastar
NOTE
l If the NE information (such as NE FDN) changes, the Nastar cannot automatically issue basic
subscription commands. In such case, users need to manually issue basic subscription commands.
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
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.
Issue 03 (2015-07-30)
Click Import under the NE tree and select an Excel file.

158
Nastar
Figure 3-17 Example of Excel file
NOTE
The Excel file must contain columns eNodeBID and eNodeBName, and eNodeBID is the first
column, eNodeBID and eNodeBName must be completed correctly, otherwise the system will
display an error message.
2.
View the subscription status of imported NEs in Table 3-44.

Table 3-44 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.
Issue 03 (2015-07-30)

159
Nastar
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.
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.
: 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.
: 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.
NOTE
On PS Core networks, after you click Confirm, the Nastar checks whether the license consumption of
managed NEs exceeds the license capacity. If yes, The number of subscribers attached to the USN
reaches the upper threshold of the license. The upgrade of the license is recommended. is displayed,
and subscription cannot be enabled. In such case, disable subscription for certain themes so that subscription
can be enabled.
----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.
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 3-45 describes the switch status of various data source switches.
Issue 03 (2015-07-30)

160
Nastar
NOTE
For the LTE network, the eNodeB switch status is refreshed on the Nastar by the basic subscription.
If Unknown is displayed after the refresh, view the eNodeB information in the Log Info area.
Table 3-45 Data switch status

Icon
Issue 03 (2015-07-30)
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

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.

161
Nastar
Icon
Status
Description
Unknown

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.
View information about the subscription in the Log Info area. Table 3-46 lists the
parameters.
Issue 03 (2015-07-30)
Parameter
Description
Date/Time

162
Nastar
Parameter
Description
Level
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.
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.
3.5.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.
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 3.3 Configuring OSS and NE
Information.
You have imported the configuration data. For detailed operations, see 3.4.2 Checking the
Integrity of Configuration Data.
You have performed basic subscription of analysis data. For detailed operations, see 3.5.2
Basic Subscription of Analysis Data.
You have created a VIP group before subscribing to VIP analysis data. For detailed
operations, see Managing VIP Groups.
You have imported the engineering parameters before subscribing to network geographic
observation data. For detailed operations, see Importing Engineering Parameters.
Issue 03 (2015-07-30)

163
Nastar
Context
NOTE
If the NE information (such as NE FDN) changes, the Nastar cannot automatically issue application
subscription commands. In such case, users need to manually issue application subscription commands.
Application subscription is not required for certain analysis themes. To learn the data you must
subscribe to for the analysis themes, see Appendix: List of Data Subscription Function of All
the Analysis Function.
Procedure Diagram
NOTE
On GSM/UMTS/LTE TDD/LTE FDD networks, Refresh is unavailable when you attempt to subscribe
to the VIP analysis at the Group level.
On GSM/UMTS networks, Refresh is unavailable when you attempt to subscribe to the VIP analysis at
the User level.
Procedure
Step 1 Choose Maintenance > Data Subscription Management. The Data Subscription
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.
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
Issue 03 (2015-07-30)

164
Nastar
1.
Click Import under the NE tree and select an Excel file.

Figure 3-18 Example of Excel file
NOTE
The Excel file must contain columns eNodeBID and eNodeBName, and eNodeBID is the first
column, eNodeBID and eNodeBName must be completed correctly, otherwise the system will
display an error message.
2.
View the subscription status of imported NEs in Table 3-47.

Table 3-47 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.
The Nastar starts to deliver rule files to the NEs. The operation information is displayed in the
Log Info area.
----End
Issue 03 (2015-07-30)

165
Nastar
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.
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 3-48 describes the switch status of various data source switches.
Table 3-48 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.
View information about the subscription in the Log Info area. Table 3-49 lists the
parameters.
Issue 03 (2015-07-30)
Parameter
Description
Date/Time

166
Nastar
Parameter
Description
Level
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.
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.
3.6 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.
You are authorized to query analysis data.
Issue 03 (2015-07-30)

167
Nastar
Procedure Diagram
Procedure
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.
Issue 03 (2015-07-30)

168
Nastar
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.
NOTE
l When you query data about multiple eNodeBs, by default, detailed data about the first eNodeB is displayed
in the query results.
l Cell Name and eNodeB Name of deactivated cells are displayed.
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.
3.7 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.
Prerequisites
l
The analysis data and configuration data have been imported to the Nastar database. For
detailed operations, see 3.6 Checking the Integrity of Analysis Data.
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
Issue 03 (2015-07-30)
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
169
Nastar
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
3.11 Periodically Deleting Analysis Data.
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.
Procedure Diagram
Issue 03 (2015-07-30)

170
Nastar
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.
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.
NOTE
When you create an LTE task, Cell Name and eNodeB Name of deactivated cells are not displayed.
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 3-50.
Issue 03 (2015-07-30)

171
Nastar
Table 3-50 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 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 03 (2015-07-30)

172
Nastar
Execution Type
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 Some 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...

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

Issue 03 (2015-07-30)

173
Nastar
If you need to...

Delete a Task
Then...
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 or Running state and click

, or
right-click a periodic task in Waiting or Running state and choose
Suspend from the shortcut menu.
NOTE
Suspension is to suspend the next periodic task rather than the ongoing task.
Restore a suspended
task
Select a periodic task in Suspended state and click

, or right-click
a periodic task in Suspended state and choose Resume from the
shortcut menu.
NOTE
Restoration is to restore the next periodic task rather than the ongoing task.
Set the task result

expiration period.
Click
. In the displayed Task Management Parameter
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

time threshold.
Click
. In the displayed Task Management Parameter
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
Issue 03 (2015-07-30)

174
Nastar
3.8 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%.
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.
Issue 03 (2015-07-30)

175
Nastar
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
3.9 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.
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.
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.
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 3.8 Querying Analysis Results.
Step 2 Optional: In the displayed task analysis result window, click
Observation window is displayed.
. The Geographic
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.
Issue 03 (2015-07-30)

176
Nastar
If you select multiple counters, the Nastar displays the analysis results of the last selected counter.
For details about the Geographic Observation window, see 3.2.3 Interface Description:
Geographic Observation Results.
----End
3.10 Exporting Analysis Reports

This section describes how to export the analysis reports as files.
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 even some
data loss . 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.
on the right side of the progress bar to cancel an export task in the waiting
l You can click
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.
Issue 03 (2015-07-30)

177
Nastar
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
3.11 Periodically Deleting Analysis Data

This section describes how to periodically delete analysis data. When the preset storage duration
for analysis data expires, the Nastar automatically deletes overdue analysis data on the Nastar
server and in the eSAU database. This ensures that the Nastar is running properly.
Prerequisites
You are authorized to set the storage duration for analysis data.
Procedure
Step 2 In the navigation tree of Data Maintenance Management window, choose Data Type >
Analysis sort > *** Data.
Step 3 Click the Delete Data tab to delete analysis data.
If you need to...
Then...
Periodically delete analysis data 1. Select a row where a data type is located, and set the
data storage duration of this data type in Storage
Period.
The data storage duration varies by data type. For
details, see technical specifications of each theme.
After the setting is complete, the Nastar automatically
deletes analysis data at 00:00 every day. For example,
the storage duration for GSM VIP data is 15 days, the
Nastar automatically deletes analysis data of the past
15 days at 00:00 every day.
2. Click Settings.
NOTE
If the data storage duration of different time units can be
configured for a data type, the Nastar saves data of this type based
on time levels. For example, the storage duration for a data is 15
days and 40 hours, the Nastar automatically deletes day-level data
15 days ago and hour-level data 40 hours ago at 00:00 every day.
Immediately delete analysis

data
Click Maintain Data Now.
----End
Issue 03 (2015-07-30)

178
Nastar
Follow-up Procedure
View information about the subscription in the Log Info area. Table 3-51 lists the parameters.
Parameter
Description
Date
Severity
Level of a log, including Minor and Major. You are advised to focus
on logs of the Major level.
Operator
User that executes a task. The default user is system.
Data Type
Type of analysis data on which operations are performed.
Operation Name
Name of a user who performs operations.
Operation Result
Result of an operation. The value can be Successful or Failed.
Select Function, Severity, Condition, and type the keyword. Click Filter to filter log
information.
The latest 100 logs are displayed by default in the Log Info area. Click Show All, the Log
Manager window is displayed. You can view all logs generated within seven days.
Click Show All, the Log Manager window is displayed. Right-click the log list and choose
3.12 FAQs
This section describes the problems and solutions to the FAQs when using the Nastar, and also
provides methods for common operations.
3.12.1 How Do I Enable the LTE Automatic Subscription Function

Prerequisites
You have logged in to the server as user ossuser in SSH mode.
Background
l
On an LTE network, change the configuration file on the server to enable the automatic
subscription function so that you do not need to manually enable the function on the client
and the subscription function can be automatically updated.
The subscription commands related to northbound themes are not issued automatically.
1.
Run the following commands to change the configuration file:
Procedure
Issue 03 (2015-07-30)

179
Nastar
~> cd /opt/nastar/server/Galaxy/bundles/
com.huawei.galaxy.framework.esausubscribe.impl/conf
~> vi subscribe.cfg
NOTE
Change AutoSubscribeEnable=0 in file subscribe.cfg toAutoSubscribeEnable=1.
2.
Press Esc to switch to the command mode and run the :wq! command to save file
subscribe.cfg and quit.
3.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.
Other causes.
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 3.5 Subscribing to Analysis Data.
Solution
If...
Then...
The subscription switch status is
The subscription switch status is
The problem is resolved.

Contact Huawei technical support.
3.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
Issue 03 (2015-07-30)

180
Nastar
(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.
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.
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:

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.
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.
Issue 03 (2015-07-30)

181
Nastar
No.
Procedure
Description
Obtain new subscriber identity

information, such as the IMSI,
MSISDN, and IMEI
l In scenario 1, contact the operator to obtain

the anonymized subscriber identity
information.
the subscriber identity information
encrypted by using the new encryption key.
the plaintext subscriber identity
information.
Change original VIP subscriber

identity information
This procedure is applicable only to VIP

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 3.4.6 Managing VIP Groups or VIP Users
(VIP Analysis).
Re-subscribe to analysis data for

performing VIP analysis
This procedure is applicable only to VIP

analysis. For detailed operations, see 3.5.3
Application Subscription of Analysis Data.
Suspend or delete existing VIP and

complaint analysis tasks
For detailed operations, see the Follow-up

Procedure in 3.7 Creating an Analysis Task.
Re-create VIP and complaint

analysis tasks
For detailed operations, see 3.7 Creating an

Analysis Task.
NOTE
When performing a complaint analysis task, you need
to import the new identity information of the
complaining subscriber into this task.
3.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.
Issue 03 (2015-07-30)

182
Nastar
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).
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.
3.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.
Symptom
If the information that a user inputs into the Nastar by using a PC contains characters of a nonspecified 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.
Issue 03 (2015-07-30)

183
Nastar
3.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.
3.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.
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
Issue 03 (2015-07-30)

184
Nastar
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.
NOTE
For an ATAE cluster system, stop eSAU service see Nastar ATAE Cluster System Administrator
Guide (SUSE11, S3900) > Managing eSAU Services and Processes (Cluster System, ATAE) >
Stopping eSAU Services (Cluster System, ATAE).
4.
Run the following commands to set the communication mode:

# cd /opt/esau
# . ./svc_profile.sh
# cd /opt/esau/script/admin/
# bash setTaoService.sh
5.
When the system displays information similar to the following, type y:

In the following displayed information, XXXX indicates disable or enable.
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
NOTE
For an ATAE cluster system, restart eSAU service see For an ATAE cluster system, stop eSAU
service see Nastar ATAE Cluster System Administrator Guide (SUSE11, S3900) > Managing
eSAU Services and Processes (Cluster System, ATAE) > Starting eSAU Services (Cluster
System, ATAE).
3.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.
Issue 03 (2015-07-30)

185
Nastar
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
details, see Preparing for Obtaining Data (Common) in Nastar Commissioning
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 hours 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
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.
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.
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.
3.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.
Issue 03 (2015-07-30)

186
Nastar
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.
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
details, see Preparing for Obtaining Data (Common) in Nastar Commissioning
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 hours 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
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.
6.
Issue 03 (2015-07-30)
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.
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.
187
Nastar
3.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.
3.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%.
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.
Issue 03 (2015-07-30)
Obtain the number of exceptions in terms of the problem category.

188
Nastar
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.
3.12.12 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.
3.12.13 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.
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.
Issue 03 (2015-07-30)
The data sources are different.

189
Nastar
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.
3.12.14 Handling NE Data Processing Timeout When Tasks Fail to

Be Created in the Nastar
This section describes how to handle NE data processing timeout when tasks fail to be created
in the Nastar.
Symptom
The tasks result information indicating NE data processing timeout is displayed on the Task
Result Information tab page when tasks fail to be created or some tasks are successfully created
on the Nastar client.
Causes
SAU information may not be configured in the Nastar before tasks are created on the Nastar
client.
Procedure
1.
Choose Maintenance > OSS Information Management. Under the NE Management

node, check whether corresponding NEs access SAU information.
2.
The solutions are as follows:

l If SAU information is accessed, contact Huawei technical support.
l If SAU information is not accessed, contact the administrator to access the information.
Issue 03 (2015-07-30)

190
Nastar
4 GSM Network Optimization
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.
4.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.
4.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.
4.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.
4.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 03 (2015-07-30)

191
Nastar
4.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.
4.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.
4.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.
4.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.
4.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
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 for voice service , the Nastar helps you
locate and solve complaint problems.
Issue 03 (2015-07-30)

192
Nastar
4.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.
4.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.
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.
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.
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.
Issue 03 (2015-07-30)

193
Nastar
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 4-1 shows the principles for collecting, importing, and analyzing data on the Nastar. For
detailed operations, see Table 4-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.
Figure 4-1 Principles for analysis
Issue 03 (2015-07-30)

194
Nastar
Table 4-1 Description of analysis
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
applicat
ion data
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U
To deliver performance indicator requirements to the

U2000/M2000 so that the U2000/M2000 filters out the
performance data that meets the Nastar's requirements.
After a user enables the application data subscription
function on the Nastar client, the Nastar issues an
application data subscription command to the eSAU.
Collect
perform
ance
data
eS
AU
U20
00/
M20
00
To deliver a data-processing request to the U2000/

M2000, requesting the U2000/M2000 to filter out the
Upload
perform
ance
data
U2
000
/
M2
000
eSA
U
To upload the performance data that meets the Nastar's

requirements to the eSAU.
2.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U
To issue a data query command to the eSAU. After a user

enables the data maintenance function on the Nastar
client, the Nastar checks whether the analysis data is
ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er
To return data integrity check results to the Nastar server

and display the results on the Nastar client.
3.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U
To issue a task execution request to the eSAU. After a

user creates an analysis task on the Nastar client, the
Nastar server issues a task execution command to the
eSAU, requesting the eSAU to aggregate data.
Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er
To aggregate the data reported by SAUs, generate data

analysis results, and upload the data analysis results to
the Nastar server.

195
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
4. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
To display analysis results on the Nastar client.
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
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 4-2 describes the relation between the quality classes of received signals and the bit error
rate.
Table 4-2 Relation between the quality classes of the received signals and bit error rate
Issue 03 (2015-07-30)
Quality
Class of
Received
Signals
Bit Error Rate (%)
[0.2, 0.4)
[0.4, 0.8)
[0.8, 1.6)
[1.6, 3.2)
[3.2, 6.4)
[6.4, 12.8)
12.8

196
Nastar
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 4-3 describes the relation between the received levels and the seven classes.
Table 4-3 Relation between the received levels and the seven classes
Class of
Received
Level
Received Level (dBm)
(-100, -95]
(-95, -90]
(-90, -85]
(-85, -80]
(-80, -75]
(-75, -70]
> -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 4-4 describes the relations between classes and values of the Uplink
and Downlink Balance Level counter.
Issue 03 (2015-07-30)

197
Nastar
Table 4-4 Description of link balance classes

Uplink and
Downlink
Balance
Class
Downlink Receive Level- Uplink Receive Level- 6 (dB)
-15
-14, -13, -12, -11
-10, -9, -8
-7, -6, -5
-4, -3, -2
-1, 0, 1
2, 3, 4
5, 6, 7
8, 9, 10
10
11, 12, 13, 14
11
15
NOTE
The number 6 in the formula "Downlink receive level - Uplink receive level - 6 (dB)" refers to the 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.
Issue 03 (2015-07-30)
Item
Service Specifications
Execution type
One-time task or periodic task

198
Nastar
Item
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

task
7 days
Duration of one analysis task
<= 5 minutes
Default duration for storing

analysis data
15 days
Maximum duration for storing

analysis data
15 days
4.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.

l
Check that you have applied for a valid license for GSM MR analysis.
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.
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.
Check that you have the view rights of data maintenance and management.
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 3.4.2 Checking the
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 03 (2015-07-30)

199
Nastar
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 V200R013C00 (or later),and the NE version
is BSC6900 V900R015C00 (or later) or BSC6910 V100R015C00 (or later).
4.1.3 Process of GSM MR Analysis

This section describes procedures of GSM MR analysis, and steps of each procedure.
l
Prerequisite
Procedure
Subscription Task Parameters
Analysis Task Parameters
Prerequisite
GSM configuration data has been imported into the Nastar Database. For details, see 4.1.2
Preparations for GSM MR Analysis.
Procedure
Figure 4-2 shows the analysis process.
Figure 4-2 Analysis process
Issue 03 (2015-07-30)

200
Nastar
Table 4-5 Description of GSM MR analysis procedures

No.
Procedur
e
Description
Reference for
Detailed
Operations
(1)
Check the
integrity
of GSM
MR
analysis
data
Entry: Choose Maintenance > Data

Maintenance Management.
3.6 Checking the

Integrity of
Analysis Data
Procedure:
1. Choose Data Type > Basic Network
Optimization > GSM MR 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.
(2)
Subscribe
to analysis
data
(applicati
on)
Navigation path: Choose Maintenance > Data

Subscription Management
3.5 Subscribing
to Analysis Data
Procedure:
1. In the Data Subscription Management
window, click the GSM tab.
2. In the left navigation tree, select the NEs to be
configured.
3. On the MR Analysis tab page, click ON.
4. Set the parameters for the MR analysis data task.
5. Click Confirm.
For details about the parameters, see Subscription
Task Parameters.
Issue 03 (2015-07-30)

201
Nastar
No.
Procedur
e
Description
Reference for
Detailed
Operations
Check the
integrity
of GSM
MR
analysis
data

3.6 Checking the

Integrity of
Analysis Data
Procedure:
Optimization > GSM MR Analysis Data.
4. Click Query.
of the window.
an analysis task.
l If the analysis data does not exist, contact
Huawei technical support.
(3)
Create a
GSM MR
analysis
task
Entry: Choose Theme Function > Basic Network

Optimization > GSM MR Analysis from the
navigation tree of the Analysis Task
Management window.
3.7 Creating an
Analysis Task
Procedure:
1. Double-click GSM MR 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. Set MR analysis parameters on the Parameter
Settings 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 03 (2015-07-30)

202
Nastar
No.
Procedur
e
Description
Reference for
Detailed
Operations
(4)
Query the
GSM MR
overview
analysis
result
Entry: Choose an MR analysis task whose status is

Finished from the upper right area of the Task
Result window. In the lower right Analysis Task
Management area, choose an analysis result of the
task.
3.8 Querying
Analysis Results
Procedure:
1. Double-click an analysis result of the task.
2. View a GSM MR analysis result in the displayed
GSM MR Analysis Task window.
For details about analysis results, see Interface
Description: GSM MR Overview Analysis.
View the
GSM Cell
MR
analysis
result
Entry: Choose a task, whose status is Complete

and which lies in the Task Result area, from the
upper right area of the Analysis Task
Management window.
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.
Description: GSM MR Query.
Compare
GSM MR
analysis
results
Entry: Choose a neighboring cell analysis task

whose status is Complete and whose execution
type is Period from the upper right area of the
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. Rightclick 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.
Description: GSM MR Comparison
Analysis.
Issue 03 (2015-07-30)

203
Nastar
No.
Procedur
e
Description
Reference for
Detailed
Operations
(5)
Export a
GSM MR
overview
analysis
report
Entry: Click the icon on the toolbar in the upper

left part of each MR analysis results window.
3.10 Exporting
Analysis Reports
Procedure:
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.

Application Subscription
Parameter
Description
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.

Basic task information
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.
Task Type
Type of an analysis task to be created.
Remarks
Description of the task.

NE information
Issue 03 (2015-07-30)

204
Nastar
Parameter
Description
Select NE(s)
NEs or cell groups to be selected for analysis.

Network scale for one analysis task <= 10,000 cells
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.
Parameter information
Parameter
Description
Uplink Quality >= X MRs of

(%) >= Y MRs >= Z
If the proportion of MRs in which the uplink quality equals 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 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
Downlink Quality >= X MRs

of (%) >= Y MRs >= Z
If the proportion of MRs in which the downlink quality equals

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.
Uplink Level <= X MRs of

dBm(%) >= Y MRs >= Z
If the proportion of MRs in which the uplink level equals 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 uplink level. It can be -100, -95, -90,
-85, -80, -75, or -70. The default value is -90.
Issue 03 (2015-07-30)

205
Nastar
Parameter
Description
Downlink Level <= X MRs

of dBm(%) >= Y MRs >= Z
If the proportion of MRs in which the downlink level equals

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.
TA >= X MRs of (%) >= Y

MRs >= Z
If the proportion of MRs in which TA equals 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 is a TA value and can be set to any integer from 1 to 64. The
default value is 6.
Downlink Level - Uplink

Level <= X MRs of dB(%)
>= Y and MRs >= Z
If the proportion of MRs in which difference between

downlink level and uplink level equals 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 level difference. It can be -15, -10, -6, -3, or
-1. The default value is -15.
Downlink Level - Uplink

Level >= X MRs of dB(%)
>= Y and MRs >= Z
If the proportion of MRs in which difference between

downlink level and uplink level equals to or is greater 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 difference. It can be 1, 3, 6, 10, or 15. The
Issue 03 (2015-07-30)

206
Nastar
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.
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
eter
Description
Note
Start
time
Date for starting a task.
Start Time of a periodic task = Next

time point + Delay by (hours)
Period
Interval between periodic tasks.

Value range: 1 to 7 Days, and 1 Week.
Repeat
times
Number of times that a periodic task is

executed. If you set this parameter to 0,
the task is executed all the time.
Value range: 0 to 9999
Time period of a periodic task: [Start

Time of a periodic task - Period, Start
Time of a periodic task]
The Next time point is related to Start
time and Period.
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 03 (2015-07-30)

207
Nastar
Param
eter
Description
Note
Delay
by
(hours)
Time delayed for executing a task.
NOTE
Whole
day
Value range: 0 to 24. Unit: hour.

NOTE
If DST starts before a task is executed, the
execution delay will be automatically
updated to ensure that the task can be
executed at the specified time. For example,
if you set Start time at 01:00 on a day, and
the value of Delay by (hours) for the task
was set to 3 hours, the task was scheduled to
be executed at 04:00. However, DST started
before 02:00 on that day, 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).
If you select this parameter, it works the

same as All Busy Time under Busy
hours.
l If the start time of a periodic task is

later than the current server time, the
Nastar automatically executes the task
at the start time.
Example: If the current server time is
01/01/2013 14:00:00, Start time is
01/02/2013, Period is 1 Day, and Delay
by (hours) is 3, the Nastar automatically
executes the task at 01/03/2013
03:00:00.
earlier than the current server time, the
Nastar immediately executes the task.
Example: The current server time is
01/02/2013 14:00:00, Start time is
by (hours) is 3, the Nastar immediately
executes the task.
You are not allowed to set this

parameter.
Busy
hours
If you select this parameter, the 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.
4.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 03 (2015-07-30)

208
Nastar
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.
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 4-3.
Figure 4-3 GSM MR overview analysis interface
Issue 03 (2015-07-30)
N
o.
Name
Description
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.
: 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.

209
Nastar
N
o.
Name
Description
Navigation
tree of GSM
MR overview
report
Users can accurately locate the objects of an MR report on the

navigation tree. The Nastar provides TRX overview analysis of three
latitudes: BSC/Cell Group, TopN, and Filter Condition.
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 03 (2015-07-30)

210
Nastar
N
o.
Name
Description
Area for
TopN TRXs
or
problematic
TRXs
Display the information about TopN TRXs or problematic TRXs

complying with a counter on the navigation tree in a table.
The Nastar provides the function of highlighting MR overview reports
in colors. If the number of TopN TRXs or problematic TRXs for a radio
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
display the table in the descending order.
column header to
For details, see 4.1.5 Reference for GSM MR Analysis Parameters.

4
Area for
TRXs
Display different results for different analysis latitudes:

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.
to display the table in a filtered way; click the
display the table in the descending order.
column header to
For details, see 4.1.5 Reference for GSM MR Analysis Parameters.

5
Area for
counter
charts
Display the selected information in Area 3 and Area 4 in 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.
Task
information
list
l The upper part displays basic information of the task.

l The middle part displays related information about the cell where a
selected TRX is located.
l The lower part displays all filter conditions a selected TRX meets.
Issue 03 (2015-07-30)

211
Nastar
Interface Description: GSM MR Query

This section describes the interface for GSM MR query results. Before performing relevant
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
4-4.
Figure 4-4 GSM MR query result interface
Issue 03 (2015-07-30)

212
Nastar
No.
Name
Description
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.
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.
Area for counter

charts
Display the selected information in Area 1 and Area 2 in

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 doubleclick 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.
Task information
list
Display basic information of this task, and related

information about the cell corresponding to the selected
TRX in Area 2.
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.
Issue 03 (2015-07-30)
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.

213
Nastar
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

GSM MR analysis task is set to BSC
1. Select Cell, BSC or All from the upper area

in the navigation tree.
2. Select one or multiple objects from the
navigation tree.
3. Click OK.
Select NE Object for the current

GSM MR analysis task is set to Cell
Group
1. Select All, NE Group or Cell from the upper

area in the navigation tree.
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 4-5.
Figure 4-5 GSM MR comparison report interface
Issue 03 (2015-07-30)

214
Nastar
No.
Name
Description
Area for counter

overview
information
Displays the differences of radio link counters of each object

within two periods in tables. Area 1 and Area 2 are displayed
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.
Area for counter

charts
Displays the counter comparison information about a selected

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.
4.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.
Issue 03 (2015-07-30)

215
Nastar
Parameters for Querying TRXs on the Entire Network (1)

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

216
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Average Uplink
Receive Quality
[0,+)
N/A
Indicates the
number of
TRXs with the
average
received signal
quality values of
the BTSs
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Average
Downlink
Receive Quality
[0,+)
N/A
Indicates the
number of
TRXs with the
average
received signal
quality values of
the MSs
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

217
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Average Uplink
Receive Level
[0,+)
dBm
Indicates the
number of
TRXs with the
average
received levels
of the BTSs
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Average
Downlink
Receive Level
[0,+)
dBm
Indicates the
number of
TRXs with the
average
received levels
of the MSs
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

218
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Average TA
Distribution
[0,+)
N/A
Indicates the
number of
TRXs with the
values of
Average TA
Distribution
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Link Balance
[0,+)
N/A
Indicates the
number of
TRXs with the
values of Link
Balance
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

219
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Uplink Quality
>= X AND MR
(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the uplink
quality is larger
than or equal to
X in all MRs
exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
NOTE:
l SRAN10.0/
GBSS17.0/
RAN17.0
X and Y are the

thresholds
specified when
you create an
analysis task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Downlink
Quality >= X
AND MR(%)
>= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the
downlink
quality is larger
than or equal to
X in all MRs
exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

220
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Uplink Level
Grade <= X
dBm AND MR
(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the uplink
level grade is
smaller than or
equal to X in all
MRs exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Downlink Level
Grade <= X
dBm AND MR
(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the
downlink level
grade is smaller
than or equal to
X in all MRs
exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

221
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

TA >= X AND
MR(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the TA is
larger than or
equal to X in all
MRs exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Link Balance
<= X dB AND
MR(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the link
balance is
smaller than or
equal to X in all
MRs exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

222
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Link Balance
>= X dB AND
MR(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the link
balance is larger
than or equal to
X in all MRs
exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

223
Nastar
Parameters for Querying TRXs on the Entire Network (2)

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

224
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
value of the
average
received signal
quality (full
rate) of the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

225
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
value of the
average
received signal
quality (full
rate) of the MS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received level
(full rate) of the
BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

226
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received level
(full rate) of the
MS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

227
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Link Balance
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS Average
received level of
the BTS Difference
between the
values of the
average
sensitivity of the
MS and BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

228
Nastar
Parameters for Querying TRXs in a GBSC(1)

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

229
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

230
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX ID
[0,8191]
N/A
Index of a TRX,
uniquely
identifying a
TRX in a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX No.
[0,125]
N/A
Number of a
TRX in a BTS.
The number of a
TRX is unique
in a BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

231
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

232
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the BTSs
corresponding
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

233
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the MSs
corresponding
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

234
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Link Balance
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS
corresponding
to the TopN
TRX or
problematic
TRX controlled
by the BSC Average
received level of
the BTS
corresponding
to the TopN
TRX or
problematic
TRX controlled
by the BSC Difference
between the
values of the
average
sensitivity of the
MS and BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
235
Nastar
Parameters for Querying TRXs in a GBSC(2)

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

236
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

237
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX ID
[0,8191]
N/A
Index of a TRX,
uniquely
identifying a
TRX in a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX No.
[0,125]
N/A
Number of a
TRX in a BTS.
The number of a
TRX is unique
in a BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

238
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Frequency Band
GSM900
GSM1800
N/A
Indicates the
frequency band
assigned to
BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

239
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

240
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

241
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Link Balance
Issue 03 (2015-07-30)
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS
corresponding
to each TRX Average
received level of
the BTS
corresponding
to each TRX Difference
between the
values of the
average
sensitivity of the
MS and BTS.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
242
Nastar
Parameters related to the basic information

Parameter
Range
Unit
Description
Supported
Solution
Version
Task Name
1 to 64
characters
N/A
Indicates the
name of the
queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Start Time
N/A
N/A
Indicates the
time that the
Nastar starts
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

243
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
End Time
N/A
N/A
Indicates the
time that the
Nastar stops
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Creator
N/A
N/A
Indicates the
creator's name
of the queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

244
Nastar
Parameters Related to Querying TopN TRXs(1)

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

245
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

246
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX ID
[0,8191]
N/A
Index of a TRX,
uniquely
identifying a
TRX in a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX No.
[0,125]
N/A
Number of a
TRX in a BTS.
The number of a
TRX is unique
in a BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

247
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

248
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the BTSs
corresponding
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

249
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the MSs
corresponding
to the TopN
TRXs or
problematic
TRXs
controlled by
the BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

250
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Link Balance
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS
corresponding
to the TopN
TRX or
problematic
TRX controlled
by the BSC Average
received level of
the BTS
corresponding
to the TopN
TRX or
problematic
TRX controlled
by the BSC Difference
between the
values of the
average
sensitivity of the
MS and BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
251
Nastar
Parameters Related to Querying TopN TRXs(2)

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

252
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

253
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX ID
[0,8191]
N/A
Index of a TRX,
uniquely
identifying a
TRX in a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX No.
[0,125]
N/A
Number of a
TRX in a BTS.
The number of a
TRX is unique
in a BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

254
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Frequency Band
GSM900
GSM1800
N/A
Indicates the
frequency band
assigned to
BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

255
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

256
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

257
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Link Balance
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS
corresponding
to each TRX Average
received level of
the BTS
corresponding
between the
values of the
average
sensitivity of the
MS and BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
258
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Task Name
1 to 64
characters
N/A
Indicates the
name of the
queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Start Time
N/A
N/A
Indicates the
time that the
Nastar starts
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

259
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
End Time
N/A
N/A
Indicates the
time that the
Nastar stops
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Task Creator
N/A
N/A
Indicates the
creator's name
of the queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

260
Nastar
Parameters Related to Querying the TRXs on the Entire Network (1)

Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Group ID
N/A
N/A
Indicates the ID
of a cell group.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Group
Name
1 to 128
characters
N/A
Indicates the
name of a cell
group, for
example,
CELL_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

261
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Average Uplink
Receive Quality
[0,+)
N/A
Indicates the
number of TopN
TRXs with the
average quality
values of the
received signals
of the BTSs
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Average
Downlink
Receive Quality
[0,+)
N/A
Indicates the
number of TopN
TRXs with the
average quality
values of the
received signals
of the MSs
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

262
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Average Uplink
Receive Level
[0,+)
dBm
Indicates the
number of TopN
TRXs with the
average
received levels
of the BTSs
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Average
Downlink
Receive Level
[0,+)
dBm
Indicates the
number of TopN
TRXs with the
average
received levels
of the MSs
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

263
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Average TA
Distribution
[0,64)
N/A
Indicates the
number of TopN
TRXs with the
values of
Average TA
Distribution
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Link Balance
[0,+)
N/A
Indicates the
number of TopN
TRXs with the
values of Link
Balance
exceeding the
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

264
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Uplink Quality
>= X AND MR
(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the uplink
quality is larger
than or equal to
X in all MRs
exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
NOTE:
l SRAN10.0/
GBSS17.0/
RAN17.0
X and Y are the

thresholds
specified when
you create an
analysis task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Downlink
Quality >= X
AND MR(%)
>= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the
downlink
quality is larger
than or equal to
X in all MRs
exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

265
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Uplink Level
Grade <= X
dBm AND MR
(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the uplink
level grade is
smaller than or
equal to X in all
MRs exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Downlink Level
Grade <= X
dBm AND MR
(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the
downlink level
grade is smaller
than or equal to
X in all MRs
exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

266
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

TA >= X AND
MR(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the TA is
larger than or
equal to X in all
MRs exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX Count for

Link Balance
<= X dB AND
MR(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the link
balance is
smaller than or
equal to X in all
MRs exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

267
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX Count for

Link Balance
>= X dB AND
MR(%) >= Y%
[0,+)
N/A
Indicates the
number of the
TRXs for which
the proportion
of the MRs in
which the link
balance is larger
than or equal to
X in all MRs
exceeds Y.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

268
Nastar
Parameters Related to Querying the TRXs on the Entire Network (2)

Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Group ID
N/A
N/A
Indicates the ID
of a cell group.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Group
Name
1 to 128
characters
N/A
Indicates the
name of a cell
group, for
example,
CELL_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

269
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
value of the
average
received signal
quality (full
rate) of the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

270
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
value of the
average
received signal
quality (full
rate) of the MS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received level
(full rate) of the
BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

271
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received level
(full rate) of the
MS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

272
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Link Balance
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS Average
received level of
the BTS Difference
between the
values of the
average
sensitivity of the
MS and BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

273
Nastar
Parameters Related to Querying TRXs in a Cell Group (1)

Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Group ID
N/A
N/A
Indicates the ID
of a cell group.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Group
Name
1 to 128
characters
N/A
Indicates the
name of a cell
group, for
example,
CELL_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

274
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
[1,64]
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

275
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX ID
[0,8191]
N/A
Index of a TRX,
uniquely
identifying a
TRX in a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX No.
[0,125]
N/A
Number of a
TRX in a BTS.
The number of a
TRX is unique
in a BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

276
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTS
corresponding
to a TopN TRX
or problematic
TRX in the cell
group.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

277
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MS
corresponding
to a TopN TRX
or problematic
TRX in the cell
group.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received level
value of the BTS
corresponding
to a TopN TRX
or problematic
TRX in the cell
group.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

278
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received level
value of the MS
corresponding
to a TopN TRX
or problematic
TRX in the cell
group.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
is used by the
MS to advance
its timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

279
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Link Balance
N/A
dB
Indicates the dB
value,
corresponding
to a TopN TRX
or problematic
TRX in the cell
group,
calculated
through this
expression:
Average
received level of
the MS
corresponding
to the TopN
TRX or
problematic
TRX - Average
received level of
the BTS
corresponding
to the TopN
TRX or
problematic
TRX Difference
between the
values of the
average
sensitivity of the
MS and BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
280
Nastar
Parameters Related to Querying TRXs in a Cell Group (2)

Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Group ID
N/A
N/A
Indicates the ID
of a cell group.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Group
Name
1 to 128
characters
N/A
Indicates the
name of a cell
group, for
example,
CELL_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

281
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
[1,64]
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

282
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX ID
[0,8191]
N/A
Index of a TRX,
uniquely
identifying a
TRX in a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX No.
[0,125]
N/A
Number of a
TRX in a BTS.
The number of a
TRX is unique
in a BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

283
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Frequency Band
GSM900
GSM1800
N/A
Indicates the
frequency band
assigned to
BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

284
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

285
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

286
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Link Balance
Issue 03 (2015-07-30)
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS
corresponding
to each TRX Average
received level of
the BTS
corresponding
between the
values of the
average
sensitivity of the
MS and BTS.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
287
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Task Name
1 to 64
characters
N/A
Indicates the
name of the
queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Start Time
N/A
N/A
Indicates the
time that the
Nastar starts
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

288
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
End Time
N/A
N/A
Indicates the
time that the
Nastar stops
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Task Creator
N/A
N/A
Indicates the
creator's name
of the queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

289
Nastar
Parameters Related to Querying Problematic TRXs Involved in Filter Condition

Analysis (1)
Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

290
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

291
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX ID
[0,8191]
N/A
Index of a TRX,
uniquely
identifying a
TRX in a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX No.
[0,125]
N/A
Number of a
TRX in a BTS.
The number of a
TRX is unique
in a BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

292
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTS
corresponding
to the
problematic
TRX.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

293
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MS
corresponding
to the
problematic
TRX.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received level of
the BTS
corresponding
to the
problematic
TRX.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

294
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received level of
the MS
corresponding
to the
problematic
TRX.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
is used by the
MS to advance
its timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

295
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Link Balance
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS
corresponding
to the
problematic
TRX - Average
received level of
the BTS
corresponding
to the
problematic
TRX Difference
between the
values of the
average
sensitivity of the
MS and BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
296
Nastar
Parameters Related to Querying Problematic TRXs Involved in Filter Condition

Analysis (2)
Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

297
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

298
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX ID
[0,8191]
N/A
Index of a TRX,
uniquely
identifying a
TRX in a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX No.
[0,125]
N/A
Number of a
TRX in a BTS.
The number of a
TRX is unique
in a BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

299
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Frequency Band
GSM900
GSM1800
N/A
Indicates the
frequency band
assigned to
BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

300
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

301
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

302
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Link Balance
Issue 03 (2015-07-30)
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS
corresponding
to each TRX Average
received level of
the BTS
corresponding
between the
values of the
average
sensitivity of the
MS and BTS.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
303
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Task Name
1 to 64
characters
N/A
Indicates the
name of the
queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Start Time
N/A
N/A
Indicates the
time that the
Nastar starts
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

304
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
End Time
N/A
N/A
Indicates the
time that the
Nastar stops
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Task Creator
N/A
N/A
Indicates the
creator's name
of the queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

305
Nastar
Parameters Related to Querying TopN TRXs and Problematic TRXs in the MR

Analysis Results (1)
Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

306
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

307
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

308
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

309
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

310
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Link Balance
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS
corresponding
to each TRX Average
received level of
the BTS
corresponding
between the
values of the
average
sensitivity of the
MS and BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
311
Nastar
Parameters Related to Querying TopN TRXs and Problematic TRXs in the MR

Analysis Results (2)
Parameter
Range
Unit
Description
Supported
Solution
Version
BSC ID
1 to 64
characters
N/A
Indicates the ID
of a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC Name
1 to 64
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

312
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

313
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TRX ID
[0,8191]
N/A
Index of a TRX,
uniquely
identifying a
TRX in a BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TRX No.
[0,125]
N/A
Number of a
TRX in a BTS.
The number of a
TRX is unique
in a BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

314
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Frequency Band
GSM900
GSM1800
N/A
Indicates the
frequency band
assigned to
BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
transferred over
the channel.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

315
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

316
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the BTSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received levels
of the MSs
corresponding
to all TRXs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

317
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average TA
Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Link Balance
Issue 03 (2015-07-30)
N/A
dB
Indicates the dB
value calculated
through this
expression:
Average
received level of
the MS
corresponding
to each TRX Average
received level of
the BTS
corresponding
between the
values of the
average
sensitivity of the
MS and BTS.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
318
Nastar
Parameters Related to the Basic Information (1)

Parameter
Range
Unit
Description
Supported
Solution
Version
Task Name
1 to 64
characters
N/A
Indicates the
name of the
queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Start Time
N/A
N/A
Indicates the
time that the
Nastar starts
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

319
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
End Time
N/A
N/A
Indicates the
time that the
Nastar stops
generating a
task report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Creator
N/A
N/A
Indicates the
creator's name
of the queried
performance
analysis task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

320
Nastar
Parameters Related to the Basic Information (2)

Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,2047]
N/A
Indicates the
number of the
cell that the
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that the TRX
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

321
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
LAC
[1,65533],
[65535]
N/A
Indicates the
location area
code of the cell
where the
selected TRX is
located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CI
[0,65535]
N/A
Indicates the ID
of the cell where
the selected
TRX is located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

322
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BCCH
[0,1023]
N/A
Indicates the
frequency
transmitted on
the BCCH.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BCC
[0,7]
N/A
Indicates the
color code of a
base station.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

323
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
NCC
[0,7]
N/A
Indicates the
network color
code.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Layer
[1,4]
N/A
Indicates the
layer where the
cell is located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

324
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Priority
[1,3]
N/A
Indicates the
cell priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Supporting Half
Rate
Yes, No
N/A
Indicates
whether half
rate is
supported.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

325
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Frequency
Hopping Type
N/A
N/A
Indicates the
type of the
frequency
hopping, such as
the RF hopping
and baseband
frequency
hopping.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Supporting
GPRS
Yes, No
N/A
Indicates
whether the
GPRS service is
supported.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

326
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Supporting
EDGE
Yes, No
N/A
Indicates
whether the
EDGE service is
supported.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Type
Normal Cell,
Concentric
Circle Cell,
Enhanced Dual
Frequency
Network Cell
N/A
Indicates the
cell type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

327
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Base Station
Type
N/A
N/A
Indicates the
BTS type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

328
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Object Name
1 to 64
characters
N/A
Names of the
objects to which
two MR results
to be compared
belong.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
First Total
Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
in the previous
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

329
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Second Total
Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
in the next
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Difference of
Total
Measurement
Reports
[0,+)
Number
Indicates the
differences of
the number of
MRs in the
previous and
next periods.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

330
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
First Average
Uplink Receive
Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to all the TRXs
in the previous
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Second Average
Uplink Receive
Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
BTSs
corresponding
to all the TRXs
in the next
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

331
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Quality
Difference
[-7,7]
N/A
Indicates the
differences of
the average
received signal
quality values of
the BTSs
corresponding
to all the TRXs
in the previous
and next
periods.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
First Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to all the TRXs
in the previous
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

332
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Second Average
Downlink
Receive Quality
[0,7]
N/A
Indicates the
average quality
of received
signals of the
MSs
corresponding
to all the TRXs
in the next
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Quality
Difference
[-7,7]
N/A
Indicates the
differences of
the average
received signal
quality values of
the MSs
corresponding
to all the TRXs
in the previous
and next
periods.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

333
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
First Average
Uplink Receive
Level
[-110,-40]
dBm
Indicates the
average
received signal
levels of the
BTSs
corresponding
to all the TRXs
in the previous
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Second Average
Uplink Receive
Level
[-110,-40]
dBm
Indicates the
average
received signal
levels of the
BTSs
corresponding
to all the TRXs
in the next
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

334
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Receive Level
Difference
[-70,70]
dBm
Indicates the
differences of
the average
received signal
levels of the
BTSs
corresponding
to all the TRXs
in the previous
and next
periods.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
First Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received signal
levels of the
MSs
corresponding
to all the TRXs
in the previous
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

335
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Second Average
Downlink
Receive Level
[-110,-40]
dBm
Indicates the
average
received signal
levels of the
MSs
corresponding
to all the TRXs
in the next
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Receive Level
Difference
[-70,70]
dBm
Indicates the
differences of
the average
received signal
levels of the
MSs
corresponding
to all the TRXs
in the previous
and next
periods.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

336
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
First Average
TA Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS in the
previous period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Second Average
TA Distribution
[0,64)
N/A
Indicates the
weighted
average TA that
the MS uses to
advance its
timings of
transmissions to
the BTS in the
next period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

337
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average TA
Distribution
Difference
(-64,64)
N/A
Indicates the
difference of the
weighted
average TAs
that the MS uses
to advance its
timings of
transmissions to
the BTS in the
previous and
next periods.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
First Link
Balance
Issue 03 (2015-07-30)
N/A
dB
Indicates the dB
value in the
previous period,
which is
calculated
through this
expression:
Average
received level of
the MS
corresponding
to each TRX Average
received level of
the BTS
corresponding
between the
values of the
average
sensitivity of the
MS and BTS.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
338
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Second Link
Balance
N/A
dB
Indicates the dB
value in the next
period, which is
calculated
through this
expression:
Average
received level of
the MS
corresponding
to each TRX Average
received level of
the BTS
corresponding
between the
values of the
average
sensitivity of the
MS and BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
difference
between the
value of First
Link Balance
and the value of
Second Link
Balance.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Link Balance
Difference
N/A
dB
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

339
Nastar
4.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.
4.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.
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 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.
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.
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.
Issue 03 (2015-07-30)

340
Nastar
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.
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.
NOTE
Issue 03 (2015-07-30)

341
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
applicat
ion data
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U
To request the U2000/M2000 to filter out the

performance data and neighboring cell measurement
data that meets the Nastar's requirements. After a user
enables the application data subscription function on the
Nastar client, the Nastar issues an application data
subscription command to the eSAU.

342
Nastar
User
Operat
ion
Issue 03 (2015-07-30)
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Collect
perform
ance
data and
neighbo
ring cell
measure
ment
data
eS
AU
U20
00/
M20
00

data that meets the Nastar's requirements.
Upload
perform
ance
data and
neighbo
ring cell
measure
ment
data
U2
000
/
M2
000
eSA
U
To upload the performance data and neighboring cell

measurement data that meets the Nastar's requirements
to the eSAU.
2.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

3.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
4. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er

343
Nastar
NOTE
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 4-7 describes network changes and their
impacts.
Table 4-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

data, such as the azimuth,
tilt, and height of an
antenna
The cell coverage and network interference may change.
Adjusting the transmit

power or other powerrelated parameters, such
as discontinuous
transmission or power
control.
Adjusting frequency
planning, for example,
adding new frequencies
Adjustment of configuration data affects the identification of

defined and undefined neighboring GSM cells. As a result, the
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
relationship and
handover parameters
Statistical results are affected if you change the handover

parameters and handover relationship during neighbor
relationship data collection and optimization.
Adjusting the BSC

topology or other
network topology
As the BSC is responsible for collecting statistical results, the

measurement task cannot be successfully executed if the network
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 4-8 shows the spacing rules for GSM ARFCNs.
Issue 03 (2015-07-30)

344
Nastar
NOTE
l The ARFCNs that violate co-site spacing rules are highlighted in pink with the legend
ARFCNs that violate co-cell spacing rules are highlighted in red with the legend
. The
. 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 4-8 Description of GSM ARFCN spacing rules
Issue 03 (2015-07-30)
Cla
ss
Sub
class
Description
Example
Cosite
Betw
een
BCC
H
ARF
CNs
If a BCCH ARFCN of
a cell violates an
ARFCN spacing rule
for a BCCH ARFCN of
the selected co-site cell,
this BCCH ARFCN is
highlighted in pink in
BCCH.
Scenario: Three co-site cells are Cell A, Cell B, and

Cell C. The BCCH ARFCN spacing is set to 2.
CellB_BCCH=16 and CellC_BCCH=20.
Betw
een
TCH
ARF
CNs
If a TCH ARFCN of a
cell violates an ARFCN
spacing rule for a TCH
ARFCN of the selected
co-site cell, this TCH
ARFCN is highlighted
in pink in TCH.

Cell C. The TCH ARFCN spacing rules is set to 2.
CellB_TCH=8, 21, and CellC_TCH=4, 13.
Purpose: To set BCCH ARFCNs for Cell A.

Result: According to the ARFCN spacing rule,
CellA_BCCH must not be set to 15, 16, 17, 19, 20,
or 21. If these ARFCNs are present in the 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.
Purpose: To set TCH ARFCNs for Cell A.

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.

345
Nastar
Cla
ss
Cocell
Issue 03 (2015-07-30)
Sub
class
Description
Example
Betw
een
BCC
H
ARF
CNs
and
TCH
ARF
CNs
l If a TCH frequency
is displayed in pink
in TCH if it is not
properly isolated
from the BCCH
frequency of a cosite cell of the
selected cell.

Cell C. The spacing rules between BCCH ARFCNs
and TCH ARFCNs is set to 2. CellB_BCCH=16,
CellC_BCCH=20, CellB_TCH=8, 21, and
CellC_TCH=4, 13.
Betw
een
BCC
H
ARF
CNs
Each cell has only one

BCCH ARFCN.
Therefore, no spacing
rule is required for
BCCH ARFCN of one
cell. The default
spacing is 0, which
means no limitation on
ARFCNs.
Betw
een
TCH
ARF
CNs
If a TCH ARFCN
violates an ARFCN
spacing rule for a TCH
ARFCN of the selected
cell, this TCH ARFCN
is highlighted in red in
TCH.
Scenario: The selected cell is Cell A. The co-cell

TCH ARFCN spacing rules is set to 2.
CellA_TCH=27, 51, 61.
l If a BCCH ARFCN
violates a spacing
rule between BCCH
ARFCNs and TCH
ARFCNs for a TCH
ARFCN of the
selected co-site cell,
this BCCH ARFCN
is highlighted in
pink in BCCH.
Purpose: To set a BCCH ARFCN and TCH

ARFCNs for Cell A.
CellA_TCH must not be set to 15, 16, 17, 19, 20, or
21; CellA_BCCH 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 and
candidate BCCH ARFCNs of Cell A, these
ARFCNs are highlighted in pink, indicating that
these ARFCNs violate the spacing rule between
BCCH ARFCNs and TCH ARFCNs for co-site
cells. These ARFCNs are not recommended.
Purpose: To set new TCH ARFCNs for Cell A.

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.

346
Nastar
Cla
ss
Nei
ghb
orin
g
cell
Issue 03 (2015-07-30)
Sub
class
Description
Example
Betw
een
BCC
H
ARF
CNs
and
TCH
ARF
CNs
l If a TCH frequency
is displayed in red in
TCH if it is not
properly isolated
from the BCCH
frequency of the
selected cell.
Scenario: The selected cell is Cell A. The spacing

rules between the BCCH ARFCN and TCH
ARFCNs of one cell is set to 2. CellA_BCCH=15
and CellA_TCH=27, 51, 61.
Betw
een
BCC
H
ARF
CNs
If a BCCH ARFCN
violates an ARFCN
spacing rule for the
BCCH ARFCN of a
defined neighboring
cell of the selected cell,
this BCCH ARFCN is
highlighted in orange in
BCCH.
l If a BCCH
frequency is
displayed in red in
BCCH if it is not
properly isolated
from the TCH
frequencies of the
selected cell.

ARFCNs for Cell A.
CellA_TCH must not be set to 14 or 16.
or 62. If these ARFCNs are present in the candidate
TCH ARFCNs and candidate BCCH ARFCNs of
Cell A, these ARFCNs are highlighted in red,
indicating that these ARFCNs violate the spacing
rule between the BCCH ARFCN and TCH ARFCNs
for one cell. These ARFCNs are not recommended.
Scenario: The serving cell is Cell A, and its defined
neighboring cells are Cell B, Cell C, and Cell D. The
spacing for BCCH ARFCNs between the serving
cell and its neighboring cells is set to 2.
CellB_BCCH=16, CellC_BCCH=19, and
CellD_BCCH=27.
Purpose: To set BCCH ARFCNs for Cell A.
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.

347
Nastar
Cla
ss
Sub
class
Description
Example
Betw
een
TCH
ARF
CNs
If a TCH frequency is
displayed in orange in
TCH if it is not
properly isolated from
the TCH frequencies of
a defined neighboring
cell of the selected cell.

spacing for BCCH ARFCNs between the serving
cell and its neighboring cells is set to 2.
CellB_TCH=16, 19, CellC_TCH=27, 45, and
CellD_TCH=87, 102.
Purpose: To set TCH ARFCNs for Cell A.
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
een
BCC
H
ARF
CNs
and
TCH
ARF
CNs
l If a TCH ARFCN
violates a spacing
rule between BCCH
ARFCNs and TCH
ARFCNs for the
BCCH ARFCN of a
defined
neighboring cell of
the selected cell,
this TCH ARFCN is
highlighted in
orange in TCH.
l If a BCCH ARFCN
violates a spacing
rule between BCCH
ARFCNs and TCH
ARFCNs for a TCH
ARFCN of a
defined
neighboring cell of
the selected cell,
this BCCH ARFCN
is highlighted in
orange in BCCH.

ARFCN spacing between the serving cell and its
neighboring cells is set to 2. CellB_BCCH=16,
CellC_BCCH=19, CellD_BCCH=27,
CellB_TCH=16, 19, CellC_TCH=27, 45, and
CellD_TCH=87, 102.
ARFCNs for Cell A.
20, 26, 27, 28, 44, 45, 46, 86, 87, 88, 101, 102, or
103. CellA_TCH must not be set to 15, 16, 17, 18,
19, 20, 26, 27, or 28. If these ARFCNs are present
in the candidate TCH ARFCNs and candidate
BCCH ARFCNs of Cell A, these ARFCNs are
highlighted in orange, indicating that these ARFCNs
violate spacing rules between BCCH ARFCNs and
TCH ARFCNs for the serving cell and its
neighboring cells. These ARFCNs are not
recommended.
Technical Specifications for GSM Frequency Analysis

of analysis time.
Issue 03 (2015-07-30)

348
Nastar
NOTE
Item
Execution type
One-time task
Network scale for one

analysis task
<= 10,000 cells
Number of allowed
analysis tasks
<= 50
Time range for data in

one analysis task
7 days
Duration of one analysis

task
<= 30 minutes
Default duration for

storing analysis data
15 days
Maximum duration for

15 days
4.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.

l
Check that you have applied for a valid license for GSM frequency analysis.
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.
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.

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.
Issue 03 (2015-07-30)

349
Nastar
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.

l
Check that the matching U2000/M2000 version is V200R013C00 (or later),and the NE
version is BSC6900 V900R015C00 (or later) or BSC6910 V100R015C00 (or later).
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(RH2288).
4.2.3 Process of GSM Frequency Analysis

This section describes the process of GSM frequency analysis, and steps of each procedure.
l
Prerequisite
Procedure
Issue 03 (2015-07-30)

350
Nastar
Prerequisite
GSM configuration data and GSM engineering parameters have been imported into the Nastar
Database. For details, see 4.2.2 Preparations for GSM Frequency Analysis.
Procedure
Issue 03 (2015-07-30)

351
Nastar
Table 4-9 Description of GSM frequency analysis procedures

N
o.
Procedure
Description
Reference for
Detailed
Operations
(1
)
Check the
integrity of
GSM
frequency
analysis
data

Maintenance Management
3.6 Checking the

Integrity of
Analysis Data
Procedure:
1. Set Data Type to GSM Frequency Analysis
Data.
4. Click Query.
of the window.
an analysis task.
performing (2).
NOTE
Issue 03 (2015-07-30)

352
Nastar
N
o.
Procedure
Description
Reference for
Detailed
Operations
(2
)
Subscribe
to GSM
frequency
analysis
data
(applicatio
n)
NOTE
When a neighboring cell measurement task is being
performed, the BA2 table does not automatically update.
Ensure frequency stability of measured cells and their
neighboring cells. Otherwise, errors may occur during
cell handover and measurement data may not be accurate.
3.5 Subscribing to
Analysis Data

Procedure:
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 .
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 03 (2015-07-30)

353
Nastar
N
o.
Procedure
Description
Reference for
Detailed
Operations
Check the
integrity of
GSM
frequency
analysis
data

3.6 Checking the

Integrity of
Analysis Data
Procedure:
1. Set Data Type to GSM Frequency Analysis
Data.
4. Click Query.
of the window.
an analysis task.
(3
)
Create a
GSM
frequency
analysis
task
Navigation path: Choose Theme Function >

Basic Network Optimization > GSM Frequency
Analysis Task from the navigation tree of the
3.7 Creating an
Analysis Task
Procedure:
1. Double-click GSM Frequency Analysis Task.
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
generated within this time range.
6. Click Finish.
Issue 03 (2015-07-30)

354
Nastar
N
o.
Procedure
Description
Reference for
Detailed
Operations
(4
)
View the
GSM
frequency
analysis
result
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.
3.8 Querying
Analysis Results
Procedure:
2. View the GSM frequency analysis result in the
displayed GSM Frequency Analysis Task
window.
Description: GSM Frequency Analysis.
Issue 03 (2015-07-30)

355
Nastar
N
o.
Procedure
Description
(5
)
View the
GSM
frequency
optimizatio
n result
Navigation path: Choose a frequency analysis task

whose status is Finished from the upper right area
of the Analysis Task Management window. In the
lower right Task Result area, choose an analysis
result of the task.
Reference for
Detailed
Operations
Procedure:
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 03 (2015-07-30)

356
Nastar
N
o.
Procedure
Description
Reference for
Detailed
Operations
(6
)
Export the
GSM
frequency
analysis
report
Navigation path: Click the icon on the toolbar in

the upper left part of each analysis results window.
3.10 Exporting
Analysis Reports
Procedure:
Description: GSM Frequency Analysis.
3. Click Save.
(7
)
Export the
GSM
frequency
optimizatio
n report

Procedure:
Description: GSM Frequency Optimization.
3. Click Save.

Parameter
Description
Task Name
Indicates the name of a created analysis task.

Value range:
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.
Time Setting
Start Time
Indicates the time when the task starts to run.

The start time must be later than the current time. By
default, the start time is five minutes later than the
current system time.
Cycle Setting
Cycle
Indicates the interval between periodic tasks. This

parameter involves the period unit and the interval.
Interval: 1 to 65535.
Issue 03 (2015-07-30)

357
Nastar
Parameter
Description
Execute Times
Indicates the times that a periodic task is executed.

If this parameter is set to 0, you can infer that the task
is executed all the time.
Value range: 0 to 3650.
Measure extra frequencies
l If this parameter is selected, the Nastar delivers

an analysis task to SAUs and delivers data source
switches to the 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
Task
Measurement step
Indicates the number of ARFCNs in the same group.

The value is an integer from 1 to 31, including 1 and
31.
The measurement step must be less than or equal to
the minimum rest step of the selected cell.
NOTE
The measurement duration (Number of ARFCNs/
Measurement step x Measurement period) is less than or
equal to 24 hours. If the number of ARFCNs is not an
integer multiple of the measurement step, the value of
Number of ARFCNs/Measurement step must be rounded
up. For example, the value of [5/2] is 3.
Cell Object
Indicates the cell involved in the neighboring cell

measurement task. The cell is displayed in the format
of Cell ID+Cell name+BA2 table length.
NOTICE
It is recommended that the number of measured cells
delivered by each BSC do not exceed 200. If the number
exceeds 200, the data about some cells cannot be reported
completely. The maximum number of measured cells is
400.
Issue 03 (2015-07-30)

358
Nastar
Parameter
Description
Selected Frequency
You need to collect the frequencies that you want to

measure. This ensures that all signal strength values
of the neighboring cells of a cell can be measured in
order to identify possible missing neighboring cells.
Frequencies are managed by group, and the number
of frequencies in each group is determined by the
value of Measure Step.
NOTE
l You can select a maximum of 762 ARFCNs for a cell.
If the number exceeds 762, the NE returns an error
message after the corresponding MML command is
executed, indicating that the task creation or
modification fails.
l Before setting this parameter, you must set Measure
Step. The selected ARFCNs are grouped by Measure
Step. For example, if Measure Step is set to 2 and the
ARFCNs 59, 60, and 61 are selected, the ARFCNs are
organized into two groups. One group consists of
ARFCNs 59 and 60, and the other group consists of
ARFCN 61.
The U2000/M2000 measures the ARFCN groups in
turn during the measurement period. You can also
change the value of Measure Step to reorganize the
ARFCNs after setting the ARFCNs.
Search
Recommended
ARFCNs
Click Search Recommended ARFCNs. The Nastar

traverses the three-level neighboring cells of the
selected cell. Then, the Nastar analyzes the BCCH
ARFCNs of the traversed neighboring cells and
highlights these BCCH ARFCNs in the frequency
selection area in gray to provide reference for
selecting measurement ARFCNs.
Traversing of the three-level neighboring cells
indicates that the Nastar searches for the neighboring
cell (neighboring cell A) of the selected cell, the
neighboring cell (neighboring cells B) of
neighboring cell A, and the neighboring cell
(neighboring cells C) of neighboring cell B. All
traversed neighboring cells A, B, and C are
neighboring cells obtained through the traversing of
the three-level neighboring cells.
Advance
Parameters
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.
Issue 03 (2015-07-30)

359
Nastar
Parameter
Description
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
period
Interval between the ARFCNs of each group. The

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 215 minutes,
that is, 30 minutes.

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Issue 03 (2015-07-30)

360
Nastar
Parameter
Description
Select NE(s)

NOTE
Parameter
Description
Number of
undefined
neighboring cells
Displays the TopN undefined neighboring cells.
Co-channel
interference C/I
Indicates the threshold of co-channel interference.
N can be any integer from 20 to 999. The default value is 30.
This parameter can be set to any integer from 6 to 15. The default value
is 12.
Unit: dB
Adjacent-channel
interference C/A
Indicates the threshold of adjacent-channel interference.

This parameter can be set to any integer from -12 to 0. The default value
is -6.
Unit: dB
Max. distance for

checking for coBCCH co-BSIC
neighboring cell
(km)
Indicates the distance of the search for cells with the same BCCH
ARFCN and BSIC as the test cell.
Typical site
distance
Indicates the distance between typical base stations. The Nastar

calculates a threshold according to the distance, and filters analysis
results.
This parameter can be set to any flowing point number from 0.0 to 20.0.
The default value is 5.0.
Unit: km
The parameter can be set to any value from 0.1 to 35.0. The default
value is 0.5.
Unit: km
Issue 03 (2015-07-30)

361
Nastar
Parameter
Description
Duration
Delay
immediately.
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
4.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
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.
Select a finished GSM frequency analysis task, right-click a result of the task in the Task
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 4-8 and Figure 4-9.
Issue 03 (2015-07-30)

362
Nastar
Figure 4-8 Frequency analysis interface 1
Issue 03 (2015-07-30)

363
Nastar
N
o.
Name
Description
Button
area
Portals for five functions are provided:

l
: Exporting frequency analysis overview information is to export the

information about all the test cells involved in the selected analysis task.
: 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.
: 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.
: 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.
: Exporting analysis results of possible neighboring cells is to export

the information about possible neighboring cells of all test cells.
: 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 03 (2015-07-30)

364
Nastar
N
o.
Name
Description
Test Cell
Overvie
w
Informat
ion
Displays the information about all task-related test cells, the interference of
a test cell caused by co-channel or adjacent-channel neighboring cells and
the interference of co-channel or adjacent-channel neighboring cells caused
by a test cell.
Neighbo
ring
CellTest Cell
Interfere
nce
Matrix
Details
Displays the matrix detail affected by the interference from neighboring cells
of the test cell selected in Area 2 to the test cell. It provides the basis for
frequency optimization.
Test
CellNeighbo
ring Cell
Interfere
nce
Matrix
Details
Displays matrix details of the interference from the test cell selected in Area
2 to all the defined and undefined neighboring cells. It provides the basis for
The Nastar automatically sorts cells by interference and picks out targeted
cells, providing a basis of frequency analysis for test cells.
For details, see Parameters for Viewing GSM Frequency Analysis

Results.

Results.
Figure 4-9 Frequency analysis interface 2
Issue 03 (2015-07-30)

365
Nastar
N
o.
Name
Description
Frequency
Interference
Matrix
Displays the interference traffic between the test cell selected in the left
list and its neighboring cells with BCCH configuration by frequencies.
BCCH
Configured
Frequency
Cell List
Displays the interfered traffic between the test cell and its co-channel or
adjacent-channel neighboring cells when a frequency in Area 5 is selected
as the BCCH frequency of the test cell.

Results.

Results.
Interface Description: GSM Frequency Optimization

This section describes the interface for GSM frequency optimization. Before performing relevant
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 4-10.
Issue 03 (2015-07-30)

366
Nastar
Figure 4-10 GSM frequency optimization interface
Issue 03 (2015-07-30)

367
Nastar
No.
Name
Description
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.
: 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.
: 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.
Issue 03 (2015-07-30)
: 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.
: Export a frequency optimization result.

Set the file name, file type, and save path in the dialog box of
exporting a result.
: Analyze spectrum usage.

View the usage of current BCCH and TCH ARFCNs to improve the
spectrum usage.

368
Nastar
No.
Name
Description
l
: View interference comparison results before and after

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.
: 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
selection.
button to stop automatic ARFCN
Test cell
overview
information
Shows the information about all the test cells involved in the current
task.
BCCH and
TCH
information
Displays the BCCH and TCH frequency information about the selected
test cell in area 2.
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
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 03 (2015-07-30)

369
Nastar
No.
Name
Description
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.
Legends of
the
highlightin
g function
Displays information about ARFCNs that violate the co-cell, co-site,

or neighboring cell frequencies rules in different colors.
Algorithm
parameter
area
Displays the algorithm parameters set when frequency optimization is

queried. Rules for spacing between ARFCNs and VIP cell groups are
contained in this area.
For details of spacing rules of ARFCNs, see GSM ARFCN Spacing

Rules.
4.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.
Issue 03 (2015-07-30)

370
Nastar
Overview Report of the GSM Test Cells

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Name
1 to 32
characters
N/A
Indicates the
name of the
BSC that a test
cell belongs to,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Test Cell
1 to 64
characters
N/A
Indicates the
name of a test
cell, for
example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

371
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
MCC[000,999]
l SRAN8.1/
GBSS15.1/
RAN 15.1
MNC[00,99]
LAC[1,65533],
[65535]
CI[0,65535]
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

372
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900;
l SRAN8.1/
GBSS15.1/
RAN 15.1
0 to 124, 975 to
1023: belong to
E-GSM900;
l SRAN9.0/
GBSS16.0/
RAN16.0
0 to 124, 955 to
1023: belong to
R-GSM900;
l SRAN10.0/
GBSS17.0/
RAN17.0
512 to 885:
belong to
DCS1800;
l SRAN10.1/
GBSS17.1/
RAN17.1
512 to 810:
belong to
PCS1900;
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
Regulation: PGSM, E-GSM,
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to
GSM1800
layer.
Issue 03 (2015-07-30)

373
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BSIC
[0,77]
N/A
Indicates the
base station
identity code of
a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Consists of the
following parts:
NCC[0,7]
BCC[0,7]
BSIC=NCC*10
+BCC
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of CoBCCH
Neighboring
Cells (CoBCCH defined
neighbors and
Co-BCCH
defined
neighbors of
tested cell's
defined cells.)
[0,+)
Number
Total number of
co-BCCH
neighboring
cells = Number
of co-BCCH
neighboring
cells for the test
cell + Number
of co-BCCH
neighboring
cells for the
neighboring
cells
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

374
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Probable
Overlapped
Traffic
Interfered by
Co-BCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
number of MRs
received by the
test cell from the
neighboring
cells that share
the same BCCH
ARFCN with
the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlapped
Traffic
Interfered by
AdjacentBCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
number of MRs
received by the
test cell from the
neighboring
cells that have
neighboring
ARFCNs of the
BCCH ARFCN
of the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

375
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Probable
Overlapped
Traffic
Interfered on
Co-BCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
number of MRs
received by the
neighboring
cells that share
the same BCCH
ARFCN with
the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlapped
Traffic
Interfered on
AdjacentBCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
number of MRs
received by the
neighboring
cells that have
neighboring
ARFCNs of the
BCCH ARFCN
of the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

376
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Measurement
Reports on Test
Cell
[0,+)
Number
Indicates the
total number of
downlink MRs
received by the
test cell within
the
measurement
period.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proximate CoChannel
Neighboring
Cell Distance
[0,+)
km
Indicates the
distance from
the test cell to
the nearest intrafrequency
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

377
Nastar
Interference Matrix Details (Neighboring Cell to Test Cell)

Parameter
Range
Unit
Description
Supported
Solution
Version
Interference
Cell
1 to 64
characters
N/A
Indicates the
name of a cell
that causes
interference to
the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

378
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Interference
Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for an
interfering cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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;
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to
GSM1800
layer.
Issue 03 (2015-07-30)

379
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Interference
Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
an interfering
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Consists of the
following parts:
NCC[0,7]
BCC[0,7]
BSIC=NCC*10
+BCC
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell Property
Defined
neighboring
cell, Undefined
neighboring cell
N/A
Indicates the
attributes of an
interfering cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

380
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlapped
Traffic
[0,+)
N/A
Indicates the
number of MRs
received by the
test cell from the
intra-frequency
neighboring
cells and
adjacentchannel
neighboring
cells.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

381
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Overlapped
Traffic
Interfered by
Co-Channel
Neighboring
Cell on Test Cell
[0.00,100.00]
If the BCCH
ARFCN of the
test cell is set to
be the same as
that of a
neighboring
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 cochannel
neighboring cell
to the test cell/
Number of
reports
generated by the
test cell during
the
measurement
period x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
382
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Overlapped
Traffic
Interfered by
AdjacentChannel
Neighboring
Cell on Test Cell
[0.00,100.00]
If the BCCH of
the test cell is set
to the frequency
adjacent to the
BCCH of a
neighboring
cell, the value of
this parameter is
calculated
according to the
formula:
Percentage of
Overlapped
Traffic
Interfered by
Co-Channel
Neighboring
Cell on Test Cell
(%) = Traffic
affected by the
interference
from an
adjacentchannel
neighboring cell
to the test cell/
Number of
reports
generated by the
test cell during
measurement
period x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
383
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Probable
Overlapped
Traffic
Interfered by
Co-BCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
total traffic
affected by the
interference
from a
neighboring cell
to the test cell
when the BCCH
ARFCN of the
test cell is the
same as that of
the neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlapped
Traffic
Interfered by
AdjacentBCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
total traffic
affected by the
interference
from a
neighboring 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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

384
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance
[0,+)
km
Indicates the
distance from
the test cell to a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

385
Nastar
Interference Matrix Details (Test Cell to Neighboring Cell)

Parameter
Range
Unit
Description
Supported
Solution
Version
Interfered Cell
1 to 64
characters
N/A
Indicates the
name of a cell
interfered by the
test cell
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

386
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Interfered Cell
BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for an interfered
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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;
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to
GSM1800
layer.
Issue 03 (2015-07-30)

387
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Interfered Cell
BSIC
[0,77]
N/A
Indicates the
base station
identity code of
an interfered
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Consists of the
following parts:
NCC[0,7]
BCC[0,7]
BSIC=NCC*10
+BCC
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell Property
Defined
neighboring
cell, Undefined
neighboring cell
N/A
Indicates the
attributes of an
interfered cell,
such as Defined
Neighboring
Cell and
Undefined
Neighboring
Cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

388
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlapped
Traffic
[0,+)
N/A
Indicates the
number of MRs
received by the
intra-frequency
neighboring
cells and
adjacentchannel
neighboring
cells from the
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

389
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Overlapped
Traffic
Interfered by
Test Cell on CoChannel
Neighboring
Cell
[0.00,100.00]
If the BCCH
ARFCN of the
test cell is set to
be the same as
that of a
neighboring
cell, the value of
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 cochannel
neighboring
cell/Number of
reports
generated by the
test cell during
measurement
period x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
390
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Overlapped
Traffic
Interfered by
Test Cell on
AdjacentChannel
Neighboring
Cell
[0.00,100.00]
If the BCCH
ARFCN of the
test cell is set to
the frequency
adjacent to the
BCCH of a
neighboring
cell, the value of
this parameter is
calculated
according to the
formula:
Percentage of
AdjInterference
Traffic to
Neighbor(%) =
Traffic affected
by the
interference
from the test cell
to the adjacentchannel
neighboring
cell/Number of
reports
generated by the
test cell during
measurement
period x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
391
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Probable
Overlapped
Traffic
Interfered on
Co-BCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
total traffic
affected by the
interference
from the test cell
to a neighboring
cell when the
BCCH ARFCN
of the test cell is
the same as that
of the
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlapped
Traffic
Interfered on
AdjacentBCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
total traffic
affected by the
interference
from the test cell
to a neighboring
cell when the
BCCH ARFCN
of the test cell is
a neighboring
ARFCN for the
BCCH ARFCN
of the
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

392
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance
[0,+)
km
Indicates the
distance from
the test cell to an
interfered cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

393
Nastar
Frequency Interference Matrix

Parameter
Range
Unit
Description
Supported
Solution
Version
BCCH
[0,1023]
N/A
Indicates the
BCCH
ARFCNs of the
defined and
undefined
neighboring
cells of the test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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;
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
512 to 810:
belong to
PCS1900;
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to
Issue 03 (2015-07-30)

394
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
GSM1800
layer.
Traffic of Test
Cell Caused by
Neighboring
Cell
Interference
Traffic of
Neighboring
Cell Caused by
Test Cell
Interference
Issue 03 (2015-07-30)
[0,+)
[0,+)
N/A
N/A
If this ARFCN
of the test cell is
set to the BCCH
ARFCN, the
value of this
parameter is the
total volume of
the interfered
traffic of the test
cell. The
interfered traffic
is caused by the
co-channel and
adjacentchannel
neighboring
cells for the test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If this ARFCN
of the test cell is
set to the BCCH
ARFCN, the
value of this
parameter is the
total volume of
the interfered
traffic of the cochannel and
adjacentchannel
neighboring
cells. The
interfered traffic
is caused by the
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
395
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proximate CoChannel
Neighboring
Cell Distance
[0,+)
km
If this ARFCN
of the test cell is
set to the BCCH
ARFCN, the
value of this
parameter is the
distance from
the test cell to
the nearest intrafrequency
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

396
Nastar
Cell List with BCCH Configured As This ARFCN

Parameter
Range
Unit
Description
Supported
Solution
Version
Interference
Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for an
interfering cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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;
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to
GSM1800
layer.
Issue 03 (2015-07-30)

397
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Interference
Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
an interfering
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Consists of the
following parts:
NCC[0,7]
BCC[0,7]
BSIC=NCC*10
+BCC
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Interference
Cell ID.
[0 to 2047]
N/A
Indicates the
number of an
interfering cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

398
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Interference
Cell Name
1 to 64
characters
N/A
Indicates the
name of a cell
that causes
interference to
the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell Property
Defined
neighboring
cell, Undefined
neighboring cell
N/A
Indicates the
attributes of an
interfering cell,
such as Defined
Neighboring
Cell and
Undefined
Neighboring
Cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

399
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Overlapped
Traffic
Interfered by
Co-Channel
Neighboring
Cell on Test Cell
[0.00,100.00]
If the BCCH
ARFCN of the
test cell is the
same as that of a
neighboring
cell, the value of
this parameter is
calculated
according to the
formula: Value
= Traffic
affected by the
interference
from the cochannel
neighboring cell
to the test cell/
Number of
reports
generated by the
test cell during
the
measurement
period x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
400
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Overlapped
Traffic
Interfered by
AdjacentChannel
Neighboring
Cell on Test Cell
[0.00,100.00]
If the BCCH
ARFCN of the
test cell is set to
a neighboring
ARFCN for the
BCCH ARFCN
of a neighboring
cell, the value of
this parameter is
calculated
according to the
formula: Value
= Traffic
affected by the
interference
from the
adjacentchannel
neighboring cell
to the test cell/
Number of
reports
generated by the
test cell during
the
measurement
period x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
401
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Probable
Overlapped
Traffic
Interfered by
Co-BCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
total traffic
affected by the
interference
from a
neighboring cell
to the test cell
when the BCCH
ARFCN of the
test cell is the
same as that of
the neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlapped
Traffic
Interfered by
AdjacentBCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
total traffic
affected by the
interference
from a
neighboring 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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

402
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Overlapped
Traffic
Interfered by
Test Cell on CoChannel
Neighboring
Cell
[0.00,100.00]
If the BCCH of
the test cell is set
to be the same as
that of a
neighboring
cell, the value of
this parameter is
calculated
according to the
formula: Value
= Traffic
affected by the
interference
from the test cell
to the cochannel
neighboring
cell/Number of
reports
generated by the
test cell during
the
measurement
period x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
403
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Overlapped
Traffic
Interfered by
Test Cell on
AdjacentChannel
Neighboring
Cell
[0.00,100.00]
If the BCCH
ARFCN of the
test cell is set to
a neighboring
ARFCN for the
BCCH ARFCN
of a neighboring
cell, the value of
this parameter is
calculated
according to the
formula: Value
= Traffic
affected by the
interference
from the test cell
to the adjacentchannel
neighboring
cell/Number of
reports
generated by the
test cell during
the
measurement
period x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
total traffic
affected by the
interference
from the test cell
to a neighboring
cell when the
BCCH ARFCN
of the test cell is
the same as that
of the
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Probable
Overlapped
Traffic
Interfered on
Co-BCCH
Neighboring
Cell
[0,+)
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

404
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlapped
Traffic
Interfered on
AdjacentBCCH
Neighboring
Cell
[0,+)
N/A
Indicates the
total traffic
affected by the
interference
from the test cell
to a neighboring
cell when the
BCCH ARFCN
of the test cell is
a neighboring
ARFCN for the
BCCH ARFCN
of the
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance
[0,+)
km
Indicates the
distance from
the test cell to a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

405
Nastar
Current Measurement Cell

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Name
1 to 32
characters
N/A
Indicates the
name of the
BSC that a test
cell belongs to,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of a test
cell, for
example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

406
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900;
l SRAN8.1/
GBSS15.1/
RAN 15.1
0 to 124, 975 to
1023: belong to
E-GSM900;
l SRAN9.0/
GBSS16.0/
RAN16.0
0 to 124, 955 to
1023: belong to
R-GSM900;
l SRAN10.0/
GBSS17.0/
RAN17.0
512 to 885:
belong to
DCS1800;
l SRAN10.1/
GBSS17.1/
RAN17.1
512 to 810:
belong to
PCS1900;
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450;
306 to 340:
belong to
GSM480;
128 to 251:
belong to
GSM850;
R-GSM,
GSM450,
GSM480,
GSM850 is
belong to
GSM900 layer;
DCS1800,
PCS1900 is
belong to
GSM1800
layer.
Issue 03 (2015-07-30)

407
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
LAC
[1,65533],
[65535]
N/A
Indicates the
location area
code of the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CI
[0,65535]
N/A
Indicates the
identification
code of the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

408
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCH
N/A
N/A
Indicates traffic
channels for the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
Measurement
Reports on Test
Cell
[0,+)
Number
Indicates total
number of MRs
on the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

409
Nastar
BCCH/TCH ARFCNs
Parameter
Range
Unit
Description
Supported
Solution
Version
Configured
Yes, No
N/A
Indicates
whether the
current ARFCN
is configured as
the BCCH
ARFCN or a
TCH ARCFN of
the selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
ARFCN
N/A
N/A
Indicates the
configured and
candidate
BCCH
ARFCNs and
TCH ARFCNs
of the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

410
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell with the

Strongest
Interference
N/A
N/A
Indicates the
name of the cell
that has the
strongest
interference
over the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

411
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Measured
Yes, No
N/A
Indicates
whether the cell
with the
strongest
interference
over the test cell
is within the
interference
matrix, that is,
whether the cell
with the
strongest
interference is
measured.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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
Issue 03 (2015-07-30)

412
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
such a case,
External
Interference
Traffic of this
ARFCN is
unreliable.
Maximum
Interfered
Traffic
[0,+)
N/A
Indicates the
maximum
interference
traffic received
by the test cell
when the BCCH
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the current
candidate
ARFCN.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Interfered
Traffic
[0,+)
N/A
Indicates the
total
interference
traffic received
from and caused
to other cells
when the BCCH
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the current
candidate
ARFCN.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

413
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Interfered
Traffic
[0,+)
N/A
Indicates the
total
interference
traffic received
from other cells
when the
BCCH/TCH of
the test cell is
configured as
the current
candidate
ARFCN.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
External
Interfered
Traffic
[0,+)
N/A
Indicates the
total
interference
traffic caused to
other cells when
the BCCH
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the current
candidate
ARFCN.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

414
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Interfered
Traffic to VIP
Cells
[0,+)
N/A
Indicates the
total
interference
traffic caused to
other VIP cells
when the BCCH
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the current
candidate
ARFCN.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Latest Total
Interfered
Traffic
Issue 03 (2015-07-30)
[0,+)
N/A
Indicates the
total
interference
traffic received
from and caused
to other cells
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.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
415
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Original Total
Interfered
Traffic
[0,+)
N/A
Indicates the
total
interference
traffic received
from and caused
to other cells
when the BCCH
ARFCN or a
TCH ARFCN of
the test cell is
configured as
the ARFCN of
the live
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
4.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,
problems due to redundant neighboring GSM cells, missing neighboring GSM cells, or incorrect
priorities.
4.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.
NOTE
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.
Issue 03 (2015-07-30)

416
Nastar
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
cells and undefined neighboring GSM cells. Figure 4-11 shows the process of measuring the
ARFCNs in the BA2 list.
Figure 4-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
Issue 03 (2015-07-30)

417
Nastar
neighboring GSM cells, and defined and undefined neighboring GSM cells in different colors.
This helps you query neighboring relationships.
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 4-12 shows the principles for collecting, importing, and analyzing data on the Nastar.
For detailed operations, see Table 4-10.
NOTE
Issue 03 (2015-07-30)

418
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
applicat
ion data
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U
To request the U2000/M2000 to filter out the

data that meets the Nastar's requirements. After a user
enables the application data subscription function on the
Nastar client, the Nastar issues an application data

419
Nastar
User
Operat
ion
Issue 03 (2015-07-30)
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Collect
perform
ance
data and
neighbo
ring cell
measure
ment
data
eS
AU
U20
00/
M20
00

data that meets the Nastar's requirements.
Upload
perform
ance
data and
neighbo
ring cell
measure
ment
data
U2
000
/
M2
000
eSA
U
To upload the performance data and neighboring cell

measurement data that meets the Nastar's requirements
to the eSAU.
2.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

3.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
4. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er

420
Nastar
NOTE
Network Requirements
During raw data collection, the network must be stable. Otherwise, the accuracy of GSM
neighboring cell analysis will be affected. Table 4-11 lists the network changes and their
respective impacts.
Network Change
Impacts


antenna

as discontinuous
control.
Adjusting frequency

Adjusting handover
relationship and
handover parameters

Adjusting the BSC

topology or other
network topology

Technical Specifications for GSM Neighboring Cell Analysis

of analysis time.
Issue 03 (2015-07-30)

421
Nastar
NOTE
Item
Execution type
One-time task

analysis task
<= 10,000 cells
Number of allowed
analysis tasks
<= 50

one analysis task
7 days

task
<= 10 minutes

15 days

15 days
4.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.
Ensure that you have the operation rights to subscribe to GSM neighboring cell analysis
data upon login.
Ensure that your user account is authorized to create GSM neighboring cell analysis tasks,

Configuration Data
Issue 03 (2015-07-30)

422
Nastar
Data.
Engineering parameter data
The engineering parameters in the analysis area include the cell longitude and latitude and the
antenna azimuth. The information is used for effectively identifying serving cells and possible
neighboring cells and geographically displaying the 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 3.4.4
Preparing the Map File (Optional).
Checking Network Environment

l
data and the BSC has the license for using the function 2G/3G neighboring cell autooptimization. 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
(RH2288).
Issue 03 (2015-07-30)

423
Nastar
4.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
Procedure
Prerequisites
database. For details, see 4.3.2 Preparations for GSM Neighboring Cell Analysis.
Procedure
Issue 03 (2015-07-30)

424
Nastar
Table 4-12 Process of GSM neighboring cell analysis

No.
Step
Description
Details
(1)
Check
GSM
Neighbo
ring Cell
analysis
data

3.6
Checking
the Integrity
of Analysis
Data
Procedure:
1. Choose Data Type > Basic Network Optimization
> 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.
performing (2).
NOTE
administrator with subscription rights to perform the
subscription operation.
Issue 03 (2015-07-30)

425
Nastar
No.
Step
Description
Details
(2)
Subscrib
e to the
GSM
neighbor
ing cell
analysis
data
(applicat
ion)
NOTE
When a neighboring cell measurement task is being performed,
the BA2 table does not automatically update. Ensure frequency
stability of measured cells and their neighboring cells.
Otherwise, errors may occur during cell handover and
measurement data may not be accurate.
3.5
Subscribing
to Analysis
Data

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 .
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.
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 03 (2015-07-30)

426
Nastar
No.
Step
Description
Details
Check
GSM
Neighbo
ring Cell
analysis
data

3.6
Checking
the Integrity
of Analysis
Data
Procedure:
1. Choose Data Type > Basic Network Optimization
> GSM Neighboring Cell Analysis Data.
3. Select one or multiple NEs.
4. Click Query.
window.
analysis task.
l If the analysis data does not exist, contact Huawei
technical support.
(3)
Create a
GSM
neighbor
ing cell
analysis
task
Navigation path: In the Analysis Task Management

window, choose Theme Function > Basic Network
Optimization > GSM Neighboring Cell Analysis
Task from the navigation tree.
3.7 Creating
an Analysis
Task
Procedure:
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 03 (2015-07-30)

427
Nastar
No.
Step
Description
Details
(4)
View
GSM
neighbor
ing cell
analysis
results
Function: By viewing the check result of neighboring

GSM cells, you can learn the redundant or missing
configuration of the neighboring cells. This helps you
configure missing neighboring cells and delete redundant
neighboring cells.
3.8
Querying
Analysis
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
GSM
possible
neighbor
ing cell
analysis
results
Function: By viewing the analysis results of possible

neighboring GSM cells, you can quickly learn all possible
neighboring GSM cells and optimize neighbor
relationships based on the 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:
2. In the GSM Possible Neighboring Cell Analysis
dialog box, view the GSM possible neighboring cell
analysis results.
Description: Possible GSM Neighboring Cell
Analysis.
Issue 03 (2015-07-30)

428
Nastar
No.
Step
Description
(6)
View
GSM
CoBCCH
and CoBSIC
Neighbo
ring Cell
Analysis
Results
Function: This function allows you to check whether the

selected cell has co-BCCH and co-BSIC neighboring
cells within all the cells having neighbor relationships
with the selected cell or within the cells that are physically
adjacent to the selected cell. Then, you can determine
whether to modify the BCCH or BSIC frequency
information about the selected cell based on the check
result.
Details

Procedure:
2. In the Co-BCCH and Co-BSIC Check Result dialog
box, view the GSM possible neighboring cell analysis
results.
Description: GSM Intra-Frequency Co-BSIC Cell
Analysis.
(7)
GSM
IntraFrequen
cy
Neighbo
ring Cell
Analysis
Results
Function: This function allows you to check whether the

selected cell has co-BCCH cells within all the
neighboring cells of the selected cell. Then, you can
determine whether to modify the BCCH frequency
information about the selected cell based on the check
result.
Procedure:
2. In the Neighboring Cells Co-BCCH Analysis
Result dialog box, view the GSM possible
neighboring cell analysis results.
Description: GSM Intra-Frequency Neighboring
Cell Analysis.
Issue 03 (2015-07-30)

429
Nastar
No.
Step
Description
Details
(8)
Export
Neighbo
ring Cell
Analysis
reports
Navigation path: Click the icon on the toolbar in the

upper left part of each analysis results window.
3.10
Exporting
Analysis
Reports
Procedure:
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.

Parameter
Description
Task Name

Value range:
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.
Time Setting
Start Time
Indicates the time when the task starts to run.

The start time must be later than the current time. By
default, the start time is five minutes later than the
current system time.
Cycle Setting
Cycle
Indicates the interval between periodic tasks. This

parameter involves the period unit and the interval.
Interval: 1 to 65535.
Execute Times
Indicates the times that a periodic task is executed.

If this parameter is set to 0, you can infer that the task
is executed all the time.
Value range: 0 to 3650.
Issue 03 (2015-07-30)

430
Nastar
Parameter
Description

an analysis task to SAUs and delivers data source
switches to the NEs when users deliver an
application data subscription task.
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.
Measurement
Task
Measurement step
Indicates the number of ARFCNs in the same group.

The value is an integer from 1 to 31, including 1 and
31.
NOTE
The measurement duration (Number of ARFCNs/
Measurement step x Measurement period) is less than or
equal to 24 hours. If the number of ARFCNs is not an
integer multiple of the measurement step, the value of
Number of ARFCNs/Measurement step must be rounded
up. For example, the value of [5/2] is 3.
Cell Object
Indicates the cell involved in the neighboring cell

measurement task. The cell is displayed in the format
of Cell ID+Cell name+BA2 table length.
NOTICE
It is recommended that the number of measured cells
delivered by each BSC do not exceed 200. If the number
exceeds 200, the data about some cells cannot be reported
completely. The maximum number of measured cells is
400.
Issue 03 (2015-07-30)

431
Nastar
Parameter
Description
Selected Frequency
You need to collect the frequencies that you want to

measure. This ensures that all signal strength values
of the neighboring cells of a cell can be measured in
order to identify possible missing neighboring cells.
Frequencies are managed by group, and the number
of frequencies in each group is determined by the
value of Measure Step.
NOTE
l You can select a maximum of 762 ARFCNs for a cell.
If the number exceeds 762, the NE returns an error
message after the corresponding MML command is
executed, indicating that the task creation or
modification fails.
l Before setting this parameter, you must set Measure
Step. The selected ARFCNs are grouped by Measure
Step. For example, if Measure Step is set to 2 and the
ARFCNs 59, 60, and 61 are selected, the ARFCNs are
organized into two groups. One group consists of
ARFCNs 59 and 60, and the other group consists of
ARFCN 61.
The U2000/M2000 measures the ARFCN groups in
turn during the measurement period. You can also
change the value of Measure Step to reorganize the
ARFCNs after setting the ARFCNs.
Search
Recommended
ARFCNs
Click Search Recommended ARFCNs. The Nastar

traverses the three-level neighboring cells of the
selected cell. Then, the Nastar analyzes the BCCH
ARFCNs of the traversed neighboring cells and
highlights these BCCH ARFCNs in the frequency
selection area in gray to provide reference for
selecting measurement ARFCNs.
Traversing of the three-level neighboring cells
indicates that the Nastar searches for the neighboring
cell (neighboring cell A) of the selected cell, the
neighboring cell (neighboring cells B) of
neighboring cell A, and the neighboring cell
(neighboring cells C) of neighboring cell B. All
traversed neighboring cells A, B, and C are
neighboring cells obtained through the traversing of
the three-level neighboring cells.
Advance
Parameters
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.
Issue 03 (2015-07-30)

432
Nastar
Parameter
Description
Duration

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
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 215 minutes,
that is, 30 minutes.

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Issue 03 (2015-07-30)

433
Nastar
Parameter
Description
Select NE(s)

NOTE
Parameter Setting Information

Parameter
Missing
Neighboring
Cell
Parameters
Description
Neighboring
cell ranking
number
Indicates the lower threshold of the neighboring cell

sequence. All the undefined neighboring cells whose
sequence numbers are smaller than or equal to the value of
this parameter are regarded as missing neighboring cells.
This parameter can be set to any integer from 1 to 32. The
Redundant
Neighboring
Cell
Parameters
BA2 table
length limit
Indicates the limitation on the number of test ARFCNs of

neighboring cells.
Neighboring
cell table
length limit
Indicates the limitation on the number of neighboring cells.

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
Parameters
Display the
number of
undefined
neighboring
cells
Indicates that only the TopN undefined neighboring cells are

displayed.
Other
Parameter
Settings
Superdistance
threshold
Specifies the threshold for the distance to a super-far

neighboring cell.
The value of this parameter ranges from 0 to 50000 (unit:

meter). The default value of this parameter is 5000.
Issue 03 (2015-07-30)

434
Nastar
Parameter
Description
Duration
Delay
immediately.
Busy hours
Execute on
4.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
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 4-14.
Issue 03 (2015-07-30)

435
Nastar
Figure 4-14 Interface for GSM neighboring cell analysis
No
.
Area
Description
List of test
cells
Lists the information about each test cell. You can press Ctrl+F to search
in the list, or right-click in the list and choose Save As from the shortcut
menu to save the list.
column header and choose a filtering item from the drop-down box to
display the table in a filtered way; click the
the table in the descending order.
List of
defined
neighborin
g GSM
cells
column header to display
Lists all defined neighboring GSM cells of all test cells in the list of test
cells.
l Select the User Modify check box of a defined neighboring GSM
cell. The system automatically saves the modification and reads the
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 03 (2015-07-30)

436
Nastar
No
.
Area
Description
List of
undefined
neighborin
g GSM
cells
Lists all undefined neighboring GSM cells of all test cells in the list of
test cells.
Chart area
Shows the information about all neighboring GSM cells of all test cells
in a bar+line chart.
The operations in this area are the same as those in area 2.
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 03 (2015-07-30)

437
Nastar
No
.
Area
Description
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.
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.
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.
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 4-15 shows this interface.
Issue 03 (2015-07-30)

438
Nastar
Figure 4-15 Map interface for GSM GSM neighboring cell analysis results
No.
Name
Description
Button area
Displays all the buttons for performing basic operations on the map
interface. For the meanings of these buttons, see 3.2.3 Interface
Description: Geographic Observation Results.
Navigation
tree
Site Layer: When an RAT is selected, site information of the selected

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
display area
After you select a cell in the neighboring cell analysis results, the map
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.
Legend area
This area is not displayed by default. It is displayed only after you

click
Issue 03 (2015-07-30)
Information
area
in the button area.
Displays information such as names and engineering parameters of

the selected cell. If no engineering parameter has been imported for
this cell, a message is displayed in this area.

439
Nastar
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 4-16.
Figure 4-16 Window for analyzing possible neighboring GSM cells
Issue 03 (2015-07-30)
No
.
Area
Button
area
Description
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.
440
Nastar
No
.
Area
Description
Summary
of possible
neighborin
g GSM
cell
analysis
results
Lists the summary of the possible neighboring GSM cells of all cells
involved in the analysis task.
Confirmati
on list of
possible
neighborin
g GSM
cells
Lists all the possible neighboring GSM cells of selected cells in area 2.
display the table in a filtered way; click the column header to display
the table in the descending order. You can also press Ctrl+F to search in
the area.
l Button area:
is used to add possible neighboring GSM cells for
the serving cell. The procedure is as follows:
Select a cell in area 2, and click this button. The GSM Possible
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
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:
Task Result area, and choose Co-BCCH & Co-BSIC Checking from the shortcut menu.
Issue 03 (2015-07-30)

441
Nastar
Main Window
Nastar shows the list of intra-frequency co-BSIC GSM cells in the main window, as shown in
Figure 4-17.
Figure 4-17 GSM Intra-frequency co-BSIC cell analysis Interface
Figure 4-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.
column header and choose
a filtering item from the drop-down box to display the table in a filtered way; click the
header to display the table in the descending order.
column
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 03 (2015-07-30)

442
Nastar
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 4-18.
Figure 4-18 GSM intra-frequency neighboring cell analysis Interface
Figure 4-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.
column header and choose
a filtering item from the drop-down box to display the table in a filtered way; click the
column
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.
4.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
Issue 03 (2015-07-30)

443
Nastar
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
Solution
Version
BSC Where
Test Cell Is
Located
1 to 32
characters
N/A
Indicates the
name of the
BSC that a test
cell belongs to,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Test Cell Name
1 to 64
characters
N/A
Indicates the
name of a test
cell, for
example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

444
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
total number of
MRs received
by a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Configured
Neighboring
Cells
[0,64]
Number
Indicates the
number of
neighboring
cells defined for
a specified cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

445
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Redundant
Neighboring
Cells
[0,+)
Number
Indicates the
number of
redundant
neighboring
cells for the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of Not
Configured
Neighboring
Cells
[0,+)
Number
Indicates the
number of
missing
neighboring
cells for the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

446
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Measurement
Report on Not
Configured
Neighboring
Cells
[0.00,100.00]
Indicates the
sum of the
integrated
priority
percentages of
all missing
neighboring
cells for the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
LAC
[1,65533],
[65535]
N/A
Indicates the
location area
code of the
selected test
cell.
LAC is a part of
CGI and
uniquely
identifies a
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

447
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CI
[0,65535]
N/A
Indicates the
identification
code of the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

448
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to GSM
450.
306 to 340:
belong to GSM
480.
128 to 251:
belong to GSM
850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

449
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BSIC
[0,77]
N/A
Indicates the
base station
identity code of
the selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Test Cell ID
[0 to 2047]
N/A
Indicates the ID
of the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

450
Nastar
Defined Neighboring Cell

Parameter
Range
Unit
Description
Supported
Solution
Version
Defined
Neighboring
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
defined
neighboring cell
for the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
neighboring
cell.
MCC [000,999]
MNC [00,99]
LAC [0,65535]
CI [0,65535]
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

451
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900.
l SRAN9.0/
GBSS16.0/
RAN16.0
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to GSM
450.
306 to 340:
belong to GSM
480.
128 to 251:
belong to GSM
850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

452
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
the selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service Type of
Neighboring
Cell
Issue 03 (2015-07-30)
Indoor, Outdoor
or null
N/A
Indicates the
service type
provided by a
GSM
neighboring
cell, including
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.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
453
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Suggested
Operation
"Defined
Neighboring
Cell
(Reserved)" or
"Defined
Neighboring
Cell
(Redundant)"
N/A
Indicates the
operation
suggestions on a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
One-Way/TwoWay
"One-Way",
"Two-Way",
"Unknown"
N/A
Field for
identifying a
unidirectional
or bidirectional
neighbor
relationship
based on
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

454
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
User Modify
N/A
N/A
Field for
identifying data
that users can
modify. Each of
such data
records contains
this field after
being exported.
Users can
change this field
as required.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Handover
Requests
[0,+)
Number
Indicates the
number of
handover
requests from
the current
serving cell to
another cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

455
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Handover
Failure
[0,+)
Number
Indicates the
number of
handover
failures among
all handover
requests from
the current
serving cell to
another cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Handover
Success Rate
Issue 03 (2015-07-30)
[0.00,100.00]
Indicates the
handover
success rate
from the current
serving cell to
another cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Outgoing cell
handover
success rate =
Number of
successful
outgoing cell
handovers/
Number of
outgoing cell
handover
requests x 100%
l SRAN9.0/
GBSS16.0/
RAN16.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
456
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Relative
Percentage
[0.00,100.00]
Indicates the
proportion of
the total
handover
attempts from
the current
serving cell to a
neighboring cell
to the total
handover
attempts from
the current
serving cell to
any neighboring
cells.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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%
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
457
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Integrated
Priority
[0.00,100.00]
Indicates the
percentage of
the total number
of MRs related
to a test cell to
the number of
MRs related to
the neighboring
cell level that is
higher than the
relative level
and the absolute
level.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Integrity
Priority TH =
Number of MRs
related to the
neighboring cell
level that is
higher than the
relative level
and the absolute
level/Total
number of MRs
related to a test
cell x 100%
l SRAN10.1/
GBSS17.1/
RAN17.1
Indicates the
sequence
number of a
neighboring cell
among all
neighboring
cells for the
selected test cell
according to its
integrated
priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Priority
[0,+)
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

458
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance
[0,+)
km
Indicates the
distance from
the selected test
cell to a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Co-Site
Yes, No
N/A
Field for
determining
whether a
neighboring cell
shares the same
site with a
specified cell
based on certain
algorithms.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

459
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Super-Distance
Yes, No or null
N/A
Indicates that
the distance
between a
specified cell
and its
neighboring cell
exceeds a
predefined
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
In BA Time
[1,+)
minute
Indicates the
duration for
measuring a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

460
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Neighboring
Cell
Measurement
Reports
[0,+)
Number
Indicates the
total number of
MRs of a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Measurement
Reports of This
Frequency in
BA Time
[0,+)
Number
Indicates the
total number of
measurement
reports (MRs)
where a
frequency is
found to be
available in the
BA table during
frequency
polling in the
serving cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

461
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Source Cell
Signal Strength
N/A
dBm
Indicates the
average signal
strength of the
selected test cell
that serves as the
source handover
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell Signal
Strength
N/A
dBm
Indicates the
average signal
strength of a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

462
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Mean S-N
Difference
N/A
dB
Indicates the
average
difference
between the
signal strength
of the selected
test cell serving
as the source
handover cell
and the signal
strength of a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Relative TH
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
related to the
information that
the value of
Mean S-N
Difference is
greater than the
relative level
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

463
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Absolute TH
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
containing
information that
the signal
strength of a
neighboring cell
is greater than
the absolute
level threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

464
Nastar
Undefined Neighboring Cell

Parameter
Range
Unit
Description
Supported
Solution
Version
Undefined
Neighboring
Cell Name
1 to 64
characters
N/A
Indicates the
name of an
undefined
neighboring cell
for the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
neighboring
cell.
MCC [000,999]
MNC [00,99]
LAC [0,65535]
CI [0,65535]
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

465
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900.
l SRAN9.0/
GBSS16.0/
RAN16.0
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to GSM
450.
306 to 340:
belong to GSM
480.
128 to 251:
belong to GSM
850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

466
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
the selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service Type of
Neighboring
Cell
Issue 03 (2015-07-30)
Indoor, Outdoor
or null
N/A
Indicates the
service type
provided by a
GSM
neighboring
cell, including
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.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
467
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Suggested
Operation
"Undefined
Neighboring
Cell (Missing)"
or "Undefined
Neighboring
Cell (NonOperation)"
N/A
Indicates the
operation
suggestions on a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
One-Way/TwoWay
"One-Way",
"Unknown", "-"
N/A
Field for
identifying
neighbor
relationship
based on
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

468
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
User Modify
N/A
N/A
Field for
identifying data
that users can
modify. Each of
such data
records contains
this field after
being exported.
Users can
change this field
as required.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Percentage of
Integrated
Priority
[0.00,100.00]
Indicates the
integrated
priority of a
neighboring
cell, that is, the
percentage of
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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

469
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Priority
[0,+)
N/A
Indicates the
sequence
number of a
neighboring cell
among all
neighboring
cells for the
selected test cell
according to its
integrated
priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance
[0,+)
km
Indicates the
distance from
the selected test
cell to a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

470
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Co-Site
Yes, No
N/A
Field for
determining
whether a
neighboring cell
shares the same
site with a
specified cell
based on certain
algorithms.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Super-Distance
Yes, No or null
N/A
Indicates that
the distance
between a
specified cell
and its
neighboring cell
exceeds a
predefined
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

471
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
In BA Time
[0,+)
minute
Indicates the
duration for
measuring a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Neighboring
Cell
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
related to a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

472
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total
Measurement
Reports of This
Frequency in
BA Time
[0,+)
Number
Indicates the
total number of
measurement
reports (MRs)
where a
frequency is
found to be
available in the
BA table during
frequency
polling in the
serving cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Source Cell
Signal Strength
N/A
dBm
Indicates the
average signal
strength of the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

473
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell Signal
Strength
N/A
dBm
Indicates the
average signal
strength of a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Mean S-N
Difference
N/A
dB
Indicates the
average
difference
between the
signal strength
of the selected
test cell and the
signal strength
of a neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

474
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Relative TH
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
containing
information that
the difference
between the
signal strength
of a neighboring
cell and the
signal strength
of the test cell is
greater than the
relative level
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Absolute TH
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
containing the
signal strength
of neighboring
cells greater
than the
absolute level
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

475
Nastar
Possible Neighboring Cell Overview Table

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Where
Test Cell Is
Located
1 to 32
characters
N/A
Indicates the
name of the
BSC that a test
cell belongs to,
for example,
ERM3H201.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Test Cell Name
1 to 64
characters
N/A
Indicates the
name of the test
serving cell, for
example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

476
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for a test
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900.
l SRAN9.0/
GBSS16.0/
RAN16.0
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

477
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Test Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
test cell, for
example,
286-01-33034-5
0712.
l SRAN8.0/
GBSS15.0/
RAN 15.0
MCC[000,999]
l SRAN9.0/
GBSS16.0/
RAN16.0
MNC[00,99]
LAC[0,65535]
CI[0,65535]
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

478
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for a test
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900.
l SRAN9.0/
GBSS16.0/
RAN16.0
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

479
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
a test
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of the
selected
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
MCC[000,999]
l SRAN9.0/
GBSS16.0/
RAN16.0
MNC[00,99]
LAC[0,65535]
CI[0,65535]
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

480
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BSC of Selected
Neighboring
Cell
1 to 32
characters
N/A
Indicates the
name of the
BSC that the
selected
possible
neighboring cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell Name
1 to 64
characters
N/A
Indicates the
name of the
selected
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

481
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance
[0,+)
km
Indicates the
distance from
the test cell to
the selected
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Possible
Neighboring
Cell Laps
2,3,9
N/A
Indicates the
number of laps
between the
selected
possible
neighboring cell
and the test cell,
that is, the
number of cells
between the
selected
possible
neighboring cell
and the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

482
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Angle of
Neighboring
Cell Direction
[0,360]
Indicates the
relative angle
between the
selected
possible
neighboring cell
and the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Predicted Signal
Strength of
Neighboring
Cell
N/A
dBm
Indicates the
signal strength
of the selected
possible
neighboring cell
based on the
dimensioning.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

483
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Get from Config

Data
Yes, No
N/A
Indicates
whether the
selected
possible
neighboring cell
is obtained from
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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
number of
possible
neighboring
cells.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of
Possible
Neighboring
Cells
[0,+)
Number
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

484
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Percentage of
Integrated
Priority
[0.00,100.00]
Indicates the
percentage of
integrated
priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Priority
[0,+)
N/A
Indicates the
sequence
number of a
possible
neighboring cell
among all
possible
neighboring
cells for the
selected test cell
according to its
integrated
priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

485
Nastar
Possible Neighboring Cell Confirmation Table

Parameter
Range
Unit
Description
Supported
Solution
Version
Whether to Use
N/A
N/A
Indicates
whether to
select the
current possible
neighboring cell
as the most
possible
neighboring cell
for the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Possible
Neighboring
Cell CGI
replaces
Neighboring
Cell CGI.
Possible
Neighboring
Cell BSC Name
replaces
Neighboring
BSC.
Issue 03 (2015-07-30)

486
Nastar
Parameter
Range
Unit
Description
Supported
Solution
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
Issue 03 (2015-07-30)

487
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
is not
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
Issue 03 (2015-07-30)

488
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Possible
Neighboring
Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
MCC[000,999]
MNC[00,99]
LAC[0,65535]
CI[0,65535]
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC of Possible
Neighboring
Cell
1 to 32
characters
N/A
Indicates the
name of the
BSC that a
possible
neighboring cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

489
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Name of
Possible
Neighboring
Cell
1 to 64
characters
N/A
Indicates the
name of a
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance of
Possible
Neighboring
Cell
[0,+)
km
Indicates the
distance from
the test cell to a
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

490
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Possible
Neighboring
Cell Laps
2,3,9
N/A
Indicates the
number of laps
between the test
cell and a
possible
neighboring
cell, that is, the
number of cells
between the test
cell and a
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Relative Angle
of Possible
Neighboring
Cell
[0,360]
Indicates the
relative angle
between the test
cell and a
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

491
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Predicted Signal
Strength of
Possible
Neighboring
Cell
N/A
dBm
Indicates the
signal strength
of a possible
neighboring cell
based on the
dimensioning.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Get from Config

Data
Issue 03 (2015-07-30)
Yes, No
N/A
Indicates
whether
possible
neighboring
cells are
obtained from
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.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
492
Nastar
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 CoBSIC Neighboring Cell Analysis results.
Parameter
Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Where
Test Cell Is
Located
1 to 32
characters
N/A
Indicates the
name of the
BSC that a test
cell belongs to,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

493
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell Name
1 to 64
characters
N/A
Indicates the
name of a test
cell, for
example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Test Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
neighboring cell
for the selected
test cell.
MCC[000,999]
MNC[00,99]
LAC[0,65535]
CI[0,65535]
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

494
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900.
l SRAN8.1/
GBSS15.1/
RAN 15.1
0 to 124, 975 to
1023: belong to
E-GSM 900.
l SRAN9.0/
GBSS16.0/
RAN16.0
0 to 124, 955 to
1023: belong to
R-GSM 900.
l SRAN10.0/
GBSS17.0/
RAN17.0
512 to 885:
belong to
DCS1800
l SRAN10.1/
GBSS17.1/
RAN17.1
512 to 810:
belong to
PCS1900.
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

495
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
neighboring cell
for the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

496
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
neighboring cell
for the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
MCC[000,999]
MNC[00,99]
LAC[0,65535]
CI[0,65535]
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Angle of
Neighboring
Cell Direction
[0,360]
Degree
Indicates the
antenna azimuth
of the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

497
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance
[0,+)
km
Indicates the
distance
between the test
cell and a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Handover
Requests
[0,+)
Number
Indicates the
number of
handover
requests from
the current
serving cell to
another cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

498
Nastar
Parameter
Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Where
Test Cell Is
Located
1 to 32
characters
N/A
Indicates the
name of the
BSC that a test
cell belongs to,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Test Cell Name
1 to 64
characters
N/A
Indicates the
name of a test
cell, for
example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

499
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
neighboring cell
for the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
MCC[000,999]
MNC[00,99]
LAC[0,65535]
CI[0,65535]
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

500
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900.
l SRAN8.1/
GBSS15.1/
RAN 15.1
0 to 124, 975 to
1023: belong to
E-GSM 900.
l SRAN9.0/
GBSS16.0/
RAN16.0
0 to 124, 955 to
1023: belong to
R-GSM 900.
l SRAN10.0/
GBSS17.0/
RAN17.0
512 to 885:
belong to
DCS1800
l SRAN10.1/
GBSS17.1/
RAN17.1
512 to 810:
belong to
PCS1900.
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

501
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
neighboring cell
for the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

502
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Where
Neighboring
Cell Is Located
1 to 32
characters
N/A
Indicates the
name of the
BSC that a
neighboring cell
for the selected
test cell belongs
to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
neighboring cell
for the selected
test cell.
MCC[000,999]
MNC[00,99]
LAC[0,65535]
CI[0,65535]
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

503
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
for a
neighboring cell
for the selected
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
1 to 124: belong
to P-GSM 900.
l SRAN9.0/
GBSS16.0/
RAN16.0
0 to 124, 975 to
1023: belong to
E-GSM 900.
l SRAN10.0/
GBSS17.0/
RAN17.0
0 to 124, 955 to
1023: belong to
R-GSM 900.
l SRAN10.1/
GBSS17.1/
RAN17.1
512 to 885:
belong to
DCS1800
l SRAN11.0/
GBSS18.0/
RAN18.0
512 to 810:
belong to
PCS1900.
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

504
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
a neighboring
cell for the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance
[0,+)
km
Indicates the
distance from
the selected test
cell to a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

505
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number Of
Handover
Requests
[0,+)
Number
Indicates the
number of
handover
requests from
the current
serving cell to
another cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Priority
[0,+)
N/A
Indicates the
sequence
number of a
possible
neighboring cell
among all
possible
neighboring
cells for the
selected test cell
according to its
integrated
priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
4.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 03 (2015-07-30)

506
Nastar
redundant or missing neighboring UMTS cells.
4.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.
NOTE
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.
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 03 (2015-07-30)

507
Nastar
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.
NOTE
Issue 03 (2015-07-30)

508
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
applicat
ion data
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U
To deliver performance indicator requirements to the

U2000/M2000 so that the U2000/M2000 filters out the
function on the Nastar client, the Nastar issues an
application data subscription command to the eSAU.
Collect
perform
ance
data
eS
AU
U20
00/
M20
00


509
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Upload
perform
ance
data
U2
000
/
M2
000
eSA
U
To upload the performance data that meets the Nastar's

requirements to the eSAU.
2.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

3.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
4. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
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 4-14 describes network
changes and their impacts.
Issue 03 (2015-07-30)

510
Nastar

Network Change
Impacts


antenna

as discontinuous
control.
Adjusting frequency

Adjusting handover
relationship and
handover parameters

Adjusting the BSC

topology or other
network topology

Technical Specifications for GSM/UMTS Neighboring Cell Analysis

of analysis time.
NOTE
Issue 03 (2015-07-30)
Item
Execution type
One-time task

analysis task
<= 10,000 cells

511
Nastar
Item
Number of allowed
analysis tasks
<= 50

one analysis task
14 days

task
<= 5 minutes

15 days

15 days
4.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.
Ensure that you have the operation rights to subscribe to GSM/UMTS neighboring cell
analysis data upon login.
Ensure that your user account is authorized to create GSM/UMTS neighboring cell analysis
tasks, and the operation rights to operate the analyzed NEs.

Configuration Data
Issue 03 (2015-07-30)

512
Nastar
Data.
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)
Checking Network Environment

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
(RH2288).
data and the BSC has the license for using the function 2G/3G neighboring cell autooptimization. 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
(RH2288).
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
Issue 03 (2015-07-30)

513
Nastar
Obtaining Data(GSM) > Turning On the Switch Whether to Allow a 3G to 2G

Handover (GSM/UMTS Neighboring Cell Analysis) in Nastar Commissioning Guide
(RH2288).
4.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
Procedure
Prerequisite
GSM configuration data and GSM engineering parameters have been imported to the Nastar
database. For details, see 4.4.2 Preparations for GSM/UMTS Neighboring Cell Analysis.
Procedure
Issue 03 (2015-07-30)

514
Nastar
Table 4-15 Description of GSM/UMTS neighboring cell analysis procedures

N
o.
Procedure
Description
Reference for
Detailed
Operations
(1
)
Check the
integrity of
GSM/UMTS
neighboring
cell analysis
data

3.6 Checking the

Integrity of
Analysis Data
Procedure:
1. Set Data Type to GSM/UMTS
Neighboring Cell analysis data.
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.
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 03 (2015-07-30)

515
Nastar
N
o.
Procedure
Description
Reference for
Detailed
Operations
(2
)
Subscribe to
GSM/UMTS
neighboring
cell analysis
data
(application)

3.5 Subscribing to
Analysis Data
Procedure:
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
5. On the Advanced Parameter Settings tab,
set advanced parameters for GSM/UMTS
6. Click Next.
7. In Result of setting window, add the
ARFCN and scrambling code of a cell.
8. Click .
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
integrity of
GSM/UMTS
neighboring
cell analysis
data

Procedure:
3.6 Checking the

Integrity of
Analysis Data
1. Set Data Type to GSM/UMTS

Neighboring Cell analysis data.
4. Click Query.
The query results are displayed in the right
pane of the window.
Issue 03 (2015-07-30)

516
Nastar
N
o.
Procedure
Description
Reference for
Detailed
Operations
(3
)
Create a GSM/
UMTS
neighboring
cell analysis
task

Basic Network Optimization > GSM/UMTS
Neighboring Cell Analysis from the navigation
tree of the Analysis Task Management
window.
3.7 Creating an
Analysis Task
Procedure:
1. Double-click GSM/UMTS Neighboring
Cell Analysis.
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/
UMTS
neighboring
cell analysis
results

analysis task in the Finished state. In the lower
right of the Task Result area, select a result
record of the task.
3.8 Querying
Analysis Results
Procedure:
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 03 (2015-07-30)

517
Nastar
N
o.
Procedure
Description
(5
)
View possible
GSM/UMTS
neighboring
cell analysis
results
Navigation path: Choose a neighboring cell

analysis task whose status is Complete from the
upper right area of the Analysis Task
Management window. In the lower right Task
Result area, choose an analysis result of the
task.
Reference for
Detailed
Operations
Procedure:
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
Possible Neighboring Cell Analysis.
(6
)
Export GSM/
UMTS
neighboring
cell analysis
reports
Navigation path: Click the icon on the toolbar

in the upper left part of each analysis results
window.
3.10 Exporting
Analysis Reports
Procedure:
For the description of export icon, see
3. Click Finish.
(7
)
Export GSM/
UMTS
Possible
Neighboring
Cell Analysis
Reports
Navigation path: Click the icon on the toolbar

in the upper left part of each analysis results
window.
Procedure:
For the description of export icon, see
Possible Neighboring Cell Analysis.
3. Click Save.

Issue 03 (2015-07-30)

518
Nastar
Parameter
Measure Task
Description
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
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.
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.
Measurement step
Number of frequencies in a frequency group.

The value of this parameter is an integer ranging
from 1 to 31.
Advanced
Parameter
Settings
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.
Duration

task is performed.
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.
Measurement
period
Issue 03 (2015-07-30)

interval is 15 minutes by default and cannot be
changed.

519
Nastar
Parameter
Description
Result of setting
Query
Configuration
allows users to fill the configured ARFCNs and

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

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Issue 03 (2015-07-30)

520
Nastar
Parameter
Description
Select NE(s)

NOTE
Parameter
Neighboring
Cell Analysis
Parameters
Description
Neighboring
Cell Count
Setting
Threshold of the neighboring cell sequence number. All the

undefined neighboring cells whose sequence numbers are
smaller than or equal to the value of this parameter are
regarded as missing neighboring cells. All the defined
neighboring cells whose sequence numbers are larger than
the value of this parameter are regarded as redundant
neighboring cells.
Result Show
Parameters
Other
Parameter
Settings
Number of
undefined
neighboring
cells to be
displayed
Indicates that only the TopN undefined neighboring cells are

displayed.
Superdistance
threshold

neighboring cell.


Parameter
Description
Duration
Delay
immediately.
Issue 03 (2015-07-30)

521
Nastar
Parameter
Description
Execute on
4.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.
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 4-21.
Figure 4-21 GSM/UMTS neighboring cell analysis Interface
Issue 03 (2015-07-30)

522
Nastar
No.
Area
Description
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.
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.
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.
List of test
cells
Lists the information about each test cell.
List of
neighboring
UMTS cells
Lists all neighboring UMTS cells of selected test cells in area 1.

In this area, you can perform the following operations;
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 doubleclick 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 dropdown box to display the table in a filtered way; click the
Issue 03 (2015-07-30)

column
523
Nastar
No.
Area
Description
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
Figure 4-22 Map interface for GSM/UMTS neighboring cell analysis results
Issue 03 (2015-07-30)
No.
Name
Description
Button area

524
Nastar
No.
Name
Description
Navigation
tree

NOTE
in area 3.
3
Geographic
display area
Legend area

click
Information
area
in the button 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 4-23.
Issue 03 (2015-07-30)

525
Nastar
Figure 4-23 GSM/UMTS Neighboring cell analysis Interface
Issue 03 (2015-07-30)
No.
Area
Description
Button area
Summary
of possible
neighborin
g UMTS
cell
analysis
results
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.
Lists the summary of the possible neighboring UMTS cells of all cells
involved in the analysis task.
to display the table in a filtered way; click the column header to
display the table in the descending order. You can also press Ctrl+F to
search in the area.

526
Nastar
No.
Area
Description
Confirmati
on list of
possible
neighborin
g UMTS
cells
Lists all the possible neighboring UMTS cells of selected cells in area
2.
l Button area:
is used to add possible neighboring UMTS cells
for a serving cell. The procedure is as follows:
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.
4.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 03 (2015-07-30)

527
Nastar
Parameters About a Test Cell

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Where
Test Cell Is
Located
1 to 32
characters
N/A
Indicates the
name of the
BSC that a test
cell belongs to,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Test Cell Name
1 to 64
characters
N/A
Indicates the
name of a test
cell, for
example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

528
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
FDD REP
QUANT
ECNO
N/A
Indicates the
signal receiving
indicator of the
UMTS
neighboring cell
reported in the
FDD cell test
report, for
example, ECNO
or RSCP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
RSCP
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
Measurement
Reports
[0,+)
Number
Indicates the
total number of
Measurement
Reports
received by a
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

529
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Configured
Neighboring
Cells
[0,64]
Number
Indicates the
number of
neighboring
cells defined for
a specified cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Redundant
Neighboring
Cells
[0,+)
Number
Indicates the
number of
redundant
neighboring
UMTS cells of
the current test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

530
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Missing
Neighboring
Cells
[0,+)
Number
Number of
Missing
Neighboring
Cells
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Percentage of
Measurement
Reports on
Missing
Neighboring
Cells (%)
[0.00,100.00]
Indicates the
sum of the
integrated
priority of the
missing
neighboring
UMTS cells of
the current test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

531
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
LAC
[1,65533],
[65535]
N/A
Indicates the
location area
code of the
current test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CI
[0,65535]
N/A
Indicates the
identification
code of the
current test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

532
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
of the current
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSIC
[0,77]
N/A
Indicates the
base station
identity code of
the current test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

533
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Service Type of
Cell
Indoor, Outdoor
or null
N/A
Indicates the
service type of
the neighboring
cell of the
current test cell,
such as indoor
site, outdoor site
and unknow
service type.
Learning the
service type of
the test cell
prevents
important
neighboring
cells from being
mistakenly
deleted.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the ID
of the current
test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Test Cell ID
[0,2047]
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

534
Nastar
Parameters About the Neighboring UMTS Cells

Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
UMTS Cell
Name
1 to 64
characters
N/A
Indicates the
name of a
defined or
undefined
neighboring
UMTS cell of
the current test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
the neighboring
UMTS cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

535
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
UMTS CI
[0,65535]
N/A
Indicates the
cell identity of a
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DownLink
ARFCN
[0,65535]
N/A
Indicates the
downlink
ARFCNs of a
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

536
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Suggested
Operation
Defined
Neighboring
Cell(Reserved),
Defined
Neighboring
Cell
(Redundant),
Undefined
Neighboring
Cell(Missing)
or Undefined
Neighboring
Cell(NonOperation)
N/A
Indicates the
operation
suggestions that
the Nastar
provides.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

537
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
One-Way/TwoWay
"One-Way",
"Two-Way",
"Unknown", "-"
N/A
Field for
identifying a
unidirectional
or bidirectional
neighbor
relationship
based on
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User Modify
N/A
N/A
Field for
identifying data
that users can
modify. Each of
such data
records contains
this field after
being exported.
Users can
change this field
as required.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

538
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Score
[0,+)
N/A
Indicates the
total score of
each
neighboring cell
based on the
measurement
result according
to the
neighboring cell
algorithm.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Integrated
Priority
[0,+)
N/A
Indicates the
integrated
priority of the
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

539
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Service Type of
Neighboring
Cell
Indoor, Outdoor
or null
N/A
Indicates the
service type of a
neighboring
UMTS cell,
such as indoor
site, outdoor site
and unknow
service type.
Learning the
service type of
the neighboring
UMTS cell
prevents
important
neighboring
cells from being
mistakenly
deleted.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
distance from
the current test
cell to a
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Distance
[0,+)
km
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

540
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Co-site
Yes, No
N/A
Field for
determining
whether a
neighboring cell
shares the same
site with a
specified cell
based on certain
algorithms.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Super-Distance
Yes, No or null
N/A
Indicates that
the distance
between a
specified cell
and its
neighboring cell
exceeds a
predefined
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

541
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Duration in
BA List
[0,+)
minute
Indicates the
duration that a
neighboring
UMTS cell is
measured.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
UMTS
Neighboring
Cell RSCP
(dBm)/ECNO
(dB)
(-,0]
dB
Indicates the
average RSCP/
ECNO of
UMTS
neighboring
cells. Test FDD
REP QUANT to
decide whether
the data reported
by UMTS
neighboring cell
is the RSCP or
the ECNO.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

542
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Source Cell
Signal Strength
(-,0]
dBm
Indicates the
average signal
strength of the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Measurement
Reports with
UMTS Cell
[0,+)
Number
Indicates the
number of MRs
including the
UMTS
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

543
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Measurement
Reports with
UMTS Cell
Ranking First
[0,+)
Number
Indicates the
number of times
a UMTS cell
ranking No.1 in
the neighboring
cell list of MR.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Request
Number of
Handover
[0,+)
Number
Indicates the
number of
handover
requests from
the current
serving cell to
another cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

544
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Failure Number
of Handover
[0,+)
Number
Indicates the
number of
handover
failures among
all handover
requests from
the current
serving cell to
another cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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 03 (2015-07-30)

545
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell Name
1 to 64
characters
N/A
Indicates the
name of a
dominant cell,
for example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
FDD REP
QUANT
ECNO
RSCP
N/A
Indicates the
signal receiving
indicator of the
UMTS
neighboring cell
reported in the
FDD cell test
report, for
example, ECNO
or RSCP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

546
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of a
test cell, for
example,
286-01-33034-5
0712.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Test Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
of a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

547
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Test Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
a test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell DownLink
ARFCN
N/A
N/A
Indicates the
measured
downlink
ARFCNs of a
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

548
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell P-SC
[0,511]
N/A
Indicates the
measured
primary
scrambling code
of a neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RNC ID of the
Selected
Possible
Neighboring
Cell
[0,+)
N/A
Indicates the
number of the
RNC that the
selected
possible
neighboring
UMTS cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

549
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Name of the
Selected
Possible
Neighboring
Cell
1 to 64
characters
N/A
Indicates the
name of the
selected
possible
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell CI
[0,65535]
N/A
Indicates the
cell identity
code of the
selected
possible
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

550
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance
[0,+)
km
Indicates the
distance from
the test cell to
the selected
possible UMTS
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Relative Angle
of Possible
Neighboring
Cell
[0,360]
()
Indicates the
relative angle
between the
selected
possible
neighboring
UMTS cell and
the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

551
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Predicted Signal
Strength
N/A
dBm
Indicates the
signal strength
of the selected
possible UMTS
neighboring cell
based on the
dimensioning.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Get from Config

Data
Yes,No
N/A
Indicates
whether the
selected
possible
neighboring
UMTS cell is
obtained from
the
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

552
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Neighboring
Cell Laps
2,3,9
N/A
Indicates the
number of laps
between the
selected
possible UMTS
neighboring cell
and the test cell,
that is, the
number of cells
between the
selected
possible
neighboring
UMTS cell and
the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Possible
Neighboring
Cells
[0,+)
N/A
Indicates the
number of
possible
neighboring
cells in the
possible
neighboring
UMTS cell pair.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

553
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Integrated
Priority
N/A
N/A
Indicates the
integrated
priority of the
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
UMTS
Neighboring
Cell RSCP
(dBm)/ECNO
(dB)
N/A
dB
Indicates the
average RSCP/
ECNO of
UMTS
neighboring
cells. Test FDD
REP QUANT to
decide whether
the data reported
by UMTS
neighboring cell
is the RSCP or
the ECNO.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

554
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Source Cell
Signal Strength
N/A
dBm
Indicates the
average signal
strength of the
selected test
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Neighboring
Cell
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
of a UMTS
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

555
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Times A
Neighboring
Cell Ranking
No.1 in
Measurement
Reports
[0,+)
Number
Indicates the
number of times
a UMTS cell
ranking No.1 in
the neighboring
cell list of MR.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

556
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Whether to Use
N/A
N/A
Indicates
whether to
select the
current possible
neighboring
UMTS cell as
the most
possible
neighboring cell
of the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Name of the
Selected
Possible
Neighboring
Cell replaces
Neighboring
Cell Name.
Issue 03 (2015-07-30)

557
Nastar
Parameter
Range
Unit
Description
Supported
Solution
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
Issue 03 (2015-07-30)

558
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
system clears all

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
Issue 03 (2015-07-30)

559
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Name of
Possible
Neighboring
Cell
1 to 64
characters
N/A
Indicates the
cell name of a
possible
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
a possible
neighboring
UMTS cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

560
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CI
[0,65535]
N/A
Indicates the
cell identity of a
possible
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance
[0,+)
km
Indicates the
distance from
the test cell to a
possible
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

561
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Relative Angle
of Possible
Neighboring
Cell
[0,360]
()
Indicates the
relative angle
between the test
cell and a
possible
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Predicted Signal
Strength
N/A
dBm
Indicates the
signal strength
of a possible
neighboring
UMTS cell
based on the
dimensioning.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

562
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Get from Config

Data
Yes,No
N/A
Indicates
whether the
possible
neighboring
UMTS cell is
obtained from
the
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Neighboring
Cell Laps
2,3,9
Number
Indicates the
number of laps
between the test
cell and a
possible
neighboring
UMTS cell, that
is, the number of
cells between
the test cell and
a possible
neighboring
UMTS cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

563
Nastar
4.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.
4.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
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.
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), 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
Issue 03 (2015-07-30)

564
Nastar
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 4-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
Issue 03 (2015-07-30)

565
Nastar

User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
applicat
ion data
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
U20
00/
M20
00
To request the U2000/M2000 to filter out the scanned

uplink frequency data that meets the Nastar's
requirements. After a user enables the application data
subscription function on the Nastar client, the Nastar
issues an application data subscription command to the
eSAU.
Upload
scanned
uplink
frequen
cy data
U2
000
/
M2
000
Nast
ar
Serv
er
The Nastar periodically scans the directories on the

U2000/M2000 for saving reported data. By doing this,
the Nastar can obtain data from the U2000/M2000
immediately once data is reported.
2.
Check
the
integrit
y of
analysi
s data
Issue
data
query
comma
nds and
return
data
query
results
Nast
ar
Serv
er
To issue a data query command to the Nastar server.

After a user enables the data maintenance function on
the Nastar client, the Nastar checks whether the analysis
data is ready on the Nastar server. To return data integrity
check results to the Nastar client and display the results
3.
Create
and
execute
an
analysi
s task
Issue
task
executio
n
comma
nds and
upload
data
analysis
results
Nast
ar
Serv
er
To issue a task execution request to the Nastar server.

After a user creates an analysis task on the Nastar client,
the Nastar client issues a task execution command to the
Nastar server, requesting the Nastar server to aggregate
data. To aggregate the data reported by SAUs, generate
data analysis results, and upload the data analysis results
to the Nastar client.
4. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Issue 03 (2015-07-30)

566
Nastar
Figure 4-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
4-17.
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
applicat
ion data
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

eSAU.
Collect
scanned
uplink
frequen
cy data
eS
AU
U20
00/
M20
00
The eSAU delivers data processing requests to NEs

through the U2000/M2000, requesting the NEs to report
scanned uplink frequency data to the U2000/M2000.

567
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Upload
scanned
uplink
frequen
cy data
U2
000
/
M2
000
Nast
ar
Serv
er
The eSAU periodically scans the directories on the

the eSAU can notify the Nastar of obtaining data from
the U2000/M2000 once data is reported.
2.
Check
the
integrit
y of
analysi
s data
Issue
data
query
comma
nds and
return
data
query
results
Nast
ar
Serv
er
To issue a data query command to the Nastar server.

After a user enables the data maintenance function on
the Nastar client, the Nastar checks whether the analysis
data is ready on the Nastar server. To return data integrity
check results to the Nastar client and display the results
3.
Create
and
execute
an
analysi
s task
Issue
task
executio
n
comma
nds and
upload
data
analysis
results
Nast
ar
Serv
er
To issue a task execution request to the Nastar server.

After a user creates an analysis task on the Nastar client,
the Nastar client issues a task execution command to the
Nastar server, requesting the Nastar server to aggregate
data. To aggregate the data reported by SAUs, generate
data analysis results, and upload the data analysis results
to the Nastar client.
4. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for GSM Uplink Interference Analysis

This section describes the technical specifications.
NOTE
Issue 03 (2015-07-30)

568
Nastar
Item
Execution type
One-time task
<= 1000 cells
<= 50

task
7 days
<= 135 minutes

analysis data
15 days

analysis data
15 days
4.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.

l
Check that you have applied the license for GSM uplink interference analysis and the
license is valid.
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.

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.
Issue 03 (2015-07-30)

569
Nastar
Data.

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
4.5.3 Process of GSM Uplink Interference Analysis

This section describes the GSM uplink interference analysis process.
l
Prerequisites
Procedure
Prerequisites
GSM configuration data has been imported into the Nastar database. For detailed operations,
see 4.5.2 Preparations for GSM Uplink Interference Analysis.
Procedure
Issue 03 (2015-07-30)

570
Nastar
Issue 03 (2015-07-30)

571
Nastar
Table 4-18 Description of the GSM uplink interference analysis process

No.
Proced
ure
Description
Reference
(1)
Check
the
integrit
y of
GSM
uplink
interfer
ence
analysis
data

3.6 Checking the

Integrity of
Analysis Data
Procedure:
Optimization > GSM Uplink Interference
Analysis Data.
2. Specify the time period.
3. Select the desired NEs.
4. Click Query.
of the window.
analysis task.
performing (2).
NOTE
Issue 03 (2015-07-30)

572
Nastar
No.
Proced
ure
Description
Reference
(2)
Subscri
be to
uplink
interfer
ence
analysis
data
(applica
tion)

3.5 Subscribing
to Analysis Data
Procedure:
click the GSM tab.
2. In the navigation tree, select the desired NEs.
3. On the Uplink Interference Analysis tab page,
click ON.
4. In the displayed Uplink Interference Analysis
Parameter Settings dialog box, set the threshold
parameters.
Task Parameters.
5. Click .
NOTICE
In the multi-site cell scenario, if the NE version is BSC6900
V900R015C00 (or later) or BSC6910 V100R015C00 (or
later), the test channel will be in the test state after the
application data subscription for GSM uplink interface
analysis (namely, the uplink ARFCN scanning test) is
started. During the test, the test channel is unavailable to
subscribers, which reduces the number of available TCHs.
The test channel will become available after the test. In the
non-multi-site cell scenario, however, this will not happen.
Check
the
integrit
y of
GSM
uplink
interfer
ence
analysis
data

Procedure:
3.6 Checking the

Integrity of
Analysis Data

Optimization > GSM Uplink Interference
Analysis Data.
4. Click Query.
of the window.
analysis task.
Issue 03 (2015-07-30)

573
Nastar
No.
Proced
ure
Description
Reference
(3)
Create a
GSM
uplink
interfer
ence
analysis
task
Navigation path: In the navigation tree of the

Analysis Task Management window, choose
Theme Function > Basic Network Optimization >
GSM Uplink Interference Analysis.
l For detailed
operations, see
3.7 Creating
an Analysis
Task.
Procedure:
1. Double-click GSM Uplink Interference
Analysis.
2. Specify the task name and remarks. Then, click
Next.
3. On the Select NE(s) tab page, select the desired
NEs.
l For details
about the
parameters,
see Analysis
Task
Parameters.
4. Set parameters on the Parameter Settings tab

page. Then, click Next.
5. Specify the time period. After the task is executed,
the Nastar obtains the analysis results for the
specified time period.
6. Click Finish.
(4)
View
GSM
uplink
interfer
ence
analysis
results

task.
l For detailed
operations, see
3.8 Querying
Analysis
Results.
Procedure:
l For details
about the
analysis result
interface, see
4.5.4
Interface
Description:
GSM Uplink
Interference
Analysis.
1. Double-click the result record of the task.

2. In the displayed GSM Uplink Interference
Analysis window, view the analysis results about
this record.

Issue 03 (2015-07-30)

574
Nastar
Parameter
Description
Task Name

Value range:
l Characters not allowed: ` ~ ! @ # $ % ^ & * ( ) + { } [ ] \ / | ; ' : , . ? <
>"
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 24-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
Segment
Frequency band used by a cell.

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
Issue 03 (2015-07-30)
Cells involved in a GSM uplink interference analysis task.

575
Nastar
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.

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Parameter
Description
Select NE(s)

Network scale for one analysis task <= 1000 cells
NOTE
Parameter description
Issue 03 (2015-07-30)

576
Nastar
Parameter
Description
Minimum
Diversity
Threshold
Threshold of the average uplink interference strength of the diversity

antenna.
The value is an integer from -115 to 0. The default value is -115.
Unit: dBm
Minimum Main
Threshold
Threshold of the average uplink interference strength of the main antenna.

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
Calculation
Algorithm
Algorithm for calculating the average value.

The value can be Signal Strength or Power. If the parameter is set to
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.

Parameter
Description
Duration
Delay
immediately.
Execute on
4.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 03 (2015-07-30)

577
Nastar
Select an executed GSM uplink interference analysis task and double-click a result record
in the Task Result area.
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 4-27 shows the interface.
Figure 4-27 Interface for GSM uplink interference analysis results
N
o.
Name
Description
Cell
informati
on table
Displays the interference strength of all measurement cells involved in an

analysis task.
Informati
on area
Displays the basic information about the selected cell, including the cell
name, BCCH frequency, frequency hopping mode, time range, location
group number, BSC name, and TCH list.
Issue 03 (2015-07-30)
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.

578
Nastar
N
o.
Name
Description
Bar chart
of
interferen
ce
strength
Displays the interference strength of all ARFCNs in the selected cell at a

certain time point.
l The horizontal coordinate lists ARFCNs sequentially from left to right
after you can set Sort Type.
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.
Line
chart of
interferen
ce
strength
Displays the interference strength of a certain ARFCN in the selected cell

within a specified time period. You can select the ARFCN from the
Frequency drop-down list.
l The horizontal coordinate represents the time period.
l The vertical coordinate represents the interference strength of the
ARFCN.
4.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 03 (2015-07-30)

579
Nastar
Measurement Cell Overview Information

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Name
1 to 32
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of a cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

580
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that a measured
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Location Group
Number
0 to 35 or null
N/A
Number of the
location group
under the BTS.
It is unique for
each BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

581
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Frequency
[0,1023]
N/A
Indicates the
frequency of a
measured TRX.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Type
BCCH, TCH
N/A
Indicates the
type of a
measured TRX.
The options are
BCCH and
TCH.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

582
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Main Average
Interference
Strength
[-120,-47]
dBm
Indicates the
average main
interference
strength of a
measured TRX.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Diverse
Average
Interference
Strength
[-120,-47]
dBm
Indicates the
average
diversity
interference
strength of a
measured TRX.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

583
Nastar
Parameters
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
that a measured
TRX belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Location Group
Number
0 to 35 or null
N/A
Number of the
location group
under the BTS.
It is unique for
each BTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

584
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Name
1 to 32
characters
N/A
Indicates the
name of a BSC,
for example,
BSC_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Time Range
N/A
N/A
Indicates the
time range in
which an uplink
interference
analysis task is
performed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

585
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BCCH
Frequency
N/A
N/A
Indicates a
BCCH ARFCN
of the selected
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Frequency
Hopping Mode
No Frequency
Hopping,
Baseband
Frequency
Hopping, RF
Frequency
Hopping,
BCCHinvolved
baseband
Frequency
Hopping
N/A
Indicates the
type of the
frequency
hopping.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

586
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCH List
N/A
N/A
Indicates all
TCH ARFCNs
of the selected
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Time Point
N/A
N/A
Indicates the
counter bar
chart of the
selected cell at a
certain time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

587
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Sort Type
Frequency,
Diversity, Main
N/A
Indicates the
data sequence
mode in the bar
chart.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Diversity
indicates the
average
diversity
interference
strength. Main
indicates the
average main
interference
strength.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Date
N/A
day
Time period for

the analysis
results of a
selected cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

588
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Frequency
[0,1023]
N/A
Indicates the
trend of the
strength of a
frequency in the
selected cell in a
certain time
segment. The
trend is
displayed on a
line chart.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
4.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.
4.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.
NOTE
Issue 03 (2015-07-30)

589
Nastar
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.
Call records of subscribers can reflect the access performance, service retainability, and intraRAT handover performance of terminals. KPIs related to delay, service quality, and traffic can
reflect the terminal capability.
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 followup network building and marketing strategies.
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.
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).
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.
Issue 03 (2015-07-30)

590
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U
To turn on the data source switch on the NE side. After

a user enables the basic data subscription function on the
Nastar client, the Nastar issues a basic data subscription
command to the eSAU.
Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00
To issue an MML command to the U2000/M2000.

591
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC
To forward the MML command to the NE through the

U2000/M2000, requesting the NE to generate raw data.
Upload
raw data
BS
C/
RN
C
SAU
To upload the raw data to the SAU.
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U
To deliver a data-preprocessing request to the eSAU.

function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU
To deliver a data-preprocessing request to the SAU,

requesting the SAU to start the data-preprocessing task.
Upload
preproc
essed
data
(direct)
SA
U
eSA
U
To upload preprocessed data to the eSAU.
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U
To enable the data maintenance function. After a user

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U
To deliver a task execution request to the eSAU. After a

2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

592
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
analysi
s task
Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for GSM Terminal Analysis

of analysis time.
NOTE
Issue 03 (2015-07-30)
Item
Execution type
One-time task

analysis task
l <= 10,000 cells (for terminal inventory analysis)
Number of allowed
analysis tasks
<= 50

one analysis task
7 days

task
l Terminal inventory analysis: <= 90 minutes

15 days

15 days
l <= 10,000 cells (for terminal geographic observation)
l Terminal geographic observation: <= 80 minutes

593
Nastar
4.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.
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 and right to perform operations
on terminal analysis tasks.

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.
Terminal Type Management. Then double-click Terminal Type Management. Import or edit
the terminal information as required. For details, see 3.4.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 03 (2015-07-30)

594
Nastar
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)
Checking the Analysis Environment

l
GSM RAN CS analysis:

GSM RAN PS analysis:

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.
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.
4.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:
Issue 03 (2015-07-30)

595
Nastar
Prerequisites
Process
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 4.6.2
Preparations for GSM Terminal Analysis.
Process
Issue 03 (2015-07-30)

596
Nastar
Table 4-20 Description of the terminal analysis process

No.
Procedure
Description
Reference
(1)
Check
whether
analysis
data is
integrated?

3.6 Checking
the Integrity of
Analysis Data
Procedure:
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.
of the window.
an analysis task.
performing (2).
NOTE
Issue 03 (2015-07-30)

597
Nastar
No.
Procedure
Description
Reference
(2)
Subscribe
to analysis
data
(basic).

3.5 Subscribing
to Analysis Data
Procedure:
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(CHRPS) to ON.
5. Click Confirm.
Verify that the data switch is successfully turned
on by viewing information displayed in the Log
Info area.
Subscribe
to analysis
data
(applicatio
n).

Procedure:
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
5. Click OK.
Verify that data subscription is successfully
turned on by viewing information displayed in
the Log Info area.
Issue 03 (2015-07-30)

598
Nastar
No.
Procedure
Description
Reference
Check
whether
analysis
data is
integrated?

3.6 Checking
the Integrity of
Analysis Data
Procedure:
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,
l Only GSM Terminal Geographic Observation
geographically.

4. Click Query.
of the window.
an analysis task.
Issue 03 (2015-07-30)

599
Nastar
No.
Procedure
Description
Reference
(3)
Create an
analysis
task.
Navigation path: In the left navigation tree of the

Theme Function > Terminal Analysis > GSM
Terminal Analysis.
3.7 Creating an
Analysis Task
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.
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 03 (2015-07-30)

600
Nastar
No.
Procedure
Description
Reference
(4)
View
analysis
results.

task.
l For details,
see 3.8
Querying
Analysis
Results.
Procedure:
l For details on
the
description
about the
window for
displaying
task results,
see 4.6.4
Interface
Description:
GSM
Terminal
Analysis.
1. Double-click the analysis result of a task.

2. In the displayed GSM Terminal Analysis
Task window, view the GSM terminal analysis
result.
(5)
Export
analysis
reports.

Procedure:
3. Click Save.
l For details,
see 3.10
Exporting
Analysis
Reports.
l For details on
the
description
about the
window for
displaying
task results,
see 4.6.4
Interface
Description:
GSM
Terminal
Analysis.

Basic Subscription
Issue 03 (2015-07-30)

601
Nastar
Parameter
Description
Terminal
Analysis Data
(CHR-CS)
Switch for enabling or disabling the reporting of CS CHR data. You can
retain the default state of the switch.
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 03 (2015-07-30)

602
Nastar
Parameter
Description
Terminal
Analysis Data
(CHR-PS)
Switch for enabling or disabling the reporting of PS CHR data. You can retain
the default state of the switch.
You can click
l Internal Message: 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
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:
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:
l Overlong UL PDU Receiving Delay Threshold: For details, see the SET
Parameter
Description
Short Call
Threshold
(MOC)
Indicates the threshold for a very short call duration when a terminal
initiates a call. It reflects the active hangup behaviors caused by
exceptions, such as one-way audio, cross talk, and disturbance call.
Value range: [0.00,255.00], unit: s.
Short Call
Threshold
(MTC)
Indicates the threshold for a very short call duration when a terminal
terminates a call. It reflects the active hangup behaviors caused by
exceptions, such as one-way audio, cross talk, and disturbance call.
Issue 03 (2015-07-30)

603
Nastar
Parameter
Description
Overlong Call
Setup Duration
Threshold
(MOC)
Indicates the threshold for an extra long call setup duration when a
terminal initiates a call. The call setup duration indicates the average
duration from the Channel Request message to the Alerting message.
Overlong Call
Setup Duration
Threshold
(MTC)
Indicates the threshold for an extra long call setup duration when a
terminal terminates a call. The call setup duration indicates the average
duration from the Channel Request message to the Alerting message.
Uplink VQI
Abnormal
Threshold
Indicates the threshold for uplink Voice Quality Indicator (VQI)

exceptions of the voice service.
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.
Downlink VQI
Abnormal
Threshold
Indicates the threshold for downlink Voice Quality Indicator (VQI)

exceptions of the voice service.
The VQI is the Mean Opinion Score (MOS) and reflects the voice quality
during a call.
Value range: [0.0,5.0].
Uplink HQI
Abnormal
Threshold
Indicates the threshold for uplink High Quality Indicator (HQI) exceptions
of the voice service.
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/
to level 7 x 100%
Value range: [0.0,100.0], unit: %.
Downlink HQI
Abnormal
Threshold
Indicates the threshold for downlink HQI exceptions of the voice service.
The HQI reflects the voice quality in a call and 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/
to level 7 x 100%
Value range: [0.0,100.0], unit: %.
Issue 03 (2015-07-30)

604
Nastar

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Parameter
Description
Select NE(s)

Network scale for one analysis task:
NOTE
Parameter
Description
Grid Resolution
Settings
Set the Grid Resolution for displaying terminal geographic observation

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
Terminal
Abilities
Issue 03 (2015-07-30)
Selects terminal capabilities. After you select terminal capabilities, the

Nastar geographically displays the selected terminal capabilities.
If the parameters are not set, the Nastar does not geographically display
the terminal capabilities.
605
Nastar
Parameter
Description
Geographic
Terminal
Objects
Selects terminal objects. After you select terminal objects, the Nastar
geographically displays the traffic of the selected terminal objects. You
can select a maximum of ten terminal objects.
If the parameters are not set, the Nastar does not geographically display
the traffic of terminals.

Parameter
Description
Duration
Delay
immediately.
Execute on
4.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
Select a GSM terminal analysis task in the state, right-click a result record of the task in
Interface
Figure 4-30 shows the GSM terminal analysis result interface.
Figure 4-30 Interface for GSM terminal analysis results
Issue 03 (2015-07-30)

606
Nastar
No.
Item
Icon area
Analysis result
tab page
Description
is used to display terminal analysis results on maps. For
detailed operations, see Terminal Analysis Results Displayed
Through Geographic Observation.
Analysis results are displayed on tab pages.
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 4-31 shows the tab page.
Figure 4-31 Terminal penetration evaluation
Issue 03 (2015-07-30)

607
Nastar
No.
Item
Description
Icons and
analysis
options
is used to export terminal penetration analysis results

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.
Statistics table
The number and occupation of TopN terminals on the live

network from a certain analysis dimension are displayed in a
table. The following shortcut menus by right-clicking are
supported:
l Search, which is used to search for contents in the the table.
l Save As, which is used to save contents in the table.
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 4-32 shows the tab page.
Figure 4-32 Terminal capability evaluation
Issue 03 (2015-07-30)

608
Nastar
No.
Item
Description
Icon area
NE object
navigation tree
Selects all objects to be analyzed.
Terminal
capability list
Selects the terminal capability to be analyzed. If you select one

or more terminal capabilities, the capability analysis results are
displayed in both the chart area and table area on the right.
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.
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.
Allows users to select objects for analysis from three

dimensions: whole network, a single BSC, or a single cell.
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.The following shortcut menus by right-clicking are
supported:
For detailed parameters, see 4.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 4-33 shows the tab page.
Issue 03 (2015-07-30)

609
Nastar
Figure 4-33 Terminal performance evaluation
No.
Item
Description
Analysis
indicator
navigation tree
l The Aggregation Type drop-down list is used to select an

aggravation dimension.
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
table of the
terminal
performance
indicators
Displays the KPI value of the aggregation analysis performed

on the terminals based on the selected dimension.
l You can select a KPI in the Sequence Column drop-down
list, and the system sorts the table in area 2 again based on
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 03 (2015-07-30)

610
Nastar
No.
Item
Description
Aggregation
table of the celllevel terminal
performance
indicators
Displays the performance indicator value of a certain type of

NEs in area 2 in each cell.
the selected KPI.
objects that you want to analyze. The default value of TopN
number is 200. If you want to check all results, click
displayalldata on the right pane. All data in area 3 will be
displayed.
You can save the table by right-clicking the table and choosing
Save As from the shortcut menu.
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 4.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
Observation window is displayed, as shown in Figure 4-34.
Issue 03 (2015-07-30)

. The Geographic
611
Nastar
Figure 4-34 Terminal analysis results displayed through geographic observation
Issue 03 (2015-07-30)
N
o.
Item
Description
Icon area
Provides icons for you to perform operations.

612
Nastar
N
o.
Item
Description
Navigati
on tree
Contains the KPIs to be analyzed:

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
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 03 (2015-07-30)

613
Nastar
N
o.
Item
Description
Geograp
hic
observati
on area
l Displays the analysis results of selected KPIs on grid maps using distinct
colors by default. However, only the analysis results of the last selected
KPI are visible.
Raster
details
area
This area is empty for terminal analysis.
Legend
area
By default, the Nastar does not display this area. If you want to view the
legend details about an analysis theme, click the icon in the button 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.
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
on area
The interface displays no information when it is opened. If you select a grid,

the values of selected KPIs are displayed in all the cells in this gird. 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.
4.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 03 (2015-07-30)

614
Nastar
Basic Terminal Information
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported Solution Version
Mo
del
[
1
,
2
5
6
]
N Indicates the terminal model, for

/ example, iPhone4.
A
N/A
IME
ITA
C
E
i
g
h
t
d
i
g
it
s
N Indicates the combination of the type

/ approval code (TAC) and the final
A assembly code (FAC) in an
International Mobile Equipment
Identity (IMEI). An IMEI consists of
15 digits and uniquely identifies a
terminal in the world. In an IMEI, the
TAC refers to the first six digits, and
the FAC refers to the seventh and
eighth digits. The combination of
TAC and FAC uniquely identifies a
terminal.
N/A
Ven
dor
[
1
,
2
5
6
]
N Indicates the terminal vendor, for

/ example, Nokia and Apple.
A
N/A
Typ
e
N
/
A
N Indicates the terminal type, for

/ example, common terminal,
A intelligent terminal, and data card.
N/A
Chi
p
Mo
del
[
0
,
2
5
6
]
N Indicates the terminal chip model.

/
A
N/A
Tec
hnol
ogy
N
/
A
N Indicates the RAT that the terminal

/ supports, for example, GSM and
A WCDMA.
N/A

615
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Dat
a
Tra
nsfe
r
N
/
A
N Indicates the data transfer mode that

/ the terminal uses, for example,
A HSDPA and HSUPA.
N/A
Ter
min
als
[
1
,
+
N
u
m
b
e
r
Indicates the number of terminals of

this type within the statistical range.
If the statistics are collected based on
IMEI-TAC, this parameter indicates
the number of terminals with the
same IMEI-TAC and different
IMEIs.
N/A
Ter
min
al
Rati
o
[
0
,
1
0
0
]
% Proportion of terminals of a specified

type in all terminals.
N/A
Terminal Capability Analysis Summary

Par
am
eter
R
a
n
g
e
U Description
n
i
t
EG
PRS
N
/
A
N Used to collect statistics about the

/ numbers and percentages of
A terminals that support EGPRS, that
do not support EGPRS, and whose
capability is unknown under a cell,
BSC, or the entire network.
l SRAN8.0/GBSS15.0/RAN 15.0
l SRAN9.0/GBSS16.0/RAN16.0
Issue 03 (2015-07-30)

616
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
180
0
ban
d
N
/
A

A terminals that support GSM-1800,
that do not support GSM-1800, and
whose capability is unknown under a
cell, BSC, or the entire network.
GS
ME
ban
d
N
/
A

A terminals that support E-GSM-900,
that do not support E-GSM-900, and
G/U
dual
mod
es
G/
TD
dual
mod
es
FD
DLTE
N
/
A
N
/
A
N
/
A

A terminals that support GSM/UMTS
dual-mode, that do not support GSM/
UMTS dual-mode, and whose

A terminals that support GSM/TDSCDMA dual-mode, that do not
support GSM/TD-SCDMA dualmode, and whose capability is
unknown under a cell, BSC, or the
entire network.

A terminals that support FDD-LTE, that
do not support FDD-LTE, and whose
Issue 03 (2015-07-30)

617
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
TD
DLTE
N
/
A

A terminals that support TDD-LTE,
that do not support TDD-LTE, and
DT
M
N
/
A

A terminals that support DTM, that do
not support DTM, and whose
8PS
K
mod
ulati
on
Upli
nk
exp
ansi
on
PS
han
dov
er
N
/
A
N
/
A
N
/
A

A terminals that support the 8PSK
modulation mode, that do not support
the 8PSK modulation mode, and

A terminals that support uplink
expansion, that do not support uplink
expansion, and whose capability is
unknown under a cell, BSC, or the
entire network.

A terminals that support PS handovers,
that do not support PS handovers, and
Issue 03 (2015-07-30)

618
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
U90
0
N
/
A

A terminals that support U900, that do
not support U900, and whose
VA
MO
S
N
/
A

A terminals that support VAMOS, that
do not support VAMOS, and whose
WiFi
N
/
A

A terminals that support Wi-Fi, that do
not support Wi-Fi, and whose
Performance Analysis Summary-Accessibility Evaluation
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Call
Setu
p
Req
uest
s
[
0
,
+
N
u
m
b
e
r
Indicates the number of originated

call and terminated call setup
requests initiated by a terminal, that
is, the number of voice service call
setup requests (Channel request
signaling) initiated by the terminal in
the case that IMEIs are correctly
identified.

619
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Call
Setu
p
Exc
epti
ons
[
0
,
+
N
u
m
b
e
r
Indicates the number of abnormal

originated call and terminated call
setups.
If a terminal receives a Connect
Acknowledge message or a
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
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.
Issue 03 (2015-07-30)
Rati
o of
Call
Setu
p
Exc
epti
ons
[
0
,
1
0
0
]
Call
Setu
p
Req
uest
s
(M
OC)
[
0
,
+
% Indicates the proportion of abnormal

originated call and terminated call
setups.
Proportion of abnormal call setups =
Number of abnormal call setups/
Number of call setup requests x 100%
N
u
m
b
e
r
Indicates the number of originated

call setup requests, that is, the number
of voice service call setup requests
(Channel request signaling) in the
case that IMEIs are correctly
identified.

620
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Call
Setu
p
Exc
epti
ons
(M
OC)
[
0
,
+
N
u
m
b
e
r

originated call setups.
If the terminal receives a Connect

Acknowledge signaling or the
Disconnect signaling and the call is
call setup is successful.
If the terminal receives a Clear

normally released by the network,
If 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.
Issue 03 (2015-07-30)
Rati
o of
Call
Setu
p
Exc
epti
ons
(M
OC)
[
0
,
1
0
0
]

originated call setups.
Proportion of abnormal originated

call setups = Number of abnormal
originated call setups/Number of
originated call setup requests x 100%
Call
Setu
p
Req
uest
s
(MT
C)
[
0
,
+
N
u
m
b
e
r
Indicates the number of terminated

call setup requests, that is, the number
of voice service call setup requests
(Channel request signaling) in the
case that IMEIs are correctly
identified.

621
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Call
Setu
p
Exc
epti
ons
(MT
C)
[
0
,
+
N
u
m
b
e
r

terminated call setups.
If a terminal receives a Connect

Acknowledge message or a
Disconnect message and the call is
If a terminal receives a Clear

properly released by the network,
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.
Issue 03 (2015-07-30)
Rati
o of
Call
Setu
p
Exc
epti
ons
(MT
C)
[
0
,
1
0
0
]

terminated call setups.
Abn
orm
al
Rele
ases
Bef
ore
Call
Co
mpl
etio
n
[
0
,
+
N
u
m
b
e
r
Proportion of abnormal terminated

call setups = Number of abnormal
terminated call setups/Number of
terminated call setup requests
Indicates the total number of call

setup failures due to exceptions that
occur upon outgoing call alerting
after a terminal sends call access
requests.

622
Nastar
Performance Analysis Summary- Retainability

Par
am
eter
R
a
n
g
e
U Description
n
i
t
Abn
orm
al
Call
Rele
ases
[
0
,
+
N
u
m
b
e
r
Indicates the total number of

abnormal call releases after the
terminal uses the voice service to
access the network. The call is
abnormally released if any of the
following situations occurs:
1. The Disconnect message carries an

abnormal cause (not Normal
signaling) when the call is released.
2. The terminal receives the Clear

command message, and the call is
abnormally released by the network,
local terminal, or peer terminal.
3. An inter-BSC handover fails.
4. An intra-BSC handover fails.
5. The BSC is abnormal.
6. The MSC is abnormal.
Issue 03 (2015-07-30)
Rati
o of
Abn
orm
al
Call
Rele
ases
[
0
,
1
0
0
]
Sho
rt
Call
s
(M
OC)
[
0
,
+

call releases after the terminal uses
the voice service to access the
network.
Proportion of abnormal call releases

= Number of abnormal call releases/
Number of call release requests
The number of call release requests

refers to the times the terminal sends
a Disconnect message.
N
u
m
b
e
r
Indicates the number of measurement

reports (MRs) on the originated calls
with the duration that is less than the
specified threshold. The call duration
is from the time when the terminal
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.

623
Nastar
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Rati
o of
Sho
rt
Call
s
(M
OC)
[
0
,
1
0
0
]
% Indicates the proportion of MRs on

the originated calls with the duration
that is less than the specified
threshold to all MRs.
Proportion of originated short calls =

Number of originated short calls/
Number of MRs with valid originated
call duration
Sho
rt
Call
s
(MT
C)
[
0
,
+
Indicates the number of MRs on the

terminated calls with the duration that
is less than the specified threshold.
The call duration is from the time
when the terminal 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 interBSC handovers because the entire
duration of the calls cannot be
obtained.
% Indicates the proportion of MRs on

the terminated calls with the duration
that is less than the specified
threshold to all MRs.
Proportion of terminated short calls =

Number of terminated short calls/
Number of MRs with valid
terminated call duration
Proportion of abnormal voice service

releases = Total traffic/Number of
abnormal voice service releases
N
u
m
b
e
r
Rati
o of
Sho
rt
Call
s
(MT
C)
[
0
,
1
0
0
]
Abn
orm
al
Traf
fic
Rele
ase
Rati
o
[ s
0
,
+
The total traffic refers to the duration

from the time when the terminal
receives a Connect Acknowledge to
the time when the terminal sends a
Disconnect message.

624
Nastar
Performance Analysis Summary-Handover Evaluation
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Intr
aSyst
em
Han
dov
er
Req
uest
s
[
0
,
+
N Indicates the number of intra-RAT

u handover requests initiated by the
m terminal.
b
e
r
Intr
aSyst
em
Abn
orm
al
Han
dov
ers
[
0
,
+
Rati
o of
Intr
aSyst
em
Abn
orm
al
Han
dov
ers
[
0
,
1
0
0
]
N Indicates the number of abnormal

u intra-RAT handovers.
m
b
e
r

intra-RAT handovers.
Proportion of abnormal intra-RAT

handovers = Number of abnormal
intra-RAT handovers/Number of
intra-RAT handover requests x 100%

625
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Abn
orm
al
Rele
ases
Duri
ng
Intr
aSyst
em
Han
dov
er
[
0
,
+
N Indicates the number of abnormal call

u releases during the intra-RAT
m handover.
b
e
r
Performance Analysis Summary-System Handover Evaluation
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Inte
rRA
T
Out
goin
g
Han
dov
er
Req
uest
s
[
0
,
+
N
u
m
b
e
r
Indicates the number of terminal

requests for the handover from a cell
on a GSM network to a cell on
another network.

626
Nastar
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Abn
orm
al
Inte
rRA
T
Out
goin
g
Han
dov
ers
[
0
,
+
N
u
m
b
e
r
Rati
o of
Abn
orm
al
Inte
rRA
T
Out
goin
g
Han
dov
ers
[
0
,
1
0
0
]

terminal handovers from a cell on a
GSM network to a cell on another
network.

terminal handovers from a cell on a
GSM network to a cell on another
network.
Proportion of abnormal outgoing

inter-RAT handovers = Number of
abnormal outgoing inter-RAT
handovers/Number of outgoing interRAT handover requests x 100%

627
Nastar
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Abn
orm
al
Rele
ases
Duri
ng
Inte
rRA
T
Out
goin
g
Han
dov
er
[
0
,
+
N
u
m
b
e
r
Inte
rRA
T
Inco
min
g
Han
dov
er
Req
uest
s
[
0
,
+
Abn
orm
al
Inte
rRA
T
Inco
min
g
Han
dov
ers
[
0
,
+
Indicates the number of abnormal call

releases during the handover of the
terminal from a cell on a GSM
network to a cell on another network.
N
u
m
b
e
r
Indicates the number of terminal

requests for the handover from a cell
on another network to a cell on a
GSM network.
N
u
m
b
e
r

terminal handovers from a cell on
another network to a cell on a GSM
network.

628
Nastar
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Rati
o of
Abn
orm
al
Inte
rRA
T
Inco
min
g
Han
dov
ers
[
0
,
1
0
0
]

terminal handovers from a cell on
another network to a cell on a GSM
network.
Proportion of abnormal incoming

inter-RAT handovers = Number of
abnormal incoming inter-RAT
handovers/Number of incoming
inter-RAT handover requests x 100%
Inte
rRA
T
Inco
min
g
Han
dov
er
Del
ay
Rep
orts
[
0
,
+
N
u
m
b
e
r
Indicates the number of MRs with

valid incoming inter-RAT handover
delays. The Nastar cannot collect
statistics on the delays of failed
incoming inter-RAT handovers.
Incoming inter-RAT handover delay

= Handover completion time Handover request time
Inte
rRA
T
Inco
min
g
Han
dov
er
Ave
rage
Del
ay
[ s
0
,
+
Indicates the average delay for the

handover from a cell on another
network to a cell on a GSM network.
Average delay for incoming interRAT handover = Delay of all

successful incoming inter-RAT
handovers/Number of MRs with
valid incoming inter-RAT handover
delays

629
Nastar
Performance Analysis Summary-Delay Evaluation
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Call
Setu
p
Del
ay
Rep
orts
(M
OC)
[
0
,
+
N
u
m
b
e
r

valid interval between the time when
the terminal sends a Channel Request
message to originate a call and the
time when the terminal receives an
Alerting message. The Nastar does
not collect statistics on the delay for
calls involved in inter-BSC
handovers.
Call
Setu
p
Ave
rage
Del
ay
(M
OC)
[ s
0
,
+
Indicates the average interval

between the time when the terminal
sends a Channel Request message to
originate a call and the time when the
terminal receives an Alerting
message.
Rati
o of
Call
Setu
p
Ove
rlon
g
Del
ays
(M
OC)
[
0
,
1
0
0
]
% Indicates the proportion of MRs in

which the originated call setup delay
is greater than the specified threshold.
Call
Setu
p
Del
ay
Rep
orts
(MT
C)
[
0
,
+
N
u
m
b
e
r
Proportion of long delay for

originated call setup = Number of
MRs in which the originated call
setup delay is greater than the
specified threshold/Number of MRs
with originated call setup delay x
100%

valid interval between the time when
the terminal sends a Channel Request
message to terminate a call and the
time when the terminal receives an
Alerting message. The Nastar does
not collect statistics on the delay for
calls involved in inter-BSC
handovers.

630
Nastar
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Call
Setu
p
Ave
rage
Del
ay
(MT
C)
[ s
0
,
+
Rati
o of
Call
Setu
p
Ove
rlon
g
Del
ays
(MT
C)
[
0
,
1
0
0
]
Indicates the average interval

between the time when the terminal
sends a Channel Request message to
terminate a call and the time when the
terminal receives an Alerting
message.
% Indicates the proportion of MRs in

which the terminated call setup delay
is greater than the specified threshold.
Proportion of long delay for
terminated call setup = Number of
MRs in which the terminated call
setup delay is greater than the
specified threshold/Number of MRs
with terminated call setup delay x
100%

631
Nastar
Performance Analysis Summary-Quality Evaluation

Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Upli
nk
VQI
Rep
orts
[
0
,
+
N
u
m
b
e
r
l SRAN8.0/
GBSS15.0/RAN
15.0
Indicates the number of MRs with valid uplink Voice

Quality Indicator (VQI) of the voice service.
As the Mean Opinion Score (MOS), VQI reflects the
voice quality during the call process. The VQI value
ranges from 1 to 5. The greater the VQI value, the
better the voice quality.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Upli
nk
Ave
rage
VQI
[
0
,
5
]
N Average uplink VQI value = Total value of uplink

/ VQIs/Number of MRs with valid uplink VQI
A
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

632
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Rati
o of
Upli
nk
Bad
VQI
Rep
orts
[
0
,
1
0
0
]
% Indicates the proportion of MRs in which the uplink

VQI value is smaller than the specified threshold.
l SRAN8.0/
GBSS15.0/RAN
15.0
Proportion of MRs with poor uplink VQI = Number of

MRs in which the uplink VQI value is smaller than the
specified threshold/Number of MRs with uplink VQI
x 100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Upli
nk
HQI
Rep
orts
[
0
,
+
N
u
m
b
e
r
Indicates the number of MRs with valid uplink High

Quality Indicator (HQI) of the voice service after the
l SRAN8.0/
GBSS15.0/RAN
15.0
HQI reflects the voice quality during the call process.

The HQI value ranges from 0 to 7. The smaller the HQI
value, the better the voice quality.
l SRAN8.1/
GBSS15.1/RAN
15.1
In the CHRs of BSC6900 V900R011 and later BSC

versions:
l SRAN9.0/
GBSS16.0/
RAN16.0
HQI value = Number of MRs with grade 0 to grade 3

receive quality/Number of MRs with grade 0 to grade
7 receive quality x 100%
In the CHRs of BSC6000 V900R008:
l SRAN10.0/
GBSS17.0/
RAN17.0

l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

633
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Upli
nk
Ave
rage
HQI
[
0
,
1
0
0
]
% Indicates the average uplink HQI value obtained on the

basis of MRs with valid uplink HQI within the
statistical range and time after the call setup is
successful.
l SRAN8.0/
GBSS15.0/RAN
15.0
Average uplink HQI value = Total value of uplink

HQIs/Number of MRs with uplink HQI
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Rati
o of
Upli
nk
Bad
HQI
Rep
orts
[
0
,
1
0
0
]
% Indicates the proportion of MRs in which the uplink

HQI value is smaller than the specified threshold
within the statistical range and time after the call setup
is successful.
Proportion of MRs with poor uplink HQI = Number of
MRs in which the uplink HQI is smaller than the
specified threshold/Number of MRs with uplink HQI
x 100%
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

634
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Do
wnli
nk
VQI
Rep
orts
[
0
,
+
N
u
m
b
e
r
l SRAN8.0/
GBSS15.0/RAN
15.0
Indicates the number of MRs with valid Downlink

Voice Quality Indicator (VQI) of the voice service. As
the Mean Opinion Score (MOS), VQI reflects the
voice quality during the call process. The VQI value
ranges from 1 to 5. The greater the VQI value, the
better the voice quality.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Do
wnli
nk
Ave
rage
VQI
[
0
,
5
]
N Average Downlink VQI value = Total value of

/ Downlink VQIs/Number of MRs with valid Downlink
A VQI.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

635
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Rati
o of
Do
wnli
nk
Bad
VQI
Rep
orts
[
0
,
1
0
0
]
% Indicates the proportion of MRs in which the

Downlink VQI value is smaller than the specified
threshold. Proportion of MRs with poor Downlink
VQI = Number of MRs in which the Downlink VQI
value is smaller than the specified threshold/Number
of MRs with Downlink VQI x 100%.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Do
wnli
nk
HQI
Rep
orts
[
0
,
+
N
u
m
b
e
r
Indicates the number of MRs with valid downlink HQI

of the voice service after the call setup is successful.
HQI reflects the voice quality during the call process.
The HQI value ranges from 0 to 7. The smaller the HQI
value, the better the voice quality.
In the CHRs of BSC6900 V900R011 and later BSC
versions:
In the CHRs of BSC6000 V900R008:
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

636
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Do
wnli
nk
Ave
rage
HQI
[
0
,
1
0
0
]
% Indicates the average downlink HQI value obtained on

the basis of MRs with valid downlink HQI within the
statistical range and time after the call setup is
successful.
l SRAN8.0/
GBSS15.0/RAN
15.0
Average downlink HQI value = Total value of

downlink HQIs/Number of MRs with downlink HQI
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Rati
o of
Do
wnli
nk
Bad
HQI
Rep
orts
[
0
,
1
0
0
]
% Indicates the proportion of MRs in which the downlink

HQI value is smaller than the specified threshold
within the statistical range and time after the call setup
is successful.
Proportion of MRs with poor downlink HQI = Number
of MRs in which the downlink HQI value is smaller
than the specified threshold/Number of MRs with
downlink HQI x 100%
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

637
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Upli
nk
Cro
sstal
k
Rati
o
[
0
,
1
0
0
]
% Indicates the proportion of calls with uplink crosstalk.
l SRAN8.0/
GBSS15.0/RAN
15.0
Proportion of calls with uplink crosstalk = Number of

calls with uplink crosstalk/Total number of successful
calls x 100%
The uplink crosstalk check detects only crosstalk on
the BSS internal channel between the BTS and the TC
board but cannot detect crosstalk over the Um interface
and A interface.
Principle of the uplink crosstalk check:
The DSP of the BTS inserts call unique IDs into the
idle bits of uplink voice TRAU frames during the call
process. The DSP of the TC board decodes the call
unique IDs and checks the consistency of the call
unique IDs with the call unique ID in the DSP of the
TC board. If all call unique IDs in the uplink voice
TRAU frames are inconsistent with the call unique ID
in the DSP of the TC board within the check period,
uplink crosstalk occurs.
Do
wnli
nk
Cro
sstal
k
Rati
o
[
0
,
1
0
0
]
% Indicates the proportion of calls with uplink crosstalk.

Proportion of calls with downlink crosstalk = Number
of calls with downlink crosstalk/Total number of
successful calls x 100%
The downlink crosstalk check detects only crosstalk
on the BSS internal channel between the BTS and the
TC board but cannot detect crosstalk over the Um
interface and A interface.
Principle of the downlink crosstalk check:
The DSP of the TC board inserts call unique IDs into
the idle bits of downlink voice TRAU frames during
the call process. The DSP of the BTS decodes the call
unique IDs and checks the consistency of the call
unique IDs with the call unique ID in the DSP of the
BTS. If all call unique IDs in the downlink voice
TRAU frames are inconsistent with the call unique ID
in the DSP of the BTS within the check period,
downlink crosstalk occurs.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
638
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Upli
nk
One
Wa
y
Aud
io
Rati
o
[
0
,
1
0
0
]
% Indicates the proportion of calls with uplink one-way

audio.
l SRAN8.0/
GBSS15.0/RAN
15.0
Proportion of calls with uplink one-way audio =

Number of successful calls with uplink one-way audio/
Total number of successful calls x 100%
The uplink one-way audio check detects only one-way
audio on the BSS internal channel between the BTS
and the TC board but cannot detect one-way audio over
the Um interface and A interface.
Principle of the uplink one-way audio check:
The DSP on the TC board of the BSC periodically
collects statistics on the ratio of error uplink TRAU
frames. When the ratio of error uplink TRAU frames
reaches the threshold, the BSS determines that lowlevel one-way audio occurs on the uplink and starts the
confirmation mechanism. The BSC notifies the BTS
to send a test TRAU frame, one-way audio occurs on
the uplink voice channel if the TS does not receive the
test TRAU frame within the specified time.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
The total number of successful calls refers to the

number of successful call setups within the statistical
range, including the number of successful channel
assignments during inter-BSC incoming handovers.
Issue 03 (2015-07-30)

639
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Do
wnli
nk
One
Wa
y
Aud
io
Rati
o
[
0
,
1
0
0
]
% Indicates the proportion of calls with downlink oneway audio.
l SRAN8.0/
GBSS15.0/RAN
15.0
Proportion of calls with downlink one-way audio =

Number of successful calls with downlink one-way
audio/Total number of successful calls x 100%
The downlink one-way audio check detects only oneway audio on the BSS internal channel between the
BTS and the TC board but cannot detect one-way audio
over the Um interface and A interface.
Principle of the downlink one-way audio check:
The DSP on the DTRU of the BTS periodically collects
statistics on the ratio of error downlink TRAU frames.
When the ratio of error downlink TRAU frames
reaches the threshold, the BSS determines that lowlevel one-way audio occurs on the downlink and starts
the confirmation mechanism. The BSC notifies the TC
board to send a test TRAU frame, one-way audio
occurs on the downlink voice channel if the BTS does
not receive the test TRAU frame within the specified
time.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
The total number of successful calls refers to the

number of successful call setups within the statistical
range, including the number of successful channel
assignments during inter-BSC incoming handovers.
Issue 03 (2015-07-30)

640
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution Version
Upli
nk
and
Do
wnli
nk
NoAud
io
Rati
o
[
0
,
1
0
0
]
% Indicates the proportion of calls with no audio on both

the uplink and the downlink.
l SRAN8.0/
GBSS15.0/RAN
15.0
Proportion of calls with no audio on both the uplink

and the downlink = Number of calls with downlink
one-way audio and uplink one-way audio/Total
number of successful calls x 100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Performance Analysis Summary-Multi-Mode
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Voi
ce
Serv
ice
Dur
atio
n
Rep
orts
[
0
,
+
N
u
m
b
e
r

valid voice service duration.
The voice service duration is the TCH

occupation duration from the time
when the TCH is assigned to the time
when the TCH is released.

641
Nastar
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Voi
ce
Serv
ice
Ave
rage
Dur
atio
n
[ s
0
,
+
Utra
nFD
DSup
port
ed
Ter
min
al
Voi
ce
Serv
ice
Dur
atio
n
Rep
orts
[
0
,
+
N
u
m
b
e
r
Indicates the average duration of the

voice service. The voice service
duration in the MR is from the time
Average voice service duration =

TCH occupation duration/Number of
MRs with voice service duration

valid voice service duration of
terminals that support UTRAN FDD.


642
Nastar
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Utra
nFD
DSup
port
ed
Ter
min
al
Voi
ce
Serv
ice
Ave
rage
Dur
atio
n
[ s
0
,
+
Utra
nTD
DSup
port
ed
Ter
min
al
Voi
ce
Serv
ice
Dur
atio
n
Rep
orts
[
0
,
+
N
u
m
b
e
r
Indicates the average voice service

duration for terminals that support
UTRAN FDD. The voice service


valid voice service duration of
terminals that support UTRAN TDD.


643
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Utra
nTD
DSup
port
ed
Ter
min
al
Voi
ce
Serv
ice
Ave
rage
Dur
atio
n
[ s
0
,
+
Indicates the average voice service

duration for terminals that support
UTRAN TDD. The voice service

Cell Information Overview

Par
am
eter
Range
U Description
n
i
t
Ro
w
No
[1,50000)
N Indicates the number of a row in

/ the summary table.
A
l SRAN8.0/GBSS15.0/RAN
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
l SRAN10.0/GBSS17.0/
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

644
Nastar
Par
am
eter
Range
U Description
n
i
t
BS
C
Na
me
1 to 64
character
s
N Indicates the name of the BSC

/ where the terminal is located.
A
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Cell
ID
[0,7999]
N Indicates the ID of the cell where

/ the terminal is located.
A
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Cell
Na
me
1 to 64
character
s
N Indicates the name of the cell

/ where the terminal is located.
A
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

645
Nastar
Par
am
eter
Range
U Description
n
i
t
CGI
MCCMNCLAC-CI
N Indicates the global identity of

/ the cell where the terminal is
A located.
15.0
MCC
[000,999]
l SRAN9.0/GBSS16.0/
RAN16.0
MNC
[00,99]
RAN17.0
LAC
[0,65535]
RAN17.1
CI
[0,65535]
Ter
min
als
[0,+)
15.1
RAN18.0
N Indicates the number of terminals
/ of a specified type in each cell.
A
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
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.
Issue 03 (2015-07-30)

646
Nastar
Terminal Geographic Display-Traffic Analysis

Par
am
eter
R
a
n
g
e
U Description
n
i
t
Tota
l
Traf
fic
[ K The grid map is rendered according

0 B to the total traffic of terminals in the
,
grids.
+
Upli
nk
Traf
fic

0 B to the uplink traffic of terminals in the
,
grids.
+
Do
wnli
nk
Traf
fic

0 B to the downlink traffic of terminals in
,
the grids.
+
Terminal Geographic Display-Capability Analysis

Par
am
eter
R
a
n
g
e
U Description
n
i
t
EG
PRS
N
/
A
N The grid map is rendered according

/ to the percentage of terminals that
A support the EGPRS frequency band
in the total number of terminals in the
grids.
Issue 03 (2015-07-30)

647
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
180
0
ban
d
N
/
A

A support the GSM 1800 frequency
band in the total number of terminals
in the grids.
GS
ME
ban
d
N
/
A

A support the E-GSM frequency band
in the total number of terminals in the
grids.
FD
DLTE
N
/
A

A support FDD-LTE in the total
number of terminals in the grids.
TD
DLTE
N
/
A

A support TDD-LTE in the total
DT
M
N
/
A

A support DTM in the total number of
terminals in the grids.
Issue 03 (2015-07-30)

648
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
8PS
K
mod
ulati
on
N
/
A

A support 8PSK modulation in the total
Upli
nk
exp
ansi
on
N
/
A

A support uplink expansion in the total
PS
han
dov
er
N
/
A

A support PS handover in the total
WiFi
N
/
A

A support Wi-Fi in the total number of
terminals in the grids.
4.7 GSM Cell Performance Analysis

Issue 03 (2015-07-30)

649
Nastar
4.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.
NOTE
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.
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.
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.
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.
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 03 (2015-07-30)

650
Nastar
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.
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.
Issue 03 (2015-07-30)

651
Nastar

User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

652
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
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.
NOTE
Issue 03 (2015-07-30)
Item
Execution type
One-time task

653
Nastar
Item
Network scale for one analysis

task
<= 2048 cells
<= 50
Time range for data in one

analysis task
7 days
<= 100 minutes

analysis data
7 days

analysis data
15 days
4.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.

l
You have applied for a valid license for GSM cell performance analysis.
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.
The login user is authorized to execute GSM cell performance analysis tasks and analyze
related NEs.

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 03 (2015-07-30)

654
Nastar
Data.
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

l
GSM RAN CS analysis:

GSM RAN PS analysis:

Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On
the User Identity Information Reporting Switch (GSM) in Nastar Commissioning
Guide.
4.7.3 Process of GSM Cell Performance Analysis

This section describes the process of GSM cell performance analysis.
l
Prerequisites
Process
Prerequisites
database. For detailed operations, see 4.7.2 Preparations for GSM Cell Performance
Analysis.
Process
Issue 03 (2015-07-30)

655
Nastar
Issue 03 (2015-07-30)

656
Nastar
Table 4-22 Description of the GSM cell performance analysis process

No.
Proced
ure
Description
Reference
(1)
Check
the
integrit
y of
analysi
s data

3.6 Checking
the Integrity
of Analysis
Data
Steps:
1. Set Data Type to GSM Cell Performance Analysis
Data.
3. Select query NEs.
4. Click Query.
window.
analysis task.
administrator to subscribe to the data by performing
(2).
NOTE
requirements. You are advised to contact the administrator
with subscription rights to perform the subscription
operation.
(2)
Subscri
be to
analysi
s data
(basic)
NOTE
The source data subscription function has high security
requirements. You are advised to contact the administrator to turn
on the data source switch.

Subscription Management.
3.5
Subscribing
to Analysis
Data
Steps:
1. Click the GSM tab in the displayed Data Subscription
Management window.
2. Select the NEs to be configured in the navigation tree.
3. Click Set on the Basic Subscription Settings tab page.
4. In the Basic Subscription Settings dialog box, set the
data source switch of Cell Performance Analysis Data
(CHR-CS) or Cell Performance Analysis Data
(CHR-PS) to ON.
5. Click Confirm.
Check the information in the Log Info area and ensure
that the data source switch is turned on.
Issue 03 (2015-07-30)

657
Nastar
No.
Proced
ure
Description
Subscri
be to
analysi
s data
(applic
ation)

Reference
Steps:
1. Click the GSM tab in the displayed Data Subscription
Management window.
3. Click ON on the Cell Performance Analysis tab page.
4. Set threshold parameters in the displayed Cell
Performance Analysis Parameter Setting window.
5. Click Confirm.
For details about parameters, see Subscription Task
Parameters
Check
the
integrit
y of
analysi
s data

Steps:
1. Set Data Type to GSM Cell Performance Analysis
Data.
3.6 Checking
the Integrity
of Analysis
Data

4. Click Query.
window.
analysis task.
technical support.
Issue 03 (2015-07-30)

658
Nastar
No.
Proced
ure
Description
Reference
(3)
Create
an
analysi
s task
Navigation path: Choose Theme Function > Network

Analysis > GSM Cell Performance Analysis in the
navigation tree of the Analysis Task Management
window.
l For
detailed
operations
, see 3.7
Creating
an
Analysis
Task
Steps:
1. Double-click GSM Cell Performance Analysis.
2. Set the task name and remarks. Then, click Next.
3. On the Select NE(s) tab page, select the NEs to be
analyzed and click Next.
4. Specify the time period. After the task is executed, the
Nastar obtains the analysis results for the specified time
period.
5. Click Finish.
(4)
View
analysi
s
results

Steps:
1. Right-click the result record and choose View Analysis
Result from the shortcut menu.
2. In the displayed GSM Cell Performance Analysis
window, view the analysis results matching the record.
View
indepth
analysi
s
results
Navigation path: In the window for showing analysis

icon, or right-click a cell in the
results, click the
navigation tree and choose In-depth analysis from the
shortcut menu.
Steps:
1. In the window for showing analysis results, click the
icon, or right-click a cell in the navigation tree and
choose In-depth analysis from the shortcut menu.
2. View the analysis results in the displayed Further
Analysis window.
NOTE
When you perform in-depth analysis on an existing cell
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 03 (2015-07-30)

l For
detailed
descriptio
n of the
parameter
s, see
Analysis
Task
Paramete
rs.
l For
detailed
operations
, see 3.8
Querying
Analysis
Results
l For
detailed
descriptio
n of the
window
for
showing
analysis
results,
see 4.7.4
Interface
Descripti
on: GSM
Cell
Performa
nce
Analysis.
659
Nastar
No.
Proced
ure
Description
Reference
(5)
Export
analysi
s
results
Navigation path: Click the export icon on the toolbar in

the upper left area of the GSM cell performance analysis
window.
l For
details,
see 3.10
Exportin
g
Analysis
Reports.
Steps:
2. Set the format and save path for exporting file.
3. Click Save.
l For details
on the
descriptio
n of the
window
for
showing
analysis
results,
see 4.7.4
Interface
Descripti
on: GSM
Cell
Performa
nce
Analysis.

Basic Subscription
Issue 03 (2015-07-30)

660
Nastar
Parameter
Description
Cell
Performance
Analysis Data
(CHR-CS)
You can click

NOTE
Issue 03 (2015-07-30)

661
Nastar
Parameter
Description
Cell
Performance
Analysis Data
(CHR-PS)
You can click
documentation.
Parameter
Vo
ice
Ser
vic
e
Issue 03 (2015-07-30)
Servi
ce
Quali
ty
Probl
em
Description
Uplink
VQI
Service quality problem indicating poor Um-interface quality:

Average value of the uplink Voice Quality Indicators (VQIs), or the
mean opinion score (MOS). This parameter indicates the voice
quality during a call. The value of the parameter ranges from 0 to
5. A higher value indicates better voice quality.

662
Nastar
Parameter
Description
Uplink
HQI

Average value of the uplink High Quality Indicators (HQIs).
In CHRs of the BSC6900 V900R011 or later:
HQI = Number of measurement reports with a received signal quality
(RxQual) of levels 0 to 3/Number of measurement reports with an
RxQual of levels 0 to 7 x 100%
In CHRs of the BSC6000 V900R008:
HQI = Number of measurement reports with an RxQual of levels 0
to 5/Number of measurement reports with an RxQual of levels 0 to
7 x 100%
Downli
nk HQI

Average value of the downlink HQIs.
In CHRs of the BSC6900 V900R011 or later:
7 x 100%
In CHRs of the BSC6000 V900R008:
7 x 100%
Dela
y
Probl
em
Issue 03 (2015-07-30)
Downli
nk VQI

Average value of the downlink VQIs, or the MOS. This parameter
indicates the voice quality during a call. The value of the parameter
ranges from 0 to 5. A higher value indicates better voice quality.
Percent
of
Uplink
Low
VQI
Time
Indicates the percent of call time of the low uplink VQI to the total
call time of the voice service.
Percent
of
Downli
nk Low
VQI
Time
Indicates the percent of call time of the low downlink VQI to the total
call time of the voice service.
Access
Delay
(MOC)
Delay problem indicating a long call access delay (mobileoriginated): Call access delay (mobile-originated) (s) - The access
duration for mobile-originated call spans from the time when a
terminal sends a Channel Request message to the time when the
terminal sends an Assignment Complete message.

663
Nastar
Parameter
Short
Call
Probl
em
Acce
ss
Cove
rage
Probl
em
Issue 03 (2015-07-30)
Description
Access
Delay
(MTC)
Delay problem indicating a long call access delay (mobileterminated): Call access delay (mobile-terminated) (s) - The access
duration for mobile-terminated call spans from the time when a
terminal sends a Channel Request message to the time when the
terminal sends an Assignment Complete message.
Call
Compl
etion
Delay
(Alteri
ng)
(MOC)
Delay problem indicating a long call completion delay (Alerting)

(mobile-originated): Call completion delay (Alerting) (mobileoriginated) (s) = Time when a mobile-originated subscriber starts
calling (time when the subscriber's terminal sends a Channel Request
message) - Time when the subscriber hears the alerting (time when
the terminal receives an Alerting message).
Call
Compl
etion
Delay
(Alteri
ng)
(MTC)
Delay problem indicating a long call completion delay (Alerting)

(mobile-terminated): Call completion delay (Alerting) (mobileterminated) (s) = Time when a mobile-terminated subscriber starts
calling (time when the subscriber's terminal sends a Channel Request
message) - Time when the subscriber hears the alerting (time when
the terminal receives an Alerting message).
Short
Call
(MOC)
Short call problem indicating short call (mobile-originated): A short

call (mobile-originated) (s) occurs when a caller's actual call duration
exceeds the threshold for mobile-originated short call. Caller's actual
call duration is calculated based on the following formula: Caller's
actual call duration = Timestamp of the DisConnect message -Timestamp of the Connect Acknowledge message.
Short
Call
(MTC)
Short call problem indicating a short call (mobile-terminated): A

short call (mobile-terminated) (s) occurs when a called party's actual
call duration exceeds the threshold for mobile-terminated short call.
Called party's actual call duration is calculated based on the
following formula: Called party's actual call duration = Timestamp
of the DisConnect message - Timestamp of the Connect
Acknowledge message.
TA on
Access
Access coverage problem indicating an abnormal TA on access: This

parameter indicates the value of the TA when a terminal sends a
Channel Request message.
RACH
Level
on
Access
Access coverage problem indicating an abnormal RACH level on

access: This parameter indicates the RACH level (dBm) when a
terminal sends a Channel Request message.

664
Nastar
Parameter
Da
ta
Ser
vic
e
Abno
rmal
Servi
ce
Inter
actio
n
Dela
y
Averag
e
Durati
on on
Service
Interac
tion
Respon
se
Abnormal service interaction delay indicating a long average

duration for making a service interaction response: The average
duration for making a service interaction response (s) covers the
duration for data transmission by using the downlink PDU, the
duration for data reception by using the uplink PDU, and the interval
between the time when data is transmitted by the using downlink
PDU and the time when the data is received by using uplink PDU.
Slow
Dow
nload
Spee
d
Downl
oad
Speed
Slow download speed indicating a slow download speed: Download

Speed (Kbit/s) = Number of bytes transmitted by using downlink
PDU/Duration for data transmission by using downlink PDU.
Trans
missio
n
Resour
ce
Satisfa
ction
Rate of
Downli
nk
Averag
e
SingleSlot
Throug
hput
Slow download speed indicating a slow download speed, judge

whether the download problem is caused by the transmission
resource.
Um
Quality
NonSatisfa
ction of
Downli
nk
Averag
e
SingleSlot
Throug
hput
Slow download speed indicating a slow download speed, judge

whether the download problem is caused by the Um interface.
Upload
Speed
Slow upload speed indicating a slow upload speed: Upload Speed

(Kbit/s) = Number of bytes transmitted by using uplink PDU/
Duration for data transmission by using uplink PDU.
Slow
Uplo
ad
Spee
d
Issue 03 (2015-07-30)
Description

665
Nastar
Parameter
Description
Trans
missio
n
Resour
ce
Satisfa
ction
Rate of
Uplink
Averag
e
SingleSlot
Throug
hput
Slow upload speed indicating a slow upload speed, judge whether

the upload problem is caused by the transmission resource.

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Issue 03 (2015-07-30)

666
Nastar
Parameter
Description
Select NE(s)

NOTE

Parameter
Description
Duration
Delay
immediately.
Execute on
4.7.4 Interface Description: GSM Cell Performance Analysis

This section describes the interface that displays the results of GSM cell performance analysis.
this interface.
Portal
l
Use either of the following methods to open the interface that displays the results of GSM
cell performance analysis (aggregated):
Select an executed GSM cell performance analysis task and double-click a result record
Select an executed GSM cell performance analysis task, right-click a result record in
the Task Result area, and choose from the shortcut menu.
Open the interface that displays the results of GSM cell performance analysis (in-depth):
On the aggregated analysis result interface, click
Further Analysis from the shortcut menu.
Issue 03 (2015-07-30)
, or right-click an NE and choose

667
Nastar
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 4-37 shows the analysis result interface.
Figure 4-37 Interface for cell performance analysis results
No.
Name
Button area
NE
navigation
tree
l Upper part: Type a cell name in the Search area to quickly locate
a cell.
Table of
exception
types
Displays the number of reports and ratio under each exception type
for the selected BSC or cell under each service type. This area is
displayed accordingly with Area 4.
Description
Click
cause.
to export analysis reports of all cells under each exception
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.
Right-click on the table and choose Save As from the shortcut menu
to export this table.
Issue 03 (2015-07-30)

668
Nastar
No.
Name
Description
Table of
exception
causes
Displays the number of reports and ratio under each exception cause
of an exception type for the selected BSC or cell. This area is
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 indepth analysis interface where you can view all abnormal call
records caused by this exception cause.
Table of
bottom N
users,
terminal
models, or
cells
Displays the number of reports related to bottom N users(N<=50),

terminal models(N<=50), or cells(N<=50) under an exception cause
for the selected BSC or cell.
l After you select a BSC in Area 2, this table displays the number
and ratio of reports caused by bottom N subscribers, terminals,
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 indepth analysis. All in-depth analysis results generated before the in-depth analysis is stopped will be
properly displayed.
4.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 03 (2015-07-30)

669
Nastar
Summary of Exception Types

Par
am
ete
r
Ra
nge
Un
it
Description
Ser
vice
Typ
e
Voi
ce
Ser
vice
N/
A
Service type of a cell exception.
15.0
Exc
epti
on
Typ
e
15.1
Sho
rt
Me
ssa
ge
l SRAN9.0/GBSS16.0/
RAN16.0
Dat
a
Ser
vice
RAN17.1
N/
A
RAN17.0
RAN18.0
N/
A
Classified analysis of exceptions

under a specific exception type.
15.0
For detailed description of the

exception types, see the following.
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Exc
epti
on
Occ
urre
nce
Tim
es
[0,
+
)
Nu
mb
er
Number of abnormal times under a

specific exception type.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

670
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Rati
o
(%)
[0.0
0,1
00.
00]
Proportion of the abnormal times

under a specific exception type in
all the abnormal call records.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Description of Exception Types-Voice Service

Par
am
ete
r
Ra
nge
Un
it
Description
Supported Solution
Version
Call
Set
up
Fail
ure
N/
A
N/
A
Failed call setup due to certain exceptions

when a terminal receives a Disconnect
message after sending a Channel Request
message.
l SRAN8.0/
GBSS15.0/RAN 15.0
l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

671
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Supported Solution
Version
Ab
nor
mal
Rel
eas
e
Bef
ore
Call
Co
mpl
etio
n
N/
A
N/
A
After sending a Channel Request message, a

terminal receives an Alerting message, but
fails to receive a Connect Acknowledge
message due to certain exceptions.
l SRAN8.0/
GBSS15.0/RAN 15.0
Ab
nor
mal
Call
Rel
eas
e
N/
A
l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
N/
A
Abnormal call release after a terminal gains

access to the network.
l SRAN8.0/
GBSS15.0/RAN 15.0
After a successful call setup, any of the

following indicates an abnormal call release:
l SRAN8.1/
GBSS15.1/RAN 15.1
1. The terminal receives a Disconnect

message that carries an abnormal cause
(indicating that this is a non-Normal
message).
l SRAN9.0/
GBSS16.0/RAN16.0
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).
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN11.0/
GBSS18.0/RAN18.0
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 03 (2015-07-30)

672
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Supported Solution
Version
Ser
vice
Qua
lity
Pro
ble
m
N/
A
N/
A
Any of the following exceptions that might

occur after a terminal gains access to the
network and successfully sends a Setup
message:
l SRAN8.0/
GBSS15.0/RAN 15.0
Poor Um-interface quality
l SRAN9.0/
GBSS16.0/RAN16.0
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
ay
Pro
ble
m
N/
A
N/
A
Any of the following delay problems that

might occur after a terminal gains access to
the network:
Long call access delay (mobile-originated)
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
rt
Call
Pro
ble
m
N/
A
N/
A
Short call that occurs when a terminal

attempts to access the network and initiate a
call.
A short call occurs when a 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
l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
l SRAN8.0/
GBSS15.0/RAN 15.0
l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
l SRAN8.0/
GBSS15.0/RAN 15.0
l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

673
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Supported Solution
Version
Acc
ess
Cov
era
ge
Pro
ble
m
N/
A
N/
A
Number of abnormal TA values and RACH

levels when a terminal attempts to access the
network.
l SRAN8.0/
GBSS15.0/RAN 15.0
You can set the exception threshold by using

l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Inc
omi
ng
Har
d
Han
dov
er
Fail
ure
N/
A
N/
A
Number of failed incoming hard handovers

when a subscriber is using a specific service.
Statistics on incoming hard handovers are
collected based on the target cell.
l SRAN8.0/
GBSS15.0/RAN 15.0
l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Out
goi
ng
Har
d
Han
dov
er
Fail
ure
N/
A
N/
A
Number of failed outgoing hard handovers

Statistics on outgoing hard handovers are
collected based on the source cell.
l SRAN8.0/
GBSS15.0/RAN 15.0
l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

674
Nastar
Issue 03 (2015-07-30)
Par
am
ete
r
Ra
nge
Un
it
Description
Supported Solution
Version
Inte
rSys
tem
Out
goi
ng
Han
dov
er
Fail
ure
(Int
raSys
tem
)
N/
A
N/
A
Number of failed outgoing inter-RAT

handovers from the current GSM network
(and the failures occur on the GSM network)
l SRAN8.0/
GBSS15.0/RAN 15.0
Inte
rSys
tem
Inc
omi
ng
Han
dov
er
Fail
ure
(Int
raSys
tem
)
N/
A
l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
N/
A
Number of failed call setups after a

subscriber is handed over from a non-GSM
network to a GSM network.
l SRAN8.0/
GBSS15.0/RAN 15.0
l SRAN8.1/
GBSS15.1/RAN 15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0

675
Nastar
Description of Exception Types-SMS

Par
am
ete
r
Ra
nge
Un
it
Description
SM
S
Req
uest
Fail
ure
(M
OC
)
N/
A
N/
A
Number of times that a mobileoriginated subscriber attempts to

access the network to use SMS
service fails.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
SM
S
Req
uest
Fail
ure
(M
TC)
N/
A
N/
A
Number of times that a mobileterminated subscriber attempts to

access the network to use SMS
service fails.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

676
Nastar
Description of Exception Types-Data Service

Par
am
ete
r
Ra
nge
Un
it
Description
Acc
ess
Fail
ure
N/
A
N/
A
Number of access fails when a

subscriber is using a data service.
15.0
Any of the following indicates a

access fail:
15.1
No Service Interaction Response
l SRAN9.0/GBSS16.0/
RAN16.0
Attach Failure
PDP Active Failure
AUC Failure
RAN17.0
RAN17.1
RAN18.0
Ser
vice
Inte
rrup
tion
N/
A
N/
A
Number of service interruptions

when a subscriber is using a data
service.
Any of the following indicates a
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
nor
mal
Ser
vice
Inte
ract
ion
Del
ay
N/
A
N/
A
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Any of the following serviceinteraction delay problems that

might occur when a subscriber is
using a data service.
15.0
Service interaction response times

out.
l SRAN9.0/GBSS16.0/
RAN16.0
The average duration for making a

service interaction response is
long.
RAN17.0
You can set the exception

thresholds by using the source data
Issue 03 (2015-07-30)
15.0

15.1
RAN17.1
RAN18.0
677
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Lo
w
Do
wnl
oad
Spe
ed
N/
A
N/
A
Any of the following download

rate problems that might occur
service:
15.0
Low download rate
l SRAN9.0/GBSS16.0/
RAN16.0

15.1
RAN17.0
RAN17.1
RAN18.0
Lo
w
Upl
oad
Spe
ed
N/
A
N/
A
Any of the following Upload rate

problems that might occur when a
subscriber is using a data service:
Low upload rate
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
TB
F
Ab
nor
mal
N/
A
N/
A
Displayed when any of the

following conditions is met:
15.0
Condition 1: The number of times

that the downlink TBF
establishment fails is greater than
0.
15.1

that the downlink TBF is
abnormally released is greater than
0.
RAN17.0

that the uplink TBF establishment
fails is greater than 0.
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.1
RAN18.0

that the uplink TBF is abnormally
released is greater than 0.
Issue 03 (2015-07-30)

678
Nastar
Data About Exception Causes

Par
am
ete
r
Ra
nge
Un
it
Description
Exc
epti
ona
l
Cau
se
N/
A
N/
A
Cause of exceptions under a

specific exception type.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Exc
epti
on
Occ
urre
nce
Tim
es
[0,
+
)
Nu
mb
er
Number of times that a specific

cause of certain exceptions is
reported.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Rati
o
(%)
[0.0
0,1
00.
00]
Proportion of a cause against the

number of exceptions under the
same exception type.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

679
Nastar
Description of Exception Causes

Par
am
ete
r
Ra
nge
Un
it
Description
Um
Inte
rfac
e
Qua
lity
Pro
ble
m/
MS
Fau
lt
N/
A
N/
A
Exceptions caused by poor Uminterface quality or terminal fault.
15.0
Sys
tem
Res
our
ce
Con
gest
ion
N/
A
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
N/
A
Exceptions caused by system

resource congestion.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Tra
nsm
issi
on
Fau
lt
N/
A
N/
A
Exceptions caused by transmission

fault.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

680
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
CN
Fau
lt
N/
A
N/
A
Exceptions caused by CN fault.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Oth
er
Cau
ses
N/
A
N/
A
Exceptions caused by other faults

except poor Um-interface quality,
terminal fault, system resource
congestion, transmission fault, and
CN fault.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Call
Dro
p
Due
to
HO
Fail
ure
N/
A
N/
A
Call drops caused by failed

handovers after a terminal gains
access to the network and sends a
Setup message.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

681
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Call
Dro
p
Due
to
Um
Inte
rfac
e
Pro
ble
ms
N/
A
N/
A
Call drops caused by poor Uminterface quality after a terminal

gains access to the network and
sends a Setup message.
15.0
Call
Dro
p
Due
to
Tra
nsm
issi
on
Fau
lt
N/
A
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
N/
A
Call drops caused by transmission

faults after a terminal gains access
to the network and sends a Setup
message.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Call
Dro
p
Due
to
CN
Fau
lt
N/
A
N/
A
Call drops caused by CN faults

after a terminal gains access to the
network and sends a Setup
message.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

682
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Pee
r
Call
Dro
p
N/
A
N/
A
Call drops caused by call drops of

the peer-end terminal after a
terminal gains access to the
message.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Call
Dro
p
Due
to
Oth
er
Cau
ses
N/
A
N/
A
Call drops caused by other faults

except failed handover, poor Uminterface quality, transmission
fault, CN fault, and peer-end
terminal fault after a terminal gains
Setup message.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Poo
r
Qua
lity
of
Um
Inte
rfac
e
N/
A
N/
A
Poor Um-interface quality caused

by the following KPIs after the
subscriber gains access to the
network and sends a Set Up
message (Call Setup Success).
Uplink VQI
Uplink HQI
Downlink HQI
thresholds for the KPIs by using the
source data subscription function.
For description of the KPIs, refer to
the description of source data
subscription.
Issue 03 (2015-07-30)

15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
683
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
UL
One
Wa
y
Au
dio
N/
A
N/
A
Uplink one-way audio event that

occurs after a terminal gains access
message.
15.0
The one-way audio test can only

detect one-way audio events
related to the channels within the
BSS (BTS<->TC) instead of those
related on the Um and A interfaces.
l SRAN9.0/GBSS16.0/
RAN16.0
15.1
RAN17.0
Principles for detecting uplink one- l SRAN10.1/GBSS17.1/

RAN17.1
way audio are as follows: The DSP
in the TC of the BSC performs
RAN18.0
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 03 (2015-07-30)

684
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
DL
One
Wa
y
Au
dio
N/
A
N/
A
Downlink one-way audio event

that occurs after a terminal gains
Setup message.
15.0

detect one-way audio events
related to the channels within the
BSS (BTS<->TC) instead of those
related on the Um and A interfaces.
l SRAN9.0/GBSS16.0/
RAN16.0
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.
RAN17.1
No-audio event that occurs after a

terminal gains access to the
message.
15.0
Mut
e
Call
N/
A
N/
A
15.1
RAN17.0
RAN18.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

685
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
UL
Cro
ssta
lk
N/
A
N/
A
Uplink crosstalk event that occurs

after a terminal gains access to the
message.
15.0
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.
l SRAN9.0/GBSS16.0/
RAN16.0
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.
RAN17.1
Downlink crosstalk event that

occurs after a terminal gains access
message.
15.0

crosstalk events related to the
channels within the BSS (BTS<>TC) instead of those related on the
l SRAN9.0/GBSS16.0/
RAN16.0
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
detected among the unique call
identifiers within the test period,
downlink crosstalk occurs.
RAN17.1
DL
Cro
ssta
lk
Issue 03 (2015-07-30)
N/
A
N/
A

15.1
RAN17.0
RAN18.0
15.1
RAN17.0
RAN18.0
686
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Ove
rlon
g
Acc
ess
Del
ay
(M
OC
)
N/
A
N/
A
Long delay for a mobile-originated

terminal to gain access to the
network.
15.0
Ove
rlon
g
Acc
ess
Del
ay
(M
TC)
Call access delay (mobileoriginated) (s) - The access

duration for mobile-originated call
spans from the time when the
terminal sends a Channel Request
terminal sends an Assignment
Complete message.
N/
A
N/
A
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
You can set the threshold for long

call access delay (mobileoriginated) by using the source data
RAN18.0
Long delay for a mobileterminated terminal to gain access

to the network.
15.0
Call access delay (mobileterminated) (s) - The access

duration for mobile-terminated call
spans from the time when the
terminal sends an Assignment
Complete message.
call access delay (mobileterminated) by using the source
data subscription function.
Issue 03 (2015-07-30)
15.1

15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
687
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Ove
rlon
g
Call
Co
mpl
etio
n
Del
ay
(Alt
erin
g)
(M
OC
)
N/
A
N/
A
Long duration spanning from the

time when a mobile-originated
subscriber initiates a call to the
time when the subscriber hears the
alerting.
15.0
Call completion delay (Altering)

(mobile-originated) (s) is the
duration spanning from the time
when the mobile-originated
subscriber initiates a call (namely,
when the subscriber's terminal
sends a Channel Request message)
to the time when the subscriber
hears the alerting (namely, when
the terminal receives the Alerting
message).
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0

call completion delay (mobileoriginated) by using the source data
Ove
rlon
g
Call
Co
mpl
etio
n
Del
ay
(Alt
erin
g)
(M
TC)
N/
A
N/
A
Long duration spanning from the

time when a mobile-terminated
subscriber initiates a call to the
time when the subscriber hears the
alerting.
Call completion delay (Altering)
(mobile-terminated) (s) is the
duration spanning from the time
when the mobile-terminated
subscriber initiates a call (namely,
when the subscriber's terminal
sends a Channel Request message)
to the time when the subscriber
hears the alerting (namely, when
the terminal receives the Alerting
message).
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0

call completion delay (mobileterminated) by using the source
Issue 03 (2015-07-30)

688
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Sho
rt
Call
(M
OC
)
N/
A
N/
A
Exception where a call lasts shortly

after a mobile-originated
network and successfully initiates
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).
15.0
You can set the short-call threshold

by using the source data
Sho
rt
Call
(M
TC)
N/
A
N/
A
Exception where a call lasts shortly

after a mobile-terminated
network and successfully initiates
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 shortcall threshold (Call duration =
Timestamp of the Disconnect
message - Timestamp of the
Connect Acknowledge message).
You can set the short-call threshold
Issue 03 (2015-07-30)

15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
689
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Ab
nor
mal
TA
on
Acc
ess
N/
A
N/
A
Abnormal value of the TA when a

message.
15.0
You can set the exception threshold

15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Ab
nor
mal
RA
CH
Lev
el
on
Acc
ess
N/
A
N/
A
Abnormal RACH level when a

message.
You can set the exception threshold
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

690
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
No
Ser
vice
Inte
ract
ion
Res
pon
se
N/
A
N/
A
Exception where no response to

service interaction is made when a
15.0
No response to service interaction

is made when the number of times
that the uplink PDU carries data but
the downlink PDU does not is
above threshold 1 for determining
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]).
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Thresholds 1 and 2 for determining

that no response to service
interaction is made are customized
algorithm parameters.
Att
ach
Fail
ure
N/
A
N/
A
Attach failure that occurs when a

15.0
Number of Attach Request

messages - Number of Attach
Accept messages > 0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

691
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
PD
P
Act
ive
Fail
ure
N/
A
N/
A
PDP activation failure that occurs

service.
15.0
Number of PDP Active Request

messages - Number of PDP Active
Accept messages > 0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
AU
C
Fail
ure
N/
A
N/
A
AUC failure that occurs when a

15.0
Number of Authentication and

ciphering req messages - Number
of Authentication and ciphering
resp messages > 0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Las
t
Ser
vice
Inte
rrup
ted
Due
to
Rou
ting
Are
a
Up
date
Issue 03 (2015-07-30)
N/
A
N/
A
Last service interruption caused by

routing area update.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0

692
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Ab
nor
mal
Inte
rrup
tion
on
Cell
Res
elec
tion
N/
A
N/
A
Exception that occurs when access

and reselection information area or
FLUSHLL exists.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)
Ser
vice
Inte
rrup
tion
s
Due
to
FL
US
H
LL
N/
A
Ser
vice
Inte
rrup
tion
s
Due
to
TB
F
Ab
nor
mal
N/
A
N/
A
Exception that occurs when RAN

exception information shows that
the number of abnormal downlink
interruptions on the RAN side is
greater than 0 and that the cause of
clearing the downlink LLC PDU
buffer is
PDU_REMOVE_FLUSH.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
N/
A
Exception that occurs when RAN

exception information shows that
the total number of abnormal
uplink and downlink interruptions
on the RAN side is greater than 0
(the interruptions occur because
the PDU is cleared due to timed-out
PDU removal and due to TBF
exceptions.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0

693
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Ser
vice
Inte
ract
ion
Res
pon
se
Tim
eou
t
N/
A
N/
A
Long duration for making a service

interaction response when a
15.0
The duration for making a service

interaction response is long if any
of the following exceeds its
specified threshold:
1. Duration for the downlink PDU
to transmit data.
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.
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Specific devices are equipped to

directly detect whether the
preceding duration or interval
exceeds its specified threshold.
Ove
rlon
g
Ave
rag
e
Dur
atio
n on
Ser
vice
Inte
ract
ion
Res
pon
se
Issue 03 (2015-07-30)
N/
A
N/
A
Long average duration for making

a service interaction response when
a subscriber is using a data service.
Average duration for making a
service interaction response =
Duration for data transmission by
using the downlink PDU +
Duration for data reception by
using the uplink PDU + Interval
between the data transmission by
using the downlink PDU and the
data reception by using the uplink
PDU
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
You can set the threshold by using

the source data subscription
function.

694
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Lo
w
Do
wnl
oad
Spe
ed
N/
A
N/
A
Low download rate when a

15.0
Download rate (kbit/s) = Number

of bytes transmitted by using the
downlink PDU/Duration for the
downlink PDU to complete
transmitting the bytes
15.1

function.
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Lo
w
Upl
oad
Spe
ed
N/
A
N/
A
Low upload rate when a subscriber

is using a data service.
15.0
Upload rate (kbit/s) = Number of

bytes transmitted by using the
uplink PDU/Duration for the
uplink PDU to complete
transmitting the bytes
15.1

function.
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
TB
F
Ab
nor
mal
N/
A
N/
A
Displayed when any of the

following conditions is met:
15.0

that the downlink TBF
establishment fails is greater than
0.
15.1

that the downlink TBF is
abnormally released is greater than
0.
RAN17.0

that the uplink TBF establishment
fails is greater than 0.
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.1
RAN18.0

that the uplink TBF is abnormally
released is greater than 0.
Issue 03 (2015-07-30)

695
Nastar
Analysis of Bottom Subscribers

Par
am
ete
r
Ra
nge
Un
it
Description
Use
r
Na
me
N/
A
N/
A
Unique identifier that the system

assigns to each bottom subscriber
troubled with exceptions.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Exc
epti
on
Occ
urre
nce
Tim
es
[0,
+
)
Nu
mb
er
Number of the exceptions that

trouble a subscriber under the
cause of a certain type of exception.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Rati
o
(%)
[0.0
0,1
00.
00]
Proportion of the exceptions that

trouble a subscriber in all the
exceptions.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

696
Nastar
Analysis of Bottom Terminal Models

Par
am
ete
r
Ra
nge
Un
it
Description
IM
EITA
C
000
000
00999
999
99
N/
A
Type identifier of a bottom

terminal troubled with exceptions.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Ter
min
al
Mo
del
N/
A
N/
A
Terminal model that is obtained by

using the terminal type
management function based on
IMEI-TAC.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Exc
epti
on
Occ
urre
nce
Tim
es
[0,
+
]
Nu
mb
er

trouble a certain type of terminal
under the cause of a certain type of
exception.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

697
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Rati
o
(%)
[0.0
0,1
00.
00]

trouble a terminal in all the
exceptions.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Analysis of Bottom Cells

Par
am
ete
r
Ra
nge
Un
it
Description
Cell
Ide
ntit
y
N/
A
N/
A
The identity of a bottom

problematic cell is in the following
format: LAC: CI.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

698
Nastar
Par
am
ete
r
Ra
nge
Un
it
Description
Cell
Na
me
1 to
64
cha
ract
ers
N/
A
Name of a bottom cell in which

exceptions occur.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Exc
epti
on
Occ
urre
nce
Tim
es
[0,
+
]
Nu
mb
er

occur in a cell under the cause of a
certain type of exception.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Rati
o
(%)
[0.0
0,1
00.
00]

occur in a cell in all the exceptions.
15.0
15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

699
Nastar
4.8 GSM Network Geographic Observation

4.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.
NOTE
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.
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 03 (2015-07-30)

700
Nastar
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.
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.
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.
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.
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 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 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 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 03 (2015-07-30)

701
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00

702
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

703
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
analysi
s task
Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for GSM Network Geographic Observation

of analysis time.
NOTE
Item
Execution type

analysis task
l <= 6000 cells (when the number of GSM basic licenses is less
than or equal to 50,000 TRXs)
l <= 12,000 cells (when the number of GSM basic licenses is
less than or equal to 100,000 TRXs)
l <= 18,000 cells (when the number of GSM basic licenses is
less than or equal to 150,000 TRXs)
Issue 03 (2015-07-30)
Number of allowed
analysis tasks

one analysis task
7 days

task
<= 60 minutes

15 days

704
Nastar
Item

15 days
4.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.

l
Check that you have applied for a valid license for GSM network geographic observation.
Check that you have the operation rights to subscribe to GSM network geographic
observation data upon login.
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.

Before analyzing, prepare the following basic data described in Table 4-24 for performing the
task successfully.
Issue 03 (2015-07-30)

705
Nastar
Table 4-24 Required basic data of network geographic observation

Data
Type
Function
Operation
Config
uratio
n Data
(Mand
atory)
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 3.4.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
eering
Param
eters
(Mand
atory)
Issue 03 (2015-07-30)
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.
In the navigation tree of the Analysis Task

Management window, choose System Function >
Engineering Parameter Management. Then doubleclick 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
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

706
Nastar
Data
Type
Function
Operation
Map
File
(Optio
nal)
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 3.4.4 Preparing the Map File
(Optional).

l
If you want to analyze the PS network geographic observation function, check that the PS
4.8.3 Process of GSM Network Geographic Observation

This section describes the process of GSM network geographic observation and each procedure
in the process.
l
Prerequisites
Process
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 4.8.2 Preparations for
GSM Network Geographic Observation.
Process
Issue 03 (2015-07-30)

707
Nastar
Issue 03 (2015-07-30)

708
Nastar
Table 4-25 Description of the network geographic observation process

No.
Proced
ure
Description
Reference
(1)
Check
whether
analysis
data is
integrat
ed

3.6 Checking
the Integrity
of Analysis
Data
Procedure:
1. Choose Data Type > Network Analysis > GSM
Network Geographic Observation Data(***).
*** indicates the data type including MR, CHR-CS,
and CHR-PS.
4. Click Query.
window.
analysis task.
(2).
NOTE
(2)
Subscri
be to
analysis
data
(basic)

Procedure:
1. Click the GSM tab in the Data Subscription
Management window.
3.5
Subscribing
to Analysis
Data

4. On the Basic Subscription Settings tab page, set the
data source switch of Network Geographic
Observation Data(CHR-CS), Network Geographic
Observation Data(CHR-PS), and Network
Geographic Observation Data(MR-CS) to ON.
By default, the data source switch is set to No
Modification.
5. Click Confirm.
Issue 03 (2015-07-30)

709
Nastar
No.
Proced
ure
Description
Subscri
be to
analysis
data
(applica
tion)

Reference
Procedure:
1. Click the GSM tab in the Data Subscription
Management window.
3. Click ON on the Network Geographic Observation
tab page.
4. Set the threshold parameters in the displayed Network
Geographic observation Analysis Parameter
Setting dialog box.
For detailed operations, see Subscription Task
Parameters.
5. Click Confirm.
Check
whether
analysis
data is
integrat
ed

Procedure:
1. Choose Data Type > Network Analysis > GSM
*** indicates the data type including MR, CHR-CS,
and CHR-PS.
3.6 Checking
the Integrity
of Analysis
Data

4. Click Query.
window.
analysis task.
technical support.
Issue 03 (2015-07-30)

710
Nastar
No.
Proced
ure
Description
Reference
(3)
Create
an
analysis
task

Analysis > GSM Network Geographic Observation in
the navigation tree of the Analysis Task Management
window.
l For
details,
see 3.7
Creating
an
Analysis
Task.
Procedure:
1. Double-click GSM Network Geographic
observation.
2. Specify the task name and remarks. Then, click Next.
3. On the Grid Resolution Settings tab page, select the
Grid Resolution for displaying terminal geographic
observation results.
analyzed. Then, click Next.
Nastar obtains the observation results for the specified
time period.
l For details
about the
parameter
s, see
Analysis
Task
Paramete
rs.
6. Click Finish.
(4)
View
analysis
results

Procedure:
1. Right-click the result record and choose Network
Geographic Observation from the shortcut menu.
2. In the Geographic Observation window, view the
observation results matching the record.
Issue 03 (2015-07-30)

l For
details,
see 3.8
Querying
Analysis
Results.
l For details
on the
descriptio
n of the
window
for
showing
analysis
results,
see 4.8.4
Interface
Descripti
on: GSM
Network
Geograp
hic
Observat
ion.
711
Nastar
No.
Proced
ure
Description
Reference
(5)
Export
analysis
results
Navigation path: Click the icon on the button area in the

upper left part of the Geographic observation window.
l For
details,
see 3.10
Exportin
g
Analysis
Reports.
Procedure:
1. Click the export icon on the button area.
2. Set the export format and path of a file, and the export
counter and range of data.
3. Click Save.
l For details
on the
descriptio
n of the
window
for
showing
analysis
results,
see 4.8.4
Interface
Descripti
on: GSM
Network
Geograp
hic
Observat
ion.

Basic Subscription
Issue 03 (2015-07-30)

712
Nastar
Parameter
Description
Network
Geographic
Observation
Data (CHRCS)
You can click

NOTE
Issue 03 (2015-07-30)

713
Nastar
Parameter
Description
Network
Geographic
Observation
Data (CHRPS)
You can click
documentation.
Network
Geographic
Observation
Data (MRCS)
Switch for enabling or disabling the reporting of CS MR data. You can retain
You can click
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 03 (2015-07-30)

714
Nastar
Parameter
Description
Value Range
Traffic Down
Link RxQual
>= X
Indicates the threshold for poor quality traffic.
X: an integer
between 0 and 7. The
default value is 6.
The Nastar obtains the data that shows a downlink

receive quality greater than or equal to X.
X indicates the level of downlink receive quality.
Down Link
RxQual >= X
and Down Link
RxLev (dBm)
<= Y
Indicates the threshold for poor downlink coverage X: an integer

and low quality.
The Nastar obtains the data that shows a downlink default value is 6.
receive quality greater than or equal to X and a
receive level smaller than or equal to Y.
X indicates the level of downlink quality.
Y: -110.0~0.0. The
default value is
-90.0.
Y indicates the downlink level.

Up Link
RxQual >= X
and Up Link
RxLev (dBm)
<= Y
Indicates the threshold of poor uplink coverage and

low quality.
The Nastar obtains the data that shows an uplink
receive quality greater than or equal to X and an
uplink receive level smaller than or equal to Y.
X indicates the level of uplink quality.
X: an integer
default value is 6.
Y: -110.0~0.0. The
default value is
-95.0.
Y indicates the uplink level.

Absolute
Down Link
RxLev
between Main
cell and
Neighboring
Cell (dB) < X
Satisfy Cell
Count >= Y
Issue 03 (2015-07-30)
Indicates non-dominant cells.

If the absolute value of the downlink receive level
difference between a serving cell and its
neighboring cell is smaller than X, the serving cell
is regarded as an area without a dominant cell.
The Nastar obtains the number of neighboring cells,
which meet conditions of non-dominant cells. The
number of neighboring cells is greater than or equal
to Y.

X: an integer from 1
to 20. The default
value is 5.
Y: an integer from 1
to 6. The default
value is 2.
715
Nastar
Parameter
Description
Value Range
X < Up Link
RxLev(dBm)
<= Y and Up
Link RxQual
>= P or
Defines the uplink interference threshold.
l X and Y: an
integer from
-110.0 to 0.0 and
by default they
are -90.0 and
-85.0.
P: an integer
from 0 to 7 and
by default it is 7.
The Nastar obtains the data that shows an uplink

receive level ranging from X to Y and an uplink
receive quality greater than or equal to P, the data
that shows an uplink receive level ranging from M
to N and an uplink receive quality greater than or
equal to Q, or the data that shows an uplink receive
level greater than Z and an uplink receive quality
greater than or equal to R.
M < Up Link
RxLev(dBm)
<= N and Up
Link RxQual
>= Q or
Up Link
RxLev(dBm) >
Z and Up Link
RxQual >= R
l M and N: an
integer from
-110.0 to 0.0 and
by default they
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 03 (2015-07-30)

716
Nastar
Parameter
Description
Value Range
X < Down Link

RxLev(dBm)
<= Y and Down
Link RxQual
>= P or
Defines the downlink interference threshold.
l X and Y: an
integer from
-110.0 to 0.0 and
by default they
are -90.0 and
-85.0.
P: an integer
from 0 to 7 and
by default it is 7.
M < Down
Link Rxlex
(dBm) <= N
and Down Link
ReQual >= Q
or
The Nastar obtains the data that shows a downlink

receive level ranging from X to Y and a downlink
receive quality greater than or equal to P, the data
that shows a downlink receive level ranging from
M to N and a downlink receive quality greater than
or equal to Q, or the data that shows a downlink
receive level greater than Z and a downlink receive
quality greater than or equal to R.
l M and N: an
integer from
-110.0 to 0.0 and
by default they
are -85.0 and
-80.0.
Q: an integer
from 0 to 7 and
by default it is 6.
Down Link
RxLev(dBm) >
Z and Down
Link RxQual
>= R
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.

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

Issue 03 (2015-07-30)

717
Nastar
NE information
Parameter
Description
Select NE(s)

l <= 6000 cells (when the number of GSM basic licenses is less than or
equal to 50,000 TRXs)
l <= 12,000 cells (when the number of GSM basic licenses is less than
or equal to 100,000 TRXs)
l <= 18,000 cells (when the number of GSM basic licenses is less than
or equal to 150,000 TRXs)
NOTE
Parameter
Description
Grid Resolution
Settings

results.
100m*100m.

Parameter
Description
Duration
Delay
immediately.
Busy hours
Issue 03 (2015-07-30)

718
Nastar
Parameter
Description
Execute on

Param
eter
Description
Note
Start
time

Period

Value range: 1 to 7 Days.
Repeat
times

Delay
by
(hours)
Whole
day

NOTE

hours.

time and Period. 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.
NOTE
at the start time.
01/01/2013 14:00:00, Start time is
03:00:00.
01/02/2013 14:00:00, Start time is
executes the task.

parameter.
Issue 03 (2015-07-30)

719
Nastar
Param
eter
Description
Busy
hours
If you set this parameter, the system

in each period.
Note

busy time.
4.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
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 4-40 shows the interface that displays network geographic observation results on grid
maps.
Issue 03 (2015-07-30)

720
Nastar
Figure 4-40 Interface for GSM network geographic observation results
NOTE
This section describes only the functions supported by GSM network geographic observation. For detailed
operations of each function, see 3.2.3 Interface Description: Geographic Observation Results.
Issue 03 (2015-07-30)
N
o.
Item
Description
Button
area

721
Nastar
N
o.
Item
Description
Navigation
tree

NOTE
If you need to delete all sites in a network system, click Remove through the
layer management function.

map interface.
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.
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.
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 display setting function available in the shortcut
menu to reset the grid display effect or the number of measurement
reports (MRs) to be filtered within a grid.
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
Issue 03 (2015-07-30)

722
Nastar
N
o.
Item
Description
NE tab page: enables you to select the NEs of the displayed
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).
Geographi
c
observatio
n area
l Displays the analysis results of selected KPIs on grid maps using

distinct colors by default. However, only the analysis results of the last
selected KPI are visible.
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.
, the
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
Details
area
Displays selected KPIs on different tab pages. Each tab page shows the
contribution values of the Top 5 cells related to a selected grid under this
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 03 (2015-07-30)

723
Nastar
N
o.
Item
Description
Legend
details area
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.
Informatio
n area
The interface displays no information when it is opened. If you select a

grid, the values of selected KPIs are displayed in all the cells in this gird.
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.
4.8.5 Parameters for Viewing GSM Network Geographic

Observation Results
This section describes the parameters for viewing GSM network geographic observation results.
Read this section before viewing GSM network geographic observation results.
Network Coverage Map

Parameter
Range
Unit
Description
Supported
Solution
Version
Primary
Serving Cell
(G)
N/A
N/A
The traffic map is rendered based on the

cells that serve as primary serving cells
most frequently in MRs in the raster
view. If some cells serve as primary
serving cells for the same number of
times, the traffic map is rendered based
on the primary serving cell in the MR
last reported.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

724
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
UL
Coverage
Strength(G)
[-110,47]
dBm

average uplink received signal strength
(RSS) in the MRs in the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DL
Coverage
Strength(G)
[-110,47]
dBm

average downlink receive signal
strength (RSS) in the MRs in the raster
view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

725
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
UL Poor
Coverage
Low Quality
(G)
[0.00,1
00.00]

percentage of the MRs with poor uplink
quality (quality level higher than 6) and
low uplink level (RSS lower than -95
dBm) in all the MRs in the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DL Poor
Coverage
Low Quality
(G)
[0.00,1
00.00]

percentage of the MRs with poor
downlink quality (quality level higher
than 6) and low downlink level (RSS
lower than -90 dBm) in all the MRs in
the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

726
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
UL
Interference
Area(G)
[0.00,1
00.00]

percentage of the uplink interference
MRs in all the MRs in the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Uplink interference: Interference is

manifested by a strong received signal
level (RSL) and a low received signal
quality (RxQual). The Nastar divides
the uplink RSL ranging from 110 dBm
to 0 dBm into several intervals. In each
interval, uplink interference occurs if
the RxQual is above a specified RxQual
class (a higher RxQual class indicates a
lower RxQual and a higher possibility
that interference occurs).
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DL
Interference
Area(G)
[0.00,1
00.00]

percentage of the downlink interference
MRs in all the MRs in the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Downlink interference: Interference is

manifested by a strong RSL and a low
RxQual. The Nastar divides the
downlink RSL ranging from -110.0
dBm to 0 dBm into several intervals. In
each interval, downlink interference
occurs if the RxQual is above a
specified RxQual class (a higher
RxQual class indicates a lower RxQual
and a higher possibility that interference
occurs).
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

727
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
LAC
Stability(G)
[0.00,1
00.00]

percentage of the MRs (in which a
specific LAC that maps to the most
serving cells resides) in all the MRs in
the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
No
Dominance
Serving Cell
Area(G)
[0.00,1
00.00]

percentage of the MRs containing no
dominant cell in all the MRs in the raster
view.
If the number of neighboring cells with
not more than 5 dB signal level
difference for the serving cell is equal
to or greater than a specific threshold
(by default, the value of the threshold is
2), this area is considered as an area
without a dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

728
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Confidence
Level(G)
[0.00,1
00.00]

theoretical precision of the positioning
method used by MRs and on the
percentage of MRs of specified high
confidence levels in all MRs in the
raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
All MRs are positioned based on the

following levels that are divided by
theoretical precision: A, B, C, D, and E.
You can specify N (N > 5) high
confidence levels.
l SRAN9.0/
GBSS16.0/
RAN16.0
l Lev_A: indicates a precision of 50

m to 80 m. It is used for positioning
MRs reported only by AGPS or
distributed base stations.
l Lev_B: indicates a precision of 80 m
to 120 m. It is used for RRT
triangular positioning or for highscore feature database-based
matching.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l Lev_C: indicates a precision of 120

MRs related to three neighboring
cells that are served by different base
stations.
l Lev_D: indicates a precision of 200
MRs reported by two base stations.
l Lev_E: indicates a precision of over
350 m. It is used for positioning MRs
in any other scenarios, for example,
for positioning MRs reported by one
base station.
Issue 03 (2015-07-30)

729
Nastar
Network Traffic Map

Parameter
Range
Unit
Description
Supported
Solution
Version
Voice
Traffic
Distribution
(G)
[0,+)
Num
ber

number of MRs of the voice service in
the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PoorQuality
Traffic
Distribution
(G)
[0,+)
Num
ber
If the percentage of the MRs containing

voice services whose quality level is
lower than a specified threshold (which
is 6 by default) in all the MRs in the
raster view is higher than a specified
threshold (which is 10% by default), the
traffic map is rendered based on the
MRs of voice services with poor signal
quality in the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

730
Nastar
Network Event Map

Parameter
Range
Unit
Description
Supported
Solution
Version
Call Drops
(G)
[0,+)
Num
ber

number of call drops in the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HO Failures
(G)
[0,+)
Num
ber

number of failed handovers in the raster
view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

731
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
UL PS
Access
Failures(G)
[0,+)
Num
ber

number of uplink PS access failures in
the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DL PS
Access
Failures(G)
[0,+)
Num
ber

number of downlink PS access failures
in the raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

732
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
UL PS Call
Drops(G)
[0,+)
Num
ber

number of uplink PS call drops in the
raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DL PS Call
Drops(G)
[0,+)
Num
ber

number of downlink PS call drops in the
raster view.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
4.9 VIP Analysis

Issue 03 (2015-07-30)

733
Nastar
4.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.
NOTE
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.
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.
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.
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 allsignaling analysis on a few VIP subscribers.
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.
Issue 03 (2015-07-30)

734
Nastar
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.
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.
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.
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:
l
Engineers can learn about VIP subscribers' service preferences by analyzing the trend of
their service usage.
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.
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 4-26.
Issue 03 (2015-07-30)

735
Nastar
Table 4-26 Description of VIP all-signaling analysis

Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
GS
M
<= 500/BSC
l All-signaling
analysis on CS
services: A
interface
(3GPP-48.008)
signaling, Abis
interface
(3GPP-48.058)
signaling, and
Um interface
(3GPP-44.018/
44.060)
signaling.
If you want to view

the all signaling
information on CS
domain, check that
the matching
BSC6900 version
is V900R011C00
or later. If you want
to view the all
signaling
information on PS
domain, check that
the matching
BSC6900 version
is V900R014C00
or later.
For VIP
subscribers of
Important level
who subscribe to
all-signaling data, a
complete signaling
procedure will be
displayed in the indepth analysis
function, and you
can double-click a
signaling record
and then analyze
detailed signaling
contents in the
displayed window.
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.
l All-signaling
analysis on PS
services: Gb
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 03 (2015-07-30)

736
Nastar
Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
UM
TS
l <= 100/RNC
(BSC6900
V900R013C0
0 or later
version)
Iu interface (3GPP
TS 25.413)
signaling, Iur
interface (3GPP TS
25.423) signaling,
Iub interface
(3GPP TS 25.433)
signaling, Uu
interface (3GPP TS
25.331) signaling.
If you want to view

the all signaling
information, check
that the matching
BSC6900 version
is V900R013C00
or later.
For VIP
subscribers of
Important level
who subscribe to
complete signaling
procedure will be
displayed in the
deep analysis
function, you can
double-click a
signaling record
and then analyze
detailed signaling
contents in the
displayed window.
l <= 500/RNC
(BSC6900
V900R016C0
0 or later
version)
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.
Issue 03 (2015-07-30)

737
Nastar
Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
LTE
<= 500/HSS
Signaling
messages on the
S1-MME interface
(3GPP
specifications 36.423), X2
interface (3GPP
specifications 36.413), and Uu
interface (3GPP
specifications 36.331).
LTE3900
V100R008C00 or
later; U2000/
M2000
V200R013C00SP
C230 or later;
HSS9860
V900R008C01 or
later.
The in-depth
analysis function
displays signaling
procedures in
charts and allows
you to double-click
a signaling
message and
analyze details
about the signaling
message in the
displayed window.
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.
Note: This function

allows you to
analyze the
signaling
procedures,
including RRC
connection setup
and release, eRAB
setup and release,
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 03 (2015-07-30)
Note: You can

analyze the key
signaling
procedures of
common
subscribers other
than the 500
Important VIP
subscribers only in
LTE3900
V100R005C00SP
C370 or later.

738
Nastar
Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
Mult
iRAT
netw
orks
<= 500 of all the

RATs on the
entire network.
VIP subscribers
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 03 (2015-07-30)

739
Nastar
NOTE
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.
the Encryption Key.
On the PS Core network, the CHR data includes the SGSN/MME CHR data and the GGSN/SAE-GW
CHR data.
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
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking
scheme.
Issue 03 (2015-07-30)

740
Nastar
Figure 4-41 Principle for analysis function
Issue 03 (2015-07-30)

741
Nastar
Table 4-27 Description of VIP analysis

User
Oper
ation
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
1.
Subscr
ibe to
basic
data.
GSM
/
UMT
S
netw
ork
Issue
basic
data
subscri
ption
comma
nds
(GSM/
UMTS
).
Nast
ar
Serv
er
eSA
U
To turn on the data source switch on the NE side.

After a user enables the basic data subscription
function (GSM VIP analysis or UMTS VIP
analysis) on the Nastar client, the Nastar issues
basic data subscription commands to the eSAU.
Issue
MML
comma
nds.
eSA
U
U200
0/
M20
00
To issue MML commands to the U2000/

M2000.
Forwar
d
MML
comma
nds.
U20
00/
M20
00
BSC/
RNC
To forward MML commands to the NEs through

the U2000/M2000, requesting the NEs to
generate raw data.
Upload
raw
data.
BSC/
RNC
SAU
Issue
basic
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

function (PS Core VIP analysis) on the Nastar
client, the Nastar issues basic data subscription
commands to the eSAU.
Issue
MML
comma
nds.
eSA
U
U200
0/
M20
00

M2000.
Forwar
d
MML
comma
nds.
U20
00/
M20
00
SGS
N/
MM
E
To forward MML commands to NEs, requesting

the NEs to generate raw data.
PS
Core
netw
ork
Issue 03 (2015-07-30)

742
Nastar
User
Oper
ation
Scen
e
LTE
netw
ork
Proce
dure
Sour
ce
Dest
inati
on
Purpose
Upload
raw
data.
SGS
N/
MM
E/
GGS
N/
SAE
-GW
PS
SAU
To upload the raw data to the PS SAU.
Issue
basic
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

function (LTE VIP analysis) on the Nastar client,
the Nastar issues basic data subscription
Issue
subscri
ption
comma
nds.
eSA
U
U200
0/
M20
00
To issue subscription commands to the U2000/

M2000.
Forwar
d
subscri
ption
comma
nds.
U20
00/
M20
00
eNod
eB
l For VIP summary/in-depth/trend analysis:

The U2000/M2000 issues subscription
commands to the eNodeB, requesting
eNodeBs to generate eNodeB CHRs.
Upload
raw
data.
eNod
eB/
MM
E
NOTE
The generation and transmission of the GGSN/SAEGW CHR data is not triggered by Nastar subscription
commands. The GGSN/SAE-GW CHR data will be
uploaded to the PS SAU through Huawei internal
protocols in real time after the CHR data switch is
enabled.
l For VIP all-signaling analysis: The U2000/

M2000 issues subscription commands to the
HSS, and the HSS then requests eNodeBs to
generate all-signaling trace data for single
subscribers through the MME.
Trace
Serve
r/
LTE
SAU
l To upload the raw data (eNodeB CHR and

eNodeB single-subscriber all-signaling data)
from the eNodeB to the Trace Server.
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 Nastar subscription
commands. 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 03 (2015-07-30)

743
Nastar
User
Oper
ation
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
2.
Subscr
ibe to
applic
ation
data.
GSM
/
UMT
S
netw
ork
Issue
applica
tion
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U
To deliver a data-preprocessing request to the

eSAU. After a user enables the application data
subscription function (GSM VIP analysis or
UMTS VIP analysis) on the Nastar client, the
Nastar issues data-processing commands to the
eSAU.
Deliver
a dataprepro
cessing
task
(direct)
.
eSA
U
SAU

SAU, requesting the SAU to start the datapreprocessing task.
Upload
prepro
cessed
data
(direct)
.
SAU
eSA
U
Issue
applica
tion
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

subscription function (PS Core VIP analysis) on
the Nastar client, the Nastar issues dataprocessing commands to the eSAU.
Deliver
a dataprepro
cessing
task
(direct)
.
eSA
U
PS
SAU
To deliver a data-preprocessing request to the PS

SAU, requesting the PS SAU to start the datapreprocessing task.
Upload
prepro
cessed
data
(direct)
.
PS
SAU
eSA
U
PS
Core
netw
ork
Issue 03 (2015-07-30)

744
Nastar
User
Oper
ation
Issue 03 (2015-07-30)
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
LTE
netw
ork
Issue
applica
tion
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

subscription function (LTE VIP analysis) on the
Nastar client, the Nastar issues data-processing
Deliver
a
prepro
cessing
task
(direct)
.
eSA
U
LTE
SAU
To deliver a data-preprocessing task to the LTE

SAU, requesting the LTE SAU to start the datapreprocessing task.
Upload
prepro
cessed
data
(direct)
.
LTE
SAU
eSA
U
To upload preprocessed data to the eSAU after

obtaining the data from Trace Server and
preprocessing the data.
Issue
data
query
comma
nds.
Nast
ar
Serv
er
eSA
U
To enable the data maintenance function. After

a user enables the data maintenance function on
the Nastar client, the Nastar checks whether the
analysis data is ready on the eSAU.
Return
data
query
results.
eSA
U
Nasta
r
Serve
r
To return data integrity check results to the

Nastar server and display the results on the
Nastar client.
Issue
task
executi
on
comma
nds.
Nast
ar
Serv
er
eSA
U
To deliver a task execution request to the eSAU.

After a user creates an analysis task on the Nastar
client, the Nastar server issues task execution
commands to the eSAU, requesting the eSAU to
aggregate data.
Upload
data
analysi
s
results.
eSA
U
Nasta
r
Serve
r
To aggregate the data reported by SAUs,

generate data analysis results, and upload the
data analysis results to the Nastar server.
3.
Check
the
integri
ty of
analys
is data.
4.
Create
and
execut
e an
analys
is task.

745
Nastar
User
Oper
ation
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
5.
View
analys
is
results
.
Displa
y
analysi
s
results.
Nasta
r
Serve
r
Technical Specifications for VIP Analysis

of analysis time.
NOTE
Item
Execution type
One-time or periodic task

analysis task
Maximum management capacity of the Nastar
Number of subscribers
allowed in one analysis
task
30,000 VIP subscribers (when aggregation analysis and indepth analysis are supported)
Number of allowed
analysis tasks
l 300 one-time tasks (for all RATs)
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.
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.

one analysis task
Issue 03 (2015-07-30)
l 7 days (one-time task)

l 30 days (periodic task)

746
Nastar
Item

task
l GSM: 75 minutes
l UMTS: 90 minutes
l LTE: 10 minutes
l PS Core: 25 minutes

l GSM: 30 days
l UMTS: 30 days
l LTE: 30 days
l PS Core: 30 days

l GSM: 30 days
l UMTS: 30 days
l LTE: 30 days
l PS Core: 30 days
4.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
Checking the Data Source Environment

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 4-28.
Issue 03 (2015-07-30)

747
Nastar
Table 4-28 Required license and rights of VIP analysis

Functi
on
Required license
Required rights (Security > Security

Management > User)
Data
subscri
ption
manage
ment
l GSM/UMTS/LTE
FDD/LTE TDD/PS
Core basic function
license
l Function operation rights

Operation Rights > Operation > Nastar
System Task Management > Data
Subscription Management Authentication
NOTE
l When the number of
cells controlled by the
LTE basic license and
the number of online
users reach the upper
limits, the Alarm
dialog box is
displayed, prompting
you to upgrade the
license. When you
query the license
consumption in the
license Information,
the result is not
consistent with that
displayed in the
Alarm dialog box
because the exceeded
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
the license in a timely
manner.
l Operation rights of NEs to be analyzed

Assign Operation Rights of Objects > NE
Object Authentication > *** NE Operation
Rights. *** refers the NEs to be subscribed.
l Operation rights of VIP users to be analyzed
Assign Operation Rights of Objects > VIP
Group Authentication > *** VIP Group
Operation Rights *** refers the VIP groups to
be analyzed.
Subject Management > *** VIP Analysis
Operation Rights. *** refers the RAT.
l LTE Periodic MR
Period Setting is
only available to an
account in the
Administrators group
or a user with data
subscription
management
permission.
l GSM/UMTS/LTE
FDD/LTE TDD/PS
Core VIP analysis
license
Issue 03 (2015-07-30)

748
Nastar
Functi
on
Required license

Management > User)
NOTE
l You need to obtain the
licenses for basic
functions and VIP
analysis related only to
the desired RATs instead
of all RATs.
l The license for the basic
functions related to an
RAT is the basis for all
functions related to this
RAT, which means the
RAT depends on the
availability of the license
for the basic functions
related to this RAT.
GSM
VIP
analysi
s
l GSM basic function

license
l GSM VIP analysis
license

Subject Management > GSM VIP Analysis
Operation Rights
Rights *** refers the NEs to be analyzed.
Operation Rights. *** indicates the VIP group
to which VIP subscribers to be analyzed belong.
l Automatical Delivering User Authentication
Assign Operation Rights of Objects >
Automatical Delivering User Authentication.
l Geographic Observation
System Task Management > Geographic
Observation.
Issue 03 (2015-07-30)

749
Nastar
Functi
on
Required license

Management > User)
UMTS
VIP
analysi
s
l UMTS basic function

license

Subject Management > UMTS VIP Analysis
Operation Rights
l UMTS VIP analysis

license

Observation.
Issue 03 (2015-07-30)

750
Nastar
Functi
on
Required license

Management > User)
LTE
TDD
VIP
analysi
s
l LTE TDD basic

function license

Subject Management > LTE TDD VIP
Analysis Operation Rights
NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.
l Operation rights of the NE group to which NEs

to be analyzed belong
Group Object Authentication > *** NE Group
Operation Rights. *** indicates the NE group
to which NEs to be analyzed belong.
Observation.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.
l LTE TDD VIP analysis

license
l (Optional) LTE TDD
CSFB analysis license,
only for controlling the
display of the CSFB
counters.
VoLTE analysis
license, only for
controlling the display
of the VoLTE counters.
Issue 03 (2015-07-30)

751
Nastar
Functi
on
Required license

Management > User)
LTE
FDD
VIP
analysi
s
l LTE FDD basic

function license

Subject Management > LTE FDD VIP
NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.

Observation.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.
l LTE FDD VIP analysis

license
l (Optional) LTE FDD
display of the CSFB
counters.
VoLTE analysis
license, only for
Issue 03 (2015-07-30)

752
Nastar
Functi
on
Required license

Management > User)
PS
Core
VIP
analysi
s
l PS Core basic function

license

Subject Management > PS Core VIP Analysis
Operation Rights
l PS Core VIP analysis

license
l (Optional) SGSN/MME
VoLTE signaling
analysis license
l (Optional) GGSN/SAEGW VoLTE signaling
analysis license
display of the CSFB
counters.

Observation.
Issue 03 (2015-07-30)

753
Nastar
Functi
on
Required license

Management > User)
GSM/
UMTS/
LTE
TDD/
LTE
FDD/
PS
Core
combin
ed
analysi
s
l GSM/UMTS/LTE
FDD/LTE TDD/PS
Core basic function
license

Have both involved licenses of VIP Analysis
Operation Rights of combined analysis.
NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.
l Operation rights of NEs and VIP groups to be

analyzed is the same as the rights of VIP analysis
of each network.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.
l GSM VIP analysis

license
l UMTS VIP analysis
license
license
license
license
Issue 03 (2015-07-30)

754
Nastar
Functi
on
Required license

Management > User)
Comm
on
To control the User Identity right, otherwise, you can

not view the integrated IMSI information.
Function operation rights: Operation Rights >
Select > Nastar Application > Operation > Nastar
Security Information Management > User
Identity
Viewing rights of theme data to be analyzed:
Operation Rights > Select > Operation > Nastar
System Task Management > Viewing Rights of
Data Maintenance and Management: to control
the viewing rights of the VIP Analysis page during
task creation.

task successfully.
Table 4-29 Required basic data of VIP analysis
Data
Type
Function
Operation
Config
uratio
n Data
(Mand
atory)

analysis cell allows the
Nastar to correctly obtain
detailed call data from the
network and analyze cell
information in MR
reports and information
about the following cells:
cells to which subscribers
have gained access, cells
which subscribers have
released, and cells to
handed over.

Data.

NOTE
If you only perform the PS Expired configuration data may cause incorrect cell
Core VIP analysis, you do
not need the configuration
data.
Issue 03 (2015-07-30)

755
Nastar
Data
Type
Function
Operation
VIP
Infor
matio
n
(Mand
atory)
VIP information includes

VIP user and IMSI
information. Before
subscribing to VIP
analysis data, create a
VIP group so that you can
perform analysis on and
ensure the service quality
of multiple VIP users in
the VIP group.
For details, see 3.4.6 Managing VIP Groups or VIP

Users (VIP Analysis).
NOTE
Generally, you obtain the IMSI and MSISDN of a VIP
subscriber and enter them into the Nastar.
If telecom operators have high requirements for subscriber
information security and the anonymization policy is enabled
on the network where the Nastar is deployed, all subscriber
information such as IMSI, MSISDN, and IMEI contained in
the analysis data will be encrypted. To protect the securitysensitive subscriber information, 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
Software Center > Tool > Mini-tool Software > Core
Network Product Line > Wireless-OSS > iManager
M2000-II > HMACUtil to obtain the tool to encrypt
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 3.12.3 Troubleshooting Problems
Caused by Change of the Subscriber Identity
Anonymization Switch or the Encryption Key.
Engin
eering
Param
eters
(Optio
nal)
The engineering
area are used for the
geographic observation
of the analysis result.
You do not need to
prepare the engineering
parameters if the
geographic display of the
analysis result is not
required.

Issue 03 (2015-07-30)

756
Nastar
Data
Type
Function
Operation
Map
File
(Optio
nal)
The map file for a

analysis result
result on the map.

(Optional).
Mailb
ox
Infor
matio
n
(Optio
nal)
The information includes

mailbox addresses of the
sender and receiver. The
Nastar needs the
information for
automatically sending
analysis reports. If you do
not need to automatically
send analysis reports,
such information is not
needed.
For details, see 3.4.10 Setting a Mailbox and Address

List for Sending Analysis Reports (Optional).

Before analyzing, check that the used NE versions and M2000 versions are consistent with those
described in Table 4-30.
NOTE
For the required NE versions and M2000 versions of the signaling tracing analysis, refer to Table 4-26 in the
Functions of VIP Analysis chapter.
Issue 03 (2015-07-30)

757
Nastar
Table 4-30 Description of the data source environment

Net
wor
k
Description
GSM
l Check that the matching U2000/M2000 version is V200R013C00 (or later),and

the NE version is BSC6900 V900R015C00 (or later) or BSC6910 V100R015C00
(or later).
l GSM RAN PS analysis:
Check that the matching U2000/M2000 version is V200R013C00 (or later),and
(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.
UM
TS

(or later).
Obtaining Data(UMTS) > Turning On the User Identity Information
Reporting Switch (UMTS) in Nastar Commissioning Guide.
Issue 03 (2015-07-30)

758
Nastar
Net
wor
k
Description
LTE
l Check that the matching U2000/M2000 version is V200R013C00 (or later), the
NE version is BTS3900 V100R008C00SPC020 (or later), BTS3900
V100R008C01SPC200 (or later), BTS3900 V100R009C00 (or later),BTS3900
V100R010C00 (or later), BTS3900 V100R010C10 (or later), or BTS3900
V100R011C00 (or later), and the MME on the CN is provided by Huawei and the
version is USN9810 V900R011C02 or later
NOTE
l If the MME on the CN is not provided by Huawei, you need to contact Huawei technical
support for the requirements, as stipulated in the 3GPP specifications, that the MME must
meet in order to interconnect to the eNodeB.
l For details about how to set the vendor type of the EPCs (MMEs) accessed by the Nastar,
see 3.3.7 Setting the Vendor Type of EPCs (MMEs) (Optional).
l Set the CHR reporting value. For details, see Commissioning the Function of
Obtaining Data(LTE) > Setting the MME CHR Data Reporting Values
(LTE) in the Nastar Commissioning Guide(RH2288).
l Check that the CHR transmission switch is enabled. For details, see
Commissioning the Function of Obtaining the Data > Preparing for
Obtaining Data > Preparing for Obtaining Data(LTE) > Enabling the MME
CHR Data Transmission Switch (LTE) in the Nastar Commissioning Guide
(RH2288).
l Check that the IMEI switch is enabled. For details, see Commissioning the
Function of Obtaining the Data > Preparing for Obtaining Data > Preparing
for Obtaining Data(LTE) > Checking and Turning on the IMEI Switch at the
CN (LTE) in the Nastar Commissioning Guide(RH2288).
l Check that the switches for reporting voicestatic events is enabled. For details, see
Obtaining Data > Preparing for Obtaining Data(LTE) > Turning On the
Switches for Reporting VoiceStatic Events on an eNodeB (LTE VIP Analysis/
Complaint Analysis Support) in the Nastar Commissioning Guide(RH2288).
Issue 03 (2015-07-30)

759
Nastar
Net
wor
k
Description
PS
Core
l Check that the CHR data switch has been turned on at the SGSN/MME and GGSN/
SAE-GW. For details, see Setting the Device Number Type in the SGSN/MME
CHR Record, Enabling the CHR Data Transmission Switch (SGSN/MME),
Enabling the CHR Data Switch (GGSN/SAE-GW) under Nastar
Commissioning Guide Commissioning the Function of Obtaining Data >
Preparing for Obtaining Data > Preparing for Obtaining Data (PS Core).
l For the PS Core analysis, check that the used NE versions and U2000/M2000
versions are consistent with the following information:
NE version:
USN9810 V900R011C01SPC300 or later version, USN9810
V900R011C02SPC200 or later version, USN9810 V900R012C00,
USN9810 V900R012C01, USN9810 V900R013C00, USN9810
V900R014C00, USN9810 V900R014C10, USN9810 V900R015C00
UGW9811 V900R009C01, UGW9811 V900R009C02, UGW9811
V900R010C00, UGW9811 V900R010C01, UGW9811 V900R011C00,
V900R013C00
U2000/M2000 version: U2000/M2000 V200R012C00 or later version,OMC
V400R008 or later version
4.9.3 Process of VIP Analysis

This section describes the process of VIP analysis and each procedure in the process.
l
Prerequisites
Procedure
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 4.9.2 Preparations for VIP Analysis.
Procedure
Issue 03 (2015-07-30)

760
Nastar
Issue 03 (2015-07-30)

761
Nastar
Table 4-31 Description of VIP analysis procedures

No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(1)
Check
whether
analysis
data is
integrated

3.6
Checking
the
Integrity
of Analysis
Data
Procedure:
1. Choose Data Type > User Assurance > *** VIP
Analysis 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.
analysis task.
performing (2).
NOTE
(2)
LTE
Periodic
MR Period
Setting
NOTE
l For LTE analysis themes, you must set this parameter
before basic subscription. Otherwise, the Nastar uses the
current value of this parameter to perform basic
subscription.
l For an LTE network, this function is available only to an
account in the Administrators group or users with data
subscription management permission.
Navigation path: Choose Maintenance > LTE

Periodic MR Period Setting
For details
about
parameters,
see LTE
Periodic
MR Period
Setting
Parameter
s
Procedure:
1. In the LTE Periodic MR Period Setting window,
set Periodic MR Period, Number of Sampled
Users and Number of Times MRs Are Reported.
2. Click Configure.
Issue 03 (2015-07-30)

762
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
Subscribe
to analysis
data (basic)

3.5
Subscribin
g to
Analysis
Data
Procedure:
click the *** tab.
configured.
3. On the Basic Subscription Settings tab page, click
Set.
4. In the displayed Basic Subscription Settings dialog
box, set the switch of VIP analysis data to ON.
l In the GSM network, the switch name is VIP
Analysis Data (CHR-CS) and VIP Analysis
Data (CHR-PS) for subscribing to the CHR-CS
and CHR-PS data of the GSM network.
l In the UMTS, LTE FDD, and LTE TDD network,
the switch name is VIP Analysis Data (CHR).
l In the PS Core network, the switch name is VIP
Analysis Data (SGSN/MME-CHR).
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 4.9.2 Preparations for
VIP Analysis.
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 03 (2015-07-30)

763
Nastar
No.
Procedur
e
Description
Subscribe
to analysis
data
(applicatio
n)

Reference
for
Detailed
Operatio
ns
Procedure:
click the *** tab.
configured.
3. On the VIP analysis tab page, choose Group
Level, and click ON.
4. Select VIP groups and NEs.
l For a GSM network, you need to select VIP
groups, and select NEs for CS service analysis and
PS service analysis separately.
l For a UMTS network, you need to select VIP
analysis features, including all-signaling analysis,
user plane analysis, and control plane analysis,
and select VIP groups and NEs.
VIP Analysis (SIGNALING): is selected to
conduct all-signaling analysis of only
important VIP subscribers.
VIP Analysis (SUMMARY): is selected to
conduct signaling-plane data analysis of all
VIP subscribers.
l For an LTE network, you need select VIP groups
and NEs.
l If you want to perform all-signaling analysis on a
subscriber, check that the subscriber is an
important VIP subscriber and that the VIP group
to which the subscriber belongs has been selected.
NOTE
l For details about all-signaling analysis on an LTE
network, see 4.9.9 FAQ: How Do I Set the LTE
All-Signaling Switch to On?.
l 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.
5. Click Confirm.
Issue 03 (2015-07-30)

764
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
View information in the Log Info area to ensure that

VIP analysis data has been successfully subscribed
to.
Check
whether
analysis
data is
integrated

Procedure:
Analysis Data.
3.6
Checking
the
Integrity
of Analysis
Data

integrity.
4. Click Query.
the window.
analysis task.
technical support.
Issue 03 (2015-07-30)

765
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(3)
Create an
analysis
task
Navigation path: Choose Theme Function > User

Assurance > VIP Analysis in the navigation tree of the
l For
details,
see 3.7
Creatin
g an
Analysi
s Task.
Procedure:
1. Double-click the VIP Analysis node.
3. On the Analysis Type tab page, set the Analysis
Scenario, Access Network Type and Data type.
4. On the Select NE(s) tab page, select a NE.
5. On the VIP Group tab page, select the VIP groups
to be analyzed.
NOTE
In combined complaint analysis support scenarios, when
you select a VIP group during taks creation, the MSISDN
user group cannot be selected.
6. On the Result Threshold tab page, set the abnormal

threshold of each KPI.
7. On the Process Threshold tab page, set the abnormal
threshold of each KPI. Click Next.
8. Choose the task type, and set the analysis time
segment. The Nastar will obtain the relevant analysis
data in the time period. Click Next.
NOTE
To obtain accurate subscriber information, you are advised
to set Execute on to 1 hour.
9. Optional: On the Sending Analysis Reports

Setting tab page, set the values of multiple
parameters for automatically sending an analysis
report through email.
10.Click Finish.
Issue 03 (2015-07-30)

l For
details
about
the
paramet
ers, see
Analysi
s Task
Param
eters.
l For
details
about
Sendin
g
Analysi
s
Report
s
Setting,
see
3.4.10
Setting
a
Mailbo
x and
Addres
s List
for
Sendin
g
Analysi
s
Report
s
(Optio
nal)
766
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(4)
View
analysis
results VIP
summary
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.
l For
details,
see 3.8
Queryi
ng
Analysi
s
Results
.
Procedure:
2. In the displayed VIP Analysis window, click the
User Level Results tab to view the VIP summary
analysis results.
View
analysis
results VIP deep
analysis
Navigation path:
icon in the Deep Analysis
parameter of the VIP summary analysis results.
Procedure:
icon in the Deep Analysis parameter of the
1. Click
VIP summary analysis results.
NOTE
icon to enter
If the analysis object is VIP group, click
the analysis result window that the analysis object is VIP
subscriber. If you want to enter the deep analysis window,
you need click
icon again.
2. In the displayed Deep Analysis Result_*** window,

view the in-depth analysis results.
NOTE
View
analysis
results VIP active
cells
analysis
l For
details
on the
descript
ion of
the
window
for
showin
g
analysis
results,
see
4.9.4
Refere
nce for
VIP
Analysi
s
Interfa
ce.

Procedure:
Network Level Results: Active Cell tab to view the
analysis results of cells where VIP subscribers are
active.
Issue 03 (2015-07-30)

767
Nastar
No.
Procedur
e
Description
View
analysis
results VIP active
servers
analysis
(only
support the
GSM
network)

View
analysis
results VIP trend
analysis

Task Management window, select a periodic task in the
Reference
for
Detailed
Operatio
ns
Procedure:
Network Level Results: Active Server tab to view
the analysis results of servers where VIP subscribers
are active.
Procedure:
1. Right-click the analysis result of the task, and choose
Trend Analysis from the shortcut menu.
2. In the displayed *** VIP Trend Analysis window,
view the trend analysis results.
Issue 03 (2015-07-30)

768
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(5)
Export
analysis
reports

l For
details,
see 3.10
Exporti
ng
Analysi
s
Report
s.
Procedure:
2. Specify the export path and export content.
3. Click Save.
l For
details
on the
descript
ion of
the
window
for
showin
g
analysis
results,
see
Interfa
ce
Descrip
tion:
VIP
Analysi
s/InDepth
Analysi
s/
Geogra
phic
Display
.
Issue 03 (2015-07-30)

769
Nastar
LTE Periodic MR Period Setting Parameters

Parameter
Description
Periodic MR
Period
Specify the measurement report period for periodic events. The value of this
parameter can be 1024(ms), 2048(ms), 5120(ms), 10240(ms), 1(min), or
6(min). The default value is 10240(ms).
Number of
Sampled Users
Specify the number of sampled subscribers in periodic MRs. A larger

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.
NOTE
For eRAN7.0 SPC135 and later versions, add more sampled users in the MR collection
based on user distribution on the live network so that more users can be sampled in
the LTE complaint analysis support.
Number of
Times MRs
Are Reported
Specify the number of MRs times in periodic.

l The value of this parameter can be 16, Unbounded.
l The default value is 16.

Basic Subscription
Issue 03 (2015-07-30)

770
Nastar
Netwo
rk
Parameter
Description
GSM
VIP
Analysis
Data (CHRCS)
Switch for enabling or disabling the reporting of CS CHR data. You

can retain the default state of the switch.
You can click
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 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 03 (2015-07-30)

771
Nastar
Netwo
rk
Parameter
Description
VIP
Analysis
Data (CHRPS)
Switch for enabling or disabling the reporting of PS CHR data. You

You can click
l Internal Message: 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.
documentation.
l Overlong DL PDU Sending Delay Threshold for Delay-Related
Services: For details, see the SET GPSCHRCTRL command
l Overlong UL PDU Receiving Delay Threshold for DelayRelated Services: For details, see the SET GPSCHRCTRL
l Abnormal UL/DL PDU Interval Threshold for Delay-Related
l UL PDU Response Waiting Threshold for Delay-Related
l Overlong DL PDU Sending Delay Threshold for Rate-Related
l Overlong UL PDU Receiving Delay Threshold: For details, see
the SET GPSCHRCTRL command in the related NE product
documentation.
Issue 03 (2015-07-30)

772
Nastar
Netwo
rk
Parameter
Description
UMTS
VIP
Analysis
Data (CHR)
Switch for enabling or disabling the reporting of CHR data. You

You can click
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
contained in reported CHR data. For details, see the SET
VIP
Analysis
Data (MR)
Issue 03 (2015-07-30)
Switch for enabling or disabling the reporting of MR data. You can

You can click
to set advanced parameters (mainly the
parameters for MR collection). For details, see the LST
UMMMRCTRL command in the related NE product
documentation. You can select all or none of the options for a
parameter or retain the existing settings.

773
Nastar
Netwo
rk
Parameter
Description
LTE
FDD/
LTE
TDD
VIP
Analysis
Data (CHR)
Switch for enabling or disabling the reporting of eNodeB CHR data.

You can retain the default state of the switch.
You can click
l Common tab page: Set Trace Event Block Type. The selected
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 intrafrequency 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
UL NI SUBFRAME MR, subframe uplink NI 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
L2 MSG3 INFO, L2 MSG3 info
PERIOD PRIVATE THROUGHPUT MEASUREMENT
MDT, periodic throughput MDT measurement
Issue 03 (2015-07-30)

774
Nastar
Netwo
rk
Parameter
Description
PERIOD_UE_MultiRRU_UL_RSRP_MR, uplink RSRP
events in multiple RRU cells
If PERIOD LOGGED MDT MEASUREMENT is contained
in Trace Event Block Type, click Select Idle State
Measurement Object at the lower left corner to select the idle
object to be measured. The range of selected objects is displayed
in the Idle State Measurement Object Range column on the
Periodic Event Block Parameter Settings tab page.
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.
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 intrafrequency 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).
Idle State Measurement Object Range: Specify the range
of idle objects to be measured. A maximum of 32 cells or
eight TACs can be selected.
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.
Issue 03 (2015-07-30)

775
Nastar
Netwo
rk
Parameter
Description
PS Core
VIP
Analysis
Data
(SGSN/
MMECHR)
Switch for enabling or disabling the reporting of SGSN/MME CHR

data. You can retain the default state of the switch.
You can click
l Error Type: specifies the types of reported information. If you

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
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.
Netwo
rk
Level
Parameter
Description
GSM
Group
Level
VIP Group
VIP groups, CS NEs, and PS NEs to be analyzed.
GSM CS NE
List
GSM PS NE
List
UTMS
Group
Level
Open VIP
Speciality
VIP functions to be analyzed.
VIP Group
VIP groups and NEs to be analyzed.
NE List
LTE
FDD/
LTE
TDD
Issue 03 (2015-07-30)
Group
Level
VIP Group
User Level
eNodeB
Interface
Select
NE List
eNodeB interfaces to be analyzed.

776
Nastar
Netwo
rk
PS
Core
Level
Group
Level
Parameter
Description
IMSI
International mobile subscriber identify (IMSI)

information of VIP subscribers.
Select
Whether a specified VIP subscriber is selected.
Trace
Reference No.
Reference number for tracing a specified VIP

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.
VIP Group
NE List

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
l Task Name must be named in Chinese or English. Otherwise, the
function of distributing analysis results by emails is unavailable.
Task Type
Remarks

Issue 03 (2015-07-30)

777
Nastar
Parameter
Analysis Type
Description
Analysis
Scene
Set the analysis type:

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
Network
Type
Set the RAT for an NE. The system supports the following
RATs: 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 CS Data Access: Analyzes the PS service based
on the PS-related data on the RAN side.
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.
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.
Issue 03 (2015-07-30)
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
Date
Indicates the last time the VIP group information is

updated.

778
Nastar
Parameter
Result
Threshold
Description
Network
Indicates the RAT of a VIP group.
Domain
Indicates the domain of an NE.

Domains include signaling plane-CS,
signaling plane-PS, signaling planeintegration.
Service Type
l When only analyzing the RAN data,

the parameter is displayed as Service
Type that indicates the service type
of the KPIs, such as NET, Call, and
so on.
or Flow Type
or Service/
Flow Type
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
Name
Indicates the name of a KPI indicator.

The indicators are displayed on the
analysis result window.
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. The abnormal
KPIs will be colored yellow in the
analysis results.
Click the unit and enter the KPI
abnormal threshold. This parameter can
be empty. That is, no threshold value is
provided.
Process
Threshold
Issue 03 (2015-07-30)
Network

NOTE
Use the result
counter of
Short Calls
(Calling
Party) in VIP
analysis results
as an example
to describe the
differences
between the
result
threshold and
the process
threshold.
Result
threshold:
Engineers can
set the result
threshold of
the Short
Calls (Calling
Party) counter
and detect VIP
subscribers
that have more
short calls.
Process
threshold:
Engineers need
to set the
process
threshold for
defining a
short call based
on the
preceding
analysis result
counter. For
example, If the
Service
Duration
(Calling
Party) of one
call is shorter
than the Short
Call
Threshold
(Calling
Party), the call
is called a short
call (calling
party).
779
Nastar
Parameter
Description
Domain

Service Type

so on.
or Flow Type
or Service/
Flow Type

on.
type of the KPIs.
Indicator
Name
Indicates the name of a KPI process

threshold. The threshold is based on the
process of obtaining the final values of
KPI indicators.
Criterion

Threshold

KPI.
or deteriorating KPI.
provided.
Issue 03 (2015-07-30)

780
Nastar
Parameter
Description
Duration
Delay
immediately.
Execute on

Param
eter
Description
Note
Start
time
Date for starting the task.
Start Time of a periodic task = Next time

point + Delay by (hours)
Period

Value range: 30 Minutes, 1 to
24 Hours, 1 to 7 Days, and 1
Week.
Repeat
times
Number of times that a periodic

task is executed. If you set this
parameter to 0, the task is
executed all the time.
Time period of a periodic task: [Start Time of

a periodic task - Period, Start Time of a
periodic task]
The Next time point is related to Start time and
Period.
l If you set Period to 30 Minutes, the Next
time point is 00 seconds of the next 30
minutes starting from the current server time
(minute-level). For example, if the current
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
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
the (7*N + 1) day starting from Start time.
Issue 03 (2015-07-30)

781
Nastar
Param
eter
Description
Note
Delay
by
(hours)
Time delayed for executing a

task.
NOTE

NOTE
If DST starts before a task is
executed, the execution delay will
be automatically updated to ensure
that the task can be executed at the
specified time. For example, if you
set Start time at 01:00 on a day,
and the value of Delay by
(hours) for the task was set to 3
hours, the task was scheduled to be
executed at 04:00. However, DST
started before 02:00 on that day,
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
day
l If the start time of a periodic task is later than

the current server time, the Nastar automatically
executes the task at the start time.
Example: If the current server time is 01/01/2013
14:00:00, Start time is 01/02/2013, Period is 1
Day, and Delay by (hours) is 3, the Nastar
automatically executes the task at 01/03/2013
03:00:00.
l If the start time of a periodic task is earlier than
the current server time, the Nastar immediately
executes the task.
Example: The current server time is 01/02/2013
immediately executes the task.
If this parameter is set, it works

the same as All Busy Time
under Busy hours.
parameter.
Busy
hours
If you select this parameter, the

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 03 (2015-07-30)

782
Nastar
Parameter
Description
Sendin
g
Analysi
s
Reports
Setting
Automatically
send analysis
reports via
emails
After you select this option, the system delivers the exported VIP
analysis result file to the mailboxes of the specified users.
Target email
Indicates the recipient's mailbox. Click Select. In the displayed

Email dialog box, choose user mailboxes.
Email subject
Indicates the title of an email.

Users are not allowed to change the value of this parameter.
Email
contents
Indicates the type of the report being sent.

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.
4.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 03 (2015-07-30)

783
Nastar
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.
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.
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 4.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 4-43 shows the VIP analysis results window.
Figure 4-43 VIP analysis interface (example for a GSM network)
Issue 03 (2015-07-30)

784
Nastar
No.
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_GSM PS.csv
indicates the counter overview information table of the user-level
analysis, according the analysis object is group, and the service
type is GSM PS.
: Displays the VIP analysis results geographically.

For details, see Geographic Display Interface.
Issue 03 (2015-07-30)
: Starts VIP trend analysis. Only periodical tasks support trend

analysis. For details, see Interface Description: VIP Trend
Analysis.

785
Nastar
No.
Analysis
result tab
page
Displays analysis results on different tab pages as follows:

l On the User Level Results tab page, you can analyze counter value
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 4-44.
Figure 4-44 VIP analysis interface - user-level analysis (example for a GSM network)
Issue 03 (2015-07-30)

786
Nastar
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 rightclicking.
(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 UserDefined 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
Issue 03 (2015-07-30)

787
Nastar
No.
Parameter
Description
(4)
Counter
overview
information
table
Lists all counter values in different applications for the selected NE

object based on the selected counter set.
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
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 4.10.4
Reference for Complaint Analysis Support Interface.
NOTE
l 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.
l For combined CHRs, combination calculation is not performed because the
information in the summary table before in-depth analysis is obtained from
theme analysis before the in-depth analysis. However, combination
calculation is performed when the CHRs are exported. As a result, the type
of CHR displayed in the summary table before the in-depth analysis may be
inconsistent with that in the exported summary report after the in-depth
analysis.
(5)
Active cell
information
table
(6)
Active server Displays active servers of a selected VIP user object. It is only
information supported by the GSM network.
table
(7)
Active MME Displays active MME of a selected VIP user object. It is only supported
information by the LTE network.
table
Issue 03 (2015-07-30)
Displays active cells of a selected VIP user object.

788
Nastar
No.
Parameter
Description
(8)
Active TAC
information
table
Displays active TAC of a selected VIP user object. It is only supported

by the LTE network.
Network-Level Analysis Tab Page-Active Cell

The VIP analysis results are displayed in tables. Figure 4-45 shows the interface.
Figure 4-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.
Issue 03 (2015-07-30)

789
Nastar
No.
Parameter
Description
(2)

selection area
NOTE
The RAN-CS and RAN-PS types cannot be chosen at the same time.
(3)

selection area
The Nastar defines a default counter set by analysis scenario.
(4)
Counter
overview
information
table

(5)
Active VIP
subscriber
information
table
Displays VIP subscribers for selected NE objects.
Network-Level Analysis Tab Page-Active Server of GSM Network

The network-level VIP analysis results are displayed in tables. Figure 4-46 shows the interface.
Figure 4-46 VIP analysis interface - active servers
Issue 03 (2015-07-30)

790
Nastar
No.
Parameter
Description
(1)
Analysis object
selection area
Set the counter summary results to being displayed by server

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)
(3)
Service type
selection area
Select a service type to be viewed.
Counter set
selection area
Contains a counter set to be analyzed.
NOTE
Only the RAN-PS service is supported.
(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 4-47.
Issue 03 (2015-07-30)

791
Nastar
Figure 4-47 Geographic display interface (example for an LTE network)
No.
Feature
Description
(1)
Button area
Navigation path for basic operations in the Geographic Observation

window. For details about the icons, see 3.2.3 Interface
(2)
Navigation
tree in the
Geographic
Observation
window
NOTE
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 03 (2015-07-30)

792
Nastar
No.
Feature
Description
(3)
Geographic
observation
area
Analysis results are displayed as icons in different colors.
(4)
Grid detail
area
This area is empty for VIP analysis.
(5)
Legend area

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
area
l In the geographic observation area, select an icon of a cell and

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.
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 4-48 shows the VIP trend analysis
results.
Issue 03 (2015-07-30)

793
Nastar
No.
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 03 (2015-07-30)

794
Nastar
No.
Area for
setting
filtering
criteria
Selects a VIP user whose trend analysis is to be analyzed.

NOTE
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 (IntraRAT) > 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.
Issue 03 (2015-07-30)
Service
type
selection
area
Select the service type whose trend analysis is to be viewed. Only one
service type can be selected each time.

795
Nastar
No.
Counter
type
selection
area
Select the counter type whose trend analysis is to be viewed. One or more
counter types can be selected.
Trend
analysis
chart
Displays the trend analysis charts of multiple counters for a selected

subscriber during a time segment.
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/InDepth Analysis/Geographic Display.
l For a data point showing an abnormal counter (such as a failurerelated 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 4.10.4 Reference for Complaint
Analysis Support Interface.
6
Trend
analysis
table
Displays detailed counter information during each period for the selected
users. The counter information in this table is displayed synchronously
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 03 (2015-07-30)

796
Nastar
No.
Area for
setting
trend
analysis
mode
The trend analysis modes are as follows:

l Auto Refresh Mode: In this mode, The trend data is displayed based
on a periodical VIP analysis task. The trend chart refreshes itself
automatically upon a VIP analysis task for one period is completed.
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.
4.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.
Issue 03 (2015-07-30)

797
Nastar
Common
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Deep
Analysis
N/A
N/A
When the dimension is Group, this parameter is

used to switch from the analysis results of a VIP
group to the analysis results of the VIP
subscribers in this group.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
When the dimension is User, this parameter is

used to switch from the analysis results of
counters to the analysis results of calls.
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

798
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Group
Name
N/A
N/A
Name of a VIP group.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

799
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
User ID
N/A
N/A
ID of a VIP subscriber. Query the ID of a VIP

subscriber using VIP group management.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

800
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Alias
N/A
N/A
Name of a VIP alias. Query the alias of a VIP

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

801
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
IMSI information of a subscriber.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
Note: Only when you have the "User Identity"

right, you can view the IMSI information.
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

802
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
IMEITAC
0000
0000
9999
9999
N/A
International mobile equipment identity-type

allocation code (IMEI-TAC) of the terminal
used by a VIP subscriber.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

803
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Terminal
Model
N/A
N/A
Model of the terminal used by a VIP subscriber.

Obtain the terminal type in the Terminal Type
Management window based on the IMEI-TAC
of the terminal used by the VIP subscriber.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

804
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Service
Type
N/A
N/A
Service type for a following counter.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

805
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Number
of
Abnormal
KPIs
[0,
+)
Numb
er
Number of abnormal counters in all counter sets

determined based on the result thresholds set
when engineers create a task.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

806
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Total
Reports
[0,
+)
Numb
er
Indicates the number of records generated for all

service types during the network access of a
subscriber.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
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.
Issue 03 (2015-07-30)

807
Nastar
RAN-CS/NET/Accessibility Evaluation
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Acces
s
Reque
sts
(IntraRAT)
[0,
+)
Number
Number of access requests that a VIP

subscriber initiates to access the network
from a cell in the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acces
s
Failur
es
(IntraRAT)
[0,
+)
Number
Number of access failures that a VIP

subscriber experiences during the process
of accessing the network from a cell in the
current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

808
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Acces
s
Reque
sts
(InterRAT)
[0,
+)
Number

from a cell in another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acces
s
Failur
es
(InterRAT)
[0,
+)
Number

of accessing the network from a cell in
another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

809
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Avera
ge TA
on
Acces
s
[0,63
]
N/A
Average TA value when a VIP subscriber

initiates channel setup requests for
accessing the network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnor
mal
TAs
on
Acces
s
[0,
+)
Number
Number of times that the TA value is

abnormal when a VIP subscriber initiates
channel setup requests for accessing the
network.
Set the exception threshold when you
create a task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

810
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Ratio
of
Abnor
mal
TAs
on
Acces
s
[0.00,
100.0
0]
Proportion of abnormal TA values when

a VIP subscriber initiates channel setup
requests for accessing the network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Proportion of abnormal TA values =

Number of abnormal TA values/Number
of all TA values x 100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Avera
ge
RAC
H
Level
on
Acces
s
[-110
,-47]
dBm
Average RACH level when a VIP

subscriber initiates channel setup
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

811
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Abnor
mal
RAC
H
Levels
on
Acces
s
[0,
+)
Number
Number of times that the RACH level is

network.
l SRAN8.0/
GBSS15.0/
RAN 15.0

create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio
of
Abnor
mal
RAC
H
Levels
on
Acces
s
[0.00,
100.0
0]
Proportion of abnormal RACH levels

when a VIP subscriber initiates channel
setup requests for accessing the network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Proportion of abnormal RACH levels =

Number of abnormal RACH levels/
Number of all RACH levels x 100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

812
Nastar
RAN-CS/NET/Retainability Evaluation
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Relea
ses
(Intra
RAT)
[0,
+)
Numb
er
Number of times that a VIP subscriber releases

all services in the current system.
l SRAN8.0
/
GBSS15.
0/RAN
15.0
Number of releases (intra-RAT) = Access

requests (intra-RAT) - Access failures (intraRAT)
l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

813
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Abno
rmal
Relea
ses
(Intra
RAT)
[0,
+)
Numb
er
Number of times that a VIP subscriber

abnormally releases all services in the current
system. The Nastar supports only the Call service.
l SRAN8.0
/
GBSS15.
0/RAN
15.0
l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

814
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Relea
ses
(Inter
RAT)
[0,
+)
Numb
er

all services in another system.
l SRAN8.0
/
GBSS15.
0/RAN
15.0
Number of releases (inter-RAT) = Access

requests (inter-RAT) - Access failures (interRAT)
l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

815
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Abno
rmal
Relea
ses
(Inter
RAT)
[0,
+)
Numb
er

abnormally releases all services successfully
accessed from another system.
l SRAN8.0
/
GBSS15.
0/RAN
15.0
This parameter is also referred to as the number

of times that the service is successfully handed
over from another system and proceeds but the
call is abnormally released.
l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

816
Nastar
RAN-CS/NET/Mobility Evaluation
Paramet
er
Range
Unit
Description
Supported
Solution Version
Hard
Handover
Requests
[0,+)
Num
ber
Number of hard handover requests that

a VIP subscriber initiates.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Hard
Handover
Failures
[0,+)
Num
ber
Number of hard handover failures that

a VIP subscriber experiences.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

817
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
Hard
Handover
Success
Times
[0,+)
Num
ber

successfully initiates a hard handover.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
Outgoing
Handover
Requests
[0,+)
Num
ber
Number of times that an outgoing

inter-RAT handover from a GSM
network is triggered during a service.
The BSC records the value of the
parameter after it successfully sends
the command.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

818
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
InterRAT
Outgoing
Handover
Failures
(Normal
Release)
[0,+)
Num
ber

network is triggered during a service
but the handover fails and the VIP
subscriber then is handed back over to
the GSM network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
Outgoing
Handover
Failures
(Abnorm
al
Release)
[0,+)
Num
ber
Number of times that call drops occur

during an outgoing inter-RAT
handover from a GSM network during
a service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

819
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
InterRAT
Incoming
Handover
Requests
[0,+)
Num
ber
Number of times that a handover from

a non-GSM cell to a GSM cell is
triggered during a service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
Incoming
Handover
Failures
[0,+)
Num
ber

a non-GSM cell to a GSM cell fails
during a service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

820
Nastar
RAN-CS/Call/Accessibility Evaluation
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Total
Call
Setup
Reques
ts
[0,
+)
Numb
er
Number of call setup requests that a VIP

and initiate a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
That is, the number of Channel Request

messages from a VIP subscriber after the
BSC obtains the IMSI correctly.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Failure
s
[0,
+)
Numb
er
Number of call setup failures that a VIP

of accessing the network and initiating a
call.
The call setup process spans from the
Channel Request message to the Altering
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

821
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Abnor
mal
Release
Before
Call
Compl
etion
[0,
+)
Numb
er
Number of times that the call is abnormally

released before being set up when a VIP
subscriber accesses the network and
initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The process before call setup spans from

the Channel Request message to the
Connect Acknowledge message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Succes
s Times
[0,
+)
Numb
er
Number of successful call setups when a

VIP subscriber accesses the network and
initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Channel Request message to the Alerting
message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

822
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Call
Compl
etion
(Alerti
ng)
[0,
+)
Numb
er
Number of successful call completions

(Alerting) when a VIP subscriber accesses
the network and initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The call completion (Alerting) process

spans from the Channel Request message
to the Altering message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Compl
etion
(Conne
ct Ack)
[0,
+)
Numb
er

(Connect Ack) after a subscriber accesses
l SRAN8.0/
GBSS15.0/
RAN 15.0
The call completion process (Connect Ack)

to the Connect Acknowledge message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

823
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Call
Compl
etion
Succes
s Rate
(Alerti
ng)
[0.00
,
100.
00]
Call completion rate (Alerting) when a VIP

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Call completion rate (Alerting) = Number

of successful call completions (Alerting)/
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Compl
etion
Succes
s Rate
(Conne
ct Ack)
[0.00
,
100.
00]
Call completion rate (Connect Ack) when

a VIP subscriber accesses the network and
initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Call completion rate (Connect Ack) =

Number of successful call completions/
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

824
Nastar
RAN-CS/Call/Retainability Evaluation
Parame
ter
Rang
e
Unit
Description
Supported
Solution Version
Call
Setup
Success
Times
[0,
+)
Num
ber

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Channel Request message to the
Alerting message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Complet
ion
(Connec
t Ack)
[0,
+)
Num
ber
Same as the related counter in RAN/CS/

Call/Accessibility Evaluation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

825
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution Version
Abnorm
al Call
Releases
[0,
+)
Num
ber
Number of times that the call is

abnormally released when a VIP
initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

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.
5. The BSC releases the channel
resources abnormally.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
6. The MSC releases the channel

Abnorm
al Call
Rate
[0.00,
100.00
]
Abnormal call release rate when a VIP

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Abnormal call release rate = Number of

abnormal call releases/Number of
successful call completions (Connect
Ack) x 100%
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

826
Nastar
RAN-CS/Call/Service Evaluation for Delay

Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Access
Delays
(MOC)
[0,
+)
Numbe
r
Number of times that the access delay

is overlong upon successful call
initiation (mobile-originated call).
l SRAN8.0/
GBSS15.0/RAN
15.0
Access delay = Time when the

Assignment Complete message is
generated - Time when the Channel
Request message is generated
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Access
Delay
(MOC)
[0,
+)
Second
Average access delay upon successful

call initiation (mobile-originated call).
Average access delay = Sum of access
delays/Number of access delays
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

827
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Access
Delays
(MOC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Access
Delays
(MOC)
[0.00
,
100.0
0]
Proportion of overlong access delays

upon successful call initiation (mobileoriginated call).
l SRAN8.0/
GBSS15.0/RAN
15.0
Proportion of overlong access delays =

Number of overlong access delays/
Number of access delays x 100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

828
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Access
Delays
(MTC)
[0,
+)
Numbe
r

initiation (mobile-terminated call).
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Access
Delay
(MTC)
[0,
+)
Second

call initiation (mobile-terminated call).
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

829
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Access
Delays
(MTC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Access
Delays
(MTC)
[0.00
,
100.0
0]

upon successful call initiation (mobileterminated call).
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

830
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Times of
Call
Complet
ion
Delay
(Alertin
g)
(MOC)
[0,
+)
Numbe
r
Number of times that the completion

(Alerting) delay is overlong upon
successful call initiation (mobileoriginated call).
l SRAN8.0/
GBSS15.0/RAN
15.0

spans from the Channel Request
message to the Altering message.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Call
Complet
ion
Delay
(Alertin
g)
(MOC)
[0,
+)
Second
Average call completion (Alerting)

delay upon successful call initiation
(mobile-originated call).
l SRAN8.0/
GBSS15.0/RAN
15.0
Average call completion delay = Sum

of call completion delays/Number of
call completion delays
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

831
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MOC)
[0,
+)
Numbe
r
Number of times that the call

completion (Alerting) delay is overlong
l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MOC)
[0.00
,
100.0
0]
Proportion of overlong call completion

(Alerting) delays upon successful call
l SRAN8.0/
GBSS15.0/RAN
15.0

delays = Number of overlong call
completion (Alerting) delays/Number
of call completion delays x 100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

832
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Average
Call
Complet
ion
Delay
(Connec
t Ack)
(MOC)
[0,
+)
Second
Average call completion (Connect

Ack) delay upon successful call
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MOC)
[0,
+)
Numbe
r

completion (Connect Ack) delay is
overlong upon successful call initiation
create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

833
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Ratio of
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MOC)
[0.00
,
100.0
0]

(Connect Ack) delays upon successful
l SRAN8.0/
GBSS15.0/RAN
15.0

completion delays/Number of call
completion delays x 100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Times of
Call
Complet
ion
Delay
(Alertin
g)
(MTC)
[0,
+)
Numbe
r

message to the Alerting message.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

834
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Average
Call
Complet
ion
Delay
(Alertin
g)
(MTC)
[0,
+)
Second

(mobile-terminated call).
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MTC)
[0,
+)
Numbe
r

create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

835
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Ratio of
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MTC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Call
Complet
ion
Delay
(Connec
t Ack)
(MTC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

836
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MTC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MTC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

837
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Average
Call
Duration
(MOC)
[0,
+)
Second
Average duration of successful calls for

the mobile-originated party.
l SRAN8.0/
GBSS15.0/RAN
15.0
This parameter indicates the average

call duration.
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.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Short
Calls
(MOC)
[0,
+)
Numbe
r
Number of short calls for the mobileoriginated party during a successful

call.
l SRAN8.0/
GBSS15.0/RAN
15.0
This parameter indicates the VIP

subscriber's call-terminating actions
caused by exceptions, such as one-way
audio, crosstalk, and disturbance call,
based on a predefined short call
threshold.
l SRAN8.1/
GBSS15.1/RAN
15.1
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).
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

838
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Ratio of
Short
Calls
(MOC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

call duration.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Call
Duration
(MTC)
[0,
+)
Second

the mobile-terminated party.
call duration.
incomplete.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

839
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Short
Calls
(MTC)
[0,
+)
Numbe
r
Number of short calls for the mobileterminated party during a successful

call.
l SRAN8.0/
GBSS15.0/RAN
15.0

threshold.
l SRAN8.1/
GBSS15.1/RAN
15.1

task is created).
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Short
Calls
(MTC)
[0.00
,
100.0
0]
Proportion of short calls for the mobileterminated party during a successful

call.
l SRAN8.0/
GBSS15.0/RAN
15.0
Proportion of short calls = Number of

short calls/Number of calls with valid
call durations x 100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

840
Nastar
RAN-CS/Call/Service Evaluation for Call

Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Call
Setup
Success
Times
[0,
+)
Num
ber
Number of successful call setups when

a VIP subscriber accesses the network
and initiates a call.
l SRAN8.0/
GBSS15.0/RAN
15.0

Alerting message.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Complet
ion
(Connec
t Ack)
[0,
+)
Num
ber
Same as the related counter in RAN/

CS/Call/Accessibility Evaluation.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

841
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Downlin
k Oneway
Audio
Times
[0,
+)
Num
ber
Number of times that one-way audio

occurs in the downlink during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
The one-way audio test can only detect

the one-way audio exceptions related
to the channels within the BSS (BTS<>TC) instead of those related to the
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.
Downlin
k Oneway
Audio
Ratio
[0.00
,
100.
00]
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of successful call setups

where one-way audio occurs in the
downlink in all successful call setups.
l SRAN8.0/
GBSS15.0/RAN
15.0

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%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

842
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Uplink
Oneway
Audio
Times
[0,
+)
Num
ber

occurs in the uplink during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0

in the uplink: The DSP in the TC of the
BSC performs periodic statistics on
the bad frame rate based on uplink
rate reaches the predefined threshold,
the BSS determines that primary oneway 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
Oneway
Audio
Ratio
[0.00
,
100.
00]
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

uplink in all successful call setups.
l SRAN8.0/
GBSS15.0/RAN
15.0

uplink in all successful call setups =
occurs in the uplink/Number of
100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

843
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Downlin
k/Uplink
NoAudio
Times
[0,
+)
Num
ber
Number of times that no audio occurs

in both the uplink and downlink during
calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Downlin
k/Uplink
No
Audio
Rate
[0.00
,
100.
00]

where one-way audio occurs in both
the uplink and downlink in all
successful call setups.
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%
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

844
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Downlin
k
Crosstal
k Times
[0,
+)
Num
ber
Number of times that crosstalk occurs

in the downlink during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
The crosstalk test can only detect the

crosstalk exceptions related to the
channels within the BSS (BTS<->TC)
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
k
Crosstal
k Ratio
[0.00
,
100.
00]
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

where crosstalk occurs in the
l SRAN8.0/
GBSS15.0/RAN
15.0

= Number of successful call setups
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

845
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Uplink
Crosstal
k Times
[0,
+)
Num
ber

in the uplink during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0

A interfaces.
Principle for detecting uplink
crosstalk: The DSP of the BTS inserts
free bits of uplink speech TRAU
frames. The DSP of the TC decodes
the unique call identifier and checks its
detected within the test period,
crosstalk occurs in the uplink.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink
Crosstal
k Ratio
[0.00
,
100.
00]

where crosstalk occurs in the uplink in
all successful call setups.
l SRAN8.0/
GBSS15.0/RAN
15.0

all successful call setups = Number of
successful call setups where crosstalk
100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

846
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Downlin
k HQI
[0.00
,
100.
00]
Average value of downlink HQIs after

the call setup is successful.
l SRAN8.0/
GBSS15.0/RAN
15.0
HQI indicates the voice quality of a

call and is measured on a 0-to-7 scale.
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
levels 0 to 7 x 100%
version:
Poor
Downlin
k HQI
Times
[0,
+)
Num
ber
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of times that the uplink HQI

is poor after the call setup is
successful.
l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

847
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Uplink
HQI
[0.00
,
100.
00]
Average value of uplink high quality

indicators (HQIs) after the call setup is
successful.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1

l SRAN9.0/
GBSS16.0/
RAN16.0

version:
Poor
Uplink
HQI
Times
[0,
+)
Num
ber
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1

l SRAN11.0/
GBSS18.0/
RAN18.0

successful.
l SRAN8.0/
GBSS15.0/RAN
15.0

a create task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

848
Nastar
Parame
ter
Ran
ge
Unit
Description
Average
Uplink
VQI
[1.00
,
5.00]
N/A
Average value of uplink voice quality l SRAN8.0/

indicators (VQIs) during calls.
GBSS15.0/RAN
15.0
VQI is the Mean Opinion Score
(MOS) and indicates the voice quality
of a call. The value of the voice quality
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
Supported Solution
Version
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Poor
Uplink
VQI
Times
[0,
+)
Num
ber
Number of times that the uplink VQI

is poor during calls.
create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

849
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Downlin
k VQI
[0.00
,
5.00]
N/A
Average value of downlink voice

quality indicators (VQIs) during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
Average value for the downlink VQIs
GBSS16.0/
of successful call setups = Aggregated
RAN16.0
value of downlink VQIs/Number of
l SRAN10.0/
downlink VQI tests
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Poor
Downlin
k VQI
Times
[0,
+)
Num
ber
Number of times that the downlink

VQI is poor during calls.
create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

850
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Downlin
k Level
[0,
+)
Num
ber
Average downlink level during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Uplink
Level
[0,
+)
Num
ber
Average uplink level during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

851
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Downlin
k
Quality
[0,7]
N/A
Average downlink quality during

calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Uplink
Quality
[0,7]
N/A
Average uplink quality during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

852
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Downlin
k Noise
Occurre
nce
Times
[0,
+)
Num
ber
Number of times that noise occurs in

the downlink during calls, which is
detected by the BSC.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Downlin
k Noise
Ratio
[0.00
,
100.
00]

where noise occurs in the downlink in
l SRAN8.0/
GBSS15.0/RAN
15.0

successful call setups where noise
100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

853
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Uplink
Noise
Occurre
nce
Times
[0,
+)
Num
ber

the uplink during calls, which is
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink
Noise
Ratio
[0.00
,
100.
00]

where noise occurs in the uplink in all
l SRAN8.0/
GBSS15.0/RAN
15.0

100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

854
Nastar
RAN-CS/SMS/Accessibility Evaluation
Param
eter
Range
Unit
Description
Supported
Solution Version
Call
Setup
Reques
ts
(MOC)
[0,+)
Num
ber
Number of setup requests that the

mobile-originated party initiates to use
the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Failure
s
(MOC)
[0,+)
Num
ber
Number of call setup failures that the

mobile-originated party experiences
during the process of attempting to use
the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

855
Nastar
Param
eter
Range
Unit
Description
Supported
Solution Version
Call
Setup
Succes
s Rate
(MOC)
[0.00,1
00.00]
Proportion of successful setup requests

that mobile-originated party initiates to
use the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Reques
ts
(MTC)
[0,+)
Num
ber

mobile-terminated party initiates to use
the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

856
Nastar
Param
eter
Range
Unit
Description
Supported
Solution Version
Call
Setup
Failure
s
(MTC)
[0,+)
Num
ber

mobile-terminated party experiences
the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Succes
s Rate
(MTC)
[0.00,1
00.00]
Proportion of successful call setup

requests that the mobile-terminated
party initiates to use the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

857
Nastar
RAN-PS/PS/General Evaluation
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Access
Failures
[0,
+)
Numb
er
See Access Failures in RAN-PS/PS/

Accessibility Evaluation.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Reports
of
Access
Failure
Count >
0
[0,
+)
Numb
er
Indicates the number of the

measurement reports that the access
failure count exceeds 0.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

858
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Proporti
on of
Access
Failure
Count >
0
[0,10
0]
Indicates the proportion of the total

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Interrupt
ions
[0,
+)
Numb
er
See Service Interruptions in RANPS/PS/Retainability Evaluation.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

859
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Total
Reports
of
Service
Interrupt
ion
Count >
0
[0,
+)
Numb
er

measurement reports that the service
interruption count exceeds 0.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
Proporti
on of
Service
Interrupt
ion
Count >
0
[0,10
0]

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

860
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Service
Interacti
on
Delays
[0,
+)
Numb
er
See Abnormal Service Interaction

Delays in RAN-PS/PS/Service
Evaluation for Delay.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Reports
of
Abnorm
al
Service
Interacti
on
Latency
Count >
0
[0,
+)
Numb
er

measurement reports that the
abnormal service interaction latency
count exceeds 0.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

861
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Proporti
on of
Abnorm
al
Service
Interacti
on
Latency
Count >
0
[0,10
0]

count exceeds 0.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Downloa
ds at
Low
Rate
[0,
+)
Numb
er
See Downloads at Low Rate in

RAN-PS/PS/Service Evaluation for
Rate.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

862
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Proporti
on at
Low
Downloa
d Rate
[0,10
0]

download rate is low.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uploads
at Low
Rate
[0,
+)
Numb
er
See Uploads at Low Rate in RANPS/PS/Service Evaluation for Rate.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

863
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Proporti
on at
Low
Upload
Rate
[0,10
0]

measurement reports that the upload
rate is low.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAN-PS/PS/Accessibility Evaluation
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Access
Failures
[0,
+)
Numb
er

of using a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of access failures = Number of

Attach Fail messages + Number of PDP
Active Fail messages + Number of
exceptions where no response to service
interaction is made + Number of
Authentication and Ciphering Failures
messages.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

864
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Attach
Requests
[0,
+)
Numb
er
Number of Attach Request messages that

a VIP subscriber sends during the whole
process of using a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Attach
Failures
[0,
+)
Numb
er
Number of Attach Fail messages that a

VIP subscriber receives during the
l SRAN8.0/
GBSS15.0/
RAN 15.0
Attach Fail messages are triggered when

the CN rejects the Attach Request
messages from the VIP subscriber or
when the VIP subscriber fails to receive
the responses from the CN due to network
exceptions.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Number of Attach Fail messages =

Number of Attach Request messages Number of Attach Accept messages
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

865
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
PDP
Active
Requests
[0,
+)
Numb
er
Number of PDP Active Request messages

that a VIP subscriber sends during the
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP
Active
Failures
[0,
+)
Numb
er
Number of PDP Active Fail messages that

a VIP subscriber receives during the
l SRAN8.0/
GBSS15.0/
RAN 15.0
PDP Active Fail messages are triggered

when the CN rejects the PDP Active
Request messages from the VIP
subscriber or when the VIP subscriber
fails to receive the responses from the CN
due to network exceptions.
l SRAN8.1/
GBSS15.1/
RAN 15.1

- Number of PDP Active Accept messages
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

866
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Authenti
cation
and
Cipherin
g
Requests
[0,
+)
Numb
er
Number of authentication and ciphering

requests that a VIP subscriber receives
during the process of using a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Authenti
cation
and
Cipherin
g
Failures
[0,
+)
Numb
er

failures that a VIP subscriber receives
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

867
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
No
Service
Interacti
on
Respons
es
[0,
+)
Numb
er
Number of times that no response to

service interaction is made.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If the number of times that the uplink PDU

carries data but downlink PDU does not
exceeds the exception threshold 1 for the
response to service interaction and,
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. (The exception threshold 1 for the
response to service interaction and the
exception threshold 2 for the response to
service interaction are customized
algorithm parameters).
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
868
Nastar
RAN-PS/PS/Retainability Evaluation
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Service
Interrupt
ions
[0,
+)
Numb
er
Number of service interruptions that a

VIP subscriber experiences during the
l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of service interruptions =

Number of service interruptions due to
cell reselection + Number of service
interruptions due to routing area update +
FLUSH LL + Number of service
interruptions due to TBF
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Interrupt
ions Due
to Cell
Reselect
ion
[0,
+)
Numb
er

process of using a data service due to cell
reselection.
The parameter is also referred to as the
number of cell reselections.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

869
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Cell
Reselect
ion
Interval
[0,
+)
Secon
d
Mean time between cell reselections

during the process for a VIP subscriber to
use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
This parameter is also referred to as the

average interval between cell
reselections.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlon
g Cell
Reselect
ion
Interval
Times
[0,
+)
Numb
er
Number of times that the cell reselection

interval is overlong during the process for
a VIP subscriber to use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If the time interval is above the threshold

for overlong cell reselection, the cell
reselection interval is overlong.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Set the threshold when you create a task.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

870
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Service
Interrupt
ions Due
to
Routing
Area
Update
[0,
+)
Numb
er

process of using a data service due to
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Interrupt
ions Due
to
FLUSHLL
[0,
+)
Numb
er

FLUSH-LL.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

871
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Interrupt
ions Due
to TBF
[0,
+)
Numb
er

TBF.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

872
Nastar
RAN-PS/PS/Service Evaluation for Delay

Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Abnorm
al
Service
Interacti
on
Delays
[0,
+)
Numb
er
Number of times that the service interaction

delay is abnormal during the process for a VIP
subscriber to use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If Number of Service Interaction Timeouts is

not equal to 0, Number of Abnormal Service
Interaction Delays is equal to Number of
Service Interaction Timeouts.
l SRAN8.1/
GBSS15.1/
RAN 15.1

equal to 0, Number of Abnormal Service
Service Interactions with Long Delay.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Interacti
on
Timeout
s
[0,
+)
Numb
er
Number of times that the response to service

interaction times out during the process for a
VIP subscriber to use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of Service Interaction Timeout

Times = Number of Timeout Times on
sending PDUs at Downlink + Number of
Timeout Times on sending PDUs at Uplink +
Number of Interval Timeouts for data
transmission between the uplink and
downlink PDUs.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

873
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Delay on
Service
Interacti
on
[0,
+)
Secon
d
Average duration of the response to service

interaction during the process for a VIP
l SRAN8.0/
GBSS15.0/
RAN 15.0

interaction = (Average duration of data
transmission by using the downlink PDU +
Average duration of data reception by using
the uplink PDU + Average duration of data
downlink PDUs) / number of valid values.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Interacti
ons with
Long
Delay
[0,
+)
Numb
er
Number of times that the average duration of

the response to service interaction is overlong
during the process for a subscriber to use a
data service.
If the average duration of the response to
service interaction is above the upper
threshold for the average duration of the
response to service interaction,
the average duration of the response to service
interaction is overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

874
Nastar
RAN-PS/PS/Service Evaluation for Rate

Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Downlo
ad Rate
[0.00,
+)
kbit/s
Average download rate during the process for

a subscriber to use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Download rate = Number of bytes transmitted

by using the downlink PDU/Duration of data
transmission by using the downlink PDU
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

875
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Downlo
ads at
Low
Rate
[0,
+)
Numb
er
Number of times that the download rate is low

data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
A download rate is low if it is lower than the

threshold for low download rate.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Abnorm
al
Proporti
on at
Low
Downlo
ad Rate
[0,10
0]

measurement reports that the download rate is
low.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

876
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Downlin
k TCP
Out-ofOrders
[0,
+)
Numb
er
Number of times that downlink TCP disorder

occurs during the process for a subscriber to
use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Average
Upload
Rate
[0.00,
+)
kbit/s
Average upload rate during the process for a

Upload rate = Number of bytes transmitted by
using the uplink PDU/Duration of data
transmission by using the uplink PDU
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

877
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Uploads
at Low
Rate
[0,
+)
Numb
er
Number of times that the upload rate is low

data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
An upload rate is low if it is lower than the

threshold for low upload rate.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Set the threshold is when you create a task.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Abnorm
al
Proporti
on at
Low
Upload
Rate
[0,10
0]

measurement reports that the upload rate is
low.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

878
Nastar
RAN-PS/PS/Traffic Model Analysis

Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Downlo
ad Rate
[0.00,
+)
kbit/s
See Average Download Rate in RAN-PS/PS/

Service Evaluation for Rate.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

879
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Upload
Rate
[0.00,
+)
kbit/s
See Average Upload Rate in RAN-PS/PS/

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Total
Traffic
Downlin
k
[0,
+)
MB
Total downlink traffic during the process for

Total downlink traffic = Delay-Sensitive
Information/Total Number of the Bytes
Transmitted by Using the Downlink PDU
+ Rate-Sensitive Information/Statistics on
Downlink Rate-Sensitive Service/Number of
the Bytes Transmitted by Using the Downlink
PDU
Uplink Rate-Sensitive Service/Number of the
Bytes Transmitted by Using the Downlink
PDU
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

880
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Total
Traffic
Uplink
[0,
+)
MB
Total uplink traffic during the process for a

l SRAN8.0/
GBSS15.0/
RAN 15.0
Total uplink traffic = Delay-Sensitive

Transmitted by Using the Uplink PDU
Bytes Transmitted by Using the Uplink PDU
the Bytes Transmitted by Using the Uplink
PDU
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Uplink
Signalin
g Access
Times
[0,
+)
Numb
er
Number of access requests on the RACH

(uplink CCCH) during the process for a
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

881
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Occupie
d
Downlin
k
Channel
s
[0,
+)
Numb
er
Average number of channels occupied by the

downlink during the process for a subscriber
to use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Average
Occupie
d Uplink
Channel
s
[0,
+)
Numb
er

uplink during the process for a subscriber to
use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

882
Nastar
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.
Common
Para
met
er
Range
Unit
Description
Supported
Solution
Version
BSC
Nam
e
1 to 64
charact
ers
N/A
Name of the BSC to which an active cell

belongs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Note: when name information cannot be

obtained because configuration
information has been deleted or cell
information has not been activated,
Undefined is displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell
ID
[0,2047
]
N/A
ID of an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

883
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
Cell
Nam
e
1 to 64
charact
ers
N/A
Name of an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CGI
MCCMNCLACCI
N/A
Cell global identification (CGI) of an

active cell.
MCC
[000,99
9]
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
MNC
[00,99]
l SRAN9.0/
GBSS16.0/
RAN16.0
LAC
[0,6553
5]
l SRAN10.0/
GBSS17.0/
RAN17.0
CI
[0,6553
5]
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

884
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
Gro
up
Nam
e
1 to 128
charact
ers
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User
ID
[0,2047
]
N/A
ID of a VIP subscriber. Query the ID of

a VIP subscriber using VIP group
management.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

885
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
Alia
s
1 to 64
charact
ers
N/A
Name of a VIP alias. Query the alias of a

VIP subscriber using VIP group
management.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMS
I
N/A
N/A

Note: Only when you have the "User
Identity" right, you can view the IMSI
information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

886
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
IME
ITAC
N/A
N/A
International mobile equipment identitytype allocation code (IMEI-TAC) of the

terminal used by a VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ter
mina
l
Mod
el
N/A
N/A
Type of the terminal used by a VIP

subscriber. Obtain the terminal type in
the Terminal Type Management window
based on the IMEI-TAC of the terminal
used by the VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

887
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
Serv
ice
Typ
e
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

888
Nastar
Par
am
eter
R
a
n
g
e
Uni
t
Acc
ess
Req
uest
s
[ Nu
0 mbe
,
r
+
Description
Supported
Solution
Version
Number of access requests that a VIP group or VIP l SRAN8.0/

subscriber initiates during the process of using a call
GBSS15.0/
or SMS service in an active cell.
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acc
ess
Fail
ures
[ Nu
0 mbe
,
r
+
Number of access failures that a VIP group or VIP

subscriber experiences during the process of using a
call or SMS service in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

889
Nastar
Par
am
eter
R
a
n
g
e
Uni
t
Abn
orm
al
TAs
on
Acc
ess
[ Nu
0 mbe
,
r
+
Description
Supported
Solution
Version
Number of abnormal TA values that a VIP group or

VIP subscriber experiences during the process of
attempting to access the network in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abn
orm
al
RA
CH
Lev
els
on
Acc
ess
[ Nu
0 mbe
,
r
+
Number of abnormal RACH levels that a VIP group

or VIP subscriber experiences during the process of
attempting the network in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

890
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Rele
ases
[
0
,
+
N Number of times that a VIP group or VIP subscriber

u releases the Call service in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abn
orm
al
Rele
ases
[
0
,
+

u abnormally releases the Call service in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

891
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Inte
rRA
T
Inco
min
g
Han
dov
er
Req
uest
s
[
0
,
+
N Number of incoming inter-RAT handover requests that

u a VIP group or VIP subscriber initiates in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inte
rRA
T
Inco
min
g
Han
dov
er
Fail
ures
[
0
,
+
N Number of incoming inter-RAT handover failures that l SRAN8.0/

u a VIP group or VIP subscriber experiences in an active
GBSS15.0/
m cell.
RAN 15.0
b
l SRAN8.1/
e
GBSS15.1/
r
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

892
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Tota
l
Call
Setu
p
Req
uest
s
[
0
,
+
N Number of call setup requests that a VIP group or VIP

u subscriber initiates in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setu
p
Fail
ures
[
0
,
+
N Number of call setup failures that a VIP group or VIP

u subscriber experiences in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

893
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Abn
orm
al
Rele
ase
Bef
ore
Call
Co
mpl
etio
n
[
0
,
+
N Number of call releases that a VIP group or VIP

u subscriber experiences before call completion in an
m active cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

894
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Abn
orm
al
Call
Rele
ases
[
0
,
+
N Number of abnormal call releases that a VIP group or

u VIP subscriber experiences in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

895
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Call
Setu
p
Req
uest
s
(M
OC)
[
0
,
+

u subscriber initiates in an active cell as the mobilem originated party.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setu
p
Fail
ures
(M
OC)
[
0
,
+

u subscriber experiences in an active cell as the mobilem originated party.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

896
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Call
Setu
p
Req
uest
s
(MT
C)
[
0
,
+

u subscriber initiates in an active cell as the mobilem terminated party.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setu
p
Fail
ures
(MT
C)
[
0
,
+

u subscriber experiences in an active cell as the mobilem terminated party.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

897
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Atta
ch
Req
uest
s
[
0
,
+
N Number of Attach Request messages that a VIP group or

u VIP subscriber sends in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PD
P
Acti
ve
Req
uest
s
[
0
,
+
N Number of PDP Active Request messages that a VIP

u group or VIP subscriber sends in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

898
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
No
Serv
ice
Inte
racti
on
Res
pon
ses
[
0
,
+
N Number of exceptions where no response to service

u interaction is made when a VIP group or VIP subscriber
m is using a service in an active cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

899
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Inte
rrup
tion
s
Due
to
Cell
Res
elec
tion
[
0
,
+
N Number of service interruptions that a VIP group or VIP

u subscriber experiences due to cell reselection in an active
m cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ove
rlon
g
Cell
Res
elec
tion
Inte
rval
Tim
es
[
0
,
+
N Number of times that the cell reselection interval is

u overlong when a VIP group or VIP subscriber is using a
m service in an active cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

900
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Serv
ice
Inte
rrup
tion
s
Due
to
Rou
ting
Are
a
Upd
ate
[
0
,
+

u subscriber experiences due to routing area update in an
m active cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

901
Nastar
RAN-PS/PS/Service Quality Evaluation for Delay

Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Serv
ice
Inte
racti
on
Tim
eout
s
[
0
,
+
N Number of times that the duration of the response to

u service interaction is overlong when a VIP group or VIP
m subscriber is using a service in an active cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Serv
ice
Inte
racti
ons
with
Lon
g
Del
ay
[
0
,
+
N Number of times that the delay of the response to service

u interaction is overlong when a VIP group or VIP
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

902
Nastar
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
er
Rang
e
Unit
Description
Supported Solution
Version
Server IP
N/A
N/A
IP address of an active server.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Server
Name
N/A
N/A
Name of an active server. Obtain

the name of an active server by
choosing System Function >
Data Service Server
Management in the navigation
tree of the Nastar client based on
the IP address of the server.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

903
Nastar
Paramet
er
Rang
e
Unit
Description
Supported Solution
Version
Server
Port
N/A
N/A
Port number of an active server.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Service
Name
N/A
N/A
Name of an active service.

Obtain the name of an active
service by choosing System
Function > Data Service Server
the Server IP and Server Port
values of the service.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Total
Reports
[0,
+)
Num
ber
Number of reports generated

when a user accesses the server.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

904
Nastar
Paramet
er
Rang
e
Unit
Description
Supported Solution
Version
ServerRelated
Service
Abnorma
lities
[0,
+)
Num
ber
Server-Related Service
Abnormalities = No Service
Interaction Responses + Service
Interaction Timeouts + Service
Interaction with Long Delay +
Downlink TCP Out-of-Orders
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Paramet
er
Rang
e
Unit
Description
Supported Solution
Version
No
Service
Interactio
n
Response
s
[0,
+)
Num
ber
Number of times that no

response to service interaction
is made when a VIP group or
VIP subscriber is using a
service in an active cell.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

905
Nastar

Paramet
er
Rang
e
Unit
Description
Supported Solution
Version
Service
Interactio
n
Timeouts
[0,
+)
Num
ber
Number of times that the response

to service interaction times out
when a VIP group or VIP subscriber
is using a service in an active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Interactio
n with
Long
Delay
[0,
+)
Num
ber
Number of times that the duration of

the response to service interaction is
overlong when a VIP group or VIP
subscriber is using a service in an
active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

906
Nastar

Paramet
er
Range
Unit
Description
Supported Solution
Version
Downlin
k TCP
Out-ofOrders
[0,+)
Num
ber
Number of times that

downlink TCP disorder
occurs when a VIP group or
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
4.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.
Common
Param
eter
Rang
e
Unit
Description
Supported Solution
Version
Deep
Analysi
s
N/A
N/A
When the dimension is Group,

this parameter is used to switch
from the analysis results of a
VIP group to the analysis
results of VIP subscribers in
this group.
l SRAN8.0/GBSS15.0/
RAN 15.0
When the dimension is User,

from the analysis results of
counters to the analysis results
of calls.
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

907
Nastar
Param
eter
Rang
e
Unit
Description
Supported Solution
Version
Group
Name
N/A
N/A
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
User ID
N/A
N/A
ID of a VIP subscriber. Query

the ID of a VIP subscriber
using VIP group management.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Alias
N/A
N/A
Name of a VIP alias. Query the

alias of a VIP subscriber using
VIP group management.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

908
Nastar
Param
eter
Rang
e
Unit
Description
Supported Solution
Version
IMSI
N/A
N/A
IMSI information of a
subscriber.
l SRAN8.0/GBSS15.0/
RAN 15.0
Note: Only when you have the

"User Identity" right, you can
view the IMSI information.
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
IMEITAC
N/A
N/A
Type approval code (TAC) in

international mobile
equipment identity (IMEI) of
the UE used by a VIP
subscriber.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Termin
al
Model
N/A
N/A
Type of the UE used by a VIP

subscriber. Query the UE type
of a VIP subscriber using
terminal type management
based on the IMEI-TAC of the
VIP subscriber.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

909
Nastar
Param
eter
Rang
e
Unit
Description
Supported Solution
Version
Service
Type
N/A
N/A
Service type for a counter.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Numbe
r of
Abnor
mal
KPIs
[0,
+)
Num
ber
Number of abnormal counters

in all counter sets determined
based on the result thresholds
set when engineers create a
task.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Total
Reports
[0,
+)
Num
ber
Indicates the number of

records generated for all
service types during the
network access of a subscriber.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
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.
Issue 03 (2015-07-30)

910
Nastar
RAN-NET/Accessibility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Access
Requests(IntraRAT)
[0,+)
Numbe
r
Number of access requests that a

VIP subscriber initiates from a
cell in the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access Failures
(Intra-RAT)
Issue 03 (2015-07-30)
[0,+)
Numbe
r
Number of access failures that a

VIP subscriber experiences from
a cell in the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of failed access requests

(intra-RAT) = Number of failed
service requests initiated by a
specified UE that has gained
access to a system of the current
RAT
l SRAN8.1/
GBSS15.1/
RAN 15.1
= 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)
l SRAN10.0/
GBSS17.0/
RAN17.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
911
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Access
Requests(InterRAT)
[0,+)
Numbe
r

cell in another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access Failures
(Inter-RAT)
[0,+)
Numbe
r

a cell in another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0

(inter-RAT) = Number of failed
access to a system of another
RAT
l SRAN8.1/
GBSS15.1/
RAN 15.1
= Number of incoming interRAT handover failures that this

UE experiences on the entire
network + Number of times that
incoming inter-RAT handover
fails
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

912
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average TP on
Access
[0,3069
]
N/A
Average TP value when a VIP

network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal TPs
on Access
[0,+)
Numbe
r
Number of times that theTP

value is abnormal upon network
access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Set the exception threshold when

you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Remark: If the active set contains

multiple cells during access,
only the counters for the first cell
in this active set are analyzed.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

913
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Abnormal TPs
on Access
[0.00,10
0.00]
Proportion of abnormal TP
values that a VIP subscriber
experiences upon network
access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
values = Number of abnormal TP
values/Number of TP values x
100%
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RSCP
on Access
[-116,-2
5]
dBm
Average RSCP value when a

VIP subscriber gains access to
the network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

914
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
RSCPs on
Access
[0,+)
Numbe
r
Number of times that the RSCP

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0

you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Abnormal
RSCPs on
Access
[0.00,10
0.00]
Proportion of abnormal RSCP

access.
values = Number of abnormal
RSCP values/Number of RSCP
values x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

915
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Ec/No
on Access
[-31.5,0]
dB
Average Ec/No value when a

the network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal Ec/
Nos on Access
[0,+)
Numbe
r
Number of times that the Ec/No

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0

you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

916
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Abnormal Ec/
Nos on Access
[0.00,10
0.00]
Proportion of abnormal Ec/No

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Ec/No values/Number of Ec/No
values x 100%
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Requests(NonService)
[0,+)
Numbe
r
Number of non-service RRC

connection setup requests
initiated by a VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
RRC is short for radio resource

control.
l SRAN8.1/
GBSS15.1/
RAN 15.1
The non-service RRC

connection setup process spans
from the time when the nonservice RRC connection setup
request is initiated to the time
when the non-service RRC
connection setup is complete.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

917
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Failures(NonService)
[0,+)
Numbe
r

connection setup failures after
network access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Success Rate
(Non-Service)
[0.00,10
0.00]
Success rate of non-service RRC

connection setups after network
access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

918
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Numbe
r
Number of service RRC

connection setup requests after
network access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Failures
(Service)
[0,+)
Numbe
r

network access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

919
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Rate
(Service)
[0.00,10
0.00]
Success rate of service RRC

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Failures
(Service-CS)
[0,+)
Numbe
r
Number of CS RRC connection

setup failures after network
access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

920
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Rate
(Service-CS)
[0.00,10
0.00]
Success rate of CS RRC

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Failures
(Service-PS)
[0,+)
Numbe
r
Number of PS RRC connection

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

921
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Rate
(Service-PS)
[0.00,10
0.00]
Success rate of PS RRC

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

922
Nastar
RAN-NET/E2E Evaluation(CS Domain)

Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Requests
(MOC)
[0,+)
Numbe
r
Number of call setup requests

that a VIP subscriber initiates to
use the CS service as the mobileoriginated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Setup
Failures(MOC)
[0,+)
Numbe
r
Number of call setup failures

that a VIP subscriber
experiences during the process
of using the CS service as the
mobile-originated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

923
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Success Rate
(MOC)
[0.00,10
0.00]
Success rate of call setup

requests that a VIP subscriber
initiates to use the CS service as
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Setup
Requests(MTC)
[0,+)
Numbe
r

use the CS service as the mobileterminated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

924
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Failures(MTC)
[0,+)
Numbe
r

mobile-terminated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Setup
Success Rate
(MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

925
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MOC)
[0,+)
Numbe
r
Number of call connection

acknowledgment (alerting)
successes of a VIP subscriber
who accesses the network and
uses the CS service as the
l SRAN8.0/
GBSS15.0/
RAN 15.0
The alerting process spans from

the RRC connection setup
request to the Alerting message.
l SRAN9.0/
GBSS16.0/
RAN16.0
Note: This parameter is

collected based only on the first
RAB after the RRC connection
setup is complete.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success Rate
(Alerting)
(MOC)
[0.00,10
0.00]
Rate of call connection

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

926
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MTC)
[0,+)
Numbe
r
Number of successful call

connection acknowledgments
(alerting) that a VIP subscriber
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success Rate
(Alerting)
(MTC)
[0.00,10
0.00]
Success rate of call connection

acknowledgments (alerting)
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

927
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MOC)
[0,+)
Numbe
r

(Connect Ack) that a VIP
subscriber experiences during
the process of using the CS
service as the mobile-originated
party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The connection
acknowledgment (Connect
Ack) process spans from the
RRC connection setup request
to the Connect Ack message.
setup is complete.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success Rate
(Connect Ack)
(MOC)
[0.00,10
0.00]

acknowledgments (Connect
Ack) that a VIP subscriber
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

928
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MTC)
[0,+)
Numbe
r

service as the mobile-terminated
party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success Rate
(Connect Ack)
(MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

929
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Success
Times(MOC)
[0,+)
Numbe
r
Number of calls that a VIP

subscriber successfully initiates
to use the CS service as the
l SRAN8.0/
GBSS15.0/
RAN 15.0
The call success process spans

from the RRC connection setup
request to the Disconnect
message.
setup is complete.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Success
Rate(MOC)
[0.00,10
0.00]
Success rate of calls that a VIP

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

930
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Success
Times(MTC)
[0,+)
Numbe
r

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Success
Rate(MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

931
Nastar
RAN-NET/E2E Evaluation(PS Domain)

Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Requests(PS)
[0,+)
Number

access the network and use the
PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Setup
Failures(PS)
[0,+)
Number

of attempting to access the
network and use the PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

932
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Success Rate
(PS)
[0.00,10
0.00]

initiates to access the network
and use the PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Success
Times(PS)
[0,+)
Number

to use the PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0

message.
l SRAN8.1/
GBSS15.1/
RAN 15.1

setup is complete.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

933
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Success
Rate(PS)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

934
Nastar
RAN-NET/PDP Evaluation-PS
Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Activation
Requests
[0,+)
Number
Number of PDP activation

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP Activation
Failures
[0,+)
Number

failures that a VIP subscriber
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

935
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Activation
Success Rate
[0.00,10
0.00]
Success rate of PDP activation

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

936
Nastar
RAN-NET/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Release Times
(Intra-RAT)
[0,+)
Number
Number of times that a VIP

subscriber releases all services in
the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Releases(Intra-RAT) = Access
Requests(Intra-RAT) - Access
Failures(Intra-RAT)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal
Release Times
(Intra-RAT)
[0,+)
Number

subscriber abnormally releases
l SRAN8.0/
GBSS15.0/
RAN 15.0
Abnormal Release Times(IntraRAT) = Number of AMR RAB

abnormal releases
l SRAN8.1/
GBSS15.1/
RAN 15.1
+ Number of VP RAB abnormal

releases
l SRAN9.0/
GBSS16.0/
RAN16.0
+ 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 interRAT incoming handover occurs.
Issue 03 (2015-07-30)

l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
937
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Release Times
(Inter-RAT)
[0,+)
Number

another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Releases(Inter-RAT) = Access
Requests(Inter-RAT) - Access
Failures(Inter-RAT)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal
Release Times
(Inter-RAT)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
Abnormal Release Times(InterRAT) = Number of times that the

first RAB after an incoming
inter-RAT handover is
abnormally released.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

938
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Release
Times
[0,+)
Number

subscriber releases all RRC
connections during the process
of using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RRC
Release Times
[0,+)
Number

all RRC connections during the
process of using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

939
Nastar
RAN-NET/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Times
(Non-Service)
[0,+)
Number
Number of successful nonservice RRC connection setups

upon successful call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of successful RRC

connection setups (non-service)
setup requests (non-service) Number of RRC connection
setup failures (non-service) =
Number of valid RRC
connection setup delays (nonservice)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RRC
Setup Delay
(Non-Service)
N/A
Second
Average delay for non-service

RRC connection setup upon
successful call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
RRC connection setup delay =

Time when the RRC CONN
SETUP CMP message is
generated - Time when the RRC
CONN REQ message is
generated.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

940
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RRC
Setup Delay
Times(NonService)
[0,+)
Number
Number of overlong delays for

non-service RRC connection
setup upon successful call
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Set the overlong delay threshold

when you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RRC
Setup Delay
(Non-Service)
[0.00,1
00.00]
Proportion of delays for nonservice RRC connection setup in

all overlong delays upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

941
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Times
(Service)
[0,+)
Number
Number of successful service

RRC connection setups upon
l SRAN8.0/
GBSS15.0/
RAN 15.0

connection setups = Number of
service RRC connection setup
requests - Number of service
RRC connection setup failures =
Number of valid delays for
service RRC connection setup.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RRC
Setup Delay
(Service)
[0,+)
Second
Average delay for service RRC

connection setup upon
l SRAN8.0/
GBSS15.0/
RAN 15.0

CONN REQ message is
generated.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

942
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RRC
Setup Delay
Times(Service)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RRC
Setup Delay
(Service)
[0.00,1
00.00]
Proportion of overlong delays

for service RRC connection
setup in all overlong delays upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

943
Nastar
RAN-NET/Mobility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Soft Handover
Requests
[0,+)
Number
Number of soft handover

initiates during the process of
using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Soft Handover
Failures
[0,+)
Number
Number of soft handover failures

that a VIP subscriber experiences
during the process of using a
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

944
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Soft Handover
Success Rate
[0.00,1
00.00]
Success rate of soft handovers

(including softer handovers) that
a VIP subscriber initiates during
the process of using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Hard Handover
Requests
[0,+)
Number
Number of hard handover

using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

945
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Hard Handover
Failures
[0,+)
Number

experiences during the process of
using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Hard Handover
Success Rate
[0.00,1
00.00]
Success rate of hard handovers

that a VIP subscriber initiates
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

946
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Soft
Handover Delay
[0,+)
Second
Average soft handover delay

during the process for a VIP
subscriber to use a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Hard
Handover Delay
[0,+)
Second
Average hard handover delay

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

947
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of outgoing handover

requests (from a UMTS network
to another network) initiated by a
UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Outgoing
Handover
Requests
(UMTS to
GSM)
[0,+)
Number

to a GSM network) initiated by a
VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

948
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Requests
(UMTS to LTE)
[0,+)
Number

to an LTE network) initiated by a
VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Number

failures (from a UMTS network
to another network) experienced
by a VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

949
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Failures(UMTS
to GSM)
[0,+)
Number

to a GSM network) experienced
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Outgoing
Handover
Failures(UMTS
to LTE)
[0,+)
Number

failures (from one UMTS
network to another LTE
network) experienced by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

950
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Requests
[0,+)
Number
Number of inter-RAT handover

requests (from another network
to a UMTS network) initiated by
a VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Incoming
Handover
Requests(GSM
to UMTS)
[0,+)
Number

requests (from a GSM network to
a UMTS network) initiated by a
VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

951
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Requests(LTE
to UMTS)
[0,+)
Number

requests (from an LTE network
a VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Incoming
Handover
Failures
[0,+)
Number

failures (from another network to
a UMTS network) experienced
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

952
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Failures(GSM
to UMTS)
[0,+)
Number

failures (from a GSM network to
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Incoming
Handover
Failures(LTE to
UMTS)
[0,+)
Number

failures (from an LTE network to
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

953
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average InterRAT Outgoing

Handover Delay
[0,+)
Second
Average delay for outgoing interRAT handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Outgoing inter-RAT handover

delay = Time when the IU
RELEASE COMMAND
message is generated - Time
when the RELOCATION
REQUIRED message is
generated.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Handover Delay
(UMTS to
GSM)
[0,+)
Second
Average delay for UMTS-toGSM handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

954
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version

Handover Delay
(UMTS to LTE)
[0,+)
Second
Average delay for UMTS-toLTE handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average InterRAT Incoming

Handover Delay
[0,+)
Second
Average delay for incoming

inter-RAT handover recorded by
the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Incoming inter-RAT handover

delay = Time when the UTRAN
MOBILITY INFORMATION
CONFIRM message is generated
- Time when the RELOCATION
REQUIRED message is
generated.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

955
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version

Handover Delay
(GSM to
UMTS)
[0,+)
Second
Average delay for GSM-toUMTS handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Handover Delay
(LTE to UMTS)
[0,+)
Second
Average delay for LTE-toUMTS handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

956
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT Cell
Reselection
Times
[0,+)
Number
Number of cell reselections

recorded by the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

957
Nastar
RAN-CS/AMR/Accessibility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Number of RAB setup requests

l SRAN8.0/
GBSS15.0/
RAN 15.0
RAB is short for radio access

bearer.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number

experienced by a VIP
subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

958
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

an RAB setup request.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,10
0.00]
RAB setup success rate after

network access.
RAB setup success rate (%) =
Number of successful RAB
setups/Number of RAB setup
requests x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

959
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
[0,+)
Number

subscriber hears the alerting
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)
[0,+)
Number

subscriber hears the peer ends'
voice upon successful call
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

960
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
Release Times
Before
Connection
Acknowledge
[0,+)
Number
Number of times that a call is

abnormally released between
the time when a subscriber
hears the alerting and the time
when the subscriber hears the
voice of the peer-end subscriber
during a successful call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

961
Nastar
RAN-CS/AMR/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number
See RAB Setup Success Times

in RAN-CS/VP/Accessibility
Evaluation
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Number
Number of times that the RAB

is abnormally released after a
the network and successfully
initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

962
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,10
0.00]
Abnormal RAB release rate

after a VIP subscriber gains
access to the network and
successfully initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Abnormal RAB release rate (%)

= Number of abnormal RAB
releases/Number of successful
call setups x 100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

963
Nastar
RAN-CS/AMR/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

setups during call initiation, that
is, number of RAB setup delays.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

964
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Setup Delay
[0,+)
Second
Average RAB setup delay

subscriber to initiate a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Average RAB setup delay (s) =

Sum of RAB setup delays/
Number of RAB setup delays.
l SRAN8.1/
GBSS15.1/
RAN 15.1
RAB setup delay = RAB setup

request connection
acknowledge time - RAB setup
request time.
l SRAN9.0/
GBSS16.0/
RAN16.0
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.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

request time: When the UTRAN
receives a Radio Access Bearer
Assignment Request message
from the CN.
Issue 03 (2015-07-30)

965
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,+)
Number
Number of times that the RAB l SRAN8.0/

setup delay is overlong during
GBSS15.0/
the process for a VIP subscriber
RAN 15.0
to initiate a call.
l SRAN8.1/
Set the exception threshold
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,10
0.00]
Proportion of RAB setup delays

in all overlong delays.
(%) = Number of overlong RAB
setup delays/Number of RAB
setup delays x 100% = Number
of overlong RAB setup delays/
setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

966
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,+)
Number

setup delay of the mobileoriginated party upon successful
call initiation is overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,+)
Second
Average call setup delay of the

mobile-originated party upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

967
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,10
0.00]
Proportion of overlong call

setup delays of the mobileoriginated party upon successful
call initiation.
setup delays (mobileoriginated) (%) = Number of
overlong call setup delays
(mobile-originated)/Number of
call setup delays (mobileoriginated) x 100% = Number of
successful RRC connection
setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

968
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,+)
Number

setup delay of the mobileterminated party upon
successful call initiation is
overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,+)
Second

mobile-terminated party upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

969
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,+)
Number

overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,10
0.00]

setup delays of the mobileterminated party upon
setup delays (mobileterminated) (%) = Number of
(mobile-terminated)/Number of
call setup delays (mobileterminated) x 100% = Number
of overlong call setup delays
setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

970
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MOC)
[0,+)
Number
Number of times that the

mobile-originated party hears
the alerting upon successful call
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MOC)
[0,+)
Second
Average alerting delay of the

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

971
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Alerting)
(MOC)
[0,+)
Number

alerting delay of the mobileoriginated party upon successful
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MOC)
[0.00,10
0.00]
Proportion of overlong alerting

delays experienced by the
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

972
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MOC)
[0,+)
Number

Ack) delays experienced by the
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MOC)
[0,+)
Second
Average call connection

Ack) delay of the mobileoriginated party upon successful
call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

973
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Connect Ack)
(MOC)
[0,+)
Number

connection acknowledgment
(Connect Ack) delay of the
overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MOC)
[0.00,10
0.00]

(Connect Ack) delays
experienced by the mobileoriginated party upon successful
call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

974
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MTC)
[0,+)
Number

mobile-terminated party hears
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MTC)
[0,+)
Second

delay of the mobile-terminated
party upon successful call
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

975
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Alerting)
(MTC)
[0,+)
Number

(alerting) delay of the mobileterminated party upon
overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MTC)
[0.00,10
0.00]

(alerting) delays experienced by
the mobile-terminated party
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

976
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MTC)
[0,+)
Number

(Connect Ack) experienced by
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MTC)
[0,+)
Second

Ack) delay of the mobileterminated party upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

977
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Connect Ack)
(MTC)
[0,+)
Number

overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MTC)
[0.00,10
0.00]
Proportion of call connection

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

978
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,+)
Second
Average RAB duration upon

l SRAN8.0/
GBSS15.0/
RAN 15.0
Average RAB duration (s) =

Total RAB duration/Number of
RAB durations
- 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
Service
Duration Times
[0,+)
Number

duration is below the threshold
for short RAB duration upon
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

979
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Service
Duration(MOC)
[0,+)
Second
Average call duration of calls

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Short Calls
(MOC)
[0,+)
Number
Number of short calls upon

l SRAN8.0/
GBSS15.0/
RAN 15.0
The mechanism for calculating

the number of short calls adds
l SRAN8.1/
the condition that short calls are
GBSS15.1/
initiated by the mobileRAN 15.1
originated party.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

980
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Short Calls
(MOC)
[0.00,10
0.00]
Proportion of short calls upon

l SRAN8.0/
GBSS15.0/
RAN 15.0

the proportion of short calls adds l SRAN8.1/
GBSS15.1/
originated party.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Service
Duration(MTC)
[0,+)
Second

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

981
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Short Calls
(MTC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
terminated.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Short Calls
(MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0

GBSS15.1/
terminated.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

982
Nastar
RAN-CS/AMR/Quality Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Success Times
[0,+)
Number

a call setup request.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Downlink OneWay Audio

Times
[0,+)
Number
Number of calls with downlink

one-way audio problems.
problems are detected by the
RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

983
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
[0.00,10
0.00]
Proportion of Downlink OneWay Audio = Downlink OneWay Audio Times/RAB Setup

Successes x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink OneWay Audio

Times
[0,+)
Number
Number of calls with uplink

Uplink one-way audio problems
are detected by the RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

984
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Uplink OneWay Audio
[0.00,10
0.00]
Proportion of Uplink One-Way

Audio = Uplink One-Way
Audio Times/RAB Setup
Successes x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Noise Times
[0,+)
Number
Number of calls with static

problems.
Static problems are detected by
the RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

985
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Noise
Proportion
[0.00,10
0.00]
Proportion of calls with static

problems.
l SRAN8.0/
GBSS15.0/
RAN 15.0

problems (%) = Number of calls
with static problems/Number of
connected calls (Connect Ack) x
100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

986
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SQI Reports
[0,+)
Number
Number of signal quality

indicator (SQI) reports
generated during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1. Signal quality indicator (SQI)

indicates signal quality on the
uplink to show voice quality
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
2. The RNC collects statistics on

the average SQI value and
divides signal quality into
different levels according to SQI
values:
l SRAN10.1/
GBSS17.1/
RAN17.1
RAN14.0: Excellent (SQI<=

(400,500]), Good (SQI<=
(300,400]), Accept (SQI<=
(200,300]), Poor (SQI<=
(100,200]), Bad (SQI<=
[0,100]).
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
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 03 (2015-07-30)

987
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average SQI
[0,+)
N/A
Average SQI value in the SQI

reports generated during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal SQIs
[0,+)
Number
Number of abnormal SQI values

in the SQI reports.
A SQI value is abnormal if the
SQI value of a call is below the
SQI exception threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

988
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Abnormal SQIs
[0.00,10
0.00]
Proportion of calls with

abnormal SQI values.
l SRAN8.0/
GBSS15.0/
RAN 15.0

abnormal SQI values (%) =
Number of calls with abnormal
SQI values/Number of
100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Voice Quality
with SQI as
Excellent
[0.00,10
0.00]
Proportion of calls whose SQI is

Excellent during successful
voice service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
This parameter is applicable

only to the AMR service.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

989
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Voice Quality
with SQI as
Good
[0.00,10
0.00]

Good during successful voice
service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Voice Quality
with SQI as
Accept
[0.00,10
0.00]

Accept during successful voice
service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

990
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Voice Quality
with SQI as
Poor
[0.00,10
0.00]

Poor during successful voice
service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Voice Quality
with SQI as Bad
[0.00,10
0.00]

Bad during successful voice
service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

991
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Level 1 Uplink
BLER
[0.00,10
0.00]
Proportion of level 1 uplink

BLER values upon successful
call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BLER is short for block error

rate.
l SRAN8.1/
GBSS15.1/
RAN 15.1

Standard for level 1: 0-0.78%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 2 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
Standard for level 2:

0.78%-1.56%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

992
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Level 3 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1

1.56%-3.12%
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 4 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1

3.12%-6.24%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

993
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Level 5 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1

6.24%-12.48%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 6 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
Standard for level 6: above

12.48%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

994
Nastar
RAN-CS/VP/Accessibility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Same as the related counter in

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

995
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

996
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

997
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
Release Times
Before
Connection
Acknowledgme
nt
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

998
Nastar
RAN-CS/VP/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

999
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1000
Nastar
RAN-CS/VP/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1001
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1002
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1003
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1004
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1005
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1006
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MOC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1007
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Alerting)
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MOC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1008
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MOC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1009
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Connect Ack)
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MOC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1010
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MTC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1011
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Alerting)
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MTC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1012
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MTC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1013
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Connect Ack)
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MTC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1014
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overshort RAB
Service
Duration Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1015
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Service
Duration(MOC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Short Calls
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1016
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Short Calls
(MOC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Service
Duration(MTC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1017
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Short Calls
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Short Calls
(MTC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1018
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Setup Requests
(MOC)
[0,+)
Number
Number of SMS service setup

requests initiated by the mobileterminated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Setup Failures
(MOC)
[0,+)
Number
Number of failed SMS service

setups initiated by the mobileoriginated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1019
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Setup Success
Rate (MOC)
[0.00,10
0.00]
Number of successful SMS

service setups initiated by the
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Setup Requests
(MTC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1020
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Setup Failures
(MTC)
[0,+)
Number

setups initiated by the mobileterminated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Setup Success
Rate (MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

1021
Nastar
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
Solution
Version
RAB Setup
Requests
[0,+)
Numb
er

initiated by a VIP subscriber after
network access.
l SRAN8.0/
GBSS15.0/
RAN 15.0

bearer.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Numb
er

experienced by a VIP subscriber
after network access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1022
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Numb
er
Number of successful RAB setups

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,1
00.00]
RAB setup success rate

l SRAN8.0/
GBSS15.0/
RAN 15.0
RAB setup success rate = Number l SRAN8.1/

of successful RAB setups/Number
GBSS15.1/
of RAB setup requests x 100%.
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1023
Nastar
RAN-PS/PS R99/Retainability Evaluation

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Numb
er
See RAB Setup Success Times in

RAN-PS/PS R99/Accessibility
Evaluation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Numb
er

subscriber abnormally releases an
RAB after network access and
successful service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1024
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,1
00.00]
Proportion of abnormal RAB

releases experienced by a VIP
subscriber after network access
and successful service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

releases = Number of abnormal
RAB releases/Number of
successful call setups x 100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1025
Nastar
RAN-PS/PS R99/Delay Evaluation

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numb
er

during call initiation, that is,
number of RAB setup delays.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,
+)
Secon
d
Average RAB setup delay during

call initiation.
Average RAB setup delay = Sum
of RAB setup delays/Number of
RAB setup delays.
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.
from the CN.
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1026
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,
+)
Numb
er

setup delay during call initiation is
overlong
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,1
00.00]
Proportion of times that the RAB

overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Proportion of overlong RAB setup

delays = Number of overlong RAB
setup delays x 100% = Number of
overlong RAB setup delays/
x 100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1027
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,
+)
Numb
er
Number of times that the call setup

delay of the mobile-originated
initiation is overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,
+)
Secon
d
Average call delay of the mobileoriginated party upon successful

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1028
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times(MOC)
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,1
00.00]
Proportion of overlong call setup

delays of the mobile-originated
initiation.
delays (mobile-originated) =
Number of overlong call setup
delays (mobile-originated)/
Number of call setup delays
(mobile-originated) x 100% =
connection setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1029
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,
+)
Numb
er

upon successful call initiation is
abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,
+)
Secon
d

mobile-terminated upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
Average call setup delay =Sum of

call setup delays/Number of call
setup delays.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Call setup delay = RAB request

connection acknowledge time Signaling access time.
l SRAN9.0/
GBSS16.0/
RAN16.0

l SRAN10.0/
GBSS17.0/
RAN17.0
Statistical point for signaling

access time: When an RRC
SETUP REQ or RELOC REQ
message is received or when an
request is initiated.
Issue 03 (2015-07-30)

l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1030
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,1
00.00]

delays experienced by the mobileterminated party upon successful
call initiation.
setup delays/Number of call setup
delays x 100% = Number of
overlong call setup delays/Number
of successful RRC connection
setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1031
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
Average RAB duration = RAB

duration/Number of RAB
durations.
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.
procedure is successful, after
receiving an RAB setup
connection acknowledge message,
the SRNC sends a Radio Access
message to the CN.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1032
Nastar
RAN-PS/PS R99/Rate Evaluation

Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Final Average
Negotiated
Downlink RAB
Rate
[0.00,
+)
kbit/s
Final negotiated rate of downlink

RAB when a VIP subscriber
initiates a common PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Average final negotiated rate of

downlink RAB = Final negotiated
rate of downlink RAB/Number of
times for collecting the final
negotiated rate of downlink RAB.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Final Average
Negotiated
Uplink RAB
Rate
[0.00,
+)
kbit/s
Final negotiated rate of uplink

l SRAN8.0/
GBSS15.0/
RAN 15.0

uplink RAB = Final negotiated
rate of uplink RAB/Number of
negotiated rate of uplink RAB.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1033
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
[0,
+)
MB
Downlink traffic volume of all

common PS services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Transmission
Duration
[0,
+)
Second
Average downlink transmission

duration for all common PS
services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1034
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Downlink
Throughput
[0.00,
+)
kbit/s
Average downlink throughput for

all common PS services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Average downlink throughput =

Downlink traffic volume/
Downlink data transmission
duration.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Downlink
Throughput
Times
[0,
+)
Numbe
r
Number of times that among all

common PS services, the average
downlink throughput for one RAB
setup is below a threshold for low
average downlink throughput.
you create a task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1035
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Uplink Traffic
Volume
[0,
+)
MB
Uplink traffic volume for all

common PS services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Transmission
Duration
[0,
+)
Second
Average uplink transmission

services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1036
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Average Uplink
Throughput
[0.00,
+)
kbit/s
Average uplink throughput rate for

l SRAN8.0/
GBSS15.0/
RAN 15.0
Average uplink throughput = Total

uplink traffic volume/Total uplink
transmission duration
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Uplink
Throughput
Times
[0,
+)
Numbe
r

uplink throughput for one RAB
average uplink throughput.
you create a task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1037
Nastar
RAN-PS/PS R99/Quality Evaluation

Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Proportion of
Level 1 Uplink
BLER
[0.00,
100.00
]
Proportion of level 1 uplink BLER

values upon successful call
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
This parameter is applicable only

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Standard for level 1: 0 =< X

=< 0.39%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 2 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Standard for level 2: 0.39% < X

=< 0.78%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1038
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Proportion of
Level 3 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1

=< 3.12%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 4 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1

=< 6.24%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1039
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Proportion of
Level 5 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1

=< 12.48%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 6 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Standard for level 6: 12.48% <

X.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1040
Nastar
RAN-PS/HSDPA/Accessibility Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1041
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1042
Nastar
RAN-PS/HSDPA/Retainability Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1043
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,
100.00
]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1044
Nastar
RAN-PS/HSDPA/Delay Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1045
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,
100.00
]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1046
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1047
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,
100.00
]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1048
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1049
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,
100.00
]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1050
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1051
Nastar
RAN-PS/Rate Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
[0,
+)
MB

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Transmission
Duration
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1052
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Downlink
Throughput
[0.00,
+)
kbit/s

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Downlink
Throughput
Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1053
Nastar
RAN-PS/HSUPA/Accessibility Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1054
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1055
Nastar
RAN-PS/HSUPA/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1056
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1057
Nastar
RAN-PS/HSUPA/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,+)
Secon
d

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1058
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1059
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,+)
Secon
d

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1060
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1061
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,+)
Secon
d

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1062
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1063
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,+)
Secon
d

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1064
Nastar
RAN-PS/HSUPA/Rate Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink Traffic
Volume
[0,+)
MB
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Transmission
Duration
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1065
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Throughput
[0.00,+)
kbit/s
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Uplink
Throughput
Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1066
Nastar
RAN-PS/HSPA/Accessibility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1067
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1068
Nastar
RAN-PS/HSPA/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1069
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1070
Nastar
RAN-PS/HSPA/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1071
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1072
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1073
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1074
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1075
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1076
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1077
Nastar
RAN-PS/HSPA/Rate Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
[0,+)
MB
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Transmission
Duration
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1078
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Throughput
[0.00,+)
kbit/s
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Downlink
Throughput
Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1079
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink Traffic
Volume
[0,+)
MB
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Transmission
Duration
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1080
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Throughput
[0.00,+)
kbit/s
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Uplink
Throughput
Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

1081
Nastar
RAN INTEGRATED/MULTI-RAB/Accessibility Evaluation
Issue 03 (2015-07-30)
Par
am
eter
Ra
ng
e
U Description
n
i
t
Mul
tiRA
B
Setu
p
Req
uest
s
[0,
+
)
N Number of RAB setup requests

u where multiple RABs are accessed
m during a call.
b
e
r
Mul
tiRA
B
Setu
p
Fail
ures
[0,
+
)
Mul
tiRA
B
Setu
p
Suc
cess
Rate
[0.
00,
10
0.0
0]
N Number of RAB setup failures

m during a call.
b
e
r
% Setup success rate for accessing

multiple RABs during a call.

1082
Nastar
RAN INTEGRATED/MULTI-RAB/Retainability Evaluation-With CS
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Mul
tiRA
B
Rele
ase
Tim
es
[
0
,
+
N
u
m
b
e
r
Abn
orm
al
Mul
tiRA
B
Rele
ase
Tim
es
[
0
,
+
Abn
orm
al
Mul
tiRA
B
Rele
ase
Rate
[
0
.
0
0
,
1
0
0
.
0
0
]
Number of RAB releases where

multiple CS RABs that contain at
least one CS RAB are released during
a call.
N
u
m
b
e
r
Number of abnormal RAB releases

where multiple CS RABs that contain
at least one CS RAB are released at a
time during a call.
% Abnormal RAB release rate for

releasing multiple RABs that contain
at least one CS RAB at a time during
a call.

1083
Nastar
RAN INTEGRATED/MULTI-RAB/Retainability Evaluation-Only PS

Par
am
eter
R
a
n
g
e
U Description
n
i
t
Mul
tiRA
B
Rele
ase
Tim
es
[
0
,
+
N Number of RAB releases where

u multiple RABs that contain only PS
m RABs are released during a call.
b
e
r
Abn
orm
al
Mul
tiRA
B
Rele
ase
Tim
es
[
0
,
+
Abn
orm
al
Mul
tiRA
B
Rele
ase
Rate
[
0
.
0
0
,
1
0
0
.
0
0
]
N
u
m
b
e
r

where multiple RABs that contain
only PS RABs are released during a
call.

only PS RABs during a call.
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.
Issue 03 (2015-07-30)

1084
Nastar
Active Cell/Common
Paramete
r
Range
Unit
Description
Supported Solution
Version
RNC ID
[0,4095]
N/A
ID of the RNC to which

an active cell belongs.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RNC
Name
N/A
N/A
Name of the RNC to

which an active cell
belongs.
l SRAN8.0/
GBSS15.0/RAN
15.0
Note: when name

information cannot be
obtained because
configuration
information has been
deleted or cell
information has not
been activated,
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1085
Nastar
Paramete
r
Range
Unit
Description
Supported Solution
Version
Cell ID
[0,65535]
N/A
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A

Note: when name
obtained because
configuration
deleted or cell
information has not
been activated,
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1086
Nastar
Paramete
r
Range
Unit
Description
Supported Solution
Version
Service
Type
N/A
N/A
Service type for a

counter.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Active Cell/RAN NET/NET/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
[0,+)
Number
Number of nonl SRAN8.0/

service setup
GBSS15.0/
requests that a VIP
RAN 15.0
group or VIP
l SRAN8.1/
subscriber initiates
GBSS15.1/
in an active cell.
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1087
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal TPs
on Access
[0,+)
Number
Number of times
that the TP value is
abnormal when a
VIP group or VIP
subscriber gains
access to the
network in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Set the exception

threshold when
you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal Ec/
Nos on Access
[0,+)
Number
Number of times
that the Ec/No
value is abnormal
when a VIP group
or VIP subscriber
gains access to the
network in an
active cell.
Set the exception
threshold when
you create a task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1088
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
RSCPs on
Access
[0,+)
Number
Number of times
that the RSCP
value is abnormal
when a VIP group
or VIP subscriber
gains access to the
network in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Set the exception

threshold when
you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
[0,+)
Number

service setup
GBSS15.0/
requests that a VIP
RAN 15.0
group or VIP
l SRAN8.1/
GBSS15.1/
in an active cell.
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1089
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Number
Number of service l SRAN8.0/

setup requests that
GBSS15.0/
a VIP group or VIP
RAN 15.0
subscriber initiates l SRAN8.1/
in an active cell.
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Failures
(Service)
[0,+)
Number
Number of service
setup failures that
a VIP group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1090
Nastar
Active Cell/RAN NET/NET/Retainability

Parameter
Range
Unit
Description
Supported Solution
Version
RRC Release
Times
[0,+)
Number
Number of times
that the RRC
connection setup
for a VIP group or
VIP subscriber is
released in an
active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RRC
Release Times
[0,+)
Number
Number of times
that the RRC
connection setup
for a VIP group or
VIP subscriber is
abnormally
released in an
active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1091
Nastar
Active Cell/RAN CS/AMR/Accessibility

Parameter
Range
Unit
Description
Supported
Solution Version
RAB Setup
Requests
[0,+)
Numbe
r
Number of CS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Numbe
r
Number of CS
service setup failures
that a VIP group or
VIP subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1092
Nastar
Active Cell/RAN CS/AMR/Retainability

Parameter
Range
Unit
Description
Supported
Solution Version
Best Cell Times

Before RAB
Release
[0,+)
Numb
er

an active cell serves
as the best cell before
the CS service of a
VIP group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Numb
er

the CS service of a
VIP group or VIP
subscriber is
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1093
Nastar
Active Cell/RAN CS/VP/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Number of CS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of CS
service setup
failures that a VIP
group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1094
Nastar
Active Cell/RAN CS/VP/Retainability

Parameter
Range
Unit
Description
Supported
Solution
Version
Best Cell Times

Before RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the CS
service of a VIP
group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the CS
service of a VIP
group or VIP
subscriber is
abnormally
released.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1095
Nastar
Active Cell/RAN CS/SMS/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
SMS Requests
(MOC)
[0,+)
Number
Number of SMS
requests that a VIP
group or VIP
subscriber sends in
an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
SMS Request
Failures(MOC)
[0,+)
Number
Number of SMS
requests that a VIP
group or VIP
subscriber fails to
send in an active
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1096
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SMS Requests
(MTC)
[0,+)
Number
Number of SMS
requests that a VIP
group or VIP
subscriber receives
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
SMS Request
Failures(MTC)
[0,+)
Number
Number of SMS
requests that a VIP
group or VIP
subscriber fails to
receive in an active
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1097
Nastar
Active Cell/RAN PS/R99/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Number of PS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of PS
service setup
failures that a VIP
group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1098
Nastar
Active Cell/RAN PS/R99/Retainability

Parameter
Range
Unit
Description
Supported
Solution Version
Best Cell Times

Before RAB
Release
[0,+)
Numbe
r

as the best cell
before the PS service
of a VIP group or
VIP subscriber is
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before RAB
Abnormal RAB
Release
[0,+)
Numbe
r

as the best cell
of a VIP group or
VIP subscriber is
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1099
Nastar
Active Cell/RAN PS/HSDPA/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Number of PS
service setup
requests that a
VIP group or VIP
subscriber
initiates in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of PS
l SRAN8.0/
service setup
GBSS15.0/
failures that a VIP
RAN 15.0
group or VIP
l SRAN8.1/
subscriber
GBSS15.1/
experiences in an
RAN 15.1
active cell.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1100
Nastar
Active Cell/RAN PS/HSDPA/Retainability

Parameter
Range
Unit
Description
Supported
Solution Version
Best Cell Times

Before RAB
Release
[0,+)
Numbe
r

the PS service of a
VIP group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Numbe
r

the PS service of a
VIP group or VIP
subscriber is
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1101
Nastar
Active Cell/RAN PS/HSUPA/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Number of PS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of PS
service setup
failures that a VIP
group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1102
Nastar
Active Cell/RAN PS/HSUPA/Retainability

Parameter
Range
Unit
Description
Supported
Solution
Version
Best Cell Times

Before RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the PS
service of a VIP
group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the PS
service of a VIP
group or VIP
subscriber is
abnormally
released.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1103
Nastar
Active Cell/RAN PS/HSPA/Accessibility

Parameter
Range
Unit
Description
Supported
Solution Version
RAB Setup
Requests
[0,+)
Number
Number of PS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of PS
service setup
failures that a VIP
group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1104
Nastar
Active Cell/RAN PS/HSPA/Retainability

Parameter
Range
Unit
Description
Supported
Solution Version
Best Cell Times

Before RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the PS
service of a VIP
group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the PS
service of a VIP
group or VIP
subscriber is
abnormally
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
4.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.
Issue 03 (2015-07-30)

1105
Nastar
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.
Common
Parameter
Range
Unit
Description
Supported
Solution
Version
In-depth
Analysis
N/A
N/A
When the
dimension is
Group, this
parameter is
used to switch
from the
analysis results
of a VIP group
to the analysis
results of VIP
subscribers in
this group.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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
group.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
User ID
[1,+)
N/A
Identity of a VIP
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
User ID, which

is created by the
system when
creating a VIP
User in the VIP
Group
Management.
Issue 03 (2015-07-30)

1106
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Alias
N/A
N/A
Alias of a VIP
subscriber.
Query the name
of a VIP
subscriber using
VIP group
management
based on the
IMSI of the VIP
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
IMSI
N/A
N/A
IMSI
information of a
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Note: Only
when you have
the "User
Identity" right,
you can view the
IMSI
information.
IMEI-TAC
00000000-9999
9999
N/A
First eight digits

in the IMEI of a
UE.
IMEI is
international
mobile
equipment
identity for short
and TAC is type
approval code
for short.
Terminal Model
Issue 03 (2015-07-30)
N/A
N/A
Type of the UE
used by a VIP
subscriber.
Query the UE
type of a VIP
subscriber using
terminal type
management
based on the
IMEI-TAC of
the VIP
subscriber.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1107
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Service Type
N/A
N/A
Service type for

a counter.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Number of
Abnormal
Indicator
[0,+)
Number
Number of
abnormal
counters in all
counter sets
determined
based on the
result thresholds
set when
engineers create
a task.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Reports
[0,+)
Number
Indicates the
number of
records
generated for all
service types
during the
network access
of a subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests (NonService)
[0,+)
Number
Number of nonservice RRC

setup requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1108
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Number
Number of
service RRC
setup requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Requests
[0,+)
Number
Number of RRC
reestablishment
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Number
Number of
failed RRC
reestablishment
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Success Rate
[0,100]
RRC
reestablishment
success rate.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
intra-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Mobility
Issue 03 (2015-07-30)

1109
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
failed intraRAT outgoing
handovers after
a UE initiates
intra-RAT
outgoing
handover
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Success Rate
[0,100]
Ratio of
successful intraRAT outgoing
handovers to
intra-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
intra-RAT
outgoing
handover
requests during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Success Rate
(with Data
Transmission)
[0,100]
Ratio of
handovers to
intra-RAT
outgoing
handover
requests
initiated by a UE
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1110
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
failed interRAT outgoing
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Success Rate
[0,100]
Ratio of
successful interRAT outgoing
handovers to
inter-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1111
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Success Rate
(with Data
Transmission)
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a UE
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Success
Rate
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1112
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through CSFB
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Success
Rate (with Data
Transmission)
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through CSFB
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a UE
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1113
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Success Rate
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through
SRVCC during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Success Rate
(with Data
Transmission)
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through
SRVCC during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Parameters for Viewing LTE VIP Analysis-RAN PS Results

This section describes the parameters for querying LTE VIP analysis-RAN PS results. You can
Issue 03 (2015-07-30)

1114
Nastar
All/GBR/GBR-QCI 1 to 4-Accessibility
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Requests
[0,+)
Number
Number of ERAB (short for

Evolved Radio
Access Bearer)
setup requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Number
Number of
failed E-RAB
setups after a
UE initiates ERAB setup
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Times
[0,+)
Number
Number of
successful ERAB setups
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Rate
[0,100]
Ratio of
successful ERAB setups to
E-RAB setup
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
All/GBR/GBR-QCI 1 to 4-Retainability
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1115
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal ERAB Release

Times
[0,+)
Number
Number of
abnormal ERAB releases
due to E-RAB
exceptions
among
successful ERAB setups.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate
[0,100]
Ratio of
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Times (with
Data
Transmission)
[0,+)
Number
Number of
with data
transmission
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate (with Data
Transmission)
[0,100]
Ratio of
with data
transmission
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1116
Nastar
All/GBR/GBR-QCI 1 to 4-Service Evaluation for Delay

Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB Setup

Delay
[0,+)
Second
Average ERAB setup

delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB setup

delay = E-RAB
setup delay/
Number of ERAB setup
delay reports
The E-RAB
setup delay
indicates the
duration from
the time when
the Initial
Context Setup
Request
message is sent
to the time when
the Initial
Context Setup
Response
message is
received or that
from the time
when the ERAB Setup
Request
message is sent
to the time when
the E-RAB
Setup Response
message is
received.
Issue 03 (2015-07-30)

1117
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Long E-RAB
Setup Delay
Times
[0,+)
Number
Number of
times when the
E-RAB setup
delay is greater
than the long ERAB setup
delay threshold.
The threshold is
set during
analysis task
creation.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion of
long E-RAB
Setup Delay
[0,100]
Ratio of long ERAB setup

delay to the
number of ERAB setup
delay reports.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB Duration
[0,+)
Second
Average ERAB duration

recorded in a
report.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1118
Nastar
All/GBR/GBR-QCI 1 to 4-Service Evaluation for Voice

Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink VQI
[1.00,5.00]
N/A
Average value
for the downlink
voice quality
indicators
(VQIs) of
successful call
setups.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
VQI is the Mean

Opinion Score
(MOS) and
indicates the
voice quality of
a call. The value
of the voice
quality ranges
from 1 to 5. A
larger value
indicates better
voice quality.
Average value
for the downlink
VQIs of
successful call
setups =
Aggregated
value of
downlink VQIs/
Total number of
downlink VQI
tests
Poor Downlink
VQI Times
[0,+)
Number
Number of poor
downlink VQIs.
The exception
threshold is set
by engineers
during task
creation.
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1119
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink VQI
[1.00,5.00]
N/A
Average value
for the uplink
VQIs of
successful call
setups.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
VQI is the MOS

and indicates the
voice quality of
a call. The value
of the voice
quality ranges
from 1 to 5. A
larger value
indicates better
voice quality.
Average value
for the uplink
VQIs of
successful call
setups =
Aggregated
value of uplink
VQIs/Total
number of
uplink VQI tests
Poor Uplink
VQI Times
[0,+)
Number
Number of poor
uplink VQIs.
The exception
threshold is set
by engineers
during task
creation.
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1120
Nastar
All/GBR/GBR-QCI 1 to 4-Service Evaluation for Rate

Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
(MB)
[0,+)
MB
Total downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Transmission
Duration(s)
[0,+)
Second
Average
downlink data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Throughput
[0,+)
kbit/s
Average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
downlink
throughput =
Total downlink
throughput/
Total downlink
data
transmission
duration
Issue 03 (2015-07-30)

1121
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Low Average
Downlink
Throughput
Times
[0,+)
Number
Number of
times when the
average
downlink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
Uplink Traffic
Volume(MB)
[0,+)
MB
Total uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Transmission
Duration(s)
[0,+)
Second
Average uplink
data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0,+)
kbit/s
Average uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average uplink
throughput =
Total uplink
throughput/
Total uplink
data
transmission
duration
Issue 03 (2015-07-30)

1122
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Low Average
Uplink
Throughput
Times
[0,+)
Number
Number of
times when the
average uplink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
All/NonGBR/NonGBR-QCI 5 to 9-Accessibility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Requests
[0,+)
Number

requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Number
Number of
failed E-RAB
setups after a
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1123
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Rate
[0,100]
Ratio of
E-RAB setup
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
All/NonGBR/NonGBR-QCI 5 to 9-Retainability
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Times
[0,+)
Number
Number of
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate
[0,100]
Ratio of
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1124
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version

Times (with
Data
Transmission)
[0,+)
Number
Number of
with data
transmission
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate(with Data
Transmission)
[0,100]
Ratio of
with data
transmission
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
All/NonGBR/NonGBR-QCI 5 to 9-Service Evaluation for Delay
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1125
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average ERAB Setup

Delay
[0,+)
Second
Average ERAB setup

delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB setup

delay = E-RAB
setup delay/
delay reports
The E-RAB
setup delay
indicates the
duration from
the time when
the Initial
Context Setup
Request
message is sent
to the time when
the Initial
Context Setup
Response
message is
received or that
from the time
when the ERAB Setup
Request
message is sent
to the time when
the E-RAB
Setup Response
message is
received.
Issue 03 (2015-07-30)

1126
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Long E-RAB
Setup Delay
Times
[0,+)
Number
This parameter
indicates the
number of times
when the ERAB setup
delay is greater
delay threshold.
The threshold is
set during
analysis task
creation.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion of
long E-RAB
Setup Delay
[0,100]

delay to the
delay reports.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0,+)
Second
Average ERAB
occupation
duration
recorded in a
report.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
All/NonGBR/NonGBR-QCI 5 to 9-Service Evaluation for Rate
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
[0,+)
MB
Total downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1127
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Transmission
Duration
[0,+)
Second
Average
downlink data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Throughput
[0,+)
kbit/s
Average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
downlink
throughput =
Total downlink
throughput/
Total downlink
data
transmission
duration
Low Average
Downlink
Throughput
Times
[0,+)
Number
Number of
times when the
average
downlink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
Uplink Traffic
Volume
Issue 03 (2015-07-30)
[0,+)
MB
Total uplink
throughput of
PS services.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1128
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Transmission
Duration
[0,+)
Second
Average uplink
data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0,+)
kbit/s
Average uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average uplink
throughput =
Total uplink
throughput/
Total uplink
data
transmission
duration
Low Average
Uplink
Throughput
Times
[0,+)
Number
Number of
times when the
average uplink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
Parameters for Viewing LTE VIP Analysis-Active Cell Results

This section describes the parameters for querying LTE VIP analysis-active cell results. You
Issue 03 (2015-07-30)

1129
Nastar
Common
Parameter
Range
Unit
Description
Supported
Solution
Version
eNodeB ID
N/A
N/A
ID of an eNodeB.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
eNodeB Name
1 to 64
charact
ers
N/A
Name of an eNodeB.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
Cell ID
N/A
N/A
ID of a cell.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
Cell Name
1 to 64
charact
ers
N/A
Name of a cell.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
N/A
N/A
Service Type
Note: when name information

cannot be obtained because
configuration information has
been deleted or cell information
has not been activated,

eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
RAN NET-Accessibility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
[0,+)
Number

setup requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1130
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Number
Number of
service RRC
setup requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Requests
[0,+)
Number
Number of RRC
reestablishment
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Number
Number of
failed RRC
reestablishment
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
intra-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RAN NET-Mobility
Issue 03 (2015-07-30)

1131
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Failures
[0,+)
Number
Number of
failed intraRAT incoming
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1132
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Incoming
Handover
Failures
[0,+)
Number
Number of
failed interRAT incoming
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1133
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through CSFB
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1134
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through
SRVCC during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RAN PS-All/GBR (Including QCI 1 to 4)/NonGBR (Including QCI 5 to 9)Accessibility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Requests
[0,+)
Number

requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Number
Number of
failed E-RAB
setups initiated
by a VIP group
or VIP
subscriber in an
active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1135
Nastar
RAN PS-All/GBR (Including QCI 1 to 4)/NonGBR (Including QCI 5 to 9)Retainability

Parameter
Range
Unit
Description
Supported
Solution
Version

Times
[0,+)
Number
Number of
abnormal ERAB releases of
a VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Times (with
Data
Transmission)
[0,+)
Number
Number of
a VIP group or
VIP subscriber
in an active cell
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Parameters for Viewing LTE VIP Analysis-Active MME Results

This section describes the parameters for querying LTE VIP analysis-active mme results. You
Common
Parameter
Ran
ge
Unit
Description
Supported
Solution Version
MME
N/A
N/A
ID of a MME.
eRAN 6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
MME format:
MMEGroupIDMMECode
Service Type
Issue 03 (2015-07-30)
N/A
N/A
Service type for a

counter.

eRAN6.0/
eRAN6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
1136
Nastar
RAN NET-Mobility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of intra-RAT
outgoing handover
requests initiated by a VIP
group or VIP subscriber in
an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er
Number of failed intraRAT outgoing handover

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Failures
[0,+)
Numb
er
Number of failed intraRAT incoming handover

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

an active mme during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er
Number of failed interRAT outgoing handover

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1137
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Failures
[0,+)
Numb
er
Number of failed interRAT incoming handover

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
an active mme through
CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Numb
er

CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Numb
er

CSFB during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Numb
er

SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1138
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Numb
er

SRVCC during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Parameter
Range
Unit
Description
Supported
Solution Version
E-RAB Setup
Requests
[0,+)
Numbe
r
Number of E-RAB
setup requests
initiated by a VIP
group or VIP
subscriber in an
active mme.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Numbe
r
Number of failed ERAB setups initiated

by a VIP group or
VIP subscriber in an
active mme.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
subscriber in an active
mme.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

1139
Nastar
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times (with
Data
Transmission)
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
mme during data
transmission.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
RAN PS-All/GBR (Including QCI 1 to 4)/NonGBR (Including QCI 5 to 9)-Service

Evaluation for Delay
Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported Solution
Version
E-RAB Setup
Success Times
[0,+)
Nu
mbe
r
Number of successful
E-RAB setups after a
UE initiates E-RAB
setup requests.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average E-RAB
Setup Delay(s)
[0,+)
Sec
ond
Average E-RAB setup

delay. Average E-RAB
setup delay = E-RAB
setup delay/Number of
E-RAB setup delay
reports The E-RAB
setup delay indicates
the duration from the
time when the Initial
Context Setup Request
message is sent to the
Context Setup
Response message is
received or that from the
time when the E-RAB
Setup Request message
is sent to the time when
the E-RAB Setup
Response message is
received.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

1140
Nastar
RAN PS-All/GBR/GBR-QCI 1-Service Evaluation for Voice

Parameter
Range
Uni
t
Description
Supported Solution
Version
Downlink VQI
[1.00,5.00]
N/A
Average value for the

downlink voice quality
indicators (VQIs) of
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the Mean

Opinion Score (MOS)
and indicates the voice
quality of a call. The
value of the voice
quality ranges from 1 to
5. A larger value
indicates better voice
quality.
downlink VQIs of
successful call setups =
Aggregated value of
downlink VQIs/Total
number of downlink
VQI tests
Uplink VQI
[1.00,5.00]
N/A

uplink VQIs of
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the MOS and

indicates the voice
value of the voice
5. A larger value
quality.
uplink VQIs of
Aggregated value of
uplink VQIs/Total
number of uplink VQI
tests
Issue 03 (2015-07-30)

1141
Nastar

Evaluation for Rate
Parameter
Range
Unit
Description
Supported Solution
Version
Downlink
Traffic Volume
(MB)
[0,+)
MB
Total downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Downlink
Transmission
Duration(s)
[0,+)
Downlink data
transmission duration of
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average
Downlink
Throughput
(kbit/s)
[0,+)
kbit/s
Average downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink Traffic
Volume(MB)
[0,+)
MB
Total uplink throughput

of PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink
Transmission
Duration(s)
[0,+)
Secon
d
Uplink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average Uplink
Throughput
(kbit/s)
[0,+)
kbit/s
Average uplink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average downlink
throughput = Total
downlink throughput/
Total downlink data
Average uplink
throughput = Total
uplink throughput/Total
uplink data
Parameters for Viewing LTE VIP Analysis-Active TAC Results

This section describes the parameters for querying LTE VIP analysis-active tac results. You can
Issue 03 (2015-07-30)

1142
Nastar
Common
Parameter
Ran
ge
Unit
Description
Supported
Solution Version
TAC
[0,65
535]
N/A
Indicates the
tracking area code
of a cell.
eRAN6.0/
eRAN6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
Service Type
N/A
N/A
Service type for a

counter.
eRAN6.0/
eRAN6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Un
it
Description
Supported
Solution
Version
RRC Setup
[0,+)
Nu
mb
er

setup requests initiated by a
VIP group or VIP subscriber
in an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Setup
Requests
(Service)
[0,+)
Nu
mb
er
Number of service RRC setup

group or VIP subscriber in an
active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Requests
[0,+)
Nu
mb
er
Number of RRC
reestablishment requests
initiated by a VIP group or
VIP subscriber in an active
mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Nu
mb
er
Number of failed RRC

mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1143
Nastar
RAN NET-Mobility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of intra-RAT
outgoing handover
an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

an active cell during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1144
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
an active cell through
CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Numb
er

CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Numb
er

CSFB during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Numb
er

SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1145
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Numb
er

SRVCC during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Parameter
Range
Unit
Description
Supported
Solution Version
E-RAB Setup
Requests
[0,+)
Numbe
r
Number of E-RAB
setup requests
initiated by a VIP
group or VIP
subscriber in an
active cell.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Numbe
r

by a VIP group or
active cell.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
cell.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

1146
Nastar
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times (with
Data
Transmission)
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
cell during data
transmission.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported Solution
Version
E-RAB Setup
Success Times
[0,+)
Nu
mbe
r
UE initiates E-RAB
setup requests.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average E-RAB
Setup Delay(s)
[0,+)
Sec
ond
Average E-RAB setup

setup delay = E-RAB
E-RAB setup delay
reports The E-RAB
Context Setup
Response message is
time when the E-RAB
the E-RAB Setup
Response message is
received.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

1147
Nastar

Parameter
Range
Uni
t
Description
Supported Solution
Version
Downlink VQI
[1.00,5.00]
N/A

eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the Mean

Opinion Score (MOS)
value of the voice
5. A larger value
quality.
downlink VQIs of
Aggregated value of
downlink VQIs/Total
number of downlink
VQI tests
Uplink VQI
[1.00,5.00]
N/A

uplink VQIs of
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the MOS and

indicates the voice
value of the voice
5. A larger value
quality.
uplink VQIs of
Aggregated value of
uplink VQIs/Total
tests
Issue 03 (2015-07-30)

1148
Nastar

Evaluation for Rate
Parameter
Range
Unit
Description
Supported Solution
Version
Downlink
Traffic Volume
(MB)
[0,+)
MB
Total downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Downlink
Transmission
Duration(s)
[0,+)
Downlink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average
Downlink
Throughput
(kbit/s)
[0,+)
kbit/s
Average downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink Traffic
Volume(MB)
[0,+)
MB

of PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink
Transmission
Duration(s)
[0,+)
Secon
d
Uplink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average Uplink
Throughput
(kbit/s)
[0,+)
kbit/s
Average uplink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average downlink
throughput = Total
Total downlink data
Average uplink
throughput = Total
uplink data
4.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.
Issue 03 (2015-07-30)

1149
Nastar
Common
Parameter
Rang
e
Unit
Description
Supported
Solution Version
Deep
Analysis
N/A
N/A
When the dimension is Group, this

parameter is used to switch from the
analysis results of a VIP group to
those of the VIP subscribers in this
group.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
When the dimension is User, this

analysis results of counters to those
of the calls.
Group
Name
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
IMSI
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

"User Identity" right, you can view
the IMSI information.
MSISDN
N/A
N/A
MSISDN information of a
subscriber.
the MSISDN information.
Issue 03 (2015-07-30)
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
IMEI-TAC
N/A
N/A
International mobile equipment

identity-type allocation code
(IMEI-TAC) of the terminal used
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User ID
N/A
N/A
ID of a VIP subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Alias
N/A
N/A
Alias of a VIP subscriber. You can

obtain the user name in the VIP
Group Management window based
on the IMSI of the VIP subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Terminal
Model
N/A
N/A

subscriber. You can obtain the
terminal type in the Terminal Type
Management window based on the
IMEI-TAC of the terminal used by
the VIP subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

1150
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution Version
Total
Reports
[0,
+)
Numb
er
Indicates the number of records

generated for all service types
during the network access of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Service
Type
N/A
N/A
Service type for a following

counter.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Number of
Abnormal
KPIs
[0,
+)
Numb
er
Number of abnormal counters in all

counter sets determined based on
the result thresholds set when
engineers create a task.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGSN/Accessability/Attach
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN-Attach
Requests
[0,+)
Numb
er
Number of attach process requests

by a VIP subscriber on the GSM
and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Attach processes include:

GPRS attach
Combined attach
SGSN-Attach
Failures
[0,+)
Numb
er
Number of attach process failures

and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN-Attach
Success Rate
[0.00,10
0.00]
Attach process success rate by a

VIP subscriber on the GSM and
UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Attach success rate = (1 - Number

of attach failures/Number of attach
requests) x 100%
SGSN-Average
Attach Delay
Issue 03 (2015-07-30)
[0,+)
ms
Average delay of an attach process

and UMTS networks.

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
1151
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSNOverlong
Attach Delays
[0,+)
Numb
er
Number of delays that exceed the

exception threshold of an attach
process by a VIP subscriber on the
GSM and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN/Accessability/Service Req
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN-Service
Req Requests
[0,+)
Number
Number of service req process

requests by a VIP subscriber on
the GSM and UMTS network.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
The service req process

includes:
Service Request
SGSN-Service
Req Failures
[0,+)
Number

failures by a VIP subscriber on
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN-Service
Req Success
Rate
[0.00,100.
00]
Service req process success rate

by a VIP subscriber on the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Service req success rate = (1 Number of service req failures/

Number of service req
requests) x 100%
Issue 03 (2015-07-30)
SGSN-Average
Service Req
Delay
[0,+)
ms
Average delay of a service req

process by a VIP subscriber on
the GSM and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSNOverlong
Service Req
Delays
[0,+)
Number
Number of delays that exceed

the exception threshold of a
service req process by a VIP
subscriber on the GSM and
UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1152
Nastar
SGSN/Accessability/Paging
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN-Paging
Requests
[0,+)
Number
Number of paging process

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
The paging process includes

Paging.
SGSN-Paging
Failures
[0,+)
Number

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN-Paging
Success Rate
[0.00,100.
00]
Paging process success rate by

a VIP subscriber on the GSM
and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Paging success rate = (1 Number of paging failures/

Number of paging requests) x
100%
Issue 03 (2015-07-30)
SGSN-Average
Paging Delay
[0,+)
ms
Average delay of a paging

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSNOverlong
Paging Delays
[0,+)
Number

paging process by a VIP
UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1153
Nastar
SGSN/Accessability/PDP Act
Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Act
Requests
[0,+)
Numb
er
Number of PDP act process

requests by a VIP subscriber on the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP act processes include:

MS Init PDP Act
CN Init PDP Act
PDP Act
Failures
[0,+)
Numb
er

failures by a VIP subscriber on the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP Act
Success Rate
[0.00,100.
00]
PDP act process success rate by a

UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP act success rate = (1 - Number

of PDP act failures/Number of
PDP act requests) x 100%
Issue 03 (2015-07-30)
Average PDP
Act Delay
[0,+)
ms
Average delay of a PDP act

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Overlong PDP
Act Delays
[0,+)
Numb
er

exception threshold of a PDP act
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1154
Nastar
SGSN/Accessability/PDP Sec Act

Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Sec Act

Requests
[0,+)
Numbe
r
Number of PDP sec act process

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
The PDP sec act process

includes:
MS Init PDP Sec Act
CN Init PDP Sec Act
PDP Sec Act
Failures
[0,+)
Numbe
r

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP Sec Act

Success Rate
[0.00,100.0
0]
PDP sec act process success rate

and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP sec act success rate = (1 Number of PDP sec act failures/
Number of PDP sec act
requests) x 100%
Issue 03 (2015-07-30)
Average PDP
Sec Act Delay
[0,+)
ms
Average delay of a PDP sec act

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Overlong PDP
Sec Act Delays
[0,+)
Numbe
r

the exception threshold of a PDP
sec act process by a VIP
UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1155
Nastar
SGSN/Accessability/RAB Assignment
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB
Assignment
Requests
[0,+)
Numbe
r
Number of RAB Assignment

requests of a VIP subscriber on
the GSM/UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAB
Assignment
Failures
[0,+)
Numbe
r
Number of RAB assignment

failures of a VIP subscriber on
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAB
Assignment
Success Rate
[0.00,100.0
0]
RAB assignment success rate of

a VIP subscriber on the GSM/
UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAB assignment success rate =

(1 - Number of RAB assignment
failures/Number of RAB
Assignment requests) x 100%
Issue 03 (2015-07-30)
Average RAB
Assignment
Delay
[0,+)
ms
Average RAB assignment delay

of a VIP subscriber on the GSM/
UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Overlong RAB
Assignment
Delays
[0,+)
Numbe
r

assignment delay of a VIP
subscriber exceeds the
predefined exception threshold
on the GSM/UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1156
Nastar
SGSN/Accessability/PDN GW Dedicated Bearer Act

Parameter
Range
Unit
Description
Supported
Solution
Version
PDN GW
Dedicated
Bearer Act
Requests
[0,+)
Numbe
r
Number of PDN GW
Dedicated Bearer Act requests
of a VIP subscriber on the
GSM/UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
A PDN GW Dedicated Bearer

Act request indicates a PDN
GW dedicated bearer
activation.
PDN GW
Dedicated
Bearer Act
Failures
[0,+)
Numbe
r
Number of PDN GW dedicated

bearer activation failures of a
VIP subscriber on the GSM/
UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDN GW
Dedicated
Bearer Act
Success Rate
[0.00,100.
00]
PDN GW dedicated bearer

activation success rate of a VIP
subscriber on the GSM/UMTS
network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

activation success rate = (1 Number of PDN GW dedicated
bearer activation failures/
Number of PDN GW
Dedicated Bearer Act requests)
x 100%
Issue 03 (2015-07-30)
Average PDN
GW Dedicated
Bearer Act
Delay
[0,+)
ms
Average PDN GW dedicated

bearer activation delay of a VIP
network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Overlong PDN
GW Dedicated
Bearer Act
Delays
[0,+)
Numbe
r
Number of times that the PDN

GW dedicated bearer activation
delay of a VIP subscriber
exceeds the predefined
exception threshold on the
GSM/UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1157
Nastar
SGSN/Mobility/RAU
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra SGSN
RAU Requests
[0,+)
Number
Number of intra SGSN RAU

process requests by a VIP
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra SGSN RAU processes

include:
Intra RAU
Intra combined RAU
Periodic RAU
Periodic combined RAU
Intra SGSN
RAU Failures
[0,+)
Number

process failures by a VIP
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra SGSN
RAU Success
Rate
[0.00,100.
00]
Intra SGSN RAU process

success rate by a VIP
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra SGSN RAU success

rate = (1 - Number of intra
SGSN RAU failures/
requests) x 100%
Issue 03 (2015-07-30)
Average Intra
SGSN RAU
Delay
[0,+)
ms
Average delay of an intra

SGSN RAU process by a
VIP subscriber on the GSM
and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Intra
SGSN RAU
Delays
[0,+)
Number
Number of delays that

exceed the exception
threshold of an intra SGSN
RAU process by a VIP
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1158
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter SGSN
RAU Requests
[0,+)
Number
Number of inter SGSN RAU

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter SGSN RAU processes

include:
Inter RAU
Inter combined RAU
Inter SGSN
RAU Failures
[0,+)
Number

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter SGSN
RAU Success
Rate
[0.00,100.
00]
Inter SGSN RAU process

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

UMTS networks.
Issue 03 (2015-07-30)
Average Inter
SGSN RAU
Delay
[0,+)
ms
Average delay of an inter

and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Inter
SGSN RAU
Delays
[0,+)
Number

threshold of an inter SGSN
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAU (others)
Requests
[0.00,100.
00]
Number of other RAU

processes by a VIP
UMTS networks
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAU (others)
Failures
[0,+)
ms
Number of other RAU

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1159
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAU (others)
Success Rate
[0,+)
Number
Other RAU process success

rate by a VIP subscriber on
the GSM and UMTS
networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAU (others) success rate =

(1 - Number of RAU (others)
failures/Number of RAU
(others) requests) x 100%
SGSN/Mobility/Relocation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Relocation
Requests
[0,
+)
Number
Number of relocation process

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Relocation processes include:

Intra SRNS relocation
Inter SRNS relocation
Relocation
Failures
[0,
+)
Number

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Relocation
Success Rate
[0.00,1
00.00]
Relocation process success rate

and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Relocation success rate = (1 Number of relocation failures/

Number of relocation requests)
x 100%
Issue 03 (2015-07-30)
Average
Relocation
Delay
[0,
+)
ms
Average delay of a relocation

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong
Relocation
Delays
[0,
+)
Number

relocation process by a VIP
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1160
Nastar
SGSN/Mobility/System Change
Parameter
Range
Unit
Description
Supported
Solution
Version
System Change
Requests
[0,+)
Numb
er
Number of system change

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
System change processes

include:
3G to 2G system change
System Change
Failures
[0,+)
Numb
er

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
System Change
Success Rate
[0.00,100
.00]
System change process

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
System change success rate =

(1 - Number of system change
failures/Number of system
change requests) x 100%
Issue 03 (2015-07-30)
Average System
Change Delay
[0,+)
ms
Average delay of a system

change process by a VIP
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong
System Change
Delays
[0,+)
Numb
er

system change process by a
and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1161
Nastar
SGSN/PDP Modification/PDP Mod

Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Mod
Requests
[0,+)
Number
Number of PDP mod

subscriber on the GSM
and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDP mod processes

include:
MS Init PDP Mod
CN Init PDP Mod
PDP Mod
Failures
[0,+)
Number
Number of PDP mod

and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDP Mod
Success Rate
[0.00,100.
00]
PDP mod process success

rate by a VIP subscriber
on the GSM and UMTS
networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDP mod success rate = (1

- Number of PDP mod
failures/Number of PDP
mod requests) x 100%
Issue 03 (2015-07-30)
Average PDP
Mod Delay
[0,+)
ms
Average delay of a PDP

mod process by a VIP
and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong PDP
Mod Delays
[0,+)
Number

threshold of a PDP mod
process by a VIP
and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1162
Nastar
SGSN/Modification/PDN GW Initiated Bearer Mod

Parameter
Range
Unit
Description
Supported
Solution
Version
PDN GW
Initiated Bearer
Mod Requests
[0,+)
Number
Number of PDN GW
Initiated Bearer Mod
requests of a VIP
subscriber on the GSM/
UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
A PDN GW Initiated
Bearer Mod request
indicates a PDN GW
initiated bearer
modification.
PDN GW
Initiated Bearer
Mod Failures
[0,+)
Number
Number of PDN GW
initiated bearer
modification failures of a
VIP subscriber on the
GSM/UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDN GW
Initiated Bearer
Mod Success
Rate
[0.00,100.
00]
PDN GW initiated bearer

modification success rate
GSM/UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

= (1 - Number of PDN
GW initiated bearer
modification failures/
Number of PDN GW
requests) x 100%
Issue 03 (2015-07-30)
Average PDN
GW Initiated
Bearer Mod
Delay
[0,+)
ms
Average PDN GW
initiated bearer
modification delay of a
GSM/UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong PDN
GW Initiated
Bearer Mod
Delays
[0,+)
Number

VIP subscriber exceeds
the predefined exception
threshold on the GSM/
UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1163
Nastar
MME/Accessability/Attach
Parameter
Range
Unit
Description
Supported
Solution
Version
MME-Attach
Requests
[0,+)
Numbe
r
Number of attach process

requests by a VIP subscriber
on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
The attach process includes:

Attach
Combined Attach
MME-Attach
Failures
[0,+)
Numbe
r

failures by a VIP subscriber
on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Attach
Success Rate
[0.00,100.0
0]
Attach process success rate

LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Attach success rate = (1 Number of attach failures/

Number of attach requests) x
100%
Issue 03 (2015-07-30)
MME-Average
Attach Delay
[0,+)
ms
Average delay of an attach

process by a VIP subscriber
on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Overlong
Attach Delays
[0,+)
Numbe
r

threshold of an attach
on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1164
Nastar
MME/Accessability/Service Req
Parameter
Range
Unit
Description
Supported
Solution
Version
MME-Service
Req Requests
[0,+)
Numbe
r

subscriber on the LTE
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

includes:
Service Request
MME-Service
Req Failures
[0,+)
Numbe
r

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Service
Req Success
Rate
[0.00,100.
00]
Service req process success

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Service req success rate = (1

- Number of service req
failures/Number of service
req requests) x 100%
Issue 03 (2015-07-30)
MME-Average
Service Req
Delay
[0,+)
ms
Average delay of a service

req process by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Overlong
Service Req
Delays
[0,+)
Numbe
r

threshold of a service req
on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1165
Nastar
MME/Accessability/Default Bearer Act

Parameter
Range
Unit
Description
Supported
Solution
Version
Default Bearer
Act Requests
[0,+)
Numb
er
Number of Default Bearer

Act process requests by a VIP
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
The default bearer act

processes include:
Default bearer activation in
attach
Default Bearer
Act Failures
[0,+)
Numb
er

Act process failures by a VIP
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Default Bearer
Act Success
Rate
[0.00,100.
00]
Default Bearer Act process

network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Default Bearer Act success

rate = (1 - Number of Default
Bearer Act failures/Number
of Default Bearer Act
requests) x 100%
Issue 03 (2015-07-30)
Default Bearer
Act Delay
[0,+)
ms
Average delay of a Default

Bearer Act process by a VIP
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Overlong
Default Bearer
Act Delays
[0,+)
Numb
er

LTE network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0

1166
Nastar
MME/Accessability/Paging
Parameter
Range
Unit
Description
Supported
Solution
Version
MME-Paging
Requests
[0,+)
Numb
er

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
The paging process includes:

Paging.
MME-Paging
Failures
[0,+)
Numb
er

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Paging
Success Rate
[0.00,100.
00]
Paging process success rate

LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

100%
Issue 03 (2015-07-30)
MME-Average
Paging Delay
[0,+)
ms

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Overlong
Paging Delays
[0,+)
Numb
er

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1167
Nastar
MME/Accessability/Dedicated Bearer Act

Parameter
Range
Unit
Description
Supported
Solution
Version
Dedicated
Bearer Act
Requests
[0,+)
Numbe
r
Number of dedicated bearer

act process requests by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
The dedicated bearer act

process includes:
Dedicated bearer activation
procedure
Dedicated
Bearer Act
Failures
[0,+)
Numbe
r

act process failures by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Dedicated
Bearer Act
Success Rate
[0.00,100.
00]
Success rate of a dedicated

bearer act process by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Dedicated bearer act success

rate = (1 - Number of
dedicated bearer act failures/
act requests) x 100%
Issue 03 (2015-07-30)
Average
Dedicated
Bearer Act
Delay
[0,+)
ms
Average delay of a dedicated

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong
Dedicated
Bearer Act
Delays
[0,+)
Numbe
r

threshold of a dedicated
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1168
Nastar
MME/Accessability/PDN Connectivity
Parameter
Range
Unit
Description
Supported
Solution
Version
PDN
Connectivity
Requests
[0,+)
Number
Number of PDN
Connectivity process
requests by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
The PDN Connectivity

process includes:
UE requested PDN
connectivity
PDN
Connectivity
Failures
[0,+)
Number
Number of PDN
connectivity process
failures by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDN
Connectivity
Success Rate
[0.00,100.
00]
PDN Connectivity process

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDN Connectivity success

rate = (1 - Number of PDN
Connectivity failures/
Number of PDN
Connectivity requests) x
100%
Issue 03 (2015-07-30)
Average PDN
Connectivity
Delay
[0,+)
ms
Average delay of a PDN

Connectivity process by a
VIP subscriber on the LTE
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong PDN
Connectivity
Delays
[0,+)
Number

threshold of a PDN
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1169
Nastar
MME/Mobility/TAU
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra TAU
Requests
[0,+)
Numbe
r
Number of intra TAU process

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra TAU processes include:

Intra USN Intra E-UTRAN
TAU
Intra USN GERAN to EUTRAN Inter RAT TAU
Intra USN UTRAN to EUTRAN Inter RAT TAU
Intra USN E-UTRAN to
GERAN Inter RAT RAU
UTRAN Inter RAT RAU
Combined TAU
Intra USN GERAN to EUTRAN Inter RAT
Combined TAU
Intra USN UTRAN to EUTRAN Inter RAT
Combined TAU
Intra TAU
Failures
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra TAU
Success Rate
[0.00,100.
00]
Intra TAU process success

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra TAU success rate = (1 Number of intra TAU

failures/Number of intra TAU
requests) x 100%
Average Intra
TAU Delay
Issue 03 (2015-07-30)
[0,+)
ms

TAU process by a VIP
network.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
1170
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Intra
TAU Delays
[0,+)
Numbe
r

the exception threshold of an
intra TAU process by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter TAU
Requests
[0,+)
Numbe
r
Number of inter TAU process

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
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
Combined TAU
to E-UTRAN Combined
TAU
Inter TAU
Failures
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter TAU
Success Rate
[0.00,100.
00]
Inter TAU process success

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter TAU success rate = (1 Number of inter TAU

failures/Number of inter TAU
requests) x 100%
Issue 03 (2015-07-30)
Average Inter
TAU Delay
[0,+)
ms

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Inter
TAU Delays
[0,+)
Numbe
r

inter TAU process by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1171
Nastar
MME/Mobility/Handover
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra E-UTRAN
Handover
Requests
[0,+)
Numbe
r
Number of intra E-UTRAN

handover process requests by
a VIP subscriber on the LTE
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra E-UTRAN handover

processes include:
X2 Handover
Intra MME S1 Handover
Inter MME S1 Handover
Intra E-UTRAN
Handover
Failures
[0,+)
Numbe
r

handover process failures by
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra E-UTRAN
Handover
Success Rate
[0.00,100.
00]
Success rate of an intra EUTRAN handover process

LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

success rate = (1 - Number of
intra E-UTRAN handover
failures/Number of intra EUTRAN handover requests)
x 100%
Issue 03 (2015-07-30)
Average Intra
E-UTRAN
Handover Delay
[0,+)
ms
Average delay of an intra EUTRAN handover process

LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Intra
E-UTRAN
Handover
Delays
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1172
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter RAT
Handover
Requests
[0,+)
Numbe
r
Number of inter RAT

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter RAT handover

processes include:
Intra USN UTRAN Iu mode
to E-UTRAN Inter RAT
handover
Inter USN UTRAN Iu mode
handover
UTRAN Iu mode Inter RAT
handover
handover
Inter RAT
Handover
Failures
[0,+)
Numbe
r
Number of inter RAT

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter RAT
Handover
Success Rate
[0.00,100.
00]
Success rate of an inter RAT

handover process by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter RAT handover success

rate = (1 - Number of inter
RAT handover failures/
Number of inter RAT
handover requests) x 100%
Issue 03 (2015-07-30)
Average Inter
RAT Handover
Delay
[0,+)
ms

RAT handover process by a
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Inter
RAT Handover
Delays
[0,+)
Numbe
r

inter RAT handover process
LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1173
Nastar
MME/Bearer Modification/UE Requested Bearer Resource Allocation

Parameter
Range
Unit
Description
Supported
Solution
Version
UE Requested
Bearer
Resource
Allocation
Requests
[0,+)
Number
Number of UE requested
bearer resource allocation
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
The UE requested bearer

resource allocation process
includes:
UE requested bearer
resource allocation
UE Requested
Bearer
Resource
Allocation
Failures
[0,+)
Number
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
UE Requested
Bearer
Resource
Allocation
Success Rate
[0.00,100
.00]
Success rate of a UE
requested bearer resource
allocation process by a VIP
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
UE requested bearer
resource allocation success
rate = (1 - Number of UE
allocation failures/Number
of UE requested bearer
resource allocation
requests) x 100%
Issue 03 (2015-07-30)
UE Requested
Bearer
Resource
Allocation
Delay
[0,+)
ms
Average delay of a UE
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Overlong UE
Requested
Bearer
Resource
Allocation
Delays
[0,+)
Number

threshold of a UE requested
on the LTE network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0

1174
Nastar
MME/Bearer Modification/Bearer Mod

Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer Mod
Requests
[0,+)
Numb
er
Number of bearer mod process

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer mod processes include:

modification with bearer QoS
update
HSS Initiated Subscribed QoS
Modification
modification without bearer
QoS update
Bearer Mod
Failures
[0,+)
Numb
er

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer Mod
Success Rate
[0.00,100
.00]
Bearer mod process success

rate by a VIP subscriber on the
LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer mod success rate = (1 Number of bearer mod failures/

Number of bearer mod
requests) x 100%
Issue 03 (2015-07-30)
Average Bearer
Mod Delay
[0,+)
ms
Average delay of a bearer mod

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong
Bearer Mod
Delays
[0,+)
Numb
er

bearer mod process by a VIP
subscriber on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1175
Nastar
MME/Bearer Modification/Bearer Resource Mod

Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer
Resource Mod
Requests
[0,+)
Number
Number of bearer resource

mod process requests by a
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
The bearer resource mod

process includes:
UE requested bearer
resource modification
Bearer
Resource Mod
Failures
[0,+)
Number

mod process failures by a
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Bearer
Resource Mod
Success Rate
[0.00,100
.00]
Success rate of a bearer

resource mod process by a
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Bearer resource mod

success rate = (1 - Number
of bearer resource mod
failures/Number of bearer
resource mod requests) x
100%
Issue 03 (2015-07-30)
Bearer
Resource Mod
Delay
[0,+)
ms
Average delay of a bearer

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Overlong
Bearer
Resource Mod
Delays
[0,+)
Number

threshold of a bearer
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

1176
Nastar
GGSN/Accessability/Create PDP
Parameter
Range
Unit
Description
Supported
Solution
Version
Create PDP
Requests
[0,+)
Numb
er
Number of Create PDP

procedures of a VIP
UMTS network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create PDP
Failures
[0,+)
Numb
er

the GSM/UMTS network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create PDP
Success Rate
[0.00,100
.00]
Success rate of the Create PDP

procedures of a VIP
UMTS network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create PDP Success Rate = (1

- Number of Create PDP
failures/Number of Create
PDP requests) x 100%
GGSN/PDP Update/Update PDP

Parameter
Range
Unit
Description
Supported
Solution
Version
Update PDP
Requests
[0,+)
Numb
er
Number of Update PDP

procedures of a VIP subscriber
on the GSM/UMTS network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update PDP
Failures
[0,+)
Numb
er

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update PDP
Success Rate
[0.00,100.
00]
Success rate of the Update

PDP procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update PDP Success Rate = (1

- Number of Update PDP
failures/Number of Update
Issue 03 (2015-07-30)

1177
Nastar
SAE-GW/Accessability/Create Session
Parameter
Range
Unit
Description
Supported
Solution
Version
Create Session
Requests
[0,+)
Numbe
r
Number of Create Session

procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Session
Failures
[0,+)
Numbe
r

failures of a VIP subscriber
on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Session
Success Rate
[0.00,100.
00]
Success rate of the Create

Session procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Session Success Rate

= (1 - Number of Create
Session failures/Number of
Create Session requests) x
100%
SAE-GW/Accessability/Create Bearer
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Create Bearer
Requests
[0,+)
Number
Number of Create Bearer

procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Bearer
Failures
[0,+)
Number

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1178
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Create Bearer
Success Rate
[0.00,100.
00]

Bearer procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Bearer Success Rate

Bearer failures/Number of
Create Bearer requests) x
100%
SAE-GW/Accessability/Create Indirect Data Forwarding

Parameter
Range
Unit
Description
Supported
Solution
Version
Create Indirect
Data
Forwarding
Requests
[0,+)
Number
Number of Create
Indirect Data
Forwarding
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Indirect
Data
Forwarding
Failures
[0,+)
Number
Number of Create
Indirect Data
Forwarding failures
of a VIP subscriber on
the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Indirect
Data
Forwarding
Success Rate
[0.00,100.00]
Success rate of the

Create Indirect Data
Forwarding
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

Forwarding Success
Rate = (1 - Number of
Forwarding failures/
Number of Create
Indirect Data
Forwarding requests)
x 100%
Issue 03 (2015-07-30)

1179
Nastar
SAE-GW/Bearer Modification/Modify Bearer

Parameter
Range
Unit
Description
Supported
Solution
Version
Modify Bearer
Requests
[0,+)
Numb
er
Number of Modify
Bearer procedures of a
LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Failures
[0,+)
Numb
er
Number of Modify
Bearer failures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Success Rate
[0.00,100.00]
Success rate of the

Modify Bearer
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer Success

Modify Bearer failures/
Number of Modify
Bearer requests) x
100%
SAE-GW/Bearer Modification/Update Bearer
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Update Bearer
Requests
[0,+)
Numbe
r
Number of Update
LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update Bearer
Failures
[0,+)
Numbe
r
Number of Update
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1180
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Update Bearer
Success Rate
[0.00,100.00]
Success rate of the

Update Bearer
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update Bearer Success

Update Bearer failures/
Number of Update
Bearer requests) x 100%
SAE-GW/Bearer Modification/Modify Bearer Command

Parameter
Range
Unit
Description
Supported
Solution
Version
Modify Bearer
Command
Requests
[0,+)
Numbe
r
Number of Modify
Bearer Command
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Command
Failures
[0,+)
Numbe
r
Number of Modify
Bearer Command
failures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Command
Success Rate
[0.00,100.00]
Success rate of the

Modify Bearer
Command procedures
the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Command Success Rate
= (1 - Number of Modify
Bearer Command
failures/Number of
Modify Bearer
Command requests) x
100%
Issue 03 (2015-07-30)

1181
Nastar
SAE-GW/Bearer Modification/Bearer Resource Command

Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer Resource
Command
Requests
[0,+)
Number
Number of Bearer
Resource Command
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer Resource
Command
Failures
[0,+)
Number
Number of Bearer
Resource Command
failures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer Resource
Command
Success Rate
[0.00,100.00]
Success rate of the

Bearer Resource
Command procedures
the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer Resource
Command Success
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.
Issue 03 (2015-07-30)

1182
Nastar
Common
Parameter
Rang
e
Unit
Description
Supported Solution
Version
Deep
Analysis
N/A
N/A
When the dimension is

Group, this parameter is
used to switch from the
analysis results of a VIP
group to those of the VIP
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0

User, this parameter is used
to switch from the analysis
results of counters to those
of the calls.
Group
Name
N/A
N/A
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
IMSI
N/A
N/A
subscriber.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Note: Only when you have

the "User Identity" right,
you can view the IMSI
information.
MSISDN
N/A
N/A
subscriber.
you can view the MSISDN
information.
Issue 03 (2015-07-30)
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
IMEI-TAC
N/A
N/A
International mobile
equipment identity-type
allocation code (IMEITAC) of the terminal used
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
User ID
N/A
N/A
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Alias
N/A
N/A
Alias of a VIP subscriber.

You can obtain the user
name in the VIP Group
Management window based
on the IMSI of the VIP
subscriber.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0

1183
Nastar
Parameter
Rang
e
Unit
Description
Supported Solution
Version
Terminal
Model
N/A
N/A
Type of the terminal used by

a VIP subscriber. You can
obtain the terminal type in
the Terminal Type
on the IMEI-TAC of the
terminal used by the VIP
subscriber.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Total
Reports
[0,
+)
Number

network access of a
subscriber.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Service
Type
N/A
N/A

counter.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Number of
Abnormal
KPIs
[0,
+)
Number
Number of abnormal
counters in all counter sets
determined based on the
result thresholds set when
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
Combined
Attach Requests
[0,+)
Numb
er
Number of times that a

VIP subscriber initiates
the Combined Attach
procedure on the LTE
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Combined
Attach CS
Failures
[0,+)
Numb
er

Combined Attach
procedure initiated by a
LTE network fails.
PS 11.0/PS 12.0/PS
12.1/PS 13.0

1184
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Combined
Attach CS
Success Rate
[0.00,100.
00]
Success rate of the

Combined Attach
procedure, which is
initiated by a VIP
network, in the CS
domain.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Combined Attach CS
Success Rate = (1 Number of failed
Combined Attach
requests in the CS
domain/Number of
Combined Attach
requests) x 100%
Combined
Attach Delay
[0,+)
ms
Average delay of the

Combined Attach
LTE network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Overlong
Combined
Attach Delays
[0,+)
Numb
er

delay of the Combined
Attach procedure initiated
LTE network exceeds a
predefined exception
threshold.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution Version
SGs CS Paging
Requests
[0,+)
Numbe
r

the SGs CS Paging
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
The SGs CS Paging

procedure includes:
SGs Paging
Issue 03 (2015-07-30)

1185
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
SGs CS Paging
Failures
[0,+)
Numbe
r

SGs CS Paging procedure
initiated by a VIP
network fails.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
SGs CS Paging
Success Rate
[0.00,100
.00]
Success rate of the SGs

CS Paging procedure
initiated by a VIP
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
SGs CS Paging Success

failed SGs CS Paging
requests/Number of SGs
CS Paging requests) x
100%
SGs CS Paging
Delay
[0,+)
ms
Average delay of the SGs

CS Paging procedure
initiated by a VIP
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Overlong SGs
CS Paging
Delays
[0,+)
Numbe
r

delay of the SGs CS
Paging procedure
initiated by a VIP
network exceeds a
threshold.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
S1 CS Paging
Requests
[0,+)
Numbe
r

the S1 CS Paging
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
The S1 CS Paging
procedure includes:
Paging
S1 CS Paging
Failures
Issue 03 (2015-07-30)
[0,+)
Numbe
r

S1 CS Paging procedure
initiated by a VIP
network fails.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
1186
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
S1 CS Paging
Success Rate
[0.00,100
.00]
Success rate of the S1 CS

Paging procedure
initiated by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
S1 CS Paging Success
failed S1 CS Paging
requests/Number of S1
100%
S1 CS Paging
Delay
[0,+)
ms
Average delay of the S1

CS Paging procedure
initiated by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Overlong S1 CS
Paging Delays
[0,+)
Numbe
r

delay of the S1 CS Paging
threshold.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
S1 SMS Paging
Requests
[0,+)
Numbe
r

the S1 SMS Paging
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
The S1 SMS Paging

procedure includes:
Paging
S1 SMS Paging
Failures
Issue 03 (2015-07-30)
[0,+)
Numbe
r

S1 SMS Paging procedure
initiated by a VIP
network fails.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
1187
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
S1 SMS Paging
Success Rate
[0.00,100
.00]
Success rate of the S1

SMS Paging procedure
initiated by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
S1 SMS Paging Success

failed S1 SMS Paging
SMS Paging requests) x
100%
S1 SMS Paging
Delay
[0,+)
ms

initiated by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Overlong SMS
Paging Delays
[0,+)
Numbe
r

delay of the S1 SMS
Paging procedure
initiated by a VIP
network exceeds a
threshold.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGs SMS
Paging
Requests
[0,+)
Numbe
r

the SGs SMS Paging
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
The SGs SMS Paging

procedure includes:
SGs Paging
SGs SMS
Paging Failures
Issue 03 (2015-07-30)
[0,+)
Numbe
r

SGs SMS Paging
LTE network fails.

PS 11.0/PS 12.0/PS
12.1/PS 13.0
1188
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
SGs SMS
Paging Success
Rate
[0.00,100
.00]

initiated by a VIP
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
SGs SMS Paging Success

failed SGs SMS Paging
100%
SGs SMS
Paging Delay
[0,+)
ms

initiated by a VIP
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Overlong SGs
SMS Paging
Delays
[0,+)
Numbe
r

delay of the SGs SMS
Paging procedure
initiated by a VIP
network exceeds a
threshold.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution Version
Extended
Service Req
Requests
[0,+)
Numbe
r

subscriber initiates the
Extended Service Req
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
The Extended Service Req

procedure includes:
Extended Service Request
Extended
Service Req
Failures
Issue 03 (2015-07-30)
[0,+)
Numbe
r

procedure initiated by a VIP
network fails.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
1189
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Extended
Service Req
Success Rate
[0.00,1
00.00]
Success rate of the Extended

Service Req procedure
initiated by a VIP subscriber
on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

Success Rate = (1 - Number
of failed Extended Service
Req requests/Number of
requests) x 100%
Issue 03 (2015-07-30)
Extended
Service Req
Delay
[0,+)
ms

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Overlong
Extended
Service Req
Delays
[0,+)
Numbe
r

delay of the Extended
on the LTE network exceeds
a predefined exception
threshold.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

1190
Nastar
MME/Mobility/TAU
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra Combined
TAU Requests
[0,+)
Number

the Intra Combined
TAU procedure on the
LTE network.
PS 12.0/PS 12.1/
PS 13.0
The Intra Combined

TAU procedure
includes:
Intra USN Intra EUTRAN Combined
TAU
Combined TAU
Combined TAU
Intra Combined
TAU CS
Failures
[0,+)
Number

Intra Combined TAU
LTE network fails.
PS 12.0/PS 12.1/
PS 13.0
Intra Combined
TAU CS
Success Rate
[0.00,100.0
0]
Success rate of the Intra

Combined TAU
LTE network.
PS 12.0/PS 12.1/
PS 13.0
Intra Combined TAU

CS Success Rate = (1 Number of failed Intra
Combined TAU
requests/Number of
Intra Combined TAU
requests) x 100%
Intra Combined
TAU Delay
Issue 03 (2015-07-30)
[0,+)
ms

Intra Combined TAU
LTE network.

PS 12.0/PS 12.1/
PS 13.0
1191
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Intra
Combined TAU
Delays
[0,+)
Number

delay of the Intra
Combined TAU
threshold.
PS 12.0/PS 12.1/
PS 13.0
Inter Combined
TAU Requests
[0,+)
Number

the Inter Combined
LTE network.
PS 12.0/PS 12.1/
PS 13.0
The Inter Combined

TAU procedure
includes:
Inter USN Intra EUTRAN Combined
TAU
Inter USN GERAN/
UTRAN to E-UTRAN
Combined TAU
Inter Combined
TAU CS
Failures
[0,+)
Number

Inter Combined TAU
LTE network fails.
PS 12.0/PS 12.1/
PS 13.0
Inter Combined
TAU CS
Success Rate
[0.00,100.0
0]
Success rate of the Inter

Combined TAU
LTE network.
PS 12.0/PS 12.1/
PS 13.0
Inter Combined TAU

CS Success Rate = (1 Number of failed Inter
Combined TAU
requests/Number of
Inter Combined TAU
requests) x 100%
Issue 03 (2015-07-30)

1192
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter Combined
TAU Delay
[0,+)
ms

Inter Combined TAU
LTE network.
PS 12.0/PS 12.1/
PS 13.0
Overlong Inter
Combined TAU
Delays
[0,+)
Number

delay of the Inter
Combined TAU
threshold.
PS 12.0/PS 12.1/
PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
CSFB PS
Handover
Requests
[0,+)
Number

the CSFB PS Handover
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
The CSFB PS Handover

procedure includes:
UTRAN Iu mode Inter
RAT handover
UTRAN Iu mode Inter
RAT handover
CSFB PS
Handover
Failures
Issue 03 (2015-07-30)
[0,+)
Number

CSFB PS Handover
LTE network fails.

PS 11.0/PS 12.0/
PS 12.1/PS 13.0
1193
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CSFB PS
Handover
Success Rate
[0.00,100.0
0]
Success rate of the CSFB

PS Handover procedure
initiated by a VIP
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
CSFB PS Handover
Success Rate = (1 Number of failed CSFB
PS Handover requests/
Number of CSFB PS
Handover requests) x
100%
CSFB PS
Handover Delay
[0,+)
ms

CSFB PS Handover
LTE network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Overlong CSFB
PS Handover
Delays
[0,+)
Number

delay of the CSFB PS
Handover procedure
initiated by a VIP
network exceeds a
threshold.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Parameters for Viewing PS Core VIP Analysis - VoLTE Results

This section describes the parameters for querying PS Core VIP analysis VoLTE results. You
can refer to the description when querying PS Core VIP analysis VoLTE results.
Issue 03 (2015-07-30)

1194
Nastar
Common
Parameter
Range
Unit
Description
Supported
Solution
Version
Deep Analysis
N/A
N/A
When the
dimension is
Group, this
parameter is
used to switch
from the
analysis results
of a VIP group
to those of the
VIP subscribers
in this group.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
When the
dimension is
User, this
parameter is
used to switch
from the
analysis results
of counters to
those of the
calls.
Group Name
N/A
N/A
Name of a VIP
group.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
IMSI
N/A
N/A
IMSI
information of a
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Note: Only
when you have
the "User
Identity" right,
you can view the
IMSI
information.
Issue 03 (2015-07-30)

1195
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MSISDN
N/A
N/A
MSISDN
information of a
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Note: Only
when you have
the "User
Identity" right,
you can view the
MSISDN
information.
Issue 03 (2015-07-30)
User ID
N/A
N/A
ID of a VIP
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Alias
N/A
N/A
Alias of a VIP
subscriber. You
can obtain the
user name in the
VIP Group
Management
window based
on the IMSI of
the VIP
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
IMEI-TAC
N/A
N/A
International
mobile
equipment
identity-type
allocation code
(IMEI-TAC) of
the terminal
used by a VIP
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1196
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Terminal Model
N/A
N/A
Type of the
terminal used by
a VIP
subscriber. You
can obtain the
terminal type in
the Terminal
Type
Management
window based
on the IMEITAC of the
terminal used by
the VIP
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Total Reports
[0,+)
Number
Indicates the
number of
records
generated for all
service types
during the
network access
of a subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Service Type
N/A
N/A
Service type for

a following
counter.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Number of
Abnormal KPIs
[0,+)
Number
Number of
abnormal KPIs.
The abnormal
KPIs are
obtained by
comparing the
KPI values with
the exception
thresholds
which are
predefined by
engineers when
creating tasks.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1197
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Paging
Requests
[0,+)
Number
Number of
paging process
requests by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
The paging
process
includes:
Paging.
VoLTE Paging
Failures
[0,+)
Number
Number of
paging process
failures by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE Paging
Success Rate
[0.00,100.00]
Paging process
success rate by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Paging success
rate = (1 Number of
paging failures/
Number of
paging requests)
x 100%
VoLTE
Average Paging
Delay
Issue 03 (2015-07-30)
[0,+)
ms
Average delay
of a paging
process by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
1198
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Overlong
Paging Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of a
paging process
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Dedicated
Bearer Act
Requests
[0,+)
Number
Number of
dedicated bearer
act process
requests by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
The dedicated
bearer act
process
includes:
Dedicated
bearer
activation
VoLTE
Dedicated
Bearer Act
Failures
Issue 03 (2015-07-30)
[0,+)
Number
Number of
dedicated bearer
act process
failures by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
1199
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Dedicated
Bearer Act
Success Rate
[0.00,100.00]
Success rate of a
dedicated bearer
act process by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Dedicated
bearer act
success rate = (1
- Number of
dedicated bearer
act failures/
Number of
dedicated bearer
act requests) x
100%
Issue 03 (2015-07-30)
VoLTE
Average
Dedicated
Bearer Act
Delay
[0,+)
ms
Average delay
of a dedicated
bearer act
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE
Overlong
Dedicated
Bearer Act
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of a
dedicated bearer
act process by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1200
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE PDN
Connectivity
Requests
[0,+)
Number
Number of PDN
Connectivity
process requests
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
The PDN
Connectivity
process
includes:
UE requested
PDN
connectivity
Default bearer
activation in
attach
VoLTE PDN
Connectivity
Failures
[0,+)
Number
Number of PDN
connectivity
process failures
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE PDN
Connectivity
Success Rate
[0.00,100.00]
PDN
Connectivity
process success
rate by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
PDN
Connectivity
success rate = (1
- Number of
PDN
Connectivity
failures/
Number of PDN
Connectivity
requests) x
100%
Issue 03 (2015-07-30)

1201
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Average PDN
Connectivity
Delay
[0,+)
ms
Average delay
of a PDN
Connectivity
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE
Overlong PDN
Connectivity
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of a
PDN
Connectivity
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1202
Nastar
MME/Accessability/Bearer Mod
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update
Requests
[0,+)
Number
Number of PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update process
requests by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
PDN GW
Initiated Bearer
Mod with
Bearer QoS
Update
Requests
process
includes:
PDN GW
initiated bearer
modification
with bearer QoS
update
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update Failures
Issue 03 (2015-07-30)
[0,+)
Number
Number of PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update process
failures by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
1203
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update Success
Rate
[0.00,100.00]
Success rate of
an PDN GW
Initiated Bearer
Mod with
Bearer QoS
Update process
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
PDN GW
Initiated Bearer
Mod with
Bearer QoS
Update success
rate = (1 Number of
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update failures/
Number of
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update
requests) x
100%
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update Success
Delay
Issue 03 (2015-07-30)
[0,+)
ms
Average delay
of an VoLTE
PDN GW
Initiated Bearer
Mod with
Bearer QoS
Update process
by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
1204
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of an
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update process
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Intra EUTRAN

Handover
Requests
[0,+)
Number
Number of intra
E-UTRAN
handover
process requests
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Intra E-UTRAN
handover
processes
include:
X2 Handover
Intra MME S1
Handover
Inter MME S1
Handover
Issue 03 (2015-07-30)

1205
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Intra EUTRAN

Handover
Failures
[0,+)
Number
Number of intra
E-UTRAN
handover
process failures
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1206
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Intra EUTRAN

Handover
Success Rate
[0.00,100.00]
Success rate of
an intra EUTRAN
handover
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Intra E-UTRAN
handover
success rate = (1
- Number of
intra E-UTRAN
handover
failures/
Number of intra
E-UTRAN
handover
requests) x
100%
Issue 03 (2015-07-30)

1207
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
NOTE
The VoLTE
handover
success rate
contains the
LTE handover
success rate and
the IMS voice
bearer handover
success rate. If
the IMS voice
bearer exists
before the
VoLTE
handover but
disappears after
the handover,
the IMS voice
bearer handover
fails during the
VoLTE
handover. This
indicates a
VoLTE
handover
failure.
Therefore, in the
Nastar analysis
window of the
VoLTE
handover, if the
IMS voice
bearer is
interrupted, an
external cause
value is
displayed
indicating a
successful
handover.
However, the
displayed value
only indicates
"X2/Intra EUTRAN/Inter
MME S1/Intra
MME S1
Handover" and
the VoLTE IMS
handover fails.
Issue 03 (2015-07-30)

1208
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Average Intra EUTRAN
Handover Delay
[0,+)
ms
Average delay
of an intra EUTRAN
handover
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE
Overlong Intra
E-UTRAN
Handover
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of an
intra E-UTRAN
handover
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE SRVCC
(to GERAN)
Requests
[0,+)
Number
Number of
SRVCC(to
GERAN)
process requests
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
The SRVCC(to
GERAN)
Requests
process
includes:
SRVCC from EUTRAN to
GERAN or
UTRAN
Issue 03 (2015-07-30)

1209
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE SRVCC
(to GERAN)
Failures
[0,+)
Number
Number of
SRVCC(to
GERAN)
process failures
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE SRVCC
(to GERAN)
Success Rate
[0.00,100.00]
Success rate of
an SRVCC(to
GERAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SRVCC(to
GERAN)
success rate = (1
- Number of
VoLTE SRVCC
(to GERAN)
failures/
Number of
VoLTE SRVCC
(to GERAN)
requests) x
100%
Average
VoLTE SRVCC
(to GERAN)
Delay
Issue 03 (2015-07-30)
[0,+)
ms
Average delay
of an VoLTE
SRVCC(to
GERAN)
process by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
1210
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong
VoLTE SRVCC
(to GERAN)
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of an
VoLTE SRVCC
(to GERAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE SRVCC
(to UTRAN)
Requests
[0,+)
Number
Number of
SRVCC(to
UTRAN)
process requests
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SRVCC(to
UTRAN)
Requests
process
includes:
GERAN or
UTRAN
VoLTE SRVCC
(to UTRAN)
Failures
Issue 03 (2015-07-30)
[0,+)
Number
Number of
SRVCC(to
UTRAN)
process failures
by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
1211
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE SRVCC
(to UTRAN)
Success Rate
[0.00,100.00]
Success rate of
an SRVCC(to
UTRAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SRVCC(to
UTRAN)
success rate = (1
- Number of
VoLTE SRVCC
(to UTRAN)
failures/
Number of
VoLTE SRVCC
(to UTRAN)
requests) x
100%
Issue 03 (2015-07-30)
Average
VoLTE SRVCC
(to UTRAN)
Delay
[0,+)
ms
Average delay
of an VoLTE
SRVCC(to
UTRAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Overlong
SRVCC(to
UTRAN)
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of an
VoLTE SRVCC
(to UTRAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1212
Nastar
MME/Mobility/Voice retention/Dedicated Bearer Act

Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Dedicated
Bearer Act
Success
[0,+)
Number
Number of
times that
dedicated bearer
is successfully
created for a
VIP subscriber
on the LTE
network.
VoLTE
Dedicated
Bearer Act
Success process
includes:
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Dedicated
bearer
activation
MME/Mobility/Voice retention/eNB Init Call Drop

Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE eNB
Init Call Drop
Cnt
[0,+)
Number
VoLTE call
drop count of a
VIP subscriber
on the LTE
network.
Process
includes:
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
MME Initiated
Dedicated
Bearer
Deactivation
Issue 03 (2015-07-30)

1213
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE eNB
Init Call Drop
rate (%)
[0.00,100.00]
VoLTE call
drop rate of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Process
includes:MME
Initiated
Dedicated
Bearer
Deactivation
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Create
Session
Requests
[0,+)
Number
Number of
Create Session
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE Create
Session Failures
[0,+)
Number
Number of
Create Session
failures of a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1214
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Create
Session Success
Rate
[0.00,100.00]
Success rate of
the Create
Session
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Create Session
Success Rate =
(1 - Number of
Create Session
failures/
Number of
Create Session
requests) x
100%
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Create
Bearer Requests
[0,+)
Number
Number of
Create Bearer
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE Create
Bearer Failures
[0,+)
Number
Number of
Create Bearer
failures of a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1215
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Create
Bearer Success
Rate
[0.00,100.00]
Success rate of
the Create
Bearer
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Create Bearer
Success Rate =
(1 - Number of
Create Bearer
failures/
Number of
Create Bearer
requests) x
100%
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Update
Bearer Requests
[0,+)
Number
Number of
Update Bearer
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE Update
Bearer Failures
[0,+)
Number
Number of
Update Bearer
failures of a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1216
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Update
Bearer Success
Rate
[0.00,100.00]
Success rate of
the Update
Bearer
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Update Bearer
Success Rate =
(1 - Number of
Update Bearer
failures/
Number of
Update Bearer
requests) x
100%
4.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
l
Relationships between HSSs and eNodeBs have been configured. For detailed operations,
see 3.3.8 Configuring Relationships Between HSSs and eNodeBs (Optional).
When the MME license for basic functions has been applied, the MME vendor is Huawei,
and the LTE all-signaling function needs to be used, it is recommended to connect the USN
to the Nastar for checking the single-user trace information enabled on the MME.
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.
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.
Issue 03 (2015-07-30)

1217
Nastar
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

number of a VIP
subscriber is available on
the HSS
The User Level tab page is automatically displayed for you to

view the trace reference number (which is available on the HSS)
and all-signaling switch status of the VIP subscriber.
The trace reference

number of a VIP
subscriber is unavailable
on the HSS
The User Level tab page is automatically displayed. The Nastar

randomly assigns a trace reference number, which is unique in
the Nastar system, to the VIP subscriber.
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.
Check that the data switch is successfully turned on by viewing the displayed information in the
Log Info area.
----End

Context
l
Issue 03 (2015-07-30)
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
1218
Nastar
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.
4.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.
NOTE
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.
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.
Supports the combined complaint analysis support between the networks on the RAN side,
including GSM/UMTS, and LTE FDD/LTE TDD.
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 4-32.
Issue 03 (2015-07-30)

1219
Nastar
Table 4-32 Function description of complaint analysis support
Issue 03 (2015-07-30)
Function Type
Description
Supported
Network
Aggregation and
analysis of cause
types in call reports
of complaining
subscribers
Helps network engineers filter and aggregate call

reports based on exception causes.
GSM/
UMTS/
LTE/PS
Core
Summary and
analysis of call
reports of
complaining
subscribers
Provide an information overview about all the filtered

call records. The information includes the information,
such as access time, access cell, release time, release
cell, and service duration. This function helps network
engineers quickly identify abnormal call records (for
example, too-short-time call records) and preliminarily
learn the situation of complaining subscribers.
GSM/
UMTS/
LTE/PS
Core
Analysis of detailed
call reports of
complaining
subscribers
Provides the detailed information about all the filtered

call records. The information includes the subscriber
information, call access information, call release
information, and handover information. This function
helps network engineers learn the key events that occur
during calls, service usage, and measurement reports
(MRs) before signaling release, accurately and quickly
assisting in problem location.
GSM/
UMTS/
LTE/PS
Core
Analysis of
procedure before
signaling release in
call reports of
complaining
subscribers
Provides the detailed procedure before signaling

release of all the filtered subscribers. This function
helps network engineers locate problems based on the
information before signaling release.
GSM/
UMTS/LTE
Analysis of
measurement
reports (MRs) on
calls of complaint
subscribers before
call release
Provides MR details and trend charts of measurement

counters, including TA, DLRxLevel, DLRxQuality/
Level, ULRxQuality/Level, MS/BTS Power, and VQI.
The VQI indicates the voice quality during services and
helps network engineers more accurately locate voice
quality problems.
GSM
Provides information about the serving cells of

subscribers before call release and the neighboring
cells. This helps engineers analyze and locate
problems.
UMTS/LTE
Mobility analysis
Provides handover information of a terminal and helps

network engineers to learn all cells that are recorded in
abnormal call records.
GSM/
UMTS/LTE
Service analysis
Analyzes RAB-related counters and provides network

quality information about a service.
UMTS/LTE

1220
Nastar
Function Type
Description
Supported
Network
Analysis results
displayed through
geographic
observation
Geographically displays the cells to which

complaining subscribers have gained access and the
cells from which complaining subscribers have been
released.
GSM/
UMTS/LTE
Principles of Complaint Analysis Support

This section describes the data source and the function principles of the complaint analysis
support.
Data Source
The Nastar uses the CHR data for the complaint analysis support 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.
Function Principles of complaint analysis support based on CHR data only, see Function
Principles (Common). Function Principles of PS Core complaint analysis support based on
UGW internal xDR data, seeFunction Principles(PS only - Base on UGW ).Function
Principles of LTE(signaling plane) and PS Core(user plane) combined complaint analysis
support based on UGW internal xDR data, seeFunction Principles(RAN + PS - Base on
UGW ).
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
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
NOTE
scheme.
Issue 03 (2015-07-30)

1221
Nastar
Table 4-33 Description of complaint analysis support
Issue 03 (2015-07-30)
User
Operation
Proce
dure
Sour
ce
Desti
nation
Purpose
1.
Subscr
ibe to
basic
data
Issue a
basic
data
subscri
ption
comma
nd
Nasta
r
Serve
r
eSAU
To turn on the data source switch on the NE

side. After a user enables the basic data
subscription function (GSM complaint
analysis support or UMTS complaint analysis
support) on the Nastar client, the Nastar issues
a basic data subscription command to the
eSAU.
Issue
an
MML
comma
nd
eSA
U
U2000
/
M2000
To issue an MML command to the U2000/

M2000.
Forwar
d the
MML
comma
nd
U200
0/
M20
00
BSC/
RNC
To forward the MML command to the NE

through the U2000/M2000, requesting the NE
to generate raw data.
GSM
/
UM
TS
netw
ork

1222
Nastar
User
Operation
PS
Core
netw
ork
LTE
netw
ork
Issue 03 (2015-07-30)
Proce
dure
Sour
ce
Desti
nation
Purpose
Upload
raw
data
BSC/
RNC
SAU
Issue a
basic
data
subscri
ption
comma
nd
Nasta
r
Serve
r
eSAU

subscription function (PS Core complaint
analysis support) on the Nastar client, the
Nastar issues a basic data subscription
Issue
an
MML
comma
nd
eSA
U
U2000
/
M2000

M2000.
Forwar
d the
MML
comma
nd
U200
0/
M20
00
SGSN/
MME
To forward the MML command to the NE,

requesting the NE to generate raw data.
Upload
raw
data
SGS
N/
MM
E/
GGS
N/
SAEGW
PS
SAU
Issue a
basic
data
subscri
ption
comma
nd
Nasta
r
Serve
r
eSAU

subscription function (LTE complaint analysis
eSAU.
Issue a
subscri
ption
comma
nd
eSA
U
U2000
/
M2000
To issue a subscription command to the

U2000/M2000.
NOTE
The generation and transmission of the GGSN/
SAE-GW CHR data is not triggered by the Nastar
subscription command. The GGSN/SAE-GW CHR
data will be uploaded to the PS SAU through
Huawei internal protocols in real time after the CHR
data switch is enabled.

1223
Nastar
User
Operation
Proce
dure
Sour
ce
Desti
nation
Purpose
Forwar
d the
subscri
ption
comma
nd
U200
0/
M20
00
eNode
B
To forward the subscription command to the

NE, requesting the NE to generate raw data.
Upload
raw
data
eNod
eB/
MM
E
Trace
Server/
LTE
SAU
l To collect the data from Trace Server after

uploading the raw data (eNodeB CHR)
l To upload the raw data (MME CHR) from
the MME to the LTE SAU directly.
NOTE
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.
Create
and
execut
e an
analys
is task
3.
View
analys
is
results
Deliver
a dataprepro
cessing
task
(direct)
Nasta
r
Serve
r
SAU/
LTE
SAU/
PS
SAU

SAU/LTE SAU/PS SAU through the eSAU,
requesting the SAU/LTE SAU/PS SAU to start
the data-preprocessing task.
Upload
prepro
cessed
data
(direct)
SAU/
LTE
SAU/
PS
SAU
eSAU
Upload
data
analysi
s
results
eSA
U
Nastar
Server
To aggregate the data reported by SAU/LTE

SAU/PS SAU, generate data analysis results,
and upload the data analysis results to the
Nastar server.
Displa
y
analysi
s
results
Nastar
Server
Function Principles(PS only - Base on UGW )

The data sources of PS Core complaint analysis support based on user plane data on UGW
include PS CHR data and UGW xDR data.Figure 4-50 shows the working principles for
Issue 03 (2015-07-30)

1224
Nastar
collecting, importing, and analyzing data on the Nastar. Table 4-34 describes details about the
working principles.
Table 4-34 Description of complaint analysis support(UGW)

User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Function
1.
Prepare
for
analysi
s.
Commis
sion the
PS SAU
and the
UGW
manuall
y.
User
PS
SAU
/
UG
W
To enable the PS SAU to collect data from UGW. For

detailed operations, see Activating the Service
Reporting Function (GGSN/SAE-GW).
Upload
data
collecte
d over
the
UGW.
UG
W
PS
SAU
To enable the UGW to upload the UGW xDR data to

the PS SAU.
Issue
basic
subscrip
tion
comma
nds.
Nast
ar
Serv
er
eSA
U

this function is enabled on the Nastar client, the Nastar
issues a subscription command to the eSAU.
2.
Subscri
be to
basic
data.
Issue 03 (2015-07-30)

1225
Nastar
User
Operat
ion
3.
Create
and
execute
analysi
s tasks.
4. View
analysi
s
results.
Proced
ure
Sou
rce
Dest
inati
on
Function
Issue
subscrip
tion
comma
nds.
eSA
U
U20
00/
M20
00
To issue subscription commands to the U2000/M2000

based on the subscription requirements.
Forward
subscrip
tion
comma
nds.
U20
00/
M20
00
MM
E/
SGS
N
To issue subscription commands to NEs through the

U2000/M2000 requesting the NEs to generate raw data.
Upload
raw
data.
MM
E/
SGS
N
PS
SAU
To upload the CHRs from the MME/SGSN to the PS

SAU.
Deliver
data preprocessi
ng tasks.
eSA
U
PS
SAU
To enable the eSAU to deliver the data processing

request to the PS SAU, requesting the PS SAU to start
a data pre-processing task.
Upload
complai
nt data.
PS
SAU
eSA
U
To enable the PS SAU to pre-process the CHRs reported

by the MME/SGSN, and xDRs uploaded over the
UGW. After the data pre-processing task is complete,
the PS SAU uploads the pre-processed data to the
eSAU.
Upload
complai
nt data.
eSA
U
Nast
ar
Serv
er
To enable the eSAU to uploads the complaint data to

Nastar server, and Nastar server aggregates the preprocessed data and generate analysis results.
Display
analysis
results.
Nast
ar
Serv
er
To enable the Nastar server to display analysis results

Function Principles(RAN + PS - Base on UGW )

The data sources of LTE FDD/TDD and PS Core combined complaint analysis support based
on user plane data on UGW include LTE CHR data and UGW xDR data.NFigure 4-51shows
the working principles for collecting, importing, and analyzing data on the Nastar.Table 4-35
describes details about the working principles.
Issue 03 (2015-07-30)

1226
Nastar
Table 4-35 Description of complaint combined analysis support

User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Function
1.
Prepare
for
analysi
s.
Commis
sion the
PS SAU
and the
UGW
manuall
y.
User
PS
SAU
/
UG
W

Upload
data
collecte
d over
the
UGW.
UG
W
PS
SAU

the PS SAU.
Issue a
basic
data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U

a user enables the basic data subscription function (LTE
complaint analysis support) on the Nastar client, the
Nastar issues a basic data subscription command to the
eSAU.
2.
Subscri
be to
basic
data.
Issue 03 (2015-07-30)

1227
Nastar
User
Operat
ion
3.
Create
and
execute
analysi
s tasks.
4. View
analysi
s
results.
Issue 03 (2015-07-30)
Proced
ure
Sou
rce
Dest
inati
on
Function
Issue a
subscrip
tion
comma
nd
eSA
U
U20
00/
M20
00
To issue a subscription command to the U2000/

M2000.
Forward
the
subscrip
tion
comma
nd
U20
00/
M20
00
eNod
eB
To forward the subscription command to the NE,

Upload
raw data
eNo
deB/
MM
E
Trac
e
Serv
er/
LTE
SAU

uploading the raw data (eNodeB CHR) from the
eNodeB to the Trace Server.
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
Deliver
data preprocessi
ng tasks.
eSA
U
PS
SAU
/LTE
SAU

request to the PS SAU/LTE SAU, requesting the PS
SAU/LTE SAU to start a data pre-processing task.
Upload
complai
nt data.
PS
SAU
/
LTE
SAU
eSA
U
To enable the PS SAU/LTE SAU uploads the preprocessed data to the eSAU.
Upload
complai
nt data.
eSA
U
Nast
ar
Serv
er

Display
analysis
results.
Nast
ar
Serv
er


1228
Nastar
Technical Specifications for Complaint Analysis Support

of analysis time.
NOTE
Item
Execution type
One-time task

analysis task
Maximum management capacity of the Nastar (A maximum

of six NEs are supported in USN+UGW joint analysis.)
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.
task
l 2,000 complaining subscribers (for all networks when

IMSIs are used for analysis.)
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
analysis tasks
500 (for all RATs)

one analysis task
Last 7 days

task
GSM/UMTS/LTE/PS Core: 210 minutes

l GSM: 7 days
l UMTS: 7 days
l LTE: 7 days
l PS Core: 30 days
The preceding specifications are the default duration for storing
analysis data when the default traffic model is used. The actual
duration varies depending on the traffic model and storage space.

l GSM: 7 days
l UMTS: 7 days
l LTE: 7 days
l PS Core: 30 days
Issue 03 (2015-07-30)

1229
Nastar
4.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

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 4-36.
Issue 03 (2015-07-30)

1230
Nastar
Table 4-36 Required license and rights of complaint analysis support

Funct
ion
Required license

Management > User)
Data
subscr
iption
manag
ement
l GSM/UMTS/LTE FDD/LTE
TDD/PS Core basic function
license

Authentication
NOTE
l When the number of cells
controlled by the LTE basic
license and the number of
online users reach the upper
limits, the Alarm dialog box is
displayed, prompting you to
upgrade the license. When you
query the license consumption
in the license Information, the
result is not consistent with that
displayed in the Alarm dialog
box because the exceeded
number has not been reported.
The data displayed in the
Alarm dialog box is correct.
You are advised to upgrade the
license in a timely manner.

NE Object Authentication > *** NE
Operation Rights. *** refers the NEs to
be subscribed.
Subject Management > *** Complaint
Analysis Support Operation Rights.
*** refers the RAT.
l LTE Periodic MR Period

Setting is only available to an
account in the Administrators
group or a user with data
subscription management
permission.
TDD/PS Core complaint
analysis support license
NOTE
l You need to obtain the licenses for
basic functions and complaint
analysis support related only to the
desired RATs instead of all RATs.
l The license for the basic functions
related to an RAT is the basis for
all functions related to this RAT,
which means the functions related
to an RAT depends on the
availability of the license for the
basic functions related to this RAT.
Issue 03 (2015-07-30)

1231
Nastar
Funct
ion
Required license

Management > User)
GSM
compl
aint
analys
is
suppor
t
l GSM basic function license

Operation Rights >
Operation > Nastar
Subject Management >
GSM Complaint Analysis
Support Operation
Rights
l GSM complaint analysis

support license
l Operation rights of NEs to

be analyzed
Assign Operation Rights
of Objects > NE Object
Authentication > *** NE
Operation Rights ***
refers the NEs to be
analyzed.
UMT
S
compl
aint
analys
is
suppor
t
Issue 03 (2015-07-30)
l UMTS basic function license

l UMTS complaint analysis
support license

Operation Rights >
Operation > Nastar
UMTS Complaint
Analysis Support
Operation Rights
be analyzed
analyzed.

NOTICE
If the
analyzed
IMSI or
MSISDN
of
complaini
ng user is
the same as
the VIP
user in the
VIP group
manageme
nt
function,
and you
has not the
operation
rights to
operate the
VIP user,
you are not
allowed to
create the
complaint
analysis
support
task about
the IMSI
or
MSISDN.
1232
Nastar
Funct
ion
Required license

Management > User)
LTE
TDD
compl
aint
analys
is
suppor
t
l LTE TDD basic function license

Operation Rights >
Operation > Nastar
LTE TDD Complaint
Analysis Support
Operation Rights
NOTE

be analyzed
analyzed.

permission.
l LTE TDD complaint analysis

support license
l (Optional) LTE TDD CSFB
analysis license, only for
controlling the display of the
CSFB counters.
l (Optional) LTE TDD VoLTE
VoLTE counters.
Issue 03 (2015-07-30)

1233
Nastar
Funct
ion
Required license

Management > User)
LTE
FDD
compl
aint
analys
is
suppor
t
l LTE FDD basic function license

Operation Rights >
Operation > Nastar
LTE FDD Complaint
Analysis Support
Operation Rights
NOTE

be analyzed
analyzed.

permission.
l LTE FDD complaint analysis

support license
l (Optional) LTE FDD CSFB
CSFB counters.
l (Optional) LTE FDD VoLTE
VoLTE counters.
Issue 03 (2015-07-30)

1234
Nastar
Funct
ion
Required license

Management > User)
PS
Core
compl
aint
analys
is
suppor
t
l PS Core basic function license

Operation Rights >
Operation > Nastar
PS Core Complaint
Analysis Support
Operation Rights
l PS Core complaint analysis

support license
l (Optional) SGSN/MME VoLTE
signaling analysis license
l (Optional) GGSN/SAE-GW
VoLTE signaling analysis
license
l (Optional) SGSN/MME CSFB
CSFB counters.
l (Optional) Data Access-Gn
License and GGSN/SAE-GW
Data Service User Plane
Complaint Analysis Support
License, for controlling the
availability of the analysis
function based on PS Core user
plane data obtained from the
UGW.
Issue 03 (2015-07-30)

be analyzed
analyzed.

1235
Nastar
Funct
ion
Required license

Management > User)
l GS
M/
U
M
TS
co
mb
ine
d
co
mp
lai
nt
ana
lys
is
sup
por
t
TDD/PS Core basic analysis
support license

Have both involved
licenses of Complaint
Analysis Support
Operation Rights of
combined analysis.
be analyzed is the same as
the rights of complaint
analysis support of each
network.
l LT
E
FD
D/
LT
E
TD
D
co
mb
ine
d
co
mp
lai
nt
ana
lys
is
sup
por
t
l RA
N
sid
e
(G
S
Issue 03 (2015-07-30)

1236
Nastar
Funct
ion
M/
U
M
TS
/
LT
E
FD
D/
LT
E
TD
D)
an
d
PS
Co
re
co
mb
ine
d
co
mp
lai
nt
ana
lys
is
sup
por
t
Issue 03 (2015-07-30)
Required license

Management > User)
NOTE
permission.

support license, and UMTS
complaint analysis support
license
support license, and LTE TDD
license
l Complaint analysis support
license of analyzed network on
the RAN side, and PS Core
license

1237
Nastar
Funct
ion
Required license

Management > User)
Comm
on
To control the User Identity right, otherwise,

you can not view the integrated IMSI
information.
Function operation rights: Operation
Rights > Select > Nastar Application >
Operation > Nastar Security Information
Management > User Identity
Operation Rights > Select > Operation >
Nastar System Task Management >
Viewing Rights of Data Maintenance and
Management: to control the viewing rights
of the Complaint Analysis page during task
creation.

task successfully.
Issue 03 (2015-07-30)

1238
Nastar
Table 4-37 Required basic data of complaint analysis support

Data
Type
Function
Operation
Configur
ation
Data
(Mandato
ry)

the NE corresponding to
a complaint location
allows users to correctly
obtain the data of
complaining subscribers
from the network and
analyze the cell
information in MRs and
the information about the
following cells: cells to
gained access, cells
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 3.4.2
Checking the Integrity of Configuration Data.
NOTE
If you only perform the PS
Core complaint analysis
support, you do not need
Issue 03 (2015-07-30)

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.

1239
Nastar
Data
Type
Function
Operation
Complain
ing
Subscribe
r
Informati
on
(Mandato
ry)
l Time
The Nastar only
analyzes complaints
that occurred in the
latest seven days.
Enter the complaining subscriber information when

creating complaint analysis support.
l Place
The NE information
that the problem
occurs, including one
or multiple NEs. The
Nastar can analyze
complaints that occur
on the whole network
(The network can
involve multiple
OSSs). It does not
require the precise
information about the
complaining place.
However, it is
recommended that
you locate the
complaining place to
the base station
controller level or cell
level to ensure
performance of the
complaint analysis
support function.
l IMSI, STMSI,
MSISDN, or peer
MSISDN
IMSI: Supported
by every network.
NOTE
If telecom operators have high requirements for
subscriber information security and the anonymization
policy is enabled on the network where the Nastar is
deployed, all subscriber information such as IMSI,
MSISDN, and IMEI contained in the analysis data will be
encrypted. To protect the security-sensitive subscriber
information, 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 Software Center > Tool > Mini-tool
Software > Core Network Product Line > WirelessOSS > iManager M2000-II > HMACUtil to obtain the
anonymization switch or the encryption key is changed.
If the subscriber identity anonymization switch or the
encryption key is changed, see 3.12.3 Troubleshooting
Problems Caused by Change of the Subscriber
Identity Anonymization Switch or the Encryption
Key.
If the number of complaining subscribers to be

analyzed is large, you can save the IMSI,
STMSI,MSISDN or peer MSISDN information in
the files in .xls/.xlsx/.csv format.
NOTE
The IMSI or MSISDN information stores a maximum of
2,000 records. Each IMSI must contain 15 digits. The peer
MSISDN information stores a maximum of 200 records.
STMSI:
Supported only
when the LTE is
not interconnected
to the EPC.
MSISDN: Only
supported by the
PS Core network.
Peer MSISDN:
Only supported by
the GSM network
Issue 03 (2015-07-30)

1240
Nastar
Data
Type
Function
Operation
when choosing the

CS service.
You can obtain
either the above
information of a
complaining
subscriber for
analysis when
supporting multi
information.
Engineeri
ng
Paramete
rs
(Optional
)
The engineering
of the analysis result. You
do not need to prepare the
engineering parameters if
the geographic display of
the analysis result is not
required.

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
supported by the Nastar, see Appendix:
Engineering Parameter Templates.
parameters is not consistent with the configuration
data, the TOP cell will be repeated in the network
geographic observation function.
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.

Internet, you can view analysis results on the
Google Earth. For details, see 3.4.4 Preparing the
Map File (Optional).

Before analyzing, check that the used NE versions and U2000/M2000 versions are consistent
with those described in Table 4-38.
Issue 03 (2015-07-30)

1241
Nastar

Net
wor
k
Description
GSM

(or later).
(or later).
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
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.
UM
TS

(or later).
Issue 03 (2015-07-30)

1242
Nastar
Net
wor
k
Description
LTE
NOTE
(RH2288).
Issue 03 (2015-07-30)

1243
Nastar
Net
wor
k
Description
PS
Core
NE version:
V900R013C00
4.10.3 Process of Complaint Analysis Support

This section describes the process of complaint analysis support and the steps of each procedure.
l
Prerequisites
Procedure
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 4.10.2 Preparations for Complaint
Analysis Support.
Procedure
Figure 4-52 shows the process of complaint analysis support. For details, see Table 4-39.
Issue 03 (2015-07-30)

1244
Nastar
Figure 4-52 Flowchart for complaint analysis support
Table 4-39 Description of complaint analysis support procedures

No.
Proced
ure
Description
Reference for
Detailed
Operations
(1)
LTE
Periodic
MR
Period
Setting
NOTE
For details about

parameters, see LTE
Periodic MR Period
Setting Parameters
l For LTE analysis themes, you must set this

parameter before basic subscription. Otherwise, the
Nastar uses the current value of this parameter to
perform basic subscription.
l For an LTE network, this function is available only
to an account in the Administrators group or users
with data subscription management permission.

Procedure:
1. In the LTE Periodic MR Period Setting
window, set Periodic MR Period, Number
of Sampled Users and Number of Times
MRs Are Reported.
2. Click Configure.
Issue 03 (2015-07-30)

1245
Nastar
No.
Proced
ure
Description
Reference for
Detailed
Operations
Subscrib
e to
analysis
data
(basic)
NOTE
The basic data subscription function has high security
administrator who is authorized to subscribe to basic
data to turn on the data switch.
3.5 Subscribing to
Analysis Data

Procedure:
window, click *** tab.
*** indicates the network.
configured.
click Configure.
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
(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 03 (2015-07-30)

1246
Nastar
No.
Proced
ure
Description
Reference 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 4.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 03 (2015-07-30)

1247
Nastar
No.
Proced
ure
Description
Reference for
Detailed
Operations
(2)
Create a
complai
nt
analysis
support
task

User Assurance > Complaint Analysis
Support in the navigation tree of the Analysis
Task Management window.
l For details, see

3.7 Creating an
Analysis Task.
Procedure:
1. Double-click the Complaint Analysis
Support node.
Next.
l For details about

the parameters,
see Analysis
Task
Parameters.
3. On the Set Analysis Type tab page, set a net

type and a data type.
4. On the Select NE(s) tab page, click Select to
select the NEs located in an area where
subscribers complained about.
5. On the Select Complaining User tab page,
click Add or Import to set the IMSI
information (user alias, IMSI, and remark),
MSISDN, or peer MSISDN of the
complaining subscriber.
l IMSI: Supported by every network.
l STMSI: Supported only when the LTE is
not interconnected to the EPC.
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
period.
NOTE
To obtain accurate subscriber information, you are
advised to set Execute on to 1 hour.
8. Click Finish.
Issue 03 (2015-07-30)

1248
Nastar
No.
Proced
ure
Description
Reference for
Detailed
Operations
(3)
View
complai
nt
analysis
support
results

record of the task.
l For details, see

3.8 Querying
Analysis
Results.
Procedure:
2. In the displayed Complaint Analysis
Support window, view the complaint analysis
support results
(4)
Export
complai
nt
analysis
support
reports

the upper left part of each analysis results
window.
Procedure:
2. Specify the export path and export format.
3. Click Save.
l For details on the

interface
description, see
4.10.4 Reference
for Complaint
Analysis
Support
Interface.
l For details, see
3.10 Exporting
Analysis
Reports.
interface
description, see
4.10.4 Reference
for Complaint
Analysis
Support
Interface.
Issue 03 (2015-07-30)
Parameter
Description
Periodic MR
Period

1249
Nastar
Parameter
Description
Number of
Sampled Users

Nastar.
NOTE
Number of
Times MRs
Are Reported


Basic Subscription
Issue 03 (2015-07-30)

1250
Nastar
RA
T
Parameter
Description
GS
M
Complaint
Analysis
Support
Data (CHRCS)

You can click

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.
documentation. You can select all or none of the types or retain the
existing settings.
documentation. You can set this parameter to a value ranging from
0 to 6 or retain the existing settings.
NOTE
Issue 03 (2015-07-30)

1251
Nastar
RA
T
Parameter
Description
Complaint
Analysis
Support
Data (CHRPS)

You can click
documentation.
documentation.
Services: For details, see the SET GPSCHRCTRL command in
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 UL PDU Receiving Delay Threshold: For details, see the
SET GPSCHRCTRL command in the related NE product
documentation.
Complaint
Analysis
Support
Data (MRCS)
Switch for enabling or disabling the reporting of CS MR data. You can

You can click
l Collection Switch: For details, see the SET GMRCTRL command

l Original Sampling Rate: For details, see the SET GMRCTRL
l Preprocessed Sampling Rate: For details, see the SET
Issue 03 (2015-07-30)

1252
Nastar
RA
T
Parameter
Description
UM
TS
Complaint
Analysis
Support
Data (CHR)
Switch for enabling or disabling the reporting of CHR data. You can
You can click

l Error: specifies that all CHR data containing normal and abnormal
service procedures is reported. This parameter is unavailable.
existing settings.
existing settings.
Issue 03 (2015-07-30)

1253
Nastar
RA
T
Parameter
Description
LTE
FD
D/
LTE
TD
D
Complaint
Analysis
Support
Data (CHR)

You can click
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_MR_MDT, periodic intra-frequency
MDT measurement
measurement
PERIOD LOGGED MDT MEASUREMENT, log-type MDT
measurement
measurement
measurement
measurement
CSFB PREP, CSFB
Issue 03 (2015-07-30)

1254
Nastar
RA
T
Parameter
Description
PRIVATE L2 UE Context Release, L2 UE context release
If PERIOD LOGGED MDT MEASUREMENT is contained in
Trace Event Block Type, click Select Idle State Measurement
Object at the lower left corner to select the idle object to be
measured. The range of selected objects is displayed in the Idle
State Measurement Object Range column on the 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
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.
600(s), 1200(s), 2400(s), 3600(s), 5400(s), or 7200(s). The
Idle State Measurement Object Range: Specify the range of
idle objects to be measured. A maximum of 32 cells or eight
TACs can be selected.
NOTE
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.
Issue 03 (2015-07-30)

1255
Nastar
RA
T
Parameter
Description
PS
Core
Complaint
Analysis
Support
Data
(SGSN/
MMECHR)


Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

Parameter
Description
Set
Analysi
s Type
Analysis
Scene

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.
Issue 03 (2015-07-30)

1256
Nastar
Parameter
Description
Access
Network Type
Set the RAT for an NE. The system supports the following RATs:
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, GSM/LTE, UMTS/LTE,
GSM/UMTS/LTE.
Data Type 1

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.
NOTE
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 03 (2015-07-30)

1257
Nastar
Parameter
Description
PS Core SDR
Type
The following options are available if you select PS Core when

creating a complaint analysis support task.
l Signaling-Plane CHR Type:
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.
Normal process: Only the call records about normal
normal services are displayed.
Normal process: Only the traffic call records are reported
and only the traffic analysis results are displayed.
l Data Type: Data user plane. Data Access-Gn license is
needed for use this function.
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
NE(s)
Issue 03 (2015-07-30)
RAN NE
Click Select to select an NE. The lowest level is the base station
controller level.

1258
Nastar
Parameter
Description
Select
Compla
ining
User
Add or import the user alias, the IMSIs, and remarks of

complaining users.
IMSI
NOTE
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 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.
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 complaining subscriber is the same as the VIP
subscriber in the VIP group management function, and you has not the
operation rights to operate the VIP subscriber, you are not allowed to
create the complaint analysis support task about the IMSI.
Issue 03 (2015-07-30)

1259
Nastar
Parameter
Description
STMSI
NOTE
STMSI is
displayed only
when the EPC
is not
interconnecte
d on LTE
network.
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.

l Only numbers are allowed.
STMSI value range:
Value range: a 10-digit alphanumeric string composed of 0-9, 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 complaining subscriber is the same as the VIP
create the complaint analysis support task about the MSISDN.
Issue 03 (2015-07-30)

1260
Nastar
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.
through 9).
the Nastar is deployed, the Nastar does not support analyzing
using the MSISDN.
NOTICE
If the input peer MSISDN of complaining subscriber is the same as the
VIP subscriber in the VIP group management function, and you has not
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
Thresh
old
Network
Indicates the RAT of an NE.
Domain
Indicates the domain of an NE. Domains include signaling planeCS, signaling plane-PS, signaling plane-integration.
Service/Flow
Type
l When only the RAN data is analyzed, this row displays the
service type of the KPIs, such as NET, Call, and so on.
l When only the PS Core data is analyzed, this row displays 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, this
row displays the service type or flow type of the KPIs.
Indicator
Name
Indicates the name of a KPI.
Operator
Indicates the relationship between the KPI value and KPI

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 value. This
parameter can be empty. That is, no threshold value is provided.
Issue 03 (2015-07-30)

1261
Nastar

Parameter
Description
Duration
4.10.4 Reference for Complaint Analysis Support Interface

This section describes the interface for complaint analysis support. Before performing relevant
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.
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 4-53.
Issue 03 (2015-07-30)

1262
Nastar
Figure 4-53 Complaint analysis support interface
Issue 03 (2015-07-30)

1263
Nastar
No.
Parame Description
ter
Button
area
Provides entries to three functions:

l
: Displays the complaint analysis support results geographically.

For details, see Map Interface.
: 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.
: 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, rightclick 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
l After clicking the export button, a dialog box that provides personal data disclaimer
will be displayed, reminding you of the illegality if you possess personal data. Click
OK and export data.
l If you have the "User Identity" right, the IMSI column is added to the analysis result
page.
Issue 03 (2015-07-30)

1264
Nastar
No.
Parame Description
ter
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
l Lower part: Select the display mode in the drop-down combo box after
type
Tree aggregation for the navigation tree.
overvie
In Cause type-User ID: Alias mode, all filtered call records are
w of
classified by cause type and the call records of each cause type are
complai
then classified by User ID: Alias.
nt
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 03 (2015-07-30)

1265
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers
The table contains the overview information of the filtered call reports. The
information includes the information such as access time, access cell, release
time, release cell, service duration, and call status.
Each row indicates one call record.
l
l
: Indicates that the call record in the row is abnormal.

: 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.
: Indicates that the service detail record is a combined one.
The Nastar supports combining inter-BSC call history records. If an interBSC 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.
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.
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
page.
Issue 03 (2015-07-30)

1266
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers
Displays detailed information about the selected subscriber in area 2,

including user information, call access information, call release information.
For details about parameters, see 4.10.5 Reference for Complaint Analysis
Support Parameters (GSM).
When the window is opened initially, the area hidden by default.
Description of Signaling Procedure Before Call Release Tab Page

Figure 4-54 shows the signaling process before call release. The table describes the signaling
process.
Figure 4-54 Signaling process before call release tab page
Issue 03 (2015-07-30)

1267
Nastar
No.
Parameter
Description
(1)
Signaling
information
table
Lists all the interactive signaling information between NEs in the call
process, including the time, direction, type, and content. The chart
displays the corresponding information when you select the
information in the table.
NOTE
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.
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
flowchart
The flowchart shows the interactions between signaling of NEs

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).
NOTE
When you double-click the time of a signaling record, the time is displayed
as 00:00:00. Double-click it again so that it can be displayed correctly.
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 03 (2015-07-30)

1268
Nastar
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 4-55 shows the measurement information before call release.

Figure 4-55 Measurement information before call release tab page
No.
Parameter
Description
(1)
Detailed MR
information
table
Lists detailed MR information before call release. The information

includes time, measurement object type, and detailed counter
information.
Issue 03 (2015-07-30)

1269
Nastar
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 4-40 describes the change trend of each measurement
counters.
Table 4-40 Description of measurement counter change trend chart

Counter
Statistic Indication
Description
TA
Helps identify abnormal releases

caused by poor coverage.
Displayed as a bar chart. The value

ranges from 0 to 63.
DLRxLevel
DLRxQuality
/Level
Displayed as a broken line graph. The

value ranges from -47 to -110.
caused by uplink or downlink
interference.
ULRxQuality
/Level
Issue 03 (2015-07-30)
RxQuality: displayed as a bar chart.

The value ranges from 0 to 7.
RxLevel: displayed as a broken line
graph. The value ranges from -47 to
-110.
-110
MS/BTS
Power

caused by unbalanced uplink and
downlink by analyzing this KPI with
DLRxQuality/Level and
ULRxQuality/Level.
BTS Power: displayed as a bar chart.

The value ranges from 0 to 15. MS
Power: displayed as a broken line
graph. The value ranges from 0 to 30.
VQI
Displays voice quality changes in the

process, help evaluate the quality
accurately.
UL VQI: displayed as a bar chart.

The value ranges from 0 to 50. DL
VQI: displayed as a broken line

1270
Nastar
Description of Mobility Analysis Tab Page

Figure 4-56 shows handover information of the terminal through the mobility analysis.
Figure 4-56 Mobility analysis tab page
For details about parameters, see 4.10.5 Reference for Complaint Analysis Support
Parameters (GSM).
Map Interface
Click
Figure 4-57.
Figure 4-57 Map interface
Issue 03 (2015-07-30)
No.
Feature
Description
(1)
Button area
Entry for basic operations in the map window. For details about the
icons, see 3.2.3 Interface Description: Geographic Observation
Results.

1271
Nastar
No.
Feature
Description
(2)
Navigation
tree in the
map window
NOTE
l Complaint Analysis Support: Node for the complaint analysis

support theme.
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
observation
area
(4)
Grid detail
area
This area is empty for complaint analysis support.
(5)
Legend area

click the
area displays the legend information about the legends in area 3.
(6)
Information
area

l If the engineering parameters of a cell is not imported, the
Interface Description: UMTS Complaint Analysis Support

This section describes the interface for UMTS complaint analysis support. Before performing
Opening the Window

You can enter UMTS complaint analysis support interface in two modes:
l
Issue 03 (2015-07-30)
Select an executed UMTS complaint analysis support task, and double-click an analysis
1272
Nastar
Main Window
NOTE
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.
Issue 03 (2015-07-30)

1273
Nastar
No.
Parame Description
ter
Button
area
Provides entries to four functions:

l
: displays the complaint analysis support results geographically.

For details, see Description of Mobility Analysis Tab Page.

type.file format.
format.
: exports data reports.

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.
reports.
provides the abnormal cause statistics function of the service. For

details, see Common Statistics Interface.
NOTE
OK and export data.
page.
Issue 03 (2015-07-30)

1274
Nastar
No.
Parame Description
ter
w tree of
NOTE
the call
If users select only a service type node (such as NET, CS domain, and PS domain),
the Nastar filters only the abnormal or normal CHRs of the selected service type.
report
cause
l Middle part: Call records of multiple subscribers are displayed by cause
type
overvie
w of
complai
nt
subscrib
ers
NOTE
Non-exception node.
Issue 03 (2015-07-30)

1275
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers
l
l

unknown.
The Nastar supports combining inter-RNC call history records. If an interRNC handover occurs in one call process, the Nastar combines several
the user.
Click the
NOTE
page.

g
procedu For details, see Description of the Signaling Procedure Before Call
re area Release Tab Page.
area
subscribers.
For details, see Description of the Measurement Information Before Call
Release Tab Page, Description of Service Analysis Tab Page, and
Common Statistics Interface.
NOTE
page.
Issue 03 (2015-07-30)

1276
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers

including user information, call access information, call release information,
and statistical information.
Support Parameters (UMTS).
Description of the Signaling Procedure Before Call Release Tab Page

process.
Issue 03 (2015-07-30)

1277
Nastar
No.
Parameter
Description
(1)
Signaling
information
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
flowchart

NOTE

Description of the Measurement Information Before Call Release Tab Page

Before call release, measurement information in the UMTS complaint analysis support window
values.
NOTE
reports.
Issue 03 (2015-07-30)

1278
Nastar

No.
Parameter
Description
(1)
Detailed MR
information
table

information.
(2)

chart of
charts.
measurement
to right:
l Title
l Legend
counters.
Issue 03 (2015-07-30)

1279
Nastar

Counter
Description
Ec/No
Indicates the change trend of the

signal intensity according to the
received cells of the UE.
Displayed as a broken line chart.
RSCP

signal level according to the received
cells of the UE.
RSSI

RSSI according to the received intercells of the UE.
RSRP

RSRP according to the received LTE
cells of the UE.
RSRQ

RSRQ according to the received
inter-cells of the UE.
UE Tx Power

transmit power of the UE.

Figure 4-61 Description of mobility analysis tab page
For details, see 4.10.6 Reference for Complaint Analysis Support Parameters (UMTS).
Description of Service Analysis Tab Page

The service analysis includes RAB analysis.
l
Issue 03 (2015-07-30)
Figure 4-62 shows the items about the RAB service through the RAB analysis.
1280
Nastar
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.
Figure 4-62 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.
in the button area. In the displayed Common Statistics dialog box, select an object
Click
from the navigation tree and click Confirm. Details about the abnormal causes are displayed in
the right pane.
Map Interface
Click
Figure 4-63.
Issue 03 (2015-07-30)

1281
Nastar
No.
Feature
Description
(1)
Button area
Results.
(2)
Navigation
tree in the
map window
NOTE

support theme.
release cell KPI.
(3)
Geographic
observation
area
(4)
Grid detail
area
(5)
Legend area

click the
(6)
Information
area

Interface Description: LTE Complaint Analysis Support

This section describes the interface for LTE complaint analysis support. Before performing
related 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 03 (2015-07-30)

1282
Nastar
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.
Main Window
Issue 03 (2015-07-30)

1283
Nastar
No.
Parame Description
ter
Button
area

l

For details, see Description of the E-RAB Analysis Tab Page.

type.file format.
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.
reports.
NOTE
OK and export data.
page.
Issue 03 (2015-07-30)

1284
Nastar
No.
Parame Description
ter
the call
report
cause
type
overvie
w of
complai
nt
subscrib
ers
NOTE
Non-exception node.
Issue 03 (2015-07-30)

1285
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers
l
l

unknown.
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
NOTE
page.

g
analysis subscribers. The Nastar analyzes the mobility and service of all filtered
area
subscribers.
For details, see Map Interface, Description of the Measurement
Information Page and Description of the Mobility Analysis Tab Page.
NOTE
page.
Issue 03 (2015-07-30)

1286
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers

Support Parameters (LTE).

process.
Issue 03 (2015-07-30)

1287
Nastar
No.
Parameter
Description
(1)
Signaling
information
table
NOTE
When the signaling code stream is too long, copy it to a notepad and view the
complete information. Then, delete the notepad in time.
(2)
Signaling
flowchart

NOTE

Description of the Measurement Information Page

Before call release, measurement information in the LTE complaint analysis support window
values, as shown in Figure 4-66.
Figure 4-66 Measurement information tab page
Issue 03 (2015-07-30)

1288
Nastar
No.
Parameter
Description
(1)
Detailed MR
information
table
Lists detailed MR information. The information includes time,

measurement object type, and detailed counter information.
(2)

chart of
charts.
measurement
to right:
l Title
l Legend
For details, see 4.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 4-67.
Figure 4-67 E-RAB analysis tab page
Right-click one E-RAB, choose Detail E-RAB Information from the shortcut menu, view
the detailed information of the selected service bearer.
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.
Description of the Mobility Analysis Tab Page

Issue 03 (2015-07-30)

1289
Nastar
Map Interface
Click
Figure 4-69.
Issue 03 (2015-07-30)
No.
Feature
Description
(1)
Button area
Results.

1290
Nastar
No.
Feature
Description
(2)
Navigation
tree in the
map window
NOTE

support theme.
release cell KPI.
(3)
Geographic
observation
area
(4)
Grid detail
area
(5)
Legend area

click the
(6)
Information
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.
l
Main Interface (Signaling Plane)
Main Interface (User plane)
Issue 03 (2015-07-30)

1291
Nastar
Navigation Path
Use either of the following methods to open the interface that displays PS core complaint analysis
support results:
l
Select a finished PS core complaint analysis support task, and double-click a result record
in the Task Result area and choose View Analysis Result from the shortcut menu.

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 4-70.
Figure 4-70 Interface for PS core complaint analysis support results
Issue 03 (2015-07-30)

1292
Nastar
No.
Item
Description
Button
area

l

mode is XX-Cause type in the summary navigation tree. The naming
convention is Overview Tree_XX-Cause type.file format.
mode is Cause type-XX in the overview tree. The naming convention
is Overview Tree_Cause type-XX.file format.
The value of XX is as follows:
When you have the User Identity permission and choose to filter
complaining subscribers by IMSI, the value of XX is IMSI.
When you do not have the User Identity permission and choose to filter
complaining subscribers by IMSI, the value of XX is User ID: Alias.
When you choose to filter complaining subscribers by MSISDN, the
value of XX is MSISDN.

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.
provides the traffic statistics function. For details, see Traffic

Statistics on the Interface.
NOTE
OK and export data.
page.
l If you have the "User Identity" right, "MSISDN" will display the true MSISDN
information instead of the scrambled information with *.
Issue 03 (2015-07-30)

1293
Nastar
No.
Item
Description
Navigati
on tree
of the
CHR
cause
type
summar
y of
complai
ning
subscrib
ers
l Upper part: Displays the service types. You can select the service types.
l Middle part (upper): Displays the procedure types. You can select the
procedure types. The content in brackets after the SGSN and GGSN
indicates the RAT.
l Middle part (lower): Based on the selected service type and the procedure,
the call records of multiple subscribers are displayed by cause type in the
navigation tree mode.
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 follows: Cause type(N). (N) after each node
indicates the number of call records under the node.
NOTE
Non-exception node.
Issue 03 (2015-07-30)

1294
Nastar
No.
Item
Description
Summar View the overview information of all filtered records, such as time, cell,
y table procedure, and exception cause.
of
in the Combined column: indicates that the call record in the row is
complai l
a combined one.
ning
The Nastar supports combination of records on the same NE during a
subscrib
call and displays the combined record in the summary table.
er
records
Double-click a specified combined record to open the list of raw
records.
NOTE
The name of the tab page is in the format of ***_Serial Number, where ***
indicates a subscriber.
l
l
: indicates that the call record in the row is abnormal.

in the USN+UGW Associated column: indicates that the call record
in the row is a associated one.
The Nastar supports association of USN, UGW, and Gx/Gy/Radius
records during a call and displays the associated record in the summary
table.
Double-click a specified associated record to open the list of raw
records, in which raw records closely related to the associated record
are highlighted.
In the list of raw records, double-click a record. The raw records
closely related to the selected record in the other two RATs are
highlighted.
NOTE
Click the
NOTE
page.
l For some columns (such as User ID: Alias), the system only centralized display the
Issue 03 (2015-07-30)
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

1295
Nastar
No.
Item
Description
Details
table of
complai
ning
subscrib
er
records
Displays the subscriber details corresponding to the records selected in area

2.
For details about the parameters, see Reference for Complaint Analysis
Support Parameters (PS Core) - Signaling Plane.
The table is hidden by default when you initially open the window.
NOTE
page.
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.
in the button area. The Common Statistics dialog box is displayed.
1.
Click
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
4-71.
Figure 4-71 Common statistics dialog box
Issue 03 (2015-07-30)

1296
Nastar
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.
Main Window (User plane)

The complaint analysis support results can be displayed in tables, such as overview table, SDR
information, subscriber information, and procedure information, as shown in Figure 4-70.
Figure 4-72 PS Core Complaint analysis support interface
Issue 03 (2015-07-30)

1297
Nastar
No.
Parame Description
ter
Button
area

l


detailed information (such as base information, user information, KQI
information).
provides the abnormal cause statistics function of the service. This

button is available only for user plane call records. For details, see
l SDR Model: including signaling plane and user plane. This option is
available only when the Nastar analyzes user plane and signaling plane
data at the same time.
NOTE
OK and export data.
page.
Issue 03 (2015-07-30)

1298
Nastar
No.
Parame Description
ter
Overvie l Upper part: Displays the service types for GSM/UMTS/LTE. You can
w tree of
select the service types.
the xDR
NOTE
cause
If users select only a service type node, the Nastar filters only the abnormal or
normal xDRs of the selected service type.
type
overvie l Middle part: Call records of multiple subscribers are displayed by cause
w of
complai
nt
subscrib
ers
In Cause type-XX mode, all filtered call records are classified by
cause type and the call records of each cause type are then classified
by XX.
In XX-Cause type mode, all filtered call records are classified by
XX and the call records of each XX are then classified by cause type.
NOTE
page.
Issue 03 (2015-07-30)

1299
Nastar
No.
Parame Description
ter
xDR
overvie
w table
of
complai
nt
subscrib
ers
information includes the information, such as access time, access cell, release
l
l
l
: indicates that the call record in the row can be associated with user
or signaling plane call records. Click this icon to open an associated call
record.
unknown.
Click the
NOTE
Theme Displays detailed KQI information about all filtered subscribers.

analysis
area
xDR
overvie
w table
of
complai
nt
subscrib
ers
Displays detailed information about the selected subscriber in area 2.

For details about parameters, see Reference for Complaint Analysis
Support Parameters (PS Core) - User Plane.

The common statistics function allows the Nastar to collect statistics on the abnormal cause,
abnormal sub-cause, demarcation result, and abnormal counts generated for a specified user or
service.
1.
Click
2.
Select an object from the navigation tree and click Confirm. Details about the abnormal
causes are displayed in the right pane, as shown in Figure 4-73.
Issue 03 (2015-07-30)

1300
Nastar
Interface Description: Combined Complaint Analysis Support

This section describes the interface that displays combined complaint analysis support results.
interface.
Combined complaint analysis support based on signaling plane data
The Nastar allows you to perform combined complaint analysis support based on the signaling
plane data collected from different network types on the RAN side as well as based on signaling
plane data collected on the RAN and PS core sides. Therefore, the Nastar supports combined
complaint analysis support based on signaling plane data of networks in the following
combinations:
l
Only RAN side

LTE-FDD+LTE TDD
GSM+UMTS
GSM+LTE-FDD/TDD
GSM+LTE-TDD
UMTS+LTE-FDD/TDD
GSM+UMTS+LTE-FDD/TDD
Issue 03 (2015-07-30)

1301
Nastar
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
Combined complaint analysis support based on signaling and user plane data
The Nastar allows you to perform combined complaint analysis support based on signaling plane
data collected from LTE FDD and TDD networks and user plane data collected on the PS core
side using the UGW. Therefore, the Nastar supports combined complaint analysis support based
on signaling plane and user plane data in the following combinations:
l
LTE FDD(signaling plane)+PS Core(user plane)
LTE TDD(signaling plane)+PS Core(user plane)
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. Right-click a result record of the task and choose View Analysis
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, as shown in Figure 4-74:
Issue 03 (2015-07-30)

1302
Nastar
Figure 4-74 Combined Complaint Analysis Support signaling plane data (Using LTE and
PS Core as an example)
The service types displayed in the navigation tree (area 1) are combinations of the service
types for the complaint analysis support of involved RATs.
The cause types displayed in the navigation tree (area 2) are combinations of the cause
The description of the exception causes provides the mapping between service types and
cause types. For details, see Appendix: Exception Cause Classification (Combined
Analysis).
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 4.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.
l For details about the interface for the VoLTE combined complaint analysis support based on signaling
plane data collected from LTE FDD and TDD networks and user plane data collected on the PS core
side, see the description for the user plane data analysis interface in Interface Description: PS Core
Complaint Analysis Support. For details about parameters, see Reference for Complaint Analysis
Issue 03 (2015-07-30)

1303
Nastar
4.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

This section describes the parameters for querying GSM CS complaint analysis support results.
You can refer to the description when querying GSM CS complaint analysis support results.
Summary
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Serial
Num
ber
[1,2^31-1)
N/A
Serial number of a CHR in

General Evaluation. Serial
number is the key word of a
CHR by which you can
identify this unique CHR. It
is also an internal identifier
provided by Nastar.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1304
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Comb
ined
N/A
N/A
Whether a CHR is a
combined one.
l SRAN8.0/
GBSS15.0/
RAN 15.0
By Nastar, information about

a call is obtained from both
the mobile-originated BSC
and the mobile-terminated
BSC and then is combined
into one CHR. A CHR is a
combined one if a yellow
icon is displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Status
N/A
N/A
Whether a CHR is abnormal.

A CHR is abnormal if a red
exclamation mark is
displayed.
The cause type of a call is
Other and the exception
status of the call is unknown
if a yellow question mark is
displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1305
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Abno
rmal
Cause
For details, see

"Appendix: Exception
Cause Classification / Key
Signaling (GSM)".
N/A
Cause of the exception

carried in an Access Request
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
NOTE
l SRAN8.1/
GBSS15.1/
RAN 15.1
l The HQIs after the call

setup is successful are only
counted in the abnormal
cause. Short call-related
counters in raw CHRs to be
combined are for reference
only, and do not affect the
exception cause results in
combined CHRs.
l For combined CHRs, the
voice quality problem
counters (excluding
average counters) are
measured based on the subCHRs 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 subCHRs 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.
Issue 03 (2015-07-30)

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1306
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Netw
ork
GSM-CS, GSM-PS
N/A
Network that a VIP

subscriber accesses to
initiate a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1307
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Acces
s
Cause
Non-SMS message from a

mobile-originated VIP
subscriber
(AC_ORIGIN_CALL_N
O_SMS)
N/A
Cause of a signaling access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
SMS message from a

subscriber
(AC_ORIGIN_CALL_S
MS)
Answer to paging
(AC_ANSWER_TO_PA
GING)
Call re-setup
(AC_CALL_RE_ESTABLISH)
Emergency call
(AC_EMERGENCY_CA
LL)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Location update
(AC_LOCATION_UPDATE)
IMSI detachment
(AC_IMSI_DETACH)
Data service
(AC_PACKET_CALL)
LMU service
(AC_LMU_ESTABLISH)
SS service
(AC_SS_ESTABLISH)
VGCS service
(AC_VGCS_ESTABLISH)
VBS service
(AC_VBCS_ESTABLISH)
LCS service
(AC_LCS_ESTABLISH)
Any other service
(AC_RESERVED)
Issue 03 (2015-07-30)

1308
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
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_INDICATION)
VGCS access
(AC_VGCS_VBS_VPCS
)
mobile-terminated VIP
subscriber
(AC_ANSWER_TO_PA
GING_CALL)
SMS message from a
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)
Issue 03 (2015-07-30)

1309
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Start
Time
N/A
N/A
Signaling start time for a call,

namely, the time when a MS
sends the Channel Request
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acces
s Cell
1 to 64 characters
N/A
Name of the cell in which a

MS sends the Channel
Request message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The parameter is displayed in

the following format: BSC
Name: Cell Name (BSC
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
In the preceding format, BSC

OPC is the originating
signaling point configured
on the BSC side.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1310
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
End
Time
N/A
N/A
Signaling end time for a call,
l SRAN8.0/
GBSS15.0/
RAN 15.0

receives the Channel Release
message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Relea
se
Cell
1 to 64 characters
N/A

MS receives the Channel
Release message.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1311
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
User
ID:Al
ias
N/A
N/A
User ID, which is created by

the system when creating the
task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Alias, which is created by

the user when creating the
task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMSI
N/A
N/A
subscriber.
the "User Identity" right, you
can view the IMSI
information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1312
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
IMEI
-TAC
00000000-99999999
N/A
allocation code (IMSI-TAC)
of a VIP subscriber, which is
the first eight digits in the
IMEI of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Mode
l
N/A
N/A
Type of a MS.
You can obtain the IMEITACs of the UE from the MS
type management function.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1313
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Peer
MSIS
DN
N/A
N/A
Mobile station international

ISDN number (MSISDN) of
a peer subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Durat
ion
[0,+)
Sec
ond
Service duration covering

the call duration and the
signaling setup duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Service duration = End time

- Start time
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1314
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
CS
Servi
ce
Durat
ion
[0,+)
Sec
ond
Call duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Call duration = Time stamp

of the Disconnect message Time stamp of the Connect
Acknowledge message
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1315
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Call
Setup
Resul
t
Following are criteria

indicating a proper call
setup:
N/A
Network access result for a

mobile-originated call. The
result indicates a proper call
setup or an abnormal call
setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1. Normal: The called

subscriber receives the
Connect ACK message
and proper call
communication is
established between the
calling and called
subscribers.
2. The calling subscriber
receives the Disconnect
message and termination
of the call is triggered by
the peer subscriber.
The call setup result is

displayed in the following
format: Call Release Result/
Cause of Abnormal Call
Release/Sub-Cause of
Abnormal Call Release.
(You can obtain the
preceding three parameters
in the Call Release
Information window.)
3. Connection is released
due to an outgoing interBSC handover.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

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
5. The traffic channel is
6. The call setup duration
threshold.
7. The BSS rejects the
immediate assignment
request.
8. The BSC releases
channel resources.
9. The MSC releases
channel resources
abnormally.
Issue 03 (2015-07-30)

1316
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
N/A
Network release result for a

release or an abnormal call
release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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 interBSC handover fails.
Call
Relea
se
Resul
t

release:
1. Normal: The subscriber
message and starts
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

release of traffic channel
during a call:
handover fails.
2. An intra-BSC handover
fails.
3. The BSC releases
channel resources.
4. The MSC releases
channel resources.
Issue 03 (2015-07-30)

1317
Nastar
User Information
Parame
ter
Range
Unit
Description
Supported Solution
Version
User
ID:Alias
N/A
N/A

task.
l SRAN8.0/
GBSS15.0/RAN
15.0

task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
IMSI
N/A
N/A
subscriber.
can view the IMSI
information.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

1318
Nastar
Parame
ter
Range
Unit
Description
Supported Solution
Version
IMEITAC
00000000-9
9999999
N/A
Refer to "IMEI-TAC" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Model
N/A
N/A
Refer to "Model" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
MS
Capabili
ty
N/A
N/A
Capability of the MS.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

1319
Nastar
Parame
ter
Range
Unit
Description
Supported Solution
Version
>Suppor
t
UtranFD
D
Yes
N/A
Whether a MS supports the

UtranFDD.
l SRAN8.0/
GBSS15.0/RAN
15.0
No
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
>Suppor
t
UtranT
DD
Yes
N/A
No

UtranTDD.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
>Suppor
t
VAMO
S
Yes
No
N/A

VAMOS.
VAMOS, voice services
over adaptive multi-user
channels on one slot.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

1320
Nastar
Parame
ter
Range
Unit
Description
Supported Solution
Version
>Suppor
t U900
Frequen
cy Band
Yes
N/A

U900.
l SRAN8.0/
GBSS15.0/RAN
15.0
No
That is, whether a MS

supports accessing to the 3G
network using the 900 MHz/
850 MHz band of the 2G
network.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Peer
MSISD
N
N/A
N/A
Refer to "MSISDN" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

1321
Nastar
Call Access Information

Parame
ter
Range
Unit
Description
Supported
Solution Version
Start
Time
N/A
N/A
Refer to "Start Time" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Cell
1 to 64
characters
N/A
Refer to "Access Cell" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1322
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Access
Carrier
[0,71]
N/A
Information about the carrier

frequency at which a MS sends a
Channel Request message,
namely, the number of the carrier
frequency.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Channel
[0,7]
N/A
Information about the channel

through which a MS sends a
namely, the number of the
channel.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1323
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Access
Cause
N/A
N/A
Cause carried in an access

request message.
l SRAN8.0/
GBSS15.0/RAN
15.0
See Access Type in General

Evaluation.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Flag
(Intersystem/
Intrasystem)
Intersystem
Intrasystem
N/A
According to the access causes to

identify the user's current
business is accessed from intrasystem or from inter-system.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1324
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Access
Flag
(MOC/
MTC)
MOC
N/A

business is accessed by MTC or
MOC.
l SRAN8.0/
GBSS15.0/RAN
15.0
MTC
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Flag
(SMS/
Voice)
SMS
Voice
N/A

business is accessed by SMS or
Voice.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1325
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Call
Setup
Result
N/A
N/A

mobile-originated call.
l SRAN8.0/
GBSS15.0/RAN
15.0
See the level-1 cause, Call Setup

Result, in Call Setup Result/
Cause of Abnormal Call Setup/
Sub-Cause of Abnormal Call
Setup in General Evaluation.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cause of
abnorma
l call
setup
N/A
N/A
Cause of an abnormal signaling

access for a call.
See the level-2 cause, Cause of
Abnormal Call Setup, in Call
Setup Result/Cause of Abnormal
Call Setup/Sub-Cause of
Abnormal Call Setup in General
Evaluation.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1326
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Subcaus
e of
abnorma
l call
setup
N/A
N/A
Detailed cause of an abnormal

signaling access for a call.
l SRAN8.0/
GBSS15.0/RAN
15.0
See the level-3 cause, Sub-Cause

of Abnormal Call Setup, in Call
Evaluation.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Delay
Estimati
on
N/A
N/A
Access delay estimation when

the UE accesses the network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1327
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>ASSIG
NMENT
COMPL
ETE
Message
Timesta
mp
N/A
N/A
Time when the assignment is

finished after initiating a call and
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Access
Delay
[0,+)
Secon
d
Access delay time of the service.

Access Delay = Time of
ASSIGNMENT COMPLETE Time of CHANNEL REQUEST
="ASSIGNMENT COMPLETE
Message Timestamp"-"Start
Time"
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1328
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>Overlo
ng
Access
Delay
Yes
N/A
Whether the abnormal of

overlong access delay is
occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0
The abnormal threshold is set

when creating tasks.
l SRAN8.1/
GBSS15.1/RAN
15.1
No
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Alertin
g Time
N/A
N/A
Time when a VIP subscriber

hears the alerting after initiating
a call.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1329
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>Call
Complet
ion
Delay
(Alertin
g)
[0,+)
Secon
d
Call completion delay time of the

service.
l SRAN8.0/
GBSS15.0/RAN
15.0
Call Completion Delay(Alerting)

= Time of ALERTING - Time of
CHANNEL REQUEST
=Alerting Time - Start Time
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Overlo
ng Call
Complet
ion
Delay
(Alertin
g)
Yes
No
N/A

overlong call completion delay
(Alerting) is occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1330
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>Connec
t
Acknow
ledge
Time
N/A
N/A

hears the voice of the peer
subscriber after initiating a call.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Call
Complet
ion
Delay
(Connec
t Ack)
[0,+)
Secon
d

service.
Call Completion Delay(Connect
Ack) = Time of CONNECK
ACK - Time of CHANNEL
REQUES REQUEST
=Connect Acknowledge Time Start Time
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1331
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>Overlo
ng Call
Complet
ion
Delay
(Connec
t Ack)
Yes
N/A

(Connect Ack) is occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
No
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measure
ment
Informat
ion On
Access
N/A
N/A
Measurement information when

a MS accesses to the network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1332
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>TA
[0,63]
N/A
Value of the TA when a MS

accesses to the network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Abnor
mal TA
Yes
No
N/A
Whether the abnormal that TA is

too large when accessing to the
network is occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1333
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>RACH
Level
[-110,-47]
dBm
Value of the RACH level when a

MS accesses to the network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Abnor
mal
RACH
Level
Yes
No
N/A
Whether the abnormal that

RACH Level is too small is
occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1334
Nastar
Call Release Information

Parame
ter
Range
Unit
Description
Supported
Solution Version
End
Time
N/A
N/A
Refer to "End Time" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Duration
[0,+)
Secon
d
Refer to "Duration" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1335
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Release
Cell
1 to 64
characters
N/A
Refer to "Release Cell" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Release
Carrier
N/A
N/A

signaling release message.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1336
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Call
Release
Result
N/A
N/A

l SRAN8.0/
GBSS15.0/RAN
15.0
See the level-1 cause, Call

Release Result, in Call Release
Result/Cause of Abnormal Call
Release/Sub-Cause of Abnormal
Call Release in General
Evaluation.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cause of
abnorma
l call
completi
on
N/A
N/A

release during a call.
Abnormal Call Release, in Call
Release Result/Cause of
Abnormal Call Release/SubCause of Abnormal Call Release
in General Evaluation.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1337
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Subcaus
e of
abnorma
l call
completi
on
N/A
N/A

signaling release during a call.
l SRAN8.0/
GBSS15.0/RAN
15.0

of Abnormal Call Release, in
Call Release Result/Cause of
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Location
Group
Number
N/A
N/A
Refer to the location group where

a terminal is located when the
signaling is released. This
parameter is valid only for the
multi-RRU serving a cell feature.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1338
Nastar
CS Service Information
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Service
Process
Delay
Estimati
on
N/A
N/A
Delay estimation for service

process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>IntraBSC
Channel
Release
Timesta
mp
N/A
N/A
Timestamp of intra-BSC channel

release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1339
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Calling
Duration
[0,+)
Secon
d
Calling Duration = Time of

DISCONNECT - Time of
CONNECT ACK
l SRAN8.0/
GBSS15.0/
RAN 15.0
=Intra-BSC Channel Release

Timestamp - CONNECT ACK
Timestamp
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Short
Call
Yes
No
N/A
Whether the abnormal of short call

is occurred.
The abnormal threshold is set when
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1340
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Service
Quality
Estimati
on for
Service
Process
N/A
N/A
Service quality estimation for

service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)
>Time
of Up
Single
Pass
N/A
N/A
Time of uplink one-way audio
SRAN10.1/
GBSS17.1/
RAN17.1
>Time
of Down
Single
Pass
N/A
N/A
Time of downlink one-way audio
SRAN10.1/
GBSS17.1/
RAN17.1

1341
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Oneway
Audio
During a
Call
Yes
N/A
Whether uplink one-way audio

occurs during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

detect the one-way audio
exceptions related to the channels
within the BSS (BTS<->TC)
instead of those related to the Um
and A interfaces.
Principle for detecting uplink oneway 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
primary uplink one-way audio
occurs, and starts the mechanism for
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
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1342
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Downli
nk Oneway
Audio
During a
Call
Yes
N/A
Whether downlink one-way audio

l SRAN8.0/
GBSS15.0/
RAN 15.0
No

and A interfaces.
one-way audio: The DSP in the
DTRU of the BTS performs
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
primary downlink one-way audio.
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, oneway audio occurs on the downlink
voice channel.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1343
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Call
Crosstal
k
Yes
N/A
Whether uplink crosstalk occurs

during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

the crosstalk exceptions related to
the channels within the BSS (BTS<>TC) instead of those related to the
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.
>Downli
nk Call
Crosstal
k
Yes
No
N/A
Whether downlink crosstalk occurs

during a call.
the unique identifier of a call into
the free bits of uplink voice TRAU
frames. The DSP of the BTS
period, downlink crosstalk occurs.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1344
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Noise
Yes
N/A
Whether uplink noise occurs during

a call, which is detected by the
device.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Downli
nk Noise
Yes
No
N/A
Whether downlink noise occurs

during a call, which is detected by
the device.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1345
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Call HQI
[0.00,100.00
]
Average value for the uplink high

quality indicators (HQIs) of call
setups that include the HQIs before
and after the call setup is successful.
l SRAN8.0/
GBSS15.0/
RAN 15.0

call and is measured on a 0-to-7
scale. Level 0 indicates the best
quality.
In CHRs of the BSC6900
V900R011 or any later version:
levels 0 to 3/Number of
measurement reports indicating a
voice quality of levels 0 to 7 x 100%
V900R008:
>Bad
Uplink
HQI
Yes
No
N/A
Whether the abnormal of bad uplink

HQI is occurred of call setups that
include the HQIs before and after
creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1346
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Downli
nk Call
HQI
[0.00,100.00
]
Average value for the downlink

HQIs of call setups that include the
HQIs before and after the call setup
is successful.
l SRAN8.0/
GBSS15.0/
RAN 15.0

V900R008:
>Bad
Downlin
k HQI
Yes
No
N/A
Whether the abnormal of bad

downlink HQI is occurred of call
creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1347
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Call VQI
[0.00,5.00]
N/A
Average value for the uplink voice

quality indicators (VQIs) of
l SRAN8.0/
GBSS15.0/
RAN 15.0

(MOS) and indicates the voice
quality of a call. The value of the
voice quality ranges from 0 to 5.
The larger the value is, the better the
voice quality is.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Average value for the uplink VQIs

of successful call setups =
Aggregated value of uplink VQIs/
Total number of uplink VQI tests
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Bad
Uplink
VQI
Yes
No
N/A

VQI is occurred.
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1348
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Downli
nk Call
VQI
[0.00,5.00]
N/A

voice quality indicators (VQIs) of
l SRAN8.0/
GBSS15.0/
RAN 15.0

voice quality is.
l SRAN8.1/
GBSS15.1/
RAN 15.1

VQIs of successful call setups =
Aggregated value of downlink
VQIs/Total number of downlink
VQI tests
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Bad
Downlin
k VQI
Yes
No
N/A

downlink VQI is occurred.
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1349
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Measure
ment
Informat
ion On
Service
Process
N/A
N/A
Measurement information on
service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Averag
e Uplink
Level
[-110,-47]
dBm
Average uplink level on service

process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1350
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Averag
e
Downlin
k Level
[-110,-47]
dBm
Average downlink level on service

process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Averag
e Uplink
Quality
[0,7]
N/A
Average uplink quality on service

process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1351
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Averag
e
Downlin
k
Quality
[0,7]
N/A
Average downlink quality on

service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signaling Procedure Before Call Release

Parame
ter
Range
Unit
Description
Supported
Solution Version
Number
[1,+)
N/A
Unique number for the signaling

message that a VIP subscriber
sends and receives during the
signaling procedure.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1352
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Signalin
g Time
N/A
N/A
Time when a signaling message

is sent or received.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signalin
g Direct
Uplink
Downlink
N/A
Direction in which a signaling

message is sent or received.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1353
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Signalin
g Type
N/A
N/A
Type of a signaling message

transmitted on the A or Abis
interface during the signaling
procedure. For example, the
parameter can be a Channel
Request message.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signalin
g
Content
N/A
N/A
Content of a signaling message.

You can obtain the content of a
signaling message by viewing
the related tree structure.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1354
Nastar
Measurement Information Before Call Release

Parame
ter
Range
Unit
Description
Supported
Solution Version
Number
[1,+)
N/A
Unique number of a signaling

message carrying a
measurement report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measure
ment
Time
N/A
N/A
Time when a measurement

report is submitted.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1355
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Serial
Number
N/A
N/A
Serial number for a reported

measurement report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measure
ment
Object
Type
Server
Nbr1~6
N/A
Type of a measurement object,

reported in a measurement
report.
l SRAN8.0/
GBSS15.0/RAN
15.0
For example, if the parameter is

Server, the measurement object
is a serving cell; if the parameter
is Nbr1, the measurement object
is neighboring cell 1.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1356
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Measure
ment
Object
N/A
N/A
Name of a measurement object

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
The parameter is displayed in the

following format: Name of the
BSC: Name of the cell.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BCCH
[0,1023]
N/A
Broadcast control channel

(BCCH) of a neighboring cell,
report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1357
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
BSIC
[0,77]
N/A
Base transceiver Station Identity

Code (BSIC) of a neighboring
cell, reported in a measurement
report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TA
[0,63]
N/A
TA of a serving cell, reported in

a measurement report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1358
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
RxLevel
(Downli
nk)
[-110,-47]
dBm
Downlink RxLevel of a serving

cell and that of a neighboring
report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RxLevel
(Uplink)
[-110,-47]
dBm
Uplink RxLevel of a serving

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1359
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
RxQualit
y
(Downli
nk)
[0,7]
N/A
Downlink RxQuality of a
serving cell, reported in a
measurement report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RxQualit
y
(Uplink)
[0,7]
N/A
Uplink RxQuality of a serving

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1360
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
BTS
Power
[0,15]
N/A
BTS power of a serving cell,

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
MS
Power
[0,31]
N/A
MS power of a serving cell,

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1361
Nastar
Mobility Analysis
Parame
ter
Range
Unit
Description
Supported
Solution Version
Number
[1,+)
Numb
er
Number for a handover triggered

during a call.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
N/A
N/A
Whether a record indicates an

abnormal handover.
The record indicates an
abnormal handover if a red
exclamation mark is displayed.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1362
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Abnorm
al Cause
Communicat
ion resumes
on the
original
channel after
a handover
failure
N/A
Whether a handover succeeds,

and the cause of a handover
failure.
l SRAN8.0/
GBSS15.0/RAN
15.0
The cause is displayed as

Normal if a handover succeeds.
l SRAN8.1/
GBSS15.1/RAN
15.1
Possible causes of a handover

failure include the following:
communication resumes on the
original channel after a handover
failure; the BSC releases
channel resources; the MSC is
faulty.
the BSC
releases
channel
resources
the MSC is
faulty
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Handove
r Type
Intra-BSC
handover
N/A
Type of a handover
Outgoing
cell handover
Incoming
inter-BSC
handover
Outgoing
inter-BSC
handover
Outgoing
inter-RAT
handover
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1363
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Initiatin
g Time
N/A
N/A
Time when a handover is

initiated,
l SRAN8.0/
GBSS15.0/RAN
15.0
namely, the time when the BSC

sends the Handover CMD
message.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Interval
[0,+)
N/A
Duration = End time - Start time
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1364
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Overlon
g
Interval
Yes
N/A
The first case: "Handover Type"

is "Outgoing inter-BSC
handover"
l SRAN8.0/
GBSS15.0/RAN
15.0
If the duration is more than

"Outgoing BSC Handover
Interval", it displays "Yes"; If
not, it displays "No".
l SRAN8.1/
GBSS15.1/RAN
15.1
No
The second case: "Handover

Type" is "Outgoing inter-RAT
handover"
"Outgoing System Handover
not, it displays "No". The other
case: displays null.
Interval" and "Outgoing System
Handover Interval" is set when
creating tasks.
End
Time
N/A
N/A
End time of a handover.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1365
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Handove
r
Triggeri
ng Cause
N/A
N/A
Cause of a handover.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Source
cell
N/A
N/A
Name of the source cell to be

handed over.
BSC: Name of the cell (BSC
obtain the names of the BSC and
the cell from the configuration
data. The names are not
displayed if they are not
available.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0

OPC is the originating signaling
l SRAN10.1/
point configured on the BSC
GBSS17.1/
side.
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1366
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Source
Location
Group
No.
N/A
N/A
Number of source location

group.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
cell
N/A
N/A
Name of the target cell to which

a handover is to be performed.
data.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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 03 (2015-07-30)

1367
Nastar
Summary
Param
eter
Range
Unit
Description
Supported
Solution
Version
Serial
Number
[1,2^31-1)
N/A

number is the key word of a CHR
by which you can identify this
unique CHR. It is also an internal
identifier provided by Nastar.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Combin
ed
N/A
N/A
Whether a CHR is a combined

one.
By Nastar, information about a
call is obtained from both the
mobile-originated BSC and the
mobile-terminated BSC and then
is combined into one CHR. A
CHR is a combined one if a
yellow icon is displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1368
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Status
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

The cause type of a call is Other
and the exception status of the
call is unknown if a yellow
question mark is displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al Cause
For details, see

"Appendix:
Exception Cause
Classification /
Key Signaling
(GSM)".
N/A
Cause of the exception carried in

an Access Request message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1369
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Networ
k
GSM-CS, GSMPS
N/A
Network that a VIP subscriber

accesses to initiate a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Start
Time
N/A
N/A
Signaling access time for a call,

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1370
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Access
Cell
1 to 64 characters
N/A
Name of the cell in which a MS

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0

following format: BSC Name:
Cell Name (Cell ID). You can
displayed
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
End
Time
N/A
N/A
Signaling release time for a call,

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1371
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Release
Cell
1 to 64 characters
N/A

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0

data. The names are not display
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User
ID:Alia
s
N/A
N/A
User ID, which is created by the

system when creating the task.
Alias, which is created by the
user when creating the task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1372
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMEITAC
00000000-999999
99
N/A

(IMSI-TAC) of a VIP subscriber,
which is the first eight digits in
the IMEI of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1373
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Model
N/A
N/A
Type of a MS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
You can obtain the IMEI-TACs

of the UE from the MS type
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Peer
MSISD
N
N/A
N/A

ISDN number (MSISDN) of a
peer subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1374
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Duratio
n
[0,+)
Seco
nd
Service duration covering the

call duration and the signaling
setup duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Service duration = End time Start time
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1375
Nastar
User Information
Param
eter
Range
Unit
Description
Supported
Solution
Version
User
ID:Alia
s
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMSI
N/A
N/A
subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1376
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
IMEITAC
00000000-99999
999
N/A

Summary area.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Model
N/A
N/A

Summary area.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1377
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
MS
Capabil
ity
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt GPRS
Support
Unsupport
N/A
Whether a Terminal supports

GPRS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1378
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt GPRS
MultiSlot
Class
N/A
N/A
GPRS Multislot Class of a

Terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt
EGPRS
Support
Unsupport
N/A

EGPRS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1379
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt
EGPRS
MultiSlot
Class
N/A
N/A
EGPRS Multislot Class of a

Terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt 900M
E
Frequen
cy Band
Support
Unsupport
N/A
Whether a Terminal supports the

E-GSM900 band.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1380
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt
1800M
Frequen
cy Band
Support
N/A

E-GSM1800 band.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Unsupport
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt G-TD
DualMode
Support
Unsupport
N/A

both GSM and TD-SCDMA.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1381
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt G-U
DualMode
Support
N/A

both GSM and UMTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Unsupport
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt DTM
Support
Unsupport
N/A

DTM.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1382
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt PS
Handov
er
Support
N/A

handovers in the PS domain.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Unsupport
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Insuffic
ient
Termin
al
Capabil
ity
Yes
No
N/A
The capability of a Terminal is

insufficient in the case of the
following:
l SRAN8.0/
GBSS15.0/
RAN 15.0
The Terminal supports GPRS

but not EGPRS.
l SRAN8.1/
GBSS15.1/
RAN 15.1
The Terminal supports EGPRS

but the EGPRS multislot class is
below 10.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1383
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Subscri
ber
Registra
tion
Paramet
er
N/A
N/A
Parameters related to the service

that a VIP subscriber subscribes
to when opening an account.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Reliab
ility
Level
N/A
N/A
For details about the parameter,

see see 3GPP TS 23.107.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1384
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Subscr
iption
Rate
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
Subscri
ber
Registra
tion
Yes
No
N/A
An account-opening exception
occurs in the case of the
following:
l SRAN8.0/
GBSS15.0/
RAN 15.0
The reliability class of a VIP

subscriber is not 3, namely, the
reliability class is not the RLC
acknowledged mode.
l SRAN8.1/
GBSS15.1/
RAN 15.1
The subscription rate is lower

than the predefined exception
threshold (which is set by
engineers when creating tasks).
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1385
Nastar
Peer Information
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Number
of
Server
Applica
tions
N/A
N/A
Total number of the server applications that

a VIP subscriber accesses when attempting
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
List of
Servers
and
Applica
tions
N/A
N/A
The list of applications that the server

supports.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1386
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>IP
Address
N/A
N/A
IP address of the server that a VIP subscriber

accesses when attempting to use a data
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Server
Name
N/A
N/A
Name of the server that a VIP subscriber

service. You can obtain the name of a server
by choosing System Function > Data
Service Server Management in the
navigation tree of Nastar based on the IP
address of the serve
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1387
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Port
[0,65
535)
N/A
Port number of the server that a VIP

subscriber accesses when attempting to use
a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Applic
ation
N/A
N/A
name of the application that a VIP

a data service. You can obtain the name of
an application by choosing System Function
> Data Service Server Management in the
navigation tree of Nastar based on the port
number
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1388
Nastar
Access and Release Information

Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Start
Time
N/A
N/A
Start time for a VIP subscriber to use a data

service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TA
upon
Access
[0,63
]
N/A
Value of the TA when a Terminal sends the

Channel Request message for a VIP subscriber
to use a data service. It indicates the distance
between the Terminal and its serving cell to
some extent.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1389
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
RxQual
ity upon
Access
[0,7]
N/A
Value of the RxQuality when a Terminal sends

the Channel Request message for a VIP
subscriber to use a data service. It indicates the
signal quality during the initial access of the
Terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
GMSK
MEAN
BEP
upon
Access
[0,31
]
N/A
Information about the GMSK MEAN BEP

when a Terminal sends the Channel Request
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1390
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
8PSK
MEAN
BEP
upon
Access
[0,31
]
N/A
Information about the 8PSK MEAN BEP

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Cell
1 to
64
chara
cters
N/A
Name of the cell in which a MS sends the

The parameter is displayed in the following
format: BSC Name: Cell Name (Cell ID). You
can obtain the names of the BSC and the cell
from the configuration data. The names are not
displayed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1391
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
End
Time
N/A
N/A
Time when a VIP subscriber releases a data

service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Duratio
n
[0,
+)
Sec
ond
Duration of the data service used by a VIP

subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1392
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Release
Cell
1 to
64
chara
cters
N/A
Cell in which a VIP subscriber releases a data

service. In a GSM network, a cell reselection
always triggers the release of data service.
Therefore, the release cell is always the access
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink
Signalin
g
Access
Times
[0,
+)
Nu
mbe
r

(uplink CCCH) during the whole process for
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1393
Nastar
Mobility Manager Information

Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Attach
Request
Times
[0,
+)
Nu
mbe
r
Number of the Attach Request messages that

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Attach
Accept
Times
[0,
+)
Nu
mbe
r
Number of the Attach Accept messages that a

VIP subscriber receives during the whole
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1394
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Attach
Reject
Times
[0,
+)
Nu
mbe
r
Number of the Attach Reject messages that a

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Detach
Request
Times
[0,
+)
Nu
mbe
r
Number of the Detach Request messages that

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1395
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Detach
Accept
Times
[0,
+)
Nu
mbe
r
Number of the Detach Accept messages that a

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP
Active
Request
Times
[0,
+)
Nu
mbe
r
Number of the PDP Active Request messages

that a VIP subscriber sends during the whole
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1396
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
PDP
Active
Accept
Times
[0,
+)
Nu
mbe
r
Number of the PDP Active Accept messages

that a VIP subscriber receives during the whole
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP
Active
Reject
Times
[0,
+)
Nu
mbe
r
Number of the PDP Active Reject messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1397
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
RA
Update
Request
Times
[0,
+)
Nu
mbe
r
Number of the RA Update Request messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RA
Update
Accept
Times
[0,
+)
Nu
mbe
r
Number of the RA Update Accept messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1398
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
RA
Update
Reject
Times
[0,
+)
Nu
mbe
r
Number of the RA Update Reject messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Suspen
d Times
[0,
+)
Nu
mbe
r
Number of Suspends during the whole process

for a VIP subscriber to use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1399
Nastar
RAN Abnormal Information

Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Times
of
Downli
nk TBF
Setup
Failure
[0,
+)
Num
ber
Number of TBF setup failures on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
s of
Downli
nk TBF
Setup
Failure
N/A
N/A
Cause of a TBF setup failure on the downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1400
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Carrie
r Index
N/A
N/A
Carrier of a TBF setup failure on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BCCH
N/A
N/A
BCCH of a TBF setup failure on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1401
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Times
of
Uplink
TBF
Setup
Failure
N/A
Num
ber
Number of TBF setup failures on the uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
s of
Uplink
TBF
Setup
Failure
N/A
N/A
Cause of a TBF setup failure on the uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1402
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Carrie
r Index
N/A
N/A
Carrier of a TBF setup failure on the uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BCCH
N/A
N/A
BCCH of a TBF setup failure on the uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1403
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Times
of
Abnor
mal
Downli
nk TBF
Release
[0,
+)
Num
ber
Number of abnormal TBF releases on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
s of
Abnor
mal
Downli
nk TBF
Release
N/A
N/A
Cause of an abnormal TBF release on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1404
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Carrie
r Index
N/A
N/A
Carrier of an abnormal TBF release on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BCCH
N/A
N/A
BCCH of an abnormal TBF release on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1405
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Times
of
Abnor
mal
Uplink
TBF
Release
[0,
+)
Num
ber

uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
s of
Abnor
mal
Uplink
TBF
Release
N/A
N/A

uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1406
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Carrie
r Index
N/A
N/A

uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BCCH
N/A
N/A

uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1407
Nastar
Latency Sensitivity Information

Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Downli
nk PDU
N/A
N/A
Information about the downlink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Sent
Bytes
[0,
+)
Byte
Size of the data transmitted by using the

downlink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1408
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Maxi
mum
Duratio
n on
Sendin
g PDU
[0,
+)
Seco
nd
Maximum duration for data transmission by

using the downlink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Total
Duratio
n on
Sendin
g PDU
[0,
+)
Seco
nd
Overall duration for data transmission by

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1409
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Sent
Count
[0,
+)
Num
ber
Total number of the blocks transmitted by

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Avera
ge
Duratio
n on
Sendin
g PDU
[0,
+)
Seco
nd
Average duration for data transmission by

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1410
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Sendi
ng
Timeou
t Times
[0,
+)
Num
ber
Number of times that the duration for data

exceeds the predefined threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
A device is configured to directly check

whether the duration for data transmission by
using the PDU exceeds the predefined
threshold.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink
PDU
N/A
N/A
Information about the uplink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1411
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Recei
ved
Bytes
[0,
+)
Byte

uplink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Maxi
mum
Duratio
n on
Receivi
ng PDU
[0,
+)
Seco
nd

using the uplink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1412
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Total
Duratio
n on
Receivi
ng PDU
[0,
+)
Seco
nd

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Recei
ved
Count
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1413
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Avera
ge
Duratio
n on
Receivi
ng PDU
[0,
+)
Seco
nd

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Recei
ving
Timeou
t Times
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

threshold.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1414
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Uplink/
Downli
nk PDU
N/A
N/A
Information about the uplink and downlink

PDUs, namely, the information about the
incoming and outgoing data transmission on
the PDU GB interfaces.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Maxi
mum
Interval
Duratio
n
[0,
+)
Seco
nd
Maximum interval for data transmission

between the uplink and downlink PDUs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1415
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Total
Interval
Duratio
n
[0,
+)
Seco
nd
Aggregated interval of all the intervals for

data transmission between every two datatransmission time points on the uplink and
downlink PDUs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Numb
er of
Interval
s
[0,
+)
Num
ber
Number of times that an interval for data

downlink PDUs is available.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1416
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Avera
ge
Interval
Duratio
n
[0,
+)
Seco
nd
Average interval for data transmission

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Numb
er of
Interval
Timeou
ts
[0,
+)
Num
ber
Number of times that the interval for data

downlink PDUs exceeds the predefined
threshold.
whether the interval for data transmission
between the uplink and downlink PDUs
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1417
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Uplin
k Data
Availab
le and
Downli
nk Data
Unavail
able
Occurre
nce
Times
[0,
+)
Num
ber
Number of times that the uplink PDU carries

data but downlink PDU does not.
l SRAN8.0/
GBSS15.0/
RAN 15.0

whether the uplink PDU carries data while
the downlink PDU does not.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Numbe
r of No
Service
Interact
ion
Timeou
t Times
[0,
+)
Num
ber
Number of times that no service interaction

responses.
response to service interaction, and,
obtained by using the following formula, is
larger than the exception threshold 2 for the
service interaction is made indicates a value
of 1; otherwise, it indicates a value of 0.(A =
data but the downlink PDU does not).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1418
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Numbe
r of
Service
Interact
ion
Timeou
t Times
[0,
+)
Num
ber
Number of exceptions where the response to

service interaction is overdue during the
whole process for a VIP subscriber to use a
data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Number of Number of Interval Timeouts for
data transmission between the uplink and
downlink PDUs.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Averag
e
Duratio
n on
Service
Interact
ion
Respon
se
[0,
+)
Num
ber
Average duration for the response to service

interaction during the whole process for a
l SRAN8.0/
GBSS15.0/
RAN 15.0

interaction = Average duration for data
Average duration for data reception by using
the uplink PDU + Average duration for data
downlink PDUs.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1419
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Overlo
ng
Averag
e
Duratio
n on
Service
Interact
ion
Respon
se
Yes
N/A
Number of exceptions where the average

duration for the response to service
interaction exceeds the predefined threshold
during the whole process for a subscriber to
use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No
If the average duration for the response to

threshold for the average duration for the
response to service interaction, the average
interaction overlong.
The threshold is set by engineers during
analysis task creation.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1420
Nastar
Speed Sensitivity Information

Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Statistic
s on
Downli
nkRateSensitiv
e
Service
s
N/A
N/A
Information about the statistics on downlink

rate-sensitive services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>PDU
Bytes
Sent at
Downli
nk
[0,
+)
Byte

downlink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1421
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Durati
on for
Sendin
g PDU
at
Downli
nk
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>PDU
Bytes
Receive
d at
Uplink
[0,
+)
Byte
Size of the data received by using the uplink

PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1422
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Down
load
Speed
(kbit/s)
[0,
+)
kbit/s
Average download rate during the whole

process for a subscriber to use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Download rate = Number of bytes

transmitted by using the downlink PDU/
Duration for data transmission by using the
downlink PDU
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Low
Downlo
ad
Speed
Yes
No
N/A
Number of low download rate exceptions

use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If a download rate is lower than the lower

threshold for download rate,
l SRAN8.1/
GBSS15.1/
RAN 15.1
the download rate is low.

The threshold is set by engineers when
creating tasks.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1423
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Numb
er of
Downli
nk NU
Out-ofOrder
Times
[0,
+)
Num
ber
Number of exceptions where downlink NU

disorder occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Numb
er of
Downli
nk TCP
Out-ofOrder
Times
[0,
+)
Num
ber
Number of exceptions where downlink TCP

disorder occurs during the whole process for
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1424
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Avera
ge
Occupi
ed
Downli
nk Slots
[1,6]
Num
ber
Number of timeslots occupied during

downlink data transmission.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Down
load
MultiSlot
Statisfa
ction
Ratio
[0.00,
100.0
0]
Multislot satisfaction rate on the downlink =

Average number of timeslots occupied by the
downlink/Multislot Class of a Terminal x
100%
The method for calculating the multislot class
of a Terminal is as follows:
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/
Supporting GPRS.
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1425
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Trans
mission
Resour
ces
Require
d for
Code
Request
ed by
Downli
nk
Block
[0,
+)
Num
ber
Number of transmission resources requested

for the encoding of downlink blocks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Trans
mission
Resour
ces
Used by
Code
Assigne
d to
Downli
nk
Block
[0,
+)
Num
ber
Number of transmission resources actually

used for the encoding of downlink blocks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1426
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Resou
rce
Statisfa
ction
Ratio of
Downli
nk
Averag
e
SingleSlot
Throug
hput
(%)
[0.00,
100.0
0]
Transmission-resource satisfaction rate at the

average downlink single-slot throughput =
Number of the transmission resources
actually used for the encoding of downlink
blocks/Number of the transmission resources
requested for the encoding of downlink
blocks x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>GPRS
Service
Flag
N/A
N/A
Information about the data service that a VIP

subscriber uses through GPRS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1427
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Downli
nk
CS1~4
Blocks/
Valid
Blocks
[0,
+)
Num
ber
Total number of the blocks, and that of the

valid blocks, transmitted on the downlink by
using channel coding schemes CS-1 through
CS-4.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Total
Blocks
Sent at
Downli
nk
[0,
+)
Num
ber
Total number of the blocks transmitted on the

downlink
= Total number of the blocks transmitted on
the downlink by using various channel
coding schemes
= Number of the blocks transmitted on the
downlink by using CS-1 ++ Number of
the blocks transmitted on the downlink by
using CS-4
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1428
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Total
Valid
Blocks
Sent at
Downli
nk
[0,
+)
Num
ber
Total number of the valid blocks transmitted

on the downlink
l SRAN8.0/
GBSS15.0/
RAN 15.0
= Total number of the valid blocks

transmitted on the downlink by using various
channel coding schemes
= Number of the valid blocks transmitted on
the downlink by using CS-1 ++ Number
of the valid blocks transmitted on the
downlink by using CS-4
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Total
Bytes
of Valid
Blocks
Sent at
Downli
nk
Issue 03 (2015-07-30)
[0,
+)
Byte
Total number of the bytes contained in the

valid blocks transmitted on the downlink
coding schemes x Number of the bytes
contained in one valid block
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1

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
l SRAN9.0/
GBSS16.0/
RAN16.0
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.
l SRAN10.1/
GBSS17.1/
RAN17.1

l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
1429
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Dow
nlink
Retrans
mission
Ratio
[0.00,
100.0
0]
Downlink data-retransmission rate = Total

number of the valid blocks transmitted on the
downlink/Total number of the blocks
transmitted on the downlink
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Dow
nlink
Reuse
Ratio
[0.00,
+)
N/A
Downlink timeslot reuse = Overall duration

for data transmission by using the downlink
PDU x Average number of the timeslots
occupied by the downlink/2/Total number of
the blocks transmitted on the downlink
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1430
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>EGDE
Service
Flag
N/A
N/A

subscriber uses through EGDE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Downli
nk
MCS1~
9
Blocks/
Valid
Blocks
[0,
+)
Num
ber

using modulation and coding schemes
MCS-1 through MCS-9.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1431
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Total
Blocks
Sent at
Downli
nk
[0,
+)
Num
ber

downlink
l SRAN8.0/
GBSS15.0/
RAN 15.0

the downlink by using various modulation
and coding schemes
downlink by using MCS-1 ++ Number
of the blocks transmitted on the downlink by
using MCS-9
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Total
Valid
Blocks
Sent at
Downli
nk
[0,
+)
Num
ber

on the downlink
modulation and coding schemes
the downlink by using MCS-1 ++
downlink by using MCS-9
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1432
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Total
Bytes
of Valid
Blocks
Sent at
Downli
nk
[0,
+)
Byte

l SRAN8.0/
GBSS15.0/
RAN 15.0
>>Dow
nlink
Retrans
mission
Ratio

and coding schemes x Number of the bytes
[0.00,
100.0
0]
l SRAN8.1/
GBSS15.1/
RAN 15.1

the downlink by using MCS-1 x Number of
the bytes contained in one valid block +
+ Number of the valid blocks transmitted on
the bytes contained in one valid block
l SRAN9.0/
GBSS16.0/
RAN16.0

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.
l SRAN10.1/
GBSS17.1/
RAN17.1

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1433
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Dow
nlink
Averag
e
GMSK
BEP
[0,31
]
N/A
Average downlink GMSK BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Dow
nlink
Averag
e 8PSK
BEP
[0,31
]
N/A
Average downlink 8PSK BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1434
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Dow
nlink
Averag
e BEP
[0,31
]
N/A
1. If both the average downlink GMSK BEP

and the average downlink 8PSK BEP are
valid,
l SRAN8.0/
GBSS15.0/
RAN 15.0
use the average downlink GMSK BEP with a

higher order.
l SRAN8.1/
GBSS15.1/
RAN 15.1
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.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Dow
nlink
Averag
e
SingleSlot
Throug
hput
N/A
kbit/s
You can obtain the maximum single-slot rate,

namely, the average downlink single-slot
throughput, in BEP-Coding Scheme-Rate
Mapping Table based on the average
downlink BEP.
The BEP-Coding Scheme-Rate Mapping
Table is generated by an NE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1435
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Um
Quality
Satisfac
tion
Ratio of
Downli
nk
Averag
e
SingleSlot
Throug
hput
[0.00,
100.0
0]
Um-interface quality satisfaction rate at the

MIN (Average downlink single-slot
throughput/Target single-slot throughput x
100%, 100%)
l SRAN8.0/
GBSS15.0/
RAN 15.0
The target single-slot throughput is a

customized algorithm parameter.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Poor
Transm
ission
Quality
Indicate
d by
Downli
nk
Averag
e
SingleSlot
Throug
hput
Yes
No
N/A
If the average downlink BEP is higher than

the BEP required by the lowest-level coding,
and at the same time, the downlink dataretransmission rate is higher than the upper
threshold for downlink data-retransmission
rate,
l SRAN8.0/
GBSS15.0/
RAN 15.0
the transmission quality at the average

downlink single-slot throughput is poor.
l SRAN9.0/
GBSS16.0/
RAN16.0
The BEP required by the lowest-level coding

and the upper threshold for downlink dataretransmission rate are customized algorithm
parameters.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1436
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Dow
nlink
Reuse
Ratio
[0.00,
+)
N/A

PDU x Average number of downlink
timeslots/2/Total number of the blocks
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Statistic
s on
UplinkRateSensitiv
e
Service
s
N/A
N/A
Information about the statistics on uplink

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1437
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>PDU
Bytes
Receive
d at
Uplink
[0,
+)
Byte

PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Durati
on for
Receivi
ng PDU
at
Uplink
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1438
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>PDU
Bytes
Sent at
Downli
nk
[0,
+)
Byte

downlink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Uploa
d Speed
(kbit/s)
[0,
+)
kbit/s
Average upload rate during the whole process

for a subscriber to use a data service.
Upload rate = Number of bytes transmitted
by using the uplink PDU/Duration for data
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1439
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Low
Upload
Speed
Yes
N/A
Number of low upload rate exceptions during

the whole process for a subscriber to use a
data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If an upload rate is lower than the lower

threshold for upload rate,
l SRAN8.1/
GBSS15.1/
RAN 15.1
No
the upload rate is low.

creating tasks.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Numb
er of
Uplink
NU
Out-ofOrder
Times
[0,
+)
Num
ber
Number of exceptions where uplink NU

disorder occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1440
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Numb
er of
Uplink
TCP
Out-ofOrder
Times
[0,
+)
Num
ber
Number of exceptions where uplink TCP

disorder occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Avera
ge
Occupi
ed
Uplink
Slots
[1,6]
Num
ber
Number of timeslots occupied during uplink

data transmission.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1441
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Uplin
k MultiSlot
Statisfa
ction
Ratio
[0.00,
100.0
0]
Uplink multislot-satisfaction rate = Average

number of timeslots occupied by the uplink/
Multislot Class of a Terminal x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
Uplink Rate-Sensitive Service/EGDE
Supporting EGPRS.
Supporting GPRS.
>Trans
mission
Resour
ces
Require
d for
Code
Request
ed by
Uplink
Block
[0,
+)
Num
ber

for the encoding of uplink blocks.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1442
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Trans
mission
Resour
ces
Used by
Code
Assigne
d to
Uplink
Block
[0,
+)
Num
ber

used for the encoding of uplink blocks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Resou
rce
Statisfa
ction
Ratio of
Uplink
Averag
e
SingleSlot
Throug
hput
(%)
[0.00,
100.0
0]

average uplink single-slot throughput
= Number of transmission resources actually
used for the encoding of uplink blocks/
for the encoding of uplink blocks x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1443
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Durati
on for
Sendin
g PDU
at
Downli
nk
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Total
Duratio
n for
Sendin
g PDU
at
Downli
nk
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1444
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>PDUs
Sent at
Downli
nk
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Timeo
ut
Times
on
sending
PDUs
at
Downli
nk
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

threshold.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1445
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>GPRS
Service
Flag
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Uplink
CSN
(1~4)
Blocks/
Valid
Blocks
[0,
+)
Num
ber

valid blocks, transmitted on the uplink by
CS-4.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1446
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Total
Blocks
Receive
d at
Uplink
[0,
+)
Num
ber

uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0

the uplink by using various channel coding
schemes
uplink by using CS-1 ++ Number of the
blocks transmitted on the uplink by using
CS-4
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Total
Valid
Blocks
Receive
d at
Uplink
[0,
+)
Num
ber

on the uplink
transmitted on the uplink by using various
the uplink by using CS-1 ++ Number of
the valid blocks transmitted on the uplink by
using CS-4
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1447
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Total
Bytes
of Valid
Blocks
Receive
d at
Uplink
[0,
+)
Byte

valid blocks transmitted on the uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0
>>Upli
nk
SingleSlot
Throug
hput
(Actual
)

schemes x Number of the bytes contained in
one valid block
[0.00,
100.0
0]
kbit/s
l SRAN8.1/
GBSS15.1/
RAN 15.1

the uplink by using CS-1 x Number of the
uplink by using CS-4 x Number of the bytes
l SRAN9.0/
GBSS16.0/
RAN16.0

TS 44.060-10.2.
l SRAN10.1/
GBSS17.1/
RAN17.1
Uplink single-slot throughput (Actual)
l SRAN8.0/
GBSS15.0/
RAN 15.0
Uplink single-slot throughput = Total number

of the bytes contained the valid blocks
received on the uplink x 8 x 50/1000/Total
number of the blocks received on the uplink
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1448
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Reuse
Ratio
[0.00,
+)
N/A
Uplink timeslot reuse = Overall duration for

data reception by using the uplink PDU x
Average number of the timeslots occupied by
the uplink/2/Total number of the blocks
received on the uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>EGDE
Service
Flag
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1449
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Uplink
MCS1~
9
Blocks/
Valid
Blocks
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Total
Blocks
Receive
d at
Uplink
[0,
+)
Num
ber

uplink
the uplink by using various modulation and
coding schemes
uplink by using MCS-1 ++ Number of
the blocks transmitted on the uplink by using
MCS-9
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1450
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Total
Valid
Blocks
Receive
d at
Uplink
[0,
+)
Num
ber

on the uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0

the uplink by using MCS-1 ++ Number
of the valid blocks transmitted on the uplink
by using MCS-9
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Total
Bytes
of Valid
Blocks
Receive
d at
Uplink
Issue 03 (2015-07-30)
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1

the uplink by using MCS-1 x Number of the
uplink by using MCS-9 x Number of the bytes
l SRAN9.0/
GBSS16.0/
RAN16.0

3GPP TS 44.060-10.3.
l SRAN10.1/
GBSS17.1/
RAN17.1

l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
1451
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Receive
Retrans
mission
Rate
(%)
[0.00,
100.0
0]
Uplink data-retransmission rate = Total

uplink/Total number of the blocks
transmitted on the uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Upli
nk
Averag
e
GMSK
BEP
[0,31
]
N/A
Average uplink GMSK BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1452
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Averag
e 8PSK
BEP
[0,31
]
N/A
Average uplink 8PSK BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Upli
nk
Averag
e BEP
[0,31
]
N/A
1. If both the average uplink GMSK BEP and

the average uplink 8PSK BEP are valid,
use the average uplink GMSK BEP with a
higher order.
2. If either the average uplink GMSK BEP or
the average uplink 8PSK BEP is valid,
uplink BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1453
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Averag
e
SingleSlot
Throug
hput
Require
d for
Um
Quality
[0.00,
100.0
0]
kbit/s
Average uplink single-slot throughput

required to achieve a specific quality level on
the Um interface.
l SRAN8.0/
GBSS15.0/
RAN 15.0

namely, the average uplink single-slot
Mapping Table based on the average uplink
BEP.
l SRAN8.1/
GBSS15.1/
RAN 15.1

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1454
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Um
Quality
Unsatis
faction
Times
of
Downli
nk
Averag
e
SingleSlot
Throug
hput
[0,
+)
Num
ber
1 Obtain a coding scheme from BEP-Coding

Scheme-Rate Mapping Table based on the
average uplink BEP. Then record it as
Average coding scheme_Average uplink
BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Obtain the coding scheme used for collecting

the total number of the blocks actually
received on the uplink, based on the total
number of the blocks received on the uplink.
Then record it as Average coding
scheme_Number of the blocks actually
received on the uplink.
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)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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
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 03 (2015-07-30)

1455
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Poor
Transm
ission
Quality
Indicate
d by
Uplink
Averag
e
SingleSlot
Throug
hput
Yes
N/A
If the average uplink BEP is higher than the

BEP required by the lowest-level coding,
and,
l SRAN8.0/
GBSS15.0/
RAN 15.0
at the same time, the uplink dataretransmission rate is higher than the upper
threshold for uplink data-retransmission rate,
l SRAN8.1/
GBSS15.1/
RAN 15.1

l SRAN9.0/
GBSS16.0/
RAN16.0
No

and the upper threshold for uplink datareception-and-retransmission rate are
internal algorithm parameters.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Upli
nk
SingleSlot
Throug
hput
(Actual
)
[0,10
0]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1456
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Reuse
Ratio
[0.00,
+)
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1457
Nastar
Summary Information
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Total
Traffic
at
Downli
nk
[0,
+)
Byte
Total downlink traffic during the whole

l SRAN8.0/
GBSS15.0/
RAN 15.0

the Bytes Transmitted by Using the
Downlink PDU
Uplink Rate-Sensitive Service/Number of
Downlink PDU
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Traffic
at
Uplink
[0,
+)
Byte
Total uplink traffic during the whole process

PDU
PDU
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1458
Nastar

Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Number
[1,
+)
N/A
Unique number for the signaling message that

a VIP subscriber sends and receives during
the signaling procedure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signali
ng Time
N/A
N/A
Time when a signaling message is sent or

received.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1459
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Signali
ng
Direct
Uplin
k
N/A
Direction in which a signaling message is sent

or received.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Dow
nlink
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signali
ng Type
N/A
N/A
Type of a signaling message transmitted on

the A, Abis, GB, or PTP interface during the
signaling procedure. For example, the
parameter can be an Immediate Assignment
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1460
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Signali
ng
Content
N/A
N/A
Content of a signaling message. You can

obtain the content of a signaling message by
viewing the related tree structure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1461
Nastar
Measurement Information
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Number
[1,
+)
N/A
Unique number of a signaling message

carrying a measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Time
N/A
N/A
Time when a measurement report is

submitted.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1462
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
MR
Type
2G
NC
MR
N/A
Type of a measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
3G
MR
l SRAN8.1/
GBSS15.1/
RAN 15.1
EUTRA
N MR
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measure
ment
Object
Type
Server
Nbr1~
6
N/A
Type of a measurement object reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
For example, if the parameter is Server, the

measurement object is a serving cell; if the l SRAN8.1/
parameter is Nbr1, the measurement object
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1463
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Measure
ment
Object
N/A
N/A
name of a measurement object reported in

l SRAN8.0/
GBSS15.0/
RAN 15.0

format: name of the BSC: name of the cell.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BCCH
[0,102
3]
N/A
BCCH of a neighboring cell on 2G network,

reported in a measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1464
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
BSIC
[0,77]
N/A
BSIC of a neighboring cell on 2G network,

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RxLevel
(DL)
[-110,47]
dBm
Downlink RxLevel of a serving cell and that

of a neighboring cell on 2G network,
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1465
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Frequen
cy
[0,102
3]
N/A
Frequency on 3G network, reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
P-SC
[0,512
]
N/A
Primary scrambling code on 3G networkl,

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1466
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
RSCP
[-116,25]
dBm
RSCP on 3G networkl, reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Frequen
cy
[0,102
3]
N/A
Frequency on LTE network, reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1467
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
PCI
[0,503
]
N/A
Primary scrambling code on LTE networkl,

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RSRP
[-140,43]
dBm
RSCP on LTE networkl, reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1468
Nastar
Mobility Analysis
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Number
[1,
+)
N/A
Number.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
N/A
N/A
If the time interval is above the exception

threshold for cell reselection,
the cell reselection fails and an exclamation
mark ! is displayed.
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1469
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Abnorm
al Cause
Overlo
ng
time of
cell
reselec
tion
(Durati
on)
N/A

threshold for cell reselection, it displays
"Overlong time of cell reselection
(Duration)".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Type
Cell
Resele
ction
N/A
Type of a mobility analysis, namely, cell

reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1470
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
End
Time
N/A
N/A
Time when a cell reselection ends.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Source
Cell
N/A
N/A
Source cell for a cell reselection.

format: BSC Name: Cell Name (Cell ID).
You can obtain the names of the BSC and
the cell based on the internal ID of the BSC
and the ID of the cell. The names are not
displayed if they are not available.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1471
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Reselect
RxQuali
ty
[0,7]
N/A
RxQulity of the source cell for a cell

reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Reselect
GMSK
MEAN
BEP
[0,31]
N/A
GMSK MEAN BEP of the source cell for a

cell reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1472
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Reselect
8PSK
MEAN
BEP
[0,31]
N/A
8PSK MEAN BEP of the source cell for a

cell reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
Cell
N/A
N/A
Target cell for a cell reselection.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1473
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Access
RxQuali
ty
[0,7]
N/A
RxQulity of the target cell for a cell

reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
GMSK
MEAN
BEP
[0,31]
N/A
GMSK MEAN BEP of the target cell for a

cell reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1474
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Access
8PSK
MEAN
BEP
[0,31]
N/A
8PSK MEAN BEP of the target cell for a

cell reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

(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.
Issue 03 (2015-07-30)

1475
Nastar
Summary
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Serial
Numbe
r
[1,2^31-1)
N/A
Serial number of a CHR in the Overview

Table. Serial number is a keyword of a
call record. It is an internal identification
in the Nastar and can uniquely identify
a call record.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Combi
ned
N/A
N/A
Whether a CHR is combined.

The Nastar supports the combination of
inter-RNC CHRs. If a yellow icon is
displayed in this column, the CHR is
combined.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1476
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Status
N/A
Whether a call record is abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Blank
If a red exclamation mark is 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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnor
mal
Cause
For details,
see
"Appendix:
Exception
Cause
Classificatio
n/
Enumeration
Values of
Failure Cause
(UMTS)".
N/A
Exception cause of a call.

Remark: For the access counters such as
TP, Ec/No, RSCP, if the active set
contains multiple cells during access,
only the counters for the first cell in this
active set are analyzed.
The Nastar collects statistics on the
number of each of the following types
of exceptions occuring during calls:
uplink one-way audio, downlink oneway audio, and garble noise.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1477
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Networ
k
UMTS
N/A
Network that a call accesses.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Type
Static reloc
in
N/A
Same as Access Information -> RRC

Setup Type.
HHO reloc
in
Cell update
reloc in
Inter RAT
handover in
RRC setup
without DRD
RRC setup
with DRD
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1478
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Access
Cause
Originating
Conversation
al Call
N/A

Setup Cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Originating
Streaming
Call
l SRAN8.1/
GBSS15.1/
RAN 15.1
Originating
Interactive
Call
l SRAN9.0/
GBSS16.0/
RAN16.0
Originating
Background
Call
l SRAN10.0/
GBSS17.0/
RAN17.0
Originating
Subscribed
traffic Call
l SRAN10.1/
GBSS17.1/
RAN17.1
Terminating
Conversation
al Call
l SRAN11.0/
GBSS18.0/
RAN18.0
Terminating
Streaming
Call
Terminating
Interactive
Call
Terminating
Background
Call
Emergency
Call
Inter-RAT
cell reselection
Inter-RAT
cell change
order
Registration
Detach
Originating
High Priority
Signaling
Issue 03 (2015-07-30)

1479
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
N/A

Request Time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Originating
Low Priority
Signaling
Call reestablishmen
t
Terminating
High Priority
Signaling
Terminating
Low Priority
Signaling
Terminating
- cause
unknown
MBMS
reception
MBMS ptp
RB request
Start
Time
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1480
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Access
Cell
1 to 64
characters
N/A
Same as Access Information -> Cell on

RRC Setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
End
Time
N/A
N/A
Same as Release Information -> RRC

Release Time
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1481
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Release
Cell
1 to 64
characters
N/A

Release Cell
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User
ID:Alia
s
N/A
N/A
User ID, which is created by the system

when creating the task.
Alias, which is created by the user when
creating the task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1482
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
IMSI
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

information.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMEITAC
00000000-99
999999
N/A
First eight digits in the IMEI of a UE.

IMEI is international mobile equipment
identity for short and TAC is type
approval code for short.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1483
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Termin
al
Model
N/A
N/A
Model of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The UE model can be queried using

terminal type management based on the
IMEI-TAC of the UE.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Duratio
n
[0,+)
Seco
nd
Duration of a call, including service

duration and signaling duration.
Call duration = End time - Start time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1484
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
CS
Reques
ted
Service
Type
AMR
N/A
Statistics on the types of CS service

requested by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
VP
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CS
Service
Duratio
n
[0,+)
Seco
nd
Statistics on the duration of CS services

used by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1485
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
PS
Reques
ted
Service
Type
PS R99
N/A
Statistics on the types of PS service

requested by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
HSDPA
HSUPA
l SRAN8.1/
GBSS15.1/
RAN 15.1
HSPA
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PS
RAB
Duratio
n
[0,+)
Seco
nd
Statistics on the duration of PS services

used by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1486
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Failure
Cause
For details,
see "Access
information/
RRC Setup
Failure
Cause".
N/A
For details, see "Access information/

RRC Setup Failure Cause".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IU
Release
Cause
N/A
N/A
Cause of signaling release of a call.

The value of this parameter is carried in
the IU RELEASE REQUEST message.
For details, see 3GPP 25.413 - 9.1.6.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1487
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Cause
for CS
RAB
Setup
Failure
N/A
N/A
Cause of CS RAB setup or release

failure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
This parameter contains information in

following levels: exception type,
exception causes of an exception type.
the RAB ASSIGNMENT RESPONSE
message for the Iu interface. For details,
see 3GPP 25.413 - 9.1.4.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cause
for CS
RAB
Release
Failure
N/A
N/A

failure.
see 3GPP 25.413 - 9.1.4.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1488
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Cause
for PS
RAB
Setup
Failure
N/A
N/A
Cause of PS RAB setup or release

failure.
l SRAN8.0/
GBSS15.0/
RAN 15.0

see 3GPP 25.413 - 9.1.4.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cause
for PS
RAB
Release
Failure
N/A
N/A

failure.
see 3GPP 25.413 - 9.1.4.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1489
Nastar
User Information
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
TMSI/
PTMSI
0000000-FFFFFFFF
N/A
Temporary mobile subscriber

identity (TMSI) or packet
temporary mobile subscriber
identify (P-TMSI) of a UE
assigned by the network in the
CS domain or PS domain.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User
ID:Alia
s
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1490
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMEITAC
00000000-99999999
N/A
First eight digits in the IMEI of

a UE.
IMEI is international mobile
equipment identity for short and
TAC is type approval code for
short.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1491
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Termin
al
Model
N/A
N/A
Model of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The UE model can be queried

using terminal type management
UE.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
UE
Capabil
ity
N/A
N/A
Capability of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1492
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Proto
col
Versio
n
REL-99
N/A
3GPP version with which a UE

complies.
l SRAN8.0/
GBSS15.0/
RAN 15.0
REL-4 ~ REL-20
later than REL-20
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Power
Class
[1,4]
N/A
Power class of a UE.

For details, see "A UE with UE
power class 3bis signals the
value 3" under "UE Radio
Transmission and Reception
(FDD)" in 3GPP TS 25.101.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1493
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Suppo
rt
UTRA
Band
Band I
N/A
Universal Terrestrial Radio

Access (UTRA) frequency
bands supported by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
For details, see Table 5.0

"UTRA FDD frequency bands"
under "UE Radio Transmission
and Reception (FDD)" in 3GPP
TS 25.101.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Band II
Band III
Band IV
Band V
Band VI
Band VII
Band VIII
Band IX
Band X
Band XI
Band XII
Band XIII
Band XIV
Band XV
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Band XVI
Band XVII
Band XVIII
Band XIX
Band XX
Band XXI
Band XXII
Reserved
Issue 03 (2015-07-30)

1494
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>HSPA
Capabil
ity
N/A
N/A
HSPA capability of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>HSDSCH
Capabil
ity
[1,64]
N/A
HSDPA capability of a UE. A

larger value of this parameter
indicates larger HSDPA
capability.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1495
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>>EDCH
Capabil
ity
[1,16]
N/A
HSUPA capability of a UE. A

indicates larger HSUPA
capability.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Sup
port ERACH
supported
unsupported
N/A
Whether a UE supports ERACH.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1496
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>>Sup
port EFACH
supported
N/A
Whether a UE supports EFACH.
l SRAN8.0/
GBSS15.0/
RAN 15.0
unsupported
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Sup
port
DTXD
RX
supported
unsupported
N/A
Whether a UE supports
discontinuous transmission
(DTX) and discontinuous
reception (DRX).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1497
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>>Sup
port
HSSCCH
Less
Operati
on
supported
N/A
Whether a UE supports HSSCCH.
l SRAN8.0/
GBSS15.0/
RAN 15.0
unsupported
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1498
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Mobil
ity
Capabil
ity
Support of GSM
N/A
Mobility capability of a UE. For

example, "Support of Inter-RAT
PS handover" indicates whether
a UE supports inter-RAT
handover in the PS domain.
l SRAN8.0/
GBSS15.0/
RAN 15.0
GSM450
GSM480
GSM850
GSM900P
GSM900E
GSM1800
GSM1900
Support of InterRAT PS handover
Support for lossless
SRNS relocation
Support of E-UTRA
FDD
Support of InterRAT PS Handover to
E-UTRA FDD
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Support of UTRAN
to GERAN NACC
Support of Handover
to GAN
Support of PS
Handover to GAN
Reserved
Issue 03 (2015-07-30)

1499
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Suppo
rt EUTRA
Band
Capabil
ity
Support Band 1
N/A
Evolved Universal Terrestrial

Radio Access (E-UTRA)
frequency bands supported by a
UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
......
Support Band 64
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Positi
oning
Capabil
ity
Standalone location
method(s) supported
N/A
Positioning capability of a UE.
UE based OTDOA
supported
l SRAN8.0/
GBSS15.0/
RAN 15.0
GANSS support
indication
l SRAN8.1/
GBSS15.1/
RAN 15.1
Support for GPS

timing of cell frames
measurement
l SRAN9.0/
GBSS16.0/
RAN16.0
Support for IPDL
l SRAN10.0/
GBSS17.0/
RAN17.0
Support for Rx-Tx

time difference type2
measurement
Support for UP
assisted GPS
measurement validity
in CELL_PCH and
URA_PCH states
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Support for SFNSFN observed time

difference type 2
measurement
Network Assisted
GPS support
Issue 03 (2015-07-30)

1500
Nastar
Access Information
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Request
Time
N/A
N/A
Time of signaling access during a

call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
That is, timestamp in the RRC

CONNECTION SETUP message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Radio
Link
Setup
Time
N/A
N/A
Time of RRC radio link setup

during a call. That is, timestamp in
the RADIO LINK SETUP
REQUEST message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1501
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Cell on
RRC
Setup
N/A
N/A
Name of the cell to which

signaling accesses.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The parameter value is displayed

in the following format: RNC
name:cell name (RNCID:cell ID).
The RNC name and cell name can
be obtained from configuration
data. If the RNC name and cell
name cannot be queried, they are
not displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DRD
Target
Cell on
RRC
Setup
N/A
N/A
Target cell of Directed Retry

Decision (DRD) during signaling
access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Note that when DRD occurs

during signaling access, statistics
on accessibility counters are
collected under the DRD target
call instead of under the RRC
setup cell. A example of such
counter is the number of
successful accesses and failed
accesses under a cell.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1502
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Status
SRB on
FACH_RACH
N/A
RRC status after RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
SRB on
DCH_DCH
l SRAN8.1/
GBSS15.1/
RAN 15.1
SRB on
HSDSCH_RACH
l SRAN9.0/
GBSS16.0/
RAN16.0
SRB on
HSDPA_DCH
SRB on
DCH_HSUPA
l SRAN10.0/
GBSS17.0/
RAN17.0
SRB on
HSDPA_HSUPA
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Setup
Type
Static reloc in
HHO reloc in
Cell update reloc
in
Inter RAT
handover in
RRC setup
without DRD
RRC setup with
DRD
N/A
Value of RRC Connection Setup

Type carried in the RRC
CONNECTION SETUP message:
l SRAN8.0/
GBSS15.0/
RAN 15.0
Incoming migration (Static reloc

in)
l SRAN8.1/
GBSS15.1/
RAN 15.1
Incoming migration (HHO reloc

in): The first radio link is set up
after the Iu interface sends the
migration request.
Incoming migration (Cell update
reloc in)
(Inter RAT handover in)
RNC access (RRC setup without
DRD)
RNC access (RRC setup with
DRD)
Issue 03 (2015-07-30)

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1503
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Cause
Originating
Conversational
Call
N/A
Cause of RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Originating
Streaming Call
For details, see 3GPP TS

25.331-10.3.3.11 "Establishment
cause."
Originating
Interactive Call
l SRAN8.1/
GBSS15.1/
RAN 15.1
Originating
Background Call
l SRAN9.0/
GBSS16.0/
RAN16.0
Originating
Subscribed traffic
Call
l SRAN10.0/
GBSS17.0/
RAN17.0
Terminating
Conversational
Call
l SRAN10.1/
GBSS17.1/
RAN17.1
Terminating
Streaming Call
l SRAN11.0/
GBSS18.0/
RAN18.0
Terminating
Interactive Call
Terminating
Background Call
Emergency Call
Inter-RAT cell reselection
Inter-RAT cell
change order
Registration
Detach
Originating High
Priority Signaling
Originating Low
Priority Signaling
Call reestablishment
Terminating High
Priority Signaling
Terminating Low
Priority Signaling
Terminating cause unknown
MBMS reception
Issue 03 (2015-07-30)

1504
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
N/A
Whether RRC setup is triggered

by service or non-service causes
based on RRC Setup Cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The rules for determining the

trigger conditions are as follows:
l SRAN8.1/
GBSS15.1/
RAN 15.1
MBMS ptp RB
request
RRC
Setup
Flag
(Servic
e/NonService
)
Service
Non-service
1. RRC setup is triggered by nonservice causes when the following

conditions are met:
The value of RRC Setup Cause is
any of the following:
@Inter-RAT cell re-selection
@Inter-RAT cell change order
@Registration
@Detach
There is no RAB information in
this call record.
2. Otherwise, RRC setup is
triggered by service causes.
RRC
Setup
Flag
(CS
Domain
/PS
Domain
)
CS
PS
N/A
Whether RRC setup occurs in the

CS or PS domain based on RRC
Setup Cause.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1505
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Flag
(MOC/
MTC)
MOC
N/A
Whether RRC setup occurs on the

MOC or MTC side based on RRC
Setup Cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0

occurrence conditions are as
follows:
l SRAN8.1/
GBSS15.1/
RAN 15.1
1. RRC setup occurs on the MOC

side when the value of RRC Setup
Cause is any of the following:
l SRAN9.0/
GBSS16.0/
RAN16.0
Originating Conversational Call
l SRAN10.0/
GBSS17.0/
RAN17.0
MTC
Blank
Originating Streaming Call

Originating Interactive Call
Originating Background Call
Originating Subscribed traffic
Call
Originating High Priority
Signaling
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Originating Low Priority

Signaling
Emergency Call
2. RRC setup occurs on the MTC
Terminating Conversational Call
Terminating Streaming Call
Terminating Interactive Call
Terminating Background Call
Terminating High Priority
Signaling,
Terminating Low Priority
Signaling,
Terminating - cause unknown
3. The value of this parameter is
empty when the value of RRC
Setup Cause contains other
information.
Issue 03 (2015-07-30)

1506
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Flag
(SMS/
NonSMS)
SMS
N/A

by SMS or non-SMS causes based
on RRC Setup Cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
No-SMS
1. RRC setup is triggered by SMS

causes when the value of RRC
Setup Cause is any of the
following:
Signaling
Signaling
triggered by non-SMS causes.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Setup
Results
Successful
N/A
Results of RRC setup.
Failed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1507
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Failure
Cause
N/A
N/A
Cause of RRC setup failure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error Type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1508
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error Reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Setup
Time
Info
N/A
N/A
Time information on RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1509
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>RRC
Setup
Delay
[0,+)
Seco
nd
Delay on RRC setup. The

statistical points are as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0
RRC setup: Timestamp in the

RRC CONNECTION REQUEST
message - Timestamp in the RRC
CONNECTION SETUP
COMPLETE message.
Incoming migration: Timestamp
in the RELOCATION REQUEST
message - Timestamp in the UE
CAPABILITY INFORMATION
CONFIRM message.
>Overl
ong
RRC
Setup
Delay
Yes
No
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
Inter-RAT handover: Timestamp

message - Timestamp in the
UTRAN MOBILITY
INFORMATION CONFIRM
message.
l SRAN10.1/
GBSS17.1/
RAN17.1
Overlong RRC setup delay occurs

when the RRC setup delay
exceeds the overlong delay
threshold limit.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The abnormal threshold is set by

engineers during analysis task
creation.
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1510
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Measur
ement
Info on
RRC
Setup
N/A
N/A
RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cell
N/A
N/A
Cell on which RAB setup is

requested.
not displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1511
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>TP
[0,3069 ]
N/A
Time Propagation (TP) is a term

defined by Huawei to indicate
time propagation delay during UE
access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>TP
Abnor
mal
Yes
No
N/A
If "TP" is larger than "TP

abnormal threshold", it indicators
that the TP is abnormal on RRC
setup.
Abnormal threshold is set when
creating tasks.
multiple cells during access, the
counters for all the cells in this
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1512
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Ec/
NO
[-31.5,0]
dB
Ec/No of the serving cell on RRC

setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Ec/
NO
Abnor
mal
Yes
No
N/A
If "Ec/No" is smaller than "Ec/No

abnormal threshold on RRC
setup", it indicators that the Ec/No
is abnormal on RRC setup.
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1513
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>RSCP
[-116,-25]
dBm
RSCP of the serving cell on RRC

setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RSCP
Abnor
mal
Yes
No
N/A
If "RSCP" is smaller than "RSCP

setup", it indicators that the RSCP
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1514
Nastar
Release Information
Param
eter
Range
Unit
Description
Supported
Solution
Version
RRC
Release
Time
N/A
N/A
Release time of RRC connection.
l SRAN8.0/
GBSS15.0/
RAN 15.0

CONNECTION RELEASE
message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Duratio
n
[0,+)
Seco
nd
Duration of a call.
Call duration = RRC release time
- RRC setup request time
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1515
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RRC
Release
Cell
1 to 64 characters
N/A
Name of the cell from which

signaling is released.
l SRAN8.0/
GBSS15.0/
RAN 15.0

name:cell name (RNCID: cellID).
not displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Release
Result
Successful
N/A
RRC release results.
Failed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1516
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
IU
Release
Cause
N/A
N/A
Release cause carried in the last IU

RELEASE COMMAND message
received by an RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
type
Radio Network
Layer Cause
Transport Layer
Cause
N/A
Type of failure cause.

For details, see 3GPP
25.413-9.2.1.4.
NAS Cause
Protocol Cause
Miscellaneous
Cause
Non-standard
Cause
Radio Network
Layer Cause
Extension
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1517
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Cause
value
N/A
N/A
Failure cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0

25.413-9.2.1.4.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1518
Nastar
Statistical Information
Param
eter
Range
Unit
Description
Supported
Solution
Version
Soft
Handov
er Info
N/A
N/A
Soft handover information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Soft
Handov
er
Request
s
[0,+)
Num
ber
Number of soft handover requests,

including soft handover requests
and softer handover requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1519
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Succe
ssful
Soft
Handov
ers
[0,+)
Num
ber
Number of successful soft

handovers, including successful
soft handovers and successful
softer handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Softer
Handov
er
Request
s
[0,+)
Num
ber
Number of softer handover

requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1520
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Succe
ssful
Softer
Handov
ers
[0,+)
Num
ber
Number of successful softer

handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Hard
Handov
er Info
N/A
N/A
Hard handover information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1521
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>IntraFreq
Handov
er
Request
s
[0,+)
Num
ber
Number of intra-frequency hard

handover requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Succe
ssful
IntraFreq
Handov
ers
[0,+)
Num
ber
Number of successful intrafrequency hard handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1522
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>InterFreq
Handov
er
Request
s
[0,+)
Num
ber
Number of inter-frequency hard

handover requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Succe
ssful
InterFreq
Handov
ers
[0,+)
Num
ber
Number of successful interfrequency hard handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1523
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
InterRAT
Handov
er Info
N/A
N/A
Inter-RAT handover information
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>InterSystem
Outgoin
g
Handov
er
Request
s(CS)
[0,+)
Num
ber
Number of CS domain outgoing

inter-RAT handover requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1524
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>InterSystem
Outgoin
g
Handov
er
Request
s(PS)
[0,+)
Num
ber
Number of PS domain outgoing

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Succe
ssful
InterSystem
Outgoin
g
Handov
ers
[0,+)
Num
ber
Number of successful outgoing

inter-RAT handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1525
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>InterSystem
Incomi
ng
Handov
er
Request
s
[0,+)
Num
ber
Number of incoming inter-RAT

handover requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Succe
ssful
InterSystem
Incomi
ng
Handov
ers
[0,+)
Num
ber
Number of successful incoming

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1526
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
DCCC
Info
N/A
N/A
DCCC information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DCCC
Speed
Increas
e
Initializ
ation
Times
[0,+)
Num
ber
Number of DCCC speed increase

initializations during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1527
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DCCC
Speed
Increas
e
Success
Times
[0,+)
Num
ber
Number of successful DCCC

speed increases during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DCCC
Speed
Decreas
e
Initializ
ation
Times
[0,+)
Num
ber
Number of DCCC speed decrease

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1528
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DCCC
Speed
Decreas
e
Success
Times
[0,+)
Num
ber

speed decreases during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Info
N/A
N/A
RAB information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1529
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Request
/Setup
Success
Times/
Normal
Release
Times/
Abnor
mal
Release
Times
(AMR)
[0,+)
Num
ber
Number of RAB requests,

successful RAB setups, normal
RAB releases, and abnormal RAB
releases for the AMR service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Request
/Setup
Success
Times/
Normal
Release
Times/
Abnor
mal
Release
Times
(VP)
[0,+)
Num
ber

releases for the VP service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1530
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Request
/Setup
Success
Times/
Normal
Release
Times/
Abnor
mal
Release
Times
(PS)
[0,+)
Num
ber

releases for PS services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In which, PS services include the

PS R99 service, HSDPA service,
HSUPA, service, and HSPA
service.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Request
/Setup
Success
Times/
Normal
Release
Times/
Abnor
mal
Release
Times
(HSDP
A)
[0,+)
Num
ber

releases for the HSDPA service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1531
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
MultiRAB
Info
N/A
N/A
Multi-RAB information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Abnor
mal CS
Release
due to
PS
Release
[0,+)
Num
ber
Number of abnormal CS releases

caused by PS release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1532
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Abnor
mal CS
Release
due to
PS
Service
Setup
[0,+)
Num
ber

caused by PS service setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Releas
ed
RABs
in CS
Domain
Trigger
ed by
the
Failure
in
Securit
y Mode
[0,+)
Num
ber
Number of released RABs in the

CS domain triggered by failed
security authentication.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1533
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Releas
ed
RABs
in PS
Domain
Trigger
ed by
the
Failure
in
Securit
y Mode
[0,+)
Num
ber

PS domain triggered by failed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Setup
Attempt
s of
Combin
ed
Service
(CS +
PS)
[0,+)
Num
ber
Setup Attempts of Combined

Service(CS + PS)
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1534
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Succe
ssful
Setups
of
Combin
ed
Service
(CS +
PS)
[0,+)
Num
ber
Successful Setups of Combined

Service(CS + PS)
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>CS
plus PS
multiRAB
CS
normal
release
times
[0,+)
Num
ber
CS plus PS multi-RAB CS normal

release times.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1535
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>CS
plus PS
multiRAB
CS
abnorm
al
release
times
[0,+)
Num
ber
CS plus PS multi-RAB CS
abnormal release times.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>CS
plus PS
multiRAB PS
normal
release
times
[0,+)
Num
ber
CS plus PS multi-RAB PS normal

release times.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1536
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>CS
plus PS
multiRAB PS
abnorm
al
release
times
[0,+)
Num
ber
CS plus PS multi-RAB PS
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Setup
Attempt
s of
Combin
ed
Service
(PS +
PS)
[0,+)
Num
ber
Setup attempts of combined

service(PS + PS).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1537
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Succe
ssful
Setups
of
Combin
ed
Service
(PS +
PS)
[0,+)
Num
ber
Successful setups of combined

service(PS + PS).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Norm
al
Release
s of
Combin
ed
Service
(PS +
PS)
[0,+)
Num
ber
Normal releases of combined

service(PS + PS).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1538
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Abnor
mal
Release
s of
Combin
ed
Service
(PS +
PS)
[0,+)
Num
ber
Abnormal releases of combined

service(PS + PS).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Statistic
s of
Voice
Quality
in CS
Domain
N/A
N/A
Statistics on voice quality in CS

domain.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1539
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>OneWayAudio
Times
[0,+)
Num
ber
Number of times that one-way

audio occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Noise
Times
[0,+)
Num
ber
Number of times that noise occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1540
Nastar
CS RAB Service Information

Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Setup
Info
N/A
N/A
RAB setup information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
RAB is radio access bearer for

short.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Multi
RAB
info
1CS
1CS + 1PS
N/A
Information about the setup of

combined RABs.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1541
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Request
Service
Type
Traffic class:
N/A
RAB request service type consists

of two parts: Traffic class and
Traffic type.
l SRAN8.0/
GBSS15.0/
RAN 15.0

in the format of Traffic class/
Traffic type.
l SRAN8.1/
GBSS15.1/
RAN 15.1
For details about Traffic class, see

3GPP 25.413.
l SRAN9.0/
GBSS16.0/
RAN16.0
conversational
streaming
interactive
background
Traffic type:
CS_AMR
Traffic type is a service type

defined by Huawei in terms of
radio access bearer (RAB).
CS_VP
CS_OTHER
PS_GENERAL
PS_HSDPA
l SRAN10.1/
GBSS17.1/
RAN17.1
PS_HSUPA
PS_HSPA ...
>RAB
Request
Time
N/A
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
N/A
Time when RAB setup is

requested. The statistical points
are as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0
RAB setup: Timestamp in the

RAB ASSIGNMENT REQUEST
message.
l SRAN8.1/
GBSS15.1/
RAN 15.1

in the RELOCATION
COMPLETE message.
l SRAN9.0/
GBSS16.0/
RAN16.0

in the HANDOVER TO UTRAN
COMPLETE message.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1542
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Cell
on RAB
Setup
Request
N/A
N/A

requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0

name:cell name (cell ID). The
RNC name and cell name can be
obtained from configuration data.
If the RNC name and cell name
cannot be queried, they are not
displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Comple
tion
Time
[0,+)
Seco
nd
Time when RAB setup completes.

The statistical points are as
follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0

RAB ASSIGNMENT
RESPONSE message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Incoming migration: The time is

not recorded.
l SRAN9.0/
GBSS16.0/
RAN16.0
Inter-RAT handover: The time is

not recorded.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1543
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Best
Cell on
RAB
Setup
Comple
tion
N/A
N/A
Best cell on which RAB setup

completes.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Servin
g Cell
on RAB
Setup
Comple
tion
N/A
N/A
Service cell on which RAB setup

completes.
displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1544
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DRD
Info
N/A
N/A
Information about DRDs during

RAB setup, recording the last three
DRDs at most.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DRD
Info:N
N/A
N/A
The N DRD record.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1545
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>DR
D
Target
Cell on
RRC
Setup
N/A
N/A
Target cell of the current DRD.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>DR
D
traffic
type
CS_AMR
CS_VP
N/A
Traffic type when the current DRD

occurs.
CS_OTHER
PS_GENERAL
PS_HSDPA
PS_HSUPA
PS_HSPA
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1546
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>DR
D
Failure
Cause
N/A
N/A
DRD failure cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
For details, see "Appendix:

Exception Cause Classification /
Enumeration Values of Failure
Cause (UMTS)".
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>>Er
ror
Type
For details, see the

"Enumeration
Values of Failure
Cause".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1547
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>>Er
ror
Reason

"Enumeration
Values of Failure
Cause".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Peer
Info
N/A
N/A
Information about the peer UE

during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1548
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>Pee
r
MSISD
N
00000000000000
0-999999999999
999
N/A
Mobile station international ISDN l SRAN8.0/

number (MSISDN) of the peer UE.
GBSS15.0/
MSISDN is a 15-digit numeric
RAN 15.0
string of decimal digits (0-9). For l SRAN8.1/
details, see 3GPP TS 23.003.
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1549
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL
Channe
l Types
After
RAB
Setup
DL transport
channel type:
N/A
Type of an uplink or downlink data

transmission channel after RAB
setup. The channel types are
defined by Huawei.
l SRAN8.0/
GBSS15.0/
RAN 15.0
DCH
FACH
RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
UL transport
channel type:
DCH
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
Issue 03 (2015-07-30)

1550
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL RB
Rate
[0,+)
kbit/s
Uplink and downlink RB rate after

RAB setup. The parameter value is
displayed in the format of UL RB
bitrate after RAB setup/DL RB
bitrate after RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In which,
l SRAN8.1/
GBSS15.1/
RAN 15.1
When UL is carried on RACH,

UL RB bitrate after RAB setup =
8000 bit/s.
l SRAN9.0/
GBSS16.0/
RAN16.0
When UL is carried on PCH, UL

RB bitrate after RAB setup = 0 bit/
s.
l SRAN10.0/
GBSS17.0/
RAN17.0
When UL is carried on the other

channels, UL RB bitrate after RAB
setup varies according to site
conditions.
l SRAN10.1/
GBSS17.1/
RAN17.1
When DL is carried on FACH, DL

RB bitrate after RAB setup = 8000
bit/s.
l SRAN11.0/
GBSS18.0/
RAN18.0
When DL is carried on PCH, DL

s.
When DL is carried on the other
channels, DL RB bitrate after RAB
conditions.
Issue 03 (2015-07-30)

1551
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Result
Successful
N/A
RAB setup results.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Failed
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Failure
Time
N/A
N/A
Time when RAB setup fails.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1552
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Failure
Cause
N/A
N/A
Cause of RAB setup failure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1553
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Delay
Estimat
ion
N/A
N/A
Delay estimation on RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1554
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>RAB
Setup
Delay
[0,+)
Seco
nd
RAB setup delay = Time when

RAB setup completes - Time when
RAB setup is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Over
long
RAB
Setup
Delay
Yes
No
N/A
Overlong RAB setup delay occurs

when the RAB setup delay exceeds
the overlong delay threshold limit.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The overlong delay threshold is set

by engineers during analysis task
creation.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1555
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Call
Setup
Delay
[0,+)
Seco
nd
Call setup delay = Time when

RRC setup is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Call setup delay = RAB setup

delay + RRC setup delay.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Note that this parameter is

applicable only to the first RAB
after RRC setup.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Over
long
Call
Setup
Delay
Yes
No
N/A
Overlong call setup delay occurs

when the call setup delay exceeds
l SRAN8.0/
GBSS15.0/
RAN 15.0

creation.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1556
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>CM
Service
Request
Time
N/A
N/A
Service request time, that is, the

timestamp of "CM Service
Request" message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Uu
Delay
[0,+)
Seco
nd
Uu delay. The statistical points are

as follows:
RB setup: Timestamp in the
RADIO BEARER SETUP
COMPLETE message Timestamp in the RADIO
BEARER SETUP message.
RB reconfiguration: Timestamp
in the RADIO BEARER
RECONFIGURATION
BEARER RECONFIGURATION
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1557
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Alert
ing
Time
N/A
N/A
Time of outgoing call alerting

during a call. Statistical point:
Timestamp in the ALERTING
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Call
Comple
tion
Delay
(Alertin
g)
N/A
[0,+)
N/A
1.The parameter value is N/A in

the following condition:
The current RAB is not the first
RAB after RRC setup.
2.The parameter value is the actual
time in the following conditions:
The current RAB is the first RAB
after RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
Outgoing call alerting delay =

Alerting time - RRC setup request l SRAN10.0/
GBSS17.0/
time.
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1558
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Over
long
Call
Comple
tion
Delay
(Alertin
g)
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
Yes
No

2.The parameter value is Yes in the
following conditions:
after RRC setup.
RRC Setup Flag(MOC/MTC) is
MOC.
Outgoing call alerting delay >
Overlong outgoing call alerting
delay threshold (MOC).
after RRC setup.
MTC.
delay threshold (MTC).
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3.The parameter value is No in the

other conditions.
The overlong delay thresholds
(MOC) and overlong delay
threshold (MTC) are set by
engineers during task creation.
Issue 03 (2015-07-30)

1559
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Conn
ect Ack
Time
N/A
N/A
Time of incoming call alerting

Timestamp in the CONNECT
ACKNOWLEDGE message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Call
Comple
tion
Delay
(Conne
ct Ack)
[0,+)
Seco
nd

after RRC setup.
Incoming call alerting delay =
Connect Ack time - RRC setup
request time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1560
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Over
long
Call
Comple
tion
Delay
(Conne
ct Ack)
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
Yes
No

after RRC setup.
MOC.
Incoming call alerting delay >
Overlong incoming call alerting
after RRC setup.
MTC.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

other conditions.
Issue 03 (2015-07-30)

1561
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Process
N/A
N/A
Process information of RAB setup.

This parameter is used with RAB
Setup Failure Cause to analyze
problems.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Queu
ing
Indicato
r
False
True
N/A
TRUE(1) indicates that queuing

occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1562
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Intra
-system
DRD
Indicato
r
False
N/A
TRUE(1) indicates that intrasystem DRD occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
True
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Inter
-system
DRD
Indicato
r
False
True
N/A
TRUE(1) indicates that intersystem DRD occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1563
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Resourc
e
Congest
ion
Informa
tion on
RAB
Setup
N/A
N/A
Information about the latest radio

resource congestion during RAB
setup. This parameter is used with
RAB Setup Failure Cause to
analyze problems.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Cong
estion
Time
N/A
N/A
Time when radio resource

congestion occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1564
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Cong
estion
Cell ID
N/A
N/A
Cell where radio resource

congestion occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Cong
estion
Status
Code
DL CE
N/A
Cause of radio resource

congestion.
UL CE
UL DL CE
DL IUB band
UL IUB band
UL DL IUB band
UL power
DL power
UL DL power
HSDPA user
number
HSUPA user
number
HSPA user
number
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1565
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Release
Info
N/A
N/A
Information about RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Multi
RAB
info
1CS
1CS + 1PS
N/A
Information about the release of

combined RABs.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1566
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Single
-RAB
Abnor
mal
Release
Indicato
r
False
N/A
TRUE(1) indicates single-RAB

abnormal release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
True
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Multip
le-RAB
Abnor
mal
Release
Indicato
r
False
True
N/A
TRUE(1) indicates multiple-RAB

abnormal release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1567
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Release
Time
N/A
N/A
Time when RAB release

completes. The statistical points
are as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0
Normal release and CN abnormal l SRAN8.1/

release: RAB release time =
GBSS15.1/
Timestamp in the IU RELEASE
RAN 15.1
COMMAND or RAB
l SRAN9.0/
ASSIGNMENT REQUEST
GBSS16.0/
message.
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Duratio
n
[0,+)
Seco
nd

- RAB setup time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1568
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Duratio
n
Shorter
Yes
N/A
If "RAB Duration" is smaller than

"RAB Duration shorter threshold",
it indicators that the RAB duration
is too shorter.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Best
Cell
Before
RAB
Release
N/A
N/A
Best cell before RAB release.

displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1569
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Servin
g Cell
Before
RAB
Release
N/A
N/A
Serving cell before RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1570
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL
Channe
l Types
DL transport
channel type:
N/A

transmission channel before RAB
release. The channel types are
defined by Huawei.
l SRAN8.0/
GBSS15.0/
RAN 15.0
DCH
FACH
RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
UL transport
channel type:
DCH
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
Issue 03 (2015-07-30)

1571
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL RB
Rate
[0,+)
kbit/s

RAB setup and before RAB
release. The parameter value is
l SRAN8.0/
GBSS15.0/
RAN 15.0
In which,
l SRAN9.0/
GBSS16.0/
RAN16.0

8000 bit/s.
s.
conditions.
bit/s.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

s.
conditions.
Issue 03 (2015-07-30)

1572
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Disco
nnect
Cause
N/A
N/A
Cause carried in the

DISCONNECT message. For
details, see 3GPP
24.008-10.5.4.11.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Disco
nnect
Directio
n
from UE
from CN
N/A
Direction for sending the

DISCONNECT message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1573
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Release
Failure
Cause
N/A
N/A
Cause of abnormal RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1574
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Release
Failure
Time
N/A
N/A
Time when RAB release fails.

That is, when the system receives
the following timestamp:
l SRAN8.0/
GBSS15.0/
RAN 15.0
IU RELEASE REQUEST
l SRAN8.1/
GBSS15.1/
RAN 15.1
RAB RELEASE REQUEST
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1575
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Process
Info
N/A
N/A
RAB process information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Delay
Estimat
ion
N/A
N/A
Delay estimation on RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1576
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Disc
onnect
time
N/A
N/A
Time when a call completes.

Statistical point: timestamp in the
DISCONNECT message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Servi
ce
Duratio
n
[0,+)
Seco
nd
Service duration = Disconnect

time - Connect Ack time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1577
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Short
Call
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
Yes
No
When the current RAB is not the

first RAB after RRC setup and Call
duration < Short call threshold.
after RRC setup.
MOC.
Call duration < Short call threshold
(MOC).
after RRC setup.
MTC.
(MTC).
other conditions.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
The short call threshold, short call

threshold (MOC), and short call
Issue 03 (2015-07-30)

1578
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>SQI
Statistic
s
N/A
N/A
Statistics on SQIs
l SRAN8.0/
GBSS15.0/
RAN 15.0

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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
2. The RNC can statistics based on

the average SQI value and divides
signal quality into different levels l SRAN10.1/
GBSS17.1/
according to SQI values:
RAN17.1
l SRAN11.0/
(400,500]), Good (SQI<=
GBSS18.0/
(300,400]), Accept (SQI<=
RAN18.0
(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.
Issue 03 (2015-07-30)

1579
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Aver
age SQI
[0,500]
N/A
Average SQI value during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Abn
ormal
SQI
Yes
No
N/A
If SQI average < Abnormal SQI

threshold,
The value of this parameter is Yes.
Otherwise, the value is No.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
The abnormal SQI threshold is set
RAN 15.1
by engineers during task creation.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1580
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Radi
o of
Excelle
nt SQIs
(%)
[0,100]
Proportion of voice quality with

SQI as Excellent from RAB setup
to RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Radi
o of
Good
SQIs
(%)
[0,100]

SQI as Good from RAB setup to
RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1581
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Radi
o of
Accept
SQIs
(%)
[0,100]

SQI as Accept from RAB setup to
RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Radi
o of
Poor
SQIs
(%)
[0,100]

SQI as Poor from RAB setup to
RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1582
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Radi
o of Bad
SQIs
(%)
[0,100]

SQI as Bad from RAB setup to
RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BLER
Statistic
Info
N/A
N/A
Statistics on BLERs.
1. Block error rate (BLER)
uplink during a call. The BLER
statistics are collected by the 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%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1583
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Time
s UL
Service
BLER
Falls
into
Levels
1 to 6
[0,+)
Num
ber
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Statist
ics on
Last
Receive
d
Blocks
N/A
N/A
Statistics on received blocks

before link release.
The statistical period is 2.56
seconds.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1584
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Num
ber of
UL
Total
Blocks
(1~5)
[0,+)
Num
ber
Total number of UL blocks

received within the five periods
l SRAN8.0/
GBSS15.0/
RAN 15.0

in this format: Number of UL
blocks received in period 1/
Number of UL blocks received in
period 2/.../Number of UL blocks
received in period 5.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
UL
Error
Blocks
(1~5)
[0,+)
Num
ber
Number of UL error blocks

l SRAN8.0/
GBSS15.0/
RAN 15.0

in this format: Number of UL error
received in period 2/.../Number of
UL error blocks received in period
5.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1585
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Uplin
k OneWayAudio
Statistic
s
N/A
N/A
Statistics on uplink one-way

audio.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1. The RNC records an uplink oneway audio problem when it detects

any error packet or a large packet
loss rate at the uplink IUUP layer.
2. The RNC records a maximum of
the first five uplink one-way audio
problems during each call of a UE.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Occu
rrence
Time
N/A
N/A
Time when uplink one-way audio

occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1586
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Occu
rrence
Cell
N/A
N/A
Cell when uplink one-way audio

occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DL
Silence
Statistic
Info
N/A
N/A
Statistics on downlink one-way

audio. The downlink one-way
audio problems fall into two types:
l SRAN8.0/
GBSS15.0/
RAN 15.0
1. The RNC records a downlink

one-way audio problem when it
detects any error packet or a large
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1

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
Issue 03 (2015-07-30)

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1587
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Occu
rrence
Time
N/A
N/A
Time when a downlink one-way

audio problem occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Occu
rrence
Cell
N/A
N/A
Cell when a downlink one-way

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1588
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Nois
e
Statistic
s
N/A
N/A
Statistics on noises.
1. The RNC records a noise
problem.
l SRAN8.0/
GBSS15.0/
RAN 15.0
2. The RNC records only the first

one noise problem during each call
of a UE.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Occu
rrence
Time
N/A
N/A
Time when a noise problem

occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1589
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Occu
rrence
Cell
N/A
N/A
Cell when a noise problem occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1590
Nastar
PS RAB Service Information

Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Setup
Info
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

short.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Multi
RAB
info
1CS
1CS + 1PS
N/A

combined RABs.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1591
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Request
Service
Type
Traffic class:
N/A
There are two RAB request

service types: Traffic class and
Traffic type.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Traffic type.
l SRAN8.1/
GBSS15.1/
RAN 15.1

3GPP 25.413.
l SRAN9.0/
GBSS16.0/
RAN16.0
conversational
streaming
interactive
background
Traffic type:
CS_AMR

CS_VP
CS_OTHER
PS_GENERAL
PS_HSDPA
l SRAN10.1/
GBSS17.1/
RAN17.1
PS_HSUPA
PS_HSPA ...
>RAB
Request
Time
N/A
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
N/A
Time for requesting RAB setup.

follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0

message.
l SRAN8.1/
GBSS15.1/
RAN 15.1

in the RELOCATION
COMPLETE message.
l SRAN9.0/
GBSS16.0/
RAN16.0

COMPLETE message.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1592
Nastar
Param
eter
Range
>Cell
N/A
on RAB
Setup
Request
Unit
Description
Supported
Solution
Version
N/A

requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Comple
tion
Time
[0,+)
Seco
nd

follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0

RAB ASSIGNMENT
RESPONSE message.
l SRAN8.1/
GBSS15.1/
RAN 15.1

not recorded.
l SRAN9.0/
GBSS16.0/
RAN16.0

not recorded.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1593
Nastar
Param
eter
Range
>Cell
N/A
on RAB
Setup
Comple
tion
Unit
Description
Supported
Solution
Version
N/A

completes.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Serving
Cel on
RAB
Setup
Comple
tion
N/A
N/A
Serving cell on which RAB setup

completes.
displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1594
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DRD
Info
N/A
N/A

RAB setup, recording the last
three DRDs at most.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DRD
Info:N
N/A
N/A
The N DRD record.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1595
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>DR
D
Target
Cell on
RRC
Setup
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>DR
D
traffic
type
CS_AMR
CS_VP
N/A
Traffic type when the current

DRD occurs.
CS_OTHER
PS_GENERAL
PS_HSDPA
PS_HSUPA
PS_HSPA ...
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1596
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>DR
D
Failure
Cause
N/A
N/A
DRD failure cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
For details, see the Failure Cause

tab page.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>>Er
ror
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)"
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1597
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>>Er
ror
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1598
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL
Channe
l Types
After
RAB
Setup
DL transport
channel type:
N/A
Type of an uplink or downlink

data transmission channel after
RAB setup. The channel types are
defined by Huawei.
l SRAN8.0/
GBSS15.0/
RAN 15.0
DCH
FACH
RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
UL transport
channel type:
DCH
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
Issue 03 (2015-07-30)

1599
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL RB
Rate
[0,+)
bps
DL/UL RB rate after RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0

in the format of UL RB bitrate
after RAB setup/DL RB bitrate
after RAB setup.
In which,
l SRAN8.1/
GBSS15.1/
RAN 15.1
If UL is carried on RACH, UL RB
bitrate after RAB setup = 8000 bit/
s.
l SRAN9.0/
GBSS16.0/
RAN16.0
If UL is carried on PCH, UL RB
bitrate after RAB setup = 0 bit/s.
l SRAN10.0/
GBSS17.0/
RAN17.0

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.
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

s.
channels, DL RB bitrate after
conditions.
Issue 03 (2015-07-30)

1600
Nastar
Param
eter
Range
>UL/
[0,+)
DL
RAB
Negotia
ted Rate
Unit
Description
Supported
Solution
Version
bps
UL/DL RAB negotiated rate.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Yes
Overlo
w UL
No
RAB
Negotia
ted Rate
N/A
If "Overlow UL RAB Negotiated

Rate" is smaller than "Overlow
UL RAB Negotiated Rate
Threshold", the record has the
problem that the overlow UL RAB
vegotiated rate is too small.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1601
Nastar
Param
eter
Range
Overlo
Yes
w DL
No
RAB
Negotia
ted Rate
Unit
Description
Supported
Solution
Version
N/A
If "Overlow DL RAB Negotiated

DL RAB Negotiated Rate
problem that the overlow DL RAB
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Result
Successful
N/A
Failed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1602
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Failure
Time
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Failure
Cause
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1603
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1604
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Delay
Estimat
ion
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>RAB
Setup
Delay
[0,+)
Seco
nd

RAB setup completes - Time
when RAB setup is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1605
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Over
long
RAB
Setup
Delay
Yes
N/A

when the RAB setup delay
threshold limit.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No
The overlong delay threshold is

set by engineers during analysis
task creation.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Call
Connec
tion
Delay
[0,+)
Seco
nd
1.When the following scene

occurs, it displays "N/A".
Scene: the first RAB after the
RAB (Non-RRC) setup.
occurs, it displays the result value.
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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1606
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Over
long
Call
Connec
tion
Delay
Yes
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
No

2.When the following scenes
occur, it displays the result value.
l SRAN8.1/
GBSS15.1/
RAN 15.1

RAB (RRC) setup; and "RRC
Setup Flag(MOC/MTC)" is
"MOC"; and "Call Setup Delay" is
larger than "Latency on Call
Connection (MOC) ".
l SRAN9.0/
GBSS16.0/
RAN16.0

"MTC"; and "Call Setup Delay" is
smaller than "Latency on Call
Connection (MTC) ".
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
3.When the other scene occurs, it

displays "No".
The threshold is set by engineers
during analysis task creation.
>>CM
Service
Request
Time
N/A
N/A

Request" message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1607
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Uu
delay
(ms)
[0,+)
Seco
nd

as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0

RADIO BEARER SETUP
in the RADIO BEARER
RECONFIGURATION
BEARER
RECONFIGURATION message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Sched
uling
Priority
N/A
N/A
Scheduling priority during RAB

setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1608
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Allo
cation/
Retenti
on
Priority
N/A
N/A
Allocation/retention priority. For

details, see 3GPP 25.413-9.2.1.3.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>Pri
ority
Level
[0,15]
N/A
Priority level in the allocation and

retention of RABs.
The value range is [0,15]. A larger
value indicates lower priority.
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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1609
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>Pre
emptio
n
Capabil
ity
Shall not trigger

pre-emption
N/A
Whether the current RAB can

preempt resources of other RABs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
May trigger preemption
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>Pre
emptio
n
Vulnera
bility
Not pre-emptable
Pre-emptable
N/A
Whether resources of the current

RAB can be preempted by other
RABs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1610
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>Qu
euing
Allowe
d
Queuing not
allowed
N/A
Whether the current RAB can be

queued for resource scheduling.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Queuing allowed
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Traff
ic
Handlin
g
Priority
[0,15]
N/A

retention of system resources. For
details, see 3GPP
25.433-9.2.1.1A.
highest priority.
lowest priority.
no priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1611
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Sche
duling
Priority
Indicato
r
[0,15]
N/A
HS-DSCH scheduling priority.

25.433-9.2.1.53H.
l SRAN8.0/
GBSS15.0/
RAN 15.0

value indicates higher priority.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Release
Info
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1612
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Multi
RAB
info
1CS
N/A

combined RABs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1CS + 1PS
1CS + 2PS
l SRAN8.1/
GBSS15.1/
RAN 15.1
1CS + 3PS
2CS
2CS + 1PS
l SRAN9.0/
GBSS16.0/
RAN16.0
2CS + 2PS
1PS
l SRAN10.0/
GBSS17.0/
RAN17.0
2PS
3PS
4PS
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Single
-RAB
Abnor
mal
Release
Indicato
r
False
True
N/A

abnormal release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1613
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Multi
pleRAB
Abnor
mal
Release
Indicato
r
False
N/A

abnormal release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
True
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Release
Time
N/A
N/A

are as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0
Normal release and CN abnormal

COMMAND or RAB
ASSIGNMENT REQUEST
message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1614
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Duratio
n
[0,+)
RAB duration = RAB release

time - RAB setup time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Best
Cell
Before
RAB
Release
N/A
N/A

displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1615
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Servin
g Cell
Before
RAB
Release
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1616
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL
Channe
l Types
UL transport
channel type:
N/A

data transmission channel before
RAB release. The channel types
are defined by Huawei.
l SRAN8.0/
GBSS15.0/
RAN 15.0
DCH
FACH
RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
DL transport
channel type:
DCH
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
Issue 03 (2015-07-30)

1617
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL RB
Rate
[0,+)
kbit/s
UL/DL RB rate after RAB setup

and before RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0

after RAB setup.
In which,
s.
conditions.
8000 bit/s.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

s.
conditions.
Issue 03 (2015-07-30)

1618
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DP
Deactiv
ate
Cause
N/A
N/A
Cause carried by the Deactivate

PDP context request message. For
details, see 3GPP 24.008-10.5.6.6
SM cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Release
Failure
Cause
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1619
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1620
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Release
Failure
Time
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
IU RELEASE REQUEST
l SRAN8.1/
GBSS15.1/
RAN 15.1
RAB RELEASE REQUEST
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Process
Info
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1621
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>PDP
Activat
e
Request
Time
N/A
N/A
Timestamp in the PDP

ACTIVIATE REQUEST
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>PDP
Activat
e Ack
Time
N/A
N/A

ACTIVIATE ACKNOWLEDGE
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1622
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>PDP
Deactiv
ate
Time
N/A
N/A
Timestamp in the DEACTIVATE

PDP CONTEXT REQUEST
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BLER
Statistic
Info
N/A
N/A
Statistical information about

BLERs.
statistics are collected by the
RNC. The value range is
[0.00,100.00]. A larger value
indicates worse signal quality.
are:
0-0.78%, 0.78%-1.56%,
1.56%-3.12%, 3.12%-6.24%,
6.24%-12.48%, above 12.48%.
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1623
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Time
s UL
Service
BLER
Falls
into
Levels
1 to 6
[0,+)
Num
ber
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Statist
ics on
Last
Receive
d
Blocks
N/A
N/A

seconds.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1624
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Num
ber of
UL
Total
Blocks
(1~5)
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
UL
Error
Blocks
(1~5)
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

5.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1625
Nastar

Param
eter
Range
Unit
Description
Supported
Solution
Version
Numbe
r
[1,+)
N/A
Number that uniquely identifies a

sent and received signaling
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signali
ng
Time
N/A
N/A
Time when a signaling message is

sent or received.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1626
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Signali
ng
Direct
to CN
N/A
Direction for sending or receiving

a signaling message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
from CN
to other RNC
l SRAN8.1/
GBSS15.1/
RAN 15.1
from other RNC

to NODEB
from NODEB
l SRAN9.0/
GBSS16.0/
RAN16.0
to UE
from UE
l SRAN10.0/
GBSS17.0/
RAN17.0
to SAS
from SAS
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signali
ng Type
N/A
N/A
Type of a signaling message that

complies with any protocol and is
transmitted over the Iu, Iur, Iub, or
Uu interface.
For example, RRC CONNECT
REQUEST is a signaling type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1627
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Signali
ng
Content
N/A
N/A

The signaling message of the
VVIP (very very important person)
is displayed when double-click a
record, it do not support to display
the common users' signaling
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1628
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Number
[1,+)
N/A

measurement report (MR).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measur
ement
Time
N/A
N/A
Time when an MR is reported.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1629
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
MR
Type
Intra-freq
measurement
type
N/A
MR type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Inter-freq
measurement
type
l SRAN8.1/
GBSS15.1/
RAN 15.1
Inter-RAT
measurement
type
l SRAN9.0/
GBSS16.0/
RAN16.0
Event MR, such

as E1A and so on
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measur
ement
Object
Type
Best cell
Active set cell
N/A
Type of a measurement object

reported in an MR.
Monitor set cell
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1630
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Measur
ement
Object
N/A
N/A

reported in an MR.
l SRAN8.0/
GBSS15.0/
RAN 15.0

name:cell name (cell ID).
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
P-SC
[0,512]
N/A
Scrambling code in an MR.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1631
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Ec/NO
(dB)
[-31.5,0]
dB
Ratio of energy per modulating bit

to the noise spectral density (Ec/
No). For details, see 3GPP 25.331.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RSCP
(dBm)
[-116,-25]
dBm
Received signal code power

(RSCP). For details, see 3GPP
25.331.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In the complaint analysis support

theme, the first result in the
measurement report information
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1632
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
InterRAT
Carrier
RSSI
(dBm)
N/A
dBm
Received signal strength indicator

(RSSI) of a GSM carrier. For
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RSRP
(dBm)
[0,97]
dBm
Reference signal received power

(RSRP). For details, see 3GPP
36.133.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1633
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RSRQ
(dB)
[0,33]
dB
Reference signal received quality

(RSRQ). For details, see 3GPP
36.133.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
UE TX
Power
(dBm)
N/A
dBm
Transmit power of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1634
Nastar
Mobility Analysis
Param
eter
Range
Unit
Description
Supported
Solution
Version
Number
[1,+)
N/A
Number of a handover during a

call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
N/A
Blank
Whether a handover is abnormal.

If a red exclamation mark is
displayed in this column, the
handover is abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1635
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Type
Softer
handover
N/A
Type of mobility analysis.

Currently, the system supports the
following mobility analysis types:
l SRAN8.0/
GBSS15.0/
RAN 15.0
Intra-freq hard
handover
Soft handover
Inter-freq hard
handover
l SRAN8.1/
GBSS15.1/
RAN 15.1
Inter-system
incoming
handover
Incoming migration
Inter-system
outgoing
handover/CS
system
handover
Cell update
Soft handover
Hard handover
Outgoing migration
Channel handover
Inter-system
outgoing
handover/Cell
change order PS
system
handover
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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 03 (2015-07-30)

1636
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
N/A
Start time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Incoming
migration/Cell
update reloc in
Outgoing
migration/
Static migration
Cell update
Channel
handover
.U2L handover
.U2L
redirection
Begin
Time
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1637
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Interval
(s)
[0,+)
Interval = Start time - End time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1638
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Overlon
g
Interval
Yes
N/A
If Interval > Overlong xxx delay

threshold,
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

The overlong xxx delay threshold
is set by engineers during task
creation. The threshold types are as
follows:
Overlong soft handover delay
threshold
Overlong hard handover delay
threshold
Overlong incoming inter-RAT
handover delay threshold
Overlong outgoing inter-RAT
Overlong incoming handover
delay threshold
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlong outgoing handover

delay threshold
Overlong channel handover delay
threshold
.Overlong U2L redirection delay
threshold
Issue 03 (2015-07-30)

1639
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
End
Time
N/A
N/A
End time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Trigger
Cause
converage
based
N/A
Trigger cause.
HCS blind
based
HCS meas
based
load based but
blind handover
load based and
measurement
based CLB
load based and
measurement
based LDR
forced
handover
emergency
handover
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
1640
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
MutiRAB
Info
1CS
N/A
Combined RAB service status

when mobility analysis is
performed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1CS + 1PS
1CS + 2PS
l SRAN8.1/
GBSS15.1/
RAN 15.1
1CS + 3PS
2CS
2CS + 1PS
l SRAN9.0/
GBSS16.0/
RAN16.0
2CS + 2PS
1PS
l SRAN10.0/
GBSS17.0/
RAN17.0
2PS
3PS
4PS
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measur
e Type
Active Set
N/A
Measurement type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1641
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Source
Cell
N/A
N/A
The parameter value is displayed in

the following format: cell name
(cell ID).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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Source
Ec/NO
(dB)
[-31.5,0]
dB

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1642
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Source
RSCP
(dBm)
[-116,-25]
dBm

25.331.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Source
UL
Channel
Type
DCH
FACH
N/A
Source UL channel type when

occuring the channel handover.
RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1643
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Source
DL
Channel
Type
DCH
N/A
Source DL channel type when

l SRAN8.0/
GBSS15.0/
RAN 15.0
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
HSDSCH
EDCH
PCH
l SRAN9.0/
GBSS16.0/
RAN16.0
EFACH
ERACH
l SRAN10.0/
GBSS17.0/
RAN17.0
EPCH
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
UL RB
Rate
(kbit/s)
[0,+)
kbit/s
UL RB rate when occuring the

channel handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1644
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
DL RB
Rate
(kbit/s)
[0,+)
kbit/s
DL RB rate when occuring the

channel handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
System
N/A
N/A
Indicates the RAT of the target

network after an outgoing or
incoming inter-RAT handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1645
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
Cell
N/A
N/A
Name of target cell. The parameter

value is displayed in the following
format: RNC name:cell name (cell
ID).The NE name can be obtained
name cannot be queried, the cell ID
in the MR is displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
Ec/NO
(dB)
[-31.5,0]
dB

No) of 3G target cell. For details,
see 3GPP 25.331.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1646
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
RSCP
(dBm)
[-116,-25]
dBm

(RSCP) of 3G target cell. For
details, see 3GPP 25.331.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
Target
Cell
Operati
on
RL ADD
RL DEL
N/A
Target cell operation of the 3G

target cell when occuring the soft
handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1647
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
Target
Cell
Operati
on Time
N/A
N/A
Target cell operation time of the

3G target cell when occuring the
soft handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
carrier
RSSI
(dBm)
N/A
dBm

(RSSI) of a GSM carrier of 2G
target cell. For details, see 3GPP
TS 45.008.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1648
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RSRP
(dBm)
[-140,-43]
dBm

(RSRP) of LTE target cell. For
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RSRQ
(dB)
[-19.5,-2.5]
dB

(RSRQ) of LTE target cell. For
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1649
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
UL
Channel
Type
DCH
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
HSDSCH
EDCH
PCH
l SRAN9.0/
GBSS16.0/
RAN16.0
EFACH
ERACH
l SRAN10.0/
GBSS17.0/
RAN17.0
EPCH
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
DL
Channel
Type
DCH
FACH
N/A

RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1650
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
UL RB
Rate
(kbit/s)
[0,+)
kbit/s

channel handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
DL RB
Rate
(kbit/s)
[0,+)
kbit/s

channel handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1651
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Fail
Cause
N/A
N/A
Failure cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1652
Nastar
Service Analysis(RAB)
Param
eter
Range
Unit
Description
Supported
Solution
Version
Numbe
r
[1,+)
N/A
Record number of RAB service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnor
mal
N/A
Blank
Whether a servive record is

abnormal.
displayed in this column, the record
is abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1653
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Setup
Abnor
mal
N/A
Whether a servive record of RAB

setup is abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Blank

is abnormal.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Setup
Failure
Cause
For details, see

"Appendix:
Exception
Cause
Classification /
Enumeration
Values of
Failure Cause
(UMTS)".
N/A
Cause when RAB setup fails.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1654
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Request
Service
Type
CS_AMR
N/A
Service type of RAB request.
l SRAN8.0/
GBSS15.0/
RAN 15.0
CS_VP
CS_OTHER
l SRAN8.1/
GBSS15.1/
RAN 15.1
PS_GENERAL
PS_HSDPA
l SRAN9.0/
GBSS16.0/
RAN16.0
PS_HSUPA
PS_HSPA
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Request
Time
N/A
N/A
Time when RAB is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1655
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Cell on
RRC
Request
N/A
N/A
Cell when RAB is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Setup
Time
N/A
N/A
Time of RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1656
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Best
Cell on
RAB
Setup
N/A
N/A
Best cell on RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Serving
Cell on
RAB
Setup
N/A
N/A
Serving cell on RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1657
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Peer
Informa
tion
N/A
N/A
Peer information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If the service is RAB on CS domain,

it displays "Peer MSISDN".
If the service is RAB on PS domain,
it displays N/A.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
MultiRAB
Informa
tion on
RAB
Setup
1CS
1CS + 1PS
N/A
Multi-RAB Information on RAB

setup.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
...
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1658
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Release
Abnor
mal
N/A

release is abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Blank

that "Single-RAB Abnormal
Release Indicator" or "MultipleRAB Abnormal Release Indicator"
is YES.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Release
Failure
Cause
For details, see

"Appendix:
Exception
Cause
Classification /
Enumeration
Values of
Failure Cause
(UMTS)".
N/A
Cause of RAB release failure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1659
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Discon
nect
Cause
For details, see

3GPP.
N/A
Cause of the call is disconnected,

that is the cause value of NAS
Disconnect message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The value is valid only on RAB CS

domain.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP
Deactiv
e Cause
For details, see

3GPP.
N/A
Cause of the PDP is deactive, that is

the cause value of Deactivate PDP
context request message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The value is valid only on RAB PS

domain.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1660
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Release
Time
N/A
N/A
Time on RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best
Cell
Before
RAB
Release
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1661
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Serving
Cell
Before
RAB
Release
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
MultiRAB
Informa
tion on
RAB
Release
1CS
1CS + 1PS
N/A
Multi-RAB information on RAB

release.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
...
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1662
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Setup
Delay
[0,+)
Seco
nd
RAB setup delay = Time when RAB

setup completes - Time when RAB
setup is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Duratio
n
[0,+)
Seco
nd
RAB duration = Time when RAB is

released - Time when RAB setup
completes
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1663
Nastar
Param
eter
Range
Unit
Description
Service
Duratio
n
[0,+)
Seco
nd
Service duration.
Supported
Solution
Version
l SRAN8.0/
GBSS15.0/
RAN 15.0
it displays the service duration (that
is call time).
l SRAN8.1/
GBSS15.1/
RAN 15.1
it displays N/A (that is not
involved).
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Uplink
Throug
hput
[0,+)
Byte
Total uplink throughput.

involved).
it displays total throughput on
uplink of RAB process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1664
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Total
Uplink
Transm
ission
Duratio
n
[0,+)
Seco
nd
Total uplink transmission duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0

involved).
it displays total transmission
duration on uplink of RAB process.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Averag
e
Uplink
Throug
hput
[0,+)
kbit/s
Average uplink throughput.

involved).
it displays average throughput on
uplink throughput/Total uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1665
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Overlo
w
Averag
e
Uplink
Throug
hput
Yes
N/A
If "Average Uplink Throughput" is

smaller than "Average Uplink
Throughput Threshold", the record
has the problem that the average
uplink throughput is too small.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Downli
nk
Throug
hput
[0,+)
Byte
Total downlink throughput.

involved).
downlink of RAB process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1666
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Total
Downli
nk
Transm
ission
Duratio
n
[0,+)
Seco
nd
Total downlink transmission

duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0

involved).
duration on downlink of RAB
process.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Averag
e
Downli
nk
Throug
hput
[0,+)
kbit/s
Average downlink throughput.

involved).
Total downlink throughput/Total
downlink transmission duration
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

1667
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Overlo
w
Averag
e
Downli
nk
Throug
hput
Yes
N/A
If "Average Downlink Throughput"

is smaller than "Average Downlink
downlink throughput is too small.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
4.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
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Serial
Number
N/A
N/A
Serial number of a CHR. It

uniquely identifies a call record.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1668
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Combined
N/A
N/A

one.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

mobile-originated and mobileterminated eNodeBs and then is
combined into one CHR. A CHR
is a combined one if a yellow icon
is displayed.
Abnormal
N/A
N/A
Whether a call record is

abnormal.
displayed in this column, the call
record is abnormal.
Abnormal
Cause
N/A
N/A
Cause of an abnormal call record,

which is displayed in the format
of Exception type (number of
exception types)/Exception
cause (number of exception
causes). The exception types
include access failure, call drop,
and handover failure.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Network
LTE FDD
N/A
Network technology type.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
LTE TDD
Issue 03 (2015-07-30)
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1669
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Access
Type
Intra-RAT
RRC Access
N/A
Access type, based on which

subscriber access types can be
defined.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Access type of CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Incoming
HO/IntraRAT
Incoming
HO
Incoming
HO/UTRAN
Incoming
HO
Incoming
HO/GERAN
Incoming
HO
Incoming
HO
CSFB On
Access
CSFB:VOIC
EEmergency
call
CSFB:VOIC
E-Nonemergency
call
CSFB:LCSNonemergency
call
Access
Time
N/A
N/A
Time when a UE accesses a cell

at the beginning of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Access Cell
1 to 64
characters
N/A
Cell that a UE accesses at the

beginning of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

in the following format: eNodeB
name:cell name (eNodeB ID:cell
ID).
Issue 03 (2015-07-30)

1670
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Release
Time
N/A
N/A
Time when the link is released at

the end of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Release
Cell
1 to 64
characters
N/A
Cell from which a UE is released

at the end of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

ID).
Interworkin
g Mode
RedirectionWCDMA
N/A
Interworking Mode and RAT of

target network
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RedirectionGERAN
RedirectionTDSCDMA
RedirectionCDMA
PSHOWCDMA
PSHOTDSCDMA
PSHOCDMA
PSHOGERAN
IMSI
N/A

IMSI is displayed only when the
EPC is not interconnected.
STMSI
N/A
N/A
STMSI information of a
subscriber.
NOTE
STMSI is displayed only when the
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1671
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
User
ID:Alias
N/A
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

IMEI-TAC
00000000-99
999999
N/A
First eight digits in the IMEI of a

UE.
short.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Terminal
Model
N/A
N/A
Model of a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Duration
[0,+)
Second
Duration of a call, which is

displayed in the format of
hh:mm:ss.nnn.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Call duration = End time - Start

time.
User Information
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Call ID
N/A
N/A
ID that uniquely identifies a

Call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1672
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

can view the IMSI
information.
IMSI is displayed only when
the EPC is not
interconnected.
STMSI
N/A
N/A
subscriber.
NOTE
STMSI is displayed only when
the EPC is not interconnected.
User ID:Alias
N/A
N/A

task.
Issue 03 (2015-07-30)
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
MMEC
BIT STRING
(SIZE (8))
bit
MME code.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
mTMSI
BIT STRING
(SIZE (32))
bit
mTMSI information of a
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eNodeB UE
S1AP ID
[0,2^32-1]
N/A

UE on an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1673
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MME UE
S1AP ID
[0,2^32-1]
N/A

UE on an MME.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
IMEI-TAC
00000000-9999
9999
N/A
First eight digits in the IMEI

of a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

equipment identity for short
and TAC is type approval
code for short.
Issue 03 (2015-07-30)
Terminal
Model
N/A
N/A
Model of a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UE Capability
N/A
N/A
Access capability of a UE in
terms of RAT support,
protocol version support,
GERAN PS handover
support, device type, and
terminal type.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>FGI
N/A
N/A
Specifies the FGI capability

of UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Capability
Related to
PUSCH NonPeriodic CQI/
PMI/RI
Reporting
Support
N/A
Specifies whether the

capability of non-periodically
reporting CQIs, PMIs, or RIs
over the PUSCH is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Capability
Related to
PUCCH
Periodic CQI/
PMI/RI
Reporting
Support
N/A

capability of periodically
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1674
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>RLC UM
SN&PDCP
SN
Support
N/A
Specifies whether the UM

mode is supported at the RLC
layer and so on.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>ShortPeriod DRX
Support
N/A
Specifies whether short-term

DKX control is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>LongPeriod DRX
and Support
DRX Control
at MAC Layer
Support
N/A
Specifies whether DRX

control is supported by the
long-term DRX and at the
MAC layer.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Prioritized
Bit Rate
Support
N/A

prioritized bit rate is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>RLC UM
Support
N/A

layer.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>PS-toUTRAN HO
Capability
Support
N/A

capability of handing over
from PS to UTRAN is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>GERAN
HO Capability
Using SRVCC
Support
N/A

from SRVCC to GERAN is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1675
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>CCO/
NACC
Capability
Support
N/A
Specifies whether the CCO/

NACC capability is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>HO to
1xRTT CS
Using SRVCC
Support
N/A

from SRVCC to 1xRTT CS is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Active HO
from EUTRA
RRC_CONN
ECTED to
CDMA2000
HRPD
Support
N/A

capability of actively handing
over from the EUTRA
RRC_CONNECTED mode
to the CDMA2000 HRPD
mode is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>InterFrequency HO
Capability
Support
N/A
Specifies whether the interfrequency handover

capability is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Intra-RAT
A4/A5
Measurement
Capability
Support
N/A
Specifies whether the intraRAT A4/A5 measurement

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Inter-RAT
B1
Measurement
Capability
Support
N/A
Specifies whether the interRAT B1 measurement

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1676
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Periodic
Measurements
Including
IntraFrequency,
InterFrequency,
and Inter-RAT
Measurements
Support
N/A
Specifies whether periodic

measurement, including
intra-frequency
measurement, interfrequency measurement, and
inter-RAT measurement, is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>IntraFrequency
ANR
Support
N/A
Specifies whether the intrafrequency ANR function is

supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>InterFrequency
ANR
Support
N/A
Specifies whether the interfrequency ANR function is

supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Inter-RAT
ANR
Support
N/A
Specifies whether the interRAT ANR function is

supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Capability
Support
of Supporting
AM or UM
Mode by DRB
N/A
Specifies whether the AM or

UM mode supported by the
DRB is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Intra- or
InterSubframe FH
Capability
N/A
Specifies whether the intraor inter-subframe frequency

hopping capability is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Support

1677
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>UTRAN
B2
Measurement
Capability
Support
N/A

UTRAN B2 measurement
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>GERAN
B2
Measurement
Capability
Support
N/A

GERAN B2 measurement
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>1xRTT B2
Measurement
Capability
Support
N/A
Specifies whether the 1xRTT

B2 measurement capability is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>InterFrequency
Measurement
Capability
(Including
Measurement
Capability
Between TDD
and FDD)
Support
N/A
Specifies whether interfrequency measurement,

including measurement
between TDD and FDD
frequencies, is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>HRPD B2
Measurement
Capability
Support
N/A
Specifies whether the HRPD

supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UTRAN
CS HO
Capability
Using SRVCC
Support
N/A

from SRVCC to UTRAN CS
is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1678
Nastar
Parameter
Issue 03 (2015-07-30)
Range
Unit
Description
Supported
Solution
Version
>>Capability
Support
Related to TTI
Bundling
N/A

capability related to TTI
Bundling is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Capability
Related to
Half-Static
Scheduling
Support
N/A

capability related to halfstatic scheduling is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>HO
Between FDD
and TDD
Support
N/A

between FDD and TDD is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UTRAN
IRAT ANR
Capability
Support
N/A

UTRAN IRAT ANR
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>GERAN
IRAT ANR
Capability
Support
N/A

GERAN IRAT ANR
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>1xRTT/
2xRTT IRAT
ANR
Capability
Support
N/A

1xRTT/2xRTT IRAT ANR
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>HRPD
IRAT ANR
Capability
Support
N/A

IRAT ANR capability is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1679
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Support
RAT
EUTRAN
N/A
RATs supported by a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Protocol versions supported

by a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Whether a UE supports interRAT handover to GERAN

PS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
battery consumption
optimization.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UTRAN
GERAN CS
GERAN PS
CDMA2000 1X
>Supported
Protocol
Version
Number
REL-8
>Support HO
to GERAN PS
domain
Yes
>Device Type
N/A
REL-9
REL-10
No
The UE does not
report capability
indicator
information.
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
Class
Category 1
Category 2
N/A
Uplink and downlink

capability of UE.
Category 3
Category 4
Category 5
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1680
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Physical
Layer
Parameter
N/A
N/A
Uplink physical layer

parameter related to UE
category.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum
Number of
Uplink-SCH
Transport
Block Bits
Transmitted
within a TTI
N/A
N/A
Maximum number of ULSCH transport block bits

transmitted within a TTI.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum
Number of
Bits of an
Uplink-SCH
Transport
Block
Transmitted
within a TTI
N/A
N/A
Maximum number of bits of

an UL-SCH transport block
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Support for
64QAM in
Uplink
Yes
N/A
Whether support for 64QAM

in UL.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Downlink
Physical
Layer
Parameter
N/A
N/A
Downlink physical layer

category.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum
Number of
DownlinkSCH
Transport
Block Bits
Received
within a TTI
N/A
N/A
Maximum number of DLSCH transport block bits

received within a TTI.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

1681
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Maximum
Number of
Bits of a
DownlinkSCH
Transport
Block
Received
within a TTI
N/A
N/A
Maximum number of bits of a

DL-SCH transport block
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum
Number of
Supported
Layers for
Spatial
Multiplexing
in Downlink
N/A
Maximum number of
supported layers for spatial
multiplexing in DL.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
2
4
8
2 or 4
Access Information
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Time
N/A
N/A
Time when a UE accesses a

cell at the beginning of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Access Cell
1 to 64
characters
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The parameter value is in the

following format: eNodeB
name: cell name (eNodeB
ID:cell ID).
Issue 03 (2015-07-30)
Access Physical
eNodeB ID
[0,104857
5]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1
Access Physical
LocalCell ID
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1

1682
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Physical
Sector
Equipment or
Equipment
Group ID
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1
Access TA
[0,1314]
16*Ts=0.5
2 ms
Time advance (TA) during the

access of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Access Uplink
RSRP
[-150,-30]
dBm
Reference signal received

power (RSRP) on the uplink
during the access of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Access Uplink
SINR
[-15,35]
dB
SINR on the uplink during the

access of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1683
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Type
IntraRAT
RRC
Access
N/A

defined.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Cause in the RRC setup

request message.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Complete time during the

access of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Incoming
HO/IntraRAT
Incoming
HO
Incoming
HO/
UTRAN
Incoming
HO
Incoming
HO/
GERAN
Incoming
HO
Incoming
HO
Access Cause
Emergenc
y
High
Priority
Access
MtAccess
Mosignaling
Mo-Data
N/A
Access
Complete Time
Issue 03 (2015-07-30)
N/A

1684
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Delay
Time
N/A
The delay time between the

time of access request and the
time of access completion.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Release Information
Parameter
Range
Unit
Description
Supported
Solution
Version
Release Time
N/A
N/A
Time when the link is released at the

end of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Release Cell
1 to 64
character
s
N/A
Cell from which a UE is released at

the end of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
N/A
CSFB
Issue 03 (2015-07-30)

following format: eNodeB name: cell
name (eNodeB ID:cell ID).
CSFB information.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1685
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>CSFB
Triggering
Cause
CSFB:V
OICEEmergen
cy call
N/A
The triggering cause indicated by a

CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates whether an eNodeB

successfully responds to the CSFP
indication from the MME.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
CSFB:V
OICENonemergen
cy call
CSFB:L
CS-Nonemergen
cy call
>CSFB
Response
Respons
e
No
Respons
e
Interworking
Information
N/A
N/A
Interworking Information.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Blind or
Measurement
l Blind
N/A
Used for determining whether the UE

received MR report before handover
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>With SIBInfo
l Yes
N/A
Used for determining whether RRC

Connection Release message which
sent by eNodeB was with SIBInfo.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
l Meas
urem
ent
l No
Issue 03 (2015-07-30)

1686
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Triggering
Cause
l CSF
B
N/A
Interworking triggering Cause.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Release cause based on RRC of a

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
l SRV
CC
l Other
RRC Release
Cause
Load
balancin
g TAU
Other
CS
Rollback
to High
Priority
UE Context
Release Cause
N/A
N/A
Release cause based on UE context

release of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Handover
Release Cause
Handove
r based
on the
distance
N/A
Release cause based on the last

handover release of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Handove
r based
on the
coverage
Handove
r based
on the
load
balancin
g
Issue 03 (2015-07-30)

1687
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MSG4's HARQ
Final State
l 0
NAC
K
N/A
State of the MSG4's HARQ.
eRAN11.0
l 1
ACK
l 2
DTX
Issue 03 (2015-07-30)
Release
Information
N/A
N/A
Cause of a failed release.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Release Type
N/A
N/A
Type of the cause of a failed release.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Release
Reason
N/A
N/A
Details about the cause of a failed

release.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cause
N/A
N/A
Internal release failure cause.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Error Detail
Cause
N/A
N/A
Detailed cause value obtained from

internal CHRs.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1688
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Call
Procedure Type
N/A
N/A
Information about the status of the

call procedure.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DC Err Type
N/A
N/A
Type of an abnormal call procedure.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DC Detail
value
N/A
N/A
Detailed cause of an abnormal call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Re-setup Information
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC
Reestablishmen
t Count
[0,+)
N/A
Times of RRC
connection resetup.
eRAN 7.0/
eRAN 8.0/
eRAN 8.1
Handover
Triggered RRC
Reestablishmen
t Result
N/A
N/A
Number of RRC
connection resetup triggered
by failed
handovers.
eRAN 7.0/
eRAN 8.0/
eRAN 8.1

1689
Nastar
Signaling Flow Analysis

Parameter
Range
Unit
Description
Supported
Solution
Version
No.
[1,+)
N/A
Number that uniquely identifies

a sent and received signaling
message.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Signaling Time
N/A
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Signaling Direct
No
Direction
N/A
Direction for sending or

receiving a signaling message.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A

transmitted over the S1-MME or
Uu interface.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Uplink
Downlink
Signaling Type
N/A

Signaling
Content
N/A
N/A
Content for sending or receiving

Note: it will display the contents
only for the all-signaling
analysis.
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1690
Nastar
Measurement Report Analysis

Parameter
Range
Unit
Description
Supported
Solution
Version
No.
[1,+)
N/A
Number that is added

sequentially from 1.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Measurement
Time
N/A
N/A
Local time on the eNodeB

when an MR is generated.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
MR Type
EVENT_MR
N/A
The type of MR including

event MR, intra-frequency
MR of periodic MR, private
UE MR of periodic MR and
period private throughput
measurement MDT.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
PRE_INTRA_F
REQ_MR
PRE_UE_MR
NOTE
Period private throughput
measurement MDT is
supported only on eRAN8.1/
eRAN11.0.
Access Type
EUTRAN
N/A
RAT type of an MR for

inter-RAT measurement.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Type of a measurement
object in an MR.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates the measure cell

information of MR, which
displays as eNodeBID:
CellID.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UTRAN
GERAN
CDMA2000
TD-SCDMA
Measurement
Object Type
Server
Nbr1
Nbr2
Nbr...
Measure Object
Issue 03 (2015-07-30)
N/A

1691
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
EARFCN/
ARFCN
LTE:[0,65535]
N/A
Indicates the cell ARFCNs

of the LTE, GSM, or TDSCDMA network.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates the physical

identify code of the cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
TD-SCDMA:
[0,65535]
GSM:[0,1023]
PCI/P-SC/
BSIC/PN
LTE:[0,503]
UMTS:[0,511]
RSRP/RSCP/
RSSI/Pilot
Strength
TD-SCDMA:
[0,127]
LTE: PCI
GSM:[00,77]
GSM: BSIC
CDMA:[0,511]
CDMA: PN
LTE:[-150,-30]
UMTS/TD-SCDMA: P-SC
dBm
UMTS/TDSCDMA:
[-116,-25]
Indicates the signal strength

of the cell.
LTE: RSRP
UMTS/TD-SCDMA:
RSCP
GSM/CDMA:
[0,63]
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GSM: RSSI
CDMA: Pilot Strength
RSRQ/EcNo
LTE:
[-19.5,-2.5]
dB
UMTS:
[-31.5,0]
Issue 03 (2015-07-30)
Frequency Band
Indicator
DCS1800
UL DM RSRP
[-150,-30]
Indicates the signal quality

of the cell.
LTE: RSRQ
UMTS: Ec/No
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Frequency band indicator of

a neighboring cell when the
measurement type is interRAT and the RAT is
GERAN in an MR.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
dBm
Indicates the RSRP of

uplink DMRS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
PCS1900

1692
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
UL DM SINR
[-15,35]
dB
Indicates the SINR of

downlink DMRS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL IBLER
[0.00,100.00]
Indicates the block error

rate on the uplink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL IBLER(0)
[0.00,100.00]

rate of the code 0 on the
downlink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL SINR
[-15,35]
dB
Indicates the SINR on the

uplink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL CQI(0)
[0,26]
N/A
Indicates the CQI of the

code 0 on all bandwidth of
the downlink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1693
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
UL MIMO
Mode
1T1R
N/A
Indicates the MIMO mode

on the uplink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1T2R
2T2R
VIRTUAL
MIMO
1T4R
2T4R
VIRTUAL
MIMO
1T8R BEAM
FORMING
2T28R BEAM
FORMING
Issue 03 (2015-07-30)

1694
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
DL MIMO
Mode
TX_MODE_SI
NGLE_ANT_P
ORT_0
N/A

on the downlink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates the RANK value

reported by the UE at the
last time.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates the total use times

of the RB on the uplink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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
Rank2
UL RB Use
Times
Issue 03 (2015-07-30)
[0,4294967295]

1695
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
DL RB Use
Times
[0,4294967295]
N/A

of the RB on the downlink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Initial
Transmission
DL Grant
[0,+)
Numbe
r

downlink UE is scheduled
during initial transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL Grant
[0,+)
Numbe
r
Number of times that an

uplink UE is scheduled,
including initial
transmissions and
retransmissions.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion of
Dual
Codewords in
Initial
Transmission
[0.00,100.00]
Proportion of dual
codewords during initial
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL
Retransmission
Rate
[0.00,100.00]
Uplink retransmission rate.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL
Retransmission
Rate
[0.00,100.00]
Downlink retransmission
rate.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1696
Nastar
Mobility Management Information

Parameter
Range
Unit
Description
Supported
Solution
Version
No.
[1,+)
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Abnormal
N/A
Field indicating an abnormal

handover.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Blank
The value of this field is ! if

the value of Handover Result
is either of the following:
HO Preparation Succeeded/
HO Failure
HO Preparation Failure/
NULL
Otherwise, the value of this
field is blank.
Issue 03 (2015-07-30)

1697
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover
Triggering
Cause
Based on
distance
N/A
The triggered cause of a

handover.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Based on
coverage area
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_nonemergency call
Based on
coverage
area_nonemergency call
Based on
bearer_nonemergency call
Based on
service_nonemergency call
Based on
uplink
quality_nonemergency call
Based on
frequency
priority_nonemergency call
Based on
CSFB_nonemergency call
Issue 03 (2015-07-30)

1698
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
Handover type during a voice

service.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Based on
CSFB_emergen
cy call
Based on
HPLMN
return_nonemergency call
Based on other
causes_nonemergency call
Based on other
causes_emerge
ncy call
HO Type Voice
NON_SRVCC
CS_ONLY_SR
VCC
CS_AND_PS_
SRVCC
Issue 03 (2015-07-30)

1699
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover Type
Intra-RAT
outgoing
handover/Intrafrequency
handover
N/A
Handover type during a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
outgoing
handover/Interfrequency
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 03 (2015-07-30)

1700
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover
Interface Type
The handover
interface types
of intra-RAT
handover are the
following:
N/A
Interface types involved in a

handover during a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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.
Issue 03 (2015-07-30)
Begin Time
N/A
N/A
Preparation time for initiating

an incoming or outgoing intraRAT or inter-RAT handover
during a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Interval
[0,+)
Interval = Start time - End

time.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1701
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong
Interval
Yes
N/A
If the interval exceeds the

overlong xxx delay threshold,
the value of this parameter is
Yes. Otherwise, the value of
this parameter is No.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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
threshold;
Overlong intra-RAT
incoming handover delay
threshold.
End Time
N/A
N/A
End time.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Source Cell
N/A
N/A
Source cell from which a call

is handed over.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

ID:cell ID).
Issue 03 (2015-07-30)
HO Physical
eNodeB ID
[0,1048575]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
HO Physical
LocalCell ID
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
HO Physical
Sector
Equipment ID
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1702
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Source Cell
RSRP
[-150,-30]
dBm
RSRP of the serving cell on

the uplink during the
handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Source Cell
RSRQ
[-15,35]
dB
RSRQ of the serving cell on

handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Target Cell
N/A
N/A
Target cell to which a call is

handed over.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

ID:cell ID).
Target Cell
RSRP/RSCP/
RSSI
[-150,-30]
dBm
RSRP/RSCP/RSSI of the
serving cell during the
handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Target Cell
RSRQ/EcNo
[-19.5,-2.5]
dB
RSRQ/EcNo of the serving

cell during the handover of a
call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Handover
Preparation
Triggering
Cause
Radio Network
Layer
N/A
Triggering cause of the

preparation of an outgoing
handover during a call. The
preparation triggering cause
of an incoming handover is
empty.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Transport
Layer
NAS Layer
Protocol Layer
Miscellaneous
Issue 03 (2015-07-30)

1703
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover
Preparation
Failure Cause
Handover
preparation to
target cell
failure
N/A
Cause of a failed outgoing

cause of a failed incoming
handover is empty.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Whether the HANDOVER

CANCEL message is received
during the handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Protocol cause initiated due to

a canceled handover. For
details, see 9.2.1.3 and 9.2.6 in
3GPPTS36.413
specifications.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates whether data is

transmitted during the
handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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
Handover
Yes
Reason for
Canceling HO
Radio Network
Layer Cause
No
Transport
Layer Cause
NAS Layer
Cause
Protocol Layer
Cause
Other Cause
With Data
Transmission
Issue 03 (2015-07-30)
Yes
No

1704
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover
Result
HO Preparation
Succeed/HO
Execution
Succeed
N/A
Handover result of a call,

including the handover
preparation result and
handover execution result.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
HO Preparation
Succeed/HO
Execution
Failure
HO Preparation
Failure/NULL
HO Preparation
Succeeded/HO
SUCC WITH
REEST
Issue 03 (2015-07-30)
TA upon
Handover
[0,1314]
16*T
s=0.5
2 ms

handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULRSRP upon
Handover
[-150,-30]
dBm

power (RSRP) on the UL
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULSINR upon
Handover
[-15,35]
dB
SINR on the UL during the

handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB ID
[0,15]
N/A
ID of the E-RAB that is

handed over.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1705
Nastar
Parameter
Range
Unit
Description
E-RAB QCI
GBR(QCI1)
N/A
Service type for which ERAB is handed over. The

parameter values are as
follows:
GBR(QCI2)
GBR(QCI3)
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)
Supported
Solution
Version
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
GBR (QCIN): GBR service
with high QoS. N = 1, 2, 3, or eRAN11.0
4. QCI is QoS class identifier
for 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.
Non GBR
(QCI7)
Non GBR
(QCI8)
Non GBR
(QCI9)
E-RAB
Handover
Preparation
Result
Succeed
N/A
Result of accessing an E-RAB

during an incoming handover.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Failure
E-RAB Analysis
Parameter
Range
Unit
Description
Supported
Solution
Version
No.
[1,+)
N/A
Serial number of an E-RAB

ID. It uniquely identifies an ERAB ID.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Abnormal
N/A
Indicates whether an E-RAB

is abnormal.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Blank
Issue 03 (2015-07-30)

1706
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Abnormal
N/A
Setup result of an E-RAB

setup request.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Cause
Procedure
Complete
N/A
Cause of failed E-RAB setup.

The parameter value also
includes detailed causes.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
QCI level on E-RAB setup.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Blank
Radio Network
Layer Cause
Transport
Layer Cause
NAS Cause
Protocol Cause
Miscellaneous
Cause
Incoming HO
No Responding
After E-RAB
Setup Request
E-RAB Request
Service Type
(QCI) on ERAB Setup
GBR(QCI1)
GBR(QCI2)
The parameter values are as

follows:
GBR(QCI3)

with high QoS. N = 1, 2, 3, 4.
QCI is QoS class identifier for
short and GBR is guaranteed
bit rate for short.
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)

6, 7, 8, or 9.
Non GBR
(QCI7)
Non GBR
(QCI8)
Non GBR
(QCI9)
E-RAB Request
Time
Issue 03 (2015-07-30)
N/A
N/A
Time when E-RAB is

requested.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1707
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell on E-RAB
Request
N/A
N/A
Cell when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
SGW IP
Displaying
example of
IPV4:
10.22.33.44
N/A
Transport Layer IP.
eRAN 7.0
SPC800/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Displaying
example of
IPV6:
fe80:981c:981c:
237:fd93:4dea:f
d93:4dea
Issue 03 (2015-07-30)
E-RAB Setup
Time
N/A
N/A
Time of RAB setup.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
TA on E-RAB
Setup
[0,1314]
16*Ts
=0.52
ms

E-RAB setup of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULRSRP on ERAB Setup
[-150,-30]
dBm

during the E-RAB setup of a
call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULSINR on ERAB Setup
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1708
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Release
Abnormal
N/A
Release result of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Release
Cause
Procedure
Complete
N/A
Cause of E-RAB release.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Identifier indicating whether

data is being transmitted when
an E-RAB is released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Blank
Radio Network
Layer Cause
Transport
Layer Cause
NAS Cause
Protocol Cause
Miscellaneous
Cause
RRC
Establishment
Cause
RRC Release
Cause
RRC
Reestablishmen
t Cause
E-RAB Data on
E-RAB Release
Yes
No
If no data is being transmitted

when the E-RAB is released,
the subscriber cannot perceive
the exception.
E-RAB Request
Service Type
(QCI) on ERAB Release
GBR[1,4]
Non GBR[5,9]
N/A
QCI level on E-RAB release.

bit rate for short.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

6, 7, 8, or 9.
Issue 03 (2015-07-30)

1709
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Release
Complete Time
N/A
N/A
Time when an E-RAB is

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cells Released
for E-RAB
1 to 64
characters
N/A
Cell from which an E-RAB is

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Physical
eNodeB ID
Released For ERAB
[0,1048575]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Physical
LocalCell ID
Released For ERAB
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Physical Sector
Equipment ID
Released For ERAB
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
TA on E-RAB
Release
[0,1314]
16*Ts
=0.52
ms

E-RAB release of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULRSRP on ERAB Release
[-150,-30]
dBm

during the E-RAB release of a
call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULSINR on ERAB Release
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1710
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Delay
[0,+)
Secon
d
Setup delay of E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
Duration
[0,+)
Secon
d
Duration of E-RAB.
Total Uplink
Traffic Volume
(0.0,+)
MB
Total volume of uplink traffic

generated from an RAB in an
eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Uplink
Transmission
Duration
(0.000,+)
Total duration of transmitting

uplink data for an RAB in an
eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0.000,+)
kbit/s
Average uplink throughput

for an RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Downlink
Traffic Volume
(0.0,+)
MB
Total volume of downlink

traffic generated from an RAB
in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Downlink
Transmission
Duration
(0.000,+)

downlink data for an RAB in
an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup Delay = E-RAB

Setup Time - E-RAB Request
Time.
E-RAB Duration = E-RAB

Release Time - E-RAB Setup
Time

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1711
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Throughput
[0.000,+)
kbit/s
Average downlink throughput

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Uplink VQI
[0.0,5.0]
N/A
Average VQI value for uplink

voice services borne by an
RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Downlink VQI
[0.0,5.0]
N/A
Average VQI value for

downlink voice services borne
by an RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Detail E-RAB Information(QCI2 to QCI9)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB ID
N/A
N/A
E-RAB ID.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Info
N/A
N/A
The information during the ERAB setup of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1712
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB
Request Service
Type(QCI) on
E-RAB Setup
GBR(QCI1)
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GBR(QCI2)

follows:
GBR(QCI3)

bit rate for short.
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)

6, 7, 8, or 9.
Non GBR
(QCI7)
Non GBR
(QCI8)
Non GBR
(QCI9)
Issue 03 (2015-07-30)
>E-RAB
Request Time
N/A
N/A
Time when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cell on ERAB Request
N/A
N/A
Cell when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB Setup
Time
N/A
N/A
Time of RAB setup.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB Setup
Result
Succeed
N/A

setup request.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Failure

1713
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Setup
Cause
Procedure
Complete
N/A
Cause of E-RAB setup. The

parameter value also includes
detailed causes.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Radio Network
Layer Cause
Transport
Layer Cause
NAS Cause
Protocol Cause
Miscellaneous
Cause
Incoming HO
No Responding
After E-RAB
Setup Request
>E-RAB Setup
Delay
Estimation
N/A
N/A
Delay information about the

setup of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>E-RAB
Setup Delay
[0,+)
Second
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Long E-RAB
Setup Delay
Yes
E-RAB Setup Delay = ERAB Setup Time - E-RAB

Request Time.
N/A
No
Used for determining

whether an E-RAB setup
delay is exceedingly long.
An E-RAB setup delay is
exceedingly long if it is
greater than or equal to the
threshold for long E-RAB
setup delay.
>MR
Information on
E-RAB Setup
Issue 03 (2015-07-30)
N/A
N/A
MR information during the ERAB setup of a call.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1714
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>TA
[0,1314]
16*Ts
=0.52
ms
Time advance (TA) during

the E-RAB setup of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL RSRP
[-150,-30]
dBm

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL SINR
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Priority
N/A
N/A
Priority information of an ERAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Priority
High-priority
N/A
Priority of a setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Preempting capability of a
setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Preempted capability of a
setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
mediumpriority
low-priority
>>E-RAB
Active
Preemptability
Shall not
trigger preemption
May trigger
pre-emption
>>E-RAB
Passive
Preemptability
Issue 03 (2015-07-30)
Not preemptable
Pre-emptable

1715
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Rate
Information
N/A
N/A
Rate information of an ERAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum ERAB DL Rate
[0, 10,000,000]
Mbit/s
Maximum downlink rate of a

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Assured ERAB DL Rate
[0, 10,000,000]
Mbit/s
Assured downlink rate of a

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum ERAB UL Rate
[0, 10,000,000]
Mbit/s
Maximum uplink rate of a

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Assured ERAB UL Rate
[0, 10,000,000]
Mbit/s
Assured uplink rate of a setup

E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>SGW IP
Displaying
example of
IPV4:
10.22.33.44
N/A
Transport Layer IP.
eRAN 7.0
SPC800/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Displaying
example of
IPV6:
fe80:981c:981c:
237:fd93:4dea:f
d93:4dea
Issue 03 (2015-07-30)

1716
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Release
Information
N/A
N/A
The information during the ERAB release of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Request Service
Type(QCI) on
E-RAB Release
GBR[1,4]
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Non GBR[5,9]

bit rate for short.
6, 7, 8, or 9.
Issue 03 (2015-07-30)
>E-RAB
Release Request
Time
N/A
N/A
Time when an E-RAB release

request is started.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Release
Complete Time
N/A
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Duration
[0,+)
Second
Duration of E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cells Released
for E-RAB
1 to 64
characters

Time
N/A

released.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1717
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Physical
eNodeB ID
Released For ERAB
[0,1048575]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Physical
LocalCell ID
Released For ERAB
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Physical
Sector
Equipment ID
Released For ERAB
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Release Cause
E-RAB
abnormal
release
triggered by
MME
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
End where an E-RAB is

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
abnormal
release
triggered by
eNodeB
E-RAB
abnormal
release
triggered by
outgoing HO
execution
failure
>Initiating Party
of E-RAB
Release
Issue 03 (2015-07-30)
MME
eNodeB

1718
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Data
on E-RAB
Release
Yes
N/A

data is being transmitted
when an E-RAB is released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

the subscriber cannot
perceive the exception.
Issue 03 (2015-07-30)
>MR
Information on
E-RAB Release
N/A
N/A
MR information during the ERAB release of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>TA
[0,1314]
16*Ts
=0.52
ms

the E-RAB release of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL RSRP
[-150,-30]
dBm

during the E-RAB release of
a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL SINR
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Process
Information
N/A
N/A
Information about the setup

of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1719
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>Statistics of
Data
Transmission
N/A
N/A
Statistics on data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total Uplink
Traffic Volume
(0.0,+)
MB

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total Uplink
Transmission
Duration
(0.000,+)

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Average
Uplink
Throughput
[0,+)
kbit/s

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Low Average
Uplink
Throughput
Yes
N/A
Indicates whether the average

uplink throughput for an
RAB in an eNodeB is less
than the threshold for low
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total
Downlink
Traffic Volume
(0.0,+)
MB

traffic generated from an
RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total
Downlink
Transmission
Duration
(0.000,+)

an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

1720
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Average
Downlink
Throughput
[0,+)
kbit/s

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Low Average
Downlink
Throughput
Yes
N/A

downlink throughput for an
average downlink
throughput.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No
Detail E-RAB Information(QCI1)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB ID
N/A
N/A
E-RAB ID.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Info
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1721
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB
Request Service
Type(QCI) on
E-RAB Setup
GBR(QCI1)
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GBR(QCI2)

follows:
GBR(QCI3)

bit rate for short.
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)

6, 7, 8, or 9.
Non GBR
(QCI7)
Non GBR
(QCI8)
Non GBR
(QCI9)
Issue 03 (2015-07-30)
>E-RAB
Request Time
N/A
N/A
Time when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cell on E-RAB
Request
N/A
N/A
Cell when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB Setup
Time
N/A
N/A
Time of RAB setup.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB Setup
Result
Succeed
N/A

setup request.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Failure

1722
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Setup
Cause
Procedure
Complete
N/A

detailed causes.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Radio Network
Layer Cause
Transport
Layer Cause
NAS Cause
Protocol Cause
Miscellaneous
Cause
Incoming HO
No Responding
After E-RAB
Setup Request
>E-RAB Setup
Delay
Estimation
N/A
N/A

setup of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>E-RAB
Setup Delay
[0,+)
Secon
d
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Long E-RAB
Setup Delay
Yes
N/A
Used for determining whether

an E-RAB setup delay is
exceedingly long.
No

Time.

exceedingly long if it is greater
than or equal to the threshold
for long E-RAB setup delay.
>MR
Information on
E-RAB Setup
Issue 03 (2015-07-30)
N/A
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1723
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>TA
[0,1314]
16*Ts
=0.52
ms

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL RSRP
[-150,-30]
dBm

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL SINR
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Priority
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Priority
High-priority
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
mediumpriority
low-priority
>>E-RAB
Active
Preemptability
Shall not
trigger preemption
May trigger
pre-emption
>>E-RAB
Passive
Preemptability
Issue 03 (2015-07-30)
Not preemptable
Pre-emptable

1724
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Rate
Information
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Release
Information
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1725
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB
Request Service
Type(QCI) on
E-RAB Release
GBR[1,4]
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Non GBR[5,9]

bit rate for short.
6, 7, 8, or 9.
Issue 03 (2015-07-30)
>E-RAB
Release Request
Time
N/A
N/A

request is started.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Release
Complete Time
N/A
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Duration
[0,+)
Secon
d
Duration of E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cells Released
for E-RAB
1 to 64
characters
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Physical
eNodeB ID
Released For ERAB
[0,1048575]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Physical
LocalCell ID
Released For ERAB
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Time

1726
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Physical
Sector
Equipment ID
Released For ERAB
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Release Cause
E-RAB
abnormal
release triggered
by MME
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
abnormal
release triggered
by eNodeB
E-RAB
abnormal
release triggered
by outgoing HO
execution
failure
>Initiating Party
of E-RAB
Release
MME
>E-RAB Data
on E-RAB
Release
Yes
eNodeB
No

the exception.
>MR
Information on
E-RAB Release
Issue 03 (2015-07-30)
N/A
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1727
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>TA
[0,1314]
16*Ts
=0.52
ms

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL RSRP
[-150,-30]
dBm

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL SINR
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Process
Information
N/A
N/A

an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Statistics of
Voice Quality
N/A
N/A
Statistics on the voice quality

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI
[0.0,5.0]
N/A

RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI as
Excellent Times
[0,65535]
Numb
er

average VQI value for uplink
RAB in an eNodeB is greater
than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1728
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>UL VQI as
Good Times
[0,65535]
Numb
er

than 3.6 but is less than or
equal to 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI as
Accept Times
[0,65535]
Numb
er

equal to 3.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI as
Poor Times
[0,65535]
Numb
er

equal to 3.1.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI as
Bad Times
[0,65535]
Numb
er

RAB in an eNodeB is less than
or equal to 2.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Poor Uplink
VQI
Yes
N/A

VQI value for uplink voice
services borne by an RAB in
an eNodeB is less than the
threshold for poor uplink VQI.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Uplink Voice
Frame Error
Rate (Including
Error Packets
and Delay
Packets)()
[0,1000]
N/A
Average frame deletion rate

(covering error packets and
delayed packets) for uplink
RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Proportion of
Uplink Voice
Delay Packets
()
[0,1000]
N/A
Proportion of delayed uplink

voice packets borne by an
RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

1729
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>DL VQI
[0.0,5.0]
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Excellent Times
[0,65535]
Numb
er

average VQI value for
by an RAB in an eNodeB is
greater than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Good Times
[0,65535]
Numb
er

greater than 3.6 but is less than
or equal to 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Accept Times
[0,65535]
Numb
er

or equal to 3.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Poor Times
[0,65535]
Numb
er

or equal to 3.1.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Bad Times
[0,65535]
N/A

less than or equal to 2.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Poor
Downlink VQI
Yes
N/A

VQI value for downlink voice
threshold for poor downlink
VQI.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

1730
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Downlink
Voice Frame
Error Rate
(Including Error
Packets and
Delay Packets)
()
[0,1000]
N/A

delayed packets) for downlink
RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Statistics of
Data
Transmission
N/A
N/A
Statistics on data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total Uplink
Traffic Volume
(0.0,+)
MB

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total Uplink
Transmission
Duration
(0.000,+)

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Average
Uplink
Throughput
[0,+)
kbit/s
Average uplink throughput for

an RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Low Average
Uplink
Throughput
Yes
N/A

uplink throughput for an RAB
in an eNodeB is less than the
threshold for low average
uplink throughput.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total
Downlink
Traffic Volume
(0.0,+)
MB

in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

1731
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Total
Downlink
Transmission
Duration
(0.000,+)

an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Average
Downlink
Throughput
[0,+)
kbit/s

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Low Average
Downlink
Throughput
Yes
N/A

the threshold for low average
downlink throughput.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No
Trend Analysis-Process Traffic Statistics
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
No.
N/A
N/A
Serial number of a record.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cell
N/A
N/A
Information about a cell in

which traffic is consumed.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1732
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Record Time
N/A
N/A
Period within which traffic

is consumed.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Uplink MCS
N/A
N/A
Uplink MCS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Downlink MCS
N/A
N/A
Downlink MCS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB ID
N/A
N/A
ID of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB QCI
GBR(QCI1)
N/A
QCI of an E-RAB. The

follows:
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GBR(QCI2)
GBR(QCI3)
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)
Non GBR
(QCI7)
Non GBR
(QCI8)

with high QoS. N = 1, 2, 3,
or 4. QCI is QoS class
identifier for short and
GBR is guaranteed bit rate
for short.
Non GBR (QCIN): nonGBR service with low QoS.
N = 5, 6, 7, 8, or 9.
Non GBR
(QCI9)
Issue 03 (2015-07-30)

1733
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink
Throughput
[0,+)
MB
Uplink Throughput within

a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Uplink
Transmission
Duration
[0,+)
Duration of transmitting
uplink data within a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0,+)
kbit/s
Average Uplink throughput

within a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Downlink
Throughput
[0,+)
MB
Downlink Throughput
within a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Downlink
Transmission
Duration
[0,+)
downlink data within a
period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Throughput
[0,+)
kbit/s
Average downlink
throughput within a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1734
Nastar
Trend Analysis-Cell-Process Voice Statistics

Paramet
er
Range
Unit
Description
Supported
Solution
Version
No.
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Record
Time
N/A
N/A
Time when a voice service is

recorded.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cell
N/A
N/A
Information about a cell in which

a voice service is used.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
ID
N/A
N/A
ID of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
QCI
GBR(QCI1)
N/A
QCI of an E-RAB. The parameter

values are as follows:
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GBR(QCI2)
GBR (QCIN): GBR service with

high QoS. N = 1, 2, 3, or 4. QCI
is QoS class identifier for short
and GBR is guaranteed bit rate
for short.
GBR(QCI3)
GBR(QCI4)
Non GBR(QCI5)
Non GBR(QCI6)

service with low QoS. N = 5, 6,
7, 8, or 9.
Non GBR(QCI7)
Non GBR(QCI8)
Non GBR(QCI9)
UL VQI
Issue 03 (2015-07-30)
[0.0,5.0]
N/A

voice services.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1735
Nastar
Issue 03 (2015-07-30)
Paramet
er
Range
Unit
Description
Supported
Solution
Version
UL VQI
as
Excellent
Times
[0,65535]
Num
ber
Number of times that the VQI

value for uplink voice services is
greater than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL VQI
as Good
Times
[0,65535]
Num
ber

greater than 3.6 but is equal to or
less than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL VQI
as Accept
Times
[0,65535]
Num
ber

less than 3.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL VQI
as Poor
Times
[0,65535]
Num
ber

less than 3.1.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL VQI
as Bad
Times
[0,65535]
Num
ber

equal to or less than 2.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL FER
[0,1000]
N/A

delayed packets) for uplink voice
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL Out
Delay
Ratio()
[0,1000]
N/A
Out delay rate for uplink voice

services borne by an RAB in an
eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1736
Nastar
Issue 03 (2015-07-30)
Paramet
er
Range
Unit
Description
Supported
Solution
Version
DL VQI
[0.0,5.0]
N/A
Average VQI value for downlink

voice services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as
Excellent
Times
[0,65535]
Num
ber

value for downlink voice services
is greater than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as Good
Times
[0,65535]
Num
ber

is greater than 3.6 but is equal to
or less than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as Accept
Times
[0,65535]
Num
ber

or less than 3.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as Poor
Times
[0,65535]
Num
ber

or less than 3.1.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as Bad
Times
[0,65535]
Num
ber

is equal to or less than 2.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL FER
[0,1000]
N/A

voice services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

1737
Nastar
4.10.8 Reference for Complaint Analysis Support Parameters (PS

Core)
This section describes the parameters for PS Core complaint analysis support.
Reference for Complaint Analysis Support Parameters (PS Core) - User Plane
This section describes the parameters for complaint analysis support based on user plane data
on UGW.
Parameters for Viewing PS Core Complaint Analysis Support Results - Summary (UGW)
This section describes the parameters for querying complaint analysis support (summary) results
analysis based on user plane data. You can refer to the description when querying complaint
analysis support (summary) results.
Summary
Parameter
Range
Unit
Description
Supported
Solution
Version
Serial Number
(0,2^31-1)
N/A
Serial number of an xDR in the

summary table. The serial
number is the keyword of a
service and uniquely identifies
a service record. It is an internal
identifier used in the Nastar
system.
PS 12.1
Assoiciated
Signaling Plane
SDR
N/A
N/A
If an associated signaling plane

SDR is available for a user
plane SDR, the association icon
is displayed. Otherwise, the
area is displayed as blank.
PS 12.1
NOTE
This parameter is displayed only
when the Nastar analyzes user
plane and signaling plane data at
the same time.
Issue 03 (2015-07-30)

1738
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
N/A
Whether a service is abnormal.
PS 12.1

service is abnormal.
Blank
If a yellow question mark is

exception type of this service in
the navigation tree is Other and
the exception status is
unknown.
Abnormal
Cause
N/A
N/A
Exception cause of a service.
PS 12.1
Demarcation
Result
RAN Cause
N/A
Demarcation result of an
exception cause.
PS 12.1
UE Cause
SP Cause
CN or SP
Cause
Other Cause
Application
Name
N/A
N/A
Name of an application.
PS 12.1
Service Start
Time
YYYYMM-DD
hh:mm:ss.x
xx
N/A
Time when a service starts.
PS 12.1
Service End
Time
YYYYMM-DD
hh:mm:ss.x
xx
N/A
Time when a service ends.
PS 12.1
Terminal IP
Address
N/A
N/A
IP address of a terminal that

uses services.
PS 12.1
Server IP
Address
N/A
N/A
IP address of a server that

provides services.
PS 12.1
User ID:User
Name
N/A
N/A
User ID, which is randomly

distributed by the system when
creating the task.
PS 12.1
User Name, which is set by the

Issue 03 (2015-07-30)

1739
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
PS 12.1

IMEI-TAC
00000000FFFFFFFF
N/A

a UE.
PS 12.1

short.
Terminal Model
N/A
N/A
Model of a UE.
PS 12.1

using System Function >
Terminal Type Management
UE.
Host Name
N/A
N/A
Name of a host that provides

services.
PS 12.1
RAT
UTRAN
N/A
RAT.
PS 12.1
GERAN
EUTRAN
Cell
N/A
N/A
The format is: eNodeB ID : Cell

ID.
PS 12.1
SGW IP/PGW
IP
Displaying
example of
IPV4:
10.22.33.44
N/A
IP address of the SGW and

PGW.
PS 12.1
N/A
A User agent that provides

services.
PS 12.1
Displaying
example of
IPV6:
fe80:981c:
981c:
237:fd93:4d
ea:fd93:4de
a
User Agent
Issue 03 (2015-07-30)
N/A

1740
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
APN
N/A
N/A
Information about an APN that

provides services.
PS 12.1
Parameters for Viewing PS Core Complaint Analysis Support Results - Web Browsing
(UGW)
This section describes the parameters for querying complaint analysis support (web browsing)
results. You can refer to the description when querying complaint analysis support (web
browsing) results.
Detailed Information--Page Overall Info
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
Page DNS
Response Offset
[0.00,+)
Offset between the time

when the first page DNS
response event occurs and
the time when the page
browsing function is
enabled.
PS 12.1
Page TCP SYN

Offset
[0.00,+)

when the syn packet of the
first page TCP connection is
received and the time when
the page browsing function
is enabled.
PS 12.1
Page TCP SYN

ack Offset
[0.00,+)

when the syn ack packet of
the first page TCP
connection is received and
enabled.
PS 12.1
Page TCP ack

Offset
[0.00,+)

when the last ack packet of
the first page TCP
enabled.
PS 12.1

1741
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
Page First
Request Offset
[0.00,+)

when the first page request
(page redirection request or
main page request) is
initiated and the time when
is enabled.
PS 12.1
Page First
Response Offset
[0.00,+)

is enabled.
PS 12.1
Page First
Redirect
Request Offset
[0.00,+)

when the first page
redirection request is
is enabled.
PS 12.1
Page First
Redirect
Response Offset
[0.00,+)

when the first page
is enabled.
PS 12.1
Page Request
Offset
[0.00,+)

when the main page request
is initiated and the time
when the page browsing
function is enabled.
PS 12.1
Page Response
Offset
[0.00,+)

PS 12.1

1742
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Page TCP
Release Offset
[0.00,+)

when the page TCP
connection is released and
enabled.
PS 12.1
Page TCP connection

release means that the
quintuple of the page TCP
connection releases the
TCP connection.
Detailed Information--Page Response Phase
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Redirect
Count
[0,+)
Numb
er

page redirection occurs
during the page response
phase. This parameter is
calculated when page
redirection exists.
PS 12.1
Page No
Response Wait
Time
[0.00,+)
Time when subscribers

actively close pages (a
UE sends RST or FIN
first) relative to the time
when SYNC appears if
there is no page
response.
PS 12.1
Page Request
Retransmission
Count
[0,+)
Numb
er

page Get request is
retransmitted.
PS 12.1

1743
Nastar
Detailed Information--Page Display Phase

Parameter
Range
Unit
Description
Supported
Solution
Version
Page DNS
[0,+)
Response Count
Number
Number of times that all DNS

requests are responded to
during the page display phase
(between the time when the
main page request is
responded to and the time
function is disabled).
PS 12.1
Wireless
Effective
Throughput
kbit/s
Effective transmission rate on

the RAN side.
PS 12.1
[0.00,
+)
Comprehensive Complaints KQI Information
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Response
Result
Success/Failure
N/A
Result of
responding to a
page request.
PS 12.1
Page Response
Code
N/A
N/A
Page Response
Code.
PS 12.1
Page Display
Success Flag
Success/Failure
N/A
Page display is
successful only
when a main
page request is
successfully
responded to.
Page display
fails if page
redirection
occurs and fails.
PS 12.1

1744
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Download
Throughput
[0,+)
kbit/s
Average page
transmission
rate during the
page display
phase (between
the time when
the main page
request is
responded to
and the time
when the page
browsing
function is
disabled).
PS 12.1
>Page Size
[0,+)
Byte
Total size of
downlink nonretransmission
packets for page
contents
(between the
time when the
main page
request is
initiated and the
time when the
page browsing
function is
enabled) during
the page display
phase.
PS 12.1
Page Browsing
Delay
[0,+)
Page Display
Delay = Page
end time - Page
start time - Page
Response Delay
PS 12.1
The page
display delay
starts when SP
responds with
"2**, 304".
Issue 03 (2015-07-30)

1745
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Response
Delay
[0,+)
Time when the

first page DNS
request is
responded to
relative to the
time when the
main page
request is
responded to.
PS 12.1
If no page DNS
is available, this
parameter
indicates the
time when the
first page syn is
responded to
relative to the
time when the
main page
request is
responded to. If
no page TCP
connection is
available, this
parameter
indicates the
time when the
first page
request is
responded to
relative to the
time when the
main page
request is
responded to.
The value of
Page Response
Code must be
2**, 304, 4**,
5**, 600, 601,
602, or 0xFFFF.
When the value
of Page
Response
Result is 2**,
304, 4**, or 5**,
Issue 03 (2015-07-30)

1746
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Page DNS
Response Delay
is equal to Page
Response
Offset. When
the value of
Page Response
Result is 600,
601, 602, or
0xFFFF, Page
DNS Response
Delay is equal to
Page Request
Offset.
>Page DNS
Response Delay
[0,+)
Page DNS
response delay.
PS 12.1
Page DNS refers

to the DNS
when the first
event of an xDR
is a DNS request
or response
events.
>SYN to SYN
ACK Delay
Issue 03 (2015-07-30)
[0,+)
Delay between
the time when
the first page
syn packet is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first or
second
handshake fails,
the value of this
parameter is 0.

PS 12.1
1747
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>SYN ACK to
First ACK
Delay
[0,+)
Delay between
the time when
the first page
syn ack packet is
responded to
and the time
when the first
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
>SYN ACK to
Last Ack Delay
[0,+)
Delay between
the time when
the first page
syn ack packet is
responded to
and the time
when the last
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
>ACK to Get
Delay
[0,+)
Delay between
the time when
the last page ack
packet of TCP
connection is
responded to
and the time
when the first
page get packet
is responded to.
If the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

1748
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Display
Delay
[0,+)
Page Display
Delay = Page
end time - Page
start time - Page
Response Delay
PS 12.1
The page
display delay
starts when SP
responds with
"2**, 304".
Issue 03 (2015-07-30)
TCP DL Total
Traffic
[0,+)
Byte
Total TCP
downlink data
volume refers to
the total size of
all TCP
downlink
payload
packets,
including
retransmitted
packets, during
the page display
phase (between
the time when
the main page
request is
responded to
and the time
when the page
browsing
function is
disabled).
PS 12.1
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
TCP UL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1

1749
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
TCP DL Out-ofOrder Count
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1
TCP UL Total
Packets
[0,+)
Number
Total number of
all TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL Out-ofOrder Count
[0,+)
Number
Number of
disordered TCP
uplink packets.
PS 12.1
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times when the
uplink TCP
window is set to
0 during the
page display
phase.
PS 12.1

1750
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Upstream
Packet Loss
Count
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.
Downstream
Packet Loss
Count
[0,+)
Number
Downstream
means below the
Iu-PS interface
(below the
RAN).
PS 12.1
Number of
times that
packets are lost
on the
downstream
during the page
display phase.
Issue 03 (2015-07-30)
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
TCP SYN Max

Window Size
N/A
N/A
Maximum size
of the SYN
window of the
page.
PS 12.1
TCP SYN Min

Window Size
N/A
N/A
Minimum size
of the SYN
window.
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.

1751
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP DL Max
Send Window
N/A
N/A
Downlink
sending window
of the maximum
size.
PS 12.1
Parameters for Viewing PS Core Complaint Analysis Support Results - Video Streaming
(UGW)
This section describes the parameters for querying complaint analysis support (video streaming)
results. You can refer to the description when querying complaint analysis support (video
streaming) results.
Detailed Information--Overall Streaming Info

Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming DNS
Response Offset
[0,+)
Offset between
the time when
the video
streaming DNS
responds and the
time when video
streaming starts.
PS 12.1
Video
streaming DNS
refers to the
DNS when the
first event of the
video streaming
is a DNS request
or response
event.
Issue 03 (2015-07-30)

1752
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming TCP
SYN Offset
[0,+)
Offset between
the time when
the first TCP
handshake of
video streaming
occurs and the
time when video
streaming starts.
PS 12.1
Video
streaming TCP
connection
refers to the first
TCP connection
of the video
streaming.
Before this
connection, no
HTTP requests
are initiated.
Time when the
first TCP
handshake of
video streaming
occurs refers to
the time when
the first syn
packet of video
streaming TCP
connection is
responded to.
Issue 03 (2015-07-30)

1753
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming TCP
SYN ACK
Offset
[0,+)
Offset between
the time when
the second TCP
handshake of
video streaming
occurs and the
time when video
streaming starts.
PS 12.1
Video
streaming TCP
connection
refers to the first
TCP connection
of the video
streaming.
Before this
connection, no
HTTP requests
are initiated.
Time when the
second TCP
handshake of
video streaming
occurs refers to
the time when
the first syn ack
packet of video
streaming TCP
connection is
responded to.
Issue 03 (2015-07-30)

1754
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming TCP
ACK Offset
[0,+)
Offset between
the time when
the third TCP
handshake of
video streaming
and the time
when video
streaming starts.
PS 12.1
Video
streaming TCP
connection
refers to the first
TCP connection
of the video
streaming.
Before this
connection, no
HTTP requests
are initiated.
Time when the
third TCP
handshake of
video streaming
occurs refers to
the time when
the last ack
packet of video
streaming TCP
connection is
responded to.
Issue 03 (2015-07-30)

1755
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming First
Request Offset
[0,+)
Offset between
the time when
the first request
of video
streaming is
initiated and the
time when video
streaming is
started.
PS 12.1
The scenario
where no video
streaming
requests are
initiated (that is,
DNS parsing or
TCP connection
of the video
streaming fails)
is not
considered
because video
streaming xDRs
do not exist.
Video
Streaming First
Response Offset
Issue 03 (2015-07-30)
[0,+)
Offset between
the time when
the first request
of video
streaming is
responded to
between the
time when video
streaming starts.

PS 12.1
1756
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming TCP
Release Offset
[0,+)
Offset between
the time when
the video
streaming TCP
connection is
released and the
time when video
streaming starts.
PS 12.1
Video
streaming TCP
connection
release means
that the
quintuple of the
video streaming
TCP connection
releases the TCP
connection.
Issue 03 (2015-07-30)
Video
Streaming
Format
N/A
N/A
Format of video
streaming, such
as FLV, MP4,
3GP, and TS.
PS 12.1
Video
Streaming Total
Size
[0,+)
Byte
Total size of
multiple
segmented
videos after the
videos are
combined.
PS 12.1
Video
Streaming Total
Duration
hh: mm: ss
N/A
Total duration
of multiple
segmented
videos after the
videos are
combined.
PS 12.1

1757
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Segment Bit
Rate
[0,+)
Kbps
Segment code
rate of video
streaming.
PS 12.1
Video
Streaming
Average Bit
Rate
[0,+)
Kbps
Video
Streaming
Average Bit
Rate = (Video
Streaming Start
TCP DL Total
Traffic + Video
Streaming Play
TCP DL Total
Traffic) x 8/
Time that video
streaming can
be played/
10241000.
PS 12.1
Video
Streaming Bit
Rate Obtain
Method
1_Normally Get
Bit Rate
N/A
Method of
obtaining the
video streaming
code rate.
PS 12.1
If multiple flows
of a video
streaming
medium are
transmitted, pay
attention to code
rates of the first
five flows.
2_URI Get
Video Size
Calculate Bit
Rate(Chunk)
3_Chunk
Length
Calculate Bit
Rate
4_Cannot Get
Bit Rate and
Calculate Bit
Rate(Fixed
Size)
5_Same UE IP
and URI Key Bit
Rate
Issue 03 (2015-07-30)

1758
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Transfer
Method
Download,
Non-download
N/A
Transfer mode
of video
streaming.
PS 12.1
Video
Streaming
Merge Method
N/A
N/A
Method of
merging video
segments. This
method is used
only by Huawei
technical
support
engineers.
PS 12.1
Video
Streaming
Finish State
Flag
Finish normally,
Finish with stall
state
N/A
States of
finished video
streaming
playing,
including the
normal state and
pause state.
PS 12.1
Detailed Information--Initial Buffer Period
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
TCP DL Total
Traffic
[0,+)
Byte
Total size of all

TCP downlink
payload
packets,
including
retransmitted
packets, during
the video
streaming
buffering phase
(between the
time when the
first video
streaming
request is
responded to
and the time
when the video
streaming
buffering ends).
PS 12.1

1759
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
Video
Streaming Start
TCP DL
Retransmission
Count
[0,+)
Number
Number of TCP
downlink
retransmitted
packets.
PS 12.1
Video
Streaming Start
TCP DL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
downlink
retransmitted
packets.
PS 12.1
Video
Streaming Start
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
Video
Streaming Start
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1
Video
Streaming Start
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
Video
Streaming Start
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1

1760
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
TCP
Downstream
Total RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Total RTT
Delay
(Accurate) =
Sum of
TCP_DL_Trans
_RTT of all
HTTP response
completion
events of video
streaming.
PS 12.1
Video
Streaming Start
TCP
Downstream
Total RTT
Count
(Accurate)
[0,+)
Number
TCP
Downstream
Total RTT
Count
(Accurate) =
Sum of
TCP_DL_Trans
_RTT_Count of
all HTTP
response
completion
events of video
streaming.
PS 12.1
Video
Streaming Start
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times when the
uplink TCP
window is set to
0 during the
video streaming
display phase.
PS 12.1
Video
Streaming Start
Upstream
Packet Loss
Count
[0,+)
Number
Number of
times that
upstream
packets are lost
during the video
streaming
display phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Issue 03 (2015-07-30)

1761
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
Downstream
Packet Loss
Count
[0,+)
Number
Number of
times that
downstream
packets are lost
during the video
streaming
display phase.
PS 12.1
Downstream
means below the
Iu-PS interface
(below the
RAN).
Video
Streaming Start
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Number of
times that
upstream
packets are lost
due to packet
retransmission
during the initial
buffering of
video
streaming.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Issue 03 (2015-07-30)
Video
Streaming Start
TCP Max
Window Size
N/A
N/A
Maximum size
of the SYN
window of
video
streaming.
PS 12.1
Video
Streaming Start
TCP Min
Window Size
N/A
N/A
Minimum size
of the SYN
window of
video
streaming.
PS 12.1
Video
Streaming Start
TCP DL
Transfer Time
[0,+)
TCP downlink
transfer time.
PS 12.1

1762
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Accumulated
Time Difference
Between Video
Streaming Start
Segments
[0,+)
Accumulated
time difference
between
adjacent
segments during
the initial
buffering phase.
PS 12.1
Abnormal
Video
Streaming Start
TCP DL
Continuous
Timeout
Retransmission
Count at
Interval(0~4s]
[0,+)
Number
Number of
times that
downlink
continuous
retransmission
time of a
quintuple flow
is abnormal
within the time
range (0-4s].
PS 12.1
Abnormal
Video
Streaming Start
TCP DL
Continuous
Timeout
Retransmission
Count at
Interval
(4s~10s]
[0,+)
Number
Number of
times that
downlink
continuous
retransmission
time of a
quintuple flow
is abnormal
within the time
range (4-10s].
PS 12.1
Abnormal
Video
Streaming Start
TCP DL
Continuous
Timeout
Retransmission
Count at
Interval(>10s)
[0,+)
Number
Number of
times that
downlink
continuous
retransmission
time of a
quintuple flow
is abnormal and
is longer than
10s.
PS 12.1
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(0~300ms]
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
within the range
(0-300 ms].
PS 12.1

1763
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(300~500ms]
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
within the range
(300-500 ms].
PS 12.1
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(500~1000ms]
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
within the range
(500-1000 ms].
PS 12.1
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(1000~5000ms]
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
within the range
(1000-5000
ms].
PS 12.1
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(>5000ms)
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
more than 5000
ms.
PS 12.1
Video
Streaming Start
TCP DL Max
Send Window
N/A
N/A
Downlink
sending window
of the maximum
size.
PS 12.1

1764
Nastar
Detailed Information--Streaming Play Info

Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Troubleshootin
g Time Segment
[0,+)
Number
Number of time
segments for
locating
problems.
PS 12.1
Video
Streaming
Troubleshootin
g Start Time
YYYY-MMDD hh: mm: ss

xxx
N/A
Time when a
time segment
for locating
problems starts
(UTC).
PS 12.1
Video
Streaming
Troubleshootin
g End Time

xxx
N/A
Time when a
time segment
for locating
problems ends
(UTC).
PS 12.1
Abnormal
Video
Streaming P3
Stall Delay
Count
[0,+)
Number
Number of
times that the
duration of a
pause exceeds
the threshold.
PS 12.1
You can set the

threshold. The
default value is
8000 ms.
Accumulated
Time Difference
Between Video
Streaming Play
Segments
N/A
Accumulated
time difference
between
adjacent
segments during
the video
streaming
playing phase.
PS 12.1
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
Delay
[0,+)
Initial buffering
delay of video
streaming.
PS 12.1

1765
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
Result
Video
Streaming Start
Success
N/A
Result of video
streaming
playing.
PS 12.1
Video
Streaming Start
Failure:
Response
Failure
Video
Streaming Start
Failure: No Bit
Rate
Video
Streaming Start
Failure: Server
Abnormal
Release
Video
Streaming Start
Failure:
Terminal
Intentionally
Release
Video
Streaming Start
Failure:
Timeout
Video
Streaming Start
Failure:
Redirect Failure
Video
Streaming Start
Failure: No Bit
Rate and
Downloaded
Data Exceeds
200 KB
Video
Streaming Start
Failure: Others
Issue 03 (2015-07-30)

1766
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Access Delay
[0,+)
Time when
video streaming
is started
relative to the
time when the
first request of
video streaming
is responded to.
The response
code of the first
request of video
streaming must
be 2**, The TS
flow and m3u8
request scenario
is included.
PS 12.1
Video
Streaming Play
Duration
[0,+)
Duration of
playing video
streaming.
PS 12.1
Video
Streaming Stall
Count
[0,+)
Number
Number of
pauses when
video streaming
is played.
PS 12.1
Video
Streaming Stall
Total Delay
[0,+)
Total duration
of pauses when
video streaming
is played.
PS 12.1
Video
Streaming
Download
Throughput
[0,+)
kbit/s
Download rate
of video
streaming.
PS 12.1
Video
Streaming P3
Stall Count
[0,+)
Number
Number of
times that the
duration of a
pause exceeds
the threshold.
PS 12.1
You can set the

threshold. The
default value is
300 ms.
Video
Streaming Play
Flag
Issue 03 (2015-07-30)
Success/Failure
N/A
Identifier of
video streaming
playing.

PS 12.1
1767
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Response Delay
[0,+)
Response delay
of video
streaming.
PS 12.1
>Video
Streaming DNS
Response Delay
[0,+)
DNS response
time of video
streaming.
PS 12.1
Video
streaming DNS
refers to the
DNS when the
first event of an
xDR is a DNS
request or
response event.
Issue 03 (2015-07-30)
>Video
Streaming SYN
to SYN ACK
Delay
[0,+)
Delay between
the time when
the first video
streaming syn
packet is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first or
second
handshake fails,
the value of this
parameter is 0.
PS 12.1
>Video
Streaming SYN
ACK to First
ACK Delay
[0,+)
Delay between
the time when
the first video
streaming syn
ack packet is
responded to
and the time
when the first
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1

1768
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
>Video
Streaming SYN
ACK to Last
ACK Delay
[0,+)
Delay between
the time when
the first video
streaming syn
ack packet is
responded to
and the time
when the last
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
>Video
Streaming ACK
to Get Delay
[0,+)
Delay between
the time when
the last video
streaming ack
packet of TCP
connection is
responded to
and the time
when the first
video streaming
get packet is
responded to. If
the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

1769
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Play
TCP DL Total
Traffic
[0,+)
Byte
Total TCP
downlink data
volume refers to
the total size of
all TCP
downlink
payload
packets, during
the video
streaming
display phase
(between the
time when video
streaming starts
being played
and the time
when video
streaming stops
being played).
PS 12.1
Video
Streaming Play
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
Video
Streaming Play
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
Video
Streaming Play
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1
Video
Streaming Play
TCP DL
Transfer Time
[0,+)
TCP downlink
transfer time.
PS 12.1

1770
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Play
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
Video
Streaming Play
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downlink RTT
delay
(accurate)/
Number of
packets whose
accurate
downlink RTT
delay is not 0
(accurate).
PS 12.1
Video
Streaming Play
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times when the
uplink TCP
window is set to
0 during the
video streaming
display phase.
PS 12.1
Video
Streaming Play
Upstream
Packet Loss
Count
[0,+)
Number
Number of
times that
upstream
packets are lost
during the video
streaming
display phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Issue 03 (2015-07-30)

1771
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Play
Downstream
Packet Loss
Count
[0,+)
Number
Number of
times that
downstream
packets are lost
during the video
streaming
display phase.
PS 12.1
Downstream
means below the
Iu-PS interface
(below the
RAN).
Video
Streaming Play
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Video
Streaming Play
TCP Max
Window Size
N/A
N/A
Maximum size
of the SYN
window of
video
streaming.
PS 12.1
Video
Streaming Play
TCP Min
Window Size
N/A
N/A
Minimum size
of the SYN
window of
video
streaming.
PS 12.1
Video
Streaming Play
TCP DL Max
Send Window
N/A
N/A
Downlink
sending window
of the maximum
size during the
video streaming
playing phase.
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.
Parameters for Viewing PS Core Complaint Analysis Support Results - Email Send (UGW)
This section describes the parameters for querying PS Core complaint analysis support (email
send) results. You can refer to the description when querying PS Core complaint analysis support
(email send) results.
Issue 03 (2015-07-30)

1772
Nastar
Detailed Information--Email Transfer Overall Info

Parameter
Range
Unit
Description
Supported Solution
Version
Email Send Flag
Email
Send
N/A
Email sending
identifier.
PS 12.1
Email Login
DNS Response
Offset
[0,+)
Offset between the

time when the email
login DNS responds
and the time when
email transmission
starts.
PS 12.1
Before you log in to the

email client, find the IP
address of the email
server and then find the
DNS.
TCP SYN
Offset
[0,+)
Offset between the

time when the first
TCP handshake occurs
and the time when
email transmission
starts.
PS 12.1
Time when the first

TCP handshake of
email transmission
occurs refers to the
time when the first syn
packet of TCP
connection is
responded to during
email login.
TCP SYN ACK
Offset
[0,+)
Offset between the

time when the second
and the time when
email transmission
starts.
PS 12.1
Time when the second

TCP handshake of
email transmission
ack packet of TCP
connection is
responded to during
email login.
Issue 03 (2015-07-30)

1773
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
TCP ACK
Offset
[0,+)
Offset between the

time when the third
and the time when
email transmission
starts.
PS 12.1

TCP handshake of
email transmission
time when the last ack
packet of TCP
connection is
responded to during
email login.
Issue 03 (2015-07-30)
Email Login
First Request
Offset
[0,+)
Offset between the

time when an email
login request is
initiated and the time
when email
transmission starts.
PS 12.1
Email Login
First Response
Offset
[0,+)
Offset between the

time when an email
login request is
responded to and the
time when email
PS 12.1
Email TCP
Release Offset
[0,+)
Offset between the

time when the email
transmission TCP
connection is released
and the time when
email transmission
starts. Email
transmission TCP
connection release
means that the
quintuple of the email
transmission TCP
TCP connection.
PS 12.1

1774
Nastar
Detailed Information--Email Send Info

Parameter
Range
Unit
Description
Supported
Solution
Version
Email Send
Request Count
[0,65535]
Numb
er

email sending request is
initiated when an email
is sent once.
PS 12.1
Email Request
Valid Count
[0,65535]
Numb
er

initiated, excluding the
request terminated by a
subscriber or server, or
the request that expires.
PS 12.1
Email Request
Success Count
[0,65535]
Numb
er

responded to when an
email is sent once.
PS 12.1
Email Integrity
Send Count
[0,+)
Numb
er

email sending events are
intact during the email
transmission phase.
PS 12.1
Wireless
Effective
Throughput
[0,+)
kbit/s
Effective transmission
rate on the RAN side.
PS 12.1
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
DNS Response
Delay
[0,+)
If DNS request
and response
events exist in
email login,
Email Login
DNS Response
Delay is equal to
DNS_Response
_Duration of the
events.
PS 12.1

1775
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
Response
Result
Success/Failure
N/A
Result of
responding to an
email login
request.
PS 12.1
>Email Login
Response Code
N/A
N/A
Response code
of an email login
request.
PS 12.1
Email Receive
Success Indictor
Success/Failure
N/A
Indicator of
email login
success. Email
login succeeds
when a TCP
connection
setup event
succeeds and
login
authentication
succeeds once
during email
login.
PS 12.1
First Send Email

Response Code
N/A
N/A
Send first email

response code.
PS 12.1
Email Size
[0,+)
Byte
Total size of all

nonretransmission
packets during
the email
transmission
phase (between
the time when
an email
sending request
is responded to
and the time
when email
transmission
ends).
PS 12.1

1776
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Send
Transfer Delay
[0,+)
Valid time for

transmitting
data during the
email sending
phase (between
the time when
the first email
sending request
is responded to
and the time
when email
transmission
ends).
PS 12.1
Email Send
Throughput
[0,+)
kbit/s
Average
transmission
rate of email
sending during
the email
sending phase.
PS 12.1
Email Login
Response Delay
[0,+)
Time when the

first email login
DNS request is
responded to
relative to the
time when the
last login
request is
responded to.
PS 12.1
If no DNS is
available, this
parameter
indicates the
time when the
first syn request
is responded to
relative to the
time when the
last login
request is
responded to.
Issue 03 (2015-07-30)

1777
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>Email Login
SYN to SYN
ACK Delay
[0,+)
Delay between
the time when
the first syn
packet of email
login is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first
handshake fails,
the value of this
parameter is 0.
PS 12.1
>Email Login
SYN ACK to
First Ack Delay
[0,+)
Delay between
the time when
the first syn ack
packet of email
login is
responded to
and the time
when the first
ack packet is
responded to. If
the second
handshake fails,
the value of this
parameter is 0.
PS 12.1
>Email Login
ACK to First
Data Delay
[0,+)
Delay between
the time when
the last ack
packet of email
login TCP
connection is
responded to
and the time
when the first
email login
request is
responded to. If
the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

1778
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Email Login
TCP
Connection
Delay
[0,+)
Scenario 1:
Email Login
TCP
Connection
Delay is the time
when the first
email login
request is
responded to
relative to the
time when the
last payload
packet is
responded to
during email
login when the
third handshake
does not occur.
PS 12.1
Scenario 2:
Email Login
TCP
Connection
Delay is the time
when the first
email login
request is
responded to
relative to the
time when the
first TCP
handshake of
email login
occurs when the
third handshake
occurs.
Scenario 3: The
value of Email
Login TCP
Connection
Delay is 0 when
the email server
connection
times out and no
response packet
is available.
Issue 03 (2015-07-30)

1779
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Scenario 4:
Email Login
TCP
Connection
Delay is the time
when the last
payload packet
is responded to
relative to the
time when the
first TCP
handshake of
email login
occurs during
email login
when the email
server
connection
times out and
the response
packet is
available.
Issue 03 (2015-07-30)
>Email Server
Process Delay
[0,+)
Delay in the
email server's
responding to
the first login
request.
PS 12.1
Email Server
Process
Average Delay
[0,+)
Delay between
the time when
the smtp from
request is
responded to
and the time
when the DATA
request is
responded to
during email
sending.
PS 12.1

1780
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SMTP Data
Delay
[0,+)
Delay between
the time when
the smtp from
request is
responded to
and the time
when the DATA
request is
responded to
during email
sending.
PS 12.1
TCP DL Total
Traffic
[0,+)
Byte
Total size of
TCP downlink
payload
packets,
including
retransmitted
packets, during
the email
sending phase.
PS 12.1
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Count
[0,+)
Number
Number of TCP
downlink
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
downlink
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1

1781
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP UL Total
Packets
[0,+)
Number
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL Total
Traffic
[0,+)
Byte
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Count
[0,+)
Number
Number of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
uplink packets.
PS 12.1
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1

1782
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP Upstream
Average RTT
Delay
(Accurate)
[0,+)
TCP Upstream
Average RTT
Delay
(Accurate) =
Packet upstream
RTT delay
(accurate)/
Number of
packets whose
accurate
upstream RTT
delay is not 0
(accurate).
PS 12.1
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times that the
uplink TCP
window is set to
0 during the
email sending
phase.
PS 12.1
Upstream
Packet Loss
Count
[0,+)
Number
Number of
times that
upstream
packets are lost
due to packet
retransmission
during the email
sending phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Number of
times that
upstream
packets are lost
during the email
sending phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Issue 03 (2015-07-30)

1783
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Upstream
Packet Loss
Ratio
[0.00,100.00]
Proportion of
TCP uplink
packet loss.
PS 12.1
Downstream
Packet Loss
Count
[0,+)
Number
Number of
times that
downstream
packets are lost
during the email
transmission
phase.
PS 12.1
Downstream
means below the
Iu-PS interface
(below the
RAN).
TCP Max
Window Size
N/A
N/A
Maximum size
of the window
during the email
transmission
phase.
PS 12.1
TCP Min
Window Size
N/A
N/A
Maximum size
of the window
during the email
transmission
phase.
PS 12.1
Parameters for Viewing PS Core Complaint Analysis Support Results - Email Receive
(UGW)
receive) results. You can refer to the description when querying PS Core complaint analysis
support (email receive) results.
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Receive
Flag
Email Receive
N/A
Identifier of email receiving.
PS 12.1

1784
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
DNS Response
Offset
[0,+)
Time when email login DNS

responds relative to the time
when email transmission
starts.
PS 12.1

address of the email server
and then find the DNS.
TCP SYN
Offset
[0,+)

when the first TCP
handshake occurs and the
time when email
PS 12.1
Time when the first TCP

handshake of email
transmission occurs refers to
the time when the first syn
packet of TCP connection is
responded to.
TCP SYN ACK
Offset
[0,+)

when the second TCP
time when email
PS 12.1
Time when the second TCP

handshake of email
ack packet of TCP
connection is responded to
during email login.
TCP ACK
Offset
[0,+)

when the third TCP
time when email
PS 12.1

handshake of email
the time when the last ack
responded to during email
login.
Issue 03 (2015-07-30)

1785
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
First Request
Offset
[0,+)

when an email login request
starts.
PS 12.1
Email Login
First Response
Offset
[0,+)

is responded to and the time
starts.
PS 12.1
Email TCP
Release Offset
[0,+)

when the email transmission
TCP connection is released
and the time when email
transmission starts. Email
transmission TCP
connection release means
that the quintuple of the
email transmission TCP
connection releases the TCP
connection.
PS 12.1
Detailed Information--Email Receive Info
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supporte
d
Solution
Version
Email Receive
Request Count
[0,+)
Numbe
r
Number of times that an email

receiving request is initiated
when an email is received
once.
PS 12.1
Email Request
Valid Count
[0,+)
Numbe
r

receiving request is initiated,
excluding the request
terminated by a subscriber or
server, or the request that
expires.
PS 12.1

1786
Nastar
Parameter
Range
Unit
Description
Supporte
d
Solution
Version
Email Request
Success Count
[0,+)
Numbe
r

receiving request is responded
to when an email is received
once.
PS 12.1
Email Integrity
Receive Count
[0,+)
Numbe
r

receiving event is integral
during the email transmission
phase.
PS 12.1
Wireless
Effective
Throughput
[0,+)
kbit/s

the RAN side.
PS 12.1
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
DNS Response
Delay
[0,+)
If DNS request
and response
events exist in
email login,
Email Login
DNS Response
Delay is equal to
DNS_Response
_Duration of the
events.
PS 12.1
Email Login
Response
Result
Success/Failure
N/A
Result of
responding to an
email login
request.
PS 12.1
>Email Login
Response Code
N/A
N/A
Response code
of an email login
request.
PS 12.1
Comprehensive Complaints
Issue 03 (2015-07-30)

1787
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Receive
Success Indictor
Success/Failure
N/A
Indicator of
email login
success. Email
login succeeds
when a TCP
connection
setup event
succeeds and
login
authentication
succeeds once
during email
login. In other
scenarios, email
login fails.
PS 12.1
>Receive First
Email Response
Code
N/A
N/A
Receive First
Email Response
Code.
PS 12.1
Email Size
[0,+)
Byte
Total size of all

nonretransmission
packets during
the email
transmission
phase (between
the time when
an email
receiving
request is
responded to
and the time
when email
transmission
ends).
PS 12.1

1788
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Receive
Transfer Delay
[0,+)
Valid time for

transmitting
data during the
email receiving
phase (between
the time when
the first email
receiving
request is
responded to
and the time
when email
transmission
ends).
PS 12.1
Email Receive
Throughput
[0,+)
kbit/s
Average
transmission
rate of email
receiving during
the email
receiving phase.
PS 12.1
Email Login
Response Delay
[0,+)
Time when the

first email login
DNS request is
responded to
relative to the
time when the
last login
request is
responded to.
PS 12.1
If no DNS is
available, this
parameter
indicates the
time when the
first syn request
is responded to
relative to the
time when the
last login
request is
responded to.
Issue 03 (2015-07-30)

1789
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>Email Login
SYN to SYN
ACK Delay
[0,+)
Delay between
the time when
the first syn
packet of email
login is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first
handshake fails,
the value of this
parameter is 0.
PS 12.1
>Email Login
SYN ACK to
First Ack Delay
[0,+)
Delay between
the time when
the first syn ack
packet of email
login is
responded to
and the time
when the first
ack packet is
responded to. If
the second
handshake fails,
the value of this
parameter is 0
PS 12.1
>Email Login
ACK to First
Data Delay
[0,+)
Delay between
the time when
the last ack
packet of email
login TCP
connection is
responded to
and the time
when the first
email login
request is
responded to. If
the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

1790
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Email Login
TCP
Connection
Delay
[0,+)
Scenario 1:
Email Login
TCP
Connection
Delay is the time
when the first
email login
request is
responded to
relative to the
time when the
last payload
packet is
responded to
during email
login when the
third handshake
does not occur.
PS 12.1
Scenario 2:
Email Login
TCP
Connection
Delay is the time
when the first
email login
request is
responded to
relative to the
time when the
first TCP
handshake of
email login
occurs when the
third handshake
occurs.
Scenario 3: The
value of Email
Login TCP
Connection
Delay is 0 when
the email server
connection
times out and no
response packet
is available.
Issue 03 (2015-07-30)

1791
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Scenario 4:
Email Login
TCP
Connection
Delay is the time
when the last
payload packet
is responded to
relative to the
time when the
first TCP
handshake of
email login
occurs during
email login
when the email
server
connection
times out and
the response
packet is
available.
Issue 03 (2015-07-30)
>Email Server
Process Delay
[0,+)
Delay in the
email server's
responding to
the first login
request.
PS 12.1
Email Server
Process
Average Delay
[0,+)
Delay between
the time when
the smtp from
request is
responded to
and the time
when the DATA
request is
responded to
during email
receiving.
PS 12.1

1792
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP DL Total
Traffic
[0,+)
Byte
Total size of
TCP downlink
payload
packets,
including
retransmitted
packets, during
the email
receiving phase.
PS 12.1
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Count
[0,+)
Number
Number of TCP
downlink
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
downlink
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1
TCP UL Total
Packets
[0,+)
Number
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1

1793
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP UL Total
Traffic
[0,+)
Byte
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Count
[0,+)
Number
Number of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
uplink packets.
PS 12.1
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1

1794
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP Upstream
Average RTT
Delay
(Accurate)
[0,+)
TCP Upstream
Average RTT
Delay
(Accurate) =
Packet upstream
RTT delay
(accurate)/
Number of
packets whose
accurate
upstream RTT
delay is not 0
(accurate).
PS 12.1
Upstream
Packet Loss
Count
[0,+)
Number
Number of
times that
upstream
packets are lost
due to packet
retransmission
during the email
receiving phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Number of
times that
upstream
packets are lost
during the email
receiving phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Upstream
Packet Loss
Ratio
Issue 03 (2015-07-30)
[0.00,100.00]
Proportion of
TCP uplink
packet loss.

PS 12.1
1795
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Downstream
Packet Loss
Count
[0,+)
Number
Number of
times that
downstream
packets are lost
during the email
receiving phase.
PS 12.1
Downstream
means below the
Iu-PS interface
(below the
RAN).
TCP Max
Window Size
N/A
N/A
Maximum size
of the window
during the email
receiving phase.
PS 12.1
TCP Min
Window Size
N/A
N/A
Minimum size
of the window
during the email
receiving phase.
PS 12.1
Parameters for Viewing PS Core Complaint Analysis Support Results - File Access(UGW)
This section describes the parameters for querying complaint analysis support (file access)
results. You can refer to the description when querying complaint analysis support (file access)
results.
Detailed Information--File Transfer Overall Info

Parameter
Range
Unit
Description
Supported
Solution
Version
File Upload and

Download Flag
Downl
oad
N/A
File upload/download identifier.

Currently, only file download is
supported.
PS 12.1
File Transfer
DNS Response
Offset
[0.00,
+)
Time when the file transfer DNS

when file transfer starts.
PS 12.1
File transfer DNS refers to the

DNS when the first event of file
transfer is a DNS request or
response event.
Issue 03 (2015-07-30)

1796
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
TCP SYN
Offset
[0.00,
+)
Offset between the time when the

first TCP handshake of file
transfer occurs and the time when
file transfer starts.
PS 12.1
File transfer TCP connection

refers to the first TCP connection
of file transfer. Before this
connection, no HTTP requests
are initiated.
handshake of file transfer occurs
refers to the time when the first
syn packet of file transfer TCP
connection is responded to.
File Transfer
TCP SYN ack
Offset
[0.00,
+)

second TCP handshake of file
PS 12.1

are initiated.
syn ack packet of file transfer
TCP connection is responded to.
File Transfer
TCP ack Offset
[0.00,
+)

third TCP handshake of file
PS 12.1

are initiated.
Time when the third TCP
refers to the time when the last
ack packet of file transfer TCP
Issue 03 (2015-07-30)

1797
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
First Request
Offset
[0.00,
+)

first request of file transfer is
initiated between the time when
PS 12.1
The first request of file transfer

may be a redirection request or
main file transfer request.
If no file transfer request exists,
file transfer DNS parsing fails.
File Transfer
First Response
Offset
[0.00,
+)

PS 12.1

File Transfer
First Redirect
Request Offset
[0.00,
+)

first redirection request of file
transfer is initiated between the
time when file transfer starts.
PS 12.1
File Transfer
First Redirect
Response Offset
[0.00,
+)

PS 12.1
File Transfer
Request Offset
[0.00,
+)

main file transfer request is
PS 12.1
Only one main file transfer

request is available for file
transfer. The main request
response code
(FileAccess_Response_Result)
can be only 2**, 304, 4**, 5**,
600, 601, and 0xFFFF.
Issue 03 (2015-07-30)

1798
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Response Offset
[0.00,
+)

responded to and the time when
PS 12.1

response code
(HTTP_Response_Result) can
be only 2**, 3**, 4**, 5**, 600,
601, and 0xFFFF. (For POST
upload, the time when the main
request is responded to indicates
the offset between the time when
the ack packet corresponding to
the main request is received and
the time when file transfer starts.)
File Transfer
TCP Release
Offset
[0.00,
+)

release means that the quintuple
of the file transfer TCP
connection.
PS 12.1
File Transfer
End Offset
[0.00,
+)
Offset between the time when file

transfer ends and the time when
PS 12.1
The ending of file transfer means

that the file transfer DNS request
fails to be responded to or times
out.
Detailed Information--File Request Response Phase Info
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Request
Redirect
Success Count
[0,+)
Numbe
r
Number of times that redirection

succeeds when the file transfer
request is responded to.
PS 12.1
This parameter is calculated when

redirection exists.

1799
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Request
Redirect Failure
Count
[0,+)
Numbe
r

fails when the file transfer request
is responded to.
PS 12.1
File Transfer No
Response Wait
Time
hh:
mm: ss

redirection exists.
N/A
Time when subscribers actively

terminates file transfer (a UE sends
RST or FIN first) relative to the
time when SYNC appears if there
is no file transfer response.
PS 12.1
Detailed Information--File Transfer Phase Info
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Request Count
[0,65535]
Numb
er
Number of times that GET/POST

requests are responded to during
the file transfer phase (between
the time when the main file
transfer request is responded to
and the time when file transfer
ends).
PS 12.1
File Transfer
Request Success
Count
[0,65535]
Numb
er

FileAccess_Response_Result is
equal to 2**, 304 during file
transfer request and response
events.
PS 12.1

1800
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Valid Request
Count
[0,65535]
Numb
er

requests whose response code is
2**, 3**, 4**, or 5** are
responded to during the file
transfer phase (between the time
when the main page request is
the page browsing function is
disabled).
PS 12.1
Effective requests refer to the

requests that are responded to,
excluding the request terminated
by a subscriber or server, or the
request that expires.
File Transfer
Integrity Count
[0,+)
Numb
er
Number of times that file transfer

succeeds.
PS 12.1
File Transfer
Total Count
[0,+)
Numb
er
File Transfer Total Count = File

Transfer Integrity Count +
fails.
PS 12.1
File Transfer
Redirect Failure
Count
[0,+)
Numb
er

fails during the file transfer phase
(for file download only)
PS 12.1
Wireless
Effective
Throughput
[0,+)
kbit/s
Effective transmission rate on the

RAN side.
PS 12.1
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Response
Succeed
Indictor
Success/Failure
N/A
Result of
responding to a
file transfer
request.
PS 12.1
File Transfer
Response Result
N/A
N/A
Response code
of a main file
transfer request.
PS 12.1

1801
Nastar
Parameter
Issue 03 (2015-07-30)
Range
Unit
Description
Supported
Solution
Version
File Transfer
Success/Failure
Success Indictor
N/A
File transfer
succeeds only
when the main
file transfer
request is
successfully
responded to.
PS 12.1
File Transfer
Size
[0,+)
Byte
Total size of
uplink/
downlink nonretransmitted
packets during
the file transfer
phase (between
the time when
the main file
transfer request
is responded to
and the time
when file
transfer ends).
PS 12.1
File Transfer
Throughput
[0,+)
kbit/s
Average
transmission
rate during the
file transfer
phase (between
the time when
the main file
transfer request
is responded to
and the time
when file
transfer ends).
PS 12.1

1802
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Response Delay
[0,+)
Time when the

first file transfer
DNS request is
responded to
relative to the
time when the
main file
transfer request
is responded to.
If no file transfer
DNS is
available, this
parameter
indicates the
time when the
first file transfer
syn is responded
to relative to the
time when the
main file
transfer request
is responded to.
If no file transfer
TCP connection
is available, this
parameter
indicates the
time when the
first request is
responded to
relative to the
time when the
main file
transfer request
is responded to.
The value of
File Transfer
Response Code
must be 2**,
3**, 4**, 5**,
600, 601, or
0xFFFF.
PS 12.1
>File Transfer
DNS Response
Delay
[0,+)
Delay in
responding to
the file transfer
DNS request.
PS 12.1

1803
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
SYN to SYN
ACK Delay
[0,+)
Delay between
the time when
the first file
transfer syn
packet is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first or
second
handshake fails,
the value of this
parameter is 0.
PS 12.1
>File Transfer
SYN ACK to
First ACK
Delay
[0,+)
Delay between
the time when
the first file
transfer syn ack
packet is
responded to
and the time
when the first
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
>File Transfer
SYN ACK to
Last ACK Delay
[0,+)
Delay between
the time when
the first file
transfer syn ack
packet is
responded to
and the time
when the last
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1

1804
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
ACK to First
Data Delay
[0,+)
Delay between
the time when
the last ack
packet of the file
transfer TCP
connection is
responded to
and the time
when the first
payload packet
of file transfer is
responded to. If
the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

1805
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
Max SYN to
SYN ACK
Delay
[0,+)
Delay between
the time when
the file transfer
syn packet is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first or
second
handshake fails,
the value of this
parameter is 0.
PS 12.1
Note:
Redirection
occurs for
multiple times
when the file
transfer request
is responded to.
The third TCP
handshake may
occur for the
quintuple flow
of each
redirection and
main request.
Delays between
the time when
the syn is
responded to
and the time
when the syn
ack is responded
to for multiple
TCP
connections are
calculated and
the maximum
value is
selected.
Issue 03 (2015-07-30)

1806
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
Max SYN ACK
to First ACK
Delay
[0,+)
Delay between
the time when
the file transfer
syn ack packet is
responded to
and the time
when the first
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
Note:
Redirection
occurs for
multiple times
when the file
transfer request
is responded to.
The third TCP
handshake may
occur for the
quintuple flow
of each
redirection and
main request.
Delays between
the time when
the syn ack is
responded to
and the time
when the first
ack is responded
to for multiple
TCP
connections are
calculated and
the maximum
value is
selected.
Issue 03 (2015-07-30)

1807
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
Max ACK to
First Data Delay
[0,+)
Delay between
the time when
the last ack
packet of the file
transfer TCP
connection is
responded to
and the time
when the file
transfer request
is responded to.
If the third
handshake fails,
the value of this
parameter is 0.
PS 12.1
Note:
Redirection
occurs for
multiple times
when the file
transfer request
is responded to.
The third TCP
handshake may
occur for the
quintuple flow
of each
redirection and
main request.
Delays between
the time when
the ack is
responded to
and the time
when the first
request is
responded to for
multiple TCP
connections are
calculated and
the maximum
value is
selected.
Issue 03 (2015-07-30)

1808
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Delay
[0,+)
File Transfer
Delay = File
transfer end
time - File
transfer start
time.
PS 12.1
The file transfer

delay starts
when SP
responds with
"2**, 304", or
the ack (for
POST upload).
Issue 03 (2015-07-30)
TCP DL Total
Traffic
[0,+)
Byte
Total TCP
downlink data
volume refers to
the total size of
all TCP
downlink
payload
packets,
including
retransmitted
packets, during
the file access
phase.
PS 12.1
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
downlink
packets (only
payload packets
are calculated).
PS 12.1

1809
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP UL Total
Packets
[0,+)
Number
Number of all
TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL Total
Traffic
[0,+)
Byte
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
uplink packets
(only payload
packets are
calculated).
PS 12.1
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1

1810
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP Upstream
Average RTT
Delay
(Accurate)
[0,+)
TCP Upstream
PS 12.1
Average RTT
Delay
(Accurate) =
Packet upstream
RTT delay
(accurate)/
Number of
packets whose
accurate
upstream RTT
delay is not 0
(accurate).
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times that the
uplink TCP
window is set to
0 during the file
transfer phase.
PS 12.1
Upstream
Packet Loss
Count
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
Issue 03 (2015-07-30)
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.

1811
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Downstream
Packet Loss
Count
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.
TCP SYN Max
Window Size
N/A
N/A
Maximum size
of the SYN
window of file
transfer.
PS 12.1
TCP SYN Min

Window Size
N/A
N/A
Minimum size
of the SYN
window of file
transfer.
PS 12.1
TCP DL Max
Send Window
N/A
N/A
Downlink
PS 12.1
sending window
of the maximum
size.
Reference for Complaint Analysis Support Parameters (PS Core) - Signaling Plane
This section describes the parameters for querying PS Core complaint analysis support resultssignaling plane. You can refer to the description when querying PS Core complaint analysis
support results.
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.
Issue 03 (2015-07-30)

1812
Nastar
Summary
Parameter
Range
Unit
Description
Supported
Solution
Version
Serial
Number
[1,2^31-1)
N/A
Serial number of a CHR in the

Summary Table. Serial number
is a keyword of a call record. It is
an internal identification in the
Nastar and can uniquely identify
a call record.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Combined
N/A
N/A
The field in the PS core

complaint analysis support is
empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
USN+UGW
Associated
N/A
N/A

empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Abnormal
N/A
N/A
Indicates whether a call record is

abnormal.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

record is abnormal.
exception type of this call record
in the navigation tree is Other and
the exception status is unknown.
Abnormal
Cause
N/A
N/A

Key Signaling".
Issue 03 (2015-07-30)
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Protocol
Cause
Description
N/A
N/A
Description of failure cause

values in the signaling flow.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Demarcatio
n Result
N/A
N/A
NE that experiences an
exception.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

1813
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Start Time
N/A
N/A
Start time of the signaling

procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
End Time
N/A
N/A
End time of the signaling

procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
IMSI
N/A
N/A
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

User ID:
Alias
N/A
N/A

MSISDN
N/A
N/A
subscriber.
view the MSISDN information.
Access Net
Type
N/A
N/A
Radio access network (RAN)

type for the signaling procedure.
This parameter can be any of the
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
GPRS
UMTS(W/TD)
LTE
UTRAN
GERAN
WLAN
GAN
HSPA Evolution
EUTRAN
N/A
Issue 03 (2015-07-30)

1814
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CSFB On
Access
Yes
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
N/A
Access type of VoLTE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
N/A
Core network (CN) NE types for

the signaling procedure. This
parameter can be any of the
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
No
N/A
VoLTE On
Access
Yes
No
N/A
NE Type
N/A
SGSN
MME
GGSN
SGW
PGW
SGW+PGW
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Procedure
Type
N/A
N/A
Name of a signaling procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
RAI/TAI
N/A

Key Signaling".
N/A
Indicates the routing area where

an SGSN signaling procedure is
initiated.
Indicates the tracking area where
an MME signaling procedure is
initiated.
Cell
Issue 03 (2015-07-30)
N/A
N/A
Name of the cell where signaling

accesses.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
1815
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
APN
N/A
N/A
APN involved in the session for

the SM procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
The field does not apply to the

MM procedure.
Procedure
Delay Time
(ms)
0-65535
ms
Delay of a signaling procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
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
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
SN
[1,2^32-1)
N/A
SN of a reported
CHR. The SN
accumulates on an
NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Start Time
N/A
N/A
Start time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
End Time
N/A
N/A
End time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Procedure
Delay Time
0-65535
ms
Delay of a signaling
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

1816
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
NE Type
N/A
N/A
CN NE types for the

This parameter can be
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGSN
MME
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Subrack
No.
0-255
N/A
Subrack number of
the device that
generates CHRs.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Slot No.
0-255
N/A
Slot number of the

device that generates
a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Proc No.
0-65535
N/A
Number of the
process that generates
a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Parameter
Range
Unit
Description
Supported
Solution Version
IMSI
N/A
N/A
subscriber.
User Information
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
Note: Only when you PS12.0/PS 12.1/PS
13.0
have the "User
Identity" right, you
can view the IMSI
information.
Issue 03 (2015-07-30)

1817
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
User ID: Alias
N/A
N/A
User ID, which is

created by the system
when creating the
task.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Alias, which is
created by the user
when creating the
task.
MSISDN
N/A
N/A
MSISDN
information of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
Note: Only when you 13.0
have the "User
can view the
MSISDN
information.
IMEI-TAC
00000000-9999
9999
N/A
IMEI-TAC of the
terminal that initiates
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Terminal Model
N/A
N/A
Model of the terminal

that initiates a
service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
MS Network
Capability
N/A
N/A
Indicates the GRRSrelated terminal

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>GEA/1
encryption
algorithm
0/1
N/A
Indicates whether the

GEA/1 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SM
capabilities via
dedicated
channels
0/1
N/A

dedicated-channelbased SM capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1818
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>SM
capabilities via
GPRS channels
0/1
N/A

GPRS-channel-based
SM capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SS Screening
Indicator string
(2)
0/1
N/A

SS screening
indicator is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SoLSA
Capability
0/1
N/A

SoLSA capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Revision level
indicator (R99
or later versions
of the protocol
support)
0/1
N/A

revision-level
indicator is supported
(by protocols in
3GPP Specifications
Release 99 or later).
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PFC feature
mode(BSS
packet flow
procedures
support)
0/1
N/A

PFC feature mode
(BSS data packet
flow procedure) is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1819
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>GEA/2
encryption
algorithm
0/1
N/A

GEA/2 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/3
encryption
algorithm
0/1
N/A

GEA/3 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/4
encryption
algorithm
0/1
N/A

GEA/4 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/5
encryption
algorithm
0/1
N/A

GEA/5 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/6
encryption
algorithm
0/1
N/A

GEA/6 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/7
encryption
algorithm
0/1
N/A

GEA/7 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1820
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>LCS VA
capability
0/1
N/A
Indicates whether the PS 11.0/PS 12.0/PS

LCS VA capability is 12.1/PS 13.0
supported.
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to
UTRAN Iu
mode capability
0/1
N/A

inter-PS handover
(GERAN to UTRAN
handover) capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to EUTRAN S1
mode capability
0/1
N/A

inter-PS handover
(GERAN to EUTRAN handover)
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EMM
Combined
procedures
Capability
0/1
N/A

EMM combined
procedure capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>ISR support
0/1
N/A
Indicates whether
ISR is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SRVCC to
GERAN/
UTRAN
capability
0/1
N/A

SRVCC-to-GERAN/
UTRAN handover
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1821
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPC capability
0/1
N/A

EPC capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A

NF capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
UE Network
Capability
N/A
N/A
Indicates the UErelated terminal

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>EPS
encryption
algorithm EEA0
supported
0/1
N/A

EPS encryption
algorithm EEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA1
supported
0/1
N/A

EPS encryption
algorithm 128-EEA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA2
supported
0/1
N/A

EPS encryption
algorithm 128-EEA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA3
supported
0/1
N/A

EPS encryption
algorithm EEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1822
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS
encryption
algorithm EEA4
supported
0/1
N/A

EPS encryption
algorithm EEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA5
supported
0/1
N/A

EPS encryption
algorithm EEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA6
supported
0/1
N/A

EPS encryption
algorithm EEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA7
supported
0/1
N/A

EPS encryption
algorithm EEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA0
supported
0/1
N/A

EPS integrity
algorithm EIA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm 128EIA1 supported
0/1
N/A

EPS integrity
algorithm 128-EIA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1823
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS integrity
0/1
N/A

EPS integrity
algorithm 128-EIA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA3
supported
0/1
N/A

EPS integrity
algorithm EIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA4
supported
0/1
N/A

EPS integrity
algorithm EIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA5
supported
0/1
N/A

EPS integrity
algorithm EIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA6
supported
0/1
N/A

EPS integrity
algorithm EIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA7
supported
0/1
N/A

EPS integrity
algorithm EIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1824
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA0
supported
0/1
N/A

UMTS encryption
algorithm UEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA1
supported
0/1
N/A

UMTS encryption
algorithm UEA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA2
supported
0/1
N/A

UMTS encryption
algorithm UEA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA3
supported
0/1
N/A

UMTS encryption
algorithm UEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA4
supported
0/1
N/A

UMTS encryption
algorithm UEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA5
supported
0/1
N/A

UMTS encryption
algorithm UEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1825
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA6
supported
0/1
N/A

UMTS encryption
algorithm UEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA7
supported
0/1
N/A

UMTS encryption
algorithm UEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
(UCS2)
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA1
supported
0/1
N/A

UMTS integrity
algorithm UIA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA2
supported
0/1
N/A

UMTS integrity
algorithm UIA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA3
supported
0/1
N/A

UMTS integrity
algorithm UIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1826
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
integrity
algorithm UIA4
supported
0/1
N/A

UMTS integrity
algorithm UIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA5
supported
0/1
N/A

UMTS integrity
algorithm UIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA6
supported
0/1
N/A

UMTS integrity
algorithm UIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA7
supported
0/1
N/A

UMTS integrity
algorithm UIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A

NF capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>1xSRVCC
capability
0/1
N/A

1xSRVCC capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1827
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>Location
services (LCS)
notification
mechanisms
capability
0/1
N/A

LCS notification
mechanism
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LTE
Positioning
Protocol (LPP)
capability
0/1
N/A

LPP capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Access class
control for
CSFB (ACCCSFB)
capability
0/1
N/A

CSFB-access-level
control capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
MS P-TMSI
[1,2^32-1)
N/A
P-TMSI received
from a terminal when
a procedure is
initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Allocated PTMSI
[1,2^32-1)
N/A
P-TMSI that the

network allocates to a
terminal.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Index
N/A
N/A
Index number of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Home
PLMN
N/A
N/A
PLMN in the IMSI of

a subscriber. This
parameter is used for
personal data
anonymization.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Authentication
Flag
NoAuth
N/A
Indicates whether a
procedure requires
authentication.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
FirAuth
SecAuth
Issue 03 (2015-07-30)

1828
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
IMEI Check
Flag
N/A
N/A
Indicates whether a
procedure requires
IMEI check.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
P-TMSI
Reallocation
Flag
N/A
N/A
Indicates whether a
procedure requires PTMSI reallocation.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Access Information
Parameter
Range
Unit
Description
Supported Solution
Version
Type
N/A
N/A
Type of the signaling

procedure. This
parameter can be any of
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
SM
MM
Procedure Type
N/A
N/A
Name of a signaling
procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Procedure Init
Cause
N/A
N/A
Procedure initiating party

(UE or MME) and cause.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

Description of Procedure
Initiating Causes in the
appendix.
Access Network
Description
N/A
N/A
Description of the access

network.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Inter CN Node
Type
N/A
N/A
Radio access network

(RAN) type for the
signaling procedure. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
GPRS
UMTS(W/TD)
LTE
Issue 03 (2015-07-30)

1829
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported Solution
Version
Access BSC/
RNC
Description
N/A
N/A
Description of an NE that
gains access to the RAN.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>BSC/RNC
PLMN
N/A
N/A
PLMN serving a BSC or

RNC.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
>BSC/RNC ID
N/A
N/A
ID of a BSC or RNC.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
>CGI
N/A
N/A
Cell where a procedure is

initiated.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Cell Name
[0,200]
N/A

initiated.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
PS Core
Description
N/A
N/A
gains access to the CN.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>GGSN or
PGW Address
for Signalling
N/A
N/A
IP address of the GGSN

signaling plane.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>GGSN
Address for
User Traffic
N/A
N/A

user plane.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Mobility
Information
N/A
N/A
Information about
mobility analysis.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Old SGSN IP
N/A
N/A
If a procedure involves
two SGSNs, the field
indicates the IP address of
the old SGSN.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>SM Procedure
Information
N/A
N/A
Information about the SM

procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

1830
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>PDP Type In
Used
N/A
N/A
Type of the PDP used by

an MS. The values of this
parameter are as follows:
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
IPv4
IPv6
BOTH(IPV4 & IPV6)
PPP
Empty
>PDP Type
Request By MS
N/A
N/A
Type of the PDP

requested by a MS. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
IPv4
IPv6
BOTH(IPV4 & IPV6)
PPP
Empty
>PDP Address
Request By MS
N/A
N/A
IP address of the PDP

requested by a MS.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
>PDP Address
in Use
N/A
N/A
Activated PDP IP
address.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>APN Request
By MS
N/A
N/A
Name of the access point

requested by an MS.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
>Access APN
N/A
N/A
Access point name.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>APN Selection
Mode
N/A
N/A
APN selection mode.

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
MS & Network Verified

MS not Verified
Network not Verified
QoS
Issue 03 (2015-07-30)
N/A
N/A
Information about the

QoS.

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
1831
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Allocation/
Retention
Priority
N/A
N/A
Allocation/retention
priority. This parameter
can be any of the
following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
High priority
Normal priority
Low priority
>Reliability
Class
N/A
N/A
Subscribed reliability
class. This parameter can
be any of the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
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.

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Subscribed delay class

Delay class 1
Delay Class 2
Delay Class 3
Delay Class 4 (best
effort)
Reserved
Issue 03 (2015-07-30)

1832
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Precedence
Class
N/A
N/A
Subscribed precedence.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Subscribed precedence
High priority
Normal priority
Low priority
Reserved
>Peak
Throughput
N/A
N/A
Subscribed peak
throughput. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
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
Reserved
Issue 03 (2015-07-30)

1833
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Mean
Throughput
N/A
N/A
Subscribed mean
throughput. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
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
Erroneous SDU
N/A
N/A
Subscribed delivery of
erroneous SDUs. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
No detect('-')
Erroneous SDUs are
delivered('yes')
Erroneous SDUs are not
delivered ('no')
Reserved
Issue 03 (2015-07-30)

1834
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Delivery
Order
N/A
N/A
Subscribed delivery
order. This parameter can
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
With delivery order

('yes')
Without delivery order
('no')
>Traffic Class
N/A
N/A
Subscribed traffic class.

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Conversational class
Streaming class
Interactive class
Background class
>Traffic
Handling
Priority
N/A
N/A
Subscribed traffic
handling priority. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Priority level 1
Priority level 2
Priority level 3
>Maximum
SDU Size
0-255
byte
Maximum SDU length.

Subscribed maximum
SDU size
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
150: 10~1500 octets

151: 1502 octets
152: 1510 octets
153: 1520 octets
Reserved
Issue 03 (2015-07-30)
>Maximum Bit
Rate for Uplink
0-8640
bps
Maximum uplink rate.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Maximum Bit
Rate for
Downlink
0-2560
00
bps
Maximum downlink rate.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

1835
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Residual BER
N/A
N/A
Subscribed residual BER.

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
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
Ratio
N/A
N/A
Subscribed SDU error

ratio. This parameter can
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

ratio
1*10^2
7*10^3
1*10^3
1*10^4
1*10^5
1*10^6
1*10^1
Issue 03 (2015-07-30)
>Transfer Delay
0-255
ms
Transfer delay.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Guaranteed
Bit Rate for
Uplink
0-8640
bps
Guaranteed uplink rate.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Guaranteed
Bit Rate for
Downlink
0-2560
00
bps
Guaranteed downlink
rate.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

1836
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
GTP Tunnel
Version
N/A
N/A
GTP tunnel version. This

the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
GTPv0
GTPv1
Bearer ID
5-15
N/A
Bearer ID.
PS 13.0 or later
Result Information
Parameter
Range
Unit
Description
Supported
Solution Version
Protocol Cause
N/A
N/A
Cause value
provided in a
protocol.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Protocol Cause
Description
N/A
N/A
Description of a
protocol cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Huawei's Cause
N/A
N/A
Procedure result and

failure cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

Description of
Exception Cause
Fields in the
appendix.
Huawei's Cause
Description
N/A
N/A
Description of a
cause according to
Huawei's knowledge
base.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Parameter
Range
Unit
Description
Supported
Solution Version
Traffic
Information
N/A
N/A

traffic.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Process Information
Issue 03 (2015-07-30)

1837
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>Uplink Data
Volume
[0,+)
Byte
The traffic on the

uplink.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Downlink
Data Volume
[0,+)
Byte
The traffic on the

downlink.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Data Tunnel
Type
Yes
N/A
Tunnel type,
including RNCSGSN-GGSN or
RNC-GGSN.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
No
Yes indicates Direct

Tunnel(BSC/RNCGGSN), the
transmission
efficiency is higher.
No indicates UnDirect Tunnel(BSC/
RNC-SGSNGGSN).
Charging
Information
N/A
N/A

charging.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Charging ID
from GGSN
[1,2^32-1)
N/A
SN of a CHR that is
sent to the billing
center.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Charging
Characteristics
N/A
N/A
Charging attribute of
a UE. This parameter
can be any of the
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Unspecified
Hot billing Charging
Flat rate Charging
Prepaid Charging
Normal Charging
Issue 03 (2015-07-30)

1838
Nastar
Parameters for Viewing PS Core Complaint Analysis Support Results - SGSN MM

MM) results. You can refer to the description when querying PS Core complaint analysis support
(SGSN MM) results.
Base Information
Parameter
Range
Unit
Description
Supported Solution
Version
SN
[1,2^31-1
)
N/A
SN of a reported CHR.
The SN accumulates on
an NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Start Time
N/A
N/A
Start time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
End Time
N/A
N/A
End time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Procedure
Delay Time
0-65535
ms
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
NE Type
N/A
N/A
CN NE types for the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
SGSN
MME
Issue 03 (2015-07-30)
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Board Subrack
No.
0-255
N/A
Subrack number of the

CHRs.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Board Slot No.
0-255
N/A
Slot number of the

device that generates a
CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Board Proc No.
0-65535
N/A
Number of the process

that generates a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0

1839
Nastar
User Information
Parameter
Range
Unit
Description
Supported
Solution Version
IMSI
N/A
N/A
IMSI information of
a subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Note: Only when

you have the "User
can view the IMSI
information.
User ID: Alias
N/A
N/A
User ID, which is

created by the
system when
creating the task.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Alias, which is
created by the user
when creating the
task.
MSISDN
N/A
N/A
MSISDN
information of a
subscriber.
Note: Only when
you have the "User
can view the
MSISDN
information.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
IMEI-TAC
00000000-9999
9999
N/A
IMEI-TAC of the
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Terminal Model
N/A
N/A
Model of the
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
MS Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>GEA/1
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/1
encryption algorithm
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1840
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>SM
capabilities via
dedicated
channels
0/1
N/A
Indicates whether
the dedicatedchannel-based SM
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SM
capabilities via
GPRS channels
0/1
N/A
Indicates whether
the GPRS-channelbased SM capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SS Screening
Indicator string
(2)
0/1
N/A
Indicates whether
the SS screening
indicator is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SoLSA
Capability
0/1
N/A
Indicates whether
the SoLSA
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Revision level
indicator (R99
or later versions
of the protocol
support)
0/1
N/A
Indicates whether
the revision-level
indicator is
supported (by
protocols in 3GPP
Specifications
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1841
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>PFC feature
mode(BSS
packet flow
procedures
support)
0/1
N/A
Indicates whether
the PFC feature
mode (BSS data
packet flow
procedure) is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/2
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/3
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/3
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/4
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/4
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/5
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/5
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/6
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/6
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1842
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>GEA/7
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/7
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LCS VA
capability
0/1
N/A
Indicates whether
the LCS VA
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to
UTRAN Iu
mode capability
0/1
N/A
Indicates whether
the inter-PS
handover (GERAN
to UTRAN
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to EUTRAN S1
mode capability
0/1
N/A
Indicates whether
the inter-PS
handover (GERAN
to E-UTRAN
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EMM
Combined
procedures
Capability
0/1
N/A
Indicates whether
the EMM combined
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>ISR support
0/1
N/A
Indicates whether
ISR is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1843
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>SRVCC to
GERAN/
UTRAN
capability
0/1
N/A
Indicates whether
the SRVCC-toGERAN/UTRAN
handover capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPC capability
0/1
N/A
Indicates whether
the EPC capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A
Indicates whether
the NF capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
UE Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>EPS
encryption
algorithm EEA0
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA1
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm 128-EEA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA2
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm 128-EEA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1844
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS
encryption
algorithm EEA3
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA4
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA5
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA6
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA7
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA0
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1845
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS integrity
0/1
N/A
Indicates whether
the EPS integrity
algorithm 128-EIA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
0/1
N/A
Indicates whether
the EPS integrity
algorithm 128-EIA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA3
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA4
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA5
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA6
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1846
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS integrity
algorithm EIA7
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA0
supported
0/1
N/A
Indicates whether
the UMTS
UEA0 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA1
supported
0/1
N/A
Indicates whether
the UMTS
UEA1 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA2
supported
0/1
N/A
Indicates whether
the UMTS
UEA2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA3
supported
0/1
N/A
Indicates whether
the UMTS
UEA3 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA4
supported
0/1
N/A
Indicates whether
the UMTS
UEA4 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1847
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA5
supported
0/1
N/A
Indicates whether
the UMTS
UEA5 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA6
supported
0/1
N/A
Indicates whether
the UMTS
UEA6 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA7
supported
0/1
N/A
Indicates whether
the UMTS
UEA7 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
(UCS2)
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA1
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA2
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1848
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
integrity
algorithm UIA3
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA4
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA5
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA6
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA7
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1849
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>1xSRVCC
capability
0/1
N/A
Indicates whether
the 1xSRVCC
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Location
services (LCS)
notification
mechanisms
capability
0/1
N/A
Indicates whether
the LCS notification
mechanism
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LTE
Positioning
Protocol (LPP)
capability
0/1
N/A
Indicates whether
the LPP capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Access class
control for
CSFB (ACCCSFB)
capability
0/1
N/A
Indicates whether
the CSFB-accesslevel control
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)
MS P-TMSI
[1,2^31-1)
N/A
P-TMSI received
from a terminal
when a procedure is
initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Allocated PTMSI
[1,2^31-1)
N/A
P-TMSI that the

network allocates to
a terminal.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Index
N/A
N/A
Index number of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

1850
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
User Home
PLMN
N/A
N/A
PLMN in the IMSI of

a subscriber. This
personal data
anonymization.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Authentication
Flag
NoAuth
N/A
MM procedure
requires
authentication.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
N/A
MM procedure
requires IMEI check.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
N/A
MM procedure
requires P-TMSI
reallocation.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
FirAuth
SecAuth
IMEI Check
Flag
Yes
P-TMSI
Reallocation
Flag
Yes
No
No
Access Information
Parameter
Range
Unit
Description
Supported
Solution Version
Type
N/A
N/A

procedure. This
parameter can be any
of the following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SM
MM
Procedure Type
N/A
N/A
Name of a signaling
procedure.
Description of
Signaling Procedures
in the appendix.
Issue 03 (2015-07-30)

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
1851
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Procedure Init
Cause
N/A
N/A
Procedure initiating
party (UE or MME)
and cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

Description of
Procedure Initiating
Causes in the
appendix.
Access Network
Description
N/A
N/A
Description of the
access network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Inter CN Node
Type
0/1
N/A
Access network type

of the source or target
node in the Inter RAU
or Inter Relocation
procedure.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>Access Type
N/A
N/A

(RAN) type for the
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
GPRS
UMTS(W/TD)
LTE
>Source Access
Net Type
GPRS
UMTS(W/TD)
LTE
Issue 03 (2015-07-30)
N/A
Works together with

Inter CN Node Type.
This parameter is
valid only when Inter
CN Node Type is set
to new indicating the
access network type
on the source node.
This parameter is
blank in all the other
cases.

PS 11.0/PS 12.0/PS
12.1/PS 13.0
1852
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>Target Access
Net Type
GPRS
N/A
Works together with

Inter CN Node Type.
This parameter is
CN Node Type is set
to old indicating the
access network type
on the target node.
This parameter is
cases.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
UMTS(W/TD)
LTE
Access BSC/
RNC
Description
N/A
N/A
Description of an NE
that gains access to
the RAN.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>RAI
N/A
N/A
If a procedure does
not involve two
routing areas, the
field indicates the
routing area where
the procedure is
initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
If a procedure
involves two routing
areas, the field
indicates the new
routing area.
Issue 03 (2015-07-30)
>Old RAI
N/A
N/A
If a procedure does
not involve two
routing areas, the
field indicates the
routing area where
the procedure is
initiated. Otherwise,
the field is empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>BSC/RNC
PLMN
N/A
N/A
PLMN serving a BSC

or RNC.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>BSC/RNC ID
N/A
N/A
ID of a BSC or RNC.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>Target RNC
PLMN
N/A
N/A
Target RNC PLMN

in relocation produce
in 3G.
PS 12.0/PS 12.1/PS
13.0

1853
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
>Target RNC
ID
N/A
N/A
Target RNC ID in
relocation produce in
3G.
PS 12.0/PS 12.1/PS
13.0
>CGI
N/A
N/A
Cell where a
procedure is initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Cell Name
[0,200]
N/A
Name of a cell.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Mobility
Information
N/A
N/A
Information about
mobility analysis.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Old SGSN IP
N/A
N/A
If a procedure
involves two SGSNs,
the field indicates the
IP address of the old
SGSN. Otherwise,
the field is empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
DNS Domain
Type
0-19
N/A
DNS Domain Type in

MM produce.
PS 12.0/PS 12.1/PS
13.0
Relocation
Type
0/1
N/A
Relocation Type in
3G.
PS 12.0/PS 12.1/PS
13.0
RFSP ID
1-256
N/A
RFSP (RAT/
Frequency Selection
Priority) ID.
PS 13.0 or later
254

1854
Nastar
Result Information
Parameter
Range
Unit
Description
Supported
Solution Version
Attach Result
N/A
N/A
Helps identify the

result of the
combined attach
procedure. The
values of this
parameter are as
follows:
PS 11.0/PS 12.0/PS
12.1/PS 13.0
GPRS only attached

Combined GPRS/
IMSI attached
Update Result
N/A
N/A
Helps identify the

result of the
combined RAU
procedure. The
values of this
parameter are as
follows:
PS 11.0/PS 12.0/PS
12.1/PS 13.0
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
provided in a
protocol.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Protocol Cause
Description
N/A
N/A
Description of a
protocol cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Huawei's Cause
N/A
N/A

failure cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

Description of
Exception Cause
Fields in the
appendix.
Issue 03 (2015-07-30)

1855
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Huawei's Cause
Description
N/A
N/A
Description of a
cause according to
Huawei's knowledge
base.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Parameters for Viewing PS Core Complaint Analysis Support Results - MME SM

This section describes the parameters for querying PS Core complaint analysis support (MME
(MME SM) results.
Base Information
Parameter
Range
Unit
Description
Supported
Solution Version
SN
[1,2^31-1)
N/A
SN of a reported
CHR. The SN
accumulates on an
NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Start Time
N/A
N/A
Start time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
End Time
N/A
N/A
End time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Procedure
Delay Time
0-65535
ms
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
NE Type
N/A
N/A
CN NE types for the

This parameter can
be any of the
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGSN
MME
Issue 03 (2015-07-30)

1856
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Subrack
No.
0-255
N/A
Subrack number of
the device that
generates CHRs.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Slot No.
0-255
N/A
Slot number of the

a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Proc No.
0-65535
N/A
Number of the
process that
generates a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Parameter
Range
Unit
Description
Supported
Solution Version
IMSI
N/A
N/A
IMSI information of
a subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Information
Note: Only when

you have the "User
can view the IMSI
information.
User ID: Alias
N/A
N/A
User ID, which is

created by the
system when
creating the task.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Alias, which is
created by the user
when creating the
task.
Issue 03 (2015-07-30)

1857
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
MSISDN
N/A
N/A
MSISDN
information of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Note: Only when

you have the "User
can view the
MSISDN
information.
IMEI-TAC
00000000-9999
9999
N/A
IMEI-TAC of the
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Terminal Model
N/A
N/A
Model of the
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
MS Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>GEA/1
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/1
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SM
capabilities via
dedicated
channels
0/1
N/A
Indicates whether
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SM
capabilities via
GPRS channels
0/1
N/A
Indicates whether
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1858
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UCS2 support
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SS Screening
Indicator string
(2)
0/1
N/A
Indicates whether
the SS screening
indicator is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SoLSA
Capability
0/1
N/A
Indicates whether
the SoLSA
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Revision level
indicator (R99
or later versions
of the protocol
support)
0/1
N/A
Indicates whether
the revision-level
indicator is
supported (by
protocols in 3GPP
Specifications
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PFC feature
mode(BSS
packet flow
procedures
support)
0/1
N/A
Indicates whether
the PFC feature
mode (BSS data
packet flow
procedure) is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/2
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/2
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1859
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>GEA/3
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/3
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/4
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/4
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/5
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/5
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/6
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/6
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/7
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/7
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LCS VA
capability
0/1
N/A
Indicates whether
the LCS VA
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1860
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>PS inter-RAT
HO from
GERAN to
UTRAN Iu
mode capability
0/1
N/A
Indicates whether
the inter-PS
handover (GERAN
to UTRAN
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to EUTRAN S1
mode capability
0/1
N/A
Indicates whether
the inter-PS
handover (GERAN
to E-UTRAN
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EMM
Combined
procedures
Capability
0/1
N/A
Indicates whether
the EMM combined
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>ISR support
0/1
N/A
Indicates whether
ISR is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SRVCC to
GERAN/
UTRAN
capability
0/1
N/A
Indicates whether
handover capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPC capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1861
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>NF capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
UE Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>EPS
encryption
algorithm EEA0
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA1
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm 128EEA1 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA2
supported
0/1
N/A
Indicates whether
the EPS encryption
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA3
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA4
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1862
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS
encryption
algorithm EEA5
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA6
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA7
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA0
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
0/1
N/A
Indicates whether
the EPS integrity
algorithm 128-EIA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
0/1
N/A
Indicates whether
the EPS integrity
algorithm 128-EIA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1863
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS integrity
algorithm EIA3
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA4
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA5
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA6
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA7
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA0
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1864
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA1
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA2
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA3
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA4
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA5
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1865
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA6
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA7
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
(UCS2)
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA1
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA2
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA3
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1866
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
integrity
algorithm UIA4
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA5
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA6
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA7
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>1xSRVCC
capability
0/1
N/A
Indicates whether
the 1xSRVCC
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1867
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>Location
services (LCS)
notification
mechanisms
capability
0/1
N/A
Indicates whether
mechanism
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LTE
Positioning
Protocol (LPP)
capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Access class
control for
CSFB (ACCCSFB)
capability
0/1
N/A
Indicates whether
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
User Index
N/A
N/A
Index number of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Home
PLMN
N/A
N/A
PLMN in the IMSI

of a subscriber. This
personal data
anonymization.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Access Information
Parameter
Range
Unit
Description
Supported Solution
Version
Type
N/A
N/A

procedure. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
SM
MM
Issue 03 (2015-07-30)

1868
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
Procedure Type
N/A
N/A
Name of a signaling
procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Procedure Init
Cause
N/A
N/A

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

appendix.
Access eNodeB
Information
N/A
N/A
Information of the
eNodeB where a UE
accesses.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>eNodeB
PLMN
N/A
N/A
PLMN of the eNodeB

where a UE is located
when a signaling
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>eNodeB ID
[1,2^31
-1)
N/A
ID of the eNodeB where

a UE is located when a
signaling procedure is
initiated.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
MME UE S1AP
ID
[1,2^31
-1)
N/A
UES1AP connection
identification allocated
by an MME in a traffic
procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
MME S1AP ID
Time
N/A
N/A
Time when the UES1AP

connection identification
is allocated by an MME
in a traffic procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Current TAC
N/A
N/A
Tracking area where a

terminal is located when
a signaling procedure is
initiated.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
PDN Type
N/A
N/A
Requested PDN type in a

traffic procedure. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
IPV4
IPV6
both(IPV4 & IPV6)
unused
Issue 03 (2015-07-30)

1869
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
PDN Type In
Used
N/A
N/A
Used PDN type in a

the following:
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
IPV4
IPV6
both(IPV4 & IPV6)
unused
Issue 03 (2015-07-30)
PDN Address In
Used
IPv4,
IPv6
N/A
Used PDN address in a

traffic procedure.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
APN
N/A
N/A
Requested APN in a
traffic procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
APN In Used
N/A
N/A
Requested APN in a
traffic procedure.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
Serving
Gateway
Address
N/A
N/A
IP address of the Serving

Gateway in a signaling
procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
PDN Gateway
Address
N/A
N/A
IP address of the PDN

procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
PDN Gateway
Host Name
N/A
N/A
Domain name of the

PDN Gateway in a
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
QoS
N/A
N/A

QoS.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>QCI
0-255
N/A
QCI information
allocated by a session.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>ARP
0-255
N/A
ARP information
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>UE Uplink
Max Bandwidth
[1,2^31
-1)
bit/s
Maximum UE-level
uplink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>UE Downlink
Max Bandwidth
[1,2^31
-1)
bit/s
Maximum UE-level
downlink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

1870
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>APN Uplink
Max Bandwidth
[1,2^31
-1)
bit/s
Maximum APN-level
uplink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>APN
Downlink Max
Bandwidth
[1,2^31
-1)
bit/s
Maximum APN-level
downlink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>GBR Uplink
[1,2^31
-1)
bit/s
Maximum bearer-level
uplink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>GBR
Downlink
[1,2^31
-1)
bit/s
downlink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>MBR Uplink
[1,2^31
-1)
bit/s
Guaranteed bearer-level
uplink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>MBR
Downlink
[1,2^31
-1)
bit/s
downlink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
IMS Flag
0/1
N/A
Identity of an IMS. The

(enumerated) values of
this parameter are as
follows:
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
0: non-IMS PDN
1: IMS PDN
S1-U Serving
Gateway
Address1
l IPv
4
S1-U Serving
Gateway
Address2
l IPv
4
S1-U eNodeB
Address1
l IPv
4
N/A
S1-U Serving Gateway

Address1.
PS 12.0/PS 12.1/PS 13.0
N/A

Address2.
PS 12.0/PS 12.1/PS 13.0
N/A
S1-U eNodeB Address1.
PS 12.0/PS 12.1/PS 13.0
l IPv
6
l IPv
6
l IPv
6
Issue 03 (2015-07-30)

1871
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
S1-U eNodeB
Address2
l IPv
4
N/A
PS 12.0/PS 12.1/PS 13.0
N/A
Serving Gateway
Address2.
PS 12.0/PS 12.1/PS 13.0
N/A
PDN Gateway Address2.
PS 12.0/PS 12.1/PS 13.0
l IPv
6
Serving
Gateway
Address2
l IPv
4
PDN Gateway
Address2
l IPv
4
l IPv
6
l IPv
6
Result Information
Parameter
Range
Unit
Description
Supported Solution
Version
Protocol Cause
N/A
N/A
Negotiated cause in a
procedure result.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Protocol Cause
Description
N/A
N/A
Description of a
protocol cause.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Huawei's Cause
N/A
N/A

failure cause.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Huawei's Cause
Description
N/A
N/A
Description of a cause
according to Huawei's
knowledge base.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Parameters for Viewing PS Core Complaint Analysis Support Results - MME MM

(MME MM) results.
Issue 03 (2015-07-30)

1872
Nastar
Base Information
Parameter
Range
Unit
Description
Supported
Solution Version
SN
[1,2^31-1)
N/A
SN of a reported
CHR. The SN
accumulates on an
NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Start Time
N/A
N/A
Begin time of the

signaling
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
End Time
N/A
N/A
End time of the

signaling
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Procedure
Delay Time
0-65535
ms
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
NE Type
N/A
N/A
CN NE types for the

signaling
procedure. This
parameter can be
any of the
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGSN
MME
Issue 03 (2015-07-30)
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Subrack
No.
0-255
N/A
Subrack number of
the device that
generates CHRs.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Slot No.
0-255
N/A
Slot number of the

device that
generates a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Proc No.
0-65535
N/A
Number of the
process that
generates a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

1873
Nastar
User Information
Parameter
Range
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Note: Only when you

have the "User Identity"
right, you can view the
IMSI information.
User ID: Alias
N/A
N/A
User ID, which is

Alias, which is created
by the user when
creating the task.
MSISDN
N/A
N/A
MSISDN information of
a subscriber.
Note: Only when you
MSISDN information.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
IMEI-TAC
00000000-9999
9999
N/A
IMEI-TAC of the
terminal that initiates a
service.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Terminal Model
N/A
N/A

that initiates a service.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
MS Network
Capability
N/A
N/A

capability.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
>GEA/1
encryption
algorithm
0/1
N/A

GEA/1 encryption
algorithm is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1874
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>SM
capabilities via
dedicated
channels
0/1
N/A

dedicated-channelbased SM capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>SM
capabilities via
GPRS channels
0/1
N/A

GPRS-channel-based
SM capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UCS2 support
0/1
N/A
Indicates whether UCS2

is supported.
0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
>SS Screening
Indicator string
(2)
0/1
N/A
Indicates whether the SS

screening indicator is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>SoLSA
Capability
0/1
N/A

SoLSA capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>Revision level
indicator (R99
or later versions
of the protocol
support)
0/1
N/A

revision-level indicator
is supported (by
protocols in 3GPP
Specifications Release
99 or later).
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1875
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>PFC feature
mode(BSS
packet flow
procedures
support)
0/1
N/A

PFC feature mode (BSS
data packet flow
procedure) is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/2
encryption
algorithm
0/1
N/A

GEA/2 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/3
encryption
algorithm
0/1
N/A

GEA/3 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/4
encryption
algorithm
0/1
N/A

GEA/4 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/5
encryption
algorithm
0/1
N/A

GEA/5 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/6
encryption
algorithm
0/1
N/A

GEA/6 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/7
encryption
algorithm
0/1
N/A

GEA/7 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1876
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>LCS VA
capability
0/1
N/A

LCS VA capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to
UTRAN Iu
mode capability
0/1
N/A

inter-PS handover
(GERAN to UTRAN
handover) capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to EUTRAN S1
mode capability
0/1
N/A

inter-PS handover
(GERAN to E-UTRAN
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EMM
Combined
procedures
Capability
0/1
N/A

EMM combined
procedure capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>ISR support
0/1
N/A
Indicates whether ISR is

supported.
0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
>SRVCC to
GERAN/
UTRAN
capability
0/1
N/A

SRVCC-to-GERAN/
UTRAN handover
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1877
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>EPC capability
0/1
N/A

EPC capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>NF capability
0/1
N/A
Indicates whether the NF

0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
UE Network
Capability
N/A
N/A
Indicates the UE-related

terminal capability.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
>EPS
encryption
algorithm EEA0
supported
0/1
N/A

EPS encryption
algorithm EEA0 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA1
supported
0/1
N/A

EPS encryption
algorithm 128-EEA1 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA2
supported
0/1
N/A

EPS encryption
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA3
supported
0/1
N/A

EPS encryption
algorithm EEA3 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1878
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>EPS
encryption
algorithm EEA4
supported
0/1
N/A

EPS encryption
algorithm EEA4 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA5
supported
0/1
N/A

EPS encryption
algorithm EEA5 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA6
supported
0/1
N/A

EPS encryption
algorithm EEA6 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA7
supported
0/1
N/A

EPS encryption
algorithm EEA7 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA0
supported
0/1
N/A

EPS integrity algorithm
EIA0 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
0/1
N/A

128-EIA1 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1879
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>EPS integrity
0/1
N/A

PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA3
supported
0/1
N/A

EIA3 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA4
supported
0/1
N/A

EIA4 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA5
supported
0/1
N/A

EIA5 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA6
supported
0/1
N/A

EIA6 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA7
supported
0/1
N/A

EIA7 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA0
supported
0/1
N/A

UMTS encryption
algorithm UEA0 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1880
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>UMTS
encryption
algorithm
UEA1
supported
0/1
N/A

UMTS encryption
algorithm UEA1 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA2
supported
0/1
N/A

UMTS encryption
algorithm UEA2 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA3
supported
0/1
N/A

UMTS encryption
algorithm UEA3 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA4
supported
0/1
N/A

UMTS encryption
algorithm UEA4 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA5
supported
0/1
N/A

UMTS encryption
algorithm UEA5 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA6
supported
0/1
N/A

UMTS encryption
algorithm UEA6 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1881
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>UMTS
encryption
algorithm
UEA7
supported
0/1
N/A

UMTS encryption
algorithm UEA7 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UCS2 support
(UCS2)
0/1
N/A

is supported.
0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
>UMTS
integrity
algorithm UIA1
supported
0/1
N/A

UMTS integrity
algorithm UIA1 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA2
supported
0/1
N/A

UMTS integrity
algorithm UIA2 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA3
supported
0/1
N/A

UMTS integrity
algorithm UIA3 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA4
supported
0/1
N/A

UMTS integrity
algorithm UIA4 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1882
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>UMTS
integrity
algorithm UIA5
supported
0/1
N/A

UMTS integrity
algorithm UIA5 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA6
supported
0/1
N/A

UMTS integrity
algorithm UIA6 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA7
supported
0/1
N/A

UMTS integrity
algorithm UIA7 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>NF capability
0/1
N/A

0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
>1xSRVCC
capability
0/1
N/A

1xSRVCC capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>Location
services (LCS)
notification
mechanisms
capability
0/1
N/A

LCS notification
mechanism capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>LTE
Positioning
Protocol (LPP)
capability
0/1
N/A

LPP capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

1883
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Access class
control for
CSFB (ACCCSFB)
capability
0/1
N/A

CSFB-access-level
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)
MS P-TMSI
0-2^32-1
N/A
P-TMSI received from a

terminal when a
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Allocated PTMSI
0-2^32-1
N/A
P-TMSI that the network

allocates to a terminal.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
User Index
N/A
N/A
Index number of a
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
User Home
PLMN
N/A
N/A
PLMN in the IMSI of a

subscriber. This
personal data
anonymization.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1884
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Special Service
Indication
N/A
N/A
Indication of a special
service. The values of
follows:
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
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.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Authentication
Flag
NoAuth
N/A
MM procedure requires
authentication.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
FirAuth
SecAuth
Issue 03 (2015-07-30)
IMEI Check
Flag
Yes/No
N/A
IMEI check.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
P-TMSI
Reallocation
Flag
Yes/No
N/A
P-TMSI reallocation.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1885
Nastar
Access Information
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
Type
N/A
N/A
Type of the signaling procedure.

following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SM
MM
Procedure Type
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure Init
Cause
N/A
N/A
Procedure initiating party (UE or

MME) and cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
For details, see the Description of

Procedure Initiating Causes in the
appendix.
Access Network
Description
N/A
N/A
Description of the access network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>Inter CN Node
Type
0/1
N/A
Access network type of the source

or target node in the Inter RAU or
Inter Relocation procedure.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
>Access Type
N/A
N/A
Radio access network (RAN) type

for the signaling procedure. This
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
GPRS
UMTS(W/TD)
LTE
>Source Access
Net Type
Issue 03 (2015-07-30)
N/A
N/A
Works together with Inter CN Node

Type. This parameter is valid only
when Inter CN Node Type is set to
new indicating the access network
type on the source node. This
parameter is blank in all the other
cases.

PS 11.0/PS 12.0/
PS 12.1/PS 13.0
1886
Nastar
Issue 03 (2015-07-30)
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
>Target Access
Net Type
N/A
N/A

old indicating the access network
type on the target node. This
cases.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
SGW Change
Flag
0/1
N/A
Indicates whether the S-GW has

been changed in the TAU/HO
procedure.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Access eNodeB
Information
N/A
N/A
Information about the eNodeB that

serves a terminal when a signaling
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>eNodeB
PLMN
N/A
N/A
PLMN of the eNodeB where a UE

is located when a signaling
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>eNodeB ID
0-2^
32-1
N/A
ID of the eNodeB that serves a UE

when a signaling procedure is
initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME UE S1AP
ID
0-2^
32-1
N/A
UES1AP connection identification

allocated by an MME in a traffic
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME UE S1AP
ID Time
N/A
N/A

connection identification is
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Current TAC
N/A
N/A
Tracking area where a terminal is

located when a signaling procedure
is initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
New GUTI
PLMN
N/A
N/A
PLMN of GUTI allocated by the

network in a traffic procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1887
Nastar
Issue 03 (2015-07-30)
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
New GUTI
MMEGI
0-65
535
N/A
MME Group Id of GUTI allocated

by the network in a traffic
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
New GUTI
MMEC
0-25
5
N/A
MME CODE of GUTI allocated by

the network in a traffic procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
New GUTI
MTMSI
0-2^
32-1
N/A
M-TMSI of GUTI allocated by the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old GUTI
PLMN
N/A
N/A
PLMN of GUTI received from a UE

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old GUTI
MMEGI
0-65
535
N/A
MME Group Id of GUTI received

from a UE in a traffic procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old GUTI
MMEC
0-25
5
N/A
MME CODE of GUTI received

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old GUTI
MTMSI
0-2^
32-1
N/A
M-TMSI of GUTI received from a

UE in a traffic procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old TAC
N/A
N/A
ID of the old tracking area in a

signaling procedure that involves
more than one tracking area.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Target eNodeB
Information
N/A
N/A
Information about the target

eNodeB in an inter-eNodeB
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>Target ID
PLMN
N/A
N/A
PLMN of the target eNodeB in a

more than one eNodeB.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1888
Nastar
Issue 03 (2015-07-30)
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
>Target ID
0-2^
32-1
N/A
ID of the target eNodeB in a

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Target TAC
N/A
N/A
ID of the target tracking area in a

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Gateway
Address
N/A
N/A
IP address of the Serving Gateway

in a signaling procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Gateway Host
Name
N/A
N/A
Domain name of the Serving

Gateway in a signaling procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
GU RAI
N/A
N/A
If a UE is handed over from a LTE

network to a 2G/3G network or the
location of the UE is updated, the
field is the RAC of the target routing
area. Otherwise, the field is empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
GU Cell
N/A
N/A

field is the CGI of the target cell.
Otherwise, the field is empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
GU Old RAI
N/A
N/A
If a UE is handed over from a 2G/

3G network to a LTE network or the
field is the RAC of the old routing
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Mobility
Information
N/A
N/A
Information about mobility

analysis.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>Old SGSN IP
N/A
N/A
If a procedure involves two SGSNs,

the field indicates the IP address of
the old SGSN.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1889
Nastar
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
DNS Domain
Type
0-20
N/A
DNS Domain Type in MM produce.
PS 12.0/PS 12.1/
PS 13.0
254
Result Information
Parameter
Range
Unit
Description
Supported
Solution Version
EPS Attach
Result
N/A
N/A
Helps identify the

result of the combined
attach procedure.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
EPS only
combined EPS/IMSI
attach
EPS Update
Result
N/A
N/A
Helps identify the

RAU procedure. The
values of this
parameter are as
follows:
PS 11.0/PS 12.0/PS
12.1/PS 13.0
TA updated
combined TA/LA
updated
TA updated and ISR
activated (NOTE)
combined TA/LA
updated and ISR
activated (NOTE)
Additional
Update Result
N/A
N/A
Result of the
additional update
procedure. The values
of this parameter are
as follows:
PS 11.0/PS 12.0/PS
12.1/PS 13.0
no additional
information
CS Fallback not
preferred
SMS only
reserved
Issue 03 (2015-07-30)

1890
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
SGS RePaging
Count
N/A
N/A
Sgs paging repeat

sending times.
Default is 0, means no
repeat sending.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
VoIMS Bear
Status
N/A
N/A
To describe the Voice

bearer(QCI=1) status
before and after the
Procedure. Bit1~Bit2
is used,Bit3~Bit8 is
retain.Default value is
0.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
VoIMS Bearer Status

(octet 1) Bearer of
QCI1 Exist Flag
before Handover
Procedure (octet 1, bit
1).
0 Bearer of QCI1 Not
Exist before
Handover Procedure.
1 Bearer of QCI1
Exist before
Handover Procedure
Bearer(QCI=1) Exist
Flag after Handover
2).
Exist after Handover
Procedure.
1 Bearer of QCI1
Procedure.
Issue 03 (2015-07-30)

1891
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
SRVCC Cause
ID
N/A
N/A
SRVCC cause value.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
In case of SRVCC(CS
+PS), SRVCC Cause
is used to describe PS
Handover failure
cause,Huawei's
Cause is used to
describe CS
Handover failure
cause.
Default value is 0. In
case of SRVCC(CS
Only) or no-SRVCC,
the value is fixed to 0.
In case of SRVCC(CS
+PS), the value is
meaningful.
Issue 03 (2015-07-30)
SRVCC Cause
N/A
N/A
Description of
SRVCC cause.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
VoIMS Bear
Status
N/A
N/A
Status of a voice
bearer (with a leve-1
QCI) before and after
the procedure is
executed.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Protocol Cause
N/A
N/A
Protocol cause value

in a procedure result.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Protocol Cause
Description
N/A
N/A
Description of a
protocol cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Huawei's Cause
N/A
N/A

failure cause value.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Huawei's Cause
Description
N/A
N/A
knowledge base.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

1892
Nastar
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.
Base Information
Parameter
Range
Unit
Description
Supported
Solution
Version
CHR SN
[1,2^31-1
)
N/A
SN of a reported CHR. The SN

accumulates on an NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
End Time
N/A
N/A

procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
NE Type
GGSN
N/A
CN NE types for the signaling

procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SGW
PGW
SGW
+PGW
NE Name
N/A
User Information
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

User ID: Alias
N/A
N/A

Alias, which is created by the user
Issue 03 (2015-07-30)

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
1893
Nastar
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
MSISDN
N/A
N/A
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

Terminal Model
N/A
N/A
Model of the terminal that initiates

a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
IMEI-TAC
0000
0000
-999
9999
9
N/A
IMEI-TAC of the terminal that

initiates a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure Information-Common
Parameter
Range
Unit
Description
Supported
Solution
Version
Procedure Type
N/A
N/A
Name of a signaling
procedure.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
APN
N/A
N/A
Requested APN in a traffic

procedure.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Access Net
Type
NA
N/A
Type of the RAN involved in

the signaling procedure
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
UTRAN
GERAN
WLAN
GAN
HSPA
Evolution
EUTRAN
Issue 03 (2015-07-30)

1894
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
Cause
N/A
N/A

carried in an Access
message.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

Description of Exception
Cause in the appendix.
Procedure Information-Create PDP

Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Type
X25
N/A
Type of the PDP when the

context is activated
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PPP
OSP_IHOS
S
IPV4
IPV6
IPV4V6
Issue 03 (2015-07-30)
MS IP V4
N/A
N/A
IPv4 address allocated to the

subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS IP V6
N/A
N/A

subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN Address
for Signaling
N/A
N/A
IPv4 address for configuring the

control plane of the SGSN that
the subscriber's MS accesses
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1895
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN IPv6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN Address
for Data
N/A
N/A

user plane of the SGSN that the
subscriber's MS accesses
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN IPv6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN Address
for Signaling
N/A
N/A

control plane of the GGSN that
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN IPv6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN Address
for Data
N/A
N/A

user plane of the GGSN that the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN IPv6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Protocol
Version
GTPv0
N/A
Version of the GTP protocol
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GTPv1
GTPv2
Issue 03 (2015-07-30)

1896
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cause
N/A
N/A
Cause value carried in the

response message for creating
the PDP context. For details, see
7.7.1 in 3GPP 29.060.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN PLMN
N/A
N/A
Information about the PLMN

served by the access SGSN
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A
Location area where the

signaling procedure is triggered
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A
Routing area where the

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SAC
N/A
N/A
Serving area where the

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CI
N/A
N/A
Cell where the signaling

procedure is triggered
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Netwrok Layer
Service Access
Point Identifier
N/A
N/A
Identity of the service access

point (SAP) in the network
layer
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Activation Type
First
activation
N/A
Identifies whether an activation

is a first or second activation
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Second
activation
Unknown
Issue 03 (2015-07-30)

1897
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TEID-C
N/A
N/A
Identity of the GTP-C tunneling

protocol
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Charging
Characteristics
Unspecifie
d
N/A
Marks different charging

characteristics.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Hot billing
Charging
For detailed characteristic

description, see UGW product
documentation.
Flat rate
Charging
Prepaid
Charging
Normal
Charging
Reliability
Class
N/A
N/A
Subscribed reliability class.

following:
Unused. If received, it shall be
interpreted as '010' (Note)
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Unacknowledged GTP;
Acknowledged LLC and RLC,
Protected data
Unacknowledged GTP and
LLC; Acknowledged RLC,
Protected data
Unacknowledged GTP, LLC,
and RLC, Protected data
and RLC, Unprotected data
Delay Class
N/A
N/A
Subscribed delay class. This

following:
Delay class 1
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Delay Class 2
Delay Class 3
Delay Class 4 (best effort)
Reserved
Issue 03 (2015-07-30)

1898
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Precedence
Class
N/A
N/A
Subscribed precedence. This

following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
High priority
Normal priority
Low priority
Reserved
Peak
Throughput
N/A
N/A
Subscribed peak throughput.

following:
Subscribed peak throughput
Up to 1 000 octet/s
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Up to 2 000 octet/s
Up to 4 000 octet/s
Up to 8 000 octet/s
Up to 16 000 octet/s
Reserved
Issue 03 (2015-07-30)

1899
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Mean
Throughput
N/A
N/A
Subscribed mean throughput.

following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
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
Erroneous SDU
N/A
N/A
following:
erroneous SDUs
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
No detect('-')
Erroneous SDUs are delivered
('yes')
delivered ('no')
Reserved
Issue 03 (2015-07-30)

1900
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Delivery Order
N/A
N/A
Subscribed delivery order. This

following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Subscribed delivery order

With delivery order ('yes')
Without delivery order ('no')
Reserved
Traffic Class
N/A
N/A
Subscribed traffic class. This

following:
Subscribed traffic class
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Streaming class
Interactive class
Background class
Reserved
Maximum SDU
Size
0-255
Byte
Maximum SDU length.

Subscribed maximum SDU size
150: 10~1500 octets
151: 1502 octets
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
152: 1510 octets

153: 1520 octets
Reserved
Issue 03 (2015-07-30)
Maximum Bit
Rate for Uplink
0-8640
Maximum Bit
Rate for
Downlink
0-256000
bps
Maximum uplink rate

Subscribed maximum bit rate
for uplink
bps

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
1901
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SDU Error
Ratio
N/A
N/A
Subscribed residual BER. This

following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
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
Reserved
Residual BER
N/A
N/A

following:
5*10^2
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
1*10^2
5*10^3
4*10^3
1*10^3
1*10^4
1*10^5
1*10^6
6*10^8
Reserved
Traffic
Handling
priority
N/A
N/A
Traffic Handling priority.

Subscribed traffic handling
priority
Priority level 1
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Priority level 2
Priority level 3
Issue 03 (2015-07-30)

1902
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Transfer Delay
0-255
ms
Transfer delay.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Subscribed transfer delay

10~150ms
200~950ms
1000~4000ms
Reserved
Guaranteed Bit
Rate for Uplink
0-8640
Guaranteed Bit
Rate for
Downlink
0-256000
bps

for uplink.
bps
Guaranteed downlink rate.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure Information-Update PDP/Delete PDP

Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Type
X25
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PPP
OSP_IHOSS
IPV4
IPV6
IPV4V6
Issue 03 (2015-07-30)
MS IP V4
N/A
N/A
IPv4 address allocated to

the subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS IP V6
N/A
N/A

the subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1903
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN Address
for Signaling
N/A
N/A
IPv4 address for

configuring the control
plane of the SGSN that the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN IPv6
Address for
Signaling
N/A
N/A
IPv6 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN Address
for Data
N/A
N/A
IPv4 address for

configuring the user plane
of the SGSN that the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN IPv6
Address for
Data
N/A
N/A
IPv6 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN Address
for Signaling
N/A
N/A
IPv4 address for

plane of the GGSN that the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN IPv6
Address for
Signaling
N/A
N/A
IPv6 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN Address
for Data
N/A
N/A
IPv4 address for

of the GGSN that the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN IPv6
Address for
Data
N/A
N/A
IPv6 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1904
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Protocol
Version
GTPv0
N/A
Version of the GTP

protocol
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
N/A
Initiator of the signaling

procedure recorded in the
CHR.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GTPv1
GTPv2
Procedure
Organizer
SSGN
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Cause
N/A
N/A

response message for
creating the PDP context.
For details, see 7.7.1 in
3GPP 29.060.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN PLMN
N/A
N/A

PLMN served by the access
SGSN
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A

triggered
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A

triggered
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SAC
N/A
N/A

triggered
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1905
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CI
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Netwrok Layer
Service Access
Point Identifier
N/A
N/A
Identity of the service

access point (SAP) in the
network layer
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
TEID-C
N/A
N/A
Identity of the GTP-C

tunneling protocol
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Charging
Characteristics
Unspecified
N/A

characteristics.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Hot billing
Charging
Flat rate
Charging

description, see UGW
Prepaid
Charging
Normal
Charging
Issue 03 (2015-07-30)

1906
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Reliability Class
N/A
N/A

This parameter can be any
of the following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Unused. If received, it shall

be interpreted as
'010' (Note)
Unacknowledged GTP;
RLC, Protected data
Protected data
Unacknowledged GTP,
data
Unacknowledged GTP,
LLC, and RLC,
Unprotected data
Delay Class
N/A
N/A

of the following:
Delay class 1
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Delay Class 2
Delay Class 3
Reserved
Precedence
Class
N/A
N/A
of the following:
High priority
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Normal priority
Low priority
Reserved
Issue 03 (2015-07-30)

1907
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Peak
Throughput
N/A
N/A
Subscribed peak
throughput. This parameter
can be any of the following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
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
Reserved
Issue 03 (2015-07-30)

1908
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Mean
Throughput
N/A
N/A
Subscribed mean
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
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
Erroneous SDU
N/A
N/A
following:
erroneous SDUs
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
No detect('-')
Erroneous SDUs are
delivered('yes')
delivered ('no')
Reserved
Issue 03 (2015-07-30)

1909
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Delivery Order
N/A
N/A
Subscribed delivery order.

of the following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

('no')
Reserved
Traffic Class
N/A
N/A

of the following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Streaming class
Interactive class
Background class
Reserved
Maximum SDU
Size
0-255
Byte
Maximum SDU length.

Subscribed maximum SDU
size
150: 10~1500 octets
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
151: 1502 octets

152: 1510 octets
153: 1520 octets
Reserved
Issue 03 (2015-07-30)
Maximum Bit
Rate for Uplink
0-8640
Maximum Bit
Rate for
Downlink
0-256000
bps
Maximum uplink rate

Subscribed maximum bit
rate for uplink
bps

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
1910
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SDU Error
Ratio
N/A
N/A

of the following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

ratio
1*10^2
7*10^3
1*10^3
1*10^4
1*10^5
1*10^6
1*10^1
Reserved
Residual BER
N/A
N/A

of the following:
5*10^2
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
1*10^2
5*10^3
4*10^3
1*10^3
1*10^4
1*10^5
1*10^6
6*10^8
Reserved
Traffic
Handling
priority
N/A
N/A

Subscribed traffic
handling priority
Priority level 1
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Priority level 2
Priority level 3
Issue 03 (2015-07-30)

1911
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Transfer Delay
0-255
ms
Transfer delay.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

10~150ms
200~950ms
1000~4000ms
Reserved
Guaranteed Bit
Rate for Uplink
0-8640
Guaranteed Bit
Rate for
Downlink
0-256000
bps

rate for uplink.
bps
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure Information-Create Session
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^311)
N/A
Unique ID of the whole procedure

for a subscriber to use a web
service through the MS. This
parameter distinguishes between
the multiple web service
procedures for the same subscriber.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure NO.
[1,2^311)
N/A
Unique No. of each service

procedure in the whole procedure
for a subscriber
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1912
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Message
Organizer
SSGN
N/A
Initiator of the signaling message

recorded in the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW
+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A
Logical board No. of the device

that processes the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
Logical CPU No. of the device that

processes the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
SPU group No. of the device that

processes the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
SPU instance No. of the device that

processes the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the subscriber's

serving network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CI
N/A
N/A
CGI information, including MCC,

MNC, LAC, and CI
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1913
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SAC
N/A
N/A
SAI information, including MCC,

MNC, LAC, and SAC
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A
RAI information, including MCC,

MNC, LAC, and RAC
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
TAC
N/A
N/A
TAI information, including MCC,

MNC, and TAC
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
ECI
N/A
N/A
ECGI information, including

MCC, MNC, and ECI
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A
LAI information, including MCC,

MNC, and LAC
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS IP V4
N/A
N/A

subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS IP V6
N/A
N/A

subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV4
Address for
Signaling
N/A
N/A

control plane of the CN NE
interconnected to this NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1914
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Peer IPV4
Address for
Data
N/A
N/A

user plane of the CN NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Signaling
N/A
N/A

control plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Data
N/A
N/A

user plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1915
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Selection Mode
MS or
network
provided
APN,
subscrib
ed
verified
N/A
APN selection mode
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
N/A
Type of the PDN, including IPv4,

IPv6, and IPv4v6
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS
provided
APN,
subscrip
tion not
verified
Network
provided
APN,
subscrip
tion not
verified
PDN Type
IPv4
IPv6
IPv4v6
Issue 03 (2015-07-30)
Linked EPS
Bearer ID
N/A
N/A
ID of the default bearer. This

parameter can also be used to
identify the PDN connection.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
EPS Bearer ID
N/A
N/A
ID of all bearers (including the

default bearer) for the PDN
connection
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS PCI
N/A
N/A
PCI in the Bearer QoS parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1916
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer QoS PL
N/A
N/A
PL in the Bearer QoS parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS PVI
N/A
N/A
PVI in the Bearer QoS parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS QCI
N/A
N/A
QCI in the Bearer QoS parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS
MBRU
N/A
N/A
MBRU in the Bearer QoS

parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS
MBRD
N/A
N/A
MBRD in the Bearer QoS

parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS
GBRU
N/A
N/A
GBRU in the Bearer QoS

parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS
GBRD
N/A
N/A
GBRD in the Bearer QoS

parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
UE Time Zone
N/A
N/A
Time zone information of the UE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1917
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Charging
Characteristics
Unspeci
fied
N/A

characteristics.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Hot
billing
Chargin
g

documentation.
Flat rate
Chargin
g
Prepaid
Chargin
g
Normal
Chargin
g
Protocol Cause
N/A
N/A
Standard cause value carried in the

response message
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure Information-Delete Session
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A
Unique ID of the
whole
procedure for a
subscriber to use
a web service
through the MS.
This parameter
distinguishes
between the
multiple web
service
procedures for
the same
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1918
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Procedure NO.
[1,2^31-1)
N/A
Unique No. of
each service
procedure in the
whole
procedure for a
subscriber
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Message
Organizer
SSGN
N/A
Initiator of the
signaling
message
recorded in the
CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A
Logical board
No. of the
device that
processes the
CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
Logical CPU
No. of the
device that
processes the
CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
SPU group No.

of the device
that processes
the CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
SPU instance
No. of the
device that
processes the
CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Serving
Network
N/A
N/A
MCC and MNC

of the
subscriber's
serving network
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
CI
N/A
N/A
CGI
information,
including MCC,
MNC, LAC, and
CI
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1919
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SAC
N/A
N/A
SAI
information,
including MCC,
MNC, LAC, and
SAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A
RAI
information,
including MCC,
MNC, LAC, and
RAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
TAC
N/A
N/A
TAI
information,
including MCC,
MNC, and TAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
ECI
N/A
N/A
ECGI
information,
including MCC,
MNC, and ECI
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A
LAI
information,
including MCC,
MNC, and LAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Linked EPS
Bearer ID
N/A
N/A
ID of the default
bearer. This
parameter can
also be used to
identify the
PDN
connection.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
EPS Bearer ID
N/A
N/A
ID of all bearers
(including the
default bearer)
for the PDN
connection
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
UE Time Zone
N/A
N/A
Time zone
information of
the UE
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1920
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Protocol Cause
N/A
N/A
Standard cause
value carried in
the response
message
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure Information-Create Bearer/Modify Bearer/Update Bearer

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^311)
N/A
Unique ID of the whole

procedure for a subscriber to use
a web service through the MS.
This parameter distinguishes
between the multiple web
service procedures for the same
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure No.
[1,2^311)
N/A

procedure in the whole
procedure for a subscriber
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Message
Organizer
SSGN
N/A

message recorded in the CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW
+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
Logical CPU No. of the device

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1921
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SPU Group
N/A
N/A

processes the CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
SPU instance No. of the device

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

subscriber's serving network
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
CI
N/A
N/A
CGI information, including

MCC, MNC, LAC, and CI
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SAC
N/A
N/A
SAI information, including

MCC, MNC, LAC, and SAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A
RAI information, including

MCC, MNC, LAC, and RAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
TAC
N/A
N/A
TAI information, including

MCC, MNC, and TAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
ECI
N/A
N/A

MCC, MNC, and ECI
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A
LAI information, including

MCC, MNC, and LAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Peer IPV4
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1922
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Peer IPV4
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure
Transaction ID
(PTI)
N/A
N/A
ID dynamically allocated by the

UE used for modifying and
deactivating the bearer
resources requested by the UE.
The PTI is released when the
modification or deactivation
procedure ends.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Linked EPS
Bearer ID
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1923
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
EPS Bearer ID
N/A
N/A

connection
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS PCI
N/A
N/A
PCI in the Flow QoS parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS PL
N/A
N/A
PL in the Flow QoS parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS PVI
N/A
N/A
PVI in the Flow QoS parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS QCI
N/A
N/A
QCI in the Flow QoS parameter PS 10.0/PS

10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS
MBRU
N/A
N/A
MBRU in the Flow QoS

parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS
MBRD
N/A
N/A
MBRD in the Flow QoS

parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS
GBRU
N/A
N/A
GBRU in the Flow QoS

parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS
GBRD
N/A
N/A
GBRD in the Flow QoS

parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
UE Time Zone
N/A
N/A
Time zone information of the

UE
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

1924
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Protocol Cause
N/A
N/A
Standard cause value carried in

the response message
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure
Transaction ID
(PTI)
N/A
N/A

procedure ends.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure Information-Delete Bearer

Parameter
Range
Uni
t
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

to use a web service
through the MS. This
parameter distinguishes
service procedures for the
same subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure NO.
[1,2^31-1)
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Message
Organizer
SSGN
N/A

message recorded in the
CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
N/A
Logical board No. of the

device that processes the
CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Slot
Issue 03 (2015-07-30)
N/A

1925
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported
Solution
Version
CPU
N/A
N/A
Logical CPU No. of the

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Group
N/A
N/A
SPU group No. of the

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Instance
N/A
N/A
SPU instance No. of the

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

subscriber's serving
network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CI
N/A
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SAC
N/A
N/A

MCC, MNC, LAC, and
SAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAC
N/A
N/A

MCC, MNC, LAC, and
RAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
TAC
N/A
N/A

MCC, MNC, and TAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
ECI
N/A
N/A
ECGI information,
including MCC, MNC, and
ECI
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
LAC
N/A
N/A

MCC, MNC, and LAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1926
Nastar
Parameter
Range
Uni
t
Description
Supported
Solution
Version
EPS Bearer ID
N/A
N/A
ID of all bearers (including

the default bearer) for the
PDN connection
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
UE Time Zone
N/A
N/A
Time zone information of

the UE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Protocol Cause
N/A
N/A
Standard cause value

carried in the response
message
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure Information-Release Access Bearers

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31
-1)
N/A

procedures for the same
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure NO.
[1,2^31
-1)
N/A

for a subscriber
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Message
Organizer
SSGN
N/A

recorded in the CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME
GGSN
SGW
PGW
SGW
+PGW
Issue 03 (2015-07-30)

1927
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Slot
N/A
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CPU
N/A
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Group
N/A
N/A

processes the CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Instance
N/A
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Network
N/A
N/A

serving network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
EPS Bearer ID
N/A
N/A

connection
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Protocol Cause
N/A
N/A

response message
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1928
Nastar
Procedure Information-Modify Bearer Command/Delete Bearer Command

Parameter
Range
Uni
t
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

same subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure NO.
[1,2^31-1)
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Message
Organizer
SSGN
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CPU
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Group
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Instance
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1929
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported
Solution
Version
EPS Bearer ID
N/A
N/A

PDN connection
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS PCI
N/A
N/A
PCI in the Bearer QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS PL
N/A
N/A
PL in the Bearer QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS PVI
N/A
N/A
PVI in the Bearer QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS QCI
N/A
N/A
QCI in the Bearer QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS
MBRU
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS
MBRD
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS
GBRU
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS
GBRD
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
UE Time Zone
N/A
N/A

the UE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1930
Nastar
Parameter
Range
Uni
t
Description
Supported
Solution
Version
Protocol Cause
N/A
N/A

message
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure Information-Bearer Resource Command

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

procedure for a
subscriber to use a web
service through the MS.
This parameter
distinguishes between
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure No.
[1,2^31-1)
N/A
Unique No. of each

service procedure in the
whole procedure for a
subscriber
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Message
Organizer
SSGN
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CPU
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1931
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SPU Group
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Instance
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CI
N/A
N/A
CGI information,
including MCC, MNC,
LAC, and CI
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SAC
N/A
N/A
SAI information,
including MCC, MNC,
LAC, and SAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAC
N/A
N/A
RAI information,
including MCC, MNC,
LAC, and RAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
TAC
N/A
N/A
TAI information,
including MCC, MNC,
and TAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
ECI
N/A
N/A
ECGI information,
including MCC, MNC,
and ECI
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
LAC
N/A
N/A
LAI information,
including MCC, MNC,
and LAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Peer IPV4
Address for
Signaling
N/A
N/A
IPv4 address for

plane of the CN NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1932
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Peer IPV4
Address for
Data
N/A
N/A
IPv4 address for

configuring the user
plane of the CN NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Local IPV4
Address for
Signaling
N/A
N/A
IPv4 address for

plane of the NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Local IPV4
Address for
Data
N/A
N/A
IPv4 address for

plane of the NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Peer IPV6
Address for
Signaling
N/A
N/A
IPv6 address for

plane of the CN NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Peer IPV6
Address for
Data
N/A
N/A
IPv6 address for

plane of the CN NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Local IPV6
Address for
Signaling
N/A
N/A
IPv6 address for

plane of the NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Local IPV6
Address for
Data
N/A
N/A
IPv6 address for

plane of the NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Linked EPS
Bearer ID
N/A
N/A
ID of the default bearer.

This parameter can also
be used to identify the
PDN connection.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
EPS Bearer ID
N/A
N/A
ID of all bearers
(including the default
bearer) for the PDN
connection
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1933
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Procedure
Transaction ID
(PTI)
N/A
N/A
ID dynamically allocated
by the UE used for
modifying and
resources requested by
the UE. The PTI is
released when the
modification or
deactivation procedure
ends.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS QCI
N/A
N/A
QCI in the Flow QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS
MBRU
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS
MBRD
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS
GBRU
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS
GBRD
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Protocol Cause
N/A
N/A

message
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

1934
Nastar
Procedure Information-Create Indirect Data Forwarding

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

procedure for a
This parameter
subscriber.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure NO.
[1,2^31-1)
N/A
Unique No. of each

subscriber
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Message
Organizer
SSGN
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1935
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Serving
Network
N/A
N/A
MCC and MNC of the

network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV4
Address for
Signaling
N/A
N/A
IPv4 address for

plane of the CN NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV4
Address for
Data
N/A
N/A
IPv4 address for

plane of the CN NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Signaling
N/A
N/A
IPv4 address for

plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Data
N/A
N/A
IPv4 address for

plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Signaling
N/A
N/A
IPv6 address for

plane of the CN NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Data
N/A
N/A
IPv6 address for

plane of the CN NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Signaling
N/A
N/A
IPv6 address for

plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1936
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Local IPV6
Address for
Data
N/A
N/A
IPv6 address for

plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
EPS Bearer ID
N/A
N/A
ID of all bearers
bearer) for the PDN
connection
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Protocol Cause
N/A
N/A

message
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure Information-Delete Indirect Data Forwarding

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

procedure for a subscriber to
use a web service through the
MS. This parameter
distinguishes between the
multiple web service
subscriber.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure NO.
[1,2^31-1)
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Message
Organizer
SSGN
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)

1937
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Slot
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
SPU group No. of the device

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
EPS Bearer ID
N/A
N/A

PDN connection
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Protocol Cause
N/A
N/A
Standard cause value carried

in the response message
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

1938
Nastar
Procedure Information-Traffic
Parameter
Range
Unit
Description
Supported
Solution
Version
UL Total
Volume
[1,2^31-1)
Type
Uplink traffic volume

recorded in the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
DL Total
Volume
[1,2^31-1)
Type
Downlink traffic volume

recorded in the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Total Volume
[1,2^31-1)
Type
Total traffic volume

recorded in the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
First URL
N/A
N/A
First 20 bytes of the first

URL that the subscriber
visits during a service
procedure
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS Side Port of
First URL
N/A
N/A
TCP/UDP port No. (on the

UE side) of the first URL
that the subscriber visits
during a service procedure
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Network Side
Port of First
URL
N/A
N/A

network side) of the first
procedure
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer Duration
N/A
Bearer online duration.
PS 13.0 or
later
NOTE
When the duration is less than
1s, 1s is used.
Issue 03 (2015-07-30)
Bearer TEIDU
N/A
N/A
Bearer TEIDU information.
PS 13.0 or
later
MS IP V4
N/A
N/A

subscriber's MS
PS 13.0 or
later

1939
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MS IP V6
N/A
N/A

subscriber's MS
PS 13.0 or
later
Procedure-Authentication access
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A
Access Point
Name for real
used
PS 12.0/PS
12.1/PS 13.0
RAT Type
UTRAN 1
N/A
access type
when the
context is
activated
PS 12.0/PS
12.1/PS 13.0
N/A
the Time Zone

for this NE
PS 12.0/PS
12.1/PS 13.0
GERAN 2
WLAN 3
GAN 4
HSPA
Evolution 5
EUTRAN 6
FF
NE Time Zone
Issue 03 (2015-07-30)
N/A

1940
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Anonymous
Switch
No scramble 0
N/A
Whether
personal
information
anonymized
PS 12.0/PS
12.1/PS 13.0
private cause
0-4294967295
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
Delay time
0-65535
ms
Delay time from

request message
to response
message.
PS 12.0/PS
12.1/PS 13.0
User-NameReq
N/A
N/A
user-name from
access-request
message
PS 12.0/PS
12.1/PS 13.0
Framed-IPAddress-Req
N/A
N/A
indicates the
identifying IP
Address of the
NAS which is
requesting
authentication
of the user, and
is unique to the
NAS within the
scope of the
RADIUS server
PS 12.0/PS
12.1/PS 13.0
Framed-IPv6Prefix-Req
N/A
N/A
The attribute
Framed-IPv6Prefix in
Access-Request
message
PS 12.0/PS
12.1/PS 13.0
FramedInterface-IdReq
N/A
N/A
The attribute
FramedInterface-Id in
Access-Request
message
PS 12.0/PS
12.1/PS 13.0
Scramble 1

1941
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
NAS-IPAddress
N/A
N/A
indicates the
identifying IP
Address of the
NAS which is
requesting
authentication
of the user, and
is unique to the
NAS within the
scope of the
RADIUS server
PS 12.0/PS
12.1/PS 13.0
EventTimestamp
1-4294967295
N/A
The timestamp
of this message
being sent out.
PS 12.0/PS
12.1/PS 13.0
Charging-Id
1-4294967295
N/A
This Attribute
specifies a
unique ID for
GPRS charging
for the user
PS 12.0/PS
12.1/PS 13.0
SessionTimeout
30-4294967295
Second
This Attribute
sets the
maximum
number of
seconds of
service to be
provided to the
user before
termination of
the session or
prompt
PS 12.0/PS
12.1/PS 13.0
Idle-Timeout
30-4294967295
Second
This Attribute
sets the
maximum
number of
consecutive
seconds of idle
connection
allowed to the
user before
termination of
the session or
prompt
PS 12.0/PS
12.1/PS 13.0

1942
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Framed-Pool
N/A
N/A
This Attribute
contains the
name of an
assigned
address pool
that is used to
assign an
address for the
user
PS 12.0/PS
12.1/PS 13.0
HW-PrimaryDNS-Server
N/A
N/A
This Attribute
indicates the IP
address of the
primary DNS
Server
PS 12.0/PS
12.1/PS 13.0
HWSecondaryDNS-Server
N/A
N/A
This Attribute
indicates the IP
address of the
secondary DNS
Server
PS 12.0/PS
12.1/PS 13.0
HW-SESSIONFLOW-OUT
1000-42949672
95
Biye
This Attribute
HW-SESSIONFLOW-OUT is
from the
response
message
PS 12.0/PS
12.1/PS 13.0
HW-ChargeRule-BaseName
N/A
N/A
HW-ChargingRule-BaseName will be
used as a pointer
into a list of
charging-rules
PS 12.0/PS
12.1/PS 13.0

1943
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
HW-SessionCharging-Type
prepaid: 0
N/A
This attribute
defines the
charging type
for the user
session.
PS 12.0/PS
12.1/PS 13.0
post-paid with
credit control: 2
prepaid with
credit control: 3
The Value field

contains the
charging
profile.
HLR: 4
wallet specific:
5
wallet specific
without credit
control: 6
0 = prepaid
1 = post-paid
2 = post-paid
with credit
control
hot billing: 7
FF
3 = prepaid with
credit card
4 = HLR
5 = wallet
specific
6 = wallet
specific w
Issue 03 (2015-07-30)
HW-OCS-ID1
0-65535
N/A
This attribute
defines the
primary OCS
server.
PS 12.0/PS
12.1/PS 13.0
HW-OCS-ID2
0-65535
N/A
This attribute
defines the
primary OCS
server.
PS 12.0/PS
12.1/PS 13.0
HW-QOS-ID
0-255
N/A
The attribute
defines the QoS
information to
be applied for
the PDP
context.
PS 12.0/PS
12.1/PS 13.0
User-Name-Rsp
N/A
N/A
user-name from
response
message
PS 12.0/PS
12.1/PS 13.0

1944
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Framed-IPAddress-Rsp
N/A
N/A
Framed-IPAddress from
response
message,the real
user IP
PS 12.0/PS
12.1/PS 13.0
Framed-IPv6Prefix-Rsp
N/A
N/A
Framed-IPv6Prefix from
response
message
PS 12.0/PS
12.1/PS 13.0
FramedInterface-IdRsp
N/A
N/A
FramedInterface-Id
from response
message
PS 12.0/PS
12.1/PS 13.0
AAA-IPADDR
N/A
N/A
the IP adress of
AAA server
which receive
the request
message
PS 12.0/PS
12.1/PS 13.0
AAA-PORT
1-65535
N/A
the port of AAA

server which
receive the
request message
PS 12.0/PS
12.1/PS 13.0
Framed-Route
[0,200]
Byte
Subscriber route
segment in a
response
message
PS 12.0/PS
12.1/PS 13.0
Procedure-Radius accounting
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0

1945
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Slot
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
0~0xffffffff
byte
This attribute
indicates how
many octets
have been
received from
the port over the
course of this
service being
provided
PS 12.0/PS
12.1/PS 13.0
RAT Type
0~0xffffffff
byte
This attribute
indicates how
many octets
have been sent
to the port in the
course of
delivering this
service
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
This attribute is
a unique
Accounting ID
to make it easy
to match start
and stop records
in a log file.
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
0~0xffffffff
Second
This attribute
indicates how
many seconds
the user has
received service
PS 12.0/PS
12.1/PS 13.0

1946
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
private cause
0~0xffffffff
packet
This attribute
indicates how
many packets
have been
received from
the port over the
course of this
service being
provided to a
Framed User
PS 12.0/PS
12.1/PS 13.0
Delay time
0~0xffffffff
packet
This attribute
indicates how
many packets
have been sent
to the port in the
course of
delivering this
service to a
Framed User
PS 12.0/PS
12.1/PS 13.0
User-Name
1~18
N/A
This attribute
indicates how
the session was
terminated
PS 12.0/PS
12.1/PS 13.0
NAS-IPAddress
N/A
N/A
This attribute is
a unique
Accounting ID
to make it easy
to link together
multiple related
sessions in a log
file.
PS 12.0/PS
12.1/PS 13.0
Framed-IPAddress
0~0xffffffff
Number
This attribute
gives the count
of links which
are known to
have been in a
given multilink
session at the
time the
accounting
record is
generated.
PS 12.0/PS
12.1/PS 13.0

1947
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Framed-IPv6Prefix
0~0xffffffff
N/A
This attribute
indicates how
many times the
Acct-InputOctets counter
has wrapped
around 2^32
over the course
of this service
being provided
PS 12.0/PS
12.1/PS 13.0
FramedInterface-Id
0~0xffffffff
N/A
This attribute
indicates how
many times the
Acct-OutputOctets counter
has wrapped
around 2^32 in
the course of
delivering this
service
PS 12.0/PS
12.1/PS 13.0
Acct-StatusType
0~0xffffffff
Second
The EventTimestamp
SHOULD be
included in the
request and
contains the
time when the
request was
sent.
PS 12.0/PS
12.1/PS 13.0
Acct-DelayTime
0~0xffffffff
N/A
charging id
PS 12.0/PS
12.1/PS 13.0
Acct-InputOctets
0~0xff
N/A
prepaid
indicator,filled
with the low
byte of CC
PS 12.0/PS
12.1/PS 13.0
Acct-OutputOctets
N/A
N/A
The IP address
of AAA
accounting
server
PS 12.0/PS
12.1/PS 13.0
Acct-Session-Id
0~65535
N/A
The Port of
AAA
accounting
server
PS 12.0/PS
12.1/PS 13.0

1948
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Acct-SessionTime
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Acct-InputPackets
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
Acct-OutputPackets
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
AcctTerminateCause
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
Acct-MultiSession-Id
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
Acct-LinkCount
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
Acct-InputGigawords
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
Acct-OutputGigawords
N/A
N/A
Access Point
Name for real
used
PS 12.0/PS
12.1/PS 13.0
EventTimestamp
UTRAN 1
N/A
access type
when the
context is
activated
PS 12.0/PS
12.1/PS 13.0
GERAN 2
WLAN 3
GAN 4
HSPA
Evolution 5
EUTRAN 6
FF
Charging-Id
N/A
N/A
the Time Zone

for this NE
PS 12.0/PS
12.1/PS 13.0
Prepaid-Ind
No scramble 0
N/A
Whether
personal
information
anonymized
PS 12.0/PS
12.1/PS 13.0
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
Scramble 1
AAA-IPADDR
Issue 03 (2015-07-30)
0~4294967295

1949
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
AAA-PORT
65535
ms
Delay time from

request message
to response
message.
PS 12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
User name for

disconnect
message
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
Indicates the
identifying IP
Address of the
NAS which is
requesting
authentication
of the user, and
is unique to the
NAS within the
scope of the
RADIUS server
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
the IP adress for

subscriber
surfing
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A
Identifying the
NAS
originating the
Access-Request
PS 12.0/PS
12.1/PS 13.0
Procedure-disconnect
Issue 03 (2015-07-30)

1950
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
CPU
N/A
N/A
This attribute is
a unique
Accounting ID
to make it easy
to match start
and stop records
in a log file. The
start and stop
records for a
given session
have the same
Acct-SessionId.
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
This attribute is
a unique
Accounting ID
to make it easy
to link together
multiple related
sessions in a log
file. Each
session linked
together would
have a unique
Acct-Session-Id
but the same
PS 12.0/PS
12.1/PS 13.0

1951
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SPU Instance
0: Carrying 0
N/A
If the value of TI
is set to "1", then
all IP-CAN
bearers that
share the same
user session
with the IPCAN bearer
identified by the
Acct-Session-Id
shall be torn
down.
PS 12.0/PS
12.1/PS 13.0
1: Carrying 1
255: No
carrying
If the value of TI
is "0", or if TI is
missing, only
the IP-CAN
bearer identified
by the AcctSession-Id shall
be torn down. If
the AcctSesssion-Id
identifies the
default bearer,
the P-GW shall
tear down all the
IP-CAN bearers
that share the
same user
session
identified by the
Acct-Session-Id
Issue 03 (2015-07-30)
Access Point
Name (APN)
N/A
N/A
the IP adress of
AAA server
which send the
disconnect
message
PS 12.0/PS
12.1/PS 13.0
RAT Type
1-65535
N/A
the port of AAA

server which
send the
disconnect
message
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0

1952
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Anonymous
Switch
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Delay time
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
User-Name
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
NAS-IPAddress
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
Framed-IPAddress
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
NAS-Identifier
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
Acct-Session-Id
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
3GPPTeardown
Indicator
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0
AAA-IPADDR
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
AAA-PORT
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Procedure-Credit-Control Messages (Gy)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
Reserved
Information
PS 12.0/PS
12.1/PS 13.0

1953
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Procedure NO.
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
The origin-host
carried in CCR
messages
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A
The originrealm carried in

CCR messages
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
The destinationhost carried in

CCR messages
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
The destinationrealm carried in

CCR messages
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
The origin-host
carried in CCA
messages
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A

CCA messages
PS 12.0/PS
12.1/PS 13.0
RAT Type
N/A
The AuthApplication-Id
MUST be set to
the value 4,
indicating the
Diameter creditcontrol
application.
PS 12.0/PS
12.1/PS 13.0

1954
Nastar
Procedure-Re-Auth Messages (Gy)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
NE Time Zone
1~4
N/A
The CCRequest-Type is
of type
Enumerated and
contains the
reason for
sending the
credit-control
request
message. It
MUST be
present in all
Credit-ControlRequest
messages.
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
0~0xffffffff
N/A
The CCRequestNumber
identifies this
request within
one session.
PS 12.0/PS
12.1/PS 13.0
private cause
1000~5999
N/A
The ResultCode indicates

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
Delay time
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0

1955
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Reserved Info
0~0xffffffff
Second
The EventTimestamp
SHOULD be
included in the
request and
contains the
time when the
request was
sent.
PS 12.0/PS
12.1/PS 13.0
Session-Id
0~1
N/A
The CCSessionFailover
contains
information as
to whether
moving the
credit-control
message stream
to a backup
server during an
ongoing creditcontrol session
is supported.
PS 12.0/PS
12.1/PS 13.0
Origin-HostCCR
0~2
N/A
The creditcontrol client

uses this AVP to
decide what to
do if sending
credit-control
messages to the
credit-control
server has been,
for instance,
temporarily
prevented due to
a network
problem.
PS 12.0/PS
12.1/PS 13.0

1956
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Origin-RealmCCR
1~8
N/A
The
TerminationCause is used to
indicate the
reason why a
session was
terminated on
the access
device.
PS 12.0/PS
12.1/PS 13.0
DestinationHost-CCR
N/A
N/A
MultipleServices-CreditControl AVP is
of type Grouped
and contains the
AVPs related to
the independent
credit-control of
multiple
services feature.
PS 12.0/PS
12.1/PS 13.0
DestinationRealm-CCR
1000~5999
N/A

whether a
MSCC was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
Origin-HostCCA
0~0xfffffffe
N/A
The RatingGroup AVP

contains the
identifier of a
rating group
PS 12.0/PS
12.1/PS 13.0
Origin-RealmCCA
0~0xfffffffe
N/A
The ServiceIdentifier
contains the
identifier of a
service.
PS 12.0/PS
12.1/PS 13.0

1957
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
AuthApplication-Id
0~0xffffffff
Second
The TariffTime-Change is
sent from the
server to the
client and
includes the
time in seconds
since January 1,
1900, 00:00
UTC, when the
tariff of the
service will be
changed.
PS 12.0/PS
12.1/PS 13.0
CC-RequestType
0~0xffffffff
Second
The TimeQuotaThreshold
contains a
threshold value
in seconds.
PS 12.0/PS
12.1/PS 13.0
CC-RequestNumber
0~0xffffffff
byte
The VolumeQuotaThreshold
contains a
threshold value
in octets.
PS 12.0/PS
12.1/PS 13.0
Result-Code
0~0xffffffff
time
The UnitQuotaThreshold
contains a
threshold value
in service
specific units.
PS 12.0/PS
12.1/PS 13.0
ExperimentalResult-Code
0~0xffffffff
Second
The QuotaHolding-Time
AVP contains
the quota
holding time in
seconds. The
client shall start
the quota
holding timer
when quota
consumption
ceases.
PS 12.0/PS
12.1/PS 13.0

1958
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
EventTimestamp
0~0xffffffff
Second
The QuotaConsumptionTime contains

an idle traffic
threshold time
in seconds.
PS 12.0/PS
12.1/PS 13.0
CC-SessionFailover
0~0xffffffff
Second
The ValidityTime is sent

from the creditcontrol server to
the creditcontrol client.
This AVP
contains the
validity time of
the granted
service units.
PS 12.0/PS
12.1/PS 13.0
Credit-ControlFailureHandling
0~4
N/A
This EnvelopeReporting is
used in the CCA
(INITIAL) to
indicate whether
the client shall
report the start
and end of each
time envelope,
in those cases in
which quota is
consumed in
envelopes
PS 12.0/PS
12.1/PS 13.0
TerminationCause
0~1
N/A
The TimePS 12.0/PS

Quota-Type
12.1/PS 13.0
AVP is used to
indicate which
time quota
consumption
mechanism
shall be used for
the associated
Rating Group.

1959
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MultipleServicesCredit-Control
0~0xffffffff
Second
The Base-TimeInterval
contains the
length of the
base time
interval, for
controlling the
consumption of
time quota, in
seconds.
PS 12.0/PS
12.1/PS 13.0
Result-Code
0~2
N/A
The Final-UnitAction indicates

to the creditcontrol client
the action to be
taken when the
user's account
cannot cover the
service cost.
PS 12.0/PS
12.1/PS 13.0
Procedure-Abort-Session Messages (Gy)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rating-Group
N/A
N/A
The RedirectServer-Address
defines the
address of the
redirect server
(e.g., HTTP
redirect server)
with which the
end user is to be
connected when
the account
cannot cover the
service cost.
PS 12.0/PS
12.1/PS 13.0

1960
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
ServiceIdentifier
N/A
N/A
The RequestedService-Unit
contains the
amount of
requested units
specified by the
Diameter creditcontrol client.
PS 12.0/PS
12.1/PS 13.0
Tariff-TimeChange
0~0xffffffff
Second
The CC-Time
AVP indicates
the length of the
requested,
granted, or used
time in seconds.
PS 12.0/PS
12.1/PS 13.0
Time-QuotaThreshold
0~0xfffffffffffff
fff
byte
The CC-TotalOctets contains

the total number
of requested,
granted, or used
octets
regardless of the
direction (sent
or received).
PS 12.0/PS
12.1/PS 13.0
Volume-QuotaThreshold
0~0xfffffffffffff
fff
byte
The CCServiceSpecific-Units
specifies the
number of
service-specific
units (e.g.,
number of
events, points)
given in a
selected service.
PS 12.0/PS
12.1/PS 13.0

1961
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Unit-QuotaThreshold
N/A
N/A
GrantedService-Unit
contains the
amount of units
that the
Diameter creditcontrol client
can provide to
the end user
until the service
must be released
or the new
Credit-ControlRequest must be
sent.
PS 12.0/PS
12.1/PS 13.0
Quota-HoldingTime
0~0xffffffff
Second
sent from the
server to the
client and
includes the
time in seconds
since January 1,
1900, 00:00
UTC, when the
tariff of the
service will be
changed.
PS 12.0/PS
12.1/PS 13.0
QuotaConsumptionTime
0~0xffffffff
Second
The CC-Time
AVP indicates
the length of the
requested,
granted, or used
time in seconds.
PS 12.0/PS
12.1/PS 13.0
Validity-Time
0~0xfffffffffffff
fff
byte

the total number
of requested,
granted, or used
octets
regardless of the
direction (sent
or received).
PS 12.0/PS
12.1/PS 13.0

1962
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
EnvelopeReporting
0~0xfffffffffffff
fff
byte
specifies the
number of
service-specific
units (e.g.,
number of
events, points)
given in a
selected service.
PS 12.0/PS
12.1/PS 13.0
Time-QuotaType
N/A
N/A
The UsedService-Unit
contains the
amount of used
units.
PS 12.0/PS
12.1/PS 13.0
Base-TimeInterval
0~2
N/A
The TariffChange-Usage
defines whether
units are used
before or after a
tariff change, or
whether the
units straddled a
tariff change
during the
reporting
period.
PS 12.0/PS
12.1/PS 13.0
Final-UnitAction
0~0xffffffff
Second
The CC-Time
AVP indicates
the length of the
requested,
granted, or used
time in seconds.
PS 12.0/PS
12.1/PS 13.0
RedirectServer-Address
0~0xfffffffffffff
fff
byte

the total number
of requested,
granted, or used
octets
regardless of the
direction (sent
or received).
PS 12.0/PS
12.1/PS 13.0

1963
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RequestedService-Unit
0~0xfffffffffffff
fff
byte
specifies the
number of
service-specific
units (e.g.,
number of
events, points)
given in a
selected service.
PS 12.0/PS
12.1/PS 13.0
CC-Time
0~8
N/A
The ReportingReason
specifies the
reason for usage
reporting for
one or more
types of quota
for a particular
category.
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
CC-ServiceSpecific-Units
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
GrantedService-Unit
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Tariff-TimeChange
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
Procedure-Credit-Control Messages (Gx)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
CC-Time
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0

1964
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
* Used-ServiceUnit
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
Tariff-ChangeUsage
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
CC-Time
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
ReportingReason
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
16777238
N/A
Gx application
ID
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
protocol version
PS 12.0/PS
12.1/PS 13.0

1965
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Slot
0~1
N/A
R970 dictionary
flag.
0:R940,1:R970
PS 12.0/PS
12.1/PS 13.0
CPU
1~3
N/A
of type
Enumerated and
contains the
reason for
sending the
credit-control
request
message. It
MUST be
present in all
messages.
PS 12.0/PS
12.1/PS 13.0
SPU Group
0~0xffffffff
N/A
The CCRequestNumber
identifies this
request within
one session.
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
CCR
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
RAT Type
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
DestinationHost name
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
N/A
DestinationRealm name
PS 12.0/PS
12.1/PS 13.0

1966
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
private cause
1~8
N/A
The
indicate the
reason why a
session was
terminated on
the access
device.
PS 12.0/PS
12.1/PS 13.0
Delay time
0~1
N/A
The NetworkRequestSupport
indicates the UE
and network
support of the
network
requested bearer
control mode.
PS 12.0/PS
12.1/PS 13.0
Session-Id
0~6
N/A
The IP-CANType indicates

the type of
Connectivity
Access Network
in which the
user is
connected. The
IP-CAN-Type
AVP shall
always be
present during
the IP-CAN
session
establishment.
During an IPCAN session
modification,
this AVP shall
be present when
there has been a
change in the IPCAN type and
the PCRF
requested to be
informed of this
event.
PS 12.0/PS
12.1/PS 13.0

1967
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
AuthApplication-Id
0~1
N/A
session online
flag
PS 12.0/PS
12.1/PS 13.0
Protocol version
0~1
N/A
session offline
flag
PS 12.0/PS
12.1/PS 13.0
R970
N/A
N/A
The UserLocation-Info is
used to report
the details of
where the UE is
currently
located (e.g.
SAI or CGI).
PS 12.0/PS
12.1/PS 13.0
CC-RequestType
N/A
N/A
The BearerIdentifier
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0

1968
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
CC-RequestNumber
0~1
N/A
The QoSNegotiation is
applicable for
3GPP-GPRS
only. The value
of it indicates
for a single PCC
rule request if
the PCRF is
allowed to
negotiate the
QoS by
supplying in the
answer to this
request an
authorized QoS
different from
the requested
QoS.
PS 12.0/PS
12.1/PS 13.0
CCR
0~1
N/A
The QoSUpgrade is
applicable for
3GPP-GPRS
only. The value
of it indicates
whether the
SGSN supports
that the GGSN
upgrades the
QoS in a Create
PDP context
response or
Update PDP
context
response.
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
charging
characteristic
PS 12.0/PS
12.1/PS 13.0

1969
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Origin-Realm
N/A
N/A
When sent from

the PCRF to the
PCEF the
Event-Trigger
indicates an
event that shall
cause a rerequest of PCC
rules. When sent
from the PCEF
to the PCRF the
Event-Trigger
indicates that
the
corresponding
event has
occurred at the
gateway.
Whenever one
of these events
occurs, the
PCEF shall send
the related AVP
that has changed
together with
the event trigger
indication.
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0

1970
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
DestinationRealm
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
applicable bitrates for the IPCAN bearer or
service flow.
PS 12.0/PS
12.1/PS 13.0
TerminationCause
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
NetworkRequestSupport
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
IP-CAN-Type
N/A
bps
it indicates the
guaranteed bitrate in bits per
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0
Online
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0

1971
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Offline
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

1972
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
3GPP-UserLocation-Info
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
the DefaultEPS-BearerQoS AVP, the
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

1973
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
BearerIdentifier
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
Default-EPSBearer-QoS
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
QoSNegotiation
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
across all nonGBR bearers
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

1974
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
QoS-Upgrade
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
3GPPChargingCharacteristics
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
*Event-Trigger
N/A
N/A
The DefaultEPS-BearerQoS is
applicable for
3GPP-EPS
only. It defines
the QoS
information for
the EPS default
bearer.
PS 12.0/PS
12.1/PS 13.0

1975
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
QoSInformation
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

1976
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MaxRequestedBandwidth-UL
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

1977
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MaxRequestedBandwidth-DL
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
GuaranteedBitrate-UL
N/A
N/A
It contains the
usage
monitoring
control
information.
PS 12.0/PS
12.1/PS 13.0
GuaranteedBitrate-DL
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

1978
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Priority-Level
N/A
It is used by the
PCRF to
indicate that
accumulated
usage is to be
reported by the
PCEF
regardless of
whether a usage
threshold is
reached
PS 12.0/PS
12.1/PS 13.0
Pre-emptionCapability
N/A
It is used by the
PCRF to
indicate
whether usage
monitoring shall
be disabled for
certain
Monitoring Key
PS 12.0/PS
12.1/PS 13.0
Pre-emptionVulnerability
N/A
byte
It contains the
usage reporting
thresholds.
PS 12.0/PS
12.1/PS 13.0
APNAggregateMax-BitrateUL
0~0xffffffff
byte
value of the
usage reporting
thresholds
PS 12.0/PS
12.1/PS 13.0
APNAggregateMax-BitrateDL
N/A
byte
It contains the
amount of used
units measured
from the point
when the service
became active
or, if interim
interrogations
are used during
the session,
from the point
when the
previous
measurement
ended.
PS 12.0/PS
12.1/PS 13.0

1979
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
BearerIdentifier
0~0xffffffff
byte
the amount of
used units
measured
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It report
charging rule
name or
charging rule
base name is
installed,
modified or
removed (for
dynamic PCC
rules)
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
0~2
N/A
It describes the
status of one or a
group of PCC
Rules
PS 12.0/PS
12.1/PS 13.0
Priority-Level
1~2000
N/A
The RuleFailure-Code
indicates the
reason that the
PCC rules
cannot be
successfully
installed/
activated or
enforced.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
report, the
termination
action
instructed by the
OCS, to PCRF
when
corresponding
PCC rules is out
of credit.
PS 12.0/PS
12.1/PS 13.0
0~2
N/A
It indicates the
action to be
taken when the
user's account
cannot cover the
service cost.
PS 12.0/PS
12.1/PS 13.0

1980
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
*UsageMonitoringInformation
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
MonitoringKey
N/A
N/A
it indicates the
name of a predefined group of
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
UsageMonitoringReport
N/A
N/A
CCA
PS 12.0/PS
12.1/PS 13.0
UsageMonitoringSupport
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
GrantedService-Unit
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
Used-ServiceUnit
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Report
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
PCC-RuleStatus
N/A
Second
RevalidationTime
PS 12.0/PS
12.1/PS 13.0

1981
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rule-FailureCode
0~1
N/A
session online
flag
PS 12.0/PS
12.1/PS 13.0
Final-UnitIndication
0~1
N/A
session offline
flag
PS 12.0/PS
12.1/PS 13.0
Final-UnitAction
N/A
N/A
It can only be
sent from PCRF
to PCEF,
indicating the
PCRF selected
bearer control
mode.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
N/A
When sent from

the PCRF to the
PCEF the
Event-Trigger
indicates an
event that shall
rules. When sent
from the PCEF
to the PCRF the
Event-Trigger
indicates that
the
corresponding
event has
occurred at the
gateway.
Whenever one
of these events
occurs, the
PCEF shall send
the related AVP
that has changed
together with
the event trigger
indication.
PS 12.0/PS
12.1/PS 13.0

1982
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
*ChargingRule-BaseName
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0
CCA
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
bps
it indicates the
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0

1983
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
DestinationRealm
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0
Result-Code
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

1984
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
RevalidationTime
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
Online
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

1985
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Offline
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
Bearer-ControlMode
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
*Event-Trigger
N/A
N/A
applicable for
3GPP-EPS
only. It defines
the QoS
information for
the EPS default
bearer.
PS 12.0/PS
12.1/PS 13.0

1986
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
*QoSInformation
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

1987
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

1988
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It contains the
usage
monitoring
control
information.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

1989
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Priority-Level
N/A
It is used by the
PCRF to
indicate that
accumulated
usage is to be
reported by the
PCEF
regardless of
whether a usage
threshold is
reached
PS 12.0/PS
12.1/PS 13.0
N/A
It is used by the
PCRF to
indicate
whether usage
monitoring shall
be disabled for
certain
Monitoring Key
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
usage reporting
thresholds.
PS 12.0/PS
12.1/PS 13.0
0~0xffffffff
byte
value of the
usage reporting
thresholds
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
amount of used
units measured
from the point
when the service
became active
or, if interim
interrogations
are used during
the session,
from the point
when the
previous
measurement
ended.
PS 12.0/PS
12.1/PS 13.0

1990
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
BearerIdentifier
0~0xffffffff
byte
the amount of
used units
measured
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
deactivate or
remove PCC
rules from an IP
CAN session.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
Priority-Level
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
activate, install
or modify PCC
rules as
instructed from
the PCRF to the
PCEF
PS 12.0/PS
12.1/PS 13.0
N/A
Second
This value
indicates the
NTP time at
which the PCC
rule has to be
enforced.
PS 12.0/PS
12.1/PS 13.0
N/A
Second
This value
indicates the
NTP time at
which the PCEF
has to stop
enforcing the
PCC rule.
PS 12.0/PS
12.1/PS 13.0
MonitoringKey
N/A
N/A
it defines the
PCC rule for a
service flow
sent by the
PCRF to the
PCEF.
PS 12.0/PS
12.1/PS 13.0

1991
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it contains the
identifier of a
service.
PS 12.0/PS
12.1/PS 13.0
GrantedService-Unit
N/A
N/A
It contains the
identifier of a
rating group
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
0~3
N/A
It describes
whether the IP
flow(s) are
enabled or
disabled.
PS 12.0/PS
12.1/PS 13.0
Used-ServiceUnit
0~1
N/A
it defines on
what level the
PCEF reports
the usage for the
related PCC
rule.
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
Online
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Remove
N/A
N/A
Offline
PS 12.0/PS
12.1/PS 13.0
0~2
N/A
it defines what
parameters shall
be metered for
offline
charging.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
N/A
Precedence
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Install
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

1992
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RuleActivationTime
N/A
N/A
determines the
traffic that
belongs to the
service flow.
PS 12.0/PS
12.1/PS 13.0
RuleDeactivationTime
N/A
N/A
determines the
traffic that
belongs to the
service flow.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Definition
N/A
N/A
it indicates the
identity of the
packet filter.
The packet filter
identifier is
assigned by the
PCRF and
within the scope
of the PCRF is
unique per UE.
PS 12.0/PS
12.1/PS 13.0
Charging-RuleName
0~3
N/A
It indicates the
direction/
directions that a
filter is
applicable,
downlink only,
uplink only or
both down- and
uplink
(bidirectional).
PS 12.0/PS
12.1/PS 13.0
ServiceIdentifier
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0

1993
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rating-Group
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
Flow-Status
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
ReportingLevel
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
Online
N/A
bps
it indicates the
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0
Offline
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0

1994
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MeteringMethod
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

1995
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Precedence
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

1996
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MonitoringKey
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
* FlowInformation
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

1997
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
FlowDescription
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
Packet-FilterIdentifier
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
Flow-Direction
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
QoSInformation
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0

1998
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
Priority-Level
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
BearerIdentifier
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0

1999
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
The origin-host
carried in RAR
messages
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A

RAR messages
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A

RAR messages
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

RAR messages
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
MUST be set to
the value 4,
indicating the
application.
PS 12.0/PS
12.1/PS 13.0
SPU Instance
0~0xfffffffe
N/A
The RatingGroup AVP

contains the
identifier of a
rating group
PS 12.0/PS
12.1/PS 13.0

2000
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Point
Name (APN)
0~0xfffffffe
N/A
contains the
identifier of a
service.
PS 12.0/PS
12.1/PS 13.0
RAT Type
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Delay time
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
Session-Id
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
AuthApplication-Id
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
Rating-Group
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0
ServiceIdentifier
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0

2001
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Result-Code
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
The origin-host
carried in ASR
messages
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A

ASR messages
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A

ASR messages
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

ASR messages
PS 12.0/PS
12.1/PS 13.0

2002
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SPU Group
N/A
MUST be set to
the value 4,
indicating the
application.
PS 12.0/PS
12.1/PS 13.0
SPU Instance
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
RAT Type
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
Delay time
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
Session-Id
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0

2003
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
AuthApplication-Id
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
Result-Code
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Procedure-Re-Auth Messages (Gx)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
16777238
N/A
Gx application
ID
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
protocol version
PS 12.0/PS
12.1/PS 13.0
Slot
0~1
N/A
R970 dictionary
flag.
0:R940,1:R970
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
RAR
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A
PS 12.0/PS
12.1/PS 13.0

2004
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RAT Type
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
1~8
N/A
The
indicate the
reason why a
session was
terminated on
the access
device.
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
Second
RevalidationTime
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
When sent from

the PCRF to the
PCEF the
Event-Trigger
indicates an
event that shall
rules. When sent
from the PCEF
to the PCRF the
Event-Trigger
indicates that
the
corresponding
event has
occurred at the
gateway.
Whenever one
of these events
occurs, the
PCEF shall send
the related AVP
that has changed
together with
the event trigger
indication.
PS 12.0/PS
12.1/PS 13.0

2005
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Delay time
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0
Session-Id
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
AuthApplication-Id
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
Protocol version
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
R970
N/A
bps
it indicates the
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0

2006
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RAR
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0
Origin-Host
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

2007
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Origin-Realm
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

2008
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
DestinationHost
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

2009
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SessionRelease-Cause
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
RevalidationTime
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
*Event-Trigger
N/A
N/A
applicable for
3GPP-EPS
only. It defines
the QoS
information for
the EPS default
bearer.
PS 12.0/PS
12.1/PS 13.0

2010
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
*QoSInformation
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

2011
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

2012
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It contains the
usage
monitoring
control
information.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

2013
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Priority-Level
N/A
It is used by the
PCRF to
indicate that
accumulated
usage is to be
reported by the
PCEF
regardless of
whether a usage
threshold is
reached
PS 12.0/PS
12.1/PS 13.0
N/A
It is used by the
PCRF to
indicate
whether usage
monitoring shall
be disabled for
certain
Monitoring Key
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
usage reporting
thresholds.
PS 12.0/PS
12.1/PS 13.0
0~0xffffffff
byte
value of the
usage reporting
thresholds
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
amount of used
units measured
from the point
when the service
became active
or, if interim
interrogations
are used during
the session,
from the point
when the
previous
measurement
ended.
PS 12.0/PS
12.1/PS 13.0

2014
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
BearerIdentifier
0~0xffffffff
byte
the amount of
used units
measured
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
deactivate or
remove PCC
rules from an IP
CAN session.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
Priority-Level
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
activate, install
or modify PCC
rules as
instructed from
the PCRF to the
PCEF
PS 12.0/PS
12.1/PS 13.0
N/A
Second
This value
indicates the
NTP time at
which the PCC
rule has to be
enforced.
PS 12.0/PS
12.1/PS 13.0
N/A
Second
This value
indicates the
NTP time at
which the PCEF
has to stop
enforcing the
PCC rule.
PS 12.0/PS
12.1/PS 13.0
MonitoringKey
N/A
N/A
it defines the
PCC rule for a
service flow
sent by the
PCRF to the
PCEF.
PS 12.0/PS
12.1/PS 13.0

2015
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it contains the
identifier of a
service.
PS 12.0/PS
12.1/PS 13.0
GrantedService-Unit
N/A
N/A
It contains the
identifier of a
rating group
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
0~3
N/A
It describes
whether the IP
flow(s) are
enabled or
disabled.
PS 12.0/PS
12.1/PS 13.0
Used-ServiceUnit
0~1
N/A
it defines on
what level the
PCEF reports
the usage for the
related PCC
rule.
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
0~1
N/A
Online
PS 12.0/PS
12.1/PS 13.0
0~1
N/A
Offline
PS 12.0/PS
12.1/PS 13.0
0~2
N/A
it defines what
parameters shall
be metered for
offline
charging.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
N/A
Precedence
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

2016
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RuleActivationTime
N/A
N/A
determines the
traffic that
belongs to the
service flow.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
determines the
traffic that
belongs to the
service flow.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it indicates the
identity of the
packet filter.
The packet filter
identifier is
assigned by the
PCRF and
within the scope
of the PCRF is
unique per UE.
PS 12.0/PS
12.1/PS 13.0
Charging-RuleName
0~3
N/A
It indicates the
direction/
directions that a
filter is
applicable,
downlink only,
uplink only or
both down- and
uplink
(bidirectional).
PS 12.0/PS
12.1/PS 13.0
ServiceIdentifier
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0

2017
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rating-Group
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
Flow-Status
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
ReportingLevel
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
Online
N/A
bps
it indicates the
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0
Offline
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0

2018
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MeteringMethod
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

2019
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Precedence
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

2020
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MonitoringKey
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
*FlowInformation
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

2021
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
FlowDescription
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
Flow-Direction
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
QoSInformation
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
N/A
N/A
RAA
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0

2022
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
Priority-Level
N/A
N/A
RAA resultcode
PS 12.0/PS
12.1/PS 13.0
N/A
Second
RevalidationTime
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It report
charging rule
name or
charging rule
base name is
installed,
modified or
removed (for
dynamic PCC
rules)
PS 12.0/PS
12.1/PS 13.0
0~2
N/A
It describes the
status of one or a
group of PCC
Rules
PS 12.0/PS
12.1/PS 13.0
1~2000
N/A
indicates the
reason that the
PCC rules
cannot be
successfully
installed/
activated or
enforced.
PS 12.0/PS
12.1/PS 13.0
BearerIdentifier
N/A
N/A
it is used to
report, the
termination
action
instructed by the
OCS, to PCRF
when
corresponding
PCC rules is out
of credit.
PS 12.0/PS
12.1/PS 13.0

2023
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~2
N/A
It indicates the
action to be
taken when the
user's account
cannot cover the
service cost.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
RAA
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
Result-Code
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
RevalidationTime
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
PCC-RuleStatus
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
Rule-FailureCode
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
Final-UnitAction
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0

2024
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
*ChargingRule-Name
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Procedure-Abort-Session Message(Gx)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
16777238
N/A
Gx application
ID
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
protocol version
PS 12.0/PS
12.1/PS 13.0
Slot
0~1
N/A
R970 dictionary
flag.
0:R940,1:R970
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
ASR
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0

2025
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Point
Name (APN)
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
RAT Type
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
ASA
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
Delay time
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
Session-Id
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
AuthApplication-Id
16777238
N/A
Gx application
ID
PS 12.0/PS
12.1/PS 13.0
Protocol version
N/A
N/A
protocol version
PS 12.0/PS
12.1/PS 13.0
R970
0~1
N/A
R970 dictionary
flag.
0:R940,1:R970
PS 12.0/PS
12.1/PS 13.0

2026
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
ASR
N/A
N/A
ASR
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
DestinationHosT
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
ASA
N/A
N/A
ASA
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
Result-Code
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0

(Combined Analysis)
This section describes the parameters for querying combined complaint analysis support data
results. You can refer to the description when querying combined complaint analysis support
data results.
Issue 03 (2015-07-30)

2027
Nastar
Summary
Parameter
Range
Unit
Description
RAT
Serial
Number
[1,2^31-1)
N/A

Overview Table. Serial number is
a keyword of a call record. It is an
internal identification in the
a call record.
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
Combined
N/A
N/A

The Nastar supports the
combination of inter-BSC/RNC/
PS Core CHRs. If a yellow icon is
displayed in this column, the CHR
is combined.
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
USN
+UGW
Associated
N/A
N/A
Whether a CHR is associated.
PS Core
Status
N/A
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
Blank

record is abnormal.
Issue 03 (2015-07-30)
Abnormal
Cause
N/A
Network
N/A
N/A

Remark: For the access counters
such as TP, Ec/No, RSCP, if the
active set contains multiple cells
during access, only the counters
for the first cell in this active set
are analyzed.
N/A

GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
2028
Nastar
Parameter
Range
Unit
Description
RAT
Access Net
Type
N/A
N/A

following:
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
GPRS
UMTS(W/TD)
LTE
Access
Type
Intra-RAT RRC
Access
N/A
Incoming HO/
Intra-RAT
Incoming HO

CONNECTION SETUP
message:
UMTS/
LTE

in)
Incoming HO/
UTRAN
Incoming HO

migration request.
Incoming HO/
GERAN
Incoming HO

reloc in)
Incoming HO

DRD)
DRD)
CSFB on
Access
Yes
N/A
No
UMTS/
LTE
N/A
Issue 03 (2015-07-30)

2029
Nastar
Parameter
Range
Unit
Description
RAT
Access
Cause
Originating
Conversational
Call
N/A
Cause of RRC setup.
GSM/
UMTS
Originating
Streaming Call

cause."
Originating
Interactive Call
Originating
Background Call
Originating
Subscribed traffic
Call
Terminating
Conversational
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
Terminating
High Priority
Signaling
Terminating
Low Priority
Signaling
MBMS reception
Issue 03 (2015-07-30)

2030
Nastar
Parameter
Range
Unit
Description
RAT
MBMS ptp RB
request
Start Time
N/A
N/A
Signaling start time for a call.
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
Access Cell
1 to 64 characters
N/A

terminal sends the Channel
Request message.
GSM/
UMTS/
TDSCDMA/
LTE
End Time
N/A
N/A
Signaling end time for a call.
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
Release
Cell
1 to 64 characters
N/A

terminal receives the Channel
Release message.
GSM/
UMTS/
TDSCDMA/
LTE
User
ID:User
Name
N/A
N/A

GSM/
UMTS/
TDSCDMA/
LTE
IMSI
N/A
User Name, which is created by

the user when creating the task.
N/A

IMEI-TAC
Issue 03 (2015-07-30)
00000000-99999
999
N/A

UE.

GSM/
UMTS/
TDSCDMA/
LTE
GSM/
UMTS/
TDSCDMA/
LTE
2031
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
RAT
Terminal
Model
N/A
N/A
Model of a UE.
GSM/
UMTS/
TDSCDMA/
LTE
Peer
MSISDN
N/A
N/A

peer subscriber.
GSM
Duration
[0,+)
Secon
d
Duration of a call, including

service duration and signaling
duration.
time.
GSM/
UMTS/
TDSCDMA/
LTE
N/A
Statistics on the types of CS

service requested by a UE.
GSM/
UMTS
Secon
d
Statistics on the duration of CS

services used by a UE.
GSM/
UMTS

UE.
CS
Requested
Service
Type
AMR
CS Service
Duration
[0,+)
VP

2032
Nastar
Parameter
Range
Unit
Description
RAT
Call Setup
Result/RRC
Setup
Failure
Cause
Following are
criteria indicating
a proper call
setup:
N/A

mobile-originated call. The result
indicates a proper call setup or an
abnormal call setup.
GSM/
UMTS
1. Normal: The
called subscriber
receives the
Connect ACK
message and
proper call
communication is
established
between the
calling and called
subscribers.
The call setup result is displayed

in the following format: Call
Abnormal Call Release/SubCause of Abnormal Call Release.
(You can obtain the preceding
three parameters in the Call
Release Information window.)
2. The calling
subscriber
receives the
Disconnect
message and
termination of the
call is triggered
by the peer
subscriber.
3. Connection is
released due to an
outgoing interBSC 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.
Issue 03 (2015-07-30)

2033
Nastar
Parameter
Range
Unit
Description
RAT
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.
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.
Issue 03 (2015-07-30)

2034
Nastar
Parameter
Range
Unit
Description
RAT
Call Setup
Result
Following are
criteria indicating
a proper call
release:
N/A

indicates a proper call release or
an abnormal call release.
GSM
1. Normal: The
subscriber
receives the
Disconnect
message and
starts 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 interRAT 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 03 (2015-07-30)

2035
Nastar
Parameter
Range
Unit
Description
RAT
PS
Requested
Service
Type
PS R99
N/A
Statistics on the types of PS

UMTS
HSDPA
HSUPA
HSPA
PS RAB
Duration
[0,+)
Secon
d
Statistics on the duration of PS

UMTS
IU Release
Cause
N/A
N/A
Cause of signaling release of a

call.
UMTS
The value of this parameter is

carried in the IU RELEASE
REQUEST message. For details,
see 3GPP 25.413 - 9.1.6.
NE Type
N/A
N/A

following:
PS Core
SGSN
MME
NE Name
N/A
N/A
Name of a CN NE.
PS Core
Procedure
Type
N/A
N/A
PS Core
RAC/TAC
N/A

Signaling Procedures in the
appendix.
N/A

initiated.
PS Core

initiated.
Cell
N/A
N/A

accesses.
PS Core
APN
N/A
N/A

the SM procedure.
PS Core

MM procedure.
Procedure
Delay Time
0-65535
ms
PS Core
The parameters for the LTE-FDD/TDD signaling plane data and PS Core user plane combined
complaint analysis based on UGW are similar to those for the PS Core user plane complaint
Issue 03 (2015-07-30)

2036
Nastar
analysis based on UGW.For details,see Reference for Complaint Analysis Support

Parameters (PS Core) - User Plane.
4.10.10 Appendix: Exception Cause Classification / Key Signaling

The section describes the exception cause classification in the summary table. The section also
lists the key signaling when analyzing the all signaling on PS domain.
Appendix: Exception Cause Classification / Key Signaling (GSM)

Exception Cause Classification

Doma
in
Servic
e Type
RANNET
Networ
k
Evalu
ation
Type
Access
ibility
Evalua
tion
Abnormal Type
Access Failure
(Intra-System)
Um Interface Quality
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Abnormal TA on
Access
N/A
N/A
Abnormal RACH
Level on Access
N/A
N/A
Abnormal Release
(Intra-system)
Handover Failure
N/A
Problem
High TA
Access Failure
(Inter-System)
Retain
ability
Evalua
tion
Issue 03 (2015-07-30)
Abnormal Sub-type

2037
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Weak
TCH
Uplink/
Downlink
Level
TCH
Uplink/
Downlink
Interferen
ce
Poor
uplink
quality of
the TCH
Weak
TCH
Uplink
Level
Weak
TCH
Downlink
Level
TCH
Uplink
Interferen
ce
TCH
Downlink
Interferen
ce
Poor TCH
Uplink
Quality
Poor TCH
Downlink
Quality
Sharp
Decrease
on TCH
Uplink
Level
Issue 03 (2015-07-30)

2038
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Sharp
Decrease
on TCH
Downlink
Level
Other Um
Interface
Quality
Problems
Retain
ability
Evalua
tion
Abnormal Release
(Inter-system)
Transmission Fault
N/A
CN fault
N/A
Peer Fault
N/A
Other Causes
N/A
Handover Failure
N/A
Problem
High TA
Weak
TCH
Uplink/
Downlink
Level
TCH
Uplink/
Downlink
Interferen
ce
Poor
uplink
quality of
the TCH
Weak
TCH
Uplink
Level
Weak
TCH
Downlink
Level
Issue 03 (2015-07-30)

2039
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
TCH
Uplink
Interferen
ce
TCH
Downlink
Interferen
ce
Poor TCH
Uplink
Quality
Poor TCH
Downlink
Quality
Sharp
Decrease
on TCH
Uplink
Level
Sharp
Decrease
on TCH
Downlink
Level
Other Um
Interface
Quality
Problems
Mobilit
y
Evalua
tion
Issue 03 (2015-07-30)
Hard Handover
Failure
Transmission Fault
N/A
CN fault
N/A
Peer Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A

2040
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Inter-System
Outgoing Handover
Failure (Normal
Release)
Inter-System
Outgoing Handover
Failure (Abnormal
Release)
Inter-System
Incoming Handover
Failure
RANCS
Issue 03 (2015-07-30)
Call
Access
ibility
Evalua
tion
Call Setup Failure
Abnormal Sub-type
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A

2041
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Release
Before Call
Completion
Retain
ability
Evalua
tion
Abnormal Call
Release
Abnormal Sub-type
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Handover Failure
N/A
Problem
High TA
Weak
TCH
Uplink/
Downlink
Level
TCH
Uplink/
Downlink
Interferen
ce
Poor
uplink
quality of
the TCH
Weak
TCH
Uplink
Level
Weak
TCH
Downlink
Level
TCH
Uplink
Interferen
ce
Issue 03 (2015-07-30)

2042
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
TCH
Downlink
Interferen
ce
Poor TCH
Uplink
Quality
Poor TCH
Downlink
Quality
Sharp
Decrease
on TCH
Uplink
Level
Sharp
Decrease
on TCH
Downlink
Level
Other Um
Interface
Quality
Problems
Service
Quality
- Delay
Evalua
tion
Issue 03 (2015-07-30)
Abnormal Delay
Transmission Fault
N/A
CN fault
N/A
Peer Fault
N/A
Other Causes
N/A
Overlong Access Delay

(MOC)
N/A

(MTC)
N/A
Overlong Call
Completion Delay
(Alerting)(MOC)
N/A
Overlong Call
Completion Delay
(Alerting)(MTC)
N/A

2043
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Service
Quality
Quality
Evalua
tion
SMS
RANPS
Issue 03 (2015-07-30)
PS
Abnormal Type
Service Quality
Problem
Abnormal Sub-type
Overlong Call
Completion Delay
(Connect Ack)(MOC)
N/A
Overlong Call
Completion Delay
(Connect Ack)(MTC)
N/A
Short Call(MOC)
N/A
Short Call(MTC)
N/A
Poor Quality of Um
Interface
N/A
Bad Downlink HQI
N/A
Bad Uplink HQI
N/A
Bad Uplink VQI
N/A
Bad Downlink VQI
N/A
Uplink One-Way Audio
N/A
Downlink One-Way
Audio
N/A
Mute Call
N/A
Downlink Crosstalk
N/A
Uplink Crosstalk
N/A
Downlink Noise
N/A
Uplink Noise
N/A
Access
ibility
Evalua
tion
Setup Failure(Caller) N/A
N/A
Setup Failure
(Callee)
N/A
N/A
Access
ibility
Evalua
tion
Setup Failure
Attach Failure
Attach
Reject
Failure

Attach
Failure No
Responses
2044
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
PDP Active Failure
PDP
Active
Reject
Failure
PDP
Active
Failure No
Responses
AUC Failure
AUC
Reject
Failure
AUC
Failure No
Responses
Retain
ability
Evalua
tion
Delay
Evalua
tion
Service Interrupt
Abnormal Service
Interaction Delay
No Service Interaction
Responses
N/A
Last Service
Interruptions Due to
Routing Area Update
N/A
Abnormal Interruption
on Cell Reselection
N/A
Service Interruptions
Due to FLUSH LL
N/A
Due to TBF Abnormal
N/A
Service Interaction
Timeout
Service
Interaction
Timeout
on interval
between
Uplink
and
Downlink
PDUs
Service
Interaction
Timeout
on sending
PDUs at
Downlink
Issue 03 (2015-07-30)

2045
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Service
Interaction
Timeout
on
receiving
PDUs at
Uplink
Rate
Evalua
tion
Low Download
Speed
Overlong Average
Duration on Service
Interaction Response
N/A
Low Download Speed
Downlink
Multi-Slot
NonSatisfactio
n
Downlink
Reuse to
High
Um
Quality
NonSatisfactio
n of
Downlink
Average
SingleSlot
Throughp
ut
Poor
Transmiss
ion
Quality of
Downlink
Average
SingleSlot
Throughp
ut
Issue 03 (2015-07-30)

2046
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Transmiss
ion
Resource
NonSatisfactio
n of
Downlink
Average
SingleSlot
Throughp
ut
Downlink
TCP Outof-Order
Downlink
NU Outof-Order
Insufficien
t Terminal
Capability
Abnormal
Subscriber
Registrati
on
Other
Low Upload Speed
Low Upload Speed
Uplink
Multi-Slot
NonSatisfactio
n
Uplink
Reuse to
High
Issue 03 (2015-07-30)

2047
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Um
Quality
NonSatisfactio
n of
Uplink
Average
SingleSlot
Throughp
ut
Poor
Transmiss
ion
Quality of
Uplink
Average
SingleSlot
Throughp
ut
Transmiss
ion
Resource
NonSatisfactio
n of
Uplink
Average
SingleSlot
Throughp
ut
Uplink
TCP Outof-Order
Uplink
NU Outof-Order
Insufficien
t Terminal
Capability
Issue 03 (2015-07-30)

2048
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Abnormal
Subscriber
Registrati
on
Other
TBF
Abnor
mal
TBF Abnormal
TBF Abnormal
Um
Quality
Cause
Um
Resource
Cause
Cell
Reselectio
n Cause
Voice
Cause
Equipmen
t Cause
Terminal
Cause
Other
Nonexecpti
on
Non-exception
N/A
N/A
Key Signaling (PS Domain)

Interface
Key Signaling
RA CAPABILITY UPDATE
RADIO STATUS
Gb
DOWNLOAD BSS PFC

CREATE BSS PFC ACK
CREATE BSS PFC NACK
MODIFY BSS PFC
Issue 03 (2015-07-30)

2049
Nastar
Interface
Key Signaling
DELETE BSS PFC ACK
PS HANDOVER REQUIRED
PS HANDOVER REQUEST ACK
PS HANDOVER REQUEST NACK
PS HANDOVER COMPLETE
PS HANDOVER CANCEL
SUSPEND
RESUME
FLUSH-LL-ACK
LLC DISCARDED
RA CAPABILITY UPDATE ACK
CREATE BSS PFC
MODIFY BSS PFC ACK
DELETE BSS PFC
PS HANDOVER REQUEST
PS HANDOVER REQUIRED ACK
PS HANDOVER REQUIRED NACK
SUSPEND-ACK
SUSPEND-NACK
RESUME-ACK
RESUME-NACK
FLUSH-LL
ATTACH REQUEST
ATTACH ACCEPT
ATTACH REJECT
ATTACH COMPLETE
DETACH REQUEST
DETACH ACCEPT
ROUTING AREA UPDATE REQUEST
Issue 03 (2015-07-30)

2050
Nastar
Interface
Key Signaling
ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE REJECT
ROUTING AREA UPDATE COMPLETE
AUTHENTICATION AND CIPHERING REJECT
AUTHENTICATION AND CIPHERING REQUEST
AUTHENTICATION AND CIPHERING RESPONSE
AUTHENTICATION AND CIPHERING FAILURE
IDENTITY REQUEST
IDENTITY RESPONSE
PTMSI REALLOCATION COMMAND
PTMSI REALLOCATION COMPLETE
GMM STATUS
GMM INFORMATION
ACTIVATE PDP CONTEXT REQUEST
ACTIVATE-PDP-CONTEXT-REQUEST
ACTIVATE PDP CONTEXT ACCEPT
ACTIVATE PDP CONTEXT REJECT
ACTIVATE SECONDARY PDP CONTEXT REQUEST
ACTIVATE SECONDARY PDP CONTEXT ACCEPT
ACTIVATE SECONDARY PDP CONTEXT REJECT
REQUEST PDP CONTEXT ACTIVATION
REQUEST PDP CONTEXT ACTIVATION REJECT
MODIFY PDP CONTEXT REQUEST(MS To NET)
MODIFY PDP CONTEXT ACCEPT(MS To NET)
MODIFY PDP CONTEXT REQUEST(NET To MS)
MODIFY PDP CONTEXT ACCEPT(NET To MS)
MODIFY PDP CONTEXT REJECT
DEACTIVATE PDP CONTEXT REQUEST
DEACTIVATE PDP CONTEXT ACCEPT
Issue 03 (2015-07-30)

2051
Nastar
Interface
Key Signaling
SM-STATUS
Channel Request
Packet Channel Req
Packet Control Acknowledgement (NB) Packet Control Ack
(AB)
Packet Cell Change Failure
Packet Resource Request
Packet SI Status
Additional MS Radio Access Capabilities
Packet Cell Change Notification
Packet Downlink Ack/Nack
EGPRS Packet Downlink Ack/Nack
EGPRS Packet Downlink Ack/Nack Type 2
Immediate Assignment
Immediate Assignment Reject
Um
Packet Downlink Assignment

Packet Polling Request
Packet Power Control/Timing Advance
Packet Timeslot Reconfigure
Packet TBF Release
Packet Uplink Assignment
Packet Cell Change Continue
Packet Neighbor Cell Data
Packet Serving Cell Data
Packet Cell Change Order
Packet Measurement Order
Packet Physical Information
PS Handover Command
Packet Uplink Ack/Nack
Uplink RLC Data header
Issue 03 (2015-07-30)

2052
Nastar
Interface
Key Signaling
Downlink RLC Data header
Appendix: Exception Cause Classification / Enumeration Values of Failure Cause

(UMTS)
The section describes the exception cause classification in the summary table, and the
enumeration values of the failure cause.

Domain
RAN-Net
Servi
ce
Type
Netwo
rk
Abnormal CauseClassification
Abnormal Cause-Sub-classification
Non-exception
N/A
Setup Failure
RRC Setup Failure

RRC Setup Failure (Service-CS)
RRC Setup Failure (Service-PS)
Access Coverage
Problem
Abnormal TP on access
Abnormal CPICH Ec/N0 on access
Abnormal CPICH RSCP on access
Abnormal Release
RRC Abnormal Release
Delay Problem
Overlong RRC Setup Delay (Non-service)

Overlong RRC Setup Delay (Service)
Overlong Soft Handover Delay
Overlong Hard Handover Delay
Overlong Channel Handover Delay
Overlong Incoming Handover Delay
Overlong Outgoing Handover Delay
Overlong Inter-RAT Incoming Handover
Delay
Overlong Inter-RAT Outgoing Handover
Delay
.Overlong U2L redirection delay threshold
HO Problem
Issue 03 (2015-07-30)
Soft Handover Failure

2053
Nastar
Domain
Servi
ce
Type
Hard Handover Failure
Cell Update Failure
Channel Handover Failure
Migration Failure
Inter-RAT Handover Failure
PDP Activate Failure
RAN-CS
AMR
Non-exception
N/A
Setup Failure
CS RAB Setup Failure

Abnormal Release Before Call Completion
Abnormal Release
CS RAB Abnormal Release
Service Quality Problem
Uplink One-Way-Audio
Downlink One-Way-Audio
Noise
SQI Abnormal
Radio of Bad SQIs Higher
Delay Problem
Overlong RRC Setup Delay

Overlong RAB Connection Delay (MTC)
Overlong RAB Connection Delay (MOC)
Overlong RAB Connection Delay
(Alerting)(MTC)
Overlong RAB Connection Delay (Connect
Ack)(MTC)
(Alerting)(MOC)
Ack)(MOC)
ShortCall Problem
RAB Duration Shorter

Short Calls (MTC)
Short Calls (MOC)
VP
Issue 03 (2015-07-30)
Non-exception
N/A

2054
Nastar
Domain
Servi
ce
Type
Setup Failure

Abnormal Release
Delay Problem

(Alerting)(MTC)
Ack)(MTC)
(Alerting)(MOC)
Ack)(MOC)
ShortCall Problem

Short Calls (MTC)
Short Calls (MOC)
SMS
Non-exception
N/A
Setup Failure
SMS Failed Requests (MTC)

SMS Failed Requests (MOC)
RAN-PS
Other
Other
N/A
PS
R99
Non-exception
N/A
Setup Failure
PS RAB Setup Failure
Abnormal Release
PS RAB Abnormal Release
QoS Problem
Overlow Average Downlink Throughput
HSDP
A
HSUP
A
Overlow Average Uplink Throughput
HSPA
Average Uplink Transmission Rate Slow

Delay Problem

Issue 03 (2015-07-30)

2055
Nastar
Domain
RANMulti
Servi
ce
Type
Other
Other
N/A
Multi
Servic
e
Non-exception
N/A
Setup Failure
Multi-RAB Setup Failure
Multi
Servic
e(CS
Includ
ed)
Abnormal Release
Multi-RAB Abnormal Release
Multi
Servic
e(PS
Only)
Enumeration Values of Failure Cause
Issue 03 (2015-07-30)
ErrType
ErrReason
Radio Resource Congestion
UL Power Congestion
DL Power Congestion
Code Congestion
HSUPA User Num Congestion
HSDPA User Num Congestion
HSUPA_HSDPA User Num Congestion
UL_DL Power Congestion
UL CE Congestion
DL CE Congestion
UL_DL CE Congestion
UL Iub Band Congestion
DL Iub Band Congestion
UL_DL Iub Band Congestion
Overload Control
Preempted User Due To Congestion
Iub Interface Failure
Iub AAL2/AL Establishment Failure

2056
Nastar
Issue 03 (2015-07-30)
ErrType
ErrReason
Iur Interface Failure
Iur AAL2/AL Establishment Failure
Uu Interface Failure
SRB Reset
TRB Reset
Iu Relocation Failure
Iu Relocation Preparation Failure Timer

Relocation Preparation Expiry
Iu Relocation Execution Timer Expiry
Timer Expired
Iu Relocation Preparation Iu Release

Command
Iu Relocation Preparation Failure Unknown

Target RNC
Iu Relocation Preparation Failure Cancel
Iu Relocation Preparation Failure Cipher

Unsupport
Iu Relocation Preparation Failure Target

Not Allow

System Unsupport
Iub Cell not Available
Iub Control Plane Process Resources

Overload
Iub Hardware Failure
Iub OAM Intervention Failure
Iub not Enough User Plane Process

Resources Failure
Radio Link Permanent Failure
Iur RL Reconfiguration Commit Timeout
Iur Radio Link Reconfiguration Cancel
Iur RL Add/Setup Timeout
Iur Control Plane Process Resources

Overload
UE Reestablishment
Overlapped Cell Update

2057
Nastar
ErrType
ErrReason
Uu Configuration Unsupport
Uu Physical Channel Failure
Uu Simultaneous Configuration
Uu Compress Mode Runtime Tgpsi Error
Uu Protocol Error
Uu Cell Update Occur Error
Uu Invalid Configuration
Uu Configuration Incomplete
Uu Unsupport Measurement Error
Uu MBMS Session Failure
Uu MBMS Service Failure
Uu Inter-RAT HO Failure Configuration

Unaccept
Uu Inter-RAT HO Failure Physical CH

Failure
Uu Inter-RAT HO Failure Protocol Error
Uu Inter-RAT HO Failure Inter-RAT

Protocol Error
Uu Inter-RAT HO Failure Unspecified
Uu Inter-RAT Change Failure
Uu Inter-RAT Change Failure Protocol

Error
Uu Inter-RAT Change Failure Unspecified
Appendix: Exception Cause Classification / Key Signaling (LTE)

lists the key signaling.
Issue 03 (2015-07-30)

2058
Nastar

Service
Type
Evaluati
on Type
Net
Accessibil
ity
Evaluatio
n
Abnormal
CauseClassificati
on
Setup Failure
RRC Setup Failure (Resource Allocation Failure)

(Service)
RRC Setup Failure (UE No-answer) (Service)
(Non-service)
RRC Setup Failure (UE No-answer) (Nonservice)
RRC Re-setup Failure
Mobility
Evaluatio
n
HO Failure
Intra-RAT outgoing handover preparation failure

Intra-RAT outgoing handover execution failure
(with Data Transmission)
Inter-RAT outgoing handover preparation failure
Inter-RAT outgoing handover execution failure
Inter-RAT outgoing handover CSFB preparation
failure
Inter-RAT outgoing handover CSFB execution
failure
failure (with Data Transmission)
Inter-RAT outgoing handover SRVCC
preparation failure
Inter-RAT outgoing handover SRVCC execution
failure
Issue 03 (2015-07-30)

2059
Nastar
Service
Type
Evaluati
on Type
Abnormal
CauseClassificati
on

preparation failure (with Data Transmission)
Intra-RAT incoming handover preparation failure
Intra-RAT incoming handover execution failure
Inter-RAT incoming handover preparation failure
Inter-RAT incoming handover execution failure
Delay
Evaluatio
n
Delay
Problem
Overlong RRC setup delay (Service)

Overlong RRC setup delay (Non-service)
Overlong intra-RAT outgoing handover delay
Overlong inter-RAT outgoing handover delay
Overlong intra-RAT incoming handover delay
Overlong inter-RAT incoming handover delay
GBR
(QCI=2)
GBR
(QCI=3)
GBR
(QCI=4)
Non-GBR
(QCI=5)
Non-GBR
(QCI=6)
Non-GBR
(QCI=7)
Non-GBR
(QCI=8)
Non-GBR
(QCI=9)
Note: data
service
Accessibil
ity
Evaluatio
n
Setup Failure
E-RAB Setup Failure (QCI=N) Note: N indicates

the detailed QCI value.
Retainabil
ity
Evaluatio
n
E-RAB
Abnormal
Release
E-RAB abnormal release triggered by MME

(QCI=N) Note: N indicates the detailed QCI
value.
E-RAB abnormal release triggered by eNodeB
value.
E-RAB abnormal release triggered by outgoing
HO execution failure (QCI=N) Note: N indicates
E-RAB abnormal release triggered by MME (with
Data Transmission)(QCI=N) Note: N indicates
(with Data Transmission)(QCI=N) Note: N
indicates the detailed QCI value.
Issue 03 (2015-07-30)

2060
Nastar
Service
Type
Evaluati
on Type
Abnormal
CauseClassificati
on

HO execution failure (with Data Transmission)
value.
GBR
(QCI=1)
Note:
voice
service
Service
Evaluatio
n for
Delay
Delay
Problem
Long E-RAB Setup Delay (QCI=N) Note: N

Service
Evaluatio
n for Rate
Rate Problem
Accessibil
ity
Evaluatio
n
Setup Failure
E-RAB Setup Failure (QCI=1)
Retainabil
ity
Evaluatio
n
E-RAB
Abnormal
Release

(QCI=1)
Short E-RAB Duration (QCI=N) Note: N

Low Average Downlink Throughput (QCI=N)
Note: N indicates the detailed QCI value.
Low Average Uplink Throughput (QCI=N) Note:
N indicates the detailed QCI value.

(QCI=1)
HO execution failure (QCI=1)
Data Transmission)(QCI=1)
(with Data Transmission)(QCI=1)
(QCI=1)
Issue 03 (2015-07-30)
Service
Evaluatio
n for
Delay
Delay
Problem
Long E-RAB Setup Delay (QCI=1)
Service
Evaluatio
n for
Voice
Quality
Problem
Poor Downlink VQI
Short E-RAB Duration (QCI=1)

2061
Nastar
Service
Type
Evaluati
on Type
Abnormal
CauseClassificati
on
Voice
Quality
Service
Evaluatio
n for Rate
Poor Uplink VQI
Rate Problem
Low Average Downlink Throughput (QCI=1)

Low Average Uplink Throughput (QCI=1)
Key Signaling
Procedure
Key Event
RRC Setup or Release
RRC CONNECTION REESTABLISHMENT REQUEST

RRC CONNECTION REJECT
RRC CONNECTION SETUP COMPLETE
RRC CONNECTION RELEASE
E-RAB Setup or Release
E-RAB SETUP REQUEST

E-RAB SETUP RESPONSE
E-RAB RELEASE INDICATION
E-RAB RELEASE COMMAND
E-RAB MODIFY REQUEST
E-RAB MODIFY RESPONSE
E-RAB RELEASE RESPONSE
Context Setup or Release
INITIAL CONTEXT SETUP REQUEST

INITIAL CONTEXT SETUP RESPONSE
INITIAL CONTEXT SETUP FAILURE
UE CONTEXT RELEASE REQUEST
UE CONTEXT RELEASE COMMAND
UE CONTEXT MODIFICATION FAILURE
UE CONTEXT MODIFICATION RESPONSE
Issue 03 (2015-07-30)

2062
Nastar
Procedure
Key Event
UE CONTEXT MODIFICATION REQUEST
Handover
HANDOVER REQUIRED
HANDOVER REQUEST
HANDOVER COMMAND
HANDOVER FAILURE
HANDOVER CANCEL
HANDOVER NOTIFY
HANDOVER PREPARATION FAILURE
MOBILITY FROM EUTRA COMMAND
X2 HANDOVER REQUEST
X2 HANDOVER PREPARATION FAILURE
X2 HANDOVER CANCEL
PATH SWITCH REQUEST
PATH SWITCH REQUEST FAILURE
S1 HANDOVER REQUEST ACKNOWLEDGE
S1 PATH SWITCH REQUEST ACKNOWLEDGE
CELL TRAFFIC TRACE
X2 HANDOVER REQUEST ACKNOWLEDGE
X2 SN STATUS TRANSFER
Other
UE CAPABILITY INFORMATION
INITIAL UE MESSAGE
MEASUREMENT REPORT
UPLINK NAS TRANSPORT
NAS NON DELIVERY INDICATION
Appendix: Exception Cause Classification / Signaling Procedure / Procedure

Initiated Cause (PS Core)
lists the signaling procedure and the cause of procedure initiated.
l
Issue 03 (2015-07-30)
Exception Cause Classification (Data)

2063
Nastar
Exception Cause Classification (Voice-CSFB)
Exception Cause Classification (Voice-VoLTE)
Exception Cause Classification(Based on user plane data on UGW)
Signaling Procedure
Cause of Procedure Initiated

NOTE
For detailed description of the exception cause field, see PS Core Knowledge Base Management.

Procedure
Type
Abnormal
Type
Abnormal
Sub-type
Non-exception
Non-exception
N/A
Abnormal
Attach
Attach Failure
Abnormal
Paging
Paging Failure
Abnormal
PDP Act
PDP Act Failure
Abnormal
PDP Sec Act
PDP Sec Act Failure
Abnormal
PDN GW
Dedicated
Bearer Act
PDN GW Dedicated Bearer Act

Failure
Abnormal
RAU
Intra SGSN RAU Failure
Accessibility
Exception
SGSN(G)
Procedure
Detailed Abnormal Type
Attach Overlong Delay
Paging Overlong Delay
PDP Act Overlong Delay
PDP Sec Act Overlong Delay

Overlong Delay
Intra SGSN RAU Overlong Delay

Inter SGSN RAU Failure
Inter SGSN RAU Overlong Delay
Mobility
Exception
Issue 03 (2015-07-30)
RAU(others) Failure
Abnormal
Relocation
Relocation Failure
Abnormal
System
Change
System Change Failure
Relocation Overlong Delay
System Change Overlong Delay

2064
Nastar
Procedure
Type
Abnormal
Type
PDP
Modification
Exception
Retainability
Exception
Non-exception
SGSN(U)
Procedure
Accessibility
Exception
Mobility
Exception
Issue 03 (2015-07-30)
Abnormal
Sub-type
Abnormal
PDP Mod
PDP Mod Failure
Abnormal
PDN GW
Initiated
Bearer Mod
PDN GW Initiated Bearer Mod Failure
Abnormal
Detach
Detach Failure
Abnormal
PDP Deact
PDP Deact Failure
Abnormal
PDN GW
Initiated
Bearer Deact
PDN GW Initiated Bearer Deact

Failure
Non-exception
N/A
Abnormal
Attach
Attach Failure
Abnormal
Service Req
Service Req Failure
Abnormal
Paging
Paging Failure
Abnormal
PDP Act
PDP Act Failure
Abnormal
PDP Sec Act
PDP Sec Act Failure
Abnormal
RAB
Assignment
RAB Assignment Failure
Abnormal
PDN GW
Dedicated
Bearer Act

Failure
Abnormal
RAU
PDP Mod Overlong Delay
PDN GW Initiated Bearer Mod

Overlong Delay
Service Req Overlong Delay
RAB Assignment Overlong Delay

Overlong Delay

2065
Nastar
Procedure
Type
Abnormal
Type
Abnormal
Sub-type

RAU(others) Failure
Abnormal
Relocation
Relocation Failure
Abnormal
System
Change
Abnormal
PDP Mod
PDP Mod Failure
Abnormal
PDN GW
Initiated
Bearer Mod
Abnormal
Detach
Detach Failure
Abnormal Iu
Release
Iu Release Failure
Abnormal
RAB Release
RAB Release Failure
Abnormal
PDP Deact
PDP Deact Failure
Abnormal
PDN GW
Initiated
Bearer Deact

Failure
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Attach
Attach Failure
Abnormal
Service Req
Service Req Failure
Abnormal
Default Bearer
Act
Default Bearer Act Failure
PDP
Modification
Exception
Retainability
Exception
MME
Procedure
Issue 03 (2015-07-30)

Overlong Delay
Default Bearer Act Overlong Delay

2066
Nastar
Procedure
Type
Abnormal
Type
Retainability
Exception
Mobility
Exception
Abnormal
Sub-type
Abnormal
Paging
Paging Failure
Abnormal
Dedicated
Bearer Act
Dedicated Bearer Act Failure
Abnormal
PDN
Connectivity
PDN Connectivity Failure
Abnormal
Detach
Detach Failure
Abnormal S1
Release
S1 Release Failure
Abnormal
Bearer Deact
Abnormal Bearer Deact
Abnormal
PDN
Disconnection
PDN Disconnection Failure
Abnormal
TAU
Intra TAU Failure
Dedicated Bearer Act Overlong Delay
PDN Connectivity Overlong Delay
Intra TAU Overlong Delay

Inter TAU Failure
Inter TAU Overlong Delay
Abnormal
Handover
Intra E-UTRAN Handover Failure

Intra E-UTRAN Handover Overlong
Delay
Inter RAT Handover Failure
Inter RAT Handover Overlong Delay
Bearer
Modification
Exception
Issue 03 (2015-07-30)
Abnormal
Bearer Mod
Bearer Mod Failure
Abnormal
Bearer
Resource Mod
Abnormal Bearer Resource Mod
Abnormal
Bearer
Resource
Allocation
Abnormal Bearer Resource Allocation
Bearer Mod Overlong Delay
Bearer Resource Mod Overlong Delay
Bearer Resource Allocation Overlong

Delay

2067
Nastar
Procedure
Type
GGSN(G)
Procedure
Abnormal
Type
Abnormal
Sub-type
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Create PDP
Abnormal Create PDP
PDP
Modification
Exception
Abnormal
Update PDP
Abnormal Update PDP
Retainability
Exception
Abnormal
Delete PDP
Abnormal Delete PDP
Radius
Abnormal
Authentication
access
Abnormal Authentication access
Abnormal
Radius
Accounting
Abnormal Radius Accounting
Abnormal
Disconnect
Abnormal Disconnect
Abnormal
Credit-Control
Messages
Abnormal Credit-Control Messages
Abnormal ReAuth
Messages
Abnormal Re-Auth Messages
Abnormal
Abort-Session
Messages
Abnormal Abort-Session Messages
Abnormal
Credit-Control
Messages
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Message
Abnormal Abort-Session Message
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Create PDP
Abnormal Create PDP
Gy
Gx
GGSN(U)
Procedure
Issue 03 (2015-07-30)

2068
Nastar
Procedure
Type
Abnormal
Type
Abnormal
Update PDP
Abnormal Update PDP
Retainability
Exception
Abnormal
Delete PDP
Abnormal Delete PDP
Radius
Abnormal
Authentication
access
Abnormal
Radius
Accounting
Abnormal
Disconnect
Abnormal Disconnect
Abnormal
Credit-Control
Messages
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Messages
Abnormal
Credit-Control
Messages
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Message
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Create Session
Abnormal Create Session
Abnormal
Create Bearer
Abnormal Create Bearer
Gx
Issue 03 (2015-07-30)
PDP
Modification
Exception
Gy
SAE-GW
Procedure
Abnormal
Sub-type

2069
Nastar
Procedure
Type
Abnormal
Type
Bearer
Modification
Exception
Retainability
Exception
Radius
Issue 03 (2015-07-30)
Abnormal
Sub-type
Abnormal
Create Indirect
Data
Forwarding
Tunnel
Abnormal Create Indirect Data

Forwarding Tunnel
Abnormal
Modify Bearer
Abnormal Modify Bearer
Abnormal
Update Bearer
Abnormal Update Bearer
Abnormal
Modify Bearer
Command
Abnormal Modify Bearer Command
Abnormal
Bearer
Resource
Command
Abnormal Bearer Resource Command
Abnormal
Delete Session
Abnormal Delete Session
Abnormal
Delete Bearer
Abnormal Delete Bearer
Abnormal
Release
Access
Bearers
Abnormal Release Access Bearers
Abnormal
Delete Bearer
Command
Abnormal Delete Bearer Command
Abnormal
Delete Indirect
Data
Forwarding
Tunnel
Abnormal Delete Indirect Data

Forwarding Tunnel
Abnormal
Authentication
access
Abnormal
Radius
Accounting
Abnormal
Disconnect
Abnormal Disconnect

2070
Nastar
Procedure
Type
Abnormal
Type
Gy
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Messages
Abnormal
Credit-Control
Messages
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Message
N/A
N/A
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Create PDP
Abnormal Create PDP
Accessibility
Exception
Abnormal
Create Session
Abnormal
Create Bearer
Abnormal
Create Indirect
Data
Forwarding
Tunnel

Forwarding Tunnel
PDP
Modification
Exception
Abnormal
Update PDP
Abnormal Update PDP
Retainability
Exception
Abnormal
Delete PDP
Abnormal Delete PDP
Traffic
Other
Procedure
Issue 03 (2015-07-30)
Abnormal
Credit-Control
Messages
Gx
Traffic
Procedure
Abnormal
Sub-type

2071
Nastar
Procedure
Type
Abnormal
Type
Retainability
Exception
Bearer
Modification
Exception
Abnormal
Sub-type
Abnormal
Delete Session
Abnormal
Delete Bearer
Abnormal
Release
Access
Bearers
Abnormal
Delete Bearer
Command
Abnormal
Delete Indirect
Data
Forwarding
Tunnel

Forwarding Tunnel
Abnormal
Modify Bearer
Abnormal
Update Bearer
Abnormal
Modify Bearer
Command
Abnormal
Bearer
Resource
Command

Procedure
Type
MME
Procedure
Issue 03 (2015-07-30)
Abnormal
Type
Abnormal
Sub-type
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Attach
Combined Attach CS Failure
Abnormal
Paging
SGs CS Paging Failure
Combined Attach CS Overlong Delay
SGs CS Paging Overlong Delay

2072
Nastar
Procedure
Type
Abnormal
Type
Abnormal
Sub-type

SGs SMS Paging Failure
SGs SMS Paging Overlong Dela
S1 CS Paging Failure
S1 CS Paging Overlong Delay
S1 SMS Paging Failure
S1 SMS Paging Overlong Delay
Mobility
Exception
Abnormal
Service Req
Extended Service Req Failure
Abnormal
TAU
Intra Combined TAU Failure
Extended Service Req Overlong Delay
Intra Combined TAU Overlong Delay

Inter Combined TAU Failure
Inter Combined TAU Overlong Delay
Abnormal
Handover
CSFB PS Handover Failure

CSFB PS Handover Overlong Delay

Procedure Type
Abnormal Type
Abnormal Subtype
Detailed
Abnormal Type
MME Procedure
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal UE
requested PDN
connectivity
VoLTE PDN
Connectivity Failure
Abnormal Paging
VoLTE Paging
Failure
VoLTE PDN
Connectivity
Overlong Delay
VoLTE Paging
Overlong Delay
Abnormal Dedicated
Bearer Act
Issue 03 (2015-07-30)

VoLTE Dedicated
Bearer Act Failure
2073
Nastar
Procedure Type
Abnormal Type
Abnormal Subtype
Detailed
Abnormal Type
VoLTE Dedicated
Bearer Act Overlong
Delay
Abnormal Bearer
Mod
VoLTE Bearer Mod

Failure
VoLTE Bearer Mod
Overlong Delay
Mobility Exception
Abnormal Handover
VoLTE Intra EUTRAN Handover

Failure
Overlong Delay
SRVCC Failure
SRVCC Overlong
Delay
SAE-GW Procedure
Retainability
Exception
Call Drop
VoLTE Call Drop
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal VoLTE
Create Session
N/A
Abnormal VoLTE
Create Bearer
N/A
Abnormal VoLTE
Update Bearer
N/A

Service
Web
Browsin
g
Issue 03 (2015-07-30)
Assess
ment
Type
Demarcation
Type
Demarcation Sub-Type
Accessib
ility
Page Response
Failure
Server Returns Error Code

4**
Terminal Problem

5**
SP Problem

Demarcation
Result
2074
Nastar
Service
Assess
ment
Type
Demarcation
Type
Abnormal Page
Response Delay
Integrity
Issue 03 (2015-07-30)
Slow Page
Response
Demarcation
Result
Redirect Failure (Terminal

Problem)
Terminal Problem
Server Response Failure

(RAN Problem)
RAN problem/
Problem on NEs
below PS core
Server Abnormal Release
SP Problem
Server Response Timeout
Problem on NEs
above PS core
Others
Others
DNS Abnormal Delay
Problem on NEs
above PS core
Abnormal Delay Between

SYN and SYN ACK
Problem on NEs
above PS core

SYN ACK and ACK
RAN problem/
Problem on NEs
below PS core

ACK and GET/POST
RAN problem/
Problem on NEs
below PS core

GET/POST and Response
Problem on NEs
above PS core
Others
Others
Small Terminal Receiving

Window
Terminal Problem
Zero Terminal Receiving

Window
Terminal Problem
High Downstream Packet

Loss Rate
RAN problem/
Problem on NEs
below PS core
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core
High Upstream Packet Loss

Rate
Problem on NEs
above PS core
High Uplink
Retransmission Rate
RAN Problem

2075
Nastar
Service
Video
Streamin
g
Issue 03 (2015-07-30)
Assess
ment
Type
Accessib
ility
Demarcation
Type
Demarcation
Result
Low Upstream
Transmission Throughput
Problem on NEs
above PS core
Others
Others
Slow Page
Display
Low Success Rate of Page

Display Request
NA
Video Streaming
Start Failure

Window
Terminal Problem

Window
Terminal Problem

SYN and SYN ACK
Problem on NEs
above PS core

ACK and GET
RAN problem/
Problem on NEs
below PS core

SYN ACK and ACK
RAN problem/
Problem on NEs
below PS core
DNS Abnormal Delay
Problem on NEs
above PS core

GET and Response
Problem on NEs
above PS core
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core

Loss Rate
RAN problem/
Problem on NEs
below PS core

Rate
Problem on NEs
above PS core
Abnormal Request Delay

Between Clips in Starting
Period
RAN problem/
Problem on NEs
below PS core
High Code Rate
SP Problem
Low Upstream
Problem on NEs
above PS core

2076
Nastar
Service
Assess
ment
Type
Demarcation
Type
Abnormal Video
Streaming Start
Delay
Issue 03 (2015-07-30)
Demarcation
Result
Terminal Intentionally
Release
Terminal Problem

4**
Terminal Problem

5**
SP Problem
Problem on NEs
above PS core
Others
Others

Window
Terminal Problem

Window
Terminal Problem

SYN and SYN ACK
Problem on NEs
above PS core

ACK and GET
RAN problem/
Problem on NEs
below PS core

SYN ACK and ACK
RAN problem/
Problem on NEs
below PS core
DNS Abnormal Delay
Problem on NEs
above PS core

GET and Response
Problem on NEs
above PS core
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core

Loss Rate
RAN problem/
Problem on NEs
below PS core

Rate
Problem on NEs
above PS core
High Code Rate
SP Problem

2077
Nastar
Service
Assess
ment
Type
Integrity
File
Transfer
Issue 03 (2015-07-30)
Accessib
ility
Demarcation
Type
Video Streaming
Play Stall
File Request
Response Failure
Demarcation
Result

Period
RAN problem/
Problem on NEs
below PS core
Low Upstream
Problem on NEs
above PS core
Others
Others

Window
Terminal Problem

Window
Terminal Problem
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core

Loss Rate
RAN problem/
Problem on NEs
below PS core

Rate
Problem on NEs
above PS core
High Code Rate
SP Problem

Between Clips in Playing
Period
RAN problem/
Problem on NEs
below PS core
Low Upstream
Problem on NEs
above PS core
Others
Others

4**
Terminal Problem

5**
SP Problem

(RAN Problem)
RAN problem/
Problem on NEs
below PS core
SP Problem
Problem on NEs
above PS core

2078
Nastar
Service
Assess
ment
Type
Demarcation
Type
Abnormal File
Request
Response Delay
Integrity
File Transfer
Failure
Slow File
Transfer
Issue 03 (2015-07-30)
Demarcation
Result
Others
Others
DNS Abnormal Delay
Problem on NEs
above PS core

SYN and SYN ACK
Problem on NEs
above PS core

SYN ACK and ACK
RAN problem/
Problem on NEs
below PS core

ACK and GET/POST
RAN problem/
Problem on NEs
below PS core
Abnormal Delay between

Redirect Response and
SYN
RAN problem/
Problem on NEs
below PS core

Problem on NEs
above PS core
Others
Others

4**
Terminal Problem

5**
SP Problem
Release
Terminal Problem
SP Problem
Others
Others

Window
Terminal Problem

Loss Rate
RAN problem/
Problem on NEs
below PS core

Rate
Problem on NEs
above PS core

Window
Terminal Problem

2079
Nastar
Service
Assess
ment
Type
Demarcation
Type
Demarcation
Result
High Uplink
Retransmission Rate
RAN problem/
Problem on NEs
below PS core
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core
Low Upstream
Problem on NEs
above PS core
Others
Others
Signaling Procedure
Issue 03 (2015-07-30)
Procedure Type
Procedure Name
SGSN
GPRS Attach
SGSN
Combined Attach
SGSN
Intra Combined RAU with IMSI Attached
SGSN
Inter Combined RAU with IMSI Attached
SGSN
MS Init GPRS Detach
SGSN
MS Init Combined Detach
SGSN
CN Init GPRS Detach
SGSN
CN Init Combined Deatch
SGSN
Implicit GPRS Detach
SGSN
Implicit Combined Detach
SGSN
MS Init IMSI Detach
SGSN
RAN Init Iu Release
SGSN
CN Init Iu Release
SGSN
RAU(others)
SGSN
Intra RAU
SGSN
Intra Combined RAU
SGSN
Inter RAU
SGSN
Inter Combined RAU

2080
Nastar
Issue 03 (2015-07-30)
Procedure Type
Procedure Name
SGSN
Periodic RAU
SGSN
Periodic Combined RAU
SGSN
Intra SRNS Relocation
SGSN
Inter SRNS Relocation
SGSN
3G to 2G System Change
SGSN
SGSN
Service Req
SGSN
Paging
SGSN
MS Init PDP Act
SGSN
MS Init PDP Sec Act
SGSN
CN Init PDP Act
SGSN
MS Init PDP Deact
SGSN
CN Init PDP Deact
SGSN
MS Init PDP Mod
SGSN
CN Init PDP Mod
SGSN
RAN Init RAB Release
SGSN
CN Init RAB Release
SGSN
CN Init PDP Sec Act
SGSN
RAB Assignment
SGSN
SGSN
SGSN
MME
EPS Attach
MME
Combined Attach
MME
Intra USN Intra E-UTRAN TAU
MME
Inter USN Intra E-UTRAN TAU
MME
eNodeB S1 Release
MME
CN Init S1 Release
MME
MS Init Detach

2081
Nastar
Issue 03 (2015-07-30)
Procedure Type
Procedure Name
MME
CN Init Detach
MME
MME
MS Init IMSI Detach
MME
CN Init IMSI Detach
MME
CN Init Implicit Detach
MME
X2 HandOver
MME
Intra MME S1 HandOver
MME
Inter MME S1 HandOver
MME
Paging
MME
SGs Paging
MME
Service Req
MME
MME
Intra USN GERAN to E-UTRAN Inter RAT TAU
MME
Intra USN UTRAN to E-UTRAN Inter RAT TAU
MME
Intra USN UTRAN Iu mode to E-UTRAN Inter RAT handover
MME
Inter USN UTRAN Iu mode to E-UTRAN Inter RAT handover
MME
Inter USN GERAN/UTRAN to E-UTRAN TAU
MME
Intra USN E-UTRAN to GERAN Inter RAT RAU
MME
Intra USN E-UTRAN to UTRAN Inter RAT RAU
MME
Intra USN E-UTRAN to UTRAN Iu mode Inter RAT handover
MME
Inter USN E-UTRAN to UTRAN Iu mode Inter RAT handover
MME
Inter USN E-UTRAN to GERAN/UTRAN Inter RAT RAU
MME
Intra USN Intra E-UTRAN Combined TAU
MME
Intra USN GERAN to E-UTRAN Inter RAT Combined TAU
MME
Intra USN UTRAN to E-UTRAN Inter RAT Combined TAU
MME
Inter USN Intra E-UTRAN Combined TAU
MME
Inter USN GERAN/UTRAN to E-UTRAN Combined TAU
MME
Intra USN Intra E-UTRAN Periodic TAU
MME
Dedicated Bearer Act

2082
Nastar
Issue 03 (2015-07-30)
Procedure Type
Procedure Name
MME
PDN GW Initiated Bearer Mod with Bearer QoS Update
MME
HSS Initiated Subscribed QoS Mod
MME
PDN GW Initiated Bearer Mod Without Bearer QoS Update
MME
MME
MME Initiated Dedicated Bearer Deact
MME
Bearer Resource Mod
MME
PDN Connectivity
MME
PDN Disconnection
MME
MME Requested PDN Disconnection
MME
Bearer Resource Allocation
MME
Default Bearer Act
GGSN/SAE-GW
Create PDP
GGSN/SAE-GW
Update PDP
GGSN/SAE-GW
Delete PDP
GGSN/SAE-GW
Traffic
SAE-GW
Create Session
SAE-GW
Modify Bearer
SAE-GW
Delete Session
SAE-GW
Create Bearer
SAE-GW
Update Bearer
SAE-GW
Delete Bearer
SAE-GW
Release Access Bearers
SAE-GW
Modify Bearer Command
SAE-GW
Delete Bearer Command
SAE-GW
Bearer Resource Command
GGSN/SAE-GW
Create Indirect Data Forwarding Tunnel
GGSN/SAE-GW
Delete Indirect Data Forwarding Tunnel
GGSN/SAE-GW
Authentication access
GGSN/SAE-GW
Radius Accounting

2083
Nastar
Procedure Type
Procedure Name
GGSN/SAE-GW
Disconnect
GGSN/SAE-GW
Credit-Control Messages (Gy)
GGSN/SAE-GW
Re-Auth Messages (Gy)
GGSN/SAE-GW
Abort-Session Messages (Gy)
GGSN/SAE-GW
Credit-Control Messages (Gx)
GGSN/SAE-GW
Re-Auth Messages (Gx)
GGSN/SAE-GW
Abort-Session Messages (Gx)

Cause
SOURCE
CHR_PROC_INIT_CAUSE_MS
CHR_PROC_INIT_CAUSE_MS_ATTACH
CHR_PROC_INIT_CAUSE_MS_RAU
CHR_PROC_INIT_CAUSE_MS_DEACT_DECODE_FAIL
CHR_PROC_INIT_CAUSE_MS_DEACT_LLC_FAIL
CHR_PROC_INIT_CAUSE_MS_DEACT_INSUFF_RESOURCE
Procedure initiated
by the MS
CHR_PROC_INIT_CAUSE_MS_DEACT_REGULAR
CHR_PROC_INIT_CAUSE_MS_DEACT_QOS_NOT_ACCEPT
CHR_PROC_INIT_MS_ACT
CHR_PROC_INIT_MS_SEC_ACT
CHR_PROC_INIT_MS_MOD
CHR_PROC_INIT_MS_SERVICE_REQ_SIGNALLING
CHR_PROC_INIT_MS_SERVICE_REQ_DATA
CHR_PROC_INIT_MS_SERVICE_REQ_PAGING_RSP
Issue 03 (2015-07-30)

2084
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_SGSN
CHR_PROC_INIT_CAUSE_SGSN_INTERNAL_FAIL
CHR_PROC_INIT_CAUSE_SGSN_INIT_SECURITY
CHR_PROC_INIT_CAUSE_SGSN_INIT_UPDATE_LOCATION
CHR_PROC_INIT_CAUSE_SGSN_DIFF_SERVICE_CHK
CHR_PROC_INIT_CAUSE_SGSN_LICE_LIMIT
CHR_PROC_INIT_CAUSE_SGSN_FLOW_CTRL
CHR_PROC_INIT_CAUSE_SGSN_IUFLEX_CFG_ERR
CHR_PROC_INIT_CAUSE_SGSN_APNNI_FORBID
CHR_PROC_INIT_CAUSE_SGSN_DETACH_NONACT_USER
CHR_PROC_INIT_CAUSE_LMT_DEL
CHR_PROC_INIT_CAUSE_SGSN_USPU_LOCKED
CHR_PROC_INIT_CAUSE_OLD_SGSN
CHR_PROC_INIT_CAUSE_OLD_SGSN_IMSI_UNKOWN
CHR_PROC_INIT_CAUSE_OLD_SGSN_MISS_MAND_IE
CHR_PROC_INIT_CAUSE_NEW_SGSN
CHR_PROC_INIT_SGSN_ACT
CHR_PROC_INIT_SGSN_MOD
Procedure initiated
by the SGSN
CHR_PROC_INIT_CAUSE_SGSN_DEACT_PATH_ERR
CHR_PROC_INIT_CAUSE_SGSN_DEACT_CARD_FAIL
CHR_PROC_INIT_CAUSE_SGSN_DEACT_CDRF_LIMIT
CHR_PROC_INIT_CAUSE_SGSN_DEACT_CAMEL_DELETE
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GGSN_RESTART
CHR_PROC_INIT_CAUSE_SGSN_DEACT_PDP_IDLE
CHR_PROC_INIT_CAUSE_SGSN_DEACT_LOC_STATE_ERR_
IND
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GB_ERR_IND_PDP
_NOT_ACTIVE
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GB_ERR_IND_LLC
_DATA_UNITDATA_ERR
CHR_PROC_INIT_CAUSE_SGSN_DEACT_V0_GGSN_ERR_IN
D
D
CHR_PROC_INIT_CAUSE_SGSN_DEACT_V0_SGSN_ERR_IN
D
D
CHR_PROC_INIT_CAUSE_SDB
Issue 03 (2015-07-30)

2085
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_HLR
CHR_PROC_INIT_CAUSE_HLR_SUB_DEL
CHR_PROC_INIT_CAUSE_HLR_SUB_CAMEL_DEL
CHR_PROC_INIT_CAUSE_HLR_CANCEL_LOCATION
CHR_PROC_INIT_CAUSE_HLR_DEACT_SUB_MOD
Procedure initiated
by the HLR
CHR_PROC_INIT_CAUSE_HLR_ALL_ODB
CHR_PROC_INIT_CAUSE_HLR_VPLMN_ODB
CHR_PROC_INIT_CAUSE_HLR_HPLMN_ODB
CHR_PROC_INIT_CAUSE_HLR_ARD
CHR_PROC_INIT_CAUSE_HLR_ZC_RESTRIC
CHR_PROC_INIT_CAUSE_HLR_SUBSCRIBE_INFO_FORBID
CHR_PROC_INIT_CAUSE_HLR_AUTHSET_ERROR
Issue 03 (2015-07-30)
Procedure initiated
by the GGSN
CHR_PROC_INIT_CAUSE_GGSN
Procedure initiated
by the DNS
CHR_PROC_INIT_CAUSE_DNS
CHR_PROC_INIT_CAUSE_DNS_RET_INVALID_ADDR
Procedure initiated
by the MSC
CHR_PROC_INIT_CAUSE_MSC
CHR_PROC_INIT_CAUSE_MSC_UNREACHABLE
Procedure initiated
by the EIR
CHR_PROC_INIT_CAUSE_EIR
Procedure initiated
by the SCP
CHR_PROC_INIT_CAUSE_SCP
Procedure initiated
by the BSS
CHR_PROC_INIT_CAUSE_BSS
Procedure initiated
by the RNC
CHR_PROC_INIT_CAUSE_RNC

2086
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GTPU_BLOCK
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GTPU_SM_IP_TEID
_REPEATED
CHR_PROC_INIT_CAUSE_SGSN_DEACT_NO_EPS_BR_CONTEXT
CHR_PROC_INIT_CAUSE_APN_RESTRICTION
Procedure initiated
by the SGSN
CHR_PROC_INIT_CAUSE_SMARTPHONE_SPECIAL_CAUSE_
REJECT
CHR_PROC_INIT_CAUSE_SMARTPHONE_PARKING_APN
CHR_PROC_INIT_CAUSE_SMARTPHONE_DETACH_ABNOR
MAL_MS
CHR_PROC_INIT_CAUSE_SMARTPHONE_WAKE_UP_DETACH
CHR_PROC_INIT_CAUSE_SMARTPHONE_WAKE_UP_DEAC
T_PARKING_APN
CHR_PROC_INIT_CAUSE_SGSN_INTERNAL_PDP_MOD
CHR_PROC_INIT_CAUSE_UE
CHR_PROC_INIT_CAUSE_UE_ATTACH
CHR_PROC_INIT_CAUSE_UE_HO
Procedure initiated
by the UE
CHR_PROC_INIT_UE_DETACH_FOR_IMSI_DETACH
CHR_PROC_INIT_UE_DETACH_FOR_PS_DETACH
CHR_PROC_INIT_MS_ESR_MO_CSFB_OR_1xCSFB
CHR_PROC_INIT_MS_ESR_MT_CSFB_OR_1xCSFB
CHR_PROC_INIT_MS_ESR_MO_CSFB_EMERGENCY_CALL_
OR_1xCSFB_EMERGENCY_CALL
CHR_PROC_INIT_CAUSE_PGWSGW
Procedure initiated
by the PGW/SGW
CHR_PROC_INIT_CAUSE_PGWSGW_BEARER_TO_BE_REMOVED
CHR_PROC_INIT_CAUSE_PGWSGW_CONTEXT_NOT_FOUN
D
CHR_PROC_INIT_CAUSE_PGWSGW_VOIMS_PAGING
Procedure initiated
by the HSS
Issue 03 (2015-07-30)
CHR_PROC_INIT_CAUSE_HSS

2087
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_ENODEB
CHR_PROC_INIT_CAUSE_ENODEB_CSFB_TRIGGERED_HO
CHR_PROC_INIT_CAUSE_ENODEB_SRVCC_GERAN_WITHO
UT_DTM
Procedure initiated
by the eNodeB
CHR_PROC_INIT_CAUSE_ENODEB_SRVCC_GERAN_WITH_
DTM_WITHOUT_HO
CHR_PROC_INIT_CAUSE_ENODEB_SRVCC_UTRAN_WITHO
UT_PSHO
CHR_PROC_INIT_CAUSE_ENODEB_SRVCC_UTRAN_WITH_
PSHO
CHR_PROC_INIT_CAUSE_ENODEB_S1_RELEASE
CHR_PROC_INIT_CAUSE_ENODEB_ERAB_RELEASE
CHR_PROC_INIT_CAUSE_ENODEB_HANDOVER_ERABFAIL
Issue 03 (2015-07-30)

2088
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_MME
CHR_PROC_INIT_CAUSE_PAGING_BY_NETWORK_DETACH
CHR_PROC_INIT_CAUSE_PAGING_BY_SM_SIG
CHR_PROC_INIT_CAUSE_PAGING_BY_SMS
CHR_PROC_INIT_CAUSE_PAGING_BY_GSS
CHR_PROC_INIT_CAUSE_PAGING_BY_CS
CHR_PROC_INIT_CAUSE_PAGING_BY_INSM
CHR_PROC_INIT_CAUSE_PAGING_BY_SM_DATA
CHR_PROC_INIT_IMSI_DETACH_BY_AUTO_OFFLOAD
CHR_PROC_INIT_IMSI_DETACH_BY_VLR_RESET
CHR_PROC_INIT_IMSI_DETACH_BY_HSS_CS_NOT_ALLOW
CHR_PROC_INIT_PAGING_BY_PGW_RESELECT,
Procedure initiated
by the MME
CHR_PROC_INIT_PDN_DEACT_BY_PGW_RESELECT
CHR_PROC_INIT_DETACH_BY_PGW_RESELECT
CHR_PROC_INIT_DETACH_FOR_REATTACH_REQUIRED_D
UETO_ABNORMAL_SINGALING_CTRL
CHR_PROC_INIT_DEACTVIATE_FOR_REACTIVATE_REQUI
RED_DUETO_ABNORMAL_SINGALING_CTRL
CHR_PROC_INIT_PARKING_APN_ACVTIVATE_DUETO_AB
NORMAL_SINGALING_CTRL
CHR_PROC_INIT_DETACH_FOR_REATTACH_NOT_REQUIR
ED_DUETO_ABNORMAL_SINGALING_CTRL
CHR_PROC_INIT_PAGING_IMSI_PS_BY_SGWPGW_FAILURE
CHR_PROC_INIT_PAGING_STMSI_PS_BY_SGWPGW_FAILURE
CHR_PROC_INIT_PDN_DEACT_BY_SGWPGW_FAILURE
CHR_PROC_INIT_DETACH_BY_SGWPGW_FAILURE
Appendix: Exception Cause Classification (Combined Analysis)

The section describes the exception cause classification in the summary table.
NOTE
The following table lists all the exception causes of all RATs. For detailed exception causes of each RAT, see
the exception cause description chapters of each RAT 4.10.10 Appendix: Exception Cause Classification /
Key Signaling.
Issue 03 (2015-07-30)

2089
Nastar
Abnormal
CauseClassificatio
n
Non-exception
NA
RAN
Accessibility
Abnormal
Access Failure (Intra-System)

Access Failure (Inter-System)
Access Failure
Call Setup Failure
Setup Failure(MOC)
Setup Failure(MTC)
Abnormal TA on Access
Abnormal RACH Level on Access
Setup Failure
RAN
Retainability
Abnormal
Abnormal Release (Intra-system)

Abnormal Release (Inter-system)
Abnormal Call Release
Service Interruption
Abnormal Release
RAN Mobility
Abnormal

Inter-System Outgoing Handover Failure (Normal Release)
Inter-System Outgoing Handover Failure (Abnormal Release)
Inter-System Incoming Handover Failure
Handover Failure
RAN Delay
Abnormal
Delay Problem
RAN Service
Quality
Abnormal
Poor Voice Quality Connect Ack->Disconnect
Short Call Problem

Abnormal Service Interaction Delay
Issue 03 (2015-07-30)

2090
Nastar
Abnormal
CauseClassificatio
n
PS Core
Accessibility
Abnormal
Attach Abnormal
Service Req Abnormal
Paging Abnormal
PDP Act Abnormal
PDP Sec Act Abnormal
RAB Assignment Abnormal
PDN GW Dedicated Bearer Act Abnormal
Default Bearer Act Abnormal
Dedicated Bearer Act Abnormal
PDN Connectivity Abnormal
Create PDP Abnormal
Create Session Abnormal
Create Bearer Abnormal
Create Indirect Data Forwarding Tunnel Abnormal
PS Core
Mobility
Abnormal
RAU Abnormal
Relocation Abnormal
System Change Abnormal
TAU Abnormal
Handover Abnormal
Interoperation Abnormal
PS Core PDP
Modification
Abnormal
PDP Mod Abnormal

PDN GW Initiated Bearer Mod Abnormal
Update PDP Abnormal
PS Core
Retainability
Abnormal
Detach Abnormal
Iu Release Abnormal
RAB Release Abnormal
PDP Deact Abnormal
PDN GW Initiated Bearer Deact Abnormal
Issue 03 (2015-07-30)

2091
Nastar
Abnormal
CauseClassificatio
n
S1 Release Abnormal
Bearer Deact Abnormal
PDN Disconnection Abnormal
Delete PDP Abnormal
Delete Session Abnormal
Delete Bearer Abnormal
Release Access Bearers Abnormal
Delete Bearer Command Abnormal
Delete Indirect Data Forwarding Tunnel Abnormal
PS Core
Bearer
Modification
Abnormal
Bearer Mod Abnormal

Bearer Resourece Mod Abnormal
Modify Bearer Abnormal
Update Bearer Abnormal
Modify Bearer Command Abnormal
Bearer Resource Command Abnormal
Traffic
Issue 03 (2015-07-30)

2092
Nastar
5 UMTS Network Optimization
UMTS Network Optimization
About This Chapter

The Nastar provides network optimization function. The network optimization function helps
you perform various UMTS theme analyses on the Nastar, including coverage analysis, intrafrequency analysis, 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.1 UMTS Coverage Analysis
Nastar provides the UMTS coverage analysis feature. Using this feature, you can analyze the
MRs reported by UEs, view the coverage, quality, and user layout of UMTS cells in tables and
charts, and perform troubleshooting based on the analysis results and suggestions provided by
Nastar. You can also help operators quickly locate the UMTS cells that are affected by poor
coverage, coverage overlap, and poor quality.
5.2 UMTS Intra-Frequency Neighboring Cell Analysis
On Nastar, you can identify redundant or missing intra-frequency neighboring UMTS cells or
incorrect priority settings by summarizing and analyzing the MRs and events sent by UEs,
problems due to redundant neighboring cells, missing neighboring cells, or incorrect priorities.
5.3 UMTS/GSM Neighboring Cell Analysis
On Nastar, you can check whether any neighboring GSM cell of a UMTS test cell is redundant
or missing by summarizing and analyzing the MRs and events sent by UEs, configuration data,
redundant or missing neighboring GSM cells.
5.4 UMTS Inter-Frequency Neighboring Cell Analysis
The UMTS inter-frequency neighboring cell analysis function enables the Nastar to discover
network quality problems due to missing or redundant inter-frequency neighboring cell
configuration, or improper priority configuration based on the measurement reports (MRs) and
events reported by UEs.
Issue 03 (2015-07-30)

2093
Nastar
5.5 UMTS Pilot Pollution Analysis

The Nastar analyzes the calls of subscribers to identify cells where pilot pollution exists, cells
that cause interference, and severity of cell pollution. It can display the analysis results on a map
so that you can geographically locate pilot pollution problems. This reduces the drive test (DT)
time and improves the accuracy of problem locating.
5.6 UMTS Uplink Interference Analysis
The Nastar analyzes received total wideband power(RTWP) data reported by NodeBs to help
you troubleshoot signal interference on the network. The Nastar also analyzes signal strength of
uplink main and diversity antennas to help you locate antenna problems.
5.7 UMTS Terminal Analysis
This section describes the UMTS terminal inventory analysis tasks, including the management
of terminal inventory analysis tasks and the query and export of terminal inventory analysis
reports. The system analyzes the KPIs in the call records of terminal users. This function helps
operators identify the terminals with poor performance in the UMTS network, therefore
encouraging terminal manufacturers to improve the terminals with poor performance and guide
subscribers to purchase terminals with good performance. In this case, subscribers can obtain
stable services, and the subscriber satisfaction can be improved. 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.
5.8 UMTS Cell Performance Analysis
5.9 UMTS Network Geographic Observation
5.10 VIP Analysis
Issue 03 (2015-07-30)

2094
Nastar
Issue 03 (2015-07-30)

2095
Nastar
5.1 UMTS Coverage Analysis

Nastar provides the UMTS coverage analysis feature. Using this feature, you can analyze the
MRs reported by UEs, view the coverage, quality, and user layout of UMTS cells in tables and
charts, and perform troubleshooting based on the analysis results and suggestions provided by
Nastar. You can also help operators quickly locate the UMTS cells that are affected by poor
coverage, coverage overlap, and poor quality.
5.1.1 Basics of UMTS Coverage Analysis

This section describes the basics of the UMTS coverage analysis feature, including analysis
functions, technical specifications, and restrictions. Read this section before you perform UMTS
coverage analysis.
NOTE
Functions of UMTS Coverage Analysis

The Nastar analyzes the measurement reports (MRs) sent by UEs to display the coverage, quality,
and subscriber distribution of the test cell. The analysis result helps users to determine whether
problems such as weak cell coverage, cross coverage, and poor service quality occur on the live
network.
An MR reported by a UE contains downlink received signal code power (RSCP), Ec/No, transmit
propagation delay (TP), DL BLER, and UE TX POWER. After you specify the conditions for
coverage analysis, the Nastar analyzes the coverage of the selected cell and then displays the
analysis results in a two-dimensional chart, a three-dimensional chart, and a table.
l
In the two-dimensional chart, information about the following services is displayed: AMR,
VP, BE, AMR+BE, and OTHER services. Information about the AMR and VP services
contains five counters: RSCP, Ec/No, TP, DL BLER, and UE TX POWER. Information
about the BE, AMR+BE, and OTHER services contains four counters: RSCP, Ec/No, TP,
and UE TX POWER.
In the three-dimensional chart, information about the CS and PS services is displayed.

Information about each service contains four counters including Ec/No, RSCP, TP, and UE
TX POWER.
In the overview table, the counter statistics of all services involved in the two-dimensional
chart are displayed.
The results of coverage analysis can be exported as .csv, .xls, or .xlsx files. Users can optimize
cells with coverage problems according to the exported analysis results.
Function Principles
The Nastar uses the MRs on the NE side for UMTS coverage analysis.
Issue 03 (2015-07-30)

2096
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00

2097
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

2098
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
analysi
s task
Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for UMTS Coverage Analysis

of analysis time.
NOTE
Issue 03 (2015-07-30)
Item
Execution type
One-time task
<= 10,000 cells
<= 50

task
7 days
<= 85 minutes

analysis data
8 days

analysis data
8 days

2099
Nastar
5.1.2 Preparations for UMTS Coverage Analysis

Before starting a UMTS coverage analysis task, you must check the operation rights and the
matching environment and prepare relevant data to ensure that the UMTS coverage analysis task
is executed normally. Therefore, you must read this section before starting the analysis.
Checking the License and Operation Rights

l
Check that you have applied the license for UMTS coverage analysis and the license is
valid.
Check that the logged in user has the rights to subscribe to the data source for coverage
analysis upon login.
You are advised to contact the administrator to turn on the data source switch because the
data source subscription function has a high security requirement.
Check that the user has the rights to create a UMTS coverage analysis task upon login.

Configuration Data
Data.
NOTE
To ensure the validity of configuration data, you are advised to perform UMTS coverage analysis on a
daily basis.

5.1.3 Process of UMTS Coverage Analysis

This section describes the process of UMTS coverage analysis and the steps of each operation
procedure.
Issue 03 (2015-07-30)

2100
Nastar
Prerequisite
Procedure
Prerequisite
UMTS configuration data has been imported to the Nastar Database. For details, see 5.1.2
Preparations for UMTS Coverage Analysis.
Procedure
Issue 03 (2015-07-30)

2101
Nastar
Table 5-2 Process of UMTS Coverage Analysis

N Step
o
.
Description
Details
(
1
)
Navigation path: Choose Maintenance >

Data Maintenance Management
3.6 Checking the

Integrity of Analysis
Data
Check the
integrity of the
UMTS
coverage
analysis data
Procedure:
1. Set Data Type to UMTS coverage
analysis data.
3. Select the 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
security requirements. You are advised
to contact the administrator with
subscription rights to perform the
(
2
)
Subscribe to
the UMTS
coverage
analysis data
(basic)

Data Subscription Management
3.5 Subscribing to
Analysis Data
Procedure:
1. In the Data Subscription
Management window, click the
UMTS tab.
2. In the navigation tree, select the NEs.
3. On the Basic Subscription Settings
tab page, click Set.
4. In the Basic Subscription Settings
dialog box, set Coverage Analysis
Data to ON.
5. Click Confirm.
Verify that the function is successfully
enabled in the Log Info area.
Issue 03 (2015-07-30)

2102
Nastar
N Step
o
.
Description
Subscribe to
the UMTS
coverage
analysis data
(application)
Details

Procedure:
UMTS tab.
2. In the navigation tree, select the NEs.
3. On the Coverage Analysis tab page,
click ON.
Check that data is successfully
subscribed by clicking Refresh and
viewing the application subscription
status.
Check the
integrity of the
UMTS
coverage
analysis data

Procedure:
3.6 Checking the

Data
1. Set Data Type to UMTS coverage

analysis data.
3. Select the NEs.
4. Click Query.
l If the analysis data does not exist,
Issue 03 (2015-07-30)

2103
Nastar
N Step
o
.
Description
Details
(
3
)
Navigation path: In the Analysis Task

Management window, choose Theme
Function > Basic Network
Optimization > UMTS Coverage
Analysis.
3.7 Creating an Analysis

Task
Create a
UMTS
coverage
analysis task
Procedure:
1. Double-click UMTS Coverage
Analysis.
2. Set the task name and remarks. Click
Next.
3. On the Select NE(s) tab page, select the
NEs.
4. On the Parameter Settings tab page,
set the filter criteria.
5. Optional: Select MR Numbers, set
the MR quantity, and click Next.
6. Specify the analysis period. Nastar
obtains the data of the analysis period.
7. Click Finish.
For details about the parameters, see
Analysis Task Parameters.
(
4
)
View the
UMTS
coverage
analysis 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.
3.8 Querying Analysis

Results
Procedure:
2. In the UMTS Coverage Analysis
Task dialog box, view the analysis
results.
For details about the dialog box, see
5.1.4 Interface Description: UMTS
Coverage Analysis.
Issue 03 (2015-07-30)

2104
Nastar
N Step
o
.
Description
Details
(
5
)
Navigation path: Click the icon on the

toolbar in the upper left part of each
analysis results window.
3.10 Exporting Analysis

Reports
Export the
UMTS
coverage
analysis report
Procedure:
1. Click the export icon in the toolbar.
For details about the icon, see 5.1.4
Interface Description: UMTS
Coverage Analysis.
2. Set the save path and format of the
analysis report.
3. Click Save.

Basic Subscription
Parameter
Description
Coverage
Analysis Data
(MR)
Switch for enabling or disabling the reporting of MR data. You can retain
You can click
to set advanced parameters (mainly the parameters for
MR collection). For details, see the LST UMMMRCTRL command in the
related NE product documentation. You can select all or none of the options
for a parameter or retain the existing settings.

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Issue 03 (2015-07-30)

2105
Nastar
Parameter
Description
Remarks

NE information
Parameter
Description
Select NE(s)

NOTE
Parameter settings
Parameter
Parameters
Setting
Description
Analysis KPI
Set the data filter criteria. Nastar provides 30 default

filter criteria.
After the filter criteria is set, only the filtered analysis
data is displayed.
Numbers
The value range is 10 to 100,000. The default value is

100.
After the filter criteria is set, only the filtered analysis
data is displayed.

Parameter
Description
Duration
Delay
immediately.
Execute on
Issue 03 (2015-07-30)

2106
Nastar
5.1.4 Interface Description: UMTS Coverage Analysis

This section describes the interface for UMTS coverage analysis. Before performing relevant
Opening the Window

You can open the UMTS Coverage Analysis Task dialog box in two modes:
l
Select an executed UMTS coverage analysis task, and double-click a result of the task in
Select an executed UMTS coverage analysis task, right-click a result of the task in the Task
Main Window
UMTS coverage analysis results are displayed in 2-dimension/3-dimension windows or lists.
For details, see Figure 5-3, Figure 5-4, or Figure 5-5.
Figure 5-3 2-dimension window
Issue 03 (2015-07-30)

2107
Nastar
N
o.
Name
Description
Button
area
Two buttons are provided:
Cell
navigati
on tree
is used to export the summary report of UMTS coverage analysis,

which contains the summary of the analysis data of all cells involved in
the analysis task.
Click the icon, and set the save path. The report is exported as a .csv, .xls
or .xlsx file.
is used to export the raw data report of UMTS coverage analysis,

which contains the raw data information of all cells involved in the
analysis task.
Click the icon, and set the save path and file names for exporting the
report. The report is exported as five .csv, .xls or .xlsx files:
TP,RSCP ,ECNO , DL BLER, and UE TX POWER.
Selects all objects to be analyzed. System afford filter function of Cell

navigation tree.
l Middle part: Enter the NodeB name in the search box, and press Enter
or click
. The cells whose analysis results you want to view are
displayed.
l Upper part: Select a filter formula. Nastar automatically filters the cells
that meet the specified formula in the navigation tree. The percentage of
the cells that meet the filter criteria is displayed, and the cells are listed
in descending order according to the percentage.
Filter formulas are set when you create the analysis task.
l Lower part: All cells can be displayed in a navigation tree.
The navigation tree provides the export function. Right-click a node in
the navigation tree, and choose Save As from the shortcut menu. Set the
save path, file name, and file type. The information about the cells under
the node can be exported as a .csv, .xls, or .xlsx file. By default, a csv file
is exported. The parameters in the file vary according to the actual
situations.
If no filter criterion is set, the file contains the following parameters:
RNC ID:RNC Name/Group Name, Cell ID:Cell Name, and Filter
Condition:ALL.
If filter criteria (percentage) is set, the file contains the following
parameters: RNC ID:RNC Name/Group Name, Cell ID:Cell
Name, Filter Condition:***.
Issue 03 (2015-07-30)

2108
Nastar
N
o.
Name
Description
2dimensi
on
window
Five tab pages are provided: AMR, VP, BE, AMR+BE, and OTHER. Each
tab page displays the bar chart and cumulative layout curve of each KPI of
the corresponding service. The KPIs of each service are as follows:
l The KPIs of AMR and VP services are as follows: RSCP, ECNO, TP, DL
BLER, and UE TX POWER.
l The KPIs of BE, OTHER, and AMR+BE services are as follows: RSCP,
ECNO, TP, and UE TX POWER.
Chart area:
l The description of the coordinate chart is as follows:
The horizontal axis indicates the value of each KPI.
The left vertical axis is a bar chart value, indicating the percentage of
the MRs of each KPI.
The right vertical axis is a line chart value, indicating the total
percentage of the MRs of all KPIs whose value is smaller than or equal
to a KPI value on the horizontal axis.
l You can double-click a chart to zoom in/out the chart.
Alternatively, you can use the mouse to drag the border of the chart or
right-click the chart and choose Zoom In or Zoom Out or Auto Range
from the shortcut menu to adjust the size of the chart.
You can also use the shortcut menu items to query, save, or print the chart.
Figure 5-4 Plane 3-dimension window
Issue 03 (2015-07-30)

2109
Nastar
No.
Name
Description
3dimensi
on area
The RSCP, ECNO, TP, and UE TX POWER of the CS and PS services are
divided into KPI pairs, corresponding to 12 tab pages. Each tab page
displays the KPI layout of the corresponding service.
The description of the chart area is as follows:
l The horizontal and vertical axes indicate the values of two different
KPIs.
l The color of each cell indicates the percentage of the KPI layout in the
case of a certain KPI pair.
Legends are provided on the right. Each number indicates a specific
percentage value.
l You can use the mouse to drag the border of the chart or right-click the
chart and choose Zoom In or Zoom Out from the shortcut menu to
adjust the size of the chart.
You can also use the shortcut menu items to query, save, or print the
chart.
Formula
area
Set the value ranges of the horizontal and vertical axes of the 3-dimension
chart, and click Calculation. Nastar automatically calculates the total
percentage of KPI layout within the value ranges.
Figure 5-5 KPI summary window
Issue 03 (2015-07-30)

2110
Nastar
No.
Name
Description
KPI
summar
y list
Displays the statistics of the KPIs of all services in the 2-dimension

window.
For details about the parameters, see 5.1.5 Parameters for Viewing
UMTS Coverage Analysis Results.
5.1.5 Parameters for Viewing UMTS Coverage Analysis Results

This section describes the parameters for querying UMTS coverage analysis results. You can
refer to the description when querying UMTS coverage analysis results.
Parameter
Parameter
Range
Unit
Description
Supported
Solution
Version
Service Type
AMR, VP, BE,

AMR+BE,
Other
N/A
Indicates the
service type for
coverage
analysis. The
coverage
analysis
involves the
following types
of services:
AMR, VP, BE,
AMR+BE, and
Other.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2111
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
TP
Measurement
Reports
[0,+)
Number
Indicates the
total number of
TP MRs of the
selected cell by
service type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
RSCP
Measurement
Reporsts
[0,+)
Number
Indicates the
total number of
RSCP MRs of
the selected cell
by service type
in the selected
time segment.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2112
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
ECNO
Measurement
Reports
[0,+)
Number
Indicates the
total number of
Ec/No MRs of
the selected cell
by service type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
DL BLER
Measurement
Reports
[0,+)
Number
Indicates the
total number of
DL BLER MRs
of the selected
cell by service
type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2113
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
UE TX Power
Measurement
Reports
[0,+)
Number
Indicates the
total number of
UE TX Power
MRs of the
selected cell by
service type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average TP
N/A
N/A
Indicates the
average TP of
the selected cell
by service type
in the selected
time segment.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2114
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RSCP
[-116,-25]
dBm
Indicates the
average RSCP
of the selected
cell by service
type in the
selected time
segment.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average ECNO
[-31.5,0]
dB
Indicates the
average Ec/No
of the selected
cell by service
type in the
selected time
segment.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2115
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average DL
BLER(%)
[0,100]
Indicates the
average DL
BLER of the
selected cell by
service type in
the selected time
segment.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average UE TX
POWER
[-50,33]
dBm
Indicates the
average UE TX
POWER of the
selected cell by
service type in
the selected time
segment.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
5.2 UMTS Intra-Frequency Neighboring Cell Analysis

On Nastar, you can identify redundant or missing intra-frequency neighboring UMTS cells or
incorrect priority settings by summarizing and analyzing the MRs and events sent by UEs,
Issue 03 (2015-07-30)

2116
Nastar
problems due to redundant neighboring cells, missing neighboring cells, or incorrect priorities.
5.2.1 Basics of UMTS Intra-Frequency Neighboring Cell Analysis

This section describes the basics of UMTS intra-frequency neighboring cell analysis in terms
of function, authority policies, technical specifications, and restrictions. You can refer to this
section when you analyze Inter-RAT Neighboring cells.
NOTE
Functions of UMTS Intra-Frequency Neighboring Cell Analysis

The MRs of UEs reflect the actual propagation status of radio signals. By using the UMTS intrafrequency neighboring cell analysis function, the Nastar can aggregate and analyze the MRs and
events reported by UEs on the network to check for redundant and missing neighboring cell
configuration of a test cell and to check for the priorities that need to be adjusted. By directly
displaying information, the Nastar help you to solve network quality problems that are caused
by redundant or missing neighboring cells or incorrect priorities of neighboring cells.
Proper neighboring cell relationships can guarantee that a UE at the edge of a cell can be handed
over in time. This helps in reducing intra-RAT interference, improving the quality of service of
the network, and ensuring stable network performance.
Using the configuration data and engineering parameters, the Nastar can analyze the intrafrequency neighboring cells of a selected cell on the basis of the MRs and events reported by a
UE. Based on the measurement data, the Nastar can determine the missing and redundant
neighboring cells and the neighboring cell priorities that need to be adjusted of the selected cell.
In addition, the Nastar can sequence the recommended priorities of the neighboring cells. By
comparing the recommended priorities and the actually configured priorities, you can adjust the
final priorities of the neighboring cells on the Nastar client.
The Nastar displays results in a line or bar chart. It displays the neighboring cells of different
types in different colors and the sequence of finally ascertained priorities.
You can export the results of the neighboring cell analysis as .csv, .xls, or .xlsx files, which help
to optimize the neighboring cell relationships on the network.
In measurement results, undefined neighboring cells are identified first by frequencies and
primary scrambling codes (PSCs). On the network, cells that have the same frequency and same
PSC always exist around a dominant cell. You need to predict the signal strength based on the
site location, antenna azimuth, and antenna gain of these cells and then determine the possible
neighboring cells. In addition, you need to export the analysis report on the possible neighboring
cells through the Nastar client.
The Nastar can also display the UMTS neighboring cell analysis and possible neighboring cell
analysis results on maps. By rending the test cell, missing neighboring cells, redundant
neighboring cells, defined neighboring cells, and undefined neighboring cells with different
colors, Nastar helps you to view the neighboring cell relationships easily.
Issue 03 (2015-07-30)

2117
Nastar
Function Algorithm
The neighboring cell analysis algorithms are the basis for determining the missing neighboring
cells, redundant neighboring cells, and recommended priorities of neighboring cells.
l
The algorithm for calculating the recommended priority of a neighboring cell is as follows:
1.
Calculate the overall score of a neighboring cell.

The overall score of a neighboring cell is determined together by the appearance times
of the neighboring cell, the relative difference between the Ec/No of the neighboring
cell and the Ec/No of the dominant cell, and the absolute difference between the Ec/
No of the neighboring cell and the Ec/No of the dominant cell.
2.
Sequence the total scores in descending order. The higher the overall score is, the
higher the recommended priority is.
The recommended highest priority is 1.
The algorithms for checking the missing neighboring cells are as follows:
In the case of an undefined neighboring cell, if the recommended priority of the neighboring
cell is not larger than the recommended number of neighboring cells, you can infer that the
neighboring cell is a missing neighboring cell.
The algorithms for checking the redundant neighboring cells are as follows:
In the case of a defined neighboring cell, if the recommended priority of the neighboring
cell is larger than the recommended number of neighboring cells, you can infer that the
neighboring cell is a redundant neighboring cell.
Function Principles
The Nastar uses the MRs on the NE side for intra-frequency neighboring cell analysis.
Issue 03 (2015-07-30)

2118
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00

2119
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

2120
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
analysi
s task
Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Limitation and Impact

The following factors may affect the accuracy of the neighboring cell analysis results:
l
Correctness of engineering parameters
Network stability such as the stability of air interface parameters and network topology
during the collection of UMTS neighboring cell analysis data
Table 5-4 describes the network changes and their impacts.
Table 5-4 Network changes and their impacts
Issue 03 (2015-07-30)
Network
Change
Impact
Addition or
deletion of base
stations
Affects the cell handover and network coverage. In this case, the
analysis result cannot correctly reflect the current network status.
Changes in
antenna data such
as the changes of
the azimuth, tilt
angle, and height
Results in the changes in the cell coverage and network interference.
Changes in
handover
relationships and
parameters
Affects the statistical results during the period of collecting and

optimizing the neighboring relationship data.

2121
Nastar
Network
Change
Impact
Changes in the
RNC topology or
other NE
topologies
Affects the execution of measurement tasks. The RNC is responsible

for collecting statistical results, and therefore measurement tasks
cannot be normally performed if the network topology is changed.
Users are advised to keep the network topology unchanged during
the data collection period.
Technical Specifications for UMTS Intra-frequency Neighboring Cell Analysis

of analysis time.
NOTE
Item
Execution type
One-time task

analysis task
<= 10,000 cells
Number of allowed
analysis tasks
<= 50

one analysis task
7 days

task
<= 135 minutes

15 days

15 days
5.2.2 Preparations for UMTS Intra-Frequency Neighboring Cell

Analysis
Before starting a UMTS intra-frequency neighboring cell analysis task, you must check the
operation rights and the matching environment and prepare relevant data to ensure that the
UMTS intra-frequency neighboring cell analysis task is executed normally. Therefore, you must
read this section before starting the analysis.
Issue 03 (2015-07-30)

2122
Nastar

l
Check that you have applied the license for UMTS intra-frequency neighboring cell
analysis and the license is valid.
Check that the user has the rights to subscribe to the data source for neighboring UMTS
cell analysis upon login.
Check that the user has the rights to create a UMTS intra-frequency neighboring cell
analysis task upon login.

Configuration Data
Data.
NOTE
To ensure the validity of the configuration data, you are advised to analyze the configuration data on a per
day basis.
Engineering Parameters
Issue 03 (2015-07-30)

2123
Nastar
Map File (Optional)

l
Check that the detected set cell 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(UMTS) > Turning On the Detected Set Cell
Reporting Switch (UMTS Intra-Frequency Neighboring Cell Analysis) in Nastar
5.2.3 Process of UMTS Intra-Frequency Neighboring Cell Analysis

This section describes the process of UMTS intra-frequency neighboring cell analysis and the
steps of each operation procedure.
l
Prerequisite
Procedure
Prerequisite
UMTS configuration data and UMTS engineering parameters have been imported to the Nastar
Database. For details, see 5.2.2 Preparations for UMTS Intra-Frequency Neighboring Cell
Analysis.
Procedure
Issue 03 (2015-07-30)

2124
Nastar
Issue 03 (2015-07-30)

2125
Nastar
Table 5-5 Process of UMTS intra-frequency neighboring cell analysis

N Step
o
.
Description
Details
(
1
)

3.6 Checking the

Integrity of
Analysis Data
Check the
integrity of
the UMTS
intrafrequency
neighborin
g cell
analysis
data
Procedure:
1. Set Data Type to UMTS Intra-Frequency
Neighboring Cell Analysis Data.
3. Select the NEs.
4. Click Query.
the window.
analysis task.
performing (2).
NOTE
(
2
)
Subscribe
to the
UMTS
intrafrequency
neighborin
g cell
analysis
data (basic)

3.5 Subscribing
to Analysis Data
Procedure:
click the UMTS tab.
2. Select the NEs in the navigation tree.
click Set.
4. In the Basic Subscription Settings dialog box, set
UMTS neighboring cell analysis data to ON.
By default, the data subscription function is in No
Modification state.
5. Click Confirm.
Verify that the function is successfully enabled in
the Log Info area.
Issue 03 (2015-07-30)

2126
Nastar
N Step
o
.
Description
Subscribe
to the
UMTS
intrafrequency
neighborin
g cell
analysis
data
(applicatio
n)

Check the
integrity of
the UMTS
intrafrequency
neighborin
g cell
analysis
data

Details
Procedure:
click the UMTS tab.
2. Select the NEs from the navigation tree.
3. On the Coverage Analysis tab page, click ON.
Check that data is successfully subscribed by
clicking Refresh and viewing the application
subscription status.
Procedure:
3.6 Checking the

Integrity of
Analysis Data
1. Set Data Type to UMTS Intra-Frequency

3. Select the NEs.
4. Click Query.
the window.
analysis task.
Issue 03 (2015-07-30)

2127
Nastar
N Step
o
.
Description
Details
(
3
)

Management window, choose Theme Function >
Basic Network Optimization > UMTS IntraFrequency Neighboring Cell Analysis Task in the
navigation tree.
3.7 Creating an
Analysis Task
Create a
UMTS
intrafrequency
neighborin
g cell
analysis
task
Procedure:
1. Double-click UMTS Intra-Frequency
Neighboring Cell Analysis Task.
3. On the Select NE(s) tab page, select the NEs.
4. On the Parameter Settings tab page, set the
Intra-Frequency Neighboring Cell Analysis
Data, and 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.
(
4
)
(
5
)
View the
UMTS
intrafrequency
neighborin
g cell
analysis
results

Analysis Task Management window, select an IntraFrequency Neighboring Cell analysis task in the
Finished state. In the lower right of the Task Result
area, select a result record of the task.
Procedure:
Export the
UMTS
intrafrequency
neighborin
g cell
analysis
report

upper left part of UMTS Intra-Frequency
Neighboring Cell Analysis results window.
3.8 Querying
Analysis Results

2. In the UMTS Intra-Frequency Neighboring
Cell Analysis window, view the UMTS intrafrequency neighboring cell analysis results.
For details about the window, see 5.2.5
Parameters for Viewing UMTS Intrafrequency Neighboring Cell Analysis Results.
3.10 Exporting
Analysis
Reports
Procedure
For details about the icon, see 5.2.4 Interface
Description: UMTS Intra-Frequency
3. Click .
Issue 03 (2015-07-30)

2128
Nastar

Basic Subscription
Parameter
Description
Intrafrequency
Neighboring
Cell Analysis
Data (MR)
You can click

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Parameter
Description
Select NE(s)

NOTE
Issue 03 (2015-07-30)

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

recommended to configure.
It can be any integer ranging from 0 to 63. The default value
is 30.
Super-distance threshold

neighboring cell.

Parameter
Description
Duration
Delay
immediately.
Execute on
5.2.4 Interface Description: UMTS Intra-Frequency Neighboring

Cell Analysis
This section describes the interface for UMTS intra-frequency neighboring cell analysis. Before
performing relevant operations, familiarize yourself with the functions of the areas on the
interface.
Opening the Window

You can open the UMTS Intra-Frequency Neighboring Cell Analysis Task dialog box in two
modes:
l
Select an executed UMTS intra-frequency neighboring cell analysis task, and double-click
a result of the task in the Task Result area.
Select an executed UMTS intra-frequency 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.
Issue 03 (2015-07-30)

2130
Nastar
Main Window
The UMTS intra-frequency neighboring cell analysis results are displayed in two tables
(Overview Neighboring Cell Data of the Test Cell and Detailed Neighboring cell Data of the
Test list) and a chart, as shown in Figure 5-8.
Figure 5-8 UMTS Intra-Frequency Neighboring Cell Analysis Task Interface
Issue 03 (2015-07-30)
N
o.
Name
Description
Button area

l
is used to export the summary of neighboring cell information,

that is, the information about all dominant cells involved in the
analysis task.
is used to export all neighboring cell analysis results, that is, the
information about the intra-frequency neighboring cells of all
dominant cells.
Nastar can save the neighboring cell analysis results as .csv, .xls,
or .xlsx files by RNC.
is used to export possible neighboring cell analysis results, that

is, the information about the possible neighboring cells of a dominant
cell.

2131
Nastar
N
o.
Name
Description
Dominant
cell list
Displays information about the current dominant cells. You can press
Ctrl+F to search in the list, or right-click in the list and choose Save
As from the shortcut menu to save the list.
Neighborin
g cell list
Lists all neighboring UMTS cells of the dominant cells in the cell list.
The background of undefined neighboring cells is gray, and the
background of indoor neighboring cells is black.
l You can view the possible neighboring cell analysis results of a
dominant cell by performing the following operations:
1. Right-click an undefined neighboring cell and choose View
Possible Neighboring Analysis from the shortcut menu.
2. In the displayed dialog box, select a neighboring cell as a possible
neighboring cell and click OK.
3. In the neighboring cell list, the updated fields such as RNC ID, CI,
Cell Name, Get from Config Data are displayed. For details, see
5.2.5 Parameters for Viewing UMTS Intra-frequency
Neighboring Cell Analysis Results.
l Nastar identifies the type of a neighboring cell according to the
neighboring cell analysis algorithm, and provides operation
suggestions. For details about the neighboring cell analysis algorithm,
see UMTS Intra-Frequency Neighboring Cell Analysis
Algorithm.
l User Modify indicates whether to automatically save the list
information after modification. If you select the check box of User
Modify, Nastar reads the modified information when you open the
analysis report next time.
If no modification is performed, Nastar 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 directory of
the client. The file will be automatically deleted when the analysis
task is deleted.
l You can double-click in the list to zoom out or zoom in the list.
Issue 03 (2015-07-30)

2132
Nastar
N
o.
Name
Description
Chart area
This area displays all neighboring cell information of a dominant cell in

bar chart and line chart.
l Upper part: The color of each legend indicates a neighboring cell type.
You can select a parameter from the drop-down list box on the right
to display the value of each neighboring cell in a line chart.
l Coordinate chart: The left axis represents the total score of
neighboring cells; the right axis represents the distance in kilometers;
the horizontal ordinate represents neighboring cell names. If the name
of a missing neighboring cell of the dominant cell is unknown, the
system will display the name as Unknown Cell(Downlink ARFCNNeighboring P-SC).
The chart shows neighboring cells from left to right based on their
total scores in descending order. Only the top 32 neighboring cells
with a high overall priority are displayed.
You can right-click in the diagram and choose Zoom In, Zoom
Out, or Auto Range to adjust the chart size. You can also right-click
in the chart and choose a shortcut menu as required to query, save, or
print.
Map Interface
After you click
Figure 5-9 Map interface for UMTS Intra-Frequency neighboring cell analysis results
Issue 03 (2015-07-30)

2133
Nastar
No.
Name
Description
Button area
Navigation
tree

NOTE
in area 3.
3
Geographic
display area
Legend area

click
Information
area
in the button area.

5.2.5 Parameters for Viewing UMTS Intra-frequency Neighboring

Cell Analysis Results
This section describes the parameters for querying UMTS intra-frequency neighboring cell
analysis results. You can refer to the description when querying UMTS intra-frequency
Issue 03 (2015-07-30)

2134
Nastar
General Information About a Test Cell

Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
[0,+)
N/A
Indicates the ID
of an RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of a dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2135
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Downlink
ARFCN
N/A
N/A
Indicates the
downlink
absolute radio
frequency
channel number
(ARFCN) of the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2136
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of MRs
received by the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average ECNO
[-24.5,0]
dB
Indicates the
average ECNO
of the dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2137
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RSCP
[-116,-25]
dBm
Indicates the
average
Received Signal
Code Power
(RSCP) of the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of the
1A1C Events
[0,+)
Number
Indicates the
total number of
1A1C events
triggered by
neighboring
cells.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2138
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Missing
Neighboring
Cells
[0,+)
Number
Indicates the
number of
missing intrafrequency
neighboring
cells among the
undefined
neighboring
cells of the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Missing
Neighboring
cell Percentage
(%)
[0.00,100.00]
Sum of the
overall scores of
all missing
neighboring
cells of the
current
dominant cell/
Sum of the
overall scores of
all measured
neighboring
cells of the
current
dominant cell x
100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2139
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Redundant
Neighboring
Cells
[0,+)
Number
Indicates the
number of
redundant intrafrequency
neighboring
cells among the
defined
neighboring
cells of the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Configured
Intra-Frequency
Neighboring
Cells
[0,31]
Number
Indicates the
number of
defined intrafrequency
neighboring
cells of the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2140
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Service Type of
Cell
Indoor, Outdoor
or null
N/A
Indicates the
service type of
the current
dominant cell,
such as indoor
site, outdoor site
and unknow
service type.
Learning the
service type of
the current
dominant cell
helps prevent
important
neighboring
cells from being
mistakenly
deleted.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2141
Nastar
Detailed Information About Neighboring Cells

Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
a neighboring
cell belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell ID
0 to 65535
N/A
Indicates the ID
of a neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2142
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
neighboring
cell, for
example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring PSC
[0,511]
N/A
Indicates the
primary
scrambling code
of a neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2143
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Suggested
Operation
"Defined
Neighboring
Cell
(Reserved)",
"Defined
Neighboring
Cell
(Redundant)",
"Undefined
Neighboring
Cell(Missing)"
or "Undefined
Neighboring
Cell(NonOperation)"
N/A
Indicates the
operation
suggestions on a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
One-Way/TwoWay
"One-Way",
"Two-Way",
"Unknown", "-"
N/A
Field for
identifying a
unidirectional
or bidirectional
neighbor
relationship
based on
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2144
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
User Modify
N/A
N/A
Field for
identifying data
that users can
modify. Each of
such data
records contains
this field after
being exported.
Users can
change this field
as required.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Score
N/A
N/A
Indicates the
total score of
each
neighboring
cell. The total
score is
calculated using
the neighboring
cell algorithm
based on each
measurement
result.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2145
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Recommended
Priority
N/A
N/A
Indicates the
recommended
priority of a
neighboring cell
based on the
total score of the
neighboring
cell. The higher
the total score,
the higher is the
recommended
priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RSCP
of Neighboring
Cells
[-116,-25]
dBm
Indicates the
average RSCP
of a neighboring
cell in all MRs
containing the
information
about this
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2146
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average ECNO
of Neighboring
Cells
[-24.5,0]
dB
Indicates the
average ECNO
of a neighboring
cell in all MRs
containing the
information
about this
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average ECNO
of Primary Cells
[-24.5,0]
dB
Indicates the
average ECNO
of the dominant
cell in all MRs
containing the
current
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2147
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RSCP
of Primary Cells
[-116,-25]
dBm
Indicates the
average RSCP
of the best cell in
all the
measurement
reports that
contains the
current
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
MR Number of
the Neighboring
Cell in the
Monitor Set/
Detective Set
[0,+)
Number
Indicates the
number of MRs
containing the
current
neighboring cell
in the monitor
set or detected
set.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2148
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MR Number of
the Neighboring
Cell in the
Active Set
[0,+)
Number
Indicates the
number of MRs
containing the
current
neighboring cell
in the active set.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of the
1A1C Events
[0,+)
Number
Indicates the
number of
1A1C events
triggered by the
current
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2149
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of the
1D Events
[0,+)
Number
Indicates the
number of 1D
events triggered
by the current
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance
[0,+)
km
Indicates the
distance
between the
dominant cell
and the current
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2150
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Co-Site
Yes, No
N/A
Field for
determining
whether a
neighboring cell
shares the same
site with a
specified cell
based on certain
algorithms.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Super-Distance
Yes, No or null
N/A
Indicates that
the distance
between a
specified cell
and its
neighboring cell
exceeds a
predefined
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2151
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell Service
Type
Indoor, Outdoor
or null
N/A
Indicates the
type of a
neighboring
cell. The options
are indoor,
outdoor and
unknow service
type. Learning
the types of
neighboring
cells helps
prevent
important
neighboring
cells from being
mistakenly
deleted.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The Nastar
displays
information
indicating that
the allocation of
scrambling
codes is
inappropriate
when multiple
intra-frequency
cells have the
same
scrambling code
but different ID.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Remark
Empty or
Scrambling
codes may be
allocated
improperly
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2152
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Whether to Use
N/A
N/A
Indicates
whether to
select the
current possible
neighboring cell
as the most
possible
neighboring cell
of the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2153
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
a possible
neighboring cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of a possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2154
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance(km)
[0,+)
km
Indicates the
distance
between the
dominant cell
and the selected
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Relative Angle
of Neighboring
Cell
[0,360]
N/A
Indicates the
relative angle
between the
selected
possible
neighboring cell
and the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2155
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Predicted Signal
Strength
N/A
dBm
Indicates the
signal strength
of the selected
possible
neighboring cell
based on the
dimensioning.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Get From
Config Data
Yes, No
N/A
Indicates
whether the
selected
possible
neighboring cell
is obtained from
the
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2156
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Neighboring
Cell Laps
2, 3, 9
N/A
Indicates the
number of laps
between the
selected
possible
neighboring cell
and the
dominant cell,
that is, the
number of cells
between the
selected
possible
neighboring cell
and the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
5.3 UMTS/GSM Neighboring Cell Analysis

On Nastar, you can check whether any neighboring GSM cell of a UMTS test cell is redundant
or missing by summarizing and analyzing the MRs and events sent by UEs, configuration data,
redundant or missing neighboring GSM cells.
5.3.1 Basics of UMTS/GSM Neighboring Cell Analysis

This section describes the basics of UMTS/GSM neighboring cell analysis in terms of function,
authority policies, technical specifications, and restrictions. You can refer to this section when
you analyze UMTS/GSM neighboring cells.
NOTE
Functions of UMTS/GSM Neighboring Cell Analysis

The Nastar performs neighboring cell analysis based on the defined and undefined neighboring
GSM cells of the UMTS cells and then generates the analysis results. These analysis results help
users to identify problems such as redundant neighboring cells, missing neighboring cells, and
cross coverage. By directly displaying information, the Nastar helps you solve network quality
problems that are caused by the redundant or missing neighboring cells or cross coverage.
Issue 03 (2015-07-30)

2157
Nastar
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 on a bar chart. In the results, the defined neighboring GSM
cells, undefined neighboring GSM cells, redundant neighboring GSM cells, and missing
neighboring GSM cells are displayed in different colors.
The Nastar can export the inter-RAT neighboring cell analysis results. In the window of the
inter-RAT neighboring cell analysis results, after you add missing neighboring cells and delete
the redundant neighboring cells, the Nastar generates the analysis result file, which provides the
optimization suggestions.
You can export the results of the inter-RAT neighboring cell analysis as .csv, .xls, or .xlsx files,
which help to optimize the neighboring cell relationship on the network.
Function Algorithm
Based on the information reported by the MS such as the signal level of a cell, the Nastar
calculates the total score and then sorts the defined and undefined neighboring GSM cells.
According to the ranks of neighboring GSM cells and result charts, users can analyze the
neighboring cells depending on the actual network situation, and then provide operation
suggestions on configuring the missing neighboring GSM cells and deleting redundant
The algorithm is as follows:
1.
Calculate the overall priority of all the neighboring GSM cells of the test cell.
In terms of multiple factors such as GSM neighboring cell MRs and serving cell MRs, the
UMTS/GSM neighboring cell analysis provides scores and integrated priorities based on
the Nastar algorithms. The higher the integrated priority is, and the smaller the sequence
number is. The recommended highest priority is 1.
2.
Determine missing neighboring cells.

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

If the sequence number of a defined neighboring GSM cell is greater than Neighboring
Cell Count Setting (specified when a UMTS/GSM neighboring cell analysis task is
created), this defined neighboring GSM cell is regarded as a redundant neighboring cell.
Function Principles
The Nastar uses the UMTS MRs for UMTS/GSM neighboring cell analysis.
Issue 03 (2015-07-30)

2158
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00

2159
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

2160
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
analysi
s task
Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for UMTS/GSM Neighboring Cell Analysis

of analysis time.
NOTE
Issue 03 (2015-07-30)
Item
Execution type
One-time task

analysis task
<= 10,000 cells
Number of allowed
analysis tasks
<= 50

one analysis task
14 days

task
<= 5 minutes

15 days

15 days

2161
Nastar
5.3.2 Preparations for UMTS/GSM Neighboring Cell Analysis

Before starting a UMTS/GSM neighboring cell analysis task, you must check the operation rights
and the matching environment and prepare relevant data to ensure that the UMTS/GSM
neighboring cell analysis task is executed normally. Therefore, you must read this section before
starting the analysis.

l
Check that you have applied the license for UMTS/GSM neighboring cell analysis and the
license is valid.
Check that the user has the rights to subscribe to the data source for UMTS/GSM
neighboring cell analysis upon login.
Check that the user has the rights to create a UMTS/GSM neighboring cell analysis task
upon login.

Configuration Data
Data.
Issue 03 (2015-07-30)

2162
Nastar

NOTE
If the matching BSC6900 version is V900R012, check that the parameters for tracing missing neighboring
cells have been configured before using the neighboring UMTS/GSM cell analysis function of the Nastar.
For details, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data
> Preparing for Obtaining Data(UMTS) > Setting Neighboring Cell Measurement Parameters
(UMTS/GSM Neighboring Cell Analysis) in the Nastar System Commissioning Guide (HP) or Nastar
ATAE Cluster System Commissioning Guide (SUSE10, S3900).
5.3.3 Process of UMTS/GSM Neighboring Cell Analysis

This section describes the process of UMTS/GSM neighboring cell analysis and the steps of
each operation procedure.
l
Prerequisite
Procedure
Prerequisite
Database. For details, see 5.3.2 Preparations for UMTS/GSM Neighboring Cell Analysis.
Procedure
Issue 03 (2015-07-30)

2163
Nastar
Issue 03 (2015-07-30)

2164
Nastar
Table 5-7 Process of UMTS/GSM neighboring cell analysis

N Step
o
.
Description
Details
(
1
)

3.6 Checking the

Integrity of
Analysis Data
Check the
integrity of
the UMTS/
GSM
neighborin
g cell
analysis
data
Procedure:
1. Set Data Type to UMTS/GSM neighboring cell
analysis data.
3. Select an NE.
4. Click Query.
the window.
analysis task.
performing (2).
NOTE
(
2
)
Subscribe
to the
UMTS/
GSM
neighborin
g cell
analysis
data (basic)

3.5 Subscribing
to Analysis Data
Procedure:
click the UMTS tab.
2. Select an NE in the navigation tree.
click Set.
UMTS/GSM Neighboring Cell Analysis Data to
ON.
5. Click Confirm.
the Log Info area.
Issue 03 (2015-07-30)

2165
Nastar
N Step
o
.
Description
Subscribe
to the
UMTS/
GSM
neighborin
g cell
analysis
data
(applicatio
n)
Details

Procedure:
click the UMTS tab.
2. Select an NE in the navigation tree.
3. On the UMTS/GSM Neighboring Cell Analysis
tab page, click ON.
4. Specify the analysis period and NE objects, and set
the related parameters.
5. Click Confirm.
the Log Info area.
Task Parameters.
Check the
integrity of
the UMTS/
GSM
neighborin
g cell
analysis
data

Procedure:
3.6 Checking the

Integrity of
Analysis Data
1. Set Data Type to UMTS/GSM neighboring cell

analysis data.
3. Select an NE.
4. Click Query.
The system displays the existing status of the data
in the right pane.
5. Click Query.
the window.
analysis task.
Issue 03 (2015-07-30)

2166
Nastar
N Step
o
.
Description
Details
(
3
)

Basic Network Optimization > UMTS/GSM
Neighboring Cell Analysis from the navigation tree.
3.7 Creating an
Analysis Task
Create an
UMTS/
GSM
neighborin
g cell
analysis
task
Procedure:
1. Double-click UMTS/GSM Neighboring Cell
Analysis.
3. On the Select NE(s) tab page, select an NE.
4. On the Parameter Settings tab page, set Analysis
Parameter and Scores Settings. 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.
(
4
)
View the
UMTS/
GSM
neighborin
g cell
analysis
results

task.
3.8 Querying
Analysis Results
Procedure:
2. In the UMTS/GSM Neighboring Cell Analysis
dialog box, view the UMTS/GSM neighboring cell
analysis results.
Description: UMTS/GSM Neighboring Cell
Analysis.
Issue 03 (2015-07-30)

2167
Nastar
N Step
o
.
Description
(
5
)

Management window, select an UMTS/GSM
neighboring cell analysis task whose state is
Finished, and select the result of the task in the Task
Result area.
View the
possible
UMTS/
GSM
neighborin
g cell
analysis
results
Details
Procedure:
1. Right-click the result of the task, and choose
UMTS/GSM Possible Neighboring Analysis
2. In the UMTS/GSM Possible Neighboring Cell
Analysis dialog box, view the possible UMTS/
GSM neighboring cell analysis results.
Description: UMTS/GSM Possible
(
6
)
(
7
)
Export the
UMTS/
GSM
neighborin
g cell
analysis
report

Export the
possible
UMTS/
GSM
neighborin
g cell
analysis
report

Procedure:
3.10 Exporting
Analysis
Reports

3. Click Save.
Procedure:
3. Click Save.

Basic Subscription
Issue 03 (2015-07-30)

2168
Nastar
Parameter
Description
UMTS/GSM
Neighboring
Cell Analysis
Data (MR)
You can click
Parameter
Description
Begin Time
Specifies the start time of the measurement task.

The start time must be later than the current system
time.
End Time
Specifies the end time of the measurement task.

The end time must be later that the start time.

an analysis task to SAUs and delivers data
source switches to the NEs when users deliver
an application data subscription task.
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.
Measur
e Task
Begin NCC
End NCC
Begin BCC
End BCC
The start BCC of the BCC scope delimit the BCC

scope.
Frequency Band
Indicates the frequency band of UMTS/GSM cells.
Begin Frequency
The start frequency and end frequency delimit the

frequency scope.
End Frequency
Issue 03 (2015-07-30)
The start NCC and end NCC delimit the NCC

scope.
The NCC scope, BCC scope, and frequency scope

are used to determine the list of candidate UMTS/
GSM neighboring cells.

2169
Nastar

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Parameter
Description
Select NE(s)

NOTE
Parameter settings
Parameter
Description
Neighboring
Cell Count
Indicates the threshold of the neighboring cell sequence number. All the
undefined neighboring cells whose sequence numbers are smaller than or
equal to the value of this parameter are regarded as missing neighboring
cells. All the defined neighboring cells whose sequence numbers are larger
than the value of this parameter are regarded as redundant neighboring
cells.
This parameter can be set to any integer from 0 to 64. The default value
is 26.
Super-distance
threshold
Issue 03 (2015-07-30)
Specifies the threshold for the distance to a super-far neighboring cell.

The value of this parameter ranges from 0 to 50000 (unit: meter). The
default value of this parameter is 5000.

2170
Nastar
Parameter
Description
RankingNScore
Indicates the scores of the neighboring cell ranking No.1 to 8.

This parameter can be set to any integer from 1 to 100. In addition, the
neighboring cell with a small sequence number must obtain a higher score
than that of the neighboring cell with a large sequence number.

Parameter
Description
Duration
Delay
immediately.
Execute on
5.3.4 Reference for UMTS/GSM Neighboring Cell Analysis

Interface
This section describes the functions of each area in the following interfaces: UMTS/GSM
neighboring cell analysis and possible UMTS/GSM neighboring cell analysis. Before
interfaces.
Interface Description: UMTS/GSM Neighboring Cell Analysis

This section describes the interface for UMTS/GSM neighboring cell analysis. Before
interface.
Opening the Window

You can open the UMTS/GSM Neighboring Cell Analysis dialog box in two modes:
l
Select an executed UMTS/GSM neighboring cell analysis task, and double-click a result
Select an executed UMTS/GSM neighboring cell analysis task, right-click a result of the
Issue 03 (2015-07-30)

2171
Nastar
Main Window
The UMTS/GSM neighboring cell analysis results are displayed in two tables (cell list and
neighboring cell list) and a chart, as shown in Figure 5-12.
Figure 5-12 UMTS/GSM Neighboring Cell Analysis Interface
Issue 03 (2015-07-30)
N
o.
Name
Description
Button area

l
is used to export the summary of neighboring cell information,

that is, the information about all test cells involved in the analysis task.
is used to export the neighboring cell analysis results of a test

cell, that is, the information about all defined neighboring GSM cells
and undefined neighboring GSM cells of a test cell.
is used to export all the neighboring cell analysis results, that is,
the information about all defined neighboring GSM cells and
undefined neighboring GSM cells of all dominant cells.
Nastar can save the neighboring cell analysis results as .csv files by
RNC only. The neighboring cell analysis results of each RNC are
saved as a .csv file. The format of the csv file is as follows:
TaskName_NEName_WholeNet_NCS.

2172
Nastar
N
o.
Name
Description
Cell list
The system displays information about the current dominant cell. You can
press Ctrl+F to search in the list. Alternatively, you can right-click in the
list and choose Save As from the shortcut menu to save the list.
Neighborin
g GSM cell
list
Displays all the defined neighboring GSM cells and undefined

neighboring GSM cells of all cells in the cell list. The background of
undefined neighboring cells is gray, and the background of indoor
neighboring cells is black.
l Nastar identifies the type of a neighboring cell according to the
see UMTS/GSM Neighboring Cell Analysis Algorithm.
l Select the User Modify check box of a neighboring cell. Nastar
automatically saves the modification. You can view the modified
information when you open the analysis report next time.
If you perform no operation, Nastar reads the list information from the
database when you open the analysis report next time. Nastar
automatically saves the modified information as a file in the
installation directory of the client. The file will be automatically
deleted when the analysis task is deleted.
l You can double-click in the list to zoom in/out the list.
Chart area
The neighboring GSM cell information of a cell is displayed in bar chart

and line chart.
l Legend: The color of each legend indicates a neighboring cell type.
l Coordinate chart: The left vertical axis indicates the total score of a
neighboring cell, the right vertical axis indicates the current value of
the neighboring cell, and the horizontal axis indicates the name of the
neighboring cell. This chart lists the neighboring cells in descending
order from left to right according to the total score. Only the
neighboring cells whose overall priority ranks top 32 are listed.
You can use the mouse to drag the border of the chart or right-click
the chart and choose Zoom In or Zoom Out from the shortcut menu
to adjust the size of the chart. You can also use the shortcut menu items
to query or save the chart properties.
Issue 03 (2015-07-30)

2173
Nastar
Map Interface
After you click
Figure 5-13 Map interface for UMTS/GSM neighboring cell analysis results
No.
Name
Description
Button area
Navigation
tree

NOTE
in area 3.
3
Geographic
display area
Issue 03 (2015-07-30)

2174
Nastar
No.
Name
Description
Legend area

click
Information
area
in the button area.

Interface Description: UMTS/GSM Possible Neighboring Cell Analysis

This section describes the interface for UMTS/GSM possible neighboring cell analysis. Before
interface.
Opening the Window

You can open the UMTS/GSM Possible Neighboring Analysis dialog box in the following
mode:
Select an executed UMTS/GSM neighboring cell analysis task, right-click a result of the task in
the Task Result area, and choose UMTS/GSM Possible Neighboring Analysis from the
shortcut menu.
Main Window
The UMTS/GSM possible neighboring cell analysis results are displayed in two tables: summary
of possible neighboring cell analysis results and possible neighboring cell confirmation list, as
shown in Figure 5-14.
Issue 03 (2015-07-30)

2175
Nastar
Figure 5-14 UMTS/GSM Possible Neighboring Analysis Interface
N
o.
Name
Description
Button
area
Summary
of possible
neighborin
g cell
analysis
results
is used to export the possible neighboring cell analysis results, that

is, all information in the summary of possible neighboring cell analysis
results.
Summarizes the information about all possible neighboring GSM cells of
all cells involved in the analysis task.
You can press Ctrl+F to search information in the list.
Issue 03 (2015-07-30)

2176
Nastar
N
o.
Name
Description
Possible
neighborin
g cell
confirmati
on list
Displays all possible neighboring GSM cells of all cells in the summary
of possible neighboring cell analysis results.
l Upper part: button area.
is used to add possible neighboring cells for a dominant cell. The
Select a cell from the summary of possible neighboring cell analysis
results, and click this icon. The UMTS/GSM Possible Neighboring
Cell Analysis dialog box is displayed. Select one or multiple
neighboring cells in the navigation tree, and click OK. New lines are
added to the list. Each new line contains the information about a
possible neighboring cell.
l Lower part: neighboring cell list.
In the possible neighboring cell list, Whether to Use indicates
whether to set a possible neighboring cell as the best possible
neighboring cell of a dominant cell. If the Whether to Use check box
of a possible neighboring cell is selected, the related parameters (such
as Cell Name, Distance(km), and Number of Neighboring Cell
Laps) of the dominant cell are modified according to the possible
neighboring cell.
Otherwise, the preceding parameters will not be displayed in the left
area.
5.3.5 Reference for UMTS/GSM Neighboring Cell Analysis

Parameters
This section describes the parameters for viewing UMTS/GSM neighboring cell analysis and
possible UMTS/GSM neighboring cell analysis. You can refer to the description when viewing
UMTS/GSM neighboring cell analysis results.
Parameters for Viewing UMTS/GSM Neighboring Cell Results

This section describes the parameters for querying UMTS/GSM neighboring cell results. You
can refer to the description when querying UMTS/GSM neighboring cell results.
Issue 03 (2015-07-30)

2177
Nastar
Overview Neighboring Cell Data of the Test Cell

Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
the dominant
cell belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of a dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2178
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DownLink
ARFCN
[0,65535]
N/A
Indicates the
downlink
ARFCNs of a
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2179
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of MRs
[0,+)
N/A
Indicates the
total number of
MRs received
by each
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Redundant
Neighboring
Cells
[0,+)
N/A
Indicates the
number of
redundant
neighboring
GSM cells of the
current
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2180
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Missing
Neighboring
Cells
[0,+)
N/A
Indicates the
number of
missing
neighboring
GSM cells of the
current
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Missing
Neighboring
cell Percentage
(%)
[0.000,100.000]
N/A
Indicates the
sum of the
integrated
priority
percentages of
all missing
neighboring
cells for the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2181
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Configured
Neighboring
GSM Cells
[0,+)
N/A
Indicates the
number of
defined
neighboring
GSM cells of the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service Type of
Serving Cell
Issue 03 (2015-07-30)
Indoor, Outdoor
or null
N/A
Indicates the
service type of
the current
dominant cell,
such as indoor
site, outdoor site
and unknow
service type.
Learning the
service type of
the dominant
cell helps
prevent
important
neighboring
cells from being
mistakenly
deleted.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2182
Nastar
Detailed Neighboring Cell Data of the Test Cell

Parameter
Range
Unit
Description
Supported
Solution
Version
BSC Name
N/A
N/A
Indicates the
name of the
BSC that a
neighboring
GSM cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
LAC
[1,65533],
[65535]
N/A
Indicates the
location area
code of a
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2183
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CI
[0,65535]
N/A
Indicates the
cell identity of a
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
defined or
undefined
neighboring
GSM cell of the
current
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2184
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
of a neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900.
0 to 124, 975 to
1023: belong
to P-GSM 900.
0 to 124, 955 to
1023: belong to
P-GSM 900.
512 to 885:
belong to
DCS1800.
512 to 810:
belong to
DCS1900.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

2185
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
BSIC
[0,77]
N/A
Indicates the
base station
identity code of
a neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Defined
Neighboring
Cell
1 to 64
characters
N/A
Indicates
whether the
selected cell is
the defined
neighboring cell
of the current
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2186
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Suggested
Operation
Defined
Neighboring
Cell(reserved),
Defined
Neighboring
Cell
(Redundant),
Undefined
Neighboring
Cell(Missing)
and Undefined
Neighboring
Cell(NonOperation).
N/A
Indicates the
operation
suggestions
provided by the
Nastar on a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
One-Way/TwoWay
"One-Way",
"Two-Way",
"Unknown", "-"
N/A
Field for
identifying a
unidirectional
or bidirectional
neighbor
relationship
based on
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2187
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
User Modify
N/A
N/A
Field for
identifying data
that users can
modify. Each of
such data
records contains
this field after
being exported.
Users can
change this field
as required.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Score
[0,+)
N/A
Indicates the
total score of
each
neighboring cell
based on the
measurement
result according
to the
neighboring cell
algorithm.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2188
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Final Priority
N/A
N/A
Indicates the
final sequence
of priorities
adjusted on the
basis of
suggested
priorities.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Suggested
Priority
N/A
N/A
Indicates the
suggested
priorities
provided on the
basis of total
score of
neighboring
cells. The higher
the total score is,
the higher the
suggested
priority is.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2189
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Receive Level
of Neighboring
Cell
N/A
dBm
Indicates the
average receive
signal strength
of a neighboring
GSM cell
ranking No.1 in
MRs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Neighboring
Cell MRs
[0,+)
N/A
Indicates the
number of MRs
related to the
current
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2190
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance
[0,+)
km
Indicates the
distance
between the
current
dominant cell
and a
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Co-Site
Yes, No
N/A
Field for
determining
whether a
neighboring cell
shares the same
site with a
specified cell
based on certain
algorithms.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2191
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Super-Distance
Yes, No or null
N/A
Indicates that
the distance
between a
specified cell
and its
neighboring cell
exceeds a
predefined
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service Type of
Neighboring
Cell
Issue 03 (2015-07-30)
Indoor, Outdoor
or null
N/A
Indicates the
service type of a
neighboring
GSM cell, such
as indoor,
outdoor site and
unknow service
type. Learning
the service type
of the
neighboring
GSM cell helps
prevent
important
neighboring
cells from being
mistakenly
deleted.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2192
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Times A
Neighboring
Cell Ranking
No.1 in MRs
[0,+)
N/A
Indicates the
number of times
a cell ranking
No.1 in the
neighboring cell
list.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Times A
Neighboring
Cell Ranking
No.2 in MRs
[0,+)
N/A
Indicates the
number of times
a cell ranking
No.2 in the
neighboring cell
list.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2193
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Times A
Neighboring
Cell Ranking
No.3 in MRs
[0,+)
N/A
Indicates the
number of times
a cell ranking
No.3 in the
neighboring cell
list.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Times A
Neighboring
Cell Ranking
No.4 in MRs
[0,+)
N/A
Indicates the
number of times
a cell ranking
No.4 in the
neighboring cell
list.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2194
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Times A
Neighboring
Cell Ranking
No.5 in MRs
[0,+)
N/A
Indicates the
number of times
a cell ranking
No.5 in the
neighboring cell
list.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Times A
Neighboring
Cell Ranking
No.6 in MRs
[0,+)
N/A
Indicates the
number of times
a cell ranking
No.6 in the
neighboring cell
list.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2195
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Times A
Neighboring
Cell Ranking
No.7 in MRs
[0,+)
N/A
Indicates the
number of times
a cell ranking
No.7 in the
neighboring cell
list.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Times A
Neighboring
Cell Ranking
No.8 in MRs
[0,+)
N/A
Indicates the
number of times
a cell ranking
No.8 in the
neighboring cell
list.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Parameters for Viewing UMTS/GSM Possible Neighboring Cell Results

This section describes the parameters for querying UMTS/GSM possible neighboring cell
results. You can refer to the description when querying UMTS/GSM possible neighboring cell
results.
Issue 03 (2015-07-30)

2196
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
the dominant
cell belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of a dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2197
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
dominant cell,
for example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DownLink
ARFCN
N/A
N/A
Indicates the
downlink
ARFCNs of a
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2198
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2199
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BCCH
[0,1023]
N/A
Indicates the
broadcast
control channel
of a neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1 to 124: belong
to P-GSM 900.
0 to 124, 975 to
1023: belong
to P-GSM 900.
0 to 124, 955 to
1023: belong to
P-GSM 900.
512 to 885:
belong to
DCS1800.
512 to 810:
belong to
DCS1900.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
259 to 293:
belong to
GSM450.
306 to 340:
belong to
GSM480.
128 to 251:
belong to
GSM850.
R-GSM,
GSM450,
GSM480, and
GSM850 is
belong to
GSM900.
DCS1800 and
PCS1900 is
belong to
GSM1800.
Issue 03 (2015-07-30)

2200
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell BSIC
[0,77]
N/A
Indicates the
base station
identity code of
a neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BSIC=NCC*10
+BCC, NCC
[0,7], BCC
[0,7].
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC ID of the
Selected
Possible
Neighboring
Cell
N/A
N/A
Indicates the
name of the
BSC that the
selected
possible
neighboring
GSM cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2201
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Name of the
Selected
Possible
Neighboring
Cell
1 to 64
characters
N/A
Indicates the
name of the
selected
possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID of the
selected
possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
MCC[000,999]
l SRAN9.0/
GBSS16.0/
RAN16.0
MNC[00,99]
LAC[1,65533],
[65535]
CI[0,65535]
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2202
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
LAC
[1,65533],
[65535]
N/A
Indicates the
location area
code of the
selected
possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CI
[0,65535]
N/A
Indicates the
cell identity of
the selected
possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2203
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance
[0,+)
km
Indicates the
distance from
the dominant
cell to the
selected
possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Relative Angle
of Neighboring
Cell
[0,360]
N/A
Indicates the
relative angle
between the
selected
possible
neighboring
GSM cell and
the dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2204
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Predicted Signal
Strength
N/A
dBm
Indicates the
signal strength
of the selected
possible
neighboring
GSM cell based
on the
dimensioning.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Get from Config

Data
Yes, No
N/A
Indicates
whether the
selected
possible
neighboring
GSM cell is
obtained from
the
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2205
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Neighboring
Cell Laps
2,3,9
N/A
Indicates the
number of laps
between the
selected
possible
neighboring
GSM cell and
the dominant
cell, that is, the
number of cells
between the
selected
possible
neighboring
GSM cell and
the dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
number of
possible
neighboring
cells in the
possible
neighboring
GSM cell pair.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of
Possible
Neighboring
Cells in the
Possible
Neighboring
Cell Pairs
[0,+)
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2206
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Measurement
Reports
[0,+)
N/A
Indicates the
number of MRs
of the current
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Score
[0,+)
N/A
Indicates the
total score of
each
neighboring cell
based on the
measurement
result according
to the
neighboring cell
algorithm.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2207
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Whether to Use
N/A
N/A
Indicates
whether to
select the
current possible
neighboring
UMTS cell as
the most
possible
neighboring cell
of the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If the parameter
is selected, the
current possible
neighboring
UMTS cell
serves as the
most possible
neighboring
UMTS cell of
the test cell. In
addition, you
must replace the
information
about the
selected
possible
neighboring cell
in the possible
neighboring cell
confirmation
table with the
corresponding
information in
the possible
neighboring cell
overview table.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
If this parameter
is not selected,
the most
possible
neighboring cell
is not
determined. In
addition, the
system clears all
Issue 03 (2015-07-30)

2208
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
the information
in the fields in
the possible
neighboring cell
overview table.
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BSC
N/A
N/A
Indicates the
name of the
BSC that a
possible
neighboring
GSM cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2209
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CGI
MCC-MNCLAC-CI
N/A
Indicates the
global ID that a
possible
neighboring
GSM cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
MCC[000,999]
l SRAN9.0/
GBSS16.0/
RAN16.0
MNC[00,99]
LAC[1,65533],
[65535]
CI[0,65535]
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell LAC
[1,65533],
[65535]
N/A
Indicates the
location area
code of a
possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2210
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell CI
[0,65535]
N/A
Indicates the
cell identity of a
possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance
[0,+)
km
Indicates the
distance
between the
dominant cell
and a possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2211
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Relative Angle
of Possible
Neighboring
Cell
[0,360]
N/A
Indicates the
relative angle
between the
dominant cell
and a possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Predicted Signal
Strength
N/A
N/A
Indicates the
signal strength
of a possible
neighboring
GSM cell based
on the
dimensioning.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2212
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Obtain From
Configuration
Data
N/A
N/A
Indicates
whether the
possible
neighboring
GSM cell is
obtained from
the
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Neighboring
Cell Laps
2,3,9
N/A
Indicates the
number of laps
between the
dominant cell
and a possible
neighboring
GSM cell, that
is, the number of
cells between
the dominant
cell and a
possible
neighboring
GSM cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
5.4 UMTS Inter-Frequency Neighboring Cell Analysis

The UMTS inter-frequency neighboring cell analysis function enables the Nastar to discover
network quality problems due to missing or redundant inter-frequency neighboring cell
Issue 03 (2015-07-30)

2213
Nastar
configuration, or improper priority configuration based on the measurement reports (MRs) and
events reported by UEs.
5.4.1 Basics of UMTS Inter-Frequency Neighboring Cell Analysis

This section describes the basics of UMTS inter-frequency neighboring cell analysis, including
the analysis function, technical specifications, and feature limitation. This helps you perform
operations related to UMTS inter-frequency neighboring cell analysis. Read this section before
performing UMTS inter-frequency neighboring cell analysis.
NOTE
Functions of UMTS Inter-Frequency Neighboring Cell Analysis

Based on configuration data and engineering parameters, the Nastar aggregates and analyzes
measurement reports (MRs) and events reported by UEs to check missing and redundant
neighboring cell configuration of measurement cells and afford recommended priorities. By
using this function, the Nastar intuitively displays the required information, helping you solve
network quality problems that are caused by redundant or missing neighboring cell configuration
or improper configuration of neighboring cell priorities.
In the UMTS network, different UARFCNs are assigned for networking indoors and therefore
a large number of inter-frequency handovers occur. The femto cell also requires a large number
of inter-frequency handovers. In addition, as the number of femto cells is increasing, a large
number of redundant neighboring cells are configured for the cells using UARFCN f1. Therefore,
different UARFCNs are used and network problems may occur due to incorrect configuration
of inter-frequency neighboring cells.
After the user sets the filter criteria of redundant or missing neighboring cell configuration, the
Nastar can perform inter-frequency neighboring cell analysis on the selected cell. The analysis
results are displayed in bar charts or line charts. In addition, different kinds of neighboring cells
are marked with different colors and neighboring cells are sorted by priorities.
The Nastar also supports the export of inter-frequency neighboring cell analysis result files. In
the inter-frequency neighboring cell analysis result window, after the user supplements missing
neighboring cells and deletes redundant neighboring cells, an analysis result file is generated,
providing related optimization suggestions for users. You can export the analysis results as
a .csv, .xls, or .xlsx file, which helps to optimize the neighbor relationship on the network.
Function Algorithm
This section describes the algorithms for UMTS inter-frequency neighboring cell analysis, such
as the algorithms used to check missing and redundant neighboring cells.
The Nastar calculates the overall scores of defined and undefined neighboring cells and ranks
them based on the inter-frequency measurement reports reported by UEs. Based on the UMTS
neighboring cell ranking and analysis results, the Nastar provides operation suggestions on
supplementing missing neighboring cells and deleting redundant neighboring cells depending
on the live network conditions.
Issue 03 (2015-07-30)

2214
Nastar
The algorithms for UMTS inter-frequency neighboring cell analysis are as follows:
1.
The algorithm for calculating the overall priority of each inter-frequency neighboring cell
of the serving cell is as follows:
The priorities are ranked by the cell received signal power. The stronger the received signal
power, the higher the priority. The higher the priority, the smaller the sequence number.
2.
The algorithm for checking redundant neighboring cells is as follows:

If the sequence number of a defined UMTS neighboring cell in the inter-frequency
measurement report is greater than the value of Number of Configured Neighboring
Cells that is set when the user creates a UMTS inter-frequency neighboring cell analysis
task, this defined neighboring cell is considered as a redundant neighboring cell.
3.
The algorithm for checking missing neighboring cells is as follows:

If the sequence number of an undefined UMTS neighboring cell in the inter-frequency
measurement report is less than or equal to the value of Number of Configured
Neighboring Cells that is set when the user creates a UMTS inter-frequency neighboring
cell analysis task, this undefined neighboring cell is considered as a missing neighboring
cell.
Function Principles
The data source of UMTS inter-frequency neighboring cell analysis is MR data on the NE side.
Issue 03 (2015-07-30)

2215
Nastar

User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

2216
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for UMTS Inter-frequency Neighboring Cell Analysis

of analysis time.
NOTE
Issue 03 (2015-07-30)
Item
Execution type
One-time task

2217
Nastar
Item

analysis task
<= 10,000 cells
Number of allowed
analysis tasks
<= 50

one analysis task
14 days

task
<= 5 minutes

15 days

15 days
5.4.2 Preparations for UMTS Inter-Frequency Neighboring Cell

Analysis
Before running a UMTS inter-frequency neighboring cell analysis task, verify user rights and
related environment information and obtain related data, ensuring that the task is properly
executed. Read this section before performing UMTS inter-frequency neighboring cell analysis.

l
You have obtained the license for UMTS inter-frequency neighboring cell analysis and the
license is valid.
You are authorized to subscribe to data related to UMTS inter-frequency neighboring cell
analysis.
Subscribing to data source imposes high requirements on the security. You are advised to
ask the authorized administrator to enable the data source.
You are authorized to create a UMTS inter-frequency neighboring cell analysis task.

Configuration Data
Issue 03 (2015-07-30)

2218
Nastar
Data.
Map Files (Optional)

5.4.3 Process of UMTS Inter-Frequency Neighboring Cell Analysis

This section describes the process of UMTS inter-frequency neighboring cell analysis and each
procedure in the process.
l
Prerequisites
Procedure
Issue 03 (2015-07-30)

2219
Nastar
Prerequisites
Database. For details, see 5.4.2 Preparations for UMTS Inter-Frequency Neighboring Cell
Analysis.
Procedure
Issue 03 (2015-07-30)

2220
Nastar
Table 5-9 Description about the UMTS inter-frequency neighboring cell analysis flowchart
N Procedure
o
.
Description
Reference
(
1
)

3.6 Checking the

Integrity of
Analysis Data
Check data
integrity
related to
UMTS
interfrequency
neighborin
g cell
analysis
Procedure:
1. Set Data Type to UMTS Inter-Frequency
4. Click Query.
the window.
analysis task.
performing (2).
NOTE
(
2
)
Subscribe
to basic
data related
to UMTS
interfrequency
neighborin
g cell
analysis.

3.5 Subscribing
to Analysis Data
Procedure:
click the UMTS tab.
2. In the left navigation tree, choose NEs to be
configured.
click Set.
Inter-Frequency Neighboring Cell Analysis
Data to ON.
5. Click Confirm.
Verify that basic data subscription is successfully
enabled by viewing information displayed in the
Log Info area.
Issue 03 (2015-07-30)

2221
Nastar
N Procedure
o
.
Subscribe
to
application
data related
to UMTS
interfrequency
neighborin
g cell
analysis.
Description
Reference

Procedure:
click the UMTS tab.
2. In the left navigation tree, choose NEs to be
configured.
3. On the Inter-Frequency Neighboring Cell
Analysis tab page, click ON.
4. Set the analysis time period, NEs, and related
parameters.
Task Parameters.
5. Click Confirm.
Verify that basic data subscription is successfully
enabled by viewing information displayed in the
Log Info area.
Check data
integrity
related to
UMTS
interfrequency
neighborin
g cell
analysis

Procedure:
3.6 Checking the

Integrity of
Analysis Data
1. Set Data Type to UMTS Inter-Frequency

4. Click Query.
the window.
analysis task.
Issue 03 (2015-07-30)

2222
Nastar
N Procedure
o
.
Description
Reference
(
3
)
Navigation path: In the left navigation tree of the

UMTS Inter-Frequency Neighboring Cell
Analysis.
3.7 Creating an
Analysis Task
Create a
UMTS
interfrequency
neighborin
g cell
analysis
task.
Procedure:
1. Double-click UMTS Inter-Frequency
2. Set the task name and task remarks. Then, click
Next.
analyzed.
4. On the Parameter Settings tab page, set
parameters related to the neighboring cell. Then,
click Next.
5. Select the analysis time period. The Nastar will
obtain the related analysis data in the time period.
6. Click Finish.
Parameters.
(
4
)
View the
UMTS
interfrequency
neighborin
g cell
analysis
results.

task.
3.8 Querying
Analysis Results
Procedure:
2. In the displayed UMTS Inter-Frequency
Neighboring Cell Analysis Task window, view
the UMTS inter-frequency neighboring cell
analysis results.
For details on the analysis result window, see 5.4.4
Interface Description: UMTS Inter-Frequency
Issue 03 (2015-07-30)

2223
Nastar
N Procedure
o
.
Description
(
5
)
Navigation path: In the Detailed Neighboring Cell

Data of the Test Cell area, on the right pane of the
UMTS inter-frequency neighboring cell analysis
result window, select an undefined neighboring cell.
View the
UMTS
possible
neighborin
g cell
analysis
results.
Reference
Procedure:
1. Right-click an undefined neighboring cell and
choose View Possible Neighboring Analysis
2. In the displayed UMTS Inter-Frequency
Possible Neighboring Cell Analysis Task dialog
box, select a cell and click OK.
3. View the analysis results in the UMTS InterFrequency Neighboring Cell Analysis Task
table.
For details on the analysis result window, see 5.4.4
Interface Description: UMTS Inter-Frequency
(
6
)
Export the
UMTS
interfrequency
neighborin
g cell
analysis
report.

Procedure:
3.10 Exporting
Analysis
Reports

For details about the icon, see 5.4.4 Interface
Description: UMTS Inter-Frequency
2. Set the format and save path for the file to be
exported.
3. Click Save.

Basic Subscription
Issue 03 (2015-07-30)
Parameter
Description
Interfrequency
Neighboring
Cell Analysis
Data (MR)
You can click

2224
Nastar
Parameter
Description
Begin Time
Specifies the start time of the measurement task.

The start time must be later than the current system time.
End Time
Specifies the end time of the measurement task.

The end time must be later that the start time.
l If this parameter is selected, the Nastar delivers an analysis

task to SAUs and delivers data source switches to the 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.
Measur
e Task
DownLink
Uarfcn
Specifies the UARFCN to be measured for the neighboring

cell.
Value range: [10562,10838], [9662,9938], [1162,1513],
[1537,1738], [4357,4458], [4387,4413], [2237,2563],
[2937,3088], [9237,9387] .
You can also enter one of the following values: 412, 437, 462,
487, 512, 537, 562, 587, 612, 637, 662, 687, 1007, 1012, 1032,
1037, 1062, 1087, 1887, 1912, 1937, 1962, 1987, 2012, 2037 ,
2062, 2087, 2587, 2612, 2637, 2662, 2687, 2712, 2737, 2762,
2787, 2812, 2837, 2862, 2887, 2912.
Measure Begin
PSC
Measure Begin
PSC
Specifies the scrambling code range used by neighboring cells

and formed by start scrambling codes and end scrambling
codes.
The downlink UARFCN and scrambling code range together
determine the list of supplementary neighboring cells using the
UARFCN.
Both the start and end scrambling codes range from 0 to 511.
Add Downlink
ARFCN
You can click this icon to manually enter the downlink

ARFCNs for measurement.

Issue 03 (2015-07-30)

2225
Nastar
Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Parameter
Description
Select NE(s)

NOTE
Parameter Information
Parameter
Description
Number of
Configured
Neighboring
Cells
Specifies the number of neighboring cells configured on a UARFCN.
Super-distance
threshold
Specifies the threshold for the distance to a super-far neighboring cell.
The value is an integer ranging from 0 to 63. The default value is 30.
The value of this parameter ranges from 0 to 50000 (unit: meter). The
default value of this parameter is 5000.
Issue 03 (2015-07-30)

2226
Nastar
Parameter
Description
Duration
Delay
immediately.
Execute on
5.4.4 Interface Description: UMTS Inter-Frequency Neighboring

Cell Analysis
This section describes the result window of UMTS inter-frequency neighboring cell analysis,
including functions of each area in the window, helping you to perform related operations.
Opening the Window

You can enter the result window using either of the following methods:
l
Select a UMTS inter-frequency neighboring cell analysis task in the Finished state. Then,
in the displayed Task Result area, double-click the results of this task.
Select a UMTS inter-frequency neighboring cell analysis task in the Finished state. Then,
in the displayed Task Result area, right-click the results of this task and choose View
Main Window
The UMTS inter-frequency neighboring cell analysis result window displays information in
charts and tables. It consists of the test cell information list, neighboring cell information list,
and chart area, as shown in Figure 5-17.
Issue 03 (2015-07-30)

2227
Nastar
Figure 5-17 Result window of UMTS inter-frequency neighboring cell analysis
N
o.
Name
Description
Button area
Provides two buttons for entries of two function as follows:
Dominant
cell
information
list
exports the general neighboring cell analysis results.

Specifically, related information about all dominant cells involved in
the selected analysis task is exported.
exports all neighboring cell analysis results. Specifically, related

information about neighboring cells of all dominant cells is exported.
Only all neighboring cell analysis results can be exported as
a .csv, .xls, or .xlsx file by RNC.
Displays related information about all dominant cells involved in the

current task. It is associated with area 3 and area 4.
You can search information in the list by pressing Ctrl+F.
Issue 03 (2015-07-30)

2228
Nastar
N
o.
Name
Description
Neighborin
g cell list
Displays all UMTS inter-frequency neighboring cells of the selected

dominant cells in area 2. The background of undefined neighboring cells
is gray, and the background of indoor neighboring cells is black.
l You can view the possible neighboring cell analysis results of a
dominant cell by performing the following operations:
1. Right-click an undefined neighboring cell and choose View
Possible Neighboring Analysis from the shortcut menu.
2. In the displayed dialog box, select a neighboring cell as a possible
neighboring cell and click OK.
3. In the neighboring cell list, the updated fields such as RNC ID, CI,
Cell Name, Get from Config Data are displayed.
l The Nastar identifies the type of a neighboring cell according to the
see UMTS Intra-Frequency Neighboring Cell Analysis
Algorithm.
If the name of a missing neighboring cell is unknown, Nastar marks
the name of the neighboring cell with Unknown Cell.
l You can double-click in the list to zoom out or zoom in the list.
Chart area
Displays related information about all neighboring cells of the selected

dominant cell in bar charts and line charts.
l Upper part: The color of each legend indicates a neighboring cell type.
l Coordinate graphs: The left Y axis represents the overall score of each
neighboring cell; the right Y axis represents the distance in kilometers;
the X axis represents neighboring cell names. If the name of a missing
neighboring cell is unknown, the system will display the name with
Unknown Cell(Neighboring Downlink ARFCN-Neighboring PSC).
In this chart, the neighboring cells are listed in descending order from
left to right according to the total score.
You can right-click in the chart and choose Zoom In or Zoom Out
from the shortcut menu to adjust the size of the chart. You can also
use the shortcut menu items to query, save, or print the chart
properties.
Map Interface
After you click
Issue 03 (2015-07-30)

2229
Nastar
Figure 5-18 Map interface for UMTS Inter-Frequency neighboring cell analysis results
No.
Name
Description
Button area
Navigation
tree

NOTE
in area 3.
3
Geographic
display area
Legend area

click
Issue 03 (2015-07-30)
in the button area.

2230
Nastar
No.
Name
Description
Information
area

5.4.5 Parameters for Viewing UMTS Inter-frequency Neighboring

Cell Analysis Results
This section describes the parameters for querying UMTS inter-frequency neighboring cell
analysis results. You can refer to the description when querying UMTS inter-frequency
General Information About a Test Cell

Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
[0,+)
N/A
Indicates the ID
of an RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2231
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,65535]
N/A
Indicates the ID
of a dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
dominant cell,
for example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2232
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a dominant
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Downlink
ARFCN
N/A
N/A
Indicates the
downlink
absolute radio
frequency
channel number
(ARFCN) of the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2233
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Measurement
Requests
[0,+)
Number
Indicates the
number of MRs
received by the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Configed
Interfreq
Neighboring
Cells
[0,+)
Number
Indicates the
number of interfrequency
neighboring
cells that are
configured for
the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2234
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Missing
Neighboring
Cells
[0,+)
Number
Indicates the
number of
missing intrafrequency
neighboring
cells among the
undefined
neighboring
cells of the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Percentage of
Missing
Neighboring
cells
[0.000,100.000]
Sum of the
overall scores of
all missing
neighboring
cells of the
current
dominant cell/
Sum of the
overall scores of
all measured
neighboring
cells of the
current
dominant cell x
100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2235
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Redundant
Neighboring
Cells
[0,+)
Number
Indicates the
number of
redundant intrafrequency
neighboring
cells among the
defined
neighboring
cells of the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service Type of
Cell
Issue 03 (2015-07-30)
Indoor, Outdoor
or null
N/A
Indicates the
service type of
the current
dominant cell,
such as indoor
site, outdoor site
and unknow
service type.
Learning the
service type of
the current
dominant cell
helps prevent
important
neighboring
cells from being
mistakenly
deleted.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2236
Nastar
Detailed Information About Neighboring Cells

Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
a neighboring
cell belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring
Cell ID
0 to 65535
N/A
Indicates the ID
of a neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2237
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
neighboring
cell, for
example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Neighboring PSC
[0,511]
N/A
Indicates the
primary
scrambling code
of a neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2238
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Neighboring
Downlink
ARFCN
N/A
N/A
Indicates the
downlink
absolute radio
frequency
channel number
(ARFCN) of a
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Suggested
Operation
Issue 03 (2015-07-30)
"Defined
Neighboring
Cell
(Reserved)" ,
"Defined
Neighboring
Cell
(Redundant)" ,
"Undefined
Neighboring
Cell (Missing)"
or "Undefined
Neighboring
Cell (NonOperation)"
N/A
Indicates the
type of a
neighboring
cell. The options
are Defined
Neighboring
Cell (reserved),
Defined
Neighboring
Cell
(redundant),
Undefined
Neighboring
Cell (missing),
and Undefined
Neighboring
Cell (nonoperation).

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2239
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
One-Way/TwoWay
"One-Way",
"Two-Way",
"Unknown", "-"
N/A
Field for
identifying a
unidirectional
or bidirectional
neighbor
relationship
based on
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User Modify
N/A
N/A
Field for
identifying data
that users can
modify. Each of
such data
records contains
this field after
being exported.
Users can
change this field
as required.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2240
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Score
N/A
N/A
If this option is
selected, you are
advised to
perform
modification
according to
Neighboring
Cell Type.
Otherwise, no
user operation is
recommended.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Recommended
Priority
N/A
N/A
Indicates the
total score of
each
neighboring
cell. The total
score is
calculated using
the neighboring
cell algorithm
based on each
measurement
result.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2241
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RSCP
of Neighboring
Cells
[-115,-25]
dBm
Indicates the
average RSCP
of a neighboring
cell in all MRs
containing the
information
about this
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average ECNO
of Neighboring
Cells
[-24,0]
dB
Indicates the
average ECNO
of the dominant
cell in all MRs
containing the
current
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2242
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Measurement
Reports
[0,+)
Number
Indicates the
number of interfrequency MRs
of the
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance
[0,+)
km
Indicates the
distance
between the
dominant cell
and the current
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2243
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Co-Site
Yes, No
N/A
Field for
determining
whether a
neighboring cell
shares the same
site with a
specified cell
based on certain
algorithms.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Super-Distance
Yes, No or null
N/A
Indicates that
the distance
between a
specified cell
and its
neighboring cell
exceeds a
predefined
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2244
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Service Type of
Neighboring
Cell
Indoor, Outdoor
or null
N/A
Indicates the
service type of a
neighboring
GSM cell, such
as indoor
site,outdoor site
and unknow
service type.
Learning the
service type of
the neighboring
GSM cell helps
prevent
important
neighboring
cells from being
mistakenly
deleted.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
type of a
neighboring
cell. The options
are indoor and
outdoor.
Learning the
types of
neighboring
cells helps
prevent
important
neighboring
cells from being
mistakenly
deleted.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of
Times A
Neighboring
Cell Ranking
No.1 in MRs
[0,+)
Number
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2245
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Times A
Neighboring
Cell Ranking
No.2 in MRs
[0,+)
Number
Accumulated
number of times
the neighboring
cell ranking No.
1 in interfrequency MRs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Times A
Neighboring
Cell Ranking
No.3 in MRs
[0,+)
Number
Accumulated
number of times
the neighboring
cell ranking No.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2246
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Times A
Neighboring
Cell Ranking
No.4 in MRs
[0,+)
Number
Accumulated
number of times
the neighboring
cell ranking No.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Times A
Neighboring
Cell Ranking
No.5 in MRs
[0,+)
Number
Accumulated
number of times
the neighboring
cell ranking No.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2247
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Neighboring
Cell Ranking
No.6 to 12 in
MRs
[0,+)
Number
Accumulated
number of times
the neighboring
cell ranking No.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Remark
Empty or
Scrambling
codes may be
allocated
improperly
N/A
The Nastar
displays
information
indicating that
the allocation of
scrambling
codes is
inappropriate
when multiple
intra-frequency
cells have the
same
scrambling code
but different ID.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2248
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Whether to Use
N/A
N/A
Indicates
whether to
select the
current possible
neighboring cell
as the most
possible
neighboring cell
of the test cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
a possible
neighboring cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2249
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CI
[0,65535]
N/A
Indicates the
cell identity of a
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2250
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
One-Way/TwoWay
"One-Way",
"Two-Way",
"Unknown", "-"
N/A
Field for
identifying a
unidirectional
or bidirectional
neighbor
relationship
based on
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance
[0,+)
km
Indicates the
distance
between the
dominant cell
and the selected
possible
neighboring
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2251
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Co-Site
Yes, No
N/A
Field for
determining
whether a
neighboring cell
shares the same
site with a
specified cell
based on certain
algorithms.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Super-Distance
Yes, No or null
N/A
Indicates that
the distance
between a
specified cell
and its
neighboring cell
exceeds a
predefined
threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2252
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Relative Angle
of Possible
Neighboring
Cell
[0,360]
Indicates the
relative angle
between the
selected
possible
neighboring cell
and the
dominant cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Predicted Signal
Strength
N/A
dBm
Indicates the
signal strength
of the selected
possible
neighboring cell
based on the
dimensioning.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2253
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Get from config

Data
Yes, No
N/A
Indicates
whether the
selected
possible
neighboring cell
is obtained from
the
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Primary CPICH
Power
[-10,50]
dBm
Indicates
transmission
power of the
primary CPICH
in the selected
possible
neighboring
cell. It is
obtained from
the
configuration
data.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2254
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Neighboring
Cell Laps
2, 3, 9
N/A
If you cannot
obtain the
parameter value
from the
configuration
data, use the
default value 40
dBm.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
5.5 UMTS Pilot Pollution Analysis

The Nastar analyzes the calls of subscribers to identify cells where pilot pollution exists, cells
that cause interference, and severity of cell pollution. It can display the analysis results on a map
so that you can geographically locate pilot pollution problems. This reduces the drive test (DT)
time and improves the accuracy of problem locating.
5.5.1 Basics of UMTS Pilot Pollution Analysis

This section describes the basics of UMTS pilot pollution analysis, including the function,
technical specifications, and feature restrictions. Read this section before performing UMTS
pilot pollution analysis.
NOTE
Functions of UMTS Pilot Pollution Analysis

The Nastar provides the UMTS pilot pollution analysis function to analyze the calls of
subscribers. By analyzing the query reports, the Nastar identifies cells where pilot pollution
exists, cells that cause interference, and severity of cell pollution. It can display the analysis
results on a map so that you can geographically locate pilot pollution problems.
Issue 03 (2015-07-30)

2255
Nastar
Pilot pollution refers to the situation when excessive number of signals have similar strength in
the same coverage area of a CDMA network. Due to the complexity of radio network coverage,
it is hard to obtain ideal signal strength.
The following factors may cause pilot pollution:
l
Improper cell layout: This problem is usually caused by complicated geographical

conditions and inappropriate network design. It may result in coverage hole in some areas
and competitive signal coverage of multiple pilots in the other areas. This problem needs
to be resolved during network optimization.
Inappropriate site location selection or high antenna: High antenna enables signals to be
transmitted in a wide area but it also brings pilot pollution to neighboring cells. When the
antennas of neighboring NodeBs vary greatly in height, pilot pollution occurs due to
coverage overlap.
Incorrect pilot power settings: When NodeBs are distributed densely with small coverage
area each, pilot pollution may also occur if the pilot power is set to a large value.
High geographical location of covered objects: Pilot pollution occurs when a high building
is in the line-of-sight coverage area of multiple NodeBs.
Pilot pollution affects network performance in the following aspects:

l
Low Call Setup Success Rate (CSSR): The UE constantly reselects its serving cells because
it cannot stably camp on one cell. This usually causes call failure.
High call drop rate: Ping-pong hangovers occur frequently during a call because no pilot
is strong enough to become the dominant pilot. This increases the call drop rate.
Small system capacity: Pilot pollution causes strong interference. Therefore, the receive
sensitivity of the system is improved, and signals far away from the NodeB cannot be
received. As a result, the system capacity is reduced.
High block error rate (BLER): Pilot pollution causes high BLER that results in decreased
voice quality and data transmission rate.
You can troubleshoot pilot pollution in the following ways:

Reconfigure radio parameters, adjust antennas, reconfigure NodeBs, add or delete neighbor
relationships, reconfigure frequency and scrambling code parameters, add sites (micro cells for
instance), and add repeaters.
Generate a dominant pilot in areas where pilot pollution occurs. Because pilot pollution may be
caused by various factors, network optimization engineers need to troubleshoot pilot pollution
in a comprehensive manner. The Nastar analyzes pilot pollution based on the calls of subscribers
and displays the analysis results on a map. This helps network optimization engineers quickly
locate polluter cells and polluted cells, improving troubleshooting efficiency.
Function Principles
The Nastar uses the MRs on the NE side for pilot pollution analysis.
Issue 03 (2015-07-30)

2256
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00

2257
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

2258
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
analysi
s task
Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for UMTS Pilot Pollution Analysis

NOTE
Item
Execution type
One-time task

task
<= 10,000 cells
<= 50

analysis task
7 days
<= 5 minutes

analysis data
15 days

analysis data
15 days
5.5.2 Preparations for UMTS Pilot Pollution Analysis

Before starting a UMTS pilot pollution analysis task, you must check the operation rights and
the matching environment and prepare relevant data to ensure that the UMTS pilot pollution
Issue 03 (2015-07-30)

2259
Nastar
analysis task is executed normally. Read this section before performing UMTS pilot pollution
analysis.

l
Check that you have applied the license for UMTS pilot pollution analysis and the license
is valid.
Check that the login user has the rights to subscribe to the source data for pilot pollution
analysis.
contact the administrator to enable the data source switch.
Check that the login user has the rights to create a UMTS pilot pollution analysis task.

Configuration Data
Data.
The engineering parameters for a specific area are used for the geographic observation of the
analysis result. You do not need to prepare the engineering parameters if the geographic display
of the analysis result is not required.
Issue 03 (2015-07-30)

2260
Nastar
Map Files (Optional)

5.5.3 Process of UMTS Pilot Pollution Analysis

This section describes the UMTS pilot pollution analysis process.
l
Prerequisites
Procedure
Prerequisites
The UMTS configuration data and engineering parameters have been imported into the Nastar
database. For details, see 5.5.2 Preparations for UMTS Pilot Pollution Analysis.
Procedure
Issue 03 (2015-07-30)

2261
Nastar
Issue 03 (2015-07-30)

2262
Nastar
Table 5-11 Description of UMTS pilot pollution analysis process

No.
Proced
ure
Description
Reference
(1)
Check
the
integrit
y of
UMTS
pilot
pollutio
n
analysis
data

3.6 Checking the

Integrity of
Analysis Data
Procedure:
1. Set Data Type to UMTS Pilot Pollution Analysis
Data.
4. Click Query.
of the window.
analysis task.
performing (2).
NOTE
(2)
Subscri
be to
pilot
pollutio
n
analysis
data
(basic)
NOTE
requirements. You are advised to contact the administrator
who has subscription permission to turn on the data source
switch.
3.5 Subscribing
to Analysis Data

Procedure:
click the UMTS tab.
click Set.
the data source switch of Pilot Pollution Analysis
Data to ON.
Modification.
5. Click Confirm.
Check that the data source switch is open based on
the information in the Log Info area.
Issue 03 (2015-07-30)

2263
Nastar
No.
Proced
ure
Description
Subscri
be to
pilot
pollutio
n
analysis
data
(applica
tion)

Reference
Procedure:
click the UMTS tab.
3. On the Pilot Polluting Analysis tab page, click
ON.
4. In the displayed Pilot Pollution Analysis
Parameters Setting dialog box, set the related
parameters.
5. Click Confirm.
For the parameter description, see Subscription
Task Parameters.
Check
the
integrit
y of
UMTS
pilot
pollutio
n
analysis
data

Procedure:
3.6 Checking the

Integrity of
Analysis Data
1. Set Data Type to UMTS Pilot Pollution Analysis

Data.
4. Click Query.
of the window.
analysis task.
Issue 03 (2015-07-30)

2264
Nastar
No.
Proced
ure
Description
Reference
(3)
Create a
UMTS
pilot
pollutio
n
analysis
task

UMTS Pilot Pollution Analysis.
3.7 Creating an
Analysis Task
Procedure:
1. Double-click UMTS Pilot Pollution Analysis.
Next.
NEs. Then, click Next.
5. Click Finish.
(4)
View
UMTS
pilot
pollutio
n
analysis
results

task.
3.8 Querying
Analysis Results
Procedure:
1. Right-click the result record and choose View
2. In the displayed UMTS Pilot Pollution Analysis
Task window, view the analysis results about this
record.
For details about the analysis result interface, see
5.5.4 Interface Description: UMTS Pilot
Pollution Analysis.

Basic Subscription
Issue 03 (2015-07-30)
Parameter
Description
Pilot Pollution
Analysis Data
(MR)
You can click

2265
Nastar
Parameter
Description
1st best CPICH

RSCP - 4st best
CPICH RSCP
(dB)<Y
Pilot pollution occurs when the following conditions are met:

l In all the active set, monitor set and detected set, there are more than
three pilots the difference between whose RSCP and the RSCP of the
strongest pilot is less than the threshold value.
l The RSCP of the four strongest pilots is more than or equal to the
threshold value.
CS service: The Nastar obtains data only when:
l The difference between the RSCP of the strongest pilot and that of the
fourth strongest pilot is less than Y.
l The RSCP of the four strongest pilots is more than or equal to M.
PS service: The Nastar obtains data only when:
l The difference between the RSCP of the strongest pilot and that of the
fourth strongest pilot is less than Y.
l The RSCP of the four strongest pilots is more than or equal to N.
Y indicates the difference between the RSCP of the strongest pilot and that
of the fourth strongest pilot. The default value is 5.
CS RSCP (dBm)
>=M
M indicates the minimum threshold value when pilot pollution occurs in

the CS service domain. The default value is -95.
PS RSCP (dBm)
>=N
N: indicates the minimum threshold value when pilot pollution occurs in

the PS service domain. The default value is -95.

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

Issue 03 (2015-07-30)

2266
Nastar
NE information
Parameter
Description
Select NE(s)

NOTE

Parameter
Description
Duration
Delay
immediately.
Execute on
5.5.4 Interface Description: UMTS Pilot Pollution Analysis

This section describes the interface that displays the results of UMTS pilot pollution analysis.
this interface.
Portal
Use either of the following methods to open the interface that displays UMTS pilot pollution
analysis results:
l
Select an executed UMTS pilot pollution analysis task and double-click a result record in
Select an executed UMTS pilot pollution analysis task, right-click a result record in the
Task Result area, and choose View Analysis Result from the shortcut menu.
Interface List
The interface contains a polluted cell overview table, a polluter cell overview table, and an
analysis result geographic display area.
Issue 03 (2015-07-30)

2267
Nastar
When you open the result analysis interface for the first time, the interface displays the
polluted cell overview table and polluter cell details table by default. For details, see
Interface 1.
After you click

, the interface switches to displaying the polluter cell overview table
and polluted cell details table. For details, see Interface 2.
After you click

, the interface switches to geographically displaying polluter cells and
polluted cells on a map. For details, see Map Interface.
Interface 1
The pilot pollution analysis results are displayed in tables, including the polluted cell overview
table and polluter cell details table. Figure 5-21 shows this interface.
Figure 5-21 Interface 1 for UMTS pilot pollution analysis results
No.
Name
Description
Button area
Provides the function of switching the information in Area 2 and 3.

After you click the switching button, Area 2 will display the polluter
cell overview table and Area 3 will display the polluted cell details
table. For details, see Interface 2.
Issue 03 (2015-07-30)

2268
Nastar
No.
Name
Description
Overview of
polluted cells
Displays information about all polluted cells involved in this task.

By default, the information in this table is displayed according to
Total Number of Polluted Events in descending order.
You can filter, resort and export this table:
l Click the column header and choose a filtering item from the
drop-down box to display the table in a filtered way.
l Click the
l 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 overview information about all polluted cells.
3
List of
polluter cells
Displays all neighboring cells that have polluted a certain polluted

cell in Area 2. This area is displayed after you select a polluted cell
in Area 2.
You can resort and export this table:
l Click the

Nastar will save information about all neighboring cells that have
polluted a certain polluted cell.
Interface 2
After you click the switching button, the interface switches to displaying the polluter cell
overview table and polluted cell details table. Figure 5-22 shows this interface.
Issue 03 (2015-07-30)

2269
Nastar
Figure 5-22 Interface 2 for UMTS pilot pollution analysis results
No.
Name
Description
Overview of
polluter cells
Displays information about all polluter cells involved in this task. By

default, the information in this table is displayed according to
Number of Pollution Events in descending order.
l Click the

Nastar will save the overview information about all polluter cells.
Issue 03 (2015-07-30)

2270
Nastar
No.
Name
Description
List of
polluted cells
Displays all neighboring cells that have been polluted by a certain

polluter cell in Area 4. This area is displayed after you select a
polluter cell in Area 4.
l Click the

Nastar will save information about all neighboring cells that have
been polluted by a certain polluter cell.
Map Interface
After you click
in the upper left corner of the Nastar client, the map interface (Geographic
Observation) is displayed. Figure 5-23 shows this interface.
Figure 5-23 Map interface for UMTS pilot pollution analysis results
Issue 03 (2015-07-30)
No.
Name
Description
Button area

2271
Nastar
No.
Name
Description
Navigation
tree
Site Layer: When UMTS is selected, the information of UMTS sites

is displayed in Area 3.
NOTE
in area 3.
3
Legend area

click
Geographic
display area
in the button area.

l After you select a polluted cell in the polluted cell overview table,
the map interface displays this cell and all the neighboring cells
that have polluted this cell in different colors.
l After you select a polluter cell in the polluter cell overview table,
the map interface displays this cell and all the neighboring cells
that have been polluted by this cell in different colors.
Information
area
Displays related information about a cell after you select the cell. If
no engineering parameter has been imported for this cell, a message
is displayed in this area.
5.5.5 Parameters for Viewing UMTS Pilot Pollution Analysis

Results
This section describes the parameters for viewing UMTS pilot pollution analysis results. You
can refer to the description when querying UMTS pilot pollution analysis results.
Issue 03 (2015-07-30)

2272
Nastar
Overview Polluted Cell data

Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
a polluted cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of a polluted
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2273
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
polluted cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a polluted
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2274
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
DownLink
ARFCN
N/A
N/A
Indicates the
UTRAN
Absolute Radio
Frequency
Channel
Number
(UARFCN) on
the downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
UTRAN is an
abbreviation for
Universal
Terrestrial
Radio Access
Network.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluted cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2275
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RSCP
[-116,-25]
dBm
Indicates the
average pilot
signal reception
of polluted cells
functioned as
dominant cells.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
Polluted Events
[0,+)
Number
Indicates the
total number of
pollution events
for a polluted
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2276
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
Polluted Events
[0,+)
Number
Total number of
measurement
reports.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number
Of Polluting
Neighboring
Cells
[0,+)
Number
Indicates the
total number of
cells that bring
pollution to the
current cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2277
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CS Average
ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluted cell in
CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CS Average
RSCP
[-116,-25]
dBm
Indicates the
average receive
signal strength
of pilot signals
of a polluted cell
in CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2278
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CS Total
Number of
Polluted Events
[0,+)
Number
Indicates the
total number of
pollution events
for a polluted
cell in CS
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CS Total
Number of
Measurement
Reports
[0,+)
Number
Total number of
measurement
reports in CS
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2279
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PS Average
ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluted cell in
PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PS Average
RSCP
[-116,-25]
dBm
Indicates the
average receive
signal strength
of pilot signals
of a polluted cell
in PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2280
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PS Total
Number of
Polluted Events
[0,+)
Number
Indicates the
total number of
pollution events
for a polluted
cell in PS
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PS Total
Number of
Measurement
Reports
[0,+)
Number
Total number of
measurement
reports in PS
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2281
Nastar
List of Polluting Cells

Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
a polluter cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of a polluted
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2282
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
polluter cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l If the current
polluter cell
is a defined
neighboring
cell of the
current
polluted cell,
the name of a
defined
neighboring
cell is
displayed in
this field.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l If the current
polluter cell
is an
undefined
neighboring
cell of the
current
polluted cell,
the name of a
possible
neighboring
cell is
displayed in
this field.
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l If the system
cannot find
the detailed
information
about the
cell
correspondi
ng to the PSC of the
polluted cell,
Unknown is
displayed in
this field.
Issue 03 (2015-07-30)

2283
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a polluting
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Is Neighbour
Define
Defined
neighboring
cell, Undefined
neighboring cell
N/A
Indicates the
polluting cell is
whether a
defined
neighboring cell
or not.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2284
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluter cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RSCP
[-116,-25]
dBm
Indicates the
average pilot
signal reception
of polluted cells
functioned as
dominant cells
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2285
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number Of
Polluting
Events
[0,+)
Number
Indicates the
total number of
pollution events
that the current
cell is polluted
by polluter cells.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CS Average
ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluter cell in
CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2286
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CS Average
RSCP
[-116,-25]
dBm
Indicates the
average receive
signal strength
of pilot signals
of a polluter cell
in CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CS Number Of
Polluting
Events
[0,+)
Number
Indicates the
total number of
pollution events
that the current
cell is polluted
by polluter cells
in CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2287
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PS Average
ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluter cell in
PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PS Average
RSCP
[-116,-25]
dBm
Indicates the
average receive
signal strength
of pilot signals
of a polluter cell
in PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2288
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PS Number Of
Polluting
Events
[0,+)
Number
Indicates the
total number of
pollution events
that the current
cell is polluted
by polluter cells
in PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Distance
[0,+)
km
Indicates the
distance
between a
polluted cell and
a polluter cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2289
Nastar
Overview Polluting Cell data

Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
a polluter cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of a polluting
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2290
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
polluter cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a polluter cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2291
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
DownLink
ARFCN
N/A
N/A
Indicates the
UARFCN
Absolute Radio
Frequency
Channel
Number
(UARFCN) on
the downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluter cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2292
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RSCP
[-116,-25]
dBm
Indicates the
average receive
signal strength
of pilot signals
of a polluter cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total Number of
Polluting
Events
[0,+)
Number
Indicates the
total number of
pollution events
that the polluter
cell brings
pollution to
other cells.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2293
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number
Of Polluted
Neighboring
Cells
[0,+)
Number
Indicates the
total number of
cells that is
polluted by the
current cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CS Average
ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluter cell in
CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2294
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CS Average
RSCP
[-116,-25]
dBm
Indicates the
average receive
signal strength
of pilot signals
of a polluter cell
in CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CS Total
Number of
Polluting
Events
[0,+)
Number
Indicates the
total number of
pollution events
that the polluter
cell brings
pollution to
other cells in CS
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2295
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PS Average
ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluter cell in
PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PS Average
RSCP
[-116,-25]
dBm
Indicates the
average receive
signal strength
of pilot signals
of a polluter cell
in PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2296
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PS Total
Number of
Polluting
Events
[0,+)
Number
Indicates the
total number of
pollution events
that the polluter
cell brings
pollution to
other cells in PS
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2297
Nastar
List of Polluted Cells

Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
[0,+)
N/A
Indicates the ID
of the RNC that
a polluted cell
belongs to.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of a polluted
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2298
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Name
1 to 64
characters
N/A
Indicates the
name of a
polluted cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a polluted
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2299
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Is Neighbour
Define
Defined
neighboring
cell, Undefined
neighboring cell
N/A
Indicates the
polluted cell is
whether a
defined
neighboring cell
or not.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluted cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2300
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RSCP
[-116,-25]
dBm
Indicates the
average pilot
signal reception
of polluted cells
functioned as
dominant cells.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number Of
Polluted Events
[0,+)
Number
Indicates the
total number of
pollution events
that the polluter
cell brings
pollution to
other cells.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2301
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CS Average
ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluted cell in
CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CS Average
RSCP
[-116,-25]
dBm
Indicates the
average receive
signal strength
of pilot signals
of a polluted cell
in CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2302
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CS Total
Number of
Polluted Events
[0,+)
Number
Indicates the
total number of
pollution events
that the polluted
cell is polluted
by the current
polluter cell in
CS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PS Average
ECNO
[-24,0]
dB
Indicates the
average receive
signal quality of
pilot signals of a
polluted cell in
PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2303
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PS Average
RSCP
[-116,-25]
dBm
Indicates the
average receive
signal strength
of pilot signals
of a polluted cell
in PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PS Total
Number of
Polluted Events
[0,+)
Number
Indicates the
total number of
pollution events
that the polluted
cell is polluted
by the current
polluter cell in
PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2304
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Distance
[0,+)
km
Indicates the
distance
between a
polluted cell and
a polluter cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
5.6 UMTS Uplink Interference Analysis

The Nastar analyzes received total wideband power(RTWP) data reported by NodeBs to help
you troubleshoot signal interference on the network. The Nastar also analyzes signal strength of
uplink main and diversity antennas to help you locate antenna problems.
5.6.1 Basics of UMTS Uplink Interference Analysis

This section describes the basics of UMTS uplink interference analysis, including the function,
technical specifications, and feature restrictions. Read this section before performing UMTS
uplink interference analysis.
NOTE
Functions of UMTS Uplink Interference Analysis

The Nastar provides the UMTS uplink interference analysis function to analyze the RTWP data
reported by NodeBs. During network optimization, this function can be used to identify
interference on the network. In addition, this function allows you to analyze the average uplink
interference strength of the diversity and main antennas so as to locate antenna problems. During
network assurance, this function can be used to evaluate the interference level of the network.
Issue 03 (2015-07-30)

2305
Nastar
Uplink interference degrades network performance as it causes high call drop rates, frequent
handovers, and network congestion. When uplink interference occurs, the call quality, network
coverage, and network capacity deteriorate. If interference and load are not clearly identified,
load control cannot function properly.
With the uplink interference analysis function, the Nastar analyzes RTWP data reported by
NodeBs to preliminarily locate NodeBs that are interfered. The Nastar provides an RTWP trend
chart for you to view RTWP trends of selected cells to determine whether the average
interference strength is proper for the main and diversity antennas and determine the interference
characteristics. You can also view the distribution chart of differences between the main and
diversity antennas to determine whether the main and diversity antennas are connected properly.
After creating an uplink interference analysis task, the Nastar will perform uplink interference
analysis on the selected cells. The Nastar displays analysis results in a line chart. The line chart
uses different colors to show the main and diversity interference strength at each time point and
trends in the interference strength over time.
Function Principles
The Nastar uses the scanned uplink frequency data on the U2000/M2000 for UMTS uplink
interference analysis.
Issue 03 (2015-07-30)

2306
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
applicat
ion data
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

eSAU.
Collect
scanned
uplink
frequen
cy data
eS
AU
U20
00/
M20
00
The eSAU delivers data processing requests to NEs

through the U2000/M2000, requesting the NEs to report
scanned uplink frequency data to the U2000/M2000.
Upload
scanned
uplink
frequen
cy data
U2
000
/
M2
000
Nast
ar
Serv
er
The Nastar periodically scans the directories on the

the Nastar can obtain data from the U2000/M2000
immediately once data is reported.
2.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

3.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.

2307
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
4. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for UMTS Uplink Interference Analysis

NOTE
Item
Execution type
One-time task
<= 4000 cells
<= 50

task
7 days
<= 15 minutes

analysis data
15 days

analysis data
15 days
5.6.2 Preparations for UMTS Uplink Interference Analysis

Before starting a UMTS uplink interference analysis task, you must check the operation rights
and the matching environment and prepare relevant data. Read this section before performing
UMTS uplink interference analysis.
Issue 03 (2015-07-30)

2308
Nastar

l
Check that you have applied the license for UMTS uplink interference analysis and the
license is valid.
Check that the login user has the rights to subscribe to the source data for UMTS uplink
interference analysis, create UMTS uplink interference analysis tasks, and perform
operations on the NEs involved in these tasks.

Configuration Data
Data.

l
NOTE
When the U2000/M2000 version is V200R008C03SPC130 or earlier, the Nastar cannot

automatically obtain RTWP data. You need to manually obtain and import the RTWP data into the
Nastar. For detailed operations, see section Commissioning the Function of Obtaining the Data
> Preparing for Obtaining Data > Preparing for Obtaining Data(UMTS) > Obtaining the
RTWP Data Manually in Nastar System Commissioning Guide.
5.6.3 Process of UMTS Uplink Interference Analysis

This section describes the process of UMTS uplink interference analysis and the steps of each
operation procedure.
l
Prerequisite
Procedure
Issue 03 (2015-07-30)

2309
Nastar
Prerequisite
UMTS configuration data has been imported into the Nastar database. For detailed operations,
see 5.6.2 Preparations for UMTS Uplink Interference Analysis.
Procedure
Issue 03 (2015-07-30)

2310
Nastar
Table 5-13 Description of the UMTS uplink interference analysis process

No.
Proced
ure
Description
Reference
(1)
Check
the
integrit
y of
UMTS
uplink
interfer
ence
analysis
data

3.6 Checking the

Integrity of
Analysis Data
Procedure:
1. Set Data Type to UMTS Uplink Interference
Analysis Data.
4. Click Query.
of the window.
analysis task.
performing (2).
NOTE
(2)
Subscri
be to
uplink
interfer
ence
analysis
data
(applica
tion)

3.5 Subscribing
to Analysis Data
Procedure:
click the UMTS tab.
3. On the Uplink Interference Analysis tab page,
click ON.
4. In the displayed Uplink Interference Analysis
Parameters Settings dialog box, set data
subscription parameters.
Task Parameters.
5. Click .
Issue 03 (2015-07-30)

2311
Nastar
No.
Proced
ure
Description
Check
the
integrit
y of
UMTS
uplink
interfer
ence
analysis
data

Reference
Procedure:
1. Set Data Type to UMTS Uplink Interference
Analysis Data.
4. Click Query.
of the window.
analysis task.
(3)
Create a
UMTS
uplink
interfer
ence
analysis
task

UMTS Uplink Interference Analysis.
Procedure:
1. Double-click UMTS Uplink Interference
Analysis.
Next.
NEs. Then, click Next.
l For detailed
operations, see
3.7 Creating
an Analysis
Task.
l For details
about the
parameters,
see Analysis
Task
Parameters.

5. Click Finish.
Issue 03 (2015-07-30)

2312
Nastar
No.
Proced
ure
Description
Reference
(4)
View
UMTS
uplink
interfer
ence
analysis
results

task.
l For detailed
operations, see
3.8 Querying
Analysis
Results.
Procedure:
l For details
about the
analysis result
interface, see
5.6.4
Interface
Description:
UMTS
Uplink
Interference
Analysis.

2. In the displayed UMTS Uplink Interference
Analysis window, view the analysis results about
this record.

Parameter
Description
Meas
ure
Task
Task name
Value range:
l Characters not allowed: ` ~ ! @ # $ % ^ & * ( ) + { } [ ] \ / | ;
':,.?<>"
l The name is unique and case-sensitive. It cannot be left empty.
Start time
Start time of a measurement task.

The default time is the current system time on the hour.
End time
End time of a measurement task.

The end time cannot be later than the start time more than 3 days.
Para
meter
Setti
ng
Issue 03 (2015-07-30)
NE list
Select the NEs to be delivered the application subscription task.

Because of the limitation of the U2000/M2000 RTWP data
collection task, you only can select up to 60 NodeBs.
RTWP Data
Stat Type
Statistical type of the RTWP data. This parameter specifies whether

the Nastar obtains the maximum or average RTWP values to meet
analysis requirements.

2313
Nastar

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Parameter
Description
Select NE(s)

NOTE

Parameter
Description
Duration
Delay
immediately.
Execute on
Issue 03 (2015-07-30)

2314
Nastar
5.6.4 Interface Description: UMTS Uplink Interference Analysis

This section describes the interface that displays the results of UMTS 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 UMTS uplink interference
analysis results:
l
Select an executed UMTS uplink interference analysis task and double-click a result record
Select an executed UMTS uplink interference analysis task, right-click a result record in
Interface
The uplink interference analysis results are displayed in one table and two charts: table of
measurement cells, trend chart of interference strength, and bar chart of interference strength
differences. Figure 5-26 shows the interface.
Figure 5-26 Interface for UMTS uplink interference analysis results
Issue 03 (2015-07-30)
N
o.
Name
Description
Cell
information
table
Displays the basic information about all measurement cells involved in

an analysis task.
Right-click on the table and choose Save As from the shortcut menu.
The Nastar will save the analysis results in this table as a file.

2315
Nastar
N
o.
Name
Description
Line chart of
interference
strength
Displays trends in the main and diversity interference strength of a

selected cell over a specified time period.
l The upper part displays the title of the line chart and the lower part
displays the legend.
l The horizontal coordinate represents the time period. The RTWP
data is summarized every one minute.
l The vertical coordinate represents the interference strength values.
l You can hold down Ctrl while rotating the mouse wheel to zoom in
or out on the line chart, or right-click on the line chart and choose
Zoom In or Zoom Out or Auto Range to adjust the line chart size.
You can also right-click on the line chart and choose an option from
the shortcut menu to query, save, or print the line chart.
Bar chart of
interference
strength
differences
Displays the distribution of differences between the main and diversity

interference strength of the selected cell. The Nastar first calculates the
interference strength difference at each time point and then displays the
percentage of each difference in the total number of differences. The
bar chart in this area is displayed accordingly with the line chart in area
1.
5.6.5 Parameters for Viewing UMTS Uplink Interference Analysis

Results
This section describes the parameters for viewing UMTS uplink interference analysis results.
You can refer to the description when viewing UMTS uplink interference analysis results.
Issue 03 (2015-07-30)

2316
Nastar
Parameter
Parameter
Range
Unit
Description
Supported
Solution
Version
RNC ID
N/A
N/A
Indicates the ID
of an RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RNC Name
1 to 64
characters
N/A
Indicates the
name of an
RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2317
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell ID
[0,65535]
N/A
Indicates the ID
of a cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of a cell,
for example,
Cell_1.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2318
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
P-SC
[0,511]
N/A
Indicates the
primary
scrambling code
of a cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Main Average
Strength
[-120,-47]
N/A
Indicates the
average value of
the interference
strength of main
antennas.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2319
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Diversity
Average
Strength
[-120,-47]
N/A
Indicates the
average value of
the interference
strength of
diversity
antennas.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Difference
(MainDiversity)
N/A
N/A
Indicates the
value calculated
by dividing the
sum of the
signal
differences
between the
main and
diversity
antennas at each
time point in the
selected time
range by the
total number of
time points.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2320
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Standard
Deviation
(MainDiversity)
N/A
N/A
Indicates the
square root of
the value
calculated
through the
following steps:
Firstly,
calculate the
average of the
signal
differences
between the
main and
diversity
antennas at
every time point
in a selected
time range.
Secondly,
subtract the
average from
the signal
differences
between the
main and
diversity
antennas
separately.
Thirdly, divide
the sum of the
squares of the
values obtained
in the second
step by the total
number of time
points.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
5.7 UMTS Terminal Analysis

This section describes the UMTS terminal inventory analysis tasks, including the management
of terminal inventory analysis tasks and the query and export of terminal inventory analysis
reports. The system analyzes the KPIs in the call records of terminal users. This function helps
operators identify the terminals with poor performance in the UMTS network, therefore
encouraging terminal manufacturers to improve the terminals with poor performance and guide
subscribers to purchase terminals with good performance. In this case, subscribers can obtain
Issue 03 (2015-07-30)

2321
Nastar
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.
5.7.1 Basics of UMTS Terminal Analysis

This section describes the basics of UMTS terminal analysis, including the terminal analysis
function, technical specification, and feature restriction. The basic knowledge helps you perform
the operations related to UMTS terminal analysis. Read this section before performing UMTS
terminal analysis.
NOTE
Functions of UMTS Terminal Analysis

The Nastar performs terminal analysis based on the call records in the UMTS network to locate
and solve network problems caused by terminals.
Call records of subscribers can reflect the access performance, service retainability, and intraRAT handover performance of terminals. KPIs related to delay, service quality, and traffic can
reflect the terminal capability.
The Nastar terminal analysis provides the following functions:
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 followup network building and marketing strategies.
Terminal Ability Evaluate: The Nastar evaluates the proportion of various terminals
supported in the network to provide a basis for telecom operators to develop the network
that supports a certain feature. In addition, the Nastar calculates the distribution of
terminals, which support LTE and U900 frequency bands and have gained access to a
UMTS network, on each frequency band, and the voice traffic and data traffic generated
on each frequency band. This provides guidance for telecom operators to deploy new LTE
and UMTS900 networks, and helps accurately estimate the volume of traffic that the new
LTE and UMTS900 networks can offload from the existing UMTS network.
Terminal Inventory Evaluate: Use the cell-level aggregation function and bearer-level
aggregation function based on KPIs. Based on aggregation results of cell-level KPIs, you
can analyze the actual status of each cell and queried results to determine whether the poor
terminal performance is caused by a terminal defect or is affected by special cells (for
example, GSM cells neighboring a GSM network). You can also analyze the query results
and bearers together based on the aggregated bearer-level KPIs to identify the bearer types
that terminals on the live network fail to support. Bearer types include AMR, HSPA+,
HSDPA, and others.
Issue 03 (2015-07-30)

2322
Nastar
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 and MR data on the NE side.
NOTE
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.
Issue 03 (2015-07-30)

2323
Nastar

User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

2324
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for UMTS Terminal Analysis

of analysis time.
NOTE
Issue 03 (2015-07-30)
Item
Execution type
One-time task

2325
Nastar
Item

analysis task
Number of allowed
analysis tasks
<= 50

one analysis task
7 days

task
l <= 75 minutes (for terminal inventory analysis)

15 days

15 days
l <= 25 minutes (for terminal geographic observation)
5.7.2 Preparations for UMTS Terminal Analysis

Before running a UMTS terminal analysis task, verify user rights and related environment
information and obtain related data, ensuring that the task is properly executed. Read this section
before performing UMTS terminal analysis.

l
Ensure that the License for UMTS terminal analysis is applied and the License is valid.
The license for UMTS terminal inventory analysis is required for viewing the functions
of UMTS terminal penetration analysis, UMTS terminal ability analysis, and UMTS
terminal performance analysis.
The license for UMTS terminal geographic display is required for viewing the function
of UMTS terminal geographic display.
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 and right to perform operations
on terminal analysis tasks.

Terminal information
Terminal information indicates the IMEI-TAC, vendor, terminal model, chip model, terminal
type, terminal technology, and data transfer information. After creating terminal information as
Issue 03 (2015-07-30)

2326
Nastar
required, the Nastar creates the management record for terminals to facilitate follow-up 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.
Data.
NOTE
You are advised to perform terminal analysis with the granularity of a day to ensure the validity and

The engineering parameters for a specific area are used for the geographic observation of the
analysis result. You do not need to prepare the engineering parameters if the geographic display
of the analysis result is not required.
Map files (Optional)
Issue 03 (2015-07-30)

2327
Nastar
Checking the Analysis Environment

l
Preparing for Obtaining Data > Preparing for Obtaining Data(UMTS) > Turning On
the User Identity Information Reporting Switch (UMTS) in Nastar Commissioning
Guide.
5.7.3 Process of UMTS Terminal Analysis

This section describes the process of UMTS terminal analysis and each procedure in the process.
l
Prerequisites
Process
Prerequisites
The UMTS configuration data and UMTS engineering parameters have been imported to the
Nastar database. The terminal type has been configured on the Nastar. For details, see 5.7.2
Preparations for UMTS Terminal Analysis.
Process
Issue 03 (2015-07-30)

2328
Nastar
Issue 03 (2015-07-30)

2329
Nastar
Table 5-15 Description of the UMTS terminal analysis process

N Procedure
o
.
Description
Reference
(
1
)

3.6 Checking the

Integrity of
Analysis Data
Check
whether
analysis
data is
integrated?
Procedure:
1. Set Data Type to UMTS Terminal Inventory
Analysis Data or UMTS Terminal Geographic
Observation Data.
NOTE
l Only UMTS Terminal Inventory Analysis Data is
required to analyze terminal penetration rate,
l Only UMTS Terminal Geographic Observation
geographically.

4. Click Query.
the window.
analysis task.
performing (2).
NOTE
Issue 03 (2015-07-30)

2330
Nastar
N Procedure
o
.
Description
Reference
(
2
)

3.5.2 Basic
Subscription of
Analysis Data
Subscribe
to analysis
data
(basic).
Procedure:
click the UMTS tab.
navigation tree.
click Set.
the switch of Terminal Analysis Data(CHR) and
Terminal Analysis Data(MR) to ON.
If terminal geographic display is not required, you
do not need to turn on the Terminal Analysis Data
(MR) switch.
5. Click Confirm.
Info area.
Issue 03 (2015-07-30)

2331
Nastar
N Procedure
o
.
Subscribe
to analysis
data
(applicatio
n).
Description
Reference

3.5.3
Application
Subscription of
Analysis Data
Procedure:
click the UMTS tab.
navigation tree.
4. In the displayed Terminal Analysis Parameter
Settings dialog box, click the Basic Parameter
Settings tab. On the displayed Basic Parameter
Settings tab page, select the analysis functions you
want to enable, and set exception thresholds.
5. Optional: Click the Select Frequency Band tab.
On the displayed Select Frequency Band tab
page, select the frequency bands on which you
want to perform terminal refarming analysis.
NOTE
You are allowed to select a maximum of 10 frequency
bands for each RAT during data subscription.
6. Click Confirm.
Verify that data subscription is successfully turned
Info area.
For details about the parameters related to application
subscription, see Subscription Task Parameters.
Issue 03 (2015-07-30)

2332
Nastar
N Procedure
o
.
Check
whether
analysis
data is
integrated?
Description
Reference

3.6 Checking the

Integrity of
Analysis Data
Procedure:
1. Set Data Type to UMTS Terminal Inventory
Analysis Data or UMTS Terminal Geographic
Observation Data.
NOTE
l Only UMTS Terminal Inventory Analysis Data is
required to analyze terminal penetration rate,
l Only UMTS Terminal Geographic Observation
geographically.

4. Click Query.
the window.
analysis task.
Issue 03 (2015-07-30)

2333
Nastar
N Procedure
o
.
Description
Reference
(
3
)
Entry: In the left navigation tree of the Analysis Task

Terminal Analysis > UMTS Terminal Analysis.
l For detailed
operations,
see 3.7
Creating an
Analysis
Task.
Create an
analysis
task.
Procedure:
1. Double-click the UMTS Terminal Analysis node.
analyzed. You can select NEs by RNC or Cell
Group.
Abilities tab page, select terminal capabilities for
analysis. The Nastar calculates numbers and
percentages of terminals supporting the
capabilities in each raster.
l For parameter
description,
see Analysis
Task
Parameters.

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.
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.
Parameters.
Issue 03 (2015-07-30)

2334
Nastar
N Procedure
o
.
Description
Reference
(
4
)

task.
l For details,
see 3.8
Querying
Analysis
Results.
Procedure:
l For details on
the
description
about the
window for
displaying
task results,
see 5.7.4
Interface
Description:
UMTS
Terminal
Analysis.
View
analysis
results.

2. In the displayed UMTS Terminal Analysis
Task window, view the UMTS terminal analysis
result.
(
5
)
Export
analysis
reports.

Procedure:
3. Click Complete.
l For details,
see 3.10
Exporting
Analysis
Reports.
l For details on
the
description
about the
window for
displaying
task results,
see 5.7.4
Interface
Description:
UMTS
Terminal
Analysis.

Basic Subscription
Issue 03 (2015-07-30)

2335
Nastar
Parameter
Description
Terminal
Analysis Data
(CHR)
Switch for enabling or disabling the reporting of CHR data. You can retain
You can click
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.
reported CHR data. For details, see the SET UEVENTCHRCTRL
Terminal
Analysis Data
(MR)
You can click
Application Subscription-Basic Parameter Settings
Issue 03 (2015-07-30)
Parameter
Description
Range
Recomm
ended
Value
Enable Terminal
Features
Indicates the type of terminal analysis, such as

Terminal Inventory Analysis, and Terminal
Geographic Analysis. You are allowed to
select multiple terminal analysis types.
NA
NA

2336
Nastar
Parameter
Termina
l
Threshol
d Setting
Issue 03 (2015-07-30)
Description
Range
Recomm
ended
Value
Over
long
RRC
Setu
p
Dela
y
Thre
shold
(Non
Servi
ce)
(s)
Indicates the threshold for extra long RRC

setup delay when a terminal performs cell
reselection, cell change commands,
registration or separation.
[0,255]
>= 10
Over
long
RRC
Setu
p
Dela
y
Thre
shold
(Serv
ice)
(s)
Indicates the threshold for extra long RRCconnection setup when a terminal accesses
services.
[0,255]
>= 10
Over
long
RAB
Setu
p
Dela
y
Thre
shold
(s)
Indicates the threshold for extra long RABconnection setup when a terminal accesses
services. RAB setup delay indicates the
duration from the RAB ASSIGNMENT
REQUEST message to the RAB
ASSIGNMENT RESPONSE message.
[0,255]
>= 10
RRC setup delay indicates the duration from

the RRC Connection Request message to the
RRC Connection Setup Complete message.
RRC setup delay indicates the duration from

the RRC Connection Request message to the
RRC Connection Setup Complete message.

2337
Nastar
Parameter
Issue 03 (2015-07-30)
Description
Range
Recomm
ended
Value
Over
long
Inter
Syste
m
Outg
oing
Hand
over
Dela
y
Thre
shold
(s)
Indicates the expiration threshold for handing

over a terminal to other systems such as GSM.
[0,255]
>= 10
Over
long
Inter
Syste
m
Inco
ming
Hand
over
Dela
y
Thre
shold
(s)
Indicates the expiration threshold for handing

over a terminal from other systems such as
GSM to the UMTS.
[0,255]
>= 10
AM
R
Short
Call
Thre
shold
(s)
Indicates the threshold for a very short call

duration when a terminal performs a voice call.
[0,255]
<= 1
VP
Short
Call
Thre
shold
(s)
Indicates the threshold for a very short call

duration when a terminal performs a VP call.
[0,255]
<= 1
The AMR call duration indicates the duration

from the RAB ASSIGNMENT REQUEST
message to the IU RELEASE COMMAND
message.
The AMR call duration indicates the duration

from the RAB ASSIGNMENT REQUEST
message to the IU RELEASE COMMAND
message.

2338
Nastar
Parameter
Abn
orma
l SQI
Thre
shold
(s)
Description
Range
Recomm
ended
Value
Indicates the threshold for SQI exceptions

when a terminal performs a voice call. This
indicator is calculated for only the AMR
service.
[0,500]
<= 300
The SQI equals to the score for a voice service.

Good indicates excellent. Accept indicates
qualified. Bad indicates not qualified. The
threshold for each level is determined by the
RNC configuration. the default configuration
is as follows: the score lower than 200 is Bad
and the score higher than 313 is Good.
Application Subscription-Select Frequency Band

Tab
Page
Freque
ncy
Band
Name
Uplink(UL) Operating
band BS receive UE
transmit
Downlink(DL) Operating band

BS transmit UE receive
LTE
FDD
Band 1
1920MHz-1980MHz
2110MHz-2170MHz
Band 2
1850MHz-1910MHz
1930MHz-1990MHz
Band 3
1710MHz-1785MHz
1805MHz-1880MHz
Band 4
1710MHz-1755MHz Aws
2110MHz-2155MHz
Band 5
824MHz-849MHz
869MHz-894MHz
Band 6
830MHz-840MHz
875MHz-885MHz
Band 7
2500MHz-2570MHz
2620MHz-2690MHz
2600MHz
Issue 03 (2015-07-30)
Band 8
880MHz-915MHz
925MHz-960MHz
Band 8
1749.9MHz-1784.9MHz
1844.9MHz-1879.9MHz
Band 10
1710MHz-1770MHz
2110MHz-2170MHz
Band 11
1427.9MHz-1447.9MHz
1475.9MHz-1495.9MHz
Band 12
699MHz-716MHz
729MHz-746MHz
Band 13
777MHz-787MHz
746MHz-756MHz
Band 14
788MHz-798MHz
758MHz-768MHz
Band 15
Reserved
Reserved

2339
Nastar
Tab
Page
LTE
TDD
UMTS
Issue 03 (2015-07-30)
Freque
ncy
Band
Name
band BS receive UE
transmit

Band 16
Reserved
Reserved
Band 17
704MHz-716MHz
734MHz-746MHz
Band 18
815MHz-830MHz
860MHz-875MHz
Band 19
830MHz-845MHz
875MHz-890MHz
Band 20
832MHz-862MHz
791MHz-821MHz
Band 21
1447.9MHz-1462.9MHz
1495.9MHz-1510.9MHz
Band 22
3410MHz-3490MHz
3510MHz-3590MHz
Band 23
2000MHz-2020MHz
2180MHz-2200MHz
Band 24
1626.5MHz-1660.5MHz
1525MHz-1559MHz
Band 25
1850MHz-1915MHz
1930MHz-1995MHz
Band 26
814MHz-849MHz
859MHz-894MHz
Band 27
807MHz-824MHz
852MHz-869MHz
Band 28
703MHz-748MHz
758MHz-803MHz
Band 29
N/A
717MHz-728MHz
Band 33
1900MHz-1920MHz
1900MHz-1920MHz
Band 34
2010MHz-2025MHz
2010MHz-2025MHz
Band 35
1850MHz-1910MHz
1850MHz-1910MHz
Band 36
1930MHz-1990MHz
1930MHz-1990MHz
Band 37
1910MHz-1930MHz
1910MHz-1930MHz
Band 38
2570MHz-2620MHz
2570MHz-2620MHz
Band 39
1880MHz-1920MHz
1880MHz-1920MHz
Band 40
2300MHz-2400MHz
2300MHz-2400MHz
Band 41
2496MHz-2690MHz
2496MHz-2690MHz
Band 42
3400MHz-3600MHz
3400MHz-3600MHz
Band 43
3600MHz-3800MHz
3600MHz-3800MHz
Band 44
703MHz-803MHz
703MHz-803MHz
Band V
824MHz-849MHz
869MHz-894MHz
Band VI
830MHz-843MHz
875MHz-885MHz

2340
Nastar
Tab
Page
Freque
ncy
Band
Name
band BS receive UE
transmit

Band
VIII
880MHz-915MHz
925MHz-960MHz
Band XII
699MHz-716MHz
729MHz-746MHz
Band
XIII
777MHz-787MHz
746MHz-756MHz
Band
XIV
788MHz-798MHz
758MHz-768MHz
Band
XIX
830MHz-845MHz
875MHz-890MHz
Band XX
832MHz-862MHz
791MHz-821MHz

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Issue 03 (2015-07-30)

2341
Nastar
Parameter
Description
Select NE(s)

NOTE
Parameter
Description
Geographic
Terminal
Objects
Selects terminal objects. After you select terminal objects, the Nastar
geographically displays the traffic of the selected terminal objects. You
can select a maximum of ten terminal objects.
If terminal objects are not selected, terminal traffic analysis will not
function during geographic observation.
Geographic
Terminal
Abilities
Selects terminal capabilities. After you select terminal capabilities, the

Nastar geographically displays the selected terminal capabilities.
Grid Resolution
Settings
Set the Grid Resolutionfor displaying terminal geographic observation

results.
If terminal capabilities are not selected, terminal capability analysis will

not function during geographic observation.
100m*100m.

Parameter
Description
Duration
Delay
immediately.
Execute on
Issue 03 (2015-07-30)

2342
Nastar
5.7.4 Interface Description: UMTS Terminal Analysis

This section describes the interface that displays UMTS terminal analysis results. 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 UMTS terminal analysis
results:
l
Select a UMTS terminal analysis task in the Finished state, and double-click a result record
of the task in the displayed Task Result area.
Select a UMTS terminal analysis task in the Finished state. Double-click a result record
of the task in the displayed Task Result area and choose View Analysis Result from the
shortcut menu.
Interface
Figure 5-29 shows the terminal analysis results.
Figure 5-29 Interface for UMTS terminal analysis results
No.
Name
Icon area
Analysis result
tab page
Description
is used to display terminal analysis results through
geographic display. For detailed operations, see Terminal
Analysis Results Displayed Through Geographic Display.
Analysis results are displayed in the form of tab page.
occupation of terminals on the live network from different
Description: Terminal Penetration Analysis.
of each terminal capability supported by the terminals on the
live network. For detailed operations, see Interface
Description: Terminal Capability Analysis.
performance indicator of each type of terminal and analyze
the performance indicator of a type of terminal in each cell.
For details, see Interface Description: Terminal
Performance Analysis.
Issue 03 (2015-07-30)

2343
Nastar
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 5-30 shows the tab page.
Figure 5-30 Terminal penetration evaluation
No.
Item
Description
Icons and
analysis
options


objects.
2
Statistics chart

Statistics table

supported:
Interface Description: Terminal Capability Analysis

The terminal capability analysis result displays the occupation of different capabilities supported
by the terminals in the form of a histogram and a table. Figure 5-31 shows the tab page.
Issue 03 (2015-07-30)

2344
Nastar
Figure 5-31 Terminal capability evaluation
No.
Name
Description
Icon area
NE object
navigation tree
Terminal
capability list
Selects the terminal capability to be analyzed. If you select one or

more terminal capabilities, the capability analysis results are
displayed in both the chart area and table area on the right.
Chart area

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 the form of a histogram. The histogram is mapped to
the table on the right.
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.
Supports the selection of analyzed objects by the following three

different dimensions: the whole network, a single BSC, or a single
cell.
The analysis results of a maximum of two types of terminal

capability can be displayed at the same time. You can view the
analysis results of other terminal capabilities by using the scroll
bar.
Issue 03 (2015-07-30)

2345
Nastar
No.
Name
Description
Table area
The number and occupation of the terminals that support a certain

terminal capability in an NE object is displayed in the form of a
table. You can save the table by right-clicking the table and
choosing Save As from the shortcut menu.
For detailed description of the parameters, see 5.7.5 Parameters
for Viewing UMTS Terminal Analysis Results.

The terminal performance analysis table displays the terminal performance indicator, and the
No.
Name
Description
Analysis
indicator
navigation tree
l The Aggregation Type drop-down list is used to select the

aggravation dimension to be analyzed.
l The Terminal Properties node is used to select the terminal
attribute to be analyzed. 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
displayed only when you select IMEI-TAC_OS_Version.

analyzed. The KPIs are also displayed in the right area.
Issue 03 (2015-07-30)

2346
Nastar
No.
Name
Description
Aggregation
table of the
terminal
performance
indicators

on the terminals based on the selected dimension.
the selected KPI.
all as from the shortcut menu, and the system saves the
displayed TopN results and all the other results that are not
displayed to your local computer.
Aggregation
table of the celland bearerlevel terminal
performance
indicators
l The Analyze by Cell tab displays the performance indicator

value of a certain type of NE in area 2 in each cell.
l The Analyze by Bearer tab displays the performance
indicator value of a certain type of NE in area 2 in each
bearer.
the selected KPI.
displayed.
local computer.
For detailed description of the parameters, see5.7.5 Parameters
for Viewing UMTS Terminal Analysis Results.
Issue 03 (2015-07-30)

2347
Nastar
Terminal Analysis Results Displayed Through Geographic Display

On the icon area for displaying terminal analysis results, click
Observation window is displayed, as shown in Figure 5-33.
. The Geographic
Figure 5-33 Terminal analysis results displayed through geographic display
Issue 03 (2015-07-30)
N
o.
Item
Description
Icon area

2348
Nastar
N
o.
Item
Description
Navigati
on tree

NOTE
If you need to delete all sites in a network system, click Remove through the layer

map interface.
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.
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.
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 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.
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 03 (2015-07-30)

2349
Nastar
N
o.
Item
Description
Geograp
hic
display
area
l Displays the analysis results of selected KPIs on grid maps using distinct
colors by default. However, only the analysis results of the last selected
KPI are visible.
Raster
details
area
This area is empty for terminal analysis.
Legend
detail
area
Informati
on area
The interface displays no information when it is opened. If you select a grid,

the values of selected KPIs are displayed in all the cells in this gird. 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.

, the
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.

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.
5.7.5 Parameters for Viewing UMTS Terminal Analysis Results

This section describes the parameters for viewing UMTS terminal analysis results, You can refer
to the description when viewing terminal analysis results.
Issue 03 (2015-07-30)

2350
Nastar
Terminal Penetration Analysis Information
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
IMEI-TAC
Eight digits
N/A
Indicates the
combination of
the type
approval code
(TAC) and the
final assembly
code (FAC) in
an International
Mobile
Equipment
Identity (IMEI).
An IMEI
consists of 15
digits and
uniquely
identifies a
terminal in the
world. In an
IMEI, the TAC
refers to the first
six digits, and
the FAC refers
to the seventh
and eighth
digits. The
combination of
TAC and FAC
uniquely
identifies a
terminal.
N/A
Vendor
[1,256]
N/A
Indicates the
terminal vendor,
for example,
Nokia and
Apple.
N/A
Type
N/A
N/A
Indicates the
terminal type,
for example,
common
terminal,
intelligent
terminal, and
data card.
N/A

2351
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Model
[1,256]
N/A
Indicates the
terminal model,
for example,
iPhone4.
N/A
Chip Model
[0,256]
N/A
Indicates the
terminal chip
model.
N/A
Technology
N/A
N/A
Indicates the
RAT that the
terminal
supports, for
example, GSM
and WCDMA.
N/A
Data Transfer
N/A
N/A
Indicates the
data transfer
mode that the
terminal uses,
for example,
HSDPA and
HSUPA.
N/A
Terminals
[1,+)
Number
Indicates the
number of
terminals of this
type within the
statistical range.
If the statistics
are collected
based on IMEITAC, this
parameter
indicates the
number of
terminals with
the same IMEITAC and
different IMEIs.
N/A
Terminal Ratio
[0,100]
Proportion of
terminals of a
specified type in
all terminals.
N/A

2352
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
R99/HSDPA/
HSUPA
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support the R99,
HSDPA, or
HSUPA
transmission
mode under a
cell, RNC, or
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Protocol
Version
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support each
protocol version
under a cell,
RNC, or
network. The
protocol
versions include
R99, R4, R5,
and R6.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2353
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E_FACH
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support
E_FACH under
a cell, RNC, or
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
E_RACH
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support
E_RACH under
a cell, RNC, or
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2354
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
U900
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support
frequency band
900 under a cell,
RNC, or
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDPA
Issue 03 (2015-07-30)
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support each
HSDPA
category under a
cell, RNC, or
network. The
HSDPA
categories are
common
HSDPA,
64QAM,
MIMO, MIMO
+64QAM, DC,
DC+64QAM,
DC+MIMO,
and DC+MIMO
+64QAM.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2355
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
HSUPA
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support each
HSDPA
category under a
cell, RNC, or
network. The
HSDPA
categories are
10ms TTI, 2ms
TTI, uplink
16QAM, DCHSUPA, and
DC-HSUPA
+16QAM.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Used to collect
statistics on the
number and
percentage of
terminals that
support
continuous
packet
connectivity
(CPC) under a
cell, RNC, or
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
CPC
N/A
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2356
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Fast Dormancy
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support Fast
Dormancy
under a cell,
RNC, or
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
R8 Fast
Dormancy
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support R8 Fast
Dormancy
under a cell,
RNC, or
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2357
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Wi-Fi
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support Wi-Fi
under a cell,
RNC, or
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
FDD-LTE
N/A
N/A
Used to collect
statistics on the
number and
percentage of
terminals that
support LTE
under a cell,
RNC, or
network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2358
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
LTE FDD
Frequency Band
N/A
N/A
LTE FDD
frequency band
supported by
terminals that
have gained
access to a
UMTS network
to use voice or
data services
during terminal
refarming
analysis.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
LTE TDD
Frequency Band
N/A
N/A
LTE TDD
frequency band
supported by
terminals that
have gained
access to a
UMTS network
to use voice or
data services
during terminal
refarming
analysis.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2359
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
UMTS
Frequency Band
N/A
N/A
UMTS
frequency band
supported by
terminals that
have gained
access to a
UMTS network
to use voice or
data services
during terminal
refarming
analysis.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2360
Nastar
Terminal Performance Analysis - Basic Information
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
IMEI-TAC
Eight digits
N/A
Indicates the
combination of
the type
approval code
(TAC) and the
final assembly
code (FAC) in
an International
Mobile
Equipment
Identity (IMEI).
An IMEI
consists of 15
digits and
uniquely
identifies a
terminal in the
world. In an
IMEI, the TAC
refers to the first
six digits, and
the FAC refers
to the seventh
and eighth
digits. The
combination of
TAC and FAC
uniquely
identifies a
terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2361
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Vendor
[1,256]
N/A
Indicates the
terminal vendor,
for example,
Nokia and
Apple.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Model
[1,256]
N/A
Indicates the
terminal model,
for example,
iPhone4.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2362
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Type
N/A
N/A
Indicates the
terminal type,
for example,
common
terminal,
intelligent
terminal, and
data card.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Chip Model
[0,256]
N/A
Indicates the
terminal chip
model.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2363
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Technology
N/A
N/A
Indicates the
RAT that the
terminal
supports, for
example, GSM
and WCDMA.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Data Transfer
N/A
N/A
Indicates the
data transfer
mode that the
terminal uses,
for example,
HSDPA and
HSUPA.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2364
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Support Wi-Fi
N/A
N/A
Indicates
whether the
terminal
supports Wi-Fi.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RNCID
[0,4095]
N/A
Indicates the ID
of the RNC
where the
terminal is
located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2365
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RNC Name
N/A
N/A
Indicates the
name of the
RNC where the
terminal is
located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of the cell where
the terminal is
located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2366
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
where the
terminal is
located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Terminals
[1,+)
Number
Indicates the
number of
terminals of this
type within the
statistical range.
If the statistics
are collected
parameter
indicates the
number of
terminals with
different IMEIs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2367
Nastar
Terminal Performance Analysis Summary - Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
[0,+)
Number
Indicates the
number of
measurement
reports (MRs)
on the RRC
Connection
Request
message that
carries the setup
reason (cell
reselection, cell
change
command,
registration, or
detachment).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Failures (NonService)
Issue 03 (2015-07-30)
[0,+)
Number
Indicates the
number of MRs
on abnormal
RRC
connection
setups by
sending an RRC
Connection
Request
message that
carries the setup
reason (cell
reselection, cell
change
command,
registration, or
detachment).

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2368
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Rate
(Non-Service)
[0,100]
Indicates the
success rate of
non-service
RRC setups
initiated by the
terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Requests
(Service)
[0,+)
Number
Indicates the
number of MRs
on the RRC
Connection
Request
message that
carries the setup
reason (the
setup reason is
not cell
reselection, cell
change
command,
registration, or
detachment).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2369
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Failures
(Service)
[0,+)
Number
Indicates the
number of MRs
on abnormal
RRC
connection
setups by
sending an RRC
Connection
Request
message that
carries the setup
reason (the
setup reason is
not cell
reselection, cell
change
command,
registration, or
detachment).
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
success rate of
service RRC
setups initiated
by the terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
RRC Setup
Success Rate
(Service)
[0,100]
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2370
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Indicates the
number of MRs
on the event that
the core network
(CN) sends an
RAB
ASSIGNMENT
REQUEST
message after
the terminal
signaling
connection is set
up successfully.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
Issue 03 (2015-07-30)
[0,+)
Number
Indicates the
number of MRs
on the RAB
ASSIGNMENT
REQUEST
message
initiated by the
core network
whose
corresponding
RAB
ASSIGNMENT
RESPONSE
message is not
received, or
contains
Failure.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2371
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Rate
[0,100]
Indicates the
percentage of
normal RAB
setups after the
terminal
signaling
connection is set
up successfully
and the CN
sends an RAB
ASSIGNMENT
REQUEST
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2372
Nastar
Terminal Performance Analysis Summary - Retainability

Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Releases
[0,+)
Number
Indicates the
total number of
abnormal RAB
releases. The
RAB is
abnormally
released in any
of the following
situations:
l SRAN8.0/
GBSS15.0/
RAN 15.0
(1) The call is

released by the
RNC. If the
RNC detects
that a UE fails to
send data for a
long time or if
the RNC
experiences an
exception (for
example, SRB
reset or
exception on an
AAL2 link over
the Iu interface),
the RNC sends
an RAB
RELEASE
REQUEST
message to the
CN for releasing
the RAB or
sends an IU
RELEASE
REQUEST
message to the
CN for releasing
the IU
connection. Call
releases
initiated by the
RNC with any
of the following
cause values are
considered as a
normal release:
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2373
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
User Inactivity,
Normal
Release,
Successful
Relocation,
Network
Optimization,
UE Generated
Signaling
Connection
Release. Call
releases
initiated by the
RNC with other
cause values are
considered as
abnormal
release.
(2) The call is
released by the
CN. The CN
sends an RAB
ASSIGNMENT
REQUEST
message to the
RNC for
releasing the
RAB or sends an
IU RELEASE
COMMAND
message to the
RNC for
releasing the IU
connection. All
call releases
initiated by the
CN are
considered as
normal release.
(3) The call is
released by a UE
using a
SIGNALING
CONNECTION
RELEASE
INDICATION
Issue 03 (2015-07-30)

2374
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
message. Based
on domain
information
carried in the
message, the
RNC sends an
IU RELEASE
REQUEST
message to a
related SGSN or
MSC of the CN
for initiating IU
connection
release in the
domain. After
the IU
connection in
the domain is
released, the
RNC initiates
RRC release for
the UE if no IU
connection in
another domain
is available. Call
releases in this
situation are
considered as
normal release.
Issue 03 (2015-07-30)

2375
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Ratio of
Abnormal RAB
Releases
[0,100]
Indicates the
percentage of
abnormal RAB
releases.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2376
Nastar
Terminal Performance Analysis Summary - Mobility

Parameter
Range
Unit
Description
Supported
Solution
Version
Soft Handover
Requests
[0,+)
Number
Indicates the
number of soft
handovers
initiated by the
terminal during
the service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If the NE
version is
RAN14.0 or
later and
multiple soft
handovers are
initiated during
a call, the Naster
collects
statistics on and
analyzes all the
initiated soft
handovers.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
If the NE
version is
RAN13.0 or
earlier and
multiple soft
handovers are
initiated during
the a call, the
Naster collects
statistics on and
analyzes only
the first and last
soft handovers.
Issue 03 (2015-07-30)

2377
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Soft Handover
Failures
[0,+)
Number
Indicates the
number of
abnormal soft
handovers
during the
service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If the NE
version is
RAN14.0 or
later and
multiple soft
handovers are
initiated during
a call, the Naster
collects
statistics on and
analyzes all the
initiated
handovers.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
If the NE
version is
RAN13.0 or
earlier and
multiple soft
handovers are
initiated during
the a call, the
Naster collects
statistics on and
analyzes only
the first and last
handovers.
Issue 03 (2015-07-30)

2378
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Soft Handover
Success Rate
[0,100]
Indicates the
success rate of
soft handovers
initiated by the
terminal during
the service
process. If
multiple soft
handovers are
initiated during
the process of
one call, the
Nastar collects
and analyzes
statistics on the
first and last
handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2379
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Hard Handover
Requests
[0,+)
Number
Indicates the
number of hard
handover
requests
initiated by a
terminal during
the service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In RAN14.0 and
later versions, if
multiple soft
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes all
the initiated soft
handovers.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
In RAN13.0 and
earlier versions,
if multiple soft
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes
only the last soft
handover.
Issue 03 (2015-07-30)

2380
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Hard Handover
Failures
[0,+)
Number
Indicates the
number of
abnormal hard
handovers
failures for a
terminal during
the service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In RAN14.0 and
later versions, if
multiple soft
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes all
the initiated soft
handovers.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
In RAN13.0 and
earlier versions,
if multiple soft
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes
only the last soft
handover.
Issue 03 (2015-07-30)

2381
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Hard Handover
Success Rate
[0,100]
Indicates the
success rate of
hard handovers
initiated by a
terminal during
the service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In RAN14.0 and
later versions, if
multiple soft
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes all
the initiated soft
handovers.
In RAN13.0 and
earlier versions,
if multiple soft
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes
only the last soft
handover.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2382
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number
Indicates the
number of intersystem outgoing
handover
requests
initiated by a
terminal during
the service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In RAN14.0 and
later versions, if
multiple intersystem outgoing
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes all
the initiated
handovers.
Successful
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number
Indicates the
number of times
inter-system
outgoing
handover
requests are
successfully
initiated by a
terminal during
the service
process.
In RAN14.0 and
later versions, if
multiple intersystem outgoing
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes all
the initiated
handovers.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2383
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Requests
[0,+)
Number
Indicates the
number of intersystem
incoming
handover
requests
initiated by a
terminal during
the service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In RAN14.0 and
later versions, if
multiple intersystem
incoming
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes all
the initiated
handovers.
l SRAN10.0/
GBSS17.0/
RAN17.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2384
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Successful
Inter-RAT
Incoming
Handover
Requests
[0,+)
Number
Indicates the
number of times
inter-system
incoming
handover
requests are
successfully
initiated by a
terminal during
the service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In RAN14.0 and
later versions, if
multiple intersystem
incoming
handovers are
initiated during
a call, the Nastar
collects
statistics about
and analyzes all
the initiated
handovers.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2385
Nastar
Terminal Performance Analysis Summary - Delay

Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Delay Reports
(Non-Service)
[0,+)
Number
Indicates the
number of MRs
with RRC
Connection
Request and
RRC
Connection
Setup Complete
messages
existing in the
same report
during the
process of
sending system
messages such
as the location
change
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
value for
average RRC
setup delays
during the
process of
sending system
messages such
as the location
change
message. RRC
setup delay =
Timestamp of
an RRC CONN
SETUP CMP
message Timestamp of
an RRC CONN
REQ message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
RRC Setup
Average Delay
(Non-Service)
Issue 03 (2015-07-30)
[0,+)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2386
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Ratio of RRC
Setup Overlong
Delays (NonService)
[0,100]
Indicates the
percentage of
RRC setup
overlong delays
during the
process of
sending system
messages such
as the location
change
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Delay Reports
(Service)
[0,+)
Number
Indicates the
number of MRs
with RRC
Connection
Request and
RRC
Connection
Setup Complete
messages
existing in the
same report
during the
service process
initiated by the
terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2387
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Average Delay
(Service)
[0,+)
Indicates the
value for
average RRC
setup delays
during the
service process
initiated by the
terminal. RRC
setup delay =
Timestamp of
an RRC CONN
SETUP CMP
an RRC CONN
REQ message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of RRC
Setup Overlong
Delays
(Service)
[0,100]
Indicates the
percentage of
RRC setup
overlong delays
during the
service process
initiated by the
terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2388
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Delay Reports
[0,+)
Number
Indicates the
number of RAB
setup delay
reports within a
valid interval
between the
time of sending
an RAB
ASSIGNMENT
REQUEST
message
timestamp and
that of sending
an RAB
ASSIGNMENT
RESPONSE
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
value for
average RAB
setup delays
between the
time of sending
an RAB
ASSIGNMENT
REQUEST
message and the
time of sending
an RAB
ASSIGNMENT
RESPONSE
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
RAB Setup
Average Delay
[0,+)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2389
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Overlong
Delays Ratio
[0,100]
Indicates the
percentage of
MRs with RAB
setup overlong
delay in all MRs
with RAB setup
delay. The RAB
setup overlong
delay means that
the interval
between the
time when the
terminal sends
an RAB
ASSIGNMENT
REQUEST
message and the
time when the
terminal
receives an
RAB
ASSIGNMENT
RESPONSE
message is
greater than the
specified
threshold.
Percentage of
long RAB setup
delay = Number
of MRs with
RAB setup
overlong delay/
Number of MRs
with RAB setup
delay.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2390
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover Delay
Reports
[0,+)
Number
Indicates the
number of intersystem outgoing
handover delay
reports recorded
by the Nastar.
Inter-system
outgoing
handover delay
= Timestamp of
an IU
RELEASE
COMMAND
an
RELOCATION
REQUIRED
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
value for
average intersystem outgoing
handover delays
recorded by the
Nastar. Intersystem outgoing
handover delay
= Timestamp of
an IU
RELEASE
COMMAND
an
RELOCATION
REQUIRED
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Inter-RAT
Outgoing
Handover
Average Delay
Issue 03 (2015-07-30)
[0,+)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2391
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Ratio of InterRAT Outgoing

Handover
Overlong
Delays
[0,100]
Indicates the
percentage of
inter-system
outgoing
handover
overlong delays
recorded by the
Nastar.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Incoming
Handover Delay
Reports
[0,+)
Number
Indicates the
number of intersystem
incoming
handover delay
reports recorded
by the Nastar.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2392
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Average Delay
[0,+)
Indicates the
value for
average intersystem
incoming
handover delays
recorded by the
Nastar.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of InterRAT Incoming

Handover
Overlong
Delays
[0,100]
Indicates the
value for
average intersystem
incoming
handover delays
recorded by the
Nastar.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2393
Nastar
Terminal Performance Analysis Summary - Quality

Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink OneWay Audio

Times
[0,+)
Number
Indicates the
number of
uplink one-way
audio calls
during the
calling process.
Uplink one-way
calls are
detected by the
BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Times
[0,+)
Number
Indicates the
number of
downlink oneway audio calls
during the
calling process.
Downlink oneway calls are
detected by the
BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2394
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Noise Times
[0,+)
Number
Indicates the
number of calls
with noises
during the
calling process.
The noises can
be detected by
the BSC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Noise Ratio
[0,100]
Indicates the
percentage of
calls with noises
during the
calling process.
Percentage of
calls with noises
= Number of
calls with
noises/Number
of connection
acknowledgeme
nts x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2395
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SQI Reports
[0,+)
Number
Indicates the
number of valid
mean opinion
Score (SQL )
reports for the
voice service on
the uplink. SQL
reflects the
voice quality
during the
calling process.
Its value ranges
from 0 to 500.
The greater the
value is, the
better the voice
quality is.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
average SQI
value during the
calling process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Average SQI
[0,+)
Number
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2396
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Ratio of
Abnormal SQIs
[0,100]
Indicates the
percentage of
abnormal SQLs
during the
calling process.
Percentage of
abnormal SQLs
= Number of
calls with
abnormal SQLs/
Connection
acknowledgeme
nts x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Excellent SQIs
Issue 03 (2015-07-30)
[0,100]
Percentage of
uplink SQI
whose value is
Excellent
collected based
on the SQI
calculation
period during a
whole cal. The
percentage
reflects the
voice quality
during the call.
The threshold
for Excellent is
configured by
running the SET
USQICOUNT
command. If the
call duration is
less than a
statistical
period, this
indicator is not
collected.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2397
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Ratio of Good
SQIs
[0,100]
Indicates the
percentage of
uplink calls with
Good SQLs,
based on the
SQL calculation
period. The
percentage
reflects the
voice quality
during the
calling process.
The Good
threshold is set
by running the
SET
USQICOUNT
command. If the
duration of one
call is shorter
than on period,
the call is not
counted.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Indicates the
percentage of
uplink calls with
Accept SQLs,
based on the
SQL calculation
period. The
percentage
reflects the
voice quality
during the
calling process.
The Accept
threshold is set
by running the
SET
USQICOUNT
command. If the
duration is
shorter than one
period, the call
is not counted.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Ratio of Accept
SQIs
Issue 03 (2015-07-30)
[0,100]

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2398
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Ratio of Poor
SQIs
[0,100]
Percentage of
uplink SQI
whose value is
Poor collected
based on the
SQI calculation
period during a
whole cal. The
percentage
reflects the
voice quality
during the call.
The threshold
for Poor is
configured by
running the SET
USQICOUNT
command. If the
call duration is
less than a
statistical
period, this
indicator is not
collected.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2399
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Ratio of Bad
SQIs
[0,100]
Indicates the
percentage of
uplink calls with
Bad SQLs,
based on the
SQL calculation
period. The
percentage
reflects the
voice quality
during the
calling process.
The Bad
threshold is set
by running the
SET
USQICOUNT
command. If the
duration of one
call is shorter
than one period,
the call is not
counted.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2400
Nastar
Terminal Performance Analysis Summary - Duration

Parameter
Range
Unit
Description
Supported
Solution
Version
AMR RAB
Duration
Reports
[0,+)
Number
Indicates the
number of valid
MRs with RAB
occupation
duration that can
be counted by
the Nastar
during the voice
service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1. Starting time
The time when
an RAB
assigned
process
succeeds.
The time when
the migration
into the process
ends.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
The time when

the inter-system
handover
process
succeeds.
2. End time
The time when
an RAB is
released by the
terminal.
The time when
an IU REL CM
message is
received.
The time when
an RB REL
SUCC message
is received.
Issue 03 (2015-07-30)

2401
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
AMR RAB
Average
Duration
[0,+)
Indicates the
value for
average RAB
occupation
duration
recorded in one
report during the
voice service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
AMR RAB
Overshort
Durations
[0,+)
Number
Indicates the
number of voice
calls with short
duration.
If the RAB
duration of a call
is shorter than
the AMR short
call threshold,
the duration of
an AMR RAB is
regarded as a
short call
duration.
The AMR short
call threshold is
set by engineers
when an RAB is
set up.
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2402
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VP RAB
Duration
Reports
[0,+)
Number
Indicates the
number of valid
reports with
RAB
occupation
duration that can
be collected by
the Nastar
during the video
phone service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
For details about

how to analyze
the RAB setup
and release, see
Description of
Measurement
Reports for
AMR Service
Duration.
VP RAB
Average
Duration
[0,+)
Indicates the
value for
average VP
RAB
occupation
duration
recorded in one
report during the
VP service
process.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2403
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VP RAB
Overshort
Durations
[0,+)
Number
Indicates the
number of
videophone
calls with short
call duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If the RAB
duration of a
videophone call
is shorter than
the VP short call
threshold, the
duration of a VP
RAB is regarded
as a short call
duration.
The short call
threshold is set
by engineers
when an RAB is
set up.
PS R99 RAB
Duration
Reports
Issue 03 (2015-07-30)
[0,+)
Number
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Indicates the
number of
reports with
valid RAB
occupation
duration that can
be collected by
the Nastar
during the R99
service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
For details about

how to analyze
the RAB setup
and release, see
Description of
Measurement
Reports for
AMR Service
Duration.
l SRAN10.0/
GBSS17.0/
RAN17.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2404
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average PS R99
RAB Duration
[0,+)
Indicates the
value for
average RAB
occupation
duration
recorded in one
report during the
R99 service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDPA RAB
Duration
Reports
[0,+)
Number
Indicates the
number of MRs
with valid data
transmission
duration during
the HSDPA
service process.
The valid data
transmission
duration refers
to the duration
when data is
transmitted
through on the
network during
the service
process.
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2405
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
HSDPA RAB
Average
Duration
[0,+)
Indicates the
average valid
data
transmission
duration during
an HSDPA
service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSUPA RAB
Duration
Reports
[0,+)
Number
Indicates the
number of
reports with
valid data
transmission
duration that can
be collected by
the Nastar
during the
HSUPA service
process.
For details about
how to analyze
the RAB setup
and release, see
Description of
Measurement
Reports for
AMR Service
Duration.
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2406
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
HSUPA RAB
Average
Duration
[0,+)
Indicates the
value for
average RAB
occupation
duration
recorded in one
report during the
HSUPA service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSUPA_HSDP
A RAB
Duration
Reports
[0,+)
Number
Indicates the
number of
reports with
valid RAB
occupation
duration that can
be counted
during the
HSUPA and
HSDPA service
processes.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2407
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
HSUPA_HSDP
A RAB Average
Duration
[0,+)
Indicates the
average RAB
occupation
duration
recorded in a
report during the
HSUPA and
HSDPA service
processes.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2408
Nastar
Terminal Performance Analysis Summary - Rate

Parameter
Range
Unit
Description
Supported
Solution
Version
PS R99 Uplink
Average
Throughput
[0,+)
kbit/s
Indicates the
ratio of the
downlink
throughput to
transmission
duration of valid
data during the
R99 service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PS R99
Downlink
Average
Throughput
[0,+)
kbit/s
Indicates the
ratio of the
uplink
throughput to
transmission
duration of valid
data during the
R99 service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2409
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
HSDPA
Average
Throughput
[0,+)
kbit/s
Indicates the
ratio of the
downlink
throughput to
transmission
duration of valid
data during the
HSDPA service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSUPA
Average
Throughput
[0,+)
kbit/s
Indicates the
ratio of the
uplink
throughput to
transmission
duration of valid
data during the
HSUPA service
process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2410
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
HSUPA
HSDPA Uplink
Average
Throughput
[0,+)
kbit/s
Indicates the
ratio of the
uplink
throughput to
transmission
duration of valid
data during the
HSDPA and
HSUPA service
processes.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSUPA
HSDPA
Downlink
Average
Throughput
[0,+)
kbit/s
Indicates the
ratio of the
downlink
throughput to
transmission
duration of valid
data during the
HSDPA and
HSUPA service
processes.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2411
Nastar
Terminal Performance Analysis Summary - By Cell

Parameter
Range
Unit
Description
Supported
Solution
Version
Row No
[1,50000)
N/A
Indicates the
number of a row
in the summary
table.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RNC ID
[0,4095]
N/A
Indicates the ID
of the RNC
where the
terminal is
located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2412
Nastar
RNC Name
N/A
N/A
Indicates the
name of the
RNC where the
terminal is
located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell ID
[0,65535]
N/A
Indicates the ID
of the cell where
the terminal is
located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2413
Nastar
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
where the
terminal is
located.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Terminals
[0,+)
N/A
Indicates the
number of
terminals of a
specified type in
each cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
NOTE
For details about other parameters, see Terminal Performance Analysis Summary - Accessibility,
Terminal Performance Analysis Summary - Retainability, Terminal Performance Analysis
Summary - Mobility, Terminal Performance Analysis Summary - Delay, Terminal Performance
Analysis Summary - Quality, Terminal Performance Analysis Summary - Duration and Terminal
Performance Analysis Summary - Rate.
Issue 03 (2015-07-30)

2414
Nastar
Terminal Performance Analysis Summary - By Bearer

Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer Type
NA
NA
Type of the
channel that
bears voice or
data services.
Common bearer
types include
AMR, R99 PS,
HSDPA,
HSUPA, and
HSDPA_HSUP
A.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
NOTE
For details about other parameters, see Terminal Performance Analysis Summary - Accessibility,
Terminal Performance Analysis Summary - Retainability, Terminal Performance Analysis
Summary - Mobility, Terminal Performance Analysis Summary - Delay, Terminal Performance
Analysis Summary - Quality, Terminal Performance Analysis Summary - Duration and Terminal
Performance Analysis Summary - Rate.
Issue 03 (2015-07-30)

2415
Nastar
Terminal Geographic Display-Traffic Analysis

Parameter
Range
Unit
Description
Supported
Solution
Version
Total Traffic
[0,+)
KB
The grid map is

rendered
according to the
total traffic of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink traffic
[0,+)
KB
The grid map is

rendered
according to the
uplink traffic of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2416
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink
traffic
[0,+)
KB
The grid map is

rendered
according to the
downlink traffic
of terminals in
the grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2417
Nastar
Terminal Geographic Display-Capability Analysis

Parameter
Range
Unit
Description
Supported
Solution
Version
R99/HSDPA/
HSUPA
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support R99/
HSDPA/
HSUPA in the
total number of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
protocol version
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support a
protocol version
in the total
number of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2418
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E_FACH
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support
E_FACH in the
total number of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
E_RACH
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support
E_RACH in the
total number of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2419
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
U900
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support U900 in
the total number
of terminals in
the grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDPA
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support HSDPA
in the total
number of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2420
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
HSUPA
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support HSUPA
in the total
number of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CPC
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support CPC in
the total number
of terminals in
the grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2421
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Fast Dormancy
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support Fast
Dormancy in the
total number of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
R8 Fast
Dormancy
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support R8 Fast
Dormancy in the
total number of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2422
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
FDD-LTE
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support FDDLTE in the total
number of
terminals in the
grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Wi-Fi
N/A
N/A
The grid map is

rendered
according to the
percentage of
terminals that
support Wi-Fi in
the total number
of terminals in
the grids.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
5.8 UMTS Cell Performance Analysis

Issue 03 (2015-07-30)

2423
Nastar
5.8.1 Basics of UMTS Cell Performance Analysis

This section describes the basics of UMTS cell performance analysis, including the function and
technical specifications. Read this section before performing UMTS cell performance analysis.
NOTE
Functions of UMTS Cell Performance Analysis

The Nastar provides the UMTS cell performance analysis function to help quickly identify
abnormal cells and obtain data of abnormal calls in these cells. The obtained data helps network
optimization engineers detect the causes of abnormal cells, facilitating in-depth problem
analysis.
Generally, the network optimization engineers use the whole-to-partial analysis method for
network optimization or performance analysis. With this method, they analyze and detect
network problems by evaluating performance indicators, and then analyzes the counters of the
entire network or for a specific RNC. Then, the Nastar analyzes cells under an abnormal RNC
to identify the bottom N cells. After that, the Nastar performs in-depth analysis on the bottom
N cells. The Nastar provides the following functions for cell performance analysis:
l
The Nastar analyzes abnormal call records by RNC or by NE group to identify the exception
types. This helps network optimization engineers detect the causes of an exception type,
improving problem-solving efficiency.
After indentifying the exception types of an abnormal cell, the Nastar provides the in-depth
analysis function to detect bottom N subscribers and bottom N terminals with poor
performance. This function helps network optimization engineers quickly locate bottom N
subscribers and bottom N terminals that cause the same exception for an abnormal cell.
The network optimization engineers can then resolve problems in these subscribers and
terminals to improve cell performance.
When abnormal cells are not identified, the Nastar can perform exception analysis on a
large number of cells under an RNC, which helps to quickly identify the bottom N abnormal
cells.
Except for identifying the problematic cells and the causes of certain exceptions, the Nastar
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
Issue 03 (2015-07-30)

2424
Nastar
function is enabled, the Nastar leads engineers to the complaint analysis results, helping
them obtain the information about subscribers' calls and locate problems.
The cell performance analysis results can be exported as .csv, .xls, or .xlsx files. You can optimize
cells based on these result files.
NOTE
The statistical results based on the cell performance analysis function differ from those based on
performance data.
l
The Nastar collects statistics based on subscriber experience data while the U2000/M2000 and PRS
collect statistics based on performance data obtained from network devices.
The Nastar can perform in-depth analysis on abnormal cells with the cell performance analysis
function while the U2000/M2000 and PRS can only detect abnormal cells.
Function Principles
The Nastar uses the CHRs on the NE side for cell performance analysis.
NOTE
Issue 03 (2015-07-30)

2425
Nastar

User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

2426
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for UMTS Cell Performance Analysis

NOTE
Issue 03 (2015-07-30)
Item
Execution type
One-time task

task
<= 5100 cells

2427
Nastar
Item
<= 50

analysis task
7 days
<= 140 minutes

analysis data
7 days

analysis data
15 days
5.8.2 Preparations for UMTS Cell Performance Analysis

Before starting a UMTS cell performance analysis task, you must check the operation rights and
the matching environment and prepare relevant data to ensure that the UMTS cell performance
analysis task is executed normally. Read this section before performing UMTS cell performance
analysis.

l
Check that you have applied the license for UMTS cell performance analysis and the license
is valid.
Check that the login user has the rights to subscribe to the source data for UMTS cell
performance analysis.
contact the administrator to enable the data source switch.
Check that the login user has the rights to create UMTS cell performance analysis tasks
and perform operations on the NEs involved in these tasks.

Configuration Data
The configuration data of NEs related to the measurement cells is used to obtain CHR data of
cells from the network. The configuration data is also used to analyze cell information in CHRs
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.
Issue 03 (2015-07-30)

2428
Nastar
Data.
NOTE
To ensure the validity of the configuration data, you are advised to analyze cell performance on a daily
basis.

l
Preparing for Obtaining Data > Preparing for Obtaining Data(UMTS) > Turning On
the User Identity Information Reporting Switch (UMTS) in Nastar Commissioning
Guide.
5.8.3 Process of UMTS Cell Performance Analysis

This section describes the process of UMTS cell performance analysis and the steps of each
procedure.
l
Prerequisites
Process
Prerequisites
The UMTS configuration data and engineering parameters have been imported into the Nastar
database. For details, see 5.8.2 Preparations for UMTS Cell Performance Analysis.
Process
Issue 03 (2015-07-30)

2429
Nastar
Issue 03 (2015-07-30)

2430
Nastar
Table 5-17 Description of UMTS cell performance analysis process

No.
Procedure
Description
Reference
(1)
Check the
integrity of
analysis data

3.6 Checking the

Integrity of
Analysis Data
Procedure:
1. Set Data Type to UMTS Cell
Performance Analysis Data.
4. Click Query.
(2).
NOTE
Issue 03 (2015-07-30)

2431
Nastar
No.
Procedure
Description
Reference
(2)
Subscribe to
analysis data
(basic)
NOTE
You are advised to contact the administrator
with subscription rights to turn on the data
source switch because the source data
subscription function has high security
requirements.
3.5 Subscribing to
Analysis Data

Procedure:
UMTS tab.
2. In the navigation tree, select the desired
NEs.
3. On the Basic Subscription Settings tab
page, click Set.
dialog box, set the data source switch of
Cell Performance Analysis Data
(CHR) to ON.
5. Click Confirm.
Check that the data source switch is
open based on the information in the
Log Info area.
Subscribe to
analysis data
(application)

Procedure:
UMTS tab.
2. In the navigation tree, select the desired
NEs.
3. On the Cell Performance Analysis tab
page, click ON.
4. Set threshold parameters in the
displayed Cell Performance Analysis
Parameter Setting window.
5. Click Confirm. For details about
parameters, see Subscription Task
Parameters.
Issue 03 (2015-07-30)

2432
Nastar
No.
Procedure
Description
Reference
Check the
integrity of
analysis data

3.6 Checking the

Integrity of
Analysis Data
Procedure:
1. Set Data Type to UMTS Cell
4. Click Query.
(3)
Create an
analysis task
Entry: In the navigation tree of the

Analysis Task Management window,
choose Theme Function > Network
Analysis > UMTS Cell Performance
Analysis.
Procedure:
1. Double-click UMTS Cell
2. Specify the task name and remarks.
Then, click Next.
l For detailed
operations, see
3.7 Creating an
Analysis Task.
l For details about
the parameters,
see Analysis
Task
Parameters.

desired NEs. Then, click Next.
4. Specify the time period. After the task
is executed, the Nastar obtains the
analysis results for the specified time
period.
5. Click Finish.
(4)
View
analysis
resultsUMTS cell
performance
analysis
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,
l For detailed
operations, see
3.8 Querying
Analysis
Results.
Procedure:
l For details about

the analysis
result interface,
see 5.8.4
Interface
Description:
UMTS Cell
1. Double-click the result record of the

task.
2. In the displayed UMTS Cell
Performance Analysis window, view
the analysis results about this record.
Issue 03 (2015-07-30)

2433
Nastar
No.
Procedure
Description
View indepth
analysis
results
Entry: Click the

icon, or right-click a
cell in the navigation tree and choose
Further Analysis from the shortcut menu.
Reference
Performance
Analysis.
Procedure:
icon, or right-click a cell
1. Click the
in the navigation tree and choose
Further Analysis from the shortcut
menu.
2. View the analysis results in the
displayed further analysis window.
NOTE
When you perform in-depth analysis on an
existing cell 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.
(5)
Export
analysis
results
Entry: On the toolbar in the upper left part

of the cell performance analysis window,
click the export icon.
Procedure
2. Specify the export format, export path,
counters to be exported, and export
scope.
3. Click Export.
l For details, see

3.10 Exporting
Analysis
Reports.
description of the
window for
showing analysis
results, see 5.8.4
Interface
Description:
UMTS Cell
Performance
Analysis.

Basic Subscription
Issue 03 (2015-07-30)

2434
Nastar
Parameter
Description
Cell
Performance
Analysis Data
(CHR)
You can click

is unavailable.
Issue 03 (2015-07-30)
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
N
et
w
or
k
Ac
ces
s
Co
ver
ag
e
Pr
obl
em
TP
on
Acce
ss
Access coverage problem indicating a TP exception when the UE gains

access to the network: The TP value is the value of the TP when the UE
gains access to the network.
CPI
CH
Ec/
No
on
Acce
ss
Access coverage problem indicating a CPICH Ec/No exception when the

UE gains access to the network: The CPICH Ec/No value is the value of
the CPICH Ec/No when the UE gains access to the network.

2435
Nastar
P
ar
a
m
et
er
Ra
ng
e
De
lay
Pr
obl
em
Issue 03 (2015-07-30)
Unit
Description
CPI
CH
RSC
P on
Acce
ss
Access coverage problem indicating a CPICH RSCP exception when the

UE gains access to the network: The CPICH RSCP value is the value of
the CPICH RSCP when the UE gains access to the network.
RRC
Acce
ss
Dela
y(s)
(Non
Servi
ce)
Delay problem indicating that the non-service RRC connection setup delay
exceeds the predefined threshold: Non-service RRC connection setup
delay = Time stamp of the RRC CONN SETUP CMP message - Time
stamp of the RRC CONN REQ message.
RRC
Acce
ss
Dela
y(s)
(Serv
ice)
Delay problem indicating that the service RRC connection setup delay
exceeds the predefined threshold: Service RRC connection setup delay =
Time stamp of the RRC CONN SETUP CMP message - Time stamp of
the RRC CONN REQ message.
Soft
hand
over
Dela
ys(s)
Delay problem indicating that the outgoing soft handover delay exceeds
the predefined threshold: You can obtain the outgoing soft handover delay
by using the following formula from the source cell perspective: SHO
delay (s) = SHO complete time - SHO begin time.
Hard
hand
over
Dela
y(s)
Delay problem indicating that the outgoing hard handover delay exceeds
the predefined threshold: You can obtain the outgoing hard handover delay
by using the following formula from the source cell perspective: HHO
delay (s) = HHO complete time - HHO begin time.
Chan
nel
Swit
chov
er
Dela
ys(s)
Delay problem indicating that the outgoing channel switch delay exceeds
the predefined threshold: You can obtain the outgoing channel switch
delay by using the following formula from the source cell perspective:
Channel switch delay (s) = Channel switch complete time - Channel switch
begin time.

2436
Nastar
P
ar
a
m
et
er
Issue 03 (2015-07-30)
Ra
ng
e
Unit
Description
Relo
catio
n
Dela
y(s)
Delay problem indicating that the relocation delay exceeds the predefined
threshold: Relocation delay (s) = Relocation complete time - Relocation
time.
Outg
oing
Inter
Syste
m
Hand
over
Dela
y
(Intr
aSyste
m)(s)
Delay problem indicating that the outgoing inter-RAT handover delay

exceeds the predefined threshold (the delay occurs on the UMTS network):
You can obtain the outgoing inter-RAT handover delay by using the
following formula from the source cell perspective: Outgoing inter-RAT
handover delay = Time stamp of the IU RELEASE COMMAND message
- Time stamp of the RELOCATION REQUIRED message.
Inco
ming
Inter
Syste
m
Hand
over
Dela
y
(Intr
aSyste
m)(s)
Delay problem indicating that the incoming inter-RAT handover delay

exceeds the predefined threshold (the delay occurs on the UMTS network):
You can obtain the incoming inter-RAT handover delay by using the
following formula from the target cell perspective: Incoming inter-RAT
handover delay = Time stamp of the IU RELEASE COMMAND message
- Time stamp of the RELOCATION REQUIRED message.
Over
long
U2L
redir
ectio
n
delay
thres
hold
Delay problem indicating that the overlong U2L redirection delay exceeds
the predefined threshold, You can obtain the overlong U2L redirection
delay when the handover type is U2L redirection, and the outgoing interRAT handover (UMTS->LTE) delay exceeds the predefined threshold.

2437
Nastar
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
A
M
R
S
er
vi
ce
in
C
S
D
o
m
ai
n
De
lay
Pr
obl
em
Call
Setu
p
Dela
y
(MO
C) (s)
Delay problem indicating that the call setup delay exceeds the predefined
threshold (mobile-originated): If the first RAB is used for the VP service
in the CS domain and the RRC connection setup is caused by the mobileoriginated service, the call setup delay (s) (mobile-originated) spans from
the signaling access time to the RAB setup complete time.
Measurement point of the RAB request complete time: Time when the
RAB assignment succeeds, namely, the time when the SRNC responds to
the CN with an RAB Assignment Response message after receiving the
message indicating that the RAB setup is complete.
Measurement point of the signaling access time: Time when the SRNC
receives the RRC SETUP REQ or RELOC REQ message, or the incoming
inter-RAT handover request, from the UE.
Call
Setu
p
Dela
y
(MT
C) (s)
threshold (mobile-terminated): If the first RAB is used for the VP service
in the CS domain and the RRC connection setup is caused by the mobileterminated service, the call setup delay (s) (mobile-terminated) spans from
Call
Com
pleti
on
Dela
y
(Aler
ting)
(MO
C) (s)
Issue 03 (2015-07-30)
Delay problem indicating that the call connection delay exceeds the
predefined threshold (alerting) (mobile-originated): If the first RAB is
used for the mobile-originated AMR service in the CS domain, you can
obtain the call connection delay by using the following formula: Call
connection delay (s) (alerting) (mobile-originated) = Time stamp of the
alerting message - Signaling access time.

2438
Nastar
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
Call
Com
pleti
on
Dela
y
(Aler
ting)
(MT
C) (s)
predefined threshold (alerting) (mobile-terminated): If the first RAB is
used for the mobile-terminated AMR service in the CS domain, you can
connection delay (s) (alerting) (mobile-terminated) = Time stamp of the
RAB
Setu
p
Dela
y(s)
Delay problem indicating that the RAB setup delay exceeds the predefined
threshold: RAB setup delay (s) = RAB request complete time - RAB
request time.
Measurement point of the RAB request time: Time when the UTRAN
receives the RAB Assignment Request message from the CN.
Sh
ort
Ca
ll
Pr
obl
em
RAB
Dura
tion
(s)
Short call problem indicating that the RAB duration exceeds the
predefined lower limit: RAB duration (s) = RAB release time - RAB
request complete time.
Measurement point of the RAB release time: Time when the CN releases
the RAB; time when the SRNC receives the IU REL CMD message from
the CN (namely, the time when the CN releases the Iu interface signaling
properly); time when the RNC receives the RB REL SUCC message from
the subscriber.
Short
call
(MO
C) (s)
Issue 03 (2015-07-30)
Short call problem indicating a short-call (mobile-originated) exception:

If the first RAB is used for the AMR service in the CS domain, the actual
duration (Call duration = Time stamp of the DisConnect message - Time
stamp of the Connect Acknowledge message) of mobile-originated short
call is shorter than the threshold for mobile-originated short call.

2439
Nastar
P
ar
a
m
et
er
V
P
S
er
vi
ce
in
C
S
D
o
m
ai
n
Issue 03 (2015-07-30)
Ra
ng
e
Unit
Description
Short
call
(MT
C) (s)
Short call problem indicating a short call (mobile-terminated) exception:

If the first RAB is used for the AMR service in the CS domain, the actual
duration of mobile-terminated short call (Call duration = Time stamp of
the DisConnect message - Time stamp of the Connect Acknowledge
message) is shorter than the threshold for mobile-terminated short call.
Ser
vic
e
Qu
alit
y
Pr
obl
em
Over
high
Prop
ortio
n of
Servi
ce
Qual
ity
with
Bad
SQI
Service quality problem indicating a high proportion (%) of services with

bad SQI: The proportion of services with bad SQI is the number of
successful calls, the SQIs of which are bad, against all successful calls
initiated by subscribers.
De
lay
Pr
obl
em
Call
Setu
p
Dela
y
(MO
C) (s)
threshold (mobile-originated): If the first RAB is used for the VP service
in the CS domain and the RRC connection setup is caused by the mobileoriginated service, the call setup delay (s) (mobile-originated) spans from

2440
Nastar
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
Call
Setu
p
Dela
y
(MT
C) (s)
threshold (mobile-terminated): If the first RAB is used for the VP service
in the CS domain and the RRC connection setup is caused by the mobileterminated service, the call setup delay (s) (mobile-terminated) spans from
Issue 03 (2015-07-30)
Call
Com
pleti
on
Dela
y
(Aler
ting)
(MO
C) (s)
predefined threshold (alerting) (mobile-originated): If the first RAB is
used for the mobile-originated VP service in the CS domain, you can obtain
the call connection delay by using the following formula: Call connection
delay (s) (alerting) (mobile-originated) = Time stamp of the alerting
message - Signaling access time.
Call
Com
pleti
on
Dela
y
(Aler
ting)
(MT
C) (s)
predefined threshold (alerting) (mobile-terminated): If the first RAB is
used for the mobile-terminated VP service in the CS domain, you can
connection delay (s) (alerting) (mobile-terminated) = Time stamp of the

2441
Nastar
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
RAB
Setu
p
Dela
y(s)
request time.
Sh
ort
Ca
ll
Pr
obl
em
RAB
Dura
tion
(s)
Short call problem indicating that the RAB duration exceeds the
predefined lower limit: RAB duration (s) = RAB release time - RAB
request complete time.
Measurement point of the RAB release time: Time when the CN releases
the RAB; time when the SRNC receives the IU REL CMD message from
the CN (namely, the time when the CN releases the Iu interface signaling
properly); time when the RNC receives the RB REL SUCC message from
the subscriber.
Issue 03 (2015-07-30)
Short
call
(MO
C)(s)
Short call problem indicating a short-call (mobile-originated) exception:

If the first RAB is used for the VP service in the CS domain, the actual
duration of mobile-originated short call (Call duration = Time stamp of
message) is shorter than the threshold for mobile-originated short call.
Short
call
(MT
C)(s)
Short-call problem indicating a short-call (mobile-terminated) exception:

If the first RAB is used for the VP service in the CS domain, the actual
duration of mobile-terminated short call (Call duration = Time stamp of
message) is shorter than the threshold for mobile-terminated short call.

2442
Nastar
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
P
S
S
er
vi
ce
in
P
S
D
o
m
ai
n
De
lay
Pr
obl
em
Call
Setu
p
Dela
y
(MO
C)(s)
threshold (mobile-originated): If the first RAB is used for the PS service
in the PS domain and the RRC connection setup is caused by the mobileoriginated service, the call setup delay (s) (mobile-originated) spans from
Call
Setu
p
Dela
y
(MT
C)(s)
threshold (mobile-terminated): If the first RAB is used for the PS service
in the PS domain and the RRC connection setup is caused by the mobileterminated service, the call setup delay (s) (mobile-terminated) spans from
RAB
Setu
p
Dela
y(s)
request time.
Issue 03 (2015-07-30)

2443
Nastar
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
Slo
w
Do
wn
lin
k
Sp
ee
d
Final
ly
Nego
tiate
d
Rate
of
Dow
nlink
RAB
(kbit/
s)
Low downlink rate indicating a low downlink RAB negotiated final rate:
The downlink RAB negotiated final rate (kbit/s) is the downlink RAB
negotiated final rate when a subscriber initiates a regular PS service.
Aver
age
Dow
nlink
Thro
ughp
ut
(kbit/
s)
Low downlink rate indicating a low average downlink throughput rate:

Average downlink throughput rate (kbit/s) = Downlink throughput/
Downlink data transfer duration.
Final
ly
Nego
tiate
d
Rate
of
Upli
nk
RAB
(kbit/
s)
Low uplink rate indicating a low uplink RAB negotiated final rate: The
uplink RAB negotiated final rate (kbit/s) is the uplink RAB negotiated
final rate when a subscriber initiates a regular PS service.
Aver
age
Upli
nk
Thro
ughp
ut
(kbit/
s)
Low uplink rate indicating a low average uplink throughput rate: Average
uplink throughput rate (kbit/s) = Uplink throughput/Uplink data transfer
duration.
Slo
w
Up
lin
k
Sp
ee
d
Issue 03 (2015-07-30)

2444
Nastar
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
H
S
D
P
A
S
er
vi
ce
in
P
S
D
o
m
ai
n
De
lay
Pr
obl
em
Call
Setu
p
Dela
y
(MO
C) (s)
threshold (mobile-originated): If the first RAB is used for the HSDPA
service in the PS domain and the RRC connection setup is caused by the
mobile-originated service, the call setup delay (s) (mobile-originated)
spans from the signaling access time to the RAB setup complete time.
Call
Setu
p
Dela
y
(MT
C) (s)
threshold (mobile-terminated): If the first RAB is used for the HSDPA
mobile-terminated service, the call setup delay (s) (mobile-terminated)
RAB
Setu
p
Dela
y(s)
request time.
Issue 03 (2015-07-30)

2445
Nastar
P
ar
a
m
et
er
H
S
U
P
A
S
er
vi
ce
in
P
S
D
o
m
ai
n
Ra
ng
e
Unit
Description
Slo
w
Do
wn
lin
k
Sp
ee
d
Aver
age
Dow
nlink
Thro
ughp
ut
(kbit/
s)

De
lay
Pr
obl
em
Call
Setu
p
Dela
y
(MO
C) (s)
threshold (mobile-originated): If the first RAB is used for the HSUPA
mobile-originated service, the call setup delay (s) (mobile-originated)
Call
Setu
p
Dela
y
(MT
C) (s)
threshold (mobile-terminated): If the first RAB is used for the HSUPA
mobile-terminated service, the call setup delay (s) (mobile-terminated)
Issue 03 (2015-07-30)

2446
Nastar
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
RAB
Setu
p
Dela
y(s)
request time.
H
S
D
P
A
_
H
S
U
P
A
S
er
vi
ce
in
P
S
D
o
m
ai
n
Issue 03 (2015-07-30)
Slo
w
Up
lin
k
Sp
ee
d
Aver
age
Upli
nk
Thro
ughp
ut
(kbit/
s)
duration.
De
lay
Pr
obl
em
Call
Setu
p
Dela
y
(MO
C) (s)
threshold (mobile-originated): If the first RAB is used for the
HSDPA_HSUPA service in the PS domain and the RRC connection setup
is caused by the mobile-originated service, the call setup delay (s) (mobileoriginated) spans from the signaling access time to the RAB setup
complete time.

2447
Nastar
P
ar
a
m
et
er
Ra
ng
e
Unit
Description
Call
Setu
p
Dela
y
(MT
C) (s)
threshold (mobile-terminated): If the first RAB is used for the
HSDPA_HSUPA service in the PS domain and the RRC connection setup
is caused by the mobile-terminated service, the call setup delay (s) (mobileterminated) spans from the signaling access time to the RAB setup
complete time.
RAB
Setu
p
Dela
y(s)
request time.
Issue 03 (2015-07-30)
Slo
w
Do
wn
lin
k
Sp
ee
d
Aver
age
Dow
nlink
Thro
ugho
ut
(kbit/
s)

Slo
w
Up
lin
k
Sp
ee
d
Aver
age
Upli
nk
Thro
ugho
ut
(kbit/
s)
duration.

2448
Nastar

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Parameter
Description
Select NE(s)

NOTE

Parameter
Description
Duration
Delay
immediately.
Execute on
Issue 03 (2015-07-30)

2449
Nastar
5.8.4 Interface Description: UMTS Cell Performance Analysis

This section describes the interface that displays the results of UMTS cell performance analysis.
this interface.
Portal
l
Use either of the following methods to open the interface that displays the results of UMTS
Select an executed UMTS cell performance analysis task and double-click a result
record in the Task Result area.
Select an executed UMTS cell performance analysis task, right-click a result record in
Open the interface that displays the results of UMTS cell performance analysis (in-depth):
Interface
exception types, table of exception causes, and table of bottom N users, terminal models, or
cells. Figure 5-36 shows the analysis result interface.
Issue 03 (2015-07-30)

2450
Nastar
No.
Name
Button area
Description
l
: Export the results of Abnormal Summary during a cell

performance analysis task, namely, export the analysis results of
all cells under each exception type.
: Export the results of Abnormal Cause analysis during a cell

performance analysis task, namely, export the analysis results of
all cells under each exception cause.
NE
navigation
tree
l Upper part: Type a cell name in the Search area to quickly locate
a cell.
Table of
exception
types
Displays the number of reports and ratio under each exception type
for the selected RNC or cell under each service type. This area is
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.
Right-click on the table and choose Save As from the shortcut menu
to export this table.
4
Table of
exception
causes
Displays the number of reports and ratio under each exception cause
of an exception type for the selected RNC or cell. This area is
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.
icon to open the indepth analysis interface where you can view all abnormal call
records caused by this exception cause.
Table of
bottom N
users,
terminal
models, or
cells
Displays the number of reports related to bottom N users(N<=50),

terminal models(N<=50), or cells(N<=50) under an exception cause
for the selected RNC or cell.
l After you select a RNC in Area 2, this table displays the number
and ratio of reports caused by bottom N users, terminal models,
and cells.
and ratio of reports caused by bottom N users and terminal models.
l Select a user, a terminal model, or a cell and click the
icon to
open the in-depth analysis interface where you can view all
abnormal call records under this user, terminal model, or cell.
Issue 03 (2015-07-30)

2451
Nastar
NOTE
l Click the
based on problematic cells. For details about the interfaces, see Interface Description: UMTS
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.
l For BSC6900 V900R013C00 or earlier, the number of soft handover (outgoing/incoming) failures and
the number of hard handover (outgoing/incoming) failures for the UMTS cell performance theme are
sometimes different from those in the in-depth analysis summary table. The cause is that soft and hard
handover modules record only information about some handovers but the statistical module records
all handover attempts and successes.
5.8.5 Parameters for Viewing UMTS Cell Performance Analysis

Results
This section describes the parameters for viewing UMTS cell performance analysis results. You
can refer to the description when viewing UMTS cell performance analysis results.
Issue 03 (2015-07-30)

2452
Nastar

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Service
Type
N/
A
N/
A
Service type of a cell exception. including:
l SRAN8.
0/
GBSS15.
0/RAN
15.0
Network level
CS AMR service
CS VP service
SMS
PS Service in PS Domain (R99)
PS HSDPA service
PS HSUPA service
HSDPA_HSUPA Service in PS Domain
Composite service
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2453
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Excepti
on
Type
N/
A
N/
A
Analysis of an exception from two dimensions: the

network exception itself and the subscriber's subjective
perception.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2454
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Excepti
on
Occurr
ence
Times
[0,
+
)
Nu
mb
er
Number of abnormal times under a specific exception

type.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2455
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Ratio
(%)
[0.
00,
10
0.0
0]
Proportion of abnormal times under a specific

exception type in all the abnormal times.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2456
Nastar
Types of Network Exceptions

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
RRC
Setup
Failure
(NonService
)
N/
A
N/
A
A failure during the process from a subscriber starts

accessing the network until the non-service radio
resource control (RRC) connection setup is complete.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2457
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
RRC
Setup
Failure
(Servic
e)
N/
A
N/
A
A failure during the process from a subscriber starts

accessing the network until the service RRC
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2458
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Abnor
mal
RRC
Releas
e
N/
A
N/
A
An exception occurs during the process from an RRC

connection release is initiated until the RRC
connection release is complete.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2459
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Access
Covera
ge
Proble
m
N/
A
N/
A
A traffic policing (TP) exception or a Common Pilot

Channel (CPICH) Ec/N0 exception occurs when a
subscriber attempts to access the network.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
You are advised to set the threshold for the TP

exception or the CPICH Ec/N0 exception by using the
data source subscription function.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2460
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Outgoi
ng
SHO
Failure
N/
A
N/
A
A soft handover fails when a subscriber is using a

specific service. Statistics on outgoing soft handovers
are collected based on the source cell.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2461
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Incomi
ng
SHO
Failure
N/
A
N/
A
A soft handover fails when a subscriber is using a

specific service. Statistics on incoming soft handovers
are collected based on the target cell.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2462
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Outgoi
ng
HHO
Failure
N/
A
N/
A
A hard handover fails when a subscriber is using a

specific service. Statistics on outgoing hard handovers
are collected based on the source cell.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2463
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Incomi
ng
HHO
Failure
N/
A
N/
A
A hard handover fails when a subscriber is using a

specific service. Statistics on incoming hard handovers
are collected based on the target cell.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2464
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Cell
Update
Failure
N/
A
N/
A
A cell update fails when a subscriber is using a specific

service.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2465
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Outgoi
ng
Channe
l
Hando
ver
Failure
N/
A
N/
A
A channel switch fails when a subscriber is using a

specific service. Statistics on outgoing channel
switches are collected based on the source cell.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2466
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Incomi
ng
Channe
l
Hando
ver
Failure
N/
A
N/
A
A channel switch fails when a subscriber is using a

specific service. Statistics on incoming channel
switches are collected based on the target cell.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2467
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Relocat
ion
Failure
N/
A
N/
A
A relocation fails when a subscriber is using a specific

service.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2468
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
InterSystem
Outgoi
ng
Hando
ver
Failure
(IntraSystem
)
N/
A
N/
A
When a subscriber is using a specific service, a failure

occurs on the Universal Mobile Telecommunications
System (UMTS) network when the subscriber attempts
to perform an outgoing handover from the UMTS
network.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2469
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
InterSystem
Outgoi
ng
Hando
ver
Failure
(UMT
S>GSM
) (IntraSystem
)
N/
A
N/
A
A UMTS-to-GSM handover fails on the UMTS

network when a subscriber is using a specific service.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2470
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
InterSystem
Outgoi
ng
Hando
ver
Failure
(UMT
S>LTE)
(IntraSystem
)
N/
A
N/
A
A UMTS-to-LTE handover fails on the UMTS

l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2471
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
InterSystem
Incomi
ng
Hando
ver
Failure
(IntraSystem
)
N/
A
N/
A
Setting up the RRC connection fails when a subscriber

is performing an incoming handover from a nonUMTS network to a UMTS network.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2472
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
InterSystem
Incomi
ng
Hando
ver
Failure
(GSM>UMT
S)
(IntraSystem
)
N/
A
N/
A
A GSM-to-UMTS handover fails on the UMTS

l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2473
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
InterSystem
Incomi
ng
Hando
ver
Failure
(LTE>UMT
S)
(IntraSystem
)
N/
A
N/
A
An LTE-to-UMTS handover fails on the UMTS

l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2474
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Delay
Proble
m
N/
A
N/
A
The following delay exceptions might occur when a

subscriber attempts to access the network:
l SRAN8.
0/
GBSS15.
0/RAN
15.0
Overlong Non-Service RRC Setup Delay

Overlong Service RRC Setup Delay
Overlong Outgoing Soft Handover Delay
Overlong Incoming Soft Handover Delay
Overlong Outgoing Hard Handover Delay
Overlong Incoming Hard Handover Delay
Overlong Outgoing Channel Handover Delay
Overlong Incoming Channel Handover Delay
Overlong Migration Delay
Overlong Inter-System Outgoing Handover Delay
(Intra-System)
(UMTS->GSM)(Intra-System)
(UMTS->LTE)(Intra-System)
Overlong Inter-System Incoming Handover Delay
(Intra-System)
Overlong U2L redirection delay threshold
(GSM->UMTS)(Intra-System)
(LTE->UMTS)(Intra-System)
The exception thresholds are set when you subscribe
to source data.
Issue 03 (2015-07-30)

l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
2475
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
PDP
Activat
e
Failure
[0,
+
)
Nu
mb
er
PDP Activate fails when a subscriber is using a specific

service.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2476
Nastar
Types of Exceptions in the CS Domain-AMR/VP

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
RAB
Setup
Failure
N/
A
N/
A
After a subscriber starts accessing the network, an

exception occurs during the process from the RAB
setup starts until the RAB setup is complete.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2477
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Abnor
mal
Releas
e
N/
A
N/
A

setup is complete until the alerting message is received.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2478
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Delay
Proble
m
N/
A
N/
A

l SRAN8.
0/
GBSS15.
0/RAN
15.0
The call setup delay exceeds the predefined threshold

(mobile-originated).
(mobile-terminated).
(alerting) (mobile-originated).
(alerting) (mobile-terminated).
Overlong RAB Setup Delay
The exception thresholds are set when you subscribe
to source data.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2479
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Short
Call
Proble
m
N/
A
N/
A
If the first RAB is used for the AMR or VP service in

the CS domain, the actual call duration (Call duration
= Time stamp of the DisConnect message - Time stamp
of the Connect Acknowledgment message) of the
mobile-originated call is shorter than the short-call
threshold.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
You can set the exception threshold by using the source

l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2480
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Service
Quality
N/
A
N/
A
Any of the following exceptions that might occur after

a subscriber gains access to the network and
successfully sends a Setup message:
l SRAN8.
0/
GBSS15.
0/RAN
15.0
High Ratio of Bad SQI

You can set the exception thresholds by using the
source data subscription function.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2481
Nastar
Types of Exceptions in the CS Domain - Short Message

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
SMS
Reques
t
Failure
(MOC)
N/
A
N/
A
Initiating the request message for a mobile-originated

subscriber to access the network fails.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2482
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
SMS
Reques
t
Failure
(MTC)
N/
A
N/
A
Initiating the request message for a mobile-terminated

subscriber to access the network fails.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2483
Nastar
Types of Exceptions in the PS Domain - Services in the PS Domain/HSDPA Service

in PS Domain/HSUPA Service in PS Domain/HSDPA_HSUPA Service in PS
Domain/Composite Services
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
RAB
Setup
Failure
N/
A
N/
A

setup starts until the RAB setup is complete.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
Note: When attempting to set up the connection for an

HSDPA service, the RNC switches to the DCH and
tries to set up the connection for a PS R99 data service
if the HSDPA service setup fails. Therefore, the value
of Number of RAB Setup Failures for an HSDPA
service in analysis results is always 0.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2484
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Abnor
mal
Releas
e
N/
A
N/
A

setup is complete until the alerting message is received.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2485
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Delay
Proble
m
N/
A
N/
A

l SRAN8.
0/
GBSS15.
0/RAN
15.0

(mobile-originated).
(mobile-terminated).
The RAB setup delay exceeds the predefined
threshold.
You are advised to set the exception thresholds by
using the data source subscription function.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2486
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
DCCC
Rate
Increas
e
Failure
N/
A
N/
A
Increasing the rate by using Dynamic Channel

Configuration Control (DCCC) fails when a subscriber
attempts to initiate a call.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2487
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
DCCC
Rate
Decrea
se
Failure
N/
A
N/
A
Decreasing the rate by using DCCC fails when a

subscriber attempts to initiate a call.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2488
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Low
Downli
nk
Speed
N/
A
N/
A
The average downlink throughput rate is low when a

l SRAN8.
0/
GBSS15.
0/RAN
15.0
Average downlink throughput rate (kbit/s) = Downlink

throughput/Downlink data transfer duration.
You are advised to set the exception threshold by using
the data source subscription function.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2489
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Low
Uplink
Speed
N/
A
N/
A
The average uplink throughput rate is low when a

l SRAN8.
0/
GBSS15.
0/RAN
15.0
Average uplink throughput rate (kbit/s) = Uplink

throughput/Uplink data transfer duration.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2490
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
MultiRAB
Setup
Failure
N/
A
N/
A
Setting up the RAB for a composite service fails when

a subscriber attempts to originate a call.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2491
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
MultiRAB
Abnor
mal
Releas
e
(Includ
ing CS
Domai
n)
N/
A
N/
A
A subscriber disconnects from the network abnormally

while attempting to originate a call when the composite
service contains at least one RAB for a service in the
CS domain.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2492
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
MultiRAB
Abnor
mal
Releas
e
(Includ
ing
only PS
Domai
n)
N/
A
N/
A
A subscriber disconnects from the network abnormally

while attempting to originate a call when the composite
service contains only RABs for services in the PS
domain.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2493
Nastar

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Excepti
onal
Cause
N/
A
N/
A
Cause of a type of exceptions.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2494
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Excepti
on
Occurr
ence
Times
[0,
+
)
Nu
mb
er
Number of times that the cause of certain exceptions is

reported.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2495
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Ratio
(%)
[0.
00,
10
0.0
0]
Proportion of a cause against the number of a certain

type of exceptions.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2496
Nastar
Param
eter
Ra
ng
e
U
nit
Deep
Analys
is
N/
A
N/
A
Description
Click , to open the window for deep analysis

(namely, to be directed to the window for complaint
analysis support).
Supported
Solution
Version
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2497
Nastar
Causes of Network Exceptions

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Abnor
mal TP
on
Access
N/
A
N/
A
A TP exception occurs when a subscriber attempts to

access the network.
l SRAN8.
0/
GBSS15.
0/RAN
15.0

Remark: If the active set contains multiple cells during
access, only the counters for the first cell in this active
set are analyzed.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2498
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Abnor
mal
CPICH
Ec/N0
on
Access
N/
A
N/
A
A CPICH Ec/N0 exception occurs when a subscriber

attempts to access the network.
l SRAN8.
0/
GBSS15.
0/RAN
15.0

set are analyzed.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2499
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Abnor
mal
CPICH
RSCP
on
Access
N/
A
N/
A
A CPICH RSCP exception occurs when a subscriber

attempts to access the network (RSCP is short for
received signal code power).
l SRAN8.
0/
GBSS15.
0/RAN
15.0

set are analyzed.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2500
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
NonServic
e RRC
Access
Delay
N/
A
N/
A
The non-service RRC connection setup delay exceeds

the predefined threshold during the RRC connection
setup for a mobile-originated call.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
RRC connection setup delay = Time stamp of the RRC

CONN SETUP CMP message - Time stamp of the
RRC CONN REQ message.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2501
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
Servic
e RRC
Access
Delay
N/
A
N/
A
The service RRC connection setup delay exceeds the

predefined threshold during the RRC connection setup
for a mobile-originated call.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
RRC connection setup delay = Time stamp of the RRC

CONN SETUP CMP message - Time stamp of the
RRC CONN REQ message.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2502
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
Outgoi
ng Soft
Hando
ver
Delay
N/
A
N/
A
A subscriber successfully initiates a soft handover

when using a specific service but the outgoing soft
handover delay exceeds the predefined threshold. You
can obtain the soft handover delay by using the
following formula from the source cell perspective.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2503
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
Incomi
ng Soft
Hando
ver
Delay
N/
A
N/
A
A subscriber successfully initiates a soft handover

when using a specific service but the incoming soft
can obtain the soft handover delay by using the
following formula from the target cell perspective.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2504
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
Outgoi
ng
Hard
Hando
ver
Delay
N/
A
N/
A
A subscriber successfully initiates a hard handover

when using a specific service but the outgoing hard
can obtain the the hard handover delay by using the
following formula from the source cell perspective.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2505
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
Incomi
ng
Hard
Hando
ver
Delay
N/
A
N/
A
A subscriber successfully initiates a hard handover

when using a specific service but the incoming hard
can obtain the hard handover delay by using the
following formula from the target cell perspective.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2506
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
Outgoi
ng
Chann
el
Hando
ver
Delay
N/
A
N/
A
A subscriber successfully initiates a channel switch

when using a specific service but the outgoing channel
switch delay exceeds the predefined threshold. You can
obtain the channel switch delay by using the following
formula from the source cell perspective.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2507
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
Incomi
ng
Chann
el
Hando
ver
Delay
N/
A
N/
A
A subscriber successfully initiates a channel switch

when using a specific service but the incoming channel
switch delay exceeds the predefined threshold. You can
obtain the channel switch delay by using the following
formula from the target cell perspective.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2508
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
Migrat
ion
Delay
N/
A
N/
A
A subscriber successfully initiates a relocation when

using a specific service but the relocation delay exceeds
the predefined threshold. You can obtain the hard
handover delay by using the following formula:
Relocation delay (s) = Relocation complete timeRelocation time.
l SRAN8.
0/
GBSS15.
0/RAN
15.0

l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2509
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
InterSystem
Outgoi
ng
Hando
ver (3G
to 2G)
Delay
(IntraSystem
)
N/
A
N/
A
A subscriber successfully initiates an outgoing interRAT handover when using a specific service but the
outgoing inter-RAT handover (3G->2G) delay exceeds
the predefined threshold (the delay occurs on the
UMTS network). You can obtain the outgoing interRAT handover delay by using the following formula
from the source cell perspective: Outgoing inter-RAT
handover delay = Time stamp of the IU RELEASE
COMMAND message - Time stamp of the
RELOCATION REQUIRED message.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2510
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
InterSystem
Incomi
ng
Hando
ver (2G
to 3G)
Delay
(IntraSystem
)
N/
A
N/
A
A subscriber successfully initiates an incoming interRAT handover when using a specific service but the
incoming inter-RAT handover (2G->3G) delay
exceeds the predefined threshold (the delay occurs on
the UMTS network). You can obtain the incoming
inter-RAT handover delay by using the following
formula from the target cell perspective: Incoming
inter-RAT handover delay = Time stamp of the
UTRAN MOBILITY INFORMATION CONF
message - Time stamp of the RELOCATION
REQUIRED message.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2511
Nastar
Causes of the Exceptions in the CS Domain

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng Call
Setup
Delay
(MOC)
N/
A
N/
A
The call setup duration exceeds the predefined

threshold when a mobile-originated subscriber
attempts to access the network. If the first RAB is used
for the service in the CS domain and the RRC
connection setup is caused by the mobile-originated
service.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2512
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng Call
Setup
Delay
(MTC)
N/
A
N/
A

threshold when a mobile-terminated subscriber
for the service in the CS domain and the RRC
connection setup is caused by the mobile-terminated
service.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2513
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng Call
Compl
etion
Delay
(Alerti
ng)
(MOC)
N/
A
N/
A
The call connection delay exceeds the predefined

for the mobile-originated service in the CS domain,
you can obtain the call connection delay by using the
following formula: Call connection delay (alerting) =
Time stamp of the alerting message-Signaling access
time.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2514
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng Call
Compl
etion
Delay
(Alerti
ng)
(MTC)
N/
A
N/
A
The call connection delay exceeds the predefined

for the mobile-terminated service in the CS domain,
you can obtain the call connection delay by using the
following formula: Call connection delay (alerting) =
Time stamp of the alerting message-0Signaling access
time.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2515
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
RAB
Setup
Delay
Long
N/
A
N/
A
The RAB setup delay exceeds the predefined threshold

when a subscriber attempts to access the network. You
can obtain the RAB setup delay by using the following
formula: RAB setup delay (s) = RAB request complete
time - RAB request time.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
Measurement point of the RAB request complete time:

Time when the RAB assignment succeeds, namely, the
time when the SRNC responds to the CN with an RAB
Assignment Response message after receiving the
l SRAN8.
1/
GBSS15.
1/RAN
15.1
Measurement point of the RAB request time: Time

when the universal terrestrial radio access network
(UTRAN) receives the RAB Assignment Request
message from the CN.
l SRAN9.
0/
GBSS16.
0/
RAN16.0

l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2516
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Oversh
ort
RAB
Duratio
n
N/
A
N/
A
The RAB duration delay exceeds the predefined

threshold when a subscriber attempts to access the
network. You can obtain the RAB duration by using
the following formula: RAB duration (s) = RAB
release time - RAB request complete time.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
Measurement point of the RAB release time: Time

when the CN releases the RAB; time when the SRNC
receives the IU REL CMD message from the CN
(namely, the time when the CN releases the Iu interface
signaling properly); time when the RNC receives the
RB REL SUCC message from the subscriber.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
Measurement point of the RAB request complete time:

Time when the RAB assignment succeeds, namely, the
time when the SRNC responds to the CN with an RAB
Assignment Response message after receiving the
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2517
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Short
Call
(MOC)
N/
A
N/
A
If a call lasts shortly after a mobile-originated

subscriber accesses the network and successfully
initiates the call, the probable causes are one-way audio
or cross talk. If the first RAB is used for the service in
the CS domain, the actual call duration (Call duration
= Time stamp of the DisConnect message - Time stamp
of the Connect Acknowledge message) of the mobileterminated subscriber is shorter than the threshold for
mobile-terminated short call.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2518
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Short
Call
(MTC)
N/
A
N/
A
If a call lasts shortly after a mobile-originated

subscriber accesses the network and successfully
initiates the call, the probable causes are one-way
audio, cross talk, and disturbance call. If the first RAB
is used for the service in the CS domain, the actual call
duration (Call duration = Time stamp of the
DisConnect message - Time stamp of the Connect
Acknowledge message) of the mobile-terminated
subscriber is shorter than the threshold for mobileterminated short call.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2519
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
High
Ratio
of Bad
SQI
N/
A
N/
A
Number of times that the proportion of services with

bad SQI is high. The proportion of services with bad
SQI indicates the number of successful calls, the SQIs
of which are bad, against all successful calls initiated
by subscribers.
l SRAN8.
0/
GBSS15.
0/RAN
15.0

l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2520
Nastar
Causes of the Exceptions in the PS Domain

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng Call
Setup
Delay
(MOC)
N/
A
N/
A

for the service in the PS domain and the RRC
connection setup is caused by the mobile-originated
service, the call setup duration spans from the signaling
access time to the RAB setup complete time.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2521
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng Call
Setup
Delay
(MTC)
N/
A
N/
A

for the service in the PS domain and the RRC
connection setup is caused by the mobile-terminated
service, the call setup duration spans from the signaling
access time to the RAB setup complete time.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2522
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Overlo
ng
RAB
Setup
Delay
N/
A
N/
A
The RAB setup delay exceeds the predefined threshold

when a subscriber attempts to access the network. RAB
setup delay (s) = RAB request complete time - RAB
request time.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2523
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Low
Downli
nk
RAB
Negoti
ated
Final
Rate
N/
A
N/
A
The downlink RAB negotiated final rate is low when

a subscriber is using a data service. The downlink RAB
negotiated final rate (kbit/s) is the downlink RAB
negotiated final rate when the subscriber initiates a
regular PS service.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2524
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Low
Averag
e
Downli
nk
Throug
hput
N/
A
N/
A
The average downlink throughput rate is low when a

subscriber is using a data service: Average downlink
throughput rate (kbit/s) = Downlink throughput/
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2525
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Low
Uplink
RAB
Negoti
ated
Final
Rate
N/
A
N/
A
The uplink RAB negotiated final rate is low when a

subscriber is using a data service. The uplink RAB
negotiated final rate (kbit/s) is the uplink RAB
negotiated final rate when the subscriber initiates a
regular PS service.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2526
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Low
Averag
e
Uplink
Throug
hput
N/
A
N/
A
The average uplink throughput rate is low when a

subscriber is using a data service: Average uplink
throughput rate (kbit/s) = Uplink throughput/Uplink
data transfer duration.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2527
Nastar
Analysis of Bottom Subscribers

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
User
Name
N/
A
N/
A
The system assigns a unique identifier to the bottom

subscriber troubled with an exception.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2528
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Excepti
on
Occurr
ence
Times
[0,
+
)
Nu
mb
er
Number of the exceptions that trouble a subscriber

under the cause of a certain type of exceptions.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2529
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Ratio
(%)
[0.
00,
10
0.0
0]
Proportion of the exceptions that trouble a subscriber

against all exceptions.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2530
Nastar
Param
eter
Ra
ng
e
U
nit
Deep
Analys
is
N/
A
N/
A
Description
Click
to open the window for deep analysis
analysis support).
Supported
Solution
Version
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2531
Nastar
Analysis of Bottom Cells

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Cell
Identit
y
N/
A
N/
A
The identity of a bottom problematic cell is in the

following format: RNC ID: Cell ID.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2532
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Cell
Name
1 to
64
cha
rac
ters
N/
A
Name of the bottom cell to which an exception occur.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2533
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Excepti
on
Occurr
ence
Times
[0,
+
]
Nu
mb
er
Number of the exceptions that occur in a cell under the

cause of a certain type of exceptions.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2534
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Ratio
(%)
[0.
00,
10
0.0
0]
Proportion of the exceptions that occur in a cell against

all exceptions.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2535
Nastar
Param
eter
Ra
ng
e
U
nit
Deep
Analys
is
N/
A
N/
A
Description
Click
analysis support).
Supported
Solution
Version
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2536
Nastar
Analysis of Bottom Terminal Models

Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
IMEITAC
00
00
00
0099
99
99
99
N/
A
Type identifier of the bottom terminal to which an

exception occur.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2537
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Termin
al
Model
N/
A
N/
A
Terminal model that is obtained by the terminal type

management function based on IMEI-TAC.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2538
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Excepti
on
Occurr
ence
Times
[0,
+
]
Nu
mb
er
Number of the exceptions that occur in a certain type

of terminals under the cause of a certain type of
exceptions.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2539
Nastar
Param
eter
Ra
ng
e
U
nit
Description
Supported
Solution
Version
Ratio
(%)
[0.
00,
10
0.0
0]
Proportion of the exceptions that occur in a terminal

against all exceptions.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2540
Nastar
Param
eter
Ra
ng
e
U
nit
Deep
Analys
is
N/
A
N/
A
Description
Click
analysis support).
Supported
Solution
Version
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.0
l SRAN10
.0/
GBSS17.
0/
RAN17.0
l SRAN10
.1/
GBSS17.
1/
RAN17.1
l SRAN11
.0/
GBSS18.
0/
RAN18.0
5.8.6 FAQ: What Do I Do When NE Objects Are Missing from the

Analysis Results?
You have selected multiple NE groups when creating a UMTS cell performance analysis task.
The analysis results, however, display the results of only some NE groups.
Symptom
You have selected multiple NE groups when creating an analysis task. The analysis results,
however, display the results of only some NE groups.
For example:
Issue 03 (2015-07-30)

2541
Nastar
1.
You have created the following two NE groups in the NE Group Management window:
NEgroup1 and NEgroup2.
2.
You have selected the two NE groups when creating a UMTS cell performance analysis
task.
3.
After the task execution is complete, you can find the analysis results of only one NE group.
Cause
The UMTS cell performance analysis results display only the NEs, NE groups, and cells that
experience exceptions.
5.9 UMTS Network Geographic Observation

5.9.1 Basics of UMTS Network Geographic Observation

This section describes the basics of UMTS network geographic observation, including the
function, technical specifications and feature restrictions. The basic knowledge helps users
perform operations related to UMTS network geographic observation. You must read this section
before starting the analysis.
NOTE
UMTS 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.
UMTS network geographic observation supports network coverage geographic observation,
network traffic geographic observation, and network event geographic observation:
l
Issue 03 (2015-07-30)
Network coverage geographic observation supports the geographic rendering for the
following indicators: CPICH Ec/No, CPICH RSCP, soft handover area, pilot pollution area,
LAC stability, primary serving cell, and confidence level.
2542
Nastar
Functions:
It replaces traditional simulation means to display the coverage of each serving cell on
the live network, helping 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, and renders the results by grid. Each level measures the proportion of a
specified number of confidence MRs to the total number of MRs in the 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, HSDPA/
HSUPA traffic volume and throughput, UL/DL PS R99 traffic volume and throughput.
Function: It displays the traffic distribution of each area on the live network on a map and
helps telecom operators identify traffic hot spots.
Network event geographic observation supports the geographic rendering for the following
indicators: number of call drops, number of soft handover failures, number of hard handover
failures, and number of inter-RAT handover failures.
Functions: 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
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.
l



Issue 03 (2015-07-30)

2543
Nastar
Function Principles
The data source of network geographic observation is the CHR and MR data on the NE side.
NOTE
Issue 03 (2015-07-30)

2544
Nastar

User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Issue an
MML
comma
nd
eS
AU
U20
00/
M20
00
Forward
the
MML
comma
nd
U2
000
/
M2
000
BSC/
RNC

Upload
raw data
BS
C/
RN
C
SAU
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nas
tar
Ser
ver
eSA
U

Deliver
a datapreproc
essing
task
(direct)
eS
AU
SAU

Upload
preproc
essed
data
(direct)
SA
U
eSA
U
2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

2545
Nastar
User
Operat
ion
Proced
ure
So
urc
e
Dest
inati
on
Purpose
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nas
tar
Ser
ver
eSA
U

ready on the eSAU.
Return
data
query
results
eS
AU
Nast
ar
Serv
er

4.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nas
tar
Ser
ver
eSA
U

Upload
data
analysis
results
eS
AU
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for UMTS Network Geographic Observation

of analysis time.
NOTE
Issue 03 (2015-07-30)
Item
Execution type

2546
Nastar
Item

analysis task
l <= 6000 cells (when the number of UMTS basic licenses is

less than or equal to 50,000 cells)
l <= 12,000 cells (when the number of UMTS basic licenses is
l <= 18,000 cells (when the number of UMTS basic licenses is
Number of allowed
analysis tasks

one analysis task
7 days

task
<= 25 minutes

15 days

15 days
5.9.2 Preparations for UMTS Network Geographic Observation

Before starting a UMTS network geographic observation, you check the user rights and the
matching environment, and prepare relevant data to ensure that the UMTS network geographic
observation task is performed normally. You must read this section before starting the analysis.

l
Check that you have applied for a valid license for UMTS network geographic observation.
Check that you have the operation rights to subscribe to UMTS network geographic
observation data upon login.
Check that you have the operation rights to create UMTS network geographic observation
tasks upon login, and the operation rights to operate the analyzed NEs.

task successfully.
Issue 03 (2015-07-30)

2547
Nastar

Data
Type
Function
Operation
Config
uratio
n Data
(Mand
atory)

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.

Data.
Expired configuration data may cause incorrect cell
Engin
eering
Param
eters
(Mand
atory)
Issue 03 (2015-07-30)
The engineering
longitude and latitude
and the antenna azimuth.
The information is used
for the effective
identification of
neighboring cell
information and
theme analysis.


2548
Nastar
Data
Type
Function
Operation
Map
File
(Optio
nal)
The map file for a

analysis result
result on the map.

(Optional).

l
If you want to analyze the PS network geographic observation function, check that the PS
5.9.3 Process of UMTS Network Geographic Observation

This section describes the process of UMTS network geographic observation and each procedure
in the process.
l
Prerequisite
Process
Prerequisite
UMTS Network Geographic Observation.
Process
Issue 03 (2015-07-30)

2549
Nastar
Issue 03 (2015-07-30)

2550
Nastar

No.
Proced
ure
Description
Reference
(1)
Check
whether
analysis
data is
integrat
ed

3.6 Checking
the Integrity
of Analysis
Data
Procedure:
1. Choose Data Type > Network Analysis > UMTS
*** indicates the data type including MR and CHR.
4. Click Query.
window.
analysis task.
(2).
NOTE
(2)
Subscri
be to
analysis
data
(basic)

Procedure:
1. Click the UMTS tab in the Data Subscription
Management window.
3.5
Subscribing
to Analysis
Data

Observation Data(CHR) and Network Geographic
Observation Data(MR) to ON.
Modification.
5. Click Confirm.
Issue 03 (2015-07-30)

2551
Nastar
No.
Proced
ure
Description
Subscri
be to
analysis
data
(applica
tion)

Reference
Procedure:
1. Click the UMTS tab in the Data Subscription
Management window.
tab page.
Geographic observation Analysis Parameter
Setting dialog box.
5. Click Confirm.
Parameters.
Check
whether
analysis
data is
integrat
ed

Procedure:
1. Choose Data Type > Network Analysis > UMTS
*** indicates the data type including MR and CHR.
3.6 Checking
the Integrity
of Analysis
Data

4. Click Query.
window.
analysis task.
technical support.
Issue 03 (2015-07-30)

2552
Nastar
No.
Proced
ure
Description
Reference
(3)
Create
an
analysis
task

Analysis > UMTS Network Geographic Observation
in the navigation tree of the Analysis Task
Management window.
l For
details,
see 3.7
Creating
an
Analysis
Task.
Procedure:
1. Double-click UMTS Network Geographic
observation.
2. Specify the task name and remarks. Then, click Next.
analyzed.
Grid Resolution for displaying terminal geographic
observation results. Then, click Next.
Nastar obtains the observation results for the specified
time period.
l For details
about the
parameter
s, see
Analysis
Task
Paramete
rs.
6. Click Finish.
(4)
View
analysis
results

Procedure:
Geographic observation from the shortcut menu.
2. In the Geographic observation window, view the
Issue 03 (2015-07-30)

l For
details,
see 3.8
Querying
Analysis
Results.
l For details
on the
descriptio
n of the
window
for
showing
analysis
results,
see 5.9.4
Interface
Descripti
on:
UMTS
Network
Geograp
hic
Observat
ion.
2553
Nastar
No.
Proced
ure
Description
Reference
(5)
Export
analysis
results

upper left part of the Geographic observation window.
l For
details,
see 3.10
Exportin
g
Analysis
Reports.
Procedure:
3. Click Save.
l For details
on the
descriptio
n of the
window
for
showing
analysis
results,
see 5.9.4
Interface
Descripti
on:
UMTS
Network
Geograp
hic
Observat
ion.

Basic Subscription
Issue 03 (2015-07-30)

2554
Nastar
Parameter
Description
Network
Geographic
Observation
Data (CHR)
You can click

is unavailable.
Network
Geographic
Observation
Data (MR)
You can click
Parameter
Description
Range Value
Downlink Ec/
No(dB)<= X
Indicates the threshold for determining poor

coverage quality on the downlink in the
threshold for Traffic of bad RxQual area.
X range: [-25,0]. The

default value is -15.0.
The Nastar obtains only the data with the

downlink receive quality level smaller than or
equal to X.
Issue 03 (2015-07-30)

2555
Nastar
Parameter
Description
Range Value
1st best CPICH

RSCP- 4th best
CPICH RSCP
(dB)<Y
Defines the RSCP difference between the best

serving cell and the 4th cell.
Y range: [0,50]. The

default value is 5.
In all active sets, monitor sets, and detected sets,

when the number of cells whose RSCP varies
by less than the value of Y as compared to that
of the best serving cell, and the RSCP of all the
top 4 cells is greater than or equal to M or N, the
Nastar determines that pilot pollution has
occurred.
For CS domain services: The Nastar only
obtains the data when the RSCP difference
between the best serving cell and the 4th cell is
smaller than Y and the RSCP value of the top 4
cells is greater than or equal to M.
For PS domain services: The Nastar only
obtains the data when the RSCP difference
between the best serving cell and the 4th cell is
smaller than Y and the RSCP value of the top 4
cells is greater than or equal to N.
CS RSCP
(dBm)>=M
Defines the lower RSCP threshold for CS

domain services.
X range: [-116,-25]. The

default value is -95.
PS RSCP
(dBm)>=N
Defines the lower RSCP threshold for PS

domain services.
X range: [-116,-25]. The

default value is -95.

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

Issue 03 (2015-07-30)

2556
Nastar
NE information
Parameter
Description
Select NE(s)

l <= 6000 cells (when the number of UMTS basic licenses is less than
or equal to 50,000 cells)
l <= 12,000 cells (when the number of UMTS basic licenses is less than
l <= 18,000 cells (when the number of UMTS basic licenses is less than
NOTE
Parameter
Description
Grid Resolution
Settings

results.
100m*100m.

Parameter
Description
Duration
Delay
immediately.
Busy hours
Issue 03 (2015-07-30)

2557
Nastar
Parameter
Description
Execute on

Param
eter
Description
Note
Start
time

Period

Repeat
times

Delay
by
(hours)
Whole
day

NOTE

hours.

NOTE
at the start time.
01/01/2013 14:00:00, Start time is
03:00:00.
01/02/2013 14:00:00, Start time is
executes the task.

parameter.
Issue 03 (2015-07-30)

2558
Nastar
Param
eter
Description
Busy
hours

in each period.
Note

busy time.
5.9.4 Interface Description: UMTS Network Geographic

Observation
This section describes the interface that displays UMTS network geographic display results.
Navigation Path
Use either of the following methods to open the interface that displays UMTS network
geographic observation results:
l
Select a finished UMTS network geographic observation task and double-click a result
record in the Task Result area.
Select a finished UMTS network geographic observation task, right-click a result record
in the Task Result area, and choose Geographic Observation from the shortcut menu.
Interface
Figure 5-39 shows the interface that displays network geographic observation results on grid
maps.
Issue 03 (2015-07-30)

2559
Nastar
Figure 5-39 Interface for showing UMTS network geographic observation results
NOTE
This section describes only the functions supported by UMTS network geographic observation. For detailed
operations of each function, see 3.2.3 Interface Description: Geographic Observation Results.
Issue 03 (2015-07-30)
N
o.
Item
Description
Button
area

2560
Nastar
N
o.
Item
Description
Navigation
tree

NOTE

map interface.
of grids within a polygon area is 1000. If the number of grids
exceeds the threshold, draw the polygon area again.
polygon.
visible.
menu to reset the grid display effect or the number of measurement
reports (MRs) to be filtered within a grid.
NOTE
Issue 03 (2015-07-30)

2561
Nastar
N
o.
Item
Description
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. That is, only the results met the parameter value can
be displayed in the map window.
To query Pilot Pollution Area(U), you can set the service types
and service EcNO values on the Parameter tab page to collect
statistics on pilot pollution areas.
To query Poor-Quality Traffic Distribution(U), you can set the
poor-quality traffic ratio on the Parameter tab page to collect
statistics on the distribution of voice traffic with poor quality.
Geographi
c
observatio
n area

distinct colors by default. However, only the analysis results of the last
selected KPI are visible.
NOTE
function is enabled, the Nastar displays only the filtered sites. However, no
matter whether the filtering function is enabled or disabled, the Nastar
, the
original window.
Issue 03 (2015-07-30)

2562
Nastar
N
o.
Item
Description
Grid
Details
area
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.
Legend
details area
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.
Informatio
n area

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
5.9.5 Parameters for Viewing UMTS Network Geographic

Observation Results
This section describes the parameters for querying UMTS network geographic observation
results. Read this section before querying UMTS network geographic observation results.
Issue 03 (2015-07-30)

2563
Nastar

Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Primar
y
Servin
g Cell
(U)
N/A
N/A
The traffic map is rendered based on the cells that

serve as primary serving cells most frequently in
MRs in the raster view. If some cells serve as
primary serving cells for the same number of
times, the traffic map is rendered based on the
primary serving cell in the MR last reported.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.
0
l SRAN10
.0/
GBSS17.
0/
RAN17.
0
l SRAN10
.1/
GBSS17.
1/
RAN17.
1
l SRAN11
.0/
GBSS18.
0/
RAN18.
0
Issue 03 (2015-07-30)

2564
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
CPIC
H
RSCP
(U)
[-116,
-25]
dBm
The traffic map is geographically rendered based

on the average RSCP value in MRs in the raster
view.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.
0
l SRAN10
.0/
GBSS17.
0/
RAN17.
0
l SRAN10
.1/
GBSS17.
1/
RAN17.
1
l SRAN11
.0/
GBSS18.
0/
RAN18.
0
Issue 03 (2015-07-30)

2565
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
CPIC
H Ec/
No(U)
[-31.5
,0]
dB
The traffic map is rendered based on the average

received signal quality (RxQual) in MRs in the
raster view.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.
0
l SRAN10
.0/
GBSS17.
0/
RAN17.
0
l SRAN10
.1/
GBSS17.
1/
RAN17.
1
l SRAN11
.0/
GBSS18.
0/
RAN18.
0
Issue 03 (2015-07-30)

2566
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
LAC
Stabilit
y(U)
[0.00,
100.0
0]

percentage of the MRs containing serving cells
corresponding to the LAC occurring most
frequently to the total number of MRs in the raster
view.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.
0
l SRAN10
.0/
GBSS17.
0/
RAN17.
0
l SRAN10
.1/
GBSS17.
1/
RAN17.
1
l SRAN11
.0/
GBSS18.
0/
RAN18.
0
Issue 03 (2015-07-30)

2567
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
SHO
Area
(U)
[0.00,
100.0
0]

percentage of MRs in the soft handover state to the
total number of MRs in the raster view.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
If the active set of an MR contains two or more

cells, the MR is in the soft handover state.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.
0
l SRAN10
.0/
GBSS17.
0/
RAN17.
0
l SRAN10
.1/
GBSS17.
1/
RAN17.
1
l SRAN11
.0/
GBSS18.
0/
RAN18.
0
Issue 03 (2015-07-30)

2568
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Pilot
Polluti
on
Area
(U)
[0,
+)
Num
ber
The traffic map is rendered based on the number

of times that pilot pollution occurs during which
the average Ec/No of the CS/PS service is smaller
than a specific threshold value in the raster view.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
Pilot pollution: If a periodic MR in the raster view

meets the following criteria, pilot pollution occurs
once:
1. The number of neighboring cells is greater than
three; 2. Cell pilot RSCP is greater than X; 3. Cell
1 pilot RSCP minus Cell 4 pilot RSCP is less than
a specific threshold value.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.
0
l SRAN10
.0/
GBSS17.
0/
RAN17.
0
l SRAN10
.1/
GBSS17.
1/
RAN17.
1
l SRAN11
.0/
GBSS18.
0/
RAN18.
0
Issue 03 (2015-07-30)

2569
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
l SRAN8.
0/
GBSS15.
0/RAN
15.0
l SRAN8.
1/
GBSS15.
1/RAN
15.1
UE
TxPow
er(U)
l SRAN9.
0/
GBSS16.
0/
RAN16.
0
(-50,3
3)
dBm
The traffic map is rendered based on the average

UE TxPower value, which is calculated based on l SRAN10
AMR-service-related MRs, for the best cell in the
.0/
raster view.
GBSS17.
0/
RAN17.
0
l SRAN10
.1/
GBSS17.
1/
RAN17.
1
l SRAN11
.0/
GBSS18.
0/
RAN18.
0
Issue 03 (2015-07-30)

2570
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
l SRAN8.
0/
GBSS15.
0/RAN
15.0
DL
Poor
Covera
ge
Area
(U)

of MRs, which meet the criteria for weak coverage,
for the best cell in the raster view.
The criteria for determining weak coverage are as
follows:
[0,
+)
Num
ber
1. Obtain the RSCP and Ec/No values for cells in

all active sets and monitoring sets based on the
intra-frequency periodical MRs or intra-frequency
cell list containing the best cell.
2. If the maximum RSCP value contained in an MR
is equal to or less than the threshold for weak
coverage_RSCP, and the maximum Ec/No value
is equal to or less than the threshold for weak
coverage_Ec/No, the MR is determined as a weakcoverage MR. (The preceding thresholds are set
during data subscription.)
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.
0
l SRAN10
.0/
GBSS17.
0/
RAN17.
0
l SRAN10
.1/
GBSS17.
1/
RAN17.
1
l SRAN11
.0/
GBSS18.
0/
RAN18.
0
Issue 03 (2015-07-30)

2571
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Confid
ence
Level
(U)
[0.00,
100.0
0]
The traffic map is rendered based on the theoretical

precision of the positioning method used by MRs
and on the percentage of MRs of specified high
confidence levels in all MRs in the raster view.
l SRAN8.
0/
GBSS15.
0/RAN
15.0
All MRs are positioned based on the following

levels that are divided by theoretical precision: A,
B, C, D, and E. You can specify N (N > 5) high
confidence levels.
l Lev_A: indicates a precision of 50 m to 80 m.
It is used for positioning MRs reported only by
AGPS or distributed base stations.
l Lev_B: indicates a precision of 80 m to 120 m.
It is used for RRT triangular positioning or for
high-score feature database-based matching.
l Lev_C: indicates a precision of 120 m to 200
m. It is used for positioning MRs related to
three neighboring cells that are served by
different base stations.
l Lev_D: indicates a precision of 200 m to 350
m. It is used for positioning MRs reported by
two base stations.
l Lev_E: indicates a precision of over 350 m. It
is used for positioning MRs in any other
scenarios, for example, for positioning MRs
reported by one base station.
l SRAN8.
1/
GBSS15.
1/RAN
15.1
l SRAN9.
0/
GBSS16.
0/
RAN16.
0
l SRAN10
.0/
GBSS17.
0/
RAN17.
0
l SRAN10
.1/
GBSS17.
1/
RAN17.
1
l SRAN11
.0/
GBSS18.
0/
RAN18.
0
Issue 03 (2015-07-30)

2572
Nastar
Network Traffic Map

Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Voice
Traffic
Distrib
ution
(U)
[0,
+)
Num
ber
The traffic map is rendered based on the traffic

volume (unit: number of MRs) of voice services
(default service, AMR) in the raster view.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2573
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
PoorQualit
y
Traffic
Distrib
ution
(U)
[0,
+)
Num
ber
If the percentage of the MRs containing the Ec/No

value of voice services (AMR by default) lower
than a specified threshold (-15 dB by default) in all
the MRs in the raster view is higher than a specified
threshold (10% by default), the traffic map is
rendered based on the traffic volume (measured by
the number of MRs) of voice services with poor
coverage quality in the raster view.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2574
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
HSDP
A
Traffic
Volum
e(U)
[0,
+)
KB
RAN13.0 (BSC6900 V900R013C00): The Nastar

collects statistics related to the HSDPA traffic over
the RLC layer and displays the statistical results
using different distinct colors in the traffic map.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
RAN14.0 (BSC6900 V900R014C00) or a later

version: The Nastar collects statistics related to the
HSDPA traffic over the PDCP layer and displays
the statistical results using different distinct colors
in the traffic map.
NOTE
The value range of the parameter is displayed in the
format of scientific notation.
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2575
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
HSDP
A
Throug
hput
(U)
[0,
+)
kbit/
s
RAN13.0 (BSC6900 V900R013C00): The Nastar

collects statistics related to the HSDPA traffic rate
over the RLC layer and displays the statistical
results using different distinct colors in the traffic
map.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
RAN14.0 (BSC6900 V900R014C00) or a later

version: The Nastar collects statistics related to the
HSDPA traffic rate over the PDCP layer and
displays the statistical results using different
distinct colors in the traffic map.
l SRAN8.
1/
GBSS15
.1/RAN
15.1
NOTE
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2576
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
HSUP
A
Traffic
Volum
e(U)
[0,
+)
KB
The Nastar collects statistics related to the HSUPA

traffic over the MAC-d layer and displays the
statistical results using different distinct colors in
the traffic map.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
NOTE
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2577
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
HSUP
A
Throug
hput
(U)
[0,
+)
kbit/
s
The Nastar collects statistics related to the HSUPA

traffic rate over the MAC-d layer and displays the
statistical results using different distinct colors in
the traffic map.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
NOTE
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2578
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
UL PS
R99
Traffic
Volum
e (U)
[0,
+)
KB
The Nastar collects statistics related to the uplink

PS R99 traffic over the PDCP layer and displays
the statistical results using different distinct colors
in the traffic map.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
NOTE
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2579
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
UL PS
R99
Throug
hput
(U)
[0,
+)
kbit/
s
The Nastar collects statistics related to the uplink

PS R99 traffic rate over the PDCP layer and
l SRAN8.
0/
GBSS15
.0/RAN
15.0
NOTE
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2580
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
DL PS
R99
Traffic
Volum
e(U)
[0,
+)
KB
The Nastar collects statistics related to the

downlink PS R99 traffic over the PDCP layer and
l SRAN8.
0/
GBSS15
.0/RAN
15.0
NOTE
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2581
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
DL PS
R99
Throug
hput
(U)
[0,
+)
kbit/
s
The Nastar collects statistics related to the

downlink PS R99 traffic rate over the PDCP layer
and displays the statistical results using different
l SRAN8.
0/
GBSS15
.0/RAN
15.0
NOTE
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2582
Nastar
Network Event Map

Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Call
Drops
(U)
[0,
+)
Num
ber

of call drops in the raster view.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2583
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
SHO
Failure
s(U)
[0,
+)
Num
ber

of failed soft handovers in the raster view.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2584
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
HHO
Failure
s(U)
[0,
+)
Num
ber

of failed hard handovers in the raster view.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2585
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
IRAT
HO
Failure
s(U)
[0,
+)
Num
ber

of inter-RAT handover failures (UMTS to GSM
handover and UMTS to LTE handover) in the
raster view.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN10
.0/
GBSS17
.0/
RAN17.
0
l SRAN10
.1/
GBSS17
.1/
RAN17.
1
l SRAN11
.0/
GBSS18
.0/
RAN18.
0
5.10 VIP Analysis

Issue 03 (2015-07-30)

2586
Nastar

NOTE

Function Scenarios
l

l
Issue 03 (2015-07-30)
2587
Nastar
GSM.

onsite.
l

l
of short calls.

a problem.
Issue 03 (2015-07-30)

2588
Nastar

Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
GS
M
<= 500/BSC
l All-signaling
analysis on CS
services: A
interface
(3GPP-48.008)
signaling, Abis
interface
(3GPP-48.058)
signaling, and
Um interface
(3GPP-44.018/
44.060)
signaling.
If you want to view

the all signaling
information on CS
domain, check that
the matching
BSC6900 version
is V900R011C00
to view the all
signaling
information on PS
domain, check that
the matching
BSC6900 version
is V900R014C00
or later.
For VIP
subscribers of
Important level
who subscribe to
complete signaling
procedure will be
function, and you
can double-click a
signaling record
and then analyze
detailed signaling
contents in the
displayed window.
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.
l All-signaling
analysis on PS
services: Gb
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 03 (2015-07-30)

2589
Nastar
Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
UM
TS
l <= 100/RNC
(BSC6900
V900R013C0
0 or later
version)
Iu interface (3GPP
TS 25.413)
signaling, Iur
interface (3GPP TS
25.423) signaling,
Iub interface
(3GPP TS 25.433)
signaling, Uu
interface (3GPP TS
25.331) signaling.
If you want to view

the all signaling
information, check
that the matching
BSC6900 version
is V900R013C00
or later.
For VIP
subscribers of
Important level
who subscribe to
complete signaling
procedure will be
displayed in the
deep analysis
function, you can
double-click a
signaling record
and then analyze
detailed signaling
contents in the
displayed window.
l <= 500/RNC
(BSC6900
V900R016C0
0 or later
version)
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.
Issue 03 (2015-07-30)

2590
Nastar
Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
LTE
<= 500/HSS
Signaling
messages on the
S1-MME interface
(3GPP
interface (3GPP
interface (3GPP
LTE3900
V100R008C00 or
later; U2000/
M2000
V200R013C00SP
C230 or later;
HSS9860
V900R008C01 or
later.
The in-depth
analysis function
displays signaling
procedures in
charts and allows
you to double-click
a signaling
message and
analyze details
about the signaling
message in the
displayed window.
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.
Note: This function

allows you to
analyze the
signaling
procedures,
including RRC
connection setup
and release, eRAB
setup and release,
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 03 (2015-07-30)
Note: You can

analyze the key
signaling
procedures of
common
subscribers other
than the 500
Important VIP
subscribers only in
LTE3900
V100R005C00SP
C370 or later.

2591
Nastar
Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
Mult
iRAT
netw
orks
<= 500 of all the

RATs on the
entire network.
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.

Data Source
Issue 03 (2015-07-30)

2592
Nastar
NOTE
the Encryption Key.
CHR data.
Function Principles
NOTE
scheme.
Issue 03 (2015-07-30)

2593
Nastar
Issue 03 (2015-07-30)

2594
Nastar

User
Oper
ation
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
1.
Subscr
ibe to
basic
data.
GSM
/
UMT
S
netw
ork
Issue
basic
data
subscri
ption
comma
nds
(GSM/
UMTS
).
Nast
ar
Serv
er
eSA
U

Issue
MML
comma
nds.
eSA
U
U200
0/
M20
00

M2000.
Forwar
d
MML
comma
nds.
U20
00/
M20
00
BSC/
RNC

generate raw data.
Upload
raw
data.
BSC/
RNC
SAU
Issue
basic
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

Issue
MML
comma
nds.
eSA
U
U200
0/
M20
00

M2000.
Forwar
d
MML
comma
nds.
U20
00/
M20
00
SGS
N/
MM
E

PS
Core
netw
ork
Issue 03 (2015-07-30)

2595
Nastar
User
Oper
ation
Scen
e
LTE
netw
ork
Proce
dure
Sour
ce
Dest
inati
on
Purpose
Upload
raw
data.
SGS
N/
MM
E/
GGS
N/
SAE
-GW
PS
SAU
Issue
basic
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

Issue
subscri
ption
comma
nds.
eSA
U
U200
0/
M20
00

M2000.
Forwar
d
subscri
ption
comma
nds.
U20
00/
M20
00
eNod
eB

Upload
raw
data.
eNod
eB/
MM
E
NOTE
enabled.

Trace
Serve
r/
LTE
SAU

NOTE
Issue 03 (2015-07-30)

2596
Nastar
User
Oper
ation
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
2.
Subscr
ibe to
applic
ation
data.
GSM
/
UMT
S
netw
ork
Issue
applica
tion
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

eSAU.
Deliver
a dataprepro
cessing
task
(direct)
.
eSA
U
SAU

Upload
prepro
cessed
data
(direct)
.
SAU
eSA
U
Issue
applica
tion
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

Deliver
a dataprepro
cessing
task
(direct)
.
eSA
U
PS
SAU

Upload
prepro
cessed
data
(direct)
.
PS
SAU
eSA
U
PS
Core
netw
ork
Issue 03 (2015-07-30)

2597
Nastar
User
Oper
ation
Issue 03 (2015-07-30)
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
LTE
netw
ork
Issue
applica
tion
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

Deliver
a
prepro
cessing
task
(direct)
.
eSA
U
LTE
SAU

Upload
prepro
cessed
data
(direct)
.
LTE
SAU
eSA
U

Issue
data
query
comma
nds.
Nast
ar
Serv
er
eSA
U

Return
data
query
results.
eSA
U
Nasta
r
Serve
r

Nastar client.
Issue
task
executi
on
comma
nds.
Nast
ar
Serv
er
eSA
U

aggregate data.
Upload
data
analysi
s
results.
eSA
U
Nasta
r
Serve
r

3.
Check
the
integri
ty of
analys
is data.
4.
Create
and
execut
e an
analys
is task.

2598
Nastar
User
Oper
ation
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
5.
View
analys
is
results
.
Displa
y
analysi
s
results.
Nasta
r
Serve
r

of analysis time.
NOTE
Item
Execution type

analysis task
task
Number of allowed
analysis tasks

analysis.

NOTE

one analysis task
Issue 03 (2015-07-30)


2599
Nastar
Item

task
l GSM: 75 minutes
l UMTS: 90 minutes
l LTE: 10 minutes

l GSM: 30 days
l UMTS: 30 days
l LTE: 30 days
l PS Core: 30 days

l GSM: 30 days
l UMTS: 30 days
l LTE: 30 days
l PS Core: 30 days

l

Issue 03 (2015-07-30)

2600
Nastar

Functi
on
Required license

Management > User)
Data
subscri
ption
manage
ment
l GSM/UMTS/LTE
FDD/LTE TDD/PS
Core basic function
license

NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.

be analyzed.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.
l GSM/UMTS/LTE
FDD/LTE TDD/PS
Core VIP analysis
license
Issue 03 (2015-07-30)

2601
Nastar
Functi
on
Required license

Management > User)
NOTE
licenses for basic
functions and VIP
of all RATs.
RAT depends on the
GSM
VIP
analysi
s

license
l GSM VIP analysis
license

Operation Rights
Observation.
Issue 03 (2015-07-30)

2602
Nastar
Functi
on
Required license

Management > User)
UMTS
VIP
analysi
s

license

Operation Rights
l UMTS VIP analysis

license

Observation.
Issue 03 (2015-07-30)

2603
Nastar
Functi
on
Required license

Management > User)
LTE
TDD
VIP
analysi
s
l LTE TDD basic

function license

NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.

Observation.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.

license
display of the CSFB
counters.
VoLTE analysis
license, only for
Issue 03 (2015-07-30)

2604
Nastar
Functi
on
Required license

Management > User)
LTE
FDD
VIP
analysi
s
l LTE FDD basic

function license

NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.

Observation.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.

license
display of the CSFB
counters.
VoLTE analysis
license, only for
Issue 03 (2015-07-30)

2605
Nastar
Functi
on
Required license

Management > User)
PS
Core
VIP
analysi
s

license

Operation Rights

license
VoLTE signaling
analysis license
analysis license
display of the CSFB
counters.

Observation.
Issue 03 (2015-07-30)

2606
Nastar
Functi
on
Required license

Management > User)
GSM/
UMTS/
LTE
TDD/
LTE
FDD/
PS
Core
combin
ed
analysi
s
l GSM/UMTS/LTE
FDD/LTE TDD/PS
Core basic function
license

NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.

of each network.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.
l GSM VIP analysis

license
l UMTS VIP analysis
license
license
license
license
Issue 03 (2015-07-30)

2607
Nastar
Functi
on
Required license

Management > User)
Comm
on

Identity
task creation.

task successfully.
Data
Type
Function
Operation
Config
uratio
n Data
(Mand
atory)

information in MR
handed over.

Data.

NOTE
data.
Issue 03 (2015-07-30)

2608
Nastar
Data
Type
Function
Operation
VIP
Infor
matio
n
(Mand
atory)

VIP user and IMSI
information. Before
subscribing to VIP
the VIP group.

NOTE
Engin
eering
Param
eters
(Optio
nal)
The engineering
You do not need to
parameters if the
required.

Issue 03 (2015-07-30)

2609
Nastar
Data
Type
Function
Operation
Map
File
(Optio
nal)
The map file for a

analysis result
result on the map.

(Optional).
Mailb
ox
Infor
matio
n
(Optio
nal)

Nastar needs the
information for
needed.


NOTE
Issue 03 (2015-07-30)

2610
Nastar

Net
wor
k
Description
GSM

(or later).
(or later).
UM
TS

(or later).
Issue 03 (2015-07-30)

2611
Nastar
Net
wor
k
Description
LTE
NOTE
(RH2288).
Issue 03 (2015-07-30)

2612
Nastar
Net
wor
k
Description
PS
Core
NE version:
V900R013C00

l
Prerequisites
Procedure
Prerequisites
Procedure
Issue 03 (2015-07-30)

2613
Nastar
Issue 03 (2015-07-30)

2614
Nastar

No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(1)
Check
whether
analysis
data is
integrated

3.6
Checking
the
Integrity
of Analysis
Data
Procedure:
Analysis Data.
integrity.
4. Click Query.
the window.
analysis task.
performing (2).
NOTE
(2)
LTE
Periodic
MR Period
Setting
NOTE
subscription.

For details
about
parameters,
see LTE
Periodic
MR Period
Setting
Parameter
s
Procedure:
2. Click Configure.
Issue 03 (2015-07-30)

2615
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
Subscribe
to analysis
data (basic)

3.5
Subscribin
g to
Analysis
Data
Procedure:
click the *** tab.
configured.
Set.
NOTE
VIP Analysis.
reported.
5. Click Confirm.
Info area.
Issue 03 (2015-07-30)

2616
Nastar
No.
Procedur
e
Description
Subscribe
to analysis
data
(applicatio
n)

Reference
for
Detailed
Operatio
ns
Procedure:
click the *** tab.
configured.
VIP subscribers.
and NEs.
NOTE
subscribers.
5. Click Confirm.
Issue 03 (2015-07-30)

2617
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns

to.
Check
whether
analysis
data is
integrated

Procedure:
Analysis Data.
3.6
Checking
the
Integrity
of Analysis
Data

integrity.
4. Click Query.
the window.
analysis task.
technical support.
Issue 03 (2015-07-30)

2618
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(3)
Create an
analysis
task

l For
details,
see 3.7
Creatin
g an
Analysi
s Task.
Procedure:
to be analyzed.
NOTE

NOTE

10.Click Finish.
Issue 03 (2015-07-30)

l For
details
about
the
paramet
ers, see
Analysi
s Task
Param
eters.
l For
details
about
Sendin
g
Analysi
s
Report
s
Setting,
see
3.4.10
Setting
a
Mailbo
x and
Addres
s List
for
Sendin
g
Analysi
s
Report
s
(Optio
nal)
2619
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(4)
View
analysis
results VIP
summary
analysis

l For
details,
see 3.8
Queryi
ng
Analysi
s
Results
.
Procedure:
analysis results.
View
analysis
results VIP deep
analysis
Navigation path:
Procedure:
1. Click
NOTE
icon to enter
you need click
icon again.

NOTE
View
analysis
results VIP active
cells
analysis
l For
details
on the
descript
ion of
the
window
for
showin
g
analysis
results,
see
5.10.4
Refere
nce for
VIP
Analysi
s
Interfa
ce.

Procedure:
active.
Issue 03 (2015-07-30)

2620
Nastar
No.
Procedur
e
Description
View
analysis
results VIP active
servers
analysis
(only
support the
GSM
network)

View
analysis
results VIP trend
analysis

Reference
for
Detailed
Operatio
ns
Procedure:
are active.
Procedure:
Issue 03 (2015-07-30)

2621
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(5)
Export
analysis
reports

l For
details,
see 3.10
Exporti
ng
Analysi
s
Report
s.
Procedure:
3. Click Save.
l For
details
on the
descript
ion of
the
window
for
showin
g
analysis
results,
see
Interfa
ce
Descrip
tion:
VIP
Analysi
s/InDepth
Analysi
s/
Geogra
phic
Display
.
Issue 03 (2015-07-30)

2622
Nastar

Parameter
Description
Periodic MR
Period
Number of
Sampled Users

Nastar.
NOTE
Number of
Times MRs
Are Reported


Basic Subscription
Issue 03 (2015-07-30)

2623
Nastar
Netwo
rk
Parameter
Description
GSM
VIP
Analysis
Data (CHRCS)

You can click

NOTE
Issue 03 (2015-07-30)

2624
Nastar
Netwo
rk
Parameter
Description
VIP
Analysis
Data (CHRPS)

You can click
documentation.
documentation.
documentation.
Issue 03 (2015-07-30)

2625
Nastar
Netwo
rk
Parameter
Description
UMTS
VIP
Analysis
Data (CHR)

You can click

unavailable.
VIP
Analysis
Data (MR)
Issue 03 (2015-07-30)

You can click

2626
Nastar
Netwo
rk
Parameter
Description
LTE
FDD/
LTE
TDD
VIP
Analysis
Data (CHR)

You can click
measurement
MDT measurement
measurement
measurement
measurement
CSFB PREP, CSFB
Issue 03 (2015-07-30)

2627
Nastar
Netwo
rk
Parameter
Description
can be 1280(ms), 2560(ms), 5120(ms), 10240(ms), 20480
(ms), 30720(ms), 40960(ms), or 61440(ms).
600(s), 1200(s), 2400(s), 3600(s), 5400(s), or 7200(s). The
NOTE
Issue 03 (2015-07-30)

2628
Nastar
Netwo
rk
Parameter
Description
PS Core
VIP
Analysis
Data
(SGSN/
MMECHR)

You can click

settings.
settings.
Netwo
rk
Level
Parameter
Description
GSM
Group
Level
VIP Group
GSM CS NE
List
GSM PS NE
List
UTMS
Group
Level
Open VIP
Speciality
VIP Group
NE List
LTE
FDD/
LTE
TDD
Issue 03 (2015-07-30)
Group
Level
VIP Group
User Level
eNodeB
Interface
Select
NE List

2629
Nastar
Netwo
rk
PS
Core
Level
Group
Level
Parameter
Description
IMSI

Select
Trace
Reference No.

VIP Group

belongs.
HSS Name

to be delivered.
VIP Group
NE List

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

Issue 03 (2015-07-30)

2630
Nastar
Parameter
Analysis Type
Description
Analysis
Scene

CN side
side
Access
Network
Type
Data Type 1

NOTE
Data Type 2

and the PS domain:
Select NEs
RAN NE
VIP Group
Select

NOTE
VIP analysis task.
Issue 03 (2015-07-30)
Group Name
Members
Description
Updated
Date

updated.

2631
Nastar
Parameter
Result
Threshold
Description
Network
Domain

Service Type

so on.
or Flow Type
or Service/
Flow Type

on.
type of the KPIs.
Indicator
Name

Criterion

Threshold

KPI.
analysis results.
provided.
Process
Threshold
Issue 03 (2015-07-30)
Network

NOTE
Use the result
counter of
Short Calls
(Calling
Party) in VIP
analysis results
as an example
to describe the
differences
between the
result
threshold and
the process
threshold.
Result
threshold:
Engineers can
set the result
threshold of
the Short
Calls (Calling
Party) counter
and detect VIP
subscribers
that have more
short calls.
Process
threshold:
Engineers need
to set the
process
threshold for
defining a
short call based
on the
preceding
analysis result
counter. For
example, If the
Service
Duration
(Calling
Party) of one
call is shorter
than the Short
Call
Threshold
(Calling
Party), the call
is called a short
call (calling
party).
2632
Nastar
Parameter
Description
Domain

Service Type

so on.
or Flow Type
or Service/
Flow Type

on.
type of the KPIs.
Indicator
Name

KPI indicators.
Criterion

Threshold

KPI.
provided.
Issue 03 (2015-07-30)

2633
Nastar
Parameter
Description
Duration
Delay
immediately.
Execute on

Param
eter
Description
Note
Start
time

Period

Week.
Repeat
times


periodic task]
Period.
Issue 03 (2015-07-30)

2634
Nastar
Param
eter
Description
Note
Delay
by
(hours)

task.
NOTE

NOTE
started).
Whole
day

03:00:00.
executes the task.

under Busy hours.
parameter.
Busy
hours

day as busy time.
busy time.
time.
Issue 03 (2015-07-30)

2635
Nastar
Parameter
Description
Sendin
g
Analysi
s
Reports
Setting
Automatically
send analysis
reports via
emails
Target email

Email subject

Email
contents

indicators.
analysis result.
Attachment

Settings function.
directly.
mails.


NOTE
Issue 03 (2015-07-30)

2636
Nastar
Opening the Window

l
methods):
in the front
) directly.

l

Main Window
Issue 03 (2015-07-30)

2637
Nastar
No.
l

1. Click
default.
type is GSM PS.

Issue 03 (2015-07-30)

Analysis.

2638
Nastar
No.
Analysis
result tab
page

Cell.
Network.

Issue 03 (2015-07-30)

2639
Nastar
No.
Parameter
Description
(1)
Analysis
object
l User
4.
NOTE
(2)

selection area
NOTE
(3)

selection area
service type node.
NOTE
Issue 03 (2015-07-30)

2640
Nastar
No.
Parameter
Description
(4)
Counter
overview
information
table

click


NOTE
analysis.
(5)
Active cell
information
table
(6)
table
(7)
table
Issue 03 (2015-07-30)

2641
Nastar
No.
Parameter
Description
(8)
Active TAC
information
table

by the LTE network.

No.
Parameter
Description
(1)
Analysis
object
in area 4.
l Cell
Issue 03 (2015-07-30)

2642
Nastar
No.
Parameter
Description
(2)

selection area
NOTE
(3)

selection area
(4)
Counter
overview
information
table

(5)
Active VIP
subscriber
information
table

Issue 03 (2015-07-30)

2643
Nastar
No.
Parameter
Description
(1)
Analysis object
selection area

l Server
NOTE
IP:Server Name.
l Port
(2)
(3)
Service type
selection area
Counter set
selection area
NOTE
(4)
(5)
Active VIP
subscriber
information table

Click
Figure 5-46.
Issue 03 (2015-07-30)

2644
Nastar
No.
Feature
Description
(1)
Button area

(2)
Navigation
tree in the
Geographic
Observation
window
NOTE

cell KPI.
deleted.
Issue 03 (2015-07-30)

2645
Nastar
No.
Feature
Description
(3)
Geographic
observation
area
(4)
Grid detail
area
(5)
Legend area

click the
(6)
Information
area


NOTE
Opening the Window

l
Main Window
results.
Issue 03 (2015-07-30)

2646
Nastar
No.
1. Click
Issue 03 (2015-07-30)

2647
Nastar
No.
Area for
setting
filtering
criteria

NOTE

criteria.
1. Click

criteria.
9. Click OK.
NOTE
Issue 03 (2015-07-30)
Service
type
selection
area

2648
Nastar
No.
Counter
type
selection
area
Trend
analysis
chart

NOTE

the trend chart.
save data.
6
Trend
analysis
table
N.
NOTE
Issue 03 (2015-07-30)

2649
Nastar
No.
Area for
setting
trend
analysis
mode

5.10.5 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.
Common
Param
eter
Rang
e
Unit
Description
Supported Solution
Version
Deep
Analysi
s
N/A
N/A
When the dimension is Group,

from the analysis results of a
VIP group to the analysis
results of VIP subscribers in
this group.
l SRAN8.0/GBSS15.0/
RAN 15.0
When the dimension is User,

from the analysis results of
counters to the analysis results
of calls.
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

2650
Nastar
Param
eter
Rang
e
Unit
Description
Supported Solution
Version
Group
Name
N/A
N/A
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
User ID
N/A
N/A
ID of a VIP subscriber. Query

the ID of a VIP subscriber
using VIP group management.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Alias
N/A
N/A
Name of a VIP alias. Query the

alias of a VIP subscriber using
VIP group management.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

2651
Nastar
Param
eter
Rang
e
Unit
Description
Supported Solution
Version
IMSI
N/A
N/A
subscriber.
l SRAN8.0/GBSS15.0/
RAN 15.0

l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
IMEITAC
N/A
N/A
Type approval code (TAC) in

international mobile
equipment identity (IMEI) of
the UE used by a VIP
subscriber.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Termin
al
Model
N/A
N/A
Type of the UE used by a VIP

subscriber. Query the UE type
of a VIP subscriber using
terminal type management
VIP subscriber.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

2652
Nastar
Param
eter
Rang
e
Unit
Description
Supported Solution
Version
Service
Type
N/A
N/A
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Numbe
r of
Abnor
mal
KPIs
[0,
+)
Num
ber
Number of abnormal counters

in all counter sets determined
based on the result thresholds
set when engineers create a
task.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Total
Reports
[0,
+)
Num
ber

network access of a subscriber.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
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.
Issue 03 (2015-07-30)

2653
Nastar
RAN-NET/Accessibility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Access
Requests(IntraRAT)
[0,+)
Numbe
r

cell in the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access Failures
(Intra-RAT)
Issue 03 (2015-07-30)
[0,+)
Numbe
r

a cell in the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0

(intra-RAT) = Number of failed
access to a system of the current
RAT
l SRAN8.1/
GBSS15.1/
RAN 15.1

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 +
for HSPA - Number of times that
incoming intra-RAT handover
fails)
l SRAN10.0/
GBSS17.0/
RAN17.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2654
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Access
Requests(InterRAT)
[0,+)
Numbe
r

cell in another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access Failures
(Inter-RAT)
[0,+)
Numbe
r

a cell in another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0

(inter-RAT) = Number of failed
access to a system of another
RAT
l SRAN8.1/
GBSS15.1/
RAN 15.1
= Number of incoming interRAT handover failures that this

UE experiences on the entire
network + Number of times that
fails
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2655
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average TP on
Access
[0,3069
]
N/A
Average TP value when a VIP

network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal TPs
on Access
[0,+)
Numbe
r
Number of times that theTP

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0

you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2656
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Abnormal TPs
on Access
[0.00,10
0.00]
access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
values = Number of abnormal TP
values/Number of TP values x
100%
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RSCP
on Access
[-116,-2
5]
dBm
Average RSCP value when a

the network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2657
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
RSCPs on
Access
[0,+)
Numbe
r
Number of times that the RSCP

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0

you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Abnormal
RSCPs on
Access
[0.00,10
0.00]

access.
RSCP values/Number of RSCP
values x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2658
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Ec/No
on Access
[-31.5,0]
dB
Average Ec/No value when a

the network.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal Ec/
Nos on Access
[0,+)
Numbe
r
Number of times that the Ec/No

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0

you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2659
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Abnormal Ec/
Nos on Access
[0.00,10
0.00]

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Ec/No values/Number of Ec/No
values x 100%
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
[0,+)
Numbe
r

connection setup requests
l SRAN8.0/
GBSS15.0/
RAN 15.0
RRC is short for radio resource

control.
l SRAN8.1/
GBSS15.1/
RAN 15.1
The non-service RRC

connection setup process spans
from the time when the nonservice RRC connection setup
request is initiated to the time
when the non-service RRC
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2660
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Failures(NonService)
[0,+)
Numbe
r

network access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Success Rate
(Non-Service)
[0.00,10
0.00]
Success rate of non-service RRC

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2661
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Numbe
r

connection setup requests after
network access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Failures
(Service)
[0,+)
Numbe
r

network access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2662
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Rate
(Service)
[0.00,10
0.00]
Success rate of service RRC

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Failures
(Service-CS)
[0,+)
Numbe
r
Number of CS RRC connection

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2663
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Rate
(Service-CS)
[0.00,10
0.00]
Success rate of CS RRC

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Failures
(Service-PS)
[0,+)
Numbe
r
Number of PS RRC connection

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2664
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Rate
(Service-PS)
[0.00,10
0.00]
Success rate of PS RRC

access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2665
Nastar
RAN-NET/E2E Evaluation(CS Domain)

Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Requests
(MOC)
[0,+)
Numbe
r

use the CS service as the mobileoriginated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Setup
Failures(MOC)
[0,+)
Numbe
r

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2666
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Success Rate
(MOC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Setup
Requests(MTC)
[0,+)
Numbe
r

use the CS service as the mobileterminated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2667
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Failures(MTC)
[0,+)
Numbe
r

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Setup
Success Rate
(MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2668
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MOC)
[0,+)
Numbe
r

l SRAN8.0/
GBSS15.0/
RAN 15.0
The alerting process spans from

the RRC connection setup
request to the Alerting message.
l SRAN9.0/
GBSS16.0/
RAN16.0

setup is complete.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success Rate
(Alerting)
(MOC)
[0.00,10
0.00]
Rate of call connection

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2669
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MTC)
[0,+)
Numbe
r

(alerting) that a VIP subscriber
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success Rate
(Alerting)
(MTC)
[0.00,10
0.00]

acknowledgments (alerting)
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2670
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MOC)
[0,+)
Numbe
r

service as the mobile-originated
party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The connection
Ack) process spans from the
RRC connection setup request
to the Connect Ack message.
setup is complete.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success Rate
(Connect Ack)
(MOC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2671
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MTC)
[0,+)
Numbe
r

service as the mobile-terminated
party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success Rate
(Connect Ack)
(MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2672
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Success
Times(MOC)
[0,+)
Numbe
r

l SRAN8.0/
GBSS15.0/
RAN 15.0

message.
setup is complete.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Success
Rate(MOC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2673
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Success
Times(MTC)
[0,+)
Numbe
r

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Success
Rate(MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2674
Nastar
RAN-NET/E2E Evaluation(PS Domain)

Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Requests(PS)
[0,+)
Number

access the network and use the
PS service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Setup
Failures(PS)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2675
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Success Rate
(PS)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Success
Times(PS)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0

message.
l SRAN8.1/
GBSS15.1/
RAN 15.1

setup is complete.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2676
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Success
Rate(PS)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2677
Nastar
RAN-NET/PDP Evaluation-PS
Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Activation
Requests
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP Activation
Failures
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2678
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Activation
Success Rate
[0.00,10
0.00]
Success rate of PDP activation

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2679
Nastar
RAN-NET/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Release Times
(Intra-RAT)
[0,+)
Number

the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Releases(Intra-RAT) = Access
Requests(Intra-RAT) - Access
Failures(Intra-RAT)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal
Release Times
(Intra-RAT)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
Abnormal Release Times(IntraRAT) = Number of AMR RAB

abnormal releases
l SRAN8.1/
GBSS15.1/
RAN 15.1
+ Number of VP RAB abnormal

releases
l SRAN9.0/
GBSS16.0/
RAN16.0
+ 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 interRAT incoming handover occurs.
Issue 03 (2015-07-30)

l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2680
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Release Times
(Inter-RAT)
[0,+)
Number

another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Releases(Inter-RAT) = Access
Requests(Inter-RAT) - Access
Failures(Inter-RAT)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal
Release Times
(Inter-RAT)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
Abnormal Release Times(InterRAT) = Number of times that the

first RAB after an incoming
inter-RAT handover is
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2681
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Release
Times
[0,+)
Number

subscriber releases all RRC
connections during the process
of using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RRC
Release Times
[0,+)
Number

all RRC connections during the
process of using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2682
Nastar
RAN-NET/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Times
(Non-Service)
[0,+)
Number
Number of successful nonservice RRC connection setups

l SRAN8.0/
GBSS15.0/
RAN 15.0

connection setups (non-service)
setup requests (non-service) Number of RRC connection
setup failures (non-service) =
Number of valid RRC
connection setup delays (nonservice)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RRC
Setup Delay
(Non-Service)
N/A
Second
Average delay for non-service

RRC connection setup upon
l SRAN8.0/
GBSS15.0/
RAN 15.0

CONN REQ message is
generated.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2683
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RRC
Setup Delay
Times(NonService)
[0,+)
Number

non-service RRC connection
setup upon successful call
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RRC
Setup Delay
(Non-Service)
[0.00,1
00.00]
Proportion of delays for nonservice RRC connection setup in

all overlong delays upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2684
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Success Times
(Service)
[0,+)
Number
Number of successful service

RRC connection setups upon
l SRAN8.0/
GBSS15.0/
RAN 15.0

connection setups = Number of
requests - Number of service
RRC connection setup failures =
Number of valid delays for
service RRC connection setup.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RRC
Setup Delay
(Service)
[0,+)
Second
Average delay for service RRC

connection setup upon
l SRAN8.0/
GBSS15.0/
RAN 15.0

CONN REQ message is
generated.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2685
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RRC
Setup Delay
Times(Service)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RRC
Setup Delay
(Service)
[0.00,1
00.00]
Proportion of overlong delays

for service RRC connection
setup in all overlong delays upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2686
Nastar
RAN-NET/Mobility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Soft Handover
Requests
[0,+)
Number
Number of soft handover

using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Soft Handover
Failures
[0,+)
Number
Number of soft handover failures

that a VIP subscriber experiences
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2687
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Soft Handover
Success Rate
[0.00,1
00.00]
Success rate of soft handovers

(including softer handovers) that
a VIP subscriber initiates during
the process of using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Hard Handover
Requests
[0,+)
Number

using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2688
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Hard Handover
Failures
[0,+)
Number

experiences during the process of
using a service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Hard Handover
Success Rate
[0.00,1
00.00]
Success rate of hard handovers

that a VIP subscriber initiates
service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2689
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Soft
Handover Delay
[0,+)
Second
Average soft handover delay

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Hard
Handover Delay
[0,+)
Second
Average hard handover delay

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2690
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number

to another network) initiated by a
UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Outgoing
Handover
Requests
(UMTS to
GSM)
[0,+)
Number

to a GSM network) initiated by a
VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2691
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Requests
(UMTS to LTE)
[0,+)
Number

to an LTE network) initiated by a
VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Number

to another network) experienced
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2692
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Failures(UMTS
to GSM)
[0,+)
Number

to a GSM network) experienced
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Outgoing
Handover
Failures(UMTS
to LTE)
[0,+)
Number

failures (from one UMTS
network to another LTE
network) experienced by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2693
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Requests
[0,+)
Number

requests (from another network
a VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Incoming
Handover
Requests(GSM
to UMTS)
[0,+)
Number

requests (from a GSM network to
a UMTS network) initiated by a
VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2694
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Requests(LTE
to UMTS)
[0,+)
Number

requests (from an LTE network
a VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Incoming
Handover
Failures
[0,+)
Number

failures (from another network to
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2695
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Failures(GSM
to UMTS)
[0,+)
Number

failures (from a GSM network to
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inter-RAT
Incoming
Handover
Failures(LTE to
UMTS)
[0,+)
Number

failures (from an LTE network to
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2696
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version

Handover Delay
[0,+)
Second
Average delay for outgoing interRAT handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0

delay = Time when the IU
RELEASE COMMAND
message is generated - Time
when the RELOCATION
REQUIRED message is
generated.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Handover Delay
(UMTS to
GSM)
[0,+)
Second
Average delay for UMTS-toGSM handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2697
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version

Handover Delay
(UMTS to LTE)
[0,+)
Second
Average delay for UMTS-toLTE handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Handover Delay
[0,+)
Second
Average delay for incoming

inter-RAT handover recorded by
the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0

delay = Time when the UTRAN
MOBILITY INFORMATION
CONFIRM message is generated
- Time when the RELOCATION
REQUIRED message is
generated.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2698
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version

Handover Delay
(GSM to
UMTS)
[0,+)
Second
Average delay for GSM-toUMTS handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Handover Delay
(LTE to UMTS)
[0,+)
Second
Average delay for LTE-toUMTS handover recorded by the

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2699
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT Cell
Reselection
Times
[0,+)
Number
Number of cell reselections

recorded by the current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

2700
Nastar
RAN-CS/AMR/Accessibility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0

bearer.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number

experienced by a VIP
subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2701
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

an RAB setup request.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,10
0.00]
RAB setup success rate after

network access.
RAB setup success rate (%) =
setups/Number of RAB setup
requests x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2702
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
[0,+)
Number

subscriber hears the alerting
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)
[0,+)
Number

subscriber hears the peer ends'
voice upon successful call
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2703
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
Release Times
Before
Connection
Acknowledge
[0,+)
Number
Number of times that a call is

abnormally released between
the time when a subscriber
hears the alerting and the time
when the subscriber hears the
voice of the peer-end subscriber
during a successful call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2704
Nastar
RAN-CS/AMR/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number
See RAB Setup Success Times

in RAN-CS/VP/Accessibility
Evaluation
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Number

is abnormally released after a
the network and successfully
initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2705
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,10
0.00]
Abnormal RAB release rate

after a VIP subscriber gains
access to the network and
successfully initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Abnormal RAB release rate (%)

= Number of abnormal RAB
releases/Number of successful
call setups x 100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2706
Nastar
RAN-CS/AMR/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

setups during call initiation, that
is, number of RAB setup delays.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2707
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Setup Delay
[0,+)
Second
Average RAB setup delay

subscriber to initiate a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Average RAB setup delay (s) =

Sum of RAB setup delays/
Number of RAB setup delays.
l SRAN8.1/
GBSS15.1/
RAN 15.1
RAB setup delay = RAB setup

request connection
acknowledge time - RAB setup
request time.
l SRAN9.0/
GBSS16.0/
RAN16.0

request connection
acknowledge time: When the
RAB assignment procedure is
successful, namely, when the
SRNC sends a Radio Access
message to the CN after it
receives an RAB setup
connection acknowledge
message.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

from the CN.
Issue 03 (2015-07-30)

2708
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,+)
Number
Number of times that the RAB l SRAN8.0/

setup delay is overlong during
GBSS15.0/
the process for a VIP subscriber
RAN 15.0
to initiate a call.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,10
0.00]

in all overlong delays.
(%) = Number of overlong RAB
setup delays x 100% = Number
of overlong RAB setup delays/
setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2709
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,+)
Second

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2710
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,10
0.00]

setup delays of the mobileoriginated party upon successful
call initiation.
setup delays (mobileoriginated) (%) = Number of
call setup delays (mobileoriginated) x 100% = Number of
setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2711
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,+)
Number

overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,+)
Second

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2712
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,+)
Number

overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,10
0.00]

setup delays of the mobileterminated party upon
setup delays (mobileterminated) (%) = Number of
call setup delays (mobileterminated) x 100% = Number
of overlong call setup delays
setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2713
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MOC)
[0,+)
Number

mobile-originated party hears
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MOC)
[0,+)
Second
Average alerting delay of the

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2714
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Alerting)
(MOC)
[0,+)
Number

alerting delay of the mobileoriginated party upon successful
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MOC)
[0.00,10
0.00]
Proportion of overlong alerting

delays experienced by the
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2715
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MOC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MOC)
[0,+)
Second

Ack) delay of the mobileoriginated party upon successful
call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2716
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Connect Ack)
(MOC)
[0,+)
Number

overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MOC)
[0.00,10
0.00]

(Connect Ack) delays
experienced by the mobileoriginated party upon successful
call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2717
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MTC)
[0,+)
Number

mobile-terminated party hears
initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MTC)
[0,+)
Second

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2718
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Alerting)
(MTC)
[0,+)
Number

(alerting) delay of the mobileterminated party upon
overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MTC)
[0.00,10
0.00]

(alerting) delays experienced by
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2719
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MTC)
[0,+)
Number

(Connect Ack) experienced by
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MTC)
[0,+)
Second

Ack) delay of the mobileterminated party upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2720
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Connect Ack)
(MTC)
[0,+)
Number

overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MTC)
[0.00,10
0.00]
Proportion of call connection

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2721
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,+)
Second

l SRAN8.0/
GBSS15.0/
RAN 15.0
Average RAB duration (s) =

Total RAB duration/Number of
RAB durations
- 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
Service
Duration Times
[0,+)
Number

duration is below the threshold
for short RAB duration upon
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2722
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Service
Duration(MOC)
[0,+)
Second

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Short Calls
(MOC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
originated party.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2723
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Short Calls
(MOC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0

GBSS15.1/
originated party.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Service
Duration(MTC)
[0,+)
Second

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2724
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Short Calls
(MTC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
terminated.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Short Calls
(MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0

GBSS15.1/
terminated.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2725
Nastar
RAN-CS/AMR/Quality Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Success Times
[0,+)
Number

a call setup request.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Times
[0,+)
Number
Number of calls with downlink

problems are detected by the
RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2726
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
[0.00,10
0.00]
Proportion of Downlink OneWay Audio = Downlink OneWay Audio Times/RAB Setup

Successes x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink OneWay Audio

Times
[0,+)
Number
Number of calls with uplink

Uplink one-way audio problems
are detected by the RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2727
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Uplink OneWay Audio
[0.00,10
0.00]
Proportion of Uplink One-Way

Audio = Uplink One-Way
Audio Times/RAB Setup
Successes x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Noise Times
[0,+)
Number
Number of calls with static

problems.
Static problems are detected by
the RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2728
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Noise
Proportion
[0.00,10
0.00]

problems.
l SRAN8.0/
GBSS15.0/
RAN 15.0

problems (%) = Number of calls
with static problems/Number of
100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2729
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SQI Reports
[0,+)
Number
Number of signal quality

indicator (SQI) reports
generated during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
2. The RNC collects statistics on

the average SQI value and
divides signal quality into
different levels according to SQI
values:
l SRAN10.1/
GBSS17.1/
RAN17.1

(400,500]), Good (SQI<=
(300,400]), Accept (SQI<=
(200,300]), Poor (SQI<=
(100,200]), Bad (SQI<=
[0,100]).
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
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 03 (2015-07-30)

2730
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average SQI
[0,+)
N/A
Average SQI value in the SQI

reports generated during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal SQIs
[0,+)
Number
Number of abnormal SQI values

in the SQI reports.
A SQI value is abnormal if the
SQI value of a call is below the
SQI exception threshold.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2731
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Abnormal SQIs
[0.00,10
0.00]

abnormal SQI values.
l SRAN8.0/
GBSS15.0/
RAN 15.0

abnormal SQI values (%) =
Number of calls with abnormal
SQI values/Number of
100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Voice Quality
with SQI as
Excellent
[0.00,10
0.00]

Excellent during successful
voice service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2732
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Voice Quality
with SQI as
Good
[0.00,10
0.00]

Good during successful voice
service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Voice Quality
with SQI as
Accept
[0.00,10
0.00]

Accept during successful voice
service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2733
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Voice Quality
with SQI as
Poor
[0.00,10
0.00]

Poor during successful voice
service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Voice Quality
with SQI as Bad
[0.00,10
0.00]

Bad during successful voice
service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2734
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Level 1 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
BLER is short for block error

rate.
l SRAN8.1/
GBSS15.1/
RAN 15.1

Standard for level 1: 0-0.78%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 2 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1

0.78%-1.56%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2735
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Level 3 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1

1.56%-3.12%
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 4 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1

3.12%-6.24%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2736
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Level 5 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1

6.24%-12.48%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 6 Uplink
BLER
[0.00,10
0.00]

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
Standard for level 6: above

12.48%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2737
Nastar
RAN-CS/VP/Accessibility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2738
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2739
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2740
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
Release Times
Before
Connection
Acknowledgme
nt
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2741
Nastar
RAN-CS/VP/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2742
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2743
Nastar
RAN-CS/VP/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2744
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2745
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2746
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2747
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2748
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2749
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MOC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2750
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Alerting)
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MOC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2751
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MOC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2752
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Connect Ack)
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MOC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2753
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Alerting)
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MTC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2754
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Alerting)
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Alerting)
(MTC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2755
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Connection
Acknowledgme
nt Success
Times(Connect
Ack)(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MTC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2756
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Connection
Acknowledgme
nt Delay Times
(Connect Ack)
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Connection
Acknowledgme
nt Delay
(Connect Ack)
(MTC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2757
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overshort RAB
Service
Duration Times
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2758
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Service
Duration(MOC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Number of
Short Calls
(MOC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2759
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Proportion of
Short Calls
(MOC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Service
Duration(MTC)
[0,+)
Second

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2760
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Number of
Short Calls
(MTC)
[0,+)
Number

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Short Calls
(MTC)
[0.00,10
0.00]

"RAN-CS/AMR".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2761
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Setup Requests
(MOC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Setup Failures
(MOC)
[0,+)
Number

setups initiated by the mobileoriginated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2762
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Setup Success
Rate (MOC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Setup Requests
(MTC)
[0,+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2763
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Setup Failures
(MTC)
[0,+)
Number

setups initiated by the mobileterminated party.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Setup Success
Rate (MTC)
[0.00,10
0.00]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

2764
Nastar
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
Solution
Version
RAB Setup
Requests
[0,+)
Numb
er

initiated by a VIP subscriber after
network access.
l SRAN8.0/
GBSS15.0/
RAN 15.0

bearer.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2765
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,1
00.00]
RAB setup success rate

l SRAN8.0/
GBSS15.0/
RAN 15.0
RAB setup success rate = Number l SRAN8.1/

of successful RAB setups/Number
GBSS15.1/
of RAB setup requests x 100%.
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2766
Nastar
RAN-PS/PS R99/Retainability Evaluation

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Numb
er
See RAB Setup Success Times in

RAN-PS/PS R99/Accessibility
Evaluation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Numb
er

subscriber abnormally releases an
RAB after network access and
successful service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2767
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,1
00.00]

releases experienced by a VIP
subscriber after network access
and successful service initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

releases = Number of abnormal
RAB releases/Number of
successful call setups x 100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2768
Nastar
RAN-PS/PS R99/Delay Evaluation

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numb
er

during call initiation, that is,
number of RAB setup delays.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,
+)
Secon
d
Average RAB setup delay during

call initiation.
Average RAB setup delay = Sum
of RAB setup delays/Number of
RAB setup delays.
RAB setup delay = RAB request
connection acknowledge time RAB setup request time.
from the CN.
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2769
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,
+)
Numb
er

overlong
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,1
00.00]
Proportion of times that the RAB

overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Proportion of overlong RAB setup

delays = Number of overlong RAB
setup delays x 100% = Number of
overlong RAB setup delays/
x 100%.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2770
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,
+)
Secon
d
Average call delay of the mobileoriginated party upon successful

call initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2771
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times(MOC)
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,1
00.00]

delays of the mobile-originated
initiation.
delays (mobile-originated) =
Number of call setup delays
(mobile-originated) x 100% =
connection setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2772
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,
+)
Numb
er

upon successful call initiation is
abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,
+)
Secon
d

mobile-terminated upon
l SRAN8.0/
GBSS15.0/
RAN 15.0
Average call setup delay =Sum of

call setup delays/Number of call
setup delays.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Call setup delay = RAB request

connection acknowledge time Signaling access time.
l SRAN9.0/
GBSS16.0/
RAN16.0

l SRAN10.0/
GBSS17.0/
RAN17.0
Statistical point for signaling

access time: When an RRC
SETUP REQ or RELOC REQ
message is received or when an
request is initiated.
Issue 03 (2015-07-30)

l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2773
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,1
00.00]

delays experienced by the mobileterminated party upon successful
call initiation.
setup delays/Number of call setup
delays x 100% = Number of
overlong call setup delays/Number
of successful RRC connection
setups x 100%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2774
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
Average RAB duration = RAB

duration/Number of RAB
durations.
- 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.
procedure is successful, after
receiving an RAB setup
connection acknowledge message,
the SRNC sends a Radio Access
message to the CN.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2775
Nastar
RAN-PS/PS R99/Rate Evaluation

Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Final Average
Negotiated
Downlink RAB
Rate
[0.00,
+)
kbit/s
Final negotiated rate of downlink

l SRAN8.0/
GBSS15.0/
RAN 15.0

downlink RAB = Final negotiated
rate of downlink RAB/Number of
negotiated rate of downlink RAB.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Final Average
Negotiated
Uplink RAB
Rate
[0.00,
+)
kbit/s
Final negotiated rate of uplink

l SRAN8.0/
GBSS15.0/
RAN 15.0

uplink RAB = Final negotiated
rate of uplink RAB/Number of
negotiated rate of uplink RAB.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2776
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
[0,
+)
MB
Downlink traffic volume of all

common PS services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Transmission
Duration
[0,
+)
Second
Average downlink transmission

services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2777
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Downlink
Throughput
[0.00,
+)
kbit/s
Average downlink throughput for

l SRAN8.0/
GBSS15.0/
RAN 15.0

Downlink traffic volume/
Downlink data transmission
duration.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Downlink
Throughput
Times
[0,
+)
Numbe
r

downlink throughput for one RAB
average downlink throughput.
you create a task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2778
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Uplink Traffic
Volume
[0,
+)
MB
Uplink traffic volume for all

common PS services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Transmission
Duration
[0,
+)
Second
Average uplink transmission

services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2779
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Average Uplink
Throughput
[0.00,
+)
kbit/s
Average uplink throughput rate for

l SRAN8.0/
GBSS15.0/
RAN 15.0

uplink traffic volume/Total uplink
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Uplink
Throughput
Times
[0,
+)
Numbe
r

uplink throughput for one RAB
you create a task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2780
Nastar
RAN-PS/PS R99/Quality Evaluation

Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Proportion of
Level 1 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Standard for level 1: 0 =< X

=< 0.39%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 2 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1

=< 0.78%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2781
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Proportion of
Level 3 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1

=< 3.12%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 4 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1

=< 6.24%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2782
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Proportion of
Level 5 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1

=< 12.48%.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Level 6 Uplink
BLER
[0.00,
100.00
]

initiation.
l SRAN8.0/
GBSS15.0/
RAN 15.0

to the PS service.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Standard for level 6: 12.48% <

X.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2783
Nastar
RAN-PS/HSDPA/Accessibility Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2784
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2785
Nastar
RAN-PS/HSDPA/Retainability Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2786
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,
100.00
]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2787
Nastar
RAN-PS/HSDPA/Delay Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2788
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,
100.00
]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2789
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2790
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,
100.00
]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2791
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2792
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,
100.00
]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2793
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2794
Nastar
RAN-PS/Rate Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
[0,
+)
MB

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Transmission
Duration
[0,
+)
Second

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2795
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Downlink
Throughput
[0.00,
+)
kbit/s

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Downlink
Throughput
Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2796
Nastar
RAN-PS/HSUPA/Accessibility Evaluation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2797
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,
+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2798
Nastar
RAN-PS/HSUPA/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Numbe
r

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2799
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2800
Nastar
RAN-PS/HSUPA/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,+)
Secon
d

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2801
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2802
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,+)
Secon
d

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2803
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2804
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,+)
Secon
d

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2805
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,+)
Numb
er

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
[0.00,1
00.00]

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2806
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,+)
Secon
d

"RAN-PS/PS R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2807
Nastar
RAN-PS/HSUPA/Rate Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink Traffic
Volume
[0,+)
MB
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Transmission
Duration
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2808
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Throughput
[0.00,+)
kbit/s
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Uplink
Throughput
Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2809
Nastar
RAN-PS/HSPA/Accessibility Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2810
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Success Rate
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2811
Nastar
RAN-PS/HSPA/Retainability Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RAB
Release Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2812
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal RAB
Release Rate
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2813
Nastar
RAN-PS/HSPA/Delay Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Success Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average RAB
Setup Delay
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2814
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong RAB
Setup Delay
Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong RAB
Setup Delay
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2815
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MOC)
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MOC)
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2816
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MOC)
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MOC)
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2817
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Call Setup
Delay Times
(MTC)
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Call
Setup Delay
(MTC)
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2818
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Call
Setup Delay
Times(MTC)
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Proportion of
Overlong Call
Setup Delay
(MTC)
[0.00,100.00]
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2819
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RAB
Service
Duration
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2820
Nastar
RAN-PS/HSPA/Rate Evaluation
Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
[0,+)
MB
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Downlink
Transmission
Duration
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2821
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Throughput
[0.00,+)
kbit/s
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Downlink
Throughput
Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2822
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink Traffic
Volume
[0,+)
MB
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average Uplink
Transmission
Duration
[0,+)
Second
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2823
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Throughput
[0.00,+)
kbit/s
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Low Average
Uplink
Throughput
Times
[0,+)
Number
Same as the
related counter
in "RAN-PS/PS
R99".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

2824
Nastar
RAN INTEGRATED/MULTI-RAB/Accessibility Evaluation
Issue 03 (2015-07-30)
Par
am
eter
Ra
ng
e
U Description
n
i
t
Mul
tiRA
B
Setu
p
Req
uest
s
[0,
+
)
N Number of RAB setup requests

m during a call.
b
e
r
Mul
tiRA
B
Setu
p
Fail
ures
[0,
+
)
Mul
tiRA
B
Setu
p
Suc
cess
Rate
[0.
00,
10
0.0
0]
N Number of RAB setup failures

m during a call.
b
e
r
% Setup success rate for accessing

multiple RABs during a call.

2825
Nastar
RAN INTEGRATED/MULTI-RAB/Retainability Evaluation-With CS
Issue 03 (2015-07-30)
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Mul
tiRA
B
Rele
ase
Tim
es
[
0
,
+
N
u
m
b
e
r
Abn
orm
al
Mul
tiRA
B
Rele
ase
Tim
es
[
0
,
+
Abn
orm
al
Mul
tiRA
B
Rele
ase
Rate
[
0
.
0
0
,
1
0
0
.
0
0
]
Number of RAB releases where

multiple CS RABs that contain at
least one CS RAB are released during
a call.
N
u
m
b
e
r

where multiple CS RABs that contain
at least one CS RAB are released at a
time during a call.

at least one CS RAB at a time during
a call.

2826
Nastar
RAN INTEGRATED/MULTI-RAB/Retainability Evaluation-Only PS

Par
am
eter
R
a
n
g
e
U Description
n
i
t
Mul
tiRA
B
Rele
ase
Tim
es
[
0
,
+
N Number of RAB releases where

u multiple RABs that contain only PS
m RABs are released during a call.
b
e
r
Abn
orm
al
Mul
tiRA
B
Rele
ase
Tim
es
[
0
,
+
Abn
orm
al
Mul
tiRA
B
Rele
ase
Rate
[
0
.
0
0
,
1
0
0
.
0
0
]
N
u
m
b
e
r

where multiple RABs that contain
only PS RABs are released during a
call.

only PS RABs during a call.
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.
Issue 03 (2015-07-30)

2827
Nastar
Active Cell/Common
Paramete
r
Range
Unit
Description
Supported Solution
Version
RNC ID
[0,4095]
N/A
ID of the RNC to which

an active cell belongs.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RNC
Name
N/A
N/A
Name of the RNC to

which an active cell
belongs.
l SRAN8.0/
GBSS15.0/RAN
15.0
Note: when name

obtained because
configuration
deleted or cell
information has not
been activated,
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2828
Nastar
Paramete
r
Range
Unit
Description
Supported Solution
Version
Cell ID
[0,65535]
N/A
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell Name
1 to 64
characters
N/A

Note: when name
obtained because
configuration
deleted or cell
information has not
been activated,
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2829
Nastar
Paramete
r
Range
Unit
Description
Supported Solution
Version
Service
Type
N/A
N/A
Service type for a

counter.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Active Cell/RAN NET/NET/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
[0,+)
Number

service setup
GBSS15.0/
requests that a VIP
RAN 15.0
group or VIP
l SRAN8.1/
GBSS15.1/
in an active cell.
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2830
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal TPs
on Access
[0,+)
Number
Number of times
that the TP value is
abnormal when a
VIP group or VIP
subscriber gains
access to the
network in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Set the exception

threshold when
you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal Ec/
Nos on Access
[0,+)
Number
Number of times
that the Ec/No
value is abnormal
when a VIP group
or VIP subscriber
gains access to the
network in an
active cell.
Set the exception
threshold when
you create a task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2831
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
RSCPs on
Access
[0,+)
Number
Number of times
that the RSCP
value is abnormal
when a VIP group
or VIP subscriber
gains access to the
network in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Set the exception

threshold when
you create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
[0,+)
Number

service setup
GBSS15.0/
requests that a VIP
RAN 15.0
group or VIP
l SRAN8.1/
GBSS15.1/
in an active cell.
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2832
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Number
Number of service l SRAN8.0/

setup requests that
GBSS15.0/
a VIP group or VIP
RAN 15.0
subscriber initiates l SRAN8.1/
in an active cell.
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC Setup
Failures
(Service)
[0,+)
Number
Number of service
setup failures that
a VIP group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2833
Nastar
Active Cell/RAN NET/NET/Retainability

Parameter
Range
Unit
Description
Supported Solution
Version
RRC Release
Times
[0,+)
Number
Number of times
that the RRC
connection setup
for a VIP group or
VIP subscriber is
released in an
active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnormal RRC
Release Times
[0,+)
Number
Number of times
that the RRC
connection setup
for a VIP group or
VIP subscriber is
abnormally
released in an
active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2834
Nastar
Active Cell/RAN CS/AMR/Accessibility

Parameter
Range
Unit
Description
Supported
Solution Version
RAB Setup
Requests
[0,+)
Numbe
r
Number of CS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Numbe
r
Number of CS
service setup failures
that a VIP group or
VIP subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2835
Nastar
Active Cell/RAN CS/AMR/Retainability

Parameter
Range
Unit
Description
Supported
Solution Version
Best Cell Times

Before RAB
Release
[0,+)
Numb
er

the CS service of a
VIP group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Numb
er

the CS service of a
VIP group or VIP
subscriber is
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2836
Nastar
Active Cell/RAN CS/VP/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Number of CS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of CS
service setup
failures that a VIP
group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2837
Nastar
Active Cell/RAN CS/VP/Retainability

Parameter
Range
Unit
Description
Supported
Solution
Version
Best Cell Times

Before RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the CS
service of a VIP
group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the CS
service of a VIP
group or VIP
subscriber is
abnormally
released.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2838
Nastar
Active Cell/RAN CS/SMS/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
SMS Requests
(MOC)
[0,+)
Number
Number of SMS
requests that a VIP
group or VIP
subscriber sends in
an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
SMS Request
Failures(MOC)
[0,+)
Number
Number of SMS
requests that a VIP
group or VIP
subscriber fails to
send in an active
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2839
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SMS Requests
(MTC)
[0,+)
Number
Number of SMS
requests that a VIP
group or VIP
subscriber receives
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
SMS Request
Failures(MTC)
[0,+)
Number
Number of SMS
requests that a VIP
group or VIP
subscriber fails to
receive in an active
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2840
Nastar
Active Cell/RAN PS/R99/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Number of PS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of PS
service setup
failures that a VIP
group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2841
Nastar
Active Cell/RAN PS/R99/Retainability

Parameter
Range
Unit
Description
Supported
Solution Version
Best Cell Times

Before RAB
Release
[0,+)
Numbe
r

as the best cell
of a VIP group or
VIP subscriber is
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before RAB
Abnormal RAB
Release
[0,+)
Numbe
r

as the best cell
of a VIP group or
VIP subscriber is
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2842
Nastar
Active Cell/RAN PS/HSDPA/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Number of PS
service setup
requests that a
VIP group or VIP
subscriber
initiates in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of PS
l SRAN8.0/
service setup
GBSS15.0/
failures that a VIP
RAN 15.0
group or VIP
l SRAN8.1/
subscriber
GBSS15.1/
experiences in an
RAN 15.1
active cell.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2843
Nastar
Active Cell/RAN PS/HSDPA/Retainability

Parameter
Range
Unit
Description
Supported
Solution Version
Best Cell Times

Before RAB
Release
[0,+)
Numbe
r

the PS service of a
VIP group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Numbe
r

the PS service of a
VIP group or VIP
subscriber is
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2844
Nastar
Active Cell/RAN PS/HSUPA/Accessibility

Parameter
Range
Unit
Description
Supported
Solution
Version
RAB Setup
Requests
[0,+)
Number
Number of PS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of PS
service setup
failures that a VIP
group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2845
Nastar
Active Cell/RAN PS/HSUPA/Retainability

Parameter
Range
Unit
Description
Supported
Solution
Version
Best Cell Times

Before RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the PS
service of a VIP
group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the PS
service of a VIP
group or VIP
subscriber is
abnormally
released.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2846
Nastar
Active Cell/RAN PS/HSPA/Accessibility

Parameter
Range
Unit
Description
Supported
Solution Version
RAB Setup
Requests
[0,+)
Number
Number of PS
service setup
requests that a VIP
group or VIP
in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB Setup
Failures
[0,+)
Number
Number of PS
service setup
failures that a VIP
group or VIP
subscriber
experiences in an
active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2847
Nastar
Active Cell/RAN PS/HSPA/Retainability

Parameter
Range
Unit
Description
Supported
Solution Version
Best Cell Times

Before RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the PS
service of a VIP
group or VIP
subscriber is
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best Cell Times

Before
Abnormal RAB
Release
[0,+)
Number
Number of times
that an active cell
serves as the best
cell before the PS
service of a VIP
group or VIP
subscriber is
abnormally
released.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Issue 03 (2015-07-30)

2848
Nastar

Common
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Deep
Analysis
N/A
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0

l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2849
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Group
Name
N/A
N/A
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2850
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
User ID
N/A
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2851
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Alias
N/A
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2852
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
l SRAN8.
0/
GBSS15
.0/RAN
15.0

l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2853
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
IMEITAC
0000
0000
9999
9999
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2854
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Terminal
Model
N/A
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2855
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Service
Type
N/A
N/A
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2856
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Number
of
Abnormal
KPIs
[0,
+)
Numb
er

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

2857
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Total
Reports
[0,
+)
Numb
er

subscriber.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0

Issue 03 (2015-07-30)

2858
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Acces
s
Reque
sts
(IntraRAT)
[0,
+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acces
s
Failur
es
(IntraRAT)
[0,
+)
Number

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2859
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Acces
s
Reque
sts
(InterRAT)
[0,
+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acces
s
Failur
es
(InterRAT)
[0,
+)
Number

another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2860
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Avera
ge TA
on
Acces
s
[0,63
]
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnor
mal
TAs
on
Acces
s
[0,
+)
Number

network.
create a task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2861
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Ratio
of
Abnor
mal
TAs
on
Acces
s
[0.00,
100.0
0]

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Avera
ge
RAC
H
Level
on
Acces
s
[-110
,-47]
dBm

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2862
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Abnor
mal
RAC
H
Levels
on
Acces
s
[0,
+)
Number

network.
l SRAN8.0/
GBSS15.0/
RAN 15.0

create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio
of
Abnor
mal
RAC
H
Levels
on
Acces
s
[0.00,
100.0
0]

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2863
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Relea
ses
(Intra
RAT)
[0,
+)
Numb
er

l SRAN8.0
/
GBSS15.
0/RAN
15.0

l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2864
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Abno
rmal
Relea
ses
(Intra
RAT)
[0,
+)
Numb
er

l SRAN8.0
/
GBSS15.
0/RAN
15.0
l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2865
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Relea
ses
(Inter
RAT)
[0,
+)
Numb
er

l SRAN8.0
/
GBSS15.
0/RAN
15.0

l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2866
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Abno
rmal
Relea
ses
(Inter
RAT)
[0,
+)
Numb
er

l SRAN8.0
/
GBSS15.
0/RAN
15.0

l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

2867
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
Hard
Handover
Requests
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Hard
Handover
Failures
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2868
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
Hard
Handover
Success
Times
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
Outgoing
Handover
Requests
[0,+)
Num
ber

the command.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2869
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
InterRAT
Outgoing
Handover
Failures
(Normal
Release)
[0,+)
Num
ber

the GSM network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
Outgoing
Handover
Failures
(Abnorm
al
Release)
[0,+)
Num
ber

a service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2870
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
InterRAT
Incoming
Handover
Requests
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
Incoming
Handover
Failures
[0,+)
Num
ber

during a service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2871
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Total
Call
Setup
Reques
ts
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Failure
s
[0,
+)
Numb
er

call.
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2872
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Abnor
mal
Release
Before
Call
Compl
etion
[0,
+)
Numb
er

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Succes
s Times
[0,
+)
Numb
er

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2873
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Call
Compl
etion
(Alerti
ng)
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Compl
etion
(Conne
ct Ack)
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2874
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Call
Compl
etion
Succes
s Rate
(Alerti
ng)
[0.00
,
100.
00]

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Compl
etion
Succes
s Rate
(Conne
ct Ack)
[0.00
,
100.
00]

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2875
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution Version
Call
Setup
Success
Times
[0,
+)
Num
ber

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Alerting message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Complet
ion
(Connec
t Ack)
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2876
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution Version
Abnorm
al Call
Releases
[0,
+)
Num
ber

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

release:
abnormal one.
subscriber.
fails.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Abnorm
al Call
Rate
[0.00,
100.00
]

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Ack) x 100%
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2877
Nastar

Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Access
Delays
(MOC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Access
Delay
(MOC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2878
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Access
Delays
(MOC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Access
Delays
(MOC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2879
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Access
Delays
(MTC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Access
Delay
(MTC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2880
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Access
Delays
(MTC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Access
Delays
(MTC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2881
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Times of
Call
Complet
ion
Delay
(Alertin
g)
(MOC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Call
Complet
ion
Delay
(Alertin
g)
(MOC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2882
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MOC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MOC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2883
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Average
Call
Complet
ion
Delay
(Connec
t Ack)
(MOC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MOC)
[0,
+)
Numbe
r

create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2884
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Ratio of
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MOC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Times of
Call
Complet
ion
Delay
(Alertin
g)
(MTC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2885
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Average
Call
Complet
ion
Delay
(Alertin
g)
(MTC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MTC)
[0,
+)
Numbe
r

create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2886
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Ratio of
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MTC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Call
Complet
ion
Delay
(Connec
t Ack)
(MTC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2887
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MTC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MTC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2888
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Average
Call
Duration
(MOC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

call duration.
incomplete.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Short
Calls
(MOC)
[0,
+)
Numbe
r
Number of short calls for the mobileoriginated party during a successful

call.
l SRAN8.0/
GBSS15.0/RAN
15.0

threshold.
l SRAN8.1/
GBSS15.1/RAN
15.1

task is created).
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2889
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Ratio of
Short
Calls
(MOC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

call duration.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Call
Duration
(MTC)
[0,
+)
Second

call duration.
incomplete.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2890
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Short
Calls
(MTC)
[0,
+)
Numbe
r
Number of short calls for the mobileterminated party during a successful

call.
l SRAN8.0/
GBSS15.0/RAN
15.0

threshold.
l SRAN8.1/
GBSS15.1/RAN
15.1

task is created).
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Short
Calls
(MTC)
[0.00
,
100.0
0]
Proportion of short calls for the mobileterminated party during a successful

call.
l SRAN8.0/
GBSS15.0/RAN
15.0
Proportion of short calls = Number of

short calls/Number of calls with valid
call durations x 100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2891
Nastar
RAN-CS/Call/Service Evaluation for Call

Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Call
Setup
Success
Times
[0,
+)
Num
ber
Number of successful call setups when

a VIP subscriber accesses the network
and initiates a call.
l SRAN8.0/
GBSS15.0/RAN
15.0

Alerting message.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Complet
ion
(Connec
t Ack)
[0,
+)
Num
ber
Same as the related counter in RAN/

CS/Call/Accessibility Evaluation.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2892
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Downlin
k Oneway
Audio
Times
[0,
+)
Num
ber

occurs in the downlink during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0

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
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.
Downlin
k Oneway
Audio
Ratio
[0.00
,
100.
00]
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

l SRAN8.0/
GBSS15.0/RAN
15.0

= Number of times that one-way audio
100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2893
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Uplink
Oneway
Audio
Times
[0,
+)
Num
ber

occurs in the uplink during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0

in the uplink: The DSP in the TC of the
BSC performs periodic statistics on
the bad frame rate based on uplink
rate reaches the predefined threshold,
the BSS determines that primary oneway 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
Uplink
Oneway
Audio
Ratio
[0.00
,
100.
00]
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

uplink in all successful call setups.
l SRAN8.0/
GBSS15.0/RAN
15.0

uplink in all successful call setups =
100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2894
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Downlin
k/Uplink
NoAudio
Times
[0,
+)
Num
ber
Number of times that no audio occurs

in both the uplink and downlink during
calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Downlin
k/Uplink
No
Audio
Rate
[0.00
,
100.
00]

successful call setups where one-way
audio occurs in both the uplink and
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2895
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Downlin
k
Crosstal
k Times
[0,
+)
Num
ber

in the downlink during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0

A interfaces.
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
k
Crosstal
k Ratio
[0.00
,
100.
00]
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

l SRAN8.0/
GBSS15.0/RAN
15.0

= Number of successful call setups
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2896
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Uplink
Crosstal
k Times
[0,
+)
Num
ber

in the uplink during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0

A interfaces.
crosstalk: The DSP of the BTS inserts
free bits of uplink speech TRAU
frames. The DSP of the TC decodes
the unique call identifier and checks its
detected within the test period,
crosstalk occurs in the uplink.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink
Crosstal
k Ratio
[0.00
,
100.
00]

l SRAN8.0/
GBSS15.0/RAN
15.0

successful call setups where crosstalk
100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2897
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Downlin
k HQI
[0.00
,
100.
00]
Average value of downlink HQIs after

l SRAN8.0/
GBSS15.0/RAN
15.0

version:
Poor
Downlin
k HQI
Times
[0,
+)
Num
ber
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

successful.
l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2898
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Uplink
HQI
[0.00
,
100.
00]
Average value of uplink high quality

indicators (HQIs) after the call setup is
successful.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1

l SRAN9.0/
GBSS16.0/
RAN16.0

version:
Poor
Uplink
HQI
Times
[0,
+)
Num
ber
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1

l SRAN11.0/
GBSS18.0/
RAN18.0

successful.
l SRAN8.0/
GBSS15.0/RAN
15.0

a create task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2899
Nastar
Parame
ter
Ran
ge
Unit
Description
Average
Uplink
VQI
[1.00
,
5.00]
N/A
Average value of uplink voice quality l SRAN8.0/

indicators (VQIs) during calls.
GBSS15.0/RAN
15.0
Average value for the uplink VQIs of
successful call setups = Aggregated
value of uplink VQIs/Number of
uplink VQI tests
Supported Solution
Version
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Poor
Uplink
VQI
Times
[0,
+)
Num
ber
Number of times that the uplink VQI

is poor during calls.
create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2900
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Downlin
k VQI
[0.00
,
5.00]
N/A
Average value of downlink voice

quality indicators (VQIs) during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
Average value for the downlink VQIs
GBSS16.0/
of successful call setups = Aggregated
RAN16.0
value of downlink VQIs/Number of
l SRAN10.0/
downlink VQI tests
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Poor
Downlin
k VQI
Times
[0,
+)
Num
ber
Number of times that the downlink

VQI is poor during calls.
create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2901
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Downlin
k Level
[0,
+)
Num
ber
Average downlink level during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Uplink
Level
[0,
+)
Num
ber
Average uplink level during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2902
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Average
Downlin
k
Quality
[0,7]
N/A
Average downlink quality during

calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Uplink
Quality
[0,7]
N/A
Average uplink quality during calls.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2903
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Downlin
k Noise
Occurre
nce
Times
[0,
+)
Num
ber

the downlink during calls, which is
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Downlin
k Noise
Ratio
[0.00
,
100.
00]

l SRAN8.0/
GBSS15.0/RAN
15.0

100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2904
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Uplink
Noise
Occurre
nce
Times
[0,
+)
Num
ber

the uplink during calls, which is
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink
Noise
Ratio
[0.00
,
100.
00]

l SRAN8.0/
GBSS15.0/RAN
15.0

100%
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2905
Nastar
Param
eter
Range
Unit
Description
Supported
Solution Version
Call
Setup
Reques
ts
(MOC)
[0,+)
Num
ber

mobile-originated party initiates to use
the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Failure
s
(MOC)
[0,+)
Num
ber

mobile-originated party experiences
the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2906
Nastar
Param
eter
Range
Unit
Description
Supported
Solution Version
Call
Setup
Succes
s Rate
(MOC)
[0.00,1
00.00]
Proportion of successful setup requests

that mobile-originated party initiates to
use the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Reques
ts
(MTC)
[0,+)
Num
ber

mobile-terminated party initiates to use
the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2907
Nastar
Param
eter
Range
Unit
Description
Supported
Solution Version
Call
Setup
Failure
s
(MTC)
[0,+)
Num
ber

mobile-terminated party experiences
the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Succes
s Rate
(MTC)
[0.00,1
00.00]
Proportion of successful call setup

requests that the mobile-terminated
party initiates to use the SMS service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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.
Issue 03 (2015-07-30)

2908
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Access
Failures
[0,
+)
Numb
er
See Access Failures in RAN-PS/PS/

Accessibility Evaluation.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Reports
of
Access
Failure
Count >
0
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2909
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Proporti
on of
Access
Failure
Count >
0
[0,10
0]

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Interrupt
ions
[0,
+)
Numb
er
See Service Interruptions in RANPS/PS/Retainability Evaluation.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2910
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Total
Reports
of
Service
Interrupt
ion
Count >
0
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
Proporti
on of
Service
Interrupt
ion
Count >
0
[0,10
0]

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2911
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Service
Interacti
on
Delays
[0,
+)
Numb
er
See Abnormal Service Interaction

Delays in RAN-PS/PS/Service
Evaluation for Delay.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Reports
of
Abnorm
al
Service
Interacti
on
Latency
Count >
0
[0,
+)
Numb
er

count exceeds 0.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2912
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Proporti
on of
Abnorm
al
Service
Interacti
on
Latency
Count >
0
[0,10
0]

count exceeds 0.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Downloa
ds at
Low
Rate
[0,
+)
Numb
er
See Downloads at Low Rate in

RAN-PS/PS/Service Evaluation for
Rate.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2913
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Proporti
on at
Low
Downloa
d Rate
[0,10
0]

download rate is low.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uploads
at Low
Rate
[0,
+)
Numb
er
See Uploads at Low Rate in RANPS/PS/Service Evaluation for Rate.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2914
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported Solution
Version
Abnorm
al
Proporti
on at
Low
Upload
Rate
[0,10
0]

measurement reports that the upload
rate is low.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Access
Failures
[0,
+)
Numb
er

of using a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of access failures = Number of

Attach Fail messages + Number of PDP
Active Fail messages + Number of
exceptions where no response to service
interaction is made + Number of
Authentication and Ciphering Failures
messages.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2915
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Attach
Requests
[0,
+)
Numb
er
Number of Attach Request messages that

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Attach
Failures
[0,
+)
Numb
er
Number of Attach Fail messages that a

VIP subscriber receives during the
l SRAN8.0/
GBSS15.0/
RAN 15.0
Attach Fail messages are triggered when

the CN rejects the Attach Request
messages from the VIP subscriber or
when the VIP subscriber fails to receive
the responses from the CN due to network
exceptions.
l SRAN8.1/
GBSS15.1/
RAN 15.1

Number of Attach Request messages Number of Attach Accept messages
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2916
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
PDP
Active
Requests
[0,
+)
Numb
er

that a VIP subscriber sends during the
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP
Active
Failures
[0,
+)
Numb
er
Number of PDP Active Fail messages that

a VIP subscriber receives during the
l SRAN8.0/
GBSS15.0/
RAN 15.0
PDP Active Fail messages are triggered

when the CN rejects the PDP Active
Request messages from the VIP
subscriber or when the VIP subscriber
fails to receive the responses from the CN
due to network exceptions.
l SRAN8.1/
GBSS15.1/
RAN 15.1

- Number of PDP Active Accept messages
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2917
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Authenti
cation
and
Cipherin
g
Requests
[0,
+)
Numb
er

requests that a VIP subscriber receives
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Authenti
cation
and
Cipherin
g
Failures
[0,
+)
Numb
er

failures that a VIP subscriber receives
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2918
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
No
Service
Interacti
on
Respons
es
[0,
+)
Numb
er
Number of times that no response to

service interaction is made.
l SRAN8.0/
GBSS15.0/
RAN 15.0

response to service interaction and,
obtained by using the following formula,
is larger than the exception threshold 2 for
the response to service interaction,
service interaction is made indicates a
value of 1; otherwise, it indicates a value
of 0. (The exception threshold 1 for the
response to service interaction and the
exception threshold 2 for the response to
service interaction are customized
algorithm parameters).
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
2919
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Service
Interrupt
ions
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0
Number of service interruptions =

cell reselection + Number of service
interruptions due to routing area update +
FLUSH LL + Number of service
interruptions due to TBF
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Interrupt
ions Due
to Cell
Reselect
ion
[0,
+)
Numb
er

process of using a data service due to cell
reselection.
The parameter is also referred to as the
number of cell reselections.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2920
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Cell
Reselect
ion
Interval
[0,
+)
Secon
d
Mean time between cell reselections

during the process for a VIP subscriber to
use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
This parameter is also referred to as the

average interval between cell
reselections.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlon
g Cell
Reselect
ion
Interval
Times
[0,
+)
Numb
er
Number of times that the cell reselection

interval is overlong during the process for
a VIP subscriber to use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If the time interval is above the threshold

for overlong cell reselection, the cell
reselection interval is overlong.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2921
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Service
Interrupt
ions Due
to
Routing
Area
Update
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Interrupt
ions Due
to
FLUSHLL
[0,
+)
Numb
er

FLUSH-LL.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2922
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Interrupt
ions Due
to TBF
[0,
+)
Numb
er

TBF.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2923
Nastar

Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Abnorm
al
Service
Interacti
on
Delays
[0,
+)
Numb
er
Number of times that the service interaction

delay is abnormal during the process for a VIP
l SRAN8.0/
GBSS15.0/
RAN 15.0

not equal to 0, Number of Abnormal Service
Service Interaction Timeouts.
l SRAN8.1/
GBSS15.1/
RAN 15.1

equal to 0, Number of Abnormal Service
Service Interactions with Long Delay.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Interacti
on
Timeout
s
[0,
+)
Numb
er
Number of times that the response to service

interaction times out during the process for a
l SRAN8.0/
GBSS15.0/
RAN 15.0

Number of Interval Timeouts for data
downlink PDUs.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2924
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Delay on
Service
Interacti
on
[0,
+)
Secon
d

interaction during the process for a VIP
l SRAN8.0/
GBSS15.0/
RAN 15.0

interaction = (Average duration of data
Average duration of data reception by using
the uplink PDU + Average duration of data
downlink PDUs) / number of valid values.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Interacti
ons with
Long
Delay
[0,
+)
Numb
er
Number of times that the average duration of

the response to service interaction is overlong
data service.
If the average duration of the response to
threshold for the average duration of the
the average duration of the response to service
interaction is overlong.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2925
Nastar

Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Downlo
ad Rate
[0.00,
+)
kbit/s
Average download rate during the process for

l SRAN8.0/
GBSS15.0/
RAN 15.0
Download rate = Number of bytes transmitted

by using the downlink PDU/Duration of data
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2926
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Downlo
ads at
Low
Rate
[0,
+)
Numb
er
Number of times that the download rate is low

data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
A download rate is low if it is lower than the

threshold for low download rate.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Abnorm
al
Proporti
on at
Low
Downlo
ad Rate
[0,10
0]

measurement reports that the download rate is
low.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2927
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Downlin
k TCP
Out-ofOrders
[0,
+)
Numb
er
Number of times that downlink TCP disorder

occurs during the process for a subscriber to
use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Average
Upload
Rate
[0.00,
+)
kbit/s
Average upload rate during the process for a

Upload rate = Number of bytes transmitted by
using the uplink PDU/Duration of data
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2928
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Uploads
at Low
Rate
[0,
+)
Numb
er
Number of times that the upload rate is low

data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
An upload rate is low if it is lower than the

threshold for low upload rate.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Set the threshold is when you create a task.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Abnorm
al
Proporti
on at
Low
Upload
Rate
[0,10
0]

measurement reports that the upload rate is
low.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2929
Nastar
RAN-PS/PS/Traffic Model Analysis

Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Downlo
ad Rate
[0.00,
+)
kbit/s
See Average Download Rate in RAN-PS/PS/

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2930
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Upload
Rate
[0.00,
+)
kbit/s
See Average Upload Rate in RAN-PS/PS/

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Total
Traffic
Downlin
k
[0,
+)
MB
Total downlink traffic during the process for

the Bytes Transmitted by Using the Downlink
PDU
Bytes Transmitted by Using the Downlink
PDU
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2931
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Total
Traffic
Uplink
[0,
+)
MB
Total uplink traffic during the process for a

l SRAN8.0/
GBSS15.0/
RAN 15.0

Bytes Transmitted by Using the Uplink PDU
PDU
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Uplink
Signalin
g Access
Times
[0,
+)
Numb
er

(uplink CCCH) during the process for a
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2932
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Average
Occupie
d
Downlin
k
Channel
s
[0,
+)
Numb
er

downlink during the process for a subscriber
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Average
Occupie
d Uplink
Channel
s
[0,
+)
Numb
er

uplink during the process for a subscriber to
use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0
/
GBSS17.0/
RAN17.0
l SRAN10.1
/
GBSS17.1/
RAN17.1
l SRAN11.0
/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2933
Nastar
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.
Common
Para
met
er
Range
Unit
Description
Supported
Solution
Version
BSC
Nam
e
1 to 64
charact
ers
N/A
Name of the BSC to which an active cell

belongs.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cell
ID
[0,2047
]
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2934
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
Cell
Nam
e
1 to 64
charact
ers
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CGI
MCCMNCLACCI
N/A
Cell global identification (CGI) of an

active cell.
MCC
[000,99
9]
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
MNC
[00,99]
l SRAN9.0/
GBSS16.0/
RAN16.0
LAC
[0,6553
5]
l SRAN10.0/
GBSS17.0/
RAN17.0
CI
[0,6553
5]
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2935
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
Gro
up
Nam
e
1 to 128
charact
ers
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User
ID
[0,2047
]
N/A
ID of a VIP subscriber. Query the ID of

a VIP subscriber using VIP group
management.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2936
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
Alia
s
1 to 64
charact
ers
N/A
Name of a VIP alias. Query the alias of a

VIP subscriber using VIP group
management.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMS
I
N/A
N/A

information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2937
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
IME
ITAC
N/A
N/A
International mobile equipment identitytype allocation code (IMEI-TAC) of the

terminal used by a VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ter
mina
l
Mod
el
N/A
N/A

subscriber. Obtain the terminal type in
the Terminal Type Management window
based on the IMEI-TAC of the terminal
used by the VIP subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2938
Nastar
Para
met
er
Range
Unit
Description
Supported
Solution
Version
Serv
ice
Typ
e
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2939
Nastar
Par
am
eter
R
a
n
g
e
Uni
t
Acc
ess
Req
uest
s
[ Nu
0 mbe
,
r
+
Description
Supported
Solution
Version
Number of access requests that a VIP group or VIP l SRAN8.0/

subscriber initiates during the process of using a call
GBSS15.0/
or SMS service in an active cell.
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acc
ess
Fail
ures
[ Nu
0 mbe
,
r
+
Number of access failures that a VIP group or VIP

subscriber experiences during the process of using a
call or SMS service in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2940
Nastar
Par
am
eter
R
a
n
g
e
Uni
t
Abn
orm
al
TAs
on
Acc
ess
[ Nu
0 mbe
,
r
+
Description
Supported
Solution
Version
Number of abnormal TA values that a VIP group or

VIP subscriber experiences during the process of
attempting to access the network in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abn
orm
al
RA
CH
Lev
els
on
Acc
ess
[ Nu
0 mbe
,
r
+
Number of abnormal RACH levels that a VIP group

or VIP subscriber experiences during the process of
attempting the network in an active cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2941
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Rele
ases
[
0
,
+

u releases the Call service in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abn
orm
al
Rele
ases
[
0
,
+

u abnormally releases the Call service in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2942
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Inte
rRA
T
Inco
min
g
Han
dov
er
Req
uest
s
[
0
,
+
N Number of incoming inter-RAT handover requests that

u a VIP group or VIP subscriber initiates in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Inte
rRA
T
Inco
min
g
Han
dov
er
Fail
ures
[
0
,
+
N Number of incoming inter-RAT handover failures that l SRAN8.0/

u a VIP group or VIP subscriber experiences in an active
GBSS15.0/
m cell.
RAN 15.0
b
l SRAN8.1/
e
GBSS15.1/
r
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2943
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Tota
l
Call
Setu
p
Req
uest
s
[
0
,
+

u subscriber initiates in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setu
p
Fail
ures
[
0
,
+

u subscriber experiences in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2944
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Abn
orm
al
Rele
ase
Bef
ore
Call
Co
mpl
etio
n
[
0
,
+
N Number of call releases that a VIP group or VIP

u subscriber experiences before call completion in an
m active cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2945
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Abn
orm
al
Call
Rele
ases
[
0
,
+
N Number of abnormal call releases that a VIP group or

u VIP subscriber experiences in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2946
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Call
Setu
p
Req
uest
s
(M
OC)
[
0
,
+

u subscriber initiates in an active cell as the mobilem originated party.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setu
p
Fail
ures
(M
OC)
[
0
,
+

u subscriber experiences in an active cell as the mobilem originated party.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2947
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Call
Setu
p
Req
uest
s
(MT
C)
[
0
,
+

u subscriber initiates in an active cell as the mobilem terminated party.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setu
p
Fail
ures
(MT
C)
[
0
,
+

u subscriber experiences in an active cell as the mobilem terminated party.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2948
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Atta
ch
Req
uest
s
[
0
,
+
N Number of Attach Request messages that a VIP group or

u VIP subscriber sends in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PD
P
Acti
ve
Req
uest
s
[
0
,
+
N Number of PDP Active Request messages that a VIP

u group or VIP subscriber sends in an active cell.
m
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2949
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
No
Serv
ice
Inte
racti
on
Res
pon
ses
[
0
,
+
N Number of exceptions where no response to service

u interaction is made when a VIP group or VIP subscriber
m is using a service in an active cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2950
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Inte
rrup
tion
s
Due
to
Cell
Res
elec
tion
[
0
,
+

u subscriber experiences due to cell reselection in an active
m cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ove
rlon
g
Cell
Res
elec
tion
Inte
rval
Tim
es
[
0
,
+
N Number of times that the cell reselection interval is

u overlong when a VIP group or VIP subscriber is using a
m service in an active cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2951
Nastar
Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Serv
ice
Inte
rrup
tion
s
Due
to
Rou
ting
Are
a
Upd
ate
[
0
,
+

u subscriber experiences due to routing area update in an
m active cell.
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2952
Nastar
RAN-PS/PS/Service Quality Evaluation for Delay

Par
am
eter
R
a
n
g
e
U Description
n
i
t
Supported
Solution
Version
Serv
ice
Inte
racti
on
Tim
eout
s
[
0
,
+
N Number of times that the duration of the response to

u service interaction is overlong when a VIP group or VIP
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Serv
ice
Inte
racti
ons
with
Lon
g
Del
ay
[
0
,
+
N Number of times that the delay of the response to service

u interaction is overlong when a VIP group or VIP
b
e
r
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2953
Nastar
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
er
Rang
e
Unit
Description
Supported Solution
Version
Server IP
N/A
N/A
IP address of an active server.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Server
Name
N/A
N/A
Name of an active server. Obtain

the name of an active server by
choosing System Function >
Data Service Server
the IP address of the server.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

2954
Nastar
Paramet
er
Rang
e
Unit
Description
Supported Solution
Version
Server
Port
N/A
N/A
Port number of an active server.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Service
Name
N/A
N/A
Name of an active service.

Obtain the name of an active
service by choosing System
Function > Data Service Server
the Server IP and Server Port
values of the service.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Total
Reports
[0,
+)
Num
ber
Number of reports generated

when a user accesses the server.
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

2955
Nastar
Paramet
er
Rang
e
Unit
Description
Supported Solution
Version
ServerRelated
Service
Abnorma
lities
[0,
+)
Num
ber
Server-Related Service
Abnormalities = No Service
Interaction Responses + Service
Interaction Timeouts + Service
Interaction with Long Delay +
Downlink TCP Out-of-Orders
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Paramet
er
Rang
e
Unit
Description
Supported Solution
Version
No
Service
Interactio
n
Response
s
[0,
+)
Num
ber
Number of times that no

response to service interaction
is made when a VIP group or
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0
Issue 03 (2015-07-30)

2956
Nastar

Paramet
er
Rang
e
Unit
Description
Supported Solution
Version
Service
Interactio
n
Timeouts
[0,
+)
Num
ber
Number of times that the response

to service interaction times out
when a VIP group or VIP subscriber
is using a service in an active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Interactio
n with
Long
Delay
[0,
+)
Num
ber
Number of times that the duration of

the response to service interaction is
overlong when a VIP group or VIP
subscriber is using a service in an
active cell.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

2957
Nastar

Paramet
er
Range
Unit
Description
Supported Solution
Version
Downlin
k TCP
Out-ofOrders
[0,+)
Num
ber

downlink TCP disorder
occurs when a VIP group or
l SRAN8.0/GBSS15.0/
RAN 15.0
l SRAN8.1/GBSS15.1/
RAN 15.1
l SRAN9.0/GBSS16.0/
RAN16.0
RAN17.0
RAN17.1
RAN18.0


Issue 03 (2015-07-30)

2958
Nastar
Common
Parameter
Range
Unit
Description
Supported
Solution
Version
In-depth
Analysis
N/A
N/A
When the
dimension is
Group, this
parameter is
used to switch
from the
analysis results
of a VIP group
to the analysis
results of VIP
subscribers in
this group.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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
group.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
User ID
[1,+)
N/A
Identity of a VIP
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
User ID, which

is created by the
system when
creating a VIP
User in the VIP
Group
Management.
Issue 03 (2015-07-30)

2959
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Alias
N/A
N/A
Alias of a VIP
subscriber.
Query the name
of a VIP
subscriber using
VIP group
management
based on the
IMSI of the VIP
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
IMSI
N/A
N/A
IMSI
information of a
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Note: Only
when you have
the "User
Identity" right,
you can view the
IMSI
information.
IMEI-TAC
00000000-9999
9999
N/A
First eight digits

in the IMEI of a
UE.
IMEI is
international
mobile
equipment
identity for short
and TAC is type
approval code
for short.
Terminal Model
Issue 03 (2015-07-30)
N/A
N/A
Type of the UE
used by a VIP
subscriber.
Query the UE
type of a VIP
subscriber using
terminal type
management
based on the
IMEI-TAC of
the VIP
subscriber.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
2960
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Service Type
N/A
N/A
Service type for

a counter.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Number of
Abnormal
Indicator
[0,+)
Number
Number of
abnormal
counters in all
counter sets
determined
based on the
result thresholds
set when
engineers create
a task.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Reports
[0,+)
Number
Indicates the
number of
records
generated for all
service types
during the
network access
of a subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Accessibility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
[0,+)
Number

setup requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2961
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Number
Number of
service RRC
setup requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Requests
[0,+)
Number
Number of RRC
reestablishment
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Number
Number of
failed RRC
reestablishment
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Success Rate
[0,100]
RRC
reestablishment
success rate.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
intra-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Mobility
Issue 03 (2015-07-30)

2962
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handovers after
a UE initiates
intra-RAT
outgoing
handover
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Success Rate
[0,100]
Ratio of
handovers to
intra-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
intra-RAT
outgoing
handover
requests during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Success Rate
(with Data
Transmission)
[0,100]
Ratio of
handovers to
intra-RAT
outgoing
handover
requests
initiated by a UE
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2963
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Success Rate
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2964
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Success Rate
(with Data
Transmission)
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a UE
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Success
Rate
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2965
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through CSFB
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Success
Rate (with Data
Transmission)
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through CSFB
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a UE
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2966
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Success Rate
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through
SRVCC during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Success Rate
(with Data
Transmission)
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through
SRVCC during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Issue 03 (2015-07-30)

2967
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Requests
[0,+)
Number

Evolved Radio
Access Bearer)
setup requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Number
Number of
failed E-RAB
setups after a
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Rate
[0,100]
Ratio of
E-RAB setup
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2968
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version

Times
[0,+)
Number
Number of
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate
[0,100]
Ratio of
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Times (with
Data
Transmission)
[0,+)
Number
Number of
with data
transmission
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate (with Data
Transmission)
[0,100]
Ratio of
with data
transmission
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2969
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB Setup

Delay
[0,+)
Second
Average ERAB setup

delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB setup

delay = E-RAB
setup delay/
delay reports
The E-RAB
setup delay
indicates the
duration from
the time when
the Initial
Context Setup
Request
message is sent
to the time when
the Initial
Context Setup
Response
message is
received or that
from the time
when the ERAB Setup
Request
message is sent
to the time when
the E-RAB
Setup Response
message is
received.
Issue 03 (2015-07-30)

2970
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Long E-RAB
Setup Delay
Times
[0,+)
Number
Number of
times when the
E-RAB setup
delay is greater
delay threshold.
The threshold is
set during
analysis task
creation.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion of
long E-RAB
Setup Delay
[0,100]

delay to the
delay reports.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0,+)
Second

recorded in a
report.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2971
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink VQI
[1.00,5.00]
N/A
Average value
for the downlink
voice quality
indicators
(VQIs) of
successful call
setups.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
VQI is the Mean

Opinion Score
(MOS) and
indicates the
voice quality of
a call. The value
of the voice
quality ranges
from 1 to 5. A
larger value
indicates better
voice quality.
Average value
for the downlink
VQIs of
successful call
setups =
Aggregated
value of
downlink VQIs/
Total number of
downlink VQI
tests
Poor Downlink
VQI Times
[0,+)
Number
Number of poor
downlink VQIs.
The exception
threshold is set
by engineers
during task
creation.
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
2972
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink VQI
[1.00,5.00]
N/A
Average value
for the uplink
VQIs of
successful call
setups.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
VQI is the MOS

and indicates the
voice quality of
a call. The value
of the voice
quality ranges
from 1 to 5. A
larger value
indicates better
voice quality.
Average value
for the uplink
VQIs of
successful call
setups =
Aggregated
value of uplink
VQIs/Total
number of
uplink VQI tests
Poor Uplink
VQI Times
[0,+)
Number
Number of poor
uplink VQIs.
The exception
threshold is set
by engineers
during task
creation.
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
2973
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
(MB)
[0,+)
MB
Total downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Transmission
Duration(s)
[0,+)
Second
Average
downlink data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Throughput
[0,+)
kbit/s
Average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
downlink
throughput =
Total downlink
throughput/
Total downlink
data
transmission
duration
Issue 03 (2015-07-30)

2974
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Low Average
Downlink
Throughput
Times
[0,+)
Number
Number of
times when the
average
downlink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
Uplink Traffic
Volume(MB)
[0,+)
MB
Total uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Transmission
Duration(s)
[0,+)
Second
Average uplink
data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0,+)
kbit/s
Average uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average uplink
throughput =
Total uplink
throughput/
Total uplink
data
transmission
duration
Issue 03 (2015-07-30)

2975
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Low Average
Uplink
Throughput
Times
[0,+)
Number
Number of
times when the
average uplink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Requests
[0,+)
Number

requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Number
Number of
failed E-RAB
setups after a
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2976
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Rate
[0,100]
Ratio of
E-RAB setup
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Times
[0,+)
Number
Number of
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate
[0,100]
Ratio of
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2977
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version

Times (with
Data
Transmission)
[0,+)
Number
Number of
with data
transmission
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate(with Data
Transmission)
[0,100]
Ratio of
with data
transmission
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2978
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average ERAB Setup

Delay
[0,+)
Second
Average ERAB setup

delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB setup

delay = E-RAB
setup delay/
delay reports
The E-RAB
setup delay
indicates the
duration from
the time when
the Initial
Context Setup
Request
message is sent
to the time when
the Initial
Context Setup
Response
message is
received or that
from the time
when the ERAB Setup
Request
message is sent
to the time when
the E-RAB
Setup Response
message is
received.
Issue 03 (2015-07-30)

2979
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Long E-RAB
Setup Delay
Times
[0,+)
Number
This parameter
indicates the
number of times
when the ERAB setup
delay is greater
delay threshold.
The threshold is
set during
analysis task
creation.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion of
long E-RAB
Setup Delay
[0,100]

delay to the
delay reports.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0,+)
Second
Average ERAB
occupation
duration
recorded in a
report.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
[0,+)
MB
Total downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2980
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Transmission
Duration
[0,+)
Second
Average
downlink data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Throughput
[0,+)
kbit/s
Average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
downlink
throughput =
Total downlink
throughput/
Total downlink
data
transmission
duration
Low Average
Downlink
Throughput
Times
[0,+)
Number
Number of
times when the
average
downlink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
Uplink Traffic
Volume
Issue 03 (2015-07-30)
[0,+)
MB
Total uplink
throughput of
PS services.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
2981
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Transmission
Duration
[0,+)
Second
Average uplink
data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0,+)
kbit/s
Average uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average uplink
throughput =
Total uplink
throughput/
Total uplink
data
transmission
duration
Low Average
Uplink
Throughput
Times
[0,+)
Number
Number of
times when the
average uplink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.

Issue 03 (2015-07-30)

2982
Nastar
Common
Parameter
Range
Unit
Description
Supported
Solution
Version
eNodeB ID
N/A
N/A
ID of an eNodeB.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
eNodeB Name
1 to 64
charact
ers
N/A
Name of an eNodeB.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
Cell ID
N/A
N/A
ID of a cell.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
Cell Name
1 to 64
charact
ers
N/A
Name of a cell.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
N/A
N/A
Service Type


eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
[0,+)
Number

setup requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2983
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Number
Number of
service RRC
setup requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Requests
[0,+)
Number
Number of RRC
reestablishment
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Number
Number of
failed RRC
reestablishment
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
intra-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RAN NET-Mobility
Issue 03 (2015-07-30)

2984
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2985
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Incoming
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2986
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through CSFB
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2987
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through
SRVCC during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Requests
[0,+)
Number

requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Number
Number of
failed E-RAB
setups initiated
by a VIP group
or VIP
subscriber in an
active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2988
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version

Times
[0,+)
Number
Number of
a VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Times (with
Data
Transmission)
[0,+)
Number
Number of
a VIP group or
VIP subscriber
in an active cell
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Common
Parameter
Ran
ge
Unit
Description
Supported
Solution Version
MME
N/A
N/A
ID of a MME.
eRAN 6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
MME format:
MMEGroupIDMMECode
Service Type
Issue 03 (2015-07-30)
N/A
N/A
Service type for a

counter.

eRAN6.0/
eRAN6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
2989
Nastar
RAN NET-Mobility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of intra-RAT
outgoing handover
an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2990
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Numb
er

CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Numb
er

CSFB during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Numb
er

SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2991
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Numb
er

SRVCC during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Parameter
Range
Unit
Description
Supported
Solution Version
E-RAB Setup
Requests
[0,+)
Numbe
r
Number of E-RAB
setup requests
initiated by a VIP
group or VIP
subscriber in an
active mme.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Numbe
r

by a VIP group or
active mme.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
mme.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

2992
Nastar
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times (with
Data
Transmission)
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
mme during data
transmission.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported Solution
Version
E-RAB Setup
Success Times
[0,+)
Nu
mbe
r
UE initiates E-RAB
setup requests.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average E-RAB
Setup Delay(s)
[0,+)
Sec
ond
Average E-RAB setup

setup delay = E-RAB
E-RAB setup delay
reports The E-RAB
Context Setup
Response message is
time when the E-RAB
the E-RAB Setup
Response message is
received.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

2993
Nastar

Parameter
Range
Uni
t
Description
Supported Solution
Version
Downlink VQI
[1.00,5.00]
N/A

eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the Mean

Opinion Score (MOS)
value of the voice
5. A larger value
quality.
downlink VQIs of
Aggregated value of
downlink VQIs/Total
number of downlink
VQI tests
Uplink VQI
[1.00,5.00]
N/A

uplink VQIs of
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the MOS and

indicates the voice
value of the voice
5. A larger value
quality.
uplink VQIs of
Aggregated value of
uplink VQIs/Total
tests
Issue 03 (2015-07-30)

2994
Nastar

Evaluation for Rate
Parameter
Range
Unit
Description
Supported Solution
Version
Downlink
Traffic Volume
(MB)
[0,+)
MB
Total downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Downlink
Transmission
Duration(s)
[0,+)
Downlink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average
Downlink
Throughput
(kbit/s)
[0,+)
kbit/s
Average downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink Traffic
Volume(MB)
[0,+)
MB

of PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink
Transmission
Duration(s)
[0,+)
Secon
d
Uplink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average Uplink
Throughput
(kbit/s)
[0,+)
kbit/s
Average uplink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average downlink
throughput = Total
Total downlink data
Average uplink
throughput = Total
uplink data

Issue 03 (2015-07-30)

2995
Nastar
Common
Parameter
Ran
ge
Unit
Description
Supported
Solution Version
TAC
[0,65
535]
N/A
Indicates the
tracking area code
of a cell.
eRAN6.0/
eRAN6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
Service Type
N/A
N/A
Service type for a

counter.
eRAN6.0/
eRAN6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Un
it
Description
Supported
Solution
Version
RRC Setup
[0,+)
Nu
mb
er

in an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Setup
Requests
(Service)
[0,+)
Nu
mb
er

active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Requests
[0,+)
Nu
mb
er
Number of RRC
mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Nu
mb
er

mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2996
Nastar
RAN NET-Mobility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of intra-RAT
outgoing handover
an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2997
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Numb
er

CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Numb
er

CSFB during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Numb
er

SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

2998
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Numb
er

SRVCC during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Parameter
Range
Unit
Description
Supported
Solution Version
E-RAB Setup
Requests
[0,+)
Numbe
r
Number of E-RAB
setup requests
initiated by a VIP
group or VIP
subscriber in an
active cell.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Numbe
r

by a VIP group or
active cell.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
cell.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

2999
Nastar
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times (with
Data
Transmission)
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
cell during data
transmission.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported Solution
Version
E-RAB Setup
Success Times
[0,+)
Nu
mbe
r
UE initiates E-RAB
setup requests.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average E-RAB
Setup Delay(s)
[0,+)
Sec
ond
Average E-RAB setup

setup delay = E-RAB
E-RAB setup delay
reports The E-RAB
Context Setup
Response message is
time when the E-RAB
the E-RAB Setup
Response message is
received.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

3000
Nastar

Parameter
Range
Uni
t
Description
Supported Solution
Version
Downlink VQI
[1.00,5.00]
N/A

eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the Mean

Opinion Score (MOS)
value of the voice
5. A larger value
quality.
downlink VQIs of
Aggregated value of
downlink VQIs/Total
number of downlink
VQI tests
Uplink VQI
[1.00,5.00]
N/A

uplink VQIs of
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the MOS and

indicates the voice
value of the voice
5. A larger value
quality.
uplink VQIs of
Aggregated value of
uplink VQIs/Total
tests
Issue 03 (2015-07-30)

3001
Nastar

Evaluation for Rate
Parameter
Range
Unit
Description
Supported Solution
Version
Downlink
Traffic Volume
(MB)
[0,+)
MB
Total downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Downlink
Transmission
Duration(s)
[0,+)
Downlink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average
Downlink
Throughput
(kbit/s)
[0,+)
kbit/s
Average downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink Traffic
Volume(MB)
[0,+)
MB

of PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink
Transmission
Duration(s)
[0,+)
Secon
d
Uplink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average Uplink
Throughput
(kbit/s)
[0,+)
kbit/s
Average uplink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average downlink
throughput = Total
Total downlink data
Average uplink
throughput = Total
uplink data
5.10.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.
Issue 03 (2015-07-30)

3002
Nastar
Common
Parameter
Rang
e
Unit
Description
Supported
Solution Version
Deep
Analysis
N/A
N/A
When the dimension is Group, this

analysis results of a VIP group to
those of the VIP subscribers in this
group.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
When the dimension is User, this

analysis results of counters to those
of the calls.
Group
Name
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
IMSI
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

MSISDN
N/A
N/A
subscriber.
Issue 03 (2015-07-30)
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
IMEI-TAC
N/A
N/A

(IMEI-TAC) of the terminal used
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User ID
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Alias
N/A
N/A
Alias of a VIP subscriber. You can

obtain the user name in the VIP
Group Management window based
on the IMSI of the VIP subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Terminal
Model
N/A
N/A

subscriber. You can obtain the
terminal type in the Terminal Type
Management window based on the
IMEI-TAC of the terminal used by
the VIP subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

3003
Nastar
Parameter
Rang
e
Unit
Description
Supported
Solution Version
Total
Reports
[0,
+)
Numb
er
Indicates the number of records

generated for all service types
during the network access of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Service
Type
N/A
N/A

counter.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Number of
Abnormal
KPIs
[0,
+)
Numb
er
Number of abnormal counters in all

counter sets determined based on
the result thresholds set when
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGSN/Accessability/Attach
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN-Attach
Requests
[0,+)
Numb
er
Number of attach process requests

and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Attach processes include:

GPRS attach
Combined attach
SGSN-Attach
Failures
[0,+)
Numb
er
Number of attach process failures

and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN-Attach
Success Rate
[0.00,10
0.00]
Attach process success rate by a

UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Attach success rate = (1 - Number

of attach failures/Number of attach
requests) x 100%
SGSN-Average
Attach Delay
Issue 03 (2015-07-30)
[0,+)
ms
Average delay of an attach process

and UMTS networks.

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
3004
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSNOverlong
Attach Delays
[0,+)
Numb
er

exception threshold of an attach
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN/Accessability/Service Req
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN-Service
Req Requests
[0,+)
Number

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

includes:
Service Request
SGSN-Service
Req Failures
[0,+)
Number

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN-Service
Req Success
Rate
[0.00,100.
00]
Service req process success rate

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Service req success rate = (1 Number of service req failures/

requests) x 100%
Issue 03 (2015-07-30)
SGSN-Average
Service Req
Delay
[0,+)
ms
Average delay of a service req

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSNOverlong
Service Req
Delays
[0,+)
Number

service req process by a VIP
UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3005
Nastar
SGSN/Accessability/Paging
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN-Paging
Requests
[0,+)
Number

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
The paging process includes

Paging.
SGSN-Paging
Failures
[0,+)
Number

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN-Paging
Success Rate
[0.00,100.
00]
Paging process success rate by

a VIP subscriber on the GSM
and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

100%
Issue 03 (2015-07-30)
SGSN-Average
Paging Delay
[0,+)
ms

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSNOverlong
Paging Delays
[0,+)
Number

UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3006
Nastar
SGSN/Accessability/PDP Act
Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Act
Requests
[0,+)
Numb
er

requests by a VIP subscriber on the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP act processes include:

MS Init PDP Act
CN Init PDP Act
PDP Act
Failures
[0,+)
Numb
er

failures by a VIP subscriber on the
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP Act
Success Rate
[0.00,100.
00]
PDP act process success rate by a

UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP act success rate = (1 - Number

of PDP act failures/Number of
PDP act requests) x 100%
Issue 03 (2015-07-30)
Average PDP
Act Delay
[0,+)
ms
Average delay of a PDP act

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Overlong PDP
Act Delays
[0,+)
Numb
er

exception threshold of a PDP act
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3007
Nastar
SGSN/Accessability/PDP Sec Act

Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Sec Act

Requests
[0,+)
Numbe
r

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
The PDP sec act process

includes:
MS Init PDP Sec Act
CN Init PDP Sec Act
PDP Sec Act
Failures
[0,+)
Numbe
r

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP Sec Act

Success Rate
[0.00,100.0
0]
PDP sec act process success rate

and UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDP sec act success rate = (1 Number of PDP sec act failures/
Number of PDP sec act
requests) x 100%
Issue 03 (2015-07-30)
Average PDP
Sec Act Delay
[0,+)
ms
Average delay of a PDP sec act

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Overlong PDP
Sec Act Delays
[0,+)
Numbe
r

the exception threshold of a PDP
sec act process by a VIP
UMTS networks.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3008
Nastar
SGSN/Accessability/RAB Assignment
Parameter
Range
Unit
Description
Supported
Solution
Version
RAB
Assignment
Requests
[0,+)
Numbe
r
Number of RAB Assignment

requests of a VIP subscriber on
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAB
Assignment
Failures
[0,+)
Numbe
r
Number of RAB assignment

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAB
Assignment
Success Rate
[0.00,100.0
0]
RAB assignment success rate of

a VIP subscriber on the GSM/
UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAB assignment success rate =

(1 - Number of RAB assignment
failures/Number of RAB
Assignment requests) x 100%
Issue 03 (2015-07-30)
Average RAB
Assignment
Delay
[0,+)
ms
Average RAB assignment delay

of a VIP subscriber on the GSM/
UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Overlong RAB
Assignment
Delays
[0,+)
Numbe
r

assignment delay of a VIP
subscriber exceeds the
predefined exception threshold
on the GSM/UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3009
Nastar
SGSN/Accessability/PDN GW Dedicated Bearer Act

Parameter
Range
Unit
Description
Supported
Solution
Version
PDN GW
Dedicated
Bearer Act
Requests
[0,+)
Numbe
r
Number of PDN GW
Dedicated Bearer Act requests
GSM/UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
A PDN GW Dedicated Bearer

Act request indicates a PDN
GW dedicated bearer
activation.
PDN GW
Dedicated
Bearer Act
Failures
[0,+)
Numbe
r
Number of PDN GW dedicated

bearer activation failures of a
VIP subscriber on the GSM/
UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PDN GW
Dedicated
Bearer Act
Success Rate
[0.00,100.
00]

activation success rate of a VIP
network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

activation success rate = (1 Number of PDN GW dedicated
bearer activation failures/
Number of PDN GW
Dedicated Bearer Act requests)
x 100%
Issue 03 (2015-07-30)
Average PDN
GW Dedicated
Bearer Act
Delay
[0,+)
ms
Average PDN GW dedicated

bearer activation delay of a VIP
network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Overlong PDN
GW Dedicated
Bearer Act
Delays
[0,+)
Numbe
r
Number of times that the PDN

GW dedicated bearer activation
delay of a VIP subscriber
exception threshold on the
GSM/UMTS network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3010
Nastar
SGSN/Mobility/RAU
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra SGSN
RAU Requests
[0,+)
Number

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra SGSN RAU processes

include:
Intra RAU
Intra combined RAU
Periodic RAU
Periodic combined RAU
Intra SGSN
RAU Failures
[0,+)
Number

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra SGSN
RAU Success
Rate
[0.00,100.
00]
Intra SGSN RAU process

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra SGSN RAU success

rate = (1 - Number of intra
SGSN RAU failures/
requests) x 100%
Issue 03 (2015-07-30)
Average Intra
SGSN RAU
Delay
[0,+)
ms

and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Intra
SGSN RAU
Delays
[0,+)
Number

threshold of an intra SGSN
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3011
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter SGSN
RAU Requests
[0,+)
Number

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter SGSN RAU processes

include:
Inter RAU
Inter combined RAU
Inter SGSN
RAU Failures
[0,+)
Number

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter SGSN
RAU Success
Rate
[0.00,100.
00]

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

UMTS networks.
Issue 03 (2015-07-30)
Average Inter
SGSN RAU
Delay
[0,+)
ms

and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Inter
SGSN RAU
Delays
[0,+)
Number

threshold of an inter SGSN
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAU (others)
Requests
[0.00,100.
00]
Number of other RAU

processes by a VIP
UMTS networks
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAU (others)
Failures
[0,+)
ms
Number of other RAU

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3012
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RAU (others)
Success Rate
[0,+)
Number
Other RAU process success

the GSM and UMTS
networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAU (others) success rate =

(1 - Number of RAU (others)
failures/Number of RAU
(others) requests) x 100%
SGSN/Mobility/Relocation
Parameter
Rang
e
Unit
Description
Supported
Solution
Version
Relocation
Requests
[0,
+)
Number

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Relocation processes include:

Intra SRNS relocation
Inter SRNS relocation
Relocation
Failures
[0,
+)
Number

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Relocation
Success Rate
[0.00,1
00.00]
Relocation process success rate

and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Relocation success rate = (1 Number of relocation failures/

Number of relocation requests)
x 100%
Issue 03 (2015-07-30)
Average
Relocation
Delay
[0,
+)
ms
Average delay of a relocation

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong
Relocation
Delays
[0,
+)
Number

relocation process by a VIP
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3013
Nastar
SGSN/Mobility/System Change
Parameter
Range
Unit
Description
Supported
Solution
Version
System Change
Requests
[0,+)
Numb
er

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
System change processes

include:
System Change
Failures
[0,+)
Numb
er

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
System Change
Success Rate
[0.00,100
.00]
System change process

UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
System change success rate =

(1 - Number of system change
failures/Number of system
change requests) x 100%
Issue 03 (2015-07-30)
Average System
Change Delay
[0,+)
ms
Average delay of a system

change process by a VIP
UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong
System Change
Delays
[0,+)
Numb
er

system change process by a
and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3014
Nastar
SGSN/PDP Modification/PDP Mod

Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Mod
Requests
[0,+)
Number
Number of PDP mod

and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDP mod processes

include:
MS Init PDP Mod
CN Init PDP Mod
PDP Mod
Failures
[0,+)
Number
Number of PDP mod

and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDP Mod
Success Rate
[0.00,100.
00]
PDP mod process success

rate by a VIP subscriber
on the GSM and UMTS
networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDP mod success rate = (1

- Number of PDP mod
failures/Number of PDP
mod requests) x 100%
Issue 03 (2015-07-30)
Average PDP
Mod Delay
[0,+)
ms
Average delay of a PDP

mod process by a VIP
and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong PDP
Mod Delays
[0,+)
Number

threshold of a PDP mod
process by a VIP
and UMTS networks.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3015
Nastar
SGSN/Modification/PDN GW Initiated Bearer Mod

Parameter
Range
Unit
Description
Supported
Solution
Version
PDN GW
Initiated Bearer
Mod Requests
[0,+)
Number
Number of PDN GW
requests of a VIP
UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
A PDN GW Initiated
Bearer Mod request
indicates a PDN GW
initiated bearer
modification.
PDN GW
Initiated Bearer
Mod Failures
[0,+)
Number
Number of PDN GW
initiated bearer
modification failures of a
GSM/UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDN GW
Initiated Bearer
Mod Success
Rate
[0.00,100.
00]

GSM/UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

= (1 - Number of PDN
GW initiated bearer
modification failures/
Number of PDN GW
requests) x 100%
Issue 03 (2015-07-30)
Average PDN
GW Initiated
Bearer Mod
Delay
[0,+)
ms
Average PDN GW
initiated bearer
GSM/UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong PDN
GW Initiated
Bearer Mod
Delays
[0,+)
Number

VIP subscriber exceeds
the predefined exception
threshold on the GSM/
UMTS network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3016
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MME-Attach
Requests
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
The attach process includes:

Attach
Combined Attach
MME-Attach
Failures
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Attach
Success Rate
[0.00,100.0
0]
Attach process success rate

LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Attach success rate = (1 Number of attach failures/

Number of attach requests) x
100%
Issue 03 (2015-07-30)
MME-Average
Attach Delay
[0,+)
ms
Average delay of an attach

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Overlong
Attach Delays
[0,+)
Numbe
r

threshold of an attach
on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3017
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MME-Service
Req Requests
[0,+)
Numbe
r

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

includes:
Service Request
MME-Service
Req Failures
[0,+)
Numbe
r

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Service
Req Success
Rate
[0.00,100.
00]
Service req process success

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Service req success rate = (1

- Number of service req
failures/Number of service
req requests) x 100%
Issue 03 (2015-07-30)
MME-Average
Service Req
Delay
[0,+)
ms
Average delay of a service

req process by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Overlong
Service Req
Delays
[0,+)
Numbe
r

threshold of a service req
on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3018
Nastar
MME/Accessability/Default Bearer Act

Parameter
Range
Unit
Description
Supported
Solution
Version
Default Bearer
Act Requests
[0,+)
Numb
er

Act process requests by a VIP
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
The default bearer act

processes include:
Default bearer activation in
attach
Default Bearer
Act Failures
[0,+)
Numb
er

Act process failures by a VIP
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Default Bearer
Act Success
Rate
[0.00,100.
00]

network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Default Bearer Act success

rate = (1 - Number of Default
Bearer Act failures/Number
of Default Bearer Act
requests) x 100%
Issue 03 (2015-07-30)
Default Bearer
Act Delay
[0,+)
ms
Average delay of a Default

Bearer Act process by a VIP
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Overlong
Default Bearer
Act Delays
[0,+)
Numb
er

LTE network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0

3019
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MME-Paging
Requests
[0,+)
Numb
er

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
The paging process includes:

Paging.
MME-Paging
Failures
[0,+)
Numb
er

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Paging
Success Rate
[0.00,100.
00]
Paging process success rate

LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

100%
Issue 03 (2015-07-30)
MME-Average
Paging Delay
[0,+)
ms

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME-Overlong
Paging Delays
[0,+)
Numb
er

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3020
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Dedicated
Bearer Act
Requests
[0,+)
Numbe
r

act process requests by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
The dedicated bearer act

process includes:
Dedicated bearer activation
procedure
Dedicated
Bearer Act
Failures
[0,+)
Numbe
r

act process failures by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Dedicated
Bearer Act
Success Rate
[0.00,100.
00]
Success rate of a dedicated

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Dedicated bearer act success

rate = (1 - Number of
dedicated bearer act failures/
act requests) x 100%
Issue 03 (2015-07-30)
Average
Dedicated
Bearer Act
Delay
[0,+)
ms
Average delay of a dedicated

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong
Dedicated
Bearer Act
Delays
[0,+)
Numbe
r

threshold of a dedicated
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3021
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
PDN
Connectivity
Requests
[0,+)
Number
Number of PDN
Connectivity process
requests by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
The PDN Connectivity

process includes:
UE requested PDN
connectivity
PDN
Connectivity
Failures
[0,+)
Number
Number of PDN
connectivity process
failures by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDN
Connectivity
Success Rate
[0.00,100.
00]
PDN Connectivity process

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
PDN Connectivity success

rate = (1 - Number of PDN
Connectivity failures/
Number of PDN
Connectivity requests) x
100%
Issue 03 (2015-07-30)
Average PDN
Connectivity
Delay
[0,+)
ms
Average delay of a PDN

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong PDN
Connectivity
Delays
[0,+)
Number

threshold of a PDN
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3022
Nastar
MME/Mobility/TAU
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra TAU
Requests
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra TAU processes include:

TAU
Intra USN GERAN to EUTRAN Inter RAT TAU
Intra USN UTRAN to EUTRAN Inter RAT TAU
GERAN Inter RAT RAU
UTRAN Inter RAT RAU
Combined TAU
Combined TAU
Combined TAU
Intra TAU
Failures
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra TAU
Success Rate
[0.00,100.
00]
Intra TAU process success

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra TAU success rate = (1 Number of intra TAU

failures/Number of intra TAU
requests) x 100%
Average Intra
TAU Delay
Issue 03 (2015-07-30)
[0,+)
ms

network.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
3023
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Intra
TAU Delays
[0,+)
Numbe
r

intra TAU process by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter TAU
Requests
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter TAU processes include:

TAU
to E-UTRAN TAU
GERAN/UTRAN Inter RAT
RAU
Combined TAU
to E-UTRAN Combined
TAU
Inter TAU
Failures
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter TAU
Success Rate
[0.00,100.
00]
Inter TAU process success

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter TAU success rate = (1 Number of inter TAU

failures/Number of inter TAU
requests) x 100%
Issue 03 (2015-07-30)
Average Inter
TAU Delay
[0,+)
ms

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Inter
TAU Delays
[0,+)
Numbe
r

inter TAU process by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3024
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra E-UTRAN
Handover
Requests
[0,+)
Numbe
r

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

processes include:
X2 Handover
Intra MME S1 Handover
Inter MME S1 Handover
Intra E-UTRAN
Handover
Failures
[0,+)
Numbe
r

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Intra E-UTRAN
Handover
Success Rate
[0.00,100.
00]
Success rate of an intra EUTRAN handover process

LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

success rate = (1 - Number of
failures/Number of intra EUTRAN handover requests)
x 100%
Issue 03 (2015-07-30)
Average Intra
E-UTRAN
Handover Delay
[0,+)
ms
Average delay of an intra EUTRAN handover process

LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Intra
E-UTRAN
Handover
Delays
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3025
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter RAT
Handover
Requests
[0,+)
Numbe
r
Number of inter RAT

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter RAT handover

processes include:
Intra USN UTRAN Iu mode
handover
Inter USN UTRAN Iu mode
handover
handover
handover
Inter RAT
Handover
Failures
[0,+)
Numbe
r
Number of inter RAT

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter RAT
Handover
Success Rate
[0.00,100.
00]
Success rate of an inter RAT

handover process by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Inter RAT handover success

rate = (1 - Number of inter
RAT handover failures/
Number of inter RAT
handover requests) x 100%
Issue 03 (2015-07-30)
Average Inter
RAT Handover
Delay
[0,+)
ms

RAT handover process by a
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong Inter
RAT Handover
Delays
[0,+)
Numbe
r

inter RAT handover process
LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3026
Nastar
MME/Bearer Modification/UE Requested Bearer Resource Allocation

Parameter
Range
Unit
Description
Supported
Solution
Version
UE Requested
Bearer
Resource
Allocation
Requests
[0,+)
Number
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
The UE requested bearer

resource allocation process
includes:
UE requested bearer
resource allocation
UE Requested
Bearer
Resource
Allocation
Failures
[0,+)
Number
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
UE Requested
Bearer
Resource
Allocation
Success Rate
[0.00,100
.00]
Success rate of a UE
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
UE requested bearer
resource allocation success
rate = (1 - Number of UE
allocation failures/Number
of UE requested bearer
resource allocation
requests) x 100%
Issue 03 (2015-07-30)
UE Requested
Bearer
Resource
Allocation
Delay
[0,+)
ms
Average delay of a UE
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Overlong UE
Requested
Bearer
Resource
Allocation
Delays
[0,+)
Number

threshold of a UE requested
on the LTE network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0

3027
Nastar
MME/Bearer Modification/Bearer Mod

Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer Mod
Requests
[0,+)
Numb
er

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer mod processes include:

modification with bearer QoS
update
HSS Initiated Subscribed QoS
Modification
modification without bearer
QoS update
Bearer Mod
Failures
[0,+)
Numb
er

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer Mod
Success Rate
[0.00,100
.00]
Bearer mod process success

rate by a VIP subscriber on the
LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer mod success rate = (1 Number of bearer mod failures/

Number of bearer mod
requests) x 100%
Issue 03 (2015-07-30)
Average Bearer
Mod Delay
[0,+)
ms
Average delay of a bearer mod

the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Overlong
Bearer Mod
Delays
[0,+)
Numb
er

bearer mod process by a VIP
subscriber on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3028
Nastar
MME/Bearer Modification/Bearer Resource Mod

Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer
Resource Mod
Requests
[0,+)
Number

mod process requests by a
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
The bearer resource mod

process includes:
UE requested bearer
resource modification
Bearer
Resource Mod
Failures
[0,+)
Number

mod process failures by a
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Bearer
Resource Mod
Success Rate
[0.00,100
.00]
Success rate of a bearer

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Bearer resource mod

success rate = (1 - Number
of bearer resource mod
failures/Number of bearer
resource mod requests) x
100%
Issue 03 (2015-07-30)
Bearer
Resource Mod
Delay
[0,+)
ms
Average delay of a bearer

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Overlong
Bearer
Resource Mod
Delays
[0,+)
Number

threshold of a bearer
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

3029
Nastar
GGSN/Accessability/Create PDP
Parameter
Range
Unit
Description
Supported
Solution
Version
Create PDP
Requests
[0,+)
Numb
er

procedures of a VIP
UMTS network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create PDP
Failures
[0,+)
Numb
er

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create PDP
Success Rate
[0.00,100
.00]
Success rate of the Create PDP

procedures of a VIP
UMTS network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create PDP Success Rate = (1

- Number of Create PDP
failures/Number of Create
GGSN/PDP Update/Update PDP

Parameter
Range
Unit
Description
Supported
Solution
Version
Update PDP
Requests
[0,+)
Numb
er

procedures of a VIP subscriber
on the GSM/UMTS network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update PDP
Failures
[0,+)
Numb
er

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update PDP
Success Rate
[0.00,100.
00]
Success rate of the Update

PDP procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update PDP Success Rate = (1

- Number of Update PDP
failures/Number of Update
Issue 03 (2015-07-30)

3030
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Create Session
Requests
[0,+)
Numbe
r

procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Session
Failures
[0,+)
Numbe
r

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Session
Success Rate
[0.00,100.
00]

Session procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Session Success Rate

Session failures/Number of
Create Session requests) x
100%
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Create Bearer
Requests
[0,+)
Number

procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Bearer
Failures
[0,+)
Number

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3031
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Create Bearer
Success Rate
[0.00,100.
00]

Bearer procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Bearer Success Rate

Bearer failures/Number of
Create Bearer requests) x
100%
SAE-GW/Accessability/Create Indirect Data Forwarding

Parameter
Range
Unit
Description
Supported
Solution
Version
Create Indirect
Data
Forwarding
Requests
[0,+)
Number
Number of Create
Indirect Data
Forwarding
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Indirect
Data
Forwarding
Failures
[0,+)
Number
Number of Create
Indirect Data
Forwarding failures
the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Create Indirect
Data
Forwarding
Success Rate
[0.00,100.00]
Success rate of the

Forwarding
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

Forwarding Success
Forwarding failures/
Number of Create
Indirect Data
Forwarding requests)
x 100%
Issue 03 (2015-07-30)

3032
Nastar
SAE-GW/Bearer Modification/Modify Bearer

Parameter
Range
Unit
Description
Supported
Solution
Version
Modify Bearer
Requests
[0,+)
Numb
er
Number of Modify
LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Failures
[0,+)
Numb
er
Number of Modify
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Success Rate
[0.00,100.00]
Success rate of the

Modify Bearer
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer Success

Modify Bearer failures/
Number of Modify
Bearer requests) x
100%
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Update Bearer
Requests
[0,+)
Numbe
r
Number of Update
LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update Bearer
Failures
[0,+)
Numbe
r
Number of Update
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3033
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Update Bearer
Success Rate
[0.00,100.00]
Success rate of the

Update Bearer
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Update Bearer Success

Update Bearer failures/
Number of Update
Bearer requests) x 100%
SAE-GW/Bearer Modification/Modify Bearer Command

Parameter
Range
Unit
Description
Supported
Solution
Version
Modify Bearer
Command
Requests
[0,+)
Numbe
r
Number of Modify
Bearer Command
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Command
Failures
[0,+)
Numbe
r
Number of Modify
Bearer Command
failures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Command
Success Rate
[0.00,100.00]
Success rate of the

Modify Bearer
Command procedures
the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Modify Bearer
Command Success Rate
= (1 - Number of Modify
Bearer Command
failures/Number of
Modify Bearer
Command requests) x
100%
Issue 03 (2015-07-30)

3034
Nastar
SAE-GW/Bearer Modification/Bearer Resource Command

Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer Resource
Command
Requests
[0,+)
Number
Number of Bearer
Resource Command
procedures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer Resource
Command
Failures
[0,+)
Number
Number of Bearer
Resource Command
failures of a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer Resource
Command
Success Rate
[0.00,100.00]
Success rate of the

Bearer Resource
Command procedures
the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer Resource
Command Success
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.
Issue 03 (2015-07-30)

3035
Nastar
Common
Parameter
Rang
e
Unit
Description
Supported Solution
Version
Deep
Analysis
N/A
N/A

Group, this parameter is
used to switch from the
analysis results of a VIP
group to those of the VIP
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0

User, this parameter is used
to switch from the analysis
results of counters to those
of the calls.
Group
Name
N/A
N/A
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
IMSI
N/A
N/A
subscriber.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0

you can view the IMSI
information.
MSISDN
N/A
N/A
subscriber.
you can view the MSISDN
information.
Issue 03 (2015-07-30)
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
IMEI-TAC
N/A
N/A
allocation code (IMEITAC) of the terminal used
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
User ID
N/A
N/A
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Alias
N/A
N/A
Alias of a VIP subscriber.

You can obtain the user
name in the VIP Group
on the IMSI of the VIP
subscriber.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0

3036
Nastar
Parameter
Rang
e
Unit
Description
Supported Solution
Version
Terminal
Model
N/A
N/A
Type of the terminal used by

a VIP subscriber. You can
obtain the terminal type in
the Terminal Type
on the IMEI-TAC of the
terminal used by the VIP
subscriber.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Total
Reports
[0,
+)
Number

network access of a
subscriber.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Service
Type
N/A
N/A

counter.
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Number of
Abnormal
KPIs
[0,
+)
Number
Number of abnormal
counters in all counter sets
determined based on the
result thresholds set when
PS 10.0/PS 10.1/PS10.2/PS
11.0/PS12.0/PS 12.1/PS
13.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
Combined
Attach Requests
[0,+)
Numb
er

the Combined Attach
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Combined
Attach CS
Failures
[0,+)
Numb
er

Combined Attach
LTE network fails.
PS 11.0/PS 12.0/PS
12.1/PS 13.0

3037
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Combined
Attach CS
Success Rate
[0.00,100.
00]
Success rate of the

Combined Attach
procedure, which is
initiated by a VIP
network, in the CS
domain.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Combined Attach CS
Success Rate = (1 Number of failed
Combined Attach
requests in the CS
domain/Number of
Combined Attach
requests) x 100%
Combined
Attach Delay
[0,+)
ms

Combined Attach
LTE network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Overlong
Combined
Attach Delays
[0,+)
Numb
er

delay of the Combined
Attach procedure initiated
threshold.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution Version
SGs CS Paging
Requests
[0,+)
Numbe
r

the SGs CS Paging
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
The SGs CS Paging

procedure includes:
SGs Paging
Issue 03 (2015-07-30)

3038
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
SGs CS Paging
Failures
[0,+)
Numbe
r

SGs CS Paging procedure
initiated by a VIP
network fails.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
SGs CS Paging
Success Rate
[0.00,100
.00]

CS Paging procedure
initiated by a VIP
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
SGs CS Paging Success

failed SGs CS Paging
100%
SGs CS Paging
Delay
[0,+)
ms

CS Paging procedure
initiated by a VIP
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Overlong SGs
CS Paging
Delays
[0,+)
Numbe
r

delay of the SGs CS
Paging procedure
initiated by a VIP
network exceeds a
threshold.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
S1 CS Paging
Requests
[0,+)
Numbe
r

the S1 CS Paging
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
The S1 CS Paging
procedure includes:
Paging
S1 CS Paging
Failures
Issue 03 (2015-07-30)
[0,+)
Numbe
r

S1 CS Paging procedure
initiated by a VIP
network fails.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
3039
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
S1 CS Paging
Success Rate
[0.00,100
.00]
Success rate of the S1 CS

Paging procedure
initiated by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
S1 CS Paging Success
failed S1 CS Paging
100%
S1 CS Paging
Delay
[0,+)
ms

CS Paging procedure
initiated by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Overlong S1 CS
Paging Delays
[0,+)
Numbe
r

delay of the S1 CS Paging
threshold.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
S1 SMS Paging
Requests
[0,+)
Numbe
r

the S1 SMS Paging
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
The S1 SMS Paging

procedure includes:
Paging
S1 SMS Paging
Failures
Issue 03 (2015-07-30)
[0,+)
Numbe
r

S1 SMS Paging procedure
initiated by a VIP
network fails.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
3040
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
S1 SMS Paging
Success Rate
[0.00,100
.00]
Success rate of the S1

initiated by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
S1 SMS Paging Success

failed S1 SMS Paging
100%
S1 SMS Paging
Delay
[0,+)
ms

initiated by a VIP
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Overlong SMS
Paging Delays
[0,+)
Numbe
r

delay of the S1 SMS
Paging procedure
initiated by a VIP
network exceeds a
threshold.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGs SMS
Paging
Requests
[0,+)
Numbe
r

the SGs SMS Paging
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
The SGs SMS Paging

procedure includes:
SGs Paging
SGs SMS
Paging Failures
Issue 03 (2015-07-30)
[0,+)
Numbe
r

SGs SMS Paging
LTE network fails.

PS 11.0/PS 12.0/PS
12.1/PS 13.0
3041
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
SGs SMS
Paging Success
Rate
[0.00,100
.00]

initiated by a VIP
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
SGs SMS Paging Success

failed SGs SMS Paging
100%
SGs SMS
Paging Delay
[0,+)
ms

initiated by a VIP
network.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Overlong SGs
SMS Paging
Delays
[0,+)
Numbe
r

delay of the SGs SMS
Paging procedure
initiated by a VIP
network exceeds a
threshold.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution Version
Extended
Service Req
Requests
[0,+)
Numbe
r

subscriber initiates the
network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
The Extended Service Req

procedure includes:
Extended
Service Req
Failures
Issue 03 (2015-07-30)
[0,+)
Numbe
r

network fails.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
3042
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Extended
Service Req
Success Rate
[0.00,1
00.00]
Success rate of the Extended

on the LTE network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

Success Rate = (1 - Number
of failed Extended Service
Req requests/Number of
requests) x 100%
Issue 03 (2015-07-30)
Extended
Service Req
Delay
[0,+)
ms

network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Overlong
Extended
Service Req
Delays
[0,+)
Numbe
r

delay of the Extended
on the LTE network exceeds
a predefined exception
threshold.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

3043
Nastar
MME/Mobility/TAU
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra Combined
TAU Requests
[0,+)
Number

the Intra Combined
LTE network.
PS 12.0/PS 12.1/
PS 13.0
The Intra Combined

TAU procedure
includes:
Intra USN Intra EUTRAN Combined
TAU
Combined TAU
Combined TAU
Intra Combined
TAU CS
Failures
[0,+)
Number

Intra Combined TAU
LTE network fails.
PS 12.0/PS 12.1/
PS 13.0
Intra Combined
TAU CS
Success Rate
[0.00,100.0
0]
Success rate of the Intra

Combined TAU
LTE network.
PS 12.0/PS 12.1/
PS 13.0
Intra Combined TAU

CS Success Rate = (1 Number of failed Intra
Combined TAU
requests/Number of
Intra Combined TAU
requests) x 100%
Intra Combined
TAU Delay
Issue 03 (2015-07-30)
[0,+)
ms

Intra Combined TAU
LTE network.

PS 12.0/PS 12.1/
PS 13.0
3044
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong Intra
Combined TAU
Delays
[0,+)
Number

delay of the Intra
Combined TAU
threshold.
PS 12.0/PS 12.1/
PS 13.0
Inter Combined
TAU Requests
[0,+)
Number

the Inter Combined
LTE network.
PS 12.0/PS 12.1/
PS 13.0
The Inter Combined

TAU procedure
includes:
Inter USN Intra EUTRAN Combined
TAU
Inter USN GERAN/
UTRAN to E-UTRAN
Combined TAU
Inter Combined
TAU CS
Failures
[0,+)
Number

Inter Combined TAU
LTE network fails.
PS 12.0/PS 12.1/
PS 13.0
Inter Combined
TAU CS
Success Rate
[0.00,100.0
0]
Success rate of the Inter

Combined TAU
LTE network.
PS 12.0/PS 12.1/
PS 13.0
Inter Combined TAU

CS Success Rate = (1 Number of failed Inter
Combined TAU
requests/Number of
Inter Combined TAU
requests) x 100%
Issue 03 (2015-07-30)

3045
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter Combined
TAU Delay
[0,+)
ms

Inter Combined TAU
LTE network.
PS 12.0/PS 12.1/
PS 13.0
Overlong Inter
Combined TAU
Delays
[0,+)
Number

delay of the Inter
Combined TAU
threshold.
PS 12.0/PS 12.1/
PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
CSFB PS
Handover
Requests
[0,+)
Number

the CSFB PS Handover
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
The CSFB PS Handover

procedure includes:
UTRAN Iu mode Inter
RAT handover
UTRAN Iu mode Inter
RAT handover
CSFB PS
Handover
Failures
Issue 03 (2015-07-30)
[0,+)
Number

CSFB PS Handover
LTE network fails.

PS 11.0/PS 12.0/
PS 12.1/PS 13.0
3046
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CSFB PS
Handover
Success Rate
[0.00,100.0
0]
Success rate of the CSFB

PS Handover procedure
initiated by a VIP
network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
CSFB PS Handover
Success Rate = (1 Number of failed CSFB
PS Handover requests/
Number of CSFB PS
Handover requests) x
100%
CSFB PS
Handover Delay
[0,+)
ms

CSFB PS Handover
LTE network.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Overlong CSFB
PS Handover
Delays
[0,+)
Number

delay of the CSFB PS
Handover procedure
initiated by a VIP
network exceeds a
threshold.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Parameters for Viewing PS Core VIP Analysis - VoLTE Results

This section describes the parameters for querying PS Core VIP analysis VoLTE results. You
can refer to the description when querying PS Core VIP analysis VoLTE results.
Issue 03 (2015-07-30)

3047
Nastar
Common
Parameter
Range
Unit
Description
Supported
Solution
Version
Deep Analysis
N/A
N/A
When the
dimension is
Group, this
parameter is
used to switch
from the
analysis results
of a VIP group
to those of the
VIP subscribers
in this group.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
When the
dimension is
User, this
parameter is
used to switch
from the
analysis results
of counters to
those of the
calls.
Group Name
N/A
N/A
Name of a VIP
group.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
IMSI
N/A
N/A
IMSI
information of a
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Note: Only
when you have
the "User
Identity" right,
you can view the
IMSI
information.
Issue 03 (2015-07-30)

3048
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MSISDN
N/A
N/A
MSISDN
information of a
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Note: Only
when you have
the "User
Identity" right,
you can view the
MSISDN
information.
Issue 03 (2015-07-30)
User ID
N/A
N/A
ID of a VIP
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Alias
N/A
N/A
Alias of a VIP
subscriber. You
can obtain the
user name in the
VIP Group
Management
window based
on the IMSI of
the VIP
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
IMEI-TAC
N/A
N/A
International
mobile
equipment
identity-type
allocation code
(IMEI-TAC) of
the terminal
used by a VIP
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3049
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Terminal Model
N/A
N/A
Type of the
terminal used by
a VIP
subscriber. You
can obtain the
terminal type in
the Terminal
Type
Management
window based
on the IMEITAC of the
terminal used by
the VIP
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Total Reports
[0,+)
Number
Indicates the
number of
records
generated for all
service types
during the
network access
of a subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Service Type
N/A
N/A
Service type for

a following
counter.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Number of
Abnormal KPIs
[0,+)
Number
Number of
abnormal KPIs.
The abnormal
KPIs are
obtained by
comparing the
KPI values with
the exception
thresholds
which are
predefined by
engineers when
creating tasks.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3050
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Paging
Requests
[0,+)
Number
Number of
paging process
requests by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
The paging
process
includes:
Paging.
VoLTE Paging
Failures
[0,+)
Number
Number of
paging process
failures by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE Paging
Success Rate
[0.00,100.00]
Paging process
success rate by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Paging success
rate = (1 Number of
paging failures/
Number of
paging requests)
x 100%
VoLTE
Average Paging
Delay
Issue 03 (2015-07-30)
[0,+)
ms
Average delay
of a paging
process by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
3051
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Overlong
Paging Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of a
paging process
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Dedicated
Bearer Act
Requests
[0,+)
Number
Number of
dedicated bearer
act process
requests by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
The dedicated
bearer act
process
includes:
Dedicated
bearer
activation
VoLTE
Dedicated
Bearer Act
Failures
Issue 03 (2015-07-30)
[0,+)
Number
Number of
dedicated bearer
act process
failures by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
3052
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Dedicated
Bearer Act
Success Rate
[0.00,100.00]
Success rate of a
dedicated bearer
act process by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Dedicated
bearer act
success rate = (1
- Number of
dedicated bearer
act failures/
Number of
dedicated bearer
act requests) x
100%
Issue 03 (2015-07-30)
VoLTE
Average
Dedicated
Bearer Act
Delay
[0,+)
ms
Average delay
of a dedicated
bearer act
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE
Overlong
Dedicated
Bearer Act
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of a
dedicated bearer
act process by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3053
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE PDN
Connectivity
Requests
[0,+)
Number
Number of PDN
Connectivity
process requests
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
The PDN
Connectivity
process
includes:
UE requested
PDN
connectivity
Default bearer
activation in
attach
VoLTE PDN
Connectivity
Failures
[0,+)
Number
Number of PDN
connectivity
process failures
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE PDN
Connectivity
Success Rate
[0.00,100.00]
PDN
Connectivity
process success
rate by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
PDN
Connectivity
success rate = (1
- Number of
PDN
Connectivity
failures/
Number of PDN
Connectivity
requests) x
100%
Issue 03 (2015-07-30)

3054
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Average PDN
Connectivity
Delay
[0,+)
ms
Average delay
of a PDN
Connectivity
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE
Overlong PDN
Connectivity
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of a
PDN
Connectivity
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3055
Nastar
MME/Accessability/Bearer Mod
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update
Requests
[0,+)
Number
Number of PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update process
requests by a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
PDN GW
Initiated Bearer
Mod with
Bearer QoS
Update
Requests
process
includes:
PDN GW
initiated bearer
modification
with bearer QoS
update
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update Failures
Issue 03 (2015-07-30)
[0,+)
Number
Number of PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update process
failures by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
3056
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update Success
Rate
[0.00,100.00]
Success rate of
an PDN GW
Initiated Bearer
Mod with
Bearer QoS
Update process
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
PDN GW
Initiated Bearer
Mod with
Bearer QoS
Update success
rate = (1 Number of
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update failures/
Number of
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update
requests) x
100%
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update Success
Delay
Issue 03 (2015-07-30)
[0,+)
ms
Average delay
of an VoLTE
PDN GW
Initiated Bearer
Mod with
Bearer QoS
Update process
by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
3057
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of an
VoLTE PDN
GW Initiated
Bearer Mod
with Bearer QoS
Update process
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Intra EUTRAN

Handover
Requests
[0,+)
Number
Number of intra
E-UTRAN
handover
process requests
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Intra E-UTRAN
handover
processes
include:
X2 Handover
Intra MME S1
Handover
Inter MME S1
Handover
Issue 03 (2015-07-30)

3058
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Intra EUTRAN

Handover
Failures
[0,+)
Number
Number of intra
E-UTRAN
handover
process failures
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3059
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Intra EUTRAN

Handover
Success Rate
[0.00,100.00]
Success rate of
an intra EUTRAN
handover
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Intra E-UTRAN
handover
success rate = (1
- Number of
intra E-UTRAN
handover
failures/
Number of intra
E-UTRAN
handover
requests) x
100%
Issue 03 (2015-07-30)

3060
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
NOTE
The VoLTE
handover
success rate
contains the
LTE handover
success rate and
the IMS voice
bearer handover
success rate. If
the IMS voice
bearer exists
before the
VoLTE
handover but
disappears after
the handover,
the IMS voice
bearer handover
fails during the
VoLTE
handover. This
indicates a
VoLTE
handover
failure.
Therefore, in the
Nastar analysis
window of the
VoLTE
handover, if the
IMS voice
bearer is
interrupted, an
external cause
value is
displayed
indicating a
successful
handover.
However, the
displayed value
only indicates
"X2/Intra EUTRAN/Inter
MME S1/Intra
MME S1
Handover" and
the VoLTE IMS
handover fails.
Issue 03 (2015-07-30)

3061
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Average Intra EUTRAN
Handover Delay
[0,+)
ms
Average delay
of an intra EUTRAN
handover
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE
Overlong Intra
E-UTRAN
Handover
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of an
intra E-UTRAN
handover
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE SRVCC
(to GERAN)
Requests
[0,+)
Number
Number of
SRVCC(to
GERAN)
process requests
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
The SRVCC(to
GERAN)
Requests
process
includes:
GERAN or
UTRAN
Issue 03 (2015-07-30)

3062
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE SRVCC
(to GERAN)
Failures
[0,+)
Number
Number of
SRVCC(to
GERAN)
process failures
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE SRVCC
(to GERAN)
Success Rate
[0.00,100.00]
Success rate of
an SRVCC(to
GERAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SRVCC(to
GERAN)
success rate = (1
- Number of
VoLTE SRVCC
(to GERAN)
failures/
Number of
VoLTE SRVCC
(to GERAN)
requests) x
100%
Average
VoLTE SRVCC
(to GERAN)
Delay
Issue 03 (2015-07-30)
[0,+)
ms
Average delay
of an VoLTE
SRVCC(to
GERAN)
process by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
3063
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong
VoLTE SRVCC
(to GERAN)
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of an
VoLTE SRVCC
(to GERAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE SRVCC
(to UTRAN)
Requests
[0,+)
Number
Number of
SRVCC(to
UTRAN)
process requests
by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SRVCC(to
UTRAN)
Requests
process
includes:
GERAN or
UTRAN
VoLTE SRVCC
(to UTRAN)
Failures
Issue 03 (2015-07-30)
[0,+)
Number
Number of
SRVCC(to
UTRAN)
process failures
by a VIP
subscriber on
the LTE
network.

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
3064
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE SRVCC
(to UTRAN)
Success Rate
[0.00,100.00]
Success rate of
an SRVCC(to
UTRAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SRVCC(to
UTRAN)
success rate = (1
- Number of
VoLTE SRVCC
(to UTRAN)
failures/
Number of
VoLTE SRVCC
(to UTRAN)
requests) x
100%
Issue 03 (2015-07-30)
Average
VoLTE SRVCC
(to UTRAN)
Delay
[0,+)
ms
Average delay
of an VoLTE
SRVCC(to
UTRAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Overlong
SRVCC(to
UTRAN)
Delays
[0,+)
Number
Number of
delays that
exceed the
exception
threshold of an
VoLTE SRVCC
(to UTRAN)
process by a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3065
Nastar
MME/Mobility/Voice retention/Dedicated Bearer Act

Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE
Dedicated
Bearer Act
Success
[0,+)
Number
Number of
times that
dedicated bearer
is successfully
created for a
VIP subscriber
on the LTE
network.
VoLTE
Dedicated
Bearer Act
Success process
includes:
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Dedicated
bearer
activation
MME/Mobility/Voice retention/eNB Init Call Drop

Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE eNB
Init Call Drop
Cnt
[0,+)
Number
VoLTE call
drop count of a
VIP subscriber
on the LTE
network.
Process
includes:
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
MME Initiated
Dedicated
Bearer
Deactivation
Issue 03 (2015-07-30)

3066
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE eNB
Init Call Drop
rate (%)
[0.00,100.00]
VoLTE call
drop rate of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Process
includes:MME
Initiated
Dedicated
Bearer
Deactivation
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Create
Session
Requests
[0,+)
Number
Number of
Create Session
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE Create
Session Failures
[0,+)
Number
Number of
Create Session
failures of a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3067
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Create
Session Success
Rate
[0.00,100.00]
Success rate of
the Create
Session
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Create Session
Success Rate =
(1 - Number of
Create Session
failures/
Number of
Create Session
requests) x
100%
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Create
Bearer Requests
[0,+)
Number
Number of
Create Bearer
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE Create
Bearer Failures
[0,+)
Number
Number of
Create Bearer
failures of a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3068
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Create
Bearer Success
Rate
[0.00,100.00]
Success rate of
the Create
Bearer
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Create Bearer
Success Rate =
(1 - Number of
Create Bearer
failures/
Number of
Create Bearer
requests) x
100%
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Update
Bearer Requests
[0,+)
Number
Number of
Update Bearer
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
VoLTE Update
Bearer Failures
[0,+)
Number
Number of
Update Bearer
failures of a VIP
subscriber on
the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3069
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
VoLTE Update
Bearer Success
Rate
[0.00,100.00]
Success rate of
the Update
Bearer
procedures of a
VIP subscriber
on the LTE
network.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Update Bearer
Success Rate =
(1 - Number of
Update Bearer
failures/
Number of
Update Bearer
requests) x
100%
5.10.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
l
Relationships between HSSs and eNodeBs have been configured. For detailed operations,
see 3.3.8 Configuring Relationships Between HSSs and eNodeBs (Optional).
When the MME license for basic functions has been applied, the MME vendor is Huawei,
and the LTE all-signaling function needs to be used, it is recommended to connect the USN
to the Nastar for checking the single-user trace information enabled on the MME.
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.
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.
Issue 03 (2015-07-30)

3070
Nastar
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

number of a VIP
subscriber is available on
the HSS
The User Level tab page is automatically displayed for you to

view the trace reference number (which is available on the HSS)
and all-signaling switch status of the VIP subscriber.
The trace reference

number of a VIP
subscriber is unavailable
on the HSS
The User Level tab page is automatically displayed. The Nastar

randomly assigns a trace reference number, which is unique in
the Nastar system, to the VIP subscriber.
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.
Check that the data switch is successfully turned on by viewing the displayed information in the
Log Info area.
----End

Context
l
Issue 03 (2015-07-30)
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
3071
Nastar
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.
5.11.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.
NOTE
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.
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.
Supports the combined complaint analysis support between the networks on the RAN side,
including GSM/UMTS, and LTE FDD/LTE TDD.
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 5-27.
Issue 03 (2015-07-30)

3072
Nastar
Table 5-27 Function description of complaint analysis support
Issue 03 (2015-07-30)
Function Type
Description
Supported
Network
Aggregation and
analysis of cause
types in call reports
of complaining
subscribers
Helps network engineers filter and aggregate call

reports based on exception causes.
GSM/
UMTS/
LTE/PS
Core
Summary and
analysis of call
reports of
complaining
subscribers
Provide an information overview about all the filtered

call records. The information includes the information,
such as access time, access cell, release time, release
cell, and service duration. This function helps network
engineers quickly identify abnormal call records (for
example, too-short-time call records) and preliminarily
learn the situation of complaining subscribers.
GSM/
UMTS/
LTE/PS
Core
Analysis of detailed
call reports of
complaining
subscribers
Provides the detailed information about all the filtered

call records. The information includes the subscriber
information, call access information, call release
information, and handover information. This function
helps network engineers learn the key events that occur
during calls, service usage, and measurement reports
(MRs) before signaling release, accurately and quickly
assisting in problem location.
GSM/
UMTS/
LTE/PS
Core
Analysis of
procedure before
signaling release in
call reports of
complaining
subscribers
Provides the detailed procedure before signaling

release of all the filtered subscribers. This function
helps network engineers locate problems based on the
information before signaling release.
GSM/
UMTS/LTE
Analysis of
measurement
reports (MRs) on
calls of complaint
subscribers before
call release
Provides MR details and trend charts of measurement

counters, including TA, DLRxLevel, DLRxQuality/
Level, ULRxQuality/Level, MS/BTS Power, and VQI.
The VQI indicates the voice quality during services and
helps network engineers more accurately locate voice
quality problems.
GSM
Provides information about the serving cells of

subscribers before call release and the neighboring
cells. This helps engineers analyze and locate
problems.
UMTS/LTE
Mobility analysis
Provides handover information of a terminal and helps

network engineers to learn all cells that are recorded in
abnormal call records.
GSM/
UMTS/LTE
Service analysis
Analyzes RAB-related counters and provides network

quality information about a service.
UMTS/LTE

3073
Nastar
Function Type
Description
Supported
Network
Analysis results
displayed through
geographic
observation
Geographically displays the cells to which

complaining subscribers have gained access and the
cells from which complaining subscribers have been
released.
GSM/
UMTS/LTE
Principles of Complaint Analysis Support

This section describes the data source and the function principles of the complaint analysis
support.
Data Source
The Nastar uses the CHR data for the complaint analysis support 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.
Function Principles of complaint analysis support based on CHR data only, see Function
Principles (Common). Function Principles of PS Core complaint analysis support based on
UGW internal xDR data, seeFunction Principles(PS only - Base on UGW ).Function
Principles of LTE(signaling plane) and PS Core(user plane) combined complaint analysis
support based on UGW internal xDR data, seeFunction Principles(RAN + PS - Base on
UGW ).
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
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
NOTE
scheme.
Issue 03 (2015-07-30)

3074
Nastar
Table 5-28 Description of complaint analysis support
Issue 03 (2015-07-30)
User
Operation
Proce
dure
Sour
ce
Desti
nation
Purpose
1.
Subscr
ibe to
basic
data
Issue a
basic
data
subscri
ption
comma
nd
Nasta
r
Serve
r
eSAU

subscription function (GSM complaint
analysis support or UMTS complaint analysis
eSAU.
Issue
an
MML
comma
nd
eSA
U
U2000
/
M2000

M2000.
Forwar
d the
MML
comma
nd
U200
0/
M20
00
BSC/
RNC
To forward the MML command to the NE

through the U2000/M2000, requesting the NE
to generate raw data.
GSM
/
UM
TS
netw
ork

3075
Nastar
User
Operation
PS
Core
netw
ork
LTE
netw
ork
Issue 03 (2015-07-30)
Proce
dure
Sour
ce
Desti
nation
Purpose
Upload
raw
data
BSC/
RNC
SAU
Issue a
basic
data
subscri
ption
comma
nd
Nasta
r
Serve
r
eSAU

subscription function (PS Core complaint
analysis support) on the Nastar client, the
Nastar issues a basic data subscription
Issue
an
MML
comma
nd
eSA
U
U2000
/
M2000

M2000.
Forwar
d the
MML
comma
nd
U200
0/
M20
00
SGSN/
MME
To forward the MML command to the NE,

Upload
raw
data
SGS
N/
MM
E/
GGS
N/
SAEGW
PS
SAU
Issue a
basic
data
subscri
ption
comma
nd
Nasta
r
Serve
r
eSAU

subscription function (LTE complaint analysis
eSAU.
Issue a
subscri
ption
comma
nd
eSA
U
U2000
/
M2000
To issue a subscription command to the

U2000/M2000.
NOTE
The generation and transmission of the GGSN/
SAE-GW CHR data is not triggered by the Nastar
subscription command. The GGSN/SAE-GW CHR
data will be uploaded to the PS SAU through
Huawei internal protocols in real time after the CHR
data switch is enabled.

3076
Nastar
User
Operation
Proce
dure
Sour
ce
Desti
nation
Purpose
Forwar
d the
subscri
ption
comma
nd
U200
0/
M20
00
eNode
B
To forward the subscription command to the

NE, requesting the NE to generate raw data.
Upload
raw
data
eNod
eB/
MM
E
Trace
Server/
LTE
SAU

uploading the raw data (eNodeB CHR)
l To upload the raw data (MME CHR) from
the MME to the LTE SAU directly.
NOTE
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.
Create
and
execut
e an
analys
is task
3.
View
analys
is
results
Deliver
a dataprepro
cessing
task
(direct)
Nasta
r
Serve
r
SAU/
LTE
SAU/
PS
SAU

SAU/LTE SAU/PS SAU through the eSAU,
requesting the SAU/LTE SAU/PS SAU to start
the data-preprocessing task.
Upload
prepro
cessed
data
(direct)
SAU/
LTE
SAU/
PS
SAU
eSAU
Upload
data
analysi
s
results
eSA
U
Nastar
Server
To aggregate the data reported by SAU/LTE

SAU/PS SAU, generate data analysis results,
and upload the data analysis results to the
Nastar server.
Displa
y
analysi
s
results
Nastar
Server
Function Principles(PS only - Base on UGW )

The data sources of PS Core complaint analysis support based on user plane data on UGW
include PS CHR data and UGW xDR data.Figure 5-49 shows the working principles for
Issue 03 (2015-07-30)

3077
Nastar
collecting, importing, and analyzing data on the Nastar. Table 5-29 describes details about the
working principles.
Table 5-29 Description of complaint analysis support(UGW)

User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Function
1.
Prepare
for
analysi
s.
Commis
sion the
PS SAU
and the
UGW
manuall
y.
User
PS
SAU
/
UG
W

Upload
data
collecte
d over
the
UGW.
UG
W
PS
SAU

the PS SAU.
Issue
basic
subscrip
tion
comma
nds.
Nast
ar
Serv
er
eSA
U

this function is enabled on the Nastar client, the Nastar
issues a subscription command to the eSAU.
2.
Subscri
be to
basic
data.
Issue 03 (2015-07-30)

3078
Nastar
User
Operat
ion
3.
Create
and
execute
analysi
s tasks.
4. View
analysi
s
results.
Proced
ure
Sou
rce
Dest
inati
on
Function
Issue
subscrip
tion
comma
nds.
eSA
U
U20
00/
M20
00
To issue subscription commands to the U2000/M2000

based on the subscription requirements.
Forward
subscrip
tion
comma
nds.
U20
00/
M20
00
MM
E/
SGS
N
To issue subscription commands to NEs through the

U2000/M2000 requesting the NEs to generate raw data.
Upload
raw
data.
MM
E/
SGS
N
PS
SAU
To upload the CHRs from the MME/SGSN to the PS

SAU.
Deliver
data preprocessi
ng tasks.
eSA
U
PS
SAU

request to the PS SAU, requesting the PS SAU to start
a data pre-processing task.
Upload
complai
nt data.
PS
SAU
eSA
U
To enable the PS SAU to pre-process the CHRs reported

by the MME/SGSN, and xDRs uploaded over the
UGW. After the data pre-processing task is complete,
the PS SAU uploads the pre-processed data to the
eSAU.
Upload
complai
nt data.
eSA
U
Nast
ar
Serv
er

Display
analysis
results.
Nast
ar
Serv
er

Function Principles(RAN + PS - Base on UGW )

The data sources of LTE FDD/TDD and PS Core combined complaint analysis support based
on user plane data on UGW include LTE CHR data and UGW xDR data.NFigure 5-50shows
the working principles for collecting, importing, and analyzing data on the Nastar.Table 5-30
describes details about the working principles.
Issue 03 (2015-07-30)

3079
Nastar
Table 5-30 Description of complaint combined analysis support

User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Function
1.
Prepare
for
analysi
s.
Commis
sion the
PS SAU
and the
UGW
manuall
y.
User
PS
SAU
/
UG
W

Upload
data
collecte
d over
the
UGW.
UG
W
PS
SAU

the PS SAU.
Issue a
basic
data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U

a user enables the basic data subscription function (LTE
complaint analysis support) on the Nastar client, the
Nastar issues a basic data subscription command to the
eSAU.
2.
Subscri
be to
basic
data.
Issue 03 (2015-07-30)

3080
Nastar
User
Operat
ion
3.
Create
and
execute
analysi
s tasks.
4. View
analysi
s
results.
Issue 03 (2015-07-30)
Proced
ure
Sou
rce
Dest
inati
on
Function
Issue a
subscrip
tion
comma
nd
eSA
U
U20
00/
M20
00

M2000.
Forward
the
subscrip
tion
comma
nd
U20
00/
M20
00
eNod
eB

Upload
raw data
eNo
deB/
MM
E
Trac
e
Serv
er/
LTE
SAU

uploading the raw data (eNodeB CHR) from the
eNodeB to the Trace Server.
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
Deliver
data preprocessi
ng tasks.
eSA
U
PS
SAU
/LTE
SAU

request to the PS SAU/LTE SAU, requesting the PS
SAU/LTE SAU to start a data pre-processing task.
Upload
complai
nt data.
PS
SAU
/
LTE
SAU
eSA
U
To enable the PS SAU/LTE SAU uploads the preprocessed data to the eSAU.
Upload
complai
nt data.
eSA
U
Nast
ar
Serv
er

Display
analysis
results.
Nast
ar
Serv
er


3081
Nastar
Technical Specifications for Complaint Analysis Support

of analysis time.
NOTE
Item
Execution type
One-time task

analysis task
Maximum management capacity of the Nastar (A maximum

of six NEs are supported in USN+UGW joint analysis.)
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.
task
l 2,000 complaining subscribers (for all networks when

IMSIs are used for analysis.)
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
analysis tasks
500 (for all RATs)

one analysis task
Last 7 days

task
GSM/UMTS/LTE/PS Core: 210 minutes

l GSM: 7 days
l UMTS: 7 days
l LTE: 7 days
l PS Core: 30 days

l GSM: 7 days
l UMTS: 7 days
l LTE: 7 days
l PS Core: 30 days
Issue 03 (2015-07-30)

3082
Nastar
5.11.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

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 5-31.
Issue 03 (2015-07-30)

3083
Nastar
Table 5-31 Required license and rights of complaint analysis support

Funct
ion
Required license

Management > User)
Data
subscr
iption
manag
ement
TDD/PS Core basic function
license

Authentication
NOTE

NE Object Authentication > *** NE
Operation Rights. *** refers the NEs to
be subscribed.
Subject Management > *** Complaint
Analysis Support Operation Rights.
*** refers the RAT.

permission.
TDD/PS Core complaint
analysis support license
NOTE
l You need to obtain the licenses for
basic functions and complaint
analysis support related only to the
desired RATs instead of all RATs.
l The license for the basic functions
related to an RAT is the basis for
all functions related to this RAT,
which means the functions related
to an RAT depends on the
availability of the license for the
basic functions related to this RAT.
Issue 03 (2015-07-30)

3084
Nastar
Funct
ion
Required license

Management > User)
GSM
compl
aint
analys
is
suppor
t
l GSM basic function license

Operation Rights >
Operation > Nastar
GSM Complaint Analysis
Support Operation
Rights

support license

be analyzed
analyzed.
UMT
S
compl
aint
analys
is
suppor
t
Issue 03 (2015-07-30)
l UMTS basic function license

l UMTS complaint analysis
support license

Operation Rights >
Operation > Nastar
UMTS Complaint
Analysis Support
Operation Rights
be analyzed
analyzed.

NOTICE
If the
analyzed
IMSI or
MSISDN
of
complaini
ng user is
the same as
the VIP
user in the
VIP group
manageme
nt
function,
and you
has not the
operation
rights to
operate the
VIP user,
you are not
allowed to
create the
complaint
analysis
support
task about
the IMSI
or
MSISDN.
3085
Nastar
Funct
ion
Required license

Management > User)
LTE
TDD
compl
aint
analys
is
suppor
t
l LTE TDD basic function license

Operation Rights >
Operation > Nastar
LTE TDD Complaint
Analysis Support
Operation Rights
NOTE

be analyzed
analyzed.

permission.
l LTE TDD complaint analysis

support license
l (Optional) LTE TDD CSFB
CSFB counters.
l (Optional) LTE TDD VoLTE
VoLTE counters.
Issue 03 (2015-07-30)

3086
Nastar
Funct
ion
Required license

Management > User)
LTE
FDD
compl
aint
analys
is
suppor
t
l LTE FDD basic function license

Operation Rights >
Operation > Nastar
LTE FDD Complaint
Analysis Support
Operation Rights
NOTE

be analyzed
analyzed.

permission.

support license
l (Optional) LTE FDD CSFB
CSFB counters.
l (Optional) LTE FDD VoLTE
VoLTE counters.
Issue 03 (2015-07-30)

3087
Nastar
Funct
ion
Required license

Management > User)
PS
Core
compl
aint
analys
is
suppor
t
l PS Core basic function license

Operation Rights >
Operation > Nastar
PS Core Complaint
Analysis Support
Operation Rights
l PS Core complaint analysis

support license
l (Optional) SGSN/MME VoLTE
signaling analysis license
l (Optional) GGSN/SAE-GW
VoLTE signaling analysis
license
l (Optional) SGSN/MME CSFB
CSFB counters.
l (Optional) Data Access-Gn
License and GGSN/SAE-GW
Data Service User Plane
Complaint Analysis Support
License, for controlling the
availability of the analysis
function based on PS Core user
plane data obtained from the
UGW.
Issue 03 (2015-07-30)

be analyzed
analyzed.

3088
Nastar
Funct
ion
Required license

Management > User)
l GS
M/
U
M
TS
co
mb
ine
d
co
mp
lai
nt
ana
lys
is
sup
por
t
TDD/PS Core basic analysis
support license

Have both involved
licenses of Complaint
Analysis Support
Operation Rights of
combined analysis.
be analyzed is the same as
the rights of complaint
analysis support of each
network.
l LT
E
FD
D/
LT
E
TD
D
co
mb
ine
d
co
mp
lai
nt
ana
lys
is
sup
por
t
l RA
N
sid
e
(G
S
Issue 03 (2015-07-30)

3089
Nastar
Funct
ion
M/
U
M
TS
/
LT
E
FD
D/
LT
E
TD
D)
an
d
PS
Co
re
co
mb
ine
d
co
mp
lai
nt
ana
lys
is
sup
por
t
Issue 03 (2015-07-30)
Required license

Management > User)
NOTE
permission.

support license, and UMTS
license
support license, and LTE TDD
license
l Complaint analysis support
license of analyzed network on
the RAN side, and PS Core
license

3090
Nastar
Funct
ion
Required license

Management > User)
Comm
on
To control the User Identity right, otherwise,

you can not view the integrated IMSI
information.
Function operation rights: Operation
Rights > Select > Nastar Application >
Operation > Nastar Security Information
Management > User Identity
Operation Rights > Select > Operation >
Nastar System Task Management >
Viewing Rights of Data Maintenance and
Management: to control the viewing rights
of the Complaint Analysis page during task
creation.

task successfully.
Issue 03 (2015-07-30)

3091
Nastar
Table 5-32 Required basic data of complaint analysis support

Data
Type
Function
Operation
Configur
ation
Data
(Mandato
ry)

the NE corresponding to
a complaint location
allows users to correctly
obtain the data of
complaining subscribers
from the network and
analyze the cell
information in MRs and
following cells: cells to
gained access, cells
handed over.

and imports the configuration data after the OSS
and NE information is configured. You can also
Data Maintenance Management to check
whether the configuration data is available in the
Nastar database. For detailed information about
collecting, importing, and checking, see 3.4.2
Checking the Integrity of Configuration Data.
NOTE
If you only perform the PS
Core complaint analysis
support, you do not need
Issue 03 (2015-07-30)

imported, you are advised to check the validity of
the configuration data. The purpose is to avoid

3092
Nastar
Data
Type
Function
Operation
Complain
ing
Subscribe
r
Informati
on
(Mandato
ry)
l Time
The Nastar only
analyzes complaints
that occurred in the
latest seven days.
Enter the complaining subscriber information when

creating complaint analysis support.
l Place
The NE information
that the problem
occurs, including one
or multiple NEs. The
Nastar can analyze
complaints that occur
on the whole network
(The network can
involve multiple
OSSs). It does not
require the precise
information about the
complaining place.
However, it is
recommended that
you locate the
complaining place to
the base station
controller level or cell
level to ensure
performance of the
complaint analysis
support function.
l IMSI, STMSI,
MSISDN, or peer
MSISDN
IMSI: Supported
by every network.
NOTE
If telecom operators have high requirements for
subscriber information security and the anonymization
policy is enabled on the network where the Nastar is
deployed, all subscriber information such as IMSI,
MSISDN, and IMEI contained in the analysis data will be
encrypted. To protect the security-sensitive subscriber
information, 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 Software Center > Tool > Mini-tool
Software > Core Network Product Line > WirelessOSS > iManager M2000-II > HMACUtil to obtain the
anonymization switch or the encryption key is changed.
If the subscriber identity anonymization switch or the
encryption key is changed, see 3.12.3 Troubleshooting
Problems Caused by Change of the Subscriber
Identity Anonymization Switch or the Encryption
Key.
If the number of complaining subscribers to be

analyzed is large, you can save the IMSI,
STMSI,MSISDN or peer MSISDN information in
the files in .xls/.xlsx/.csv format.
NOTE
The IMSI or MSISDN information stores a maximum of
2,000 records. Each IMSI must contain 15 digits. The peer
MSISDN information stores a maximum of 200 records.
STMSI:
Supported only
when the LTE is
not interconnected
to the EPC.
MSISDN: Only
supported by the
PS Core network.
Peer MSISDN:
Only supported by
the GSM network
Issue 03 (2015-07-30)

3093
Nastar
Data
Type
Function
Operation
when choosing the

CS service.
You can obtain
either the above
information of a
complaining
subscriber for
analysis when
supporting multi
information.
Engineeri
ng
Paramete
rs
(Optional
)
The engineering
of the analysis result. You
engineering parameters if
the geographic display of
the analysis result is not
required.

parameters have been imported. If the parameters
are unavailable, you must import the engineering
Map File
(Optional
)

result geographically.
You do not need to
prepare the map file if you
do not want to view the
analysis result on the
map.

Internet, you can view analysis results on the
Google Earth. For details, see 3.4.4 Preparing the
Map File (Optional).

Before analyzing, check that the used NE versions and U2000/M2000 versions are consistent
with those described in Table 5-33.
Issue 03 (2015-07-30)

3094
Nastar

Net
wor
k
Description
GSM

(or later).
(or later).
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
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.
UM
TS

(or later).
Issue 03 (2015-07-30)

3095
Nastar
Net
wor
k
Description
LTE
NOTE
(RH2288).
Issue 03 (2015-07-30)

3096
Nastar
Net
wor
k
Description
PS
Core
NE version:
V900R013C00
5.11.3 Process of Complaint Analysis Support

This section describes the process of complaint analysis support and the steps of each procedure.
l
Prerequisites
Procedure
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 5.11.2 Preparations for Complaint
Analysis Support.
Procedure
Figure 5-51 shows the process of complaint analysis support. For details, see Table 5-34.
Issue 03 (2015-07-30)

3097
Nastar
Figure 5-51 Flowchart for complaint analysis support
Table 5-34 Description of complaint analysis support procedures

No.
Proced
ure
Description
Reference for
Detailed
Operations
(1)
LTE
Periodic
MR
Period
Setting
NOTE
For details about

parameters, see LTE
Periodic MR Period
Setting Parameters
l For LTE analysis themes, you must set this

parameter before basic subscription. Otherwise, the
Nastar uses the current value of this parameter to
perform basic subscription.
l For an LTE network, this function is available only
to an account in the Administrators group or users
with data subscription management permission.

Procedure:
window, set Periodic MR Period, Number
of Sampled Users and Number of Times
MRs Are Reported.
2. Click Configure.
Issue 03 (2015-07-30)

3098
Nastar
No.
Proced
ure
Description
Reference for
Detailed
Operations
Subscrib
e to
analysis
data
(basic)
NOTE
administrator who is authorized to subscribe to basic
data to turn on the data switch.
3.5 Subscribing to
Analysis Data

Procedure:
window, click *** tab.
*** indicates the network.
configured.
click Configure.
Settings dialog box, set complaint analysis
support data to ON.
l In the GSM network, the switch names are
(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
(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 03 (2015-07-30)

3099
Nastar
No.
Proced
ure
Description
Reference 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 5.11.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 03 (2015-07-30)

3100
Nastar
No.
Proced
ure
Description
Reference for
Detailed
Operations
(2)
Create a
complai
nt
analysis
support
task

User Assurance > Complaint Analysis
Support in the navigation tree of the Analysis
Task Management window.
l For details, see

3.7 Creating an
Analysis Task.
Procedure:
1. Double-click the Complaint Analysis
Support node.
Next.
l For details about

the parameters,
see Analysis
Task
Parameters.
3. On the Set Analysis Type tab page, set a net

type and a data type.
4. On the Select NE(s) tab page, click Select to
select the NEs located in an area where
subscribers complained about.
5. On the Select Complaining User tab page,
click Add or Import to set the IMSI
information (user alias, IMSI, and remark),
MSISDN, or peer MSISDN of the
complaining subscriber.
l IMSI: Supported by every network.
l STMSI: Supported only when the LTE is
not interconnected to the EPC.
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
period.
NOTE
8. Click Finish.
Issue 03 (2015-07-30)

3101
Nastar
No.
Proced
ure
Description
Reference for
Detailed
Operations
(3)
View
complai
nt
analysis
support
results

record of the task.
l For details, see

3.8 Querying
Analysis
Results.
Procedure:
2. In the displayed Complaint Analysis
Support window, view the complaint analysis
support results
(4)
Export
complai
nt
analysis
support
reports

the upper left part of each analysis results
window.
Procedure:
3. Click Save.

interface
description, see
5.11.4 Reference
for Complaint
Analysis
Support
Interface.
l For details, see
3.10 Exporting
Analysis
Reports.
interface
description, see
5.11.4 Reference
for Complaint
Analysis
Support
Interface.
Issue 03 (2015-07-30)
Parameter
Description
Periodic MR
Period

3102
Nastar
Parameter
Description
Number of
Sampled Users

Nastar.
NOTE
Number of
Times MRs
Are Reported


Basic Subscription
Issue 03 (2015-07-30)

3103
Nastar
RA
T
Parameter
Description
GS
M
Complaint
Analysis
Support
Data (CHRCS)

You can click

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.
existing settings.
documentation. You can set this parameter to a value ranging from
0 to 6 or retain the existing settings.
NOTE
Issue 03 (2015-07-30)

3104
Nastar
RA
T
Parameter
Description
Complaint
Analysis
Support
Data (CHRPS)

You can click
documentation.
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 UL PDU Receiving Delay Threshold: For details, see the
SET GPSCHRCTRL command in the related NE product
documentation.
Complaint
Analysis
Support
Data (MRCS)
Switch for enabling or disabling the reporting of CS MR data. You can

You can click
l Collection Switch: For details, see the SET GMRCTRL command

l Original Sampling Rate: For details, see the SET GMRCTRL
l Preprocessed Sampling Rate: For details, see the SET
Issue 03 (2015-07-30)

3105
Nastar
RA
T
Parameter
Description
UM
TS
Complaint
Analysis
Support
Data (CHR)
Switch for enabling or disabling the reporting of CHR data. You can
You can click

l Error: specifies that all CHR data containing normal and abnormal
service procedures is reported. This parameter is unavailable.
existing settings.
existing settings.
Issue 03 (2015-07-30)

3106
Nastar
RA
T
Parameter
Description
LTE
FD
D/
LTE
TD
D
Complaint
Analysis
Support
Data (CHR)

You can click
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_MR_MDT, periodic intra-frequency
MDT measurement
measurement
measurement
measurement
measurement
measurement
CSFB PREP, CSFB
Issue 03 (2015-07-30)

3107
Nastar
RA
T
Parameter
Description
Object at the lower left corner to select the idle object to be
measured. The range of selected objects is displayed in the Idle
State Measurement Object Range column on the Periodic Event
Trace Event Block: Specify the type of event to be traced. The
value of this parameter can be
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.
600(s), 1200(s), 2400(s), 3600(s), 5400(s), or 7200(s). The
Idle State Measurement Object Range: Specify the range of
idle objects to be measured. A maximum of 32 cells or eight
TACs can be selected.
NOTE
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.
Issue 03 (2015-07-30)

3108
Nastar
RA
T
Parameter
Description
PS
Core
Complaint
Analysis
Support
Data
(SGSN/
MMECHR)


Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

Parameter
Description
Set
Analysi
s Type
Analysis
Scene

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.
Issue 03 (2015-07-30)

3109
Nastar
Parameter
Description
Access
Network Type
Set the RAT for an NE. The system supports the following RATs:
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, GSM/LTE, UMTS/LTE,
GSM/UMTS/LTE.
Data Type 1

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.
NOTE
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 03 (2015-07-30)

3110
Nastar
Parameter
Description
PS Core SDR
Type
The following options are available if you select PS Core when

creating a complaint analysis support task.
l Signaling-Plane CHR Type:
Abnormal process: Only the call records about abnormal
abnormal services are displayed. This option is selected by
default.
Normal process: Only the call records about normal
normal services are displayed.
Normal process: Only the traffic call records are reported
and only the traffic analysis results are displayed.
l Data Type: Data user plane. Data Access-Gn license is
needed for use this function.
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
NE(s)
Issue 03 (2015-07-30)
RAN NE
Click Select to select an NE. The lowest level is the base station
controller level.

3111
Nastar
Parameter
Description
Select
Compla
ining
User
Add or import the user alias, the IMSIs, and remarks of

complaining users.
IMSI
NOTE
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.

l Only numbers allowed.
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.
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 complaining subscriber is the same as the VIP
create the complaint analysis support task about the IMSI.
Issue 03 (2015-07-30)

3112
Nastar
Parameter
Description
STMSI
NOTE
STMSI is
displayed only
when the EPC
is not
interconnecte
d on LTE
network.
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.

l Only numbers are allowed.
STMSI value range:
Value range: a 10-digit alphanumeric string composed of 0-9, and
A-F.
MSISDN
Add or export MSISDNs of complaining subscribers.

l It is only supported by the PS Core network.
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 complaining subscriber is the same as the VIP
create the complaint analysis support task about the MSISDN.
Issue 03 (2015-07-30)

3113
Nastar
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.
through 9).
the Nastar is deployed, the Nastar does not support analyzing
using the MSISDN.
NOTICE
If the input peer MSISDN of complaining subscriber is the same as the
VIP subscriber in the VIP group management function, and you has not
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
Thresh
old
Network
Indicates the RAT of an NE.
Domain
Indicates the domain of an NE. Domains include signaling planeCS, signaling plane-PS, signaling plane-integration.
Service/Flow
Type
l When only the RAN data is analyzed, this row displays the
service type of the KPIs, such as NET, Call, and so on.
l When only the PS Core data is analyzed, this row displays 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, this
row displays the service type or flow type of the KPIs.
Indicator
Name
Indicates the name of a KPI.
Operator
Indicates the relationship between the KPI value and KPI

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 value. This
parameter can be empty. That is, no threshold value is provided.
Issue 03 (2015-07-30)

3114
Nastar

Parameter
Description
Duration
5.11.4 Reference for Complaint Analysis Support Interface

This section describes the interface for complaint analysis support. Before performing relevant
Interface Description: UMTS Complaint Analysis Support

This section describes the interface for UMTS complaint analysis support. Before performing
Opening the Window

You can enter UMTS complaint analysis support interface in two modes:
l
Main Window
NOTE
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.
Issue 03 (2015-07-30)

3115
Nastar
Issue 03 (2015-07-30)

3116
Nastar
No.
Parame Description
ter
Button
area

l
: displays the complaint analysis support results geographically.

For details, see Description of Mobility Analysis Tab Page.

type.file format.
format.
: exports data reports.

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.
reports.
provides the abnormal cause statistics function of the service. For

details, see Common Statistics Interface.
NOTE
OK and export data.
page.
Issue 03 (2015-07-30)

3117
Nastar
No.
Parame Description
ter
w tree of
NOTE
the call
If users select only a service type node (such as NET, CS domain, and PS domain),
the Nastar filters only the abnormal or normal CHRs of the selected service type.
report
cause
l Middle part: Call records of multiple subscribers are displayed by cause
type
overvie
w of
complai
nt
subscrib
ers
NOTE
Non-exception node.
Issue 03 (2015-07-30)

3118
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers
l
l

unknown.
The Nastar supports combining inter-RNC call history records. If an interRNC handover occurs in one call process, the Nastar combines several
the user.
Click the
NOTE
page.

g
area
subscribers.
For details, see Description of the Measurement Information Before Call
Release Tab Page, Description of Service Analysis Tab Page, and
NOTE
page.
Issue 03 (2015-07-30)

3119
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers

including user information, call access information, call release information,
and statistical information.
Support Parameters (UMTS).

process.
Issue 03 (2015-07-30)

3120
Nastar
No.
Parameter
Description
(1)
Signaling
information
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
flowchart

NOTE

Description of the Measurement Information Before Call Release Tab Page

Before call release, measurement information in the UMTS complaint analysis support window
values.
NOTE
reports.
Issue 03 (2015-07-30)

3121
Nastar

No.
Parameter
Description
(1)
Detailed MR
information
table

information.
(2)

chart of
charts.
measurement
to right:
l Title
l Legend
counters.
Issue 03 (2015-07-30)

3122
Nastar

Counter
Description
Ec/No

signal intensity according to the
received cells of the UE.
RSCP

signal level according to the received
cells of the UE.
RSSI

RSSI according to the received intercells of the UE.
RSRP

RSRP according to the received LTE
cells of the UE.
RSRQ

RSRQ according to the received
inter-cells of the UE.
UE Tx Power

transmit power of the UE.

Figure 5-55 Description of mobility analysis tab page
Description of Service Analysis Tab Page

The service analysis includes RAB analysis.
l
Issue 03 (2015-07-30)
Figure 5-56 shows the items about the RAB service through the RAB analysis.
3123
Nastar
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.
Figure 5-56 Description of service analysis tab page (RAB)

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.
in the button area. In the displayed Common Statistics dialog box, select an object
Click
from the navigation tree and click Confirm. Details about the abnormal causes are displayed in
the right pane.
Map Interface
Click
Figure 5-57.
Issue 03 (2015-07-30)

3124
Nastar
No.
Feature
Description
(1)
Button area
Results.
(2)
Navigation
tree in the
map window
NOTE

support theme.
release cell KPI.
(3)
Geographic
observation
area
(4)
Grid detail
area
(5)
Legend area

click the
(6)
Information
area

Interface Description: GSM Complaint Analysis Support

This section describes the interface for GSM complaint analysis support. Before performing
Opening the Window

You can enter GSM complaint analysis support interface in two modes:
Issue 03 (2015-07-30)

3125
Nastar
Main Window
Issue 03 (2015-07-30)

3126
Nastar
No.
Parame Description
ter
Button
area

l

For details, see Map Interface.

type.file format.
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, rightclick 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.
reports.
NOTE
OK and export data.
page.
Issue 03 (2015-07-30)

3127
Nastar
No.
Parame Description
ter
the call
report
cause
type
overvie
w of
complai
nt
subscrib
ers
NOTE
Non-exception node.
Issue 03 (2015-07-30)

3128
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers
l
l

unknown.
The Nastar supports combining inter-BSC call history records. If an interBSC handover occurs in one call process, the Nastar combines several
the user.
Click the
NOTE
page.

g
procedu For details, see Description of Signaling Procedure Before Call Release
re area Tab Page.
area
subscribers.
For details, see Description of Measurement Information Before Call
Release Tab Page, Description of Mobility Analysis Tab Page.
NOTE
page.
Issue 03 (2015-07-30)

3129
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers

Support Parameters (GSM).
Description of Signaling Procedure Before Call Release Tab Page

process.
Issue 03 (2015-07-30)

3130
Nastar
No.
Parameter
Description
(1)
Signaling
information
table
NOTE
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.
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
flowchart

NOTE

Description of Measurement Information Before Call Release Tab Page

Before call release, measurement information in the GSM complaint analysis support window
values.
Issue 03 (2015-07-30)

3131
Nastar
NOTE
reports.

No.
Parameter
Description
(1)
Detailed MR
information
table

information.
Issue 03 (2015-07-30)

3132
Nastar
No.
Parameter
Description
(2)

chart of
charts.
measurement
to right:
l Title
l Legend
counters.

Counter
Description
TA

caused by poor coverage.
Displayed as a bar chart. The value

ranges from 0 to 63.
DLRxLevel
DLRxQuality
/Level
Displayed as a broken line graph. The

value ranges from -47 to -110.
caused by uplink or downlink
interference.
ULRxQuality
/Level
Issue 03 (2015-07-30)

-110.
-110
MS/BTS
Power

caused by unbalanced uplink and
downlink by analyzing this KPI with
DLRxQuality/Level and
ULRxQuality/Level.
BTS Power: displayed as a bar chart.

The value ranges from 0 to 15. MS
Power: displayed as a broken line
VQI
Displays voice quality changes in the

process, help evaluate the quality
accurately.
UL VQI: displayed as a bar chart.

The value ranges from 0 to 50. DL
VQI: displayed as a broken line

3133
Nastar

For details about parameters, see 5.11.6 Reference for Complaint Analysis Support
Parameters (GSM).
Map Interface
Click
Figure 5-62.
Issue 03 (2015-07-30)
No.
Feature
Description
(1)
Button area
Results.

3134
Nastar
No.
Feature
Description
(2)
Navigation
tree in the
map window
NOTE

support theme.
release cell KPI.
(3)
Geographic
observation
area
(4)
Grid detail
area
(5)
Legend area

click the
(6)
Information
area

Interface Description: LTE Complaint Analysis Support

This section describes the interface for LTE complaint analysis support. Before performing
related 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:
l
Issue 03 (2015-07-30)
3135
Nastar
of the task in the Task Result area. Right-click an analysis result of a task and choose View
Main Window
Issue 03 (2015-07-30)

3136
Nastar
No.
Parame Description
ter
Button
area

l

For details, see Description of the E-RAB Analysis Tab Page.

type.file format.
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.
reports.
NOTE
OK and export data.
page.
Issue 03 (2015-07-30)

3137
Nastar
No.
Parame Description
ter
the call
report
cause
type
overvie
w of
complai
nt
subscrib
ers
NOTE
Non-exception node.
Issue 03 (2015-07-30)

3138
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers
l
l

unknown.
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
NOTE
page.

g
analysis subscribers. The Nastar analyzes the mobility and service of all filtered
area
subscribers.
For details, see Map Interface, Description of the Measurement
Information Page and Description of the Mobility Analysis Tab Page.
NOTE
page.
Issue 03 (2015-07-30)

3139
Nastar
No.
Parame Description
ter
Call
report
overvie
w table
of
complai
nt
subscrib
ers

Support Parameters (LTE).

process.
Issue 03 (2015-07-30)

3140
Nastar
No.
Parameter
Description
(1)
Signaling
information
table
NOTE
When the signaling code stream is too long, copy it to a notepad and view the
complete information. Then, delete the notepad in time.
(2)
Signaling
flowchart

NOTE

Description of the Measurement Information Page

Before call release, measurement information in the LTE complaint analysis support window
values, as shown in Figure 5-65.
Figure 5-65 Measurement information tab page
Issue 03 (2015-07-30)

3141
Nastar
No.
Parameter
Description
(1)
Detailed MR
information
table
Lists detailed MR information. The information includes time,

measurement object type, and detailed counter information.
(2)

chart of
charts.
measurement
to right:
l Title
l Legend
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 5-66.
Figure 5-66 E-RAB analysis tab page
Right-click one E-RAB, choose Detail E-RAB Information from the shortcut menu, view
the detailed information of the selected service bearer.
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.
Description of the Mobility Analysis Tab Page

Issue 03 (2015-07-30)

3142
Nastar
Map Interface
Click
Figure 5-68.
Issue 03 (2015-07-30)
No.
Feature
Description
(1)
Button area
Results.

3143
Nastar
No.
Feature
Description
(2)
Navigation
tree in the
map window
NOTE

support theme.
release cell KPI.
(3)
Geographic
observation
area
(4)
Grid detail
area
(5)
Legend area

click the
(6)
Information
area

Interface Description: PS Core Complaint Analysis Support

This section describes the interface that displays PS core complaint analysis support results.
interface.
l
Main Interface (User plane)
Issue 03 (2015-07-30)

3144
Nastar
Navigation Path
Use either of the following methods to open the interface that displays PS core complaint analysis
support results:
l
in the Task Result area and choose View Analysis Result from the shortcut menu.

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 5-69.
Figure 5-69 Interface for PS core complaint analysis support results
Issue 03 (2015-07-30)

3145
Nastar
No.
Item
Description
Button
area

l


detailed information (such as CHR base information, user information,
procedure information).
provides the traffic statistics function. For details, see Traffic

Statistics on the Interface.
NOTE
OK and export data.
page.
Issue 03 (2015-07-30)

3146
Nastar
No.
Item
Description
Navigati
on tree
of the
CHR
cause
type
summar
y of
complai
ning
subscrib
ers
l Upper part: Displays the service types. You can select the service types.
l Middle part (upper): Displays the procedure types. You can select the
procedure types. The content in brackets after the SGSN and GGSN
indicates the RAT.
l Middle part (lower): Based on the selected service type and the procedure,
the call records of multiple subscribers are displayed by cause type in the
navigation tree mode.
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 follows: Cause type(N). (N) after each node
indicates the number of call records under the node.
NOTE
Non-exception node.
Issue 03 (2015-07-30)

3147
Nastar
No.
Item
Description
Summar View the overview information of all filtered records, such as time, cell,
y table procedure, and exception cause.
of
in the Combined column: indicates that the call record in the row is
complai l
a combined one.
ning
The Nastar supports combination of records on the same NE during a
subscrib
call and displays the combined record in the summary table.
er
records
Double-click a specified combined record to open the list of raw
records.
NOTE
l
l
: indicates that the call record in the row is abnormal.

in the USN+UGW Associated column: indicates that the call record
in the row is a associated one.
The Nastar supports association of USN, UGW, and Gx/Gy/Radius
records during a call and displays the associated record in the summary
table.
Double-click a specified associated record to open the list of raw
records, in which raw records closely related to the associated record
are highlighted.
In the list of raw records, double-click a record. The raw records
closely related to the selected record in the other two RATs are
highlighted.
NOTE
Click the
NOTE
page.
l For some columns (such as User ID: Alias), the system only centralized display the
Issue 03 (2015-07-30)
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

3148
Nastar
No.
Item
Description
Details
table of
complai
ning
subscrib
er
records
Displays the subscriber details corresponding to the records selected in area

2.
For details about the parameters, see Reference for Complaint Analysis
Support Parameters (PS Core) - Signaling Plane.
The table is hidden by default when you initially open the window.
NOTE
page.
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
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
5-70.
Issue 03 (2015-07-30)

3149
Nastar
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.
Main Window (User plane)

The complaint analysis support results can be displayed in tables, such as overview table, SDR
information, subscriber information, and procedure information, as shown in Figure 5-69.
Figure 5-71 PS Core Complaint analysis support interface
Issue 03 (2015-07-30)

3150
Nastar
No.
Parame Description
ter
Button
area

l


detailed information (such as base information, user information, KQI
information).
provides the abnormal cause statistics function of the service. This

button is available only for user plane call records. For details, see
l SDR Model: including signaling plane and user plane. This option is
available only when the Nastar analyzes user plane and signaling plane
data at the same time.
NOTE
OK and export data.
page.
Issue 03 (2015-07-30)

3151
Nastar
No.
Parame Description
ter
Overvie l Upper part: Displays the service types for GSM/UMTS/LTE. You can
w tree of
select the service types.
the xDR
NOTE
cause
If users select only a service type node, the Nastar filters only the abnormal or
normal xDRs of the selected service type.
type
overvie l Middle part: Call records of multiple subscribers are displayed by cause
w of
complai
nt
subscrib
ers
In Cause type-XX mode, all filtered call records are classified by
cause type and the call records of each cause type are then classified
by XX.
In XX-Cause type mode, all filtered call records are classified by
XX and the call records of each XX are then classified by cause type.
NOTE
page.
Issue 03 (2015-07-30)

3152
Nastar
No.
Parame Description
ter
xDR
overvie
w table
of
complai
nt
subscrib
ers
information includes the information, such as access time, access cell, release
l
l
l
: indicates that the call record in the row can be associated with user
or signaling plane call records. Click this icon to open an associated call
record.
unknown.
Click the
NOTE
Theme Displays detailed KQI information about all filtered subscribers.

analysis
area
xDR
overvie
w table
of
complai
nt
subscrib
ers
Displays detailed information about the selected subscriber in area 2.

For details about parameters, see Reference for Complaint Analysis

The common statistics function allows the Nastar to collect statistics on the abnormal cause,
abnormal sub-cause, demarcation result, and abnormal counts generated for a specified user or
service.
1.
Click
2.
Select an object from the navigation tree and click Confirm. Details about the abnormal
causes are displayed in the right pane, as shown in Figure 5-72.
Issue 03 (2015-07-30)

3153
Nastar
Interface Description: Combined Complaint Analysis Support

This section describes the interface that displays combined complaint analysis support results.
interface.
Combined complaint analysis support based on signaling plane data
The Nastar allows you to perform combined complaint analysis support based on the signaling
plane data collected from different network types on the RAN side as well as based on signaling
plane data collected on the RAN and PS core sides. Therefore, the Nastar supports combined
complaint analysis support based on signaling plane data of networks in the following
combinations:
l
Only RAN side

LTE-FDD+LTE TDD
GSM+UMTS
GSM+LTE-FDD/TDD
GSM+LTE-TDD
UMTS+LTE-FDD/TDD
GSM+UMTS+LTE-FDD/TDD
Issue 03 (2015-07-30)

3154
Nastar
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
Combined complaint analysis support based on signaling and user plane data
The Nastar allows you to perform combined complaint analysis support based on signaling plane
data collected from LTE FDD and TDD networks and user plane data collected on the PS core
side using the UGW. Therefore, the Nastar supports combined complaint analysis support based
on signaling plane and user plane data in the following combinations:
l
LTE FDD(signaling plane)+PS Core(user plane)
LTE TDD(signaling plane)+PS Core(user plane)
Navigation Path
Use either of the following methods to open the interface that displays combined complaint
analysis support results:
l
in the Task Result area. Right-click a result record of the task and choose View Analysis
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, as shown in Figure 5-73:
Issue 03 (2015-07-30)

3155
Nastar
Figure 5-73 Combined Complaint Analysis Support signaling plane data (Using LTE and
PS Core as an example)
The service types displayed in the navigation tree (area 1) are combinations of the service
The cause types displayed in the navigation tree (area 2) are combinations of the cause
The description of the exception causes provides the mapping between service types and
cause types. For details, see Appendix: Exception Cause Classification (Combined
Analysis).
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 5.11.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.
l For details about the interface for the VoLTE combined complaint analysis support based on signaling
plane data collected from LTE FDD and TDD networks and user plane data collected on the PS core
side, see the description for the user plane data analysis interface in Interface Description: PS Core
Complaint Analysis Support. For details about parameters, see Reference for Complaint Analysis
Issue 03 (2015-07-30)

3156
Nastar

(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
eter
Range
Uni
t
Description
Supported
Solution
Version
Serial
Numbe
r
[1,2^31-1)
N/A
Serial number of a CHR in the Overview

Table. Serial number is a keyword of a
call record. It is an internal identification
in the Nastar and can uniquely identify
a call record.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3157
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Combi
ned
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
The Nastar supports the combination of

inter-RNC CHRs. If a yellow icon is
displayed in this column, the CHR is
combined.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Status
N/A
Blank

If a red exclamation mark is 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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3158
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Abnor
mal
Cause
For details,
see
"Appendix:
Exception
Cause
Classificatio
n/
Enumeration
Values of
Failure Cause
(UMTS)".
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
Remark: For the access counters such as

TP, Ec/No, RSCP, if the active set
contains multiple cells during access,
only the counters for the first cell in this
The Nastar collects statistics on the
number of each of the following types
of exceptions occuring during calls:
uplink one-way audio, downlink oneway audio, and garble noise.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Networ
k
UMTS
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3159
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Access
Type
Static reloc
in
N/A

Setup Type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
HHO reloc
in
Cell update
reloc in
Inter RAT
handover in
RRC setup
without DRD
RRC setup
with DRD
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3160
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Access
Cause
Originating
Conversation
al Call
N/A

Setup Cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Originating
Streaming
Call
l SRAN8.1/
GBSS15.1/
RAN 15.1
Originating
Interactive
Call
l SRAN9.0/
GBSS16.0/
RAN16.0
Originating
Background
Call
l SRAN10.0/
GBSS17.0/
RAN17.0
Originating
Subscribed
traffic Call
l SRAN10.1/
GBSS17.1/
RAN17.1
Terminating
Conversation
al Call
l SRAN11.0/
GBSS18.0/
RAN18.0
Terminating
Streaming
Call
Terminating
Interactive
Call
Terminating
Background
Call
Emergency
Call
Inter-RAT
cell reselection
Inter-RAT
cell change
order
Registration
Detach
Originating
High Priority
Signaling
Issue 03 (2015-07-30)

3161
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
N/A

Request Time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Originating
Low Priority
Signaling
Call reestablishmen
t
Terminating
High Priority
Signaling
Terminating
Low Priority
Signaling
Terminating
- cause
unknown
MBMS
reception
MBMS ptp
RB request
Start
Time
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3162
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Access
Cell
1 to 64
characters
N/A
Same as Access Information -> Cell on

RRC Setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
End
Time
N/A
N/A

Release Time
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3163
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Release
Cell
1 to 64
characters
N/A

Release Cell
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User
ID:Alia
s
N/A
N/A
User ID, which is created by the system

Alias, which is created by the user when
creating the task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3164
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
IMSI
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

information.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMEITAC
00000000-99
999999
N/A
First eight digits in the IMEI of a UE.

IMEI is international mobile equipment
identity for short and TAC is type
approval code for short.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3165
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Termin
al
Model
N/A
N/A
Model of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The UE model can be queried using

terminal type management based on the
IMEI-TAC of the UE.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Duratio
n
[0,+)
Seco
nd
Duration of a call, including service

duration and signaling duration.
Call duration = End time - Start time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3166
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
CS
Reques
ted
Service
Type
AMR
N/A
Statistics on the types of CS service

requested by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
VP
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
CS
Service
Duratio
n
[0,+)
Seco
nd
Statistics on the duration of CS services

used by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3167
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
PS
Reques
ted
Service
Type
PS R99
N/A
Statistics on the types of PS service

requested by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
HSDPA
HSUPA
l SRAN8.1/
GBSS15.1/
RAN 15.1
HSPA
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PS
RAB
Duratio
n
[0,+)
Seco
nd
Statistics on the duration of PS services

used by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3168
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Failure
Cause
For details,
see "Access
information/
RRC Setup
Failure
Cause".
N/A
For details, see "Access information/

RRC Setup Failure Cause".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IU
Release
Cause
N/A
N/A
Cause of signaling release of a call.

the IU RELEASE REQUEST message.
For details, see 3GPP 25.413 - 9.1.6.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3169
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Cause
for CS
RAB
Setup
Failure
N/A
N/A

failure.
l SRAN8.0/
GBSS15.0/
RAN 15.0

see 3GPP 25.413 - 9.1.4.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cause
for CS
RAB
Release
Failure
N/A
N/A

failure.
see 3GPP 25.413 - 9.1.4.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3170
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Cause
for PS
RAB
Setup
Failure
N/A
N/A

failure.
l SRAN8.0/
GBSS15.0/
RAN 15.0

see 3GPP 25.413 - 9.1.4.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cause
for PS
RAB
Release
Failure
N/A
N/A

failure.
see 3GPP 25.413 - 9.1.4.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3171
Nastar
User Information
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
TMSI/
PTMSI
0000000-FFFFFFFF
N/A
Temporary mobile subscriber

identity (TMSI) or packet
temporary mobile subscriber
identify (P-TMSI) of a UE
assigned by the network in the
CS domain or PS domain.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User
ID:Alia
s
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3172
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMEITAC
00000000-99999999
N/A

a UE.
short.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3173
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Termin
al
Model
N/A
N/A
Model of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0

UE.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
UE
Capabil
ity
N/A
N/A
Capability of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3174
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Proto
col
Versio
n
REL-99
N/A
3GPP version with which a UE

complies.
l SRAN8.0/
GBSS15.0/
RAN 15.0
REL-4 ~ REL-20
later than REL-20
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Power
Class
[1,4]
N/A
Power class of a UE.

For details, see "A UE with UE
power class 3bis signals the
value 3" under "UE Radio
Transmission and Reception
(FDD)" in 3GPP TS 25.101.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3175
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Suppo
rt
UTRA
Band
Band I
N/A
Universal Terrestrial Radio

Access (UTRA) frequency
bands supported by a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
For details, see Table 5.0

"UTRA FDD frequency bands"
under "UE Radio Transmission
and Reception (FDD)" in 3GPP
TS 25.101.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Band II
Band III
Band IV
Band V
Band VI
Band VII
Band VIII
Band IX
Band X
Band XI
Band XII
Band XIII
Band XIV
Band XV
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Band XVI
Band XVII
Band XVIII
Band XIX
Band XX
Band XXI
Band XXII
Reserved
Issue 03 (2015-07-30)

3176
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>HSPA
Capabil
ity
N/A
N/A
HSPA capability of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>HSDSCH
Capabil
ity
[1,64]
N/A
HSDPA capability of a UE. A

indicates larger HSDPA
capability.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3177
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>>EDCH
Capabil
ity
[1,16]
N/A
HSUPA capability of a UE. A

indicates larger HSUPA
capability.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Sup
port ERACH
supported
unsupported
N/A
Whether a UE supports ERACH.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3178
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>>Sup
port EFACH
supported
N/A
Whether a UE supports EFACH.
l SRAN8.0/
GBSS15.0/
RAN 15.0
unsupported
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Sup
port
DTXD
RX
supported
unsupported
N/A
discontinuous transmission
(DTX) and discontinuous
reception (DRX).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3179
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>>Sup
port
HSSCCH
Less
Operati
on
supported
N/A
Whether a UE supports HSSCCH.
l SRAN8.0/
GBSS15.0/
RAN 15.0
unsupported
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3180
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Mobil
ity
Capabil
ity
Support of GSM
N/A
Mobility capability of a UE. For

example, "Support of Inter-RAT
PS handover" indicates whether
a UE supports inter-RAT
handover in the PS domain.
l SRAN8.0/
GBSS15.0/
RAN 15.0
GSM450
GSM480
GSM850
GSM900P
GSM900E
GSM1800
GSM1900
Support of InterRAT PS handover
Support for lossless
SRNS relocation
Support of E-UTRA
FDD
Support of InterRAT PS Handover to
E-UTRA FDD
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Support of UTRAN
to GERAN NACC
Support of Handover
to GAN
Support of PS
Handover to GAN
Reserved
Issue 03 (2015-07-30)

3181
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Suppo
rt EUTRA
Band
Capabil
ity
Support Band 1
N/A
Evolved Universal Terrestrial

Radio Access (E-UTRA)
frequency bands supported by a
UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
......
Support Band 64
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Positi
oning
Capabil
ity
Standalone location
method(s) supported
N/A
Positioning capability of a UE.
UE based OTDOA
supported
l SRAN8.0/
GBSS15.0/
RAN 15.0
GANSS support
indication
l SRAN8.1/
GBSS15.1/
RAN 15.1
Support for GPS

timing of cell frames
measurement
l SRAN9.0/
GBSS16.0/
RAN16.0
Support for IPDL
l SRAN10.0/
GBSS17.0/
RAN17.0
Support for Rx-Tx

time difference type2
measurement
Support for UP
assisted GPS
measurement validity
in CELL_PCH and
URA_PCH states
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Support for SFNSFN observed time

difference type 2
measurement
Network Assisted
GPS support
Issue 03 (2015-07-30)

3182
Nastar
Access Information
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Request
Time
N/A
N/A
Time of signaling access during a

call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

CONNECTION SETUP message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Radio
Link
Setup
Time
N/A
N/A
Time of RRC radio link setup

during a call. That is, timestamp in
the RADIO LINK SETUP
REQUEST message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3183
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Cell on
RRC
Setup
N/A
N/A
Name of the cell to which

signaling accesses.
l SRAN8.0/
GBSS15.0/
RAN 15.0

not displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
DRD
Target
Cell on
RRC
Setup
N/A
N/A
Target cell of Directed Retry

Decision (DRD) during signaling
access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Note that when DRD occurs

during signaling access, statistics
on accessibility counters are
collected under the DRD target
call instead of under the RRC
setup cell. A example of such
counter is the number of
successful accesses and failed
accesses under a cell.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3184
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Status
SRB on
FACH_RACH
N/A
RRC status after RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
SRB on
DCH_DCH
l SRAN8.1/
GBSS15.1/
RAN 15.1
SRB on
HSDSCH_RACH
l SRAN9.0/
GBSS16.0/
RAN16.0
SRB on
HSDPA_DCH
SRB on
DCH_HSUPA
l SRAN10.0/
GBSS17.0/
RAN17.0
SRB on
HSDPA_HSUPA
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Setup
Type
Static reloc in
HHO reloc in
Cell update reloc
in
Inter RAT
handover in
RRC setup
without DRD
RRC setup with
DRD
N/A

CONNECTION SETUP message:
l SRAN8.0/
GBSS15.0/
RAN 15.0

in)
l SRAN8.1/
GBSS15.1/
RAN 15.1

migration request.
reloc in)
DRD)
DRD)
Issue 03 (2015-07-30)

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3185
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Cause
Originating
Conversational
Call
N/A
Cause of RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Originating
Streaming Call

cause."
Originating
Interactive Call
l SRAN8.1/
GBSS15.1/
RAN 15.1
Originating
Background Call
l SRAN9.0/
GBSS16.0/
RAN16.0
Originating
Subscribed traffic
Call
l SRAN10.0/
GBSS17.0/
RAN17.0
Terminating
Conversational
Call
l SRAN10.1/
GBSS17.1/
RAN17.1
Terminating
Streaming Call
l SRAN11.0/
GBSS18.0/
RAN18.0
Terminating
Interactive Call
Terminating
Background Call
Emergency Call
Inter-RAT cell reselection
Inter-RAT cell
change order
Registration
Detach
Originating High
Priority Signaling
Originating Low
Priority Signaling
Terminating High
Priority Signaling
Terminating Low
Priority Signaling
MBMS reception
Issue 03 (2015-07-30)

3186
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
N/A

by service or non-service causes
based on RRC Setup Cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
MBMS ptp RB
request
RRC
Setup
Flag
(Servic
e/NonService
)
Service
Non-service
1. RRC setup is triggered by nonservice causes when the following

conditions are met:
The value of RRC Setup Cause is
@Inter-RAT cell re-selection
@Inter-RAT cell change order
@Registration
@Detach
There is no RAB information in
this call record.
triggered by service causes.
RRC
Setup
Flag
(CS
Domain
/PS
Domain
)
CS
PS
N/A
Whether RRC setup occurs in the

CS or PS domain based on RRC
Setup Cause.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3187
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Flag
(MOC/
MTC)
MOC
N/A
Whether RRC setup occurs on the

MOC or MTC side based on RRC
Setup Cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0

occurrence conditions are as
follows:
l SRAN8.1/
GBSS15.1/
RAN 15.1
1. RRC setup occurs on the MOC

l SRAN9.0/
GBSS16.0/
RAN16.0
Originating Conversational Call
l SRAN10.0/
GBSS17.0/
RAN17.0
MTC
Blank
Originating Streaming Call

Originating Interactive Call
Originating Background Call
Originating Subscribed traffic
Call
Originating High Priority
Signaling
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Signaling
Emergency Call
2. RRC setup occurs on the MTC
Terminating Conversational Call
Terminating Streaming Call
Terminating Interactive Call
Terminating Background Call
Terminating High Priority
Signaling,
Signaling,
Terminating - cause unknown
3. The value of this parameter is
empty when the value of RRC
Setup Cause contains other
information.
Issue 03 (2015-07-30)

3188
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Flag
(SMS/
NonSMS)
SMS
N/A

by SMS or non-SMS causes based
on RRC Setup Cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
No-SMS
1. RRC setup is triggered by SMS

causes when the value of RRC
Setup Cause is any of the
following:
Signaling
Signaling
triggered by non-SMS causes.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Setup
Results
Successful
N/A
Failed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3189
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
RRC
Setup
Failure
Cause
N/A
N/A
Cause of RRC setup failure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error Type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3190
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error Reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Setup
Time
Info
N/A
N/A
Time information on RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3191
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>RRC
Setup
Delay
[0,+)
Seco
nd
Delay on RRC setup. The

statistical points are as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0
RRC setup: Timestamp in the

message - Timestamp in the RRC
CONNECTION SETUP
COMPLETE message.
message - Timestamp in the UE
CAPABILITY INFORMATION
CONFIRM message.
>Overl
ong
RRC
Setup
Delay
Yes
No
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0

message - Timestamp in the
UTRAN MOBILITY
INFORMATION CONFIRM
message.
l SRAN10.1/
GBSS17.1/
RAN17.1
Overlong RRC setup delay occurs

when the RRC setup delay
threshold limit.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The abnormal threshold is set by

engineers during analysis task
creation.
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3192
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
Measur
ement
Info on
RRC
Setup
N/A
N/A
RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cell
N/A
N/A

requested.
not displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3193
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>TP
[0,3069 ]
N/A
Time Propagation (TP) is a term

defined by Huawei to indicate
time propagation delay during UE
access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>TP
Abnor
mal
Yes
No
N/A
If "TP" is larger than "TP

abnormal threshold", it indicators
that the TP is abnormal on RRC
setup.
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3194
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>Ec/
NO
[-31.5,0]
dB
Ec/No of the serving cell on RRC

setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Ec/
NO
Abnor
mal
Yes
No
N/A
If "Ec/No" is smaller than "Ec/No

setup", it indicators that the Ec/No
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3195
Nastar
Param
eter
Range
Uni
t
Description
Supported
Solution
Version
>RSCP
[-116,-25]
dBm
RSCP of the serving cell on RRC

setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RSCP
Abnor
mal
Yes
No
N/A
If "RSCP" is smaller than "RSCP

setup", it indicators that the RSCP
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3196
Nastar
Release Information
Param
eter
Range
Unit
Description
Supported
Solution
Version
RRC
Release
Time
N/A
N/A
Release time of RRC connection.
l SRAN8.0/
GBSS15.0/
RAN 15.0

CONNECTION RELEASE
message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Duratio
n
[0,+)
Seco
nd
Duration of a call.
Call duration = RRC release time
- RRC setup request time
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3197
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RRC
Release
Cell
1 to 64 characters
N/A
Name of the cell from which

signaling is released.
l SRAN8.0/
GBSS15.0/
RAN 15.0

name:cell name (RNCID: cellID).
not displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RRC
Release
Result
Successful
N/A
RRC release results.
Failed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3198
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
IU
Release
Cause
N/A
N/A
Release cause carried in the last IU

RELEASE COMMAND message
received by an RNC.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
type
Radio Network
Layer Cause
Transport Layer
Cause
N/A
Type of failure cause.

25.413-9.2.1.4.
NAS Cause
Protocol Cause
Miscellaneous
Cause
Non-standard
Cause
Radio Network
Layer Cause
Extension
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3199
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Cause
value
N/A
N/A
Failure cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0

25.413-9.2.1.4.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3200
Nastar
Statistical Information
Param
eter
Range
Unit
Description
Supported
Solution
Version
Soft
Handov
er Info
N/A
N/A
Soft handover information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Soft
Handov
er
Request
s
[0,+)
Num
ber
Number of soft handover requests,

including soft handover requests
and softer handover requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3201
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Succe
ssful
Soft
Handov
ers
[0,+)
Num
ber
Number of successful soft

handovers, including successful
soft handovers and successful
softer handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Softer
Handov
er
Request
s
[0,+)
Num
ber
Number of softer handover

requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3202
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Succe
ssful
Softer
Handov
ers
[0,+)
Num
ber
Number of successful softer

handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Hard
Handov
er Info
N/A
N/A
Hard handover information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3203
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>IntraFreq
Handov
er
Request
s
[0,+)
Num
ber
Number of intra-frequency hard

handover requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Succe
ssful
IntraFreq
Handov
ers
[0,+)
Num
ber
Number of successful intrafrequency hard handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3204
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>InterFreq
Handov
er
Request
s
[0,+)
Num
ber
Number of inter-frequency hard

handover requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Succe
ssful
InterFreq
Handov
ers
[0,+)
Num
ber
Number of successful interfrequency hard handovers.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3205
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
InterRAT
Handov
er Info
N/A
N/A
Inter-RAT handover information
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>InterSystem
Outgoin
g
Handov
er
Request
s(CS)
[0,+)
Num
ber
Number of CS domain outgoing

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3206
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>InterSystem
Outgoin
g
Handov
er
Request
s(PS)
[0,+)
Num
ber
Number of PS domain outgoing

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Succe
ssful
InterSystem
Outgoin
g
Handov
ers
[0,+)
Num
ber
Number of successful outgoing

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3207
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>InterSystem
Incomi
ng
Handov
er
Request
s
[0,+)
Num
ber
Number of incoming inter-RAT

handover requests.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Succe
ssful
InterSystem
Incomi
ng
Handov
ers
[0,+)
Num
ber
Number of successful incoming

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3208
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
DCCC
Info
N/A
N/A
DCCC information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DCCC
Speed
Increas
e
Initializ
ation
Times
[0,+)
Num
ber
Number of DCCC speed increase

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3209
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DCCC
Speed
Increas
e
Success
Times
[0,+)
Num
ber

speed increases during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DCCC
Speed
Decreas
e
Initializ
ation
Times
[0,+)
Num
ber
Number of DCCC speed decrease

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3210
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DCCC
Speed
Decreas
e
Success
Times
[0,+)
Num
ber

speed decreases during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Info
N/A
N/A
RAB information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3211
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Request
/Setup
Success
Times/
Normal
Release
Times/
Abnor
mal
Release
Times
(AMR)
[0,+)
Num
ber

releases for the AMR service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Request
/Setup
Success
Times/
Normal
Release
Times/
Abnor
mal
Release
Times
(VP)
[0,+)
Num
ber

releases for the VP service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3212
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Request
/Setup
Success
Times/
Normal
Release
Times/
Abnor
mal
Release
Times
(PS)
[0,+)
Num
ber

releases for PS services.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In which, PS services include the

PS R99 service, HSDPA service,
HSUPA, service, and HSPA
service.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Request
/Setup
Success
Times/
Normal
Release
Times/
Abnor
mal
Release
Times
(HSDP
A)
[0,+)
Num
ber

releases for the HSDPA service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3213
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
MultiRAB
Info
N/A
N/A
Multi-RAB information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Abnor
mal CS
Release
due to
PS
Release
[0,+)
Num
ber

caused by PS release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3214
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Abnor
mal CS
Release
due to
PS
Service
Setup
[0,+)
Num
ber

caused by PS service setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Releas
ed
RABs
in CS
Domain
Trigger
ed by
the
Failure
in
Securit
y Mode
[0,+)
Num
ber

CS domain triggered by failed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3215
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Releas
ed
RABs
in PS
Domain
Trigger
ed by
the
Failure
in
Securit
y Mode
[0,+)
Num
ber

PS domain triggered by failed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Setup
Attempt
s of
Combin
ed
Service
(CS +
PS)
[0,+)
Num
ber
Setup Attempts of Combined

Service(CS + PS)
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3216
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Succe
ssful
Setups
of
Combin
ed
Service
(CS +
PS)
[0,+)
Num
ber
Successful Setups of Combined

Service(CS + PS)
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>CS
plus PS
multiRAB
CS
normal
release
times
[0,+)
Num
ber
CS plus PS multi-RAB CS normal

release times.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3217
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>CS
plus PS
multiRAB
CS
abnorm
al
release
times
[0,+)
Num
ber
CS plus PS multi-RAB CS
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>CS
plus PS
multiRAB PS
normal
release
times
[0,+)
Num
ber
CS plus PS multi-RAB PS normal

release times.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3218
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>CS
plus PS
multiRAB PS
abnorm
al
release
times
[0,+)
Num
ber
CS plus PS multi-RAB PS
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Setup
Attempt
s of
Combin
ed
Service
(PS +
PS)
[0,+)
Num
ber
Setup attempts of combined

service(PS + PS).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3219
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Succe
ssful
Setups
of
Combin
ed
Service
(PS +
PS)
[0,+)
Num
ber
Successful setups of combined

service(PS + PS).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Norm
al
Release
s of
Combin
ed
Service
(PS +
PS)
[0,+)
Num
ber
Normal releases of combined

service(PS + PS).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3220
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Abnor
mal
Release
s of
Combin
ed
Service
(PS +
PS)
[0,+)
Num
ber
Abnormal releases of combined

service(PS + PS).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Statistic
s of
Voice
Quality
in CS
Domain
N/A
N/A
Statistics on voice quality in CS

domain.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3221
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>OneWayAudio
Times
[0,+)
Num
ber
Number of times that one-way

audio occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Noise
Times
[0,+)
Num
ber
Number of times that noise occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3222
Nastar
CS RAB Service Information

Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Setup
Info
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

short.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Multi
RAB
info
1CS
1CS + 1PS
N/A

combined RABs.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3223
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Request
Service
Type
Traffic class:
N/A
RAB request service type consists

of two parts: Traffic class and
Traffic type.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Traffic type.
l SRAN8.1/
GBSS15.1/
RAN 15.1

3GPP 25.413.
l SRAN9.0/
GBSS16.0/
RAN16.0
conversational
streaming
interactive
background
Traffic type:
CS_AMR

CS_VP
CS_OTHER
PS_GENERAL
PS_HSDPA
l SRAN10.1/
GBSS17.1/
RAN17.1
PS_HSUPA
PS_HSPA ...
>RAB
Request
Time
N/A
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
N/A
Time when RAB setup is

requested. The statistical points
are as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0

message.
l SRAN8.1/
GBSS15.1/
RAN 15.1

in the RELOCATION
COMPLETE message.
l SRAN9.0/
GBSS16.0/
RAN16.0

COMPLETE message.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3224
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Cell
on RAB
Setup
Request
N/A
N/A

requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Comple
tion
Time
[0,+)
Seco
nd

follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0

RAB ASSIGNMENT
RESPONSE message.
l SRAN8.1/
GBSS15.1/
RAN 15.1

not recorded.
l SRAN9.0/
GBSS16.0/
RAN16.0

not recorded.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3225
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Best
Cell on
RAB
Setup
Comple
tion
N/A
N/A

completes.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Servin
g Cell
on RAB
Setup
Comple
tion
N/A
N/A
Service cell on which RAB setup

completes.
displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3226
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DRD
Info
N/A
N/A

RAB setup, recording the last three
DRDs at most.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DRD
Info:N
N/A
N/A
The N DRD record.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3227
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>DR
D
Target
Cell on
RRC
Setup
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>DR
D
traffic
type
CS_AMR
CS_VP
N/A
Traffic type when the current DRD

occurs.
CS_OTHER
PS_GENERAL
PS_HSDPA
PS_HSUPA
PS_HSPA
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3228
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>DR
D
Failure
Cause
N/A
N/A
DRD failure cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Enumeration Values of Failure
Cause (UMTS)".
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>>Er
ror
Type

"Enumeration
Values of Failure
Cause".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3229
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>>Er
ror
Reason

"Enumeration
Values of Failure
Cause".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Peer
Info
N/A
N/A
Information about the peer UE

during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3230
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>Pee
r
MSISD
N
00000000000000
0-999999999999
999
N/A
Mobile station international ISDN l SRAN8.0/

number (MSISDN) of the peer UE.
GBSS15.0/
MSISDN is a 15-digit numeric
RAN 15.0
string of decimal digits (0-9). For l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3231
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL
Channe
l Types
After
RAB
Setup
DL transport
channel type:
N/A

transmission channel after RAB
setup. The channel types are
defined by Huawei.
l SRAN8.0/
GBSS15.0/
RAN 15.0
DCH
FACH
RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
UL transport
channel type:
DCH
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
Issue 03 (2015-07-30)

3232
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL RB
Rate
[0,+)
kbit/s

RAB setup. The parameter value is
l SRAN8.0/
GBSS15.0/
RAN 15.0
In which,
l SRAN8.1/
GBSS15.1/
RAN 15.1

8000 bit/s.
l SRAN9.0/
GBSS16.0/
RAN16.0

s.
l SRAN10.0/
GBSS17.0/
RAN17.0

conditions.
l SRAN10.1/
GBSS17.1/
RAN17.1

bit/s.
l SRAN11.0/
GBSS18.0/
RAN18.0

s.
conditions.
Issue 03 (2015-07-30)

3233
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Result
Successful
N/A
RAB setup results.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Failed
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Failure
Time
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3234
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Failure
Cause
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3235
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Delay
Estimat
ion
N/A
N/A
Delay estimation on RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3236
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>RAB
Setup
Delay
[0,+)
Seco
nd

RAB setup is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Over
long
RAB
Setup
Delay
Yes
No
N/A

when the RAB setup delay exceeds
l SRAN8.0/
GBSS15.0/
RAN 15.0

creation.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3237
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Call
Setup
Delay
[0,+)
Seco
nd
Call setup delay = Time when

RRC setup is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Call setup delay = RAB setup

delay + RRC setup delay.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Note that this parameter is

applicable only to the first RAB
after RRC setup.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Over
long
Call
Setup
Delay
Yes
No
N/A
Overlong call setup delay occurs

when the call setup delay exceeds
l SRAN8.0/
GBSS15.0/
RAN 15.0

creation.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3238
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>CM
Service
Request
Time
N/A
N/A

Request" message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Uu
Delay
[0,+)
Seco
nd

as follows:
RADIO BEARER SETUP
in the RADIO BEARER
RECONFIGURATION
BEARER RECONFIGURATION
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3239
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Alert
ing
Time
N/A
N/A
Time of outgoing call alerting

Timestamp in the ALERTING
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Call
Comple
tion
Delay
(Alertin
g)
N/A
[0,+)
N/A

after RRC setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
Outgoing call alerting delay =

Alerting time - RRC setup request l SRAN10.0/
GBSS17.0/
time.
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3240
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Over
long
Call
Comple
tion
Delay
(Alertin
g)
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
Yes
No

after RRC setup.
MOC.
after RRC setup.
MTC.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

other conditions.
Issue 03 (2015-07-30)

3241
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Conn
ect Ack
Time
N/A
N/A
Time of incoming call alerting

Timestamp in the CONNECT
ACKNOWLEDGE message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Call
Comple
tion
Delay
(Conne
ct Ack)
[0,+)
Seco
nd

after RRC setup.
Incoming call alerting delay =
Connect Ack time - RRC setup
request time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3242
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Over
long
Call
Comple
tion
Delay
(Conne
ct Ack)
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
Yes
No

after RRC setup.
MOC.
after RRC setup.
MTC.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

other conditions.
Issue 03 (2015-07-30)

3243
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Process
N/A
N/A
Process information of RAB setup.

This parameter is used with RAB
Setup Failure Cause to analyze
problems.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Queu
ing
Indicato
r
False
True
N/A
TRUE(1) indicates that queuing

occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3244
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Intra
-system
DRD
Indicato
r
False
N/A
TRUE(1) indicates that intrasystem DRD occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
True
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Inter
-system
DRD
Indicato
r
False
True
N/A
TRUE(1) indicates that intersystem DRD occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3245
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Resourc
e
Congest
ion
Informa
tion on
RAB
Setup
N/A
N/A
Information about the latest radio

resource congestion during RAB
setup. This parameter is used with
RAB Setup Failure Cause to
analyze problems.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Cong
estion
Time
N/A
N/A
Time when radio resource

congestion occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3246
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Cong
estion
Cell ID
N/A
N/A
Cell where radio resource

congestion occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Cong
estion
Status
Code
DL CE
N/A
Cause of radio resource

congestion.
UL CE
UL DL CE
DL IUB band
UL IUB band
UL DL IUB band
UL power
DL power
UL DL power
HSDPA user
number
HSUPA user
number
HSPA user
number
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3247
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Release
Info
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Multi
RAB
info
1CS
1CS + 1PS
N/A

combined RABs.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3248
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Single
-RAB
Abnor
mal
Release
Indicato
r
False
N/A

abnormal release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
True
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Multip
le-RAB
Abnor
mal
Release
Indicato
r
False
True
N/A

abnormal release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3249
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Release
Time
N/A
N/A

are as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0
Normal release and CN abnormal l SRAN8.1/

GBSS15.1/
RAN 15.1
COMMAND or RAB
l SRAN9.0/
ASSIGNMENT REQUEST
GBSS16.0/
message.
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Duratio
n
[0,+)
Seco
nd

- RAB setup time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3250
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Duratio
n
Shorter
Yes
N/A
If "RAB Duration" is smaller than

"RAB Duration shorter threshold",
it indicators that the RAB duration
is too shorter.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Best
Cell
Before
RAB
Release
N/A
N/A

displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3251
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Servin
g Cell
Before
RAB
Release
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3252
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL
Channe
l Types
DL transport
channel type:
N/A

transmission channel before RAB
release. The channel types are
defined by Huawei.
l SRAN8.0/
GBSS15.0/
RAN 15.0
DCH
FACH
RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
UL transport
channel type:
DCH
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
Issue 03 (2015-07-30)

3253
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL RB
Rate
[0,+)
kbit/s

RAB setup and before RAB
release. The parameter value is
l SRAN8.0/
GBSS15.0/
RAN 15.0
In which,
l SRAN9.0/
GBSS16.0/
RAN16.0

8000 bit/s.
s.
conditions.
bit/s.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

s.
conditions.
Issue 03 (2015-07-30)

3254
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Disco
nnect
Cause
N/A
N/A
Cause carried in the

DISCONNECT message. For
details, see 3GPP
24.008-10.5.4.11.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Disco
nnect
Directio
n
from UE
from CN
N/A
Direction for sending the

DISCONNECT message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3255
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Release
Failure
Cause
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3256
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Release
Failure
Time
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
IU RELEASE REQUEST
l SRAN8.1/
GBSS15.1/
RAN 15.1
RAB RELEASE REQUEST
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3257
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Process
Info
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Delay
Estimat
ion
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3258
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Disc
onnect
time
N/A
N/A
Time when a call completes.

Statistical point: timestamp in the
DISCONNECT message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Servi
ce
Duratio
n
[0,+)
Seco
nd
Service duration = Disconnect

time - Connect Ack time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3259
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Short
Call
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
Yes
No
When the current RAB is not the

first RAB after RRC setup and Call
duration < Short call threshold.
after RRC setup.
MOC.
(MOC).
after RRC setup.
MTC.
(MTC).
other conditions.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
The short call threshold, short call

threshold (MOC), and short call
Issue 03 (2015-07-30)

3260
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>SQI
Statistic
s
N/A
N/A
Statistics on SQIs
l SRAN8.0/
GBSS15.0/
RAN 15.0

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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
2. The RNC can statistics based on

the average SQI value and divides
signal quality into different levels l SRAN10.1/
GBSS17.1/
according to SQI values:
RAN17.1
l SRAN11.0/
(400,500]), Good (SQI<=
GBSS18.0/
(300,400]), Accept (SQI<=
RAN18.0
(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.
Issue 03 (2015-07-30)

3261
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Aver
age SQI
[0,500]
N/A
Average SQI value during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Abn
ormal
SQI
Yes
No
N/A
If SQI average < Abnormal SQI

threshold,
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
The abnormal SQI threshold is set
RAN 15.1
by engineers during task creation.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3262
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Radi
o of
Excelle
nt SQIs
(%)
[0,100]

SQI as Excellent from RAB setup
to RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Radi
o of
Good
SQIs
(%)
[0,100]

SQI as Good from RAB setup to
RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3263
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Radi
o of
Accept
SQIs
(%)
[0,100]

SQI as Accept from RAB setup to
RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Radi
o of
Poor
SQIs
(%)
[0,100]

SQI as Poor from RAB setup to
RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3264
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Radi
o of Bad
SQIs
(%)
[0,100]

SQI as Bad from RAB setup to
RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BLER
Statistic
Info
N/A
N/A
Statistics on BLERs.
statistics are collected by the RNC.
The value range is [0.00,100.00].
A larger value indicates worse
signal quality.
are:
0-0.78%, 0.78%-1.56%,
1.56%-3.12%, 3.12%-6.24%,
6.24%-12.48%, above 12.48%.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3265
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Time
s UL
Service
BLER
Falls
into
Levels
1 to 6
[0,+)
Num
ber
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Statist
ics on
Last
Receive
d
Blocks
N/A
N/A

seconds.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3266
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Num
ber of
UL
Total
Blocks
(1~5)
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
UL
Error
Blocks
(1~5)
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

5.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3267
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Uplin
k OneWayAudio
Statistic
s
N/A
N/A
Statistics on uplink one-way

audio.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1. The RNC records an uplink oneway audio problem when it detects

any error packet or a large packet
loss rate at the uplink IUUP layer.
2. The RNC records a maximum of
the first five uplink one-way audio
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Occu
rrence
Time
N/A
N/A
Time when uplink one-way audio

occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3268
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Occu
rrence
Cell
N/A
N/A
Cell when uplink one-way audio

occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DL
Silence
Statistic
Info
N/A
N/A
Statistics on downlink one-way

audio. The downlink one-way
audio problems fall into two types:
l SRAN8.0/
GBSS15.0/
RAN 15.0

detects any error packet or a large
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1

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
Issue 03 (2015-07-30)

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3269
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Occu
rrence
Time
N/A
N/A
Time when a downlink one-way

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Occu
rrence
Cell
N/A
N/A
Cell when a downlink one-way

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3270
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Nois
e
Statistic
s
N/A
N/A
Statistics on noises.
1. The RNC records a noise
problem.
l SRAN8.0/
GBSS15.0/
RAN 15.0
2. The RNC records only the first

one noise problem during each call
of a UE.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Occu
rrence
Time
N/A
N/A
Time when a noise problem

occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3271
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Occu
rrence
Cell
N/A
N/A
Cell when a noise problem occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3272
Nastar
PS RAB Service Information

Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Setup
Info
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

short.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Multi
RAB
info
1CS
1CS + 1PS
N/A

combined RABs.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3273
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Request
Service
Type
Traffic class:
N/A
There are two RAB request

service types: Traffic class and
Traffic type.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Traffic type.
l SRAN8.1/
GBSS15.1/
RAN 15.1

3GPP 25.413.
l SRAN9.0/
GBSS16.0/
RAN16.0
conversational
streaming
interactive
background
Traffic type:
CS_AMR

CS_VP
CS_OTHER
PS_GENERAL
PS_HSDPA
l SRAN10.1/
GBSS17.1/
RAN17.1
PS_HSUPA
PS_HSPA ...
>RAB
Request
Time
N/A
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
N/A
Time for requesting RAB setup.

follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0

message.
l SRAN8.1/
GBSS15.1/
RAN 15.1

in the RELOCATION
COMPLETE message.
l SRAN9.0/
GBSS16.0/
RAN16.0

COMPLETE message.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3274
Nastar
Param
eter
Range
>Cell
N/A
on RAB
Setup
Request
Unit
Description
Supported
Solution
Version
N/A

requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Comple
tion
Time
[0,+)
Seco
nd

follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0

RAB ASSIGNMENT
RESPONSE message.
l SRAN8.1/
GBSS15.1/
RAN 15.1

not recorded.
l SRAN9.0/
GBSS16.0/
RAN16.0

not recorded.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3275
Nastar
Param
eter
Range
>Cell
N/A
on RAB
Setup
Comple
tion
Unit
Description
Supported
Solution
Version
N/A

completes.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Serving
Cel on
RAB
Setup
Comple
tion
N/A
N/A
Serving cell on which RAB setup

completes.
displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3276
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DRD
Info
N/A
N/A

RAB setup, recording the last
three DRDs at most.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>DRD
Info:N
N/A
N/A
The N DRD record.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3277
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>DR
D
Target
Cell on
RRC
Setup
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>DR
D
traffic
type
CS_AMR
CS_VP
N/A
Traffic type when the current

DRD occurs.
CS_OTHER
PS_GENERAL
PS_HSDPA
PS_HSUPA
PS_HSPA ...
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3278
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>DR
D
Failure
Cause
N/A
N/A
DRD failure cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
For details, see the Failure Cause

tab page.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>>Er
ror
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)"
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3279
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>>Er
ror
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3280
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL
Channe
l Types
After
RAB
Setup
DL transport
channel type:
N/A

data transmission channel after
RAB setup. The channel types are
defined by Huawei.
l SRAN8.0/
GBSS15.0/
RAN 15.0
DCH
FACH
RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
UL transport
channel type:
DCH
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
Issue 03 (2015-07-30)

3281
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL RB
Rate
[0,+)
bps
DL/UL RB rate after RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0

after RAB setup.
In which,
l SRAN8.1/
GBSS15.1/
RAN 15.1
s.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0

conditions.
8000 bit/s.
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

s.
conditions.
Issue 03 (2015-07-30)

3282
Nastar
Param
eter
Range
>UL/
[0,+)
DL
RAB
Negotia
ted Rate
Unit
Description
Supported
Solution
Version
bps
UL/DL RAB negotiated rate.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Yes
Overlo
w UL
No
RAB
Negotia
ted Rate
N/A
If "Overlow UL RAB Negotiated

UL RAB Negotiated Rate
problem that the overlow UL RAB
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3283
Nastar
Param
eter
Range
Overlo
Yes
w DL
No
RAB
Negotia
ted Rate
Unit
Description
Supported
Solution
Version
N/A
If "Overlow DL RAB Negotiated

DL RAB Negotiated Rate
problem that the overlow DL RAB
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Result
Successful
N/A
Failed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3284
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Failure
Time
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Setup
Failure
Cause
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3285
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3286
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Setup
Delay
Estimat
ion
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>RAB
Setup
Delay
[0,+)
Seco
nd

RAB setup completes - Time
when RAB setup is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3287
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Over
long
RAB
Setup
Delay
Yes
N/A

when the RAB setup delay
threshold limit.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No
The overlong delay threshold is

set by engineers during analysis
task creation.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Call
Connec
tion
Delay
[0,+)
Seco
nd

occurs, it displays the result value.
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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3288
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Over
long
Call
Connec
tion
Delay
Yes
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
No

2.When the following scenes
occur, it displays the result value.
l SRAN8.1/
GBSS15.1/
RAN 15.1

"MOC"; and "Call Setup Delay" is
larger than "Latency on Call
Connection (MOC) ".
l SRAN9.0/
GBSS16.0/
RAN16.0

"MTC"; and "Call Setup Delay" is
smaller than "Latency on Call
Connection (MTC) ".
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
3.When the other scene occurs, it

displays "No".
The threshold is set by engineers
during analysis task creation.
>>CM
Service
Request
Time
N/A
N/A

Request" message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3289
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Uu
delay
(ms)
[0,+)
Seco
nd

as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0

RADIO BEARER SETUP
in the RADIO BEARER
RECONFIGURATION
BEARER
RECONFIGURATION message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Sched
uling
Priority
N/A
N/A
Scheduling priority during RAB

setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3290
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Allo
cation/
Retenti
on
Priority
N/A
N/A
Allocation/retention priority. For

details, see 3GPP 25.413-9.2.1.3.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>Pri
ority
Level
[0,15]
N/A

retention of RABs.
highest priority.
lowest priority.
no priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3291
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>Pre
emptio
n
Capabil
ity
Shall not trigger

pre-emption
N/A
Whether the current RAB can

preempt resources of other RABs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
May trigger preemption
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>>Pre
emptio
n
Vulnera
bility
Not pre-emptable
Pre-emptable
N/A
Whether resources of the current

RAB can be preempted by other
RABs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3292
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>>Qu
euing
Allowe
d
Queuing not
allowed
N/A
Whether the current RAB can be

queued for resource scheduling.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Queuing allowed
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Traff
ic
Handlin
g
Priority
[0,15]
N/A

retention of system resources. For
details, see 3GPP
25.433-9.2.1.1A.
highest priority.
lowest priority.
no priority.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3293
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Sche
duling
Priority
Indicato
r
[0,15]
N/A
HS-DSCH scheduling priority.

25.433-9.2.1.53H.
l SRAN8.0/
GBSS15.0/
RAN 15.0

value indicates higher priority.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Release
Info
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3294
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Multi
RAB
info
1CS
N/A

combined RABs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1CS + 1PS
1CS + 2PS
l SRAN8.1/
GBSS15.1/
RAN 15.1
1CS + 3PS
2CS
2CS + 1PS
l SRAN9.0/
GBSS16.0/
RAN16.0
2CS + 2PS
1PS
l SRAN10.0/
GBSS17.0/
RAN17.0
2PS
3PS
4PS
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Single
-RAB
Abnor
mal
Release
Indicato
r
False
True
N/A

abnormal release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3295
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Multi
pleRAB
Abnor
mal
Release
Indicato
r
False
N/A

abnormal release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
True
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Release
Time
N/A
N/A

are as follows:
l SRAN8.0/
GBSS15.0/
RAN 15.0
Normal release and CN abnormal

COMMAND or RAB
ASSIGNMENT REQUEST
message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3296
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Duratio
n
[0,+)
RAB duration = RAB release

time - RAB setup time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Best
Cell
Before
RAB
Release
N/A
N/A

displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3297
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Servin
g Cell
Before
RAB
Release
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3298
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL
Channe
l Types
UL transport
channel type:
N/A

data transmission channel before
RAB release. The channel types
are defined by Huawei.
l SRAN8.0/
GBSS15.0/
RAN 15.0
DCH
FACH
RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
DL transport
channel type:
DCH
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
Issue 03 (2015-07-30)

3299
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>UL/
DL RB
Rate
[0,+)
kbit/s
UL/DL RB rate after RAB setup

and before RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0

after RAB setup.
In which,
s.
conditions.
8000 bit/s.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

s.
conditions.
Issue 03 (2015-07-30)

3300
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>DP
Deactiv
ate
Cause
N/A
N/A
Cause carried by the Deactivate

PDP context request message. For
details, see 3GPP 24.008-10.5.6.6
SM cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>RAB
Release
Failure
Cause
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3301
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Error
Type
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Error
Reason
For details, see

"Appendix:
Exception Cause
Classification /
Enumeration
Values of Failure
Cause (UMTS)".
N/A
Error reason.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3302
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>RAB
Release
Failure
Time
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
IU RELEASE REQUEST
l SRAN8.1/
GBSS15.1/
RAN 15.1
RAB RELEASE REQUEST
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Process
Info
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3303
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>PDP
Activat
e
Request
Time
N/A
N/A

ACTIVIATE REQUEST
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>PDP
Activat
e Ack
Time
N/A
N/A

ACTIVIATE ACKNOWLEDGE
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3304
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>PDP
Deactiv
ate
Time
N/A
N/A
Timestamp in the DEACTIVATE

PDP CONTEXT REQUEST
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BLER
Statistic
Info
N/A
N/A
Statistical information about

BLERs.
statistics are collected by the
RNC. The value range is
[0.00,100.00]. A larger value
indicates worse signal quality.
are:
0-0.78%, 0.78%-1.56%,
1.56%-3.12%, 3.12%-6.24%,
6.24%-12.48%, above 12.48%.
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3305
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Time
s UL
Service
BLER
Falls
into
Levels
1 to 6
[0,+)
Num
ber
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Statist
ics on
Last
Receive
d
Blocks
N/A
N/A

seconds.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3306
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>>Num
ber of
UL
Total
Blocks
(1~5)
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
UL
Error
Blocks
(1~5)
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

5.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3307
Nastar

Param
eter
Range
Unit
Description
Supported
Solution
Version
Numbe
r
[1,+)
N/A

sent and received signaling
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signali
ng
Time
N/A
N/A
Time when a signaling message is

sent or received.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3308
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Signali
ng
Direct
to CN
N/A
Direction for sending or receiving

l SRAN8.0/
GBSS15.0/
RAN 15.0
from CN
to other RNC
l SRAN8.1/
GBSS15.1/
RAN 15.1
from other RNC

to NODEB
from NODEB
l SRAN9.0/
GBSS16.0/
RAN16.0
to UE
from UE
l SRAN10.0/
GBSS17.0/
RAN17.0
to SAS
from SAS
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signali
ng Type
N/A
N/A

transmitted over the Iu, Iur, Iub, or
Uu interface.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3309
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Signali
ng
Content
N/A
N/A

The signaling message of the
VVIP (very very important person)
is displayed when double-click a
record, it do not support to display
the common users' signaling
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3310
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Number
[1,+)
N/A

measurement report (MR).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measur
ement
Time
N/A
N/A
Time when an MR is reported.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3311
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
MR
Type
Intra-freq
measurement
type
N/A
MR type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Inter-freq
measurement
type
l SRAN8.1/
GBSS15.1/
RAN 15.1
Inter-RAT
measurement
type
l SRAN9.0/
GBSS16.0/
RAN16.0
Event MR, such

as E1A and so on
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measur
ement
Object
Type
Best cell
Active set cell
N/A
Type of a measurement object

reported in an MR.
Monitor set cell
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3312
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Measur
ement
Object
N/A
N/A

reported in an MR.
l SRAN8.0/
GBSS15.0/
RAN 15.0

name:cell name (cell ID).
The NE name can be obtained
name cannot be queried, the cell
ID in the MR is displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
P-SC
[0,512]
N/A
Scrambling code in an MR.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3313
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Ec/NO
(dB)
[-31.5,0]
dB

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RSCP
(dBm)
[-116,-25]
dBm

25.331.
l SRAN8.0/
GBSS15.0/
RAN 15.0
In the complaint analysis support

theme, the first result in the
measurement report information
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3314
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
InterRAT
Carrier
RSSI
(dBm)
N/A
dBm

(RSSI) of a GSM carrier. For
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RSRP
(dBm)
[0,97]
dBm

(RSRP). For details, see 3GPP
36.133.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3315
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RSRQ
(dB)
[0,33]
dB

(RSRQ). For details, see 3GPP
36.133.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
UE TX
Power
(dBm)
N/A
dBm
Transmit power of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3316
Nastar
Mobility Analysis
Param
eter
Range
Unit
Description
Supported
Solution
Version
Number
[1,+)
N/A
Number of a handover during a

call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
N/A
Blank
Whether a handover is abnormal.

handover is abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3317
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Type
Softer
handover
N/A
Type of mobility analysis.

Currently, the system supports the
following mobility analysis types:
l SRAN8.0/
GBSS15.0/
RAN 15.0
Intra-freq hard
handover
Soft handover
Inter-freq hard
handover
l SRAN8.1/
GBSS15.1/
RAN 15.1
Inter-system
incoming
handover
Incoming migration
Inter-system
outgoing
handover/CS
system
handover
Cell update
Soft handover
Hard handover
Outgoing migration
Channel handover
Inter-system
outgoing
handover/Cell
change order PS
system
handover
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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 03 (2015-07-30)

3318
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
N/A
Start time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Incoming
migration/Cell
update reloc in
Outgoing
migration/
Static migration
Cell update
Channel
handover
.U2L handover
.U2L
redirection
Begin
Time
N/A
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3319
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Interval
(s)
[0,+)
Interval = Start time - End time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3320
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Overlon
g
Interval
Yes
N/A
If Interval > Overlong xxx delay

threshold,
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

The overlong xxx delay threshold
is set by engineers during task
creation. The threshold types are as
follows:
Overlong soft handover delay
threshold
Overlong hard handover delay
threshold
Overlong incoming inter-RAT
Overlong outgoing inter-RAT
Overlong incoming handover
delay threshold
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlong outgoing handover

delay threshold
Overlong channel handover delay
threshold
.Overlong U2L redirection delay
threshold
Issue 03 (2015-07-30)

3321
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
End
Time
N/A
N/A
End time.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Trigger
Cause
converage
based
N/A
Trigger cause.
HCS blind
based
HCS meas
based
load based but
blind handover
load based and
measurement
based CLB
load based and
measurement
based LDR
forced
handover
emergency
handover
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3322
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
MutiRAB
Info
1CS
N/A
Combined RAB service status

when mobility analysis is
performed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1CS + 1PS
1CS + 2PS
l SRAN8.1/
GBSS15.1/
RAN 15.1
1CS + 3PS
2CS
2CS + 1PS
l SRAN9.0/
GBSS16.0/
RAN16.0
2CS + 2PS
1PS
l SRAN10.0/
GBSS17.0/
RAN17.0
2PS
3PS
4PS
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measur
e Type
Active Set
N/A
Measurement type.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3323
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Source
Cell
N/A
N/A
The parameter value is displayed in

the following format: cell name
(cell ID).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.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Source
Ec/NO
(dB)
[-31.5,0]
dB

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3324
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Source
RSCP
(dBm)
[-116,-25]
dBm

25.331.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Source
UL
Channel
Type
DCH
FACH
N/A

RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3325
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Source
DL
Channel
Type
DCH
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
HSDSCH
EDCH
PCH
l SRAN9.0/
GBSS16.0/
RAN16.0
EFACH
ERACH
l SRAN10.0/
GBSS17.0/
RAN17.0
EPCH
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
UL RB
Rate
(kbit/s)
[0,+)
kbit/s

channel handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3326
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
DL RB
Rate
(kbit/s)
[0,+)
kbit/s

channel handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
System
N/A
N/A
Indicates the RAT of the target

network after an outgoing or
incoming inter-RAT handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3327
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
Cell
N/A
N/A
Name of target cell. The parameter

value is displayed in the following
format: RNC name:cell name (cell
ID).The NE name can be obtained
name cannot be queried, the cell ID
in the MR is displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
Ec/NO
(dB)
[-31.5,0]
dB

No) of 3G target cell. For details,
see 3GPP 25.331.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3328
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
RSCP
(dBm)
[-116,-25]
dBm

(RSCP) of 3G target cell. For
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
Target
Cell
Operati
on
RL ADD
RL DEL
N/A
Target cell operation of the 3G

target cell when occuring the soft
handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3329
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
Target
Cell
Operati
on Time
N/A
N/A
Target cell operation time of the

3G target cell when occuring the
soft handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
carrier
RSSI
(dBm)
N/A
dBm

(RSSI) of a GSM carrier of 2G
target cell. For details, see 3GPP
TS 45.008.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3330
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RSRP
(dBm)
[-140,-43]
dBm

(RSRP) of LTE target cell. For
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RSRQ
(dB)
[-19.5,-2.5]
dB

(RSRQ) of LTE target cell. For
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3331
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
UL
Channel
Type
DCH
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
FACH
RACH
l SRAN8.1/
GBSS15.1/
RAN 15.1
HSDSCH
EDCH
PCH
l SRAN9.0/
GBSS16.0/
RAN16.0
EFACH
ERACH
l SRAN10.0/
GBSS17.0/
RAN17.0
EPCH
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
DL
Channel
Type
DCH
FACH
N/A

RACH
HSDSCH
EDCH
PCH
EFACH
ERACH
EPCH
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3332
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Target
UL RB
Rate
(kbit/s)
[0,+)
kbit/s

channel handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
DL RB
Rate
(kbit/s)
[0,+)
kbit/s

channel handover.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3333
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Fail
Cause
N/A
N/A
Failure cause.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3334
Nastar
Service Analysis(RAB)
Param
eter
Range
Unit
Description
Supported
Solution
Version
Numbe
r
[1,+)
N/A
Record number of RAB service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnor
mal
N/A
Blank
Whether a servive record is

abnormal.
is abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3335
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Setup
Abnor
mal
N/A

setup is abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Blank

is abnormal.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Setup
Failure
Cause
For details, see

"Appendix:
Exception
Cause
Classification /
Enumeration
Values of
Failure Cause
(UMTS)".
N/A
Cause when RAB setup fails.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3336
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Request
Service
Type
CS_AMR
N/A
Service type of RAB request.
l SRAN8.0/
GBSS15.0/
RAN 15.0
CS_VP
CS_OTHER
l SRAN8.1/
GBSS15.1/
RAN 15.1
PS_GENERAL
PS_HSDPA
l SRAN9.0/
GBSS16.0/
RAN16.0
PS_HSUPA
PS_HSPA
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Request
Time
N/A
N/A
Time when RAB is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3337
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Cell on
RRC
Request
N/A
N/A
Cell when RAB is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Setup
Time
N/A
N/A
Time of RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3338
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Best
Cell on
RAB
Setup
N/A
N/A
Best cell on RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Serving
Cell on
RAB
Setup
N/A
N/A
Serving cell on RAB setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3339
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Peer
Informa
tion
N/A
N/A
Peer information.
l SRAN8.0/
GBSS15.0/
RAN 15.0

it displays "Peer MSISDN".
it displays N/A.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
MultiRAB
Informa
tion on
RAB
Setup
1CS
1CS + 1PS
N/A
Multi-RAB Information on RAB

setup.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
...
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3340
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Release
Abnor
mal
N/A

release is abnormal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Blank

that "Single-RAB Abnormal
Release Indicator" or "MultipleRAB Abnormal Release Indicator"
is YES.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Release
Failure
Cause
For details, see

"Appendix:
Exception
Cause
Classification /
Enumeration
Values of
Failure Cause
(UMTS)".
N/A
Cause of RAB release failure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3341
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Discon
nect
Cause
For details, see

3GPP.
N/A
Cause of the call is disconnected,

that is the cause value of NAS
Disconnect message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The value is valid only on RAB CS

domain.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP
Deactiv
e Cause
For details, see

3GPP.
N/A
Cause of the PDP is deactive, that is

the cause value of Deactivate PDP
context request message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
The value is valid only on RAB PS

domain.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3342
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Release
Time
N/A
N/A
Time on RAB release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Best
Cell
Before
RAB
Release
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3343
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Serving
Cell
Before
RAB
Release
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
MultiRAB
Informa
tion on
RAB
Release
1CS
1CS + 1PS
N/A
Multi-RAB information on RAB

release.
1CS + 2PS
1CS + 3PS
2CS
2CS + 1PS
2CS + 2PS
1PS
2PS
3PS
4PS
...
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3344
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
RAB
Setup
Delay
[0,+)
Seco
nd
RAB setup delay = Time when RAB

setup completes - Time when RAB
setup is requested.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RAB
Duratio
n
[0,+)
Seco
nd
RAB duration = Time when RAB is

released - Time when RAB setup
completes
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3345
Nastar
Param
eter
Range
Unit
Description
Service
Duratio
n
[0,+)
Seco
nd
Service duration.
Supported
Solution
Version
l SRAN8.0/
GBSS15.0/
RAN 15.0
it displays the service duration (that
is call time).
l SRAN8.1/
GBSS15.1/
RAN 15.1
involved).
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Uplink
Throug
hput
[0,+)
Byte
Total uplink throughput.

involved).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3346
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Total
Uplink
Transm
ission
Duratio
n
[0,+)
Seco
nd
Total uplink transmission duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0

involved).
duration on uplink of RAB process.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Averag
e
Uplink
Throug
hput
[0,+)
kbit/s
Average uplink throughput.

involved).
uplink throughput/Total uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3347
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Overlo
w
Averag
e
Uplink
Throug
hput
Yes
N/A
If "Average Uplink Throughput" is

smaller than "Average Uplink
uplink throughput is too small.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Downli
nk
Throug
hput
[0,+)
Byte
Total downlink throughput.

involved).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3348
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Total
Downli
nk
Transm
ission
Duratio
n
[0,+)
Seco
nd
Total downlink transmission

duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0

involved).
duration on downlink of RAB
process.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Averag
e
Downli
nk
Throug
hput
[0,+)
kbit/s
Average downlink throughput.

involved).
Total downlink throughput/Total
downlink transmission duration
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3349
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Overlo
w
Averag
e
Downli
nk
Throug
hput
Yes
N/A
If "Average Downlink Throughput"

is smaller than "Average Downlink
downlink throughput is too small.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

(GSM)
This section describes the parameters for GSM complaint analysis support.
Parameters for Viewing GSM Complaint Analysis Support Results - RAN CS

This section describes the parameters for querying GSM CS complaint analysis support results.
You can refer to the description when querying GSM CS complaint analysis support results.
Issue 03 (2015-07-30)

3350
Nastar
Summary
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Serial
Num
ber
[1,2^31-1)
N/A

number is the key word of a
CHR by which you can
identify this unique CHR. It
is also an internal identifier
provided by Nastar.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Comb
ined
N/A
N/A
Whether a CHR is a
combined one.
By Nastar, information about
a call is obtained from both
the mobile-originated BSC
and the mobile-terminated
BSC and then is combined
into one CHR. A CHR is a
combined one if a yellow
icon is displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3351
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Status
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

exclamation mark is
displayed.
The cause type of a call is
Other and the exception
status of the call is unknown
if a yellow question mark is
displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3352
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Abno
rmal
Cause
For details, see

"Appendix: Exception
Cause Classification / Key
Signaling (GSM)".
N/A

carried in an Access Request
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
NOTE
l SRAN8.1/
GBSS15.1/
RAN 15.1
l The HQIs after the call

setup is successful are only
counted in the abnormal
cause. Short call-related
counters in raw CHRs to be
combined are for reference
only, and do not affect the
exception cause results in
combined CHRs.
l For combined CHRs, the
voice quality problem
counters (excluding
average counters) are
measured based on the subCHRs 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 subCHRs 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.
Issue 03 (2015-07-30)

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3353
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Netw
ork
GSM-CS, GSM-PS
N/A
Network that a VIP

subscriber accesses to
initiate a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3354
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Acces
s
Cause

subscriber
(AC_ORIGIN_CALL_N
O_SMS)
N/A
Cause of a signaling access.
l SRAN8.0/
GBSS15.0/
RAN 15.0
SMS message from a

subscriber
(AC_ORIGIN_CALL_S
MS)
Answer to paging
(AC_ANSWER_TO_PA
GING)
Call re-setup
(AC_CALL_RE_ESTABLISH)
Emergency call
(AC_EMERGENCY_CA
LL)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Location update
(AC_LOCATION_UPDATE)
IMSI detachment
(AC_IMSI_DETACH)
Data service
(AC_PACKET_CALL)
LMU service
(AC_LMU_ESTABLISH)
SS service
(AC_SS_ESTABLISH)
VGCS service
(AC_VGCS_ESTABLISH)
VBS service
(AC_VBCS_ESTABLISH)
LCS service
(AC_LCS_ESTABLISH)
Any other service
(AC_RESERVED)
Issue 03 (2015-07-30)

3355
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
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_INDICATION)
VGCS access
(AC_VGCS_VBS_VPCS
)
subscriber
(AC_ANSWER_TO_PA
GING_CALL)
SMS message from a
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)
Issue 03 (2015-07-30)

3356
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Start
Time
N/A
N/A
Signaling start time for a call,

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acces
s Cell
1 to 64 characters
N/A

MS sends the Channel
Request message.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1

OPC is the originating
signaling point configured
on the BSC side.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3357
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
End
Time
N/A
N/A
Signaling end time for a call,
l SRAN8.0/
GBSS15.0/
RAN 15.0

message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Relea
se
Cell
1 to 64 characters
N/A

MS receives the Channel
Release message.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3358
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
User
ID:Al
ias
N/A
N/A

task.
l SRAN8.0/
GBSS15.0/
RAN 15.0

task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMSI
N/A
N/A
subscriber.
can view the IMSI
information.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3359
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
IMEI
-TAC
00000000-99999999
N/A
allocation code (IMSI-TAC)
of a VIP subscriber, which is
the first eight digits in the
IMEI of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Mode
l
N/A
N/A
Type of a MS.
You can obtain the IMEITACs of the UE from the MS
type management function.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3360
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Peer
MSIS
DN
N/A
N/A

ISDN number (MSISDN) of
a peer subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Durat
ion
[0,+)
Sec
ond
Service duration covering

the call duration and the
signaling setup duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Service duration = End time

- Start time
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3361
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
CS
Servi
ce
Durat
ion
[0,+)
Sec
ond
Call duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Call duration = Time stamp

of the Disconnect message Time stamp of the Connect
Acknowledge message
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.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3362
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
Call
Setup
Resul
t

setup:
N/A

setup or an abnormal call
setup.
l SRAN8.0/
GBSS15.0/
RAN 15.0
1. Normal: The called

subscriber receives the
Connect ACK message
and proper call
communication is
established between the
calling and called
subscribers.
2. The calling subscriber
message and termination
of the call is triggered by
the peer subscriber.
The call setup result is

displayed in the following
format: Call Release Result/
Cause of Abnormal Call
Release/Sub-Cause of
Abnormal Call Release.
(You can obtain the
preceding three parameters
in the Call Release
Information window.)
3. Connection is released
due to an outgoing interBSC handover.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

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
5. The traffic channel is
6. The call setup duration
threshold.
7. The BSS rejects the
immediate assignment
request.
8. The BSC releases
channel resources.
9. The MSC releases
channel resources
abnormally.
Issue 03 (2015-07-30)

3363
Nastar
Para
mete
r
Range
Uni
t
Description
Supported
Solution
Version
N/A

release or an abnormal call
release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
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 interBSC handover fails.
Call
Relea
se
Resul
t

release:
1. Normal: The subscriber
message and starts
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.
handover or inter-RAT
handover is triggered and
completed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

release of traffic channel
during a call:
handover fails.
2. An intra-BSC handover
fails.
3. The BSC releases
channel resources.
4. The MSC releases
channel resources.
Issue 03 (2015-07-30)

3364
Nastar
User Information
Parame
ter
Range
Unit
Description
Supported Solution
Version
User
ID:Alias
N/A
N/A

task.
l SRAN8.0/
GBSS15.0/RAN
15.0

task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
IMSI
N/A
N/A
subscriber.
can view the IMSI
information.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

3365
Nastar
Parame
ter
Range
Unit
Description
Supported Solution
Version
IMEITAC
00000000-9
9999999
N/A

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Model
N/A
N/A

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
MS
Capabili
ty
N/A
N/A
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

3366
Nastar
Parame
ter
Range
Unit
Description
Supported Solution
Version
>Suppor
t
UtranFD
D
Yes
N/A

UtranFDD.
l SRAN8.0/
GBSS15.0/RAN
15.0
No
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
>Suppor
t
UtranT
DD
Yes
N/A
No

UtranTDD.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
>Suppor
t
VAMO
S
Yes
No
N/A

VAMOS.
VAMOS, voice services
over adaptive multi-user
channels on one slot.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

3367
Nastar
Parame
ter
Range
Unit
Description
Supported Solution
Version
>Suppor
t U900
Frequen
cy Band
Yes
N/A

U900.
l SRAN8.0/
GBSS15.0/RAN
15.0
No
That is, whether a MS

supports accessing to the 3G
network using the 900 MHz/
850 MHz band of the 2G
network.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Peer
MSISD
N
N/A
N/A
Refer to "MSISDN" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/RAN16.0
l SRAN10.0/
GBSS17.0/RAN17.0
l SRAN10.1/
GBSS17.1/RAN17.1
l SRAN11.0/
GBSS18.0/RAN18.0
Issue 03 (2015-07-30)

3368
Nastar
Call Access Information

Parame
ter
Range
Unit
Description
Supported
Solution Version
Start
Time
N/A
N/A
Refer to "Start Time" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Cell
1 to 64
characters
N/A
Refer to "Access Cell" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3369
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Access
Carrier
[0,71]
N/A

namely, the number of the carrier
frequency.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Channel
[0,7]
N/A
Information about the channel

through which a MS sends a
namely, the number of the
channel.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3370
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Access
Cause
N/A
N/A
Cause carried in an access

request message.
l SRAN8.0/
GBSS15.0/RAN
15.0
See Access Type in General

Evaluation.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Flag
(Intersystem/
Intrasystem)
Intersystem
Intrasystem
N/A

business is accessed from intrasystem or from inter-system.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3371
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Access
Flag
(MOC/
MTC)
MOC
N/A

business is accessed by MTC or
MOC.
l SRAN8.0/
GBSS15.0/RAN
15.0
MTC
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Flag
(SMS/
Voice)
SMS
Voice
N/A

business is accessed by SMS or
Voice.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3372
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Call
Setup
Result
N/A
N/A

l SRAN8.0/
GBSS15.0/RAN
15.0
See the level-1 cause, Call Setup

Result, in Call Setup Result/
Cause of Abnormal Call Setup/
Sub-Cause of Abnormal Call
Setup in General Evaluation.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cause of
abnorma
l call
setup
N/A
N/A

access for a call.
Abnormal Call Setup, in Call
Evaluation.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3373
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Subcaus
e of
abnorma
l call
setup
N/A
N/A

signaling access for a call.
l SRAN8.0/
GBSS15.0/RAN
15.0

of Abnormal Call Setup, in Call
Evaluation.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Delay
Estimati
on
N/A
N/A
Access delay estimation when

the UE accesses the network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3374
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>ASSIG
NMENT
COMPL
ETE
Message
Timesta
mp
N/A
N/A
Time when the assignment is

finished after initiating a call and
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Access
Delay
[0,+)
Secon
d
Access delay time of the service.

Access Delay = Time of
ASSIGNMENT COMPLETE Time of CHANNEL REQUEST
="ASSIGNMENT COMPLETE
Message Timestamp"-"Start
Time"
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3375
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>Overlo
ng
Access
Delay
Yes
N/A

overlong access delay is
occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
No
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Alertin
g Time
N/A
N/A

hears the alerting after initiating
a call.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3376
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>Call
Complet
ion
Delay
(Alertin
g)
[0,+)
Secon
d

service.
l SRAN8.0/
GBSS15.0/RAN
15.0
Call Completion Delay(Alerting)

= Time of ALERTING - Time of
CHANNEL REQUEST
=Alerting Time - Start Time
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Overlo
ng Call
Complet
ion
Delay
(Alertin
g)
Yes
No
N/A

(Alerting) is occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3377
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>Connec
t
Acknow
ledge
Time
N/A
N/A

hears the voice of the peer
subscriber after initiating a call.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Call
Complet
ion
Delay
(Connec
t Ack)
[0,+)
Secon
d

service.
Call Completion Delay(Connect
Ack) = Time of CONNECK
ACK - Time of CHANNEL
REQUES REQUEST
=Connect Acknowledge Time Start Time
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3378
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>Overlo
ng Call
Complet
ion
Delay
(Connec
t Ack)
Yes
N/A

(Connect Ack) is occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
No
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measure
ment
Informat
ion On
Access
N/A
N/A
Measurement information when

a MS accesses to the network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3379
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>TA
[0,63]
N/A
Value of the TA when a MS

accesses to the network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Abnor
mal TA
Yes
No
N/A
Whether the abnormal that TA is

too large when accessing to the
network is occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3380
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
>RACH
Level
[-110,-47]
dBm
Value of the RACH level when a

MS accesses to the network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Abnor
mal
RACH
Level
Yes
No
N/A
Whether the abnormal that

RACH Level is too small is
occurred.
l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3381
Nastar
Call Release Information

Parame
ter
Range
Unit
Description
Supported
Solution Version
End
Time
N/A
N/A
Refer to "End Time" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Duration
[0,+)
Secon
d
Refer to "Duration" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3382
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Release
Cell
1 to 64
characters
N/A
Refer to "Release Cell" in the

Summary area.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Release
Carrier
N/A
N/A

signaling release message.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3383
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Call
Release
Result
N/A
N/A

l SRAN8.0/
GBSS15.0/RAN
15.0
See the level-1 cause, Call

Release Result, in Call Release
Result/Cause of Abnormal Call
Release/Sub-Cause of Abnormal
Call Release in General
Evaluation.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Cause of
abnorma
l call
completi
on
N/A
N/A

release during a call.
Abnormal Call Release, in Call
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3384
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Subcaus
e of
abnorma
l call
completi
on
N/A
N/A

signaling release during a call.
l SRAN8.0/
GBSS15.0/RAN
15.0

of Abnormal Call Release, in
Call Release Result/Cause of
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Location
Group
Number
N/A
N/A
Refer to the location group where

a terminal is located when the
signaling is released. This
parameter is valid only for the
multi-RRU serving a cell feature.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3385
Nastar
CS Service Information
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Service
Process
Delay
Estimati
on
N/A
N/A
Delay estimation for service

process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>IntraBSC
Channel
Release
Timesta
mp
N/A
N/A
Timestamp of intra-BSC channel

release.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3386
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Calling
Duration
[0,+)
Secon
d
Calling Duration = Time of

DISCONNECT - Time of
CONNECT ACK
l SRAN8.0/
GBSS15.0/
RAN 15.0
=Intra-BSC Channel Release

Timestamp - CONNECT ACK
Timestamp
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Short
Call
Yes
No
N/A
Whether the abnormal of short call

is occurred.
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3387
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Service
Quality
Estimati
on for
Service
Process
N/A
N/A
Service quality estimation for

service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)
>Time
of Up
Single
Pass
N/A
N/A
Time of uplink one-way audio
SRAN10.1/
GBSS17.1/
RAN17.1
>Time
of Down
Single
Pass
N/A
N/A
Time of downlink one-way audio
SRAN10.1/
GBSS17.1/
RAN17.1

3388
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Oneway
Audio
During a
Call
Yes
N/A
Whether uplink one-way audio

l SRAN8.0/
GBSS15.0/
RAN 15.0
No

and A interfaces.
Principle for detecting uplink oneway 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
primary uplink one-way audio
occurs, and starts the mechanism for
primary uplink one-way audio.
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
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3389
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Downli
nk Oneway
Audio
During a
Call
Yes
N/A
Whether downlink one-way audio

l SRAN8.0/
GBSS15.0/
RAN 15.0
No

and A interfaces.
one-way audio: The DSP in the
DTRU of the BTS performs
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
primary downlink one-way audio.
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, oneway audio occurs on the downlink
voice channel.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3390
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Call
Crosstal
k
Yes
N/A
Whether uplink crosstalk occurs

during a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No

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
period, uplink crosstalk occurs.
>Downli
nk Call
Crosstal
k
Yes
No
N/A
Whether downlink crosstalk occurs

during a call.
the unique identifier of a call into
the free bits of uplink voice TRAU
frames. The DSP of the BTS
period, downlink crosstalk occurs.
Issue 03 (2015-07-30)

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3391
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Noise
Yes
N/A
Whether uplink noise occurs during

a call, which is detected by the
device.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Downli
nk Noise
Yes
No
N/A
Whether downlink noise occurs

during a call, which is detected by
the device.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3392
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Call HQI
[0.00,100.00
]
Average value for the uplink high

quality indicators (HQIs) of call
l SRAN8.0/
GBSS15.0/
RAN 15.0

call and is measured on a 0-to-7
scale. Level 0 indicates the best
quality.
V900R008:
>Bad
Uplink
HQI
Yes
No
N/A

HQI is occurred of call setups that
include the HQIs before and after
creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3393
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Downli
nk Call
HQI
[0.00,100.00
]

HQIs of call setups that include the
HQIs before and after the call setup
is successful.
l SRAN8.0/
GBSS15.0/
RAN 15.0

V900R008:
>Bad
Downlin
k HQI
Yes
No
N/A

downlink HQI is occurred of call
creating tasks.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3394
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Call VQI
[0.00,5.00]
N/A
Average value for the uplink voice

quality indicators (VQIs) of
l SRAN8.0/
GBSS15.0/
RAN 15.0

voice quality is.
l SRAN8.1/
GBSS15.1/
RAN 15.1
Average value for the uplink VQIs

of successful call setups =
Aggregated value of uplink VQIs/
Total number of uplink VQI tests
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Bad
Uplink
VQI
Yes
No
N/A

VQI is occurred.
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3395
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Downli
nk Call
VQI
[0.00,5.00]
N/A

voice quality indicators (VQIs) of
l SRAN8.0/
GBSS15.0/
RAN 15.0

voice quality is.
l SRAN8.1/
GBSS15.1/
RAN 15.1

VQIs of successful call setups =
Aggregated value of downlink
VQIs/Total number of downlink
VQI tests
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Bad
Downlin
k VQI
Yes
No
N/A

downlink VQI is occurred.
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3396
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Measure
ment
Informat
ion On
Service
Process
N/A
N/A
service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Averag
e Uplink
Level
[-110,-47]
dBm
Average uplink level on service

process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3397
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Averag
e
Downlin
k Level
[-110,-47]
dBm
Average downlink level on service

process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Averag
e Uplink
Quality
[0,7]
N/A
Average uplink quality on service

process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3398
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
>Averag
e
Downlin
k
Quality
[0,7]
N/A
Average downlink quality on

service process.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Parame
ter
Range
Unit
Description
Supported
Solution Version
Number
[1,+)
N/A
Unique number for the signaling

message that a VIP subscriber
sends and receives during the
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3399
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Signalin
g Time
N/A
N/A

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signalin
g Direct
Uplink
Downlink
N/A
Direction in which a signaling

message is sent or received.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3400
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Signalin
g Type
N/A
N/A
Type of a signaling message

transmitted on the A or Abis
interface during the signaling
procedure. For example, the
parameter can be a Channel
Request message.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signalin
g
Content
N/A
N/A

You can obtain the content of a
signaling message by viewing
the related tree structure.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3401
Nastar
Measurement Information Before Call Release

Parame
ter
Range
Unit
Description
Supported
Solution Version
Number
[1,+)
N/A
Unique number of a signaling

message carrying a
measurement report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measure
ment
Time
N/A
N/A
Time when a measurement

report is submitted.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3402
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Serial
Number
N/A
N/A
Serial number for a reported

measurement report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measure
ment
Object
Type
Server
Nbr1~6
N/A
Type of a measurement object,

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
For example, if the parameter is

Server, the measurement object
is a serving cell; if the parameter
is Nbr1, the measurement object
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3403
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Measure
ment
Object
N/A
N/A

report.
l SRAN8.0/
GBSS15.0/RAN
15.0

BSC: Name of the cell.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BCCH
[0,1023]
N/A
Broadcast control channel

(BCCH) of a neighboring cell,
report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3404
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
BSIC
[0,77]
N/A
Base transceiver Station Identity

Code (BSIC) of a neighboring
report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TA
[0,63]
N/A
TA of a serving cell, reported in

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3405
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
RxLevel
(Downli
nk)
[-110,-47]
dBm
Downlink RxLevel of a serving

cell and that of a neighboring
report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RxLevel
(Uplink)
[-110,-47]
dBm
Uplink RxLevel of a serving

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3406
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
RxQualit
y
(Downli
nk)
[0,7]
N/A
Downlink RxQuality of a
serving cell, reported in a
measurement report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RxQualit
y
(Uplink)
[0,7]
N/A
Uplink RxQuality of a serving

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3407
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
BTS
Power
[0,15]
N/A
BTS power of a serving cell,

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
MS
Power
[0,31]
N/A
MS power of a serving cell,

report.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3408
Nastar
Mobility Analysis
Parame
ter
Range
Unit
Description
Supported
Solution Version
Number
[1,+)
Numb
er
Number for a handover triggered

during a call.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
N/A
N/A
Whether a record indicates an

abnormal handover.
The record indicates an
abnormal handover if a red
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3409
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Abnorm
al Cause
Communicat
ion resumes
on the
original
channel after
a handover
failure
N/A
Whether a handover succeeds,

and the cause of a handover
failure.
l SRAN8.0/
GBSS15.0/RAN
15.0
The cause is displayed as

Normal if a handover succeeds.
l SRAN8.1/
GBSS15.1/RAN
15.1
Possible causes of a handover

failure include the following:
communication resumes on the
original channel after a handover
failure; the BSC releases
channel resources; the MSC is
faulty.
the BSC
releases
channel
resources
the MSC is
faulty
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Handove
r Type
Intra-BSC
handover
N/A
Type of a handover
Outgoing
cell handover
Incoming
inter-BSC
handover
Outgoing
inter-BSC
handover
Outgoing
inter-RAT
handover
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3410
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Initiatin
g Time
N/A
N/A
Time when a handover is

initiated,
l SRAN8.0/
GBSS15.0/RAN
15.0
namely, the time when the BSC

sends the Handover CMD
message.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Interval
[0,+)
N/A
Duration = End time - Start time
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3411
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Overlon
g
Interval
Yes
N/A
The first case: "Handover Type"

is "Outgoing inter-BSC
handover"
l SRAN8.0/
GBSS15.0/RAN
15.0

not, it displays "No".
l SRAN8.1/
GBSS15.1/RAN
15.1
No
The second case: "Handover

Type" is "Outgoing inter-RAT
handover"
"Outgoing System Handover
not, it displays "No". The other
case: displays null.
Interval" and "Outgoing System
Handover Interval" is set when
creating tasks.
End
Time
N/A
N/A
End time of a handover.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3412
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Handove
r
Triggeri
ng Cause
N/A
N/A
Cause of a handover.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Source
cell
N/A
N/A
Name of the source cell to be

handed over.
displayed if they are not
available.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0

OPC is the originating signaling
l SRAN10.1/
point configured on the BSC
GBSS17.1/
side.
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3413
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution Version
Source
Location
Group
No.
N/A
N/A
Number of source location

group.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
cell
N/A
N/A
Name of the target cell to which

a handover is to be performed.
data.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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 03 (2015-07-30)

3414
Nastar
Summary
Param
eter
Range
Unit
Description
Supported
Solution
Version
Serial
Number
[1,2^31-1)
N/A

number is the key word of a CHR
by which you can identify this
unique CHR. It is also an internal
identifier provided by Nastar.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Combin
ed
N/A
N/A

one.
mobile-originated BSC and the
mobile-terminated BSC and then
is combined into one CHR. A
CHR is a combined one if a
yellow icon is displayed.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3415
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Status
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0

The cause type of a call is Other
and the exception status of the
call is unknown if a yellow
question mark is displayed.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al Cause
For details, see

"Appendix:
Exception Cause
Classification /
Key Signaling
(GSM)".
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3416
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Networ
k
GSM-CS, GSMPS
N/A
Network that a VIP subscriber

accesses to initiate a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Start
Time
N/A
N/A
Signaling access time for a call,

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3417
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Access
Cell
1 to 64 characters
N/A

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0

displayed
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
End
Time
N/A
N/A
Signaling release time for a call,

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3418
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Release
Cell
1 to 64 characters
N/A

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0

data. The names are not display
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
User
ID:Alia
s
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3419
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMEITAC
00000000-999999
99
N/A

(IMSI-TAC) of a VIP subscriber,
which is the first eight digits in
the IMEI of a UE.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3420
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Model
N/A
N/A
Type of a MS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
You can obtain the IMEI-TACs

of the UE from the MS type
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Peer
MSISD
N
N/A
N/A

peer subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3421
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Duratio
n
[0,+)
Seco
nd
Service duration covering the

call duration and the signaling
setup duration.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Service duration = End time Start time
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3422
Nastar
User Information
Param
eter
Range
Unit
Description
Supported
Solution
Version
User
ID:Alia
s
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
IMSI
N/A
N/A
subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3423
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
IMEITAC
00000000-99999
999
N/A

Summary area.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Model
N/A
N/A

Summary area.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3424
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
MS
Capabil
ity
N/A
N/A
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt GPRS
Support
Unsupport
N/A

GPRS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3425
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt GPRS
MultiSlot
Class
N/A
N/A
GPRS Multislot Class of a

Terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt
EGPRS
Support
Unsupport
N/A

EGPRS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3426
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt
EGPRS
MultiSlot
Class
N/A
N/A
EGPRS Multislot Class of a

Terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt 900M
E
Frequen
cy Band
Support
Unsupport
N/A

E-GSM900 band.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3427
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt
1800M
Frequen
cy Band
Support
N/A

E-GSM1800 band.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Unsupport
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt G-TD
DualMode
Support
Unsupport
N/A

both GSM and TD-SCDMA.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3428
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt G-U
DualMode
Support
N/A

both GSM and UMTS.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Unsupport
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Suppo
rt DTM
Support
Unsupport
N/A

DTM.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3429
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Suppo
rt PS
Handov
er
Support
N/A

handovers in the PS domain.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Unsupport
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Insuffic
ient
Termin
al
Capabil
ity
Yes
No
N/A
The capability of a Terminal is

insufficient in the case of the
following:
l SRAN8.0/
GBSS15.0/
RAN 15.0
The Terminal supports GPRS

but not EGPRS.
l SRAN8.1/
GBSS15.1/
RAN 15.1
The Terminal supports EGPRS

but the EGPRS multislot class is
below 10.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3430
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
Subscri
ber
Registra
tion
Paramet
er
N/A
N/A
Parameters related to the service

that a VIP subscriber subscribes
to when opening an account.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Reliab
ility
Level
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3431
Nastar
Param
eter
Range
Unit
Description
Supported
Solution
Version
>Subscr
iption
Rate
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
Subscri
ber
Registra
tion
Yes
No
N/A
An account-opening exception
occurs in the case of the
following:
l SRAN8.0/
GBSS15.0/
RAN 15.0
The reliability class of a VIP

subscriber is not 3, namely, the
reliability class is not the RLC
acknowledged mode.
l SRAN8.1/
GBSS15.1/
RAN 15.1
The subscription rate is lower

than the predefined exception
threshold (which is set by
engineers when creating tasks).
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3432
Nastar
Peer Information
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Number
of
Server
Applica
tions
N/A
N/A
Total number of the server applications that

a VIP subscriber accesses when attempting
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
List of
Servers
and
Applica
tions
N/A
N/A
The list of applications that the server

supports.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3433
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>IP
Address
N/A
N/A
IP address of the server that a VIP subscriber

service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Server
Name
N/A
N/A
Name of the server that a VIP subscriber

service. You can obtain the name of a server
by choosing System Function > Data
Service Server Management in the
navigation tree of Nastar based on the IP
address of the serve
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3434
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Port
[0,65
535)
N/A
Port number of the server that a VIP

a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Applic
ation
N/A
N/A
name of the application that a VIP

a data service. You can obtain the name of
an application by choosing System Function
> Data Service Server Management in the
navigation tree of Nastar based on the port
number
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3435
Nastar
Access and Release Information

Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Start
Time
N/A
N/A
Start time for a VIP subscriber to use a data

service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
TA
upon
Access
[0,63
]
N/A
Value of the TA when a Terminal sends the

Channel Request message for a VIP subscriber
to use a data service. It indicates the distance
between the Terminal and its serving cell to
some extent.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3436
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
RxQual
ity upon
Access
[0,7]
N/A
Value of the RxQuality when a Terminal sends

the Channel Request message for a VIP
subscriber to use a data service. It indicates the
signal quality during the initial access of the
Terminal.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
GMSK
MEAN
BEP
upon
Access
[0,31
]
N/A
Information about the GMSK MEAN BEP

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3437
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
8PSK
MEAN
BEP
upon
Access
[0,31
]
N/A
Information about the 8PSK MEAN BEP

message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
Cell
1 to
64
chara
cters
N/A
Name of the cell in which a MS sends the

format: BSC Name: Cell Name (Cell ID). You
can obtain the names of the BSC and the cell
from the configuration data. The names are not
displayed
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3438
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
End
Time
N/A
N/A
Time when a VIP subscriber releases a data

service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Service
Duratio
n
[0,
+)
Sec
ond
Duration of the data service used by a VIP

subscriber.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3439
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Release
Cell
1 to
64
chara
cters
N/A
Cell in which a VIP subscriber releases a data

service. In a GSM network, a cell reselection
always triggers the release of data service.
Therefore, the release cell is always the access
cell.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink
Signalin
g
Access
Times
[0,
+)
Nu
mbe
r

(uplink CCCH) during the whole process for
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3440
Nastar
Mobility Manager Information

Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Attach
Request
Times
[0,
+)
Nu
mbe
r
Number of the Attach Request messages that

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Attach
Accept
Times
[0,
+)
Nu
mbe
r
Number of the Attach Accept messages that a

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3441
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Attach
Reject
Times
[0,
+)
Nu
mbe
r
Number of the Attach Reject messages that a

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Detach
Request
Times
[0,
+)
Nu
mbe
r
Number of the Detach Request messages that

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3442
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
Detach
Accept
Times
[0,
+)
Nu
mbe
r
Number of the Detach Accept messages that a

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP
Active
Request
Times
[0,
+)
Nu
mbe
r
Number of the PDP Active Request messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3443
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
PDP
Active
Accept
Times
[0,
+)
Nu
mbe
r
Number of the PDP Active Accept messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
PDP
Active
Reject
Times
[0,
+)
Nu
mbe
r
Number of the PDP Active Reject messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3444
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
RA
Update
Request
Times
[0,
+)
Nu
mbe
r
Number of the RA Update Request messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RA
Update
Accept
Times
[0,
+)
Nu
mbe
r
Number of the RA Update Accept messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3445
Nastar
Param
eter
Ran
ge
Uni
t
Description
Supported
Solution
Version
RA
Update
Reject
Times
[0,
+)
Nu
mbe
r
Number of the RA Update Reject messages

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Suspen
d Times
[0,
+)
Nu
mbe
r
Number of Suspends during the whole process

for a VIP subscriber to use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3446
Nastar
RAN Abnormal Information

Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Times
of
Downli
nk TBF
Setup
Failure
[0,
+)
Num
ber
Number of TBF setup failures on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
s of
Downli
nk TBF
Setup
Failure
N/A
N/A
Cause of a TBF setup failure on the downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3447
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Carrie
r Index
N/A
N/A
Carrier of a TBF setup failure on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BCCH
N/A
N/A
BCCH of a TBF setup failure on the

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3448
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Times
of
Uplink
TBF
Setup
Failure
N/A
Num
ber
Number of TBF setup failures on the uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
s of
Uplink
TBF
Setup
Failure
N/A
N/A
Cause of a TBF setup failure on the uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3449
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Carrie
r Index
N/A
N/A
Carrier of a TBF setup failure on the uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BCCH
N/A
N/A
BCCH of a TBF setup failure on the uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3450
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Times
of
Abnor
mal
Downli
nk TBF
Release
[0,
+)
Num
ber

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
s of
Abnor
mal
Downli
nk TBF
Release
N/A
N/A

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3451
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Carrie
r Index
N/A
N/A

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BCCH
N/A
N/A

downlink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3452
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Times
of
Abnor
mal
Uplink
TBF
Release
[0,
+)
Num
ber

uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Cause
s of
Abnor
mal
Uplink
TBF
Release
N/A
N/A

uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3453
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Carrie
r Index
N/A
N/A

uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>BCCH
N/A
N/A

uplink.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3454
Nastar
Latency Sensitivity Information

Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Downli
nk PDU
N/A
N/A
Information about the downlink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Sent
Bytes
[0,
+)
Byte

downlink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3455
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Maxi
mum
Duratio
n on
Sendin
g PDU
[0,
+)
Seco
nd

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Total
Duratio
n on
Sendin
g PDU
[0,
+)
Seco
nd

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3456
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Sent
Count
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Avera
ge
Duratio
n on
Sendin
g PDU
[0,
+)
Seco
nd

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3457
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Sendi
ng
Timeou
t Times
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

threshold.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Uplink
PDU
N/A
N/A
Information about the uplink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3458
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Recei
ved
Bytes
[0,
+)
Byte

uplink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Maxi
mum
Duratio
n on
Receivi
ng PDU
[0,
+)
Seco
nd

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3459
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Total
Duratio
n on
Receivi
ng PDU
[0,
+)
Seco
nd

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Recei
ved
Count
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3460
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Avera
ge
Duratio
n on
Receivi
ng PDU
[0,
+)
Seco
nd

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Recei
ving
Timeou
t Times
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

threshold.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3461
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Uplink/
Downli
nk PDU
N/A
N/A
Information about the uplink and downlink

PDUs, namely, the information about the
incoming and outgoing data transmission on
the PDU GB interfaces.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Maxi
mum
Interval
Duratio
n
[0,
+)
Seco
nd
Maximum interval for data transmission

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3462
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Total
Interval
Duratio
n
[0,
+)
Seco
nd
Aggregated interval of all the intervals for

data transmission between every two datatransmission time points on the uplink and
downlink PDUs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Numb
er of
Interval
s
[0,
+)
Num
ber
Number of times that an interval for data

downlink PDUs is available.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3463
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Avera
ge
Interval
Duratio
n
[0,
+)
Seco
nd
Average interval for data transmission

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Numb
er of
Interval
Timeou
ts
[0,
+)
Num
ber
Number of times that the interval for data

downlink PDUs exceeds the predefined
threshold.
whether the interval for data transmission
between the uplink and downlink PDUs
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3464
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
>Uplin
k Data
Availab
le and
Downli
nk Data
Unavail
able
Occurre
nce
Times
[0,
+)
Num
ber

data but downlink PDU does not.
l SRAN8.0/
GBSS15.0/
RAN 15.0

whether the uplink PDU carries data while
the downlink PDU does not.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Numbe
r of No
Service
Interact
ion
Timeou
t Times
[0,
+)
Num
ber
Number of times that no service interaction

responses.
response to service interaction, and,
larger than the exception threshold 2 for the
service interaction is made indicates a value
of 1; otherwise, it indicates a value of 0.(A =
data but the downlink PDU does not).
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3465
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Numbe
r of
Service
Interact
ion
Timeou
t Times
[0,
+)
Num
ber
Number of exceptions where the response to

service interaction is overdue during the
whole process for a VIP subscriber to use a
data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Number of Number of Interval Timeouts for
data transmission between the uplink and
downlink PDUs.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Averag
e
Duratio
n on
Service
Interact
ion
Respon
se
[0,
+)
Num
ber

interaction during the whole process for a
l SRAN8.0/
GBSS15.0/
RAN 15.0

interaction = Average duration for data
Average duration for data reception by using
the uplink PDU + Average duration for data
downlink PDUs.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3466
Nastar
Param
eter
Rang
e
Unit
Description
Supported
Solution
Version
Overlo
ng
Averag
e
Duratio
n on
Service
Interact
ion
Respon
se
Yes
N/A
Number of exceptions where the average

interaction exceeds the predefined threshold
use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
No
If the average duration for the response to

threshold for the average duration for the
response to service interaction, the average
interaction overlong.
The threshold is set by engineers during
analysis task creation.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3467
Nastar
Speed Sensitivity Information

Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Statistic
s on
Downli
nkRateSensitiv
e
Service
s
N/A
N/A
Information about the statistics on downlink

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>PDU
Bytes
Sent at
Downli
nk
[0,
+)
Byte

downlink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3468
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Durati
on for
Sendin
g PDU
at
Downli
nk
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>PDU
Bytes
Receive
d at
Uplink
[0,
+)
Byte

PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3469
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Down
load
Speed
(kbit/s)
[0,
+)
kbit/s
Average download rate during the whole

l SRAN8.0/
GBSS15.0/
RAN 15.0
Download rate = Number of bytes

transmitted by using the downlink PDU/
Duration for data transmission by using the
downlink PDU
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Low
Downlo
ad
Speed
Yes
No
N/A
Number of low download rate exceptions

use a data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If a download rate is lower than the lower

threshold for download rate,
l SRAN8.1/
GBSS15.1/
RAN 15.1
the download rate is low.

creating tasks.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3470
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Numb
er of
Downli
nk NU
Out-ofOrder
Times
[0,
+)
Num
ber
Number of exceptions where downlink NU

disorder occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Numb
er of
Downli
nk TCP
Out-ofOrder
Times
[0,
+)
Num
ber
Number of exceptions where downlink TCP

disorder occurs during the whole process for
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3471
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Avera
ge
Occupi
ed
Downli
nk Slots
[1,6]
Num
ber
Number of timeslots occupied during

downlink data transmission.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Down
load
MultiSlot
Statisfa
ction
Ratio
[0.00,
100.0
0]
Multislot satisfaction rate on the downlink =

Average number of timeslots occupied by the
downlink/Multislot Class of a Terminal x
100%
Downlink Rate-Sensitive Service/EGDE
Supporting EGPRS.
Supporting GPRS.
Issue 03 (2015-07-30)

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
3472
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Trans
mission
Resour
ces
Require
d for
Code
Request
ed by
Downli
nk
Block
[0,
+)
Num
ber

for the encoding of downlink blocks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Trans
mission
Resour
ces
Used by
Code
Assigne
d to
Downli
nk
Block
[0,
+)
Num
ber

used for the encoding of downlink blocks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3473
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Resou
rce
Statisfa
ction
Ratio of
Downli
nk
Averag
e
SingleSlot
Throug
hput
(%)
[0.00,
100.0
0]

Number of the transmission resources
actually used for the encoding of downlink
blocks/Number of the transmission resources
requested for the encoding of downlink
blocks x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>GPRS
Service
Flag
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3474
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Downli
nk
CS1~4
Blocks/
Valid
Blocks
[0,
+)
Num
ber

CS-4.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Total
Blocks
Sent at
Downli
nk
[0,
+)
Num
ber

downlink
coding schemes
downlink by using CS-1 ++ Number of
the blocks transmitted on the downlink by
using CS-4
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3475
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Total
Valid
Blocks
Sent at
Downli
nk
[0,
+)
Num
ber

on the downlink
l SRAN8.0/
GBSS15.0/
RAN 15.0

the downlink by using CS-1 ++ Number
of the valid blocks transmitted on the
downlink by using CS-4
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Total
Bytes
of Valid
Blocks
Sent at
Downli
nk
Issue 03 (2015-07-30)
[0,
+)
Byte

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1

the downlink by using CS-1 x Number of the
downlink by using CS-4 x Number of the
bytes contained in one valid block
l SRAN9.0/
GBSS16.0/
RAN16.0

TS 44.060-10.2.
l SRAN10.1/
GBSS17.1/
RAN17.1

l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
3476
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Dow
nlink
Retrans
mission
Ratio
[0.00,
100.0
0]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Dow
nlink
Reuse
Ratio
[0.00,
+)
N/A

PDU x Average number of the timeslots
occupied by the downlink/2/Total number of
the blocks transmitted on the downlink
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3477
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>EGDE
Service
Flag
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Downli
nk
MCS1~
9
Blocks/
Valid
Blocks
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3478
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Total
Blocks
Sent at
Downli
nk
[0,
+)
Num
ber

downlink
l SRAN8.0/
GBSS15.0/
RAN 15.0

and coding schemes
downlink by using MCS-1 ++ Number
of the blocks transmitted on the downlink by
using MCS-9
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Total
Valid
Blocks
Sent at
Downli
nk
[0,
+)
Num
ber

on the downlink
the downlink by using MCS-1 ++
downlink by using MCS-9
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3479
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Total
Bytes
of Valid
Blocks
Sent at
Downli
nk
[0,
+)
Byte

l SRAN8.0/
GBSS15.0/
RAN 15.0
>>Dow
nlink
Retrans
mission
Ratio

and coding schemes x Number of the bytes
[0.00,
100.0
0]
l SRAN8.1/
GBSS15.1/
RAN 15.1

the bytes contained in one valid block +
+ Number of the valid blocks transmitted on
the bytes contained in one valid block
l SRAN9.0/
GBSS16.0/
RAN16.0

3GPP TS 44.060-10.3.
l SRAN10.1/
GBSS17.1/
RAN17.1

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3480
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Dow
nlink
Averag
e
GMSK
BEP
[0,31
]
N/A
Average downlink GMSK BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Dow
nlink
Averag
e 8PSK
BEP
[0,31
]
N/A
Average downlink 8PSK BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3481
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Dow
nlink
Averag
e BEP
[0,31
]
N/A
1. If both the average downlink GMSK BEP

and the average downlink 8PSK BEP are
valid,
l SRAN8.0/
GBSS15.0/
RAN 15.0
use the average downlink GMSK BEP with a

higher order.
l SRAN8.1/
GBSS15.1/
RAN 15.1
2. If either the average downlink GMSK BEP

or the average downlink 8PSK BEP is valid,
downlink BEP.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Dow
nlink
Averag
e
SingleSlot
Throug
hput
N/A
kbit/s

namely, the average downlink single-slot
Mapping Table based on the average
downlink BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3482
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Um
Quality
Satisfac
tion
Ratio of
Downli
nk
Averag
e
SingleSlot
Throug
hput
[0.00,
100.0
0]
Um-interface quality satisfaction rate at the

MIN (Average downlink single-slot
throughput/Target single-slot throughput x
100%, 100%)
l SRAN8.0/
GBSS15.0/
RAN 15.0
The target single-slot throughput is a

customized algorithm parameter.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Poor
Transm
ission
Quality
Indicate
d by
Downli
nk
Averag
e
SingleSlot
Throug
hput
Yes
No
N/A
If the average downlink BEP is higher than

the BEP required by the lowest-level coding,
and at the same time, the downlink dataretransmission rate is higher than the upper
threshold for downlink data-retransmission
rate,
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN9.0/
GBSS16.0/
RAN16.0

and the upper threshold for downlink dataretransmission rate are customized algorithm
parameters.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3483
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Dow
nlink
Reuse
Ratio
[0.00,
+)
N/A

PDU x Average number of downlink
timeslots/2/Total number of the blocks
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Statistic
s on
UplinkRateSensitiv
e
Service
s
N/A
N/A
Information about the statistics on uplink

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3484
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>PDU
Bytes
Receive
d at
Uplink
[0,
+)
Byte

PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Durati
on for
Receivi
ng PDU
at
Uplink
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3485
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>PDU
Bytes
Sent at
Downli
nk
[0,
+)
Byte

downlink PDU.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Uploa
d Speed
(kbit/s)
[0,
+)
kbit/s
Average upload rate during the whole process

Upload rate = Number of bytes transmitted
by using the uplink PDU/Duration for data
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3486
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Low
Upload
Speed
Yes
N/A
Number of low upload rate exceptions during

the whole process for a subscriber to use a
data service.
l SRAN8.0/
GBSS15.0/
RAN 15.0
If an upload rate is lower than the lower

threshold for upload rate,
l SRAN8.1/
GBSS15.1/
RAN 15.1
No
the upload rate is low.

creating tasks.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Numb
er of
Uplink
NU
Out-ofOrder
Times
[0,
+)
Num
ber
Number of exceptions where uplink NU

disorder occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3487
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Numb
er of
Uplink
TCP
Out-ofOrder
Times
[0,
+)
Num
ber
Number of exceptions where uplink TCP

disorder occurs.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Avera
ge
Occupi
ed
Uplink
Slots
[1,6]
Num
ber
Number of timeslots occupied during uplink

data transmission.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3488
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Uplin
k MultiSlot
Statisfa
ction
Ratio
[0.00,
100.0
0]
Uplink multislot-satisfaction rate = Average

number of timeslots occupied by the uplink/
Multislot Class of a Terminal x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
Uplink Rate-Sensitive Service/EGDE
Supporting EGPRS.
Supporting GPRS.
>Trans
mission
Resour
ces
Require
d for
Code
Request
ed by
Uplink
Block
[0,
+)
Num
ber

for the encoding of uplink blocks.
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3489
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Trans
mission
Resour
ces
Used by
Code
Assigne
d to
Uplink
Block
[0,
+)
Num
ber

used for the encoding of uplink blocks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Resou
rce
Statisfa
ction
Ratio of
Uplink
Averag
e
SingleSlot
Throug
hput
(%)
[0.00,
100.0
0]

average uplink single-slot throughput
= Number of transmission resources actually
used for the encoding of uplink blocks/
for the encoding of uplink blocks x 100%
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3490
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>Durati
on for
Sendin
g PDU
at
Downli
nk
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Total
Duratio
n for
Sendin
g PDU
at
Downli
nk
[0,
+)
Secon
d

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3491
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>PDUs
Sent at
Downli
nk
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>Timeo
ut
Times
on
sending
PDUs
at
Downli
nk
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0

threshold.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3492
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>GPRS
Service
Flag
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Uplink
CSN
(1~4)
Blocks/
Valid
Blocks
[0,
+)
Num
ber

CS-4.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3493
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Total
Blocks
Receive
d at
Uplink
[0,
+)
Num
ber

uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0

schemes
uplink by using CS-1 ++ Number of the
blocks transmitted on the uplink by using
CS-4
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Total
Valid
Blocks
Receive
d at
Uplink
[0,
+)
Num
ber

on the uplink
the uplink by using CS-1 ++ Number of
the valid blocks transmitted on the uplink by
using CS-4
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3494
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Total
Bytes
of Valid
Blocks
Receive
d at
Uplink
[0,
+)
Byte

l SRAN8.0/
GBSS15.0/
RAN 15.0
>>Upli
nk
SingleSlot
Throug
hput
(Actual
)

schemes x Number of the bytes contained in
one valid block
[0.00,
100.0
0]
kbit/s
l SRAN8.1/
GBSS15.1/
RAN 15.1

the uplink by using CS-1 x Number of the
uplink by using CS-4 x Number of the bytes
l SRAN9.0/
GBSS16.0/
RAN16.0

TS 44.060-10.2.
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3495
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Reuse
Ratio
[0.00,
+)
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>EGDE
Service
Flag
N/A
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3496
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Uplink
MCS1~
9
Blocks/
Valid
Blocks
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Num
ber of
Total
Blocks
Receive
d at
Uplink
[0,
+)
Num
ber

uplink
coding schemes
uplink by using MCS-1 ++ Number of
the blocks transmitted on the uplink by using
MCS-9
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3497
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Num
ber of
Total
Valid
Blocks
Receive
d at
Uplink
[0,
+)
Num
ber

on the uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0

the uplink by using MCS-1 ++ Number
of the valid blocks transmitted on the uplink
by using MCS-9
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Total
Bytes
of Valid
Blocks
Receive
d at
Uplink
Issue 03 (2015-07-30)
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1

the uplink by using MCS-1 x Number of the
uplink by using MCS-9 x Number of the bytes
l SRAN9.0/
GBSS16.0/
RAN16.0

3GPP TS 44.060-10.3.
l SRAN10.1/
GBSS17.1/
RAN17.1

l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN11.0/
GBSS18.0/
RAN18.0
3498
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Receive
Retrans
mission
Rate
(%)
[0.00,
100.0
0]
Uplink data-retransmission rate = Total

uplink/Total number of the blocks
transmitted on the uplink
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Upli
nk
Averag
e
GMSK
BEP
[0,31
]
N/A
Average uplink GMSK BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3499
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Averag
e 8PSK
BEP
[0,31
]
N/A
Average uplink 8PSK BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Upli
nk
Averag
e BEP
[0,31
]
N/A
1. If both the average uplink GMSK BEP and

the average uplink 8PSK BEP are valid,
use the average uplink GMSK BEP with a
higher order.
2. If either the average uplink GMSK BEP or
the average uplink 8PSK BEP is valid,
uplink BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3500
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Averag
e
SingleSlot
Throug
hput
Require
d for
Um
Quality
[0.00,
100.0
0]
kbit/s
Average uplink single-slot throughput

required to achieve a specific quality level on
the Um interface.
l SRAN8.0/
GBSS15.0/
RAN 15.0

namely, the average uplink single-slot
Mapping Table based on the average uplink
BEP.
l SRAN8.1/
GBSS15.1/
RAN 15.1

l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3501
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Um
Quality
Unsatis
faction
Times
of
Downli
nk
Averag
e
SingleSlot
Throug
hput
[0,
+)
Num
ber
1 Obtain a coding scheme from BEP-Coding

Scheme-Rate Mapping Table based on the
average uplink BEP. Then record it as
Average coding scheme_Average uplink
BEP.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Obtain the coding scheme used for collecting

the total number of the blocks actually
received on the uplink, based on the total
number of the blocks received on the uplink.
Then record it as Average coding
scheme_Number of the blocks actually
received on the uplink.
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)
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
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
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 03 (2015-07-30)

3502
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Poor
Transm
ission
Quality
Indicate
d by
Uplink
Averag
e
SingleSlot
Throug
hput
Yes
N/A
If the average uplink BEP is higher than the

BEP required by the lowest-level coding,
and,
l SRAN8.0/
GBSS15.0/
RAN 15.0
at the same time, the uplink dataretransmission rate is higher than the upper
threshold for uplink data-retransmission rate,
l SRAN8.1/
GBSS15.1/
RAN 15.1

l SRAN9.0/
GBSS16.0/
RAN16.0
No

and the upper threshold for uplink datareception-and-retransmission rate are
internal algorithm parameters.
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
>>Upli
nk
SingleSlot
Throug
hput
(Actual
)
[0,10
0]

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3503
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
>>Upli
nk
Reuse
Ratio
[0.00,
+)
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3504
Nastar
Summary Information
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Total
Traffic
at
Downli
nk
[0,
+)
Byte
Total downlink traffic during the whole

l SRAN8.0/
GBSS15.0/
RAN 15.0

Downlink PDU
Downlink PDU
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Total
Traffic
at
Uplink
[0,
+)
Byte
Total uplink traffic during the whole process

PDU
PDU
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3505
Nastar

Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Number
[1,
+)
N/A
Unique number for the signaling message that

a VIP subscriber sends and receives during
the signaling procedure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signali
ng Time
N/A
N/A
Time when a signaling message is sent or

received.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3506
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Signali
ng
Direct
Uplin
k
N/A
Direction in which a signaling message is sent

or received.
l SRAN8.0/
GBSS15.0/
RAN 15.0
Dow
nlink
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Signali
ng Type
N/A
N/A
Type of a signaling message transmitted on

the A, Abis, GB, or PTP interface during the
signaling procedure. For example, the
parameter can be an Immediate Assignment
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3507
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Signali
ng
Content
N/A
N/A
Content of a signaling message. You can

obtain the content of a signaling message by
viewing the related tree structure.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3508
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Number
[1,
+)
N/A
Unique number of a signaling message

carrying a measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Time
N/A
N/A
Time when a measurement report is

submitted.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3509
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
MR
Type
2G
NC
MR
N/A
Type of a measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
3G
MR
l SRAN8.1/
GBSS15.1/
RAN 15.1
EUTRA
N MR
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Measure
ment
Object
Type
Server
Nbr1~
6
N/A
Type of a measurement object reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
For example, if the parameter is Server, the

measurement object is a serving cell; if the l SRAN8.1/
parameter is Nbr1, the measurement object
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3510
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Measure
ment
Object
N/A
N/A
name of a measurement object reported in

l SRAN8.0/
GBSS15.0/
RAN 15.0

format: name of the BSC: name of the cell.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
BCCH
[0,102
3]
N/A
BCCH of a neighboring cell on 2G network,

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3511
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
BSIC
[0,77]
N/A
BSIC of a neighboring cell on 2G network,

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RxLevel
(DL)
[-110,47]
dBm
Downlink RxLevel of a serving cell and that

of a neighboring cell on 2G network,
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3512
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
Frequen
cy
[0,102
3]
N/A
Frequency on 3G network, reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
P-SC
[0,512
]
N/A
Primary scrambling code on 3G networkl,

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3513
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
RSCP
[-116,25]
dBm
RSCP on 3G networkl, reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Frequen
cy
[0,102
3]
N/A
Frequency on LTE network, reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3514
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution
Version
PCI
[0,503
]
N/A
Primary scrambling code on LTE networkl,

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
RSRP
[-140,43]
dBm
RSCP on LTE networkl, reported in a

measurement report.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3515
Nastar
Mobility Analysis
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Number
[1,
+)
N/A
Number.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnorm
al
N/A
N/A

threshold for cell reselection,
the cell reselection fails and an exclamation
mark ! is displayed.
creating tasks.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3516
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Abnorm
al Cause
Overlo
ng
time of
cell
reselec
tion
(Durati
on)
N/A

threshold for cell reselection, it displays
"Overlong time of cell reselection
(Duration)".
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Type
Cell
Resele
ction
N/A
Type of a mobility analysis, namely, cell

reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3517
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
End
Time
N/A
N/A
Time when a cell reselection ends.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Source
Cell
N/A
N/A
Source cell for a cell reselection.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3518
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Reselect
RxQuali
ty
[0,7]
N/A
RxQulity of the source cell for a cell

reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Reselect
GMSK
MEAN
BEP
[0,31]
N/A
GMSK MEAN BEP of the source cell for a

cell reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3519
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Reselect
8PSK
MEAN
BEP
[0,31]
N/A
8PSK MEAN BEP of the source cell for a

cell reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Target
Cell
N/A
N/A
Target cell for a cell reselection.

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3520
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Access
RxQuali
ty
[0,7]
N/A
RxQulity of the target cell for a cell

reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Access
GMSK
MEAN
BEP
[0,31]
N/A
GMSK MEAN BEP of the target cell for a

cell reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

3521
Nastar
Parame
ter
Range
Unit
Description
Supported
Solution
Version
Access
8PSK
MEAN
BEP
[0,31]
N/A
8PSK MEAN BEP of the target cell for a

cell reselection.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
5.11.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
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Serial
Number
N/A
N/A
Serial number of a CHR. It

uniquely identifies a call record.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3522
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Combined
N/A
N/A

one.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

mobile-originated and mobileterminated eNodeBs and then is
combined into one CHR. A CHR
is a combined one if a yellow icon
is displayed.
Abnormal
N/A
N/A
Whether a call record is

abnormal.
record is abnormal.
Abnormal
Cause
N/A
N/A
Cause of an abnormal call record,

which is displayed in the format
of Exception type (number of
exception types)/Exception
cause (number of exception
causes). The exception types
include access failure, call drop,
and handover failure.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Network
LTE FDD
N/A
Network technology type.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
LTE TDD
Issue 03 (2015-07-30)
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3523
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Access
Type
Intra-RAT
RRC Access
N/A

defined.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Incoming
HO/IntraRAT
Incoming
HO
Incoming
HO/UTRAN
Incoming
HO
Incoming
HO/GERAN
Incoming
HO
Incoming
HO
CSFB On
Access
CSFB:VOIC
EEmergency
call
CSFB:VOIC
E-Nonemergency
call
CSFB:LCSNonemergency
call
Access
Time
N/A
N/A
Time when a UE accesses a cell

at the beginning of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Access Cell
1 to 64
characters
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

ID).
Issue 03 (2015-07-30)

3524
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Release
Time
N/A
N/A
Time when the link is released at

the end of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Release
Cell
1 to 64
characters
N/A
Cell from which a UE is released

at the end of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

ID).
Interworkin
g Mode
RedirectionWCDMA
N/A
Interworking Mode and RAT of

target network
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RedirectionGERAN
RedirectionTDSCDMA
RedirectionCDMA
PSHOWCDMA
PSHOTDSCDMA
PSHOCDMA
PSHOGERAN
IMSI
N/A

IMSI is displayed only when the
STMSI
N/A
N/A
subscriber.
NOTE
STMSI is displayed only when the
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3525
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
User
ID:Alias
N/A
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

IMEI-TAC
00000000-99
999999
N/A

UE.
short.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Terminal
Model
N/A
N/A
Model of a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Duration
[0,+)
Second
Duration of a call, which is

displayed in the format of
hh:mm:ss.nnn.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

time.
User Information
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Call ID
N/A
N/A

Call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3526
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

can view the IMSI
information.
IMSI is displayed only when
the EPC is not
interconnected.
STMSI
N/A
N/A
subscriber.
NOTE
STMSI is displayed only when
the EPC is not interconnected.
User ID:Alias
N/A
N/A

task.
Issue 03 (2015-07-30)
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
MMEC
BIT STRING
(SIZE (8))
bit
MME code.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
mTMSI
BIT STRING
(SIZE (32))
bit
mTMSI information of a
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eNodeB UE
S1AP ID
[0,2^32-1]
N/A

UE on an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3527
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MME UE
S1AP ID
[0,2^32-1]
N/A

UE on an MME.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
IMEI-TAC
00000000-9999
9999
N/A
First eight digits in the IMEI

of a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

equipment identity for short
and TAC is type approval
code for short.
Issue 03 (2015-07-30)
Terminal
Model
N/A
N/A
Model of a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UE Capability
N/A
N/A
Access capability of a UE in
terms of RAT support,
protocol version support,
GERAN PS handover
support, device type, and
terminal type.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>FGI
N/A
N/A
Specifies the FGI capability

of UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Capability
Related to
PUSCH NonPeriodic CQI/
PMI/RI
Reporting
Support
N/A

capability of non-periodically
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Capability
Related to
PUCCH
Periodic CQI/
PMI/RI
Reporting
Support
N/A

capability of periodically
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3528
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>RLC UM
SN&PDCP
SN
Support
N/A

layer and so on.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>ShortPeriod DRX
Support
N/A
Specifies whether short-term

DKX control is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>LongPeriod DRX
and Support
DRX Control
at MAC Layer
Support
N/A
Specifies whether DRX

control is supported by the
long-term DRX and at the
MAC layer.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Prioritized
Bit Rate
Support
N/A

prioritized bit rate is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>RLC UM
Support
N/A

layer.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>PS-toUTRAN HO
Capability
Support
N/A

from PS to UTRAN is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>GERAN
HO Capability
Using SRVCC
Support
N/A

from SRVCC to GERAN is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3529
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>CCO/
NACC
Capability
Support
N/A
Specifies whether the CCO/

NACC capability is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>HO to
1xRTT CS
Using SRVCC
Support
N/A

from SRVCC to 1xRTT CS is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Active HO
from EUTRA
RRC_CONN
ECTED to
CDMA2000
HRPD
Support
N/A

capability of actively handing
over from the EUTRA
RRC_CONNECTED mode
to the CDMA2000 HRPD
mode is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>InterFrequency HO
Capability
Support
N/A
Specifies whether the interfrequency handover

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Intra-RAT
A4/A5
Measurement
Capability
Support
N/A
Specifies whether the intraRAT A4/A5 measurement

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Inter-RAT
B1
Measurement
Capability
Support
N/A
Specifies whether the interRAT B1 measurement

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3530
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Periodic
Measurements
Including
IntraFrequency,
InterFrequency,
and Inter-RAT
Measurements
Support
N/A
Specifies whether periodic

measurement, including
intra-frequency
measurement, interfrequency measurement, and
inter-RAT measurement, is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>IntraFrequency
ANR
Support
N/A
Specifies whether the intrafrequency ANR function is

supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>InterFrequency
ANR
Support
N/A
Specifies whether the interfrequency ANR function is

supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Inter-RAT
ANR
Support
N/A
Specifies whether the interRAT ANR function is

supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Capability
Support
of Supporting
AM or UM
Mode by DRB
N/A
Specifies whether the AM or

UM mode supported by the
DRB is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Intra- or
InterSubframe FH
Capability
N/A
Specifies whether the intraor inter-subframe frequency

hopping capability is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Support

3531
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>UTRAN
B2
Measurement
Capability
Support
N/A

UTRAN B2 measurement
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>GERAN
B2
Measurement
Capability
Support
N/A

GERAN B2 measurement
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>1xRTT B2
Measurement
Capability
Support
N/A
Specifies whether the 1xRTT

supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>InterFrequency
Measurement
Capability
(Including
Measurement
Capability
Between TDD
and FDD)
Support
N/A
Specifies whether interfrequency measurement,

including measurement
between TDD and FDD
frequencies, is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>HRPD B2
Measurement
Capability
Support
N/A

supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UTRAN
CS HO
Capability
Using SRVCC
Support
N/A

from SRVCC to UTRAN CS
is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3532
Nastar
Parameter
Issue 03 (2015-07-30)
Range
Unit
Description
Supported
Solution
Version
>>Capability
Support
Related to TTI
Bundling
N/A

capability related to TTI
Bundling is supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Capability
Related to
Half-Static
Scheduling
Support
N/A

capability related to halfstatic scheduling is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>HO
Between FDD
and TDD
Support
N/A

between FDD and TDD is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UTRAN
IRAT ANR
Capability
Support
N/A

UTRAN IRAT ANR
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>GERAN
IRAT ANR
Capability
Support
N/A

GERAN IRAT ANR
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>1xRTT/
2xRTT IRAT
ANR
Capability
Support
N/A

1xRTT/2xRTT IRAT ANR
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>HRPD
IRAT ANR
Capability
Support
N/A

IRAT ANR capability is
supported.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3533
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Support
RAT
EUTRAN
N/A
RATs supported by a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Protocol versions supported

by a UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Whether a UE supports interRAT handover to GERAN

PS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
battery consumption
optimization.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UTRAN
GERAN CS
GERAN PS
CDMA2000 1X
>Supported
Protocol
Version
Number
REL-8
>Support HO
to GERAN PS
domain
Yes
>Device Type
N/A
REL-9
REL-10
No
The UE does not
report capability
indicator
information.
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
Class
Category 1
Category 2
N/A
Uplink and downlink

capability of UE.
Category 3
Category 4
Category 5
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3534
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>Uplink
Physical
Layer
Parameter
N/A
N/A
Uplink physical layer

category.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum
Number of
Uplink-SCH
Transport
Block Bits
Transmitted
within a TTI
N/A
N/A
Maximum number of ULSCH transport block bits

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum
Number of
Bits of an
Uplink-SCH
Transport
Block
Transmitted
within a TTI
N/A
N/A
Maximum number of bits of

an UL-SCH transport block
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Support for
64QAM in
Uplink
Yes
N/A
Whether support for 64QAM

in UL.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Downlink
Physical
Layer
Parameter
N/A
N/A
Downlink physical layer

category.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum
Number of
DownlinkSCH
Transport
Block Bits
Received
within a TTI
N/A
N/A
Maximum number of DLSCH transport block bits

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

3535
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Maximum
Number of
Bits of a
DownlinkSCH
Transport
Block
Received
within a TTI
N/A
N/A
Maximum number of bits of a

DL-SCH transport block
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Maximum
Number of
Supported
Layers for
Spatial
Multiplexing
in Downlink
N/A
Maximum number of
supported layers for spatial
multiplexing in DL.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
2
4
8
2 or 4
Access Information
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Time
N/A
N/A
Time when a UE accesses a

cell at the beginning of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Access Cell
1 to 64
characters
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

ID:cell ID).
Issue 03 (2015-07-30)
Access Physical
eNodeB ID
[0,104857
5]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1
Access Physical
LocalCell ID
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1

3536
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Physical
Sector
Equipment or
Equipment
Group ID
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1
Access TA
[0,1314]
16*Ts=0.5
2 ms

access of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Access Uplink
RSRP
[-150,-30]
dBm

during the access of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Access Uplink
SINR
[-15,35]
dB

access of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3537
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Type
IntraRAT
RRC
Access
N/A

defined.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Cause in the RRC setup

request message.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Complete time during the

access of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Incoming
HO/IntraRAT
Incoming
HO
Incoming
HO/
UTRAN
Incoming
HO
Incoming
HO/
GERAN
Incoming
HO
Incoming
HO
Access Cause
Emergenc
y
High
Priority
Access
MtAccess
Mosignaling
Mo-Data
N/A
Access
Complete Time
Issue 03 (2015-07-30)
N/A

3538
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Delay
Time
N/A
The delay time between the

time of access request and the
time of access completion.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Release Information
Parameter
Range
Unit
Description
Supported
Solution
Version
Release Time
N/A
N/A
Time when the link is released at the

end of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Release Cell
1 to 64
character
s
N/A
Cell from which a UE is released at

the end of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
N/A
CSFB
Issue 03 (2015-07-30)

following format: eNodeB name: cell
name (eNodeB ID:cell ID).
CSFB information.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3539
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>CSFB
Triggering
Cause
CSFB:V
OICEEmergen
cy call
N/A
The triggering cause indicated by a

CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates whether an eNodeB

successfully responds to the CSFP
indication from the MME.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
CSFB:V
OICENonemergen
cy call
CSFB:L
CS-Nonemergen
cy call
>CSFB
Response
Respons
e
No
Respons
e
Interworking
Information
N/A
N/A
Interworking Information.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Blind or
Measurement
l Blind
N/A
Used for determining whether the UE

received MR report before handover
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>With SIBInfo
l Yes
N/A
Used for determining whether RRC

Connection Release message which
sent by eNodeB was with SIBInfo.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
l Meas
urem
ent
l No
Issue 03 (2015-07-30)

3540
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Triggering
Cause
l CSF
B
N/A
Interworking triggering Cause.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Release cause based on RRC of a

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
l SRV
CC
l Other
RRC Release
Cause
Load
balancin
g TAU
Other
CS
Rollback
to High
Priority
UE Context
Release Cause
N/A
N/A
Release cause based on UE context

release of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Handover
Release Cause
Handove
r based
on the
distance
N/A
Release cause based on the last

handover release of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Handove
r based
on the
coverage
Handove
r based
on the
load
balancin
g
Issue 03 (2015-07-30)

3541
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MSG4's HARQ
Final State
l 0
NAC
K
N/A
State of the MSG4's HARQ.
eRAN11.0
l 1
ACK
l 2
DTX
Issue 03 (2015-07-30)
Release
Information
N/A
N/A
Cause of a failed release.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Release Type
N/A
N/A
Type of the cause of a failed release.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Release
Reason
N/A
N/A
Details about the cause of a failed

release.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cause
N/A
N/A
Internal release failure cause.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Error Detail
Cause
N/A
N/A
Detailed cause value obtained from

internal CHRs.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3542
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Call
Procedure Type
N/A
N/A
Information about the status of the

call procedure.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DC Err Type
N/A
N/A
Type of an abnormal call procedure.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DC Detail
value
N/A
N/A
Detailed cause of an abnormal call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Re-setup Information
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC
Reestablishmen
t Count
[0,+)
N/A
Times of RRC
connection resetup.
eRAN 7.0/
eRAN 8.0/
eRAN 8.1
Handover
Triggered RRC
Reestablishmen
t Result
N/A
N/A
Number of RRC
connection resetup triggered
by failed
handovers.
eRAN 7.0/
eRAN 8.0/
eRAN 8.1

3543
Nastar
Signaling Flow Analysis

Parameter
Range
Unit
Description
Supported
Solution
Version
No.
[1,+)
N/A
Number that uniquely identifies

a sent and received signaling
message.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Signaling Time
N/A
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Signaling Direct
No
Direction
N/A
Direction for sending or

receiving a signaling message.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A

transmitted over the S1-MME or
Uu interface.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Uplink
Downlink
Signaling Type
N/A

Signaling
Content
N/A
N/A
Content for sending or receiving

Note: it will display the contents
only for the all-signaling
analysis.
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3544
Nastar
Measurement Report Analysis

Parameter
Range
Unit
Description
Supported
Solution
Version
No.
[1,+)
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Measurement
Time
N/A
N/A
Local time on the eNodeB

when an MR is generated.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
MR Type
EVENT_MR
N/A
The type of MR including

event MR, intra-frequency
MR of periodic MR, private
UE MR of periodic MR and
period private throughput
measurement MDT.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
PRE_INTRA_F
REQ_MR
PRE_UE_MR
NOTE
Period private throughput
measurement MDT is
supported only on eRAN8.1/
eRAN11.0.
Access Type
EUTRAN
N/A
RAT type of an MR for

inter-RAT measurement.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Type of a measurement
object in an MR.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates the measure cell

information of MR, which
displays as eNodeBID:
CellID.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UTRAN
GERAN
CDMA2000
TD-SCDMA
Measurement
Object Type
Server
Nbr1
Nbr2
Nbr...
Measure Object
Issue 03 (2015-07-30)
N/A

3545
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
EARFCN/
ARFCN
LTE:[0,65535]
N/A
Indicates the cell ARFCNs

of the LTE, GSM, or TDSCDMA network.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates the physical

identify code of the cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
TD-SCDMA:
[0,65535]
GSM:[0,1023]
PCI/P-SC/
BSIC/PN
LTE:[0,503]
UMTS:[0,511]
RSRP/RSCP/
RSSI/Pilot
Strength
TD-SCDMA:
[0,127]
LTE: PCI
GSM:[00,77]
GSM: BSIC
CDMA:[0,511]
CDMA: PN
LTE:[-150,-30]
UMTS/TD-SCDMA: P-SC
dBm
UMTS/TDSCDMA:
[-116,-25]
Indicates the signal strength

of the cell.
LTE: RSRP
UMTS/TD-SCDMA:
RSCP
GSM/CDMA:
[0,63]
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GSM: RSSI
CDMA: Pilot Strength
RSRQ/EcNo
LTE:
[-19.5,-2.5]
dB
UMTS:
[-31.5,0]
Issue 03 (2015-07-30)
Frequency Band
Indicator
DCS1800
UL DM RSRP
[-150,-30]
Indicates the signal quality

of the cell.
LTE: RSRQ
UMTS: Ec/No
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Frequency band indicator of

a neighboring cell when the
measurement type is interRAT and the RAT is
GERAN in an MR.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
dBm
Indicates the RSRP of

uplink DMRS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
PCS1900

3546
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
UL DM SINR
[-15,35]
dB
Indicates the SINR of

downlink DMRS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL IBLER
[0.00,100.00]

rate on the uplink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL IBLER(0)
[0.00,100.00]

rate of the code 0 on the
downlink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL SINR
[-15,35]
dB
Indicates the SINR on the

uplink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL CQI(0)
[0,26]
N/A
Indicates the CQI of the

code 0 on all bandwidth of
the downlink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3547
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
UL MIMO
Mode
1T1R
N/A

on the uplink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
1T2R
2T2R
VIRTUAL
MIMO
1T4R
2T4R
VIRTUAL
MIMO
1T8R BEAM
FORMING
2T28R BEAM
FORMING
Issue 03 (2015-07-30)

3548
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
DL MIMO
Mode
TX_MODE_SI
NGLE_ANT_P
ORT_0
N/A

on the downlink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates the RANK value

reported by the UE at the
last time.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A

of the RB on the uplink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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
Rank2
UL RB Use
Times
Issue 03 (2015-07-30)
[0,4294967295]

3549
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
DL RB Use
Times
[0,4294967295]
N/A

of the RB on the downlink.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Initial
Transmission
DL Grant
[0,+)
Numbe
r

downlink UE is scheduled
during initial transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL Grant
[0,+)
Numbe
r

uplink UE is scheduled,
including initial
transmissions and
retransmissions.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion of
Dual
Codewords in
Initial
Transmission
[0.00,100.00]
Proportion of dual
codewords during initial
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL
Retransmission
Rate
[0.00,100.00]
Uplink retransmission rate.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL
Retransmission
Rate
[0.00,100.00]
Downlink retransmission
rate.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3550
Nastar
Mobility Management Information

Parameter
Range
Unit
Description
Supported
Solution
Version
No.
[1,+)
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Abnormal
N/A
Field indicating an abnormal

handover.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Blank
The value of this field is ! if

the value of Handover Result
is either of the following:
HO Preparation Succeeded/
HO Failure
HO Preparation Failure/
NULL
Otherwise, the value of this
field is blank.
Issue 03 (2015-07-30)

3551
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover
Triggering
Cause
Based on
distance
N/A
The triggered cause of a

handover.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Based on
coverage area
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_nonemergency call
Based on
coverage
area_nonemergency call
Based on
bearer_nonemergency call
Based on
service_nonemergency call
Based on
uplink
quality_nonemergency call
Based on
frequency
priority_nonemergency call
Based on
CSFB_nonemergency call
Issue 03 (2015-07-30)

3552
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
Handover type during a voice

service.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Based on
CSFB_emergen
cy call
Based on
HPLMN
return_nonemergency call
Based on other
causes_nonemergency call
Based on other
causes_emerge
ncy call
HO Type Voice
NON_SRVCC
CS_ONLY_SR
VCC
CS_AND_PS_
SRVCC
Issue 03 (2015-07-30)

3553
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover Type
Intra-RAT
outgoing
handover/Intrafrequency
handover
N/A
Handover type during a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
outgoing
handover/Interfrequency
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 03 (2015-07-30)

3554
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover
Interface Type
The handover
interface types
of intra-RAT
handover are the
following:
N/A
Interface types involved in a

handover during a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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.
Issue 03 (2015-07-30)
Begin Time
N/A
N/A
Preparation time for initiating

an incoming or outgoing intraRAT or inter-RAT handover
during a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Interval
[0,+)
Interval = Start time - End

time.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3555
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Overlong
Interval
Yes
N/A
If the interval exceeds the

overlong xxx delay threshold,
the value of this parameter is
Yes. Otherwise, the value of
this parameter is No.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No
The overlong xxx delay

threshold is set by engineers
during task creation. The
threshold types are as follows:
Overlong intra-RAT
threshold;
Overlong inter-RAT
threshold;
Overlong intra-RAT
incoming handover delay
threshold.
End Time
N/A
N/A
End time.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Source Cell
N/A
N/A
Source cell from which a call

is handed over.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

ID:cell ID).
Issue 03 (2015-07-30)
HO Physical
eNodeB ID
[0,1048575]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
HO Physical
LocalCell ID
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
HO Physical
Sector
Equipment ID
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3556
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Source Cell
RSRP
[-150,-30]
dBm
RSRP of the serving cell on

handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Source Cell
RSRQ
[-15,35]
dB
RSRQ of the serving cell on

handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Target Cell
N/A
N/A
Target cell to which a call is

handed over.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

ID:cell ID).
Target Cell
RSRP/RSCP/
RSSI
[-150,-30]
dBm
RSRP/RSCP/RSSI of the
serving cell during the
handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Target Cell
RSRQ/EcNo
[-19.5,-2.5]
dB
RSRQ/EcNo of the serving

cell during the handover of a
call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Handover
Preparation
Triggering
Cause
Radio Network
Layer
N/A
Triggering cause of the

preparation of an outgoing
preparation triggering cause
of an incoming handover is
empty.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Transport
Layer
NAS Layer
Protocol Layer
Miscellaneous
Issue 03 (2015-07-30)

3557
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover
Preparation
Failure Cause
Handover
preparation to
target cell
failure
N/A
Cause of a failed outgoing

cause of a failed incoming
handover is empty.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Whether the HANDOVER

CANCEL message is received
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Protocol cause initiated due to

a canceled handover. For
details, see 9.2.1.3 and 9.2.6 in
3GPPTS36.413
specifications.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
Indicates whether data is

transmitted during the
handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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
Handover
Yes
Reason for
Canceling HO
Radio Network
Layer Cause
No
Transport
Layer Cause
NAS Layer
Cause
Protocol Layer
Cause
Other Cause
With Data
Transmission
Issue 03 (2015-07-30)
Yes
No

3558
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Handover
Result
HO Preparation
Succeed/HO
Execution
Succeed
N/A
Handover result of a call,

including the handover
preparation result and
handover execution result.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
HO Preparation
Succeed/HO
Execution
Failure
HO Preparation
Failure/NULL
HO Preparation
Succeeded/HO
SUCC WITH
REEST
Issue 03 (2015-07-30)
TA upon
Handover
[0,1314]
16*T
s=0.5
2 ms

handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULRSRP upon
Handover
[-150,-30]
dBm

power (RSRP) on the UL
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULSINR upon
Handover
[-15,35]
dB
SINR on the UL during the

handover of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB ID
[0,15]
N/A
ID of the E-RAB that is

handed over.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3559
Nastar
Parameter
Range
Unit
Description
E-RAB QCI
GBR(QCI1)
N/A
Service type for which ERAB is handed over. The

follows:
GBR(QCI2)
GBR(QCI3)
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)
Supported
Solution
Version
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
with high QoS. N = 1, 2, 3, or eRAN11.0
4. QCI is QoS class identifier
for short and GBR is
guaranteed bit rate for short.
6, 7, 8, or 9.
Non GBR
(QCI7)
Non GBR
(QCI8)
Non GBR
(QCI9)
E-RAB
Handover
Preparation
Result
Succeed
N/A
Result of accessing an E-RAB

during an incoming handover.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Failure
E-RAB Analysis
Parameter
Range
Unit
Description
Supported
Solution
Version
No.
[1,+)
N/A
Serial number of an E-RAB

ID. It uniquely identifies an ERAB ID.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Abnormal
N/A
Indicates whether an E-RAB

is abnormal.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Blank
Issue 03 (2015-07-30)

3560
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Abnormal
N/A

setup request.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Cause
Procedure
Complete
N/A
Cause of failed E-RAB setup.

The parameter value also
includes detailed causes.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Blank
Radio Network
Layer Cause
Transport
Layer Cause
NAS Cause
Protocol Cause
Miscellaneous
Cause
Incoming HO
No Responding
After E-RAB
Setup Request
E-RAB Request
Service Type
(QCI) on ERAB Setup
GBR(QCI1)
GBR(QCI2)

follows:
GBR(QCI3)

bit rate for short.
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)

6, 7, 8, or 9.
Non GBR
(QCI7)
Non GBR
(QCI8)
Non GBR
(QCI9)
E-RAB Request
Time
Issue 03 (2015-07-30)
N/A
N/A
Time when E-RAB is

requested.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3561
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cell on E-RAB
Request
N/A
N/A
Cell when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
SGW IP
Displaying
example of
IPV4:
10.22.33.44
N/A
Transport Layer IP.
eRAN 7.0
SPC800/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Displaying
example of
IPV6:
fe80:981c:981c:
237:fd93:4dea:f
d93:4dea
Issue 03 (2015-07-30)
E-RAB Setup
Time
N/A
N/A
Time of RAB setup.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
TA on E-RAB
Setup
[0,1314]
16*Ts
=0.52
ms

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULRSRP on ERAB Setup
[-150,-30]
dBm

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULSINR on ERAB Setup
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3562
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Release
Abnormal
N/A
Release result of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Release
Cause
Procedure
Complete
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Blank
Radio Network
Layer Cause
Transport
Layer Cause
NAS Cause
Protocol Cause
Miscellaneous
Cause
RRC
Establishment
Cause
RRC Release
Cause
RRC
Reestablishmen
t Cause
E-RAB Data on
E-RAB Release
Yes
No

the exception.
E-RAB Request
Service Type
(QCI) on ERAB Release
GBR[1,4]
Non GBR[5,9]
N/A

bit rate for short.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

6, 7, 8, or 9.
Issue 03 (2015-07-30)

3563
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Release
Complete Time
N/A
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cells Released
for E-RAB
1 to 64
characters
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Physical
eNodeB ID
Released For ERAB
[0,1048575]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Physical
LocalCell ID
Released For ERAB
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Physical Sector
Equipment ID
Released For ERAB
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
TA on E-RAB
Release
[0,1314]
16*Ts
=0.52
ms

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULRSRP on ERAB Release
[-150,-30]
dBm

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
ULSINR on ERAB Release
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3564
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Delay
[0,+)
Secon
d
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
Duration
[0,+)
Secon
d
Duration of E-RAB.
Total Uplink
Traffic Volume
(0.0,+)
MB

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Uplink
Transmission
Duration
(0.000,+)

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0.000,+)
kbit/s

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Downlink
Traffic Volume
(0.0,+)
MB

in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Downlink
Transmission
Duration
(0.000,+)

an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Time.

Time

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3565
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Throughput
[0.000,+)
kbit/s
Average downlink throughput

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Uplink VQI
[0.0,5.0]
N/A

RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Downlink VQI
[0.0,5.0]
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Detail E-RAB Information(QCI2 to QCI9)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB ID
N/A
N/A
E-RAB ID.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Info
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3566
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB
Request Service
Type(QCI) on
E-RAB Setup
GBR(QCI1)
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GBR(QCI2)

follows:
GBR(QCI3)

bit rate for short.
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)

6, 7, 8, or 9.
Non GBR
(QCI7)
Non GBR
(QCI8)
Non GBR
(QCI9)
Issue 03 (2015-07-30)
>E-RAB
Request Time
N/A
N/A
Time when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cell on ERAB Request
N/A
N/A
Cell when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB Setup
Time
N/A
N/A
Time of RAB setup.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB Setup
Result
Succeed
N/A

setup request.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Failure

3567
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Setup
Cause
Procedure
Complete
N/A

detailed causes.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Radio Network
Layer Cause
Transport
Layer Cause
NAS Cause
Protocol Cause
Miscellaneous
Cause
Incoming HO
No Responding
After E-RAB
Setup Request
>E-RAB Setup
Delay
Estimation
N/A
N/A

setup of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>E-RAB
Setup Delay
[0,+)
Second
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Long E-RAB
Setup Delay
Yes
E-RAB Setup Delay = ERAB Setup Time - E-RAB

Request Time.
N/A
No
Used for determining

whether an E-RAB setup
delay is exceedingly long.
exceedingly long if it is
greater than or equal to the
threshold for long E-RAB
setup delay.
>MR
Information on
E-RAB Setup
Issue 03 (2015-07-30)
N/A
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3568
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>TA
[0,1314]
16*Ts
=0.52
ms

the E-RAB setup of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL RSRP
[-150,-30]
dBm

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL SINR
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Priority
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Priority
High-priority
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
mediumpriority
low-priority
>>E-RAB
Active
Preemptability
Shall not
trigger preemption
May trigger
pre-emption
>>E-RAB
Passive
Preemptability
Issue 03 (2015-07-30)
Not preemptable
Pre-emptable

3569
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Rate
Information
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>SGW IP
Displaying
example of
IPV4:
10.22.33.44
N/A
Transport Layer IP.
eRAN 7.0
SPC800/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Displaying
example of
IPV6:
fe80:981c:981c:
237:fd93:4dea:f
d93:4dea
Issue 03 (2015-07-30)

3570
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Release
Information
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Request Service
Type(QCI) on
E-RAB Release
GBR[1,4]
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Non GBR[5,9]

bit rate for short.
6, 7, 8, or 9.
Issue 03 (2015-07-30)
>E-RAB
Release Request
Time
N/A
N/A

request is started.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Release
Complete Time
N/A
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Duration
[0,+)
Second
Duration of E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cells Released
for E-RAB
1 to 64
characters

Time
N/A

released.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3571
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Physical
eNodeB ID
Released For ERAB
[0,1048575]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Physical
LocalCell ID
Released For ERAB
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Physical
Sector
Equipment ID
Released For ERAB
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Release Cause
E-RAB
abnormal
release
triggered by
MME
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
abnormal
release
triggered by
eNodeB
E-RAB
abnormal
release
triggered by
outgoing HO
execution
failure
>Initiating Party
of E-RAB
Release
Issue 03 (2015-07-30)
MME
eNodeB

3572
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Data
on E-RAB
Release
Yes
N/A

data is being transmitted
when an E-RAB is released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

the subscriber cannot
perceive the exception.
Issue 03 (2015-07-30)
>MR
Information on
E-RAB Release
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>TA
[0,1314]
16*Ts
=0.52
ms

the E-RAB release of a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL RSRP
[-150,-30]
dBm

during the E-RAB release of
a call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL SINR
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Process
Information
N/A
N/A
Information about the setup

of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3573
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>Statistics of
Data
Transmission
N/A
N/A
Statistics on data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total Uplink
Traffic Volume
(0.0,+)
MB

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total Uplink
Transmission
Duration
(0.000,+)

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Average
Uplink
Throughput
[0,+)
kbit/s

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Low Average
Uplink
Throughput
Yes
N/A

uplink throughput for an
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total
Downlink
Traffic Volume
(0.0,+)
MB

traffic generated from an
RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total
Downlink
Transmission
Duration
(0.000,+)

an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

3574
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Average
Downlink
Throughput
[0,+)
kbit/s

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Low Average
Downlink
Throughput
Yes
N/A

average downlink
throughput.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No
Detail E-RAB Information(QCI1)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB ID
N/A
N/A
E-RAB ID.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Info
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3575
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB
Request Service
Type(QCI) on
E-RAB Setup
GBR(QCI1)
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GBR(QCI2)

follows:
GBR(QCI3)

bit rate for short.
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)

6, 7, 8, or 9.
Non GBR
(QCI7)
Non GBR
(QCI8)
Non GBR
(QCI9)
Issue 03 (2015-07-30)
>E-RAB
Request Time
N/A
N/A
Time when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cell on E-RAB
Request
N/A
N/A
Cell when E-RAB is

requested.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB Setup
Time
N/A
N/A
Time of RAB setup.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB Setup
Result
Succeed
N/A

setup request.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Failure

3576
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Setup
Cause
Procedure
Complete
N/A

detailed causes.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Radio Network
Layer Cause
Transport
Layer Cause
NAS Cause
Protocol Cause
Miscellaneous
Cause
Incoming HO
No Responding
After E-RAB
Setup Request
>E-RAB Setup
Delay
Estimation
N/A
N/A

setup of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>E-RAB
Setup Delay
[0,+)
Secon
d
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Long E-RAB
Setup Delay
Yes
N/A
Used for determining whether

an E-RAB setup delay is
exceedingly long.
No

Time.

exceedingly long if it is greater
than or equal to the threshold
for long E-RAB setup delay.
>MR
Information on
E-RAB Setup
Issue 03 (2015-07-30)
N/A
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3577
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>TA
[0,1314]
16*Ts
=0.52
ms

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL RSRP
[-150,-30]
dBm

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL SINR
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Priority
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Priority
High-priority
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A
setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
mediumpriority
low-priority
>>E-RAB
Active
Preemptability
Shall not
trigger preemption
May trigger
pre-emption
>>E-RAB
Passive
Preemptability
Issue 03 (2015-07-30)
Not preemptable
Pre-emptable

3578
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB Rate
Information
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

setup E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0, 10,000,000]
Mbit/s

E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Release
Information
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3579
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>E-RAB
Request Service
Type(QCI) on
E-RAB Release
GBR[1,4]
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Non GBR[5,9]

bit rate for short.
6, 7, 8, or 9.
Issue 03 (2015-07-30)
>E-RAB
Release Request
Time
N/A
N/A

request is started.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Release
Complete Time
N/A
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Duration
[0,+)
Secon
d
Duration of E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Cells Released
for E-RAB
1 to 64
characters
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Physical
eNodeB ID
Released For ERAB
[0,1048575]
N/A
eNodeB ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Physical
LocalCell ID
Released For ERAB
[0,255]
N/A
Local cell ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Time

3580
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Physical
Sector
Equipment ID
Released For ERAB
[0,65535]
N/A
Sector equipment or
Equipment Group ID
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>E-RAB
Release Cause
E-RAB
abnormal
release triggered
by MME
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A

released.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
abnormal
release triggered
by eNodeB
E-RAB
abnormal
release triggered
by outgoing HO
execution
failure
>Initiating Party
of E-RAB
Release
MME
>E-RAB Data
on E-RAB
Release
Yes
eNodeB
No

the exception.
>MR
Information on
E-RAB Release
Issue 03 (2015-07-30)
N/A
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3581
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>TA
[0,1314]
16*Ts
=0.52
ms

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL RSRP
[-150,-30]
dBm

call.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL SINR
[-15,35]
dB

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Process
Information
N/A
N/A

an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Statistics of
Voice Quality
N/A
N/A
Statistics on the voice quality

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI
[0.0,5.0]
N/A

RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI as
Excellent Times
[0,65535]
Numb
er

than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3582
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>UL VQI as
Good Times
[0,65535]
Numb
er

equal to 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI as
Accept Times
[0,65535]
Numb
er

equal to 3.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI as
Poor Times
[0,65535]
Numb
er

equal to 3.1.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>UL VQI as
Bad Times
[0,65535]
Numb
er

or equal to 2.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Poor Uplink
VQI
Yes
N/A

VQI value for uplink voice
threshold for poor uplink VQI.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Uplink Voice
Frame Error
Rate (Including
Error Packets
and Delay
Packets)()
[0,1000]
N/A

delayed packets) for uplink
RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Proportion of
Uplink Voice
Delay Packets
()
[0,1000]
N/A
Proportion of delayed uplink

voice packets borne by an
RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

3583
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>DL VQI
[0.0,5.0]
N/A

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Excellent Times
[0,65535]
Numb
er

greater than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Good Times
[0,65535]
Numb
er

or equal to 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Accept Times
[0,65535]
Numb
er

or equal to 3.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Poor Times
[0,65535]
Numb
er

or equal to 3.1.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>DL VQI as
Bad Times
[0,65535]
N/A

less than or equal to 2.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Poor
Downlink VQI
Yes
N/A

VQI value for downlink voice
threshold for poor downlink
VQI.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

3584
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Downlink
Voice Frame
Error Rate
(Including Error
Packets and
Delay Packets)
()
[0,1000]
N/A

RAB in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>Statistics of
Data
Transmission
N/A
N/A
Statistics on data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total Uplink
Traffic Volume
(0.0,+)
MB

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total Uplink
Transmission
Duration
(0.000,+)

eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Average
Uplink
Throughput
[0,+)
kbit/s

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Low Average
Uplink
Throughput
Yes
N/A

uplink throughput for an RAB
in an eNodeB is less than the
threshold for low average
uplink throughput.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Total
Downlink
Traffic Volume
(0.0,+)
MB

in an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No

3585
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>>Total
Downlink
Transmission
Duration
(0.000,+)

an eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Average
Downlink
Throughput
[0,+)
kbit/s

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
>>Low Average
Downlink
Throughput
Yes
N/A

the threshold for low average
downlink throughput.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
No
Trend Analysis-Process Traffic Statistics
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
No.
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cell
N/A
N/A
Information about a cell in

which traffic is consumed.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3586
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Record Time
N/A
N/A
Period within which traffic

is consumed.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Uplink MCS
N/A
N/A
Uplink MCS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Downlink MCS
N/A
N/A
Downlink MCS.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB ID
N/A
N/A
ID of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB QCI
GBR(QCI1)
N/A
QCI of an E-RAB. The

follows:
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GBR(QCI2)
GBR(QCI3)
GBR(QCI4)
Non GBR
(QCI5)
Non GBR
(QCI6)
Non GBR
(QCI7)
Non GBR
(QCI8)

with high QoS. N = 1, 2, 3,
or 4. QCI is QoS class
identifier for short and
GBR is guaranteed bit rate
for short.
Non GBR (QCIN): nonGBR service with low QoS.
N = 5, 6, 7, 8, or 9.
Non GBR
(QCI9)
Issue 03 (2015-07-30)

3587
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink
Throughput
[0,+)
MB
Uplink Throughput within

a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Uplink
Transmission
Duration
[0,+)
uplink data within a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0,+)
kbit/s
Average Uplink throughput

within a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Downlink
Throughput
[0,+)
MB
Downlink Throughput
within a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Downlink
Transmission
Duration
[0,+)
downlink data within a
period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Throughput
[0,+)
kbit/s
Average downlink
throughput within a period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3588
Nastar
Trend Analysis-Cell-Process Voice Statistics

Paramet
er
Range
Unit
Description
Supported
Solution
Version
No.
N/A
N/A
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Record
Time
N/A
N/A
Time when a voice service is

recorded.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cell
N/A
N/A
Information about a cell in which

a voice service is used.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
ID
N/A
N/A
ID of an E-RAB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB
QCI
GBR(QCI1)
N/A
QCI of an E-RAB. The parameter

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GBR(QCI2)
GBR (QCIN): GBR service with

high QoS. N = 1, 2, 3, or 4. QCI
is QoS class identifier for short
and GBR is guaranteed bit rate
for short.
GBR(QCI3)
GBR(QCI4)
Non GBR(QCI5)
Non GBR(QCI6)

service with low QoS. N = 5, 6,
7, 8, or 9.
Non GBR(QCI7)
Non GBR(QCI8)
Non GBR(QCI9)
UL VQI
Issue 03 (2015-07-30)
[0.0,5.0]
N/A

voice services.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
3589
Nastar
Issue 03 (2015-07-30)
Paramet
er
Range
Unit
Description
Supported
Solution
Version
UL VQI
as
Excellent
Times
[0,65535]
Num
ber

greater than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL VQI
as Good
Times
[0,65535]
Num
ber

less than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL VQI
as Accept
Times
[0,65535]
Num
ber

less than 3.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL VQI
as Poor
Times
[0,65535]
Num
ber

less than 3.1.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL VQI
as Bad
Times
[0,65535]
Num
ber

equal to or less than 2.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL FER
[0,1000]
N/A

delayed packets) for uplink voice
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL Out
Delay
Ratio()
[0,1000]
N/A
Out delay rate for uplink voice

services borne by an RAB in an
eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3590
Nastar
Issue 03 (2015-07-30)
Paramet
er
Range
Unit
Description
Supported
Solution
Version
DL VQI
[0.0,5.0]
N/A
Average VQI value for downlink

voice services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as
Excellent
Times
[0,65535]
Num
ber

is greater than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as Good
Times
[0,65535]
Num
ber

or less than 4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as Accept
Times
[0,65535]
Num
ber

or less than 3.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as Poor
Times
[0,65535]
Num
ber

or less than 3.1.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL VQI
as Bad
Times
[0,65535]
Num
ber

is equal to or less than 2.6.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL FER
[0,1000]
N/A

voice services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3591
Nastar
5.11.8 Reference for Complaint Analysis Support Parameters (PS

Core)
This section describes the parameters for PS Core complaint analysis support.
Reference for Complaint Analysis Support Parameters (PS Core) - User Plane
This section describes the parameters for complaint analysis support based on user plane data
on UGW.
Parameters for Viewing PS Core Complaint Analysis Support Results - Summary (UGW)
This section describes the parameters for querying complaint analysis support (summary) results
analysis based on user plane data. You can refer to the description when querying complaint
analysis support (summary) results.
Summary
Parameter
Range
Unit
Description
Supported
Solution
Version
Serial Number
(0,2^31-1)
N/A
Serial number of an xDR in the

summary table. The serial
number is the keyword of a
service and uniquely identifies
a service record. It is an internal
identifier used in the Nastar
system.
PS 12.1
Assoiciated
Signaling Plane
SDR
N/A
N/A
If an associated signaling plane

SDR is available for a user
plane SDR, the association icon
is displayed. Otherwise, the
area is displayed as blank.
PS 12.1
NOTE
This parameter is displayed only
when the Nastar analyzes user
plane and signaling plane data at
the same time.
Issue 03 (2015-07-30)

3592
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
N/A
Whether a service is abnormal.
PS 12.1

service is abnormal.
Blank

exception type of this service in
the navigation tree is Other and
the exception status is
unknown.
Abnormal
Cause
N/A
N/A
Exception cause of a service.
PS 12.1
Demarcation
Result
RAN Cause
N/A
Demarcation result of an
exception cause.
PS 12.1
UE Cause
SP Cause
CN or SP
Cause
Other Cause
Application
Name
N/A
N/A
Name of an application.
PS 12.1
Service Start
Time
YYYYMM-DD
hh:mm:ss.x
xx
N/A
Time when a service starts.
PS 12.1
Service End
Time
YYYYMM-DD
hh:mm:ss.x
xx
N/A
Time when a service ends.
PS 12.1
Terminal IP
Address
N/A
N/A
IP address of a terminal that

uses services.
PS 12.1
Server IP
Address
N/A
N/A
IP address of a server that

provides services.
PS 12.1
User ID:User
Name
N/A
N/A
User ID, which is randomly

distributed by the system when
creating the task.
PS 12.1
User Name, which is set by the

Issue 03 (2015-07-30)

3593
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
PS 12.1

IMEI-TAC
00000000FFFFFFFF
N/A

a UE.
PS 12.1

short.
Terminal Model
N/A
N/A
Model of a UE.
PS 12.1

using System Function >
Terminal Type Management
UE.
Host Name
N/A
N/A
Name of a host that provides

services.
PS 12.1
RAT
UTRAN
N/A
RAT.
PS 12.1
GERAN
EUTRAN
Cell
N/A
N/A
The format is: eNodeB ID : Cell

ID.
PS 12.1
SGW IP/PGW
IP
Displaying
example of
IPV4:
10.22.33.44
N/A
IP address of the SGW and

PGW.
PS 12.1
N/A
A User agent that provides

services.
PS 12.1
Displaying
example of
IPV6:
fe80:981c:
981c:
237:fd93:4d
ea:fd93:4de
a
User Agent
Issue 03 (2015-07-30)
N/A

3594
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
APN
N/A
N/A
Information about an APN that

provides services.
PS 12.1
Parameters for Viewing PS Core Complaint Analysis Support Results - Web Browsing
(UGW)
This section describes the parameters for querying complaint analysis support (web browsing)
results. You can refer to the description when querying complaint analysis support (web
browsing) results.
Detailed Information--Page Overall Info
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
Page DNS
Response Offset
[0.00,+)

when the first page DNS
response event occurs and
enabled.
PS 12.1
Page TCP SYN

Offset
[0.00,+)

when the syn packet of the
first page TCP connection is
received and the time when
is enabled.
PS 12.1
Page TCP SYN

ack Offset
[0.00,+)

when the syn ack packet of
the first page TCP
enabled.
PS 12.1
Page TCP ack

Offset
[0.00,+)

when the last ack packet of
the first page TCP
enabled.
PS 12.1

3595
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
Page First
Request Offset
[0.00,+)

is enabled.
PS 12.1
Page First
Response Offset
[0.00,+)

is enabled.
PS 12.1
Page First
Redirect
Request Offset
[0.00,+)

when the first page
is enabled.
PS 12.1
Page First
Redirect
Response Offset
[0.00,+)

when the first page
is enabled.
PS 12.1
Page Request
Offset
[0.00,+)

PS 12.1
Page Response
Offset
[0.00,+)

PS 12.1

3596
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Page TCP
Release Offset
[0.00,+)

when the page TCP
connection is released and
enabled.
PS 12.1
Page TCP connection

release means that the
quintuple of the page TCP
TCP connection.
Detailed Information--Page Response Phase
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Redirect
Count
[0,+)
Numb
er

page redirection occurs
during the page response
phase. This parameter is
calculated when page
redirection exists.
PS 12.1
Page No
Response Wait
Time
[0.00,+)
Time when subscribers

actively close pages (a
UE sends RST or FIN
first) relative to the time
when SYNC appears if
there is no page
response.
PS 12.1
Page Request
Retransmission
Count
[0,+)
Numb
er

page Get request is
retransmitted.
PS 12.1

3597
Nastar
Detailed Information--Page Display Phase

Parameter
Range
Unit
Description
Supported
Solution
Version
Page DNS
[0,+)
Response Count
Number
Number of times that all DNS

requests are responded to
during the page display phase
(between the time when the
main page request is
responded to and the time
function is disabled).
PS 12.1
Wireless
Effective
Throughput
kbit/s

the RAN side.
PS 12.1
[0.00,
+)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Response
Result
Success/Failure
N/A
Result of
responding to a
page request.
PS 12.1
Page Response
Code
N/A
N/A
Page Response
Code.
PS 12.1
Page Display
Success Flag
Success/Failure
N/A
Page display is
successful only
when a main
page request is
successfully
responded to.
Page display
fails if page
redirection
occurs and fails.
PS 12.1

3598
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Download
Throughput
[0,+)
kbit/s
Average page
transmission
rate during the
page display
phase (between
the time when
the main page
request is
responded to
and the time
when the page
browsing
function is
disabled).
PS 12.1
>Page Size
[0,+)
Byte
Total size of
downlink nonretransmission
packets for page
contents
(between the
time when the
main page
request is
initiated and the
time when the
page browsing
function is
enabled) during
the page display
phase.
PS 12.1
Page Browsing
Delay
[0,+)
Page Display
Delay = Page
end time - Page
start time - Page
Response Delay
PS 12.1
The page
display delay
starts when SP
responds with
"2**, 304".
Issue 03 (2015-07-30)

3599
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Response
Delay
[0,+)
Time when the

first page DNS
request is
responded to
relative to the
time when the
main page
request is
responded to.
PS 12.1
If no page DNS
is available, this
parameter
indicates the
time when the
first page syn is
responded to
relative to the
time when the
main page
request is
responded to. If
no page TCP
connection is
available, this
parameter
indicates the
time when the
first page
request is
responded to
relative to the
time when the
main page
request is
responded to.
The value of
Page Response
Code must be
2**, 304, 4**,
5**, 600, 601,
602, or 0xFFFF.
When the value
of Page
Response
Result is 2**,
304, 4**, or 5**,
Issue 03 (2015-07-30)

3600
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Page DNS
Response Delay
is equal to Page
Response
Offset. When
the value of
Page Response
Result is 600,
601, 602, or
0xFFFF, Page
DNS Response
Delay is equal to
Page Request
Offset.
>Page DNS
Response Delay
[0,+)
Page DNS
response delay.
PS 12.1
Page DNS refers

to the DNS
when the first
event of an xDR
is a DNS request
or response
events.
>SYN to SYN
ACK Delay
Issue 03 (2015-07-30)
[0,+)
Delay between
the time when
the first page
syn packet is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first or
second
handshake fails,
the value of this
parameter is 0.

PS 12.1
3601
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>SYN ACK to
First ACK
Delay
[0,+)
Delay between
the time when
the first page
syn ack packet is
responded to
and the time
when the first
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
>SYN ACK to
Last Ack Delay
[0,+)
Delay between
the time when
the first page
syn ack packet is
responded to
and the time
when the last
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
>ACK to Get
Delay
[0,+)
Delay between
the time when
the last page ack
packet of TCP
connection is
responded to
and the time
when the first
page get packet
is responded to.
If the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

3602
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Page Display
Delay
[0,+)
Page Display
Delay = Page
end time - Page
start time - Page
Response Delay
PS 12.1
The page
display delay
starts when SP
responds with
"2**, 304".
Issue 03 (2015-07-30)
TCP DL Total
Traffic
[0,+)
Byte
Total TCP
downlink data
volume refers to
the total size of
all TCP
downlink
payload
packets,
including
retransmitted
packets, during
the page display
phase (between
the time when
the main page
request is
responded to
and the time
when the page
browsing
function is
disabled).
PS 12.1
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
TCP UL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1

3603
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1
TCP UL Total
Packets
[0,+)
Number
Total number of
all TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
[0,+)
Number
Number of
disordered TCP
uplink packets.
PS 12.1
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times when the
uplink TCP
window is set to
0 during the
page display
phase.
PS 12.1

3604
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Upstream
Packet Loss
Count
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.
Downstream
Packet Loss
Count
[0,+)
Number
Downstream
means below the
Iu-PS interface
(below the
RAN).
PS 12.1
Number of
times that
packets are lost
on the
downstream
during the page
display phase.
Issue 03 (2015-07-30)
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
TCP SYN Max

Window Size
N/A
N/A
Maximum size
of the SYN
window of the
page.
PS 12.1
TCP SYN Min

Window Size
N/A
N/A
Minimum size
of the SYN
window.
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.

3605
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP DL Max
Send Window
N/A
N/A
Downlink
sending window
of the maximum
size.
PS 12.1
Parameters for Viewing PS Core Complaint Analysis Support Results - Video Streaming
(UGW)
This section describes the parameters for querying complaint analysis support (video streaming)
results. You can refer to the description when querying complaint analysis support (video
streaming) results.
Detailed Information--Overall Streaming Info

Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming DNS
Response Offset
[0,+)
Offset between
the time when
the video
streaming DNS
responds and the
time when video
streaming starts.
PS 12.1
Video
streaming DNS
refers to the
DNS when the
first event of the
video streaming
is a DNS request
or response
event.
Issue 03 (2015-07-30)

3606
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming TCP
SYN Offset
[0,+)
Offset between
the time when
the first TCP
handshake of
video streaming
occurs and the
time when video
streaming starts.
PS 12.1
Video
streaming TCP
connection
refers to the first
TCP connection
of the video
streaming.
Before this
connection, no
HTTP requests
are initiated.
Time when the
first TCP
handshake of
video streaming
occurs refers to
the time when
the first syn
packet of video
streaming TCP
connection is
responded to.
Issue 03 (2015-07-30)

3607
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming TCP
SYN ACK
Offset
[0,+)
Offset between
the time when
the second TCP
handshake of
video streaming
occurs and the
time when video
streaming starts.
PS 12.1
Video
streaming TCP
connection
refers to the first
TCP connection
of the video
streaming.
Before this
connection, no
HTTP requests
are initiated.
Time when the
second TCP
handshake of
video streaming
occurs refers to
the time when
the first syn ack
packet of video
streaming TCP
connection is
responded to.
Issue 03 (2015-07-30)

3608
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming TCP
ACK Offset
[0,+)
Offset between
the time when
the third TCP
handshake of
video streaming
and the time
when video
streaming starts.
PS 12.1
Video
streaming TCP
connection
refers to the first
TCP connection
of the video
streaming.
Before this
connection, no
HTTP requests
are initiated.
Time when the
third TCP
handshake of
video streaming
occurs refers to
the time when
the last ack
packet of video
streaming TCP
connection is
responded to.
Issue 03 (2015-07-30)

3609
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming First
Request Offset
[0,+)
Offset between
the time when
the first request
of video
streaming is
initiated and the
time when video
streaming is
started.
PS 12.1
The scenario
where no video
streaming
requests are
initiated (that is,
DNS parsing or
TCP connection
of the video
streaming fails)
is not
considered
because video
streaming xDRs
do not exist.
Video
Streaming First
Response Offset
Issue 03 (2015-07-30)
[0,+)
Offset between
the time when
the first request
of video
streaming is
responded to
between the
time when video
streaming starts.

PS 12.1
3610
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming TCP
Release Offset
[0,+)
Offset between
the time when
the video
streaming TCP
connection is
released and the
time when video
streaming starts.
PS 12.1
Video
streaming TCP
connection
release means
that the
quintuple of the
video streaming
TCP connection
releases the TCP
connection.
Issue 03 (2015-07-30)
Video
Streaming
Format
N/A
N/A
Format of video
streaming, such
as FLV, MP4,
3GP, and TS.
PS 12.1
Video
Streaming Total
Size
[0,+)
Byte
Total size of
multiple
segmented
videos after the
videos are
combined.
PS 12.1
Video
Streaming Total
Duration
hh: mm: ss
N/A
Total duration
of multiple
segmented
videos after the
videos are
combined.
PS 12.1

3611
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Segment Bit
Rate
[0,+)
Kbps
Segment code
rate of video
streaming.
PS 12.1
Video
Streaming
Average Bit
Rate
[0,+)
Kbps
Video
Streaming
Average Bit
Rate = (Video
Streaming Start
TCP DL Total
Traffic + Video
Streaming Play
TCP DL Total
Traffic) x 8/
Time that video
streaming can
be played/
10241000.
PS 12.1
Video
Streaming Bit
Rate Obtain
Method
1_Normally Get
Bit Rate
N/A
Method of
obtaining the
video streaming
code rate.
PS 12.1
If multiple flows
of a video
streaming
medium are
transmitted, pay
attention to code
rates of the first
five flows.
2_URI Get
Video Size
Calculate Bit
Rate(Chunk)
3_Chunk
Length
Calculate Bit
Rate
4_Cannot Get
Bit Rate and
Calculate Bit
Rate(Fixed
Size)
5_Same UE IP
and URI Key Bit
Rate
Issue 03 (2015-07-30)

3612
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Transfer
Method
Download,
Non-download
N/A
Transfer mode
of video
streaming.
PS 12.1
Video
Streaming
Merge Method
N/A
N/A
Method of
merging video
segments. This
method is used
only by Huawei
technical
support
engineers.
PS 12.1
Video
Streaming
Finish State
Flag
Finish normally,
Finish with stall
state
N/A
States of
finished video
streaming
playing,
including the
normal state and
pause state.
PS 12.1
Detailed Information--Initial Buffer Period
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
TCP DL Total
Traffic
[0,+)
Byte
Total size of all

TCP downlink
payload
packets,
including
retransmitted
packets, during
the video
streaming
buffering phase
(between the
time when the
first video
streaming
request is
responded to
and the time
when the video
streaming
buffering ends).
PS 12.1

3613
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
Video
Streaming Start
TCP DL
Retransmission
Count
[0,+)
Number
Number of TCP
downlink
retransmitted
packets.
PS 12.1
Video
Streaming Start
TCP DL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
downlink
retransmitted
packets.
PS 12.1
Video
Streaming Start
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
Video
Streaming Start
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1
Video
Streaming Start
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
Video
Streaming Start
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1

3614
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
TCP
Downstream
Total RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Total RTT
Delay
(Accurate) =
Sum of
TCP_DL_Trans
_RTT of all
HTTP response
completion
events of video
streaming.
PS 12.1
Video
Streaming Start
TCP
Downstream
Total RTT
Count
(Accurate)
[0,+)
Number
TCP
Downstream
Total RTT
Count
(Accurate) =
Sum of
TCP_DL_Trans
_RTT_Count of
all HTTP
response
completion
events of video
streaming.
PS 12.1
Video
Streaming Start
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times when the
uplink TCP
window is set to
0 during the
video streaming
display phase.
PS 12.1
Video
Streaming Start
Upstream
Packet Loss
Count
[0,+)
Number
Number of
times that
upstream
packets are lost
during the video
streaming
display phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Issue 03 (2015-07-30)

3615
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
Downstream
Packet Loss
Count
[0,+)
Number
Number of
times that
downstream
packets are lost
during the video
streaming
display phase.
PS 12.1
Downstream
means below the
Iu-PS interface
(below the
RAN).
Video
Streaming Start
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Number of
times that
upstream
packets are lost
due to packet
retransmission
during the initial
buffering of
video
streaming.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Issue 03 (2015-07-30)
Video
Streaming Start
TCP Max
Window Size
N/A
N/A
Maximum size
of the SYN
window of
video
streaming.
PS 12.1
Video
Streaming Start
TCP Min
Window Size
N/A
N/A
Minimum size
of the SYN
window of
video
streaming.
PS 12.1
Video
Streaming Start
TCP DL
Transfer Time
[0,+)
TCP downlink
transfer time.
PS 12.1

3616
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Accumulated
Time Difference
Between Video
Streaming Start
Segments
[0,+)
Accumulated
time difference
between
adjacent
segments during
the initial
buffering phase.
PS 12.1
Abnormal
Video
Streaming Start
TCP DL
Continuous
Timeout
Retransmission
Count at
Interval(0~4s]
[0,+)
Number
Number of
times that
downlink
continuous
retransmission
time of a
quintuple flow
is abnormal
within the time
range (0-4s].
PS 12.1
Abnormal
Video
Streaming Start
TCP DL
Continuous
Timeout
Retransmission
Count at
Interval
(4s~10s]
[0,+)
Number
Number of
times that
downlink
continuous
retransmission
time of a
quintuple flow
is abnormal
within the time
range (4-10s].
PS 12.1
Abnormal
Video
Streaming Start
TCP DL
Continuous
Timeout
Retransmission
Count at
Interval(>10s)
[0,+)
Number
Number of
times that
downlink
continuous
retransmission
time of a
quintuple flow
is abnormal and
is longer than
10s.
PS 12.1
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(0~300ms]
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
within the range
(0-300 ms].
PS 12.1

3617
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(300~500ms]
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
within the range
(300-500 ms].
PS 12.1
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(500~1000ms]
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
within the range
(500-1000 ms].
PS 12.1
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(1000~5000ms]
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
within the range
(1000-5000
ms].
PS 12.1
Abnormal
Video
Streaming Start
TCP
Downstream
RTT Count at
Interval
(>5000ms)
[0,+)
Number
Number of
times that TCP
Downlink RTT
(Accurate) is
more than 5000
ms.
PS 12.1
Video
Streaming Start
TCP DL Max
Send Window
N/A
N/A
Downlink
sending window
of the maximum
size.
PS 12.1

3618
Nastar
Detailed Information--Streaming Play Info

Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Troubleshootin
g Time Segment
[0,+)
Number
Number of time
segments for
locating
problems.
PS 12.1
Video
Streaming
Troubleshootin
g Start Time

xxx
N/A
Time when a
time segment
for locating
problems starts
(UTC).
PS 12.1
Video
Streaming
Troubleshootin
g End Time

xxx
N/A
Time when a
time segment
for locating
problems ends
(UTC).
PS 12.1
Abnormal
Video
Streaming P3
Stall Delay
Count
[0,+)
Number
Number of
times that the
duration of a
pause exceeds
the threshold.
PS 12.1
You can set the

threshold. The
default value is
8000 ms.
Accumulated
Time Difference
Between Video
Streaming Play
Segments
N/A
Accumulated
time difference
between
adjacent
segments during
the video
streaming
playing phase.
PS 12.1
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
Delay
[0,+)
Initial buffering
delay of video
streaming.
PS 12.1

3619
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Start
Result
Video
Streaming Start
Success
N/A
Result of video
streaming
playing.
PS 12.1
Video
Streaming Start
Failure:
Response
Failure
Video
Streaming Start
Failure: No Bit
Rate
Video
Streaming Start
Failure: Server
Abnormal
Release
Video
Streaming Start
Failure:
Terminal
Intentionally
Release
Video
Streaming Start
Failure:
Timeout
Video
Streaming Start
Failure:
Redirect Failure
Video
Streaming Start
Failure: No Bit
Rate and
Downloaded
Data Exceeds
200 KB
Video
Streaming Start
Failure: Others
Issue 03 (2015-07-30)

3620
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Access Delay
[0,+)
Time when
video streaming
is started
relative to the
time when the
first request of
video streaming
is responded to.
The response
code of the first
request of video
streaming must
be 2**, The TS
flow and m3u8
request scenario
is included.
PS 12.1
Video
Streaming Play
Duration
[0,+)
Duration of
playing video
streaming.
PS 12.1
Video
Streaming Stall
Count
[0,+)
Number
Number of
pauses when
video streaming
is played.
PS 12.1
Video
Streaming Stall
Total Delay
[0,+)
Total duration
of pauses when
video streaming
is played.
PS 12.1
Video
Streaming
Download
Throughput
[0,+)
kbit/s
Download rate
of video
streaming.
PS 12.1
Video
Streaming P3
Stall Count
[0,+)
Number
Number of
times that the
duration of a
pause exceeds
the threshold.
PS 12.1
You can set the

threshold. The
default value is
300 ms.
Video
Streaming Play
Flag
Issue 03 (2015-07-30)
Success/Failure
N/A
Identifier of
video streaming
playing.

PS 12.1
3621
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming
Response Delay
[0,+)
Response delay
of video
streaming.
PS 12.1
>Video
Streaming DNS
Response Delay
[0,+)
DNS response
time of video
streaming.
PS 12.1
Video
streaming DNS
refers to the
DNS when the
first event of an
xDR is a DNS
request or
response event.
Issue 03 (2015-07-30)
>Video
Streaming SYN
to SYN ACK
Delay
[0,+)
Delay between
the time when
the first video
streaming syn
packet is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first or
second
handshake fails,
the value of this
parameter is 0.
PS 12.1
>Video
Streaming SYN
ACK to First
ACK Delay
[0,+)
Delay between
the time when
the first video
streaming syn
ack packet is
responded to
and the time
when the first
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1

3622
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
>Video
Streaming SYN
ACK to Last
ACK Delay
[0,+)
Delay between
the time when
the first video
streaming syn
ack packet is
responded to
and the time
when the last
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
>Video
Streaming ACK
to Get Delay
[0,+)
Delay between
the time when
the last video
streaming ack
packet of TCP
connection is
responded to
and the time
when the first
video streaming
get packet is
responded to. If
the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

3623
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Play
TCP DL Total
Traffic
[0,+)
Byte
Total TCP
downlink data
volume refers to
the total size of
all TCP
downlink
payload
packets, during
the video
streaming
display phase
(between the
time when video
streaming starts
being played
and the time
when video
streaming stops
being played).
PS 12.1
Video
Streaming Play
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
Video
Streaming Play
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
Video
Streaming Play
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1
Video
Streaming Play
TCP DL
Transfer Time
[0,+)
TCP downlink
transfer time.
PS 12.1

3624
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Play
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
Video
Streaming Play
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downlink RTT
delay
(accurate)/
Number of
packets whose
accurate
downlink RTT
delay is not 0
(accurate).
PS 12.1
Video
Streaming Play
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times when the
uplink TCP
window is set to
0 during the
video streaming
display phase.
PS 12.1
Video
Streaming Play
Upstream
Packet Loss
Count
[0,+)
Number
Number of
times that
upstream
packets are lost
during the video
streaming
display phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Issue 03 (2015-07-30)

3625
Nastar
Parameter
Range
Unit
Description
Supported NE
Version
Video
Streaming Play
Downstream
Packet Loss
Count
[0,+)
Number
Number of
times that
downstream
packets are lost
during the video
streaming
display phase.
PS 12.1
Downstream
means below the
Iu-PS interface
(below the
RAN).
Video
Streaming Play
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Video
Streaming Play
TCP Max
Window Size
N/A
N/A
Maximum size
of the SYN
window of
video
streaming.
PS 12.1
Video
Streaming Play
TCP Min
Window Size
N/A
N/A
Minimum size
of the SYN
window of
video
streaming.
PS 12.1
Video
Streaming Play
TCP DL Max
Send Window
N/A
N/A
Downlink
sending window
of the maximum
size during the
video streaming
playing phase.
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.
Parameters for Viewing PS Core Complaint Analysis Support Results - Email Send (UGW)
send) results. You can refer to the description when querying PS Core complaint analysis support
(email send) results.
Issue 03 (2015-07-30)

3626
Nastar

Parameter
Range
Unit
Description
Supported Solution
Version
Email Send Flag
Email
Send
N/A
Email sending
identifier.
PS 12.1
Email Login
DNS Response
Offset
[0,+)
Offset between the

time when the email
login DNS responds
and the time when
email transmission
starts.
PS 12.1

address of the email
server and then find the
DNS.
TCP SYN
Offset
[0,+)
Offset between the

time when the first
and the time when
email transmission
starts.
PS 12.1
Time when the first

TCP handshake of
email transmission
packet of TCP
connection is
responded to during
email login.
TCP SYN ACK
Offset
[0,+)
Offset between the

time when the second
and the time when
email transmission
starts.
PS 12.1

TCP handshake of
email transmission
ack packet of TCP
connection is
responded to during
email login.
Issue 03 (2015-07-30)

3627
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
TCP ACK
Offset
[0,+)
Offset between the

time when the third
and the time when
email transmission
starts.
PS 12.1

TCP handshake of
email transmission
time when the last ack
packet of TCP
connection is
responded to during
email login.
Issue 03 (2015-07-30)
Email Login
First Request
Offset
[0,+)
Offset between the

time when an email
login request is
initiated and the time
when email
PS 12.1
Email Login
First Response
Offset
[0,+)
Offset between the

time when an email
login request is
responded to and the
time when email
PS 12.1
Email TCP
Release Offset
[0,+)
Offset between the

time when the email
transmission TCP
connection is released
and the time when
email transmission
starts. Email
transmission TCP
connection release
means that the
quintuple of the email
transmission TCP
TCP connection.
PS 12.1

3628
Nastar
Detailed Information--Email Send Info

Parameter
Range
Unit
Description
Supported
Solution
Version
Email Send
Request Count
[0,65535]
Numb
er

initiated when an email
is sent once.
PS 12.1
Email Request
Valid Count
[0,65535]
Numb
er

initiated, excluding the
request terminated by a
subscriber or server, or
the request that expires.
PS 12.1
Email Request
Success Count
[0,65535]
Numb
er

responded to when an
email is sent once.
PS 12.1
Email Integrity
Send Count
[0,+)
Numb
er

email sending events are
intact during the email
transmission phase.
PS 12.1
Wireless
Effective
Throughput
[0,+)
kbit/s
Effective transmission
rate on the RAN side.
PS 12.1
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
DNS Response
Delay
[0,+)
If DNS request
and response
events exist in
email login,
Email Login
DNS Response
Delay is equal to
DNS_Response
_Duration of the
events.
PS 12.1

3629
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
Response
Result
Success/Failure
N/A
Result of
responding to an
email login
request.
PS 12.1
>Email Login
Response Code
N/A
N/A
Response code
of an email login
request.
PS 12.1
Email Receive
Success Indictor
Success/Failure
N/A
Indicator of
email login
success. Email
login succeeds
when a TCP
connection
setup event
succeeds and
login
authentication
succeeds once
during email
login.
PS 12.1
First Send Email

Response Code
N/A
N/A
Send first email

response code.
PS 12.1
Email Size
[0,+)
Byte
Total size of all

nonretransmission
packets during
the email
transmission
phase (between
the time when
an email
sending request
is responded to
and the time
when email
transmission
ends).
PS 12.1

3630
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Send
Transfer Delay
[0,+)
Valid time for

transmitting
data during the
email sending
phase (between
the time when
the first email
sending request
is responded to
and the time
when email
transmission
ends).
PS 12.1
Email Send
Throughput
[0,+)
kbit/s
Average
transmission
rate of email
sending during
the email
sending phase.
PS 12.1
Email Login
Response Delay
[0,+)
Time when the

first email login
DNS request is
responded to
relative to the
time when the
last login
request is
responded to.
PS 12.1
If no DNS is
available, this
parameter
indicates the
time when the
first syn request
is responded to
relative to the
time when the
last login
request is
responded to.
Issue 03 (2015-07-30)

3631
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>Email Login
SYN to SYN
ACK Delay
[0,+)
Delay between
the time when
the first syn
packet of email
login is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first
handshake fails,
the value of this
parameter is 0.
PS 12.1
>Email Login
SYN ACK to
First Ack Delay
[0,+)
Delay between
the time when
the first syn ack
packet of email
login is
responded to
and the time
when the first
ack packet is
responded to. If
the second
handshake fails,
the value of this
parameter is 0.
PS 12.1
>Email Login
ACK to First
Data Delay
[0,+)
Delay between
the time when
the last ack
packet of email
login TCP
connection is
responded to
and the time
when the first
email login
request is
responded to. If
the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

3632
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Email Login
TCP
Connection
Delay
[0,+)
Scenario 1:
Email Login
TCP
Connection
Delay is the time
when the first
email login
request is
responded to
relative to the
time when the
last payload
packet is
responded to
during email
login when the
third handshake
does not occur.
PS 12.1
Scenario 2:
Email Login
TCP
Connection
Delay is the time
when the first
email login
request is
responded to
relative to the
time when the
first TCP
handshake of
email login
occurs when the
third handshake
occurs.
Scenario 3: The
value of Email
Login TCP
Connection
Delay is 0 when
the email server
connection
times out and no
response packet
is available.
Issue 03 (2015-07-30)

3633
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Scenario 4:
Email Login
TCP
Connection
Delay is the time
when the last
payload packet
is responded to
relative to the
time when the
first TCP
handshake of
email login
occurs during
email login
when the email
server
connection
times out and
the response
packet is
available.
Issue 03 (2015-07-30)
>Email Server
Process Delay
[0,+)
Delay in the
email server's
responding to
the first login
request.
PS 12.1
Email Server
Process
Average Delay
[0,+)
Delay between
the time when
the smtp from
request is
responded to
and the time
when the DATA
request is
responded to
during email
sending.
PS 12.1

3634
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SMTP Data
Delay
[0,+)
Delay between
the time when
the smtp from
request is
responded to
and the time
when the DATA
request is
responded to
during email
sending.
PS 12.1
TCP DL Total
Traffic
[0,+)
Byte
Total size of
TCP downlink
payload
packets,
including
retransmitted
packets, during
the email
sending phase.
PS 12.1
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Count
[0,+)
Number
Number of TCP
downlink
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
downlink
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1

3635
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP UL Total
Packets
[0,+)
Number
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL Total
Traffic
[0,+)
Byte
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Count
[0,+)
Number
Number of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
uplink packets.
PS 12.1
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1

3636
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP Upstream
Average RTT
Delay
(Accurate)
[0,+)
TCP Upstream
Average RTT
Delay
(Accurate) =
Packet upstream
RTT delay
(accurate)/
Number of
packets whose
accurate
upstream RTT
delay is not 0
(accurate).
PS 12.1
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times that the
uplink TCP
window is set to
0 during the
email sending
phase.
PS 12.1
Upstream
Packet Loss
Count
[0,+)
Number
Number of
times that
upstream
packets are lost
due to packet
retransmission
during the email
sending phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Number of
times that
upstream
packets are lost
during the email
sending phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Issue 03 (2015-07-30)

3637
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Upstream
Packet Loss
Ratio
[0.00,100.00]
Proportion of
TCP uplink
packet loss.
PS 12.1
Downstream
Packet Loss
Count
[0,+)
Number
Number of
times that
downstream
packets are lost
during the email
transmission
phase.
PS 12.1
Downstream
means below the
Iu-PS interface
(below the
RAN).
TCP Max
Window Size
N/A
N/A
Maximum size
of the window
during the email
transmission
phase.
PS 12.1
TCP Min
Window Size
N/A
N/A
Maximum size
of the window
during the email
transmission
phase.
PS 12.1
Parameters for Viewing PS Core Complaint Analysis Support Results - Email Receive
(UGW)
receive) results. You can refer to the description when querying PS Core complaint analysis
support (email receive) results.
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Receive
Flag
Email Receive
N/A
Identifier of email receiving.
PS 12.1

3638
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
DNS Response
Offset
[0,+)
Time when email login DNS

starts.
PS 12.1

address of the email server
and then find the DNS.
TCP SYN
Offset
[0,+)

when the first TCP
time when email
PS 12.1

handshake of email
responded to.
TCP SYN ACK
Offset
[0,+)

when the second TCP
time when email
PS 12.1

handshake of email
ack packet of TCP
connection is responded to
during email login.
TCP ACK
Offset
[0,+)

when the third TCP
time when email
PS 12.1

handshake of email
the time when the last ack
responded to during email
login.
Issue 03 (2015-07-30)

3639
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
First Request
Offset
[0,+)

starts.
PS 12.1
Email Login
First Response
Offset
[0,+)

is responded to and the time
starts.
PS 12.1
Email TCP
Release Offset
[0,+)

when the email transmission
TCP connection is released
and the time when email
transmission starts. Email
transmission TCP
connection release means
that the quintuple of the
email transmission TCP
connection.
PS 12.1
Detailed Information--Email Receive Info
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supporte
d
Solution
Version
Email Receive
Request Count
[0,+)
Numbe
r

receiving request is initiated
when an email is received
once.
PS 12.1
Email Request
Valid Count
[0,+)
Numbe
r

receiving request is initiated,
excluding the request
terminated by a subscriber or
server, or the request that
expires.
PS 12.1

3640
Nastar
Parameter
Range
Unit
Description
Supporte
d
Solution
Version
Email Request
Success Count
[0,+)
Numbe
r

receiving request is responded
to when an email is received
once.
PS 12.1
Email Integrity
Receive Count
[0,+)
Numbe
r

receiving event is integral
during the email transmission
phase.
PS 12.1
Wireless
Effective
Throughput
[0,+)
kbit/s

the RAN side.
PS 12.1
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Login
DNS Response
Delay
[0,+)
If DNS request
and response
events exist in
email login,
Email Login
DNS Response
Delay is equal to
DNS_Response
_Duration of the
events.
PS 12.1
Email Login
Response
Result
Success/Failure
N/A
Result of
responding to an
email login
request.
PS 12.1
>Email Login
Response Code
N/A
N/A
Response code
of an email login
request.
PS 12.1
Comprehensive Complaints
Issue 03 (2015-07-30)

3641
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Receive
Success Indictor
Success/Failure
N/A
Indicator of
email login
success. Email
login succeeds
when a TCP
connection
setup event
succeeds and
login
authentication
succeeds once
during email
login. In other
scenarios, email
login fails.
PS 12.1
>Receive First
Email Response
Code
N/A
N/A
Receive First
Email Response
Code.
PS 12.1
Email Size
[0,+)
Byte
Total size of all

nonretransmission
packets during
the email
transmission
phase (between
the time when
an email
receiving
request is
responded to
and the time
when email
transmission
ends).
PS 12.1

3642
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Email Receive
Transfer Delay
[0,+)
Valid time for

transmitting
data during the
email receiving
phase (between
the time when
the first email
receiving
request is
responded to
and the time
when email
transmission
ends).
PS 12.1
Email Receive
Throughput
[0,+)
kbit/s
Average
transmission
rate of email
receiving during
the email
receiving phase.
PS 12.1
Email Login
Response Delay
[0,+)
Time when the

first email login
DNS request is
responded to
relative to the
time when the
last login
request is
responded to.
PS 12.1
If no DNS is
available, this
parameter
indicates the
time when the
first syn request
is responded to
relative to the
time when the
last login
request is
responded to.
Issue 03 (2015-07-30)

3643
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>Email Login
SYN to SYN
ACK Delay
[0,+)
Delay between
the time when
the first syn
packet of email
login is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first
handshake fails,
the value of this
parameter is 0.
PS 12.1
>Email Login
SYN ACK to
First Ack Delay
[0,+)
Delay between
the time when
the first syn ack
packet of email
login is
responded to
and the time
when the first
ack packet is
responded to. If
the second
handshake fails,
the value of this
parameter is 0
PS 12.1
>Email Login
ACK to First
Data Delay
[0,+)
Delay between
the time when
the last ack
packet of email
login TCP
connection is
responded to
and the time
when the first
email login
request is
responded to. If
the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

3644
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Email Login
TCP
Connection
Delay
[0,+)
Scenario 1:
Email Login
TCP
Connection
Delay is the time
when the first
email login
request is
responded to
relative to the
time when the
last payload
packet is
responded to
during email
login when the
third handshake
does not occur.
PS 12.1
Scenario 2:
Email Login
TCP
Connection
Delay is the time
when the first
email login
request is
responded to
relative to the
time when the
first TCP
handshake of
email login
occurs when the
third handshake
occurs.
Scenario 3: The
value of Email
Login TCP
Connection
Delay is 0 when
the email server
connection
times out and no
response packet
is available.
Issue 03 (2015-07-30)

3645
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Scenario 4:
Email Login
TCP
Connection
Delay is the time
when the last
payload packet
is responded to
relative to the
time when the
first TCP
handshake of
email login
occurs during
email login
when the email
server
connection
times out and
the response
packet is
available.
Issue 03 (2015-07-30)
>Email Server
Process Delay
[0,+)
Delay in the
email server's
responding to
the first login
request.
PS 12.1
Email Server
Process
Average Delay
[0,+)
Delay between
the time when
the smtp from
request is
responded to
and the time
when the DATA
request is
responded to
during email
receiving.
PS 12.1

3646
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP DL Total
Traffic
[0,+)
Byte
Total size of
TCP downlink
payload
packets,
including
retransmitted
packets, during
the email
receiving phase.
PS 12.1
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Count
[0,+)
Number
Number of TCP
downlink
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
downlink
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
downlink
packets.
PS 12.1
TCP UL Total
Packets
[0,+)
Number
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1

3647
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP UL Total
Traffic
[0,+)
Byte
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Count
[0,+)
Number
Number of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Traffic
[0,+)
Byte
Sum of the data

volume of TCP
uplink
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
uplink packets.
PS 12.1
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1

3648
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP Upstream
Average RTT
Delay
(Accurate)
[0,+)
TCP Upstream
Average RTT
Delay
(Accurate) =
Packet upstream
RTT delay
(accurate)/
Number of
packets whose
accurate
upstream RTT
delay is not 0
(accurate).
PS 12.1
Upstream
Packet Loss
Count
[0,+)
Number
Number of
times that
upstream
packets are lost
due to packet
retransmission
during the email
receiving phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
[0,+)
Number
Number of
times that
upstream
packets are lost
during the email
receiving phase.
PS 12.1
Upstream
means above the
Iu-PS interface
(above the CN).
Upstream
Packet Loss
Ratio
Issue 03 (2015-07-30)
[0.00,100.00]
Proportion of
TCP uplink
packet loss.

PS 12.1
3649
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Downstream
Packet Loss
Count
[0,+)
Number
Number of
times that
downstream
packets are lost
during the email
receiving phase.
PS 12.1
Downstream
means below the
Iu-PS interface
(below the
RAN).
TCP Max
Window Size
N/A
N/A
Maximum size
of the window
during the email
receiving phase.
PS 12.1
TCP Min
Window Size
N/A
N/A
Minimum size
of the window
during the email
receiving phase.
PS 12.1
Parameters for Viewing PS Core Complaint Analysis Support Results - File Access(UGW)
This section describes the parameters for querying complaint analysis support (file access)
results. You can refer to the description when querying complaint analysis support (file access)
results.
Detailed Information--File Transfer Overall Info

Parameter
Range
Unit
Description
Supported
Solution
Version
File Upload and

Download Flag
Downl
oad
N/A
File upload/download identifier.

Currently, only file download is
supported.
PS 12.1
File Transfer
DNS Response
Offset
[0.00,
+)
Time when the file transfer DNS

when file transfer starts.
PS 12.1
File transfer DNS refers to the

DNS when the first event of file
transfer is a DNS request or
response event.
Issue 03 (2015-07-30)

3650
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
TCP SYN
Offset
[0.00,
+)

first TCP handshake of file
PS 12.1

are initiated.
syn packet of file transfer TCP
File Transfer
TCP SYN ack
Offset
[0.00,
+)

second TCP handshake of file
PS 12.1

are initiated.
syn ack packet of file transfer
TCP connection is responded to.
File Transfer
TCP ack Offset
[0.00,
+)

third TCP handshake of file
PS 12.1

are initiated.
Time when the third TCP
refers to the time when the last
ack packet of file transfer TCP
Issue 03 (2015-07-30)

3651
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
First Request
Offset
[0.00,
+)

PS 12.1

If no file transfer request exists,
file transfer DNS parsing fails.
File Transfer
First Response
Offset
[0.00,
+)

PS 12.1

File Transfer
First Redirect
Request Offset
[0.00,
+)

PS 12.1
File Transfer
First Redirect
Response Offset
[0.00,
+)

PS 12.1
File Transfer
Request Offset
[0.00,
+)

PS 12.1

response code
(FileAccess_Response_Result)
can be only 2**, 304, 4**, 5**,
600, 601, and 0xFFFF.
Issue 03 (2015-07-30)

3652
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Response Offset
[0.00,
+)

PS 12.1

response code
(HTTP_Response_Result) can
be only 2**, 3**, 4**, 5**, 600,
601, and 0xFFFF. (For POST
upload, the time when the main
request is responded to indicates
the offset between the time when
the ack packet corresponding to
the main request is received and
the time when file transfer starts.)
File Transfer
TCP Release
Offset
[0.00,
+)

release means that the quintuple
of the file transfer TCP
connection.
PS 12.1
File Transfer
End Offset
[0.00,
+)
Offset between the time when file

transfer ends and the time when
PS 12.1
The ending of file transfer means

that the file transfer DNS request
fails to be responded to or times
out.
Detailed Information--File Request Response Phase Info
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Request
Redirect
Success Count
[0,+)
Numbe
r

succeeds when the file transfer
request is responded to.
PS 12.1

redirection exists.

3653
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Request
Redirect Failure
Count
[0,+)
Numbe
r

fails when the file transfer request
is responded to.
PS 12.1
File Transfer No
Response Wait
Time
hh:
mm: ss

redirection exists.
N/A
Time when subscribers actively

terminates file transfer (a UE sends
RST or FIN first) relative to the
time when SYNC appears if there
is no file transfer response.
PS 12.1
Detailed Information--File Transfer Phase Info
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Request Count
[0,65535]
Numb
er

requests are responded to during
the file transfer phase (between
the time when the main file
transfer request is responded to
and the time when file transfer
ends).
PS 12.1
File Transfer
Request Success
Count
[0,65535]
Numb
er

FileAccess_Response_Result is
equal to 2**, 304 during file
transfer request and response
events.
PS 12.1

3654
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Valid Request
Count
[0,65535]
Numb
er

requests whose response code is
2**, 3**, 4**, or 5** are
responded to during the file
transfer phase (between the time
when the main page request is
the page browsing function is
disabled).
PS 12.1
Effective requests refer to the

requests that are responded to,
excluding the request terminated
by a subscriber or server, or the
request that expires.
File Transfer
Integrity Count
[0,+)
Numb
er

succeeds.
PS 12.1
File Transfer
Total Count
[0,+)
Numb
er
File Transfer Total Count = File

Transfer Integrity Count +
fails.
PS 12.1
File Transfer
Redirect Failure
Count
[0,+)
Numb
er

fails during the file transfer phase
(for file download only)
PS 12.1
Wireless
Effective
Throughput
[0,+)
kbit/s
Effective transmission rate on the

RAN side.
PS 12.1
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Response
Succeed
Indictor
Success/Failure
N/A
Result of
responding to a
file transfer
request.
PS 12.1
File Transfer
Response Result
N/A
N/A
Response code
of a main file
transfer request.
PS 12.1

3655
Nastar
Parameter
Issue 03 (2015-07-30)
Range
Unit
Description
Supported
Solution
Version
File Transfer
Success/Failure
Success Indictor
N/A
File transfer
succeeds only
when the main
file transfer
request is
successfully
responded to.
PS 12.1
File Transfer
Size
[0,+)
Byte
Total size of
uplink/
downlink nonretransmitted
packets during
the file transfer
phase (between
the time when
the main file
transfer request
is responded to
and the time
when file
transfer ends).
PS 12.1
File Transfer
Throughput
[0,+)
kbit/s
Average
transmission
rate during the
file transfer
phase (between
the time when
the main file
transfer request
is responded to
and the time
when file
transfer ends).
PS 12.1

3656
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Response Delay
[0,+)
Time when the

first file transfer
DNS request is
responded to
relative to the
time when the
main file
transfer request
is responded to.
If no file transfer
DNS is
available, this
parameter
indicates the
time when the
first file transfer
syn is responded
to relative to the
time when the
main file
transfer request
is responded to.
If no file transfer
TCP connection
is available, this
parameter
indicates the
time when the
first request is
responded to
relative to the
time when the
main file
transfer request
is responded to.
The value of
File Transfer
Response Code
must be 2**,
3**, 4**, 5**,
600, 601, or
0xFFFF.
PS 12.1
>File Transfer
DNS Response
Delay
[0,+)
Delay in
responding to
the file transfer
DNS request.
PS 12.1

3657
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
SYN to SYN
ACK Delay
[0,+)
Delay between
the time when
the first file
transfer syn
packet is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first or
second
handshake fails,
the value of this
parameter is 0.
PS 12.1
>File Transfer
SYN ACK to
First ACK
Delay
[0,+)
Delay between
the time when
the first file
transfer syn ack
packet is
responded to
and the time
when the first
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
>File Transfer
SYN ACK to
Last ACK Delay
[0,+)
Delay between
the time when
the first file
transfer syn ack
packet is
responded to
and the time
when the last
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1

3658
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
ACK to First
Data Delay
[0,+)
Delay between
the time when
the last ack
packet of the file
transfer TCP
connection is
responded to
and the time
when the first
payload packet
of file transfer is
responded to. If
the third
handshake fails,
the value of this
parameter is 0.
PS 12.1

3659
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
Max SYN to
SYN ACK
Delay
[0,+)
Delay between
the time when
the file transfer
syn packet is
responded to
and the time
when the first
syn ack packet is
responded to. If
the first or
second
handshake fails,
the value of this
parameter is 0.
PS 12.1
Note:
Redirection
occurs for
multiple times
when the file
transfer request
is responded to.
The third TCP
handshake may
occur for the
quintuple flow
of each
redirection and
main request.
Delays between
the time when
the syn is
responded to
and the time
when the syn
ack is responded
to for multiple
TCP
connections are
calculated and
the maximum
value is
selected.
Issue 03 (2015-07-30)

3660
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
Max SYN ACK
to First ACK
Delay
[0,+)
Delay between
the time when
the file transfer
syn ack packet is
responded to
and the time
when the first
ack packet is
responded to. If
the second or
third handshake
fails, the value
of this
parameter is 0.
PS 12.1
Note:
Redirection
occurs for
multiple times
when the file
transfer request
is responded to.
The third TCP
handshake may
occur for the
quintuple flow
of each
redirection and
main request.
Delays between
the time when
the syn ack is
responded to
and the time
when the first
ack is responded
to for multiple
TCP
connections are
calculated and
the maximum
value is
selected.
Issue 03 (2015-07-30)

3661
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>File Transfer
Max ACK to
First Data Delay
[0,+)
Delay between
the time when
the last ack
packet of the file
transfer TCP
connection is
responded to
and the time
when the file
transfer request
is responded to.
If the third
handshake fails,
the value of this
parameter is 0.
PS 12.1
Note:
Redirection
occurs for
multiple times
when the file
transfer request
is responded to.
The third TCP
handshake may
occur for the
quintuple flow
of each
redirection and
main request.
Delays between
the time when
the ack is
responded to
and the time
when the first
request is
responded to for
multiple TCP
connections are
calculated and
the maximum
value is
selected.
Issue 03 (2015-07-30)

3662
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
File Transfer
Delay
[0,+)
File Transfer
Delay = File
transfer end
time - File
transfer start
time.
PS 12.1
The file transfer

delay starts
when SP
responds with
"2**, 304", or
the ack (for
POST upload).
Issue 03 (2015-07-30)
TCP DL Total
Traffic
[0,+)
Byte
Total TCP
downlink data
volume refers to
the total size of
all TCP
downlink
payload
packets,
including
retransmitted
packets, during
the file access
phase.
PS 12.1
TCP DL Total
Packets
[0,+)
Number
Total number of
TCP downlink
packets,
including
retransmitted
packets.
PS 12.1
TCP DL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
downlink
packets (only
payload packets
are calculated).
PS 12.1

3663
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP UL Total
Packets
[0,+)
Number
Number of all
TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL Total
Traffic
[0,+)
Byte
Total size of all

TCP uplink
packets,
including
retransmitted
packets.
PS 12.1
TCP UL
Retransmission
Ratio
[0.00,100.00]
Proportion of
TCP downlink
retransmission.
PS 12.1
[0,+)
Number
Number of
disordered TCP
uplink packets
(only payload
packets are
calculated).
PS 12.1
TCP
Downstream
Average RTT
Delay
(Accurate)
[0,+)
TCP
Downstream
Average RTT
Delay
(Accurate) =
Packet
downstream
RTT delay
(accurate)/
Number of
packets whose
accurate
downstream
RTT delay is not
0 (accurate).
PS 12.1

3664
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TCP Upstream
Average RTT
Delay
(Accurate)
[0,+)
TCP Upstream
PS 12.1
Average RTT
Delay
(Accurate) =
Packet upstream
RTT delay
(accurate)/
Number of
packets whose
accurate
upstream RTT
delay is not 0
(accurate).
UL TCP
Window Zero
Count
[0,+)
Number
Number of
times that the
uplink TCP
window is set to
0 during the file
transfer phase.
PS 12.1
Upstream
Packet Loss
Count
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.
Upstream
Packet Loss
Count
(Triggered By
Retransmitted
Packet)
Issue 03 (2015-07-30)
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.

3665
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Downstream
Packet Loss
Count
[0,+)
Number
Upstream
means above the
Iu-PS interface
(above the CN).
PS 12.1
Number of
times that
packets are lost
on the upstream
during the page
display phase.
TCP SYN Max
Window Size
N/A
N/A
Maximum size
of the SYN
window of file
transfer.
PS 12.1
TCP SYN Min

Window Size
N/A
N/A
Minimum size
of the SYN
window of file
transfer.
PS 12.1
TCP DL Max
Send Window
N/A
N/A
Downlink
PS 12.1
sending window
of the maximum
size.
Reference for Complaint Analysis Support Parameters (PS Core) - Signaling Plane
This section describes the parameters for querying PS Core complaint analysis support resultssignaling plane. You can refer to the description when querying PS Core complaint analysis
support results.
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.
Issue 03 (2015-07-30)

3666
Nastar
Summary
Parameter
Range
Unit
Description
Supported
Solution
Version
Serial
Number
[1,2^31-1)
N/A

Summary Table. Serial number
is a keyword of a call record. It is
an internal identification in the
a call record.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Combined
N/A
N/A

empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
USN+UGW
Associated
N/A
N/A

empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Abnormal
N/A
N/A
Indicates whether a call record is

abnormal.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

record is abnormal.
Abnormal
Cause
N/A
N/A

Key Signaling".
Issue 03 (2015-07-30)
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Protocol
Cause
Description
N/A
N/A
Description of failure cause

values in the signaling flow.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Demarcatio
n Result
N/A
N/A
NE that experiences an
exception.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

3667
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Start Time
N/A
N/A
Start time of the signaling

procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
End Time
N/A
N/A

procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
IMSI
N/A
N/A
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

User ID:
Alias
N/A
N/A

MSISDN
N/A
N/A
subscriber.
view the MSISDN information.
Access Net
Type
N/A
N/A
Radio access network (RAN)

type for the signaling procedure.
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
GPRS
UMTS(W/TD)
LTE
UTRAN
GERAN
WLAN
GAN
HSPA Evolution
EUTRAN
N/A
Issue 03 (2015-07-30)

3668
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CSFB On
Access
Yes
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
N/A
Access type of VoLTE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
N/A

following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
No
N/A
VoLTE On
Access
Yes
No
N/A
NE Type
N/A
SGSN
MME
GGSN
SGW
PGW
SGW+PGW
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Procedure
Type
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
RAI/TAI
N/A

Key Signaling".
N/A

initiated.
initiated.
Cell
Issue 03 (2015-07-30)
N/A
N/A

accesses.

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
3669
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
APN
N/A
N/A

the SM procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

MM procedure.
Procedure
Delay Time
(ms)
0-65535
ms
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Parameters for Viewing PS Core Complaint Analysis Support Results - SGSN SM

(SGSN SM) results.
Base Information
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
SN
[1,2^32-1)
N/A
SN of a reported
CHR. The SN
accumulates on an
NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Start Time
N/A
N/A
Start time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
End Time
N/A
N/A
End time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Procedure
Delay Time
0-65535
ms
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

3670
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
NE Type
N/A
N/A
CN NE types for the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGSN
MME
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Subrack
No.
0-255
N/A
Subrack number of
the device that
generates CHRs.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Slot No.
0-255
N/A
Slot number of the

a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Proc No.
0-65535
N/A
Number of the
process that generates
a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Parameter
Range
Unit
Description
Supported
Solution Version
IMSI
N/A
N/A
subscriber.
User Information
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
Note: Only when you PS12.0/PS 12.1/PS
13.0
have the "User
can view the IMSI
information.
Issue 03 (2015-07-30)

3671
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
User ID: Alias
N/A
N/A
User ID, which is

when creating the
task.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Alias, which is
created by the user
when creating the
task.
MSISDN
N/A
N/A
MSISDN
information of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
Note: Only when you 13.0
have the "User
can view the
MSISDN
information.
IMEI-TAC
00000000-9999
9999
N/A
IMEI-TAC of the
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Terminal Model
N/A
N/A

that initiates a
service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
MS Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>GEA/1
encryption
algorithm
0/1
N/A

GEA/1 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SM
capabilities via
dedicated
channels
0/1
N/A

dedicated-channelbased SM capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3672
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>SM
capabilities via
GPRS channels
0/1
N/A

GPRS-channel-based
SM capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SS Screening
Indicator string
(2)
0/1
N/A

SS screening
indicator is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SoLSA
Capability
0/1
N/A

SoLSA capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Revision level
indicator (R99
or later versions
of the protocol
support)
0/1
N/A

revision-level
indicator is supported
(by protocols in
3GPP Specifications
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PFC feature
mode(BSS
packet flow
procedures
support)
0/1
N/A

PFC feature mode
(BSS data packet
flow procedure) is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3673
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>GEA/2
encryption
algorithm
0/1
N/A

GEA/2 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/3
encryption
algorithm
0/1
N/A

GEA/3 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/4
encryption
algorithm
0/1
N/A

GEA/4 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/5
encryption
algorithm
0/1
N/A

GEA/5 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/6
encryption
algorithm
0/1
N/A

GEA/6 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/7
encryption
algorithm
0/1
N/A

GEA/7 encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3674
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>LCS VA
capability
0/1
N/A
Indicates whether the PS 11.0/PS 12.0/PS

LCS VA capability is 12.1/PS 13.0
supported.
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to
UTRAN Iu
mode capability
0/1
N/A

inter-PS handover
(GERAN to UTRAN
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to EUTRAN S1
mode capability
0/1
N/A

inter-PS handover
(GERAN to EUTRAN handover)
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EMM
Combined
procedures
Capability
0/1
N/A

EMM combined
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>ISR support
0/1
N/A
Indicates whether
ISR is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SRVCC to
GERAN/
UTRAN
capability
0/1
N/A

SRVCC-to-GERAN/
UTRAN handover
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3675
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPC capability
0/1
N/A

EPC capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A

NF capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
UE Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>EPS
encryption
algorithm EEA0
supported
0/1
N/A

EPS encryption
algorithm EEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA1
supported
0/1
N/A

EPS encryption
algorithm 128-EEA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA2
supported
0/1
N/A

EPS encryption
algorithm 128-EEA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA3
supported
0/1
N/A

EPS encryption
algorithm EEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3676
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS
encryption
algorithm EEA4
supported
0/1
N/A

EPS encryption
algorithm EEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA5
supported
0/1
N/A

EPS encryption
algorithm EEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA6
supported
0/1
N/A

EPS encryption
algorithm EEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA7
supported
0/1
N/A

EPS encryption
algorithm EEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA0
supported
0/1
N/A

EPS integrity
algorithm EIA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
0/1
N/A

EPS integrity
algorithm 128-EIA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3677
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS integrity
0/1
N/A

EPS integrity
algorithm 128-EIA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA3
supported
0/1
N/A

EPS integrity
algorithm EIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA4
supported
0/1
N/A

EPS integrity
algorithm EIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA5
supported
0/1
N/A

EPS integrity
algorithm EIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA6
supported
0/1
N/A

EPS integrity
algorithm EIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA7
supported
0/1
N/A

EPS integrity
algorithm EIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3678
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA0
supported
0/1
N/A

UMTS encryption
algorithm UEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA1
supported
0/1
N/A

UMTS encryption
algorithm UEA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA2
supported
0/1
N/A

UMTS encryption
algorithm UEA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA3
supported
0/1
N/A

UMTS encryption
algorithm UEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA4
supported
0/1
N/A

UMTS encryption
algorithm UEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA5
supported
0/1
N/A

UMTS encryption
algorithm UEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3679
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA6
supported
0/1
N/A

UMTS encryption
algorithm UEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA7
supported
0/1
N/A

UMTS encryption
algorithm UEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
(UCS2)
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA1
supported
0/1
N/A

UMTS integrity
algorithm UIA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA2
supported
0/1
N/A

UMTS integrity
algorithm UIA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA3
supported
0/1
N/A

UMTS integrity
algorithm UIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3680
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
integrity
algorithm UIA4
supported
0/1
N/A

UMTS integrity
algorithm UIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA5
supported
0/1
N/A

UMTS integrity
algorithm UIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA6
supported
0/1
N/A

UMTS integrity
algorithm UIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA7
supported
0/1
N/A

UMTS integrity
algorithm UIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A

NF capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>1xSRVCC
capability
0/1
N/A

1xSRVCC capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3681
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>Location
services (LCS)
notification
mechanisms
capability
0/1
N/A

LCS notification
mechanism
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LTE
Positioning
Protocol (LPP)
capability
0/1
N/A

LPP capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Access class
control for
CSFB (ACCCSFB)
capability
0/1
N/A

CSFB-access-level
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
MS P-TMSI
[1,2^32-1)
N/A
P-TMSI received
from a terminal when
a procedure is
initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Allocated PTMSI
[1,2^32-1)
N/A
P-TMSI that the

network allocates to a
terminal.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Index
N/A
N/A
Index number of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Home
PLMN
N/A
N/A
PLMN in the IMSI of

a subscriber. This
personal data
anonymization.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Authentication
Flag
NoAuth
N/A
Indicates whether a
procedure requires
authentication.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
FirAuth
SecAuth
Issue 03 (2015-07-30)

3682
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
IMEI Check
Flag
N/A
N/A
Indicates whether a
procedure requires
IMEI check.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
P-TMSI
Reallocation
Flag
N/A
N/A
Indicates whether a
procedure requires PTMSI reallocation.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Access Information
Parameter
Range
Unit
Description
Supported Solution
Version
Type
N/A
N/A

procedure. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
SM
MM
Procedure Type
N/A
N/A
Name of a signaling
procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Procedure Init
Cause
N/A
N/A

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

appendix.
Access Network
Description
N/A
N/A
Description of the access

network.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Inter CN Node
Type
N/A
N/A

(RAN) type for the
signaling procedure. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
GPRS
UMTS(W/TD)
LTE
Issue 03 (2015-07-30)

3683
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported Solution
Version
Access BSC/
RNC
Description
N/A
N/A
gains access to the RAN.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>BSC/RNC
PLMN
N/A
N/A
PLMN serving a BSC or

RNC.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
>BSC/RNC ID
N/A
N/A
ID of a BSC or RNC.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
>CGI
N/A
N/A

initiated.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Cell Name
[0,200]
N/A

initiated.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
PS Core
Description
N/A
N/A
gains access to the CN.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>GGSN or
PGW Address
for Signalling
N/A
N/A

signaling plane.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>GGSN
Address for
User Traffic
N/A
N/A

user plane.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Mobility
Information
N/A
N/A
Information about
mobility analysis.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Old SGSN IP
N/A
N/A
If a procedure involves
two SGSNs, the field
indicates the IP address of
the old SGSN.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>SM Procedure
Information
N/A
N/A
Information about the SM

procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

3684
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>PDP Type In
Used
N/A
N/A
Type of the PDP used by

an MS. The values of this
parameter are as follows:
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
IPv4
IPv6
BOTH(IPV4 & IPV6)
PPP
Empty
>PDP Type
Request By MS
N/A
N/A
Type of the PDP

requested by a MS. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
IPv4
IPv6
BOTH(IPV4 & IPV6)
PPP
Empty
>PDP Address
Request By MS
N/A
N/A
IP address of the PDP

requested by a MS.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
>PDP Address
in Use
N/A
N/A
Activated PDP IP
address.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>APN Request
By MS
N/A
N/A
Name of the access point

requested by an MS.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
>Access APN
N/A
N/A
Access point name.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>APN Selection
Mode
N/A
N/A
APN selection mode.

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
MS & Network Verified

MS not Verified
Network not Verified
QoS
Issue 03 (2015-07-30)
N/A
N/A

QoS.

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
3685
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Allocation/
Retention
Priority
N/A
N/A
Allocation/retention
priority. This parameter
can be any of the
following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
High priority
Normal priority
Low priority
>Reliability
Class
N/A
N/A
Subscribed reliability
class. This parameter can
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Unused. If received, it
shall be interpreted as
'010' (Note)
Unacknowledged GTP;
RLC, Protected data
Unacknowledged GTP
and LLC; Acknowledged
RLC, Protected data
Unacknowledged GTP,
data
Unacknowledged GTP,
LLC, and RLC,
Unprotected data
>Delay Class
N/A
N/A

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

Delay class 1
Delay Class 2
Delay Class 3
Delay Class 4 (best
effort)
Reserved
Issue 03 (2015-07-30)

3686
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Precedence
Class
N/A
N/A
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
High priority
Normal priority
Low priority
Reserved
>Peak
Throughput
N/A
N/A
Subscribed peak
throughput. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
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
Reserved
Issue 03 (2015-07-30)

3687
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Mean
Throughput
N/A
N/A
Subscribed mean
throughput. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
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
Erroneous SDU
N/A
N/A
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
No detect('-')
Erroneous SDUs are
delivered('yes')
delivered ('no')
Reserved
Issue 03 (2015-07-30)

3688
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Delivery
Order
N/A
N/A
Subscribed delivery
order. This parameter can
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
With delivery order

('yes')
('no')
>Traffic Class
N/A
N/A

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Streaming class
Interactive class
Background class
>Traffic
Handling
Priority
N/A
N/A
Subscribed traffic
handling priority. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Priority level 1
Priority level 2
Priority level 3
>Maximum
SDU Size
0-255
byte
Maximum SDU length.

Subscribed maximum
SDU size
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
150: 10~1500 octets

151: 1502 octets
152: 1510 octets
153: 1520 octets
Reserved
Issue 03 (2015-07-30)
>Maximum Bit
Rate for Uplink
0-8640
bps
Maximum uplink rate.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Maximum Bit
Rate for
Downlink
0-2560
00
bps
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

3689
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>Residual BER
N/A
N/A

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

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
Ratio
N/A
N/A

ratio. This parameter can
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

ratio
1*10^2
7*10^3
1*10^3
1*10^4
1*10^5
1*10^6
1*10^1
Issue 03 (2015-07-30)
>Transfer Delay
0-255
ms
Transfer delay.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Guaranteed
Bit Rate for
Uplink
0-8640
bps
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>Guaranteed
Bit Rate for
Downlink
0-2560
00
bps
Guaranteed downlink
rate.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

3690
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
GTP Tunnel
Version
N/A
N/A
GTP tunnel version. This

the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
GTPv0
GTPv1
Bearer ID
5-15
N/A
Bearer ID.
PS 13.0 or later
Result Information
Parameter
Range
Unit
Description
Supported
Solution Version
Protocol Cause
N/A
N/A
Cause value
provided in a
protocol.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Protocol Cause
Description
N/A
N/A
Description of a
protocol cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Huawei's Cause
N/A
N/A

failure cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

Description of
Exception Cause
Fields in the
appendix.
Huawei's Cause
Description
N/A
N/A
Description of a
cause according to
Huawei's knowledge
base.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Parameter
Range
Unit
Description
Supported
Solution Version
Traffic
Information
N/A
N/A

traffic.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Process Information
Issue 03 (2015-07-30)

3691
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>Uplink Data
Volume
[0,+)
Byte
The traffic on the

uplink.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Downlink
Data Volume
[0,+)
Byte
The traffic on the

downlink.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Data Tunnel
Type
Yes
N/A
Tunnel type,
including RNCSGSN-GGSN or
RNC-GGSN.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
No
Yes indicates Direct

Tunnel(BSC/RNCGGSN), the
transmission
efficiency is higher.
No indicates UnDirect Tunnel(BSC/
RNC-SGSNGGSN).
Charging
Information
N/A
N/A

charging.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Charging ID
from GGSN
[1,2^32-1)
N/A
SN of a CHR that is
sent to the billing
center.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Charging
Characteristics
N/A
N/A
Charging attribute of
a UE. This parameter
can be any of the
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Unspecified
Hot billing Charging
Flat rate Charging
Prepaid Charging
Normal Charging
Issue 03 (2015-07-30)

3692
Nastar
Parameters for Viewing PS Core Complaint Analysis Support Results - SGSN MM

(SGSN MM) results.
Base Information
Parameter
Range
Unit
Description
Supported Solution
Version
SN
[1,2^31-1
)
N/A
SN of a reported CHR.
The SN accumulates on
an NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Start Time
N/A
N/A
Start time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
End Time
N/A
N/A
End time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Procedure
Delay Time
0-65535
ms
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
NE Type
N/A
N/A
CN NE types for the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
SGSN
MME
Issue 03 (2015-07-30)
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Board Subrack
No.
0-255
N/A
Subrack number of the

CHRs.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Board Slot No.
0-255
N/A
Slot number of the

device that generates a
CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0
Board Proc No.
0-65535
N/A
Number of the process

that generates a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS 13.0

3693
Nastar
User Information
Parameter
Range
Unit
Description
Supported
Solution Version
IMSI
N/A
N/A
IMSI information of
a subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Note: Only when

you have the "User
can view the IMSI
information.
User ID: Alias
N/A
N/A
User ID, which is

created by the
system when
creating the task.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Alias, which is
created by the user
when creating the
task.
MSISDN
N/A
N/A
MSISDN
information of a
subscriber.
Note: Only when
you have the "User
can view the
MSISDN
information.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
IMEI-TAC
00000000-9999
9999
N/A
IMEI-TAC of the
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Terminal Model
N/A
N/A
Model of the
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
MS Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>GEA/1
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3694
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>SM
capabilities via
dedicated
channels
0/1
N/A
Indicates whether
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SM
capabilities via
GPRS channels
0/1
N/A
Indicates whether
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SS Screening
Indicator string
(2)
0/1
N/A
Indicates whether
the SS screening
indicator is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SoLSA
Capability
0/1
N/A
Indicates whether
the SoLSA
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Revision level
indicator (R99
or later versions
of the protocol
support)
0/1
N/A
Indicates whether
the revision-level
indicator is
supported (by
protocols in 3GPP
Specifications
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3695
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>PFC feature
mode(BSS
packet flow
procedures
support)
0/1
N/A
Indicates whether
the PFC feature
mode (BSS data
packet flow
procedure) is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/2
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/3
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/3
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/4
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/4
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/5
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/5
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/6
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/6
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3696
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>GEA/7
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/7
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LCS VA
capability
0/1
N/A
Indicates whether
the LCS VA
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to
UTRAN Iu
mode capability
0/1
N/A
Indicates whether
the inter-PS
handover (GERAN
to UTRAN
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to EUTRAN S1
mode capability
0/1
N/A
Indicates whether
the inter-PS
handover (GERAN
to E-UTRAN
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EMM
Combined
procedures
Capability
0/1
N/A
Indicates whether
the EMM combined
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>ISR support
0/1
N/A
Indicates whether
ISR is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3697
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>SRVCC to
GERAN/
UTRAN
capability
0/1
N/A
Indicates whether
handover capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPC capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
UE Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>EPS
encryption
algorithm EEA0
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA1
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm 128-EEA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA2
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm 128-EEA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3698
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS
encryption
algorithm EEA3
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA4
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA5
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA6
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA7
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA0
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3699
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS integrity
0/1
N/A
Indicates whether
the EPS integrity
algorithm 128-EIA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
0/1
N/A
Indicates whether
the EPS integrity
algorithm 128-EIA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA3
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA4
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA5
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA6
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3700
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS integrity
algorithm EIA7
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA0
supported
0/1
N/A
Indicates whether
the UMTS
UEA0 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA1
supported
0/1
N/A
Indicates whether
the UMTS
UEA1 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA2
supported
0/1
N/A
Indicates whether
the UMTS
UEA2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA3
supported
0/1
N/A
Indicates whether
the UMTS
UEA3 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA4
supported
0/1
N/A
Indicates whether
the UMTS
UEA4 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3701
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA5
supported
0/1
N/A
Indicates whether
the UMTS
UEA5 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA6
supported
0/1
N/A
Indicates whether
the UMTS
UEA6 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA7
supported
0/1
N/A
Indicates whether
the UMTS
UEA7 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
(UCS2)
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA1
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA2
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3702
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
integrity
algorithm UIA3
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA4
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA5
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA6
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA7
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3703
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>1xSRVCC
capability
0/1
N/A
Indicates whether
the 1xSRVCC
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Location
services (LCS)
notification
mechanisms
capability
0/1
N/A
Indicates whether
mechanism
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LTE
Positioning
Protocol (LPP)
capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Access class
control for
CSFB (ACCCSFB)
capability
0/1
N/A
Indicates whether
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)
MS P-TMSI
[1,2^31-1)
N/A
P-TMSI received
from a terminal
when a procedure is
initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Allocated PTMSI
[1,2^31-1)
N/A
P-TMSI that the

network allocates to
a terminal.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Index
N/A
N/A
Index number of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

3704
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
User Home
PLMN
N/A
N/A
PLMN in the IMSI of

a subscriber. This
personal data
anonymization.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Authentication
Flag
NoAuth
N/A
MM procedure
requires
authentication.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
N/A
MM procedure
requires IMEI check.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
N/A
MM procedure
requires P-TMSI
reallocation.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
FirAuth
SecAuth
IMEI Check
Flag
Yes
P-TMSI
Reallocation
Flag
Yes
No
No
Access Information
Parameter
Range
Unit
Description
Supported
Solution Version
Type
N/A
N/A

procedure. This
parameter can be any
of the following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SM
MM
Procedure Type
N/A
N/A
Name of a signaling
procedure.
Description of
Signaling Procedures
in the appendix.
Issue 03 (2015-07-30)

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
3705
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Procedure Init
Cause
N/A
N/A
Procedure initiating
party (UE or MME)
and cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

Description of
Procedure Initiating
Causes in the
appendix.
Access Network
Description
N/A
N/A
Description of the
access network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Inter CN Node
Type
0/1
N/A
Access network type

of the source or target
node in the Inter RAU
or Inter Relocation
procedure.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>Access Type
N/A
N/A

(RAN) type for the
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
GPRS
UMTS(W/TD)
LTE
>Source Access
Net Type
GPRS
UMTS(W/TD)
LTE
Issue 03 (2015-07-30)
N/A
Works together with

Inter CN Node Type.
This parameter is
CN Node Type is set
to new indicating the
access network type
on the source node.
This parameter is
cases.

PS 11.0/PS 12.0/PS
12.1/PS 13.0
3706
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>Target Access
Net Type
GPRS
N/A
Works together with

Inter CN Node Type.
This parameter is
CN Node Type is set
to old indicating the
access network type
on the target node.
This parameter is
cases.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
UMTS(W/TD)
LTE
Access BSC/
RNC
Description
N/A
N/A
Description of an NE
that gains access to
the RAN.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>RAI
N/A
N/A
If a procedure does
not involve two
routing areas, the
field indicates the
routing area where
the procedure is
initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
If a procedure
involves two routing
areas, the field
indicates the new
routing area.
Issue 03 (2015-07-30)
>Old RAI
N/A
N/A
If a procedure does
not involve two
routing areas, the
field indicates the
routing area where
the procedure is
initiated. Otherwise,
the field is empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>BSC/RNC
PLMN
N/A
N/A
PLMN serving a BSC

or RNC.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>BSC/RNC ID
N/A
N/A
ID of a BSC or RNC.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>Target RNC
PLMN
N/A
N/A
Target RNC PLMN

in relocation produce
in 3G.
PS 12.0/PS 12.1/PS
13.0

3707
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution Version
>Target RNC
ID
N/A
N/A
Target RNC ID in
3G.
PS 12.0/PS 12.1/PS
13.0
>CGI
N/A
N/A
Cell where a
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
>Cell Name
[0,200]
N/A
Name of a cell.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Mobility
Information
N/A
N/A
Information about
mobility analysis.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Old SGSN IP
N/A
N/A
If a procedure
involves two SGSNs,
the field indicates the
IP address of the old
SGSN. Otherwise,
the field is empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
DNS Domain
Type
0-19
N/A
DNS Domain Type in

MM produce.
PS 12.0/PS 12.1/PS
13.0
Relocation
Type
0/1
N/A
Relocation Type in
3G.
PS 12.0/PS 12.1/PS
13.0
RFSP ID
1-256
N/A
RFSP (RAT/
Frequency Selection
Priority) ID.
PS 13.0 or later
254

3708
Nastar
Result Information
Parameter
Range
Unit
Description
Supported
Solution Version
Attach Result
N/A
N/A
Helps identify the

result of the
combined attach
procedure. The
values of this
parameter are as
follows:
PS 11.0/PS 12.0/PS
12.1/PS 13.0
GPRS only attached

Combined GPRS/
IMSI attached
Update Result
N/A
N/A
Helps identify the

result of the
combined RAU
procedure. The
values of this
parameter are as
follows:
PS 11.0/PS 12.0/PS
12.1/PS 13.0
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
provided in a
protocol.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Protocol Cause
Description
N/A
N/A
Description of a
protocol cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Huawei's Cause
N/A
N/A

failure cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

Description of
Exception Cause
Fields in the
appendix.
Issue 03 (2015-07-30)

3709
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
Huawei's Cause
Description
N/A
N/A
Description of a
cause according to
Huawei's knowledge
base.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Parameters for Viewing PS Core Complaint Analysis Support Results - MME SM

(MME SM) results.
Base Information
Parameter
Range
Unit
Description
Supported
Solution Version
SN
[1,2^31-1)
N/A
SN of a reported
CHR. The SN
accumulates on an
NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Start Time
N/A
N/A
Start time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
End Time
N/A
N/A
End time of the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Procedure
Delay Time
0-65535
ms
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
NE Type
N/A
N/A
CN NE types for the

This parameter can
be any of the
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGSN
MME
Issue 03 (2015-07-30)

3710
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Subrack
No.
0-255
N/A
Subrack number of
the device that
generates CHRs.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Slot No.
0-255
N/A
Slot number of the

a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Proc No.
0-65535
N/A
Number of the
process that
generates a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Parameter
Range
Unit
Description
Supported
Solution Version
IMSI
N/A
N/A
IMSI information of
a subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Information
Note: Only when

you have the "User
can view the IMSI
information.
User ID: Alias
N/A
N/A
User ID, which is

created by the
system when
creating the task.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Alias, which is
created by the user
when creating the
task.
Issue 03 (2015-07-30)

3711
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
MSISDN
N/A
N/A
MSISDN
information of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Note: Only when

you have the "User
can view the
MSISDN
information.
IMEI-TAC
00000000-9999
9999
N/A
IMEI-TAC of the
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Terminal Model
N/A
N/A
Model of the
a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
MS Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>GEA/1
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/1
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SM
capabilities via
dedicated
channels
0/1
N/A
Indicates whether
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SM
capabilities via
GPRS channels
0/1
N/A
Indicates whether
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3712
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UCS2 support
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SS Screening
Indicator string
(2)
0/1
N/A
Indicates whether
the SS screening
indicator is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SoLSA
Capability
0/1
N/A
Indicates whether
the SoLSA
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Revision level
indicator (R99
or later versions
of the protocol
support)
0/1
N/A
Indicates whether
the revision-level
indicator is
supported (by
protocols in 3GPP
Specifications
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PFC feature
mode(BSS
packet flow
procedures
support)
0/1
N/A
Indicates whether
the PFC feature
mode (BSS data
packet flow
procedure) is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/2
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/2
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3713
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>GEA/3
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/3
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/4
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/4
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/5
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/5
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/6
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/6
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>GEA/7
encryption
algorithm
0/1
N/A
Indicates whether
the GEA/7
encryption
algorithm is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LCS VA
capability
0/1
N/A
Indicates whether
the LCS VA
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3714
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>PS inter-RAT
HO from
GERAN to
UTRAN Iu
mode capability
0/1
N/A
Indicates whether
the inter-PS
handover (GERAN
to UTRAN
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to EUTRAN S1
mode capability
0/1
N/A
Indicates whether
the inter-PS
handover (GERAN
to E-UTRAN
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EMM
Combined
procedures
Capability
0/1
N/A
Indicates whether
the EMM combined
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>ISR support
0/1
N/A
Indicates whether
ISR is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>SRVCC to
GERAN/
UTRAN
capability
0/1
N/A
Indicates whether
handover capability
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPC capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3715
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>NF capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
UE Network
Capability
N/A
N/A

capability.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
>EPS
encryption
algorithm EEA0
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA1
supported
0/1
N/A
Indicates whether
the EPS encryption
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA2
supported
0/1
N/A
Indicates whether
the EPS encryption
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA3
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA4
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3716
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS
encryption
algorithm EEA5
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA6
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA7
supported
0/1
N/A
Indicates whether
the EPS encryption
algorithm EEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA0
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
0/1
N/A
Indicates whether
the EPS integrity
algorithm 128-EIA1
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
0/1
N/A
Indicates whether
the EPS integrity
algorithm 128-EIA2
is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3717
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>EPS integrity
algorithm EIA3
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA4
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA5
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA6
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA7
supported
0/1
N/A
Indicates whether
the EPS integrity
algorithm EIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA0
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA0 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3718
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA1
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA2
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA3
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA4
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA5
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3719
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
encryption
algorithm
UEA6
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA7
supported
0/1
N/A
Indicates whether
the UMTS
encryption
algorithm UEA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UCS2 support
(UCS2)
0/1
N/A
Indicates whether
UCS2 is supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA1
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA1 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA2
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA2 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA3
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA3 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3720
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>UMTS
integrity
algorithm UIA4
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA4 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA5
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA5 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA6
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA6 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA7
supported
0/1
N/A
Indicates whether
the UMTS integrity
algorithm UIA7 is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>NF capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>1xSRVCC
capability
0/1
N/A
Indicates whether
the 1xSRVCC
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3721
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
>Location
services (LCS)
notification
mechanisms
capability
0/1
N/A
Indicates whether
mechanism
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>LTE
Positioning
Protocol (LPP)
capability
0/1
N/A
Indicates whether
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
>Access class
control for
CSFB (ACCCSFB)
capability
0/1
N/A
Indicates whether
capability is
supported.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
0 not supported
1 supported
User Index
N/A
N/A
Index number of a
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
User Home
PLMN
N/A
N/A
PLMN in the IMSI

of a subscriber. This
personal data
anonymization.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Access Information
Parameter
Range
Unit
Description
Supported Solution
Version
Type
N/A
N/A

procedure. This
the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
SM
MM
Issue 03 (2015-07-30)

3722
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
Procedure Type
N/A
N/A
Name of a signaling
procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Procedure Init
Cause
N/A
N/A

PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

appendix.
Access eNodeB
Information
N/A
N/A
Information of the
eNodeB where a UE
accesses.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>eNodeB
PLMN
N/A
N/A
PLMN of the eNodeB

where a UE is located
when a signaling
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>eNodeB ID
[1,2^31
-1)
N/A
ID of the eNodeB where

a UE is located when a
initiated.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
MME UE S1AP
ID
[1,2^31
-1)
N/A
UES1AP connection
identification allocated
by an MME in a traffic
procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
MME S1AP ID
Time
N/A
N/A

connection identification
is allocated by an MME
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Current TAC
N/A
N/A
Tracking area where a

terminal is located when
a signaling procedure is
initiated.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
PDN Type
N/A
N/A
Requested PDN type in a

the following:
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
IPV4
IPV6
both(IPV4 & IPV6)
unused
Issue 03 (2015-07-30)

3723
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
PDN Type In
Used
N/A
N/A
Used PDN type in a

the following:
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
IPV4
IPV6
both(IPV4 & IPV6)
unused
Issue 03 (2015-07-30)
PDN Address In
Used
IPv4,
IPv6
N/A
Used PDN address in a

traffic procedure.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
APN
N/A
N/A
Requested APN in a
traffic procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
APN In Used
N/A
N/A
Requested APN in a
traffic procedure.
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
Serving
Gateway
Address
N/A
N/A
IP address of the Serving

procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
PDN Gateway
Address
N/A
N/A
IP address of the PDN

procedure.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
PDN Gateway
Host Name
N/A
N/A
Domain name of the

PDN Gateway in a
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
QoS
N/A
N/A

QoS.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>QCI
0-255
N/A
QCI information
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>ARP
0-255
N/A
ARP information
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>UE Uplink
Max Bandwidth
[1,2^31
-1)
bit/s
Maximum UE-level
uplink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>UE Downlink
Max Bandwidth
[1,2^31
-1)
bit/s
Maximum UE-level
downlink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0

3724
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
>APN Uplink
Max Bandwidth
[1,2^31
-1)
bit/s
Maximum APN-level
uplink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>APN
Downlink Max
Bandwidth
[1,2^31
-1)
bit/s
Maximum APN-level
downlink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>GBR Uplink
[1,2^31
-1)
bit/s
uplink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>GBR
Downlink
[1,2^31
-1)
bit/s
downlink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>MBR Uplink
[1,2^31
-1)
bit/s
uplink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
>MBR
Downlink
[1,2^31
-1)
bit/s
downlink bandwidth
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
IMS Flag
0/1
N/A
Identity of an IMS. The

(enumerated) values of
follows:
PS 11.0/PS 12.0/PS 12.1/

PS 13.0
0: non-IMS PDN
1: IMS PDN
S1-U Serving
Gateway
Address1
l IPv
4
S1-U Serving
Gateway
Address2
l IPv
4
S1-U eNodeB
Address1
l IPv
4
N/A

Address1.
PS 12.0/PS 12.1/PS 13.0
N/A

Address2.
PS 12.0/PS 12.1/PS 13.0
N/A
PS 12.0/PS 12.1/PS 13.0
l IPv
6
l IPv
6
l IPv
6
Issue 03 (2015-07-30)

3725
Nastar
Parameter
Range
Unit
Description
Supported Solution
Version
S1-U eNodeB
Address2
l IPv
4
N/A
PS 12.0/PS 12.1/PS 13.0
N/A
Serving Gateway
Address2.
PS 12.0/PS 12.1/PS 13.0
N/A
PDN Gateway Address2.
PS 12.0/PS 12.1/PS 13.0
l IPv
6
Serving
Gateway
Address2
l IPv
4
PDN Gateway
Address2
l IPv
4
l IPv
6
l IPv
6
Result Information
Parameter
Range
Unit
Description
Supported Solution
Version
Protocol Cause
N/A
N/A
Negotiated cause in a
procedure result.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Protocol Cause
Description
N/A
N/A
Description of a
protocol cause.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Huawei's Cause
N/A
N/A

failure cause.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Huawei's Cause
Description
N/A
N/A
knowledge base.
PS 10.0/PS 10.1/PS10.2/
PS 11.0/PS12.0/PS 12.1/
PS 13.0
Parameters for Viewing PS Core Complaint Analysis Support Results - MME MM

(MME MM) results.
Issue 03 (2015-07-30)

3726
Nastar
Base Information
Parameter
Range
Unit
Description
Supported
Solution Version
SN
[1,2^31-1)
N/A
SN of a reported
CHR. The SN
accumulates on an
NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Start Time
N/A
N/A
Begin time of the

signaling
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
End Time
N/A
N/A
End time of the

signaling
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Procedure
Delay Time
0-65535
ms
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
NE Type
N/A
N/A
CN NE types for the

signaling
procedure. This
parameter can be
any of the
following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
SGSN
MME
Issue 03 (2015-07-30)
NE Name
N/A
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Subrack
No.
0-255
N/A
Subrack number of
the device that
generates CHRs.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Slot No.
0-255
N/A
Slot number of the

device that
generates a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Board Proc No.
0-65535
N/A
Number of the
process that
generates a CHR.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

3727
Nastar
User Information
Parameter
Range
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Note: Only when you

IMSI information.
User ID: Alias
N/A
N/A
User ID, which is

Alias, which is created
by the user when
creating the task.
MSISDN
N/A
N/A
MSISDN information of
a subscriber.
Note: Only when you
MSISDN information.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
IMEI-TAC
00000000-9999
9999
N/A
IMEI-TAC of the
terminal that initiates a
service.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Terminal Model
N/A
N/A

that initiates a service.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
MS Network
Capability
N/A
N/A

capability.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
>GEA/1
encryption
algorithm
0/1
N/A

GEA/1 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3728
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>SM
capabilities via
dedicated
channels
0/1
N/A

dedicated-channelbased SM capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>SM
capabilities via
GPRS channels
0/1
N/A

GPRS-channel-based
SM capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UCS2 support
0/1
N/A

is supported.
0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
>SS Screening
Indicator string
(2)
0/1
N/A
Indicates whether the SS

screening indicator is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>SoLSA
Capability
0/1
N/A

SoLSA capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>Revision level
indicator (R99
or later versions
of the protocol
support)
0/1
N/A

revision-level indicator
is supported (by
protocols in 3GPP
Specifications Release
99 or later).
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3729
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>PFC feature
mode(BSS
packet flow
procedures
support)
0/1
N/A

PFC feature mode (BSS
data packet flow
procedure) is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/2
encryption
algorithm
0/1
N/A

GEA/2 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/3
encryption
algorithm
0/1
N/A

GEA/3 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/4
encryption
algorithm
0/1
N/A

GEA/4 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/5
encryption
algorithm
0/1
N/A

GEA/5 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/6
encryption
algorithm
0/1
N/A

GEA/6 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>GEA/7
encryption
algorithm
0/1
N/A

GEA/7 encryption
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3730
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>LCS VA
capability
0/1
N/A

LCS VA capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to
UTRAN Iu
mode capability
0/1
N/A

inter-PS handover
(GERAN to UTRAN
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>PS inter-RAT
HO from
GERAN to EUTRAN S1
mode capability
0/1
N/A

inter-PS handover
(GERAN to E-UTRAN
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EMM
Combined
procedures
Capability
0/1
N/A

EMM combined
procedure capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>ISR support
0/1
N/A
Indicates whether ISR is

supported.
0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
>SRVCC to
GERAN/
UTRAN
capability
0/1
N/A

SRVCC-to-GERAN/
UTRAN handover
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3731
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>EPC capability
0/1
N/A

EPC capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>NF capability
0/1
N/A

0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
UE Network
Capability
N/A
N/A
Indicates the UE-related

terminal capability.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
>EPS
encryption
algorithm EEA0
supported
0/1
N/A

EPS encryption
algorithm EEA0 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA1
supported
0/1
N/A

EPS encryption
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm 128EEA2
supported
0/1
N/A

EPS encryption
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA3
supported
0/1
N/A

EPS encryption
algorithm EEA3 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3732
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>EPS
encryption
algorithm EEA4
supported
0/1
N/A

EPS encryption
algorithm EEA4 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA5
supported
0/1
N/A

EPS encryption
algorithm EEA5 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA6
supported
0/1
N/A

EPS encryption
algorithm EEA6 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS
encryption
algorithm EEA7
supported
0/1
N/A

EPS encryption
algorithm EEA7 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA0
supported
0/1
N/A

EIA0 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
0/1
N/A

PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3733
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>EPS integrity
0/1
N/A

PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA3
supported
0/1
N/A

EIA3 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA4
supported
0/1
N/A

EIA4 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA5
supported
0/1
N/A

EIA5 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA6
supported
0/1
N/A

EIA6 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>EPS integrity
algorithm EIA7
supported
0/1
N/A

EIA7 is supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA0
supported
0/1
N/A

UMTS encryption
algorithm UEA0 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3734
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>UMTS
encryption
algorithm
UEA1
supported
0/1
N/A

UMTS encryption
algorithm UEA1 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA2
supported
0/1
N/A

UMTS encryption
algorithm UEA2 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA3
supported
0/1
N/A

UMTS encryption
algorithm UEA3 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA4
supported
0/1
N/A

UMTS encryption
algorithm UEA4 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA5
supported
0/1
N/A

UMTS encryption
algorithm UEA5 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
encryption
algorithm
UEA6
supported
0/1
N/A

UMTS encryption
algorithm UEA6 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3735
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>UMTS
encryption
algorithm
UEA7
supported
0/1
N/A

UMTS encryption
algorithm UEA7 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UCS2 support
(UCS2)
0/1
N/A

is supported.
0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
>UMTS
integrity
algorithm UIA1
supported
0/1
N/A

UMTS integrity
algorithm UIA1 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA2
supported
0/1
N/A

UMTS integrity
algorithm UIA2 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA3
supported
0/1
N/A

UMTS integrity
algorithm UIA3 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA4
supported
0/1
N/A

UMTS integrity
algorithm UIA4 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3736
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>UMTS
integrity
algorithm UIA5
supported
0/1
N/A

UMTS integrity
algorithm UIA5 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA6
supported
0/1
N/A

UMTS integrity
algorithm UIA6 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>UMTS
integrity
algorithm UIA7
supported
0/1
N/A

UMTS integrity
algorithm UIA7 is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>NF capability
0/1
N/A

0 not supported
PS 11.0/PS
12.0/PS 12.1/PS
13.0
1 supported
>1xSRVCC
capability
0/1
N/A

1xSRVCC capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>Location
services (LCS)
notification
mechanisms
capability
0/1
N/A

LCS notification
mechanism capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
>LTE
Positioning
Protocol (LPP)
capability
0/1
N/A

LPP capability is
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)

3737
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
>Access class
control for
CSFB (ACCCSFB)
capability
0/1
N/A

CSFB-access-level
supported.
PS 11.0/PS
12.0/PS 12.1/PS
13.0
0 not supported
1 supported
Issue 03 (2015-07-30)
MS P-TMSI
0-2^32-1
N/A
P-TMSI received from a

terminal when a
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Allocated PTMSI
0-2^32-1
N/A
P-TMSI that the network

allocates to a terminal.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
User Index
N/A
N/A
Index number of a
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
User Home
PLMN
N/A
N/A
PLMN in the IMSI of a

subscriber. This
personal data
anonymization.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3738
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Special Service
Indication
N/A
N/A
Indication of a special
service. The values of
follows:
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
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.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Authentication
Flag
NoAuth
N/A
authentication.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
FirAuth
SecAuth
Issue 03 (2015-07-30)
IMEI Check
Flag
Yes/No
N/A
IMEI check.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
P-TMSI
Reallocation
Flag
Yes/No
N/A
P-TMSI reallocation.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3739
Nastar
Access Information
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
Type
N/A
N/A
Type of the signaling procedure.

following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SM
MM
Procedure Type
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure Init
Cause
N/A
N/A
Procedure initiating party (UE or

MME) and cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

Procedure Initiating Causes in the
appendix.
Access Network
Description
N/A
N/A
Description of the access network.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>Inter CN Node
Type
0/1
N/A
Access network type of the source

or target node in the Inter RAU or
Inter Relocation procedure.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
>Access Type
N/A
N/A

following:
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
GPRS
UMTS(W/TD)
LTE
>Source Access
Net Type
Issue 03 (2015-07-30)
N/A
N/A

new indicating the access network
type on the source node. This
cases.

PS 11.0/PS 12.0/
PS 12.1/PS 13.0
3740
Nastar
Issue 03 (2015-07-30)
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
>Target Access
Net Type
N/A
N/A

old indicating the access network
type on the target node. This
cases.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
SGW Change
Flag
0/1
N/A
Indicates whether the S-GW has

been changed in the TAU/HO
procedure.
PS 11.0/PS 12.0/
PS 12.1/PS 13.0
Access eNodeB
Information
N/A
N/A
Information about the eNodeB that

serves a terminal when a signaling
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>eNodeB
PLMN
N/A
N/A
PLMN of the eNodeB where a UE

is located when a signaling
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>eNodeB ID
0-2^
32-1
N/A
ID of the eNodeB that serves a UE

when a signaling procedure is
initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME UE S1AP
ID
0-2^
32-1
N/A
UES1AP connection identification

procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME UE S1AP
ID Time
N/A
N/A

connection identification is
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Current TAC
N/A
N/A
Tracking area where a terminal is

located when a signaling procedure
is initiated.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
New GUTI
PLMN
N/A
N/A
PLMN of GUTI allocated by the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3741
Nastar
Issue 03 (2015-07-30)
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
New GUTI
MMEGI
0-65
535
N/A
MME Group Id of GUTI allocated

by the network in a traffic
procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
New GUTI
MMEC
0-25
5
N/A
MME CODE of GUTI allocated by

the network in a traffic procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
New GUTI
MTMSI
0-2^
32-1
N/A
M-TMSI of GUTI allocated by the

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old GUTI
PLMN
N/A
N/A
PLMN of GUTI received from a UE

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old GUTI
MMEGI
0-65
535
N/A
MME Group Id of GUTI received

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old GUTI
MMEC
0-25
5
N/A
MME CODE of GUTI received

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old GUTI
MTMSI
0-2^
32-1
N/A
M-TMSI of GUTI received from a

UE in a traffic procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Old TAC
N/A
N/A
ID of the old tracking area in a

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Target eNodeB
Information
N/A
N/A
Information about the target

eNodeB in an inter-eNodeB
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>Target ID
PLMN
N/A
N/A
PLMN of the target eNodeB in a

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3742
Nastar
Issue 03 (2015-07-30)
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
>Target ID
0-2^
32-1
N/A
ID of the target eNodeB in a

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Target TAC
N/A
N/A
ID of the target tracking area in a

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Gateway
Address
N/A
N/A
IP address of the Serving Gateway

in a signaling procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Gateway Host
Name
N/A
N/A
Domain name of the Serving

Gateway in a signaling procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
GU RAI
N/A
N/A

field is the RAC of the target routing
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
GU Cell
N/A
N/A

field is the CGI of the target cell.
Otherwise, the field is empty.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
GU Old RAI
N/A
N/A
If a UE is handed over from a 2G/

3G network to a LTE network or the
field is the RAC of the old routing
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Mobility
Information
N/A
N/A
Information about mobility

analysis.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
>Old SGSN IP
N/A
N/A
If a procedure involves two SGSNs,

the field indicates the IP address of
the old SGSN.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3743
Nastar
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
DNS Domain
Type
0-20
N/A
DNS Domain Type in MM produce.
PS 12.0/PS 12.1/
PS 13.0
254
Result Information
Parameter
Range
Unit
Description
Supported
Solution Version
EPS Attach
Result
N/A
N/A
Helps identify the

attach procedure.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
EPS only
combined EPS/IMSI
attach
EPS Update
Result
N/A
N/A
Helps identify the

RAU procedure. The
values of this
parameter are as
follows:
PS 11.0/PS 12.0/PS
12.1/PS 13.0
TA updated
combined TA/LA
updated
TA updated and ISR
activated (NOTE)
combined TA/LA
updated and ISR
activated (NOTE)
Additional
Update Result
N/A
N/A
Result of the
additional update
procedure. The values
of this parameter are
as follows:
PS 11.0/PS 12.0/PS
12.1/PS 13.0
no additional
information
CS Fallback not
preferred
SMS only
reserved
Issue 03 (2015-07-30)

3744
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
SGS RePaging
Count
N/A
N/A
Sgs paging repeat

sending times.
Default is 0, means no
repeat sending.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
VoIMS Bear
Status
N/A
N/A
To describe the Voice

bearer(QCI=1) status
before and after the
Procedure. Bit1~Bit2
is used,Bit3~Bit8 is
retain.Default value is
0.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
VoIMS Bearer Status

(octet 1) Bearer of
QCI1 Exist Flag
before Handover
1).
Exist before
Handover Procedure.
1 Bearer of QCI1
Exist before
Handover Procedure
Bearer(QCI=1) Exist
Flag after Handover
2).
Procedure.
1 Bearer of QCI1
Procedure.
Issue 03 (2015-07-30)

3745
Nastar
Parameter
Range
Unit
Description
Supported
Solution Version
SRVCC Cause
ID
N/A
N/A
SRVCC cause value.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
In case of SRVCC(CS
+PS), SRVCC Cause
is used to describe PS
Handover failure
cause,Huawei's
Cause is used to
describe CS
Handover failure
cause.
Default value is 0. In
case of SRVCC(CS
Only) or no-SRVCC,
the value is fixed to 0.
In case of SRVCC(CS
+PS), the value is
meaningful.
Issue 03 (2015-07-30)
SRVCC Cause
N/A
N/A
Description of
SRVCC cause.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
VoIMS Bear
Status
N/A
N/A
Status of a voice
bearer (with a leve-1
QCI) before and after
the procedure is
executed.
PS 11.0/PS 12.0/PS
12.1/PS 13.0
Protocol Cause
N/A
N/A
Protocol cause value

in a procedure result.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Protocol Cause
Description
N/A
N/A
Description of a
protocol cause.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Huawei's Cause
N/A
N/A

failure cause value.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0
Huawei's Cause
Description
N/A
N/A
knowledge base.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/PS
13.0

3746
Nastar
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.
Base Information
Parameter
Range
Unit
Description
Supported
Solution
Version
CHR SN
[1,2^31-1
)
N/A
SN of a reported CHR. The SN

accumulates on an NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
End Time
N/A
N/A

procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
NE Type
GGSN
N/A
CN NE types for the signaling

procedure.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
N/A
Name of a CN NE.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SGW
PGW
SGW
+PGW
NE Name
N/A
User Information
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

User ID: Alias
N/A
N/A

Alias, which is created by the user
Issue 03 (2015-07-30)

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
3747
Nastar
Parameter
Ran
ge
Unit
Description
Supported
Solution
Version
MSISDN
N/A
N/A
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

Terminal Model
N/A
N/A
Model of the terminal that initiates

a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
IMEI-TAC
0000
0000
-999
9999
9
N/A
IMEI-TAC of the terminal that

initiates a service.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure Information-Common
Parameter
Range
Unit
Description
Supported
Solution
Version
Procedure Type
N/A
N/A
Name of a signaling
procedure.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
APN
N/A
N/A
Requested APN in a traffic

procedure.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Access Net
Type
NA
N/A
Type of the RAN involved in

the signaling procedure
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
UTRAN
GERAN
WLAN
GAN
HSPA
Evolution
EUTRAN
Issue 03 (2015-07-30)

3748
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal
Cause
N/A
N/A

carried in an Access
message.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

Description of Exception
Cause in the appendix.
Procedure Information-Create PDP

Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Type
X25
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PPP
OSP_IHOS
S
IPV4
IPV6
IPV4V6
Issue 03 (2015-07-30)
MS IP V4
N/A
N/A

subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS IP V6
N/A
N/A

subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN Address
for Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3749
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN IPv6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN Address
for Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN IPv6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN Address
for Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN IPv6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN Address
for Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN IPv6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Protocol
Version
GTPv0
N/A
Version of the GTP protocol
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GTPv1
GTPv2
Issue 03 (2015-07-30)

3750
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Cause
N/A
N/A

response message for creating
the PDP context. For details, see
7.7.1 in 3GPP 29.060.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN PLMN
N/A
N/A
Information about the PLMN

served by the access SGSN
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SAC
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CI
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Netwrok Layer
Service Access
Point Identifier
N/A
N/A
Identity of the service access

point (SAP) in the network
layer
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Activation Type
First
activation
N/A
Identifies whether an activation

is a first or second activation
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Second
activation
Unknown
Issue 03 (2015-07-30)

3751
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
TEID-C
N/A
N/A
Identity of the GTP-C tunneling

protocol
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Charging
Characteristics
Unspecifie
d
N/A

characteristics.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Hot billing
Charging

documentation.
Flat rate
Charging
Prepaid
Charging
Normal
Charging
Reliability
Class
N/A
N/A

following:
Unused. If received, it shall be
interpreted as '010' (Note)
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Unacknowledged GTP;
Acknowledged LLC and RLC,
Protected data
Protected data
and RLC, Protected data
and RLC, Unprotected data
Delay Class
N/A
N/A
Subscribed delay class. This

following:
Delay class 1
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Delay Class 2
Delay Class 3
Reserved
Issue 03 (2015-07-30)

3752
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Precedence
Class
N/A
N/A
Subscribed precedence. This

following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
High priority
Normal priority
Low priority
Reserved
Peak
Throughput
N/A
N/A
Subscribed peak throughput.

following:
Subscribed peak throughput
Up to 1 000 octet/s
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Up to 2 000 octet/s
Up to 4 000 octet/s
Up to 8 000 octet/s
Reserved
Issue 03 (2015-07-30)

3753
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Mean
Throughput
N/A
N/A
Subscribed mean throughput.

following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
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
Erroneous SDU
N/A
N/A
following:
erroneous SDUs
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
No detect('-')
Erroneous SDUs are delivered
('yes')
delivered ('no')
Reserved
Issue 03 (2015-07-30)

3754
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Delivery Order
N/A
N/A
Subscribed delivery order. This

following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

Without delivery order ('no')
Reserved
Traffic Class
N/A
N/A
Subscribed traffic class. This

following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Streaming class
Interactive class
Background class
Reserved
Maximum SDU
Size
0-255
Byte
Maximum SDU length.

Subscribed maximum SDU size
150: 10~1500 octets
151: 1502 octets
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
152: 1510 octets

153: 1520 octets
Reserved
Issue 03 (2015-07-30)
Maximum Bit
Rate for Uplink
0-8640
Maximum Bit
Rate for
Downlink
0-256000
bps
Maximum uplink rate

for uplink
bps

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
3755
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SDU Error
Ratio
N/A
N/A

following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
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
Reserved
Residual BER
N/A
N/A

following:
5*10^2
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
1*10^2
5*10^3
4*10^3
1*10^3
1*10^4
1*10^5
1*10^6
6*10^8
Reserved
Traffic
Handling
priority
N/A
N/A

Subscribed traffic handling
priority
Priority level 1
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Priority level 2
Priority level 3
Issue 03 (2015-07-30)

3756
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Transfer Delay
0-255
ms
Transfer delay.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

10~150ms
200~950ms
1000~4000ms
Reserved
Guaranteed Bit
Rate for Uplink
0-8640
Guaranteed Bit
Rate for
Downlink
0-256000
bps

for uplink.
bps
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure Information-Update PDP/Delete PDP

Parameter
Range
Unit
Description
Supported
Solution
Version
PDP Type
X25
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PPP
OSP_IHOSS
IPV4
IPV6
IPV4V6
Issue 03 (2015-07-30)
MS IP V4
N/A
N/A

the subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS IP V6
N/A
N/A

the subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3757
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SGSN Address
for Signaling
N/A
N/A
IPv4 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN IPv6
Address for
Signaling
N/A
N/A
IPv6 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN Address
for Data
N/A
N/A
IPv4 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN IPv6
Address for
Data
N/A
N/A
IPv6 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN Address
for Signaling
N/A
N/A
IPv4 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN IPv6
Address for
Signaling
N/A
N/A
IPv6 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN Address
for Data
N/A
N/A
IPv4 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GGSN IPv6
Address for
Data
N/A
N/A
IPv6 address for

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3758
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Protocol
Version
GTPv0
N/A
Version of the GTP

protocol
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
N/A

procedure recorded in the
CHR.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
GTPv1
GTPv2
Procedure
Organizer
SSGN
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Cause
N/A
N/A

response message for
creating the PDP context.
For details, see 7.7.1 in
3GPP 29.060.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SGSN PLMN
N/A
N/A

PLMN served by the access
SGSN
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A

triggered
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A

triggered
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SAC
N/A
N/A

triggered
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3759
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
CI
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Netwrok Layer
Service Access
Point Identifier
N/A
N/A
Identity of the service

access point (SAP) in the
network layer
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
TEID-C
N/A
N/A
Identity of the GTP-C

tunneling protocol
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Charging
Characteristics
Unspecified
N/A

characteristics.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Hot billing
Charging
Flat rate
Charging

description, see UGW
Prepaid
Charging
Normal
Charging
Issue 03 (2015-07-30)

3760
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Reliability Class
N/A
N/A

of the following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Unused. If received, it shall

be interpreted as
'010' (Note)
Unacknowledged GTP;
RLC, Protected data
Protected data
Unacknowledged GTP,
data
Unacknowledged GTP,
LLC, and RLC,
Unprotected data
Delay Class
N/A
N/A

of the following:
Delay class 1
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Delay Class 2
Delay Class 3
Reserved
Precedence
Class
N/A
N/A
of the following:
High priority
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Normal priority
Low priority
Reserved
Issue 03 (2015-07-30)

3761
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Peak
Throughput
N/A
N/A
Subscribed peak
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
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
Reserved
Issue 03 (2015-07-30)

3762
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Mean
Throughput
N/A
N/A
Subscribed mean
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
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
Erroneous SDU
N/A
N/A
following:
erroneous SDUs
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
No detect('-')
Erroneous SDUs are
delivered('yes')
delivered ('no')
Reserved
Issue 03 (2015-07-30)

3763
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Delivery Order
N/A
N/A
Subscribed delivery order.

of the following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

('no')
Reserved
Traffic Class
N/A
N/A

of the following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Streaming class
Interactive class
Background class
Reserved
Maximum SDU
Size
0-255
Byte
Maximum SDU length.

Subscribed maximum SDU
size
150: 10~1500 octets
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
151: 1502 octets

152: 1510 octets
153: 1520 octets
Reserved
Issue 03 (2015-07-30)
Maximum Bit
Rate for Uplink
0-8640
Maximum Bit
Rate for
Downlink
0-256000
bps
Maximum uplink rate

rate for uplink
bps

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
3764
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SDU Error
Ratio
N/A
N/A

of the following:
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

ratio
1*10^2
7*10^3
1*10^3
1*10^4
1*10^5
1*10^6
1*10^1
Reserved
Residual BER
N/A
N/A

of the following:
5*10^2
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
1*10^2
5*10^3
4*10^3
1*10^3
1*10^4
1*10^5
1*10^6
6*10^8
Reserved
Traffic
Handling
priority
N/A
N/A

Subscribed traffic
handling priority
Priority level 1
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Priority level 2
Priority level 3
Issue 03 (2015-07-30)

3765
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Transfer Delay
0-255
ms
Transfer delay.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

10~150ms
200~950ms
1000~4000ms
Reserved
Guaranteed Bit
Rate for Uplink
0-8640
Guaranteed Bit
Rate for
Downlink
0-256000
bps

rate for uplink.
bps
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure Information-Create Session
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^311)
N/A

procedures for the same subscriber.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure NO.
[1,2^311)
N/A

for a subscriber
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3766
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Message
Organizer
SSGN
N/A

recorded in the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW
+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
Logical CPU No. of the device that

processes the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A

processes the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
SPU instance No. of the device that

processes the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Serving
Network
N/A
N/A

serving network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CI
N/A
N/A
CGI information, including MCC,

MNC, LAC, and CI
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3767
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SAC
N/A
N/A
SAI information, including MCC,

MNC, LAC, and SAC
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A
RAI information, including MCC,

MNC, LAC, and RAC
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
TAC
N/A
N/A
TAI information, including MCC,

MNC, and TAC
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
ECI
N/A
N/A

MCC, MNC, and ECI
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A
LAI information, including MCC,

MNC, and LAC
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS IP V4
N/A
N/A

subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS IP V6
N/A
N/A

subscriber's MS
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV4
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3768
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Peer IPV4
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3769
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Selection Mode
MS or
network
provided
APN,
subscrib
ed
verified
N/A
APN selection mode
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
N/A
Type of the PDN, including IPv4,

IPv6, and IPv4v6
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS
provided
APN,
subscrip
tion not
verified
Network
provided
APN,
subscrip
tion not
verified
PDN Type
IPv4
IPv6
IPv4v6
Issue 03 (2015-07-30)
Linked EPS
Bearer ID
N/A
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
EPS Bearer ID
N/A
N/A

connection
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS PCI
N/A
N/A
PCI in the Bearer QoS parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3770
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer QoS PL
N/A
N/A
PL in the Bearer QoS parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS PVI
N/A
N/A
PVI in the Bearer QoS parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS QCI
N/A
N/A
QCI in the Bearer QoS parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS
MBRU
N/A
N/A

parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS
MBRD
N/A
N/A

parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS
GBRU
N/A
N/A

parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer QoS
GBRD
N/A
N/A

parameter
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
UE Time Zone
N/A
N/A
Time zone information of the UE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3771
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Charging
Characteristics
Unspeci
fied
N/A

characteristics.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Hot
billing
Chargin
g

documentation.
Flat rate
Chargin
g
Prepaid
Chargin
g
Normal
Chargin
g
Protocol Cause
N/A
N/A

response message
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure Information-Delete Session
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A
Unique ID of the
whole
procedure for a
subscriber to use
a web service
through the MS.
This parameter
distinguishes
between the
multiple web
service
procedures for
the same
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3772
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Procedure NO.
[1,2^31-1)
N/A
Unique No. of
each service
procedure in the
whole
procedure for a
subscriber
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Message
Organizer
SSGN
N/A
Initiator of the
signaling
message
recorded in the
CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A
Logical board
No. of the
device that
processes the
CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
Logical CPU
No. of the
device that
processes the
CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
SPU group No.

of the device
that processes
the CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
SPU instance
No. of the
device that
processes the
CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Serving
Network
N/A
N/A
MCC and MNC

of the
subscriber's
serving network
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
CI
N/A
N/A
CGI
information,
including MCC,
MNC, LAC, and
CI
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3773
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SAC
N/A
N/A
SAI
information,
including MCC,
MNC, LAC, and
SAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A
RAI
information,
including MCC,
MNC, LAC, and
RAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
TAC
N/A
N/A
TAI
information,
including MCC,
MNC, and TAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
ECI
N/A
N/A
ECGI
information,
including MCC,
MNC, and ECI
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A
LAI
information,
including MCC,
MNC, and LAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Linked EPS
Bearer ID
N/A
N/A
ID of the default
bearer. This
parameter can
also be used to
identify the
PDN
connection.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
EPS Bearer ID
N/A
N/A
ID of all bearers
(including the
default bearer)
for the PDN
connection
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
UE Time Zone
N/A
N/A
Time zone
information of
the UE
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3774
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Protocol Cause
N/A
N/A
Standard cause
value carried in
the response
message
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure Information-Create Bearer/Modify Bearer/Update Bearer

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^311)
N/A

procedure for a subscriber to use
a web service through the MS.
This parameter distinguishes
service procedures for the same
subscriber.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure No.
[1,2^311)
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Message
Organizer
SSGN
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW
+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3775
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SPU Group
N/A
N/A

processes the CHR
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
CI
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
SAC
N/A
N/A

MCC, MNC, LAC, and SAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
RAC
N/A
N/A

MCC, MNC, LAC, and RAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
TAC
N/A
N/A

MCC, MNC, and TAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
ECI
N/A
N/A

MCC, MNC, and ECI
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
LAC
N/A
N/A

MCC, MNC, and LAC
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Peer IPV4
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3776
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Peer IPV4
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Signaling
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Data
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure
Transaction ID
(PTI)
N/A
N/A

procedure ends.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Linked EPS
Bearer ID
N/A
N/A

PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3777
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
EPS Bearer ID
N/A
N/A

connection
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS PCI
N/A
N/A
PCI in the Flow QoS parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS PL
N/A
N/A
PL in the Flow QoS parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS PVI
N/A
N/A
PVI in the Flow QoS parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS QCI
N/A
N/A
QCI in the Flow QoS parameter PS 10.0/PS

10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS
MBRU
N/A
N/A

parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS
MBRD
N/A
N/A

parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS
GBRU
N/A
N/A

parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Bearer QoS
GBRD
N/A
N/A

parameter
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
UE Time Zone
N/A
N/A
Time zone information of the

UE
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0

3778
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Protocol Cause
N/A
N/A
Standard cause value carried in

the response message
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure
Transaction ID
(PTI)
N/A
N/A

procedure ends.
PS 10.0/PS
10.1/PS10.2/PS
11.0/PS12.0/PS
12.1/PS 13.0
Procedure Information-Delete Bearer

Parameter
Range
Uni
t
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

same subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure NO.
[1,2^31-1)
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Message
Organizer
SSGN
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Slot
Issue 03 (2015-07-30)
N/A

3779
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported
Solution
Version
CPU
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Group
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Instance
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CI
N/A
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SAC
N/A
N/A

MCC, MNC, LAC, and
SAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAC
N/A
N/A

MCC, MNC, LAC, and
RAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
TAC
N/A
N/A

MCC, MNC, and TAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
ECI
N/A
N/A
ECGI information,
including MCC, MNC, and
ECI
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
LAC
N/A
N/A

MCC, MNC, and LAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3780
Nastar
Parameter
Range
Uni
t
Description
Supported
Solution
Version
EPS Bearer ID
N/A
N/A

PDN connection
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
UE Time Zone
N/A
N/A

the UE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Protocol Cause
N/A
N/A

message
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure Information-Release Access Bearers

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31
-1)
N/A

subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure NO.
[1,2^31
-1)
N/A

for a subscriber
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Message
Organizer
SSGN
N/A

recorded in the CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME
GGSN
SGW
PGW
SGW
+PGW
Issue 03 (2015-07-30)

3781
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Slot
N/A
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CPU
N/A
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Group
N/A
N/A

processes the CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Instance
N/A
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Network
N/A
N/A

serving network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
EPS Bearer ID
N/A
N/A

connection
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Protocol Cause
N/A
N/A

response message
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3782
Nastar
Procedure Information-Modify Bearer Command/Delete Bearer Command

Parameter
Range
Uni
t
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

same subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure NO.
[1,2^31-1)
N/A

PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Message
Organizer
SSGN
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CPU
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Group
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Instance
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3783
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported
Solution
Version
EPS Bearer ID
N/A
N/A

PDN connection
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS PCI
N/A
N/A
PCI in the Bearer QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS PL
N/A
N/A
PL in the Bearer QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS PVI
N/A
N/A
PVI in the Bearer QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS QCI
N/A
N/A
QCI in the Bearer QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS
MBRU
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS
MBRD
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS
GBRU
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Bearer QoS
GBRD
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
UE Time Zone
N/A
N/A

the UE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3784
Nastar
Parameter
Range
Uni
t
Description
Supported
Solution
Version
Protocol Cause
N/A
N/A

message
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure Information-Bearer Resource Command

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

procedure for a
This parameter
subscriber.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Procedure No.
[1,2^31-1)
N/A
Unique No. of each

subscriber
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Message
Organizer
SSGN
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CPU
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3785
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SPU Group
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SPU Instance
N/A
N/A

CHR
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

network
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
CI
N/A
N/A
CGI information,
including MCC, MNC,
LAC, and CI
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
SAC
N/A
N/A
SAI information,
including MCC, MNC,
LAC, and SAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
RAC
N/A
N/A
RAI information,
including MCC, MNC,
LAC, and RAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
TAC
N/A
N/A
TAI information,
including MCC, MNC,
and TAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
ECI
N/A
N/A
ECGI information,
including MCC, MNC,
and ECI
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
LAC
N/A
N/A
LAI information,
including MCC, MNC,
and LAC
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Peer IPV4
Address for
Signaling
N/A
N/A
IPv4 address for

plane of the CN NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3786
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Peer IPV4
Address for
Data
N/A
N/A
IPv4 address for

plane of the CN NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Local IPV4
Address for
Signaling
N/A
N/A
IPv4 address for

plane of the NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Local IPV4
Address for
Data
N/A
N/A
IPv4 address for

plane of the NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Peer IPV6
Address for
Signaling
N/A
N/A
IPv6 address for

plane of the CN NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Peer IPV6
Address for
Data
N/A
N/A
IPv6 address for

plane of the CN NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Local IPV6
Address for
Signaling
N/A
N/A
IPv6 address for

plane of the NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Local IPV6
Address for
Data
N/A
N/A
IPv6 address for

plane of the NE
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Linked EPS
Bearer ID
N/A
N/A
ID of the default bearer.

This parameter can also
be used to identify the
PDN connection.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
EPS Bearer ID
N/A
N/A
ID of all bearers
bearer) for the PDN
connection
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3787
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Procedure
Transaction ID
(PTI)
N/A
N/A
ID dynamically allocated
by the UE used for
modifying and
resources requested by
the UE. The PTI is
released when the
modification or
deactivation procedure
ends.
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS QCI
N/A
N/A
QCI in the Flow QoS

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS
MBRU
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS
MBRD
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS
GBRU
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Flow QoS
GBRD
N/A
N/A

parameter
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0
Protocol Cause
N/A
N/A

message
PS 10.0/PS 10.1/
PS10.2/PS 11.0/
PS12.0/PS 12.1/
PS 13.0

3788
Nastar
Procedure Information-Create Indirect Data Forwarding

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

procedure for a
This parameter
subscriber.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure NO.
[1,2^31-1)
N/A
Unique No. of each

subscriber
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Message
Organizer
SSGN
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)
Slot
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3789
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Serving
Network
N/A
N/A
MCC and MNC of the

network
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV4
Address for
Signaling
N/A
N/A
IPv4 address for

plane of the CN NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV4
Address for
Data
N/A
N/A
IPv4 address for

plane of the CN NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Signaling
N/A
N/A
IPv4 address for

plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV4
Address for
Data
N/A
N/A
IPv4 address for

plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Signaling
N/A
N/A
IPv6 address for

plane of the CN NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Peer IPV6
Address for
Data
N/A
N/A
IPv6 address for

plane of the CN NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Local IPV6
Address for
Signaling
N/A
N/A
IPv6 address for

plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3790
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Local IPV6
Address for
Data
N/A
N/A
IPv6 address for

plane of the NE
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
EPS Bearer ID
N/A
N/A
ID of all bearers
bearer) for the PDN
connection
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Protocol Cause
N/A
N/A

message
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure Information-Delete Indirect Data Forwarding

Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
[1,2^31-1)
N/A

procedure for a subscriber to
use a web service through the
MS. This parameter
distinguishes between the
multiple web service
subscriber.
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Procedure NO.
[1,2^31-1)
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Message
Organizer
SSGN
N/A

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MME
GGSN
SGW
PGW
SGW+PGW
Issue 03 (2015-07-30)

3791
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Slot
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
SPU group No. of the device

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A

CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Serving
Network
N/A
N/A
MCC and MNC of the

PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
EPS Bearer ID
N/A
N/A

PDN connection
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Protocol Cause
N/A
N/A
Standard cause value carried

in the response message
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0

3792
Nastar
Procedure Information-Traffic
Parameter
Range
Unit
Description
Supported
Solution
Version
UL Total
Volume
[1,2^31-1)
Type
Uplink traffic volume

recorded in the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
DL Total
Volume
[1,2^31-1)
Type
Downlink traffic volume

recorded in the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Total Volume
[1,2^31-1)
Type
Total traffic volume

recorded in the CHR
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
First URL
N/A
N/A
First 20 bytes of the first

procedure
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
MS Side Port of
First URL
N/A
N/A

UE side) of the first URL
that the subscriber visits
during a service procedure
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Network Side
Port of First
URL
N/A
N/A

network side) of the first
procedure
PS 10.0/PS
10.1/PS10.2/
PS 11.0/
PS12.0/PS
12.1/PS 13.0
Bearer Duration
N/A
Bearer online duration.
PS 13.0 or
later
NOTE
When the duration is less than
1s, 1s is used.
Issue 03 (2015-07-30)
Bearer TEIDU
N/A
N/A
Bearer TEIDU information.
PS 13.0 or
later
MS IP V4
N/A
N/A

subscriber's MS
PS 13.0 or
later

3793
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MS IP V6
N/A
N/A

subscriber's MS
PS 13.0 or
later
Procedure-Authentication access
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A
Access Point
Name for real
used
PS 12.0/PS
12.1/PS 13.0
RAT Type
UTRAN 1
N/A
access type
when the
context is
activated
PS 12.0/PS
12.1/PS 13.0
N/A
the Time Zone

for this NE
PS 12.0/PS
12.1/PS 13.0
GERAN 2
WLAN 3
GAN 4
HSPA
Evolution 5
EUTRAN 6
FF
NE Time Zone
Issue 03 (2015-07-30)
N/A

3794
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Anonymous
Switch
No scramble 0
N/A
Whether
personal
information
anonymized
PS 12.0/PS
12.1/PS 13.0
private cause
0-4294967295
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
Delay time
0-65535
ms
Delay time from

request message
to response
message.
PS 12.0/PS
12.1/PS 13.0
User-NameReq
N/A
N/A
user-name from
access-request
message
PS 12.0/PS
12.1/PS 13.0
Framed-IPAddress-Req
N/A
N/A
indicates the
identifying IP
Address of the
NAS which is
requesting
authentication
of the user, and
is unique to the
NAS within the
scope of the
RADIUS server
PS 12.0/PS
12.1/PS 13.0
Framed-IPv6Prefix-Req
N/A
N/A
The attribute
Framed-IPv6Prefix in
Access-Request
message
PS 12.0/PS
12.1/PS 13.0
FramedInterface-IdReq
N/A
N/A
The attribute
FramedInterface-Id in
Access-Request
message
PS 12.0/PS
12.1/PS 13.0
Scramble 1

3795
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
NAS-IPAddress
N/A
N/A
indicates the
identifying IP
Address of the
NAS which is
requesting
authentication
of the user, and
is unique to the
NAS within the
scope of the
RADIUS server
PS 12.0/PS
12.1/PS 13.0
EventTimestamp
1-4294967295
N/A
The timestamp
of this message
being sent out.
PS 12.0/PS
12.1/PS 13.0
Charging-Id
1-4294967295
N/A
This Attribute
specifies a
unique ID for
GPRS charging
for the user
PS 12.0/PS
12.1/PS 13.0
SessionTimeout
30-4294967295
Second
This Attribute
sets the
maximum
number of
seconds of
service to be
provided to the
user before
termination of
the session or
prompt
PS 12.0/PS
12.1/PS 13.0
Idle-Timeout
30-4294967295
Second
This Attribute
sets the
maximum
number of
consecutive
seconds of idle
connection
allowed to the
user before
termination of
the session or
prompt
PS 12.0/PS
12.1/PS 13.0

3796
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Framed-Pool
N/A
N/A
This Attribute
contains the
name of an
assigned
address pool
that is used to
assign an
address for the
user
PS 12.0/PS
12.1/PS 13.0
HW-PrimaryDNS-Server
N/A
N/A
This Attribute
indicates the IP
address of the
primary DNS
Server
PS 12.0/PS
12.1/PS 13.0
HWSecondaryDNS-Server
N/A
N/A
This Attribute
indicates the IP
address of the
secondary DNS
Server
PS 12.0/PS
12.1/PS 13.0
HW-SESSIONFLOW-OUT
1000-42949672
95
Biye
This Attribute
HW-SESSIONFLOW-OUT is
from the
response
message
PS 12.0/PS
12.1/PS 13.0
HW-ChargeRule-BaseName
N/A
N/A
HW-ChargingRule-BaseName will be
used as a pointer
into a list of
charging-rules
PS 12.0/PS
12.1/PS 13.0

3797
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
HW-SessionCharging-Type
prepaid: 0
N/A
This attribute
defines the
charging type
for the user
session.
PS 12.0/PS
12.1/PS 13.0
post-paid with
credit control: 2
prepaid with
credit control: 3
The Value field

contains the
charging
profile.
HLR: 4
wallet specific:
5
wallet specific
without credit
control: 6
0 = prepaid
1 = post-paid
2 = post-paid
with credit
control
hot billing: 7
FF
3 = prepaid with
credit card
4 = HLR
5 = wallet
specific
6 = wallet
specific w
Issue 03 (2015-07-30)
HW-OCS-ID1
0-65535
N/A
This attribute
defines the
primary OCS
server.
PS 12.0/PS
12.1/PS 13.0
HW-OCS-ID2
0-65535
N/A
This attribute
defines the
primary OCS
server.
PS 12.0/PS
12.1/PS 13.0
HW-QOS-ID
0-255
N/A
The attribute
defines the QoS
information to
be applied for
the PDP
context.
PS 12.0/PS
12.1/PS 13.0
User-Name-Rsp
N/A
N/A
user-name from
response
message
PS 12.0/PS
12.1/PS 13.0

3798
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Framed-IPAddress-Rsp
N/A
N/A
Framed-IPAddress from
response
message,the real
user IP
PS 12.0/PS
12.1/PS 13.0
Framed-IPv6Prefix-Rsp
N/A
N/A
Framed-IPv6Prefix from
response
message
PS 12.0/PS
12.1/PS 13.0
FramedInterface-IdRsp
N/A
N/A
FramedInterface-Id
from response
message
PS 12.0/PS
12.1/PS 13.0
AAA-IPADDR
N/A
N/A
the IP adress of
AAA server
which receive
the request
message
PS 12.0/PS
12.1/PS 13.0
AAA-PORT
1-65535
N/A
the port of AAA

server which
receive the
request message
PS 12.0/PS
12.1/PS 13.0
Framed-Route
[0,200]
Byte
Subscriber route
segment in a
response
message
PS 12.0/PS
12.1/PS 13.0
Procedure-Radius accounting
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0

3799
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Slot
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
0~0xffffffff
byte
This attribute
indicates how
many octets
have been
received from
the port over the
course of this
service being
provided
PS 12.0/PS
12.1/PS 13.0
RAT Type
0~0xffffffff
byte
This attribute
indicates how
many octets
have been sent
to the port in the
course of
delivering this
service
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
This attribute is
a unique
Accounting ID
to make it easy
to match start
and stop records
in a log file.
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
0~0xffffffff
Second
This attribute
indicates how
many seconds
the user has
received service
PS 12.0/PS
12.1/PS 13.0

3800
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
private cause
0~0xffffffff
packet
This attribute
indicates how
many packets
have been
received from
the port over the
course of this
service being
provided to a
Framed User
PS 12.0/PS
12.1/PS 13.0
Delay time
0~0xffffffff
packet
This attribute
indicates how
many packets
have been sent
to the port in the
course of
delivering this
service to a
Framed User
PS 12.0/PS
12.1/PS 13.0
User-Name
1~18
N/A
This attribute
indicates how
the session was
terminated
PS 12.0/PS
12.1/PS 13.0
NAS-IPAddress
N/A
N/A
This attribute is
a unique
Accounting ID
to make it easy
to link together
multiple related
sessions in a log
file.
PS 12.0/PS
12.1/PS 13.0
Framed-IPAddress
0~0xffffffff
Number
This attribute
gives the count
of links which
are known to
have been in a
given multilink
session at the
time the
accounting
record is
generated.
PS 12.0/PS
12.1/PS 13.0

3801
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Framed-IPv6Prefix
0~0xffffffff
N/A
This attribute
indicates how
many times the
Acct-InputOctets counter
has wrapped
around 2^32
over the course
of this service
being provided
PS 12.0/PS
12.1/PS 13.0
FramedInterface-Id
0~0xffffffff
N/A
This attribute
indicates how
many times the
Acct-OutputOctets counter
has wrapped
around 2^32 in
the course of
delivering this
service
PS 12.0/PS
12.1/PS 13.0
Acct-StatusType
0~0xffffffff
Second
The EventTimestamp
SHOULD be
included in the
request and
contains the
time when the
request was
sent.
PS 12.0/PS
12.1/PS 13.0
Acct-DelayTime
0~0xffffffff
N/A
charging id
PS 12.0/PS
12.1/PS 13.0
Acct-InputOctets
0~0xff
N/A
prepaid
indicator,filled
with the low
byte of CC
PS 12.0/PS
12.1/PS 13.0
Acct-OutputOctets
N/A
N/A
The IP address
of AAA
accounting
server
PS 12.0/PS
12.1/PS 13.0
Acct-Session-Id
0~65535
N/A
The Port of
AAA
accounting
server
PS 12.0/PS
12.1/PS 13.0

3802
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Acct-SessionTime
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Acct-InputPackets
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
Acct-OutputPackets
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
AcctTerminateCause
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
Acct-LinkCount
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
Acct-InputGigawords
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
Acct-OutputGigawords
N/A
N/A
Access Point
Name for real
used
PS 12.0/PS
12.1/PS 13.0
EventTimestamp
UTRAN 1
N/A
access type
when the
context is
activated
PS 12.0/PS
12.1/PS 13.0
GERAN 2
WLAN 3
GAN 4
HSPA
Evolution 5
EUTRAN 6
FF
Charging-Id
N/A
N/A
the Time Zone

for this NE
PS 12.0/PS
12.1/PS 13.0
Prepaid-Ind
No scramble 0
N/A
Whether
personal
information
anonymized
PS 12.0/PS
12.1/PS 13.0
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
Scramble 1
AAA-IPADDR
Issue 03 (2015-07-30)
0~4294967295

3803
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
AAA-PORT
65535
ms
Delay time from

request message
to response
message.
PS 12.0/PS
12.1/PS 13.0
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
User name for

disconnect
message
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
Indicates the
identifying IP
Address of the
NAS which is
requesting
authentication
of the user, and
is unique to the
NAS within the
scope of the
RADIUS server
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
the IP adress for

subscriber
surfing
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A
Identifying the
NAS
originating the
Access-Request
PS 12.0/PS
12.1/PS 13.0
Procedure-disconnect
Issue 03 (2015-07-30)

3804
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
CPU
N/A
N/A
This attribute is
a unique
Accounting ID
to make it easy
to match start
and stop records
in a log file. The
start and stop
records for a
given session
have the same
Acct-SessionId.
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
This attribute is
a unique
Accounting ID
to make it easy
to link together
multiple related
sessions in a log
file. Each
session linked
together would
have a unique
Acct-Session-Id
but the same
PS 12.0/PS
12.1/PS 13.0

3805
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
SPU Instance
0: Carrying 0
N/A
If the value of TI
is set to "1", then
all IP-CAN
bearers that
share the same
user session
with the IPCAN bearer
identified by the
Acct-Session-Id
shall be torn
down.
PS 12.0/PS
12.1/PS 13.0
1: Carrying 1
255: No
carrying
If the value of TI
is "0", or if TI is
missing, only
the IP-CAN
bearer identified
by the AcctSession-Id shall
be torn down. If
the AcctSesssion-Id
identifies the
default bearer,
the P-GW shall
tear down all the
IP-CAN bearers
that share the
same user
session
identified by the
Acct-Session-Id
Issue 03 (2015-07-30)
Access Point
Name (APN)
N/A
N/A
the IP adress of
AAA server
which send the
disconnect
message
PS 12.0/PS
12.1/PS 13.0
RAT Type
1-65535
N/A
the port of AAA

server which
send the
disconnect
message
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0

3806
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Anonymous
Switch
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Delay time
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
User-Name
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
NAS-IPAddress
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
Framed-IPAddress
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
NAS-Identifier
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
Acct-Session-Id
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
3GPPTeardown
Indicator
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0
AAA-IPADDR
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
AAA-PORT
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Procedure-Credit-Control Messages (Gy)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
Reserved
Information
PS 12.0/PS
12.1/PS 13.0

3807
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Procedure NO.
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
The origin-host
carried in CCR
messages
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A

CCR messages
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

CCR messages
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A

CCR messages
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
The origin-host
carried in CCA
messages
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A

CCA messages
PS 12.0/PS
12.1/PS 13.0
RAT Type
N/A
MUST be set to
the value 4,
indicating the
application.
PS 12.0/PS
12.1/PS 13.0

3808
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
NE Time Zone
1~4
N/A
of type
Enumerated and
contains the
reason for
sending the
credit-control
request
message. It
MUST be
present in all
messages.
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
0~0xffffffff
N/A
The CCRequestNumber
identifies this
request within
one session.
PS 12.0/PS
12.1/PS 13.0
private cause
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
Delay time
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0

3809
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Reserved Info
0~0xffffffff
Second
The EventTimestamp
SHOULD be
included in the
request and
contains the
time when the
request was
sent.
PS 12.0/PS
12.1/PS 13.0
Session-Id
0~1
N/A
The CCSessionFailover
contains
information as
to whether
moving the
credit-control
message stream
to a backup
server during an
ongoing creditcontrol session
is supported.
PS 12.0/PS
12.1/PS 13.0
Origin-HostCCR
0~2
N/A
The creditcontrol client

uses this AVP to
decide what to
do if sending
credit-control
messages to the
credit-control
server has been,
for instance,
temporarily
prevented due to
a network
problem.
PS 12.0/PS
12.1/PS 13.0

3810
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Origin-RealmCCR
1~8
N/A
The
indicate the
reason why a
session was
terminated on
the access
device.
PS 12.0/PS
12.1/PS 13.0
DestinationHost-CCR
N/A
N/A
MultipleServices-CreditControl AVP is
of type Grouped
and contains the
AVPs related to
the independent
credit-control of
multiple
services feature.
PS 12.0/PS
12.1/PS 13.0
DestinationRealm-CCR
1000~5999
N/A

whether a
MSCC was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
Origin-HostCCA
0~0xfffffffe
N/A
The RatingGroup AVP

contains the
identifier of a
rating group
PS 12.0/PS
12.1/PS 13.0
Origin-RealmCCA
0~0xfffffffe
N/A
contains the
identifier of a
service.
PS 12.0/PS
12.1/PS 13.0

3811
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
AuthApplication-Id
0~0xffffffff
Second
sent from the
server to the
client and
includes the
time in seconds
since January 1,
1900, 00:00
UTC, when the
tariff of the
service will be
changed.
PS 12.0/PS
12.1/PS 13.0
CC-RequestType
0~0xffffffff
Second
The TimeQuotaThreshold
contains a
threshold value
in seconds.
PS 12.0/PS
12.1/PS 13.0
CC-RequestNumber
0~0xffffffff
byte
The VolumeQuotaThreshold
contains a
threshold value
in octets.
PS 12.0/PS
12.1/PS 13.0
Result-Code
0~0xffffffff
time
The UnitQuotaThreshold
contains a
threshold value
in service
specific units.
PS 12.0/PS
12.1/PS 13.0
0~0xffffffff
Second
The QuotaHolding-Time
AVP contains
the quota
holding time in
seconds. The
client shall start
the quota
holding timer
when quota
consumption
ceases.
PS 12.0/PS
12.1/PS 13.0

3812
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
EventTimestamp
0~0xffffffff
Second
The QuotaConsumptionTime contains

an idle traffic
threshold time
in seconds.
PS 12.0/PS
12.1/PS 13.0
CC-SessionFailover
0~0xffffffff
Second
The ValidityTime is sent

from the creditcontrol server to
the creditcontrol client.
This AVP
contains the
validity time of
the granted
service units.
PS 12.0/PS
12.1/PS 13.0
Credit-ControlFailureHandling
0~4
N/A
This EnvelopeReporting is
used in the CCA
(INITIAL) to
indicate whether
the client shall
report the start
and end of each
time envelope,
in those cases in
which quota is
consumed in
envelopes
PS 12.0/PS
12.1/PS 13.0
TerminationCause
0~1
N/A
The TimePS 12.0/PS

Quota-Type
12.1/PS 13.0
AVP is used to
indicate which
time quota
consumption
mechanism
shall be used for
the associated
Rating Group.

3813
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MultipleServicesCredit-Control
0~0xffffffff
Second
The Base-TimeInterval
contains the
length of the
base time
interval, for
controlling the
consumption of
time quota, in
seconds.
PS 12.0/PS
12.1/PS 13.0
Result-Code
0~2
N/A
The Final-UnitAction indicates

to the creditcontrol client
the action to be
taken when the
user's account
cannot cover the
service cost.
PS 12.0/PS
12.1/PS 13.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rating-Group
N/A
N/A
The RedirectServer-Address
defines the
address of the
redirect server
(e.g., HTTP
redirect server)
with which the
end user is to be
connected when
the account
cannot cover the
service cost.
PS 12.0/PS
12.1/PS 13.0

3814
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
ServiceIdentifier
N/A
N/A
The RequestedService-Unit
contains the
amount of
requested units
specified by the
Diameter creditcontrol client.
PS 12.0/PS
12.1/PS 13.0
Tariff-TimeChange
0~0xffffffff
Second
The CC-Time
AVP indicates
the length of the
requested,
granted, or used
time in seconds.
PS 12.0/PS
12.1/PS 13.0
Time-QuotaThreshold
0~0xfffffffffffff
fff
byte

the total number
of requested,
granted, or used
octets
regardless of the
direction (sent
or received).
PS 12.0/PS
12.1/PS 13.0
Volume-QuotaThreshold
0~0xfffffffffffff
fff
byte
specifies the
number of
service-specific
units (e.g.,
number of
events, points)
given in a
selected service.
PS 12.0/PS
12.1/PS 13.0

3815
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Unit-QuotaThreshold
N/A
N/A
GrantedService-Unit
contains the
amount of units
that the
Diameter creditcontrol client
can provide to
the end user
until the service
must be released
or the new
Credit-ControlRequest must be
sent.
PS 12.0/PS
12.1/PS 13.0
Quota-HoldingTime
0~0xffffffff
Second
sent from the
server to the
client and
includes the
time in seconds
since January 1,
1900, 00:00
UTC, when the
tariff of the
service will be
changed.
PS 12.0/PS
12.1/PS 13.0
QuotaConsumptionTime
0~0xffffffff
Second
The CC-Time
AVP indicates
the length of the
requested,
granted, or used
time in seconds.
PS 12.0/PS
12.1/PS 13.0
Validity-Time
0~0xfffffffffffff
fff
byte

the total number
of requested,
granted, or used
octets
regardless of the
direction (sent
or received).
PS 12.0/PS
12.1/PS 13.0

3816
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
EnvelopeReporting
0~0xfffffffffffff
fff
byte
specifies the
number of
service-specific
units (e.g.,
number of
events, points)
given in a
selected service.
PS 12.0/PS
12.1/PS 13.0
Time-QuotaType
N/A
N/A
The UsedService-Unit
contains the
amount of used
units.
PS 12.0/PS
12.1/PS 13.0
Base-TimeInterval
0~2
N/A
The TariffChange-Usage
defines whether
units are used
before or after a
tariff change, or
whether the
units straddled a
tariff change
during the
reporting
period.
PS 12.0/PS
12.1/PS 13.0
Final-UnitAction
0~0xffffffff
Second
The CC-Time
AVP indicates
the length of the
requested,
granted, or used
time in seconds.
PS 12.0/PS
12.1/PS 13.0
RedirectServer-Address
0~0xfffffffffffff
fff
byte

the total number
of requested,
granted, or used
octets
regardless of the
direction (sent
or received).
PS 12.0/PS
12.1/PS 13.0

3817
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RequestedService-Unit
0~0xfffffffffffff
fff
byte
specifies the
number of
service-specific
units (e.g.,
number of
events, points)
given in a
selected service.
PS 12.0/PS
12.1/PS 13.0
CC-Time
0~8
N/A
The ReportingReason
specifies the
reason for usage
reporting for
one or more
types of quota
for a particular
category.
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
GrantedService-Unit
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Tariff-TimeChange
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
CC-Time
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0

3818
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
* Used-ServiceUnit
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
Tariff-ChangeUsage
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
CC-Time
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
ReportingReason
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
16777238
N/A
Gx application
ID
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
protocol version
PS 12.0/PS
12.1/PS 13.0

3819
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Slot
0~1
N/A
R970 dictionary
flag.
0:R940,1:R970
PS 12.0/PS
12.1/PS 13.0
CPU
1~3
N/A
of type
Enumerated and
contains the
reason for
sending the
credit-control
request
message. It
MUST be
present in all
messages.
PS 12.0/PS
12.1/PS 13.0
SPU Group
0~0xffffffff
N/A
The CCRequestNumber
identifies this
request within
one session.
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
CCR
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
RAT Type
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
N/A
PS 12.0/PS
12.1/PS 13.0

3820
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
private cause
1~8
N/A
The
indicate the
reason why a
session was
terminated on
the access
device.
PS 12.0/PS
12.1/PS 13.0
Delay time
0~1
N/A
The NetworkRequestSupport
indicates the UE
and network
support of the
network
requested bearer
control mode.
PS 12.0/PS
12.1/PS 13.0
Session-Id
0~6
N/A
The IP-CANType indicates

the type of
Connectivity
Access Network
in which the
user is
connected. The
IP-CAN-Type
AVP shall
always be
present during
the IP-CAN
session
establishment.
During an IPCAN session
modification,
this AVP shall
be present when
there has been a
change in the IPCAN type and
the PCRF
requested to be
informed of this
event.
PS 12.0/PS
12.1/PS 13.0

3821
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
AuthApplication-Id
0~1
N/A
session online
flag
PS 12.0/PS
12.1/PS 13.0
Protocol version
0~1
N/A
session offline
flag
PS 12.0/PS
12.1/PS 13.0
R970
N/A
N/A
The UserLocation-Info is
used to report
the details of
where the UE is
currently
located (e.g.
SAI or CGI).
PS 12.0/PS
12.1/PS 13.0
CC-RequestType
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0

3822
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
CC-RequestNumber
0~1
N/A
The QoSNegotiation is
applicable for
3GPP-GPRS
only. The value
of it indicates
for a single PCC
rule request if
the PCRF is
allowed to
negotiate the
QoS by
supplying in the
answer to this
request an
authorized QoS
different from
the requested
QoS.
PS 12.0/PS
12.1/PS 13.0
CCR
0~1
N/A
The QoSUpgrade is
applicable for
3GPP-GPRS
only. The value
of it indicates
whether the
SGSN supports
that the GGSN
upgrades the
QoS in a Create
PDP context
response or
Update PDP
context
response.
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
charging
characteristic
PS 12.0/PS
12.1/PS 13.0

3823
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Origin-Realm
N/A
N/A
When sent from

the PCRF to the
PCEF the
Event-Trigger
indicates an
event that shall
rules. When sent
from the PCEF
to the PCRF the
Event-Trigger
indicates that
the
corresponding
event has
occurred at the
gateway.
Whenever one
of these events
occurs, the
PCEF shall send
the related AVP
that has changed
together with
the event trigger
indication.
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0

3824
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
DestinationRealm
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
TerminationCause
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
NetworkRequestSupport
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
IP-CAN-Type
N/A
bps
it indicates the
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0
Online
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0

3825
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Offline
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

3826
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
3GPP-UserLocation-Info
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

3827
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
BearerIdentifier
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
QoSNegotiation
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

3828
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
QoS-Upgrade
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
3GPPChargingCharacteristics
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
*Event-Trigger
N/A
N/A
applicable for
3GPP-EPS
only. It defines
the QoS
information for
the EPS default
bearer.
PS 12.0/PS
12.1/PS 13.0

3829
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
QoSInformation
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

3830
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

3831
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It contains the
usage
monitoring
control
information.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

3832
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Priority-Level
N/A
It is used by the
PCRF to
indicate that
accumulated
usage is to be
reported by the
PCEF
regardless of
whether a usage
threshold is
reached
PS 12.0/PS
12.1/PS 13.0
N/A
It is used by the
PCRF to
indicate
whether usage
monitoring shall
be disabled for
certain
Monitoring Key
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
usage reporting
thresholds.
PS 12.0/PS
12.1/PS 13.0
0~0xffffffff
byte
value of the
usage reporting
thresholds
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
amount of used
units measured
from the point
when the service
became active
or, if interim
interrogations
are used during
the session,
from the point
when the
previous
measurement
ended.
PS 12.0/PS
12.1/PS 13.0

3833
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
BearerIdentifier
0~0xffffffff
byte
the amount of
used units
measured
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It report
charging rule
name or
charging rule
base name is
installed,
modified or
removed (for
dynamic PCC
rules)
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
0~2
N/A
It describes the
status of one or a
group of PCC
Rules
PS 12.0/PS
12.1/PS 13.0
Priority-Level
1~2000
N/A
indicates the
reason that the
PCC rules
cannot be
successfully
installed/
activated or
enforced.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
report, the
termination
action
instructed by the
OCS, to PCRF
when
corresponding
PCC rules is out
of credit.
PS 12.0/PS
12.1/PS 13.0
0~2
N/A
It indicates the
action to be
taken when the
user's account
cannot cover the
service cost.
PS 12.0/PS
12.1/PS 13.0

3834
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
MonitoringKey
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
CCA
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
GrantedService-Unit
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
Used-ServiceUnit
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
PCC-RuleStatus
N/A
Second
RevalidationTime
PS 12.0/PS
12.1/PS 13.0

3835
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rule-FailureCode
0~1
N/A
session online
flag
PS 12.0/PS
12.1/PS 13.0
0~1
N/A
session offline
flag
PS 12.0/PS
12.1/PS 13.0
Final-UnitAction
N/A
N/A
It can only be
sent from PCRF
to PCEF,
indicating the
PCRF selected
bearer control
mode.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
N/A
When sent from

the PCRF to the
PCEF the
Event-Trigger
indicates an
event that shall
rules. When sent
from the PCEF
to the PCRF the
Event-Trigger
indicates that
the
corresponding
event has
occurred at the
gateway.
Whenever one
of these events
occurs, the
PCEF shall send
the related AVP
that has changed
together with
the event trigger
indication.
PS 12.0/PS
12.1/PS 13.0

3836
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0
CCA
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
bps
it indicates the
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0

3837
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
DestinationRealm
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0
Result-Code
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

3838
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
RevalidationTime
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
Online
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

3839
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Offline
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
Bearer-ControlMode
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
*Event-Trigger
N/A
N/A
applicable for
3GPP-EPS
only. It defines
the QoS
information for
the EPS default
bearer.
PS 12.0/PS
12.1/PS 13.0

3840
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
*QoSInformation
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

3841
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

3842
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It contains the
usage
monitoring
control
information.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

3843
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Priority-Level
N/A
It is used by the
PCRF to
indicate that
accumulated
usage is to be
reported by the
PCEF
regardless of
whether a usage
threshold is
reached
PS 12.0/PS
12.1/PS 13.0
N/A
It is used by the
PCRF to
indicate
whether usage
monitoring shall
be disabled for
certain
Monitoring Key
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
usage reporting
thresholds.
PS 12.0/PS
12.1/PS 13.0
0~0xffffffff
byte
value of the
usage reporting
thresholds
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
amount of used
units measured
from the point
when the service
became active
or, if interim
interrogations
are used during
the session,
from the point
when the
previous
measurement
ended.
PS 12.0/PS
12.1/PS 13.0

3844
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
BearerIdentifier
0~0xffffffff
byte
the amount of
used units
measured
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
deactivate or
remove PCC
rules from an IP
CAN session.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
Priority-Level
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
activate, install
or modify PCC
rules as
instructed from
the PCRF to the
PCEF
PS 12.0/PS
12.1/PS 13.0
N/A
Second
This value
indicates the
NTP time at
which the PCC
rule has to be
enforced.
PS 12.0/PS
12.1/PS 13.0
N/A
Second
This value
indicates the
NTP time at
which the PCEF
has to stop
enforcing the
PCC rule.
PS 12.0/PS
12.1/PS 13.0
MonitoringKey
N/A
N/A
it defines the
PCC rule for a
service flow
sent by the
PCRF to the
PCEF.
PS 12.0/PS
12.1/PS 13.0

3845
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it contains the
identifier of a
service.
PS 12.0/PS
12.1/PS 13.0
GrantedService-Unit
N/A
N/A
It contains the
identifier of a
rating group
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
0~3
N/A
It describes
whether the IP
flow(s) are
enabled or
disabled.
PS 12.0/PS
12.1/PS 13.0
Used-ServiceUnit
0~1
N/A
it defines on
what level the
PCEF reports
the usage for the
related PCC
rule.
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
N/A
N/A
Online
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Offline
PS 12.0/PS
12.1/PS 13.0
0~2
N/A
it defines what
parameters shall
be metered for
offline
charging.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
N/A
Precedence
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

3846
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RuleActivationTime
N/A
N/A
determines the
traffic that
belongs to the
service flow.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
determines the
traffic that
belongs to the
service flow.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it indicates the
identity of the
packet filter.
The packet filter
identifier is
assigned by the
PCRF and
within the scope
of the PCRF is
unique per UE.
PS 12.0/PS
12.1/PS 13.0
Charging-RuleName
0~3
N/A
It indicates the
direction/
directions that a
filter is
applicable,
downlink only,
uplink only or
both down- and
uplink
(bidirectional).
PS 12.0/PS
12.1/PS 13.0
ServiceIdentifier
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0

3847
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rating-Group
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
Flow-Status
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
ReportingLevel
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
Online
N/A
bps
it indicates the
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0
Offline
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0

3848
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MeteringMethod
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

3849
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Precedence
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

3850
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MonitoringKey
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
* FlowInformation
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

3851
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
FlowDescription
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
Flow-Direction
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
QoSInformation
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0

3852
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
Priority-Level
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
BearerIdentifier
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0

3853
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
The origin-host
carried in RAR
messages
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A

RAR messages
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A

RAR messages
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

RAR messages
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
MUST be set to
the value 4,
indicating the
application.
PS 12.0/PS
12.1/PS 13.0
SPU Instance
0~0xfffffffe
N/A
The RatingGroup AVP

contains the
identifier of a
rating group
PS 12.0/PS
12.1/PS 13.0

3854
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Point
Name (APN)
0~0xfffffffe
N/A
contains the
identifier of a
service.
PS 12.0/PS
12.1/PS 13.0
RAT Type
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Delay time
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
Session-Id
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
AuthApplication-Id
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
Rating-Group
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0
ServiceIdentifier
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0

3855
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Result-Code
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
N/A
N/A
The origin-host
carried in ASR
messages
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A

ASR messages
PS 12.0/PS
12.1/PS 13.0
Slot
N/A
N/A

ASR messages
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A

ASR messages
PS 12.0/PS
12.1/PS 13.0

3856
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SPU Group
N/A
MUST be set to
the value 4,
indicating the
application.
PS 12.0/PS
12.1/PS 13.0
SPU Instance
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
RAT Type
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
Delay time
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
Session-Id
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0

3857
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
AuthApplication-Id
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
Result-Code
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Procedure-Re-Auth Messages (Gx)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
16777238
N/A
Gx application
ID
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
protocol version
PS 12.0/PS
12.1/PS 13.0
Slot
0~1
N/A
R970 dictionary
flag.
0:R940,1:R970
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
RAR
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
Access Point
Name (APN)
N/A
N/A
PS 12.0/PS
12.1/PS 13.0

3858
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RAT Type
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
1~8
N/A
The
indicate the
reason why a
session was
terminated on
the access
device.
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
Second
RevalidationTime
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
When sent from

the PCRF to the
PCEF the
Event-Trigger
indicates an
event that shall
rules. When sent
from the PCEF
to the PCRF the
Event-Trigger
indicates that
the
corresponding
event has
occurred at the
gateway.
Whenever one
of these events
occurs, the
PCEF shall send
the related AVP
that has changed
together with
the event trigger
indication.
PS 12.0/PS
12.1/PS 13.0

3859
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Delay time
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0
Session-Id
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
AuthApplication-Id
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
Protocol version
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
R970
N/A
bps
it indicates the
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0

3860
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RAR
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0
Origin-Host
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

3861
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Origin-Realm
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

3862
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
DestinationHost
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

3863
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
SessionRelease-Cause
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
RevalidationTime
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
*Event-Trigger
N/A
N/A
applicable for
3GPP-EPS
only. It defines
the QoS
information for
the EPS default
bearer.
PS 12.0/PS
12.1/PS 13.0

3864
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
*QoSInformation
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

3865
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

3866
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It contains the
usage
monitoring
control
information.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

3867
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Priority-Level
N/A
It is used by the
PCRF to
indicate that
accumulated
usage is to be
reported by the
PCEF
regardless of
whether a usage
threshold is
reached
PS 12.0/PS
12.1/PS 13.0
N/A
It is used by the
PCRF to
indicate
whether usage
monitoring shall
be disabled for
certain
Monitoring Key
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
usage reporting
thresholds.
PS 12.0/PS
12.1/PS 13.0
0~0xffffffff
byte
value of the
usage reporting
thresholds
PS 12.0/PS
12.1/PS 13.0
N/A
byte
It contains the
amount of used
units measured
from the point
when the service
became active
or, if interim
interrogations
are used during
the session,
from the point
when the
previous
measurement
ended.
PS 12.0/PS
12.1/PS 13.0

3868
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
BearerIdentifier
0~0xffffffff
byte
the amount of
used units
measured
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
deactivate or
remove PCC
rules from an IP
CAN session.
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
Priority-Level
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it is used to
activate, install
or modify PCC
rules as
instructed from
the PCRF to the
PCEF
PS 12.0/PS
12.1/PS 13.0
N/A
Second
This value
indicates the
NTP time at
which the PCC
rule has to be
enforced.
PS 12.0/PS
12.1/PS 13.0
N/A
Second
This value
indicates the
NTP time at
which the PCEF
has to stop
enforcing the
PCC rule.
PS 12.0/PS
12.1/PS 13.0
MonitoringKey
N/A
N/A
it defines the
PCC rule for a
service flow
sent by the
PCRF to the
PCEF.
PS 12.0/PS
12.1/PS 13.0

3869
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it contains the
identifier of a
service.
PS 12.0/PS
12.1/PS 13.0
GrantedService-Unit
N/A
N/A
It contains the
identifier of a
rating group
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
0~3
N/A
It describes
whether the IP
flow(s) are
enabled or
disabled.
PS 12.0/PS
12.1/PS 13.0
Used-ServiceUnit
0~1
N/A
it defines on
what level the
PCEF reports
the usage for the
related PCC
rule.
PS 12.0/PS
12.1/PS 13.0
CC-TotalOctets
0~1
N/A
Online
PS 12.0/PS
12.1/PS 13.0
0~1
N/A
Offline
PS 12.0/PS
12.1/PS 13.0
0~2
N/A
it defines what
parameters shall
be metered for
offline
charging.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
N/A
Precedence
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It is used for
usage
monitoring
control
purposes as an
identifier to a
usage
monitoring
control instance.
PS 12.0/PS
12.1/PS 13.0

3870
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RuleActivationTime
N/A
N/A
determines the
traffic that
belongs to the
service flow.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
determines the
traffic that
belongs to the
service flow.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
it indicates the
identity of the
packet filter.
The packet filter
identifier is
assigned by the
PCRF and
within the scope
of the PCRF is
unique per UE.
PS 12.0/PS
12.1/PS 13.0
Charging-RuleName
0~3
N/A
It indicates the
direction/
directions that a
filter is
applicable,
downlink only,
uplink only or
both down- and
uplink
(bidirectional).
PS 12.0/PS
12.1/PS 13.0
ServiceIdentifier
N/A
N/A
The QoSInformation
defines the QoS
information for
resources
requested by the
UE, an IP-CAN
bearer, PCC
rule, QCI or
APN.
PS 12.0/PS
12.1/PS 13.0

3871
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rating-Group
N/A
N/A
it identifies a set
of IP-CAN
specific QoS
parameters that
define the
authorized QoS,
excluding the
service flow.
PS 12.0/PS
12.1/PS 13.0
Flow-Status
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an uplink IP
flow.
PS 12.0/PS
12.1/PS 13.0
ReportingLevel
N/A
bps
it indicates the
maximum
requested
bandwidth in
bits per second
for an downlink
IP flow.
PS 12.0/PS
12.1/PS 13.0
Online
N/A
bps
it indicates the
second for an
uplink service
data flow.
PS 12.0/PS
12.1/PS 13.0
Offline
N/A
bps
it indicates the
second for an
downlink
service data
flow.
PS 12.0/PS
12.1/PS 13.0

3872
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MeteringMethod
1~15
N/A
It is used for
deciding
whether a bearer
establishment or
modification
request can be
accepted or
needs to be
rejected in case
of resource
limitations
(typically used
for admission
control of GBR
traffic). It can
also be used to
decide which
existing bearers
to pre-empt
during resource
limitations. The
priority level
defines the
relative
importance of a
resource
request.
PS 12.0/PS
12.1/PS 13.0

3873
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Precedence
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can get
resources that
were already
assigned to
another service
data flow with a
lower priority
level. If it is
provided within
AVP defines
whether the
default bearer
can get
resources that
were already
assigned to
another bearer
with a lower
priority level.
PS 12.0/PS
12.1/PS 13.0

3874
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
MonitoringKey
0~1
N/A
It is used for
3GPP-EPS
only. If it is
provided within
the QoSInformation
AVP, the AVP
defines whether
a service data
flow can lose the
resources
assigned to it in
order to admit a
service data
flow with higher
priority level. If
it is provided
within the
AVP, the AVP
defines whether
the default
bearer can lose
the resources
assigned to it in
order to admit a
pre-emption
capable bearer
with a higher
priority level.
PS 12.0/PS
12.1/PS 13.0
*FlowInformation
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
uplink direction
related with the
same APN.
PS 12.0/PS
12.1/PS 13.0

3875
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
FlowDescription
N/A
bps
It indicates the
maximum
aggregate bit
rate in bits per
seconds for the
downlink
direction across
all non-GBR
bearers related
with the same
APN.
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
indicates the
bearer to which
specific
information
refers. It is
selected solely
by the PCEF and
its encoding is
transparent to
the PCRF. It will
only be needed
in GPRS access
mode.
PS 12.0/PS
12.1/PS 13.0
Flow-Direction
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
QoSInformation
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
QoS-ClassIdentifier
N/A
N/A
RAA
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0

3876
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
Priority-Level
N/A
N/A
RAA resultcode
PS 12.0/PS
12.1/PS 13.0
N/A
Second
RevalidationTime
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
It report
charging rule
name or
charging rule
base name is
installed,
modified or
removed (for
dynamic PCC
rules)
PS 12.0/PS
12.1/PS 13.0
0~2
N/A
It describes the
status of one or a
group of PCC
Rules
PS 12.0/PS
12.1/PS 13.0
1~2000
N/A
indicates the
reason that the
PCC rules
cannot be
successfully
installed/
activated or
enforced.
PS 12.0/PS
12.1/PS 13.0
BearerIdentifier
N/A
N/A
it is used to
report, the
termination
action
instructed by the
OCS, to PCRF
when
corresponding
PCC rules is out
of credit.
PS 12.0/PS
12.1/PS 13.0

3877
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
0~2
N/A
It indicates the
action to be
taken when the
user's account
cannot cover the
service cost.
PS 12.0/PS
12.1/PS 13.0
*ChargingRule-Name
N/A
N/A
it defines a name
for PCC rule
PS 12.0/PS
12.1/PS 13.0
RAA
N/A
N/A
it indicates the
PCC rules
residing at the
PCEF.
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
User Whole
Procedure ID
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
Procedure NO.
PS 12.0/PS
12.1/PS 13.0
DestinationHost
N/A
N/A
Message
Organiger
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
N/A
Slot
PS 12.0/PS
12.1/PS 13.0
Result-Code
N/A
N/A
CPU
PS 12.0/PS
12.1/PS 13.0
RevalidationTime
N/A
N/A
SPU Group
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
SPU Instance
PS 12.0/PS
12.1/PS 13.0
PCC-RuleStatus
N/A
N/A
Access Point
Name (APN)
PS 12.0/PS
12.1/PS 13.0
Rule-FailureCode
N/A
N/A
RAT Type
PS 12.0/PS
12.1/PS 13.0
N/A
N/A
NE Time Zone
PS 12.0/PS
12.1/PS 13.0
Final-UnitAction
N/A
N/A
Anonymous
Switch
PS 12.0/PS
12.1/PS 13.0

3878
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
*ChargingRule-Name
N/A
N/A
private cause
PS 12.0/PS
12.1/PS 13.0
N/A
tick
Delay time
PS 12.0/PS
12.1/PS 13.0
Procedure-Abort-Session Message(Gx)
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
User Whole
Procedure ID
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
Procedure NO.
16777238
N/A
Gx application
ID
PS 12.0/PS
12.1/PS 13.0
Message
Organiger
N/A
N/A
protocol version
PS 12.0/PS
12.1/PS 13.0
Slot
0~1
N/A
R970 dictionary
flag.
0:R940,1:R970
PS 12.0/PS
12.1/PS 13.0
CPU
N/A
N/A
ASR
PS 12.0/PS
12.1/PS 13.0
SPU Group
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
SPU Instance
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0

3879
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Access Point
Name (APN)
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
RAT Type
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
NE Time Zone
N/A
N/A
ASA
PS 12.0/PS
12.1/PS 13.0
Anonymous
Switch
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
private cause
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
Delay time
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0
Session-Id
N/A
N/A
The Session-Id
is used to
identify a
specific session.
All messages
pertaining to a
specific session
MUST include
only one
Session-Id and
the same value
MUST be used
throughout the
life of a session.
PS 12.0/PS
12.1/PS 13.0
AuthApplication-Id
16777238
N/A
Gx application
ID
PS 12.0/PS
12.1/PS 13.0
Protocol version
N/A
N/A
protocol version
PS 12.0/PS
12.1/PS 13.0
R970
0~1
N/A
R970 dictionary
flag.
0:R940,1:R970
PS 12.0/PS
12.1/PS 13.0

3880
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
ASR
N/A
N/A
ASR
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
DestinationHosT
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
DestinationRealm
N/A
N/A
PS 12.0/PS
12.1/PS 13.0
ASA
N/A
N/A
ASA
PS 12.0/PS
12.1/PS 13.0
Origin-Host
N/A
N/A
Origin-Host
name
PS 12.0/PS
12.1/PS 13.0
Origin-Realm
N/A
N/A
Origin-Realm
name
PS 12.0/PS
12.1/PS 13.0
Result-Code
1000~5999
N/A

whether a
particular
request was
completed
successfully or
whether an error
occurred.
PS 12.0/PS
12.1/PS 13.0

(Combined Analysis)
This section describes the parameters for querying combined complaint analysis support data
results. You can refer to the description when querying combined complaint analysis support
data results.
Issue 03 (2015-07-30)

3881
Nastar
Summary
Parameter
Range
Unit
Description
RAT
Serial
Number
[1,2^31-1)
N/A

Overview Table. Serial number is
a keyword of a call record. It is an
internal identification in the
a call record.
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
Combined
N/A
N/A

The Nastar supports the
combination of inter-BSC/RNC/
PS Core CHRs. If a yellow icon is
displayed in this column, the CHR
is combined.
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
USN
+UGW
Associated
N/A
N/A
Whether a CHR is associated.
PS Core
Status
N/A
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
Blank

record is abnormal.
Issue 03 (2015-07-30)
Abnormal
Cause
N/A
Network
N/A
N/A

Remark: For the access counters
such as TP, Ec/No, RSCP, if the
active set contains multiple cells
during access, only the counters
for the first cell in this active set
are analyzed.
N/A

GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
3882
Nastar
Parameter
Range
Unit
Description
RAT
Access Net
Type
N/A
N/A

following:
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
GPRS
UMTS(W/TD)
LTE
Access
Type
Intra-RAT RRC
Access
N/A
Incoming HO/
Intra-RAT
Incoming HO

CONNECTION SETUP
message:
UMTS/
LTE

in)
Incoming HO/
UTRAN
Incoming HO

migration request.
Incoming HO/
GERAN
Incoming HO

reloc in)
Incoming HO

DRD)
DRD)
CSFB on
Access
Yes
N/A
No
UMTS/
LTE
N/A
Issue 03 (2015-07-30)

3883
Nastar
Parameter
Range
Unit
Description
RAT
Access
Cause
Originating
Conversational
Call
N/A
Cause of RRC setup.
GSM/
UMTS
Originating
Streaming Call

cause."
Originating
Interactive Call
Originating
Background Call
Originating
Subscribed traffic
Call
Terminating
Conversational
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
Terminating
High Priority
Signaling
Terminating
Low Priority
Signaling
MBMS reception
Issue 03 (2015-07-30)

3884
Nastar
Parameter
Range
Unit
Description
RAT
MBMS ptp RB
request
Start Time
N/A
N/A
Signaling start time for a call.
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
Access Cell
1 to 64 characters
N/A

terminal sends the Channel
Request message.
GSM/
UMTS/
TDSCDMA/
LTE
End Time
N/A
N/A
Signaling end time for a call.
GSM/
UMTS/
TDSCDMA/
LTE/PS
Core
Release
Cell
1 to 64 characters
N/A

terminal receives the Channel
Release message.
GSM/
UMTS/
TDSCDMA/
LTE
User
ID:User
Name
N/A
N/A

GSM/
UMTS/
TDSCDMA/
LTE
IMSI
N/A
User Name, which is created by

the user when creating the task.
N/A

IMEI-TAC
Issue 03 (2015-07-30)
00000000-99999
999
N/A

UE.

GSM/
UMTS/
TDSCDMA/
LTE
GSM/
UMTS/
TDSCDMA/
LTE
3885
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
RAT
Terminal
Model
N/A
N/A
Model of a UE.
GSM/
UMTS/
TDSCDMA/
LTE
Peer
MSISDN
N/A
N/A

peer subscriber.
GSM
Duration
[0,+)
Secon
d
Duration of a call, including

service duration and signaling
duration.
time.
GSM/
UMTS/
TDSCDMA/
LTE
N/A
Statistics on the types of CS

GSM/
UMTS
Secon
d
Statistics on the duration of CS

GSM/
UMTS

UE.
CS
Requested
Service
Type
AMR
CS Service
Duration
[0,+)
VP

3886
Nastar
Parameter
Range
Unit
Description
RAT
Call Setup
Result/RRC
Setup
Failure
Cause
Following are
criteria indicating
a proper call
setup:
N/A

indicates a proper call setup or an
abnormal call setup.
GSM/
UMTS
1. Normal: The
called subscriber
receives the
Connect ACK
message and
proper call
communication is
established
between the
calling and called
subscribers.
The call setup result is displayed

in the following format: Call
Abnormal Call Release/SubCause of Abnormal Call Release.
(You can obtain the preceding
three parameters in the Call
Release Information window.)
2. The calling
subscriber
receives the
Disconnect
message and
termination of the
call is triggered
by the peer
subscriber.
3. Connection is
released due to an
outgoing interBSC 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.
Issue 03 (2015-07-30)

3887
Nastar
Parameter
Range
Unit
Description
RAT
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.
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.
Issue 03 (2015-07-30)

3888
Nastar
Parameter
Range
Unit
Description
RAT
Call Setup
Result
Following are
criteria indicating
a proper call
release:
N/A

indicates a proper call release or
an abnormal call release.
GSM
1. Normal: The
subscriber
receives the
Disconnect
message and
starts 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 interRAT 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 03 (2015-07-30)

3889
Nastar
Parameter
Range
Unit
Description
RAT
PS
Requested
Service
Type
PS R99
N/A
Statistics on the types of PS

UMTS
HSDPA
HSUPA
HSPA
PS RAB
Duration
[0,+)
Secon
d
Statistics on the duration of PS

UMTS
IU Release
Cause
N/A
N/A
Cause of signaling release of a

call.
UMTS
The value of this parameter is

carried in the IU RELEASE
REQUEST message. For details,
see 3GPP 25.413 - 9.1.6.
NE Type
N/A
N/A

following:
PS Core
SGSN
MME
NE Name
N/A
N/A
Name of a CN NE.
PS Core
Procedure
Type
N/A
N/A
PS Core
RAC/TAC
N/A

Signaling Procedures in the
appendix.
N/A

initiated.
PS Core

initiated.
Cell
N/A
N/A

accesses.
PS Core
APN
N/A
N/A

the SM procedure.
PS Core

MM procedure.
Procedure
Delay Time
0-65535
ms
PS Core
The parameters for the LTE-FDD/TDD signaling plane data and PS Core user plane combined
complaint analysis based on UGW are similar to those for the PS Core user plane complaint
Issue 03 (2015-07-30)

3890
Nastar
analysis based on UGW.For details,see Reference for Complaint Analysis Support

Parameters (PS Core) - User Plane.
5.11.10 Appendix: Exception Cause Classification / Key Signaling

Appendix: Exception Cause Classification / Key Signaling (GSM)


Doma
in
Servic
e Type
RANNET
Networ
k
Evalu
ation
Type
Access
ibility
Evalua
tion
Abnormal Type
Access Failure
(Intra-System)
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Abnormal TA on
Access
N/A
N/A
Abnormal RACH
Level on Access
N/A
N/A
Abnormal Release
(Intra-system)
Handover Failure
N/A
Problem
High TA
Access Failure
(Inter-System)
Retain
ability
Evalua
tion
Issue 03 (2015-07-30)
Abnormal Sub-type

3891
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Weak
TCH
Uplink/
Downlink
Level
TCH
Uplink/
Downlink
Interferen
ce
Poor
uplink
quality of
the TCH
Weak
TCH
Uplink
Level
Weak
TCH
Downlink
Level
TCH
Uplink
Interferen
ce
TCH
Downlink
Interferen
ce
Poor TCH
Uplink
Quality
Poor TCH
Downlink
Quality
Sharp
Decrease
on TCH
Uplink
Level
Issue 03 (2015-07-30)

3892
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Sharp
Decrease
on TCH
Downlink
Level
Other Um
Interface
Quality
Problems
Retain
ability
Evalua
tion
Abnormal Release
(Inter-system)
Transmission Fault
N/A
CN fault
N/A
Peer Fault
N/A
Other Causes
N/A
Handover Failure
N/A
Problem
High TA
Weak
TCH
Uplink/
Downlink
Level
TCH
Uplink/
Downlink
Interferen
ce
Poor
uplink
quality of
the TCH
Weak
TCH
Uplink
Level
Weak
TCH
Downlink
Level
Issue 03 (2015-07-30)

3893
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
TCH
Uplink
Interferen
ce
TCH
Downlink
Interferen
ce
Poor TCH
Uplink
Quality
Poor TCH
Downlink
Quality
Sharp
Decrease
on TCH
Uplink
Level
Sharp
Decrease
on TCH
Downlink
Level
Other Um
Interface
Quality
Problems
Mobilit
y
Evalua
tion
Issue 03 (2015-07-30)
Hard Handover
Failure
Transmission Fault
N/A
CN fault
N/A
Peer Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A

3894
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Inter-System
Outgoing Handover
Failure (Normal
Release)
Inter-System
Outgoing Handover
Failure (Abnormal
Release)
Inter-System
Incoming Handover
Failure
RANCS
Issue 03 (2015-07-30)
Call
Access
ibility
Evalua
tion
Call Setup Failure
Abnormal Sub-type
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A

3895
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Release
Before Call
Completion
Retain
ability
Evalua
tion
Abnormal Call
Release
Abnormal Sub-type
Problem/MS Fault
N/A
System Resource
Congestion
N/A
Transmission Fault
N/A
CN Fault
N/A
Other Causes
N/A
Handover Failure
N/A
Problem
High TA
Weak
TCH
Uplink/
Downlink
Level
TCH
Uplink/
Downlink
Interferen
ce
Poor
uplink
quality of
the TCH
Weak
TCH
Uplink
Level
Weak
TCH
Downlink
Level
TCH
Uplink
Interferen
ce
Issue 03 (2015-07-30)

3896
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
TCH
Downlink
Interferen
ce
Poor TCH
Uplink
Quality
Poor TCH
Downlink
Quality
Sharp
Decrease
on TCH
Uplink
Level
Sharp
Decrease
on TCH
Downlink
Level
Other Um
Interface
Quality
Problems
Service
Quality
- Delay
Evalua
tion
Issue 03 (2015-07-30)
Abnormal Delay
Transmission Fault
N/A
CN fault
N/A
Peer Fault
N/A
Other Causes
N/A

(MOC)
N/A

(MTC)
N/A
Overlong Call
Completion Delay
(Alerting)(MOC)
N/A
Overlong Call
Completion Delay
(Alerting)(MTC)
N/A

3897
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Service
Quality
Quality
Evalua
tion
SMS
RANPS
Issue 03 (2015-07-30)
PS
Abnormal Type
Service Quality
Problem
Abnormal Sub-type
Overlong Call
Completion Delay
(Connect Ack)(MOC)
N/A
Overlong Call
Completion Delay
(Connect Ack)(MTC)
N/A
Short Call(MOC)
N/A
Short Call(MTC)
N/A
Poor Quality of Um
Interface
N/A
Bad Downlink HQI
N/A
Bad Uplink HQI
N/A
Bad Uplink VQI
N/A
Bad Downlink VQI
N/A
Uplink One-Way Audio
N/A
Downlink One-Way
Audio
N/A
Mute Call
N/A
Downlink Crosstalk
N/A
Uplink Crosstalk
N/A
Downlink Noise
N/A
Uplink Noise
N/A
Access
ibility
Evalua
tion
Setup Failure(Caller) N/A
N/A
Setup Failure
(Callee)
N/A
N/A
Access
ibility
Evalua
tion
Setup Failure
Attach Failure
Attach
Reject
Failure

Attach
Failure No
Responses
3898
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
PDP Active Failure
PDP
Active
Reject
Failure
PDP
Active
Failure No
Responses
AUC Failure
AUC
Reject
Failure
AUC
Failure No
Responses
Retain
ability
Evalua
tion
Delay
Evalua
tion
Service Interrupt
Abnormal Service
Interaction Delay
No Service Interaction
Responses
N/A
Last Service
Interruptions Due to
Routing Area Update
N/A
Abnormal Interruption
on Cell Reselection
N/A
Due to FLUSH LL
N/A
Due to TBF Abnormal
N/A
Service Interaction
Timeout
Service
Interaction
Timeout
on interval
between
Uplink
and
Downlink
PDUs
Service
Interaction
Timeout
on sending
PDUs at
Downlink
Issue 03 (2015-07-30)

3899
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Service
Interaction
Timeout
on
receiving
PDUs at
Uplink
Rate
Evalua
tion
Low Download
Speed
Overlong Average
Duration on Service
Interaction Response
N/A
Low Download Speed
Downlink
Multi-Slot
NonSatisfactio
n
Downlink
Reuse to
High
Um
Quality
NonSatisfactio
n of
Downlink
Average
SingleSlot
Throughp
ut
Poor
Transmiss
ion
Quality of
Downlink
Average
SingleSlot
Throughp
ut
Issue 03 (2015-07-30)

3900
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Transmiss
ion
Resource
NonSatisfactio
n of
Downlink
Average
SingleSlot
Throughp
ut
Downlink
TCP Outof-Order
Downlink
NU Outof-Order
Insufficien
t Terminal
Capability
Abnormal
Subscriber
Registrati
on
Other
Low Upload Speed
Low Upload Speed
Uplink
Multi-Slot
NonSatisfactio
n
Uplink
Reuse to
High
Issue 03 (2015-07-30)

3901
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Um
Quality
NonSatisfactio
n of
Uplink
Average
SingleSlot
Throughp
ut
Poor
Transmiss
ion
Quality of
Uplink
Average
SingleSlot
Throughp
ut
Transmiss
ion
Resource
NonSatisfactio
n of
Uplink
Average
SingleSlot
Throughp
ut
Uplink
TCP Outof-Order
Uplink
NU Outof-Order
Insufficien
t Terminal
Capability
Issue 03 (2015-07-30)

3902
Nastar
Doma
in
Servic
e Type
Evalu
ation
Type
Abnormal Type
Abnormal Sub-type
Abnormal
Subscriber
Registrati
on
Other
TBF
Abnor
mal
TBF Abnormal
TBF Abnormal
Um
Quality
Cause
Um
Resource
Cause
Cell
Reselectio
n Cause
Voice
Cause
Equipmen
t Cause
Terminal
Cause
Other
Nonexecpti
on
Non-exception
N/A
N/A
Key Signaling (PS Domain)

Interface
Key Signaling
RA CAPABILITY UPDATE
RADIO STATUS
Gb
DOWNLOAD BSS PFC

CREATE BSS PFC ACK
CREATE BSS PFC NACK
MODIFY BSS PFC
Issue 03 (2015-07-30)

3903
Nastar
Interface
Key Signaling
DELETE BSS PFC ACK
PS HANDOVER REQUIRED
PS HANDOVER REQUEST ACK
PS HANDOVER REQUEST NACK
PS HANDOVER COMPLETE
PS HANDOVER CANCEL
SUSPEND
RESUME
FLUSH-LL-ACK
LLC DISCARDED
RA CAPABILITY UPDATE ACK
CREATE BSS PFC
MODIFY BSS PFC ACK
DELETE BSS PFC
PS HANDOVER REQUEST
PS HANDOVER REQUIRED ACK
PS HANDOVER REQUIRED NACK
SUSPEND-ACK
SUSPEND-NACK
RESUME-ACK
RESUME-NACK
FLUSH-LL
ATTACH REQUEST
ATTACH ACCEPT
ATTACH REJECT
ATTACH COMPLETE
DETACH REQUEST
DETACH ACCEPT
ROUTING AREA UPDATE REQUEST
Issue 03 (2015-07-30)

3904
Nastar
Interface
Key Signaling
ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE REJECT
ROUTING AREA UPDATE COMPLETE
AUTHENTICATION AND CIPHERING REJECT
AUTHENTICATION AND CIPHERING REQUEST
AUTHENTICATION AND CIPHERING RESPONSE
AUTHENTICATION AND CIPHERING FAILURE
IDENTITY REQUEST
IDENTITY RESPONSE
PTMSI REALLOCATION COMMAND
PTMSI REALLOCATION COMPLETE
GMM STATUS
GMM INFORMATION
ACTIVATE PDP CONTEXT REQUEST
ACTIVATE-PDP-CONTEXT-REQUEST
ACTIVATE PDP CONTEXT ACCEPT
ACTIVATE PDP CONTEXT REJECT
ACTIVATE SECONDARY PDP CONTEXT REQUEST
ACTIVATE SECONDARY PDP CONTEXT ACCEPT
ACTIVATE SECONDARY PDP CONTEXT REJECT
REQUEST PDP CONTEXT ACTIVATION
REQUEST PDP CONTEXT ACTIVATION REJECT
MODIFY PDP CONTEXT REQUEST(MS To NET)
MODIFY PDP CONTEXT ACCEPT(MS To NET)
MODIFY PDP CONTEXT REQUEST(NET To MS)
MODIFY PDP CONTEXT ACCEPT(NET To MS)
MODIFY PDP CONTEXT REJECT
DEACTIVATE PDP CONTEXT REQUEST
DEACTIVATE PDP CONTEXT ACCEPT
Issue 03 (2015-07-30)

3905
Nastar
Interface
Key Signaling
SM-STATUS
Channel Request
Packet Channel Req
Packet Control Acknowledgement (NB) Packet Control Ack
(AB)
Packet Cell Change Failure
Packet Resource Request
Packet SI Status
Additional MS Radio Access Capabilities
Packet Cell Change Notification
Packet Downlink Ack/Nack
EGPRS Packet Downlink Ack/Nack
EGPRS Packet Downlink Ack/Nack Type 2
Immediate Assignment
Immediate Assignment Reject
Um
Packet Downlink Assignment

Packet Polling Request
Packet Power Control/Timing Advance
Packet Timeslot Reconfigure
Packet TBF Release
Packet Uplink Assignment
Packet Cell Change Continue
Packet Neighbor Cell Data
Packet Serving Cell Data
Packet Cell Change Order
Packet Measurement Order
Packet Physical Information
PS Handover Command
Packet Uplink Ack/Nack
Uplink RLC Data header
Issue 03 (2015-07-30)

3906
Nastar
Interface
Key Signaling
Downlink RLC Data header
Appendix: Exception Cause Classification / Enumeration Values of Failure Cause

(UMTS)
The section describes the exception cause classification in the summary table, and the
enumeration values of the failure cause.

Domain
RAN-Net
Servi
ce
Type
Netwo
rk
Non-exception
N/A
Setup Failure
RRC Setup Failure

RRC Setup Failure (Service-CS)
RRC Setup Failure (Service-PS)
Access Coverage
Problem
Abnormal TP on access
Abnormal CPICH Ec/N0 on access
Abnormal CPICH RSCP on access
Abnormal Release
RRC Abnormal Release
Delay Problem
Overlong RRC Setup Delay (Non-service)

Overlong RRC Setup Delay (Service)
Overlong Soft Handover Delay
Overlong Hard Handover Delay
Overlong Channel Handover Delay
Overlong Incoming Handover Delay
Overlong Outgoing Handover Delay
Overlong Inter-RAT Incoming Handover
Delay
Overlong Inter-RAT Outgoing Handover
Delay
.Overlong U2L redirection delay threshold
HO Problem
Issue 03 (2015-07-30)
Soft Handover Failure

3907
Nastar
Domain
Servi
ce
Type
Cell Update Failure
Channel Handover Failure
Migration Failure
Inter-RAT Handover Failure
PDP Activate Failure
RAN-CS
AMR
Non-exception
N/A
Setup Failure

Abnormal Release
Uplink One-Way-Audio
Downlink One-Way-Audio
Noise
SQI Abnormal
Radio of Bad SQIs Higher
Delay Problem

(Alerting)(MTC)
Ack)(MTC)
(Alerting)(MOC)
Ack)(MOC)
ShortCall Problem

Short Calls (MTC)
Short Calls (MOC)
VP
Issue 03 (2015-07-30)
Non-exception
N/A

3908
Nastar
Domain
Servi
ce
Type
Setup Failure

Abnormal Release
Delay Problem

(Alerting)(MTC)
Ack)(MTC)
(Alerting)(MOC)
Ack)(MOC)
ShortCall Problem

Short Calls (MTC)
Short Calls (MOC)
SMS
Non-exception
N/A
Setup Failure
SMS Failed Requests (MTC)

SMS Failed Requests (MOC)
RAN-PS
Other
Other
N/A
PS
R99
Non-exception
N/A
Setup Failure
PS RAB Setup Failure
Abnormal Release
PS RAB Abnormal Release
QoS Problem
Overlow Average Downlink Throughput
HSDP
A
HSUP
A
Overlow Average Uplink Throughput
HSPA
Average Uplink Transmission Rate Slow

Delay Problem

Issue 03 (2015-07-30)

3909
Nastar
Domain
RANMulti
Servi
ce
Type
Other
Other
N/A
Multi
Servic
e
Non-exception
N/A
Setup Failure
Multi-RAB Setup Failure
Multi
Servic
e(CS
Includ
ed)
Abnormal Release
Multi-RAB Abnormal Release
Multi
Servic
e(PS
Only)
Enumeration Values of Failure Cause
Issue 03 (2015-07-30)
ErrType
ErrReason
UL Power Congestion
DL Power Congestion
Code Congestion
HSUPA User Num Congestion
HSDPA User Num Congestion
HSUPA_HSDPA User Num Congestion
UL_DL Power Congestion
UL CE Congestion
DL CE Congestion
UL_DL CE Congestion
UL Iub Band Congestion
DL Iub Band Congestion
UL_DL Iub Band Congestion
Overload Control
Preempted User Due To Congestion
Iub AAL2/AL Establishment Failure

3910
Nastar
Issue 03 (2015-07-30)
ErrType
ErrReason
Iur AAL2/AL Establishment Failure
SRB Reset
TRB Reset
Iu Relocation Preparation Failure Timer

Relocation Preparation Expiry
Iu Relocation Execution Timer Expiry
Timer Expired
Iu Relocation Preparation Iu Release

Command
Iu Relocation Preparation Failure Unknown

Target RNC
Iu Relocation Preparation Failure Cancel
Iu Relocation Preparation Failure Cipher

Unsupport

Not Allow

System Unsupport
Iub Cell not Available
Iub Control Plane Process Resources

Overload
Iub Hardware Failure
Iub OAM Intervention Failure
Iub not Enough User Plane Process

Resources Failure
Radio Link Permanent Failure
Iur RL Reconfiguration Commit Timeout
Iur Radio Link Reconfiguration Cancel
Iur RL Add/Setup Timeout
Iur Control Plane Process Resources

Overload
UE Reestablishment
Overlapped Cell Update

3911
Nastar
ErrType
ErrReason
Uu Configuration Unsupport
Uu Physical Channel Failure
Uu Simultaneous Configuration
Uu Compress Mode Runtime Tgpsi Error
Uu Protocol Error
Uu Cell Update Occur Error
Uu Invalid Configuration
Uu Configuration Incomplete
Uu Unsupport Measurement Error
Uu MBMS Session Failure
Uu MBMS Service Failure
Uu Inter-RAT HO Failure Configuration

Unaccept
Uu Inter-RAT HO Failure Physical CH

Failure
Uu Inter-RAT HO Failure Protocol Error
Uu Inter-RAT HO Failure Inter-RAT

Protocol Error
Uu Inter-RAT HO Failure Unspecified
Uu Inter-RAT Change Failure
Uu Inter-RAT Change Failure Protocol

Error
Uu Inter-RAT Change Failure Unspecified
Appendix: Exception Cause Classification / Key Signaling (LTE)

lists the key signaling.
Issue 03 (2015-07-30)

3912
Nastar

Service
Type
Evaluati
on Type
Net
Accessibil
ity
Evaluatio
n
Abnormal
CauseClassificati
on
Setup Failure

(Service)
RRC Setup Failure (UE No-answer) (Service)
(Non-service)
RRC Setup Failure (UE No-answer) (Nonservice)
RRC Re-setup Failure
Mobility
Evaluatio
n
HO Failure

failure
failure
preparation failure
failure
Issue 03 (2015-07-30)

3913
Nastar
Service
Type
Evaluati
on Type
Abnormal
CauseClassificati
on

preparation failure (with Data Transmission)
Intra-RAT incoming handover preparation failure
Intra-RAT incoming handover execution failure
Inter-RAT incoming handover preparation failure
Inter-RAT incoming handover execution failure
Delay
Evaluatio
n
Delay
Problem
Overlong RRC setup delay (Service)

Overlong RRC setup delay (Non-service)
Overlong intra-RAT outgoing handover delay
Overlong inter-RAT outgoing handover delay
Overlong intra-RAT incoming handover delay
Overlong inter-RAT incoming handover delay
GBR
(QCI=2)
GBR
(QCI=3)
GBR
(QCI=4)
Non-GBR
(QCI=5)
Non-GBR
(QCI=6)
Non-GBR
(QCI=7)
Non-GBR
(QCI=8)
Non-GBR
(QCI=9)
Note: data
service
Accessibil
ity
Evaluatio
n
Setup Failure
E-RAB Setup Failure (QCI=N) Note: N indicates

Retainabil
ity
Evaluatio
n
E-RAB
Abnormal
Release

value.
value.
HO execution failure (QCI=N) Note: N indicates
Data Transmission)(QCI=N) Note: N indicates
(with Data Transmission)(QCI=N) Note: N
Issue 03 (2015-07-30)

3914
Nastar
Service
Type
Evaluati
on Type
Abnormal
CauseClassificati
on

value.
GBR
(QCI=1)
Note:
voice
service
Service
Evaluatio
n for
Delay
Delay
Problem
Long E-RAB Setup Delay (QCI=N) Note: N

Service
Evaluatio
n for Rate
Rate Problem
Accessibil
ity
Evaluatio
n
Setup Failure
E-RAB Setup Failure (QCI=1)
Retainabil
ity
Evaluatio
n
E-RAB
Abnormal
Release

(QCI=1)
Short E-RAB Duration (QCI=N) Note: N

Low Average Downlink Throughput (QCI=N)
Note: N indicates the detailed QCI value.
Low Average Uplink Throughput (QCI=N) Note:
N indicates the detailed QCI value.

(QCI=1)
HO execution failure (QCI=1)
Data Transmission)(QCI=1)
(with Data Transmission)(QCI=1)
(QCI=1)
Issue 03 (2015-07-30)
Service
Evaluatio
n for
Delay
Delay
Problem
Long E-RAB Setup Delay (QCI=1)
Service
Evaluatio
n for
Voice
Quality
Problem
Poor Downlink VQI
Short E-RAB Duration (QCI=1)

3915
Nastar
Service
Type
Evaluati
on Type
Abnormal
CauseClassificati
on
Voice
Quality
Service
Evaluatio
n for Rate
Poor Uplink VQI
Rate Problem
Low Average Downlink Throughput (QCI=1)

Low Average Uplink Throughput (QCI=1)
Key Signaling
Procedure
Key Event
RRC Setup or Release
RRC CONNECTION REESTABLISHMENT REQUEST

RRC CONNECTION REJECT
RRC CONNECTION SETUP COMPLETE
RRC CONNECTION RELEASE
E-RAB Setup or Release
E-RAB SETUP REQUEST

E-RAB SETUP RESPONSE
E-RAB RELEASE INDICATION
E-RAB RELEASE COMMAND
E-RAB MODIFY REQUEST
E-RAB MODIFY RESPONSE
E-RAB RELEASE RESPONSE
Context Setup or Release
INITIAL CONTEXT SETUP REQUEST

INITIAL CONTEXT SETUP RESPONSE
INITIAL CONTEXT SETUP FAILURE
UE CONTEXT RELEASE REQUEST
UE CONTEXT RELEASE COMMAND
UE CONTEXT MODIFICATION FAILURE
UE CONTEXT MODIFICATION RESPONSE
Issue 03 (2015-07-30)

3916
Nastar
Procedure
Key Event
UE CONTEXT MODIFICATION REQUEST
Handover
HANDOVER REQUIRED
HANDOVER REQUEST
HANDOVER COMMAND
HANDOVER FAILURE
HANDOVER CANCEL
HANDOVER NOTIFY
HANDOVER PREPARATION FAILURE
MOBILITY FROM EUTRA COMMAND
X2 HANDOVER REQUEST
X2 HANDOVER PREPARATION FAILURE
X2 HANDOVER CANCEL
PATH SWITCH REQUEST
PATH SWITCH REQUEST FAILURE
S1 HANDOVER REQUEST ACKNOWLEDGE
S1 PATH SWITCH REQUEST ACKNOWLEDGE
CELL TRAFFIC TRACE
X2 HANDOVER REQUEST ACKNOWLEDGE
X2 SN STATUS TRANSFER
Other
UE CAPABILITY INFORMATION
INITIAL UE MESSAGE
MEASUREMENT REPORT
UPLINK NAS TRANSPORT
NAS NON DELIVERY INDICATION
Appendix: Exception Cause Classification / Signaling Procedure / Procedure

Initiated Cause (PS Core)
lists the signaling procedure and the cause of procedure initiated.
l
Issue 03 (2015-07-30)

3917
Nastar
Signaling Procedure

NOTE
For detailed description of the exception cause field, see PS Core Knowledge Base Management.

Procedure
Type
Abnormal
Type
Abnormal
Sub-type
Non-exception
Non-exception
N/A
Abnormal
Attach
Attach Failure
Abnormal
Paging
Paging Failure
Abnormal
PDP Act
PDP Act Failure
Abnormal
PDP Sec Act
PDP Sec Act Failure
Abnormal
PDN GW
Dedicated
Bearer Act

Failure
Abnormal
RAU
Accessibility
Exception
SGSN(G)
Procedure

Overlong Delay

Mobility
Exception
Issue 03 (2015-07-30)
RAU(others) Failure
Abnormal
Relocation
Relocation Failure
Abnormal
System
Change

3918
Nastar
Procedure
Type
Abnormal
Type
PDP
Modification
Exception
Retainability
Exception
Non-exception
SGSN(U)
Procedure
Accessibility
Exception
Mobility
Exception
Issue 03 (2015-07-30)
Abnormal
Sub-type
Abnormal
PDP Mod
PDP Mod Failure
Abnormal
PDN GW
Initiated
Bearer Mod
Abnormal
Detach
Detach Failure
Abnormal
PDP Deact
PDP Deact Failure
Abnormal
PDN GW
Initiated
Bearer Deact

Failure
Non-exception
N/A
Abnormal
Attach
Attach Failure
Abnormal
Service Req
Service Req Failure
Abnormal
Paging
Paging Failure
Abnormal
PDP Act
PDP Act Failure
Abnormal
PDP Sec Act
PDP Sec Act Failure
Abnormal
RAB
Assignment
RAB Assignment Failure
Abnormal
PDN GW
Dedicated
Bearer Act

Failure
Abnormal
RAU

Overlong Delay
RAB Assignment Overlong Delay

Overlong Delay

3919
Nastar
Procedure
Type
Abnormal
Type
Abnormal
Sub-type

RAU(others) Failure
Abnormal
Relocation
Relocation Failure
Abnormal
System
Change
Abnormal
PDP Mod
PDP Mod Failure
Abnormal
PDN GW
Initiated
Bearer Mod
Abnormal
Detach
Detach Failure
Abnormal Iu
Release
Iu Release Failure
Abnormal
RAB Release
RAB Release Failure
Abnormal
PDP Deact
PDP Deact Failure
Abnormal
PDN GW
Initiated
Bearer Deact

Failure
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Attach
Attach Failure
Abnormal
Service Req
Service Req Failure
Abnormal
Default Bearer
Act
Default Bearer Act Failure
PDP
Modification
Exception
Retainability
Exception
MME
Procedure
Issue 03 (2015-07-30)

Overlong Delay
Default Bearer Act Overlong Delay

3920
Nastar
Procedure
Type
Abnormal
Type
Retainability
Exception
Mobility
Exception
Abnormal
Sub-type
Abnormal
Paging
Paging Failure
Abnormal
Dedicated
Bearer Act
Dedicated Bearer Act Failure
Abnormal
PDN
Connectivity
PDN Connectivity Failure
Abnormal
Detach
Detach Failure
Abnormal S1
Release
S1 Release Failure
Abnormal
Bearer Deact
Abnormal Bearer Deact
Abnormal
PDN
Disconnection
PDN Disconnection Failure
Abnormal
TAU
Intra TAU Failure
Dedicated Bearer Act Overlong Delay
PDN Connectivity Overlong Delay
Intra TAU Overlong Delay

Inter TAU Failure
Inter TAU Overlong Delay
Abnormal
Handover
Intra E-UTRAN Handover Failure

Intra E-UTRAN Handover Overlong
Delay
Inter RAT Handover Failure
Inter RAT Handover Overlong Delay
Bearer
Modification
Exception
Issue 03 (2015-07-30)
Abnormal
Bearer Mod
Bearer Mod Failure
Abnormal
Bearer
Resource Mod
Abnormal Bearer Resource Mod
Abnormal
Bearer
Resource
Allocation
Abnormal Bearer Resource Allocation
Bearer Mod Overlong Delay
Bearer Resource Mod Overlong Delay
Bearer Resource Allocation Overlong

Delay

3921
Nastar
Procedure
Type
GGSN(G)
Procedure
Abnormal
Type
Abnormal
Sub-type
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Create PDP
Abnormal Create PDP
PDP
Modification
Exception
Abnormal
Update PDP
Abnormal Update PDP
Retainability
Exception
Abnormal
Delete PDP
Abnormal Delete PDP
Radius
Abnormal
Authentication
access
Abnormal
Radius
Accounting
Abnormal
Disconnect
Abnormal Disconnect
Abnormal
Credit-Control
Messages
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Messages
Abnormal
Credit-Control
Messages
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Message
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Create PDP
Abnormal Create PDP
Gy
Gx
GGSN(U)
Procedure
Issue 03 (2015-07-30)

3922
Nastar
Procedure
Type
Abnormal
Type
Abnormal
Update PDP
Abnormal Update PDP
Retainability
Exception
Abnormal
Delete PDP
Abnormal Delete PDP
Radius
Abnormal
Authentication
access
Abnormal
Radius
Accounting
Abnormal
Disconnect
Abnormal Disconnect
Abnormal
Credit-Control
Messages
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Messages
Abnormal
Credit-Control
Messages
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Message
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Create Session
Abnormal
Create Bearer
Gx
Issue 03 (2015-07-30)
PDP
Modification
Exception
Gy
SAE-GW
Procedure
Abnormal
Sub-type

3923
Nastar
Procedure
Type
Abnormal
Type
Bearer
Modification
Exception
Retainability
Exception
Radius
Issue 03 (2015-07-30)
Abnormal
Sub-type
Abnormal
Create Indirect
Data
Forwarding
Tunnel

Forwarding Tunnel
Abnormal
Modify Bearer
Abnormal
Update Bearer
Abnormal
Modify Bearer
Command
Abnormal
Bearer
Resource
Command
Abnormal
Delete Session
Abnormal
Delete Bearer
Abnormal
Release
Access
Bearers
Abnormal
Delete Bearer
Command
Abnormal
Delete Indirect
Data
Forwarding
Tunnel

Forwarding Tunnel
Abnormal
Authentication
access
Abnormal
Radius
Accounting
Abnormal
Disconnect
Abnormal Disconnect

3924
Nastar
Procedure
Type
Abnormal
Type
Gy
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Messages
Abnormal
Credit-Control
Messages
Abnormal ReAuth
Messages
Abnormal
Abort-Session
Message
N/A
N/A
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Create PDP
Abnormal Create PDP
Accessibility
Exception
Abnormal
Create Session
Abnormal
Create Bearer
Abnormal
Create Indirect
Data
Forwarding
Tunnel

Forwarding Tunnel
PDP
Modification
Exception
Abnormal
Update PDP
Abnormal Update PDP
Retainability
Exception
Abnormal
Delete PDP
Abnormal Delete PDP
Traffic
Other
Procedure
Issue 03 (2015-07-30)
Abnormal
Credit-Control
Messages
Gx
Traffic
Procedure
Abnormal
Sub-type

3925
Nastar
Procedure
Type
Abnormal
Type
Retainability
Exception
Bearer
Modification
Exception
Abnormal
Sub-type
Abnormal
Delete Session
Abnormal
Delete Bearer
Abnormal
Release
Access
Bearers
Abnormal
Delete Bearer
Command
Abnormal
Delete Indirect
Data
Forwarding
Tunnel

Forwarding Tunnel
Abnormal
Modify Bearer
Abnormal
Update Bearer
Abnormal
Modify Bearer
Command
Abnormal
Bearer
Resource
Command

Procedure
Type
MME
Procedure
Issue 03 (2015-07-30)
Abnormal
Type
Abnormal
Sub-type
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal
Attach
Combined Attach CS Failure
Abnormal
Paging
SGs CS Paging Failure
Combined Attach CS Overlong Delay
SGs CS Paging Overlong Delay

3926
Nastar
Procedure
Type
Abnormal
Type
Abnormal
Sub-type

SGs SMS Paging Failure
SGs SMS Paging Overlong Dela
S1 CS Paging Failure
S1 CS Paging Overlong Delay
S1 SMS Paging Failure
S1 SMS Paging Overlong Delay
Mobility
Exception
Abnormal
Service Req
Extended Service Req Failure
Abnormal
TAU
Intra Combined TAU Failure
Extended Service Req Overlong Delay
Intra Combined TAU Overlong Delay

Inter Combined TAU Failure
Inter Combined TAU Overlong Delay
Abnormal
Handover
CSFB PS Handover Failure

CSFB PS Handover Overlong Delay

Procedure Type
Abnormal Type
Abnormal Subtype
Detailed
Abnormal Type
MME Procedure
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal UE
requested PDN
connectivity
VoLTE PDN
Connectivity Failure
Abnormal Paging
VoLTE Paging
Failure
VoLTE PDN
Connectivity
Overlong Delay
VoLTE Paging
Overlong Delay
Abnormal Dedicated
Bearer Act
Issue 03 (2015-07-30)

VoLTE Dedicated
Bearer Act Failure
3927
Nastar
Procedure Type
Abnormal Type
Abnormal Subtype
Detailed
Abnormal Type
VoLTE Dedicated
Bearer Act Overlong
Delay
Abnormal Bearer
Mod
VoLTE Bearer Mod

Failure
VoLTE Bearer Mod
Overlong Delay
Mobility Exception
Abnormal Handover

Failure
Overlong Delay
SRVCC Failure
SRVCC Overlong
Delay
SAE-GW Procedure
Retainability
Exception
Call Drop
VoLTE Call Drop
Non-exception
Non-exception
N/A
Accessibility
Exception
Abnormal VoLTE
Create Session
N/A
Abnormal VoLTE
Create Bearer
N/A
Abnormal VoLTE
Update Bearer
N/A

Service
Web
Browsin
g
Issue 03 (2015-07-30)
Assess
ment
Type
Demarcation
Type
Accessib
ility
Page Response
Failure

4**
Terminal Problem

5**
SP Problem

Demarcation
Result
3928
Nastar
Service
Assess
ment
Type
Demarcation
Type
Abnormal Page
Response Delay
Integrity
Issue 03 (2015-07-30)
Slow Page
Response
Demarcation
Result
Redirect Failure (Terminal

Problem)
Terminal Problem

(RAN Problem)
RAN problem/
Problem on NEs
below PS core
SP Problem
Problem on NEs
above PS core
Others
Others
DNS Abnormal Delay
Problem on NEs
above PS core

SYN and SYN ACK
Problem on NEs
above PS core

SYN ACK and ACK
RAN problem/
Problem on NEs
below PS core

ACK and GET/POST
RAN problem/
Problem on NEs
below PS core

Problem on NEs
above PS core
Others
Others

Window
Terminal Problem

Window
Terminal Problem

Loss Rate
RAN problem/
Problem on NEs
below PS core
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core

Rate
Problem on NEs
above PS core
High Uplink
Retransmission Rate
RAN Problem

3929
Nastar
Service
Video
Streamin
g
Issue 03 (2015-07-30)
Assess
ment
Type
Accessib
ility
Demarcation
Type
Demarcation
Result
Low Upstream
Problem on NEs
above PS core
Others
Others
Slow Page
Display
Low Success Rate of Page

Display Request
NA
Video Streaming
Start Failure

Window
Terminal Problem

Window
Terminal Problem

SYN and SYN ACK
Problem on NEs
above PS core

ACK and GET
RAN problem/
Problem on NEs
below PS core

SYN ACK and ACK
RAN problem/
Problem on NEs
below PS core
DNS Abnormal Delay
Problem on NEs
above PS core

GET and Response
Problem on NEs
above PS core
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core

Loss Rate
RAN problem/
Problem on NEs
below PS core

Rate
Problem on NEs
above PS core

Period
RAN problem/
Problem on NEs
below PS core
High Code Rate
SP Problem
Low Upstream
Problem on NEs
above PS core

3930
Nastar
Service
Assess
ment
Type
Demarcation
Type
Abnormal Video
Streaming Start
Delay
Issue 03 (2015-07-30)
Demarcation
Result
Release
Terminal Problem

4**
Terminal Problem

5**
SP Problem
Problem on NEs
above PS core
Others
Others

Window
Terminal Problem

Window
Terminal Problem

SYN and SYN ACK
Problem on NEs
above PS core

ACK and GET
RAN problem/
Problem on NEs
below PS core

SYN ACK and ACK
RAN problem/
Problem on NEs
below PS core
DNS Abnormal Delay
Problem on NEs
above PS core

GET and Response
Problem on NEs
above PS core
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core

Loss Rate
RAN problem/
Problem on NEs
below PS core

Rate
Problem on NEs
above PS core
High Code Rate
SP Problem

3931
Nastar
Service
Assess
ment
Type
Integrity
File
Transfer
Issue 03 (2015-07-30)
Accessib
ility
Demarcation
Type
Video Streaming
Play Stall
File Request
Response Failure
Demarcation
Result

Period
RAN problem/
Problem on NEs
below PS core
Low Upstream
Problem on NEs
above PS core
Others
Others

Window
Terminal Problem

Window
Terminal Problem
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core

Loss Rate
RAN problem/
Problem on NEs
below PS core

Rate
Problem on NEs
above PS core
High Code Rate
SP Problem

Between Clips in Playing
Period
RAN problem/
Problem on NEs
below PS core
Low Upstream
Problem on NEs
above PS core
Others
Others

4**
Terminal Problem

5**
SP Problem

(RAN Problem)
RAN problem/
Problem on NEs
below PS core
SP Problem
Problem on NEs
above PS core

3932
Nastar
Service
Assess
ment
Type
Demarcation
Type
Abnormal File
Request
Response Delay
Integrity
File Transfer
Failure
Slow File
Transfer
Issue 03 (2015-07-30)
Demarcation
Result
Others
Others
DNS Abnormal Delay
Problem on NEs
above PS core

SYN and SYN ACK
Problem on NEs
above PS core

SYN ACK and ACK
RAN problem/
Problem on NEs
below PS core

ACK and GET/POST
RAN problem/
Problem on NEs
below PS core
Abnormal Delay between

Redirect Response and
SYN
RAN problem/
Problem on NEs
below PS core

Problem on NEs
above PS core
Others
Others

4**
Terminal Problem

5**
SP Problem
Release
Terminal Problem
SP Problem
Others
Others

Window
Terminal Problem

Loss Rate
RAN problem/
Problem on NEs
below PS core

Rate
Problem on NEs
above PS core

Window
Terminal Problem

3933
Nastar
Service
Assess
ment
Type
Demarcation
Type
Demarcation
Result
High Uplink
Retransmission Rate
RAN problem/
Problem on NEs
below PS core
Abnormal Downstream
RTT Delay
RAN problem/
Problem on NEs
below PS core
Low Upstream
Problem on NEs
above PS core
Others
Others
Signaling Procedure
Issue 03 (2015-07-30)
Procedure Type
Procedure Name
SGSN
GPRS Attach
SGSN
Combined Attach
SGSN
Intra Combined RAU with IMSI Attached
SGSN
Inter Combined RAU with IMSI Attached
SGSN
MS Init GPRS Detach
SGSN
SGSN
CN Init GPRS Detach
SGSN
CN Init Combined Deatch
SGSN
Implicit GPRS Detach
SGSN
Implicit Combined Detach
SGSN
MS Init IMSI Detach
SGSN
RAN Init Iu Release
SGSN
CN Init Iu Release
SGSN
RAU(others)
SGSN
Intra RAU
SGSN
Intra Combined RAU
SGSN
Inter RAU
SGSN
Inter Combined RAU

3934
Nastar
Issue 03 (2015-07-30)
Procedure Type
Procedure Name
SGSN
Periodic RAU
SGSN
Periodic Combined RAU
SGSN
Intra SRNS Relocation
SGSN
Inter SRNS Relocation
SGSN
SGSN
SGSN
Service Req
SGSN
Paging
SGSN
MS Init PDP Act
SGSN
MS Init PDP Sec Act
SGSN
CN Init PDP Act
SGSN
MS Init PDP Deact
SGSN
CN Init PDP Deact
SGSN
MS Init PDP Mod
SGSN
CN Init PDP Mod
SGSN
RAN Init RAB Release
SGSN
CN Init RAB Release
SGSN
CN Init PDP Sec Act
SGSN
RAB Assignment
SGSN
SGSN
SGSN
MME
EPS Attach
MME
Combined Attach
MME
Intra USN Intra E-UTRAN TAU
MME
Inter USN Intra E-UTRAN TAU
MME
eNodeB S1 Release
MME
CN Init S1 Release
MME
MS Init Detach

3935
Nastar
Issue 03 (2015-07-30)
Procedure Type
Procedure Name
MME
CN Init Detach
MME
MME
MS Init IMSI Detach
MME
CN Init IMSI Detach
MME
CN Init Implicit Detach
MME
X2 HandOver
MME
Intra MME S1 HandOver
MME
Inter MME S1 HandOver
MME
Paging
MME
SGs Paging
MME
Service Req
MME
MME
Intra USN GERAN to E-UTRAN Inter RAT TAU
MME
Intra USN UTRAN to E-UTRAN Inter RAT TAU
MME
Intra USN UTRAN Iu mode to E-UTRAN Inter RAT handover
MME
Inter USN UTRAN Iu mode to E-UTRAN Inter RAT handover
MME
Inter USN GERAN/UTRAN to E-UTRAN TAU
MME
Intra USN E-UTRAN to GERAN Inter RAT RAU
MME
Intra USN E-UTRAN to UTRAN Inter RAT RAU
MME
Intra USN E-UTRAN to UTRAN Iu mode Inter RAT handover
MME
Inter USN E-UTRAN to UTRAN Iu mode Inter RAT handover
MME
Inter USN E-UTRAN to GERAN/UTRAN Inter RAT RAU
MME
Intra USN Intra E-UTRAN Combined TAU
MME
Intra USN GERAN to E-UTRAN Inter RAT Combined TAU
MME
Intra USN UTRAN to E-UTRAN Inter RAT Combined TAU
MME
Inter USN Intra E-UTRAN Combined TAU
MME
Inter USN GERAN/UTRAN to E-UTRAN Combined TAU
MME
Intra USN Intra E-UTRAN Periodic TAU
MME
Dedicated Bearer Act

3936
Nastar
Issue 03 (2015-07-30)
Procedure Type
Procedure Name
MME
PDN GW Initiated Bearer Mod with Bearer QoS Update
MME
HSS Initiated Subscribed QoS Mod
MME
PDN GW Initiated Bearer Mod Without Bearer QoS Update
MME
MME
MME Initiated Dedicated Bearer Deact
MME
Bearer Resource Mod
MME
PDN Connectivity
MME
PDN Disconnection
MME
MME Requested PDN Disconnection
MME
Bearer Resource Allocation
MME
Default Bearer Act
GGSN/SAE-GW
Create PDP
GGSN/SAE-GW
Update PDP
GGSN/SAE-GW
Delete PDP
GGSN/SAE-GW
Traffic
SAE-GW
Create Session
SAE-GW
Modify Bearer
SAE-GW
Delete Session
SAE-GW
Create Bearer
SAE-GW
Update Bearer
SAE-GW
Delete Bearer
SAE-GW
Release Access Bearers
SAE-GW
Modify Bearer Command
SAE-GW
Delete Bearer Command
SAE-GW
Bearer Resource Command
GGSN/SAE-GW
Create Indirect Data Forwarding Tunnel
GGSN/SAE-GW
Delete Indirect Data Forwarding Tunnel
GGSN/SAE-GW
Authentication access
GGSN/SAE-GW
Radius Accounting

3937
Nastar
Procedure Type
Procedure Name
GGSN/SAE-GW
Disconnect
GGSN/SAE-GW
Credit-Control Messages (Gy)
GGSN/SAE-GW
Re-Auth Messages (Gy)
GGSN/SAE-GW
Abort-Session Messages (Gy)
GGSN/SAE-GW
Credit-Control Messages (Gx)
GGSN/SAE-GW
Re-Auth Messages (Gx)
GGSN/SAE-GW
Abort-Session Messages (Gx)

Cause
SOURCE
CHR_PROC_INIT_CAUSE_MS
CHR_PROC_INIT_CAUSE_MS_ATTACH
CHR_PROC_INIT_CAUSE_MS_RAU
CHR_PROC_INIT_CAUSE_MS_DEACT_DECODE_FAIL
CHR_PROC_INIT_CAUSE_MS_DEACT_LLC_FAIL
CHR_PROC_INIT_CAUSE_MS_DEACT_INSUFF_RESOURCE
Procedure initiated
by the MS
CHR_PROC_INIT_CAUSE_MS_DEACT_REGULAR
CHR_PROC_INIT_CAUSE_MS_DEACT_QOS_NOT_ACCEPT
CHR_PROC_INIT_MS_ACT
CHR_PROC_INIT_MS_SEC_ACT
CHR_PROC_INIT_MS_MOD
CHR_PROC_INIT_MS_SERVICE_REQ_SIGNALLING
CHR_PROC_INIT_MS_SERVICE_REQ_DATA
CHR_PROC_INIT_MS_SERVICE_REQ_PAGING_RSP
Issue 03 (2015-07-30)

3938
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_SGSN
CHR_PROC_INIT_CAUSE_SGSN_INTERNAL_FAIL
CHR_PROC_INIT_CAUSE_SGSN_INIT_SECURITY
CHR_PROC_INIT_CAUSE_SGSN_INIT_UPDATE_LOCATION
CHR_PROC_INIT_CAUSE_SGSN_DIFF_SERVICE_CHK
CHR_PROC_INIT_CAUSE_SGSN_LICE_LIMIT
CHR_PROC_INIT_CAUSE_SGSN_FLOW_CTRL
CHR_PROC_INIT_CAUSE_SGSN_IUFLEX_CFG_ERR
CHR_PROC_INIT_CAUSE_SGSN_APNNI_FORBID
CHR_PROC_INIT_CAUSE_SGSN_DETACH_NONACT_USER
CHR_PROC_INIT_CAUSE_LMT_DEL
CHR_PROC_INIT_CAUSE_SGSN_USPU_LOCKED
CHR_PROC_INIT_CAUSE_OLD_SGSN
CHR_PROC_INIT_CAUSE_OLD_SGSN_IMSI_UNKOWN
CHR_PROC_INIT_CAUSE_OLD_SGSN_MISS_MAND_IE
CHR_PROC_INIT_CAUSE_NEW_SGSN
CHR_PROC_INIT_SGSN_ACT
CHR_PROC_INIT_SGSN_MOD
Procedure initiated
by the SGSN
CHR_PROC_INIT_CAUSE_SGSN_DEACT_PATH_ERR
CHR_PROC_INIT_CAUSE_SGSN_DEACT_CARD_FAIL
CHR_PROC_INIT_CAUSE_SGSN_DEACT_CDRF_LIMIT
CHR_PROC_INIT_CAUSE_SGSN_DEACT_CAMEL_DELETE
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GGSN_RESTART
CHR_PROC_INIT_CAUSE_SGSN_DEACT_PDP_IDLE
CHR_PROC_INIT_CAUSE_SGSN_DEACT_LOC_STATE_ERR_
IND
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GB_ERR_IND_PDP
_NOT_ACTIVE
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GB_ERR_IND_LLC
_DATA_UNITDATA_ERR
D
D
D
D
CHR_PROC_INIT_CAUSE_SDB
Issue 03 (2015-07-30)

3939
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_HLR
CHR_PROC_INIT_CAUSE_HLR_SUB_DEL
CHR_PROC_INIT_CAUSE_HLR_SUB_CAMEL_DEL
CHR_PROC_INIT_CAUSE_HLR_CANCEL_LOCATION
CHR_PROC_INIT_CAUSE_HLR_DEACT_SUB_MOD
Procedure initiated
by the HLR
CHR_PROC_INIT_CAUSE_HLR_ALL_ODB
CHR_PROC_INIT_CAUSE_HLR_VPLMN_ODB
CHR_PROC_INIT_CAUSE_HLR_HPLMN_ODB
CHR_PROC_INIT_CAUSE_HLR_ARD
CHR_PROC_INIT_CAUSE_HLR_ZC_RESTRIC
CHR_PROC_INIT_CAUSE_HLR_SUBSCRIBE_INFO_FORBID
CHR_PROC_INIT_CAUSE_HLR_AUTHSET_ERROR
Issue 03 (2015-07-30)
Procedure initiated
by the GGSN
CHR_PROC_INIT_CAUSE_GGSN
Procedure initiated
by the DNS
CHR_PROC_INIT_CAUSE_DNS
CHR_PROC_INIT_CAUSE_DNS_RET_INVALID_ADDR
Procedure initiated
by the MSC
CHR_PROC_INIT_CAUSE_MSC
CHR_PROC_INIT_CAUSE_MSC_UNREACHABLE
Procedure initiated
by the EIR
CHR_PROC_INIT_CAUSE_EIR
Procedure initiated
by the SCP
CHR_PROC_INIT_CAUSE_SCP
Procedure initiated
by the BSS
CHR_PROC_INIT_CAUSE_BSS
Procedure initiated
by the RNC
CHR_PROC_INIT_CAUSE_RNC

3940
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GTPU_BLOCK
CHR_PROC_INIT_CAUSE_SGSN_DEACT_GTPU_SM_IP_TEID
_REPEATED
CHR_PROC_INIT_CAUSE_SGSN_DEACT_NO_EPS_BR_CONTEXT
CHR_PROC_INIT_CAUSE_APN_RESTRICTION
Procedure initiated
by the SGSN
CHR_PROC_INIT_CAUSE_SMARTPHONE_SPECIAL_CAUSE_
REJECT
CHR_PROC_INIT_CAUSE_SMARTPHONE_PARKING_APN
CHR_PROC_INIT_CAUSE_SMARTPHONE_DETACH_ABNOR
MAL_MS
CHR_PROC_INIT_CAUSE_SMARTPHONE_WAKE_UP_DETACH
CHR_PROC_INIT_CAUSE_SMARTPHONE_WAKE_UP_DEAC
T_PARKING_APN
CHR_PROC_INIT_CAUSE_SGSN_INTERNAL_PDP_MOD
CHR_PROC_INIT_CAUSE_UE
CHR_PROC_INIT_CAUSE_UE_ATTACH
CHR_PROC_INIT_CAUSE_UE_HO
Procedure initiated
by the UE
CHR_PROC_INIT_UE_DETACH_FOR_IMSI_DETACH
CHR_PROC_INIT_UE_DETACH_FOR_PS_DETACH
CHR_PROC_INIT_MS_ESR_MO_CSFB_OR_1xCSFB
CHR_PROC_INIT_MS_ESR_MT_CSFB_OR_1xCSFB
CHR_PROC_INIT_MS_ESR_MO_CSFB_EMERGENCY_CALL_
OR_1xCSFB_EMERGENCY_CALL
CHR_PROC_INIT_CAUSE_PGWSGW
Procedure initiated
by the PGW/SGW
CHR_PROC_INIT_CAUSE_PGWSGW_BEARER_TO_BE_REMOVED
CHR_PROC_INIT_CAUSE_PGWSGW_CONTEXT_NOT_FOUN
D
CHR_PROC_INIT_CAUSE_PGWSGW_VOIMS_PAGING
Procedure initiated
by the HSS
Issue 03 (2015-07-30)
CHR_PROC_INIT_CAUSE_HSS

3941
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_ENODEB
CHR_PROC_INIT_CAUSE_ENODEB_CSFB_TRIGGERED_HO
CHR_PROC_INIT_CAUSE_ENODEB_SRVCC_GERAN_WITHO
UT_DTM
Procedure initiated
by the eNodeB
CHR_PROC_INIT_CAUSE_ENODEB_SRVCC_GERAN_WITH_
DTM_WITHOUT_HO
CHR_PROC_INIT_CAUSE_ENODEB_SRVCC_UTRAN_WITHO
UT_PSHO
CHR_PROC_INIT_CAUSE_ENODEB_SRVCC_UTRAN_WITH_
PSHO
CHR_PROC_INIT_CAUSE_ENODEB_S1_RELEASE
CHR_PROC_INIT_CAUSE_ENODEB_ERAB_RELEASE
CHR_PROC_INIT_CAUSE_ENODEB_HANDOVER_ERABFAIL
Issue 03 (2015-07-30)

3942
Nastar
Cause
SOURCE
CHR_PROC_INIT_CAUSE_MME
CHR_PROC_INIT_CAUSE_PAGING_BY_NETWORK_DETACH
CHR_PROC_INIT_CAUSE_PAGING_BY_SM_SIG
CHR_PROC_INIT_CAUSE_PAGING_BY_SMS
CHR_PROC_INIT_CAUSE_PAGING_BY_GSS
CHR_PROC_INIT_CAUSE_PAGING_BY_CS
CHR_PROC_INIT_CAUSE_PAGING_BY_INSM
CHR_PROC_INIT_CAUSE_PAGING_BY_SM_DATA
CHR_PROC_INIT_IMSI_DETACH_BY_AUTO_OFFLOAD
CHR_PROC_INIT_IMSI_DETACH_BY_VLR_RESET
CHR_PROC_INIT_IMSI_DETACH_BY_HSS_CS_NOT_ALLOW
CHR_PROC_INIT_PAGING_BY_PGW_RESELECT,
Procedure initiated
by the MME
CHR_PROC_INIT_PDN_DEACT_BY_PGW_RESELECT
CHR_PROC_INIT_DETACH_BY_PGW_RESELECT
CHR_PROC_INIT_DETACH_FOR_REATTACH_REQUIRED_D
UETO_ABNORMAL_SINGALING_CTRL
CHR_PROC_INIT_DEACTVIATE_FOR_REACTIVATE_REQUI
RED_DUETO_ABNORMAL_SINGALING_CTRL
CHR_PROC_INIT_PARKING_APN_ACVTIVATE_DUETO_AB
NORMAL_SINGALING_CTRL
CHR_PROC_INIT_DETACH_FOR_REATTACH_NOT_REQUIR
ED_DUETO_ABNORMAL_SINGALING_CTRL
CHR_PROC_INIT_PAGING_IMSI_PS_BY_SGWPGW_FAILURE
CHR_PROC_INIT_PAGING_STMSI_PS_BY_SGWPGW_FAILURE
CHR_PROC_INIT_PDN_DEACT_BY_SGWPGW_FAILURE
CHR_PROC_INIT_DETACH_BY_SGWPGW_FAILURE
Appendix: Exception Cause Classification (Combined Analysis)

The section describes the exception cause classification in the summary table.
NOTE
The following table lists all the exception causes of all RATs. For detailed exception causes of each RAT, see
the exception cause description chapters of each RAT 5.11.10 Appendix: Exception Cause Classification /
Key Signaling.
Issue 03 (2015-07-30)

3943
Nastar
Abnormal
CauseClassificatio
n
Non-exception
NA
RAN
Accessibility
Abnormal
Access Failure (Intra-System)

Access Failure (Inter-System)
Access Failure
Call Setup Failure
Setup Failure(MOC)
Setup Failure(MTC)
Abnormal TA on Access
Abnormal RACH Level on Access
Setup Failure
RAN
Retainability
Abnormal
Abnormal Release (Intra-system)

Abnormal Release (Inter-system)
Abnormal Call Release
Service Interruption
Abnormal Release
RAN Mobility
Abnormal

Inter-System Outgoing Handover Failure (Normal Release)
Inter-System Outgoing Handover Failure (Abnormal Release)
Inter-System Incoming Handover Failure
Handover Failure
RAN Delay
Abnormal
Delay Problem
RAN Service
Quality
Abnormal
Poor Voice Quality Connect Ack->Disconnect
Short Call Problem

Abnormal Service Interaction Delay
Issue 03 (2015-07-30)

3944
Nastar
Abnormal
CauseClassificatio
n
PS Core
Accessibility
Abnormal
Attach Abnormal
Service Req Abnormal
Paging Abnormal
PDP Act Abnormal
PDP Sec Act Abnormal
RAB Assignment Abnormal
PDN GW Dedicated Bearer Act Abnormal
Default Bearer Act Abnormal
Dedicated Bearer Act Abnormal
PDN Connectivity Abnormal
Create PDP Abnormal
Create Session Abnormal
Create Bearer Abnormal
Create Indirect Data Forwarding Tunnel Abnormal
PS Core
Mobility
Abnormal
RAU Abnormal
Relocation Abnormal
System Change Abnormal
TAU Abnormal
Handover Abnormal
Interoperation Abnormal
PS Core PDP
Modification
Abnormal
PDP Mod Abnormal

PDN GW Initiated Bearer Mod Abnormal
Update PDP Abnormal
PS Core
Retainability
Abnormal
Detach Abnormal
Iu Release Abnormal
RAB Release Abnormal
PDP Deact Abnormal
PDN GW Initiated Bearer Deact Abnormal
Issue 03 (2015-07-30)

3945
Nastar
Abnormal
CauseClassificatio
n
S1 Release Abnormal
Bearer Deact Abnormal
PDN Disconnection Abnormal
Delete PDP Abnormal
Delete Session Abnormal
Delete Bearer Abnormal
Release Access Bearers Abnormal
Delete Bearer Command Abnormal
Delete Indirect Data Forwarding Tunnel Abnormal
PS Core
Bearer
Modification
Abnormal
Bearer Mod Abnormal

Bearer Resourece Mod Abnormal
Modify Bearer Abnormal
Update Bearer Abnormal
Modify Bearer Command Abnormal
Bearer Resource Command Abnormal
Traffic
Issue 03 (2015-07-30)

3946
Nastar
6 LTE Network Optimization
LTE Network Optimization
About This Chapter

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.1 LTE Coverage Analysis
The LTE coverage analysis function enables the Nastar to analyze the measurement reports
reported by MSs and intuitively display the coverage and user allocation of the test cell. This
helps the user to quickly locate wireless network problems, such as weak cell coverage, cross
coverage, and poor QoS occur on the network.
6.2 LTE Cell Performance Analysis
The Nastar provides data about subscribers experiencing abnormal calls in problematic cells and
helps to analyze the root causes of these abnormal calls. This helps operators 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.
6.3 LTE Terminal Analysis
The LTE terminal analysis function enables the Nastar to analyze KPIs based on the call records
of subscribers. It helps operators identify the terminals with poor performance so that the
operators can motivate terminal vendors to upgrade their terminal products or they can provide
guidance for subscribers to purchase terminals with better performance. By doing the preceding,
the function helps the operators provide subscribers with stable services and improve the
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
Issue 03 (2015-07-30)

3947
Nastar
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.
6.4 LTE Network Geographic Observation
The Nastar geographically locates and displays network coverage, traffic, users, and unusual
events after collecting the entire network data, intuitively displaying general network conditions
and problem areas.
6.5 VIP Analysis
Issue 03 (2015-07-30)

3948
Nastar
6.1 LTE Coverage Analysis

The LTE coverage analysis function enables the Nastar to analyze the measurement reports
reported by MSs and intuitively display the coverage and user allocation of the test cell. This
helps the user to quickly locate wireless network problems, such as weak cell coverage, cross
coverage, and poor QoS occur on the network.
6.1.1 Basics of LTE Coverage Analysis

This section describes the basics of LTE coverage analysis, including the analysis function,
technical specification, and feature restriction. The basic knowledge helps you perform the
operations related to LTE coverage analysis. Read this section before performing LTE coverage
analysis.
NOTE
Functions of LTE Coverage Analysis

The LTE coverage analysis function enables the Nastar to analyze the measurement reports sent
by UEs, measurement information reported by eNodeBs, and related events in important call
records. The analysis results help you to check the coverage status of the measurement cell on
the network and determine whether problems such as weak cell coverage, cross coverage, and
poor quality of service occur on the network.
The LTE coverage analysis data includes the measurement reports sent by UEs, measurement
information reported by eNodeBs, and related events in important call records.
l
Downlink RSRP and RSRQ that are contained in the measurement reports reported by UEs.
Information about the indicators such as UE TxPower,Timing Advance (TA), and number
of uplink and downlink retransmissions collected and processed by the eNodeB.UE
TxPower is converted from the Power Headroom (PH) reported by UEs.
Key events including RRC Connection Setup Requests, RRC Connection Setup Failures,
Abnormal E-RAB Releases, UL Retransmissions, DL Retransmissions, and Intra-RAT HO
Failures.
After setting coverage analysis criteria, the Nastar performs coverage analysis to the selected
cells. The analysis results are displayed in the format of a 2D chart, 3D chart, and overview table.
l
Issue 03 (2015-07-30)
On the 2D Chart tab page, the following charts are displayed: charts of indicator distribution
in PDF and CDF mode (the indicators include TA, UE transmit power, RSRP, RSRQ, UL
DM RS RxPower, UL SINR, and CQI), charts of average indicator measurement value and
TA distribution (the indicators include average UE transmit power, average RSRP, and
average RSRQ), charts of number of events and TA distribution (the key events include
RRC Connection Setup Requests, RRC Connection Setup Failures, Abnormal E-RAB
Releases, UL Retransmissions, DL Retransmissions, Intra-RAT Outgoing Handover
3949
Nastar
Execution Failures, Inter-RAT Outgoing Handover Execution Attempts, and Inter-RAT

Outgoing Handover Execution Failures).
l
In the 3D chart, the distribution of indicator pairs is displayed, including the RSRP
distribution of different RSRQ indicator values, UE TxPower distribution of different TA
values, RSRP distribution of different TA values, and the RSRQ distribution of different
TA values.
In the overview table, the statistics of all service indicators such as TA, RSRP, RSRQ, and
UE TxPower are displayed in 2D charts.
The analysis results can be exported as a .csv, .xls, or .xlsx file. You can optimize the cell
coverage based on the analysis results.
Function Principles
The data source for LTE coverage analysis is the eNodeB CHR data on the NE side.
Issue 03 (2015-07-30)

3950
Nastar

User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U

a user enables the basic data subscription function on
the Nastar client, the Nastar issues a basic data
Issue a
subscrip
tion
comma
nd
eSA
U
U20
00/
M20
00

M2000.
Forward
the
subscrip
tion
comma
nd
U20
00/
M20
00
eNod
eB

Upload
raw data
(CHR)
eNo
deB
Trac
e
Serv
er
To upload the raw data (eNodeB CHR) to the Trace

Server.
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U

Deliver
a
preproc
essing
task
(direct)
eSA
U
LTE
SAU
To deliver a data-preprocessing task to the LTE SAU,

requesting the LTE SAU to start the data-preprocessing
task.
Collect
data
(CHR)
(direct)
LTE
SA
U
Trac
e
Serv
er
To collect raw data (eNodeB CHR) from the Trace

Server.
2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)

3951
Nastar
User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Purpose
Trac
e
Serv
er
LTE
SAU
The collected data (eNodeB CHR) is placed in the

specified path of the LTE SAU.
Upload
preproc
essed
data
(direct)
LTE
SA
U
eSA
U
To upload preprocessed data (eNodeB CHR) to the

eSAU.
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nast
ar
Serv
er
eSA
U
To issue a data query command. After a user enables the

data maintenance function on the Nastar client, the
Nastar checks whether the analysis data is ready on the
eSAU.
Return
data
query
results
eSA
U
Nast
ar
Serv
er
To return data integrity check results to the Nastar

server and display the results on the Nastar client.
4.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nast
ar
Serv
er
eSA
U
To deliver a task execution request to the eSAU. After

a user creates an analysis task on the Nastar client, the
Upload
data
analysis
results
eSA
U
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for LTE Coverage Analysis

of analysis time.
Issue 03 (2015-07-30)

3952
Nastar
NOTE
Item
Execution type
One-time task

analysis task
<= 10,000 cells
Number of allowed
analysis tasks
<= 50

one analysis task
<= 7 days

task
85 minutes

15 days

15 days
6.1.2 Preparations for LTE Coverage Analysis

Before running an LTE coverage analysis task, you must verify user rights and related
environment information and obtain related data, ensuring that the task is properly executed.
Read this section before performing LTE coverage analysis.

The coverage analysis in the LTE mode is divided into the FDD coverage analysis and TDD
coverage analysis. The two functions are independent from each other.
l
For LTE FDD coverage analysis:

Check that you have obtained the licenses for LTE FDD basic function and LTE FDD
coverage analysis, and the licenses are valid.
Check that have the following operation rights for subscribing the data: data subscription
management authentication, LTE FDD coverage analysis operation right, and the
operation rights to operate the analyzed NEs.
Subscribing to analysis data imposes higher requirements on the security. You are
advised to ask the authorized administrator to enable analysis data subscription.
Check that you have the following operation rights of analysis task: LTE FDD coverage
analysis operation right, and the operation rights to operate the NE groups that the
analyzed NEs belong to.
Issue 03 (2015-07-30)

3953
Nastar
For LTE TDD coverage analysis:

Check that you have obtained the licenses for LTE TDD basic function and LTE FDD
coverage analysis, and the licenses are valid.
management authentication, LTE TDD coverage analysis operation right, and the
Check that you have the following operation rights of analysis task: LTE TDD coverage
analysis operation right, and the operation rights to operate the NE groups that the
NOTE
l When the number of cells controlled by the LTE basic license and the number of online users reach the
upper limits, the Alarm dialog box is displayed, prompting you to upgrade the license. When you query the
license consumption in the license Information, the result is not consistent with that displayed in the
Alarm dialog box because the exceeded number has not been reported. The data displayed in the Alarm
dialog box is correct. You are advised to upgrade the license in a timely manner.
l LTE Periodic MR Period Setting is only available to an account in the Administrators group or a user with
data subscription management permission.

Configuration Data
The configuration data of the NEs for the analyzed area 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 theme analysis process.
Data.
NOTE
You are advised to perform coverage analysis with the granularity of a day to ensure the validity and

Check that the matching U2000/M2000 version is V200R013C00 (or later), the NE version is
BTS3900 V100R008C00SPC020 (or later), BTS3900 V100R008C01SPC200 (or later),
Issue 03 (2015-07-30)

3954
Nastar
BTS3900 V100R009C00 (or later),BTS3900 V100R010C00 (or later), BTS3900

V100R010C10 (or later), or BTS3900 V100R011C00 (or later).
6.1.3 Process of LTE Coverage Analysis

This section describes the process of LTE coverage analysis and detailed operations in the
process.
l
Prerequisite
Procedure
Prerequisite
LTE configuration data has been imported to the Nastar Database. For details, see 6.1.2
Preparations for LTE Coverage Analysis.
Procedure
Issue 03 (2015-07-30)

3955
Nastar
Table 6-2 Description of the LTE coverage analysis process

N Procedure
o
.
Description
Reference
(
1
)

3.6 Checking the

Data
Check the
integrity of
LTE coverage
analysis data
Procedure:
1. Set Data Type to LTE FDD Coverage
Analysis Data or LTE TDD
Coverage Analysis Data.
4. Click Query.
(2).
NOTE
(
2
)
LTE Periodic
MR Period
Setting

LTE Periodic MR Period Setting
Procedure:
1. In the LTE Periodic MR Period
Setting window, set Periodic MR
Period, Number of Sampled Users
and Number of Times MRs Are
Reported.
For details about

parameters, see LTE
Periodic MR Period
Setting Parameters.
2. Click Configure.
Issue 03 (2015-07-30)

3956
Nastar
N Procedure
o
.
Subscribe to
LTE coverage
analysis data
(basic).
Description
Reference

3.5 Subscribing to
Analysis Data
Procedure:
Management window, click the LTE
FDD or LTE TDD tab.
NOTE
If you want to subscribe to data related to
LTE FDD coverage analysis, click the
LTE FDD tab; if you want to subscribe to
data related to LTE TDD coverage
analysis, click the LTE TDD tab.
2. Select the NEs to be configured from

the left navigation tree.
3. On the Basic Subscription Settings
tab page, click Set.
dialog box, set Coverage Analysis
Data to ON.
By default, The default subscription
switch status is No Modification.
5. Click Confirm.
Verify that data source subscription is
successfully enabled by viewing
information displayed in the Log Info
area.
Issue 03 (2015-07-30)

3957
Nastar
N Procedure
o
.
Subscribe to
LTE coverage
analysis data
(application)
Description
Reference

Procedure:
Management window, click the LTE
FDD or LTE TDD tab.
NOTE
If you want to subscribe to data related to
LTE FDD coverage analysis, click the
LTE FDD tab; if you want to subscribe to
data related to LTE TDD coverage
analysis, click the LTE TDD tab.
2. Select the NEs to be configured from

the left navigation tree.
3. On the Coverage Analysis tab page,
click ON.
Check that data is successfully
subscribed by clicking Refresh and
viewing the application subscription
status.
Check the
integrity of
LTE coverage
analysis data

Procedure:
3.6 Checking the

Data
1. Set Data Type to LTE FDD Coverage

Analysis Data or LTE TDD
Coverage Analysis Data.
4. Click Query.
Issue 03 (2015-07-30)

3958
Nastar
N Procedure
o
.
Description
Reference
(
3
)
Navigation path: In the left navigation

tree of the Analysis Task Management
window, choose Theme Function > Basic
Network Optimization > LTE Coverage
Analysis.
3.7 Creating an Analysis

Task
Create an LTE
coverage
analysis task.
Procedure:
1. Double-click the LTE Coverage
Analysis node.
2. Set the task name and task remarks.
Click Next.
analysis type and NEs to be analyzed.
4. On the Parameter Settings tab page,
set filter criteria.
5. Select Numbers and set the report
number. Click Next.
6. Select the analysis time period. The
Nastar obtains the relevant analysis
data in the time period.
7. Click Finish.
For details about parameters, see
(
4
)
View LTE
coverage
analysis
results.

Task Result area, select a result record of
the task.
Procedure:
1. Double-click the analysis result of a
task.
2. In the displayed LTE Coverage
Analysis Task window, view the LTE
coverage analysis result.
Issue 03 (2015-07-30)

l For details, see

3.8 Querying
Analysis Results
description about the
window for displaying
task results, see 6.1.4
Interface
Description: LTE
Coverage Analysis.
3959
Nastar
N Procedure
o
.
Description
Reference
(
5
)
Navigation path: Click the icon on the

toolbar in the upper left part of each
analysis results window.
3.10 Exporting Analysis

Reports
Export LTE
coverage
analysis
reports.
Procedure:
NOTE
If the TA counter columns exceed the
restriction of 256 columns of the .xls file,
export LTE coverage analysis reports
as .csv or .xlsx files. Otherwise, the LTE
coverage analysis report cannot be
exported.
3. Click Save.

Parameter
Description
Periodic MR
Period
Number of
Sampled Users

Nastar.
NOTE
Issue 03 (2015-07-30)

3960
Nastar
Parameter
Description
Number of
Times MRs
Are Reported


Basic Subscription
Issue 03 (2015-07-30)

3961
Nastar
Parameter
Description
Coverage
Analysis Data
(CHR)
Switch for enabling or disabling the reporting of eNodeB CHR data. You
You can click
l Common tab page: Set Trace Event Block Type. The selected type of
event block will be traced and recorded in CHRs. The details about
various types of event blocks are as follows:
measurement
PERIOD THROUGHPUT MEASUREMENT, periodic throughput
measurement
measurement
measurement
measurement
UE CAPABILITY INFORMATION, UE capability measurement
CSFB PREP, CSFB
PERIOD PRIVATE THROUGHPUT MEASUREMENT MDT,
periodic throughput MDT measurement
Issue 03 (2015-07-30)

3962
Nastar
Parameter
Description
PERIOD_UE_MultiRRU_UL_RSRP_MR, uplink RSRP events in
multiple RRU cells
Object at the lower left corner to select the idle object to be measured.
The range of selected objects is displayed in the Idle State
Measurement Object Range column on the 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.
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 interRAT 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).
Idle State Measurement Object Range: Specify the range of idle
objects to be measured. A maximum of 32 cells or eight TACs can
be selected.
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.
Issue 03 (2015-07-30)

3963
Nastar
Parameter
Description
UltraOverla
pping
Cover
age
Cell
Defini
tion
Specifies the threshold value for a ultra-overlapping coverage

cell.
DL RSRP
difference
between serving
cell and
neighboring cell
A number of
neighboring cells
meeting previous
conditions B
and serving cell
RSRP > C
This parameter enables the Nastar to obtain only the data that
shows the DL RSRP difference between the serving cell and
its neighboring cell less than or equal to A, the number of
neighboring cells meeting the previous condition greater than
or equal to B, and the RSRP of the serving cell greater than C.
Value range:
l A: [0,10]
l B: [1,6]
l C: [-140,-43]
Overs
hootin
g Cell
Defini
tion
RSRP of
neighboring cell
as evaluated
object - Serving
cell RSRP > K,
and Serving cell
RSRP > L
Specifies the threshold value for a overshooting coverage cell.

shows the difference between the RSRP of a neighboring cell
as the evaluated object and the RSRP of the serving cell greater
than D and the RSRP of the serving cell greater than E.
Value range:
l D: [-10,0]
l E: [-140,-43]
HighInterfe
rence
Defini
tion
Average highinterference value

F
Defines the high-interference threshold.

Default value: -105
Value range: F: [-127,-75]

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Issue 03 (2015-07-30)

3964
Nastar
Parameter
Description
Remarks

NE information
Parameter
Description
Analysis Type
Select LTE TDD or LTE FDD.
Select NE(s)

NOTE
Distribution parameter setting
Issue 03 (2015-07-30)

3965
Nastar
Parameter
Parameters
Setting
Description
Analysis
indicator
Sets the filter criteria for analysis data. Then, the Nastar
filters cells that experience coverage problems and meet
the filter criteria in the analysis results.
The Nastar provides filter criteria in two models as
follows:
l In the 2D model, the Nastar allows users to filter cells
by a single counter. The counter can be TA,
UE_TxPower, RSRP, or RSRQ.
For example, 2D: DLRSRP < -110, ratio > 5%
indicates that the serving cells for which Number of
MRs in which the DL RSRP is less than -110
dBm accounts for more than 5% of Total number
of MRs are filtered. That is, cells with weak coverage
problems are filtered.
l In the 3D model, the Nastar allows users to filter cells
in terms of two counters using the and or or
algorithm. The counter can be TA, UE_TxPower,
RSRP, or RSRQ.
For example, 3D: DL RSRP < -110 OR DL RSRQ
> -10, ratio > 5% indicates that the serving cells for
which Number of MRs in which the DL RSRP is
less than -110 dBm or Number of MRs in which
the DL RSRQ is greater than -10 accounts for more
than 5% of Total number of MRs are filtered. That
is, cells with weak coverage problems are filtered.
l The Nastar allows users to set filter criteria based on
OverLappingCell and OverShootingCell.
OverLappingCell:[MRPercent > 0] > 5%
indicates that the ratio of overlapping coverage
MRs of the cell to be evaluated is greater than 5%,
and the number of MRs of the cell to be evaluated
is greater than 3000. That is, the cell is an
overlapping cell.
OverShootingCell:[(CorrelativeRatio > 0.01)
and (CorrelativeCellNum > 8)] > 0% indicates
that the correlation coefficient between the object
to be evaluated when serving as a neighboring
cell and the corresponding primary serving cell is
greater than 1, and the number of MRs of the
object to be evaluated when serving as the
primary serving cell is 3000, and the number of
primary serving cells that meet the preceding two
conditions is greater than or equal to 8. That is,
the cell is an overshooting cell.
When users filter OverLappingCell or
OverShootingCell, the default value of Numbers is
greater than 3000. You can set Numbers as required.
Issue 03 (2015-07-30)

3966
Nastar
Parameter
Description
NOTE
You can add or delete filter criteria as required. A maximum
of 30 filter criteria are allowed.
Numbers
Filters cells based on the size of the traffic amount, that

is, filters cells based on the total number of reports of an
indicator. After the filter criteria are set, analysis results
only meeting the filter criteria can be displayed.
It ranges from 10 to 100000. The default value is 100.
MR RSRP
Coverage Rate
The RSRP value ranges from -140 to -43 dBm. The

default value is -110 dBm.
Other Parameters Setting

Parameter
Description
Over Lapping
Cell Setting
OverLappingCell:[MRPercent > 0] > X indicates that the ratio of

overlapping coverage MRs of the cell to be evaluated is greater than X,
and the number of MRs of the cell to be evaluated is greater than Y. That
is, the cell is an overlapping cell.
By default, X is 5%, and Y is 3000. You can set X and Y as required.
Over Shooting
Cell Setting
If the value for CorrelativeRatio is greater than X and the value for
CorrelativeCellNum is greater than Y, the number of cells for which the
correlative ratio between the cells and the evaluated cell is greater than X
is at least Y.
Correlative ratio: If the evaluated cell is B, the correlative ratio between
B and cell A is calculated using the following formula: Number of MRs
whose serving cell is A and neighboring cell is B and the RSRP in cell A
minus RSRP in neighboring cell B is less than 6 dB/Number of MRs for
which the primary serving cell is A) x 100%.
Number of sampled MRs > 3000: indicates that the number of MRs in the
evaluated cell that is a primary serving cell is greater than 3000.
High
Interference
Setting
Indicates the threshold for the ratio of high interference MRs. The default
value is 5%, and the value range is [0,100].
MR RSRP
Coverage
Setting
Indicates the threshold for the MR RSRP coverage rate. The default value
is -110, and the value range is [-140,-43].
Issue 03 (2015-07-30)

3967
Nastar
Parameter
Description
Duration
Delay
immediately.
Execute on
6.1.4 Interface Description: LTE Coverage Analysis

This section describes the result window of LTE coverage analysis, including functions of each
area in the window, helping you perform related operations.
Opening the Window

l
Select an executed LTE coverage analysis task and double-click a result of the task in the
Task Result area.
Select an executed LTE coverage analysis task, right-click a result of the task in the Task
Main Window
The LTE coverage analysis results are displayed in 2D charts, 3D charts, and tables. For details,
see Figure 6-3, Figure 6-4, and Figure 6-5.
Figure 6-3 2D chart
Issue 03 (2015-07-30)

3968
Nastar
No.
Name
Description
Button area
l Provides the button

for you to export the LTE coverage
analysis overview. Specifically, the summary information about
all cells to be analyzed in the analysis task is exported.
for you to export raw data used for
coverage analysis, which means that you can export detailed
information about all counters related to an analysis task.
for you to export coverage analysis
evaluation results. Specifically, the evaluation information about
all cells to be analyzed in the analysis task is exported.
for you to export information about top
N poorest cells after coverage analysis. Specifically, the detailed
information about top N poorest cells in the analysis task is
exported.
You can export the analysis results in a .csv, .xls, or .xlsx file after
setting the save path, file name, and file format.
NOTE
If the TA counter columns exceed the restriction of 256 columns of the .xls
file, export LTE coverage analysis reports as .csv or .xlsx files. Otherwise, the
LTE coverage analysis report cannot be exported.
Navigation
tree
Contains all NE objects to be analyzed. The system allows you to

filter NE objects using the following parameters:
l DL EARFCN: The default value is ALL, indicating that cells of
all ARFCNs will be displayed in the NE list. If the value is an
ARFCN, the cells of the specified ARFCN will be displayed in
the NE list.
l Filter: The default value is ALL, indicating that all cells will be
displayed in the NE list. If the value is a formula, the cells
matching the specified formula will be displayed in the NE list.
Then, the percentage of the cells that meet the filter criteria is
displayed, and the cells are listed in descending order according
to the percentage.
Filter formulas are set when you create the analysis task.
l Search box: After enter an NE name in the search box, press
Enter or click
. The cells matching the search criteria will be
quickly displayed in the NE list, which is convenient for users.
Issue 03 (2015-07-30)

3969
Nastar
No.
Name
Description
2D chart area
Contains three service tag pages: PDF/CDF, Indicator value, and

Number of key events/TA. On each tab page, each KPI of this service
is displayed in bar charts and line charts. Different services have
different KPIs as follows:
l PDF/CDF service have four KPIs: TA, RSRP, RSRQ, UE TX
POWER, CQI, UL DM RS RxPower and UL SINR. Following
describes how each KPI is mapped to the coordinate system:
The horizontal axis indicates the value of each KPI.
The left vertical axis is a bar chart value, indicating the
percentage of the MRs of each KPI.
The right vertical axis is a line chart value, indicating the total
percentage of the MRs of all KPIs whose value is smaller than
or equal to a KPI value on the horizontal axis.
l Indicator Measurement value/TA service have three KPIs: RSRP,
RSRQ, and UE TX POWER. Following describes how each KPI
is mapped to the coordinate system:
The horizontal axis represents the value of TA.
The left vertical axis represents the value of each column in
the chart. It indicates the percentage of the MRs that have
mapping values on the coordinate system in all the MRs.
The right axis represents the values of RSRP, RSRQ, and UE
TX POWER.
l Number of Events/TA service have multiple KPIs, including RRC
Connect Setup Requests, RRC Connect Setup Failures, Abnormal
E-RAB Releases,UL Retransmission, DL Retransmission, IntraRAT Outgoing Handover Execution Failures, Inter-RAT
Outgoing Handover Requests and Inter-RAT Outgoing Handover
Execution Failures. Following describes how each KPI is mapped
to the coordinate system:
The horizontal axis represents the value of TA.
The left vertical axis represents the value of each column in
the chart. It indicates the percentage of the events that have
mapping values on the coordinate system in all the events.
The right axis represents the number of times that each event
occurs.
NOTE
During the calculation of the counter percentage, the last percentage may be
less than 100% due to the round-off operation.
You can perform the following operations in the chart area:

l You can double-click a chart to zoom in/out the chart.
l You can use the mouse to drag the border of the chart or rightclick the chart and choose Zoom In or Zoom Out or Auto
Range from the shortcut menu to adjust the size of the chart.
Issue 03 (2015-07-30)

3970
Nastar
No.
Name
Description
l You can also use the shortcut menu items to query, save, or print
the chart.
Figure 6-4 3D chart
Issue 03 (2015-07-30)

3971
Nastar
No.
Name
Description
3D chart area
Contains four tab pages: RSRQ/RSRP, TA/UE TX POWER, TA/

RSRP, and TA/RSRQ. The four KPI pairs are formed with two of
the four KPIs: TA, RSRQ, RSRP, and UE TX POWER. On each tab
page, the allocation of each KPI pair is displayed.
The description of the chart area is as follows:
l The horizontal and vertical axes indicate the values of two
different KPIs.
l The color of each cell indicates the percentage of the KPI layout
in the case of a certain KPI pair.
Legends are provided on the right. Each number indicates a
specific percentage value.
l You can use the mouse to drag the border of the chart or rightclick the chart and choose Zoom In or Zoom Out from the
shortcut menu to adjust the size of the chart.
NOTE
You can use the mouse to adjust the size of the chart. Press and hold the
primary mouse button and drag the cursor from the left to the lower right
to zoom in the chart or drag the cursor from the right to the upper left to
zoom out the chart.
You can also use the shortcut menu items to query, save, or print
the chart.
5
Formula area
Set the value ranges of the horizontal and vertical axes of the 3dimension chart, and click Calculate. The Nastar automatically
calculates the total percentage of KPI layout within the value ranges.
Figure 6-5 KPI information summary area
Issue 03 (2015-07-30)

3972
Nastar
No.
Name
Description
KPI
information
summary
table
Displays the statistics of the KPIs of all services in the 2-dimension

window.
For details about parameters, see 6.1.5 Parameters for Viewing LTE
Coverage Analysis Results.
6.1.5 Parameters for Viewing LTE Coverage Analysis Results

This section describes the parameters for querying LTE coverage analysis results, You can refer
to the description when querying LTE coverage analysis results.
Parameter
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
TA
Measurement
Reports
[0,+)
Number
Indicates the
total number of
TA MRs in MRs
for coverage
analysis.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Number of
UE TX POWER
Measurement
Reports
[0,+)
Number
Indicates the
total number of
UE TxPower
MRs in MRs for
coverage
analysis.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Number of
RSRP
Measurement
Reports
[0,+)
Number
Indicates the
total number of
RSRP MRs in
MRs for
coverage
analysis.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Number of
RSRQ
Measurement
Reports
[0,+)
Number
Indicates the
total number of
RSRQ MRs in
MRs for
coverage
analysis.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3973
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Total Number of
CQI
Measurement
Reports
[0,+)
Number
Indicates the
total number of
CQI MRs in
MRs for
coverage
analysis.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Number of
UL DM RS
RxPower
Measurement
Reports
[0,+)
Number
Indicates the
total number of
UL DM RS
RxPower MRs
in MRs for
coverage
analysis.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Number of
UL DM RS
SINR
Measurement
Reports
[0,+)
Number
Indicates the
total number of
UL SINR MRs
in MRs for
coverage
analysis.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average TA
[0,1314]
16*Ts=0.52 ms
Indicates the
timing advance,
which reflects
the distance
between the UE
and the eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average UE TX
POWER
[-17,23]
dBm
Indicates the
transmit power
of a UE, which
reflects the
coverage
strength of
uplink signals.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average RSRP
[-140,-43]
dBm
Indicates the
reference signal
receive power,
which reflects
the coverage
strength of
downlink
reference
signals.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3974
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Average RSRQ
[-19.5,-2.5]
dB
Indicates the
reference signal
receive strength,
which reflects
the coverage
quality of
downlink
reference
signals.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average CQI
[0,15]
N/A
Indicates the
channel quality
indicator (CQI),
which reflects
the quality of a
radio channel.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average UL
DM RS
RxPower
[-150,-30)
dBm
Indicates the
average number
of UL DM RS
MRs in MRs for
coverage
analysis.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average UL
DM RS SINR
[-15,35]
dB
Indicates the
average number
of UL SINR
MRs in MRs for
coverage
analysis.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
MR RSRP
Coverage Rate
[0,100]
Number of MRs
that show that
the RSRP of the
evaluated cell
serving as the
dominant
serving cell
greater than or
equal to X/Total
number of
sampled MRs
that show that
the evaluated
cell serving as
the dominant
serving cell
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

3975
Nastar
6.2 LTE Cell Performance Analysis

The Nastar provides data about subscribers experiencing abnormal calls in problematic cells and
helps to analyze the root causes of these abnormal calls. This helps operators 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.
6.2.1 Basics of LTE Cell Performance Analysis

This section describes the basics of LTE cell performance analysis, including the functions and
technical specifications. Read this section before performing an LTE cell performance analysis.
NOTE
Functions of LTE Cell Performance Analysis

This section describes the functions of LTE cell performance analysis. These functions help
engineers quickly identify problematic cells and obtain 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.
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
eNodeB. If the analysis results indicate that an eNodeB is faulty, the engineers analyze the cells
under the faulty eNodeB 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 eNodeBs or NE groups. This helps engineers better identify the detailed
causes of certain exceptions and solve the problems accordingly.
After identifying the key exceptions in the problematic cells, the Nastar analyzes the bottom
subscribers and bottom terminals with exceptions, bottom peer cells, bottom MME, bottom
TAC, bottom SGW IP and bottom sector equipment or equipment group in the problematic
cells. This helps engineers collect more information about the bottom objects that have low
KPI values. In this way, the function helps engineers quickly identify certain types of
bottom subscriber, bottom terminal and bottom MME and so on with exceptions in the
problematic cells so that the engineers can improve cell performance by eliminating the
exceptions that occur on the bottom objects.
Issue 03 (2015-07-30)

3976
Nastar
When problematic cells are not identified, the Nastar analyzes the exceptions in a large
number of problematic bottom cells under a specific eNodeB to help engineers identify the
bottom cells with the most exceptions.
Except for identifying the problematic cells and the causes of certain exceptions, the Nastar
cover selected causes of certain types of exception, and bottom cells, bottom users, bottom
terminals, bottom peer cells, bottom MME , bottom TAC, bottom SGW IP or bottom sector
equipment or equipment group 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.
NOTE
Under the Nastar, the statistical results of cell performance analysis are different from the statistical results
collected based on 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.
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 eNodeB CHR data and MME CHR data from NEs for LTE cell performance
analysis. The MME CHR data provides the IMSI and IMEI information.
Issue 03 (2015-07-30)

3977
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U

Issue a
subscrip
tion
comma
nd
eSA
U
U20
00/
M20
00

M2000.

3978
Nastar
User
Operat
ion
2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)
Proced
ure
Sou
rce
Dest
inati
on
Purpose
Forward
the
subscrip
tion
comma
nd
U20
00/
M20
00
eNod
eB

Upload
raw data
(eNode
B CHR)
eNo
deB
Trac
e
Serv
er

Server.
Upload
raw data
(MME
CHR)
MM
E
LTE
SAU
To upload the raw data (MME CHR) to the LTE SAU

directly.
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U

Deliver
a
preproc
essing
task
(direct)
eSA
U
LTE
SAU

task.
Collect
data
(eNode
B CHR)
(direct)
LTE
SA
U
Trac
e
Serv
er

Server.
Trac
e
Serv
er
LTE
SAU

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.

3979
Nastar
User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Purpose
Upload
preproc
essed
data
(direct)
LTE
SA
U
eSA
U
To upload preprocessed data (eNodeB CHR and MME

CHR) to the eSAU.
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nast
ar
Serv
er
eSA
U

eSAU.
Return
data
query
results
eSA
U
Nast
ar
Serv
er

4.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nast
ar
Serv
er
eSA
U

Upload
data
analysis
results
eSA
U
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for LTE Cell Performance Analysis

of analysis time.
NOTE
Issue 03 (2015-07-30)

3980
Nastar
Item
Item
Execution type
One-time task

analysis task
1,000 cells
Number of allowed
analysis tasks
50

one analysis task
7 days

task
10 minutes

7 days

15 days
NOTE
During in-depth analysis, the window of the complaint support analysis
is displayed. The data of the LTE complaint support analysis can be saved
for a maximum of seven days. When the data is saved for longer than
seven days, the xDR may fail to be displayed for in-depth analysis.
6.2.2 Preparations for LTE Cell Performance Analysis

Before starting an LTE cell performance analysis task, you must check the user rights and onsite
environment and prepare data. Read this section before performing an LTE cell performance
analysis.

For the LTE network, cell performance analysis is classified into LTE FDD cell performance
analysis and LTE TDD cell performance analysis. The two functions are independent from each
other.
l
The licenses and user rights required for LTE FDD cell performance analysis are as follows:
cell performance analysis, and the licenses are valid.
management authentication, LTE FDD cell performance analysis task operation right,
Check that you have the following operation rights of analysis task: LTE FDD cell
performance analysis task operation right, and the operation rights to operate the NE
groups that the analyzed NEs belong to.
Issue 03 (2015-07-30)

3981
Nastar
l
The licenses and user rights required for LTE TDD cell performance analysis are as follows:
Check that you have obtained the licenses for LTE TDD basic function and LTE TDD
cell performance analysis, and the licenses are valid.
management authentication, LTE TDD cell performance analysis task operation right,
Check that you have the following operation rights of analysis task: LTE TDD cell
performance analysis task operation right, and the operation rights to operate the NE
NOTE

Configuration data
The configuration data of NEs related to LTE cell performance analysis is used to obtain CHR
data from the network. The configuration data is also used to analyze cell information in related
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.
Data.
NOTE
To ensure the validity of configuration data, you are advised to perform LTE cell performance analyses on
a per day basis.
Issue 03 (2015-07-30)

3982
Nastar
Checking Onsite Environment

l
Check that the matching U2000/M2000 version is V200R013C00 (or later), the NE version
is BTS3900 V100R008C00SPC020 (or later), BTS3900 V100R008C01SPC200 (or later),
V100R010C10 (or later), or BTS3900 V100R011C00 (or later), and the MME on the CN
is provided by Huawei and the version is USN9810 V900R011C02 or later
NOTE
l If the MME on the CN is not provided by Huawei, you need to contact Huawei technical support
for the requirements, as stipulated in the 3GPP specifications, that the MME must meet in order
to interconnect to the eNodeB.
l For details about how to set the vendor type of the EPCs (MMEs) accessed by the Nastar, see
3.3.7 Setting the Vendor Type of EPCs (MMEs) (Optional).
Set the CHR reporting value. For details, see Commissioning the Function of Obtaining
the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(LTE) >
Setting the MME CHR Data Reporting Values (LTE) in the Nastar Commissioning
Guide(RH2288).
Check that the CHR transmission switch is enabled. For details, see Commissioning the
Obtaining Data(LTE) > Enabling the MME CHR Data Transmission Switch (LTE)
in the Nastar Commissioning Guide(RH2288).
6.2.3 Process of LTE Cell Performance Analysis

This section describes the process of LTE cell performance analysis and each procedure in the
process.
l
Prerequisites
Process
Prerequisites
LTE configuration data and LTE engineering parameters have been imported into the Nastar
database. For detailed operations, see 6.2.2 Preparations for LTE Cell Performance
Analysis.
Process
Issue 03 (2015-07-30)

3983
Nastar
Issue 03 (2015-07-30)

3984
Nastar
Table 6-4 Description of the LTE cell performance analysis process

No.
Procedure
Description
Reference
(1)
Check the
integrity of
analysis data
Navigation path: Choose

Maintenance > Data Maintenance
Management.
3.6 Checking
the Integrity of
Analysis Data
Steps:
1. Set Data Type to LTE Cell
4. Click Query.
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
(2)
LTE Periodic
MR Period
Setting

Maintenance > LTE Periodic MR
Period Setting
Procedure:
1. In the LTE Periodic MR Period
Setting window, set Periodic MR
Period, Number of Sampled Users
and Number of Times MRs Are
Reported.
For details about

parameters, see
LTE Periodic
MR Period
Setting
Parameters.
2. Click Configure.
Issue 03 (2015-07-30)

3985
Nastar
No.
Procedure
Description
Reference
Subscribe to
analysis data
(basic)
NOTE
The source data subscription function has
high security requirements. You are advised
to contact the administrator to turn on the data
source switch.
3.5 Subscribing
to Analysis Data

Maintenance > Data Subscription
Management.
Steps:
1. Click the LTE FDD or LTE TDD tab
in the Data Subscription
Management window.
2. Select the NEs to be configured in the
navigation tree.
3. Click Set on the Basic Subscription
Settings tab page.
Settings dialog box, set the data
source switch of Cell Performance
Analysis Data to ON.
By default, the data source switch is
set to No Modification.
5. Click Confirm.
Check the information in the Log
Info area and ensure that the data
source switch is turned on.
Subscribe to
analysis data
(application)

Maintenance > Data Subscription
Management.
Steps:
1. Click the LTE FDD or LTE TDD tab
in the displayed Data Subscription
Management window.
2. Select the NEs to be configured in the
navigation tree.
3. Click ON on the Cell Performance
Analysis tab page.
4. Set threshold parameters in the
displayed Cell Performance
Analysis Parameter Setting dialog
box.
5. Click Confirm.
For detailed description of the
parameters, see Subscription Task
Parameters.
Issue 03 (2015-07-30)

3986
Nastar
No.
Procedure
Description
Reference
Check the
integrity of
analysis data

Maintenance > Data Maintenance
Management.
3.6 Checking
the Integrity of
Analysis Data
Steps:
1. Set Data Type to LTE Cell
4. Click Query.
(3)
Create an
analysis task
Navigation path: Choose Theme

Function > Network Analysis > LTE
Cell Performance Analysis in the
navigation tree of the Analysis Task
Management window.
Steps:
1. Double-click LTE Cell
2. Specify the task name and remarks.
Then, click Next.
3. Select analysis type and the NEs to be
analyzed on the Select NE(s) tab
page. Select Analysis Type and NE
(s). Then, click Next.
l For detailed
operations,
see 3.7
Creating an
Analysis
Task.
l For detailed
description of
the
parameters,
see Analysis
Task
Parameters.
4. Specify the time period. After the

task is executed, the Nastar obtains
the analysis results for the specified
time period.
NOTE
To obtain accurate subscriber
information, you are advised to set
Execute on to 1 hour.
5. Click Finish.
NOTE
If the task result contains abnormal NEs
to be analyzed, a message is displayed
indicating that the task is successful.
Issue 03 (2015-07-30)

3987
Nastar
No.
Procedure
Description
Reference
(4)
View analysis
results

Task Result area, select a result record
of the task.
l For detailed
operations,
see 3.8
Querying
Analysis
Results.
Steps:
l For detailed
description of
the window
for showing
analysis
results, see
6.2.4
Interface
Description:
LTE Cell
Performanc
e Analysis.
1. Right-click the result record and

choose View Analysis Result from
the shortcut menu.
2. In the displayed LTE Cell
Performance Analysis window,
view the analysis results matching
the record.
View in-depth
analysis results
Navigation path: In the window for

showing analysis results, click the
icon.
Steps:
1. In the window for showing analysis
results, click the
icon.
2. View the analysis results in the

displayed Compliant Analysis
Support window.
NOTE
When you perform in-depth analysis on
an existing cell 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
Issue 03 (2015-07-30)

3988
Nastar
No.
Procedure
Description
Reference
(5)
Export analysis
results
Navigation path: Click the export icon

on the toolbar in the upper left area of the
LTE cell performance analysis window.
l For details,
see 3.10
Exporting
Analysis
Reports.
Steps:
2. Set the format and save path for
exporting file and set the counters and
scope for exporting data.
3. Click Save.
l For detailed
description of
the window
for showing
analysis
results, see
6.2.4
Interface
Description:
LTE Cell
Performanc
e Analysis.

Parameter
Description
Periodic MR
Period
Number of
Sampled Users

Nastar.
NOTE
Issue 03 (2015-07-30)

3989
Nastar
Parameter
Description
Number of
Times MRs
Are Reported


Basic Subscription
Issue 03 (2015-07-30)

3990
Nastar
Parameter
Description
Cell
Performance
Analysis Data
(CHR)
You can click
PERIOD INTRA FREQ MEASUREMENT, periodic intra-frequency
measurement
PERIOD UE MEASUREMENT, periodic user-defined measurement
measurement
measurement
measurement
measurement
CSFB PREP, CSFB
Issue 03 (2015-07-30)

3991
Nastar
Parameter
Description
multiple RRU cells
If PERIOD LOGGED MDT MEASUREMENT is contained in Trace
Event Block Type, click Select Idle State Measurement Object at the
lower left corner to select the idle object to be measured. The range of
selected objects is displayed in the Idle State Measurement Object
Range column on the Periodic Event Block Parameter Settings tab
page.
(ms), 2560(ms), 5120(ms), 10240(ms), 20480(ms), 30720(ms),
40960(ms), or 61440(ms).
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.
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).
objects to be measured. A maximum of 32 cells or eight TACs can be
selected.
NOTE
Issue 03 (2015-07-30)
Parameter
Description
Overlong RRC
Setup Delay(NonService)
Threshold for acceptable average delay when a subscriber initiates a

non-service RRC connection setup. An average delay is long if it reaches
or is above the threshold.

3992
Nastar
Parameter
Description
Overlong RRC
Setup Delay
(Service)
Threshold for acceptable average delay when a subscriber initiates a

service RRC connection setup. An average delay is long if it reaches or
is above the threshold.
Overlong E-RAB
Setup Delay
Threshold for acceptable average delay when a subscriber successfully

initiates an E-RAB setup after gaining access to the network. An average
delay is long if it reaches or is above the threshold.
Overlong interRAT Incoming

Handover Delay
Threshold for acceptable average delay when a subscriber performs an

incoming inter-RAT handover from a different network to the current
network. An average delay is long if it reaches or is above the threshold.
Overlong intraRAT Incoming

Handover Delay

incoming intra-RAT handover at the X2 or S1 interface. An average
Overlong interRAT Outgoing

Handover Delay

outgoing inter-RAT handover from the current network to a different
network. An average delay is long if it reaches or is above the threshold.
Overlong intraRAT Outgoing

Handover Delay

outgoing intra-RAT handover at the X2 or S1 interface. An average

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Issue 03 (2015-07-30)

3993
Nastar
Parameter
Description
Analysis Type
Select NE(s)

Network scale for one analysis task 1,000 cells
NOTE

Parameter
Description
Duration
Delay
immediately.
Execute on
6.2.4 Interface Description: LTE Cell Performance Analysis

This section describes the interface that displays the results of LTE cell performance analysis.
this interface.
Navigation Path
l
Use either of the following methods to open the interface that displays the results of LTE
Select a finished LTE cell performance analysis task and double-click a result record
Select a finished LTE cell performance analysis task, right-click a result record of the
Open the interface that displays the results of LTE cell performance analysis (in-depth):
, turn into the in-depth analysis
interface (that is complaint analysis support interface).
Issue 03 (2015-07-30)

3994
Nastar
Interface
exception types, table of exception causes, and table of bottomN users, terminal models, cells,
sector equipment or equipment group, TAC, SGW IP or MME. Figure 6-8 shows the analysis
result interface.
No.
Item
Description
Button area
: Export the results of exception aggregation during a cell

performance analysis task, namely, export the analysis results
of all cells under each exception type.
: Export the results of exception causes analysis during a

cell performance analysis task, namely, export the analysis
results of all cells under each exception cause.
: Export the results of the core network KPIs. namely,

export KPIs by cells and core network and by only core
network.
NOTE
The icon for exporting the results of the core network KPIs is
displayed only when you have the Internal Use Version Control
license and the license is valid.
Issue 03 (2015-07-30)

3995
Nastar
No.
Item
Description
NE navigation
tree
l Upper part: Type a cell name in the Search area to quickly

locate a cell.
l Lower part: Displays all abnormal NEs to be analyzed in this
task in a navigation tree. (N) after each node indicates the
number of times related to the exception causes.
Table of
exception types
Displays the number of reports and ratio under each exception

type for the selected eNodeB or cell under each service type. This
area is displayed accordingly with Area 4 and Area 5.
You can export and search this table by performing the save and
search operations: right-click on the table and choose Save As
from the shortcut menu to export this table.
Table of
exception causes
Displays the number of reports and ratio under each exception

cause of an exception type for the selected eNodeB or cell. This
area is displayed accordingly with Area 5.
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.
icon to open the
in-depth analysis interface where you can view all abnormal
call records under this exception cause.
Issue 03 (2015-07-30)

3996
Nastar
No.
Item
Description
Table of bottom
N users, bottom
N terminal
models, bottom
N cells, bottom N
peer cells
Displays the number of reports related to bottomN peer cells

(N<=50), bottomN users(N<=50), bottomN terminal models
(N<=50), bottomN TAC(N50), bottomN sector equipment or
equipment group(N50), bottomN MME(N50), bottomN
SGW IP(N50) or bottomN cells(N<=50) under an exception
cause for the selected eNodeB group or cell.
l After you select a group in Area 2, this table displays the
number and ratio of reports caused by bottomN users,
bottomN terminal models, bottomN TAC, bottomN MME,
bottomN SGW IP and bottomN cells.
and ratio of reports caused by bottomN peer cells, bottomN
users, bottomN TAC, bottomN sector equipment or
equipment group, bottomN MME, bottomN SGW IP and
terminal models.
NOTE
l After you select a cell in Area 2 and set the exception type to
Inter-RAT Outgoing HO Failure, Intra-RAT Outgoing HO
Failure, or Intra-RAT Incoming HO Failure, this table displays
the number and ratio of reports caused by bottomN peer cells.
l After you select a cell in Area 2 and set the exception type to RRC
Setup Failure (Non-Service), RRC Setup Failure (Service),
Intra-RAT Outgoing HO Failure (HoType-BASED), IntraRAT Outgoing HO Failure (HoItf-BASED)or E-RAB
Abnormal Release, this table displays the number and ratio of
reports caused by bottomN sector equipment or equipment group.
l After you set the exception type to RRC Setup Failure (NonService), RRC Setup Failuer (Service), RRC Reestablishment
triggered by HO, Overlong RRC Setup Delay (Non-Service),
or Overlong RRC Setup Delay (Service), this table does not
display the number of reports related to bottomN MMEs.
l After you set the exception type to GBR Service E-RAB Setup
failure, Non-GBR Service E-RAB Setup failure, GBR Service
E-RAB Abnormal Realease, Non-GBR Service E-RAB
Abnormal Realease, GBR Service Delay Problem, or NonGBR Service Delay Problem, this table displays the number and
ratio of reports caused by bottomN SGW IP.
l When the cell type is LampSite, BottomN Sector Equipment or
Equipment Group is BottomN Sector Equipment Group. When
other cell types is in use, BottomN Sector Equipment or
Equipment Group is BottomN Sector Equipment.
l Select a user, terminal, or cell and click the

icon to open
the in-depth analysis interface where you can view all
abnormal call records under this user, terminal, or cell.
Issue 03 (2015-07-30)

3997
Nastar
NOTE
Click the
based on problematic cells. For details about the interfaces, see Interface Description: LTE Complaint
Analysis Support.
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 indepth analysis. All in-depth analysis results generated before the in-depth analysis is stopped will be
properly displayed.
6.2.5 Parameters for Viewing LTE Cell Performance Analysis

Results
This section describes the parameters for viewing LTE cell performance analysis results. You
can refer to the description when viewing LTE cell performance analysis results.

Para
mete
r
Range
Unit
Description
Supp
orted
Solut
ion
Versi
on
Servi
ce
Type
N/A
N/A
Service type of a cell

exception. Type of a service.
Following are possible
service types:
eRA
N 6.0/
eRA
N 6.1/
eRA
N 7.0/
eRA
N 8.0/
eRA
N 8.1/
eRA
N11.0
l Network level
l GBR service
l Non-GBR service
Issue 03 (2015-07-30)

3998
Nastar
Para
mete
r
Range
Unit
Description
Supp
orted
Solut
ion
Versi
on
Exce
ption
Type
l When the service type is

"Network service", the
enumeration values are as
follows:
N/A
Analysis of exceptions by
two dimensions: the network
exception itself and the
subscriber's subjective
perception.
eRA
N 6.0/
eRA
N 6.1/
eRA
N 7.0/
eRA
N 8.0/
eRA
N 8.1/
eRA
N11.0
RRC Setup Failure (NonService)

RRC Setup Failure
(Service)
Inter-RAT Outgoing HO
Failure
For description of the

exception types, see
Description of NetworkLevel Exception Types.
Intra-RAT Outgoing HO
Failure (HoType-BASED)
Intra-RAT Outgoing HO
Failure (HoItf-BASED)
RRC Reestablishment
triggered by HO
Inter-RAT Incoming HO
Failure
Intra-RAT Incoming HO
Failure (HoItf-BASED)
Delay Problem
l When the service type is "GBR
service" or " Non-GBR
service", the enumeration
E-RAB Setup Failure
E-RAB Abnormal Release
Delay Problem
Issue 03 (2015-07-30)

3999
Nastar
Issue 03 (2015-07-30)
Para
mete
r
Range
Unit
Description
Supp
orted
Solut
ion
Versi
on
Exce
ption
Occu
rrenc
e
Time
s
[0,+)
Numb
er
Number of abnormal times

under a specific exception
type.
eRA
N 6.0/
eRA
N 6.1/
eRA
N 7.0/
eRA
N 8.0/
eRA
N 8.1/
eRA
N11.0
Rate
[0.00,100.00]
Proportion of abnormal
times under a specific
exception type in all the
abnormal times.
eRA
N 6.0/
eRA
N 6.1/
eRA
N 7.0/
eRA
N 8.0/
eRA
N 8.1/
eRA
N11.0

4000
Nastar
Description of Network-Level Exception Types
Issue 03 (2015-07-30)
Parame
ter
Range
Unit
Description
Support
ed
Solution
Version
RRC
Setup
Failure
(NonService)
N/A
N/A
Failure during the process from when a

terminal sends an RRC Connection Request
message until the non-service RRC
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11.
0
RRC
Setup
Failure
(Service
)
N/A
N/A
Failure during the process from when a

terminal sends an RRC Connection Request
message until the service RRC connection
setup is complete.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11.
0
InterRAT
Outgoin
g HO
Failure
N/A
N/A
Failed outgoing inter-RAT handover.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11.
0

4001
Nastar
Issue 03 (2015-07-30)
Parame
ter
Range
Unit
Description
Support
ed
Solution
Version
InterRAT
Incomin
g HO
Failure
N/A
N/A
Failed incoming inter-RAT handover.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11.
0
IntraRAT
Outgoin
g HO
Failure
(HoTyp
eBASED
)
N/A
N/A
Failed outgoing intra-RAT handover on the

intra-FREQ or inter-FREQ.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11.
0
IntraRAT
Outgoin
g HO
Failure
(HoItfBASED
)
N/A
N/A
Failed outgoing intra-RAT handover on the

inter-ENB, X2, or S1 interface.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11.
0

4002
Nastar
Parame
ter
Range
Unit
Description
Support
ed
Solution
Version
IntraRAT
Incomin
g HO
Failure
(HoItfBASED
)
N/A
N/A
Failed incoming intra-RAT handover on

the inter-ENB, X2, or S1 interface.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11.
0
RRC
Reestabl
ishment
triggere
d by HO
N/A
N/A
The following problems occurs when a

eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11.
0
Delay
Problem
N/A
l RRC Reestablishment success triggered

by HO
l RRC Reestablishment failure triggered
by HO
N/A
Any of the following delay problems that

might occur when a terminal attempts to
access the network:
Overlong delay for non-service RRC
connection setup
Overlong delay for service RRC
connection setup
Overlong delay for outgoing inter-RAT
handover
Overlong delay for outgoing intra-RAT
handover
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11.
0
Overlong delay for incoming inter-RAT

handover
Overlong delay for incoming intra-RAT
handover
The abnormal delay thresholds are set when
users subscribe to application data for LTE
cell performance analysis.
Issue 03 (2015-07-30)

4003
Nastar
Description of GBR Service/Non-GBR Service Exception Types
Issue 03 (2015-07-30)
Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
ERAB
Setup
Failu
re
N/A
N/A
Exception that occurs during the process

from the E-RAB setup starts until the E-RAB
setup is complete after a terminal gains
access to the network.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
ERAB
Abno
rmal
Relea
se
N/A
N/A
E-RAB release exception that occurs when

the QCI of the E-RAB indicates a GBR or
non-GBR service after a subscriber gains
access to the network and successfully
initiates a call.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Dela
y
Probl
em
N/A
N/A
Long E-RAB setup delay after a terminal

gains access to the network and successfully
sends an E-RAB Setup Request message.
Statistics on E-RAB setup delay are collected
based by GBR and Non-GBR, respectively.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0

4004
Nastar
Issue 03 (2015-07-30)
Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
Exce
ption
al
Caus
e
N/A
N/A
Detailed cause of exceptions under a specific

exception type.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Exce
ption
Occu
rrenc
e
Time
s
[0,+]
Number
Number of times that a specific cause of

certain exceptions is reported.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Rate
[0.00,100.
00]
Proportion of a cause against the number of

exceptions under the same exception type.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Indepth
Anal
ysis
N/A
N/A
This parameter is used to switch from the

analysis results of counters to the analysis
results of calls.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0

4005
Nastar
Description of Exception Causes
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
Resource
Allocation
Failure(NonService)
N/A
N/A
Number of non-service RRC setup

failures because resource allocation
fails.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
No UE
Responding
(Non-Service)
N/A
N/A
Number of non-service RRC setup

failures because the UE does not make
any response.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Resource
Allocation
Failure
(Service)
N/A
N/A
Number of service RRC setup failures

because resource allocation fails.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4006
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
No UE
Responding
(Service)
N/A
N/A
Number of service RRC setup failures

because the UE does not make any
response.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT
Intra-FREQ
outgoing HO
preparation
failure
N/A
N/A
Number of intra-RAT intra-FREQ

outgoing handover failures because of
the failure in the handover preparation
phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT
Inter-FREQ
outgoing HO
preparation
failure
N/A
N/A
Number of intra-RAT inter-FREQ

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4007
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
Intra-RAT
Intra-FREQ
outgoing HO
execution
failure
N/A
N/A
Number of intra-RAT intra-FREQ

the failure in the handover execution
phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT
Inter-FREQ
outgoing HO
execution
failure
N/A
N/A
Number of intra-RAT inter-FREQ

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT
Intra-ENB
outgoing HO
preparation
failure
N/A
N/A
Number of intra-RAT intra-ENB

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4008
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
Intra-RAT X2BASED
outgoing HO
preparation
failure
N/A
N/A
Number of intra-RAT X2-BASED

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT S1BASED
outgoing HO
preparation
failure
N/A
N/A
Number of intra-RAT S1-BASED

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT
Intra-ENB
outgoing HO
execution
failure
N/A
N/A

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4009
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
Intra-RAT X2BASED
outgoing HO
execution
failure
N/A
N/A

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT S1BASED
outgoing HO
execution
failure
N/A
N/A

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
RRC
Reestablishme
nt success
triggered by
HO
N/A
N/A
Number of RRC reestablishment

successes because of the handover.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
NOTE
When this indicator is analyzed using the
complaint analysis function, the complaint
analysis summary table does not contain
information about this indicator since this
function does not consider the indicator has
an exception. To view information about
this indicator, refer to the xDR
reestablishment information.

4010
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
RRC
Reestablishme
nt failure
triggered by
HO
N/A
N/A
Number of RRC reestablishment

failures because of the handover.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Inter-RAT
outgoing HO
preparation
failure
N/A
N/A
Number of inter-RAT outgoing

handover failures because of the failure
in the handover preparation phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Inter-RAT
outgoing HO
execution
failure
N/A
N/A
Number of inter-RAT outgoing

in the handover execution phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4011
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
Intra-RAT
Intra-ENB
incoming HO
preparation
failure
N/A
N/A

incoming handover failures because of
phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT X2BASED
incoming HO
preparation
failure
N/A
N/A

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT S1BASED
incoming HO
preparation
failure
N/A
N/A

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4012
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
Intra-RAT
Intra-ENB
incoming HO
execution
failure
N/A
N/A

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT X2BASED
incoming HO
execution
failure
N/A
N/A

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Intra-RAT S1BASED
incoming HO
execution
failure
N/A
N/A

phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4013
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
Inter-RAT
incoming HO
preparation
failure
N/A
N/A
Number of inter-RAT incoming

in the handover preparation phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Inter-RAT
incoming HO
execution
failure
N/A
N/A
Number of inter-RAT incoming

in the handover execution phase.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Overlong RRC
Setup Delay
(Non-Service)
N/A
N/A
Long setup delay of non-service RRC

connection.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4014
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
Overlong RRC
Setup Delay
(Service)
N/A
N/A
Long setup delay of service RRC

connection.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Overlong InterRAT Outgoing

Handover
Delay
N/A
N/A
Long delay of outgoing inter-RAT

handover.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Overlong IntraRAT Outgoing

Handover
Delay
N/A
N/A
Long delay of outgoing inter-RAT

handover on the X2 or S1 interface.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4015
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
Overlong InterRAT Incoming

Handover
Delay
N/A
N/A
Long delay of incoming inter-RAT

handover.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Overlong IntraRAT Incoming

Handover
Delay
N/A
N/A
Long delay of incoming inter-RAT

handover on the X2 or S1 interface.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
E-RAB
Abnormal
Release
Triggered by
MME
N/A
N/A
E-RAB abnormal releases triggered by

MME. The cause of the release is UE
CONTEXT RELEASE COMMAND,
E-RAB RELEASE COMMAND, and
so on.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4016
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
E-RAB
Abnormal
Release
Triggered by
eNodeB
N/A
N/A

eNodeB. The cause of the release is UE
CONTEXT RELEASE COMMAND,
E-RAB RELEASE COMMAND, and
so on.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
E-RAB
Abnormal
Release
Triggered by
Outgoing HO
Execution
Failure
N/A
N/A

outgoing handover execution failure.
The causes of the release are the same
as those of outgoing handover failures.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0
Overlong ERAB Setup

Delay
N/A
N/A
Long E-RAB setup delay after a

terminal gains access to the network and
successfully sends an E-RAB Setup
Request message.
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4017
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Suppor
ted
Solutio
n
Versio
n
E-RAB
abnormal
release
triggered by ERAB setup
failure in HO
Peer Cells
N/A
N/A

E-RAB setup failures in handover
target cells.
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN11
.0

4018
Nastar
BottomN Peer Cell

Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
Cell
Identi
ty
N/A
N/A
Identity of an abnormal bottom target cell. A

GSM cell is in the format of LAC:CI. A
UMTS cell is in the format of RNC ID:CELL
ID. An LTE cell is in the format of eNodeB
ID:Cell ID.
l IntraRAT
Outgoi
ng HO
Failure
and
InterRAT
Outgoi
ng HO
Failure
:
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
l IntraRAT
Incomi
ng HO
Failure
:
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
Issue 03 (2015-07-30)

4019
Nastar
Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
Cell
Nam
e
1 to 64
characters
N/A
Name of an abnormal bottom peer cell.
l IntraRAT
Outgoi
ng HO
Failure
and
InterRAT
Outgoi
ng HO
Failure
:
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
l IntraRAT
Incomi
ng HO
Failure
:
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
Issue 03 (2015-07-30)

4020
Nastar
Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
Exce
ption
Occu
rrenc
e
Time
s
[0,+]
Number
Number of the exceptions that occur due to

an exception cause of an exception type in a
service type in a bottom peer cell.
l IntraRAT
Outgoi
ng HO
Failure
and
InterRAT
Outgoi
ng HO
Failure
:
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
l IntraRAT
Incomi
ng HO
Failure
:
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
Issue 03 (2015-07-30)

4021
Nastar
Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
Rate
[0.00,100.
00]
Ratio of the exceptions to all exceptions.
l IntraRAT
Outgoi
ng HO
Failure
and
InterRAT
Outgoi
ng HO
Failure
:
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
l IntraRAT
Incomi
ng HO
Failure
:
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
Issue 03 (2015-07-30)

4022
Nastar
Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
Indepth
Anal
ysis
N/A
N/A

analysis results of counters to call detail
records
l IntraRAT
Outgoi
ng HO
Failure
and
InterRAT
Outgoi
ng HO
Failure
:
eRAN
6.0/
eRAN
6.1/
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
l IntraRAT
Incomi
ng HO
Failure
:
eRAN
7.0/
eRAN
8.0/
eRAN
8.1/
eRAN
11.0
Issue 03 (2015-07-30)

4023
Nastar
BottomN Cells
Issue 03 (2015-07-30)
Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
Cell
Identi
ty
N/A
N/A
The identity of a bottom problematic cell is

in the following format: eNodeB ID: Cell ID.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Cell
Nam
e
1 to 64
characters
N/A
Name of the bottom cell in which exceptions

occur. The Name of a bottom problematic
cell is in the following format: eNodeB
Name:Cell Name(eNodeB ID:Cell ID).
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Exce
ption
Occu
rrenc
e
Time
s
[0,+]
Number
Number of the exceptions that occur in a cell

under the cause of a certain type of exception.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Rate
[0.00,100.
00]
Proportion of the exceptions that occur in a

cell in all the exceptions.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Indepth
Anal
ysis
N/A
N/A

results of calls.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0

4024
Nastar
BottomN Users
Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
User
Name
N/A
N/A
Unique identifier that the system assigns to

each bottom user troubled with exceptions.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
NOTE
When the user name is IMSI or STMSI, the
STMSI information is displayed if the value of
Maintenance > EPC(MME) Vendor Setting of
the client is set to Non-interconnection;
otherwise, the IMSI information is displayed.
Issue 03 (2015-07-30)
Exce
ption
Occu
rrenc
e
Time
s
[0,+)
Number
Number of the exceptions that trouble a user

under the cause of a certain type of exception.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Rate
[0.00,100.
00]
Proportion of the exceptions that trouble a

user in all the exceptions.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Indepth
Anal
ysis
N/A
N/A

results of calls.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0

4025
Nastar
BottomN Terminal Models
Issue 03 (2015-07-30)
Para
mete
r
Range
Unit
Description
Support
ed
Solution
Version
IMEI
-TAC
00000000
-9999999
9
N/A
Type identifier of a bottom terminal troubled

with exceptions.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Term
inal
Mode
l
N/A
N/A
Terminal model that is obtained by using the

terminal type management function based on
IMEI-TAC.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Exce
ption
Occu
rrenc
e
Time
s
[0,+]
Number
Number of the exceptions that trouble a

certain type of terminal under the cause of a
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Rate
[0.00,100.
00]

terminal in all the exceptions.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Indepth
Anal
ysis
N/A
N/A

results of calls.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0

4026
Nastar
BottomN TAC
Issue 03 (2015-07-30)
Para
mete
r
Scope
Unit
Description
Support
ed
Solution
Version
TAC
N/A
N/A
Tracking area code.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Exce
ption
Occu
rrenc
e
Time
s
[0,+]
Number

certain type of TAC under the cause of a
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Rate
(%)
[0.00,100.
00]

eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Indepth
Anal
ysis
N/A
N/A

results of calls.
eRAN
6.0/eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0

4027
Nastar
BottomN MME
Para
mete
r
Scope
Unit
Description
Support
ed
Solution
Version
MM
E
N/A
N/A
Identifier that consists of MMEGroupID and

MMECode.
eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Exce
ption
Occu
rrenc
e
Time
s
[0,+]
Number

certain type of MME under the cause of a
eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
Rate
(%)
[0.00,100.
00]

eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
NOTE
When the RRC connection request messages are
being processed, the MME information is not
identified. As a result, when the exception type is
Overlong RRC Setup Delay, the exception data
does not contain information about BottomN
MMEs. When you set the exception cause for
Delay Problem to ALL, the exception ratio of the
BottomN MMEs is calculated based on the
number of exceptions for which the exception
cause is ALL. Therefore, the sum of exception
ratios of the BottomN MMEs may be less than
100%.
Indepth
Anal
ysis
Issue 03 (2015-07-30)
N/A
N/A

results of calls.

eRAN
6.1/eRAN
7.0/eRAN
8.0/eRAN
8.1/
eRAN11.
0
4028
Nastar
BottomN Sector Equipment or Equipment group
Issue 03 (2015-07-30)
Para
mete
r
Scope
Unit
Description
Support
ed
Solution
Version
Secto
r
Equi
pmen
t
Identi
ty or
Equi
pmen
t
Grou
p
Identi
ty
N/A
N/A
This parameter consists of an eNodeB ID,

Local cell ID, and sector equipment ID and
indicates the information about the sector
equipment or equipment group in the SFN
cell.
eRAN
8.0/eRAN
8.1/
eRAN11.
0
Exce
ption
Occu
rrenc
e
Time
s
[0,+]
Times
This parameter indicates the number of

exceptions occurred on the bottom sector
equipment or equipment group under the
cause of a certain type of exception.
eRAN
8.0/eRAN
8.1/
eRAN11.
0
Rate
(%)
[0.00,100.
00]

sector equipment or equipment group in all
the exceptions.
eRAN
8.0/eRAN
8.1/
eRAN11.
0
Indepth
Anal
ysis
N/A
N/A

results of calls.
eRAN
8.0/eRAN
8.1/
eRAN11.
0

4029
Nastar
BottomN SGW IP
Para
mete
r
Scope
Unit
Description
Support
ed
Solution
Version
SGW
IP
Displayin
g example
of IPV4:
10.22.33.
44
N/A
Transport Layer IP.
eRAN 7.0
SPC800/
eRAN
8.0/eRAN
8.1/
eRAN11.
0
Displayin
g example
of IPV6:
fe80:981c
:981c:
237:fd93:
4dea:fd93
:4dea
Exce
ption
Occu
rrenc
e
Time
s
[0,+]
Times

certain type of SGW under the cause of a
eRAN 7.0
SPC800/
eRAN
8.0/eRAN
8.1/
eRAN11.
0
Rate
(%)
[0.00,100.
00]

SGW in all the exceptions.
eRAN 7.0
SPC800/
eRAN
8.0/eRAN
8.1/
eRAN11.
0
Indepth
Anal
ysis
N/A
N/A

results of calls.
eRAN 7.0
SPC800/
eRAN
8.0/eRAN
8.1/
eRAN11.
0
6.3 LTE Terminal Analysis

The LTE terminal analysis function enables the Nastar to analyze KPIs based on the call records
of subscribers. It helps operators identify the terminals with poor performance so that the
Issue 03 (2015-07-30)

4030
Nastar
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.
6.3.1 Basics of LTE Terminal Analysis

This section describes the functions, technical specifications, and feature limitations of LTE
terminal analysis. Read this section before performing an LTE terminal analysis.
NOTE
Functions of LTE Terminal Analysis

This section describes the LTE terminal analysis function provided by the Nastar. The function
enables users to analyze the call records of all subscribers under the selected NEs and then obtain
the related KPIs. It helps operators identify the terminals with poor performance so that the
subscriber satisfaction.
The call records of subscribers reflect the access performance, service retainability, and mobility
of their terminals. The LTE terminal analysis function provided by the Nastar enables users to
analyze terminal performance, subscriber behaviors, and network problems from the
perspectives of penetration rate, capability, and performance.
l
Terminal market share analysis: This analysis enables users to collect statistics on the
distribution of terminals on the existing network from dimensions, such as terminal vendor
and terminal type, and then provide guidance for future network deployment and marketing
strategies.
Terminal capability analysis: This analysis enables users to calculate the number of
terminals with a specific capability on a network and then provide basis for operators to
deploy networks that support terminals with such a capability.
Terminal performance analysis: This analysis enables users to identify certain types of
terminal that impose large signaling load on the network and then provide solution to
signaling storm. It also enables users to aggregate cell- and bearer-level KPIs. By
aggregating cell-level KPIs, the users can perform joint analyses on the query results and
the actual conditions of cells, and then determine whether the poor performance of terminals
are caused by the defects of the terminals themselves or by the impacts from certain cells.
By aggregating bearer-level KPIs, the users can perform joint analyses on the query results
and the services, and then determine which service is not supported enough due to certain
defects of the terminals on the existing network.
Issue 03 (2015-07-30)

4031
Nastar
Function Principles
The Nastar uses the eNodeB CHR data and MME CHR data from NEs for LTE terminal analysis.
The MME CHR data provides the IMEI information.
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U


4032
Nastar
User
Operat
ion
2.
Subscri
be to
applicat
ion data
Issue 03 (2015-07-30)
Proced
ure
Sou
rce
Dest
inati
on
Purpose
Issue a
subscrip
tion
comma
nd
eSA
U
U20
00/
M20
00

M2000.
Forward
the
subscrip
tion
comma
nd
U20
00/
M20
00
eNod
eB

Upload
raw data
(eNode
B CHR)
eNo
deB
Trac
e
Serv
er

Server.
Upload
raw data
(MME
CHR)
MM
E
LTE
SAU
To upload the raw data (MME CHR) to the LTE SAU

directly.
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U

Deliver
a
preproc
essing
task
(direct)
eSA
U
LTE
SAU

task.
Collect
data
(eNode
B CHR)
(direct)
LTE
SA
U
Trac
e
Serv
er

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

4033
Nastar
User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Purpose
Trac
e
Serv
er
LTE
SAU

Upload
preproc
essed
data
(direct)
LTE
SA
U
eSA
U
To upload preprocessed data (eNodeB CHR and MME

CHR) to the eSAU.
3.
Check
the
integrit
y of
analysi
s data
Issue a
data
query
comma
nd
Nast
ar
Serv
er
eSA
U

eSAU.
Return
data
query
results
eSA
U
Nast
ar
Serv
er

4.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nast
ar
Serv
er
eSA
U

Upload
data
analysis
results
eSA
U
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for LTE Terminal Analysis

of analysis time.
Issue 03 (2015-07-30)

4034
Nastar
NOTE
Item
Execution type
One-time task

analysis task
6000 cells
Number of allowed
analysis tasks
50

one analysis task
7 days

task
30 minutes

15 days

15 days
6.3.2 Preparations for LTE Terminal Analysis

Before starting an LTE terminal analysis, you must check the user rights and version mapping
and prepare relevant data. Read this section before performing an LTE terminal analysis.

For the LTE network, cell performance analysis is classified into LTE FDD terminal analysis
and LTE TDD terminal analysis. The two functions are independent from each other.
l
The licenses and user rights required for LTE FDD terminal analysis are as follows:
terminal analysis, and the licenses are valid.
management authentication, LTE FDD terminal analysis task operation right, and the
Check that you have the following operation rights of analysis task: LTE FDD terminal
analysis task operation right, and the operation rights to operate the NE groups that the
l
Issue 03 (2015-07-30)
The licenses and user rights required for LTE TDD terminal analysis are as follows:
4035
Nastar
terminal analysis, and the licenses are valid.
management authentication,LTE TDD terminal analysis task operation right, and the
Check that you have the following operation rights of analysis task: LTE TDD terminal
analysis task operation right, and the operation rights to operate the NE groups that the
NOTE

Terminal Information
This includes information, such as the IMEI-TAC, vendor, terminal type, terminal model, chip
model, and terminal technology. After creating the terminal information as required, the Nastar
creates management records for terminals to facilitate follow-up analyses on the terminals.
Configuration Data
NE configuration data in the analysis area allows users to correctly obtain the performance data
of subscribers whose proposed complaints from the network and analyze the cell information in
related measurements 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
will be handed over.
Issue 03 (2015-07-30)

4036
Nastar
Data.
NOTE
To ensure the validity of the configuration data, you are advised to perform terminal analyses on a per day
basis.
Checking Version Mapping

l
V100R010C10 (or later), or BTS3900 V100R011C00 (or later), and the MME on the CN
is provided by Huawei and the version is USN9810 V900R011C02 or later
NOTE
l If the MME on the CN is not provided by Huawei, you need to contact Huawei technical support
for the requirements, as stipulated in the 3GPP specifications, that the MME must meet in order
to interconnect to the eNodeB.
l For details about how to set the vendor type of the EPCs (MMEs) accessed by the Nastar, see
3.3.7 Setting the Vendor Type of EPCs (MMEs) (Optional).
Set the CHR reporting value. For details, see Commissioning the Function of Obtaining
the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(LTE) >
Setting the MME CHR Data Reporting Values (LTE) in the Nastar Commissioning
Guide(RH2288).
Check that the CHR transmission switch is enabled. For details, see Commissioning the
Obtaining Data(LTE) > Enabling the MME CHR Data Transmission Switch (LTE)
in the Nastar Commissioning Guide(RH2288).
Check that the IMEI switch is enabled. For details, see Commissioning the Function of
(LTE) > Checking and Turning on the IMEI Switch at the CN (LTE) in the Nastar
Commissioning Guide(RH2288).
6.3.3 Process of LTE Terminal Analysis

This section describes the process of LTE terminal analysis and the procedures in the process.
l
Prerequisites
Process
Prerequisites
The LTE configuration data and LTE engineering parameters have been imported into the Nastar
database. The NE groups have been created. The terminal type has been configured. For detailed
operations, see 6.3.2 Preparations for LTE Terminal Analysis.
Issue 03 (2015-07-30)

4037
Nastar
Process
Issue 03 (2015-07-30)

4038
Nastar
Table 6-6 Description of the LTE terminal analysis process

N
o.
Procedure
Description
Reference
(1)
Check
whether
analysis
data is
integrated?

3.6 Checking
the Integrity of
Analysis Data
Procedure:
1. Set Data Type to LTE FDD Terminal Analysis
Data or LTE TDD Terminal Analysis Data.
4. Click Query.
of the window.
analysis task.
performing (2).
NOTE
(2)
LTE
Periodic
MR Period
Setting

Procedure:
window, set Periodic MR Period, Number of
Sampled Users and Number of Times MRs Are
Reported.
For details about

parameters, see
LTE Periodic
MR Period
Setting
Parameters
2. Click Configure.
Issue 03 (2015-07-30)

4039
Nastar
N
o.
Procedure
Description
Reference
Subscribe
to analysis
data
(basic).

3.5.2 Basic
Subscription of
Analysis Data
Procedure:
click the LTE FDD or LTE TDD tab.
navigation tree.
click Set.
4. In the Basic Subscription Settings dialog box,
set the switch of Terminal Analysis Data to
ON.
5. Click Confirm.
Info area.
Subscribe
to analysis
data
(applicatio
n).

Procedure:
click the LTE FDD or LTE TDD tab.
navigation tree.
4. In the Terminal Analysis Parameter Setting
dialog box, set the threshold value for exceptions.
Task Parameters.
5. Click Confirm.
Verify that data subscription is successfully
turned on by viewing information displayed in the
Log Info area.
Issue 03 (2015-07-30)

4040
Nastar
N
o.
Procedure
Description
Reference
Check
whether
analysis
data is
integrated?

3.6 Checking
the Integrity of
Analysis Data
Procedure:
1. Set Data Type to LTE FDD Terminal Analysis
Data or LTE TDD Terminal Analysis Data.
4. Click Query.
of the window.
analysis task.
(3)
Create an
analysis
task.

Theme Function > Terminal Analysis > LTE
Terminal Analysis.
3.7 Creating an
Analysis Task
Procedure: :
1. Double-click LTE Terminal Analysis.
3. On the Select NE(s) tab page, specify the analysis
type and the NEs that you want to analyze. You
can select NEs by eNodeB or Cell Group.
4. Click Next.
5. Select an analysis time period. The Nastar then
obtains analysis data based on the selected time
period.
NOTE
6. Click Finish.
For details about the parameter settings, see
NOTE
If the time at which the data of an eNodeB is configured
is later than the time of the theme data, the information
about the eNodeB and its cell is not displayed on the
Issue 03 (2015-07-30)

4041
Nastar
N
o.
Procedure
Description
Reference
(4)
View
analysis
results.

task.
l For details,
see 3.8
Querying
Analysis
Results.
Procedure:
l For details
about the
description of
2. The results of the LTE terminal analysis task are
the window
displayed in the LTE Terminal Analysis
for showing
window.
analysis
results, see
6.3.4
Interface
Description:
LTE
Terminal
Analysis.
(5)
Export
analysis
reports.

Procedure:
3. Click Save.
l For details,
see 3.10
Exporting
Analysis
Reports.
l For details
about the
description of
the window
for showing
analysis
results, see
6.3.4
Interface
Description:
LTE
Terminal
Analysis.
Issue 03 (2015-07-30)
Parameter
Description
Periodic MR
Period

4042
Nastar
Parameter
Description
Number of
Sampled Users

Nastar.
NOTE
Number of
Times MRs
Are Reported


Basic Subscription
Issue 03 (2015-07-30)

4043
Nastar
Parameter
Description
Terminal
Analysis Data
(CHR)
You can click
measurement
measurement
measurement
measurement
measurement
CSFB PREP, CSFB
multiple RRU cells
Issue 03 (2015-07-30)

4044
Nastar
Parameter
Description
If PERIOD LOGGED MDT MEASUREMENT is contained in Trace
Event Block Type, click Select Idle State Measurement Object at the
lower left corner to select the idle object to be measured. The range of
selected objects is displayed in the Idle State Measurement Object
Range column on the Periodic Event Block Parameter Settings tab
page.
(ms), 2560(ms), 5120(ms), 10240(ms), 20480(ms), 30720(ms),
40960(ms), or 61440(ms).
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.
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).
objects to be measured. A maximum of 32 cells or eight TACs can be
selected.
NOTE
Issue 03 (2015-07-30)

4045
Nastar
Parameter
Description
Overlong RRC
Setup Delay
Threshold
(Non-Service)
(s)
Threshold indicating that the duration for RRC connection setup is

exceedingly long when a terminal sends an RRC Connection Setup Request
message due to mo-Signaling.
The duration for RRC connection setup spans from the time when the
terminal sends an RRC Connection Setup Request message to the time
when the terminal sends an RRC Connection Setup Complete message.
Value range: [0,100000]
Overlong RRC
Setup Delay
Threshold
(Service)(s)
Threshold indicating that the duration for RRC connection setup is

exceedingly long when a terminal sends an RRC Connection Setup Request
message due to emergency, highPriorityAccess, mt-Access, or mo-Data.
The duration for RRC connection setup spans from the time when the
terminal sends an RRC Connection Setup Request message to the time
when the terminal sends an RRC Connection Setup Complete message.
Overlong ERAB Setup

Delay
Threshold(s)
The duration for E-RAB setup spans from the time when a terminal sends
an Initial Context Setup Request message to the time when the terminal
receives an Initial Context Setup Response message.
It can also refer to the time when a terminal sends an E-RAB Setup Request
message to the time when the terminal receives an E-RAB Setup Response
message.
Issue 03 (2015-07-30)
Overlong InterSystem
Outgoing
Handover
Delay
Threshold(s)
Threshold indicating that the duration for a terminal to perform inter-RAT

handovers from LTE to GSM, UMTS, CDMA2000, or TD-SCDMA is
exceedingly long.
Overlong InterSystem
Incoming
Handover
Delay
Threshold(s)
Threshold indicating that the duration for a terminal to perform inter-RAT

handovers from GSM, UMTS, CDMA2000, or TD-SCDMA to LTE is
exceedingly long.
Overlong IntraSystem
Outgoing
Handover
Delay
Threshold(s)
Threshold indicating that the duration at the X2 or S1 interface for a

terminal to perform handovers within the LTE system is exceedingly long.

4046
Nastar
Parameter
Description
Overlong IntraSystem
Incoming
Handover
Delay
Threshold(s)
Threshold indicating that the duration at the X2 or S1 interface for a

terminal to perform handovers within the LTE system is exceedingly long.

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

NE information
Parameter
Description
Analysis Type
Select NE(s)

Network scale for one analysis task 6000 cells
NOTE
Issue 03 (2015-07-30)

4047
Nastar
Parameter
Description
GBR
Guaranteed bit rate. When the QoS Class Identifier (QCI) indicates a value
ranging from 1 to 4, the bearer is a GBR bearer,
and the network reserves a minimum amount of bandwidth for the bearer.
Therefore, the minimum forwarding bit rate is guaranteed even when
network resources are insufficient. After the GBR bearer releases radio
links, the terminal and the mobility management entity (MME) remove the
information about the bearer. GBR bearer must be set up again when
necessary.
Non-GBR
Non-guaranteed bit rate. When the QCI indicates a value ranging from 5
to 9, the bearer is a non-GBR bearer,
and the network does not reserve a minimum amount of bandwidth for the
bearer. After the non-GBR bearer releases radio links, the terminal and the
MME save the information about the bearer. In this way, the bearer can be
reconnected once the radio links are restored.

Parameter
Description
Duration
Delay
immediately.
Execute on
6.3.4 Interface Description: LTE Terminal Analysis

This section describes the result window of LTE terminal analysis, including functions of each
area in the window, helping you perform related operations.
Opening the Window

You can enter the result window for LTE terminal analysis using either of the following methods:
l
Select a LTE terminal analysis task in the complete state. Then, in the displayed Task
Result area, double-click the results of this task.
Select a LTE terminal analysis task in the complete state. Then, in the displayed Task
Result area, right-click a result of this task and choose View Analysis Result from the
shortcut menu.
Issue 03 (2015-07-30)

4048
Nastar
Main Window
Figure 6-11 shows the terminal analysis results.
Figure 6-11 Terminal analysis window
No.
Name
Description
Analysis result
tab page
Analysis results are displayed in the form of tab page.

occupation of terminals on the live network by different
Description: Terminal Market Share Analysis.
of different terminal capabilities supported by the terminals
on the live network. For detailed operations, see Interface
Description: Terminal Ability Analysis.
performance counters of one type of terminals in a cell and
of a specific bearer type. For detailed operations, see
Interface Description: Terminal Performance Analysis.
Interface Description: Terminal Market Share Analysis

The terminal market share analysis result displays the occupation of the terminals of different
dimensions on the live network in the form of a chart and a table. Figure 6-12 shows the tab
page.
Issue 03 (2015-07-30)

4049
Nastar
Figure 6-12 Terminal market share interface
No.
Item
Description
Icons and
analysis
options


objects.
2
Statistics chart

Statistics table

supported:
Interface Description: Terminal Ability Analysis

The terminal ability analysis result displays the occupation of different abilities supported by
the terminals in the form of a histogram and a table. Figure 6-13 shows the tab page.
Issue 03 (2015-07-30)

4050
Nastar
Figure 6-13 Terminal ability evaluation
No.
Name
Icon area
NE object
navigation tree
Terminal ability
list
Selects the terminal ability to be analyzed. If you select one or more

terminal abilities, the analysis results of the ability are displayed
in both the chart area and table area on the right.
Description
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.
Supports the selection of analyzed objects from three different

dimensions: by the whole network, by a single eNodeB, or by a
single cell.
NOTE
A lot of UEs do not report the capability of supporting UTRANs. In RAT
statistics,The UE capability of supporting UTRANs may be lower than the
actual capability.
Chart area

ability in an NE object and the proportion of the terminals that do
not support a certain terminal ability in an NE object are displayed
in the form of a histogram. The histogram is mapped to the table
on the right.
The analysis results of a maximum of two types of terminal abilities
can be displayed at the same time. You can view the analysis results
of other terminal abilities by using the scroll bar.
Issue 03 (2015-07-30)

4051
Nastar
No.
Name
Description
Table area
The number and occupation of the terminals that support a certain

terminal ability in an NE object is displayed in the form of a table.
NOTE
Due to the use of knockoff phones or due to the limited success rate of
combining the wireless data with the CN data, the number of UEs that
support a capability and UEs that do not support the capability in the UE
capability analysis is slightly different from the number of UEs that trigger
RRC access.
The following shortcut menus by right-clicking are supported:

For details about parameters, see 6.3.5 Parameters for Viewing
LTE Terminal Analysis Results.

The terminal performance analysis table displays the terminal performance indicator, and the
Issue 03 (2015-07-30)

4052
Nastar
No.
Name
Description
Analysis
indicator
navigation tree
l The Aggregation Type drop-down list is used to select an

aggravation dimension.
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
displayed only when you select IMEI-TAC.

analyzed. The KPIs are also displayed in the area on the right.
2
Aggregation
table of the
terminal
performance
indicators

to the terminals based on the selected dimension.
the selected KPI.
displayed.
You can right-click in the table in area 2, The following shortcut
menus by right-clicking are supported:
l Save all as, which is used to save contents in the table. and
the system saves the displayed TopN results and all the other
results that are not displayed to your local computer.
Issue 03 (2015-07-30)

4053
Nastar
No.
Name
Description
Aggregation
table of the celllevel and
bearer-level
terminal
performance
indicators
l Analyze by Cell tab: Displays the performance indicator

value of a certain type of NE in area 2 in each cell.
l Analyze by Bearer tab: Displays the performance indicator
value of a certain type of NE in area 2 in each bearer.
the selected KPI.
l You can click displayalldata to display all analysis results
in area 3.
local computer.
For details about parameters, see 6.3.5 Parameters for Viewing
LTE Terminal Analysis Results.
6.3.5 Parameters for Viewing LTE Terminal Analysis Results

This section describes the parameters for viewing LTE terminal analysis results, You can refer
to the description when viewing LTE terminal analysis results.
Issue 03 (2015-07-30)

4054
Nastar
Basic Terminal Information
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
IMEI-TAC
Eight digits
N/A
Indicates the
combination of
the type
approval code
(TAC) and the
final assembly
code (FAC) in
an International
Mobile
Equipment
Identity (IMEI).
An IMEI
consists of 15
digits and
uniquely
identifies a
terminal in the
world. In an
IMEI, the TAC
refers to the first
six digits, and
the FAC refers
to the seventh
and eighth
digits. The
combination of
TAC and FAC
uniquely
identifies a
terminal.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Vendor
[1,256]
N/A
Indicates the
terminal vendor,
for example,
Nokia and
Apple.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Model
[1,256]
N/A
Indicates the
terminal model,
for example,
iPhone4.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4055
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Type
N/A
N/A
Indicates the
terminal type,
for example,
common
terminal,
intelligent
terminal, and
data card.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Chip Model
[0,256]
N/A
Indicates the
terminal chip
model.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Technology
N/A
N/A
Indicates the
RAT that the
terminal
supports, for
example, GSM
and WCDMA.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Terminals
[1,+)
Number
Indicates the
number of
terminals of this
type within the
statistical range.
If the statistics
are collected
parameter
indicates the
number of
terminals with
different IMEIs.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Terminal Ratio
[0,100]
Proportion of
terminals of a
specified type in
all terminals.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4056
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RAT
N/A
N/A
Number and
percentage of
the terminals
that support
specific radio
access systems,
including EUTRAN,
UTRAN,
GERAN CS,
GERAN PS,
and
CDMA2000-1
XRTT, within a
cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4057
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Multiple Modes
N/A
N/A
Number and
percentage of
the terminals
that support
GERAN/
UTRAN dualmode, UTRAN/
E-UTRAN
dual-mode,
GERAN/EUTRAN dualmode, and
GERAN/
UTRAN/EUTRAN multimode, within a
cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
NOTE
In the statistics
collected from
an LTE network,
the terminals
that support
GERAN/
UTRAN dualmode also
support EUTRAN.
Therefore, in
multi-mode
analysis, the
number of
terminals that
support
GERAN/
UTRAN dual
mode is the same
as the number of
terminals that
support
GERAN/
UTRAN/EUTRAN multimode.
Issue 03 (2015-07-30)

4058
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Protocol
Version
N/A
N/A
Number and
percentage of
the terminals
that support the
R8/R9/R10
protocol, within
a cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Handover to the
GERAN PS
Domain
N/A
N/A
Number and
percentage of
the terminals
that support
handovers to the
GERAN PS
domain, within
a cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-frequency
Measurement
N/A
N/A
Number and
percentage of
the terminals
that support
inter-frequency
measurements,
within a cell or
eNodeB or over
the E-UTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Measurement
N/A
N/A
Number and
percentage of
the terminals
that support
inter-RAT
measurements
on UTRAN,
GERAN,
CDMA2000HRPD, and
CDMA2000-1
XRTT, within a
cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4059
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-frequency
Handover
N/A
N/A
Number and
percentage of
the terminals
that support
inter-frequency
handovers,
within a cell or
eNodeB or over
the E-UTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Handover
N/A
N/A
Number and
percentage of
the terminals
that support
inter-RAT
handovers,
within a cell or
eNodeB or over
the E-UTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-frequency/
Inter-frequency/
Inter-RAT ANR
Measurement
N/A
N/A
Number and
percentage of
the terminals
that support
intra- and interfrequency ANR
measurements
and inter-RAT
ANR
measurements,
within a cell or
eNodeB or over
the E-UTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
LTE FDD/TDD
Handover
N/A
N/A
Number and
percentage of
the terminals
that support
LTE FDD/TDD
handovers,
within a cell or
eNodeB or over
the E-UTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4060
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
MIMO
N/A
N/A
Number and
percentage of
the terminals
that support
FDD TM7,
FDD/TDD
TM8, TM9 and
triggering RNC
access, within a
cell or eNodeB
or over the EUTRAN.
eRAN 8.0/
eRAN 8.1
SRVCC
N/A
N/A
Number and
percentage of
the terminals
that support
handover from
SRVCC to GSM
and from
SRVCC to
UMTS, within a
cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
CSFB
N/A
N/A
Number and
percentage of
the terminals
that support
CSFB, within a
cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
NOTE
The statistics are
collected based
on operations on
terminals. If
CSFB events
occur on a
terminal, the
terminal is
considered to
support CSFB.
Issue 03 (2015-07-30)

4061
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
LTE
Redirection
N/A
N/A
Number and
percentage of
the terminals
that support
LTE redirection
to UMTS or
GSM, within a
cell or eNodeB
or over the EUTRAN.
l LTE
Redirection
to UMTS:
eRAN 8.0/
eRAN 8.1
l LTE
Redirection
to GSM:
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1
LTE Frequency
Band
N/A
N/A
Number and
percentage of
the terminals
that support
various LTE
frequency
bands, within a
cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
GSM
Frequency Band
N/A
N/A
Number and
percentage of
the terminals
that support
various GSM
frequency
bands, within a
cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UMTS
Frequency Band
N/A
N/A
Number and
percentage of
the terminals
that support
various UMTS
frequency
bands, within a
cell or eNodeB
or over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4062
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
CA
N/A
N/A
Number and
percentage of
the terminals
that support
uplink CA
bandwidth
levels of various
frequency
bands, within a
cell or eNodeB
or over the EUTRAN.
eRAN 8.0/
eRAN 8.1
TM9 Capability
Distribution
N/A
N/A
Number and
percentage of
the terminals
that support
uplink or
downlink TM9
transmission
capability
distribution of
various
frequency
bands, within a
cell or eNodeB
or over the EUTRAN.
eRAN 8.0/
eRAN 8.1
Wi-Fi
N/A
N/A
Number and
percentage of
the terminals
that support WiFi, within a cell
or eNodeB or
over the EUTRAN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4063
Nastar
Performance Analysis Summary-Accessibility Evaluation
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
[0,+)
Number
Number of
times that the
cause values
carried in the
RRC
connection
setup requests
initiated by a
specified type of
terminal is MoSignalling and,
at the same time,
no service
requests are
initiated.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Setup
Requests
(Service)
[0,+)
Number
Number of
times that the
cause values
carried in the
RRC
connection
setup requests
initiated by a
specified type of
terminal is not
Mo-Signalling,
or the number of
times that the
cause values
carried in the
RRC
connection
setup requests
initiated by a
specified type of
terminal is MoSignalling and,
at the same time,
service requests
are initiated.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4064
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Reestablishment
Requests
[0,+)
Number
Number of
PRIVATE_RR
C_REEST
messages.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Number
Times when
ucResult is not
RRC_REEST_
CMP
(successful) and
is smaller than
the number of
PRIVATE_RR
C_REEST
messages.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Success Rate
[0,100]
(1 - Number of
RRC reestablishment
failures/
Number of RRC
reestablishment
requests) x
100%
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Requests
[0,+)
Number
Number of the
E-RAB Setup
Request
messages or
Internal Context
Setup Request
messages that a
terminal sends
(E-RAB is short
for evolved
radio access
bearer).
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4065
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Failures
[0,+)
Number
Number of the
E-RAB Setup
Responses or
Initial Context
Setup Response
messages that a
terminal
receives from
the related
eNodeB after
sending E-RAB
Setup Request
or Initial
Context Setup
Request
messages.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Rate
[0,100]
E-RAB setup
success rate =
Number of
successful ERAB setups/
Number of ERAB Setup
Request
messages
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Performance Analysis Summary-Retainability Evaluation
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Abnormal ERAB Releases
[0,+)
Number
Number of
due to E-RAB
exceptions,
among
successful ERAB
connection
setups
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4066
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Rate of
Abnormal ERAB Releases
[0,100]
Proportion of
due to E-RAB
exceptions
against
successful ERAB
connection
setups.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Performance Analysis Summary-Mobility Evaluation
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Execution
Request Times
[0,+)
Number
Number of
times the
preparation for
an outgoing
intra- or interfrequency
handover on the
LTE network
succeeds when
the eNodeB
receives the
RRC
Connection
Setup message
or when the UE
is handed over
to the eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4067
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Execution
Failures
[0,+)
Number
Number of
times the
preparation for
an outgoing
handover on an
LTE network
succeeds but the
handover fails
when the
eNodeB
receives the
RRC
Connection
Setup message
or when the UE
is handed over
to the eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Execution
Success Rate
[0,100]
Outgoing intraRAT handover

success rate
during the same
call process =
(Number of
outgoing intraRAT handovers
- Number of
failed outgoing
intra-RAT
handovers)/
Number of
outgoing intraRAT handover
requests
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4068
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Execution
Request Times
[0,+)
Number
Number of
times the
preparation for
an outgoing
handover from
LTE to GSM,
UMTS,
CDMA2000, or
TD-SCDMA
succeeds when
the eNodeB
receives the
RRC
Connection
Setup message
or when the UE
is handed over
to the eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Execution
Failures
[0,+)
Number
Number of
times the
preparation for
an outgoing
handover from
LTE to GSM,
UMTS,
CDMA2000, or
TD-SCDMA
succeeds but the
handover fails
when the
eNodeB
receives the
RRC
Connection
Setup message
or when the UE
is handed over
to the eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4069
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Execution
Success Rate
[0,100]
Inter-RAT
outgoing
handover
success rate
from LTE to
GSM, UMTS,
CDMA2000, or
TD-SCDMA
during the same
call process =
(Number of
inter-RAT
outgoing
handover
requests Number of
handover
requests)/
Number of
inter-RAT
outgoing
handover
requests
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Incoming
Handover
Execution
Request Times
[0,+)
Number
Number of
times the
preparation for
an incoming
handover from
GSM, UMTS,
or TD-SCDMA
to LTE
succeeds.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Incoming
Handover
Execution
Failures
[0,+)
Number
Number of
times the
preparation for
an incoming
handover from
GSM, UMTS,
or TD-SCDMA
to LTE succeeds
but the handover
fails.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4070
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Execution
Success Rate
[0,100]
Inter-RAT
incoming
handover
success rate
from GSM,
UMTS, or TDSCDMA to LTE
during the same
call process =
(Number of
inter-RAT
incoming
handover
requests Number of
handover
requests)/
Number of
inter-RAT
incoming
handover
requests
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Execution
Request Times
[0,+)
Number
Number of
times the
preparation for
an incoming
handover on the
LTE network
succeeds when
the eNodeB
receives the
RRC
Connection
Setup message
or when the UE
is handed over
to the eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4071
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Incoming
Handover
Execution
Failures
[0,+)
Number
Number of
times the
preparation for
an incoming
handover on an
LTE network
succeeds but the
handover fails
when the
eNodeB
receives the
RRC
Connection
Setup message
or when the UE
is handed over
to the eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Execution
Success Rate
[0,100]
Incoming intraRAT handover

success rate
during the same
call process on
the LTE
network =
(Number of
incoming intraRAT handover
requests Number of
failed incoming
intra-RAT
handovers)/
Number of
requests
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4072
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
LTE to TDSCDMA
Handover
Execution
Request Times
[0,+)
Number
Number of
times the
preparation for
an outgoing
handover from
LTE to TDSCDMA
succeeds when
the eNodeB
receives the
RRC
Connection
Setup message
or when the UE
is handed over
to the eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
LTE to TDSCDMA
Handover
Execution
Failures
[0,+)
Number
Number of
times the
preparation for
an outgoing
handover from
LTE to TDSCDMA
succeeds but the
handover fails
when the
eNodeB
receives the
RRC
Connection
Setup message
or when the UE
is handed over
to the eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4073
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
LTE to TDSCDMA
Handover
Execution
Success Rate
[0,100]
Handover
success rate
from LTE to
TD-SCDMA
during the same
call process =
(Number of
handover
requests from
LTE to TDSCDMA Number of
failed handover
requests from
LTE to TDSCDMA)/
Number of
handover
requests from
LTE to TDSCDMA
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Performance Analysis Summary-Delay Evaluation
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Delay Reports
(Non-Service)
[0,+)
Number
Number of RRC
Connection
Setup Request
messages (nonservice) with a
delay according
to the
predefined
delay for RRC
connection
setup.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4074
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Average Delay
(Non-Service)
[0,+)
Second
You can obtain

the average
delay for RRC
connection
setup (nonservice) by
using the
following
formula:
Average delay
for RRC
connection
setup (nonservice) = Sum
of all RRC
connection
setup delays
(non-service)/
Number of
reports with
RRC
connection
setup delay
(non-service).
In the preceding
formula, the
RRC
connection
setup delay
spans from the
time when a
terminal sends
an RRC
Connection
Setup Request
message to the
time when the
terminal sends
an RRC
Connection
Setup Complete
message.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4075
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rate of RRC
Setup Overlong
Delays (NonService)
[0,100]
You can obtain

the proportion
of exceedingly
long RRC
connection
setup delays
(non-service) by
using the
following
formula:
Proportion of
exceedingly
long RRC
connection
setup delays
(non-service) =
Number of
exceedingly
long RRC
connection
setup delays
(non-service)/
Number of
reports with
RRC
connection
setup delay
(non-service).
In the preceding
formula, the
number of
exceedingly
long RRC
connection
setup delays
(non-service) is
the number of
times that the
RRC
connection
setup delay
(non-service)
exceeds the
threshold for
RRC
connection
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4076
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
setup delay
(non-service).
RRC Setup
Delay Reports
(Service)
Issue 03 (2015-07-30)
[0,+)
Number
Number of RRC
Connection
Setup Request
messages
(service) with a
delay according
to the
predefined
delay for RRC
connection
setup.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
4077
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Average Delay
(Service)
[0,+)
Second
You can obtain

the average
delay for RRC
connection
setup (service)
by using the
following
formula:
Average delay
for RRC
connection
setup (service) =
Sum of all RRC
connection
setup delays
(service)/
Number of
reports with
RRC
connection
setup delay
(service). In the
preceding
formula, the
RRC
connection
setup delay
spans from the
time when a
terminal sends
an RRC
Connection
Setup Request
to the time when
the terminal
sends an RRC
Connection
Setup Complete
message, when
the terminal
sends the RRC
Connection
Setup Request
and RRC
Connection
Setup Complete
messages due to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4078
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
emergency,
highPriorityAccess, mtAccess, or moData.
Issue 03 (2015-07-30)

4079
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rate of RRC
Setup Overlong
Delays
(Service)
[0,100]
You can obtain

the proportion
of exceedingly
long RRC
connection
setup delays
(service) by
using the
following
formula:
Proportion of
exceedingly
long RRC
connection
setup delays
(service) =
Number of
exceedingly
long RRC
connection
setup delays
(service)/
Number of
reports with
RRC
connection
setup delay
(service). In the
preceding
formula, the
number of
exceedingly
long RRC
connection
setup delays
(service) is the
number of times
that the RRC
connection
setup delay
(service)
exceeds the
threshold for
RRC
connection
setup delay
(service).
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4080
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Delay Reports
[0,+)
Number
Number of
Initial Context
Setup Request
or E-RAB Setup
Request
messages with a
delay according
to the
predefined
delay for ERAB setup.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4081
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Average Delay
[0,+)
Second
You can obtain

the average
delay for ERAB setup by
using the
following
formula:
Average delay
for E-RAB
setup = Sum of
all E-RAB setup
delays/Number
of reports with
E-RAB setup
delay. In the
preceding
formula, the ERAB setup
delay spans
from the time
when a terminal
sends an Initial
Context Setup
Request
message to the
time when the
terminal
receives an
Initial Context
Setup Response
message. The ERAB setup
delay can also
span from the
time when a
terminal sends
an E-RAB Setup
Request
message to the
time when the
terminal
receives an
ERAB Setup
Response
message.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4082
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rate of
Overlong ERAB Setup
Delays
[0,100]
You can obtain

the proportion
of exceedingly
long E-RAB
setup delays by
using the
following
formula:
Proportion of
exceedingly
long E-RAB
setup delays =
Number of
exceedingly
long E-RAB
setup delays /
Number of
reports with ERAB setup
delay. In the
preceding
formula, the
number of
exceedingly
long E-RAB
setup delays is
the number of
times that the ERAB setup
delay exceeds
the threshold for
E-RAB setup
delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover Delay
Reports
[0,+)
Number
Number of
times that the
request for an
outgoing interRAT handover
from LTE to
GSM, UMTS,
CDMA2000, or
TD-SCDMA is
accepted and the
handover
succeeds.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4083
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Average Delay
[0,+)
Second
You can obtain

the average
delay for
by using the
following
formula:
Average delay
for outgoing
inter-RAT
handover = Sum
of all outgoing
inter-RAT
handover
delays/Number
of reports with
delay. In the
preceding
formula, the
delay spans
from the time
when the
request for an
outgoing
handover from
LTE to GSM,
UMTS,
CDMA2000, or
TD-SCDMA is
sent to the time
when the
handover
succeeds.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4084
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rate of
Overlong InterRAT Outgoing
Handover
Delays
[0,100]
You can obtain

the proportion
of exceedingly
long outgoing
inter-RAT
handover delays
by using the
following
formula:
Proportion of
exceedingly
long outgoing
inter-RAT
handover
delays=
Number of
exceedingly
long outgoing
inter-RAT
handover
delays/Number
of reports with
exceedingly
long outgoing
inter-RAT
handover delay.
In the preceding
formula, the
number of
exceedingly
long outgoing
inter-RAT
handover delays
is the number of
times that the
sum of all
outgoing interRAT delays is
above the upper
threshold for
delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4085
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover Delay
Reports
[0,+)
Number
Number of the
reports
indicating that
an incoming
inter-RAT
handover from
GSM or UMTS
to LTE succeeds
after the request
for the handover
is accepted.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Incoming
Handover
Average Delay
[0,+)
Second
You can obtain

the average
delay for
incoming interRAT handover
by using the
following
formula:
Average delay
for incoming
inter-RAT
handover = Sum
of all incoming
inter-RAT
handover
delays/Number
of reports with
delay. In the
preceding
formula, the
delay spans
from the time
when the
request for an
incoming
handover from
GSM or UMTS
to LTE is sent to
the time when
the handover
succeeds.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4086
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rate of
Overlong InterRAT Incoming
Handover
Delays
[0,100]
You can obtain

the proportion
of exceedingly
long incoming
inter-RAT
handover delays
by using the
following
formula:
Proportion of
exceedingly
long incoming
inter-RAT
handover
delays=
Number of
exceedingly
long incoming
inter-RAT
handover
delays/Number
of reports with
exceedingly
long incoming
inter-RAT
handover delay.
In the preceding
formula, the
number of
exceedingly
long incoming
inter-RAT
handover delays
is the number of
times that the
sum of all
incoming interRAT delays is
above the
threshold for
delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4087
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover Delay
Reports
[0,+)
Number
Number of the
reports
indicating that
an outgoing
inter-RAT
handover
succeeds after
the request for
handover within
an LTE system
is accepted.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4088
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Average Delay
[0,+)
Second
You can obtain

the average
delay for
by using the
following
formula:
Average delay
for outgoing
intra-RAT
handover = Sum
of all outgoing
intra-RAT
handover
delays/Number
of reports with
delay. In the
preceding
formula, the
delay spans
from the time
when the
request for an
handover within
an LTE system
is sent to the
time when the
handover
succeeds.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4089
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rate of
Overlong IntraRAT Outgoing
Handover
Delays
[0,100]
You can obtain

the proportion
of exceedingly
long outgoing
intra-RAT
handover delays
by using the
following
formula:
Proportion of
exceedingly
long outgoing
intra-RAT
handover
delays=
Number of
exceedingly
long outgoing
intra-RAT
handover
delays/Number
of reports with
exceedingly
long outgoing
intra-RAT
handover delay.
In the preceding
formula, the
number of
exceedingly
long outgoing
intra-RAT
handover delays
is the number of
times that the
sum of all
outgoing intraRAT delays is
above the
threshold for
delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4090
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Incoming
Handover Delay
Reports
[0,+)
Number
Number of the
reports
indicating that
an incoming
inter-RAT
handover
succeeds after
the request for
handover within
an LTE system
is accepted.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4091
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Incoming
Handover
Average Delay
[0,+)
Second
You can obtain

the average
delay for
by using the
following
formula:
Average delay
for incoming
intra-RAT
handover = Sum
of all incoming
intra-RAT
handover
delays/Number
of reports with
delay. In the
preceding
formula, the
delay spans
from the time
when the
request for an
handover within
an LTE system
is sent to the
time when the
handover
succeeds.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4092
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Rate of
Overlong IntraRAT Incoming
Handover
Delays
[0,100]
of exceedingly
long incoming
intra-RAT
handover delays
= Number of
exceedingly
long incoming
intra-RAT
handover
delays/Number
of reports with
exceedingly
long incoming
going intraRAT handover
delay. In the
preceding
formula, the
number of
exceedingly
long incoming
intra-RAT
handover delays
is the number of
times that the
sum of all
incoming intraRAT delays is
above the
threshold for
delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4093
Nastar
Terminal performance analysis summary - quality evaluation
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
QCI Reports
[0,+)
Number
Number of ERAB IDs upon

E-RAB failures
after a terminal
sends the ERAB SETUP
REQUEST or
INITIAL
CONTEXT
SETUP
REQUEST
message and
receives the ERAB SETUP
response or
INITIAL
CONTEXT
SETUP
response
message from
the related
eNodeB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4094
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average QCI
Value
GBR[1,4]
N/A
Average QCI
value.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Non GBR[5,9]
GBR (QCIN)
indicates the
GBR service
with high-level
QoS. The value
of N can be 1, 2,
3, or 4. QoS is
short for QoS
class indicator,
and GBR is
short for
guaranteed bit
rate.
Non GBR
(QCIN)
indicates the
non-GBR
service with
low-level QoS.
The value of N
can be 5, 6, 7, 8,
or 9.
Issue 03 (2015-07-30)
Rate of GBR
QCIs
[0,100]
Percentage of
reports for QCIs
indicating the
GBR service =
Number of
reports in which
QCI range is
from 1 to 4/
Number of QCI
reports.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL RSRP
Reports
[0,+)
Number
Number of MRs
with valid
downlink
RSRPs.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4095
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average DL
RSRP
[-140,-43]
dBm
Average
downlink RSRP
value. Average
DL RSRP =
Sum of
downlink
RSRPs/Number
of MRs with
valid DL RSRPs
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL SINR
Reports
[0,+)
Number
Number of MRs
with valid
uplink SINRs.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average UL
SINR
[-15.0,35.0]
dB
Average uplink
SINR value.
Average UL
SINR = Sum of
uplink SINRs/
Number of MRs
with valid
uplink SINRs
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Parameter
Range
Unit
Description
Supported
Solution
Version
Row No
[1,50000)
N/A
Indicates the
number of a row
in the summary
table.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eNodeB ID
N/A
N/A
Indicates the ID
of the eNodeB
where the
terminal is
located.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cell Information Overview
Issue 03 (2015-07-30)

4096
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
eNodeB Name
N/A
N/A
Indicates the
name of the
eNodeB where
the terminal is
located.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cell ID
N/A
N/A
Indicates the ID
of the cell where
the terminal is
located.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cell Name
1 to 64
characters
N/A
Indicates the
name of the cell
where the
terminal is
located.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Terminals
[0,+)
N/A
Indicates the
number of
terminals of a
specified type in
each cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
NOTE
Performance Analysis Summary-Retainability Evaluation, Performance Analysis SummaryMobility Evaluation, Performance Analysis Summary-Delay Evaluation, and Terminal performance
analysis summary - quality evaluation.
Issue 03 (2015-07-30)

4097
Nastar
Terminal Performance Analysis Summary - By Bearer

Parameter
Range
Unit
Description
Supported
Solution
Version
Bearer Type
NA
NA
Type of the
channel that
bears voice or
data services.
Common bearer
types include
AMR, R99 PS,
HSDPA,
HSUPA, and
HSDPA_HSUP
A.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Terminals
[0,+)
N/A
Indicates the
number of
terminals of a
specified type in
each cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
NOTE
Performance Analysis Summary-Retainability Evaluation, Performance Analysis SummaryMobility Evaluation, Performance Analysis Summary-Delay Evaluation, and Terminal performance
analysis summary - quality evaluation.
6.4 LTE Network Geographic Observation

The Nastar geographically locates and displays network coverage, traffic, users, and unusual
events after collecting the entire network data, intuitively displaying general network conditions
and problem areas.
6.4.1 Basics of LTE Network Geographic Observation

This section describes the conceptual knowledge about LTE network geographic observation,
including the network geographic observation function, technical specifications, and feature
limitations. This helps you perform operations related to LTE network geographic observation.
Read this section before performing LTE network geographic observation analysis.
NOTE
Issue 03 (2015-07-30)

4098
Nastar
LTE Network Geographic Observation

Network geographic observation uses radio link measurement reports of subscribers on the live
network to locate exceptions. This function uses call history records (CHRs) 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.
LTE network geographic observation supports network coverage problem geographic analysis,
network coverage geographic analysis, network traffic geographic analysis, and network event
geographic analysis:
l
Network coverage problem geographic analysis supports the geographic rendering for the
following indicators: proportion of poor coverage, proportion of coverage hole, proportion
of overshooting coverage, proportion of non-dominant pilot, and proportion of UL limited
coverage, Proportion of Overshooting Coverage Interference.
Function: It replaces traditional simulation means to display the coverage problems of the
serving cell, helping telecom operators identify problematic areas such as those with a poor
coverage.
Network coverage geographic analysis supports the geographic rendering for the following
indicators: RSRP, RSRQ, UL DM RS RxPower, UL DM RS SINR, UE TxPower, primary
serving cell, and confidence level.
Network traffic geographic analysis supports the geographic rendering for the following
indicators: total traffic volume, UL traffic volume, DL traffic volume, UL average
throughput, DL average throughput.
Function: It geographically displays the resource throughput in each area on the network,
helping telecom operators know the air interface resource occupation situation and identify
problematic areas where exceptions occur frequently.
Network event geographic analysis supports the geographic rendering for the following
indicators: radio link failures (RLF), intra-frequency outgoing HO failures, inter-frequency
outgoing HO failures, and inter-RAT outgoing HO failures.
Functions:
Geographic display of RLF events helps engineers learn the distribution of RLF events
on the network comprehensively during network evaluation so they can optimize the
areas where problems centered by preference. It also allows the engineers to subscribe
to the related events after the optimization and tuning are complete in order to check
the optimization effect. This facilities RLF problem locating and network evaluation.
It displays the locations where exceptions (including handover failures) occur and the
frequency for each type of exceptions in each area on grid maps, helping telecom
operators identify problematic areas where handover failures occur frequently.
Issue 03 (2015-07-30)

4099
Nastar
NOTE
technology. You can set the Trace Event Block Type dialog box under the Data Subscription
Management function to enable NEs to report trace measurement results. For example, after you select
MEASUREMENT REPORT, PERIOD LOGGED MDT MEASUREMENT, PERIOD UE
POSITIONING MEASUREMENT, PERIOD INTRA FREQ MDT MEASUREMENT, and RLF
REPORT, the corresponding event block types are recorded on the CHRs reported by NEs. After the
geographic feature is used, deselect the corresponding event block types on the Nastar.
l



Function Principles
The data source of LTE network geographic observation is the eNodeB CHR data on the NE
side.
Issue 03 (2015-07-30)

4100
Nastar
Issue 03 (2015-07-30)
User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Purpose
1.
Subscri
be to
basic
data
Issue a
basic
data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U

Issue a
subscrip
tion
comma
nd
eSA
U
U20
00/
M20
00

M2000.

4101
Nastar
User
Operat
ion
2.
Subscri
be to
applicat
ion data
3.
Check
the
integrit
y of
Issue 03 (2015-07-30)
Proced
ure
Sou
rce
Dest
inati
on
Purpose
Forward
the
subscrip
tion
comma
nd
U20
00/
M20
00
eNod
eB

Upload
raw data
(CHR)
eNo
deB
Trac
e
Serv
er

Server.
Issue an
applicat
ion data
subscrip
tion
comma
nd
Nast
ar
Serv
er
eSA
U

Deliver
a
preproc
essing
task
(direct)
eSA
U
LTE
SAU

task.
Collect
data
(CHR)
(direct)
LTE
SA
U
Trac
e
Serv
er

Server.
Trac
e
Serv
er
LTE
SAU

Upload
preproc
essed
data
(direct)
LTE
SA
U
eSA
U
To upload preprocessed data (eNodeB CHR) to the

eSAU.
Issue a
data
query
comma
nd
Nast
ar
Serv
er
eSA
U

eSAU.

4102
Nastar
User
Operat
ion
Proced
ure
Sou
rce
Dest
inati
on
Purpose
analysi
s data
Return
data
query
results
eSA
U
Nast
ar
Serv
er

4.
Create
and
execute
an
analysi
s task
Issue a
task
executio
n
comma
nd
Nast
ar
Serv
er
eSA
U

Upload
data
analysis
results
eSA
U
Nast
ar
Serv
er

the Nastar server.
5. View
analysi
s results
Display
analysis
results
Nast
ar
Serv
er
NOTE
Technical Specifications for LTE Network Geographic Observation

of analysis time.
NOTE
Item
Execution type

analysis task
l 6000 cells (when the number of LTE basic licenses is less

than or equal to 24,000 cells)
l 12,000 cells (when the number of LTE basic licenses is less
l 18,000 cells (when the number of LTE basic licenses is less
Issue 03 (2015-07-30)

4103
Nastar
Item
Number of allowed
analysis tasks
l 50 one-time tasks

one analysis task
7 days

task
30 minutes

15 days

15 days
l 10 periodic tasks
NOTE
The execution duration of one analysis task is set based on the 500-meter
coverage radius of a single cell. In the analysis task, if the average singlecell coverage radius is longer than 500 m, the execution duration may
increase.
6.4.2 Preparations for LTE Network Geographic Observation

Before running an LTE network geographic observation task, verify user rights and related
environment information and obtain related data, ensuring that the task is properly executed.
Read this section before performing LTE network geographic observation analysis.

For the LTE network, network geographic observation is classified into LTE FDD network
geographic observation and LTE TDD network geographic observation. The two functions are
independent from each other.
l
The licenses and user rights required for LTE FDD network geographic observation are as
follows:
network geographic observation, and the licenses are valid.
management authentication, LTE FDD network geographic observation task operation
right, and the operation rights to operate the analyzed NEs.
Check that you have the following operation rights of analysis task: LTE FDD network
geographic observation task operation right, and the operation rights to operate the NE
Issue 03 (2015-07-30)
The licenses and user rights required for LTE TDD network geographic observation are as
follows:
4104
Nastar
network geographic observation, and the licenses are valid.
management authentication, LTE TDD network geographic observation task operation
right, and the operation rights to operate the analyzed NEs.
Check that you have the following operation rights of analysis task: LTE TDD network
geographic observation task operation right, and the operation rights to operate the NE
NOTE

task successfully.
Issue 03 (2015-07-30)

4105
Nastar

Data
Type
Function
Operation
Config
uration
Data
(Mand
atory)

the NE controlling the test
cell and neighboring cells
is used to correctly analyze
cells and collect the
analysis data of these cells
from the network during
the analysis process.

and imports the configuration data after the OSS and
NE information is configured. You can also
Data Maintenance Management to check whether
the configuration data is available in the Nastar
database. For detailed information about collecting,
importing, and checking, see 3.4.2 Checking the
configuration data. The purpose is to avoid
Engine
ering
Parame
ters
(Mand
atory)
The engineering
longitude and latitude and
the antenna azimuth. The
information is used for the
effective identification of
neighboring cell
information and
theme analysis.

parameters have been imported. If the parameters are
unavailable, you must import the engineering
Issue 03 (2015-07-30)

4106
Nastar
Data
Type
Function
Operation
Map
File
(Option
al)

result geographically. You
map file if you do not want
to view the analysis result
on the map.

(Optional).

l
V100R010C10 (or later), or BTS3900 V100R011C00 (or later).
(Optional) Ensure that the Nastar can obtain the real time analysis data required for the
LTE network geographic observation function. Only the real time data is used by the LTE
network geographic observation, that is choosing the Real-time data on the data
subscription function, you need to configure the parameters. For details, see
Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data
> Preparing for Obtaining Data(LTE) > Configuring the Trace Server on the eNodeB
(LTE Network Geographic Observation, Optional) in the Nastar Commissioning Guide
(RH2288).
6.4.3 Process of LTE Network Geographic Observation

This section describes the process of LTE network geographic observation and the detailed
operations during the process.
l
Prerequisites
Process
Prerequisites
LTE Network Geographic Observation.
Process
Issue 03 (2015-07-30)

4107
Nastar
Issue 03 (2015-07-30)

4108
Nastar

No.
Proced
ure
Description
Reference
(1)
Check
whether
analysis
data is
integrat
ed

3.6 Checking
the Integrity
of Analysis
Data
Procedure:
1. Choose Data Type > Network Analysis > ***
Network Geographic Observation Data.
*** indicates the network type including LTE TDD
and LTE FDD.
4. Click Query.
window.
analysis task.
(2).
NOTE
(2)
LTE
Periodic
MR
Period
Setting
Navigation path: Choose Maintenance > LTE Periodic

MR Period Setting
Procedure:
1. In the LTE Periodic MR Period Setting window, set
Periodic MR Period, Number of Sampled Users and
Number of Times MRs Are Reported.
2. Click Configure.
Issue 03 (2015-07-30)

For details
about
parameters,
see LTE
Periodic MR
Period
Setting
Parameters.
4109
Nastar
No.
Proced
ure
Description
Reference
Subscri
be to
analysis
data
(basic)

3.5
Subscribing
to Analysis
Data
Procedure:
1. Click the LTE FDD or LTE TDD tab in the Data
Subscription Management window.
NOTE
If you want to subscribe to data related to LTE FDD network
geographic observation, click the LTE FDD tab; if you want
to subscribe to data related to LTE TDD network geographic
observation, click the LTE TDD tab.

3. Click Configure on the Basic Subscription Settings
tab page.
Observation to ON.
Modification.
Click ... to set the advanced parameters, for details, see
5. Click OK.
Subscri
be to
analysis
data
(applica
tion)

Procedure:
1. Click the LTE FDD or LTE TDD tab in the Data
Subscription Management window.
tab page.
Geographic Observation Parameter Setting dialog
box.
Parameters.
5. Click OK.
Issue 03 (2015-07-30)

4110
Nastar
No.
Proced
ure
Description
Reference
Check
whether
analysis
data is
integrat
ed

3.6 Checking
the Integrity
of Analysis
Data
Procedure:
1. Choose Data Type > Network Analysis > ***
Network Geographic Observation Data.
*** indicates the network type including LTE TDD
and LTE FDD.
4. Click Query.
window.
analysis task.
technical support.
(3)
Create
an
analysis
task

Analysis > LTE Network Geographic Observation in
the navigation tree of the Analysis Task Management
window.
Procedure:
1. Double-click the LTE Network Geographic
Observation.
3. Select the NE to be analyzed on the Select NE(s) tab.
Grid Resolution for displaying network geographic
observation results.
5. On the Parameter Settings tab page, set filtering
parameters. Click Next.
The system provides four types of filter criteria by
default, and you can add or delete filter criteria based
on the default ones as required.
l For
details,
see 3.7
Creating
an
Analysis
Task.
l For details
about the
parameter
s, see
Analysis
Task
Paramete
rs.
For details about the parameters, see Analysis Task

Parameters.
6. Choose an analysis time segment. After you set the
generated within this time range. Click Next.
7. Click Finish.
Issue 03 (2015-07-30)

4111
Nastar
No.
Proced
ure
Description
Reference
(4)
View
analysis
results

l For
details,
see 3.8
Querying
Analysis
Results.
Procedure:
Geographic Observation from the shortcut menu.
2. In the Geographic Observation window, view the
View
analysis
results
(indepth
traffic)
Navigation path: Choose Polygon Areas in the

navigation tree of the LTE network geographic
observation window.
Procedure:
1. In the navigation tree, right-click Polygon Areas and
choose LTE Network Geographic Observation >
In-depth Traffic Analysis from the shortcut menu.
2. In the displayed In-depth Traffic Analysis window,
view the LTE network geographic observation results.
Issue 03 (2015-07-30)

l For details
on the
descriptio
n of the
window
for
showing
analysis
results,
see 6.4.4
Interface
Descripti
on: LTE
Network
Geograp
hic
Observat
ion.
4112
Nastar
No.
Proced
ure
Description
Reference
(5)
Export
analysis
results

upper left part of the Geographic Observation window.
l For
details,
see 3.10
Exportin
g
Analysis
Reports.
Procedure:
3. Click Save.
l For details
on the
descriptio
n of the
window
for
showing
analysis
results,
see 6.4.4
Interface
Descripti
on: LTE
Network
Geograp
hic
Observat
ion.
Issue 03 (2015-07-30)
Parameter
Description
Periodic MR
Period

4113
Nastar
Parameter
Description
Number of
Sampled Users

Nastar.
NOTE
Number of
Times MRs
Are Reported


Basic Subscription
Issue 03 (2015-07-30)

4114
Nastar
Para
met
er
Description
Net
wor
k
Geo
grap
hic
Obs
ervat
ion
Data
Switch for enabling or disabling the reporting of eNodeB CHR data. You can retain
You can click
l Common tab page: Set Trace Event Block Type. The selected type of event block
will be traced and recorded in CHRs. The details about various types of event
blocks are as follows:
measurement
measurement
PERIOD LOGGED MDT MEASUREMENT, log-type MDT measurement
PERIOD INTRA FREQ MR MDT, intra-frequency MDT measurement
PERIOD UE MEASUREMENT MDT, user-defined MDT measurement
CSFB PREP, CSFB
PERIOD PRIVATE THROUGHPUT MEASUREMENT MDT, periodic
throughput MDT measurement
Issue 03 (2015-07-30)

4115
Nastar
Para
met
er
Description
PERIOD_UE_MultiRRU_UL_RSRP_MR, uplink RSRP events in multiple

RRU cells
L2 UE Context Release
If PERIOD LOGGED MDT MEASUREMENT is contained in Trace Event
Block Type, click Select Idle State Measurement Object at the lower left corner
to select the idle object to be measured. The range of selected objects is displayed
in the Idle State Measurement Object Range column on the Periodic Event
Trace Event Block: Specify the type of event to be traced. The value of this
parameter can be PERIOD_LOGGED_MDT_MEASUREMENT.
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).
Idle State Measurement Object Range: Specify the range of idle objects to
be measured. A maximum of 32 cells or eight TACs can be selected.
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.
Issue 03 (2015-07-30)

4116
Nastar
Parameter
Description
Weak
covera
ge area
definit
ion
Defines the thresholds for a weak coverage area.
Weak coverage
area RSRP < A Or
Weak coverage
area RSRQ < B
shows an RSRP smaller than A or an RSRQ smaller than B
within the area.
Range:
l A, [-140,-43]
l B, [-19.5,-2.5]
Cover
age
hole
area
definit
ion
Coverage hole
area RSRP < C
Nonprimar
y pilot
area
definit
ion
Absolute value of
the downlink
RSRP difference
between nonprimary pilot area
and neighboring
cell < D
Defines the thresholds for an area with no primary pilot.
Number of
neighboring cells
meeting previous
conditions E,
and Non-primary
pilot area RSRP >
F
l E, [1,5]
Terminal transmit
power G, and
Uplink base
station receive
power in
problematic
uplink coverage
area < H, or
Uplink base
station receive
SINR in
problematic
uplink coverage
area < I
Defines the thresholds for an area with uplink limited coverage.
Uplink
limite
d
covera
ge
areas
definit
ion
Issue 03 (2015-07-30)
Defines the thresholds for a coverage hole area.

shows an RSRP smaller than C within the area.
Range: C, [-140,-43]
shows an RSRP larger than F and a difference of less than D
in downlink RSRP from E neighboring cells within the area.
Range:
l D, [0,10]
l F, [-140,-43]
shows a terminal transmit power higher than G and an uplink
eNodeB receive power lower than H, or the data that shows an
uplink eNodeB receive SINR smaller than I, within the area.
Range:
l G, [-17,23]
l H, [-150,-30]
l I, [-15.0,35.0]

4117
Nastar
Parameter
Description
Cross
Overs
hootin
g area
definit
ion
Ratio of distance
from overlapped
coverage area to
service area and
distance from
overlapped
coverage area to
strongest RSRP
neighboring cell >
J, and the number
of cells in the
circular area
whose diameter is
the connection
line from the
overlapped
coverage area to
the service cell is
greater than the
threshold of
layers.
Defines the thresholds for an overlapped coverage area.
RSRP of
neighboring cell
as evaluated
object - Serving
cell RSRP > K,
and Serving cell
RSRP > L
Defines the thresholds for an overshooting coverage cell area.
Overs
hootin
g Cell
area
Defini
tion
shows a ratio of distance A to distance B (distance A spans from
the area to its serving cell and distance B spans from the area
to its neighboring cell with the strongest RSRP) larger than J,
and the number of cells (within the diameter connecting the
area and its serving cell) larger than the threshold for the
number of layers.
The threshold for the number of layers is not a fixed value, you
can set the threshold based on different angles. The angle is
between the connection line from the overlapped coverage area
to the service cell and the orientation of the service cell antenna.
The absolute value of the angle is [0,45), [45,90), [90,135), or
[135,180).
Range: J, [1,10]
Layer number limit: [0,100]. Set different limits for different
angles.
shows the difference between the RSRP of a neighboring cell
as the evaluated object and the RSRP of the serving cell larger
than K and the RSRP of the serving cell larger than L.
Range:
l K, [-10,0]
l L, [-140,-43]

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Issue 03 (2015-07-30)

4118
Nastar
Parameter
Description
Task Type
Remarks

NE information
Parameter
Description
Analysis Type
Select NE(s)

l 6000 cells (when the number of LTE basic licenses is less than or
equal to 24,000 cells)
l 12,000 cells (when the number of LTE basic licenses is less than or
l 18,000 cells (when the number of LTE basic licenses is less than or
NOTE
Parameter
Description
Parameters
Setting
Specifies the filter criteria for analysis data. A maximum of 30 filter

criteria are allowed.
After the filter criteria are specified, analysis results that meet only the
filter criteria can be displayed.
Grid Resolution
Settings
Set the Grid Resolution for displaying network geographic observation

results.
100m*100m.
Issue 03 (2015-07-30)

4119
Nastar
Parameter
Description
Duration
Delay
immediately.
Busy hours
Execute on

Param
eter
Description
Note
Start
time

Period

Repeat
times

Issue 03 (2015-07-30)


4120
Nastar
Param
eter
Description
Note
Delay
by
(hours)
NOTE
Whole
day

NOTE

hours.

at the start time.
01/01/2013 14:00:00, Start time is
03:00:00.
01/02/2013 14:00:00, Start time is
executes the task.

parameter.
Busy
hours

in each period.
busy time.
6.4.4 Interface Description: LTE Network Geographic Observation

This section describes the result window of LTE network geographic observation, including
functions of each area in the window, helping you perform related operations.
Opening the Window

l
Issue 03 (2015-07-30)
Select an LTE network geographic observation task in the complete state. Then, in the
displayed Task Result area, double-click the results of this task.
4121
Nastar
Select an LTE network geographic observation task in the complete state. Then, in the
displayed Task Result area, right-click the results of this task and choose View Analysis
Main Window
Network geographic observation results are displayed in raster graphics, as show in Figure
6-17.
Figure 6-17 Window for showing LTE network geographic observation results
Issue 03 (2015-07-30)
N
o.
Name
Description
Button area

4122
Nastar
N
o.
Name
Description
Navigation
tree

Nastar database and site information have been loaded in map
window.
NOTE
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.
polygon.
The Nastar provides an entry for traffic further analysis on the
selected area. For description about the window for showing
traffic further analysis, see Subinterface Display - Traffic
Further Analysis.
visible.
menu to reset the grid display effect or the number of
measurement reports (MRs) to be filtered within a grid.
The display setting functions of different indicators are not
exactly the same, all the functions are described as follows:
Issue 03 (2015-07-30)

4123
Nastar
N
o.
Name
Description
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 confidence
level. Five confidence levels are available in descending order:
A, B, C, D, and E. That is, only the results reached the
configured proportion of confidence level can be displayed in
the map window.
Filter tab page: enables you to set the display condition. That
is, only the results met the filter condition can be displayed in
the map window.
parameter. That is, only the results met the parameter value
can be displayed in the map window.
3
Geographic
observation
area

distinct colors by default. However, only the analysis results of the
last selected KPI are visible.
NOTE
function is enabled, the Nastar displays only the filtered sites. However,
no matter whether the filtering function is enabled or disabled, the Nastar
, the
original window.
4
Detailed grill
information
list area
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 03 (2015-07-30)

4124
Nastar
N
o.
Name
Description
Legend detail By default, the Nastar does not display this area. If you want to view the
area
Information
area

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
Subinterface Display - Traffic Further Analysis

The results show detailed information about traffic indicators in the polygon areas in charts and
tables, as shown in Figure 6-18.
Figure 6-18 In-depth Traffic Analysis
No.
Name
Description
Button area
After you set the file name and file path using the button, the
analysis results of all dimensions are saved as files in the format
of .csv, .xls, or .xlsx.
Navigation tree
Aggregates all objects to be analyzed. By default, all objects are

chosen.
Analysis results in a dimension can be displayed in the right chart
and table areas only when the corresponding analysis node is
selected in this navigation tree.
Issue 03 (2015-07-30)

4125
Nastar
No.
Name
Description
Chart area
Displays the value change trends within the task execution period
for different indicators by selected analysis objects. The chart area
is associated with the table area on the right.
l The X axis represents analysis task execution time with the unit
hour.
l The Y axis represents indicator values.
Table area
Lists values of traffic indicators of the cells by hours.

By default, the system displays the values in chronological order.
You can filter and sort contents in the tables in the table headers as
required.
6.4.5 Parameters for Viewing LTE Network Geographic

Observation Results
This section describes the parameters for querying LTE network geographic observation results.
Read this section before querying LTE network geographic observation results.
Issue 03 (2015-07-30)
Paramet
er
Range
Unit
Description
Supported
Solution
Version
RSRP
[-140,-43]
dBm
The raster traffic map is rendered

according to RSRP average values.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RSRQ
[-19.5,-2.5
]
dB
The traffic map is rendered according to

RSRQ average values.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL DM
RS
RxPower
[-150,-30]
dBm

the average of uplink RS RX powers of
the base station measured based on the
uplink demodulation reference signal in
the raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4126
Nastar
Issue 03 (2015-07-30)
Paramet
er
Range
Unit
Description
Supported
Solution
Version
UL DM
RS SINR
[-15.0,35.0
]
dB

the average of the uplink SINR
measured based on the uplink
demodulation reference signal in the
raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UE
TxPower
[-17,23]
dBm

the average of uplink TX powers of the
UE in the raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Primary
Serving
Cell
eNodeB ID N/A
+ Cell ID

the cell with the maximum number of
accumulated times in working as the
primary serving cell in MRs in the raster
view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The
interface is
shown as:
eNodeB
ID-Cell ID

4127
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution
Version
Confidenc
e Level
[0.00,100.
00]

theoretical precision of the positioning
method used by MRs and on the
percentage of MRs of specified high
confidence levels in all MRs in the raster
view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
All MRs are positioned based on the

following levels that are divided by
theoretical precision: A, B, C, D, and E.
You can specify N (N > 5) high
confidence levels.
l Lev_A: indicates a precision of 50 m
to 80 m. It is used for positioning
MRs reported only by AGPS or
distributed base stations.
l Lev_B: indicates a precision of 80 m
to 120 m. It is used for RRT
triangular positioning or for highscore feature database-based
matching.
l Lev_C: indicates a precision of 120
MRs related to three neighboring
cells that are served by different base
stations.
l Lev_D: indicates a precision of 200
MRs reported by two base stations.
l Lev_E: indicates a precision of over
350 m. It is used for positioning MRs
in any other scenarios, for example,
for positioning MRs reported by one
base station.
Issue 03 (2015-07-30)

4128
Nastar
Network Coverage Problem Map
Issue 03 (2015-07-30)
Paramete
r
Range
Unit
Description
Supported
Solution
Version
Proportion
of Weak
Coverage
[0.00,100.
00]

the percentage of MRs for poor coverage
to the total number of MRs in the raster
view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion
of
Coverage
Hole
[0.00,100.
00]

the percentage of MRs for coverage
holes to the total number of MRs in the
raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion
of Cross
Overshoot
ing
Coverage
[0.00,100.
00]

the percentage of MRs for overshooting
coverage to the total number of MRs in
the raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion
of Nondominant
Pilot
[0.00,100.
00]

the percentage of MRs for no dominant
pilot to the total number of MRs in the
raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion
of UL
Limited
Coverage
[0.00,100.
00]

the percentage of MRs for uplink
coverage problems to the total number
of MRs in the raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion
of
Overshoot
ing
Coverage
Interferen
ce
[0.00,100.
00]

the percentage of MRs for overlapping
coverage problems to the total number
of MRs in the raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4129
Nastar
NOTE
The statistics on Proportion of Coverage Hole and Proportion of Non-dominant Pilot involves the
statistics on radio link failure (RLF) reports.
The 3GPP R9 protocol defines RLF reports sent by UEs as follows: Cells restoring from an RLF return
RLF reports sent by UEs to the cells that have the same physical cell identifiers (PCIs) as those carried in
the restoration request message. If multiple cells on the network have the same PCI, RLF reports cannot
be sent to the correct cells. To avoid this problem, Huawei has restrictions on sending RLF reports. If an
eNodeB detects that multiple cells on the network have the same PCI, UEs do not send RLF reports.
Therefore, when multiple cells on the network have the same PCI, the RLF report statistical value calculated
by the Nastar is less than the actual number of RLF reports.
Network Traffic Map
Issue 03 (2015-07-30)
Paramete
r
Range
Unit
Description
Supported
Solution
Version
Total
Traffic
Volume
[0, +)
KB

the total traffic recorded in MRs in the
raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL Traffic
Volume
[0, +)
KB

the uplink traffic recorded in MRs in the
raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL Traffic
Volume
[0, +)
KB

the downlink traffic in MRs in the raster
view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL
Average
Throughp
ut
[0, +)
kbit/s

the average uplink throughput in MRs in
the raster view.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL
Average
Throughp
ut
[0, +)
The average uplink throughput refers to

the average uplink throughput within a
unit period.
kbit/s

the average downlink throughput in MRs
in the raster view.
The average downlink throughput refers
to the average downlink traffic within a
unit period.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
4130
Nastar
Network Event Map

Paramete
r
Range
Unit
Description
Supported Solution
Version
Radio
Link
Failures
[0,+)
Num
ber
The traffic map is

rendered according to the
failure number of radio
link in the raster view.
eRAN 6.0/eRAN 6.1/eRAN

7.0/eRAN 8.0/eRAN 8.1/
eRAN11.0
IntraFREQ
Outgoing
HO
Failures
[0,+)
Num
ber
The traffic map is

failure number of intrafrequency outgoing
handover in the raster
view.

7.0/eRAN 8.0/eRAN 8.1/
eRAN11.0
InterFREQ
Outgoing
HO
Failures
[0,+)
Num
ber
The traffic map is

failure number of interfrequency outgoing
view.

7.0/eRAN 8.0/eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
HO
Failures
[0,+)
Num
ber
The traffic map is

failure number of intersystem (LTE to UMTS)
view.

7.0/eRAN 8.0/eRAN 8.1/
eRAN11.0
Abnormal
RAB
Release
Times
[0,+)
Num
ber

subscriber abnormally
releases an RAB after
network access and
successful service
initiation.
eRAN 8.1/eRAN11.0
In-Depth Traffic Analysis
Issue 03 (2015-07-30)
Paramete
r
Range
Unit
Description
Supported
Solution
Version
Time
YYYYMMDD
hh:mm
N/A
The time when the data occurs.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4131
Nastar
Paramete
r
Range
Unit
Description
Supported
Solution
Version
eNodeB
ID
[0,1048
575]
N/A
Indicates the ID of the base station. The

value is unique on a PLMN. This
parameter constitutes a part of the cell
CGI.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eNodeB
Name
[1,64]
Chara
cter
Indicates the name of the base station. The

value is unique on a PLMN.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Cell ID
[0,255]
N/A
Indicates the ID of the EUTRAN cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
This parameter, together with the eNodeB

ID, constitutes EUTRAN cell ID.
EUTRAN cell ID, together with the
PLMN, constitutes the ECGI.
Issue 03 (2015-07-30)
Cell Name
[1,64]
Chara
cter
Indicates the cell name.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total
Traffic
Volume
[0, +)
KB
The total traffic volume occurs in certain

time within the selected area.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
UL
Traffic
Volume
[0, +)
KB
The uplink traffic volume occurs in certain

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL
Traffic
Volume
[0, +)
KB
The downlink traffic volume occurs in

certain time within the selected area.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4132
Nastar
Paramete
r
Range
Unit
Description
Supported
Solution
Version
UL
Throughp
ut
[0, +)
kbit/s
The uplink throughput occurs in certain

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
DL
Throughp
ut
[0, +)
The average uplink throughput refers to

the average uplink throughput within a
unit period.
kbit/s
The downlink throughput occurs in certain

The average downlink throughput refers
to the average downlink traffic within a
unit period.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
6.5 VIP Analysis


NOTE

Issue 03 (2015-07-30)

4133
Nastar
Function Scenarios
l

l
GSM.

onsite.
l

Issue 03 (2015-07-30)

4134
Nastar

l
of short calls.

a problem.
Issue 03 (2015-07-30)

4135
Nastar

Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
GS
M
<= 500/BSC
l All-signaling
analysis on CS
services: A
interface
(3GPP-48.008)
signaling, Abis
interface
(3GPP-48.058)
signaling, and
Um interface
(3GPP-44.018/
44.060)
signaling.
If you want to view

the all signaling
information on CS
domain, check that
the matching
BSC6900 version
is V900R011C00
to view the all
signaling
information on PS
domain, check that
the matching
BSC6900 version
is V900R014C00
or later.
For VIP
subscribers of
Important level
who subscribe to
complete signaling
procedure will be
function, and you
can double-click a
signaling record
and then analyze
detailed signaling
contents in the
displayed window.
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.
l All-signaling
analysis on PS
services: Gb
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 03 (2015-07-30)

4136
Nastar
Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
UM
TS
l <= 100/RNC
(BSC6900
V900R013C0
0 or later
version)
Iu interface (3GPP
TS 25.413)
signaling, Iur
interface (3GPP TS
25.423) signaling,
Iub interface
(3GPP TS 25.433)
signaling, Uu
interface (3GPP TS
25.331) signaling.
If you want to view

the all signaling
information, check
that the matching
BSC6900 version
is V900R013C00
or later.
For VIP
subscribers of
Important level
who subscribe to
complete signaling
procedure will be
displayed in the
deep analysis
function, you can
double-click a
signaling record
and then analyze
detailed signaling
contents in the
displayed window.
l <= 500/RNC
(BSC6900
V900R016C0
0 or later
version)
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.
Issue 03 (2015-07-30)

4137
Nastar
Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
LTE
<= 500/HSS
Signaling
messages on the
S1-MME interface
(3GPP
interface (3GPP
interface (3GPP
LTE3900
V100R008C00 or
later; U2000/
M2000
V200R013C00SP
C230 or later;
HSS9860
V900R008C01 or
later.
The in-depth
analysis function
displays signaling
procedures in
charts and allows
you to double-click
a signaling
message and
analyze details
about the signaling
message in the
displayed window.
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.
Note: This function

allows you to
analyze the
signaling
procedures,
including RRC
connection setup
and release, eRAB
setup and release,
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 03 (2015-07-30)
Note: You can

analyze the key
signaling
procedures of
common
subscribers other
than the 500
Important VIP
subscribers only in
LTE3900
V100R005C00SP
C370 or later.

4138
Nastar
Net
wor
k
Number of
Supported VIP
All-Signaling
Subscribers
Supported
Signaling Range
Required NE
Version
Function
Display Mode
Mult
iRAT
netw
orks
<= 500 of all the

RATs on the
entire network.
VIP subscribers
are managed as
Important VIP
subscribers by
using the VIP
group
management
function.

Data Source
Issue 03 (2015-07-30)

4139
Nastar
NOTE
the Encryption Key.
CHR data.
Function Principles
NOTE
scheme.
Issue 03 (2015-07-30)

4140
Nastar
Issue 03 (2015-07-30)

4141
Nastar

User
Oper
ation
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
1.
Subscr
ibe to
basic
data.
GSM
/
UMT
S
netw
ork
Issue
basic
data
subscri
ption
comma
nds
(GSM/
UMTS
).
Nast
ar
Serv
er
eSA
U

Issue
MML
comma
nds.
eSA
U
U200
0/
M20
00

M2000.
Forwar
d
MML
comma
nds.
U20
00/
M20
00
BSC/
RNC

generate raw data.
Upload
raw
data.
BSC/
RNC
SAU
Issue
basic
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

Issue
MML
comma
nds.
eSA
U
U200
0/
M20
00

M2000.
Forwar
d
MML
comma
nds.
U20
00/
M20
00
SGS
N/
MM
E

PS
Core
netw
ork
Issue 03 (2015-07-30)

4142
Nastar
User
Oper
ation
Scen
e
LTE
netw
ork
Proce
dure
Sour
ce
Dest
inati
on
Purpose
Upload
raw
data.
SGS
N/
MM
E/
GGS
N/
SAE
-GW
PS
SAU
Issue
basic
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

Issue
subscri
ption
comma
nds.
eSA
U
U200
0/
M20
00

M2000.
Forwar
d
subscri
ption
comma
nds.
U20
00/
M20
00
eNod
eB

Upload
raw
data.
eNod
eB/
MM
E
NOTE
enabled.

Trace
Serve
r/
LTE
SAU

NOTE
Issue 03 (2015-07-30)

4143
Nastar
User
Oper
ation
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
2.
Subscr
ibe to
applic
ation
data.
GSM
/
UMT
S
netw
ork
Issue
applica
tion
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

eSAU.
Deliver
a dataprepro
cessing
task
(direct)
.
eSA
U
SAU

Upload
prepro
cessed
data
(direct)
.
SAU
eSA
U
Issue
applica
tion
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

Deliver
a dataprepro
cessing
task
(direct)
.
eSA
U
PS
SAU

Upload
prepro
cessed
data
(direct)
.
PS
SAU
eSA
U
PS
Core
netw
ork
Issue 03 (2015-07-30)

4144
Nastar
User
Oper
ation
Issue 03 (2015-07-30)
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
LTE
netw
ork
Issue
applica
tion
data
subscri
ption
comma
nds.
Nast
ar
Serv
er
eSA
U

Deliver
a
prepro
cessing
task
(direct)
.
eSA
U
LTE
SAU

Upload
prepro
cessed
data
(direct)
.
LTE
SAU
eSA
U

Issue
data
query
comma
nds.
Nast
ar
Serv
er
eSA
U

Return
data
query
results.
eSA
U
Nasta
r
Serve
r

Nastar client.
Issue
task
executi
on
comma
nds.
Nast
ar
Serv
er
eSA
U

aggregate data.
Upload
data
analysi
s
results.
eSA
U
Nasta
r
Serve
r

3.
Check
the
integri
ty of
analys
is data.
4.
Create
and
execut
e an
analys
is task.

4145
Nastar
User
Oper
ation
Scen
e
Proce
dure
Sour
ce
Dest
inati
on
Purpose
5.
View
analys
is
results
.
Displa
y
analysi
s
results.
Nasta
r
Serve
r

of analysis time.
NOTE
Item
Execution type

analysis task
task
Number of allowed
analysis tasks

analysis.

NOTE

one analysis task
Issue 03 (2015-07-30)


4146
Nastar
Item

task
l GSM: 75 minutes
l UMTS: 90 minutes
l LTE: 10 minutes

l GSM: 30 days
l UMTS: 30 days
l LTE: 30 days
l PS Core: 30 days

l GSM: 30 days
l UMTS: 30 days
l LTE: 30 days
l PS Core: 30 days

l

Issue 03 (2015-07-30)

4147
Nastar

Functi
on
Required license

Management > User)
Data
subscri
ption
manage
ment
l GSM/UMTS/LTE
FDD/LTE TDD/PS
Core basic function
license

NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.

be analyzed.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.
l GSM/UMTS/LTE
FDD/LTE TDD/PS
Core VIP analysis
license
Issue 03 (2015-07-30)

4148
Nastar
Functi
on
Required license

Management > User)
NOTE
licenses for basic
functions and VIP
of all RATs.
RAT depends on the
GSM
VIP
analysi
s

license
l GSM VIP analysis
license

Operation Rights
Observation.
Issue 03 (2015-07-30)

4149
Nastar
Functi
on
Required license

Management > User)
UMTS
VIP
analysi
s

license

Operation Rights
l UMTS VIP analysis

license

Observation.
Issue 03 (2015-07-30)

4150
Nastar
Functi
on
Required license

Management > User)
LTE
TDD
VIP
analysi
s
l LTE TDD basic

function license

NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.

Observation.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.

license
display of the CSFB
counters.
VoLTE analysis
license, only for
Issue 03 (2015-07-30)

4151
Nastar
Functi
on
Required license

Management > User)
LTE
FDD
VIP
analysi
s
l LTE FDD basic

function license

NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.

Observation.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.

license
display of the CSFB
counters.
VoLTE analysis
license, only for
Issue 03 (2015-07-30)

4152
Nastar
Functi
on
Required license

Management > User)
PS
Core
VIP
analysi
s

license

Operation Rights

license
VoLTE signaling
analysis license
analysis license
display of the CSFB
counters.

Observation.
Issue 03 (2015-07-30)

4153
Nastar
Functi
on
Required license

Management > User)
GSM/
UMTS/
LTE
TDD/
LTE
FDD/
PS
Core
combin
ed
analysi
s
l GSM/UMTS/LTE
FDD/LTE TDD/PS
Core basic function
license

NOTE
limits, the Alarm
dialog box is
you to upgrade the
license. When you
query the license
consumption in the
the result is not
displayed in the
Alarm dialog box
number has not been
reported. The data
displayed in the
Alarm dialog box is
correct. You are
advised to upgrade
manner.

of each network.
l LTE Periodic MR
Period Setting is
account in the
or a user with data
subscription
management
permission.
l GSM VIP analysis

license
l UMTS VIP analysis
license
license
license
license
Issue 03 (2015-07-30)

4154
Nastar
Functi
on
Required license

Management > User)
Comm
on

Identity
task creation.

task successfully.
Data
Type
Function
Operation
Config
uratio
n Data
(Mand
atory)

information in MR
handed over.

Data.

NOTE
data.
Issue 03 (2015-07-30)

4155
Nastar
Data
Type
Function
Operation
VIP
Infor
matio
n
(Mand
atory)

VIP user and IMSI
information. Before
subscribing to VIP
the VIP group.

NOTE
Engin
eering
Param
eters
(Optio
nal)
The engineering
You do not need to
parameters if the
required.

Issue 03 (2015-07-30)

4156
Nastar
Data
Type
Function
Operation
Map
File
(Optio
nal)
The map file for a

analysis result
result on the map.

(Optional).
Mailb
ox
Infor
matio
n
(Optio
nal)

Nastar needs the
information for
needed.


NOTE
Issue 03 (2015-07-30)

4157
Nastar

Net
wor
k
Description
GSM

(or later).
(or later).
UM
TS

(or later).
Issue 03 (2015-07-30)

4158
Nastar
Net
wor
k
Description
LTE
NOTE
(RH2288).
Issue 03 (2015-07-30)

4159
Nastar
Net
wor
k
Description
PS
Core
NE version:
V900R013C00

l
Prerequisites
Procedure
Prerequisites
Procedure
Issue 03 (2015-07-30)

4160
Nastar
Issue 03 (2015-07-30)

4161
Nastar

No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(1)
Check
whether
analysis
data is
integrated

3.6
Checking
the
Integrity
of Analysis
Data
Procedure:
Analysis Data.
integrity.
4. Click Query.
the window.
analysis task.
performing (2).
NOTE
(2)
LTE
Periodic
MR Period
Setting
NOTE
subscription.

For details
about
parameters,
see LTE
Periodic
MR Period
Setting
Parameter
s
Procedure:
2. Click Configure.
Issue 03 (2015-07-30)

4162
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
Subscribe
to analysis
data (basic)

3.5
Subscribin
g to
Analysis
Data
Procedure:
click the *** tab.
configured.
Set.
NOTE
VIP Analysis.
reported.
5. Click Confirm.
Info area.
Issue 03 (2015-07-30)

4163
Nastar
No.
Procedur
e
Description
Subscribe
to analysis
data
(applicatio
n)

Reference
for
Detailed
Operatio
ns
Procedure:
click the *** tab.
configured.
VIP subscribers.
and NEs.
NOTE
subscribers.
5. Click Confirm.
Issue 03 (2015-07-30)

4164
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns

to.
Check
whether
analysis
data is
integrated

Procedure:
Analysis Data.
3.6
Checking
the
Integrity
of Analysis
Data

integrity.
4. Click Query.
the window.
analysis task.
technical support.
Issue 03 (2015-07-30)

4165
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(3)
Create an
analysis
task

l For
details,
see 3.7
Creatin
g an
Analysi
s Task.
Procedure:
to be analyzed.
NOTE

NOTE

10.Click Finish.
Issue 03 (2015-07-30)

l For
details
about
the
paramet
ers, see
Analysi
s Task
Param
eters.
l For
details
about
Sendin
g
Analysi
s
Report
s
Setting,
see
3.4.10
Setting
a
Mailbo
x and
Addres
s List
for
Sendin
g
Analysi
s
Report
s
(Optio
nal)
4166
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(4)
View
analysis
results VIP
summary
analysis

l For
details,
see 3.8
Queryi
ng
Analysi
s
Results
.
Procedure:
analysis results.
View
analysis
results VIP deep
analysis
Navigation path:
Procedure:
1. Click
NOTE
icon to enter
you need click
icon again.

NOTE
View
analysis
results VIP active
cells
analysis
l For
details
on the
descript
ion of
the
window
for
showin
g
analysis
results,
see
6.5.4
Refere
nce for
VIP
Analysi
s
Interfa
ce.

Procedure:
active.
Issue 03 (2015-07-30)

4167
Nastar
No.
Procedur
e
Description
View
analysis
results VIP active
servers
analysis
(only
support the
GSM
network)

View
analysis
results VIP trend
analysis

Reference
for
Detailed
Operatio
ns
Procedure:
are active.
Procedure:
Issue 03 (2015-07-30)

4168
Nastar
No.
Procedur
e
Description
Reference
for
Detailed
Operatio
ns
(5)
Export
analysis
reports

l For
details,
see 3.10
Exporti
ng
Analysi
s
Report
s.
Procedure:
3. Click Save.
l For
details
on the
descript
ion of
the
window
for
showin
g
analysis
results,
see
Interfa
ce
Descrip
tion:
VIP
Analysi
s/InDepth
Analysi
s/
Geogra
phic
Display
.
Issue 03 (2015-07-30)

4169
Nastar

Parameter
Description
Periodic MR
Period
Number of
Sampled Users

Nastar.
NOTE
Number of
Times MRs
Are Reported


Basic Subscription
Issue 03 (2015-07-30)

4170
Nastar
Netwo
rk
Parameter
Description
GSM
VIP
Analysis
Data (CHRCS)

You can click

NOTE
Issue 03 (2015-07-30)

4171
Nastar
Netwo
rk
Parameter
Description
VIP
Analysis
Data (CHRPS)

You can click
documentation.
documentation.
documentation.
Issue 03 (2015-07-30)

4172
Nastar
Netwo
rk
Parameter
Description
UMTS
VIP
Analysis
Data (CHR)

You can click

unavailable.
VIP
Analysis
Data (MR)
Issue 03 (2015-07-30)

You can click

4173
Nastar
Netwo
rk
Parameter
Description
LTE
FDD/
LTE
TDD
VIP
Analysis
Data (CHR)

You can click
measurement
MDT measurement
measurement
measurement
measurement
CSFB PREP, CSFB
Issue 03 (2015-07-30)

4174
Nastar
Netwo
rk
Parameter
Description
can be 1280(ms), 2560(ms), 5120(ms), 10240(ms), 20480
(ms), 30720(ms), 40960(ms), or 61440(ms).
600(s), 1200(s), 2400(s), 3600(s), 5400(s), or 7200(s). The
NOTE
Issue 03 (2015-07-30)

4175
Nastar
Netwo
rk
Parameter
Description
PS Core
VIP
Analysis
Data
(SGSN/
MMECHR)

You can click

settings.
settings.
Netwo
rk
Level
Parameter
Description
GSM
Group
Level
VIP Group
GSM CS NE
List
GSM PS NE
List
UTMS
Group
Level
Open VIP
Speciality
VIP Group
NE List
LTE
FDD/
LTE
TDD
Issue 03 (2015-07-30)
Group
Level
VIP Group
User Level
eNodeB
Interface
Select
NE List

4176
Nastar
Netwo
rk
PS
Core
Level
Group
Level
Parameter
Description
IMSI

Select
Trace
Reference No.

VIP Group

belongs.
HSS Name

to be delivered.
VIP Group
NE List

Parameter
Description
Task Name

Value range:
~!@#$%^&*()+{}[]\/|;':,.?<>"
Task Type
Remarks

Issue 03 (2015-07-30)

4177
Nastar
Parameter
Analysis Type
Description
Analysis
Scene

CN side
side
Access
Network
Type
Data Type 1

NOTE
Data Type 2

and the PS domain:
Select NEs
RAN NE
VIP Group
Select

NOTE
VIP analysis task.
Issue 03 (2015-07-30)
Group Name
Members
Description
Updated
Date

updated.

4178
Nastar
Parameter
Result
Threshold
Description
Network
Domain

Service Type

so on.
or Flow Type
or Service/
Flow Type

on.
type of the KPIs.
Indicator
Name

Criterion

Threshold

KPI.
analysis results.
provided.
Process
Threshold
Issue 03 (2015-07-30)
Network

NOTE
Use the result
counter of
Short Calls
(Calling
Party) in VIP
analysis results
as an example
to describe the
differences
between the
result
threshold and
the process
threshold.
Result
threshold:
Engineers can
set the result
threshold of
the Short
Calls (Calling
Party) counter
and detect VIP
subscribers
that have more
short calls.
Process
threshold:
Engineers need
to set the
process
threshold for
defining a
short call based
on the
preceding
analysis result
counter. For
example, If the
Service
Duration
(Calling
Party) of one
call is shorter
than the Short
Call
Threshold
(Calling
Party), the call
is called a short
call (calling
party).
4179
Nastar
Parameter
Description
Domain

Service Type

so on.
or Flow Type
or Service/
Flow Type

on.
type of the KPIs.
Indicator
Name

KPI indicators.
Criterion

Threshold

KPI.
provided.
Issue 03 (2015-07-30)

4180
Nastar
Parameter
Description
Duration
Delay
immediately.
Execute on

Param
eter
Description
Note
Start
time

Period

Week.
Repeat
times


periodic task]
Period.
Issue 03 (2015-07-30)

4181
Nastar
Param
eter
Description
Note
Delay
by
(hours)

task.
NOTE

NOTE
started).
Whole
day

03:00:00.
executes the task.

under Busy hours.
parameter.
Busy
hours

day as busy time.
busy time.
time.
Issue 03 (2015-07-30)

4182
Nastar
Parameter
Description
Sendin
g
Analysi
s
Reports
Setting
Automatically
send analysis
reports via
emails
Target email

Email subject

Email
contents

indicators.
analysis result.
Attachment

Settings function.
directly.
mails.


NOTE
Issue 03 (2015-07-30)

4183
Nastar
Opening the Window

l
methods):
in the front
) directly.

l

Main Window
Issue 03 (2015-07-30)

4184
Nastar
No.
l

1. Click
default.
type is GSM PS.

Issue 03 (2015-07-30)

Analysis.

4185
Nastar
No.
Analysis
result tab
page

Cell.
Network.

Issue 03 (2015-07-30)

4186
Nastar
No.
Parameter
Description
(1)
Analysis
object
l User
4.
NOTE
(2)

selection area
NOTE
(3)

selection area
service type node.
NOTE
Issue 03 (2015-07-30)

4187
Nastar
No.
Parameter
Description
(4)
Counter
overview
information
table

click


NOTE
analysis.
(5)
Active cell
information
table
(6)
table
(7)
table
Issue 03 (2015-07-30)

4188
Nastar
No.
Parameter
Description
(8)
Active TAC
information
table

by the LTE network.

No.
Parameter
Description
(1)
Analysis
object
in area 4.
l Cell
Issue 03 (2015-07-30)

4189
Nastar
No.
Parameter
Description
(2)

selection area
NOTE
(3)

selection area
(4)
Counter
overview
information
table

(5)
Active VIP
subscriber
information
table

Issue 03 (2015-07-30)

4190
Nastar
No.
Parameter
Description
(1)
Analysis object
selection area

l Server
NOTE
IP:Server Name.
l Port
(2)
(3)
Service type
selection area
Counter set
selection area
NOTE
(4)
(5)
Active VIP
subscriber
information table

Click
Figure 6-25.
Issue 03 (2015-07-30)

4191
Nastar
No.
Feature
Description
(1)
Button area

(2)
Navigation
tree in the
Geographic
Observation
window
NOTE

cell KPI.
deleted.
Issue 03 (2015-07-30)

4192
Nastar
No.
Feature
Description
(3)
Geographic
observation
area
(4)
Grid detail
area
(5)
Legend area

click the
(6)
Information
area


NOTE
Opening the Window

l
Main Window
results.
Issue 03 (2015-07-30)

4193
Nastar
No.
1. Click
Issue 03 (2015-07-30)

4194
Nastar
No.
Area for
setting
filtering
criteria

NOTE

criteria.
1. Click

criteria.
9. Click OK.
NOTE
Issue 03 (2015-07-30)
Service
type
selection
area

4195
Nastar
No.
Counter
type
selection
area
Trend
analysis
chart

NOTE

the trend chart.
save data.
6
Trend
analysis
table
N.
NOTE
Issue 03 (2015-07-30)

4196
Nastar
No.
Area for
setting
trend
analysis
mode



Issue 03 (2015-07-30)

4197
Nastar
Common
Parameter
Range
Unit
Description
Supported
Solution
Version
In-depth
Analysis
N/A
N/A
When the
dimension is
Group, this
parameter is
used to switch
from the
analysis results
of a VIP group
to the analysis
results of VIP
subscribers in
this group.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
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
group.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
User ID
[1,+)
N/A
Identity of a VIP
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
User ID, which

is created by the
system when
creating a VIP
User in the VIP
Group
Management.
Issue 03 (2015-07-30)

4198
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Alias
N/A
N/A
Alias of a VIP
subscriber.
Query the name
of a VIP
subscriber using
VIP group
management
based on the
IMSI of the VIP
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
IMSI
N/A
N/A
IMSI
information of a
subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Note: Only
when you have
the "User
Identity" right,
you can view the
IMSI
information.
IMEI-TAC
00000000-9999
9999
N/A
First eight digits

in the IMEI of a
UE.
IMEI is
international
mobile
equipment
identity for short
and TAC is type
approval code
for short.
Terminal Model
Issue 03 (2015-07-30)
N/A
N/A
Type of the UE
used by a VIP
subscriber.
Query the UE
type of a VIP
subscriber using
terminal type
management
based on the
IMEI-TAC of
the VIP
subscriber.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
4199
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Service Type
N/A
N/A
Service type for

a counter.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Number of
Abnormal
Indicator
[0,+)
Number
Number of
abnormal
counters in all
counter sets
determined
based on the
result thresholds
set when
engineers create
a task.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Total Reports
[0,+)
Number
Indicates the
number of
records
generated for all
service types
during the
network access
of a subscriber.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Accessibility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
[0,+)
Number

setup requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4200
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Number
Number of
service RRC
setup requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Requests
[0,+)
Number
Number of RRC
reestablishment
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Number
Number of
failed RRC
reestablishment
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Success Rate
[0,100]
RRC
reestablishment
success rate.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
intra-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Mobility
Issue 03 (2015-07-30)

4201
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handovers after
a UE initiates
intra-RAT
outgoing
handover
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Success Rate
[0,100]
Ratio of
handovers to
intra-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
intra-RAT
outgoing
handover
requests during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Success Rate
(with Data
Transmission)
[0,100]
Ratio of
handovers to
intra-RAT
outgoing
handover
requests
initiated by a UE
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4202
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Success Rate
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4203
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Success Rate
(with Data
Transmission)
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a UE
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Success
Rate
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4204
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through CSFB
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Success
Rate (with Data
Transmission)
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through CSFB
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a UE
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4205
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Success Rate
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handovers after
a UE initiates
inter-RAT
outgoing
handover
requests
through
SRVCC during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Success Rate
(with Data
Transmission)
[0,100]
Ratio of
handovers to
inter-RAT
outgoing
handover
requests
initiated by a UE
through
SRVCC during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Issue 03 (2015-07-30)

4206
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Requests
[0,+)
Number

Evolved Radio
Access Bearer)
setup requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Number
Number of
failed E-RAB
setups after a
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Rate
[0,100]
Ratio of
E-RAB setup
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4207
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version

Times
[0,+)
Number
Number of
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate
[0,100]
Ratio of
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Times (with
Data
Transmission)
[0,+)
Number
Number of
with data
transmission
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate (with Data
Transmission)
[0,100]
Ratio of
with data
transmission
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4208
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB Setup

Delay
[0,+)
Second
Average ERAB setup

delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB setup

delay = E-RAB
setup delay/
delay reports
The E-RAB
setup delay
indicates the
duration from
the time when
the Initial
Context Setup
Request
message is sent
to the time when
the Initial
Context Setup
Response
message is
received or that
from the time
when the ERAB Setup
Request
message is sent
to the time when
the E-RAB
Setup Response
message is
received.
Issue 03 (2015-07-30)

4209
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Long E-RAB
Setup Delay
Times
[0,+)
Number
Number of
times when the
E-RAB setup
delay is greater
delay threshold.
The threshold is
set during
analysis task
creation.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion of
long E-RAB
Setup Delay
[0,100]

delay to the
delay reports.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0,+)
Second

recorded in a
report.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4210
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink VQI
[1.00,5.00]
N/A
Average value
for the downlink
voice quality
indicators
(VQIs) of
successful call
setups.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
VQI is the Mean

Opinion Score
(MOS) and
indicates the
voice quality of
a call. The value
of the voice
quality ranges
from 1 to 5. A
larger value
indicates better
voice quality.
Average value
for the downlink
VQIs of
successful call
setups =
Aggregated
value of
downlink VQIs/
Total number of
downlink VQI
tests
Poor Downlink
VQI Times
[0,+)
Number
Number of poor
downlink VQIs.
The exception
threshold is set
by engineers
during task
creation.
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
4211
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Uplink VQI
[1.00,5.00]
N/A
Average value
for the uplink
VQIs of
successful call
setups.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
VQI is the MOS

and indicates the
voice quality of
a call. The value
of the voice
quality ranges
from 1 to 5. A
larger value
indicates better
voice quality.
Average value
for the uplink
VQIs of
successful call
setups =
Aggregated
value of uplink
VQIs/Total
number of
uplink VQI tests
Poor Uplink
VQI Times
[0,+)
Number
Number of poor
uplink VQIs.
The exception
threshold is set
by engineers
during task
creation.
Issue 03 (2015-07-30)

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
4212
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
(MB)
[0,+)
MB
Total downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Transmission
Duration(s)
[0,+)
Second
Average
downlink data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Throughput
[0,+)
kbit/s
Average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
downlink
throughput =
Total downlink
throughput/
Total downlink
data
transmission
duration
Issue 03 (2015-07-30)

4213
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Low Average
Downlink
Throughput
Times
[0,+)
Number
Number of
times when the
average
downlink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
Uplink Traffic
Volume(MB)
[0,+)
MB
Total uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Transmission
Duration(s)
[0,+)
Second
Average uplink
data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0,+)
kbit/s
Average uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average uplink
throughput =
Total uplink
throughput/
Total uplink
data
transmission
duration
Issue 03 (2015-07-30)

4214
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Low Average
Uplink
Throughput
Times
[0,+)
Number
Number of
times when the
average uplink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Requests
[0,+)
Number

requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Number
Number of
failed E-RAB
setups after a
requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4215
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Rate
[0,100]
Ratio of
E-RAB setup
requests
initiated by a
UE.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Times
[0,+)
Number
Number of
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate
[0,100]
Ratio of
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4216
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version

Times (with
Data
Transmission)
[0,+)
Number
Number of
with data
transmission
due to E-RAB
exceptions
among
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Rate(with Data
Transmission)
[0,100]
Ratio of
with data
transmission
due to E-RAB
exceptions to
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Success Times
[0,+)
Number
Number of
after a UE
initiates E-RAB
setup requests.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4217
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average ERAB Setup

Delay
[0,+)
Second
Average ERAB setup

delay.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average ERAB setup

delay = E-RAB
setup delay/
delay reports
The E-RAB
setup delay
indicates the
duration from
the time when
the Initial
Context Setup
Request
message is sent
to the time when
the Initial
Context Setup
Response
message is
received or that
from the time
when the ERAB Setup
Request
message is sent
to the time when
the E-RAB
Setup Response
message is
received.
Issue 03 (2015-07-30)

4218
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Long E-RAB
Setup Delay
Times
[0,+)
Number
This parameter
indicates the
number of times
when the ERAB setup
delay is greater
delay threshold.
The threshold is
set during
analysis task
creation.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Proportion of
long E-RAB
Setup Delay
[0,100]

delay to the
delay reports.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
[0,+)
Second
Average ERAB
occupation
duration
recorded in a
report.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Downlink
Traffic Volume
[0,+)
MB
Total downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4219
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average
Downlink
Transmission
Duration
[0,+)
Second
Average
downlink data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
Downlink
Throughput
[0,+)
kbit/s
Average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average
downlink
throughput =
Total downlink
throughput/
Total downlink
data
transmission
duration
Low Average
Downlink
Throughput
Times
[0,+)
Number
Number of
times when the
average
downlink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
downlink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.
Uplink Traffic
Volume
Issue 03 (2015-07-30)
[0,+)
MB
Total uplink
throughput of
PS services.

eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
4220
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Average Uplink
Transmission
Duration
[0,+)
Second
Average uplink
data
transmission
duration of PS
services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average Uplink
Throughput
[0,+)
kbit/s
Average uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Average uplink
throughput =
Total uplink
throughput/
Total uplink
data
transmission
duration
Low Average
Uplink
Throughput
Times
[0,+)
Number
Number of
times when the
average uplink
throughput in
one E-RAB
setup request is
smaller than the
exception
threshold for
low average
uplink
throughput of
PS services.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
The exception
threshold is set
by engineers
during task
creation.

Issue 03 (2015-07-30)

4221
Nastar
Common
Parameter
Range
Unit
Description
Supported
Solution
Version
eNodeB ID
N/A
N/A
ID of an eNodeB.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
eNodeB Name
1 to 64
charact
ers
N/A
Name of an eNodeB.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
Cell ID
N/A
N/A
ID of a cell.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
Cell Name
1 to 64
charact
ers
N/A
Name of a cell.
eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
N/A
N/A
Service Type


eRAN 6.0/eRAN
6.1/eRAN 7.0/
eRAN 8.0/eRAN
8.1/eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
[0,+)
Number

setup requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4222
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
RRC Setup
Requests
(Service)
[0,+)
Number
Number of
service RRC
setup requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Requests
[0,+)
Number
Number of RRC
reestablishment
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Number
Number of
failed RRC
reestablishment
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
intra-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RAN NET-Mobility
Issue 03 (2015-07-30)

4223
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4224
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Incoming
Handover
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4225
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through CSFB.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through CSFB
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Number
Number of
inter-RAT
outgoing
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through
SRVCC.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4226
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Number
Number of
handover
requests
initiated by a
VIP group or
VIP subscriber
in an active cell
through
SRVCC during
data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
E-RAB Setup
Requests
[0,+)
Number

requests
initiated by a
VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Number
Number of
failed E-RAB
setups initiated
by a VIP group
or VIP
subscriber in an
active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4227
Nastar

Parameter
Range
Unit
Description
Supported
Solution
Version

Times
[0,+)
Number
Number of
a VIP group or
VIP subscriber
in an active cell.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Times (with
Data
Transmission)
[0,+)
Number
Number of
a VIP group or
VIP subscriber
in an active cell
during data
transmission.
eRAN 6.0/
eRAN 6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Common
Parameter
Ran
ge
Unit
Description
Supported
Solution Version
MME
N/A
N/A
ID of a MME.
eRAN 6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
MME format:
MMEGroupIDMMECode
Service Type
Issue 03 (2015-07-30)
N/A
N/A
Service type for a

counter.

eRAN6.0/
eRAN6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
4228
Nastar
RAN NET-Mobility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of intra-RAT
outgoing handover
an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4229
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Numb
er

CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Numb
er

CSFB during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Numb
er

SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4230
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Numb
er

SRVCC during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Parameter
Range
Unit
Description
Supported
Solution Version
E-RAB Setup
Requests
[0,+)
Numbe
r
Number of E-RAB
setup requests
initiated by a VIP
group or VIP
subscriber in an
active mme.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Numbe
r

by a VIP group or
active mme.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
mme.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

4231
Nastar
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times (with
Data
Transmission)
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
mme during data
transmission.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported Solution
Version
E-RAB Setup
Success Times
[0,+)
Nu
mbe
r
UE initiates E-RAB
setup requests.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average E-RAB
Setup Delay(s)
[0,+)
Sec
ond
Average E-RAB setup

setup delay = E-RAB
E-RAB setup delay
reports The E-RAB
Context Setup
Response message is
time when the E-RAB
the E-RAB Setup
Response message is
received.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

4232
Nastar

Parameter
Range
Uni
t
Description
Supported Solution
Version
Downlink VQI
[1.00,5.00]
N/A

eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the Mean

Opinion Score (MOS)
value of the voice
5. A larger value
quality.
downlink VQIs of
Aggregated value of
downlink VQIs/Total
number of downlink
VQI tests
Uplink VQI
[1.00,5.00]
N/A

uplink VQIs of
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the MOS and

indicates the voice
value of the voice
5. A larger value
quality.
uplink VQIs of
Aggregated value of
uplink VQIs/Total
tests
Issue 03 (2015-07-30)

4233
Nastar

Evaluation for Rate
Parameter
Range
Unit
Description
Supported Solution
Version
Downlink
Traffic Volume
(MB)
[0,+)
MB
Total downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Downlink
Transmission
Duration(s)
[0,+)
Downlink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average
Downlink
Throughput
(kbit/s)
[0,+)
kbit/s
Average downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink Traffic
Volume(MB)
[0,+)
MB

of PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink
Transmission
Duration(s)
[0,+)
Secon
d
Uplink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average Uplink
Throughput
(kbit/s)
[0,+)
kbit/s
Average uplink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average downlink
throughput = Total
Total downlink data
Average uplink
throughput = Total
uplink data

Issue 03 (2015-07-30)

4234
Nastar
Common
Parameter
Ran
ge
Unit
Description
Supported
Solution Version
TAC
[0,65
535]
N/A
Indicates the
tracking area code
of a cell.
eRAN6.0/
eRAN6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
Service Type
N/A
N/A
Service type for a

counter.
eRAN6.0/
eRAN6.1/eRAN
7.0/eRAN 8.0/
eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
Un
it
Description
Supported
Solution
Version
RRC Setup
[0,+)
Nu
mb
er

in an active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Setup
Requests
(Service)
[0,+)
Nu
mb
er

active mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Requests
[0,+)
Nu
mb
er
Number of RRC
mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
RRC Reestablishment
Failures
[0,+)
Nu
mb
er

mme.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4235
Nastar
RAN NET-Mobility
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Intra-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of intra-RAT
outgoing handover
an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Intra-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4236
Nastar
Issue 03 (2015-07-30)
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Incoming
Handover
Failures
[0,+)
Numb
er

an active cell.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
Failures (with
Data
Transmission)
[0,+)
Numb
er

transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
[0,+)
Numb
er

CSFB.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
CSFB Failures
(with Data
Transmission)
[0,+)
Numb
er

CSFB during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Requests
[0,+)
Numb
er
Number of inter-RAT
outgoing handover
SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0
Inter-RAT
Outgoing
Handover
SRVCC
Failures
[0,+)
Numb
er

SRVCC.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

4237
Nastar
Parameter
Range
Unit
Description
Supported
Solution
Version
Inter-RAT
Outgoing
Handover
SRVCC
Failures (with
Data
Transmission)
[0,+)
Numb
er

SRVCC during data
transmission.
eRAN6.0/
eRAN6.1/
eRAN 7.0/
eRAN 8.0/
eRAN 8.1/
eRAN11.0

Parameter
Range
Unit
Description
Supported
Solution Version
E-RAB Setup
Requests
[0,+)
Numbe
r
Number of E-RAB
setup requests
initiated by a VIP
group or VIP
subscriber in an
active cell.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
E-RAB Setup
Failures
[0,+)
Numbe
r

by a VIP group or
active cell.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN
8.0/eRAN 8.1/
eRAN11.0
Issue 03 (2015-07-30)
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
cell.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

4238
Nastar
Parameter
Range
U
ni
t
Description
Supported Solution
Version

Times (with
Data
Transmission)
[0,+)
N
u
m
be
r
Number of abnormal
E-RAB releases of a
VIP group or VIP
cell during data
transmission.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

Issue 03 (2015-07-30)
Parameter
Range
Uni
t
Description
Supported Solution
Version
E-RAB Setup
Success Times
[0,+)
Nu
mbe
r
UE initiates E-RAB
setup requests.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average E-RAB
Setup Delay(s)
[0,+)
Sec
ond
Average E-RAB setup

setup delay = E-RAB
E-RAB setup delay
reports The E-RAB
Context Setup
Response message is
time when the E-RAB
the E-RAB Setup
Response message is
received.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0

4239
Nastar

Parameter
Range
Uni
t
Description
Supported Solution
Version
Downlink VQI
[1.00,5.00]
N/A

eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the Mean

Opinion Score (MOS)
value of the voice
5. A larger value
quality.
downlink VQIs of
Aggregated value of
downlink VQIs/Total
number of downlink
VQI tests
Uplink VQI
[1.00,5.00]
N/A

uplink VQIs of
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
VQI is the MOS and

indicates the voice
value of the voice
5. A larger value
quality.
uplink VQIs of
Aggregated value of
uplink VQIs/Total
tests
Issue 03 (2015-07-30)

4240
Nastar

Evaluation for Rate
Parameter
Range
Unit
Description
Supported Solution
Version
Downlink
Traffic Volume
(MB)
[0,+)
MB
Total downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Downlink
Transmission
Duration(s)
[0,+)
Downlink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average
Downlink
Throughput
(kbit/s)
[0,+)
kbit/s
Average downlink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink Traffic
Volume(MB)
[0,+)
MB

of PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Uplink
Transmission
Duration(s)
[0,+)
Secon
d
Uplink data
PS services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average Uplink
Throughput
(kbit/s)
[0,+)
kbit/s
Average uplink
throughput of PS
services.
eRAN6.0/eRAN6.1/
eRAN 7.0/eRAN 8.0/
eRAN 8.1/eRAN11.0
Average downlink
throughput = Total
Total downlink data
Average uplink
throughput = Total
uplink data


Issue 03 (2015-07-30)

4241
Nastar
Common
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Deep
Analysis
N/A
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0

l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

4242
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Group
Name
N/A
N/A
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

4243
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
User ID
N/A
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

4244
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Alias
N/A
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

4245
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
IMSI
N/A
N/A
l SRAN8.
0/
GBSS15
.0/RAN
15.0

l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

4246
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
IMEITAC
0000
0000
9999
9999
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

4247
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Terminal
Model
N/A
N/A

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

4248
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Service
Type
N/A
N/A
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

4249
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Number
of
Abnormal
KPIs
[0,
+)
Numb
er

l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0
Issue 03 (2015-07-30)

4250
Nastar
Paramet
er
Ran
ge
Unit
Description
Supported
Solution
Version
Total
Reports
[0,
+)
Numb
er

subscriber.
l SRAN8.
0/
GBSS15
.0/RAN
15.0
l SRAN8.
1/
GBSS15
.1/RAN
15.1
l SRAN9.
0/
GBSS16
.0/
RAN16.
0
l SRAN1
0.0/
GBSS17
.0/
RAN17.
0
l SRAN1
0.1/
GBSS17
.1/
RAN17.
1
l SRAN1
1.0/
GBSS18
.0/
RAN18.
0

Issue 03 (2015-07-30)

4251
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Acces
s
Reque
sts
(IntraRAT)
[0,
+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acces
s
Failur
es
(IntraRAT)
[0,
+)
Number

current system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4252
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Acces
s
Reque
sts
(InterRAT)
[0,
+)
Number

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Acces
s
Failur
es
(InterRAT)
[0,
+)
Number

another system.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4253
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Avera
ge TA
on
Acces
s
[0,63
]
N/A

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Abnor
mal
TAs
on
Acces
s
[0,
+)
Number

network.
create a task.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4254
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Ratio
of
Abnor
mal
TAs
on
Acces
s
[0.00,
100.0
0]

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Avera
ge
RAC
H
Level
on
Acces
s
[-110
,-47]
dBm

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4255
Nastar
Para
meter
Ran
ge
Unit
Description
Supported
Solution
Version
Abnor
mal
RAC
H
Levels
on
Acces
s
[0,
+)
Number

network.
l SRAN8.0/
GBSS15.0/
RAN 15.0

create a task.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio
of
Abnor
mal
RAC
H
Levels
on
Acces
s
[0.00,
100.0
0]

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4256
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Relea
ses
(Intra
RAT)
[0,
+)
Numb
er

l SRAN8.0
/
GBSS15.
0/RAN
15.0

l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

4257
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Abno
rmal
Relea
ses
(Intra
RAT)
[0,
+)
Numb
er

l SRAN8.0
/
GBSS15.
0/RAN
15.0
l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

4258
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Relea
ses
(Inter
RAT)
[0,
+)
Numb
er

l SRAN8.0
/
GBSS15.
0/RAN
15.0

l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

4259
Nastar
Para
mete
r
Rang
e
Unit
Description
Supported
Solution
Version
Abno
rmal
Relea
ses
(Inter
RAT)
[0,
+)
Numb
er

l SRAN8.0
/
GBSS15.
0/RAN
15.0

l SRAN8.1
/
GBSS15.
1/RAN
15.1
l SRAN9.0
/
GBSS16.
0/
RAN16.0
l SRAN10.
0/
GBSS17.
0/
RAN17.0
l SRAN10.
1/
GBSS17.
1/
RAN17.1
l SRAN11.
0/
GBSS18.
0/
RAN18.0
Issue 03 (2015-07-30)

4260
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
Hard
Handover
Requests
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Hard
Handover
Failures
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4261
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
Hard
Handover
Success
Times
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
Outgoing
Handover
Requests
[0,+)
Num
ber

the command.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4262
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
InterRAT
Outgoing
Handover
Failures
(Normal
Release)
[0,+)
Num
ber

the GSM network.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
Outgoing
Handover
Failures
(Abnorm
al
Release)
[0,+)
Num
ber

a service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4263
Nastar
Paramet
er
Range
Unit
Description
Supported
Solution Version
InterRAT
Incoming
Handover
Requests
[0,+)
Num
ber

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
InterRAT
Incoming
Handover
Failures
[0,+)
Num
ber

during a service.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4264
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Total
Call
Setup
Reques
ts
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Failure
s
[0,
+)
Numb
er

call.
message.
l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4265
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Abnor
mal
Release
Before
Call
Compl
etion
[0,
+)
Numb
er

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Setup
Succes
s Times
[0,
+)
Numb
er

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4266
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Call
Compl
etion
(Alerti
ng)
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Compl
etion
(Conne
ct Ack)
[0,
+)
Numb
er

l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4267
Nastar
Param
eter
Ran
ge
Unit
Description
Supported
Solution
Version
Call
Compl
etion
Succes
s Rate
(Alerti
ng)
[0.00
,
100.
00]

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Compl
etion
Succes
s Rate
(Conne
ct Ack)
[0.00
,
100.
00]

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4268
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution Version
Call
Setup
Success
Times
[0,
+)
Num
ber

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Alerting message.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Call
Complet
ion
(Connec
t Ack)
[0,
+)
Num
ber

l SRAN8.0/
GBSS15.0/
RAN 15.0
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4269
Nastar
Parame
ter
Rang
e
Unit
Description
Supported
Solution Version
Abnorm
al Call
Releases
[0,
+)
Num
ber

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

release:
abnormal one.
subscriber.
fails.
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0

Abnorm
al Call
Rate
[0.00,
100.00
]

initiates a call.
l SRAN8.0/
GBSS15.0/
RAN 15.0

Ack) x 100%
l SRAN8.1/
GBSS15.1/
RAN 15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4270
Nastar

Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Access
Delays
(MOC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Access
Delay
(MOC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4271
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Access
Delays
(MOC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Access
Delays
(MOC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4272
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Access
Delays
(MTC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Access
Delay
(MTC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4273
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Access
Delays
(MTC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Access
Delays
(MTC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4274
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Times of
Call
Complet
ion
Delay
(Alertin
g)
(MOC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Call
Complet
ion
Delay
(Alertin
g)
(MOC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4275
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MOC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0

create a task.
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Ratio of
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MOC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4276
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Average
Call
Complet
ion
Delay
(Connec
t Ack)
(MOC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MOC)
[0,
+)
Numbe
r

create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4277
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Ratio of
Overlon
g Call
Complet
ion
Delays
(Connec
t Ack)
(MOC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Times of
Call
Complet
ion
Delay
(Alertin
g)
(MTC)
[0,
+)
Numbe
r

l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4278
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Average
Call
Complet
ion
Delay
(Alertin
g)
(MTC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MTC)
[0,
+)
Numbe
r

create a task.
l SRAN8.0/
GBSS15.0/RAN
15.0
l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4279
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Ratio of
Overlon
g Call
Complet
ion
Delays
(Alertin
g)
(MTC)
[0.00
,
100.0
0]

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Average
Call
Complet
ion
Delay
(Connec
t Ack)
(MTC)
[0,
+)
Second

l SRAN8.0/
GBSS15.0/RAN
15.0

l SRAN8.1/
GBSS15.1/RAN
15.1
l SRAN9.0/
GBSS16.0/
RAN16.0
l SRAN10.0/
GBSS17.0/
RAN17.0
l SRAN10.1/
GBSS17.1/
RAN17.1
l SRAN11.0/
GBSS18.0/
RAN18.0
Issue 03 (2015-07-30)

4280
Nastar
Parame
ter
Ran
ge
Unit
Description
Supported
Solution Version
Overlon
g Call
Complet

Nastar Network Optimization User Guide (V600R015C00 - 03) (PDF) - EN PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nastar Network Optimization User Guide (V600R015C00 - 03) (PDF) - EN PDF

Uploaded by

Copyright:

Available Formats

Nastar

Network Optimization User Guide

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Network optimization engineers

Huawei Proprietary and Confidential

About This Document

6.1.3 Process of LTE Coverage Analysis

6.2.3 Process of LTE Cell Performance

Huawei Proprietary and Confidential

About This Document

4.10 Complaint Analysis Support

Parameters for Viewing PS Core VIP Analysis

3.3.4 Configuring OSS Information

Configuring SAU or LTE SAU Information

Configuring SAU or LTE SAU Information

3.5.2 Basic Subscription of Analysis Data

Huawei Proprietary and Confidential

3 Nastar Quick Start.......................................................................................................................29

Huawei Proprietary and Confidential

3.4 Preparing Basic Data....................................................................................................................................................92

Huawei Proprietary and Confidential

4 GSM Network Optimization..................................................................................................191

Huawei Proprietary and Confidential

4.7.4 Interface Description: GSM Cell Performance Analysis.........................................................................................667

5 UMTS Network Optimization..............................................................................................2093

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

5.9.3 Process of UMTS Network Geographic Observation...........................................................................................2549

6 LTE Network Optimization...................................................................................................3947

Huawei Proprietary and Confidential

6.3.4 Interface Description: LTE Terminal Analysis.....................................................................................................4048

7 PS Core Network Optimization............................................................................................5493

Huawei Proprietary and Confidential

7.2.3 Process of Root Cause Analysis for PS Core Performance Problems...................................................................5560

Huawei Proprietary and Confidential

8.2 Security Management...............................................................................................................................................7107

Huawei Proprietary and Confidential

8.6.7 Interface Reference for System Monitoring..........................................................................................................7558

9 Nastar Alarm Reference.........................................................................................................7620

Huawei Proprietary and Confidential

9.26 ALM-129 The Digital Certificate Is Invalid...........................................................................................................7680

Huawei Proprietary and Confidential

9.67 ALM-50066 ATAE Board Is Not Present..............................................................................................................7773

Huawei Proprietary and Confidential

1 About This Help

About This Help

About This Chapter

Huawei Proprietary and Confidential

1 About This Help

1.1 Intended Audience

Buttons, menus, parameters, tab pages, windows, and dialog box

The OK and Apply buttons

The Default button

Multiple accesses to an operation

Huawei Proprietary and Confidential