Professional Documents
Culture Documents
Copyright Huawei Technologies Co., Ltd. 2013. 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.
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.
Website: Email:
Issue 01 (2013-07-15)
Product Version
The products described in this guide are as follows: Product Name Nastar Product Version V600R011
Intended Audience
This document is intended for network optimization engineers.
Change History
Issue 01 (2013-07-15)
This is the first formal release.
Organization
1 Nastar Overview Nastar provides a complete solution for wireless network performance analysis. It is applicable to GSM/GPRS/EDGE, UMTS/HSUPA/HSDPA, LTE TDD/LTE FDD, and PS Core networks. This solution can deeply analyze and locate wireless network problems and supports user experience-based performance optimization and location-based network evaluation. 2 Nastar Quick Start This chapter describes the basic ideas and operations for network optimization and describes the Nastar operation processes by using examples. Only basic Nastar operations are described in this section. It is especially useful to new users. It is recommended that you read this section when using the Nastar the first time. If you are familiar with Nastar basic operations, refer to chapters named in *** Network Optimization format to perform theme analysis. 3 GSM Network Optimization This section describes how to perform GSM network optimization on the Nastar. Through this function, you can perform various theme analysis functions on the Nastar, such as MR analysis, frequency analysis, neighboring cell analysis, GSM/UMTS neighboring cell analysis, VIP analysis, complaint analysis support, terminal analysis, and network geographic observation. It is especially useful to users who are familiar with the Nastar basic operations. It is recommended that you read this section when using the Nastar for the GSM network optimization. If you use the Nastar in the first time, refer to Nastar Quick Start chapters. 4 UMTS Network Optimization The Nastar provides network optimization function. The network optimization function helps you perform various UMTS theme analyses on the Nastar, including coverage analysis, 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 LTE Network Optimization This section describes how to perform LTE network optimization on the Nastar. Through this function, you can perform various theme analysis functions on the Nastar, such as coverage analysis, VIP analysis, complaint analysis support, network geographic observation. This helps to quickly locate network problems. It is especially useful to users who are familiar with the Nastar basic operations. It is recommended that you read this section when using the Nastar for the LTE network optimization. If you use the Nastar in the first time, refer to Nastar Quick Start chapters. 6 System Management
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
The system management includes the following parts, such as security management, log management, task management, and monitoring the Nastar system. You can manage the Nastar and monitor the running status of the Nastar through the functions.
Conventions
Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level or medium level of risk which, if not avoided, could result in death or serious injury. Indicates a hazard with a low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
Command Conventions The command conventions that may be found in this document are defined as follows. Convention Boldface
Issue 01 (2013-07-15)
Description Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operations The mouse operations that may be found in this document are defined as follows.
Issue 01 (2013-07-15)
Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Issue 01 (2013-07-15)
vi
Contents
Contents
About This Document.....................................................................................................................ii 1 Nastar Overview............................................................................................................................1
1.1 Position in Networking...................................................................................................................................................2 1.2 Product Functions...........................................................................................................................................................4 1.3 Basic Concept/Glossary..................................................................................................................................................7
Contents
2.5.1 Basics of Data Subscription.....................................................................................................................................101 2.5.2 Basic Subscription of Analysis Data.......................................................................................................................104 2.5.3 Application Subscription of Analysis Data.............................................................................................................107 2.5.4 Appendix: List of Data Subscription Function of All the Analysis Function.........................................................110 2.6 Checking the Integrity of Analysis Data....................................................................................................................119 2.7 Creating an Analysis Task..........................................................................................................................................120 2.8 Querying Analysis Results.........................................................................................................................................124 2.9 Viewing Geographic Analysis Results (Optional).....................................................................................................125 2.10 Exporting Analysis Reports......................................................................................................................................125 2.11 FAQs.........................................................................................................................................................................126 2.11.1 What Do I Do When I Fail to Open the Excel File Exported from the Nastar?....................................................126 2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key....................................................................................................................................................................................127 2.11.3 Supporting Historical Data Analysis on a Changed NE........................................................................................128 2.11.4 Nastar Fails to Identify Information in Non-Specified Languages.......................................................................129 2.11.5 Why Cannot the Nastar Client Be Displayed Again?............................................................................................130 2.11.6 What Do I Do if the System Displays Login M2000 Failed When a Nastar Basic Data Subscription Task Fails?.................................................................................................................................................................................130 2.11.7 Failed NE Version Upgrade Causes Failures in Subscribing To Basic Data for Some Themes...........................131 2.11.8 Data Subscription Failures in Some Themes Due to the Reconstruction of Existing RNCs into RNC Pools ..........................................................................................................................................................................................132
Contents
3.4.3 Process of GSM/UMTS Neighboring Cell Analysis...............................................................................................323 3.4.4 Reference for GSM/UMTS Neighboring Cell Analysis Interface..........................................................................330 3.4.5 Reference for GSM/UMTS Neighboring Cell Analysis Parameters.......................................................................335 3.5 GSM Uplink Interference Analysis............................................................................................................................350 3.5.1 Basics of GSM Uplink Interference Analysis.........................................................................................................350 3.5.2 Preparations for GSM Uplink Interference Analysis...............................................................................................355 3.5.3 Process of GSM Uplink Interference Analysis........................................................................................................356 3.5.4 Interface Description: GSM Uplink Interference Analysis.....................................................................................361 3.5.5 Parameters for Viewing GSM Uplink Interference Analysis Results.....................................................................363 3.6 GSM Terminal Analysis.............................................................................................................................................366 3.6.1 Basics of GSM Terminal Analysis..........................................................................................................................366 3.6.2 Preparations for GSM Terminal Analysis...............................................................................................................370 3.6.3 Process of GSM Terminal Analysis........................................................................................................................372 3.6.4 Interface Description: GSM Terminal Analysis......................................................................................................381 3.6.5 Parameters for Viewing GSM Terminal Analysis Results......................................................................................389 3.7 GSM Cell Performance Analysis...............................................................................................................................422 3.7.1 Basics of GSM Cell Performance Analysis.............................................................................................................422 3.7.2 Preparations for GSM Cell Performance Analysis..................................................................................................426 3.7.3 Process of GSM Cell Performance Analysis...........................................................................................................427 3.7.4 Interface Description: GSM Cell Performance Analysis.........................................................................................435 3.7.5 Parameters for Viewing GSM Cell Performance Analysis Results........................................................................437 3.8 GSM Network Geographic Observation....................................................................................................................461 3.8.1 Basics of GSM Network Geographic Observation..................................................................................................461 3.8.2 Preparations for GSM Network Geographic Observation.......................................................................................465 3.8.3 Process of GSM Network Geographic Observation................................................................................................467 3.8.4 Interface Description: GSM Network Geographic Observation.............................................................................476 3.8.5 Parameters for Viewing GSM Network Geographic Observation Results.............................................................479 3.9 VIP Analysis...............................................................................................................................................................482 3.9.1 Basics of VIP Analysis............................................................................................................................................483 3.9.2 Preparations for VIP Analysis.................................................................................................................................493 3.9.3 Process of VIP Analysis..........................................................................................................................................499 3.9.4 Reference for VIP Analysis Interface......................................................................................................................514 3.9.5 Reference for VIP Analysis Parameters (GSM)......................................................................................................526 3.9.6 Reference for VIP Analysis Parameters (UMTS)...................................................................................................567 3.9.7 Reference for VIP Analysis Parameters (LTE).......................................................................................................630 3.9.8 Reference for VIP Analysis Parameters (PS Core).................................................................................................635 3.10 Complaint Analysis Support.....................................................................................................................................661 3.10.1 Basics of Complaint Analysis Support..................................................................................................................662 3.10.2 Preparations for Complaint Analysis Support.......................................................................................................668 3.10.3 Process of Complaint Analysis Support................................................................................................................676 3.10.4 Reference for Complaint Analysis Support Interface............................................................................................686 3.10.5 Reference for Complaint Analysis Support Parameters (GSM)............................................................................715 Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
3.10.6 Reference for Complaint Analysis Support Parameters (UMTS).........................................................................774 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).............................................................................853 3.10.8 Reference for Complaint Analysis Support Parameters (PS Core).......................................................................877 3.10.9 Appendix: Exception Cause Classification / Key Signaling.................................................................................908
Contents
4.7.1 Basics of UMTS Terminal Analysis......................................................................................................................1114 4.7.2 Preparations for UMTS Terminal Analysis...........................................................................................................1117 4.7.3 Process of UMTS Terminal Analysis....................................................................................................................1119 4.7.4 Interface Description: UMTS Terminal Analysis..................................................................................................1129 4.7.5 Parameters for Viewing UMTS Terminal Analysis Results.................................................................................1136 4.8 UMTS Cell Performance Analysis...........................................................................................................................1156 4.8.1 Basics of UMTS Cell Performance Analysis........................................................................................................1156 4.8.2 Preparations for UMTS Cell Performance Analysis.............................................................................................1160 4.8.3 Process of UMTS Cell Performance Analysis......................................................................................................1161 4.8.4 Interface Description: UMTS Cell Performance Analysis....................................................................................1180 4.8.5 Parameters for Viewing UMTS Cell Performance Analysis Results....................................................................1182 4.8.6 FAQ: What Do I Do When NE Objects Are Missing from the Analysis Results?...............................................1199 4.9 UMTS Network Geographic Observation................................................................................................................1200 4.9.1 Basics of UMTS Network Geographic Observation.............................................................................................1200 4.9.2 Preparations for UMTS Network Geographic Observation..................................................................................1204 4.9.3 Process of UMTS Network Geographic Observation...........................................................................................1206 4.9.4 Interface Description: UMTS Network Geographic Observation.........................................................................1214 4.9.5 Parameters for Viewing UMTS Network Geographic Observation Results.........................................................1217 4.10 VIP Analysis...........................................................................................................................................................1221 4.10.1 Basics of VIP Analysis........................................................................................................................................1221 4.10.2 Preparations for VIP Analysis.............................................................................................................................1232 4.10.3 Process of VIP Analysis......................................................................................................................................1238 4.10.4 Reference for VIP Analysis Interface..................................................................................................................1253 4.10.5 Reference for VIP Analysis Parameters (UMTS)...............................................................................................1265 4.10.6 Reference for VIP Analysis Parameters (GSM)..................................................................................................1328 4.10.7 Reference for VIP Analysis Parameters (LTE)...................................................................................................1368 4.10.8 Reference for VIP Analysis Parameters (PS Core).............................................................................................1373 4.11 Complaint Analysis Support...................................................................................................................................1399 4.11.1 Basics of Complaint Analysis Support................................................................................................................1400 4.11.2 Preparations for Complaint Analysis Support.....................................................................................................1406 4.11.3 Process of Complaint Analysis Support..............................................................................................................1414 4.11.4 Reference for Complaint Analysis Support Interface..........................................................................................1424 4.11.5 Reference for Complaint Analysis Support Parameters (UMTS).......................................................................1453 4.11.6 Reference for Complaint Analysis Support Parameters (GSM)..........................................................................1532 4.11.7 Reference for Complaint Analysis Support Parameters (LTE)...........................................................................1591 4.11.8 Reference for Complaint Analysis Support Parameters (PS Core).....................................................................1615 4.11.9 Appendix: Exception Cause Classification / Key Signaling...............................................................................1646
Contents
5.1.4 Interface Description: LTE Coverage Analysis.....................................................................................................1719 5.1.5 Parameters for Viewing LTE Coverage Analysis Results.....................................................................................1723 5.2 LTE Terminal Analysis............................................................................................................................................1725 5.2.1 Basics of LTE Terminal Analysis.........................................................................................................................1725 5.2.2 Preparations for LTE Terminal Analysis...............................................................................................................1729 5.2.3 Process of LTE Terminal Analysis........................................................................................................................1731 5.2.4 Interface Description: LTE Terminal Analysis.....................................................................................................1737 5.2.5 Parameters for Viewing LTE Terminal Analysis Results.....................................................................................1742 5.3 LTE Cell Performance Analysis...............................................................................................................................1754 5.3.1 Basics of LTE Cell Performance Analysis............................................................................................................1754 5.3.2 Preparations for LTE Cell Performance Analysis.................................................................................................1759 5.3.3 Process of LTE Cell Performance Analysis..........................................................................................................1760 5.3.4 Interface Description: LTE Cell Performance Analysis........................................................................................1767 5.3.5 Parameters for Viewing LTE Cell Performance Analysis Results........................................................................1770 5.4 LTE Network Geographic Observation....................................................................................................................1780 5.4.1 Basics of LTE Network Geographic Observation.................................................................................................1780 5.4.2 Preparations for LTE Network Geographic Observation......................................................................................1785 5.4.3 Process of LTE Network Geographic Observation...............................................................................................1788 5.4.4 Interface Description: LTE Network Geographic Observation.............................................................................1797 5.4.5 Parameters for Viewing LTE Network Geographic Observation Results.............................................................1801 5.5 VIP Analysis.............................................................................................................................................................1806 5.5.1 Basics of VIP Analysis..........................................................................................................................................1806 5.5.2 Preparations for VIP Analysis...............................................................................................................................1817 5.5.3 Process of VIP Analysis........................................................................................................................................1823 5.5.4 Reference for VIP Analysis Interface....................................................................................................................1838 5.5.5 Reference for VIP Analysis Parameters (LTE).....................................................................................................1850 5.5.6 Reference for VIP Analysis Parameters (GSM)....................................................................................................1855 5.5.7 Reference for VIP Analysis Parameters (UMTS).................................................................................................1896 5.5.8 Reference for VIP Analysis Parameters (PS Core)...............................................................................................1959 5.6 Complaint Analysis Support.....................................................................................................................................1985 5.6.1 Basics of Complaint Analysis Support..................................................................................................................1986 5.6.2 Preparations for Complaint Analysis Support.......................................................................................................1992 5.6.3 Process of Complaint Analysis Support................................................................................................................2000 5.6.4 Reference for Complaint Analysis Support Interface............................................................................................2010 5.6.5 Reference for Complaint Analysis Support Parameters (LTE).............................................................................2039 5.6.6 Reference for Complaint Analysis Support Parameters (GSM)............................................................................2063 5.6.7 Reference for Complaint Analysis Support Parameters (UMTS).........................................................................2122 5.6.8 Reference for Complaint Analysis Support Parameters (PS Core).......................................................................2201 5.6.9 Appendix: Exception Cause Classification / Key Signaling.................................................................................2233 5.6.10 FAQ: Why Are CHRs Related to RRC Connection Setup Failures Not Displayed in LTE Complaint Analysis Support Results?.............................................................................................................................................................2293
Contents
6.1 Common Client Settings...........................................................................................................................................2295 6.1.1 Logging In to or Exiting the Nastar Client............................................................................................................2295 6.1.2 Changing the Password of the Current User.........................................................................................................2297 6.1.3 Getting to Know the Client GUI............................................................................................................................2298 6.1.4 Customizing the Client GUI Effect.......................................................................................................................2308 6.1.5 Locking the Client.................................................................................................................................................2318 6.1.6 Unlocking the Client..............................................................................................................................................2319 6.1.7 Broadcast Messages...............................................................................................................................................2320 6.1.8 Displaying the Current Window in Full Screen Mode..........................................................................................2321 6.1.9 Setting the Alert at Network Disconnection..........................................................................................................2322 6.1.10 (Optional) Setting the File Transfer Mode Between the Server and Client........................................................2322 6.1.11 Checking Whether the Client Needs Upgrade.....................................................................................................2323 6.1.12 Setting the Interval of Client Upgrade Check.....................................................................................................2323 6.1.13 Managing the Nastar License..............................................................................................................................2324 6.1.14 GUI Reference..................................................................................................................................................... 2327 6.1.15 FAQs about the Client Operations.......................................................................................................................2337 6.2 Security Management...............................................................................................................................................2340 6.2.1 Overview of User Management.............................................................................................................................2340 6.2.2 Configuration and Management of User Security................................................................................................. 2349 6.2.3 Reference of the Security Management GUI.........................................................................................................2395 6.2.4 FAQs About Security Operations..........................................................................................................................2423 6.2.5 Appendix A : Nastar Operation Right References................................................................................................2425 6.2.6 Appendix B : Nastar Default Items.......................................................................................................................2425 6.3 Managing Digital Certificates..................................................................................................................................2427 6.3.1 Understanding Digital Certificates........................................................................................................................2427 6.3.2 Configuring Digital Certificates............................................................................................................................2430 6.3.3 Managing SSL Connection Policies......................................................................................................................2439 6.3.4 Reference of the Certificate Authentication Management GUI............................................................................2444 6.4 Log Management...................................................................................................................................................... 2453 6.4.1 Getting to Know Log Management.......................................................................................................................2453 6.4.2 Managing the Nastar Operation Logs....................................................................................................................2459 6.4.3 Managing the Nastar System Logs........................................................................................................................ 2462 6.4.4 Managing the Nastar Security Logs......................................................................................................................2465 6.4.5 Setting Log Templates...........................................................................................................................................2468 6.4.6 Setting a Nastar Log Forwarding Server...............................................................................................................2469 6.4.7 Managing Log Data...............................................................................................................................................2470 6.4.8 Downloading Nastar Trace Logs........................................................................................................................... 2472 6.4.9 Reference of the Log Management GUI...............................................................................................................2474 6.5 Monitoring the Nastar System.................................................................................................................................. 2505 6.5.1 Setting the Monitoring Parameters........................................................................................................................2505 6.5.2 Setting the Monitoring Parameters........................................................................................................................2508 6.5.3 Monitoring the Status of the Nastar Server...........................................................................................................2510 Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
6.5.4 Monitoring the Status of the xSAU.......................................................................................................................2514 6.5.5 Distributing xSAU System Monitoring Results....................................................................................................2516 6.5.6 Monitoring the System's Network Connections....................................................................................................2517 6.5.7 Interface Reference for System Monitoring..........................................................................................................2518 6.6 Integrated Task Management...................................................................................................................................2537 6.6.1 Introduction to Integrated Task Management........................................................................................................2537 6.6.2 Customizing the Interface for Managing Timing Tasks........................................................................................2541 6.6.3 Managing Timing Tasks........................................................................................................................................2542 6.6.4 Viewing Timing Tasks..........................................................................................................................................2544 6.6.5 Reference of the Integrated Task Management GUI.............................................................................................2546 6.7 Managing Adapter Packages....................................................................................................................................2552 6.7.1 Delivering an Adapter Package.............................................................................................................................2553 6.7.2 Rolling Back an Adapter Package.........................................................................................................................2554 6.7.3 Viewing Log Information About Adapter Packages.............................................................................................2555 6.8 Managing Analysis Data..........................................................................................................................................2556 6.8.1 Checking the Integrity of Analysis Data...............................................................................................................2556 6.8.2 Periodically Deleting Analysis Data......................................................................................................................2558
Issue 01 (2013-07-15)
xiv
1 Nastar Overview
1
About This Chapter
Nastar Overview
Nastar provides a complete solution for wireless network performance analysis. It is applicable to GSM/GPRS/EDGE, UMTS/HSUPA/HSDPA, LTE TDD/LTE FDD, and PS Core networks. This solution can deeply analyze and locate wireless network problems and supports user experience-based performance optimization and location-based network evaluation. 1.1 Position in Networking The Nastar system consists of multiple physical entities such as the Nastar server, eSAU, SAU, LTE SAU, and PS SAU. Each physical entity is deployed in specific position of the network. 1.2 Product Functions This section lists the analysis functions provided by the Nastar for the GSM, UMTS, LTE, and PS Core networks. 1.3 Basic Concept/Glossary This chapter describes the basic concepts used in this document.
Issue 01 (2013-07-15)
1 Nastar Overview
The communication between different units on the network is based on the TCP/IP protocol. The Nastar server, eSAU, LTE SAU, and M2000 must be in the same local area network (LAN), and their IP addresses must be on the same network segment. Table 1-1 describes the function of each unit. Table 1-1 Description of the functional units System Radio access network (RAN)
Issue 01 (2013-07-15)
Description 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.
2
1 Nastar Overview
System
Description 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. 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. The SGSN is a functional unit at the CN. It provides PS data on the CN side for the Nastar system. The GPRS is a functional unit at the CN. It provides PS data on the CN side for the Nastar system.
E-UTRAN
Serving GPRS support node (SGSN) Gateway GPRS support node (GGSN/SAEGW) Mobility management entity (MME)
The MME provides data on the LTE RAN side for the Nastar system to analyze. 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. The data collection server on the LTE network is used to collect the LTE analysis data. For details about Trace Server, see M2000 Trace Server User Guide on M2000 Product Documentation.
M2000
Trace Server
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.
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.
Issue 01 (2013-07-15)
1 Nastar Overview
System
Description 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. 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. 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.
Nastar server
Issue 01 (2013-07-15)
1 Nastar Overview
Scenario
Description 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. 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.
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. 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/ UMTS
Frequency analysis
GSM
Issue 01 (2013-07-15)
1 Nastar Overview
Scenario
Description 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. 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. 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. In addition, the Nastar analyzes cell performance faults based on cell service alarms in the LTE network.
Networ k UMTS
Network analysis
GSM/ UMTS/ LTE TDD/ LTE FDD GSM/ UMTS/ LTE TDD/ LTE FDD
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 efficiency. 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.
PS Core
User assurance
Issue 01 (2013-07-15)
1 Nastar Overview
Scenario
Description 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. 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.
Nastar System
The Nastar system consists of multiple physical entities such as the Nastar server, eSAU, 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 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7
1 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. The MR data is generated by the base station controller and saved as a binary file on the SAU board (or the OMU board if there is no SAU board).
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. The CHR data is generated by the base station controller and saved as a binary file on the SAU board (or the OMU board if there is no SAU board).
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, or LTE network, the 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 l MCC refers to the mobile country code of a mobile subscriber. MNC refers to the mobile network code, that is, the PLMN code of a mobile subscriber. PLMN refers to the public land mobile network.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8
1 Nastar Overview
l l
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 l l 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 l 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.
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. Table 1-2 describes the definition of each counter in the formula.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9
1 Nastar Overview
Table 1-2 Definitions of A, B, C, W1, W2, and W3 Counter A B C W1 Definition Total number of services under a base station controller in busy hours. The services include calls and data services. Number of handovers triggered during busy-hour services. Number of NAS messages in busy hours. Weight of services affecting BHCA. l The value is 1 for GSM. l The value is 1 for UMTS. l The value is 1 for LTE. W2 Weight of handovers affecting BHCA. l The value is 0.3125 for GSM. l The value is 0.33 for UMTS. l The value is 0.33 for LTE. W3 Weight of NAS messages affecting processing capabilities. l The value is 0.41 for GSM. l The value is 0.38 for UMTS. l The value is 0.38 for LTE.
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.
Equivalent NE
Equivalent NE is a term introduced to calculate the network scale for the Nastar. Table 1-3 describes the relationship between equivalent NEs and the network scale on the Nastar side. Table 1-3 Relationship between equivalent NEs and the network scale Equivalent NE RAN network scale (Unit: BHCA) GSM UMTS TDSCD MA 250,00 0 25,000, 000 LTE CN (unit: PS SAU) PS Core network control plane 12,500 1,250,000
46,875 4,687,50 0
250,000 25,000,00 0
10
1 Nastar Overview
Equivalent NE
RAN network scale (Unit: BHCA) GSM UMTS TDSCD MA 100,00 0,000 200,00 0,000 LTE
18,750,0 00 37,500,0 00
100,000,0 00 200,000,0 00
Issue 01 (2013-07-15)
11
2
About This Chapter
This chapter describes the basic ideas and operations for network optimization and describes the Nastar operation processes by using examples. Only basic Nastar operations are described in this section. It is especially useful to new users. It is recommended that you read this section when using the Nastar the first time. If you are familiar with Nastar basic operations, refer to chapters named in *** Network Optimization format to perform theme analysis. 2.1 Nastar Operation Process This section describes the operation process for network optimization by using Nastar and each involved procedure. 2.2 Login In to the Nastar This topic describes how to log in to the Nastar client, and how to log out the current user add exit the Nastar client. 2.3 Configuring OSS and NE Information This chapter 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 M2000, eSAU, LTE SAU, SAU, and PS SAU. Therefore, you need to configure OSS and NE information so that these entities can identify and communicate with each other. In this manner, data can be obtained successfully. The information to be configured includes IP address, user name, password, and FTP information. 2.4 Preparing Basic Data This section describes how to collect basic data including configuration data, engineering parameters, and map information before analyzing data. 2.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. 2.6 Checking the Integrity of Analysis Data This chapter describes how to check the integrity of analysis data. You need to check the integrity of analysis data to ensure that the Nastar can analyze the data normally. 2.7 Creating an Analysis Task
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 12
This section describes how to create an analysis task. After the analysis task is created, the Nastar retrieves the performance data of the selected NE from the database, analyzes it, and generates an analysis report. 2.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. 2.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. 2.10 Exporting Analysis Reports This section describes how to export the analysis reports as files. 2.11 FAQs This chapter describes the problems and solutions to the FAQs when using the Nastar, and also provides methods for common operations.
Issue 01 (2013-07-15)
13
2.
3.
Figure 2-1 shows the flowchart. For details, see Table 2-1.
Issue 01 (2013-07-15)
14
Table 2-1 Operation procedures for network optimization by using Nastar No. (1) Procedure Prepar ation phase Configuring OSS and NE Information Description 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. Before obtaining the data for analysis, users must collect some basic data for analysis such as the configuration data, engineering parameters, and map information.
(2)
Issue 01 (2013-07-15)
15
No. (3)
Description 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 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. After an analysis task is created, the Nastar retrieves the performance data of the desired NE from the database for analysis. After the analysis is complete, users can view the analysis result. The analysis result can be used as a basis for network optimization. You can export the analysis results into Excel files.
(4)
Check the Integrity of Analysis Data Analys is phase Creating an Analysis Task View the Analysis Result Exporting Analysis Reports
(5)
(6)
(7)
Prerequisites
Before login, ensure that the Nastar client and server are connected normally, and the server works properly.
Context
l l The default port number of the server is 31037. Do not change it in normal conditions. Otherwise, you cannot log in to the Nastar client. The Nastar server provides the default user account admin. The admin user has all operation rights, and the password is empty 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16
Issue 01 (2013-07-15)
l l l
By default, if you do not log in to the Nastar client for more than 60 days, your account automatically turns to the suspend state except that you are an admin user. 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: 1. 2. 3. 4. 5. Click on the right of Server drop-down list.
In the Server List dialog box, click Add. In the Add Server Information dialog box, set the Name, Server Name (or IP Address), Port and Mode. 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. 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.
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. 2. l 1.
Issue 01 (2013-07-15)
Choose File > Exit from the main menu. In the Confirm dialog box, click OK. Choose File > Log Out from the main menu.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 17
2.
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.
For details of the areas in the interface, see 6.1.3 Getting to Know the Client GUI.
Navigation Path
l In the Nastar main window, click . The Geographic Observation window is displayed. In this window, you can check the geographic distribution of sites on the network, or check analysis results of added themes.
Issue 01 (2013-07-15)
18
In the theme analysis result window, click . The Geographic Observation window is displayed. In this window, you can add counters related to a theme to the layer navigation tree for analysis.
NOTE
l Before you perform a geographic observation analysis, check that engineering parameters have been imported into the Nastar. For detailed operations, see Importing Engineering Parameters. l When you close the window, the Nastar hides the window and does not delete the analysis results. When you click again, the analysis results are displayed again.
l If the Geographic Observation window of a theme (excluding network geographic observation themes) is open, the Nastar deletes related counters from the layer navigation tree when you close the theme analysis result window. l There is no analysis result window for network geographic observation themes. The results of such themes are displayed in the Geographic Observation window.
Window
Figure 2-3 shows the Geographic Observation window. Figure 2-3 Geographic Observation window
N Item o . 1 Toolbar
Description
Provides icons for you to perform operations. For detailed operations, see Buttons on the toolbar.
Issue 01 (2013-07-15)
19
Description
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.
TIP 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 01 (2013-07-15)
20
N Item o .
Description
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 Geographic Observation window. Further polygon analysis includes the following functions: l Statistical analysis: enables you to analyze multiple counters simultaneously based on a polygon and displays the analysis results in a list. To enable this function, perform the following operations: 1. Right-click a polygon and choose Statistical Analysis from the shortcut menu. 2. In the displayed dialog box, select an analysis task, dimension, and counters, and click OK. 3. In the displayed Statistical Analysis Result dialog box, view the counter analysis results of the polygon.
NOTE Currently, the themes that support the statistical analysis function are network geographic observation, service geographic observation, and terminal geographic observation.
l Grid in-depth analysis: enables you to further analyze grids by performing the following operations: Right-click a polygon and choose Analysis Theme > Grid In-depth Analysis from the shortcut menu. You can use this function to further analyze traffic hot spots and quickly determine an expansion solution.
Issue 01 (2013-07-15)
21
N Item o .
Description
NOTE Currently, only service geographic observation themes support the grid in-depth analysis function.
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, GSM service 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. For service geographic observation, the analysis dimensions are set by users when they create analysis tasks, for example, high-value service. 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 01 (2013-07-15)
22
Description
The display effects of themes are different: l After you select counters for network geographic observation and service geographic observation, this area displays information about grids, sites,
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
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. l Further analyzing cells: Right-click a cell and choose Cell Deep Analyze > Analysis Theme from the shortcut menu. In the displayed dialog box, the Nastar further analyzes cell traffic from multiple dimensions.
NOTE Currently, only service geographic observation themes support the cell in-depth analysis function.
Issue 01 (2013-07-15)
23
Description
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. 5 Legend details area This area is not displayed by default. If you want to view the legend details about an analysis theme, click in the button area. The Nastar provides three methods for you to set legends: l Click in area 1. In the displayed Layer Management dialog box, click Display to set the counter legend. l Right-click a counter in area 2 and choose Display from the shortcut menu. In the displayed dialog box, set the counter legend. l Right-click in area 3 and choose Layer Management from the shortcut menu. In the displayed Layer Management dialog box, click Display to set the counter legend.
NOTE l If no counter needs to be analyzed in a geographic observation theme, such as GSM neighboring cell analysis, the counter legend cannot be set. l You can back up and restore the configured counter legends by using the file sharing function. The counter legend information is saved in \NastarClient\client\plugins \com.huawei.galaxy.geography.ui\style\config\style.
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.
Issue 01 (2013-07-15)
24
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. 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.
Moves a map.
Issue 01 (2013-07-15)
25
Button
Operation
Click 1. Click
on the toolbar and click an object on the map to select it. 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
Click on the toolbar to zoom in the map or click out the map.
to zoom
TIP 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 Geographic Observation window.
Click on the toolbar. Colors and connection lines are deleted from the site or sector icons that are highlighted based on service and geographical differences. 1. Click on the toolbar. The Save dialog box is displayed.
Saves a map.
2. Set the file name and type. You can export the display effect of overlapped layers in the map window as an image in .png, .gif, .jpg or .tab Reformat. 3. Click Save.
Issue 01 (2013-07-15)
26
Button
Operation
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 The lines of a polygon must not intersect. Otherwise, certain selected areas may be missed out.
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 01 (2013-07-15)
27
Button
Operation
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. 1. Click on the toolbar. The Search dialog box is displayed.
2. Select a RAT in Network Technology. 3. Select the area you want to filter in Region. 4. Set engineering parameters in the lower left corner of the dialog box. The Nastar supports filtering of all engineering parameters. Generally, you can set one or two parameters as the filter criteria. The logical operator between the two parameters can be set to And or Or. 3. Click Search. The Nastar starts to filter cells. The filtering results are displayed in the Search Result area. 4. Select or clear Search Result to determine whether to filter cells again. 5. The Nastar geographically displays filtered cells. Click Geographic(D). The cells selected in the Search Result area are highlighted in the Geographic Observation window. 6. Save the filtered cells as an NE group. 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. Loads the last map. Click on the toolbar. The Nastar loads the last map.
Issue 01 (2013-07-15)
28
Button
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.
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.
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.
Issue 01 (2013-07-15)
29
Button
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. Currently, only scenario files in .csv format can be imported. 6. Click Export. You can view the export progress in the displayed Exported File List dialog box.
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.
Issue 01 (2013-07-15)
30
Issue 01 (2013-07-15)
31
Table 2-2 Configuration procedures Configur ation Scenario Configuri ng informatio n about NEs on the radio access network (RAN) side No. Step Description
a.1
Configuring eSAU information Configuring OSS information Selecting RAN NEs managed by an OSS Setting SAU or LTE SAU information. Configuring eSAU information Configuring OSS information Selecting CN NEs managed by an OSS Setting PS SAU information.
In this step, configure the IP address, port number, and FTP information of the server running the eSAU software. In this step, configure the IP address, software version, networking mode, and FTP information of the OSS server. In this step, select the RAN NEs managed by an OSS, such as BSC, RNC, and eNodeB. In this step, configure the SAU information before you use the analysis function of the SAU board. In this step, configure the IP address, port number, and FTP information of the server running the eSAU software. In this step, configure the IP address, software version, networking mode, and FTP information of the OSS server. In this step, select the CN NEs managed by an OSS, such as serving GPRS support node (SGSN). In this step, configure the PS SAU information before you use the analysis function of the CN network.
a.2
a.3
a.4
b.1
b.2
b.3
b.4
Required Information Information about the OSS system within the analysis area, including: l Version number and networking scheme l User name, password, and port number for the FTP service of the OSS system. If the OSS system contains slave servers, obtain the preceding information about the slave servers. l Number of the port for communicating with the OSS system. Retain the default setting when you configure information about NEs. l User name and password for logging in to the OSS client. This user has the following operation rights: For the M2000 V200R011C00SPC230/ V200R011C01SPC230 or earlier, this user is authorized to centrally manage tasks and issue MML commands. For the M2000 V200R012, or the version later than V200R011C00SPC230/V200R011C01SPC230, this user is granted the rights of Nastar Collection Task Management, Send MML to NE, Send Binary Command to NE, Query OSS Basic Info, Collect NE FM Data, Collect NE PM Data, and Collect NE Signal Data under Data Collection Management. The Collect NE Signal Data is only used for the LTE analysis. For the M2000 V200R013 or a later version, this user is granted the rights as follows: OSS Tool Collection Task Management, Send MML to NE, Send Binary Command to NE, Query OSS Basic Info, Collect NE FM Data, Collect NE PM Data, and Collect NE Signal Data under Data Collection Management. The Collect NE Signal Data is only used for the LTE analysis. RAN Pool Management and RAN Pool Management Browser under Configuration Management. l If an access control list (ACL) is configured on the M2000, add the IP address of the Nastar to the Security > System ACL of the M2000 to ensure that the Nastar can access the M2000.
Information about the SAU, including: l IP address and port information of the SAU board for the GSM or UMTS network. l IP address and port information of the server running the LTE SAU for the LTE network.
Issue 01 (2013-07-15)
33
Required Information 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 l User name, password, and port number for the FTP service of the PS SAU server for SGSN/MME Obtain information about the GGSN/SAE-GW within the analysis area: l View the equipment serial number (ESN). 1. Log in to the UGW LMT. 2. Run the display chr device-number command in the OM view. l View the time zone and daylight saving time (DST) of the NE. 1. Log in to the UGW LMT. 2. Run the display clock command in any view.
Prerequisites
You have obtained relevant information includes the server running eSAU. Information include IP address, user name and password for FTP service, and ports.
Procedure
Step 1 Choose Maintenance > OSS Information Management. If... You configure the eSAU information firstly, You modify the configured eSAU information, Then... The eSAU modification window will be displayed. Please perform Step 2. 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 2-5.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 34
Table 2-4 describes basic eSAU server information. Table 2-4 Basic eSAU server information Parameter IP Address Port SSL Port Description IP address of the server running eSAU. Number of the port for logging in to the server. The default port number is 30010. Number of the port for logging in to the server by the security mode. The default port number is 30110.
Step 3 In the lower area of the right pane, set FTP information so that the system can collect data from the eSAU server using FTP. Table 2-5 describes eSAU FTP information. Table 2-5 eSAU FTP information Parameter IP Address Port Description IP address of the server running eSAU. l FTP port of the server. The default port number is 21. l SFTP port of the server. The default port number is 22.
Issue 01 (2013-07-15)
35
Description Name of the user for connecting to the FTP service. The default user is ftpuser. Password of the user for connecting to the FTP service. l SFTP: encrypted FTP transfer, which requires the support from the FTP server. Select SFTP for an ATAE cluster system because security hardening is performed by default when the system is deployed. l FTP: non-encrypted and common FTP mode.
Prerequisites
l l You have configured eSAU information. You have obtained M2000 system information, such as the IP address and the network mode. For details, see Table 2-6, Table 2-7, and Table 2-9 in the Procedure section.
Procedure
Step 1 Choose Maintenance > OSS Information Management. Step 2 Click NE Management in the navigation tree in the OSS Information Management window, as shown in Figure 2-6. Figure 2-6 NE Management navigation tree
Issue 01 (2013-07-15)
36
Step 3 Click Create OSS in the lower-right of the window. The window shown in Figure 2-7 is displayed. Figure 2-7 OSS information
Step 4 Set basic OSS information by referring to Table 2-6. Table 2-6 Basic OSS information Param eter Name Type Description A user-defined OSS server name, which must be unique. Type of the data collection interface between the M2000 and the Nastar.
NOTE 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.
Networ k Mode
Networking mode of the M2000, which includes: 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).
NOTE If you set this parameter to Multi-server load sharing system (SLS)/ATAE Cluster, you need to set information about slave servers. For details, see Step 6.
Mandatory
Issue 01 (2013-07-15)
37
Description IP address of the M2000 server. l If the M2000 adopts the HA, RHA, or SLS system, type the IP address of the active or master server. l If you have configured northbound and southbound IP addresses for the M2000 servers, type the northbound IP address of the M2000 active server. l If the IP address of the M2000 active server has been translated using an NAT device during the communication between the Nastar server and the M2000 active server, you need to type the translated IP address of the M2000 active server. In addition, you need to configure the mapping between the IP address and logical host name of the M2000 active server on the Nastar server. For detailed operations, see How Do I Configure the Mapping Between the Public IP Address and Host Name of the M2000 Active Server on the Nastar? on the Commissioning Guide.
Port number used for logging in to the M2000 server. Generally, the port number is 9999. Name of the user for logging in to the M2000 client. This user must have the following rights: l For the M2000 V200R011C00SPC230/V200R011C01SPC230 or earlier, this user is authorized to centrally manage tasks and issue MML commands. l For the M2000 V200R012, or the version later than V200R011C00SPC230/V200R011C01SPC230, this user is granted the rights of Nastar Collection Task Management, Send MML to NE, Send Binary Command to NE, Query OSS Basic Info, Collect NE FM Data, Collect NE PM Data, and Collect NE Signal Data under Data Collection Management. The Collect NE Signal Data is only used for the LTE analysis. l For the M2000 V200R013 or a later version, this user is granted the rights as follows: OSS Tool Collection Task Management, Send MML to NE, Send Binary Command to NE, Query OSS Basic Info, Collect NE FM Data, Collect NE PM Data, and Collect NE Signal Data under Data Collection Management. The Collect NE Signal Data is only used for the LTE analysis. RAN Pool Management and RAN Pool Management Browser under Configuration Management.
Mandatory Mandatory
Passwor d
Mandatory
Issue 01 (2013-07-15)
38
Description IP address for the communication between the M2000 and the OM network.
NOTE l If the Nastar is deployed by using the relay-based networking mode, this parameter must be set. l If the M2000 is already equipped with southbound and northbound IP addresses, enter the southbound IP address of the active M2000 server. This parameter must be set.
Proxy Port
Port number used for the communication between M2000 and eSAU. If the Nastar is deployed by using the relay-based networking mode, this parameter must be set. By default, the value of this parameter is set to 31035.
Optional
SSL Availab le
Set the M2000 and the Nastar mode of communication for SSL.
NOTE The communication mode of the M2000 must be the same as that of the eSAU. l If you want to change the value of this parameter, also manually reset the communication mode of the eSAU. Otherwise, executing basic data subscription tasks fail. For details, see 2.11.6 What Do I Do if the System Displays Login M2000 Failed When a Nastar Basic Data Subscription Task Fails?. l If one eSAU serves multiple M2000 systems, the communication mode must be the same on each of these M2000 systems.
Mandatory
Descrip tion
Description information.
Optional
Step 5 Set OSS FTP information by referring to Table 2-7. Table 2-7 OSS FTP information Param eter User Name Passwo rd Port Description Name of the user for connecting to the FTP service on the M2000. Password of the user for connecting to the FTP service. FTP port of the server. The default port number is 21. Mandatory/ optional Mandatory Mandatory Mandatory
Issue 01 (2013-07-15)
39
Description Transfer mode of the FTP server, consisting of Passive and Active. l Passive mode: The client sends a connection request to the FTP port of the server. The server receives the request and sets up a command link. Before transmitting data, the server sends a message to the client using the PASV command on the link. The message indicates that the FTP port on the server is enabled and the server can be connected. Then, the client sends a connection request to the server to set up a link for transmitting data. l Active mode: The client sends a connection request to the FTP port of the server. The server receives the request and sets up a command link. Before transmitting data, the client sends a message to the server using the PORT command on the link. The message indicates that the port on the client is enabled and the client can be connected. In response to the client, the server sends a connection request through port 20 to establish a link for transmitting data.
Protoco l
l SFTP: encrypted FTP transfer, which requires the support from the FTP server. You must select this protocol if the operating system of the M2000 server connected to the Nastar has been hardened.
NOTE l If the M2000 is deployed on a SUN server and its version is V200R011 or later, the operating system is hardened upon factory delivery. If the M2000 version is earlier than V200R011, you need to check whether the operating system is hardened based on the description in M2000 Commissioning Guide. l If the M2000 is deployed in an ATAE cluster system, the operating system is hardened upon factory delivery. l If the M2000 is deployed on an IBM server, the operating system is hardened upon factory delivery.
Mandatory
Step 6 Optional: If Type is M2000 V200R008 or a later version, and you have set M2000 to Multiserver load sharing system (SLS)/ATAE Cluster, you need to perform the following operations to set slave servers:
NOTE
When the M2000 V200R008 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. 2.
Click Add Slave. The Add Slave dialog box is displayed. Set information about slave servers by referring to Table 2-8.
Issue 01 (2013-07-15)
40
Table 2-8 Slave server FTP information Param eter Server IP NAT IP Description Mandato ry/ optional Mandator y Optional
IP address of the slave server. Configure the slave server IP address that has been translated using NAT. If the IP address of the M2000 active server has been translated using an NAT device during the communication between the Nastar server and the M2000 active server, you need to set NAT IP.
Name of the user for connecting to the FTP service on the slave server. The default user name is ftpuser. Password of the user for connecting to the FTP service. FTP port of the server. The default port number is 21. Transfer mode of the FTP server, consisting of Passive and Active. l Passive mode: The client sends a connection request to the FTP port of the server. The server receives the request and sets up a command link. Before transmitting data, the server sends a message to the client using the PASV command on the link. The message indicates that the FTP port on the server is enabled and the server can be connected. Then, the client sends a connection request to the server to set up a link for transmitting data. l Active mode: The client sends a connection request to the FTP port of the server. The server receives the request and sets up a command link. Before transmitting data, the client sends a message to the server using the PORT command on the link. The message indicates that the port on the client is enabled and the client can be connected. In response to the client, the server sends a connection request through port 20 to establish a link for transmitting data.
Issue 01 (2013-07-15)
41
Description
l SFTP: encrypted FTP transfer, which requires the support from the FTP server.You must select this protocol if the operating system of the M2000 server connected to the Nastar has been hardened.
NOTE l If the M2000 is deployed on a SUN server and its version is V200R011 or later, the operating system is hardened upon factory delivery. If the M2000 version is earlier than V200R011, you need to check whether the operating system is hardened based on the description in M2000 Commissioning Guide. l If the M2000 is deployed in an ATAE cluster system, the operating system is hardened upon factory delivery. l If the M2000 is deployed on an IBM server, the operating system is hardened upon factory delivery.
l FTP: non-encrypted and common FTP mode. 3. 4. Click OK. Repeat the preceding operations to set parameters of all slave servers.
Step 7 Optional: Configure the Trace Server information by referring to Table 2-9. Only performing the LTE network analysis, you need set the Trace Server information. Table 2-9 Trace Server FTP information Param eter Server IP User Name Description IP address of the Trace Server. Name of the user for connecting to the FTP service on the Trace Server. The user for connecting to the FTP service on the Trace Server is ftpuser. Passwo rd Port Password of the user for connecting to the FTP service. FTP port of the server. The default port number is 21. Mandatory Mandatory Mandatory/ optional Mandatory Mandatory
Issue 01 (2013-07-15)
42
Description Transfer mode of the FTP server, consisting of Passive and Active. l Passive mode: The client sends a connection request to the FTP port of the server. The server receives the request and sets up a command link. Before transmitting data, the server sends a message to the client using the PASV command on the link. The message indicates that the FTP port on the server is enabled and the server can be connected. Then, the client sends a connection request to the server to set up a link for transmitting data. l Active mode: The client sends a connection request to the FTP port of the server. The server receives the request and sets up a command link. Before transmitting data, the client sends a message to the server using the PORT command on the link. The message indicates that the port on the client is enabled and the client can be connected. In response to the client, the server sends a connection request through port 20 to establish a link for transmitting data.
Protoco l
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.
NOTE l If the Trace Server is deployed on a SUN server and the M2000 version is V200R013 or later, the operating system is hardened upon factory delivery. If the M2000 version is earlier than V200R013, you need to check whether the operating system is hardened based on the description in M2000 Trace Server User Guide. l If the Trace Server is deployed in an ATAE cluster system, the operating system is hardened upon factory delivery.
Mandatory
Follow-up Procedure
l Modify OSS information. 1. 2. 3. l In the navigation tree, select a node to be modified and click Modify. Modify OSS information. Click OK.
Issue 01 (2013-07-15)
43
1. 2.
Click NE Management in the navigation tree in the OSS Information Management window. 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.
Prerequisites
You have created an OSS.
Procedure
Step 1 Choose Maintenance > OSS Information Management. Step 2 Select an OSS from the navigation tree in the OSS Information Management window. Step 3 Click the RAN NE List tab in the right pane, as shown in Figure 2-8. Figure 2-8 NE List tab page
Step 4 Click Select NE. The Select NE dialog box is displayed. Step 5 Select NEs managed by the selected OSS. The NEs to be selected are in the left pane, and the selected NEs are in the right pane.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 44
l Click , , , or to select NEs. You can click a single-arrow icon to move an NE at a time, or a double-arrow icon to move all NEs. l You can also select multiple NEs while holding down Ctrl. l When an NE changes (for example, its name is changed) and reconnects to the Nastar, you must configure the NE mapping relationship before and after the change. For detailed operations, see 2.11.3 Supporting Historical Data Analysis on a Changed NE.
CAUTION
l 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. 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 OK. ----End
Follow-up Procedure
l Modify the NEs managed by an OSS. 1. 2. 3. l Select an OSS node to be modified in the navigation tree of the OSS Information Management window. On the RAN NE List tab page, click Select NE to reselect NEs managed by the OSS. Click OK.
Modify the description of the NEs managed by the OSS. 1. 2. 3. 4. Select an OSS node to be modified in the navigation tree of the OSS Information Management window. Select an NE row on the RAN NE List tab page. Click Modify Description to add description for the NE. Click OK.
Prerequisites
l l
Issue 01 (2013-07-15)
You have selected an NE. You have obtained related SAU information.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 45
Context
l On the GSM network, the data used for GSM MR analysis, GSM neighboring cell analysis, GSM frequency analysis, GSM/UMTS neighboring cell analysis, and GSM uplink interference analysis is the GSM performance data or uplink interference data which is collected from the 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 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.
Procedure
Step 1 Choose Maintenance > OSS Information Management. Step 2 In the navigation tree in the left pane of the OSS Information Management window, select an OSS node. Step 3 Click the RAN NE List tab in the right pane, as shown in Figure 2-9. Figure 2-9 NE list tab page
Issue 01 (2013-07-15)
46
If... The selected NE belongs to the GSM or UMTS network and the SAU board has been installed
Then... You must perform this step to set the IP address and port number of the SAU. Otherwise, the analysis functions such as the VIP analysis and complaint analysis of the SAU are unavailable to the NE.
The NE belongs to the GSM or UMTS No information needs to be configured. network but the SAU board has not been installed 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.
1. 2. 3. 4. 1. 2. 3.
Select an NE row. Click Configure SAU to configure the SAU or LTE SAU information. Set the IP address and port number of the SAU. The default port is 30020, the default port of security mode is 30120. Click OK. View details about the selected NE on the RAN NE List tab page, including the NE type, NE FDN, and NE version. View the SAU information about the NE. 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 1 hour. For example, the start time of the data collection service is 7:00, so the next execution time is 8:00. The start time of the data collection service is the same as the start time of the system service. After clicking Immediately Collect Configuration Data, the system will immediately collects configuration data in the OSS instead of collecting the data until the default time. If the system is executing another collection task, the task that you trigger manually will be automatically executed after the running task is complete.
----End
Follow-up Procedure
View information about the collection and import of configuration data in the Log Info area. Table 2-10 lists the parameters.
Issue 01 (2013-07-15)
47
Table 2-10 Log parameters Parameter Time Function Severity Operation User NE Name Description Time when a task is complete. Log type such as configuration data collect and import. Level of the log, including Minor and Major. You are advised to focus on the Major level log information. User that executes a task. The default user is system. 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 Operation Name Operation Result Details Data type, such as configuration data. Task type, such as data collection, data import, or basic NE information update. Operation result. The value can be Succeed or Failure. 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.
l l
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.
Prerequisites
You have deployed an OSS system.
Context
If the M2000 is in V200R013C00 or a later version, the Nastar supports RNC pooling, and you can:
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 48
l l 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 1 Choose Maintenance > OSS Information Management. Step 2 In the navigation tree of the OSS Information Management window, select an OSS node. Step 3 In the right pane, click the RNC Pool tab, as shown in Figure 2-10. Figure 2-10 RNC Pool tab page
----End
Prerequisites
You have created an OSS system.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 49
Procedure
Step 1 Choose Maintenance > OSS Information Management. Step 2 In the navigation tree in the left pane of the OSS Information Management window, select an OSS node. Step 3 Click the RAN NE List tab in the right pane, as shown in Figure 2-11. Figure 2-11 NE list tab page
Step 4 Click Select NE. The Select NE dialog box is displayed. Step 5 Select NEs managed by the selected OSS system. The NEs to be selected are in the left pane, and the selected NEs are in the right pane. An NE exists only in the left or right pane. l Click , , , or to select NEs. You can click a single-arrow icon to select an NE or multiple NEs at a time, or a double-arrow icon to select all NEs. l You can also hold down Ctrl to select multiple NEs. l If an NE is changed (for example, the name is changed), configure its matching relationship before and after the change. For detailed operations, see 2.11.3 Supporting Historical Data Analysis on a Changed NE.
CAUTION
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).
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 50
The GGSN/SAE-GW and SGSN/MME do not support MML commands. Therefore, you have to manually set the information on the Nastar after querying related NE equipment number, time zone, and DST information on the LMT. l GGSN/SAE-GW: You have to set the NE equipment number, time zone, and DST. For details about how to obtain the information, see 2.3.2 Preparations for OSS and NE Information Configuration. l SGSN/MME: You have to set the time zone and DST. For details about how to obtain the information, see 2.3.2 Preparations for OSS and NE Information Configuration. Step 7 Click OK. ----End
Follow-up Procedure
l Modify NEs managed by an OSS system. 1. 2. 3. l In the navigation tree of the OSS Information Management window, select an OSS node you want to modify. On the PS Core NE List tab page, click Select NE to select NEs managed by the OSS system again. Click OK.
Modify the description of the NEs managed by the OSS system. 1. 2. 3. 4. In the navigation tree of the OSS Information Management window, select an OSS node you want to modify. On the PS Core NE List tab page, select an NE row. Click Modify Description to add description for the NE. Click OK.
Prerequisites
l l You have selected NEs. You have obtained relevant PS SAU information.
Procedure
Step 1 Choose Maintenance > OSS Information Management. Step 2 In the navigation tree in the left pane of the OSS Information Management window, select an OSS node. Step 3 Click the PS Core NE List tab in the right pane, as shown in Figure 2-12.
Issue 01 (2013-07-15)
51
Step 4 Set the PS SAU information. 1. 2. 3. Select an NE row. Click Configure SAU to configure the PS SAU information. Configure the IP address and port of the SAU. Table 2-11 SAU information Parameter SAU IP SAU Port SSL Port Description Description IP address of the PS SAU server for SGSN/MME or GGSN/SAEGW. Port number of the PS SAU server for SGSN/MME or GGSN/SAEGW. The default port number is 30030, the default SSL port number is 30130. Description information. This parameter is optional.
4.
Click OK.
Step 5 Set the time zone information. 1. 2. 3. 4. Select an NE row. Click Time Zone Settings. Set Time Zone. 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: View details about the selected NE on the PS Core NE List tab page, including the NE type, NE FDN, NE version, and SAU information about the NE. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 52
Prerequisites
You have configured OSS and NE information. For detailed operations, see 2.3.5 Configuring NE Information on the RAN Side.
Context
l l l When the non-anonymization data analysis switch is set to ON, Nastar analysis tasks are performed using non-anonymized personal data. When the non-anonymization data analysis switch is set to OFF, Nastar analysis tasks are performed using anonymized personal data. If the status of the data anonymization switch is different among multiple M2000 systems that access the Nastar system, you might fail to create an analysis task for analyzing data of multiple M2000 systems. If this occurs, you can turn on the non-anonymization data analysis switch; alternatively, you can contact M2000 engineers to turn on or off the M2000 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 Choose Security > Anonymity Key Management. Step 2 In the displayed Anonymity Key Management window, click NonAnonymization Data Analysis Switch. Step 3 In the displayed NonAnonymization Data Analysis Switch dialog box, select ON or OFF from Settings. The status of the non-anonymization data analysis switch is displayed in State. Step 4 Click OK. The setting is complete. ----End
Follow-up Procedure
l In the left pane of the Anonymity Key Management window, Current Key Info is displayed for the M2000. You can view the status of the data anonymization switch and the current key hash value in State and Current Key Hash Value. Table 2-12 describes the State of the data anonymization switch. Table 2-12 Switch status description Status ON Description The data anonymization switch of the M2000 is turned on.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 53
Issue 01 (2013-07-15)
Status OFF
Description The data anonymization switch of the M2000 is turned off, and therefore the current cipher key hash value is null. The Nastar might fail to set up a connection with the M2000 or the M2000 does not support the data anonymization switch. Therefore, the current cipher key hash value is null.
Abnormal
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 M2000.
NOTE
l If you select Show modified records, you can view the State of the M2000 data anonymization switch, Cipher Key Hash Value, Updated On, and Triggering Mode. If the Nastar task analysis duration includes the time when the M2000 cipher key hash value changes, errors might occur in the task analysis result. l The Nastar system automatically checks the data anonymization switch of the M2000 every 30 minutes. You can select Show all records to view all historical cipher key information.
In the Anonymity Key Management window, you can click Check Now to manually check the current cipher key hash value of the M2000 and click Refresh to manually refresh the historical cipher key information.
Issue 01 (2013-07-15)
54
Table 2-13 Basic data Da ta Ty pe M an dat or y or Op tio nal Ma nda tor y Description
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. Acquisition means: The Nastar automatically retrieves the configuration data from a specific path of the M2000 or OMC after users have configured the OSS information on the Nastar. Data format: The data format is related to NE versions. It can be in .xml.gz, MML, or .dat format.
Op tio nal
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.
Op tio nal
Function: Electronic maps help Nastar to achieve accurate geographic display for desired regions. Acquisition means: Contact the onsite administrator. 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.
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.
Issue 01 (2013-07-15)
55
Da ta Ty pe
Description
Ter mi nal inf or ma tio n VI P inf or ma tio n Co mp lai nin g sub scr ibe r inf or ma tio n
Function: The terminal information, such as the model, radio access technology (RAT), and vendor, is used during terminal analysis. Acquisition means: Contact the onsite administrator. Data format: Terminal information files in .xls, .xlsx, or .csv format can be imported and exported.
Op tio nal
Function: The VIP information, such as a specific VIP and its IMSI, is used during VIP analysis. Acquisition means: Contact the onsite administrator. Data format: VIP files in .csv format can be imported and exported.
NOTE Generally, you obtain the IMSI and MSISDN of a VIP user and enter them into the Nastar. If telecom operators have high requirements for user information security and the anonymous policy is enabled on the network where the Nastar is deployed, all user information such as IMSI, MSISDN, and IMEI contained in the analysis data will be encrypted. To protect the securitysensitive user 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 visit http:// support.huawei.com and choose Software Center > Controlled Tool (Mini-tool Software) > Core Network Product Line > WirelessOSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt user 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 2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key.
Op tio nal
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.
Issue 01 (2013-07-15)
56
Da ta Ty pe
Description
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. Acquisition means: Contact the onsite administrator. Data format: Address books in .xls, .xlsx, or .csv format can be imported and exported.
Op tio nal
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.
Lo cat ion par am ete rs 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.
Op tio nal
Function: The data service servers information is used during VIP analysis for analyzing the servers. Acquisition means: Contact the onsite administrator. Data format: Files in .xls, .xlsx, or .csv format can be imported and exported.
Issue 01 (2013-07-15)
57
Prerequisites
l 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 1 hour. For example, the start time of the data collection service is 7:00, so the next execution time is 8:00. The start time of the data collection service is the same as the start time of the system service. After clicking Immediately Collect Configuration Data on the RAN NE List tab page of OSS information management function, the system will immediately collects configuration data in the OSS instead of collecting the data until the default time. If the system is executing another collection task, the task that you trigger manually will be automatically executed after the running task is complete. l Importing: When detecting the configuration data, the system will import it to the database automatically. This chapter describes the method to check whether the configuration data has been imported to the database.
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. 2. 3. Set Query type. You can query the configuration data of hour-level. 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. 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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 58
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, detailed data information about an NE with data is displayed on an hour basis. On the tab page, green grids indicate that data is available, and white grids indicate that data is not available. If you fail to query configuration data provided that the OSS is configured and the configuration result is normal, contact Huawei technical support engineers. ----End
Follow-up Procedure
l l You can right-click in the right pane and then choose Save As from the shortcut menu to save the current query results as a .csv, .xls, or .xlsx file. View information about the subscription in the Log Info area. Table 2-14 lists the parameters. Table 2-14 Log parameters Parameter Date/Time Level Action Type Action Result OSS Name NE Name Switch Name Details Description Time when a task is complete. Level of the log, including Minor and Major. You are advised to focus on the Major level log information. Action type, including open and close. Action result. The value can be Succeed or Failure. The name of OSS which the subscribed NEs belong to. The name of the subscribed NEs. Switch type. Detailed information about the operation result.
Select Function, Severity, Condition, and type the keyword. Click Filter to filter the log information. It displays the latest 100 log information by default in the Log Info area. Click Show All, the Log Manager window is opened. You can view all of the log information generated within seven days. Click Show All, the Log Manager window is opened. Right-click the log list and choose Save As from the shortcut menu to save the log information.
Issue 01 (2013-07-15)
59
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 27,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.)
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.
TIP
You can also choose System Function > Engineering Parameter Management from the navigation tree in the Analysis Task Management window and right-click Open. The Engineering Parameter Management window is displayed.
Step 2 In the Engineering Parameter Management window, click the *** engineering parameters tab and then click Import. In the name of the tab, *** refers to the network system such as GSM, UMTS, or LTE. Step 3 In the displayed Open dialog box, select an engineering parameter file, and then click Open. If an engineering parameter file in .xls or .xlsx format is selected and the file contains multiple sheets, the system displays a message, prompting you to select the sheet to be imported. Step 4 Configure the column headers.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 60
l At the header of each column, right-click and choose the title of the current column. When you move the pointer to the column header of a column, a pop-up message is displayed, showing the information about this column, for example, Column No./Configured column title/Column title in the engineering parameter file. l Right-click the header of a column and view the field configuration information in the shortcut menu. The column headers marked with the * character must be configured. Otherwise, the import operation is not allowed. l If you need to modify an incorrectly configured column header, right-click the column header, clear the check box next to the original header, and then reconfigure the header. l The engineering parameters must meet the following restrictions in different network systems. For details, see Table 2-15. Otherwise, the engineering parameter file cannot be imported into the database. For details of the mandatory parameters and the range, see Appendix: Engineering Parameter Templates. Table 2-15 Restrictions on engineering parameters Network System GSM Restriction l The mandatory parameters must be configured, and the values of the mandatory parameters must not be empty. l The values of the parameters must be in the specified range. l The value of MCC+MNC+LAC+CI of a cell must be unique. UMTS l The mandatory parameters must be configured, and the values of the mandatory parameters must not be empty. l The values of the parameters must be in the specified range. l The value of RNC ID+CELL ID of a cell must be unique. LTE l The mandatory parameters must be configured, and the values of the mandatory parameters must not be empty. l The values of the parameters must be in the specified range. l The value of eNodeB ID+CELL ID of a cell must be unique.
Step 5 Click OK. Step 6 In the OK dialog box, check the number of added records, updated records, and failed records. Then, click OK. Step 7 Perform the operations as prompted.
Issue 01 (2013-07-15)
61
If... The imported engineering parameter data is correct The imported engineering parameter data is abnormal.
Then... Click Close. 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. 2. In the lower right area, click Close to return to the Engineering Parameters Management window. Click View Synchronize Configuration 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.
Prerequisites
l l Configuration data is imported. For details, see 2.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.
TIP
You can also choose System Function > Engineering Parameter Management from the navigation tree in the Analysis Task Management window and right-click Open. The Engineering Parameter Management window is displayed.
Step 2 In the Engineering parameter management window, click the *** engineering parameters tab. 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. 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. It is only for the GSM engineering parameters. 2. 3. Click Export Checking Results. 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. 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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 63
The file is used to check engineering parameters only on the GSM network. Step 4 Optional: Click Configuration Synchronize to synchronize engineering parameter data with configuration data. After engineering parameter data is imported into the database, the Nastar updates some engineering parameters based on the latest configuration data according to some fields. Table 2-16 describes the parameters are updated. Table 2-16 Update description between configuration data and engineering parameters Network GSM UMTS LTE Fields CGI (MNC + MCC + LAC + CI) RNCID + CELLID ENODEBID + CELLID Parameters to be updated BCC, NCC, BCCH, CELLNAME, and TCH. CELLNAME, PSC, and UARFCNDOWNLINK. 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
Issue 01 (2013-07-15)
64
Description Indicates the name of a site. Indicates the name of a cell. Indicates the mobile country code.
Value Range String, a maximum of 33 characters String, a maximum of 33 characters l Integer l Value range: [000,999] l Integer l Value range: [00,99] l Integer l Value range: [0,65535] l Integer l Value range: [0,65535]
MNC
Mandatory
LAC
Optional
CI
Mandatory
BCCH
l Integer l Value range: [0,1024] l Integer l Value range: [0,7] l Integer l Value range: [0,7] Value range: [-180.0000,180.0000] Value range: [-90.00000,90.00000] Value range: [0.00,360.00] l No: indoor cell l Yes: outdoor cell
Mandatory
BCC
Indicates the base station color code. Indicates the network color code. Indicates the longitude where a cell is located, for example, 116.389722. Indicates the latitude where a cell is located, for example, 39.952778. Indicates the azimuth of an antenna. Indicates whether the cell is an outdoor cell.
Mandatory
NCC
Mandatory
Longitude
Mandatory
Latitude
Mandatory
Azimuth Outdoor
Mandatory Optional
NOTE It is mandatory for the network geographic observation function.
Issue 01 (2013-07-15)
65
Parameter Sectorization
TCH
Optional
AntHeight
l Integer l Value range: [0,65535] l Integer l Value range: [-90.0,90.0] l Integer l Value range: [-90.0,90.0] String, a maximum of 33 characters String, a maximum of 33 characters String, a maximum of 33 characters l No: diversity antenna l Yes: main antenna
Optional
MechTilt
Optional
ElecTilt
Optional
Indicates the antenna vendor. Indicates the antenna type. Indicates the site type. Indicates whether an antenna is the main antenna.
Issue 01 (2013-07-15)
66
Table 2-18 UMTS engineering parameters Parameter RNCID Description Indicates the ID of an RNC. Value Range l Integer l Value range: [0,65535] l Integer l Value range: [0,65535] String, a maximum of 33 characters l Integer l Value range: [0,65535] CellName LAC Indicates the name of a cell. Indicates the location area code of a cell. String, a maximum of 33 characters l Integer l Value range: [0,65535] l Integer l Value range: [0,65535] l Integer l Value range: [0,65535] l Integer l Value range: [0,65535] l Integer l Value range: [0,511] Value range: [-180.0000,180.0000] Value range: [-90.00000,90.00000] Value range: [0,360] Mandatory Mandatory Optional Mandatory Optional Mandatory Optional Mandatory Mandatory Mandatory Optional/ Mandatory Mandatory
NodeBID
NodeBName CellID
RAC
UARFCNDo wnlink
UARFCNUpl ink
PSC
Longitude
Indicates the longitude where a cell is located, for example, 116.389722. Indicates the latitude where a cell is located, for example, 39.952778. Indicates the azimuth of an antenna.
Latitude
Mandatory
Azimuth
Mandatory
Issue 01 (2013-07-15)
67
Parameter Outdoor
Sectorization
Optional
NOTE It is mandatory for the network geographic observation function.
SAC
l Integer l Value range: [0,65535] l Integer l Value range: [0,65535] l Integer l Value range: [-90.0,90.0] l Integer l Value range: [-90.0,90.0] String, a maximum of 33 characters String, a maximum of 33 characters String, a maximum of 33 characters
Optional
AntHeight
Optional
MechTilt
Optional
ElecTilt
Optional
Indicates the antenna type. Indicates the antenna vendor. Indicates the site type.
Issue 01 (2013-07-15)
68
Table 2-19 LTE engineering parameters Parameter eNodeBNam e SiteName CellName eNodeBID Description Indicates the name of an eNodeB. Indicates the name of a site. Indicates the name of a cell. Indicates the ID of an eNodeB. Value Range String, a maximum of 32 characters String, a maximum of 33 characters String, a maximum of 33 characters l Integer l Value range: [0,65535] l Integer l Value range: [0,16] l Integer l Value range: [0,32] l Integer l Value range: [0,65535] PhyCellID Indicates the ID of a physical cell. l Integer l Value range: [0,503] l Integer l Value range: [0,65535] Value range: [-180.00000,180.000 00] Value range: [-90.00000,90.00000] Value range: [0,360] l Integer l Value range: [0,65535] Mandatory Optional Mandatory Mandatory Optional Optional Optional/ Mandatory Mandatory Mandatory Mandatory Mandatory
SectorID
LocalCellID
CellID
TAC
Longitude
Indicates the longitude where a cell is located, for example, 116.389722. Indicates the latitude where a cell is located, for example, 39.952778. Indicates the azimuth of an antenna. Indicates the antenna height.
Latitude
Mandatory
Azimuth AntHeight
Mandatory Optional
Issue 01 (2013-07-15)
69
Parameter MechTilt
Value Range l Integer l Value range: [-90.0,90.0] l Integer l Value range: [-90.0,90.0] String, a maximum of 33 characters String, a maximum of 33 characters l No: indoor cell l Yes: outdoor cell
ElecTilt
Optional
Indicates the antenna vendor. Indicates the antenna type. Indicates whether a cell is an outdoor cell.
UARFCNUp link
l Integer l Value range: [0,65535] l Integer l Value range: [0,65535] l String l Value range: YES, NO. String, a maximum of 33 characters l Omni: omnidirectional cell l Sectorize: directional cell
Mandatory
UARFCNDo wnlink
Mandatory
OnAir
Optional
SiteType Sectorization
Optional Optional
NOTE It is mandatory for the network geographic observation function.
Issue 01 (2013-07-15)
70
Context
Nastar provides two modes for viewing analysis results on a map, as shown in Figure 2-13. Figure 2-13 Displaying analysis results on a map
Prerequisites
l l The PC is connected to the Internet. The Google Earth is installed in the PC.
Context
The principles for displaying the Nastar data on the Google Earth are as follows: l After the engineering parameters are read, the geographic data is displayed on the scale of 2,600 meters at heights and with the last cell in the engineering parameter list being in the center by default. The Nastar data can be displayed on the Google Earth synchronously. The geographic data is displayed on the scale of 2,600 meters at heights with the selected cell being in the center.
NOTE
The description of operations related to the Google Earth is not provided in this document.
Procedure
Step 1 Choose Tools > Google Earth. The EarthViewWindow window is displayed. The system loads the Google Earth components through the Internet. After the loading is complete, the system automatically reads the engineering parameters in the Nastar system and displays the engineering parameters as labels on the Google Earth.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 71
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
Prerequisites
A map file in .wor or .tab format is available on the PC.
NOTE
l Before importing a TAB map file, you must verify that a DAT or DBF file that has the same file name as the TAB map file exists in the directory for saving map files. If such file does not exist, converting file format fails. l Before importing a WOR map file, you must verify that the TAB map files that form the WOR map file exist in the directory for saving map files. If such files do not exist, converting file format fails.
Context
It takes a long time to import a WOR or TAB map file. If users on multiple clients attempt to import the same map file, the work efficiency is low. To solve this problem, the Nastar allows users to convert a WOR or TAB map file to an SXWU map file and import the file because the Nastar can quickly identify and import SXWU map files and allows multiple users to share the SXWU map files. This greatly improves the efficiency of importing map files. It is recommended that the map files be converted by one person, and then be shared to others.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 72
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. It takes about 3 minutes to convert 1 MB map files. The file after format conversion is saved in a folder, which contains multiple files. In the folder, the File Name.sxwu file is used to import map data. ----End
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.
Context
CAUTION
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.
Procedure
Step 1 Click Step 2 Click on the toolbar. The Geographic Observation window is displayed. 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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 73
If the map file is in WOR orTAB format, the import speed and the operation response are slow. You are advised to see Converting the Map File Format and convert the map file into an SXWU map file. You can import the SXWU map file to improve file-importing efficiency. ----End
Prerequisites
You have configured the information about the OSS and NEs. For detailed operations, see 2.3 Configuring OSS and NE Information.
Context
l 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, and Remarks, as shown in Table 2-20. The sequence for matching each column must be the same as that in the following example. Table 2-20 Examples of NE group files NE Group Name Group1 Group2 BSC Name A B Cell Name a b LAC CI Remarks
12121 21212
21212 12121
NA 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, and Remarks. An eNodeB group file of the LTE FDD/TDD network to be imported must contain the following fields: NE Group Name, NE Group Type, eNodeB Name, eNodeB ID, and Remarks. A cell group file of the LTE network to be imported must contain the following fields: NE Group Name, NE Group Type, eNodeB Name, eNodeB ID, Cell Name, Cell ID, and Remarks. 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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 74
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. l For the LTE FDD/TDD network, you must create NE groups before using the analysis functions except the complaint analysis support function.
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.
TIP
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. Set relevant parameters. The Nastar supports the function of searching for objects in the object navigation tree. You can click anywhere in the navigation tree and then press Ctrl+F to search for and locate objects. Table 2-21 describes the parameter settings. Table 2-21 Description of NE group parameters Parameter Group Name Description 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. NE Group Type (You need to set this parameter only when creating LTE NE groups) Element List Type of an NE group. The LTE network supports the following NE group types: l eNodeB Group l Cell Group Select required NEs.
3.
Issue 01 (2013-07-15)
75
Parameter Note
Description Description of an NE group. Value range: l A maximum of 250 characters l Characters not allowed: ~ ! # $ % ^ * + = | \ / , ' ` : " <>?
4. l 1.
Click OK. 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. 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
2.
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. No. 1 Procedure Opening the map window Step On the toolbar of the main window, click Observation window is displayed. . The Geographic
Issue 01 (2013-07-15)
76
No. 2
2. Add points to the polygon one by one in the Geographic Observation window.
NOTE The lines of a polygon must not intersect. Otherwise, certain selected areas may be missed out.
3. After the last point is added, double-click or right-click in the window to exit the polygon drawing. In addition, the Label dialog box is displayed. 4. Set the name of the polygon. 5. Click OK. The polygon drawing is complete. The Geographic Observation window displays the polygon and its name. In addition, the polygon name is added to the Polygon Areas node in the navigation tree in the left pane. 3 Setting filtering criteria to filter the cells in the defined area and with the specified network system and engineerin g parameter fields Saving the filtered cells as an NE group 1. Click on the toolbar. The Search dialog box is displayed.
2. Select a RAT in Network Technology. 3. Select the area you want to filter in Region. 4. Set engineering parameters in the lower left corner of the dialog box. The Nastar supports filtering of all engineering parameters. Generally, you can set one or two parameters as the filter criteria. The logical operator between the two parameters can be set to And or Or.
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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 77
Then... 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 2-21. 4. Click OK.
NOTE 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. TIP 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.
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.
Relationship
Figure 2-14 shows the relationship between VIP groups and VIP users.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 78
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.
l l l
Technical Specifications
Table 2-22 describes the technical specifications of the VIP group and the VIP user.
Issue 01 (2013-07-15)
79
Table 2-22 Technical specifications for VIP group management 1 Item Number of allowed VIP groups Number of allowed VIP subscribers Task Management Capacity <= 1,000 VIP subscribers are classified into important VIP subscribers and common VIP subscribers. The total number of important and common VIP subscribers is not allowed to exceed 30,000. The following describes the specifications for the two levels of VIP subscribers: l Common VIP subscribers: <= 30,000 (summarization analysis supported) l Important VIP subscribers: <= 500 (signaling tracing analysis supported)
NOTE
VIP subscribers move across networks of different types. Therefore, the technical specifications for VIP management have nothing to do with network types. No matter how many types of networks there are, the Nastar supports a maximum of 30,000 VIP subscribers and a maximum of 1,000 VIP groups.
The number of important VIP subscribers that support signaling tracing analysis on the radio access network (RAN) side depends on the capability of the NE. Therefore, the value of supported numbers varies with NE version. For details, see Table 2-23. Table 2-23 Technical specifications for VIP group management 2 Network Type GSM UMTS LTE Earliest NE Version Supported GBSS13.0 RAN13.0 eRAN6.0 Number of Important VIP Subscribers That Support Signaling Tracing Analysis <= 500/BSC <= 100/RNC <= 500/eNodeB
Prerequisites
l l You are authorized to manage VIP groups. You have obtained VIP user information, including the MS number, IMSI, and user class.
Context
You can create a VIP group using either of the following methods:
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 80
l l
Create a VIP group directly Create a VIP group by importing a file. VIP group files in .csv format can be imported and exported. The VIP group file to be imported must include the following fields as shown in Table 2-24. The column sequence must be the same as that in the following example, which is the same as that on the Nastar. Table 2-24 Sample VIP group file No. 1 2 Group Name Group 1 Group 2 Number of Members 50 100 Description Secondary department director of ** Group 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.
TIP
You can also choose System Function > VIP Group Management from the navigation tree in the Analysis Task Management window and right-click Open. The VIP Group Management window is displayed.
Step 2 Click the VIP Group tab. Step 3 Create a VIP group. If you need to... Create a VIP group directly Then... 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.
Issue 01 (2013-07-15)
81
Then...
Create VIP groups by importing a file 1. Click Import. The Open dialog box is displayed. 2. Select a VIP group file. VIP group files in .csv format can be imported and exported. For the requirements of a VIP group file, see Table 2-24. 3. Click Open. If the file contains multiple worksheets, a prompt is displayed for you to select the desired worksheet. The imported VIP groups are displayed on the VIP Group tab page. Step 4 Add VIP users to VIP groups. 1. 2. 3. On the VIP Group tab page, select a VIP group, and click Modify/View. Click Select in Members. Select one or multiple VIP users from the existing VIP user list, and click OK. If the required VIP user is unavailable in the existing VIP user list, click New or Import to create a VIP user. For detailed parameter descriptions, see Managing VIP Users. Click OK.
4.
----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.
Then... 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.
Issue 01 (2013-07-15)
82
Then... Click Modify/View. In the displayed Modify/View VIP Group dialog box, change the values of VIP group parameters. The VIP group name cannot be changed. You can change the values of Members and Description. Change the value of Members. l Click Select to add an existing VIP user to the VIP group. l Click New to create a VIP user and then add it to the VIP group. l Click Delete to delete a VIP user that has been added to the VIP group.
CAUTION l Issue the subscription task again after the VIP group is updated so that the VIP subscription function is not affected. l If an existing VIP user not involved in data subscription is added to a VIP group for which data subscription has been performed, a message will be displayed indicating that you need to perform the subscription again. l If you attempt to delete a VIP user from a VIP group involved in data subscription, a message will be displayed indicating that you have to cancel the subscription before the deletion. l A VIP user can be analyzed only after the VIP user is grouped into VIP groups. Therefore, if the VIP user you want to delete belongs only to the current VIP group, you will not be allowed to delete the VIP user.
Double-click a VIP group to view the detailed information. On the VIP Group tab page, right-click the VIP group list, and choose Save As from the shortcut menu.
Prerequisites
l You are authorized to manage VIP groups. The entered subscriber information by using the VIP subscriber management function contains real personal information, such as the MSISDN and IMSI. Therefore, user rights of this function must be properly managed to protect real subscriber information from being leaked. You have obtained VIP user information, including the MSISDN, IMSI, and user class.
NOTE
Generally, you obtain the IMSI and MSISDN of a VIP user and enter them into the Nastar. If telecom operators have high requirements for user information security and the anonymous policy is enabled on the network where the Nastar is deployed, all user information such as IMSI, MSISDN, and IMEI contained in the analysis data will be encrypted. To protect the security-sensitive user information, the Nastar no longer allows you to enter the plaintext IMSI and MSISDN. In this situation, you need to contact telecom operators to obtain the encrypted IMSI. The Nastar does not support the encrypted MSISDN. Telecom operators can visit http://support.huawei.com and choose Software Center > Controlled Tool(Mini-tool Software) > Core Network Product Line > Wireless-OSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt user 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 2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key.
Context
You can create a VIP user using either of the following methods: l l Create a VIP user directly. Create VIP users by importing a file. VIP user files in .csv format can be imported and exported.
NOTE
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, information in the IMSI column might be abnormally displayed as non-text characters such as 4.60029E+14. When this happens, you can convert the nontext characters into text characters so that the information in the IMSI column can be normally displayed, such as 123231213424124. If you use the notepad to open a file in .csv format, however, information in the file is displayed normally. Therefore, you are advised to open a file in .csv format by using the notepad.
The VIP user file you want to import must include the following fields as shown in Table 2-25. The column sequence must be the same as that in the following example, which is the same as that on the Nastar. Table 2-25 Sample VIP user file No. 1 2 3 Alias a1 b2 c3 Phone Number 66036439 91268866 25452452 IMSI 123231213424 124 123231213424 125 123231213424 126 Class Important Common Common VIP Group A,B A A,B,C Descrip tion User a User b User c
Issue 01 (2013-07-15)
84
Procedure
Step 1 Double-click System Function > VIP Group Management in the navigation tree on the left side of the Analysis Task Management window.
TIP
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 users and add them to VIP groups. If you need to... Create a VIP user directly Then... 1. Click New. The Create VIP User dialog box is displayed. 2. Set VIP user information. If the asterisk (*) is present on the right of a parameter, the setting of this parameter is mandatory. Table 2-26 lists the detailed parameter descriptions. 3. Click OK. The new VIP user is displayed on the VIP User tab page. Create VIP users by importing a file 1. Click Import. The Open dialog box is displayed. 2. Select a VIP user file. VIP user files in .csv format can be imported and exported. To learn the requirements for a VIP user file, see Table 2-25. 3. Click Open. If the file contains multiple worksheets, a warning is displayed for you to select the desired worksheet. The imported VIP users are displayed on the VIP User tab page.
Issue 01 (2013-07-15)
85
Table 2-26 VIP user information parameters Parameter Alias Description Indicates the name alias of a VIP user, which is not the real name of the user. Function: The VIP user alias, together with the user ID automatically allocated by the system in the VIP analysis results, uniquely identify a user. 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 user can have multiple MSISDNs. Phone Number Indicates the MSISDN of a VIP user. Function: l In the VIP group management function, it facilities the maintenance of VIP information. l In the complaint analysis support function, the MSISDN is used to control operations of unauthorized Nastar users; that is, prevent unauthorized Nastar users from performing complaint analysis by using a VIP user's MSIDSN. Value range: l When the anonymous policy is disabled on the network where the Nastar is deployed, enter the MSISDN of a VIP user. Value range: A 1- to 16-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, obtain the encrypted MSISDN of a VIP user from the telecom operator and then enter the encrypted MSISDN. Value range: A 1- to 16-digit alphanumeric string composed of 0-9 and A-F. l The MSISDN must be unique and maps the IMSI. One IMSI maps only one MSISDN. IMSI Indicates the IMSI of a VIP user. Function: The system can collect the analysis data from the network through the IMSI information. Value range: l When the anonymous policy is disabled on the network where the Nastar is deployed, enter the IMSI of a VIP user. Value range: A 15-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, obtain the encrypted IMSI of a VIP user 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.
Issue 01 (2013-07-15)
86
Parameter Class
Description VIP users fall into two classes: l Important: important VIP users, supporting all types of analysis including aggregation analysis, in-depth record analysis, and allsignaling analysis. A maximum of 500 important users are supported. l Common: common VIP users, supporting only aggregation analysis and in-depth record analysis. A maximum of 30,000 common users are supported. Function: The class is used to control the users to view different types of analysis results.
Description
Indicates the description of a VIP user. Value range: l The name contains a maximum of 250 characters. l Characters not allowed: ~ ! # $ % ^ * + = | \ / ' ` " < > ? :
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.
----End
Follow-up Procedure
On the VIP User tab page, select a VIP user, and then perform operations as required.
NOTE
If the VIP user is used by other tasks, the modification does not affect the ongoing tasks. If the VIP user is used by a periodic task, the related information is updated in the next period after the modification. If a newly created VIP user 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.
Then... On the VIP User tab page, right-click the VIP user list and choose Search from the shortcut menu. Enter a keyword to quickly find a VIP user. 1. Select a VIP user, and click Modify/View. The Modify/View VIP User window is displayed. 2. Set one or multiple fields among User Name, Phone Number, Class, Description, and VIP Group.
NOTE The IMSI of a VIP user cannot be modified.
3. Click OK.
Issue 01 (2013-07-15)
87
If you need to... Add or delete the VIP group to which a VIP user belongs Import VIP users
Then... 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 user belongs. Click Import. If the file contains multiple worksheets, a warning is displayed for you to select the desired worksheet.
1. Select a VIP user record or press Ctrl to select multiple VIP user records and click Delete. 2. In the displayed dialog box, click Yes.
On the VIP User tab page, right-click the VIP user list, and choose Save As from the shortcut menu.
Prerequisites
l l You are authorized to manage terminal information. You have obtained the terminal information.
Context
l The system supports a maximum number of terminal types as follows: 10,000 (the Nastar hardware configuration is matched with the 400 equal NEs network size.) 100,000 (the Nastar hardware configuration is matched with the 800 equal NEs network size.) l You can create a terminal type using either of the following methods: Create a terminal type directly. Create a terminal type by importing a file. Terminal type files in .csv, .xls, and .xlsx formats can be imported and exported.
NOTE
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.
Issue 01 (2013-07-15)
88
The terminal type file to be imported must include the following fields: IMEI-TAC, Vendor, and Terminal Model. The sample of terminal type file is shown in Table 2-27. Table 2-27 Sample terminal type file IMEITAC Vendo r Termi nal Model AB800 Chip Model Termi nal Type Cell phone Cell phone Data Transf er GPRS/ EDGE/ HSDPA GPRS/ EDGE Termi nal Techn ology WCDM A GSM Suppo rt WiFi Support
860004 00 860043 00 l
Huawei
Huawei 8 Huawei 9
SAMS UNG
GTI6320C
Not Support
If the default terminal attributes cannot meet your requirement when you create terminal types, you can define terminal attributes. 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, and .xlsx format can be imported and exported. Table 2-28 shows a sample terminal attribute file. Table 2-28 Sample terminal attribute file Attribute Name Terminal Type Terminal Type Terminal Technology Terminal Technology Optional Parameter Feature Phone Data Card GSM 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.
TIP
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.
Issue 01 (2013-07-15)
89
If you need to... Create a terminal type directly Create a terminal type by importing a terminal type file Step 3 Create a terminal type directly. 1. 2.
Click New in the lower right corner. The Terminal Type Management-New dialog box is displayed. Set parameters listed in Table 2-29. If the asterisk (*) is present on the right of a parameter, the setting of this parameter is mandatory. Table 2-29 Terminal type parameters Parameter IMEI-TAC Description Indicates the first eight digits of the International Mobile Equipment Identity (IMEI) that identifies the type of a terminal. Indicates the vendor of a terminal. Indicates the model of a terminal. Indicates the chip model. Indicates the technology the terminal supports. The default technologies include GSM, WCDMA, TDSCDMA, GSM/WCDMA, GSM/TD-SCDMA, and LTE. If the default terminal attributes cannot meet the statistical requirements, define terminal attributes. For details, see Step 5. The default terminal attributes and their values cannot be deleted, but values can be added to the default terminal attributes. 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. 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. Optional Optional/ Mandatory Mandatory
Issue 01 (2013-07-15)
90
Description Indicates the type of a terminal. The default terminal types include Feature Phone, Smartphone, Data Card, Wireless Landline, Family Gateway. If the default terminal attributes cannot meet the statistical requirements, define terminal attributes. For details, see Step 5. The default terminal attributes and their values cannot be deleted, but values can be added to the default terminal attributes.
Support WiFi
Optional
3.
Click OK.
Step 4 Create a terminal type by importing a terminal type file. 1. 2. Click Import in the lower right corner. The Open dialog box is displayed. 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. 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.
Issue 01 (2013-07-15)
91
Then... 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... Modify a terminal attribute and its value Then... 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. Delete a terminal attribute and its value Only user-defined terminal attributes can be deleted. 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, 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 1. In the Terminal Type Management window, right-click the table header and choose Customize Column from the shortcut menu. The Customize Column dialog box is displayed. 2. Click Export. 3. Set the file name and specify the save path and file type. Then, click Save.
Issue 01 (2013-07-15)
92
Then... 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 type 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.
1. In the Terminal Type Management window, select one or multiple terminal types, and click Delete. 2. In the displayed dialog box, click Yes. If a terminal type is used by certain tasks, the modification does not affect the ongoing tasks. If a terminal type is used by a periodic task, the related information is updated in the next period after the modification.
1. In the Terminal Type Management window, click Filter. The Filter dialog box is displayed. 2. Set the filter condition and the filter context. 3. Click OK. The system will filter out the terminal information that meet the filter condition and the filter context.
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.
Prerequisites
l 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 93
Issue 01 (2013-07-15)
Context
Use either of the folloiwng methods to configure the information about a data service server: l 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 2-30. The column sequence must be the same as that in the following example. Table 2-30 Example of a data service server file Server IP 11.111.11.1 1 22.222.222. 22 Server Name Huawei A Service Huawei B Service Port 21 443 Service Name FTP service HTTPS service Remark -
Procedure
Step 1 Double-click System Function > Data Service Server Management in the navigation tree of the Analysis Task Management window.
TIP
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 Management window is displayed.
Step 2 Configure the information about a data service server. If You Need to... Directly configure the information about a data service server. Then... 1. Click New. The New Data Service Server dialog box is displayed. 2. Set Server IP, Server Name, Port, Service Name, and Remark. Table 2-31 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.
Issue 01 (2013-07-15)
94
Then...
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 2-30 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 2-31 Settings of data service server parameters Parameter Server IP Server Name Description IP address of a data service server. For example, 11.111.111.11. A maximum of 15 characters are allowed. 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.
Port number of a data service server for a service. The value ranges from 0 to 65534. Name of a service running on a data service server. A maximum of 64 characters are allowed. 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 ... Search for a data service server. Then... Right-click the data service server list in the Data Service Server Management window and choose Search from the shortcut menu. Then, type keywords to quickly locate the data service server. Click Modify/View to re-set the parameters of a data service server.
95
If You Need to ... Export the information about a data service server. Delete the information about a data service server.
View the information about a data service server. Save the information about a data service server.
Double-click a data service server record. Right-click the data service server list in the Data Service Server Management window and choose Save As from the shortcut menu.
Prerequisites
You are authorized to manage PS Core knowledge bases.
Context
l l PS Core knowledge bases include the SGSN/MME knowledge base and GGSN/SAE-GW knowledge base. Each of the knowledge bases supports a maximum of 10,000 records. 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 2-32. Step 3 Optional: If an existing record in a knowledge base does not meet requirements, you can modify it or create new ones.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 96
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 2-32. l To import records in batches, click Import and select a file you want to import. The Nastar does not allow you to import a record with the same cause value as an existing record in the knowledge bases.
NOTE Comply with the following rules when you edit the records exported in a csv file and then import the records into the knowledge databases: l If the information in a table cell contains commas (,) or line feeds, add a pair of quotation marks (") to include the information. l If the information in a table cell is included in a pair of quotation marks ("), add one more pair of quotation marks (") to include the information.
Table 2-32 Parameters recorded in the knowledge bases Parameter Cause Description Hexadecimal value, which is the unique identifier of a record. l Cause value range for SGSN/MME: 0x0 to 0xFFFF l Cause value range for GGSN/SAE-GW: 0x0 to 0xFFFFFFFF Failure cause description Solution Note Description of a failure cause. Solutions to failures. You can solve problems by referring to this description. Remarks. Knowledge bases apply to any NE versions. If there are differences between failure cause description and solutions, you are advised to add remarks. Mandatory Mandatory Optional Optional/ Mandatory Mandatory
----End
Follow-up Procedure
If you need to... Delete a record
Issue 01 (2013-07-15)
Then... Click Export and set the name of the file you want to import. The Nastar then exports all existing records. Click Resume. The Nastar restores the default knowledge base information during initial Nastar installation.
2.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 l You have obtained the mailbox information, including the server address, mail address, user name, and password. You have obtained the addressee information.
Context
The Nastar allows you to create an address list using either of the following methods: l 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: Name, Email, and Remark, as shown in Table 2-33. The match sequence of columns is specified and automatic matching of columns is not supported. Table 2-33 Example of the address list Name a1 b2 Email a12121212@huawei.com b90909090@yahoo.com Remark ** CEO ** PM
Procedure
l Do as follows to set the mailbox for sending analysis reports: 1. 2. Choose Maintenance > Email Settings. The Email Settings window is displayed. Set the parameters for the mailbox in Table 2-34.
Issue 01 (2013-07-15)
98
Table 2-34 Parameters for setting the mailbox for sending analysis reports Parameter SMTP Host Name or Address Description Address of the sending email server. 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. 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 size of attachments exceeds the specified threshold, you will receive an email prompting you to obtain the analysis report from the specified directory of the Nastar server through FTP. Is it required to authenticate 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. User Name Password 3. l 1. 2. 3. Click OK. Choose Maintenance > Auto-Distribution User Management. The AutoDistribution User Management window is displayed. Click New. The New User window is displayed. You can click Import to add users. Set the parameters for the mailbox in Table 2-35. Table 2-35 Parameter for setting the addressee Parameter Name Email Remarks 4. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 99
User name used to log in to the email sending server. Password used to log in to the email sending server.
Description User name of the addressee. Email address of the addressee. Description of the email to be sent.
Click OK.
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.
Procedure
Step 1 In the navigation tree of the Analysis Task Management window, double-click System Function > Geo-Location Parameter Management. Step 2 In the displayed Geo-Location Parameter Management window, view the existing origin records. The system performs analysis based on the latest origin record. For detailed historical origin parameters, see Table 2-36. Table 2-36 Historical origin parameters Parameter No. Delivered On Origin Delivery Mode Description Number of the historical origin. Time when the origin was delivered. 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.
Issue 01 (2013-07-15)
100
Step 3 Set the origin if the existing origin records do not meet requirements. 1. 2. 3. 4. In the Geo-Location Parameter Management window, select a record. Click Parameter Settings. Change the grid origin. 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 2-37. Table 2-37 Log parameters Parameter Delivered On Severity Description Time when the task was delivered. 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. Name of the NE involved in the task. Result of the operation. The value of this parameter can be Success or Fail. Details about the operation result.
l l l
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.
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. 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. Application data subscription is used to deliver specific rule files to NEs so that NEs can generate raw data that meets the analysis requirements.
Basic subscription is required for almost all analysis themes. Application subscription is required for only a few analysis themes. About the conditions and purposes of applying basic subscription and application subscription for different themes, refer to 2.5.4 Appendix: List of Data Subscription Function of All the Analysis Function.
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 l Administrator: has the permission to query and set the subscription status of all NEs and VIP users. Common user: has the permission to query the subscription status of only specified NEs and VIP 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. The administrator grants users permission to query and set NEs and VIP objects so that different users have the permission to query or set the subscription status of different NEs and VIP objects.
Figure 2-15 shows the application scenarios for the two roles to use the analysis data subscription function. Figure 2-15 Application scenarios of the data subscription function
Issue 01 (2013-07-15)
102
Table 2-38 Scenario description of the data subscription function User Applica tion Scenari o Initial configura tion Description Example
Admin istrator
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. 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. -
The administrator can obtain information for routine maintenance in the following ways: l The administrator periodically updates the data subscription status on the live network. If a data switch that should be turned on is in the OFF state, the administrator needs to enable the data subscription function again and turns on the data switch. l A common user queries the data switch status on the live network and finds that the certain data switch status does not meet analysis requirements. In this case, the administrator enables the data subscription function again and turns on these data switches.
Issue 01 (2013-07-15)
103
User
Description
Example
Comm on users
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.
Prerequisites
l l l You have the permissions to manage analysis data subscription. The OSS and NEs involved in an analysis task have been created. For detailed operations, see 2.3.4 Configuring OSS Information. Configuration data has been imported. For details, see 2.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.
Procedure
Step 1 Choose Maintenance > Data Subscription Management. The Data Subscription Management window is displayed. Step 2 Click a tab for an RAT in the Data Subscription Management window. Step 3 In the NE object navigation tree, select the required NEs.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 104
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 Click Set on the Basic Subscription Settings tab page. The Basic Subscription Settings dialog box is displayed. Step 5 Set the data switch status of each analysis theme to ON. Basic subscription of analysis data has the following states: l ON: turn on the data switches of the selected NEs for corresponding analysis themes. l OFF: turn off the data switches of the selected NEs for corresponding analysis themes. This operation is not recommended. l No Modification: The data switch status has not ever been changed by using the Nastar. This is the default state.
NOTE
Certain analysis themes use data of the same type. For example, complaint analysis, VIP analysis, and cell performance analysis use the CHR data. If you change the status of the data switch for a type of data in one analysis theme, the status of the data switch for this type of data in all other analysis themes changes accordingly. For example, the status of the data switch for CHR data in both VIP analysis and cell performance analysis is changed to ON if you change the status of the data switch for CHR data in complaint analysis support to ON.
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 Select Um Message about All Signaling parameter. After subscribing successfully, the CHR data generated by the NEs will contain all the signaling information of the Um interface. 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. 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
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.
Step 7 Click Confirm. The Nastar starts to deliver commands to the NEs to turn on their data switches. The operation information is displayed in the Log Info area. ----End
Follow-up Procedure
l After the basic subscription, click Refresh to view the data switch status of each NE on the live network in Table 2-39.
Issue 01 (2013-07-15)
105
Table 2-39 Data switch status Icon Status ON Description 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. The data switch of an NE for an analysis theme on the live network is in the OFF state, not meeting analysis requirements of the Nastar. 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. The data switch of an NE for an analysis theme on the live network is in the Unknown state. The Nastar cannot detect the data switch status. The possible causes are as follows: l The communication between the Nastar and the M2000/OMC is abnormal. l The communication between the M2000/ OMC and NEs is abnormal. l NEs are not in normal running status. For example, NEs are being upgraded or have been shut down. 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.
OFF
Processing
Unknown
Issue 01 (2013-07-15)
106
Icon
Status NonSupport
Description 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.
NOTE
l In general, querying data switch status of an NE takes about two seconds. If the data switch status of multiple NEs is queried, more time is required. l You can click Cancel to cancel the data switch status query.
View information about the subscription in the Log Info area. Table 2-40 lists the parameters. Table 2-40 Log parameters Parameter Date/Time Level Action Type Action Result OSS Name NE Name Switch Name Details Description Time when a task is complete. Level of the log, including Minor and Major. You are advised to focus on the Major level log information. Action type, including open and close. Action result. The value can be Succeed or Failure. The name of OSS which the subscribed NEs belong to. The name of the subscribed NEs. Switch type. Detailed information about the operation result.
Select Function, Severity, Condition, and type the keyword. Click Filter to filter the log information. It displays the latest 100 log information by default in the Log Info area. Click Show All, the Log Manager window is opened. You can view all of the log information generated within seven days. Click Show All, the Log Manager window is opened. Right-click the log list and choose Save As from the shortcut menu to save the log information.
preprocessing functions of the SAU and eSAU, 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.
Prerequisites
l l l l l l You have the permissions to manage analysis data subscription. You have created the OSS and NEs involved in an analysis task. For detailed operations, see 2.3.4 Configuring OSS Information. You have imported the configuration data. For detailed operations, see 2.4.2 Checking the Integrity of Configuration Data. You have performed basic subscription of analysis data. For detailed operations, see 2.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.
Context
Application subscription is not required for certain analysis themes. To learn the data you must subscribe to for the analysis themes, see 2.5.1 Basics of Data Subscription.
Procedure
Step 1 Choose Maintenance > Data Subscription Management. The Data Subscription Management window is displayed. Step 2 Click a tab for an RAT in the Data Subscription Management window. Step 3 In the NE object navigation tree, select the required NEs. On the *** Analysis tab page, application subscription status of the selected NEs is displayed. During the initial setting, all application subscription status is OFF or Unknown. Step 4 Click ON on the tab page. The *** Analysis Parameter Setting dialog box is displayed. Step 5 Set application subscription parameters. The application subscription GUI varies based on analysis theme. For details about the application subscription parameters of each analysis theme, see *** Network Optimization > *** Analysis > Process of *** Analysis in the Online Help. Step 6 Click Confirm. The Nastar starts to deliver rule files to the NEs. The operation information is displayed in the Log Info area. ----End
Follow-up Procedure
l After the application subscription of analysis data, click Refresh to view the application subscription status in Table 2-41.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 108
Issue 01 (2013-07-15)
Table 2-41 Application subscription status Icon Status ON OFF Processing Description The Nastar has delivered rule files to NEs to obtain analysis data. The Nastar does not deliver rule files to NEs. The Nastar is delivering or canceling delivering the rule files to NEs, the status is Processing. 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.
Unknown
View information about the subscription in the Log Info area. Table 2-42 lists the parameters. Table 2-42 Log parameters Parameter Date/Time Level Action Type Action Result OSS Name NE Name Switch Name Details Description Time when a task is complete. Level of the log, including Minor and Major. You are advised to focus on the Major level log information. Action type, including open and close. Action result. The value can be Succeed or Failure. The name of OSS which the subscribed NEs belong to. The name of the subscribed NEs. Switch type. Detailed information about the operation result.
Issue 01 (2013-07-15)
109
Select Function, Severity, Condition, and type the keyword. Click Filter to filter the log information. It displays the latest 100 log information by default in the Log Info area. Click Show All, the Log Manager window is opened. You can view all of the log information generated within seven days. Click Show All, the Log Manager window is opened. Right-click the log list and choose Save As from the shortcut menu to save the log information.
2.5.4 Appendix: List of Data Subscription Function of All the Analysis Function
Basic subscription is required for almost all analysis themes. Application subscription is required for only a few analysis themes. This chapter lists the conditions and purposes of applying basic subscription and application subscription for different themes. l l l l l GSM UMTS LTE TDD LTE FDD PS Core
GSM
Table 2-43 Data subscription for different themes (GSM) Theme Required Data Whether Data Subscriptio n Is Required Basic subscription: No Application subscription: Yes GSM Neighbo ring Cell Analysis Performanc e data and neighboring cell measureme nt data Basic subscription: No Application subscription: Yes Basic subscription: No Purpose
GSM MR Analysis
Performanc e data
Basic subscription: -
Application subscription: Obtain NE performance data from the M2000. Basic subscription: -
Application subscription: Set neighboring cell measurement parameters of NEs so that the Nastar can obtain performance data that meets the analysis requirements. Basic subscription: -
110
Theme
Required Data
Whether Data Subscriptio n Is Required Application subscription: Yes Basic subscription: No Application subscription: Yes
Purpose
measureme nt data
Application subscription: Set neighboring cell measurement parameters of NEs so that the Nastar can obtain performance data that meets the analysis requirements. Basic subscription: -
Performanc e data
Application subscription: Set neighboring cell measurement parameters of NEs so that the Nastar can obtain performance data that meets the analysis requirements. Basic subscription: -
Application subscription: Set frequency measurement parameters of NEs so that the Nastar can obtain scanned uplink frequency data that meets the analysis requirements. Basic subscription: l GSM complaint analysis support data (MRCS), optional: Turn on the MR switch. The information in the MR data can replace the original measurement report information in the CHR data, so that measurement report information more comprehensively and the voice quality analysis more accurately. l GSM complaint analysis support data (CHRCS): Turn on the CHR switch for the CS service and enable MSs to report international mobile subscriber identities (IMSIs). l GSM complaint analysis support data (CHRPS): Turn on the CHR switch for the PS service.
Application subscription: No
Application subscription: -
Issue 01 (2013-07-15)
111
Theme
Required Data
Purpose
CHR data
Basic subscription: l GSM VIP analysis data (CHR-CS): Turn on the CHR switch for the CS service and enable MSs to report IMSIs. l GSM VIP analysis data (CHR-PS): Turn on the CHR switch for the PS service.
Application subscription: Yes GSM Cell Perform ance Analysis CHR data Basic subscription: Yes
Application subscription: Set VIP objects and NE objects. Basic subscription: l GSM cell performance analysis data (CHRCS): Turn on the CHR switch for the CS service and enable MSs to report IMSIs. l GSM cell performance analysis data (CHRPS): Turn on the CHR switch for the PS service.
Application subscription: Yes GSM Termina l Analysis CHR data Basic subscription: Yes
Application subscription: Set the exception thresholds of KPIs. Basic subscription: l GSM terminal analysis data (CHR-CS): Turn on the CHR switch for the CS service and enable MSs to report IMSIs. l GSM CHR terminal analysis (CHR-PS): Turn on the CHR switch for the PS service.
Application subscription: Yes GSM Network Geograp hic Observa tion MR data and CHR data Basic subscription: Yes
Application subscription: Set the exception thresholds of KPIs. Basic subscription: l Network geographic observation data (MRCS): Turn on the BSC- or BTS-level MR measurement switch. l Network geographic observation data (CHRCS): Turn on the CHR switch for the CS service and enable MSs to report IMSIs. l Network geographic observation data (CHRPS): Turn on the CHR switch for the PS service.
Issue 01 (2013-07-15)
112
Theme
Required Data
Purpose
UMTS
Table 2-44 Data subscription for different themes (UMTS) Theme Required Data Whether Data Subscriptio n Is Required Basic subscription: Yes Application subscription: Yes MR data Basic subscription: Yes Application subscription: No MR data Basic subscription: Yes Application subscription: Yes MR data Basic subscription: Yes Application subscription: Yes Purpose
MR data
Basic subscription: Turn on the RNC-level MR measurement switch. Application subscription: Turn on the threshold switch. Basic subscription: Turn on the RNC-level MR measurement switch. Application subscription: Turn on the threshold switch. Basic subscription: Turn on the RNC-level MR measurement switch. Application subscription: Set frequency measurement parameters. Basic subscription: Turn on the RNC-level MR measurement switch. Application subscription: Set frequency measurement parameters.
UMTS IntraFrequen cy Neighbo ring Cell Analysis UMTS InterFrequen cy Neighbo ring Cell Analysis UMTS/ GSM Neighbo ring Cell Analysis
Issue 01 (2013-07-15)
113
Theme
Required Data
Whether Data Subscriptio n Is Required Basic subscription: Yes Application subscription: Yes
Purpose
MR data
Basic subscription: Turn on the RNC-level MR measurement switch. Application subscription: Set the exception thresholds of KPIs. Basic subscription: -
RTWP data
Application subscription: Set the exception thresholds of KPIs. Basic subscription: l UMTS complaint analysis support data (MR), optional: Turn on the MR switch. The information in the MR data can replace the original measurement report information in the CHR data, so that measurement report information more comprehensively and the voice quality analysis more accurately. l UMTS complaint analysis support data (CHR): Turn on the CHR switch and enable UEs to report IMSIs.
Application subscription: No UMTS VIP Analysis CHR data Basic subscription: Yes Application subscription: Yes UMTS Termina l Analysis MR data and CHR data Basic subscription: Yes
Application subscription: -
Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs. Application subscription: Set VIP objects and NE objects. Basic subscription: l UMTS terminal analysis data (MR): Turn on the RNC-level MR measurement switch. l UMTS terminal analysis data (CHR): Turn on the CHR switch and enable UEs to report IMSIs.
Issue 01 (2013-07-15)
114
Theme
Required Data
Purpose
Application subscription: Set the exception thresholds of KPIs. Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs. Application subscription: Set the exception thresholds of KPIs. Basic subscription: l Network geographic observation data (MR): Turn on the RNC-level MR measurement switch. l Network geographic observation data (CHR): Turn on the CHR switch and enable UEs to report IMSIs.
CHR data
LTE TDD
Table 2-45 Data subscription for different themes (LTE TDD) Theme Required Data Whether Data Subscriptio n Is Required Basic subscription: Yes Application subscription: Yes CHR data Basic subscription: Yes Purpose
MR data
Basic subscription: Turn on the MR measurement switch. Application subscription: Turn on the threshold switch. Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs.
Issue 01 (2013-07-15)
115
Theme
Required Data
Purpose
Application subscription: -
Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs. Application subscription: Set VIP objects and NE objects. Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs. Application subscription: Set the exception thresholds of KPIs. Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs. Application subscription: Set the exception thresholds of KPIs. Basic subscription: Turn on the CHR switch.
CHR data
LTE TDD Cell Perform ance Analysis LTE TDD Network Geograp hic Observa tion
CHR data
CHR data
Issue 01 (2013-07-15)
116
LTE FDD
Table 2-46 Data subscription for different themes (LTE FDD) Theme Required Data Whether Data Subscriptio n Is Required Basic subscription: Yes Application subscription: Yes CHR data Basic subscription: Yes Application subscription: No CHR data Basic subscription: Yes Application subscription: Yes CHR data Basic subscription: Yes Application subscription: Yes CHR data Basic subscription: Yes Application subscription: Yes CHR data Basic subscription: Yes Purpose
MR data
Basic subscription: Turn on the MR measurement switch. Application subscription: Turn on the threshold switch. Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs. Application subscription: -
Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs. Application subscription: Set VIP objects and NE objects. Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs. Application subscription: Set the exception thresholds of KPIs. Basic subscription: Turn on the CHR switch and enable UEs to report IMSIs. Application subscription: Set the exception thresholds of KPIs. Basic subscription: Turn on the CHR switch.
LTE FDD Cell Perform ance Analysis LTE FDD Network Geograp hic
Issue 01 (2013-07-15)
117
Theme
Required Data
Purpose
Observa tion
PS Core
Table 2-47 Data subscription for different themes (PS Core) Theme Required Data Whether Data Subscriptio n Is Required Basic subscription: Yes Application subscription: Yes CHR data Basic subscription: Yes Application subscription: Yes CHR data Basic subscription: Yes Application subscription: Yes PS Core Complai nt Analysis Support CHR data Basic subscription: Yes Application subscription: No Purpose
CHR data
Basic subscription: Set the SGSN/MME CHR reporting value. Application subscription: Deliver the preprocessing task. Basic subscription: Set the SGSN/MME CHR reporting value. Application subscription: Deliver the preprocessing task. Basic subscription: Set the SGSN/MME CHR reporting value. Application subscription: Set VIP objects and NE objects. Basic subscription: Set the SGSN/MME CHR reporting value. Application subscription: -
Issue 01 (2013-07-15)
118
Prerequisites
l l You have subscribed to analysis data. You are authorized to query analysis data.
Procedure
Step 1 Choose Maintenance > Data Maintenance Management. The Data Maintenance Management window is displayed. Step 2 In the navigation tree of Data Maintenance Management window, choose Data Type > Analysis sort > *** Data. For the analysis theme of the different type, you need to query the data of the different type. *** indicates the name of analysis theme to be analyzed. 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. For the analysis data on the RAN side, you can query the data of day-level. For the analysis data on the CN side, you can query the data of day-level and month-level. 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. 4.
Select specific nodes from the NE object navigation tree. Optional: Select the VIP group to be queried from the VIP group navigation tree. This step is only used for querying the *** VIP analysis data. *** refers to the network system.
Step 4 Click Query in the bottom left corner of the window. You can check and ensure that the configuration data is imported into the database. l The Overview tab page displays NEs with data and the data time range (start time and end time) of the NEs. The start time and the end time are the actual time when the data is generated, but not the time when 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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 119
On the tab page, green grids indicate that data is available, and white grids indicate that data is not available. If the analysis data is subscribed, and the result is normal, but no relevant data is displayed, contact Huawei technical support personnel. ----End
Follow-up Procedure
l l You can right-click in the right pane and then choose Save As from the shortcut menu to save the current query results as a .csv, .xls, or .xlsx file. View information about the subscription in the Log Info area. Table 2-48 lists the parameters. Table 2-48 Log parameters Parameter Date/Time Level Action Type Action Result OSS Name NE Name Switch Name Details Description Time when a task is complete. Level of the log, including Minor and Major. You are advised to focus on the Major level log information. Action type, including open and close. Action result. The value can be Succeed or Failure. The name of OSS which the subscribed NEs belong to. The name of the subscribed NEs. Switch type. Detailed information about the operation result.
Select Function, Severity, Condition, and type the keyword. Click Filter to filter the log information. It displays the latest 100 log information by default in the Log Info area. Click Show All, the Log Manager window is opened. You can view all of the log information generated within seven days. Click Show All, the Log Manager window is opened. Right-click the log list and choose Save As from the shortcut menu to save the log information.
Issue 01 (2013-07-15)
120
Prerequisites
l l The analysis data and configuration data have been imported to the Nastar database. For detailed operations, see 2.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 The network scale that the Nastar supports for one analysis task is limited. For details, see the specification-related section of each theme. When you create an analysis task beyond specifications, the task may fail due to uncontrollable risks of task execution time and required disk space. If unnecessary, you are not advised to create a task beyond specifications. 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 6.8.2 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
Step 1 In the Analysis Task Management window, click
TIP
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.
CAUTION
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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 121
Step 4 Set the task properties. The task properties vary from one function to another. For details about the parameters, see the sections for each theme, such as "Process of GSM MR Analysis." 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 Period is available for Execution Type in the window, the task supports only periodic analysis. l If both One-time and Period are available for Execution Type, the task supports one-time analysis and periodic analysis. For details about parameters, see Table 2-49. Table 2-49 Parameters for task execution time Execution Type One-time Parameter Description 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, and the end time should precede the locale system time. : Indicates the time range of the analysis of the selected task. For details about the time range of the analysis for each task, see the sections for different themes.
NOTE If the time exceeds the maximum value, creating the new task fails.
l Delayed: Indicates that if this parameter is not selected, the system executes the task immediately. If it is selected, the system will execute the task at the time of the Execution Delay. l Execution Delay: Indicates the specified execution time of the task. The parameter must not precede the end time of the Time Range. 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.
TIP Select the desired time range of the analysis on the tab page. The selected time range is associated with Time Range.
Issue 01 (2013-07-15)
122
Parameter Description 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: 09999. The value 0 indicates that the execution times are countless. l Part of the analysis tasks support only busy-hour analysis.
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.
TIP
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.
Only tasks in Waiting and Suspended states can be modified. Delete a Task Select one or more tasks and click , or right-click Delete.
Tasks in Running state cannot be deleted. Suspend a task Select a task in Waiting state and click Suspended. , or right-click
Issue 01 (2013-07-15)
123
Prerequisites
The progress bar of the analysis task reaches 100%.
Procedure
Step 1 Choose Theme Function > *** Analysis Task from the navigation tree on the left of the Analysis Task Management window. If you choose Theme Function, the task list on the right displays all the performance analysis tasks. Step 2 Select a task from the task list in the upper right pane. All the analysis results of the selected task are displayed in the lower right pane. Step 3 Select an analysis result from the result list on the lower right of the Analysis Task Management window. If a theme analysis task is executed more than 30 days, only result records of the latest 30 days are displayed in the analysis result list. For example, the start time of a created MR analysis task is September 1, 2012. If the task is executed more than 30 days (if the task execution period is 12 hours, the task is executed more than 60 times), the result record on September 1, 2012 will be deleted and the result records of 30 days from September 2, 2012 to October 1, 2012 are reserved when the task is executed on October 1, 2012. Step 4 Double click or right-click the analysis result, and then choose View Analysis Result. The analysis results window is displayed.
NOTE
Only the analysis result whose Result Status is Successful can be queried.
Step 5 Query the results in the displayed window. For details, see the *** Network Optimization chapter. *** refers to the network system such as GSM, UMTS, or LTE. ----End
Follow-up Procedure
You can right-click in the results and then choose Save As from the shortcut menu to save the current query results as a .csv, .xls, or .xlsx file.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 124
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, and 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, and 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 2.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. If you select multiple counters, the Nastar displays the analysis results of the last selected counter. For details about the Geographic Observation window, see 2.2.3 Interface Description: Geographic Observation Results. ----End
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.
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. l You can click on the right side of the progress bar to view detailed information about an export task in the finished state. ----End
2.11 FAQs
This chapter describes the problems and solutions to the FAQs when using the Nastar, and also provides methods for common operations.
2.11.1 What Do I Do When I Fail to Open the Excel File Exported from the Nastar?
When users open an Excel file exported from the Nastar, the system displays a file error message or certain contents in the file get lost.
Symptom
On the PC running Windows 7 and Office 2007, users export an Excel file in .xls format that contains information such as analysis results or engineering parameters from the Nastar.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 126
After the file is exported, the system displays a file error message or certain contents in the file get lost when users open the file. This problem does not exist on the PC running Windows XP and Office 2007.
Cause
The Nastar cannot properly export Excel files in .xls format on the PC running Windows 7 and Office 2007.
Solution
Users are advised to export Excel files in .xlsx format on the PC running Windows 7 and Office 2007.
2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key
This section describes how the change of the subscriber identity anonymization switch or the encryption key affects the execution of VIP and complaint analysis tasks. The identity information of a subscriber includes the subscriber's international mobile subscriber identity (IMSI), mobile station international ISDN number (MSISDN), and international mobile equipment identity (IMEI). This section also provides measures for you to mitigate the impact.
Prerequisites
You have the operation authority as user Administrator to change VIP subscriber identity information.
Scenario Description
Usually, the Nastar analyzes plaintext subscriber identity information, such as the IMSI, MSISDN, and IMEI. If a privacy and security policy for subscriber identity anonymization is implemented on the network that houses the Nastar system, all subscriber identity information, including the IMSI, MSISDN, and IMEI, is anonymized. In this case, the Nastar obtains and analyzes the anonymized subscriber identity information. If the privacy and security policy for subscriber identity anonymization on the network is changed, the performance of the VIP and complaint analysis functions provided by the Nastar is affected. Following describes the scenarios in which the privacy and security policy for subscriber identity anonymization is changed: l Scenario 1: A user implements the privacy and security policy for subscriber identity anonymization on the network that has no privacy and security policy for subscriber identity anonymization. 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. 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
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 127
Issue 01 (2013-07-15)
theNastar system is different from the encryption key stored on the network side, and the Nastar system cannot properly obtain or analyze information. For example, when the encryption key is changed, the subscriber IMSI stored in the Nastar system is different from the subscriber IMSI stored on the network side, and one VIP subscriber is mapped to multiple anonymized subscriber IMSIs. This produces inaccurate results for VIP and complaint analysis tasks. l The impacts of the preceding changes on the analysis service performance of the Nastar system are the same.
Troubleshooting Methods
Perform the following procedures based on how the change of the privacy and security policy for subscriber identity anonymization impacts the results of VIP and complaint analysis tasks. No. 1 Procedure Obtain new subscriber identity information, such as the IMSI, MSISDN, and IMEI Description l In scenario 1, contact the operator to obtain the anonymized subscriber identity information. l In scenario 2, contact the operator to obtain the subscriber identity information encrypted by using the new encryption key. l In scenario 3, contact the operator to obtain the plaintext subscriber identity information. 2 Change original VIP subscriber 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 2.4.6 Managing VIP Groups or VIP Users (VIP Analysis). This procedure is applicable only to VIP analysis. For detailed operations, see 2.5.3 Application Subscription of Analysis Data. For detailed operations, see the Follow-up Procedure in 2.7 Creating an Analysis Task. For detailed operations, see 2.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.
Re-subscribe to analysis data for performing VIP analysis Suspend or delete existing VIP and complaint analysis tasks Re-create VIP and complaint analysis tasks
4 5
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 M2000, or an NE abc is deleted from and then reconnected to the M2000 with the name of def. l The NE is deleted from and then reconnected to the M2000 For example, an NE abc is deleted from the M2000 and then reconnected to the M2000 with the same name (abc). l The NE is managed by another M2000 system For example, an NE is moved from M2000 A to M2000 B and managed by 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. 2. 3. 4. 5. 6. 7. Choose Maintenance > OSS Information Management. In the navigation tree in the OSS Information Management window, select the OSS node where the changed NE is located. On the RAN NE List tab page in the right pane, click Select NE. The Select NE dialog box is displayed. Select the changed NE in the NE List area and then add it to the List of Selected NEs area. 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. Select the NE name before change and click OK. Click OK.
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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 129
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.
Symptom
Users click a result record on the Nastar client, switch to another tool when they wait for the Nastar to display the result, and then switch back to the Nastar client. However, the Nastar client cannot be displayed again.
Cause
The Nastar client occupies too much memory or the computer that runs the Nastar client does not provide sufficient resources, and consequently users cannot switch from one window to another. In fact, this problem occurs during the running of many Windows applications.
Solution
Log off or close the Nastar client, and then log in to the Nastar client again.
2.11.6 What Do I Do if the System Displays Login 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 M2000 Failed. However, the 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 M2000 on the Nastar client.
Solution
1.
Issue 01 (2013-07-15)
For an ATAE cluster system, log in to the active eSAU node as user omcuser. 2. Run the following command to switch to user root. ~> su - root Password:Password of root 3. Run the following commands to set the communication mode: # cd /opt/esau # . ./svc_profile.sh # cd /opt/esau/script/utils/ # sh setTaoService.sh 4. 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
5.
Restart eSAU services. a. 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. b. Run the following command to restart eSAU services: # esau_start
2.11.7 Failed NE Version Upgrade Causes Failures in Subscribing To Basic Data for Some Themes
This section describes the solution to the problem that after the NE version is upgraded, the Nastar fails to obtain the basic data for some themes when it executes basic data subscription tasks.
Symptom
When the Nastar executes basic data subscription tasks, it fails to obtain the basic data for some themes, and logs show Execute MML Failed.
Cause
After the NE version is upgraded, new NE configuration data is not imported into the Nastar. MML commands that the Nastar issues for subscribing to basic data still contain old NE version information. Consequently the Nastar fails to obtain the basic data for some themes.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 131
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 M2000. l By default, the M2000 periodically exports NE configuration data. Generally, the period is one day. l If you need to export NE configuration data immediately, you can do it manually. For detailed operations, see Preparing for Obtaining Data (Common) in section Product Documentation > Installation and Commissioning > Nastar Commissioning Guide (HP) > Commissioning the Function of Obtaining Data > Preparing for Obtaining Data. 2. Collect NE configuration data on the Nastar client again. l By default, the Nastar automatically collects configuration data. The start time for collecting configuration data is the start time of the data collection service and the period is 1 hour by default. For example, if the start time of the data collection service is 7:00, the next execution time is 8: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. Execute failed basic data subscription tasks again. a. b. 5. Turn off the switch for the basic data that the Nastar fails to collect. 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. b. Turn off the switch for the application data that the Nastar fails to obtain. Turn on the switch for the application data that you want to subscribe to again.
2.11.8 Data Subscription Failures in Some Themes Due to the Reconstruction of Existing RNCs into RNC Pools
This section provides a solution to the problem that after existing RNCs are reconstructed into RNC pools, the Nastar fails to obtain basic and application data in some themes.
Symptom
When the Nastar executes basic and application data subscription tasks, it fails to obtain data in some themes, and logs show Execute MML Failed.
Issue 01 (2013-07-15)
132
Cause
After existing RNCs are reconstructed into RNC 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 M2000. l By default, the M2000 periodically exports NE configuration data. Generally, the period is one day. l If you need to export NE configuration data immediately, you can do it manually. For detailed operations, see Preparing for Obtaining Data (Common) in section Product Documentation > Installation and Commissioning > Nastar Commissioning Guide (HP) > Commissioning the Function of Obtaining Data > Preparing for Obtaining Data. 2. Collect NE configuration data on the Nastar client again. l By default, the Nastar automatically collects configuration data. The start time for collecting configuration data is the start time of the data collection service and the period is 1 hour by default. For example, if the start time of the data collection service is 7:00, the next execution time is 8: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. Optional: Import engineering parameters again for the network geographic observation theme. Execute failed basic data subscription tasks again. a. b. 6. a. b. Turn off the switch for the basic data that the Nastar fails to collect. Turn on the switch for the basic data that you want to subscribe to again. Turn off the switch for the application data that the Nastar fails to obtain. Turn on the switch for the application data that you want to subscribe to again.
Execute failed application data subscription tasks for the related themes.
Issue 01 (2013-07-15)
133
3
About This Chapter
This section describes how to perform GSM network optimization on the Nastar. Through this function, you can perform various theme analysis functions on the Nastar, such as MR analysis, frequency analysis, neighboring cell analysis, GSM/UMTS neighboring cell analysis, VIP analysis, complaint analysis support, terminal analysis, and network geographic observation. It is especially useful to users who are familiar with the Nastar basic operations. It is recommended that you read this section when using the Nastar for the GSM network optimization. If you use the Nastar in the first time, refer to Nastar Quick Start chapters. 3.1 GSM MR Analysis The GSM MR analysis function in the Nastar analyzes uplink/downlink level, uplink/downlink quality, timing advance (TA) distribution and link balance information of test cells. Through the function, the Nastar directly displays radio link information on wireless network problems for quickly locating problems. 3.2 GSM Frequency Analysis The Nastar provides the interference matrix analysis function and frequency interference matrix analysis function based on Measurement Reports (MRs) to assist users in adjusting the frequency setting. In addition, users can plan a frequency optimization scheme based on frequency interference matrix and judge the usability of the scheme based on frequency optimization results. You are advised to perform neighboring cell analysis before starting frequency analysis. This helps to improve the accuracy of neighboring cell identification and enable the Nastar to generate a correct interference model. 3.3 GSM Neighboring Cell Analysis On Nastar, you can identify redundant or missing neighboring GSM cells of a test cell and incorrect priority settings by summarizing and analyzing the MRs and events sent by MSs, configuration data, and engineering parameter data. This helps you resolve network quality problems due to redundant neighboring GSM cells, missing neighboring GSM cells, or incorrect priorities. 3.4 GSM/UMTS Neighboring Cell Analysis On Nastar, you can check whether any neighboring UMTS cell of a GSM cell is missing or redundant by summarizing and analyzing the MRs and events sent by MSs, configuration data, and engineering parameter data. This helps you resolve network quality problems due to redundant or missing neighboring UMTS cells.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 134
3.5 GSM Uplink Interference Analysis The Nastar analyzes uplink levels of cells and displays signal strength of measurement ARFCNs of certain cells in the analysis results. This provides reference for you to select appropriate ARFCNs. 3.6 GSM Terminal Analysis The GSM terminal analysis function enables the Nastar to analyze KPIs based on the CHR data of terminal users. This function helps operators identify the terminals with poor performance in the GSM network, therefore encouraging terminal manufacturers to improve the terminals with poor performance and guide subscribers to purchase terminals with good performance. In this case, subscribers can obtain stable services, and the subscriber satisfaction can be improved. 3.7 GSM Cell Performance Analysis The Nastar analyzes the call data of subscribers in abnormal cells to detect the root cause of abnormal calls. This helps provide better services and improve subscriber satisfaction.This function can be used to quickly locate and resolve problems. Normally there is no way to avoid that some user data such as International Mobile Subscriber Identity (IMSI) will be used during the troubleshooting. However, this function provides an anonymous data processing method. You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected. 3.8 GSM Network Geographic Observation The Nastar displays the relevant information on the map based on the data collected for the entire network to show the network coverage and distribution of traffic and abnormal events in an intuitive and comprehensive manner. 3.9 VIP Analysis By monitoring the indicators related to the quality of service of VIP subscribers, the Nastar helps you identify and solve the network problems that may cause VIP complaints so that the service quality of VIP subscribers is ensured and the satisfaction of VIP subscribers is improved.This function can be used to quickly locate and resolve problems. Normally there is no way to avoid that some user data such as International Mobile Subscriber Identity (IMSI) will be used during the troubleshooting. However, this function provides an anonymous data processing method. You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected. 3.10 Complaint Analysis Support After receiving a subscriber complaint, the Nastar can quickly searches for all call records of the complaint subscriber in a problem cell based on the known problem cell and International Mobile Subscriber Identity (IMSI) of the complaint subscriber, MSISDN number, or peer MSISDN of the complaint subscriber. Through the analysis of causes of exceptions such as access failure, handover failure, and abnormal call drop, the Nastar helps you locate and solve complaint problems.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.
Issue 01 (2013-07-15)
135
Function Description
MR overview analysis The MR overview analysis results provide the following information: an overview of the radio network performance, the distribution of TopN TRXs and problematic TRXs of each BSC or cell group, and the TopN TRXs for which the value of each radio link counter is the lowest. This function also offers analysis results and suggestions. Users can view the daily overview analysis report to learn information about the problematic TRXs of each BSC, each cell group, and the entire network, and check the causes of the problems. Users can also check whether other problematic TRXs exist in the cell where a TopN TRX is located and analyze these TRXs. The analysis results can be displayed in tables or bar charts to provide the radio link quality, level, traffic distance distribution, and link balance. Analysis of the problems and suggestions are provided to help you quickly analyze and locate the quality problems that occur on the wireless network. MR query During network performance analysis and optimization, when problematic cells (such as a cell whose call drop rate is high or number of handover failures is large) are found, you can query the information about these cells and radio link information about the TRXs in the cells through the Nastar. You can set cell objects before the query. The MR information about these cells is displayed in the result window. The Nastar allows further query of TRXs. The comparison and query of different TRXs in cells enable you to locate more complicated network problems effectively. The query results are displayed in tables or bar charts to provide the radio link quality and user distribution of each TRX.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 136
MR comparison analysis After network upgrade and optimization, you can compare the quality and coverage of the entire network, BSCs, or cells 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 M2000. Figure 3-1 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 3-1.
NOTE
Before you use the Nastar to collect and import performance data, check that the data export function has been enabled on the M2000.
Issue 01 (2013-07-15)
137
Table 3-1 Description of analysis User Operat ion 1. Subscri be to applicat ion data Proced ure Issue an applicat ion data subscrip tion comma nd Collect perform ance data Upload perform ance data 2. Check the integrit y of analysi s data Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results So urc e Nas tar Ser ver Dest inati on eSA U Purpose
To request the M2000 to filter 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.
eS AU
M20 00
To deliver a data-processing request to the M2000, requesting the M2000 to filter out the performance data that meets the Nastar's requirements. To upload the performance data that meets the Nastar's requirements to the eSAU.
M2 000
eSA U
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. To display analysis results on the Nastar client.
Issue 01 (2013-07-15)
138
The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of MML Commands Delivered by Subscription Function.
[0.2, 0.4) [0.4, 0.8) [0.8, 1.6) [1.6, 3.2) [3.2, 6.4) [6.4, 12.8) 12.8
Received Level
The received signal level is divided into seven classes according to level values. Each class corresponds to different ranges of received levels. Class 1 indicates the lowest received level and class 7 indicates the highest received level. Table 3-3 describes the relation between the received levels and the seven classes.
Issue 01 (2013-07-15)
139
Table 3-3 Relation between the received levels and the seven classes Class of Received Level 1 2 3 4 5 6 7 Received Level (dBm)
(-100, -95] (-95, -90] (-90, -85] (-85, -80] (-80, -75] (-75, -70] > -70
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.
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.
Issue 01 (2013-07-15)
141
Prerequisite Procedure
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 142
l l
Prerequisite
GSM configuration data has been imported into the Nastar Database. For details, see 3.1.2 Preparations for GSM MR Analysis.
Procedure
Figure 3-2 shows the analysis process. Figure 3-2 Analysis process
Issue 01 (2013-07-15)
143
Table 3-5 Description of GSM MR analysis procedures No. Procedur e Check the integrity of GSM MR analysis data Description Reference for Detailed Operations 2.6 Checking the Integrity of Analysis Data
(1)
Entry: Choose Maintenance > Data Maintenance Management. 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
(2)
Navigation path: Choose Maintenance > Data Subscription Management 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 01 (2013-07-15)
144
No.
Description
Reference for Detailed Operations 2.6 Checking the Integrity of Analysis Data
Entry: Choose Maintenance > Data Maintenance Management. 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 the analysis data does not exist, contact Huawei technical support.
(3)
Entry: Choose Theme Function > Basic Network Optimization > GSM MR Analysis from the navigation tree of the Analysis Task Management window. 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.
(4)
Entry: Choose an MR analysis task whose status is Finish 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. 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.
Issue 01 (2013-07-15)
145
No.
Description
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. For details about analysis results, see Interface Description: GSM MR Query.
Entry: 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. Procedure: 1. Right-click an analysis result of the task, and choose Comparison Analysis from the shortcut menu. 2. Choose a cell as the object. Click OK. 3. View GSM MR analysis results in the displayed GSM MR Comparison Analysis window. For details about analysis results, see Interface Description: GSM MR Comparison Analysis.
(5)
Entry: Click the icon on the toolbar in the upper left part of each MR analysis results window. 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.
Issue 01 (2013-07-15)
146
Parameter information Parameter Uplink Quality >= X MRs of (%) >= Y MRs >= Z Description 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 default value is 200.
Issue 01 (2013-07-15)
147
Description 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. Y is the threshold. It can be any integer from 1 to 100. The default value is 10. Z is the threshold. It can be any integer from 1 to 9999. The default value is 200.
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. Y is the threshold. It can be any integer from 1 to 100. The default value is 70. Z is the threshold. It can be any integer from 1 to 9999. The default value is 200.
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. Y is the threshold. It can be any integer from 1 to 100. The default value is 40. Z is the threshold. It can be any integer from 1 to 9999. The default value is 200.
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. Y is the threshold. It can be any integer from 1 to 100. The default value is 50. Z is the threshold. It can be any integer from 1 to 9999. The default value is 200.
Issue 01 (2013-07-15)
148
Parameter Downlink Level - Uplink Level <= X MRs of dB(%) >= Y and MRs >= Z
Description 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. Y is the threshold. It can be any integer from 1 to 100. The default value is 40. Z is the threshold. It can be any integer from 1 to 9999. The default value is 200.
Downlink Level - Uplink 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 default value is 15. Y is the threshold. It can be any integer from 1 to 100. The default value is 40. Z is the threshold. It can be any integer from 1 to 9999. The default value is 200.
Use a radio link counter to query the information about X problematic TRXs whose performance is the poorest on the entire network. Make sure that the number of all MRs is greater than or equal to Z. X is the number of TopN counters. It can be any integer from 1 to 99. The default value is 99. Z is the threshold. It can be any integer from 1 to 9999. The default value is 200.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 149
Time information of periodic task Param eter Start time Period Description Date for starting a task. 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 Delay by (hours) Whole day Time delayed for executing a task. Value range: 0 to 24. Unit: hour. If you select this parameter, it works the same as All Busy Time under Busy hours. You are not allowed 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. Note Start Time of a periodic task = Next time point + Delay by (hours) Time period of a periodic task: [Start Time of a periodic task - 1 x Period, Start Time of a periodic task The Next time point is related to Start time and Period. l If you set Period to Day, the Next time point is 00 hours:00 minutes:00 seconds of the next day starting from Start time. l If you set Period to Week, the Next time point is 00 hours:00 minutes:00 seconds of the eighth day starting from Start time.
NOTE 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 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 14:00:00, Start time is 01/01/2013, Period is Day, and Delay by (hours) is 3, the Nastar immediately executes the task.
Main Window
The GSM MR overview analysis results can be displayed in a combination of tables and bar charts. The query list of MR overview report, TRX list, counter bar chart, and task information list are contained, as shown in Figure 3-3. Figure 3-3 GSM MR overview analysis interface
N o. 1
Description 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.
Issue 01 (2013-07-15)
151
N o. 2
Description 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 NE 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. 3 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
Issue 01 (2013-07-15)
152
N o. 4
Description 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. 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 3.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. 6 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.
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. Select one or multiple cells to be viewed in the displayed window. Click OK and open the GSM MR Query Results window.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 153
Main Window
The GSM MR query results can be displayed in a combination of tables and bar charts. The cell list, TRX list, counter bar chart, and task information list are contained, as shown in Figure 3-4. Figure 3-4 GSM MR query result interface
No. 1
Description 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.
Display average values of radio link counters for all TRXs of a cell in Area 1 in tables. The system supports the function of highlighting MR results in colors. If a TRX is faulty, this TRX is highlighted in red. For details, see Parameters for Viewing MR Analysis Results of GSM Cells.
Issue 01 (2013-07-15)
154
No. 3
Description 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.
Display basic information of this task, and related information about the cell corresponding to the selected TRX in Area 2. For details, see Parameters for Viewing MR Analysis Results of GSM Cells.
The premise of displaying the comparison analysis result is that the finished GSM MR analysis task is a periodic task.
2. 3.
Select one or multiple cells to be viewed in the displayed window. Click OK to enter the GSM MR Comparison Analysis window. Perform operations as configured. If... Select NE Object for the current GSM MR analysis task is set to BSC Then... 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, Cell Group or Cell from the upper area in the navigation tree. 2. Select one or multiple objects from the navigation tree. 3. Click OK.
Issue 01 (2013-07-15)
155
Main Window
The GSM MR analysis results can be displayed in a combination of tables and bar charts. The counter information and counter charts are contained, as shown in Figure 3-5. Figure 3-5 GSM MR comparison report interface
No. 1
Description 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.
Issue 01 (2013-07-15)
156
No. 2
Description 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.
BSC Name
N/A
[0,7]
N/A
Issue 01 (2013-07-15)
157
Range [0,7]
Unit N/A
Description Indicates the number of TRXs with the average received signal quality values of the MSs exceeding the threshold. Indicates the number of TRXs with the average received levels of the BTSs exceeding the threshold. Indicates the number of TRXs with the average received levels of the MSs exceeding the threshold. Indicates the number of TRXs with the values of Average TA Distribution exceeding the threshold. Indicates the number of TRXs with the values of Link Balance exceeding the threshold.
[-110,-40]
dBm
[-110,-40]
dBm
[0,64)
N/A
[0,+)
N/A
Issue 01 (2013-07-15)
158
Parameter TRX Count for Uplink Quality >= X AND MR (%) >= Y%
Range [0,+)
Unit N/A
Description 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. NOTE: X and Y are the thresholds specified when you create an analysis task.
[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. 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.
TRX Count for Uplink Level Grade <= X dBm AND MR (%) >= Y%
[0,+)
N/A
Issue 01 (2013-07-15)
159
Parameter TRX Count for Downlink Level Grade <= X dBm AND MR (%) >= Y%
Range [0,+)
Unit N/A
Description 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. 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. 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. 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.
[0,+)
N/A
TRX Count for Link Balance <= X dBm AND MR(%) >= Y%
[0,+)
N/A
TRX Count for Link Balance >= X dBm AND MR(%) >= Y%
[0,+)
N/A
Issue 01 (2013-07-15)
160
BSC Name
N/A
[0,+)
Number
[0,7]
N/A
[0,7]
N/A
[-110,-40]
dBm
[-110,-40]
dBm
Average TA Distribution
[0,64)
N/A
Issue 01 (2013-07-15)
161
Range N/A
Unit dB
Description Indicates the dB value calculated through this expression: Average received level of the MS Average received level of the BTS Difference between the values of the average sensitivity of the MS and BTS.
BSC Name
N/A
Cell ID
[0,2047]
N/A
Cell Name
1 to 64 characters
N/A
TRX ID
[0,8191]
N/A
Issue 01 (2013-07-15)
162
Range [0,125]
Unit N/A
Description Number of a TRX in a BTS. The number of a TRX is unique in a BTS. Indicates the number of MRs transferred over the channel. Indicates the average quality of received signals of the BTSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average quality of received signals of the MSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average received levels of the BTSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC.
[0,+)
Number
[0,7]
N/A
[0,7]
N/A
[-110,-40]
dBm
Issue 01 (2013-07-15)
163
Range [-110,-40]
Unit dBm
Description Indicates the average received levels of the MSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS. 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.
Average TA Distribution
[0,64)
N/A
Link Balance
N/A
dB
Issue 01 (2013-07-15)
164
BSC Name
N/A
Cell ID
[0,2047]
N/A
Cell Name
1 to 64 characters
N/A
TRX ID
[0,8191]
N/A
TRX No.
[0,125]
N/A
Frequency Band
GSM900 GSM1800
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,7]
N/A
Issue 01 (2013-07-15)
165
Range [-110,-40]
Unit N/A
Description Indicates the average quality of received signals of the MSs corresponding to all TRXs. Indicates the average received levels of the BTSs corresponding to all TRXs. Indicates the average received levels of the MSs corresponding to all TRXs. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS. Indicates the dB value calculated through this expression: Average received level of the MS corresponding to each TRX Average received level of the BTS corresponding to each TRX Difference between the values of the average sensitivity of the MS and BTS.
[-110,-40]
dBm
[0,64)
dBm
Average TA Distribution
[0,64)
N/A
Link Balance
N/A
dB
Issue 01 (2013-07-15)
166
Start Time
N/A
N/A
End Time
N/A
N/A
Task Creator
N/A
N/A
BSC Name
N/A
Issue 01 (2013-07-15)
167
Parameter Cell ID
Range [0,2047]
Unit N/A
Description Indicates the number of the cell that the TRX belongs to. Indicates the name of the cell that the TRX belongs to. Index of a TRX, uniquely identifying a TRX in a BSC. Number of a TRX in a BTS. The number of a TRX is unique in a BTS. Indicates the number of MRs transferred over the channel. Indicates the average quality of received signals of the BTSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average quality of received signals of the MSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Cell Name
1 to 64 characters
N/A
TRX ID
[0,8191]
N/A
TRX No.
[0,125]
N/A
[0,+)
Number
[0,7]
N/A
[0,7]
N/A
Issue 01 (2013-07-15)
168
Range [-110,-40]
Unit dBm
Description Indicates the average received levels of the BTSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the average received levels of the MSs corresponding to the TopN TRXs or problematic TRXs controlled by the BSC. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS.
[-110,-40]
dBm
Average TA Distribution
[0,64)
N/A
Issue 01 (2013-07-15)
169
Range N/A
Unit dB
Description Indicates the dB value calculated through this expression: Average received level of the MS corresponding to the TopN TRX or problematic TRX controlled by the BSC Average received level of the BTS corresponding to the TopN TRX or problematic TRX controlled by the BSC Difference between the values of the average sensitivity of the MS and BTS.
BSC Name
N/A
Cell ID
[0,2047]
N/A
Issue 01 (2013-07-15)
170
Range 1 to 64 characters
Unit N/A
Description Indicates the name of the cell that the TRX belongs to. Index of a TRX, uniquely identifying a TRX in a BSC. Number of a TRX in a BTS. The number of a TRX is unique in a BTS. Indicates the frequency band assigned to BSC. Indicates the number of MRs transferred over the channel. Indicates the average quality of received signals of the BTSs corresponding to all TRXs. Indicates the average quality of received signals of the MSs corresponding to all TRXs. Indicates the average received levels of the MSs corresponding to all TRXs.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
TRX ID
[0,8191]
N/A
TRX No.
[0,125]
N/A
Frequency Band
GSM900 GSM1800
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,7]
N/A
[0,7]
N/A
[-110,-40]
dBm
Issue 01 (2013-07-15)
171
Range [0,64)
Unit N/A
Description Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS. Indicates the dB value calculated through this expression: Average received level of the MS corresponding to each TRX Average received level of the BTS corresponding to each TRX Difference between the values of the average sensitivity of the MS and BTS.
Link Balance
N/A
dB
Issue 01 (2013-07-15)
172
Start Time
N/A
N/A
End Time
N/A
N/A
Task Creator
N/A
N/A
1 to 128 characters
N/A
Issue 01 (2013-07-15)
173
Range [0,7]
Unit N/A
Description Indicates the number of TopN TRXs with the average quality values of the received signals of the BTSs exceeding the threshold. Indicates the number of TopN TRXs with the average quality values of the received signals of the MSs exceeding the threshold. Indicates the number of TopN TRXs with the average received levels of the BTSs exceeding the threshold. Indicates the number of TopN TRXs with the average received levels of the MSs exceeding the threshold. Indicates the number of TopN TRXs with the values of Average TA Distribution exceeding the threshold.
[0,7]
N/A
[-110,-40]
dBm
[-110,-40]
dBm
[0,64)
N/A
Issue 01 (2013-07-15)
174
Range [0,+)
Unit N/A
Description Indicates the number of TopN TRXs with the values of Link Balance exceeding the threshold. 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. NOTE: X and Y are the thresholds specified when you create an analysis task.
[0,+)
N/A
[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. 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.
TRX Count for Uplink Level Grade <= X dBm AND MR (%) >= Y%
[0,+)
N/A
Issue 01 (2013-07-15)
175
Parameter TRX Count for Downlink Level Grade <= X dBm AND MR (%) >= Y%
Range [0,+)
Unit N/A
Description 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. 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. 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. 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.
[0,+)
N/A
TRX Count for Link Balance <= X dBm AND MR(%) >= Y%
[0,+)
N/A
TRX Count for Link Balance >= X dBm AND MR(%) >= Y%
[0,+)
N/A
Issue 01 (2013-07-15)
176
1 to 128 characters
N/A
[0,+)
Number
[0,7]
N/A
[0,7]
N/A
[-110,-40]
dBm
[-110,-40]
dBm
Average TA Distribution
[0,64)
N/A
Issue 01 (2013-07-15)
177
Range N/A
Unit dB
Description Indicates the dB value calculated through this expression: Average received level of the MS Average received level of the BTS Difference between the values of the average sensitivity of the MS and BTS.
1 to 128 characters
N/A
Cell ID
[0,2047]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Cell Name
[1,64]
N/A
TRX ID
[0,8191]
N/A
Issue 01 (2013-07-15)
178
Range [0,125]
Unit N/A
Description Number of a TRX in a BTS. The number of a TRX is unique in a BTS. Indicates the number of MRs transferred over the channel. Indicates the average quality of received signals of the BTS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the average quality of received signals of the MS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the average received level value of the BTS corresponding to a TopN TRX or problematic TRX in the cell group.
[0,+)
Number
[0,7]
N/A
[0,7]
N/A
[-110,-40]
dBm
Issue 01 (2013-07-15)
179
Range [-110,-40]
Unit dBm
Description Indicates the average received level value of the MS corresponding to a TopN TRX or problematic TRX in the cell group. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS. Indicates the dB value, corresponding to a TopN TRX or problematic TRX in the cell group, calculated through this expression: Average received level of the MS corresponding to the TopN TRX or problematic TRX - Average received level of the BTS corresponding to the TopN TRX or problematic TRX Difference between the values of the average sensitivity of the MS and BTS.
Average TA Distribution
[0,64)
N/A
Link Balance
N/A
dB
Issue 01 (2013-07-15)
180
1 to 128 characters
N/A
Cell ID
[0,2047]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Cell Name
[1,64]
N/A
TRX ID
[0,8191]
N/A
TRX No.
[0,125]
N/A
Frequency Band
GSM900 GSM1800
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,7]
N/A
Issue 01 (2013-07-15)
181
Range [0,7]
Unit N/A
Description Indicates the average quality of received signals of the MSs corresponding to all TRXs. Indicates the average received levels of the BTSs corresponding to all TRXs. Indicates the average received levels of the MSs corresponding to all TRXs. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS. Indicates the dB value calculated through this expression: Average received level of the MS corresponding to each TRX Average received level of the BTS corresponding to each TRX Difference between the values of the average sensitivity of the MS and BTS.
[-110,-40]
dBm
[-110,-40]
dBm
Average TA Distribution
[0,64)
N/A
Link Balance
N/A
dB
Issue 01 (2013-07-15)
182
Start Time
N/A
N/A
End Time
N/A
N/A
Task Creator
N/A
N/A
Parameters Related to Querying Problematic TRXs Involved in Filter Condition Analysis (1)
Parameter BSC ID Range 1 to 64 characters 1 to 64 characters Unit N/A Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
BSC Name
N/A
Issue 01 (2013-07-15)
183
Parameter Cell ID
Range [0,2047]
Unit N/A
Description Indicates the number of the cell that the TRX belongs to. Indicates the name of the cell that the TRX belongs to. Index of a TRX, uniquely identifying a TRX in a BSC. Number of a TRX in a BTS. The number of a TRX is unique in a BTS. Indicates the number of MRs transferred over the channel. Indicates the average quality of received signals of the BTS corresponding to the problematic TRX. Indicates the average quality of received signals of the MS corresponding to the problematic TRX.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Cell Name
1 to 64 characters
N/A
TRX ID
[0,8191]
N/A
TRX No.
[0,125]
N/A
[0,+)
Number
[0,7]
N/A
[0,7]
N/A
Issue 01 (2013-07-15)
184
Range [-110,-40]
Unit dBm
Description Indicates the average received level of the BTS corresponding to the problematic TRX. Indicates the average received level of the MS corresponding to the problematic TRX. Indicates the weighted average TA that is used by the MS to advance its timings of transmissions to the BTS. Indicates the dB value calculated through this expression: Average received level of the MS corresponding to the problematic TRX - Average received level of the BTS corresponding to the problematic TRX Difference between the values of the average sensitivity of the MS and BTS.
[-110,-40]
dBm
Average TA Distribution
[0,64)
N/A
Link Balance
N/A
dB
Issue 01 (2013-07-15)
185
Parameters Related to Querying Problematic TRXs Involved in Filter Condition Analysis (2)
Parameter BSC ID Range 1 to 64 characters 1 to 64 characters Unit N/A Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the number of the cell that the TRX belongs to. Indicates the name of the cell that the TRX belongs to. Index of a TRX, uniquely identifying a TRX in a BSC. Number of a TRX in a BTS. The number of a TRX is unique in a BTS. Indicates the frequency band assigned to BSC. Indicates the number of MRs transferred over the channel. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
BSC Name
N/A
Cell ID
[0,2047]
N/A
Cell Name
1 to 64 characters
N/A
TRX ID
[0,8191]
N/A
TRX No.
[0,125]
N/A
Frequency Band
GSM900 GSM1800
N/A
[0,+)
Number
Issue 01 (2013-07-15)
186
Range [0,7]
Unit N/A
Description Indicates the average quality of received signals of the BTSs corresponding to all TRXs. Indicates the average quality of received signals of the MSs corresponding to all TRXs. Indicates the average received levels of the BTSs corresponding to all TRXs. Indicates the average received levels of the MSs corresponding to all TRXs. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS.
[0,7]
N/A
[-110,-40]
dBm
[-110,-40]
dBm
Average TA Distribution
[0,64)
N/A
Issue 01 (2013-07-15)
187
Range N/A
Unit dB
Description Indicates the dB value calculated through this expression: Average received level of the MS corresponding to each TRX Average received level of the BTS corresponding to each TRX Difference between the values of the average sensitivity of the MS and BTS.
Start Time
N/A
N/A
End Time
N/A
N/A
Issue 01 (2013-07-15)
188
Range N/A
Unit N/A
Description Indicates the creator's name of the queried performance analysis task.
Parameters Related to Querying TopN TRXs and Problematic TRXs in the MR Analysis Results (1)
Parameter BSC ID Range 1 to 64 characters 1 to 64 characters Unit N/A Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the number of the cell that the TRX belongs to. Indicates the name of the cell that the TRX belongs to. Indicates the number of MRs transferred over the channel. Indicates the average quality of received signals of the BTSs corresponding to all TRXs. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
BSC Name
N/A
Cell ID
[0,2047]
N/A
Cell Name
1 to 64 characters
N/A
[0,+)
Number
[0,7]
N/A
Issue 01 (2013-07-15)
189
Range [0,7]
Unit N/A
Description Indicates the average quality of received signals of the MSs corresponding to all TRXs. Indicates the average received levels of the BTSs corresponding to all TRXs. Indicates the average received levels of the MSs corresponding to all TRXs. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS. Indicates the dB value calculated through this expression: Average received level of the MS corresponding to each TRX Average received level of the BTS corresponding to each TRX Difference between the values of the average sensitivity of the MS and BTS.
[-110,-40]
dBm
[-110,-40]
dBm
Average TA Distribution
[0,64)
N/A
Link Balance
N/A
dB
Issue 01 (2013-07-15)
190
Parameters Related to Querying TopN TRXs and Problematic TRXs in the MR Analysis Results (2)
Parameter BSC ID Range 1 to 64 characters 1 to 64 characters Unit N/A Description Indicates the ID of a BSC. Indicates the name of a BSC, for example, BSC_1. Indicates the number of the cell that the TRX belongs to. Indicates the name of the cell that the TRX belongs to. Index of a TRX, uniquely identifying a TRX in a BSC. Number of a TRX in a BTS. The number of a TRX is unique in a BTS. Indicates the frequency band assigned to BSC. Indicates the number of MRs transferred over the channel. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
BSC Name
N/A
Cell ID
[0,2047]
N/A
Cell Name
1 to 64 characters
N/A
TRX ID
[0,8191]
N/A
TRX No.
[0,125]
N/A
Frequency Band
GSM900 GSM1800
N/A
[0,+)
Number
Issue 01 (2013-07-15)
191
Range [0,7]
Unit N/A
Description Indicates the average quality of received signals of the BTSs corresponding to all TRXs. Indicates the average quality of received signals of the MSs corresponding to all TRXs. Indicates the average received levels of the BTSs corresponding to all TRXs. Indicates the average received levels of the MSs corresponding to all TRXs. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS.
[0,7]
N/A
[-110,-40]
dBm
[-110,-40]
dBm
Average TA Distribution
[0,64)
N/A
Issue 01 (2013-07-15)
192
Range N/A
Unit dB
Description Indicates the dB value calculated through this expression: Average received level of the MS corresponding to each TRX Average received level of the BTS corresponding to each TRX Difference between the values of the average sensitivity of the MS and BTS.
Start Time
N/A
N/A
End Time
N/A
N/A
Issue 01 (2013-07-15)
193
Range N/A
Unit N/A
Description Indicates the creator's name of the queried performance analysis task.
Cell Name
1 to 64 characters
N/A
LAC
[1,65533], [65535]
N/A
CI
[0,65535]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
BCCH
[0,1023]
N/A
BCC
[0,7]
N/A
NCC
[0,7]
N/A
Cell Layer
[1,4]
N/A
Issue 01 (2013-07-15)
194
Range [1,3]
Unit N/A
Description Indicates the cell priority. Indicates whether half rate is supported. Indicates the type of the frequency hopping, such as the RF hopping and baseband frequency hopping. Indicates whether the GPRS service is supported. Indicates whether the EDGE service is supported. Indicates whether the intelligent underlayoverlay cell function is supported. Indicates the BTS type.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Yes, No
N/A
N/A
N/A
Supporting GPS
Yes, No
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Supporting EDGE
0,1
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
195
Parameter Description
Parameter Object Name Range 1 to 64 characters Unit N/A Description Names of the objects to which two MR results to be compared belong. Indicates the number of MRs in the previous period. Indicates the number of MRs in the next period. Indicates the differences of the number of MRs in the previous and next periods. Indicates the average quality of received signals of the BTSs corresponding to all the TRXs in the previous period. Indicates the average quality of received signals of the BTSs corresponding to all the TRXs in the next period. Supported NE Version BSC6900 V900R013C00 or later version
First Total Number of Measurement Reports Second Total Number of Measurement Reports Difference of Total Measurement Reports
[0,+)
Number
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
[0,7]
N/A
[0,7]
N/A
Issue 01 (2013-07-15)
196
Range [0,7]
Unit N/A
Description Indicates the differences of the average received signal quality values of the BTSs corresponding to all the TRXs in the previous and next periods. Indicates the average quality of received signals of the MSs corresponding to all the TRXs in the previous period. Indicates the average quality of received signals of the MSs corresponding to all the TRXs in the next period. Indicates the differences of the average received signal quality values of the MSs corresponding to all the TRXs in the previous and next periods.
[0,7]
N/A
[0,7]
N/A
[0,7]
N/A
Issue 01 (2013-07-15)
197
Range [-110,-40]
Unit dBm
Description Indicates the average received signal levels of the BTSs corresponding to all the TRXs in the previous period. Indicates the average received signal levels of the BTSs corresponding to all the TRXs in the next period. Indicates the differences of the average received signal levels of the BTSs corresponding to all the TRXs in the previous and next periods. Indicates the average received signal levels of the MSs corresponding to all the TRXs in the previous period. Indicates the average received signal levels of the MSs corresponding to all the TRXs in the next period.
[-110,-40]
dBm
[-110,-40]
dBm
[-110,-40]
dBm
[-110,-40]
dBm
Issue 01 (2013-07-15)
198
Range [-110,-40]
Unit dBm
Description Indicates the differences of the average received signal levels of the MSs corresponding to all the TRXs in the previous and next periods. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS in the previous period. Indicates the weighted average TA that the MS uses to advance its timings of transmissions to the BTS in the next period. Indicates the difference of the weighted average TAs that the MS uses to advance its timings of transmissions to the BTS in the previous and next periods.
[0,64)
N/A
[0,64)
N/A
[0,64)
N/A
Issue 01 (2013-07-15)
199
Range N/A
Unit dB
Description Indicates the dB value in the previous period, which is calculated through this expression: Average received level of the MS corresponding to each TRX Average received level of the BTS corresponding to each TRX Difference between the values of the average sensitivity of the MS and BTS. Indicates the dB value in the next period, which is calculated through this expression: Average received level of the MS corresponding to each TRX Average received level of the BTS corresponding to each TRX Difference between the values of the average sensitivity of the MS and BTS.
N/A
dB
Issue 01 (2013-07-15)
200
Range N/A
Unit dB
Description Indicates the difference between the value of First Link Balance and the value of Second Link Balance.
Function Description
Frequency analysis The Nastar provides the interference traffic of each neighboring cell of a test cell and provides the interference matrix of each cell in a report. The mechanism of GSM frequency analysis is as follows: The Nastar identifies the interference between a test cell and its co-channel or adjacent-channel cells, evaluates the frequency planning results, and analyzes the cells and ARFCNs with strong interference on the current network. 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
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 201
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. 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 M2000. Figure 3-6 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 3-6.
NOTE
Before you use the Nastar to collect and import performance data, check that the data export function has been enabled on the M2000.
Issue 01 (2013-07-15)
202
Table 3-6 Description of analysis User Operat ion 1. Subscri be to applicat ion data Proced ure Issue an applicat ion data subscrip tion comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
To request the 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.
Issue 01 (2013-07-15)
203
Proced ure Collect perform ance data and neighbo ring cell measure ment data Upload perform ance data and neighbo ring cell measure ment data
So urc e eS AU
Purpose
To deliver a data-processing request to the M2000, requesting the M2000 to filter out the performance data and neighboring cell measurement data that meets the Nastar's requirements.
M2 000
eSA U
To upload the performance data and neighboring cell measurement data that meets the Nastar's requirements to the eSAU.
Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. To display analysis results on the Nastar client.
Issue 01 (2013-07-15)
204
The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of MML Commands Delivered by Subscription Function.
Adjusting the antenna data, such as the azimuth, tilt, and height of an antenna 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. Statistical results are affected if you change the handover parameters and handover relationship during neighbor relationship data collection and optimization. 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.
Adjusting handover relationship and handover parameters Adjusting the BSC topology or other network topology
Issue 01 (2013-07-15)
205
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 that violate neighboring cell spacing rules are highlighted in orange with the legend
l The ARFCNs are highlighted by their class priorities in the following descending order: co-cell ARFCNs, co-site ARFCNs, and neighboring cell ARFCNs. If an ARFCN violates multiple spacing rules, this ARFCN is highlighted in the color based on its highest class priority. l Assume that the ARFCN spacing is set to N. l For and , the range of ARFCNs that violate spacing rules is [Current ARFCN - N + 1, Current ARFCN + N - 1]. l For , the range of ARFCNs that violate spacing rules is [Current ARFCN - N + 1, current ARFCN) and (Current ARFCN, Current ARFCN + N - 1]. l If N is 0, ARFCN spacing rules are not limited.
Table 3-8 Description of GSM ARFCN spacing rules Cla ss Cosite Sub class Betw een BCC H ARF CNs Description 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. Example 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. 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. Scenario: Three co-site cells are Cell A, Cell B, and Cell C. The TCH ARFCN spacing rules is set to 2. CellB_TCH=8, 21, and CellC_TCH=4, 13. Purpose: To set TCH ARFCNs for Cell A. Result: According to the ARFCN spacing rule, CellA_TCH must not be set to 3, 4, 5, 7, 8, 9, 12, 13, 14, 20, 21, or 22. If these ARFCNs are present in 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.
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.
Issue 01 (2013-07-15)
206
Cla ss
Sub class Betw een BCC H ARF CNs and TCH ARF CNs
Description 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. 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. 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. 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.
Example Scenario: Three co-site cells are Cell A, Cell B, and 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. Purpose: To set a BCCH ARFCN and TCH ARFCNs for Cell A. Result: According to the ARFCN spacing rule, 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. -
Cocell
Scenario: The selected cell is Cell A. The co-cell TCH ARFCN spacing rules is set to 2. CellA_TCH=27, 51, 61. Purpose: To set new TCH ARFCNs for Cell A. Result: According to the ARFCN spacing rule, CellA_TCH must not be set to 26, 28, 50, 52, 60, or 62. If these ARFCNs are present in the candidate TCH ARFCNs of Cell A, these ARFCNs are highlighted in red, indicating that these ARFCNs violate the co-cell TCH ARFCN spacing rule. These ARFCNs are not recommended.
Issue 01 (2013-07-15)
207
Cla ss
Sub class Betw een BCC H ARF CNs and TCH ARF CNs
Description 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. 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. 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.
Example 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. Purpose: To set a BCCH ARFCN and TCH ARFCNs for Cell A. Result: According to the ARFCN spacing rule, CellA_TCH must not be set to 14 or 16. CellA_BCCH must not be set to 26, 28, 50, 52, 60, or 62. If these ARFCNs are present in the 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. Result: According to the ARFCN spacing rule, CellA_BCCH must not be set to 15, 16, 17, 18, 19, 20, 26, 27, or 28. If these ARFCNs are present in the candidate BCCH ARFCNs of Cell A, these ARFCNs are highlighted in orange, indicating that these ARFCNs violate spacing rules for BCCH ARFCNs between the serving cell and its neighboring cells. These ARFCNs are not recommended.
Issue 01 (2013-07-15)
208
Cla ss
Description 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.
Example 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_TCH=16, 19, CellC_TCH=27, 45, and CellD_TCH=87, 102. Purpose: To set TCH ARFCNs for Cell A. Result: According to the ARFCN spacing rule, CellA_TCH must not be set to 15, 16, 17, 18, 19, 20, 26, 27, 28, 44, 45, 46, 86, 87, 88, 101, 102, or 103. If these ARFCNs are present in the candidate 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.
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.
Scenario: The serving cell is Cell A, and its defined neighboring cells are Cell B, Cell C, and Cell D. The 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. Purpose: To set a BCCH ARFCN and TCH ARFCNs for Cell A. Result: According to the ARFCN spacing rule, CellA_BCCH must not be set to 15, 16, 17, 18, 19, 20, 26, 27, 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.
Issue 01 (2013-07-15)
209
Item Execution type Number of analysis tasks to be created Network scale to be analyzed in a task Time range of analysis data
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.
Prerequisite
GSM configuration data and GSM engineering parameters have been imported into the Nastar Database. For details, see 3.2.2 Preparations for GSM Frequency Analysis.
Procedure
Figure 3-7 shows the analysis process.
Issue 01 (2013-07-15)
211
Issue 01 (2013-07-15)
212
Table 3-9 Description of GSM frequency analysis procedures N o. (1 ) Procedure Description Reference for Detailed Operations 2.6 Checking the Integrity of Analysis Data
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to GSM Frequency 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
213
N o. (2 )
Procedure
Description
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.
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the GSM tab. 2. Select one or multiple NEs in the navigation tree. 3. On the Neighboring Cell/Frequency Analysis tab page, click ON. 4. In the Neighboring Cell/Frequency Analysis Parameter Setting window, set the analysis period. Click Next. 5. Set the parameters for the neighboring cell measurement data task. 6. Click Finish. 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 Parameter Description for Subscribing to Analysis Data.
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 01 (2013-07-15)
214
N o.
Procedure
Description
Reference for Detailed Operations 2.6 Checking the Integrity of Analysis Data
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to GSM Frequency Analysis Data. 2. Set the query time segment. 3. Select the NE to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
(3 )
Navigation path: Choose Theme Function > Basic Network Optimization > GSM Frequency Analysis Task from the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click GSM Frequency Analysis Task. 2. Set the task name and task remarks. Click Next. 3. Select the NE to be analyzed on the Select NE Object tab. 4. Set frequency analysis parameters on the Parameters Setting tab. Click Next. For details, see Analysis Task Parameters. 5. Choose an analysis time range. After you set the time range, the Nastar obtains the analysis data generated within this time range. 6. Click Finish.
Issue 01 (2013-07-15)
215
N o. (4 )
Procedure
Description
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click an analysis result of the task. 2. View the GSM frequency analysis result in the displayed GSM Frequency Analysis Task window. For details about analysis results, see Interface Description: GSM Frequency Analysis.
Issue 01 (2013-07-15)
216
N o. (5 )
Procedure
Description
Navigation path: Choose a frequency analysis task whose status is Finish 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. Right-click an analysis result of the task, and choose Frequency Optimization from the shortcut menu. 2. Configure the parameters related to frequency optimization algorithm on the Algorithm Parameters tab. 1. In the ARFCN Spacing Rule Setting area, double-click each cell to set detailed ARFCN spacing rules. For details, see GSM ARFCN Spacing Rules. to the right of BCCH ARFCN 2. Click 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. 3. 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 01 (2013-07-15)
217
N o. (6 )
Procedure
Description
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. For the description of export icon, see Interface Description: GSM Frequency Analysis. 2. Set the export path and export format. 3. Click Save.
(7 )
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. For the description of export icon, see Interface Description: GSM Frequency Optimization. 2. Set the export path and export format. 3. Click Save.
Issue 01 (2013-07-15)
218
Description 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.
CAUTION 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.
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 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.
Issue 01 (2013-07-15)
219
Description Click Frequency Analysis. 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.
Counter Period
The 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.
Indicates the total duration which a measurement task is performed. The value is an integer from 1 to 1410. The duration time must be later than the time calculated by (Measurement period 15) ([Total number of test ARFCNs measurement step + 1]) + 15.
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.
Issue 01 (2013-07-15)
220
Description 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 The name is unique and case-sensitive and cannot be empty. l Task Name must be named in Chinese or English. Otherwise, the function of distributing analysis results by emails is unavailable.
Type of an analysis task to be created. Description of the task. Value range: The name contains a maximum of 200 characters.
Parameter information Parameter Number of undefined neighboring cells Co-channel interference C/I Description Displays the TopN undefined neighboring cells. N can be any integer from 20 to 50. The default value is 30. Indicates the threshold of co-channel interference. This parameter can be set to any integer from 6 to 15. The default value is 12. Unit: dB Adjacent-channel interference C/A Indicates the threshold of adjacent-channel interference. This parameter can be set to any integer from -12 to 0. The default value is -6. Unit: dB The Distance of CoBCCH& BSIC Check of Neighboring Cells (km) Typical site distance(km) Indicates the distance of the search for cells with the same BCCH ARFCN and BSIC as the test cell. This parameter can be set to any flowing point number from 0.0 to 20.0. The default value is 5.0. Unit: km Indicates the distance between typical base stations. The Nastar calculates a threshold according to the distance, and filters analysis results. The parameter can be set to any value from 0.1 to 35.0. The default value is 0.5. Unit: km
Issue 01 (2013-07-15)
221
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time. 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. 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. The value of this parameter must not precede the end time of Date.
Main Window
The GSM frequency analysis results can be displayed in tables. The overview information about test cells, information about interference matrix, and information about frequency interference matrix are contained, as shown in Figure 3-8 and Figure 3-9.
Issue 01 (2013-07-15)
222
Issue 01 (2013-07-15)
223
N o. 1
Description 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 Cellopt(txt) from File Type to export the .txt file of a specified template of the Cellopt software. The exported result can be imported into the Cellopt software for frequency re-planning on the entire network. If serving cell base station (BS) name (Column 4) and interference cell BS name (Column 7) are left empty in the exported document, this means that the Nastar cannot retrieve related information in engineering parameters and configuration data. You need to check the integrity of engineering parameters and configuration data. l : Exporting the check results of the interference matrix is to export the interference matrix check results summarized by BSC and cell for all BSCs and cells and the time check report result. : 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.
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. The Nastar automatically sorts cells by interference and picks out targeted cells, providing a basis of frequency analysis for test cells.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 224
Issue 01 (2013-07-15)
N o. 3
Name Neighbo ring CellTest Cell Interfere nce Matrix Details Test CellNeighbo ring Cell Interfere nce Matrix Details
Description 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. For details, see Parameters for Viewing GSM Frequency Analysis Results.
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 frequency optimization. For details, see Parameters for Viewing GSM Frequency Analysis Results.
Issue 01 (2013-07-15)
225
N o. 5
Description Displays the interference traffic between the test cell selected in the left list and its neighboring cells with BCCH configuration by frequencies. For details, see Parameters for Viewing GSM Frequency Analysis Results. 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. For details, see Parameters for Viewing GSM Frequency Analysis Results.
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\plugins\NastarPA\style\conf\FreqConf directory. The query conditions of each frequency analysis task are saved in a file.
Main Window
The GSM frequency optimization results can be displayed in a combination of tables and charts. The overview information about test cells, BCCH information, TCH information, bar chart of frequency interference, and algorithm parameters are included, as shown in Figure 3-10.
Issue 01 (2013-07-15)
226
Issue 01 (2013-07-15)
227
No. 1
Description 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. l : Delete configured BCCH or TCH ARFCNs. The function of this button is to deselect the check box in the Configured column for a configured ARFCN. : Submit an operation request. After users click or delete ARFCNs, click this button and perform the submit operation to make the settings take effect. : 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. : View interference comparison results before and after frequency optimization. The Nastar provides comparison results of three levels, including Overview Compare, BSC Compare, and Cell Compare. Right-click in the result list and choose Save As to save the current result.
Issue 01 (2013-07-15)
228
No.
Name
Description l : Provide the function of automatic frequency optimization. 1. Click the icon. In the displayed Optimize Parameters tab page, configure Phase Optimize Range, ARFCN Type, and Optimize Loop Count. 2. Click OK.Display the progress of automatic ARFCN selection in the upper right progress bar of the interface. You can click the selection. button to stop automatic ARFCN
Shows the information about all the test cells involved in the current task. 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 frequency optimization. The system allows you to resort the table by performing the following operations: After you click on a column, the system to display the table in reverse order. After you set the ascending or descending order for the ARFCN, Maximum Interference Traffic, Interfered Traffic, External Interference Traffic, and Interference Traffic to VIP Cells columns, the system displays the image based on the new rule in area 4. For details, see Parameters for Viewing GSM Frequency Optimization Results.
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.
Displays information about ARFCNs that violate the co-cell, co-site, or neighboring cell frequencies rules in different colors. For details of spacing rules of ARFCNs, see GSM ARFCN Spacing Rules.
229
Issue 01 (2013-07-15)
No. 6
Description Displays the algorithm parameters set when frequency optimization is queried. Rules for spacing between ARFCNs and VIP cell groups are contained in this area.
Test Cell
1 to 64 characters
N/A
Issue 01 (2013-07-15)
230
Parameter BCCH
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for a test cell. 1 to 124: belong to P-GSM 900; 0 to 124, 975 to 1023: belong to E-GSM900; 0 to 124, 955 to 1023: belong to R-GSM900; 512 to 885: belong to DCS1800; 512 to 810: belong to PCS1900; 259 to 293: belong to GSM450; 306 to 340: belong to GSM480; 128 to 251: belong to GSM850; Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, GSM850 is belong to GSM900 layer; DCS1800, PCS1900 is belong to GSM1800 layer.
Issue 01 (2013-07-15)
231
Parameter BSIC
Range [0,77]
Unit N/A
Description Indicates the base station identity code of a test cell. Consists of the following parts: NCC[0,7] BCC[0,7] BSIC=NCC*10 +BCC
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 Indicates the number of MRs received by the test cell from the neighboring cells that share the same BCCH ARFCN with the test cell. 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.
[0,+)
N/A
[0,+)
N/A
Issue 01 (2013-07-15)
232
Parameter Probable Overlapped Traffic Interfered on Co-BCCH Neighboring Cell Overlapped Traffic Interfered on AdjacentBCCH Neighboring Cell
Range [0,+)
Unit N/A
Description Indicates the number of MRs received by the neighboring cells that share the same BCCH ARFCN with the test cell. Indicates the number of MRs received by the neighboring cells that have neighboring ARFCNs of the BCCH ARFCN of the test cell. Indicates the total number of downlink MRs received by the test cell within the measurement period. Indicates the distance from the test cell to the nearest intrafrequency neighboring cell.
[0,+)
N/A
[0,+)
Number
[0,+)
km
Issue 01 (2013-07-15)
233
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for an interfering cell. 1 to 124: belong to P-GSM 900; 0 to 124, 975 to 1023: belong to E-GSM900; 0 to 124, 955 to 1023: belong to R-GSM900; 512 to 885: belong to DCS1800; 512 to 810: belong to PCS1900; 259 to 293: belong to GSM450; 306 to 340: belong to GSM480; 128 to 251: belong to GSM850; Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, GSM850 is belong to GSM900 layer; DCS1800, PCS1900 is belong to GSM1800 layer.
Issue 01 (2013-07-15)
234
Range [0,77]
Unit N/A
Description Indicates the base station identity code of an interfering cell. Consists of the following parts: NCC[0,7] BCC[0,7] BSIC=NCC*10 +BCC
N/A
Indicates the attributes of an interfering cell. Indicates the number of MRs received by the test cell from the intra-frequency neighboring cells and adjacentchannel neighboring cells.
Overlapping Traffic
N/A
Issue 01 (2013-07-15)
235
Parameter Percentage of Overlapped Traffic Interfered by Co-Channel Neighboring Cell on Test Cell (%)
Range [0,100%]
Unit N/A
Description 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%
Issue 01 (2013-07-15)
236
Parameter Percentage of Overlapped Traffic Interfered by Co-Channel Neighboring Cell on Test Cell (%)
Range [0,100%]
Unit N/A
Description 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% 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.
[0,+)
N/A
Issue 01 (2013-07-15)
237
Range [0,+)
Unit N/A
Description 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. Indicates the distance from the test cell to a neighboring cell.
Distance
[0,+)
km
Issue 01 (2013-07-15)
238
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for an interfered cell. 1 to 124: belong to P-GSM 900; 0 to 124, 975 to 1023: belong to E-GSM900; 0 to 124, 955 to 1023: belong to R-GSM900; 512 to 885: belong to DCS1800; 512 to 810: belong to PCS1900; 259 to 293: belong to GSM450; 306 to 340: belong to GSM480; 128 to 251: belong to GSM850; Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, GSM850 is belong to GSM900 layer; DCS1800, PCS1900 is belong to GSM1800 layer.
Issue 01 (2013-07-15)
239
Range [0,+)
Unit N/A
Description Indicates the number of MRs received by the intra-frequency neighboring cells and adjacentchannel neighboring cells from the test cell. 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%
Percentage of Overlapped Traffic Interfered by Test Cell on CoChannel Neighboring Cell (%)
[0,100%]
N/A
Issue 01 (2013-07-15)
240
Parameter Percentage of Overlapped Traffic Interfered by Test Cell on AdjacentChannel Neighboring Cell (%)
Range [0,100%]
Unit N/A
Description 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% 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.
[0,+)
N/A
Issue 01 (2013-07-15)
241
Range [0,+)
Unit N/A
Description 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. Indicates the distance from the test cell to an interfered cell.
Distance
[0,+)
km
Matrix of the interference from the measurement cell to its neighboring cells
Parameter Interfered Cell BSIC Range [0,77] Unit N/A Description Indicates the base station identity code of an interfered cell. Consists of the following parts: NCC[0,7] BCC[0,7] BSIC=NCC*10 +BCC 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. BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
242
Issue 01 (2013-07-15)
243
Range [0,+)
Unit N/A
Description 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. 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. 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.
[0,+)
N/A
[0,+)
km
Issue 01 (2013-07-15)
244
Issue 01 (2013-07-15)
245
Range [0,77]
Unit N/A
Description Indicates the base station identity code of an interfering cell. Consists of the following parts: NCC[0,7] BCC[0,7] BSIC=NCC*10 +BCC
[0 to 2047]
N/A
Indicates the number of an interfering cell. Indicates the name of a cell that causes interference to the test cell. Indicates the attributes of an interfering cell, such as Defined Neighboring Cell and Undefined Neighboring Cell.
1 to 64 characters
N/A
N/A
Issue 01 (2013-07-15)
246
Parameter Percentage of Overlapped Traffic Interfered by Co-Channel Neighboring Cell on Test Cell (%)
Range [0,100%]
Unit N/A
Description 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%
Issue 01 (2013-07-15)
247
Parameter Percentage of Overlapped Traffic Interfered by AdjacentChannel Neighboring Cell on Test Cell (%)
Range [0,100%]
Unit N/A
Description 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% 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.
[0,+)
N/A
Issue 01 (2013-07-15)
248
Range [0,+)
Unit N/A
Description 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. 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%
Percentage of Overlapped Traffic Interfered by Test Cell on CoChannel Neighboring Cell (%)
[0,100%]
N/A
Issue 01 (2013-07-15)
249
Parameter Percentage of Overlapped Traffic Interfered by Test Cell on AdjacentChannel Neighboring Cell (%)
Range [0,100%]
Unit N/A
Description 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% 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.
[0,+)
N/A
Issue 01 (2013-07-15)
250
Range [0,+)
Unit N/A
Description 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. Indicates the distance from the test cell to a neighboring cell.
Distance (km)
[0,+)
km
Cell Name
1 to 64 characters
N/A
Issue 01 (2013-07-15)
251
Parameter LAC
Unit N/A
Description Indicates the location area code of the selected test cell. Indicates the identification code of the selected test cell. Indicates traffic channels for the selected test cell. Indicates total number of MRs on the test cell.
CI
[0,65535]
N/A
TCH
N/A
N/A
[0,+)
Number
BCCH/TCH ARFCNs
Parameter Configured Range Yes, No Unit N/A Description Indicates whether the current ARFCN is configured as the BCCH ARFCN or a TCH ARCFN of the selected test cell. Indicates the configured and candidate BCCH ARFCNs and TCH ARFCNs of the test cell. Supported NE Version BSC6900 V900R013C00 or later version
ARFCN
N/A
N/A
Issue 01 (2013-07-15)
252
Range N/A
Unit N/A
Description Indicates the name of the cell that has the strongest interference over the test cell.
Issue 01 (2013-07-15)
253
Range Yes, No
Unit N/A
Description 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. The value can be Yes or No. Yes indicates that the cell with the strongest interference over the test cell is within the interference matrix, that is, the cell with the strongest interference is measured. In such a case, External Interference Traffic of this ARFCN is reliable. No indicates that the cell with the strongest interference over the test cell is not within the interference matrix, that is, the cell with the strongest interference is not measured. In such a case, External Interference
Issue 01 (2013-07-15)
254
Parameter
Range
Unit
Supported NE Version
[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. 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. Indicates the total interference traffic received from other cells when the BCCH/TCH of the test cell is configured as the current candidate ARFCN.
[0,+)
N/A
Interfered Traffic
[0,+)
N/A
Issue 01 (2013-07-15)
255
Range [0,+)
Unit N/A
Description 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. 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. 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.
[0,+)
N/A
[0,+)
N/A
Issue 01 (2013-07-15)
256
Range [0,+)
Unit N/A
Description 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.
Function Description
GSM neighboring cell analysis is based on the MRs of the ARFCNs in the BA2 list reported by MSs. The ARFCNs in the BA2 list include the BCCH ARFCNs of defined neighboring GSM cells and undefined neighboring GSM cells. Figure 3-11 shows the process of measuring the ARFCNs in the BA2 list.
Issue 01 (2013-07-15)
257
Run the data subscription function on Nastar, and send the BCCH ARFCNs of undefined neighboring GSM cells to an NE. The NE sends the ARFCN information through system messages to MSs in the serving cell. Before you perform the analysis, check whether the BCCHs of any defined or undefined neighboring GSM cells share one BCCH ARFCN and BSIC. If the BCCHs of two defined or undefined neighboring GSM cells share one BCCH ARFCN and BSIC, the stability of the network and the accuracy of GSM neighboring cell analysis will be affected. During calls, the MSs in the serving cell test the ARFCNs in the BA2 list, and send MRs to the BSC. The BSC collects statistics on the MRs by cell-neighboring cell pair, including the BCCHs and BSICs of defined and undefined neighboring GSM cells, how many times the absolute level of the serving cell exceeds the preset threshold, how many times the relative level of the serving cell exceeds the preset threshold, and quantity of MRs. Nastar analyzes neighboring GSM cells based on the statistical results provided by the BSC, and generates analysis results. Based on the analysis results, you can add missing neighboring GSM cells and delete redundant neighboring GSM cells. Then, set Nastar to generate the result files of GSM neighboring cell analysis, which serve as the suggestions on GSM network optimization. The results of GSM neighboring cell analysis can be exported as .csv, .xls, or .xlsx files. Nastar can display the results of GSM neighboring cell analysis and possible neighboring cell analysis on a map and highlights the serving cell, missing neighboring GSM cells, redundant neighboring GSM cells, and defined and undefined neighboring GSM cells in different colors. This helps you query neighboring relationships.
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
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 258
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 priorities of neighboring cells are re-calculated based on their overall priorities calculated based on the number of handovers between every two neighboring cells and the analysis of MR data. All defined neighboring cells are sorted by priority. 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 M2000. Figure 3-12 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 3-10.
NOTE
Before you use the Nastar to collect and import performance data, check that the data export function has been enabled on the M2000.
Issue 01 (2013-07-15)
259
Table 3-10 Description of analysis User Operat ion 1. Subscri be to applicat ion data Proced ure Issue an applicat ion data subscrip tion comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
To request the 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.
Issue 01 (2013-07-15)
260
Proced ure Collect perform ance data and neighbo ring cell measure ment data Upload perform ance data and neighbo ring cell measure ment data
So urc e eS AU
Purpose
To deliver a data-processing request to the M2000, requesting the M2000 to filter out the performance data and neighboring cell measurement data that meets the Nastar's requirements.
M2 000
eSA U
To upload the performance data and neighboring cell measurement data that meets the Nastar's requirements to the eSAU.
Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. To display analysis results on the Nastar client.
Issue 01 (2013-07-15)
261
The list of the MML command delivered by the Nastar subscription function is referred to Appendix: List of MML Commands Delivered by Subscription Function.
Network Requirements
During raw data collection, the network must be stable. Otherwise, the accuracy of GSM neighboring cell analysis will be affected. Table 3-11 lists the network changes and their respective impacts. Table 3-11 Network changes and their respective impacts Network Change Adding or deleting BTSs Impacts Affects network coverage and normal handovers between cells. As a result, the analysis results cannot accurately reflect the current state of network. The cell coverage and network interference may change.
Adjusting the antenna data, such as the azimuth, tilt, and height of an antenna 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. Statistical results are affected if you change the handover parameters and handover relationship during neighbor relationship data collection and optimization. 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.
Adjusting handover relationship and handover parameters Adjusting the BSC topology or other network topology
Issue 01 (2013-07-15)
262
Item Execution type Number of analysis tasks to be created Network scale to be analyzed in a task Time range of analysis 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. 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 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. Map file (optional) The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map. You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
Prerequisites Procedure
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 264
l l
Prerequisites
GSM configuration data and GSM engineering parameters have been imported into the Nastar database. For details, see 3.3.2 Preparations for GSM Neighboring Cell Analysis.
Procedure
Figure 3-13 shows the analysis process. Figure 3-13 Analysis process
Issue 01 (2013-07-15)
265
Table 3-12 Process of GSM neighboring cell analysis No. (1) Step Check GSM Neighbo ring Cell analysis data Description Navigation path: Choose Maintenance > Data Maintenance Management 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. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
266
No. (2)
Step Subscrib e to the GSM neighbor ing cell analysis data (applicat ion)
Description
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.
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the GSM tab. 2. Select one or multiple NEs in the navigation tree. 3. On the Neighboring Cell/Frequency Analysis tab page, click ON. 4. In the Neighboring Cell/Frequency Analysis Parameter Setting window, set the analysis period. Click Next. 5. Set the parameters for the neighboring cell measurement data task. 6. Click Finish. 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 Parameter Description for Subscribing to Analysis Data.
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.
Navigation path: Choose Maintenance > Data Maintenance Management 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. l If the analysis data does not exist, contact Huawei technical support.
Issue 01 (2013-07-15)
267
No. (3)
Description Navigation path: In the Analysis Task Management window, choose Theme Function > Basic Network Optimization > GSM Neighboring Cell Analysis Task from the navigation tree. Procedure: 1. Double-click GSM Neighboring Cell Analysis Task. 2. Set the task name and remarks. Click Next. 3. On the Select NE(s) tab page, Select one or multiple NEs. 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.
(4)
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. Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish 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.
Issue 01 (2013-07-15)
268
No. (5)
Description 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. Navigation path: In the Analysis Task Management window, select an inter-RAT neighboring cell analysis task whose state is Finish, and select the result of the task in the Task Result area. Procedure: 1. Double-click the result of the task. 2. In the GSM Possible Neighboring Cell Analysis dialog box, view the GSM possible neighboring cell analysis results. For details about the dialog box, see Interface Description: Possible GSM Neighboring Cell Analysis.
Details
(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. Navigation path: In the Analysis Task Management window, select an inter-RAT neighboring cell analysis task whose state is Finish, and select the result of the task in the Task Result area. Procedure: 1. Double-click the result of the task. 2. In the Co-BCCH and Co-BSIC Check Result dialog box, view the GSM possible neighboring cell analysis results. For details about the dialog box, see Interface Description: GSM Intra-Frequency Co-BSIC Cell Analysis.
Issue 01 (2013-07-15)
269
No. (7)
Description 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. Navigation path: In the Analysis Task Management window, select an inter-RAT neighboring cell analysis task whose state is Finish, and select the result of the task in the Task Result area. Procedure: 1. Double-click the result of the task. 2. In the Neighboring Cells Co-BCCH Analysis Result dialog box, view the GSM possible neighboring cell analysis results. For details about the dialog box, see Interface Description: GSM Intra-Frequency Neighboring Cell Analysis.
Details
(8)
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. 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.
Issue 01 (2013-07-15)
270
Description Indicates the interval between periodic tasks. This parameter involves the period unit and the interval. Interval: 1 to 65535. Repeat 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 65535.
Measure Task
Measure 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.
CAUTION 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 01 (2013-07-15)
271
Description 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 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.
Frequency Analysis
Click Frequency Analysis. 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.
Counter Period
The 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.
Issue 01 (2013-07-15)
272
Description Indicates the total duration which a measurement task is performed. The value is an integer from 1 to 1410. The duration time must be later than the time calculated by (Measurement period 15) ([Total number of test ARFCNs measurement step + 1]) + 15. 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.
Issue 01 (2013-07-15)
273
Description Indicates the lower threshold of the neighboring cell sequence. All the undefined neighboring cells whose sequence numbers are smaller than or equal to the value of this parameter are regarded as missing neighboring cells. This parameter can be set to any integer from 1 to 32. The default value is 10.
Indicates the limitation on the number of test ARFCNs of neighboring cells. This parameter can be set to any integer from 1 to 32. The default value is 20.
Constraint of Neighboring Cell Table Length Neighboring cell table length limit
Indicates the limitation on the number of neighboring cells. This parameter can be set to any integer from 1 to 64. The default value is 50. This parameter and BA2 table length limit are used to determine the redundant neighboring cells. If these two conditions are not met, the system searches for redundant neighboring cells constantly until the two conditions are met. Indicates that only the TopN undefined neighboring cells are displayed. N can be any integer from 20 to 50. The default value is 30.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time. 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. 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. The value of this parameter must not precede the end time of Date.
Issue 01 (2013-07-15)
274
Main Window
In the main window, the GSM neighboring cell analysis results are displayed in charts and lists, such as the list of test cells, list of neighboring GSM cells, bar chart, and line chart, as shown in Figure 3-14. Figure 3-14 Interface for GSM neighboring cell analysis
Issue 01 (2013-07-15)
275
No . 1
Description 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. 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 the table in the descending order. 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.
Lists all undefined neighboring GSM cells of all test cells in the list of test cells. The operations in this area are the same as those in area 2.
Shows the information about all neighboring GSM cells of all test cells in a bar+line chart. l The neighboring GSM cells of a selected test cell can be arranged in sequence by their overall priorities. The percentages of the top 32 neighboring GSM cells are displayed in a bar chart. l You can select a parameter from the drop-down list on the upper right to display the statistical results of the parameter for the top 32 neighboring GSM cells in a line chart. l The rules on displaying cell names on the X-axis are as follows: Generally, only cell names are displayed on the X-axis. If the names of two or more cells are the same, the BCCHs and BSICs of the cells are displayed along with the cell names on the X-axis. If a cell cannot be located, the BCCH and BSIC of the cell is displayed on the X-axis.
Issue 01 (2013-07-15)
276
No . 5
Description 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. 3. In the Confirm message box, set whether to add or delete bidirectional neighboring GSM cells. 1. If you click Yes, the modifications you make in the analysis results (the check box of User Modify is selected) will also be exported in the result files. A Is Bidirectional Neighboring Cell column will be added to the list of result files. The value of a bidirectional neighboring GSM cell in this column will be Y, and bidirectional neighboring GSM cells will be added to the end of the list. For example, cell B is a redundant neighboring cell of cell A. If the check box of User Modify is selected for cell B, cell A and cell B are redundant neighboring cells for each other, and the redundant neighboring relationship needs to be deleted. In this case, the redundant neighboring relationship will be displayed at the end of the list of result files.
Issue 01 (2013-07-15)
277
No .
Area
Description 2. If you click No, the modifications you make in the analysis results of neighboring GSM cells will be ignored and not exported in the result files. 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.
Map Interface
on the upper left of the Nastar client, the map interface (Geographic After you click Observation) is displayed. The Figure 3-15 shows this interface. Figure 3-15 Map interface for GSM GSM neighboring cell analysis results
No. 1
Description Displays all the buttons for performing basic operations on the map interface. For the meanings of these buttons, see 2.2.3 Interface Description: Geographic Observation Results.
Issue 01 (2013-07-15)
278
No. 2
Description 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.
TIP 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. 4 Legend area This area is not displayed by default. It is displayed only after you click 5 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.
Main Window
In the main window, the analysis results of possible neighboring GSM cells are displayed in charts and lists, including the summary of possible neighboring cell analysis results and the confirmation list of possible neighboring GSM cells, as shown in Figure 3-16.
Issue 01 (2013-07-15)
279
No . 1
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. Lists the summary of the possible neighboring GSM cells of all cells involved in the analysis task. 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. You can also press Ctrl+F to search in the area.
Issue 01 (2013-07-15)
280
No . 3
Description Lists all the possible neighboring GSM cells of selected cells in area 2. 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 neighboring GSM cells. l List of possible neighboring GSM cells: In the list of possible neighboring GSM cells, select the Whether to Use check box of a possible neighboring GSM cell. The possible neighboring GSM cell is set as the best possible neighboring GSM cell of the serving cell in the left area. The information about the corresponding parameters (such as Neighboring Cell CGI, Neighboring BSC, and Neighboring Cell Name) in the summary of possible neighboring GSM cell analysis results is replaced with the information about this possible neighboring GSM cell. If the check box of Whether to Use is cleared, the information about the preceding parameters will not be displayed in the left area. For details about the parameters, see Parameters for Viewing GSM Possible Neighboring Cell Analysis Results.
Main Window
Nastar shows the list of intra-frequency co-BSIC GSM cells in the main window, as shown in Figure 3-17.
Issue 01 (2013-07-15)
281
Figure 3-17 lists the analysis results of the intra-frequency co-BSIC GSM cells of all cells involved in the analysis task. You can press Ctrl+F to search in the area. The Nastar provides the functions of filtering and sorting. Click the column header and choose column 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.
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.
Main Window
The system shows the list of analysis results of intra-frequency neighboring GSM cells in the main window, as shown in Figure 3-18.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 282
Figure 3-18 lists the analysis results of the intra-frequency neighboring GSM cells of all cells involved in the analysis task. You can press Ctrl+F to search in the area. The Nastar provides the functions of filtering and sorting. Click the column header and choose column
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.
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.
Issue 01 (2013-07-15)
283
1 to 64 characters
N/A
[0,+)
Number
[0.00,100.00]
[0,+)
Number
Issue 01 (2013-07-15)
284
Range [0,+)
Unit %
Description Indicates the sum of the integrated priority percentages of all missing neighboring cells for the selected test cell. Indicates the location area code of the selected test cell. LAC is a part of CGI and uniquely identifies a GSM cell.
LAC
[1,65533], [65535]
N/A
CI
[0,65535]
N/A
Issue 01 (2013-07-15)
285
Parameter BCCH
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for the selected test cell. 1 to 124: belong to P-GSM 900. 0 to 124, 975 to 1023: belong to E-GSM 900. 0 to 124, 955 to 1023: belong to R-GSM 900. 512 to 885: belong to DCS 1800. 512 to 810: belong to PCS 1900. 259 to 293: belong to GSM 450. 306 to 340: belong to GSM 480. 128 to 251: belong to GSM 850. Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, and GSM850 is belong to GSM900. DCS1800 and PCS1900 is belong to GSM1800.
Issue 01 (2013-07-15)
286
Parameter BSIC
Range [0,77]
Unit N/A
Description Indicates the base station identity code of the selected test cell. BSIC=NCC*10 +BCC, NCC [0,7], BCC [0,7].
Test Cell ID
[0 to 2047]
N/A
Indicates the ID of the selected test cell. Indicates the object ID of the BSC serving the current test cell.
BSC Object ID
Integer
N/A
CGI
MCC-MNCLAC-CI
N/A
Issue 01 (2013-07-15)
287
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for a neighboring cell. 1 to 124: belong to P-GSM 900. 0 to 124, 975 to 1023: belong to E-GSM 900. 0 to 124, 955 to 1023: belong to R-GSM 900. 512 to 885: belong to DCS 1800. 512 to 810: belong to PCS 1900. 259 to 293: belong to GSM 450. 306 to 340: belong to GSM 480. 128 to 251: belong to GSM 850. Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, and GSM850 is belong to GSM900. DCS1800 and PCS1900 is belong to GSM1800.
Issue 01 (2013-07-15)
288
Range [0,77]
Unit N/A
Description Indicates the base station identity code of the selected test cell. BSIC=NCC*10 +BCC, NCC [0,7], BCC [0,7].
N/A
N/A
Indicates the service type provided by a GSM neighboring cell, including indoor site and outdoor site. Learning about the service type provided by a GSM neighboring cell helps prevent important neighboring cells from being deleted. Indicates the operation suggestions on a neighboring cell.
Suggested Operation
N/A
User Modify
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.
Issue 01 (2013-07-15)
289
Range [0,+)
Unit Number
Description Indicates the number of handover requests from the current serving cell to another cell. Indicates the number of handover failures among all handover requests from the current serving cell to another cell. Indicates the handover success rate from the current serving cell to another cell. Outgoing cell handover success rate = Number of successful outgoing cell handovers/ Number of outgoing cell handover requests x 100%
[0,+)
Number
[0.00,100.00]
Issue 01 (2013-07-15)
290
Range [0.00,100.00]
Unit %
Description 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. 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 01 (2013-07-15)
291
Range [0.00,100.00]
Unit %
Description 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. 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%
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. Indicates the distance from the selected test cell to a neighboring cell.
Distance
[0,+)
km
Issue 01 (2013-07-15)
292
Parameter In BA Time
Range [1,+)
Unit minute
Description Indicates the duration for measuring a neighboring cell. 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. Indicates the total number of MRs of a neighboring cell. Indicates the average signal strength of the selected test cell that serves as the source handover cell. Indicates the average signal strength of a neighboring cell.
[0,+)
Number
[0,+)
Number
N/A
dBm
N/A
dBm
Issue 01 (2013-07-15)
293
Range N/A
Unit dB
Description 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. Indicates the number of MRs related to the information that the value of Mean S-N Difference is greater than the relative level threshold. Indicates the number of MRs containing information that the signal strength of a neighboring cell is greater than the absolute level threshold.
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
294
Parameter CGI
Range MCC-MNCLAC-CI
Unit N/A
Description Indicates the global ID of a neighboring cell. MCC [000,999] MNC [00,99] LAC [0,65535] CI [0,65535]
Issue 01 (2013-07-15)
295
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for a neighboring cell. 1 to 124: belong to P-GSM 900. 0 to 124, 975 to 1023: belong to E-GSM 900. 0 to 124, 955 to 1023: belong to R-GSM 900. 512 to 885: belong to DCS 1800. 512 to 810: belong to PCS 1900. 259 to 293: belong to GSM 450. 306 to 340: belong to GSM 480. 128 to 251: belong to GSM 850. Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, and GSM850 is belong to GSM900. DCS1800 and PCS1900 is belong to GSM1800.
Issue 01 (2013-07-15)
296
Range [0,77]
Unit N/A
Description Indicates the base station identity code of the selected test cell. BSIC=NCC*10 +BCC, NCC [0,7], BCC [0,7].
N/A
N/A
Indicates the service type provided by a GSM neighboring cell, including indoor site and outdoor site. Learning about the service type provided by a GSM neighboring cell helps prevent important neighboring cells from being deleted. Indicates the operation suggestions on a neighboring cell.
Suggested Operation
N/A
User Modify
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.
Issue 01 (2013-07-15)
297
Range [0.00,100.00]
Unit %
Description 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. Indicates the sequence number of a neighboring cell among all neighboring cells for the selected test cell according to its integrated priority. Indicates the distance from the selected test cell to a neighboring cell. Indicates the duration for measuring a neighboring cell. Indicates the number of MRs related to a neighboring cell.
Priority
[0,+)
N/A
Distance
[0,+)
km
In BA Time
[0,+)
minute
[0,+)
Number
Issue 01 (2013-07-15)
298
Range [0,+)
Unit Number
Description 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. Indicates the average signal strength of the selected test cell. Indicates the average signal strength of a neighboring cell. Indicates the average difference between the signal strength of the selected test cell and the signal strength of a neighboring cell. 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.
N/A
dBm
N/A
dBm
N/A
dB
[0,+)
Number
Issue 01 (2013-07-15)
299
Range [0,+)
Unit Number
Description Indicates the number of MRs containing the signal strength of neighboring cells greater than the absolute level threshold.
1 to 64 characters
N/A
[0,77]
N/A
Issue 01 (2013-07-15)
300
Range MCC-MNCLAC-CI
Unit N/A
Description Indicates the global ID of a test cell, for example, 286-01-33034-5 0712. MCC[000,999] MNC[00,99] LAC[0,65535] CI[0,65535]
Issue 01 (2013-07-15)
301
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for a test neighboring cell. 1 to 124: belong to P-GSM 900. 0 to 124, 975 to 1023: belong to E-GSM 900. 0 to 124, 955 to 1023: belong to R-GSM 900. 512 to 885: belong to DCS1800 512 to 810: belong to PCS1900. 259 to 293: belong to GSM450. 306 to 340: belong to GSM480. 128 to 251: belong to GSM850. Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, and GSM850 is belong to GSM900. DCS1800 and PCS1900 is belong to GSM1800.
Issue 01 (2013-07-15)
302
Range [0,77]
Unit N/A
Description Indicates the base station identity code of a test neighboring cell. BSIC=NCC*10 +BCC, NCC [0,7], BCC [0,7].
MCC-MNCLAC-CI
N/A
Indicates the global ID of the selected possible neighboring cell. MCC[000,999] MNC[00,99] LAC[0,65535] CI[0,65535]
1 to 64 characters
N/A
Indicates the name of the BSC that the selected possible neighboring cell belongs to. Indicates the name of the selected possible neighboring cell. Indicates the distance from the test cell to the selected possible neighboring cell.
1 to 64 characters
N/A
Distance
[0,+)
km
Issue 01 (2013-07-15)
303
Range 0,1,2,3,99
Unit N/A
Description Indicates the number of laps between the selected possible neighboring cell and the test cell, that is, the number of cells between the selected possible neighboring cell and the test cell. Indicates the relative angle between the selected possible neighboring cell and the test cell. Indicates the signal strength of the selected possible neighboring cell based on the dimensioning. Indicates whether the selected possible neighboring cell is obtained from the configuration data. Indicates the number of possible neighboring cells.
[0,360]
Degree
N/A
dBm
Yes, No
N/A
[0,+)
Number
Issue 01 (2013-07-15)
304
Range [0%,100%]
Unit Number
Description Indicates the percentage of integrated priority. Indicates the sequence number of a possible neighboring cell among all possible neighboring cells for the selected test cell according to its integrated priority.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
N/A
Issue 01 (2013-07-15)
305
Parameter
Range
Unit
Description Cell replaces Neighboring Cell Name. Distance of Possible Neighboring Cell(km) replaces Neighboring Distance(km). Number of Possible Neighboring Cell Laps replaces Neighboring Cell Loop Number. Relative Angle of Neighboring Cell() replaces Angle form Neighboring Cell Direction. Predicted Signal Strength of Neighboring Cell(dBm) replaces Predicted DL Signal Strength. Obtain From Configuration Data replaces Get from config data. If this parameter is not selected, it indicates that the most possible neighboring cell is not determined. In addition, the system clears all the information in the following
Supported NE Version
Issue 01 (2013-07-15)
307
Parameter
Range
Unit
Description 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
Supported NE Version
MCC-MNCLAC-CI
N/A
Indicates the global ID of a possible neighboring cell. MCC[000,999] MNC[00,99] LAC[0,65535] CI[0,65535]
1 to 64 characters
N/A
Indicates the name of the BSC that a possible neighboring cell belongs to. Indicates the name of a possible neighboring cell.
1 to 64 characters
N/A
Issue 01 (2013-07-15)
308
Range [0,+)
Unit km
Description Indicates the distance from the test cell to a possible neighboring cell. Indicates the number of laps between the test cell and a possible neighboring cell, that is, the number of cells between the test cell and a possible neighboring cell. Indicates the relative angle between the test cell and a possible neighboring cell. Indicates the signal strength of a possible neighboring cell based on the dimensioning.
0,1,2,3,99
N/A
[0,360]
Degree
N/A
dBm
Issue 01 (2013-07-15)
309
Range Yes, No
Unit N/A
Description Indicates whether possible neighboring cells are obtained from the configuration data. 0 indicates that possible neighboring cells are obtained from the configuration data. 1 indicates that possible neighboring cells are not obtained from the configuration data.
Parameters for Viewing GSM Co-BCCH and Co-BSIC Neighboring Cell Analysis Results
This section describes the parameters for querying GSM Co-BCCH and Co-BSIC Neighboring Cell Analysis results, You can refer to the description when querying GSM Co-BCCH and CoBSIC Neighboring Cell Analysis results.
Parameter
Parameter BSC Where Test Cell Is Located Range 1 to 64 characters Unit N/A Description Indicates the name of the BSC that a test cell belongs to, for example, BSC_1. Indicates the name of a test cell, for example, Cell_1. Supported NE Version BSC6900 V900R013C00 or later version
1 to 64 characters
N/A
Issue 01 (2013-07-15)
310
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for a test cell. 1 to 124: belong to P-GSM 900. 0 to 124, 975 to 1023: belong to E-GSM 900. 0 to 124, 955 to 1023: belong to R-GSM 900. 512 to 885: belong to DCS1800 512 to 810: belong to PCS1900. 259 to 293: belong to GSM450. 306 to 340: belong to GSM480. 128 to 251: belong to GSM850. Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, and GSM850 is belong to GSM900. DCS1800 and PCS1900 is belong to GSM1800.
Issue 01 (2013-07-15)
311
Range [0,77]
Unit N/A
Description Indicates the base station identity code of a test cell. BSIC=NCC*10 +BCC, NCC [0,7], BCC [0,7].
1 to 64 characters
N/A
Indicates the name of a neighboring cell for the selected test cell. 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]
MCC-MNCLAC-CI
N/A
[0,360]
Degree
Indicates the antenna azimuth of the selected test cell. Indicates the distance between the test cell and a neighboring cell. Indicates the number of handover requests from the current serving cell to another cell.
[0,+)
km
[0,+)
Number
Issue 01 (2013-07-15)
312
Parameter
Parameter BSC Where Test Cell Is Located Range 1 to 64 characters Unit N/A Description Indicates the name of the BSC that a test cell belongs to, for example, BSC_1. Indicates the name of a test cell, for example, Cell_1. Supported NE Version BSC6900 V900R013C00 or later version
1 to 64 characters
N/A
Issue 01 (2013-07-15)
313
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for a test cell. 1 to 124: belong to P-GSM 900. 0 to 124, 975 to 1023: belong to E-GSM 900. 0 to 124, 955 to 1023: belong to R-GSM 900. 512 to 885: belong to DCS1800 512 to 810: belong to PCS1900. 259 to 293: belong to GSM450. 306 to 340: belong to GSM480. 128 to 251: belong to GSM850. Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, and GSM850 is belong to GSM900. DCS1800 and PCS1900 is belong to GSM1800.
Issue 01 (2013-07-15)
314
Range [0,77]
Unit N/A
Description Indicates the base station identity code of a test cell. BSIC=NCC*10 +BCC, NCC [0,7], BCC [0,7].
1 to 64 characters
N/A
Indicates the name of a neighboring cell for the selected test cell. Indicates the name of the BSC that a neighboring cell for the selected test cell belongs to. 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]
1 to 64 characters
N/A
MCC-MNCLAC-CI
N/A
Issue 01 (2013-07-15)
315
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel for a neighboring cell for the selected test cell. 1 to 124: belong to P-GSM 900. 0 to 124, 975 to 1023: belong to E-GSM 900. 0 to 124, 955 to 1023: belong to R-GSM 900. 512 to 885: belong to DCS1800 512 to 810: belong to PCS1900. 259 to 293: belong to GSM450. 306 to 340: belong to GSM480. 128 to 251: belong to GSM850. Regulation: PGSM, E-GSM, R-GSM, GSM450, GSM480, and GSM850 is belong to GSM900. DCS1800 and PCS1900 is belong to GSM1800.
Issue 01 (2013-07-15)
316
Range [0,77]
Unit N/A
Description Indicates the base station identity code of a neighboring cell for the selected test cell. BSIC=NCC*10 +BCC, NCC [0,7], BCC [0,7].
Distance
[0,+)
km
Indicates the distance from the selected test cell to a neighboring cell. Indicates the number of handover requests from the current serving cell to another cell.
[0,+)
Number
Function Description
After you set the conditions for checking the redundant or missing neighboring cell configurations, the Nastar performs inter-RAT neighboring cell analysis for the selected cell. The analysis results are displayed in a bar chart. In the bar chart, the defined UMTS neighboring cells, undefined UMTS neighboring cells, redundant UMTS neighboring cells, and missing UMTS neighboring cells are illustrated in different colors. The Nastar can export analysis results of inter-RAT neighboring cells to a file. In the inter-RAT neighboring cell analysis result window, you can export the result file of inter-RAT neighboring cell analysis after adding the missing neighboring cells and deleting the redundant neighboring cells. The result file provides the related optimization suggestions. The GSM/UMTS neighboring cell analysis results can be exported to a .csv, .xls, or .xlsx file.
Function Algorithm
This section describes the algorithm for the neighboring GSM/UMTS cell analysis, such as the algorithm used to check missing neighboring cells and redundant neighboring cells. Based on the measurement reports (MRs) reported by UEs, the Nastar calculates the overall score and then ranks the defined and undefined UMTS neighboring cells. According to the ranking of UMTS neighboring cells and result analysis charts, you can enable the Nastar to analyze the neighboring cells depending on the actual network situation, and then provide suggestions on missing UMTS neighboring cells to be added and redundant UMTS neighboring cells to be deleted. The algorithms for GSM/UMTS neighboring cell analysis are as follows: 1. Calculate the integrated priority of all the UMTS neighboring cells of a serving cell. In terms of multiple factors such as UMTS neighboring cells MRs, measurement time, and serving cell MRs, the GSM/UMTS neighboring cell analysis provides scores and integrated 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 M2000. Figure 3-19 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 3-13.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 318
Before you use the Nastar to collect and import performance data, check that the data export function has been enabled on the M2000.
Table 3-13 Description of analysis User Operat ion 1. Subscri be to applicat ion data Proced ure Issue an applicat ion data subscrip tion comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
To request the M2000 to filter 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.
Issue 01 (2013-07-15)
319
Proced ure Collect perform ance data Upload perform ance data
So urc e eS AU
Purpose
To deliver a data-processing request to the M2000, requesting the M2000 to filter out the performance data that meets the Nastar's requirements. To upload the performance data that meets the Nastar's requirements to the eSAU.
M2 000
eSA U
Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Issue 01 (2013-07-15)
320
Table 3-14 Network changes and their respective impacts Network Change Adding or deleting BTSs Impacts Affects network coverage and normal handovers between cells. As a result, the analysis results cannot accurately reflect the current state of network. The cell coverage and network interference may change.
Adjusting the antenna data, such as the azimuth, tilt, and height of an antenna 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. Statistical results are affected if you change the handover parameters and handover relationship during neighbor relationship data collection and optimization. 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.
Adjusting handover relationship and handover parameters Adjusting the BSC topology or other network topology
Issue 01 (2013-07-15)
321
engineering parameters are correct. For example, if the cell identification information in the engineering parameters is not consistent with the configuration data, the TOP cell will be repeated in the network geographic observation function. Map file (optional) The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map. You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
Prerequisite
GSM configuration data and GSM engineering parameters have been imported to the Nastar database. For details, see 3.4.2 Preparations for GSM/UMTS Neighboring Cell Analysis.
Procedure
Figure 3-20 shows the analysis process.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 323
Issue 01 (2013-07-15)
324
Table 3-15 Description of GSM/UMTS neighboring cell analysis procedures N o. (1 ) Procedure Description Reference for Detailed Operations 2.6 Checking the Integrity of Analysis Data
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to GSM/UMTS Neighboring Cell analysis data. 2. Set the query time segment. 3. Select the NE to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
(2 )
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the GSM tab. 2. Choose the NE to be configured in the navigation tree. 3. Click ON on the Subscribe to GSM/UMTS neighboring cell application data tab. 4. On the Measure Task tab, configure the time segment. Click Next. 5. In Result of setting window, click Batch. 6. In Set ARFCH and scrambling code window, add the ARFCN and scrambling code of a cell. 7. Click Finish. 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.
Issue 01 (2013-07-15)
325
N o.
Procedure
Description
Reference for Detailed Operations 2.6 Checking the Integrity of Analysis Data
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to GSM/UMTS Neighboring Cell analysis data. 2. Set the query time segment. 3. Select the NE to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
(3 )
Navigation path: Choose Theme Function> > Basic Network Optimization > GSM/ UMTS Neighboring Cell Analysis from the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click GSM/UMTS Neighboring Cell Analysis. 2. Set the task name and task remarks. Click Next. 3. Select the NE to be analyzed on the Select NE(s) tab. 4. Configure parameters on the Parameter Settings tab. Click Next. For details about parameters, see Analysis Task Parameters. 5. Choose an analysis time segment. After you set the time range, the Nastar obtains the analysis data generated within this time range. 6. Click Finish.
Issue 01 (2013-07-15)
326
N o. (4 )
Procedure
Description
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click an analysis result of the task. 2. View the analysis result in the displayed GSM/UMTS Neighboring Cell Analysis window. For details about analysis results, see Interface Description: GSM/UMTS Neighboring Cell Analysis.
(5 )
Navigation path: Choose a neighboring cell analysis task whose status is Finish 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. Right-click an analysis result of the task, and choose GSM/UMTS Possible Neighboring Analysis from the shortcut menu. 2. View the GSM/UMTS possible neighboring cell analysis result in the displayed GSM/ UMTS Possible Neighboring Cell Analysis. For details about analysis results, see Interface Description: GSM/UMTS Possible Neighboring Cell Analysis.
(6 )
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. For the description of export icon, see Interface Description: GSM/UMTS Neighboring Cell Analysis. 2. Set the export path and export format. 3. Click Finish.
Issue 01 (2013-07-15)
327
N o. (7 )
Procedure
Description
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. For the description of export icon, see Interface Description: GSM/UMTS Possible Neighboring Cell Analysis. 2. Set the export path and export format. 3. Click Save.
Measure Step
Execute Times
NE Object
Issue 01 (2013-07-15)
328
Description The 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.
Parameter information Parameter Neighboring Cell Count Setting Description Threshold of the neighboring cell sequence number. All the undefined neighboring cells whose sequence numbers are smaller than or equal to the value of this parameter are regarded as missing neighboring cells. All the defined neighboring cells whose sequence numbers are larger than the value of this parameter are regarded as redundant neighboring cells. This parameter can be set to any integer from 3 to 32. The default value is 26. Number of undefined neighboring cells to be displayed Indicates that only the TopN undefined neighboring cells are displayed. N can be any integer from 20 to 50. The default value is 30.
Issue 01 (2013-07-15)
329
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Main Window
In the main window, the system shows the analysis results of neighboring UMTS cells in lists and charts, including the list of test cells, list of neighboring cells, bar chart, and line chart, as shown in Figure 3-21.
Issue 01 (2013-07-15)
330
No. 1
Description 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.
Issue 01 (2013-07-15)
331
No. 3
Description 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 header to display the table in the descending order. column
Chart area
In this area, the information about all neighboring UMTS cells of the selected cells is displayed in a bar+line chart. l The system arranges the neighboring UMTS cells in sequence by their overall priorities and displays the percentages of the top 32 neighboring UMTS cells in a bar chart. l You can select a parameter from the drop-down list on the upper right to display the statistical results of the parameter for the top 32 neighboring UMTS cells in a line chart.
Map Interface
After you click on the upper left of the Nastar client, the map interface (Geographic Observation) is displayed. The Figure 3-22 shows this interface.
Issue 01 (2013-07-15)
332
Figure 3-22 Map interface for GSM/UMTS neighboring cell analysis results
No. 1
Description Displays all the buttons for performing basic operations on the map interface. For the meanings of these buttons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
Navigation tree
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. 4 Legend area This area is not displayed by default. It is displayed only after you click 5 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.
333
Issue 01 (2013-07-15)
Main Window
In the main window, the system shows the analysis results of possible neighboring UMTS cells in charts and lists, including the summary of possible neighboring UMTS cell analysis results and the confirmation list of possible neighboring UMTS cells, as shown in Figure 3-23. Figure 3-23 GSM/UMTS Neighboring cell analysis Interface
Issue 01 (2013-07-15)
334
No. 1
Description 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. 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. You can also press Ctrl+F to search in the area. 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.
Summary of possible neighborin g UMTS cell analysis results Confirmati on list of possible neighborin g UMTS cells
Issue 01 (2013-07-15)
335
Ec/NO RSCP
N/A
[0,+)
Number
[0,+)
Number
[0,+)
N/A
Issue 01 (2013-07-15)
336
Parameter Number of Missing Neighboring Cells Percentage of Measurement Reports on Missing Neighboring Cells (%)
Range [0,+)
Unit Number
Description Number of Missing Neighboring Cells Indicates the sum of the integrated priority of the missing neighboring UMTS cells of the current test cell. Indicates the location area code of the current test cell. Indicates the identification code of the current test cell. Indicates the broadcast control channel of the current test cell. Indicates the base station identity code of the current test cell. Indicates the ID of the current test cell.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
N/A
LAC
[1,65533], [65535]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
CI
[0,65535]
N/A
BCCH
[0,1023]
N/A
BSIC
[0,77]
N/A
[0,2047]
N/A
Issue 01 (2013-07-15)
337
Range N/A
Unit N/A
Description Indicates the service type of the neighboring cell of the current test cell, such as indoor site and outdoor site. Learning the service type of the test cell prevents important neighboring cells from being mistakenly deleted.
RNC ID
[0,+)
N/A
CI
[0,65535]
N/A
DownLink ARFCN
N/A
N/A
Issue 01 (2013-07-15)
338
Parameter P-SC
Range [0,511]
Unit N/A
Description Indicates the primary scrambling code of a neighboring UMTS cell. Indicates the operation suggestions that the Nastar provides.
Suggested Operation
Defined Neighboring Cell(Reserved), Defined Neighboring Cell (Redundant), Undefined Neighboring Cell(Missing) or Undefined Neighboring Cell(NonOperation) N/A
N/A
User Modify
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. Indicates the total score of each neighboring cell based on the measurement result according to the neighboring cell algorithm. Indicates the integrated priority of the neighboring UMTS cell.
Total Score
N/A
N/A
Integrated Priority
N/A
N/A
Issue 01 (2013-07-15)
339
Range N/A
Unit N/A
Description Indicates the service type of a neighboring UMTS cell, such as indoor site and outdoor site. Learning the service type of the neighboring UMTS cell prevents important neighboring cells from being mistakenly deleted. Indicates the distance from the current test cell to a neighboring UMTS cell. Indicates the duration that a neighboring UMTS cell is measured. 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. Indicates the average signal strength of the selected test cell.
Distance
[0,+)
km
[0,+)
minute
N/A
N/A
N/A
dB
Issue 01 (2013-07-15)
340
Range [0,+)
Unit Number
Description Indicates the number of MRs including the UMTS neighboring cell. Indicates the number of times a UMTS cell ranking No.1 in the neighboring cell list of MR. Indicates the number of handover requests from the current serving cell to another cell. Indicates the number of handover failures among all handover requests from the current serving cell to another cell.
Number of Measurement Reports with UMTS Cell Ranking First Request Number Of Handover
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
341
MCC-MNCLAC-CI
N/A
[0,1023]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,77]
N/A
N/A
N/A
[0,511]
N/A
[0,+)
N/A
Issue 01 (2013-07-15)
342
Range 1 to 64 characters
Unit N/A
Description Indicates the name of the selected possible neighboring UMTS cell. Indicates the cell identity code of the selected possible neighboring UMTS cell. Indicates the distance from the test cell to the selected possible UMTS neighboring cell. Indicates the relative angle between the selected possible neighboring UMTS cell and the test cell. Indicates the signal strength of the selected possible UMTS neighboring cell based on the dimensioning. Indicates whether the selected possible neighboring UMTS cell is obtained from the configuration data.
Neighboring Cell CI
[0,65535]
N/A
Distance
[0,+)
km
[0,360]
()
N/A
dBm
0,1
N/A
Issue 01 (2013-07-15)
343
Range 0,1,2,3,99
Unit N/A
Description Indicates the number of laps between the selected possible UMTS neighboring cell and the test cell, that is, the number of cells between the selected possible neighboring UMTS cell and the test cell. Indicates the number of possible neighboring cells in the possible neighboring UMTS cell pair. Indicates the integrated priority of the neighboring UMTS cell. 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. Indicates the average signal strength of the selected test cell.
[0,+)
N/A
Integrated Priority
N/A
N/A
N/A
dB
N/A
dBm
Issue 01 (2013-07-15)
344
Parameter Number of Neighboring Cell Measurement Reports Number of Times A Neighboring Cell Ranking No.1 in Measurement Reports
Range [0,+)
Unit Number
Description Indicates the number of MRs of a UMTS neighboring cell. Indicates the number of times a UMTS cell ranking No.1 in the neighboring cell list of MR.
[0,+)
Number
Issue 01 (2013-07-15)
345
Parameter
Range
Unit
Description Possible Neighboring Cell replaces Neighboring RNC. CI replaces Neighboring Cell CI. Distance(km) replaces Distance(km). Relative Angle of Possible Neighboring Cell() replaces Relative Angle of Neighboring Cell(). Predicted Signal Strength (dBm) replaces Predicted Signal Strength (dBm). Get from Config Data replaces Get from Config Data. Number of Neighboring Cell Laps replaces Number of Neighboring Cell Laps. If this parameter is not selected, it indicates that the most possible neighboring cell is not determined. In addition, the system clears all the information in the following fields in the possible
Supported NE Version
Issue 01 (2013-07-15)
347
Parameter
Range
Unit
Description 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
Supported NE Version
1 to 64 characters
N/A
Indicates the cell name of a possible neighboring UMTS cell. Indicates the ID of the RNC that a possible neighboring UMTS cell belongs to. Indicates the cell identity of a possible neighboring UMTS cell.
[0,+)
N/A
CI
[0,65535]
N/A
Issue 01 (2013-07-15)
348
Parameter Distance
Range [0,+)
Unit km
Description Indicates the distance from the test cell to a possible neighboring UMTS cell. Indicates the relative angle between the test cell and a possible neighboring UMTS cell. Indicates the signal strength of a possible neighboring UMTS cell based on the dimensioning. Indicates whether the possible neighboring UMTS cell is obtained from the configuration data. Indicates the number of laps between the test cell and a possible neighboring UMTS cell, that is, the number of cells between the test cell and a possible neighboring UMTS cell.
[0,360]
()
N/A
dBm
0,1
N/A
[0,+)
Number
Issue 01 (2013-07-15)
349
Function Description
The Nastar analyzes the uplink levels of a cell to display the received signal strength of the measurement ARFCNs in this cell. This provides reference for you to select appropriate ARFCNs. Huawei BTSs can scan the uplink receive levels of all frequencies at P-GSM (1124), E-GSM (0, 9751023), R-GSM (955974), DCS1800 (512885), PCS1900 (512810), GSM850_BAND (128251) or FB_BAND_TGSM810 (350425). That is, Huawei BTSs can scan the interfering signal strength at any of the preceding frequencies. Huawei BTS3X series BTSs perform uplink interference analysis based on the following principles: Without affecting normal calls, the BTSs use the IDLE frame of a TCH within the measurement cell to repeatedly scan the uplink receive levels of specified ARFCNs. When the BSC allocates TCHs, the BTSs prefer the IDLE frame of the TCH at the TRX where the BCCH is located. Therefore, the BTSs can scan only the ARFCNs that are in the same frequency band as the ARFCN of the measurement cell. The TCH adopts the structure of 26 multiframes. Each TCH multiframe contains an IDLE frame. The period of the IDLE frame on the TCH is 26 multiframes x 0.577 (Burst length) x 8 (TDMA frame) = 120 ms. Each ARFCN is measured 10 times and about one minute is required for measuring 50 ARFCNs. An uplink interference analysis task records a maximum of 124 ARFCNs. Therefore, about three minutes are required for measuring these ARFCNs. After you create an uplink interference analysis task, the Nastar will perform uplink interference analysis on the selected cells. The analysis results can be displayed in bar charts or line charts that use different colors to show the average main and diversity interference strength for each ARFCN at each time point.
Issue 01 (2013-07-15)
350
Function Principles
The Nastar uses the scanned uplink frequency data on the M2000 for GSM uplink interference analysis. Figure 3-24 shows the principles for collecting, importing, and analyzing data by using the Nastar on a newtork where NEs such as BSC6900s (excluding eGSM BTSs) are deployed. For detailed operations, see Table 3-16. Figure 3-24 Principles for analysis
Issue 01 (2013-07-15)
351
Table 3-16 Description of analysis User Operat ion 1. Subscri be to applicat ion data Proced ure Issue an applicat ion data subscrip tion comma nd Upload scanned uplink frequen cy data 2. Check the integrit y of analysi s data Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results So urc e Nas tar Ser ver Dest inati on eSA U Purpose
To request the 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.
M2 000
The Nastar periodically scans the directories on the M2000 for saving reported data. By doing this, the Nastar can obtain data from the M2000 immediately once data is reported. 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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Issue 01 (2013-07-15)
352
Figure 3-25 shows the principles for collecting, importing, and analyzing data by using the Nastar on a network where eGSM BTSs are deployed. For detailed operations, see Table 3-17. Figure 3-25 Principles for analysis
Table 3-17 Description of analysis User Operat ion 1. Subscri be to applicat ion data Proced ure Issue an applicat ion data subscrip tion comma nd Collect scanned uplink frequen cy data So urc e Nas tar Ser ver Dest inati on eSA U Purpose
To request the 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.
eS AU
M20 00
The eSAU delivers data processing requests to NEs through the M2000, requesting the NEs to report scanned uplink frequency data to the M2000.
Issue 01 (2013-07-15)
353
So urc e M2 000
Purpose
The eSAU periodically scans the directories on the M2000 for saving reported data. By doing this, the eSAU can notify the Nastar of obtaining data from the M2000 once data is reported. 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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
354
Issue 01 (2013-07-15)
Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Checking the License on the M2000/GBSC License(GSM) in Nastar System Commissioning Guide.
Prerequisites
GSM configuration data has been imported into the Nastar database. For detailed operations, see 3.5.2 Preparations for GSM Uplink Interference Analysis.
Procedure
Figure 3-26 shows the analysis process. Figure 3-26 Analysis process
Issue 01 (2013-07-15)
356
Table 3-18 Description of the GSM uplink interference analysis process No. (1) Proced ure Check the integrit y of GSM uplink interfer ence analysis data Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Choose Data Type > Basic Network Optimization > GSM Uplink Interference Analysis Data. 2. Specify the time period. 3. Select the desired 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
(2)
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, 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 Parameters Setting dialog box, set the threshold parameters. For details about the parameters, see Subscription Task Parameters. 5. Click Finish.
Issue 01 (2013-07-15)
357
No.
Proced ure Check the integrit y of GSM uplink interfer ence analysis data
Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Choose Data Type > Basic Network Optimization > GSM Uplink Interference Analysis Data. 2. Specify the time period. 3. Select the desired 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 the analysis data does not exist, contact Huawei technical support.
(3)
Navigation path: In the navigation tree of the Analysis Task Management window, choose Theme Function > Basic Network Optimization > GSM Uplink Interference Analysis. 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. 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.
l For detailed operations, see 2.7 Creating an Analysis Task. l For details about the parameters, see Analysis Task Parameters.
Issue 01 (2013-07-15)
358
No. (4)
Description Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 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.
Reference l For detailed operations, see 2.8 Querying Analysis Results. l For details about the analysis result interface, see 3.5.4 Interface Description: GSM Uplink Interference Analysis.
Issue 01 (2013-07-15)
359
Description 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)
Cells involved in a GSM uplink interference analysis task. 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
Issue 01 (2013-07-15)
360
Description 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
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
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.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Portal
Use either of the following methods to open the interface that displays GSM uplink interference analysis results:
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 361
l l
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 3-27 shows the interface. Figure 3-27 Interface for GSM uplink interference analysis results
N o. 1
Description Displays the interference strength of all measurement cells involved in an analysis task. 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. 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.
Informati on area
Issue 01 (2013-07-15)
362
N o. 3
Description 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 Interference, 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 Interference, 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.
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.
Overview
Parameter BSC Name Range 1 to 32 characters Unit N/A Description Indicates the name of a BSC, for example, BSC_1. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
363
Parameter Cell ID
Range [0,65535]
Unit N/A
Description Indicates the ID of a cell. Number of the location group under the BTS. It is unique for each BTS. Indicates the frequency of a measured TRX. Indicates the type of a measured TRX. The options are BCCH and TCH. Indicates the average main interference strength of a measured TRX. Indicates the average diversity interference strength of a measured TRX. Number of the location group under the BTS. It is unique for each BTS.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
0 to 35 or null
N/A
Frequency
N/A
N/A
Type
BCCH, TCH
N/A
N/A
dBm
N/A
dBm
0 to 35 or null
N/A
Parameters
Parameter Cell Name Range 1 to 64 characters Unit N/A Description Indicates the name of the cell that a measured TRX belongs to. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
364
Range 1 to 32 characters
Unit N/A
Description Indicates the name of a BSC, for example, BSC_1. Indicates the time range in which an uplink interference analysis task is performed. Indicates a BCCH ARFCN of the selected cell. Indicates the type of the frequency hopping. Indicates all TCH ARFCNs of the selected cell. Indicates the counter bar chart of the selected cell at a certain time. Indicates the data sequence mode in the bar chart. Diversity indicates the average diversity interference strength. Main indicates the average main interference strength.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Time Scope
N/A
N/A
BCCH Frequency
N/A
N/A
N/A
TCH List
N/A
Time Point
N/A
N/A
Sort Type
N/A
Issue 01 (2013-07-15)
365
Parameter Date
Range N/A
Unit day
Description Time period for the analysis results of a selected cell. 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.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Frequency
N/A
N/A
Function Description
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:
Issue 01 (2013-07-15)
366
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 Traffic Model. The Nastar calculates the traffic counter value of each terminal on the live network during the busy hour by different dimensions and provides a trend analysis chart based on the analysis result. The analysis chart shows the traffic problems on the GSM network. Terminal geographic observation. The Nastar supports the display of terminal distribution using the Geographic Information System (GIS) and supports the geographic display from the two dimensions of terminal flow consumption and terminal support ability, which helps network optimization engineers to analyze problems and improve the efficiency of locating problems.
Function Principles
The data source for terminal analysis is the CHR data on the NE side. Figure 3-28 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 3-19.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
367
Table 3-19 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
Issue 01 (2013-07-15)
368
So urc e M2 000
Purpose
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue a data query comma nd Return data query results Issue a task executio n comma nd
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
Issue 01 (2013-07-15)
369
So urc e eS AU
Purpose
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
The license for GSM terminal traffic model analysis is required for viewing the function of GSM terminal traffic model analysis. The license for GSM terminal geographic display is required for viewing the function of GSM terminal geographic display. l If a user wants to view only the task results, only the rights to view terminal analysis results needs to be granted. If the user wants to perform further operations on tasks, the following rights must be granted: Right to subscribe to the source data for terminal analysis. The source data subscription function has high security requirements. You are advised to contact the administrator to turn on the data source switch. Right to perform operations on the NEs to be analyzed. Right to perform operations on terminal analysis tasks. You need to obtain right to perform GSM terminal inventory analysis if you want to perform GSM terminal penetration analysis, GSM terminal capability analysis, and GSM terminal performance analysis. You need to obtain right in order to perform GSM terminal traffic model analysis. You need to obtain right in order to perform GSM terminal geographic observation.
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) 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 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. Map files (Optional) The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map.
Prerequisites
The GSM configuration data and GSM engineering parameters have been imported to the Nastar database. The terminal types and data service types have been configured on the Nastar. For details, see 3.6.2 Preparations for GSM Terminal Analysis.
Process
Figure 3-29 shows the analysis process. Figure 3-29 Analysis process
Issue 01 (2013-07-15)
373
Table 3-20 Description of the terminal analysis process No. (1) Procedure Check whether analysis data is integrated? Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to GSM Terminal Inventory Analysis Data, GSM Terminal Traffic Model Analysis Data or 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 Traffic Model Analysis Data is required to analyze terminal traffic models. l Only GSM Terminal Geographic Observation Data is required to observe terminals geographically.
2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
374
No. (2)
Description Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the GSM tab. 2. Select the NEs to be configured from the left navigation tree. 3. On the Basic Subscription Settings tab page, click Set. 4. In the Basic Subscription Settings dialog box, set the switch of Terminal Analysis Data (CHR-CS), Terminal Analysis Data(CHRPS) to ON. 5. Click Confirm. Verify that the data switch is successfully turned on by viewing information displayed in the Log Info area.
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the GSM tab. 2. Select the NEs to be configured from the left navigation tree. 3. On the Terminal Analysis tab page, click ON. 4. In the Terminal Analysis Parameter Setting dialog box, set the threshold value for exceptions. For details about parameters, see Subscription Task Parameters. 5. Click Confirm. Verify that data subscription is successfully turned on by viewing information displayed in the Log Info area.
Issue 01 (2013-07-15)
375
No.
Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to GSM Terminal Inventory Analysis Data, GSM Terminal Traffic Model Analysis Data or 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 Traffic Model Analysis Data is required to analyze terminal traffic models. l Only GSM Terminal Geographic Observation Data is required to observe terminals geographically.
2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
Issue 01 (2013-07-15)
376
No. (3)
Description Navigation path: In the left navigation tree of the Analysis Task Management window, choose Theme Function > Terminal Analysis > GSM Terminal Analysis. Procedure: 1. Double-click the GSM Terminal Analysis node. 2. Set the task name and task remarks. Click Next. 3. On the Select NE(s) tab page, select the NEs to be analyzed. 4. Optional: On the Select Geographic Terminal Objects tab page, select terminals for analysis. You can select a maximum of 10 terminals. The Nastar automatically analyzes traffic of selected terminals in each raster. 5. Optional: On the Select Geographic Terminal Abilities tab page, select terminal capabilities for analysis. The Nastar calculates numbers and percentages of terminals supporting the capabilities in each raster. 6. Optional: On the Set Traffic Model Parameters tab page, select busy hours for traffic model analysis. 7. Optional: On the Grid Resolution Settings tab page, select the Grid Resolution for displaying terminal geographic observation results. 8. Click Next. 9. Select the analysis time period. The Nastar obtains the relevant analysis data in the time period. 10.Click Finish. For details about parameters, see Analysis Task Parameters.
Issue 01 (2013-07-15)
377
No. (4)
Description Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click the analysis result of a task. 2. In the displayed GSM Terminal Analysis Task window, view the GSM terminal analysis result.
Reference l For details, see 2.8 Querying Analysis Results. l For details on the description about the window for displaying task results, see 3.6.4 Interface Description: GSM Terminal Analysis. l For details, see 2.10 Exporting Analysis Reports. l For details on the description about the window for displaying task results, see 3.6.4 Interface Description: GSM Terminal Analysis.
(5)
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. 2. Set the export path and export format. 3. Click Save.
Issue 01 (2013-07-15)
378
Description 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. Value range: [0.0,100000.0]
Overlong Call Setup Duration Threshold (MOC) Overlong Call Setup Duration Threshold (MTC) Uplink VQI Abnormal Threshold
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. 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. 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,5] The larger the value is, the better the voice quality is.
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/ Number of the measurement reports with the reception quality of level 0 to level 7 x 100%
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/ Number of the measurement reports with the reception quality of level 0 to level 7 x 100%
Issue 01 (2013-07-15)
379
Description 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 The name is unique and case-sensitive and cannot be empty. l Task Name must be named in Chinese or English. Otherwise, the function of distributing analysis results by emails is unavailable.
Type of an analysis task to be created. Description of the task. Value range: The name contains a maximum of 200 characters.
Parameter information Parameter Grid Resolution Settings Description 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. Select Geographic Terminal Abilities Select Geographic Terminal Objects 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. 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. Sets busy hours for traffic model analysis. If the parameters are not set, the Nastar does not analyze the traffic model.
Issue 01 (2013-07-15)
380
Parameter Date
Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Navigation Path
Use either of the following methods to open the interface that displays GSM terminal analysis results: l l Select a GSM terminal analysis task in the Finish state and double-click a result record in the Task Result area. Select a GSM terminal analysis task in the Finish state, right-click a result record of the task in the Task Result area, and choose View Analysis Result from the shortcut menu.
Interface
Figure 3-30 shows the GSM terminal analysis result interface. Figure 3-30 Interface for GSM terminal analysis results
No. 1
Description is used to display terminal analysis results on maps. For detailed operations, see Terminal Analysis Results Displayed Through Geographic Observation.
Issue 01 (2013-07-15)
381
No. 2
Description Analysis results are displayed on tab pages. l The Analyze Terminal 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 Analyze Terminal 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 Analyze Terminal 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. l The Analyze Terminal Traffic Model tab page is used to analyze the traffic indicator of each type of terminal within a certain period. For detailed operations, see Interface Description: Terminal Traffic Model Analysis.
Issue 01 (2013-07-15)
382
No. 1
Description l 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 Aggregation Type 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. The number and occupation of TopN terminals on the live network from a certain analysis dimension are displayed in a table. You can save the table by right-clicking the table and choosing Save As from the shortcut menu.
Statistics table
No. 1
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.
383
Issue 01 (2013-07-15)
No. 2
Description Selects all objects to be analyzed. Allows users to select objects for analysis from three dimensions: whole network, a single BSC, or a single cell. 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. The proportion of the terminals that support a certain terminal capability in an NE object and the proportion of the terminals that do not support a certain terminal capability in an NE object are displayed in a histogram. The histogram is mapped to the table on the right. The analysis results of a maximum of two types of terminal capabilities can be displayed at the same time. You can view the analysis results of other terminal capabilities by using the scroll bar.
Table area
The number and occupation of the terminals that support a certain terminal capability in an NE object are displayed in a table. You can save the table by right-clicking the table and choosing Save As from the shortcut menu. For detailed parameters, see 3.6.5 Parameters for Viewing GSM Terminal Analysis Results.
Issue 01 (2013-07-15)
384
No. 1
Description 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 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. 3 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. You can save the table by rightclicking the table and choosing Save As from the shortcut menu. For detailed parameters, see 3.6.5 Parameters for Viewing GSM Terminal Analysis Results.
Issue 01 (2013-07-15)
385
No. 1
Description l Top part of the table Aggregation Type drop-down list: allows you to select a dimension from which the analysis is performed. Sequence Column: allows you to select a KPI based on which the system sorts the table in area 1 again. TOPN: allows you to specify the number of the TopN objects that you want to analyze. Busy Hour: displays the period for analyzing traffic models. Set the period when you create an analysis task. l Table part: Displays the traffic model KPI value of the aggregation analysis performed on the terminals based on the selected dimension. The table is displayed together with the chart below the table. You can right-click in the table 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. For detailed parameters, see 3.6.5 Parameters for Viewing GSM Terminal Analysis Results.
Displays the trend chart of an indicator of the selected NEs in the preceding table during the busy hour. You can view the trend chart of different indicators by selecting indicators in the Trend Chat Counters drop-down list. l The horizontal coordinate represents the analysis period (unit: day). l The vertical coordinate represents the average values of indicators during the busy hour.
Issue 01 (2013-07-15)
386
N o. 1
Issue 01 (2013-07-15)
387
N o. 2
Description 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
l Polygon Areas: enables you to analyze only a selected polygon in the Geographic Observation interface. You can save the cells in a polygon as a cell group. You can analyze multiple KPIs simultaneously based on a polygon. 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\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. 3 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. 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. This area is empty for terminal analysis.
Issue 01 (2013-07-15)
388
N o. 5
Description 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. 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.
Informati on area
The interface displays no information when it is opened. If you select a grid, the values of selected KPIs in this gird are displayed. If you select a site, information about the site is displayed. If you select a cell, information about the cell such as engineering parameters and longitude and latitude coordinates is displayed.
Mo del
IME ITA C
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.
Issue 01 (2013-07-15)
389
Par am eter
R a n g e [ 1 , 2 5 6 ] N / A [ 0 , 2 5 6 ] N / A N / A
U Description n i t N Indicates the terminal vendor, for / example, Nokia and Apple. A
Supported NE Version
Ven dor
N Indicates the terminal type, for / example, common terminal, A intelligent terminal, and data card. N Indicates the terminal chip model. / A
N Indicates the RAT that the terminal / supports, for example, GSM and A WCDMA. N Indicates the data transfer mode that / the terminal uses, for example, A HSDPA and HSUPA.
[ 1 , + ) N / A
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.
Issue 01 (2013-07-15)
390
Par am eter
R a n g e N / A
U Description n i t N User-defined terminal attributes in / the terminal type management A window. The user-defined attribute names are displayed.
Supported NE Version
EG PRS
180 0 ban d
N / A
GS ME ban d
N / A
Issue 01 (2013-07-15)
391
Par am eter
R a n g e N / A
U Description n i t N Used to collect statistics about the / numbers and percentages of A terminals that support GSM/UMTS dual-mode, that do not support GSM/ UMTS dual-mode, and whose capability is unknown under a cell, BSC, or the entire network. N Used to collect statistics about the / numbers and percentages of 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. N Used to collect statistics about the / numbers and percentages of A terminals that support FDD-LTE, that do not support FDD-LTE, and whose capability is unknown under a cell, BSC, or the entire network. N Used to collect statistics about the / numbers and percentages of A terminals that support TDD-LTE, that do not support TDD-LTE, and whose capability is unknown under a cell, BSC, or the entire network. N Used to collect statistics about the / numbers and percentages of A terminals that support DTM, that do not support DTM, and whose capability is unknown under a cell, BSC, or the entire network. N Used to collect statistics about the / numbers and percentages of A terminals that support the 8PSK modulation mode, that do not support the 8PSK modulation mode, and whose capability is unknown under a cell, BSC, or the entire network.
Supported NE Version
G/ TD dual mod es
N / A
FD DLTE
N / A
TD DLTE
N / A
DT M
N / A
N / A
Issue 01 (2013-07-15)
392
Par am eter
R a n g e N / A
U Description n i t N Used to collect statistics about the / numbers and percentages of 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. N Used to collect statistics about the / numbers and percentages of A terminals that support PS handovers, that do not support PS handovers, and whose capability is unknown under a cell, BSC, or the entire network. N Used to collect statistics about the / numbers and percentages of A terminals that support U900, that do not support U900, and whose capability is unknown under a cell, BSC, or the entire network. N Used to collect statistics about the / numbers and percentages of A terminals that support VAMOS, that do not support VAMOS, and whose capability is unknown under a cell, BSC, or the entire network. N Used to collect statistics about the / numbers and percentages of A terminals that support Wi-Fi, that do not support Wi-Fi, and whose capability is unknown under a cell, BSC, or the entire network.
Supported NE Version
PS han dov er
N / A
U90 0
N / A
VA MO S
N / A
WiFi
N / A
Issue 01 (2013-07-15)
393
[ 0 , + )
N u m b e r
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.
Issue 01 (2013-07-15)
394
Par am eter
R a n g e [ 0 , + )
U Description n i t N u m b e r Indicates the number of abnormal originated call setups. If the terminal receives a Connect Acknowledge signaling or the Disconnect signaling and the call is terminated by the peer terminal, the call setup is successful. If the terminal receives a Clear command message and the call is normally released by the network, local terminal, or peer terminal, the call setup is successful. If inter-BSC handover occurs during the call setup process and the call fails to be set up in the destination BSC, the Nastar records that the call is released abnormally.
Supported NE Version
Rati o of Call Setu p Exc epti ons (M OC) Call Setu p Req uest s (MT C)
[ 0 , 1 0 0 ]
% Indicates the proportion of abnormal originated call setups. Proportion of abnormal originated call setups = Number of abnormal originated call setups/Number of originated call setup requests x 100%
[ 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.
Issue 01 (2013-07-15)
395
Par am eter
R a n g e [ 0 , + )
U Description n i t N u m b e r Indicates the number of abnormal 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 call is set up successfully. If an inter-BSC handover occurs during the call setup process and the call fails to be set up in the destination BSC, the Nastar records that the call is released abnormally.
Supported NE Version
Rati o of Call Setu p Exc epti ons (MT C) Abn orm al Rele ases Bef ore Call Co mpl etio n
[ 0 , 1 0 0 ]
% Indicates the proportion of abnormal terminated call setups. Proportion of abnormal terminated call setups = Number of abnormal terminated call setups/Number of terminated call setup requests
[ 0 , + )
N u m b e r
Indicates the total number of call setup failures due to exceptions that occur upon outgoing call alerting after a terminal sends call access requests.
Issue 01 (2013-07-15)
396
Issue 01 (2013-07-15)
397
Par am eter
R a n g e [ 0 , 1 0 0 ]
U Description n i t % 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 N u m b e r 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.
Supported NE Version
[ 0 , + )
Rati o of Sho rt Call s (MT C) Abn orm al Traf fic Rele ase Rati o
[ 0 , 1 0 0 ]
% 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 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.
[ s 0 , + )
Issue 01 (2013-07-15)
398
Intr aSyst em Han dov er Req uest s Intr aSyst em Abn orm al Han dov ers Rati o of Intr aSyst em Abn orm al Han dov ers
[ 0 , + )
[ 0 , 1 0 0 ]
% Indicates the proportion of abnormal intra-RAT handovers. Proportion of abnormal intra-RAT handovers = Number of abnormal intra-RAT handovers/Number of intra-RAT handover requests x 100%
Issue 01 (2013-07-15)
399
Par am eter
R a n g e [ 0 , + )
U Description n i t N Indicates the number of abnormal call u releases during the intra-RAT m handover. b e r
Supported NE Version
Issue 01 (2013-07-15)
400
Par am eter
R a n g e [ 0 , + )
U Description n i t N u m b e r Indicates the number of abnormal terminal handovers from a cell on a GSM network to a cell on another network.
Supported NE Version
Abn orm al Inte rRA T Out goin g Han dov ers Rati o of Abn orm al Inte rRA T Out goin g Han dov ers Abn orm al Rele ases Duri ng Inte rRA T Out goin g Han dov er
[ 0 , 1 0 0 ]
% Indicates the proportion of abnormal 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%
[ 0 , + )
N u m b e r
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.
Issue 01 (2013-07-15)
401
Par am eter
R a n g e [ 0 , + )
U Description n i t 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.
Supported NE Version
Inte rRA T Inco min g Han dov er Req uest s Abn orm al Inte rRA T Inco min g Han dov ers Rati o of Abn orm al Inte rRA T Inco min g Han dov ers
[ 0 , + )
N u m b e r
Indicates the number of abnormal terminal handovers from a cell on another network to a cell on a GSM network.
[ 0 , 1 0 0 ]
% Indicates the proportion of abnormal 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%
Issue 01 (2013-07-15)
402
Par am eter
R a n g e [ 0 , + )
U Description n i t 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
Supported NE Version
Inte rRA T Inco min g Han dov er Del ay Rep orts 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
Issue 01 (2013-07-15)
403
Call Setu p Del ay Rep orts (M OC) Call Setu p Ave rage Del ay (M OC) Rati o of Call Setu p Ove rlon g Del ays (M OC) Call Setu p Del ay Rep orts (MT C)
[ s 0 , + )
[ 0 , 1 0 0 ]
% Indicates the proportion of MRs in which the originated call setup delay is greater than the specified threshold. 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%
[ 0 , + )
N u m b e r
Indicates the number of MRs with 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.
Issue 01 (2013-07-15)
404
Par am eter
R a n g e
U Description n i t 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.
Supported NE Version
Call Setu p Ave rage Del ay (MT C) Rati o of Call Setu p Ove rlon g Del ays (MT C)
[ s 0 , + )
[ 0 , 1 0 0 ]
% 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%
N Average uplink VQI value = Total value of uplink / VQIs/Number of MRs with valid uplink VQI A
Issue 01 (2013-07-15)
405
Par am eter
R a n g e [ 0 , 1 0 0 ] [ 0 , + )
U Description n i t % Indicates the proportion of MRs in which the uplink VQI value is smaller than the specified threshold. 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%
Supported NE Version
Rati o of Upli nk Bad VQI Rep orts Upli nk HQI Rep orts
N u m b e r
Indicates the number of MRs with valid uplink High Quality Indicator (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: 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: HQI value = Number of MRs with grade 0 to grade 5 receive quality/Number of MRs with grade 0 to grade 7 receive quality x 100%
[ 0 , 1 0 0 ] [ 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. Average uplink HQI value = Total value of uplink HQIs/Number of MRs with uplink HQI % 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%
Issue 01 (2013-07-15)
406
Par am eter
R a n g e [ 0 , + )
U Description n i t 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: 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: HQI value = Number of MRs with grade 0 to grade 5 receive quality/Number of MRs with grade 0 to grade 7 receive quality x 100%
Supported NE Version
Do wnli nk Ave rage HQI Rati o of Do wnli nk Bad HQI Rep orts
[ 0 , 1 0 0 ] [ 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. Average downlink HQI value = Total value of downlink HQIs/Number of MRs with downlink HQI % 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%
Issue 01 (2013-07-15)
407
Par am eter
R a n g e [ 0 , 1 0 0 ]
U Description n i t % Indicates the proportion of calls with uplink crosstalk. 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.
Supported NE Version
[ 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 01 (2013-07-15)
408
Par am eter
R a n g e [ 0 , 1 0 0 ]
U Description n i t % Indicates the proportion of calls with uplink one-way audio. 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. 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.
Supported NE Version
Issue 01 (2013-07-15)
409
Par am eter
R a n g e [ 0 , 1 0 0 ]
U Description n i t % Indicates the proportion of calls with downlink oneway audio. 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. 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.
Supported NE Version
[ 0 , 1 0 0 ]
% Indicates the proportion of calls with no audio on both the uplink and the downlink. 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%
Issue 01 (2013-07-15)
410
Voi ce Serv ice Dur atio n Rep orts Ave rage Voi ce Serv ice Dur atio n Utra nFD DSup port ed Ter min al Voi ce Serv ice Dur atio n Rep orts
[ s 0 , + )
Indicates the average duration of the voice service. The voice service duration in the MR is from the time when the TCH is assigned to the time when the TCH is released. Average voice service duration = TCH occupation duration/Number of MRs with voice service duration Indicates the number of MRs with valid voice service duration of terminals that support UTRAN FDD. 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.
[ 0 , + )
N u m b e r
Issue 01 (2013-07-15)
411
Par am eter
R a n g e
U Description n i t Indicates the average voice service duration for terminals that support UTRAN FDD. The voice service duration in the MR is from the time when the TCH is assigned to the time when the TCH is released. Average voice service duration = TCH occupation duration/Number of MRs with voice service duration
Supported NE Version
Ave rage Utra nFD DSup port ed Ter min al Voi ce Serv ice Dur atio n Utra nTD DSup port ed Ter min al Voi ce Serv ice Dur atio n Rep orts
[ s 0 , + )
[ 0 , + )
N u m b e r
Indicates the number of MRs with valid voice service duration of terminals that support UTRAN TDD. 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.
Issue 01 (2013-07-15)
412
Par am eter
R a n g e
U Description n i t Indicates the average voice service duration for terminals that support UTRAN TDD. The voice service duration in the MR is from the time when the TCH is assigned to the time when the TCH is released. Average voice service duration = TCH occupation duration/Number of MRs with voice service duration
Supported NE Version
Ave rage Utra nTD DSup port ed Ter min al Voi ce Serv ice Dur atio n
[ s 0 , + )
BS C Na me
Issue 01 (2013-07-15)
413
Par am eter
R a n g e [ 0 , 7 9 9 9 ] 1 t o 6 4 c h a r a ct e rs
Supported NE Version
Cell ID
Cell Na me
Issue 01 (2013-07-15)
414
Par am eter
R a n g e
U Description n i t
Supported NE Version
CGI
M N Indicates the global identity of the C / cell where the terminal is located. C A M N C L A C C I M C C [ 0 0 0 , 9 9 9 ] M N C [ 0 0 , 9 9 ] L A C [ 0 , 6 5 5 3
Issue 01 (2013-07-15)
415
Par am eter
R a n g e 5 ] C I [ 0 , 6 5 5 3 5 ]
U Description n i t
Supported NE Version
NOTE
For details about other parameters, see Performance Analysis Summary-Accessibility Evaluation, Performance Analysis Summary-Retainability Evaluation, Performance Analysis SummaryHandover Evaluation, Performance Analysis Summary-System Handover Evaluation, Performance Analysis Summary-Delay Evaluation, Performance Analysis Summary-Quality Evaluation and Performance Analysis Summary-Multi-Mode.
[ K Used to collect statistics on the 0 B average uplink traffic of a terminal during busy hours. Busy hours are , specified by users. + )
Issue 01 (2013-07-15)
416
Par am eter
R a n g e
U Description n i t
Supported NE Version
Sin gleSub scri ber Bus yHou r Do wnli nk Traf fic Sin gleSub scri ber Bus yHou r Upl oad Rate Sin gleSub scri ber Bus yHou r Do wnl oad Rate
[ K Used to collect statistics on the 0 B average downlink traffic of a terminal during busy hours. Busy hours are , specified by users. + )
[ 0 , + )
k b it / s
Used to collect statistics on the average upload rate of a terminal during busy hours. Busy hours are specified by users.
[ 0 , + )
k b it / s
Used to collect statistics on the average download rate of a terminal during busy hours. Busy hours are specified by users.
Issue 01 (2013-07-15)
417
Par am eter
R a n g e
U Description n i t Used to collect statistics on the average number of interaction service delays of a terminal during busy hours. The delay is the duration from the time the service request is sent to the time the service data is received. Busy hours are specified by users.
Supported NE Version
Sin gleSub scri ber Bus yHou r Inte racti ve Serv ice Del ay Sin gleSub scri ber Sig nali ng Acc esse s at Upli nk CC CH to PS Serv ice in Bus y Hou rs
[ s 0 , + )
[ 0 , + )
N u m b e r
Used to collect statistics on the average number of PS service accessing CCCH of a terminal during busy hours. This parameter can be used to evaluate terminal impacts on the network load. Busy hours are specified by users.
Issue 01 (2013-07-15)
418
Par am eter
R a n g e [ 0 , + )
U Description n i t N u m b e r Used to collect statistics on the average number of PS service accesses of a terminal during busy hours. This parameter can be used to evaluate terminal impacts on the network load. Busy hours are specified by users.
Supported NE Version
Tota l Sin gleSub scri ber Upli nk Sig nali ng Acc esse s to PS Serv ice in Bus y Hou rs Ave rage Upli nk Cha nnel s Occ upie d by Sin gleSub scri ber PS in Bus y Hou rs
[ 0 , + )
N u m b e r
Used to collect statistics on the average uplink channel resources occupied by the PS service of a terminal during busy hours. Busy hours are specified by users.
Issue 01 (2013-07-15)
419
Par am eter
R a n g e [ 0 , + )
U Description n i t N u m b e r Used to collect statistics on the average downlink channel resources occupied by the PS service of a terminal during busy hours. Busy hours are specified by users.
Supported NE Version
Ave rage Do wnli nk Cha nnel s Occ upie d by Sin gleSub scri ber PS in Bus y Hou rs
[ K The grid map is rendered according 0 B to the total traffic of terminals in the , grids. + ) [ K The grid map is rendered according 0 B to the uplink traffic of terminals in the , grids. + )
Issue 01 (2013-07-15)
420
Par am eter
R a n g e
U Description n i t
Supported NE Version
[ K The grid map is rendered according 0 B to the downlink traffic of terminals in , the grids. + )
EG PRS
N / A
N / A
N / A N / A
Issue 01 (2013-07-15)
421
Par am eter
R a n g e N / A N / A
U Description n i t N The grid map is rendered according / to the percentage of terminals that A support DTM in the total number of terminals in the grids. N The grid map is rendered according / to the percentage of terminals that A support 8PSK modulation in the total number of terminals in the grids. N The grid map is rendered according / to the percentage of terminals that A support uplink expansion in the total number of terminals in the grids. N The grid map is rendered according / to the percentage of terminals that A support PS handover in the total number of terminals in the grids. N The grid map is rendered according / to the percentage of terminals that A support Wi-Fi in the total number of terminals in the grids.
Supported NE Version
DT M
N / A
N / A N / A
Issue 01 (2013-07-15)
422
Function Description
Generally, engineers prefer a whole-to-partial method to optimize the network and analyze the network performance. Under this method, the engineers locate and analyze network problems by monitoring certain KPIs, 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 cells, selected types of exception in a cell, selected causes of certain types of exception, and 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.
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 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 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 423
Figure 3-36 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 3-21.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Table 3-21 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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 01 (2013-07-15)
424
Proced ure Issue an MML comma nd Forward the MML comma nd Upload raw data
So urc e eS AU
Purpose
M2 000
BSC/ RNC
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
Nast ar Serv er
Issue 01 (2013-07-15)
425
Proced ure Issue a task executio n comma nd Upload data analysis results Display analysis results
Purpose
To deliver 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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Issue 01 (2013-07-15)
426
To ensure the validity of the configuration data, you are advised to perform GSM cell performance analyses on a per day basis.
This section includes the following information: l l l l Prerequisites Process Subscription Task Parameters Analysis Task Parameters
Prerequisites
GSM configuration data and GSM engineering parameters have been imported into the Nastar database. For detailed operations, see 3.7.2 Preparations for GSM Cell Performance Analysis.
Process
Figure 3-37 shows the analysis process. Figure 3-37 Analysis process
Issue 01 (2013-07-15)
428
Table 3-22 Description of the GSM cell performance analysis process No. (1) Proced ure Check the integrit y of analysi s data Description Navigation path: Choose Maintenance > Data Maintenance Management. Steps: 1. Set Data Type to GSM Cell Performance Analysis Data. 2. Specify the time period. 3. Select query 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
(2)
NOTE The source data subscription function has high security requirements. You are advised to contact the administrator to turn on the data source switch.
Navigation path: Choose Maintenance > Data Subscription Management. 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. If you want to view the all signaling information when viewing deep analysis results, click interface about All Signaling. , select the
5. Click Confirm. Check the information in the Log Info area and ensure that the data source switch is turned on.
Issue 01 (2013-07-15)
429
No.
Description Navigation path: Choose Maintenance > Data Subscription Management. 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 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
Reference
Navigation path: Choose Maintenance > Data Maintenance Management. Steps: 1. Set Data Type to GSM Cell Performance Analysis Data. 2. Specify the time period. 3. Select query 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 the analysis data does not exist, contact Huawei technical support.
(3)
Navigation path: Choose Theme Function > Network Analysis > GSM Cell Performance Analysis in the navigation tree of the Analysis Task Management window. 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.
l For detailed operations , see 2.7 Creating an Analysis Task l For detailed descriptio n of the parameter s, see Analysis Task Paramete rs.
430
Issue 01 (2013-07-15)
No. (4)
Description Navigation path: In the upper right area of the Analysis Task Management window, select a cell performance analysis task in the Finish state. In the lower right Task Result area, select a result record of the task. 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.
Reference l For detailed operations , see 2.8 Querying Analysis Results l For detailed descriptio n of the window for showing analysis results, see 3.7.4 Interface Descripti on: GSM Cell Performa nce Analysis. l For details, see 2.10 Exportin g Analysis Reports. l For details on the descriptio n of the window for showing analysis results, see 3.7.4 Interface Descripti on: GSM Cell Performa nce Analysis.
Navigation path: 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. 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.
(5)
Navigation path: Click the export icon on the toolbar in the upper left area of the GSM cell performance analysis window. Steps: 1. Click the export icon on the toolbar. 2. Set the format and save path for exporting file. 3. Click Save.
Issue 01 (2013-07-15)
431
Uplink HQI
Issue 01 (2013-07-15)
432
Parameter Call Compl etion Delay (Alteri ng) (MOC) (s) Call Compl etion Delay (Alteri ng) (MTC) (s) Short Call Probl em Short Call (MOC) (s)
Description 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).
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 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 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. 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. 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.
TA on Access RACH Level on Access (dBm) Cell Resele ction Durati on(s)
Da ta Ser vic e
Service interruption indicating service interruption caused by a cell reselection (the cell reselection succeeds after multiple attempts): The cell reselection duration (s) is the average service interruption duration, namely, the average interval between two cell reselection attempts, when a subscriber is using a data service.
Issue 01 (2013-07-15)
433
Parameter Abno rmal Servi ce Inter actio n Dela y Slow Dow nload Spee d Slow Uplo ad Spee d Averag e Durati on on Service Interac tion Respon se(s) Downl oad Speed (kbit/s) Upload Speed (kbit/s)
Description 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 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.
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.
Issue 01 (2013-07-15)
434
Parameter Date
Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
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 in the Task Result area. Select an executed GSM cell performance analysis task, right-click a result record in the Task Result area, and choose from the shortcut menu. l 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. , or right-click an NE and choose
Interface
The aggregated cell performance analysis results are displayed in tables, including the table of exception types, table of exception causes, and table of bottom N subscribers, terminals, or cells. Figure 3-38 shows the analysis result interface.
Issue 01 (2013-07-15)
435
No. 1
Description Click cause. to export analysis reports of all cells under each exception
NE navigation tree
l Upper part: Type a cell name in the Search area to quickly locate a cell. 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 reports related to the exception causes. In the navigation tree, you can right-click a cell and choose Further Analysis from the shortcut menu. The in-depth analysis result interface is displayed, showing all the abnormal call records under this cell. 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. Click the column header to resort this table. Right-click on the table and choose Save As from the shortcut menu to export this table.
Issue 01 (2013-07-15)
436
No. 4
Description Displays the number of reports and ratio under each exception cause of an exception type for the selected BSC or cell. This area is displayed accordingly with Area 5. l The first row displays the total number of reports under all exception causes, which is also the number of reports under the selected exception type. Starting from the second row, each row displays the number and ratio of reports under each exception cause. l Select an exception cause and click the icon to open the indepth analysis interface where you can view all abnormal call records caused by this exception cause.
Displays the number of reports related to bottom N users, terminal models, or cells 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.
Issue 01 (2013-07-15)
437
N/ A
Exc epti on Typ e Exc epti on Occ urre nce Tim es Rati o (%)
N/ A
N/ A
Classified analysis of exceptions under a specific exception type. For detailed description of the exception types, see the following.
[0, + )
Nu mb er
Proportion of the abnormal call records under a specific exception type in all the abnormal call records.
Issue 01 (2013-07-15)
438
N/ A
N/ A
Failed call setup due to certain exceptions when a terminal receives a Disconnect message after sending a Channel Request message. After sending a Channel Request message, a terminal receives an Alerting message, but fails to receive a Connect Acknowledge message due to certain exceptions.
N/ A
N/ A
Issue 01 (2013-07-15)
439
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Abnormal call release after a terminal gains access to the network. After a successful call setup, any of the following indicates an abnormal call release: 1. The terminal receives a Disconnect message that carries an abnormal cause (indicating that this is a nonNormal message). 2. The BSC receives a Clear command message from the MSC due to an abnormal call release triggered by the network or the terminal (or the peer-end terminal). 3. Call drops occur due to interBSC handovers. 4. Call drops occur due to intraBSC handovers. 5. The BSC releases channel resources abnormally. 6. The MSC releases channel resources abnormally.
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: Poor Um-interface quality 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.
Issue 01 (2013-07-15)
440
Ra nge
Un it
Description
Supported NE Version
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 (mobileoriginated) Long call access delay (mobileterminated) 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.
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 the source data subscription function.
N/ A
N/ A
Number of abnormal TA values and RACH levels when a terminal attempts to access the network. You can set the exception threshold by using the source data subscription function.
Issue 01 (2013-07-15)
441
Par am ete r Inc omi ng Har d Han dov er Fail ure Out goi ng Har d Han dov er Fail ure Inte rSys tem Out goi ng Han dov er Fail ure (Int raSys tem )
Ra nge
Un it
Description
Supported NE Version
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.
N/ A
N/ A
Number of failed outgoing hard handovers when a subscriber is using a specific service. Statistics on outgoing hard handovers are collected based on the source cell.
N/ A
N/ A
Number of failed outgoing interRAT handovers from the current GSM network (and the failures occur on the GSM network) when a subscriber is using a specific service.
Issue 01 (2013-07-15)
442
Par am ete r Inte rSys tem Inc omi ng Han dov er Fail ure (Int raSys tem )
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Number of failed call setups after a subscriber is handed over from a non-GSM network to a GSM network.
N/ A
N/ A
Number of times that a mobileoriginated subscriber attempts to access the network to use SMS service fails.
N/ A
N/ A
Number of times that a mobileterminated subscriber attempts to access the network to use SMS service fails.
Issue 01 (2013-07-15)
443
N/ A
N/ A
Number of times that a subscriber fails to gain access to the network when using a data service, namely, the number of times that no response to service interaction is made. 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]). Thresholds 1 and 2 for determining that no response to service interaction is made are internal algorithm parameters.
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. The service is abnormally interrupted due to a cell reselection that succeeds upon one attempt. The service is abnormally interrupted due to a cell reselection that succeeds after multiple attempts.
Issue 01 (2013-07-15)
444
Par am ete r Ab nor mal Ser vice Inte ract ion Del ay
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Any of the following serviceinteraction delay problems that might occur when a subscriber is using a data service. Service interaction response times out. The average duration for making a service interaction response is long. You can set the exception thresholds by using the source data subscription function.
N/ A
N/ A
Any of the following download rate problems that might occur when a subscriber is using a data service: Low download rate You can set the exception thresholds by using the source data subscription function.
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 You can set the exception thresholds by using the source data subscription function.
Issue 01 (2013-07-15)
445
N/ A
N/ A
Provides detailed algorithms that trigger handovers upon outgoing hard handover and outgoing interRAT handover (within the system) failures. The handover trigger algorithm is displayed only when exceptions occur on location group handovers. Cause of exceptions under a specific exception type.
N/ A
N/ A
[0, + )
Nu mb er
Proportion of a cause against the number of exceptions under the same exception type.
Issue 01 (2013-07-15)
446
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A N/ A
N/ A N/ A
Exceptions caused by other faults except poor Um-interface quality, terminal fault, system resource congestion, transmission fault, and CN fault. Call drops caused by failed handovers after a terminal gains access to the network and sends a Setup message.
N/ A
N/ A
Issue 01 (2013-07-15)
447
Par am ete r Call Dro p Due to Um Inte rfac e Pro ble ms Call Dro p Due to Tra nsm issi on Fau lt Call Dro p Due to CN Fau lt Pee r Call Dro p Call Dro p Due to Oth er Cau ses
Issue 01 (2013-07-15)
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Call drops caused by poor Uminterface quality after a terminal gains access to the network and sends a Setup message.
N/ A
N/ A
Call drops caused by transmission faults after a terminal gains access to the network and sends a Setup message.
N/ A
N/ A
Call drops caused by CN faults after a terminal gains access to the network and sends a Setup message.
N/ A
N/ A
Call drops caused by call drops of the peer-end terminal after a terminal gains access to the network and sends a Setup message. 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 access to the network and sends a Setup message.
N/ A
N/ A
448
Ra nge
Un it
Description
Supported NE Version
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 You can set the exception thresholds for the KPIs by using the source data subscription function. For description of the KPIs, refer to the description of source data subscription.
UL One Wa y Au dio
N/ A
N/ A
Uplink one-way audio event that occurs after a terminal gains access to the network and sends a Setup message. 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. Principles for detecting uplink oneway audio are as follows: The DSP in the TC of the BSC performs periodic statistics on the bad frame rate based on uplink TRAU frames. When the bad frame rate reaches a specified threshold, the BSS determines that a primary uplink one-way audio event occurs, and starts the mechanism for further confirming the occurrence of uplink one-way audio. During this process, the BSC sends a message to the BTS demanding that the BTS send a test TRAU frame to the TC. If the TC fails to receive a test TRAU frame from the BTS within a specified time period, one-way audio occurs on the uplink voice channel.
Issue 01 (2013-07-15)
449
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Downlink one-way audio event that occurs after a terminal gains access to the network and sends a Setup message. 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. Principles for detecting downlink one-way audio are as follows: The DSP in the DTRU of the BTS performs periodic statistics on the bad frame rate based on downlink TRAU frames. When the bad frame rate reaches a specified threshold, the BSS determines that a primary downlink one-way audio event occurs, and starts the mechanism for further confirming the occurrence of downlink one-way audio. During this process, the BSC sends a message to the TC demanding that the TC send a test TRAU frame to the BTS. If the BTS fails to receive a test TRAU frame from the TC within a specified time period, one-way audio occurs on the downlink voice channel.
Mut e Call
N/ A
N/ A
No-audio event that occurs after a terminal gains access to the network and sends a Setup message.
Issue 01 (2013-07-15)
450
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Uplink crosstalk event that occurs after a terminal gains access to the network and sends a Setup message. The crosstalk test can only detect crosstalk events related to the channels within the BSS (BTS<>TC) instead of those related on the Um and A interfaces. Principles for detecting uplink crosstalk are as follows: The DSP of the BTS inserts the unique identifier of a call into the free bit of each TRAU frame on the uplink voice channel. The DSP of the TC decodes all the unique call identifiers and checks their consistency. If inconsistency is detected among the unique call identifiers within the test period, uplink crosstalk occurs.
DL Cro ssta lk
N/ A
N/ A
Downlink crosstalk event that occurs after a terminal gains access to the network and sends a Setup message. The crosstalk test can only detect crosstalk events related to the channels within the BSS (BTS<>TC) instead of those related on the Um and A interfaces. Principles for detecting downlink crosstalk are as follows: The DSP of the TC inserts the unique identifier of a call into the free bit of each TRAU frame on the downlink voice channel. The DSP of the BTS decodes all the unique call identifiers and checks their consistency. If inconsistency is detected among the unique call identifiers within the test period, downlink crosstalk occurs.
Issue 01 (2013-07-15)
451
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Long delay for a mobile-originated terminal to gain access to the network. Call access delay (mobileoriginated) (s) The access duration for mobile-originated call spans from the time when the terminal sends a Channel Request message to the time when the terminal sends an Assignment Complete message. You can set the threshold for long call access delay (mobileoriginated) by using the source data subscription function.
N/ A
N/ A
Long delay for a mobileterminated terminal to gain access to the network. Call access delay (mobileterminated) (s) The access duration for mobile-terminated call spans from the time when the terminal sends a Channel Request message to the time when the terminal sends an Assignment Complete message. You can set the threshold for long call access delay (mobileterminated) by using the source data subscription function.
Issue 01 (2013-07-15)
452
Par am ete r Ove rlon g Call Co mpl etio n Del ay (Alt erin g) (M OC )
Ra nge
Un it
Description
Supported NE Version
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. 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). You can set the threshold for long call completion delay (mobileoriginated) by using the source data subscription function.
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). You can set the threshold for long call completion delay (mobileterminated) by using the source data subscription function.
Issue 01 (2013-07-15)
453
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Exception where a call lasts shortly after a mobile-originated subscriber gains access to the 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). You can set the short-call threshold by using the source data subscription function.
N/ A
N/ A
Exception where a call lasts shortly after a mobile-terminated subscriber gains access to the 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 by using the source data subscription function.
N/ A
N/ A
Abnormal value of the TA when a terminal sends a Channel Request message. You can set the exception threshold by using the source data subscription function.
Issue 01 (2013-07-15)
454
Par am ete r Ab nor mal RA CH Lev el on Acc ess No Ser vice Inte ract ion Res pon se
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Abnormal RACH level when a terminal sends a Channel Request message. You can set the exception threshold by using the source data subscription function.
N/ A
N/ A
Exception where no response to service interaction is made when a subscriber is using a data service. 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]). Thresholds 1 and 2 for determining that no response to service interaction is made are internal algorithm parameters.
Issue 01 (2013-07-15)
455
Par am ete r Las t Ser vice Inte rrup ted Due to Rou ting Are a Up date Ser vice Inte rrup tion Cau sed by Cell Res elec tion (Su cce ede d Aft er One Att em pt)
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
N/ A
N/ A
Exception where a data service is interrupted due to a cell reselection that succeeds upon one attempt.
Issue 01 (2013-07-15)
456
Par am ete r Ser vice Inte rrup tion Cau sed by Cell Res elec tion (Su cce ede d Aft er Mul tipl e Att em pts) Ser vice Inte ract ion Res pon se Tim eou t
Ra nge
Un it
Description
Supported NE Version
N/ A
N/ A
Exception where a data service is interrupted due to a cell reselection that succeeds after multiple attempts. You can compare the actual cell reselection duration (s) with the average service interruption duration caused by the cell reselection (namely, the average interval between two cell reselection attempts) to roughly determine whether a cell reselection succeeds upon one attempt or after multiple attempts. You can set the threshold for multiple cell reselection attempts by using the source data subscription function.
N/ A
N/ A
Long duration for making a service interaction response when a subscriber is using a data service. 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. Specific devices are equipped to directly detect whether the preceding duration or interval exceeds its specified threshold.
Issue 01 (2013-07-15)
457
Par am ete r Ove rlon g Ave rag e Dur atio n on Ser vice Inte ract ion Res pon se Lo w Do wnl oad Spe ed
Ra nge
Un it
Description
Supported NE Version
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 You can set the threshold by using the source data subscription function.
N/ A
N/ A
Low download rate when a subscriber is using a data service. Download rate (kbit/s) = Number of bytes transmitted by using the downlink PDU/Duration for the downlink PDU to complete transmitting the bytes You can set the threshold by using the source data subscription function.
N/ A
N/ A
Low upload rate when a subscriber is using a data service. Upload rate (kbit/s) = Number of bytes transmitted by using the uplink PDU/Duration for the uplink PDU to complete transmitting the bytes You can set the threshold by using the source data subscription function.
Issue 01 (2013-07-15)
458
N/ A
N/ A
Unique identifier that the system assigns to each bottom subscriber troubled with exceptions. Number of the exceptions that trouble a subscriber under the cause of a certain type of exception.
[0, + )
Nu mb er
N/ A
N/ A
Terminal model that is obtained by using the terminal type management function based on IMEI-TAC.
Issue 01 (2013-07-15)
459
Par am ete r Exc epti on Occ urre nce Tim es Rati o (%)
Ra nge
Un it
Description
Supported NE Version
[0, + ]
Nu mb er
Number of the exceptions that trouble a certain type of terminal under the cause of a certain type of exception.
N/ A
N/ A
The identity of a bottom problematic cell is in the following format: LAC: CI. Name of a bottom cell in which exceptions occur. Number of the exceptions that occur in a cell under the cause of a certain type of exception.
N/ A [0, + ]
N/ A Nu mb er
Issue 01 (2013-07-15)
460
Function Description
Network geographic observation displays the distribution of network coverage, traffic, and exceptions based on data collected from the live network. It replaces traditional drive tests (DTs) and addresses the problem that DTs fail to cover all areas, thereby providing telecom operators with cost-effective network evaluation and problem identification means. GSM network geographic observation supports network coverage geographic analysis, network traffic geographic analysis, and network event geographic analysis: 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 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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 461
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.
Application Scenarios
l Network optimization: By providing grid-level analysis on network coverage, traffic, and events at this stage, the system helps identify problems such as weak coverage, intra-system interference and improper network structure and then locates problematic cells through associated grid-cell analysis. This helps to greatly reduce DTs. After the addressed problems are solved, the system allows network optimization engineers to evaluate the network quality before and after the optimization. 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 monitoring and maintenance: By geographically displaying network events at this stage, the system helps network optimization engineers identify areas where exceptions such as call drops and handover failures occur and provides guidance for troubleshooting. Traditional network guarantee and routine problem locating use network performance KPIs to identify and analyze cell-level call drops and handover failures. Exceptions occurred in certain coverage areas of a cell might be ignored because users see only the average KPI values and, if telecom operators fail to pay attention to such exceptions, complaints will arise. By geographically displaying exceptions such as call drops and handover failures on the live network, the system helps network optimization engineers quickly identify areas where exceptions occur frequently. Then, in conjunction with functions such as cell performance analysis and the GIS, the engineers can further locate radio frequency (RF) causes so as to improve user experience of the entire network.
Function Principles
The data source of network geographic observation is the CHR and MR data on the NE side. Figure 3-39 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 3-23.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
462
Table 3-23 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
Issue 01 (2013-07-15)
463
So urc e M2 000
Purpose
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue a data query comma nd Return data query results Issue a task executio n comma nd
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
Issue 01 (2013-07-15)
464
So urc e eS AU
Purpose
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
<= 7 days
Check that you have applied for a valid license for GSM network geographic observation.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 465
Check that you have the operation rights to subscribe to GSM network geographic observation data upon login. You are advised to contact the administrator to turn on the data switch because the analysis data subscription function has a high security requirement.
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.
Issue 01 (2013-07-15)
466
Function 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.
Operation 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 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. You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the 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.
Prerequisites
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 467
l l l
Prerequisites
You have finished the preparation of network geographic observation, such as checking the operation rights, preparing the basic data, and so on. For details, see 3.8.2 Preparations for GSM Network Geographic Observation.
Process
Figure 3-40 shows the analysis process. Figure 3-40 Analysis process
Issue 01 (2013-07-15)
468
Table 3-25 Description of the network geographic observation process No. (1) Proced ure Check whether analysis data is integrat ed Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Choose Data Type > Network Analysis > GSM Network Geographic Observation Data(***). *** indicates the data type including MR, CHR-CS, and CHR-PS. 2. Specify the time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
(2)
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. Click the GSM 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. 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. Check the information in the Log Info area and ensure that the data source switch is turned on.
Issue 01 (2013-07-15)
469
No.
Description Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. Click the GSM tab in the Data Subscription Management window. 2. Select the NEs to be configured in the navigation tree. 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 Finish.
Reference
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Choose Data Type > Network Analysis > GSM Network Geographic Observation Data(***). *** indicates the data type including MR, CHR-CS, and CHR-PS. 2. Specify the time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
Issue 01 (2013-07-15)
470
No. (3)
Description Navigation path: Choose Theme Function > Network Analysis > GSM Network Geographic Observation in the navigation tree of the Analysis Task Management window. 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. 4. On the Select NE(s) tab page, select the NEs to be analyzed. Then, click Next. 5. Specify the time period. After the task is executed, the Nastar obtains the observation results for the specified time period. 6. Click Finish.
Reference l For details, see 2.7 Creating an Analysis Task. l For details about the parameter s, see Analysis Task Paramete rs.
(4)
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. 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.
l For details, see 2.8 Querying Analysis Results. l For details on the descriptio n of the window for showing analysis results, see 3.8.4 Interface Descripti on: GSM Network Geograp hic Observat ion.
Issue 01 (2013-07-15)
471
No. (5)
Description Navigation path: Click the icon on the button area in the upper left part of the Geographic observation window. 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.
Reference l For details, see 2.10 Exportin g Analysis Reports. l For details on the descriptio n of the window for showing analysis results, see 3.8.4 Interface Descripti on: GSM Network Geograp hic Observat ion.
Issue 01 (2013-07-15)
472
Description 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. Y indicates the uplink level.
Value Range X: an integer between 0 and 7. The default value is 6. Y: -110.0~0.0. The default value is -95.0.
Absolute Down Link RxLev between Main cell and Neighboring Cell (dB) < X Satisfy Cell Count >= Y X <Up Link RxLev(dBm) <=Y and Up Link RxQual>=P or M <Up Link RxLev(dBm) <=N and Up Link RxQual>=Q or Up Link RxLev(dBm) >Z and Up Link RxQual>=R
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. Defines the uplink interference threshold. 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.
X: an integer from 1 to 20. The default value is 5. Y: an integer from 1 to 6. The default value is 2.
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. 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 01 (2013-07-15)
473
Parameter X <Down Link RxLev(dBm) <=Y and Down Link RxQual >=P or M <Down Link Rxlex(dBm) <=N and Down Link ReQual >=Q or Down Link RxLev(dBm) >Z and Down Link RxQual >=R
Description Defines the downlink interference threshold. 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.
Value Range 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. 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 01 (2013-07-15)
474
Parameter information Parameter Select NE(s) Grid Resolution Settings Description Select BSC or Cell Group, and select the NEs to be analyzed in the navigation tree. 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.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time. 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. 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. The value of this parameter must not precede the end time of Date.
Time information of periodic task Param eter Start time Period Description Date for starting a task. Interval between periodic tasks. Value range: 1 to 7 Days. Note Start Time of a periodic task = Next time point + Delay by (hours) Time period of a periodic task: [Start Time of a periodic task - 1 x Period, Start Time of a periodic task The Next time point is related to Start time and Period. If you set Period to Day, the Next time point is 00 hours:00
475
Issue 01 (2013-07-15)
Description 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
Note minutes:00 seconds of the next day starting from Start time.
NOTE 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 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 14:00:00, Start time is 01/01/2013, Period is Day, and Delay by (hours) is 3, the Nastar immediately executes the task.
Time delayed for executing a task. Value range: 0 to 24. Unit: hour. If you select this parameter, it works the same as All Busy Time under Busy hours. You are not allowed to set this parameter.
Busy hours
If you set 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.
Navigation Path
Use either of the following methods to open the interface that displays GSM network geographic observation results: l l Select a finished GSM network geographic observation task and double-click a result record in the Task Result area. Select a finished GSM network geographic observation task, right-click a result record in the Task Result area, and choose Geographic Observation from the shortcut menu.
Interface
Figure 3-41 shows the interface that displays network geographic observation results on grid maps.
Issue 01 (2013-07-15)
476
NOTE
This section describes only the functions supported by GSM network geographic observation. For detailed operations of each function, see 2.2.3 Interface Description: Geographic Observation Results.
N o. 1
Issue 01 (2013-07-15)
477
N o. 2
Description 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
l Polygon Areas: enables you to analyze only a selected polygon in the Geographic Observation interface. You can save the cells in a polygon as a cell group. You can analyze multiple KPIs simultaneously based on a polygon. 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 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. 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\plugins\com.huawei.galaxy.geography.ui \style\config\style.
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).
Issue 01 (2013-07-15)
478
N o. 3
Description 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. l Displays analysis results in multiple windows. If you click , the Nastar divides the current window into multiple small windows with each small window displaying the analysis results of one KPI. The small windows are zoomed in, zoomed out, and moved simultaneously. If you click the icon again, the Nastar displays the original window. 4 Grid Details area Legend 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. 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. The Nastar distinguishes between directional and omnidirectional cells using different legends. You can change the legend for directional cells. The legend for omnidirectional cells is set the Nastar by default, and therefore you cannot change it. 6 Informatio n area The interface displays no information when it is opened. If you select a grid, the values of selected KPIs in this gird are displayed. If you select a site, information about the site is displayed. If you select a cell, information about the cell such as engineering parameters and longitude and latitude coordinates is displayed.
Issue 01 (2013-07-15)
479
UL Coverage Strength(G) DL Coverage Strength(G) UL Poor Coverage Low Quality (G) DL Poor Coverage Low Quality (G)
[-110,47] [-110,47]
dBm
BSC6900 V900R011C00 or later version BSC6900 V900R011C00 or later version BSC6900 V900R011C00 or later version
dBm
[0.00,1 00.00]
[0.00,1 00.00]
UL Interference Area(G)
[0.00,1 00.00]
Issue 01 (2013-07-15)
480
Unit %
Description The traffic map is rendered based on the percentage of the downlink interference MRs in all the MRs in the raster view. 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).
LAC Stability(G)
[0.00,1 00.00]
The traffic map is rendered based on the 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. The traffic map is rendered based on the 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.
[0.00,1 00.00]
Confidence Level(G)
[0.00,1 00.00]
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.
Issue 01 (2013-07-15)
481
[0,+)
Num ber
[0,+)
[0,+)
[0,+)
[0,+)
[0,+)
quality of VIP subscribers is ensured and the satisfaction of VIP subscribers is improved.This function can be used to quickly locate and resolve problems. Normally there is no way to avoid that some user data such as International Mobile Subscriber Identity (IMSI) will be used during the troubleshooting. However, this function provides an anonymous data processing method. You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected.
Function Scenarios
l During network monitoring, 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.
Function Description
VIP Report Analysis (GSM/UMTS/LTE/PS Core) The Nastar periodically collects statistics on and analyzes various user assurance KPIs of VIP subscribers and VIP groups, and generates different types of service assurance reports. l Generates KPI reports on the network, CS services, and PS services on the RAN side, and collects statistics on and analyzes the success rate and delay of each key procedure on the CN side. This helps you quickly learn the service usage of VIP subscribers or VIP groups. 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
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 483
Issue 01 (2013-07-15)
occurred in these areas. You can then solve the problem of service quality deterioration experienced by VIP subscribers in time if the problem is caused by a cell. l Generates KPI reports on the active servers for PS services. This helps you quickly locate the servers that VIP subscribers or VIP groups often visit and solve the problem of service quality deterioration caused by server problems in time. This function is available only for GSM.
VIP In-depth Analysis (GSM/UMTS/LTE/PS Core) This function allows you to retrieve and analyze the call history information of a VIP subscriber if the KPIs of the VIP subscriber deteriorates but the problem cannot be located or identified onsite. l 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 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 3-26.
Issue 01 (2013-07-15)
484
Table 3-26 Description of VIP all-signaling analysis Net wor k GS M Number of Supported VIP Subscribers 500 on the entire network. VIP subscribers are managed as Important VIP subscribers by using the VIP group management function. Supported Signaling Range 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. 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). UM TS 100 on the entire network. VIP subscribers are managed as Important VIP subscribers by using the VIP group management function. 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. Required NE Version 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. Function Display Mode 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.
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 all-signaling data, a 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.
Issue 01 (2013-07-15)
485
Number of Supported VIP Subscribers 500 on the entire network. VIP subscribers are managed as Important VIP subscribers by using the VIP group management function.
Supported Signaling Range Signaling messages on the S1-MME interface (3GPP specifications 36.423), X2 interface (3GPP specifications 36.413), and Uu interface (3GPP specifications 36.331). 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.
Required NE Version LTE3900 V100R008C00 or later; M2000 V200R013C00 or later; HSS9860 V900R008C01 or later. Note: You can analyze the key signaling procedures of common subscribers other than the 500 Important VIP subscribers only in LTE3900 V100R005C00SP C230 or later.
Function Display Mode 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.
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 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 486
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. On the PS Core network, the CHR data includes the SGSN/MME CHR data and the GGSN/SAE-GW CHR data.
Function Principles
Figure 3-42 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 3-27.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
487
Issue 01 (2013-07-15)
488
Table 3-27 Description of VIP analysis User Oper ation 1. Subscr ibe to basic data Scen e GSM / UMT S netw ork Proce dure Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd Upload raw data PS Core netw ork Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd Sour ce Nast ar Serv er Dest inati on eSA U Purpose
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 a basic data subscription command to the eSAU.
eSA U
M20 00
M20 00
BSC/ RNC
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
eSA U
To turn on the data source switch on the NE side. After a user enables the basic data subscription function (PS Core VIP analysis) on the Nastar client, the Nastar issues a basic data subscription command to the eSAU.
eSA U
M20 00
M20 00
SGS N/ MM E
To forward the MML command to the NE, requesting the NE to generate raw data.
Issue 01 (2013-07-15)
489
Scen e
Purpose
Issue a basic data subscri ption comma nd Issue a subscri ption comma nd Forwar d the subscri ption comma nd Upload raw data
eSA U
To turn on the data source switch on the NE side. After a user enables the basic data subscription function (LTE VIP analysis) on the Nastar client, the Nastar issues a basic data subscription command to the eSAU.
eSA U
M20 00
M20 00
eNod eB
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNod eB/ MM E
l To upload 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 transmission switch is enabled.
Issue 01 (2013-07-15)
490
Proce dure Issue an applica tion data subscri ption comma nd Deliver a dataprepro cessing task (direct) Upload prepro cessed data (direct)
Purpose
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 a data-processing command to the eSAU.
eSA U
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the datapreprocessing task.
SAU
eSA U
Issue an applica tion data subscri ption comma nd Deliver a dataprepro cessing task (direct) Upload prepro cessed data (direct)
Nast ar Serv er
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function (PS Core VIP analysis) on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eSA U
PS SAU
To deliver a data-preprocessing request to the PS SAU, requesting the PS SAU to start the datapreprocessing task.
PS SAU
eSA U
Issue 01 (2013-07-15)
491
Proce dure Issue an applica tion data subscri ption comma nd Deliver a prepro cessing task (direct) Upload prepro cessed data (direct)
Purpose
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function (LTE VIP analysis) on the Nastar client, the Nastar issues a data-processing command to the eSAU.
eSA U
LTE SAU
To deliver a data-preprocessing task to the LTE SAU, requesting the LTE SAU to start the datapreprocessing task.
LTE SAU
eSA U
To upload preprocessed data to the eSAU after obtaining the data from LTE SAU to Trace Server, and preprocessing .
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. To return data integrity check results to the Nastar server and display the results on the Nastar client. To deliver 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. To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server.
Nast ar Serv er
eSA U
Nasta r Serve r
Issue 01 (2013-07-15)
492
Scen e -
Sour ce -
Purpose
Number of analysis tasks to be created Period that can be analyzed (for periodic task) Time range of analysis data
l Once tasks <= 300, for all RATs. l Period tasks <= 60, for all RATs. 30 minutes, 1 to 24 hours, 1 to 7 days, and 1 week
l <= 7 days (for one-time task) l <= 30 days (for periodic task)
Before running a VIP analysis task, you must check and prepare the following information: l l l Checking the License Information and User Rights Preparing Basic Data Checking the Data Source Environment
Required rights (Security > Security Management > User) l Function operation rights Operation Rights > Operation > Nastar Subject Management > LTE FDD VIP Analysis Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM VIP analysis.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > PS Core VIP Analysis Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM VIP analysis.
GSM VIP analysis UMTS VIP analysis LTE TDD VIP analysis LTE FDD VIP analysis PS Core VIP analysis
l Function operation rights Have both involved licenses of VIP Analysis Operation Rights of combined analysis. l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM VIP analysis.
Issue 01 (2013-07-15)
495
Table 3-29 Required basic data of VIP analysis Data Type Config uratio n Data (Mand atory) Function The configuration data of the NE controlling the 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 which subscribers have handed over. Operation If the OSS information has been already configured, the Nastar automatically collects and imports the configuration data after the OSS and NE information is configured. You can also manually collect the configuration data before the specified time period starts. After the configuration data is imported, you can choose Maintenance > Data Maintenance Management to check whether the configuration data is available in the Nastar database. For detailed information about collecting, importing, and checking, see 2.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 NOTE of configuration data due to network adjustment. If you only perform the PS Expired configuration data may cause incorrect cell Core VIP analysis, you do information in the analysis result. For detailed not need the configuration operations, see Checking Engineering Parameters data. and Configuration Data. VIP Infor matio n (Mand atory) VIP information includes VIP user and IMSI information. Before subscribing to VIP analysis data, create a VIP group to centrally monitor the service of quality for multiple VIP users in one VIP group. For details, see 2.4.6 Managing VIP Groups or VIP Users (VIP Analysis).
NOTE Generally, you obtain the IMSI and MSISDN of a VIP user and enter them into the Nastar. If telecom operators have high requirements for user information security and the anonymous policy is enabled on the network where the Nastar is deployed, all user information such as IMSI, MSISDN, and IMEI contained in the analysis data will be encrypted. To protect the security-sensitive user information, the Nastar no longer allows you to enter the plaintext IMSI and MSISDN. In this situation, you need to contact telecom operators to obtain the encrypted IMSI. The Nastar does not support the encrypted MSISDN. Telecom operators can visit http://support.huawei.com and choose Software Center > Controlled Tool(Mini-tool Software) > Core Network Product Line > Wireless-OSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt user 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 2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key.
Issue 01 (2013-07-15)
496
Function 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.
Operation 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 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.
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. 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.
You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
For details, see 2.4.10 Setting a Mailbox and Address List for Sending Analysis Reports (Optional).
Issue 01 (2013-07-15)
497
For the required NE versions and M2000 versions of the signaling tracing analysis, refer to Table 3-26.
Table 3-30 Description of the data source environment Net wor k GSM Description
l GSM RAN CS analysis : Check that the matching M2000 version is V200R011C00 (or later), and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l GSM RAN PS analysis: Check that the matching M2000 version is V200R012C00 (or later), and the NE version is BSC6900 V900R014C00 (or later), and BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On the User Identity Information Reporting Switch (GSM) in Nastar Commissioning Guide.
UM TS
l Check that the matching M2000 version is V200R011C00SPC220 or later and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(UMTS) > Turning On the User Identity Information Reporting Switch (UMTS) in Nastar Commissioning Guide.
LTE
l Check that the matching M2000 version is M2000 V200R012C00SPC200 or later, the NE version is LTE3900 V100R005C00SPC320 (or later) or LTE3900 V100R008C00SPC020 (or later), and the MME on the CN must be provided by Huawei and the version is USN9810 V900R011C01SPC300 or later.
NOTE 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 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. 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. 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.
Issue 01 (2013-07-15)
498
Description
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 M2000 versions are consistent with the following information: NE version: USN9810 V900R011C01, USN9810 V900R011C02, USN9810 V900R012C00; UGW9811 V900R009C01, UGW9811 V900R009C02, UGW9811 V900R010C00. M2000 version: M2000 V200R011C01, M2000 V200R012C01, M2000 V200R013C00.
Prerequisites
You have finished the preparation of VIP analysis, such as checking the operation rights, preparing the basic data, and so on. For details, see 3.9.2 Preparations for VIP Analysis.
Procedure
Figure 3-43 shows the analysis process.
Issue 01 (2013-07-15)
499
Issue 01 (2013-07-15)
500
Table 3-31 Description of VIP analysis procedures No. Procedure Description Reference for Detailed Operatio ns 2.6 Checking the Integrity of Analysis Data
(1)
Navigation path: Choose Maintenance > Data Maintenance Management 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. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
501
No.
Procedure
Description
(2)
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the *** tab. *** indicates the network type. 2. In the left navigation tree, select the NEs to be configured. 3. On the Basic Subscription Settings tab page, click Set. 4. In the displayed Basic Subscription Settings dialog box, set 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 3.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.
l If you want to view the all signaling information when viewing deep analysis results, click select the interface about All Signaling. ,
l If you want to view the all signaling information when viewing deep analysis results, , For the GSM/UMTS network, click select the interface about All Signaling.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 502
No.
Procedure
Description
For the LTE network, choose the important level VIP users on the VIP analysis tab page of the application subscription function, and the system will prompt you to start the all signaling trace. 5. Click Confirm. Check that the data switch is successfully turned on by viewing the displayed information in the Log Info area. Subscribe to analysis data (application ) Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the *** tab. *** indicates the network type. 2. In the left navigation tree, select the NEs to be configured. 3. On the VIP analysis tab page, click ON. 4. Select the VIP user(s) and the NE(s). The level of a VIP user determines the type of data that a VIP user subscribe to. Define the user level through the VIP group management function. 5. Click Confirm. Check that data is successfully subscribed by viewing the displayed information in the Log Info area.
Issue 01 (2013-07-15)
503
No.
Procedure
Description
Reference for Detailed Operatio ns 2.6 Checking the Integrity of Analysis Data
Navigation path: Choose Maintenance > Data Maintenance Management 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. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
(3)
Navigation path: Choose Theme Function > User Assurance > VIP Analysis in the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click the VIP Analysis node. 2. Set the task name and task remarks. Click Next. 3. On the Analysis Type tab page, set the net type and the data type(s). 4. On the Select NE(s) tab page, select a NE. 5. On the VIP Group tab page, select the VIP group (s) to be analyzed. 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. 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.
l For details, see 2.7 Creati ng an Analysi s Task. l For details about the paramet ers, see Analysi s Task Param eters.
Issue 01 (2013-07-15)
504
No.
Procedure
Description
(4)
l For details, see 2.8 Queryi ng Procedure: Analysi 1. Double-click an analysis result of the task. s 2. In the displayed VIP Analysis window, click the Results User Level Results tab to view the VIP summary . analysis results. l For details View Navigation path: icon in the Deep Analysis on the analysis parameter of the VIP summary analysis results. descript results - VIP ion of Procedure: deep the analysis window icon in the Deep Analysis parameter of the 1. Click for VIP summary analysis results. showin NOTE g If the analysis object is VIP group, click icon to enter analysis the analysis result window that the analysis object is VIP results, user. If you want to enter the deep analysis window, you see need click icon again. 3.9.4 Refere 2. In the displayed Deep Analysis Result_*** nce for window, view the in-depth analysis results. VIP Navigation path: In the upper right area of the Analysis View Analysi Task Management window, select an analysis task in analysis s results - VIP the Finish state. In the lower right of the Task Result Interfa area, select a result record of the task. active cells ce. analysis Procedure: View analysis results - VIP summary analysis Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. 1. Double-click an analysis result of the task. 2. In the displayed VIP Analysis window, click the Network Level Results: Active Cell tab to view the analysis results of cells where VIP users are active.
Issue 01 (2013-07-15)
505
No.
Procedure
Description
View analysis results - VIP active servers analysis (only support the GSM network) View analysis results - VIP trend analysis
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click an analysis result of the task. 2. In the displayed VIP Analysis window, click the Network Level Results: Active Server tab to view the analysis results of servers where VIP users are active. Navigation path: In the upper right area of the Analysis Task Management window, select a periodic task in the Finish state. In the lower right of the Task Result area, select a result record of the task. 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 01 (2013-07-15)
506
No.
Procedure
Description
Reference for Detailed Operatio ns l For details, see 2.10 Export ing Analysi s Report s. l For details on the descript ion of the window for showin g analysis results, see Interfa ce Descri ption: VIP Analysi s/InDepth Analysi s/ Geogra phic Display .
(5)
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the button area. 2. Specify the export path and export content. 3. Click Save.
Issue 01 (2013-07-15)
507
Description 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 The name is unique and case-sensitive and cannot be empty. l Task Name must be named in Chinese or English. Otherwise, the function of distributing analysis results by emails is unavailable.
Type of an analysis task to be created. Description of the task. Value range: The name contains a maximum of 200 characters.
Parameter information Parameter Analysis Type Analysis Scene Description 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 Data Type 1 Set the RAT for an NE. The system supports the following RATs: GSM, UMTS, LTE FDD, LTE TDD. Both access methods can be chosen. Set the data type on the RAN side. l RAN CS Data Access: Analyzes the CS service based on the CS-related data on the RAN side. The LTE network does not involve this parameter. l RAN CS Data Access: Analyzes the PS service based on the PS-related data on the RAN side. Both access methods can be chosen.
NOTE If you set the analysis scene to PS Core, you do not need to set the data type, because it only supports the PS data on the PS Core.
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 01 (2013-07-15)
508
Description Click Select to select an NE. 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.
Indicates the name of a VIP group. Indicates the number of members in the VIP group. Indicates the description of a VIP group. Indicates the last time the VIP group information is updated.
Issue 01 (2013-07-15)
509
Description Indicates the RAT of a VIP group. Indicates the domain of an NE. Domains include signaling plane-CS, signaling plane-PS, signaling planeintegration. 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. 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 Criterion Threshold Indicates the name of a KPI indicator. The indicators are displayed on the analysis result window. Indicates the relationship between the KPI value and KPI abnormal 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.
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 users 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).
Process Threshold
Network Domain
Indicates the RAT of a VIP group. Indicates the domain of an NE. Domains include signaling plane-CS, signaling plane-PS, signaling planeintegration.
Issue 01 (2013-07-15)
510
Description 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. 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 process threshold. The threshold is based on the process of obtaining the final values of KPI indicators. Indicates the relationship between the KPI value and KPI abnormal threshold. Indicates the abnormal threshold of a KPI. In the analysis report of the corresponding task, if the KPI value of a subscriber reaches the threshold, this KPI is considered as a problematic KPI or deteriorating KPI. Click the unit and enter the KPI abnormal threshold. This parameter can be empty. That is, no threshold value is provided.
Criterion Threshold
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time.
Issue 01 (2013-07-15)
511
Parameter Delay
Description 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. The value of this parameter must not precede the end time of Date.
Time information of periodic task Param eter Start time Period Description Date for starting the task. Interval between periodic tasks. 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. Value range: 0 to 9999 Delay by (hours) Whole day Time delayed for executing a task. Value range: 0 to 24. Unit: hour. If this parameter is set, it works the same as All Busy Time under Busy hours. You are not allowed to set this parameter. Note Start Time of a periodic task = Next time point + Delay by (hours) Time period of a periodic task: [Start Time of a periodic task - 1 x Period, Start Time of a periodic task The Next time point is related to Start time and Period. l If you set Period to Minute, the Next time point is 00 seconds of the next minute starting from the current server time (minutelevel). For example, if the current server time is 01:10, the Next time point is 02:00 starting from Start time. l If you set Period to Hour, the Next time point is 00 minutes:00 seconds of the next hour starting from the current server time (hour-level). For example, if the current server time is 14:01:10, the Next time point is 15:00:00 starting from Start time. l If you set Period to Day, the Next time point is 00 hours:00 minutes:00 seconds of the next day starting from Start time. l If you set Period to Week, the Next time point is 00 hours:00 minutes:00 seconds of the eighth day starting from Start time.
Issue 01 (2013-07-15)
512
Description 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.
Note
NOTE 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 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 14:00:00, Start time is 01/01/2013, Period is Day, and Delay by (hours) is 3, the Nastar immediately executes the task.
Parameters about sending the analysis report Parameter Sendin g Analysi s Reports Setting Automatically send analysis reports via emails Target email Email subject Description After you select this option, the system delivers the exported VIP analysis result file to the mailboxes of the specified users.
Indicates the recipient's mailbox. Click Select. In the displayed Email dialog box, set user mailboxes. 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.
Issue 01 (2013-07-15)
513
Parameter Attachment
Description 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 reports by the email directly. l If the actual attachment is larger than the configured threshold, you can obtain the analysis reports by the FTP. Obtain the FTP information. The information will be sent to you by the email. Includes: IP address of the Nastar server (if the hardware is ATAE, the IP address is the one of the master board), FTP user and password, port number, and the analysis report path ( the default path is /export/home/sysm/ nastar/report). Prepare the tool that supports sftp for downloading the analysis reports. The Huawei supports the psftp tool. The path and the operation of the psftp tool is referred to FAQs > FAQs About the SUSE Linux Operating System > How Do I Transfer Data by Using the PSFTP Client? in the Nastar Commissioning Guide.
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.
Open the interface that displays the results of VIP analysis (in-depth): On the User Level Results tab page of VIP analysis result interface, If the table displays the counter overview information by group, click in the front
of each row, or click the counter value underlined in red (for example, ) directly. The tab page for the counter overview information by user is displayed. You can view the counter value for each user in the group. In such a case, click in the front of each row, or click the counter value underlined
in red (for example, ) directly. In-depth analysis of selected counters is started. For details, see 3.10.4 Reference for Complaint Analysis Support Interface. l Open the geographic display interface: On the button area of VIP analysis result interface, click .
Main Window
Figure 3-44 shows the VIP analysis results window. Figure 3-44 VIP analysis interface (example for a GSM network)
Issue 01 (2013-07-15)
515
No. 1
Parameter Description Button area The buttons provide navigation paths to the following three functions. l : Exports VIP analysis summary reports. 1. Click , a dialog box that provides personal data disclaimer will be displayed, reminding you of the illegality if you possess the personal data. Click OK. 2. On the displayed dialog box, set the result (Exception or ALL), service type, and report type. Click Next. 3. Set the report save path and the folder name, click Save to export the analysis reports. All the exported reports are contained in a folder named VIP Analysis_Name of analysis task_YYYYMMDDHHMMSS by default. VIP analysis reports are named following the format of Number Report type_Report categories 1 + Report categories 2 + Number_Service type.csv. Report categories 1 indicates the analysis object, such as the group and user of the user-level analysis. Report categories 2 indicates the analysis result categories, such as counter overview information table (KPI) and active cell information table (cell) of the user-level analysis. For example, 01 User Level Results_groupKPI00_RAN NET.csv indicates the counter overview information table of the user-level analysis, according the analysis object is group, and the service type is RAN NET. l : Displays the VIP analysis results geographically. For details, see Geographic Display Interface. l : Starts VIP trend analysis. Only periodical tasks support trend analysis. For details, see Interface Description: VIP Trend Analysis.
Issue 01 (2013-07-15)
516
No. 2
Parameter Description 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.
Issue 01 (2013-07-15)
517
No. (1)
Parameter
Description
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)
(3)
Counter set Contains a counter set to be analyzed. selection area The Nastar defines a default counter set by analysis scenario. 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
(4)
underlined in red (for example, ) directly. The tab page for the counter overview information by user is displayed. You can view the counter value for each user in the group. l In such a case, click in the front of each row, or click the counter
value underlined in red (for example, ) directly. In-depth analysis of selected counters is started. For details, see 3.10.4 Reference for Complaint Analysis Support Interface. (5) Active cell information table Displays active cells of a selected VIP user object.
Issue 01 (2013-07-15)
518
No. (6)
Parameter
Description
Active server Displays active servers of a selected VIP user object. It is only information supported by the GSM network. table
No. (1)
Parameter
Description
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 01 (2013-07-15)
519
No. (2)
Parameter
Description
NOTE The RAN-CS and RAN-PS types cannot be chosen at the same time.
(3)
Counter set Contains a counter set to be analyzed. selection area The Nastar defines a default counter set by analysis scenario. Counter overview information table Active VIP subscriber information table Lists all counter values in different applications for the selected NE object based on the selected counter set.
(4)
(5)
Issue 01 (2013-07-15)
520
No. (1)
Description 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) Service type selection area Select a service type to be viewed.
NOTE Only the RAN-PS service is supported.
(3)
Contains a counter set to be analyzed. The Nastar defines a default counter set by analysis scenario.
(4)
Counter overview Lists all counter values in different applications for the selected information table analysis object based on the selected counter set. Active VIP Displays VIP subscribers for selected server objects. subscriber information table
(5)
Issue 01 (2013-07-15)
521
No. (1)
Description Navigation path for basic operations in the Geographic Observation window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
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 01 (2013-07-15)
522
No. (3)
(4) (5)
This area is empty for VIP analysis. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the icons in area 3.
(6)
Information 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.
VIP trend analysis is supported by the GSM, UMTS, LTE, and PS Core network.
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 when monitoring and optimizing VIP KPIs. Figure 3-49 shows the VIP trend analysis results.
Issue 01 (2013-07-15)
523
No. 1
Parameter Description 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 01 (2013-07-15)
524
No. 2
Parameter Description Area for setting filtering criteria Selects a VIP user or VIP group whose trend analysis is to be analyzed. The options 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.
Select the service type whose trend analysis is to be viewed. Only one service type can be selected each time.
Issue 01 (2013-07-15)
525
No. 5
Parameter Description Trend analysis chart Displays the trend analysis charts of multiple counters for a selected subscriber during a time segment. l Displays user objects and time dimension 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. 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.
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.
The trend analysis modes are as follows: l Real-time monitoring 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.
Issue 01 (2013-07-15)
526
Common
Paramet er Deep Analysis Ran ge N/A Unit Description Supported NE Version BSC6900 V900R013 C00 or later version
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. 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
BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version
User ID
N/A
N/A
ID of a VIP subscriber. Query the ID of a VIP subscriber using VIP group management.
Alias
N/A
N/A
Alias of a VIP subscriber. Query the alias of a VIP subscriber using VIP group management.
IMEITAC
N/A
International mobile equipment identity-type allocation code (IMEI-TAC) of the terminal used by a VIP subscriber.
Terminal Model
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. Service type for a following counter.
Service Type
N/A
N/A
[0, +)
Numb er
Number of abnormal counters whose values exceed the predefined thresholds that you set when creating a task. Number of reports generated when a subscriber accesses the network.
[0, +)
Numb er
Issue 01 (2013-07-15)
527
RAN-CS/NET/Accessibility Evaluation
Para meter Acces s Reque sts (IntraRAT) Acces s Failur es (IntraRAT) Acces s Reque sts (InterRAT) Acces s Failur es (InterRAT) Avera ge TA on Acces s Abnor mal TAs on Acces s Ran ge [0, +) Unit Number Description Number of access requests that a VIP subscriber initiates to access the network from a cell in the current system. Supported NE Version BSC6900 V900R013C00 or later version
[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.
[0, +)
Number
Number of access requests that a VIP subscriber initiates to access the network from a cell in another system.
[0, +)
Number
Number of access failures that a VIP subscriber experiences during the process of accessing the network from a cell in another system.
[0,63 ]
N/A
Average TA value when a VIP subscriber initiates channel setup requests for accessing the network.
[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.
Issue 01 (2013-07-15)
528
Para meter Ratio of Abnor mal TAs on Acces s Avera ge RAC H Level on Acces s Abnor mal RAC H Levels on Acces s Ratio of Abnor mal RAC H Levels on Acces s
Unit %
Description Proportion of abnormal TA values when a VIP subscriber initiates channel setup requests for accessing the network. Proportion of abnormal TA values = Number of abnormal TA values/Number of all TA values x 100%.
[-110 ,-47]
dBm
Average RACH level when a VIP subscriber initiates channel setup requests for accessing the network.
[0, +)
Number
Number of times that the RACH level is abnormal when a VIP subscriber initiates channel setup requests for accessing the network. Set the exception threshold when you create a task.
[0.00, 100.0 0]
Proportion of abnormal RACH levels when a VIP subscriber initiates channel setup requests for accessing the network. Proportion of abnormal RACH levels = Number of abnormal RACH levels/ Number of all RACH levels x 100%.
Issue 01 (2013-07-15)
529
RAN-CS/NET/Retainability Evaluation
Para mete r Relea ses (Intra RAT) Abno rmal Relea ses (Intra RAT) Relea ses (Inter RAT) Abno rmal Relea ses (Inter RAT) Rang e [0, +) Unit Description Supported NE Version BSC6900 V900R013C 00 or later version
Numb er
Number of times that a VIP subscriber releases all services in the current system. Number of releases (intra-RAT) = Access requests (intra-RAT) Access failures (intraRAT)
[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.
[0, +)
Numb er
Number of times that a VIP subscriber releases all services in another system. Number of releases (inter-RAT) = Access requests (inter-RAT) Access failures (interRAT)
[0, +)
Numb er
Number of times that a VIP subscriber abnormally releases all services successfully accessed from another system. 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.
RAN-CS/NET/Mobility Evaluation
Paramet er Hard Handover Requests Hard Handover Failures Hard Handover Success Times Range [0,+) Unit Num ber Num ber Num ber Description Number of hard handover requests that a VIP subscriber initiates. Number of hard handover failures that a VIP subscriber experiences. Number of times that a VIP subscriber successfully initiates a hard handover. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
[0,+)
Issue 01 (2013-07-15)
530
Paramet er InterRAT Outgoing Handover Requests InterRAT Outgoing Handover Failures (Normal Release) InterRAT Outgoing Handover Failures (Abnorm al Release) InterRAT Incoming Handover Requests InterRAT Incoming Handover Failures
Range [0,+)
Description 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. Number of times that an outgoing inter-RAT handover from a GSM network is triggered during a service but the handover fails and the VIP subscriber then is handed back over to the GSM network. Number of times that call drops occur during an outgoing inter-RAT handover from a GSM network during a service.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Number of times that a handover from a non-GSM cell to a GSM cell is triggered during a service.
[0,+)
Num ber
Number of times that a handover from a non-GSM cell to a GSM cell fails during a service.
RAN-CS/Call/Accessibility Evaluation
Param eter Total Call Setup Reques ts Ran ge [0, +) Unit Numb er Description Number of call setup requests that a VIP subscriber initiates to access the network and initiate a call. That is, the number of Channel Request messages from a VIP subscriber after the BSC obtains the IMSI correctly. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
531
Ran ge [0, +)
Unit Numb er
Description Number of call setup failures that a VIP subscriber experiences during the process of accessing the network and initiating a call. The call setup process spans from the Channel Request message to the Altering message.
Abnor mal Release Before Call Compl etion Call Setup Succes s Times
[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. The process before call setup spans from the Channel Request message to the Connect Acknowledge message.
[0, +)
Numb er
Number of successful call setups when a VIP subscriber accesses the network and initiates a call. The call setup process spans from the Channel Request message to the Alerting message.
[0, +)
Numb er
Number of successful call completions (Alerting) when a VIP subscriber accesses the network and initiates a call. The call completion (Alerting) process spans from the Channel Request message to the Altering message.
[0, +)
Numb er
Number of successful call completions (Connect Ack) after a subscriber accesses the network and initiates a call. The call completion process (Connect Ack) spans from the Channel Request message to the Connect Acknowledge message.
Call completion rate (Alerting) when a VIP subscriber accesses the network and initiates a call. Call completion rate (Alerting) = Number of successful call completions (Alerting)/ Number of call setup requests x 100%
Issue 01 (2013-07-15)
532
Unit %
Description Call completion rate (Connect Ack) when a VIP subscriber accesses the network and initiates a call. Call completion rate (Connect Ack) = Number of successful call completions/ Number of call setup requests x 100%
RAN-CS/Call/Retainability Evaluation
Parame ter Call Setup Success Times Rang e [0, +) Unit Num ber Description Number of successful call setups when a VIP subscriber accesses the network and initiates a call. The call setup process spans from the Channel Request message to the Alerting message. [0, +) Num ber Same as the related counter in RAN/CS/ Call/Accessibility Evaluation. BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
533
Rang e [0, +)
Description Number of times that the call is abnormally released when a VIP subscriber accesses the network and initiates a call. After a successful call setup, any of the following indicates an abnormal call release: 1. The Disconnect message is called an abnormal one. 2. The BSS receives the Clear Command message from the MSC and the abnormal call release is caused by the network or the calling (or called) VIP subscriber. 3. An outgoing inter-BSC handover fails. 4. An intra-BSC handover fails. 5. The BSC releases the channel resources abnormally. 6. The MSC releases the channel resources abnormally.
[0.00, 100.00 ]
Abnormal call release rate when a VIP subscriber accesses the network and initiates a call. Abnormal call release rate = Number of abnormal call releases/Number of successful call completions (Connect Ack) x 100%
Issue 01 (2013-07-15)
534
Parame ter Average Access Delay (MOC) Overlon g Access Delays (MOC)
Ran ge [0, +)
Unit Second
Description Average access delay upon successful call initiation (mobile-originated call). Average access delay = Sum of access delays/Number of access delays
[0, +)
Numbe r
Number of times that the access delay is overlong upon successful call initiation (mobile-originated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong access delays upon successful call initiation (mobileoriginated call). Proportion of overlong access delays = Number of overlong access delays/ Number of access delays x 100%
[0, +)
Numbe r
Number of times that the access delay is overlong upon successful call initiation (mobile-terminated call). Access delay = Time when the Assignment Complete message is generated Time when the Channel Request message is generated
[0, +)
Second
Average access delay upon successful call initiation (mobile-terminated call). Average access delay = Sum of access delays/Number of access delays
[0, +)
Numbe r
Number of times that the access delay is overlong upon successful call initiation (mobile-terminated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong access delays upon successful call initiation (mobileterminated call). Proportion of overlong access delays = Number of overlong access delays/ Number of access delays x 100%
Issue 01 (2013-07-15)
535
Parame ter Times of Call Complet ion Delay (Alertin g) (MOC) Average Call Complet ion Delay (Alertin g) (MOC) Overlon g Call Complet ion Delays (Alertin g) (MOC) Ratio of Overlon g Call Complet ion Delays (Alertin g) (MOC) Average Call Complet ion Delay (Connec t Ack) (MOC)
Ran ge [0, +)
Unit Numbe r
Description Number of times that the completion (Alerting) delay is overlong upon successful call initiation (mobileoriginated call). The call completion (Alerting) process spans from the Channel Request message to the Altering message.
[0, +)
Second
Average call completion (Alerting) delay upon successful call initiation (mobile-originated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
[0, +)
Numbe r
Number of times that the call completion (Alerting) delay is overlong upon successful call initiation (mobileoriginated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Alerting) delays upon successful call initiation (mobile-originated call). Proportion of overlong call completion delays = Number of overlong call completion (Alerting) delays/Number of call completion delays x 100%
[0, +)
Second
Average call completion (Connect Ack) delay upon successful call initiation (mobile-originated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
Issue 01 (2013-07-15)
536
Parame ter Overlon g Call Complet ion Delays (Connec t Ack) (MOC) Ratio of Overlon g Call Complet ion Delays (Connec t Ack) (MOC) Times of Call Complet ion Delay (Alertin g) (MTC) Average Call Complet ion Delay (Alertin g) (MTC) Overlon g Call Complet ion Delays (Alertin g) (MTC)
Ran ge [0, +)
Unit Numbe r
Description Number of times that the call completion (Connect Ack) delay is overlong upon successful call initiation (mobile-originated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Connect Ack) delays upon successful call initiation (mobile-originated call). Proportion of overlong call completion delays = Number of overlong call completion delays/Number of call completion delays x 100%
[0, +)
Numbe r
Number of times that the call completion (Alerting) delay is overlong upon successful call initiation (mobileterminated call). The call completion (Alerting) process spans from the Channel Request message to the Alerting message.
[0, +)
Second
Average call completion (Alerting) delay upon successful call initiation (mobile-terminated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
[0, +)
Numbe r
Number of times that the call completion (Alerting) delay is overlong upon successful call initiation (mobileterminated call). Set the exception threshold when you create a task.
Issue 01 (2013-07-15)
537
Parame ter Ratio of Overlon g Call Complet ion Delays (Alertin g) (MTC) Average Call Complet ion Delay (Connec t Ack) (MTC) Overlon g Call Complet ion Delays (Connec t Ack) (MTC) Ratio of Overlon g Call Complet ion Delays (Connec t Ack) (MTC) Average Call Duration (MOC)
Unit %
Description Proportion of overlong call completion (Alerting) delays upon successful call initiation (mobile-terminated call). Proportion of overlong call completion delays = Number of overlong call completion delays/Number of call completion delays x 100%
[0, +)
Second
Average call completion (Connect Ack) delay upon successful call initiation (mobile-terminated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
[0, +)
Numbe r
Number of times that the call completion (Connect Ack) delay is overlong upon successful call initiation (mobile-terminated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Connect Ack) delays upon successful call initiation (mobile-terminated call). Proportion of overlong call completion delays = Number of overlong call completion delays/Number of call completion delays x 100%
[0, +)
Second
Average duration of successful calls for the mobile-originated party. 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
Issue 01 (2013-07-15)
538
Ran ge [0, +)
Unit Numbe r
Description Number of short calls for the mobileoriginated party during a successful call. 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. 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).
[0.00 , 100.0 0]
Average duration of successful calls for the mobile-originated party. 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
[0, +)
Second
Average duration of successful calls for the mobile-terminated party. 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
Issue 01 (2013-07-15)
539
Ran ge [0, +)
Unit Numbe r
Description Number of short calls for the mobileterminated party during a successful call. 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. 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).
[0.00 , 100.0 0]
Proportion of short calls for the mobileterminated party during a successful call. Proportion of short calls = Number of short calls/Number of calls with valid call durations x 100%
Issue 01 (2013-07-15)
540
Ran ge [0, +)
Description Number of times that one-way audio occurs in the downlink during calls. 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 Um and A interfaces. Principle for detecting one-way audio occurs in the downlink: The DSP in the DTRU of the BTS performs periodic statistics on the bad frame rate based on downlink TRAU frames. When the bad frame rate reaches the predefined threshold, the BSS determines that primary one-way audio occurs in the downlink and starts the mechanism for confirming the occurrence of primary one-way audio in the downlink. During this process, the BSC sends a message to the TC demanding that the TC send a test TRAU frame to the BTS. If the BTS fails to receive the test TRAU frame from the TC within a specified time period, one-way audio occurs on the downlink voice channel.
Proportion of successful call setups where one-way audio occurs in the downlink in all successful call setups. Proportion of successful call setups where one-way audio occurs in the 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%
Issue 01 (2013-07-15)
541
Ran ge [0, +)
Description Number of times that one-way audio occurs in the uplink during calls. 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 Um and A interfaces. Principle for detecting one-way audio in the uplink: The DSP in the TC of the BSC performs periodic statistics on the bad frame rate based on uplink TRAU frames. When the bad frame rate reaches the predefined threshold, the BSS determines that primary 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.
Proportion of successful call setups where one-way audio occurs in the uplink in all successful call setups. Proportion of successful call setups where one-way audio occurs in the uplink in all successful call setups = Number of times that one-way audio occurs in the uplink/Number of successful call setups (Connect Ack) x 100%
[0, +)
Num ber
Number of times that no audio occurs in both the uplink and downlink during calls.
Issue 01 (2013-07-15)
542
Unit %
Description Proportion of successful call setups where one-way audio occurs in both the uplink and downlink in all successful call setups. Proportion of successful call setups where one-way audio occurs in both the uplink and downlink in all successful call setups = Number of successful call setups where one-way audio occurs in both the uplink and downlink/Number of successful call setups (Connect Ack) x 100%
[0, +)
Num ber
Number of times that crosstalk occurs in the downlink during calls. 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.
Proportion of successful call setups where crosstalk occurs in the downlink in all successful call setups. Proportion of successful call setups where crosstalk occurs in the downlink in all successful call setups = Number of successful call setups where crosstalk occurs in the downlink/Number of successful call setups (Connect Ack) x 100%
Issue 01 (2013-07-15)
543
Ran ge [0, +)
Description Number of times that crosstalk occurs in the uplink during calls. 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 uplink crosstalk: The DSP of the BTS inserts the unique identifier of a call into the free bits of uplink speech TRAU frames. The DSP of the TC decodes the unique call identifier and checks its consistency. If inconsistency is detected within the test period, crosstalk occurs in the uplink.
Proportion of successful call setups where crosstalk occurs in the uplink in all successful call setups. Proportion of successful call setups where crosstalk occurs in the uplink in all successful call setups = Number of successful call setups where crosstalk occurs in the uplink/Number of successful call setups (Connect Ack) x 100%
Average value of downlink HQIs after the call setup is successful. 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 reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008 version: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
Issue 01 (2013-07-15)
544
Ran ge [0, +)
Description Number of times that the uplink HQI is poor after the call setup is successful. Set the exception threshold when you create a task.
Average value of uplink high quality indicators (HQIs) after the call setup is successful. 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 reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008 version: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
[0, +)
Num ber
Number of times that the uplink HQI is poor after the call setup is successful. Set the exception threshold when you a create task.
[1.00 , 5.00]
N/A
Average value of uplink voice quality BSC6900 indicators (VQIs) during calls. V900R013C00 or later version 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
Issue 01 (2013-07-15)
545
Parame ter Poor Uplink VQI Times Average Downlin k Level Average Uplink Level Average Downlin k Quality Average Uplink Quality Downlin k Noise Occurre nce Times Downlin k Noise Ratio
Ran ge [0, +)
Description Number of times that the uplink VQI is poor during calls. Set the exception threshold when you create a task.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,7]
N/A
[0, +)
Num ber
Number of times that noise occurs in the downlink during calls, which is detected by the BSC.
Proportion of successful call setups where noise occurs in the downlink in all successful call setups. Proportion of successful call setups where noise occurs in the downlink in all successful call setups = Number of successful call setups where noise occurs in the downlink/Number of successful call setups (Connect Ack) x 100%
[0, +)
Num ber
Number of times that noise occurs in the uplink during calls, which is detected by the BSC.
Issue 01 (2013-07-15)
546
Unit %
Description Proportion of successful call setups where noise occurs in the uplink in all successful call setups. Proportion of successful call setups where noise occurs in the uplink in all successful call setups = Number of successful call setups where noise occurs in the uplink/Number of successful call setups (Connect Ack) x 100%
RAN-CS/SMS/Accessibility Evaluation
Param eter Call Setup Reques ts (MOC) Call Setup Failure s (MOC) Call Setup Succes s Rate (MOC) Call Setup Reques ts (MTC) Call Setup Failure s (MTC) Range [0,+) Unit Num ber Description Number of setup requests that the mobile-originated party initiates to use the SMS service. Supported NE Version BSC6900 V900R013C00 or later version
[0,+)
Num ber
Number of call setup failures that the mobile-originated party experiences during the process of attempting to use the SMS service. Proportion of successful setup requests that mobile-originated party initiates to use the SMS service.
[0.00,1 00.00]
[0,+)
Num ber
Number of setup requests that the mobile-terminated party initiates to use the SMS service.
[0,+)
Num ber
Number of call setup failures that the mobile-terminated party experiences during the process of attempting to use the SMS service.
Issue 01 (2013-07-15)
547
Unit %
Description Proportion of successful call setup requests that the mobile-terminated party initiates to use the SMS service.
RAN-PS/PS/General Evaluation
Parame ter Access Failures Total Reports of Access Failure Count > 0 Abnorm al Proporti on of Access Failure Count > 0 Service Interrupt ions Total Reports of Service Interrupt ion Count > 0
Issue 01 (2013-07-15)
Description See Access Failures in RAN-PS/PS/ Accessibility Evaluation. Indicates the number of the measurement reports that the access failure count exceeds 0.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0,10 0]
Indicates the proportion of the total measurement reports that the access failure count exceeds 0.
[0, +) [0, +)
Numb er Numb er
See Service Interruptions in RANPS/PS/Retainability Evaluation. Indicates the number of the measurement reports that the service interruption count exceeds 0.
548
Parame ter Abnorm al Proporti on of Service Interrupt ion Count > 0 Abnorm al Service Interacti on Delays Total Reports of Abnorm al Service Interacti on Latency Count > 0 Abnorm al Proporti on of Abnorm al Service Interacti on Latency Count > 0 Downloa ds at Low Rate
Ran ge [0,10 0]
Unit %
Description Indicates the proportion of the total measurement reports that the service interruption count exceeds 0.
[0, +)
Numb er
[0, +)
Numb er
Indicates the number of the measurement reports that the abnormal service interaction latency count exceeds 0.
[0,10 0]
Indicates the proportion of the total measurement reports that the abnormal service interaction latency count exceeds 0.
[0, +)
Numb er
Issue 01 (2013-07-15)
549
Parame ter Abnorm al Proporti on at Low Downloa d Rate Uploads at Low Rate Abnorm al Proporti on at Low Upload Rate
Ran ge [0,10 0]
Unit %
Description Indicates the proportion of the total measurement reports that the download rate is low.
[0, +) [0,10 0]
Numb er %
See Uploads at Low Rate in RANPS/PS/Service Evaluation for Rate. Indicates the proportion of the total measurement reports that the upload rate is low.
RAN-PS/PS/Accessibility Evaluation
Parame ter Access Failures Rang e [0, +) Unit Numb er Description Number of access failures that a VIP subscriber experiences during the process of using a data service. 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. Attach Requests [0, +) Numb er Number of Attach Request messages that a VIP subscriber sends during the whole process of using a data service. BSC6900 V900R013C01 or later version Supported NE Version BSC6900 V900R013C01 or later version
Issue 01 (2013-07-15)
550
Rang e [0, +)
Unit Numb er
Description Number of Attach Fail messages that a VIP subscriber receives during the process of using a data service. 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. Number of Attach Fail messages = Number of Attach Request messages Number of Attach Accept messages
[0, +) [0, +)
Numb er Numb er
Number of PDP Active Request messages that a VIP subscriber sends during the process of using a data service. Number of PDP Active Fail messages that a VIP subscriber receives during the process of using a data service. 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. Number of Attach Fail messages = Number of PDP Active Request messages Number of PDP Active Accept messages
Authenti cation and Cipherin g Requests Authenti cation and Cipherin g Failures
[0, +)
Numb er
Number of authentication and ciphering requests that a VIP subscriber receives during the process of using a data service.
[0, +)
Numb er
Number of authentication and ciphering failures that a VIP subscriber receives during the process of using a data service.
Issue 01 (2013-07-15)
551
Rang e [0, +)
Unit Numb er
Description Number of times that no response to service interaction is made. 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. (A = Number of times that the uplink PDU carries data but the downlink PDU does not). The exception thresholds 1 and 2 for the response to service interaction are internal algorithm parameters.
RAN-PS/PS/Retainability Evaluation
Parame ter Service Interrupt ions Rang e [0, +) Unit Numb er Description Number of service interruptions that a VIP subscriber experiences during the process of using a data service. Number of service interruptions = Number of service interruptions due to cell reselection + Number of service interruptions due to routing area update Interrupt ions Due to Cell Reselect ion [0, +) Numb er Number of service interruptions that a VIP subscriber experiences during the process of using a data service due to cell reselection. The parameter is also referred to as the number of cell reselections. [0, +) Secon d Mean time between cell reselections during the process for a VIP subscriber to use a data service. This parameter is also referred to as the average interval between cell reselections. BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version Supported NE Version BSC6900 V900R013C01 or later version
Issue 01 (2013-07-15)
552
Rang e [0, +)
Unit Numb er
Description Number of times that the cell reselection interval is overlong during the process for a VIP subscriber to use a data service. If the time interval is above the threshold for overlong cell reselection, the cell reselection interval is overlong. Set the threshold when you create a task.
[0, +)
Numb er
Number of service interruptions that a VIP subscriber experiences during the process of using a data service due to routing area update.
Issue 01 (2013-07-15)
553
Rang e [0, +)
Unit Secon d
Description Average duration of the response to service interaction during the process for a VIP subscriber to use a data service. Average duration of the response to service 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 transmission between the uplink and downlink PDUs.
[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. Set the threshold when you create a task.
Issue 01 (2013-07-15)
554
Parame ter Abnorm al Proporti on at Low Downlo ad Rate Downlin k TCP Out-ofOrders Average Upload Rate
Rang e [0,10 0]
Unit %
Description Indicates the proportion of the total measurement reports that the download rate is low.
[0, +)
Numb er
Number of times that downlink TCP disorder occurs during the process for a subscriber to use a data service. Average upload rate during the process for a subscriber to use a data service. Upload rate = Number of bytes transmitted by using the uplink PDU/Duration of data transmission by using the uplink PDU
[0.00, +)
Kbps
[0, +)
Numb er
Number of times that the upload rate is low during the process for a subscriber to use a data service. An upload rate is low if it is lower than the threshold for low upload rate. Set the threshold is when you create a task.
[0,10 0]
Indicates the proportion of the total measurement reports that the upload rate is low.
[0.00, +)
Kbps
Issue 01 (2013-07-15)
555
Rang e [0, +)
Unit MB
Description Total downlink traffic during the process for a subscriber to use a data service. 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 + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Downlink PDU
[0, +)
MB
Total uplink traffic during the process for a subscriber to use a data service. Total uplink traffic = Delay-Sensitive Information/Total Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Downlink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU
Uplink Signalin g Access Times Average Occupie d Downlin k Channel s Average Occupie d Uplink Channel s
[0, +)
Numb er
Number of access requests on the RACH (uplink CCCH) during the process for a subscriber to use a data service. Average number of channels occupied by the downlink during the process for a subscriber to use a data service.
[0, +)
Numb er
[0, +)
Numb er
Average number of channels occupied by the uplink during the process for a subscriber to use a data service.
Issue 01 (2013-07-15)
556
Common
Para met er BSC Nam e Cell ID Cell Nam e CGI Range Unit Description Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
ID of a VIP subscriber. Query the ID of a VIP subscriber using VIP group management. Name of a VIP alias. Query the alias of a VIP subscriber using VIP group management.
N/A
N/A
Issue 01 (2013-07-15)
557
Para met er IME ITAC Ter mina l Mod el Serv ice Typ e
Range
Unit
Description
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
International mobile equipment identitytype allocation code (IMEI-TAC) of the terminal used by a VIP subscriber. 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. Service type for a following counter.
N/A
N/A
N/A
N/A
RAN-CS/NET/Accessibility Evaluation
Par am eter R a n g e Uni t Description Supported NE Version
Number of access requests that a VIP group or VIP BSC6900 subscriber initiates during the process of using a call V900R013C00 or or SMS service in an active cell. later version
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.
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.
Issue 01 (2013-07-15)
558
Par am eter
R a n g e
Uni t
Description
Supported NE Version
[ 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.
RAN-CS/NET/Retainability Evaluation
Par am eter R a n g e [ 0 , + ) [ 0 , + ) U Description n i t N Number of times that a VIP group or VIP subscriber u releases the Call service in an active cell. m b e r N Number of times that a VIP group or VIP subscriber u abnormally releases the Call service in an active cell. m b e r Supported NE Version
Rele ases
Issue 01 (2013-07-15)
559
RAN-CS/NET/Mobility Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t 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 Supported NE Version
Inte rRA T Inco min g Han dov er Req uest s Inte rRA T Inco min g Han dov er Fail ures
[ 0 , + )
N Number of incoming inter-RAT handover failures that BSC6900 u a VIP group or VIP subscriber experiences in an active V900R013C00 or m cell. later version b e r
RAN-CS/Call/Accessibility Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t N Number of call setup requests that a VIP group or VIP u subscriber initiates in an active cell. m b e r Supported NE Version
Issue 01 (2013-07-15)
560
Par am eter
R a n g e [ 0 , + ) [ 0 , + )
U Description n i t N Number of call setup failures that a VIP group or VIP u subscriber experiences in an active cell. m b e r 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
Supported NE Version
Call Setu p Fail ures Abn orm al Rele ase Bef ore Call Co mpl etio n
RAN-CS/Call/Retainability Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t N Number of abnormal call releases that a VIP group or u VIP subscriber experiences in an active cell. m b e r Supported NE Version
Issue 01 (2013-07-15)
561
RAN-CS/SMS/Accessibility Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t N Number of call setup requests that a VIP group or VIP u subscriber initiates in an active cell as the mobilem originated party. b e r Supported NE Version
Call Setu p Req uest s (M OC) Call Setu p Fail ures (M OC) Call Setu p Req uest s (MT C) Call Setu p Fail ures (MT C)
[ 0 , + ) [ 0 , + )
N Number of call setup failures that a VIP group or VIP u subscriber experiences in an active cell as the mobilem originated party. b e r N Number of call setup requests that a VIP group or VIP u subscriber initiates in an active cell as the mobilem terminated party. b e r
[ 0 , + )
N Number of call setup failures that a VIP group or VIP u subscriber experiences in an active cell as the mobilem terminated party. b e r
Issue 01 (2013-07-15)
562
RAN-PS/PS/Accessibility Evaluation
Par am eter R a n g e [ 0 , + ) [ 0 , + ) [ 0 , + ) U Description n i t N Number of Attach Request messages that a VIP group or u VIP subscriber sends in an active cell. m b e r N Number of PDP Active Request messages that a VIP u group or VIP subscriber sends in an active cell. m b e r 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 Supported NE Version
Atta ch Req uest s PD P Acti ve Req uest s No Serv ice Inte racti on Res pon ses
RAN-PS/PS/Retainability Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t 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 Supported NE Version
Issue 01 (2013-07-15)
563
Par am eter
R a n g e [ 0 , + )
U Description n i t 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
Supported NE Version
Ove rlon g Cell Res elec tion Inte rval Tim es Serv ice Inte rrup tion s Due to Rou ting Are a Upd ate
[ 0 , + )
N Number of service interruptions that a VIP group or VIP u subscriber experiences due to routing area update in an m active cell. b e r
Issue 01 (2013-07-15)
564
Par am eter
R a n g e [ 0 , + )
U Description n i t N Number of times that the delay of the response to service u interaction is overlong when a VIP group or VIP m subscriber is using a service in an active cell. b e r
Supported NE Version
Common
Paramet er Server IP Server Name Rang e N/A N/A Unit N/A N/A Description IP address of an active server. 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. Port number of an active server. Name of an active service. Obtain the name of an active service by choosing System Function > Data Service Server Management in the navigation tree of the Nastar client based on the Server IP and Server Port values of the service. Number of reports generated when a user accesses the server. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A N/A
N/A N/A
Total Reports
Issue 01 (2013-07-15)
[0, +)
Num ber
RAN-PS/PS/General Evaluation
Paramet er ServerRelated Service Abnorma lities Rang e [0, +) Unit Num ber Description Server-Related Service Abnormalities = No Service Interaction Responses + Service Interaction Timeouts + Service Interaction with Long Delay + Downlink TCP Out-of-Orders Supported NE Version BSC6900 V900R013C01 or later version
RAN-PS/PS/Accessibility Evaluation
Paramet er No Service Interactio n Response s Rang e [0, +) Unit Num ber Description 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. Supported NE Version BSC6900 V900R013C01 or later version
[0, +)
Num ber
Issue 01 (2013-07-15)
566
Common
Param eter Deep Analysi s Rang e N/A Unit N/A Description 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. 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 IMSI N/A N/A N/A N/A Name of a VIP group. International mobile subscriber identity (IMSI) of a VIP subscriber. Alias of a VIP subscriber. Query the name of a VIP subscriber using VIP group management based on the IMSI of the VIP subscriber. BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Alias
N/A
N/A
Issue 01 (2013-07-15)
567
Rang e N/A
Unit N/A
Description Type approval code (TAC) in international mobile equipment identity (IMEI) of the UE used by a VIP subscriber. 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. Service type for a counter. Number of abnormal counters whose values exceed the result thresholds that engineers set during analysis task creation. Number of reports generated when a user accesses the network.
Termin al Model
N/A
N/A
N/A [0, +)
[0, +)
Num ber
RAN-NET/Accessibility Evaluation
Parameter Access Requests(IntraRAT) Range [0,+) Unit Numbe r Description Number of access requests that a VIP subscriber initiates from a cell in the current system. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
568
Range [0,+)
Unit Numbe r
Description Number of access failures that a VIP subscriber experiences from a cell in the current system. 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 = 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)
[0,+)
Numbe r Numbe r
Number of access requests that a VIP subscriber initiates from a cell in another system. Number of access failures that a VIP subscriber experiences from a cell in another system. Number of failed access requests (inter-RAT) = Number of failed service requests initiated by a specified UE that has gained access to a system of another RAT = Number of incoming interRAT handover failures that this UE experiences on the entire network + Number of times that the first RAB setup after an incoming inter-RAT handover fails)
[0,+)
Average TP on Access
[0,3069 ]
N/A
Issue 01 (2013-07-15)
569
Range [0,+)
Unit Numbe r
Description Number of times that theTP value is abnormal upon network access. Set the exception threshold when you create a task. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
[0.00,10 0.00]
Proportion of abnormal TP values that a VIP subscriber experiences upon network access. Proportion of abnormal TP values = Number of abnormal TP values/Number of TP values x 100%
[-115,-2 5] [0,+)
dBm
Average RSCP value when a VIP subscriber gains access to the network. Number of times that the RSCP value is abnormal upon network access. Set the exception threshold when you create a task. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
Numbe r
[0.00,10 0.00]
Proportion of abnormal RSCP values that a VIP subscriber experiences upon network access. Proportion of abnormal RSCP values = Number of abnormal RSCP values/Number of RSCP values x 100%
[-24,0]
dB
Average Ec/No value when a VIP subscriber gains access to the network.
Issue 01 (2013-07-15)
570
Range [0,+)
Unit Numbe r
Description Number of times that the Ec/No value is abnormal upon network access. Set the exception threshold when you create a task. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
[0.00,10 0.00]
Proportion of abnormal Ec/No values that a VIP subscriber experiences upon network access. Proportion of abnormal Ec/No values = Number of abnormal Ec/No values/Number of Ec/No values x 100%
[0,+)
Numbe r
Number of non-service RRC connection setup requests initiated by a VIP subscriber. RRC is short for radio resource control. 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.
RRC Setup Failures(NonService) RRC Setup Success Rate (Non-Service) RRC Setup Requests (Service) RRC Setup Failures (Service)
[0,+)
Numbe r %
Number of non-service RRC connection setup failures after network access. Success rate of non-service RRC connection setups after network access. Number of service RRC connection setup requests after network access. Number of service RRC connection setup failures after network access.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Numbe r Numbe r
[0,+)
Issue 01 (2013-07-15)
571
Parameter RRC Setup Success Rate (Service) RRC Setup Failures (Service-CS) RRC Setup Success Rate (Service-CS) RRC Setup Failures (Service-PS) RRC Setup Success Rate (Service-PS)
Unit %
Description Success rate of service RRC connection setups after network access. Number of CS RRC connection setup failures after network access. Success rate of CS RRC connection setups after network access. Number of PS RRC connection setup failures after network access. Success rate of PS RRC connection setups after network access.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Numbe r %
Numbe r %
[0.00,10 0.00]
[0,+)
Numbe r
[0.00,10 0.00]
[0,+)
Numbe r
Issue 01 (2013-07-15)
572
Range [0,+)
Unit Numbe r
Description Number of call setup failures that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Success rate of call setup requests that a VIP subscriber initiates to use the CS service as the mobile-terminated party. Number of call connection acknowledgment (alerting) successes of a VIP subscriber who accesses the network and uses the CS service as the mobile-originated party. The alerting process spans from the RRC connection setup request to the Alerting message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
Call Setup Success Rate (MTC) Call Connection Acknowledgme nt Success Times(Alerting) (MOC)
[0.00,10 0.00]
[0,+)
Numbe r
Call Connection Acknowledgme nt Success Rate (Alerting) (MOC) Call Connection Acknowledgme nt Success Times(Alerting) (MTC) Call Connection Acknowledgme nt Success Rate (Alerting) (MTC)
[0.00,10 0.00]
Rate of call connection acknowledgment (alerting) successes of a VIP subscriber who accesses the network and uses the CS service as the mobile-originated party. Number of successful call connection acknowledgments (alerting) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Success rate of call connection acknowledgments (alerting) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party.
[0,+)
Numbe r
[0.00,10 0.00]
Issue 01 (2013-07-15)
573
Range [0,+)
Unit Numbe r
Description Number of successful call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-originated party. The connection acknowledgment (Connect Ack) process spans from the RRC connection setup request to the Connect Ack message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
Call Connection Acknowledgme nt Success Rate (Connect Ack) (MOC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MTC)
[0.00,10 0.00]
Success rate of call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-originated party. Number of successful call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Success rate of call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party.
[0,+)
Numbe r
[0.00,10 0.00]
Issue 01 (2013-07-15)
574
Range [0,+)
Unit Numbe r
Description Number of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-originated party. The call success process spans from the RRC connection setup request to the Disconnect message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
[0.00,10 0.00]
Success rate of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-originated party. Number of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-terminated party. Success rate of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-terminated party.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Numbe r
[0.00,10 0.00]
[0,+)
Number
[0.00,10 0.00]
Issue 01 (2013-07-15)
575
Range [0,+)
Unit Number
Description Number of calls that a VIP subscriber successfully initiates to use the PS service. The call success process spans from the RRC connection setup request to the Disconnect message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
[0.00,10 0.00]
Success rate of calls that a VIP subscriber successfully initiates to use the PS service.
RAN-NET/PDP Evaluation-PS
Parameter PDP Activation Requests Range [0,+) Unit Number Description Number of PDP activation requests that a VIP subscriber initiates to access the network and use the PS service. Number of PDP activation failures that a VIP subscriber experiences during the process of attempting to access the network and use the PS service. Success rate of PDP activation requests that a VIP subscriber initiates to access the network and use the PS service. Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0.00,10 0.00]
Issue 01 (2013-07-15)
576
RAN-NET/Retainability Evaluation
Parameter Release Times (Intra-RAT) Range [0,+) Unit Number Description Number of times that a VIP subscriber releases all services in the current system. Releases(Intra-RAT) = Access Requests(Intra-RAT) - Access Failures(Intra-RAT) Abnormal Release Times (Intra-RAT) [0,+) Number Number of times that a VIP subscriber abnormally releases all services in the current system. Abnormal Release Times(IntraRAT) = Number of AMR RAB abnormal releases + Number of VP RAB abnormal releases + Number of PS R99 RAB abnormal releases + Number of HSDPA RAB abnormal releases + Number of HSUPA abnormal releases + Number of HSPA abnormal releases Number of the first RAB abnormal releases after interRAT incoming handover occurs. Release Times (Inter-RAT) [0,+) Number Number of times that a VIP subscriber releases all services in another system. Releases(Inter-RAT) = Access Requests(Inter-RAT) Access Failures(Inter-RAT) Abnormal Release Times (Inter-RAT) [0,+) Number Number of times that a VIP subscriber abnormally releases all services in another system. Abnormal Release Times(InterRAT) = Number of times that the first RAB after an incoming inter-RAT handover is abnormally released. BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
577
Range [0,+)
Unit Number
Description Number of times that a VIP subscriber releases all RRC connections during the process of using a service. Number of times that a VIP subscriber abnormally releases all RRC connections during the process of using a service.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
RAN-NET/Delay Evaluation
Parameter RRC Setup Success Times (Non-Service) Range [0,+) Unit Number Description Number of successful nonservice RRC connection setups upon successful call initiation. Number of successful RRC connection setups (non-service) = Number of RRC connection setup requests (non-service) Number of RRC connection setup failures (non-service) = Number of valid RRC connection setup delays (nonservice) Average RRC Setup Delay (Non-Service) N/A Second Average delay for non-service RRC connection setup upon successful call initiation. RRC connection setup delay = Time when the RRC CONN SETUP CMP message is generated Time when the RRC CONN REQ message is generated. Overlong RRC Setup Delay Times(NonService) [0,+) Number Number of overlong delays for non-service RRC connection setup upon successful call initiation. Set the overlong delay threshold when you create a task. BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
578
Parameter Proportion of Overlong RRC Setup Delay (Non-Service) RRC Setup Success Times (Service)
Unit %
Description Proportion of delays for nonservice RRC connection setup in all overlong delays upon successful call initiation. Number of successful service RRC connection setups upon successful call initiation. Number of service RRC 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.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Second
Average delay for service RRC connection setup upon successful call initiation. RRC connection setup delay = Time when the RRC CONN SETUP CMP message is generated Time when the RRC CONN REQ message is generated.
[0,+)
Number
Number of overlong delays for service RRC connection setup upon successful call initiation. Set the overlong delay threshold when you create a task.
[0.00,1 00.00]
Proportion of overlong delays for service RRC connection setup in all overlong delays upon successful call initiation.
RAN-NET/Mobility Evaluation
Parameter Soft Handover Requests Range [0,+) Unit Number Description Number of soft handover requests that a VIP subscriber initiates during the process of using a service. Supported NE Version BSC6900 V900R014C00 or later version
Issue 01 (2013-07-15)
579
Range [0,+)
Unit Number
Description Number of soft handover failures that a VIP subscriber experiences during the process of using a service. Success rate of soft handovers (including softer handovers) that a VIP subscriber initiates during the process of using a service. Number of hard handover requests that a VIP subscriber initiates during the process of using a service. Number of hard handover failures that a VIP subscriber experiences during the process of using a service. Success rate of hard handovers that a VIP subscriber initiates during the process of using a service. Average soft handover delay during the process for a VIP subscriber to use a service. Average hard handover delay during the process for a VIP subscriber to use a service. Number of outgoing handover requests (from a UMTS network to another network) initiated by a UE. Number of outgoing handover requests (from a UMTS network to a GSM network) initiated by a VIP subscriber.
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0.00,1 00.00]
[0,+)
Number
[0,+)
Number
[0.00,1 00.00]
Average Soft Handover Delay Average Hard Handover Delay Inter-RAT Outgoing Handover Requests Inter-RAT Outgoing Handover Requests (UMTS to GSM) Inter-RAT Outgoing Handover Requests (UMTS to LTE)
[0,+)
Second
[0,+)
Second
[0,+)
Number
[0,+)
Number
[0,+)
Number
Number of outgoing handover requests (from a UMTS network to an LTE network) initiated by a VIP subscriber.
Issue 01 (2013-07-15)
580
Parameter Inter-RAT Outgoing Handover Failures Inter-RAT Outgoing Handover Failures(UMTS to GSM) Inter-RAT Outgoing Handover Failures(UMTS to LTE) Inter-RAT Incoming Handover Requests Inter-RAT Incoming Handover Requests(GSM to UMTS) Inter-RAT Incoming Handover Requests(LTE to UMTS) Inter-RAT Incoming Handover Failures Inter-RAT Incoming Handover Failures(GSM to UMTS) Inter-RAT Incoming Handover Failures(LTE to UMTS)
Range [0,+)
Unit Number
Description Number of outgoing handover failures (from a UMTS network to another network) experienced by a VIP subscriber. Number of outgoing handover failures (from a UMTS network to a GSM network) experienced by a VIP subscriber. Number of outgoing handover failures (from one UMTS network to another LTE network) experienced by a UE. Number of inter-RAT handover requests (from another network to a UMTS network) initiated by a VIP subscriber. Number of inter-RAT handover requests (from a GSM network to a UMTS network) initiated by a VIP subscriber. Number of inter-RAT handover requests (from an LTE network to a UMTS network) initiated by a VIP subscriber. Number of inter-RAT handover failures (from another network to a UMTS network) experienced by a VIP subscriber. Number of inter-RAT handover failures (from a GSM network to a UMTS network) experienced by a VIP subscriber. Number of inter-RAT handover failures (from an LTE network to a UMTS network) experienced by a VIP subscriber.
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
581
Range [0,+)
Unit Second
Description Average delay for outgoing interRAT handover recorded by the current system. Outgoing inter-RAT handover delay = Time when the IU RELEASE COMMAND message is generated Time when the RELOCATION REQUIRED message is generated.
Average InterRAT Outgoing Handover Delay (UMTS to GSM) Average InterRAT Outgoing Handover Delay (UMTS to LTE) Average InterRAT Incoming Handover Delay
[0,+)
Second
[0,+)
Second
Average delay for UMTS-toLTE handover recorded by the current system. Average delay for incoming inter-RAT handover recorded by the current system. Incoming inter-RAT handover delay = Time when the UTRAN MOBILITY INFORMATION CONFIRM message is generated Time when the RELOCATION REQUIRED message is generated.
[0,+)
Second
Average InterRAT Incoming Handover Delay (GSM to UMTS) Average InterRAT Incoming Handover Delay (LTE to UMTS) Inter-RAT Cell Reselection Times
[0,+)
Second
[0,+)
Second
Average delay for LTE-toUMTS handover recorded by the current system. Number of cell reselections recorded by the current system.
[0,+)
Number
Issue 01 (2013-07-15)
582
RAN-CS/AMR/Accessibility Evaluation
Parameter RAB Setup Requests Range [0,+) Unit Number Description Number of RAB setup requests initiated by a VIP subscriber. RAB is short for radio access bearer. RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate [0,+) Number Number of RAB setup failures experienced by a VIP subscriber. Number of times that a VIP subscriber successfully initiates an RAB setup request. RAB setup success rate after network access. RAB setup success rate (%) = Number of successful RAB setups/Number of RAB setup requests x 100%. Call Connection Acknowledgme nt Success Times(Alerting) Call Connection Acknowledgme nt Success Times(Connect Ack) Abnormal Release Times Before Connection Acknowledge [0,+) Number Number of times that a VIP subscriber hears the alerting upon successful call initiation. Number of times that a VIP subscriber hears the peer ends' voice upon successful call initiation. 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. Supported NE Version BSC6900 V900R013C00 or later version
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
583
RAN-CS/AMR/Retainability Evaluation
Parameter RAB Setup Success Times Abnormal RAB Release Times Range [0,+) Unit Number Description See RAB Setup Success Times in RAN-CS/VP/Accessibility Evaluation Number of times that the RAB is abnormally released after a VIP subscriber gains access to the network and successfully initiates a call. Abnormal RAB release rate after a VIP subscriber gains access to the network and successfully initiates a call. Abnormal RAB release rate (%) = Number of abnormal RAB releases/Number of successful call setups x 100%. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,10 0.00]
RAN-CS/AMR/Delay Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Number Description Number of successful RAB setups during call initiation, that is, number of RAB setup delays. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
584
Range [0,+)
Unit Second
Description Average RAB setup delay during the process for a VIP subscriber to initiate a call. Average RAB setup delay (s) = Sum of RAB setup delays/ Number of RAB setup delays. RAB setup delay = RAB setup request connection acknowledge time RAB setup request time. Statistical point for RAB setup request connection acknowledge time: When the RAB assignment procedure is successful, namely, when the SRNC sends a Radio Access Bearer Assignment Response message to the CN after it receives an RAB setup connection acknowledge message. Statistical point for RAB setup request time: When the UTRAN receives a Radio Access Bearer Assignment Request message from the CN.
[0,+)
Number
Number of times that the RAB BSC6900 setup delay is overlong during V900R013C00 the process for a VIP subscriber or later version to initiate a call. Set the exception threshold when you create a task.
[0.00,10 0.00]
Proportion of RAB setup delays in all overlong delays. Proportion of RAB setup delays (%) = Number of overlong RAB setup delays/Number of RAB setup delays x 100% = Number of overlong RAB setup delays/ Number of successful RAB setups x 100%.
[0,+)
Number
Number of times that the call setup delay of the mobileoriginated party upon successful call initiation is overlong.
Issue 01 (2013-07-15)
585
Parameter Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC)
Range [0,+)
Unit Second
Description Average call setup delay of the mobile-originated party upon successful call initiation. Number of times that the call setup delay of the mobileoriginated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,10 0.00]
Proportion of overlong call setup delays of the mobileoriginated party upon successful call initiation. Proportion of overlong call setup delays (mobileoriginated) (%) = Number of overlong call setup delays (mobile-originated)/Number of call setup delays (mobileoriginated) x 100% = Number of overlong call setup delays (mobile-originated)/Number of successful RRC connection setups x 100%.
[0,+)
Number
Number of times that the call setup delay of the mobileterminated party upon successful call initiation is overlong. Average call setup delay of the mobile-terminated party upon successful call initiation. Number of times that the call setup delay of the mobileterminated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
Average Call Setup Delay (MTC) Overlong Call Setup Delay Times(MTC)
[0,+)
Second
[0,+)
Number
Issue 01 (2013-07-15)
586
Unit %
Description Proportion of overlong call setup delays of the mobileterminated party upon successful call initiation. Proportion of overlong call setup delays (mobileterminated) (%) = Number of overlong call setup delays (mobile-terminated)/Number of call setup delays (mobileterminated) x 100% = Number of overlong call setup delays (mobile-terminated)/Number of successful RRC connection setups x 100%.
Call Connection Acknowledgme nt Success Times(Alerting) (MOC) Average Call Connection Acknowledgme nt Delay (Alerting) (MOC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MOC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MOC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MOC)
[0,+)
Number
Number of times that the mobile-originated party hears the alerting upon successful call initiation. Average alerting delay of the mobile-originated party upon successful call initiation.
[0,+)
Second
[0,+)
Number
Number of times that the alerting delay of the mobileoriginated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0.00,10 0.00]
Proportion of overlong alerting delays experienced by the mobile-originated party upon successful call initiation.
[0,+)
Number
Number of call connection acknowledgment (Connect Ack) delays experienced by the mobile-originated party upon successful call initiation.
Issue 01 (2013-07-15)
587
Parameter Average Call Connection Acknowledgme nt Delay (Connect Ack) (MOC) Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MOC)
Range [0,+)
Unit Second
Description Average call connection acknowledgment (Connect Ack) delay of the mobileoriginated party upon successful call initiation. Number of times that the call connection acknowledgment (Connect Ack) delay of the mobile-originated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0,+)
Number
Proportion of Overlong Call Connection Acknowledgme nt Delay (Connect Ack) (MOC) Call Connection Acknowledgme nt Success Times(Alerting) (MTC) Average Call Connection Acknowledgme nt Delay (Alerting) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MTC)
[0.00,10 0.00]
Proportion of overlong call connection acknowledgment (Connect Ack) delays experienced by the mobileoriginated party upon successful call initiation. Number of times that the mobile-terminated party hears the alerting upon successful call initiation. Average call connection acknowledgment (alerting) delay of the mobile-terminated party upon successful call initiation. Number of times that the call connection acknowledgment (alerting) delay of the mobileterminated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0,+)
Number
[0,+)
Second
[0,+)
Number
Issue 01 (2013-07-15)
588
Parameter Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MTC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MTC) Average Call Connection Acknowledgme nt Delay (Connect Ack) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MTC)
Unit %
Description Proportion of overlong call connection acknowledgment (alerting) delays experienced by the mobile-terminated party upon successful call initiation.
[0,+)
Number
Number of successful call connection acknowledgments (Connect Ack) experienced by the mobile-terminated party upon successful call initiation. Average call connection acknowledgment (Connect Ack) delay of the mobileterminated party upon successful call initiation. Number of times that the call connection acknowledgment (Connect Ack) delay of the mobile-terminated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
Proportion of call connection acknowledgment (Connect Ack) delays experienced by the mobile-terminated party upon successful call initiation.
Issue 01 (2013-07-15)
589
Range [0,+)
Unit Second
Description Average RAB duration upon successful call initiation. 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
[0,+)
Number
Number of times that the RAB duration is below the threshold for short RAB duration upon successful call initiation. Set the exception threshold when you create a task.
[0,+)
Second
Average call duration of calls initiated by a VIP subscriber. Number of short calls upon successful call initiation. The mechanism for calculating the number of short calls adds the condition that short calls are initiated by the mobileoriginated party.
[0,+)
Number
Issue 01 (2013-07-15)
590
Unit %
Description Proportion of short calls upon successful call initiation. The mechanism for calculating the proportion of short calls adds the condition that short calls are initiated by the mobileoriginated party.
[0,+)
Second
Average call duration of calls initiated by a VIP subscriber. Number of short calls upon successful call initiation. The mechanism for calculating the number of short calls adds the condition that short calls are initiated by the mobileterminated.
[0,+)
Number
[0.00,10 0.00]
Proportion of short calls upon successful call initiation. The mechanism for calculating the proportion of short calls adds the condition that short calls are initiated by the mobileterminated.
RAN-CS/AMR/Quality Evaluation
Parameter Call Setup Success Times Downlink OneWay Audio Times Range [0,+) Unit Number Description Number of times that a VIP subscriber successfully initiates a call setup request. Number of calls with downlink one-way audio problems. Downlink one-way audio problems are detected by the RNC. [0.00,10 0.00] % Proportion of Downlink OneWay Audio = Downlink OneWay Audio Times/RAB Setup Successes x 100% Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
Issue 01 (2013-07-15)
591
Range [0,+)
Unit Number
Description Number of calls with uplink one-way audio problems. Uplink one-way audio problems are detected by the RNC.
[0.00,10 0.00]
Proportion of Uplink One-Way Audio = Uplink One-Way Audio Times/RAB Setup Successes x 100% Number of calls with static problems. Static problems are detected by the RNC.
[0,+)
Number
Noise Proportion
[0.00,10 0.00]
Proportion of calls with static problems. Proportion of calls with static problems (%) = Number of calls with static problems/Number of connected calls (Connect Ack) x 100%.
Issue 01 (2013-07-15)
592
Range [0,+)
Unit Number
Description Number of signal quality indicator (SQI) reports generated during a call. 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. 2. The RNC collects statistics on the average SQI value and divides signal quality into different levels according to SQI values: RAN14.0: Excellent (SQI<= (400,500]), Good (SQI<= (300,400]), Accept (SQI<= (200,300]), Poor (SQI<= (100,200]), Bad (SQI<= [0,100]). RAN13.0 and earlier: Good (SQI <= (300,500]), Accept (SQI <= (200,300]), Bad (SQI <=(0,200]). You can modify the segment intervals of levels by running the SET USQICOUNT command on the RNC.
Average SQI
[0,+)
N/A
Average SQI value in the SQI reports generated during a call. 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. Set the exception threshold when you create a task.
Abnormal SQIs
[0,+)
Number
Issue 01 (2013-07-15)
593
Unit %
Description Proportion of calls with abnormal SQI values. Proportion of calls with abnormal SQI values (%) = Number of calls with abnormal SQI values/Number of connected calls (Connect Ack) x 100%.
[0.00,10 0.00]
Proportion of calls whose SQI is Excellent during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Good during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Accept during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Poor during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Bad during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of level 1 uplink BLER values upon successful call initiation. BLER is short for block error rate. This parameter is applicable only to the AMR service. Standard for level 1: 00.78%.
Issue 01 (2013-07-15)
594
Unit %
Description Proportion of level 2 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 2: 0.78% 1.56%.
[0.00,10 0.00]
Proportion of level 3 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 3: 1.56% 3.12%
[0.00,10 0.00]
Proportion of level 4 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 4: 3.12% 6.24%.
[0.00,10 0.00]
Proportion of level 5 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 5: 6.24% 12.48%.
[0.00,10 0.00]
Proportion of level 6 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 6: above 12.48%.
Issue 01 (2013-07-15)
595
RAN-CS/VP/Accessibility Evaluation
Parameter RAB Setup Requests RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate Call Connection Acknowledgme nt Success Times(Alerting) Call Connection Acknowledgme nt Success Times(Connect Ack) Abnormal Release Times Before Connection Acknowledgme nt Range [0,+) Unit Number Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
Number
[0,+)
Number
[0,+)
Number
RAN-CS/VP/Retainability Evaluation
Parameter RAB Setup Success Times Abnormal RAB Release Times Range [0,+) Unit Number Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
Issue 01 (2013-07-15)
596
Unit %
RAN-CS/VP/Delay Evaluation
Parameter RAB Setup Success Times Average RAB Setup Delay Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Average Call Setup Delay (MTC) Range [0,+) Unit Number Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Second
[0,+)
Number
Number
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR".
[0,+)
Second
Issue 01 (2013-07-15)
597
Parameter Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay (MTC) Call Connection Acknowledgme nt Success Times(Alerting) (MOC) Average Call Connection Acknowledgme nt Delay (Alerting) (MOC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MOC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MOC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MOC) Average Call Connection Acknowledgme nt Delay (Connect Ack) (MOC)
Range [0,+)
Unit Number
Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0.00,10 0.00]
[0,+)
Number
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
[0,+)
Second
Issue 01 (2013-07-15)
598
Parameter Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MOC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Connect Ack) (MOC) Call Connection Acknowledgme nt Success Times(Alerting) (MTC) Average Call Connection Acknowledgme nt Delay (Alerting) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MTC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MTC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MTC)
Range [0,+)
Unit Number
[0.00,10 0.00]
[0,+)
Number
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
Issue 01 (2013-07-15)
599
Parameter Average Call Connection Acknowledgme nt Delay (Connect Ack) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MTC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Connect Ack) (MTC) Average RAB Service Duration Overshort RAB Service Duration Times Average Service Duration(MOC) Number of Short Calls (MOC) Proportion of Short Calls (MOC) Average Service Duration(MTC) Number of Short Calls (MTC)
Range [0,+)
Unit Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Second
Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR".
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0,+)
Second
[0,+)
Number
Second
[0,+)
Number
Issue 01 (2013-07-15)
600
Unit %
RAN-CS/SMS/Accessibility Evaluation
Parameter Setup Requests (MOC) Setup Failures (MOC) Setup Success Rate (MOC) Setup Requests (MTC) Setup Failures (MTC) Setup Success Rate (MTC) Range [0,+) Unit Number Description Number of SMS service setup requests initiated by the mobileterminated party. Number of failed SMS service setups initiated by the mobileoriginated party. Number of successful SMS service setups initiated by the mobile-originated party. Number of SMS service setup requests initiated by the mobileterminated party. Number of failed SMS service setups initiated by the mobileterminated party. Number of successful SMS service setups initiated by the mobile-terminated party. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
Number
[0,+)
Number
[0.00,10 0.00]
Issue 01 (2013-07-15)
601
[0,+)
[0.00,1 00.00]
[0,+)
[0.00,1 00.00]
Issue 01 (2013-07-15)
602
Issue 01 (2013-07-15)
603
Parameter Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong RAB Setup Delay Times(MOC)
Range [0, +)
Unit Numb er
Description Number of times that the call setup delay of the mobile-originated party upon successful call initiation is overlong. Average call delay of the mobileoriginated party upon successful call initiation. Number of times that the call setup delay of the mobile-originated party upon successful call initiation is overlong. Set the overlong delay threshold when you create a task.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0, +) [0, +)
Secon d Numb er
[0.00,1 00.00]
Proportion of overlong call setup delays of the mobile-originated party upon successful call initiation. Proportion of overlong call setup delays (mobile-originated) = Number of overlong call setup delays (mobile-originated)/ Number of call setup delays (mobile-originated) x 100% = Number of overlong call setup delays (mobile-originated)/ Number of successful RRC connection setups x 100%.
[0, +)
Numb er
Number of times that the call setup delay of the mobile-terminated upon successful call initiation is abnormal.
Issue 01 (2013-07-15)
604
Range [0, +)
Unit Secon d
Description Average call setup delay of the mobile-terminated upon successful call initiation. Average call setup delay =Sum of call setup delays/Number of call setup delays. Call setup delay = RAB request connection acknowledge time Signaling access time. Statistical point for RAB request connection acknowledge time: When the RAB assignment procedure is successful, namely, when the SRNC sends a Radio Access Bearer Assignment Response message to the CN after it receives an RAB setup connection acknowledge message. Statistical point for signaling access time: When an RRC SETUP REQ or RELOC REQ message is received or when an incoming inter-RAT handover request is initiated.
[0, +)
Numb er
Number of times that the call setup delay of the mobile-terminated party upon successful call initiation is overlong. Set the overlong delay threshold when you create a task.
[0.00,1 00.00]
Proportion of overlong call setup delays experienced by the mobileterminated party upon successful call initiation. Proportion of overlong call setup delays = Number of overlong call setup delays/Number of call setup delays x 100% = Number of overlong call setup delays/Number of successful RRC connection setups x 100%.
Issue 01 (2013-07-15)
605
Range [0, +)
Unit Secon d
Description Average RAB duration upon successful call initiation. 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. Statistical point for RAB request connection acknowledge time: When the RAB assignment procedure is successful, after receiving an RAB setup connection acknowledge message, the SRNC sends a Radio Access Bearer Assignment Response message to the CN.
Issue 01 (2013-07-15)
606
Parameter Downlink Traffic Volume Average Downlink Transmission Duration Average Downlink Throughput
Unit KB
Description Downlink traffic volume of all common PS services. Average downlink transmission duration for all common PS services. Average downlink throughput for all common PS services. Average downlink throughput = Downlink traffic volume/ Downlink data transmission duration.
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
Second
[0.00, +)
kbit/s
[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. Set the exception threshold when you create a task.
Uplink Traffic Volume Average Uplink Transmission Duration Average Uplink Throughput
KB
Uplink traffic volume for all common PS services. Average uplink transmission duration for all common PS services. Average uplink throughput rate for all common PS services. Average uplink throughput = Total uplink traffic volume/Total uplink transmission duration
BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
Second
kbit/s
[0, +)
Numbe r
Number of times that among all common PS services, the average uplink throughput for one RAB setup is below a threshold for low average uplink throughput. Set the exception threshold when you create a task.
Issue 01 (2013-07-15)
607
Issue 01 (2013-07-15)
608
Unit %
Description Proportion of level 6 uplink BLER values upon successful call initiation. This parameter is applicable only to the PS service. Standard for level 6: 12.48% < X.
RAN-PS/HSDPA/Accessibility Evaluation
Parameter RAB Setup Requests RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate Rang e [0, +) [0, +) [0, +) [0.00,1 00.00] Unit Numbe r Numbe r Numbe r % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RAN-PS/HSDPA/Retainability Evaluation
Parameter RAB Setup Success Times Abnormal RAB Release Times Abnormal RAB Release Rate Rang e [0, +) [0, +) [0.00, 100.00 ] Unit Numbe r Numbe r % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
609
RAN-PS/HSDPA/Delay Evaluation
Parameter RAB Setup Success Times Average RAB Setup Delay Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Average Call Setup Delay (MTC) Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay (MTC) Rang e [0, +) [0, +) [0, +) [0.00, 100.00 ] [0, +) [0, +) [0, +) [0.00, 100.00 ] [0, +) [0, +) [0, +) [0.00, 100.00 ] Unit Numbe r Second Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Numbe r %
Numbe r Second
Numbe r %
Numbe r Second
Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Numbe r %
Issue 01 (2013-07-15)
610
Rang e [0, +)
Unit Second
RAN-PS/HSDPA/Rate Evaluation
Parameter Downlink Traffic Volume Average Downlink Transmission Duration Average Downlink Throughput Low Average Downlink Throughput Times Average HSDPA Downlink Rate Low Average HSDPA Downlink Rate Times Rang e [0, +) [0, +) Unit KB Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Second
[0.00, +) [0, +)
kbit/s
Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Numbe r
[0.00, +) [0, +)
kbit/s
Average downlink rate for all HSDPA services. Number of times that the average downlink rate for all HSDPA services is low. Set the threshold for low average rate when you create a task.
Numbe r
Average HSDPA Downlink Rate with Sufficient Resources Times of Low Average HSDPA Downlink Rate with Sufficient Resources
[0.00, +)
kbit/s
Average downlink rate for all HSDPA services when service resources are sufficient.
[0, +)
Numbe r
Number of times that the average downlink rate for all HSDPA services is low when service resources are sufficient. Set the threshold for low average rate when you create a task.
Issue 01 (2013-07-15)
611
Parameter Average HSDPA Downlink Rate with Insufficient Resources Times of Low Average HSDPA Downlink Rate with Insufficient Resources
Rang e [0.00, +)
Unit kbit/s
Description Average downlink rate for all HSDPA services when service resources are insufficient.
[0, +)
Numbe r
Number of times that the average downlink rate for all HSDPA services is low when service resources are insufficient. Set the threshold for low average rate when you create a task.
RAN-PS/HSUPA/Accessibility Evaluation
Parameter RAB Setup Requests RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate Rang e [0, +) [0, +) [0, +) [0.00,1 00.00] Unit Numbe r Numbe r Numbe r % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RAN-PS/HSUPA/Retainability Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Numbe r Description Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
612
Range [0,+)
Unit Numbe r %
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0.00,1 00.00]
RAN-PS/HSUPA/Delay Evaluation
Parameter RAB Setup Success Times Average RAB Setup Delay Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Range [0,+) Unit Numb er Secon d Numb er % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
[0,+)
[0,+)
[0,+)
[0.00,1 00.00]
[0,+)
Numb er
Issue 01 (2013-07-15)
613
Parameter Average Call Setup Delay (MTC) Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay Average RAB Service Duration
Range [0,+)
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Secon d
RAN-PS/HSUPA/Rate Evaluation
Parameter Uplink Traffic Volume Range [0,+) Unit KB Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Second
[0.00,+)
kbit/s
[0,+)
Number
Issue 01 (2013-07-15)
614
RAN-PS/HSPA/Accessibility Evaluation
Parameter RAB Setup Requests Range [0,+) Unit Number Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
[0.00,100.00]
RAN-PS/HSPA/Retainability Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Number Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,100.00]
Issue 01 (2013-07-15)
615
RAN-PS/HSPA/Delay Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Number Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Second
Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Average Call Setup Delay (MTC)
[0,+)
Number
[0.00,100.00]
[0,+)
Number
[0,+)
Second
[0,+)
Number
[0.00,100.00]
[0,+)
Number
[0,+)
Second
Issue 01 (2013-07-15)
616
Parameter Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay (MTC) Average RAB Service Duration
Range [0,+)
Unit Number
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0.00,100.00]
[0,+)
Second
RAN-PS/HSPA/Rate Evaluation
Parameter Downlink Traffic Volume Range [0,+) Unit KB Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
Average Downlink Transmission Duration Average Downlink Throughput Low Average Downlink Throughput Times Uplink Traffic Volume
[0,+)
Second
[0.00,+)
kbit/s
[0,+)
Number
[0,+)
KB
[0,+)
Second
Issue 01 (2013-07-15)
617
Range [0.00,+)
Unit kbit/s
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0, + )
N Number of RAB setup failures u where multiple RABs are accessed m during a call. b e r
Issue 01 (2013-07-15)
618
U Description n i t % Setup success rate for accessing multiple RABs during a call.
Supported NE Version
Mul tiRA B Rele ase Tim es Abn orm al Mul tiRA B Rele ase Tim es
[ 0 , + )
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.
Issue 01 (2013-07-15)
619
Par am eter
R a n g e [ 0 . 0 0 , 1 0 0 . 0 0 ]
U Description n i t % Abnormal RAB release rate for releasing multiple RABs that contain at least one CS RAB at a time during a call.
Supported NE Version
Mul tiRA B Rele ase Tim es Abn orm al Mul tiRA B Rele ase Tim es
[ 0 , + )
N u m b e r
Number of abnormal RAB releases where multiple RABs that contain only PS RABs are released during a call.
Issue 01 (2013-07-15)
620
Par am eter
R a n g e [ 0 . 0 0 , 1 0 0 . 0 0 ]
U Description n i t % Abnormal RAB release rate for releasing multiple RABs that contain only PS RABs during a call.
Supported NE Version
Active Cell/Common
Paramete r RNC ID Range [0,4095] Unit N/A Description ID of the RNC to which an active cell belongs. Name of the RNC to which an active cell belongs. ID of an active cell. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
[0,65535]
N/A
Cell Name
N/A
N/A
Service Type
N/A
N/A
Issue 01 (2013-07-15)
621
Number of nonBSC6900 service setup V900R013C00 or requests that a VIP later version group or VIP subscriber initiates in an active cell. 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. Set the exception threshold when you create a task. BSC6900 V900R013C00 or later version
[0,+)
Number
[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.
[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. Set the exception threshold when you create a task.
Issue 01 (2013-07-15)
622
Range [0,+)
Unit Number
Description
Supported NE Version
Number of nonBSC6900 service setup V900R013C00 or requests that a VIP later version group or VIP subscriber initiates in an active cell. Number of service BSC6900 setup requests that V900R013C00 or a VIP group or VIP later version subscriber initiates in an active cell. Number of service setup failures that a VIP group or VIP subscriber experiences in an active cell. BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
623
[0,+)
Numbe r
[0,+)
Numb er
Issue 01 (2013-07-15)
624
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
625
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
626
[0,+)
Numbe r
[0,+)
Number
Number of PS BSC6900 service setup V900R013C00 or failures that a VIP later version group or VIP subscriber experiences in an active cell.
Issue 01 (2013-07-15)
627
[0,+)
Numbe r
[0,+)
Number
Issue 01 (2013-07-15)
628
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
629
[0,+)
Number
Common
Parameter Deep Analysis Ran ge N/A Uni t N/A Description 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. 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. LTE 3900 V100R005C00 or later version Supported NE Version LTE 3900 V100R005C00 or later version
Issue 01 (2013-07-15)
630
Parameter User ID
Ran ge [1, +)
Uni t N/A
Description Identity of a VIP subscriber. User ID, which is created by the system when creating a VIP User in the VIP Group Management.
User Name
N/A
N/A
Name of a VIP subscriber. Query the name of a VIP subscriber using VIP group management based on the IMSI of the VIP subscriber. 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.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
IMEI-TAC
N/A
Terminal Model
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. Service type for a counter.
N/A
N/A
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0, +)
Num ber
Number of abnormal counters whose values exceed the thresholds that engineers set during analysis task creation. Number of reports generated when a user accesses the network.
[0, +)
Num ber
[0,+)
Number
Issue 01 (2013-07-15)
631
[0,+)
Number
Number of failed intraRAT handover preparations after a UE initiates intra-RAT handover requests. Successful preparation rate of intra-RAT handovers.
[0,100]
[0,+)
Number
[0,+)
Number
[0,100]
[0,+)
Number
[0,+)
Number
Number of failed interRAT handover preparations after a UE initiates inter-RAT handover requests.
Issue 01 (2013-07-15)
632
Parameter Inter-RAT Outgoing Handover Preparing Success Rate Inter-RAT Outgoing Handover Execution Attempts Inter-RAT Outgoing Handover Execution Failures Inter-RAT Outgoing Handover Execution Success Rate
Range [0,100]
Unit %
[0,+)
Number
[0,+)
Number
[0,100]
RAN PS Counters-Accessibility
Parameter E-RAB Setup Requests E-RAB Setup Failures E-RAB Setup Success Rate Range [0,+) Unit Number Description Number of E-RAB setup requests initiated by a UE. Number of failed E-RAB setups after a UE initiates E-RAB setup requests. Success rate of E-RAB setups after a UE initiates E-RAB setup requests. ERAB is E-UTRAN radio access bearer for short. Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,+)
Number
[0,100]
Issue 01 (2013-07-15)
633
RAN PS Counters-Retainablity
Parameter Abnormal ERAB Releases Abnormal ERAB Release Ratio Range [0,+) Unit Number Description Number of abnormal ERAB releases in the E-RAB releases. Proportion of abnormal ERAB releases in the E-RAB releases. Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,100]
Active Cell
Parameter eNodeB ID Range N/A Unit N/A Description ID of an eNodeB. Supported NE Version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version
eNodeB Name
N/A
N/A
Name of an eNodeB.
Cell ID
N/A
N/A
ID of a cell.
Cell Name
N/A
N/A
Name of a cell.
Service Type
N/A
N/A
[0,+)
Numbe r
Number of service RRC setup requests of a VIP group or a VIP object in an active cell. Number of non-service RRC setup requests of a VIP group or a VIP object in an active cell.
[0,+)
Numbe r
Issue 01 (2013-07-15)
634
Range [0,+)
Unit Numbe r
Description Number of E-RAB setup requests of a VIP group or a VIP object in an active cell. Number of failed E-RAB setups of a VIP group or a VIP object in an active cell. Number of abnormal E-RAB releases of a VIP group or a VIP object in an active cell.
Supported NE Version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version
[0,+)
Numbe r
[0,+)
Numbe r
Common
Parameter Deep Analysis Rang e N/A Unit N/A Description 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. 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. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
User ID
N/A
N/A
ID of a VIP subscriber.
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.
Issue 01 (2013-07-15)
635
Parameter IMEI-TAC
Rang e N/A
Unit N/A
Description International mobile equipment identity-type allocation code (IMEI-TAC) of the terminal used by a VIP subscriber. 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. 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. Number of reports of the VIP user.
Terminal Model
N/A
N/A
[0, +)
Numb er
Total Reports
[0, +)
Numb er
SGSN-Attach
Parameter Rang e Unit Numb er Description Number of attach process requests by a VIP subscriber on the GSM and UMTS networks. Attach processes include: GPRS attach Combined attach Attach Failures [0, +) Numb er Number of attach process failures by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
636
Unit %
Description Attach process success rate by a VIP subscriber on the GSM and UMTS networks. Attach success rate = (1 Number of attach failures/ Number of attach requests) x 100%
[0, +) [0, +)
ms
Average delay of an attach process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of an attach process by a VIP subscriber on the GSM and UMTS networks.
Numb er
SGSN-RAU
Parameter RAU (others) Requests Rang e [0.00, 100.0 0] [0, +) [0, +) Unit % Description Number of other RAU processes by a VIP subscriber on the GSM and UMTS networks Number of other RAU process failures by a VIP subscriber on the GSM and UMTS networks. Other RAU process success rate by a VIP subscriber on the GSM and UMTS networks. RAU (others) success rate = (1 Number of RAU (others) failures/Number of RAU (others) requests) x 100% Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
ms
Numb er
Issue 01 (2013-07-15)
637
Rang e [0, +)
Unit Numb er
Description Number of intra SGSN RAU process requests by a VIP subscriber on the GSM and UMTS networks. Intra SGSN RAU processes include: Intra RAU Intra combined RAU Periodic RAU Periodic combined RAU
[0, +)
Numb er
Number of intra SGSN RAU process failures by a VIP subscriber on the GSM and UMTS networks. Intra SGSN RAU process success rate by a VIP subscriber on the GSM and UMTS networks. Intra SGSN RAU success rate = (1 Number of intra SGSN RAU failures/Number of intra SGSN RAU requests) x 100%
[0.00, 100.0 0]
Average Intra SGSN RAU Delay Overlong Intra SGSN RAU Delays
[0, +)
ms
Average delay of an intra SGSN RAU process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of an intra SGSN RAU process by a VIP subscriber on the GSM and UMTS networks. Number of inter SGSN RAU process requests by a VIP subscriber on the GSM and UMTS networks. Inter SGSN RAU processes include: Inter RAU Inter combined RAU
[0, +)
Numb er
[0, +)
Numb er
Issue 01 (2013-07-15)
638
Rang e [0, +)
Unit Numb er
Description Number of inter SGSN RAU process failures by a VIP subscriber on the GSM and UMTS networks. Inter SGSN RAU process success rate by a VIP subscriber on the GSM and UMTS networks. Inter SGSN RAU process success rate by a VIP subscriber on the GSM and UMTS networks.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
[0.00, 100.0 0]
Average Inter SGSN RAU Delay Overlong Inter SGSN RAU Delays
[0, +)
ms
Average delay of an inter SGSN RAU process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of an inter SGSN RAU process by a VIP subscriber on the GSM and UMTS networks.
[0, +)
Numb er
SGSN-Service Req
Parameter Service Req Requests Rang e [0, +) Unit Numb er Description Number of service req process requests by a VIP subscriber on the GSM and UMTS network. The service req process includes: Service Request Service Req Failures Service Req Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of service req process failures by a VIP subscriber on the GSM and UMTS network. Service req process success rate by a VIP subscriber on the GSM and UMTS networks. Service req success rate = (1 Number of service req failures/ Number of service req requests) x 100% USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
639
Unit ms
Description Average delay of a service req process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a service req process by a VIP subscriber on the GSM and UMTS networks.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Numb er
SGSN-Relocation
Parameter Relocation Requests Rang e [0, +) Unit Numb er Description Number of relocation process requests by a VIP subscriber on the GSM and UMTS networks. Relocation processes include: Intra SRNS relocation Inter SRNS relocation Relocation Failures Relocation Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of relocation process failures by a VIP subscriber on the GSM and UMTS networks. Relocation process success rate by a VIP subscriber on the GSM and UMTS networks. Relocation success rate = (1 Number of relocation failures/ Number of relocation requests) x 100% Average Relocation Delay Overlong Relocation Delays [0, +) [0, +) ms Average delay of a relocation process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a relocation process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Numb er
Issue 01 (2013-07-15)
640
SGSN-System Change
Parameter System Change Requests Rang e [0, +) Unit Numb er Description Number of system change process requests by a VIP subscriber on the GSM and UMTS networks. System change processes include: 3G to 2G system change 2G to 3G system change System Change Failures [0, +) Numb er Number of system change process failures by a VIP subscriber on the GSM and UMTS networks. System change process success rate by a VIP subscriber on the GSM and UMTS networks. System change success rate = (1 Number of system change failures/Number of system change requests) x 100% Average System Change Delay [0, +) ms Average delay of a system change process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a system change process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0.00, 100.0 0]
[0, +)
Numb er
SGSN-Paging
Parameter Paging Requests Rang e [0, +) Unit Numb er Description Number of paging process requests by a VIP subscriber on the GSM and UMTS networks. The paging process includes Paging. Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
641
Unit Numb er %
Description Number of paging process failures by a VIP subscriber on the GSM and UMTS networks. Paging process success rate by a VIP subscriber on the GSM and UMTS networks. Paging success rate = (1 Number of paging failures/ Number of paging requests) x 100%
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
[0, +) [0, +)
ms
Average delay of a paging process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a paging process by a VIP subscriber on the GSM and UMTS networks.
Numb er
SGSN-PDP Act
Parameter PDP Act Requests Rang e [0, +) Unit Numb er Description Number of PDP act process requests by a VIP subscriber on the GSM and UMTS networks. PDP act processes include: MS Init PDP Act CN Init PDP Act PDP Act Failures PDP Act Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of PDP act process failures by a VIP subscriber on the GSM and UMTS networks. PDP act process success rate by a VIP subscriber on the GSM and UMTS networks. PDP act success rate = (1 Number of PDP act failures/ Number of PDP act requests) x 100% USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
642
Unit ms
Description Average delay of a PDP act process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a PDP act process by a VIP subscriber on the GSM and UMTS networks.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Numb er
SGSN-PDP Act
Parameter PDP Sec Act Requests Rang e [0, +) Unit Numb er Description Number of PDP sec act process requests by a VIP subscriber on the GSM and UMTS networks. The PDP sec act process includes: MS Init PDP Sec Act PDP Sec Act Failures PDP Sec Act Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of PDP sec act process failures by a VIP subscriber on the GSM and UMTS networks. PDP sec act process success rate by a VIP subscriber on the GSM and UMTS networks. PDP sec act success rate = (1 Number of PDP sec act failures/ Number of PDP sec act requests) x 100% Average PDP Sec Act Delay Overlong PDP Sec Act Delays [0, +) [0, +) ms Average delay of a PDP sec act process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a PDP sec act process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Numb er
Issue 01 (2013-07-15)
643
SGSN-PDP Mod
Parameter PDP Mod Requests Rang e [0, +) Unit Numb er Description Number of PDP mod process requests by a VIP subscriber on the GSM and UMTS networks. PDP mod processes include: MS Init PDP Mod CN Init PDP Mod PDP Mod Failures PDP Mod Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of PDP mod process failures by a VIP subscriber on the GSM and UMTS networks. PDP mod process success rate by a VIP subscriber on the GSM and UMTS networks. PDP mod success rate = (1 Number of PDP mod failures/ Number of PDP mod requests) x 100% Average PDP Mod Delay Overlong PDP Mod Delays [0, +) [0, +) ms Average delay of a PDP mod process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a PDP mod process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Numb er
SGSN-RAB Assignment
Parameter RAB Assignment Requests RAB Assignment Failures Rang e [0, +) [0, +) Unit Numb er Numb er Description Number of RAB Assignment requests of a VIP subscriber on the GSM/UMTS network Number of RAB assignment failures of a VIP subscriber on the GSM/UMTS network Supported NE Version USN9810 V900R012C00 or later version USN9810 V900R012C00 or later version
Issue 01 (2013-07-15)
644
Unit %
Description RAB assignment success rate of a VIP subscriber on the GSM/ UMTS network RAB assignment success rate = (1 Number of RAB assignment failures/Number of RAB Assignment requests) x 100%
[0, +) [0, +)
ms
Average RAB assignment delay of a VIP subscriber on the GSM/ UMTS network Number of times that the RAB assignment delay of a VIP subscriber exceeds the predefined exception threshold on the GSM/UMTS network
Numb er
[0.00, 100.0 0]
Issue 01 (2013-07-15)
645
Parameter Average PDN GW Dedicated Bearer Act Delay Overlong PDN GW Dedicated Bearer Act Delays
Ran ge [0, +)
Unit ms
Description Average PDN GW dedicated bearer activation delay of a VIP subscriber on the GSM/UMTS network 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
Supported NE Version USN9810 V900R012C00 or later version USN9810 V900R012C00 or later version
[0, +)
Numbe r
[0.00 , 100.0 0]
Issue 01 (2013-07-15)
646
Ran ge [0, +)
Unit Numbe r
Description Number of times that the PDN GW initiated bearer modification delay of a VIP subscriber exceeds the predefined exception threshold on the GSM/UMTS network
MME-Attach
Parameter Attach Requests Ran ge [0, +) Unit Numbe r Description Number of attach process requests by a VIP subscriber on the LTE network. The attach process includes: Attach Attach Failures [0, +) [0.00 , 100.0 0] Numbe r % Number of attach process failures by a VIP subscriber on the LTE network. Attach process success rate by a VIP subscriber on the LTE network. Attach success rate = (1 Number of attach failures/ Number of attach requests) x 100% ms Average delay of an attach process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an attach process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Numbe r
Issue 01 (2013-07-15)
647
MME-TAU
Parameter Intra TAU Requests Ran ge [0, +) Unit Numbe r Description Number of intra TAU process requests by a VIP subscriber on the LTE network. 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 Intra USN E-UTRAN to UTRAN Inter RAT RAU Intra TAU Failures Intra TAU Success Rate [0, +) [0.00 , 100.0 0] Numbe r % Number of intra TAU process failures by a VIP subscriber on the LTE network. Intra TAU process success rate by a VIP subscriber on the LTE network. Intra TAU success rate = (1 Number of intra TAU failures/ Number of intra TAU requests) x 100% ms Average delay of an intra TAU process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an intra TAU process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Numbe r
Issue 01 (2013-07-15)
648
Ran ge [0, +)
Unit Numbe r
Description Number of inter TAU process requests by a VIP subscriber on the LTE network. 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
Numbe r %
Number of inter TAU process failures by a VIP subscriber on the LTE network. Inter TAU process success rate by a VIP subscriber on the LTE network. Inter TAU success rate = (1 Number of inter TAU failures/ Number of inter TAU requests) x 100%
[0, +) [0, +)
ms
Average delay of an inter TAU process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an inter TAU process by a VIP subscriber on the LTE network.
Numbe r
Issue 01 (2013-07-15)
649
MME-Handover
Parameter Intra E-UTRAN Handover Requests Ran ge [0, +) Unit Numbe r Description Number of intra E-UTRAN handover process requests by a VIP subscriber on the LTE network. Intra E-UTRAN handover processes include: X2 Handover Intra MME S1 Handover Inter MME S1 Handover Intra E-UTRAN Handover Failures Intra E-UTRAN Handover Success Rate [0, +) Numbe r Number of intra E-UTRAN handover process failures by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0.00 , 100.0 0]
Success rate of an intra EUSN9810 UTRAN handover process by a V900R011C01 or VIP subscriber on the LTE later version network. Intra E-UTRAN handover success rate = (1 Number of intra E-UTRAN handover failures/Number of intra EUTRAN handover requests) x 100%
Average Intra EUTRAN Handover Delay Overlong Intra E-UTRAN Handover Delays
[0, +)
ms
Average delay of an intra EUSN9810 UTRAN handover process by a V900R011C01 or VIP subscriber on the LTE later version network. Number of delays that exceed the exception threshold of an intra E-UTRAN handover process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version
[0, +)
Numbe r
Issue 01 (2013-07-15)
650
Ran ge [0, +)
Unit Numbe r
Description Number of inter RAT handover process requests by a VIP subscriber on the LTE network. Inter RAT handover processes include: Intra USN UTRAN Iu mode to E-UTRAN Inter RAT handover Inter USN UTRAN Iu mode to E-UTRAN Inter RAT handover Intra USN E-UTRAN to UTRAN Iu mode Inter RAT handover Inter USN E-UTRAN to UTRAN Iu mode Inter RAT handover
Numbe r %
Number of inter RAT handover process failures by a VIP subscriber on the LTE network. Success rate of an inter RAT handover process by a VIP subscriber on the LTE network. Inter RAT handover success rate = (1 Number of inter RAT handover failures/Number of inter RAT handover requests) x 100%
Average Inter RAT Handover Delay Overlong Inter RAT Handover Delays
[0, +) [0, +)
ms
Average delay of an inter RAT handover process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an inter RAT handover process by a VIP subscriber on the LTE network.
Numbe r
Issue 01 (2013-07-15)
651
MME-Service Req
Parameter Service Req Requests Ran ge [0, +) Unit Number Description Number of service req process requests by a VIP subscriber on the LTE network. The service req process includes: Service Request Service Req Failures Service Req Success Rate [0, +) [0.00 , 100. 00] Number Number of service req process failures by a VIP subscriber on the LTE network. Service req process success rate by a VIP subscriber on the LTE network. Service req success rate = (1 Number of service req failures/ Number of service req requests) x 100% ms Average delay of a service req process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a service req process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Number
MME-Paging
Parameter Paging Requests Ran ge [0, +) Unit Numbe r Description Number of paging process requests by a VIP subscriber on the LTE network. The paging process includes: Paging. Paging Failures [0, +) Numbe r Number of paging process failures by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
652
Unit %
Description Paging process success rate by a VIP subscriber on the LTE network. Paging success rate = (1 Number of paging failures/ Number of paging requests) x 100%
[0, +) [0, +)
ms
Average delay of a paging process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a paging process by a VIP subscriber on the LTE network.
Numbe r
MME-Interoperation
Parameter Interoperation Requests Ran ge [0, +) Unit Numbe r Description Number of interoperation process requests by a VIP subscriber on the LTE network. Interoperation processes include: MME to 3G SGSN combined hard handover and SRNS relocation procedure 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure Interoperation Failures Interoperation Success Rate [0, +) [0.00 , 100. 00] Numbe r % Number of interoperation process failures by a VIP subscriber on the LTE network. Interoperation process success rate by a VIP subscriber on the LTE network. Interoperation success rate = (1 Number of interoperation failures/Number of interoperation requests) x 100% USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
653
Unit ms
Description Average delay of an interoperation process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an interoperation process by a VIP subscriber on the LTE network.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Numbe r
Average Dedicated Bearer Act Delay Overlong Dedicated Bearer Act Delays
[0, +)
[0, +)
Numbe r
Issue 01 (2013-07-15)
654
MME-Bearer Mod
Parameter Bearer Mod Requests Ran ge [0, +) Unit Numbe r Description Number of bearer mod process requests by a VIP subscriber on the LTE network. Bearer mod processes include: PDN GW initiated bearer modification with bearer QoS update HSS Initiated Subscribed QoS Modification PDN GW initiated bearer modification without bearer QoS update Bearer Mod Failures Bearer Mod Success Rate [0, +) [0.00 , 100. 00] Numbe r % Number of bearer mod process failures by a VIP subscriber on the LTE network. Bearer mod process success rate by a VIP subscriber on the LTE network. Bearer mod success rate = (1 Number of bearer mod failures/ Number of bearer mod requests) x 100% ms Average delay of a bearer mod process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a bearer mod process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Numbe r
Issue 01 (2013-07-15)
655
Average Bearer Resource Mod Delay Overlong Bearer Resource Mod Delays
[0, +) [0, +)
Numbe r
MME-PDN
Parameter PDN Connectivity Requests Ran ge [0, +) Unit Numbe r Description Number of PDN connectivity process requests by a VIP subscriber on the LTE network. The PDN connectivity process includes: UE requested PDN connectivity PDN Connectivity Failures [0, +) Numbe r Number of PDN connectivity process failures by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
656
Unit %
Description PDN connectivity process success rate by a VIP subscriber on the LTE network. PDN connectivity success rate = (1 Number of PDN connectivity failures/Number of PDN connectivity requests) x 100%
[0, +) [0, +)
ms
Average delay of a PDN connectivity process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a PDN connectivity process by a VIP subscriber on the LTE network.
Numbe r
GGSN-Create PDP
Parameter Create PDP Requests Create PDP Failures Create PDP Success Rate Ran ge [0, +) [0, +) [0.00 , 100. 00] Unit Numbe r Numbe r % Description Number of Create PDP procedures of a VIP subscriber on the GSM/UMTS network. Number of Create PDP failures of a VIP subscriber on the GSM/ UMTS network. Success rate of the Create PDP procedures of a VIP subscriber on the GSM/UMTS network. Create PDP Success Rate = (1 Number of Create PDP failures/ Number of Create PDP requests) x 100% Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
GGSN-Update PDP
Parameter Update PDP Requests Ran ge [0, +) Unit Numbe r Description Number of Update PDP procedures of a VIP subscriber on the GSM/UMTS network. Supported NE Version UGW9810 V900R011C01 or later version
Issue 01 (2013-07-15)
657
Unit Numbe r %
Description Number of Update PDP failures of a VIP subscriber on the GSM/ UMTS network. Success rate of the Update PDP procedures of a VIP subscriber on the GSM/UMTS network. Update PDP Success Rate = (1 Number of Update PDP failures/ Number of Update PDP requests) x 100%
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
SAE-GW-Modify Bearer
Parameter Create Session Requests Modify Bearer Requests Modify Bearer Failures Modify Bearer Success Rate Ran ge [0, +) [0, +) [0, +) [0.00 , 100. 00] Unit Numbe r Numbe r Numbe r % Description Number of Create Session procedures of a VIP subscriber on the LTE network. Number of Modify Bearer procedures of a VIP subscriber on the LTE network. Number of Modify Bearer failures of a VIP subscriber on the LTE network. Success rate of the Modify Bearer procedures of a VIP subscriber on the LTE network. Modify Bearer Success Rate = (1 Number of Modify Bearer failures/Number of Modify Bearer requests) x 100% Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
SAE-GW-Create Session
Parameter Create Session Failures Ran ge [0, +) Unit Numb er Description Number of Create Session failures of a VIP subscriber on the LTE network. Supported NE Version UGW9810 V900R011C01 or later version
Issue 01 (2013-07-15)
658
Unit %
Description Success rate of the Create Session procedures of a VIP subscriber on the LTE network. Create Session Success Rate = (1 Number of Create Session failures/Number of Create Session requests) x 100%
SAE-GW-Create Bearer
Parameter Create Bearer Requests Create Bearer Failures Create Bearer Success Rate Ran ge [0, +) [0, +) [0.00 , 100. 00] Unit Numb er Numb er % Description Number of Create Bearer procedures of a VIP subscriber on the LTE network. Number of Create Bearer failures of a VIP subscriber on the LTE network. Success rate of the Create Bearer procedures of a VIP subscriber on the LTE network. Create Bearer Success Rate = (1 Number of Create Bearer failures/ Number of Create Bearer requests) x 100% Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
SAE-GW-Update Bearer
Parameter Create Session Requests Create Session Failures Ran ge [0, +) [0, +) Unit Numbe r Numbe r Description Number of Create Session procedures of a VIP subscriber on the LTE network. Number of Create Session failures of a VIP subscriber on the LTE network. Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
Issue 01 (2013-07-15)
659
Unit %
Description Success rate of the Create Session procedures of a VIP subscriber on the LTE network. Create Session Success Rate = (1 Number of Create Session failures/Number of Create Session requests) x 100%
[0, +)
Num ber
Issue 01 (2013-07-15)
660
Unit %
Description Success rate of the Bearer Resource Command procedures of a VIP subscriber on the LTE network. Bearer Resource Command Success Rate = (1 Number of Bearer Resource Command failures/Number of Bearer Resource Command requests) x 100%
[0, +)
Numb er
[0.00 , 100.0 0]
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.
Function Description
The Nastar obtains the call event records of complaining subscribers, and then filters, aggregates, and analyzes data based on a specified history period and detailed call records of subscribers in a specified area. This can assist you in locating and solving problems. The complaint analysis support function consists of the aggregation and analysis of cause types in call reports of complaining subscribers, aggregation and analysis of information about call reports of complaining subscribers, analysis of detailed information about call reports of complaining subscribers, analysis of procedure before signaling release in call reports of complaining subscribers, analysis of active cells in call reports of complaining subscribers, and so on. The function supports the following analysis type: l l 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 3-32. Table 3-32 Function description of complaint analysis support Function Type Aggregation and analysis of cause types in call reports of complaining subscribers Description Helps network engineers filter and aggregate call reports based on exception causes. Supported Network GSM/ UMTS/ LTE/PS Core
Issue 01 (2013-07-15)
662
Description 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, service duration, and so on. 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. 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. 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.
Analysis of procedure before signaling release in call reports of complaining subscribers Analysis of measurement reports (MRs) on calls of complaint subscribers before call release
GSM/ UMTS/LTE
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. Provides information about the serving cells of subscribers before call release and the neighboring cells. This helps engineers analyze and locate problems.
GSM
UMTS/LTE
Mobility analysis
Provides handover information of a terminal and helps network engineers to learn about all cells that are recorded in abnormal call records. Analyzes RAB-related counters and provides network quality information about a service. Geographically displays the cells to which complaining subscribers have gained access and the cells from which complaining subscribers have been released.
Issue 01 (2013-07-15)
663
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.
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 UMTS network, if you want to view the comprehensive measurement report information, 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. 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.
Function Principles
Figure 3-50 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 3-33.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
664
Table 3-33 Description of complaint analysis support User Oper ation 1. Subscr ibe to basic data Scen e GSM / UM TS netw ork Proce dure Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd
Issue 01 (2013-07-15)
Purpose
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. To issue an MML command to the M2000.
eSA U
M2000
M20 00
BSC/ RNC
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
665
Scen e
Purpose
Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd Upload raw data
eSAU
To turn on the data source switch on the NE side. After a user enables the basic data subscription function (PS Core complaint analysis support) on the Nastar client, the Nastar issues a basic data subscription command to the eSAU. To issue an MML command to the M2000.
eSA U
M2000
M20 00
SGSN/ MME
To forward the MML command to the NE, requesting the NE to generate raw data.
PS SAU
Issue a basic data subscri ption comma nd Issue a subscri ption comma nd
eSAU
To turn on the data source switch on the NE side. After 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. To issue a subscription command to the M2000.
eSA U
M2000
Issue 01 (2013-07-15)
666
Scen e
Proce dure Forwar d the subscri ption comma nd Upload raw data
Sour ce M20 00
Purpose
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNod eB/ MM E
l To collect the data from Trace Server after 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 transmission switch is enabled.
Deliver a dataprepro cessing task (direct) Upload prepro cessed data (direct) Upload data analysi s results
Nasta r Serve r
To deliver a data-preprocessing request to the SAU/LTE SAU/PS SAU through the eSAU, requesting the SAU/LTE SAU/PS SAU to start the data-preprocessing task.
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. To display analysis results on the Nastar client.
Nastar Server
Item Execution type Network scale to be analyzed in a task Users to be analyzed in a task
Task Management Capacity One-time task No limited, for all RATs. l Analyzing with IMSI, <= 2,000 users, for all RATs. l Analyzing with MSISDN or peer MSISDN, <= 200 users, for all RATs. <= 500, for all RATs.
NOTE This specification is the sum of all complaint analysis support tasks. It has nothing to do with the number of licenses for complaint analysis support or with the RAT.
Issue 01 (2013-07-15)
668
Table 3-34 Required license and rights of complaint analysis support Functio n Data subscript ion manage ment Required license Data subscription management Required rights (Security > Security Management > User) l Function operation rights Operation Rights > Operation > Nastar System Task Management > Data Subscription Management Authentication 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.
Issue 01 (2013-07-15)
669
Required rights (Security > Security Management > User) l Function operation rights Operation Rights > Operation > Nastar Subject Management > GSM Complaint Analysis Support Operation Rights 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. 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.
CAUT ION If the analy zed IMSI or MSI SDN of comp lainin g user is the same as the VIP user in the VIP grou p mana geme nt funct ion, and you has not the opera tion rights to opera te the VIP user, you are not allow ed to creat e the comp laint analy sis supp ort task about the IMSI or MSI SDN.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > UMTS Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > LTE TDD Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > LTE FDD Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > PS Core Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l GSM / UMT
Issue 01 (2013-07-15)
670
Functio n S comb ined comp laint analy sis supp ort l LTE FDD/ LTE TDD comb ined comp laint analy sis supp ort l RAN side (GS M/ UMT S/ LTE FDD/ LTE TDD ) and PS Core comb ined comp laint analy sis supp ort
Required license support, and UMTS complaint analysis support l LTE FDD complaint analysis support, and LTE TDD complaint analysis support l Complaint analysis support of analyzed network on the RAN side, and PS Core complaint analysis support
Required rights (Security > Security Management > User) Have both involved licenses of Complaint Analysis Support Operation Rights of combined analysis. l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
Table 3-35 Required basic data of complaint analysis support Data Type Configur ation Data (Mandato ry) Function The configuration data of 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 which subscribers have gained access, cells which subscribers have released, and cells to which subscribers have handed over.
NOTE If you only perform the PS Core complaint analysis support, you do not need the configuration data.
Operation If the OSS information has been already configured, the Nastar automatically collects and imports the configuration data after the OSS and NE information is configured. You can also manually collect the configuration data before the specified time period starts. After the configuration data is imported, you can choose Maintenance > Data Maintenance Management to check whether the configuration data is available in the Nastar database. For detailed information about collecting, importing, and checking, see 2.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.
Issue 01 (2013-07-15)
672
Function l Time The Nastar only analyzes complaints that occurred in the latest seven days. 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, MSISDN, or peer MSISDN IMSI: Supported by every network. MSISDN: Only supported by the PS Core network. Peer MSISDN: Only supported by the GSM network when choosing the CS service. You can obtain either the above information of a complaining subscriber for analysis when
Operation Enter the complaining subscriber information when creating complaint analysis support.
NOTE Generally, you obtain the IMSI and MSISDN of a VIP user and enter them into the Nastar. If telecom operators have high requirements for user information security and the anonymous policy is enabled on the network where the Nastar is deployed, all user information such as IMSI, MSISDN, and IMEI contained in the analysis data will be encrypted. To protect the security-sensitive user information, the Nastar no longer allows you to enter the plaintext IMSI and MSISDN. In this situation, you need to contact telecom operators to obtain the encrypted IMSI. The Nastar does not support the encrypted MSISDN. Telecom operators can visit http://support.huawei.com and choose Software Center > Controlled Tool(Mini-tool Software) > Core Network Product Line > Wireless-OSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt user 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 2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key. TIP If the number of complaining subscribers to be analyzed is large, you can save the IMSI, MSISDN or peer MSISDN information in the files in .xls/.xlsx/.csv format. The IMSI information stores a maximum of 2,000 records. Each IMSI must contain 15 digits. The MSISDN or peer MSISDN information stores a maximum of 200 records.
Issue 01 (2013-07-15)
673
Data Type
Operation
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.
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.
The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map.
You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
Issue 01 (2013-07-15)
674
Table 3-36 Description of the data source environment Net wor k GSM Description
l GSM RAN CS analysis : Check that the matching M2000 version is V200R011C00 (or later), and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l GSM RAN PS analysis: Check that the matching M2000 version is V200R012C00 (or later), and the NE version is BSC6900 V900R014C00 (or later), and BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On the User Identity Information Reporting Switch (GSM) in Nastar Commissioning Guide. l (Optional) Only calculating the counters related to speech quality, you need to manually turn on the switches for reporting uplink and downlink speech quality information in MR data. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On the Switches for Reporting Speech Quality Information in MR Data (GSM Complaint Analysis Support, Optional) in Nastar Commissioning Guide. l (Optional) If you want to view the counters about the PS measurement information, check that the PS network control mode is set. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Setting the PS Network Control Mode in Nastar Commissioning Guide.
UM TS
l Check that the matching M2000 version is V200R011C00SPC220 or later and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(UMTS) > Turning On the User Identity Information Reporting Switch (UMTS) in Nastar Commissioning Guide.
Issue 01 (2013-07-15)
675
Description
l Check that the matching M2000 version is M2000 V200R012C00SPC200 or later, the NE version is LTE3900 V100R005C00SPC320 (or later) or LTE3900 V100R008C00SPC020 (or later), and the MME on the CN must be provided by Huawei and the version is USN9810 V900R011C01SPC300 or later.
NOTE 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 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. 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. 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. 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 M2000 versions are consistent with the following information: NE version: USN9810 V900R011C01, USN9810 V900R011C02, USN9810 V900R012C00; UGW9811 V900R009C01, UGW9811 V900R009C02, UGW9811 V900R010C00. M2000 version: M2000 V200R011C01, M2000 V200R012C01, M2000 V200R013C00.
Issue 01 (2013-07-15)
676
Prerequisites
You have finished the preparation of complaint analysis support, such as checking the operation rights, preparing the basic data, and so on. For details, see 3.10.2 Preparations for Complaint Analysis Support.
Procedure
Figure 3-51 shows the process of complaint analysis support. For details, see Table 3-37. Figure 3-51 Flowchart for complaint analysis support
Issue 01 (2013-07-15)
677
Table 3-37 Description of complaint analysis support procedures No. Proced ure Subscrib e to analysis data (basic) Description Reference for Detailed Operations 2.5 Subscribing to Analysis Data
(1)
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator who is authorized to subscribe to basic data to turn on the data switch.
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click *** tab. *** indicates the network. 2. In the left navigation tree, select the NEs to be configured. 3. On the Basic Subscription Settings tab page, click Set. 4. In the displayed Basic Subscription Settings dialog box, set complaint analysis support data to ON. l In the GSM network, the switch name is Complaint Analysis Support Data(CHR-CS), Complaint Analysis Support Data(CHR-PS), and Complaint Analysis Support Data(MRCS) for subscribing to the CHR-CS , CHR-PS data, and MR data of the GSM network. If you have obtained the MR data, you can view the comprehensive measurement report information, and assess business voice quality through VQI accurately. If not, you can only view a small number of measurement reports, and assess voice quality generally. l In the UMTS network, the switch name is Complaint Analysis Support Data(CHR) and Complaint Analysis Support Data(MR) for subscribing to the CHR data and MR data of the UMTS network. If you have obtained the MR data, you can view the comprehensive measurement report information. If not, you can only view a small number of measurement reports. 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 01 (2013-07-15)
678
No.
Proced ure
Description
NOTE l The Nastar cannot issue all MML commands to network elements (NEs) by using the basic subscription function. To obtain data, confirm that you have manually issued the CHR enabled operation. For details, see 3.10.2 Preparations for Complaint Analysis Support. l Disable procedures (such as the Service Request procedure and the PDP MOD procedure) that involve all signaling information on the CN side. Otherwise, a large amount of data is collected from the CN and consequently the SGSN or MME cannot upload the data in time. As a result, certain data required by the Nastar is missing or delayed being reported.
l If you want to view the all signaling information, click , select the interface about All Signaling. 5. Click Confirm. Check that the data switch is successfully turned on by viewing the displayed information in the Log Info area.
Issue 01 (2013-07-15)
679
No.
Description
Reference for Detailed Operations l For details, see 2.7 Creating an Analysis Task. l For details about the parameter s, see Analysis Task Paramete rs.
(2)
Navigation path: Choose Theme Function > User Assurance > Complaint Analysis Support in the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click the Complaint Analysis Support node. 2. Set the task name and task remarks. Click Next. 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 MSISDN: Only supported by the PS Core network. l Peer MSISDN: Only supported by the GSM network when choosing the CS service. l You can obtain either the above information of a complaining subscriber for analysis when supporting multi information. 6. On the Set KPI Threshold tab page, set the abnormal threshold of each KPI. Click Next. 7. Choose an analysis time segment. The Nastar obtains the relevant analysis data in the time period. 8. Click Finish.
Issue 01 (2013-07-15)
680
No.
Description
Reference for Detailed Operations l For details, see 2.8 Querying Analysis Results. l For details on the interface descriptio n, see 3.10.4 Referenc e for Complai nt Analysis Support Interface . l For details, see 2.10 Exportin g Analysis Reports. l For details on the interface descriptio n, see 3.10.4 Referenc e for Complai nt Analysis Support Interface .
(3)
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click an analysis result of the task. 2. In the displayed Complaint Analysis Support window, view the complaint analysis support results
(4)
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. 2. Specify the export path and export format. 3. Click Save.
Issue 01 (2013-07-15)
681
Complaining subscriber information Parameter Set Analysi s Type Analysis Scene Description 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, for the combined complaint analysis support. 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.
Issue 01 (2013-07-15)
682
Description Both access methods can be chosen. Set the data type on the RAN side. l RAN CS Data Access: Analyzes the CS service based on the CS-related data on the RAN side. The LTE network does not involve this parameter. l RAN PS Data Access: Analyzes the PS service based on the PS-related data on the RAN side. Both access methods can be chosen.
NOTE l If you set the analysis scene to PS Core, you do not need to set the data type, because it only supports the PS data on the PS Core. l For UMTS NEs, the CS and PS service information is recorded in one CHR. The SAU cannot filter CHRs by service type. Therefore, after a complaint analysis support task is created, all service information is displayed in the analysis results even though only the CS or PS is selected.
Data Type 2
The system supports the following data on the CS domain and the PS domain: Control Plane: analyze the service based on the control plane data on the RAN side and the CN side.
Select NE(s)
RAN NE
Click Select to select an NE. The lowest level is the base station controller level.
Issue 01 (2013-07-15)
683
Description Add or import the user alias, the IMSIs, and remarks of complaining users.
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.
User 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 user 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 user. Value range: A 15-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, obtain the encrypted IMSI of a VIP user 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.
CAUTION If the input IMSI of complaining user is the same as the VIP user in the VIP group management 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.
MSISDN
Add or export MSISDNs of complaining users. l It is only supported by the PS Core network. l When the anonymous policy is disabled on the network where the Nastar is deployed, enter the MSISDN of a user. Value range: A 1- to 16-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, the Nastar does not support analyzing using the MSISDN.
CAUTION If the input MSISDN of complaining user is the same as the VIP user in the VIP group management 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 MSISDN.
Issue 01 (2013-07-15)
684
Description Add or export peer MSISDNs of complaining users. l It is only supported by the GSM network when choosing the CS service. l When the anonymous policy is disabled on the network where the Nastar is deployed, enter the MSISDN of a user. Value range: A 1- to 16-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, the Nastar does not support analyzing using the MSISDN.
CAUTION If the input peer MSISDN of complaining user is the same as the VIP user in the VIP group management 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 peer MSISDN.
Indicates the RAT of an NE. Indicates the domain of an NE. Domains include signaling planeCS, signaling plane-PS, signaling plane-integration. 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. 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.
Indicates the name of a KPI. Indicates the relationship between the KPI value and KPI 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 01 (2013-07-15)
685
Parameter Date
Description 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 and the end time must precede the current system time.
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.
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. The value of this parameter must not precede the end time of Date.
Main Window
The complaint analysis support results can be displayed in tables, such as call report overview table, subscriber information table, call access information table, call release information table, and handover information table, as shown in Figure 3-52.
Issue 01 (2013-07-15)
686
Issue 01 (2013-07-15)
687
No.
Parame Description ter Button area Provides entries to three functions: l : Displays the complaint analysis support results geographically. For details, see Map Interface. l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview Table_Summary.file format. l : Exports data reports of complaint analysis support. 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 complaint analysis support reports 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 complaint analysis support reports to obtain this type of reports. Overview Table_Summary.file format. The same information with Overview Table_Summary.file format exported from summary reports of complaint analysis support.
Issue 01 (2013-07-15)
688
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. 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. Click the column header to resort this table.
NOTE 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.
Issue 01 (2013-07-15)
689
No.
Parame Description ter 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.
Displays detailed information about the selected subscriber in area 2, including user information, call access information, call release information. For details about parameters, see 3.10.5 Reference for Complaint Analysis Support Parameters (GSM). When the window is opened initially, the area hidden by default.
Issue 01 (2013-07-15)
690
No. (1)
Description 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. (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). 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.
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.
Issue 01 (2013-07-15)
691
No. (1)
Description Lists detailed MR information before call release. The information includes time, measurement object type, and detailed counter information.
(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, minimum, and mediate values. l Counter change trend chart, displaying the change of counter values for a maximum of 20 MRs l Legend Table 3-38 describes the change trend of each measurement counters.
Issue 01 (2013-07-15)
692
Table 3-38 Description of measurement counter change trend chart Counter TA DLRxLevel DLRxQuality /Level Helps identify abnormal releases caused by uplink or downlink interference. Statistic Indication Helps identify abnormal releases caused by poor coverage. Description Displayed as a bar chart. The value ranges from 0 to 63. Displayed as a broken line graph. The value ranges from -47 to -110. 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. 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 Helps identify abnormal releases caused by unbalanced uplink and downlink by analyzing this KPI with DLRxQuality/Level and ULRxQuality/Level. Displays voice quality changes in the process, help evaluate the quality accurately. 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. UL VQI: displayed as a bar chart. The value ranges from 0 to 50. DL VQI: displayed as a broken line graph. The value ranges from 0 to 50.
ULRxQuality /Level
MS/BTS Power
VQI
For details about parameters, see 3.10.5 Reference for Complaint Analysis Support Parameters (GSM).
Map Interface
Click . The map window (the Geographic Observation window) is displayed as shown in Figure 3-56.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 693
No. (1)
Description Entry for basic operations in the map window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
l Complaint Analysis Support: Node for the complaint analysis support theme. A level-2 node under the node indicates a task name. A level-3 node under the node indicates a KPI, such as access/ release cell KPI. If multiple complaint analysis support results windows are open, only one of the windows can be displayed on the map window simultaneously. If a analysis result window is closed, the node for the window in the navigation tree is deleted accordingly. In addition, the rendered layer of the corresponding theme is deleted.
Issue 01 (2013-07-15)
694
No. (3)
(4) (5)
This area is empty for complaint analysis support. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the legends 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 is not imported, the system displays a message in this area.
Main Window
The complaint analysis support results can be displayed in tables, such as call report overview table, subscriber information table, call access information table, call release information table, and handover information table, as shown in Figure 3-57.
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 01 (2013-07-15)
695
Issue 01 (2013-07-15)
696
No.
Parame Description ter Button area Provides entries to three functions: l : Displays the complaint analysis support results geographically. For details, see Map Interface. l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview Table_Summary.file format. l : Exports data reports of complaint analysis support. The following two types of reports are exported. Each type has one report. The default format is .xlsx format. Information Table_Details_UMTS.file format. The exported data includes information about overview tables, subscribers, accesses, releases, handovers, and so on. Alternatively, right-click in area 3 and choose Export complaint analysis support reports to obtain this type of reports. Overview Table_Summary.file format. The same information with Overview Table_Summary.file format exported from summary reports of complaint analysis support. l provides the abnormal cause statistics function of the service. For details, see Common Statistics Interface.
Issue 01 (2013-07-15)
697
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. 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-RNC call history records. If an interRNC 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. Click the column header to resort this table.
NOTE 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 the Signaling Procedure Before Call re area Release Tab Page.
Issue 01 (2013-07-15)
698
No.
Parame Description ter Theme Displays detailed signaling process and MR information about all filtered analysis subscribers. The Nastar analyzes the mobility and service of those area subscribers. For details, see Description of the Measurement Information Before Call Release Tab Page, Description of Mobility Analysis Tab Page, and Description of Service Analysis Tab Page.
Displays detailed information about the selected subscriber in area 2, including user information, call access information, call release information, and statistical information. For details about parameters, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS). When the window is opened initially, the area hidden by default.
Issue 01 (2013-07-15)
699
No. (1)
Description 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 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.
(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). 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.
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.
Issue 01 (2013-07-15)
700
No. (1)
Description Lists detailed MR information before call release. The information includes time, measurement object type, and detailed counter information.
(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, minimum, and mediate values. l Counter change trend chart, displaying the change of counter values for a maximum of 20 MRs l Legend Table 3-39 describes the change trend of each measurement counters.
Issue 01 (2013-07-15)
701
Table 3-39 Description of measurement counter change trend chart Counter Ec/No Statistic Indication Indicates the change trend of the signal intensity according to the received cells of the UE. Indicates the change trend of the signal level according to the received cells of the UE. Indicates the change trend of the RSSI according to the received intercells of the UE. Indicates the change trend of the RSRP according to the received LTE cells of the UE. Indicates the change trend of the RSRQ according to the received inter-cells of the UE. Indicates the change trend of the transmit power of the UE. Description Displayed as a broken line chart.
RSCP
RSSI
RSRP
RSRQ
UE Tx Power
For details, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS).
Figure 3-61 shows the items about the RAB service through the RAB analysis.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 702
Double-click one result, or right-click one result, and choose Detail Service Information, view the detailed service counters of CS domain or PS domain. Right-click one result, and choose Trend Analysis, view the throughput and throughput rate of the RAB on the uplink and downlink at the different time. For details, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS). Figure 3-61 Description of service analysis tab page (RAB)
Map Interface
. The map window (the Geographic Observation window) is displayed as shown in Click Figure 3-62. Figure 3-62 Map interface
Issue 01 (2013-07-15)
703
No. (1)
Description Entry for basic operations in the map window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
l Complaint Analysis Support: Node for the complaint analysis support theme. A level-2 node under the node indicates a task name. A level-3 node under the node indicates a KPI, such as access/ release cell KPI. If multiple complaint analysis support results windows are open, only one of the windows can be displayed on the map window simultaneously. If a analysis result window is closed, the node for the window in the navigation tree is deleted accordingly. In addition, the rendered layer of the corresponding theme is deleted. (3) Geographic observation area Grid detail area Legend area Analysis results are displayed as icons in different colors.
(4) (5)
This area is empty for complaint analysis support. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the legends 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 is not imported, the system displays a message in this area.
l l
Select an executed LTE complaint analysis support task, and double-click an analysis result of the task in the Task Result area. 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
The complaint analysis support results can be displayed in tables, such as call report overview table, subscriber information table, call access information table, call release information table, and handover information table, as shown in Figure 3-63. Figure 3-63 Complaint analysis support interface
Issue 01 (2013-07-15)
705
No.
Parame Description ter Button area Provides entries to three functions: l : Displays the complaint analysis support results geographically. For details, see Map Interface. l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview Table_Summary.file format. l : Exports data reports of complaint analysis support. The following two types of reports are exported. Each type has one report. The default format is .xlsx format. Information Table_Details_LTE.file format. The exported data includes information about overview tables, subscribers, accesses, releases, and handovers. Alternatively, right-click in area 3 and choose Export complaint analysis support reports to obtain this type of reports. Overview Table_Summary.file format. The same information with Overview Table_Summary.file format exported from summary reports of complaint analysis support.
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.
Issue 01 (2013-07-15)
706
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. column header to resort this table.
Click the
NOTE 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 the Signaling Procedure Before Call re area Release Tab Page. Theme Displays detailed signaling process and MR information about all filtered analysis subscribers. The Nastar analyzes the mobility and service of all filtered area subscribers. For details, see Description of the MR Analysis Page, Description of the E-RAB Analysis Tab Page and Description of the Mobility Analysis Tab Page.
Displays detailed information about the selected subscriber in area 2, including user information, call access information, call release information. For details about parameters, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE). When the window is opened initially, the area hidden by default.
Issue 01 (2013-07-15)
707
No. (1)
Description 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. 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). 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.
(2)
Signaling flowchart
Issue 01 (2013-07-15)
708
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).
Map Interface
Click . The map window (the Geographic Observation window) is displayed as shown in Figure 3-68.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 709
No. (1)
Description Entry for basic operations in the map window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
l Complaint Analysis Support: Node for the complaint analysis support theme. A level-2 node under the node indicates a task name. A level-3 node under the node indicates a KPI, such as access/ release cell KPI. If multiple complaint analysis support results windows are open, only one of the windows can be displayed on the map window simultaneously. If a analysis result window is closed, the node for the window in the navigation tree is deleted accordingly. In addition, the rendered layer of the corresponding theme is deleted. (3) Geographic observation area Analysis results are displayed as icons in different colors.
Issue 01 (2013-07-15)
710
Description This area is empty for complaint analysis support. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the legends 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 is not imported, the system displays a message in this area.
Navigation Path
Use either of the following methods to open the interface that displays PS core complaint analysis support results: l l Select a finished PS core 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 Result from the shortcut menu.
Interface
PS core complaint analysis support results can be displayed in tables to show CHR summary information, CHR information, subscriber information, and procedure information, as shown in Figure 3-69.
Issue 01 (2013-07-15)
711
Issue 01 (2013-07-15)
712
No. 1
Description Provides entries to three functions: l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview table_Summary.file format. l : Exports data reports of complaint analysis support. The exported data includes information about overview tables, subscribers, call accesses, call releases, and call handovers. Alternatively, right-click in area 3 and choose Export complaint analysis support reports to obtain this type of reports. l provides the traffic statistics function. For details, see Traffic Statistics on the Interface.
Navigati l Upper part: Displays the service types. You can select the service types. on tree l Middle part: Call records of multiple subscribers are displayed by cause of the type in the navigation tree mode. (N) after each node indicates the number CHR 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. summar In Cause type-User ID: Alias mode, all filtered call records are y of classified by cause type and the call records of each cause type are complai then classified by User ID: Alias. ning 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.
Issue 01 (2013-07-15)
713
No. 3
Description Displays an overview of all filtered records, such as time, cell, procedure, and exception cause. Each row indicates one call record. row is abnormal. Click the indicates that the call record in the
NOTE For some columns (such as User ID: Alias), the system only centralized display the same content, but there is no display order after resorting.
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 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 3.10.8 Reference for Complaint Analysis Support Parameters (PS Core). The table is hidden by default when you initially open the window.
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 GGSN Procedure or SAE-GW Procedure under Service Type. Traffic subnodes are displayed under Root. 2. Select a Traffic subnode to view traffic information by subscriber.
Function Description
The Nastar allows you to perform complaint analysis support based on the data collected from different types of networks simultaneously. For example, it allows you to perform GSM/UMTS complaint analysis support and LTE FDD/LTE TDD complaint analysis support. It also allows you to perform complaint analysis support based on the data collected from the RAN and the PS core network simultaneously. Therefore, the Nastar supports combined complaint analysis support in the following combinations of RATs: GSM/UMTS, LTE FDD/LTE TDD, GSM/PS Core, UMTS/PS Core, LTE TDD/PS Core, LTE FDD/PS Core, GSM/UMTS/PS Core, and LTE FDD/LTE TDD/PS Core.
Navigation Path
Use either of the following methods to open the interface that displays combined complaint analysis support results: l 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 Result from the shortcut menu.
Interface description
The interface that displays the combined complaint analysis support results of multiple RATs is generally the same as the interface that displays the complaint analysis support results of a single RAT: l The service types displayed in the navigation tree are combinations of the service types for the complaint analysis support of involved RATs. For example, if the service types for GSM complaint analysis support include RAN CS (Call\SMS\others) and the service types for UMTS complaint analysis support include RAN NET, RAN CS (AMR\VP\SMS\others)), RAN PS, and RAN Multi, the service types for GSM/UMTS complaint analysis support include RAN NET, RAN CS (AMR\VP\Call \SMS\others), RAN PS, and RAN Multi. l The cause types displayed in the navigation tree are combinations of the cause types for the complaint analysis support of involved RATs. The description of the exception causes for each RAT provides the mapping between service types and cause types. For details, see 3.10.9 Appendix: Exception Cause Classification / Key Signaling. l The information displayed in the middle and right areas on the interface varies according to the call history record (CHR) that you select in the navigation tree. One CHR belongs to only one RAT. Therefore, for descriptions of related interfaces and parameters, see the interface reference for the complaint analysis support of each RAT.
Summary
Para mete r Serial Num ber Range Uni t N/A Description Supported NE Version BSC6900 V900R013C00 or later version
(0,2^31-1)
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. 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.
Comb ined
N/A
N/A
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.
For details, see "Appendix: Exception Cause Classification / Key Signaling (GSM)".
N/A
Cause of the exception carried in an Access Request message. Note: The HQIs after the call setup is successful are only counted in the abnormal cause.
Netw ork
GSM-CS, GSM-PS
N/A
Issue 01 (2013-07-15)
716
Range
Uni t N/A
Description
Non-SMS message from a mobile-originated VIP subscriber (AC_ORIGIN_CALL_N O_SMS) SMS message from a mobile-originated VIP 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) 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) Incoming inter-BSC handover (AC_IN_BSC_HO)
Issue 01 (2013-07-15)
717
Para mete r
Range
Uni t
Description
Supported NE Version
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 ) Non-SMS message from a mobile-terminated VIP subscriber (AC_ANSWER_TO_PA GING_CALL) SMS message from a mobile-terminated VIP subscriber (AC_ANSWER_TO_PA GING_CALL) Normal location update (AC_LOCATION_UPD ATE_NORMAL) Periodic location update (AC_LOCATION_UPD ATE_PERIODIC) IMSI attachment (AC_LOCATION_UPD ATE_ATTACH) Acces s Time N/A N/A Signaling access time for a call, namely, the time when a MS sends the Channel Request message. BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
718
Range
Uni t N/A
Description
N/A
Name of the cell in which a MS sends the Channel Request message. 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. In the preceding format, BSC OPC is the originating signaling point configured on the BSC side.
Relea se Time
N/A
N/A
Signaling release time for a call, namely, the time when a MS receives the Channel Release message.
Relea se Cell
N/A
N/A
Name of the cell in which a MS receives the Channel Release message. 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.
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
Issue 01 (2013-07-15)
719
Range
Uni t N/A
Description
00000000-99999999
International mobile equipment identity-type allocation code (IMSI-TAC) of a VIP subscriber, which is the first eight digits in the IMEI of a UE. Type of a MS. You can obtain the IMEITACs of the UE from the MS type management function.
Mode l
N/A
N/A
N/A
N/A
Mobile station international ISDN number (MSISDN) of a peer subscriber. Service duration covering the call duration and the signaling setup duration. Service duration = Release time - Access time
[0,+)
Sec ond
[0,+)
Sec ond
Call duration. Call duration = Time stamp of the Disconnect message Time stamp of the Connect Acknowledge message
Issue 01 (2013-07-15)
720
Range
Uni t N/A
Description
Following are criteria indicating a proper call setup: 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. 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. 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.
Network access result for a mobile-originated call. The result indicates a proper call setup or an abnormal call setup. 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.)
Issue 01 (2013-07-15)
721
Para mete r
Range
Uni t
Description
Supported NE Version
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 Following are criteria indicating a proper call release: 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 inter-RAT handover is triggered and completed. Following are criteria indicating an abnormal release of traffic channel during a call: 1. An outgoing inter-BSC handover fails. 2. An intra-BSC handover fails. 3. The BSC releases channel resources. 4. The MSC releases channel resources. N/A Network release result for a mobile-originated call. The result indicates a proper call release or an abnormal call release. BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
722
User Information
Parame ter User ID:Alias IMEITAC Model Range N/A Unit N/A Description Refer to "User ID:Alias" in the Summary area. Refer to "IMEI-TAC" in the Summary area. Refer to "Model" in the Summary area. Capability of the MS. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Yes No
N/A
Yes No
N/A
Yes No
N/A
Whether a MS supports the VAMOS. VAMOS, voice services over adaptive multi-user channels on one slot.
Yes No
N/A
Whether a MS supports the U900. That is, whether a MS supports accessing to the 3G network using the 900 MHz/ 850 MHz band of the 2G network.
Peer MSISD N
N/A
N/A
Issue 01 (2013-07-15)
723
N/A
N/A
[0,71]
N/A
Access Channel
[0,7]
N/A
Access Type
N/A
N/A
MOC MTC
N/A
According to the access causes to identify the user's current business is accessed by MTC or MOC. According to the access causes to identify the user's current business is accessed by SMS or Voice. Network access result for a mobile-originated call. 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.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
SMS Voice
N/A
N/A
N/A
Issue 01 (2013-07-15)
724
Range N/A
Unit N/A
Description 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.
N/A
N/A
Detailed cause of an abnormal signaling access for a call. See the level-3 cause, Sub-Cause of Abnormal Call Setup, in Call Setup Result/Cause of Abnormal Call Setup/Sub-Cause of Abnormal Call Setup in General Evaluation.
Access Delay Estimati on >ASSIG NMENT COMPL ETE Message Timesta mp >Access Delay
N/A
N/A
N/A
N/A
Time when the assignment is finished after initiating a call and accessing the network.
[0,+)
Secon d
Access delay time of the service. Access Delay = Time of ASSIGNMENT COMPLETE Time of CHANNEL REQUEST ="ASSIGNMENT COMPLETE Message Timestamp"-"Access Time"
Yes No
N/A
Whether the abnormal of overlong access delay is occurred. The abnormal threshold is set when creating tasks.
>Alertin g Time
N/A
N/A
Time when a VIP subscriber hears the alerting after initiating a call.
Issue 01 (2013-07-15)
725
Parame ter >Call Complet ion Delay (Alertin g) >Overlo ng Call Complet ion Delay (Alertin g) >Connec t Acknow ledge Time >Call Complet ion Delay (Connec t Ack)
Range [0,+)
Unit Secon d
Description Call completion delay time of the service. Call Completion Delay(Alerting) = Time of ALERTING - Time of CHANNEL REQUEST =Alerting Time - Access Time
Yes No
N/A
Whether the abnormal of overlong call completion delay (Alerting) is occurred. The abnormal threshold is set when creating tasks.
N/A
N/A
Time when a VIP subscriber hears the voice of the peer subscriber after initiating a call.
[0,+)
Secon d
Call completion delay time of the service. Call Completion Delay(Connect Ack) = Time of CONNECK ACK - Time of CHANNEL REQUES REQUEST =Connect Acknowledge Time Access Time
>Overlo ng Call Complet ion Delay (Connec t Ack) Measure ment Informat ion On Access >TA
Yes No
N/A
Whether the abnormal of overlong call completion delay (Connect Ack) is occurred. The abnormal threshold is set when creating tasks.
N/A
N/A
[0,63]
N/A
Issue 01 (2013-07-15)
726
Range Yes No
Unit N/A
Description Whether the abnormal that TA is too large when accessing to the network is occurred. The abnormal threshold is set when creating tasks.
[-110,-47]
dBm
Value of the RACH level when a MS accesses to the network. Whether the abnormal that RACH Level is too small is occurred. The abnormal threshold is set when creating tasks.
Yes No
N/A
[0,+)
Secon d N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
727
Range N/A
Unit N/A
Description Cause of an abnormal signaling release during a call. See the level-2 cause, Cause of Abnormal Call Release, in Call Release Result/Cause of Abnormal Call Release/SubCause of Abnormal Call Release in General Evaluation.
N/A
N/A
Detailed cause of an abnormal signaling release during a call. See the level-3 cause, Sub-Cause of Abnormal Call Release, in Call Release Result/Cause of Abnormal Call Release/SubCause of Abnormal Call Release in General Evaluation.
CS Service Information
Parame ter Service Process Delay Estimati on >IntraBSC Channel Release Timesta mp >Calling Duration Range N/A Unit N/A Description Delay estimation for service process. Supported NE Version BSC6900 V900R013C00 or later version
N/A
N/A
[0,+)
Secon d
Calling Duration = Time of DISCONNECT - Time of CONNECT ACK =Intra-BSC Channel Release Timestamp - CONNECT ACK Timestamp
>Short Call
Yes No
N/A
Whether the abnormal of short call is occurred. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
728
Parame ter Service Quality Estimati on for Service Process >Uplink Oneway Audio During a Call
Range N/A
Unit N/A
Yes No
N/A
Whether uplink one-way audio occurs during a call. 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 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 threshold, the BSS determines that primary uplink one-way audio occurs, and starts the mechanism for confirming the occurrence of primary uplink one-way audio. During this process, the BSC sends a message to the BTS demanding that the BTS send a test TRAU frame to the TC. If the TC fails to receive the test TRAU frame from the BTS within a specified time period, one-way audio occurs on the uplink voice channel.
Issue 01 (2013-07-15)
729
Range Yes No
Unit N/A
Description Whether downlink one-way audio occurs during a call. 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 Um and A interfaces. Principle for detecting downlink one-way audio: The DSP in the DTRU of the BTS performs periodic statistics on the bad frame rate based on downlink TRAU frames. When the bad frame rate reaches the predefined threshold, the BSS determines that primary downlink one-way audio occurs, and starts the mechanism for confirming the occurrence of primary downlink one-way audio. During this process, the BSC sends a message to the TC demanding that the TC send a test TRAU frame to the BTS. If the BTS fails to receive the test TRAU frame from the TC within a specified time period, oneway audio occurs on the downlink voice channel.
Yes No
N/A
Whether uplink crosstalk occurs during a call. 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 uplink crosstalk: The DSP of the BTS inserts the unique identifier of a call into the free bits of uplink voice TRAU frames. The DSP of the TC decodes the unique call identifiers and checks their consistency. If inconsistency in the unique call identifiers is detected within the test period, uplink crosstalk occurs.
Issue 01 (2013-07-15)
730
Range Yes No
Unit N/A
Description Whether downlink crosstalk occurs during a call. 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 uplink voice TRAU frames. The DSP of the BTS decodes the unique call identifiers and checks their consistency. If inconsistency in the unique call identifiers is detected within the test period, downlink crosstalk occurs.
N/A
Whether uplink noise occurs during a call, which is detected by the device. Whether downlink noise occurs during a call, which is detected by the device. Average value for the uplink high quality indicators (HQIs) of call setups that include the HQIs before and after the call setup is successful. 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 reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
Issue 01 (2013-07-15)
731
Range Yes No
Unit N/A
Description Whether the abnormal of bad uplink HQI is occurred of call setups that include the HQIs before and after the call setup is successful. The abnormal threshold is set when creating tasks.
[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. In CHRs of the BSC6900 V900R011 or any later version: HQI = Number of measurement reports indicating a voice quality of levels 0 to 3/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
Yes No
N/A
Whether the abnormal of bad downlink HQI is occurred of call setups that include the HQIs before and after the call setup is successful. The abnormal threshold is set when creating tasks.
[1.00,5.00]
N/A
Average value for the uplink voice quality indicators (VQIs) of successful call setups. 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/ Total number of uplink VQI tests
Issue 01 (2013-07-15)
732
Range Yes No
Unit N/A
Description Whether the abnormal of bad uplink VQI is occurred. The abnormal threshold is set when creating tasks.
Measure ment Informat ion On Service Process >Averag e Uplink Level >Averag e Downlin k Level >Averag e Uplink Quality >Averag e Downlin k Quality
N/A
N/A
[-110,-47]
dBm
Average uplink level on service process. Average downlink level on service process.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[-110,-47]
dBm
[0,7]
N/A
Average uplink quality on service process. Average downlink quality on service process.
[0,7]
N/A
N/A
N/A
Uplink Downlink
N/A
Issue 01 (2013-07-15)
733
Range N/A
Unit N/A
Description 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. Content of a signaling message. You can obtain the content of a signaling message by viewing the related tree structure.
Signalin g Content
N/A
N/A
N/A
N/A
N/A
N/A
Server Nbr1~6
N/A
Issue 01 (2013-07-15)
734
Unit N/A
Description Base transceiver Station Identity Code (BSIC) of a neighboring cell, reported in a measurement report.BSIC has 6 bits, the first part is NCC, the last past is BCC. TA of a serving cell, reported in a measurement report. Downlink RxLevel of a serving cell and that of a neighboring cell, reported in a measurement report. Uplink RxLevel of a serving cell, reported in a measurement report. Downlink RxQuality of a serving cell, reported in a measurement report. Uplink RxQuality of a serving cell, reported in a measurement report. BTS power of a serving cell, reported in a measurement report. MS power of a serving cell, reported in a measurement report.
TA
[0,63]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RxLevel (Downli nk) RxLevel (Uplink) RxQualit y (Downli nk) RxQualit y (Uplink) BTS Power MS Power
[-110,-47]
dBm
[-110,-47]
dBm
[0,7]
N/A
[0,7]
N/A
[0,15]
N/A
[0,31]
N/A
Mobility Analysis
Parame ter Number Range [0,+) Unit Numb er N/A Description Number for a handover triggered during a call. Whether a record indicates an abnormal handover. The record indicates an abnormal handover if a red exclamation mark is displayed.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Abnorm al
N/A
735
Range Communicat ion resumes on the original channel after a handover failure the BSC releases channel resources the MSC is faulty
Unit N/A
Description Whether a handover succeeds, and the cause of a handover failure. The cause is displayed as Normal if a handover succeeds. 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.
Type
Intra-BSC handover Outgoing cell handover Incoming inter-BSC handover Outgoing inter-BSC handover Outgoing inter-RAT handover
N/A
Type of a handover
Initiatin g Time
N/A
N/A
Time when a handover is initiated, namely, the time when the BSC sends the Handover CMD message.
Duration
[0,+)
N/A
Issue 01 (2013-07-15)
736
Range Yes No
Unit N/A
Description The first case: "Handover Type" is "Outgoing inter-BSC handover" If the duration is more than "Outgoing BSC Handover Interval", it displays "Yes"; If not, it displays "No". The second case: "Handover Type" is "Outgoing inter-RAT handover" If the duration is more than "Outgoing System Handover Interval", it displays "Yes"; If not, it displays "No". The other case: displays null. "Outgoing BSC Handover Interval" and "Outgoing System Handover Interval" is set when creating tasks.
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Cause of a handover.
N/A
N/A
Name of the source cell to be handed over. The parameter is displayed in the following format: Name of the BSC: Name of the cell (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. In the preceding format, BSC OPC is the originating signaling point configured on the BSC side.
N/A
N/A
737
Range N/A
Unit N/A
Description Name of the target cell to which a handover is to be performed. The parameter is displayed in the following format: Name of the BSC: Name of the cell (BSC OPC: ID of the cell). You can obtain the names of the BSC and the cell from the configuration data.
Summary
Param eter Serial Number Range (0,2^31-1) Unit N/A Description 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. 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. 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. Supported NE Version BSC6900 V900R013C01 or later version
Combin ed
N/A
N/A
Issue 01 (2013-07-15)
738
Range For details, see "Appendix: Exception Cause Classification / Key Signaling (GSM)". GSM-CS, GSMPS
Unit N/A
Networ k
N/A
Issue 01 (2013-07-15)
739
Range Non-SMS message from a mobile-originated VIP subscriber (AC_ORIGIN_C ALL_NO_SMS) SMS message from a mobileoriginated VIP subscriber (AC_ORIGIN_C ALL_SMS) Answer to paging (AC_ANSWER_ TO_PAGING) Call re-setup (AC_CALL_RE_ ESTABLISH) Emergency call (AC_EMERGEN CY_CALL) Location update (AC_LOCATION _UPDATE) IMSI detachment (AC_IMSI_DET ACH) Data service (AC_PACKET_C ALL) LMU service (AC_LMU_EST ABLISH) SS service (AC_SS_ESTAB LISH) VGCS service (AC_VGCS_EST ABLISH) VBS service (AC_VBCS_EST ABLISH) LCS service (AC_LCS_ESTA BLISH)
Unit N/A
Issue 01 (2013-07-15)
740
Param eter
Range Any other service (AC_RESERVE D) Incoming interBSC handover (AC_IN_BSC_H O) Response to notification (AC_NOTIFICA TION_RSP) Immediate setup (AC_IMM_SET_ UP) RR initialization (AC_RR_INITIA LISATION_REQ ) Indication from talker (AC_TALKER_I NDICATION) VGCS access (AC_VGCS_VBS _VPCS) Non-SMS message from a mobileterminated VIP subscriber (AC_ANSWER_ TO_PAGING_C ALL) SMS message from a mobileterminated VIP subscriber (AC_ANSWER_ TO_PAGING_C ALL) Normal location update (AC_LOCATION _UPDATE_NOR MAL) Periodic location update
Unit
Description
Supported NE Version
Issue 01 (2013-07-15)
741
Param eter
Unit
Description
Supported NE Version
Access Time
N/A
N/A
Signaling access time for a call, namely, the time when a MS sends the Channel Request message. Name of the cell in which a MS sends the Channel Request message. 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
Access Cell
N/A
N/A
Release Time
N/A
N/A
Signaling release time for a call, namely, the time when a MS receives the Channel Release message.
Release Cell
N/A
N/A
Name of the cell in which a MS receives the Channel Release message. 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 display
User ID:Alia s
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
Issue 01 (2013-07-15)
742
Range 00000000-999999 99
Unit N/A
Description International mobile equipment identity-type allocation code (IMSI-TAC) of a VIP subscriber, which is the first eight digits in the IMEI of a UE. Type of a MS. You can obtain the IMEI-TACs of the UE from the MS type management function.
Model
N/A
N/A
N/A
N/A
Mobile station international ISDN number (MSISDN) of a peer subscriber. Service duration covering the call duration and the signaling setup duration. Service duration = Release time - Access time
[0,+)
Seco nd
Cause of Downli nk TBF Setup Failure Cause of Abnorm al Downli nk TBF Release Cause of Uplink TBF Setup Failure Cause of Abnorm al Uplink TBF Release
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
743
User Information
Param eter User ID:Alia s IMEITAC Model Range N/A Unit N/A Description Refer to "User ID:Alias" in the Summary area. Refer to "IMEI-TAC" in the Summary area. Refer to "Model" in the Summary area. Capability of the MS. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
MS Capabil ity >Suppo rt GPRS >Suppo rt GPRS MultiSlot Class >Suppo rt EGPRS >Suppo rt EGPRS MultiSlot Class >Suppo rt 900M E Frequen cy Band >Suppo rt 1800M Frequen cy Band
N/A
N/A
N/A
N/A
N/A
N/A
Support Unsupport
N/A
Support Unsupport
N/A
Issue 01 (2013-07-15)
744
Param eter >Suppo rt G-TD DualMode >Suppo rt G-U DualMode >Suppo rt DTM >Suppo rt PS Handov er Insuffic ient Termin al Capabil ity
Unit N/A
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Support Unsupport
N/A
N/A
Whether a Terminal supports DTM. Whether a Terminal supports handovers in the PS domain.
N/A
Yes No
N/A
The capability of a Terminal is insufficient in the case of the following: The Terminal supports GPRS but not EGPRS. The Terminal supports EGPRS but the EGPRS multislot class is below 10.
Subscri ber Registra tion Paramet er >Reliab ility Level >Subscr iption Rate
N/A
N/A
Parameters related to the service that a VIP subscriber subscribes to when opening an account.
N/A
N/A
For details about the parameter, see see 3GPP TS 23.107. For details about the parameter, see see 3GPP TS 23.107.
N/A
N/A
Issue 01 (2013-07-15)
745
Range Yes No
Unit N/A
Description An account-opening exception occurs in the case of the following: The reliability class of a VIP subscriber is not 3, namely, the reliability class is not the RLC acknowledged mode. The subscription rate is lower than the predefined exception threshold (which is set by engineers when creating tasks).
Peer Information
Param eter Number of Server Applica tions List of Servers and Applica tions >IP Address >Server Name Rang e N/A Unit N/A Description Total number of the server applications that a VIP subscriber accesses when attempting to use a data service. Supported NE Version BSC6900 V900R013C01 or later version
N/A
N/A
N/A
N/A
IP address of the server that a VIP subscriber accesses when attempting to use a data service. Name of the server that a VIP subscriber accesses when attempting to use a data 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 Port number of the server that a VIP subscriber accesses when attempting to use a data service.
N/A
N/A
>Port
[0,65 535)
N/A
Issue 01 (2013-07-15)
746
Rang e N/A
Unit N/A
Description name of the application that a VIP subscriber accesses when attempting to use 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
[0,63 ]
N/A
[0,7]
N/A
GMSK MEAN BEP upon Access 8PSK MEAN BEP upon Access Access Cell
[0,31 ]
N/A
[0,31 ]
N/A
Information about the 8PSK MEAN BEP when a Terminal sends the Channel Request message.
N/A
N/A
Name of the cell in which a MS sends the Channel Request message. 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
Issue 01 (2013-07-15)
747
Ran ge N/A
Uni t N/A
Description Time when a VIP subscriber releases a data service. Duration of the data service used by a VIP subscriber. 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. Number of access requests on the RACH (uplink CCCH) during the whole process for a subscriber to use a data service.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +) N/A
[0, +)
Nu mbe r
Issue 01 (2013-07-15)
748
Param eter PDP Active Accept Times PDP Active Reject Times RA Update Request Times RA Update Accept Times RA Update Reject Times Suspen d Times
Ran ge [0, +)
Description Number of the PDP Active Accept messages that a VIP subscriber receives during the whole process of using a data service. Number of the PDP Active Reject messages that a VIP subscriber receives during the whole process of using a data service. Number of the RA Update Request messages that a VIP subscriber sends during the whole process of using a data service. Number of the RA Update Accept messages that a VIP subscriber receives during the whole process of using a data service. Number of the RA Update Reject messages that a VIP subscriber receives during the whole process of using a data service. Number of Suspends during the whole process for a VIP subscriber to use a data service.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +)
[0, +)
[0, +)
[0, +)
[0, +)
N/A
N/A
Issue 01 (2013-07-15)
749
Rang e N/A
Unit N/A
Description Carrier of a TBF setup failure on the downlink. BCCH of a TBF setup failure on the downlink. Number of TBF setup failures on the uplink.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
Times of Uplink TBF Setup Failure >Cause s of Uplink TBF Setup Failure >Carrie r Index >BCCH
N/A
Num ber
N/A
N/A
N/A
N/A
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
Times of Abnor mal Downli nk TBF Release >Cause s of Abnor mal Downli nk TBF Release >Carrie r Index
[0, +)
Num ber
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
750
Rang e N/A
Unit N/A
Description BCCH of an abnormal TBF release on the downlink. Number of abnormal TBF releases on the uplink.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Times of Abnor mal Uplink TBF Release >Cause s of Abnor mal Uplink TBF Release >Carrie r Index >BCCH
[0, +)
Num ber
N/A
N/A
N/A
N/A
Carrier of an abnormal TBF release on the uplink. BCCH of an abnormal TBF release on the uplink.
N/A
N/A
[0, +) [0, +)
Byte
Size of the data transmitted by using the downlink PDU. Maximum duration for data transmission by using the downlink PDU.
Seco nd
Issue 01 (2013-07-15)
751
Param eter >Total Duratio n on Sendin g PDU >Sent Count >Avera ge Duratio n on Sendin g PDU >Sendi ng Timeou t Times
Rang e [0, +)
Unit Seco nd
Description Overall duration for data transmission by using the downlink PDU.
[0, +) [0, +)
Total number of the blocks transmitted by using the downlink PDU. Average duration for data transmission by using the downlink PDU.
[0, +)
Num ber
Number of times that the duration for data transmission by using the downlink PDU exceeds the predefined threshold. A device is configured to directly check whether the duration for data transmission by using the PDU exceeds the predefined threshold.
Uplink PDU >Recei ved Bytes >Maxi mum Duratio n on Receivi ng PDU >Total Duratio n on Receivi ng PDU >Recei ved Count
N/A
N/A
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +) [0, +)
Byte
Size of the data transmitted by using the uplink PDU. Maximum duration for data transmission by using the uplink PDU.
Seco nd
[0, +)
Seco nd
[0, +)
Num ber
Issue 01 (2013-07-15)
752
Param eter >Avera ge Duratio n on Receivi ng PDU >Recei ving Timeou t Times
Rang e [0, +)
Unit Seco nd
Description Average duration for data transmission by using the uplink PDU.
[0, +)
Num ber
Number of times that the duration for data transmission by using the uplink PDU exceeds the predefined threshold. A device is configured to directly check whether the duration for data transmission by using the PDU exceeds the predefined threshold.
Uplink/ Downli nk PDU >Maxi mum Interval Duratio n >Total Interval Duratio n >Numb er of Interval s >Avera ge Interval Duratio n >Numb er of Interval Timeou ts
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. Maximum interval for data transmission between the uplink and downlink PDUs.
[0, +)
Seco nd
[0, +)
Seco nd
Aggregated interval of all the intervals for data transmission between every two datatransmission time points on the uplink and downlink PDUs. Number of times that an interval for data transmission between the uplink and downlink PDUs is available. Average interval for data transmission between the uplink and downlink PDUs.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +)
Num ber
[0, +)
Seco nd
[0, +)
Num ber
Number of times that the interval for data transmission between the uplink and downlink PDUs exceeds the predefined threshold. A device is configured to directly check whether the interval for data transmission between the uplink and downlink PDUs exceeds the predefined threshold.
Issue 01 (2013-07-15)
753
Param eter >Uplin k Data Availab le and Downli nk Data Unavail able Occurre nce Times Numbe r of No Service Interact ion Timeou t Times
Rang e [0, +)
Description Number of times that the uplink PDU carries data but downlink PDU does not. A device is configured to directly check whether the uplink PDU carries data while the downlink PDU does not.
[0, +)
Num ber
Number of times that no service interaction responses. 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.(A = Number of times that the uplink PDU carries data but the downlink PDU does not). The exception thresholds 1 and 2 for the response to service interaction are internal algorithm parameters.
[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. 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 Number of Interval Timeouts for data transmission between the uplink and downlink PDUs.
Issue 01 (2013-07-15)
754
Rang e [0, +)
Description Average duration for the response to service interaction during the whole process for a VIP subscriber to use a data service. Average duration for the response to service interaction = Average duration for data transmission by using the downlink PDU + Average duration for data reception by using the uplink PDU + Average duration for data transmission between the uplink and downlink PDUs.
Yes No
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. If the average duration for the response to service interaction is above the upper threshold for the average duration for the response to service interaction, the average duration for the response to service interaction overlong. The threshold is set by engineers during analysis task creation.
[0, +)
Byte
Issue 01 (2013-07-15)
755
Param eter >Durati on for Sendin g PDU at Downli nk >PDU Bytes Receive d at Uplink >Down load Speed (Kbps)
Ran ge [0, +)
Unit Secon d
Description Overall duration for data transmission by using the downlink PDU.
[0, +)
Byte
[0, +)
Kbps
Average download rate during the whole process for a subscriber to use a data service. Download rate = Number of bytes transmitted by using the downlink PDU/ Duration for data transmission by using the downlink PDU
Yes No
N/A
Number of low download rate exceptions during the whole process for a subscriber to use a data service. If a download rate is lower than the lower threshold for download rate, the download rate is low. The threshold is set by engineers when creating tasks.
[0, +)
Num ber
[0, +)
Num ber
Number of exceptions where downlink TCP disorder occurs during the whole process for a subscriber to use a data service.
Issue 01 (2013-07-15)
756
Param eter >Avera ge Occupi ed Downli nk Slots >Down load MultiSlot Statisfa ction Ratio
Ran ge [1,6]
[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/ Multislot Class of the Terminal When Supporting GPRS.
>Trans mission Resour ces Require d for Code Request ed by Downli nk Block
[0, +)
Num ber
Issue 01 (2013-07-15)
757
Param eter >Trans mission Resour ces Used by Code Assigne d to Downli nk Block >Resou rce Statisfa ction Ratio of Downli nk Averag e SingleSlot Throug hput (%) >GPRS Service Flag >>Num ber of Downli nk CS1~4 Blocks/ Valid Blocks >>Num ber of Total Blocks Sent at Downli nk
Ran ge [0, +)
Description Number of transmission resources actually used for the encoding of downlink blocks.
[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%
N/A
N/A
Information about the data service that a VIP subscriber uses through GPRS. 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.
[0, +)
Num ber
[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
Issue 01 (2013-07-15)
758
Ran ge [0, +)
Description Total number of the valid blocks transmitted on the downlink = 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
[0, +)
Byte
Total number of the bytes contained in the valid blocks transmitted on the downlink = Number of the valid blocks transmitted on the downlink by using various channel coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the downlink by using CS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the downlink by using CS-4 x Number of the bytes contained in one valid block For details about the relation between a specific channel coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.2.
>>Dow nlink Retrans mission Ratio >>Dow nlink Reuse Ratio >EGDE Service Flag
[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 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 Information about the data service that a VIP subscriber uses through EGDE.
[0.00, +)
N/A
N/A
N/A
Issue 01 (2013-07-15)
759
Param eter >>Num ber of Downli nk MCS1~ 9 Blocks/ Valid Blocks >>Num ber of Total Blocks Sent at Downli nk
Ran ge [0, +)
Description Total number of the blocks, and that of the valid blocks, transmitted on the downlink by using modulation and coding schemes MCS-1 through MCS-9.
[0, +)
Num ber
Total number of the blocks transmitted on the downlink = Total number of the blocks transmitted on the downlink by using various modulation and coding schemes = Number of the blocks transmitted on the downlink by using MCS-1 ++ Number of the blocks transmitted on the downlink by using MCS-9
[0, +)
Num ber
Total number of the valid blocks transmitted on the downlink = Total number of the valid blocks transmitted on the downlink by using various modulation and coding schemes = Number of the valid blocks transmitted on the downlink by using MCS-1 ++ Number of the valid blocks transmitted on the downlink by using MCS-9
[0, +)
Byte
Total number of the bytes contained in the valid blocks transmitted on the downlink = Number of the valid blocks transmitted on the downlink by using various modulation and coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the downlink by using MCS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the downlink by using MCS-9 x Number of the bytes contained in one valid block For details about the relation between a specific modulation and coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.3.
Issue 01 (2013-07-15)
760
Param eter >>Dow nlink Retrans mission Ratio >>Dow nlink Averag e GMSK BEP >>Dow nlink Averag e 8PSK BEP >>Dow nlink Averag e BEP
Unit %
Description Downlink data-retransmission rate = Total number of the valid blocks transmitted on the downlink/Total number of the blocks transmitted on the downlink Average downlink GMSK BEP.
[0,31 ]
N/A
[0,31 ]
N/A
[0,31 ]
N/A
1. If both the average downlink GMSK BEP and the average downlink 8PSK BEP are valid, use the average downlink GMSK BEP with a higher order. 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.
N/A
Kbps
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.
Issue 01 (2013-07-15)
761
Param eter >>Um Quality Satisfac tion Ratio of Downli nk Averag e SingleSlot Throug hput >>Poor Transm ission Quality Indicate d by Downli nk Averag e SingleSlot Throug hput >>Dow nlink Reuse Ratio Statistic s on UplinkRateSensitiv e Service s >PDU Bytes Receive d at Uplink
Unit %
Description Um-interface quality satisfaction rate at the average downlink single-slot throughput = MIN (Average downlink single-slot throughput/Target single-slot throughput x 100%, 100%) The target single-slot throughput is an internal algorithm parameter.
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, the transmission quality at the average downlink single-slot throughput is poor. The BEP required by the lowest-level coding and the upper threshold for downlink dataretransmission rate are internal algorithm parameters.
[0.00, +)
N/A
Downlink timeslot reuse = Overall duration for data transmission by using the downlink PDU x Average number of downlink timeslots/2/Total number of the blocks transmitted on the downlink Information about the statistics on uplink rate-sensitive services.
N/A
N/A
[0, +)
Byte
Issue 01 (2013-07-15)
762
Param eter >Durati on for Receivi ng PDU at Uplink >PDU Bytes Sent at Downli nk >Uploa d Speed (Kbps)
Ran ge [0, +)
Unit Secon d
Description Overall duration for data transmission by using the uplink PDU.
[0, +)
Byte
[0, +)
Kbps
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 transmission by using the uplink PDU
Yes No
N/A
Number of low upload rate exceptions during the whole process for a subscriber to use a data service. If an upload rate is lower than the lower threshold for upload rate, the upload rate is low. The threshold is set by engineers when creating tasks.
>Numb er of Uplink NU Out-ofOrder Times >Numb er of Uplink TCP Out-ofOrder Times >Avera ge Occupi ed Uplink Slots
[0, +)
Num ber
[0, +)
Num ber
[1,6]
Num ber
Issue 01 (2013-07-15)
763
Unit %
Description Uplink multislot-satisfaction rate = Average number of timeslots occupied by the uplink/ 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 Uplink Rate-Sensitive Service/EGDE Service Flag indicates a valid value, namely, the EDGE service is available, you can obtain the multislot class of a Terminal from Information About the VIP Subscriber/Capability of the Terminal/ Multislot Class of the Terminal When Supporting EGPRS. Otherwise, you can obtain the multislot class of a Terminal from Information About the VIP Subscriber/Capability of the Terminal/ Multislot Class of the Terminal When Supporting GPRS.
>Trans mission Resour ces Require d for Code Request ed by Uplink Block >Trans mission Resour ces Used by Code Assigne d to Uplink Block
[0, +)
Num ber
[0, +)
Num ber
Number of transmission resources actually used for the encoding of uplink blocks.
Issue 01 (2013-07-15)
764
Param eter >Resou rce Statisfa ction Ratio of Uplink Averag e SingleSlot Throug hput (%) >Durati on for Sendin g PDU at Downli nk >Total Duratio n for Sendin g PDU at Downli nk >PDUs Sent at Downli nk >Timeo ut Times on sending PDUs at Downli nk >GPRS Service Flag
Unit %
Description Transmission-resource satisfaction rate at the average uplink single-slot throughput = Number of transmission resources actually used for the encoding of uplink blocks/ Number of transmission resources requested for the encoding of uplink blocks x 100%
[0, +)
Secon d
[0, +)
Secon d
[0, +)
Num ber
[0, +)
Num ber
Number of times that the duration for data transmission by using the downlink PDU exceeds the predefined threshold. A device is configured to directly check whether the duration for data transmission by using the PDU exceeds the predefined threshold.
N/A
N/A
Information about the data service that a VIP subscriber uses through GPRS.
Issue 01 (2013-07-15)
765
Param eter >>Num ber of Uplink CSN (1~4) Blocks/ Valid Blocks >>Num ber of Total Blocks Receive d at Uplink
Ran ge [0, +)
Description Total number of the blocks, and that of the valid blocks, transmitted on the uplink by using channel coding schemes CS-1 through CS-4.
[0, +)
Num ber
Total number of the blocks transmitted on the uplink = Total number of the blocks transmitted on the uplink by using various channel coding schemes = Number of the blocks transmitted on the uplink by using CS-1 ++ Number of the blocks transmitted on the uplink by using CS-4
[0, +)
Num ber
Total number of the valid blocks transmitted on the uplink = Total number of the valid blocks transmitted on the uplink by using various channel coding schemes = Number of the valid blocks transmitted on the uplink by using CS-1 ++ Number of the valid blocks transmitted on the uplink by using CS-4
[0, +)
Byte
Total number of the bytes contained in the valid blocks transmitted on the uplink = Number of the valid blocks transmitted on the uplink by using various channel coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the uplink by using CS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the uplink by using CS-4 x Number of the bytes contained in one valid block For details about the relation between a specific channel coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.2.
Issue 01 (2013-07-15)
766
Param eter >>Upli nk SingleSlot Throug hput (Actual ) >>Upli nk Reuse Ratio >EGDE Service Flag >>Num ber of Uplink MCS1~ 9 Blocks/ Valid Blocks >>Num ber of Total Blocks Receive d at Uplink
Unit Kbps
Description Uplink single-slot throughput (Actual) 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
[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 Information about the data service that a VIP subscriber uses through EGDE. Total number of the blocks, and that of the valid blocks, transmitted on the uplink by using modulation and coding schemes MCS-1 through MCS-9.
N/A
N/A
[0, +)
Num ber
[0, +)
Num ber
Total number of the blocks transmitted on the uplink = Total number of the blocks transmitted on the uplink by using various modulation and coding schemes = Number of the blocks transmitted on the uplink by using MCS-1 ++ Number of the blocks transmitted on the uplink by using MCS-9
[0, +)
Num ber
Total number of the valid blocks transmitted on the uplink = Total number of the valid blocks transmitted on the uplink by using various modulation and coding schemes = Number of the valid blocks transmitted on the uplink by using MCS-1 ++ Number of the valid blocks transmitted on the uplink by using MCS-9
Issue 01 (2013-07-15)
767
Ran ge [0, +)
Description Total number of the bytes contained in the valid blocks transmitted on the uplink = Number of the valid blocks transmitted on the uplink by using various modulation and coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the uplink by using MCS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the uplink by using MCS-9 x Number of the bytes contained in one valid block For details about the relation between a specific modulation and coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.3.
>>Upli nk Receive Retrans mission Rate (%) >>Upli nk Averag e GMSK BEP >>Upli nk Averag e 8PSK BEP >>Upli nk Averag e BEP
[0.00, 100.0 0]
Uplink data-retransmission rate = Total number of the valid blocks transmitted on the uplink/Total number of the blocks transmitted on the uplink
[0,31 ]
N/A
[0,31 ]
N/A
[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, use the one with a valid value as the average uplink BEP.
Issue 01 (2013-07-15)
768
Param eter >>Upli nk Averag e SingleSlot Throug hput Require d for Um Quality >>Um Quality Unsatis faction Times of Downli nk Averag e SingleSlot Throug hput
Unit Kbps
Description Average uplink single-slot throughput required to achieve a specific quality level on the Um interface. You can obtain the maximum single-slot rate, namely, the average uplink single-slot throughput, in BEP-Coding Scheme-Rate Mapping Table based on the average uplink BEP. The BEP-Coding Scheme-Rate Mapping Table is generated by an NE.
[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. 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) 3. If the average uplink single-slot throughput is smaller than the target single-slot throughput, and, at the same time, the value of B, which is obtained by using the following formula, is larger than the threshold for Um-interface quality satisfaction rate at the average uplink single-slot throughput, the quality on the Um interface does not meet the requirements. B = Average coding scheme_average uplink BEP/Average coding scheme_Number of the blocks actually received on the uplink.
Issue 01 (2013-07-15)
769
Param eter >>Poor Transm ission Quality Indicate d by Uplink Averag e SingleSlot Throug hput >>Upli nk SingleSlot Throug hput (Actual ) >>Upli nk Reuse Ratio
Ran ge Yes No
Unit N/A
Description If the average uplink BEP is higher than the BEP required by the lowest-level coding, and, at the same time, the uplink dataretransmission rate is higher than the upper threshold for uplink data-retransmission rate, the transmission quality at the average downlink single-slot throughput is poor. The BEP required by the lowest-level coding and the upper threshold for uplink datareception-and-retransmission rate are internal algorithm parameters.
[0,10 0]
Uplink single-slot throughput (Actual) 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
[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
Summary Information
Param eter Total Traffic at Downli nk Ran ge [0, +) Unit Byte Description Total downlink traffic during the whole process for a subscriber to use a data service. 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 + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Downlink PDU Supported NE Version BSC6900 V900R013C01 or later version
Issue 01 (2013-07-15)
770
Ran ge [0, +)
Unit Byte
Description Total uplink traffic during the whole process for a subscriber to use a data service. Total uplink traffic = Delay-Sensitive Information/Total Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Downlink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU
N/A
N/A
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. Content of a signaling message. You can obtain the content of a signaling message by viewing the related tree structure.
Signali ng Content
N/A
N/A
Issue 01 (2013-07-15)
771
Measurement Information
Parame ter Number Rang e [0, +) N/A Unit N/A Description Unique number of a signaling message carrying a measurement report. Time when a measurement report is submitted. Type of a measurement report. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Time
N/A
MR Type
2G NC MR 3G MR EUTRA N MR
N/A
Server Nbr1~ 6
N/A
Type of a measurement object reported in a measurement report. 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.
N/A
N/A
name of a measurement object reported in a measurement report. The parameter is displayed in the following format: name of the BSC: name of the cell.
BCCH
N/A
BCCH of a neighboring cell on 2G network, reported in a measurement report. BSIC of a neighboring cell on 2G network, reported in a measurement report.
BSIC
N/A
dBm
Downlink RxLevel of a serving cell and that of a neighboring cell on 2G network, reported in a measurement report. Frequency on 3G network, reported in a measurement report. Primary scrambling code on 3G networkl, reported in a measurement report.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
Issue 01 (2013-07-15)
772
Unit dBm
Description RSCP on 3G networkl, reported in a measurement report. Frequency on LTE network, reported in a measurement report. Primary scrambling code on LTE networkl, reported in a measurement report. RSCP on LTE networkl, reported in a measurement report.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Frequen cy PCI
N/A
N/A
RSRP
dBm
Mobility Analysis
Parame ter Number Range N/A Unit N/A Description Number. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
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. The threshold is set by engineers when creating tasks.
Abnorm al Cause
Overlo ng time of cell reselec tion (Durati on) Cell Resele ction N/A
N/A
If the time interval is above the exception threshold for cell reselection, it displays "Overlong time of cell reselection (Duration)".
Type
N/A
Type of a mobility analysis, namely, cell reselection. Time when a cell reselection ends.
End Time
N/A
Issue 01 (2013-07-15)
773
Range N/A
Unit N/A
Description Source cell for a cell reselection. 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 based on the internal ID of the BSC and the ID of the cell. The names are not displayed if they are not available.
Reselect RxQuali ty Reselect GMSK MEAN BEP Reselect 8PSK MEAN BEP Target Cell
[0,7]
N/A
RxQulity of the source cell for a cell reselection. GMSK MEAN BEP of the source cell for a cell reselection.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0,31]
N/A
[0,31]
N/A
N/A
N/A
Target cell for a cell reselection. 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 based on the internal ID of the BSC and the ID of the cell. The names are not displayed if they are not available.
Access RxQuali ty Access GMSK MEAN BEP Access 8PSK MEAN BEP
[0,7]
N/A
RxQulity of the target cell for a cell reselection. GMSK MEAN BEP of the target cell for a cell reselection.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0,31]
N/A
[0,31]
N/A
Summary
Param eter Serial Numbe r Range (0,2^31-1) Uni t N/A Description 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. 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. ! Blank N/A Whether a call record is abnormal. 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. Abnor mal Cause For details, see "Appendix: Exception Cause Classificatio n/ Enumeration Values of Failure Cause (UMTS)". 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. BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Combi ned
N/A
N/A
Status
Networ k
N/A
Issue 01 (2013-07-15)
775
Range Static reloc in HHO reloc in Cell update reloc in Inter RAT handover in RRC setup without DRD RRC setup with DRD
Uni t N/A
Issue 01 (2013-07-15)
776
Range Originating Conversation al Call Originating Streaming Call Originating Interactive Call Originating Background Call Originating Subscribed traffic Call Terminating Conversation al Call Terminating Streaming Call Terminating Interactive Call Terminating Background Call Emergency Call Inter-RAT cell reselection Inter-RAT cell change order Registration Detach Originating High Priority Signaling Originating Low Priority Signaling
Uni t N/A
Issue 01 (2013-07-15)
777
Param eter
Range Call reestablishmen t Terminating High Priority Signaling Terminating Low Priority Signaling Terminating - cause unknown MBMS reception MBMS ptp RB request
Uni t
Description
Supported NE Version
Access Time Access Cell Release Time Release Cell User ID:Alia s
N/A
N/A
Same as Access Information -> RRC Request Time. Same as Access Information -> Cell on RRC Setup. Same as Release Information -> RRC Release Time Same as Release Information -> RRC Release Cell Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
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.
Termin al Model
N/A
N/A
Model of a UE. The UE model can be queried using terminal type management based on the IMEI-TAC of the UE.
Issue 01 (2013-07-15)
778
Range [0,+)
Uni t Seco nd
Description Duration of a call, including service duration and signaling duration. Call duration = Release time - Access time.
CS Reques ted Service Type CS Service Duratio n PS Reques ted Service Type PS RAB Duratio n RRC Setup Failure Cause
AMR VP
N/A
[0,+)
Seco nd
N/A
Seco nd
For details, see "Access information/ RRC Setup Failure Cause". N/A
N/A
IU Release Cause
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.
N/A
N/A
Cause of CS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
Issue 01 (2013-07-15)
779
Range N/A
Uni t N/A
Description Cause of CS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
N/A
N/A
Cause of PS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
N/A
N/A
Cause of PS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
User Information
Param eter TMSI/ PTMSI Range 0000000-FFFFFFFF Uni t N/A Description 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. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
780
Range N/A
Uni t N/A
Description Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
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.
Termin al Model
N/A
N/A
Model of a UE. The UE model can be queried using terminal type management based on the IMEI-TAC of the UE.
Termin al Operati ng System UE Capabil ity >Proto col Versio n >Power Class
For details, see the OS description of the UMTS terminal analysis. N/A
N/A
N/A
Capability of a UE.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
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.
Issue 01 (2013-07-15)
781
Range Band I 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 Band XVI Band XVII Band XVIII Band XIX Band XX Band XXI Band XXII Reserved
Uni t N/A
Description Universal Terrestrial Radio Access (UTRA) frequency bands supported by a UE. For details, see Table 5.0 "UTRA FDD frequency bands" under "UE Radio Transmission and Reception (FDD)" in 3GPP TS 25.101.
>HSPA Capabil ity >>HSDSCH Capabil ity >>EDCH Capabil ity >>Sup port ERACH
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[1,64]
N/A
HSDPA capability of a UE. A larger value of this parameter indicates larger HSDPA capability. HSUPA capability of a UE. A larger value of this parameter indicates larger HSUPA capability. Whether a UE supports ERACH.
[1,16]
N/A
supported unsupported
N/A
Issue 01 (2013-07-15)
782
Param eter >>Sup port EFACH >>Sup port DTXD RX >>Sup port HSSCCH Less Operati on >Mobil ity Capabil ity
Uni t N/A
Description Whether a UE supports EFACH. Whether a UE supports discontinuous transmission (DTX) and discontinuous reception (DRX). Whether a UE supports HSSCCH.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
supported unsupported
N/A
Support of GSM 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 Support of UTRAN to GERAN NACC Support of Handover to GAN Support of PS Handover to GAN Reserved
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.
Issue 01 (2013-07-15)
783
Param eter >Suppo rt EUTRA Band Capabil ity >Positi oning Capabil ity
Uni t N/A
Description Evolved Universal Terrestrial Radio Access (E-UTRA) frequency bands supported by a UE.
Standalone location method(s) supported UE based OTDOA supported GANSS support indication Support for GPS timing of cell frames measurement Support for IPDL Support for Rx-Tx time difference type2 measurement Support for UP assisted GPS measurement validity in CELL_PCH and URA_PCH states Support for SFNSFN observed time difference type 2 measurement Network Assisted GPS support
N/A
Access Information
Param eter RRC Request Time Range N/A Uni t N/A Description Time of signaling access during a call. That is, timestamp in the RRC CONNECTION SETUP message. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
784
Param eter RRC Radio Link Setup Time Cell on RRC Setup
Range N/A
Uni t N/A
Description Time of RRC radio link setup during a call. That is, timestamp in the RADIO LINK SETUP REQUEST message. Name of the cell to which signaling accesses. 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.
N/A
N/A
N/A
N/A
Target cell of Directed Retry Decision (DRD) during signaling access. 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.
SRB on FACH_RACH SRB on DCH_DCH SRB on HSDSCH_RACH SRB on HSDPA_DCH SRB on DCH_HSUPA SRB on HSDPA_HSUPA
N/A
Issue 01 (2013-07-15)
785
Range Static reloc in HHO reloc in Cell update reloc in Inter RAT handover in RRC setup without DRD RRC setup with DRD
Uni t N/A
Description Value of RRC Connection Setup Type carried in the RRC CONNECTION SETUP message: Incoming migration (Static reloc in) 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) Incoming inter-RAT handover (Inter RAT handover in) RNC access (RRC setup without DRD) RNC access (RRC setup with DRD)
Issue 01 (2013-07-15)
786
Range Originating Conversational Call Originating Streaming Call 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 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 MBMS ptp RB request
Uni t N/A
Description Cause of RRC setup. For details, see 3GPP TS 25.331-10.3.3.11 "Establishment cause."
Issue 01 (2013-07-15)
787
Uni t N/A
Description Whether RRC setup is triggered by service or non-service causes based on RRC Setup Cause. The rules for determining the trigger conditions are as follows: 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.
CS PS
N/A
Whether RRC setup occurs in the CS or PS domain based on RRC Setup Cause.
Issue 01 (2013-07-15)
788
Uni t N/A
Description Whether RRC setup occurs on the MOC or MTC side based on RRC Setup Cause. The rules for determining the occurrence conditions are as follows: 1. RRC setup occurs on the MOC side when the value of RRC Setup Cause is any of the following: Originating Conversational Call Originating Streaming Call Originating Interactive Call Originating Background Call Originating Subscribed traffic Call Originating High Priority Signaling Originating Low Priority Signaling Emergency Call 2. RRC setup occurs on the MTC side when the value of RRC Setup Cause is any of the following: 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 01 (2013-07-15)
789
Uni t N/A
Description Whether RRC setup is triggered by SMS or non-SMS causes based on RRC Setup Cause. The rules for determining the trigger conditions are as follows: 1. RRC setup is triggered by SMS causes when the value of RRC Setup Cause is any of the following: Originating High Priority Signaling Originating Low Priority Signaling Terminating High Priority Signaling Terminating Low Priority Signaling 2. Otherwise, RRC setup is triggered by non-SMS causes.
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
N/A
Error Type.
>Error Reason
N/A
Error Reason.
N/A
790
Range [0,+)
Uni t Seco nd
Description Delay on RRC setup. The statistical points are as follows: 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. Inter-RAT handover: Timestamp in the RELOCATION REQUEST message - Timestamp in the UTRAN MOBILITY INFORMATION CONFIRM message.
Yes No
N/A
Overlong RRC setup delay occurs when the RRC setup delay exceeds the overlong delay threshold limit. The abnormal threshold is set by engineers during analysis task creation.
N/A
N/A
N/A
N/A
Cell on which RAB setup is requested. 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.
>TP
[0,3069 ]
N/A
Time Propagation (TP) is a term defined by Huawei to indicate time propagation delay during UE access.
Issue 01 (2013-07-15)
791
Range Yes No
Uni t N/A
Description 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. Remark: If the active set contains multiple cells during access, the counters for all the cells in this active set are analyzed.
[-24,0]
dB
Ec/No of the serving cell on RRC setup. If "Ec/No" is smaller than "Ec/No abnormal threshold on RRC setup", it indicators that the Ec/No is abnormal on RRC setup. Abnormal threshold is set when creating tasks. Remark: If the active set contains multiple cells during access, the counters for all the cells in this active set are analyzed.
Yes No
N/A
>RSCP
[-115,-25]
dBm
RSCP of the serving cell on RRC setup. If "RSCP" is smaller than "RSCP abnormal threshold on RRC setup", it indicators that the RSCP is abnormal on RRC setup. Abnormal threshold is set when creating tasks. Remark: If the active set contains multiple cells during access, the counters for all the cells in this active set are analyzed.
Yes No
N/A
Issue 01 (2013-07-15)
792
Release Information
Param eter RRC Release Time Range N/A Unit N/A Description Release time of RRC connection. That is, timestamp in the RRC CONNECTION RELEASE message. [0,+) Seco nd Duration of a call. Call duration = RRC release time - RRC setup request time Name of the cell from which signaling is released. The parameter value is displayed in the following format: RNC name:cell name (RNCID: cellID). 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. Successful Failed N/A N/A Release cause carried in the last IU RELEASE COMMAND message received by an RNC. Type of failure cause. For details, see 3GPP 25.413-9.2.1.4. N/A RRC release results. Supported NE Version BSC6900 V900R013C00 or later version
Duratio n
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Radio Network Layer Cause Transport Layer Cause NAS Cause Protocol Cause Miscellaneous Cause Non-standard Cause Radio Network Layer Cause Extension
N/A
>Cause value
N/A
N/A
Issue 01 (2013-07-15)
793
Statistical Information
Param eter Soft Handov er Info >Soft Handov er Request s >Succe ssful Soft Handov ers >Softer Handov er Request s >Succe ssful Softer Handov ers Hard Handov er Info >IntraFreq Handov er Request s >Succe ssful IntraFreq Handov ers Range N/A Unit N/A Description Soft handover information. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Num ber
Number of soft handover requests, including soft handover requests and softer handover requests.
[0,+)
Num ber
Number of successful soft handovers, including successful soft handovers and successful softer handovers. Number of softer handover requests.
[0,+)
Num ber
[0,+)
Num ber
N/A
N/A
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
794
Param eter >InterFreq Handov er Request s >Succe ssful InterFreq Handov ers InterRAT Handov er Info >InterSystem Outgoin g Handov er Request s(CS) >InterSystem Outgoin g Handov er Request s(PS) >Succe ssful InterSystem Outgoin g Handov ers
Range [0,+)
[0,+)
Num ber
N/A
N/A
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
795
Param eter >InterSystem Incomi ng Handov er Request s >Succe ssful InterSystem Incomi ng Handov ers DCCC Info >DCCC Speed Increas e Initializ ation Times >DCCC Speed Increas e Success Times >DCCC Speed Decreas e Initializ ation Times >DCCC Speed Decreas e Success Times
Range [0,+)
[0,+)
Num ber
N/A
N/A
DCCC information.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
796
Param eter RAB Info >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (AMR) >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (VP) >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (PS)
Range N/A
Unit N/A
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Num ber
Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for the AMR service.
[0,+)
Num ber
Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for the VP service.
[0,+)
Num ber
Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for PS services. In which, PS services include the PS R99 service, HSDPA service, HSUPA, service, and HSPA service.
Issue 01 (2013-07-15)
797
Param eter >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (HSDP A) MultiRAB Info >Abnor mal CS Release due to PS Release >Abnor mal CS Release due to PS Service Setup >Releas ed RABs in CS Domain Trigger ed by the Failure in Securit y Mode
Range [0,+)
Description Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for the HSDPA service.
N/A
N/A
Multi-RAB information.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
798
Param eter >Releas ed RABs in PS Domain Trigger ed by the Failure in Securit y Mode >Setup Attempt s of Combin ed Service (CS + PS) >Succe ssful Setups of Combin ed Service (CS + PS) >CS plus PS multiRAB CS normal release times >CS plus PS multiRAB CS abnorm al release times
Range [0,+)
Description Number of released RABs in the PS domain triggered by failed security authentication.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
799
Param eter >CS plus PS multiRAB PS normal release times >CS plus PS multiRAB PS abnorm al release times >Setup Attempt s of Combin ed Service (PS + PS) >Succe ssful Setups of Combin ed Service (PS + PS) >Norm al Release s of Combin ed Service (PS + PS)
Range [0,+)
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
800
Param eter >Abnor mal Release s of Combin ed Service (PS + PS) Statistic s of Voice Quality in CS Domain >OneWayAudio Times >Noise Times
Range [0,+)
N/A
N/A
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
801
Range 1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
Unit N/A
Traffic class: conversational streaming interactive background Traffic type: CS_AMR CS_VP CS_OTHER PS_GENERAL PS_HSDPA PS_HSUPA PS_HSPA ...
N/A
RAB request service type consists of two parts: Traffic class and Traffic type. The parameter value is displayed in the format of Traffic class/ Traffic type. For details about Traffic class, see 3GPP 25.413. Traffic type is a service type defined by Huawei in terms of radio access bearer (RAB).
N/A
N/A
Time when RAB setup is requested. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT REQUEST message. Incoming migration: Timestamp in the RELOCATION COMPLETE message. Inter-RAT handover: Timestamp in the HANDOVER TO UTRAN COMPLETE message.
Issue 01 (2013-07-15)
802
Range N/A
Unit N/A
Description Cell on which RAB setup is requested. The parameter value is displayed in the following format: RNC 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.
[0,+)
Seco nd
Time when RAB setup completes. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT RESPONSE message. Incoming migration: The time is not recorded. Inter-RAT handover: The time is not recorded.
N/A
N/A
Best cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Service cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
>DRD Info
N/A
N/A
Information about DRDs during RAB setup, recording the last three DRDs at most.
Issue 01 (2013-07-15)
803
Range N/A
Unit N/A
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Target cell of the current DRD. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
N/A
DRD failure cause. For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
>>>>Er ror Type >>>>Er ror Reason >>Peer Info >>>Pee r MSISD N
For details, see the "Enumeration Values of Failure Cause". For details, see the "Enumeration Values of Failure Cause". N/A
N/A
Error type.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
Error reason.
N/A
N/A
Mobile station international ISDN BSC6900 number (MSISDN) of the peer UE. V900R013C00 MSISDN is a 15-digit numeric or later version string of decimal digits (0-9). For details, see 3GPP TS 23.003.
Issue 01 (2013-07-15)
804
Range DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
Description Type of an uplink or downlink data transmission channel after RAB setup. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
805
Range [0,+)
Unit kbps
Description 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. In which, When UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/s. When UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/ s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>RAB Setup Result >RAB Setup Failure Time >RAB Setup Failure Cause >>Error Type
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Error type.
Issue 01 (2013-07-15)
806
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
Unit N/A
>RAB Setup Delay Estimat ion >>RAB Setup Delay >>Over long RAB Setup Delay
N/A
[0,+)
Seco nd N/A
RAB setup delay = Time when RAB setup completes - Time when RAB setup is requested. Overlong RAB setup delay occurs when the RAB setup delay exceeds the overlong delay threshold limit. The overlong delay threshold is set by engineers during analysis task creation.
Yes No
[0,+)
Seco nd
Call setup delay = Time when RAB setup completes - Time when RRC setup is requested. Call setup delay = RAB setup delay + RRC setup delay. Note that this parameter is applicable only to the first RAB after RRC setup.
Yes No
N/A
Overlong call setup delay occurs when the call setup delay exceeds the overlong delay threshold limit. The overlong delay threshold is set by engineers during analysis task creation.
N/A
N/A
Service request time, that is, the timestamp of "Service Request" message.
Issue 01 (2013-07-15)
807
Range [0,+)
Unit Seco nd
Description 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 COMPLETE message Timestamp in the RADIO BEARER RECONFIGURATION message.
N/A
N/A
Time of outgoing call alerting during a call. Statistical point: Timestamp in the ALERTING message. 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. Outgoing call alerting delay = Alerting time - RRC setup request time.
N/A [0,+)
N/A
Issue 01 (2013-07-15)
808
Unit N/A
Description 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 Yes in the following conditions: The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MOC. Outgoing call alerting delay > Overlong outgoing call alerting delay threshold (MOC). The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MTC. Outgoing call alerting delay > Overlong outgoing call alerting delay threshold (MTC). 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.
>>Conn ect Ack Time >>Call Comple tion Delay (Conne ct Ack)
N/A
N/A
Time of incoming call alerting during a call. Statistical point: Timestamp in the CONNECT ACKNOWLEDGE message. 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. Incoming call alerting delay = Connect Ack time - RRC setup request time.
[0,+)
Seco nd
Issue 01 (2013-07-15)
809
Param eter >>Over long Call Comple tion Delay (Conne ct Ack)
Unit N/A
Description 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 Yes in the following conditions: The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MOC. Incoming call alerting delay > Overlong incoming call alerting delay threshold (MOC). The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MTC. Incoming call alerting delay > Overlong incoming call alerting delay threshold (MTC). 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.
>RAB Setup Process >>Queu ing Indicato r >>Intra -system DRD Indicato r
N/A
N/A
Process information of RAB setup. This parameter is used with RAB Setup Failure Cause to analyze problems. TRUE(1) indicates that queuing occurs.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
False True
N/A
False True
N/A
Issue 01 (2013-07-15)
810
Param eter >>Inter -system DRD Indicato r >RAB Resourc e Congest ion Informa tion on RAB Setup >>Cong estion Time >>Cong estion Cell ID >>Cong estion Status
Unit N/A
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.
N/A
N/A
Time when radio resource congestion occurs. Cell where radio resource congestion occurs. Cause of radio resource congestion.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Code DL CE 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
N/A
N/A
N/A
Issue 01 (2013-07-15)
811
Range 1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
Unit N/A
>Single -RAB Abnor mal Release Indicato r >Multip le-RAB Abnor mal Release Indicato r >RAB Release Time
False True
N/A
False True
N/A
N/A
N/A
Time when RAB release completes. The statistical points are as follows: Normal release and CN abnormal release: RAB release time = Timestamp in the IU RELEASE COMMAND or RAB ASSIGNMENT REQUEST message.
>RAB Duratio n
[0,+)
Seco nd
Issue 01 (2013-07-15)
812
Range Yes No
Unit N/A
Description If "RAB Duration" is smaller than "RAB Duration shorter threshold", it indicators that the RAB duration is too shorter. Abnormal threshold is set when creating tasks.
N/A
N/A
Best cell before RAB release. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Serving cell before RAB release. The parameter value is displayed in the following format: RNC 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.
Issue 01 (2013-07-15)
813
Range DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
Description Type of an uplink or downlink data transmission channel before RAB release. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
814
Range [0,+)
Unit kbps
Description Uplink and downlink RB rate after RAB setup and before RAB release. The parameter value is displayed in the format of UL RB bitrate after RAB setup/DL RB bitrate after RAB setup. In which, When UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/s. When UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/ s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>Disco nnect Cause >Disco nnect Directio n >RAB Release Failure Cause
N/A
N/A
Cause carried in the DISCONNECT message. For details, see 3GPP 24.008-10.5.4.11. Direction for sending the DISCONNECT message.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
from UE from CN
N/A
N/A
N/A
Issue 01 (2013-07-15)
815
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
Unit N/A
>>Error Reason
N/A
Error reason.
N/A
Time when RAB release fails. That is, when the system receives the following timestamp: IU RELEASE REQUEST RAB RELEASE REQUEST
RAB Process Info >RAB Setup Delay Estimat ion >>Disc onnect time >>Servi ce Duratio n
N/A
N/A
N/A
N/A
N/A
N/A
Time when a call completes. Statistical point: timestamp in the DISCONNECT message. Service duration = Disconnect time - Connect Ack time.
[0,+)
Seco nd
Issue 01 (2013-07-15)
816
Unit N/A
Description 1.The parameter value is Yes in the following conditions: When the current RAB is not the first RAB after RRC setup and Call duration < Short call threshold. The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MOC. Call duration < Short call threshold (MOC). The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MTC. Call duration < Short call threshold (MTC). 2.The parameter value is No in the other conditions. The short call threshold, short call threshold (MOC), and short call threshold (MTC) are set by engineers during task creation.
Issue 01 (2013-07-15)
817
Range N/A
Unit N/A
Description Statistics on SQIs 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. 2. The RNC can statistics based on the average SQI value and divides signal quality into different levels according to SQI values: RAN14.0: Excellent (SQI<= (400,500]), Good (SQI<= (300,400]), Accept (SQI<= (200,300]), Poor (SQI<= (100,200]), Bad (SQI<=[0,100]). RAN13.0 and earlier: Good (SQI <= (300,500]), Accept (SQI <= (200,300]), Bad (SQI <=(0,200]). The segment intervals of levels can be modified by running the SET USQICOUNT command on the RNC.
[0,500]
N/A
Yes No
N/A
If SQI average < Abnormal SQI threshold, The value of this parameter is Yes. Otherwise, the value is No. The abnormal SQI threshold is set by engineers during task creation.
[0,100]
Proportion of voice quality with SQI as Excellent from RAB setup to RAB release.
Issue 01 (2013-07-15)
818
Param eter >>Radi o of Good SQIs (%) >>Radi o of Accept SQIs (%) >>Radi o of Poor SQIs (%) >>Radi o of Bad SQIs (%) >BLER Statistic Info
Range [0,100]
Unit %
Description Proportion of voice quality with SQI as Good from RAB setup to RAB release.
[0,100]
Proportion of voice quality with SQI as Accept from RAB setup to RAB release.
[0,100]
Proportion of voice quality with SQI as Poor from RAB setup to RAB release.
[0,100]
Proportion of voice quality with SQI as Bad from RAB setup to RAB release. Statistics on BLERs. 1. Block error rate (BLER) indicates signal quality on the 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%.
N/A
N/A
[0,+)
Num ber
N/A
Issue 01 (2013-07-15)
819
Param eter >Statist ics on Last Receive d Blocks >>Num ber of UL Total Blocks (1~5)
Range N/A
Unit N/A
Description Statistics on received blocks before link release. The statistical period is 2.56 seconds.
[0,+)
Num ber
Total number of UL blocks received within the five periods before link release. The parameter value is displayed 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.
[0,+)
Num ber
Number of UL error blocks received within the five periods before link release. The parameter value is displayed in this format: Number of UL error blocks received in period 1/ Number of UL error blocks received in period 2/.../Number of UL error blocks received in period 5.
N/A
N/A
Statistics on uplink one-way audio. 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.
N/A
N/A
Time when uplink one-way audio occurs. Cell when uplink one-way audio occurs.
N/A
N/A
Issue 01 (2013-07-15)
820
Range N/A
Unit N/A
Description Statistics on downlink one-way audio. The downlink one-way audio problems fall into two types: 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. 2. The RNC records a downlink one-way audio problem when it detects a large BLER value. This function is available only when a VIP subscriber enables periodic DL BLER reporting. The RNC records a maximum of the first three downlink one-way audio problems during each call of a UE.
N/A
N/A
Time when a downlink one-way audio problem occurs. Cell when a downlink one-way audio problem occurs. Statistics on noises. 1. The RNC records a noise problem. 2. The RNC records only the first one noise problem during each call of a UE.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
Time when a noise problem occurs. Cell when a noise problem occurs.
N/A
N/A
Issue 01 (2013-07-15)
821
Issue 01 (2013-07-15)
822
Range N/A
Unit N/A
Description Time for requesting RAB setup. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT REQUEST message. Incoming migration: Timestamp in the RELOCATION COMPLETE message. Inter-RAT handover: Timestamp in the HANDOVER TO UTRAN COMPLETE message.
N/A
Cell on which RAB setup is requested. The parameter value is displayed in the following format: RNC 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.
[0,+)
Seco nd
Time when RAB setup completes. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT RESPONSE message. Incoming migration: The time is not recorded. Inter-RAT handover: The time is not recorded.
N/A
Best cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
Issue 01 (2013-07-15)
823
Range N/A
Unit N/A
Description Serving cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Information about DRDs during RAB setup, recording the last three DRDs at most. The N DRD record.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Target cell of the current DRD. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
N/A
DRD failure cause. For details, see the Failure Cause tab page.
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)"
N/A
Error type.
Issue 01 (2013-07-15)
824
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
N/A
Type of an uplink or downlink data transmission channel after RAB setup. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
825
Range [0,+)
Unit bps
Description DL/UL 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. In which, If UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/ s. If UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>UL/ [0,+) DL RAB Negotia ted Rate Overlo Yes w UL No RAB Negotia ted Rate
bps
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. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
826
Param eter
Range
Unit N/A
Description If "Overlow DL RAB Negotiated Rate" is smaller than "Overlow DL RAB Negotiated Rate Threshold", the record has the problem that the overlow DL RAB vegotiated rate is too small. The abnormal threshold is set when creating tasks.
>RAB Setup Result >RAB Setup Failure Time >RAB Setup Failure Cause >>Error Type
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
N/A
Error type.
>>Error Reason
N/A
Error reason.
N/A
[0,+)
Seco nd
RAB setup delay = Time when RAB setup completes - Time when RAB setup is requested.
Issue 01 (2013-07-15)
827
Range Yes No
Unit N/A
Description Overlong RAB setup delay occurs when the RAB setup delay exceeds the overlong delay threshold limit. The overlong delay threshold is set by engineers during analysis task creation.
[0,+)
Seco nd
1.When the following scene occurs, it displays "N/A". Scene: the first RAB after the RAB (Non-RRC) setup. 2.When the following scene occurs, it displays the result value. Scene: the first RAB after the RAB (RRC) setup. Call connection delay = Time when RAB setup completes Time when RRC setup is requested. Call connection delay = RAB setup delay + RRC setup delay.
Yes No
N/A
1.When the following scene occurs, it displays "N/A". Scene: the first RAB after the RAB (Non-RRC) setup. 2.When the following scenes occur, it displays the result value. Scene: the first RAB after the RAB (RRC) setup; and "RRC Setup Flag(MOC/MTC)" is "MOC"; and "Call Setup Delay" is larger than "Latency on Call Connection (MOC) ". Scene: the first RAB after the RAB (RRC) setup; and "RRC Setup Flag(MOC/MTC)" is "MTC"; and "Call Setup Delay" is smaller than "Latency on Call Connection (MTC) ". 3.When the other scene occurs, it displays "No". The threshold is set by engineers during analysis task creation.
Issue 01 (2013-07-15)
828
Range N/A
Unit N/A
Description Time of service request. That is, when the system receives the Service Request timestamp. 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 COMPLETE message Timestamp in the RADIO BEARER RECONFIGURATION message.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Seco nd
>Sched uling Priority >>Allo cation/ Retenti on Priority >>>Pri ority Level
N/A
N/A
Scheduling priority during RAB setup. Allocation/retention priority. For details, see 3GPP 25.413-9.2.1.3.
N/A
N/A
[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.
N/A
829
Param eter >>>Pre emptio n Vulnera bility >>>Qu euing Allowe d >>Traff ic Handlin g Priority
Unit N/A
Description Whether resources of the current RAB can be preempted by other RABs.
N/A
N/A
Priority level in the allocation and retention of system resources. For details, see 3GPP 25.433-9.2.1.1A. 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.
[0,15]
N/A
HS-DSCH scheduling priority. For details, see 3GPP 25.433-9.2.1.53H. The value range is [0,15]. A larger value indicates higher priority.
N/A
N/A
Issue 01 (2013-07-15)
830
Range 1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
Unit N/A
>Single -RAB Abnor mal Release Indicato r >Multi pleRAB Abnor mal Release Indicato r >RAB Release Time
False True
N/A
False True
N/A
N/A
N/A
Time when RAB release completes. The statistical points are as follows: Normal release and CN abnormal release: RAB release time = Timestamp in the IU RELEASE COMMAND or RAB ASSIGNMENT REQUEST message.
>RAB Duratio n
[0,+)
Issue 01 (2013-07-15)
831
Range N/A
Unit N/A
Description Best cell before RAB release. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Serving cell before RAB release. The parameter value is displayed in the following format: RNC 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.
UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
N/A
Type of an uplink or downlink data transmission channel before RAB release. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
832
Range [0,+)
Unit kbps
Description UL/DL RB rate after RAB setup and before RAB release. The parameter value is displayed in the format of UL RB bitrate after RAB setup/DL RB bitrate after RAB setup. In which, If UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/ s. If UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>DP Deactiv ate Cause >RAB Release Failure Cause >>Error Type
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. Cause of abnormal RAB release.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Error type.
Issue 01 (2013-07-15)
833
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
Unit N/A
N/A
Time when RAB release fails. That is, when the system receives the following timestamp: IU RELEASE REQUEST RAB RELEASE REQUEST
RAB Process Info >PDP Activat e Request Time >PDP Activat e Ack Time >PDP Deactiv ate Time >BLER Statistic Info
N/A
N/A
N/A
N/A
N/A
N/A
Timestamp in the PDP ACTIVIATE ACKNOWLEDGE message. Timestamp in the DEACTIVATE PDP CONTEXT REQUEST message. Statistical information about BLERs. 1. Block error rate (BLER) indicates signal quality on the 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%.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
834
Param eter >>Time s UL Service BLER Falls into Levels 1 to 6 >Statist ics on Last Receive d Blocks >>Num ber of UL Total Blocks (1~5)
Range [0,+)
Description N/A
N/A
N/A
Statistics on received blocks before link release. The statistical period is 2.56 seconds.
[0,+)
Num ber
Total number of UL blocks received within the five periods before link release. The parameter value is displayed 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.
[0,+)
Num ber
Number of UL error blocks received within the five periods before link release. The parameter value is displayed in this format: Number of UL error blocks received in period 1/ Number of UL error blocks received in period 2/.../Number of UL error blocks received in period 5.
N/A
N/A
[0,+)
Num ber
Number of uplink radio bearer resets after multiple RLC retransmissions fail in acknowledged mode.
Issue 01 (2013-07-15)
835
Range [0,+)
Description Number of downlink radio bearer resets after multiple RLC retransmissions fail in acknowledged mode. Proportion that the amount of transmission data is zero. HSDPA is High Speed Downlink Packet Access for short. This counter is available only in versions earlier than BSC V900R013.
[0,100]
>HSDP A PDCP UL data amount >HSDP A PDCP DL data amount >Bytes of HSDP A MAC-d flow (suffici ent UE resourc es)
[0,+)
KB
Amount of uplink data at the packet data convergence layer of the HSDPA service.
[0,+)
KB
Amount of downlink data at the packet data convergence layer of the HSDPA service.
[0,+)
KB
Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are sufficient for the HSDPA service. That is, the amount of data of a UE sent on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
>Durati on for sending HSDP A MAC-d flow (suffici ent UE resourc es)
[0,+)
Duration for sending HSDPA MAC-d flow when the data resources of a UE are sufficient for the HSDPA service. That is, the duration for sending data of a UE on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
Issue 01 (2013-07-15)
836
Param eter >Bytes of HSDP A MAC-d flow (insuffi cient UE resourc es) >Durati on for sending HSDP A MAC-d flow (insuffi cient UE resourc es) >Avera ge Downli nk Rate
Range [0,+)
Unit KB
Description Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are insufficient for the HSDPA service. That is, the amount of data of a UE sent on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
[0,+)
Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient for the HSDPA service. That is, the duration for sending data of a UE on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
[0,+)
Kbps
Average downlink rate of the HSDPA service = (Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are sufficient + Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are insufficient) /(Duration for sending HSDPA MAC-d flow when the data resources of a UE are sufficient + Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient).
Issue 01 (2013-07-15)
837
Range [0,+)
Description If Average downlink rate of the HSDPA service is smaller than Slow average downlink rate threshold of the HSDPA service, Times of slow average downlink rate + 1. The slow average downlink rate threshold is set by engineers during task creation.
[0,+)
Kbps
Average uplink rate of the HSDPA service = (Number of uplink bytes in HSDPA PDCP /(Duration for sending HSDPA MAC-d flow when the data resources of a UE are sufficient + Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient).
[0,+)
Num ber
If Average uplink rate of the HSDPA service is smaller than Slow average uplink rate threshold of the HSDPA service, Times of slow average uplink rate +1 The slow average uplink rate threshold is set by engineers during task creation.
[0,+)
Kbps
Average downlink rate of the HSDPA service when the data resources are sufficient.
Issue 01 (2013-07-15)
838
Param eter >DL Averag e Rate Slow (suffici ent resourc es)
Range [0,+)
Description If Average downlink rate of the HSDPA service < Slow average downlink rate threshold of the HSDPA service when the data resources are sufficient, Times of slow average downlink rate when the data resources are sufficient + 1. The slow average downlink rate threshold when the data resources are sufficient is set by engineers during task creation.
[0,+)
Kbps
Average downlink rate of the HSDPA service when the data resources are insufficient = Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are insufficient /Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient.
[0,+)
Num ber
If Average downlink rate of the HSDPA service < Slow average downlink rate threshold of the HSDPA service when the data resources are insufficient, Times of slow average downlink rate when the data resources are insufficient + 1. The slow average downlink rate threshold when the data resources are insufficient is set by engineers during task creation.
Issue 01 (2013-07-15)
839
Range N/A
Unit N/A
Description Time when a signaling message is sent or received. Direction for sending or receiving a signaling message.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
to CN from CN to other RNC from other RNC to NODEB from NODEB to UE from UE to SAS from SAS
N/A
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.
Signali ng Content
N/A
N/A
Measurement Information
Param eter Number Range [0,+) Unit N/A Description Number that uniquely identifies a measurement report (MR). Time when an MR is reported. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
840
Range Intra-freq measurement type Inter-freq measurement type Inter-RAT measurement type Event MR, such as E1A and so on
Unit N/A
Description MR type.
N/A
N/A
Name of a measurement object reported in an MR. The parameter value is displayed in the following format: RNC 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.
P-SC
[0,512]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[-24,0]
dB
Ratio of energy per modulating bit to the noise spectral density (Ec/ No). For details, see 3GPP 25.331. Received signal code power (RSCP). For details, see 3GPP 25.331. Received signal strength indicator (RSSI) of a GSM carrier. For details, see 3GPP TS 45.008.
[-115,-25]
dBm
N/A
dBm
[0,97]
dBm
Reference signal received power (RSRP). For details, see 3GPP 36.133.
Issue 01 (2013-07-15)
841
Range [0,33]
Unit dB
Description Reference signal received quality (RSRQ). For details, see 3GPP 36.133. Transmit power of a UE.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
UE TX Power
N/A
N/A
Mobility Analysis
Param eter Number Range [0,+) Unit N/A Description Number of a handover during a call. Whether a handover is abnormal. If a red exclamation mark is displayed in this column, the handover is abnormal. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Abnorm al
! Blank
N/A
Issue 01 (2013-07-15)
842
Range Softer handover Soft handover Intra-freq hard handover Inter-freq hard handover Inter-system incoming handover Inter-system outgoing handover/CS system handover Inter-system outgoing handover/Cell change order PS system handover Inter-system outgoing handover/ Enhanced PS system handover Inter-system outgoing handover/CS and PS system handover Inter-system outgoing handover/UE generated Incoming migration/ Static reloc in Incoming migration/HHO reloc in Incoming migration/Cell update reloc in
Unit N/A
Description Type of mobility analysis. Currently, the system supports the following mobility analysis types: Soft handover Hard handover Incoming inter-RAT handover Outgoing inter-RAT handover Incoming migration Outgoing migration Cell update Channel handover
Issue 01 (2013-07-15)
843
Param eter
Unit
Description
Supported NE Version
N/A
N/A
Start time.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Overlon g Interval
Yes No
N/A
If Interval > Overlong xxx delay threshold, The value of this parameter is Yes. Otherwise, the value is 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 handover delay threshold Overlong incoming handover delay threshold Overlong outgoing handover delay threshold Overlong channel handover delay threshold
End Time
N/A
N/A
End time.
Issue 01 (2013-07-15)
844
Range converage based load based but blind handover load based and measurement based forced handover emergency handover
Unit N/A
MutiRAB Info
1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
N/A
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Active Set
N/A
Measurement type.
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. Ratio of energy per modulating bit to the noise spectral density (Ec/ No). For details, see 3GPP 25.331. Received signal code power (RSCP). For details, see 3GPP 25.331.
[-24,0]
dB
[-115,-25]
dBm
Issue 01 (2013-07-15)
845
Range DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
N/A
[0,+)
kbps
UL RB rate when occuring the channel handover. DL RB rate when occuring the channel handover. Destination cell information.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
bps
N/A
N/A
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 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. Ratio of energy per modulating bit to the noise spectral density (Ec/ No) of 3G target cell. For details, see 3GPP 25.331.
>Ec/NO (dB)
[-24,0]
dB
Issue 01 (2013-07-15)
846
Param eter >RSCP (dBm) >Target Cell Operati on >Target Cell Operati on Time InterRAT carrier RSSI (dBm) RSRP
Range [-115,-25]
Unit dBm
Description Received signal code power (RSCP) of 3G target cell. For details, see 3GPP 25.331. Target cell operation of the 3G target cell when occuring the soft handover. Target cell operation time of the 3G target cell when occuring the soft handover. Received signal strength indicator (RSSI) of a GSM carrier of 2G target cell. For details, see 3GPP TS 45.008. Reference signal received power (RSRP) of LTE target cell. For details, see 3GPP 36.133. Reference signal received quality (RSRQ) of LTE target cell. For details, see 3GPP 36.133. Source UL channel type when occuring the channel handover.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RL ADD RL DEL
N/A
N/A
N/A
N/A
dBm
[-140,-43]
dBm
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RSRQ
[-19.5,-2.5]
dB
N/A
Issue 01 (2013-07-15)
847
Range DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
[0,+)
bps
UL RB rate when occuring the channel handover. DL RB rate when occuring the channel handover. Failure cause.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
bps
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Error type.
>Error Reason
N/A
Error reason.
Issue 01 (2013-07-15)
848
Service Analysis(RAB)
Param eter Numbe r Abnor mal Range [0,+) Unit N/A Description Record number of RAB service. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
! Blank
N/A
Whether a servive record is abnormal. If a red exclamation mark is displayed in this column, the record is abnormal.
! Blank
N/A
Whether a servive record of RAB setup is abnormal. If a red exclamation mark is displayed in this column, the record is abnormal.
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". CS_AMR CS_VP CS_OTHER PS_GENERAL PS_HSDPA PS_HSUPA PS_HSPA
N/A
N/A
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
849
Param eter Best Cell on RAB Setup Serving Cell on RAB Setup Peer Informa tion
Range N/A
Unit N/A
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Peer information. If the service is RAB on CS domain, it displays "Peer MSISDN". If the service is RAB on PS domain, it displays N/A.
1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS ...
N/A
! Blank
N/A
Whether a servive record of RAB release is abnormal. If a red exclamation mark is displayed in this column, the record that "Single-RAB Abnormal Release Indicator" or "MultipleRAB Abnormal Release Indicator" is YES.
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Issue 01 (2013-07-15)
850
Unit N/A
Description Cause of the call is disconnected, that is the cause value of NAS Disconnect message. The value is valid only on RAB CS domain.
N/A
Cause of the PDP is deactive, that is the cause value of Deactivate PDP context request message. The value is valid only on RAB PS domain.
RAB Release Time Best Cell Before RAB Release Serving Cell Before RAB Release MultiRAB Informa tion on RAB Release
N/A
N/A
N/A
N/A
N/A
N/A
1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS ...
N/A
[0,+)
Seco nd
RAB setup delay = Time when RAB setup completes - Time when RAB setup is requested.
Issue 01 (2013-07-15)
851
Range [0,+)
Description RAB duration = Time when RAB is released - Time when RAB setup completes Service duration.
[0,+)
BSC6900 If the service is RAB on CS domain, V900R013C00 it displays the service duration (that or later version is call time). If the service is RAB on PS domain, it displays N/A (that is not involved).
[0,+)
Byte
Total uplink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total throughput on uplink of RAB process.
[0,+)
Seco nd
Total uplink transmission duration. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total transmission duration on uplink of RAB process.
[0,+)
Kbps
Average uplink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays average throughput on uplink of RAB process. Average uplink throughput = Total uplink throughput/Total uplink transmission duration
Yes No
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. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
852
Range [0,+)
Unit Byte
Description Total downlink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total throughput on downlink of RAB process.
[0,+)
Seco nd
Total downlink transmission duration. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total transmission duration on downlink of RAB process.
[0,+)
Kbps
Average downlink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays average throughput on downlink of RAB process. Average downlink throughput = Total downlink throughput/Total downlink transmission duration
Yes No
N/A
If "Average Downlink Throughput" is smaller than "Average Downlink Throughput Threshold", the record has the problem that the average downlink throughput is too small. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
853
Summary
Parame ter Serial Number Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Status
N/A
N/A
Whether a call record is abnormal. If a red exclamation mark is displayed in this column, the call record is abnormal.
Abnorm al 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. Network technology type.
Network
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access Type
Intra-RAT RRC Access Incoming HO/ Intra-RAT Incoming HO Incoming HO/ UTRAN Incoming HO Incoming HO/ GERAN Incoming HO
N/A
Access Time
N/A
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access Cell
N/A
N/A
Cell that a UE accesses at the beginning of a call. The parameter value is displayed in the following format: eNodeB name:cell name (eNodeB ID:cell ID).
Issue 01 (2013-07-15)
854
Range
Unit
Description
Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Release Cell
N/A
N/A
Cell from which a UE is released at the end of a call. The parameter value is in the following format: eNodeB name:cell name (eNodeB ID:cell ID).
User ID:Alias
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
IMEITAC
00000000-99999 999
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.
Termina l Model
N/A
N/A
Model of a UE.
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Duratio n
[0,+)
Second
Duration of a call, which is displayed in the format of hh:mm:ss.nnn. Call duration = Release time Access time.
User Information
Parameter Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version
User ID:Alias
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
Issue 01 (2013-07-15)
855
Parameter
Range
Unit
Description
STMSI
MMEC Range:BIT STRING (SIZE (8)) m-TMSI Range: BIT STRING (SIZE (32))
bit
S-temporary mobile subscriber identity (S-TMSI) of a subscriber. The parameter display is in the following format: MMEC:mTMSI. For more information please see 3GPP 36.331 6.3.6 S-TIMSI
[0,2^32-1]
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
[0,2^32-1]
N/A
IMEI-TAC
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.
Terminal Model
N/A
N/A
Model of a UE.
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
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. RATs supported by a UE.
>Support RAT
N/A
N/A
Issue 01 (2013-07-15)
856
Parameter
Range
Unit
Description
N/A
>Device Type
N/A
Whether a UE supports battery consumption optimization. If the parameter is zero, it indicates that the device can foresee to particularly benefit from NWbased 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.
>Category Class
N/A
>>Uplink Physical Layer Parameter >>>Maxim um Number of UL-SCH Transport Block Bits Transmitte d Within A TTI
N/A
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
857
Parameter
Range
Unit
Description
>>>Maxim um Number of Bits of an UL-SCH Transport Block Transmitte d Within A TTI >>>Suppor t for 64QAM In UL >>Downlin k Physical Layer Parameter >>>Maxim um Number of DL-SCH Transport Block Bits Received Within A TTI >>>Maxim um Number of Bits of a DL-SCH Transport Block Received Within A TTI >>>Suppor t for 64QAM In DL
N/A
N/A
Yes No
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
Yes No
N/A
Issue 01 (2013-07-15)
858
Access Information
Parameter Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access Time
N/A
N/A
Access Cell
N/A
N/A
Cell that a UE accesses at the beginning of a call. The parameter value is in the following format: eNodeB name: cell name ( eNodeB ID:cell ID).
Access TA
[0,1314]
16*Ts=0.5 2 ms
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access UL RSRP
[-140,-43]
dBm
Reference signal received power (RSRP) on the uplink during the access of a call. SINR on the uplink during the access of a call.
Access UL SINR
[-15,35]
dB
Access Type
RRC Access Incoming HO/ Intra-eNodeB Incoming HO Incoming HO/ UTRAN Incoming HO Incoming HO/ GERAN Incoming HO
N/A
Issue 01 (2013-07-15)
859
Parameter
Range
Unit
Description
Access Cause
N/A
N/A
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
The delay time between the time of access request and the time of access completion.
Release Information
Parameter Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Release Time
N/A
N/A
Release Cell
N/A
N/A
Cell from which a UE is released at the end of a call. The parameter value is in the following format: eNodeB name : cell name (eNodeB ID:cell ID).
N/A
Issue 01 (2013-07-15)
860
Parameter
Range
Unit
Description
Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Handover based on the distance Handover based on the coverage Handover based on the load balancing
N/A
No.
[0,+)
N/A
Number that uniquely identifies a LTE 3900 sent and received signaling message. V100R005 C00 or later version Time when a signaling message is sent or received. LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Signaling Time
N/A
N/A
Signaling Direct
Uplink Downlin k
N/A
Signaling Type
N/A
N/A
Type of a signaling message that complies with any protocol and is transmitted over the S1-MME or Uu interface. For example, RRC CONNECT REQUEST is a signaling type.
Signaling Context
N/A
N/A
Issue 01 (2013-07-15)
861
MR Time
N/A
N/A
N/A
MR Object Type
N/A
Eutran Cell ID
[0,255]
N/A
LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version
PCI
[0,503]
N/A
RSRP
[-140,-43]
dBm
RSRQ
[-19.5,-2.5]
dB
RSCP
[-115,-25]
dBm
RSCP of a neighboring cell when the measurement type is inter-RAT and the RAT is UTRAN in an MR.
Issue 01 (2013-07-15)
862
Parameter EcNo
Range [-24,0]
Unit dB
Description Ec/No of a neighboring cell when the measurement type is inter-RAT and the RAT is UTRAN in an MR. Network color code (NCC) of a neighboring cell when the measurement type is interRAT and the RAT is GERAN in an MR. Base station color code (BCC) of a neighboring cell when the measurement type is inter-RAT and the RAT is GERAN in an MR. ARFCN of a neighboring cell when the measurement type is inter-RAT and the RAT is GERAN in an MR. Frequency band indicator of a neighboring cell when the measurement type is interRAT and the RAT is GERAN in an MR. RSSI of a neighboring cell when the measurement type is inter-RAT and the RAT is GERAN in an MR. Pilot signal phase of a neighboring cell when the measurement type is interRAT and the RAT is CDMA2000 in an MR. Pilot signal strength of a neighboring cell when the measurement type is interRAT and the RAT is CDMA2000 in an MR.
Supported NE Version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version
[0,7]
N/A
[0,7]
N/A
ARFCN
[0,1023]
N/A
DCS1800 PCS1900
N/A
RSSI
[-110,-48]
dBm
[0,32767]
chip
[-29,33]
dBm
Issue 01 (2013-07-15)
863
Abnormal
! Blank
N/A
Issue 01 (2013-07-15)
864
Range The handover interface types of intraRAT handover are the following: intra-eNodeB handover handover based on the X2 interface; handover based on the S1 interface. The handover interface types of interRAT handover are the following: handover based on the S1 interface.
Unit N/A
N/A
Preparation time for initiating an incoming or outgoing intra-RAT or inter-RAT handover during a call. Interval = Start time - End time.
Interval
[0,+)
Issue 01 (2013-07-15)
865
Range Yes No
Unit N/A
Description If the interval exceeds the overlong xxx delay threshold, the value of this parameter is Yes. Otherwise, the value of this parameter is No. The overlong xxx delay threshold is set by engineers during task creation. The threshold types are as follows: Overlong intra-RAT outgoing handover delay threshold; Overlong inter-RAT outgoing handover delay threshold; Overlong intra-RAT incoming handover delay threshold.
End Time
N/A
N/A
End time.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
Source Cell
N/A
N/A
Source cell from which a call is handed over. The parameter value is in the following format: eNodeB name : cell name (eNodeB ID:cell ID).
UL RSRP upon Handover UL SINR upon Handover Target Cell for Handover
[-140,-43]
dBm
RSRP of the serving cell on the uplink during the handover of a call.
[-15,35]
dB
SINR of the serving cell on LTE 3900 the uplink during the V100R005C00 handover of a call. or later version Target cell to which a call is handed over. The parameter value is in the following format: eNodeB name: cell name (eNodeB ID:cell ID). LTE 3900 V100R005C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
866
Parameter Target Cell UL RSRP After Handover Target Cell UL SINR After Handover Handover Triggering Cause
Range [-140,-43]
Unit dBm
Description RSRP of the serving cell on the uplink during the handover of a call.
[-15,35]
dB
SINR of the serving cell on LTE 3900 the uplink during the V100R005C00 handover of a call. or later version Triggering cause of an outgoing handover during a call. The triggering cause of an incoming handover is empty. LTE 3900 V100R005C00 or later version
Handover based on the distance Handover based on the coverage Handover based on the load balancing
N/A
Radio Network Layer Transport Layer NAS Layer Protocol Layer Miscellaneou s
N/A
Triggering cause of the preparation of an outgoing handover during a call. The preparation triggering cause of an incoming handover is empty.
Issue 01 (2013-07-15)
867
Range Handover preparation to target cell failure 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
Unit N/A
Description Cause of a failed outgoing handover during a call. The cause of a failed incoming handover is empty.
Cancel Handover
Yes No
N/A
Whether the HANDOVER CANCEL message is received during the handover of a call. Handover result of a call, including the handover preparation result and handover execution result.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
Handover Result
N/A
Handover TA
[0,1314]
16*Ts =0.52 ms
Issue 01 (2013-07-15)
868
Range [-140,-43]
Unit dBm
Description Reference signal received power (RSRP) on the UL during the handover of a call. SINR on the UL during the handover of a call. ID of the E-RAB and QCI that is handed over. ID of the E-RAB that is handed over. Service type for which ERAB is handed over. The parameter values are as follows: 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. Non GBR (QCIN): nonGBR service with low QoS. N = 5, 6, 7, 8, or 9.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[-15,35]
dB
N/A
N/A
[0,15]
N/A
E-RAB QCI
GBR(QCI1) GBR(QCI2) GBR(QCI3) GBR(QCI4) Non GBR (QCI5) Non GBR (QCI6) Non GBR (QCI7) Non GBR (QCI8) Non GBR (QCI9)
N/A
E-RAB Analysis
Parameter No. Range [1,+) Unit N/A Description Serial number of an ERAB ID. It uniquely identifies an E-RAB ID. Setup result of an E-RAB setup request. Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
! Blank
N/A
Issue 01 (2013-07-15)
869
Range Radio Network Layer Transport Layer NAS Layer Protocol Layer Miscellaneous
Unit N/A
Description Cause of failed E-RAB setup. The parameter value also includes detailed causes.
GBR(QCI1) GBR(QCI2) GBR(QCI3) GBR(QCI4) Non GBR (QCI5) Non GBR (QCI6) Non GBR (QCI7) Non GBR (QCI8) Non GBR (QCI9)
N/A
QCI level on E-RAB setup. The parameter values are as follows: GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
E-RAB Request Time Cell on E-RAB Request E-RAB Setup Time TA on E-RAB Setup
N/A
N/A
Time when E-RAB is requested. Cell when E-RAB is requested. Time of RAB setup.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
870
N/A
N/A
N/A
N/A
[0,1314]
[-140,-43]
Reference signal received power (RSRP) on the uplink during the E-RAB setup of a call. SINR on the uplink during the E-RAB setup of a call.
[-15,35]
dB
Issue 01 (2013-07-15)
Range ! Blank E-RAB abnormal release triggered by MME E-RAB abnormal release triggered by eNodeB E-RAB abnormal release triggered by outgoing HO execution failure
Unit N/A
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
Yes No
N/A
Identifier indicating whether data is being transmitted when an ERAB is released. If no data is being transmitted when the ERAB is released, the subscriber cannot perceive the exception.
N/A
QCI level on E-RAB release. GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
N/A
N/A
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
871
Range [0,1314]
Description Time advance (TA) during the E-RAB release of a call. Reference signal received power (RSRP) on the uplink during the E-RAB release of a call. SINR on the uplink during the E-RAB release of a call. End where an E-RAB is released. End where an E-RAB is released.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[-140,-43]
[-15,35]
dB
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
872
Range GBR(QCI1) GBR(QCI2) GBR(QCI3) GBR(QCI4) Non GBR (QCI5) Non GBR (QCI6) Non GBR (QCI7) Non GBR (QCI8) Non GBR (QCI9)
Unit N/A
Description QCI level on E-RAB setup. The parameter values are as follows: GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
>E-RAB Request Time >Cell on ERAB Request >E-RAB Setup Time >E-RAB Setup Result >E-RAB Setup Cause
N/A
N/A
Time when E-RAB is requested. Cell when E-RAB is requested. Time of RAB setup.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
N/A
N/A
N/A
Succeed Failure Radio Network Layer Transport Layer NAS Layer Protocol Layer Miscellaneou s
N/A
Setup result of an E-RAB setup request. Cause of E-RAB setup. The parameter value also includes detailed causes.
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
873
Range [0,+)
Unit Seco nd
Description E-RAB setup delay = Time when E-RAB setup completes - Time when ERAB setup is requested. MR information during the ERAB setup of a call. Time advance (TA) during the E-RAB setup of a call. Reference signal received power (RSRP) on the uplink during the E-RAB setup of a call. SINR on the uplink during the E-RAB setup of a call. Priority information of an ERAB. Priority of a setup E-RAB.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
N/A
[0,1314]
>>UL RSRP
[-140,-43]
>>UL SINR
[-15,35]
dB
N/A
N/A
N/A
N/A
>>E-RAB Passive Preemptability >E-RAB Rate Information >>Maximum ERAB DL Rate >>Assured ERAB DL Rate
N/A
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
874
N/A
Rate information of an ERAB. Maximum downlink rate of a setup E-RAB. Assured downlink rate of a setup E-RAB.
kbps
kbps
Issue 01 (2013-07-15)
Parameter >>Maximum ERAB UL Rate >>Assured ERAB UL Rate E-RAB Release Information >E-RAB Request Service Type(QCI) on E-RAB Release
Unit kbps
Description Maximum uplink rate of a setup E-RAB. Assured uplink rate of a setup E-RAB. The information during the ERAB release of a call. QCI level on E-RAB release. GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
kbps
N/A
N/A
N/A
N/A
Time when an E-RAB is released. E-RAB duration = Time when E-RAB is released Time when E-RAB setup completes Cell from which an E-RAB is released.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,+)
Seco nd
N/A
N/A
Issue 01 (2013-07-15)
875
Range E-RAB abnormal release triggered by MME E-RAB abnormal release triggered by eNodeB E-RAB abnormal release triggered by outgoing HO execution failure
Unit N/A
N/A
End where an E-RAB is released. Identifier indicating whether data is being transmitted when an E-RAB is released. If no data is being transmitted when the E-RAB is released, the subscriber cannot perceive the exception.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C01 or later version
N/A
N/A
N/A
MR information during the ERAB release of a call. Time advance (TA) during the E-RAB release of a call. Reference signal received power (RSRP) on the uplink during the E-RAB release of a call. SINR on the uplink during the E-RAB release of a call.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,1314]
>>UL RSRP
[-140,-43]
>>UL SINR
[-15,35]
dB
Issue 01 (2013-07-15)
876
N/A
N/A
N/A
ms
N/A
CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-25 5 0-25 5
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR.
N/A
Issue 01 (2013-07-15)
877
User Information
Param eter User ID:Alia s Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Termin al Model IMEITAC N/A N/A Model of the terminal that initiates a service. IMEI-TAC of the terminal that initiates a service. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
Procedure Information
Param eter Access Type Ran ge N/A Unit N/A Description Radio access network (RAN) type for the signaling procedure. This parameter can be any of the following: GPRS UMTS LTE CHR Type N/A N/A Type of the signaling procedure. This parameter can be any of the following: SM MM Procedu re Type N/A N/A Name of a signaling procedure. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
878
Ran ge N/A
Unit N/A
Description Procedure initiating party (UE or MME) and cause. For details, see the Description of Procedure Initiating Causes in the appendix.
N/A
P-TMSI received from a terminal when a procedure is initiated. P-TMSI that the network allocates to a terminal. If a procedure does not involve two routing areas, the field indicates the routing area where the procedure is initiated. If a procedure involves in two routing areas, the field indicates the new routing area.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
Cell
N/A
N/A
Old RAC
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. Indicates whether a procedure requires authentication. Indicates whether a procedure requires IMEI check. Indicates whether a procedure requires P-TMSI reallocation.
Authent ication Flag IMEI Check Flag PTMSI Realloc ation Flag Externa l Cause Old SGSN Address
N/A
N/A
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
If a procedure involves two SGSNs, the field indicates the IP address of the old SGSN.
Issue 01 (2013-07-15)
879
Ran ge N/A
Unit N/A
Description APN selection mode. This parameter can be any of the following: MS & Network Verified MS not Verified Network not Verified
N/A
SN of a CHR that is sent to the billing center. Charging attribute of a UE. This parameter can be any of the following: Unspecified Hot billing Charging Flat rate Charging Prepaid Charging Normal Charging
N/A
N/A
N/A
Allocation/retention priority. This parameter can be any of the following: High priority Normal priority Low priority
N/A
N/A
Subscribed reliability class. This parameter can be any of the following: Subscribed reliability class 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
Issue 01 (2013-07-15)
880
Ran ge N/A
Unit N/A
Description Subscribed delay class. This parameter can be any of the following: Subscribed delay class Delay class 1 Delay Class 2 Delay Class 3 Delay Class 4 (best effort)
N/A
N/A
Subscribed precedence. This parameter can be any of the following: Subscribed precedence High priority Normal priority Low priority Reserved
N/A
N/A
Subscribed peak throughput. This parameter can be any of the following: Subscribed peak throughput Up to 1 000 octet/s Up to 2 000 octet/s Up to 4 000 octet/s Up to 8 000 octet/s Up to 16 000 octet/s Up to 32 000 octet/s Up to 64 000 octet/s Up to 128 000 octet/s Up to 256 000 octet/s
Issue 01 (2013-07-15)
881
Ran ge N/A
Unit N/A
Description Subscribed mean throughput. This parameter can be any of the following: Subscribed mean throughput 100 octet/h 200 octet/h 500 octet/h 1000 octet/h 2000 octet/h 5000 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
N/A
N/A
Subscribed delivery of erroneous SDUs. This parameter can be any of the following: No detect('-') Erroneous SDUs are delivered('yes') Erroneous SDUs are not delivered ('no')
Deliver y Order
N/A
N/A
Subscribed delivery order. This parameter can be any of the following: With delivery order ('yes') Without delivery order ('no')
Issue 01 (2013-07-15)
882
Ran ge N/A
Unit N/A
Description Subscribed traffic class. This parameter can be any of the following: Conversational class Streaming class Interactive class Background class
Maxim um SDU Size Maxim um Bit Rate for Uplink Maxim um Bit Rate for Downli nk SDU Error Ratio
0-25 5
byte
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-86 40
bps
0-25 6000
bps
N/A
N/A
Subscribed SDU error ratio. This parameter can be any of the following: 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
Issue 01 (2013-07-15)
883
Ran ge N/A
Unit N/A
Description Subscribed residual BER. This parameter can be any of the following: 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
N/A
N/A
Subscribed traffic handling priority. This parameter can be any of the following: Priority level 1 Priority level 2 Priority level 3
Transfe r Delay Guarant eed Bit Rate for Uplink Guarant eed Bit Rate for Downli nk GTP Tunnel Version
0-25 5 0-86 40
ms
Transfer delay.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
bps
0-25 6000
bps
N/A
N/A
GTP tunnel version. This parameter can be any of the following: GTPv0 GTPv1
Issue 01 (2013-07-15)
884
Ran ge N/A
Unit N/A
Description Type of the PDP requested by a UE. This parameter can be any of the following: IPv4 IPv6 BOTH(IPV4&IPV6) PPP Empty
PDP Address in Use GGSN Address for Signali ng GGSN Address for User Traffic APN
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Access Time
N/A
Issue 01 (2013-07-15)
885
Rang e N/A
Unit N/A
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-655 35 N/A
ms
N/A
CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
NE Name
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-255
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR.
0-255
N/A
User Information
Parameter User ID:Alias Rang e N/A Uni t N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Terminal Model IMEI-TAC N/A N/A Model of the terminal that initiates a service. IMEI-TAC of the terminal that initiates a service. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
Issue 01 (2013-07-15)
886
Procedure Information
Parameter Access Type Rang e N/A Uni t N/A Description Radio access network (RAN) type for the signaling procedure. This parameter can be any of the following: GPRS UMTS LTE CHR Type N/A N/A Type of the signaling procedure. This parameter can be any of the following: SM MM Procedure Type N/A N/A Name of a signaling procedure. For details, see the Description of Signaling Procedures in the appendix. N/A N/A Procedure initiating party (UE or MME) and cause. For details, see the Description of Procedure Initiating Causes in the appendix. MS P-TMSI 0-2^3 2-1 0-2^3 2-1 N/A N/A P-TMSI received from a terminal when a procedure is initiated. P-TMSI that the network allocates to a terminal. If a procedure does not involve two routing areas, the field indicates the routing area where the procedure is initiated. If a procedure involves two routing areas, the field indicates the new routing area. Cell N/A N/A Cell where a procedure is initiated. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
Issue 01 (2013-07-15)
887
Rang e N/A
Uni t N/A
Description 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. Indicates whether an MM procedure requires authentication. Indicates whether an MM procedure requires IMEI check. Indicates whether an MM procedure requires P-TMSI reallocation. Procedure result and failure cause. For details, see the Description of Exception Cause Fields in the appendix.
Authenticati on Flag IMEI Check Flag PTMSI Reallocation Flag External Cause
N/A
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
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.
Begin Time
N/A
Issue 01 (2013-07-15)
888
Rang e N/A
Unit N/A
Description End time of the signaling procedure. Delay time of a signaling procedure. CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-655 35 N/A
ms
N/A
NE Name Board Subrack No. Board Slot No. Board Proc No.
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-255
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR. Number of the process that generates a CHR.
0-255
N/A
0-655 35
N/A
User Information
Parame ter User ID:Alias Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Termina l Model N/A N/A Model of the terminal that initiates a service. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
889
Unit N/A
Procedure Information
Parame ter CHR Type Ran ge N/A Unit N/A Description Type of the signaling procedure. This parameter can be any of the following: SM MM Procedur e Type Procedur e Init Cause N/A N/A Name of a signaling procedure. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
N/A
Procedure initiating party (UE or MME) and cause. For details, see the Description of Procedure Initiating Causes in the appendix.
N/A
N/A
PLMN of the eNodeB where a UE is located when a signaling procedure is initiated. ID of the eNodeB where a UE is located when a signaling procedure is initiated. UES1AP connection identification allocated by an MME in a traffic procedure. Time when the UES1AP connection identification is allocated by an MME in a traffic procedure. Tracking area where a terminal is located when a signaling procedure is initiated.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
890
Ran ge N/A
Unit N/A
Description Requested PDN type in a traffic procedure. This parameter can be any of the following: IPV4 IPV6 both(IPV4 & IPV6) unused
APN
N/A
N/A
Requested APN in a traffic procedure. Negotiated cause in a procedure result. Procedure result and failure cause.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Protocol Cause External Cause Serving Gateway Address PDN Gateway Address PDN Gateway Host Name UE Uplink Max Bandwid th UE Downlin k Max Bandwid th APN Uplink Max Bandwid th
N/A
N/A
N/A
N/A
N/A
N/A
IP address of the Serving Gateway in a signaling procedure. IP address of the PDN Gateway in a signaling procedure. Domain name of the PDN Gateway in a signaling procedure.
N/A
N/A
N/A
N/A
02^32 -1
bit/s
02^32 -1
bit/s
02^32 -1
bit/s
Issue 01 (2013-07-15)
891
Ran ge 02^32 -1
Unit bit/s
N/A
QCI information allocated by a session. ARP information allocated by a session. Maximum bearer-level uplink bandwidth allocated by a session. Maximum bearer-level downlink bandwidth allocated by a session. Guaranteed bearer-level uplink bandwidth allocated by a session. Guaranteed bearer-level downlink bandwidth allocated by a session.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
ARP
N/A
bit/s
bit/s
bit/s
bit/s
Begin Time
N/A
Issue 01 (2013-07-15)
892
Ran ge N/A
Unit N/A
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
ms
N/A
CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
NE Name Board Subrack No. Board Slot No. Board Proc No.
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR. Number of the process that generates a CHR.
N/A
N/A
User Information
Parame ter User ID:Alias Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Terminal Model N/A N/A Model of the terminal that initiates a service. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
893
Unit N/A
Procedure Information
Parame ter CHR type Ran ge N/A Unit N/A Description Type of the signaling procedure. This parameter can be any of the following: SM MM Procedu re Type Procedu re Init Cause N/A N/A Name of a signaling procedure. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
N/A
Procedure initiating party (UE or MME) and cause. For deTACls, see the Description of Procedure Initiating Causes in the appendix.
N/A
N/A
PLMN of the eNodeB where a UE is located when a signaling procedure is initiated. ID of the eNodeB that serves a UE when a signaling procedure is initiated. UES1AP connection identification allocated by an MME in a traffic procedure. Time when the UES1AP connection identification is allocated by an MME in a traffic procedure. Tracking area where a terminal is located when a signaling procedure is initiated.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
894
Parame ter New GUTI PLMN New GUTI MMEGI New GUTI MMEC New GUTI MTMSI Old GUTI PLMN Old GUTI MMEGI Old GUTI MMEC Old GUTI MTMSI Old TAC Target ID PLMN Target ID Target MME UE S1AP ID Target MME S1AP ID Time
Ran ge N/A
Unit N/A
Description PLMN of GUTI allocated by the network in a traffic procedure. MME Group Id of GUTI allocated by the network in a traffic procedure. MME CODE of GUTI allocated by the network in a traffic procedure. M-TMSI of GUTI allocated by the network in a traffic procedure. PLMN of GUTI received from a UE in a traffic procedure. MME Group Id of GUTI received from a UE in a traffic procedure. MME CODE of GUTI received from a UE in a traffic procedure. M-TMSI of GUTI received from a UE in a traffic procedure. ID of the old tracking area in a signaling procedure that involves more than one tracking area. PLMN of the target eNodeB in a signaling procedure that involves more than one eNodeB. ID of the target eNodeB in a signaling procedure that involves more than one eNodeB. Target UES1AP connection identification allocated by an MME in a traffic procedure. Time when the target UES1AP connection identification is allocated by an MME in a traffic procedure.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-655 35 0-255
N/A
N/A
N/A
N/A
0-655 35 0-255
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
895
Parame ter Target TAC Protocol Cause External Cause Access Type
Ran ge N/A
Unit N/A
Description ID of the target tracking area in a signaling procedure that involves more than one tracking area. Protocol cause value in a procedure result. Procedure result and failure cause.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
Radio access network (RAN) type for the signaling procedure. This parameter can be any of the following: GPRS UMTS LTE
Serving Gateway Address Serving Gateway Host Name MS PTMSI Allocate d PTMSI GU RAC
N/A
N/A
IP address of the Serving Gateway in a signaling procedure. Domain name of the Serving Gateway in a signaling procedure.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
P-TMSI received from a terminal when a procedure is initiated. P-TMSI that the network allocates to a terminal. 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. 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 CGI of the target cell. Otherwise, the field is empty.
N/A
N/A
GU CI
N/A
N/A
Issue 01 (2013-07-15)
896
Ran ge N/A
Unit N/A
Description If a UE is handed over from a 2G/3G network to a LTE network or the location of the UE is updated, the field is the RAC of the old routing area. Otherwise, the field is empty. Indicates whether an MM procedure requires authentication. Indicates whether an MM procedure requires IMEI check. Indicates whether an MM procedure requires P-TMSI reallocation. If a procedure involves two SGSNs, the field indicates the IP address of the old SGSN.
Authenti cation Flag IMEI Check Flag PTMSI Realloca tion Flag Old SGSN Address
N/A
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
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.
N/A
Issue 01 (2013-07-15)
897
Unit N/A
NE Name
N/A
N/A
Name of a CN NE.
User Information
Param eter User ID:Alia s Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Supported NE Version UGW9810 V900R011C01 or later version
Procedure Information
Param eter Proced ure Type APN Rang e N/A Unit N/A Description Name of a signaling procedure. Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
Issue 01 (2013-07-15)
898
Rang e NA UTR AN GER AN WLA N GAN HSP A Evolu tion EUT RAN
Unit N/A
N/A
N/A
Cause of the exception carried in an Access message. For details, see the Description of Exception Cause in the appendix.
PDP Type
N/A
MSIP
N/A
N/A
MS IP V4
N/A
N/A
Issue 01 (2013-07-15)
899
Param eter MS IP V6 SGSN Addres s for Signali ng SGSN Addres s for Data GGSN Addres s for Signali ng GGSN Addres s for Data Protoco l Version
Rang e N/A
Unit N/A
Description IPv6 address allocated to the subscriber's MS IPv4 address for configuring the control plane of the SGSN that the subscriber's MS accesses
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
IPv4 address for configuring the user plane of the SGSN that the subscriber's MS accesses IPv4 address for configuring the control plane of the GGSN that the subscriber's MS accesses
N/A
N/A
N/A
N/A
IPv4 address for configuring the user plane of the GGSN that the subscriber's MS accesses Version of the GTP protocol
N/A
Issue 01 (2013-07-15)
900
Unit N/A
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. Information about the PLMN served by the access SGSN Location area where the signaling procedure is triggered Routing area where the signaling procedure is triggered Serving area where the signaling procedure is triggered Cell where the signaling procedure is triggered IPv6 address for configuring the control plane of the SGSN that the subscriber's MS accesses
UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
RAC
N/A
N/A
SAC
N/A
N/A
CI
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
901
Param eter GGSN IPv6 Addres s for Signali ng SGSN IPv6 Addres s for Data GGSN IPv6 Addres s for Data NSAPI
Rang e N/A
Unit N/A
Description IPv6 address for configuring the control plane of the GGSN that the subscriber's MS accesses
N/A
N/A
IPv6 address for configuring the user plane of the SGSN that the subscriber's MS accesses
N/A
N/A
IPv6 address for configuring the user plane of the GGSN that the subscriber's MS accesses
N/A
N/A
Identity of the service access point (SAP) in the network layer Identifies whether an activation is a first or second activation
Activati on Type
N/A
N/A
N/A
Identity of the GTP-C tunneling protocol Marks different charging characteristics. For details, see 5.1.2.2.7 in 3GPP TS 32.298. 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.
UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
0-2^3 2-1
N/A
Issue 01 (2013-07-15)
902
Rang e 0-2^3 2-1 SSG N MME GGS N SGW PGW SGW +PG W
Unit N/A
Description Unique No. of each service procedure in the whole procedure for a subscriber Initiator of the signaling message recorded in the CHR
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
Slot
N/A
N/A
Logical board No. of the device that processes the CHR Logical CPU No. of the device that processes the CHR SPU group No. of the device that processes the CHR SPU instance No. of the device that processes the CHR MCC and MNC of the subscriber's serving network CGI information, including MCC, MNC, LAC, and CI SAI information, including MCC, MNC, LAC, and SAC
UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
CPU
N/A
N/A
SPU Group SPU Instanc e Serving Networ k ULI CGI ULI SAI
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
903
Param eter ULI RAI ULI TAI ULI ECGI ULI LAI Peer IPV4 Addres s for Signali ng Peer IPV4 Addres s for Data Local IPV4 Addres s for Signali ng Local IPV4 Addres s for Data Peer IPV6 Addres s for Signali ng
Rang e N/A
Unit N/A
Description RAI information, including MCC, MNC, LAC, and RAC TAI information, including MCC, MNC, and TAC ECGI information, including MCC, MNC, and ECI LAI information, including MCC, MNC, and LAC IPv4 address for configuring the control plane of the CN NE interconnected to this NE
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
IPv4 address for configuring the user plane of the CN NE interconnected to this NE
N/A
N/A
N/A
N/A
N/A
N/A
IPv6 address for configuring the control plane of the CN NE interconnected to this NE
Issue 01 (2013-07-15)
904
Param eter Peer IPV6 Addres s for Data Local IPV6 Addres s for Signali ng Local IPV6 Addres s for Data Proced ure Transac tion ID (PTI)
Rang e N/A
Unit N/A
Description IPv6 address for configuring the user plane of the CN NE interconnected to this NE
N/A
N/A
N/A
N/A
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.
Issue 01 (2013-07-15)
905
Rang e MS or netwo rk provi ded APN, subsc ribed verifi ed MS provi ded APN, subsc riptio n not verifi ed Netw ork provi ded APN, subsc riptio n not verifi ed
Unit N/A
PDN Type
N/A
N/A
N/A
ID of the default bearer. This parameter can also be used to identify the PDN connection. ID of all bearers (including the default bearer) for the PDN connection
N/A
N/A
Issue 01 (2013-07-15)
906
Param eter Bearer QoS PCI Bearer QoS PL Bearer QoS PVI Bearer QoS QCI Bearer QoS MBRU Bearer QoS MBRD Bearer QoS GBRU Bearer QoS GBRD UE Time Zone Protoco l Cause Flow QoS QCI Flow QoS MBRU Flow QoS MBRD
Rang e N/A
Unit N/A
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Standard cause value carried in the response message QCI in the Flow QoS parameter
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
907
Param eter Flow QoS GBRU Flow QoS GBRD UL Total Volume DL Total Volume Total Volume First URL MS Side Port of First URL Networ k Side Port of First URL
Rang e N/A
Unit N/A
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
byte
Uplink traffic volume recorded in the CHR Downlink traffic volume recorded in the CHR Total traffic volume recorded in the CHR First 20 bytes of the first URL that the subscriber visits during a service procedure TCP/UDP port No. (on the UE side) of the first URL that the subscriber visits during a service procedure
byte
byte
N/A
N/A
N/A
N/A
N/A
TCP/UDP port No. (on the network side) of the first URL that the subscriber visits during a service procedure
Issue 01 (2013-07-15)
908
N/A
N/A
N/A N/A N/A N/A N/A N/A High TA Low uplink level on the TCH Uplink interference on the TCH
Issue 01 (2013-07-15)
909
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Poor uplink quality of the TCH Sudden decrease of the uplink level Low downlink level on the TCH Downlink interference on the TCH Poor downlink quality of the TCH Sudden decrease of the downlink level Low uplink and downlink level on the TCH Uplink and downlink interference on the TCH Poor uplink and downlink quality of the TCH Any other Um interface-related fault Transmission fault CN fault Peer fault Other causes N/A N/A N/A N/A N/A High TA Low uplink level on the TCH Uplink interference on the TCH
Issue 01 (2013-07-15)
910
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Poor uplink quality of the TCH Sudden decrease of the uplink level Low downlink level on the TCH Downlink interference on the TCH Poor downlink quality of the TCH Sudden decrease of the downlink level Low uplink and downlink level on the TCH Uplink and downlink interference on the TCH Poor uplink and downlink quality of the TCH Any other Um interface-related fault Transmission fault CN fault Peer fault Other causes N/A N/A N/A N/A N/A
Poor quality on the Um interface or fault of the terminal System resource congestion
N/A
Issue 01 (2013-07-15)
911
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Transmission fault CN fault Other causes N/A N/A N/A N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault
N/A
N/A
Issue 01 (2013-07-15)
912
Dom ain
Servi ce Type
Abnormal Type
RANCS
Call
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
N/A N/A N/A N/A High TA Low uplink level on the TCH Uplink interference on the TCH Poor uplink quality of the TCH Sudden decrease of the uplink level
Issue 01 (2013-07-15)
913
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Low downlink level on the TCH Downlink interference on the TCH Poor downlink quality of the TCH Sudden decrease of the downlink level Low uplink and downlink level on the TCH Uplink and downlink interference on the TCH Poor uplink and downlink quality of the TCH Any other Um interface-related fault Transmission fault CN fault Peer fault Other causes N/A N/A N/A N/A N/A
Abnormal Delay
Overlong access time (MOC) Overlong access time (MTC) Overlong setup time (MOC) Overlong setup time (MTC)
N/A
N/A N/A
Issue 01 (2013-07-15)
914
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Short calls (MOC) Short calls (MTC) N/A N/A N/A
Poor quality on the Um interface Bad DL HQI Bad UL HQI Bad UL VQI Uplink oneway audio Downlink oneway audio DL/UL no audio Downlink crosstalk Uplink crosstalk
N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
SMS
N/A N/A
RANPS
PS
Setup Failure
Case3: Attach fail Case2: PDP active fail Case3: No service interaction timeout
Service Interruption
N/A
Issue 01 (2013-07-15)
915
Dom ain
Servi ce Type
Abnormal Type
Step1: Service interaction timeouts Step2: Service interaction with long latency
N/A
N/A
N/A
N/A N/A
Issue 01 (2013-07-15)
916
Interface
Key Signaling 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 ROUTING AREA UPDATE ACCEPT ROUTING AREA UPDATE REJECT ROUTING AREA UPDATE COMPLETE AUTHENTICATION AND CIPHERING REJECT AUTHENTICATION AND CIPHERING REQUEST AUTHENTICATION AND CIPHERING RESPONSE
Issue 01 (2013-07-15)
917
Interface
Key Signaling 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 SM-STATUS Channel Request Packet Channel Req Um Packet Control Acknowledgement (NB) Packet Control Ack (AB) Packet Cell Change Failure Packet Resource Request
Issue 01 (2013-07-15)
918
Interface
Key Signaling 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 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 Downlink RLC Data header
Issue 01 (2013-07-15)
919
N/A RRC Setup Failure RRC Setup Failure (Service-CS) RRC Setup Failure (Service-PS)
RRC Abnormal Release Overlong RRC Setup Delay (Nonservice) 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
HO Problem
Soft Handover Failure Hard Handover Failure Cell Update Failure Channel Handover Failure Migration Failure Inter-RAT Handover Failure PDP Activate Failure
Issue 01 (2013-07-15)
920
Doma in RANCS
Abnormal CauseClassificatio n Nonexception Setup Failure Abnormal Release Service Quality Problem
Abnormal Cause-Subclassification
RAN 13.0
RAN 14.0
N/A CS RAB Setup Failure CS RAB Abnormal Release 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) Overlong RAB Connection Delay (Alerting)(MOC) Overlong RAB Connection Delay (Connect Ack)(MOC)
ShortCall Problem
VP
N/A CS RAB Setup Failure CS RAB Abnormal Release Overlong RRC Setup Delay
Issue 01 (2013-07-15)
921
Doma in
Service Type
Abnormal CauseClassificatio n
Abnormal Cause-Subclassification Overlong RAB Connection Delay (MTC) Overlong RAB Connection Delay (MOC) Overlong RAB Connection Delay (Alerting)(MTC) Overlong RAB Connection Delay (Connect Ack)(MTC) Overlong RAB Connection Delay (Alerting)(MOC) Overlong RAB Connection Delay (Connect Ack)(MOC)
RAN 13.0
RAN 14.0
ShortCall Problem
SMS
N/A N/A PS RAB Setup Failure PS RAB Abnormal Release Overlow Average Downlink Throughput Overlow Average Uplink Throughput Average Downlink Transmission Rate Slow Average Uplink Transmission Rate Slow
Issue 01 (2013-07-15)
922
Doma in
Service Type
Abnormal CauseClassificatio n
Abnormal Cause-Subclassification DL Average Rate Slow(sufficient resources) DL Average Rate Slow (insufficient resources)
RAN 13.0
RAN 14.0
Delay Problem
Overlong RRC Setup Delay Overlong RAB Connection Delay (MTC) Overlong RAB Connection Delay (MOC)
Other RANMulti Multi Service Multi Service (CS Included) Multi Service(PS Only)
Issue 01 (2013-07-15)
923
ErrType Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure
ErrReason DL CE Congestion UL_DL CE Congestion UL CE Congestion DL CE Congestion UL_DL CE Congestion UL CE Congestion DL CE Congestion UL_DL CE Congestion UL Iub Band Congestion DL Iub Band Congestion UL_DL Iub Band Congestion UL Iub Band Congestion DL Iub Band Congestion UL_DL Iub Band Congestion DL Power Congestion Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure
Issue 01 (2013-07-15)
924
ErrType Iub Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Radio Resource Congestion Uu Interface Failure Uu Interface Failure
ErrReason Iub AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Overload Control SRB Reset TRB Reset
Issue 01 (2013-07-15)
925
ErrType Uu Interface Failure Uu Interface Failure Radio Resource Congestion Uu Interface Failure Uu Interface Failure Iu Relocation Failure Iu Relocation Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iub Interface Failure Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Iub Interface Failure Iub Interface Failure Iub Interface Failure
ErrReason SRB Reset TRB Reset Preempted User Due To Congestion Timer Expired Timer Expired Iu Relocation Preparation Failure Timer Relocation Preparation Expiry Iu Relocation Execution Timer Expiry Timer Expired Timer Expired Timer Expired Iu Relocation Preparation Iu Release Command Iu Relocation Execution Timer Expiry Iu Relocation Preparation Failure Timer Relocation Preparation Expiry 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 Iu Relocation Preparation Failure Target System Unsupport Iub Cell not Available DL CE Congestion UL CE Congestion UL CE Congestion DL CE Congestion Iub Control Plane Process Resources Overload Iub Hardware Failure Iub OAM Intervention Failure
Issue 01 (2013-07-15)
926
ErrType Iub Interface Failure Iub Interface Failure Uu Interface Failure Iur Interface Failure Iur Interface Failure Iub Interface Failure Iur Interface Failure Iur Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure
ErrReason Iub not Enough User Plane Process Resources Failure Iub not Enough User Plane Process Resources Failure Radio Link Permanent Failure Iur AAL2/AL Establishment Failure Iur RL Reconfiguration Commit Timeout Iur Radio Link Reconfiguration Cancel Iur RL Add/Setup Timeout Iur Control Plane Process Resources Overload Radio Link Permanent Failure UE Reestablishment Timer Expired Timer Expired Timer Expired Overlapped Cell Update Overlapped Cell Update Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Overlapped Cell Update Timer Expired Overlapped Cell Update Timer Expired Uu Configuration Unsupport
Issue 01 (2013-07-15)
927
ErrType Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure
ErrReason Uu Physical Channel Failure Uu Simultaneous Configuration Uu Compress Mode Runtime Tgpsi Error Uu Protocol Error Uu Protocol Error Uu Protocol Error Uu Protocol Error Uu Protocol 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 Physical CH Failure Uu Inter-RAT Change Failure Protocol Error Uu Inter-RAT Change Failure Unspecified UE Reestablishment
Abnormal Cause-Sub-classification
Net
RRC Setup Failure (Service) RRC Setup Failure (Non-service) Intra-RAT Outgoing Handover Failure Inter-RAT Outgoing Handover Failure Intra-RAT Incoming Handover Failure Inter-RAT Incoming Handover Failure
HO Failure
Delay Evaluati on
Delay Problem
Overlong RRC Setup Delay (Service) Overlong RRC Setup Delay (Non-service) Overlong Inter-RAT Outgoing Handover Delay Overlong Intra-RAT Outgoing Handover Delay Overlong Inter-RAT Incoming Handover Delay Overlong Intra-RAT Incoming Handover Delay
PS
Accessib ility Evaluati on Retainab ility Evaluati on Service Evaluati on for Delay
Setup Failure
Key Signaling
Procedure RRC Setup or Release Key Event RRC CONNECTION REESTABLISHMENT REQUEST RRC CONNECTION REJECT
Issue 01 (2013-07-15)
929
Procedure
Key Event RRC CONNECTION REQUEST RRC CONNECTION SETUP COMPLETE RRC CONNECTION 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
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 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
Issue 01 (2013-07-15)
930
Procedure
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)
The section describes the exception cause classification in the summary table. The section also lists the signaling procedure and the cause of procedure initiated. l l l l l Exception Cause Classification Exception Cause Field Description (SGSN/MME) Exception Cause Field Description (GGSN/SAE-GW) Signaling Procedure Cause of Procedure Initiated
Domin
Abnormal Sub-type Service Req Failure Service Req Overlong Delay Paging Failure Paging Overlong Delay Iu Release Failure RAB Release Failure PDP Act Failure PDP Act Overlong Delay PDP Sec Act Failure PDP Sec Act Overlong Delay PDP Mod Failure PDP Mod Overlong Delay PDP Deact Failure Rab Assignment Failure Rab Assignment Overlong Delay
Abnormal Paging Abnormal Iu Release Abnormal RAB Release Abnormal PDP Act
PDN GW Dedicated Bearer Act Failure PDN GW Dedicated Bearer Act Overlong Delay PDN GW Initiated Bearer Mod Failure PDN GW Initiated Bearer Mod Overlong Delay PDN GW Initiated Bearer Deact Failure NA Attach Failure Attach Overlong Delay Detach Failure Intra TAU Failure
Abnormal PDN GW Initiated Bearer Mod Abnormal PDN GW Initiated Bearer Deact Non-exception Abnormal Attach Abnormal Detach MME Procedure Abnormal TAU
Intra TAU Overlong Delay Inter TAU Failure Inter TAU Overlong Delay
Abnormal Handover
Issue 01 (2013-07-15)
932
Domin
Abnormal Type
Abnormal Sub-type Intra E-UTRAN Handover Overlong Delay Inter RAT Handover Failure Inter RAT Handover Overlong Delay
S1 Release Failure Service Req Failure Service Req Overlong Delay Paging Failure Paging Overlong Delay Interoperation Failure Interoperation Overlong Delay Dedicated Bearer Act Failure Dedicated Bearer Act Overlong Delay Bearer Mod Failure Bearer Mod Overlong Delay Bearer Deact Failure Bearer Resourece Mod Failure Bearer Resourece Mod Overlong Delay PDN Connectivity Failure
Abnormal Paging
Abnormal Interoperation Abnormal Dedicated Bearer Act Abnormal Bearer Mod Abnormal Bearer Deact Abnormal Bearer Resourece Mod
Abnormal PDN
Non-exception Abnormal Create PDP GGSN Procedure Abnormal Update PDP Abnormal Delete PDP Traffic Non-exception Abnormal Create Session SAE-GW Procedure Abnormal Delete Session Abnormal Create Bearer Abnormal Modify Bearer
NA NA NA NA NA NA NA NA NA NA
Issue 01 (2013-07-15)
933
Domin
Abnormal Type Abnormal Update Bearer Abnormal Delete Bearer Abnormal Release Access Bearers Abnormal Modify Bearer Command Abnormal Delete Bearer Command Abnormal Bearer Resource Command Abnormal Create Indirect Data Forwarding Tunnel Abnormal Delete Indirect Data Forwarding Tunnel Traffic
Abnormal Sub-type NA NA NA NA NA NA NA NA NA
Issue 01 (2013-07-15)
934
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The differentiated service does not allow the access of subscriber. The system does not allow the access of SIM subscribers to the 3G network. The system does not allow the access of 2G subscribers. The license resource item restricts the subscriber access. The system does not allow the access of a certain APN subscriber. The system does not allow the access of IMSI subscribers to a certain location area. GPRS service not allowed caused by MVNO limits or CAMEL subscribers not allowed. The system is being closed. The PLMN does not allow the access of subscribers. The system does not allow the access of a certain CAMEL subscriber. The system does not allow the access of subscribers when being relocated. The system does not allow the access of SIM subscribers to the 4G network. This cause value indicates that system congestion occurs. When the number of attach requests initiated by MSs/UEs subscribed with a specific APN exceeds the predefined threshold, the SGSN/MME rejects subsequent such requests with the cause value of "Congestion" and starts an MM backoff timer. Before this timer expires, the SGSN/MME rejects all such requests with the same cause value. The ZC does not allow the access of subscribers. The ARD does not allow the access of subscribers. Local PLMN does not allow users to access. HLR does not respond.
SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Issue 01 (2013-07-15)
935
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The authentication set cannot be obtained from the HLR. IMSI unknown MS has no subscription. This location area cannot be accessed by subscribers. The message returned by the HLR is incorrect. The HLR returns an unknown cause. The SCP has no response. SCP initiate detach CAMEL user The DNS server has no response. The response message returned by the DNS server is incorrect. The peer SGSN or MME has no response. The message returned from the peer SGSN indicates that the MS is already separated. The peer SGSN or MME does not have the MS information. The peer SGSN or MME returned incorrect IEs.
An inter-SGSN/MME process fails on the peer SGSN or MME. No PDP context is available. The signaling address of the peer SGSN is invalid. Undefined internal error CB operation failure This cause value indicates that the P-TMSI resource allocation fails.
Issue 01 (2013-07-15)
936
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The VLR has no response. No available VLR The message returned by the VLR does not carry the MS information. The message returned by the VLR indicates that the location area cannot to be accessed. The message returned by the VLR carries an unknown reason. Receiving error messages Gb interface error An Iu interface error occurs. SDB failure OM delete user The subscriber data are inconsistent, and subscribers were detached. time out of reachable timer The SM does not respond. The SM failed to respond. No response to the S1 message. The target eNodeB does not access the core network. The eNodeB canceled the HO process. The eNodeB failed to respond. The HSS does not respond.
Issue 01 (2013-07-15)
937
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The HSS returned an incorrect message. The UE's subscription information is not registered in the HSS. The UE's EPS subscription information is not registered in the HSS. A certain access type is restricted. The system does not allow the access of roaming subscribers. No required HSS is obtained. The HSS returned incorrect security data. The HSS failed to return security data. Incorrect APN Unknown PDP address or type Subscription data mismatch Context not found Last PDN connection not allowed Only IPv4 allowed Only IPv6 allowed Only single address allowed ESM message not received PDN connection not existing DNS resolution failure
Issue 01 (2013-07-15)
938
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause Message syntax error Invalid message format Unknown resolved IMSI MS detached MS paging without response
Service not supported Incorrect mandatory IE Missing mandatory IE Incorrect optional IE System failure Authentication failure Subscriber authentication failure
Dynamic addresses occupied Semantic error in TFT operation Syntactical error in packet filtering Semantic error in packet filtering Unknown APN returned by GGSN Unknown PDP address or PDP type TFT not activated in PDP context
Issue 01 (2013-07-15)
939
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Context not found Incorrect message format Invalid length Incorrect command IE Missing command IE Relocation failure PDN address type not supported UE paging without response Service denied Failure to page the UE Request rejected Unable to call UE in idle state Missing conditional IE Timeout of the network side This cause value indicates that multiple PDN connections are not allowed by the APN and accordingly fail. RAB assignment failure
Issue 01 (2013-07-15)
940
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause RAB assignment failure in the MME IPv6 not supported Wildcard activation rejected Access to VPLMN denied No MVNO license DPP activation restricted by CDRF No MIP license No PPP license No license for conversation PDP activation requests No license for secondary activation Secondary activation not supported by GTPCv0 Activation rejected by differentiated service This cause value indicates that system congestion occurs. When the number of 2G/3G PDP context activation requests initiated by MSs/ UEs subscribed with a specific APN exceeds the predefined threshold, the SGSN rejects subsequent such requests with the cause value of "Congestion" and starts an SM backoff timer. Before this timer expires, the SGSN rejects all such requests with the same cause value. PDP context number limited by the license Access to CDRF VPLMN denied Service barred due to operator-determined barring Access to HPLMN denied
SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Issue 01 (2013-07-15)
941
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause Resources insufficient Decoding failure Other unknown errors LLC or SNDCP failure Requested service unavailable temporarily Network failure Protocol error This cause value indicates that the UE request conflicts with procedures on the network. Operator determined barring GGSN rejection Unknown rejection cause NSAPI already used Regular deactivation. Reactivation required Context not found in secondary activation Only IPv4 allowed Only IPv6 allowed Only IPv4 or IPv6 allowed Invalid TI value
Issue 01 (2013-07-15)
942
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause Message timeout SGW and PGW rejection PTI already in use Multiple PDN connections not allowed for the same APN UE conflicting with the network side Invalid QCI Invalid PTI Protocol error or unknown error The GGSN fails to resolve the Create PDP context Response message. SGSN deact PDP context with APN restriction The IP address of the GGSN accessed in DHCP or MIP mode is not resolved. RPU-related failures Other APN-related errors The GTPU response times out. The GTPU board returns a failure cause. Sending a message to the GTPU board fails. CB resources are insufficient. SGSN reject PDP context request with APN restriction Undefined error
Issue 01 (2013-07-15)
943
Procedure Type SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure
Failure Cause Overlong Attach delays. Overlong Intra SGSN RAU delays. Overlong Inter SGSN RAU delays. Overlong Relocation delays. Overlong System Change delays. Overlong Service Req delays. Overlong Paging delays. Overlong PDP Act delays. Overlong PDP Sec Act delays. Overlong PDP Mod delays. Overlong Attach delays. Overlong Intra TAU delays. Overlong Inter TAU delays. Overlong Intra E-UTRAN Handover delays. Overlong Inter RAT Handover delays. Overlong Service Req delays. Overlong Paging delays. Overlong Interoperation delays. Overlong Dedicated Bearer Act delays. Overlong Bearer Mod delays. Overlong Bearer Resource Mod delays. Overlong PDN Connectivity delays.
The Activate PDP Context Request message is successfully processed. The received GTP header is incorrect.
Issue 01 (2013-07-15)
944
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause When operations, such as handover and data check, are performed, the Update PDP Context Request message (GTP V0) is not processed. When operations, such as handover and data check, are performed, the Delete PDP Context Request message (GTP V0) is not processed. When operations, such as handover and data check, are performed, the Update PDP Context Request message (GTP V1) is not processed. When operations, such as handover and data check, are performed, the Delete PDP Context Request message (GTP V1) is not processed. The protocol type in the Create PDP Context message (GTP V0) is incorrect. When the Create PDP Context message (GTP V0) is preprocessed, the message is rejected if the License does not support IPv6 subscribers. When the Create PDP Context message (GTP V0) is preprocessed, ApnIndex cannot be found by using ApnName. The Create PDP Context Request message (GTP V0) fails to be processed because the actual APN information cannot be obtained from ApnIndex. When the Create PDP Context Request message (GTP V0) is preprocessed, the APN is locked. When the Create PDP Context Request message (GTP V0) is preprocessed, the SPU board is locked or the CPU is overloaded. The static IP address in the Create PDP Context Request message (GTP V0) is incorrect. The Create PDP Context Request message (GTP V0) fails because the static IP address is not matched; that is, the IP address contained in the list is not consistent with that carried in the message. When the Create PDP Context Request message (GTP V0) is preprocessed, the static IP address fails to be matched because the IP address belongs to the protected IP address segment. When the Create PDP Context Request message (GTP V0) is preprocessed, the operations of allocating the context space and establish the IMSI index fail The protocol type in the Create PDP Context message (GTP V1) is incorrect. When the Create PDP Context message (GTP V1) is preprocessed, ApnIndex cannot be found by using ApnName. The Create PDP Context message (GTP V1) is directly rejected if the License does not support IPv6 subscribers.
Issue 01 (2013-07-15)
945
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Issue 01 (2013-07-15)
Failure Cause The Create PDP Context message (GTP V1) fails to be processed if the IMSI and MSISDN of V1 subscribers are not matched. When the Create PDP Context message (GTP V1) is preprocessed, the judgment on static IP addresses is invalid. The IPv4 static IP address in the Create PDP Context message (GTP V1) does not belong to the address segment configured by the APN. The IPv4 static IP address in the Create PDP Context message (GTP V1) is belongs to the protected address segment. The Create PDP Context message (GTP V1) fails to be processed because the APN is locked. Messages are sent to other boards. The possible cause is that the SPU is locked; the CPU is overloaded. The second Create PDP Context message (GTP V1) fails to be processed because the context cannot be found. The second Create PDP Context message (GTP V1) fails to be processed because PPP, L2tp, IPv6, and MIP subscribers do not support the second activation. The second Create PDP Context message (GTP V1) fails to be processed because the APN is locked. The same NSAPI is carried in the second Create PDP Context message (GTP V1). The NSAPI activated in the second Create PDP Context message (GTP V1) is the same as that activated in a common message. The second Create PDP Context message (GTP V1) fails to be processed because the second activation is not allowed when the handover or data check is performing. The second Create PDP Context message (GTP V1) fails to be processed because GGSN cannot allocate a context. The second Create PDP Context message (GTP V1) fails to be processed because the NSAPI attribute is incorrect. The Create PDP Context Request message (GTP V0) fails to be processed because the retrieved IE cannot be saved in the context. The Create PDP Context Request message (GTP V0) fails to be processed because the QoS negotiation fails. The Create PDP Context Request message (GTP V0) fails to be processed because the data stream labels cannot be allocated. The Create PDP Context Request message (GTP V0) fails to be processed because the signaling path cannot be established.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 946
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause The Create PDP Context Request message (GTP V0) fails to be processed because the data path cannot be established. The Create PDP Context Request message (GTP V0) fails to be processed because the subscriber is not authorized. The Create PDP Context Request message (GTP V0) fails to be processed because the global and APN configurations do not allow the access of roaming subscribers. The Create PDP Context Request message (GTP V0) fails to be processed because the global and APN configurations do not allow the access of visiting subscribers. The Create PDP Context Request message (GTP V0) fails to be processed because the timer cannot be created. The Create PDP Context Request message (GTP V1) fails to be processed because the TFT is invalid. The Create PDP Context Request message (GTP V1) fails to be processed because contents in the message cannot be saved in the context. The Create PDP Context Request message (GTP V1) fails to be processed because the QoS negotiation fails. The Create PDP Context Request message (GTP V1) fails to be processed because the signaling path cannot be established. The Create PDP Context Request message (GTP V1) fails to be processed because the data path cannot be established. The Create PDP Context Request message (GTP V1) fails to be processed because the subscriber is not authorized. The Create PDP Context Request message (GTP V1) fails to be processed because the global and APN configurations do not allow the access of roaming subscribers. The Create PDP Context Request message (GTP V1) fails to be processed because the global and APN configurations do not allow the access of visiting subscribers. The Create PDP Context Request message (GTP V1) fails to be processed because the timer cannot be created. The second Create PDP Context Request message (GTP V1) fails to be processed because the TFT is invalid. The second Create PDP Context Request message (GTP V1) fails to be processed because the message does not carry a TFT and a context without a TFT exists.
Issue 01 (2013-07-15)
947
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause The second Create PDP Context Request message (GTP V1) fails to be processed because contents in the message cannot be saved in the context. The second Create PDP Context message (GTP V1) fails to be processed because the context cannot be found. The second Create PDP Context message (GTP V1) fails to be processed because the context RAI carried in this message is not consistent with that of the related context. The second Create PDP Context Request message (GTP V1) fails to be processed because the QoS negotiation fails. The second Create PDP Context Request message (GTP V1) fails to be processed because the signaling path cannot be established. The second Create PDP Context Request message (GTP V1) fails to be processed because the data path cannot be established. The second Create PDP Context Request message (GTP V1) fails to be processed because the timer cannot be created. It is the cause value of failed authentication sent from the Radius module. In the DHCP ACK message sent by the DHCP server, the returncode is failure. The filter number reaches the maximum number when the Create PDP Context Request message is successfully processed. Creating the NP list fails when the Create PDP Context Request message is successfully processed. When the Create PDP Context Request message is successfully processed, the corresponding response message fails to be sent. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN PDP is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN universal PDP is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the global PDP is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the global universal PDP is reached.
Issue 01 (2013-07-15)
948
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Issue 01 (2013-07-15)
Failure Cause When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN bandwidth is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN universal bandwidth is reached. The Update PDP Context Request message is successfully processed. The protocol type in the Update PDP Context Request message (GTP V0) is incorrect. The context carried in the Update PDP Context Request message (GTP V0) cannot be found. The Update PDP Context Request message (GTP V0) fails to be processed because the CPU is overloaded. Mandatory IEs are absent in the Update PDP Context Request message. The IMSI cannot be obtained from the Update PDP Context Request message (GTP V1) and the context cannot be located based on the TEID (C) + NSAPI. The IMSI is obtained from the Update PDP Context Request message (GTP V1), but the context cannot be located based on the TEID (C) + NSAPI. The IMSI in the Update PDP Context Request message (GTP V1) cannot be found because of the version change. The context in the Update PDP Context Request message (GTP V1) cannot be found after the IMSI is obtained because of the version change. The Update PDP Context Request message (GTP V1) fails to be processed because the CPU is overloaded. The Update PDP Context Request message (GTP V1) fails to be processed because the TFT carried in the message is invalid. The Update PDP Context Response message (GTP V1) is received, but the message format is incorrect. The V1 Update PDP Context Response message is received, but the corresponding request message cannot be found. After the Update PDP Context Response message (GTP V1) is received, the context fails to be found based on the index. The number of filters exceeds the limit after the Update PDP Context Request message is processed. IEs cannot be saved in the context when the Update PDP Context Request message (GTP V1) is processed.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 949
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause When the Update PDP Context Request message is processed and the GTP version is updated from V1 to V0, the data stream labels fail to be allocated. IEs cannot be saved in the context when the Update PDP Context Request message (GTP V0) is processed. Negotiating the QoS fails when the Update PDP Context Request message is processed. Updating the signaling path fails when the Update PDP Context Request message is processed. Updating the data path fails when the Update PDP Context Request message is processed. Updating a local subscriber to a roaming subscriber fails when the Update PDP Context Request message is processed. Updating the charging information fails when the Update PDP Context Request message is processed. The NP fails to update the context when the Update PDP Context Request message is processed. After the Update PDP Context Response message is received, the SGSN rejects the update originated by the GGSN. After the Update PDP Context Response message is received, the QoS version carried in the message is not supported. After the Update PDP Context Response message is received, the GTPU table fails to be sent to the NP. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN bandwidth is reached. The Deactivate PDP Context Request message is successful processed. The protocol type in the Delete PDP Context Request message (GTP V0) is incorrect. The context is not found in the Delete PDP Context Request message (GTP V0). After an V0 subscriber receives the Delete PDP Context Request message (GTP V1), a failure response is returned. An IE is absent in the Delete PDP Context Request message (GTP V1) or the message is invalid. The context to be deleted in the Delete PDP Context Request message (GTP V1) does not exist whereas the related context exists.
Issue 01 (2013-07-15)
950
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause When the Delete PDP Context Request message (GTP V1) does not carry TEARDOWN, no corresponding context can be found in the SDB context. The Delete PDP Context Request message (GTP V1) requests to delete the last context, but TEARDOWN is not carried in this message. The value of TEARDOWN carried in the Delete PDP Context Request message (GTP V1) is 0 and no corresponding context can be found in the SDB context. The Delete PDP Context Request message (GTP V1) requests to delete the last context, but the value of TEARDOWN in this message is 0. When the Delete PDP Context Response message (GTP V0) is received, the protocol type carried in the message is incorrect. Thus, an incorrect response message is received and the context cannot be found. When the Delete PDP Context Response message (GTP V0) is received, the protocol type carried in the message is incorrect. Thus, an incorrect response message is received. The Delete PDP Context Response message (GTP V0) fails to be processed because the context cannot be located. When the Delete PDP Context Response message (GTP V0) is received, the context fails to be converted to an pointer. The received Delete PDP Context Response message (GTP V0) is incorrect. When the Delete PDP Context Response message (GTP V0) is received, the corresponding request message cannot be found. The Delete PDP Context Response message (GTP V0) fails to be processed because the context cannot be found by using the index. The Create Session Request message is successfully processed. The Create Session Request fails to be processed because the UGW9811 is locked and does not allow the access from new subscribers. The Create Session Request message fails to be processed because the board is in smooth state after the active/standby switchover and does not allow the access from new subscribers. The Create Session Request message fails to be processed because obtaining product types fails based on a request IE. The Create Session Request message fails to be processed because obtaining APN IE from IEs contained in the message fails. The Create Session Request message fails to be processed because the PGW receives the message in a non-Attach scenario.
Issue 01 (2013-07-15)
951
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Create Session Request message fails to be processed because license resources are insufficient for the type of products. The Create Session Request message fails to be processed because the system traffic reaches license limitation and the access from new subscribers is not allowed. The Create Session Request message fails to be processed because the IP address of the peer NE is on the blacklist or is not on the whitelist. The Create Session Request message fails to be processed because obtaining the usage scenario of the message fails. The Create Session Request message fails to be processed because checking the validity of the message fails. The Create Session Request message fails to be processed because applying for a bearer context fails. The Create Session Request message fails to be processed because the board is locked. The Create Session Request fails to be processed because filter resources are insufficient. The Create Session Request message fails to be processed because creating a signaling path fails. The Create Session Request message fails to be processed because policy control implemented by the PCRF, AAA server, or the UGW9811 configuration fails. The Create Session Request message fails to be processed because the QCI type is incorrect during the QoS check performed during the interaction between UGW9811 and PCRF. The Create Session Request message fails to be processed because the SGW fails to forward the message to the PGW. The Create Session Request message fails to be processed because the peer NE fails to respond before the timeout. The Create Session Request message fails to be processed because the peer NE returns a rejection message. The Create Session Request message fails to be processed because the system fails to start charging. The Create Session Request message fails to be processed because an internal system error occurs during the processing and causes subscribers to fail to access the UGW9811. The Create Session Request message fails to be processed because the system fails to enable the content resolution function.
Issue 01 (2013-07-15)
952
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Create Session Request fails to be processed because license resources are insufficient and the access from subscribers is not allowed. The Create Session Request message fails to be processed because the system fails to start data forwarding. The Create Session Request message fails to be processed because initiating AAA authentication fails. The Create Session Request message fails to be processed because mapping the APN to in the request to the actual APN fails. The Create Session Request message fails to be processed because the access from roaming subscribers is not allowed after authentication. The Create Session Request message fails to be processed because the IP address obtained from the AAA server is incorrect. The Create Session Request message fails to be processed because userprofile fails to be obtained based on the user-profile name issued by the AAA server. The Create Session Request message fails to be processed because creating L2TP tunnel fails. The Create Session Request message fails to be processed because routing resources are insufficient which results in the failure of the access from subscribers. The Create Session Request message fails to be processed because the static IP address or IP address allocated by the AAA server is incorrect. The Create Session Request message fails to be processed because obtaining an IP address fails. The Create Session Request message fails to be processed because QoS control fails. The Create Session Request message fails to be processed because the message decode fails. The Create Session Request message fails to be processed because an internal system error occurs during the processing. The Modify Bearer Request message is successfully processed. 1. The Modify Bearer Request message fails to be processed because the board is in smooth state after the switchover and does not allow the access from subscribers. 2. No default bearer can be found. The Modify Bearer Request message fails to be processed because the address of the peer NE is on the blacklist or is not on the whitelist.
Issue 01 (2013-07-15)
953
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Modify Bearer Request message fails to be processed because non-PGW NEs receive a message that does not contain bearer information. The Modify Bearer Request message fails to be processed because the bearer contained in the message belongs to multiple PDN Connections. The Modify Bearer Request message fails to be processed because obtaining the product type fails. The Modify Bearer Request message fails to be processed because checking the validity of IEs contained in the message fails. The Modify Bearer Request message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message. The Modify Bearer Request message fails to be processed because subscribers are on the multi-service APN and they are not allowed to switch to Gptv2 subscribers. The Modify Bearer Request message fails to be processed because obtaining an APN fails. The Modify Bearer Request message fails to be processed because the an internal system error occurs in the UGW9811 during the processing. The Modify Bearer Request message fails to be processed because the interaction between the UGW9811 and the PCRF fails. The Modify Bearer Request message fails to be processed because the system fails to enable the content resolution function. The Modify Bearer Request message fails to be processed because the system fails to start charging. The Modify Bearer Request message fails to be processed because an internal system error occurs during the processing. The Modify Bearer Request message fails to be processed because filter resources are insufficient. The Modify Bearer Request fails to be processed because the SGW fails to forward the request message to the PGW. The Modify Bearer Request message fails to be processed because the peer NE fails to respond before the timeout. The Modify Bearer Request message fails to be processed because the peer NE returns a rejection message code. The Modify Bearer Request message fails to be processed because the system fails to start data forwarding. The Modify Bearer Request message fails to be processed because the message decode fails.
Issue 01 (2013-07-15)
954
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Issue 01 (2013-07-15)
Failure Cause
The Delete Session Request message is successfully processed. The Delete Session Request message fails to be processed because subscribers' bearer information cannot be found. The Delete Session Request message fails to be processed because NEs in the request message are invalid. The Delete Session Request message fails to be processed because no default bearers can be found. The Delete Session Request message fails to be processed because in the nonGUL handover scenario the GGSN receives the message. In the scenario of switching services from the SPGW to the PGW, the Delete Session Request fails to be processed because a response message fails to be sent. The Delete Session Request message fails to be processed because the system processes the message improperly. The Delete Session Request message fails to be processed because the SGW receives a failure response from the PGW. The Create Bearer Request message is successfully processed. The Create Bearer Request message fails to be processed because IEs in the message are incorrect. The Create Bearer Request message fails to be processed because the information about subscriber default bearers fails to be obtained. The Create Bearer Request message fails to be processed because the number of default bearers reaches the specifications and creating dedicated bearers fails. The Create Bearer Request message fails to be processed because the NE type is incorrect. The Create Bearer Request message fails to be processed because subscriber dedicated bearers fail to be created. The Create Bearer Request message fails to be processed because the PGWFQ-CSID fails to be processed. The Create Bearer Request message fails to be processed because the TFT fails to be processed. The Create Bearer Request message fails to be processed because applying for a memory to store PCO fails. The Create Bearer Request message fails to be processed because the PCO IE fails to be resolved.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 955
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Create Bearer Request message fails to be processed because the IMS signaling bearer fails to be queried. The Create Bearer Request message fails to be processed because roaming subscribers cannot use the extended QCI. The Create Bearer Request message fails to be processed because QoS control fails. The Create Bearer Request message fails to be processed because session control resources fail to be applied. The Create Bearer Request fails to be processed because filter resources are insufficient. The Create Bearer Request message fails to be processed because the signaling or data path fails to be created. The Create Bearer Request message fails to be processed because the system fails to start data forwarding. The message Create Bearer Request fails to be processed because the SGW fails to forward a request message to the MME. The Create Bearer Request message fails to be processed because peripheral NEs fail to respond before the timeout. The Create Bearer Request message fails to be processed because the peer NE returns a rejection message code. The Create Bearer Request message fails to be processed because the system fails to start charging. The Create Bearer Request message fails to be processed because an internal system error occurs during the processing. The Create Bearer Request message fails to be processed because the system fails to enable the content resolution function. The Create Bearer Request fails to be processed because license resources are insufficient and the access from subscribers is not allowed. The Create Bearer Request message fails to be processed because the message decode fails. The Create Bearer Request message fails to be processed because the system processes the message improperly. The UGW9811 actively initiates Create Bearer procedure, and the peer NE returns a success message code. The UGW9811 actively initiates Create Bearer procedure, but the peer NE returns a rejection message code.
Issue 01 (2013-07-15)
956
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause
The Update Bearer Request message is successfully processed. The Update Bearer Request message fails to be processed because the message contains incorrect IEs. 1. The Update Bearer Request message fails to be processed because the board is in smooth state after the switchover and does not allow the bearer update. 2. The bearer cannot be found based on the TEID in the message. The Update Bearer Request message fails to be processed because the bearer information fails to be obtained based on the EBI and LBI IEs in the message. The Update Bearer Request message fails to be processed because the product is not the SGW. The Update Bearer Request message fails to be processed because applying for a bearer context fails. The Update Bearer Request message fails to be processed because the PTI in the message is inconsistent with that in the default bearer. The Update Bearer Request message fails to be processed because the message fails to be forwarded to the MME. The Update Bearer Request message fails to be processed because the peer NE fails to respond before the timeout. The Update Bearer Request message fails to be processed because the peer NE returns a rejection message code. The Update Bearer Request message fails to be processed because the system fails to start charging. The Update Bearer Request message fails to be processed because an internal system error occurs during the processing. The Update Bearer Request message fails to be processed because filter resources are insufficient. The Update Bearer Request message fails to be processed because an internal system error occurs during the processing. The Update Bearer Request message fails to be processed because the system fails to start data forwarding. The Update Bearer Request message fails to be processed because the message decode fails. The UGW9811 initiates the Update Bearer procedure, and the peer NE returns a success message code. The UGW9811 initiates the Update Bearer procedure, but the peer NE returns a rejection message code.
Issue 01 (2013-07-15)
957
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause
The Delete Bearer Request message is successfully processed. The Delete Bearer Request message fails to be processed because IEs in the message are invalid. The Delete Bearer Request message fails to be processed because information about subscriber bearers fails to be found. The Delete Bearer Request message fails to be processed because subscriber bearers to be deleted fail to be found. The Delete Bearer Request message fails to be processed because no default bearers can be found. The Delete Bearer Request message fails to be processed because the NE type in the message is incorrect. The Delete Bearer Request message fails to be processed because an internal system error occurs and causes a failure in deleting subscriber bearers. The Delete Bearer Request message fails to be processed because the message decode fails. In a UGW9811-initiated Delete Bearer procedure, the peer NE sends a Delete Bearer Response message to the UGW9811. In a UGW9811-initiated Delete Bearer procedure, the peer NE sends a Delete Bearer Response message carrying a failure cause value to the UGW9811. The Release Access Bearers Request message is successfully processed. The Release Access Bearers Request message fails to be processed because no bearer information of the subscriber is found. The Release Access Bearers Request message fails to be processed. The Modify Bearer Command message is successfully processed. The Modify Bearer Command message fails to be processed because no bearer information of the subscriber is found. The Modify Bearer Command message fails to be processed because an IE in the message is invalid. The Modify Bearer Command message fails to be processed because no information about the default bearer of the subscriber is found. The Modify Bearer Command message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message.
Issue 01 (2013-07-15)
958
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Issue 01 (2013-07-15)
Failure Cause The Modify Bearer Command message fails to be processed because the Sequence Number IE ID is incorrect. The Modify Bearer Command message fails to be processed because the extended QCI cannot be used when the subscriber is in roaming state. The Modify Bearer Command message fails to be processed because peripheral NEs fail in processing the message. The Modify Bearer Command message fails to be processed because no response is received from peripheral NEs before timeout or peripheral NEs fails in processing the message, which causes the failure in updating bearers. The Modify Bearer Command message fails to be processed because the message decode fails. The Delete Bearer Command message is successfully processed. The Delete Bearer Command message fails to be processed because no bearer information of the subscriber is found. The Delete Bearer Command message fails to be processed because the Sequence Number IE ID is incorrect. The Delete Bearer Command message fails to be processed because an IE in the message is invalid. The Delete Bearer Command message fails to be processed because the EBI in the message is incorrect. The Delete Bearer Command message fails to be processed because the subscriber bearer is not established or has been updated on the NE. The Delete Bearer Command message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message. The Delete Bearer Command message fails to be processed because peripheral NEs fail in processing the message. The Delete Bearer Command message fails to be processed because no response is received from peripheral NEs before timeout or peripheral NEs fails in processing the message, which causes the failure in updating bearers. The Bearer Resource Command message is successfully processed. The Bearer Resource Command message fails to be processed because no bearer information of the subscriber is found. The Bearer Resource Command message fails to be processed because an IE in the message is invalid. The Bearer Resource Command message fails to be processed because the bearer of the subscriber is being deleted.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 959
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Bearer Resource Command message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message. The Bearer Resource Command message fails to be processed because the Fteid IE in the message is incorrect. The Bearer Resource Command message fails to be processed because the memory application fails after the PCO setting is saved. The Bearer Resource Command message fails to be processed because the parsing of the PCO IE fails. The Bearer Resource Command message fails to be processed because the total CBR of the subscriber bearer is greater than the maximum GBR configured for the APN. The Bearer Resource Command message fails to be processed because the previous Bearer Command message has not been processed. The Bearer Resource Command message fails to be processed because the Sequence Number IE ID is incorrect. The Bearer Resource Command message fails to be processed because no IMS signaling bearer is found. The Bearer Resource Command message fails to be processed because peripheral NEs fail in processing the message. The Bearer Resource Command message fails to be processed because no response is received from peripheral NEs before timeout or peripheral NEs fails in processing the message, which causes the failure in performing bearer operations. The Bearer Resource Command message fails to be processed because the message decode fails. The Create Indirect Data Forwarding Tunnel Request message is successfully processed. The Create Indirect Data Forwarding Tunnel Request message is successfully processed. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because an IE in the message is invalid. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because the NE type is neither SGW nor SPGW. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because no bearer is found for the operation. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because the message decode fails.
Issue 01 (2013-07-15)
960
Failure Cause The Delete Indirect Data Forwarding Tunnel Request message is successfully processed.
Signaling Procedure
Procedure Type SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN Procedure Name GPRS Attach Combined Attach MS Init GPRS Detach MS Init Combined Detach CN Init GPRS Detach CN Init Combined Deatch Implicit GPRS Detach Implicit Combined Detach RAN Init Iu Release CN Init Iu Release RAU(others) Intra RAU Intra Combined RAU Inter RAU Inter Combined RAU Periodic RAU Periodic Combined RAU Intra SRNS Relocation Inter SRNS Relocation 3G to 2G System Change 2G to 3G System Change Service Req Paging MS Init PDP Act
Issue 01 (2013-07-15)
961
Procedure Type SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME
Procedure Name MS Init PDP Sec Act CN Init PDP Act MS Init PDP Deact CN Init PDP Deact MS Init PDP Mod CN Init PDP Mod RAN Init RAB Release CN Init RAB Release CN Init PDP Sec Act RAB Assignment PDN GW Dedicated Bearer Act PDN GW Initiated Bearer Mod PDN GW Initiated Bearer Deact Attach Intra USN Intra E-UTRAN TAU Inter USN Intra E-UTRAN TAU eNodeB S1 Release CN Init S1 Release Ms Init Detach CN Init Detach X2 HandOver Intra MME S1 HandOver Inter MME S1 HandOver Paging Service Req Intra USN GERAN to E-UTRAN Inter RAT TAU Intra USN UTRAN to E-UTRAN Inter RAT TAU Intra USN UTRAN Iu mode to E-UTRAN Inter RAT handover Inter USN UTRAN Iu mode to E-UTRAN Inter RAT handover Inter USN GERAN/UTRAN to E-UTRAN TAU
Issue 01 (2013-07-15)
962
Procedure Type MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME GGSN GGSN GGSN GGSN SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW
Procedure Name MME to 3G SGSN combined hard handover and SRNS relocation procedure Intra USN E-UTRAN to GERAN Inter RAT RAU Intra USN E-UTRAN to UTRAN Inter RAT RAU Intra USN E-UTRAN to UTRAN Iu mode Inter RAT handover Inter USN E-UTRAN to UTRAN Iu mode Inter RAT handover Inter USN E-UTRAN to GERAN/UTRAN Inter RAT RAU 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure Dedicated Bearer Act PDN GW Initiated Bearer Mod with Bearer QoS Update HSS Initiated Subscribed QoS Mod PDN GW Initiated Bearer Mod Without Bearer QoS Update PDN GW Initiated Bearer Deact MME Initiated Dedicated Bearer Deact Bearer Resource Mod PDN Connectivity PDN Disconnection Create PDP Update PDP Delete PDP Traffic Create Session Modify Bearer Delete Session Create Bearer Update Bearer Delete Bearer Release Access Bearers Modify Bearer Command Delete Bearer Command
Issue 01 (2013-07-15)
963
Procedure Name Bearer Resource Command Create Indirect Data Forwarding Tunnel Delete Indirect Data Forwarding Tunnel Traffic
Issue 01 (2013-07-15)
964
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
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 CHR_PROC_INIT_CAUSE_SGSN_DEACT_V1_GGSN_ERR_IN D CHR_PROC_INIT_CAUSE_SGSN_DEACT_V0_SGSN_ERR_IN D CHR_PROC_INIT_CAUSE_SGSN_DEACT_V1_SGSN_ERR_IN D CHR_PROC_INIT_CAUSE_SDB
Issue 01 (2013-07-15)
965
Cause
Procedure initiated by the GGSN Procedure initiated by the DNS Procedure initiated by the MSC Procedure initiated by the EIR Procedure initiated by the SCP Procedure initiated by the BSS Procedure initiated by the RNC
Issue 01 (2013-07-15)
966
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 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
Issue 01 (2013-07-15)
967
4
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. 4.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. 4.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, configuration data, and engineering parameter data. This helps you resolve network quality problems due to redundant neighboring cells, missing neighboring cells, or incorrect priorities. 4.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, and engineering parameter data. This helps you resolve network quality problems due to redundant or missing neighboring GSM cells. 4.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. 4.5 UMTS Pilot Pollution Analysis
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 968
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. 4.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. 4.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. 4.8 UMTS 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.9 UMTS 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.10 VIP Analysis By monitoring the indicators related to the quality of service of VIP subscribers, the Nastar helps you identify and solve the network problems that may cause VIP complaints so that the service quality of VIP subscribers is ensured and the satisfaction of VIP subscribers is improved.This function can be used to quickly locate and resolve problems. Normally there is no way to avoid that some user data such as International Mobile Subscriber Identity (IMSI) will be used during the troubleshooting. However, this function provides an anonymous data processing method. You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected. 4.11 Complaint Analysis Support After receiving a subscriber complaint, the Nastar can quickly searches for all call records of the complaint subscriber in a problem cell based on the known problem cell and International Mobile Subscriber Identity (IMSI) of the complaint subscriber, MSISDN number, or peer MSISDN of the complaint subscriber. Through the analysis of causes of exceptions such as access failure, handover failure, and abnormal call drop, the Nastar helps you locate and solve complaint problems.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
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 969
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.
Issue 01 (2013-07-15)
970
Function Description
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. Figure 4-1 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-1.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
971
Table 4-1 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
Issue 01 (2013-07-15)
972
So urc e M2 000
Purpose
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue a data query comma nd Return data query results Issue a task executio n comma nd
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
Issue 01 (2013-07-15)
973
So urc e eS AU
Purpose
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Check that the user has the rights to create a UMTS coverage analysis task upon login.
Prerequisite
UMTS configuration data has been imported to the Nastar Database. For details, see 4.1.2 Preparations for UMTS Coverage Analysis.
Procedure
Figure 4-2 shows the analysis process.
Issue 01 (2013-07-15)
975
Issue 01 (2013-07-15)
976
Table 4-2 Process of UMTS Coverage Analysis N Step o . ( 1 ) Check the integrity of the UMTS coverage analysis data Description Details
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS coverage analysis data. 2. Specify the query period. 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
( 2 )
Navigation path: Choose Maintenance > Data Subscription Management 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 01 (2013-07-15)
977
Description
Details
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the 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.
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS coverage analysis data. 2. Specify the query period. 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 the analysis data does not exist, contact Huawei technical support.
Issue 01 (2013-07-15)
978
Description
Details
Navigation path: In the Analysis Task Management window, choose Theme Function > Basic Network Optimization > UMTS Coverage Analysis. 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 )
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish 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 UMTS Coverage Analysis Task dialog box, view the analysis results. For details about the dialog box, see 4.1.4 Interface Description: UMTS Coverage Analysis.
Issue 01 (2013-07-15)
979
Description
Details
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon in the toolbar. For details about the icon, see 4.1.4 Interface Description: UMTS Coverage Analysis. 2. Set the save path and format of the analysis report. 3. Click Save.
Parameter settings Parameter Parameters Setting Analysis KPI Description Set the data filter criteria. Nastar provides 30 default filter criteria. After the filter criteria is set, only the filtered analysis data is displayed.
Issue 01 (2013-07-15)
980
Parameter Numbers
Description 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.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Main Window
UMTS coverage analysis results are displayed in 2-dimension/3-dimension windows or lists. For details, see Figure 4-3, Figure 4-4, or Figure 4-5.
Issue 01 (2013-07-15)
981
N o. 1
Description Two buttons are provided: l 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.
Issue 01 (2013-07-15)
982
N o. 2
Description 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:***.
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 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.
Issue 01 (2013-07-15)
983
No. 4
Description 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.
Issue 01 (2013-07-15)
984
No. 6
Description Displays the statistics of the KPIs of all services in the 2-dimension window. For details about the parameters, see 4.1.5 Parameters for Viewing UMTS Coverage Analysis Results.
Issue 01 (2013-07-15)
985
Parameter
Parameter Service Type Range AMR, VP, BE, AMR+BE, Other Unit N/A Description Indicates the service type for coverage analysis. The coverage analysis involves the following types of services: AMR, VP, BE, AMR+BE, and Other. Indicates the total number of TP MRs of the selected cell by service type. Indicates the total number of Ec/No MRs of the selected cell by service type. Indicates the total number of DL BLER MRs of the selected cell by service type. Indicates the total number of UE TX Power MRs of the selected cell by service type. Indicates the average TP of the selected cell by service type in the selected time segment. Supported NE Version BSC6900 V900R013C00 or later version
Total Number of TP Measurement Reports Total Number of ECNO Measurement Reports Total Number of DL BLER Measurement Reports
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
Average TP
N/A
N/A
Issue 01 (2013-07-15)
986
Range [-115,-25]
Unit dBm
Description Indicates the average RSCP of the selected cell by service type in the selected time segment. Indicates the average Ec/No of the selected cell by service type in the selected time segment. Indicates the average DL BLER of the selected cell by service type in the selected time segment. Indicates the average UE TX POWER of the selected cell by service type in the selected time segment.
Average ECNO
[-24,0]
dB
Average DL BLER(%)
[0,100]
Average UE TX POWER
[-50,33]
dBm
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.
Function Description
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.
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. l
Issue 01 (2013-07-15)
The algorithms for checking the missing neighboring cells are as follows:
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 988
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. l 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. Figure 4-6 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-3.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
989
Table 4-3 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd Forward the MML comma nd Upload raw data So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
M2 000
BSC/ RNC
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue 01 (2013-07-15)
990
Proced ure Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
Purpose
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Issue 01 (2013-07-15)
991
Table 4-4 Network changes and their impacts Network Change Addition or deletion of base stations Changes in antenna data such as the changes of the azimuth, tilt angle, and height Changes in handover relationships and parameters Changes in the RNC topology or other NE topologies Impact Affects the cell handover and network coverage. In this case, the analysis result cannot correctly reflect the current network status. Results in the changes in the cell coverage and network interference.
Affects the statistical results during the period of collecting and optimizing the neighboring relationship data.
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.
To ensure the validity of the configuration data, you are advised to analyze the configuration data on a per day basis.
Engineering Parameters 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 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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 993
Map File (Optional) The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map. You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
Prerequisite
UMTS configuration data and UMTS engineering parameters have been imported to the Nastar Database. For details, see 4.2.2 Preparations for UMTS Intra-Frequency Neighboring Cell Analysis.
Procedure
Figure 4-7 shows the analysis process.
Issue 01 (2013-07-15)
994
Issue 01 (2013-07-15)
995
Table 4-5 Process of UMTS intra-frequency neighboring cell analysis N Step o . ( 1 ) Check the integrity of the UMTS intrafrequency neighborin g cell analysis data Description Details
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Intra-Frequency Neighboring Cell Analysis Data. 2. Specify the query period. 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
( 2 )
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the UMTS tab. 2. Select the NEs in the navigation tree. 3. On the Basic Subscription Settings tab page, 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 01 (2013-07-15)
996
N Step o . Subscribe to the UMTS intrafrequency neighborin g cell analysis data (applicatio n) Check the integrity of the UMTS intrafrequency neighborin g cell analysis data
Description
Details
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, 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. Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Intra-Frequency Neighboring Cell Analysis Data. 2. Specify the query period. 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 the analysis data does not exist, contact Huawei technical support. 2.6 Checking the Integrity of Analysis Data
( 3 )
Navigation path: In the Analysis Task Management window, choose Theme Function > Basic Network Optimization > UMTS IntraFrequency Neighboring Cell Analysis Task in the navigation tree. Procedure: 1. Double-click UMTS Intra-Frequency Neighboring Cell Analysis Task. 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 neighboring cell parameters, 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.
Issue 01 (2013-07-15)
997
Description
Details
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish 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 UMTS Intra-Frequency Neighboring Cell Analysis window, view the UMTS intrafrequency neighboring cell analysis results. For details about the window, see Parameters for Viewing UMTS Intra-frequency Neighboring Cell Analysis Results. Navigation path: In the Analysis Task Management window, select a UMTS intrafrequency neighboring cell analysis task whose state is Finish, and select the result of the task in the Task Result area. Procedure: 1. Right-click the result of the task, and choose UMTS Possible Neighboring Cell Analysis from the shortcut menu. 2. In the UMTS Possible Neighboring Cell Analysis window, view the possible neighboring cell analysis results. For details about the window, see Interface Description: UMTS Intra-Frequency Possible Neighboring Cell Analysis.
( 5 )
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure 1. Click the export icon in the toolbar. For details about the icon, see Interface Description: UMTS Intra-Frequency Neighboring Cell Analysis. 2. Set the save path and format of the analysis report. 3. Click Finish.
Issue 01 (2013-07-15)
998
Description 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 The name is unique and case-sensitive and cannot be empty. l Task Name must be named in Chinese or English. Otherwise, the function of distributing analysis results by emails is unavailable.
Type of an analysis task to be created. Description of the task. Value range: The name contains a maximum of 200 characters.
Parameter settings Parameter Number of Configured Neighboring Cells Description Indicates the number of neighboring cells that you are recommended to configure. It can be any integer ranging from 0 to 31. The default value is 30.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Issue 01 (2013-07-15)
999
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 4-8. Figure 4-8 UMTS Intra-Frequency Neighboring Cell Analysis Task Interface
Issue 01 (2013-07-15)
1000
N o. 1
Description Three buttons are provided: 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.
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. 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 the table in the descending order. column header to display
Lists all neighboring UMTS cells of the dominant cells in the cell list. The background of undefined neighboring cells is gray. 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 01 (2013-07-15)
1001
N o. 4
Description 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 on the upper left of the Nastar client, the map interface (Geographic Observation) is displayed. The Figure 4-9 shows this interface. Figure 4-9 Map interface for UMTS Intra-Frequency neighboring cell analysis results
Issue 01 (2013-07-15)
1002
No. 1
Description Displays all the buttons for performing basic operations on the map interface. For the meanings of these buttons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
Navigation tree
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. 4 Legend area This area is not displayed by default. It is displayed only after you click 5 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.
Main Window
The possible intra-frequency neighboring UMTS cell analysis results are displayed in two charts: summary of possible neighboring cell analysis results and possible neighboring cell confirmation list, as shown in Figure 4-10.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1003
N o. 1
Description
is used to export the summary of possible neighboring cell analysis results. Displays the summary of the information about the possible neighboring cells of all cells involved in the analysis task. You can press Ctrl+F to search information in the list. The Nastar provides the functions of filtering and sorting. Click the column header and choose a filtering item from the drop-down box to display the table in a filtered way; click the the table in the descending order. column header to display
Issue 01 (2013-07-15)
1004
N o. 3
Description Lists all the possible neighboring cells of the cells in the summary of possible neighboring cell analysis results. l Button area: is used to add possible neighboring cells for a dominant cell. The operation procedure is as follows: Select a cell, and click this icon. The UMTS Possible Neighboring Cell Analysis dialog box is displayed. Select one or multiple possible neighboring cells from 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 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 (including RNC ID of the Selected Neighboring Cell, CI of Selected Neighboring Cell, Cell Name of Selected Neighboring, Distance(km), Relative Angle of Neighboring Cell (), Predicted Signal Strength(dBm), Get from Config Data, Number of Neighboring Cell Laps) of the dominant cell are modified according to the information about the possible neighboring cell. If the Whether to Use check box of a possible neighboring cell is not selected, the related parameters will not be displayed on the left.
Issue 01 (2013-07-15)
Parameter Cell ID
Range [0,65535]
Unit N/A
Description Indicates the ID of a dominant cell. Indicates the primary scrambling code of a dominant cell. Indicates the downlink absolute radio frequency channel number (ARFCN) of the dominant cell. Indicates the number of MRs received by the dominant cell. Indicates the average ECNO of the dominant cell. Indicates the average Received Signal Code Power (RSCP) of the dominant cell. Indicates the total number of 1A1C events triggered by neighboring cells. Indicates the number of missing intrafrequency neighboring cells among the undefined neighboring cells of the dominant cell.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
P-SC
[0,511]
N/A
Downlink ARFCN
N/A
N/A
[0,+)
Number
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[-24.5,0]
dB
Average RSCP
[-116,0]
dBm
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1006
Range [0.00,100.00]
Unit %
Description 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%. Indicates the number of redundant intrafrequency neighboring cells among the defined neighboring cells of the dominant cell. Sum of the overall scores of all redundant neighboring cells of the current dominant cell/ Sum of the overall scores of all measured neighboring cells of the current dominant cell x 100%. Indicates the number of defined intrafrequency neighboring cells of the dominant cell.
[0,+)
Number
[0.00,100.00]
[0,31]
Number
Issue 01 (2013-07-15)
1007
Range N/A
Unit N/A
Description Indicates the service type of the current dominant cell, such as indoor site and outdoor site. Learning the service type of the current dominant cell helps prevent important neighboring cells from being mistakenly deleted.
0 to 65535
N/A
1 to 64 characters
N/A
Neighboring PSC
[0,511]
N/A
Issue 01 (2013-07-15)
1008
Range N/A
Unit N/A
Description 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). 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. Indicates the total score of each neighboring cell. The total score is calculated using the neighboring cell algorithm based on each measurement result.
User Modify
N/A
N/A
Total Score
N/A
N/A
Issue 01 (2013-07-15)
1009
Range N/A
Unit N/A
Description Indicates the recommended priority of a neighboring cell based on the total score of the neighboring cell. The higher the total score, the higher is the recommended priority. Indicates the average RSCP of a neighboring cell in all MRs containing the information about this neighboring cell. Indicates the average ECNO of a neighboring cell in all MRs containing the information about this neighboring cell. Indicates the average ECNO of the dominant cell in all MRs containing the current neighboring cell.
[-116,0]
dBm
[-24.5,0]
dB
[-24.5,0]
dB
Issue 01 (2013-07-15)
1010
Range [-116,0]
Unit dBm
Description Indicates the average RSCP of the best cell in all the measurement reports that contains the current neighboring cell. Indicates the number of MRs containing the current neighboring cell in the monitor set or detected set. Indicates the number of MRs containing the current neighboring cell in the active set. Indicates the number of 1A1C events triggered by the current neighboring cell. Indicates the number of 1D events triggered by the current neighboring cell. Indicates the distance between the dominant cell and the current neighboring cell.
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
Distance
[0,+)
km
Issue 01 (2013-07-15)
1011
Range N/A
Unit N/A
Description 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.
Parameters for Viewing UMTS Intra-Frequency Possible Neighboring Cell Analysis Results
This section describes the parameters for querying UMTS possible neighboring cell analysis results. You can refer to the description when querying UMTS possible neighboring cell analysis results.
[0,65535]
N/A
N/A
N/A
[0,511]
N/A
Issue 01 (2013-07-15)
1012
Range N/A
Unit N/A
Description Indicates the downlink ARFCNs of a neighboring UMTS cell. Indicates the primary scrambling code of a neighboring UMTS cell. Indicates the ID of the RNC that the selected possible neighboring cell belongs to. Indicates the cell identity of the selected possible neighboring cell. Indicates the name of the RNC that the selected possible neighboring cell belongs to. Indicates the distance between the dominant cell and the selected possible neighboring cell. Indicates the relative angle between the selected possible neighboring cell and the dominant cell.
[0,511]
N/A
[0,+)
N/A
[0,65535]
N/A
1 to 64 characters
N/A
Distance(km)
[0,+)
km
[0,360]
N/A
Issue 01 (2013-07-15)
1013
Range N/A
Unit dBm
Description Indicates the signal strength of the selected possible neighboring cell based on the dimensioning. Indicates whether the selected possible neighboring cell is obtained from the configuration data. 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. Indicates the number of possible neighboring cells in the possible neighboring cell pair.
Yes, No
N/A
2, 3, 9
N/A
[0,+)
Number
Issue 01 (2013-07-15)
1014
Range N/A
Unit N/A
Description Indicates the recommended priority of a serving cell based on the neighboring cell algorithm. The priority value is in inverse proportion to the priority. There is a high probability that a possible neighboring cell with a smaller priority value is configured as a neighboring cell for the serving cell. Indicates the number of MRs for neighboring cells in the monitor set and detected set. Indicates the number of 1A/ 1C events.
MR Number of Neighboring Cell in Monitor Set/Detective Set Total Number of 1A1C Events
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1015
Range 1 to 64 characters
Unit N/A
Description Indicates the name of a possible neighboring cell. Indicates the ID of the RNC that a possible neighboring cell belongs to. Indicates the cell identity of a possible neighboring cell. Indicates the distance between the dominant cell and the selected possible neighboring cell. Indicates the relative angle between the selected possible neighboring cell and the dominant cell. Indicates the signal strength of the selected possible neighboring cell based on the dimensioning.
RNC ID
[0,+)
N/A
CI
[0,65535]
N/A
Distance(km)
[0,+)
km
[0,360]
N/A
N/A
dBm
Issue 01 (2013-07-15)
1016
Range Yes, No
Unit N/A
Description Indicates whether the selected possible neighboring cell is obtained from the configuration data. 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.
2, 3, 9
N/A
Function Description
After you set the conditions for checking the redundant or missing neighboring cell configurations, the Nastar performs inter-RAT neighboring cell analysis for the selected cell. The analysis results are displayed 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 neighboring GSM cells. 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. Figure 4-11 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-6.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1018
Table 4-6 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
Issue 01 (2013-07-15)
1019
So urc e M2 000
Purpose
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue a data query comma nd Return data query results Issue a task executio n comma nd
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
Issue 01 (2013-07-15)
1020
So urc e eS AU
Purpose
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Issue 01 (2013-07-15)
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. l Check that the user has the rights to create a UMTS/GSM neighboring cell analysis task upon login.
Issue 01 (2013-07-15)
1022
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).
Prerequisite
UMTS configuration data and UMTS engineering parameters have been imported to the Nastar Database. For details, see 4.4.2 Preparations for UMTS Inter-Frequency Neighboring Cell Analysis.
Procedure
Figure 4-12 shows the analysis process. Figure 4-12 Analysis process
Issue 01 (2013-07-15)
1023
Table 4-7 Process of UMTS/GSM neighboring cell analysis N Step o . ( 1 ) Check the integrity of the UMTS/ GSM neighborin g cell analysis data Description Details
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS/GSM neighboring cell analysis data. 2. Specify the query period. 3. Select an NE. 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
( 2 )
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the UMTS tab. 2. Select an NE in the navigation tree. 3. On the Basic Subscription Settings tab page, click Set. 4. In the Basic Subscription Settings dialog box, set UMTS/GSM Neighboring Cell Analysis Data to ON. 5. Click Confirm. Verify that the function is successfully enabled in the Log Info area.
Issue 01 (2013-07-15)
1024
N Step o . Subscribe to the UMTS/ GSM neighborin g cell analysis data (applicatio n)
Description
Details
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, 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. Verify that the function is successfully enabled in the Log Info area. For details about the parameters, see Subscription Task Parameters.
Check the integrity of the UMTS/ GSM neighborin g cell analysis data
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS/GSM neighboring cell analysis data. 2. Specify the query period. 3. Select an NE. 4. Click Query. The system displays the existing status of the data in the right pane.
( 3 )
Navigation path: In the Analysis Task Management window, choose Theme Function > Basic Network Optimization > UMTS/GSM Neighboring Cell Analysis from the navigation tree. Procedure: 1. Double-click UMTS/GSM Neighboring Cell Analysis. 2. Set the task name and remarks. Click Next. 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.
Issue 01 (2013-07-15)
1025
Description
Details
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish 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 UMTS/GSM Neighboring Cell Analysis dialog box, view the UMTS/GSM neighboring cell analysis results. For details about the dialog box, see Interface Description: UMTS/GSM Neighboring Cell Analysis.
( 5 )
Navigation path: In the Analysis Task Management window, select an UMTS/GSM neighboring cell analysis task whose state is Finish, and select the result of the task in the Task Result area. Procedure: 1. Right-click the result of the task, and choose UMTS/GSM Possible Neighboring Analysis from the shortcut menu. 2. In the UMTS/GSM Possible Neighboring Cell Analysis dialog box, view the possible UMTS/ GSM neighboring cell analysis results. For details about the dialog box, see Interface Description: UMTS/GSM Possible Neighboring Cell Analysis.
( 6 )
Export the UMTS/ GSM neighborin g cell analysis report Export the possible UMTS/ GSM neighborin g cell analysis report
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon in the toolbar. 2. Set the save path and format of the analysis report. 3. Click Save. Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon in the toolbar. 2. Set the save path and format of the analysis report. 3. Click Save.
( 7 )
Issue 01 (2013-07-15)
1026
Parameter settings
Issue 01 (2013-07-15)
1027
Description Indicates the threshold of the neighboring cell sequence number. All the undefined neighboring cells whose sequence numbers are smaller than or equal to the value of this parameter are regarded as missing neighboring cells. All the defined neighboring cells whose sequence numbers are larger than the value of this parameter are regarded as redundant neighboring cells. This parameter can be set to any integer from 3 to 32. The default value is 26.
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.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Issue 01 (2013-07-15)
1028
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 4-13. Figure 4-13 UMTS/GSM Neighboring Cell Analysis Interface
Issue 01 (2013-07-15)
1029
N o. 1
Description Three buttons are provided: 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.
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. 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 the table in the descending order. column header to display
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 neighboring cell analysis algorithm, and provides operation suggestions. For details about the neighboring cell analysis algorithm, 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.
Issue 01 (2013-07-15)
1030
N o. 4
Description 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. 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 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.
Map Interface
on the upper left of the Nastar client, the map interface (Geographic After you click Observation) is displayed. The Figure 4-14 shows this interface. Figure 4-14 Map interface for UMTS/GSM neighboring cell analysis results
Issue 01 (2013-07-15)
1031
No. 1
Description Displays all the buttons for performing basic operations on the map interface. For the meanings of these buttons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
Navigation tree
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. 4 Legend area This area is not displayed by default. It is displayed only after you click 5 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.
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 4-15.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1032
N o. 1
Description
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. 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 the table in the descending order. column header to display
Issue 01 (2013-07-15)
1033
N o. 3
Description 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 procedure is as follows: 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.
Issue 01 (2013-07-15)
1034
Parameter Cell ID
Range [0,65535]
Unit N/A
Description Indicates the ID of a dominant cell. Indicates the primary scrambling code of a dominant cell. Indicates the downlink ARFCNs of a dominant cell. Indicates the total number of MRs received by each dominant cell. Indicates the number of redundant neighboring GSM cells of the current dominant cell. Indicates the sum of the integrated priority percentages of all redundant neighboring cells for the dominant cell. Indicates the number of missing neighboring GSM cells of the current dominant cell.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
P-SC
[0,511]
N/A
DownLink ARFCN
N/A
N/A
Number of MRs
[0,+)
N/A
[0,+)
N/A
[0.000,100.000]
N/A
[0,+)
N/A
Issue 01 (2013-07-15)
1035
Range [0.000,100.000]
Unit N/A
Description Indicates the sum of the integrated priority percentages of all missing neighboring cells for the dominant cell. Indicates the number of defined neighboring GSM cells of the dominant cell. Indicates the service type of the current dominant cell, such as indoor site and outdoor site. Learning the service type of the dominant cell helps prevent important neighboring cells from being mistakenly deleted.
[0,+)
N/A
N/A
N/A
Issue 01 (2013-07-15)
1036
Parameter LAC
Unit N/A
Description Indicates the location area code of a neighboring GSM cell. Indicates the cell identity of a neighboring GSM cell. Indicates the name of a defined or undefined neighboring GSM cell of the current dominant cell.
CI
[0,65535]
N/A
Cell Name
1 to 64 characters
N/A
Issue 01 (2013-07-15)
1037
Parameter BCCH
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel of a neighboring GSM cell. 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. 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, and GSM850 is belong to GSM900. DCS1800 and PCS1900 is belong to GSM1800.
Issue 01 (2013-07-15)
1038
Parameter BSIC
Range [0,77]
Unit N/A
Description Indicates the base station identity code of a neighboring GSM cell. BSIC=NCC*10 +BCC, NCC [0,7], BCC [0,7].
1 to 64 characters
N/A
Indicates whether the selected cell is the defined neighboring cell of the current dominant cell. Indicates the operation suggestions provided by the Nastar on a neighboring cell.
Suggested Operation
Defined Neighboring Cell(reserved), Defined Neighboring Cell (Redundant), Undefined Neighboring Cell(Missing) and Undefined Neighboring Cell(NonOperation). N/A
N/A
User Modify
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.
Issue 01 (2013-07-15)
1039
Range N/A
Unit N/A
Description Indicates the total score of each neighboring cell based on the measurement result according to the neighboring cell algorithm. Indicates the final sequence of priorities adjusted on the basis of suggested priorities. 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. Indicates the average receive signal strength of a neighboring GSM cell ranking No.1 in MRs. Indicates the number of MRs related to the current neighboring GSM cell.
Final Priority
N/A
N/A
Suggested Priority
N/A
N/A
N/A
dBm
[0,+)
N/A
Issue 01 (2013-07-15)
1040
Parameter Distance
Range [0,+)
Unit km
Description Indicates the distance between the current dominant cell and a neighboring GSM cell. Indicates the service type of a neighboring GSM cell, such as indoor site and outdoor site. Learning the service type of the neighboring GSM cell helps prevent important neighboring cells from being mistakenly deleted. Indicates the number of times a cell ranking No.1 in the neighboring cell list. Indicates the number of times a cell ranking No.2 in the neighboring cell list. Indicates the number of times a cell ranking No.3 in the neighboring cell list.
N/A
N/A
Number of Times A Neighboring Cell Ranking No.1 in MRs Number of Times A Neighboring Cell Ranking No.2 in MRs Number of Times A Neighboring Cell Ranking No.3 in MRs
[0,+)
N/A
[0,+)
N/A
[0,+)
N/A
Issue 01 (2013-07-15)
1041
Parameter Number of Times A Neighboring Cell Ranking No.4 in MRs Number of Times A Neighboring Cell Ranking No.5 in MRs Number of Times A Neighboring Cell Ranking No.6 in MRs Number of Times A Neighboring Cell Ranking No.7 in MRs Number of Times A Neighboring Cell Ranking No.8 in MRs
Range [0,+)
Unit N/A
Description Indicates the number of times a cell ranking No.4 in the neighboring cell list. Indicates the number of times a cell ranking No.5 in the neighboring cell list. Indicates the number of times a cell ranking No.6 in the neighboring cell list. Indicates the number of times a cell ranking No.7 in the neighboring cell list. Indicates the number of times a cell ranking No.8 in the neighboring cell list.
[0,+)
N/A
[0,+)
N/A
[0,+)
N/A
[0,+)
N/A
Issue 01 (2013-07-15)
1042
Cell ID
[0,65535]
N/A
ARFCN_DL
N/A
N/A
P-SC
[0,511]
N/A
Issue 01 (2013-07-15)
1043
Range [0,1023]
Unit N/A
Description Indicates the broadcast control channel of a neighboring GSM cell. 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. 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, and GSM850 is belong to GSM900. DCS1800 and PCS1900 is belong to GSM1800.
Issue 01 (2013-07-15)
1044
Range [0,77]
Unit N/A
Description Indicates the base station identity code of a neighboring GSM cell. BSIC=NCC*10 +BCC, NCC [0,7], BCC [0,7].
N/A
N/A
Indicates the name of the BSC that the selected possible neighboring GSM cell belongs to. Indicates the name of the selected possible neighboring GSM cell. Indicates the global ID of the selected possible neighboring GSM cell. MCC[000,999] MNC[00,99] LAC[1,65533], [65535] CI[0,65535]
1 to 64 characters
N/A
MCC-MNCLAC-CI
N/A
LAC
[1,65533], [65535]
N/A
Indicates the location area code of the selected possible neighboring GSM cell.
Issue 01 (2013-07-15)
1045
Parameter CI
Range [0,65535]
Unit N/A
Description Indicates the cell identity of the selected possible neighboring GSM cell. Indicates the distance from the dominant cell to the selected possible neighboring GSM cell. Indicates the relative angle between the selected possible neighboring GSM cell and the dominant cell. Indicates the signal strength of the selected possible neighboring GSM cell based on the dimensioning. Indicates whether the selected possible neighboring GSM cell is obtained from the configuration data.
Distance
[0,+)
km
[0,360]
N/A
N/A
dBm
Yes, No
N/A
Issue 01 (2013-07-15)
1046
Range 2,3,9
Unit N/A
Description Indicates the number of laps between the selected possible neighboring GSM cell and the dominant cell, that is, the number of cells between the selected possible neighboring GSM cell and the dominant cell. Indicates the number of possible neighboring cells in the possible neighboring GSM cell pair. Indicates the number of MRs of the current neighboring GSM cell. Indicates the total score of each neighboring cell based on the measurement result according to the neighboring cell algorithm.
Number of Possible Neighboring Cells in the Possible Neighboring Cell Pairs Number of Measurement Reports
[0,+)
N/A
[0,+)
N/A
Total Score
[0,+)
N/A
Issue 01 (2013-07-15)
1047
Issue 01 (2013-07-15)
1048
Parameter
Range
Unit
Supported NE Version
Cell Name
1 to 64 characters
N/A
Indicates the name of a possible neighboring GSM cell. Indicates the name of the BSC that a possible neighboring GSM cell belongs to. Indicates the global ID that a possible neighboring GSM cell belongs to. MCC[000,999] MNC[00,99] LAC[1,65533], [65535] CI[0,65535]
BSC
N/A
N/A
CGI
MCC-MNCLAC-CI
N/A
[1,65533], [65535]
N/A
Indicates the location area code of a possible neighboring GSM cell. Indicates the cell identity of a possible neighboring GSM cell. Indicates the distance between the dominant cell and a possible neighboring GSM cell.
Neighboring Cell CI
[0,65535]
N/A
Distance
[0,+)
km
Issue 01 (2013-07-15)
1049
Range [0,360]
Unit N/A
Description Indicates the relative angle between the dominant cell and a possible neighboring GSM cell. Indicates the signal strength of a possible neighboring GSM cell based on the dimensioning. Indicates whether the possible neighboring GSM cell is obtained from the configuration data. Indicates the number of laps between the dominant cell and a possible neighboring GSM cell, that is, the number of cells between the dominant cell and a possible neighboring GSM cell.
N/A
N/A
N/A
N/A
2,3,9
N/A
Issue 01 (2013-07-15)
1050
Function Description
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. 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.
Issue 01 (2013-07-15)
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. Figure 4-16 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-8.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1052
Table 4-8 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd Forward the MML comma nd Upload raw data So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
M2 000
BSC/ RNC
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue 01 (2013-07-15)
1053
Proced ure Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
Purpose
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Issue 01 (2013-07-15)
1054
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. Map Files (Optional) The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map. You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
Prerequisites
UMTS configuration data and UMTS engineering parameters have been imported to the Nastar Database. For details, see 4.4.2 Preparations for UMTS Inter-Frequency Neighboring Cell Analysis.
Procedure
Figure 4-17 shows the analysis process.
Issue 01 (2013-07-15)
1056
Issue 01 (2013-07-15)
1057
Table 4-9 Description about the UMTS inter-frequency neighboring cell analysis flowchart N Procedure o . ( 1 ) Check data integrity related to UMTS interfrequency neighborin g cell analysis Description Reference
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Inter-Frequency Neighboring Cell Analysis Data. 2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
( 2 )
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the UMTS tab. 2. In the left navigation tree, choose NEs to be configured. 3. On the Basic Subscription Settings tab page, click Set. 4. In the Basic Subscription Settings dialog box, 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 01 (2013-07-15)
1058
N Procedure o . Subscribe to application data related to UMTS interfrequency neighborin g cell analysis.
Description
Reference
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, 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. For details about parameters, see Subscription Task Parameters. 5. Click Confirm. Verify that basic data subscription is successfully enabled by viewing information displayed in the Log Info area.
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Inter-Frequency Neighboring Cell Analysis Data. 2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
1059
Description
Reference
Navigation path: In the left navigation tree of the Analysis Task Management window, choose Theme Function > Basic Network Optimization > UMTS Inter-Frequency Neighboring Cell Analysis. Procedure: 1. Double-click UMTS Inter-Frequency Neighboring Cell Analysis. 2. Set the task name and task remarks. Then, click Next. 3. On the Select NE(s) tab page, select the NEs to be 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. For details about parameters, see Analysis Task Parameters.
( 4 )
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click the analysis result of a task. 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 4.4.4 Interface Description: UMTS Inter-Frequency Neighboring Cell Analysis.
Issue 01 (2013-07-15)
1060
Description
Reference
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. Procedure: 1. Right-click an undefined neighboring cell and choose View Possible Neighboring Analysis from the shortcut menu. 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 4.4.4 Interface Description: UMTS Inter-Frequency Neighboring Cell Analysis.
( 6 )
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon in the toolbar. For details about the icon, see 4.4.4 Interface Description: UMTS Inter-Frequency Neighboring Cell Analysis. 2. Set the format and save path for the file to be exported. 3. Click Save.
Issue 01 (2013-07-15)
1061
Description 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.
Parameter Information Parameter Number of Configured Neighboring Cells Description Specifies the number of neighboring cells configured on a UARFCN. The value is an integer ranging from 0 to 32. The default value is 20.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time.
Issue 01 (2013-07-15)
1062
Parameter Delay
Description 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. The value of this parameter must not precede the end time of Date.
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 4-18. Figure 4-18 Result window of UMTS inter-frequency neighboring cell analysis
Issue 01 (2013-07-15)
1063
N o. 1
Description Provides two buttons for entries of two function as follows: l 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. 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 the table in the descending order. column header to display
Displays all UMTS inter-frequency neighboring cells of the selected dominant cells in area 2. The background of undefined neighboring cells is gray. 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 neighboring cell analysis algorithm, and provides operation suggestions. For details about the neighboring cell analysis algorithm, 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.
Issue 01 (2013-07-15)
1064
N o. 4
Description 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. 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 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 on the upper left of the Nastar client, the map interface (Geographic Observation) is displayed. The Figure 4-19 shows this interface. Figure 4-19 Map interface for UMTS Inter-Frequency neighboring cell analysis results
Issue 01 (2013-07-15)
1065
No. 1
Description Displays all the buttons for performing basic operations on the map interface. For the meanings of these buttons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
Navigation tree
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. 4 Legend area This area is not displayed by default. It is displayed only after you click 5 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.
4.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 neighboring cell analysis results.
Issue 01 (2013-07-15)
1066
Parameter Cell ID
Range [0,65535]
Unit N/A
Description Indicates the ID of a dominant cell. Indicates the primary scrambling code of a dominant cell. Indicates the downlink absolute radio frequency channel number (ARFCN) of the dominant cell. Indicates the number of MRs received by the dominant cell. Indicates the number of interfrequency neighboring cells that are configured for the test cell. Indicates the number of missing intrafrequency neighboring cells among the undefined neighboring cells of the dominant cell.
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
P-SC
[0,511]
N/A
Downlink ARFCN
N/A
N/A
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1067
Range [0.000,100.000]
Unit %
Description 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%. Indicates the number of redundant intrafrequency neighboring cells among the defined neighboring cells of the dominant cell. Sum of the overall scores of all redundant neighboring cells of the current dominant cell/ Sum of the overall scores of all measured neighboring cells of the current dominant cell x 100%.
[0,+)
Number
[0.000,100.000]
Issue 01 (2013-07-15)
1068
Range N/A
Unit N/A
Description Indicates the service type of the current dominant cell, such as indoor site and outdoor site. Learning the service type of the current dominant cell helps prevent important neighboring cells from being mistakenly deleted.
0 to 65535
N/A
1 to 64 characters
N/A
Neighboring PSC
[0,511]
N/A
Issue 01 (2013-07-15)
1069
Range N/A
Unit N/A
Description Indicates the downlink absolute radio frequency channel number (ARFCN) of a neighboring cell. Indicates the type of a neighboring cell. The options are Defined Neighboring Cell (reserved), Defined Neighboring Cell (redundant), Undefined Neighboring Cell (missing), and Undefined Neighboring Cell (nonoperation). 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.
Suggested Operation
N/A
N/A
User Modify
N/A
N/A
Issue 01 (2013-07-15)
1070
Range N/A
Unit N/A
Description If this option is selected, you are advised to perform modification according to Neighboring Cell Type. Otherwise, no user operation is recommended. Indicates the total score of each neighboring cell. The total score is calculated using the neighboring cell algorithm based on each measurement result. Indicates the average RSCP of a neighboring cell in all MRs containing the information about this neighboring cell. Indicates the average ECNO of the dominant cell in all MRs containing the current neighboring cell. Indicates the number of interfrequency MRs of the neighboring cell.
Recommended Priority
N/A
N/A
[-115,-25]
dBm
[-24,0]
dB
[0,+)
Number
Issue 01 (2013-07-15)
1071
Parameter Distance
Range [0,+)
Unit km
Description Indicates the distance between the dominant cell and the current neighboring cell. Indicates the service type of a neighboring GSM cell, such as indoor site and outdoor site. Learning the service type of the neighboring GSM cell helps prevent important neighboring cells from being mistakenly deleted. 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. Accumulated number of times the neighboring cell ranking No. 1 in interfrequency MRs.
N/A
N/A
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1072
Parameter Number of Times A Neighboring Cell Ranking No.3 in MRs Number of Times A Neighboring Cell Ranking No.4 in MRs Number of Times A Neighboring Cell Ranking No.5 in MRs Number of Neighboring Cell Ranking No.6 to 12 in MRs
Range [0,+)
Unit Number
Description Accumulated number of times the neighboring cell ranking No. 2 in interfrequency MRs. Accumulated number of times the neighboring cell ranking No. 3 in interfrequency MRs. Accumulated number of times the neighboring cell ranking No. 4 in interfrequency MRs. Accumulated number of times the neighboring cell ranking No. 5 in interfrequency MRs.
[0,+)
Number
[0,+)
Number
[0,+)
Number
RNC ID
[0,+)
N/A
Issue 01 (2013-07-15)
1073
Parameter CI
Range [0,65535]
Unit N/A
Description Indicates the cell identity of a possible neighboring cell. Indicates the name of a possible neighboring cell. Indicates the distance between the dominant cell and the selected possible neighboring cell. Indicates the relative angle between the selected possible neighboring cell and the dominant cell. Indicates the signal strength of the selected possible neighboring cell based on the dimensioning. Indicates whether the selected possible neighboring cell is obtained from the configuration data.
Cell Name
1 to 64 characters
N/A
Distance
[0,+)
N/A
[0,360]
N/A
dBm
Yes, No
N/A
Issue 01 (2013-07-15)
1074
Range [-10,50]
Unit dBm
Description Indicates transmission power of the primary CPICH in the selected possible neighboring cell. It is obtained from the configuration data. If you cannot obtain the parameter value from the configuration data, use the default value 40 dBm.
2, 3, 9
N/A
Function Description
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:
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1075
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. 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.
l l
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. Figure 4-20 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-10.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1076
Table 4-10 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
Issue 01 (2013-07-15)
1077
So urc e M2 000
Purpose
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue a data query comma nd Return data query results Issue a task executio n comma nd
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
Issue 01 (2013-07-15)
1078
So urc e eS AU
Purpose
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Check that the login user has the rights to create a UMTS pilot pollution analysis task.
Prerequisites
The UMTS configuration data and engineering parameters have been imported into the Nastar database. For details, see 4.5.2 Preparations for UMTS Pilot Pollution Analysis.
Procedure
Figure 4-21 shows the analysis process. Figure 4-21 Analysis process
Issue 01 (2013-07-15)
1081
Table 4-11 Description of UMTS pilot pollution analysis process No. (1) Proced ure Check the integrit y of UMTS pilot pollutio n analysis data Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Pilot Pollution Analysis Data. 2. Specify the time period. 3. Select the desired 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
(2)
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the UMTS tab. 2. In the navigation tree, select the desired NEs. 3. On the Basic Subscription Settings tab page, click Set. 4. In the Basic Subscription Settings dialog box, set the data source switch of Pilot Pollution Analysis Data to ON. By default, the data source switch is set to No Modification. 5. Click Confirm. Check that the data source switch is open based on the information in the Log Info area.
Issue 01 (2013-07-15)
1082
No.
Description Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the UMTS tab. 2. In the navigation tree, select the desired NEs. 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.
Reference
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Pilot Pollution Analysis Data. 2. Specify the time period. 3. Select the desired 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
1083
No. (3)
Description Navigation path: In the navigation tree of the Analysis Task Management window, choose Theme Function > Basic Network Optimization > UMTS Pilot Pollution Analysis. Procedure: 1. Double-click UMTS Pilot Pollution Analysis. 2. Specify the task name and remarks. Then, click Next. 3. On the Select NE(s) tab page, select the 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)
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Right-click the result record and choose View Analysis Result from the shortcut menu. 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 4.5.4 Interface Description: UMTS Pilot Pollution Analysis.
Issue 01 (2013-07-15)
1084
Issue 01 (2013-07-15)
1085
Parameter Date
Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Portal
Use either of the following methods to open the interface that displays UMTS pilot pollution analysis results: l l Select an executed UMTS pilot pollution analysis task and double-click a result record in the Task Result area. 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. l 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. , the interface switches to displaying the polluter cell overview table After you click 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 4-22 shows this interface.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1086
No. 1
Description Provides the function of switching the information in Area 2 and 3. After you click the switching button, Area 3 will display the polluter cell overview table and Area 2 will display the polluted cell details table. For details, see Interface 2.
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 column header to resort this table. 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.
Issue 01 (2013-07-15)
1087
No. 3
Description 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 column header and choose a filtering item from the drop-down box to display the table in a filtered way. l Click the column header to resort this table. 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 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 4-23 shows this interface. Figure 4-23 Interface 2 for UMTS pilot pollution analysis results
Issue 01 (2013-07-15)
1088
No. 4
Description 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. You can 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 column header to resort this table. 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 polluter 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. You can 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 column header to resort this table. 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 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 4-24 shows this interface. Figure 4-24 Map interface for UMTS pilot pollution analysis results
Issue 01 (2013-07-15)
1089
No. 1
Description Displays all the buttons for performing basic operations on the map interface. For the meanings of these buttons, see 2.2.3 Interface Description: Geographic Observation Results. Site Layer: When UMTS is selected, the information of UMTS sites is displayed in Area 3. When UMTS is cleared or other RAT type is selected, the information of UMTS sites is not displayed in Area 3. The site information can be displayed only if it has been loaded to the map interface.
Navigation tree
Legend area
This area is not displayed by default. It is displayed only after you click in the button area.
Analysis results are displayed as icons in different colors. 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. 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.
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.
Issue 01 (2013-07-15)
1090
Parameter Cell ID
Range [0,65535]
Unit N/A
Description Indicates the ID of a polluted cell. Indicates the name of a polluted cell. Indicates the primary scrambling code of a polluted cell. Indicates the UTRAN Absolute Radio Frequency Channel Number (UARFCN) on the downlink. UTRAN is an abbreviation for Universal Terrestrial Radio Access Network.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Cell Name
1 to 64 characters [0,511]
N/A
P-SC
N/A
DownLink ARFCN
N/A
N/A
Average ECNO
[-24,0]
dB
Indicates the average receive signal quality of pilot signals of a polluted cell. Indicates the average receive signal strength of pilot signals of a polluted cell. Indicates the total number of pollution events for a polluted cell. Total number of measurement reports.
Average RSCP
[-115,-25]
dBm
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1091
Range [0,+)
Unit Number
Description Indicates the total number of cells that bring pollution to the current cell. Indicates the average receive signal quality of pilot signals of a polluted cell in CS service. Indicates the average receive signal strength of pilot signals of a polluted cell in CS service. Indicates the total number of pollution events for a polluted cell in CS service. Total number of measurement reports in CS service. Indicates the average receive signal quality of pilot signals of a polluted cell in PS service. Indicates the average receive signal strength of pilot signals of a polluted cell in PS service. Indicates the total number of pollution events for a polluted cell in PS service.
[-24,0]
dB
CS Average RSCP
[-115,-25]
dBm
[0,+)
Number
[0,+)
Number
[-24,0]
dB
PS Average RSCP
[-115,-25]
dBm
[0,+)
Number
Issue 01 (2013-07-15)
1092
Range [0,+)
Unit Number
Cell ID
[0,65535]
N/A
Issue 01 (2013-07-15)
1093
Range 1 to 64 characters
Unit N/A
Description Indicates the name of a polluter cell. If the current polluter cell is a defined neighboring cell of the current polluted cell, the name of a defined neighboring cell is displayed in this field. If the current polluter cell is an undefined neighboring cell of the current polluted cell, the name of a possible neighboring cell is displayed in this field. If the system cannot find the detailed information about the cell corresponding to the P-SC of the polluted cell, Unknown is displayed in this field.
P-SC
[0,511]
N/A
Indicates the primary scrambling code of a polluting cell. Indicates the polluting cell is whether a defined neighboring cell or not.
Is Neighbour Define
N/A
Issue 01 (2013-07-15)
1094
Range [-24,0]
Unit dB
Description Indicates the average receive signal quality of pilot signals of a polluter cell. Indicates the average receive signal strength of pilot signals of a polluter cell. Indicates the total number of pollution events that the current cell is polluted by polluter cells. Indicates the average receive signal quality of pilot signals of a polluter cell in CS service. Indicates the average receive signal strength of pilot signals of a polluter cell in CS service. Indicates the total number of pollution events that the current cell is polluted by polluter cells in CS service. Indicates the average receive signal quality of pilot signals of a polluter cell in PS service.
Average RSCP
[-115,-25]
dBm
[0,+)
Number
CS Average ECNO
[-24,0]
dB
CS Average RSCP
[-115,-25]
dBm
[0,+)
Number
PS Average ECNO
[-24,0]
dB
Issue 01 (2013-07-15)
1095
Range [-115,-25]
Unit dBm
Description Indicates the average receive signal strength of pilot signals of a polluter cell in PS service. Indicates the total number of pollution events that the current cell is polluted by polluter cells in PS service. Indicates the distance between a polluted cell and a polluter cell. Indicates the ID of a polluted cell.
[0,+)
Number
Distance
[0,+)
km
Cell ID
[0,65535]
N/A
Cell Name
1 to 64 characters [0,511]
N/A
P-SC
N/A
Issue 01 (2013-07-15)
1096
Range N/A
Unit N/A
Description Indicates the UARFCN Absolute Radio Frequency Channel Number (UARFCN) on the downlink. Indicates the average receive signal quality of pilot signals of a polluter cell. Indicates the average receive signal strength of pilot signals of a polluter cell. Indicates the total number of pollution events that the polluter cell brings pollution to other cells. Indicates the total number of cells that is polluted by the current cell. Indicates the average receive signal quality of pilot signals of a polluter cell in CS service. Indicates the average receive signal strength of pilot signals of a polluter cell in CS service.
Average ECNO
[-24,0]
dB
Average RSCP
[-115,-25]
dBm
[0,+)
Number
[0,+)
Number
[-24,0]
dB
CS Average RSCP
[-115,-25]
dBm
Issue 01 (2013-07-15)
1097
Range [0,+)
Unit Number
Description Indicates the total number of pollution events that the polluter cell brings pollution to other cells in CS service. Indicates the average receive signal quality of pilot signals of a polluter cell in PS service. Indicates the average receive signal strength of pilot signals of a polluter cell in PS service. Indicates the total number of pollution events that the polluter cell brings pollution to other cells in PS service.
PS Average ECNO
[-24,0]
dB
PS Average RSCP
[-115,-25]
dBm
[0,+)
Number
Issue 01 (2013-07-15)
1098
Cell Name
1 to 64 characters [0,511]
N/A
P-SC
N/A
Is Neighbour Define
N/A
Average ECNO
[-24,0]
dB
Average RSCP
[-115,-25]
dBm
[0,+)
Number
CS Average ECNO
[-24,0]
dB
Issue 01 (2013-07-15)
1099
Range [-115,-25]
Unit dBm
Description Indicates the average receive signal strength of pilot signals of a polluted cell in CS service. Indicates the total number of pollution events that the polluted cell is polluted by the current polluter cell in CS service. Indicates the average receive signal quality of pilot signals of a polluted cell in PS service. Indicates the average receive signal strength of pilot signals of a polluted cell in PS service. Indicates the total number of pollution events that the polluted cell is polluted by the current polluter cell in PS service. Indicates the distance between a polluted cell and a polluter cell.
[0,+)
Number
PS Average ECNO
[-24,0]
dB
PS Average RSCP
[-115,-25]
dBm
[0,+)
Number
Distance
[0,+)
km
Issue 01 (2013-07-15)
1100
Function Description
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 M2000 for UMTS uplink interference analysis. Figure 4-25 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-12.
Issue 01 (2013-07-15)
1101
Table 4-12 Description of analysis User Operat ion 1. Subscri be to applicat ion data Proced ure Issue an applicat ion data subscrip tion comma nd Collect scanned uplink frequen cy data So urc e Nas tar Ser ver Dest inati on eSA U Purpose
To request the 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.
eS AU
M20 00
The eSAU delivers data processing requests to NEs through the M2000, requesting the NEs to report scanned uplink frequency data to the M2000.
Issue 01 (2013-07-15)
1102
So urc e M2 000
Purpose
The Nastar periodically scans the directories on the M2000 for saving reported data. By doing this, the Nastar can obtain data from the M2000 immediately once data is reported. 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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
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.
eS AU
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
1103
Issue 01 (2013-07-15)
1104
When the 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.
Prerequisite
UMTS configuration data has been imported into the Nastar database. For detailed operations, see 3.5.2 Preparations for GSM Uplink Interference Analysis.
Procedure
Figure 4-26 shows the analysis process. Figure 4-26 Analysis process
Issue 01 (2013-07-15)
1105
Table 4-13 Description of the UMTS uplink interference analysis process No. (1) Proced ure Check the integrit y of UMTS uplink interfer ence analysis data Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Uplink Interference Analysis Data. 2. Specify the time period. 3. Select the desired 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 the analysis data does not exist, contact Huawei technical support. (2) Subscri be to uplink interfer ence analysis data (applica tion) Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the UMTS 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 Parameters Setting dialog box, set data subscription parameters. For details about the parameters, see Subscription Task Parameters. 5. Click Finish. 2.5 Subscribing to Analysis Data Reference 2.6 Checking the Integrity of Analysis Data
Issue 01 (2013-07-15)
1106
No.
Proced ure Check the integrit y of UMTS uplink interfer ence analysis data
Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Uplink Interference Analysis Data. 2. Specify the time period. 3. Select the desired 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 the analysis data does not exist, contact Huawei technical support.
Reference
(3)
Navigation path: In the navigation tree of the Analysis Task Management window, choose Theme Function > Basic Network Optimization > UMTS Uplink Interference Analysis. Procedure: 1. Double-click UMTS 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. 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.
l For detailed operations, see 2.7 Creating an Analysis Task. l For details about the parameters, see Analysis Task Parameters.
Issue 01 (2013-07-15)
1107
No. (4)
Description Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click the result record of the task. 2. In the displayed UMTS Uplink Interference Analysis window, view the analysis results about this record.
Reference l For detailed operations, see 2.8 Querying Analysis Results. l For details about the analysis result interface, see 4.6.4 Interface Description: UMTS Uplink Interference Analysis.
Description 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 The name is unique and case-sensitive and cannot be empty. l Task Name must be named in Chinese or English. Otherwise, the function of distributing analysis results by emails is unavailable.
Type of an analysis task to be created. Description of the task. Value range: The name contains a maximum of 200 characters.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Portal
Use either of the following methods to open the interface that displays UMTS uplink interference analysis results: l l Select an executed UMTS uplink interference analysis task and double-click a result record in the Task Result area. Select an executed UMTS uplink interference analysis task, right-click a result record in the Task Result area, and choose View Analysis Result from the shortcut menu.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1109
Issue 01 (2013-07-15)
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 4-27 shows the interface. Figure 4-27 Interface for UMTS uplink interference analysis results
N o. 1
Description 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. 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 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.
Issue 01 (2013-07-15)
1110
N o. 3
Description 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.
Parameter
Parameter RNC ID Range N/A Unit N/A Description Indicates the ID of an RNC. Indicates the name of an RNC. Indicates the name of a cell, for example, Cell_1. Indicates the primary scrambling code of a cell. Indicates the average value of the interference strength of main antennas. Indicates the average value of the interference strength of diversity antennas. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RNC Name
1 to 64 characters 1 to 64 characters
N/A
Cell Name
N/A
P-SC
[0,511]
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1111
Range N/A
Unit N/A
Description 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.
Issue 01 (2013-07-15)
1112
Range N/A
Unit N/A
Description 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.
Issue 01 (2013-07-15)
1113
Function Description
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 basis for carriers to develop the network that supports a certain feature. 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. 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. Figure 4-28 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-14.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1114
Table 4-14 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
Issue 01 (2013-07-15)
1115
So urc e M2 000
Purpose
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue a data query comma nd Return data query results Issue a task executio n comma nd
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
Issue 01 (2013-07-15)
1116
So urc e eS AU
Purpose
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
The license for UMTS terminal geographic display is required for viewing the function of UMTS terminal geographic display. l If a user wants to view only the task results, only the rights to view terminal analysis results needs to be granted. If the user wants to perform further operations on tasks, the following rights must be granted: Right to subscribe to the source data for terminal analysis. The source data subscription function has high security requirements. You are advised to contact the administrator to turn on the data source switch. Right to perform operations on the NEs to be analyzed. Right to perform operations on terminal analysis tasks. You need to obtain right to perform UMTS terminal inventory analysis if you want to perform UMTS terminal penetration analysis, UMTS terminal capability analysis, and UMTS terminal performance analysis. You need to obtain right in order to perform UMTS terminal geographic observation.
You are advised to perform terminal analysis with the granularity of a day to ensure the validity and timeliness of the configuration data.
Issue 01 (2013-07-15)
1118
Engineering Parameters (Optional) 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. 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. Map files (Optional) The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map. You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
Prerequisites
The UMTS configuration data and UMTS engineering parameters have been imported to the Nastar database. The terminal types and data service types have been configured on the Nastar. For details, see 4.7.2 Preparations for UMTS Terminal Analysis.
Process
Figure 4-29 shows the analysis process. Figure 4-29 Analysis process
Issue 01 (2013-07-15)
1120
Table 4-15 Description of the UMTS terminal analysis process N Procedure o . ( 1 ) Check whether analysis data is integrated? Description Reference
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Terminal Inventory Analysis Data, UMTS Terminal Traffic Model Analysis Data or UMTS Terminal Geographic Observation Data.
NOTE l Only UMTS Terminal Inventory Analysis Data is required to analyze terminal penetration rate, capability, and performance. l Only UMTS Terminal Traffic Model Analysis Data is required to analyze terminal traffic models. l Only UMTS Terminal Geographic Observation Data is required to observe terminals geographically.
2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
1121
Description
Reference
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the UMTS tab. 2. Select the NEs to be configured from the left navigation tree. 3. On the Basic Subscription Settings tab page, click Set. 4. In the Basic Subscription Settings dialog box, set the switch of Terminal Analysis Data(CHR) 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. Verify that the data switch is successfully turned on by viewing information displayed in the Log Info area.
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the UMTS tab. 2. Select the NEs to be configured from the left navigation tree. 3. On the Terminal Analysis tab page, click ON. 4. In the Terminal Analysis Parameter Setting dialog box, set the threshold value for exceptions. For details about parameters, see Subscription Task Parameters. 5. Click Confirm. Verify that data subscription is successfully turned on by viewing information displayed in the Log Info area.
Issue 01 (2013-07-15)
1122
Description
Reference
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to UMTS Terminal Inventory Analysis Data, UMTS Terminal Traffic Model Analysis Data or UMTS Terminal Geographic Observation Data.
NOTE l Only UMTS Terminal Inventory Analysis Data is required to analyze terminal penetration rate, capability, and performance. l Only UMTS Terminal Traffic Model Analysis Data is required to analyze terminal traffic models. l Only UMTS Terminal Geographic Observation Data is required to observe terminals geographically.
2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
Issue 01 (2013-07-15)
1123
Description
Reference
Entry: In the left navigation tree of the Analysis Task Management window, choose Theme Function > Terminal Analysis > UMTS Terminal Analysis. Procedure: 1. Double-click the UMTS 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. 4. Optional: On the Set Traffic Model Parameters tab page, select a service or application type and busy hours for traffic model analysis. 5. Optional: On the Select Geographic Terminal Abilities tab page, select terminal capabilities for analysis. The Nastar calculates numbers and percentages of terminals supporting the capabilities in each raster. 6. Optional: On the Select 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. 7. Optional: On the Grid Resolution Settings tab page, select the Grid Resolution for displaying terminal geographic observation results. 8. Click Next. 9. Select the analysis time period. The Nastar obtains the relevant analysis data in the time period. 10.Click Complete. For details about parameters, see Analysis Task Parameters.
l For detailed operations, see 2.7 Creating an Analysis Task. l For parameter description, see Analysis Task Parameters.
Issue 01 (2013-07-15)
1124
Description
Reference
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click the analysis result of a task. 2. In the displayed UMTS Terminal Analysis Task window, view the UMTS terminal analysis result.
l For details, see 2.8 Querying Analysis Results. l For details on the description about the window for displaying task results, see 4.7.4 Interface Description: UMTS Terminal Analysis. l For details, see 2.10 Exporting Analysis Reports. l For details on the description about the window for displaying task results, see 4.7.4 Interface Description: UMTS Terminal Analysis.
( 5 )
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. 2. Set the export path and export format. 3. Click Finish.
Issue 01 (2013-07-15)
1125
Indicates the threshold for extra long RRC setup delay when a terminal performs cell reselection, cell change commands, registration or separation. RRC setup delay indicates the duration from the RRC Connection Request message to the RRC Connection Setup Complete message.
[0.0,100000 .0]
Indicates the threshold for extra long RRCconnection setup when a terminal accesses services. RRC setup delay indicates the duration from the RRC Connection Request message to the RRC Connection Setup Complete message.
[0.0,100000 .0]
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.0,100000 .0]
Indicates the expiration threshold for handing over a terminal to other systems such as GSM.
[0.0,100000 .0]
Issue 01 (2013-07-15)
1126
Para meter Overl ong InterSyste m Incom ing Hando ver Delay Thres hold (s) AMR Short Call Thres hold (s) VP Short Call Thres hold (s) Abnor mal SQI Thres hold (s)
Description
Range
Indicates the expiration threshold for handing over a terminal from other systems such as GSM to the UMTS.
[0.0,100000 .0]
Indicates the threshold for a very short call duration when a terminal performs a voice call. The AMR call duration indicates the duration from the RAB ASSIGNMENT REQUEST message to the IU RELEASE COMMAND message. Indicates the threshold for a very short call duration when a terminal performs a VP call. The AMR call duration indicates the duration from the RAB ASSIGNMENT REQUEST message to the IU RELEASE COMMAND message. Indicates the threshold for SQI exceptions when a terminal performs a voice call. This indicator is calculated for only the AMR service. 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.
[0.0,100000 .0]
[0.0,100000 .0]
[0,500]
300
Issue 01 (2013-07-15)
1127
Description 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 The name is unique and case-sensitive and cannot be empty. l Task Name must be named in Chinese or English. Otherwise, the function of distributing analysis results by emails is unavailable.
Type of an analysis task to be created. Description of the task. Value range: The name contains a maximum of 200 characters.
Parameter information Parameter Geographic Terminal Objects Description 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. If terminal capabilities are not selected, terminal capability analysis will not function during geographic observation. Sets services or applications and busy hours for traffic model analysis. If the parameter for specifying busy hours is not set, the Nastar does not analyze the traffic model. If the parameter for specifying service or application types is not set, the Nastar analyzes the traffic model but not the service or application types. Set the Grid Resolutionfor 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.
Issue 01 (2013-07-15)
1128
Parameter Date
Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Navigation Path
Use either of the following methods to open the interface that displays UMTS terminal analysis results: l l Select a UMTS terminal analysis task in the Finish state, and double-click a result record of the task in the displayed Task Result area. Select a UMTS terminal analysis task in the Finish 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 4-30 shows the terminal analysis results. Figure 4-30 Interface for UMTS terminal analysis results
No. 1
Description is used to display terminal analysis results through geographic display. For detailed operations, see Terminal Analysis Results Displayed Through Geographic Display.
1129
Issue 01 (2013-07-15)
No. 2
Description Analysis results are displayed in the form of tab page. l The Analyze Terminal 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 Analyze Terminal 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 Analyze Terminal 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 details, see Interface Description: Terminal Performance Analysis.
Issue 01 (2013-07-15)
1130
No. 1
Description l 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 Aggregation Type 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. The number and occupation of TopN terminals on the live network from a certain analysis dimension are displayed in a table. You can save the table by right-clicking the table and choosing Save As from the shortcut menu.
Statistics table
No. 1
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.
1131
Issue 01 (2013-07-15)
No. 2
Description Selects all objects to be analyzed. Supports the selection of analyzed objects by the following three different dimensions: the whole network, a single BSC, or a single cell. 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. 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 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 capability can be displayed at the same time. You can view the analysis results of other terminal capabilities by using the scroll bar.
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 4.7.5 Parameters for Viewing UMTS Terminal Analysis Results.
Issue 01 (2013-07-15)
1132
No. 1
Description 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 When you select the aggravation objects, the node information is displayed only when you select IMEI-TAC_OS_Version.
l The KPI Evaluation node is used to select the KPIs to be analyzed. The KPIs are also displayed in the right area. 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 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, and the system saves the displayed TopN results and all the other results that are not displayed to your local computer. 3 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. You can save the table by right-clicking the table and choosing Save As from the shortcut menu. For detailed description of the parameters, see4.7.5 Parameters for Viewing UMTS Terminal Analysis Results.
Issue 01 (2013-07-15)
1133
N o. 1
Issue 01 (2013-07-15)
1134
N o. 2
Description 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
l Polygon Areas: enables you to analyze only a selected polygon in the Geographic Observation interface. You can save the cells in a polygon as a cell group. You can analyze multiple KPIs simultaneously based on a polygon. 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\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. 3 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. 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. This area is empty for terminal analysis.
Issue 01 (2013-07-15)
1135
N o. 5
Description 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. 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. The interface displays no information when it is opened. If you select a grid, the values of selected KPIs in this gird are displayed. If you select a site, information about the site is displayed. If you select a cell, information about the cell such as engineering parameters and longitude and latitude coordinates is displayed.
Informati on area
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. Indicates the operating system and version of a terminal of the same type.
N/ A
N/ A
N/ A
N/ A
Indicates the operating system and major version of the terminal, for example, Android 2.
Issue 01 (2013-07-15)
1136
Param eter OS
Ra ng e N/ A
U nit N/ A
Description
Supported NE Version BSC6900 V900R014C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
Indicates the operating system of the terminal, for example, Android and Windows Phone 7.
Vendor
[1, 25 6] [1, 25 6] N/ A
N/ A
Model
N/ A
Type
N/ A
Indicates the terminal type, for example, common terminal, intelligent terminal, and data card.
Chip Model
[0, 25 6] N/ A
N/ A
Techno logy
N/ A
Indicates the RAT that the terminal supports, for example, GSM and WCDMA.
Termin als
[1, + )
Nu mb er
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. Indicates the data transfer mode that the terminal uses, for example, HSDPA and HSUPA.
N/ A
N/ A
N/ A
N/ A
Issue 01 (2013-07-15)
1137
Ra ng e N/ A
U nit N/ A
Description
User-defined terminal attributes in the terminal type management window. The user-defined attribute names are displayed.
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.
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.
N/ A
N/ A
Used to collect statistics on the number and percentage BSC6900 of terminals that support E_FACH under a cell, RNC, V900R014C or network. 00 or later version Used to collect statistics on the number and percentage of terminals that support E_RACH under a cell, RNC, or network. Used to collect statistics on the number and percentage of terminals that support frequency band 900 under a cell, RNC, or network. 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. BSC6900 V900R014C 00 or later version BSC6900 V900R014C 00 or later version BSC6900 V900R013C 00 or later version
E_RA CH
N/ A
N/ A
U900
N/ A
N/ A
HSDP A
N/ A
N/ A
Issue 01 (2013-07-15)
1138
Ra ng e N/ A
U nit N/ A
Description
Supported NE Version BSC6900 V900R013C 00 or later version BSC6900 V900R014C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R014C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R014C 00 or later version BSC6900 V900R013C 00 or later version
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, DC-HSUPA, and DC-HSUPA+16QAM. Used to collect statistics on the number and percentage of terminals that support continuous packet connectivity (CPC) under a cell, RNC, or network. Used to collect statistics on the number and percentage of terminals that support Fast Dormancy under a cell, RNC, or network. Used to collect statistics on the number and percentage of terminals that support R8 Fast Dormancy under a cell, RNC, or network. Used to collect statistics on the number and percentage of terminals that support Wi-Fi under a cell, RNC, or network. Used to collect statistics on the number and percentage of terminals that support LTE under a cell, RNC, or network. Indicates the number of terminals with the same IMEITACs but different IMEIs.
CPC
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A
FDDLTE
N/ A
N/ A
Termin als
[0, + )
Nu mb er
Issue 01 (2013-07-15)
1139
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).
[0, + )
Nu mb er
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). Indicates the success rate of non-service RRC setups initiated by the terminal.
[0, 10 0]
[0, + )
Nu mb er
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).
[0, + )
Nu mb er
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). Indicates the success rate of service RRC setups initiated by the terminal.
[0, 10 0]
[0, + )
Nu mb er
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.
Issue 01 (2013-07-15)
1140
Ra ng e [0, + )
U nit Nu mb er
Description
Supported NE Version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
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. 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.
[0, 10 0]
Issue 01 (2013-07-15)
1141
Indicates the total number of abnormal RAB releases. The RAB is abnormally released in any of the following situations: (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: 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 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.
[0, 10 0]
Issue 01 (2013-07-15)
1142
Indicates the number of soft handovers initiated by the terminal during the service process. 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. 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.
[0, + )
Nu mb er
Indicates the number of abnormal soft handovers during the service process. 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. 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.
[0, 10 0]
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. Indicates the number of hard handover requests initiated by a terminal during the service process. 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.
[0, + )
Nu mb er
Issue 01 (2013-07-15)
1143
Ra ng e [0, + )
U nit Nu mb er
Description
Indicates the number of abnormal hard handovers failures for a terminal during the service process. 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.
[0, 10 0]
Indicates the success rate of hard handovers initiated by a terminal during the service process. 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.
InterRAT Outgoi ng Hando ver Reques ts InterRAT Outgoi ng Hando ver Succes ses InterRAT Incomi ng Hando ver Reques ts
[0, + )
Nu mb er
Indicates the number of inter-system outgoing handover requests initiated by a terminal during the service process. In RAN14.0 and later versions, if multiple inter-system outgoing handovers are initiated during a call, the Nastar collects statistics about and analyzes all the initiated handovers.
[0, + )
Nu mb er
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 inter-system outgoing handovers are initiated during a call, the Nastar collects statistics about and analyzes all the initiated handovers.
[0, + )
Nu mb er
Indicates the number of inter-system ingoing handover requests initiated by a terminal during the service process. In RAN14.0 and later versions, if multiple inter-system ingoing handovers are initiated during a call, the Nastar collects statistics about and analyzes all the initiated handovers.
Issue 01 (2013-07-15)
1144
Ra ng e [0, + )
U nit Nu mb er
Description
Indicates the number of times inter-system ingoing handover requests are successfully initiated by a terminal during the service process. In RAN14.0 and later versions, if multiple inter-system ingoing handovers are initiated during a call, the Nastar collects statistics about and analyzes all the initiated handovers.
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.
[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.
[0, 10 0]
Indicates the percentage of RRC setup overlong delays during the process of sending system messages such as the location change message.
Issue 01 (2013-07-15)
1145
Param eter RRC Setup Delay Report s (Servic e) RRC Setup Averag e Delay (Servic e) Ratio of RRC Setup Overlo ng Delays (Servic e) RAB Setup Delay Report s RAB Setup Averag e Delay RAB Setup Overlo ng Delays Ratio
Ra ng e [0, + )
U nit Nu mb er
Description
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.
[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 message Timestamp of an RRC CONN REQ message. Indicates the percentage of RRC setup overlong delays during the service process initiated by the terminal.
[0, 10 0]
[0, + )
Nu mb er
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. 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. 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.
BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
[0, + ) [0, 10 0]
Issue 01 (2013-07-15)
1146
Param eter InterRAT Outgoi ng Hando ver Delay Report s InterRAT Outgoi ng Hando ver Averag e Delay Ratio of InterRAT Outgoi ng Hando ver Overlo ng Delays InterRAT Incomi ng Hando ver Delay Report s InterRAT Incomi ng Hando ver Averag e Delay
Ra ng e [0, + )
U nit Nu mb er
Description
Indicates the number of inter-system outgoing handover delay reports recorded by the Nastar. Intersystem outgoing handover delay = Timestamp of an IU RELEASE COMMAND message Timestamp of an RELOCATION REQUIRED message.
[0, + )
Indicates the value for average inter-system outgoing handover delays recorded by the Nastar. Inter-system outgoing handover delay = Timestamp of an IU RELEASE COMMAND message Timestamp of an RELOCATION REQUIRED message.
[0, 10 0]
Indicates the percentage of inter-system outgoing handover overlong delays recorded by the Nastar.
[0, + )
Nu mb er
Indicates the number of inter-system incoming handover delay reports recorded by the Nastar.
[0, + )
Indicates the value for average inter-system incoming handover delays recorded by the Nastar.
Issue 01 (2013-07-15)
1147
Ra ng e [0, 10 0]
U nit %
Description
Indicates the value for average inter-system incoming handover delays recorded by the Nastar.
Indicates the number of uplink one-way audio calls during the calling process. Uplink one-way calls are detected by the BSC.
[0, + )
Nu mb er
Indicates the number of downlink one-way audio calls during the calling process. Downlink one-way calls are detected by the BSC.
Nu mb er %
Indicates the number of calls with noises during the calling process. The noises can be detected by the BSC.
BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
Noise Ratio
Indicates the percentage of calls with noises during the calling process. Percentage of calls with noises = Number of calls with noises/Number of connection acknowledgements x 100%. 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.
SQI Report s
Nu mb er
Issue 01 (2013-07-15)
1148
Ra ng e [0, + ) [0, 10 0]
U nit Nu mb er %
Description
Supported NE Version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
Indicates the percentage of abnormal SQLs during the calling process. Percentage of abnormal SQLs = Number of calls with abnormal SQLs/Connection acknowledgements x 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. 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. 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. 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. 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.
[0, 10 0]
[0, 10 0]
[0, 10 0]
[0, 10 0]
[0, 10 0]
Issue 01 (2013-07-15)
1149
Indicates the number of valid MRs with RAB occupation duration that can be counted by the Nastar during the voice service process. 1. Starting time The time when an RAB assigned process succeeds. The time when the migration into the process ends. 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.
Averag e AMR RAB Duratio n AMR RAB Oversh ort Duratio ns VP RAB Duratio n Report s Averag e VP RAB Duratio n
[0, + )
Indicates the value for average RAB occupation duration recorded in one report during the voice service process.
[0, + )
Nu mb er
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.
[0, + )
Nu mb er
Indicates the number of valid reports with RAB occupation duration that can be collected by the Nastar during the video phone service process. For details about how to analyze the RAB setup and release, see Description of Measurement Reports for AMR Service Duration.
[0, + )
Indicates the value for average VP RAB occupation duration recorded in one report during the VP service process.
Issue 01 (2013-07-15)
1150
Ra ng e [0, + )
U nit Nu mb er
Description
Indicates the number of videophone calls with short call duration. 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 Duratio n Report s PS R99 RAB Averag e Duratio n HSDP A RAB Duratio n Report s Averag e HSDP A RAB Duratio n HSUP A RAB Duratio n Report s Averag e HSUP A RAB Duratio n
Issue 01 (2013-07-15)
[0, + )
Nu mb er
Indicates the number of reports with valid RAB occupation duration that can be collected by the Nastar during the R99 service process. For details about how to analyze the RAB setup and release, see Description of Measurement Reports for AMR Service Duration.
[0, + )
Indicates the value for average RAB occupation duration recorded in one report during the R99 service process.
[0, + )
Nu mb er
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.
[0, + )
Indicates the average valid data transmission duration during an HSDPA service process.
[0, + )
Nu mb er
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.
[0, + )
Indicates the value for average RAB occupation duration recorded in one report during the HSUPA service process.
1151
Param eter HSUP A_HS DPA RAB Duratio n Report s Averag e HSUP A_HS DPA RAB Duratio n
Ra ng e [0, + )
U nit Nu mb er
Description
Indicates the number of reports with valid RAB occupation duration that can be counted during the HSUPA and HSDPA service processes.
[0, + )
Indicates the average RAB occupation duration recorded in a report during the HSUPA and HSDPA service processes.
Indicates the ratio of the downlink throughput to transmission duration of valid data during the R99 service process.
[0, + )
kbi t/s
Indicates the ratio of the uplink throughput to transmission duration of valid data during the R99 service process.
[0, + )
kbi t/s
Indicates the ratio of the downlink throughput to transmission duration of valid data during the HSDPA service process.
Issue 01 (2013-07-15)
1152
Param eter Averag e HSUP A Throug hput HSUP A HSDP A UL Averag e Throug hput HSUP A HSDP A DL Averag e Throug hput
Ra ng e [0, + )
Description
Indicates the ratio of the uplink throughput to transmission duration of valid data during the HSUPA service process.
[0, + )
kbi t/s
Indicates the ratio of the uplink throughput to transmission duration of valid data during the HSDPA and HSUPA service processes.
[0, + )
kbi t/s
Indicates the ratio of the downlink throughput to transmission duration of valid data during the HSDPA and HSUPA service processes.
RNC Name
N/ A
Cell ID
[0, 65 53 5]
N/ A
Issue 01 (2013-07-15)
1153
Ra ng e N/ A
U nit N/ A
Description
NOTE
For details about other parameters, see Performance Analysis Summary-Evaluate Accessibility , Performance Analysis Summary-Evaluate Retainability, Performance Analysis Summary-Evaluate Mobility, Performance Analysis Summary-Evaluate Delay, Performance Analysis SummaryEvaluate Quality, Performance Analysis Summary-Evaluate Duration and Performance Analysis Summary-Evaluate Rate.
The grid map is rendered according to the total traffic of terminals in the grids.
Uplink traffic
K B
The grid map is rendered according to the uplink traffic of terminals in the grids.
Downli nk traffic
K B
The grid map is rendered according to the downlink traffic of terminals in the grids.
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.
Issue 01 (2013-07-15)
1154
Ra ng e N/ A
U nit N/ A
Description
Supported NE Version BSC6900 V900R013C 00 or later version BSC6900 V900R014C 00 or later version BSC6900 V900R014C 00 or later version BSC6900 V900R014C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R014C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R014C 00 or later version BSC6900 V900R014C 00 or later version
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. The grid map is rendered according to the percentage of terminals that support E_FACH in the total number of terminals in the grids. The grid map is rendered according to the percentage of terminals that support E_RACH in the total number of terminals in the grids. The grid map is rendered according to the percentage of terminals that support U900 in the total number of terminals in the grids. The grid map is rendered according to the percentage of terminals that support HSDPA in the total number of terminals in the grids. The grid map is rendered according to the percentage of terminals that support HSUPA in the total number of terminals in the grids. The grid map is rendered according to the percentage of terminals that support CPC in the total number of terminals in the grids. The grid map is rendered according to the percentage of terminals that support Fast Dormancy in the total number of terminals in the grids. 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. The grid map is rendered according to the percentage of terminals that support FDD-LTE in the total number of terminals in the grids.
N/ A
N/ A
E_RA CH
N/ A
N/ A
U900
N/ A
N/ A
HSDP A
N/ A
N/ A
HSUP A
N/ A
N/ A
CPC
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A
Issue 01 (2013-07-15)
1155
Ra ng e N/ A
U nit N/ A
Description
The grid map is rendered according to the percentage of terminals that support Wi-Fi in the total number of terminals in the grids.
Function Description
Generally, the network optimization engineers use the whole-to-partial analysis method for network optimization or performance analysis. The Nastar locates and analyzes network problems by monitoring performance counters, 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1156
Issue 01 (2013-07-15)
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. In addition to detecting abnormal cells and exception causes, the cell performance analysis function allows you to perform in-depth analysis on the abnormal cells. Based on the abnormal call records, the Nastar allows for the in-depth analysis on specified cells, an exception type, all exception causes of an exception type, and bottom N subscribers and terminals related to an exception cause. After starting in-depth analysis, the Nastar will go to the complaint analysis result interface that shows detailed information about subscriber calls, facilitating problem locating.
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 l The Nastar collects statistics based on subscriber experience data while the 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 M2000 and PRS can only detect abnormal cells.
Function Principles
The Nastar uses the CHRs on the NE side for cell performance analysis. Figure 4-35 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-16.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1157
Table 4-16 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
Issue 01 (2013-07-15)
1158
So urc e M2 000
Purpose
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue a data query comma nd Return data query results Issue a task executio n comma nd
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
Issue 01 (2013-07-15)
1159
So urc e eS AU
Purpose
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
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.
To ensure the validity of the configuration data, you are advised to analyze cell performance on a daily basis.
Prerequisites
The UMTS configuration data and engineering parameters have been imported into the Nastar database. For details, see 4.8.2 Preparations for UMTS Cell Performance Analysis.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1161
Process
Figure 4-36 shows the analysis process. Figure 4-36 Analysis process
Issue 01 (2013-07-15)
1162
Table 4-17 Description of UMTS cell performance analysis process No. (1) Procedure Check the integrity of analysis data Description Entry: Choose Maintenance > Data Maintenance Management. Procedure: 1. Set Data Type to UMTS Cell Performance Analysis Data. 2. Specify the time period. 3. Select the desired 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
1163
No. (2)
Description
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.
Entry: Choose Maintenance > Data Subscription Management. Procedure: 1. In the Data Subscription Management window, click the UMTS tab. 2. In the navigation tree, select the desired NEs. 3. On the Basic Subscription Settings tab page, click Set. 4. In the Basic Subscription Settings dialog box, set the data source switch of Cell Performance Analysis Data (CHR) to ON. If you want to view the all signaling information when viewing deep , select the analysis results, click interface about All Signaling. 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) Entry: Choose Maintenance > Data Subscription Management. Procedure: 1. In the Data Subscription Management window, click the UMTS tab. 2. In the navigation tree, select the desired NEs. 3. On the Cell Performance Analysis tab page, click ON. 4. In the displayed Cell Performance Parameter Setting dialog box, set the related parameters. 5. Click Confirm. For details about parameters, see Subscription Task Parameters.
Issue 01 (2013-07-15)
1164
No.
Description Entry: Choose Maintenance > Data Maintenance Management. Procedure: 1. Set Data Type to UMTS Cell Performance Analysis Data. 2. Specify the time period. 3. Select the desired 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 the analysis data does not exist, contact Huawei technical support.
(3)
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 Performance Analysis. 2. Specify the task name and remarks. Then, click Next. 3. On the Select NE(s) tab page, select the 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.
l For detailed operations, see 2.7 Creating an Analysis Task. l For details about the parameters, see Analysis Task Parameters.
(4)
Entry: In the upper right area of the Analysis Task Management window, select a cell performance analysis task in Finish state. In the lower right Task Result area, select a result record of the task. Procedure: 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.
l For detailed operations, see 2.8 Querying Analysis Results. l For details about the analysis result interface, see 4.8.4 Interface Description: UMTS Cell Performance Analysis.
1165
Issue 01 (2013-07-15)
No.
Description Entry: Click the icon, or right-click a cell in the navigation tree and choose Further Analysis from the shortcut menu. 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.
Reference
(5)
Entry: On the toolbar in the upper left part of the cell performance analysis window, click the export icon. Procedure 1. Click the export icon on the toolbar. 2. Specify the export format, export path, counters to be exported, and export scope. 3. Click Export.
l For details, see 2.10 Exporting Analysis Reports. l For details on the description of the window for showing analysis results, see 4.8.4 Interface Description: UMTS Cell Performance Analysis.
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. 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.
Issue 01 (2013-07-15)
1166
P ar a m et er
R a n g e e m
Unit
Description
CPIC H RSC P on Acce ss NonServi ce RRC Acce ss Dela y(s) Servi ce RRC Acce ss Dela y(s) Soft hand over Dela ys(s) Hard hand over Dela y(s) Chan nel Switc hover Dela ys(s)
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.
D el ay Pr o bl e m
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.
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.
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. 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. 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.
Issue 01 (2013-07-15)
1167
P ar a m et er
R a n g e
Unit
Description
Relo catio n Dela y(s) InterSyste m Outg oing Hand over (3G to 2G) Dela y(s) InterSyste m Inco ming Hand over (2G to 3G) Dela y(s) A M R S er vi ce in C S D o m D el ay Pr o bl e m Call Setup Dela y (MO C) (s)
Delay problem indicating that the relocation delay exceeds the predefined threshold: Relocation delay (s) = Relocation complete time - Relocation time.
Delay problem indicating that the outgoing inter-RAT handover (3G->2G) 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 interRAT handover delay = Time stamp of the IU RELEASE COMMAND message - Time stamp of the RELOCATION REQUIRED message.
Delay problem indicating that 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 IU RELEASE COMMAND message - Time stamp of the RELOCATION REQUIRED message.
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.
Issue 01 (2013-07-15)
1168
P ar a m et er ai n
R a n g e
Unit
Description
Delay problem indicating that the call setup delay exceeds the predefined 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 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 Com pletio n Dela y (Aler ting) (MO C) (s) Call Com pletio n Dela y (Aler ting) (MT C) (s) RAB Setup Dela y(s)
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.
Delay problem indicating that the call connection delay exceeds the predefined threshold (alerting) (mobile-terminated): If the first RAB is used for the mobile-terminated AMR service in the CS domain, you can obtain the call connection delay by using the following formula: Call connection delay (s) (alerting) (mobile-terminated) = Time stamp of the alerting message - Signaling access time.
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 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 RAB request time: Time when the UTRAN receives the RAB Assignment Request message from the CN.
Issue 01 (2013-07-15)
1169
P ar a m et er
R a n g e S h or t C al l Pr o bl e m
Unit
Description
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. 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.
Short call (MO C) (s) Short call (MT C) (s) S er vi ce Q ua lit y Pr o bl e m Over high Prop ortio n of Servi ce Quali ty with Bad SQI
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. 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. 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.
Issue 01 (2013-07-15)
1170
P ar a m et er V P S er vi ce in C S D o m ai n
R a n g e D el ay Pr o bl e m
Unit
Description
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.
Delay problem indicating that the call setup delay exceeds the predefined 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 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.
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 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.
Issue 01 (2013-07-15)
1171
P ar a m et er
R a n g e
Unit
Description
Call Com pletio n Dela y (Aler ting) (MT C) (s) RAB Setup Dela y(s)
Delay problem indicating that the call connection delay exceeds the predefined threshold (alerting) (mobile-terminated): If the first RAB is used for the mobile-terminated VP service in the CS domain, you can obtain the call connection delay by using the following formula: Call connection delay (s) (alerting) (mobile-terminated) = Time stamp of the alerting message Signaling access time.
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 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 RAB request time: Time when the UTRAN receives the RAB Assignment Request message from the CN.
S h or t C al l Pr o bl e m
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. 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.
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 the DisConnect message - Time stamp of the Connect Acknowledge message) is shorter than the threshold for mobile-originated short call. 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 the DisConnect message - Time stamp of the Connect Acknowledge message) is shorter than the threshold for mobile-terminated short call.
Issue 01 (2013-07-15)
1172
P ar a m et er P S S er vi ce in P S D o m ai n
R a n g e D el ay Pr o bl e m
Unit
Description
Delay problem indicating that the call setup delay exceeds the predefined 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 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.
Delay problem indicating that the call setup delay exceeds the predefined 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 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.
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 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 RAB request time: Time when the UTRAN receives the RAB Assignment Request message from the CN.
Issue 01 (2013-07-15)
1173
P ar a m et er
R a n g e Sl o w D o w nl in k S pe ed
Unit
Description
Final ly Nego tiated Rate of Dow nlink RAB (kbit/ s) Aver age Dow nlink Thro ughp ut (kbit/ s) Final ly Nego tiated Rate of Uplin k RAB (kbit/ s) Aver age Uplin k Thro ughp ut (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.
Low downlink rate indicating a low average downlink throughput rate: Average downlink throughput rate (kbit/s) = Downlink throughput/ Downlink data transfer duration.
Sl o w U pl in k S pe ed
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.
Low uplink rate indicating a low average uplink throughput rate: Average uplink throughput rate (kbit/s) = Uplink throughput/Uplink data transfer duration.
Issue 01 (2013-07-15)
1174
P ar a m et er H S D P A S er vi ce in P S D o m ai n
R a n g e D el ay Pr o bl e m
Unit
Description
Delay problem indicating that the call setup delay exceeds the predefined 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. 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.
Delay problem indicating that the call setup delay exceeds the predefined threshold (mobile-terminated): If the first RAB is used for the HSDPA service in the PS domain and the RRC connection setup is caused by the mobile-terminated service, the call setup delay (s) (mobile-terminated) 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.
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 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 RAB request time: Time when the UTRAN receives the RAB Assignment Request message from the CN.
Issue 01 (2013-07-15)
1175
P ar a m et er
R a n g e Sl o w D o w nl in k S pe ed
Unit
Description
Low downlink rate indicating a low average downlink throughput rate: Average downlink throughput rate (kbit/s) = Downlink throughput/ Downlink data transfer duration.
H S U P A S er vi ce in P S D o m ai n
D el ay Pr o bl e m
Delay problem indicating that the call setup delay exceeds the predefined threshold (mobile-originated): If the first RAB is used for the HSUPA 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. 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.
Delay problem indicating that the call setup delay exceeds the predefined threshold (mobile-terminated): If the first RAB is used for the HSUPA service in the PS domain and the RRC connection setup is caused by the mobile-terminated service, the call setup delay (s) (mobile-terminated) 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.
Issue 01 (2013-07-15)
1176
P ar a m et er
R a n g e
Unit
Description
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 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 RAB request time: Time when the UTRAN receives the RAB Assignment Request message from the CN.
Sl o w U pl in k S pe ed H S D P A _ H S U P A S er vi ce in P S D o m ai n D el ay Pr o bl e m
Aver age Uplin k Thro ughp ut (kbit/ s) Call Setup Dela y (MO C) (s)
Low uplink rate indicating a low average uplink throughput rate: Average uplink throughput rate (kbit/s) = Uplink throughput/Uplink data transfer duration.
Delay problem indicating that the call setup delay exceeds the predefined 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. 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.
Issue 01 (2013-07-15)
1177
P ar a m et er
R a n g e
Unit
Description
Delay problem indicating that the call setup delay exceeds the predefined 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. 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.
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 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 RAB request time: Time when the UTRAN receives the RAB Assignment Request message from the CN.
Sl o w D o w nl in k S pe ed
Low downlink rate indicating a low average downlink throughput rate: Average downlink throughput rate (kbit/s) = Downlink throughput/ Downlink data transfer duration.
Issue 01 (2013-07-15)
1178
P ar a m et er
R a n g e Sl o w U pl in k S pe ed
Unit
Description
Low uplink rate indicating a low average uplink throughput rate: Average uplink throughput rate (kbit/s) = Uplink throughput/Uplink data transfer duration.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time.
Issue 01 (2013-07-15)
1179
Parameter Delay
Description 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. The value of this parameter must not precede the end time of Date.
Portal
l Use either of the following methods to open the interface that displays the results of UMTS cell performance analysis (aggregated): 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 the Task Result area, and choose View Analysis Result from the shortcut menu. l Open the interface that displays the results of UMTS cell performance analysis (in-depth): On the aggregated analysis result interface, click Further Analysis from the shortcut menu. , or right-click an NE and choose
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 users, terminal models, or cells. Figure 4-37 shows the analysis result interface.
Issue 01 (2013-07-15)
1180
No. 1
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. 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 reports related to the exception causes. In the navigation tree, you can right-click a cell and choose Further Analysis from the shortcut menu. The in-depth analysis result interface is displayed, showing all the abnormal call records under this cell. Displays the number of reports and ratio under each exception type for the selected RNC or cell under each service type. This area is displayed accordingly with Area 4. Click the column header to resort this table. Right-click on the table and choose Save As from the shortcut menu to export this table.
Issue 01 (2013-07-15)
1181
No. 4
Description Displays the number of reports and ratio under each exception cause of an exception type for the selected RNC or cell. This area is displayed accordingly with Area 5. l The first row displays the total number of reports under all exception causes, which is also the number of reports under the selected exception type. Starting from the second row, each row displays the number and ratio of reports under each exception cause. l Select an exception cause and click the icon to open the indepth analysis interface where you can view all abnormal call records caused by this exception cause.
Displays the number of reports related to bottom N users, terminal models, or cells 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. l After you select a cell in Area 2, this table displays the number 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.
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: UMTS Complaint Analysis Support.
Issue 01 (2013-07-15)
1182
U nit N/ A
Description
Service type of a cell exception. including: 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
Param eter
U nit
Description
Supported NE Version
N/ A
N/ A
Analysis of an exception from two dimensions: the network exception itself and the subscriber's subjective perception. Number of times that the cause of certain exceptions is reported.
BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
[0, + )
Nu mb er
Proportion of an exception type against all exception types under the same service type.
Issue 01 (2013-07-15)
1184
A failure during the process from a subscriber starts accessing the network until the non-service radio resource control (RRC) connection setup is complete.
N/ A
N/ A
A failure during the process from a subscriber starts accessing the network until the service RRC connection setup is complete.
BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
N/ A
N/ A
An exception occurs during the process from an RRC connection release is initiated until the RRC connection release is complete.
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. You are advised to set the threshold for the TP exception or the CPICH Ec/N0 exception by using the data source subscription function.
Outgoi ng SHO Failure Incomi ng SHO Failure Outgoi ng HHO Failure Incomi ng HHO 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. A soft handover fails when a subscriber is using a specific service. Statistics on incoming soft handovers are collected based on the target cell. A hard handover fails when a subscriber is using a specific service. Statistics on outgoing hard handovers are collected based on the source cell. A hard handover fails when a subscriber is using a specific service. Statistics on incoming hard handovers are collected based on the target cell.
BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A
Issue 01 (2013-07-15)
1185
Param eter Cell Update Failure Outgoi ng Channe l Hando ver Failure Incomi ng Channe l Hando ver Failure Relocat ion Failure InterSystem Outgoi ng Hando ver Failure (IntraSystem ) InterSystem Incomi ng Hando ver Failure (IntraSystem )
Ra ng e N/ A
U nit N/ A
Description
Supported NE Version BSC6900 V900R014C 00 or later version BSC6900 V900R014C 00 or later version
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.
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.
N/ A
N/ A
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.
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.
Issue 01 (2013-07-15)
1186
Ra ng e N/ A
U nit N/ A
Description
The following delay exceptions might occur when a subscriber attempts to access the network: The non-service RRC connection setup delay exceeds the predefined threshold. The service RRC connection setup delay exceeds the predefined threshold. The outgoing soft handover delay exceeds the predefined threshold.
[0, + )
Nu mb er
After a subscriber starts accessing the network, an exception occurs during the process from the RAB setup starts until the RAB setup is complete. After a subscriber starts accessing the network, an exception occurs during the process from the RAB setup is complete until the alerting message is received. The following delay exceptions might occur when a subscriber attempts to access the network: The call setup delay exceeds the predefined threshold (mobile-originated). The call setup delay exceeds the predefined threshold (mobile-terminated). The call setup delay exceeds the predefined threshold (alerting)(mobile-originated). The call setup delay exceeds the predefined threshold (alerting)(mobile-terminated). The call setup delay exceeds the predefined threshold (mobile-terminated).
N/ A
N/ A
Delay Proble m
N/ A
N/ A
Issue 01 (2013-07-15)
1187
Ra ng e N/ A
U nit N/ A
Description
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. You can set the exception threshold by using the source data subscription function.
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: High Ratio of Bad SQI You can set the exception thresholds by using the source data subscription function.
Initiating the request message for a mobile-originated subscriber to access the network fails.
N/ A
N/ A
Initiating the request message for a mobile-terminated subscriber to access the network fails.
Issue 01 (2013-07-15)
1188
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 RAB Setup Failure Call Drop Ra ng e N/ A U nit N/ A Description Supported NE Version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
After a subscriber starts accessing the network, an exception occurs during the process from the RAB setup starts until the RAB setup is complete. After a subscriber starts accessing the network, an exception occurs during the process from the RAB setup is complete until the alerting message is received. The following delay exceptions might occur when a subscriber attempts to access the network: The call setup delay exceeds the predefined threshold (mobile-originated). The call setup delay exceeds the predefined threshold (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.
N/ A
N/ A
Delay Proble m
N/ A
N/ A
DCCC Rate Increas e Failure DCCC Rate Decrea se Failure Low Downli nk Speed
N/ A
N/ A
Increasing the rate by using Dynamic Channel Configuration Control (DCCC) fails when a subscriber attempts to initiate a call.
BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R014C 00 or later version
N/ A
N/ A
Decreasing the rate by using DCCC fails when a subscriber attempts to initiate a call.
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/Downlink data transfer duration. You are advised to set the exception threshold by using the data source subscription function.
Issue 01 (2013-07-15)
1189
Ra ng e N/ A
U nit N/ A
Description
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. You are advised to set the exception threshold by using the data source subscription function.
MultiRAB Setup Failure MultiRAB Call Drop (Includ ing CS Domai n) MultiRAB Call Drop (Includ ing only PS Domai n)
N/ A
N/ A
Setting up the RAB for a composite service fails when a subscriber attempts to originate a call.
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.
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.
[0, + )
Nu mb er
Issue 01 (2013-07-15)
1190
U nit %
Description
A TP exception occurs when a subscriber attempts to access the network. You are advised to set the exception threshold by using the data source subscription function. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
N/ A
N/ A
A CPICH Ec/N0 exception occurs when a subscriber attempts to access the network. You are advised to set the exception threshold by using the data source subscription function. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
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). You are advised to set the exception threshold by using the data source subscription function. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
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. RRC connection setup delay = Time stamp of the RRC CONN SETUP CMP message Time stamp of the RRC CONN REQ message.
Issue 01 (2013-07-15)
1191
Param eter Overlo ng Servic e RRC Access Delay Overlo ng Outgoi ng Soft Hando ver Delay Overlo ng Incomi ng Soft Hando ver Delay Overlo ng Outgoi ng Hard Hando ver Delay Overlo ng Incomi ng Hard Hando ver Delay Overlo ng Outgoi ng Chann el Hando ver Delay
Issue 01 (2013-07-15)
Ra ng e N/ A
U nit N/ A
Description
The service RRC connection setup delay exceeds the predefined threshold during the RRC connection setup for a mobile-originated call. RRC connection setup delay = Time stamp of the RRC CONN SETUP CMP message Time stamp of the RRC CONN REQ message.
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.
N/ A
N/ A
A subscriber successfully initiates a soft handover when using a specific service but the incoming soft handover delay exceeds the predefined threshold. You can obtain the soft handover delay by using the following formula from the target cell perspective.
N/ A
N/ A
A subscriber successfully initiates a hard handover when using a specific service but the outgoing hard handover delay exceeds the predefined threshold. You can obtain the the hard handover delay by using the following formula from the source cell perspective.
N/ A
N/ A
A subscriber successfully initiates a hard handover when using a specific service but the incoming hard handover delay exceeds the predefined threshold. You can obtain the hard handover delay by using the following formula from the target cell perspective.
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.
1192
Param eter Overlo ng Incomi ng Chann el Hando ver Delay Overlo ng Migrat ion Delay
Ra ng e N/ A
U nit N/ A
Description
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.
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. You are advised to set the exception threshold by using the data source subscription function.
Overlo ng InterSystem Outgoi ng Hando ver (3G to 2G) Delay (IntraSystem ) Overlo ng InterSystem Incomi ng Hando ver (2G to 3G) 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.
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.
Issue 01 (2013-07-15)
1193
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. The call setup duration exceeds the predefined threshold when a mobile-terminated 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-terminated service. The call connection delay exceeds the predefined threshold when a mobile-originated subscriber attempts to access the network. If the first RAB is used 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. The call connection delay exceeds the predefined threshold when a mobile-terminated subscriber attempts to access the network. If the first RAB is used 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.
N/ A
N/ A
N/ A
N/ A
N/ A
N/ A
Issue 01 (2013-07-15)
1194
Ra ng e N/ A
U nit N/ A
Description
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. 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 RAB request time: Time when the universal terrestrial radio access network (UTRAN) receives the RAB Assignment Request message from the CN. You are advised to set the exception threshold by using the data source subscription function.
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. 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. 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. You are advised to set the exception threshold by using the data source subscription function.
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 mobile-terminated subscriber is shorter than the threshold for mobile-terminated short call.
Issue 01 (2013-07-15)
1195
Ra ng e N/ A
U nit N/ A
Description
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. 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. You are advised to set the exception threshold by using the data source subscription function.
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 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. The call setup duration exceeds the predefined threshold when a mobile-terminated subscriber attempts to access the network. If the first RAB is used 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. 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.
N/ A
N/ A
N/ A
N/ A
Issue 01 (2013-07-15)
1196
Param eter Low Downli nk RAB Negoti ated Final Rate Low Averag e Downli nk Throug hput Low Uplink RAB Negoti ated Final Rate Low Averag e Uplink Throug hput
Ra ng e N/ A
U nit N/ A
Description
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.
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/ Downlink data transfer duration.
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.
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.
The system assigns a unique identifier to the bottom subscriber troubled with an exception.
[0, + )
Nu mb er
Number of the exceptions that trouble a subscriber under the cause of a certain type of exceptions.
1197
U nit %
Description
The identity of a bottom problematic cell is in the following format: RNC ID: Cell ID.
N/ A
N/ A
[0, + ]
Nu mb er
Number of the exceptions that occur in a cell under the cause of a certain type of exceptions.
Issue 01 (2013-07-15)
1198
N/ A
Terminal model that is obtained by the terminal type management function based on IMEI-TAC.
BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version BSC6900 V900R013C 00 or later version
[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.
4.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: 1. 2. 3. You have created the following two NE groups in the NE Group Management window: NEgroup1 and NEgroup2. You have selected the two NE groups when creating a UMTS cell performance analysis task. After the task execution is complete, you can find the analysis results of only one NE group.
Issue 01 (2013-07-15)
1199
Cause
The UMTS cell performance analysis results display only the NEs, NE groups, and cells that experience exceptions.
Function Description
Network geographic observation displays the distribution of network coverage, traffic, and exceptions based on data collected from the live network. It replaces traditional drive tests (DTs) and addresses the problem that DTs fail to cover all areas, thereby providing telecom operators with cost-effective network evaluation and problem identification means. UMTS network geographic observation supports network coverage geographic analysis, network traffic geographic analysis, and network event geographic analysis: l 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. 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1200
Issue 01 (2013-07-15)
Function: It displays the traffic distribution of each area on the live network on a map and helps telecom operators identify traffic hot spots. l Network event geographic observation supports the geographic rendering for the following indicators: number of call drops, number of 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.
Application Scenarios
l Network optimization: By providing grid-level analysis on network coverage, traffic, and events at this stage, the system helps identify problems such as weak coverage, intra-system interference and improper network structure and then locates problematic cells through associated grid-cell analysis. This helps to greatly reduce DTs. After the addressed problems are solved, the system allows network optimization engineers to evaluate the network quality before and after the optimization. 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 monitoring and maintenance: By geographically displaying network events at this stage, the system helps network optimization engineers identify areas where exceptions such as call drops and handover failures occur and provides guidance for troubleshooting. Traditional network guarantee and routine problem locating use network performance KPIs to identify and analyze cell-level call drops and handover failures. Exceptions occurred in certain coverage areas of a cell might be ignored because users see only the average KPI values and, if telecom operators fail to pay attention to such exceptions, complaints will arise. By geographically displaying exceptions such as call drops and handover failures on the live network, the system helps network optimization engineers quickly identify areas where exceptions occur frequently. Then, in conjunction with functions such as cell performance analysis and the GIS, the engineers can further locate radio frequency (RF) causes so as to improve user experience of the entire network.
Function Principles
The data source of network geographic observation is the CHR and MR data on the NE side. Figure 4-38 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-18.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1201
Table 4-18 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue an MML comma nd So urc e Nas tar Ser ver Dest inati on eSA U Purpose
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.
eS AU
M20 00
Issue 01 (2013-07-15)
1202
So urc e M2 000
Purpose
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
Issue an applicat ion data subscrip tion comma nd Deliver a datapreproc essing task (direct) Upload preproc essed data (direct)
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eS AU
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the data-preprocessing task.
SA U
eSA U
Issue a data query comma nd Return data query results Issue a task executio n comma nd
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
To deliver 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.
Issue 01 (2013-07-15)
1203
So urc e eS AU
Purpose
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
<= 7 days
Check that you have applied for a valid license for UMTS network geographic observation.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1204
Check that you have the operation rights to subscribe to UMTS network geographic observation data upon login. You are advised to contact the administrator to turn on the data switch because the analysis data subscription function has a high security requirement.
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.
Issue 01 (2013-07-15)
1205
Function 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.
Operation 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 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. You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the 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.
Prerequisite
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1206
l l l
Prerequisite
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.9.2 Preparations for UMTS Network Geographic Observation.
Process
Figure 4-39 shows the analysis process. Figure 4-39 Analysis process
Issue 01 (2013-07-15)
1207
Table 4-20 Description of the network geographic observation process No. (1) Proced ure Check whether analysis data is integrat ed Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Choose Data Type > Network Analysis > UMTS Network Geographic Observation Data(***). *** indicates the data type including MR and CHR. 2. Specify the time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
(2)
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. Click the UMTS 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. 4. On the Basic Subscription Settings tab page, set the data source switch of Network Geographic Observation Data(CHR) and Network Geographic Observation Data(MR) 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.
Issue 01 (2013-07-15)
1208
No.
Description Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. Click the UMTS tab in the Data Subscription Management window. 2. Select the NEs to be configured in the navigation tree. 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 Finish.
Reference
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Choose Data Type > Network Analysis > UMTS Network Geographic Observation Data(***). *** indicates the data type including MR and CHR. 2. Specify the time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
Issue 01 (2013-07-15)
1209
No. (3)
Description Navigation path: Choose Theme Function > Network Analysis > UMTS Network Geographic Observation in the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click UMTS 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. 4. On the Select NE(s) tab page, select the NEs to be analyzed. Then, click Next. 5. Specify the time period. After the task is executed, the Nastar obtains the observation results for the specified time period. 6. Click Finish.
Reference l For details, see 2.7 Creating an Analysis Task. l For details about the parameter s, see Analysis Task Paramete rs.
(4)
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. 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.
l For details, see 2.8 Querying Analysis Results. l For details on the descriptio n of the window for showing analysis results, see 4.9.4 Interface Descripti on: UMTS Network Geograp hic Observat ion.
Issue 01 (2013-07-15)
1210
No. (5)
Description Navigation path: Click the icon on the button area in the upper left part of the Geographic observation window. 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.
Reference l For details, see 2.10 Exportin g Analysis Reports. l For details on the descriptio n of the window for showing analysis results, see 4.9.4 Interface Descripti on: UMTS Network Geograp hic Observat ion.
Issue 01 (2013-07-15)
1211
Parameter PSC Pollute The best cell - the 4th cell RSCP(dB) <Y
Description 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. Y: RSCP difference between the best serving cell and the 4th cell. The default value is 5 dB. CS RSCP (dBm) >=M M: Lower RSCP threshold for CS domain services. When this threshold is exceeded, the system determines that pilot pollution has occurred. The default value is -95 dBm. N: Lower RSCP threshold for PS domain services. When this threshold is exceeded, the system determines that pilot pollution has occurred. The default value is -95 dBm.
Issue 01 (2013-07-15)
1212
Parameter information Parameter Select NE(s) Grid Resolution Settings Description Select RNC or Cell Group, and select the NEs to be analyzed in the navigation tree. 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.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time. 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. 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. The value of this parameter must not precede the end time of Date.
Time information of periodic task Param eter Start time Period Description Date for starting a task. Interval between periodic tasks. Value range: 1 to 7 Days. Note Start Time of a periodic task = Next time point + Delay by (hours) Time period of a periodic task: [Start Time of a periodic task - 1 x Period, Start Time of a periodic task The Next time point is related to Start time and Period. If you set Period to Day, the Next time point is 00 hours:00
1213
Issue 01 (2013-07-15)
Description 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
Note minutes:00 seconds of the next day starting from Start time.
NOTE 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 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 14:00:00, Start time is 01/01/2013, Period is Day, and Delay by (hours) is 3, the Nastar immediately executes the task.
Time delayed for executing a task. Value range: 0 to 24. Unit: hour. If you select this parameter, it works the same as All Busy Time under Busy hours. You are not allowed to set this parameter.
Busy hours
If you set 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.
Navigation Path
Use either of the following methods to open the interface that displays UMTS network geographic observation results: l 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 4-40 shows the interface that displays network geographic observation results on grid maps.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1214
Figure 4-40 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 2.2.3 Interface Description: Geographic Observation Results.
N o. 1
Issue 01 (2013-07-15)
1215
N o. 2
Description 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
l Polygon Areas: enables you to analyze only a selected polygon in the Geographic Observation interface. You can save the cells in a polygon as a cell group. You can analyze multiple KPIs simultaneously based on a polygon. 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 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. 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\plugins\com.huawei.galaxy.geography.ui \style\config\style.
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. 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.
Issue 01 (2013-07-15)
1216
N o.
Item
Description 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.
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. l Displays analysis results in multiple windows. If you click , the Nastar divides the current window into multiple small windows with each small window displaying the analysis results of one KPI. The small windows are zoomed in, zoomed out, and moved simultaneously. If you click the icon again, the Nastar displays the original window. 4 Grid Details area Legend 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. 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. The Nastar distinguishes between directional and omnidirectional cells using different legends. You can change the legend for directional cells. The legend for omnidirectional cells is set the Nastar by default, and therefore you cannot change it. 6 Informatio n area The interface displays no information when it is opened. If you select a grid, the values of selected KPIs in this gird are displayed. If you select a site, information about the site is displayed. If you select a cell, information about the cell such as engineering parameters and longitude and latitude coordinates is displayed.
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. The traffic map is geographically rendered based on the average RSCP value in MRs in the raster view. The traffic map is rendered based on the average received signal quality (RxQual) in MRs in the raster view. The traffic map is rendered based on the percentage of the MRs containing serving cells corresponding to the LAC occurring most frequently to the total number of MRs in the raster view. The traffic map is rendered based on the percentage of MRs in the soft handover state to the total number of MRs in the raster view. If the active set of an MR contains two or more cells, the MR is in the soft handover state.
[-115, -25]
dBm
BSC6900 V900R011C 00 or later version BSC6900 V900R011C 00 or later version BSC6900 V900R011C 00 or later version BSC6900 V900R011C 00 or later version
[-24,0 ]
dB
[0.00, 100.0 0]
[0.00, 100.0 0]
[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. 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.
[0.00, 100.0 0]
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.
Issue 01 (2013-07-15)
1218
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.
[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. 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. 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.
[0, +)
KB
[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. 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.
[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. 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.
BSC6900 V900R014 C00 or later version BSC6900 V900R014 C00 or later version
[0, +)
kbit/ s
Issue 01 (2013-07-15)
1219
Param eter UL PS R99 Traffic Volum e (U) UL PS R99 Throug hput (U) DL PS R99 Traffic Volum e(U) DL PS R99 Throug hput (U)
Rang e [0, +)
Unit
Description
Supported NE Version BSC6900 V900R014 C00 or later version BSC6900 V900R014 C00 or later version BSC6900 V900R014 C00 or later version BSC6900 V900R014 C00 or later version
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. The Nastar collects statistics related to the uplink PS R99 traffic rate over the PDCP layer and displays the statistical results using different distinct colors in the traffic map. The Nastar collects statistics related to the downlink PS R99 traffic over the PDCP layer and displays the statistical results using different distinct colors in the traffic map. The Nastar collects statistics related to the downlink PS R99 traffic rate over the PDCP layer and displays the statistical results using different distinct colors in the traffic map.
[0, +)
kbit/ s
[0, +)
KB
[0, +)
kbit/ s
Num ber
The traffic map is rendered based on the number of call drops in the raster view.
[0, +)
Num ber
The traffic map is rendered based on the number of failed soft handovers in the raster view.
[0, +)
Num ber
The traffic map is rendered based on the number of failed hard handovers in the raster view.
Issue 01 (2013-07-15)
1220
Rang e [0, +)
Unit
Description
Num ber
The traffic map is rendered based on the number of inter-RAT handover failures (UMTS to GSM handover and UMTS to LTE handover) in the raster view.
Function Scenarios
l During network monitoring, 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
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1221
Issue 01 (2013-07-15)
exceptions requires analysis of the whole signaling procedure, you can perform VIP allsignaling analysis on a few VIP subscribers.
Function Description
VIP Report Analysis (GSM/UMTS/LTE/PS Core) The Nastar periodically collects statistics on and analyzes various user assurance KPIs of VIP subscribers and VIP groups, and generates different types of service assurance reports. l Generates KPI reports on the network, CS services, and PS services on the RAN side, and collects statistics on and analyzes the success rate and delay of each key procedure on the CN side. This helps you quickly learn the service usage of VIP subscribers or VIP groups. 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 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 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)
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1222
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-21. Table 4-21 Description of VIP all-signaling analysis Net wor k GS M Number of Supported VIP Subscribers 500 on the entire network. VIP subscribers are managed as Important VIP subscribers by using the VIP group management function. Supported Signaling Range 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. 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). Required NE Version 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. Function Display Mode 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.
Issue 01 (2013-07-15)
1223
Net wor k UM TS
Number of Supported VIP Subscribers 100 on the entire network. VIP subscribers are managed as Important VIP subscribers by using the VIP group management function.
Supported Signaling Range 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.
Required NE Version If you want to view the all signaling information, check that the matching BSC6900 version is V900R013C00 or later.
Function Display Mode For VIP subscribers of Important level who subscribe to all-signaling data, a 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.
Issue 01 (2013-07-15)
1224
Number of Supported VIP Subscribers 500 on the entire network. VIP subscribers are managed as Important VIP subscribers by using the VIP group management function.
Supported Signaling Range Signaling messages on the S1-MME interface (3GPP specifications 36.423), X2 interface (3GPP specifications 36.413), and Uu interface (3GPP specifications 36.331). 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.
Required NE Version LTE3900 V100R008C00 or later; M2000 V200R013C00 or later; HSS9860 V900R008C01 or later. Note: You can analyze the key signaling procedures of common subscribers other than the 500 Important VIP subscribers only in LTE3900 V100R005C00SP C230 or later.
Function Display Mode 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.
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 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1225
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. On the PS Core network, the CHR data includes the SGSN/MME CHR data and the GGSN/SAE-GW CHR data.
Function Principles
Figure 4-41 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-22.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1226
Issue 01 (2013-07-15)
1227
Table 4-22 Description of VIP analysis User Oper ation 1. Subscr ibe to basic data Scen e GSM / UMT S netw ork Proce dure Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd Upload raw data PS Core netw ork Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd Sour ce Nast ar Serv er Dest inati on eSA U Purpose
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 a basic data subscription command to the eSAU.
eSA U
M20 00
M20 00
BSC/ RNC
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
eSA U
To turn on the data source switch on the NE side. After a user enables the basic data subscription function (PS Core VIP analysis) on the Nastar client, the Nastar issues a basic data subscription command to the eSAU.
eSA U
M20 00
M20 00
SGS N/ MM E
To forward the MML command to the NE, requesting the NE to generate raw data.
Issue 01 (2013-07-15)
1228
Scen e
Purpose
Issue a basic data subscri ption comma nd Issue a subscri ption comma nd Forwar d the subscri ption comma nd Upload raw data
eSA U
To turn on the data source switch on the NE side. After a user enables the basic data subscription function (LTE VIP analysis) on the Nastar client, the Nastar issues a basic data subscription command to the eSAU.
eSA U
M20 00
M20 00
eNod eB
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNod eB/ MM E
l To upload 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 transmission switch is enabled.
Issue 01 (2013-07-15)
1229
Proce dure Issue an applica tion data subscri ption comma nd Deliver a dataprepro cessing task (direct) Upload prepro cessed data (direct)
Purpose
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 a data-processing command to the eSAU.
eSA U
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the datapreprocessing task.
SAU
eSA U
Issue an applica tion data subscri ption comma nd Deliver a dataprepro cessing task (direct) Upload prepro cessed data (direct)
Nast ar Serv er
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function (PS Core VIP analysis) on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eSA U
PS SAU
To deliver a data-preprocessing request to the PS SAU, requesting the PS SAU to start the datapreprocessing task.
PS SAU
eSA U
Issue 01 (2013-07-15)
1230
Proce dure Issue an applica tion data subscri ption comma nd Deliver a prepro cessing task (direct) Upload prepro cessed data (direct)
Purpose
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function (LTE VIP analysis) on the Nastar client, the Nastar issues a data-processing command to the eSAU.
eSA U
LTE SAU
To deliver a data-preprocessing task to the LTE SAU, requesting the LTE SAU to start the datapreprocessing task.
LTE SAU
eSA U
To upload preprocessed data to the eSAU after obtaining the data from LTE SAU to Trace Server, and preprocessing .
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. To return data integrity check results to the Nastar server and display the results on the Nastar client. To deliver 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. To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server.
Nast ar Serv er
eSA U
Nasta r Serve r
Issue 01 (2013-07-15)
1231
Scen e -
Sour ce -
Purpose
Number of analysis tasks to be created Period that can be analyzed (for periodic task) Time range of analysis data
l Once tasks <= 300, for all RATs. l Period tasks <= 60, for all RATs. 30 minutes, 1 to 24 hours, 1 to 7 days, and 1 week
l <= 7 days (for one-time task) l <= 30 days (for periodic task)
Before running a VIP analysis task, you must check and prepare the following information: l l l Checking the License Information and User Rights Preparing Basic Data Checking the Data Source Environment
Required rights (Security > Security Management > User) l Function operation rights Operation Rights > Operation > Nastar Subject Management > LTE FDD VIP Analysis Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM VIP analysis.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > PS Core VIP Analysis Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM VIP analysis.
GSM VIP analysis UMTS VIP analysis LTE TDD VIP analysis LTE FDD VIP analysis PS Core VIP analysis
l Function operation rights Have both involved licenses of VIP Analysis Operation Rights of combined analysis. l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM VIP analysis.
Issue 01 (2013-07-15)
1234
Table 4-24 Required basic data of VIP analysis Data Type Config uratio n Data (Mand atory) Function The configuration data of the NE controlling the 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 which subscribers have handed over. Operation If the OSS information has been already configured, the Nastar automatically collects and imports the configuration data after the OSS and NE information is configured. You can also manually collect the configuration data before the specified time period starts. After the configuration data is imported, you can choose Maintenance > Data Maintenance Management to check whether the configuration data is available in the Nastar database. For detailed information about collecting, importing, and checking, see 2.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 NOTE of configuration data due to network adjustment. If you only perform the PS Expired configuration data may cause incorrect cell Core VIP analysis, you do information in the analysis result. For detailed not need the configuration operations, see Checking Engineering Parameters data. and Configuration Data. VIP Infor matio n (Mand atory) VIP information includes VIP user and IMSI information. Before subscribing to VIP analysis data, create a VIP group to centrally monitor the service of quality for multiple VIP users in one VIP group. For details, see 2.4.6 Managing VIP Groups or VIP Users (VIP Analysis).
NOTE Generally, you obtain the IMSI and MSISDN of a VIP user and enter them into the Nastar. If telecom operators have high requirements for user information security and the anonymous policy is enabled on the network where the Nastar is deployed, all user information such as IMSI, MSISDN, and IMEI contained in the analysis data will be encrypted. To protect the security-sensitive user information, the Nastar no longer allows you to enter the plaintext IMSI and MSISDN. In this situation, you need to contact telecom operators to obtain the encrypted IMSI. The Nastar does not support the encrypted MSISDN. Telecom operators can visit http://support.huawei.com and choose Software Center > Controlled Tool(Mini-tool Software) > Core Network Product Line > Wireless-OSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt user 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 2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key.
Issue 01 (2013-07-15)
1235
Function 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.
Operation 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 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.
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. 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.
You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
For details, see 2.4.10 Setting a Mailbox and Address List for Sending Analysis Reports (Optional).
Issue 01 (2013-07-15)
1236
For the required NE versions and M2000 versions of the signaling tracing analysis, refer to Table 3-26.
Table 4-25 Description of the data source environment Net wor k GSM Description
l GSM RAN CS analysis : Check that the matching M2000 version is V200R011C00 (or later), and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l GSM RAN PS analysis: Check that the matching M2000 version is V200R012C00 (or later), and the NE version is BSC6900 V900R014C00 (or later), and BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On the User Identity Information Reporting Switch (GSM) in Nastar Commissioning Guide.
UM TS
l Check that the matching M2000 version is V200R011C00SPC220 or later and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(UMTS) > Turning On the User Identity Information Reporting Switch (UMTS) in Nastar Commissioning Guide.
LTE
l Check that the matching M2000 version is M2000 V200R012C00SPC200 or later, the NE version is LTE3900 V100R005C00SPC320 (or later) or LTE3900 V100R008C00SPC020 (or later), and the MME on the CN must be provided by Huawei and the version is USN9810 V900R011C01SPC300 or later.
NOTE 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 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. 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. 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.
Issue 01 (2013-07-15)
1237
Description
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 M2000 versions are consistent with the following information: NE version: USN9810 V900R011C01, USN9810 V900R011C02, USN9810 V900R012C00; UGW9811 V900R009C01, UGW9811 V900R009C02, UGW9811 V900R010C00. M2000 version: M2000 V200R011C01, M2000 V200R012C01, M2000 V200R013C00.
Prerequisites
You have finished the preparation of VIP analysis, such as checking the operation rights, preparing the basic data, and so on. For details, see 3.9.2 Preparations for VIP Analysis.
Procedure
Figure 4-42 shows the analysis process.
Issue 01 (2013-07-15)
1238
Issue 01 (2013-07-15)
1239
Table 4-26 Description of VIP analysis procedures No. Procedure Description Reference for Detailed Operatio ns 2.6 Checking the Integrity of Analysis Data
(1)
Navigation path: Choose Maintenance > Data Maintenance Management 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. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
1240
No.
Procedure
Description
(2)
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the *** tab. *** indicates the network type. 2. In the left navigation tree, select the NEs to be configured. 3. On the Basic Subscription Settings tab page, click Set. 4. In the displayed Basic Subscription Settings dialog box, set 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 3.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.
l If you want to view the all signaling information when viewing deep analysis results, click select the interface about All Signaling. ,
l If you want to view the all signaling information when viewing deep analysis results, , For the GSM/UMTS network, click select the interface about All Signaling.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1241
No.
Procedure
Description
For the LTE network, choose the important level VIP users on the VIP analysis tab page of the application subscription function, and the system will prompt you to start the all signaling trace. 5. Click Confirm. Check that the data switch is successfully turned on by viewing the displayed information in the Log Info area. Subscribe to analysis data (application ) Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the *** tab. *** indicates the network type. 2. In the left navigation tree, select the NEs to be configured. 3. On the VIP analysis tab page, click ON. 4. Select the VIP user(s) and the NE(s). The level of a VIP user determines the type of data that a VIP user subscribe to. Define the user level through the VIP group management function. 5. Click Confirm. Check that data is successfully subscribed by viewing the displayed information in the Log Info area.
Issue 01 (2013-07-15)
1242
No.
Procedure
Description
Reference for Detailed Operatio ns 2.6 Checking the Integrity of Analysis Data
Navigation path: Choose Maintenance > Data Maintenance Management 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. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
(3)
Navigation path: Choose Theme Function > User Assurance > VIP Analysis in the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click the VIP Analysis node. 2. Set the task name and task remarks. Click Next. 3. On the Analysis Type tab page, set the net type and the data type(s). 4. On the Select NE(s) tab page, select a NE. 5. On the VIP Group tab page, select the VIP group (s) to be analyzed. 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. 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.
l For details, see 2.7 Creati ng an Analysi s Task. l For details about the paramet ers, see Analysi s Task Param eters.
Issue 01 (2013-07-15)
1243
No.
Procedure
Description
(4)
l For details, see 2.8 Queryi ng Procedure: Analysi 1. Double-click an analysis result of the task. s 2. In the displayed VIP Analysis window, click the Results User Level Results tab to view the VIP summary . analysis results. l For details View Navigation path: icon in the Deep Analysis on the analysis parameter of the VIP summary analysis results. descript results - VIP ion of Procedure: deep the analysis window icon in the Deep Analysis parameter of the 1. Click for VIP summary analysis results. showin NOTE g If the analysis object is VIP group, click icon to enter analysis the analysis result window that the analysis object is VIP results, user. If you want to enter the deep analysis window, you see need click icon again. 3.9.4 Refere 2. In the displayed Deep Analysis Result_*** nce for window, view the in-depth analysis results. VIP Navigation path: In the upper right area of the Analysis View Analysi Task Management window, select an analysis task in analysis s results - VIP the Finish state. In the lower right of the Task Result Interfa area, select a result record of the task. active cells ce. analysis Procedure: View analysis results - VIP summary analysis Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. 1. Double-click an analysis result of the task. 2. In the displayed VIP Analysis window, click the Network Level Results: Active Cell tab to view the analysis results of cells where VIP users are active.
Issue 01 (2013-07-15)
1244
No.
Procedure
Description
View analysis results - VIP active servers analysis (only support the GSM network) View analysis results - VIP trend analysis
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click an analysis result of the task. 2. In the displayed VIP Analysis window, click the Network Level Results: Active Server tab to view the analysis results of servers where VIP users are active. Navigation path: In the upper right area of the Analysis Task Management window, select a periodic task in the Finish state. In the lower right of the Task Result area, select a result record of the task. 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 01 (2013-07-15)
1245
No.
Procedure
Description
Reference for Detailed Operatio ns l For details, see 2.10 Export ing Analysi s Report s. l For details on the descript ion of the window for showin g analysis results, see Interfa ce Descri ption: VIP Analysi s/InDepth Analysi s/ Geogra phic Display .
(5)
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the button area. 2. Specify the export path and export content. 3. Click Save.
Issue 01 (2013-07-15)
1246
Description 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 The name is unique and case-sensitive and cannot be empty. l Task Name must be named in Chinese or English. Otherwise, the function of distributing analysis results by emails is unavailable.
Type of an analysis task to be created. Description of the task. Value range: The name contains a maximum of 200 characters.
Parameter information Parameter Analysis Type Analysis Scene Description 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 Data Type 1 Set the RAT for an NE. The system supports the following RATs: GSM, UMTS, LTE FDD, LTE TDD. Both access methods can be chosen. Set the data type on the RAN side. l RAN CS Data Access: Analyzes the CS service based on the CS-related data on the RAN side. The LTE network does not involve this parameter. l RAN CS Data Access: Analyzes the PS service based on the PS-related data on the RAN side. Both access methods can be chosen.
NOTE If you set the analysis scene to PS Core, you do not need to set the data type, because it only supports the PS data on the PS Core.
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 01 (2013-07-15)
1247
Description Click Select to select an NE. 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.
Indicates the name of a VIP group. Indicates the number of members in the VIP group. Indicates the description of a VIP group. Indicates the last time the VIP group information is updated.
Issue 01 (2013-07-15)
1248
Description Indicates the RAT of a VIP group. Indicates the domain of an NE. Domains include signaling plane-CS, signaling plane-PS, signaling planeintegration. 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. 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 Criterion Threshold Indicates the name of a KPI indicator. The indicators are displayed on the analysis result window. Indicates the relationship between the KPI value and KPI abnormal 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.
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 users 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).
Process Threshold
Network Domain
Indicates the RAT of a VIP group. Indicates the domain of an NE. Domains include signaling plane-CS, signaling plane-PS, signaling planeintegration.
Issue 01 (2013-07-15)
1249
Description 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. 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 process threshold. The threshold is based on the process of obtaining the final values of KPI indicators. Indicates the relationship between the KPI value and KPI abnormal threshold. Indicates the abnormal threshold of a KPI. In the analysis report of the corresponding task, if the KPI value of a subscriber reaches the threshold, this KPI is considered as a problematic KPI or deteriorating KPI. Click the unit and enter the KPI abnormal threshold. This parameter can be empty. That is, no threshold value is provided.
Criterion Threshold
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time.
Issue 01 (2013-07-15)
1250
Parameter Delay
Description 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. The value of this parameter must not precede the end time of Date.
Time information of periodic task Param eter Start time Period Description Date for starting the task. Interval between periodic tasks. 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. Value range: 0 to 9999 Delay by (hours) Whole day Time delayed for executing a task. Value range: 0 to 24. Unit: hour. If this parameter is set, it works the same as All Busy Time under Busy hours. You are not allowed to set this parameter. Note Start Time of a periodic task = Next time point + Delay by (hours) Time period of a periodic task: [Start Time of a periodic task - 1 x Period, Start Time of a periodic task The Next time point is related to Start time and Period. l If you set Period to Minute, the Next time point is 00 seconds of the next minute starting from the current server time (minutelevel). For example, if the current server time is 01:10, the Next time point is 02:00 starting from Start time. l If you set Period to Hour, the Next time point is 00 minutes:00 seconds of the next hour starting from the current server time (hour-level). For example, if the current server time is 14:01:10, the Next time point is 15:00:00 starting from Start time. l If you set Period to Day, the Next time point is 00 hours:00 minutes:00 seconds of the next day starting from Start time. l If you set Period to Week, the Next time point is 00 hours:00 minutes:00 seconds of the eighth day starting from Start time.
Issue 01 (2013-07-15)
1251
Description 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.
Note
NOTE 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 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 14:00:00, Start time is 01/01/2013, Period is Day, and Delay by (hours) is 3, the Nastar immediately executes the task.
Parameters about sending the analysis report Parameter Sendin g Analysi s Reports Setting Automatically send analysis reports via emails Target email Email subject Description After you select this option, the system delivers the exported VIP analysis result file to the mailboxes of the specified users.
Indicates the recipient's mailbox. Click Select. In the displayed Email dialog box, set user mailboxes. 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.
Issue 01 (2013-07-15)
1252
Parameter Attachment
Description 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 reports by the email directly. l If the actual attachment is larger than the configured threshold, you can obtain the analysis reports by the FTP. Obtain the FTP information. The information will be sent to you by the email. Includes: IP address of the Nastar server (if the hardware is ATAE, the IP address is the one of the master board), FTP user and password, port number, and the analysis report path ( the default path is /export/home/sysm/ nastar/report). Prepare the tool that supports sftp for downloading the analysis reports. The Huawei supports the psftp tool. The path and the operation of the psftp tool is referred to FAQs > FAQs About the SUSE Linux Operating System > How Do I Transfer Data by Using the PSFTP Client? in the Nastar Commissioning Guide.
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.
Open the interface that displays the results of VIP analysis (in-depth): On the User Level Results tab page of VIP analysis result interface, If the table displays the counter overview information by group, click in the front
of each row, or click the counter value underlined in red (for example, ) directly. The tab page for the counter overview information by user is displayed. You can view the counter value for each user in the group. In such a case, click in the front of each row, or click the counter value underlined
in red (for example, ) directly. In-depth analysis of selected counters is started. For details, see 3.10.4 Reference for Complaint Analysis Support Interface. l Open the geographic display interface: On the button area of VIP analysis result interface, click .
Main Window
Figure 4-43 shows the VIP analysis results window. Figure 4-43 VIP analysis interface (example for a GSM network)
Issue 01 (2013-07-15)
1254
No. 1
Parameter Description Button area The buttons provide navigation paths to the following three functions. l : Exports VIP analysis summary reports. 1. Click , a dialog box that provides personal data disclaimer will be displayed, reminding you of the illegality if you possess the personal data. Click OK. 2. On the displayed dialog box, set the result (Exception or ALL), service type, and report type. Click Next. 3. Set the report save path and the folder name, click Save to export the analysis reports. All the exported reports are contained in a folder named VIP Analysis_Name of analysis task_YYYYMMDDHHMMSS by default. VIP analysis reports are named following the format of Number Report type_Report categories 1 + Report categories 2 + Number_Service type.csv. Report categories 1 indicates the analysis object, such as the group and user of the user-level analysis. Report categories 2 indicates the analysis result categories, such as counter overview information table (KPI) and active cell information table (cell) of the user-level analysis. For example, 01 User Level Results_groupKPI00_RAN NET.csv indicates the counter overview information table of the user-level analysis, according the analysis object is group, and the service type is RAN NET. l : Displays the VIP analysis results geographically. For details, see Geographic Display Interface. l : Starts VIP trend analysis. Only periodical tasks support trend analysis. For details, see Interface Description: VIP Trend Analysis.
Issue 01 (2013-07-15)
1255
No. 2
Parameter Description 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.
Issue 01 (2013-07-15)
1256
No. (1)
Parameter
Description
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)
(3)
Counter set Contains a counter set to be analyzed. selection area The Nastar defines a default counter set by analysis scenario. 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
(4)
underlined in red (for example, ) directly. The tab page for the counter overview information by user is displayed. You can view the counter value for each user in the group. l In such a case, click in the front of each row, or click the counter
value underlined in red (for example, ) directly. In-depth analysis of selected counters is started. For details, see 3.10.4 Reference for Complaint Analysis Support Interface. (5) Active cell information table Displays active cells of a selected VIP user object.
Issue 01 (2013-07-15)
1257
No. (6)
Parameter
Description
Active server Displays active servers of a selected VIP user object. It is only information supported by the GSM network. table
No. (1)
Parameter
Description
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 01 (2013-07-15)
1258
No. (2)
Parameter
Description
NOTE The RAN-CS and RAN-PS types cannot be chosen at the same time.
(3)
Counter set Contains a counter set to be analyzed. selection area The Nastar defines a default counter set by analysis scenario. Counter overview information table Active VIP subscriber information table Lists all counter values in different applications for the selected NE object based on the selected counter set.
(4)
(5)
Issue 01 (2013-07-15)
1259
No. (1)
Description 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) Service type selection area Select a service type to be viewed.
NOTE Only the RAN-PS service is supported.
(3)
Contains a counter set to be analyzed. The Nastar defines a default counter set by analysis scenario.
(4)
Counter overview Lists all counter values in different applications for the selected information table analysis object based on the selected counter set. Active VIP Displays VIP subscribers for selected server objects. subscriber information table
(5)
Issue 01 (2013-07-15)
1260
No. (1)
Description Navigation path for basic operations in the Geographic Observation window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
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 01 (2013-07-15)
1261
No. (3)
(4) (5)
This area is empty for VIP analysis. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the icons in area 3.
(6)
Information 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.
VIP trend analysis is supported by the GSM, UMTS, LTE, and PS Core network.
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 when monitoring and optimizing VIP KPIs. Figure 4-48 shows the VIP trend analysis results.
Issue 01 (2013-07-15)
1262
No. 1
Parameter Description 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 01 (2013-07-15)
1263
No. 2
Parameter Description Area for setting filtering criteria Selects a VIP user or VIP group whose trend analysis is to be analyzed. The options 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.
Select the service type whose trend analysis is to be viewed. Only one service type can be selected each time.
Issue 01 (2013-07-15)
1264
No. 5
Parameter Description Trend analysis chart Displays the trend analysis charts of multiple counters for a selected subscriber during a time segment. l Displays user objects and time dimension 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. 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.
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.
The trend analysis modes are as follows: l Real-time monitoring 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.
Issue 01 (2013-07-15)
1265
Common
Param eter Deep Analysi s Rang e N/A Unit N/A Description 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. 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 IMSI N/A N/A N/A N/A Name of a VIP group. International mobile subscriber identity (IMSI) of a VIP subscriber. Alias of a VIP subscriber. Query the name of a VIP subscriber using VIP group management based on the IMSI of the VIP subscriber. Type approval code (TAC) in international mobile equipment identity (IMEI) of the UE used by a VIP subscriber. 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. Service type for a counter. Number of abnormal counters whose values exceed the result thresholds that engineers set during analysis task creation. Number of reports generated when a user accesses the network. BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Alias
N/A
N/A
IMEITAC
N/A
N/A
Termin al Model
N/A
N/A
N/A [0, +)
[0, +)
Num ber
Issue 01 (2013-07-15)
1266
RAN-NET/Accessibility Evaluation
Parameter Access Requests(IntraRAT) Access Failures (Intra-RAT) Range [0,+) Unit Numbe r Numbe r Description Number of access requests that a VIP subscriber initiates from a cell in the current system. Number of access failures that a VIP subscriber experiences from a cell in the current system. 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 = Number of RRC connection setup failures (service) + (Number of RAB setup failures for AMR + Number of RAB setup failures for VP + Number of RAB setup failures for PS R99 + Number of RAB setup failures for HSDPA + Number of RAB setup failures for HSUPA + Number of RAB setup failures for HSPA Number of times that the first RAB setup after an incoming intra-RAT handover fails) Access Requests(InterRAT) [0,+) Numbe r Number of access requests that a VIP subscriber initiates from a cell in another system. BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Issue 01 (2013-07-15)
1267
Range [0,+)
Unit Numbe r
Description Number of access failures that a VIP subscriber experiences from a cell in another system. Number of failed access requests (inter-RAT) = Number of failed service requests initiated by a specified UE that has gained access to a system of another RAT = Number of incoming interRAT handover failures that this UE experiences on the entire network + Number of times that the first RAB setup after an incoming inter-RAT handover fails)
[0,3069 ] [0,+)
N/A
Average TP value when a VIP subscriber gains access to the network. Number of times that theTP value is abnormal upon network access. Set the exception threshold when you create a task. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
Numbe r
[0.00,10 0.00]
Proportion of abnormal TP values that a VIP subscriber experiences upon network access. Proportion of abnormal TP values = Number of abnormal TP values/Number of TP values x 100%
[-115,-2 5]
dBm
Average RSCP value when a VIP subscriber gains access to the network.
Issue 01 (2013-07-15)
1268
Range [0,+)
Unit Numbe r
Description Number of times that the RSCP value is abnormal upon network access. Set the exception threshold when you create a task. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
[0.00,10 0.00]
Proportion of abnormal RSCP values that a VIP subscriber experiences upon network access. Proportion of abnormal RSCP values = Number of abnormal RSCP values/Number of RSCP values x 100%
[-24,0]
dB
Average Ec/No value when a VIP subscriber gains access to the network. Number of times that the Ec/No value is abnormal upon network access. Set the exception threshold when you create a task. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
[0,+)
Numbe r
[0.00,10 0.00]
Proportion of abnormal Ec/No values that a VIP subscriber experiences upon network access. Proportion of abnormal Ec/No values = Number of abnormal Ec/No values/Number of Ec/No values x 100%
Issue 01 (2013-07-15)
1269
Range [0,+)
Unit Numbe r
Description Number of non-service RRC connection setup requests initiated by a VIP subscriber. RRC is short for radio resource control. 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.
RRC Setup Failures(NonService) RRC Setup Success Rate (Non-Service) RRC Setup Requests (Service) RRC Setup Failures (Service) RRC Setup Success Rate (Service) RRC Setup Failures (Service-CS) RRC Setup Success Rate (Service-CS) RRC Setup Failures (Service-PS) RRC Setup Success Rate (Service-PS)
[0,+)
Numbe r %
Number of non-service RRC connection setup failures after network access. Success rate of non-service RRC connection setups after network access. Number of service RRC connection setup requests after network access. Number of service RRC connection setup failures after network access. Success rate of service RRC connection setups after network access. Number of CS RRC connection setup failures after network access. Success rate of CS RRC connection setups after network access. Number of PS RRC connection setup failures after network access. Success rate of PS RRC connection setups after network access.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Numbe r Numbe r %
[0,+)
Numbe r %
Numbe r %
[0.00,10 0.00]
Issue 01 (2013-07-15)
1270
[0,+)
Numbe r
[0.00,10 0.00]
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Numbe r
[0,+)
Numbe r
Call Setup Success Rate (MTC) Call Connection Acknowledgme nt Success Times(Alerting) (MOC)
[0.00,10 0.00]
[0,+)
Numbe r
Issue 01 (2013-07-15)
1271
Parameter Call Connection Acknowledgme nt Success Rate (Alerting) (MOC) Call Connection Acknowledgme nt Success Times(Alerting) (MTC) Call Connection Acknowledgme nt Success Rate (Alerting) (MTC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MOC)
Unit %
Description Rate of call connection acknowledgment (alerting) successes of a VIP subscriber who accesses the network and uses the CS service as the mobile-originated party. Number of successful call connection acknowledgments (alerting) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Success rate of call connection acknowledgments (alerting) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Number of successful call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-originated party. The connection acknowledgment (Connect Ack) process spans from the RRC connection setup request to the Connect Ack message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
[0,+)
Numbe r
[0.00,10 0.00]
[0,+)
Numbe r
[0.00,10 0.00]
Success rate of call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-originated party.
Issue 01 (2013-07-15)
1272
Range [0,+)
Unit Numbe r
Description Number of successful call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Success rate of call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Number of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-originated party. The call success process spans from the RRC connection setup request to the Disconnect message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
Call Connection Acknowledgme nt Success Rate (Connect Ack) (MTC) Call Success Times(MOC)
[0.00,10 0.00]
[0,+)
Numbe r
[0.00,10 0.00]
Success rate of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-originated party. Number of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-terminated party. Success rate of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-terminated party.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Numbe r
[0.00,10 0.00]
Issue 01 (2013-07-15)
1273
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
RAN-NET/PDP Evaluation-PS
Parameter PDP Activation Requests Range [0,+) Unit Number Description Number of PDP activation requests that a VIP subscriber initiates to access the network and use the PS service. Number of PDP activation failures that a VIP subscriber experiences during the process of attempting to access the network and use the PS service. Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
Issue 01 (2013-07-15)
1274
Unit %
Description Success rate of PDP activation requests that a VIP subscriber initiates to access the network and use the PS service.
RAN-NET/Retainability Evaluation
Parameter Release Times (Intra-RAT) Range [0,+) Unit Number Description Number of times that a VIP subscriber releases all services in the current system. Releases(Intra-RAT) = Access Requests(Intra-RAT) - Access Failures(Intra-RAT) Abnormal Release Times (Intra-RAT) [0,+) Number Number of times that a VIP subscriber abnormally releases all services in the current system. Abnormal Release Times(IntraRAT) = Number of AMR RAB abnormal releases + Number of VP RAB abnormal releases + Number of PS R99 RAB abnormal releases + Number of HSDPA RAB abnormal releases + Number of HSUPA abnormal releases + Number of HSPA abnormal releases Number of the first RAB abnormal releases after interRAT incoming handover occurs. Release Times (Inter-RAT) [0,+) Number Number of times that a VIP subscriber releases all services in another system. Releases(Inter-RAT) = Access Requests(Inter-RAT) Access Failures(Inter-RAT) BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1275
Range [0,+)
Unit Number
Description Number of times that a VIP subscriber abnormally releases all services in another system. Abnormal Release Times(InterRAT) = Number of times that the first RAB after an incoming inter-RAT handover is abnormally released.
[0,+)
Number
Number of times that a VIP subscriber releases all RRC connections during the process of using a service. Number of times that a VIP subscriber abnormally releases all RRC connections during the process of using a service.
[0,+)
Number
RAN-NET/Delay Evaluation
Parameter RRC Setup Success Times (Non-Service) Range [0,+) Unit Number Description Number of successful nonservice RRC connection setups upon successful call initiation. Number of successful RRC connection setups (non-service) = Number of RRC connection setup requests (non-service) Number of RRC connection setup failures (non-service) = Number of valid RRC connection setup delays (nonservice) Average RRC Setup Delay (Non-Service) N/A Second Average delay for non-service RRC connection setup upon successful call initiation. RRC connection setup delay = Time when the RRC CONN SETUP CMP message is generated Time when the RRC CONN REQ message is generated. BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1276
Range [0,+)
Unit Number
Description Number of overlong delays for non-service RRC connection setup upon successful call initiation. Set the overlong delay threshold when you create a task.
Proportion of Overlong RRC Setup Delay (Non-Service) RRC Setup Success Times (Service)
[0.00,1 00.00]
Proportion of delays for nonservice RRC connection setup in all overlong delays upon successful call initiation. Number of successful service RRC connection setups upon successful call initiation. Number of service RRC 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.
[0,+)
Number
[0,+)
Second
Average delay for service RRC connection setup upon successful call initiation. RRC connection setup delay = Time when the RRC CONN SETUP CMP message is generated Time when the RRC CONN REQ message is generated.
[0,+)
Number
Number of overlong delays for service RRC connection setup upon successful call initiation. Set the overlong delay threshold when you create a task.
[0.00,1 00.00]
Proportion of overlong delays for service RRC connection setup in all overlong delays upon successful call initiation.
Issue 01 (2013-07-15)
1277
RAN-NET/Mobility Evaluation
Parameter Soft Handover Requests Range [0,+) Unit Number Description Number of soft handover requests that a VIP subscriber initiates during the process of using a service. Number of soft handover failures that a VIP subscriber experiences during the process of using a service. Success rate of soft handovers (including softer handovers) that a VIP subscriber initiates during the process of using a service. Number of hard handover requests that a VIP subscriber initiates during the process of using a service. Number of hard handover failures that a VIP subscriber experiences during the process of using a service. Success rate of hard handovers that a VIP subscriber initiates during the process of using a service. Average soft handover delay during the process for a VIP subscriber to use a service. Average hard handover delay during the process for a VIP subscriber to use a service. Number of outgoing handover requests (from a UMTS network to another network) initiated by a UE. Number of outgoing handover requests (from a UMTS network to a GSM network) initiated by a VIP subscriber. Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0.00,1 00.00]
[0,+)
Number
[0,+)
Number
[0.00,1 00.00]
Average Soft Handover Delay Average Hard Handover Delay Inter-RAT Outgoing Handover Requests Inter-RAT Outgoing Handover Requests (UMTS to GSM)
[0,+)
Second
[0,+)
Second
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1278
Parameter Inter-RAT Outgoing Handover Requests (UMTS to LTE) Inter-RAT Outgoing Handover Failures Inter-RAT Outgoing Handover Failures(UMTS to GSM) Inter-RAT Outgoing Handover Failures(UMTS to LTE) Inter-RAT Incoming Handover Requests Inter-RAT Incoming Handover Requests(GSM to UMTS) Inter-RAT Incoming Handover Requests(LTE to UMTS) Inter-RAT Incoming Handover Failures Inter-RAT Incoming Handover Failures(GSM to UMTS)
Range [0,+)
Unit Number
Description Number of outgoing handover requests (from a UMTS network to an LTE network) initiated by a VIP subscriber. Number of outgoing handover failures (from a UMTS network to another network) experienced by a VIP subscriber. Number of outgoing handover failures (from a UMTS network to a GSM network) experienced by a VIP subscriber. Number of outgoing handover failures (from one UMTS network to another LTE network) experienced by a UE. Number of inter-RAT handover requests (from another network to a UMTS network) initiated by a VIP subscriber. Number of inter-RAT handover requests (from a GSM network to a UMTS network) initiated by a VIP subscriber. Number of inter-RAT handover requests (from an LTE network to a UMTS network) initiated by a VIP subscriber. Number of inter-RAT handover failures (from another network to a UMTS network) experienced by a VIP subscriber. Number of inter-RAT handover failures (from a GSM network to a UMTS network) experienced by a VIP subscriber.
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1279
Parameter Inter-RAT Incoming Handover Failures(LTE to UMTS) Average InterRAT Outgoing Handover Delay
Range [0,+)
Unit Number
Description Number of inter-RAT handover failures (from an LTE network to a UMTS network) experienced by a VIP subscriber. Average delay for outgoing interRAT handover recorded by the current system. Outgoing inter-RAT handover delay = Time when the IU RELEASE COMMAND message is generated Time when the RELOCATION REQUIRED message is generated.
[0,+)
Second
Average InterRAT Outgoing Handover Delay (UMTS to GSM) Average InterRAT Outgoing Handover Delay (UMTS to LTE) Average InterRAT Incoming Handover Delay
[0,+)
Second
[0,+)
Second
Average delay for UMTS-toLTE handover recorded by the current system. Average delay for incoming inter-RAT handover recorded by the current system. Incoming inter-RAT handover delay = Time when the UTRAN MOBILITY INFORMATION CONFIRM message is generated Time when the RELOCATION REQUIRED message is generated.
[0,+)
Second
Average InterRAT Incoming Handover Delay (GSM to UMTS) Average InterRAT Incoming Handover Delay (LTE to UMTS)
[0,+)
Second
[0,+)
Second
Issue 01 (2013-07-15)
1280
Range [0,+)
Unit Number
RAN-CS/AMR/Accessibility Evaluation
Parameter RAB Setup Requests Range [0,+) Unit Number Description Number of RAB setup requests initiated by a VIP subscriber. RAB is short for radio access bearer. RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate [0,+) Number Number of RAB setup failures experienced by a VIP subscriber. Number of times that a VIP subscriber successfully initiates an RAB setup request. RAB setup success rate after network access. RAB setup success rate (%) = Number of successful RAB setups/Number of RAB setup requests x 100%. Call Connection Acknowledgme nt Success Times(Alerting) Call Connection Acknowledgme nt Success Times(Connect Ack) [0,+) Number Number of times that a VIP subscriber hears the alerting upon successful call initiation. Number of times that a VIP subscriber hears the peer ends' voice upon successful call initiation. Supported NE Version BSC6900 V900R013C00 or later version
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
Issue 01 (2013-07-15)
1281
Range [0,+)
Unit Number
Description 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.
RAN-CS/AMR/Retainability Evaluation
Parameter RAB Setup Success Times Abnormal RAB Release Times Range [0,+) Unit Number Description See RAB Setup Success Times in RAN-CS/VP/Accessibility Evaluation Number of times that the RAB is abnormally released after a VIP subscriber gains access to the network and successfully initiates a call. Abnormal RAB release rate after a VIP subscriber gains access to the network and successfully initiates a call. Abnormal RAB release rate (%) = Number of abnormal RAB releases/Number of successful call setups x 100%. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,10 0.00]
RAN-CS/AMR/Delay Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Number Description Number of successful RAB setups during call initiation, that is, number of RAB setup delays. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1282
Range [0,+)
Unit Second
Description Average RAB setup delay during the process for a VIP subscriber to initiate a call. Average RAB setup delay (s) = Sum of RAB setup delays/ Number of RAB setup delays. RAB setup delay = RAB setup request connection acknowledge time RAB setup request time. Statistical point for RAB setup request connection acknowledge time: When the RAB assignment procedure is successful, namely, when the SRNC sends a Radio Access Bearer Assignment Response message to the CN after it receives an RAB setup connection acknowledge message. Statistical point for RAB setup request time: When the UTRAN receives a Radio Access Bearer Assignment Request message from the CN.
[0,+)
Number
Number of times that the RAB BSC6900 setup delay is overlong during V900R013C00 the process for a VIP subscriber or later version to initiate a call. Set the exception threshold when you create a task.
[0.00,10 0.00]
Proportion of RAB setup delays in all overlong delays. Proportion of RAB setup delays (%) = Number of overlong RAB setup delays/Number of RAB setup delays x 100% = Number of overlong RAB setup delays/ Number of successful RAB setups x 100%.
[0,+)
Number
Number of times that the call setup delay of the mobileoriginated party upon successful call initiation is overlong.
Issue 01 (2013-07-15)
1283
Parameter Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC)
Range [0,+)
Unit Second
Description Average call setup delay of the mobile-originated party upon successful call initiation. Number of times that the call setup delay of the mobileoriginated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,10 0.00]
Proportion of overlong call setup delays of the mobileoriginated party upon successful call initiation. Proportion of overlong call setup delays (mobileoriginated) (%) = Number of overlong call setup delays (mobile-originated)/Number of call setup delays (mobileoriginated) x 100% = Number of overlong call setup delays (mobile-originated)/Number of successful RRC connection setups x 100%.
[0,+)
Number
Number of times that the call setup delay of the mobileterminated party upon successful call initiation is overlong. Average call setup delay of the mobile-terminated party upon successful call initiation. Number of times that the call setup delay of the mobileterminated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
Average Call Setup Delay (MTC) Overlong Call Setup Delay Times(MTC)
[0,+)
Second
[0,+)
Number
Issue 01 (2013-07-15)
1284
Unit %
Description Proportion of overlong call setup delays of the mobileterminated party upon successful call initiation. Proportion of overlong call setup delays (mobileterminated) (%) = Number of overlong call setup delays (mobile-terminated)/Number of call setup delays (mobileterminated) x 100% = Number of overlong call setup delays (mobile-terminated)/Number of successful RRC connection setups x 100%.
Call Connection Acknowledgme nt Success Times(Alerting) (MOC) Average Call Connection Acknowledgme nt Delay (Alerting) (MOC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MOC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MOC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MOC)
[0,+)
Number
Number of times that the mobile-originated party hears the alerting upon successful call initiation. Average alerting delay of the mobile-originated party upon successful call initiation.
[0,+)
Second
[0,+)
Number
Number of times that the alerting delay of the mobileoriginated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0.00,10 0.00]
Proportion of overlong alerting delays experienced by the mobile-originated party upon successful call initiation.
[0,+)
Number
Number of call connection acknowledgment (Connect Ack) delays experienced by the mobile-originated party upon successful call initiation.
Issue 01 (2013-07-15)
1285
Parameter Average Call Connection Acknowledgme nt Delay (Connect Ack) (MOC) Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MOC)
Range [0,+)
Unit Second
Description Average call connection acknowledgment (Connect Ack) delay of the mobileoriginated party upon successful call initiation. Number of times that the call connection acknowledgment (Connect Ack) delay of the mobile-originated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0,+)
Number
Proportion of Overlong Call Connection Acknowledgme nt Delay (Connect Ack) (MOC) Call Connection Acknowledgme nt Success Times(Alerting) (MTC) Average Call Connection Acknowledgme nt Delay (Alerting) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MTC)
[0.00,10 0.00]
Proportion of overlong call connection acknowledgment (Connect Ack) delays experienced by the mobileoriginated party upon successful call initiation. Number of times that the mobile-terminated party hears the alerting upon successful call initiation. Average call connection acknowledgment (alerting) delay of the mobile-terminated party upon successful call initiation. Number of times that the call connection acknowledgment (alerting) delay of the mobileterminated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0,+)
Number
[0,+)
Second
[0,+)
Number
Issue 01 (2013-07-15)
1286
Parameter Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MTC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MTC) Average Call Connection Acknowledgme nt Delay (Connect Ack) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MTC)
Unit %
Description Proportion of overlong call connection acknowledgment (alerting) delays experienced by the mobile-terminated party upon successful call initiation.
[0,+)
Number
Number of successful call connection acknowledgments (Connect Ack) experienced by the mobile-terminated party upon successful call initiation. Average call connection acknowledgment (Connect Ack) delay of the mobileterminated party upon successful call initiation. Number of times that the call connection acknowledgment (Connect Ack) delay of the mobile-terminated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
Proportion of call connection acknowledgment (Connect Ack) delays experienced by the mobile-terminated party upon successful call initiation.
Issue 01 (2013-07-15)
1287
Range [0,+)
Unit Second
Description Average RAB duration upon successful call initiation. 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
[0,+)
Number
Number of times that the RAB duration is below the threshold for short RAB duration upon successful call initiation. Set the exception threshold when you create a task.
[0,+)
Second
Average call duration of calls initiated by a VIP subscriber. Number of short calls upon successful call initiation. The mechanism for calculating the number of short calls adds the condition that short calls are initiated by the mobileoriginated party.
[0,+)
Number
Issue 01 (2013-07-15)
1288
Unit %
Description Proportion of short calls upon successful call initiation. The mechanism for calculating the proportion of short calls adds the condition that short calls are initiated by the mobileoriginated party.
[0,+)
Second
Average call duration of calls initiated by a VIP subscriber. Number of short calls upon successful call initiation. The mechanism for calculating the number of short calls adds the condition that short calls are initiated by the mobileterminated.
[0,+)
Number
[0.00,10 0.00]
Proportion of short calls upon successful call initiation. The mechanism for calculating the proportion of short calls adds the condition that short calls are initiated by the mobileterminated.
RAN-CS/AMR/Quality Evaluation
Parameter Call Setup Success Times Downlink OneWay Audio Times Range [0,+) Unit Number Description Number of times that a VIP subscriber successfully initiates a call setup request. Number of calls with downlink one-way audio problems. Downlink one-way audio problems are detected by the RNC. [0.00,10 0.00] % Proportion of Downlink OneWay Audio = Downlink OneWay Audio Times/RAB Setup Successes x 100% Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
Issue 01 (2013-07-15)
1289
Range [0,+)
Unit Number
Description Number of calls with uplink one-way audio problems. Uplink one-way audio problems are detected by the RNC.
[0.00,10 0.00]
Proportion of Uplink One-Way Audio = Uplink One-Way Audio Times/RAB Setup Successes x 100% Number of calls with static problems. Static problems are detected by the RNC.
[0,+)
Number
Noise Proportion
[0.00,10 0.00]
Proportion of calls with static problems. Proportion of calls with static problems (%) = Number of calls with static problems/Number of connected calls (Connect Ack) x 100%.
Issue 01 (2013-07-15)
1290
Range [0,+)
Unit Number
Description Number of signal quality indicator (SQI) reports generated during a call. 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. 2. The RNC collects statistics on the average SQI value and divides signal quality into different levels according to SQI values: RAN14.0: Excellent (SQI<= (400,500]), Good (SQI<= (300,400]), Accept (SQI<= (200,300]), Poor (SQI<= (100,200]), Bad (SQI<= [0,100]). RAN13.0 and earlier: Good (SQI <= (300,500]), Accept (SQI <= (200,300]), Bad (SQI <=(0,200]). You can modify the segment intervals of levels by running the SET USQICOUNT command on the RNC.
Average SQI
[0,+)
N/A
Average SQI value in the SQI reports generated during a call. 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. Set the exception threshold when you create a task.
Abnormal SQIs
[0,+)
Number
Issue 01 (2013-07-15)
1291
Unit %
Description Proportion of calls with abnormal SQI values. Proportion of calls with abnormal SQI values (%) = Number of calls with abnormal SQI values/Number of connected calls (Connect Ack) x 100%.
[0.00,10 0.00]
Proportion of calls whose SQI is Excellent during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Good during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Accept during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Poor during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Bad during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of level 1 uplink BLER values upon successful call initiation. BLER is short for block error rate. This parameter is applicable only to the AMR service. Standard for level 1: 00.78%.
Issue 01 (2013-07-15)
1292
Unit %
Description Proportion of level 2 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 2: 0.78% 1.56%.
[0.00,10 0.00]
Proportion of level 3 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 3: 1.56% 3.12%
[0.00,10 0.00]
Proportion of level 4 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 4: 3.12% 6.24%.
[0.00,10 0.00]
Proportion of level 5 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 5: 6.24% 12.48%.
[0.00,10 0.00]
Proportion of level 6 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 6: above 12.48%.
Issue 01 (2013-07-15)
1293
RAN-CS/VP/Accessibility Evaluation
Parameter RAB Setup Requests RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate Call Connection Acknowledgme nt Success Times(Alerting) Call Connection Acknowledgme nt Success Times(Connect Ack) Abnormal Release Times Before Connection Acknowledgme nt Range [0,+) Unit Number Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
Number
[0,+)
Number
[0,+)
Number
RAN-CS/VP/Retainability Evaluation
Parameter RAB Setup Success Times Abnormal RAB Release Times Range [0,+) Unit Number Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
Issue 01 (2013-07-15)
1294
Unit %
RAN-CS/VP/Delay Evaluation
Parameter RAB Setup Success Times Average RAB Setup Delay Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Average Call Setup Delay (MTC) Range [0,+) Unit Number Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Second
[0,+)
Number
Number
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR".
[0,+)
Second
Issue 01 (2013-07-15)
1295
Parameter Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay (MTC) Call Connection Acknowledgme nt Success Times(Alerting) (MOC) Average Call Connection Acknowledgme nt Delay (Alerting) (MOC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MOC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MOC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MOC) Average Call Connection Acknowledgme nt Delay (Connect Ack) (MOC)
Range [0,+)
Unit Number
Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0.00,10 0.00]
[0,+)
Number
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
[0,+)
Second
Issue 01 (2013-07-15)
1296
Parameter Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MOC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Connect Ack) (MOC) Call Connection Acknowledgme nt Success Times(Alerting) (MTC) Average Call Connection Acknowledgme nt Delay (Alerting) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MTC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MTC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MTC)
Range [0,+)
Unit Number
[0.00,10 0.00]
[0,+)
Number
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
Issue 01 (2013-07-15)
1297
Parameter Average Call Connection Acknowledgme nt Delay (Connect Ack) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MTC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Connect Ack) (MTC) Average RAB Service Duration Overshort RAB Service Duration Times Average Service Duration(MOC) Number of Short Calls (MOC) Proportion of Short Calls (MOC) Average Service Duration(MTC) Number of Short Calls (MTC)
Range [0,+)
Unit Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Second
Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR".
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0,+)
Second
[0,+)
Number
Second
[0,+)
Number
Issue 01 (2013-07-15)
1298
Unit %
RAN-CS/SMS/Accessibility Evaluation
Parameter Setup Requests (MOC) Setup Failures (MOC) Setup Success Rate (MOC) Setup Requests (MTC) Setup Failures (MTC) Setup Success Rate (MTC) Range [0,+) Unit Number Description Number of SMS service setup requests initiated by the mobileterminated party. Number of failed SMS service setups initiated by the mobileoriginated party. Number of successful SMS service setups initiated by the mobile-originated party. Number of SMS service setup requests initiated by the mobileterminated party. Number of failed SMS service setups initiated by the mobileterminated party. Number of successful SMS service setups initiated by the mobile-terminated party. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
Number
[0,+)
Number
[0.00,10 0.00]
Issue 01 (2013-07-15)
1299
[0,+)
[0.00,1 00.00]
[0,+)
[0.00,1 00.00]
Issue 01 (2013-07-15)
1300
Issue 01 (2013-07-15)
1301
Parameter Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong RAB Setup Delay Times(MOC)
Range [0, +)
Unit Numb er
Description Number of times that the call setup delay of the mobile-originated party upon successful call initiation is overlong. Average call delay of the mobileoriginated party upon successful call initiation. Number of times that the call setup delay of the mobile-originated party upon successful call initiation is overlong. Set the overlong delay threshold when you create a task.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0, +) [0, +)
Secon d Numb er
[0.00,1 00.00]
Proportion of overlong call setup delays of the mobile-originated party upon successful call initiation. Proportion of overlong call setup delays (mobile-originated) = Number of overlong call setup delays (mobile-originated)/ Number of call setup delays (mobile-originated) x 100% = Number of overlong call setup delays (mobile-originated)/ Number of successful RRC connection setups x 100%.
[0, +)
Numb er
Number of times that the call setup delay of the mobile-terminated upon successful call initiation is abnormal.
Issue 01 (2013-07-15)
1302
Range [0, +)
Unit Secon d
Description Average call setup delay of the mobile-terminated upon successful call initiation. Average call setup delay =Sum of call setup delays/Number of call setup delays. Call setup delay = RAB request connection acknowledge time Signaling access time. Statistical point for RAB request connection acknowledge time: When the RAB assignment procedure is successful, namely, when the SRNC sends a Radio Access Bearer Assignment Response message to the CN after it receives an RAB setup connection acknowledge message. Statistical point for signaling access time: When an RRC SETUP REQ or RELOC REQ message is received or when an incoming inter-RAT handover request is initiated.
[0, +)
Numb er
Number of times that the call setup delay of the mobile-terminated party upon successful call initiation is overlong. Set the overlong delay threshold when you create a task.
[0.00,1 00.00]
Proportion of overlong call setup delays experienced by the mobileterminated party upon successful call initiation. Proportion of overlong call setup delays = Number of overlong call setup delays/Number of call setup delays x 100% = Number of overlong call setup delays/Number of successful RRC connection setups x 100%.
Issue 01 (2013-07-15)
1303
Range [0, +)
Unit Secon d
Description Average RAB duration upon successful call initiation. 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. Statistical point for RAB request connection acknowledge time: When the RAB assignment procedure is successful, after receiving an RAB setup connection acknowledge message, the SRNC sends a Radio Access Bearer Assignment Response message to the CN.
Issue 01 (2013-07-15)
1304
Parameter Downlink Traffic Volume Average Downlink Transmission Duration Average Downlink Throughput
Unit KB
Description Downlink traffic volume of all common PS services. Average downlink transmission duration for all common PS services. Average downlink throughput for all common PS services. Average downlink throughput = Downlink traffic volume/ Downlink data transmission duration.
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
Second
[0.00, +)
kbit/s
[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. Set the exception threshold when you create a task.
Uplink Traffic Volume Average Uplink Transmission Duration Average Uplink Throughput
KB
Uplink traffic volume for all common PS services. Average uplink transmission duration for all common PS services. Average uplink throughput rate for all common PS services. Average uplink throughput = Total uplink traffic volume/Total uplink transmission duration
BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
Second
kbit/s
[0, +)
Numbe r
Number of times that among all common PS services, the average uplink throughput for one RAB setup is below a threshold for low average uplink throughput. Set the exception threshold when you create a task.
Issue 01 (2013-07-15)
1305
Issue 01 (2013-07-15)
1306
Unit %
Description Proportion of level 6 uplink BLER values upon successful call initiation. This parameter is applicable only to the PS service. Standard for level 6: 12.48% < X.
RAN-PS/HSDPA/Accessibility Evaluation
Parameter RAB Setup Requests RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate Rang e [0, +) [0, +) [0, +) [0.00,1 00.00] Unit Numbe r Numbe r Numbe r % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RAN-PS/HSDPA/Retainability Evaluation
Parameter RAB Setup Success Times Abnormal RAB Release Times Abnormal RAB Release Rate Rang e [0, +) [0, +) [0.00, 100.00 ] Unit Numbe r Numbe r % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1307
RAN-PS/HSDPA/Delay Evaluation
Parameter RAB Setup Success Times Average RAB Setup Delay Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Average Call Setup Delay (MTC) Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay (MTC) Rang e [0, +) [0, +) [0, +) [0.00, 100.00 ] [0, +) [0, +) [0, +) [0.00, 100.00 ] [0, +) [0, +) [0, +) [0.00, 100.00 ] Unit Numbe r Second Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Numbe r %
Numbe r Second
Numbe r %
Numbe r Second
Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Numbe r %
Issue 01 (2013-07-15)
1308
Rang e [0, +)
Unit Second
RAN-PS/HSDPA/Rate Evaluation
Parameter Downlink Traffic Volume Average Downlink Transmission Duration Average Downlink Throughput Low Average Downlink Throughput Times Average HSDPA Downlink Rate Low Average HSDPA Downlink Rate Times Rang e [0, +) [0, +) Unit KB Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Second
[0.00, +) [0, +)
kbit/s
Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Numbe r
[0.00, +) [0, +)
kbit/s
Average downlink rate for all HSDPA services. Number of times that the average downlink rate for all HSDPA services is low. Set the threshold for low average rate when you create a task.
Numbe r
Average HSDPA Downlink Rate with Sufficient Resources Times of Low Average HSDPA Downlink Rate with Sufficient Resources
[0.00, +)
kbit/s
Average downlink rate for all HSDPA services when service resources are sufficient.
[0, +)
Numbe r
Number of times that the average downlink rate for all HSDPA services is low when service resources are sufficient. Set the threshold for low average rate when you create a task.
Issue 01 (2013-07-15)
1309
Parameter Average HSDPA Downlink Rate with Insufficient Resources Times of Low Average HSDPA Downlink Rate with Insufficient Resources
Rang e [0.00, +)
Unit kbit/s
Description Average downlink rate for all HSDPA services when service resources are insufficient.
[0, +)
Numbe r
Number of times that the average downlink rate for all HSDPA services is low when service resources are insufficient. Set the threshold for low average rate when you create a task.
RAN-PS/HSUPA/Accessibility Evaluation
Parameter RAB Setup Requests RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate Rang e [0, +) [0, +) [0, +) [0.00,1 00.00] Unit Numbe r Numbe r Numbe r % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RAN-PS/HSUPA/Retainability Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Numbe r Description Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1310
Range [0,+)
Unit Numbe r %
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0.00,1 00.00]
RAN-PS/HSUPA/Delay Evaluation
Parameter RAB Setup Success Times Average RAB Setup Delay Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Range [0,+) Unit Numb er Secon d Numb er % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
[0,+)
[0,+)
[0,+)
[0.00,1 00.00]
[0,+)
Numb er
Issue 01 (2013-07-15)
1311
Parameter Average Call Setup Delay (MTC) Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay Average RAB Service Duration
Range [0,+)
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Secon d
RAN-PS/HSUPA/Rate Evaluation
Parameter Uplink Traffic Volume Range [0,+) Unit KB Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Second
[0.00,+)
kbit/s
[0,+)
Number
Issue 01 (2013-07-15)
1312
RAN-PS/HSPA/Accessibility Evaluation
Parameter RAB Setup Requests Range [0,+) Unit Number Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
[0.00,100.00]
RAN-PS/HSPA/Retainability Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Number Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,100.00]
Issue 01 (2013-07-15)
1313
RAN-PS/HSPA/Delay Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Number Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Second
Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Average Call Setup Delay (MTC)
[0,+)
Number
[0.00,100.00]
[0,+)
Number
[0,+)
Second
[0,+)
Number
[0.00,100.00]
[0,+)
Number
[0,+)
Second
Issue 01 (2013-07-15)
1314
Parameter Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay (MTC) Average RAB Service Duration
Range [0,+)
Unit Number
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0.00,100.00]
[0,+)
Second
RAN-PS/HSPA/Rate Evaluation
Parameter Downlink Traffic Volume Range [0,+) Unit KB Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
Average Downlink Transmission Duration Average Downlink Throughput Low Average Downlink Throughput Times Uplink Traffic Volume
[0,+)
Second
[0.00,+)
kbit/s
[0,+)
Number
[0,+)
KB
[0,+)
Second
Issue 01 (2013-07-15)
1315
Range [0.00,+)
Unit kbit/s
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0, + )
N Number of RAB setup failures u where multiple RABs are accessed m during a call. b e r
Issue 01 (2013-07-15)
1316
U Description n i t % Setup success rate for accessing multiple RABs during a call.
Supported NE Version
Mul tiRA B Rele ase Tim es Abn orm al Mul tiRA B Rele ase Tim es
[ 0 , + )
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.
Issue 01 (2013-07-15)
1317
Par am eter
R a n g e [ 0 . 0 0 , 1 0 0 . 0 0 ]
U Description n i t % Abnormal RAB release rate for releasing multiple RABs that contain at least one CS RAB at a time during a call.
Supported NE Version
Mul tiRA B Rele ase Tim es Abn orm al Mul tiRA B Rele ase Tim es
[ 0 , + )
N u m b e r
Number of abnormal RAB releases where multiple RABs that contain only PS RABs are released during a call.
Issue 01 (2013-07-15)
1318
Par am eter
R a n g e [ 0 . 0 0 , 1 0 0 . 0 0 ]
U Description n i t % Abnormal RAB release rate for releasing multiple RABs that contain only PS RABs during a call.
Supported NE Version
Active Cell/Common
Paramete r RNC ID Range [0,4095] Unit N/A Description ID of the RNC to which an active cell belongs. Name of the RNC to which an active cell belongs. ID of an active cell. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
[0,65535]
N/A
Cell Name
N/A
N/A
Service Type
N/A
N/A
Issue 01 (2013-07-15)
1319
Number of nonBSC6900 service setup V900R013C00 or requests that a VIP later version group or VIP subscriber initiates in an active cell. 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. Set the exception threshold when you create a task. BSC6900 V900R013C00 or later version
[0,+)
Number
[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.
[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. Set the exception threshold when you create a task.
Issue 01 (2013-07-15)
1320
Range [0,+)
Unit Number
Description
Supported NE Version
Number of nonBSC6900 service setup V900R013C00 or requests that a VIP later version group or VIP subscriber initiates in an active cell. Number of service BSC6900 setup requests that V900R013C00 or a VIP group or VIP later version subscriber initiates in an active cell. Number of service setup failures that a VIP group or VIP subscriber experiences in an active cell. BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1321
[0,+)
Numbe r
[0,+)
Numb er
Issue 01 (2013-07-15)
1322
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1323
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1324
[0,+)
Numbe r
[0,+)
Number
Number of PS BSC6900 service setup V900R013C00 or failures that a VIP later version group or VIP subscriber experiences in an active cell.
Issue 01 (2013-07-15)
1325
[0,+)
Numbe r
[0,+)
Number
Issue 01 (2013-07-15)
1326
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1327
[0,+)
Number
Common
Paramet er Deep Analysis Ran ge N/A Unit Description Supported NE Version BSC6900 V900R013 C00 or later version
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. 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
Issue 01 (2013-07-15)
Paramet er User ID
Ran ge N/A
Unit
Description
Supported NE Version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version
N/A
ID of a VIP subscriber. Query the ID of a VIP subscriber using VIP group management.
Alias
N/A
N/A
Alias of a VIP subscriber. Query the alias of a VIP subscriber using VIP group management.
IMEITAC
N/A
International mobile equipment identity-type allocation code (IMEI-TAC) of the terminal used by a VIP subscriber.
Terminal Model
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. Service type for a following counter.
Service Type
N/A
N/A
[0, +)
Numb er
Number of abnormal counters whose values exceed the predefined thresholds that you set when creating a task. Number of reports generated when a subscriber accesses the network.
[0, +)
Numb er
Issue 01 (2013-07-15)
1329
RAN-CS/NET/Accessibility Evaluation
Para meter Acces s Reque sts (IntraRAT) Acces s Failur es (IntraRAT) Acces s Reque sts (InterRAT) Acces s Failur es (InterRAT) Avera ge TA on Acces s Abnor mal TAs on Acces s Ratio of Abnor mal TAs on Acces s Ran ge [0, +) Unit Number Description Number of access requests that a VIP subscriber initiates to access the network from a cell in the current system. Supported NE Version BSC6900 V900R013C00 or later version
[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.
[0, +)
Number
Number of access requests that a VIP subscriber initiates to access the network from a cell in another system.
[0, +)
Number
Number of access failures that a VIP subscriber experiences during the process of accessing the network from a cell in another system.
[0,63 ]
N/A
Average TA value when a VIP subscriber initiates channel setup requests for accessing the network.
[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.
[0.00, 100.0 0]
Proportion of abnormal TA values when a VIP subscriber initiates channel setup requests for accessing the network. Proportion of abnormal TA values = Number of abnormal TA values/Number of all TA values x 100%.
Issue 01 (2013-07-15)
1330
Para meter Avera ge RAC H Level on Acces s Abnor mal RAC H Levels on Acces s Ratio of Abnor mal RAC H Levels on Acces s
Unit dBm
Description Average RACH level when a VIP subscriber initiates channel setup requests for accessing the network.
[0, +)
Number
Number of times that the RACH level is abnormal when a VIP subscriber initiates channel setup requests for accessing the network. Set the exception threshold when you create a task.
[0.00, 100.0 0]
Proportion of abnormal RACH levels when a VIP subscriber initiates channel setup requests for accessing the network. Proportion of abnormal RACH levels = Number of abnormal RACH levels/ Number of all RACH levels x 100%.
RAN-CS/NET/Retainability Evaluation
Para mete r Relea ses (Intra RAT) Abno rmal Relea ses (Intra RAT) Rang e [0, +) Unit Description Supported NE Version BSC6900 V900R013C 00 or later version
Numb er
Number of times that a VIP subscriber releases all services in the current system. Number of releases (intra-RAT) = Access requests (intra-RAT) Access failures (intraRAT)
[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.
Issue 01 (2013-07-15)
1331
Para mete r Relea ses (Inter RAT) Abno rmal Relea ses (Inter RAT)
Rang e [0, +)
Unit
Description
Numb er
Number of times that a VIP subscriber releases all services in another system. Number of releases (inter-RAT) = Access requests (inter-RAT) Access failures (interRAT)
[0, +)
Numb er
Number of times that a VIP subscriber abnormally releases all services successfully accessed from another system. 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.
RAN-CS/NET/Mobility Evaluation
Paramet er Hard Handover Requests Hard Handover Failures Hard Handover Success Times InterRAT Outgoing Handover Requests InterRAT Outgoing Handover Failures (Normal Release) Range [0,+) Unit Num ber Num ber Num ber Description Number of hard handover requests that a VIP subscriber initiates. Number of hard handover failures that a VIP subscriber experiences. Number of times that a VIP subscriber successfully initiates a hard handover. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
[0,+)
[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. Number of times that an outgoing inter-RAT handover from a GSM network is triggered during a service but the handover fails and the VIP subscriber then is handed back over to the GSM network.
[0,+)
Num ber
Issue 01 (2013-07-15)
1332
Paramet er InterRAT Outgoing Handover Failures (Abnorm al Release) InterRAT Incoming Handover Requests InterRAT Incoming Handover Failures
Range [0,+)
Description Number of times that call drops occur during an outgoing inter-RAT handover from a GSM network during a service.
[0,+)
Num ber
Number of times that a handover from a non-GSM cell to a GSM cell is triggered during a service.
[0,+)
Num ber
Number of times that a handover from a non-GSM cell to a GSM cell fails during a service.
RAN-CS/Call/Accessibility Evaluation
Param eter Total Call Setup Reques ts Ran ge [0, +) Unit Numb er Description Number of call setup requests that a VIP subscriber initiates to access the network and initiate a call. That is, the number of Channel Request messages from a VIP subscriber after the BSC obtains the IMSI correctly. [0, +) Numb er Number of call setup failures that a VIP subscriber experiences during the process of accessing the network and initiating a call. The call setup process spans from the Channel Request message to the Altering message. 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. The process before call setup spans from the Channel Request message to the Connect Acknowledge message. BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1333
Ran ge [0, +)
Unit Numb er
Description Number of successful call setups when a VIP subscriber accesses the network and initiates a call. The call setup process spans from the Channel Request message to the Alerting message.
[0, +)
Numb er
Number of successful call completions (Alerting) when a VIP subscriber accesses the network and initiates a call. The call completion (Alerting) process spans from the Channel Request message to the Altering message.
[0, +)
Numb er
Number of successful call completions (Connect Ack) after a subscriber accesses the network and initiates a call. The call completion process (Connect Ack) spans from the Channel Request message to the Connect Acknowledge message.
Call Compl etion Succes s Rate (Alerti ng) Call Compl etion Succes s Rate (Conne ct Ack)
Call completion rate (Alerting) when a VIP subscriber accesses the network and initiates a call. Call completion rate (Alerting) = Number of successful call completions (Alerting)/ Number of call setup requests x 100%
Call completion rate (Connect Ack) when a VIP subscriber accesses the network and initiates a call. Call completion rate (Connect Ack) = Number of successful call completions/ Number of call setup requests x 100%
RAN-CS/Call/Retainability Evaluation
Parame ter Call Setup Success Times Rang e [0, +) Unit Num ber Description Number of successful call setups when a VIP subscriber accesses the network and initiates a call. The call setup process spans from the Channel Request message to the Alerting message.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1334
Issue 01 (2013-07-15)
Parame ter Call Complet ion (Connec t Ack) Abnorm al Call Releases
Rang e [0, +)
[0, +)
Num ber
Number of times that the call is abnormally released when a VIP subscriber accesses the network and initiates a call. After a successful call setup, any of the following indicates an abnormal call release: 1. The Disconnect message is called an abnormal one. 2. The BSS receives the Clear Command message from the MSC and the abnormal call release is caused by the network or the calling (or called) VIP subscriber. 3. An outgoing inter-BSC handover fails. 4. An intra-BSC handover fails. 5. The BSC releases the channel resources abnormally. 6. The MSC releases the channel resources abnormally.
[0.00, 100.00 ]
Abnormal call release rate when a VIP subscriber accesses the network and initiates a call. Abnormal call release rate = Number of abnormal call releases/Number of successful call completions (Connect Ack) x 100%
Issue 01 (2013-07-15)
1335
[0, +)
Issue 01 (2013-07-15)
1336
Unit %
Description Proportion of overlong access delays upon successful call initiation (mobileterminated call). Proportion of overlong access delays = Number of overlong access delays/ Number of access delays x 100%
Times of Call Complet ion Delay (Alertin g) (MOC) Average Call Complet ion Delay (Alertin g) (MOC) Overlon g Call Complet ion Delays (Alertin g) (MOC) Ratio of Overlon g Call Complet ion Delays (Alertin g) (MOC)
[0, +)
Numbe r
Number of times that the completion (Alerting) delay is overlong upon successful call initiation (mobileoriginated call). The call completion (Alerting) process spans from the Channel Request message to the Altering message.
[0, +)
Second
Average call completion (Alerting) delay upon successful call initiation (mobile-originated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
[0, +)
Numbe r
Number of times that the call completion (Alerting) delay is overlong upon successful call initiation (mobileoriginated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Alerting) delays upon successful call initiation (mobile-originated call). Proportion of overlong call completion delays = Number of overlong call completion (Alerting) delays/Number of call completion delays x 100%
Issue 01 (2013-07-15)
1337
Parame ter Average Call Complet ion Delay (Connec t Ack) (MOC) Overlon g Call Complet ion Delays (Connec t Ack) (MOC) Ratio of Overlon g Call Complet ion Delays (Connec t Ack) (MOC) Times of Call Complet ion Delay (Alertin g) (MTC) Average Call Complet ion Delay (Alertin g) (MTC)
Ran ge [0, +)
Unit Second
Description Average call completion (Connect Ack) delay upon successful call initiation (mobile-originated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
[0, +)
Numbe r
Number of times that the call completion (Connect Ack) delay is overlong upon successful call initiation (mobile-originated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Connect Ack) delays upon successful call initiation (mobile-originated call). Proportion of overlong call completion delays = Number of overlong call completion delays/Number of call completion delays x 100%
[0, +)
Numbe r
Number of times that the call completion (Alerting) delay is overlong upon successful call initiation (mobileterminated call). The call completion (Alerting) process spans from the Channel Request message to the Alerting message.
[0, +)
Second
Average call completion (Alerting) delay upon successful call initiation (mobile-terminated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
Issue 01 (2013-07-15)
1338
Parame ter Overlon g Call Complet ion Delays (Alertin g) (MTC) Ratio of Overlon g Call Complet ion Delays (Alertin g) (MTC) Average Call Complet ion Delay (Connec t Ack) (MTC) Overlon g Call Complet ion Delays (Connec t Ack) (MTC) Ratio of Overlon g Call Complet ion Delays (Connec t Ack) (MTC)
Ran ge [0, +)
Unit Numbe r
Description Number of times that the call completion (Alerting) delay is overlong upon successful call initiation (mobileterminated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Alerting) delays upon successful call initiation (mobile-terminated call). Proportion of overlong call completion delays = Number of overlong call completion delays/Number of call completion delays x 100%
[0, +)
Second
Average call completion (Connect Ack) delay upon successful call initiation (mobile-terminated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
[0, +)
Numbe r
Number of times that the call completion (Connect Ack) delay is overlong upon successful call initiation (mobile-terminated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Connect Ack) delays upon successful call initiation (mobile-terminated call). Proportion of overlong call completion delays = Number of overlong call completion delays/Number of call completion delays x 100%
Issue 01 (2013-07-15)
1339
Ran ge [0, +)
Unit Second
Description Average duration of successful calls for the mobile-originated party. 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
[0, +)
Numbe r
Number of short calls for the mobileoriginated party during a successful call. 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. 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).
[0.00 , 100.0 0]
Average duration of successful calls for the mobile-originated party. 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
[0, +)
Second
Average duration of successful calls for the mobile-terminated party. 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
Issue 01 (2013-07-15)
1340
Ran ge [0, +)
Unit Numbe r
Description Number of short calls for the mobileterminated party during a successful call. 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. 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).
[0.00 , 100.0 0]
Proportion of short calls for the mobileterminated party during a successful call. Proportion of short calls = Number of short calls/Number of calls with valid call durations x 100%
Issue 01 (2013-07-15)
1341
Ran ge [0, +)
Description Number of times that one-way audio occurs in the downlink during calls. 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 Um and A interfaces. Principle for detecting one-way audio occurs in the downlink: The DSP in the DTRU of the BTS performs periodic statistics on the bad frame rate based on downlink TRAU frames. When the bad frame rate reaches the predefined threshold, the BSS determines that primary one-way audio occurs in the downlink and starts the mechanism for confirming the occurrence of primary one-way audio in the downlink. During this process, the BSC sends a message to the TC demanding that the TC send a test TRAU frame to the BTS. If the BTS fails to receive the test TRAU frame from the TC within a specified time period, one-way audio occurs on the downlink voice channel.
Proportion of successful call setups where one-way audio occurs in the downlink in all successful call setups. Proportion of successful call setups where one-way audio occurs in the 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%
Issue 01 (2013-07-15)
1342
Ran ge [0, +)
Description Number of times that one-way audio occurs in the uplink during calls. 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 Um and A interfaces. Principle for detecting one-way audio in the uplink: The DSP in the TC of the BSC performs periodic statistics on the bad frame rate based on uplink TRAU frames. When the bad frame rate reaches the predefined threshold, the BSS determines that primary 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.
Proportion of successful call setups where one-way audio occurs in the uplink in all successful call setups. Proportion of successful call setups where one-way audio occurs in the uplink in all successful call setups = Number of times that one-way audio occurs in the uplink/Number of successful call setups (Connect Ack) x 100%
[0, +)
Num ber
Number of times that no audio occurs in both the uplink and downlink during calls.
Issue 01 (2013-07-15)
1343
Unit %
Description Proportion of successful call setups where one-way audio occurs in both the uplink and downlink in all successful call setups. Proportion of successful call setups where one-way audio occurs in both the uplink and downlink in all successful call setups = Number of successful call setups where one-way audio occurs in both the uplink and downlink/Number of successful call setups (Connect Ack) x 100%
[0, +)
Num ber
Number of times that crosstalk occurs in the downlink during calls. 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.
Proportion of successful call setups where crosstalk occurs in the downlink in all successful call setups. Proportion of successful call setups where crosstalk occurs in the downlink in all successful call setups = Number of successful call setups where crosstalk occurs in the downlink/Number of successful call setups (Connect Ack) x 100%
Issue 01 (2013-07-15)
1344
Ran ge [0, +)
Description Number of times that crosstalk occurs in the uplink during calls. 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 uplink crosstalk: The DSP of the BTS inserts the unique identifier of a call into the free bits of uplink speech TRAU frames. The DSP of the TC decodes the unique call identifier and checks its consistency. If inconsistency is detected within the test period, crosstalk occurs in the uplink.
Proportion of successful call setups where crosstalk occurs in the uplink in all successful call setups. Proportion of successful call setups where crosstalk occurs in the uplink in all successful call setups = Number of successful call setups where crosstalk occurs in the uplink/Number of successful call setups (Connect Ack) x 100%
Average value of downlink HQIs after the call setup is successful. 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 reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008 version: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
Issue 01 (2013-07-15)
1345
Ran ge [0, +)
Description Number of times that the uplink HQI is poor after the call setup is successful. Set the exception threshold when you create a task.
Average value of uplink high quality indicators (HQIs) after the call setup is successful. 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 reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008 version: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
[0, +)
Num ber
Number of times that the uplink HQI is poor after the call setup is successful. Set the exception threshold when you a create task.
[1.00 , 5.00]
N/A
Average value of uplink voice quality BSC6900 indicators (VQIs) during calls. V900R013C00 or later version 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
Issue 01 (2013-07-15)
1346
Parame ter Poor Uplink VQI Times Average Downlin k Level Average Uplink Level Average Downlin k Quality Average Uplink Quality Downlin k Noise Occurre nce Times Downlin k Noise Ratio
Ran ge [0, +)
Description Number of times that the uplink VQI is poor during calls. Set the exception threshold when you create a task.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,7]
N/A
[0, +)
Num ber
Number of times that noise occurs in the downlink during calls, which is detected by the BSC.
Proportion of successful call setups where noise occurs in the downlink in all successful call setups. Proportion of successful call setups where noise occurs in the downlink in all successful call setups = Number of successful call setups where noise occurs in the downlink/Number of successful call setups (Connect Ack) x 100%
[0, +)
Num ber
Number of times that noise occurs in the uplink during calls, which is detected by the BSC.
Issue 01 (2013-07-15)
1347
Unit %
Description Proportion of successful call setups where noise occurs in the uplink in all successful call setups. Proportion of successful call setups where noise occurs in the uplink in all successful call setups = Number of successful call setups where noise occurs in the uplink/Number of successful call setups (Connect Ack) x 100%
RAN-CS/SMS/Accessibility Evaluation
Param eter Call Setup Reques ts (MOC) Call Setup Failure s (MOC) Call Setup Succes s Rate (MOC) Call Setup Reques ts (MTC) Call Setup Failure s (MTC) Range [0,+) Unit Num ber Description Number of setup requests that the mobile-originated party initiates to use the SMS service. Supported NE Version BSC6900 V900R013C00 or later version
[0,+)
Num ber
Number of call setup failures that the mobile-originated party experiences during the process of attempting to use the SMS service. Proportion of successful setup requests that mobile-originated party initiates to use the SMS service.
[0.00,1 00.00]
[0,+)
Num ber
Number of setup requests that the mobile-terminated party initiates to use the SMS service.
[0,+)
Num ber
Number of call setup failures that the mobile-terminated party experiences during the process of attempting to use the SMS service.
Issue 01 (2013-07-15)
1348
Unit %
Description Proportion of successful call setup requests that the mobile-terminated party initiates to use the SMS service.
RAN-PS/PS/General Evaluation
Parame ter Access Failures Total Reports of Access Failure Count > 0 Abnorm al Proporti on of Access Failure Count > 0 Service Interrupt ions Total Reports of Service Interrupt ion Count > 0
Issue 01 (2013-07-15)
Description See Access Failures in RAN-PS/PS/ Accessibility Evaluation. Indicates the number of the measurement reports that the access failure count exceeds 0.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0,10 0]
Indicates the proportion of the total measurement reports that the access failure count exceeds 0.
[0, +) [0, +)
Numb er Numb er
See Service Interruptions in RANPS/PS/Retainability Evaluation. Indicates the number of the measurement reports that the service interruption count exceeds 0.
1349
Parame ter Abnorm al Proporti on of Service Interrupt ion Count > 0 Abnorm al Service Interacti on Delays Total Reports of Abnorm al Service Interacti on Latency Count > 0 Abnorm al Proporti on of Abnorm al Service Interacti on Latency Count > 0 Downloa ds at Low Rate
Ran ge [0,10 0]
Unit %
Description Indicates the proportion of the total measurement reports that the service interruption count exceeds 0.
[0, +)
Numb er
[0, +)
Numb er
Indicates the number of the measurement reports that the abnormal service interaction latency count exceeds 0.
[0,10 0]
Indicates the proportion of the total measurement reports that the abnormal service interaction latency count exceeds 0.
[0, +)
Numb er
Issue 01 (2013-07-15)
1350
Parame ter Abnorm al Proporti on at Low Downloa d Rate Uploads at Low Rate Abnorm al Proporti on at Low Upload Rate
Ran ge [0,10 0]
Unit %
Description Indicates the proportion of the total measurement reports that the download rate is low.
[0, +) [0,10 0]
Numb er %
See Uploads at Low Rate in RANPS/PS/Service Evaluation for Rate. Indicates the proportion of the total measurement reports that the upload rate is low.
RAN-PS/PS/Accessibility Evaluation
Parame ter Access Failures Rang e [0, +) Unit Numb er Description Number of access failures that a VIP subscriber experiences during the process of using a data service. 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. Attach Requests [0, +) Numb er Number of Attach Request messages that a VIP subscriber sends during the whole process of using a data service. BSC6900 V900R013C01 or later version Supported NE Version BSC6900 V900R013C01 or later version
Issue 01 (2013-07-15)
1351
Rang e [0, +)
Unit Numb er
Description Number of Attach Fail messages that a VIP subscriber receives during the process of using a data service. 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. Number of Attach Fail messages = Number of Attach Request messages Number of Attach Accept messages
[0, +) [0, +)
Numb er Numb er
Number of PDP Active Request messages that a VIP subscriber sends during the process of using a data service. Number of PDP Active Fail messages that a VIP subscriber receives during the process of using a data service. 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. Number of Attach Fail messages = Number of PDP Active Request messages Number of PDP Active Accept messages
Authenti cation and Cipherin g Requests Authenti cation and Cipherin g Failures
[0, +)
Numb er
Number of authentication and ciphering requests that a VIP subscriber receives during the process of using a data service.
[0, +)
Numb er
Number of authentication and ciphering failures that a VIP subscriber receives during the process of using a data service.
Issue 01 (2013-07-15)
1352
Rang e [0, +)
Unit Numb er
Description Number of times that no response to service interaction is made. 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. (A = Number of times that the uplink PDU carries data but the downlink PDU does not). The exception thresholds 1 and 2 for the response to service interaction are internal algorithm parameters.
RAN-PS/PS/Retainability Evaluation
Parame ter Service Interrupt ions Rang e [0, +) Unit Numb er Description Number of service interruptions that a VIP subscriber experiences during the process of using a data service. Number of service interruptions = Number of service interruptions due to cell reselection + Number of service interruptions due to routing area update Interrupt ions Due to Cell Reselect ion [0, +) Numb er Number of service interruptions that a VIP subscriber experiences during the process of using a data service due to cell reselection. The parameter is also referred to as the number of cell reselections. [0, +) Secon d Mean time between cell reselections during the process for a VIP subscriber to use a data service. This parameter is also referred to as the average interval between cell reselections. BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version Supported NE Version BSC6900 V900R013C01 or later version
Issue 01 (2013-07-15)
1353
Rang e [0, +)
Unit Numb er
Description Number of times that the cell reselection interval is overlong during the process for a VIP subscriber to use a data service. If the time interval is above the threshold for overlong cell reselection, the cell reselection interval is overlong. Set the threshold when you create a task.
[0, +)
Numb er
Number of service interruptions that a VIP subscriber experiences during the process of using a data service due to routing area update.
Issue 01 (2013-07-15)
1354
Rang e [0, +)
Unit Secon d
Description Average duration of the response to service interaction during the process for a VIP subscriber to use a data service. Average duration of the response to service 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 transmission between the uplink and downlink PDUs.
[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. Set the threshold when you create a task.
Issue 01 (2013-07-15)
1355
Parame ter Abnorm al Proporti on at Low Downlo ad Rate Downlin k TCP Out-ofOrders Average Upload Rate
Rang e [0,10 0]
Unit %
Description Indicates the proportion of the total measurement reports that the download rate is low.
[0, +)
Numb er
Number of times that downlink TCP disorder occurs during the process for a subscriber to use a data service. Average upload rate during the process for a subscriber to use a data service. Upload rate = Number of bytes transmitted by using the uplink PDU/Duration of data transmission by using the uplink PDU
[0.00, +)
Kbps
[0, +)
Numb er
Number of times that the upload rate is low during the process for a subscriber to use a data service. An upload rate is low if it is lower than the threshold for low upload rate. Set the threshold is when you create a task.
[0,10 0]
Indicates the proportion of the total measurement reports that the upload rate is low.
[0.00, +)
Kbps
Issue 01 (2013-07-15)
1356
Rang e [0, +)
Unit MB
Description Total downlink traffic during the process for a subscriber to use a data service. 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 + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Downlink PDU
[0, +)
MB
Total uplink traffic during the process for a subscriber to use a data service. Total uplink traffic = Delay-Sensitive Information/Total Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Downlink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU
Uplink Signalin g Access Times Average Occupie d Downlin k Channel s Average Occupie d Uplink Channel s
[0, +)
Numb er
Number of access requests on the RACH (uplink CCCH) during the process for a subscriber to use a data service. Average number of channels occupied by the downlink during the process for a subscriber to use a data service.
[0, +)
Numb er
[0, +)
Numb er
Average number of channels occupied by the uplink during the process for a subscriber to use a data service.
Issue 01 (2013-07-15)
1357
Common
Para met er BSC Nam e Cell ID Cell Nam e CGI Range Unit Description Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
ID of a VIP subscriber. Query the ID of a VIP subscriber using VIP group management. Name of a VIP alias. Query the alias of a VIP subscriber using VIP group management.
N/A
N/A
Issue 01 (2013-07-15)
1358
Para met er IME ITAC Ter mina l Mod el Serv ice Typ e
Range
Unit
Description
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
International mobile equipment identitytype allocation code (IMEI-TAC) of the terminal used by a VIP subscriber. 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. Service type for a following counter.
N/A
N/A
N/A
N/A
RAN-CS/NET/Accessibility Evaluation
Par am eter R a n g e Uni t Description Supported NE Version
Number of access requests that a VIP group or VIP BSC6900 subscriber initiates during the process of using a call V900R013C00 or or SMS service in an active cell. later version
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.
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.
Issue 01 (2013-07-15)
1359
Par am eter
R a n g e
Uni t
Description
Supported NE Version
[ 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.
RAN-CS/NET/Retainability Evaluation
Par am eter R a n g e [ 0 , + ) [ 0 , + ) U Description n i t N Number of times that a VIP group or VIP subscriber u releases the Call service in an active cell. m b e r N Number of times that a VIP group or VIP subscriber u abnormally releases the Call service in an active cell. m b e r Supported NE Version
Rele ases
Issue 01 (2013-07-15)
1360
RAN-CS/NET/Mobility Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t 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 Supported NE Version
Inte rRA T Inco min g Han dov er Req uest s Inte rRA T Inco min g Han dov er Fail ures
[ 0 , + )
N Number of incoming inter-RAT handover failures that BSC6900 u a VIP group or VIP subscriber experiences in an active V900R013C00 or m cell. later version b e r
RAN-CS/Call/Accessibility Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t N Number of call setup requests that a VIP group or VIP u subscriber initiates in an active cell. m b e r Supported NE Version
Issue 01 (2013-07-15)
1361
Par am eter
R a n g e [ 0 , + ) [ 0 , + )
U Description n i t N Number of call setup failures that a VIP group or VIP u subscriber experiences in an active cell. m b e r 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
Supported NE Version
Call Setu p Fail ures Abn orm al Rele ase Bef ore Call Co mpl etio n
RAN-CS/Call/Retainability Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t N Number of abnormal call releases that a VIP group or u VIP subscriber experiences in an active cell. m b e r Supported NE Version
Issue 01 (2013-07-15)
1362
RAN-CS/SMS/Accessibility Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t N Number of call setup requests that a VIP group or VIP u subscriber initiates in an active cell as the mobilem originated party. b e r Supported NE Version
Call Setu p Req uest s (M OC) Call Setu p Fail ures (M OC) Call Setu p Req uest s (MT C) Call Setu p Fail ures (MT C)
[ 0 , + ) [ 0 , + )
N Number of call setup failures that a VIP group or VIP u subscriber experiences in an active cell as the mobilem originated party. b e r N Number of call setup requests that a VIP group or VIP u subscriber initiates in an active cell as the mobilem terminated party. b e r
[ 0 , + )
N Number of call setup failures that a VIP group or VIP u subscriber experiences in an active cell as the mobilem terminated party. b e r
Issue 01 (2013-07-15)
1363
RAN-PS/PS/Accessibility Evaluation
Par am eter R a n g e [ 0 , + ) [ 0 , + ) [ 0 , + ) U Description n i t N Number of Attach Request messages that a VIP group or u VIP subscriber sends in an active cell. m b e r N Number of PDP Active Request messages that a VIP u group or VIP subscriber sends in an active cell. m b e r 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 Supported NE Version
Atta ch Req uest s PD P Acti ve Req uest s No Serv ice Inte racti on Res pon ses
RAN-PS/PS/Retainability Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t 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 Supported NE Version
Issue 01 (2013-07-15)
1364
Par am eter
R a n g e [ 0 , + )
U Description n i t 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
Supported NE Version
Ove rlon g Cell Res elec tion Inte rval Tim es Serv ice Inte rrup tion s Due to Rou ting Are a Upd ate
[ 0 , + )
N Number of service interruptions that a VIP group or VIP u subscriber experiences due to routing area update in an m active cell. b e r
Issue 01 (2013-07-15)
1365
Par am eter
R a n g e [ 0 , + )
U Description n i t N Number of times that the delay of the response to service u interaction is overlong when a VIP group or VIP m subscriber is using a service in an active cell. b e r
Supported NE Version
Common
Paramet er Server IP Server Name Rang e N/A N/A Unit N/A N/A Description IP address of an active server. 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. Port number of an active server. Name of an active service. Obtain the name of an active service by choosing System Function > Data Service Server Management in the navigation tree of the Nastar client based on the Server IP and Server Port values of the service. Number of reports generated when a user accesses the server. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A N/A
N/A N/A
Total Reports
Issue 01 (2013-07-15)
[0, +)
Num ber
RAN-PS/PS/General Evaluation
Paramet er ServerRelated Service Abnorma lities Rang e [0, +) Unit Num ber Description Server-Related Service Abnormalities = No Service Interaction Responses + Service Interaction Timeouts + Service Interaction with Long Delay + Downlink TCP Out-of-Orders Supported NE Version BSC6900 V900R013C01 or later version
RAN-PS/PS/Accessibility Evaluation
Paramet er No Service Interactio n Response s Rang e [0, +) Unit Num ber Description 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. Supported NE Version BSC6900 V900R013C01 or later version
[0, +)
Num ber
Issue 01 (2013-07-15)
1367
Common
Parameter Deep Analysis Ran ge N/A Uni t N/A Description 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. 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. LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version Supported NE Version LTE 3900 V100R005C00 or later version
User ID
[1, +)
N/A
Identity of a VIP subscriber. User ID, which is created by the system when creating a VIP User in the VIP Group Management.
User Name
N/A
N/A
Name of a VIP subscriber. Query the name of a VIP subscriber using VIP group management based on the IMSI of the VIP subscriber. 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.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
IMEI-TAC
N/A
Issue 01 (2013-07-15)
1368
Ran ge N/A
Uni t N/A
Description 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. Service type for a counter.
N/A
N/A
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0, +)
Num ber
Number of abnormal counters whose values exceed the thresholds that engineers set during analysis task creation. Number of reports generated when a user accesses the network.
[0, +)
Num ber
[0,+)
Number
Issue 01 (2013-07-15)
1369
Parameter Intra-RAT Outgoing Handover Preparing Failures Intra-RAT Outgoing Handover Preparing Success Rate Intra-RAT Outgoing Handover Execution Attempts Intra-RAT Outgoing Handover Execution Failures Intra-RAT Outgoing Handover Execution Success Rate Inter-RAT Outgoing Handover Preparing Attempts Inter-RAT Outgoing Handover Preparing Failures Inter-RAT Outgoing Handover Preparing Success Rate
Range [0,+)
Unit Number
Description Number of failed intraRAT handover preparations after a UE initiates intra-RAT handover requests. Successful preparation rate of intra-RAT handovers.
[0,100]
[0,+)
Number
[0,+)
Number
[0,100]
[0,+)
Number
[0,+)
Number
Number of failed interRAT handover preparations after a UE initiates inter-RAT handover requests. Successful preparation rate of inter-RAT handovers.
[0,100]
Issue 01 (2013-07-15)
1370
Parameter Inter-RAT Outgoing Handover Execution Attempts Inter-RAT Outgoing Handover Execution Failures Inter-RAT Outgoing Handover Execution Success Rate
Range [0,+)
Unit Number
[0,+)
Number
[0,100]
RAN PS Counters-Accessibility
Parameter E-RAB Setup Requests E-RAB Setup Failures E-RAB Setup Success Rate Range [0,+) Unit Number Description Number of E-RAB setup requests initiated by a UE. Number of failed E-RAB setups after a UE initiates E-RAB setup requests. Success rate of E-RAB setups after a UE initiates E-RAB setup requests. ERAB is E-UTRAN radio access bearer for short. Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,+)
Number
[0,100]
RAN PS Counters-Retainablity
Parameter Abnormal ERAB Releases Range [0,+) Unit Number Description Number of abnormal ERAB releases in the E-RAB releases. Supported NE Version LTE 3900 V100R005C00 or later version
Issue 01 (2013-07-15)
1371
Range [0,100]
Unit %
Active Cell
Parameter eNodeB ID Range N/A Unit N/A Description ID of an eNodeB. Supported NE Version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version
eNodeB Name
N/A
N/A
Name of an eNodeB.
Cell ID
N/A
N/A
ID of a cell.
Cell Name
N/A
N/A
Name of a cell.
Service Type
N/A
N/A
[0,+)
Numbe r
Number of service RRC setup requests of a VIP group or a VIP object in an active cell. Number of non-service RRC setup requests of a VIP group or a VIP object in an active cell. Number of E-RAB setup requests of a VIP group or a VIP object in an active cell.
[0,+)
Numbe r
[0,+)
Numbe r
Issue 01 (2013-07-15)
1372
Range [0,+)
Unit Numbe r
Description Number of failed E-RAB setups of a VIP group or a VIP object in an active cell. Number of abnormal E-RAB releases of a VIP group or a VIP object in an active cell.
Supported NE Version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version
[0,+)
Numbe r
Common
Parameter Deep Analysis Rang e N/A Unit N/A Description 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. 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. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
User ID
N/A
N/A
ID of a VIP subscriber.
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.
Issue 01 (2013-07-15)
1373
Parameter IMEI-TAC
Rang e N/A
Unit N/A
Description International mobile equipment identity-type allocation code (IMEI-TAC) of the terminal used by a VIP subscriber. 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. 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. Number of reports of the VIP user.
Terminal Model
N/A
N/A
[0, +)
Numb er
Total Reports
[0, +)
Numb er
SGSN-Attach
Parameter Rang e Unit Numb er Description Number of attach process requests by a VIP subscriber on the GSM and UMTS networks. Attach processes include: GPRS attach Combined attach Attach Failures [0, +) Numb er Number of attach process failures by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1374
Unit %
Description Attach process success rate by a VIP subscriber on the GSM and UMTS networks. Attach success rate = (1 Number of attach failures/ Number of attach requests) x 100%
[0, +) [0, +)
ms
Average delay of an attach process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of an attach process by a VIP subscriber on the GSM and UMTS networks.
Numb er
SGSN-RAU
Parameter RAU (others) Requests Rang e [0.00, 100.0 0] [0, +) [0, +) Unit % Description Number of other RAU processes by a VIP subscriber on the GSM and UMTS networks Number of other RAU process failures by a VIP subscriber on the GSM and UMTS networks. Other RAU process success rate by a VIP subscriber on the GSM and UMTS networks. RAU (others) success rate = (1 Number of RAU (others) failures/Number of RAU (others) requests) x 100% Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
ms
Numb er
Issue 01 (2013-07-15)
1375
Rang e [0, +)
Unit Numb er
Description Number of intra SGSN RAU process requests by a VIP subscriber on the GSM and UMTS networks. Intra SGSN RAU processes include: Intra RAU Intra combined RAU Periodic RAU Periodic combined RAU
[0, +)
Numb er
Number of intra SGSN RAU process failures by a VIP subscriber on the GSM and UMTS networks. Intra SGSN RAU process success rate by a VIP subscriber on the GSM and UMTS networks. Intra SGSN RAU success rate = (1 Number of intra SGSN RAU failures/Number of intra SGSN RAU requests) x 100%
[0.00, 100.0 0]
Average Intra SGSN RAU Delay Overlong Intra SGSN RAU Delays
[0, +)
ms
Average delay of an intra SGSN RAU process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of an intra SGSN RAU process by a VIP subscriber on the GSM and UMTS networks. Number of inter SGSN RAU process requests by a VIP subscriber on the GSM and UMTS networks. Inter SGSN RAU processes include: Inter RAU Inter combined RAU
[0, +)
Numb er
[0, +)
Numb er
Issue 01 (2013-07-15)
1376
Rang e [0, +)
Unit Numb er
Description Number of inter SGSN RAU process failures by a VIP subscriber on the GSM and UMTS networks. Inter SGSN RAU process success rate by a VIP subscriber on the GSM and UMTS networks. Inter SGSN RAU process success rate by a VIP subscriber on the GSM and UMTS networks.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
[0.00, 100.0 0]
Average Inter SGSN RAU Delay Overlong Inter SGSN RAU Delays
[0, +)
ms
Average delay of an inter SGSN RAU process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of an inter SGSN RAU process by a VIP subscriber on the GSM and UMTS networks.
[0, +)
Numb er
SGSN-Service Req
Parameter Service Req Requests Rang e [0, +) Unit Numb er Description Number of service req process requests by a VIP subscriber on the GSM and UMTS network. The service req process includes: Service Request Service Req Failures Service Req Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of service req process failures by a VIP subscriber on the GSM and UMTS network. Service req process success rate by a VIP subscriber on the GSM and UMTS networks. Service req success rate = (1 Number of service req failures/ Number of service req requests) x 100% USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1377
Unit ms
Description Average delay of a service req process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a service req process by a VIP subscriber on the GSM and UMTS networks.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Numb er
SGSN-Relocation
Parameter Relocation Requests Rang e [0, +) Unit Numb er Description Number of relocation process requests by a VIP subscriber on the GSM and UMTS networks. Relocation processes include: Intra SRNS relocation Inter SRNS relocation Relocation Failures Relocation Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of relocation process failures by a VIP subscriber on the GSM and UMTS networks. Relocation process success rate by a VIP subscriber on the GSM and UMTS networks. Relocation success rate = (1 Number of relocation failures/ Number of relocation requests) x 100% Average Relocation Delay Overlong Relocation Delays [0, +) [0, +) ms Average delay of a relocation process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a relocation process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Numb er
Issue 01 (2013-07-15)
1378
SGSN-System Change
Parameter System Change Requests Rang e [0, +) Unit Numb er Description Number of system change process requests by a VIP subscriber on the GSM and UMTS networks. System change processes include: 3G to 2G system change 2G to 3G system change System Change Failures [0, +) Numb er Number of system change process failures by a VIP subscriber on the GSM and UMTS networks. System change process success rate by a VIP subscriber on the GSM and UMTS networks. System change success rate = (1 Number of system change failures/Number of system change requests) x 100% Average System Change Delay [0, +) ms Average delay of a system change process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a system change process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0.00, 100.0 0]
[0, +)
Numb er
SGSN-Paging
Parameter Paging Requests Rang e [0, +) Unit Numb er Description Number of paging process requests by a VIP subscriber on the GSM and UMTS networks. The paging process includes Paging. Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1379
Unit Numb er %
Description Number of paging process failures by a VIP subscriber on the GSM and UMTS networks. Paging process success rate by a VIP subscriber on the GSM and UMTS networks. Paging success rate = (1 Number of paging failures/ Number of paging requests) x 100%
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
[0, +) [0, +)
ms
Average delay of a paging process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a paging process by a VIP subscriber on the GSM and UMTS networks.
Numb er
SGSN-PDP Act
Parameter PDP Act Requests Rang e [0, +) Unit Numb er Description Number of PDP act process requests by a VIP subscriber on the GSM and UMTS networks. PDP act processes include: MS Init PDP Act CN Init PDP Act PDP Act Failures PDP Act Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of PDP act process failures by a VIP subscriber on the GSM and UMTS networks. PDP act process success rate by a VIP subscriber on the GSM and UMTS networks. PDP act success rate = (1 Number of PDP act failures/ Number of PDP act requests) x 100% USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1380
Unit ms
Description Average delay of a PDP act process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a PDP act process by a VIP subscriber on the GSM and UMTS networks.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Numb er
SGSN-PDP Act
Parameter PDP Sec Act Requests Rang e [0, +) Unit Numb er Description Number of PDP sec act process requests by a VIP subscriber on the GSM and UMTS networks. The PDP sec act process includes: MS Init PDP Sec Act PDP Sec Act Failures PDP Sec Act Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of PDP sec act process failures by a VIP subscriber on the GSM and UMTS networks. PDP sec act process success rate by a VIP subscriber on the GSM and UMTS networks. PDP sec act success rate = (1 Number of PDP sec act failures/ Number of PDP sec act requests) x 100% Average PDP Sec Act Delay Overlong PDP Sec Act Delays [0, +) [0, +) ms Average delay of a PDP sec act process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a PDP sec act process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Numb er
Issue 01 (2013-07-15)
1381
SGSN-PDP Mod
Parameter PDP Mod Requests Rang e [0, +) Unit Numb er Description Number of PDP mod process requests by a VIP subscriber on the GSM and UMTS networks. PDP mod processes include: MS Init PDP Mod CN Init PDP Mod PDP Mod Failures PDP Mod Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of PDP mod process failures by a VIP subscriber on the GSM and UMTS networks. PDP mod process success rate by a VIP subscriber on the GSM and UMTS networks. PDP mod success rate = (1 Number of PDP mod failures/ Number of PDP mod requests) x 100% Average PDP Mod Delay Overlong PDP Mod Delays [0, +) [0, +) ms Average delay of a PDP mod process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a PDP mod process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Numb er
SGSN-RAB Assignment
Parameter RAB Assignment Requests RAB Assignment Failures Rang e [0, +) [0, +) Unit Numb er Numb er Description Number of RAB Assignment requests of a VIP subscriber on the GSM/UMTS network Number of RAB assignment failures of a VIP subscriber on the GSM/UMTS network Supported NE Version USN9810 V900R012C00 or later version USN9810 V900R012C00 or later version
Issue 01 (2013-07-15)
1382
Unit %
Description RAB assignment success rate of a VIP subscriber on the GSM/ UMTS network RAB assignment success rate = (1 Number of RAB assignment failures/Number of RAB Assignment requests) x 100%
[0, +) [0, +)
ms
Average RAB assignment delay of a VIP subscriber on the GSM/ UMTS network Number of times that the RAB assignment delay of a VIP subscriber exceeds the predefined exception threshold on the GSM/UMTS network
Numb er
[0.00, 100.0 0]
Issue 01 (2013-07-15)
1383
Parameter Average PDN GW Dedicated Bearer Act Delay Overlong PDN GW Dedicated Bearer Act Delays
Ran ge [0, +)
Unit ms
Description Average PDN GW dedicated bearer activation delay of a VIP subscriber on the GSM/UMTS network 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
Supported NE Version USN9810 V900R012C00 or later version USN9810 V900R012C00 or later version
[0, +)
Numbe r
[0.00 , 100.0 0]
Issue 01 (2013-07-15)
1384
Ran ge [0, +)
Unit Numbe r
Description Number of times that the PDN GW initiated bearer modification delay of a VIP subscriber exceeds the predefined exception threshold on the GSM/UMTS network
MME-Attach
Parameter Attach Requests Ran ge [0, +) Unit Numbe r Description Number of attach process requests by a VIP subscriber on the LTE network. The attach process includes: Attach Attach Failures [0, +) [0.00 , 100.0 0] Numbe r % Number of attach process failures by a VIP subscriber on the LTE network. Attach process success rate by a VIP subscriber on the LTE network. Attach success rate = (1 Number of attach failures/ Number of attach requests) x 100% ms Average delay of an attach process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an attach process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Numbe r
Issue 01 (2013-07-15)
1385
MME-TAU
Parameter Intra TAU Requests Ran ge [0, +) Unit Numbe r Description Number of intra TAU process requests by a VIP subscriber on the LTE network. 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 Intra USN E-UTRAN to UTRAN Inter RAT RAU Intra TAU Failures Intra TAU Success Rate [0, +) [0.00 , 100.0 0] Numbe r % Number of intra TAU process failures by a VIP subscriber on the LTE network. Intra TAU process success rate by a VIP subscriber on the LTE network. Intra TAU success rate = (1 Number of intra TAU failures/ Number of intra TAU requests) x 100% ms Average delay of an intra TAU process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an intra TAU process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Numbe r
Issue 01 (2013-07-15)
1386
Ran ge [0, +)
Unit Numbe r
Description Number of inter TAU process requests by a VIP subscriber on the LTE network. 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
Numbe r %
Number of inter TAU process failures by a VIP subscriber on the LTE network. Inter TAU process success rate by a VIP subscriber on the LTE network. Inter TAU success rate = (1 Number of inter TAU failures/ Number of inter TAU requests) x 100%
[0, +) [0, +)
ms
Average delay of an inter TAU process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an inter TAU process by a VIP subscriber on the LTE network.
Numbe r
Issue 01 (2013-07-15)
1387
MME-Handover
Parameter Intra E-UTRAN Handover Requests Ran ge [0, +) Unit Numbe r Description Number of intra E-UTRAN handover process requests by a VIP subscriber on the LTE network. Intra E-UTRAN handover processes include: X2 Handover Intra MME S1 Handover Inter MME S1 Handover Intra E-UTRAN Handover Failures Intra E-UTRAN Handover Success Rate [0, +) Numbe r Number of intra E-UTRAN handover process failures by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0.00 , 100.0 0]
Success rate of an intra EUSN9810 UTRAN handover process by a V900R011C01 or VIP subscriber on the LTE later version network. Intra E-UTRAN handover success rate = (1 Number of intra E-UTRAN handover failures/Number of intra EUTRAN handover requests) x 100%
Average Intra EUTRAN Handover Delay Overlong Intra E-UTRAN Handover Delays
[0, +)
ms
Average delay of an intra EUSN9810 UTRAN handover process by a V900R011C01 or VIP subscriber on the LTE later version network. Number of delays that exceed the exception threshold of an intra E-UTRAN handover process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version
[0, +)
Numbe r
Issue 01 (2013-07-15)
1388
Ran ge [0, +)
Unit Numbe r
Description Number of inter RAT handover process requests by a VIP subscriber on the LTE network. Inter RAT handover processes include: Intra USN UTRAN Iu mode to E-UTRAN Inter RAT handover Inter USN UTRAN Iu mode to E-UTRAN Inter RAT handover Intra USN E-UTRAN to UTRAN Iu mode Inter RAT handover Inter USN E-UTRAN to UTRAN Iu mode Inter RAT handover
Numbe r %
Number of inter RAT handover process failures by a VIP subscriber on the LTE network. Success rate of an inter RAT handover process by a VIP subscriber on the LTE network. Inter RAT handover success rate = (1 Number of inter RAT handover failures/Number of inter RAT handover requests) x 100%
Average Inter RAT Handover Delay Overlong Inter RAT Handover Delays
[0, +) [0, +)
ms
Average delay of an inter RAT handover process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an inter RAT handover process by a VIP subscriber on the LTE network.
Numbe r
Issue 01 (2013-07-15)
1389
MME-Service Req
Parameter Service Req Requests Ran ge [0, +) Unit Number Description Number of service req process requests by a VIP subscriber on the LTE network. The service req process includes: Service Request Service Req Failures Service Req Success Rate [0, +) [0.00 , 100. 00] Number Number of service req process failures by a VIP subscriber on the LTE network. Service req process success rate by a VIP subscriber on the LTE network. Service req success rate = (1 Number of service req failures/ Number of service req requests) x 100% ms Average delay of a service req process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a service req process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Number
MME-Paging
Parameter Paging Requests Ran ge [0, +) Unit Numbe r Description Number of paging process requests by a VIP subscriber on the LTE network. The paging process includes: Paging. Paging Failures [0, +) Numbe r Number of paging process failures by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1390
Unit %
Description Paging process success rate by a VIP subscriber on the LTE network. Paging success rate = (1 Number of paging failures/ Number of paging requests) x 100%
[0, +) [0, +)
ms
Average delay of a paging process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a paging process by a VIP subscriber on the LTE network.
Numbe r
MME-Interoperation
Parameter Interoperation Requests Ran ge [0, +) Unit Numbe r Description Number of interoperation process requests by a VIP subscriber on the LTE network. Interoperation processes include: MME to 3G SGSN combined hard handover and SRNS relocation procedure 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure Interoperation Failures Interoperation Success Rate [0, +) [0.00 , 100. 00] Numbe r % Number of interoperation process failures by a VIP subscriber on the LTE network. Interoperation process success rate by a VIP subscriber on the LTE network. Interoperation success rate = (1 Number of interoperation failures/Number of interoperation requests) x 100% USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1391
Unit ms
Description Average delay of an interoperation process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an interoperation process by a VIP subscriber on the LTE network.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Numbe r
Average Dedicated Bearer Act Delay Overlong Dedicated Bearer Act Delays
[0, +)
[0, +)
Numbe r
Issue 01 (2013-07-15)
1392
MME-Bearer Mod
Parameter Bearer Mod Requests Ran ge [0, +) Unit Numbe r Description Number of bearer mod process requests by a VIP subscriber on the LTE network. Bearer mod processes include: PDN GW initiated bearer modification with bearer QoS update HSS Initiated Subscribed QoS Modification PDN GW initiated bearer modification without bearer QoS update Bearer Mod Failures Bearer Mod Success Rate [0, +) [0.00 , 100. 00] Numbe r % Number of bearer mod process failures by a VIP subscriber on the LTE network. Bearer mod process success rate by a VIP subscriber on the LTE network. Bearer mod success rate = (1 Number of bearer mod failures/ Number of bearer mod requests) x 100% ms Average delay of a bearer mod process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a bearer mod process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Numbe r
Issue 01 (2013-07-15)
1393
Average Bearer Resource Mod Delay Overlong Bearer Resource Mod Delays
[0, +) [0, +)
Numbe r
MME-PDN
Parameter PDN Connectivity Requests Ran ge [0, +) Unit Numbe r Description Number of PDN connectivity process requests by a VIP subscriber on the LTE network. The PDN connectivity process includes: UE requested PDN connectivity PDN Connectivity Failures [0, +) Numbe r Number of PDN connectivity process failures by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1394
Unit %
Description PDN connectivity process success rate by a VIP subscriber on the LTE network. PDN connectivity success rate = (1 Number of PDN connectivity failures/Number of PDN connectivity requests) x 100%
[0, +) [0, +)
ms
Average delay of a PDN connectivity process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a PDN connectivity process by a VIP subscriber on the LTE network.
Numbe r
GGSN-Create PDP
Parameter Create PDP Requests Create PDP Failures Create PDP Success Rate Ran ge [0, +) [0, +) [0.00 , 100. 00] Unit Numbe r Numbe r % Description Number of Create PDP procedures of a VIP subscriber on the GSM/UMTS network. Number of Create PDP failures of a VIP subscriber on the GSM/ UMTS network. Success rate of the Create PDP procedures of a VIP subscriber on the GSM/UMTS network. Create PDP Success Rate = (1 Number of Create PDP failures/ Number of Create PDP requests) x 100% Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
GGSN-Update PDP
Parameter Update PDP Requests Ran ge [0, +) Unit Numbe r Description Number of Update PDP procedures of a VIP subscriber on the GSM/UMTS network. Supported NE Version UGW9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1395
Unit Numbe r %
Description Number of Update PDP failures of a VIP subscriber on the GSM/ UMTS network. Success rate of the Update PDP procedures of a VIP subscriber on the GSM/UMTS network. Update PDP Success Rate = (1 Number of Update PDP failures/ Number of Update PDP requests) x 100%
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
SAE-GW-Modify Bearer
Parameter Create Session Requests Modify Bearer Requests Modify Bearer Failures Modify Bearer Success Rate Ran ge [0, +) [0, +) [0, +) [0.00 , 100. 00] Unit Numbe r Numbe r Numbe r % Description Number of Create Session procedures of a VIP subscriber on the LTE network. Number of Modify Bearer procedures of a VIP subscriber on the LTE network. Number of Modify Bearer failures of a VIP subscriber on the LTE network. Success rate of the Modify Bearer procedures of a VIP subscriber on the LTE network. Modify Bearer Success Rate = (1 Number of Modify Bearer failures/Number of Modify Bearer requests) x 100% Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
SAE-GW-Create Session
Parameter Create Session Failures Ran ge [0, +) Unit Numb er Description Number of Create Session failures of a VIP subscriber on the LTE network. Supported NE Version UGW9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1396
Unit %
Description Success rate of the Create Session procedures of a VIP subscriber on the LTE network. Create Session Success Rate = (1 Number of Create Session failures/Number of Create Session requests) x 100%
SAE-GW-Create Bearer
Parameter Create Bearer Requests Create Bearer Failures Create Bearer Success Rate Ran ge [0, +) [0, +) [0.00 , 100. 00] Unit Numb er Numb er % Description Number of Create Bearer procedures of a VIP subscriber on the LTE network. Number of Create Bearer failures of a VIP subscriber on the LTE network. Success rate of the Create Bearer procedures of a VIP subscriber on the LTE network. Create Bearer Success Rate = (1 Number of Create Bearer failures/ Number of Create Bearer requests) x 100% Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
SAE-GW-Update Bearer
Parameter Create Session Requests Create Session Failures Ran ge [0, +) [0, +) Unit Numbe r Numbe r Description Number of Create Session procedures of a VIP subscriber on the LTE network. Number of Create Session failures of a VIP subscriber on the LTE network. Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1397
Unit %
Description Success rate of the Create Session procedures of a VIP subscriber on the LTE network. Create Session Success Rate = (1 Number of Create Session failures/Number of Create Session requests) x 100%
[0, +)
Num ber
Issue 01 (2013-07-15)
1398
Unit %
Description Success rate of the Bearer Resource Command procedures of a VIP subscriber on the LTE network. Bearer Resource Command Success Rate = (1 Number of Bearer Resource Command failures/Number of Bearer Resource Command requests) x 100%
[0, +)
Numb er
[0.00 , 100.0 0]
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.
Function Description
The Nastar obtains the call event records of complaining subscribers, and then filters, aggregates, and analyzes data based on a specified history period and detailed call records of subscribers in a specified area. This can assist you in locating and solving problems. The complaint analysis support function consists of the aggregation and analysis of cause types in call reports of complaining subscribers, aggregation and analysis of information about call reports of complaining subscribers, analysis of detailed information about call reports of complaining subscribers, analysis of procedure before signaling release in call reports of complaining subscribers, analysis of active cells in call reports of complaining subscribers, and so on. The function supports the following analysis type: l l 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-27. Table 4-27 Function description of complaint analysis support Function Type Aggregation and analysis of cause types in call reports of complaining subscribers Description Helps network engineers filter and aggregate call reports based on exception causes. Supported Network GSM/ UMTS/ LTE/PS Core
Issue 01 (2013-07-15)
1400
Description 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, service duration, and so on. 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. 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. 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.
Analysis of procedure before signaling release in call reports of complaining subscribers Analysis of measurement reports (MRs) on calls of complaint subscribers before call release
GSM/ UMTS/LTE
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. Provides information about the serving cells of subscribers before call release and the neighboring cells. This helps engineers analyze and locate problems.
GSM
UMTS/LTE
Mobility analysis
Provides handover information of a terminal and helps network engineers to learn about all cells that are recorded in abnormal call records. Analyzes RAB-related counters and provides network quality information about a service. Geographically displays the cells to which complaining subscribers have gained access and the cells from which complaining subscribers have been released.
Issue 01 (2013-07-15)
1401
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.
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 UMTS network, if you want to view the comprehensive measurement report information, 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. 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.
Function Principles
Figure 4-49 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 4-28.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1402
Table 4-28 Description of complaint analysis support User Oper ation 1. Subscr ibe to basic data Scen e GSM / UM TS netw ork Proce dure Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd
Issue 01 (2013-07-15)
Purpose
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. To issue an MML command to the M2000.
eSA U
M2000
M20 00
BSC/ RNC
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
1403
Scen e
Purpose
Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd Upload raw data
eSAU
To turn on the data source switch on the NE side. After a user enables the basic data subscription function (PS Core complaint analysis support) on the Nastar client, the Nastar issues a basic data subscription command to the eSAU. To issue an MML command to the M2000.
eSA U
M2000
M20 00
SGSN/ MME
To forward the MML command to the NE, requesting the NE to generate raw data.
PS SAU
Issue a basic data subscri ption comma nd Issue a subscri ption comma nd
eSAU
To turn on the data source switch on the NE side. After 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. To issue a subscription command to the M2000.
eSA U
M2000
Issue 01 (2013-07-15)
1404
Scen e
Proce dure Forwar d the subscri ption comma nd Upload raw data
Sour ce M20 00
Purpose
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNod eB/ MM E
l To collect the data from Trace Server after 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 transmission switch is enabled.
Deliver a dataprepro cessing task (direct) Upload prepro cessed data (direct) Upload data analysi s results
Nasta r Serve r
To deliver a data-preprocessing request to the SAU/LTE SAU/PS SAU through the eSAU, requesting the SAU/LTE SAU/PS SAU to start the data-preprocessing task.
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. To display analysis results on the Nastar client.
Nastar Server
Item Execution type Network scale to be analyzed in a task Users to be analyzed in a task
Task Management Capacity One-time task No limited, for all RATs. l Analyzing with IMSI, <= 2,000 users, for all RATs. l Analyzing with MSISDN or peer MSISDN, <= 200 users, for all RATs. <= 500, for all RATs.
NOTE This specification is the sum of all complaint analysis support tasks. It has nothing to do with the number of licenses for complaint analysis support or with the RAT.
Issue 01 (2013-07-15)
1406
Table 4-29 Required license and rights of complaint analysis support Functio n Data subscript ion manage ment Required license Data subscription management Required rights (Security > Security Management > User) l Function operation rights Operation Rights > Operation > Nastar System Task Management > Data Subscription Management Authentication 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.
Issue 01 (2013-07-15)
1407
Required rights (Security > Security Management > User) l Function operation rights Operation Rights > Operation > Nastar Subject Management > GSM Complaint Analysis Support Operation Rights 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. 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.
CAUT ION If the analy zed IMSI or MSI SDN of comp lainin g user is the same as the VIP user in the VIP grou p mana geme nt funct ion, and you has not the opera tion rights to opera te the VIP user, you are not allow ed to creat e the comp laint analy sis supp ort task about the IMSI or MSI SDN.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > UMTS Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > LTE TDD Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > LTE FDD Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > PS Core Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l GSM / UMT
Issue 01 (2013-07-15)
1408
Functio n S comb ined comp laint analy sis supp ort l LTE FDD/ LTE TDD comb ined comp laint analy sis supp ort l RAN side (GS M/ UMT S/ LTE FDD/ LTE TDD ) and PS Core comb ined comp laint analy sis supp ort
Required license support, and UMTS complaint analysis support l LTE FDD complaint analysis support, and LTE TDD complaint analysis support l Complaint analysis support of analyzed network on the RAN side, and PS Core complaint analysis support
Required rights (Security > Security Management > User) Have both involved licenses of Complaint Analysis Support Operation Rights of combined analysis. l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
Table 4-30 Required basic data of complaint analysis support Data Type Configur ation Data (Mandato ry) Function The configuration data of 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 which subscribers have gained access, cells which subscribers have released, and cells to which subscribers have handed over.
NOTE If you only perform the PS Core complaint analysis support, you do not need the configuration data.
Operation If the OSS information has been already configured, the Nastar automatically collects and imports the configuration data after the OSS and NE information is configured. You can also manually collect the configuration data before the specified time period starts. After the configuration data is imported, you can choose Maintenance > Data Maintenance Management to check whether the configuration data is available in the Nastar database. For detailed information about collecting, importing, and checking, see 2.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.
Issue 01 (2013-07-15)
1410
Function l Time The Nastar only analyzes complaints that occurred in the latest seven days. 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, MSISDN, or peer MSISDN IMSI: Supported by every network. MSISDN: Only supported by the PS Core network. Peer MSISDN: Only supported by the GSM network when choosing the CS service. You can obtain either the above information of a complaining subscriber for analysis when
Operation Enter the complaining subscriber information when creating complaint analysis support.
NOTE Generally, you obtain the IMSI and MSISDN of a VIP user and enter them into the Nastar. If telecom operators have high requirements for user information security and the anonymous policy is enabled on the network where the Nastar is deployed, all user information such as IMSI, MSISDN, and IMEI contained in the analysis data will be encrypted. To protect the security-sensitive user information, the Nastar no longer allows you to enter the plaintext IMSI and MSISDN. In this situation, you need to contact telecom operators to obtain the encrypted IMSI. The Nastar does not support the encrypted MSISDN. Telecom operators can visit http://support.huawei.com and choose Software Center > Controlled Tool(Mini-tool Software) > Core Network Product Line > Wireless-OSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt user 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 2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key. TIP If the number of complaining subscribers to be analyzed is large, you can save the IMSI, MSISDN or peer MSISDN information in the files in .xls/.xlsx/.csv format. The IMSI information stores a maximum of 2,000 records. Each IMSI must contain 15 digits. The MSISDN or peer MSISDN information stores a maximum of 200 records.
Issue 01 (2013-07-15)
1411
Data Type
Operation
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.
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.
The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map.
You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
Issue 01 (2013-07-15)
1412
Table 4-31 Description of the data source environment Net wor k GSM Description
l GSM RAN CS analysis : Check that the matching M2000 version is V200R011C00 (or later), and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l GSM RAN PS analysis: Check that the matching M2000 version is V200R012C00 (or later), and the NE version is BSC6900 V900R014C00 (or later), and BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On the User Identity Information Reporting Switch (GSM) in Nastar Commissioning Guide. l (Optional) Only calculating the counters related to speech quality, you need to manually turn on the switches for reporting uplink and downlink speech quality information in MR data. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On the Switches for Reporting Speech Quality Information in MR Data (GSM Complaint Analysis Support, Optional) in Nastar Commissioning Guide. l (Optional) If you want to view the counters about the PS measurement information, check that the PS network control mode is set. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Setting the PS Network Control Mode in Nastar Commissioning Guide.
UM TS
l Check that the matching M2000 version is V200R011C00SPC220 or later and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(UMTS) > Turning On the User Identity Information Reporting Switch (UMTS) in Nastar Commissioning Guide.
Issue 01 (2013-07-15)
1413
Description
l Check that the matching M2000 version is M2000 V200R012C00SPC200 or later, the NE version is LTE3900 V100R005C00SPC320 (or later) or LTE3900 V100R008C00SPC020 (or later), and the MME on the CN must be provided by Huawei and the version is USN9810 V900R011C01SPC300 or later.
NOTE 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 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. 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. 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. 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 M2000 versions are consistent with the following information: NE version: USN9810 V900R011C01, USN9810 V900R011C02, USN9810 V900R012C00; UGW9811 V900R009C01, UGW9811 V900R009C02, UGW9811 V900R010C00. M2000 version: M2000 V200R011C01, M2000 V200R012C01, M2000 V200R013C00.
Issue 01 (2013-07-15)
1414
Prerequisites
You have finished the preparation of complaint analysis support, such as checking the operation rights, preparing the basic data, and so on. For details, see 3.10.2 Preparations for Complaint Analysis Support.
Procedure
Figure 4-50 shows the process of complaint analysis support. For details, see Table 4-32. Figure 4-50 Flowchart for complaint analysis support
Issue 01 (2013-07-15)
1415
Table 4-32 Description of complaint analysis support procedures No. Proced ure Subscrib e to analysis data (basic) Description Reference for Detailed Operations 2.5 Subscribing to Analysis Data
(1)
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator who is authorized to subscribe to basic data to turn on the data switch.
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click *** tab. *** indicates the network. 2. In the left navigation tree, select the NEs to be configured. 3. On the Basic Subscription Settings tab page, click Set. 4. In the displayed Basic Subscription Settings dialog box, set complaint analysis support data to ON. l In the GSM network, the switch name is Complaint Analysis Support Data(CHR-CS), Complaint Analysis Support Data(CHR-PS), and Complaint Analysis Support Data(MRCS) for subscribing to the CHR-CS , CHR-PS data, and MR data of the GSM network. If you have obtained the MR data, you can view the comprehensive measurement report information, and assess business voice quality through VQI accurately. If not, you can only view a small number of measurement reports, and assess voice quality generally. l In the UMTS network, the switch name is Complaint Analysis Support Data(CHR) and Complaint Analysis Support Data(MR) for subscribing to the CHR data and MR data of the UMTS network. If you have obtained the MR data, you can view the comprehensive measurement report information. If not, you can only view a small number of measurement reports. 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 01 (2013-07-15)
1416
No.
Proced ure
Description
NOTE l The Nastar cannot issue all MML commands to network elements (NEs) by using the basic subscription function. To obtain data, confirm that you have manually issued the CHR enabled operation. For details, see 3.10.2 Preparations for Complaint Analysis Support. l Disable procedures (such as the Service Request procedure and the PDP MOD procedure) that involve all signaling information on the CN side. Otherwise, a large amount of data is collected from the CN and consequently the SGSN or MME cannot upload the data in time. As a result, certain data required by the Nastar is missing or delayed being reported.
l If you want to view the all signaling information, click , select the interface about All Signaling. 5. Click Confirm. Check that the data switch is successfully turned on by viewing the displayed information in the Log Info area.
Issue 01 (2013-07-15)
1417
No.
Description
Reference for Detailed Operations l For details, see 2.7 Creating an Analysis Task. l For details about the parameter s, see Analysis Task Paramete rs.
(2)
Navigation path: Choose Theme Function > User Assurance > Complaint Analysis Support in the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click the Complaint Analysis Support node. 2. Set the task name and task remarks. Click Next. 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 MSISDN: Only supported by the PS Core network. l Peer MSISDN: Only supported by the GSM network when choosing the CS service. l You can obtain either the above information of a complaining subscriber for analysis when supporting multi information. 6. On the Set KPI Threshold tab page, set the abnormal threshold of each KPI. Click Next. 7. Choose an analysis time segment. The Nastar obtains the relevant analysis data in the time period. 8. Click Finish.
Issue 01 (2013-07-15)
1418
No.
Description
Reference for Detailed Operations l For details, see 2.8 Querying Analysis Results. l For details on the interface descriptio n, see 3.10.4 Referenc e for Complai nt Analysis Support Interface . l For details, see 2.10 Exportin g Analysis Reports. l For details on the interface descriptio n, see 3.10.4 Referenc e for Complai nt Analysis Support Interface .
(3)
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click an analysis result of the task. 2. In the displayed Complaint Analysis Support window, view the complaint analysis support results
(4)
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. 2. Specify the export path and export format. 3. Click Save.
Issue 01 (2013-07-15)
1419
Complaining subscriber information Parameter Set Analysi s Type Analysis Scene Description 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, for the combined complaint analysis support. 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.
Issue 01 (2013-07-15)
1420
Description Both access methods can be chosen. Set the data type on the RAN side. l RAN CS Data Access: Analyzes the CS service based on the CS-related data on the RAN side. The LTE network does not involve this parameter. l RAN PS Data Access: Analyzes the PS service based on the PS-related data on the RAN side. Both access methods can be chosen.
NOTE l If you set the analysis scene to PS Core, you do not need to set the data type, because it only supports the PS data on the PS Core. l For UMTS NEs, the CS and PS service information is recorded in one CHR. The SAU cannot filter CHRs by service type. Therefore, after a complaint analysis support task is created, all service information is displayed in the analysis results even though only the CS or PS is selected.
Data Type 2
The system supports the following data on the CS domain and the PS domain: Control Plane: analyze the service based on the control plane data on the RAN side and the CN side.
Select NE(s)
RAN NE
Click Select to select an NE. The lowest level is the base station controller level.
Issue 01 (2013-07-15)
1421
Description Add or import the user alias, the IMSIs, and remarks of complaining users.
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.
User 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 user 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 user. Value range: A 15-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, obtain the encrypted IMSI of a VIP user 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.
CAUTION If the input IMSI of complaining user is the same as the VIP user in the VIP group management 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.
MSISDN
Add or export MSISDNs of complaining users. l It is only supported by the PS Core network. l When the anonymous policy is disabled on the network where the Nastar is deployed, enter the MSISDN of a user. Value range: A 1- to 16-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, the Nastar does not support analyzing using the MSISDN.
CAUTION If the input MSISDN of complaining user is the same as the VIP user in the VIP group management 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 MSISDN.
Issue 01 (2013-07-15)
1422
Description Add or export peer MSISDNs of complaining users. l It is only supported by the GSM network when choosing the CS service. l When the anonymous policy is disabled on the network where the Nastar is deployed, enter the MSISDN of a user. Value range: A 1- to 16-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, the Nastar does not support analyzing using the MSISDN.
CAUTION If the input peer MSISDN of complaining user is the same as the VIP user in the VIP group management 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 peer MSISDN.
Indicates the RAT of an NE. Indicates the domain of an NE. Domains include signaling planeCS, signaling plane-PS, signaling plane-integration. 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. 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.
Indicates the name of a KPI. Indicates the relationship between the KPI value and KPI 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 01 (2013-07-15)
1423
Parameter Date
Description 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 and the end time must precede the current system time.
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.
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. The value of this parameter must not precede the end time of Date.
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-51.
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 01 (2013-07-15)
1424
Issue 01 (2013-07-15)
1425
No.
Parame Description ter Button area Provides entries to three functions: l : Displays the complaint analysis support results geographically. For details, see Map Interface. l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview Table_Summary.file format. l : Exports data reports of complaint analysis support. The following two types of reports are exported. Each type has one report. The default format is .xlsx format. Information Table_Details_UMTS.file format. The exported data includes information about overview tables, subscribers, accesses, releases, handovers, and so on. Alternatively, right-click in area 3 and choose Export complaint analysis support reports to obtain this type of reports. Overview Table_Summary.file format. The same information with Overview Table_Summary.file format exported from summary reports of complaint analysis support. l provides the abnormal cause statistics function of the service. For details, see Common Statistics Interface.
Issue 01 (2013-07-15)
1426
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. 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-RNC call history records. If an interRNC 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. Click the column header to resort this table.
NOTE 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 the Signaling Procedure Before Call re area Release Tab Page.
Issue 01 (2013-07-15)
1427
No.
Parame Description ter Theme Displays detailed signaling process and MR information about all filtered analysis subscribers. The Nastar analyzes the mobility and service of those area subscribers. For details, see Description of the Measurement Information Before Call Release Tab Page, Description of Mobility Analysis Tab Page, and Description of Service Analysis Tab Page.
Displays detailed information about the selected subscriber in area 2, including user information, call access information, call release information, and statistical information. For details about parameters, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS). When the window is opened initially, the area hidden by default.
Issue 01 (2013-07-15)
1428
No. (1)
Description 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 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.
(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). 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.
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.
Issue 01 (2013-07-15)
1429
No. (1)
Description Lists detailed MR information before call release. The information includes time, measurement object type, and detailed counter information.
(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, minimum, and mediate values. l Counter change trend chart, displaying the change of counter values for a maximum of 20 MRs l Legend Table 4-33 describes the change trend of each measurement counters.
Issue 01 (2013-07-15)
1430
Table 4-33 Description of measurement counter change trend chart Counter Ec/No Statistic Indication Indicates the change trend of the signal intensity according to the received cells of the UE. Indicates the change trend of the signal level according to the received cells of the UE. Indicates the change trend of the RSSI according to the received intercells of the UE. Indicates the change trend of the RSRP according to the received LTE cells of the UE. Indicates the change trend of the RSRQ according to the received inter-cells of the UE. Indicates the change trend of the transmit power of the UE. Description Displayed as a broken line chart.
RSCP
RSSI
RSRP
RSRQ
UE Tx Power
For details, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS).
Figure 4-55 shows the items about the RAB service through the RAB analysis.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1431
Double-click one result, or right-click one result, and choose Detail Service Information, view the detailed service counters of CS domain or PS domain. Right-click one result, and choose Trend Analysis, view the throughput and throughput rate of the RAB on the uplink and downlink at the different time. For details, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS). Figure 4-55 Description of service analysis tab page (RAB)
Map Interface
. The map window (the Geographic Observation window) is displayed as shown in Click Figure 4-56. Figure 4-56 Map interface
Issue 01 (2013-07-15)
1432
No. (1)
Description Entry for basic operations in the map window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
l Complaint Analysis Support: Node for the complaint analysis support theme. A level-2 node under the node indicates a task name. A level-3 node under the node indicates a KPI, such as access/ release cell KPI. If multiple complaint analysis support results windows are open, only one of the windows can be displayed on the map window simultaneously. If a analysis result window is closed, the node for the window in the navigation tree is deleted accordingly. In addition, the rendered layer of the corresponding theme is deleted. (3) Geographic observation area Grid detail area Legend area Analysis results are displayed as icons in different colors.
(4) (5)
This area is empty for complaint analysis support. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the legends 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 is not imported, the system displays a message in this area.
l l
Select an executed GSM complaint analysis support task, and double-click an analysis result of the task in the Task Result area. Select an executed GSM complaint analysis support task, and double-click an analysis result of the task in the Task Result area. Right-click an analysis result of a task and choose View Analysis Result from the shortcut menu.
Main Window
The complaint analysis support results can be displayed in tables, such as call report overview table, subscriber information table, call access information table, call release information table, and handover information table, as shown in Figure 4-57. Figure 4-57 Complaint analysis support interface
Issue 01 (2013-07-15)
1434
No.
Parame Description ter Button area Provides entries to three functions: l : Displays the complaint analysis support results geographically. For details, see Map Interface. l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview Table_Summary.file format. l : Exports data reports of complaint analysis support. 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 complaint analysis support reports 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 complaint analysis support reports to obtain this type of reports. Overview Table_Summary.file format. The same information with Overview Table_Summary.file format exported from summary reports of complaint analysis support.
Issue 01 (2013-07-15)
1435
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. 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. Click the column header to resort this table.
NOTE 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.
Issue 01 (2013-07-15)
1436
No.
Parame Description ter 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.
Displays detailed information about the selected subscriber in area 2, including user information, call access information, call release information. For details about parameters, see 3.10.5 Reference for Complaint Analysis Support Parameters (GSM). When the window is opened initially, the area hidden by default.
Issue 01 (2013-07-15)
1437
No. (1)
Description 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. (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). 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.
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.
Issue 01 (2013-07-15)
1438
No. (1)
Description Lists detailed MR information before call release. The information includes time, measurement object type, and detailed counter information.
(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, minimum, and mediate values. l Counter change trend chart, displaying the change of counter values for a maximum of 20 MRs l Legend Table 4-34 describes the change trend of each measurement counters.
Issue 01 (2013-07-15)
1439
Table 4-34 Description of measurement counter change trend chart Counter TA DLRxLevel DLRxQuality /Level Helps identify abnormal releases caused by uplink or downlink interference. Statistic Indication Helps identify abnormal releases caused by poor coverage. Description Displayed as a bar chart. The value ranges from 0 to 63. Displayed as a broken line graph. The value ranges from -47 to -110. 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. 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 Helps identify abnormal releases caused by unbalanced uplink and downlink by analyzing this KPI with DLRxQuality/Level and ULRxQuality/Level. Displays voice quality changes in the process, help evaluate the quality accurately. 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. UL VQI: displayed as a bar chart. The value ranges from 0 to 50. DL VQI: displayed as a broken line graph. The value ranges from 0 to 50.
ULRxQuality /Level
MS/BTS Power
VQI
For details about parameters, see 3.10.5 Reference for Complaint Analysis Support Parameters (GSM).
Map Interface
Click . The map window (the Geographic Observation window) is displayed as shown in Figure 4-61.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1440
No. (1)
Description Entry for basic operations in the map window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
l Complaint Analysis Support: Node for the complaint analysis support theme. A level-2 node under the node indicates a task name. A level-3 node under the node indicates a KPI, such as access/ release cell KPI. If multiple complaint analysis support results windows are open, only one of the windows can be displayed on the map window simultaneously. If a analysis result window is closed, the node for the window in the navigation tree is deleted accordingly. In addition, the rendered layer of the corresponding theme is deleted.
Issue 01 (2013-07-15)
1441
No. (3)
(4) (5)
This area is empty for complaint analysis support. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the legends 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 is not imported, the system displays a message in this area.
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-62.
Issue 01 (2013-07-15)
1442
Issue 01 (2013-07-15)
1443
No.
Parame Description ter Button area Provides entries to three functions: l : Displays the complaint analysis support results geographically. For details, see Map Interface. l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview Table_Summary.file format. l : Exports data reports of complaint analysis support. The following two types of reports are exported. Each type has one report. The default format is .xlsx format. Information Table_Details_LTE.file format. The exported data includes information about overview tables, subscribers, accesses, releases, and handovers. Alternatively, right-click in area 3 and choose Export complaint analysis support reports to obtain this type of reports. Overview Table_Summary.file format. The same information with Overview Table_Summary.file format exported from summary reports of complaint analysis support.
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.
Issue 01 (2013-07-15)
1444
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. column header to resort this table.
Click the
NOTE 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 the Signaling Procedure Before Call re area Release Tab Page. Theme Displays detailed signaling process and MR information about all filtered analysis subscribers. The Nastar analyzes the mobility and service of all filtered area subscribers. For details, see Description of the MR Analysis Page, Description of the E-RAB Analysis Tab Page and Description of the Mobility Analysis Tab Page.
Displays detailed information about the selected subscriber in area 2, including user information, call access information, call release information. For details about parameters, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE). When the window is opened initially, the area hidden by default.
Issue 01 (2013-07-15)
1445
No. (1)
Description 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. 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). 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.
(2)
Signaling flowchart
Issue 01 (2013-07-15)
1446
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).
Map Interface
Click . The map window (the Geographic Observation window) is displayed as shown in Figure 4-67.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1447
No. (1)
Description Entry for basic operations in the map window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
l Complaint Analysis Support: Node for the complaint analysis support theme. A level-2 node under the node indicates a task name. A level-3 node under the node indicates a KPI, such as access/ release cell KPI. If multiple complaint analysis support results windows are open, only one of the windows can be displayed on the map window simultaneously. If a analysis result window is closed, the node for the window in the navigation tree is deleted accordingly. In addition, the rendered layer of the corresponding theme is deleted. (3) Geographic observation area Analysis results are displayed as icons in different colors.
Issue 01 (2013-07-15)
1448
Description This area is empty for complaint analysis support. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the legends 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 is not imported, the system displays a message in this area.
Navigation Path
Use either of the following methods to open the interface that displays PS core complaint analysis support results: l l Select a finished PS core 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 Result from the shortcut menu.
Interface
PS core complaint analysis support results can be displayed in tables to show CHR summary information, CHR information, subscriber information, and procedure information, as shown in Figure 4-68.
Issue 01 (2013-07-15)
1449
Issue 01 (2013-07-15)
1450
No. 1
Description Provides entries to three functions: l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview table_Summary.file format. l : Exports data reports of complaint analysis support. The exported data includes information about overview tables, subscribers, call accesses, call releases, and call handovers. Alternatively, right-click in area 3 and choose Export complaint analysis support reports to obtain this type of reports. l provides the traffic statistics function. For details, see Traffic Statistics on the Interface.
Navigati l Upper part: Displays the service types. You can select the service types. on tree l Middle part: Call records of multiple subscribers are displayed by cause of the type in the navigation tree mode. (N) after each node indicates the number CHR 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. summar In Cause type-User ID: Alias mode, all filtered call records are y of classified by cause type and the call records of each cause type are complai then classified by User ID: Alias. ning 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.
Issue 01 (2013-07-15)
1451
No. 3
Description Displays an overview of all filtered records, such as time, cell, procedure, and exception cause. Each row indicates one call record. row is abnormal. Click the indicates that the call record in the
NOTE For some columns (such as User ID: Alias), the system only centralized display the same content, but there is no display order after resorting.
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 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 3.10.8 Reference for Complaint Analysis Support Parameters (PS Core). The table is hidden by default when you initially open the window.
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 GGSN Procedure or SAE-GW Procedure under Service Type. Traffic subnodes are displayed under Root. 2. Select a Traffic subnode to view traffic information by subscriber.
Function Description
The Nastar allows you to perform complaint analysis support based on the data collected from different types of networks simultaneously. For example, it allows you to perform GSM/UMTS complaint analysis support and LTE FDD/LTE TDD complaint analysis support. It also allows you to perform complaint analysis support based on the data collected from the RAN and the PS core network simultaneously. Therefore, the Nastar supports combined complaint analysis support in the following combinations of RATs: GSM/UMTS, LTE FDD/LTE TDD, GSM/PS Core, UMTS/PS Core, LTE TDD/PS Core, LTE FDD/PS Core, GSM/UMTS/PS Core, and LTE FDD/LTE TDD/PS Core.
Navigation Path
Use either of the following methods to open the interface that displays combined complaint analysis support results: l 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 Result from the shortcut menu.
Interface description
The interface that displays the combined complaint analysis support results of multiple RATs is generally the same as the interface that displays the complaint analysis support results of a single RAT: l The service types displayed in the navigation tree are combinations of the service types for the complaint analysis support of involved RATs. For example, if the service types for GSM complaint analysis support include RAN CS (Call\SMS\others) and the service types for UMTS complaint analysis support include RAN NET, RAN CS (AMR\VP\SMS\others)), RAN PS, and RAN Multi, the service types for GSM/UMTS complaint analysis support include RAN NET, RAN CS (AMR\VP\Call \SMS\others), RAN PS, and RAN Multi. l The cause types displayed in the navigation tree are combinations of the cause types for the complaint analysis support of involved RATs. The description of the exception causes for each RAT provides the mapping between service types and cause types. For details, see 3.10.9 Appendix: Exception Cause Classification / Key Signaling. l The information displayed in the middle and right areas on the interface varies according to the call history record (CHR) that you select in the navigation tree. One CHR belongs to only one RAT. Therefore, for descriptions of related interfaces and parameters, see the interface reference for the complaint analysis support of each RAT.
Issue 01 (2013-07-15)
1453
Summary
Param eter Serial Numbe r Range (0,2^31-1) Uni t N/A Description 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. 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. ! Blank N/A Whether a call record is abnormal. 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. Abnor mal Cause For details, see "Appendix: Exception Cause Classificatio n/ Enumeration Values of Failure Cause (UMTS)". 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. BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Combi ned
N/A
N/A
Status
Networ k
N/A
Issue 01 (2013-07-15)
1454
Range Static reloc in HHO reloc in Cell update reloc in Inter RAT handover in RRC setup without DRD RRC setup with DRD
Uni t N/A
Issue 01 (2013-07-15)
1455
Range Originating Conversation al Call Originating Streaming Call Originating Interactive Call Originating Background Call Originating Subscribed traffic Call Terminating Conversation al Call Terminating Streaming Call Terminating Interactive Call Terminating Background Call Emergency Call Inter-RAT cell reselection Inter-RAT cell change order Registration Detach Originating High Priority Signaling Originating Low Priority Signaling
Uni t N/A
Issue 01 (2013-07-15)
1456
Param eter
Range Call reestablishmen t Terminating High Priority Signaling Terminating Low Priority Signaling Terminating - cause unknown MBMS reception MBMS ptp RB request
Uni t
Description
Supported NE Version
Access Time Access Cell Release Time Release Cell User ID:Alia s
N/A
N/A
Same as Access Information -> RRC Request Time. Same as Access Information -> Cell on RRC Setup. Same as Release Information -> RRC Release Time Same as Release Information -> RRC Release Cell Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
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.
Termin al Model
N/A
N/A
Model of a UE. The UE model can be queried using terminal type management based on the IMEI-TAC of the UE.
Issue 01 (2013-07-15)
1457
Range [0,+)
Uni t Seco nd
Description Duration of a call, including service duration and signaling duration. Call duration = Release time - Access time.
CS Reques ted Service Type CS Service Duratio n PS Reques ted Service Type PS RAB Duratio n RRC Setup Failure Cause
AMR VP
N/A
[0,+)
Seco nd
N/A
Seco nd
For details, see "Access information/ RRC Setup Failure Cause". N/A
N/A
IU Release Cause
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.
N/A
N/A
Cause of CS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
Issue 01 (2013-07-15)
1458
Range N/A
Uni t N/A
Description Cause of CS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
N/A
N/A
Cause of PS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
N/A
N/A
Cause of PS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
User Information
Param eter TMSI/ PTMSI Range 0000000-FFFFFFFF Uni t N/A Description 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. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1459
Range N/A
Uni t N/A
Description Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
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.
Termin al Model
N/A
N/A
Model of a UE. The UE model can be queried using terminal type management based on the IMEI-TAC of the UE.
Termin al Operati ng System UE Capabil ity >Proto col Versio n >Power Class
For details, see the OS description of the UMTS terminal analysis. N/A
N/A
N/A
Capability of a UE.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
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.
Issue 01 (2013-07-15)
1460
Range Band I 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 Band XVI Band XVII Band XVIII Band XIX Band XX Band XXI Band XXII Reserved
Uni t N/A
Description Universal Terrestrial Radio Access (UTRA) frequency bands supported by a UE. For details, see Table 5.0 "UTRA FDD frequency bands" under "UE Radio Transmission and Reception (FDD)" in 3GPP TS 25.101.
>HSPA Capabil ity >>HSDSCH Capabil ity >>EDCH Capabil ity >>Sup port ERACH
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[1,64]
N/A
HSDPA capability of a UE. A larger value of this parameter indicates larger HSDPA capability. HSUPA capability of a UE. A larger value of this parameter indicates larger HSUPA capability. Whether a UE supports ERACH.
[1,16]
N/A
supported unsupported
N/A
Issue 01 (2013-07-15)
1461
Param eter >>Sup port EFACH >>Sup port DTXD RX >>Sup port HSSCCH Less Operati on >Mobil ity Capabil ity
Uni t N/A
Description Whether a UE supports EFACH. Whether a UE supports discontinuous transmission (DTX) and discontinuous reception (DRX). Whether a UE supports HSSCCH.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
supported unsupported
N/A
Support of GSM 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 Support of UTRAN to GERAN NACC Support of Handover to GAN Support of PS Handover to GAN Reserved
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.
Issue 01 (2013-07-15)
1462
Param eter >Suppo rt EUTRA Band Capabil ity >Positi oning Capabil ity
Uni t N/A
Description Evolved Universal Terrestrial Radio Access (E-UTRA) frequency bands supported by a UE.
Standalone location method(s) supported UE based OTDOA supported GANSS support indication Support for GPS timing of cell frames measurement Support for IPDL Support for Rx-Tx time difference type2 measurement Support for UP assisted GPS measurement validity in CELL_PCH and URA_PCH states Support for SFNSFN observed time difference type 2 measurement Network Assisted GPS support
N/A
Access Information
Param eter RRC Request Time Range N/A Uni t N/A Description Time of signaling access during a call. That is, timestamp in the RRC CONNECTION SETUP message. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1463
Param eter RRC Radio Link Setup Time Cell on RRC Setup
Range N/A
Uni t N/A
Description Time of RRC radio link setup during a call. That is, timestamp in the RADIO LINK SETUP REQUEST message. Name of the cell to which signaling accesses. 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.
N/A
N/A
N/A
N/A
Target cell of Directed Retry Decision (DRD) during signaling access. 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.
SRB on FACH_RACH SRB on DCH_DCH SRB on HSDSCH_RACH SRB on HSDPA_DCH SRB on DCH_HSUPA SRB on HSDPA_HSUPA
N/A
Issue 01 (2013-07-15)
1464
Range Static reloc in HHO reloc in Cell update reloc in Inter RAT handover in RRC setup without DRD RRC setup with DRD
Uni t N/A
Description Value of RRC Connection Setup Type carried in the RRC CONNECTION SETUP message: Incoming migration (Static reloc in) 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) Incoming inter-RAT handover (Inter RAT handover in) RNC access (RRC setup without DRD) RNC access (RRC setup with DRD)
Issue 01 (2013-07-15)
1465
Range Originating Conversational Call Originating Streaming Call 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 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 MBMS ptp RB request
Uni t N/A
Description Cause of RRC setup. For details, see 3GPP TS 25.331-10.3.3.11 "Establishment cause."
Issue 01 (2013-07-15)
1466
Uni t N/A
Description Whether RRC setup is triggered by service or non-service causes based on RRC Setup Cause. The rules for determining the trigger conditions are as follows: 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.
CS PS
N/A
Whether RRC setup occurs in the CS or PS domain based on RRC Setup Cause.
Issue 01 (2013-07-15)
1467
Uni t N/A
Description Whether RRC setup occurs on the MOC or MTC side based on RRC Setup Cause. The rules for determining the occurrence conditions are as follows: 1. RRC setup occurs on the MOC side when the value of RRC Setup Cause is any of the following: Originating Conversational Call Originating Streaming Call Originating Interactive Call Originating Background Call Originating Subscribed traffic Call Originating High Priority Signaling Originating Low Priority Signaling Emergency Call 2. RRC setup occurs on the MTC side when the value of RRC Setup Cause is any of the following: 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 01 (2013-07-15)
1468
Uni t N/A
Description Whether RRC setup is triggered by SMS or non-SMS causes based on RRC Setup Cause. The rules for determining the trigger conditions are as follows: 1. RRC setup is triggered by SMS causes when the value of RRC Setup Cause is any of the following: Originating High Priority Signaling Originating Low Priority Signaling Terminating High Priority Signaling Terminating Low Priority Signaling 2. Otherwise, RRC setup is triggered by non-SMS causes.
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
N/A
Error Type.
>Error Reason
N/A
Error Reason.
N/A
1469
Range [0,+)
Uni t Seco nd
Description Delay on RRC setup. The statistical points are as follows: 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. Inter-RAT handover: Timestamp in the RELOCATION REQUEST message - Timestamp in the UTRAN MOBILITY INFORMATION CONFIRM message.
Yes No
N/A
Overlong RRC setup delay occurs when the RRC setup delay exceeds the overlong delay threshold limit. The abnormal threshold is set by engineers during analysis task creation.
N/A
N/A
N/A
N/A
Cell on which RAB setup is requested. 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.
>TP
[0,3069 ]
N/A
Time Propagation (TP) is a term defined by Huawei to indicate time propagation delay during UE access.
Issue 01 (2013-07-15)
1470
Range Yes No
Uni t N/A
Description 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. Remark: If the active set contains multiple cells during access, the counters for all the cells in this active set are analyzed.
[-24,0]
dB
Ec/No of the serving cell on RRC setup. If "Ec/No" is smaller than "Ec/No abnormal threshold on RRC setup", it indicators that the Ec/No is abnormal on RRC setup. Abnormal threshold is set when creating tasks. Remark: If the active set contains multiple cells during access, the counters for all the cells in this active set are analyzed.
Yes No
N/A
>RSCP
[-115,-25]
dBm
RSCP of the serving cell on RRC setup. If "RSCP" is smaller than "RSCP abnormal threshold on RRC setup", it indicators that the RSCP is abnormal on RRC setup. Abnormal threshold is set when creating tasks. Remark: If the active set contains multiple cells during access, the counters for all the cells in this active set are analyzed.
Yes No
N/A
Issue 01 (2013-07-15)
1471
Release Information
Param eter RRC Release Time Range N/A Unit N/A Description Release time of RRC connection. That is, timestamp in the RRC CONNECTION RELEASE message. [0,+) Seco nd Duration of a call. Call duration = RRC release time - RRC setup request time Name of the cell from which signaling is released. The parameter value is displayed in the following format: RNC name:cell name (RNCID: cellID). 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. Successful Failed N/A N/A Release cause carried in the last IU RELEASE COMMAND message received by an RNC. Type of failure cause. For details, see 3GPP 25.413-9.2.1.4. N/A RRC release results. Supported NE Version BSC6900 V900R013C00 or later version
Duratio n
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Radio Network Layer Cause Transport Layer Cause NAS Cause Protocol Cause Miscellaneous Cause Non-standard Cause Radio Network Layer Cause Extension
N/A
>Cause value
N/A
N/A
Issue 01 (2013-07-15)
1472
Statistical Information
Param eter Soft Handov er Info >Soft Handov er Request s >Succe ssful Soft Handov ers >Softer Handov er Request s >Succe ssful Softer Handov ers Hard Handov er Info >IntraFreq Handov er Request s >Succe ssful IntraFreq Handov ers Range N/A Unit N/A Description Soft handover information. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Num ber
Number of soft handover requests, including soft handover requests and softer handover requests.
[0,+)
Num ber
Number of successful soft handovers, including successful soft handovers and successful softer handovers. Number of softer handover requests.
[0,+)
Num ber
[0,+)
Num ber
N/A
N/A
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
1473
Param eter >InterFreq Handov er Request s >Succe ssful InterFreq Handov ers InterRAT Handov er Info >InterSystem Outgoin g Handov er Request s(CS) >InterSystem Outgoin g Handov er Request s(PS) >Succe ssful InterSystem Outgoin g Handov ers
Range [0,+)
[0,+)
Num ber
N/A
N/A
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
1474
Param eter >InterSystem Incomi ng Handov er Request s >Succe ssful InterSystem Incomi ng Handov ers DCCC Info >DCCC Speed Increas e Initializ ation Times >DCCC Speed Increas e Success Times >DCCC Speed Decreas e Initializ ation Times >DCCC Speed Decreas e Success Times
Range [0,+)
[0,+)
Num ber
N/A
N/A
DCCC information.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
1475
Param eter RAB Info >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (AMR) >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (VP) >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (PS)
Range N/A
Unit N/A
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Num ber
Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for the AMR service.
[0,+)
Num ber
Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for the VP service.
[0,+)
Num ber
Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for PS services. In which, PS services include the PS R99 service, HSDPA service, HSUPA, service, and HSPA service.
Issue 01 (2013-07-15)
1476
Param eter >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (HSDP A) MultiRAB Info >Abnor mal CS Release due to PS Release >Abnor mal CS Release due to PS Service Setup >Releas ed RABs in CS Domain Trigger ed by the Failure in Securit y Mode
Range [0,+)
Description Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for the HSDPA service.
N/A
N/A
Multi-RAB information.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
1477
Param eter >Releas ed RABs in PS Domain Trigger ed by the Failure in Securit y Mode >Setup Attempt s of Combin ed Service (CS + PS) >Succe ssful Setups of Combin ed Service (CS + PS) >CS plus PS multiRAB CS normal release times >CS plus PS multiRAB CS abnorm al release times
Range [0,+)
Description Number of released RABs in the PS domain triggered by failed security authentication.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
1478
Param eter >CS plus PS multiRAB PS normal release times >CS plus PS multiRAB PS abnorm al release times >Setup Attempt s of Combin ed Service (PS + PS) >Succe ssful Setups of Combin ed Service (PS + PS) >Norm al Release s of Combin ed Service (PS + PS)
Range [0,+)
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
1479
Param eter >Abnor mal Release s of Combin ed Service (PS + PS) Statistic s of Voice Quality in CS Domain >OneWayAudio Times >Noise Times
Range [0,+)
N/A
N/A
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
1480
Range 1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
Unit N/A
Traffic class: conversational streaming interactive background Traffic type: CS_AMR CS_VP CS_OTHER PS_GENERAL PS_HSDPA PS_HSUPA PS_HSPA ...
N/A
RAB request service type consists of two parts: Traffic class and Traffic type. The parameter value is displayed in the format of Traffic class/ Traffic type. For details about Traffic class, see 3GPP 25.413. Traffic type is a service type defined by Huawei in terms of radio access bearer (RAB).
N/A
N/A
Time when RAB setup is requested. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT REQUEST message. Incoming migration: Timestamp in the RELOCATION COMPLETE message. Inter-RAT handover: Timestamp in the HANDOVER TO UTRAN COMPLETE message.
Issue 01 (2013-07-15)
1481
Range N/A
Unit N/A
Description Cell on which RAB setup is requested. The parameter value is displayed in the following format: RNC 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.
[0,+)
Seco nd
Time when RAB setup completes. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT RESPONSE message. Incoming migration: The time is not recorded. Inter-RAT handover: The time is not recorded.
N/A
N/A
Best cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Service cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
>DRD Info
N/A
N/A
Information about DRDs during RAB setup, recording the last three DRDs at most.
Issue 01 (2013-07-15)
1482
Range N/A
Unit N/A
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Target cell of the current DRD. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
N/A
DRD failure cause. For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
>>>>Er ror Type >>>>Er ror Reason >>Peer Info >>>Pee r MSISD N
For details, see the "Enumeration Values of Failure Cause". For details, see the "Enumeration Values of Failure Cause". N/A
N/A
Error type.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
Error reason.
N/A
N/A
Mobile station international ISDN BSC6900 number (MSISDN) of the peer UE. V900R013C00 MSISDN is a 15-digit numeric or later version string of decimal digits (0-9). For details, see 3GPP TS 23.003.
Issue 01 (2013-07-15)
1483
Range DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
Description Type of an uplink or downlink data transmission channel after RAB setup. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
1484
Range [0,+)
Unit kbps
Description 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. In which, When UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/s. When UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/ s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>RAB Setup Result >RAB Setup Failure Time >RAB Setup Failure Cause >>Error Type
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Error type.
Issue 01 (2013-07-15)
1485
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
Unit N/A
>RAB Setup Delay Estimat ion >>RAB Setup Delay >>Over long RAB Setup Delay
N/A
[0,+)
Seco nd N/A
RAB setup delay = Time when RAB setup completes - Time when RAB setup is requested. Overlong RAB setup delay occurs when the RAB setup delay exceeds the overlong delay threshold limit. The overlong delay threshold is set by engineers during analysis task creation.
Yes No
[0,+)
Seco nd
Call setup delay = Time when RAB setup completes - Time when RRC setup is requested. Call setup delay = RAB setup delay + RRC setup delay. Note that this parameter is applicable only to the first RAB after RRC setup.
Yes No
N/A
Overlong call setup delay occurs when the call setup delay exceeds the overlong delay threshold limit. The overlong delay threshold is set by engineers during analysis task creation.
N/A
N/A
Service request time, that is, the timestamp of "Service Request" message.
Issue 01 (2013-07-15)
1486
Range [0,+)
Unit Seco nd
Description 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 COMPLETE message Timestamp in the RADIO BEARER RECONFIGURATION message.
N/A
N/A
Time of outgoing call alerting during a call. Statistical point: Timestamp in the ALERTING message. 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. Outgoing call alerting delay = Alerting time - RRC setup request time.
N/A [0,+)
N/A
Issue 01 (2013-07-15)
1487
Unit N/A
Description 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 Yes in the following conditions: The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MOC. Outgoing call alerting delay > Overlong outgoing call alerting delay threshold (MOC). The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MTC. Outgoing call alerting delay > Overlong outgoing call alerting delay threshold (MTC). 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.
>>Conn ect Ack Time >>Call Comple tion Delay (Conne ct Ack)
N/A
N/A
Time of incoming call alerting during a call. Statistical point: Timestamp in the CONNECT ACKNOWLEDGE message. 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. Incoming call alerting delay = Connect Ack time - RRC setup request time.
[0,+)
Seco nd
Issue 01 (2013-07-15)
1488
Param eter >>Over long Call Comple tion Delay (Conne ct Ack)
Unit N/A
Description 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 Yes in the following conditions: The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MOC. Incoming call alerting delay > Overlong incoming call alerting delay threshold (MOC). The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MTC. Incoming call alerting delay > Overlong incoming call alerting delay threshold (MTC). 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.
>RAB Setup Process >>Queu ing Indicato r >>Intra -system DRD Indicato r
N/A
N/A
Process information of RAB setup. This parameter is used with RAB Setup Failure Cause to analyze problems. TRUE(1) indicates that queuing occurs.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
False True
N/A
False True
N/A
Issue 01 (2013-07-15)
1489
Param eter >>Inter -system DRD Indicato r >RAB Resourc e Congest ion Informa tion on RAB Setup >>Cong estion Time >>Cong estion Cell ID >>Cong estion Status
Unit N/A
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.
N/A
N/A
Time when radio resource congestion occurs. Cell where radio resource congestion occurs. Cause of radio resource congestion.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Code DL CE 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
N/A
N/A
N/A
Issue 01 (2013-07-15)
1490
Range 1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
Unit N/A
>Single -RAB Abnor mal Release Indicato r >Multip le-RAB Abnor mal Release Indicato r >RAB Release Time
False True
N/A
False True
N/A
N/A
N/A
Time when RAB release completes. The statistical points are as follows: Normal release and CN abnormal release: RAB release time = Timestamp in the IU RELEASE COMMAND or RAB ASSIGNMENT REQUEST message.
>RAB Duratio n
[0,+)
Seco nd
Issue 01 (2013-07-15)
1491
Range Yes No
Unit N/A
Description If "RAB Duration" is smaller than "RAB Duration shorter threshold", it indicators that the RAB duration is too shorter. Abnormal threshold is set when creating tasks.
N/A
N/A
Best cell before RAB release. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Serving cell before RAB release. The parameter value is displayed in the following format: RNC 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.
Issue 01 (2013-07-15)
1492
Range DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
Description Type of an uplink or downlink data transmission channel before RAB release. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
1493
Range [0,+)
Unit kbps
Description Uplink and downlink RB rate after RAB setup and before RAB release. The parameter value is displayed in the format of UL RB bitrate after RAB setup/DL RB bitrate after RAB setup. In which, When UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/s. When UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/ s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>Disco nnect Cause >Disco nnect Directio n >RAB Release Failure Cause
N/A
N/A
Cause carried in the DISCONNECT message. For details, see 3GPP 24.008-10.5.4.11. Direction for sending the DISCONNECT message.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
from UE from CN
N/A
N/A
N/A
Issue 01 (2013-07-15)
1494
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
Unit N/A
>>Error Reason
N/A
Error reason.
N/A
Time when RAB release fails. That is, when the system receives the following timestamp: IU RELEASE REQUEST RAB RELEASE REQUEST
RAB Process Info >RAB Setup Delay Estimat ion >>Disc onnect time >>Servi ce Duratio n
N/A
N/A
N/A
N/A
N/A
N/A
Time when a call completes. Statistical point: timestamp in the DISCONNECT message. Service duration = Disconnect time - Connect Ack time.
[0,+)
Seco nd
Issue 01 (2013-07-15)
1495
Unit N/A
Description 1.The parameter value is Yes in the following conditions: When the current RAB is not the first RAB after RRC setup and Call duration < Short call threshold. The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MOC. Call duration < Short call threshold (MOC). The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MTC. Call duration < Short call threshold (MTC). 2.The parameter value is No in the other conditions. The short call threshold, short call threshold (MOC), and short call threshold (MTC) are set by engineers during task creation.
Issue 01 (2013-07-15)
1496
Range N/A
Unit N/A
Description Statistics on SQIs 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. 2. The RNC can statistics based on the average SQI value and divides signal quality into different levels according to SQI values: RAN14.0: Excellent (SQI<= (400,500]), Good (SQI<= (300,400]), Accept (SQI<= (200,300]), Poor (SQI<= (100,200]), Bad (SQI<=[0,100]). RAN13.0 and earlier: Good (SQI <= (300,500]), Accept (SQI <= (200,300]), Bad (SQI <=(0,200]). The segment intervals of levels can be modified by running the SET USQICOUNT command on the RNC.
[0,500]
N/A
Yes No
N/A
If SQI average < Abnormal SQI threshold, The value of this parameter is Yes. Otherwise, the value is No. The abnormal SQI threshold is set by engineers during task creation.
[0,100]
Proportion of voice quality with SQI as Excellent from RAB setup to RAB release.
Issue 01 (2013-07-15)
1497
Param eter >>Radi o of Good SQIs (%) >>Radi o of Accept SQIs (%) >>Radi o of Poor SQIs (%) >>Radi o of Bad SQIs (%) >BLER Statistic Info
Range [0,100]
Unit %
Description Proportion of voice quality with SQI as Good from RAB setup to RAB release.
[0,100]
Proportion of voice quality with SQI as Accept from RAB setup to RAB release.
[0,100]
Proportion of voice quality with SQI as Poor from RAB setup to RAB release.
[0,100]
Proportion of voice quality with SQI as Bad from RAB setup to RAB release. Statistics on BLERs. 1. Block error rate (BLER) indicates signal quality on the 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%.
N/A
N/A
[0,+)
Num ber
N/A
Issue 01 (2013-07-15)
1498
Param eter >Statist ics on Last Receive d Blocks >>Num ber of UL Total Blocks (1~5)
Range N/A
Unit N/A
Description Statistics on received blocks before link release. The statistical period is 2.56 seconds.
[0,+)
Num ber
Total number of UL blocks received within the five periods before link release. The parameter value is displayed 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.
[0,+)
Num ber
Number of UL error blocks received within the five periods before link release. The parameter value is displayed in this format: Number of UL error blocks received in period 1/ Number of UL error blocks received in period 2/.../Number of UL error blocks received in period 5.
N/A
N/A
Statistics on uplink one-way audio. 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.
N/A
N/A
Time when uplink one-way audio occurs. Cell when uplink one-way audio occurs.
N/A
N/A
Issue 01 (2013-07-15)
1499
Range N/A
Unit N/A
Description Statistics on downlink one-way audio. The downlink one-way audio problems fall into two types: 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. 2. The RNC records a downlink one-way audio problem when it detects a large BLER value. This function is available only when a VIP subscriber enables periodic DL BLER reporting. The RNC records a maximum of the first three downlink one-way audio problems during each call of a UE.
N/A
N/A
Time when a downlink one-way audio problem occurs. Cell when a downlink one-way audio problem occurs. Statistics on noises. 1. The RNC records a noise problem. 2. The RNC records only the first one noise problem during each call of a UE.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
Time when a noise problem occurs. Cell when a noise problem occurs.
N/A
N/A
Issue 01 (2013-07-15)
1500
Issue 01 (2013-07-15)
1501
Range N/A
Unit N/A
Description Time for requesting RAB setup. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT REQUEST message. Incoming migration: Timestamp in the RELOCATION COMPLETE message. Inter-RAT handover: Timestamp in the HANDOVER TO UTRAN COMPLETE message.
N/A
Cell on which RAB setup is requested. The parameter value is displayed in the following format: RNC 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.
[0,+)
Seco nd
Time when RAB setup completes. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT RESPONSE message. Incoming migration: The time is not recorded. Inter-RAT handover: The time is not recorded.
N/A
Best cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
Issue 01 (2013-07-15)
1502
Range N/A
Unit N/A
Description Serving cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Information about DRDs during RAB setup, recording the last three DRDs at most. The N DRD record.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Target cell of the current DRD. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
N/A
DRD failure cause. For details, see the Failure Cause tab page.
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)"
N/A
Error type.
Issue 01 (2013-07-15)
1503
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
N/A
Type of an uplink or downlink data transmission channel after RAB setup. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
1504
Range [0,+)
Unit bps
Description DL/UL 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. In which, If UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/ s. If UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>UL/ [0,+) DL RAB Negotia ted Rate Overlo Yes w UL No RAB Negotia ted Rate
bps
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. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
1505
Param eter
Range
Unit N/A
Description If "Overlow DL RAB Negotiated Rate" is smaller than "Overlow DL RAB Negotiated Rate Threshold", the record has the problem that the overlow DL RAB vegotiated rate is too small. The abnormal threshold is set when creating tasks.
>RAB Setup Result >RAB Setup Failure Time >RAB Setup Failure Cause >>Error Type
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
N/A
Error type.
>>Error Reason
N/A
Error reason.
N/A
[0,+)
Seco nd
RAB setup delay = Time when RAB setup completes - Time when RAB setup is requested.
Issue 01 (2013-07-15)
1506
Range Yes No
Unit N/A
Description Overlong RAB setup delay occurs when the RAB setup delay exceeds the overlong delay threshold limit. The overlong delay threshold is set by engineers during analysis task creation.
[0,+)
Seco nd
1.When the following scene occurs, it displays "N/A". Scene: the first RAB after the RAB (Non-RRC) setup. 2.When the following scene occurs, it displays the result value. Scene: the first RAB after the RAB (RRC) setup. Call connection delay = Time when RAB setup completes Time when RRC setup is requested. Call connection delay = RAB setup delay + RRC setup delay.
Yes No
N/A
1.When the following scene occurs, it displays "N/A". Scene: the first RAB after the RAB (Non-RRC) setup. 2.When the following scenes occur, it displays the result value. Scene: the first RAB after the RAB (RRC) setup; and "RRC Setup Flag(MOC/MTC)" is "MOC"; and "Call Setup Delay" is larger than "Latency on Call Connection (MOC) ". Scene: the first RAB after the RAB (RRC) setup; and "RRC Setup Flag(MOC/MTC)" is "MTC"; and "Call Setup Delay" is smaller than "Latency on Call Connection (MTC) ". 3.When the other scene occurs, it displays "No". The threshold is set by engineers during analysis task creation.
Issue 01 (2013-07-15)
1507
Range N/A
Unit N/A
Description Time of service request. That is, when the system receives the Service Request timestamp. 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 COMPLETE message Timestamp in the RADIO BEARER RECONFIGURATION message.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Seco nd
>Sched uling Priority >>Allo cation/ Retenti on Priority >>>Pri ority Level
N/A
N/A
Scheduling priority during RAB setup. Allocation/retention priority. For details, see 3GPP 25.413-9.2.1.3.
N/A
N/A
[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.
N/A
1508
Param eter >>>Pre emptio n Vulnera bility >>>Qu euing Allowe d >>Traff ic Handlin g Priority
Unit N/A
Description Whether resources of the current RAB can be preempted by other RABs.
N/A
N/A
Priority level in the allocation and retention of system resources. For details, see 3GPP 25.433-9.2.1.1A. 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.
[0,15]
N/A
HS-DSCH scheduling priority. For details, see 3GPP 25.433-9.2.1.53H. The value range is [0,15]. A larger value indicates higher priority.
N/A
N/A
Issue 01 (2013-07-15)
1509
Range 1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
Unit N/A
>Single -RAB Abnor mal Release Indicato r >Multi pleRAB Abnor mal Release Indicato r >RAB Release Time
False True
N/A
False True
N/A
N/A
N/A
Time when RAB release completes. The statistical points are as follows: Normal release and CN abnormal release: RAB release time = Timestamp in the IU RELEASE COMMAND or RAB ASSIGNMENT REQUEST message.
>RAB Duratio n
[0,+)
Issue 01 (2013-07-15)
1510
Range N/A
Unit N/A
Description Best cell before RAB release. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Serving cell before RAB release. The parameter value is displayed in the following format: RNC 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.
UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
N/A
Type of an uplink or downlink data transmission channel before RAB release. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
1511
Range [0,+)
Unit kbps
Description UL/DL RB rate after RAB setup and before RAB release. The parameter value is displayed in the format of UL RB bitrate after RAB setup/DL RB bitrate after RAB setup. In which, If UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/ s. If UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>DP Deactiv ate Cause >RAB Release Failure Cause >>Error Type
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. Cause of abnormal RAB release.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Error type.
Issue 01 (2013-07-15)
1512
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
Unit N/A
N/A
Time when RAB release fails. That is, when the system receives the following timestamp: IU RELEASE REQUEST RAB RELEASE REQUEST
RAB Process Info >PDP Activat e Request Time >PDP Activat e Ack Time >PDP Deactiv ate Time >BLER Statistic Info
N/A
N/A
N/A
N/A
N/A
N/A
Timestamp in the PDP ACTIVIATE ACKNOWLEDGE message. Timestamp in the DEACTIVATE PDP CONTEXT REQUEST message. Statistical information about BLERs. 1. Block error rate (BLER) indicates signal quality on the 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%.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1513
Param eter >>Time s UL Service BLER Falls into Levels 1 to 6 >Statist ics on Last Receive d Blocks >>Num ber of UL Total Blocks (1~5)
Range [0,+)
Description N/A
N/A
N/A
Statistics on received blocks before link release. The statistical period is 2.56 seconds.
[0,+)
Num ber
Total number of UL blocks received within the five periods before link release. The parameter value is displayed 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.
[0,+)
Num ber
Number of UL error blocks received within the five periods before link release. The parameter value is displayed in this format: Number of UL error blocks received in period 1/ Number of UL error blocks received in period 2/.../Number of UL error blocks received in period 5.
N/A
N/A
[0,+)
Num ber
Number of uplink radio bearer resets after multiple RLC retransmissions fail in acknowledged mode.
Issue 01 (2013-07-15)
1514
Range [0,+)
Description Number of downlink radio bearer resets after multiple RLC retransmissions fail in acknowledged mode. Proportion that the amount of transmission data is zero. HSDPA is High Speed Downlink Packet Access for short. This counter is available only in versions earlier than BSC V900R013.
[0,100]
>HSDP A PDCP UL data amount >HSDP A PDCP DL data amount >Bytes of HSDP A MAC-d flow (suffici ent UE resourc es)
[0,+)
KB
Amount of uplink data at the packet data convergence layer of the HSDPA service.
[0,+)
KB
Amount of downlink data at the packet data convergence layer of the HSDPA service.
[0,+)
KB
Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are sufficient for the HSDPA service. That is, the amount of data of a UE sent on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
>Durati on for sending HSDP A MAC-d flow (suffici ent UE resourc es)
[0,+)
Duration for sending HSDPA MAC-d flow when the data resources of a UE are sufficient for the HSDPA service. That is, the duration for sending data of a UE on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
Issue 01 (2013-07-15)
1515
Param eter >Bytes of HSDP A MAC-d flow (insuffi cient UE resourc es) >Durati on for sending HSDP A MAC-d flow (insuffi cient UE resourc es) >Avera ge Downli nk Rate
Range [0,+)
Unit KB
Description Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are insufficient for the HSDPA service. That is, the amount of data of a UE sent on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
[0,+)
Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient for the HSDPA service. That is, the duration for sending data of a UE on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
[0,+)
Kbps
Average downlink rate of the HSDPA service = (Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are sufficient + Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are insufficient) /(Duration for sending HSDPA MAC-d flow when the data resources of a UE are sufficient + Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient).
Issue 01 (2013-07-15)
1516
Range [0,+)
Description If Average downlink rate of the HSDPA service is smaller than Slow average downlink rate threshold of the HSDPA service, Times of slow average downlink rate + 1. The slow average downlink rate threshold is set by engineers during task creation.
[0,+)
Kbps
Average uplink rate of the HSDPA service = (Number of uplink bytes in HSDPA PDCP /(Duration for sending HSDPA MAC-d flow when the data resources of a UE are sufficient + Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient).
[0,+)
Num ber
If Average uplink rate of the HSDPA service is smaller than Slow average uplink rate threshold of the HSDPA service, Times of slow average uplink rate +1 The slow average uplink rate threshold is set by engineers during task creation.
[0,+)
Kbps
Average downlink rate of the HSDPA service when the data resources are sufficient.
Issue 01 (2013-07-15)
1517
Param eter >DL Averag e Rate Slow (suffici ent resourc es)
Range [0,+)
Description If Average downlink rate of the HSDPA service < Slow average downlink rate threshold of the HSDPA service when the data resources are sufficient, Times of slow average downlink rate when the data resources are sufficient + 1. The slow average downlink rate threshold when the data resources are sufficient is set by engineers during task creation.
[0,+)
Kbps
Average downlink rate of the HSDPA service when the data resources are insufficient = Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are insufficient /Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient.
[0,+)
Num ber
If Average downlink rate of the HSDPA service < Slow average downlink rate threshold of the HSDPA service when the data resources are insufficient, Times of slow average downlink rate when the data resources are insufficient + 1. The slow average downlink rate threshold when the data resources are insufficient is set by engineers during task creation.
Issue 01 (2013-07-15)
1518
Range N/A
Unit N/A
Description Time when a signaling message is sent or received. Direction for sending or receiving a signaling message.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
to CN from CN to other RNC from other RNC to NODEB from NODEB to UE from UE to SAS from SAS
N/A
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.
Signali ng Content
N/A
N/A
Measurement Information
Param eter Number Range [0,+) Unit N/A Description Number that uniquely identifies a measurement report (MR). Time when an MR is reported. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
1519
Range Intra-freq measurement type Inter-freq measurement type Inter-RAT measurement type Event MR, such as E1A and so on
Unit N/A
Description MR type.
N/A
N/A
Name of a measurement object reported in an MR. The parameter value is displayed in the following format: RNC 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.
P-SC
[0,512]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[-24,0]
dB
Ratio of energy per modulating bit to the noise spectral density (Ec/ No). For details, see 3GPP 25.331. Received signal code power (RSCP). For details, see 3GPP 25.331. Received signal strength indicator (RSSI) of a GSM carrier. For details, see 3GPP TS 45.008.
[-115,-25]
dBm
N/A
dBm
[0,97]
dBm
Reference signal received power (RSRP). For details, see 3GPP 36.133.
Issue 01 (2013-07-15)
1520
Range [0,33]
Unit dB
Description Reference signal received quality (RSRQ). For details, see 3GPP 36.133. Transmit power of a UE.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
UE TX Power
N/A
N/A
Mobility Analysis
Param eter Number Range [0,+) Unit N/A Description Number of a handover during a call. Whether a handover is abnormal. If a red exclamation mark is displayed in this column, the handover is abnormal. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Abnorm al
! Blank
N/A
Issue 01 (2013-07-15)
1521
Range Softer handover Soft handover Intra-freq hard handover Inter-freq hard handover Inter-system incoming handover Inter-system outgoing handover/CS system handover Inter-system outgoing handover/Cell change order PS system handover Inter-system outgoing handover/ Enhanced PS system handover Inter-system outgoing handover/CS and PS system handover Inter-system outgoing handover/UE generated Incoming migration/ Static reloc in Incoming migration/HHO reloc in Incoming migration/Cell update reloc in
Unit N/A
Description Type of mobility analysis. Currently, the system supports the following mobility analysis types: Soft handover Hard handover Incoming inter-RAT handover Outgoing inter-RAT handover Incoming migration Outgoing migration Cell update Channel handover
Issue 01 (2013-07-15)
1522
Param eter
Unit
Description
Supported NE Version
N/A
N/A
Start time.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Overlon g Interval
Yes No
N/A
If Interval > Overlong xxx delay threshold, The value of this parameter is Yes. Otherwise, the value is 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 handover delay threshold Overlong incoming handover delay threshold Overlong outgoing handover delay threshold Overlong channel handover delay threshold
End Time
N/A
N/A
End time.
Issue 01 (2013-07-15)
1523
Range converage based load based but blind handover load based and measurement based forced handover emergency handover
Unit N/A
MutiRAB Info
1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
N/A
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Active Set
N/A
Measurement type.
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. Ratio of energy per modulating bit to the noise spectral density (Ec/ No). For details, see 3GPP 25.331. Received signal code power (RSCP). For details, see 3GPP 25.331.
[-24,0]
dB
[-115,-25]
dBm
Issue 01 (2013-07-15)
1524
Range DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
N/A
[0,+)
kbps
UL RB rate when occuring the channel handover. DL RB rate when occuring the channel handover. Destination cell information.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
bps
N/A
N/A
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 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. Ratio of energy per modulating bit to the noise spectral density (Ec/ No) of 3G target cell. For details, see 3GPP 25.331.
>Ec/NO (dB)
[-24,0]
dB
Issue 01 (2013-07-15)
1525
Param eter >RSCP (dBm) >Target Cell Operati on >Target Cell Operati on Time InterRAT carrier RSSI (dBm) RSRP
Range [-115,-25]
Unit dBm
Description Received signal code power (RSCP) of 3G target cell. For details, see 3GPP 25.331. Target cell operation of the 3G target cell when occuring the soft handover. Target cell operation time of the 3G target cell when occuring the soft handover. Received signal strength indicator (RSSI) of a GSM carrier of 2G target cell. For details, see 3GPP TS 45.008. Reference signal received power (RSRP) of LTE target cell. For details, see 3GPP 36.133. Reference signal received quality (RSRQ) of LTE target cell. For details, see 3GPP 36.133. Source UL channel type when occuring the channel handover.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RL ADD RL DEL
N/A
N/A
N/A
N/A
dBm
[-140,-43]
dBm
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RSRQ
[-19.5,-2.5]
dB
N/A
Issue 01 (2013-07-15)
1526
Range DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
[0,+)
bps
UL RB rate when occuring the channel handover. DL RB rate when occuring the channel handover. Failure cause.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
bps
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Error type.
>Error Reason
N/A
Error reason.
Issue 01 (2013-07-15)
1527
Service Analysis(RAB)
Param eter Numbe r Abnor mal Range [0,+) Unit N/A Description Record number of RAB service. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
! Blank
N/A
Whether a servive record is abnormal. If a red exclamation mark is displayed in this column, the record is abnormal.
! Blank
N/A
Whether a servive record of RAB setup is abnormal. If a red exclamation mark is displayed in this column, the record is abnormal.
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". CS_AMR CS_VP CS_OTHER PS_GENERAL PS_HSDPA PS_HSUPA PS_HSPA
N/A
N/A
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1528
Param eter Best Cell on RAB Setup Serving Cell on RAB Setup Peer Informa tion
Range N/A
Unit N/A
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Peer information. If the service is RAB on CS domain, it displays "Peer MSISDN". If the service is RAB on PS domain, it displays N/A.
1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS ...
N/A
! Blank
N/A
Whether a servive record of RAB release is abnormal. If a red exclamation mark is displayed in this column, the record that "Single-RAB Abnormal Release Indicator" or "MultipleRAB Abnormal Release Indicator" is YES.
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Issue 01 (2013-07-15)
1529
Unit N/A
Description Cause of the call is disconnected, that is the cause value of NAS Disconnect message. The value is valid only on RAB CS domain.
N/A
Cause of the PDP is deactive, that is the cause value of Deactivate PDP context request message. The value is valid only on RAB PS domain.
RAB Release Time Best Cell Before RAB Release Serving Cell Before RAB Release MultiRAB Informa tion on RAB Release
N/A
N/A
N/A
N/A
N/A
N/A
1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS ...
N/A
[0,+)
Seco nd
RAB setup delay = Time when RAB setup completes - Time when RAB setup is requested.
Issue 01 (2013-07-15)
1530
Range [0,+)
Description RAB duration = Time when RAB is released - Time when RAB setup completes Service duration.
[0,+)
BSC6900 If the service is RAB on CS domain, V900R013C00 it displays the service duration (that or later version is call time). If the service is RAB on PS domain, it displays N/A (that is not involved).
[0,+)
Byte
Total uplink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total throughput on uplink of RAB process.
[0,+)
Seco nd
Total uplink transmission duration. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total transmission duration on uplink of RAB process.
[0,+)
Kbps
Average uplink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays average throughput on uplink of RAB process. Average uplink throughput = Total uplink throughput/Total uplink transmission duration
Yes No
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. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
1531
Range [0,+)
Unit Byte
Description Total downlink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total throughput on downlink of RAB process.
[0,+)
Seco nd
Total downlink transmission duration. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total transmission duration on downlink of RAB process.
[0,+)
Kbps
Average downlink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays average throughput on downlink of RAB process. Average downlink throughput = Total downlink throughput/Total downlink transmission duration
Yes No
N/A
If "Average Downlink Throughput" is smaller than "Average Downlink Throughput Threshold", the record has the problem that the average downlink throughput is too small. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
1532
Summary
Para mete r Serial Num ber Range Uni t N/A Description Supported NE Version BSC6900 V900R013C00 or later version
(0,2^31-1)
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. 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.
Comb ined
N/A
N/A
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.
For details, see "Appendix: Exception Cause Classification / Key Signaling (GSM)".
N/A
Cause of the exception carried in an Access Request message. Note: The HQIs after the call setup is successful are only counted in the abnormal cause.
Netw ork
GSM-CS, GSM-PS
N/A
Issue 01 (2013-07-15)
1533
Range
Uni t N/A
Description
Non-SMS message from a mobile-originated VIP subscriber (AC_ORIGIN_CALL_N O_SMS) SMS message from a mobile-originated VIP 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) 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) Incoming inter-BSC handover (AC_IN_BSC_HO)
Issue 01 (2013-07-15)
1534
Para mete r
Range
Uni t
Description
Supported NE Version
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 ) Non-SMS message from a mobile-terminated VIP subscriber (AC_ANSWER_TO_PA GING_CALL) SMS message from a mobile-terminated VIP subscriber (AC_ANSWER_TO_PA GING_CALL) Normal location update (AC_LOCATION_UPD ATE_NORMAL) Periodic location update (AC_LOCATION_UPD ATE_PERIODIC) IMSI attachment (AC_LOCATION_UPD ATE_ATTACH) Acces s Time N/A N/A Signaling access time for a call, namely, the time when a MS sends the Channel Request message. BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1535
Range
Uni t N/A
Description
N/A
Name of the cell in which a MS sends the Channel Request message. 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. In the preceding format, BSC OPC is the originating signaling point configured on the BSC side.
Relea se Time
N/A
N/A
Signaling release time for a call, namely, the time when a MS receives the Channel Release message.
Relea se Cell
N/A
N/A
Name of the cell in which a MS receives the Channel Release message. 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.
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
Issue 01 (2013-07-15)
1536
Range
Uni t N/A
Description
00000000-99999999
International mobile equipment identity-type allocation code (IMSI-TAC) of a VIP subscriber, which is the first eight digits in the IMEI of a UE. Type of a MS. You can obtain the IMEITACs of the UE from the MS type management function.
Mode l
N/A
N/A
N/A
N/A
Mobile station international ISDN number (MSISDN) of a peer subscriber. Service duration covering the call duration and the signaling setup duration. Service duration = Release time - Access time
[0,+)
Sec ond
[0,+)
Sec ond
Call duration. Call duration = Time stamp of the Disconnect message Time stamp of the Connect Acknowledge message
Issue 01 (2013-07-15)
1537
Range
Uni t N/A
Description
Following are criteria indicating a proper call setup: 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. 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. 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.
Network access result for a mobile-originated call. The result indicates a proper call setup or an abnormal call setup. 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.)
Issue 01 (2013-07-15)
1538
Para mete r
Range
Uni t
Description
Supported NE Version
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 Following are criteria indicating a proper call release: 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 inter-RAT handover is triggered and completed. Following are criteria indicating an abnormal release of traffic channel during a call: 1. An outgoing inter-BSC handover fails. 2. An intra-BSC handover fails. 3. The BSC releases channel resources. 4. The MSC releases channel resources. N/A Network release result for a mobile-originated call. The result indicates a proper call release or an abnormal call release. BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1539
User Information
Parame ter User ID:Alias IMEITAC Model Range N/A Unit N/A Description Refer to "User ID:Alias" in the Summary area. Refer to "IMEI-TAC" in the Summary area. Refer to "Model" in the Summary area. Capability of the MS. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Yes No
N/A
Yes No
N/A
Yes No
N/A
Whether a MS supports the VAMOS. VAMOS, voice services over adaptive multi-user channels on one slot.
Yes No
N/A
Whether a MS supports the U900. That is, whether a MS supports accessing to the 3G network using the 900 MHz/ 850 MHz band of the 2G network.
Peer MSISD N
N/A
N/A
Issue 01 (2013-07-15)
1540
N/A
N/A
[0,71]
N/A
Access Channel
[0,7]
N/A
Access Type
N/A
N/A
MOC MTC
N/A
According to the access causes to identify the user's current business is accessed by MTC or MOC. According to the access causes to identify the user's current business is accessed by SMS or Voice. Network access result for a mobile-originated call. 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.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
SMS Voice
N/A
N/A
N/A
Issue 01 (2013-07-15)
1541
Range N/A
Unit N/A
Description 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.
N/A
N/A
Detailed cause of an abnormal signaling access for a call. See the level-3 cause, Sub-Cause of Abnormal Call Setup, in Call Setup Result/Cause of Abnormal Call Setup/Sub-Cause of Abnormal Call Setup in General Evaluation.
Access Delay Estimati on >ASSIG NMENT COMPL ETE Message Timesta mp >Access Delay
N/A
N/A
N/A
N/A
Time when the assignment is finished after initiating a call and accessing the network.
[0,+)
Secon d
Access delay time of the service. Access Delay = Time of ASSIGNMENT COMPLETE Time of CHANNEL REQUEST ="ASSIGNMENT COMPLETE Message Timestamp"-"Access Time"
Yes No
N/A
Whether the abnormal of overlong access delay is occurred. The abnormal threshold is set when creating tasks.
>Alertin g Time
N/A
N/A
Time when a VIP subscriber hears the alerting after initiating a call.
Issue 01 (2013-07-15)
1542
Parame ter >Call Complet ion Delay (Alertin g) >Overlo ng Call Complet ion Delay (Alertin g) >Connec t Acknow ledge Time >Call Complet ion Delay (Connec t Ack)
Range [0,+)
Unit Secon d
Description Call completion delay time of the service. Call Completion Delay(Alerting) = Time of ALERTING - Time of CHANNEL REQUEST =Alerting Time - Access Time
Yes No
N/A
Whether the abnormal of overlong call completion delay (Alerting) is occurred. The abnormal threshold is set when creating tasks.
N/A
N/A
Time when a VIP subscriber hears the voice of the peer subscriber after initiating a call.
[0,+)
Secon d
Call completion delay time of the service. Call Completion Delay(Connect Ack) = Time of CONNECK ACK - Time of CHANNEL REQUES REQUEST =Connect Acknowledge Time Access Time
>Overlo ng Call Complet ion Delay (Connec t Ack) Measure ment Informat ion On Access >TA
Yes No
N/A
Whether the abnormal of overlong call completion delay (Connect Ack) is occurred. The abnormal threshold is set when creating tasks.
N/A
N/A
[0,63]
N/A
Issue 01 (2013-07-15)
1543
Range Yes No
Unit N/A
Description Whether the abnormal that TA is too large when accessing to the network is occurred. The abnormal threshold is set when creating tasks.
[-110,-47]
dBm
Value of the RACH level when a MS accesses to the network. Whether the abnormal that RACH Level is too small is occurred. The abnormal threshold is set when creating tasks.
Yes No
N/A
[0,+)
Secon d N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1544
Range N/A
Unit N/A
Description Cause of an abnormal signaling release during a call. See the level-2 cause, Cause of Abnormal Call Release, in Call Release Result/Cause of Abnormal Call Release/SubCause of Abnormal Call Release in General Evaluation.
N/A
N/A
Detailed cause of an abnormal signaling release during a call. See the level-3 cause, Sub-Cause of Abnormal Call Release, in Call Release Result/Cause of Abnormal Call Release/SubCause of Abnormal Call Release in General Evaluation.
CS Service Information
Parame ter Service Process Delay Estimati on >IntraBSC Channel Release Timesta mp >Calling Duration Range N/A Unit N/A Description Delay estimation for service process. Supported NE Version BSC6900 V900R013C00 or later version
N/A
N/A
[0,+)
Secon d
Calling Duration = Time of DISCONNECT - Time of CONNECT ACK =Intra-BSC Channel Release Timestamp - CONNECT ACK Timestamp
>Short Call
Yes No
N/A
Whether the abnormal of short call is occurred. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
1545
Parame ter Service Quality Estimati on for Service Process >Uplink Oneway Audio During a Call
Range N/A
Unit N/A
Yes No
N/A
Whether uplink one-way audio occurs during a call. 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 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 threshold, the BSS determines that primary uplink one-way audio occurs, and starts the mechanism for confirming the occurrence of primary uplink one-way audio. During this process, the BSC sends a message to the BTS demanding that the BTS send a test TRAU frame to the TC. If the TC fails to receive the test TRAU frame from the BTS within a specified time period, one-way audio occurs on the uplink voice channel.
Issue 01 (2013-07-15)
1546
Range Yes No
Unit N/A
Description Whether downlink one-way audio occurs during a call. 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 Um and A interfaces. Principle for detecting downlink one-way audio: The DSP in the DTRU of the BTS performs periodic statistics on the bad frame rate based on downlink TRAU frames. When the bad frame rate reaches the predefined threshold, the BSS determines that primary downlink one-way audio occurs, and starts the mechanism for confirming the occurrence of primary downlink one-way audio. During this process, the BSC sends a message to the TC demanding that the TC send a test TRAU frame to the BTS. If the BTS fails to receive the test TRAU frame from the TC within a specified time period, oneway audio occurs on the downlink voice channel.
Yes No
N/A
Whether uplink crosstalk occurs during a call. 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 uplink crosstalk: The DSP of the BTS inserts the unique identifier of a call into the free bits of uplink voice TRAU frames. The DSP of the TC decodes the unique call identifiers and checks their consistency. If inconsistency in the unique call identifiers is detected within the test period, uplink crosstalk occurs.
Issue 01 (2013-07-15)
1547
Range Yes No
Unit N/A
Description Whether downlink crosstalk occurs during a call. 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 uplink voice TRAU frames. The DSP of the BTS decodes the unique call identifiers and checks their consistency. If inconsistency in the unique call identifiers is detected within the test period, downlink crosstalk occurs.
N/A
Whether uplink noise occurs during a call, which is detected by the device. Whether downlink noise occurs during a call, which is detected by the device. Average value for the uplink high quality indicators (HQIs) of call setups that include the HQIs before and after the call setup is successful. 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 reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
Issue 01 (2013-07-15)
1548
Range Yes No
Unit N/A
Description Whether the abnormal of bad uplink HQI is occurred of call setups that include the HQIs before and after the call setup is successful. The abnormal threshold is set when creating tasks.
[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. In CHRs of the BSC6900 V900R011 or any later version: HQI = Number of measurement reports indicating a voice quality of levels 0 to 3/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
Yes No
N/A
Whether the abnormal of bad downlink HQI is occurred of call setups that include the HQIs before and after the call setup is successful. The abnormal threshold is set when creating tasks.
[1.00,5.00]
N/A
Average value for the uplink voice quality indicators (VQIs) of successful call setups. 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/ Total number of uplink VQI tests
Issue 01 (2013-07-15)
1549
Range Yes No
Unit N/A
Description Whether the abnormal of bad uplink VQI is occurred. The abnormal threshold is set when creating tasks.
Measure ment Informat ion On Service Process >Averag e Uplink Level >Averag e Downlin k Level >Averag e Uplink Quality >Averag e Downlin k Quality
N/A
N/A
[-110,-47]
dBm
Average uplink level on service process. Average downlink level on service process.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[-110,-47]
dBm
[0,7]
N/A
Average uplink quality on service process. Average downlink quality on service process.
[0,7]
N/A
N/A
N/A
Uplink Downlink
N/A
Issue 01 (2013-07-15)
1550
Range N/A
Unit N/A
Description 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. Content of a signaling message. You can obtain the content of a signaling message by viewing the related tree structure.
Signalin g Content
N/A
N/A
N/A
N/A
N/A
N/A
Server Nbr1~6
N/A
Issue 01 (2013-07-15)
1551
Unit N/A
Description Base transceiver Station Identity Code (BSIC) of a neighboring cell, reported in a measurement report.BSIC has 6 bits, the first part is NCC, the last past is BCC. TA of a serving cell, reported in a measurement report. Downlink RxLevel of a serving cell and that of a neighboring cell, reported in a measurement report. Uplink RxLevel of a serving cell, reported in a measurement report. Downlink RxQuality of a serving cell, reported in a measurement report. Uplink RxQuality of a serving cell, reported in a measurement report. BTS power of a serving cell, reported in a measurement report. MS power of a serving cell, reported in a measurement report.
TA
[0,63]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RxLevel (Downli nk) RxLevel (Uplink) RxQualit y (Downli nk) RxQualit y (Uplink) BTS Power MS Power
[-110,-47]
dBm
[-110,-47]
dBm
[0,7]
N/A
[0,7]
N/A
[0,15]
N/A
[0,31]
N/A
Mobility Analysis
Parame ter Number Range [0,+) Unit Numb er N/A Description Number for a handover triggered during a call. Whether a record indicates an abnormal handover. The record indicates an abnormal handover if a red exclamation mark is displayed.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Abnorm al
N/A
1552
Range Communicat ion resumes on the original channel after a handover failure the BSC releases channel resources the MSC is faulty
Unit N/A
Description Whether a handover succeeds, and the cause of a handover failure. The cause is displayed as Normal if a handover succeeds. 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.
Type
Intra-BSC handover Outgoing cell handover Incoming inter-BSC handover Outgoing inter-BSC handover Outgoing inter-RAT handover
N/A
Type of a handover
Initiatin g Time
N/A
N/A
Time when a handover is initiated, namely, the time when the BSC sends the Handover CMD message.
Duration
[0,+)
N/A
Issue 01 (2013-07-15)
1553
Range Yes No
Unit N/A
Description The first case: "Handover Type" is "Outgoing inter-BSC handover" If the duration is more than "Outgoing BSC Handover Interval", it displays "Yes"; If not, it displays "No". The second case: "Handover Type" is "Outgoing inter-RAT handover" If the duration is more than "Outgoing System Handover Interval", it displays "Yes"; If not, it displays "No". The other case: displays null. "Outgoing BSC Handover Interval" and "Outgoing System Handover Interval" is set when creating tasks.
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Cause of a handover.
N/A
N/A
Name of the source cell to be handed over. The parameter is displayed in the following format: Name of the BSC: Name of the cell (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. In the preceding format, BSC OPC is the originating signaling point configured on the BSC side.
N/A
N/A
1554
Range N/A
Unit N/A
Description Name of the target cell to which a handover is to be performed. The parameter is displayed in the following format: Name of the BSC: Name of the cell (BSC OPC: ID of the cell). You can obtain the names of the BSC and the cell from the configuration data.
Summary
Param eter Serial Number Range (0,2^31-1) Unit N/A Description 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. 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. 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. Supported NE Version BSC6900 V900R013C01 or later version
Combin ed
N/A
N/A
Issue 01 (2013-07-15)
1555
Range For details, see "Appendix: Exception Cause Classification / Key Signaling (GSM)". GSM-CS, GSMPS
Unit N/A
Networ k
N/A
Issue 01 (2013-07-15)
1556
Range Non-SMS message from a mobile-originated VIP subscriber (AC_ORIGIN_C ALL_NO_SMS) SMS message from a mobileoriginated VIP subscriber (AC_ORIGIN_C ALL_SMS) Answer to paging (AC_ANSWER_ TO_PAGING) Call re-setup (AC_CALL_RE_ ESTABLISH) Emergency call (AC_EMERGEN CY_CALL) Location update (AC_LOCATION _UPDATE) IMSI detachment (AC_IMSI_DET ACH) Data service (AC_PACKET_C ALL) LMU service (AC_LMU_EST ABLISH) SS service (AC_SS_ESTAB LISH) VGCS service (AC_VGCS_EST ABLISH) VBS service (AC_VBCS_EST ABLISH) LCS service (AC_LCS_ESTA BLISH)
Unit N/A
Issue 01 (2013-07-15)
1557
Param eter
Range Any other service (AC_RESERVE D) Incoming interBSC handover (AC_IN_BSC_H O) Response to notification (AC_NOTIFICA TION_RSP) Immediate setup (AC_IMM_SET_ UP) RR initialization (AC_RR_INITIA LISATION_REQ ) Indication from talker (AC_TALKER_I NDICATION) VGCS access (AC_VGCS_VBS _VPCS) Non-SMS message from a mobileterminated VIP subscriber (AC_ANSWER_ TO_PAGING_C ALL) SMS message from a mobileterminated VIP subscriber (AC_ANSWER_ TO_PAGING_C ALL) Normal location update (AC_LOCATION _UPDATE_NOR MAL) Periodic location update
Unit
Description
Supported NE Version
Issue 01 (2013-07-15)
1558
Param eter
Unit
Description
Supported NE Version
Access Time
N/A
N/A
Signaling access time for a call, namely, the time when a MS sends the Channel Request message. Name of the cell in which a MS sends the Channel Request message. 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
Access Cell
N/A
N/A
Release Time
N/A
N/A
Signaling release time for a call, namely, the time when a MS receives the Channel Release message.
Release Cell
N/A
N/A
Name of the cell in which a MS receives the Channel Release message. 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 display
User ID:Alia s
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
Issue 01 (2013-07-15)
1559
Range 00000000-999999 99
Unit N/A
Description International mobile equipment identity-type allocation code (IMSI-TAC) of a VIP subscriber, which is the first eight digits in the IMEI of a UE. Type of a MS. You can obtain the IMEI-TACs of the UE from the MS type management function.
Model
N/A
N/A
N/A
N/A
Mobile station international ISDN number (MSISDN) of a peer subscriber. Service duration covering the call duration and the signaling setup duration. Service duration = Release time - Access time
[0,+)
Seco nd
Cause of Downli nk TBF Setup Failure Cause of Abnorm al Downli nk TBF Release Cause of Uplink TBF Setup Failure Cause of Abnorm al Uplink TBF Release
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1560
User Information
Param eter User ID:Alia s IMEITAC Model Range N/A Unit N/A Description Refer to "User ID:Alias" in the Summary area. Refer to "IMEI-TAC" in the Summary area. Refer to "Model" in the Summary area. Capability of the MS. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
MS Capabil ity >Suppo rt GPRS >Suppo rt GPRS MultiSlot Class >Suppo rt EGPRS >Suppo rt EGPRS MultiSlot Class >Suppo rt 900M E Frequen cy Band >Suppo rt 1800M Frequen cy Band
N/A
N/A
N/A
N/A
N/A
N/A
Support Unsupport
N/A
Support Unsupport
N/A
Issue 01 (2013-07-15)
1561
Param eter >Suppo rt G-TD DualMode >Suppo rt G-U DualMode >Suppo rt DTM >Suppo rt PS Handov er Insuffic ient Termin al Capabil ity
Unit N/A
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Support Unsupport
N/A
N/A
Whether a Terminal supports DTM. Whether a Terminal supports handovers in the PS domain.
N/A
Yes No
N/A
The capability of a Terminal is insufficient in the case of the following: The Terminal supports GPRS but not EGPRS. The Terminal supports EGPRS but the EGPRS multislot class is below 10.
Subscri ber Registra tion Paramet er >Reliab ility Level >Subscr iption Rate
N/A
N/A
Parameters related to the service that a VIP subscriber subscribes to when opening an account.
N/A
N/A
For details about the parameter, see see 3GPP TS 23.107. For details about the parameter, see see 3GPP TS 23.107.
N/A
N/A
Issue 01 (2013-07-15)
1562
Range Yes No
Unit N/A
Description An account-opening exception occurs in the case of the following: The reliability class of a VIP subscriber is not 3, namely, the reliability class is not the RLC acknowledged mode. The subscription rate is lower than the predefined exception threshold (which is set by engineers when creating tasks).
Peer Information
Param eter Number of Server Applica tions List of Servers and Applica tions >IP Address >Server Name Rang e N/A Unit N/A Description Total number of the server applications that a VIP subscriber accesses when attempting to use a data service. Supported NE Version BSC6900 V900R013C01 or later version
N/A
N/A
N/A
N/A
IP address of the server that a VIP subscriber accesses when attempting to use a data service. Name of the server that a VIP subscriber accesses when attempting to use a data 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 Port number of the server that a VIP subscriber accesses when attempting to use a data service.
N/A
N/A
>Port
[0,65 535)
N/A
Issue 01 (2013-07-15)
1563
Rang e N/A
Unit N/A
Description name of the application that a VIP subscriber accesses when attempting to use 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
[0,63 ]
N/A
[0,7]
N/A
GMSK MEAN BEP upon Access 8PSK MEAN BEP upon Access Access Cell
[0,31 ]
N/A
[0,31 ]
N/A
Information about the 8PSK MEAN BEP when a Terminal sends the Channel Request message.
N/A
N/A
Name of the cell in which a MS sends the Channel Request message. 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
Issue 01 (2013-07-15)
1564
Ran ge N/A
Uni t N/A
Description Time when a VIP subscriber releases a data service. Duration of the data service used by a VIP subscriber. 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. Number of access requests on the RACH (uplink CCCH) during the whole process for a subscriber to use a data service.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +) N/A
[0, +)
Nu mbe r
Issue 01 (2013-07-15)
1565
Param eter PDP Active Accept Times PDP Active Reject Times RA Update Request Times RA Update Accept Times RA Update Reject Times Suspen d Times
Ran ge [0, +)
Description Number of the PDP Active Accept messages that a VIP subscriber receives during the whole process of using a data service. Number of the PDP Active Reject messages that a VIP subscriber receives during the whole process of using a data service. Number of the RA Update Request messages that a VIP subscriber sends during the whole process of using a data service. Number of the RA Update Accept messages that a VIP subscriber receives during the whole process of using a data service. Number of the RA Update Reject messages that a VIP subscriber receives during the whole process of using a data service. Number of Suspends during the whole process for a VIP subscriber to use a data service.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +)
[0, +)
[0, +)
[0, +)
[0, +)
N/A
N/A
Issue 01 (2013-07-15)
1566
Rang e N/A
Unit N/A
Description Carrier of a TBF setup failure on the downlink. BCCH of a TBF setup failure on the downlink. Number of TBF setup failures on the uplink.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
Times of Uplink TBF Setup Failure >Cause s of Uplink TBF Setup Failure >Carrie r Index >BCCH
N/A
Num ber
N/A
N/A
N/A
N/A
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
Times of Abnor mal Downli nk TBF Release >Cause s of Abnor mal Downli nk TBF Release >Carrie r Index
[0, +)
Num ber
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1567
Rang e N/A
Unit N/A
Description BCCH of an abnormal TBF release on the downlink. Number of abnormal TBF releases on the uplink.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Times of Abnor mal Uplink TBF Release >Cause s of Abnor mal Uplink TBF Release >Carrie r Index >BCCH
[0, +)
Num ber
N/A
N/A
N/A
N/A
Carrier of an abnormal TBF release on the uplink. BCCH of an abnormal TBF release on the uplink.
N/A
N/A
[0, +) [0, +)
Byte
Size of the data transmitted by using the downlink PDU. Maximum duration for data transmission by using the downlink PDU.
Seco nd
Issue 01 (2013-07-15)
1568
Param eter >Total Duratio n on Sendin g PDU >Sent Count >Avera ge Duratio n on Sendin g PDU >Sendi ng Timeou t Times
Rang e [0, +)
Unit Seco nd
Description Overall duration for data transmission by using the downlink PDU.
[0, +) [0, +)
Total number of the blocks transmitted by using the downlink PDU. Average duration for data transmission by using the downlink PDU.
[0, +)
Num ber
Number of times that the duration for data transmission by using the downlink PDU exceeds the predefined threshold. A device is configured to directly check whether the duration for data transmission by using the PDU exceeds the predefined threshold.
Uplink PDU >Recei ved Bytes >Maxi mum Duratio n on Receivi ng PDU >Total Duratio n on Receivi ng PDU >Recei ved Count
N/A
N/A
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +) [0, +)
Byte
Size of the data transmitted by using the uplink PDU. Maximum duration for data transmission by using the uplink PDU.
Seco nd
[0, +)
Seco nd
[0, +)
Num ber
Issue 01 (2013-07-15)
1569
Param eter >Avera ge Duratio n on Receivi ng PDU >Recei ving Timeou t Times
Rang e [0, +)
Unit Seco nd
Description Average duration for data transmission by using the uplink PDU.
[0, +)
Num ber
Number of times that the duration for data transmission by using the uplink PDU exceeds the predefined threshold. A device is configured to directly check whether the duration for data transmission by using the PDU exceeds the predefined threshold.
Uplink/ Downli nk PDU >Maxi mum Interval Duratio n >Total Interval Duratio n >Numb er of Interval s >Avera ge Interval Duratio n >Numb er of Interval Timeou ts
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. Maximum interval for data transmission between the uplink and downlink PDUs.
[0, +)
Seco nd
[0, +)
Seco nd
Aggregated interval of all the intervals for data transmission between every two datatransmission time points on the uplink and downlink PDUs. Number of times that an interval for data transmission between the uplink and downlink PDUs is available. Average interval for data transmission between the uplink and downlink PDUs.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +)
Num ber
[0, +)
Seco nd
[0, +)
Num ber
Number of times that the interval for data transmission between the uplink and downlink PDUs exceeds the predefined threshold. A device is configured to directly check whether the interval for data transmission between the uplink and downlink PDUs exceeds the predefined threshold.
Issue 01 (2013-07-15)
1570
Param eter >Uplin k Data Availab le and Downli nk Data Unavail able Occurre nce Times Numbe r of No Service Interact ion Timeou t Times
Rang e [0, +)
Description Number of times that the uplink PDU carries data but downlink PDU does not. A device is configured to directly check whether the uplink PDU carries data while the downlink PDU does not.
[0, +)
Num ber
Number of times that no service interaction responses. 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.(A = Number of times that the uplink PDU carries data but the downlink PDU does not). The exception thresholds 1 and 2 for the response to service interaction are internal algorithm parameters.
[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. 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 Number of Interval Timeouts for data transmission between the uplink and downlink PDUs.
Issue 01 (2013-07-15)
1571
Rang e [0, +)
Description Average duration for the response to service interaction during the whole process for a VIP subscriber to use a data service. Average duration for the response to service interaction = Average duration for data transmission by using the downlink PDU + Average duration for data reception by using the uplink PDU + Average duration for data transmission between the uplink and downlink PDUs.
Yes No
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. If the average duration for the response to service interaction is above the upper threshold for the average duration for the response to service interaction, the average duration for the response to service interaction overlong. The threshold is set by engineers during analysis task creation.
[0, +)
Byte
Issue 01 (2013-07-15)
1572
Param eter >Durati on for Sendin g PDU at Downli nk >PDU Bytes Receive d at Uplink >Down load Speed (Kbps)
Ran ge [0, +)
Unit Secon d
Description Overall duration for data transmission by using the downlink PDU.
[0, +)
Byte
[0, +)
Kbps
Average download rate during the whole process for a subscriber to use a data service. Download rate = Number of bytes transmitted by using the downlink PDU/ Duration for data transmission by using the downlink PDU
Yes No
N/A
Number of low download rate exceptions during the whole process for a subscriber to use a data service. If a download rate is lower than the lower threshold for download rate, the download rate is low. The threshold is set by engineers when creating tasks.
[0, +)
Num ber
[0, +)
Num ber
Number of exceptions where downlink TCP disorder occurs during the whole process for a subscriber to use a data service.
Issue 01 (2013-07-15)
1573
Param eter >Avera ge Occupi ed Downli nk Slots >Down load MultiSlot Statisfa ction Ratio
Ran ge [1,6]
[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/ Multislot Class of the Terminal When Supporting GPRS.
>Trans mission Resour ces Require d for Code Request ed by Downli nk Block
[0, +)
Num ber
Issue 01 (2013-07-15)
1574
Param eter >Trans mission Resour ces Used by Code Assigne d to Downli nk Block >Resou rce Statisfa ction Ratio of Downli nk Averag e SingleSlot Throug hput (%) >GPRS Service Flag >>Num ber of Downli nk CS1~4 Blocks/ Valid Blocks >>Num ber of Total Blocks Sent at Downli nk
Ran ge [0, +)
Description Number of transmission resources actually used for the encoding of downlink blocks.
[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%
N/A
N/A
Information about the data service that a VIP subscriber uses through GPRS. 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.
[0, +)
Num ber
[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
Issue 01 (2013-07-15)
1575
Ran ge [0, +)
Description Total number of the valid blocks transmitted on the downlink = 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
[0, +)
Byte
Total number of the bytes contained in the valid blocks transmitted on the downlink = Number of the valid blocks transmitted on the downlink by using various channel coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the downlink by using CS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the downlink by using CS-4 x Number of the bytes contained in one valid block For details about the relation between a specific channel coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.2.
>>Dow nlink Retrans mission Ratio >>Dow nlink Reuse Ratio >EGDE Service Flag
[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 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 Information about the data service that a VIP subscriber uses through EGDE.
[0.00, +)
N/A
N/A
N/A
Issue 01 (2013-07-15)
1576
Param eter >>Num ber of Downli nk MCS1~ 9 Blocks/ Valid Blocks >>Num ber of Total Blocks Sent at Downli nk
Ran ge [0, +)
Description Total number of the blocks, and that of the valid blocks, transmitted on the downlink by using modulation and coding schemes MCS-1 through MCS-9.
[0, +)
Num ber
Total number of the blocks transmitted on the downlink = Total number of the blocks transmitted on the downlink by using various modulation and coding schemes = Number of the blocks transmitted on the downlink by using MCS-1 ++ Number of the blocks transmitted on the downlink by using MCS-9
[0, +)
Num ber
Total number of the valid blocks transmitted on the downlink = Total number of the valid blocks transmitted on the downlink by using various modulation and coding schemes = Number of the valid blocks transmitted on the downlink by using MCS-1 ++ Number of the valid blocks transmitted on the downlink by using MCS-9
[0, +)
Byte
Total number of the bytes contained in the valid blocks transmitted on the downlink = Number of the valid blocks transmitted on the downlink by using various modulation and coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the downlink by using MCS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the downlink by using MCS-9 x Number of the bytes contained in one valid block For details about the relation between a specific modulation and coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.3.
Issue 01 (2013-07-15)
1577
Param eter >>Dow nlink Retrans mission Ratio >>Dow nlink Averag e GMSK BEP >>Dow nlink Averag e 8PSK BEP >>Dow nlink Averag e BEP
Unit %
Description Downlink data-retransmission rate = Total number of the valid blocks transmitted on the downlink/Total number of the blocks transmitted on the downlink Average downlink GMSK BEP.
[0,31 ]
N/A
[0,31 ]
N/A
[0,31 ]
N/A
1. If both the average downlink GMSK BEP and the average downlink 8PSK BEP are valid, use the average downlink GMSK BEP with a higher order. 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.
N/A
Kbps
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.
Issue 01 (2013-07-15)
1578
Param eter >>Um Quality Satisfac tion Ratio of Downli nk Averag e SingleSlot Throug hput >>Poor Transm ission Quality Indicate d by Downli nk Averag e SingleSlot Throug hput >>Dow nlink Reuse Ratio Statistic s on UplinkRateSensitiv e Service s >PDU Bytes Receive d at Uplink
Unit %
Description Um-interface quality satisfaction rate at the average downlink single-slot throughput = MIN (Average downlink single-slot throughput/Target single-slot throughput x 100%, 100%) The target single-slot throughput is an internal algorithm parameter.
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, the transmission quality at the average downlink single-slot throughput is poor. The BEP required by the lowest-level coding and the upper threshold for downlink dataretransmission rate are internal algorithm parameters.
[0.00, +)
N/A
Downlink timeslot reuse = Overall duration for data transmission by using the downlink PDU x Average number of downlink timeslots/2/Total number of the blocks transmitted on the downlink Information about the statistics on uplink rate-sensitive services.
N/A
N/A
[0, +)
Byte
Issue 01 (2013-07-15)
1579
Param eter >Durati on for Receivi ng PDU at Uplink >PDU Bytes Sent at Downli nk >Uploa d Speed (Kbps)
Ran ge [0, +)
Unit Secon d
Description Overall duration for data transmission by using the uplink PDU.
[0, +)
Byte
[0, +)
Kbps
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 transmission by using the uplink PDU
Yes No
N/A
Number of low upload rate exceptions during the whole process for a subscriber to use a data service. If an upload rate is lower than the lower threshold for upload rate, the upload rate is low. The threshold is set by engineers when creating tasks.
>Numb er of Uplink NU Out-ofOrder Times >Numb er of Uplink TCP Out-ofOrder Times >Avera ge Occupi ed Uplink Slots
[0, +)
Num ber
[0, +)
Num ber
[1,6]
Num ber
Issue 01 (2013-07-15)
1580
Unit %
Description Uplink multislot-satisfaction rate = Average number of timeslots occupied by the uplink/ 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 Uplink Rate-Sensitive Service/EGDE Service Flag indicates a valid value, namely, the EDGE service is available, you can obtain the multislot class of a Terminal from Information About the VIP Subscriber/Capability of the Terminal/ Multislot Class of the Terminal When Supporting EGPRS. Otherwise, you can obtain the multislot class of a Terminal from Information About the VIP Subscriber/Capability of the Terminal/ Multislot Class of the Terminal When Supporting GPRS.
>Trans mission Resour ces Require d for Code Request ed by Uplink Block >Trans mission Resour ces Used by Code Assigne d to Uplink Block
[0, +)
Num ber
[0, +)
Num ber
Number of transmission resources actually used for the encoding of uplink blocks.
Issue 01 (2013-07-15)
1581
Param eter >Resou rce Statisfa ction Ratio of Uplink Averag e SingleSlot Throug hput (%) >Durati on for Sendin g PDU at Downli nk >Total Duratio n for Sendin g PDU at Downli nk >PDUs Sent at Downli nk >Timeo ut Times on sending PDUs at Downli nk >GPRS Service Flag
Unit %
Description Transmission-resource satisfaction rate at the average uplink single-slot throughput = Number of transmission resources actually used for the encoding of uplink blocks/ Number of transmission resources requested for the encoding of uplink blocks x 100%
[0, +)
Secon d
[0, +)
Secon d
[0, +)
Num ber
[0, +)
Num ber
Number of times that the duration for data transmission by using the downlink PDU exceeds the predefined threshold. A device is configured to directly check whether the duration for data transmission by using the PDU exceeds the predefined threshold.
N/A
N/A
Information about the data service that a VIP subscriber uses through GPRS.
Issue 01 (2013-07-15)
1582
Param eter >>Num ber of Uplink CSN (1~4) Blocks/ Valid Blocks >>Num ber of Total Blocks Receive d at Uplink
Ran ge [0, +)
Description Total number of the blocks, and that of the valid blocks, transmitted on the uplink by using channel coding schemes CS-1 through CS-4.
[0, +)
Num ber
Total number of the blocks transmitted on the uplink = Total number of the blocks transmitted on the uplink by using various channel coding schemes = Number of the blocks transmitted on the uplink by using CS-1 ++ Number of the blocks transmitted on the uplink by using CS-4
[0, +)
Num ber
Total number of the valid blocks transmitted on the uplink = Total number of the valid blocks transmitted on the uplink by using various channel coding schemes = Number of the valid blocks transmitted on the uplink by using CS-1 ++ Number of the valid blocks transmitted on the uplink by using CS-4
[0, +)
Byte
Total number of the bytes contained in the valid blocks transmitted on the uplink = Number of the valid blocks transmitted on the uplink by using various channel coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the uplink by using CS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the uplink by using CS-4 x Number of the bytes contained in one valid block For details about the relation between a specific channel coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.2.
Issue 01 (2013-07-15)
1583
Param eter >>Upli nk SingleSlot Throug hput (Actual ) >>Upli nk Reuse Ratio >EGDE Service Flag >>Num ber of Uplink MCS1~ 9 Blocks/ Valid Blocks >>Num ber of Total Blocks Receive d at Uplink
Unit Kbps
Description Uplink single-slot throughput (Actual) 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
[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 Information about the data service that a VIP subscriber uses through EGDE. Total number of the blocks, and that of the valid blocks, transmitted on the uplink by using modulation and coding schemes MCS-1 through MCS-9.
N/A
N/A
[0, +)
Num ber
[0, +)
Num ber
Total number of the blocks transmitted on the uplink = Total number of the blocks transmitted on the uplink by using various modulation and coding schemes = Number of the blocks transmitted on the uplink by using MCS-1 ++ Number of the blocks transmitted on the uplink by using MCS-9
[0, +)
Num ber
Total number of the valid blocks transmitted on the uplink = Total number of the valid blocks transmitted on the uplink by using various modulation and coding schemes = Number of the valid blocks transmitted on the uplink by using MCS-1 ++ Number of the valid blocks transmitted on the uplink by using MCS-9
Issue 01 (2013-07-15)
1584
Ran ge [0, +)
Description Total number of the bytes contained in the valid blocks transmitted on the uplink = Number of the valid blocks transmitted on the uplink by using various modulation and coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the uplink by using MCS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the uplink by using MCS-9 x Number of the bytes contained in one valid block For details about the relation between a specific modulation and coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.3.
>>Upli nk Receive Retrans mission Rate (%) >>Upli nk Averag e GMSK BEP >>Upli nk Averag e 8PSK BEP >>Upli nk Averag e BEP
[0.00, 100.0 0]
Uplink data-retransmission rate = Total number of the valid blocks transmitted on the uplink/Total number of the blocks transmitted on the uplink
[0,31 ]
N/A
[0,31 ]
N/A
[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, use the one with a valid value as the average uplink BEP.
Issue 01 (2013-07-15)
1585
Param eter >>Upli nk Averag e SingleSlot Throug hput Require d for Um Quality >>Um Quality Unsatis faction Times of Downli nk Averag e SingleSlot Throug hput
Unit Kbps
Description Average uplink single-slot throughput required to achieve a specific quality level on the Um interface. You can obtain the maximum single-slot rate, namely, the average uplink single-slot throughput, in BEP-Coding Scheme-Rate Mapping Table based on the average uplink BEP. The BEP-Coding Scheme-Rate Mapping Table is generated by an NE.
[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. 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) 3. If the average uplink single-slot throughput is smaller than the target single-slot throughput, and, at the same time, the value of B, which is obtained by using the following formula, is larger than the threshold for Um-interface quality satisfaction rate at the average uplink single-slot throughput, the quality on the Um interface does not meet the requirements. B = Average coding scheme_average uplink BEP/Average coding scheme_Number of the blocks actually received on the uplink.
Issue 01 (2013-07-15)
1586
Param eter >>Poor Transm ission Quality Indicate d by Uplink Averag e SingleSlot Throug hput >>Upli nk SingleSlot Throug hput (Actual ) >>Upli nk Reuse Ratio
Ran ge Yes No
Unit N/A
Description If the average uplink BEP is higher than the BEP required by the lowest-level coding, and, at the same time, the uplink dataretransmission rate is higher than the upper threshold for uplink data-retransmission rate, the transmission quality at the average downlink single-slot throughput is poor. The BEP required by the lowest-level coding and the upper threshold for uplink datareception-and-retransmission rate are internal algorithm parameters.
[0,10 0]
Uplink single-slot throughput (Actual) 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
[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
Summary Information
Param eter Total Traffic at Downli nk Ran ge [0, +) Unit Byte Description Total downlink traffic during the whole process for a subscriber to use a data service. 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 + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Downlink PDU Supported NE Version BSC6900 V900R013C01 or later version
Issue 01 (2013-07-15)
1587
Ran ge [0, +)
Unit Byte
Description Total uplink traffic during the whole process for a subscriber to use a data service. Total uplink traffic = Delay-Sensitive Information/Total Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Downlink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU
N/A
N/A
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. Content of a signaling message. You can obtain the content of a signaling message by viewing the related tree structure.
Signali ng Content
N/A
N/A
Issue 01 (2013-07-15)
1588
Measurement Information
Parame ter Number Rang e [0, +) N/A Unit N/A Description Unique number of a signaling message carrying a measurement report. Time when a measurement report is submitted. Type of a measurement report. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Time
N/A
MR Type
2G NC MR 3G MR EUTRA N MR
N/A
Server Nbr1~ 6
N/A
Type of a measurement object reported in a measurement report. 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.
N/A
N/A
name of a measurement object reported in a measurement report. The parameter is displayed in the following format: name of the BSC: name of the cell.
BCCH
N/A
BCCH of a neighboring cell on 2G network, reported in a measurement report. BSIC of a neighboring cell on 2G network, reported in a measurement report.
BSIC
N/A
dBm
Downlink RxLevel of a serving cell and that of a neighboring cell on 2G network, reported in a measurement report. Frequency on 3G network, reported in a measurement report. Primary scrambling code on 3G networkl, reported in a measurement report.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
Issue 01 (2013-07-15)
1589
Unit dBm
Description RSCP on 3G networkl, reported in a measurement report. Frequency on LTE network, reported in a measurement report. Primary scrambling code on LTE networkl, reported in a measurement report. RSCP on LTE networkl, reported in a measurement report.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Frequen cy PCI
N/A
N/A
RSRP
dBm
Mobility Analysis
Parame ter Number Range N/A Unit N/A Description Number. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
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. The threshold is set by engineers when creating tasks.
Abnorm al Cause
Overlo ng time of cell reselec tion (Durati on) Cell Resele ction N/A
N/A
If the time interval is above the exception threshold for cell reselection, it displays "Overlong time of cell reselection (Duration)".
Type
N/A
Type of a mobility analysis, namely, cell reselection. Time when a cell reselection ends.
End Time
N/A
Issue 01 (2013-07-15)
1590
Range N/A
Unit N/A
Description Source cell for a cell reselection. 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 based on the internal ID of the BSC and the ID of the cell. The names are not displayed if they are not available.
Reselect RxQuali ty Reselect GMSK MEAN BEP Reselect 8PSK MEAN BEP Target Cell
[0,7]
N/A
RxQulity of the source cell for a cell reselection. GMSK MEAN BEP of the source cell for a cell reselection.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0,31]
N/A
[0,31]
N/A
N/A
N/A
Target cell for a cell reselection. 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 based on the internal ID of the BSC and the ID of the cell. The names are not displayed if they are not available.
Access RxQuali ty Access GMSK MEAN BEP Access 8PSK MEAN BEP
[0,7]
N/A
RxQulity of the target cell for a cell reselection. GMSK MEAN BEP of the target cell for a cell reselection.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0,31]
N/A
[0,31]
N/A
Issue 01 (2013-07-15)
1591
Summary
Parame ter Serial Number Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Status
N/A
N/A
Whether a call record is abnormal. If a red exclamation mark is displayed in this column, the call record is abnormal.
Abnorm al 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. Network technology type.
Network
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access Type
Intra-RAT RRC Access Incoming HO/ Intra-RAT Incoming HO Incoming HO/ UTRAN Incoming HO Incoming HO/ GERAN Incoming HO
N/A
Access Time
N/A
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access Cell
N/A
N/A
Cell that a UE accesses at the beginning of a call. The parameter value is displayed in the following format: eNodeB name:cell name (eNodeB ID:cell ID).
Issue 01 (2013-07-15)
1592
Range
Unit
Description
Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Release Cell
N/A
N/A
Cell from which a UE is released at the end of a call. The parameter value is in the following format: eNodeB name:cell name (eNodeB ID:cell ID).
User ID:Alias
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
IMEITAC
00000000-99999 999
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.
Termina l Model
N/A
N/A
Model of a UE.
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Duratio n
[0,+)
Second
Duration of a call, which is displayed in the format of hh:mm:ss.nnn. Call duration = Release time Access time.
User Information
Parameter Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version
User ID:Alias
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
Issue 01 (2013-07-15)
1593
Parameter
Range
Unit
Description
STMSI
MMEC Range:BIT STRING (SIZE (8)) m-TMSI Range: BIT STRING (SIZE (32))
bit
S-temporary mobile subscriber identity (S-TMSI) of a subscriber. The parameter display is in the following format: MMEC:mTMSI. For more information please see 3GPP 36.331 6.3.6 S-TIMSI
[0,2^32-1]
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
[0,2^32-1]
N/A
IMEI-TAC
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.
Terminal Model
N/A
N/A
Model of a UE.
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
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. RATs supported by a UE.
>Support RAT
N/A
N/A
Issue 01 (2013-07-15)
1594
Parameter
Range
Unit
Description
N/A
>Device Type
N/A
Whether a UE supports battery consumption optimization. If the parameter is zero, it indicates that the device can foresee to particularly benefit from NWbased 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.
>Category Class
N/A
>>Uplink Physical Layer Parameter >>>Maxim um Number of UL-SCH Transport Block Bits Transmitte d Within A TTI
N/A
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
1595
Parameter
Range
Unit
Description
>>>Maxim um Number of Bits of an UL-SCH Transport Block Transmitte d Within A TTI >>>Suppor t for 64QAM In UL >>Downlin k Physical Layer Parameter >>>Maxim um Number of DL-SCH Transport Block Bits Received Within A TTI >>>Maxim um Number of Bits of a DL-SCH Transport Block Received Within A TTI >>>Suppor t for 64QAM In DL
N/A
N/A
Yes No
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
Yes No
N/A
Issue 01 (2013-07-15)
1596
Access Information
Parameter Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access Time
N/A
N/A
Access Cell
N/A
N/A
Cell that a UE accesses at the beginning of a call. The parameter value is in the following format: eNodeB name: cell name ( eNodeB ID:cell ID).
Access TA
[0,1314]
16*Ts=0.5 2 ms
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access UL RSRP
[-140,-43]
dBm
Reference signal received power (RSRP) on the uplink during the access of a call. SINR on the uplink during the access of a call.
Access UL SINR
[-15,35]
dB
Access Type
RRC Access Incoming HO/ Intra-eNodeB Incoming HO Incoming HO/ UTRAN Incoming HO Incoming HO/ GERAN Incoming HO
N/A
Issue 01 (2013-07-15)
1597
Parameter
Range
Unit
Description
Access Cause
N/A
N/A
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
The delay time between the time of access request and the time of access completion.
Release Information
Parameter Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Release Time
N/A
N/A
Release Cell
N/A
N/A
Cell from which a UE is released at the end of a call. The parameter value is in the following format: eNodeB name : cell name (eNodeB ID:cell ID).
N/A
Issue 01 (2013-07-15)
1598
Parameter
Range
Unit
Description
Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Handover based on the distance Handover based on the coverage Handover based on the load balancing
N/A
No.
[0,+)
N/A
Number that uniquely identifies a LTE 3900 sent and received signaling message. V100R005 C00 or later version Time when a signaling message is sent or received. LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Signaling Time
N/A
N/A
Signaling Direct
Uplink Downlin k
N/A
Signaling Type
N/A
N/A
Type of a signaling message that complies with any protocol and is transmitted over the S1-MME or Uu interface. For example, RRC CONNECT REQUEST is a signaling type.
Signaling Context
N/A
N/A
Issue 01 (2013-07-15)
1599
MR Time
N/A
N/A
N/A
MR Object Type
N/A
Eutran Cell ID
[0,255]
N/A
LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version
PCI
[0,503]
N/A
RSRP
[-140,-43]
dBm
RSRQ
[-19.5,-2.5]
dB
RSCP
[-115,-25]
dBm
RSCP of a neighboring cell when the measurement type is inter-RAT and the RAT is UTRAN in an MR.
Issue 01 (2013-07-15)
1600
Parameter EcNo
Range [-24,0]
Unit dB
Description Ec/No of a neighboring cell when the measurement type is inter-RAT and the RAT is UTRAN in an MR. Network color code (NCC) of a neighboring cell when the measurement type is interRAT and the RAT is GERAN in an MR. Base station color code (BCC) of a neighboring cell when the measurement type is inter-RAT and the RAT is GERAN in an MR. ARFCN of a neighboring cell when the measurement type is inter-RAT and the RAT is GERAN in an MR. Frequency band indicator of a neighboring cell when the measurement type is interRAT and the RAT is GERAN in an MR. RSSI of a neighboring cell when the measurement type is inter-RAT and the RAT is GERAN in an MR. Pilot signal phase of a neighboring cell when the measurement type is interRAT and the RAT is CDMA2000 in an MR. Pilot signal strength of a neighboring cell when the measurement type is interRAT and the RAT is CDMA2000 in an MR.
Supported NE Version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version
[0,7]
N/A
[0,7]
N/A
ARFCN
[0,1023]
N/A
DCS1800 PCS1900
N/A
RSSI
[-110,-48]
dBm
[0,32767]
chip
[-29,33]
dBm
Issue 01 (2013-07-15)
1601
Abnormal
! Blank
N/A
Issue 01 (2013-07-15)
1602
Range The handover interface types of intraRAT handover are the following: intra-eNodeB handover handover based on the X2 interface; handover based on the S1 interface. The handover interface types of interRAT handover are the following: handover based on the S1 interface.
Unit N/A
N/A
Preparation time for initiating an incoming or outgoing intra-RAT or inter-RAT handover during a call. Interval = Start time - End time.
Interval
[0,+)
Issue 01 (2013-07-15)
1603
Range Yes No
Unit N/A
Description If the interval exceeds the overlong xxx delay threshold, the value of this parameter is Yes. Otherwise, the value of this parameter is No. The overlong xxx delay threshold is set by engineers during task creation. The threshold types are as follows: Overlong intra-RAT outgoing handover delay threshold; Overlong inter-RAT outgoing handover delay threshold; Overlong intra-RAT incoming handover delay threshold.
End Time
N/A
N/A
End time.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
Source Cell
N/A
N/A
Source cell from which a call is handed over. The parameter value is in the following format: eNodeB name : cell name (eNodeB ID:cell ID).
UL RSRP upon Handover UL SINR upon Handover Target Cell for Handover
[-140,-43]
dBm
RSRP of the serving cell on the uplink during the handover of a call.
[-15,35]
dB
SINR of the serving cell on LTE 3900 the uplink during the V100R005C00 handover of a call. or later version Target cell to which a call is handed over. The parameter value is in the following format: eNodeB name: cell name (eNodeB ID:cell ID). LTE 3900 V100R005C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
1604
Parameter Target Cell UL RSRP After Handover Target Cell UL SINR After Handover Handover Triggering Cause
Range [-140,-43]
Unit dBm
Description RSRP of the serving cell on the uplink during the handover of a call.
[-15,35]
dB
SINR of the serving cell on LTE 3900 the uplink during the V100R005C00 handover of a call. or later version Triggering cause of an outgoing handover during a call. The triggering cause of an incoming handover is empty. LTE 3900 V100R005C00 or later version
Handover based on the distance Handover based on the coverage Handover based on the load balancing
N/A
Radio Network Layer Transport Layer NAS Layer Protocol Layer Miscellaneou s
N/A
Triggering cause of the preparation of an outgoing handover during a call. The preparation triggering cause of an incoming handover is empty.
Issue 01 (2013-07-15)
1605
Range Handover preparation to target cell failure 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
Unit N/A
Description Cause of a failed outgoing handover during a call. The cause of a failed incoming handover is empty.
Cancel Handover
Yes No
N/A
Whether the HANDOVER CANCEL message is received during the handover of a call. Handover result of a call, including the handover preparation result and handover execution result.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
Handover Result
N/A
Handover TA
[0,1314]
16*Ts =0.52 ms
Issue 01 (2013-07-15)
1606
Range [-140,-43]
Unit dBm
Description Reference signal received power (RSRP) on the UL during the handover of a call. SINR on the UL during the handover of a call. ID of the E-RAB and QCI that is handed over. ID of the E-RAB that is handed over. Service type for which ERAB is handed over. The parameter values are as follows: 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. Non GBR (QCIN): nonGBR service with low QoS. N = 5, 6, 7, 8, or 9.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[-15,35]
dB
N/A
N/A
[0,15]
N/A
E-RAB QCI
GBR(QCI1) GBR(QCI2) GBR(QCI3) GBR(QCI4) Non GBR (QCI5) Non GBR (QCI6) Non GBR (QCI7) Non GBR (QCI8) Non GBR (QCI9)
N/A
E-RAB Analysis
Parameter No. Range [1,+) Unit N/A Description Serial number of an ERAB ID. It uniquely identifies an E-RAB ID. Setup result of an E-RAB setup request. Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
! Blank
N/A
Issue 01 (2013-07-15)
1607
Range Radio Network Layer Transport Layer NAS Layer Protocol Layer Miscellaneous
Unit N/A
Description Cause of failed E-RAB setup. The parameter value also includes detailed causes.
GBR(QCI1) GBR(QCI2) GBR(QCI3) GBR(QCI4) Non GBR (QCI5) Non GBR (QCI6) Non GBR (QCI7) Non GBR (QCI8) Non GBR (QCI9)
N/A
QCI level on E-RAB setup. The parameter values are as follows: GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
E-RAB Request Time Cell on E-RAB Request E-RAB Setup Time TA on E-RAB Setup
N/A
N/A
Time when E-RAB is requested. Cell when E-RAB is requested. Time of RAB setup.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
1608
N/A
N/A
N/A
N/A
[0,1314]
[-140,-43]
Reference signal received power (RSRP) on the uplink during the E-RAB setup of a call. SINR on the uplink during the E-RAB setup of a call.
[-15,35]
dB
Issue 01 (2013-07-15)
Range ! Blank E-RAB abnormal release triggered by MME E-RAB abnormal release triggered by eNodeB E-RAB abnormal release triggered by outgoing HO execution failure
Unit N/A
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
Yes No
N/A
Identifier indicating whether data is being transmitted when an ERAB is released. If no data is being transmitted when the ERAB is released, the subscriber cannot perceive the exception.
N/A
QCI level on E-RAB release. GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
N/A
N/A
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
1609
Range [0,1314]
Description Time advance (TA) during the E-RAB release of a call. Reference signal received power (RSRP) on the uplink during the E-RAB release of a call. SINR on the uplink during the E-RAB release of a call. End where an E-RAB is released. End where an E-RAB is released.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[-140,-43]
[-15,35]
dB
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1610
Range GBR(QCI1) GBR(QCI2) GBR(QCI3) GBR(QCI4) Non GBR (QCI5) Non GBR (QCI6) Non GBR (QCI7) Non GBR (QCI8) Non GBR (QCI9)
Unit N/A
Description QCI level on E-RAB setup. The parameter values are as follows: GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
>E-RAB Request Time >Cell on ERAB Request >E-RAB Setup Time >E-RAB Setup Result >E-RAB Setup Cause
N/A
N/A
Time when E-RAB is requested. Cell when E-RAB is requested. Time of RAB setup.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
N/A
N/A
N/A
Succeed Failure Radio Network Layer Transport Layer NAS Layer Protocol Layer Miscellaneou s
N/A
Setup result of an E-RAB setup request. Cause of E-RAB setup. The parameter value also includes detailed causes.
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1611
Range [0,+)
Unit Seco nd
Description E-RAB setup delay = Time when E-RAB setup completes - Time when ERAB setup is requested. MR information during the ERAB setup of a call. Time advance (TA) during the E-RAB setup of a call. Reference signal received power (RSRP) on the uplink during the E-RAB setup of a call. SINR on the uplink during the E-RAB setup of a call. Priority information of an ERAB. Priority of a setup E-RAB.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
N/A
[0,1314]
>>UL RSRP
[-140,-43]
>>UL SINR
[-15,35]
dB
N/A
N/A
N/A
N/A
>>E-RAB Passive Preemptability >E-RAB Rate Information >>Maximum ERAB DL Rate >>Assured ERAB DL Rate
N/A
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
1612
N/A
Rate information of an ERAB. Maximum downlink rate of a setup E-RAB. Assured downlink rate of a setup E-RAB.
kbps
kbps
Issue 01 (2013-07-15)
Parameter >>Maximum ERAB UL Rate >>Assured ERAB UL Rate E-RAB Release Information >E-RAB Request Service Type(QCI) on E-RAB Release
Unit kbps
Description Maximum uplink rate of a setup E-RAB. Assured uplink rate of a setup E-RAB. The information during the ERAB release of a call. QCI level on E-RAB release. GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
kbps
N/A
N/A
N/A
N/A
Time when an E-RAB is released. E-RAB duration = Time when E-RAB is released Time when E-RAB setup completes Cell from which an E-RAB is released.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,+)
Seco nd
N/A
N/A
Issue 01 (2013-07-15)
1613
Range E-RAB abnormal release triggered by MME E-RAB abnormal release triggered by eNodeB E-RAB abnormal release triggered by outgoing HO execution failure
Unit N/A
N/A
End where an E-RAB is released. Identifier indicating whether data is being transmitted when an E-RAB is released. If no data is being transmitted when the E-RAB is released, the subscriber cannot perceive the exception.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C01 or later version
N/A
N/A
N/A
MR information during the ERAB release of a call. Time advance (TA) during the E-RAB release of a call. Reference signal received power (RSRP) on the uplink during the E-RAB release of a call. SINR on the uplink during the E-RAB release of a call.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,1314]
>>UL RSRP
[-140,-43]
>>UL SINR
[-15,35]
dB
Issue 01 (2013-07-15)
1614
N/A
N/A
N/A
ms
N/A
CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-25 5 0-25 5
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR.
N/A
Issue 01 (2013-07-15)
1615
User Information
Param eter User ID:Alia s Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Termin al Model IMEITAC N/A N/A Model of the terminal that initiates a service. IMEI-TAC of the terminal that initiates a service. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
Procedure Information
Param eter Access Type Ran ge N/A Unit N/A Description Radio access network (RAN) type for the signaling procedure. This parameter can be any of the following: GPRS UMTS LTE CHR Type N/A N/A Type of the signaling procedure. This parameter can be any of the following: SM MM Procedu re Type N/A N/A Name of a signaling procedure. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1616
Ran ge N/A
Unit N/A
Description Procedure initiating party (UE or MME) and cause. For details, see the Description of Procedure Initiating Causes in the appendix.
N/A
P-TMSI received from a terminal when a procedure is initiated. P-TMSI that the network allocates to a terminal. If a procedure does not involve two routing areas, the field indicates the routing area where the procedure is initiated. If a procedure involves in two routing areas, the field indicates the new routing area.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
Cell
N/A
N/A
Old RAC
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. Indicates whether a procedure requires authentication. Indicates whether a procedure requires IMEI check. Indicates whether a procedure requires P-TMSI reallocation.
Authent ication Flag IMEI Check Flag PTMSI Realloc ation Flag Externa l Cause Old SGSN Address
N/A
N/A
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
If a procedure involves two SGSNs, the field indicates the IP address of the old SGSN.
Issue 01 (2013-07-15)
1617
Ran ge N/A
Unit N/A
Description APN selection mode. This parameter can be any of the following: MS & Network Verified MS not Verified Network not Verified
N/A
SN of a CHR that is sent to the billing center. Charging attribute of a UE. This parameter can be any of the following: Unspecified Hot billing Charging Flat rate Charging Prepaid Charging Normal Charging
N/A
N/A
N/A
Allocation/retention priority. This parameter can be any of the following: High priority Normal priority Low priority
N/A
N/A
Subscribed reliability class. This parameter can be any of the following: Subscribed reliability class 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
Issue 01 (2013-07-15)
1618
Ran ge N/A
Unit N/A
Description Subscribed delay class. This parameter can be any of the following: Subscribed delay class Delay class 1 Delay Class 2 Delay Class 3 Delay Class 4 (best effort)
N/A
N/A
Subscribed precedence. This parameter can be any of the following: Subscribed precedence High priority Normal priority Low priority Reserved
N/A
N/A
Subscribed peak throughput. This parameter can be any of the following: Subscribed peak throughput Up to 1 000 octet/s Up to 2 000 octet/s Up to 4 000 octet/s Up to 8 000 octet/s Up to 16 000 octet/s Up to 32 000 octet/s Up to 64 000 octet/s Up to 128 000 octet/s Up to 256 000 octet/s
Issue 01 (2013-07-15)
1619
Ran ge N/A
Unit N/A
Description Subscribed mean throughput. This parameter can be any of the following: Subscribed mean throughput 100 octet/h 200 octet/h 500 octet/h 1000 octet/h 2000 octet/h 5000 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
N/A
N/A
Subscribed delivery of erroneous SDUs. This parameter can be any of the following: No detect('-') Erroneous SDUs are delivered('yes') Erroneous SDUs are not delivered ('no')
Deliver y Order
N/A
N/A
Subscribed delivery order. This parameter can be any of the following: With delivery order ('yes') Without delivery order ('no')
Issue 01 (2013-07-15)
1620
Ran ge N/A
Unit N/A
Description Subscribed traffic class. This parameter can be any of the following: Conversational class Streaming class Interactive class Background class
Maxim um SDU Size Maxim um Bit Rate for Uplink Maxim um Bit Rate for Downli nk SDU Error Ratio
0-25 5
byte
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-86 40
bps
0-25 6000
bps
N/A
N/A
Subscribed SDU error ratio. This parameter can be any of the following: 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
Issue 01 (2013-07-15)
1621
Ran ge N/A
Unit N/A
Description Subscribed residual BER. This parameter can be any of the following: 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
N/A
N/A
Subscribed traffic handling priority. This parameter can be any of the following: Priority level 1 Priority level 2 Priority level 3
Transfe r Delay Guarant eed Bit Rate for Uplink Guarant eed Bit Rate for Downli nk GTP Tunnel Version
0-25 5 0-86 40
ms
Transfer delay.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
bps
0-25 6000
bps
N/A
N/A
GTP tunnel version. This parameter can be any of the following: GTPv0 GTPv1
Issue 01 (2013-07-15)
1622
Ran ge N/A
Unit N/A
Description Type of the PDP requested by a UE. This parameter can be any of the following: IPv4 IPv6 BOTH(IPV4&IPV6) PPP Empty
PDP Address in Use GGSN Address for Signali ng GGSN Address for User Traffic APN
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Access Time
N/A
Issue 01 (2013-07-15)
1623
Rang e N/A
Unit N/A
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-655 35 N/A
ms
N/A
CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
NE Name
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-255
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR.
0-255
N/A
User Information
Parameter User ID:Alias Rang e N/A Uni t N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Terminal Model IMEI-TAC N/A N/A Model of the terminal that initiates a service. IMEI-TAC of the terminal that initiates a service. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
Issue 01 (2013-07-15)
1624
Procedure Information
Parameter Access Type Rang e N/A Uni t N/A Description Radio access network (RAN) type for the signaling procedure. This parameter can be any of the following: GPRS UMTS LTE CHR Type N/A N/A Type of the signaling procedure. This parameter can be any of the following: SM MM Procedure Type N/A N/A Name of a signaling procedure. For details, see the Description of Signaling Procedures in the appendix. N/A N/A Procedure initiating party (UE or MME) and cause. For details, see the Description of Procedure Initiating Causes in the appendix. MS P-TMSI 0-2^3 2-1 0-2^3 2-1 N/A N/A P-TMSI received from a terminal when a procedure is initiated. P-TMSI that the network allocates to a terminal. If a procedure does not involve two routing areas, the field indicates the routing area where the procedure is initiated. If a procedure involves two routing areas, the field indicates the new routing area. Cell N/A N/A Cell where a procedure is initiated. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
Issue 01 (2013-07-15)
1625
Rang e N/A
Uni t N/A
Description 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. Indicates whether an MM procedure requires authentication. Indicates whether an MM procedure requires IMEI check. Indicates whether an MM procedure requires P-TMSI reallocation. Procedure result and failure cause. For details, see the Description of Exception Cause Fields in the appendix.
Authenticati on Flag IMEI Check Flag PTMSI Reallocation Flag External Cause
N/A
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
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.
Begin Time
N/A
Issue 01 (2013-07-15)
1626
Rang e N/A
Unit N/A
Description End time of the signaling procedure. Delay time of a signaling procedure. CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-655 35 N/A
ms
N/A
NE Name Board Subrack No. Board Slot No. Board Proc No.
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-255
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR. Number of the process that generates a CHR.
0-255
N/A
0-655 35
N/A
User Information
Parame ter User ID:Alias Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Termina l Model N/A N/A Model of the terminal that initiates a service. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1627
Unit N/A
Procedure Information
Parame ter CHR Type Ran ge N/A Unit N/A Description Type of the signaling procedure. This parameter can be any of the following: SM MM Procedur e Type Procedur e Init Cause N/A N/A Name of a signaling procedure. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
N/A
Procedure initiating party (UE or MME) and cause. For details, see the Description of Procedure Initiating Causes in the appendix.
N/A
N/A
PLMN of the eNodeB where a UE is located when a signaling procedure is initiated. ID of the eNodeB where a UE is located when a signaling procedure is initiated. UES1AP connection identification allocated by an MME in a traffic procedure. Time when the UES1AP connection identification is allocated by an MME in a traffic procedure. Tracking area where a terminal is located when a signaling procedure is initiated.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1628
Ran ge N/A
Unit N/A
Description Requested PDN type in a traffic procedure. This parameter can be any of the following: IPV4 IPV6 both(IPV4 & IPV6) unused
APN
N/A
N/A
Requested APN in a traffic procedure. Negotiated cause in a procedure result. Procedure result and failure cause.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Protocol Cause External Cause Serving Gateway Address PDN Gateway Address PDN Gateway Host Name UE Uplink Max Bandwid th UE Downlin k Max Bandwid th APN Uplink Max Bandwid th
N/A
N/A
N/A
N/A
N/A
N/A
IP address of the Serving Gateway in a signaling procedure. IP address of the PDN Gateway in a signaling procedure. Domain name of the PDN Gateway in a signaling procedure.
N/A
N/A
N/A
N/A
02^32 -1
bit/s
02^32 -1
bit/s
02^32 -1
bit/s
Issue 01 (2013-07-15)
1629
Ran ge 02^32 -1
Unit bit/s
N/A
QCI information allocated by a session. ARP information allocated by a session. Maximum bearer-level uplink bandwidth allocated by a session. Maximum bearer-level downlink bandwidth allocated by a session. Guaranteed bearer-level uplink bandwidth allocated by a session. Guaranteed bearer-level downlink bandwidth allocated by a session.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
ARP
N/A
bit/s
bit/s
bit/s
bit/s
Begin Time
N/A
Issue 01 (2013-07-15)
1630
Ran ge N/A
Unit N/A
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
ms
N/A
CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
NE Name Board Subrack No. Board Slot No. Board Proc No.
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR. Number of the process that generates a CHR.
N/A
N/A
User Information
Parame ter User ID:Alias Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Terminal Model N/A N/A Model of the terminal that initiates a service. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1631
Unit N/A
Procedure Information
Parame ter CHR type Ran ge N/A Unit N/A Description Type of the signaling procedure. This parameter can be any of the following: SM MM Procedu re Type Procedu re Init Cause N/A N/A Name of a signaling procedure. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
N/A
Procedure initiating party (UE or MME) and cause. For deTACls, see the Description of Procedure Initiating Causes in the appendix.
N/A
N/A
PLMN of the eNodeB where a UE is located when a signaling procedure is initiated. ID of the eNodeB that serves a UE when a signaling procedure is initiated. UES1AP connection identification allocated by an MME in a traffic procedure. Time when the UES1AP connection identification is allocated by an MME in a traffic procedure. Tracking area where a terminal is located when a signaling procedure is initiated.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1632
Parame ter New GUTI PLMN New GUTI MMEGI New GUTI MMEC New GUTI MTMSI Old GUTI PLMN Old GUTI MMEGI Old GUTI MMEC Old GUTI MTMSI Old TAC Target ID PLMN Target ID Target MME UE S1AP ID Target MME S1AP ID Time
Ran ge N/A
Unit N/A
Description PLMN of GUTI allocated by the network in a traffic procedure. MME Group Id of GUTI allocated by the network in a traffic procedure. MME CODE of GUTI allocated by the network in a traffic procedure. M-TMSI of GUTI allocated by the network in a traffic procedure. PLMN of GUTI received from a UE in a traffic procedure. MME Group Id of GUTI received from a UE in a traffic procedure. MME CODE of GUTI received from a UE in a traffic procedure. M-TMSI of GUTI received from a UE in a traffic procedure. ID of the old tracking area in a signaling procedure that involves more than one tracking area. PLMN of the target eNodeB in a signaling procedure that involves more than one eNodeB. ID of the target eNodeB in a signaling procedure that involves more than one eNodeB. Target UES1AP connection identification allocated by an MME in a traffic procedure. Time when the target UES1AP connection identification is allocated by an MME in a traffic procedure.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-655 35 0-255
N/A
N/A
N/A
N/A
0-655 35 0-255
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1633
Parame ter Target TAC Protocol Cause External Cause Access Type
Ran ge N/A
Unit N/A
Description ID of the target tracking area in a signaling procedure that involves more than one tracking area. Protocol cause value in a procedure result. Procedure result and failure cause.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
Radio access network (RAN) type for the signaling procedure. This parameter can be any of the following: GPRS UMTS LTE
Serving Gateway Address Serving Gateway Host Name MS PTMSI Allocate d PTMSI GU RAC
N/A
N/A
IP address of the Serving Gateway in a signaling procedure. Domain name of the Serving Gateway in a signaling procedure.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
P-TMSI received from a terminal when a procedure is initiated. P-TMSI that the network allocates to a terminal. 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. 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 CGI of the target cell. Otherwise, the field is empty.
N/A
N/A
GU CI
N/A
N/A
Issue 01 (2013-07-15)
1634
Ran ge N/A
Unit N/A
Description If a UE is handed over from a 2G/3G network to a LTE network or the location of the UE is updated, the field is the RAC of the old routing area. Otherwise, the field is empty. Indicates whether an MM procedure requires authentication. Indicates whether an MM procedure requires IMEI check. Indicates whether an MM procedure requires P-TMSI reallocation. If a procedure involves two SGSNs, the field indicates the IP address of the old SGSN.
Authenti cation Flag IMEI Check Flag PTMSI Realloca tion Flag Old SGSN Address
N/A
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
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.
N/A
Issue 01 (2013-07-15)
1635
Unit N/A
NE Name
N/A
N/A
Name of a CN NE.
User Information
Param eter User ID:Alia s Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Supported NE Version UGW9810 V900R011C01 or later version
Procedure Information
Param eter Proced ure Type APN Rang e N/A Unit N/A Description Name of a signaling procedure. Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
Issue 01 (2013-07-15)
1636
Rang e NA UTR AN GER AN WLA N GAN HSP A Evolu tion EUT RAN
Unit N/A
N/A
N/A
Cause of the exception carried in an Access message. For details, see the Description of Exception Cause in the appendix.
PDP Type
N/A
MSIP
N/A
N/A
MS IP V4
N/A
N/A
Issue 01 (2013-07-15)
1637
Param eter MS IP V6 SGSN Addres s for Signali ng SGSN Addres s for Data GGSN Addres s for Signali ng GGSN Addres s for Data Protoco l Version
Rang e N/A
Unit N/A
Description IPv6 address allocated to the subscriber's MS IPv4 address for configuring the control plane of the SGSN that the subscriber's MS accesses
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
IPv4 address for configuring the user plane of the SGSN that the subscriber's MS accesses IPv4 address for configuring the control plane of the GGSN that the subscriber's MS accesses
N/A
N/A
N/A
N/A
IPv4 address for configuring the user plane of the GGSN that the subscriber's MS accesses Version of the GTP protocol
N/A
Issue 01 (2013-07-15)
1638
Unit N/A
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. Information about the PLMN served by the access SGSN Location area where the signaling procedure is triggered Routing area where the signaling procedure is triggered Serving area where the signaling procedure is triggered Cell where the signaling procedure is triggered IPv6 address for configuring the control plane of the SGSN that the subscriber's MS accesses
UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
RAC
N/A
N/A
SAC
N/A
N/A
CI
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1639
Param eter GGSN IPv6 Addres s for Signali ng SGSN IPv6 Addres s for Data GGSN IPv6 Addres s for Data NSAPI
Rang e N/A
Unit N/A
Description IPv6 address for configuring the control plane of the GGSN that the subscriber's MS accesses
N/A
N/A
IPv6 address for configuring the user plane of the SGSN that the subscriber's MS accesses
N/A
N/A
IPv6 address for configuring the user plane of the GGSN that the subscriber's MS accesses
N/A
N/A
Identity of the service access point (SAP) in the network layer Identifies whether an activation is a first or second activation
Activati on Type
N/A
N/A
N/A
Identity of the GTP-C tunneling protocol Marks different charging characteristics. For details, see 5.1.2.2.7 in 3GPP TS 32.298. 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.
UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
0-2^3 2-1
N/A
Issue 01 (2013-07-15)
1640
Rang e 0-2^3 2-1 SSG N MME GGS N SGW PGW SGW +PG W
Unit N/A
Description Unique No. of each service procedure in the whole procedure for a subscriber Initiator of the signaling message recorded in the CHR
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
Slot
N/A
N/A
Logical board No. of the device that processes the CHR Logical CPU No. of the device that processes the CHR SPU group No. of the device that processes the CHR SPU instance No. of the device that processes the CHR MCC and MNC of the subscriber's serving network CGI information, including MCC, MNC, LAC, and CI SAI information, including MCC, MNC, LAC, and SAC
UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
CPU
N/A
N/A
SPU Group SPU Instanc e Serving Networ k ULI CGI ULI SAI
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1641
Param eter ULI RAI ULI TAI ULI ECGI ULI LAI Peer IPV4 Addres s for Signali ng Peer IPV4 Addres s for Data Local IPV4 Addres s for Signali ng Local IPV4 Addres s for Data Peer IPV6 Addres s for Signali ng
Rang e N/A
Unit N/A
Description RAI information, including MCC, MNC, LAC, and RAC TAI information, including MCC, MNC, and TAC ECGI information, including MCC, MNC, and ECI LAI information, including MCC, MNC, and LAC IPv4 address for configuring the control plane of the CN NE interconnected to this NE
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
IPv4 address for configuring the user plane of the CN NE interconnected to this NE
N/A
N/A
N/A
N/A
N/A
N/A
IPv6 address for configuring the control plane of the CN NE interconnected to this NE
Issue 01 (2013-07-15)
1642
Param eter Peer IPV6 Addres s for Data Local IPV6 Addres s for Signali ng Local IPV6 Addres s for Data Proced ure Transac tion ID (PTI)
Rang e N/A
Unit N/A
Description IPv6 address for configuring the user plane of the CN NE interconnected to this NE
N/A
N/A
N/A
N/A
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.
Issue 01 (2013-07-15)
1643
Rang e MS or netwo rk provi ded APN, subsc ribed verifi ed MS provi ded APN, subsc riptio n not verifi ed Netw ork provi ded APN, subsc riptio n not verifi ed
Unit N/A
PDN Type
N/A
N/A
N/A
ID of the default bearer. This parameter can also be used to identify the PDN connection. ID of all bearers (including the default bearer) for the PDN connection
N/A
N/A
Issue 01 (2013-07-15)
1644
Param eter Bearer QoS PCI Bearer QoS PL Bearer QoS PVI Bearer QoS QCI Bearer QoS MBRU Bearer QoS MBRD Bearer QoS GBRU Bearer QoS GBRD UE Time Zone Protoco l Cause Flow QoS QCI Flow QoS MBRU Flow QoS MBRD
Rang e N/A
Unit N/A
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Standard cause value carried in the response message QCI in the Flow QoS parameter
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1645
Param eter Flow QoS GBRU Flow QoS GBRD UL Total Volume DL Total Volume Total Volume First URL MS Side Port of First URL Networ k Side Port of First URL
Rang e N/A
Unit N/A
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
byte
Uplink traffic volume recorded in the CHR Downlink traffic volume recorded in the CHR Total traffic volume recorded in the CHR First 20 bytes of the first URL that the subscriber visits during a service procedure TCP/UDP port No. (on the UE side) of the first URL that the subscriber visits during a service procedure
byte
byte
N/A
N/A
N/A
N/A
N/A
TCP/UDP port No. (on the network side) of the first URL that the subscriber visits during a service procedure
Issue 01 (2013-07-15)
1646
N/A
N/A
N/A N/A N/A N/A N/A N/A High TA Low uplink level on the TCH Uplink interference on the TCH
Issue 01 (2013-07-15)
1647
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Poor uplink quality of the TCH Sudden decrease of the uplink level Low downlink level on the TCH Downlink interference on the TCH Poor downlink quality of the TCH Sudden decrease of the downlink level Low uplink and downlink level on the TCH Uplink and downlink interference on the TCH Poor uplink and downlink quality of the TCH Any other Um interface-related fault Transmission fault CN fault Peer fault Other causes N/A N/A N/A N/A N/A High TA Low uplink level on the TCH Uplink interference on the TCH
Issue 01 (2013-07-15)
1648
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Poor uplink quality of the TCH Sudden decrease of the uplink level Low downlink level on the TCH Downlink interference on the TCH Poor downlink quality of the TCH Sudden decrease of the downlink level Low uplink and downlink level on the TCH Uplink and downlink interference on the TCH Poor uplink and downlink quality of the TCH Any other Um interface-related fault Transmission fault CN fault Peer fault Other causes N/A N/A N/A N/A N/A
Poor quality on the Um interface or fault of the terminal System resource congestion
N/A
Issue 01 (2013-07-15)
1649
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Transmission fault CN fault Other causes N/A N/A N/A N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault
N/A
N/A
Issue 01 (2013-07-15)
1650
Dom ain
Servi ce Type
Abnormal Type
RANCS
Call
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
N/A N/A N/A N/A High TA Low uplink level on the TCH Uplink interference on the TCH Poor uplink quality of the TCH Sudden decrease of the uplink level
Issue 01 (2013-07-15)
1651
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Low downlink level on the TCH Downlink interference on the TCH Poor downlink quality of the TCH Sudden decrease of the downlink level Low uplink and downlink level on the TCH Uplink and downlink interference on the TCH Poor uplink and downlink quality of the TCH Any other Um interface-related fault Transmission fault CN fault Peer fault Other causes N/A N/A N/A N/A N/A
Abnormal Delay
Overlong access time (MOC) Overlong access time (MTC) Overlong setup time (MOC) Overlong setup time (MTC)
N/A
N/A N/A
Issue 01 (2013-07-15)
1652
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Short calls (MOC) Short calls (MTC) N/A N/A N/A
Poor quality on the Um interface Bad DL HQI Bad UL HQI Bad UL VQI Uplink oneway audio Downlink oneway audio DL/UL no audio Downlink crosstalk Uplink crosstalk
N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
SMS
N/A N/A
RANPS
PS
Setup Failure
Case3: Attach fail Case2: PDP active fail Case3: No service interaction timeout
Service Interruption
N/A
Issue 01 (2013-07-15)
1653
Dom ain
Servi ce Type
Abnormal Type
Step1: Service interaction timeouts Step2: Service interaction with long latency
N/A
N/A
N/A
N/A N/A
Issue 01 (2013-07-15)
1654
Interface
Key Signaling 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 ROUTING AREA UPDATE ACCEPT ROUTING AREA UPDATE REJECT ROUTING AREA UPDATE COMPLETE AUTHENTICATION AND CIPHERING REJECT AUTHENTICATION AND CIPHERING REQUEST AUTHENTICATION AND CIPHERING RESPONSE
Issue 01 (2013-07-15)
1655
Interface
Key Signaling 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 SM-STATUS Channel Request Packet Channel Req Um Packet Control Acknowledgement (NB) Packet Control Ack (AB) Packet Cell Change Failure Packet Resource Request
Issue 01 (2013-07-15)
1656
Interface
Key Signaling 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 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 Downlink RLC Data header
Issue 01 (2013-07-15)
1657
N/A RRC Setup Failure RRC Setup Failure (Service-CS) RRC Setup Failure (Service-PS)
RRC Abnormal Release Overlong RRC Setup Delay (Nonservice) 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
HO Problem
Soft Handover Failure Hard Handover Failure Cell Update Failure Channel Handover Failure Migration Failure Inter-RAT Handover Failure PDP Activate Failure
Issue 01 (2013-07-15)
1658
Doma in RANCS
Abnormal CauseClassificatio n Nonexception Setup Failure Abnormal Release Service Quality Problem
Abnormal Cause-Subclassification
RAN 13.0
RAN 14.0
N/A CS RAB Setup Failure CS RAB Abnormal Release 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) Overlong RAB Connection Delay (Alerting)(MOC) Overlong RAB Connection Delay (Connect Ack)(MOC)
ShortCall Problem
VP
N/A CS RAB Setup Failure CS RAB Abnormal Release Overlong RRC Setup Delay
Issue 01 (2013-07-15)
1659
Doma in
Service Type
Abnormal CauseClassificatio n
Abnormal Cause-Subclassification Overlong RAB Connection Delay (MTC) Overlong RAB Connection Delay (MOC) Overlong RAB Connection Delay (Alerting)(MTC) Overlong RAB Connection Delay (Connect Ack)(MTC) Overlong RAB Connection Delay (Alerting)(MOC) Overlong RAB Connection Delay (Connect Ack)(MOC)
RAN 13.0
RAN 14.0
ShortCall Problem
SMS
N/A N/A PS RAB Setup Failure PS RAB Abnormal Release Overlow Average Downlink Throughput Overlow Average Uplink Throughput Average Downlink Transmission Rate Slow Average Uplink Transmission Rate Slow
Issue 01 (2013-07-15)
1660
Doma in
Service Type
Abnormal CauseClassificatio n
Abnormal Cause-Subclassification DL Average Rate Slow(sufficient resources) DL Average Rate Slow (insufficient resources)
RAN 13.0
RAN 14.0
Delay Problem
Overlong RRC Setup Delay Overlong RAB Connection Delay (MTC) Overlong RAB Connection Delay (MOC)
Other RANMulti Multi Service Multi Service (CS Included) Multi Service(PS Only)
Issue 01 (2013-07-15)
1661
ErrType Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure
ErrReason DL CE Congestion UL_DL CE Congestion UL CE Congestion DL CE Congestion UL_DL CE Congestion UL CE Congestion DL CE Congestion UL_DL CE Congestion UL Iub Band Congestion DL Iub Band Congestion UL_DL Iub Band Congestion UL Iub Band Congestion DL Iub Band Congestion UL_DL Iub Band Congestion DL Power Congestion Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure
Issue 01 (2013-07-15)
1662
ErrType Iub Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Radio Resource Congestion Uu Interface Failure Uu Interface Failure
ErrReason Iub AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Overload Control SRB Reset TRB Reset
Issue 01 (2013-07-15)
1663
ErrType Uu Interface Failure Uu Interface Failure Radio Resource Congestion Uu Interface Failure Uu Interface Failure Iu Relocation Failure Iu Relocation Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iub Interface Failure Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Iub Interface Failure Iub Interface Failure Iub Interface Failure
ErrReason SRB Reset TRB Reset Preempted User Due To Congestion Timer Expired Timer Expired Iu Relocation Preparation Failure Timer Relocation Preparation Expiry Iu Relocation Execution Timer Expiry Timer Expired Timer Expired Timer Expired Iu Relocation Preparation Iu Release Command Iu Relocation Execution Timer Expiry Iu Relocation Preparation Failure Timer Relocation Preparation Expiry 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 Iu Relocation Preparation Failure Target System Unsupport Iub Cell not Available DL CE Congestion UL CE Congestion UL CE Congestion DL CE Congestion Iub Control Plane Process Resources Overload Iub Hardware Failure Iub OAM Intervention Failure
Issue 01 (2013-07-15)
1664
ErrType Iub Interface Failure Iub Interface Failure Uu Interface Failure Iur Interface Failure Iur Interface Failure Iub Interface Failure Iur Interface Failure Iur Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure
ErrReason Iub not Enough User Plane Process Resources Failure Iub not Enough User Plane Process Resources Failure Radio Link Permanent Failure Iur AAL2/AL Establishment Failure Iur RL Reconfiguration Commit Timeout Iur Radio Link Reconfiguration Cancel Iur RL Add/Setup Timeout Iur Control Plane Process Resources Overload Radio Link Permanent Failure UE Reestablishment Timer Expired Timer Expired Timer Expired Overlapped Cell Update Overlapped Cell Update Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Overlapped Cell Update Timer Expired Overlapped Cell Update Timer Expired Uu Configuration Unsupport
Issue 01 (2013-07-15)
1665
ErrType Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure
ErrReason Uu Physical Channel Failure Uu Simultaneous Configuration Uu Compress Mode Runtime Tgpsi Error Uu Protocol Error Uu Protocol Error Uu Protocol Error Uu Protocol Error Uu Protocol 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 Physical CH Failure Uu Inter-RAT Change Failure Protocol Error Uu Inter-RAT Change Failure Unspecified UE Reestablishment
Abnormal Cause-Sub-classification
Net
RRC Setup Failure (Service) RRC Setup Failure (Non-service) Intra-RAT Outgoing Handover Failure Inter-RAT Outgoing Handover Failure Intra-RAT Incoming Handover Failure Inter-RAT Incoming Handover Failure
HO Failure
Delay Evaluati on
Delay Problem
Overlong RRC Setup Delay (Service) Overlong RRC Setup Delay (Non-service) Overlong Inter-RAT Outgoing Handover Delay Overlong Intra-RAT Outgoing Handover Delay Overlong Inter-RAT Incoming Handover Delay Overlong Intra-RAT Incoming Handover Delay
PS
Accessib ility Evaluati on Retainab ility Evaluati on Service Evaluati on for Delay
Setup Failure
Key Signaling
Procedure RRC Setup or Release Key Event RRC CONNECTION REESTABLISHMENT REQUEST RRC CONNECTION REJECT
Issue 01 (2013-07-15)
1667
Procedure
Key Event RRC CONNECTION REQUEST RRC CONNECTION SETUP COMPLETE RRC CONNECTION 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
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 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
Issue 01 (2013-07-15)
1668
Procedure
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)
The section describes the exception cause classification in the summary table. The section also lists the signaling procedure and the cause of procedure initiated. l l l l l Exception Cause Classification Exception Cause Field Description (SGSN/MME) Exception Cause Field Description (GGSN/SAE-GW) Signaling Procedure Cause of Procedure Initiated
Domin
Abnormal Sub-type Service Req Failure Service Req Overlong Delay Paging Failure Paging Overlong Delay Iu Release Failure RAB Release Failure PDP Act Failure PDP Act Overlong Delay PDP Sec Act Failure PDP Sec Act Overlong Delay PDP Mod Failure PDP Mod Overlong Delay PDP Deact Failure Rab Assignment Failure Rab Assignment Overlong Delay
Abnormal Paging Abnormal Iu Release Abnormal RAB Release Abnormal PDP Act
PDN GW Dedicated Bearer Act Failure PDN GW Dedicated Bearer Act Overlong Delay PDN GW Initiated Bearer Mod Failure PDN GW Initiated Bearer Mod Overlong Delay PDN GW Initiated Bearer Deact Failure NA Attach Failure Attach Overlong Delay Detach Failure Intra TAU Failure
Abnormal PDN GW Initiated Bearer Mod Abnormal PDN GW Initiated Bearer Deact Non-exception Abnormal Attach Abnormal Detach MME Procedure Abnormal TAU
Intra TAU Overlong Delay Inter TAU Failure Inter TAU Overlong Delay
Abnormal Handover
Issue 01 (2013-07-15)
1670
Domin
Abnormal Type
Abnormal Sub-type Intra E-UTRAN Handover Overlong Delay Inter RAT Handover Failure Inter RAT Handover Overlong Delay
S1 Release Failure Service Req Failure Service Req Overlong Delay Paging Failure Paging Overlong Delay Interoperation Failure Interoperation Overlong Delay Dedicated Bearer Act Failure Dedicated Bearer Act Overlong Delay Bearer Mod Failure Bearer Mod Overlong Delay Bearer Deact Failure Bearer Resourece Mod Failure Bearer Resourece Mod Overlong Delay PDN Connectivity Failure
Abnormal Paging
Abnormal Interoperation Abnormal Dedicated Bearer Act Abnormal Bearer Mod Abnormal Bearer Deact Abnormal Bearer Resourece Mod
Abnormal PDN
Non-exception Abnormal Create PDP GGSN Procedure Abnormal Update PDP Abnormal Delete PDP Traffic Non-exception Abnormal Create Session SAE-GW Procedure Abnormal Delete Session Abnormal Create Bearer Abnormal Modify Bearer
NA NA NA NA NA NA NA NA NA NA
Issue 01 (2013-07-15)
1671
Domin
Abnormal Type Abnormal Update Bearer Abnormal Delete Bearer Abnormal Release Access Bearers Abnormal Modify Bearer Command Abnormal Delete Bearer Command Abnormal Bearer Resource Command Abnormal Create Indirect Data Forwarding Tunnel Abnormal Delete Indirect Data Forwarding Tunnel Traffic
Abnormal Sub-type NA NA NA NA NA NA NA NA NA
Issue 01 (2013-07-15)
1672
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The differentiated service does not allow the access of subscriber. The system does not allow the access of SIM subscribers to the 3G network. The system does not allow the access of 2G subscribers. The license resource item restricts the subscriber access. The system does not allow the access of a certain APN subscriber. The system does not allow the access of IMSI subscribers to a certain location area. GPRS service not allowed caused by MVNO limits or CAMEL subscribers not allowed. The system is being closed. The PLMN does not allow the access of subscribers. The system does not allow the access of a certain CAMEL subscriber. The system does not allow the access of subscribers when being relocated. The system does not allow the access of SIM subscribers to the 4G network. This cause value indicates that system congestion occurs. When the number of attach requests initiated by MSs/UEs subscribed with a specific APN exceeds the predefined threshold, the SGSN/MME rejects subsequent such requests with the cause value of "Congestion" and starts an MM backoff timer. Before this timer expires, the SGSN/MME rejects all such requests with the same cause value. The ZC does not allow the access of subscribers. The ARD does not allow the access of subscribers. Local PLMN does not allow users to access. HLR does not respond.
SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Issue 01 (2013-07-15)
1673
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The authentication set cannot be obtained from the HLR. IMSI unknown MS has no subscription. This location area cannot be accessed by subscribers. The message returned by the HLR is incorrect. The HLR returns an unknown cause. The SCP has no response. SCP initiate detach CAMEL user The DNS server has no response. The response message returned by the DNS server is incorrect. The peer SGSN or MME has no response. The message returned from the peer SGSN indicates that the MS is already separated. The peer SGSN or MME does not have the MS information. The peer SGSN or MME returned incorrect IEs.
An inter-SGSN/MME process fails on the peer SGSN or MME. No PDP context is available. The signaling address of the peer SGSN is invalid. Undefined internal error CB operation failure This cause value indicates that the P-TMSI resource allocation fails.
Issue 01 (2013-07-15)
1674
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The VLR has no response. No available VLR The message returned by the VLR does not carry the MS information. The message returned by the VLR indicates that the location area cannot to be accessed. The message returned by the VLR carries an unknown reason. Receiving error messages Gb interface error An Iu interface error occurs. SDB failure OM delete user The subscriber data are inconsistent, and subscribers were detached. time out of reachable timer The SM does not respond. The SM failed to respond. No response to the S1 message. The target eNodeB does not access the core network. The eNodeB canceled the HO process. The eNodeB failed to respond. The HSS does not respond.
Issue 01 (2013-07-15)
1675
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The HSS returned an incorrect message. The UE's subscription information is not registered in the HSS. The UE's EPS subscription information is not registered in the HSS. A certain access type is restricted. The system does not allow the access of roaming subscribers. No required HSS is obtained. The HSS returned incorrect security data. The HSS failed to return security data. Incorrect APN Unknown PDP address or type Subscription data mismatch Context not found Last PDN connection not allowed Only IPv4 allowed Only IPv6 allowed Only single address allowed ESM message not received PDN connection not existing DNS resolution failure
Issue 01 (2013-07-15)
1676
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause Message syntax error Invalid message format Unknown resolved IMSI MS detached MS paging without response
Service not supported Incorrect mandatory IE Missing mandatory IE Incorrect optional IE System failure Authentication failure Subscriber authentication failure
Dynamic addresses occupied Semantic error in TFT operation Syntactical error in packet filtering Semantic error in packet filtering Unknown APN returned by GGSN Unknown PDP address or PDP type TFT not activated in PDP context
Issue 01 (2013-07-15)
1677
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Context not found Incorrect message format Invalid length Incorrect command IE Missing command IE Relocation failure PDN address type not supported UE paging without response Service denied Failure to page the UE Request rejected Unable to call UE in idle state Missing conditional IE Timeout of the network side This cause value indicates that multiple PDN connections are not allowed by the APN and accordingly fail. RAB assignment failure
Issue 01 (2013-07-15)
1678
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause RAB assignment failure in the MME IPv6 not supported Wildcard activation rejected Access to VPLMN denied No MVNO license DPP activation restricted by CDRF No MIP license No PPP license No license for conversation PDP activation requests No license for secondary activation Secondary activation not supported by GTPCv0 Activation rejected by differentiated service This cause value indicates that system congestion occurs. When the number of 2G/3G PDP context activation requests initiated by MSs/ UEs subscribed with a specific APN exceeds the predefined threshold, the SGSN rejects subsequent such requests with the cause value of "Congestion" and starts an SM backoff timer. Before this timer expires, the SGSN rejects all such requests with the same cause value. PDP context number limited by the license Access to CDRF VPLMN denied Service barred due to operator-determined barring Access to HPLMN denied
SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Issue 01 (2013-07-15)
1679
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause Resources insufficient Decoding failure Other unknown errors LLC or SNDCP failure Requested service unavailable temporarily Network failure Protocol error This cause value indicates that the UE request conflicts with procedures on the network. Operator determined barring GGSN rejection Unknown rejection cause NSAPI already used Regular deactivation. Reactivation required Context not found in secondary activation Only IPv4 allowed Only IPv6 allowed Only IPv4 or IPv6 allowed Invalid TI value
Issue 01 (2013-07-15)
1680
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause Message timeout SGW and PGW rejection PTI already in use Multiple PDN connections not allowed for the same APN UE conflicting with the network side Invalid QCI Invalid PTI Protocol error or unknown error The GGSN fails to resolve the Create PDP context Response message. SGSN deact PDP context with APN restriction The IP address of the GGSN accessed in DHCP or MIP mode is not resolved. RPU-related failures Other APN-related errors The GTPU response times out. The GTPU board returns a failure cause. Sending a message to the GTPU board fails. CB resources are insufficient. SGSN reject PDP context request with APN restriction Undefined error
Issue 01 (2013-07-15)
1681
Procedure Type SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure
Failure Cause Overlong Attach delays. Overlong Intra SGSN RAU delays. Overlong Inter SGSN RAU delays. Overlong Relocation delays. Overlong System Change delays. Overlong Service Req delays. Overlong Paging delays. Overlong PDP Act delays. Overlong PDP Sec Act delays. Overlong PDP Mod delays. Overlong Attach delays. Overlong Intra TAU delays. Overlong Inter TAU delays. Overlong Intra E-UTRAN Handover delays. Overlong Inter RAT Handover delays. Overlong Service Req delays. Overlong Paging delays. Overlong Interoperation delays. Overlong Dedicated Bearer Act delays. Overlong Bearer Mod delays. Overlong Bearer Resource Mod delays. Overlong PDN Connectivity delays.
The Activate PDP Context Request message is successfully processed. The received GTP header is incorrect.
Issue 01 (2013-07-15)
1682
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause When operations, such as handover and data check, are performed, the Update PDP Context Request message (GTP V0) is not processed. When operations, such as handover and data check, are performed, the Delete PDP Context Request message (GTP V0) is not processed. When operations, such as handover and data check, are performed, the Update PDP Context Request message (GTP V1) is not processed. When operations, such as handover and data check, are performed, the Delete PDP Context Request message (GTP V1) is not processed. The protocol type in the Create PDP Context message (GTP V0) is incorrect. When the Create PDP Context message (GTP V0) is preprocessed, the message is rejected if the License does not support IPv6 subscribers. When the Create PDP Context message (GTP V0) is preprocessed, ApnIndex cannot be found by using ApnName. The Create PDP Context Request message (GTP V0) fails to be processed because the actual APN information cannot be obtained from ApnIndex. When the Create PDP Context Request message (GTP V0) is preprocessed, the APN is locked. When the Create PDP Context Request message (GTP V0) is preprocessed, the SPU board is locked or the CPU is overloaded. The static IP address in the Create PDP Context Request message (GTP V0) is incorrect. The Create PDP Context Request message (GTP V0) fails because the static IP address is not matched; that is, the IP address contained in the list is not consistent with that carried in the message. When the Create PDP Context Request message (GTP V0) is preprocessed, the static IP address fails to be matched because the IP address belongs to the protected IP address segment. When the Create PDP Context Request message (GTP V0) is preprocessed, the operations of allocating the context space and establish the IMSI index fail The protocol type in the Create PDP Context message (GTP V1) is incorrect. When the Create PDP Context message (GTP V1) is preprocessed, ApnIndex cannot be found by using ApnName. The Create PDP Context message (GTP V1) is directly rejected if the License does not support IPv6 subscribers.
Issue 01 (2013-07-15)
1683
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Issue 01 (2013-07-15)
Failure Cause The Create PDP Context message (GTP V1) fails to be processed if the IMSI and MSISDN of V1 subscribers are not matched. When the Create PDP Context message (GTP V1) is preprocessed, the judgment on static IP addresses is invalid. The IPv4 static IP address in the Create PDP Context message (GTP V1) does not belong to the address segment configured by the APN. The IPv4 static IP address in the Create PDP Context message (GTP V1) is belongs to the protected address segment. The Create PDP Context message (GTP V1) fails to be processed because the APN is locked. Messages are sent to other boards. The possible cause is that the SPU is locked; the CPU is overloaded. The second Create PDP Context message (GTP V1) fails to be processed because the context cannot be found. The second Create PDP Context message (GTP V1) fails to be processed because PPP, L2tp, IPv6, and MIP subscribers do not support the second activation. The second Create PDP Context message (GTP V1) fails to be processed because the APN is locked. The same NSAPI is carried in the second Create PDP Context message (GTP V1). The NSAPI activated in the second Create PDP Context message (GTP V1) is the same as that activated in a common message. The second Create PDP Context message (GTP V1) fails to be processed because the second activation is not allowed when the handover or data check is performing. The second Create PDP Context message (GTP V1) fails to be processed because GGSN cannot allocate a context. The second Create PDP Context message (GTP V1) fails to be processed because the NSAPI attribute is incorrect. The Create PDP Context Request message (GTP V0) fails to be processed because the retrieved IE cannot be saved in the context. The Create PDP Context Request message (GTP V0) fails to be processed because the QoS negotiation fails. The Create PDP Context Request message (GTP V0) fails to be processed because the data stream labels cannot be allocated. The Create PDP Context Request message (GTP V0) fails to be processed because the signaling path cannot be established.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1684
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause The Create PDP Context Request message (GTP V0) fails to be processed because the data path cannot be established. The Create PDP Context Request message (GTP V0) fails to be processed because the subscriber is not authorized. The Create PDP Context Request message (GTP V0) fails to be processed because the global and APN configurations do not allow the access of roaming subscribers. The Create PDP Context Request message (GTP V0) fails to be processed because the global and APN configurations do not allow the access of visiting subscribers. The Create PDP Context Request message (GTP V0) fails to be processed because the timer cannot be created. The Create PDP Context Request message (GTP V1) fails to be processed because the TFT is invalid. The Create PDP Context Request message (GTP V1) fails to be processed because contents in the message cannot be saved in the context. The Create PDP Context Request message (GTP V1) fails to be processed because the QoS negotiation fails. The Create PDP Context Request message (GTP V1) fails to be processed because the signaling path cannot be established. The Create PDP Context Request message (GTP V1) fails to be processed because the data path cannot be established. The Create PDP Context Request message (GTP V1) fails to be processed because the subscriber is not authorized. The Create PDP Context Request message (GTP V1) fails to be processed because the global and APN configurations do not allow the access of roaming subscribers. The Create PDP Context Request message (GTP V1) fails to be processed because the global and APN configurations do not allow the access of visiting subscribers. The Create PDP Context Request message (GTP V1) fails to be processed because the timer cannot be created. The second Create PDP Context Request message (GTP V1) fails to be processed because the TFT is invalid. The second Create PDP Context Request message (GTP V1) fails to be processed because the message does not carry a TFT and a context without a TFT exists.
Issue 01 (2013-07-15)
1685
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause The second Create PDP Context Request message (GTP V1) fails to be processed because contents in the message cannot be saved in the context. The second Create PDP Context message (GTP V1) fails to be processed because the context cannot be found. The second Create PDP Context message (GTP V1) fails to be processed because the context RAI carried in this message is not consistent with that of the related context. The second Create PDP Context Request message (GTP V1) fails to be processed because the QoS negotiation fails. The second Create PDP Context Request message (GTP V1) fails to be processed because the signaling path cannot be established. The second Create PDP Context Request message (GTP V1) fails to be processed because the data path cannot be established. The second Create PDP Context Request message (GTP V1) fails to be processed because the timer cannot be created. It is the cause value of failed authentication sent from the Radius module. In the DHCP ACK message sent by the DHCP server, the returncode is failure. The filter number reaches the maximum number when the Create PDP Context Request message is successfully processed. Creating the NP list fails when the Create PDP Context Request message is successfully processed. When the Create PDP Context Request message is successfully processed, the corresponding response message fails to be sent. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN PDP is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN universal PDP is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the global PDP is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the global universal PDP is reached.
Issue 01 (2013-07-15)
1686
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Issue 01 (2013-07-15)
Failure Cause When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN bandwidth is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN universal bandwidth is reached. The Update PDP Context Request message is successfully processed. The protocol type in the Update PDP Context Request message (GTP V0) is incorrect. The context carried in the Update PDP Context Request message (GTP V0) cannot be found. The Update PDP Context Request message (GTP V0) fails to be processed because the CPU is overloaded. Mandatory IEs are absent in the Update PDP Context Request message. The IMSI cannot be obtained from the Update PDP Context Request message (GTP V1) and the context cannot be located based on the TEID (C) + NSAPI. The IMSI is obtained from the Update PDP Context Request message (GTP V1), but the context cannot be located based on the TEID (C) + NSAPI. The IMSI in the Update PDP Context Request message (GTP V1) cannot be found because of the version change. The context in the Update PDP Context Request message (GTP V1) cannot be found after the IMSI is obtained because of the version change. The Update PDP Context Request message (GTP V1) fails to be processed because the CPU is overloaded. The Update PDP Context Request message (GTP V1) fails to be processed because the TFT carried in the message is invalid. The Update PDP Context Response message (GTP V1) is received, but the message format is incorrect. The V1 Update PDP Context Response message is received, but the corresponding request message cannot be found. After the Update PDP Context Response message (GTP V1) is received, the context fails to be found based on the index. The number of filters exceeds the limit after the Update PDP Context Request message is processed. IEs cannot be saved in the context when the Update PDP Context Request message (GTP V1) is processed.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1687
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause When the Update PDP Context Request message is processed and the GTP version is updated from V1 to V0, the data stream labels fail to be allocated. IEs cannot be saved in the context when the Update PDP Context Request message (GTP V0) is processed. Negotiating the QoS fails when the Update PDP Context Request message is processed. Updating the signaling path fails when the Update PDP Context Request message is processed. Updating the data path fails when the Update PDP Context Request message is processed. Updating a local subscriber to a roaming subscriber fails when the Update PDP Context Request message is processed. Updating the charging information fails when the Update PDP Context Request message is processed. The NP fails to update the context when the Update PDP Context Request message is processed. After the Update PDP Context Response message is received, the SGSN rejects the update originated by the GGSN. After the Update PDP Context Response message is received, the QoS version carried in the message is not supported. After the Update PDP Context Response message is received, the GTPU table fails to be sent to the NP. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN bandwidth is reached. The Deactivate PDP Context Request message is successful processed. The protocol type in the Delete PDP Context Request message (GTP V0) is incorrect. The context is not found in the Delete PDP Context Request message (GTP V0). After an V0 subscriber receives the Delete PDP Context Request message (GTP V1), a failure response is returned. An IE is absent in the Delete PDP Context Request message (GTP V1) or the message is invalid. The context to be deleted in the Delete PDP Context Request message (GTP V1) does not exist whereas the related context exists.
Issue 01 (2013-07-15)
1688
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause When the Delete PDP Context Request message (GTP V1) does not carry TEARDOWN, no corresponding context can be found in the SDB context. The Delete PDP Context Request message (GTP V1) requests to delete the last context, but TEARDOWN is not carried in this message. The value of TEARDOWN carried in the Delete PDP Context Request message (GTP V1) is 0 and no corresponding context can be found in the SDB context. The Delete PDP Context Request message (GTP V1) requests to delete the last context, but the value of TEARDOWN in this message is 0. When the Delete PDP Context Response message (GTP V0) is received, the protocol type carried in the message is incorrect. Thus, an incorrect response message is received and the context cannot be found. When the Delete PDP Context Response message (GTP V0) is received, the protocol type carried in the message is incorrect. Thus, an incorrect response message is received. The Delete PDP Context Response message (GTP V0) fails to be processed because the context cannot be located. When the Delete PDP Context Response message (GTP V0) is received, the context fails to be converted to an pointer. The received Delete PDP Context Response message (GTP V0) is incorrect. When the Delete PDP Context Response message (GTP V0) is received, the corresponding request message cannot be found. The Delete PDP Context Response message (GTP V0) fails to be processed because the context cannot be found by using the index. The Create Session Request message is successfully processed. The Create Session Request fails to be processed because the UGW9811 is locked and does not allow the access from new subscribers. The Create Session Request message fails to be processed because the board is in smooth state after the active/standby switchover and does not allow the access from new subscribers. The Create Session Request message fails to be processed because obtaining product types fails based on a request IE. The Create Session Request message fails to be processed because obtaining APN IE from IEs contained in the message fails. The Create Session Request message fails to be processed because the PGW receives the message in a non-Attach scenario.
Issue 01 (2013-07-15)
1689
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Create Session Request message fails to be processed because license resources are insufficient for the type of products. The Create Session Request message fails to be processed because the system traffic reaches license limitation and the access from new subscribers is not allowed. The Create Session Request message fails to be processed because the IP address of the peer NE is on the blacklist or is not on the whitelist. The Create Session Request message fails to be processed because obtaining the usage scenario of the message fails. The Create Session Request message fails to be processed because checking the validity of the message fails. The Create Session Request message fails to be processed because applying for a bearer context fails. The Create Session Request message fails to be processed because the board is locked. The Create Session Request fails to be processed because filter resources are insufficient. The Create Session Request message fails to be processed because creating a signaling path fails. The Create Session Request message fails to be processed because policy control implemented by the PCRF, AAA server, or the UGW9811 configuration fails. The Create Session Request message fails to be processed because the QCI type is incorrect during the QoS check performed during the interaction between UGW9811 and PCRF. The Create Session Request message fails to be processed because the SGW fails to forward the message to the PGW. The Create Session Request message fails to be processed because the peer NE fails to respond before the timeout. The Create Session Request message fails to be processed because the peer NE returns a rejection message. The Create Session Request message fails to be processed because the system fails to start charging. The Create Session Request message fails to be processed because an internal system error occurs during the processing and causes subscribers to fail to access the UGW9811. The Create Session Request message fails to be processed because the system fails to enable the content resolution function.
Issue 01 (2013-07-15)
1690
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Create Session Request fails to be processed because license resources are insufficient and the access from subscribers is not allowed. The Create Session Request message fails to be processed because the system fails to start data forwarding. The Create Session Request message fails to be processed because initiating AAA authentication fails. The Create Session Request message fails to be processed because mapping the APN to in the request to the actual APN fails. The Create Session Request message fails to be processed because the access from roaming subscribers is not allowed after authentication. The Create Session Request message fails to be processed because the IP address obtained from the AAA server is incorrect. The Create Session Request message fails to be processed because userprofile fails to be obtained based on the user-profile name issued by the AAA server. The Create Session Request message fails to be processed because creating L2TP tunnel fails. The Create Session Request message fails to be processed because routing resources are insufficient which results in the failure of the access from subscribers. The Create Session Request message fails to be processed because the static IP address or IP address allocated by the AAA server is incorrect. The Create Session Request message fails to be processed because obtaining an IP address fails. The Create Session Request message fails to be processed because QoS control fails. The Create Session Request message fails to be processed because the message decode fails. The Create Session Request message fails to be processed because an internal system error occurs during the processing. The Modify Bearer Request message is successfully processed. 1. The Modify Bearer Request message fails to be processed because the board is in smooth state after the switchover and does not allow the access from subscribers. 2. No default bearer can be found. The Modify Bearer Request message fails to be processed because the address of the peer NE is on the blacklist or is not on the whitelist.
Issue 01 (2013-07-15)
1691
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Modify Bearer Request message fails to be processed because non-PGW NEs receive a message that does not contain bearer information. The Modify Bearer Request message fails to be processed because the bearer contained in the message belongs to multiple PDN Connections. The Modify Bearer Request message fails to be processed because obtaining the product type fails. The Modify Bearer Request message fails to be processed because checking the validity of IEs contained in the message fails. The Modify Bearer Request message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message. The Modify Bearer Request message fails to be processed because subscribers are on the multi-service APN and they are not allowed to switch to Gptv2 subscribers. The Modify Bearer Request message fails to be processed because obtaining an APN fails. The Modify Bearer Request message fails to be processed because the an internal system error occurs in the UGW9811 during the processing. The Modify Bearer Request message fails to be processed because the interaction between the UGW9811 and the PCRF fails. The Modify Bearer Request message fails to be processed because the system fails to enable the content resolution function. The Modify Bearer Request message fails to be processed because the system fails to start charging. The Modify Bearer Request message fails to be processed because an internal system error occurs during the processing. The Modify Bearer Request message fails to be processed because filter resources are insufficient. The Modify Bearer Request fails to be processed because the SGW fails to forward the request message to the PGW. The Modify Bearer Request message fails to be processed because the peer NE fails to respond before the timeout. The Modify Bearer Request message fails to be processed because the peer NE returns a rejection message code. The Modify Bearer Request message fails to be processed because the system fails to start data forwarding. The Modify Bearer Request message fails to be processed because the message decode fails.
Issue 01 (2013-07-15)
1692
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Issue 01 (2013-07-15)
Failure Cause
The Delete Session Request message is successfully processed. The Delete Session Request message fails to be processed because subscribers' bearer information cannot be found. The Delete Session Request message fails to be processed because NEs in the request message are invalid. The Delete Session Request message fails to be processed because no default bearers can be found. The Delete Session Request message fails to be processed because in the nonGUL handover scenario the GGSN receives the message. In the scenario of switching services from the SPGW to the PGW, the Delete Session Request fails to be processed because a response message fails to be sent. The Delete Session Request message fails to be processed because the system processes the message improperly. The Delete Session Request message fails to be processed because the SGW receives a failure response from the PGW. The Create Bearer Request message is successfully processed. The Create Bearer Request message fails to be processed because IEs in the message are incorrect. The Create Bearer Request message fails to be processed because the information about subscriber default bearers fails to be obtained. The Create Bearer Request message fails to be processed because the number of default bearers reaches the specifications and creating dedicated bearers fails. The Create Bearer Request message fails to be processed because the NE type is incorrect. The Create Bearer Request message fails to be processed because subscriber dedicated bearers fail to be created. The Create Bearer Request message fails to be processed because the PGWFQ-CSID fails to be processed. The Create Bearer Request message fails to be processed because the TFT fails to be processed. The Create Bearer Request message fails to be processed because applying for a memory to store PCO fails. The Create Bearer Request message fails to be processed because the PCO IE fails to be resolved.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1693
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Create Bearer Request message fails to be processed because the IMS signaling bearer fails to be queried. The Create Bearer Request message fails to be processed because roaming subscribers cannot use the extended QCI. The Create Bearer Request message fails to be processed because QoS control fails. The Create Bearer Request message fails to be processed because session control resources fail to be applied. The Create Bearer Request fails to be processed because filter resources are insufficient. The Create Bearer Request message fails to be processed because the signaling or data path fails to be created. The Create Bearer Request message fails to be processed because the system fails to start data forwarding. The message Create Bearer Request fails to be processed because the SGW fails to forward a request message to the MME. The Create Bearer Request message fails to be processed because peripheral NEs fail to respond before the timeout. The Create Bearer Request message fails to be processed because the peer NE returns a rejection message code. The Create Bearer Request message fails to be processed because the system fails to start charging. The Create Bearer Request message fails to be processed because an internal system error occurs during the processing. The Create Bearer Request message fails to be processed because the system fails to enable the content resolution function. The Create Bearer Request fails to be processed because license resources are insufficient and the access from subscribers is not allowed. The Create Bearer Request message fails to be processed because the message decode fails. The Create Bearer Request message fails to be processed because the system processes the message improperly. The UGW9811 actively initiates Create Bearer procedure, and the peer NE returns a success message code. The UGW9811 actively initiates Create Bearer procedure, but the peer NE returns a rejection message code.
Issue 01 (2013-07-15)
1694
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause
The Update Bearer Request message is successfully processed. The Update Bearer Request message fails to be processed because the message contains incorrect IEs. 1. The Update Bearer Request message fails to be processed because the board is in smooth state after the switchover and does not allow the bearer update. 2. The bearer cannot be found based on the TEID in the message. The Update Bearer Request message fails to be processed because the bearer information fails to be obtained based on the EBI and LBI IEs in the message. The Update Bearer Request message fails to be processed because the product is not the SGW. The Update Bearer Request message fails to be processed because applying for a bearer context fails. The Update Bearer Request message fails to be processed because the PTI in the message is inconsistent with that in the default bearer. The Update Bearer Request message fails to be processed because the message fails to be forwarded to the MME. The Update Bearer Request message fails to be processed because the peer NE fails to respond before the timeout. The Update Bearer Request message fails to be processed because the peer NE returns a rejection message code. The Update Bearer Request message fails to be processed because the system fails to start charging. The Update Bearer Request message fails to be processed because an internal system error occurs during the processing. The Update Bearer Request message fails to be processed because filter resources are insufficient. The Update Bearer Request message fails to be processed because an internal system error occurs during the processing. The Update Bearer Request message fails to be processed because the system fails to start data forwarding. The Update Bearer Request message fails to be processed because the message decode fails. The UGW9811 initiates the Update Bearer procedure, and the peer NE returns a success message code. The UGW9811 initiates the Update Bearer procedure, but the peer NE returns a rejection message code.
Issue 01 (2013-07-15)
1695
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause
The Delete Bearer Request message is successfully processed. The Delete Bearer Request message fails to be processed because IEs in the message are invalid. The Delete Bearer Request message fails to be processed because information about subscriber bearers fails to be found. The Delete Bearer Request message fails to be processed because subscriber bearers to be deleted fail to be found. The Delete Bearer Request message fails to be processed because no default bearers can be found. The Delete Bearer Request message fails to be processed because the NE type in the message is incorrect. The Delete Bearer Request message fails to be processed because an internal system error occurs and causes a failure in deleting subscriber bearers. The Delete Bearer Request message fails to be processed because the message decode fails. In a UGW9811-initiated Delete Bearer procedure, the peer NE sends a Delete Bearer Response message to the UGW9811. In a UGW9811-initiated Delete Bearer procedure, the peer NE sends a Delete Bearer Response message carrying a failure cause value to the UGW9811. The Release Access Bearers Request message is successfully processed. The Release Access Bearers Request message fails to be processed because no bearer information of the subscriber is found. The Release Access Bearers Request message fails to be processed. The Modify Bearer Command message is successfully processed. The Modify Bearer Command message fails to be processed because no bearer information of the subscriber is found. The Modify Bearer Command message fails to be processed because an IE in the message is invalid. The Modify Bearer Command message fails to be processed because no information about the default bearer of the subscriber is found. The Modify Bearer Command message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message.
Issue 01 (2013-07-15)
1696
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Issue 01 (2013-07-15)
Failure Cause The Modify Bearer Command message fails to be processed because the Sequence Number IE ID is incorrect. The Modify Bearer Command message fails to be processed because the extended QCI cannot be used when the subscriber is in roaming state. The Modify Bearer Command message fails to be processed because peripheral NEs fail in processing the message. The Modify Bearer Command message fails to be processed because no response is received from peripheral NEs before timeout or peripheral NEs fails in processing the message, which causes the failure in updating bearers. The Modify Bearer Command message fails to be processed because the message decode fails. The Delete Bearer Command message is successfully processed. The Delete Bearer Command message fails to be processed because no bearer information of the subscriber is found. The Delete Bearer Command message fails to be processed because the Sequence Number IE ID is incorrect. The Delete Bearer Command message fails to be processed because an IE in the message is invalid. The Delete Bearer Command message fails to be processed because the EBI in the message is incorrect. The Delete Bearer Command message fails to be processed because the subscriber bearer is not established or has been updated on the NE. The Delete Bearer Command message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message. The Delete Bearer Command message fails to be processed because peripheral NEs fail in processing the message. The Delete Bearer Command message fails to be processed because no response is received from peripheral NEs before timeout or peripheral NEs fails in processing the message, which causes the failure in updating bearers. The Bearer Resource Command message is successfully processed. The Bearer Resource Command message fails to be processed because no bearer information of the subscriber is found. The Bearer Resource Command message fails to be processed because an IE in the message is invalid. The Bearer Resource Command message fails to be processed because the bearer of the subscriber is being deleted.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1697
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Bearer Resource Command message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message. The Bearer Resource Command message fails to be processed because the Fteid IE in the message is incorrect. The Bearer Resource Command message fails to be processed because the memory application fails after the PCO setting is saved. The Bearer Resource Command message fails to be processed because the parsing of the PCO IE fails. The Bearer Resource Command message fails to be processed because the total CBR of the subscriber bearer is greater than the maximum GBR configured for the APN. The Bearer Resource Command message fails to be processed because the previous Bearer Command message has not been processed. The Bearer Resource Command message fails to be processed because the Sequence Number IE ID is incorrect. The Bearer Resource Command message fails to be processed because no IMS signaling bearer is found. The Bearer Resource Command message fails to be processed because peripheral NEs fail in processing the message. The Bearer Resource Command message fails to be processed because no response is received from peripheral NEs before timeout or peripheral NEs fails in processing the message, which causes the failure in performing bearer operations. The Bearer Resource Command message fails to be processed because the message decode fails. The Create Indirect Data Forwarding Tunnel Request message is successfully processed. The Create Indirect Data Forwarding Tunnel Request message is successfully processed. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because an IE in the message is invalid. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because the NE type is neither SGW nor SPGW. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because no bearer is found for the operation. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because the message decode fails.
Issue 01 (2013-07-15)
1698
Failure Cause The Delete Indirect Data Forwarding Tunnel Request message is successfully processed.
Signaling Procedure
Procedure Type SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN Procedure Name GPRS Attach Combined Attach MS Init GPRS Detach MS Init Combined Detach CN Init GPRS Detach CN Init Combined Deatch Implicit GPRS Detach Implicit Combined Detach RAN Init Iu Release CN Init Iu Release RAU(others) Intra RAU Intra Combined RAU Inter RAU Inter Combined RAU Periodic RAU Periodic Combined RAU Intra SRNS Relocation Inter SRNS Relocation 3G to 2G System Change 2G to 3G System Change Service Req Paging MS Init PDP Act
Issue 01 (2013-07-15)
1699
Procedure Type SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME
Procedure Name MS Init PDP Sec Act CN Init PDP Act MS Init PDP Deact CN Init PDP Deact MS Init PDP Mod CN Init PDP Mod RAN Init RAB Release CN Init RAB Release CN Init PDP Sec Act RAB Assignment PDN GW Dedicated Bearer Act PDN GW Initiated Bearer Mod PDN GW Initiated Bearer Deact Attach Intra USN Intra E-UTRAN TAU Inter USN Intra E-UTRAN TAU eNodeB S1 Release CN Init S1 Release Ms Init Detach CN Init Detach X2 HandOver Intra MME S1 HandOver Inter MME S1 HandOver Paging Service Req Intra USN GERAN to E-UTRAN Inter RAT TAU Intra USN UTRAN to E-UTRAN Inter RAT TAU Intra USN UTRAN Iu mode to E-UTRAN Inter RAT handover Inter USN UTRAN Iu mode to E-UTRAN Inter RAT handover Inter USN GERAN/UTRAN to E-UTRAN TAU
Issue 01 (2013-07-15)
1700
Procedure Type MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME GGSN GGSN GGSN GGSN SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW
Procedure Name MME to 3G SGSN combined hard handover and SRNS relocation procedure Intra USN E-UTRAN to GERAN Inter RAT RAU Intra USN E-UTRAN to UTRAN Inter RAT RAU Intra USN E-UTRAN to UTRAN Iu mode Inter RAT handover Inter USN E-UTRAN to UTRAN Iu mode Inter RAT handover Inter USN E-UTRAN to GERAN/UTRAN Inter RAT RAU 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure Dedicated Bearer Act PDN GW Initiated Bearer Mod with Bearer QoS Update HSS Initiated Subscribed QoS Mod PDN GW Initiated Bearer Mod Without Bearer QoS Update PDN GW Initiated Bearer Deact MME Initiated Dedicated Bearer Deact Bearer Resource Mod PDN Connectivity PDN Disconnection Create PDP Update PDP Delete PDP Traffic Create Session Modify Bearer Delete Session Create Bearer Update Bearer Delete Bearer Release Access Bearers Modify Bearer Command Delete Bearer Command
Issue 01 (2013-07-15)
1701
Procedure Name Bearer Resource Command Create Indirect Data Forwarding Tunnel Delete Indirect Data Forwarding Tunnel Traffic
Issue 01 (2013-07-15)
1702
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
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 CHR_PROC_INIT_CAUSE_SGSN_DEACT_V1_GGSN_ERR_IN D CHR_PROC_INIT_CAUSE_SGSN_DEACT_V0_SGSN_ERR_IN D CHR_PROC_INIT_CAUSE_SGSN_DEACT_V1_SGSN_ERR_IN D CHR_PROC_INIT_CAUSE_SDB
Issue 01 (2013-07-15)
1703
Cause
Procedure initiated by the GGSN Procedure initiated by the DNS Procedure initiated by the MSC Procedure initiated by the EIR Procedure initiated by the SCP Procedure initiated by the BSS Procedure initiated by the RNC
Issue 01 (2013-07-15)
1704
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 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
Issue 01 (2013-07-15)
1705
5
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. 5.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. 5.2 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. 5.3 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. 5.4 LTE Network Geographic Observation
Issue 01 (2013-07-15)
1706
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. 5.5 VIP Analysis By monitoring the indicators related to the quality of service of VIP subscribers, the Nastar helps you identify and solve the network problems that may cause VIP complaints so that the service quality of VIP subscribers is ensured and the satisfaction of VIP subscribers is improved.This function can be used to quickly locate and resolve problems. Normally there is no way to avoid that some user data such as International Mobile Subscriber Identity (IMSI) will be used during the troubleshooting. However, this function provides an anonymous data processing method. You are obligated to take considerable measures, in compliance with the laws of the countries concerned and the user privacy policies of your company, to ensure that the personal data of users is fully protected. 5.6 Complaint Analysis Support After receiving a subscriber complaint, the Nastar can quickly searches for all call records of the complaint subscriber in a problem cell based on the known problem cell and International Mobile Subscriber Identity (IMSI) of the complaint subscriber, MSISDN number, or peer MSISDN of the complaint subscriber. Through the analysis of causes of exceptions such as access failure, handover failure, and abnormal call drop, the Nastar helps you locate and solve complaint problems.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.
Issue 01 (2013-07-15)
1707
Function Description
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 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 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, and RSRQ), 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 HO failures, Inter-RAT HO requests, and Inter-RAT HO failures). 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1708
Issue 01 (2013-07-15)
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. Figure 5-1 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 5-1. Figure 5-1 Principles for analysis
Issue 01 (2013-07-15)
1709
Table 5-1 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue a subscrip tion comma nd Forward the subscrip tion comma nd Upload raw data (CHR) 2. Subscri be to applicat ion data Issue an applicat ion data subscrip tion comma nd Deliver a preproc essing task (direct) Collect data (CHR) (direct) Sou rce Nast ar Serv er Dest inati on eSA U Purpose
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.
eSA U
M20 00
M20 00
eNod eB
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNo deB
Nast ar Serv er
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eSA U
LTE SAU
To deliver a data-preprocessing task to the LTE SAU, requesting the LTE SAU to start the data-preprocessing task.
LTE SA U
Trac e Serv er
Issue 01 (2013-07-15)
1710
Proced ure
Purpose
The collected data (eNodeB CHR) is placed in the specified path of the LTE SAU.
Upload preproc essed data (direct) 3. Check the integrit y of analysi s data Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
LTE SA U
eSA U
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
Nast ar Serv er
To deliver 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.
eSA U
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Issue 01 (2013-07-15)
1711
Item Execution type Number of analysis tasks to be created Network scale to be analyzed in a task Time range of analysis 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. If the OSS information has been already configured, the Nastar automatically collects and imports the configuration data after the OSS and NE information is configured. You can also manually collect the configuration data before the specified time period starts. After the configuration data is imported, you can choose Maintenance > Data Maintenance Management to check whether the configuration data is available in the Nastar database. For detailed information about collecting, importing, and checking, see 2.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.
NOTE
You are advised to perform coverage analysis with the granularity of a day to ensure the validity and timeliness of the configuration data.
NE Group Information An NE group consists of NEs that are centrally managed. During Nastar theme analysis, the Nastar obtains NE information from NE groups. Before creating an analysis task, ensure that NE groups are configured. For detailed operations, see 2.4.5 Managing NE Groups.
Prerequisite
LTE configuration data has been imported to the Nastar Database. For details, see 5.1.2 Preparations for LTE Coverage Analysis.
Procedure
Figure 5-2 shows the analysis process.
Issue 01 (2013-07-15)
1713
Issue 01 (2013-07-15)
1714
Table 5-2 Description of the LTE coverage analysis process N Procedure o . ( 1 ) Check the integrity of LTE coverage analysis data Description Reference
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to LTE FDD Coverage Analysis Data or LTE TDD Coverage Analysis Data. 2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
1715
Description
Reference
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription 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. 4. In the Basic Subscription Settings 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. Subscribe to LTE coverage analysis data (application) Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription 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.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1716
Description
Reference
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to LTE FDD Coverage Analysis Data or LTE TDD Coverage Analysis Data. 2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
( 3 )
Navigation path: In the left navigation tree of the Analysis Task Management window, choose Theme Function > Basic Network Optimization > LTE Coverage Analysis. Procedure: 1. Double-click the LTE Coverage Analysis node. 2. Set the task name and task remarks. Click Next. 3. On the Select NE(s) tab page, select the analysis type and NEs to be analyzed. 4. On the Parameter Settings tab page, set filter criteria. 5. Select MR 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 Analysis Task Parameters.
Issue 01 (2013-07-15)
1717
Description
Reference
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the 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.
l For details, see 2.8 Querying Analysis Results l For details on the description about the window for displaying task results, see 5.1.4 Interface Description: LTE Coverage Analysis.
( 5 )
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon in the toolbar. 2. Set the export path and export format. 3. Click Save.
Parameter configuration
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1718
Description Sets the filter criteria for analysis data. A maximum of 30 filter criteria are allowed. 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.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Main Window
The LTE coverage analysis results are displayed in 2D charts, 3D charts, and tables. For details, see Figure 5-3, Figure 5-4, and Figure 5-5.
Issue 01 (2013-07-15)
1719
No. 1
Description Provides the button to export the summary report on LTE coverage analysis. Specifically, the summary information about all cells to be analyzed 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.
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 . The cells matching the search criteria will be Enter or click quickly displayed in the NE list, which is convenient for users.
Issue 01 (2013-07-15)
1720
No. 3
Description 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, and UE TXPOWER. 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 TXPOWER. 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 TXPOWER. l Number of Events/TA service have multiple KPIs, including RRC connect setup requests, RRC connect setup failures, call drops, call reestablishment, Inter-RAT HO requests, and uplink/ downlink retransmission. 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 number of times that each event occurs. 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 from the shortcut menu to adjust the size of the chart. l You can also use the shortcut menu items to query, save, or print the chart.
Issue 01 (2013-07-15)
1721
No. 4
Description Contains four tab pages: RSRQ/RSRP, TA/UE TXPOWER, TA/ RSRP, and TA/RSRQ. The four KPI pairs are formed with two of the four KPIs: TA, RSRQ, RSRP, and UE TXPOWER. 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. 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 3dimension chart, and click Calculate. The Nastar automatically calculates the total percentage of KPI layout within the value ranges.
Issue 01 (2013-07-15)
1722
No. 6
Description Displays the statistics of the KPIs of all services in the 2-dimension window. For details about parameters, see 5.1.5 Parameters for Viewing LTE Coverage Analysis Results.
Parameter
Parameter Total Number of TA Measurement Reports Range [0, +) Unit Number Description Indicates the total number of TA MRs in MRs for coverage analysis. Supported NE Version LTE 3900 V100R005C00 or later version
Issue 01 (2013-07-15)
1723
Range [0, +)
Unit Number
Description Indicates the total number of UE TxPower MRs in MRs for coverage analysis. Indicates the total number of RSRP MRs in MRs for coverage analysis. Indicates the total number of RSRQ MRs in MRs for coverage analysis. Indicates the timing advance, which reflects the distance between the UE and the eNodeB. Indicates the transmit power of a UE, which reflects the coverage strength of uplink signals. Indicates the reference signal receive power, which reflects the coverage strength of downlink reference signals.
[0, +)
Number
[0, +)
Number
Average TA
[0,1314]
16*Ts=0.52 ms
Average UE TX Power
[-17,23]
dBm
Average RSRP
[-140,-44]
dB
Issue 01 (2013-07-15)
1724
Range [-19.5,-3]
Unit dBm
Description Indicates the reference signal receive strength, which reflects the coverage quality of downlink reference signals.
Function Description
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.
Issue 01 (2013-07-15)
1725
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.
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. Figure 5-6 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 5-3. Figure 5-6 Principles for analysis
Issue 01 (2013-07-15)
1726
Table 5-3 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue a subscrip tion comma nd Forward the subscrip tion comma nd Upload raw data (eNode B CHR) Upload raw data (MME CHR) Sou rce Nast ar Serv er Dest inati on eSA U Purpose
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.
eSA U
M20 00
M20 00
eNod eB
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNo deB
MM E
To upload the raw data (MME CHR) to the LTE SAU directly.
NOTE The generation and transmission of the MME CHR data is not triggered by the Nastar subscription command. The MME CHR data will be uploaded to the LTE SAU through Huawei internal protocols in real time after the CHR data reporting values are configured and the CHR data transmission switch is enabled.
Issue an applicat ion data subscrip tion comma nd Deliver a preproc essing task (direct)
Nast ar Serv er
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eSA U
LTE SAU
To deliver a data-preprocessing task to the LTE SAU, requesting the LTE SAU to start the data-preprocessing task.
Issue 01 (2013-07-15)
1727
Purpose
The collected data (eNodeB CHR) is placed in the specified path of the LTE SAU.
Upload preproc essed data (direct) 3. Check the integrit y of analysi s data Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
eSA U
To upload preprocessed data (eNodeB CHR and MME CHR) to the eSAU.
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
Nast ar Serv er
To deliver 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.
eSA U
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Issue 01 (2013-07-15)
1728
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. If the OSS information has been already configured, the Nastar automatically collects and imports the configuration data after the OSS and NE information is configured. You can also manually collect the configuration data before the specified time period starts. After the configuration data is imported, you can choose Maintenance > Data Maintenance Management to check whether the configuration data is available in the Nastar database. For detailed information about collecting, importing, and checking, see 2.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.
NOTE
To ensure the validity of the configuration data, you are advised to perform terminal analyses on a per day basis.
NE Group Information An NE group consists of NEs that are centrally managed. During Nastar theme analysis, the Nastar obtains NE information from NE groups. Before creating an analysis task, ensure that NE groups are configured. For detailed operations, see 2.4.5 Managing NE Groups.
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.
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. 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. 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1730
Issue 01 (2013-07-15)
Prerequisites
The LTE configuration data and LTE engineering parameters have been imported into the Nastar database. The NE groups have been created. The terminal types and service types have been configured. For detailed operations, see 5.2.2 Preparations for LTE Terminal Analysis.
Process
Figure 5-7 shows the analysis process. Figure 5-7 Analysis process
Issue 01 (2013-07-15)
1731
Table 5-4 Description of the LTE terminal analysis process N o. (1) Procedure Check whether analysis data is integrated? Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to LTE FDD Terminal Analysis Data or LTE TDD Terminal Analysis Data. 2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
(2)
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the LTE FDD or 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. 4. In the Basic Subscription Settings dialog box, set the switch of Terminal Analysis Data to ON. 5. Click Confirm. Verify that the data switch is successfully turned on by viewing information displayed in the Log Info area.
Issue 01 (2013-07-15)
1732
N o.
Description Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the LTE FDD or LTE TDD tab. 2. Select the NEs to be configured from the left navigation tree. 3. On the Terminal Analysis tab page, click ON. 4. In the Terminal Analysis Parameter Setting dialog box, set the threshold value for exceptions. For details about parameters, see Subscription Task Parameters. 5. Click Confirm. Verify that data subscription is successfully turned on by viewing information displayed in the Log Info area.
Reference
Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Set Data Type to LTE FDD Terminal Analysis Data or LTE TDD Terminal Analysis Data. 2. Set the query time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
Issue 01 (2013-07-15)
1733
N o. (3)
Description Navigation path: In the navigation tree of the Analysis Task Management window, choose Theme Function > Terminal Analysis > LTE Terminal Analysis. Procedure: : 1. Double-click LTE Terminal Analysis. 2. Set the task name and task remarks. Click Next. 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 Group or Cell Group. 4. Click Next. 5. Select an analysis time period. The Nastar then obtains analysis data based on the selected time period. 6. Click Finish. For details about the parameter settings, see Analysis Task Parameters.
(4)
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure:
l For details about the 1. Double-click the result record of the task. 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 5.2.4 Interface Description: LTE Terminal Analysis.
Issue 01 (2013-07-15)
1734
N o. (5)
Description Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. 2. Specify the export path and export format. 3. Click Save.
Reference l For details, see 2.10 Exporting Analysis Reports. l For details about the description of the window for showing analysis results, see 5.2.4 Interface Description: LTE Terminal Analysis.
Issue 01 (2013-07-15)
1735
Parameter Overlong InterSystem Outgoing Handover Delay Threshold(s) Overlong InterSystem Incoming Handover Delay Threshold(s) Overlong IntraSystem Incoming Handover Delay Threshold(s)
Description Threshold indicating that the duration for a terminal to perform inter-RAT handovers from LTE to GSM, UMTS, CDMA2000, or TDS CDMA is exceedingly long. Value range: [0,100000]
Threshold indicating that the duration for a terminal to perform inter-RAT handovers from GSM, UMTS, CDMA2000, or TDS CDMA to LTE is exceedingly long. Value range: [0,100000]
Threshold indicating that the duration at the X2 or S1 interface for a terminal to perform handovers within the LTE system is exceedingly long. Value range: [0,100000]
Parameter information
Issue 01 (2013-07-15)
1736
Parameter GBR
Description 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.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Issue 01 (2013-07-15)
1737
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.
Main Window
Figure 5-8 shows the terminal analysis results. Figure 5-8 Terminal analysis window
No. 1
Description Analysis results are displayed in the form of tab page. l The Market Share tab page is used to analyze the occupation of terminals on the live network by different dimensions. For detailed operations, see Interface Description: Terminal Market Share Analysis. l The Capability tab page is used to analyze the proportion of different terminal capabilities supported by the terminals on the live network. For detailed operations, see Interface Description: Terminal Ability Analysis. l The Analyze Terminal Performance tab page is used to analyze the 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.
Issue 01 (2013-07-15)
1738
No. 1
Description l 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 Aggregation Type 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. The number and occupation of TopN terminals on the live network from a certain analysis dimension are displayed in a table. You can save the table by right-clicking the table and choosing Save As from the shortcut menu.
Statistics table
Issue 01 (2013-07-15)
1739
No. 1
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. Selects all objects to be analyzed. Supports the selection of analyzed objects from three different dimensions: by the whole network, by a single eNodeB, or by a single cell. 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. The proportion of the terminals that support a certain terminal 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.
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. You can save the table by right-clicking the table and choosing Save As from the shortcut menu. For details about parameters, see 5.2.5 Parameters for Viewing LTE Terminal Analysis Results.
Issue 01 (2013-07-15)
1740
No. 1
Description 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 to 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 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, and the system saves the displayed TopN results and all the other results that are not displayed to your local computer.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1741
No. 3
Name Aggregation table of the celllevel and bearer-level terminal performance indicators
Description 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. You can save the table by right-clicking the table and choosing Save As from the shortcut menu. For details about parameters, see 5.2.5 Parameters for Viewing LTE Terminal Analysis Results.
IMEITAC
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. Indicates the terminal vendor, for example, Nokia and Apple.
Vendor
[1, 25 6] N/ A
N/ A
Type
N/ A
Indicates the terminal type, for example, common terminal, intelligent terminal, and data card.
Issue 01 (2013-07-15)
1742
Ra ng e [0, 25 6] N/ A
U nit N/ A
Description
Supported NE Version eNodeB V100R005C 00 or later version eNodeB V100R005C 00 or later version
Techno logy
N/ A
Indicates the RAT that the terminal supports, for example, GSM and WCDMA.
Number and percentage of the terminals that support specific radio access systems, including E-UTRAN, UTRAN, GERAN CS, GERAN PS, and CDMA2000-1XRTT, within a cell or eNodeB or over the E-UTRAN. Number and percentage of the terminals that support GERAN/UTRAN dual-mode, UTRAN/E-UTRAN dual-mode, GERAN/E-UTRAN dual-mode, and GERAN/UTRAN/E-UTRAN multi-mode, within a cell or eNodeB or over the E-UTRAN. Number and percentage of the terminals that support the R8/R9/R10 protocol, within a cell or eNodeB or over the E-UTRAN. Number and percentage of the terminals that support handovers to the GERAN PS domain, within a cell or eNodeB or over the E-UTRAN.
Multipl e modes
N/ A
N/ A
Protoc ol version Hando ver to the GERA N PS domain Interfrequen cy measur ement
N/ A
N/ A
N/ A
N/ A
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.
Issue 01 (2013-07-15)
1743
Param eter InterRAT measur ement Interfrequen cy handov er InterRAT handov er Intrafrequen cy/ interfrequen cy/ interRAT ANR measur ement LTE FDD/ TDD handov er Wi-Fi
Ra ng e N/ A
U nit N/ A
Description
Supported NE Version eNodeB V100R005C 00 or later version eNodeB V100R005C 00 or later version eNodeB V100R005C 00 or later version eNodeB V100R005C 00 or later version
Number and percentage of the terminals that support inter-RAT measurements on UTRAN, GERAN, CDMA2000-HRPD, and CDMA2000-1XRTT, within a cell or eNodeB or over the E-UTRAN. Number and percentage of the terminals that support inter-frequency handovers, within a cell or eNodeB or over the E-UTRAN.
N/ A
N/ A
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. Number and percentage of the terminals that support intra- and inter- frequency ANR measurements and inter-RAT ANR measurements, within a cell or eNodeB or over the E-UTRAN.
N/ A
N/ A
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.
N/ A
N/ A
Number and percentage of the terminals that support Wi-Fi, within a cell or eNodeB or over the E-UTRAN.
Issue 01 (2013-07-15)
1744
Number of RRC Connection Setup Request messages that a terminal sends due to mo-Signaling.
[0, + )
Nu mb er
Number of RRC Connection Setup Request messages that a terminal sends due to emergency, highPriorityAccess, mt-Access, or mo-Data.
[0, + ) [0, + )
Nu mb er Nu mb er
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). 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. E-RAB setup success rate = Number of successful ERAB setups/Number of E-RAB Setup Request messages
eNodeB V100R005C 00 or later version eNodeB V100R005C 00 or later version eNodeB V100R005C 00 or later version
[0, 10 0]
Number of abnormal E-RAB releases due to E-RAB exceptions, among successful E-RAB connection setups
Issue 01 (2013-07-15)
1745
Ra ng e [0, 10 0]
U nit %
Description
Proportion of abnormal E-RAB releases due to E-RAB exceptions against successful E-RAB connection setups.
Number of outgoing intra-RAT intra- or interfrequency handover request attempts on the LTE network when the eNodeB receives the RRC Connection Setup message or when the UE is handed over to the eNodeB.
[0, + )
Nu mb er
Number of times the preparation for an outgoing intraor inter-frequency handover on an LTE network fails when the eNodeB receives the RRC Connection Setup message or when the UE is handed over to the eNodeB, or number of times the preparation for an outgoing intra- or inter-frequency 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. Outgoing intra-RAT handover success rate during the same call process = (Number of outgoing intra-RAT handovers Number of failed outgoing intra-RAT handovers)/Number of outgoing intra-RAT handover requests
[0, 10 0]
Issue 01 (2013-07-15)
1746
Param eter InterRAT Outgoi ng Hando ver Reques t Times InterRAT Outgoi ng Hando ver Failure s
Ra ng e [0, + )
U nit Nu mb er
Description
Number of preparation times for outgoing handovers from LTE to GSM, UMTS, CDMA2000, or TDSCDMA when the eNodeB receives the RRC Connection Setup message or when the UE is handed over to the eNodeB.
[0, + )
Nu mb er
Number of times the preparation for outgoing handovers from LTE to GSM, UMTS, CDMA2000, or TD-SCDMA fails when the eNodeB receives the RRC Connection Setup message or when the UE is handed over to the eNodeB; or number of times the preparation for outgoing handovers 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. Inter-RAT incoming handover success rate from LTE to GSM, UMTS, CDMA2000, or TD-SCDMA during the same call process = (Number of inter-RAT incoming handover requests Number of failed interRAT incoming handover requests)/Number of interRAT incoming handover requests
InterRAT Outgoi ng Hando ver Succes s Rate InterRAT Incomi ng Hando ver Reques t Times InterRAT Incomi ng Hando ver Failure s
[0, 10 0]
[0, + )
Nu mb er
Number of preparation times for incoming handovers from GSM, UMTS, or TD-SCDMA to LTE.
[0, + )
Nu mb er
Number of times the preparation for ingoing handovers from GSM, UMTS, or TD-SCDMA to LTE fails or number of times the ingoing handover preparation succeeds but the handover fails.
Issue 01 (2013-07-15)
1747
Param eter InterRAT Incomi ng Hando ver Succes s Rate LTE to TDSCDM A Hando ver Reques t Times LTE to TDSCDM A Hando ver Failure s LTE to TDSCDM A Hando ver Succes s Rate
Ra ng e [0, 10 0]
U nit %
Description
Inter-RAT incoming handover success rate from GSM, UMTS, or TD-SCDMA to LTE during the same call process = (Number of inter-RAT incoming handover requests Number of failed inter-RAT incoming handover requests)/Number of inter-RAT incoming handover requests
[0, + )
Nu mb er
Number of preparation times for outgoing handovers from LTE to TD-SCDMA when the eNodeB receives the RRC Connection Setup message or when the UE is handed over to the eNodeB.
[0, + )
Nu mb er
Number of times the preparation for outgoing handovers from LTE to TD-SCDMA fails when the eNodeB receives the RRC Connection Setup message or when the RRC is handed over to the eNodeB; or number of times the preparation succeeds but the handover fails when the eNodeB receives the RRC Connection Setup message or when the RRC is handed over to the eNodeB. Handover success rate from LTE to TD-SCDMA during the same call process = (Number of handover requests from LTE to TD-SCDMA Number of failed handover requests from LTE to TD-SCDMA)/Number of handover requests from LTE to TD-SCDMA
[0, 10 0]
Issue 01 (2013-07-15)
1748
Number of RRC Connection Setup Request messages (non-service) with a delay according to the predefined delay for RRC connection setup.
[0, + )
Se co nd
You can obtain the average delay for RRC connection setup (non-service) by using the following formula: Average delay for RRC connection setup (non-service) = Sum of all RRC connection setup delays (nonservice)/Number of reports with RRC connection setup delay (non-service). In the preceding format, 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. 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 format, 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 setup delay (nonservice). Number of RRC Connection Setup Request messages (service) with a delay according to the predefined delay for RRC connection setup.
[0, 10 0]
[0, + )
Nu mb er
Issue 01 (2013-07-15)
1749
Ra ng e [0, + )
U nit Se co nd
Description
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 format, 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 emergency, highPriorityAccess, mt-Access, or mo-Data. 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 format, 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). Number of Initial Context Setup Request or E-RAB Setup Request messages with a delay according to the predefined delay for E-RAB setup.
[0, 10 0]
[0, + )
Nu mb er
[0, + )
Se co nd
You can obtain the average delay for E-RAB 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 format, the E-RAB 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 E-RAB 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.
Issue 01 (2013-07-15)
1750
Ra ng e [0, 10 0]
U nit %
Description
You can obtain the proportion of exceedingly long ERAB 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 E-RAB setup delay. In the preceding format, the number of exceedingly long ERAB setup delays is the number of times that the ERAB setup delay exceeds the threshold for E-RAB setup delay. 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.
InterRAT Outgoi ng Hando ver Delay Report s Averag e InterRAT Outgoi ng Hando ver Delay
[0, + )
Nu mb er
[0, + )
Se co nd
You can obtain the average delay for outgoing interRAT handover by using the following formula: Average delay for outgoing inter-RAT handover = Sum of all outgoing inter-RAT handover delays/ Number of reports with outgoing inter-RAT handover delay. In the preceding format, the outgoing inter-RAT handover 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. 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 format, the number of exceedingly long outgoing interRAT handover delays is the number of times that the sum of all outgoing inter-RAT delays is above the upper threshold for outgoing inter-RAT handover delay.
[0, 10 0]
Issue 01 (2013-07-15)
1751
Param eter IntraRAT Outgoi ng Hando ver Delay Report s Averag e IntraRAT Outgoi ng Hando ver Delay Ratio of Overlo ng IntraRAT Outgoi ng Hando ver Delays InterRAT Incomi ng Hando ver Delay Report s
Ra ng e [0, + )
U nit Nu mb er
Description
Number of the reports indicating that an outgoing interRAT handover succeeds after the request for intra- or inter-frequency handover within an LTE system is accepted.
[0, + )
Se co nd
You can obtain the average delay for outgoing intraRAT handover by using the following formula: Average delay for outgoing intra-RAT handover = Sum of all outgoing intra-RAT handover delays/ Number of reports with outgoing intra-RAT handover delay. In the preceding format, the outgoing intra-RAT handover delay spans from the time when the request for an intra- or inter-frequency handover within an LTE system is sent to the time when the handover succeeds. 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 format, the number of exceedingly long outgoing intraRAT handover delays is the number of times that the sum of all outgoing intra-RAT delays is above the threshold for outgoing intra-RAT handover delay. 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.
[0, 10 0]
[0, + )
Nu mb er
Issue 01 (2013-07-15)
1752
Param eter Averag e InterRAT Incomi ng Hando ver Delay Ratio of Overlo ng InterRAT Incomi ng Hando ver Delays
Ra ng e [0, + )
U nit Se co nd
Description
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 incoming inter-RAT handover delay. In the preceding format, the incoming interRAT handover 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. 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 format, the number of exceedingly long incoming inter-RAT handover delays is the number of times that the sum of all incoming inter-RAT delays is above the threshold for incoming inter-RAT handover delay.
[0, 10 0]
Number of E-RAB IDs upon E-RAB failures after a terminal sends the E-RAB SETUP REQUEST or INITIAL CONTEXT SETUP REQUEST message and receives the E-RAB SETUP response or INITIAL CONTEXT SETUP response message from the related eNodeB. Average QCI value. GBR (QCIN) indicates the GBR service with highlevel 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.
GB R [1, 4] No n GB R [5, 9]
N/ A
Issue 01 (2013-07-15)
1753
Ra ng e [0, 10 0]
U nit %
Description
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.
N/ A
N/ A
Cell Name
N/ A
N/ A
problematic cells. In this way, the engineers can better analyze the causes of cell exceptions and then locate these cell exceptions.
Function Description
Generally, engineers prefer a whole-to-partial method to optimize the network and analyze the network performance. Under this method, the engineers locate and analyze network problems by monitoring certain KPIs, 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 in the problematic cells. This helps engineers collect more information about the bottom subscribers and terminal models that have 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 so that the engineers can 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 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 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 cells, selected types of exception in a cell, selected causes of certain types of exception, and 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.
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 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. Figure 5-12 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 5-5.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1755
Table 5-5 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue a subscrip tion comma nd Sou rce Nast ar Serv er Dest inati on eSA U Purpose
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.
eSA U
M20 00
Issue 01 (2013-07-15)
1756
Proced ure Forward the subscrip tion comma nd Upload raw data (eNode B CHR) Upload raw data (MME CHR)
Purpose
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNo deB
MM E
To upload the raw data (MME CHR) to the LTE SAU directly.
NOTE The generation and transmission of the MME CHR data is not triggered by the Nastar subscription command. The MME CHR data will be uploaded to the LTE SAU through Huawei internal protocols in real time after the CHR data reporting values are configured and the CHR data transmission switch is enabled.
Issue an applicat ion data subscrip tion comma nd Deliver a preproc essing task (direct) Collect data (eNode B CHR) (direct)
Nast ar Serv er
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eSA U
LTE SAU
To deliver a data-preprocessing task to the LTE SAU, requesting the LTE SAU to start the data-preprocessing task.
The collected data (eNodeB CHR) is placed in the specified path of the LTE SAU.
Issue 01 (2013-07-15)
1757
Purpose
To upload preprocessed data (eNodeB CHR and MME CHR) to the eSAU.
Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
Nast ar Serv er
To deliver 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.
eSA U
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Item Item Number of analysis tasks to be created Network scale to be analyzed in a task Time range of analysis data
To ensure the validity of configuration data, you are advised to perform LTE cell performance analyses on a per day basis.
NE Group Information An NE group consists of NEs that are centrally managed. During Nastar theme analysis, the Nastar obtains NE information from NE groups. Before creating an analysis task, ensure that NE groups are configured. For detailed operations, see 2.4.5 Managing NE Groups.
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.
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. 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.
Prerequisites
LTE configuration data and LTE engineering parameters have been imported into the Nastar database. For detailed operations, see 5.3.2 Preparations for LTE Cell Performance Analysis.
Process
Figure 5-13 shows the analysis process.
Issue 01 (2013-07-15)
1760
Issue 01 (2013-07-15)
1761
Table 5-6 Description of the LTE cell performance analysis process No. (1) Procedure Check the integrity of analysis data Description Navigation path: Choose Maintenance > Data Maintenance Management. Steps: 1. Set Data Type to LTE Cell Performance Analysis Data. 2. Specify the time period. 3. Select query 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, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
1762
No. (2)
Description
NOTE The source data subscription function has high security requirements. You are advised to contact the administrator to turn on the data source switch.
Navigation path: Choose 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. 4. In the displayed Basic Subscription 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) Navigation path: Choose 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 01 (2013-07-15)
1763
No.
Description Navigation path: Choose Maintenance > Data Maintenance Management. Steps: 1. Set Data Type to LTE Cell Performance Analysis Data. 2. Specify the time period. 3. Select query 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 the analysis data does not exist, contact Huawei technical support.
(3)
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 Performance Analysis. 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. 4. Specify the time period. After the task is executed, the Nastar obtains the analysis results for the specified time period. 5. Click Finish.
l For detailed operations, see 2.7 Creating an Analysis Task l For detailed description of the parameters, see Analysis Task Parameters.
Issue 01 (2013-07-15)
1764
No. (4)
Description Navigation path: In the upper right area of the Analysis Task Management window, select a cell performance analysis task in the Finish state. In the lower right Task Result area, select a result record of the task. Steps: 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.
Reference l For detailed operations, see 2.8 Querying Analysis Results l For detailed description of the window for showing analysis results, see 5.3.4 Interface Description: LTE Cell Performanc e Analysis.
Navigation path: In the window for showing analysis results, click the icon, or right-click an NE in 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 rightclick an NE in the navigation tree and choose In-depth analysis from the shortcut menu. 2. View the analysis results in the displayed Compliant Analysis window.
(5)
Navigation path: Click the export icon on the toolbar in the upper left area of the LTE cell performance analysis window. Steps: 1. Click the export icon on the toolbar. 2. Set the format and save path for exporting file and set the counters and scope for exporting data. 3. Click Save.
l For details, see 2.10 Exporting Analysis Reports. l For details on the description of the window for showing analysis results, see 5.3.4 Interface Description: LTE Cell Performanc e Analysis.
Issue 01 (2013-07-15)
1765
Parameter Date
Description 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 and the end time must precede the current system 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. The value of this parameter must not precede the end time of Date.
Navigation Path
l Use either of the following methods to open the interface that displays the results of LTE cell performance analysis (aggregated): Select a finished LTE cell performance analysis task and double-click a result record in the Task Result area. Select a finished LTE cell performance analysis task, right-click a result record of the task in the Task Result area, and choose Further Analysis from the shortcut menu. l Open the interface that displays the results of LTE cell performance analysis (in-depth): , or right-click an NE and choose On the aggregated analysis result interface, click Further Analysis from the shortcut menu, turn into the in-depth analysis interface.
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 users, terminals, or cells. Figure 5-14 shows the analysis result interface.
Issue 01 (2013-07-15)
1767
No. 1
Description l : 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.
NE navigation tree
l Upper part: Type a cell name in the Search area to quickly locate a cell. 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 reports related to the exception causes. In the navigation tree, you can right-click a cell and choose Further Analysis from the shortcut menu. The in-depth analysis result interface is displayed, showing all the abnormal call records under this cell.
Issue 01 (2013-07-15)
1768
No. 3
Description 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. l Select an exception type and click the icon to open the indepth analysis interface where you can view all abnormal call records under this exception type. l You can resort and export this table by performing the following operations: Click the column header to resort this table. Right-click on the table and choose Save As from the shortcut menu to export this table.
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. l The first row displays the total number of reports under all exception causes, which is also the number of reports under the selected exception type. Starting from the second row, each row displays the number and ratio of reports under each exception cause. l Select an exception cause and click the icon to open the in-depth analysis interface where you can view all abnormal call records under this exception cause.
Displays the number of reports related to BottomN Users, BottomN Terminal Models, or BottomN Cells under an exception cause for the selected eNodeB or cell. l After you select an eNodeB or a group in Area 2, this table displays the number and ratio of reports caused by BottomN Users, BottomN Terminal Models, and BottomN Cells. l After you select a cell in Area 2, this table displays the number and ratio of reports caused by BottomN Users and Terminal Models. 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.
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: LTE Complaint Analysis Support.
Issue 01 (2013-07-15)
1769
Servi ce Type
N/A
N/A
Service type of a cell exception. Type of a service. Following are possible service types: l Network service l GBR service l Non-GBR service
l When the service type is "Network service",the enumeration values are as follows: RRC Setup Failure(NonService) RRC Setup Failure(Service) RRC Setup Failure(Service) Intra-RAT Outgoing HO Failure Inter-RAT Incoming HO Failure Delay Problem l When the service type is "GBR service" or " Non-GBR service", the enumeration values are as follows: E-RAB Setup Failure E-RAB Abnormal Release Delay Problem
N/A
Analysis of exceptions by two dimensions: the network exception itself and the subscriber's subjective perception. For description of the exception types, see Description of NetworkLevel Exception Types.
Issue 01 (2013-07-15)
1770
Para mete r
Range
Unit
Description
Supp orted NE Versi on LTE 3900 V100 R005 C00 or later versio n LTE 3900 V100 R005 C00 or later versio n
[0,+)
Numb er
Ratio (%)
[0.00,100.00]
Proportion of abnormal call records under a specific exception type in all the abnormal call records.
N/A
N/A
Failure during the process from when a terminal sends an RRC Connection Request message until the non-service RRC connection setup is complete.
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.
Issue 01 (2013-07-15)
1771
Para mete r InterRAT Outg oing HO Failu re InterRAT Inco ming HO Failu re IntraRAT Outg oing HO Failu re IntraRAT Inco ming HO Failu re
Range
Unit
Description
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1772
Range
Unit
Description
N/A
N/A
Any of the following delay problems that might occur when a terminal attempts to access the network: Time delay or non operation of the RRC connect up delay Time delay or operation of the RRC connect up delay Time delay or overlong inter-RAT outgoing handover delay Time delay or overlong intra-RAT outgoing handover delay Time delay or overlong inter-RAT incoming handover delay Time delay or overlong intra-RAT incoming handover delay You can set the exception thresholds by using the source data subscription function.
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. 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. 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.
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1773
N/A
N/A
[0,+]
Number
[0.00,100. 00]
Proportion of a cause against the number of exceptions under the same exception type.
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
1774
Para mete r Overl ong InterRAT Outg oing Hand over Delay Overl ong IntraRAT Outg oing Hand over Delay Overl ong InterRAT Inco ming Hand over Delay Overl ong ERAB Setup Delay Reso urce Alloc ation Failur e No UE Resp ondin g
Range
Unit
Description
N/A
N/A
N/A
N/A
N/A
N/A
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.
LTE 3900 V100R00 5C00 or later version LTE 3900 V100R00 5C00 or later version LTE 3900 V100R00 5C00 or later version
N/A
N/A
N/A
N/A
Number of non-service RRC setup failures because the UE does not make any response.
Issue 01 (2013-07-15)
1775
Para mete r Reso urce Alloc ation Failur e No UE Resp ondin g IntraRAT Outg oing HO Prepa ration Failur e IntraRAT Outg oing HO Exec ution Failur e InterRAT Outg oing HO Prepa ration Failur e
Range
Unit
Description
Support ed NE Version LTE 3900 V100R00 5C00 or later version LTE 3900 V100R00 5C00 or later version LTE 3900 V100R00 5C00 or later version
N/A
N/A
N/A
N/A
Number of service RRC setup failures because the UE does not make any response.
N/A
N/A
Number of intra-RAT outgoing handover failures because of the failure in the handover preparation phase.
N/A
N/A
Number of intra-RAT outgoing handover failures because of the failure in the handover execution phase.
N/A
N/A
Number of inter-RAT outgoing handover failures because of the failure in the handover preparation phase.
Issue 01 (2013-07-15)
1776
Para mete r InterRAT Outg oing HO Exec ution Failur e InterRAT Inco ming HO Prepa ration Failur e InterRAT Inco ming HO Exec ution Failur e ERAB Abno rmal Relea se Trigg ered by MME
Range
Unit
Description
N/A
N/A
Number of inter-RAT outgoing handover failures because of the failure in the handover execution phase.
N/A
N/A
Number of inter-RAT incoming handover failures because of the failure in the handover preparation phase.
N/A
N/A
Number of inter-RAT incoming handover failures because of the failure in the handover execution phase.
N/A
N/A
E-RAB abnormal releases triggered by MME. The cause of the release is UE CONTEXT RELEASE COMMAND, ERAB RELEASE COMMAND, and so on.
Issue 01 (2013-07-15)
1777
Para mete r ERAB Abno rmal Relea se Trigg ered by eNod eB ERAB Abno rmal Relea se Trigg ered by Outg oing HO Exec ution Failur e
Range
Unit
Description
N/A
N/A
E-RAB abnormal releases triggered by eNodeB. The cause of the release is UE CONTEXT RELEASE COMMAND, ERAB RELEASE COMMAND, and so on.
N/A
N/A
E-RAB abnormal releases triggered by outgoing handover execution failure. The causes of the release are the same as those of outgoing handover failures.
N/A
N/A
Unique identifier that the system assigns to each bottom subscriber troubled with exceptions.
Issue 01 (2013-07-15)
1778
Range
Unit
Description
[0,+)
Number
Number of the exceptions that trouble a subscriber under the cause of a certain type of exception.
[0.00,100. 00]
N/A
N/A
The identity of a bottom problematic cell is in the following format: eNodeB ID: Cell ID.
Cell Nam e
N/A
N/A
[0,+]
Number
Number of the exceptions that occur in a cell under the cause of a certain type of exception.
[0.00,100. 00]
Issue 01 (2013-07-15)
1779
00000000 -9999999 9
N/A
Term inal Mode l Exce ption Occu rrenc e Time s Ratio (%)
N/A
N/A
Terminal model that is obtained by using the terminal type management function based on IMEI-TAC.
[0,+]
Number
Number of the exceptions that trouble a certain type of terminal under the cause of a certain type of exception.
[0.00,100. 00]
Function Description
Network geographic observation displays the distribution of network coverage, traffic, and exceptions based on data collected from the live network. It replaces traditional drive tests (DTs) and addresses the problem that DTs fail to cover all areas, thereby providing telecom operators with cost-effective network evaluation and problem identification means. 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. 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. l 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, and average number of RRC_connected subscribers. Function: It geographically displays the resource throughput and average RRC user connections in each area on the network, helping telecom operators know the air interface resource occupation situation and identify problematic areas where exceptions occur frequently. l Network event geographic analysis supports the geographic rendering for the following indicators: radio link failures (RLF), intra-frequency HO failures, inter-frequency HO failures, and inter-RAT HO failures. Functions: Geographic display of RLF events helps engineers learn the distribution of call drops or 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 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.
Application Scenarios
l Network optimization: By providing grid-level analysis on network coverage, traffic, and events at this stage, the system helps identify problems such as weak coverage, intra-system interference and improper network structure and then locates problematic cells through associated grid-cell analysis. This helps to greatly reduce DTs. After the addressed problems are solved, the system allows network optimization engineers to evaluate the network quality before and after the optimization.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1781
Issue 01 (2013-07-15)
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 monitoring and maintenance: By geographically displaying network events at this stage, the system helps network optimization engineers identify areas where exceptions such as call drops and handover failures occur and provides guidance for troubleshooting. Traditional network guarantee and routine problem locating use network performance KPIs to identify and analyze cell-level call drops and handover failures. Exceptions occurred in certain coverage areas of a cell might be ignored because users see only the average KPI values and, if telecom operators fail to pay attention to such exceptions, complaints will arise. By geographically displaying exceptions such as call drops and handover failures on the live network, the system helps network optimization engineers quickly identify areas where exceptions occur frequently. Then, in conjunction with functions such as cell performance analysis and the GIS, the engineers can further locate radio frequency (RF) causes so as to improve user experience of the entire network.
Function Principles
The data source of LTE network geographic observation is the eNodeB CHR data on the NE side. Figure 5-15 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 5-7. Figure 5-15 Principles for analysis
Issue 01 (2013-07-15)
1782
Table 5-7 Description of analysis User Operat ion 1. Subscri be to basic data Proced ure Issue a basic data subscrip tion comma nd Issue a subscrip tion comma nd Forward the subscrip tion comma nd Upload raw data (CHR) 2. Subscri be to applicat ion data Issue an applicat ion data subscrip tion comma nd Deliver a preproc essing task (direct) Collect data (CHR) (direct) Sou rce Nast ar Serv er Dest inati on eSA U Purpose
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.
eSA U
M20 00
M20 00
eNod eB
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNo deB
Nast ar Serv er
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eSA U
LTE SAU
To deliver a data-preprocessing task to the LTE SAU, requesting the LTE SAU to start the data-preprocessing task.
LTE SA U
Trac e Serv er
Issue 01 (2013-07-15)
1783
Proced ure
Purpose
The collected data (eNodeB CHR) is placed in the specified path of the LTE SAU.
Upload preproc essed data (direct) 3. Check the integrit y of analysi s data Issue a data query comma nd Return data query results Issue a task executio n comma nd Upload data analysis results Display analysis results
LTE SA U
eSA U
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. To return data integrity check results to the Nastar server and display the results on the Nastar client.
Nast ar Serv er
To deliver 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.
eSA U
To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server. 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.
Issue 01 (2013-07-15)
1784
Item Execution type Number of analysis tasks to be created Network scale to be analyzed in a task Period that can be analyzed (for periodic task) Time range of analysis data
Task Management Capacity One-time task or periodic task l Once tasks <= 50 l Period tasks <= 10 l <= 6,000 cells (400 equivalent NEs) l <= 12,000 cells (800 equivalent NEs) 1 to 7 days
<= 7 days
If you want both functions, all the preceding license and user rights are required.
Issue 01 (2013-07-15)
1786
Function 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.
Operation 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.
An NE group consists of NEs that are centrally managed. During Nastar theme analysis, the Nastar obtains NE information from NE groups. Before data subscription, ensure that NE groups are configured. The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map.
You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
Issue 01 (2013-07-15)
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.
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 5.4.2 Preparations for LTE Network Geographic Observation.
Process
Figure 5-16 shows the analysis process. Figure 5-16 Analysis process
Issue 01 (2013-07-15)
1788
Table 5-9 Description of the network geographic observation process No. (1) Proced ure Check whether analysis data is integrat ed Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Choose Data Type > Network Analysis > *** Network Geographic Observation Data. *** indicates the network type including LTE TDD and LTE FDD. 2. Specify the time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
1789
No. (2)
Description Navigation path: Choose Maintenance > Data Subscription Management 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.
2. Select the NEs to be configured in the navigation tree. 3. Click Set on the Basic Subscription Settings tab page. 4. On the Basic Subscription Settings tab page, set the data source switch of Network Geographic Observation to ON. By default, the data source switch is set to No Modification. Click ... to set the advanced parameters, for details, see Subscription Task Parameters. 5. Click Confirm. Check the information in the Log Info area and ensure that the data source switch is turned on. Subscri be to analysis data (applica tion) Navigation path: Choose Maintenance > Data Subscription Management Procedure: 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 ON on the Network Geographic Observation tab page. 4. Set the threshold parameters in the displayed Network Geographic Observation Parameter Setting dialog box. For detailed operations, see Subscription Task Parameters. 5. Click Finish.
Issue 01 (2013-07-15)
1790
No.
Description Navigation path: Choose Maintenance > Data Maintenance Management Procedure: 1. Choose Data Type > Network Analysis > *** Network Geographic Observation Data. *** indicates the network type including LTE TDD and LTE FDD. 2. Specify the time period. 3. Select the NEs to be queried. 4. Click Query. The query results are displayed in the right pane of the window. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
(3)
Navigation path: Choose Theme Function > Network Analysis > LTE Network Geographic Observation in the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click the LTE Network Geographic Observation. 2. Set the task name and task remarks. Click Next. 3. On the Grid Resolution Settings tab page, select the Grid Resolution for displaying terminal geographic observation results. 4. Select the NE to be analyzed on the Select NE(s) tab. Then, click Next. 5. Choose an analysis time segment. After you set the time range, the Nastar obtains the analysis data generated within this time range. Click Next. 6. Click Finish.
l For details, see 2.7 Creating an Analysis Task. l For details about the parameter s, see Analysis Task Paramete rs.
(4)
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. 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.
l For details, see 2.8 Querying Analysis Results. l For details on the descriptio n of the
Issue 01 (2013-07-15)
1791
No.
Description 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.
Reference window for showing analysis results, see 5.4.4 Interface Descripti on: LTE Network Geograp hic Observat ion. l For details, see 2.10 Exportin g Analysis Reports. l For details on the descriptio n of the window for showing analysis results, see 5.4.4 Interface Descripti on: LTE Network Geograp hic Observat ion.
(5)
Navigation path: Click the icon on the button area in the upper left part of the Geographic Observation window. 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.
Description This parameter is selected by default, indicating that the Nastar obtains and analyzes Real-time data. Users are not authorized to set this parameter.
1792
Real-time data
Parameter para mete r setti ngs of basic subs cript ion Log data
Description If this parameter is not selected, the Nastar does not obtain and analyze Log data. If this parameter is selected, the Nastar obtains and analyzes log data within Duration. l Duration(second) specifies the period for executing a log-data subscription task. The value of this parameter can be 600, 1200, 2400, 3600, 5400, or 7200. l Period(ms): specifies the interval between two logdata subscription tasks. The value of this parameter can be 1, 2, 4, 6, 8, or 12. The unit is *5120 (ms).
NOTE Before subscribing to log data, configure the mapping relationships between TCE IPs and TCE IDs of base stations on the CME. If the CME is not available, configure them on the EMS to ensure that all the mapping relationships of the base stations on a single network are the same.
l UE polling, choose the UEs by polling method, every UE will be polled. l UE capability prioritized, choose the UEs based on the UE capability, the system will give priority to the UE that the ability meets the requirements. UE capability prioritized applies only to the scenarios of coverage geographic analysis and will affect traffic geographic analysis. Defines the thresholds for a weak coverage area. This parameter enables the Nastar to obtain only the data that shows an RSRP smaller than A or an RSRQ smaller than B within the area. Range: l A, [-140,-44] l B, [-19.5,-3.0]
Adv ance d para mete r setti ngs of appli catio n subs cript ion
Defines the thresholds for a coverage hole area. This parameter enables the Nastar to obtain only the data that shows an RSRP smaller than C within the area. Range: C, [-140,-44]
Issue 01 (2013-07-15)
1793
Parameter Nonprima ry pilot area defini tion Absolute value of the downlink RSRP difference between nonprimary pilot area and neighboring cell< D Number of neighboring cells meeting previous conditions >=E, and Nonprimary pilot area RSRP> F Uplin k cover age probl em defini tion 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
Description Defines the thresholds for an area with no primary pilot. This parameter enables the Nastar to obtain only the data that 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 E, [1,5] l F, [-140,-44]
Defines the thresholds for an area with unbalanced uplink coverage. This parameter enables the Nastar to obtain only the data that 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, [-140,-44] l I, [-19.5,3.0]
Issue 01 (2013-07-15)
1794
Parameter Overl apped cover age area defini tion 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.
Description Defines the thresholds for an overlapped coverage area. This parameter enables the Nastar to obtain only the data that 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]
Parameter information
Issue 01 (2013-07-15)
1795
Description 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.
Select eNodeB or Cell Group, and select the NEs to be analyzed in the navigation tree. 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.
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time. 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. 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. The value of this parameter must not precede the end time of Date.
Time information of periodic task Param eter Start time Period Description Date for starting a task. Interval between periodic tasks. Value range: 1 to 7 Days.
Issue 01 (2013-07-15)
Note Start Time of a periodic task = Next time point + Delay by (hours) Time period of a periodic task: [Start Time of a periodic task - 1 x Period, Start Time of a periodic task
1796
Description 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
Note The Next time point is related to Start time and Period. If you set Period to Day, the Next time point is 00 hours:00 minutes:00 seconds of the next day starting from Start time.
NOTE 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 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 14:00:00, Start time is 01/01/2013, Period is Day, and Delay by (hours) is 3, the Nastar immediately executes the task.
Time delayed for executing a task. Value range: 0 to 24. Unit: hour. If you select this parameter, it works the same as All Busy Time under Busy hours. You are not allowed to set this parameter.
Busy hours
If you set 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.
Main Window
Network geographic observation results are displayed in raster graphics, as show in Figure 5-17.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1797
Figure 5-17 Window for showing LTE network geographic observation results
N o. 1
Issue 01 (2013-07-15)
1798
N o. 2
Description 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
l Polygon Areas; enables you to analyze only a selected polygon in the map interface. You can save the cells in a polygon as a cell group. You can analyze multiple KPIs simultaneously based on a 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. 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 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. 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\plugins\com.huawei.galaxy.geography.ui \style\config\style.
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 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. You can not allow custom filter conditions.
Issue 01 (2013-07-15)
1799
N o.
Name
Description 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.
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. l Displays analysis results in multiple windows. If you click , the Nastar divides the current window into multiple small windows with each small window displaying the analysis results of one KPI. The small windows are zoomed in, zoomed out, and moved simultaneously. If you click the icon again, the Nastar displays the original window. 4 Detailed grill information list 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.
5 6
Legend detail By default, the Nastar does not display this area. If you want to view the area legend details about an analysis theme, click the icon in the button area. Information area The interface displays no information when it is opened. If you select a grid, the values of selected KPIs in this gird are displayed. If you select a site, information about the site is displayed. If you select a cell, information about the cell such as engineering parameters and longitude and latitude coordinates is displayed.
Issue 01 (2013-07-15)
1800
No. 1
Description 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. 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.
Navigation tree
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.
RSRQ
[-19.5,-2.5 ]
dB
UL DM RS RxPower
[-140,-44]
dBm
The traffic map is rendered according to the average of uplink RS RX powers of the base station measured based on the uplink demodulation reference signal in the raster view. The traffic map is rendered according to the average of the uplink SINR measured based on the uplink demodulation reference signal in the raster view. The traffic map is rendered according to the average of uplink TX powers of the UE in the raster view. The traffic map is rendered according to the cell with the maximum number of accumulated times in working as the primary serving cell in MRs in the raster view. The system classifies all MR locating results into four 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.
UL DM RS SINR
[-19.5,30]
dB
UE TxPower
[-17,23]
dBm
N/A
Confidenc e Level
Issue 01 (2013-07-15)
1802
[0.00,100. 00]
[0.00,100. 00]
[0.00,100. 00]
[0.00,100. 00]
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.
Issue 01 (2013-07-15)
1803
Range [0, +)
Unit KB
Description The traffic map is rendered according to the uplink traffic recorded in MRs in the raster view. The traffic map is rendered according to the downlink traffic in MRs in the raster view. The traffic map is rendered according to the average uplink throughput in MRs in the raster view. The average uplink throughput refers to the average uplink throughput within a unit period.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0, +)
KB
[0, +)
kbit/s
DL Average Throughp ut
[0, +)
kbit/s
The traffic map is rendered according to the average downlink throughput in MRs in the raster view. The average downlink throughput refers to the average downlink traffic within a unit period.
[0, +)
Num ber/s
The traffic map is rendered according to the average number of RRC access users within a unit period in the raster view. In a unit period, the average number of RRC access users consists of the synchronized users and unsynchronized users.
[0,+)
Num ber
Issue 01 (2013-07-15)
1804
Range [0,+)
Description The traffic map is rendered according to the failure number of inter-frequency handover in the raster view. The traffic map is rendered according to the failure number of inter-system (LTE to UMTS) handover in the raster view.
Supported NE Version LTE 3900 V100R006C0 0 or later version LTE 3900 V100R006C0 0 or later version
[0,+)
Num ber
eNodeB ID
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. Indicates the name of the base station. The value is unique on a PLMN.
eNodeB Name
[1,64]
Chara cter
Cell ID
[0,255]
N/A
Indicates the ID of the EUTRAN cell. This parameter, together with the eNodeB ID, constitutes EUTRAN cell ID. EUTRAN cell ID, together with the PLMN, constitutes the ECGI.
Cell Name
[1,99]
Chara cter
LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version
[0, +)
KB
The total traffic volume occurs in certain time within the selected area.
Issue 01 (2013-07-15)
1805
Range [0, +)
Unit KB
Description The uplink traffic volume occurs in certain time within the selected area.
Supported NE Version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version
[0, +)
KB
The downlink traffic volume occurs in certain time within the selected area.
[0, +)
kbit/s
The uplink throughput occurs in certain time within the selected area. The average uplink throughput refers to the average uplink throughput within a unit period.
DL Throughp ut
[0, +)
kbit/s
The downlink throughput occurs in certain time within the selected area. The average downlink throughput refers to the average downlink traffic within a unit period.
[0, +)
Num ber/s
The number of average RRC connected subscribers that occurs in certain time within the selected area. In a unit period, the average number of RRC access users consists of the synchronized users and unsynchronized users.
Function Scenarios
l During network monitoring, 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.
Function Description
VIP Report Analysis (GSM/UMTS/LTE/PS Core) The Nastar periodically collects statistics on and analyzes various user assurance KPIs of VIP subscribers and VIP groups, and generates different types of service assurance reports. l Generates KPI reports on the network, CS services, and PS services on the RAN side, and collects statistics on and analyzes the success rate and delay of each key procedure on the CN side. This helps you quickly learn the service usage of VIP subscribers or VIP groups. 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1807
Issue 01 (2013-07-15)
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 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 5-10.
Issue 01 (2013-07-15)
1808
Table 5-10 Description of VIP all-signaling analysis Net wor k GS M Number of Supported VIP Subscribers 500 on the entire network. VIP subscribers are managed as Important VIP subscribers by using the VIP group management function. Supported Signaling Range 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. 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). UM TS 100 on the entire network. VIP subscribers are managed as Important VIP subscribers by using the VIP group management function. 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. Required NE Version 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. Function Display Mode 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.
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 all-signaling data, a 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.
Issue 01 (2013-07-15)
1809
Number of Supported VIP Subscribers 500 on the entire network. VIP subscribers are managed as Important VIP subscribers by using the VIP group management function.
Supported Signaling Range Signaling messages on the S1-MME interface (3GPP specifications 36.423), X2 interface (3GPP specifications 36.413), and Uu interface (3GPP specifications 36.331). 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.
Required NE Version LTE3900 V100R008C00 or later; M2000 V200R013C00 or later; HSS9860 V900R008C01 or later. Note: You can analyze the key signaling procedures of common subscribers other than the 500 Important VIP subscribers only in LTE3900 V100R005C00SP C230 or later.
Function Display Mode 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.
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 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1810
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. On the PS Core network, the CHR data includes the SGSN/MME CHR data and the GGSN/SAE-GW CHR data.
Function Principles
Figure 5-19 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 5-11.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1811
Issue 01 (2013-07-15)
1812
Table 5-11 Description of VIP analysis User Oper ation 1. Subscr ibe to basic data Scen e GSM / UMT S netw ork Proce dure Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd Upload raw data PS Core netw ork Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd Sour ce Nast ar Serv er Dest inati on eSA U Purpose
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 a basic data subscription command to the eSAU.
eSA U
M20 00
M20 00
BSC/ RNC
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
SAU
eSA U
To turn on the data source switch on the NE side. After a user enables the basic data subscription function (PS Core VIP analysis) on the Nastar client, the Nastar issues a basic data subscription command to the eSAU.
eSA U
M20 00
M20 00
SGS N/ MM E
To forward the MML command to the NE, requesting the NE to generate raw data.
Issue 01 (2013-07-15)
1813
Scen e
Purpose
Issue a basic data subscri ption comma nd Issue a subscri ption comma nd Forwar d the subscri ption comma nd Upload raw data
eSA U
To turn on the data source switch on the NE side. After a user enables the basic data subscription function (LTE VIP analysis) on the Nastar client, the Nastar issues a basic data subscription command to the eSAU.
eSA U
M20 00
M20 00
eNod eB
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNod eB/ MM E
l To upload 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 transmission switch is enabled.
Issue 01 (2013-07-15)
1814
Proce dure Issue an applica tion data subscri ption comma nd Deliver a dataprepro cessing task (direct) Upload prepro cessed data (direct)
Purpose
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 a data-processing command to the eSAU.
eSA U
SAU
To deliver a data-preprocessing request to the SAU, requesting the SAU to start the datapreprocessing task.
SAU
eSA U
Issue an applica tion data subscri ption comma nd Deliver a dataprepro cessing task (direct) Upload prepro cessed data (direct)
Nast ar Serv er
eSA U
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function (PS Core VIP analysis) on the Nastar client, the Nastar issues a dataprocessing command to the eSAU.
eSA U
PS SAU
To deliver a data-preprocessing request to the PS SAU, requesting the PS SAU to start the datapreprocessing task.
PS SAU
eSA U
Issue 01 (2013-07-15)
1815
Proce dure Issue an applica tion data subscri ption comma nd Deliver a prepro cessing task (direct) Upload prepro cessed data (direct)
Purpose
To deliver a data-preprocessing request to the eSAU. After a user enables the application data subscription function (LTE VIP analysis) on the Nastar client, the Nastar issues a data-processing command to the eSAU.
eSA U
LTE SAU
To deliver a data-preprocessing task to the LTE SAU, requesting the LTE SAU to start the datapreprocessing task.
LTE SAU
eSA U
To upload preprocessed data to the eSAU after obtaining the data from LTE SAU to Trace Server, and preprocessing .
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. To return data integrity check results to the Nastar server and display the results on the Nastar client. To deliver 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. To aggregate the data reported by SAUs, generate data analysis results, and upload the data analysis results to the Nastar server.
Nast ar Serv er
eSA U
Nasta r Serve r
Issue 01 (2013-07-15)
1816
Scen e -
Sour ce -
Purpose
Number of analysis tasks to be created Period that can be analyzed (for periodic task) Time range of analysis data
l Once tasks <= 300, for all RATs. l Period tasks <= 60, for all RATs. 30 minutes, 1 to 24 hours, 1 to 7 days, and 1 week
l <= 7 days (for one-time task) l <= 30 days (for periodic task)
Before running a VIP analysis task, you must check and prepare the following information: l l l Checking the License Information and User Rights Preparing Basic Data Checking the Data Source Environment
Required rights (Security > Security Management > User) l Function operation rights Operation Rights > Operation > Nastar Subject Management > LTE FDD VIP Analysis Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM VIP analysis.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > PS Core VIP Analysis Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM VIP analysis.
GSM VIP analysis UMTS VIP analysis LTE TDD VIP analysis LTE FDD VIP analysis PS Core VIP analysis
l Function operation rights Have both involved licenses of VIP Analysis Operation Rights of combined analysis. l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM VIP analysis.
Issue 01 (2013-07-15)
1819
Table 5-13 Required basic data of VIP analysis Data Type Config uratio n Data (Mand atory) Function The configuration data of the NE controlling the 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 which subscribers have handed over. Operation If the OSS information has been already configured, the Nastar automatically collects and imports the configuration data after the OSS and NE information is configured. You can also manually collect the configuration data before the specified time period starts. After the configuration data is imported, you can choose Maintenance > Data Maintenance Management to check whether the configuration data is available in the Nastar database. For detailed information about collecting, importing, and checking, see 2.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 NOTE of configuration data due to network adjustment. If you only perform the PS Expired configuration data may cause incorrect cell Core VIP analysis, you do information in the analysis result. For detailed not need the configuration operations, see Checking Engineering Parameters data. and Configuration Data. VIP Infor matio n (Mand atory) VIP information includes VIP user and IMSI information. Before subscribing to VIP analysis data, create a VIP group to centrally monitor the service of quality for multiple VIP users in one VIP group. For details, see 2.4.6 Managing VIP Groups or VIP Users (VIP Analysis).
NOTE Generally, you obtain the IMSI and MSISDN of a VIP user and enter them into the Nastar. If telecom operators have high requirements for user information security and the anonymous policy is enabled on the network where the Nastar is deployed, all user information such as IMSI, MSISDN, and IMEI contained in the analysis data will be encrypted. To protect the security-sensitive user information, the Nastar no longer allows you to enter the plaintext IMSI and MSISDN. In this situation, you need to contact telecom operators to obtain the encrypted IMSI. The Nastar does not support the encrypted MSISDN. Telecom operators can visit http://support.huawei.com and choose Software Center > Controlled Tool(Mini-tool Software) > Core Network Product Line > Wireless-OSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt user 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 2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key.
Issue 01 (2013-07-15)
1820
Function 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.
Operation 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 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.
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. 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.
You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
For details, see 2.4.10 Setting a Mailbox and Address List for Sending Analysis Reports (Optional).
Issue 01 (2013-07-15)
1821
For the required NE versions and M2000 versions of the signaling tracing analysis, refer to Table 3-26.
Table 5-14 Description of the data source environment Net wor k GSM Description
l GSM RAN CS analysis : Check that the matching M2000 version is V200R011C00 (or later), and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l GSM RAN PS analysis: Check that the matching M2000 version is V200R012C00 (or later), and the NE version is BSC6900 V900R014C00 (or later), and BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On the User Identity Information Reporting Switch (GSM) in Nastar Commissioning Guide.
UM TS
l Check that the matching M2000 version is V200R011C00SPC220 or later and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(UMTS) > Turning On the User Identity Information Reporting Switch (UMTS) in Nastar Commissioning Guide.
LTE
l Check that the matching M2000 version is M2000 V200R012C00SPC200 or later, the NE version is LTE3900 V100R005C00SPC320 (or later) or LTE3900 V100R008C00SPC020 (or later), and the MME on the CN must be provided by Huawei and the version is USN9810 V900R011C01SPC300 or later.
NOTE 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 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. 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. 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.
Issue 01 (2013-07-15)
1822
Description
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 M2000 versions are consistent with the following information: NE version: USN9810 V900R011C01, USN9810 V900R011C02, USN9810 V900R012C00; UGW9811 V900R009C01, UGW9811 V900R009C02, UGW9811 V900R010C00. M2000 version: M2000 V200R011C01, M2000 V200R012C01, M2000 V200R013C00.
Prerequisites
You have finished the preparation of VIP analysis, such as checking the operation rights, preparing the basic data, and so on. For details, see 3.9.2 Preparations for VIP Analysis.
Procedure
Figure 5-20 shows the analysis process.
Issue 01 (2013-07-15)
1823
Issue 01 (2013-07-15)
1824
Table 5-15 Description of VIP analysis procedures No. Procedure Description Reference for Detailed Operatio ns 2.6 Checking the Integrity of Analysis Data
(1)
Navigation path: Choose Maintenance > Data Maintenance Management 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. l If analysis data exists, perform (3) to create an analysis task. l If analysis data does not exist, contact the administrator to subscribe to the data.
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator with subscription rights to turn on the data source switch.
Issue 01 (2013-07-15)
1825
No.
Procedure
Description
(2)
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the *** tab. *** indicates the network type. 2. In the left navigation tree, select the NEs to be configured. 3. On the Basic Subscription Settings tab page, click Set. 4. In the displayed Basic Subscription Settings dialog box, set 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 3.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.
l If you want to view the all signaling information when viewing deep analysis results, click select the interface about All Signaling. ,
l If you want to view the all signaling information when viewing deep analysis results, , For the GSM/UMTS network, click select the interface about All Signaling.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1826
No.
Procedure
Description
For the LTE network, choose the important level VIP users on the VIP analysis tab page of the application subscription function, and the system will prompt you to start the all signaling trace. 5. Click Confirm. Check that the data switch is successfully turned on by viewing the displayed information in the Log Info area. Subscribe to analysis data (application ) Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click the *** tab. *** indicates the network type. 2. In the left navigation tree, select the NEs to be configured. 3. On the VIP analysis tab page, click ON. 4. Select the VIP user(s) and the NE(s). The level of a VIP user determines the type of data that a VIP user subscribe to. Define the user level through the VIP group management function. 5. Click Confirm. Check that data is successfully subscribed by viewing the displayed information in the Log Info area.
Issue 01 (2013-07-15)
1827
No.
Procedure
Description
Reference for Detailed Operatio ns 2.6 Checking the Integrity of Analysis Data
Navigation path: Choose Maintenance > Data Maintenance Management 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. l If analysis data exists, perform (3) to create an analysis task. l If the analysis data does not exist, contact Huawei technical support.
(3)
Navigation path: Choose Theme Function > User Assurance > VIP Analysis in the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click the VIP Analysis node. 2. Set the task name and task remarks. Click Next. 3. On the Analysis Type tab page, set the net type and the data type(s). 4. On the Select NE(s) tab page, select a NE. 5. On the VIP Group tab page, select the VIP group (s) to be analyzed. 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. 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.
l For details, see 2.7 Creati ng an Analysi s Task. l For details about the paramet ers, see Analysi s Task Param eters.
Issue 01 (2013-07-15)
1828
No.
Procedure
Description
(4)
l For details, see 2.8 Queryi ng Procedure: Analysi 1. Double-click an analysis result of the task. s 2. In the displayed VIP Analysis window, click the Results User Level Results tab to view the VIP summary . analysis results. l For details View Navigation path: icon in the Deep Analysis on the analysis parameter of the VIP summary analysis results. descript results - VIP ion of Procedure: deep the analysis window icon in the Deep Analysis parameter of the 1. Click for VIP summary analysis results. showin NOTE g If the analysis object is VIP group, click icon to enter analysis the analysis result window that the analysis object is VIP results, user. If you want to enter the deep analysis window, you see need click icon again. 3.9.4 Refere 2. In the displayed Deep Analysis Result_*** nce for window, view the in-depth analysis results. VIP Navigation path: In the upper right area of the Analysis View Analysi Task Management window, select an analysis task in analysis s results - VIP the Finish state. In the lower right of the Task Result Interfa area, select a result record of the task. active cells ce. analysis Procedure: View analysis results - VIP summary analysis Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. 1. Double-click an analysis result of the task. 2. In the displayed VIP Analysis window, click the Network Level Results: Active Cell tab to view the analysis results of cells where VIP users are active.
Issue 01 (2013-07-15)
1829
No.
Procedure
Description
View analysis results - VIP active servers analysis (only support the GSM network) View analysis results - VIP trend analysis
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click an analysis result of the task. 2. In the displayed VIP Analysis window, click the Network Level Results: Active Server tab to view the analysis results of servers where VIP users are active. Navigation path: In the upper right area of the Analysis Task Management window, select a periodic task in the Finish state. In the lower right of the Task Result area, select a result record of the task. 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 01 (2013-07-15)
1830
No.
Procedure
Description
Reference for Detailed Operatio ns l For details, see 2.10 Export ing Analysi s Report s. l For details on the descript ion of the window for showin g analysis results, see Interfa ce Descri ption: VIP Analysi s/InDepth Analysi s/ Geogra phic Display .
(5)
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the button area. 2. Specify the export path and export content. 3. Click Save.
Issue 01 (2013-07-15)
1831
Description 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 The name is unique and case-sensitive and cannot be empty. l Task Name must be named in Chinese or English. Otherwise, the function of distributing analysis results by emails is unavailable.
Type of an analysis task to be created. Description of the task. Value range: The name contains a maximum of 200 characters.
Parameter information Parameter Analysis Type Analysis Scene Description 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 Data Type 1 Set the RAT for an NE. The system supports the following RATs: GSM, UMTS, LTE FDD, LTE TDD. Both access methods can be chosen. Set the data type on the RAN side. l RAN CS Data Access: Analyzes the CS service based on the CS-related data on the RAN side. The LTE network does not involve this parameter. l RAN CS Data Access: Analyzes the PS service based on the PS-related data on the RAN side. Both access methods can be chosen.
NOTE If you set the analysis scene to PS Core, you do not need to set the data type, because it only supports the PS data on the PS Core.
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 01 (2013-07-15)
1832
Description Click Select to select an NE. 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.
Indicates the name of a VIP group. Indicates the number of members in the VIP group. Indicates the description of a VIP group. Indicates the last time the VIP group information is updated.
Issue 01 (2013-07-15)
1833
Description Indicates the RAT of a VIP group. Indicates the domain of an NE. Domains include signaling plane-CS, signaling plane-PS, signaling planeintegration. 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. 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 Criterion Threshold Indicates the name of a KPI indicator. The indicators are displayed on the analysis result window. Indicates the relationship between the KPI value and KPI abnormal 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.
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 users 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).
Process Threshold
Network Domain
Indicates the RAT of a VIP group. Indicates the domain of an NE. Domains include signaling plane-CS, signaling plane-PS, signaling planeintegration.
Issue 01 (2013-07-15)
1834
Description 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. 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 process threshold. The threshold is based on the process of obtaining the final values of KPI indicators. Indicates the relationship between the KPI value and KPI abnormal threshold. Indicates the abnormal threshold of a KPI. In the analysis report of the corresponding task, if the KPI value of a subscriber reaches the threshold, this KPI is considered as a problematic KPI or deteriorating KPI. Click the unit and enter the KPI abnormal threshold. This parameter can be empty. That is, no threshold value is provided.
Criterion Threshold
Time information of one-time task Parameter Date Description 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 and the end time must precede the current system time.
Issue 01 (2013-07-15)
1835
Parameter Delay
Description 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. The value of this parameter must not precede the end time of Date.
Time information of periodic task Param eter Start time Period Description Date for starting the task. Interval between periodic tasks. 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. Value range: 0 to 9999 Delay by (hours) Whole day Time delayed for executing a task. Value range: 0 to 24. Unit: hour. If this parameter is set, it works the same as All Busy Time under Busy hours. You are not allowed to set this parameter. Note Start Time of a periodic task = Next time point + Delay by (hours) Time period of a periodic task: [Start Time of a periodic task - 1 x Period, Start Time of a periodic task The Next time point is related to Start time and Period. l If you set Period to Minute, the Next time point is 00 seconds of the next minute starting from the current server time (minutelevel). For example, if the current server time is 01:10, the Next time point is 02:00 starting from Start time. l If you set Period to Hour, the Next time point is 00 minutes:00 seconds of the next hour starting from the current server time (hour-level). For example, if the current server time is 14:01:10, the Next time point is 15:00:00 starting from Start time. l If you set Period to Day, the Next time point is 00 hours:00 minutes:00 seconds of the next day starting from Start time. l If you set Period to Week, the Next time point is 00 hours:00 minutes:00 seconds of the eighth day starting from Start time.
Issue 01 (2013-07-15)
1836
Description 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.
Note
NOTE 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 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 14:00:00, Start time is 01/01/2013, Period is Day, and Delay by (hours) is 3, the Nastar immediately executes the task.
Parameters about sending the analysis report Parameter Sendin g Analysi s Reports Setting Automatically send analysis reports via emails Target email Email subject Description After you select this option, the system delivers the exported VIP analysis result file to the mailboxes of the specified users.
Indicates the recipient's mailbox. Click Select. In the displayed Email dialog box, set user mailboxes. 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.
Issue 01 (2013-07-15)
1837
Parameter Attachment
Description 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 reports by the email directly. l If the actual attachment is larger than the configured threshold, you can obtain the analysis reports by the FTP. Obtain the FTP information. The information will be sent to you by the email. Includes: IP address of the Nastar server (if the hardware is ATAE, the IP address is the one of the master board), FTP user and password, port number, and the analysis report path ( the default path is /export/home/sysm/ nastar/report). Prepare the tool that supports sftp for downloading the analysis reports. The Huawei supports the psftp tool. The path and the operation of the psftp tool is referred to FAQs > FAQs About the SUSE Linux Operating System > How Do I Transfer Data by Using the PSFTP Client? in the Nastar Commissioning Guide.
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.
Open the interface that displays the results of VIP analysis (in-depth): On the User Level Results tab page of VIP analysis result interface, If the table displays the counter overview information by group, click in the front
of each row, or click the counter value underlined in red (for example, ) directly. The tab page for the counter overview information by user is displayed. You can view the counter value for each user in the group. In such a case, click in the front of each row, or click the counter value underlined
in red (for example, ) directly. In-depth analysis of selected counters is started. For details, see 3.10.4 Reference for Complaint Analysis Support Interface. l Open the geographic display interface: On the button area of VIP analysis result interface, click .
Main Window
Figure 5-21 shows the VIP analysis results window. Figure 5-21 VIP analysis interface (example for a GSM network)
Issue 01 (2013-07-15)
1839
No. 1
Parameter Description Button area The buttons provide navigation paths to the following three functions. l : Exports VIP analysis summary reports. 1. Click , a dialog box that provides personal data disclaimer will be displayed, reminding you of the illegality if you possess the personal data. Click OK. 2. On the displayed dialog box, set the result (Exception or ALL), service type, and report type. Click Next. 3. Set the report save path and the folder name, click Save to export the analysis reports. All the exported reports are contained in a folder named VIP Analysis_Name of analysis task_YYYYMMDDHHMMSS by default. VIP analysis reports are named following the format of Number Report type_Report categories 1 + Report categories 2 + Number_Service type.csv. Report categories 1 indicates the analysis object, such as the group and user of the user-level analysis. Report categories 2 indicates the analysis result categories, such as counter overview information table (KPI) and active cell information table (cell) of the user-level analysis. For example, 01 User Level Results_groupKPI00_RAN NET.csv indicates the counter overview information table of the user-level analysis, according the analysis object is group, and the service type is RAN NET. l : Displays the VIP analysis results geographically. For details, see Geographic Display Interface. l : Starts VIP trend analysis. Only periodical tasks support trend analysis. For details, see Interface Description: VIP Trend Analysis.
Issue 01 (2013-07-15)
1840
No. 2
Parameter Description 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.
Issue 01 (2013-07-15)
1841
No. (1)
Parameter
Description
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)
(3)
Counter set Contains a counter set to be analyzed. selection area The Nastar defines a default counter set by analysis scenario. 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
(4)
underlined in red (for example, ) directly. The tab page for the counter overview information by user is displayed. You can view the counter value for each user in the group. l In such a case, click in the front of each row, or click the counter
value underlined in red (for example, ) directly. In-depth analysis of selected counters is started. For details, see 3.10.4 Reference for Complaint Analysis Support Interface. (5) Active cell information table Displays active cells of a selected VIP user object.
Issue 01 (2013-07-15)
1842
No. (6)
Parameter
Description
Active server Displays active servers of a selected VIP user object. It is only information supported by the GSM network. table
No. (1)
Parameter
Description
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 01 (2013-07-15)
1843
No. (2)
Parameter
Description
NOTE The RAN-CS and RAN-PS types cannot be chosen at the same time.
(3)
Counter set Contains a counter set to be analyzed. selection area The Nastar defines a default counter set by analysis scenario. Counter overview information table Active VIP subscriber information table Lists all counter values in different applications for the selected NE object based on the selected counter set.
(4)
(5)
Issue 01 (2013-07-15)
1844
No. (1)
Description 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) Service type selection area Select a service type to be viewed.
NOTE Only the RAN-PS service is supported.
(3)
Contains a counter set to be analyzed. The Nastar defines a default counter set by analysis scenario.
(4)
Counter overview Lists all counter values in different applications for the selected information table analysis object based on the selected counter set. Active VIP Displays VIP subscribers for selected server objects. subscriber information table
(5)
Issue 01 (2013-07-15)
1845
No. (1)
Description Navigation path for basic operations in the Geographic Observation window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
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 01 (2013-07-15)
1846
No. (3)
(4) (5)
This area is empty for VIP analysis. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the icons in area 3.
(6)
Information 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.
VIP trend analysis is supported by the GSM, UMTS, LTE, and PS Core network.
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 when monitoring and optimizing VIP KPIs. Figure 5-26 shows the VIP trend analysis results.
Issue 01 (2013-07-15)
1847
No. 1
Parameter Description 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 01 (2013-07-15)
1848
No. 2
Parameter Description Area for setting filtering criteria Selects a VIP user or VIP group whose trend analysis is to be analyzed. The options 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.
Select the service type whose trend analysis is to be viewed. Only one service type can be selected each time.
Issue 01 (2013-07-15)
1849
No. 5
Parameter Description Trend analysis chart Displays the trend analysis charts of multiple counters for a selected subscriber during a time segment. l Displays user objects and time dimension 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. 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.
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.
The trend analysis modes are as follows: l Real-time monitoring 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.
Issue 01 (2013-07-15)
1850
Common
Parameter Deep Analysis Ran ge N/A Uni t N/A Description 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. 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. LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version Supported NE Version LTE 3900 V100R005C00 or later version
User ID
[1, +)
N/A
Identity of a VIP subscriber. User ID, which is created by the system when creating a VIP User in the VIP Group Management.
User Name
N/A
N/A
Name of a VIP subscriber. Query the name of a VIP subscriber using VIP group management based on the IMSI of the VIP subscriber. 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.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
IMEI-TAC
N/A
Terminal Model
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. Service type for a counter.
N/A
N/A
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0, +)
Num ber
Number of abnormal counters whose values exceed the thresholds that engineers set during analysis task creation. Number of reports generated when a user accesses the network.
[0, +)
Num ber
Issue 01 (2013-07-15)
1851
[0,+)
Number
Range [0,+)
Unit Number
[0,+)
Number
Number of failed intraRAT handover preparations after a UE initiates intra-RAT handover requests. Successful preparation rate of intra-RAT handovers.
[0,100]
[0,+)
Number
[0,+)
Number
[0,100]
1852
Parameter Inter-RAT Outgoing Handover Preparing Attempts Inter-RAT Outgoing Handover Preparing Failures Inter-RAT Outgoing Handover Preparing Success Rate Inter-RAT Outgoing Handover Execution Attempts Inter-RAT Outgoing Handover Execution Failures Inter-RAT Outgoing Handover Execution Success Rate
Range [0,+)
Unit Number
[0,+)
Number
Number of failed interRAT handover preparations after a UE initiates inter-RAT handover requests. Successful preparation rate of inter-RAT handovers.
[0,100]
[0,+)
Number
[0,+)
Number
[0,100]
RAN PS Counters-Accessibility
Parameter E-RAB Setup Requests E-RAB Setup Failures Range [0,+) Unit Number Description Number of E-RAB setup requests initiated by a UE. Number of failed E-RAB setups after a UE initiates E-RAB setup requests. Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,+)
Number
Issue 01 (2013-07-15)
1853
Range [0,100]
Unit %
Description Success rate of E-RAB setups after a UE initiates E-RAB setup requests. ERAB is E-UTRAN radio access bearer for short.
RAN PS Counters-Retainablity
Parameter Abnormal ERAB Releases Abnormal ERAB Release Ratio Range [0,+) Unit Number Description Number of abnormal ERAB releases in the E-RAB releases. Proportion of abnormal ERAB releases in the E-RAB releases. Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,100]
Active Cell
Parameter eNodeB ID Range N/A Unit N/A Description ID of an eNodeB. Supported NE Version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version
eNodeB Name
N/A
N/A
Name of an eNodeB.
Cell ID
N/A
N/A
ID of a cell.
Cell Name
N/A
N/A
Name of a cell.
Issue 01 (2013-07-15)
1854
Range N/A
Unit N/A
Supported NE Version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version LTE 3900 V100R005C 00 or later version
[0,+)
Numbe r
Number of service RRC setup requests of a VIP group or a VIP object in an active cell. Number of non-service RRC setup requests of a VIP group or a VIP object in an active cell. Number of E-RAB setup requests of a VIP group or a VIP object in an active cell. Number of failed E-RAB setups of a VIP group or a VIP object in an active cell. Number of abnormal E-RAB releases of a VIP group or a VIP object in an active cell.
[0,+)
Numbe r
[0,+)
Numbe r
[0,+)
Numbe r
[0,+)
Numbe r
Issue 01 (2013-07-15)
1855
Common
Paramet er Deep Analysis Ran ge N/A Unit Description Supported NE Version BSC6900 V900R013 C00 or later version
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. 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
BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version BSC6900 V900R013 C00 or later version
User ID
N/A
N/A
ID of a VIP subscriber. Query the ID of a VIP subscriber using VIP group management.
Alias
N/A
N/A
Alias of a VIP subscriber. Query the alias of a VIP subscriber using VIP group management.
IMEITAC
N/A
International mobile equipment identity-type allocation code (IMEI-TAC) of the terminal used by a VIP subscriber.
Terminal Model
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. Service type for a following counter.
Service Type
N/A
N/A
[0, +)
Numb er
Number of abnormal counters whose values exceed the predefined thresholds that you set when creating a task. Number of reports generated when a subscriber accesses the network.
[0, +)
Numb er
Issue 01 (2013-07-15)
1856
RAN-CS/NET/Accessibility Evaluation
Para meter Acces s Reque sts (IntraRAT) Acces s Failur es (IntraRAT) Acces s Reque sts (InterRAT) Acces s Failur es (InterRAT) Avera ge TA on Acces s Abnor mal TAs on Acces s Ran ge [0, +) Unit Number Description Number of access requests that a VIP subscriber initiates to access the network from a cell in the current system. Supported NE Version BSC6900 V900R013C00 or later version
[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.
[0, +)
Number
Number of access requests that a VIP subscriber initiates to access the network from a cell in another system.
[0, +)
Number
Number of access failures that a VIP subscriber experiences during the process of accessing the network from a cell in another system.
[0,63 ]
N/A
Average TA value when a VIP subscriber initiates channel setup requests for accessing the network.
[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.
Issue 01 (2013-07-15)
1857
Para meter Ratio of Abnor mal TAs on Acces s Avera ge RAC H Level on Acces s Abnor mal RAC H Levels on Acces s Ratio of Abnor mal RAC H Levels on Acces s
Unit %
Description Proportion of abnormal TA values when a VIP subscriber initiates channel setup requests for accessing the network. Proportion of abnormal TA values = Number of abnormal TA values/Number of all TA values x 100%.
[-110 ,-47]
dBm
Average RACH level when a VIP subscriber initiates channel setup requests for accessing the network.
[0, +)
Number
Number of times that the RACH level is abnormal when a VIP subscriber initiates channel setup requests for accessing the network. Set the exception threshold when you create a task.
[0.00, 100.0 0]
Proportion of abnormal RACH levels when a VIP subscriber initiates channel setup requests for accessing the network. Proportion of abnormal RACH levels = Number of abnormal RACH levels/ Number of all RACH levels x 100%.
Issue 01 (2013-07-15)
1858
RAN-CS/NET/Retainability Evaluation
Para mete r Relea ses (Intra RAT) Abno rmal Relea ses (Intra RAT) Relea ses (Inter RAT) Abno rmal Relea ses (Inter RAT) Rang e [0, +) Unit Description Supported NE Version BSC6900 V900R013C 00 or later version
Numb er
Number of times that a VIP subscriber releases all services in the current system. Number of releases (intra-RAT) = Access requests (intra-RAT) Access failures (intraRAT)
[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.
[0, +)
Numb er
Number of times that a VIP subscriber releases all services in another system. Number of releases (inter-RAT) = Access requests (inter-RAT) Access failures (interRAT)
[0, +)
Numb er
Number of times that a VIP subscriber abnormally releases all services successfully accessed from another system. 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.
RAN-CS/NET/Mobility Evaluation
Paramet er Hard Handover Requests Hard Handover Failures Hard Handover Success Times Range [0,+) Unit Num ber Num ber Num ber Description Number of hard handover requests that a VIP subscriber initiates. Number of hard handover failures that a VIP subscriber experiences. Number of times that a VIP subscriber successfully initiates a hard handover. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
[0,+)
Issue 01 (2013-07-15)
1859
Paramet er InterRAT Outgoing Handover Requests InterRAT Outgoing Handover Failures (Normal Release) InterRAT Outgoing Handover Failures (Abnorm al Release) InterRAT Incoming Handover Requests InterRAT Incoming Handover Failures
Range [0,+)
Description 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. Number of times that an outgoing inter-RAT handover from a GSM network is triggered during a service but the handover fails and the VIP subscriber then is handed back over to the GSM network. Number of times that call drops occur during an outgoing inter-RAT handover from a GSM network during a service.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Number of times that a handover from a non-GSM cell to a GSM cell is triggered during a service.
[0,+)
Num ber
Number of times that a handover from a non-GSM cell to a GSM cell fails during a service.
RAN-CS/Call/Accessibility Evaluation
Param eter Total Call Setup Reques ts Ran ge [0, +) Unit Numb er Description Number of call setup requests that a VIP subscriber initiates to access the network and initiate a call. That is, the number of Channel Request messages from a VIP subscriber after the BSC obtains the IMSI correctly. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1860
Ran ge [0, +)
Unit Numb er
Description Number of call setup failures that a VIP subscriber experiences during the process of accessing the network and initiating a call. The call setup process spans from the Channel Request message to the Altering message.
Abnor mal Release Before Call Compl etion Call Setup Succes s Times
[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. The process before call setup spans from the Channel Request message to the Connect Acknowledge message.
[0, +)
Numb er
Number of successful call setups when a VIP subscriber accesses the network and initiates a call. The call setup process spans from the Channel Request message to the Alerting message.
[0, +)
Numb er
Number of successful call completions (Alerting) when a VIP subscriber accesses the network and initiates a call. The call completion (Alerting) process spans from the Channel Request message to the Altering message.
[0, +)
Numb er
Number of successful call completions (Connect Ack) after a subscriber accesses the network and initiates a call. The call completion process (Connect Ack) spans from the Channel Request message to the Connect Acknowledge message.
Call completion rate (Alerting) when a VIP subscriber accesses the network and initiates a call. Call completion rate (Alerting) = Number of successful call completions (Alerting)/ Number of call setup requests x 100%
Issue 01 (2013-07-15)
1861
Unit %
Description Call completion rate (Connect Ack) when a VIP subscriber accesses the network and initiates a call. Call completion rate (Connect Ack) = Number of successful call completions/ Number of call setup requests x 100%
RAN-CS/Call/Retainability Evaluation
Parame ter Call Setup Success Times Rang e [0, +) Unit Num ber Description Number of successful call setups when a VIP subscriber accesses the network and initiates a call. The call setup process spans from the Channel Request message to the Alerting message. [0, +) Num ber Same as the related counter in RAN/CS/ Call/Accessibility Evaluation. BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1862
Rang e [0, +)
Description Number of times that the call is abnormally released when a VIP subscriber accesses the network and initiates a call. After a successful call setup, any of the following indicates an abnormal call release: 1. The Disconnect message is called an abnormal one. 2. The BSS receives the Clear Command message from the MSC and the abnormal call release is caused by the network or the calling (or called) VIP subscriber. 3. An outgoing inter-BSC handover fails. 4. An intra-BSC handover fails. 5. The BSC releases the channel resources abnormally. 6. The MSC releases the channel resources abnormally.
[0.00, 100.00 ]
Abnormal call release rate when a VIP subscriber accesses the network and initiates a call. Abnormal call release rate = Number of abnormal call releases/Number of successful call completions (Connect Ack) x 100%
Issue 01 (2013-07-15)
1863
Parame ter Average Access Delay (MOC) Overlon g Access Delays (MOC)
Ran ge [0, +)
Unit Second
Description Average access delay upon successful call initiation (mobile-originated call). Average access delay = Sum of access delays/Number of access delays
[0, +)
Numbe r
Number of times that the access delay is overlong upon successful call initiation (mobile-originated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong access delays upon successful call initiation (mobileoriginated call). Proportion of overlong access delays = Number of overlong access delays/ Number of access delays x 100%
[0, +)
Numbe r
Number of times that the access delay is overlong upon successful call initiation (mobile-terminated call). Access delay = Time when the Assignment Complete message is generated Time when the Channel Request message is generated
[0, +)
Second
Average access delay upon successful call initiation (mobile-terminated call). Average access delay = Sum of access delays/Number of access delays
[0, +)
Numbe r
Number of times that the access delay is overlong upon successful call initiation (mobile-terminated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong access delays upon successful call initiation (mobileterminated call). Proportion of overlong access delays = Number of overlong access delays/ Number of access delays x 100%
Issue 01 (2013-07-15)
1864
Parame ter Times of Call Complet ion Delay (Alertin g) (MOC) Average Call Complet ion Delay (Alertin g) (MOC) Overlon g Call Complet ion Delays (Alertin g) (MOC) Ratio of Overlon g Call Complet ion Delays (Alertin g) (MOC) Average Call Complet ion Delay (Connec t Ack) (MOC)
Ran ge [0, +)
Unit Numbe r
Description Number of times that the completion (Alerting) delay is overlong upon successful call initiation (mobileoriginated call). The call completion (Alerting) process spans from the Channel Request message to the Altering message.
[0, +)
Second
Average call completion (Alerting) delay upon successful call initiation (mobile-originated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
[0, +)
Numbe r
Number of times that the call completion (Alerting) delay is overlong upon successful call initiation (mobileoriginated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Alerting) delays upon successful call initiation (mobile-originated call). Proportion of overlong call completion delays = Number of overlong call completion (Alerting) delays/Number of call completion delays x 100%
[0, +)
Second
Average call completion (Connect Ack) delay upon successful call initiation (mobile-originated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
Issue 01 (2013-07-15)
1865
Parame ter Overlon g Call Complet ion Delays (Connec t Ack) (MOC) Ratio of Overlon g Call Complet ion Delays (Connec t Ack) (MOC) Times of Call Complet ion Delay (Alertin g) (MTC) Average Call Complet ion Delay (Alertin g) (MTC) Overlon g Call Complet ion Delays (Alertin g) (MTC)
Ran ge [0, +)
Unit Numbe r
Description Number of times that the call completion (Connect Ack) delay is overlong upon successful call initiation (mobile-originated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Connect Ack) delays upon successful call initiation (mobile-originated call). Proportion of overlong call completion delays = Number of overlong call completion delays/Number of call completion delays x 100%
[0, +)
Numbe r
Number of times that the call completion (Alerting) delay is overlong upon successful call initiation (mobileterminated call). The call completion (Alerting) process spans from the Channel Request message to the Alerting message.
[0, +)
Second
Average call completion (Alerting) delay upon successful call initiation (mobile-terminated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
[0, +)
Numbe r
Number of times that the call completion (Alerting) delay is overlong upon successful call initiation (mobileterminated call). Set the exception threshold when you create a task.
Issue 01 (2013-07-15)
1866
Parame ter Ratio of Overlon g Call Complet ion Delays (Alertin g) (MTC) Average Call Complet ion Delay (Connec t Ack) (MTC) Overlon g Call Complet ion Delays (Connec t Ack) (MTC) Ratio of Overlon g Call Complet ion Delays (Connec t Ack) (MTC) Average Call Duration (MOC)
Unit %
Description Proportion of overlong call completion (Alerting) delays upon successful call initiation (mobile-terminated call). Proportion of overlong call completion delays = Number of overlong call completion delays/Number of call completion delays x 100%
[0, +)
Second
Average call completion (Connect Ack) delay upon successful call initiation (mobile-terminated call). Average call completion delay = Sum of call completion delays/Number of call completion delays
[0, +)
Numbe r
Number of times that the call completion (Connect Ack) delay is overlong upon successful call initiation (mobile-terminated call). Set the exception threshold when you create a task.
[0.00 , 100.0 0]
Proportion of overlong call completion (Connect Ack) delays upon successful call initiation (mobile-terminated call). Proportion of overlong call completion delays = Number of overlong call completion delays/Number of call completion delays x 100%
[0, +)
Second
Average duration of successful calls for the mobile-originated party. 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
Issue 01 (2013-07-15)
1867
Ran ge [0, +)
Unit Numbe r
Description Number of short calls for the mobileoriginated party during a successful call. 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. 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).
[0.00 , 100.0 0]
Average duration of successful calls for the mobile-originated party. 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
[0, +)
Second
Average duration of successful calls for the mobile-terminated party. 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
Issue 01 (2013-07-15)
1868
Ran ge [0, +)
Unit Numbe r
Description Number of short calls for the mobileterminated party during a successful call. 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. 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).
[0.00 , 100.0 0]
Proportion of short calls for the mobileterminated party during a successful call. Proportion of short calls = Number of short calls/Number of calls with valid call durations x 100%
Issue 01 (2013-07-15)
1869
Ran ge [0, +)
Description Number of times that one-way audio occurs in the downlink during calls. 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 Um and A interfaces. Principle for detecting one-way audio occurs in the downlink: The DSP in the DTRU of the BTS performs periodic statistics on the bad frame rate based on downlink TRAU frames. When the bad frame rate reaches the predefined threshold, the BSS determines that primary one-way audio occurs in the downlink and starts the mechanism for confirming the occurrence of primary one-way audio in the downlink. During this process, the BSC sends a message to the TC demanding that the TC send a test TRAU frame to the BTS. If the BTS fails to receive the test TRAU frame from the TC within a specified time period, one-way audio occurs on the downlink voice channel.
Proportion of successful call setups where one-way audio occurs in the downlink in all successful call setups. Proportion of successful call setups where one-way audio occurs in the 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%
Issue 01 (2013-07-15)
1870
Ran ge [0, +)
Description Number of times that one-way audio occurs in the uplink during calls. 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 Um and A interfaces. Principle for detecting one-way audio in the uplink: The DSP in the TC of the BSC performs periodic statistics on the bad frame rate based on uplink TRAU frames. When the bad frame rate reaches the predefined threshold, the BSS determines that primary 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.
Proportion of successful call setups where one-way audio occurs in the uplink in all successful call setups. Proportion of successful call setups where one-way audio occurs in the uplink in all successful call setups = Number of times that one-way audio occurs in the uplink/Number of successful call setups (Connect Ack) x 100%
[0, +)
Num ber
Number of times that no audio occurs in both the uplink and downlink during calls.
Issue 01 (2013-07-15)
1871
Unit %
Description Proportion of successful call setups where one-way audio occurs in both the uplink and downlink in all successful call setups. Proportion of successful call setups where one-way audio occurs in both the uplink and downlink in all successful call setups = Number of successful call setups where one-way audio occurs in both the uplink and downlink/Number of successful call setups (Connect Ack) x 100%
[0, +)
Num ber
Number of times that crosstalk occurs in the downlink during calls. 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.
Proportion of successful call setups where crosstalk occurs in the downlink in all successful call setups. Proportion of successful call setups where crosstalk occurs in the downlink in all successful call setups = Number of successful call setups where crosstalk occurs in the downlink/Number of successful call setups (Connect Ack) x 100%
Issue 01 (2013-07-15)
1872
Ran ge [0, +)
Description Number of times that crosstalk occurs in the uplink during calls. 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 uplink crosstalk: The DSP of the BTS inserts the unique identifier of a call into the free bits of uplink speech TRAU frames. The DSP of the TC decodes the unique call identifier and checks its consistency. If inconsistency is detected within the test period, crosstalk occurs in the uplink.
Proportion of successful call setups where crosstalk occurs in the uplink in all successful call setups. Proportion of successful call setups where crosstalk occurs in the uplink in all successful call setups = Number of successful call setups where crosstalk occurs in the uplink/Number of successful call setups (Connect Ack) x 100%
Average value of downlink HQIs after the call setup is successful. 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 reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008 version: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
Issue 01 (2013-07-15)
1873
Ran ge [0, +)
Description Number of times that the uplink HQI is poor after the call setup is successful. Set the exception threshold when you create a task.
Average value of uplink high quality indicators (HQIs) after the call setup is successful. 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 reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008 version: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
[0, +)
Num ber
Number of times that the uplink HQI is poor after the call setup is successful. Set the exception threshold when you a create task.
[1.00 , 5.00]
N/A
Average value of uplink voice quality BSC6900 indicators (VQIs) during calls. V900R013C00 or later version 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
Issue 01 (2013-07-15)
1874
Parame ter Poor Uplink VQI Times Average Downlin k Level Average Uplink Level Average Downlin k Quality Average Uplink Quality Downlin k Noise Occurre nce Times Downlin k Noise Ratio
Ran ge [0, +)
Description Number of times that the uplink VQI is poor during calls. Set the exception threshold when you create a task.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,7]
N/A
[0, +)
Num ber
Number of times that noise occurs in the downlink during calls, which is detected by the BSC.
Proportion of successful call setups where noise occurs in the downlink in all successful call setups. Proportion of successful call setups where noise occurs in the downlink in all successful call setups = Number of successful call setups where noise occurs in the downlink/Number of successful call setups (Connect Ack) x 100%
[0, +)
Num ber
Number of times that noise occurs in the uplink during calls, which is detected by the BSC.
Issue 01 (2013-07-15)
1875
Unit %
Description Proportion of successful call setups where noise occurs in the uplink in all successful call setups. Proportion of successful call setups where noise occurs in the uplink in all successful call setups = Number of successful call setups where noise occurs in the uplink/Number of successful call setups (Connect Ack) x 100%
RAN-CS/SMS/Accessibility Evaluation
Param eter Call Setup Reques ts (MOC) Call Setup Failure s (MOC) Call Setup Succes s Rate (MOC) Call Setup Reques ts (MTC) Call Setup Failure s (MTC) Range [0,+) Unit Num ber Description Number of setup requests that the mobile-originated party initiates to use the SMS service. Supported NE Version BSC6900 V900R013C00 or later version
[0,+)
Num ber
Number of call setup failures that the mobile-originated party experiences during the process of attempting to use the SMS service. Proportion of successful setup requests that mobile-originated party initiates to use the SMS service.
[0.00,1 00.00]
[0,+)
Num ber
Number of setup requests that the mobile-terminated party initiates to use the SMS service.
[0,+)
Num ber
Number of call setup failures that the mobile-terminated party experiences during the process of attempting to use the SMS service.
Issue 01 (2013-07-15)
1876
Unit %
Description Proportion of successful call setup requests that the mobile-terminated party initiates to use the SMS service.
RAN-PS/PS/General Evaluation
Parame ter Access Failures Total Reports of Access Failure Count > 0 Abnorm al Proporti on of Access Failure Count > 0 Service Interrupt ions Total Reports of Service Interrupt ion Count > 0
Issue 01 (2013-07-15)
Description See Access Failures in RAN-PS/PS/ Accessibility Evaluation. Indicates the number of the measurement reports that the access failure count exceeds 0.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0,10 0]
Indicates the proportion of the total measurement reports that the access failure count exceeds 0.
[0, +) [0, +)
Numb er Numb er
See Service Interruptions in RANPS/PS/Retainability Evaluation. Indicates the number of the measurement reports that the service interruption count exceeds 0.
1877
Parame ter Abnorm al Proporti on of Service Interrupt ion Count > 0 Abnorm al Service Interacti on Delays Total Reports of Abnorm al Service Interacti on Latency Count > 0 Abnorm al Proporti on of Abnorm al Service Interacti on Latency Count > 0 Downloa ds at Low Rate
Ran ge [0,10 0]
Unit %
Description Indicates the proportion of the total measurement reports that the service interruption count exceeds 0.
[0, +)
Numb er
[0, +)
Numb er
Indicates the number of the measurement reports that the abnormal service interaction latency count exceeds 0.
[0,10 0]
Indicates the proportion of the total measurement reports that the abnormal service interaction latency count exceeds 0.
[0, +)
Numb er
Issue 01 (2013-07-15)
1878
Parame ter Abnorm al Proporti on at Low Downloa d Rate Uploads at Low Rate Abnorm al Proporti on at Low Upload Rate
Ran ge [0,10 0]
Unit %
Description Indicates the proportion of the total measurement reports that the download rate is low.
[0, +) [0,10 0]
Numb er %
See Uploads at Low Rate in RANPS/PS/Service Evaluation for Rate. Indicates the proportion of the total measurement reports that the upload rate is low.
RAN-PS/PS/Accessibility Evaluation
Parame ter Access Failures Rang e [0, +) Unit Numb er Description Number of access failures that a VIP subscriber experiences during the process of using a data service. 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. Attach Requests [0, +) Numb er Number of Attach Request messages that a VIP subscriber sends during the whole process of using a data service. BSC6900 V900R013C01 or later version Supported NE Version BSC6900 V900R013C01 or later version
Issue 01 (2013-07-15)
1879
Rang e [0, +)
Unit Numb er
Description Number of Attach Fail messages that a VIP subscriber receives during the process of using a data service. 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. Number of Attach Fail messages = Number of Attach Request messages Number of Attach Accept messages
[0, +) [0, +)
Numb er Numb er
Number of PDP Active Request messages that a VIP subscriber sends during the process of using a data service. Number of PDP Active Fail messages that a VIP subscriber receives during the process of using a data service. 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. Number of Attach Fail messages = Number of PDP Active Request messages Number of PDP Active Accept messages
Authenti cation and Cipherin g Requests Authenti cation and Cipherin g Failures
[0, +)
Numb er
Number of authentication and ciphering requests that a VIP subscriber receives during the process of using a data service.
[0, +)
Numb er
Number of authentication and ciphering failures that a VIP subscriber receives during the process of using a data service.
Issue 01 (2013-07-15)
1880
Rang e [0, +)
Unit Numb er
Description Number of times that no response to service interaction is made. 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. (A = Number of times that the uplink PDU carries data but the downlink PDU does not). The exception thresholds 1 and 2 for the response to service interaction are internal algorithm parameters.
RAN-PS/PS/Retainability Evaluation
Parame ter Service Interrupt ions Rang e [0, +) Unit Numb er Description Number of service interruptions that a VIP subscriber experiences during the process of using a data service. Number of service interruptions = Number of service interruptions due to cell reselection + Number of service interruptions due to routing area update Interrupt ions Due to Cell Reselect ion [0, +) Numb er Number of service interruptions that a VIP subscriber experiences during the process of using a data service due to cell reselection. The parameter is also referred to as the number of cell reselections. [0, +) Secon d Mean time between cell reselections during the process for a VIP subscriber to use a data service. This parameter is also referred to as the average interval between cell reselections. BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version Supported NE Version BSC6900 V900R013C01 or later version
Issue 01 (2013-07-15)
1881
Rang e [0, +)
Unit Numb er
Description Number of times that the cell reselection interval is overlong during the process for a VIP subscriber to use a data service. If the time interval is above the threshold for overlong cell reselection, the cell reselection interval is overlong. Set the threshold when you create a task.
[0, +)
Numb er
Number of service interruptions that a VIP subscriber experiences during the process of using a data service due to routing area update.
Issue 01 (2013-07-15)
1882
Rang e [0, +)
Unit Secon d
Description Average duration of the response to service interaction during the process for a VIP subscriber to use a data service. Average duration of the response to service 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 transmission between the uplink and downlink PDUs.
[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. Set the threshold when you create a task.
Issue 01 (2013-07-15)
1883
Parame ter Abnorm al Proporti on at Low Downlo ad Rate Downlin k TCP Out-ofOrders Average Upload Rate
Rang e [0,10 0]
Unit %
Description Indicates the proportion of the total measurement reports that the download rate is low.
[0, +)
Numb er
Number of times that downlink TCP disorder occurs during the process for a subscriber to use a data service. Average upload rate during the process for a subscriber to use a data service. Upload rate = Number of bytes transmitted by using the uplink PDU/Duration of data transmission by using the uplink PDU
[0.00, +)
Kbps
[0, +)
Numb er
Number of times that the upload rate is low during the process for a subscriber to use a data service. An upload rate is low if it is lower than the threshold for low upload rate. Set the threshold is when you create a task.
[0,10 0]
Indicates the proportion of the total measurement reports that the upload rate is low.
[0.00, +)
Kbps
Issue 01 (2013-07-15)
1884
Rang e [0, +)
Unit MB
Description Total downlink traffic during the process for a subscriber to use a data service. 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 + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Downlink PDU
[0, +)
MB
Total uplink traffic during the process for a subscriber to use a data service. Total uplink traffic = Delay-Sensitive Information/Total Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Downlink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU
Uplink Signalin g Access Times Average Occupie d Downlin k Channel s Average Occupie d Uplink Channel s
[0, +)
Numb er
Number of access requests on the RACH (uplink CCCH) during the process for a subscriber to use a data service. Average number of channels occupied by the downlink during the process for a subscriber to use a data service.
[0, +)
Numb er
[0, +)
Numb er
Average number of channels occupied by the uplink during the process for a subscriber to use a data service.
Issue 01 (2013-07-15)
1885
Common
Para met er BSC Nam e Cell ID Cell Nam e CGI Range Unit Description Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
ID of a VIP subscriber. Query the ID of a VIP subscriber using VIP group management. Name of a VIP alias. Query the alias of a VIP subscriber using VIP group management.
N/A
N/A
Issue 01 (2013-07-15)
1886
Para met er IME ITAC Ter mina l Mod el Serv ice Typ e
Range
Unit
Description
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
International mobile equipment identitytype allocation code (IMEI-TAC) of the terminal used by a VIP subscriber. 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. Service type for a following counter.
N/A
N/A
N/A
N/A
RAN-CS/NET/Accessibility Evaluation
Par am eter R a n g e Uni t Description Supported NE Version
Number of access requests that a VIP group or VIP BSC6900 subscriber initiates during the process of using a call V900R013C00 or or SMS service in an active cell. later version
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.
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.
Issue 01 (2013-07-15)
1887
Par am eter
R a n g e
Uni t
Description
Supported NE Version
[ 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.
RAN-CS/NET/Retainability Evaluation
Par am eter R a n g e [ 0 , + ) [ 0 , + ) U Description n i t N Number of times that a VIP group or VIP subscriber u releases the Call service in an active cell. m b e r N Number of times that a VIP group or VIP subscriber u abnormally releases the Call service in an active cell. m b e r Supported NE Version
Rele ases
Issue 01 (2013-07-15)
1888
RAN-CS/NET/Mobility Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t 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 Supported NE Version
Inte rRA T Inco min g Han dov er Req uest s Inte rRA T Inco min g Han dov er Fail ures
[ 0 , + )
N Number of incoming inter-RAT handover failures that BSC6900 u a VIP group or VIP subscriber experiences in an active V900R013C00 or m cell. later version b e r
RAN-CS/Call/Accessibility Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t N Number of call setup requests that a VIP group or VIP u subscriber initiates in an active cell. m b e r Supported NE Version
Issue 01 (2013-07-15)
1889
Par am eter
R a n g e [ 0 , + ) [ 0 , + )
U Description n i t N Number of call setup failures that a VIP group or VIP u subscriber experiences in an active cell. m b e r 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
Supported NE Version
Call Setu p Fail ures Abn orm al Rele ase Bef ore Call Co mpl etio n
RAN-CS/Call/Retainability Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t N Number of abnormal call releases that a VIP group or u VIP subscriber experiences in an active cell. m b e r Supported NE Version
Issue 01 (2013-07-15)
1890
RAN-CS/SMS/Accessibility Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t N Number of call setup requests that a VIP group or VIP u subscriber initiates in an active cell as the mobilem originated party. b e r Supported NE Version
Call Setu p Req uest s (M OC) Call Setu p Fail ures (M OC) Call Setu p Req uest s (MT C) Call Setu p Fail ures (MT C)
[ 0 , + ) [ 0 , + )
N Number of call setup failures that a VIP group or VIP u subscriber experiences in an active cell as the mobilem originated party. b e r N Number of call setup requests that a VIP group or VIP u subscriber initiates in an active cell as the mobilem terminated party. b e r
[ 0 , + )
N Number of call setup failures that a VIP group or VIP u subscriber experiences in an active cell as the mobilem terminated party. b e r
Issue 01 (2013-07-15)
1891
RAN-PS/PS/Accessibility Evaluation
Par am eter R a n g e [ 0 , + ) [ 0 , + ) [ 0 , + ) U Description n i t N Number of Attach Request messages that a VIP group or u VIP subscriber sends in an active cell. m b e r N Number of PDP Active Request messages that a VIP u group or VIP subscriber sends in an active cell. m b e r 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 Supported NE Version
Atta ch Req uest s PD P Acti ve Req uest s No Serv ice Inte racti on Res pon ses
RAN-PS/PS/Retainability Evaluation
Par am eter R a n g e [ 0 , + ) U Description n i t 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 Supported NE Version
Issue 01 (2013-07-15)
1892
Par am eter
R a n g e [ 0 , + )
U Description n i t 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
Supported NE Version
Ove rlon g Cell Res elec tion Inte rval Tim es Serv ice Inte rrup tion s Due to Rou ting Are a Upd ate
[ 0 , + )
N Number of service interruptions that a VIP group or VIP u subscriber experiences due to routing area update in an m active cell. b e r
Issue 01 (2013-07-15)
1893
Par am eter
R a n g e [ 0 , + )
U Description n i t N Number of times that the delay of the response to service u interaction is overlong when a VIP group or VIP m subscriber is using a service in an active cell. b e r
Supported NE Version
Common
Paramet er Server IP Server Name Rang e N/A N/A Unit N/A N/A Description IP address of an active server. 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. Port number of an active server. Name of an active service. Obtain the name of an active service by choosing System Function > Data Service Server Management in the navigation tree of the Nastar client based on the Server IP and Server Port values of the service. Number of reports generated when a user accesses the server. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A N/A
N/A N/A
Total Reports
Issue 01 (2013-07-15)
[0, +)
Num ber
RAN-PS/PS/General Evaluation
Paramet er ServerRelated Service Abnorma lities Rang e [0, +) Unit Num ber Description Server-Related Service Abnormalities = No Service Interaction Responses + Service Interaction Timeouts + Service Interaction with Long Delay + Downlink TCP Out-of-Orders Supported NE Version BSC6900 V900R013C01 or later version
RAN-PS/PS/Accessibility Evaluation
Paramet er No Service Interactio n Response s Rang e [0, +) Unit Num ber Description 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. Supported NE Version BSC6900 V900R013C01 or later version
[0, +)
Num ber
Issue 01 (2013-07-15)
1895
Common
Param eter Deep Analysi s Rang e N/A Unit N/A Description 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. 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 IMSI N/A N/A N/A N/A Name of a VIP group. International mobile subscriber identity (IMSI) of a VIP subscriber. Alias of a VIP subscriber. Query the name of a VIP subscriber using VIP group management based on the IMSI of the VIP subscriber. BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Alias
N/A
N/A
Issue 01 (2013-07-15)
1896
Rang e N/A
Unit N/A
Description Type approval code (TAC) in international mobile equipment identity (IMEI) of the UE used by a VIP subscriber. 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. Service type for a counter. Number of abnormal counters whose values exceed the result thresholds that engineers set during analysis task creation. Number of reports generated when a user accesses the network.
Termin al Model
N/A
N/A
N/A [0, +)
[0, +)
Num ber
RAN-NET/Accessibility Evaluation
Parameter Access Requests(IntraRAT) Range [0,+) Unit Numbe r Description Number of access requests that a VIP subscriber initiates from a cell in the current system. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1897
Range [0,+)
Unit Numbe r
Description Number of access failures that a VIP subscriber experiences from a cell in the current system. 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 = 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)
[0,+)
Numbe r Numbe r
Number of access requests that a VIP subscriber initiates from a cell in another system. Number of access failures that a VIP subscriber experiences from a cell in another system. Number of failed access requests (inter-RAT) = Number of failed service requests initiated by a specified UE that has gained access to a system of another RAT = Number of incoming interRAT handover failures that this UE experiences on the entire network + Number of times that the first RAB setup after an incoming inter-RAT handover fails)
[0,+)
Average TP on Access
[0,3069 ]
N/A
Issue 01 (2013-07-15)
1898
Range [0,+)
Unit Numbe r
Description Number of times that theTP value is abnormal upon network access. Set the exception threshold when you create a task. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
[0.00,10 0.00]
Proportion of abnormal TP values that a VIP subscriber experiences upon network access. Proportion of abnormal TP values = Number of abnormal TP values/Number of TP values x 100%
[-115,-2 5] [0,+)
dBm
Average RSCP value when a VIP subscriber gains access to the network. Number of times that the RSCP value is abnormal upon network access. Set the exception threshold when you create a task. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
Numbe r
[0.00,10 0.00]
Proportion of abnormal RSCP values that a VIP subscriber experiences upon network access. Proportion of abnormal RSCP values = Number of abnormal RSCP values/Number of RSCP values x 100%
[-24,0]
dB
Average Ec/No value when a VIP subscriber gains access to the network.
Issue 01 (2013-07-15)
1899
Range [0,+)
Unit Numbe r
Description Number of times that the Ec/No value is abnormal upon network access. Set the exception threshold when you create a task. Remark: If the active set contains multiple cells during access, only the counters for the first cell in this active set are analyzed.
[0.00,10 0.00]
Proportion of abnormal Ec/No values that a VIP subscriber experiences upon network access. Proportion of abnormal Ec/No values = Number of abnormal Ec/No values/Number of Ec/No values x 100%
[0,+)
Numbe r
Number of non-service RRC connection setup requests initiated by a VIP subscriber. RRC is short for radio resource control. 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.
RRC Setup Failures(NonService) RRC Setup Success Rate (Non-Service) RRC Setup Requests (Service) RRC Setup Failures (Service)
[0,+)
Numbe r %
Number of non-service RRC connection setup failures after network access. Success rate of non-service RRC connection setups after network access. Number of service RRC connection setup requests after network access. Number of service RRC connection setup failures after network access.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Numbe r Numbe r
[0,+)
Issue 01 (2013-07-15)
1900
Parameter RRC Setup Success Rate (Service) RRC Setup Failures (Service-CS) RRC Setup Success Rate (Service-CS) RRC Setup Failures (Service-PS) RRC Setup Success Rate (Service-PS)
Unit %
Description Success rate of service RRC connection setups after network access. Number of CS RRC connection setup failures after network access. Success rate of CS RRC connection setups after network access. Number of PS RRC connection setup failures after network access. Success rate of PS RRC connection setups after network access.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Numbe r %
Numbe r %
[0.00,10 0.00]
[0,+)
Numbe r
[0.00,10 0.00]
[0,+)
Numbe r
Issue 01 (2013-07-15)
1901
Range [0,+)
Unit Numbe r
Description Number of call setup failures that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Success rate of call setup requests that a VIP subscriber initiates to use the CS service as the mobile-terminated party. Number of call connection acknowledgment (alerting) successes of a VIP subscriber who accesses the network and uses the CS service as the mobile-originated party. The alerting process spans from the RRC connection setup request to the Alerting message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
Call Setup Success Rate (MTC) Call Connection Acknowledgme nt Success Times(Alerting) (MOC)
[0.00,10 0.00]
[0,+)
Numbe r
Call Connection Acknowledgme nt Success Rate (Alerting) (MOC) Call Connection Acknowledgme nt Success Times(Alerting) (MTC) Call Connection Acknowledgme nt Success Rate (Alerting) (MTC)
[0.00,10 0.00]
Rate of call connection acknowledgment (alerting) successes of a VIP subscriber who accesses the network and uses the CS service as the mobile-originated party. Number of successful call connection acknowledgments (alerting) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Success rate of call connection acknowledgments (alerting) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party.
[0,+)
Numbe r
[0.00,10 0.00]
Issue 01 (2013-07-15)
1902
Range [0,+)
Unit Numbe r
Description Number of successful call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-originated party. The connection acknowledgment (Connect Ack) process spans from the RRC connection setup request to the Connect Ack message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
Call Connection Acknowledgme nt Success Rate (Connect Ack) (MOC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MTC)
[0.00,10 0.00]
Success rate of call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-originated party. Number of successful call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party. Success rate of call connection acknowledgments (Connect Ack) that a VIP subscriber experiences during the process of using the CS service as the mobile-terminated party.
[0,+)
Numbe r
[0.00,10 0.00]
Issue 01 (2013-07-15)
1903
Range [0,+)
Unit Numbe r
Description Number of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-originated party. The call success process spans from the RRC connection setup request to the Disconnect message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
[0.00,10 0.00]
Success rate of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-originated party. Number of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-terminated party. Success rate of calls that a VIP subscriber successfully initiates to use the CS service as the mobile-terminated party.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Numbe r
[0.00,10 0.00]
[0,+)
Number
[0.00,10 0.00]
Issue 01 (2013-07-15)
1904
Range [0,+)
Unit Number
Description Number of calls that a VIP subscriber successfully initiates to use the PS service. The call success process spans from the RRC connection setup request to the Disconnect message. Note: This parameter is collected based only on the first RAB after the RRC connection setup is complete.
[0.00,10 0.00]
Success rate of calls that a VIP subscriber successfully initiates to use the PS service.
RAN-NET/PDP Evaluation-PS
Parameter PDP Activation Requests Range [0,+) Unit Number Description Number of PDP activation requests that a VIP subscriber initiates to access the network and use the PS service. Number of PDP activation failures that a VIP subscriber experiences during the process of attempting to access the network and use the PS service. Success rate of PDP activation requests that a VIP subscriber initiates to access the network and use the PS service. Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0.00,10 0.00]
Issue 01 (2013-07-15)
1905
RAN-NET/Retainability Evaluation
Parameter Release Times (Intra-RAT) Range [0,+) Unit Number Description Number of times that a VIP subscriber releases all services in the current system. Releases(Intra-RAT) = Access Requests(Intra-RAT) - Access Failures(Intra-RAT) Abnormal Release Times (Intra-RAT) [0,+) Number Number of times that a VIP subscriber abnormally releases all services in the current system. Abnormal Release Times(IntraRAT) = Number of AMR RAB abnormal releases + Number of VP RAB abnormal releases + Number of PS R99 RAB abnormal releases + Number of HSDPA RAB abnormal releases + Number of HSUPA abnormal releases + Number of HSPA abnormal releases Number of the first RAB abnormal releases after interRAT incoming handover occurs. Release Times (Inter-RAT) [0,+) Number Number of times that a VIP subscriber releases all services in another system. Releases(Inter-RAT) = Access Requests(Inter-RAT) Access Failures(Inter-RAT) Abnormal Release Times (Inter-RAT) [0,+) Number Number of times that a VIP subscriber abnormally releases all services in another system. Abnormal Release Times(InterRAT) = Number of times that the first RAB after an incoming inter-RAT handover is abnormally released. BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1906
Range [0,+)
Unit Number
Description Number of times that a VIP subscriber releases all RRC connections during the process of using a service. Number of times that a VIP subscriber abnormally releases all RRC connections during the process of using a service.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
RAN-NET/Delay Evaluation
Parameter RRC Setup Success Times (Non-Service) Range [0,+) Unit Number Description Number of successful nonservice RRC connection setups upon successful call initiation. Number of successful RRC connection setups (non-service) = Number of RRC connection setup requests (non-service) Number of RRC connection setup failures (non-service) = Number of valid RRC connection setup delays (nonservice) Average RRC Setup Delay (Non-Service) N/A Second Average delay for non-service RRC connection setup upon successful call initiation. RRC connection setup delay = Time when the RRC CONN SETUP CMP message is generated Time when the RRC CONN REQ message is generated. Overlong RRC Setup Delay Times(NonService) [0,+) Number Number of overlong delays for non-service RRC connection setup upon successful call initiation. Set the overlong delay threshold when you create a task. BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1907
Parameter Proportion of Overlong RRC Setup Delay (Non-Service) RRC Setup Success Times (Service)
Unit %
Description Proportion of delays for nonservice RRC connection setup in all overlong delays upon successful call initiation. Number of successful service RRC connection setups upon successful call initiation. Number of service RRC 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.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Second
Average delay for service RRC connection setup upon successful call initiation. RRC connection setup delay = Time when the RRC CONN SETUP CMP message is generated Time when the RRC CONN REQ message is generated.
[0,+)
Number
Number of overlong delays for service RRC connection setup upon successful call initiation. Set the overlong delay threshold when you create a task.
[0.00,1 00.00]
Proportion of overlong delays for service RRC connection setup in all overlong delays upon successful call initiation.
RAN-NET/Mobility Evaluation
Parameter Soft Handover Requests Range [0,+) Unit Number Description Number of soft handover requests that a VIP subscriber initiates during the process of using a service. Supported NE Version BSC6900 V900R014C00 or later version
Issue 01 (2013-07-15)
1908
Range [0,+)
Unit Number
Description Number of soft handover failures that a VIP subscriber experiences during the process of using a service. Success rate of soft handovers (including softer handovers) that a VIP subscriber initiates during the process of using a service. Number of hard handover requests that a VIP subscriber initiates during the process of using a service. Number of hard handover failures that a VIP subscriber experiences during the process of using a service. Success rate of hard handovers that a VIP subscriber initiates during the process of using a service. Average soft handover delay during the process for a VIP subscriber to use a service. Average hard handover delay during the process for a VIP subscriber to use a service. Number of outgoing handover requests (from a UMTS network to another network) initiated by a UE. Number of outgoing handover requests (from a UMTS network to a GSM network) initiated by a VIP subscriber.
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0.00,1 00.00]
[0,+)
Number
[0,+)
Number
[0.00,1 00.00]
Average Soft Handover Delay Average Hard Handover Delay Inter-RAT Outgoing Handover Requests Inter-RAT Outgoing Handover Requests (UMTS to GSM) Inter-RAT Outgoing Handover Requests (UMTS to LTE)
[0,+)
Second
[0,+)
Second
[0,+)
Number
[0,+)
Number
[0,+)
Number
Number of outgoing handover requests (from a UMTS network to an LTE network) initiated by a VIP subscriber.
Issue 01 (2013-07-15)
1909
Parameter Inter-RAT Outgoing Handover Failures Inter-RAT Outgoing Handover Failures(UMTS to GSM) Inter-RAT Outgoing Handover Failures(UMTS to LTE) Inter-RAT Incoming Handover Requests Inter-RAT Incoming Handover Requests(GSM to UMTS) Inter-RAT Incoming Handover Requests(LTE to UMTS) Inter-RAT Incoming Handover Failures Inter-RAT Incoming Handover Failures(GSM to UMTS) Inter-RAT Incoming Handover Failures(LTE to UMTS)
Range [0,+)
Unit Number
Description Number of outgoing handover failures (from a UMTS network to another network) experienced by a VIP subscriber. Number of outgoing handover failures (from a UMTS network to a GSM network) experienced by a VIP subscriber. Number of outgoing handover failures (from one UMTS network to another LTE network) experienced by a UE. Number of inter-RAT handover requests (from another network to a UMTS network) initiated by a VIP subscriber. Number of inter-RAT handover requests (from a GSM network to a UMTS network) initiated by a VIP subscriber. Number of inter-RAT handover requests (from an LTE network to a UMTS network) initiated by a VIP subscriber. Number of inter-RAT handover failures (from another network to a UMTS network) experienced by a VIP subscriber. Number of inter-RAT handover failures (from a GSM network to a UMTS network) experienced by a VIP subscriber. Number of inter-RAT handover failures (from an LTE network to a UMTS network) experienced by a VIP subscriber.
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1910
Range [0,+)
Unit Second
Description Average delay for outgoing interRAT handover recorded by the current system. Outgoing inter-RAT handover delay = Time when the IU RELEASE COMMAND message is generated Time when the RELOCATION REQUIRED message is generated.
Average InterRAT Outgoing Handover Delay (UMTS to GSM) Average InterRAT Outgoing Handover Delay (UMTS to LTE) Average InterRAT Incoming Handover Delay
[0,+)
Second
[0,+)
Second
Average delay for UMTS-toLTE handover recorded by the current system. Average delay for incoming inter-RAT handover recorded by the current system. Incoming inter-RAT handover delay = Time when the UTRAN MOBILITY INFORMATION CONFIRM message is generated Time when the RELOCATION REQUIRED message is generated.
[0,+)
Second
Average InterRAT Incoming Handover Delay (GSM to UMTS) Average InterRAT Incoming Handover Delay (LTE to UMTS) Inter-RAT Cell Reselection Times
[0,+)
Second
[0,+)
Second
Average delay for LTE-toUMTS handover recorded by the current system. Number of cell reselections recorded by the current system.
[0,+)
Number
Issue 01 (2013-07-15)
1911
RAN-CS/AMR/Accessibility Evaluation
Parameter RAB Setup Requests Range [0,+) Unit Number Description Number of RAB setup requests initiated by a VIP subscriber. RAB is short for radio access bearer. RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate [0,+) Number Number of RAB setup failures experienced by a VIP subscriber. Number of times that a VIP subscriber successfully initiates an RAB setup request. RAB setup success rate after network access. RAB setup success rate (%) = Number of successful RAB setups/Number of RAB setup requests x 100%. Call Connection Acknowledgme nt Success Times(Alerting) Call Connection Acknowledgme nt Success Times(Connect Ack) Abnormal Release Times Before Connection Acknowledge [0,+) Number Number of times that a VIP subscriber hears the alerting upon successful call initiation. Number of times that a VIP subscriber hears the peer ends' voice upon successful call initiation. 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. Supported NE Version BSC6900 V900R013C00 or later version
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1912
RAN-CS/AMR/Retainability Evaluation
Parameter RAB Setup Success Times Abnormal RAB Release Times Range [0,+) Unit Number Description See RAB Setup Success Times in RAN-CS/VP/Accessibility Evaluation Number of times that the RAB is abnormally released after a VIP subscriber gains access to the network and successfully initiates a call. Abnormal RAB release rate after a VIP subscriber gains access to the network and successfully initiates a call. Abnormal RAB release rate (%) = Number of abnormal RAB releases/Number of successful call setups x 100%. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,10 0.00]
RAN-CS/AMR/Delay Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Number Description Number of successful RAB setups during call initiation, that is, number of RAB setup delays. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1913
Range [0,+)
Unit Second
Description Average RAB setup delay during the process for a VIP subscriber to initiate a call. Average RAB setup delay (s) = Sum of RAB setup delays/ Number of RAB setup delays. RAB setup delay = RAB setup request connection acknowledge time RAB setup request time. Statistical point for RAB setup request connection acknowledge time: When the RAB assignment procedure is successful, namely, when the SRNC sends a Radio Access Bearer Assignment Response message to the CN after it receives an RAB setup connection acknowledge message. Statistical point for RAB setup request time: When the UTRAN receives a Radio Access Bearer Assignment Request message from the CN.
[0,+)
Number
Number of times that the RAB BSC6900 setup delay is overlong during V900R013C00 the process for a VIP subscriber or later version to initiate a call. Set the exception threshold when you create a task.
[0.00,10 0.00]
Proportion of RAB setup delays in all overlong delays. Proportion of RAB setup delays (%) = Number of overlong RAB setup delays/Number of RAB setup delays x 100% = Number of overlong RAB setup delays/ Number of successful RAB setups x 100%.
[0,+)
Number
Number of times that the call setup delay of the mobileoriginated party upon successful call initiation is overlong.
Issue 01 (2013-07-15)
1914
Parameter Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC)
Range [0,+)
Unit Second
Description Average call setup delay of the mobile-originated party upon successful call initiation. Number of times that the call setup delay of the mobileoriginated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,10 0.00]
Proportion of overlong call setup delays of the mobileoriginated party upon successful call initiation. Proportion of overlong call setup delays (mobileoriginated) (%) = Number of overlong call setup delays (mobile-originated)/Number of call setup delays (mobileoriginated) x 100% = Number of overlong call setup delays (mobile-originated)/Number of successful RRC connection setups x 100%.
[0,+)
Number
Number of times that the call setup delay of the mobileterminated party upon successful call initiation is overlong. Average call setup delay of the mobile-terminated party upon successful call initiation. Number of times that the call setup delay of the mobileterminated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
Average Call Setup Delay (MTC) Overlong Call Setup Delay Times(MTC)
[0,+)
Second
[0,+)
Number
Issue 01 (2013-07-15)
1915
Unit %
Description Proportion of overlong call setup delays of the mobileterminated party upon successful call initiation. Proportion of overlong call setup delays (mobileterminated) (%) = Number of overlong call setup delays (mobile-terminated)/Number of call setup delays (mobileterminated) x 100% = Number of overlong call setup delays (mobile-terminated)/Number of successful RRC connection setups x 100%.
Call Connection Acknowledgme nt Success Times(Alerting) (MOC) Average Call Connection Acknowledgme nt Delay (Alerting) (MOC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MOC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MOC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MOC)
[0,+)
Number
Number of times that the mobile-originated party hears the alerting upon successful call initiation. Average alerting delay of the mobile-originated party upon successful call initiation.
[0,+)
Second
[0,+)
Number
Number of times that the alerting delay of the mobileoriginated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0.00,10 0.00]
Proportion of overlong alerting delays experienced by the mobile-originated party upon successful call initiation.
[0,+)
Number
Number of call connection acknowledgment (Connect Ack) delays experienced by the mobile-originated party upon successful call initiation.
Issue 01 (2013-07-15)
1916
Parameter Average Call Connection Acknowledgme nt Delay (Connect Ack) (MOC) Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MOC)
Range [0,+)
Unit Second
Description Average call connection acknowledgment (Connect Ack) delay of the mobileoriginated party upon successful call initiation. Number of times that the call connection acknowledgment (Connect Ack) delay of the mobile-originated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0,+)
Number
Proportion of Overlong Call Connection Acknowledgme nt Delay (Connect Ack) (MOC) Call Connection Acknowledgme nt Success Times(Alerting) (MTC) Average Call Connection Acknowledgme nt Delay (Alerting) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MTC)
[0.00,10 0.00]
Proportion of overlong call connection acknowledgment (Connect Ack) delays experienced by the mobileoriginated party upon successful call initiation. Number of times that the mobile-terminated party hears the alerting upon successful call initiation. Average call connection acknowledgment (alerting) delay of the mobile-terminated party upon successful call initiation. Number of times that the call connection acknowledgment (alerting) delay of the mobileterminated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0,+)
Number
[0,+)
Second
[0,+)
Number
Issue 01 (2013-07-15)
1917
Parameter Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MTC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MTC) Average Call Connection Acknowledgme nt Delay (Connect Ack) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MTC)
Unit %
Description Proportion of overlong call connection acknowledgment (alerting) delays experienced by the mobile-terminated party upon successful call initiation.
[0,+)
Number
Number of successful call connection acknowledgments (Connect Ack) experienced by the mobile-terminated party upon successful call initiation. Average call connection acknowledgment (Connect Ack) delay of the mobileterminated party upon successful call initiation. Number of times that the call connection acknowledgment (Connect Ack) delay of the mobile-terminated party upon successful call initiation is overlong. Set the exception threshold when you create a task.
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
Proportion of call connection acknowledgment (Connect Ack) delays experienced by the mobile-terminated party upon successful call initiation.
Issue 01 (2013-07-15)
1918
Range [0,+)
Unit Second
Description Average RAB duration upon successful call initiation. 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
[0,+)
Number
Number of times that the RAB duration is below the threshold for short RAB duration upon successful call initiation. Set the exception threshold when you create a task.
[0,+)
Second
Average call duration of calls initiated by a VIP subscriber. Number of short calls upon successful call initiation. The mechanism for calculating the number of short calls adds the condition that short calls are initiated by the mobileoriginated party.
[0,+)
Number
Issue 01 (2013-07-15)
1919
Unit %
Description Proportion of short calls upon successful call initiation. The mechanism for calculating the proportion of short calls adds the condition that short calls are initiated by the mobileoriginated party.
[0,+)
Second
Average call duration of calls initiated by a VIP subscriber. Number of short calls upon successful call initiation. The mechanism for calculating the number of short calls adds the condition that short calls are initiated by the mobileterminated.
[0,+)
Number
[0.00,10 0.00]
Proportion of short calls upon successful call initiation. The mechanism for calculating the proportion of short calls adds the condition that short calls are initiated by the mobileterminated.
RAN-CS/AMR/Quality Evaluation
Parameter Call Setup Success Times Downlink OneWay Audio Times Range [0,+) Unit Number Description Number of times that a VIP subscriber successfully initiates a call setup request. Number of calls with downlink one-way audio problems. Downlink one-way audio problems are detected by the RNC. [0.00,10 0.00] % Proportion of Downlink OneWay Audio = Downlink OneWay Audio Times/RAB Setup Successes x 100% Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
Issue 01 (2013-07-15)
1920
Range [0,+)
Unit Number
Description Number of calls with uplink one-way audio problems. Uplink one-way audio problems are detected by the RNC.
[0.00,10 0.00]
Proportion of Uplink One-Way Audio = Uplink One-Way Audio Times/RAB Setup Successes x 100% Number of calls with static problems. Static problems are detected by the RNC.
[0,+)
Number
Noise Proportion
[0.00,10 0.00]
Proportion of calls with static problems. Proportion of calls with static problems (%) = Number of calls with static problems/Number of connected calls (Connect Ack) x 100%.
Issue 01 (2013-07-15)
1921
Range [0,+)
Unit Number
Description Number of signal quality indicator (SQI) reports generated during a call. 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. 2. The RNC collects statistics on the average SQI value and divides signal quality into different levels according to SQI values: RAN14.0: Excellent (SQI<= (400,500]), Good (SQI<= (300,400]), Accept (SQI<= (200,300]), Poor (SQI<= (100,200]), Bad (SQI<= [0,100]). RAN13.0 and earlier: Good (SQI <= (300,500]), Accept (SQI <= (200,300]), Bad (SQI <=(0,200]). You can modify the segment intervals of levels by running the SET USQICOUNT command on the RNC.
Average SQI
[0,+)
N/A
Average SQI value in the SQI reports generated during a call. 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. Set the exception threshold when you create a task.
Abnormal SQIs
[0,+)
Number
Issue 01 (2013-07-15)
1922
Unit %
Description Proportion of calls with abnormal SQI values. Proportion of calls with abnormal SQI values (%) = Number of calls with abnormal SQI values/Number of connected calls (Connect Ack) x 100%.
[0.00,10 0.00]
Proportion of calls whose SQI is Excellent during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Good during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Accept during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Poor during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of calls whose SQI is Bad during successful voice service initiation. This parameter is applicable only to the AMR service.
[0.00,10 0.00]
Proportion of level 1 uplink BLER values upon successful call initiation. BLER is short for block error rate. This parameter is applicable only to the AMR service. Standard for level 1: 00.78%.
Issue 01 (2013-07-15)
1923
Unit %
Description Proportion of level 2 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 2: 0.78% 1.56%.
[0.00,10 0.00]
Proportion of level 3 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 3: 1.56% 3.12%
[0.00,10 0.00]
Proportion of level 4 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 4: 3.12% 6.24%.
[0.00,10 0.00]
Proportion of level 5 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 5: 6.24% 12.48%.
[0.00,10 0.00]
Proportion of level 6 uplink BLER values upon successful call initiation. This parameter is applicable only to the AMR service. Standard for level 6: above 12.48%.
Issue 01 (2013-07-15)
1924
RAN-CS/VP/Accessibility Evaluation
Parameter RAB Setup Requests RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate Call Connection Acknowledgme nt Success Times(Alerting) Call Connection Acknowledgme nt Success Times(Connect Ack) Abnormal Release Times Before Connection Acknowledgme nt Range [0,+) Unit Number Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
Number
[0,+)
Number
[0,+)
Number
RAN-CS/VP/Retainability Evaluation
Parameter RAB Setup Success Times Abnormal RAB Release Times Range [0,+) Unit Number Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
Issue 01 (2013-07-15)
1925
Unit %
RAN-CS/VP/Delay Evaluation
Parameter RAB Setup Success Times Average RAB Setup Delay Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Average Call Setup Delay (MTC) Range [0,+) Unit Number Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Second
[0,+)
Number
Number
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR".
[0,+)
Second
Issue 01 (2013-07-15)
1926
Parameter Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay (MTC) Call Connection Acknowledgme nt Success Times(Alerting) (MOC) Average Call Connection Acknowledgme nt Delay (Alerting) (MOC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MOC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MOC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MOC) Average Call Connection Acknowledgme nt Delay (Connect Ack) (MOC)
Range [0,+)
Unit Number
Description Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0.00,10 0.00]
[0,+)
Number
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
[0,+)
Second
Issue 01 (2013-07-15)
1927
Parameter Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MOC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Connect Ack) (MOC) Call Connection Acknowledgme nt Success Times(Alerting) (MTC) Average Call Connection Acknowledgme nt Delay (Alerting) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Alerting) (MTC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Alerting) (MTC) Call Connection Acknowledgme nt Success Times(Connect Ack)(MTC)
Range [0,+)
Unit Number
[0.00,10 0.00]
[0,+)
Number
[0,+)
Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Number
Issue 01 (2013-07-15)
1928
Parameter Average Call Connection Acknowledgme nt Delay (Connect Ack) (MTC) Overlong Call Connection Acknowledgme nt Delay Times (Connect Ack) (MTC) Proportion of Overlong Call Connection Acknowledgme nt Delay (Connect Ack) (MTC) Average RAB Service Duration Overshort RAB Service Duration Times Average Service Duration(MOC) Number of Short Calls (MOC) Proportion of Short Calls (MOC) Average Service Duration(MTC) Number of Short Calls (MTC)
Range [0,+)
Unit Second
[0,+)
Number
[0.00,10 0.00]
[0,+)
Second
Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR". Same as the related counter in "RAN-CS/AMR".
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0,+)
Second
[0,+)
Number
Second
[0,+)
Number
Issue 01 (2013-07-15)
1929
Unit %
RAN-CS/SMS/Accessibility Evaluation
Parameter Setup Requests (MOC) Setup Failures (MOC) Setup Success Rate (MOC) Setup Requests (MTC) Setup Failures (MTC) Setup Success Rate (MTC) Range [0,+) Unit Number Description Number of SMS service setup requests initiated by the mobileterminated party. Number of failed SMS service setups initiated by the mobileoriginated party. Number of successful SMS service setups initiated by the mobile-originated party. Number of SMS service setup requests initiated by the mobileterminated party. Number of failed SMS service setups initiated by the mobileterminated party. Number of successful SMS service setups initiated by the mobile-terminated party. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
Number
[0,+)
Number
[0.00,10 0.00]
Issue 01 (2013-07-15)
1930
[0,+)
[0.00,1 00.00]
[0,+)
[0.00,1 00.00]
Issue 01 (2013-07-15)
1931
Issue 01 (2013-07-15)
1932
Parameter Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong RAB Setup Delay Times(MOC)
Range [0, +)
Unit Numb er
Description Number of times that the call setup delay of the mobile-originated party upon successful call initiation is overlong. Average call delay of the mobileoriginated party upon successful call initiation. Number of times that the call setup delay of the mobile-originated party upon successful call initiation is overlong. Set the overlong delay threshold when you create a task.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0, +) [0, +)
Secon d Numb er
[0.00,1 00.00]
Proportion of overlong call setup delays of the mobile-originated party upon successful call initiation. Proportion of overlong call setup delays (mobile-originated) = Number of overlong call setup delays (mobile-originated)/ Number of call setup delays (mobile-originated) x 100% = Number of overlong call setup delays (mobile-originated)/ Number of successful RRC connection setups x 100%.
[0, +)
Numb er
Number of times that the call setup delay of the mobile-terminated upon successful call initiation is abnormal.
Issue 01 (2013-07-15)
1933
Range [0, +)
Unit Secon d
Description Average call setup delay of the mobile-terminated upon successful call initiation. Average call setup delay =Sum of call setup delays/Number of call setup delays. Call setup delay = RAB request connection acknowledge time Signaling access time. Statistical point for RAB request connection acknowledge time: When the RAB assignment procedure is successful, namely, when the SRNC sends a Radio Access Bearer Assignment Response message to the CN after it receives an RAB setup connection acknowledge message. Statistical point for signaling access time: When an RRC SETUP REQ or RELOC REQ message is received or when an incoming inter-RAT handover request is initiated.
[0, +)
Numb er
Number of times that the call setup delay of the mobile-terminated party upon successful call initiation is overlong. Set the overlong delay threshold when you create a task.
[0.00,1 00.00]
Proportion of overlong call setup delays experienced by the mobileterminated party upon successful call initiation. Proportion of overlong call setup delays = Number of overlong call setup delays/Number of call setup delays x 100% = Number of overlong call setup delays/Number of successful RRC connection setups x 100%.
Issue 01 (2013-07-15)
1934
Range [0, +)
Unit Secon d
Description Average RAB duration upon successful call initiation. 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. Statistical point for RAB request connection acknowledge time: When the RAB assignment procedure is successful, after receiving an RAB setup connection acknowledge message, the SRNC sends a Radio Access Bearer Assignment Response message to the CN.
Issue 01 (2013-07-15)
1935
Parameter Downlink Traffic Volume Average Downlink Transmission Duration Average Downlink Throughput
Unit KB
Description Downlink traffic volume of all common PS services. Average downlink transmission duration for all common PS services. Average downlink throughput for all common PS services. Average downlink throughput = Downlink traffic volume/ Downlink data transmission duration.
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
Second
[0.00, +)
kbit/s
[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. Set the exception threshold when you create a task.
Uplink Traffic Volume Average Uplink Transmission Duration Average Uplink Throughput
KB
Uplink traffic volume for all common PS services. Average uplink transmission duration for all common PS services. Average uplink throughput rate for all common PS services. Average uplink throughput = Total uplink traffic volume/Total uplink transmission duration
BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
Second
kbit/s
[0, +)
Numbe r
Number of times that among all common PS services, the average uplink throughput for one RAB setup is below a threshold for low average uplink throughput. Set the exception threshold when you create a task.
Issue 01 (2013-07-15)
1936
Issue 01 (2013-07-15)
1937
Unit %
Description Proportion of level 6 uplink BLER values upon successful call initiation. This parameter is applicable only to the PS service. Standard for level 6: 12.48% < X.
RAN-PS/HSDPA/Accessibility Evaluation
Parameter RAB Setup Requests RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate Rang e [0, +) [0, +) [0, +) [0.00,1 00.00] Unit Numbe r Numbe r Numbe r % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RAN-PS/HSDPA/Retainability Evaluation
Parameter RAB Setup Success Times Abnormal RAB Release Times Abnormal RAB Release Rate Rang e [0, +) [0, +) [0.00, 100.00 ] Unit Numbe r Numbe r % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1938
RAN-PS/HSDPA/Delay Evaluation
Parameter RAB Setup Success Times Average RAB Setup Delay Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Average Call Setup Delay (MTC) Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay (MTC) Rang e [0, +) [0, +) [0, +) [0.00, 100.00 ] [0, +) [0, +) [0, +) [0.00, 100.00 ] [0, +) [0, +) [0, +) [0.00, 100.00 ] Unit Numbe r Second Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Numbe r %
Numbe r Second
Numbe r %
Numbe r Second
Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Numbe r %
Issue 01 (2013-07-15)
1939
Rang e [0, +)
Unit Second
RAN-PS/HSDPA/Rate Evaluation
Parameter Downlink Traffic Volume Average Downlink Transmission Duration Average Downlink Throughput Low Average Downlink Throughput Times Average HSDPA Downlink Rate Low Average HSDPA Downlink Rate Times Rang e [0, +) [0, +) Unit KB Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Second
[0.00, +) [0, +)
kbit/s
Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Numbe r
[0.00, +) [0, +)
kbit/s
Average downlink rate for all HSDPA services. Number of times that the average downlink rate for all HSDPA services is low. Set the threshold for low average rate when you create a task.
Numbe r
Average HSDPA Downlink Rate with Sufficient Resources Times of Low Average HSDPA Downlink Rate with Sufficient Resources
[0.00, +)
kbit/s
Average downlink rate for all HSDPA services when service resources are sufficient.
[0, +)
Numbe r
Number of times that the average downlink rate for all HSDPA services is low when service resources are sufficient. Set the threshold for low average rate when you create a task.
Issue 01 (2013-07-15)
1940
Parameter Average HSDPA Downlink Rate with Insufficient Resources Times of Low Average HSDPA Downlink Rate with Insufficient Resources
Rang e [0.00, +)
Unit kbit/s
Description Average downlink rate for all HSDPA services when service resources are insufficient.
[0, +)
Numbe r
Number of times that the average downlink rate for all HSDPA services is low when service resources are insufficient. Set the threshold for low average rate when you create a task.
RAN-PS/HSUPA/Accessibility Evaluation
Parameter RAB Setup Requests RAB Setup Failures RAB Setup Success Times RAB Setup Success Rate Rang e [0, +) [0, +) [0, +) [0.00,1 00.00] Unit Numbe r Numbe r Numbe r % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RAN-PS/HSUPA/Retainability Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Numbe r Description Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
1941
Range [0,+)
Unit Numbe r %
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0.00,1 00.00]
RAN-PS/HSUPA/Delay Evaluation
Parameter RAB Setup Success Times Average RAB Setup Delay Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Range [0,+) Unit Numb er Secon d Numb er % Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
[0,+)
[0,+)
[0,+)
[0.00,1 00.00]
[0,+)
Numb er
Issue 01 (2013-07-15)
1942
Parameter Average Call Setup Delay (MTC) Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay Average RAB Service Duration
Range [0,+)
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Secon d
RAN-PS/HSUPA/Rate Evaluation
Parameter Uplink Traffic Volume Range [0,+) Unit KB Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Second
[0.00,+)
kbit/s
[0,+)
Number
Issue 01 (2013-07-15)
1943
RAN-PS/HSPA/Accessibility Evaluation
Parameter RAB Setup Requests Range [0,+) Unit Number Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
[0.00,100.00]
RAN-PS/HSPA/Retainability Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Number Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Number
[0.00,100.00]
Issue 01 (2013-07-15)
1944
RAN-PS/HSPA/Delay Evaluation
Parameter RAB Setup Success Times Range [0,+) Unit Number Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Second
Overlong RAB Setup Delay Times Proportion of Overlong RAB Setup Delay Call Setup Delay Times (MOC) Average Call Setup Delay (MOC) Overlong Call Setup Delay Times(MOC) Proportion of Overlong Call Setup Delay (MOC) Call Setup Delay Times (MTC) Average Call Setup Delay (MTC)
[0,+)
Number
[0.00,100.00]
[0,+)
Number
[0,+)
Second
[0,+)
Number
[0.00,100.00]
[0,+)
Number
[0,+)
Second
Issue 01 (2013-07-15)
1945
Parameter Overlong Call Setup Delay Times(MTC) Proportion of Overlong Call Setup Delay (MTC) Average RAB Service Duration
Range [0,+)
Unit Number
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0.00,100.00]
[0,+)
Second
RAN-PS/HSPA/Rate Evaluation
Parameter Downlink Traffic Volume Range [0,+) Unit KB Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99". Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
Average Downlink Transmission Duration Average Downlink Throughput Low Average Downlink Throughput Times Uplink Traffic Volume
[0,+)
Second
[0.00,+)
kbit/s
[0,+)
Number
[0,+)
KB
[0,+)
Second
Issue 01 (2013-07-15)
1946
Range [0.00,+)
Unit kbit/s
Description Same as the related counter in "RAN-PS/PS R99". Same as the related counter in "RAN-PS/PS R99".
Supported NE Version BSC6900 V900R014C00 or later version BSC6900 V900R014C00 or later version
[0,+)
Number
[0, + )
N Number of RAB setup failures u where multiple RABs are accessed m during a call. b e r
Issue 01 (2013-07-15)
1947
U Description n i t % Setup success rate for accessing multiple RABs during a call.
Supported NE Version
Mul tiRA B Rele ase Tim es Abn orm al Mul tiRA B Rele ase Tim es
[ 0 , + )
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.
Issue 01 (2013-07-15)
1948
Par am eter
R a n g e [ 0 . 0 0 , 1 0 0 . 0 0 ]
U Description n i t % Abnormal RAB release rate for releasing multiple RABs that contain at least one CS RAB at a time during a call.
Supported NE Version
Mul tiRA B Rele ase Tim es Abn orm al Mul tiRA B Rele ase Tim es
[ 0 , + )
N u m b e r
Number of abnormal RAB releases where multiple RABs that contain only PS RABs are released during a call.
Issue 01 (2013-07-15)
1949
Par am eter
R a n g e [ 0 . 0 0 , 1 0 0 . 0 0 ]
U Description n i t % Abnormal RAB release rate for releasing multiple RABs that contain only PS RABs during a call.
Supported NE Version
Active Cell/Common
Paramete r RNC ID Range [0,4095] Unit N/A Description ID of the RNC to which an active cell belongs. Name of the RNC to which an active cell belongs. ID of an active cell. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
[0,65535]
N/A
Cell Name
N/A
N/A
Service Type
N/A
N/A
Issue 01 (2013-07-15)
1950
Number of nonBSC6900 service setup V900R013C00 or requests that a VIP later version group or VIP subscriber initiates in an active cell. 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. Set the exception threshold when you create a task. BSC6900 V900R013C00 or later version
[0,+)
Number
[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.
[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. Set the exception threshold when you create a task.
Issue 01 (2013-07-15)
1951
Range [0,+)
Unit Number
Description
Supported NE Version
Number of nonBSC6900 service setup V900R013C00 or requests that a VIP later version group or VIP subscriber initiates in an active cell. Number of service BSC6900 setup requests that V900R013C00 or a VIP group or VIP later version subscriber initiates in an active cell. Number of service setup failures that a VIP group or VIP subscriber experiences in an active cell. BSC6900 V900R013C00 or later version
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1952
[0,+)
Numbe r
[0,+)
Numb er
Issue 01 (2013-07-15)
1953
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1954
[0,+)
Number
[0,+)
Number
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1955
[0,+)
Numbe r
[0,+)
Number
Number of PS BSC6900 service setup V900R013C00 or failures that a VIP later version group or VIP subscriber experiences in an active cell.
Issue 01 (2013-07-15)
1956
[0,+)
Numbe r
[0,+)
Number
Issue 01 (2013-07-15)
1957
[0,+)
Number
[0,+)
Number
Issue 01 (2013-07-15)
1958
[0,+)
Number
Common
Parameter Deep Analysis Rang e N/A Unit N/A Description 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. 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. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
1959
User ID
N/A
N/A
ID of a VIP subscriber.
Issue 01 (2013-07-15)
Parameter Alias
Rang e N/A
Unit N/A
Description 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. International mobile equipment identity-type allocation code (IMEI-TAC) of the terminal used by a VIP subscriber. 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. 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. Number of reports of the VIP user.
IMEI-TAC
N/A
N/A
Terminal Model
N/A
N/A
[0, +)
Numb er
Total Reports
[0, +)
Numb er
SGSN-Attach
Parameter Rang e Unit Numb er Description Number of attach process requests by a VIP subscriber on the GSM and UMTS networks. Attach processes include: GPRS attach Combined attach Attach Failures [0, +) Numb er Number of attach process failures by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1960
Unit %
Description Attach process success rate by a VIP subscriber on the GSM and UMTS networks. Attach success rate = (1 Number of attach failures/ Number of attach requests) x 100%
[0, +) [0, +)
ms
Average delay of an attach process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of an attach process by a VIP subscriber on the GSM and UMTS networks.
Numb er
SGSN-RAU
Parameter RAU (others) Requests Rang e [0.00, 100.0 0] [0, +) [0, +) Unit % Description Number of other RAU processes by a VIP subscriber on the GSM and UMTS networks Number of other RAU process failures by a VIP subscriber on the GSM and UMTS networks. Other RAU process success rate by a VIP subscriber on the GSM and UMTS networks. RAU (others) success rate = (1 Number of RAU (others) failures/Number of RAU (others) requests) x 100% Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
ms
Numb er
Issue 01 (2013-07-15)
1961
Rang e [0, +)
Unit Numb er
Description Number of intra SGSN RAU process requests by a VIP subscriber on the GSM and UMTS networks. Intra SGSN RAU processes include: Intra RAU Intra combined RAU Periodic RAU Periodic combined RAU
[0, +)
Numb er
Number of intra SGSN RAU process failures by a VIP subscriber on the GSM and UMTS networks. Intra SGSN RAU process success rate by a VIP subscriber on the GSM and UMTS networks. Intra SGSN RAU success rate = (1 Number of intra SGSN RAU failures/Number of intra SGSN RAU requests) x 100%
[0.00, 100.0 0]
Average Intra SGSN RAU Delay Overlong Intra SGSN RAU Delays
[0, +)
ms
Average delay of an intra SGSN RAU process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of an intra SGSN RAU process by a VIP subscriber on the GSM and UMTS networks. Number of inter SGSN RAU process requests by a VIP subscriber on the GSM and UMTS networks. Inter SGSN RAU processes include: Inter RAU Inter combined RAU
[0, +)
Numb er
[0, +)
Numb er
Issue 01 (2013-07-15)
1962
Rang e [0, +)
Unit Numb er
Description Number of inter SGSN RAU process failures by a VIP subscriber on the GSM and UMTS networks. Inter SGSN RAU process success rate by a VIP subscriber on the GSM and UMTS networks. Inter SGSN RAU process success rate by a VIP subscriber on the GSM and UMTS networks.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
[0.00, 100.0 0]
Average Inter SGSN RAU Delay Overlong Inter SGSN RAU Delays
[0, +)
ms
Average delay of an inter SGSN RAU process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of an inter SGSN RAU process by a VIP subscriber on the GSM and UMTS networks.
[0, +)
Numb er
SGSN-Service Req
Parameter Service Req Requests Rang e [0, +) Unit Numb er Description Number of service req process requests by a VIP subscriber on the GSM and UMTS network. The service req process includes: Service Request Service Req Failures Service Req Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of service req process failures by a VIP subscriber on the GSM and UMTS network. Service req process success rate by a VIP subscriber on the GSM and UMTS networks. Service req success rate = (1 Number of service req failures/ Number of service req requests) x 100% USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1963
Unit ms
Description Average delay of a service req process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a service req process by a VIP subscriber on the GSM and UMTS networks.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Numb er
SGSN-Relocation
Parameter Relocation Requests Rang e [0, +) Unit Numb er Description Number of relocation process requests by a VIP subscriber on the GSM and UMTS networks. Relocation processes include: Intra SRNS relocation Inter SRNS relocation Relocation Failures Relocation Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of relocation process failures by a VIP subscriber on the GSM and UMTS networks. Relocation process success rate by a VIP subscriber on the GSM and UMTS networks. Relocation success rate = (1 Number of relocation failures/ Number of relocation requests) x 100% Average Relocation Delay Overlong Relocation Delays [0, +) [0, +) ms Average delay of a relocation process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a relocation process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Numb er
Issue 01 (2013-07-15)
1964
SGSN-System Change
Parameter System Change Requests Rang e [0, +) Unit Numb er Description Number of system change process requests by a VIP subscriber on the GSM and UMTS networks. System change processes include: 3G to 2G system change 2G to 3G system change System Change Failures [0, +) Numb er Number of system change process failures by a VIP subscriber on the GSM and UMTS networks. System change process success rate by a VIP subscriber on the GSM and UMTS networks. System change success rate = (1 Number of system change failures/Number of system change requests) x 100% Average System Change Delay [0, +) ms Average delay of a system change process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a system change process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0.00, 100.0 0]
[0, +)
Numb er
SGSN-Paging
Parameter Paging Requests Rang e [0, +) Unit Numb er Description Number of paging process requests by a VIP subscriber on the GSM and UMTS networks. The paging process includes Paging. Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1965
Unit Numb er %
Description Number of paging process failures by a VIP subscriber on the GSM and UMTS networks. Paging process success rate by a VIP subscriber on the GSM and UMTS networks. Paging success rate = (1 Number of paging failures/ Number of paging requests) x 100%
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
[0, +) [0, +)
ms
Average delay of a paging process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a paging process by a VIP subscriber on the GSM and UMTS networks.
Numb er
SGSN-PDP Act
Parameter PDP Act Requests Rang e [0, +) Unit Numb er Description Number of PDP act process requests by a VIP subscriber on the GSM and UMTS networks. PDP act processes include: MS Init PDP Act CN Init PDP Act PDP Act Failures PDP Act Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of PDP act process failures by a VIP subscriber on the GSM and UMTS networks. PDP act process success rate by a VIP subscriber on the GSM and UMTS networks. PDP act success rate = (1 Number of PDP act failures/ Number of PDP act requests) x 100% USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1966
Unit ms
Description Average delay of a PDP act process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a PDP act process by a VIP subscriber on the GSM and UMTS networks.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Numb er
SGSN-PDP Act
Parameter PDP Sec Act Requests Rang e [0, +) Unit Numb er Description Number of PDP sec act process requests by a VIP subscriber on the GSM and UMTS networks. The PDP sec act process includes: MS Init PDP Sec Act PDP Sec Act Failures PDP Sec Act Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of PDP sec act process failures by a VIP subscriber on the GSM and UMTS networks. PDP sec act process success rate by a VIP subscriber on the GSM and UMTS networks. PDP sec act success rate = (1 Number of PDP sec act failures/ Number of PDP sec act requests) x 100% Average PDP Sec Act Delay Overlong PDP Sec Act Delays [0, +) [0, +) ms Average delay of a PDP sec act process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a PDP sec act process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Numb er
Issue 01 (2013-07-15)
1967
SGSN-PDP Mod
Parameter PDP Mod Requests Rang e [0, +) Unit Numb er Description Number of PDP mod process requests by a VIP subscriber on the GSM and UMTS networks. PDP mod processes include: MS Init PDP Mod CN Init PDP Mod PDP Mod Failures PDP Mod Success Rate [0, +) [0.00, 100.0 0] Numb er % Number of PDP mod process failures by a VIP subscriber on the GSM and UMTS networks. PDP mod process success rate by a VIP subscriber on the GSM and UMTS networks. PDP mod success rate = (1 Number of PDP mod failures/ Number of PDP mod requests) x 100% Average PDP Mod Delay Overlong PDP Mod Delays [0, +) [0, +) ms Average delay of a PDP mod process by a VIP subscriber on the GSM and UMTS networks. Number of delays that exceed the exception threshold of a PDP mod process by a VIP subscriber on the GSM and UMTS networks. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Numb er
SGSN-RAB Assignment
Parameter RAB Assignment Requests RAB Assignment Failures Rang e [0, +) [0, +) Unit Numb er Numb er Description Number of RAB Assignment requests of a VIP subscriber on the GSM/UMTS network Number of RAB assignment failures of a VIP subscriber on the GSM/UMTS network Supported NE Version USN9810 V900R012C00 or later version USN9810 V900R012C00 or later version
Issue 01 (2013-07-15)
1968
Unit %
Description RAB assignment success rate of a VIP subscriber on the GSM/ UMTS network RAB assignment success rate = (1 Number of RAB assignment failures/Number of RAB Assignment requests) x 100%
[0, +) [0, +)
ms
Average RAB assignment delay of a VIP subscriber on the GSM/ UMTS network Number of times that the RAB assignment delay of a VIP subscriber exceeds the predefined exception threshold on the GSM/UMTS network
Numb er
[0.00, 100.0 0]
Issue 01 (2013-07-15)
1969
Parameter Average PDN GW Dedicated Bearer Act Delay Overlong PDN GW Dedicated Bearer Act Delays
Ran ge [0, +)
Unit ms
Description Average PDN GW dedicated bearer activation delay of a VIP subscriber on the GSM/UMTS network 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
Supported NE Version USN9810 V900R012C00 or later version USN9810 V900R012C00 or later version
[0, +)
Numbe r
[0.00 , 100.0 0]
Issue 01 (2013-07-15)
1970
Ran ge [0, +)
Unit Numbe r
Description Number of times that the PDN GW initiated bearer modification delay of a VIP subscriber exceeds the predefined exception threshold on the GSM/UMTS network
MME-Attach
Parameter Attach Requests Ran ge [0, +) Unit Numbe r Description Number of attach process requests by a VIP subscriber on the LTE network. The attach process includes: Attach Attach Failures [0, +) [0.00 , 100.0 0] Numbe r % Number of attach process failures by a VIP subscriber on the LTE network. Attach process success rate by a VIP subscriber on the LTE network. Attach success rate = (1 Number of attach failures/ Number of attach requests) x 100% ms Average delay of an attach process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an attach process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Numbe r
Issue 01 (2013-07-15)
1971
MME-TAU
Parameter Intra TAU Requests Ran ge [0, +) Unit Numbe r Description Number of intra TAU process requests by a VIP subscriber on the LTE network. 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 Intra USN E-UTRAN to UTRAN Inter RAT RAU Intra TAU Failures Intra TAU Success Rate [0, +) [0.00 , 100.0 0] Numbe r % Number of intra TAU process failures by a VIP subscriber on the LTE network. Intra TAU process success rate by a VIP subscriber on the LTE network. Intra TAU success rate = (1 Number of intra TAU failures/ Number of intra TAU requests) x 100% ms Average delay of an intra TAU process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an intra TAU process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Numbe r
Issue 01 (2013-07-15)
1972
Ran ge [0, +)
Unit Numbe r
Description Number of inter TAU process requests by a VIP subscriber on the LTE network. 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
Numbe r %
Number of inter TAU process failures by a VIP subscriber on the LTE network. Inter TAU process success rate by a VIP subscriber on the LTE network. Inter TAU success rate = (1 Number of inter TAU failures/ Number of inter TAU requests) x 100%
[0, +) [0, +)
ms
Average delay of an inter TAU process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an inter TAU process by a VIP subscriber on the LTE network.
Numbe r
Issue 01 (2013-07-15)
1973
MME-Handover
Parameter Intra E-UTRAN Handover Requests Ran ge [0, +) Unit Numbe r Description Number of intra E-UTRAN handover process requests by a VIP subscriber on the LTE network. Intra E-UTRAN handover processes include: X2 Handover Intra MME S1 Handover Inter MME S1 Handover Intra E-UTRAN Handover Failures Intra E-UTRAN Handover Success Rate [0, +) Numbe r Number of intra E-UTRAN handover process failures by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0.00 , 100.0 0]
Success rate of an intra EUSN9810 UTRAN handover process by a V900R011C01 or VIP subscriber on the LTE later version network. Intra E-UTRAN handover success rate = (1 Number of intra E-UTRAN handover failures/Number of intra EUTRAN handover requests) x 100%
Average Intra EUTRAN Handover Delay Overlong Intra E-UTRAN Handover Delays
[0, +)
ms
Average delay of an intra EUSN9810 UTRAN handover process by a V900R011C01 or VIP subscriber on the LTE later version network. Number of delays that exceed the exception threshold of an intra E-UTRAN handover process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version
[0, +)
Numbe r
Issue 01 (2013-07-15)
1974
Ran ge [0, +)
Unit Numbe r
Description Number of inter RAT handover process requests by a VIP subscriber on the LTE network. Inter RAT handover processes include: Intra USN UTRAN Iu mode to E-UTRAN Inter RAT handover Inter USN UTRAN Iu mode to E-UTRAN Inter RAT handover Intra USN E-UTRAN to UTRAN Iu mode Inter RAT handover Inter USN E-UTRAN to UTRAN Iu mode Inter RAT handover
Numbe r %
Number of inter RAT handover process failures by a VIP subscriber on the LTE network. Success rate of an inter RAT handover process by a VIP subscriber on the LTE network. Inter RAT handover success rate = (1 Number of inter RAT handover failures/Number of inter RAT handover requests) x 100%
Average Inter RAT Handover Delay Overlong Inter RAT Handover Delays
[0, +) [0, +)
ms
Average delay of an inter RAT handover process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an inter RAT handover process by a VIP subscriber on the LTE network.
Numbe r
Issue 01 (2013-07-15)
1975
MME-Service Req
Parameter Service Req Requests Ran ge [0, +) Unit Number Description Number of service req process requests by a VIP subscriber on the LTE network. The service req process includes: Service Request Service Req Failures Service Req Success Rate [0, +) [0.00 , 100. 00] Number Number of service req process failures by a VIP subscriber on the LTE network. Service req process success rate by a VIP subscriber on the LTE network. Service req success rate = (1 Number of service req failures/ Number of service req requests) x 100% ms Average delay of a service req process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a service req process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Number
MME-Paging
Parameter Paging Requests Ran ge [0, +) Unit Numbe r Description Number of paging process requests by a VIP subscriber on the LTE network. The paging process includes: Paging. Paging Failures [0, +) Numbe r Number of paging process failures by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1976
Unit %
Description Paging process success rate by a VIP subscriber on the LTE network. Paging success rate = (1 Number of paging failures/ Number of paging requests) x 100%
[0, +) [0, +)
ms
Average delay of a paging process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a paging process by a VIP subscriber on the LTE network.
Numbe r
MME-Interoperation
Parameter Interoperation Requests Ran ge [0, +) Unit Numbe r Description Number of interoperation process requests by a VIP subscriber on the LTE network. Interoperation processes include: MME to 3G SGSN combined hard handover and SRNS relocation procedure 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure Interoperation Failures Interoperation Success Rate [0, +) [0.00 , 100. 00] Numbe r % Number of interoperation process failures by a VIP subscriber on the LTE network. Interoperation process success rate by a VIP subscriber on the LTE network. Interoperation success rate = (1 Number of interoperation failures/Number of interoperation requests) x 100% USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1977
Unit ms
Description Average delay of an interoperation process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of an interoperation process by a VIP subscriber on the LTE network.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Numbe r
Average Dedicated Bearer Act Delay Overlong Dedicated Bearer Act Delays
[0, +)
[0, +)
Numbe r
Issue 01 (2013-07-15)
1978
MME-Bearer Mod
Parameter Bearer Mod Requests Ran ge [0, +) Unit Numbe r Description Number of bearer mod process requests by a VIP subscriber on the LTE network. Bearer mod processes include: PDN GW initiated bearer modification with bearer QoS update HSS Initiated Subscribed QoS Modification PDN GW initiated bearer modification without bearer QoS update Bearer Mod Failures Bearer Mod Success Rate [0, +) [0.00 , 100. 00] Numbe r % Number of bearer mod process failures by a VIP subscriber on the LTE network. Bearer mod process success rate by a VIP subscriber on the LTE network. Bearer mod success rate = (1 Number of bearer mod failures/ Number of bearer mod requests) x 100% ms Average delay of a bearer mod process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a bearer mod process by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
[0, +) [0, +)
Numbe r
Issue 01 (2013-07-15)
1979
Average Bearer Resource Mod Delay Overlong Bearer Resource Mod Delays
[0, +) [0, +)
Numbe r
MME-PDN
Parameter PDN Connectivity Requests Ran ge [0, +) Unit Numbe r Description Number of PDN connectivity process requests by a VIP subscriber on the LTE network. The PDN connectivity process includes: UE requested PDN connectivity PDN Connectivity Failures [0, +) Numbe r Number of PDN connectivity process failures by a VIP subscriber on the LTE network. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1980
Unit %
Description PDN connectivity process success rate by a VIP subscriber on the LTE network. PDN connectivity success rate = (1 Number of PDN connectivity failures/Number of PDN connectivity requests) x 100%
[0, +) [0, +)
ms
Average delay of a PDN connectivity process by a VIP subscriber on the LTE network. Number of delays that exceed the exception threshold of a PDN connectivity process by a VIP subscriber on the LTE network.
Numbe r
GGSN-Create PDP
Parameter Create PDP Requests Create PDP Failures Create PDP Success Rate Ran ge [0, +) [0, +) [0.00 , 100. 00] Unit Numbe r Numbe r % Description Number of Create PDP procedures of a VIP subscriber on the GSM/UMTS network. Number of Create PDP failures of a VIP subscriber on the GSM/ UMTS network. Success rate of the Create PDP procedures of a VIP subscriber on the GSM/UMTS network. Create PDP Success Rate = (1 Number of Create PDP failures/ Number of Create PDP requests) x 100% Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
GGSN-Update PDP
Parameter Update PDP Requests Ran ge [0, +) Unit Numbe r Description Number of Update PDP procedures of a VIP subscriber on the GSM/UMTS network. Supported NE Version UGW9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1981
Unit Numbe r %
Description Number of Update PDP failures of a VIP subscriber on the GSM/ UMTS network. Success rate of the Update PDP procedures of a VIP subscriber on the GSM/UMTS network. Update PDP Success Rate = (1 Number of Update PDP failures/ Number of Update PDP requests) x 100%
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
SAE-GW-Modify Bearer
Parameter Create Session Requests Modify Bearer Requests Modify Bearer Failures Modify Bearer Success Rate Ran ge [0, +) [0, +) [0, +) [0.00 , 100. 00] Unit Numbe r Numbe r Numbe r % Description Number of Create Session procedures of a VIP subscriber on the LTE network. Number of Modify Bearer procedures of a VIP subscriber on the LTE network. Number of Modify Bearer failures of a VIP subscriber on the LTE network. Success rate of the Modify Bearer procedures of a VIP subscriber on the LTE network. Modify Bearer Success Rate = (1 Number of Modify Bearer failures/Number of Modify Bearer requests) x 100% Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
SAE-GW-Create Session
Parameter Create Session Failures Ran ge [0, +) Unit Numb er Description Number of Create Session failures of a VIP subscriber on the LTE network. Supported NE Version UGW9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1982
Unit %
Description Success rate of the Create Session procedures of a VIP subscriber on the LTE network. Create Session Success Rate = (1 Number of Create Session failures/Number of Create Session requests) x 100%
SAE-GW-Create Bearer
Parameter Create Bearer Requests Create Bearer Failures Create Bearer Success Rate Ran ge [0, +) [0, +) [0.00 , 100. 00] Unit Numb er Numb er % Description Number of Create Bearer procedures of a VIP subscriber on the LTE network. Number of Create Bearer failures of a VIP subscriber on the LTE network. Success rate of the Create Bearer procedures of a VIP subscriber on the LTE network. Create Bearer Success Rate = (1 Number of Create Bearer failures/ Number of Create Bearer requests) x 100% Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
SAE-GW-Update Bearer
Parameter Create Session Requests Create Session Failures Ran ge [0, +) [0, +) Unit Numbe r Numbe r Description Number of Create Session procedures of a VIP subscriber on the LTE network. Number of Create Session failures of a VIP subscriber on the LTE network. Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
Issue 01 (2013-07-15)
1983
Unit %
Description Success rate of the Create Session procedures of a VIP subscriber on the LTE network. Create Session Success Rate = (1 Number of Create Session failures/Number of Create Session requests) x 100%
[0, +)
Num ber
Issue 01 (2013-07-15)
1984
Unit %
Description Success rate of the Bearer Resource Command procedures of a VIP subscriber on the LTE network. Bearer Resource Command Success Rate = (1 Number of Bearer Resource Command failures/Number of Bearer Resource Command requests) x 100%
[0, +)
Numb er
[0.00 , 100.0 0]
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.
Function Description
The Nastar obtains the call event records of complaining subscribers, and then filters, aggregates, and analyzes data based on a specified history period and detailed call records of subscribers in a specified area. This can assist you in locating and solving problems. The complaint analysis support function consists of the aggregation and analysis of cause types in call reports of complaining subscribers, aggregation and analysis of information about call reports of complaining subscribers, analysis of detailed information about call reports of complaining subscribers, analysis of procedure before signaling release in call reports of complaining subscribers, analysis of active cells in call reports of complaining subscribers, and so on. The function supports the following analysis type: l l 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-16. Table 5-16 Function description of complaint analysis support Function Type Aggregation and analysis of cause types in call reports of complaining subscribers Description Helps network engineers filter and aggregate call reports based on exception causes. Supported Network GSM/ UMTS/ LTE/PS Core
Issue 01 (2013-07-15)
1986
Description 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, service duration, and so on. 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. 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. 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.
Analysis of procedure before signaling release in call reports of complaining subscribers Analysis of measurement reports (MRs) on calls of complaint subscribers before call release
GSM/ UMTS/LTE
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. Provides information about the serving cells of subscribers before call release and the neighboring cells. This helps engineers analyze and locate problems.
GSM
UMTS/LTE
Mobility analysis
Provides handover information of a terminal and helps network engineers to learn about all cells that are recorded in abnormal call records. Analyzes RAB-related counters and provides network quality information about a service. Geographically displays the cells to which complaining subscribers have gained access and the cells from which complaining subscribers have been released.
Issue 01 (2013-07-15)
1987
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.
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 UMTS network, if you want to view the comprehensive measurement report information, 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. 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.
Function Principles
Figure 5-27 shows the principles for collecting, importing, and analyzing data on the Nastar. For detailed operations, see Table 5-17.
NOTE
This section describes how the function is implemented when the Nastar is deployed using the direct networking scheme.
Issue 01 (2013-07-15)
1988
Table 5-17 Description of complaint analysis support User Oper ation 1. Subscr ibe to basic data Scen e GSM / UM TS netw ork Proce dure Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd
Issue 01 (2013-07-15)
Purpose
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. To issue an MML command to the M2000.
eSA U
M2000
M20 00
BSC/ RNC
To forward the MML command to the NE through the M2000, requesting the NE to generate raw data.
1989
Scen e
Purpose
Issue a basic data subscri ption comma nd Issue an MML comma nd Forwar d the MML comma nd Upload raw data
eSAU
To turn on the data source switch on the NE side. After a user enables the basic data subscription function (PS Core complaint analysis support) on the Nastar client, the Nastar issues a basic data subscription command to the eSAU. To issue an MML command to the M2000.
eSA U
M2000
M20 00
SGSN/ MME
To forward the MML command to the NE, requesting the NE to generate raw data.
PS SAU
Issue a basic data subscri ption comma nd Issue a subscri ption comma nd
eSAU
To turn on the data source switch on the NE side. After 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. To issue a subscription command to the M2000.
eSA U
M2000
Issue 01 (2013-07-15)
1990
Scen e
Proce dure Forwar d the subscri ption comma nd Upload raw data
Sour ce M20 00
Purpose
To forward the subscription command to the NE, requesting the NE to generate raw data.
eNod eB/ MM E
l To collect the data from Trace Server after 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 transmission switch is enabled.
Deliver a dataprepro cessing task (direct) Upload prepro cessed data (direct) Upload data analysi s results
Nasta r Serve r
To deliver a data-preprocessing request to the SAU/LTE SAU/PS SAU through the eSAU, requesting the SAU/LTE SAU/PS SAU to start the data-preprocessing task.
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. To display analysis results on the Nastar client.
Nastar Server
Item Execution type Network scale to be analyzed in a task Users to be analyzed in a task
Task Management Capacity One-time task No limited, for all RATs. l Analyzing with IMSI, <= 2,000 users, for all RATs. l Analyzing with MSISDN or peer MSISDN, <= 200 users, for all RATs. <= 500, for all RATs.
NOTE This specification is the sum of all complaint analysis support tasks. It has nothing to do with the number of licenses for complaint analysis support or with the RAT.
Issue 01 (2013-07-15)
1992
Table 5-18 Required license and rights of complaint analysis support Functio n Data subscript ion manage ment Required license Data subscription management Required rights (Security > Security Management > User) l Function operation rights Operation Rights > Operation > Nastar System Task Management > Data Subscription Management Authentication 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.
Issue 01 (2013-07-15)
1993
Required rights (Security > Security Management > User) l Function operation rights Operation Rights > Operation > Nastar Subject Management > GSM Complaint Analysis Support Operation Rights 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. 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.
CAUT ION If the analy zed IMSI or MSI SDN of comp lainin g user is the same as the VIP user in the VIP grou p mana geme nt funct ion, and you has not the opera tion rights to opera te the VIP user, you are not allow ed to creat e the comp laint analy sis supp ort task about the IMSI or MSI SDN.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > UMTS Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > LTE TDD Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > LTE FDD Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l Function operation rights Operation Rights > Operation > Nastar Subject Management > PS Core Complaint Analysis Support Operation Rights l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
l GSM / UMT
Issue 01 (2013-07-15)
1994
Functio n S comb ined comp laint analy sis supp ort l LTE FDD/ LTE TDD comb ined comp laint analy sis supp ort l RAN side (GS M/ UMT S/ LTE FDD/ LTE TDD ) and PS Core comb ined comp laint analy sis supp ort
Required license support, and UMTS complaint analysis support l LTE FDD complaint analysis support, and LTE TDD complaint analysis support l Complaint analysis support of analyzed network on the RAN side, and PS Core complaint analysis support
Required rights (Security > Security Management > User) Have both involved licenses of Complaint Analysis Support Operation Rights of combined analysis. l Operation rights of NEs and VIP groups to be analyzed is the same as the rights of GSM complaint analysis support.
Table 5-19 Required basic data of complaint analysis support Data Type Configur ation Data (Mandato ry) Function The configuration data of 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 which subscribers have gained access, cells which subscribers have released, and cells to which subscribers have handed over.
NOTE If you only perform the PS Core complaint analysis support, you do not need the configuration data.
Operation If the OSS information has been already configured, the Nastar automatically collects and imports the configuration data after the OSS and NE information is configured. You can also manually collect the configuration data before the specified time period starts. After the configuration data is imported, you can choose Maintenance > Data Maintenance Management to check whether the configuration data is available in the Nastar database. For detailed information about collecting, importing, and checking, see 2.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.
Issue 01 (2013-07-15)
1996
Function l Time The Nastar only analyzes complaints that occurred in the latest seven days. 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, MSISDN, or peer MSISDN IMSI: Supported by every network. MSISDN: Only supported by the PS Core network. Peer MSISDN: Only supported by the GSM network when choosing the CS service. You can obtain either the above information of a complaining subscriber for analysis when
Operation Enter the complaining subscriber information when creating complaint analysis support.
NOTE Generally, you obtain the IMSI and MSISDN of a VIP user and enter them into the Nastar. If telecom operators have high requirements for user information security and the anonymous policy is enabled on the network where the Nastar is deployed, all user information such as IMSI, MSISDN, and IMEI contained in the analysis data will be encrypted. To protect the security-sensitive user information, the Nastar no longer allows you to enter the plaintext IMSI and MSISDN. In this situation, you need to contact telecom operators to obtain the encrypted IMSI. The Nastar does not support the encrypted MSISDN. Telecom operators can visit http://support.huawei.com and choose Software Center > Controlled Tool(Mini-tool Software) > Core Network Product Line > Wireless-OSS > iManager M2000-II > HMACUtil to obtain the tool to encrypt user 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 2.11.2 Troubleshooting Problems Caused by Change of the Subscriber Identity Anonymization Switch or the Encryption Key. TIP If the number of complaining subscribers to be analyzed is large, you can save the IMSI, MSISDN or peer MSISDN information in the files in .xls/.xlsx/.csv format. The IMSI information stores a maximum of 2,000 records. Each IMSI must contain 15 digits. The MSISDN or peer MSISDN information stores a maximum of 200 records.
Issue 01 (2013-07-15)
1997
Data Type
Operation
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.
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.
The map file for a specific area displays the analysis result geographically. You do not need to prepare the map file if you do not want to view the analysis result on the map.
You can import the map files in WOR, TAB, or SXWU format to the Nastar. If the PC is connected to the Internet, you can view analysis results on the Google Earth. For details, see 2.4.4 Preparing the Map File (Optional).
Issue 01 (2013-07-15)
1998
Table 5-20 Description of the data source environment Net wor k GSM Description
l GSM RAN CS analysis : Check that the matching M2000 version is V200R011C00 (or later), and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l GSM RAN PS analysis: Check that the matching M2000 version is V200R012C00 (or later), and the NE version is BSC6900 V900R014C00 (or later), and BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On the User Identity Information Reporting Switch (GSM) in Nastar Commissioning Guide. l (Optional) Only calculating the counters related to speech quality, you need to manually turn on the switches for reporting uplink and downlink speech quality information in MR data. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Turning On the Switches for Reporting Speech Quality Information in MR Data (GSM Complaint Analysis Support, Optional) in Nastar Commissioning Guide. l (Optional) If you want to view the counters about the PS measurement information, check that the PS network control mode is set. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(GSM) > Setting the PS Network Control Mode in Nastar Commissioning Guide.
UM TS
l Check that the matching M2000 version is V200R011C00SPC220 or later and the NE version is BSC6900 V900R013C00 (or later) or BSC6910 V100R014C00 (or later). l Check that the user identity information (IMSI and IMEI) reporting switch has been turned on. For detailed operations, see Commissioning the Function of Obtaining the Data > Preparing for Obtaining Data > Preparing for Obtaining Data(UMTS) > Turning On the User Identity Information Reporting Switch (UMTS) in Nastar Commissioning Guide.
Issue 01 (2013-07-15)
1999
Description
l Check that the matching M2000 version is M2000 V200R012C00SPC200 or later, the NE version is LTE3900 V100R005C00SPC320 (or later) or LTE3900 V100R008C00SPC020 (or later), and the MME on the CN must be provided by Huawei and the version is USN9810 V900R011C01SPC300 or later.
NOTE 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 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. 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. 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. 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 M2000 versions are consistent with the following information: NE version: USN9810 V900R011C01, USN9810 V900R011C02, USN9810 V900R012C00; UGW9811 V900R009C01, UGW9811 V900R009C02, UGW9811 V900R010C00. M2000 version: M2000 V200R011C01, M2000 V200R012C01, M2000 V200R013C00.
Issue 01 (2013-07-15)
2000
Prerequisites
You have finished the preparation of complaint analysis support, such as checking the operation rights, preparing the basic data, and so on. For details, see 3.10.2 Preparations for Complaint Analysis Support.
Procedure
Figure 5-28 shows the process of complaint analysis support. For details, see Table 5-21. Figure 5-28 Flowchart for complaint analysis support
Issue 01 (2013-07-15)
2001
Table 5-21 Description of complaint analysis support procedures No. Proced ure Subscrib e to analysis data (basic) Description Reference for Detailed Operations 2.5 Subscribing to Analysis Data
(1)
NOTE The basic data subscription function has high security requirements. You are advised to contact the administrator who is authorized to subscribe to basic data to turn on the data switch.
Navigation path: Choose Maintenance > Data Subscription Management Procedure: 1. In the Data Subscription Management window, click *** tab. *** indicates the network. 2. In the left navigation tree, select the NEs to be configured. 3. On the Basic Subscription Settings tab page, click Set. 4. In the displayed Basic Subscription Settings dialog box, set complaint analysis support data to ON. l In the GSM network, the switch name is Complaint Analysis Support Data(CHR-CS), Complaint Analysis Support Data(CHR-PS), and Complaint Analysis Support Data(MRCS) for subscribing to the CHR-CS , CHR-PS data, and MR data of the GSM network. If you have obtained the MR data, you can view the comprehensive measurement report information, and assess business voice quality through VQI accurately. If not, you can only view a small number of measurement reports, and assess voice quality generally. l In the UMTS network, the switch name is Complaint Analysis Support Data(CHR) and Complaint Analysis Support Data(MR) for subscribing to the CHR data and MR data of the UMTS network. If you have obtained the MR data, you can view the comprehensive measurement report information. If not, you can only view a small number of measurement reports. 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 01 (2013-07-15)
2002
No.
Proced ure
Description
NOTE l The Nastar cannot issue all MML commands to network elements (NEs) by using the basic subscription function. To obtain data, confirm that you have manually issued the CHR enabled operation. For details, see 3.10.2 Preparations for Complaint Analysis Support. l Disable procedures (such as the Service Request procedure and the PDP MOD procedure) that involve all signaling information on the CN side. Otherwise, a large amount of data is collected from the CN and consequently the SGSN or MME cannot upload the data in time. As a result, certain data required by the Nastar is missing or delayed being reported.
l If you want to view the all signaling information, click , select the interface about All Signaling. 5. Click Confirm. Check that the data switch is successfully turned on by viewing the displayed information in the Log Info area.
Issue 01 (2013-07-15)
2003
No.
Description
Reference for Detailed Operations l For details, see 2.7 Creating an Analysis Task. l For details about the parameter s, see Analysis Task Paramete rs.
(2)
Navigation path: Choose Theme Function > User Assurance > Complaint Analysis Support in the navigation tree of the Analysis Task Management window. Procedure: 1. Double-click the Complaint Analysis Support node. 2. Set the task name and task remarks. Click Next. 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 MSISDN: Only supported by the PS Core network. l Peer MSISDN: Only supported by the GSM network when choosing the CS service. l You can obtain either the above information of a complaining subscriber for analysis when supporting multi information. 6. On the Set KPI Threshold tab page, set the abnormal threshold of each KPI. Click Next. 7. Choose an analysis time segment. The Nastar obtains the relevant analysis data in the time period. 8. Click Finish.
Issue 01 (2013-07-15)
2004
No.
Description
Reference for Detailed Operations l For details, see 2.8 Querying Analysis Results. l For details on the interface descriptio n, see 3.10.4 Referenc e for Complai nt Analysis Support Interface . l For details, see 2.10 Exportin g Analysis Reports. l For details on the interface descriptio n, see 3.10.4 Referenc e for Complai nt Analysis Support Interface .
(3)
Navigation path: In the upper right area of the Analysis Task Management window, select an analysis task in the Finish state. In the lower right of the Task Result area, select a result record of the task. Procedure: 1. Double-click an analysis result of the task. 2. In the displayed Complaint Analysis Support window, view the complaint analysis support results
(4)
Navigation path: Click the icon on the toolbar in the upper left part of each analysis results window. Procedure: 1. Click the export icon on the toolbar. 2. Specify the export path and export format. 3. Click Save.
Issue 01 (2013-07-15)
2005
Complaining subscriber information Parameter Set Analysi s Type Analysis Scene Description 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, for the combined complaint analysis support. 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.
Issue 01 (2013-07-15)
2006
Description Both access methods can be chosen. Set the data type on the RAN side. l RAN CS Data Access: Analyzes the CS service based on the CS-related data on the RAN side. The LTE network does not involve this parameter. l RAN PS Data Access: Analyzes the PS service based on the PS-related data on the RAN side. Both access methods can be chosen.
NOTE l If you set the analysis scene to PS Core, you do not need to set the data type, because it only supports the PS data on the PS Core. l For UMTS NEs, the CS and PS service information is recorded in one CHR. The SAU cannot filter CHRs by service type. Therefore, after a complaint analysis support task is created, all service information is displayed in the analysis results even though only the CS or PS is selected.
Data Type 2
The system supports the following data on the CS domain and the PS domain: Control Plane: analyze the service based on the control plane data on the RAN side and the CN side.
Select NE(s)
RAN NE
Click Select to select an NE. The lowest level is the base station controller level.
Issue 01 (2013-07-15)
2007
Description Add or import the user alias, the IMSIs, and remarks of complaining users.
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.
User 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 user 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 user. Value range: A 15-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, obtain the encrypted IMSI of a VIP user 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.
CAUTION If the input IMSI of complaining user is the same as the VIP user in the VIP group management 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.
MSISDN
Add or export MSISDNs of complaining users. l It is only supported by the PS Core network. l When the anonymous policy is disabled on the network where the Nastar is deployed, enter the MSISDN of a user. Value range: A 1- to 16-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, the Nastar does not support analyzing using the MSISDN.
CAUTION If the input MSISDN of complaining user is the same as the VIP user in the VIP group management 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 MSISDN.
Issue 01 (2013-07-15)
2008
Description Add or export peer MSISDNs of complaining users. l It is only supported by the GSM network when choosing the CS service. l When the anonymous policy is disabled on the network where the Nastar is deployed, enter the MSISDN of a user. Value range: A 1- to 16-digit numeric string composed of 0-9. l When the anonymous policy is enabled on the network where the Nastar is deployed, the Nastar does not support analyzing using the MSISDN.
CAUTION If the input peer MSISDN of complaining user is the same as the VIP user in the VIP group management 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 peer MSISDN.
Indicates the RAT of an NE. Indicates the domain of an NE. Domains include signaling planeCS, signaling plane-PS, signaling plane-integration. 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. 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.
Indicates the name of a KPI. Indicates the relationship between the KPI value and KPI 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 01 (2013-07-15)
2009
Parameter Date
Description 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 and the end time must precede the current system time.
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.
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. The value of this parameter must not precede the end time of Date.
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 5-29.
Issue 01 (2013-07-15)
2010
Issue 01 (2013-07-15)
2011
No.
Parame Description ter Button area Provides entries to three functions: l : Displays the complaint analysis support results geographically. For details, see Map Interface. l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview Table_Summary.file format. l : Exports data reports of complaint analysis support. The following two types of reports are exported. Each type has one report. The default format is .xlsx format. Information Table_Details_LTE.file format. The exported data includes information about overview tables, subscribers, accesses, releases, and handovers. Alternatively, right-click in area 3 and choose Export complaint analysis support reports to obtain this type of reports. Overview Table_Summary.file format. The same information with Overview Table_Summary.file format exported from summary reports of complaint analysis support.
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.
Issue 01 (2013-07-15)
2012
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. column header to resort this table.
Click the
NOTE 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 the Signaling Procedure Before Call re area Release Tab Page. Theme Displays detailed signaling process and MR information about all filtered analysis subscribers. The Nastar analyzes the mobility and service of all filtered area subscribers. For details, see Description of the MR Analysis Page, Description of the E-RAB Analysis Tab Page and Description of the Mobility Analysis Tab Page.
Displays detailed information about the selected subscriber in area 2, including user information, call access information, call release information. For details about parameters, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE). When the window is opened initially, the area hidden by default.
Issue 01 (2013-07-15)
2013
No. (1)
Description 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. 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). 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.
(2)
Signaling flowchart
Issue 01 (2013-07-15)
2014
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).
For details, see 3.10.7 Reference for Complaint Analysis Support Parameters (LTE).
Map Interface
Click . The map window (the Geographic Observation window) is displayed as shown in Figure 5-34.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2015
No. (1)
Description Entry for basic operations in the map window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
l Complaint Analysis Support: Node for the complaint analysis support theme. A level-2 node under the node indicates a task name. A level-3 node under the node indicates a KPI, such as access/ release cell KPI. If multiple complaint analysis support results windows are open, only one of the windows can be displayed on the map window simultaneously. If a analysis result window is closed, the node for the window in the navigation tree is deleted accordingly. In addition, the rendered layer of the corresponding theme is deleted. (3) Geographic observation area Analysis results are displayed as icons in different colors.
Issue 01 (2013-07-15)
2016
Description This area is empty for complaint analysis support. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the legends 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 is not imported, the system displays a message in this area.
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 5-35.
Issue 01 (2013-07-15)
2017
Issue 01 (2013-07-15)
2018
No.
Parame Description ter Button area Provides entries to three functions: l : Displays the complaint analysis support results geographically. For details, see Map Interface. l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview Table_Summary.file format. l : Exports data reports of complaint analysis support. 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 complaint analysis support reports 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 complaint analysis support reports to obtain this type of reports. Overview Table_Summary.file format. The same information with Overview Table_Summary.file format exported from summary reports of complaint analysis support.
Issue 01 (2013-07-15)
2019
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. 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. Click the column header to resort this table.
NOTE 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.
Issue 01 (2013-07-15)
2020
No.
Parame Description ter 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.
Displays detailed information about the selected subscriber in area 2, including user information, call access information, call release information. For details about parameters, see 3.10.5 Reference for Complaint Analysis Support Parameters (GSM). When the window is opened initially, the area hidden by default.
Issue 01 (2013-07-15)
2021
No. (1)
Description 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. (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). 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.
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.
Issue 01 (2013-07-15)
2022
No. (1)
Description Lists detailed MR information before call release. The information includes time, measurement object type, and detailed counter information.
(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, minimum, and mediate values. l Counter change trend chart, displaying the change of counter values for a maximum of 20 MRs l Legend Table 5-22 describes the change trend of each measurement counters.
Issue 01 (2013-07-15)
2023
Table 5-22 Description of measurement counter change trend chart Counter TA DLRxLevel DLRxQuality /Level Helps identify abnormal releases caused by uplink or downlink interference. Statistic Indication Helps identify abnormal releases caused by poor coverage. Description Displayed as a bar chart. The value ranges from 0 to 63. Displayed as a broken line graph. The value ranges from -47 to -110. 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. 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 Helps identify abnormal releases caused by unbalanced uplink and downlink by analyzing this KPI with DLRxQuality/Level and ULRxQuality/Level. Displays voice quality changes in the process, help evaluate the quality accurately. 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. UL VQI: displayed as a bar chart. The value ranges from 0 to 50. DL VQI: displayed as a broken line graph. The value ranges from 0 to 50.
ULRxQuality /Level
MS/BTS Power
VQI
For details about parameters, see 3.10.5 Reference for Complaint Analysis Support Parameters (GSM).
Map Interface
Click . The map window (the Geographic Observation window) is displayed as shown in Figure 5-39.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2024
No. (1)
Description Entry for basic operations in the map window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
l Complaint Analysis Support: Node for the complaint analysis support theme. A level-2 node under the node indicates a task name. A level-3 node under the node indicates a KPI, such as access/ release cell KPI. If multiple complaint analysis support results windows are open, only one of the windows can be displayed on the map window simultaneously. If a analysis result window is closed, the node for the window in the navigation tree is deleted accordingly. In addition, the rendered layer of the corresponding theme is deleted.
Issue 01 (2013-07-15)
2025
No. (3)
(4) (5)
This area is empty for complaint analysis support. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the legends 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 is not imported, the system displays a message in this area.
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 5-40.
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 01 (2013-07-15)
2026
Issue 01 (2013-07-15)
2027
No.
Parame Description ter Button area Provides entries to three functions: l : Displays the complaint analysis support results geographically. For details, see Map Interface. l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview Table_Summary.file format. l : Exports data reports of complaint analysis support. The following two types of reports are exported. Each type has one report. The default format is .xlsx format. Information Table_Details_UMTS.file format. The exported data includes information about overview tables, subscribers, accesses, releases, handovers, and so on. Alternatively, right-click in area 3 and choose Export complaint analysis support reports to obtain this type of reports. Overview Table_Summary.file format. The same information with Overview Table_Summary.file format exported from summary reports of complaint analysis support. l provides the abnormal cause statistics function of the service. For details, see Common Statistics Interface.
Issue 01 (2013-07-15)
2028
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. 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-RNC call history records. If an interRNC 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. Click the column header to resort this table.
NOTE 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 the Signaling Procedure Before Call re area Release Tab Page.
Issue 01 (2013-07-15)
2029
No.
Parame Description ter Theme Displays detailed signaling process and MR information about all filtered analysis subscribers. The Nastar analyzes the mobility and service of those area subscribers. For details, see Description of the Measurement Information Before Call Release Tab Page, Description of Mobility Analysis Tab Page, and Description of Service Analysis Tab Page.
Displays detailed information about the selected subscriber in area 2, including user information, call access information, call release information, and statistical information. For details about parameters, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS). When the window is opened initially, the area hidden by default.
Issue 01 (2013-07-15)
2030
No. (1)
Description 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 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.
(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). 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.
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.
Issue 01 (2013-07-15)
2031
No. (1)
Description Lists detailed MR information before call release. The information includes time, measurement object type, and detailed counter information.
(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, minimum, and mediate values. l Counter change trend chart, displaying the change of counter values for a maximum of 20 MRs l Legend Table 5-23 describes the change trend of each measurement counters.
Issue 01 (2013-07-15)
2032
Table 5-23 Description of measurement counter change trend chart Counter Ec/No Statistic Indication Indicates the change trend of the signal intensity according to the received cells of the UE. Indicates the change trend of the signal level according to the received cells of the UE. Indicates the change trend of the RSSI according to the received intercells of the UE. Indicates the change trend of the RSRP according to the received LTE cells of the UE. Indicates the change trend of the RSRQ according to the received inter-cells of the UE. Indicates the change trend of the transmit power of the UE. Description Displayed as a broken line chart.
RSCP
RSSI
RSRP
RSRQ
UE Tx Power
For details, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS).
Figure 5-44 shows the items about the RAB service through the RAB analysis.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2033
Double-click one result, or right-click one result, and choose Detail Service Information, view the detailed service counters of CS domain or PS domain. Right-click one result, and choose Trend Analysis, view the throughput and throughput rate of the RAB on the uplink and downlink at the different time. For details, see 3.10.6 Reference for Complaint Analysis Support Parameters (UMTS). Figure 5-44 Description of service analysis tab page (RAB)
Map Interface
. The map window (the Geographic Observation window) is displayed as shown in Click Figure 5-45. Figure 5-45 Map interface
Issue 01 (2013-07-15)
2034
No. (1)
Description Entry for basic operations in the map window. For details about the icons, see 2.2.3 Interface Description: Geographic Observation Results. 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.
TIP If you need to delete all sites in a network system, click Remove through the layer management function.
(2)
l Complaint Analysis Support: Node for the complaint analysis support theme. A level-2 node under the node indicates a task name. A level-3 node under the node indicates a KPI, such as access/ release cell KPI. If multiple complaint analysis support results windows are open, only one of the windows can be displayed on the map window simultaneously. If a analysis result window is closed, the node for the window in the navigation tree is deleted accordingly. In addition, the rendered layer of the corresponding theme is deleted. (3) Geographic observation area Grid detail area Legend area Analysis results are displayed as icons in different colors.
(4) (5)
This area is empty for complaint analysis support. This area is not displayed by default. It is displayed only after you click the icon in the button area. After you click the icon, this area displays the legend information about the legends 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 is not imported, the system displays a message in this area.
Issue 01 (2013-07-15)
2035
Navigation Path
Use either of the following methods to open the interface that displays PS core complaint analysis support results: l l Select a finished PS core 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 Result from the shortcut menu.
Interface
PS core complaint analysis support results can be displayed in tables to show CHR summary information, CHR information, subscriber information, and procedure information, as shown in Figure 5-46. Figure 5-46 Interface for PS core complaint analysis support results
Issue 01 (2013-07-15)
2036
No. 1
Description Provides entries to three functions: l : Exports summary reports of complaint analysis support. The following three types of reports are exported. Each type has one report. The default format is .xlsx format. The first type of reports lists the statistics result when the summary mode is User ID: Alias-Cause type in the summary navigation tree. The naming convention is Overview tree_User ID: Alias-Cause type.file format. The second type of reports lists the statistics result when the summary mode is Cause type-User ID: Alias in the overview tree. The naming convention is Overview tree_Cause type-User ID: Alias.file format. The third type of reports lists the summary result of overview information of complaint analysis support. The naming convention is Overview table_Summary.file format. l : Exports data reports of complaint analysis support. The exported data includes information about overview tables, subscribers, call accesses, call releases, and call handovers. Alternatively, right-click in area 3 and choose Export complaint analysis support reports to obtain this type of reports. l provides the traffic statistics function. For details, see Traffic Statistics on the Interface.
Navigati l Upper part: Displays the service types. You can select the service types. on tree l Middle part: Call records of multiple subscribers are displayed by cause of the type in the navigation tree mode. (N) after each node indicates the number CHR 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. summar In Cause type-User ID: Alias mode, all filtered call records are y of classified by cause type and the call records of each cause type are complai then classified by User ID: Alias. ning 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.
Issue 01 (2013-07-15)
2037
No. 3
Description Displays an overview of all filtered records, such as time, cell, procedure, and exception cause. Each row indicates one call record. row is abnormal. Click the indicates that the call record in the
NOTE For some columns (such as User ID: Alias), the system only centralized display the same content, but there is no display order after resorting.
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 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 3.10.8 Reference for Complaint Analysis Support Parameters (PS Core). The table is hidden by default when you initially open the window.
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 GGSN Procedure or SAE-GW Procedure under Service Type. Traffic subnodes are displayed under Root. 2. Select a Traffic subnode to view traffic information by subscriber.
Function Description
The Nastar allows you to perform complaint analysis support based on the data collected from different types of networks simultaneously. For example, it allows you to perform GSM/UMTS complaint analysis support and LTE FDD/LTE TDD complaint analysis support. It also allows you to perform complaint analysis support based on the data collected from the RAN and the PS core network simultaneously. Therefore, the Nastar supports combined complaint analysis support in the following combinations of RATs: GSM/UMTS, LTE FDD/LTE TDD, GSM/PS Core, UMTS/PS Core, LTE TDD/PS Core, LTE FDD/PS Core, GSM/UMTS/PS Core, and LTE FDD/LTE TDD/PS Core.
Navigation Path
Use either of the following methods to open the interface that displays combined complaint analysis support results: l 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 Result from the shortcut menu.
Interface description
The interface that displays the combined complaint analysis support results of multiple RATs is generally the same as the interface that displays the complaint analysis support results of a single RAT: l The service types displayed in the navigation tree are combinations of the service types for the complaint analysis support of involved RATs. For example, if the service types for GSM complaint analysis support include RAN CS (Call\SMS\others) and the service types for UMTS complaint analysis support include RAN NET, RAN CS (AMR\VP\SMS\others)), RAN PS, and RAN Multi, the service types for GSM/UMTS complaint analysis support include RAN NET, RAN CS (AMR\VP\Call \SMS\others), RAN PS, and RAN Multi. l The cause types displayed in the navigation tree are combinations of the cause types for the complaint analysis support of involved RATs. The description of the exception causes for each RAT provides the mapping between service types and cause types. For details, see 3.10.9 Appendix: Exception Cause Classification / Key Signaling. l The information displayed in the middle and right areas on the interface varies according to the call history record (CHR) that you select in the navigation tree. One CHR belongs to only one RAT. Therefore, for descriptions of related interfaces and parameters, see the interface reference for the complaint analysis support of each RAT.
Issue 01 (2013-07-15)
2039
Summary
Parame ter Serial Number Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Status
N/A
N/A
Whether a call record is abnormal. If a red exclamation mark is displayed in this column, the call record is abnormal.
Abnorm al 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. Network technology type.
Network
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access Type
Intra-RAT RRC Access Incoming HO/ Intra-RAT Incoming HO Incoming HO/ UTRAN Incoming HO Incoming HO/ GERAN Incoming HO
N/A
Access Time
N/A
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access Cell
N/A
N/A
Cell that a UE accesses at the beginning of a call. The parameter value is displayed in the following format: eNodeB name:cell name (eNodeB ID:cell ID).
Issue 01 (2013-07-15)
2040
Range
Unit
Description
Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Release Cell
N/A
N/A
Cell from which a UE is released at the end of a call. The parameter value is in the following format: eNodeB name:cell name (eNodeB ID:cell ID).
User ID:Alias
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
IMEITAC
00000000-99999 999
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.
Termina l Model
N/A
N/A
Model of a UE.
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Duratio n
[0,+)
Second
Duration of a call, which is displayed in the format of hh:mm:ss.nnn. Call duration = Release time Access time.
User Information
Parameter Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version
User ID:Alias
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
Issue 01 (2013-07-15)
2041
Parameter
Range
Unit
Description
STMSI
MMEC Range:BIT STRING (SIZE (8)) m-TMSI Range: BIT STRING (SIZE (32))
bit
S-temporary mobile subscriber identity (S-TMSI) of a subscriber. The parameter display is in the following format: MMEC:mTMSI. For more information please see 3GPP 36.331 6.3.6 S-TIMSI
[0,2^32-1]
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
[0,2^32-1]
N/A
IMEI-TAC
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.
Terminal Model
N/A
N/A
Model of a UE.
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
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. RATs supported by a UE.
>Support RAT
N/A
N/A
Issue 01 (2013-07-15)
2042
Parameter
Range
Unit
Description
N/A
>Device Type
N/A
Whether a UE supports battery consumption optimization. If the parameter is zero, it indicates that the device can foresee to particularly benefit from NWbased 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.
>Category Class
N/A
>>Uplink Physical Layer Parameter >>>Maxim um Number of UL-SCH Transport Block Bits Transmitte d Within A TTI
N/A
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
2043
Parameter
Range
Unit
Description
>>>Maxim um Number of Bits of an UL-SCH Transport Block Transmitte d Within A TTI >>>Suppor t for 64QAM In UL >>Downlin k Physical Layer Parameter >>>Maxim um Number of DL-SCH Transport Block Bits Received Within A TTI >>>Maxim um Number of Bits of a DL-SCH Transport Block Received Within A TTI >>>Suppor t for 64QAM In DL
N/A
N/A
Yes No
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
Yes No
N/A
Issue 01 (2013-07-15)
2044
Access Information
Parameter Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access Time
N/A
N/A
Access Cell
N/A
N/A
Cell that a UE accesses at the beginning of a call. The parameter value is in the following format: eNodeB name: cell name ( eNodeB ID:cell ID).
Access TA
[0,1314]
16*Ts=0.5 2 ms
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Access UL RSRP
[-140,-43]
dBm
Reference signal received power (RSRP) on the uplink during the access of a call. SINR on the uplink during the access of a call.
Access UL SINR
[-15,35]
dB
Access Type
RRC Access Incoming HO/ Intra-eNodeB Incoming HO Incoming HO/ UTRAN Incoming HO Incoming HO/ GERAN Incoming HO
N/A
Issue 01 (2013-07-15)
2045
Parameter
Range
Unit
Description
Access Cause
N/A
N/A
N/A
LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
The delay time between the time of access request and the time of access completion.
Release Information
Parameter Range Unit Description Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Release Time
N/A
N/A
Release Cell
N/A
N/A
Cell from which a UE is released at the end of a call. The parameter value is in the following format: eNodeB name : cell name (eNodeB ID:cell ID).
N/A
Issue 01 (2013-07-15)
2046
Parameter
Range
Unit
Description
Supporte d NE Version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
N/A
N/A
Handover based on the distance Handover based on the coverage Handover based on the load balancing
N/A
No.
[0,+)
N/A
Number that uniquely identifies a LTE 3900 sent and received signaling message. V100R005 C00 or later version Time when a signaling message is sent or received. LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version LTE 3900 V100R005 C00 or later version
Signaling Time
N/A
N/A
Signaling Direct
Uplink Downlin k
N/A
Signaling Type
N/A
N/A
Type of a signaling message that complies with any protocol and is transmitted over the S1-MME or Uu interface. For example, RRC CONNECT REQUEST is a signaling type.
Signaling Context
N/A
N/A
Issue 01 (2013-07-15)
2047
MR Time
N/A
N/A
N/A
MR Object Type
N/A
Eutran Cell ID
[0,255]
N/A
LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version
PCI
[0,503]
N/A
RSRP
[-140,-43]
dBm
RSRQ
[-19.5,-2.5]
dB
RSCP
[-115,-25]
dBm
RSCP of a neighboring cell when the measurement type is inter-RAT and the RAT is UTRAN in an MR.
Issue 01 (2013-07-15)
2048
Parameter EcNo
Range [-24,0]
Unit dB
Description Ec/No of a neighboring cell when the measurement type is inter-RAT and the RAT is UTRAN in an MR. Network color code (NCC) of a neighboring cell when the measurement type is interRAT and the RAT is GERAN in an MR. Base station color code (BCC) of a neighboring cell when the measurement type is inter-RAT and the RAT is GERAN in an MR. ARFCN of a neighboring cell when the measurement type is inter-RAT and the RAT is GERAN in an MR. Frequency band indicator of a neighboring cell when the measurement type is interRAT and the RAT is GERAN in an MR. RSSI of a neighboring cell when the measurement type is inter-RAT and the RAT is GERAN in an MR. Pilot signal phase of a neighboring cell when the measurement type is interRAT and the RAT is CDMA2000 in an MR. Pilot signal strength of a neighboring cell when the measurement type is interRAT and the RAT is CDMA2000 in an MR.
Supported NE Version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version LTE 3900 V100R005C0 0 or later version
[0,7]
N/A
[0,7]
N/A
ARFCN
[0,1023]
N/A
DCS1800 PCS1900
N/A
RSSI
[-110,-48]
dBm
[0,32767]
chip
[-29,33]
dBm
Issue 01 (2013-07-15)
2049
Abnormal
! Blank
N/A
Issue 01 (2013-07-15)
2050
Range The handover interface types of intraRAT handover are the following: intra-eNodeB handover handover based on the X2 interface; handover based on the S1 interface. The handover interface types of interRAT handover are the following: handover based on the S1 interface.
Unit N/A
N/A
Preparation time for initiating an incoming or outgoing intra-RAT or inter-RAT handover during a call. Interval = Start time - End time.
Interval
[0,+)
Issue 01 (2013-07-15)
2051
Range Yes No
Unit N/A
Description If the interval exceeds the overlong xxx delay threshold, the value of this parameter is Yes. Otherwise, the value of this parameter is No. The overlong xxx delay threshold is set by engineers during task creation. The threshold types are as follows: Overlong intra-RAT outgoing handover delay threshold; Overlong inter-RAT outgoing handover delay threshold; Overlong intra-RAT incoming handover delay threshold.
End Time
N/A
N/A
End time.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
Source Cell
N/A
N/A
Source cell from which a call is handed over. The parameter value is in the following format: eNodeB name : cell name (eNodeB ID:cell ID).
UL RSRP upon Handover UL SINR upon Handover Target Cell for Handover
[-140,-43]
dBm
RSRP of the serving cell on the uplink during the handover of a call.
[-15,35]
dB
SINR of the serving cell on LTE 3900 the uplink during the V100R005C00 handover of a call. or later version Target cell to which a call is handed over. The parameter value is in the following format: eNodeB name: cell name (eNodeB ID:cell ID). LTE 3900 V100R005C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
2052
Parameter Target Cell UL RSRP After Handover Target Cell UL SINR After Handover Handover Triggering Cause
Range [-140,-43]
Unit dBm
Description RSRP of the serving cell on the uplink during the handover of a call.
[-15,35]
dB
SINR of the serving cell on LTE 3900 the uplink during the V100R005C00 handover of a call. or later version Triggering cause of an outgoing handover during a call. The triggering cause of an incoming handover is empty. LTE 3900 V100R005C00 or later version
Handover based on the distance Handover based on the coverage Handover based on the load balancing
N/A
Radio Network Layer Transport Layer NAS Layer Protocol Layer Miscellaneou s
N/A
Triggering cause of the preparation of an outgoing handover during a call. The preparation triggering cause of an incoming handover is empty.
Issue 01 (2013-07-15)
2053
Range Handover preparation to target cell failure 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
Unit N/A
Description Cause of a failed outgoing handover during a call. The cause of a failed incoming handover is empty.
Cancel Handover
Yes No
N/A
Whether the HANDOVER CANCEL message is received during the handover of a call. Handover result of a call, including the handover preparation result and handover execution result.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
Handover Result
N/A
Handover TA
[0,1314]
16*Ts =0.52 ms
Issue 01 (2013-07-15)
2054
Range [-140,-43]
Unit dBm
Description Reference signal received power (RSRP) on the UL during the handover of a call. SINR on the UL during the handover of a call. ID of the E-RAB and QCI that is handed over. ID of the E-RAB that is handed over. Service type for which ERAB is handed over. The parameter values are as follows: 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. Non GBR (QCIN): nonGBR service with low QoS. N = 5, 6, 7, 8, or 9.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[-15,35]
dB
N/A
N/A
[0,15]
N/A
E-RAB QCI
GBR(QCI1) GBR(QCI2) GBR(QCI3) GBR(QCI4) Non GBR (QCI5) Non GBR (QCI6) Non GBR (QCI7) Non GBR (QCI8) Non GBR (QCI9)
N/A
E-RAB Analysis
Parameter No. Range [1,+) Unit N/A Description Serial number of an ERAB ID. It uniquely identifies an E-RAB ID. Setup result of an E-RAB setup request. Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
! Blank
N/A
Issue 01 (2013-07-15)
2055
Range Radio Network Layer Transport Layer NAS Layer Protocol Layer Miscellaneous
Unit N/A
Description Cause of failed E-RAB setup. The parameter value also includes detailed causes.
GBR(QCI1) GBR(QCI2) GBR(QCI3) GBR(QCI4) Non GBR (QCI5) Non GBR (QCI6) Non GBR (QCI7) Non GBR (QCI8) Non GBR (QCI9)
N/A
QCI level on E-RAB setup. The parameter values are as follows: GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
E-RAB Request Time Cell on E-RAB Request E-RAB Setup Time TA on E-RAB Setup
N/A
N/A
Time when E-RAB is requested. Cell when E-RAB is requested. Time of RAB setup.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
2056
N/A
N/A
N/A
N/A
[0,1314]
[-140,-43]
Reference signal received power (RSRP) on the uplink during the E-RAB setup of a call. SINR on the uplink during the E-RAB setup of a call.
[-15,35]
dB
Issue 01 (2013-07-15)
Range ! Blank E-RAB abnormal release triggered by MME E-RAB abnormal release triggered by eNodeB E-RAB abnormal release triggered by outgoing HO execution failure
Unit N/A
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
Yes No
N/A
Identifier indicating whether data is being transmitted when an ERAB is released. If no data is being transmitted when the ERAB is released, the subscriber cannot perceive the exception.
N/A
QCI level on E-RAB release. GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
N/A
N/A
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
2057
Range [0,1314]
Description Time advance (TA) during the E-RAB release of a call. Reference signal received power (RSRP) on the uplink during the E-RAB release of a call. SINR on the uplink during the E-RAB release of a call. End where an E-RAB is released. End where an E-RAB is released.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[-140,-43]
[-15,35]
dB
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2058
Range GBR(QCI1) GBR(QCI2) GBR(QCI3) GBR(QCI4) Non GBR (QCI5) Non GBR (QCI6) Non GBR (QCI7) Non GBR (QCI8) Non GBR (QCI9)
Unit N/A
Description QCI level on E-RAB setup. The parameter values are as follows: GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
>E-RAB Request Time >Cell on ERAB Request >E-RAB Setup Time >E-RAB Setup Result >E-RAB Setup Cause
N/A
N/A
Time when E-RAB is requested. Cell when E-RAB is requested. Time of RAB setup.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
N/A
N/A
N/A
Succeed Failure Radio Network Layer Transport Layer NAS Layer Protocol Layer Miscellaneou s
N/A
Setup result of an E-RAB setup request. Cause of E-RAB setup. The parameter value also includes detailed causes.
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2059
Range [0,+)
Unit Seco nd
Description E-RAB setup delay = Time when E-RAB setup completes - Time when ERAB setup is requested. MR information during the ERAB setup of a call. Time advance (TA) during the E-RAB setup of a call. Reference signal received power (RSRP) on the uplink during the E-RAB setup of a call. SINR on the uplink during the E-RAB setup of a call. Priority information of an ERAB. Priority of a setup E-RAB.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
N/A
N/A
[0,1314]
>>UL RSRP
[-140,-43]
>>UL SINR
[-15,35]
dB
N/A
N/A
N/A
N/A
>>E-RAB Passive Preemptability >E-RAB Rate Information >>Maximum ERAB DL Rate >>Assured ERAB DL Rate
N/A
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
2060
N/A
Rate information of an ERAB. Maximum downlink rate of a setup E-RAB. Assured downlink rate of a setup E-RAB.
kbps
kbps
Issue 01 (2013-07-15)
Parameter >>Maximum ERAB UL Rate >>Assured ERAB UL Rate E-RAB Release Information >E-RAB Request Service Type(QCI) on E-RAB Release
Unit kbps
Description Maximum uplink rate of a setup E-RAB. Assured uplink rate of a setup E-RAB. The information during the ERAB release of a call. QCI level on E-RAB release. GBR (QCIN): GBR service with high QoS. N = 1, 2, 3, 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.
Supported NE Version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
kbps
N/A
N/A
N/A
N/A
Time when an E-RAB is released. E-RAB duration = Time when E-RAB is released Time when E-RAB setup completes Cell from which an E-RAB is released.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,+)
Seco nd
N/A
N/A
Issue 01 (2013-07-15)
2061
Range E-RAB abnormal release triggered by MME E-RAB abnormal release triggered by eNodeB E-RAB abnormal release triggered by outgoing HO execution failure
Unit N/A
N/A
End where an E-RAB is released. Identifier indicating whether data is being transmitted when an E-RAB is released. If no data is being transmitted when the E-RAB is released, the subscriber cannot perceive the exception.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C01 or later version
N/A
N/A
N/A
MR information during the ERAB release of a call. Time advance (TA) during the E-RAB release of a call. Reference signal received power (RSRP) on the uplink during the E-RAB release of a call. SINR on the uplink during the E-RAB release of a call.
LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version LTE 3900 V100R005C00 or later version
[0,1314]
>>UL RSRP
[-140,-43]
>>UL SINR
[-15,35]
dB
Issue 01 (2013-07-15)
2062
Summary
Para mete r Serial Num ber Range Uni t N/A Description Supported NE Version BSC6900 V900R013C00 or later version
(0,2^31-1)
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. 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.
Comb ined
N/A
N/A
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.
For details, see "Appendix: Exception Cause Classification / Key Signaling (GSM)".
N/A
Cause of the exception carried in an Access Request message. Note: The HQIs after the call setup is successful are only counted in the abnormal cause.
Issue 01 (2013-07-15)
2063
Range
Uni t N/A
Description
GSM-CS, GSM-PS
Issue 01 (2013-07-15)
2064
Range
Uni t N/A
Description
Non-SMS message from a mobile-originated VIP subscriber (AC_ORIGIN_CALL_N O_SMS) SMS message from a mobile-originated VIP 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) 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) Incoming inter-BSC handover (AC_IN_BSC_HO)
Issue 01 (2013-07-15)
2065
Para mete r
Range
Uni t
Description
Supported NE Version
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 ) Non-SMS message from a mobile-terminated VIP subscriber (AC_ANSWER_TO_PA GING_CALL) SMS message from a mobile-terminated VIP subscriber (AC_ANSWER_TO_PA GING_CALL) Normal location update (AC_LOCATION_UPD ATE_NORMAL) Periodic location update (AC_LOCATION_UPD ATE_PERIODIC) IMSI attachment (AC_LOCATION_UPD ATE_ATTACH) Acces s Time N/A N/A Signaling access time for a call, namely, the time when a MS sends the Channel Request message. BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
2066
Range
Uni t N/A
Description
N/A
Name of the cell in which a MS sends the Channel Request message. 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. In the preceding format, BSC OPC is the originating signaling point configured on the BSC side.
Relea se Time
N/A
N/A
Signaling release time for a call, namely, the time when a MS receives the Channel Release message.
Relea se Cell
N/A
N/A
Name of the cell in which a MS receives the Channel Release message. 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.
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
Issue 01 (2013-07-15)
2067
Range
Uni t N/A
Description
00000000-99999999
International mobile equipment identity-type allocation code (IMSI-TAC) of a VIP subscriber, which is the first eight digits in the IMEI of a UE. Type of a MS. You can obtain the IMEITACs of the UE from the MS type management function.
Mode l
N/A
N/A
N/A
N/A
Mobile station international ISDN number (MSISDN) of a peer subscriber. Service duration covering the call duration and the signaling setup duration. Service duration = Release time - Access time
[0,+)
Sec ond
[0,+)
Sec ond
Call duration. Call duration = Time stamp of the Disconnect message Time stamp of the Connect Acknowledge message
Issue 01 (2013-07-15)
2068
Range
Uni t N/A
Description
Following are criteria indicating a proper call setup: 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. 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. 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.
Network access result for a mobile-originated call. The result indicates a proper call setup or an abnormal call setup. 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.)
Issue 01 (2013-07-15)
2069
Para mete r
Range
Uni t
Description
Supported NE Version
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 Following are criteria indicating a proper call release: 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 inter-RAT handover is triggered and completed. Following are criteria indicating an abnormal release of traffic channel during a call: 1. An outgoing inter-BSC handover fails. 2. An intra-BSC handover fails. 3. The BSC releases channel resources. 4. The MSC releases channel resources. N/A Network release result for a mobile-originated call. The result indicates a proper call release or an abnormal call release. BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
2070
User Information
Parame ter User ID:Alias IMEITAC Model Range N/A Unit N/A Description Refer to "User ID:Alias" in the Summary area. Refer to "IMEI-TAC" in the Summary area. Refer to "Model" in the Summary area. Capability of the MS. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Yes No
N/A
Yes No
N/A
Yes No
N/A
Whether a MS supports the VAMOS. VAMOS, voice services over adaptive multi-user channels on one slot.
Yes No
N/A
Whether a MS supports the U900. That is, whether a MS supports accessing to the 3G network using the 900 MHz/ 850 MHz band of the 2G network.
Peer MSISD N
N/A
N/A
Issue 01 (2013-07-15)
2071
N/A
N/A
[0,71]
N/A
Access Channel
[0,7]
N/A
Access Type
N/A
N/A
MOC MTC
N/A
According to the access causes to identify the user's current business is accessed by MTC or MOC. According to the access causes to identify the user's current business is accessed by SMS or Voice. Network access result for a mobile-originated call. 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.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
SMS Voice
N/A
N/A
N/A
Issue 01 (2013-07-15)
2072
Range N/A
Unit N/A
Description 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.
N/A
N/A
Detailed cause of an abnormal signaling access for a call. See the level-3 cause, Sub-Cause of Abnormal Call Setup, in Call Setup Result/Cause of Abnormal Call Setup/Sub-Cause of Abnormal Call Setup in General Evaluation.
Access Delay Estimati on >ASSIG NMENT COMPL ETE Message Timesta mp >Access Delay
N/A
N/A
N/A
N/A
Time when the assignment is finished after initiating a call and accessing the network.
[0,+)
Secon d
Access delay time of the service. Access Delay = Time of ASSIGNMENT COMPLETE Time of CHANNEL REQUEST ="ASSIGNMENT COMPLETE Message Timestamp"-"Access Time"
Yes No
N/A
Whether the abnormal of overlong access delay is occurred. The abnormal threshold is set when creating tasks.
>Alertin g Time
N/A
N/A
Time when a VIP subscriber hears the alerting after initiating a call.
Issue 01 (2013-07-15)
2073
Parame ter >Call Complet ion Delay (Alertin g) >Overlo ng Call Complet ion Delay (Alertin g) >Connec t Acknow ledge Time >Call Complet ion Delay (Connec t Ack)
Range [0,+)
Unit Secon d
Description Call completion delay time of the service. Call Completion Delay(Alerting) = Time of ALERTING - Time of CHANNEL REQUEST =Alerting Time - Access Time
Yes No
N/A
Whether the abnormal of overlong call completion delay (Alerting) is occurred. The abnormal threshold is set when creating tasks.
N/A
N/A
Time when a VIP subscriber hears the voice of the peer subscriber after initiating a call.
[0,+)
Secon d
Call completion delay time of the service. Call Completion Delay(Connect Ack) = Time of CONNECK ACK - Time of CHANNEL REQUES REQUEST =Connect Acknowledge Time Access Time
>Overlo ng Call Complet ion Delay (Connec t Ack) Measure ment Informat ion On Access >TA
Yes No
N/A
Whether the abnormal of overlong call completion delay (Connect Ack) is occurred. The abnormal threshold is set when creating tasks.
N/A
N/A
[0,63]
N/A
Issue 01 (2013-07-15)
2074
Range Yes No
Unit N/A
Description Whether the abnormal that TA is too large when accessing to the network is occurred. The abnormal threshold is set when creating tasks.
[-110,-47]
dBm
Value of the RACH level when a MS accesses to the network. Whether the abnormal that RACH Level is too small is occurred. The abnormal threshold is set when creating tasks.
Yes No
N/A
[0,+)
Secon d N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2075
Range N/A
Unit N/A
Description Cause of an abnormal signaling release during a call. See the level-2 cause, Cause of Abnormal Call Release, in Call Release Result/Cause of Abnormal Call Release/SubCause of Abnormal Call Release in General Evaluation.
N/A
N/A
Detailed cause of an abnormal signaling release during a call. See the level-3 cause, Sub-Cause of Abnormal Call Release, in Call Release Result/Cause of Abnormal Call Release/SubCause of Abnormal Call Release in General Evaluation.
CS Service Information
Parame ter Service Process Delay Estimati on >IntraBSC Channel Release Timesta mp >Calling Duration Range N/A Unit N/A Description Delay estimation for service process. Supported NE Version BSC6900 V900R013C00 or later version
N/A
N/A
[0,+)
Secon d
Calling Duration = Time of DISCONNECT - Time of CONNECT ACK =Intra-BSC Channel Release Timestamp - CONNECT ACK Timestamp
>Short Call
Yes No
N/A
Whether the abnormal of short call is occurred. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
2076
Parame ter Service Quality Estimati on for Service Process >Uplink Oneway Audio During a Call
Range N/A
Unit N/A
Yes No
N/A
Whether uplink one-way audio occurs during a call. 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 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 threshold, the BSS determines that primary uplink one-way audio occurs, and starts the mechanism for confirming the occurrence of primary uplink one-way audio. During this process, the BSC sends a message to the BTS demanding that the BTS send a test TRAU frame to the TC. If the TC fails to receive the test TRAU frame from the BTS within a specified time period, one-way audio occurs on the uplink voice channel.
Issue 01 (2013-07-15)
2077
Range Yes No
Unit N/A
Description Whether downlink one-way audio occurs during a call. 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 Um and A interfaces. Principle for detecting downlink one-way audio: The DSP in the DTRU of the BTS performs periodic statistics on the bad frame rate based on downlink TRAU frames. When the bad frame rate reaches the predefined threshold, the BSS determines that primary downlink one-way audio occurs, and starts the mechanism for confirming the occurrence of primary downlink one-way audio. During this process, the BSC sends a message to the TC demanding that the TC send a test TRAU frame to the BTS. If the BTS fails to receive the test TRAU frame from the TC within a specified time period, oneway audio occurs on the downlink voice channel.
Yes No
N/A
Whether uplink crosstalk occurs during a call. 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 uplink crosstalk: The DSP of the BTS inserts the unique identifier of a call into the free bits of uplink voice TRAU frames. The DSP of the TC decodes the unique call identifiers and checks their consistency. If inconsistency in the unique call identifiers is detected within the test period, uplink crosstalk occurs.
Issue 01 (2013-07-15)
2078
Range Yes No
Unit N/A
Description Whether downlink crosstalk occurs during a call. 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 uplink voice TRAU frames. The DSP of the BTS decodes the unique call identifiers and checks their consistency. If inconsistency in the unique call identifiers is detected within the test period, downlink crosstalk occurs.
N/A
Whether uplink noise occurs during a call, which is detected by the device. Whether downlink noise occurs during a call, which is detected by the device. Average value for the uplink high quality indicators (HQIs) of call setups that include the HQIs before and after the call setup is successful. 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 reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
Issue 01 (2013-07-15)
2079
Range Yes No
Unit N/A
Description Whether the abnormal of bad uplink HQI is occurred of call setups that include the HQIs before and after the call setup is successful. The abnormal threshold is set when creating tasks.
[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. In CHRs of the BSC6900 V900R011 or any later version: HQI = Number of measurement reports indicating a voice quality of levels 0 to 3/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100% In CHRs of the BSC6000 V900R008: HQI = Number of measurement reports indicating a voice quality of levels 0 to 5/Number of measurement reports indicating a voice quality of levels 0 to 7 x 100%
Yes No
N/A
Whether the abnormal of bad downlink HQI is occurred of call setups that include the HQIs before and after the call setup is successful. The abnormal threshold is set when creating tasks.
[1.00,5.00]
N/A
Average value for the uplink voice quality indicators (VQIs) of successful call setups. 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/ Total number of uplink VQI tests
Issue 01 (2013-07-15)
2080
Range Yes No
Unit N/A
Description Whether the abnormal of bad uplink VQI is occurred. The abnormal threshold is set when creating tasks.
Measure ment Informat ion On Service Process >Averag e Uplink Level >Averag e Downlin k Level >Averag e Uplink Quality >Averag e Downlin k Quality
N/A
N/A
[-110,-47]
dBm
Average uplink level on service process. Average downlink level on service process.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[-110,-47]
dBm
[0,7]
N/A
Average uplink quality on service process. Average downlink quality on service process.
[0,7]
N/A
N/A
N/A
Uplink Downlink
N/A
Issue 01 (2013-07-15)
2081
Range N/A
Unit N/A
Description 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. Content of a signaling message. You can obtain the content of a signaling message by viewing the related tree structure.
Signalin g Content
N/A
N/A
N/A
N/A
N/A
N/A
Server Nbr1~6
N/A
Issue 01 (2013-07-15)
2082
Unit N/A
Description Base transceiver Station Identity Code (BSIC) of a neighboring cell, reported in a measurement report.BSIC has 6 bits, the first part is NCC, the last past is BCC. TA of a serving cell, reported in a measurement report. Downlink RxLevel of a serving cell and that of a neighboring cell, reported in a measurement report. Uplink RxLevel of a serving cell, reported in a measurement report. Downlink RxQuality of a serving cell, reported in a measurement report. Uplink RxQuality of a serving cell, reported in a measurement report. BTS power of a serving cell, reported in a measurement report. MS power of a serving cell, reported in a measurement report.
TA
[0,63]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RxLevel (Downli nk) RxLevel (Uplink) RxQualit y (Downli nk) RxQualit y (Uplink) BTS Power MS Power
[-110,-47]
dBm
[-110,-47]
dBm
[0,7]
N/A
[0,7]
N/A
[0,15]
N/A
[0,31]
N/A
Mobility Analysis
Parame ter Number Range [0,+) Unit Numb er N/A Description Number for a handover triggered during a call. Whether a record indicates an abnormal handover. The record indicates an abnormal handover if a red exclamation mark is displayed.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Abnorm al
N/A
2083
Range Communicat ion resumes on the original channel after a handover failure the BSC releases channel resources the MSC is faulty
Unit N/A
Description Whether a handover succeeds, and the cause of a handover failure. The cause is displayed as Normal if a handover succeeds. 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.
Type
Intra-BSC handover Outgoing cell handover Incoming inter-BSC handover Outgoing inter-BSC handover Outgoing inter-RAT handover
N/A
Type of a handover
Initiatin g Time
N/A
N/A
Time when a handover is initiated, namely, the time when the BSC sends the Handover CMD message.
Duration
[0,+)
N/A
Issue 01 (2013-07-15)
2084
Range Yes No
Unit N/A
Description The first case: "Handover Type" is "Outgoing inter-BSC handover" If the duration is more than "Outgoing BSC Handover Interval", it displays "Yes"; If not, it displays "No". The second case: "Handover Type" is "Outgoing inter-RAT handover" If the duration is more than "Outgoing System Handover Interval", it displays "Yes"; If not, it displays "No". The other case: displays null. "Outgoing BSC Handover Interval" and "Outgoing System Handover Interval" is set when creating tasks.
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Cause of a handover.
N/A
N/A
Name of the source cell to be handed over. The parameter is displayed in the following format: Name of the BSC: Name of the cell (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. In the preceding format, BSC OPC is the originating signaling point configured on the BSC side.
N/A
N/A
2085
Range N/A
Unit N/A
Description Name of the target cell to which a handover is to be performed. The parameter is displayed in the following format: Name of the BSC: Name of the cell (BSC OPC: ID of the cell). You can obtain the names of the BSC and the cell from the configuration data.
Summary
Param eter Serial Number Range (0,2^31-1) Unit N/A Description 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. 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. 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. Supported NE Version BSC6900 V900R013C01 or later version
Combin ed
N/A
N/A
Issue 01 (2013-07-15)
2086
Range For details, see "Appendix: Exception Cause Classification / Key Signaling (GSM)". GSM-CS, GSMPS
Unit N/A
Networ k
N/A
Issue 01 (2013-07-15)
2087
Range Non-SMS message from a mobile-originated VIP subscriber (AC_ORIGIN_C ALL_NO_SMS) SMS message from a mobileoriginated VIP subscriber (AC_ORIGIN_C ALL_SMS) Answer to paging (AC_ANSWER_ TO_PAGING) Call re-setup (AC_CALL_RE_ ESTABLISH) Emergency call (AC_EMERGEN CY_CALL) Location update (AC_LOCATION _UPDATE) IMSI detachment (AC_IMSI_DET ACH) Data service (AC_PACKET_C ALL) LMU service (AC_LMU_EST ABLISH) SS service (AC_SS_ESTAB LISH) VGCS service (AC_VGCS_EST ABLISH) VBS service (AC_VBCS_EST ABLISH) LCS service (AC_LCS_ESTA BLISH)
Unit N/A
Issue 01 (2013-07-15)
2088
Param eter
Range Any other service (AC_RESERVE D) Incoming interBSC handover (AC_IN_BSC_H O) Response to notification (AC_NOTIFICA TION_RSP) Immediate setup (AC_IMM_SET_ UP) RR initialization (AC_RR_INITIA LISATION_REQ ) Indication from talker (AC_TALKER_I NDICATION) VGCS access (AC_VGCS_VBS _VPCS) Non-SMS message from a mobileterminated VIP subscriber (AC_ANSWER_ TO_PAGING_C ALL) SMS message from a mobileterminated VIP subscriber (AC_ANSWER_ TO_PAGING_C ALL) Normal location update (AC_LOCATION _UPDATE_NOR MAL) Periodic location update
Unit
Description
Supported NE Version
Issue 01 (2013-07-15)
2089
Param eter
Unit
Description
Supported NE Version
Access Time
N/A
N/A
Signaling access time for a call, namely, the time when a MS sends the Channel Request message. Name of the cell in which a MS sends the Channel Request message. 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
Access Cell
N/A
N/A
Release Time
N/A
N/A
Signaling release time for a call, namely, the time when a MS receives the Channel Release message.
Release Cell
N/A
N/A
Name of the cell in which a MS receives the Channel Release message. 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 display
User ID:Alia s
N/A
N/A
Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
Issue 01 (2013-07-15)
2090
Range 00000000-999999 99
Unit N/A
Description International mobile equipment identity-type allocation code (IMSI-TAC) of a VIP subscriber, which is the first eight digits in the IMEI of a UE. Type of a MS. You can obtain the IMEI-TACs of the UE from the MS type management function.
Model
N/A
N/A
N/A
N/A
Mobile station international ISDN number (MSISDN) of a peer subscriber. Service duration covering the call duration and the signaling setup duration. Service duration = Release time - Access time
[0,+)
Seco nd
Cause of Downli nk TBF Setup Failure Cause of Abnorm al Downli nk TBF Release Cause of Uplink TBF Setup Failure Cause of Abnorm al Uplink TBF Release
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2091
User Information
Param eter User ID:Alia s IMEITAC Model Range N/A Unit N/A Description Refer to "User ID:Alias" in the Summary area. Refer to "IMEI-TAC" in the Summary area. Refer to "Model" in the Summary area. Capability of the MS. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
MS Capabil ity >Suppo rt GPRS >Suppo rt GPRS MultiSlot Class >Suppo rt EGPRS >Suppo rt EGPRS MultiSlot Class >Suppo rt 900M E Frequen cy Band >Suppo rt 1800M Frequen cy Band
N/A
N/A
N/A
N/A
N/A
N/A
Support Unsupport
N/A
Support Unsupport
N/A
Issue 01 (2013-07-15)
2092
Param eter >Suppo rt G-TD DualMode >Suppo rt G-U DualMode >Suppo rt DTM >Suppo rt PS Handov er Insuffic ient Termin al Capabil ity
Unit N/A
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Support Unsupport
N/A
N/A
Whether a Terminal supports DTM. Whether a Terminal supports handovers in the PS domain.
N/A
Yes No
N/A
The capability of a Terminal is insufficient in the case of the following: The Terminal supports GPRS but not EGPRS. The Terminal supports EGPRS but the EGPRS multislot class is below 10.
Subscri ber Registra tion Paramet er >Reliab ility Level >Subscr iption Rate
N/A
N/A
Parameters related to the service that a VIP subscriber subscribes to when opening an account.
N/A
N/A
For details about the parameter, see see 3GPP TS 23.107. For details about the parameter, see see 3GPP TS 23.107.
N/A
N/A
Issue 01 (2013-07-15)
2093
Range Yes No
Unit N/A
Description An account-opening exception occurs in the case of the following: The reliability class of a VIP subscriber is not 3, namely, the reliability class is not the RLC acknowledged mode. The subscription rate is lower than the predefined exception threshold (which is set by engineers when creating tasks).
Peer Information
Param eter Number of Server Applica tions List of Servers and Applica tions >IP Address >Server Name Rang e N/A Unit N/A Description Total number of the server applications that a VIP subscriber accesses when attempting to use a data service. Supported NE Version BSC6900 V900R013C01 or later version
N/A
N/A
N/A
N/A
IP address of the server that a VIP subscriber accesses when attempting to use a data service. Name of the server that a VIP subscriber accesses when attempting to use a data 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 Port number of the server that a VIP subscriber accesses when attempting to use a data service.
N/A
N/A
>Port
[0,65 535)
N/A
Issue 01 (2013-07-15)
2094
Rang e N/A
Unit N/A
Description name of the application that a VIP subscriber accesses when attempting to use 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
[0,63 ]
N/A
[0,7]
N/A
GMSK MEAN BEP upon Access 8PSK MEAN BEP upon Access Access Cell
[0,31 ]
N/A
[0,31 ]
N/A
Information about the 8PSK MEAN BEP when a Terminal sends the Channel Request message.
N/A
N/A
Name of the cell in which a MS sends the Channel Request message. 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
Issue 01 (2013-07-15)
2095
Ran ge N/A
Uni t N/A
Description Time when a VIP subscriber releases a data service. Duration of the data service used by a VIP subscriber. 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. Number of access requests on the RACH (uplink CCCH) during the whole process for a subscriber to use a data service.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +) N/A
[0, +)
Nu mbe r
Issue 01 (2013-07-15)
2096
Param eter PDP Active Accept Times PDP Active Reject Times RA Update Request Times RA Update Accept Times RA Update Reject Times Suspen d Times
Ran ge [0, +)
Description Number of the PDP Active Accept messages that a VIP subscriber receives during the whole process of using a data service. Number of the PDP Active Reject messages that a VIP subscriber receives during the whole process of using a data service. Number of the RA Update Request messages that a VIP subscriber sends during the whole process of using a data service. Number of the RA Update Accept messages that a VIP subscriber receives during the whole process of using a data service. Number of the RA Update Reject messages that a VIP subscriber receives during the whole process of using a data service. Number of Suspends during the whole process for a VIP subscriber to use a data service.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +)
[0, +)
[0, +)
[0, +)
[0, +)
N/A
N/A
Issue 01 (2013-07-15)
2097
Rang e N/A
Unit N/A
Description Carrier of a TBF setup failure on the downlink. BCCH of a TBF setup failure on the downlink. Number of TBF setup failures on the uplink.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
Times of Uplink TBF Setup Failure >Cause s of Uplink TBF Setup Failure >Carrie r Index >BCCH
N/A
Num ber
N/A
N/A
N/A
N/A
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
Times of Abnor mal Downli nk TBF Release >Cause s of Abnor mal Downli nk TBF Release >Carrie r Index
[0, +)
Num ber
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2098
Rang e N/A
Unit N/A
Description BCCH of an abnormal TBF release on the downlink. Number of abnormal TBF releases on the uplink.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Times of Abnor mal Uplink TBF Release >Cause s of Abnor mal Uplink TBF Release >Carrie r Index >BCCH
[0, +)
Num ber
N/A
N/A
N/A
N/A
Carrier of an abnormal TBF release on the uplink. BCCH of an abnormal TBF release on the uplink.
N/A
N/A
[0, +) [0, +)
Byte
Size of the data transmitted by using the downlink PDU. Maximum duration for data transmission by using the downlink PDU.
Seco nd
Issue 01 (2013-07-15)
2099
Param eter >Total Duratio n on Sendin g PDU >Sent Count >Avera ge Duratio n on Sendin g PDU >Sendi ng Timeou t Times
Rang e [0, +)
Unit Seco nd
Description Overall duration for data transmission by using the downlink PDU.
[0, +) [0, +)
Total number of the blocks transmitted by using the downlink PDU. Average duration for data transmission by using the downlink PDU.
[0, +)
Num ber
Number of times that the duration for data transmission by using the downlink PDU exceeds the predefined threshold. A device is configured to directly check whether the duration for data transmission by using the PDU exceeds the predefined threshold.
Uplink PDU >Recei ved Bytes >Maxi mum Duratio n on Receivi ng PDU >Total Duratio n on Receivi ng PDU >Recei ved Count
N/A
N/A
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +) [0, +)
Byte
Size of the data transmitted by using the uplink PDU. Maximum duration for data transmission by using the uplink PDU.
Seco nd
[0, +)
Seco nd
[0, +)
Num ber
Issue 01 (2013-07-15)
2100
Param eter >Avera ge Duratio n on Receivi ng PDU >Recei ving Timeou t Times
Rang e [0, +)
Unit Seco nd
Description Average duration for data transmission by using the uplink PDU.
[0, +)
Num ber
Number of times that the duration for data transmission by using the uplink PDU exceeds the predefined threshold. A device is configured to directly check whether the duration for data transmission by using the PDU exceeds the predefined threshold.
Uplink/ Downli nk PDU >Maxi mum Interval Duratio n >Total Interval Duratio n >Numb er of Interval s >Avera ge Interval Duratio n >Numb er of Interval Timeou ts
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. Maximum interval for data transmission between the uplink and downlink PDUs.
[0, +)
Seco nd
[0, +)
Seco nd
Aggregated interval of all the intervals for data transmission between every two datatransmission time points on the uplink and downlink PDUs. Number of times that an interval for data transmission between the uplink and downlink PDUs is available. Average interval for data transmission between the uplink and downlink PDUs.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0, +)
Num ber
[0, +)
Seco nd
[0, +)
Num ber
Number of times that the interval for data transmission between the uplink and downlink PDUs exceeds the predefined threshold. A device is configured to directly check whether the interval for data transmission between the uplink and downlink PDUs exceeds the predefined threshold.
Issue 01 (2013-07-15)
2101
Param eter >Uplin k Data Availab le and Downli nk Data Unavail able Occurre nce Times Numbe r of No Service Interact ion Timeou t Times
Rang e [0, +)
Description Number of times that the uplink PDU carries data but downlink PDU does not. A device is configured to directly check whether the uplink PDU carries data while the downlink PDU does not.
[0, +)
Num ber
Number of times that no service interaction responses. 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.(A = Number of times that the uplink PDU carries data but the downlink PDU does not). The exception thresholds 1 and 2 for the response to service interaction are internal algorithm parameters.
[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. 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 Number of Interval Timeouts for data transmission between the uplink and downlink PDUs.
Issue 01 (2013-07-15)
2102
Rang e [0, +)
Description Average duration for the response to service interaction during the whole process for a VIP subscriber to use a data service. Average duration for the response to service interaction = Average duration for data transmission by using the downlink PDU + Average duration for data reception by using the uplink PDU + Average duration for data transmission between the uplink and downlink PDUs.
Yes No
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. If the average duration for the response to service interaction is above the upper threshold for the average duration for the response to service interaction, the average duration for the response to service interaction overlong. The threshold is set by engineers during analysis task creation.
[0, +)
Byte
Issue 01 (2013-07-15)
2103
Param eter >Durati on for Sendin g PDU at Downli nk >PDU Bytes Receive d at Uplink >Down load Speed (Kbps)
Ran ge [0, +)
Unit Secon d
Description Overall duration for data transmission by using the downlink PDU.
[0, +)
Byte
[0, +)
Kbps
Average download rate during the whole process for a subscriber to use a data service. Download rate = Number of bytes transmitted by using the downlink PDU/ Duration for data transmission by using the downlink PDU
Yes No
N/A
Number of low download rate exceptions during the whole process for a subscriber to use a data service. If a download rate is lower than the lower threshold for download rate, the download rate is low. The threshold is set by engineers when creating tasks.
[0, +)
Num ber
[0, +)
Num ber
Number of exceptions where downlink TCP disorder occurs during the whole process for a subscriber to use a data service.
Issue 01 (2013-07-15)
2104
Param eter >Avera ge Occupi ed Downli nk Slots >Down load MultiSlot Statisfa ction Ratio
Ran ge [1,6]
[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/ Multislot Class of the Terminal When Supporting GPRS.
>Trans mission Resour ces Require d for Code Request ed by Downli nk Block
[0, +)
Num ber
Issue 01 (2013-07-15)
2105
Param eter >Trans mission Resour ces Used by Code Assigne d to Downli nk Block >Resou rce Statisfa ction Ratio of Downli nk Averag e SingleSlot Throug hput (%) >GPRS Service Flag >>Num ber of Downli nk CS1~4 Blocks/ Valid Blocks >>Num ber of Total Blocks Sent at Downli nk
Ran ge [0, +)
Description Number of transmission resources actually used for the encoding of downlink blocks.
[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%
N/A
N/A
Information about the data service that a VIP subscriber uses through GPRS. 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.
[0, +)
Num ber
[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
Issue 01 (2013-07-15)
2106
Ran ge [0, +)
Description Total number of the valid blocks transmitted on the downlink = 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
[0, +)
Byte
Total number of the bytes contained in the valid blocks transmitted on the downlink = Number of the valid blocks transmitted on the downlink by using various channel coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the downlink by using CS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the downlink by using CS-4 x Number of the bytes contained in one valid block For details about the relation between a specific channel coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.2.
>>Dow nlink Retrans mission Ratio >>Dow nlink Reuse Ratio >EGDE Service Flag
[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 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 Information about the data service that a VIP subscriber uses through EGDE.
[0.00, +)
N/A
N/A
N/A
Issue 01 (2013-07-15)
2107
Param eter >>Num ber of Downli nk MCS1~ 9 Blocks/ Valid Blocks >>Num ber of Total Blocks Sent at Downli nk
Ran ge [0, +)
Description Total number of the blocks, and that of the valid blocks, transmitted on the downlink by using modulation and coding schemes MCS-1 through MCS-9.
[0, +)
Num ber
Total number of the blocks transmitted on the downlink = Total number of the blocks transmitted on the downlink by using various modulation and coding schemes = Number of the blocks transmitted on the downlink by using MCS-1 ++ Number of the blocks transmitted on the downlink by using MCS-9
[0, +)
Num ber
Total number of the valid blocks transmitted on the downlink = Total number of the valid blocks transmitted on the downlink by using various modulation and coding schemes = Number of the valid blocks transmitted on the downlink by using MCS-1 ++ Number of the valid blocks transmitted on the downlink by using MCS-9
[0, +)
Byte
Total number of the bytes contained in the valid blocks transmitted on the downlink = Number of the valid blocks transmitted on the downlink by using various modulation and coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the downlink by using MCS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the downlink by using MCS-9 x Number of the bytes contained in one valid block For details about the relation between a specific modulation and coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.3.
Issue 01 (2013-07-15)
2108
Param eter >>Dow nlink Retrans mission Ratio >>Dow nlink Averag e GMSK BEP >>Dow nlink Averag e 8PSK BEP >>Dow nlink Averag e BEP
Unit %
Description Downlink data-retransmission rate = Total number of the valid blocks transmitted on the downlink/Total number of the blocks transmitted on the downlink Average downlink GMSK BEP.
[0,31 ]
N/A
[0,31 ]
N/A
[0,31 ]
N/A
1. If both the average downlink GMSK BEP and the average downlink 8PSK BEP are valid, use the average downlink GMSK BEP with a higher order. 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.
N/A
Kbps
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.
Issue 01 (2013-07-15)
2109
Param eter >>Um Quality Satisfac tion Ratio of Downli nk Averag e SingleSlot Throug hput >>Poor Transm ission Quality Indicate d by Downli nk Averag e SingleSlot Throug hput >>Dow nlink Reuse Ratio Statistic s on UplinkRateSensitiv e Service s >PDU Bytes Receive d at Uplink
Unit %
Description Um-interface quality satisfaction rate at the average downlink single-slot throughput = MIN (Average downlink single-slot throughput/Target single-slot throughput x 100%, 100%) The target single-slot throughput is an internal algorithm parameter.
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, the transmission quality at the average downlink single-slot throughput is poor. The BEP required by the lowest-level coding and the upper threshold for downlink dataretransmission rate are internal algorithm parameters.
[0.00, +)
N/A
Downlink timeslot reuse = Overall duration for data transmission by using the downlink PDU x Average number of downlink timeslots/2/Total number of the blocks transmitted on the downlink Information about the statistics on uplink rate-sensitive services.
N/A
N/A
[0, +)
Byte
Issue 01 (2013-07-15)
2110
Param eter >Durati on for Receivi ng PDU at Uplink >PDU Bytes Sent at Downli nk >Uploa d Speed (Kbps)
Ran ge [0, +)
Unit Secon d
Description Overall duration for data transmission by using the uplink PDU.
[0, +)
Byte
[0, +)
Kbps
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 transmission by using the uplink PDU
Yes No
N/A
Number of low upload rate exceptions during the whole process for a subscriber to use a data service. If an upload rate is lower than the lower threshold for upload rate, the upload rate is low. The threshold is set by engineers when creating tasks.
>Numb er of Uplink NU Out-ofOrder Times >Numb er of Uplink TCP Out-ofOrder Times >Avera ge Occupi ed Uplink Slots
[0, +)
Num ber
[0, +)
Num ber
[1,6]
Num ber
Issue 01 (2013-07-15)
2111
Unit %
Description Uplink multislot-satisfaction rate = Average number of timeslots occupied by the uplink/ 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 Uplink Rate-Sensitive Service/EGDE Service Flag indicates a valid value, namely, the EDGE service is available, you can obtain the multislot class of a Terminal from Information About the VIP Subscriber/Capability of the Terminal/ Multislot Class of the Terminal When Supporting EGPRS. Otherwise, you can obtain the multislot class of a Terminal from Information About the VIP Subscriber/Capability of the Terminal/ Multislot Class of the Terminal When Supporting GPRS.
>Trans mission Resour ces Require d for Code Request ed by Uplink Block >Trans mission Resour ces Used by Code Assigne d to Uplink Block
[0, +)
Num ber
[0, +)
Num ber
Number of transmission resources actually used for the encoding of uplink blocks.
Issue 01 (2013-07-15)
2112
Param eter >Resou rce Statisfa ction Ratio of Uplink Averag e SingleSlot Throug hput (%) >Durati on for Sendin g PDU at Downli nk >Total Duratio n for Sendin g PDU at Downli nk >PDUs Sent at Downli nk >Timeo ut Times on sending PDUs at Downli nk >GPRS Service Flag
Unit %
Description Transmission-resource satisfaction rate at the average uplink single-slot throughput = Number of transmission resources actually used for the encoding of uplink blocks/ Number of transmission resources requested for the encoding of uplink blocks x 100%
[0, +)
Secon d
[0, +)
Secon d
[0, +)
Num ber
[0, +)
Num ber
Number of times that the duration for data transmission by using the downlink PDU exceeds the predefined threshold. A device is configured to directly check whether the duration for data transmission by using the PDU exceeds the predefined threshold.
N/A
N/A
Information about the data service that a VIP subscriber uses through GPRS.
Issue 01 (2013-07-15)
2113
Param eter >>Num ber of Uplink CSN (1~4) Blocks/ Valid Blocks >>Num ber of Total Blocks Receive d at Uplink
Ran ge [0, +)
Description Total number of the blocks, and that of the valid blocks, transmitted on the uplink by using channel coding schemes CS-1 through CS-4.
[0, +)
Num ber
Total number of the blocks transmitted on the uplink = Total number of the blocks transmitted on the uplink by using various channel coding schemes = Number of the blocks transmitted on the uplink by using CS-1 ++ Number of the blocks transmitted on the uplink by using CS-4
[0, +)
Num ber
Total number of the valid blocks transmitted on the uplink = Total number of the valid blocks transmitted on the uplink by using various channel coding schemes = Number of the valid blocks transmitted on the uplink by using CS-1 ++ Number of the valid blocks transmitted on the uplink by using CS-4
[0, +)
Byte
Total number of the bytes contained in the valid blocks transmitted on the uplink = Number of the valid blocks transmitted on the uplink by using various channel coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the uplink by using CS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the uplink by using CS-4 x Number of the bytes contained in one valid block For details about the relation between a specific channel coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.2.
Issue 01 (2013-07-15)
2114
Param eter >>Upli nk SingleSlot Throug hput (Actual ) >>Upli nk Reuse Ratio >EGDE Service Flag >>Num ber of Uplink MCS1~ 9 Blocks/ Valid Blocks >>Num ber of Total Blocks Receive d at Uplink
Unit Kbps
Description Uplink single-slot throughput (Actual) 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
[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 Information about the data service that a VIP subscriber uses through EGDE. Total number of the blocks, and that of the valid blocks, transmitted on the uplink by using modulation and coding schemes MCS-1 through MCS-9.
N/A
N/A
[0, +)
Num ber
[0, +)
Num ber
Total number of the blocks transmitted on the uplink = Total number of the blocks transmitted on the uplink by using various modulation and coding schemes = Number of the blocks transmitted on the uplink by using MCS-1 ++ Number of the blocks transmitted on the uplink by using MCS-9
[0, +)
Num ber
Total number of the valid blocks transmitted on the uplink = Total number of the valid blocks transmitted on the uplink by using various modulation and coding schemes = Number of the valid blocks transmitted on the uplink by using MCS-1 ++ Number of the valid blocks transmitted on the uplink by using MCS-9
Issue 01 (2013-07-15)
2115
Ran ge [0, +)
Description Total number of the bytes contained in the valid blocks transmitted on the uplink = Number of the valid blocks transmitted on the uplink by using various modulation and coding schemes x Number of the bytes contained in one valid block = Number of the valid blocks transmitted on the uplink by using MCS-1 x Number of the bytes contained in one valid block + + Number of the valid blocks transmitted on the uplink by using MCS-9 x Number of the bytes contained in one valid block For details about the relation between a specific modulation and coding scheme and the number of bytes contained in one valid block transmitted by using this scheme, see 3GPP TS 44.060-10.3.
>>Upli nk Receive Retrans mission Rate (%) >>Upli nk Averag e GMSK BEP >>Upli nk Averag e 8PSK BEP >>Upli nk Averag e BEP
[0.00, 100.0 0]
Uplink data-retransmission rate = Total number of the valid blocks transmitted on the uplink/Total number of the blocks transmitted on the uplink
[0,31 ]
N/A
[0,31 ]
N/A
[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, use the one with a valid value as the average uplink BEP.
Issue 01 (2013-07-15)
2116
Param eter >>Upli nk Averag e SingleSlot Throug hput Require d for Um Quality >>Um Quality Unsatis faction Times of Downli nk Averag e SingleSlot Throug hput
Unit Kbps
Description Average uplink single-slot throughput required to achieve a specific quality level on the Um interface. You can obtain the maximum single-slot rate, namely, the average uplink single-slot throughput, in BEP-Coding Scheme-Rate Mapping Table based on the average uplink BEP. The BEP-Coding Scheme-Rate Mapping Table is generated by an NE.
[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. 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) 3. If the average uplink single-slot throughput is smaller than the target single-slot throughput, and, at the same time, the value of B, which is obtained by using the following formula, is larger than the threshold for Um-interface quality satisfaction rate at the average uplink single-slot throughput, the quality on the Um interface does not meet the requirements. B = Average coding scheme_average uplink BEP/Average coding scheme_Number of the blocks actually received on the uplink.
Issue 01 (2013-07-15)
2117
Param eter >>Poor Transm ission Quality Indicate d by Uplink Averag e SingleSlot Throug hput >>Upli nk SingleSlot Throug hput (Actual ) >>Upli nk Reuse Ratio
Ran ge Yes No
Unit N/A
Description If the average uplink BEP is higher than the BEP required by the lowest-level coding, and, at the same time, the uplink dataretransmission rate is higher than the upper threshold for uplink data-retransmission rate, the transmission quality at the average downlink single-slot throughput is poor. The BEP required by the lowest-level coding and the upper threshold for uplink datareception-and-retransmission rate are internal algorithm parameters.
[0,10 0]
Uplink single-slot throughput (Actual) 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
[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
Summary Information
Param eter Total Traffic at Downli nk Ran ge [0, +) Unit Byte Description Total downlink traffic during the whole process for a subscriber to use a data service. 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 + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Downlink PDU Supported NE Version BSC6900 V900R013C01 or later version
Issue 01 (2013-07-15)
2118
Ran ge [0, +)
Unit Byte
Description Total uplink traffic during the whole process for a subscriber to use a data service. Total uplink traffic = Delay-Sensitive Information/Total Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Uplink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU + Rate-Sensitive Information/Statistics on Downlink Rate-Sensitive Service/Number of the Bytes Transmitted by Using the Uplink PDU
N/A
N/A
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. Content of a signaling message. You can obtain the content of a signaling message by viewing the related tree structure.
Signali ng Content
N/A
N/A
Issue 01 (2013-07-15)
2119
Measurement Information
Parame ter Number Rang e [0, +) N/A Unit N/A Description Unique number of a signaling message carrying a measurement report. Time when a measurement report is submitted. Type of a measurement report. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Time
N/A
MR Type
2G NC MR 3G MR EUTRA N MR
N/A
Server Nbr1~ 6
N/A
Type of a measurement object reported in a measurement report. 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.
N/A
N/A
name of a measurement object reported in a measurement report. The parameter is displayed in the following format: name of the BSC: name of the cell.
BCCH
N/A
BCCH of a neighboring cell on 2G network, reported in a measurement report. BSIC of a neighboring cell on 2G network, reported in a measurement report.
BSIC
N/A
dBm
Downlink RxLevel of a serving cell and that of a neighboring cell on 2G network, reported in a measurement report. Frequency on 3G network, reported in a measurement report. Primary scrambling code on 3G networkl, reported in a measurement report.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
N/A
N/A
Issue 01 (2013-07-15)
2120
Unit dBm
Description RSCP on 3G networkl, reported in a measurement report. Frequency on LTE network, reported in a measurement report. Primary scrambling code on LTE networkl, reported in a measurement report. RSCP on LTE networkl, reported in a measurement report.
Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
Frequen cy PCI
N/A
N/A
RSRP
dBm
Mobility Analysis
Parame ter Number Range N/A Unit N/A Description Number. Supported NE Version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
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. The threshold is set by engineers when creating tasks.
Abnorm al Cause
Overlo ng time of cell reselec tion (Durati on) Cell Resele ction N/A
N/A
If the time interval is above the exception threshold for cell reselection, it displays "Overlong time of cell reselection (Duration)".
Type
N/A
Type of a mobility analysis, namely, cell reselection. Time when a cell reselection ends.
End Time
N/A
Issue 01 (2013-07-15)
2121
Range N/A
Unit N/A
Description Source cell for a cell reselection. 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 based on the internal ID of the BSC and the ID of the cell. The names are not displayed if they are not available.
Reselect RxQuali ty Reselect GMSK MEAN BEP Reselect 8PSK MEAN BEP Target Cell
[0,7]
N/A
RxQulity of the source cell for a cell reselection. GMSK MEAN BEP of the source cell for a cell reselection.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0,31]
N/A
[0,31]
N/A
N/A
N/A
Target cell for a cell reselection. 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 based on the internal ID of the BSC and the ID of the cell. The names are not displayed if they are not available.
Access RxQuali ty Access GMSK MEAN BEP Access 8PSK MEAN BEP
[0,7]
N/A
RxQulity of the target cell for a cell reselection. GMSK MEAN BEP of the target cell for a cell reselection.
BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version BSC6900 V900R013C01 or later version
[0,31]
N/A
[0,31]
N/A
Summary
Param eter Serial Numbe r Range (0,2^31-1) Uni t N/A Description 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. 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. ! Blank N/A Whether a call record is abnormal. 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. Abnor mal Cause For details, see "Appendix: Exception Cause Classificatio n/ Enumeration Values of Failure Cause (UMTS)". 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. BSC6900 V900R013C00 or later version Supported NE Version BSC6900 V900R013C00 or later version
Combi ned
N/A
N/A
Status
Networ k
N/A
Issue 01 (2013-07-15)
2123
Range Static reloc in HHO reloc in Cell update reloc in Inter RAT handover in RRC setup without DRD RRC setup with DRD
Uni t N/A
Issue 01 (2013-07-15)
2124
Range Originating Conversation al Call Originating Streaming Call Originating Interactive Call Originating Background Call Originating Subscribed traffic Call Terminating Conversation al Call Terminating Streaming Call Terminating Interactive Call Terminating Background Call Emergency Call Inter-RAT cell reselection Inter-RAT cell change order Registration Detach Originating High Priority Signaling Originating Low Priority Signaling
Uni t N/A
Issue 01 (2013-07-15)
2125
Param eter
Range Call reestablishmen t Terminating High Priority Signaling Terminating Low Priority Signaling Terminating - cause unknown MBMS reception MBMS ptp RB request
Uni t
Description
Supported NE Version
Access Time Access Cell Release Time Release Cell User ID:Alia s
N/A
N/A
Same as Access Information -> RRC Request Time. Same as Access Information -> Cell on RRC Setup. Same as Release Information -> RRC Release Time Same as Release Information -> RRC Release Cell Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
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.
Termin al Model
N/A
N/A
Model of a UE. The UE model can be queried using terminal type management based on the IMEI-TAC of the UE.
Issue 01 (2013-07-15)
2126
Range [0,+)
Uni t Seco nd
Description Duration of a call, including service duration and signaling duration. Call duration = Release time - Access time.
CS Reques ted Service Type CS Service Duratio n PS Reques ted Service Type PS RAB Duratio n RRC Setup Failure Cause
AMR VP
N/A
[0,+)
Seco nd
N/A
Seco nd
For details, see "Access information/ RRC Setup Failure Cause". N/A
N/A
IU Release Cause
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.
N/A
N/A
Cause of CS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
Issue 01 (2013-07-15)
2127
Range N/A
Uni t N/A
Description Cause of CS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
N/A
N/A
Cause of PS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
N/A
N/A
Cause of PS RAB setup or release failure. This parameter contains information in following levels: exception type, exception causes of an exception type. The value of this parameter is carried in the RAB ASSIGNMENT RESPONSE message for the Iu interface. For details, see 3GPP 25.413 - 9.1.4.
User Information
Param eter TMSI/ PTMSI Range 0000000-FFFFFFFF Uni t N/A Description 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. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
2128
Range N/A
Uni t N/A
Description Identity of a subscriber. User ID, which is created by the system when creating the task. Alias, which is created by the user when creating the task.
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.
Termin al Model
N/A
N/A
Model of a UE. The UE model can be queried using terminal type management based on the IMEI-TAC of the UE.
Termin al Operati ng System UE Capabil ity >Proto col Versio n >Power Class
For details, see the OS description of the UMTS terminal analysis. N/A
N/A
N/A
Capability of a UE.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
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.
Issue 01 (2013-07-15)
2129
Range Band I 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 Band XVI Band XVII Band XVIII Band XIX Band XX Band XXI Band XXII Reserved
Uni t N/A
Description Universal Terrestrial Radio Access (UTRA) frequency bands supported by a UE. For details, see Table 5.0 "UTRA FDD frequency bands" under "UE Radio Transmission and Reception (FDD)" in 3GPP TS 25.101.
>HSPA Capabil ity >>HSDSCH Capabil ity >>EDCH Capabil ity >>Sup port ERACH
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[1,64]
N/A
HSDPA capability of a UE. A larger value of this parameter indicates larger HSDPA capability. HSUPA capability of a UE. A larger value of this parameter indicates larger HSUPA capability. Whether a UE supports ERACH.
[1,16]
N/A
supported unsupported
N/A
Issue 01 (2013-07-15)
2130
Param eter >>Sup port EFACH >>Sup port DTXD RX >>Sup port HSSCCH Less Operati on >Mobil ity Capabil ity
Uni t N/A
Description Whether a UE supports EFACH. Whether a UE supports discontinuous transmission (DTX) and discontinuous reception (DRX). Whether a UE supports HSSCCH.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
supported unsupported
N/A
Support of GSM 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 Support of UTRAN to GERAN NACC Support of Handover to GAN Support of PS Handover to GAN Reserved
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.
Issue 01 (2013-07-15)
2131
Param eter >Suppo rt EUTRA Band Capabil ity >Positi oning Capabil ity
Uni t N/A
Description Evolved Universal Terrestrial Radio Access (E-UTRA) frequency bands supported by a UE.
Standalone location method(s) supported UE based OTDOA supported GANSS support indication Support for GPS timing of cell frames measurement Support for IPDL Support for Rx-Tx time difference type2 measurement Support for UP assisted GPS measurement validity in CELL_PCH and URA_PCH states Support for SFNSFN observed time difference type 2 measurement Network Assisted GPS support
N/A
Access Information
Param eter RRC Request Time Range N/A Uni t N/A Description Time of signaling access during a call. That is, timestamp in the RRC CONNECTION SETUP message. Supported NE Version BSC6900 V900R013C00 or later version
Issue 01 (2013-07-15)
2132
Param eter RRC Radio Link Setup Time Cell on RRC Setup
Range N/A
Uni t N/A
Description Time of RRC radio link setup during a call. That is, timestamp in the RADIO LINK SETUP REQUEST message. Name of the cell to which signaling accesses. 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.
N/A
N/A
N/A
N/A
Target cell of Directed Retry Decision (DRD) during signaling access. 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.
SRB on FACH_RACH SRB on DCH_DCH SRB on HSDSCH_RACH SRB on HSDPA_DCH SRB on DCH_HSUPA SRB on HSDPA_HSUPA
N/A
Issue 01 (2013-07-15)
2133
Range Static reloc in HHO reloc in Cell update reloc in Inter RAT handover in RRC setup without DRD RRC setup with DRD
Uni t N/A
Description Value of RRC Connection Setup Type carried in the RRC CONNECTION SETUP message: Incoming migration (Static reloc in) 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) Incoming inter-RAT handover (Inter RAT handover in) RNC access (RRC setup without DRD) RNC access (RRC setup with DRD)
Issue 01 (2013-07-15)
2134
Range Originating Conversational Call Originating Streaming Call 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 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 MBMS ptp RB request
Uni t N/A
Description Cause of RRC setup. For details, see 3GPP TS 25.331-10.3.3.11 "Establishment cause."
Issue 01 (2013-07-15)
2135
Uni t N/A
Description Whether RRC setup is triggered by service or non-service causes based on RRC Setup Cause. The rules for determining the trigger conditions are as follows: 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.
CS PS
N/A
Whether RRC setup occurs in the CS or PS domain based on RRC Setup Cause.
Issue 01 (2013-07-15)
2136
Uni t N/A
Description Whether RRC setup occurs on the MOC or MTC side based on RRC Setup Cause. The rules for determining the occurrence conditions are as follows: 1. RRC setup occurs on the MOC side when the value of RRC Setup Cause is any of the following: Originating Conversational Call Originating Streaming Call Originating Interactive Call Originating Background Call Originating Subscribed traffic Call Originating High Priority Signaling Originating Low Priority Signaling Emergency Call 2. RRC setup occurs on the MTC side when the value of RRC Setup Cause is any of the following: 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 01 (2013-07-15)
2137
Uni t N/A
Description Whether RRC setup is triggered by SMS or non-SMS causes based on RRC Setup Cause. The rules for determining the trigger conditions are as follows: 1. RRC setup is triggered by SMS causes when the value of RRC Setup Cause is any of the following: Originating High Priority Signaling Originating Low Priority Signaling Terminating High Priority Signaling Terminating Low Priority Signaling 2. Otherwise, RRC setup is triggered by non-SMS causes.
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
N/A
Error Type.
>Error Reason
N/A
Error Reason.
N/A
2138
Range [0,+)
Uni t Seco nd
Description Delay on RRC setup. The statistical points are as follows: 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. Inter-RAT handover: Timestamp in the RELOCATION REQUEST message - Timestamp in the UTRAN MOBILITY INFORMATION CONFIRM message.
Yes No
N/A
Overlong RRC setup delay occurs when the RRC setup delay exceeds the overlong delay threshold limit. The abnormal threshold is set by engineers during analysis task creation.
N/A
N/A
N/A
N/A
Cell on which RAB setup is requested. 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.
>TP
[0,3069 ]
N/A
Time Propagation (TP) is a term defined by Huawei to indicate time propagation delay during UE access.
Issue 01 (2013-07-15)
2139
Range Yes No
Uni t N/A
Description 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. Remark: If the active set contains multiple cells during access, the counters for all the cells in this active set are analyzed.
[-24,0]
dB
Ec/No of the serving cell on RRC setup. If "Ec/No" is smaller than "Ec/No abnormal threshold on RRC setup", it indicators that the Ec/No is abnormal on RRC setup. Abnormal threshold is set when creating tasks. Remark: If the active set contains multiple cells during access, the counters for all the cells in this active set are analyzed.
Yes No
N/A
>RSCP
[-115,-25]
dBm
RSCP of the serving cell on RRC setup. If "RSCP" is smaller than "RSCP abnormal threshold on RRC setup", it indicators that the RSCP is abnormal on RRC setup. Abnormal threshold is set when creating tasks. Remark: If the active set contains multiple cells during access, the counters for all the cells in this active set are analyzed.
Yes No
N/A
Issue 01 (2013-07-15)
2140
Release Information
Param eter RRC Release Time Range N/A Unit N/A Description Release time of RRC connection. That is, timestamp in the RRC CONNECTION RELEASE message. [0,+) Seco nd Duration of a call. Call duration = RRC release time - RRC setup request time Name of the cell from which signaling is released. The parameter value is displayed in the following format: RNC name:cell name (RNCID: cellID). 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. Successful Failed N/A N/A Release cause carried in the last IU RELEASE COMMAND message received by an RNC. Type of failure cause. For details, see 3GPP 25.413-9.2.1.4. N/A RRC release results. Supported NE Version BSC6900 V900R013C00 or later version
Duratio n
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Radio Network Layer Cause Transport Layer Cause NAS Cause Protocol Cause Miscellaneous Cause Non-standard Cause Radio Network Layer Cause Extension
N/A
>Cause value
N/A
N/A
Issue 01 (2013-07-15)
2141
Statistical Information
Param eter Soft Handov er Info >Soft Handov er Request s >Succe ssful Soft Handov ers >Softer Handov er Request s >Succe ssful Softer Handov ers Hard Handov er Info >IntraFreq Handov er Request s >Succe ssful IntraFreq Handov ers Range N/A Unit N/A Description Soft handover information. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Num ber
Number of soft handover requests, including soft handover requests and softer handover requests.
[0,+)
Num ber
Number of successful soft handovers, including successful soft handovers and successful softer handovers. Number of softer handover requests.
[0,+)
Num ber
[0,+)
Num ber
N/A
N/A
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
2142
Param eter >InterFreq Handov er Request s >Succe ssful InterFreq Handov ers InterRAT Handov er Info >InterSystem Outgoin g Handov er Request s(CS) >InterSystem Outgoin g Handov er Request s(PS) >Succe ssful InterSystem Outgoin g Handov ers
Range [0,+)
[0,+)
Num ber
N/A
N/A
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
2143
Param eter >InterSystem Incomi ng Handov er Request s >Succe ssful InterSystem Incomi ng Handov ers DCCC Info >DCCC Speed Increas e Initializ ation Times >DCCC Speed Increas e Success Times >DCCC Speed Decreas e Initializ ation Times >DCCC Speed Decreas e Success Times
Range [0,+)
[0,+)
Num ber
N/A
N/A
DCCC information.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
2144
Param eter RAB Info >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (AMR) >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (VP) >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (PS)
Range N/A
Unit N/A
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Num ber
Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for the AMR service.
[0,+)
Num ber
Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for the VP service.
[0,+)
Num ber
Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for PS services. In which, PS services include the PS R99 service, HSDPA service, HSUPA, service, and HSPA service.
Issue 01 (2013-07-15)
2145
Param eter >RAB Request /Setup Success Times/ Normal Release Times/ Abnor mal Release Times (HSDP A) MultiRAB Info >Abnor mal CS Release due to PS Release >Abnor mal CS Release due to PS Service Setup >Releas ed RABs in CS Domain Trigger ed by the Failure in Securit y Mode
Range [0,+)
Description Number of RAB requests, successful RAB setups, normal RAB releases, and abnormal RAB releases for the HSDPA service.
N/A
N/A
Multi-RAB information.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
2146
Param eter >Releas ed RABs in PS Domain Trigger ed by the Failure in Securit y Mode >Setup Attempt s of Combin ed Service (CS + PS) >Succe ssful Setups of Combin ed Service (CS + PS) >CS plus PS multiRAB CS normal release times >CS plus PS multiRAB CS abnorm al release times
Range [0,+)
Description Number of released RABs in the PS domain triggered by failed security authentication.
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
2147
Param eter >CS plus PS multiRAB PS normal release times >CS plus PS multiRAB PS abnorm al release times >Setup Attempt s of Combin ed Service (PS + PS) >Succe ssful Setups of Combin ed Service (PS + PS) >Norm al Release s of Combin ed Service (PS + PS)
Range [0,+)
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
2148
Param eter >Abnor mal Release s of Combin ed Service (PS + PS) Statistic s of Voice Quality in CS Domain >OneWayAudio Times >Noise Times
Range [0,+)
N/A
N/A
[0,+)
Num ber
[0,+)
Num ber
Issue 01 (2013-07-15)
2149
Range 1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
Unit N/A
Traffic class: conversational streaming interactive background Traffic type: CS_AMR CS_VP CS_OTHER PS_GENERAL PS_HSDPA PS_HSUPA PS_HSPA ...
N/A
RAB request service type consists of two parts: Traffic class and Traffic type. The parameter value is displayed in the format of Traffic class/ Traffic type. For details about Traffic class, see 3GPP 25.413. Traffic type is a service type defined by Huawei in terms of radio access bearer (RAB).
N/A
N/A
Time when RAB setup is requested. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT REQUEST message. Incoming migration: Timestamp in the RELOCATION COMPLETE message. Inter-RAT handover: Timestamp in the HANDOVER TO UTRAN COMPLETE message.
Issue 01 (2013-07-15)
2150
Range N/A
Unit N/A
Description Cell on which RAB setup is requested. The parameter value is displayed in the following format: RNC 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.
[0,+)
Seco nd
Time when RAB setup completes. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT RESPONSE message. Incoming migration: The time is not recorded. Inter-RAT handover: The time is not recorded.
N/A
N/A
Best cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Service cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
>DRD Info
N/A
N/A
Information about DRDs during RAB setup, recording the last three DRDs at most.
Issue 01 (2013-07-15)
2151
Range N/A
Unit N/A
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Target cell of the current DRD. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
N/A
DRD failure cause. For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
>>>>Er ror Type >>>>Er ror Reason >>Peer Info >>>Pee r MSISD N
For details, see the "Enumeration Values of Failure Cause". For details, see the "Enumeration Values of Failure Cause". N/A
N/A
Error type.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
Error reason.
N/A
N/A
Mobile station international ISDN BSC6900 number (MSISDN) of the peer UE. V900R013C00 MSISDN is a 15-digit numeric or later version string of decimal digits (0-9). For details, see 3GPP TS 23.003.
Issue 01 (2013-07-15)
2152
Range DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
Description Type of an uplink or downlink data transmission channel after RAB setup. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
2153
Range [0,+)
Unit kbps
Description 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. In which, When UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/s. When UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/ s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>RAB Setup Result >RAB Setup Failure Time >RAB Setup Failure Cause >>Error Type
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Error type.
Issue 01 (2013-07-15)
2154
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
Unit N/A
>RAB Setup Delay Estimat ion >>RAB Setup Delay >>Over long RAB Setup Delay
N/A
[0,+)
Seco nd N/A
RAB setup delay = Time when RAB setup completes - Time when RAB setup is requested. Overlong RAB setup delay occurs when the RAB setup delay exceeds the overlong delay threshold limit. The overlong delay threshold is set by engineers during analysis task creation.
Yes No
[0,+)
Seco nd
Call setup delay = Time when RAB setup completes - Time when RRC setup is requested. Call setup delay = RAB setup delay + RRC setup delay. Note that this parameter is applicable only to the first RAB after RRC setup.
Yes No
N/A
Overlong call setup delay occurs when the call setup delay exceeds the overlong delay threshold limit. The overlong delay threshold is set by engineers during analysis task creation.
N/A
N/A
Service request time, that is, the timestamp of "Service Request" message.
Issue 01 (2013-07-15)
2155
Range [0,+)
Unit Seco nd
Description 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 COMPLETE message Timestamp in the RADIO BEARER RECONFIGURATION message.
N/A
N/A
Time of outgoing call alerting during a call. Statistical point: Timestamp in the ALERTING message. 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. Outgoing call alerting delay = Alerting time - RRC setup request time.
N/A [0,+)
N/A
Issue 01 (2013-07-15)
2156
Unit N/A
Description 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 Yes in the following conditions: The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MOC. Outgoing call alerting delay > Overlong outgoing call alerting delay threshold (MOC). The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MTC. Outgoing call alerting delay > Overlong outgoing call alerting delay threshold (MTC). 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.
>>Conn ect Ack Time >>Call Comple tion Delay (Conne ct Ack)
N/A
N/A
Time of incoming call alerting during a call. Statistical point: Timestamp in the CONNECT ACKNOWLEDGE message. 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. Incoming call alerting delay = Connect Ack time - RRC setup request time.
[0,+)
Seco nd
Issue 01 (2013-07-15)
2157
Param eter >>Over long Call Comple tion Delay (Conne ct Ack)
Unit N/A
Description 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 Yes in the following conditions: The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MOC. Incoming call alerting delay > Overlong incoming call alerting delay threshold (MOC). The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MTC. Incoming call alerting delay > Overlong incoming call alerting delay threshold (MTC). 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.
>RAB Setup Process >>Queu ing Indicato r >>Intra -system DRD Indicato r
N/A
N/A
Process information of RAB setup. This parameter is used with RAB Setup Failure Cause to analyze problems. TRUE(1) indicates that queuing occurs.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
False True
N/A
False True
N/A
Issue 01 (2013-07-15)
2158
Param eter >>Inter -system DRD Indicato r >RAB Resourc e Congest ion Informa tion on RAB Setup >>Cong estion Time >>Cong estion Cell ID >>Cong estion Status
Unit N/A
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.
N/A
N/A
Time when radio resource congestion occurs. Cell where radio resource congestion occurs. Cause of radio resource congestion.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Code DL CE 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
N/A
N/A
N/A
Issue 01 (2013-07-15)
2159
Range 1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
Unit N/A
>Single -RAB Abnor mal Release Indicato r >Multip le-RAB Abnor mal Release Indicato r >RAB Release Time
False True
N/A
False True
N/A
N/A
N/A
Time when RAB release completes. The statistical points are as follows: Normal release and CN abnormal release: RAB release time = Timestamp in the IU RELEASE COMMAND or RAB ASSIGNMENT REQUEST message.
>RAB Duratio n
[0,+)
Seco nd
Issue 01 (2013-07-15)
2160
Range Yes No
Unit N/A
Description If "RAB Duration" is smaller than "RAB Duration shorter threshold", it indicators that the RAB duration is too shorter. Abnormal threshold is set when creating tasks.
N/A
N/A
Best cell before RAB release. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Serving cell before RAB release. The parameter value is displayed in the following format: RNC 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.
Issue 01 (2013-07-15)
2161
Range DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
Description Type of an uplink or downlink data transmission channel before RAB release. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
2162
Range [0,+)
Unit kbps
Description Uplink and downlink RB rate after RAB setup and before RAB release. The parameter value is displayed in the format of UL RB bitrate after RAB setup/DL RB bitrate after RAB setup. In which, When UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/s. When UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/ s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>Disco nnect Cause >Disco nnect Directio n >RAB Release Failure Cause
N/A
N/A
Cause carried in the DISCONNECT message. For details, see 3GPP 24.008-10.5.4.11. Direction for sending the DISCONNECT message.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
from UE from CN
N/A
N/A
N/A
Issue 01 (2013-07-15)
2163
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
Unit N/A
>>Error Reason
N/A
Error reason.
N/A
Time when RAB release fails. That is, when the system receives the following timestamp: IU RELEASE REQUEST RAB RELEASE REQUEST
RAB Process Info >RAB Setup Delay Estimat ion >>Disc onnect time >>Servi ce Duratio n
N/A
N/A
N/A
N/A
N/A
N/A
Time when a call completes. Statistical point: timestamp in the DISCONNECT message. Service duration = Disconnect time - Connect Ack time.
[0,+)
Seco nd
Issue 01 (2013-07-15)
2164
Unit N/A
Description 1.The parameter value is Yes in the following conditions: When the current RAB is not the first RAB after RRC setup and Call duration < Short call threshold. The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MOC. Call duration < Short call threshold (MOC). The current RAB is the first RAB after RRC setup. RRC Setup Flag(MOC/MTC) is MTC. Call duration < Short call threshold (MTC). 2.The parameter value is No in the other conditions. The short call threshold, short call threshold (MOC), and short call threshold (MTC) are set by engineers during task creation.
Issue 01 (2013-07-15)
2165
Range N/A
Unit N/A
Description Statistics on SQIs 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. 2. The RNC can statistics based on the average SQI value and divides signal quality into different levels according to SQI values: RAN14.0: Excellent (SQI<= (400,500]), Good (SQI<= (300,400]), Accept (SQI<= (200,300]), Poor (SQI<= (100,200]), Bad (SQI<=[0,100]). RAN13.0 and earlier: Good (SQI <= (300,500]), Accept (SQI <= (200,300]), Bad (SQI <=(0,200]). The segment intervals of levels can be modified by running the SET USQICOUNT command on the RNC.
[0,500]
N/A
Yes No
N/A
If SQI average < Abnormal SQI threshold, The value of this parameter is Yes. Otherwise, the value is No. The abnormal SQI threshold is set by engineers during task creation.
[0,100]
Proportion of voice quality with SQI as Excellent from RAB setup to RAB release.
Issue 01 (2013-07-15)
2166
Param eter >>Radi o of Good SQIs (%) >>Radi o of Accept SQIs (%) >>Radi o of Poor SQIs (%) >>Radi o of Bad SQIs (%) >BLER Statistic Info
Range [0,100]
Unit %
Description Proportion of voice quality with SQI as Good from RAB setup to RAB release.
[0,100]
Proportion of voice quality with SQI as Accept from RAB setup to RAB release.
[0,100]
Proportion of voice quality with SQI as Poor from RAB setup to RAB release.
[0,100]
Proportion of voice quality with SQI as Bad from RAB setup to RAB release. Statistics on BLERs. 1. Block error rate (BLER) indicates signal quality on the 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%.
N/A
N/A
[0,+)
Num ber
N/A
Issue 01 (2013-07-15)
2167
Param eter >Statist ics on Last Receive d Blocks >>Num ber of UL Total Blocks (1~5)
Range N/A
Unit N/A
Description Statistics on received blocks before link release. The statistical period is 2.56 seconds.
[0,+)
Num ber
Total number of UL blocks received within the five periods before link release. The parameter value is displayed 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.
[0,+)
Num ber
Number of UL error blocks received within the five periods before link release. The parameter value is displayed in this format: Number of UL error blocks received in period 1/ Number of UL error blocks received in period 2/.../Number of UL error blocks received in period 5.
N/A
N/A
Statistics on uplink one-way audio. 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.
N/A
N/A
Time when uplink one-way audio occurs. Cell when uplink one-way audio occurs.
N/A
N/A
Issue 01 (2013-07-15)
2168
Range N/A
Unit N/A
Description Statistics on downlink one-way audio. The downlink one-way audio problems fall into two types: 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. 2. The RNC records a downlink one-way audio problem when it detects a large BLER value. This function is available only when a VIP subscriber enables periodic DL BLER reporting. The RNC records a maximum of the first three downlink one-way audio problems during each call of a UE.
N/A
N/A
Time when a downlink one-way audio problem occurs. Cell when a downlink one-way audio problem occurs. Statistics on noises. 1. The RNC records a noise problem. 2. The RNC records only the first one noise problem during each call of a UE.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
N/A
N/A
Time when a noise problem occurs. Cell when a noise problem occurs.
N/A
N/A
Issue 01 (2013-07-15)
2169
Issue 01 (2013-07-15)
2170
Range N/A
Unit N/A
Description Time for requesting RAB setup. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT REQUEST message. Incoming migration: Timestamp in the RELOCATION COMPLETE message. Inter-RAT handover: Timestamp in the HANDOVER TO UTRAN COMPLETE message.
N/A
Cell on which RAB setup is requested. The parameter value is displayed in the following format: RNC 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.
[0,+)
Seco nd
Time when RAB setup completes. The statistical points are as follows: RAB setup: Timestamp in the RAB ASSIGNMENT RESPONSE message. Incoming migration: The time is not recorded. Inter-RAT handover: The time is not recorded.
N/A
Best cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
Issue 01 (2013-07-15)
2171
Range N/A
Unit N/A
Description Serving cell on which RAB setup completes. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Information about DRDs during RAB setup, recording the last three DRDs at most. The N DRD record.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Target cell of the current DRD. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
N/A
DRD failure cause. For details, see the Failure Cause tab page.
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)"
N/A
Error type.
Issue 01 (2013-07-15)
2172
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
N/A
Type of an uplink or downlink data transmission channel after RAB setup. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
2173
Range [0,+)
Unit bps
Description DL/UL 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. In which, If UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/ s. If UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>UL/ [0,+) DL RAB Negotia ted Rate Overlo Yes w UL No RAB Negotia ted Rate
bps
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. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
2174
Param eter
Range
Unit N/A
Description If "Overlow DL RAB Negotiated Rate" is smaller than "Overlow DL RAB Negotiated Rate Threshold", the record has the problem that the overlow DL RAB vegotiated rate is too small. The abnormal threshold is set when creating tasks.
>RAB Setup Result >RAB Setup Failure Time >RAB Setup Failure Cause >>Error Type
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
N/A
Error type.
>>Error Reason
N/A
Error reason.
N/A
[0,+)
Seco nd
RAB setup delay = Time when RAB setup completes - Time when RAB setup is requested.
Issue 01 (2013-07-15)
2175
Range Yes No
Unit N/A
Description Overlong RAB setup delay occurs when the RAB setup delay exceeds the overlong delay threshold limit. The overlong delay threshold is set by engineers during analysis task creation.
[0,+)
Seco nd
1.When the following scene occurs, it displays "N/A". Scene: the first RAB after the RAB (Non-RRC) setup. 2.When the following scene occurs, it displays the result value. Scene: the first RAB after the RAB (RRC) setup. Call connection delay = Time when RAB setup completes Time when RRC setup is requested. Call connection delay = RAB setup delay + RRC setup delay.
Yes No
N/A
1.When the following scene occurs, it displays "N/A". Scene: the first RAB after the RAB (Non-RRC) setup. 2.When the following scenes occur, it displays the result value. Scene: the first RAB after the RAB (RRC) setup; and "RRC Setup Flag(MOC/MTC)" is "MOC"; and "Call Setup Delay" is larger than "Latency on Call Connection (MOC) ". Scene: the first RAB after the RAB (RRC) setup; and "RRC Setup Flag(MOC/MTC)" is "MTC"; and "Call Setup Delay" is smaller than "Latency on Call Connection (MTC) ". 3.When the other scene occurs, it displays "No". The threshold is set by engineers during analysis task creation.
Issue 01 (2013-07-15)
2176
Range N/A
Unit N/A
Description Time of service request. That is, when the system receives the Service Request timestamp. 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 COMPLETE message Timestamp in the RADIO BEARER RECONFIGURATION message.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Seco nd
>Sched uling Priority >>Allo cation/ Retenti on Priority >>>Pri ority Level
N/A
N/A
Scheduling priority during RAB setup. Allocation/retention priority. For details, see 3GPP 25.413-9.2.1.3.
N/A
N/A
[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.
N/A
2177
Param eter >>>Pre emptio n Vulnera bility >>>Qu euing Allowe d >>Traff ic Handlin g Priority
Unit N/A
Description Whether resources of the current RAB can be preempted by other RABs.
N/A
N/A
Priority level in the allocation and retention of system resources. For details, see 3GPP 25.433-9.2.1.1A. 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.
[0,15]
N/A
HS-DSCH scheduling priority. For details, see 3GPP 25.433-9.2.1.53H. The value range is [0,15]. A larger value indicates higher priority.
N/A
N/A
Issue 01 (2013-07-15)
2178
Range 1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
Unit N/A
>Single -RAB Abnor mal Release Indicato r >Multi pleRAB Abnor mal Release Indicato r >RAB Release Time
False True
N/A
False True
N/A
N/A
N/A
Time when RAB release completes. The statistical points are as follows: Normal release and CN abnormal release: RAB release time = Timestamp in the IU RELEASE COMMAND or RAB ASSIGNMENT REQUEST message.
>RAB Duratio n
[0,+)
Issue 01 (2013-07-15)
2179
Range N/A
Unit N/A
Description Best cell before RAB release. The parameter value is displayed in the following format: RNC 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.
N/A
N/A
Serving cell before RAB release. The parameter value is displayed in the following format: RNC 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.
UL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH DL transport channel type: DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
N/A
Type of an uplink or downlink data transmission channel before RAB release. The channel types are defined by Huawei.
Issue 01 (2013-07-15)
2180
Range [0,+)
Unit kbps
Description UL/DL RB rate after RAB setup and before RAB release. The parameter value is displayed in the format of UL RB bitrate after RAB setup/DL RB bitrate after RAB setup. In which, If UL is carried on RACH, UL RB bitrate after RAB setup = 8000 bit/ s. If UL is carried on PCH, UL RB bitrate after RAB setup = 0 bit/s. When UL is carried on the other channels, UL RB bitrate after RAB setup varies according to site conditions. When DL is carried on FACH, DL RB bitrate after RAB setup = 8000 bit/s. When DL is carried on PCH, DL RB bitrate after RAB setup = 0 bit/ s. When DL is carried on the other channels, DL RB bitrate after RAB setup varies according to site conditions.
>DP Deactiv ate Cause >RAB Release Failure Cause >>Error Type
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. Cause of abnormal RAB release.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Error type.
Issue 01 (2013-07-15)
2181
Range For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". N/A
Unit N/A
N/A
Time when RAB release fails. That is, when the system receives the following timestamp: IU RELEASE REQUEST RAB RELEASE REQUEST
RAB Process Info >PDP Activat e Request Time >PDP Activat e Ack Time >PDP Deactiv ate Time >BLER Statistic Info
N/A
N/A
N/A
N/A
N/A
N/A
Timestamp in the PDP ACTIVIATE ACKNOWLEDGE message. Timestamp in the DEACTIVATE PDP CONTEXT REQUEST message. Statistical information about BLERs. 1. Block error rate (BLER) indicates signal quality on the 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%.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2182
Param eter >>Time s UL Service BLER Falls into Levels 1 to 6 >Statist ics on Last Receive d Blocks >>Num ber of UL Total Blocks (1~5)
Range [0,+)
Description N/A
N/A
N/A
Statistics on received blocks before link release. The statistical period is 2.56 seconds.
[0,+)
Num ber
Total number of UL blocks received within the five periods before link release. The parameter value is displayed 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.
[0,+)
Num ber
Number of UL error blocks received within the five periods before link release. The parameter value is displayed in this format: Number of UL error blocks received in period 1/ Number of UL error blocks received in period 2/.../Number of UL error blocks received in period 5.
N/A
N/A
[0,+)
Num ber
Number of uplink radio bearer resets after multiple RLC retransmissions fail in acknowledged mode.
Issue 01 (2013-07-15)
2183
Range [0,+)
Description Number of downlink radio bearer resets after multiple RLC retransmissions fail in acknowledged mode. Proportion that the amount of transmission data is zero. HSDPA is High Speed Downlink Packet Access for short. This counter is available only in versions earlier than BSC V900R013.
[0,100]
>HSDP A PDCP UL data amount >HSDP A PDCP DL data amount >Bytes of HSDP A MAC-d flow (suffici ent UE resourc es)
[0,+)
KB
Amount of uplink data at the packet data convergence layer of the HSDPA service.
[0,+)
KB
Amount of downlink data at the packet data convergence layer of the HSDPA service.
[0,+)
KB
Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are sufficient for the HSDPA service. That is, the amount of data of a UE sent on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
>Durati on for sending HSDP A MAC-d flow (suffici ent UE resourc es)
[0,+)
Duration for sending HSDPA MAC-d flow when the data resources of a UE are sufficient for the HSDPA service. That is, the duration for sending data of a UE on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
Issue 01 (2013-07-15)
2184
Param eter >Bytes of HSDP A MAC-d flow (insuffi cient UE resourc es) >Durati on for sending HSDP A MAC-d flow (insuffi cient UE resourc es) >Avera ge Downli nk Rate
Range [0,+)
Unit KB
Description Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are insufficient for the HSDPA service. That is, the amount of data of a UE sent on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
[0,+)
Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient for the HSDPA service. That is, the duration for sending data of a UE on the downlink over the Iu interface of the PDCP layer for the HSDPA service. This counter is available only in BSC V900R013 and later versions.
[0,+)
Kbps
Average downlink rate of the HSDPA service = (Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are sufficient + Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are insufficient) /(Duration for sending HSDPA MAC-d flow when the data resources of a UE are sufficient + Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient).
Issue 01 (2013-07-15)
2185
Range [0,+)
Description If Average downlink rate of the HSDPA service is smaller than Slow average downlink rate threshold of the HSDPA service, Times of slow average downlink rate + 1. The slow average downlink rate threshold is set by engineers during task creation.
[0,+)
Kbps
Average uplink rate of the HSDPA service = (Number of uplink bytes in HSDPA PDCP /(Duration for sending HSDPA MAC-d flow when the data resources of a UE are sufficient + Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient).
[0,+)
Num ber
If Average uplink rate of the HSDPA service is smaller than Slow average uplink rate threshold of the HSDPA service, Times of slow average uplink rate +1 The slow average uplink rate threshold is set by engineers during task creation.
[0,+)
Kbps
Average downlink rate of the HSDPA service when the data resources are sufficient.
Issue 01 (2013-07-15)
2186
Param eter >DL Averag e Rate Slow (suffici ent resourc es)
Range [0,+)
Description If Average downlink rate of the HSDPA service < Slow average downlink rate threshold of the HSDPA service when the data resources are sufficient, Times of slow average downlink rate when the data resources are sufficient + 1. The slow average downlink rate threshold when the data resources are sufficient is set by engineers during task creation.
[0,+)
Kbps
Average downlink rate of the HSDPA service when the data resources are insufficient = Number of bytes sent in HSDPA MAC-d flow when the data resources of a UE are insufficient /Duration for sending HSDPA MAC-d flow when the data resources of a UE are insufficient.
[0,+)
Num ber
If Average downlink rate of the HSDPA service < Slow average downlink rate threshold of the HSDPA service when the data resources are insufficient, Times of slow average downlink rate when the data resources are insufficient + 1. The slow average downlink rate threshold when the data resources are insufficient is set by engineers during task creation.
Issue 01 (2013-07-15)
2187
Range N/A
Unit N/A
Description Time when a signaling message is sent or received. Direction for sending or receiving a signaling message.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
to CN from CN to other RNC from other RNC to NODEB from NODEB to UE from UE to SAS from SAS
N/A
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.
Signali ng Content
N/A
N/A
Measurement Information
Param eter Number Range [0,+) Unit N/A Description Number that uniquely identifies a measurement report (MR). Time when an MR is reported. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
Issue 01 (2013-07-15)
2188
Range Intra-freq measurement type Inter-freq measurement type Inter-RAT measurement type Event MR, such as E1A and so on
Unit N/A
Description MR type.
N/A
N/A
Name of a measurement object reported in an MR. The parameter value is displayed in the following format: RNC 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.
P-SC
[0,512]
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[-24,0]
dB
Ratio of energy per modulating bit to the noise spectral density (Ec/ No). For details, see 3GPP 25.331. Received signal code power (RSCP). For details, see 3GPP 25.331. Received signal strength indicator (RSSI) of a GSM carrier. For details, see 3GPP TS 45.008.
[-115,-25]
dBm
N/A
dBm
[0,97]
dBm
Reference signal received power (RSRP). For details, see 3GPP 36.133.
Issue 01 (2013-07-15)
2189
Range [0,33]
Unit dB
Description Reference signal received quality (RSRQ). For details, see 3GPP 36.133. Transmit power of a UE.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
UE TX Power
N/A
N/A
Mobility Analysis
Param eter Number Range [0,+) Unit N/A Description Number of a handover during a call. Whether a handover is abnormal. If a red exclamation mark is displayed in this column, the handover is abnormal. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Abnorm al
! Blank
N/A
Issue 01 (2013-07-15)
2190
Range Softer handover Soft handover Intra-freq hard handover Inter-freq hard handover Inter-system incoming handover Inter-system outgoing handover/CS system handover Inter-system outgoing handover/Cell change order PS system handover Inter-system outgoing handover/ Enhanced PS system handover Inter-system outgoing handover/CS and PS system handover Inter-system outgoing handover/UE generated Incoming migration/ Static reloc in Incoming migration/HHO reloc in Incoming migration/Cell update reloc in
Unit N/A
Description Type of mobility analysis. Currently, the system supports the following mobility analysis types: Soft handover Hard handover Incoming inter-RAT handover Outgoing inter-RAT handover Incoming migration Outgoing migration Cell update Channel handover
Issue 01 (2013-07-15)
2191
Param eter
Unit
Description
Supported NE Version
N/A
N/A
Start time.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
Overlon g Interval
Yes No
N/A
If Interval > Overlong xxx delay threshold, The value of this parameter is Yes. Otherwise, the value is 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 handover delay threshold Overlong incoming handover delay threshold Overlong outgoing handover delay threshold Overlong channel handover delay threshold
End Time
N/A
N/A
End time.
Issue 01 (2013-07-15)
2192
Range converage based load based but blind handover load based and measurement based forced handover emergency handover
Unit N/A
MutiRAB Info
1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS
N/A
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
Active Set
N/A
Measurement type.
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. Ratio of energy per modulating bit to the noise spectral density (Ec/ No). For details, see 3GPP 25.331. Received signal code power (RSCP). For details, see 3GPP 25.331.
[-24,0]
dB
[-115,-25]
dBm
Issue 01 (2013-07-15)
2193
Range DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
N/A
[0,+)
kbps
UL RB rate when occuring the channel handover. DL RB rate when occuring the channel handover. Destination cell information.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
bps
N/A
N/A
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 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. Ratio of energy per modulating bit to the noise spectral density (Ec/ No) of 3G target cell. For details, see 3GPP 25.331.
>Ec/NO (dB)
[-24,0]
dB
Issue 01 (2013-07-15)
2194
Param eter >RSCP (dBm) >Target Cell Operati on >Target Cell Operati on Time InterRAT carrier RSSI (dBm) RSRP
Range [-115,-25]
Unit dBm
Description Received signal code power (RSCP) of 3G target cell. For details, see 3GPP 25.331. Target cell operation of the 3G target cell when occuring the soft handover. Target cell operation time of the 3G target cell when occuring the soft handover. Received signal strength indicator (RSSI) of a GSM carrier of 2G target cell. For details, see 3GPP TS 45.008. Reference signal received power (RSRP) of LTE target cell. For details, see 3GPP 36.133. Reference signal received quality (RSRQ) of LTE target cell. For details, see 3GPP 36.133. Source UL channel type when occuring the channel handover.
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RL ADD RL DEL
N/A
N/A
N/A
N/A
dBm
[-140,-43]
dBm
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
RSRQ
[-19.5,-2.5]
dB
N/A
Issue 01 (2013-07-15)
2195
Range DCH FACH RACH HSDSCH EDCH PCH EFACH ERACH EPCH
Unit N/A
[0,+)
bps
UL RB rate when occuring the channel handover. DL RB rate when occuring the channel handover. Failure cause.
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
[0,+)
bps
N/A
N/A
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Error type.
>Error Reason
N/A
Error reason.
Issue 01 (2013-07-15)
2196
Service Analysis(RAB)
Param eter Numbe r Abnor mal Range [0,+) Unit N/A Description Record number of RAB service. Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
! Blank
N/A
Whether a servive record is abnormal. If a red exclamation mark is displayed in this column, the record is abnormal.
! Blank
N/A
Whether a servive record of RAB setup is abnormal. If a red exclamation mark is displayed in this column, the record is abnormal.
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)". CS_AMR CS_VP CS_OTHER PS_GENERAL PS_HSDPA PS_HSUPA PS_HSPA
N/A
N/A
N/A
N/A
BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2197
Param eter Best Cell on RAB Setup Serving Cell on RAB Setup Peer Informa tion
Range N/A
Unit N/A
Supported NE Version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version BSC6900 V900R013C00 or later version
N/A
N/A
N/A
N/A
Peer information. If the service is RAB on CS domain, it displays "Peer MSISDN". If the service is RAB on PS domain, it displays N/A.
1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS ...
N/A
! Blank
N/A
Whether a servive record of RAB release is abnormal. If a red exclamation mark is displayed in this column, the record that "Single-RAB Abnormal Release Indicator" or "MultipleRAB Abnormal Release Indicator" is YES.
For details, see "Appendix: Exception Cause Classification / Enumeration Values of Failure Cause (UMTS)".
N/A
Issue 01 (2013-07-15)
2198
Unit N/A
Description Cause of the call is disconnected, that is the cause value of NAS Disconnect message. The value is valid only on RAB CS domain.
N/A
Cause of the PDP is deactive, that is the cause value of Deactivate PDP context request message. The value is valid only on RAB PS domain.
RAB Release Time Best Cell Before RAB Release Serving Cell Before RAB Release MultiRAB Informa tion on RAB Release
N/A
N/A
N/A
N/A
N/A
N/A
1CS 1CS + 1PS 1CS + 2PS 1CS + 3PS 2CS 2CS + 1PS 2CS + 2PS 1PS 2PS 3PS 4PS ...
N/A
[0,+)
Seco nd
RAB setup delay = Time when RAB setup completes - Time when RAB setup is requested.
Issue 01 (2013-07-15)
2199
Range [0,+)
Description RAB duration = Time when RAB is released - Time when RAB setup completes Service duration.
[0,+)
BSC6900 If the service is RAB on CS domain, V900R013C00 it displays the service duration (that or later version is call time). If the service is RAB on PS domain, it displays N/A (that is not involved).
[0,+)
Byte
Total uplink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total throughput on uplink of RAB process.
[0,+)
Seco nd
Total uplink transmission duration. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total transmission duration on uplink of RAB process.
[0,+)
Kbps
Average uplink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays average throughput on uplink of RAB process. Average uplink throughput = Total uplink throughput/Total uplink transmission duration
Yes No
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. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
2200
Range [0,+)
Unit Byte
Description Total downlink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total throughput on downlink of RAB process.
[0,+)
Seco nd
Total downlink transmission duration. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays total transmission duration on downlink of RAB process.
[0,+)
Kbps
Average downlink throughput. If the service is RAB on CS domain, it displays N/A (that is not involved). If the service is RAB on PS domain, it displays average throughput on downlink of RAB process. Average downlink throughput = Total downlink throughput/Total downlink transmission duration
Yes No
N/A
If "Average Downlink Throughput" is smaller than "Average Downlink Throughput Threshold", the record has the problem that the average downlink throughput is too small. The abnormal threshold is set when creating tasks.
Issue 01 (2013-07-15)
2201
N/A
N/A
N/A
ms
N/A
CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-25 5 0-25 5
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR.
N/A
Issue 01 (2013-07-15)
2202
User Information
Param eter User ID:Alia s Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Termin al Model IMEITAC N/A N/A Model of the terminal that initiates a service. IMEI-TAC of the terminal that initiates a service. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
Procedure Information
Param eter Access Type Ran ge N/A Unit N/A Description Radio access network (RAN) type for the signaling procedure. This parameter can be any of the following: GPRS UMTS LTE CHR Type N/A N/A Type of the signaling procedure. This parameter can be any of the following: SM MM Procedu re Type N/A N/A Name of a signaling procedure. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
2203
Ran ge N/A
Unit N/A
Description Procedure initiating party (UE or MME) and cause. For details, see the Description of Procedure Initiating Causes in the appendix.
N/A
P-TMSI received from a terminal when a procedure is initiated. P-TMSI that the network allocates to a terminal. If a procedure does not involve two routing areas, the field indicates the routing area where the procedure is initiated. If a procedure involves in two routing areas, the field indicates the new routing area.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
Cell
N/A
N/A
Old RAC
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. Indicates whether a procedure requires authentication. Indicates whether a procedure requires IMEI check. Indicates whether a procedure requires P-TMSI reallocation.
Authent ication Flag IMEI Check Flag PTMSI Realloc ation Flag Externa l Cause Old SGSN Address
N/A
N/A
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
If a procedure involves two SGSNs, the field indicates the IP address of the old SGSN.
Issue 01 (2013-07-15)
2204
Ran ge N/A
Unit N/A
Description APN selection mode. This parameter can be any of the following: MS & Network Verified MS not Verified Network not Verified
N/A
SN of a CHR that is sent to the billing center. Charging attribute of a UE. This parameter can be any of the following: Unspecified Hot billing Charging Flat rate Charging Prepaid Charging Normal Charging
N/A
N/A
N/A
Allocation/retention priority. This parameter can be any of the following: High priority Normal priority Low priority
N/A
N/A
Subscribed reliability class. This parameter can be any of the following: Subscribed reliability class 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
Issue 01 (2013-07-15)
2205
Ran ge N/A
Unit N/A
Description Subscribed delay class. This parameter can be any of the following: Subscribed delay class Delay class 1 Delay Class 2 Delay Class 3 Delay Class 4 (best effort)
N/A
N/A
Subscribed precedence. This parameter can be any of the following: Subscribed precedence High priority Normal priority Low priority Reserved
N/A
N/A
Subscribed peak throughput. This parameter can be any of the following: Subscribed peak throughput Up to 1 000 octet/s Up to 2 000 octet/s Up to 4 000 octet/s Up to 8 000 octet/s Up to 16 000 octet/s Up to 32 000 octet/s Up to 64 000 octet/s Up to 128 000 octet/s Up to 256 000 octet/s
Issue 01 (2013-07-15)
2206
Ran ge N/A
Unit N/A
Description Subscribed mean throughput. This parameter can be any of the following: Subscribed mean throughput 100 octet/h 200 octet/h 500 octet/h 1000 octet/h 2000 octet/h 5000 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
N/A
N/A
Subscribed delivery of erroneous SDUs. This parameter can be any of the following: No detect('-') Erroneous SDUs are delivered('yes') Erroneous SDUs are not delivered ('no')
Deliver y Order
N/A
N/A
Subscribed delivery order. This parameter can be any of the following: With delivery order ('yes') Without delivery order ('no')
Issue 01 (2013-07-15)
2207
Ran ge N/A
Unit N/A
Description Subscribed traffic class. This parameter can be any of the following: Conversational class Streaming class Interactive class Background class
Maxim um SDU Size Maxim um Bit Rate for Uplink Maxim um Bit Rate for Downli nk SDU Error Ratio
0-25 5
byte
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-86 40
bps
0-25 6000
bps
N/A
N/A
Subscribed SDU error ratio. This parameter can be any of the following: 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
Issue 01 (2013-07-15)
2208
Ran ge N/A
Unit N/A
Description Subscribed residual BER. This parameter can be any of the following: 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
N/A
N/A
Subscribed traffic handling priority. This parameter can be any of the following: Priority level 1 Priority level 2 Priority level 3
Transfe r Delay Guarant eed Bit Rate for Uplink Guarant eed Bit Rate for Downli nk GTP Tunnel Version
0-25 5 0-86 40
ms
Transfer delay.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
bps
0-25 6000
bps
N/A
N/A
GTP tunnel version. This parameter can be any of the following: GTPv0 GTPv1
Issue 01 (2013-07-15)
2209
Ran ge N/A
Unit N/A
Description Type of the PDP requested by a UE. This parameter can be any of the following: IPv4 IPv6 BOTH(IPV4&IPV6) PPP Empty
PDP Address in Use GGSN Address for Signali ng GGSN Address for User Traffic APN
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Access Time
N/A
Issue 01 (2013-07-15)
2210
Rang e N/A
Unit N/A
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-655 35 N/A
ms
N/A
CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
NE Name
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-255
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR.
0-255
N/A
User Information
Parameter User ID:Alias Rang e N/A Uni t N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Terminal Model IMEI-TAC N/A N/A Model of the terminal that initiates a service. IMEI-TAC of the terminal that initiates a service. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
Issue 01 (2013-07-15)
2211
Procedure Information
Parameter Access Type Rang e N/A Uni t N/A Description Radio access network (RAN) type for the signaling procedure. This parameter can be any of the following: GPRS UMTS LTE CHR Type N/A N/A Type of the signaling procedure. This parameter can be any of the following: SM MM Procedure Type N/A N/A Name of a signaling procedure. For details, see the Description of Signaling Procedures in the appendix. N/A N/A Procedure initiating party (UE or MME) and cause. For details, see the Description of Procedure Initiating Causes in the appendix. MS P-TMSI 0-2^3 2-1 0-2^3 2-1 N/A N/A P-TMSI received from a terminal when a procedure is initiated. P-TMSI that the network allocates to a terminal. If a procedure does not involve two routing areas, the field indicates the routing area where the procedure is initiated. If a procedure involves two routing areas, the field indicates the new routing area. Cell N/A N/A Cell where a procedure is initiated. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
Issue 01 (2013-07-15)
2212
Rang e N/A
Uni t N/A
Description 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. Indicates whether an MM procedure requires authentication. Indicates whether an MM procedure requires IMEI check. Indicates whether an MM procedure requires P-TMSI reallocation. Procedure result and failure cause. For details, see the Description of Exception Cause Fields in the appendix.
Authenticati on Flag IMEI Check Flag PTMSI Reallocation Flag External Cause
N/A
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
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.
Begin Time
N/A
Issue 01 (2013-07-15)
2213
Rang e N/A
Unit N/A
Description End time of the signaling procedure. Delay time of a signaling procedure. CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-655 35 N/A
ms
N/A
NE Name Board Subrack No. Board Slot No. Board Proc No.
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-255
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR. Number of the process that generates a CHR.
0-255
N/A
0-655 35
N/A
User Information
Parame ter User ID:Alias Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Termina l Model N/A N/A Model of the terminal that initiates a service. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
2214
Unit N/A
Procedure Information
Parame ter CHR Type Ran ge N/A Unit N/A Description Type of the signaling procedure. This parameter can be any of the following: SM MM Procedur e Type Procedur e Init Cause N/A N/A Name of a signaling procedure. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
N/A
Procedure initiating party (UE or MME) and cause. For details, see the Description of Procedure Initiating Causes in the appendix.
N/A
N/A
PLMN of the eNodeB where a UE is located when a signaling procedure is initiated. ID of the eNodeB where a UE is located when a signaling procedure is initiated. UES1AP connection identification allocated by an MME in a traffic procedure. Time when the UES1AP connection identification is allocated by an MME in a traffic procedure. Tracking area where a terminal is located when a signaling procedure is initiated.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2215
Ran ge N/A
Unit N/A
Description Requested PDN type in a traffic procedure. This parameter can be any of the following: IPV4 IPV6 both(IPV4 & IPV6) unused
APN
N/A
N/A
Requested APN in a traffic procedure. Negotiated cause in a procedure result. Procedure result and failure cause.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
Protocol Cause External Cause Serving Gateway Address PDN Gateway Address PDN Gateway Host Name UE Uplink Max Bandwid th UE Downlin k Max Bandwid th APN Uplink Max Bandwid th
N/A
N/A
N/A
N/A
N/A
N/A
IP address of the Serving Gateway in a signaling procedure. IP address of the PDN Gateway in a signaling procedure. Domain name of the PDN Gateway in a signaling procedure.
N/A
N/A
N/A
N/A
02^32 -1
bit/s
02^32 -1
bit/s
02^32 -1
bit/s
Issue 01 (2013-07-15)
2216
Ran ge 02^32 -1
Unit bit/s
N/A
QCI information allocated by a session. ARP information allocated by a session. Maximum bearer-level uplink bandwidth allocated by a session. Maximum bearer-level downlink bandwidth allocated by a session. Guaranteed bearer-level uplink bandwidth allocated by a session. Guaranteed bearer-level downlink bandwidth allocated by a session.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
ARP
N/A
bit/s
bit/s
bit/s
bit/s
Begin Time
N/A
Issue 01 (2013-07-15)
2217
Ran ge N/A
Unit N/A
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
ms
N/A
CN NE types for the signaling procedure. This parameter can be any of the following: SGSN MME
NE Name Board Subrack No. Board Slot No. Board Proc No.
N/A
N/A
Name of a CN NE.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
Subrack number of the device that generates CHRs. Slot number of the device that generates a CHR. Number of the process that generates a CHR.
N/A
N/A
User Information
Parame ter User ID:Alias Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Terminal Model N/A N/A Model of the terminal that initiates a service. USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
Issue 01 (2013-07-15)
2218
Unit N/A
Procedure Information
Parame ter CHR type Ran ge N/A Unit N/A Description Type of the signaling procedure. This parameter can be any of the following: SM MM Procedu re Type Procedu re Init Cause N/A N/A Name of a signaling procedure. USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version Supported NE Version USN9810 V900R011C01 or later version
N/A
N/A
Procedure initiating party (UE or MME) and cause. For deTACls, see the Description of Procedure Initiating Causes in the appendix.
N/A
N/A
PLMN of the eNodeB where a UE is located when a signaling procedure is initiated. ID of the eNodeB that serves a UE when a signaling procedure is initiated. UES1AP connection identification allocated by an MME in a traffic procedure. Time when the UES1AP connection identification is allocated by an MME in a traffic procedure. Tracking area where a terminal is located when a signaling procedure is initiated.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2219
Parame ter New GUTI PLMN New GUTI MMEGI New GUTI MMEC New GUTI MTMSI Old GUTI PLMN Old GUTI MMEGI Old GUTI MMEC Old GUTI MTMSI Old TAC Target ID PLMN Target ID Target MME UE S1AP ID Target MME S1AP ID Time
Ran ge N/A
Unit N/A
Description PLMN of GUTI allocated by the network in a traffic procedure. MME Group Id of GUTI allocated by the network in a traffic procedure. MME CODE of GUTI allocated by the network in a traffic procedure. M-TMSI of GUTI allocated by the network in a traffic procedure. PLMN of GUTI received from a UE in a traffic procedure. MME Group Id of GUTI received from a UE in a traffic procedure. MME CODE of GUTI received from a UE in a traffic procedure. M-TMSI of GUTI received from a UE in a traffic procedure. ID of the old tracking area in a signaling procedure that involves more than one tracking area. PLMN of the target eNodeB in a signaling procedure that involves more than one eNodeB. ID of the target eNodeB in a signaling procedure that involves more than one eNodeB. Target UES1AP connection identification allocated by an MME in a traffic procedure. Time when the target UES1AP connection identification is allocated by an MME in a traffic procedure.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
0-655 35 0-255
N/A
N/A
N/A
N/A
0-655 35 0-255
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2220
Parame ter Target TAC Protocol Cause External Cause Access Type
Ran ge N/A
Unit N/A
Description ID of the target tracking area in a signaling procedure that involves more than one tracking area. Protocol cause value in a procedure result. Procedure result and failure cause.
Supported NE Version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
Radio access network (RAN) type for the signaling procedure. This parameter can be any of the following: GPRS UMTS LTE
Serving Gateway Address Serving Gateway Host Name MS PTMSI Allocate d PTMSI GU RAC
N/A
N/A
IP address of the Serving Gateway in a signaling procedure. Domain name of the Serving Gateway in a signaling procedure.
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
P-TMSI received from a terminal when a procedure is initiated. P-TMSI that the network allocates to a terminal. 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. 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 CGI of the target cell. Otherwise, the field is empty.
N/A
N/A
GU CI
N/A
N/A
Issue 01 (2013-07-15)
2221
Ran ge N/A
Unit N/A
Description If a UE is handed over from a 2G/3G network to a LTE network or the location of the UE is updated, the field is the RAC of the old routing area. Otherwise, the field is empty. Indicates whether an MM procedure requires authentication. Indicates whether an MM procedure requires IMEI check. Indicates whether an MM procedure requires P-TMSI reallocation. If a procedure involves two SGSNs, the field indicates the IP address of the old SGSN.
Authenti cation Flag IMEI Check Flag PTMSI Realloca tion Flag Old SGSN Address
N/A
USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version USN9810 V900R011C01 or later version
N/A
N/A
N/A
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.
N/A
Issue 01 (2013-07-15)
2222
Unit N/A
NE Name
N/A
N/A
Name of a CN NE.
User Information
Param eter User ID:Alia s Ran ge N/A Unit N/A Description User ID is an ID that the Nastar allocates to the system and is consistent with the user ID in the complaint analysis support task. Alias is a user name and consistent with that in the complaint analysis support task. Supported NE Version UGW9810 V900R011C01 or later version
Procedure Information
Param eter Proced ure Type APN Rang e N/A Unit N/A Description Name of a signaling procedure. Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
Issue 01 (2013-07-15)
2223
Rang e NA UTR AN GER AN WLA N GAN HSP A Evolu tion EUT RAN
Unit N/A
N/A
N/A
Cause of the exception carried in an Access message. For details, see the Description of Exception Cause in the appendix.
PDP Type
N/A
MSIP
N/A
N/A
MS IP V4
N/A
N/A
Issue 01 (2013-07-15)
2224
Param eter MS IP V6 SGSN Addres s for Signali ng SGSN Addres s for Data GGSN Addres s for Signali ng GGSN Addres s for Data Protoco l Version
Rang e N/A
Unit N/A
Description IPv6 address allocated to the subscriber's MS IPv4 address for configuring the control plane of the SGSN that the subscriber's MS accesses
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
IPv4 address for configuring the user plane of the SGSN that the subscriber's MS accesses IPv4 address for configuring the control plane of the GGSN that the subscriber's MS accesses
N/A
N/A
N/A
N/A
IPv4 address for configuring the user plane of the GGSN that the subscriber's MS accesses Version of the GTP protocol
N/A
Issue 01 (2013-07-15)
2225
Unit N/A
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. Information about the PLMN served by the access SGSN Location area where the signaling procedure is triggered Routing area where the signaling procedure is triggered Serving area where the signaling procedure is triggered Cell where the signaling procedure is triggered IPv6 address for configuring the control plane of the SGSN that the subscriber's MS accesses
UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
RAC
N/A
N/A
SAC
N/A
N/A
CI
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2226
Param eter GGSN IPv6 Addres s for Signali ng SGSN IPv6 Addres s for Data GGSN IPv6 Addres s for Data NSAPI
Rang e N/A
Unit N/A
Description IPv6 address for configuring the control plane of the GGSN that the subscriber's MS accesses
N/A
N/A
IPv6 address for configuring the user plane of the SGSN that the subscriber's MS accesses
N/A
N/A
IPv6 address for configuring the user plane of the GGSN that the subscriber's MS accesses
N/A
N/A
Identity of the service access point (SAP) in the network layer Identifies whether an activation is a first or second activation
Activati on Type
N/A
N/A
N/A
Identity of the GTP-C tunneling protocol Marks different charging characteristics. For details, see 5.1.2.2.7 in 3GPP TS 32.298. 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.
UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
0-2^3 2-1
N/A
Issue 01 (2013-07-15)
2227
Rang e 0-2^3 2-1 SSG N MME GGS N SGW PGW SGW +PG W
Unit N/A
Description Unique No. of each service procedure in the whole procedure for a subscriber Initiator of the signaling message recorded in the CHR
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
Slot
N/A
N/A
Logical board No. of the device that processes the CHR Logical CPU No. of the device that processes the CHR SPU group No. of the device that processes the CHR SPU instance No. of the device that processes the CHR MCC and MNC of the subscriber's serving network CGI information, including MCC, MNC, LAC, and CI SAI information, including MCC, MNC, LAC, and SAC
UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
CPU
N/A
N/A
SPU Group SPU Instanc e Serving Networ k ULI CGI ULI SAI
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2228
Param eter ULI RAI ULI TAI ULI ECGI ULI LAI Peer IPV4 Addres s for Signali ng Peer IPV4 Addres s for Data Local IPV4 Addres s for Signali ng Local IPV4 Addres s for Data Peer IPV6 Addres s for Signali ng
Rang e N/A
Unit N/A
Description RAI information, including MCC, MNC, LAC, and RAC TAI information, including MCC, MNC, and TAC ECGI information, including MCC, MNC, and ECI LAI information, including MCC, MNC, and LAC IPv4 address for configuring the control plane of the CN NE interconnected to this NE
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
IPv4 address for configuring the user plane of the CN NE interconnected to this NE
N/A
N/A
N/A
N/A
N/A
N/A
IPv6 address for configuring the control plane of the CN NE interconnected to this NE
Issue 01 (2013-07-15)
2229
Param eter Peer IPV6 Addres s for Data Local IPV6 Addres s for Signali ng Local IPV6 Addres s for Data Proced ure Transac tion ID (PTI)
Rang e N/A
Unit N/A
Description IPv6 address for configuring the user plane of the CN NE interconnected to this NE
N/A
N/A
N/A
N/A
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.
Issue 01 (2013-07-15)
2230
Rang e MS or netwo rk provi ded APN, subsc ribed verifi ed MS provi ded APN, subsc riptio n not verifi ed Netw ork provi ded APN, subsc riptio n not verifi ed
Unit N/A
PDN Type
N/A
N/A
N/A
ID of the default bearer. This parameter can also be used to identify the PDN connection. ID of all bearers (including the default bearer) for the PDN connection
N/A
N/A
Issue 01 (2013-07-15)
2231
Param eter Bearer QoS PCI Bearer QoS PL Bearer QoS PVI Bearer QoS QCI Bearer QoS MBRU Bearer QoS MBRD Bearer QoS GBRU Bearer QoS GBRD UE Time Zone Protoco l Cause Flow QoS QCI Flow QoS MBRU Flow QoS MBRD
Rang e N/A
Unit N/A
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Standard cause value carried in the response message QCI in the Flow QoS parameter
N/A
N/A
N/A
N/A
N/A
N/A
Issue 01 (2013-07-15)
2232
Param eter Flow QoS GBRU Flow QoS GBRD UL Total Volume DL Total Volume Total Volume First URL MS Side Port of First URL Networ k Side Port of First URL
Rang e N/A
Unit N/A
Supported NE Version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version UGW9810 V900R011C01 or later version
N/A
N/A
byte
Uplink traffic volume recorded in the CHR Downlink traffic volume recorded in the CHR Total traffic volume recorded in the CHR First 20 bytes of the first URL that the subscriber visits during a service procedure TCP/UDP port No. (on the UE side) of the first URL that the subscriber visits during a service procedure
byte
byte
N/A
N/A
N/A
N/A
N/A
TCP/UDP port No. (on the network side) of the first URL that the subscriber visits during a service procedure
Issue 01 (2013-07-15)
2233
N/A
N/A
N/A N/A N/A N/A N/A N/A High TA Low uplink level on the TCH Uplink interference on the TCH
Issue 01 (2013-07-15)
2234
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Poor uplink quality of the TCH Sudden decrease of the uplink level Low downlink level on the TCH Downlink interference on the TCH Poor downlink quality of the TCH Sudden decrease of the downlink level Low uplink and downlink level on the TCH Uplink and downlink interference on the TCH Poor uplink and downlink quality of the TCH Any other Um interface-related fault Transmission fault CN fault Peer fault Other causes N/A N/A N/A N/A N/A High TA Low uplink level on the TCH Uplink interference on the TCH
Issue 01 (2013-07-15)
2235
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Poor uplink quality of the TCH Sudden decrease of the uplink level Low downlink level on the TCH Downlink interference on the TCH Poor downlink quality of the TCH Sudden decrease of the downlink level Low uplink and downlink level on the TCH Uplink and downlink interference on the TCH Poor uplink and downlink quality of the TCH Any other Um interface-related fault Transmission fault CN fault Peer fault Other causes N/A N/A N/A N/A N/A
Poor quality on the Um interface or fault of the terminal System resource congestion
N/A
Issue 01 (2013-07-15)
2236
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Transmission fault CN fault Other causes N/A N/A N/A N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault
N/A
N/A
Issue 01 (2013-07-15)
2237
Dom ain
Servi ce Type
Abnormal Type
RANCS
Call
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
Poor quality on the Um interface or fault of the terminal System resource congestion Transmission fault CN fault Other causes
N/A
N/A N/A N/A N/A High TA Low uplink level on the TCH Uplink interference on the TCH Poor uplink quality of the TCH Sudden decrease of the uplink level
Issue 01 (2013-07-15)
2238
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Low downlink level on the TCH Downlink interference on the TCH Poor downlink quality of the TCH Sudden decrease of the downlink level Low uplink and downlink level on the TCH Uplink and downlink interference on the TCH Poor uplink and downlink quality of the TCH Any other Um interface-related fault Transmission fault CN fault Peer fault Other causes N/A N/A N/A N/A N/A
Abnormal Delay
Overlong access time (MOC) Overlong access time (MTC) Overlong setup time (MOC) Overlong setup time (MTC)
N/A
N/A N/A
Issue 01 (2013-07-15)
2239
Dom ain
Servi ce Type
Abnormal Type
Abnormal Sub-type Short calls (MOC) Short calls (MTC) N/A N/A N/A
Poor quality on the Um interface Bad DL HQI Bad UL HQI Bad UL VQI Uplink oneway audio Downlink oneway audio DL/UL no audio Downlink crosstalk Uplink crosstalk
N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
SMS
N/A N/A
RANPS
PS
Setup Failure
Case3: Attach fail Case2: PDP active fail Case3: No service interaction timeout
Service Interruption
N/A
Issue 01 (2013-07-15)
2240
Dom ain
Servi ce Type
Abnormal Type
Step1: Service interaction timeouts Step2: Service interaction with long latency
N/A
N/A
N/A
N/A N/A
Issue 01 (2013-07-15)
2241
Interface
Key Signaling 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 ROUTING AREA UPDATE ACCEPT ROUTING AREA UPDATE REJECT ROUTING AREA UPDATE COMPLETE AUTHENTICATION AND CIPHERING REJECT AUTHENTICATION AND CIPHERING REQUEST AUTHENTICATION AND CIPHERING RESPONSE
Issue 01 (2013-07-15)
2242
Interface
Key Signaling 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 SM-STATUS Channel Request Packet Channel Req Um Packet Control Acknowledgement (NB) Packet Control Ack (AB) Packet Cell Change Failure Packet Resource Request
Issue 01 (2013-07-15)
2243
Interface
Key Signaling 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 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 Downlink RLC Data header
Issue 01 (2013-07-15)
2244
N/A RRC Setup Failure RRC Setup Failure (Service-CS) RRC Setup Failure (Service-PS)
RRC Abnormal Release Overlong RRC Setup Delay (Nonservice) 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
HO Problem
Soft Handover Failure Hard Handover Failure Cell Update Failure Channel Handover Failure Migration Failure Inter-RAT Handover Failure PDP Activate Failure
Issue 01 (2013-07-15)
2245
Doma in RANCS
Abnormal CauseClassificatio n Nonexception Setup Failure Abnormal Release Service Quality Problem
Abnormal Cause-Subclassification
RAN 13.0
RAN 14.0
N/A CS RAB Setup Failure CS RAB Abnormal Release 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) Overlong RAB Connection Delay (Alerting)(MOC) Overlong RAB Connection Delay (Connect Ack)(MOC)
ShortCall Problem
VP
N/A CS RAB Setup Failure CS RAB Abnormal Release Overlong RRC Setup Delay
Issue 01 (2013-07-15)
2246
Doma in
Service Type
Abnormal CauseClassificatio n
Abnormal Cause-Subclassification Overlong RAB Connection Delay (MTC) Overlong RAB Connection Delay (MOC) Overlong RAB Connection Delay (Alerting)(MTC) Overlong RAB Connection Delay (Connect Ack)(MTC) Overlong RAB Connection Delay (Alerting)(MOC) Overlong RAB Connection Delay (Connect Ack)(MOC)
RAN 13.0
RAN 14.0
ShortCall Problem
SMS
N/A N/A PS RAB Setup Failure PS RAB Abnormal Release Overlow Average Downlink Throughput Overlow Average Uplink Throughput Average Downlink Transmission Rate Slow Average Uplink Transmission Rate Slow
Issue 01 (2013-07-15)
2247
Doma in
Service Type
Abnormal CauseClassificatio n
Abnormal Cause-Subclassification DL Average Rate Slow(sufficient resources) DL Average Rate Slow (insufficient resources)
RAN 13.0
RAN 14.0
Delay Problem
Overlong RRC Setup Delay Overlong RAB Connection Delay (MTC) Overlong RAB Connection Delay (MOC)
Other RANMulti Multi Service Multi Service (CS Included) Multi Service(PS Only)
Issue 01 (2013-07-15)
2248
ErrType Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure
ErrReason DL CE Congestion UL_DL CE Congestion UL CE Congestion DL CE Congestion UL_DL CE Congestion UL CE Congestion DL CE Congestion UL_DL CE Congestion UL Iub Band Congestion DL Iub Band Congestion UL_DL Iub Band Congestion UL Iub Band Congestion DL Iub Band Congestion UL_DL Iub Band Congestion DL Power Congestion Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure
Issue 01 (2013-07-15)
2249
ErrType Iub Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iub Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Iur Interface Failure Radio Resource Congestion Uu Interface Failure Uu Interface Failure
ErrReason Iub AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iub AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Iur AAL2/AL Establishment Failure Overload Control SRB Reset TRB Reset
Issue 01 (2013-07-15)
2250
ErrType Uu Interface Failure Uu Interface Failure Radio Resource Congestion Uu Interface Failure Uu Interface Failure Iu Relocation Failure Iu Relocation Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iu Relocation Failure Iub Interface Failure Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Radio Resource Congestion Iub Interface Failure Iub Interface Failure Iub Interface Failure
ErrReason SRB Reset TRB Reset Preempted User Due To Congestion Timer Expired Timer Expired Iu Relocation Preparation Failure Timer Relocation Preparation Expiry Iu Relocation Execution Timer Expiry Timer Expired Timer Expired Timer Expired Iu Relocation Preparation Iu Release Command Iu Relocation Execution Timer Expiry Iu Relocation Preparation Failure Timer Relocation Preparation Expiry 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 Iu Relocation Preparation Failure Target System Unsupport Iub Cell not Available DL CE Congestion UL CE Congestion UL CE Congestion DL CE Congestion Iub Control Plane Process Resources Overload Iub Hardware Failure Iub OAM Intervention Failure
Issue 01 (2013-07-15)
2251
ErrType Iub Interface Failure Iub Interface Failure Uu Interface Failure Iur Interface Failure Iur Interface Failure Iub Interface Failure Iur Interface Failure Iur Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure
ErrReason Iub not Enough User Plane Process Resources Failure Iub not Enough User Plane Process Resources Failure Radio Link Permanent Failure Iur AAL2/AL Establishment Failure Iur RL Reconfiguration Commit Timeout Iur Radio Link Reconfiguration Cancel Iur RL Add/Setup Timeout Iur Control Plane Process Resources Overload Radio Link Permanent Failure UE Reestablishment Timer Expired Timer Expired Timer Expired Overlapped Cell Update Overlapped Cell Update Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Timer Expired Overlapped Cell Update Timer Expired Overlapped Cell Update Timer Expired Uu Configuration Unsupport
Issue 01 (2013-07-15)
2252
ErrType Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure Uu Interface Failure
ErrReason Uu Physical Channel Failure Uu Simultaneous Configuration Uu Compress Mode Runtime Tgpsi Error Uu Protocol Error Uu Protocol Error Uu Protocol Error Uu Protocol Error Uu Protocol 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 Physical CH Failure Uu Inter-RAT Change Failure Protocol Error Uu Inter-RAT Change Failure Unspecified UE Reestablishment
Abnormal Cause-Sub-classification
Net
RRC Setup Failure (Service) RRC Setup Failure (Non-service) Intra-RAT Outgoing Handover Failure Inter-RAT Outgoing Handover Failure Intra-RAT Incoming Handover Failure Inter-RAT Incoming Handover Failure
HO Failure
Delay Evaluati on
Delay Problem
Overlong RRC Setup Delay (Service) Overlong RRC Setup Delay (Non-service) Overlong Inter-RAT Outgoing Handover Delay Overlong Intra-RAT Outgoing Handover Delay Overlong Inter-RAT Incoming Handover Delay Overlong Intra-RAT Incoming Handover Delay
PS
Accessib ility Evaluati on Retainab ility Evaluati on Service Evaluati on for Delay
Setup Failure
Key Signaling
Procedure RRC Setup or Release Key Event RRC CONNECTION REESTABLISHMENT REQUEST RRC CONNECTION REJECT
Issue 01 (2013-07-15)
2254
Procedure
Key Event RRC CONNECTION REQUEST RRC CONNECTION SETUP COMPLETE RRC CONNECTION 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
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 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
Issue 01 (2013-07-15)
2255
Procedure
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)
The section describes the exception cause classification in the summary table. The section also lists the signaling procedure and the cause of procedure initiated. l l l l l Exception Cause Classification Exception Cause Field Description (SGSN/MME) Exception Cause Field Description (GGSN/SAE-GW) Signaling Procedure Cause of Procedure Initiated
Domin
Abnormal Sub-type Service Req Failure Service Req Overlong Delay Paging Failure Paging Overlong Delay Iu Release Failure RAB Release Failure PDP Act Failure PDP Act Overlong Delay PDP Sec Act Failure PDP Sec Act Overlong Delay PDP Mod Failure PDP Mod Overlong Delay PDP Deact Failure Rab Assignment Failure Rab Assignment Overlong Delay
Abnormal Paging Abnormal Iu Release Abnormal RAB Release Abnormal PDP Act
PDN GW Dedicated Bearer Act Failure PDN GW Dedicated Bearer Act Overlong Delay PDN GW Initiated Bearer Mod Failure PDN GW Initiated Bearer Mod Overlong Delay PDN GW Initiated Bearer Deact Failure NA Attach Failure Attach Overlong Delay Detach Failure Intra TAU Failure
Abnormal PDN GW Initiated Bearer Mod Abnormal PDN GW Initiated Bearer Deact Non-exception Abnormal Attach Abnormal Detach MME Procedure Abnormal TAU
Intra TAU Overlong Delay Inter TAU Failure Inter TAU Overlong Delay
Abnormal Handover
Issue 01 (2013-07-15)
2257
Domin
Abnormal Type
Abnormal Sub-type Intra E-UTRAN Handover Overlong Delay Inter RAT Handover Failure Inter RAT Handover Overlong Delay
S1 Release Failure Service Req Failure Service Req Overlong Delay Paging Failure Paging Overlong Delay Interoperation Failure Interoperation Overlong Delay Dedicated Bearer Act Failure Dedicated Bearer Act Overlong Delay Bearer Mod Failure Bearer Mod Overlong Delay Bearer Deact Failure Bearer Resourece Mod Failure Bearer Resourece Mod Overlong Delay PDN Connectivity Failure
Abnormal Paging
Abnormal Interoperation Abnormal Dedicated Bearer Act Abnormal Bearer Mod Abnormal Bearer Deact Abnormal Bearer Resourece Mod
Abnormal PDN
Non-exception Abnormal Create PDP GGSN Procedure Abnormal Update PDP Abnormal Delete PDP Traffic Non-exception Abnormal Create Session SAE-GW Procedure Abnormal Delete Session Abnormal Create Bearer Abnormal Modify Bearer
NA NA NA NA NA NA NA NA NA NA
Issue 01 (2013-07-15)
2258
Domin
Abnormal Type Abnormal Update Bearer Abnormal Delete Bearer Abnormal Release Access Bearers Abnormal Modify Bearer Command Abnormal Delete Bearer Command Abnormal Bearer Resource Command Abnormal Create Indirect Data Forwarding Tunnel Abnormal Delete Indirect Data Forwarding Tunnel Traffic
Abnormal Sub-type NA NA NA NA NA NA NA NA NA
Issue 01 (2013-07-15)
2259
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The differentiated service does not allow the access of subscriber. The system does not allow the access of SIM subscribers to the 3G network. The system does not allow the access of 2G subscribers. The license resource item restricts the subscriber access. The system does not allow the access of a certain APN subscriber. The system does not allow the access of IMSI subscribers to a certain location area. GPRS service not allowed caused by MVNO limits or CAMEL subscribers not allowed. The system is being closed. The PLMN does not allow the access of subscribers. The system does not allow the access of a certain CAMEL subscriber. The system does not allow the access of subscribers when being relocated. The system does not allow the access of SIM subscribers to the 4G network. This cause value indicates that system congestion occurs. When the number of attach requests initiated by MSs/UEs subscribed with a specific APN exceeds the predefined threshold, the SGSN/MME rejects subsequent such requests with the cause value of "Congestion" and starts an MM backoff timer. Before this timer expires, the SGSN/MME rejects all such requests with the same cause value. The ZC does not allow the access of subscribers. The ARD does not allow the access of subscribers. Local PLMN does not allow users to access. HLR does not respond.
SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Issue 01 (2013-07-15)
2260
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The authentication set cannot be obtained from the HLR. IMSI unknown MS has no subscription. This location area cannot be accessed by subscribers. The message returned by the HLR is incorrect. The HLR returns an unknown cause. The SCP has no response. SCP initiate detach CAMEL user The DNS server has no response. The response message returned by the DNS server is incorrect. The peer SGSN or MME has no response. The message returned from the peer SGSN indicates that the MS is already separated. The peer SGSN or MME does not have the MS information. The peer SGSN or MME returned incorrect IEs.
An inter-SGSN/MME process fails on the peer SGSN or MME. No PDP context is available. The signaling address of the peer SGSN is invalid. Undefined internal error CB operation failure This cause value indicates that the P-TMSI resource allocation fails.
Issue 01 (2013-07-15)
2261
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The VLR has no response. No available VLR The message returned by the VLR does not carry the MS information. The message returned by the VLR indicates that the location area cannot to be accessed. The message returned by the VLR carries an unknown reason. Receiving error messages Gb interface error An Iu interface error occurs. SDB failure OM delete user The subscriber data are inconsistent, and subscribers were detached. time out of reachable timer The SM does not respond. The SM failed to respond. No response to the S1 message. The target eNodeB does not access the core network. The eNodeB canceled the HO process. The eNodeB failed to respond. The HSS does not respond.
Issue 01 (2013-07-15)
2262
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause The HSS returned an incorrect message. The UE's subscription information is not registered in the HSS. The UE's EPS subscription information is not registered in the HSS. A certain access type is restricted. The system does not allow the access of roaming subscribers. No required HSS is obtained. The HSS returned incorrect security data. The HSS failed to return security data. Incorrect APN Unknown PDP address or type Subscription data mismatch Context not found Last PDN connection not allowed Only IPv4 allowed Only IPv6 allowed Only single address allowed ESM message not received PDN connection not existing DNS resolution failure
Issue 01 (2013-07-15)
2263
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause Message syntax error Invalid message format Unknown resolved IMSI MS detached MS paging without response
Service not supported Incorrect mandatory IE Missing mandatory IE Incorrect optional IE System failure Authentication failure Subscriber authentication failure
Dynamic addresses occupied Semantic error in TFT operation Syntactical error in packet filtering Semantic error in packet filtering Unknown APN returned by GGSN Unknown PDP address or PDP type TFT not activated in PDP context
Issue 01 (2013-07-15)
2264
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Context not found Incorrect message format Invalid length Incorrect command IE Missing command IE Relocation failure PDN address type not supported UE paging without response Service denied Failure to page the UE Request rejected Unable to call UE in idle state Missing conditional IE Timeout of the network side This cause value indicates that multiple PDN connections are not allowed by the APN and accordingly fail. RAB assignment failure
Issue 01 (2013-07-15)
2265
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause RAB assignment failure in the MME IPv6 not supported Wildcard activation rejected Access to VPLMN denied No MVNO license DPP activation restricted by CDRF No MIP license No PPP license No license for conversation PDP activation requests No license for secondary activation Secondary activation not supported by GTPCv0 Activation rejected by differentiated service This cause value indicates that system congestion occurs. When the number of 2G/3G PDP context activation requests initiated by MSs/ UEs subscribed with a specific APN exceeds the predefined threshold, the SGSN rejects subsequent such requests with the cause value of "Congestion" and starts an SM backoff timer. Before this timer expires, the SGSN rejects all such requests with the same cause value. PDP context number limited by the license Access to CDRF VPLMN denied Service barred due to operator-determined barring Access to HPLMN denied
SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Issue 01 (2013-07-15)
2266
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause Resources insufficient Decoding failure Other unknown errors LLC or SNDCP failure Requested service unavailable temporarily Network failure Protocol error This cause value indicates that the UE request conflicts with procedures on the network. Operator determined barring GGSN rejection Unknown rejection cause NSAPI already used Regular deactivation. Reactivation required Context not found in secondary activation Only IPv4 allowed Only IPv6 allowed Only IPv4 or IPv6 allowed Invalid TI value
Issue 01 (2013-07-15)
2267
Procedure Type SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure SGSN Procedure, MME Procedure
Failure Cause Message timeout SGW and PGW rejection PTI already in use Multiple PDN connections not allowed for the same APN UE conflicting with the network side Invalid QCI Invalid PTI Protocol error or unknown error The GGSN fails to resolve the Create PDP context Response message. SGSN deact PDP context with APN restriction The IP address of the GGSN accessed in DHCP or MIP mode is not resolved. RPU-related failures Other APN-related errors The GTPU response times out. The GTPU board returns a failure cause. Sending a message to the GTPU board fails. CB resources are insufficient. SGSN reject PDP context request with APN restriction Undefined error
Issue 01 (2013-07-15)
2268
Procedure Type SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure SGSN Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure MME Procedure
Failure Cause Overlong Attach delays. Overlong Intra SGSN RAU delays. Overlong Inter SGSN RAU delays. Overlong Relocation delays. Overlong System Change delays. Overlong Service Req delays. Overlong Paging delays. Overlong PDP Act delays. Overlong PDP Sec Act delays. Overlong PDP Mod delays. Overlong Attach delays. Overlong Intra TAU delays. Overlong Inter TAU delays. Overlong Intra E-UTRAN Handover delays. Overlong Inter RAT Handover delays. Overlong Service Req delays. Overlong Paging delays. Overlong Interoperation delays. Overlong Dedicated Bearer Act delays. Overlong Bearer Mod delays. Overlong Bearer Resource Mod delays. Overlong PDN Connectivity delays.
The Activate PDP Context Request message is successfully processed. The received GTP header is incorrect.
Issue 01 (2013-07-15)
2269
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause When operations, such as handover and data check, are performed, the Update PDP Context Request message (GTP V0) is not processed. When operations, such as handover and data check, are performed, the Delete PDP Context Request message (GTP V0) is not processed. When operations, such as handover and data check, are performed, the Update PDP Context Request message (GTP V1) is not processed. When operations, such as handover and data check, are performed, the Delete PDP Context Request message (GTP V1) is not processed. The protocol type in the Create PDP Context message (GTP V0) is incorrect. When the Create PDP Context message (GTP V0) is preprocessed, the message is rejected if the License does not support IPv6 subscribers. When the Create PDP Context message (GTP V0) is preprocessed, ApnIndex cannot be found by using ApnName. The Create PDP Context Request message (GTP V0) fails to be processed because the actual APN information cannot be obtained from ApnIndex. When the Create PDP Context Request message (GTP V0) is preprocessed, the APN is locked. When the Create PDP Context Request message (GTP V0) is preprocessed, the SPU board is locked or the CPU is overloaded. The static IP address in the Create PDP Context Request message (GTP V0) is incorrect. The Create PDP Context Request message (GTP V0) fails because the static IP address is not matched; that is, the IP address contained in the list is not consistent with that carried in the message. When the Create PDP Context Request message (GTP V0) is preprocessed, the static IP address fails to be matched because the IP address belongs to the protected IP address segment. When the Create PDP Context Request message (GTP V0) is preprocessed, the operations of allocating the context space and establish the IMSI index fail The protocol type in the Create PDP Context message (GTP V1) is incorrect. When the Create PDP Context message (GTP V1) is preprocessed, ApnIndex cannot be found by using ApnName. The Create PDP Context message (GTP V1) is directly rejected if the License does not support IPv6 subscribers.
Issue 01 (2013-07-15)
2270
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Issue 01 (2013-07-15)
Failure Cause The Create PDP Context message (GTP V1) fails to be processed if the IMSI and MSISDN of V1 subscribers are not matched. When the Create PDP Context message (GTP V1) is preprocessed, the judgment on static IP addresses is invalid. The IPv4 static IP address in the Create PDP Context message (GTP V1) does not belong to the address segment configured by the APN. The IPv4 static IP address in the Create PDP Context message (GTP V1) is belongs to the protected address segment. The Create PDP Context message (GTP V1) fails to be processed because the APN is locked. Messages are sent to other boards. The possible cause is that the SPU is locked; the CPU is overloaded. The second Create PDP Context message (GTP V1) fails to be processed because the context cannot be found. The second Create PDP Context message (GTP V1) fails to be processed because PPP, L2tp, IPv6, and MIP subscribers do not support the second activation. The second Create PDP Context message (GTP V1) fails to be processed because the APN is locked. The same NSAPI is carried in the second Create PDP Context message (GTP V1). The NSAPI activated in the second Create PDP Context message (GTP V1) is the same as that activated in a common message. The second Create PDP Context message (GTP V1) fails to be processed because the second activation is not allowed when the handover or data check is performing. The second Create PDP Context message (GTP V1) fails to be processed because GGSN cannot allocate a context. The second Create PDP Context message (GTP V1) fails to be processed because the NSAPI attribute is incorrect. The Create PDP Context Request message (GTP V0) fails to be processed because the retrieved IE cannot be saved in the context. The Create PDP Context Request message (GTP V0) fails to be processed because the QoS negotiation fails. The Create PDP Context Request message (GTP V0) fails to be processed because the data stream labels cannot be allocated. The Create PDP Context Request message (GTP V0) fails to be processed because the signaling path cannot be established.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2271
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause The Create PDP Context Request message (GTP V0) fails to be processed because the data path cannot be established. The Create PDP Context Request message (GTP V0) fails to be processed because the subscriber is not authorized. The Create PDP Context Request message (GTP V0) fails to be processed because the global and APN configurations do not allow the access of roaming subscribers. The Create PDP Context Request message (GTP V0) fails to be processed because the global and APN configurations do not allow the access of visiting subscribers. The Create PDP Context Request message (GTP V0) fails to be processed because the timer cannot be created. The Create PDP Context Request message (GTP V1) fails to be processed because the TFT is invalid. The Create PDP Context Request message (GTP V1) fails to be processed because contents in the message cannot be saved in the context. The Create PDP Context Request message (GTP V1) fails to be processed because the QoS negotiation fails. The Create PDP Context Request message (GTP V1) fails to be processed because the signaling path cannot be established. The Create PDP Context Request message (GTP V1) fails to be processed because the data path cannot be established. The Create PDP Context Request message (GTP V1) fails to be processed because the subscriber is not authorized. The Create PDP Context Request message (GTP V1) fails to be processed because the global and APN configurations do not allow the access of roaming subscribers. The Create PDP Context Request message (GTP V1) fails to be processed because the global and APN configurations do not allow the access of visiting subscribers. The Create PDP Context Request message (GTP V1) fails to be processed because the timer cannot be created. The second Create PDP Context Request message (GTP V1) fails to be processed because the TFT is invalid. The second Create PDP Context Request message (GTP V1) fails to be processed because the message does not carry a TFT and a context without a TFT exists.
Issue 01 (2013-07-15)
2272
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause The second Create PDP Context Request message (GTP V1) fails to be processed because contents in the message cannot be saved in the context. The second Create PDP Context message (GTP V1) fails to be processed because the context cannot be found. The second Create PDP Context message (GTP V1) fails to be processed because the context RAI carried in this message is not consistent with that of the related context. The second Create PDP Context Request message (GTP V1) fails to be processed because the QoS negotiation fails. The second Create PDP Context Request message (GTP V1) fails to be processed because the signaling path cannot be established. The second Create PDP Context Request message (GTP V1) fails to be processed because the data path cannot be established. The second Create PDP Context Request message (GTP V1) fails to be processed because the timer cannot be created. It is the cause value of failed authentication sent from the Radius module. In the DHCP ACK message sent by the DHCP server, the returncode is failure. The filter number reaches the maximum number when the Create PDP Context Request message is successfully processed. Creating the NP list fails when the Create PDP Context Request message is successfully processed. When the Create PDP Context Request message is successfully processed, the corresponding response message fails to be sent. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN PDP is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN universal PDP is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the global PDP is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the global universal PDP is reached.
Issue 01 (2013-07-15)
2273
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Issue 01 (2013-07-15)
Failure Cause When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN bandwidth is reached. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN universal bandwidth is reached. The Update PDP Context Request message is successfully processed. The protocol type in the Update PDP Context Request message (GTP V0) is incorrect. The context carried in the Update PDP Context Request message (GTP V0) cannot be found. The Update PDP Context Request message (GTP V0) fails to be processed because the CPU is overloaded. Mandatory IEs are absent in the Update PDP Context Request message. The IMSI cannot be obtained from the Update PDP Context Request message (GTP V1) and the context cannot be located based on the TEID (C) + NSAPI. The IMSI is obtained from the Update PDP Context Request message (GTP V1), but the context cannot be located based on the TEID (C) + NSAPI. The IMSI in the Update PDP Context Request message (GTP V1) cannot be found because of the version change. The context in the Update PDP Context Request message (GTP V1) cannot be found after the IMSI is obtained because of the version change. The Update PDP Context Request message (GTP V1) fails to be processed because the CPU is overloaded. The Update PDP Context Request message (GTP V1) fails to be processed because the TFT carried in the message is invalid. The Update PDP Context Response message (GTP V1) is received, but the message format is incorrect. The V1 Update PDP Context Response message is received, but the corresponding request message cannot be found. After the Update PDP Context Response message (GTP V1) is received, the context fails to be found based on the index. The number of filters exceeds the limit after the Update PDP Context Request message is processed. IEs cannot be saved in the context when the Update PDP Context Request message (GTP V1) is processed.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2274
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure
Failure Cause When the Update PDP Context Request message is processed and the GTP version is updated from V1 to V0, the data stream labels fail to be allocated. IEs cannot be saved in the context when the Update PDP Context Request message (GTP V0) is processed. Negotiating the QoS fails when the Update PDP Context Request message is processed. Updating the signaling path fails when the Update PDP Context Request message is processed. Updating the data path fails when the Update PDP Context Request message is processed. Updating a local subscriber to a roaming subscriber fails when the Update PDP Context Request message is processed. Updating the charging information fails when the Update PDP Context Request message is processed. The NP fails to update the context when the Update PDP Context Request message is processed. After the Update PDP Context Response message is received, the SGSN rejects the update originated by the GGSN. After the Update PDP Context Response message is received, the QoS version carried in the message is not supported. After the Update PDP Context Response message is received, the GTPU table fails to be sent to the NP. When the Create PDP Context Request message is processed and the differentiated service switch is enabled, the subscriber is rejected because the access rejection threshold of the APN bandwidth is reached. The Deactivate PDP Context Request message is successful processed. The protocol type in the Delete PDP Context Request message (GTP V0) is incorrect. The context is not found in the Delete PDP Context Request message (GTP V0). After an V0 subscriber receives the Delete PDP Context Request message (GTP V1), a failure response is returned. An IE is absent in the Delete PDP Context Request message (GTP V1) or the message is invalid. The context to be deleted in the Delete PDP Context Request message (GTP V1) does not exist whereas the related context exists.
Issue 01 (2013-07-15)
2275
Procedure Type GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure GGSN Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause When the Delete PDP Context Request message (GTP V1) does not carry TEARDOWN, no corresponding context can be found in the SDB context. The Delete PDP Context Request message (GTP V1) requests to delete the last context, but TEARDOWN is not carried in this message. The value of TEARDOWN carried in the Delete PDP Context Request message (GTP V1) is 0 and no corresponding context can be found in the SDB context. The Delete PDP Context Request message (GTP V1) requests to delete the last context, but the value of TEARDOWN in this message is 0. When the Delete PDP Context Response message (GTP V0) is received, the protocol type carried in the message is incorrect. Thus, an incorrect response message is received and the context cannot be found. When the Delete PDP Context Response message (GTP V0) is received, the protocol type carried in the message is incorrect. Thus, an incorrect response message is received. The Delete PDP Context Response message (GTP V0) fails to be processed because the context cannot be located. When the Delete PDP Context Response message (GTP V0) is received, the context fails to be converted to an pointer. The received Delete PDP Context Response message (GTP V0) is incorrect. When the Delete PDP Context Response message (GTP V0) is received, the corresponding request message cannot be found. The Delete PDP Context Response message (GTP V0) fails to be processed because the context cannot be found by using the index. The Create Session Request message is successfully processed. The Create Session Request fails to be processed because the UGW9811 is locked and does not allow the access from new subscribers. The Create Session Request message fails to be processed because the board is in smooth state after the active/standby switchover and does not allow the access from new subscribers. The Create Session Request message fails to be processed because obtaining product types fails based on a request IE. The Create Session Request message fails to be processed because obtaining APN IE from IEs contained in the message fails. The Create Session Request message fails to be processed because the PGW receives the message in a non-Attach scenario.
Issue 01 (2013-07-15)
2276
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Create Session Request message fails to be processed because license resources are insufficient for the type of products. The Create Session Request message fails to be processed because the system traffic reaches license limitation and the access from new subscribers is not allowed. The Create Session Request message fails to be processed because the IP address of the peer NE is on the blacklist or is not on the whitelist. The Create Session Request message fails to be processed because obtaining the usage scenario of the message fails. The Create Session Request message fails to be processed because checking the validity of the message fails. The Create Session Request message fails to be processed because applying for a bearer context fails. The Create Session Request message fails to be processed because the board is locked. The Create Session Request fails to be processed because filter resources are insufficient. The Create Session Request message fails to be processed because creating a signaling path fails. The Create Session Request message fails to be processed because policy control implemented by the PCRF, AAA server, or the UGW9811 configuration fails. The Create Session Request message fails to be processed because the QCI type is incorrect during the QoS check performed during the interaction between UGW9811 and PCRF. The Create Session Request message fails to be processed because the SGW fails to forward the message to the PGW. The Create Session Request message fails to be processed because the peer NE fails to respond before the timeout. The Create Session Request message fails to be processed because the peer NE returns a rejection message. The Create Session Request message fails to be processed because the system fails to start charging. The Create Session Request message fails to be processed because an internal system error occurs during the processing and causes subscribers to fail to access the UGW9811. The Create Session Request message fails to be processed because the system fails to enable the content resolution function.
Issue 01 (2013-07-15)
2277
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Create Session Request fails to be processed because license resources are insufficient and the access from subscribers is not allowed. The Create Session Request message fails to be processed because the system fails to start data forwarding. The Create Session Request message fails to be processed because initiating AAA authentication fails. The Create Session Request message fails to be processed because mapping the APN to in the request to the actual APN fails. The Create Session Request message fails to be processed because the access from roaming subscribers is not allowed after authentication. The Create Session Request message fails to be processed because the IP address obtained from the AAA server is incorrect. The Create Session Request message fails to be processed because userprofile fails to be obtained based on the user-profile name issued by the AAA server. The Create Session Request message fails to be processed because creating L2TP tunnel fails. The Create Session Request message fails to be processed because routing resources are insufficient which results in the failure of the access from subscribers. The Create Session Request message fails to be processed because the static IP address or IP address allocated by the AAA server is incorrect. The Create Session Request message fails to be processed because obtaining an IP address fails. The Create Session Request message fails to be processed because QoS control fails. The Create Session Request message fails to be processed because the message decode fails. The Create Session Request message fails to be processed because an internal system error occurs during the processing. The Modify Bearer Request message is successfully processed. 1. The Modify Bearer Request message fails to be processed because the board is in smooth state after the switchover and does not allow the access from subscribers. 2. No default bearer can be found. The Modify Bearer Request message fails to be processed because the address of the peer NE is on the blacklist or is not on the whitelist.
Issue 01 (2013-07-15)
2278
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Modify Bearer Request message fails to be processed because non-PGW NEs receive a message that does not contain bearer information. The Modify Bearer Request message fails to be processed because the bearer contained in the message belongs to multiple PDN Connections. The Modify Bearer Request message fails to be processed because obtaining the product type fails. The Modify Bearer Request message fails to be processed because checking the validity of IEs contained in the message fails. The Modify Bearer Request message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message. The Modify Bearer Request message fails to be processed because subscribers are on the multi-service APN and they are not allowed to switch to Gptv2 subscribers. The Modify Bearer Request message fails to be processed because obtaining an APN fails. The Modify Bearer Request message fails to be processed because the an internal system error occurs in the UGW9811 during the processing. The Modify Bearer Request message fails to be processed because the interaction between the UGW9811 and the PCRF fails. The Modify Bearer Request message fails to be processed because the system fails to enable the content resolution function. The Modify Bearer Request message fails to be processed because the system fails to start charging. The Modify Bearer Request message fails to be processed because an internal system error occurs during the processing. The Modify Bearer Request message fails to be processed because filter resources are insufficient. The Modify Bearer Request fails to be processed because the SGW fails to forward the request message to the PGW. The Modify Bearer Request message fails to be processed because the peer NE fails to respond before the timeout. The Modify Bearer Request message fails to be processed because the peer NE returns a rejection message code. The Modify Bearer Request message fails to be processed because the system fails to start data forwarding. The Modify Bearer Request message fails to be processed because the message decode fails.
Issue 01 (2013-07-15)
2279
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Issue 01 (2013-07-15)
Failure Cause
The Delete Session Request message is successfully processed. The Delete Session Request message fails to be processed because subscribers' bearer information cannot be found. The Delete Session Request message fails to be processed because NEs in the request message are invalid. The Delete Session Request message fails to be processed because no default bearers can be found. The Delete Session Request message fails to be processed because in the nonGUL handover scenario the GGSN receives the message. In the scenario of switching services from the SPGW to the PGW, the Delete Session Request fails to be processed because a response message fails to be sent. The Delete Session Request message fails to be processed because the system processes the message improperly. The Delete Session Request message fails to be processed because the SGW receives a failure response from the PGW. The Create Bearer Request message is successfully processed. The Create Bearer Request message fails to be processed because IEs in the message are incorrect. The Create Bearer Request message fails to be processed because the information about subscriber default bearers fails to be obtained. The Create Bearer Request message fails to be processed because the number of default bearers reaches the specifications and creating dedicated bearers fails. The Create Bearer Request message fails to be processed because the NE type is incorrect. The Create Bearer Request message fails to be processed because subscriber dedicated bearers fail to be created. The Create Bearer Request message fails to be processed because the PGWFQ-CSID fails to be processed. The Create Bearer Request message fails to be processed because the TFT fails to be processed. The Create Bearer Request message fails to be processed because applying for a memory to store PCO fails. The Create Bearer Request message fails to be processed because the PCO IE fails to be resolved.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2280
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Create Bearer Request message fails to be processed because the IMS signaling bearer fails to be queried. The Create Bearer Request message fails to be processed because roaming subscribers cannot use the extended QCI. The Create Bearer Request message fails to be processed because QoS control fails. The Create Bearer Request message fails to be processed because session control resources fail to be applied. The Create Bearer Request fails to be processed because filter resources are insufficient. The Create Bearer Request message fails to be processed because the signaling or data path fails to be created. The Create Bearer Request message fails to be processed because the system fails to start data forwarding. The message Create Bearer Request fails to be processed because the SGW fails to forward a request message to the MME. The Create Bearer Request message fails to be processed because peripheral NEs fail to respond before the timeout. The Create Bearer Request message fails to be processed because the peer NE returns a rejection message code. The Create Bearer Request message fails to be processed because the system fails to start charging. The Create Bearer Request message fails to be processed because an internal system error occurs during the processing. The Create Bearer Request message fails to be processed because the system fails to enable the content resolution function. The Create Bearer Request fails to be processed because license resources are insufficient and the access from subscribers is not allowed. The Create Bearer Request message fails to be processed because the message decode fails. The Create Bearer Request message fails to be processed because the system processes the message improperly. The UGW9811 actively initiates Create Bearer procedure, and the peer NE returns a success message code. The UGW9811 actively initiates Create Bearer procedure, but the peer NE returns a rejection message code.
Issue 01 (2013-07-15)
2281
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause
The Update Bearer Request message is successfully processed. The Update Bearer Request message fails to be processed because the message contains incorrect IEs. 1. The Update Bearer Request message fails to be processed because the board is in smooth state after the switchover and does not allow the bearer update. 2. The bearer cannot be found based on the TEID in the message. The Update Bearer Request message fails to be processed because the bearer information fails to be obtained based on the EBI and LBI IEs in the message. The Update Bearer Request message fails to be processed because the product is not the SGW. The Update Bearer Request message fails to be processed because applying for a bearer context fails. The Update Bearer Request message fails to be processed because the PTI in the message is inconsistent with that in the default bearer. The Update Bearer Request message fails to be processed because the message fails to be forwarded to the MME. The Update Bearer Request message fails to be processed because the peer NE fails to respond before the timeout. The Update Bearer Request message fails to be processed because the peer NE returns a rejection message code. The Update Bearer Request message fails to be processed because the system fails to start charging. The Update Bearer Request message fails to be processed because an internal system error occurs during the processing. The Update Bearer Request message fails to be processed because filter resources are insufficient. The Update Bearer Request message fails to be processed because an internal system error occurs during the processing. The Update Bearer Request message fails to be processed because the system fails to start data forwarding. The Update Bearer Request message fails to be processed because the message decode fails. The UGW9811 initiates the Update Bearer procedure, and the peer NE returns a success message code. The UGW9811 initiates the Update Bearer procedure, but the peer NE returns a rejection message code.
Issue 01 (2013-07-15)
2282
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause
The Delete Bearer Request message is successfully processed. The Delete Bearer Request message fails to be processed because IEs in the message are invalid. The Delete Bearer Request message fails to be processed because information about subscriber bearers fails to be found. The Delete Bearer Request message fails to be processed because subscriber bearers to be deleted fail to be found. The Delete Bearer Request message fails to be processed because no default bearers can be found. The Delete Bearer Request message fails to be processed because the NE type in the message is incorrect. The Delete Bearer Request message fails to be processed because an internal system error occurs and causes a failure in deleting subscriber bearers. The Delete Bearer Request message fails to be processed because the message decode fails. In a UGW9811-initiated Delete Bearer procedure, the peer NE sends a Delete Bearer Response message to the UGW9811. In a UGW9811-initiated Delete Bearer procedure, the peer NE sends a Delete Bearer Response message carrying a failure cause value to the UGW9811. The Release Access Bearers Request message is successfully processed. The Release Access Bearers Request message fails to be processed because no bearer information of the subscriber is found. The Release Access Bearers Request message fails to be processed. The Modify Bearer Command message is successfully processed. The Modify Bearer Command message fails to be processed because no bearer information of the subscriber is found. The Modify Bearer Command message fails to be processed because an IE in the message is invalid. The Modify Bearer Command message fails to be processed because no information about the default bearer of the subscriber is found. The Modify Bearer Command message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message.
Issue 01 (2013-07-15)
2283
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Issue 01 (2013-07-15)
Failure Cause The Modify Bearer Command message fails to be processed because the Sequence Number IE ID is incorrect. The Modify Bearer Command message fails to be processed because the extended QCI cannot be used when the subscriber is in roaming state. The Modify Bearer Command message fails to be processed because peripheral NEs fail in processing the message. The Modify Bearer Command message fails to be processed because no response is received from peripheral NEs before timeout or peripheral NEs fails in processing the message, which causes the failure in updating bearers. The Modify Bearer Command message fails to be processed because the message decode fails. The Delete Bearer Command message is successfully processed. The Delete Bearer Command message fails to be processed because no bearer information of the subscriber is found. The Delete Bearer Command message fails to be processed because the Sequence Number IE ID is incorrect. The Delete Bearer Command message fails to be processed because an IE in the message is invalid. The Delete Bearer Command message fails to be processed because the EBI in the message is incorrect. The Delete Bearer Command message fails to be processed because the subscriber bearer is not established or has been updated on the NE. The Delete Bearer Command message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message. The Delete Bearer Command message fails to be processed because peripheral NEs fail in processing the message. The Delete Bearer Command message fails to be processed because no response is received from peripheral NEs before timeout or peripheral NEs fails in processing the message, which causes the failure in updating bearers. The Bearer Resource Command message is successfully processed. The Bearer Resource Command message fails to be processed because no bearer information of the subscriber is found. The Bearer Resource Command message fails to be processed because an IE in the message is invalid. The Bearer Resource Command message fails to be processed because the bearer of the subscriber is being deleted.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2284
Procedure Type SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure SAE-GW Procedure
Failure Cause The Bearer Resource Command message fails to be processed because the IP address of the PGW is set to a group IP address of the NE in the message. The Bearer Resource Command message fails to be processed because the Fteid IE in the message is incorrect. The Bearer Resource Command message fails to be processed because the memory application fails after the PCO setting is saved. The Bearer Resource Command message fails to be processed because the parsing of the PCO IE fails. The Bearer Resource Command message fails to be processed because the total CBR of the subscriber bearer is greater than the maximum GBR configured for the APN. The Bearer Resource Command message fails to be processed because the previous Bearer Command message has not been processed. The Bearer Resource Command message fails to be processed because the Sequence Number IE ID is incorrect. The Bearer Resource Command message fails to be processed because no IMS signaling bearer is found. The Bearer Resource Command message fails to be processed because peripheral NEs fail in processing the message. The Bearer Resource Command message fails to be processed because no response is received from peripheral NEs before timeout or peripheral NEs fails in processing the message, which causes the failure in performing bearer operations. The Bearer Resource Command message fails to be processed because the message decode fails. The Create Indirect Data Forwarding Tunnel Request message is successfully processed. The Create Indirect Data Forwarding Tunnel Request message is successfully processed. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because an IE in the message is invalid. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because the NE type is neither SGW nor SPGW. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because no bearer is found for the operation. The Create Indirect Data Forwarding Tunnel Request message fails to be processed because the message decode fails.
Issue 01 (2013-07-15)
2285
Failure Cause The Delete Indirect Data Forwarding Tunnel Request message is successfully processed.
Signaling Procedure
Procedure Type SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN Procedure Name GPRS Attach Combined Attach MS Init GPRS Detach MS Init Combined Detach CN Init GPRS Detach CN Init Combined Deatch Implicit GPRS Detach Implicit Combined Detach RAN Init Iu Release CN Init Iu Release RAU(others) Intra RAU Intra Combined RAU Inter RAU Inter Combined RAU Periodic RAU Periodic Combined RAU Intra SRNS Relocation Inter SRNS Relocation 3G to 2G System Change 2G to 3G System Change Service Req Paging MS Init PDP Act
Issue 01 (2013-07-15)
2286
Procedure Type SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN SGSN MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME
Procedure Name MS Init PDP Sec Act CN Init PDP Act MS Init PDP Deact CN Init PDP Deact MS Init PDP Mod CN Init PDP Mod RAN Init RAB Release CN Init RAB Release CN Init PDP Sec Act RAB Assignment PDN GW Dedicated Bearer Act PDN GW Initiated Bearer Mod PDN GW Initiated Bearer Deact Attach Intra USN Intra E-UTRAN TAU Inter USN Intra E-UTRAN TAU eNodeB S1 Release CN Init S1 Release Ms Init Detach CN Init Detach X2 HandOver Intra MME S1 HandOver Inter MME S1 HandOver Paging Service Req Intra USN GERAN to E-UTRAN Inter RAT TAU Intra USN UTRAN to E-UTRAN Inter RAT TAU Intra USN UTRAN Iu mode to E-UTRAN Inter RAT handover Inter USN UTRAN Iu mode to E-UTRAN Inter RAT handover Inter USN GERAN/UTRAN to E-UTRAN TAU
Issue 01 (2013-07-15)
2287
Procedure Type MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME MME GGSN GGSN GGSN GGSN SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW SAE-GW
Procedure Name MME to 3G SGSN combined hard handover and SRNS relocation procedure Intra USN E-UTRAN to GERAN Inter RAT RAU Intra USN E-UTRAN to UTRAN Inter RAT RAU Intra USN E-UTRAN to UTRAN Iu mode Inter RAT handover Inter USN E-UTRAN to UTRAN Iu mode Inter RAT handover Inter USN E-UTRAN to GERAN/UTRAN Inter RAT RAU 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure Dedicated Bearer Act PDN GW Initiated Bearer Mod with Bearer QoS Update HSS Initiated Subscribed QoS Mod PDN GW Initiated Bearer Mod Without Bearer QoS Update PDN GW Initiated Bearer Deact MME Initiated Dedicated Bearer Deact Bearer Resource Mod PDN Connectivity PDN Disconnection Create PDP Update PDP Delete PDP Traffic Create Session Modify Bearer Delete Session Create Bearer Update Bearer Delete Bearer Release Access Bearers Modify Bearer Command Delete Bearer Command
Issue 01 (2013-07-15)
2288
Procedure Name Bearer Resource Command Create Indirect Data Forwarding Tunnel Delete Indirect Data Forwarding Tunnel Traffic
Issue 01 (2013-07-15)
2289
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
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 CHR_PROC_INIT_CAUSE_SGSN_DEACT_V1_GGSN_ERR_IN D CHR_PROC_INIT_CAUSE_SGSN_DEACT_V0_SGSN_ERR_IN D CHR_PROC_INIT_CAUSE_SGSN_DEACT_V1_SGSN_ERR_IN D CHR_PROC_INIT_CAUSE_SDB
Issue 01 (2013-07-15)
2290
Cause
Procedure initiated by the GGSN Procedure initiated by the DNS Procedure initiated by the MSC Procedure initiated by the EIR Procedure initiated by the SCP Procedure initiated by the BSS Procedure initiated by the RNC
Issue 01 (2013-07-15)
2291
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 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
Issue 01 (2013-07-15)
2292
5.6.10 FAQ: Why Are CHRs Related to RRC Connection Setup Failures Not Displayed in LTE Complaint Analysis Support Results?
Why are call history records (CHRs) related to RRC connection setup failures not displayed in the results of LTE complaint analysis support, LTE in-depth VIP analysis, or LTE in-depth cell performance analysis though they exist?
Symptom
l When users view the results of LTE in-depth VIP analysis or LTE in-depth cell performance analysis, abnormal counters related to RRC connection setup failures are not displayed and CHRs related to these counters cannot be obtained. When users view the results of LTE complaint analysis support, LTE in-depth VIP analysis, or LTE in-depth cell performance analysis, CHRs related RRC connection setup failures are not displayed though they exist.
Cause
A prerequisite for VIP analysis and complaint analysis support is that the network (mainly the core network) side obtains subscriber identity information, such as IMSI and IMEI, through a subscriber authentication procedure. However, this procedure is triggered only after the RRC connection setup succeeds. Therefore, the network side cannot obtain subscriber identity information if the RRC connection setup fails, and consequently the Nastar cannot obtain related CHRs to execute complaint analysis support and VIP analysis.
Solution
None
Issue 01 (2013-07-15)
2293
6 System Management
6
About This Chapter
Introduction
Related Document Monitoring the Nastar System Security Management Description
System Management
The system management includes the following parts, such as security management, log management, task management, and monitoring the Nastar system. You can manage the Nastar and monitor the running status of the Nastar through the functions.
You can monitor the status (including the status of the service, hard disk and database) and the component information of the Nastar server. You can monitor the service, hard disk and database status of the eSAU and SAU. Security management provides the functions of managing user rights and system security policies. These functions can prevent invalid users from performing malicious operations on the Nastar, thus ensuring data security of the Nastar. The log records the operations and important system events on the Nastar. You can use log management to query and collect statistics on logs. Through the device certificate information, you can apply for digital certificates and manage device certificates, CA certificates, cross certificates, and revoked certificates. The Nastar provides a function for you to centrally manage scheduled tasks. By using this function, you can view information about the status and process of each task, and create, modify, delete, suspend, resume, or cancel a scheduled task.
Issue 01 (2013-07-15)
2294
6 System Management
Prerequisites
Before login, ensure that the Nastar client and server are connected normally, and the server works properly.
Context
l l The default port number of the server is 31037. Do not change it in normal conditions. Otherwise, you cannot log in to the Nastar client. The Nastar server provides the default user account admin. The admin user has all operation rights, and the password is empty 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. The screen resolution of the PC is recommended for the 1440 x 900 pixels or more, otherwise the interface display of the functions may be abnormal.
l l l
l l
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:
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2295
6 System Management
l If the server list does not exist: 1. 2. 3. 4. 5. Click on the right of Server drop-down list.
In the Server List dialog box, click Add. In the Add Server Information dialog box, set the Name, Server Name (or IP Address), Port and Mode. 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. 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.
NOTE
By default, the name of the last login user is displayed in the Login dialog box. If you do not want to display the name of the last login user, you can set isShowLoginUserName to false in the loginuiconfig.xml file in installation directory of the Nastar client\NastarClient\client\plugins\loginui\style\conf\loginui \loginuiconfig.xml, and then restart the client for the settings to take effect.
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
Related References
Parameters for the Server List Parameters for Logging In to the Nastar Client Parameters for the Server List Parameters for Logging In to the Nastar Client
Context
This operation does not end the client program.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2296
6 System Management
Procedure
Step 1 Choose File > Log Out from the main menu. Step 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.
----End
Context
l l To ensure security, when you do not need to perform any operations on the client, exit the Nastar client or log out the user account. This operation will end the client program. If you want to perform some operations on the client, restart the Nastar client.
Procedure
Step 1 Choose File > Exit from the main menu. Step 2 In the Confirm dialog box, click OK. ----End
Related Tasks
6.1.5 Locking the Client
Context
The new password must comply with the password policy. For details on how to set the password policy, see Setting the Password Policy.
Procedure
Step 1 Choose File > Change Password from the main menu. Step 2 In the Change Password dialog box, set the new password for the current user, then click OK. Step 3 In the displayed Confirm dialog box, click Yes. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2297
6 System Management
Related Tasks
Resetting the Password of a Nastar User
Menu Bar
The menu bar provides the entries to all the functions of the Nastar client. It consists of the following menus: File, Maintenance, Security, Tools, System. Window, and Help.
Toolbar
The toolbar provides the shortcut icons for major operation tasks. The shortcut icons are as follows: l l
Issue 01 (2013-07-15)
6 System Management
l l l l
: To lock the Nastar client. : To display the work area in full-screen mode. :To open the security management window. : To open the GIS window.
Navigation Tree
The navigation tree displays the product function in the tree structure. Provides the theme search function and type-based grouping function.
Output Pane
The output pane displays the echo message of the operation performed when the Nastar is running, such as the initialization prompt when you log in to the server.
Window Bar
The window bar displays the windows that are in use.
Status Bar
The status bar displays the information such as the system status, the login users, and the IP address of the connected server. The information displayed from left to right is as follows: l l l l Server: Displays the IP address used for logging in to the server. Login user: Displays the name of the login user. Connection duration: Displays the duration of the connection between the client and the server. System pop-up pane: Displays a prompt in real time when an operation on the server affects client operations. For example, after the user opens the Security Management window, if a user, user group, or operation set is added or deleted on the Nastar, the system pop-up pane displays a prompt.
NOTE
To enable or disable the function of displaying a prompt, right-click the icon of the system pop-up pane and choose Enable or Disable.
l l
Login mode: Displays the login mode. It can be single-user mode and multi-user mode. Connection status: Displays the status of the connection between the client and the server. When the client is disconnected from the server, the icon on the status bar is changed from
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2299
Issue 01 (2013-07-15)
6 System Management
to , and then to . When the status of the alarm indicator changes to disconnection sound is available. l Logo: Displays the logo of Huawei Technologies Co., Ltd..
,a
Menu Functions
This topic describes the menus of the Nastar and their functions. You can refer to this topic to determine the entry of a certain operation.
File Menu
This topic describes the submenus of the File main menu. Table 6-1 File menu Menu Item Preferences Function To set display effects for the client. Display effects include the font size, output window action, time and date, automatic client lock, alert for disconnection, number format, time mode, upgrade, system login mode. To customize the toolbar on the client, for example, setting which buttons are to be shown. To preview the topology view before printing it. To print the concerned contents by setting print parameters. To customize the page layout. This function applies to the users who browse the topology view offline. To lock the client manually. To change the password of the current Nastar user. To log out of the Nastar client but not close it. To log out of the Nastar client and close it.
Customize Toolbar Print Preview Print Page Setup Lock Terminal Change Password Log Out Exit
Maintenance Menu
This topic describes the submenus of the Maintenance main menu. Table 6-2 Maintenance Menu Menu Item Task Management
Issue 01 (2013-07-15)
2300
6 System Management
Menu Item E-Mail Setting Auto-Distribution User Management OSS Information Management Data Subscription Management Data Maintenance Management
Function To set the Email information for sending. To automatically send VIP analysis results to multiple mailboxes by email. To manage Nastar information of the OSS, NEs and eSAU. To provide the subscription information function for one or multiple NEs. To query NE data and set data storage days.
Security Menu
This topic describes the submenus of the Security main menu. Table 6-3 Security Menu Menu Item Security Management Function To access the Security Management window for managing users, user groups, object sets, and operation sets. To monitor current user operations and sessions or force the user to log out. To add IP address or segments to the ACL(Access Control List), change IP address or segments in the ACL, and delete IP address or segments from the ACL. To set the global security policy of the Nastar, including the password policy and the account policy. Query Operation Logs Query System Logs To set the template or filtering conditions for browsing operation logs. This helps understand the information about user operations. To set the template or filtering conditions for browsing system logs. This helps understand the information about the important events that occurred during system running. To set the template or filtering conditions for browsing operation logs. This helps understand the information about security operations such as logging in, logging out, and unlocking.
Issue 01 (2013-07-15)
2301
6 System Management
Menu Item Operation Log Statistics System Log Statistics Security Log Statistics Certificate Authentication Management Certificate Management SSL Connection Management
Function To set the template, or statistical items and filtering conditions for collecting statistics on or displaying operation logs. To set the template, or statistical items and filtering conditions for collecting statistics on or displaying system logs. To set the template, or statistical items and filtering conditions for collecting statistics on or displaying security logs. To manage Nastar certificate information. To ensure the security of Nastar data transfer by setting SSL connections. To access the Anonymity key Management window, through establishing the Non-Anonymization Data Analysis Switch, the user may open or closes use the non-anonymous personal data to carry out the Nastar analysis task.
Tools Menu
This topic describes the submenus of the Tools main menu. Table 6-4 Tools menu Menu Item Broadcast Message Convert Map Google Earth Function To send broadcast messages. To convert the map format. To provide the satellite view.
System Menu
This topic describes the submenus of the System main menu. Table 6-5 System menu Menu Item System Monitor Browser Function To browse the system information such as services, processes, hard disks, and resources.
Issue 01 (2013-07-15)
2302
6 System Management
Function To set the parameters for monitoring system resources, hard disks, databases, and services. To browse the system information such as services, processes, hard disks, and resources of the eSAU, LTE SAU, and SAU. To set the parameters for monitoring hard disks, databases, and services. To set the log forwarding server for forwarding logs. To deliver the adapter package. To download the Nastar log of the server and the client to the local PC.
Window Menu
This topic describes the submenus of the Window main menu. Table 6-6 Window menu Menu Item Full Screen Close Function To display the window where the focus exists in fullscreen mode. To close the current window.
NOTE You cannot close the Geographic Observation window.
Close All
Minimize
To minimize the current window. After a window is minimized, the related icon is displayed at the lower left corner of the client. To minimize all the open windows. After the windows are minimized, the related icon is displayed at the lower left corner of the client. To open or close the window tabbed bar. To open or close the message output pane in the lower part of the window. To display the open tab pages in different layers on the screen.
Minimize All
Issue 01 (2013-07-15)
2303
6 System Management
Function To display all active tabs on the interface. Each tab occupies part of the interface space. To horizontally display all the open tab pages on the screen, with each occupying a part of the window. To vertically display all the open tab pages on the screen, with each occupying a part of the window. To set the view to the one displayed during the first login.
Help Menu
This topic describes the submenus of the Help main menu. Table 6-7 Help menu Menu Item Help Topics Workbench License Management License Information Query Invalid License Code Revoke License Function To view the Help. To open the workbench. To display the information about a license and update the license. To view the invalidation code of a license on the Nastar client. When applying for a license, you need to provide the invalidation code of the old license. To revoke an unnecessary license. After revocation, the revocation code of the license is generated. You can use the revocation code to apply for a license. To manually check whether the Nastar client needs to be upgraded. To view the information on the version, components, and license of the Nastar.
Issue 01 (2013-07-15)
2304
6 System Management
Button
Displays a dialog box. Makes the current settings take effect. Displays the latest result(s). Saves selected data to a specified file. Makes the current settings take effect and closes the dialog box. Cancels the current settings and closes the dialog box. Closes the dialog box. Selects the files that need to be opened.
Issue 01 (2013-07-15)
2305
6 System Management
Example
Drop-down list
Dialog box
Keyboard Shortcuts
The Nastar client provides keyboard shortcuts for some operations. You can perform these operations more quickly by using the keyboard shortcuts than using the mouse.
6 System Management
Table 6-8 Controls and corresponding keyboard shortcuts Control Menu Drop-down menu Button Description For any menu followed by an asterisk * (* represents a letter or number), you can press Alt+* to display the menu instead of choosing the menu. For any drop-down menu followed by an asterisk *, you can press * instead of choosing the menu when the menu is expanded. l For any button followed by an asterisk * (* represents a letter or number), you can press Alt+* instead of clicking the button. l When a dialog box is open and the focus is on a button, this button is the default button. If the focus is not on any button, OK is the default button. l When the focus is on a button, you can press Enter or space bar instead of clicking the button. l If the focus is on a control that does not respond when you press Enter, then the effect is the same when you press Enter or when you click the default button. Drop-down list When the focus is on a drop-down list, you can press the Down arrow key to expand the drop-down list. You can press the Up, Down arrow keys to switch between the options in a drop-down list, and press Enter to select the current option. If the focus is on an option button, you can press the space bar to select the option button. If the focus is on a check box, you can press the space bar to select or clear the check box. When the focus is on the navigation tree, you can press the Down arrow key or Up arrow key to switch between the nodes in the tree. And you can press the Left arrow key or Right arrow key to expand or collapse a node that contains subnodes. When there are multiple controls in a window, dialog box, or tab page, you can press Tab to switch from one control to another, and press Shift +Tab to switch to the previous control.
6 System Management
Operation Open the Help Exit the system Find Cut Copy Paste Delete Save Display full screen Select all Close the current window Restore down (when the service window in the public window is maximized) Minimize the window (applied to the service window in the public window) Maximize the window (when the service window in the public window is restored) Zoom in the topology view Zoom out the topology view
Shortcut keys F1 Alt+F4 Ctrl+F Ctrl+X Ctrl+C Ctrl+V Delete Ctrl+S F11 Ctrl+A Ctrl+F4 Ctrl+F5 Ctrl+F9 Ctrl+F10 Ctrl++ Ctrl+-
NOTE
The common area is under the toolbar on the Nastar client interface.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 From the navigation tree on the left of the Preferences window, select Main Window Title. Step 3 In Main Window Title, enter the title you want to display.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2308
6 System Management
Result
The title that you set is displayed as the main window title.
Context
After you set the font size, you need to log in to the Nastar client again for the setting to take effect.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 From the navigation tree on the left of the Preferences window, select Font. Step 3 Select an option in Font Size.
NOTE
Font Size can be as follows: l Small: The font size is 11 points. l Medium (Default): The font size is 12 points. l Large: The font size is 13 points.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 From the navigation tree on the left of the Preferences window, select Output Window. Step 3 Set relevant parameters in the Output Window area, and then click OK. Step 4 You can perform the following operations in the information output area at the bottom of the interface.
Issue 01 (2013-07-15)
2309
6 System Management
Option Copy
Description 1. Choose the displayed output information. 2. Right-click and choose Copy to copy the information to the clipboard.
Select All
1. Right-click in the output window and choose Select All. 2. Right-click again and choose Copy to copy all the displayed output information to the clipboard.
Clear
Right-click in the output window and choose Clear to clear all the displayed output information. 1. Right-click in the output window and choose Find. 2. In the Find dialog box, type the key words to be searched for in Find what.
NOTE l Match: To set whether the search content is case sensitive. The default is case insensitive. l Match whole word only: To perform a fuzzy search, clear Match whole word only. To perform a precise search, select Match whole word only. l Direction: To set the direction for a key word search.
Find
Save As
Right-click to choose Save As. In the Save dialog box, save the current output to a .txt file. Right-click in the output window and choose AutoScroll. The output information scrolls automatically to the latest information. Right-click in the output window again and choose AutoScroll, the auto scroll is disabled. Right-click in the output window and choose Parameter Settings. The Output Window pane is displayed in the Preferences window.
AutoScroll
Parameter Settings
----End
Related References
Parameters for Setting the Output GUI Parameters for Setting the Output GUI
Issue 01 (2013-07-15)
2310
6 System Management
Context
l l After you set the workbench display, you need to restart the Nastar client for the setting to take effect. The maximum number of links on the workbench is 100.
Procedure
l You can perform the following operations on the workbench. Option Enable/disable the workbench Description l Enable/disable the workbench 1. Choose File > Preferences from the main menu. 2. In the Preferences window, choose Workbench in the navigation tree on the left. 3. Select or deselect Enable Workbench. 4. Click OK.
NOTE After enabling the workbench, the workbench interface is directly displayed when you log in to the Nastar client next time.
1. Enable/disable the workbench Choose Help > Workbench from the main menu to enable the workbench. on the workbench interface to Click disable the workbench. Create workbench 1. Log in to the Nastar client to go to the workbench operation interface. 2. Right-click the blank space on the left of the interface and choose Create Workbench. 3. In the Create Workbench dialog box, enter the workbench name and description, and then select a workbench icon and background. 4. Click Create. Modify workbench 1. On the left of the interface, right-click the icon of the workbench to be modified and choose Modify Workbench. 2. In the Modify Workbench Link dialog box, modify the workbench information such as the workbench name, description, and icon. 3. Click Modify.
Issue 01 (2013-07-15)
2311
6 System Management
Description 1. On the left of the interface, right-click the icon of the workbench to be deleted and choose Remove. 2. In the Confirm dialog box, click Yes.
Import Workbench
The Nastar provides the function of importing the workbench data from a file. You can import the workbench data from a file to a new workbench of the Nastar. This facilitates you to create a workbench. 1. On the left of the interface, right-click the icon of a workbench and choose Import Workbench. 2. In the Import Workbench dialog box, select the workbench file to be imported, and then click Import.
Export Workbench
The Nastar provides the function of exporting the workbench data. You can export the data on the workbench to a file on the local client for future maintenance and browse. 1. On the left of the interface, right-click the icon of a workbench and choose Export Workbench. 2. In the Export Workbench dialog box, set the name and format of the export file, and then click Export.
In the Workbench window, you can create the shortcut for the Nastar function. 1. In the right of Workbench window, right-click the blank space and choose Create Shortcut. 2. In Create Shortcut dialog box, select function option. 3. Click Create.
Issue 01 (2013-07-15)
2312
6 System Management
Option
Description
Create a shortcut for executable In the Workbench window, you can create links of application executable programs. 1. In the right of Workbench window, right-click the blank space and choose Create Executable Application. 2. In the Create Executable Application dialog box, enter the name and description of an executable application, and then select the application and icon of the executable application. 3. Click Create .
NOTE l To check whether the executable command is valid, click Test. l You can use the local images of the operating system as the icon of shortcuts according to your requirements.
1. In the right of Workbench window, right-click a shortcut icon of Nastar function or executable application and choose Modify. 2. In the Modify Shortcut dialog box, change the name, description, icon or move to. 3. Click Modify.
In the right of Workbench window, right-click the blank space and choose Arrange icons by name to sort shortcut icons or executable link icons. After sorting, icons are listed in horizontal lines. 1. In the right of Workbench window, right-click a shortcut icon of Nastar function or executable application and choose Remove. 2. In the Confirm dialog box, click Yes. Then the function link icon or executable application link icon is deleted from the Workbench window.
Copy an icon
Copy the selected workbench icon to the clipboard. Then choose the shortcut menu Paste to copy the icon to another workbench. Cut the selected workbench icon to the clipboard. Then choose the shortcut menu Paste to move the icon to another workbench.
Cut an icon
Issue 01 (2013-07-15)
2313
6 System Management
Option
Description
Drag an icon to another position In the Workbench window, drag an icon to a proper position. ----End
Context
This setting takes effect for the current user that logs in to different clients, but is invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the Preferences window, choose Menu Settings in the navigation tree on the left.
Step 3 Select Enable menu folding feature to enable the menu folding feature.
NOTE
Issue 01 (2013-07-15)
2314
6 System Management
Table 6-10 Parameters for menu folding Parameter Default number of visible menus Description Default number of visible menu items in each main menu. Within the configured login times, if the number of used menu items exceeds this value, menus are displayed based on the actual number. Hide menus if they are not used for X consecutive logins Value range: 1-50 Default value: 10 Setting Value range: 1-50 Default value: 5
Context
l l The settings take effect after you log in to the client again. After you modify the number settings, the display of the number may be changed. You can view the display effect in the Positive number text box and Negative number text box.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the Preferences dialog box, select Number Format from the navigation tree on the left. Step 3 Set the number display format in the Number Format area.
NOTE
l Number of digits after decimal point: The value ranges from 0 to 3, and the default value is 2. l Number separator: whether to use comma (,) to group the integer part of a number. The value can be null or comma. l 0 before decimal point: whether to add 0 before the decimal point. By default, 0 is added before the decimal point.
Issue 01 (2013-07-15)
2315
6 System Management
Context
l l l After you set the time format, you need to restart the Nastar client for the settings to take effect. Next time when you log in to the client, the Nastar client automatically uses the settings that you set last time. The time display effect that you set is displayed in the Example.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 From the navigation tree on the left of the Preferences window, expand the Region Settings node and choose Time. Step 3 In the Time group box, set the time format. Step 4 Click OK. ----End
Related Tasks
Setting the Date Format of the Client Setting the Time Mode of the Client
Related References
Parameters for Setting the Time and Date Formats Parameters for Setting the Time and Date Formats
Context
l l l After you set the date format, you need to restart the Nastar client again for the settings to take effect. Next time when you log in to the client, the Nastar client automatically uses the settings that you used last time. The date display effect that you set is displayed in Example.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the navigation tree on the left of the Preferences window, expand the Region Settings node and select Date.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2316
6 System Management
l Date Separator: symbol to separate the date. There are three symbols for you to select: "/", "-", and ".". The default is "/". l Date Format: display format of the date. It can be set to "yyyy/MM/dd", "dd/MM/yyyy", or "MM/dd/ yyyy". The default is "MM/dd/yyyy".
Related Tasks
Setting the Time Format of the Client
Related References
Parameters for Setting the Time and Date Formats Parameters for Setting the Time and Date Formats
Context
l l After you set the time mode, you need to restart the Nastar client for the settings to take effect. Next time when you log in to the client, the Nastar client automatically uses the settings that you used last time.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the navigation tree on the left of the Preferences window, select Time Mode. Step 3 In the Time Mode group box, select Time Mode.
NOTE
l Server time mode: If you select this option, the time on the Nastar client is displayed based on the time zone where the server is located. For example, if the time of the client in UTC +08:00 is 10:00, and the server is in the UTC +07:00, the time displayed on the Nastar client is 9:00. l Client time mode: If you select this option, the time on the Nastar client is displayed based on the client OS time. The default value is Client time mode.
Related Tasks
Setting the Time Format of the Client
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2317
6 System Management
Procedure
Step 1 Choose File > Customize Toolbar from the main menu. Step 2 In the Customize Toolbar dialog box, select System or GIS in the Toolbar Groups group box. Step 3 Click Advanced. The Customize Toolbar dialog box displays the Toolbar Buttons group box.
NOTE
l Click Advanced again. The Toolbar Buttons group box is hidden. l The Toolbar Buttons group box consists of two parts: Available Tools and Customized Tools. All the buttons in Customized Tools are displayed on the toolbar, and the buttons in Available Tools are not displayed on the toolbar.
Step 4 In the Toolbar Buttons group box, set the buttons you want to display on the toolbar. l In the Available Tools group box, select one button or hold down Ctrl or Shift to select multiple buttons you want to display. Click Customized Tools group box. l buttons you do not want to display. Click Available Tools group box.
NOTE
In the Customized Tools group box, select one or hold down Ctrl or Shift to select multiple to move the selected buttons to the
You can click Reset or Reset All to restore the selected or all toolbars to their initial state. These operations help you adjust the display mode of buttons on the toolbar based on the initial state.
Step 5 Click OK. The selected toolbars are displayed in the toolbar tray based on your settings. Step 6 Optional: Adjust the positions of the toolbars in the toolbar tray. 1. 2. 3. Right-click in the blank area and choose Lock Toolbar from the shortcut menu. If Lock Toolbar is not selected, you can skip this step. Drag the toolbars to change their positions. Click Lock Toolbar to lock the toolbar tray.
NOTE
Right-click in the blank area and choose Reset Toolbar from the shortcut menu. The toolbar is restored to its initial state.
----End
Related References
Tool Buttons
6 System Management
Prerequisites
The client is not locked.
Context
l l This function is applicable to only the local client. In the Preferences dialog box, select Show main window when terminal locked in the Locking Settings area. Thus, after the client is locked, the main window of the client is visible.
Procedure
l The following table describes how to set the client to be locked manually or automatically. Lock Mode Automatically Operations After you set the client to be locked automatically, the client is automatically locked if it does not receive any operation instructions in the specified period. To set the client to be locked automatically, do as follows: 1. Choose File > Preferences. 2. Select Lock Settings in the navigation tree in the left pane of the Preferences dialog box. In the Lock Settings area, select Automatically locked. 3. Enter the lock time for the Automatically locked mode. 4. Click OK. 5. In the Information dialog box, click OK. The client is locked automatically when the specified time arrives. Manually To ensure Nastar system security, if you do not perform operations on the Nastar client for a period, you can lock the client to prevent others from performing illegal operations on the Nastar client. You can lock the client manually by using the following method: l Choose File > Lock Terminal from the menu bar. l Click ----End on the toolbar.
Related Tasks
Exiting the Nastar Client 6.1.6 Unlocking the Client
6 System Management
Prerequisites
The user name and password of the user who locks the client are available.
Context
Unlocking a client as user admin indicates to enter the user name and password of user admin on the locked client to unlock it. After the client is unlocked as user admin, the original login user is logged out. The system returns to the login interface. The settings and data that the original user do not save are lost. Generally, unlock the client as user admin only when the user name or password of the user who locks the client is unavailable. To maintain the settings and operations of the user who locks the client, ask user admin to initialize the password of the user, and then unlock the client by using the user name and initialized password. If you unlock your own account, the Nastar becomes operable after the account is unlocked.
Procedure
Step 1 When the client is locked, press Ctrl+Alt+U. Step 2 In the Unlock dialog box, enter the user name and the password, and then click OK. ----End
Related Tasks
6.1.5 Locking the Client
Context
The task of the following procedure is to set broadcast parameters and apply them to the current client.
Procedure
Step 1 Choose Tools > Broadcast Message from the main menu. Step 2 In the Broadcast Message dialog box, click Options. Step 3 In the Broadcast Messages Options dialog box, enter the values in Number of messages to display and Number of messages to save, click Save.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2320
6 System Management
Related Tasks
Sending Broadcast Messages
Related References
Parameters for Setting Broadcast Parameters Parameters for Setting Broadcast Parameters
Context
l l l The client can receive its own broadcast messages. The output area in the lower part of the Nastar client displays corresponding prompts. You have both permissions to set broadcast message parameters and send broadcast messages. Only the online Nastar client can receive the broadcast messages.
Procedure
Step 1 Choose Tools > Broadcast Message from the main menu. Step 2 In the Broadcast Message dialog box, enter the message content in the Message field.
NOTE
l A broadcast message cannot be null, and cannot exceed 128 characters. l The Nastar automatically adds line feeds according to the length of broadcast messages.
Step 3 Click Send. When the sending is complete, the Message dialog box is displayed on other clients. Users can click Detail to view the message. Step 4 In the Information dialog box, click OK. ----End
Related Tasks
Setting Broadcast Parameters
6 System Management
Context
Press Esc to exit the full-screen mode.
Procedure
l Choose Window > Full Screen from the main menu or click The topology is displayed in full screen mode. ----End on the toolbar.
Context
The sound files used for prompting network disconnection support only the sound files of the Wav type in the PCM format. The sound files of the Wav type can be recorded in two formats: PCM and Microsoft ADPCM.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the Preferences dialog box, select Disconnection Alert from the navigation tree on the left. Step 3 In the Disconnection Alert group box, select Sound an alert when the client is disconnected from the server. Step 4 Click Step 5 Click Step 6 Click OK. ----End . In the Open dialog box, select a sound file, and then click Open. to play the sound.
6.1.10 (Optional) Setting the File Transfer Mode Between the Server and Client
When a firewall is deployed between the server and client, the server cannot initiate file transfer to the client. In this situation, you must enable passive file transfer mode to ensure proper file transfer.
Procedure
Step 1 from the main menu Choose File > Preferences. Step 2 In the navigation tree of the Reference dialog box, choose Nastar Client/Nastar Server File Transfer Settings. Step 3 Select Passive Mode.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2322
6 System Management
Step 4 Set the FTP setup timeout value in Network Timeout. If the FTP setup duration reaches this value, the Nastar will report an error indicating the FTP setup failure. The default value is recommended. Step 5 Click OK. ----End
Context
If the Nastar server is upgraded but the client is not upgraded, it may cause the version of the client does not match that of the server.
Procedure
Step 1 Choose Help > Check For Upgrades from the main menu to check whether the client version matches the server version. l l If the versions match, the client does not need to be upgraded. In this case, click OK. If the versions do not match, you must upgrade the client. In this case, perform the following operations to upgrade the client: 1. 2. 3. ----End Click OK. In the Update Wizard: Update Applications window, click Continue. The upgrade progress is displayed. In the Update Wizard: Update Applications window, click Finish.
Related Tasks
6.1.12 Setting the Interval of Client Upgrade Check
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the Preferences dialog box, in the navigation tree on the left, select Upgrade. Step 3 Select the interval for upgrade checking in the Time Interval drop-down list box. Step 4 Click OK. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2323
6 System Management
Related Tasks
6.1.11 Checking Whether the Client Needs Upgrade
Procedure
Step 1 Choose Help > License Management > License Information from the main menu. Step 2 In the License Information dialog box, query the license information about resources and functions on the Resource Control Item and Function Control Item tabs. ----End
Related Tasks
Updating the Nastar License
Related References
Parameters for Querying the Nastar License
Context
l l l The Revoke License dialog box displays only available license files and does not display revoked and invalid licenses. Only the SMManagers user has the permission to revoke a license. If you revoke a license file but do not apply a new license, the Nastar sends license expiration prompts periodically.
Procedure
Step 1 Choose Help > License Management > Revoke License from the main menu. Step 2 In the Revoke License dialog box, select the license that is not used any more from the list, and then click Revoke License.
Issue 01 (2013-07-15)
2324
6 System Management
l Product: name of the product. l License SN: SN of a license file. l License File Name: Name of a license file.
Step 3 In the Information dialog box, click OK. The license file is revoked. ----End
Related Tasks
Querying the License Invalidation Code on the Nastar
Related References
Parameters for Revoking a Nastar License Parameters for Revoking a Nastar License
Procedure
Step 1 Choose Help > License Management > Query Invalid License Code from the main menu. Step 2 In the Query Invalid License Code dialog box, view the License SN, License invalidation code, and invalidation setting time.
NOTE
l License SN: SN of a License file. l Invalid License Code: The License invalidation code is a string generated after a License file is invalidated. According to this unique string, you can check that its corresponding License file is invalidated. When applying for a new License, you need to provide the invalidation code of the old License. l Invalidation Time : time when you set a License file to be invalidated.
Step 3 Select the information about the queried invalidation code, and then press CTRL+C to copy the information. The copied information about the invalidation code can be used to apply for a certificate.
NOTE
You can also right-click the information about the invalidation code and choose Copy to copy the information.
----End
Related Tasks
Revoking a License on the Nastar
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2325
6 System Management
Related References
Parameters for Querying the Invalidation Code of a Nastar License Parameters for Querying the Invalidation Code of a Nastar License
Prerequisites
When updating a license, delete the license files that are not in use from the server directories $/opt/nastar/etc/conf/license and $/opt/nastar/etc/conf/licensebak, and then update the license.
Context
l l l The type of the license applied for must be consistent with the version type. Before the licenses expire, the Nastar displays a warning periodically. The valid time for the license that is uniformly used in Nastar contains two fields: Expiry (Days) and End Time. If both the fields exist, the value of Expiry(Days) is valid.
Procedure
Step 1 Choose Help > License Management > License Information from the main menu. Step 2 In the License Information dialog box, click Update License. Step 3 In the Open dialog box, select the new license file(*.dat license file), and then click Open. Step 4 In the License Comparison Results dialog box, view the changes of the licenses, and then click OK. ----End
Follow-up Procedure
l l If all items of the old license are contained in the new license, you do not need any additional operations. If some items of the old license are not contained in the new license, the use of the new license is not affected. But you will see the information of the old license when using the security management function. For this case, you can restart the service (perform stop_svc, and then perform start_svc) to delete the information of the old license.
Related Tasks
Querying the Nastar License
Related References
Parameters for Querying the Nastar License Parameters for Querying the Nastar License
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2326
6 System Management
Procedure
Step 1 Choose Help > License Management > License Information from the main menu. Step 2 In the License Information dialog box, click Export License. Step 3 In the Save dialog box, set the path,File name, File type, and Encoding of the export file. Then click Save. ----End
Tool Buttons
This topic describes the system buttons. You can refer to this topic when you perform operations by using these buttons.
Related Tasks
Setting the Toolbar
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2327
6 System Management
Parameters
Name Name Description Description: Name displayed in the server list in the Login dialog box. This facilitates the user to select a server. Server Name (or IP Address) Description: The host name or the IP address of the Nastar server. Settings Value: This parameter is unique and mandatory. Value: l Value range of server name: 1-50 characters. l Examples of IP addresses: 10.0.0.1 Port Description: Port through which the client and the Nastar server are connected. Value: Value range: 1-65535. Default value: l Common mode: 31037 l Security (SSL) mode: 31039 Mode Description: Mode of the connection between the client and the Nastar server. Add Description: To add the information about a Nastar server. Modify Description: To modify the information about the specified Nastar server. Delete Description: To delete the information about the specified Nastar server. Value: l Common l Security (SSL) Value: Value: Value: -
Related Tasks
Logging In to the Nastar Client Logging In to the Nastar Client
Issue 01 (2013-07-15)
2328
6 System Management
Parameters
Name User Name Description Description: Valid user name registered with the Nastar server. Password Description: Password used for logging in to the Nastar client. Server Description: IP address and host name of the Nastar server. Settings Value: This parameter is mandatory. Value: According to the default security policy, the password length ranges from 8 to 16 characters. Value: This parameter is mandatory. 1. If the drop-down list contains server information, select the Nastar server to which you want to log in. 2. If the drop-down list does not contain server information, . In the displayed click Server List dialog box, add server information.
Related Tasks
Logging In to the Nastar Client Logging In to the Nastar Client
Issue 01 (2013-07-15)
2329
6 System Management
Parameters
Name Maximum Output Lines Description Description: The maximum lines that can be displayed in the output window. If the lines of output information exceed the maximum lines, the earliest input lines are deleted automatically and the maximum lines are displayed. Description: If you select this option and there is new output information, the output window scrolls to the new information automatically. If you deselect this option, you can only scroll to the new information manually. Description: If you select this option, the output information is dumped to a file according to the preset conditions.
NOTE You can set Dump Lines and Dump File Name only after selecting Automatic dump.
Automatic dump
Dump Lines
Description: Dump lines of output information. The value cannot exceed the value set in Maximum Output Lines. If the value exceeds the preset maximum value, the output information is dumped to the corresponding file automatically, and the dump lines are the same as that set in Dump Lines.
Description: The dump path and dump file name of output information.
Related Tasks
Setting the Output Information Setting the Output Information
Issue 01 (2013-07-15)
2330
6 System Management
Time Parameters
Name Time Format Description Description: HH:mm:ss and hh:mm:ss tt: l HH indicates the 24-hour format. l hh indicates the 12-hour format. l mm indicates minutes. l ss indicates seconds. l tt indicates the suffix for morning or afternoon. Time Indicator Description: Format of the suffix for morning or afternoon. Settings Value: The default value is HH:mm:ss. The value can be HH:mm:ss or hh:mm:ss tt. Example: For example, 15:10:20, 03:10:20 PM.
Value: The value is AM/PM. Example: For example, 15:10:20, 03:10:20 PM.
Description: Indicates whether to show the time zone. If you select the check box, the time zone is displayed after the time.
Setting method: Check box. Example: For example, 15:10:20 +08:00. Setting method: Check box. Example: For example, 15:10:20 DST.
Description: Indicates whether to show the daylight saving time. If you select the check box, the DST is displayed after the time.
Date Parameters
Name Date Separator Description Description: Symbol to separate the date. Settings Setting method: There are three symbols can be set to "/", "-", and ".". The default is "/". Example: For example, 01/01/2009.
Issue 01 (2013-07-15)
2331
6 System Management
Settings Value: There are three format can be set to "yyyy/MM/dd", "dd/MM/yyyy", or "MM/dd/yyyy". The default is "dd/MM/yyyy". Example: For example, 01/01/2009.
Related Tasks
Setting the Time Format of the Client Setting the Date Format of the Client Setting the Time Format of the Client Setting the Date Format of the Client
Parameters
Parameter Find Description Description: Find the matched license item after you enter a license name and then click .
NOTE If a matched record is found, the row of the record is displayed and automatically selected.
Product
Description: Product name. This column is hidden by default. To show this column, right-click the table heading and choose Product from the shortcut menu.
Resource
ID
Description: Identifier of the license.This column is hidden by default. To show this column, right-click the table heading and choose ID from the shortcut menu.
Issue 01 (2013-07-15)
2332
6 System Management
Parameter Capacity
Description Description: Capacity defined in the license. Consumption Description: Capacity of the licenses consumed. Overflow Time Description: Expiry time of each authorization item. Detailed Information Description: View details of authorization items. Server ID Description: Local server ID and authorization server ID displayed after you click Server ID Update License Description: Click the button to update license. Export License Description: Export a license to a file on the local client for future maintenance and browse.
Product
Description: Product name. This column is hidden by default. To show this column, right-click the table heading and choose Product from the shortcut menu.
Function
ID
Description: Identifier of the license.This column is hidden by default. To show this column, right-click the table heading and choose ID from the shortcut menu.
Supported or Not
Description: Whether the license file used by the Nastar suports this function.
Related Tasks
Updating the Nastar License Querying the Nastar License Updating the Nastar License
Issue 01 (2013-07-15)
2333
6 System Management
Parameter Description
Parameter License SN Description Description: Serial number of a license file. Invalid License Code Description: A string generated after a license file is invalidated. According to this unique string, you can check that its corresponding unique license file is invalidated. When applying for a new license, you need to provide the invalidation code of the old license. Invalidation Time Description: Time when you set a license file to be invalidated.
Related Tasks
Querying the License Invalidation Code on the Nastar Querying the License Invalidation Code on the Nastar
Button Description
Button Revoke License Description Revoke the license that is not in use to obtain the revocation code and then use the code to apply for a new license.
Parameter Description
Parameter Product Description Description: Name of a product. License SN Description: Serial number of a license file.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2334
6 System Management
Related Tasks
Revoking a License on the Nastar Revoking a License on the Nastar
Parameters
Parameter Number of messages to display Description Description: Number of latest messages displayed in History messages. Settings Value: Value ranges: 1-1000. Setting method: Enter it in the text box. Number of messages to save Description: Number of messages saved to the local. Value: Value ranges: 0-1000. Setting method: Enter it in the text box.
Related Tasks
Setting Broadcast Parameters Setting Broadcast Parameters
Issue 01 (2013-07-15)
2335
6 System Management
Parameters
Tab General Parameter Print Service Description In this box, you can set the printer properties and select to print a document to file. Name, Status, Type and Info respectively refer to the name, status, type and the information of the selected printer. If it permits, you can click Properties to set the printer properties. Print To File shows that you can print a document to a file. Range of pages to be printed. Value range: l All: to print all pages. l Pages: to print the specified pages. Copies Copies to be printed. Value range: l Number of copies: to print the specified copies. l Collate: to print copies one by one. It is valid if you print more than one copy. Page Setup Media Property of papers for print. Value range: l Size: size of the papers for print. l Source: source of the papers for print. Orientation Orientation in which pages are to be printed. Value range: l Portrait: print perpendicularly l Landscape: print horizontally l Reverse Portrait: print perpendicularly in reverse order l Reverse Landscape: print horizontally in reverse order Margins Margins of pages to be printed. Value range: l left(in): left margin of a page. l right(in): right margin of a page. l top(in): top margin of a page. l bottom(in): bottom margin of a page.
Print Range
Issue 01 (2013-07-15)
2336
6 System Management
Tab Appearance
Description Color of pages to be printed. Value range: l Monochrome: to print in black and white. l Color: to print in multiple colors other than black and white.
Quality
Quality of pages to be printed. Value range: l Draft: to print with low quality. l Normal: to print with generic quality. l High: to print with high quality.
Sides
Set whether to print on one side or on both sides. Value range: l One Side: to print on one side of a paper. l Tumble: to print on both sides of each paper and the shorter side upturns during printing. The printed pages are like a notepad. l Duplex: to print on both sides of each paper and the longer side upturns during printing. The printed pages are like a book. For the double-sided printing, the printer may use different terms.
Job Attributes
Property of a print job. l Banner Page: page that contains titles of the job. l Priority: priority of the print job. l Job Name: name of the print job. l User Name: name of the user that starts the print job.
Issue 01 (2013-07-15)
2337
6 System Management
Possible Causes
The Solid Converter PDF is installed. This tool is not compatible with the Nastar client. If this tool is set to a default printing device, the Nastar client exit.
Procedure
Step 1 In Windows, choose Start > Printers and Faxes. Step 2 Right-click a real printing device or another virtual printing device, and choose Set as Default Printer. Step 3 Restart the Nastar client. If the fault persists, contact the technical support personnel. ----End
Answer
Hold and drag the left mouse key to select the text information and view it.
Procedure
Step 1 Right-click in any area to restore the left mouse button to its normal state. ----End
6 System Management
1. 2.
Choose Help > Help Topics from the main menu, and then the Help window is displayed. Perform some operations on the Nastar, and switch to the opened Help window during the operations. In this case, the Help window may have no response. For example, when you open the Add Template dialog box, then switch to the help window, you cannot operate on the Help window.
Procedure
Step 1 Finish the operation. For example, close all the opened dialog boxes. The Help window will be recovered. Step 2 To browse help during the operations, press F1 to open the Help window. ----End
Procedure
Step 1 Press and hold the left mouse button and move the mouse slowly to select records. Do not select too many records at a time. ----End
Possible Causes
The Nastar client is based on Java. Therefore, the print function calls the related Java interface. However, the Java print function is incompatible with the virtual printer of Office 2003. When you use the print function and select the virtual printer of Office 2003, the Java environment cannot read any file.
Procedure
Step 1 Do not use the virtual printer of Office 2003. ----End
6 System Management
Possible Causes
l l The current user has no operation rights to the menu items. The menu items are not supported in the current window. For example, Topology > Move To is gray and unavailable if no corresponding topology object is selected in the topology view.
Procedure
Step 1 Apply to the administrator for the operation rights if required. Step 2 Learn the functions and operation conditions of the menu items and perform the operations when the conditions are satisfied. ----End
Procedure
Step 1 The cause of this issue is that the Sogou Input is incompatible with the JDK. You are recommended not to use the Sogou Input. ----End
6 System Management
User group
The user group refers to a collection of user accounts. Users that belong to a user group have all rights of the user group. Managing user rights based on user groups makes right management conveniently and clearly. The Nastar provides three default user groups: Administrators, SMManagers and Operators.
Operation rights
Operation rights indicates that a user is allowed to perform specific operations. After the operation right is allocated to the user, it indicates that the user can execute the specific operation. Operation rights are classified into two types by operation object: network device operation rights and network management application operations rights. Operation rights are associated with the managed domain. Users can operate only the NEs in the managed domains of them based on their operation rights.
Operation set
The operation set refers to a collection of operation rights. The operation set is used to assign the viewing right to a user or user group. When an operation set is assigned to a user or a user group, the user or user group has the right to operate the devices. By default, the Nastar operation sets are classified into the following types by operation object: l All Object Operations is of the network devices type. It contains the rights to operate all devices. l All Application Operations is of the Nastar applications type. It contains the rights to perform all Nastar application operations except the operations on security applications.
Issue 01 (2013-07-15)
2341
6 System Management
Description The access control list is used to allow the user to connect to the Nastar server by using the specified IP address or network segment. Thus, even if the user account and password are embezzled, the embezzler cannot use the embezzled account and password to connect to the Nastar server by using an IP address that is not included in the access control list. As a result, the Nastar security is improved. ACLs are classified into two types by effective scope: l System Access Control List: The ACL of the entire Nastar. All the users can connect to the Nastar server only by using specific IP addresses or network segments. l User Access Control List: The ACL of a user. The current user can connect to the Nastar server only by using specific IP addresses or network segments.
Managed domain
The managed domain refers to a range of security objects (including objects, object sets, subnets) that can be managed by users or user groups. After logging in to the Nastar client, users can view only the security objects in the managed domains of them.
NOTE Nastar objects include NE and VIP user. The collection of NEs and that of VIP users can be managed through the NE group and VIP user group. Therefore, the object set, managed domain, and view rights are not involved when you actually grant Nastar rights and you do not need to consider these concepts.
View rights
View rights indicates a user can view a security object on the Nastar. If the user can view a security object on the Nastar, it indicates that the user has the view right of the security object. The view right is related to the managed domain. Security objects are assigned to users or user groups, and thus these users or user groups have the view rights of these security objects.
Object set
A object set is a collection of devices and object services that can be managed. The object set is used to assign the device or device service viewing right to a user or user group. After a object set is added to the managed domain of a user or a user group, the user or user group has the right to view the corresponding devices or device services. The Nastar provides a default object set, namely, AllObjects. This object set contains all security objects.
Issue 01 (2013-07-15)
2342
6 System Management
Authority Management
The application of rights involves defining, assigning, and using rights. Authority management, which is essential to user management, controls the assignment and usage of rights. A system event indicates that a user performs an operation on a resource, as shown in Figure 6-2. Figure 6-2 System event
By using the authority management function, you can set certain restrictions on user operations, as shown in Figure 6-3. Figure 6-3 Authority management
Among the three phases of right application, defining rights involves establishing correlations between rights and operations. One operation or one type of operations corresponds to one type of right. Assigning rights involves establishing correlations between rights and users as well as correlations between rights and resources. Using rights means that users use resources according to the rights assigned by the administrator.
Rights
Rights specify specific operations that can be performed on specific objects. The operations that different users can perform are different. Elements of a right include objects and operations, as shown in Figure 6-4. Figure 6-4 Elements of a right
Operable objects mainly involve the Nastar and NEs, which are managed as devices. Nastar users can perform operations on the Nastar or NEs only when they are authorized to access and operate the Nastar or NEs. Figure 6-5 shows the operations that can be performed on the Nastar and NEs.
Issue 01 (2013-07-15)
2343
6 System Management
Operation Viewing VIP users Viewing VIP user theme results Viewing NEs Viewing NE theme results
Description View specified VIP users and VIP user groups. View results of themes related to specific VIP users.
View specified NEs and NE groups. View results of themes related to specific NEs. View and operate (including create, modify, and delete) specified VIP users and VIP user groups. View and operate (including create, modify, and delete) results of themes related to specified VIP users.
Operation rights
Viewing and operating VIP users Viewing and operating VIP user theme results Viewing and operating NEs
View and operate (including create, modify, and delete) specified NEs and NE groups.
Issue 01 (2013-07-15)
2344
6 System Management
Rights Attribute
Description View and operate (including create, modify, and delete) results of themes related to specified NEs.
Users
Users with the Nastar operation rights are referred to as Nastar user.
Authorization
Authorization means granting rights to specific users to specify the specific operations that they can perform. Figure 6-6 shows the general process of authorization. Figure 6-6 General process of authorization
Proce dure 1 2
Description Specify operable objects for a user. Specify the operations that can be performed on the operable objects.
When granting rights according to the process shown in Figure 6-6, you need to specify objects and operations to users one by one. When multiple users, objects, or operations are involved, the authorization becomes complicated. If you group the users, objects, and operations according to certain properties, the authorization can be simplified. Authorization refers to granting Nastar operation rights to users. If you plan user groups, object groups, and operation groups before authorization, you can improve the authorization efficiency.For details about how to grant rights for new users by the security administrator by creating a user group and operation set, see Figure 6-7.
Issue 01 (2013-07-15)
2345
6 System Management
After a user is added to a user group, this user is granted with all the rights of the user group. If the rights of the user group cannot meet the rights requirement of the user, you can grant specific private rights to the user. If the private rights of a user are changed, the public rights of the corresponding user group are not affected. If the public rights of a user group are changed, the change is applicable to all the users in the group.
NOTE
You do not plan the object sets before assigning the Nastar rights because the objects are not managed by the object sets in the Nastar system. If you want to group the objects according to certain properties, you can use the VIP group management function and NE group management function.
Authorization Planning
Authorization planning refers to analyzing user roles and grouping users, objects, and operations before user authorization. Proper authorization planning can greatly improve the efficiency of user authorization. Rights are granted to users according to the user roles. You can plan user groups, object sets, and operation sets by referring to Figure 6-8. Figure 6-8 Basis for authorization planning
6 System Management
Currently, the organizational structure of most telecom operators is formed on the basis of the responsibilities of departments, such as maintenance departments and network planning departments. Therefore, dividing user groups based on service departments is closes to the organizational structure of telecom operators. For example, you can group all the maintenance personnel in the department to form a maintenance user group. l Classified by service function If network devices are maintained according to the functions of the Nastar, users that use the same function to maintain network devices can be grouped to form xx function group. For example, users responsible for the VIP analysis can form a VIP user group and users responsible for neighboring analysis can form a neighboring user group. If you need to separate users that have different rights (such as operation rights and query rights), you can subdivide the VIP user group into an VIP operation user group and an VIP query user group. l Classified by subnet or area If the telecom operator divides a network into several subnets or areas, you can group the maintenance users of the devices in the same subnet or area to form xx subnet user group or xx area user group (such as A subnet user group). If the responsibilities of the maintenance users are classified according to the functions of the Nastar, you can subdivide the subnet user group into xx subnet xx function user group (such as A VIP group). The Nastar provides three default user groups. For details, see 6.2.6 Appendix B : Nastar Default Items. In addition to the default user groups, the Nastar supports the creation of a maximum of 99 user groups.
6 System Management
If users maintain network devices according the functions of the Nastar, you can group the operations related to all the objects maintained by a user (or user group) to form an operation set of xx function user group (such as the operation set of a VIP user group). To distinguish between the operation rights and query rights of each function, you can subdivide the operation set of certain function user group into an operation set of xx function management user group and an operation set of xx function query user group. For example, you can subdivide the operation set of a VIP user group to an operation set of the VIP management user group and an operation set of the fault query user group. l Classified by user You can group the operations related to all the devices managed by a user or user group to form an operation set of xx user or user group (such as an operation set of the maintenance group). The Nastar provides two default operation sets. For details, see 6.2.6 Appendix B : Nastar Default Items. In addition to the default operation sets, the Nastar supports the creation of a maximum of 98 operation sets.
Access Control
During the running of resources, external access requests must be checked for authorization. To implement access control, rights must be granted to users according to the user level and the validity of access requests must be checked. Access requests include login requests and operation requests. To check the validity of access requests, you need to check whether a user logs in to the device by using the valid user account and password and whether the operations performed by the user are within the range of the operation rights. If the user account and password are invalid or the operations are not within the operation rights, the valid check fails. In this case, the user cannot log in to the device or perform any operation on the device. When a user accesses the Nastar, the validity of the access request is checked by the Nastar. When a user accesses an NE, the validity of the access request is checked by the NE or a third party such as the Nastar. The Nastar supports the following access control policies to authenticate user logins to the Nastar or an NE: l System login mode The system access modes are restricted. Only two login modes are available, that is, multiuser mode and single-user mode. Generally, the Nastar system operates in multi-user mode. If you need to perform special operations on the Nastar server, you can set the Nastar to single-user mode to ensure that your operations are not affected by malicious operations performed by other users. l Access control list The IP address of the terminal that is used by a user to log in to the Nastar is restricted to a certain range. Access control lists include the system control list and the user access control list. The Nastar supports setting the management domain of a user when authenticating the operations of the user. The user can operate only the devices that are included in the management domain and cannot view or operate the devices that are not included in the management domain. In addition to the access control policy for user authentication, the Nastar also supports the security policy for user creation to ensure the system security.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2348
6 System Management
User account policy The user account policy specifies the length of the user name and the login-related operations, thus preventing malicious logins to the system.
User password policy The user password policy defines the password complexity and the period for changing the password, thus ensuring the security of the password.
User Monitoring
User access to resources is monitored. User monitoring includes login monitoring and operation monitoring. During user monitoring, if you find that certain user operations may have adverse impact on the system, take measures to forbid the user access. The Nastar is used as the monitor center to monitor the user sessions and user operations on all devices in a centralized manner. In the case of user session monitoring, the Nastar mainly monitors the online status of users. In the case of user operation monitoring, the Nastar mainly monitors the operation objects, time, and specific operation items. If a user performs illegal operations or operations that may have adverse impact on the system, the administrator of the Nastar can forcibly log out the user.
Operation Process
This section describes the authorized operation processes based on the following two scenarios: initial configuration and adjustment during routine operation and maintenance (OM). Table 6-11 describes the authorized processes. Default values have been set for user account policies and user password policies on the Nastar and you can change them as required. Table 6-11 Rights configuration list Scenario Initial configuration This scenario involves the user-securityrelated configuration s that you perform when using the Nastar for the Configurati on Item Access control list User account policy User password policy User group Action Set Operation References l Setting the System ACL l Setting the User ACL Modify Modify Setting the Account Policy Setting the Password Policy
Issue 01 (2013-07-15)
6 System Management
Scenario first time after its initial deployment. The configuration s cover user access control policies, user security policies, and user authorization policies. Adjustment during OM This scenario involves the user-related configuration s during network maintenance, such as creating and deleting users, modifying user information, and adjusting user rights.
Action Plan and create Plan and create Create and grant permission s
Operation References 1. Planning Object Groups 2. Creating an Object Group 1. Planning Operation Sets 2. Creating an Operation Set 1. Creating an Nastar User Account 2. Adding an Nastar User to an Nastar User Group
Operation set
User
User
Maintain
l NE information change 1. Adjusting NE groups 2. Viewing and Modifying the Information About a Nastar User l VIP information change 1. Adjusting VIP groups 2. Viewing and Modifying the Information About a Nastar User l Function change 1. Adjusting operation sets 2. Viewing and Modifying the Information About a Nastar User l Adding a newly created user to an existing user group Planning User Groups Creating a Nastar User Group Adding an Nastar User to an Nastar User Group
6 System Management
Prerequisites
You have logged in as a user in SMManagers.
Context
User admin can set access rights for all users. Users belonging to Security Manager User Group can set access rights for any user except user admin.
NOTE
To ensure security, you need to force all clients whose IP addresses are not within IP address or network segment to log out before you set the user ACL. For details, see Forcing a Nastar User to Quit.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, expand the User node, and then choose a user. Step 3 Select the policies for using ACLs on the ACL tab page in the right pane of the window by referring to Table 6-12. Then, click Apply.
TIP
When applying the system ACL to a user, you can click Set System ACL at the lower right corner on the System ACL tab to access the system ACL dialog box and modify the system ACL. You can click Add, Modify, or Delete to add, modify, or delete access control items.
Table 6-12 Parameters related to user ACLs Option Use all the ACLs in the system Use the specified ACLs Setting After this option is selected, the settings of the corresponding user ACL are consistent with those of a system ACL. The available options are the same as those of Use all the ACLs in the system. After selecting this option, you can log in to the Nastar server by using the client with the selected IP address of network segment.
NOTE
If the current user cannot unlock the client, the ACL of the user may be changed. In this case, you can contact admin and adjust the ACL.
----End
Prerequisites
You have logged in as a user in SMManagers.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2351
6 System Management
Context
l Newly configured access control items are applicable only to new proxy connections and not applicable to existing proxy connections. To apply the newly configured access control items to existing proxy connections, users must re-establish the proxy connections. When a user uses the proxy service to connect to an NE, the Nastar compares the source IP address with the access control items from the top to the bottom in the Proxy Service ACL dialog box. If a matched access control item is found, the comparison ends. If no matched access control item is found, the proxy connection request is rejected. Users can click Up or Down to change the access control item sequence in the Proxy Service ACL dialog box. If the networking includes gateway devices such as the Network Address Translation (NAT) device, and Nastar clients or NEs are located on the internal NAT network, users must set IP addresses in access control items to IP addresses that are stored on the NAT device and can be connected to by the Nastar server. Do not set IP addresses in access control items to internal network IP addresses to which Nastar clients or NEs are bound. If the Nastar client and server are installed on the same machine, you must set IP addresses in access control items to 127.0.0.1. If IP Address or Network Segment is set to 0.0.0.0/0 (or a value in IP address/0 format) and Operation is set to Accept in the proxy service ACL, clients in all network segments can connect to NEs.
l l
Procedure
Step 1 Choose Security > Proxy Service ACL from the main menu. Step 2 In the Proxy Service ACL dialog box, view the existing access control items. Click Add, Modify, or Delete to add, modify, or delete an access control item, and then click OK for the settings to take effect. Setting the Proxy Service ACL Adding an access control item Procedure 1. In the Proxy Service ACL dialog box, click Add. 2. In the Add Access Control Item dialog box, enter an IP address or network segment, set Operation, and click OK.
NOTE l If Operation is set to Accept, users can use the entered IP address or an IP address in the entered network segment to connect to an NE through the proxy service. l If Operation is set to Reject, users cannot use the entered IP address or an IP address in the entered network segment to connect to an NE through the proxy service.
Issue 01 (2013-07-15)
2352
6 System Management
Procedure 1. In the Proxy Service ACL dialog box, select an access control item to be modified, and click Modify. 2. In the Modify Access Control Item dialog box, change the IP address or network segment, modify Operation, and click OK.
NOTE l If Operation is set to Accept, users can use the entered IP address or an IP address in the entered network segment to connect to an NE through the proxy service. l If Operation is set to Reject, users cannot use the entered IP address or an IP address in the entered network segment to connect to an NE through the proxy service.
1. In the Proxy Service ACL dialog box, select an access control item to be deleted, and click Delete. 2. In the Confirm dialog box, click Yes.
NOTE After connecting to NEs from clients by using the proxy service and performing required operations, users must manually delete access control items that they have set to prevent other users from connecting to the NEs based on the access control items.
----End
Prerequisites
You have logged in as a user in SMManagers.
Context
User account policies must be set during the initial phase of site deployment and can be adjusted as required during maintenance.
Procedure
Step 1 Choose Security > Security Policy from the main menu. Step 2 In the Security Policy dialog box, click the Account Policy tab, and then view the current account policies.
Issue 01 (2013-07-15)
2353
6 System Management
TIP
You can set password policies on the Password Policy tab page. For details, see Setting the Password Policy.
Step 3 According to the policy planning, set account policies by referring to Parameters for Setting an Account Policy. ----End
Related References
Parameters for Setting an Account Policy
Prerequisites
You have logged in as a user in SMManagers.
Context
l l User password policies must be set during the initial phase of site deployment and can be adjusted as required during the maintenance. After the password policy is modified, the modification takes effect immediately for all user of the Nastar. For example, after the minimum length of the userpassword is changed,
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2354
Issue 01 (2013-07-15)
6 System Management
when an online user changes a password, the minimum password length must comply with the password policy. l l The password policy does not affect the configured password. The password policy specifies the password complexity, update period, and character restrictions. The password policy prevents users from setting a too simple password or using the same password for a long time.
Procedure
Step 1 Choose Security > Security Policy from the main menu. Step 2 In the Security Policy dialog box, click the Password Policy tab, and then view the current account policies.
TIP
You can set account policies on the Account Policy tab page. For details, see Setting the Account Policy.
Step 3 According to the policy planning, set password policies by referring to Parameters for Setting a Password Policy. Then, click OK to confirm the settings. Step 4 Click OK to confirm the settings. ----End
Related References
Parameters for Setting a Password Policy
6 System Management
client. The maximum number of user group sessions and user sessions can be set by security administrators through the Nastar client to limit the number of different user roles to access the system. As a result, the most important maintenance requirements can be met
Prerequisites
l l You have logged in as a user in SMManagers. A user or user group has been created or is being created.
Context
A user can log in to the Nastar server through multiple terminals. The user can also start multiple Nastar clients on one terminal to log in to the Nastar server. Setting the maximum number of user sessions limits the total number of sessions that a user creates on multiple login terminals. User groups are categorized based on user roles. To balance the access attempts of different user roles to the system, you can set the maximum number of user group sessions to limit the total number of sessions that the users in a user group create on all the login terminals. The setting of the maximum number of user sessions and user group sessions is limited by the system login mode. If the current system login mode is the single-user login mode, only one user admin is allowed to log in to the Nastar through one Nastar client regardless of the setting of the maximum number of user group sessions and user sessions.
Procedure
Step 1 Select an operation mode based on the actual situation. If ... Then ...
You are creating a user group or user Set the maximum sessions of user group, and the maximum number of online users (in the New User dialog box you can open by clicking Details > Advance) by referring to Creating a Nastar User Group and Creating an Nastar User Account. You have created a user group or user Set the maximum number of user group, and the maximum number of online users (in the New User dialog box you can open by clicking Details > Advance) by referring to Viewing and Modifying Nastar User Group Information and Viewing and Modifying the Information About a Nastar User. ----End
6 System Management
In single-user login mode, only user admin is allowed to log in to the system. Therefore, only user admin can set the system login mode to the single-user login mode.
Prerequisites
l l You have logged in as user admin. Plan the time of switching the login mode and ask other users to save their operations.
Context
CAUTION
Only the admin user can log in to the Nastar on a client and all the other users are forced to log out after the Nastar login mode is switched from the multiuser mode to single-user mode. You need to switch to the multiuser mode after you complete the operations in single-user mode. Thus, other users can operate the Nastar properly.
Procedure
Step 1 Choose File > Preferences from the main menu. Step 2 In the Preferences dialog box, choose System Login Mode in the navigation tree on the left.
6 System Management
Operation
Switch to the single-user mode Select Single-user mode and click OK. In the Set Switch Delay dialog box, set the delay time of login mode switch, and then click OK. l If the delay time is not 0, a dialog box for warning is displayed. After the specified delay time, the Nastar is switched to the single-user mode. l If the delay time is 0, the dialog box for warning is not displayed. The Nastar is directly switched to the singleuser mode immediately. The lower right corner on the Nastar client displays Singleuser mode. Switch to the multiuser mode Select Multiuser mode and click OK. The Nastar is switched to the multiuser mode immediately. The lower right corner on the Nastar client displays Multiuser mode. ----End
Prerequisites
You have logged in as a Nastar user.
Context
After a Nastar client is locked, only the current user or user admin can unlock it. The current user can unlock the client by following the message displayed in the window. To unlock the client as user admin, see Unlocking the Client.
CAUTION
When user admin unlocks a client. the original login user is logged out, and the settings and data that the user does not save are lost.
Procedure
Step 1 Choose File > Preferences from the main menu.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2358
6 System Management
Step 2 From the navigation tree in the left part of the window, select Lock Settings. Step 3 Select Automatically locked, set the time of enabling auto-locking, and then click OK to apply the settings.
NOTE
In the Preferences dialog box, select Show main window when terminal locked in the Locking Settings area. Thus, after the client is locked, the main window of the client is visible.
----End
Prerequisites
You have logged in as a Nastar user.
Context
After a Nastar client is locked, only the current user or user admin can unlock it. The current user can unlock the client by following the message displayed in the window. To unlock the client as user admin, see Unlocking the Client.
CAUTION
When user admin unlocks a client. the original login user is logged out, and the settings and data that the user does not save are lost.
Procedure
Step 1 Lock your Nastar client in either of the following ways: l Choose File > Lock Terminal from the main menu. l On the toolbar, click ----End .
Prerequisites
The user name and password of the user who locks the client are available.
Context
Unlocking a client as user admin indicates to enter the user name and password of user admin on the locked client to unlock it. After the client is unlocked as user admin, the original
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2359
6 System Management
login user is logged out. The system returns to the login interface. The settings and data that the original user do not save are lost. Generally, unlock the client as user admin only when the user name or password of the user who locks the client is unavailable. To maintain the settings and operations of the user who locks the client, ask user admin to initialize the password of the user, and then unlock the client by using the user name and initialized password. If you unlock your own account, the Nastar becomes operable after the account is unlocked.
Procedure
Step 1 When the client is locked, press Ctrl+Alt+U. Step 2 In the Unlock dialog box, enter the user name and the password, and then click OK. ----End
Related Tasks
6.1.5 Locking the Client
Prerequisites
You have logged in as a user in SMManagers.
Context
Illegal login indicates the login to the Nastar system of a Nastar user with an incorrect password. The maximum number of illegal login times and the auto-unlocking duration can also be set when the user account policies are set. For the description of relevant parameters, see Parameters for Setting an Account Policy. To manually unlock a user as user admin or security administrators, see Unlocking a User Account.
Procedure
Step 1 Choose Security > Security Policy from the main menu. Step 2 On the Account Policy tab page, set the maximum number of illegal login times and the autounlocking duration, and then click OK to apply the settings. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2360
6 System Management
Prerequisites
l l You have logged in as a user in SMManagers. You are familiar with user roles and have planned object groups. For details, see Planning Object Groups.
Context
After creating object groups during the initial phase of site deployment, you can adjust them or create object groups during site maintenance.
Procedure
l l Create the NE groups. For details, see 2.4.5 Managing NE Groups. Create the VIP groups. For details, see 2.4.6 Managing VIP Groups or VIP Users (VIP Analysis). ----End
Prerequisites
l l You have logged in as a user in SMManagers. You are familiar with user roles and have planned operation sets. For details, see Planning Operation Sets.
Context
After creating operation sets during the initial phase of site deployment, you can adjust them or create operation sets during site maintenance.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2361
6 System Management
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, right-click the Operation Set node and choose New Operation Set. You can also click tree, and then select New Operation Set. on the toolbar that is on the top of the navigation
Step 3 On the Details tab page, set the general attributes of operation sets by referring to Table 6-13. Table 6-13 Setting parameters on the Details tab page Parameter Type Parameter Description l Network Device: Operation right related to a specified NE, which can be performed on the Nastar so that network devices can be managed on the Nastar in a centralized manner. l Network Management Application: refers to the general function rights of the Nastar. These rights are not related to specific NEs. Name Refers to the name of an operation set. You are advised to set a name that represents the user management feature. Description of an operation set. Yes Mandatory (Yes/No) Yes
Description
No
Step 4 On the Members tab page, click Select, set operations in the operation sets by referring to Parameters for Creating an Operation Set, and then click OK.
Issue 01 (2013-07-15)
2362
6 System Management
TIP
You can click Copy Members from Operation Sets to copy operations from other operation sets.
----End
Related References
Parameters for Creating an Operation Set
Prerequisites
l l l You have logged in as a user in SMManagers or Subdomain Security Administrator Group. The modification of operation sets has been planned. For details, seePlanning Object Groups. Operation sets and operation rights are already created on the Nastar.
Procedure
Step 1 Choose Security > Security Management from the main menu.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2363
6 System Management
Step 2 In the Security Management navigation tree, expand the Operation Set node, select an operation set and view the information about the operation set on the right. If you need to change the information, perform Step 3.
NOTE
You can only allow to Modify the decription of the default operation sets All Object Operations and All Application Operations, but all information of the new operations that users created.
Step 3 In the area on the right, select a tab to modify the information about the operation set. Modify an Operation Set Modify the General properties Operation Click the Details tab. Modify the operation set name and description (the type of operation set cannot be changed). After modification, click Apply.
Set members of an operation Click the Members tab. At the bottom of the tab, click set Select. In the Select Operation Set Member dialog box, set the members of the operation set, and then click OK. If you need to delete one or more members of an operation set, select one or more members on the Members tab page, and click Delete. View Applicable for On the Applicable for tab, you can view only the users or user groups served by the operation set. The Applicable for tab displays the users or user groups served by the operation set.
Issue 01 (2013-07-15)
2364
6 System Management
Operation To allocate an operation set to a user or user group, do as follows: 1. Expand the User or User Group node and choose a user or user group. 2. Click the Domain tab on the right of the interface. Click Select. 3. In the displayed Select Domain dialog box, add a object set to the user or user group. Click OK. 4. Click the Operation Rights tab on the right of the window. Then click Select. 5. Select network device operations or network management applications. l Network Device In the Select Operation Rights dialog box, select an operation set. In the Operations area, select the corresponding operation set. l Nastar Management Application In the Select Operation Rights dialog box, choose Network Management Application in the navigation tree of authorized objects. In the Operations area, select the corresponding operation set. 6. Click Selected Rights. 7. Click Ok. to move the selected operation set to
----End
Prerequisites
You have logged in as a user in SMManagers.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 Expand the navigation tree, select the operation set to be viewed, and then view the users or user groups associated with the operation set in the right part of the Applicable for tab page. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2365
6 System Management
Prerequisites
l l You have logged in as a user in SMManagers. You are familiar with user roles and have planned operation sets. For details, see Planning Object Groups.
Context
The members of an operation set need to be adjusted in the following situations: l New types of objects are connected to the system and the operation rights of these object types need to be added to the operation right scope of Nastar user. In this case, security administrators need to create object sets based on the new object types or add the new object types to the corresponding object sets, and then adjust the relevant operation sets of users. Some objects are migrated due to network reconstruction. This may result in the change of the ranges of objects managed by users. The operation rights need to be adjusted accordingly.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 Expand the navigation tree and select the operation set to be adjusted. Step 3 On the Members tab page, click Select. Step 4 In the Select Operation Set Member dialog box, set the operation set members as required. If ... Then ...
New types of objects are connected to the Select and add the operation or operation set of system or new operation or operation set is the new object to the current operation set, and added to the current operation set then click OK. You need to delete an operation or Select the operation or operation sets to be operation set from the current operation set deleted, delete them, and then click OK.
TIP You can also right-click an operation or operation set from the navigation tree, and then choose Delete from the shortcut menu to delete the operation or operation set. Repeat this operation until all the operations or operation sets that you want to delete are deleted.
----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2366
6 System Management
Querying Authorization
Viewing the assignment of operation rights is to view the users or user groups to whom the operation rights or operation set rights of a device or object set are assigned. This operation is performed by security administrators.
Prerequisites
You have logged in as a user in SMManagers.
Context
The administrators group contains all Nastar operation rights except the security management rights. Therefore, in the query authorization dialog box, if you select an operation node or operation set node, the Authorized User/User Group area always displays the information about the Administrator group.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 On the top of the Security Management navigation tree, click .
Step 3 In the Authorization Details dialog box, expand the root node or parent node in the navigation tree, and choose a node. After selection, the corresponding operations or operation sets are displayed in the Operation area.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2367
6 System Management
Step 4 In the Operation area, expand the root node or parent node, and then select an operation. On the right of the interface, the users and user groups that the operation rights are assigned to are displayed in the Authorization User/User Group area. ----End
Prerequisites
You have logged in as user admin.
Context
l For a newly installed Nastar, export operation set files about the network management application and network devices, add new operation sets to the files, and import the changed files to the Nastar using the Import Operation Sets function. In this way, you can create operation sets in batches at one time. For a Nastar that has being running for a period of time, you can export operation set files to the local computer. This helps you restore operation sets using the Import Operation Sets function after upgrading and bulk deleting old operation sets. The default Nastar operation sets All Object Operations and All Application Operations are excluded from exported operation sets.
Procedure
Step 1 Choose Security > Security Management from the main menu. in the upper left corner of the window, and then select Export Step 2 Click the shortcut icon Operation Sets. Rename the exported file and save the file to a specified location. ----End
Result
l The Network Management Application and Network Device operation sets are saved in two separate files.
NOTE
All operation information is listed from columns A to E in the exported operation set files. The information listed after column E is operation sets exist on the Nastar. Members in the existing operation sets are indicated by the letter Y in the operation list.
l l
The default Nastar operation sets All Object Operations and All Application Operations are excluded from exported operation sets. The default file names are OperationSet_NetWork Device.csv and OperationSet_Network Management Application.csv. You can specify the OperationSet part in the file name.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2368
Issue 01 (2013-07-15)
6 System Management
Prerequisites
l l l You have logged in as user admin. You are familiar with user roles and have planned operation sets. For details, see Planning Operation Sets. A file containing operation set information is available. You can perform the operations described in Adding or Modifying Operation Sets in Batches.
Context
The operation set files to be imported must be exported using the Export Operation Sets function.
Procedure
Step 1 Choose Security > Security Management from the main menu. in the upper left corner of the window, select Import Operation Step 2 Click the shortcut icon Sets, select the .csv file to be imported, and then click OK. ----End
Result
After the file is imported successfully, you can view the changes of operation set nodes in the navigation tree or select an operation set to view the change of its settings.
Prerequisites
l l l l You have logged in as user admin. The file containing the exported operation set information should be edited by user admin based on the right-related policy and operation set planning. The information about all the operation sets in the Nastar is exported and saved in a file. For details, see Exporting the Files Containing Operation Set Information. You are familiar with the planning of system operations or operation sets. For details, see Planning Operation Sets.
Issue 01 (2013-07-15)
2369
6 System Management
Context
CAUTION
l l This operation is not applicable to the change of operation set names. The columns from A to E in the file containing the exported operation set information record the information about all the operation rights. The information in columns from A to E cannot be modified. If it is modified, importing the file will fail. Therefore, you need to export the information about all the operation sets again if this information is modified. Each column after column E in the file containing the exported operation set information is considered as an operation set unit. The first cell in each column must be filled with the name of an operation set. To add a right to an operation set, fill the cell corresponding to the row of the right with Y. Otherwise, keep the cell null. The table cells that are in line 10 except columns from A to E contain only operation set names. If the operation set name in the file exists in the current Nastar, the operation set fails to import. The rule for naming a new operation set is the same as the rule for naming an operation set created in the NMS.
l l l
Procedure
Step 1 Open and edit the .csv file containing the exported operation set information. Figure 6-10 Files of the NMS application operation sets
Adding an operation set To add an NMS application operation set, perform the following steps: 1. In the csv file, add a column next to column E, and enter the name of the new operation set in the first cell of the new column, such as Figure 6-10. Assume that the NMS has Operation Set A and Operation Set B, you can add New Operation Set c next to Operation Set B. Adding members for the new operation set. You can enter Y in the line where an operation to be performed. See Figure 6-10. The blue words stand for that Create Subnet and Modify NE are performed for New Operation Set c.
NOTE
2.
Modifying the operations of an operation set 1. Enter Y in the associated table cell of operation set. If you need to delete Query System Logs of Operation Set A, you can delete Y of Operation Set A. If you need
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2370
Issue 01 (2013-07-15)
6 System Management
to add Create Subnet, you can enter Y in the associated table cell of Operation Set A. Step 2 Save the file, and then import the file by referring to Importing the Files Containing Operation Set Information for the file to take effect. ----End
Result
After the file is imported successfully, you can view the nodes in the navigation tree and view the change of the rights in an operation set.
Prerequisites
l l l You have logged in as a user in SMManagers. Ensure that no user or user group is using the operation set to be deleted. For details, see Viewing the Associative User or User Group of an Operation Set. You are familiar with user roles and have planned operation sets. For details, see Planning Operation Sets.
Context
You are not allowed to modify the default operation sets All Object Operations and All Application Operations.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, choose the Operation Set node.
The table on the right displays all the operation sets on the Nastar. Step 3 select the operation set to be deleted, and then click Delete. You can also right-click the operation set and choose Delete. Step 4 In the Confirm dialog box, click Yes. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2371
6 System Management
Issue 01 (2013-07-15)
2372
6 System Management
Application Scenario After defining multiple object sets, you can use this means to centrally grant the associated rights to users. For example, assume that you want to grant users in a region operation rights for different functions but the operation objects of these users are different. In this case, you can define these operation objects as an object set and then grant the object set rights to the users.
Action 1. from the main menuChoose Security > Security Management. 2. In the Security Management navigation treeRight-click User and choose New User from the shortcut menu. 3. On the Assign Operation Rights of Objects tab page, select the NE groups and VIP groups in the NE Group Authentication and VIP Group Authentication sub-tab pages. 4. Click OK.
You can use this means to grant users the operation rights for a function.
1. from the main menuChoose Security > Security Management. 2. In the Security Management navigation treeRight-click User and choose New User from the shortcut menu. 3. On the Operation Rights tab page, click Select. 4. In the displayed Select Operation Rights dialog box, select Nastar Management Application in the Authorization Objects area and select one or multiple operations in the Operation area. 5. In the Select Operation Rights dialog box, click and then click OK.
You can use this means to grant users the operation rights for an object.
1. from the main menuChoose Security > Security Management. 2. In the Security Management navigation treeRight-click User and choose New User from the shortcut menu. 3. On the Assign Operation Rights of Objects tab page, select an NE or a VIP user or multiple NEs or VIP users in the NE Object Authentication and VIP Object Authentication sub-tab pages. 4. Click OK.
Issue 01 (2013-07-15)
2373
6 System Management
Application Scenario This means applies to the scenario where the rights granting difference between users is small. You can create a user, copy the user's rights, and then further customize rights accordingly.
Action 1. from the main menuChoose Security > Security Management. 2. In the Security Management navigation treeRight-click User and choose New User from the shortcut menu. 3. Click Copy Rights from Users. In the displayed dialog box, select the user whose rights you want to copy. 4. Click OK. Then, customize rights based on this user. This helps improve the authorization efficiency.
NOTE
To learn the impact of operation object authorization and operation rights authorization on user operations, see 6.2.5 Appendix A : Nastar Operation Right References.
Prerequisites
l l l You have logged in as a user in SMManagers. You are familiar with the responsibilities of users and the operation rights of the Nastar default user groups. You have planned user groups. For details, see Planning User Groups.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, right-click the User Group node and choose New User Group. You can also click then select New User Group. on the toolbar that is on the top of the navigation tree, and
Step 3 In the New User Group dialog box, set the properties of the new user group. You must manually set the name of the user group. For the other properties of user group, you can set them after you create the user group successfully.
Issue 01 (2013-07-15)
2374
6 System Management
Operations
On the Details tab, set the user group name, description, type, and maximum number of sessions. l To add members, on the Details tab, click Add. In the Add User dialog box, set the members to be added to the user group. l To delete members, on the Details tab, select the members to be deleted from Members, and then click Delete.
Managed domain of On the Domain tab, click Select. In the Select Domain dialog box, set user group the management domain of the user group, and then click OK. Operation rights of user group On the Operation Rights tab, click Select. In the Select Operation Rights dialog box, set the operation rights of the user group, and then click OK.
NOTE
Click Copy Rights from User Groups. In the Copy Rights from User Groups dialog box, select user groups and copy the management domain rights and operation rights of these user groups.
Step 4 In the New User Group dialog box, click OK. ----End
Related References
Parameters for Creating a Nastar User Group
Prerequisites
l l You have logged in as a user in SMManagers. You are familiar with the planning of user accounts and password policy. For details, see Access Control.
Context
l l Users with the Nastar operation rights are referred to as Nastar user. Users that are authorized to perform operations on only NEs are referred to as NE users. After creating an Nastar user, you are advised to add the user to the corresponding user group according to the responsibilities of the user so that the Nastar user can own the public rights of the user group.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2375
Issue 01 (2013-07-15)
6 System Management
When you create an Nastar user, the property settings must comply with the password policy and the account policy.For details about how to set a password policy and an account policy, see Setting the Password Policy and Setting the Account Policy.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, right-click the User node and choose New User. You can also click select New User. on the toolbar that is on the top of the navigation tree, and then
Step 3 In the New User dialog box, set the properties of the new user. You must manually set the user name and password. For the other properties, you can use default values or set them after you create the user account successfully. User Properties Common properties Operations On the Details tab, set user properties, such as the user name, description content, and password.
Issue 01 (2013-07-15)
2376
6 System Management
Operations l To add owner groups, on the User Groups tab, click Add, select the user groups to which you want to add a user.
NOTE Only users of the SMManagers group can view their own rights.
l To delete owner groups, on the User Groups tab, select the user groups to be deleted from the user group list, and then click Delete. Managed domain of user On the Domain tab, click Select. In the Select Domain dialog box, set the managed domain of the user. On the Operation Rights tab, click Select. In the Select Operation Rights dialog box, set operation rights of the user. To learn the impact of operation rights authorization on user operations, see 6.2.5 Appendix A : Nastar Operation Right References. Access control list (ACL) Operation objects On the ACL tab, set the ACL for the user. On the Assign Operation Rights of Objects tab page, select the NE objects and VIP user objects that the user can view or operate. l With view rights, users can view NE or NE group functions and view theme tasks and results of the NEs that they have selected. l With operation rights, users can view, create, modify and delete NEs or NE groups, and view, create, modify and delete the theme tasks and results of the NEs that they have selected. To learn the impact of operation set authorization on user operations, see 6.2.5 Appendix A : Nastar Operation Right References.
NOTE
Click Copy Rights from Users. In the Copy Rights from Users dialog box, you can select users and copy the rights of the managed domain and the operation rights of these users; however, you cannot copy the rights of the user groups that these users belong to.
Related References
Parameters for Creating a Nastar User Account
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2377
6 System Management
Prerequisites
You have logged in as a user in SMManagers.
Context
You can use either of the following methods to add an Nastar user to a user group. This section describes how to use the first method to add an Nastar user to a user group. l l Select an Nastar user, and then add the user to a user group. Select a user group, and then add an Nastar user to the group. For details, see Adjusting the Members in a User Group.
Procedure
Step 1 Select a method of opening the window for adding an Nastar user according to the scenario. Scenario Method
During the creation of an Nastar user In the New User dialog box, click the User Groups tab. After the creation of an Nastar user 1. Choose Security > Security Management from the main menu. 2. Expand the navigation tree, select the Nastar user to be operated, and then click the User Groups tab in the right part of the window. Step 2 Click Add, select the user group to which the user is to be added, and then click OK. If you need to assign rights to the user, continue the setting by referring to Assigning Rights to an Nastar User or User Group. ----End
Prerequisites
l
Issue 01 (2013-07-15)
6 System Management
You are familiar with user roles and have planned user groups. For details, see Planning User Groups.
Context
You need to adjust the members in a user group in some scenarios, for example: l l The requirements on the rights of a user are the same as the rights of a certain user group. In this case, you can add the user to the user group to facilitate centralized management. A Nastar user account is not in use or the user role is changed. In these cases, you need to delete the user from the user group.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 Expand the navigation tree and select the user group whose members are to be adjusted. In the right part of the window, perform relevant operations on the Members tab page according to the actual cause. Cause Add Nastar users to the user group Operation Click Add, select the Nastar users to be added to the user group, and then click OK.
Delete Nastar users from a user group Select the Nastar users to be deleted, and then click Delete. ----End
Prerequisites
l l You have logged in as a user in SMManagers. You have planned user groups. For details, see Planning User Groups.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 On the top of the Security Management navigation tree, expand the User Group node, and then view the information about the user group.
Issue 01 (2013-07-15)
2379
6 System Management
Step 3 In the area on the right, select a relevant tab to modify the information about the user group. Modify Properties Modify general properties Operation Click the Details tab. Modify the user group name, maximum sessions and description (the type of user group cannot be changed). After modification, click Apply. To add users, click Add on the Members tab. In Add User, add users. To delete users, select the user group and then click Delete. On the Members tab, view the users that belong to the user group. Modify the managed On the Domain tab, click Select. In Select Domain dialog box, add or domain delete devices or object sets. Modify operation rights On the Operation Rights tab, click Select. In Select Operation Rights dialog box, add or delete the operation rights of network management applications and devices. Click the Current Session tab to view the online users of the user group.
Modify members
Related References
Parameters for Setting the Nastar User Group Information Parameters for Assigning Operation Rights to Nastar User and User Groups
Prerequisites
You have logged in as a user in SMManagers.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2380
6 System Management
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 On the top of the Security Management navigation tree, click .
Step 3 In the Select User for Compare dialog box, select a user from the left and right columns.
NOTE
On the Nastar, you cannot compare rights of the same user. If you select the same user in the left and right columns, the Compare button is unavailable.
Step 4 Click Compare and view the result in Compare User Rights Result.
NOTE
During the comparison of rights between user A and user B, if user A has an operation right but user B does not have this right, this right node of user B is displayed as a blank node.
In the Compare User Rights Result dialog box, the Nastar can display user rights in the following two modes: l Display all rights: All user rights are displayed in the group box. l Display only differences: Only the differences between user rights are displayed in the group box. ----End
6 System Management
Prerequisites
You have logged in as a user in SMManagers.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, expand the User node. Step 3 Select a user, and then view the information about the user in the right part of the window. Step 4 Select the user whose information you want to modify, and then modify the information about this user on the relevant tab in the right area. Modify Properties Modify general properties Change the owner user group Operation On the Details tab, modify the user information (the dimmed properties are not configurable). To add a user group, click Add on the User Groups tab. In Add User Group, add a user group. To delete a user group, click Delete.
Modify the managed On the Domain tab, click Select. In Select Domain, you can perform domain (ignore this the following operations: item) l Add objects or object sets. l Delete objects or object sets. Modify operation rights On the Operation Rights tab, click Select. In Select Operation Rights, you can perform the following operations: l Add operation rights. l Delete operation rights. Modify the ACL To set the IP addresses that the user can use for login, select Use all the ACLs in the system and Use the specified ACLs on the ACL tab. To add, modify, or delete IP addresses or network segments, select System ACL.
Modify the rights of On the Operation Object Rights tab, assign the view or operation the operation objects rights to the selected NEs or VIP users. ----End
Related References
Parameters for Setting the Nastar User Information Parameters for Assigning Operation Rights to Nastar User and User Groups
Issue 01 (2013-07-15)
2382
6 System Management
Prerequisites
l l You have logged in as a Nastar user. You are familiar with the system user password policy. For details, see Setting the Password Policy.
Context
CAUTION
User admin is the super user of the Nastar system. The default password is empty. During the initial phase of the site deployment, you must change the password of user admin first to ensure system security. When setting a password, ensure that the password meets the requirement of the password policy.
Procedure
Step 1 Choose File > Change Password from the main menu. Step 2 In Change Password window, enter the old password and the new password, and confirm the password, and then click OK. ----End
Context
l l The password setting must comply with the password policy. For details on how to set a password policy, see Setting the Password Policy. The members of the SMManagers group can reset the passwords of other users except the admin user.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 In the Security Management navigation tree, expand the User node. Right-click the user whose password is to be reset and choose Reset Password. Step 3 In the Reset Password dialog box, set New Password and Confirm Password, and then click OK.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2383
6 System Management
If User must change password for next login is selected, you need to change the password when you log in to the Nastar client next time. Otherwise, you do not need to change the user password when you log in to the Nastar client next time.
Related Tasks
6.1.2 Changing the Password of the Current User
Prerequisites
You have logged in as a user in SMManagers.
Context
The super user in the Nastar system, that is, user admin, cannot be deleted.
WARNING
Performing this operation will permanently delete the user.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 Expand the navigation tree, right-click the user to be deleted, and then choose Delete from the shortcut menu. ----End
Prerequisites
l l l
Issue 01 (2013-07-15)
You have logged in as a user in SMManagers. All users in the group to be deleted are offline. You have planned user groups. For details, see Planning User Groups.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2384
6 System Management
Context
The default user groups provided by the Nastar system, that is, Administrators, SMManagers, and Operators, cannot be deleted.
WARNING
l l Performing this operation will permanently delete the user group. After a Nastar user group is deleted, the public rights of the group are deleted accordingly. That is, all users in this group do not have these public rights any longer. Delete a Nastar user group with caution.
Procedure
Step 1 Choose Security > Security Management from the main menu. Step 2 Expand the navigation tree, right-click the user group to be deleted, and then choose Delete from the shortcut menu. ----End
Context
l l A session refers to the connection established between the client and the server. A session starts when the user logs in to the client, and ends when the user logs out of the client. Multiple sessions can be created by using one Nastar user account. On the Nastar, a user account can be used to log in to multiple clients concurrently. You can set the maximum number of clients to which a user account can be used to log in concurrently in Maximum of online users on the Details tab. If this user account is used to log in to a certain number of clients, the same number of sessions are established. l When the client uses multiple network adapters, the value of Operation Terminal is selected randomly among available IP addresses.
Procedure
Step 1 Choose Security > User Session Monitoring from the main menu.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2385
6 System Management
Step 2 In the User Session Monitoring window, view the information about login and other operations performed by Nastar users. Monitoring Mode Session Monitor Operation In the Session Monitor area, you can view the information about online users and sessions.
NOTE l After the Nastar server is restarted or the network is recovered from a disconnection, you need to click Refresh to update the session monitoring table. l If you select the local client in the Session Monitor area, Force User to Log Out becomes unavailable.
Operation Monitor
In the Operation Monitor area, you can do as follows to view the information about operations corresponding to sessions: 1. In the Session Monitor area, select a session. 2. In the Operation Monitor area, select Filter. 3. In the Filter dialog box, set the filtering condition such as Operation, Operation Object, or Operation Result. The operation information that meets the filtering condition is displayed in the Operation Monitor area. 4. Double-click an operation record. In the Operation Details dialog box, view the monitoring information.
NOTE l The Operation Monitor area displays the information about only the operations performed after the User Session Monitoring window is opened. After a monitored user performs operations, the operation monitoring table is updated in real time. l You can monitor the operations performed by the following users in Operation Monitor: l Common users or Administrators: In the Query Operation Logs window, click Choose at the lower left corner in the Filter dialog box. In the Select Operation Name dialog box, you can view the operations that can be monitored. For details, see Querying the Nastar Operation Logs. l SMManger: In the Query Security Logs window, click Choose at the lower left corner in the Filter dialog box. In the Select Security Event dialog box, you can view the operations that can be monitored (The Log out the server operation is not monitored.). For details, see Querying the Nastar Security Logs.
----End
Issue 01 (2013-07-15)
2386
6 System Management
Context
l Only administrators, members of the SMManagers group, and subdomain security administrators can force a user to quit. If you force a user to quit session, only the user corresponding to a session is logged out forcibly. For example, a user logs in to the Nastar server as user user_z on clients A and B respectively. Sessions a and b are generated. When user user_z on client A is forcibly logged out, session b is not affected. Users who have logged in cannot force themselves to quit their corresponding sessions.
Procedure
Step 1 Choose Security > User Session Monitoring from the main menu. Step 2 From the session monitoring table, select the records of the sessions to be quitted forcibly, and then click Force User to Log Out. Step 3 In the confirm dialog box, click Yes. ----End
Prerequisites
l l You have logged in as user admin or a user in SMManagers. Unlocking the user does not affect system security.
Procedure
Step 1 The Nastar supports the following user unlocking modes. Unlocking Mode Manual unlocking Operation Only a member of the SMManagers group can perform the following operations: 1. Choose Security > Security Management. 2. In the Security Management navigation tree, expand the User node. 3. Right-click the locked user account, and choose Unlock User. After that, the unlocked user can log in to the Nastar successfully.
Issue 01 (2013-07-15)
2387
6 System Management
Operation The locked user can log in successfully only when the time reaches the preset automatic unlocking time.
NOTE You can set the automatic unlocking time in Account Policy. The procedure is as follows. Choose Security > Security Policy. In the displayed Security Policy dialog box, click the Account Policy tab, and then set Auto Unlock.
----End
Context
On the Nastar, users of current sessions cannot send messages to themselves.
Procedure
Step 1 Choose Security > User Session Monitoring from the main menu. Step 2 In the Session Monitor area, send messages to the users of the specified sessions or all sessions. Sessions to Be Sent Operation A specified session Right-click a session and choose Send Message. Enter the message contents, and then click Send. Use the Ctrl or Shift key to select multiple sessions. Right-click the selected sessions and choose Send Message. Enter the message contents, and then click Send. Use the combination key Ctrl+A to select all sessions. Right-click the selected sessions and choose Send Message. Enter the message contents, and then click Send.
Multiple sessions
All sessions
NOTE
You can choose Tools > Broadcast Message to send broadcast messages to the users of all sessions. For details, see Sending Broadcast Messages.
----End
6 System Management
integrity of data transmission. You can set the SSL communication mode for an NE, the Nastar client, and the Nastar server to enable the SSL protocol.
Setting a Secure Connection Between the Client and the Nastar Server
This topic describes how to set the SSL communication mode between the Nastar client and server.
Prerequisites
The SSL communication mode is enabled on the Nastar server. For details about how to set the SSL mode, see Administrator Guide.
Context
Data transmission security is ensured when the SSL communication mode is set on both the client and the server.
Procedure
Step 1 Start the Nastar client. In the Login dialog box, click .
Step 2 In the Server List dialog box, select a server record, and then click Modify. In the Server List dialog box, if no server information exists, you need to add the server information. Do as follows: 1. 2. In Server List, click Add. In the Add Server Information dialog box, enter the name, host IP address, port, and communication mode of the Nastar server.
NOTE
When you set the communication mode to Security(SSL), the SSL communication mode is set for the client.
Step 3 In the Modify Server Information dialog box, select Security(SSL) from the Mode drop-down list. After change the communication mode in the Mode drop-down list, the value of Port changes automatically. By default, the port and mode are set as follows: l If the communication mode is Common, the port is 31037. l If the communication mode is Security(SSL), the port is 31039. Step 4 Click OK in the Modify Server Information and Server List dialog boxes. Go back to the Login dialog box. The client setting is complete. ----End
6 System Management
Prerequisites
l l The eSAU, SAU (RAN SAU, LTE SAU, PS SAU), and Nastar server must support SSL authentication. Digital certificates used for SSL authentication have been configured on the eSAU, SAU (RAN SAU, LTE SAU, PS SAU), and Nastar server. For details about the configuration process, see Basic Authentication Process by Using Digital Certificates.
Context
Data transmission security is ensured only when the SSL communication mode is set on the eSAU, SAU (RAN SAU, LTE SAU, PS SAU), and Nastar server.
Procedure
Step 1 Choose Security > Certificate Authentication Management > SSL Connection Management from the main menu. Step 2 In the SSL Connection Management window, view Connection Type and Authentication mode in the Device column. Check the network communication mode of the current device based on the description provided in Table 6-15. Table 6-15 Network communication modes Network Communication Mode Common connection mode SSL connection mode Connection Type Common SSL Authentication mode Bidirectional authentication
Step 3 In the SSL Connection Management window, select or deselect an eSAU or SAU and click Modify. In the displayed Modify SSL Connection Policy dialog box, set Connection Type and Authentication mode based on the actual network plan. For detailed parameter settings, choose Product Documentation > Operation and Maintenance > System Management > Managing Digital Certificates > Reference of the Certificate Authentication Management GUI to see Parameters for SSL Connection Management. Step 4 Click OK to make the settings take effect.
Issue 01 (2013-07-15)
2390
6 System Management
CAUTION
l After the network communication mode among the eSAU or SAU (RAN SAU, LTE SAU, PS SAU) and the Nastar is changed, the Nastar automatically disconnects the current connection and connects to the eSAU or SAU (RAN SAU, LTE SAU, PS SAU) again based on the new network communication mode. l After the network communication mode is changed, you need to check that the FTP transfer mode matches the network communication mode in the following way: The common connection mode matches the FTP transfer mode and the SSH/SSL connection mode matches the SFTP/FTPS mode. Therefore, you need to manually change the FTP transfer mode. For detailed operations, see Step 5 through Step 12. Step 5 Log in to the active eSAU node as user omcuser. Step 6 Run the following command to switch to user root. ~> su - root Password:Password of root Step 7 Do as follows to change the FTP transfer mode of the eSAU. 1. Run the following commands to change the FTP transfer mode of the eSAU. # cd /opt/esau # . ./svc_profile.sh # cd /opt/esau/script/utils/ # sh setFTPService.sh The system displays the following information:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + + + Welcome to use eSAU FtpConfig Tools + + + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + + + + + Please choose one module to configurate: 1 -- Open FTP Service 2 -- Close FTP Service 3 -- Update SSL Certificate Q -- Exit
2.
Enable or disable the FTP service. If... Common connection is used for network communication Then Do as follows to enable the FTP service: Type 1. When the system displays Open FTP Service Successful., the FTP service has been enabled successfully.
Issue 01 (2013-07-15)
2391
6 System Management
Then Do as follows to disable the FTP service: Type 2. When the system displays Close FTP Service Successful., the FTP service has been disabled successfully.
NOTE
You can type 3 to update a digital certificate. If the system displays Update SSL Successful., the digital certificate has been updated successfully.
Step 8 Log in to the active xSAU node as user omcuser. 1. Run the following command to switch to user root. ~> su - root Password:Password of root 2. Run the following commands to change the FTP transfer mode of the xSAU: # cd /opt/sau # . ./svc_profile.sh # cd /opt/sau/script/utils/ # sh setFTPService.sh The system displays the following information:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + + + Welcome to use SAU FtpConfig Tools + + + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + + + + + Please choose one module to configurate: 1 -- Open FTP Service 2 -- Close FTP Service 3 -- Update SSL Certificate Q -- Exit
3.
Enable or disable the FTP service. If... Common connection is used for network communication Then Do as follows to enable the FTP service: Type 1. When the system displays Open FTP Service Successful., the FTP service has been enabled successfully.
Issue 01 (2013-07-15)
2392
6 System Management
Then Do as follows to disable the FTP service: Type 2. When the system displays Close FTP Service Successful., the FTP service has been disabled successfully.
NOTE
You can type 3 to update a digital certificate. If the system displays Update SSL Successful., the digital certificate has been updated successfully.
Step 9 Log in to the active Nastar node as user omcuser. Step 10 Run the following command to switch to user root. ~> su - root Password:Password of root Step 11 Do as follows to change the FTP transfer mode of the Nastar: The Nastar is deployed using a different scenario and therefore the operation steps are different. For details, see Table 6-16 through Table 6-17. Table 6-16 Mapping between deployment scenarios and operations steps Deployment Scenario Whether to Switch the FTP Transfer Mode of the Server Whether to Switch the FTP Transfer Mode Between the Client and the Server
Issue 01 (2013-07-15)
2393
6 System Management
Table 6-17 Switching the FTP transfer mode of the Nastar Option Switch the FTP transfer mode of the server FTPFTPS/SFTP FTPS/SFTPFTP
1. Optional: Run the 1. Optional: Run the following commands to following commands to change the FTP transfer change the FTP transfer mode of the Nastar server mode of the Nastar server to FTPS: to FTP: # cd /opt/nastar/bin # cd /opt/nastar/bin # ./ setSSLForFtpSvr.sh disablePlainFtp 2. Optional: Run the following command to manually log in to the FTP server, and check whether the FTP transfer mode has been successfully set on the Nastar server: # ftp IP address of the server When the system displays the following information, type user name root:
Connected to IP address of the server. 220 Authorized users only. All activity may be monitored and reported. Name (IP address of the server :root):
# ./ setSSLForFtpSvr.sh enablePlainFtp 2. Optional: Run the following command to manually log in to the FTP server, and check whether the FTP transfer mode has been successfully set on the Nastar server: # ftp IP address of the server When the system displays the following information, type user name root and the password:
Connected to IP address of the server. 220 Authorized users only. All activity may be monitored and reported. Name (IP address of the server :root):
When the system displays the following information, the FTP transfer mode has been successfully set on the Nastar server:
530 Non-anonymous sessions must use encryption.
When the system displays the following information, the FTP transfer mode has been successfully set on the Nastar server:
230 Login successful.
CAUTION If you need to reinstall the Nastar system, set the FTP transfer mode of the Nastar server to FTP. Otherwise, the reinstallation fails.
Issue 01 (2013-07-15)
2394
6 System Management
Option Switch the FTP transfer mode between the client and the server
NOTE The system automatically restarts the Nastar services after you perform this operation.
FTPFTPS/SFTP 1. Run the following commands to change the FTP transfer mode between the Nastar client and server to SFTP: # cd /opt/nastar # . ./svc_profile.sh # cd /opt/nastar/bin # sh setSFTP.sh enableSFTP 2. When the system displays the following information, the SFTP transfer mode has been successfully set:
Succeed to set SFTP service
FTPS/SFTPFTP 1. Run the following commands to change the FTP transfer mode between the Nastar client and server to FTP: # cd /opt/nastar # . ./svc_profile.sh # cd /opt/nastar/bin # sh setSFTP.sh disableSFTP 2. When the system displays the following information, the FTP transfer mode has been successfully set:
Succeed to set FTP service
Step 12 Log in to the Nastar client and modify the Protocol parameter in the eSAU information area. For detailed operations, choose Product Documentation > Operation and Maintenance > Nastar Quick Start > Configuring OSS and NE Information to see 2.3.3 Configuring eSAU Information.
NOTE
l If the network communication mode is changed from SSL Connection to Common Connection, set Protocol to FTP. l If the network communication mode is changed from Common Connection to SSL Connection, set Protocol to SFTP.
----End
Follow-up Procedure
In the SSL Connection Management window, you can click Refresh to refresh the device list, connection type, and authentication mode. In the SSL Connection Management window, you can also click Test to test the status of the connection between the Nastar server and the eSAU and that between the eSAU and the SAU.
6 System Management
Common Parameters
Parameter Min. length of common user password Description Description: Minimum length of a user account except admin. Setting Value: Value range: 6-16. Default value: 8. Rule: The parameter with a larger value is more secure. To ensure the security and facilitate memory, the recommended value is 8. Min. length of super user password Description: Minimum length of the admin account. Value: Value range: 6-16. Default value: 8. Rule: The parameter with a larger value is more secure. To ensure security and help memorize, the recommended value is 8. Max. password length Description: Maximum length of a user password on the Nastar. Value: Value range: 6-16. Default value: 16. Rule: The parameter with a larger value is more secure. The recommended value is 16. Time between password repetition (month) Description: If the parameter is set to any integer from 1 to 12, the new password set by the user cannot be any history password used in the following time segments: l From the first day of the current month to the date when the new password is set l In the specified number of months before the current month For example, if the password was changed on Feb. 23, 2010 and this parameter is set to 12, the passwords used from Feb, 1, 2010 to Feb. 23, 2010 cannot be used again. Value: Value range: 0-12. Default value: 0. The value 0 indicates that the password is not limited by this security policy. Rule: The parameter with a larger value is more secure. The recommended value is 12.
Issue 01 (2013-07-15)
2396
6 System Management
Description Description: The user is forced to change a password after a specified period. Otherwise, the user cannot log in to the Nastar.
Setting Value: Value range: 1-999. Default value: 180. Rule: This parameter forces a user to change the password periodically. The recommended value is 180, that is, the password is checked every 180 days. If the user selects the Unlimited check box on the right, the Nastar does not force the user to change a password.
Description: Period after which the user can change a password again. If the user selects the Unlimited check box on the right, the user can change a password again immediately after the first change. Otherwise, the user has to change the password after the specified number of days.
NOTE If the user want to change the password in Min. password validity period (days), contact admin to change the password.
Value: Value range: 1-999. Default value: 10. Rule: The parameter with a smaller value is more secure. To prevent users from forgetting passwords due to frequent password changes, the recommended value is 10. If you select the Unlimited check box on the right, you can change a password at any time.
Description: Time when the user is prompted to change a password before the password expires. For example, if the parameter is set to 10, each time when logging in to the client 10 days before the password expires, the user is prompted to change the password.
Value: Value range: 1-30. Default value: 10. Rule: To remind the user to change the password in a timely manner, the recommended value is 30.
Issue 01 (2013-07-15)
2397
6 System Management
Parameter Number of previous passwords that cannot be same with the current password
Description Description: Number of previous passwords that cannot be the same with the current password when the user changes a password.
Setting Value: Value range: 1-24. Default value: 24. Rule: The parameter with a larger value is more secure. To prevent the password from being broken easily, you are recommended to select the Enable check box. The recommended value is 24, that is, the new password cannot be the same with the previous 24 passwords.
NOTE
Advanced Parameters
Parameter Min. different characters between new and old password Description Description: Minimum number of different characters between the new password and the old password when the user changes an old password to a new one. The number of different characters must not exceed the maximum of the value range. For example, assume the old password is abcd1234 and this parameter is set to 3. If the number of different characters between the new and old passwords is larger than 3, the new password can be set successfully. Both the passwords abcd1567 and abcd5678 can take effect. Neither the password abcd1256 nor abcd1235 can take effect. Setting Value: Value range: 3-16. Default value: 3. Rule: To prevent the password from being broken easily, the parameter with a larger value is more secure. The recommended value is 3.
Issue 01 (2013-07-15)
2398
6 System Management
Description Description: Minimum number of letters in a password when the password of the newly created user is set or when a user password is changed. The number of letters must not exceed the maximum of the value range.
Setting Value: Value range: 0-16. Default value: 1. Rule: The parameter with a larger value is more secure. The password should contain at least two letters. In this case, the parameter is set to 2. If you select the Letters are prohibited check box on the right, it indicates that you cannot enter letters.
Min. uppercase
Description: Minimum number of uppercase letters in a password when the password is set for a newly created user or when a user password is changed. The number of uppercase letters must not exceed the maximum of the value range.
Value: Value range: 0-16. Default value: 0. Recommended value: 1 Rule: The parameter with a larger value is more secure. It is recommended that the password contains at least one uppercase letter, that is, the parameter is set to 1. If you select the Uppercase are prohibited check box on the right, it indicates that you cannot enter uppercase letters.
Min. lowercase
Description: Minimum number of lowercase letters in a password when the password is set for a newly created user or when a user password is changed. The number of lowercase letters must not exceed the maximum of the value range.
Value: Value range: 0-16. Default value: 0. Recommended value: 1 Rule: The parameter with a larger value is more secure. It is recommended that the password contains at least one lowercase letter, that is, the parameter is set to 1. If you select the Lowercases are prohibited check box on the right, it indicates that you cannot enter lowercase letters.
Issue 01 (2013-07-15)
2399
6 System Management
Description Description: Minimum number of digits in a password when the password of the newly created user is set or when a user password is changed. The number of digits must not exceed the maximum of the value range.
Setting Value: Value range: 0-16. Default value: 1. Rule: The parameter with a larger value is more secure. It is recommended that the password contains at least one digit, that is, the parameter is set to 1. If you select the Numbers are prohibited check box on the right, it indicates that you cannot enter numbers.
Description: Minimum number of special characters in a password when the password is set for a newly created user or when a user password is changed. The number of special characters must not exceed the maximum of the value range. Such characters as ~!@#$% ^&*()_+-={}[]|\\:\";'?,./` are special characters.
NOTE On the Nastar, the password set by the user cannot contain any spaces. For details, see the parameter The password cannot contain blank.
Value: Value range: 0-16. Default value: 0. Recommended value: 1 Rule: The parameter with a larger value is more secure. It is recommended that the password contains at least one special character, that is, the parameter is set to 1. If you select the Special characters are prohibited check box on the right, it indicates that you cannot enter characters. Value: Default value: Deselect the check box. Rule: You are recommended to select the check box. Setting method: Select or deselect the check box.
Description: A password cannot contain any spaces when the password is set for a newly created user or when a user password is changed.
Issue 01 (2013-07-15)
2400
6 System Management
Description Description: A password cannot be the user name in reverse order when the password is set for the newly created user or when a user password is changed. For example, if the user name is ABC123, the password of this user cannot be 321CBA.
Setting Value: Default value: Deselect the check box. Rule: To prevent the password from being broken easily, you are recommended to select the check box. Setting method: Select or deselect the check box.
Description: A password cannot be set in the following manners when you set the password: l Ascending or descending sequence of numerals and letters. For example, the password cannot be abcdefg, gfedcba, 12345678, or87654321. l Ascending or descending arithmetic sequence of consecutive odd digits or even digits. For example, the password cannot be 1a2a3a4a5a, 7a5a3a1a, a2b2c2d2e2, 2g2e2c2a.
Value: Default value: Deselect the check box. Rule: To prevent the password from being broken easily, you are recommended to select the check box. Setting method: Select or deselect the check box.
Description: Maximum number of same consecutive characters between a user name and a password when the password is set for the newly created user or when a user password is changed. Set the number of consecutive characters in this parameter. For example, if the user name is userA123 and this parameter is set to 3, the password cannot be set to use5678, ser5678, or erA5678.
Value: Value range: l No requirement l Password cannot contain a complete username l Password cannot contain XX consecutive characters in username Default value: No requirement. Rule: To prevent the password from being broken easily, you are recommended to set the parameter to Password cannot contain a complete username.
Issue 01 (2013-07-15)
2401
6 System Management
Setting Value: Default value: Deselect the check box. Rule: To prevent the password from being broken easily, you are recommended to select the check box, and place the information that can be easily guessed out in the password dictionary file. Setting method: 1. Do as follows to set a password dictionary file: 1. Create a password dictionary file in dic format.In Solaris or Linux, the file is present in $/opt/nastar/etc/ conf/pwddic/ on the Nastar server. 2. In the password dictionary file, each row is a dictionary item. 3. When the configuration of the password dictionary is complete, you need to run the following command to load the configuration to the Nastar for the configuration to take effect:updatePwdDic 2. Select or deselect Password cannot contain a whole word in the password dictionary. After the setting, a password cannot contain the contents of the password directory.
Issue 01 (2013-07-15)
2402
6 System Management
Description Description: A password must meet the requirements of the hacker language dictionary when the password is set for the newly created user or when a user password is changed.
NOTE l In the hacker language dictionary file, you can configure a maximum of 104 rules. l The hacker language dictionary defines the rules of converting a character or string into a uppercase or lowercase. For example, if a rule that the string |-|1234 a is converted into x exists in the hacker language dictionary, and if the policy takes effect, a password cannot be set to |-|1234 abcd!. l You are not recommended to modify the hacker language dictionary file. When the configuration of the hacker language dictionary is complete, you need to run the following command to load the configuration to the Nastar and make the configuration take effect:sm_reload hackerpwddic
Setting Value: Default value: Deselect the check box. Rule: To prevent the password from being broken by hackers, you are recommended to select the check box, and update the hacker language dictionary in the Huawei Technologies Co., Ltd. every year. Setting method: 1. Do as follows to set a hacker language dictionary file: 1. In Solaris or Linux, the file is present in $/opt/ nastar/etc/conf/ hackerdic/ on the Nastar server. Open the hackerdic.txt file, and then select the record to be configured in the password directory. For example, select the record |-|1234 a = x. 2. Configure the converted letter of the record in the password dictionary. For example, |-|1234 a is converted into x in the hacker language dictionary. Configure the letter x in the password dictionary. 3. When the configuration is complete, you need to run the following command to load the password dictionary to the Nastar for the configuration to take effect:updatePwdDic 2. Select Password cannot contain a whole word in the password dictionary and Password meets hacker language dictionary requirements.
Issue 01 (2013-07-15)
2403
6 System Management
Description Description: In the The Password Cannot Contain Repeated Strings area, you can set the relationship between the repeated string and the number of repeats in a password when the password is set for the newly created user or when a user password is changed. For example, assume the password to be set is 123abcd123123 and that Number of repetitions and Number of characters in a repeated string are set to 2 and 3 respectively. The password contains the repeated string 123, and this string is repeated for three times. This condition violates the policy. Therefore, the password cannot be used.
NOTE Before setting Number of repetitions and Number of characters in a repeated string, select Enable.
Setting Value: l Enable check box Value range: Select or deselect the check box. Default value: Deselect the check box. Recommended value: Select the check box Rule: To prevent the password from being broken, you are recommended to select the check box. l Number of repetitions Value range: 2-8 Default value: 2 Rule: The parameter with a smaller value is more secure. l Number of characters in a repeated string Value range: 1-8 Default value: 1 Rule: The parameter with a smaller value is more secure.
NOTE
Related Tasks
Setting the Password Policy
Issue 01 (2013-07-15)
2404
6 System Management
Parameters
Parameter Min. length of user name Description Description: Minimum length of the user name. Setting Value: Value range: 1-32. Default value: 6. Rule: The parameter with a larger value is more secure. The recommended value is 8. Auto unlock (minutes) Description: Automatic unlocking time specified for a user account. Value: Value range: 1-1440 Default value: 30. Rule: The parameter with a larger value is more secure. To ensure the security and account recovery capability, the recommended value is 30. If you select Lock permanently on the right side, a locked user account cannot be automatically unlocked.
NOTE Assume that the admin account of the Nastar is locked. If the following conditions are met, you need to log in to the Nastar server to unlock the admin account and then restart Nastar service: l No security administrator account exists on the Nastar. l Lock permanently is selected. In the account policy dialog box, if Do not lock super user is selected, the admin account always cannot be locked.
Description: Wait period before performing the same operation after login or unlocking fails.
NOTE The priority of Permit XX invalid logins before locking user account is higher than that of Delay after login/ unlock failure (seconds). Delay after login/unlock failure (seconds) takes effect only when invalid logins before locking user account in Lock User is larger than three.
Value: Value range: 0-9999. Default value: 3. Rule: To prevent continuous unauthorized login or account unlocking, the parameter with a larger value is more secure. The recommended value is 10.
Issue 01 (2013-07-15)
2405
6 System Management
Description Description: Maximum number of login attempts (the login fails due to incorrect passwords) by using the account registered with the Nastar. When the number of attempts reaches the specified value, the Nastar locks this account automatically. The user of the SMManagers group has the right to unlock the account.
Setting Value: Value range: 1-99. Default value: 3. Rule: The parameter with a smaller value is more secure. A user may enter an incorrect password by mistake. To reduce the workload of manually unlocking accounts for the administrator, the recommended value is3. Value: Value range: Select or deselect the check box. Default value: Deselect the check box. Rule: To ensure security, you are recommended not to select the check box.
Description: When the user does not log in for a specified period of time, the user account is deleted or hibernates.
Value: Value range: l Delete, Suspend l 1-1000 Default value: l Suspend l 60 Rule: To ensure security, the recommended value is Suspend and 60. Unit: day
Automatically locked
Description: When the user does not use the client for a specified period of time, the user account is locked.
Related Tasks
Setting the Account Policy
6 System Management
Common Parameters
Parameter Copy Rights from Users Description Description: Copy rights of users. This operation is inapplicable to the default user of the Nastar. After you click Copy Rights from Users, the Nastar copies the domains and operation rights of the specified users and then loads them for the added users. however, you cannot copy the rights of the user groups that these users belong to. Setting Setting method: 1. Click Copy Rights from Users. 2. In the displayed Copy Rights from Users dialog box, select one or multiple users. 3. Click OK.
Unit: character.
CAUTION You are recommended not to use the information that is easily guessed as the user name, such as frequently word, name, and birthday.
Full name
Description
Value: Value range: 0-100. Unit: character. Value: For details, see Parameters for Setting a Password Policy.
Password
Issue 01 (2013-07-15)
2407
6 System Management
Description Description: The user needs to enter a password again and ensure that the passwords entered twice are the same.
Description: When logging in to the Nastar next time, the user is prompted to change the password. After password change, the user can log in to the Nastar successfully.
Setting method: You are advised to enable this function. When creating a user account: l Select the check box: When logging in to the Nastar next time, the user is prompted to change the password. l Deselect the check box: When logging in to the next time, the user does not need to Nastar change the password.
Setting method: You are advised to not enable this function. When creating a user account: l Select the check box: User cannot modify myself password in the client. l Deselect the check box: User can modify myself password in the client.
Issue 01 (2013-07-15)
2408
6 System Management
Description Description: The user whose account is suspended cannot log in to the Nastar.
Setting Setting method: When creating a user account: l Select the check box: The user cannot log in. l Deselect the check box: The user can log in successfully.
NOTE l Only the users in the security administrator group can use this method to activate non-admin users. l To activate the admin, run svc_enableUser user name in $/opt/nastar/bin of the Nastar server. When the user name contains blank spaces, a pair of double quotation marks is required. For example, svc_enableUser admin svc_enableUser "Mr Li"
Value: You are recommended to set the period to 90 days. When creating a user account: l System password validity period: The value indicates the default validity period of the password of the current account. l Custom: The validity period of the password ranges from 0-999 days. (0 indicates that the password is valid permanently.) The password validity period is in the unit of day.
Advanced Parameters
Click Advanced on the Details tab page to access the Advanced dialog box. The following table describes the parameters in the Advanced dialog box.
Issue 01 (2013-07-15)
2409
6 System Management
Description Description: Maximum number of online users who use the same account.
Setting Setting method: You are recommended to set the value to 1. l Deselect Unlimits, and then set this parameter. The default value is 30. Value range: 0-255. l Select Unlimits. Thus, the same account can be used to log in to the Nastar for unlimited times.
Description: If the user does not perform an operation within the specified period, the user is logged out automatically.
Setting method: You are recommended to set the value to 10 minutes. l Deselect Disable, and then set this parameter. The default value is 10 minutes. Value range: 10-600. l Select Disable.
Issue 01 (2013-07-15)
2410
6 System Management
Setting Setting method: You are recommended to set policy to service suspension if no login within 60 days. When creating a user account: l Select Enable the user policy of no login within a period. By default, the time limit is 60 days. The value ranges from 1 to 1000. The available operations are: Delete, Suspend, and Unlimits. l Deselect Enable the user policy of no login within a period. Thus, the default user policy of no login is used. For an existing user account, next to Inactive user click policy, and then set this parameter in the displayed Inactive user policy dialog box. l Select Enable the user policy of no lo.... By default, the time limit is one day. The value ranges from 1 to 1000. The available operations are: Delete, Suspend, and Unlimits. l Deselect Enable the user policy of no login within a period. Thus, the default security policy is used.
Issue 01 (2013-07-15)
2411
6 System Management
Description Description: Time segment within which the user can log in to the Nastar.
NOTE l If Start date is earlier than End date, Daily end time is displayed as Current day. l If Start date is later than End date, Daily end time is displayed as Next day.
Setting Setting method: You are recommended to set the period to work hours from Monday to Friday. After you change the valid login period, if the current time is not within the period, you can view the information over User Session Monitor. If the user already logs in, use the Force User to Log Out function to force the user to logout. When creating a user account: l Select Enable Period Limit. Time period setting: Start date, End date, Daily start time, Daily end time and Schedule type. Select days of a week. Value range: Monday to Sunday l Deselect Enable Period Limit. The time segment is not limited. The maximum time segment for logging in to the Nastar is from the current time to 23:59:59 on Dec. 31st, 2037. For an existing user account, next to Time segment click for login, and then set this parameter in the displayed Login Duration dialog box. l Select Enable period limit. The time settings include the Start date, End date, Daily start time and Daily end time. The weekdays can be Mon., Tue., Wed., Thu., Fri., Sat. and Sun.. l Deselect Enable period limit. The time segment is not limited. The maximum time segment for logging in to the Nastar is from the current
Issue 01 (2013-07-15)
2412
6 System Management
Parameter
Description
Issue 01 (2013-07-15)
2413
6 System Management
Select
Delete
Description: IP address that the specified user can use to log in.
Setting method: 1. Select the option button. 2. In the ACL, select one or multiple IP addresses. Value: The IP addresses are the same as those in the system ACL.
NOTE To change the ACL used when the user is created, choose Security > System ACL in the main menu and set the ACL in System ACL.
Issue 01 (2013-07-15)
2414
6 System Management
When you change the settings of the ACL, if certain IP addresses are deleted, you can view the information over User Session Monitor. If some users use these IP addresses for login, use the Force User to Log Out function to force the users to logout.
NE Group Name
Query Right
Issue 01 (2013-07-15)
2415
6 System Management
Tab Page
Name NE Type
Setting N/A
NE ID
N/A
NE Name
N/A
Query Right
Description: After the setting, the user has only the permission to query the selected NE.
Setting method: You can click to select the option or press Ctrl+A to select all. Value: No one is selected by default.
Operation Rights
Description: After the setting, the user can query, modify, and delete the rights of the selected NE.
Setting method: You can click to select the option or press Ctrl+A to select all. Value: No one is selected by default. If you select the operation rights, the system selects the query right automatically.
Creator
N/A
Edit Time
N/A
Description
N/A
VIP ID
N/A
Alias
Description: Name of a VIP user, which must be the same as that in VIP group management.
N/A
Issue 01 (2013-07-15)
2416
6 System Management
Tab Page
Description Description: After the setting, the user has only the permission to query the selected VIP user.
Setting Setting method: You can click to select the option or press Ctrl+A to select all. Value: No one is selected by default.
Operation Rights
Description: After the setting, the user can query, modify, and delete the rights of the selected VIP user.
Setting method: You can click to select the option or press Ctrl+A to select all. Value: No one is selected by default. If you select the operation rights, the system selects the query right automatically.
Creator
N/A
Edit Time
N/A
Description
N/A
Description: ID of a VIP group. Description: Name of a VIP group, which must be the same as that in VIP group management. Description: After the setting, the user has only the permission to query the selected VIP group.
N/A
N/A
Query Right
Setting method: You can click to select the option or press Ctrl+A to select all. Value: No one is selected by default.
Issue 01 (2013-07-15)
2417
6 System Management
Tab Page
Description Description: After the setting, the user can query, modify, and delete the rights of the selected VIP group.
Setting Setting method: You can click to select the option or press Ctrl+A to select all. Value: No one is selected by default. If you select the operation rights, the system selects the query right automatically.
Creator
N/A
Edit Time
N/A
Description
N/A
Description: ID of a VIP user. Description: Name of a VIP user, which must be the same as that in VIP group management. Description: After the setting, the user has only the permission to query the auto-distribution user.
N/A
N/A
Query Right
Setting method: You can click to select the option or press Ctrl+A to select all. Value: No one is selected by default.
Issue 01 (2013-07-15)
2418
6 System Management
Tab Page
Description Description: After the setting, the user can query, modify, and delete the rights of the auto-distribution user.
Setting Setting method: You can click to select the option or press Ctrl+A to select all. Value: No one is selected by default. If you select the operation rights, the system selects the query right automatically.
Creator
N/A
Edit Time
N/A
Description
N/A
Related Tasks
Creating an Nastar User Account
Common Parameters
Parameter Copy Rights from User Groups Description Description: Copy rights from a user group. This operation is inapplicable to the default user group of the Nastar. After you click Copy Rights from User Groups, the Nastar copies the domains and operation rights from the specified user group and then loads them to the added user group. Setting Setting method: 1. Click Copy Rights from User Groups. 2. In the displayed Copy Rights from User Groups dialog box, select a user group. 3. Click OK.
Issue 01 (2013-07-15)
2419
6 System Management
Maximum Sessions
Description: Number of user sessions in the current user group. During a specific period, the number of login times of users in this user group can be restricted by using this parameter.
Members
Setting method: l Adding a user Click Add, and select the users to be added. l Removing a user Select the users to be deleted and click Delete.
Issue 01 (2013-07-15)
2420
6 System Management
Parameter Find
Setting -
Select
Setting method: Click Select. In the displayed Select Domain dialog box, select the domains to be added. Setting method: On the Domain tab, select one or more nodes, and then click Delete to delete the selected nodes.
Delete
Delete
Related Tasks
Creating a Nastar User Group
Issue 01 (2013-07-15)
2421
6 System Management
Parameter Description
Parameter Copy Members from Operation Sets Description Description: Copy the members of any operation set except AllApplicationOperations and AllDeviceOperations to the created operation set. Description: Operation type of the Nastar. Setting Value: Any operation set except AllApplicationOperations and AllDeviceOperations.
Details
Type
Value: Value range: Network Device and Network Management Application Value: Value range: 1-100. Unit: character.
Name
Descripti on
Member s
Select
Setting method: Click Select. In the displayed Select Operation Set Member dialog box, select the operations and operation sets to be added. Setting method: On the Members tab, select one or more operations or operation sets, and then click Delete to delete the selected items.
Delete
Related Tasks
Creating an Operation Set
Parameters for Assigning Operation Rights to Nastar User and User Groups
This topic describes the parameters for assigning operation rights to users and user groups. When assigning operation rights to users and user groups, you can refer to this topic.
Interface Entries
You can access the Select Operation Rights dialog box through one of the following two entries: l When you create a user or user group, click the Operation Rights tab, and then click Select.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2422
Issue 01 (2013-07-15)
6 System Management
In the Security Management navigation tree select the created user or user group. In the area on the right, click the Operation Rights tab, and then click Select.
Parameters
Name Authoriz ation Objects and Operatio ns Authoriz ation Objects Description Description: Object of the operation rights. The object selected in Authorization Objects determines the operation rights displayed in Operations. Setting Setting method: 1. In the navigation tree in Authorization, choose a node. Operations lists the operations of the object synchronously. 2. In the navigation tree in Operations, choose one or more operations and operation sets. 3. Click 4. Click OK. Operatio ns Description: Operation right list. The operation rights displayed in Operations are determined by the object selected in Selected Rights. Selected rights Description: Operation rights to be assigned to the Nastar user/user group. Setting method: Operations lists the operations of the object synchronously. .
Setting method: In the navigation tree in Operations, choose one or more operations and operation sets. Click to move the selected operations and operation sets to Selected Rights.
Related Tasks
Viewing and Modifying Nastar User Group Information Viewing and Modifying the Information About a Nastar User
Issue 01 (2013-07-15)
2423
6 System Management
How to Distinguish User-Defined Operation Sets From Default Operation Sets Symptom
After user-defined operation sets are created by a user, other users cannot distinguish the userdefined operation sets from default operation sets. For example, the Nastar provides three operation sets a, b, and c. After user A creates four operation sets d, e, f, and g, user B cannot distinguish between the default operations sets and the operation sets created by user A.
Possible Causes
No cause is provided.
Fault Diagnosis
The default operation sets are stored in a .csv file after the NMS is installed for the first time. Users can refer to this file to distinguish user-defined operation sets and default operation sets.
Procedure
Step 1 from the main menu, choose Security > Security Management. Step 2 In the Security Management navigation tree, click Operation Set. Step 3 Right-click on the operation set list and choose Save All from the shortcut menu. Step 4 In the displayed Save dialog box, select a folder for the file and click Save. l The file is saved in the specified folder and contains Operation Set Name, Type, and Description. The user can view all operation sets in the current system. l The user can view the information in the Type column to distinguish operation sets of the network management application type from operation sets of the network device type. ----End
Possible Causes
l l Users cannot determine the type of an operation right. The operation right name of a device is similar to the name of the network management application type.
Procedure
Step 1 Export specified operation rights of an operation set to a .csv file and save it to the local computer. For details, see Exporting the Files Containing Operation Set Information.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2424
6 System Management
Step 2 Search for the operation right name in the following two files. The rule for determining the type of an operation right is as follows: l If the operation right name is displayed in the *_Network Device.csv file, the right is of the Network Device type.
NOTE
The default file names are OperationSet_NetWork Device.csv and OperationSet_Network Management Application.csv. You can specify the OperationSet part in the file name.
l If the operation right name is displayed in the *_Network Management Application.csv file, the right is of the Network Management Application type. l If the right name cannot be found in the two files, check the entered name of the operation right. ----End
Symptom
You have installed and then uninstalled the Nastar server software. After you successfully install the Nastar server software again and attempt to create users for the first time, the operation fails when you click OK. The system displays the following information: Operation failed.Please contact the system administrator to ensure that all the services work properly.
Possible Causes
The created user information is still saved in the Nastar database instead of being deleted after you uninstall the Nastar server software. When you create users again after reinstalling the Nastar server software, the system will refresh the existing user information and you will be asked to click OK repeatedly.
Solution
Click OK repeatedly (three times in general) when you create users for the first time until the operation succeeds.
6 System Management
Operators
Neither of the default user groups can be deleted. The rights of Administrators and SMManagers are provided by the Nastar by default, and these rights cannot be modified. In actual application, the default rights of the Operators group can be modified according to the requirements of operation and maintenance personnel. In addition to the default user groups, the Nastar supports customizing user groups as required. The default super user in the Nastar system, that is, user admin, is a member in both the Administrators group and SMManagers group. Super user admin has the highest operation rights in the Nastar system.
WARNING
The user admin and the users which belong to Administrators group or SMManagers group should behave correctly and should not perform harmful operations to the system.
6 System Management
Involves all operation rights related to the NE objects managed by the Nastar. l All Appllication Operations Involves all Nastar application rights except the security application rights. In addition to the two default operation sets, you are recommended to create a maximum of 98 operation sets. This avoids performance problems.
Digital Certificate
The digital certificate that complies with the X.509 standard contains the information about the individual, enterprise, or device and the signed public key. The authoritative and fair third-party organization CA issues digital certificates. The encryption technology based on digital certificates ensures information security during data transmission, integrity during data switching, non-repudiation of transmitted data, and identity determinism of the data switching object. The digital certificate adopts the public key password system to implement encryption and decryption by using a pair of matched keys. Each user has a private key for decryption and signing. The private key cannot be used by other users. Each user also has a public key for encryption and signature authentication. The public key can be used by other users.
Security Assurance
The process of encryption by using the digital certificate is irreversible. Only the private key can be used for decryption .
6 System Management
CA certificate Is used for verifying and identifying users' identities and signing users' certificates to ensure identities of certificate holders and possession of public keys.
Digital Signature
The public key encryption technology is used to sign data legally. On the network, the identity authentication technology replaces autographs and is implemented technically and legally. Digital signature ensures integrity of transmitted data and correctness of sender's identity, thereby avoiding arguments during business.
Certificate Authority
The Certificate Authority (CA) is responsible for issuing and managing digital certificates. In a large-scale application environment, CAs are organized in an architecture that contains upperlevel CAs and lower-level CAs. The top-level CA is also called the root CA. Upper-level CAs are responsible for issuing and managing certificates of lower-level CAs. The bottom-level CA directly issues and manages certificates of end users. CAs mainly perform the following functions: l Issuing certificates The CA receives or checks certificate applications from users (including lower-layer CAs and end users), archives the application information, and judges whether applications are valid. If applications are valid, the CA confirms the types of certificates with users. After new certificates use private key signatures of CA, they are placed on the directory server so that users can query and download them. l Updating certificates The CA periodically updates certificates of all users or receives certificate update requests from users and then updates them. l Querying certificates The CA notifies the directory server to return the query results according to the certificate query requests from users. l Managing revoked certificates The CA manages a certificate revocation list. The CA records revoked certificates in the certificate revocation list and does not use them any more. The user sends a certificate revocation request to the CA. The CA receives the request and revokes the certificate. The CA automatically revokes expired certificates.
Context
l The Nastar server, eSAU, SAU, and CA are located on the same network and can access each other. The Nastar sends data to the eSAU and SAU.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2428
Issue 01 (2013-07-15)
6 System Management
The Nastar server, eSAU, and SAU need to use digital certificates to establish trust relationships between them.
Example
Detailed operations on the Nastar client are as follows: Ste p No . 1 Description Operation Description Remarks
l Generate a certificate application file. For detailed operations, see Generating a Certificate Application File. l Apply for a digital certificate. For detailed operations, see Applying for a Digital Certificate.
l The device certificate, CA certificate, and certificate revocation list (CRL) are also applied when you apply for the digital certificate. l Applying for a device certificate is mandatory. l The CA certificate is obtained from the CA center.
l Import the CA certificate. For detailed operations, see Importing CA Certificates. l Import the CRL. For detailed operations, see Importing the Certificate Revocation List Manually.
l Import the device certificate. For detailed operations, see Importing Device Digital Certificates. l Test the device certificate. For detailed operations, see Testing a Device Digital Certificate. l Activate the device certificate. For detailed operations, see Activating a Device Digital Certificate.
Set the SSL mode. For detailed operations, see 6.3.3 Managing SSL Connection Policies.
You can check whether the connection is successful by view its Status.
Issue 01 (2013-07-15)
2429
6 System Management
Importing the Certificate Revocation List Manually Installing a Device Digital Certificate
Issue 01 (2013-07-15)
2430
6 System Management
Context
l After generating a certificate application file, the device automatically generates a key file in PEM format and saves it. In this case, you do not need to import the key file when importing the device certificate. You can select the Local NM node in the Device navigation tree to generate a certificate application file for the Nastar server. You can also select the eSAU or SAU node in the Device navigation tree to generate a certificate application file for the eSAU or SAU.
Procedure
Step 1 Choose Security > Certificate Authentication Management > Certificate Management from the main menu. Step 2 Select a device in the navigation tree on the left, and select the certificate registration information about the selected device in device registration list on the right. To modify the registration information about the device, click Modify in the Device Certificate Registration window, and set parameters in the displayed Configure Certificate Register Information dialog box. For details about how to set the parameters, see Parameters of the Device Certificate Registration Information. Click OK after modifying the registration information about the device certificate. Step 3 On the Device Certificate Registration tab page, click Create Request File. Step 4 In the navigation tree of the displayed Create Request File dialog box, the device for which , and select a folder on the you apply for a digital certificate is selected by default. Click local host. Then, click OK to save the certificate application file. The status of generating the certificate application file is displayed in the lower part of the Device Certificate Registration window. If the execution is successful, the progress is 100%, and the state is Succeeded. ----End
Prerequisites
A digital certificate application file is generated for the specified device. For details about how to generate an application file, see Generating a Certificate Application File.
Procedure
Step 1 The maintenance personnel send the local digital certificate application file to the CA to apply for a device digital certificate.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2431
6 System Management
l The maintenance personnel usually can save the application file of a device certificate to a storage medium or send the file to the CA through the network. l The CA certificate and CRL are also applied when you apply for the digital certificate. l The format for applying for a digital certificate and the naming conventions are as follows: l Device Digital Certificate: PEM or DER format. The certificate is named XXXX.pem or XXXX.der. l CA Certificate: PEM or DER format. The certificate is named XXXX.pem or XXXX.der. l Certificate Revocation List: DER format. The CRL is named XXX.crl.
Step 2 After obtaining the digital certificate, save it to the Nastar client. ----End
Importing CA Certificates
This section describes how to import CA certificates to devices on the Nastar. CA certificates are required to authenticate each other during data communications between devices.
Context
l l You must import CA certificates into the Nastar, eSAU, and all SAU. You can select the Local NM node in the Device navigation tree to import the CA certificate into the Nastar server. You can also select the eSAU or SAU node in the Device navigation tree to import the CA certificate into the eSAU or SAU.
Procedure
Step 1 Choose Security > Certificate Authentication Management > Certificate Management from the main menu. Step 2 In the Certificate Management window, click the CA Certificate tab, and click Add. Step 3 In the Batch Import CA Certificate dialog box, click Import Certificate. In the Open dialog box, select the digital certificate to be imported, and click Open. In the Batch Import CA Certificate dialog box, the information in Certificate Filename is displayed.
Issue 01 (2013-07-15)
2432
6 System Management
Step 4 In the Batch Import CA Certificate dialog box, select a certificate, and click Next. Step 5 In the navigation tree, select devices, and click OK. The status of importing the CA certificate is displayed in the lower part of the CA Certificate tab page. If the execution is successful, the progress is 100%, and the state is Succeeded.
Issue 01 (2013-07-15)
2433
6 System Management
----End
Prerequisites
The CRL of a device exists on the local host.
Context
l The CA records invalid digital certificates in the CRL. The Nastar obtains the CRL and import it to the devices. If the digital certificates of certain devices are in the CRL, the communication between the device fails. You can select the Local NM node in the Device navigation tree to import the CRL into the Nastar server. You can also select the eSAU or SAU node in the Device navigation tree to import the CRL into the eSAU or SAU.
Procedure
Step 1 Choose Security > Certificate Authentication Management > Certificate Management from the main menu. Step 2 In the Certificate Management window, click the Certificate Revocation List tab.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2434
6 System Management
Step 3 On the Certificate Revocation List tab page, click Add. Step 4 In the Add CRL File dialog box, select the device for which the CRL file is to be imported, the format of the CRL file, and the save path of the CRL file. Step 5 Click OK. Import the existing local CRL to the device manually.
NOTE
The Nastar does not support automatic configuration of CRL information. That is, you cannot configure the CRL information by clicking Config.
----End
Prerequisites
The Nastar maintenance personnel have obtained the digital certificate of a device from the CA and saved the certificate on the local host.
Context
Digital certificates, which are deployed on the Nastar server, are used for the authentication between the Nastar server and the eSAU and that between the eSAU and SAU. You can select the Local NM node in the Device navigation tree to import the device digital certificate into the Nastar server. You can also select the eSAU or SAU node in the Device navigation tree to import the device digital certificate into the eSAU or SAU.
Procedure
Step 1 Choose Security > Certificate Authentication Management > Certificate Management from the main menu. Step 2 In the Certificate Management window, click the Device Certificate tab, and click Add. Step 3 In the Device Certificate Batch Import dialog box, click Import Certificate. In the Select Folder dialog box, select the save path of the device digital certificate that you want to import, and click Select. The Device Certificate Batch Import dialog box displays the device digital certificate in the selected path.
Issue 01 (2013-07-15)
2435
6 System Management
NOTE
Step 4 In the Device Certificate Batch Import dialog box, select a device and the corresponding digital certificate, and set the parameters of the device digital certificate. Click OK. For details about the device digital certificate, see Parameters for Importing Device Certificates in Batches. The status of importing the device digital certificate is displayed in the lower part of the Device Certificate tab page. If the execution is successful, the progress is 100%, and the state is Succeeded.
Issue 01 (2013-07-15)
2436
6 System Management
----End
Prerequisites
A device digital certificate is already imported to a device.
Procedure
Step 1 Choose Security > Certificate Authentication Management > Certificate Management from the main menu. Step 2 In the Certificate Management window, select Device Certificate. Step 3 In the navigation tree on the left, choose a device. The device certificate list on the right displays the information about the selected device. Step 4 Select a device certificate record from the device certificate list. Click Test. The execution state of the tested device certificate is displayed in the lower part of Device Certificate. If the execution is successful, the progress is 100%, and the state is Succeeded. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2437
6 System Management
Prerequisites
A digital certificate is already imported to a device, but the certificate is not activated.
Procedure
Step 1 Choose Security > Certificate Authentication Management > Certificate Management from the main menu. Step 2 In the Certificate Management window, select Device Certificate. Step 3 In the navigation tree on the left, choose a device. The device certificate list on the right displays the information about the selected device. Step 4 Select a device certificate record from the device certificate list. Then click Activate.
NOTE
If Application Type is N/A, you need to specify Application Type in the Select Application Type dialog box to activate the device certificate. After activation, a record of the activated certificate is added to the device certificate list according to the selected application type.
The execution state of the activated device certificate is displayed in the lower part of Device Certificate. If the execution is successful, the progress is 100%, and the state is Succeeded. ----End
Context
l The Nastar automatically checks the CA certificates and device certificates. When certificates are likely to expire, the Nastar displays the message Digital certificate is about to expire. The Certificate validate alarm threshold of the Nastar is 30 days by default, and the alarm reporting period is 6 hours. The parameter value is fixed and cannot be modified. If the validity period of a digital certificate is less than 30 days in the Nastar, the Nastar client displays a message Digital certificate is about to expire every six hours.
NOTE
The message Digital certificate is about to expire is displayed only when you log in to the Nastar client using an administrator account.
You can refer to the following information to update a digital certificate upon its expiry.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2438
6 System Management
NOTE
l If the Connection Type is for the connection between the Nastar and the eSAU, the eSAU and the LTE SAU, and the eSAU and the SAU is SSL Connection, and the digital certificates of the eSAU, LTE SAU, and SAU have expired, you need to set Connection Type to Common Connection. For detailed operations, see 6.3.3 Managing SSL Connection Policies. l If common port listening is disabled for the eSAU, LTE SAU, and SAU, none of the eSAU, LTE SAU, and SAU can detect that the Connection Type values for the connections between the Nastar and the eSAU, the eSAU and the LTE SAU, and the eSAU and the SAU are switched to Common Connection, or update the digital certificates through common connection. To update the digital certificates through common connection, you must enable common port listening for the eSAU, LTE SAU, and SAU. For detailed operations, see How Do I Open and Close the Non-Encrypted Json Port of the eSAU?, How Do I Open and Close the Non-Encrypted Json Port of the LTE SAU?, and How Do I Open and Close the Non-Encrypted Json Port of the SAU. For an ATAE cluster system, see How Do I Open and Close the Non-Encrypted Json Port of the eSAU Server? and How Do I Open and Close the Non-Encrypted Json Port of the SAU.
Prerequisites
l l The eSAU, SAU (RAN SAU, LTE SAU, PS SAU), and Nastar server must support SSL authentication. Digital certificates used for SSL authentication have been configured on the eSAU, SAU (RAN SAU, LTE SAU, PS SAU), and Nastar server. For details about the configuration process, see Basic Authentication Process by Using Digital Certificates.
Context
Data transmission security is ensured only when the SSL communication mode is set on the eSAU, SAU (RAN SAU, LTE SAU, PS SAU), and Nastar server.
Procedure
Step 1 Choose Security > Certificate Authentication Management > SSL Connection Management from the main menu.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2439
6 System Management
Step 2 In the SSL Connection Management window, view Connection Type and Authentication mode in the Device column. Check the network communication mode of the current device based on the description provided in Table 6-19. Table 6-19 Network communication modes Network Communication Mode Common connection mode SSL connection mode Connection Type Common SSL Authentication mode Bidirectional authentication
Step 3 In the SSL Connection Management window, select or deselect an eSAU or SAU and click Modify. In the displayed Modify SSL Connection Policy dialog box, set Connection Type and Authentication mode based on the actual network plan. For detailed parameter settings, choose Product Documentation > Operation and Maintenance > System Management > Managing Digital Certificates > Reference of the Certificate Authentication Management GUI to see Parameters for SSL Connection Management. Step 4 Click OK to make the settings take effect.
CAUTION
l After the network communication mode among the eSAU or SAU (RAN SAU, LTE SAU, PS SAU) and the Nastar is changed, the Nastar automatically disconnects the current connection and connects to the eSAU or SAU (RAN SAU, LTE SAU, PS SAU) again based on the new network communication mode. l After the network communication mode is changed, you need to check that the FTP transfer mode matches the network communication mode in the following way: The common connection mode matches the FTP transfer mode and the SSH/SSL connection mode matches the SFTP/FTPS mode. Therefore, you need to manually change the FTP transfer mode. For detailed operations, see Step 5 through Step 12. Step 5 Log in to the active eSAU node as user omcuser. Step 6 Run the following command to switch to user root. ~> su - root Password:Password of root Step 7 Do as follows to change the FTP transfer mode of the eSAU. 1. Run the following commands to change the FTP transfer mode of the eSAU. # cd /opt/esau # . ./svc_profile.sh # cd /opt/esau/script/utils/ # sh setFTPService.sh
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2440
6 System Management
2.
Enable or disable the FTP service. If... Common connection is used for network communication Then Do as follows to enable the FTP service: Type 1. When the system displays Open FTP Service Successful., the FTP service has been enabled successfully. SSL connection is used for network communication Do as follows to disable the FTP service: Type 2. When the system displays Close FTP Service Successful., the FTP service has been disabled successfully.
NOTE
You can type 3 to update a digital certificate. If the system displays Update SSL Successful., the digital certificate has been updated successfully.
Step 8 Log in to the active xSAU node as user omcuser. 1. Run the following command to switch to user root. ~> su - root Password:Password of root 2. Run the following commands to change the FTP transfer mode of the xSAU: # cd /opt/sau # . ./svc_profile.sh # cd /opt/sau/script/utils/ # sh setFTPService.sh The system displays the following information:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + + + Welcome to use SAU FtpConfig Tools + + +
Issue 01 (2013-07-15)
2441
6 System Management
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + + + + + Please choose one module to configurate: 1 -- Open FTP Service 2 -- Close FTP Service 3 -- Update SSL Certificate Q -- Exit
3.
Enable or disable the FTP service. If... Common connection is used for network communication Then Do as follows to enable the FTP service: Type 1. When the system displays Open FTP Service Successful., the FTP service has been enabled successfully. SSL connection is used for network communication Do as follows to disable the FTP service: Type 2. When the system displays Close FTP Service Successful., the FTP service has been disabled successfully.
NOTE
You can type 3 to update a digital certificate. If the system displays Update SSL Successful., the digital certificate has been updated successfully.
Step 9 Log in to the active Nastar node as user omcuser. Step 10 Run the following command to switch to user root. ~> su - root Password:Password of root Step 11 Do as follows to change the FTP transfer mode of the Nastar: The Nastar is deployed using a different scenario and therefore the operation steps are different. For details, see Table 6-20 through Table 6-21. Table 6-20 Mapping between deployment scenarios and operations steps Deployment Scenario Whether to Switch the FTP Transfer Mode of the Server Whether to Switch the FTP Transfer Mode Between the Client and the Server
Issue 01 (2013-07-15)
2442
6 System Management
Table 6-21 Switching the FTP transfer mode of the Nastar Option Switch the FTP transfer mode of the server FTPFTPS/SFTP FTPS/SFTPFTP
1. Optional: Run the 1. Optional: Run the following commands to following commands to change the FTP transfer change the FTP transfer mode of the Nastar server mode of the Nastar server to FTPS: to FTP: # cd /opt/nastar/bin # cd /opt/nastar/bin # ./ setSSLForFtpSvr.sh disablePlainFtp 2. Optional: Run the following command to manually log in to the FTP server, and check whether the FTP transfer mode has been successfully set on the Nastar server: # ftp IP address of the server When the system displays the following information, type user name root:
Connected to IP address of the server. 220 Authorized users only. All activity may be monitored and reported. Name (IP address of the server :root):
# ./ setSSLForFtpSvr.sh enablePlainFtp 2. Optional: Run the following command to manually log in to the FTP server, and check whether the FTP transfer mode has been successfully set on the Nastar server: # ftp IP address of the server When the system displays the following information, type user name root and the password:
Connected to IP address of the server. 220 Authorized users only. All activity may be monitored and reported. Name (IP address of the server :root):
When the system displays the following information, the FTP transfer mode has been successfully set on the Nastar server:
530 Non-anonymous sessions must use encryption.
When the system displays the following information, the FTP transfer mode has been successfully set on the Nastar server:
230 Login successful.
CAUTION If you need to reinstall the Nastar system, set the FTP transfer mode of the Nastar server to FTP. Otherwise, the reinstallation fails.
Issue 01 (2013-07-15)
2443
6 System Management
Option Switch the FTP transfer mode between the client and the server
NOTE The system automatically restarts the Nastar services after you perform this operation.
FTPFTPS/SFTP 1. Run the following commands to change the FTP transfer mode between the Nastar client and server to SFTP: # cd /opt/nastar # . ./svc_profile.sh # cd /opt/nastar/bin # sh setSFTP.sh enableSFTP 2. When the system displays the following information, the SFTP transfer mode has been successfully set:
Succeed to set SFTP service
FTPS/SFTPFTP 1. Run the following commands to change the FTP transfer mode between the Nastar client and server to FTP: # cd /opt/nastar # . ./svc_profile.sh # cd /opt/nastar/bin # sh setSFTP.sh disableSFTP 2. When the system displays the following information, the FTP transfer mode has been successfully set:
Succeed to set FTP service
Step 12 Log in to the Nastar client and modify the Protocol parameter in the eSAU information area. For detailed operations, choose Product Documentation > Operation and Maintenance > Nastar Quick Start > Configuring OSS and NE Information to see 2.3.3 Configuring eSAU Information.
NOTE
l If the network communication mode is changed from SSL Connection to Common Connection, set Protocol to FTP. l If the network communication mode is changed from Common Connection to SSL Connection, set Protocol to SFTP.
----End
Follow-up Procedure
In the SSL Connection Management window, you can click Refresh to refresh the device list, connection type, and authentication mode. In the SSL Connection Management window, you can also click Test to test the status of the connection between the Nastar server and the eSAU and that between the eSAU and the SAU.
6 System Management
Interface Entries
l l On the Device Certificate Register tab, choose Security > Certificate Authentication Management > Certificate Management from the main menu. In the Config Certificate Register Information dialog box, do as follows: 1. Choose Security > Certificate Authentication Management > Certificate Management from the main menu. By default, the Certificate Management window displays the Device Certificate Register tab. 2. In the navigation tree on the left, choose a device. The area on the right displays the certification registration information about the device. 3. Select the device certificate registration information in the right area, and then click Modify.
Parameters
Table 6-22 Certificate Subject Information Parameter Common Name Description Description: Mode of displaying the common name of a certificate. Additional Information Description: Additional information about a digital certificate.
NOTE The parameter is not displayed on the Device Certificate Register tab. The parameter is displayed in the Config Certificate Register Information dialog box only.
Settings Value: Value: Device ESN, Device MAC Address, Device IP Address, or None of above. Value: The value contains 1-32 digits, letters, and special characters.
Country
Value: Value: A string of 2 letters. Standard abbreviation of a country name. Value: The value contains 1-128 digits, letters, and special characters. Value: The value contains 1-64 digits, letters, and special characters.
State
Organization
Issue 01 (2013-07-15)
2445
6 System Management
Parameter Unit
Settings Value: The value contains 1-64 digits, letters, and special characters. Value: The value contains 1-128 digits, letters, and special characters.
Locality
NOTE
The parameters Country, State, Organization, Unit, and Location are set usually when a device is moved to another location, an owner is changed, or a device is set initially.
Table 6-23 Subject alternative name Parameter Device IP address Description Description: IP address of the NE that applies for the certificate. This parameter is used when the Internet Key Exchange (IKE) protocol is used for switching keys. Local NM does not support IKE. Therefore, the parameter can be left blank. Device domain name Description: Host name of the NE that applies for the certificate. This parameter is used when IKE is used for switching keys.
NOTE Local NM does not support IKE. Therefore, the parameter can be left blank.
Settings Value: The format of IP address is XXX.XXX.XXX.XXX. XXX ranges from 0 to 255.
Value: The value contains 1-128 digits, letters, and special characters.
Table 6-24 Key Information Parameter Key Pair Description Description: Consisting of a public key and private key. The purpose is to encrypt and decrypt the data. Settings Value: Value: Use Existing Key Pair or Generate New Pair.
NOTE You can set Key Size only after selecting Generate New Pair.
Issue 01 (2013-07-15)
2446
6 System Management
Description Description: To encrypt data by selecting the key length or key combination.
Settings Value: Value: 1024 Bits, 2048 Bits. Value: Value: Digital Signature, Key Encipherment, Data Encipherment, and Key Agreement. Value: Value: SHA1 or MD5.
Key Usage
Signature Algorithm
Description: Signing by using a key. The purpose is to authenticate the common key arithmetic of a digital certificate.
NOTE
The product feature you have purchased may use personal information of users when providing services or maintenance. Therefore, 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.
Interface Entries
Choose Security > Certificate Authentication Management > Certificate Management from the main menu. In the Certificate Management window, click the Device Certificate tab.
Issue 01 (2013-07-15)
2447
6 System Management
Parameters
Parameter Application Type Description Description: Application type of the device certificate based on protocol, including SSL, IKE, and ALL. The default value is SSL.
NOTE l SSL: The certificate is used for identity authentication during communication between the eSAU, SAU, and the Nastar. l IKE: The certificate is used for identity authentication during communication between the NE and the remote device such as NE or security gateway. l ALL: The device certificate is applicable to all application types, including SSL and IKE. l N/A: The application type of the device certificate is not specified.
Certificate Filename
Serial Number
Common Name
Description: Name of a certificate that the certificate user specifies when applying for the certificate.
Issuer
Validate Date
Description: Expiration date of a device certificate. When the expiration date is reached, the device certificate becomes invalid.
Status
Description: Running status of a task, including default, active, inactive, and N/A.
NOTE l Default: Initial state of the certificate. l N/A: If the Application Type of the device certification is N/A, its status is N/A.
Issue 01 (2013-07-15)
2448
6 System Management
Interface Entries
1. 2. Choose Security > Certificate Authentication Management > Certificate Management from the main menu. Click the Device Certificate tab, and click Add.
Parameter description
Table 6-25 Parameters in the device certificate list Parameter Device Name Description Description: Name of the device that a certificate is imported to. Certificate Filename Description: Certificate to be imported to a device. Application Type Description: The value SSL is by default. Key Filename Description: Name of the key file of digital certificates when you import digital certificates in batches.
NOTE Key Filename must be Certificate Filename+"_key"; otherwise, the import might fail. For example, if Certificate Filename is abc.cer, then its Key Filename is abc_key.pem.
Key Password
Description: Password of the key file of digital certificates when you import digital certificates in batches.
NOTE When configuring digital certificates for devices, you need to enter the key password when importing a single certificate and a key file.
Setting method: Double-click the Key Password cell and enter the key password.
Table 6-26 Other parameters Parameter Attempt to connect to NE with the certificate Description Description: To test whether a certificate is correctly used on a device. Settings Value: Select the check box to activate the test.
Issue 01 (2013-07-15)
2449
6 System Management
Description Description: To select all the digital certificates of the same application type from the device digital certificate list.
Settings Setting method: Select an application type from the drop-down list. Value: The values can be ALL, IKE, and SSL. The default value is SSL. Setting method: This parameter can not be set currently.
Description: After you click OK in the Batch Import Device Certificate dialog box, the Nastar immediately validates the functions managed by certificates.
Interface Entries
1. 2. Choose Security > Certificate Authentication Management > Certificate Management from the main menu. In the Certificate Management window, click the CA Certificate tab.
Parameters
Parameter Certificate Filename Description Description: Name of the certificate file to be imported to a device. Serial Number Description: Unique ID of a certificate. Common Name Description: Name of a certificate that the certificate user specifies when applying for the certificate. Issuer Description: Name of a CA. Validate Date Description: Expiration date of a device certificate. When the expiration date is reached, the device certificate becomes invalid.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2450
6 System Management
Interface Entries
Choose Security > Certificate Authentication Management > SSL Connection Management from the main menu. In the SSL Connection Management window, select or clear an eSAU or SAU, and click Modify. The Modify ssl connection policy dialog box is displayed.
Button Description
Button Modify Refresh Test Description To modify the SSL connection setting of a selected device. To query the SSL connection status of a selected device. To test the status of the SSL connection between the Nastar server and the device.
Parameter Description
Table 6-27 SSL connection management Parameter Device Description Description: Name of the device that is connected to the Nastar in SSL mode. Value: -
Issue 01 (2013-07-15)
2451
6 System Management
Description Description: Type of a connection between the Nastar and a device. Value: Value range: Common Connection, SSL Connection l Common Connection: Security authentication is not performed between the Nastar and the device. l SSL Connection: Security authentication is performed between the Nastar and the device. A secure connection can be established after security authentication is passed, thereby ensuring communication security and integrity.
NOTE When the Nastar fails to query the device status, unknown connection is displayed.
Authentication Mode
Description: Authentication mode for setting up a connection between the Nastar and the device. Value: Value range: Bidirectional Authentication Bidirectional Authentication: The device and Nastar authenticate each other.
NOTE When the Nastar fails to query the device's authentication mode, unknown authentication is displayed.
Connection Status
Description: State of the current connection. Value: Value range: Normal, Unreachable, Unknown l Normal: Indicates that the Nastar is connected to the device properly. l Unreachable: Indicates that the Nastar is disconnected from the device. l Unknown: Indicates that the state of the connection between the Nastar and the device is unknown.
Issue 01 (2013-07-15)
2452
6 System Management
Table 6-28 Modification of SSL connection policies Parameter Connection Type Description Description: Type of a connection between the Nastar and a device. Setting Setting method: Select a value from the dropdown list. According to the network plan, the type must be consistent with that on the device. Value: Value range: Common Connection, SSL Connection l Common Connection: Security authentication is not performed between the Nastar and the device. l SSL Connection: Security authentication is performed between the Nastar and the device. A secure connection can be established after security authentication is passed, thereby ensuring communication security and integrity. Authentication Mode Description: Authentication mode for setting up an SSL connection between the Nastar and the device. Setting method: Select a value from the dropdown list. According to the network plan, the type must be consistent with that on the device. Value: Value range: Bidirectional Authentication Bidirectional Authentication: The device and Nastar authenticate each other.
6 System Management
Log Types
The Nastar has operation logs, system logs, security logs. The three types of logs record different log information.
Description
The operation log records the operations that are performed on the Nastar client but do not affect the Nastar security, such as creating NEs, creating views, acknowledging alarms, and clearing alarms.
Path
Operation logs are stored in the database. You can query them through the client. The entry for querying operation logs through the client is Security > Log Management > Query Operation Logs. You can dump operation logs from the database to a file. The entry for dumping operation logs is Maintance > Task Management.In the Task Type navigation tree,choose Database Capacity Management > Operation Log Dump, The default dump paths are /opt/nastar/var/ ThresholdExport/Log. After the operation logs are dumped, the Nastar generates the associated folder and log file: l l Folder: In the dump path, the Nastar generates a folder named the date of the dump operation. The format of the name is YYMMDD. Log file: The following two files are generated in the folder: YYMMDDHHMMSSoperation-log-dateThreshold_info.xml and YYMMDDHHMMSS-operation-logdateThreshold-number.extension. The file with the suffix _info.xml saves the configuration information of the dumped logs, and the file with the suffix number.extension saved the information about the dumped logs.
NOTE
Operation logs can be dumped to a .csv, .xml, .txt, or .html file, and the file can be compressed to a .zip package.
Issue 01 (2013-07-15)
2454
6 System Management
Parameters
Parameter Name Parameter Meaning Operation Name Risk Level Name of an operation that the user performs on the Nastar. Levels of risks caused by the operations that are performed on the Nastar: Warning, Minor, and Risk. Nastar user. Type of the user who performs an operation. Time when an operation starts. It is accurate to second. Time when an operation ends. It is accurate to second.
Operation Category Type of an operation. Operation Terminal IP address of the host where an operation is performed. Operation Object Operation Result Object that an operation is performed on. Result of an operation: successful, failed, partially successful, ongoing and canceled. Other useful information about an operation.
Details
Description
The system log records the tasks that are performed on the Nastar server and affect the running of the Nastar. These tasks are triggered on the Nastar client, such as starting and executing scheduled tasks, or triggered on the Nastar server, such as starting and stopping the Nastar service.
Path
System logs are stored in the database. You can query them through the client. The entry for querying system logs through the client is Security > Log Management > Query System Logs. You can dump system logs from the database to a file. The entry for dumping system logs is Maintance > Task Management.In the Task Type navigation tree,choose Database Capacity
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2455
6 System Management
Management > System Log Dump The default dump paths are /opt/nastar/var/ ThresholdExport/Log. After the system logs are dumped, the Nastar generates the associated folder and log file: l l Folder: In the dump path, the Nastar generates a folder named the date of the dump operation. The format of the name is YYMMDD. Log file: The following two files are generated in the folder: YYMMDDHHMMSS-systemlog-dateThreshold_info.xml and YYMMDDHHMMSS-system-log-dateThresholdnumber.extension. The file with the suffix _info.xml saves the configuration information of the dumped logs, and the file with the suffix -number.extension saves the information about the dumped logs.
NOTE
System logs can be dumped to a .csv, .xml, .txt, or .html file, and the file can be compressed to a .zip package.
Parameters
Parameter Name Parameter Meaning Level Levels of risks caused by the operations performed on the Nastar: Warning, Minor, and Risk. Module where the Nastar performs an operation. Time when an operation is performed. It is accurate to second.
Source Time
Basic Information Basic operation information. Operation Result Details Result of an operation: successful, failed or unknown. Other useful information about an operation.
Description
The security log records the operations that are performed on the Nastar client and affect the Nastar security, such as granting rights and canceling rights, and logging in to and logging out of the Nastar server.
Issue 01 (2013-07-15)
2456
6 System Management
Path
Security logs are stored in the database. You can query them through the client. The entry for querying security logs through the client is Security > Log Management > Query Security Logs. You can also dump security logs from the database to a file. The entry for dumping security logs is Maintance > Task Management.In the Task Type navigation tree,choose Database Capacity Management > Security Log Dump, The default dump paths are /opt/nastar/var/ ThresholdExport/Log. After the security logs are dumped, the Nastar generates the associated folder and log file: l l Folder: In the dump path, the Nastar generates a folder named the date of the dump operation. The format of the name is YYMMDD. Log file: The following two files are generated in the folder: YYMMDDHHMMSSsecurity-log-dateThreshold_info.xml and YYMMDDHHMMSS-security-logdateThreshold-number.extension. The file with the suffix _info.xml saves the configuration information of the dumped logs, and the file with the suffix number.extension saves the information about the dumped logs.
NOTE
Security logs can be dumped to a .csv, .xml, .txt, or .html file, and the file can be compressed to a .zip package.
Parameters
Parameter Name Parameter Meaning Security Event Risk Level Event that is related to Nastar security. Levels of risks caused by the operations that are performed on the Nastar: Warning, Minor, and Risk. Nastar user. Type of the Nastar user. Time when an operation is performed. It is accurate to second.
Operation Terminal IP address of the host where an operation is performed. Operation Object Operation Result Details Object that an operation is performed on. Result of an operation: successful, failed or partially successful. Other useful information about an operation.
6 System Management
Log Meaning
A Nastar trace log records information about the running process of the Nastar client, Nastar server, and eSAU, and the information storage process. The downloaded log file consists of two compressed files. l l Nastar_Client_Trace_FileYYYYMMDDhhmmss.zip contains the trace log of the Nastar client. Nastar_Server_Trace_FileYYYYMMDDhhmmss.zip contains the run logs of storage processes and the trace logs of the Nastar server and eSAU.
Log Type
Log Type Nastar client log File Name/Format Nastar_ Client_Trace_FileY YYYMMDDhhmms s.zip Log Checking If the log contains error, Error, failed, or Exception, contact Huawei technical support. Description It is the tracing information about the Nastar client. YYYYMMDDhhmms s indicates the time when the task for downloading logs is started. Decompress the ZIP file. Only the tracefile file is available. Nastar server log Galaxy_YYYYMM DDhhmmssXXX.log or Galaxy_YYYYMM DDhhmmssXXX.zip If the log contains error, Error, failed, or Exception, contact Huawei technical support. It is a Nastar server log. YYYYMMDDhhmms sXXX indicates the time when the log is downloaded. XXX indicates millisecond. If a log file of the Nastar server reaches 1 GB, the system automatically compresses the file into a ZIP file. Therefore, more than one file is named Galaxy_YYYYMM DDhhmmssXXX.zip . YYYYMMDDhhmms sXXX indicates the time when the log is compressed.
Issue 01 (2013-07-15)
2458
6 System Management
Log Checking If the log contains error, Error, or failed, contact Huawei technical support.
Description It is an eSAU run log. YYYYMMDDhhmms s indicates the time when the log is downloaded. N indicates a random number. It is a run log of a storage process. If the procedureTrace.cs v file is empty, contact Huawei technical support.
procedureTrace.cs v
If abnormal information about the Oracle is displayed in this log, contact Huawei technical support. You can view all logs of a task by task name.
Context
l When you query operation logs by user name, only names of the users that have performed operations are displayed under Available Operation User in the Select Operation User dialog box. The statistical result is generated based on the existing data in the database. If the database is empty, there is no statistical result.
Procedure
Step 1 Choose Security > Log Management > Query Operation Logs from the main menu. Step 2 In the Filter dialog box, set the filtering conditions, and then click OK.
Issue 01 (2013-07-15)
2459
6 System Management
l You can also click Cancel in the Filter dialog box, and then query logs in the Query Operation Logs window in the following ways: l Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to query logs. If no template exists on the Nastar, see 6.4.5 Setting Log Templates to create a template. l Click Filter. Set the query conditions in the Filter dialog box, and then click OK to query logs. l Click Choose at the lower left corner in the Filter dialog box. In the Select Operation Name dialog box, you can view the operations that can be monitored.
Step 3 Right-click in the query window and perform the following operations. Operation Name Details Operation Method Right-click a log in the window and choose Details, or double-click the log.
NOTE The Details dialog box displays the time, risk level, or results of the operation that generates the log.
1. Right-click a log in the window and choose Save All Records. 2. In the Save dialog box, select the path to save records, and then click Save.
NOTE The log records can only be exported as .txt, .html, .csv, .pdf or .xls files. The default file format is .xls file.
1. Select one or more logs in the window, right-click, and then choose Save Selected Records from the shortcut menu. 2. In the Save dialog box, select the path to save records, and then click Save.
NOTE Log records can be saved in .txt, .html, .csv, .pdf, or .xls format. The default file format is .xls.
1. Right-click a log in the window and choose Save Specified Records. 2. In the Save Specified Record dialog box, set the start row and end row of logs and the name of the file to be saved, and then click OK.
NOTE In the Save Specified Records dialog box, click on the right of File name. In the Save dialog box, select the path for saving the records. The log records can only be exported as .txt, .html, .csv, .pdf or .xls files. The default file format is .xls file.
Issue 01 (2013-07-15)
2460
6 System Management
Operation Method 1. Right-click a log in the window and choose Print All Records. 2. In the Print dialog box, set the print parameters, and then click Print.
1. Select one or more logs in the window, right-click, and then choose Print Selected Records from the shortcut menu. 2. In the Print dialog box, set the print parameters, and then click Print.
1. Right-click a log in the window and choose Print Specified Records. 2. In the Print Specified Records dialog box, set the start row and end row, and then click OK. 3. In the Print dialog box, set the print parameters, and then click Print.
----End
Related Tasks
6.4.5 Setting Log Templates
Related References
Parameters for Querying Operation Logs Parameters for Querying Operation Logs
Context
The statistical result is generated based on the existing data in the database. If the database is empty, there is no statistical result.
Procedure
Step 1 Choose Security > Log Management > Operation Log Statistics from the main menu. Step 2 In the Filter window, set the statistical items and statistical conditions, and then click OK.
Issue 01 (2013-07-15)
2461
6 System Management
You can also click Cancel, and then collect statistics in the Operation Log Statistics window in the following ways: l Click Template, and then select Open. Select a template from the template list, and then click Open to use an existing template to collect statistics on operation logs. If no template exists on the Nastar, see 6.4.5 Setting Log Templates to create a template. l Click Filter. Set Statistical Items and Filter Condition in the Filter window, and then click OK to collect statistics on operation logs.
----End
Result
In the Operation Log Statistics window, the statistical result is displayed. Perform the following operations as required: l l Click Print to print the statistical result. Click Save As to save the statistical result.
Related Tasks
6.4.5 Setting Log Templates
Related References
Parameters for Collecting Statistics on Operation Logs Parameters for Querying System Logs Parameters for Collecting Statistics on Operation Logs
Context
The statistical result is generated based on the existing data in the database. If the database is empty, there is no statistical result.
Procedure
Step 1 Choose Security > Log Management > Query System Logs from the main menu. Step 2 In the Filter dialog box, set the filtering conditions, and then click OK.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2462
6 System Management
You can also click Cancel in the Filter dialog box, and then query logs in the Query System Logs window in the following ways: l Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to query logs. If no template exists on the Nastar, see 6.4.5 Setting Log Templates to create a template. l Click Filter. Set the query conditions in the Filter dialog box, and then click OK to query logs.
Step 3 Right-click in the query window and perform the following operations. Operation Name Details Operation Method Right-click a log in the window and choose Details, or double-click the log.
NOTE The Details dialog box displays the time, risk level, or results of the operation that generates the log.
1. Right-click a log in the window and choose Save All Records. 2. In the Save dialog box, select the path to save records, and then click Save.
NOTE The log records can only be exported as .txt, .html, .csv, .pdf or .xls files. The default file format is .xls file.
1. Select one or more logs in the window, right-click, and then choose Save Selected Records from the shortcut menu. 2. In the Save dialog box, select the path to save records, and then click Save.
NOTE Log records can be saved in .txt, .html, .csv, .pdf, or .xls format. The default file format is .xls.
1. Right-click a log in the window and choose Save Specified Records. 2. In the Save Specified Record dialog box, set the start row and end row of logs and the name of the file to be saved, and then click OK.
NOTE In the Save Specified Records dialog box, click on the right of File name. In the Save dialog box, select the path for saving the records. The log records can only be exported as .txt, .html, .csv, .pdf or .xls files. The default file format is .xls file.
1. Right-click a log in the window and choose Print All Records. 2. In the Print dialog box, set the print parameters, and then click Print.
Issue 01 (2013-07-15)
2463
6 System Management
Operation Method 1. Select one or more logs in the window, right-click, and then choose Print Selected Records from the shortcut menu. 2. In the Print dialog box, set the print parameters, and then click Print.
1. Right-click a log in the window and choose Print Specified Records. 2. In the Print Specified Records dialog box, set the start row and end row, and then click OK. 3. In the Print dialog box, set the print parameters, and then click Print.
----End
Related Tasks
6.4.5 Setting Log Templates
Related References
Parameters for Querying System Logs Parameters for Querying System Logs
Context
The statistical result is generated based on the existing data in the database. If the database is empty, there is no statistical result.
Procedure
Step 1 Choose Security > Log Management > System Log Statistics from the main menu. Step 2 In the Filter window, set the statistical condition, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the System Log Statistics window in the following ways: l Click Template, and then select Open. Select a template from the template list, and then click Open to use an existing template to collect statistics on system logs. If no template exists on the Nastar, see 6.4.5 Setting Log Templates to create a template. l Click Filter. Set the statistical condition in the Filter window, and then click OK to collect statistics on system logs.
----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2464
6 System Management
Result
In the System Log Statistics window, the statistical result is displayed. Perform the following operations as required: l l Click Print to print the statistical result. Click Save As to save the statistical result.
Related Tasks
6.4.5 Setting Log Templates
Related References
Parameters for Collecting Statistics on System Logs Parameters for Collecting Statistics on System Logs
Context
The statistical result is generated based on the existing data in the database. If the database is empty, there is no statistical result.
Procedure
Step 1 Choose Security > Log Management > Query Security Logs from the main menu. Step 2 In the Filter dialog box, set the filtering conditions, and then click OK.
NOTE
l You can also click Cancel in the Filter dialog box, and then query logs in the Query Security Logs window in the following ways: l Click Template Filter, and then select Open. Select a template from the template list, and then click Open to use an existing template to query logs. If no template exists on the Nastar, see 6.4.5 Setting Log Templates to create a template. l Click Filter. Set the query conditions in the Filter dialog box, and then click OK to query logs. l Click Choose at the lower left corner in the Filter dialog box. In the Select Security Event dialog box, you can view the operations that can be monitored (The Log out the server operation is not monitored.).
NOTE
Step 3 Right-click in the query window and perform the following operations.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2465
6 System Management
Operation Method Right-click a log in the window and choose Details, or double-click the log.
NOTE The Details dialog box displays the time, risk level, or results of the operation that generates the log.
1. Right-click a log in the window and choose Save All Records. 2. In the Save dialog box, select the path to save records, and then click Save.
NOTE The log records can only be exported as .txt, .html, .csv, .pdf or .xls files. The default file format is .xls file.
1. Select one or more logs in the window, right-click, and then choose Save Selected Records from the shortcut menu. 2. In the Save dialog box, select the path to save records, and then click Save.
NOTE Log records can be saved in .txt, .html, .csv, .pdf, or .xls format. The default file format is .xls.
1. Right-click a log in the window and choose Save Specified Records. 2. In the Save Specified Record dialog box, set the start row and end row of logs and the name of the file to be saved, and then click OK.
NOTE In the Save Specified Records dialog box, click on the right of File name. In the Save dialog box, select the path for saving the records. The log records can only be exported as .txt, .html, .csv, .pdf or .xls files. The default file format is .xls file.
1. Right-click a log in the window and choose Print All Records. 2. In the Print dialog box, set the print parameters, and then click Print.
1. Select one or more logs in the window, right-click, and then choose Print Selected Records from the shortcut menu. 2. In the Print dialog box, set the print parameters, and then click Print.
Issue 01 (2013-07-15)
2466
6 System Management
Operation Method 1. Right-click a log in the window and choose Print Specified Records. 2. In the Print Specified Records dialog box, set the start row and end row, and then click OK. 3. In the Print dialog box, set the print parameters, and then click Print.
----End
Related Tasks
6.4.5 Setting Log Templates
Related References
Security Log List Parameters for Querying Security Logs Parameters for Querying Security Logs
Context
The statistical result is generated based on the existing data in the database. If the database is empty, there is no statistical result.
Procedure
Step 1 Choose Security > Log Management > Security Log Statistics from the main menu. Step 2 In the Filter window, set the statistical items and filtering conditions, and then click OK.
NOTE
You can also click Cancel, and then collect statistics in the Security Log Statistics window in the following ways: l Click Template, and then select Open. Select a template from the template list, and then click Open to use an existing template to collect statistics on security logs. If no template exists on the Nastar, see 6.4.5 Setting Log Templates to create a template. l Click Filter. Set Items and Filter Condition in the Filter window, and then click OK to collect statistics on security logs.
----End
Result
In the Security Log Statistics window, the statistical result is displayed.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2467
6 System Management
Perform the following operations as required: l l Click Print to print the statistical result. Click Save As to save the statistical result.
Related Tasks
6.4.5 Setting Log Templates
Related References
Parameters for Collecting Statistics on System Logs Parameters for Collecting Statistics on System Logs
Context
The operations for setting the log query and statistic collection templates are similar. The following is an example of setting the log query template.
Procedure
Step 1 Choose Security > Log Management from the main menu. Step 2 Among the displayed menus, you can choose Query Operation Logs, Query System Logs, Query Security Logs, Operation Log Statistics, System Log Statistics and Security Log Statistics. The following takes the template for querying and collecting statistics on operation logs as an example. Task Create a template Operation 1. Choose Security > Log Management > Query Operation Logs. 2. In the Filter dialog box, click Cancel. 3. In the Query Operation Logs window, choose Template Filter > New. 4. In the Enter Template Name dialog box, enter the template name, and then click OK. 5. In the Filter dialog box, set the filtering conditions of template parameters, and then click OK.
Issue 01 (2013-07-15)
2468
6 System Management
Operation If there is already a log query template or a log statistics template on the Nastar, you can do as follows to modify the template: 1. In the Query Operation Logs window, choose Template Filter > Open. Select a template in the Open dialog box, and then click Open. 2. In the Query Operation Logs window, click Filter. 3. In the Filter dialog box, modify the query conditions in the log template, and then click OK. 4. In the Query Operation Logs window, choose Template Filter > Save.
Save As
You can do as follows to save and modify a log query or statistics template: 1. In the Query Operation Logs window, choose Template Filter > Save As. 2. In the Enter Template Name dialog box, enter the template name, and then click OK.
Delete a template
If there is already a log query template or a log statistics template on the Nastar, you can do as follows to delete the template: Delete the operations in the template. 1. In the Query Operation Logs window, choose Template Filter > Delete. 2. In the displayed Delete dialog box, select the specified template. 3. Click Delete. 4. In the Confirm dialog box, click Yes.
----End
Related Tasks
Querying the Nastar Operation Logs Collecting Statistics on the Nastar Operation Logs Querying the Nastar System Logs Collecting Statistics on the Nastar System Logs Querying the Nastar Security Logs Collecting Statistics on the Nastar Security Logs
Context
The log forwarding server forwards only security logs, operation logs, and system logs.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2469
6 System Management
Procedure
Step 1 Choose System > Transmit Log from the main menu. Step 2 You can perform the following operations in the Log Forwarding Server window. Task Add Operation In the Create Log Forwarding Server dialog box, set the server that receives the logs. See Parameters for Setting a Log Forwarding Server.
NOTE l To enable the log forwarding function, select Yes from the Enable drop-down list. l The IP address cannot be set to a loopback address. l String Filter does not support wildcards. l The switchover between the primary and secondary servers is supported when the value of Protocol is TCP. When the primary server fails, the secondary server takes over the service and receives the logs. When the primary server is recovered, the service is switched back to the primary server. l You can set a maximum of five servers to receive logs.
Modify
In the Log Forwarding Servers dialog box, select a server record, and then click Modify. In the displayed Modify Log Forwarding Server dialog box, set the server information of logs. In the Log Forwarding Servers dialog box, select a server record, and then click Delete. After another user updates the information about the log forwarding server, you can click Refresh to obtain the updated information. To exit the Log Forwarding Server dialog box.
Delete
Refresh
Cancel ----End
Context
Each of the types Operation Log Dump, Security Log Dump and System Log Dump has a default system task that is provided by the Nastar. You are not allowed to delete this system task, but you can modify its setting. In addition, you cannot create new tasks of these three types.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2470
6 System Management
Procedure
Step 1 Choose Maintance > Task Management from the main menu. Step 2 In the Task Type navigation tree, expand the Database Capacity Management node, choose Operation Log Dump, Security Log Dump or System Log Dump. Step 3 Double-click the task in the task list.
NOTE
In the task list, right-click the log dump task and choose Run Immediately. The log dump task is performed instantly.
Step 4 In the displayed Attribute dialog box, set the parameters on the Common Parameters and Extended Parameters tabs. For the parameter descriptions, see Parameters for Setting Nastar Log Timing Dump. Step 5 Click OK. ----End
Related References
Parameters for Setting Nastar Log Timing Dump Parameters for Setting Nastar Log Timing Export
Context
Each of the types Operation Log Export, Security Log Export and System Log Export has a default system task that is provided by the Nastar. You are not allowed to delete the system task, but you can modify its setting. In addition, you cannot create new tasks of these three types.
Procedure
Step 1 Choose Maintance > Task Management from the main menu. Step 2 In the Task Type navigation tree, choose File Interface > Operation Log Export,File Interface > Security Log Export or File Interface > System Log Export. Step 3 Double-click the task in the task list.
NOTE
To perform the operations such as executing an export task instantly, suspending an task, and setting timing suspending and resuming, right-click the log export task in the right area and choose the corresponding menus.
Step 4 In the Attribute dialog box, set the parameters on the Common Parameters and Extended Parameters tabs. For the parameter descriptions, see Parameters for Setting Nastar Log Timing Export.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2471
6 System Management
The format of the export files of logs is .csv , .xml , .txt , or .html.
Related References
Parameters for Setting Nastar Log Timing Dump Parameters for Setting Nastar Log Timing Export
Prerequisites
l l You have logged in to the Nastar client as user admin. At least 1 GB disk space is available for storing the downloaded Nastar trace logs.
Context
The Nastar system consists of four subsystems: the Nastar client, Nastar server, eSAU, and SAU. The system generates a run log for each subsystem. These logs record the information about software running processes and help to locate and solve problems. They are saved on different hardware entities and in different paths. Therefore, it will take a long time to obtain the logs one by one. By downloading the Nastar trace logs, you can obtain the trace logs of the Nastar client, Nastar server, and eSAU by one click.
NOTE
Currently, engineers must log in to each SAU to obtain Nastar trace logs.
Procedure
Step 1 Choose System > Nastar Log Download and the Nastar Log Download dialog box is displayed. Step 2 In the Nastar Log Download dialog box, set the record duration and save path for logs. l Record duration: a maximum of three days. l Save path: Ensure that the log is saved to a disk with at least 1 GB free space. Step 3 Click Save. The log will be downloaded in ten minutes. ----End
Follow-up Procedure
Contact Huawei technical support to locate and analyze problems based on the downloaded logs. The downloaded log file consists of two compressed files.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2472
6 System Management
Nastar_Client_Trace_FileYYYYMMDDhhmmss.zip contains the trace log of the Nastar client. YYYYMMDDhhmmss indicates the time when the task for downloading logs is started. Nastar_Server_Trace_FileYYYYMMDDhhmmss.zip contains the run logs of storage processes and the trace logs of the Nastar server and eSAU. YYYYMMDDhhmmss indicates the time when the task for downloading logs is started. Table 6-29 describes the directory for saving Nastar logs. Table 6-29 nastarlog_YYYYMMDDhhmmss directory structure FirstLevel Director y Nastar_ Client_T race_Fil eYYYYM MDDhh mmss. zip SecondLevel Directory tracefile.zip var.zip Third-Level Directory Description Abnormal Information in Logs If the log contains error, Error, failed, or Exception, contact Huawei technical support.
Nastar client running logs. Logs for communication between the Nastar client and Nastar server (saved on the Nastar client). It is a run log recording the storage process. If the procedureTrace.csv file is empty, contact Huawei technical support.
procedureTra ce.csv
View all logs of a task by task name. If abnormal information about the Oracle is displayed in this log, contact Huawei technical support. If the log contains error, Error, or failed, contact Huawei technical support.
It is an eSAU run log. YYYYMMDDhhmmss indicates the time when the log is downloaded. N indicates a random number.
Issue 01 (2013-07-15)
2473
6 System Management
FirstLevel Director y
SecondLevel Directory
Third-Level Directory
Description
Abnormal Information in Logs If the log contains error, Error, failed, or Exception, contact Huawei technical support.
It is a Nastar server log. YYYYMMDDhhmmss XXX indicates the time when the log is downloaded. XXX indicates millisecond. If a log file of the Nastar server reaches 1 GB, the system automatically compresses the file into a ZIP file. Therefore, more than one file is named Galaxy_YYYYMMD DhhmmssXXX.zip. YYYYMMDDhhmmss XXX indicates the time when the log is compressed.
Interface Entries
Choose Security > Log Management > Query Security Logs from the main menu. View security events in the Query Security Logs window.
Issue 01 (2013-07-15)
6 System Management
Description To implement the function of granting rights to the current user in order to operate VIP user groups on the Nastar. To implement the function of granting rights to the current user in order to operate the auto-distribution users on the Nastar. To implement the function of managing users on the Nastar. To implement the function of assigning rights to users on the Nastar. To change the current password. The change takes effect at the next login. To implement the function of managing user groups on the Nastar. To implement the function of assigning rights to user groups on the Nastar. To implement the function of managing NE users on the Nastar. To implement the function of assigning rights to NE users on the Nastar. To force the user to log out of the Nastar if necessary to ensure network security.
CAUTION After forcible logout, the user needs to log in to the Nastar again.
Minor
User Management Grant user access Reset Password User Group Management Grant usergroup access NE User Management Assign NE User Rights Force Users to Exit
Risk Minor
To set the password policy and account policy. To monitor user sessions recorded by the Nastar. Viewing user operations helps the maintenance personnel to ensure that the Nastar runs normally. To unlock the locked user account. To implement the function of managing security rights by category on the Nastar. To change the NE user password. The change takes effect at the next login. To implement the function of managing object e sets on the Nastar.
Unlock Users Security rights management Change NE User Password Object Set Management
Issue 01 (2013-07-15)
2475
6 System Management
Security Event Operation Set Management Query Security Logs Security Log template setting
Description To implement the function of managing operation sets on the Nastar. To query security logs. To customize the template for querying security logs. The maintenance personnel can use this template to conveniently query the same type of security logs. To implement the function of checking rights on the Nastar. To implement the function of checking combined rights on the Nastar. To query the static information about the Nastar. To log in to the Nastar server. To log out of the Nastar server. To view sessions of all online users of the Nastar. To view sessions of Nastar online users except administrators. To view the system mode on the Nastar. To view the session mode on the Nastar. To view the domain information on the Nastar. To view Nastar security objects such as users, user groups, and objects. To implement the function of querying NE users on the Nastar. To implement the function of inheriting rights by security object on the Nastar. To implement the function of querying domains by security object on the Nastar. To implement the function of querying compressed security objects on the Nastar. To implement the function of querying user groups on the Nastar.
Check access Check combined access Query static information Log in to the server Log out the server Get All Login Session Get user login sessions Get system mode Get session mode Get domain information Get security object Query NE user Get access by SO Query domain by SO Query compressed SO
Minor Minor Minor Minor Risk Minor Minor Minor Minor Minor Minor Minor Minor Minor Minor
Get usergroup
Minor
Issue 01 (2013-07-15)
2476
6 System Management
Description To implement the function of querying the information about user groups on the Nastar. To implement the function of querying all users on the Nastar. To inherit rights of the user group. On the Nastar, a user can inherit the rights of the user group that the user belongs to. To implement the function of querying all user information on the Nastar. To implement the function of querying all user group information on the Nastar. To implement the function of querying any users on the Nastar. To implement the function of querying all NE user information on the Nastar. To inherit rights of other users on the Nastar. To obtain a user name by ID on the Nastar. To obtain an ID by user name on the Nastar. To access the Nastar by using an external user account. To change a user password according to the network maintenance requirement. To revert a user password according to the network maintenance requirement. To unlock the locked terminal. To create NE users according to the network maintenance requirement and assign different permissions to the users for the purpose of convenient user management.
Minor Minor
Get account information Get all usergroup Get users Get NE user information Get access by user Get user name by id Get user id by name NB login Change password Revert password Unlock terminal Create NE user
Minor Minor Minor Minor Minor Minor Minor Minor Risk Risk Minor Minor
Issue 01 (2013-07-15)
2477
6 System Management
Description To delete unnecessary NE user accounts for the purpose of network security. Misoperations and damages may be caused when invalid users use the disclosed accounts to log in.
CAUTION After deleting a user account, you cannot use it to log in to an NE unless you have created the same user account again.
Minor
To modify the user group description according to the network maintenance requirement. This helps the maintenance personnel to quickly understand the category that the user group belongs to. To modify the user group name according to the network maintenance requirement. After the modification, users with the same properties are merged into the modified user group. To create a user group. A user group includes users with similar properties. Creating a user group with custom permissions achieves the user management in a centralized manner. To delete unnecessary Nastar user groups to ensure security of the network and Nastar. To assign rights to users and user groups according to the network maintenance requirement. This facilitates network management. To delete rights of users or user groups for Nastar applications and devices. To implement the function of assigning rights to other users through rights paste on the Nastar. To implement the function of querying the right policy on the Nastar. To bind operation sets and object sets to a user. Unbind objects from a user. To bind operation sets and object sets to a user group.
Minor
Minor
Minor
Grant rights
Minor
Minor Minor
Query access policy Bind user Unbind user Bind user group
Issue 01 (2013-07-15)
2478
6 System Management
Description Unbind objects from a user group. To create users according to the network maintenance requirement and assign different permissions to users for the purpose of convenient network management. To delete unnecessary user accounts for the purpose of network security. Misoperations and damages may be caused when invalid users use the disclosed accounts to log in.
CAUTION After deleting a user account, you cannot use it to log in to the Nastar except that you have created the same user account again.
Delete user
Risk
Minor Minor
To implement the function of modifying the user description on the Nastar. To implement the function of changing the user login time segment on the Nastar. To implement the function of modifying accounts on the Nastar. To implement the function of modifying user attributes on the Nastar. To implement the function of modifying the account logout policy (if a user does not perform operations in a long period, the user is logged out automatically) on the Nastar. To implement the function of changing the password expiry date on the Nastar. To allow the user to access the Nastar by using the specified IP addresses or IP address segments. To bind objects and operations to an NE user. To unbind objects and operations from an NE user. To set security policies according to the network maintenance requirement. This ensures that the Nastar runs securely and normally.
Modify account validity Modify user attribute Modify account LogOut Policy
Minor Minor
Issue 01 (2013-07-15)
2479
6 System Management
Security Event Query child domain Change NE user password Change user password valid days Modify user password status Add system ACL
Description To implement the function of querying child domains on the Nastar. To implement the function of changing an NE user password on the Nastar. To implement the function of changing the user password validity period on the Nastar. To implement the function of modifying user password status on the Nastar. To add IP addresses or IP address segments to the system ACL. Users are allowed to access the Nastar by using the specified IP addresses or IP address segments. To change IP addresses or IP address segments in the system ACL. Users are allowed to access the Nastar by using the specified IP addresses or IP address segments. To delete IP addresses or IP address segments from the system ACL. To plan and create a object set. After you assign the object set to a user or user group, the user or user group has the permissions to perform operations on the objects included in the object set. This helps assign and manage Nastar user permissions in a centralized manner. To modify a object set name according to the network maintenance requirement. Objects with the same properties are merged into the modified object set. To modified the object set description according to the network maintenance requirement. Objects with the same properties are merged into the modified object set. To add objects to the specified object set according to the network maintenance requirement. To delete objects from the specified object set according to the network maintenance requirement.
Minor Minor
Risk
Minor Minor
Minor
Minor
Minor
Risk
Issue 01 (2013-07-15)
2480
6 System Management
Security Event Delete object set Bind object set to object set
Description To delete unnecessary object sets in time. To bind a object set to another object set according to the network maintenance requirement. The user does not need to reconfigure properties for object sets with the same properties. To unbind a object set from another object set according to the network maintenance requirement. To create an operation set. After you assign the operation set to a user or user group, the user or user group has the permissions to perform the operations included in the operation set. This helps assign and manage Nastar user permissions in a centralized manner. To modified an operation set name according to the network maintenance requirement. Operations with the same properties are merged into the modified operation set. To modified the operation set description according to the network maintenance requirement. Operations with the same properties are merged into the modified operation set. To add operations to the specified operation set according to the network maintenance requirement. To delete operations from the specified operation set according to the network maintenance requirement. To delete unnecessary operation sets in time. To bind an operation set to another operation set according to the network maintenance requirement. The user does not need to reconfigure properties for operation sets with the same properties. To unbind an operation set from another operation set according to the network maintenance requirement.
Minor
Minor
Minor
Minor
Minor
Risk
Risk Minor
Minor
Issue 01 (2013-07-15)
2481
6 System Management
Security Event Add subresource access to user group Delete subresource access from user group Add subresource access to user Delete subresource access from user Security User Management Security User Group Management Security Object Set Management Security Operation Set Management
Risk Level Minor Minor Minor Minor Minor Minor Minor Minor
Description To assign a user group the permission to access subresources. To revoke the permission to access subresources from a user group. To assign a user the permission to access subresources. To revoke the permission to access subresources from a user. To implement the function of managing security users on the Nastar. To implement the function of managing security user groups on the Nastar. To implement the function of managing security object sets on the Nastar. To implement the function of managing security operation sets on the Nastar.
Related Tasks
Querying the Nastar Security Logs
Parameters
Parameter Operation User Description Description: To query logs by user. Settings Setting method: In the Filter dialog box, click . From the Select Operation User dialog box, select one or more items.
NOTE By default, all users' operation logs will be queried.
Issue 01 (2013-07-15)
2482
6 System Management
Description Description: To select operation terminals. Queried operation records are displayed by operation terminal.
Settings Setting method: In the Filter dialog box, click . From the Operation Terminal dialog box, select one or more items. Value: l Successful means that the operation is complete and all results are returned. l Failed means that the operation fails. l Partially successful means that the operation is complete and part of operation results are returned. l Ongoing means that the operation is being carried out but results are not yet returned. l Canceled means that the operation is canceled. Setting method: In the Filter dialog box, select one or more items from the Operation Result group box.
Operation Result
Risk Level
Value: Warning, Minor, and Risk Setting method: In the Filter dialog box, select one or more items from the Risk Level group box.
Issue 01 (2013-07-15)
2483
6 System Management
Description Description: To query logs by time range. If the time range is not set, all logs generated at any time are queried.
NOTE From means the start time, and To means the end time.
Settings Setting method: In the Filter dialog box, select From and To check box on the left side, and then enter the date and time directly in the text box, and set the time in or click the Date/Time Selection dialog box. Example: Example: Set the time range to 02/08/2009 00:00:00-02/09/2009 00:00:00.
NOTE To set the time format, choose File > Preferences from the main menu, expand Region Settings, and then choose the Time node. Set Time Format in the area on the right.
Description: In the Query Operation Logs window, you can set whether to display the Details column of operation logs. In Detail information contains, enter the information to be displayed in the Details column. The Nastar filters operation logs based on the information provided in Detail information contains.
Setting method: In the Filter dialog box, select the Detail information contains check box, and then enter the fields to be contained in Details in the text box that is on the right of the check box.
Operation Name
Setting method: In the Filter dialog box, click corresponding to Operation Name. In the Select Operation Name dialog box, select one or more items.
Operation Object
Setting method: In the Filter dialog box, click corresponding to Operation Object. In the Select Operation Object dialog box, select one or more items.
Issue 01 (2013-07-15)
2484
6 System Management
Description Description: User type of the user that performs an operation, including super user and local user.
Settings
NOTE These parameters are displayed in the Query Operation Logs window, not in the Filter dialog box.
Start Time
End Time
Operation Category
Details
Related Tasks
Querying the Nastar Operation Logs Querying the Nastar Operation Logs
Statistical items
Parameter Row Statistical Item Description Description: To set the row heading of the statistical result table. Settings Value: The parameter values include None, Operation User, User Type, Operation Name, Operation Category, Operation Terminal, Operation Result, and Operation Object.
Issue 01 (2013-07-15)
2485
6 System Management
Description Description: To set the row heading of the statistical result table. This parameter is the subitem of the preceding parameter Statistical Item.
Settings Value: The parameter values include None, Operation User, User Type, Operation Name, Operation Category, Operation Terminal, Operation Result, and Operation Object.
NOTE You can set at most one of both Statistical Item in Row to None. The statistical results are grouped by Statistical Item.
Column
Statistical Item
Value: The parameter values include Count, Operation User, User Type, Operation Name, Operation Category, Operation Terminal, Operation Result, and Operation Object. Value: -
Example
Filter Criteria
Parameter Operation User Description Description: To collect statistics by user. Settings Setting method: Click . In the Select Operation User dialog box, select one or more items.
NOTE By default, statistics on all users' operation logs will be collected.
Issue 01 (2013-07-15)
2486
6 System Management
Settings Setting method: Click . In the Select Operation Terminal dialog box, select one or more items.
NOTE By default, statistics on all terminals' operation logs will be collected.
Operation Result
Value: l Successful means that the operation is being carried out and all results are returned. l Failed means that the operation fails. l Partially successful means that the operation is complete but part of operation results are returned. l Ongoing means that the operation is being carried out but results are not yet returned. l Canceled means that the operation is canceled. Setting method: From the Operation Result group box, select one or more items.
Risk Level
Value: Warning, Minor, and Risk Setting method: From the Risk Level group box, select one or more items.
Issue 01 (2013-07-15)
2487
6 System Management
Description Description: To collect statistics by time range. From means the start time, and To means the end time.
Settings Setting method: Select From and To check boxes on the left side, and then enter the date and time directly in the text box, or click and set the time in the Date/Time Selection dialog box. Example: Example: Set the time range to 02/08/2009 00:00:00-02/09/2009 00:00:00.
NOTE To set the time format, choose File > Preferences from the main menu, expand Region Settings, and then choose the Time node. Set Time Format in the area on the right.
Description: In the Operation Log Statistics window, you can set whether to display the Details column of operation logs. In Detail information contains, enter the information to be displayed in the Details column. The Nastar filters operation logs based on the information provided in Detail information contains.
Setting method: Select the Detail information contains check box, and then enter the fields to be contained in Details in the text box that is on the right of the check box.
Operation Name
Setting method: Click corresponding to Operation. In the Select Operation Name dialog box, select one or more items. Setting method: Click corresponding to Operation Object. In the Select Operation Object dialog box, select one or more items.
Operation Object
Issue 01 (2013-07-15)
2488
6 System Management
Related Tasks
Collecting Statistics on the Nastar Operation Logs Collecting Statistics on the Nastar Operation Logs
Parameters
Parameter Source Description Description: To query logs by log source. Settings Setting method: In the Filter dialog box, click . In the Select Source dialog box, select one or more items.
NOTE By default, all sources' system logs will be queried.
Level
Value: Warning, Minor, and Risk. Setting method: In the Filter dialog box, select one or more items from the Level group box.
Operation Result
Value: Failed, Successful, and Unknown. Setting method: In the Filter dialog box, select one or more items from the Operation Result group box.
Issue 01 (2013-07-15)
2489
6 System Management
Description Description: To query logs by time range. If the time range is not set, all logs generated at any time are queried.
NOTE From means the start time, and To means the end time.
Settings Setting method: In the Filter dialog box, select From and To check box on the left side, and then enter the date and time directly in the text box, and set the time in or click the Date/Time Selection dialog box. Example: Example: Set the time range to 02/08/2009 00:00:00-02/09/2009 00:00:00.
NOTE To set the time format, choose File > Preferences from the main menu, expand Region Settings, and then choose the Time node. Set Time Format in the area on the right.
Description: In the Query System Logs window, you can set whether to display the Details column of system logs. In Detail information contains, enter the information to be displayed in the Details column. The Nastar filters system logs based on the information provided in Detail information contains.
Setting method: In the Filter dialog box, select the Detail information contains check box, and then enter the fields to be contained in Details in the text box that is on the right of the check box.
Time
NOTE These parameters are displayed in the Query System Logs window, not in the Filter dialog box.
Basic Information
Details
Issue 01 (2013-07-15)
2490
6 System Management
Related Tasks
Collecting Statistics on the Nastar Operation Logs Querying the Nastar System Logs Querying the Nastar System Logs
Statistical items
Parameter Row Statistical Item Description Description: To set the row heading of the statistical result table. Column Statistical Item Description: To set the column heading of the statistical result table. Example Description: To preview the style of the statistical result table. Settings Value: The parameter values include Level, and Source. Value: The parameter values include Count, Level, and Source. Value: -
Filter Criteria
Parameter Source Description Description: To collect statistics by source. Settings Setting method: Click . In the Select Source dialog box, select one or more items.
NOTE By default, statistics on all sources' system logs will be collected.
Level
Value: Warning, Minor, and Risk. Setting method: From the Level group box, select one or more items.
Issue 01 (2013-07-15)
2491
6 System Management
Settings Value: Failed, Successful, and Unknown. Setting method: From the Operation Result group box, select one or more items.
Time Range
Description: To collect statistics by time range. If the time range is not set, all logs generated at any time are queried. From means the start time, and To means the end time.
Setting method: Select From and To check box on the left side, and then enter the date and time directly in the text and set the time box, or click in the Date/Time Selection dialog box. Example: Example: Set the time range to 02/08/2009 00:00:00-02/09/2009 00:00:00.
NOTE To set the time format, choose File > Preferences from the main menu, expand Region Settings, and then choose the Time node. Set Time Format in the area on the right.
Description: In the System Log Statistics window, you can set whether to display the Details column of system logs. In Detail information contains, enter the information to be displayed in the Details column. The Nastar filters system logs based on the information provided in Detail information contains.
Setting method: Select the Detail information contains check box, and then enter the fields to be contained in Details in the text box that is on the right of the check box.
Related Tasks
Collecting Statistics on the Nastar System Logs Collecting Statistics on the Nastar Security Logs Collecting Statistics on the Nastar System Logs Collecting Statistics on the Nastar Security Logs
Issue 01 (2013-07-15)
2492
6 System Management
Parameters
Parameter Operation User Description Description: To query logs by user. Settings Setting method: In the Filter dialog box, click . In the Select Operation User dialog box, select one or more items. Operation Terminal Description: To query logs by IP address of the terminal. Setting method: In the Filter dialog box, click . In the Select Operation Terminal dialog box, select one or more items. Value: l Successful means that the operation is complete and all results are returned. l Failed means that the operation fails. l Partially successful means that the operation is complete and part of operation results are returned. Setting method: In the Filter dialog box, select one or more items from the Operation Result group box. Risk Level Description: To query logs by risk level. Value: Warning, Minor, and Risk. Setting method: In the Filter dialog box, select one or more items from the Risk Level group box.
Operation Result
Issue 01 (2013-07-15)
2493
6 System Management
Description Description: To query logs by time range. If the time range is not set, all logs generated at any time are queried. From means the start time, and To means the end time.
Settings Setting method: In the Filter dialog box, select From and To check box on the left side, and then enter the date and time directly in the text box, and set the time in the or click Date/Time Selection dialog box. Example: Example: Set the time range to 02/08/2009 00:00:00-02/09/2009 00:00:00.
NOTE To set the time format, choose File > Preferences from the main menu, expand Region Settings, and then choose the Time node. Set Time Format in the area on the right.
Description: In the Query Security Logs window, you can set whether to display the Details column of security logs. In Detail information contains, enter the information to be displayed in the Details column. The Nastar filters security logs based on the information provided in Detail information contains.
Setting method: In the Filter dialog box, select the Detail information contains check box, and then enter the fields to be contained in Details in the text box that is on the right of the check box.
Security Event
Setting method: In the Filter dialog box, click corresponding to Security Event. In the Select Security Event dialog box, select one or more items.
Operation Object
Setting method: In the Filter dialog box, click corresponding to Operation Object. In the Select Operation Object dialog box, select one or more items.
Issue 01 (2013-07-15)
2494
6 System Management
Description Description: User type of the user that performs a security event, including super user and local user.
Settings
NOTE These parameters are displayed in the Query Security Logs window, not in the Filter dialog box.
Operation Time
Details
Related Tasks
Querying the Nastar Security Logs Querying the Nastar Security Logs
Statistical items
Parameter Row Statistical Item Description Description: To set the row heading of the statistical result table. Settings Value: The parameter values include None, Operation User, User Type, Security Event, Operation Terminal, Operation Result, Operation Object, and Risk Level.
Issue 01 (2013-07-15)
2495
6 System Management
Description Description: To set the row heading of the statistical result table. This parameter is the subitem of the preceding parameter Statistical Item.
Settings Value: The parameter values include None, Operation User, User Type, Security Event, Operation Terminal, Operation Result, Operation Object, and Risk Level.
NOTE You can set at most one of both Statistical Item in Row to None. The statistical results are grouped by Statistical Item.
Column
Statistical Item
Value: The parameter values include Count, Operation User, User Type, Security Event, Operation Terminal, Operation Result, Operation Object, and Risk Level. Value: -
Example
Filter Criteria
Parameter Operation User Description Description: To collect statistics by user. Settings Setting method: Click . In the Select Operation User dialog box, select one or more items. Setting method: Click . In the Select Operation Terminal dialog box, select one or more items.
Operation Terminal
Issue 01 (2013-07-15)
2496
6 System Management
Settings Value: l Successful means that the operation is complete and all results are returned. l Failed means that the operation fails. l Partially successful means the operation is complete, and some operation results are returned. Setting method: In the Result area, select one or more items.
Risk Level
Value: Warning, Minor, and Risk. Setting method: From the Risk Level group box, select one or more items.
Time Range
Description: To collect statistics by time range. If the time range is not specified, all logs generated at any time are queried. From means the start time, and To means the end time.
Setting method: Select From and To check box on the left side, and then enter the date and time directly in the text and set the time box, or click in the Date/Time Selection dialog box. Example: Example: Set the time range to 02/08/2009 00:00:00-02/09/2009 00:00:00.
NOTE To set the time format, choose File > Preferences from the main menu, expand Region Settings, and then choose the Time node. Set Time Format in the area on the right.
Issue 01 (2013-07-15)
2497
6 System Management
Description Description: In the Security Log Statistics window, you can set whether to display the Details column of security logs. In Detail information contains, enter the information to be displayed in the Details column. The Nastar filters security logs based on the information provided in Detail information contains.
Settings Setting method: Select the Detail information contains check box, and then enter the fields to be contained in Details in the text box that is on the right of the check box.
Security Event
Setting method: Click corresponding to Security Event. In the Select Security Event dialog box, select one or more items. Setting method: Click corresponding to Operation Object. In the Select Operation Object dialog box, select one or more items.
Operation Object
Parameters
Parameter Master Server IP Address Description Description: IP address of the primary server. The server receives the logs forwarded by the Nastar. Description: Port number of the primary server that receives forwarded logs. Value: Value range: 1-65535. Settings -
Issue 01 (2013-07-15)
2498
6 System Management
Description Description: IP address of the secondary server that receives forwarded logs. Description: Port number of the secondary server that receives forwarded logs. Description: Protocol for log forwarding.
Settings -
Value: Value range: 1-65535. Value: Value range: TCP or UDP. Value: Value range: Yes or No. Value range: Emergency, Alert, Critical, Error, Warning, Notice, Informational, and Debug.
NOTE The mapping between the Nastar log level and the Syslog level is: risk-critical, minorwarning, warning-notice. If you need to forward the Nastar log of the Risk level, click on the right, and select Critical in the Syslog Level Selection dialog box.
Protocol
Enable
Syslog Level
String Filter
Description: A log is forwarded only when the log contains the specified string.
Remark
Issue 01 (2013-07-15)
2499
6 System Management
Common Parameters
Table 6-30 Parameters Applicable for both One-time and Periodic Tasks Parameter Task name Description Description: Refers to the name of a timing task. Settings Value: l A maximum of 64 bytes. l Unique and not null. l Case sensitive. Execution type Description: l One-time: If you select this option, the system runs the created task once at the defined time point. l Periodic: If you select this option, the system runs the created task periodically. Start time Description: This parameter sets the time for starting a task. Value: l One-time l Periodic
NOTE The execution type cannot be configured again after the task is created.
Value: The start time should be later than the time displayed on the server.
NOTE For a one-time timing task, if you have selected Run immediately, the Start time parameter is invalid. The task is performed immediately after the related settings are complete.
Task type
Issue 01 (2013-07-15)
2500
6 System Management
Table 6-31 Parameters Only Applicable for Periodic Tasks Parameter Execution Interval Description Description: Interval between periodic tasks. It has two enlistments: duration and unit. Settings Value: l The period can be represented in either of the following units: minutes, hours, days, weeks, months. Second is not supported. The supported units of Period vary according to the task type. l The value range for period should be as follows: Minute (1 - 366 x 24 x 60), Hour (1 - 366 x 24), Day (1 - 366), Week (1 - 52), Month (1 12).
NOTE The execution interval cannot be configured again after a dump task is created.
Execution Times
Description: This parameter indicates the times that a periodic task is executed.
NOTE This parameter is displayed in the Attribute dialog box only after you set it when creating and copying a periodic task.
Value: 0 - 65535
NOTE l 0 indicates that the number of times for executing periodic tasks is not restricted. l The execution times cannot be configured again after the task is created.
Extended Parameters
Table 6-32 Extended Parameters Parameter Compress file after export Description Description: This parameter is used to set whether compress files after dumping. If yes, export files will be compressed to a .zip file. After compression, the source files are deleted. Description: This parameters indicates the format of the dump files of logs. File path Description: This parameter indicates that dump log files are saved to the specified path on the server. Setting Value: Yes or No
File type
Value: Value range: CSV, XML, TXT or HTML. Value: Manually input the path to save log files.
Issue 01 (2013-07-15)
2501
6 System Management
Description Description: When a dump task is executed, the logs older than this period are dumped. Description: l Hold files for XX days: In the dump directory, the log files older than this period are deleted. l Hold max. XX files: In the dump directory, if the number of log files exceeds the value of this parameter, the Nastar deletes the oldest dump files until the number of log files in this directory becomes less than the value of this parameter. l Hold max. XX MB file data: In the dump directory, if the total size of log files exceeds the value of this parameter, the Nastar deletes the oldest dump files until the total size of log files in this directory becomes less than the value of this parameter.
Setting Value: Value range: 1-180. Default value: 30. Value: l The value range of Hold files for XX days is 1-180. Default value: 15. l The value range of Hold max. XX files is 200-2000. Default value: 1000. l The value range of Hold max. XX MB file data is 200-4096. Default value: 1024.
Related Tasks
Setting Nastar Log Dump Setting Nastar Log Export
Common Parameters
Table 6-33 Parameters Applicable for both One-time and Periodic Tasks Parameter Task name Description Description: Refers to the name of a timing task. Settings Value: l A maximum of 64 bytes. l Unique and not null. l Case sensitive.
Issue 01 (2013-07-15)
2502
6 System Management
Description Description: l One-time: If you select this option, the system runs the created task once at the defined time point. l Periodic: If you select this option, the system runs the created task periodically.
Start time
Value: The start time should be later than the time displayed on the server.
NOTE For a one-time timing task, if you have selected Run immediately, the Start time parameter is invalid. The task is performed immediately after the related settings are complete.
Task type
Table 6-34 Parameters Only Applicable for Periodic Tasks Parameter Execution Interval Description Description: Interval between periodic tasks. It has two enlistments: duration and unit. Settings Value: l The period can be represented in either of the following units: minutes, hours, days, weeks, months. Second is not supported. The supported units of Period vary according to the task type. l The value range for period should be as follows: Minute (1 - 366 x 24 x 60), Hour (1 - 366 x 24), Day (1 - 366), Week (1 - 52), Month (1 12).
NOTE The execution interval cannot be configured again after a dump task is created.
Issue 01 (2013-07-15)
2503
6 System Management
Description Description: This parameter indicates the times that a periodic task is executed.
NOTE This parameter is displayed in the Attribute dialog box only after you set it when creating and copying a periodic task.
Extended Parameters
Table 6-35 Extended Parameters Parameter Compress file after export Description Description: This parameter is used to set whether compress export files. If yes, export files will be compressed to a .zip file. After compression, the source files are deleted. Description: This parameters indicates the format of the export files of logs. Description: This parameter indicates that export log files are saved to the specified path on the server. Export File Managemen t Description: l Hold files for XX days: In the export directory, the log files older than this period are deleted. l Hold max. XX files: In the export directory, if the number of log files exceeds the value of this parameter, the Nastar deletes the oldest export files until the number of log files in this directory becomes less than the value of this parameter. l Hold max. XX MB file data: In the export directory, if the total size of log files exceeds the value of this parameter, the Nastar deletes the oldest export files until the total size of log files in this directory becomes less than the value of this parameter. Setting Value: Yes or No
Value: Value range: .csv, .xml, .txt or .html. Value: Manually input the path to save log files. Value: l The value range of Hold files for XX days is 1-180. Default value: 15. l The value range of Hold max. XX files is 200-2000. Default value: 1000. l The value range of Hold max. XX MB file data is 200-4096. Default value: 1024.
File path
Issue 01 (2013-07-15)
2504
6 System Management
Related Tasks
Setting Nastar Log Dump Setting Nastar Log Export
Context
l l l The parameter Server status refresh interval indicates the sampling interval. That is, the CPU and memory usage is sampled at the specified interval. CPU overload indicates that the CPU usage is larger than the generation threshold. If the CPU usage sampled each time is larger than the generation threshold , it means that the CPU is continuously overloaded. In this case, the number of continuous CPU overload times is equal to that of continuous sampling times.
Procedure
Step 1 Choose System > System Monitor > Settings from the main menu. Step 2 In the System Monitor Settings dialog box, click the Server Monitor tab. Step 3 Set the parameters. Step 4 Click OK. ----End
Issue 01 (2013-07-15)
2505
6 System Management
Result
l When the number of sampling times with overloading reaches the specified value, the round icon in the CPU Usage column turns red on the Server Monitor tab page in the System Monitor Browser window. If you enable the function of displaying pop-up messages, you can receive performance exception messages on the status bar of the client. When the memory usage is larger than the threshold, the round icon in the Memory Usage column turns red on the Server Monitor tab page in the System Monitor Browser window. If you enable the function of displaying pop-up messages, you can receive performance exception messages on the status bar of the client.
Related Tasks
Monitoring the Status of the Nastar Server
Related References
Parameters for Setting the Monitoring Thresholds of the Nastar Server Parameters for Setting the Monitoring Thresholds of the Nastar Server
Setting the Parameters for Monitoring the Disk Usage of the Nastar Server
You can set the disk monitoring parameters to monitor the disk usage of the Nastar server. This helps you to find and handle insufficiency of the disk space in time, thereby preventing service exceptions. When the disk usage reaches the specified threshold, the Nastar client reaches a high disk usage. You can also determine whether to display pop-up messages on the client. After you enable this function, the Nastar client displays a pop-up message, prompting you of a disk exception.
Procedure
Step 1 Choose System > System Monitor > Settings from the main menu. Step 2 In the System Monitor Settings dialog box, click the Hard Disk Monitor tab. Step 3 On the Hard Disk Monitor tab page, set Hard disk status refresh interval and the thresholds for exception generation and clearance. To set the thresholds, specify default values shared by all disks under Default value setting. Then, you can specify other values in Advanced settings for a specific disk. The detailed procedure is as follows: 1. Click + before Default value setting, and then set the thresholds for generating and clearing exception of different severities. The threshold specified for generating alarms of a low severity must be smaller than that for generating alarms of a high severity. Expand Advanced settings, and then click + before the server name. You can view that all disks use the default thresholds. To specify other values for a disk, click + before the disk name, and then click the cell after the name. In the drop-down list, select Customize Value. In the text box, enter the thresholds for generating and clearing exception of different severities. If you do not want to receive alarms of a disk, select Disable alarm generation.
2.
Step 4 Optional: Expand Advanced setting until the disk name is displayed. In the Enable Bubble column, select Enable or Disable.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2506
6 System Management
Result
When the disk usage is larger than the threshold, the round icon in the Status column turns red on the Hard Disk Monitor tab page in the System Monitor Browser window. If you enable the function of displaying pop-up messages, the message The hard disk partition is abnormal is displayed on the status bar of the client.
Related Tasks
Monitoring the Disk Status of the Nastar Server
Related References
Parameters for Setting the Hard Disk Monitoring Thresholds of the Nastar Server Parameters for Setting the Hard Disk Monitoring Thresholds of the Nastar Server
Setting the Parameters for Monitoring the Database Usage of the Nastar Server
You can set the database monitoring parameters to monitor the Nastar database usage. This helps you to find and handle insufficiency of the database space in time, thereby preventing service exceptions. When the database usage of the Nastar server reaches the lower threshold, it indicates that the Nastar reaches a high database usage.
Procedure
Step 1 Choose System > System Monitor > Settings from the main menu. Step 2 In the System Monitor Settings dialog box, click the Database Monitor tab. Step 3 On the Database Monitor tab page, set Database status refresh interval and the thresholds for abnormal. To set the thresholds, specify default values shared by all databases under Default value setting. Then, you can specify other values in Advanced settings for a specific database. The detailed procedure is as follows: 1. Click + before Default value setting, and then set the thresholds of different severities. The threshold specified for generating alarms of a low severity must be smaller than that for generating alarms of a high severity. Expand Advanced settings, and then click + before the server name and database instance name. You can view that all databases use the default thresholds. To specify other values for a database, click + before the database name, and then click the cell after the name. In the drop-down list, select Customize Value. In the text box, enter the thresholds of different severities. If you do not want to monitor the usage of a database, select Disabled Monitoring.
2.
6 System Management
Result
When the database usage is larger than the threshold, the round icon in the Status column turns red on the Database Monitor tab page in the System Monitor Browser window.
Related Tasks
Monitoring the Database Status of the Nastar Server
Related References
Parameters for Setting the Database Monitoring Thresholds of the Nastar Server Parameters for Setting the Database Monitoring Thresholds of the Nastar Server
Setting the Parameters for Monitoring the Service Status of the Nastar Server
You can set the interval of refreshing the service status and determine whether to display popup messages. If you enable the function of displaying pop-up messages, the Nastar prompts service changes and refreshes the service status at the specified refresh interval.
Procedure
Step 1 Choose System > System Monitor > Settings from the main menu. Step 2 In the System Monitor Settings dialog box, click the Service Monitor tab. Step 3 On the Service Monitor tab page, set Service status refresh interval and determine whether to display pop-up messages. Step 4 Click OK. ----End
Result
l l On the Service Monitor tab page in the System Monitor Browser window, information is refreshed at the specified interval. When the tooltip function of some services is enabled, a status indicator is displayed on the status bar in the lower-right corner of the GUI. When all the services for which the tooltip function is enabled are running, the status indicator is displayed green. When one or multiple such services are stopped, the status indicator is displayed red and a pop-up message is displayed.
Related References
Parameters for Setting the Service Monitoring Thresholds of the Nastar Server Parameters for Setting the Service Monitoring Thresholds of the Nastar Server
Issue 01 (2013-07-15)
2508
6 System Management
Context
l l l The parameter Server status refresh interval indicates the sampling interval. That is, the CPU and memory usage is sampled at the specified interval. CPU overload indicates that the CPU usage is larger than the generation threshold. If the CPU usage sampled each time is larger than the generation threshold, it means that the CPU is continuously overloaded. In this case, the number of continuous CPU overload times is equal to that of continuous sampling times.
Procedure
Step 1 Choose System > xSAU System Monitor > Settings from the main menu. Step 2 In the xSAU System Monitor Settings dialog box, click the Server Monitor tab. Step 3 Set the parameters. Step 4 Click OK. ----End
Setting the Parameters for Monitoring the Disk Usage of the xSAU
You can set the disk monitoring parameters to monitor the disk usage of the xSAU. This helps you to find and handle insufficiency of the disk space in time, thereby preventing service exceptions.
Procedure
Step 1 Choose System > xSAU System Monitor > Settings from the main menu. Step 2 In the xSAU System Monitor Settings dialog box, click the Hard Disk Monitor tab. Step 3 On the Hard Disk Monitor tab page, set Hard disk status refresh interval and the thresholds. Step 4 After the setting, click OK. ----End
Setting the Parameters for Monitoring the Database Usage of the xSAU
You can set the database monitoring parameters to monitor the xSAU database usage. This helps you to find and handle insufficiency of the database space in time, thereby preventing service exceptions.
Procedure
Step 1 Choose System > xSAU System Monitor > Settings from the main menu.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2509
6 System Management
Step 2 In the xSAU System Monitor Settings dialog box, click the Database Monitor tab. Step 3 On the Database Monitor tab page, set Database status refresh interval and the thresholds. Step 4 After the setting, click OK. ----End
Context
If a service is stopped or abnormal, its status icon is displayed in red.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Service Monitor tab. Step 3 Right-click an service and choose Details.
NOTE
You can also double-click a service to access the Service Details dialog box.
Step 4 In the displayed Service Details dialog box, view the service details and dependencies between services. ----End
Related Tasks
Refreshing the Monitoring Information Saving the Monitoring Information
Related References
Parameters for Monitoring the Service Status of the Nastar Server Parameters for Monitoring the Service Status of the Nastar Server
6 System Management
status of the Nastar server. Thus, you can identify and handle exceptions in time, ensuring the efficient running of the Nastar server.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Process Monitor tab. Step 3 View the process status of the server. ----End
Related Tasks
Refreshing the Monitoring Information Saving the Monitoring Information
Related References
Parameters for Monitoring the Process Status of the Nastar Server Parameters for Monitoring the Process Status of the Nastar Server
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Hard Disk Monitor tab. Step 3 View the disk status of the server. Whether Status of an item is Normal depends on the preset threshold for alarm generation. When the usage of the item exceeds the threshold, Status changes to Abnormal. ----End
Related Tasks
Setting the Parameters for Monitoring the Disk Usage of the Nastar Server Refreshing the Monitoring Information Saving the Monitoring Information
Related References
Parameters for Monitoring the Hard Disk Status of the Nastar Server Parameters for Monitoring the Hard Disk Status of the Nastar Server
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2511
6 System Management
Context
If the database space is insufficient, contact huawei technical support engineers to determine an expansion solution.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Database Monitor tab.
NOTE
The database monitoring parameters vary according to different databases. For the Oracle database, the available parameters for database monitoring include Database Name, Total Data Space, Free Data Space, Total Data Space Usage, Table Space Usage, and Status.
Step 3 View the database status of the Nastar server. Whether Status of a database is Normal depends on the preset alarm threshold. When the database usage exceeds the threshold, Status changes to Abnormal. ----End
Related Tasks
Setting the Parameters for Monitoring the Database Usage of the Nastar Server Refreshing the Monitoring Information Saving the Monitoring Information
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Server Monitor tab. Step 3 View the status of the Nastar server. ----End
Related Tasks
Setting the Parameters for Monitoring the Nastar Server Refreshing the Monitoring Information
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2512
6 System Management
Related References
Parameters for Monitoring the Status of the Nastar Server Parameters for Monitoring the Status of the Nastar Server
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the Component Information tab. Step 3 View the information about all installed components. ----End
Related Tasks
Refreshing the Monitoring Information Saving the Monitoring Information
Related References
Parameters for Viewing the Information About Nastar Server Components Parameters for Viewing the Information About Nastar Server Components
Context
l l Only the current tab page is refreshed. After you switch to another monitor tab, the monitoring information on this tab page is refreshed immediately.
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the tab corresponding to the monitoring information to be refreshed. Step 3 Click Refresh. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2513
6 System Management
Related Tasks
Monitoring the Process Status of the Nastar Server Monitoring the Disk Status of the Nastar Server Monitoring the Database Status of the Nastar Server Monitoring the Status of the Nastar Server Viewing the Component Information of the Nastar Server Saving the Monitoring Information Monitoring the Service Status of the Nastar Server
Procedure
Step 1 Choose System > System Monitor > Browser from the main menu. Step 2 In the System Monitor Browser window, click the tab corresponding to the monitoring information, and then click Save As.
NOTE
l The monitoring information can be saved in the format of .txt, .html, .csv, or .xml. The default format is .xml. l Two types of encoding formats are supported: ANSI - Latin 1 and UTF-8. The default encoding format is ANSI - Latin 1. You are recommended to use the default encoding format if the saved file does not need to support multiple languages; otherwise, UTF-8 is recommended.
Step 3 In the Save dialog box, select a path, enter a file name, and click Save. ----End
Related Tasks
Refreshing the Monitoring Information Monitoring the Process Status of the Nastar Server Monitoring the Disk Status of the Nastar Server Monitoring the Database Status of the Nastar Server Monitoring the Status of the Nastar Server Viewing the Component Information of the Nastar Server Monitoring the Service Status of the Nastar Server
Issue 01 (2013-07-15)
2514
6 System Management
Procedure
Step 1 Choose System > xSAU System Monitor > Browser from the main menu. Step 2 In the xSAU System Monitor Browser window, click the Service Monitor tab. Step 3 View the status of the eSAU/LTE SAU/SAU. l If a service is normal, its status icon is displayed in green. l If a service is stopped or abnormal or disconnected, its status displays -. l If an SAU is not displayed in the xSAU monitoring results after you restart the Nastar services, the SAU is in abnormal state or is stopped or disconnected. ----End
Procedure
Step 1 Choose System > xSAU System Monitor > Browser from the main menu. Step 2 In the xSAU System Monitor Browser window, click the Process Monitor tab. Step 3 View the process status of the server. ----End
Procedure
Step 1 Choose System > xSAU System Monitor > Browser from the main menu. Step 2 In the xSAU System Monitor Browser window, click the Hard Disk Monitor tab. Step 3 View the disk status of the server. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2515
6 System Management
Context
If the database space is insufficient, contact huawei technical support engineers to determine an expansion solution.
Procedure
Step 1 Choose System > xSAU System Monitor > Browser from the main menu. Step 2 In the xSAU System Monitor Browser window, click the Database Monitor tab. Step 3 View the database status of the server. ----End
Procedure
Step 1 Choose System > xSAU System Monitor > Browser from the main menu. Step 2 In the xSAU System Monitor Browser window, click the Server Monitor tab. Step 3 View the status of the server. ----End
Prerequisites
l You have configured the DNS server. For detailed operations, see Configuring the DNS Server in Product Documentation > Installation and Commissioning > Nastar Commissioning Guide (HP) > Commissioning the Function of Distributing Reports Through Emails (Optional). You have set the users to whom the system sends emails. For detailed operations, see 2.4.10 Setting a Mailbox and Address List for Sending Analysis Reports (Optional) in Product Documentation > Operation and Maintenance > Nastar Quick Start > Preparing Basic Data.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2516
Issue 01 (2013-07-15)
6 System Management
Context
Table 6-36 describes the subject and content of such emails. Table 6-36 Email subject and content Scenario The used database tablespace reaches a specified threshold The disk space reaches a specified threshold Email Subject No enough table space in Nastar system No enough disk space in Nastar system Email Content Dear user: Your Nastar system is being overloaded. To keep the Nastar running properly, you must adjust the data storage policy now. Enter the data maintenance interface and adjust theme data now.
Procedure
Step 1 Choose System > xSAU System Monitor > Email Settings from the main menu. Step 2 In the Email Sending Monitored by xSAU System dialog box, the system loads all existing users. Step 3 In the Select column, select the User Name of each user to whom the system will send emails. Step 4 Click OK. ----End
Follow-up Procedure
For detailed operations about how to clean up the disk space and adjust the data storage policy, see 6.8.2 Periodically Deleting Analysis Data in Product Documentation > Operation and Maintenance > System Management > Managing Analysis Data.
Prerequisites
You have configured OSS and NE information. For detailed operations, see 2.3 Configuring OSS and NE Information.
Context
You are advised to use this function to check whether the system's network connections are normal in the following scenarios:
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2517
6 System Management
l l l l
After a new Nastar system is installed; that is, OSS and NE information are newly configured After NEs' are upgraded or NE information is changed (NE information configurations are updated) After the M2000 is upgraded, the M2000 information is changed, or a new M2000 is introduced (OSS information configurations are updated) After the Nastar system is upgraded or the information of Nastar's components is changed (eSAU/SAU/LTE SAU/PS SAU information configurations are updated)
Procedure
Step 1 Choose System > System Link Check from the main menu. Step 2 In the displayed System Link Check window, click Check. The system checks network connections and displays the status of connections between the current Nastar server and the configured OSS/SAU/LTE SAU/PS SAU. Table 6-37 lists the related parameters. Table 6-37 Parameters Paramete r Name Type Status Description IP address of the object to be checked Type of the object to be checked, such as eSAU, SAU, M2000, and so on Network connection status The status includes OK, Exception, Checking, and Unknown. Update Time Detail Info Time when the network connection status is checked Detailed information about network connection status l If the network connection status is Exception or Unknown, the possible causes will be displayed. Solve the problem based on the cause description and then check the network connection again. l If the network connection status is Checking, wait for about one minute (generally, the check does not exceed one minute) and then perform the check again. If the check duration is still long, contact Huawei technical support.
TIP
Select one or multiple rows of components, right-click, and choose Check Selected or Check All from the shortcut menu to check network connections.
----End
Issue 01 (2013-07-15)
2518
6 System Management
Parameters
Parameter Server Monitor Parameter Settings Number of consecutive CPU overloads (10-400) Description Description: l If the CPU usage sampled each time is larger than the generation threshold, it means that the CPU is consecutively overloaded. When the number of consecutive overload times reaches the specified value, the monitor status is abnormal (the icon is displayed in red). l If the CPU usage sampled at a time is smaller than the clearance threshold, the monitor status returns to normal (the icon is displayed in green). Server status refresh interval (2-60 seconds) Description: Refresh interval of server monitoring, that is, the CPU usage is sampled every x seconds. Value: Value range: 2-60 Default value: 15 Setting Value: Value range: 10-400 Default value: 40
Issue 01 (2013-07-15)
2519
6 System Management
Description Description: Set the generation threshold and the clearance threshold of high CPU usage of the Nastar.
Setting Value: Value range of usage: 1-99. Default value: 90. Value range of offset: 1-99. Default value: 70. Value: Value range of usage: 1-99. Default value: 95. Value range of offset: 1-99. Default value: 85.
Set the generation threshold and the clearance threshold of high memory usage of the Nastar. l When the Memory usage is more than Generation Threshold, the monitor status is abnormal (the icon is displayed in red). l When the Memory usage is less than Clearance Threshold, the monitor status is normal (the icon is displayed in green).
Related Tasks
Setting the Parameters for Monitoring the Nastar Server Setting the Parameters for Monitoring the Nastar Server
Parameters for Setting the Hard Disk Monitoring Thresholds of the Nastar Server
This topic describes the parameters of hard disk monitoring. When setting the hard disk monitoring thresholds of the server, you need to set these parameters.
Issue 01 (2013-07-15)
2520
6 System Management
Parameters
Parameter Disk Monitor Parameter Settings Hard disk status refresh interval (60-3600 seconds) Description Description: Refresh interval of hard disk monitoring. Description: Set the generation threshold and the clearance threshold of high disk usage of the Nastar server. Setting Value: Value range: 60-3600 Default value: 60 Setting method: Click + to expand Default value setting. Set the default thresholds of high hard disk usage in different severities. Value: Value range: 1-99 Default value of Generation Threshold: l Warning: 60 l Minor: 70 l Major: 80 l Critical: 90 Default value of Clearance Threshold: l Warning: 55 l Minor: 65 l Major: 75 l Critical: 85
Issue 01 (2013-07-15)
2521
6 System Management
Description Description: User-defined the generation threshold and the clearance threshold of high disk usage of the Nastar server. You can set thresholds for individual disks.
Setting Setting method: 1. Click + before Advanced settings to expand the nodes. 2. Click + before the server name to expand nodes. 3. Click + before a disk partition name to expand nodes. In the drop-down list after the disk partition name, select a threshold setting mode. Value: l If you select Default value, the Nastar uses the threshold specified in Default value setting. l If you select Customize value, the Nastar uses customized thresholds. The value range is 1-99.
Related Tasks
Setting the Parameters for Monitoring the Disk Usage of the Nastar Server Setting the Parameters for Monitoring the Disk Usage of the Nastar Server
Parameters for Setting the Database Monitoring Thresholds of the Nastar Server
This topic describes the parameters of database monitoring. When setting the database monitoring thresholds of the server, you need to set these parameters.
Issue 01 (2013-07-15)
2522
6 System Management
Parameters
Parameter Database Monitor Parameter Settings Database status refresh interval (300-3600 seconds) Description Description: Interval of database refreshing. Setting Value: Value range: 300-3600 Default value: 300 Database Monitor Threshold Settings Default value setting (%) Description: Default threshold for generating a high database usage alarm of the Nastar server. l When the database usage is larger than Threshold of an alarm severity, the Nastar generates a high database usage alarm of this severity. l When the database usage is smaller than Threshold of an alarm severity, the Nastar clears the high database usage alarm of this severity. Setting method: Click + to expand Default value setting. Set the default threshold for generating high database usage alarms in different severities. Value: Value range: 1-100 Default value: l Warning: 85 l Minor: 90 l Major: 95 l Critical: 98
Issue 01 (2013-07-15)
2523
6 System Management
Description Description: User-defined threshold for generating a high database usage alarm of the Nastar server. You can set thresholds for individual databases. l When the database usage is larger than Threshold of an alarm severity, the Nastar generates a high database usage alarm of this severity. l When the database usage is smaller than Threshold of an alarm severity, the Nastar clears the high database usage alarm of this severity.
Setting Setting method: 1. Click + before Advanced settings to expand nodes. 2. Click + before the server name to expand nodes. 3. Click + before the database instance name to expand nodes. 4. Click + before a database name to expand nodes. In the drop-down list after the database name, select a threshold setting mode. Value: l Default Value: Use default thresholds for the database usage alarms of different severities. l Customize Value: Customize thresholds for the database usage alarms of different severities. Value range: 1-100 Default value: Warning: 85 Minor: 90 Major: 95 Critical: 98 l Disabled Monitoring: Disable the
Issue 01 (2013-07-15)
2524
6 System Management
Parameter
Description
Related Tasks
Setting the Parameters for Monitoring the Database Usage of the Nastar Server Setting the Parameters for Monitoring the Database Usage of the Nastar Server
Parameters for Setting the Service Monitoring Thresholds of the Nastar Server
This topic describes the parameters of service monitoring. When setting the service monitoring of the server, you need to set these parameters.
Parameters
Parameter Services Monitor Parameter Settings Service status refresh interval (60-3600 seconds) Description Description: Interval of service refreshing. Setting Value: Value range: 60-3600 Default value: 60 Service Monitor Pop-Up Settings Default Group Description: Set whether to display the service status at the lower right corner of the Nastar system monitor client by using
NOTE l If all the monitored services are running, displayed. is
Setting method: Select a service from the Service Name drop-down list. Select enable or disable in the corresponding Popup drop-down list.
or
l If a monitored service is stopped, is displayed. l You can doubleclick or to access the Service Monitor tab.
Issue 01 (2013-07-15)
2525
6 System Management
Related Tasks
Setting the Parameters for Monitoring the Service Status of the Nastar Server Setting the Parameters for Monitoring the Service Status of the Nastar Server
Parameters
Parameter Service Name Description Description: Name of a service. Process Name Description: Name of a process. Description Description: Description of functions, interfaces, and other information of a service. Status Description: Status of a service. Startup Mode Description: Service startup mode: Automatic, Manual, or Disable. The Disable mode is available only for stopped services. Start Time Description: Time when a service is started. Server Name Description: Name of a server.
Related Tasks
Monitoring the Service Status of the Nastar Server Monitoring the Service Status of the Nastar Server
Issue 01 (2013-07-15)
2526
6 System Management
Parameters
Parameter Process Name Description Description: Name of a process. Process ID Description: ID of a process. Handle Count Description: Number of handles occupied by a process. CPU Usage (%) Description: CPU usage of a process. Memory Usage (MB) Description: Memory usage of a process. The memory includes the virtual memory and physical memory. Thread Number Description: Number of threads generated by a process.
Related Tasks
Monitoring the Process Status of the Nastar Server Monitoring the Process Status of the Nastar Server
Parameters for Monitoring the Hard Disk Status of the Nastar Server
This topic describes the parameters in the query results on the Hard Disk Monitor tab. When monitoring the hard disk status of the Nastar server, you need to set these parameters.
Parameters
Parameter File System Description Description: Hard disk partitions and their paths. Total Size (MB) Description: Total size of a specified partition. It equals to the sum of Used Size and Free Size. Used Size (MB) Description: Size of the used space of a specified partition. Free Size (MB) Description: Size of the remaining space of a specified partition.
Issue 01 (2013-07-15)
2527
6 System Management
Status
Description: State of a specified partition: Normal or Abnormal. If the hard disk usage is equal to or larger than the threshold, the state is Abnormal.
Related Tasks
Monitoring the Disk Status of the Nastar Server Monitoring the Disk Status of the Nastar Server
Issue 01 (2013-07-15)
2528
6 System Management
Parameter Status
Description Description: Database state: Normal or Abnormal. If the database usage is equal to or larger than the threshold, the state is Abnormal.
Parameters
Parameter Server Name Description Description: Name of the Nastar server. Server Status Description: State of the Nastar server: Active or Standby. OS Description: Operating system of the server. Total Physical Memory (MB) Description: Total capacity of the physical memory on the server. Free Physical Memory (MB) Description: Remaining capacity of the physical memory on the server. Total Swap Memory (MB) Description: Total virtual memory space of the Nastar server when the server runs the Solaris or Linux OS. Free Swap Memory (MB) Description: Remaining virtual memory space of the Nastar server when the server runs the Solaris or Linux OS. CPU Usage (%) Description: Usage of the CPU. Memory Usage (%) Description: Usage of the memory, including the physical memory and virtual memory.
Issue 01 (2013-07-15)
2529
6 System Management
Related Tasks
Monitoring the Status of the Nastar Server Monitoring the Status of the Nastar Server
Parameters
Parameter Component Description Description: Component name of the Nastar server. Version Description: Component version of the Nastar server. Description Description: Component description of the Nastar server.
Related Tasks
Viewing the Component Information of the Nastar Server Viewing the Component Information of the Nastar Server
Issue 01 (2013-07-15)
2530
6 System Management
Parameters
Parameter Server Monitor Parameter Settings Number of consecutive CPU overloads (10-400) Description Description: l If the CPU usage sampled each time is larger than the generation threshold, it means that the CPU is consecutively overloaded. When the number of consecutive overload times reaches the specified value, the monitor status is abnormal (the icon is displayed in red). l If the CPU usage sampled at a time is smaller than the clearance threshold, the monitor status returns to normal (the icon is displayed in green). Server status refresh interval (2-60 seconds) Description: Refresh interval of server monitoring, that is, the CPU usage is sampled every x seconds. Description: Set the generation threshold and the clearance threshold of high CPU usage of the xSAU. Value: Value range: 2-60 Default value: 30 The system does not support modifying the parameter. Value: Value range of usage: 1-99. Default value: 70. Value range of offset: 1-99. Default value: 70. Setting Value: Value range: 10-400 Default value: 40
Issue 01 (2013-07-15)
2531
6 System Management
Description Set the generation threshold and the clearance threshold of high memory usage of the xSAU. l When the Memory usage is more than Generation Threshold, the monitor status is abnormal (the icon is displayed in red). l When the Memory usage is less than Clearance Threshold, the monitor status is normal (the icon is displayed in green).
Setting Value: Value range of usage: 1-99. Default value: 70. Value range of offset: 1-99. Default value: 70.
Parameters for Setting the Hard Disk Monitoring Thresholds of the xSAU
This topic describes the parameters of hard disk monitoring. When setting the hard disk monitoring thresholds of the server, you need to set these parameters.
Parameters
Parameter Disk Monitor Parameter Settings Hard disk status refresh interval (30 seconds) Description Description: Refresh interval of hard disk monitoring. Setting Value: Value range: None Default value: 30 The system does not support modifying the parameter.
Issue 01 (2013-07-15)
2532
6 System Management
Description Description: Set the generation threshold and the clearance threshold of high disk usage of the xSAU.
Setting Setting method: Click + to expand Default value setting. Set the default thresholds of high hard disk usage in different severities. Value: Value range: 1-99 Default value of Generation Threshold: l Major: 60 Default value of Clearance Threshold: l Major: 60
Parameters
Parameter Database Monitor Parameter Settings Database status refresh interval (30 seconds) Description Description: Interval of database refreshing. Setting Value: Value range: None Default value: 30 The system does not support modifying the parameter.
Issue 01 (2013-07-15)
2533
6 System Management
Description Description: Set the generation threshold and the clearance threshold of high database usage of the xSAU.
Setting Setting method: Click DB usage (%). Set the default thresholds of database usage in different severities. Value: Value range: 1-100 Default value: l Major: 90
Parameters
Parameter Service Name Description Description: Name of a service. Status Description: Status of a service. l If a service is normal, its status icon is displayed in green. l If a service is stopped or abnormal, its status displays -. Start Time Description: Time when a service is started. Server Name Description: Name of a server.
Issue 01 (2013-07-15)
2534
6 System Management
Parameters
Parameter Process Name Description Description: Name of a process. Process ID Description: ID of a process. CPU Usage (%) Description: CPU usage of a process. Memory Usage (MB) Description: Memory usage of a process. The memory includes the virtual memory and physical memory.
Parameters
Parameter File System Description Description: Hard disk partitions and their paths. Total Size (MB) Description: Total size of a specified partition. It equals to the sum of Used Size and Free Size. Used Size (MB) Description: Size of the used space of a specified partition. Free Size (MB) Description: Size of the remaining space of a specified partition. Usage (%) Description: Usage of a specified partition. Status Description: State of a specified partition: Normal or Abnormal. If the hard disk usage is equal to or larger than the threshold, the state is Abnormal.
Issue 01 (2013-07-15)
2535
6 System Management
Status
Description: Database state: Normal or Abnormal. If the database usage is equal to or larger than the threshold, the state is Abnormal.
Parameters
Parameter Server Name Description Description: Name or the IP address of the server.
Issue 01 (2013-07-15)
2536
6 System Management
OS
Description: Total virtual memory space of the server when the server runs the Solaris or Linux OS.
Description: Remaining virtual memory space of the server when the server runs the Solaris or Linux OS.
Description: Usage of the memory, including the physical memory and virtual memory.
Issue 01 (2013-07-15)
2537
6 System Management
Issue 01 (2013-07-15)
2538
6 System Management
l l
Only users in the administrator group can manage the system timing tasks. Non-administrators with Analysis Task Management permission can view scheduled tasks. The system timing tasks cannot be copied or deleted. Only some parameters of the system timing tasks can be modified.
Start Time
Issue 01 (2013-07-15)
2539
6 System Management
Parameter Period
Description l Interval between periodic tasks. It has two enlistments: unit and duration. l The period can be represented in either of the following units: minutes, hours, days, weeks, months. Second is not supported. The supported units of Period vary according to the task type. l The value range for period should be as follows: Minute (1- 366 x 24 x 60), Hour (1 - 366 x 24), Day (1 - 366), Week (1 - 52), Month (1 - 12).
Run Times
Indicates execution times of a periodic task. The execution times range from 0 to 65535. The value 0 indicates no limit.
NOTE
Assume that the scheduling parameters of the entire network NE backup task are: l l l l Execution type = Periodicity Start time = 21/10/2006 09:07:28 Execution period = 1 day Period execution times = 0
The preceding information indicates that the system executes the entire network NE backup task at 09:07:28 every day from 09:07:28 on Oct. 21, 2006.
Scheduling
Running
Suspended
as k
De
in let
ga
tim
t ing
Another Scheduling? No
Finished
Issue 01 (2013-07-15)
2540
6 System Management
State transition of a scheduled task is as follows: l l l A scheduled task is in the idle state after it is initially created. An idle task is changed to the running state after being scheduled. An idle task is changed to the suspended state after being suspended.
NOTE
Certain idle tasks such as dump tasks are not allowed to be suspended to ensure the proper running of the Nastar. In other word, these idle tasks are never in the suspended state.
l l l l
A running task is changed to the idle state after being canceled. A suspended task is changed to the idle state after being resumed. If a task need not be scheduled after being performed, it is in the finished state. If it needs to be scheduled again, it returns to the idle state. A finished one-time task can be scheduled manually again to enter the running state. A finished periodic task cannot be scheduled again.
When a timing task is in the idle, suspended or finished state, you can delete the user timing task. Users can delete only the tasks created by themselves. The admin user can delete the tasks created by all users.
Prerequisites
You have logged in to the Nastar client.
Procedure
Step 1 Choose Maintance > Task Management from the main menu. Step 2 In the Task Management window perform different operations according to different customized requirement. Customized Requirement Operation
Customize the navigation tree 1. Right-click in the navigation tree and choose Filter Type from the shortcut menu. The Filter Type dialog box is displayed. 2. Select the timing task type to be displayed. By default, all the timing task types that the current user is authorized to browse are displayed.
Issue 01 (2013-07-15)
2541
6 System Management
Operation 1. Right-click the task list and select Filter Task. The Filter Task dialog box is displayed. 2. Set the Creator, Category, Task State, and Last Execution Result as the filtering conditions. For detailed parameter description, refer to Parameters for Setting Task Filter Conditions.
Prerequisites
You have logged in to the Nastar client successfully.
Context
Timing tasks are classified into System Timing Tasks and User Timing Task.
Procedure
Step 1 Choose Maintance > Task Management from the main menu. Step 2 In the Task Management window, modify the attributes of a timing task. l Select a task from the task list, and then click Attribute. In the Attribute dialog box, modify common and extended parameters. l Double-click a task in the task list. In the displayed Attribute dialog box, modify common and extended parameters.
NOTE
6 System Management
Prerequisites
You have logged in to the Nastar client.
Context
Only idle tasks can be scheduled.
Procedure
Step 1 Choose Maintance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree. Step 3 Suspend one or more idle tasks with one of the following methods: l Manual suspending Select one or more idle tasks in the task list. Right-click the task and select Suspend. In the Confirm dialog box, click Yes.
NOTE
If the Suspend menu item is not contained in the shortcut menu of a scheduled task, this task cannot be suspended.
l Automatic suspending Select a idle task in the task list. Right-click the task and select Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Suspend Time and then specify the time. Click OK.
NOTE
If the Timely Suspend/Resume menu item is not contained in the shortcut menu of a scheduled task, this task cannot be suspended.
For details of setting an automatic suspend time, refer to Parameters for Setting the Timely Suspend and Resume of a Timing Task. After the tasks are suspended, the Nastar does not schedule them until they are restored to the idle state. ----End
Prerequisites
l l You have logged in to the Nastar client. At least one suspended timing task exists.
Context
Only idle tasks can be scheduled.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2543
6 System Management
Procedure
Step 1 Choose Maintance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree. Step 3 Resume the suspended task with one of the following methods: l Manual resuming Select one or more suspended tasks in the task list in the right pane. Right-click the task and select Resume. In the Confirm dialog box, click Yes. l Automatic resuming Select a suspended task in the task list in the right pane. Right-click the task and select Timely Suspend/Resume. In the Timely Suspend/Resume dialog box, select Resume Time and then specify the time. Click OK. ----End
Prerequisites
l l You have logged in to the Nastar client. At least one Running timing task exists.
Context
A user in the common user group can cancel only the tasks created by himself. A admin can cancel the timing tasks created by all users.
Procedure
Step 1 Choose Maintance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree. Step 3 Select one or more running tasks in the task list in the right pane. Right-click the task and select Cancel. Step 4 In the Confirm dialog box, click Yes. Then the status of the task is changed from running to idle. ----End
Issue 01 (2013-07-15)
2544
6 System Management
Prerequisites
l l You have logged in to the Nastar client. At least one timing task exists.
Procedure
Step 1 Choose Maintance > Task Management from the main menu. Step 2 In the Task Management window, select Task Type in the navigation tree.
NOTE
l The task list area on the right displays the information about the tasks that can be viewed by the current user. l If you want to view the common parameters and extended parameters of each task, go to Step 3. l Part of periodic tasks support the function of downloading the log file of task execution results from the server. The downloaded log file is saved to the client. Thus, the user can view the history execution results of periodic tasks at any time: 1. Select the tasks that support log file download, and then click Save Log. 2. In the Selecting the Logs to Be Saved dialog box, select the log file to be saved, and then click OK. 3. In the Select Folder dialog box, select the path for saving the log file, and then click Select.
Step 3 Double click a task, or select a task and click Attribute. The Attribute dialog box is displayed. In the Common Parameter tab and Extended Parameter tab, you can view the task details.
NOTE
l If Status of a task is Finished, you can view the task information only. l If Status of a task is Idle, Suspended, or Running, you can modify the task details in the Attribute dialog box.
----End
Prerequisites
l l You have logged in to the Nastar client. At least one scheduled task exists.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2545
6 System Management
Step 2 In the navigation tree, select the task whose progress you want to view. In the Progress column of the task list on the right, you can view the task execution information. ----End
Prerequisites
l l You have logged in to the Nastar client. At least one scheduled task exists.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Select Task Type in the navigation tree. l View the execution conditions in the Last Execution Result column in the task list in the right pane. l You can check the result details in the Result Information area. ----End
Issue 01 (2013-07-15)
2546
6 System Management
Table 6-42 Description of the Timing Task Management interface No. 1 2 Name Navigation tree Task result information panel Description You can precisely locate a timing task through the navigation tree. After a task is carried out, the task result is displayed. On the task result information panel, you can browse the result of the task last carried out. Only the result of the currently selected task is displayed on the task result information panel. If multiple tasks are selected in the task list, only the result of the firstly selected task is displayed. The buttons used for carrying out integrated task management are available on the button panel. l l l l : Create a user timing task. For details, see Creating a User Timing Task. : View or modify the attributes of a specified task. For details, see Modifying a Timing Task. : Delete the specified user timing task. For details, see Deleting Timing Tasks. : Quickly create a multi-instance user timing task whose parameters are similar to those of the specified task. For details, see Creating a User Timing Task. : Refresh the status of a timing task. : Set the task filter conditions. For details, see Parameters for Setting Task Filter Conditions.
2547
Button panel
l l
Issue 01 (2013-07-15)
6 System Management
No. 4
Description You can browse the timing tasks that exist on the server side and the detailed information. In the task list, different colors indicate different states of tasks. l gray: complete l orange: suspended l blue: active l white: idle The selected color of the task is darker than the previous color of the task.
Parameters
Parameter User Name Current User Description Description: Indicates the user that operates the client. Other Users Description: Indicates other users except the current user. Catego ry User Task Description: Indicates the task created by users. System Task Description: Indicates the task created by OMC during the system installation or upgrade. Task State Idle Description: Indicates that the task waits for being performed by the system. Running Description: Indicates that the task is being performed by the system. Suspended Description: The task is not ready to be scheduled. Finished Description: Indicates that the task is completed by the system. Last Executi Successful Description: Indicates that the task is successfully carried out.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2548
Issue 01 (2013-07-15)
6 System Management
Description Description: Indicates that the task is being processed by the system.
Description: Indicates that the task is partly successfully carried out. Description: Indicates that the task fails to carry out.
Description: Indicates that the task misses the previous performed time. If the server is not running properly or the task is suspended before the execution, the task may miss the previous execution. Description: Indicates that the previous execution result in the server is lost caused by improper service or sudden power cut. Thus, after recovery, the previous execution result cannot be determined.
Unknown
Unexecuted
Parameters for Setting the Timely Suspend and Resume of a Timing Task
This topic describes the parameters of auto-suspend time and auto-resume time for timing tasks.
Parameters
Name Suspend Time Description Description: At the time specified by the user, the system suspends the idle timing task that is not executed to delay the task dispatch. If the timing task is not in the idle state at the specified time, the suspension fails. Settings Setting method: You can set the value manually. Alternatively, you can click and select the time from the time select panel. The time format is MM/DD/YYYY HH:MM:SS. l MM stands for the month. l DD stands for the date. l yyyy stands for the year. l HH stands for the hour. l MM stands for the minute. l SS stands for the second.
Issue 01 (2013-07-15)
2549
6 System Management
Description Description: At the specified time, the system resumes a suspended task and then the task is in the idle state and wait to be dispatched. If the timing task is not in the suspended state at the specified time, the suspension fails.
Settings Setting method: For details on how to set the resume time, refer to the description of the Suspend Time parameter.
Parameters
Task Name Operation Log Dump Security Log Dump System Log Dump Description The system periodically dump the data that reaches the specified Save Days from the database. Through database capacity management tasks, the database capability is maintained in a proper range to avoid database faults caused by large amount of data. Parameters For details on the parameters, see Parameters for Setting Nastar Log Timing Dump.
Parameters
Task Name Operation Log Export Security Log Export Description Various types of data can be periodically exported to a specified directory on the server. Through this function, you can save the data outside the system. The exported data is still saved in the database. Parameters For details on the parameters, see Parameters for Setting Nastar Log Timing Export.
Issue 01 (2013-07-15)
2550
6 System Management
Description
Parameters
Parameters
Parameter Task Name Description Description: Refers to the name of a timing task Value Range Value: l A maximum of 60 characters l Unique and not null l Case sensitive Run Type Once Description: If you select this option, the system runs the created task once at the defined time point. Period Description: If you select this option, the system runs the created task periodically. Start time Description: This parameter sets the time for starting a task. The start time should be later than the time displayed on the server. Value: If you have selected Run At Once, the Start Time parameter is invalid. The task is performed immediately after the related settings are complete. -
Issue 01 (2013-07-15)
2551
6 System Management
Description Description: Interval between periodic tasks. It has two enlistments: unit and duration.
Value Range Value: l The period can be represented in either of the following units: minutes, hours, days, weeks, months. The period, however, cannot be represented in seconds. l The value range for period should be as follows: Minute (1366 x 24 x 60), Hour (1 - 366 x 24), Day (1 - 366), Week (1 - 52), Month (1 - 12).
Execution Times
Description: This parameter indicates the times that a periodic task is executed.
Value: 0-65535
NOTE 0 indicates that the number of times for executing periodic tasks is not restricted.
Parameter Description
Parameter Backup File Path Backup Medium Description Indicates the save path of backup files. By default, the path is /export/ home/backup/omc. Indicates the backup medium of the backup files.
6 System Management
Context
l In Nastar V600R008 and earlier versions, when the filter algorithms, rules, or system configurations are modified, you need to upgrade the SAU. The upgrade takes a long time and reduces customer satisfaction. In Nastar V600R009, when the filter algorithms, rules, or system configurations are modified, you can deliver an adapter package to replace the algorithm and rule files on the Nastar and SAU. This decreases the upgrade times, increases problem-solving efficiency, and improves customer satisfaction. In other scenarios, you still need to upgrade software to implement the adaption. In Nastar V600R010 and V600R011, when the service types, application types, OS types, or OS versions are modified, you can deliver an adapter package to replace the algorithm and rule files on the Nastar, eSAU, and SAU. This decreases the upgrade times. In other scenarios, you still need to upgrade software to implement the adaption.
Prerequisites
l l You have permission to deliver adapter packages. You have obtained an adapter package and copied it to a local directory. The adapter package is delivered with the Nastar. You can obtain it from Software Center > Controlled Tool (Mini-tool Software) > Wireless Product Line > Wireless Performance & RNP & RNO > GENEX Nastar > Nastar Tools at http:// support.huawei.com.
CAUTION
Before delivering an adapter package, check the application scope (RAT for example) and version mapping of the adapter package according to the version-specific Readme.txt.
Context
The adapter package is named in the format of Adapter_V600R010C00_yyyy+mm+dd.zip. For example, Adapter_V600R010C00_20120612.zip. After the adapter package is delivered successfully, the Nastar automatically saves this package to a specific directory on the Nastar server for future rollback. By default, the Nastar saves only the latest 10 adapter packages.
Procedure
Step 1 Choose System > Adapter Package Management. The Adapter Package Management window is displayed.
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2553
6 System Management
Step 2 Click
Step 3 Click ... on the right of Adapter Package to select an adapter package from the local directory. Step 4 Click OK. In the adapter package list, the values in the Status column for the Nastar, eSAU, and SAU are Delivering. l If the values in the Status column change to Succeed, the adapter package has been delivered successfully.
NOTE
The new adapter package takes effect one hour after the delivery. The Nastar processes analysis data according to the new rules one hour after the delivery.
l If the values in the Status column change to Failed, the adapter package failed to be delivered. The delivery failure may be caused by network disconnection, device faults, or incorrect file format. For detailed information, see Details in the Logs area. Click package. ----End after locating the reason for the failure and resolving, retry to send the adapter
Prerequisites
l l You have permission to roll back adapter packages. The adapter package has been successfully delivered.
Procedure
Step 1 Choose System > Adapter Package Management. The Adapter Package Management window is displayed. Step 2 Click . The Roll Back dialog box is displayed.
Step 3 In Adapter Package, select the desired adapter package. Step 4 Specify Roll Back Reason. Step 5 Click OK. In the adapter package list, the values in the Status column for the Nastar, eSAU, and SAU are Rolling Back. l If the values in the Status column change to Succeed, the adapter package has been rolled back successfully.
NOTE
The rollback adapter package takes effect one hour after the rollback. The Nastar processes analysis data according to the rollback algorithms and rules one hour after the rollback.
Issue 01 (2013-07-15)
2554
6 System Management
l If the values in the Status column change to Failed, the adapter package failed to be rolled back. The rollback failure may be caused by network disconnection, device faults, or incorrect file format. For detailed information, see Details in the Logs area. Click package. ----End after locating the reason for the failure and resolving, retry to rollback the adapter
Prerequisites
You have permission to view log information about adapter packages.
Procedure
Step 1 Choose System > Adapter Package Management. The Adapter Package Management window is displayed. Step 2 View log information in the Log Info area. Table 6-43 describes the log parameters. Table 6-43 Log parameters Parameter Time Log Level System Type Adapter Package Type SAU IP Result Details Description Time when a delivery or rollback task is completed. Log level. The value can be Minor or Major. You only need to focus on logs of the Major level. Name of the delivery destination such as Nastar, eSAU, and SAU. Type of a delivered file. For example, a terminal information file. IP address of the delivery destination such as Nastar, eSAU, and SAU. Operation result. The value can be Succeed or Failed. Detailed information about the operation result.
l Set Function, Severity, and Condition, type keywords, and click Filter. The Nastar will display the logs that meet the filter criteria. l By default, the Log Info area displays the latest 100 logs. To view more logs, click Show All. The Nastar displays the Log Manager window, showing the logs generated in the last seven days. l To save logs, click Show All. In the displayed Log Manager window, right-click the log list and choose Save As from the shortcut menu. ----End
Issue 01 (2013-07-15) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2555
6 System Management
Prerequisites
l l You have subscribed to analysis data. You are authorized to query analysis data.
Procedure
Step 1 Choose Maintenance > Data Maintenance Management. The Data Maintenance Management window is displayed. Step 2 In the navigation tree of Data Maintenance Management window, choose Data Type > Analysis sort > *** Data. For the analysis theme of the different type, you need to query the data of the different type. *** indicates the name of analysis theme to be analyzed. 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. For the analysis data on the RAN side, you can query the data of day-level. For the analysis data on the CN side, you can query the data of day-level and month-level. 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. 4.
Select specific nodes from the NE object navigation tree. Optional: Select the VIP group to be queried from the VIP group navigation tree. This step is only used for querying the *** VIP analysis data. *** refers to the network system.
Step 4 Click Query in the bottom left corner of the window. You can check and ensure that the configuration data is imported into the database.
Issue 01 (2013-07-15)
2556
6 System Management
l The Overview tab page displays NEs with data and the data time range (start time and end time) of the NEs. The start time and the end time are the actual time when the data is generated, but not the time when 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 not available. If the analysis data is subscribed, and the result is normal, but no relevant data is displayed, contact Huawei technical support personnel. ----End
Follow-up Procedure
l l You can right-click in the right pane and then choose Save As from the shortcut menu to save the current query results as a .csv, .xls, or .xlsx file. View information about the subscription in the Log Info area. Table 6-44 lists the parameters. Table 6-44 Log parameters Parameter Date/Time Level Action Type Action Result OSS Name NE Name Switch Name Details Description Time when a task is complete. Level of the log, including Minor and Major. You are advised to focus on the Major level log information. Action type, including open and close. Action result. The value can be Succeed or Failure. The name of OSS which the subscribed NEs belong to. The name of the subscribed NEs. Switch type. Detailed information about the operation result.
Select Function, Severity, Condition, and type the keyword. Click Filter to filter the log information. It displays the latest 100 log information by default in the Log Info area. Click Show All, the Log Manager window is opened. You can view all of the log information generated within seven days. Click Show All, the Log Manager window is opened. Right-click the log list and choose Save As from the shortcut menu to save the log information.
Issue 01 (2013-07-15)
2557
6 System Management
Prerequisites
You are authorized to set the storage duration for analysis data.
Procedure
Step 1 Choose Maintenance > Data Maintenance Management. The Data Maintenance Management window is displayed. Step 2 In the navigation tree of Data Maintenance Management window, choose Data Type > Analysis sort > *** Data. 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 Setting. 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 Storage Period Setting.
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.
Follow-up Procedure
l View information about the subscription in the Log Info area. Table 6-45 lists the parameters.
Issue 01 (2013-07-15)
2558
6 System Management
Table 6-45 Log parameters Parameter Date/Time Level Action Type Action Result OSS Name NE Name Switch Name Details Description Time when a task is complete. Level of the log, including Minor and Major. You are advised to focus on the Major level log information. Action type, including open and close. Action result. The value can be Succeed or Failure. The name of OSS which the subscribed NEs belong to. The name of the subscribed NEs. Switch type. Detailed information about the operation result.
Select Function, Severity, Condition, and type the keyword. Click Filter to filter the log information. It displays the latest 100 log information by default in the Log Info area. Click Show All, the Log Manager window is opened. You can view all of the log information generated within seven days. Click Show All, the Log Manager window is opened. Right-click the log list and choose Save As from the shortcut menu to save the log information.
Issue 01 (2013-07-15)
2559