nastar v600r008 product description(gsmumtslte)

Nastar V600R008 Product Description (GSM&UMTS&LTE)

Issue V2.3

Date 2011-07-01

HUAWEI TECHNOLOGIES CO., LTD.

Issue V2.3(2011-07-01) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

of 46

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

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the commercial contract made between Huawei and the customer. All or partial products, services and features described in this document may not be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

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

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

Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Nastar Product Description (GSM&UMTS&LTE)


of 46

Contents

1 Introduction ......................................................................................................................... 4 1.1 Positioning ........................................................................................................................................... 4 1.2 Benefits ................................................................................................................................................ 6 1.3 Product Functions................................................................................................................................. 7

2 Architecture ........................................................................................................................ 11 2.1 Hardware Architecture ....................................................................................................................... 11 2.2 Software Architecture ......................................................................................................................... 13

3 Products and Application Scenarios ............................................................................. 17 3.1 Overview ............................................................................................................................................ 17 3.2 Application Scenarios ......................................................................................................................... 17

4 Configurations ................................................................................................................... 18 4.1 Overview ............................................................................................................................................ 18 4.2 Configuration Requirements of Nastar ............................................................................................... 18 4.3 Configuration Requirements of SAU ................................................................................................. 21

5 Operation and Maintenance ........................................................................................... 22 5.1 Overview ............................................................................................................................................ 22 5.2 Functions ............................................................................................................................................ 22

6 Technical Specifications .................................................................................................. 23 6.1 Management Capacity of the Nastar .................................................................................................. 23 6.2 Bandwidth Requirement of the Nastar ............................................................................................... 25 6.3 Task Management Capacity of the Nastar .......................................................................................... 27 6.4 Storage Specifications of the Nastar .................................................................................................. 41 6.5 Specifications of the SAU .................................................................................................................. 43 6.6 Restrictions on the Clients Connected to the Nastar .......................................................................... 44

7 Acronyms and Abbreviations ......................................................................................... 45



of 46

1 Introduction

1.1 Positioning This document is released with the iManager Nastar V600R008 (GSM/UMTS/LTE).

The iManager Nastar (hereinafter referred to as Nastar) is a network optimization system used for the analysis and troubleshooting of quality-related problems on the wireless network, such as GSM/GPRS/EDGE, CDMA 1X/EV-DO, UMTS/HSUPA/HSDPA, TD-SCDMA, and LTE. This system supports multi-user operations and different types of wireless network performance analysis methods. It provides a basic supporting platform for thorough wireless network analysis and troubleshooting.

Background The traditional network analysis system checks the running status of networks by monitoring alarm information and analyzing performance reports. It analyzes networks on the basis of the alarm information and performance measurement statistics on network elements (NEs). The alarm information and measurement statistics can reflect the running status of networks from the perspective of NEs, but they cannot provide evidences for expert and thorough wireless network analysis and optimization.

The Nastar obtains the data containing the characteristics of the wireless network and analyzes the data. The data includes the measurement reports (MRs) of radio links, pilot frequency measurement strength indicator, neighboring cell measurement data, uplink interference data, and user call event records. By analyzing the data, the Nastar helps to locate and analyze network problems and provides auxiliary solutions to problems.

Position of the Nastar on the Network The Nastar is deployed on the distributed network in Client/Server mode. It is connected to the element management system (EMS).

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



of 46

Figure 1-1 Position of the Nastar on the GSM, UMTS, CDMA , TD-SCDMA and LTE network

The communication between the functional units on the network is based on the TCP/IP protocol. The Nastar server and the EMS (for example, the 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 each functional unit on the network.

Table 1-1 Description of the functional unit on the network

Functional Unit Description

Nastar One of the multi-user telecommunication platforms developed by Huawei. It implements performance analyses such as coverage analysis, frequency analysis, neighboring cell analysis, uplink interference analysis, and user complaint analysis support for the radio network.

Huawei M2000 A uniform management platform of Huawei mobile network. It manages the mobile NEs manufactured by Huawei. Connecting to the Nastar, it provides performance data, configuration data, and preprocessed MR data for the Nastar through FTP.



of 46

Functional Unit Description

SAU Service Aware Unit. It implements the communication between operation and maintenance (OM) terminals and other boards of the base station controller. The main functions of the SAU are as follows:

Downloading data from the base station controller Preprocessing data and saving the preprocessed data Uploading the preprocessed data

For the base station controller, an extra SAU board is required for preprocessing the data required by the Nastar on the GSM, UMTS, CDMA, and TD-SCDMA networks. For the OSS, an SAU server is required by the Nastar on the LTE network.

Wireless network Multiple wireless networks including GSM, UMTS, CDMA, TD-SCDMA, and LTE networks.

MME Mobile management entity. The MME provides certain analysis data for the SAU LTE in the LTE network.

1.2 Benefits The Nastar provides the following benefits:

Supporting intelligent analysis of a large amount of data, thus reducing the operation expenditure (OPEX)

Traditional drive tests (DTs) and call quality tests (CQTs) cannot obtain comprehensive data because performing tests on the entire network is not feasible. The Nastar obtains a large amount of data generated during the calls of subscribers from the network, analyzes the data with configuration data and engineering parameters based on mature performance algorithms, supports correlation analysis, and provides multiple optimization analysis themes including coverage analysis, interference analysis, and neighboring cell analysis, and analyzes all the network problems. In this way, the Nastar can reduce the costs of DTs and manual analysis, reduce the OPEX, and improve the accuracy of problem analysis.

Supporting in-depth performance optimization based on subscriber experience, thus improving subscriber satisfaction

The traditional KPI monitoring can provide only the overall situation of the entire network instead of the detailed information about subscribers and subscriber groups, thus failing to reflect the actual subscriber experience. The Nastar obtains user call event records, which can reflect the quality of radio links and actual experience of subscribers, from the network and detects and thoroughly analyzes the network problems that affect subscriber experience. In this way, the Nastar overcomes the defects of the traditional KPI monitoring, and thus significantly improves subscriber experience.

Supporting multiple network systems, thus ensuring smooth network evolution



of 46

The Nastar supports multiple network systems such as GSM/GPRS/EDGE, CDMA/EV-DO, UMTS/HSPA, TD-SCDMA, and LTE network systems. It also supports the interoperations between different network systems, such as GSM/UMTS neighboring cell analysis and GSM/TD-SCDMA neighboring cell analysis. Thus, it ensures smooth network evolution.

Providing an end-to-end and automatic optimization process, thus improving the OM efficiency The Nastar can automatically collect performance data, import the data into the database, and analyze the data. Generally, users can perform certain settings so that the Nastar conducts service analysis during the night. Users only need to check and adjust the analysis result based on experience. After that, users are allowed to export the adjusted analysis result as a file that adapts to the CME and import the file to the CME so that the modified analysis result is delivered to NEs. In this way, the Nastar implements the end-to-end optimization, and thus improves the OM efficiency.

1.3 Product Functions The following lists the analysis functions provided by the Nastar for the GSM, UMTS and LTE systems.

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

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

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

Frequency analysis This function is performed to evaluate the impact of GSM frequency planning and analyze the cells and Absolute Radio Frequency Channel Numbers (ARFCNs) experiencing severe interference on the current network. If cells and ARFCNs experiencing server interference are detected during DT analysis and traffic



of 46

analysis, this function can be performed to find the frequencies that can be replaced. Therefore, network interference is decreased and network QoS is improved. Based on the interference traffic sequence of the available ARFCNs in an expansion cell, this function can also be used to find out the optimal frequencies to be added to the expansion cell. This is a basis for preparing a frequency plan for the network.

Complaint analysis support Whenever mobile subscribers encounter network-related 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, thus improving user satisfaction.

VIP analysis This function is performed to filter the call records of VIP subscribers from the user call event records of the entire network and obtain the KPIs of the voice and data services of VIP subscribers. The KPIs include call drop rate, call setup duration, and forward and reverse data rate. By monitoring the QoS 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 QoS of VIP subscribers.

Pilot pollution analysis The network systems based on the code division multiple access technology are self-interfered systems, in which interference seriously affects the performance and capacity of the network 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, thus 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.

Cell performance analysis Through the cell performance analysis, the Nastar obtains the data of abnormal calls in problematic cells, displays the data in comprehensive presentation modes, analyzes the causes of abnormal calls, and thus helps network OM personnel locate cell problems. In addition, the Nastar analyzes cell performance faults based on cell service alarms in the LTE network.

Terminal performance 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.

Cell fault analysis Usually, LTE cell fault analysis is triggered by the KPI service alarm reported by an NE. After receiving a KPI service alarm, the Nastar queries the alarm data,



of 46

performance data, and call records from the relevant NE, analyzes the cause of the alarm, and helps network O&M engineers analyze and locate the network fault.


of 46

2 Architecture

2.1 Hardware Architecture This section describes the hardware architecture of the Nastar. The Nastar is composed of a server and multiple clients. Currently, all the services are deployed on one server, and multiple clients can be deployed in the Nastar. The Nastar provides three hardware solutions based on network scales: the PC server DL580, the PC server DL785 and the PC server DL980. The four hardware solutions support the Citrix networking mode.

Figure 2-1 shows the hardware architecture when the Nastar uses the HP PC server DL580.

Figure 2-1 Hardware architecture of the Nastar when the HP PC server DL580 is adopted



of 46

Figure 2-2 and Figure 2-3 show the hardware architecture when the Nastar uses the HP PC server DL785.

Figure 2-2 Hardware architecture of the Nastar when the HP PC server DL785 is adopted (standard configuration)

Figure 2-3 Hardware architecture of the Nastar when the HP PC server DL785 is adopted (the SAN is used)

Figure 2-4 shows the hardware architecture when the Nastar uses the HP PC server DL980.



of 46

Figure 2-4 Hardware architecture of the Nastar when the HP PC server DL980 is adopted

2.2 Software Architecture

Overview As shown in Figure 2-5, the Nastar software consists of two parts:

Server software Client software

Figure 2-5 Software architecture of the Nastar

Client Software

Server Software

Database

OSS/OSS Data Configuration Tool

FTP

CORBA

Server Software Figure 2-6 shows the modules of the Nastar server software.



of 46

Figure 2-6 Modules of the server software

Task Management Subsystem

Database

Data Processing Subsystem

Service Analysis

Subsystem

Client Software

CORBA Bus

The server software of the Nastar consists of multiple function modules. These modules communicate with each other and the corresponding modules of the client software through the CORBA software bus. In addition, these modules access the database of the Nastar server through the database interface to perform operations on the database.

Table 2-1 describes the function modules of the server software.

Table 2-1 Description of the function modules of the server software

Module Name Description

Task management subsystem

Providing the functions of browsing and carrying out performance analysis tasks

Implementing the creation, management, and monitoring of tasks Managing and maintaining the tasks in the system

Data processing subsystem

Providing the functions of collecting, parsing, importing, and preprocessing data and generating the data that is suitable for service analysis

Providing the functions of managing data, such as deleting and backing up original data

Providing the functions of managing, importing, and exporting the results of performance analysis

Service analysis subsystem

Providing the function of performance service analysis and displaying performance analysis results on the client

Client Software The Nastar client provides the graphical user interface (GUI) for Nastar operators to analyze the performance of the radio network.



of 46

The modules corresponding to the task management subsystem and service analysis subsystem are included in the client software. The two modules on the client provide operation access to these two subsystems.


of 46

3 Products and Application Scenarios

3.1 Overview The Nastar, which collects data from Huawei M2000 for analyzing the radio network performance, can be used at various stages such as radio network planning, construction, optimization, and routine maintenance. It ensures the QoS of the radio network provided for VIP subscribers, and thus improving the competitiveness of the mobile operators.

3.2 Application Scenarios Network planning and optimization

The Nastar verifies optimization results based on routine measurement data, and thus provides guidelines for new optimization schemes. The Nastar analyzes neighboring cells and frequencies, and thus provides adjustment suggestions to improve network quality. It analyzes network coverage, and thus helps to analyze and locate the network problems. It also analyzes uplink interference, and thus helps to collect interference data in the network, detect and eliminate intra-network and extra-network interference, and ensure network quality.

Network operation The Nastar analyzes subscriber complaints, and thus facilitates network problem handling. It also analyzes VIP KPIs, and thus helps to monitor the network quality of VIP subscribers and improves subscriber satisfaction.



of 46

4 Configurations

4.1 Overview All the services of the Nastar are deployed on one server, which is connected to multiple clients. The following sections describe the typical hardware and software configurations of the Nastar.

4.2 Configuration Requirements of Nastar

Hardware Configuration All the services of the Nastar are deployed on one server. Multiple Nastar clients can connect to the Nastar server at the same time. The following sections describe the typical hardware and software configuration of the Nastar.

HP Server (DL580) Table 4-1 describe the typical hardware configurations of the Nastar on the HP DL580 server.

Table 4-1 Typical hardware configuration of the Nastar used on small and medium-sized networks

Object Configuration Requirement

Nastar server Server type: HP DL580G7

CPU: 4 x 2.0GHz E7540 or above (six-core)

Memory: 8 x 4 GB

Hard disk: 8 x 300 GB (RAID 5)

Tape drive: HP LTO4

SAS card: 1

Integrated NIC (four ports)

Accessories: DVD

Nastar client Client type: a common PC

CPU: E5300 or above

Memory: 4 GB

Hard disk: 320 GB or above

Accessories: DVD-RW/ NIC/19 inch wide LCD



of 46

HP Server (DL785) Table 4-2 and Table 4-3describe the typical hardware configurations of the Nastar on the HP DL785 server.

Table 4-2 Typical hardware configuration of the Nastar used on large-sized networks


Nastar server Server type: HP DL785G6

CPU: 8 x 2.8GHz 8439 SE (six-core)

Memory: 16 x 4GB

Hard disk: 2 x 300 GB

S2600 Storage Array (12 x 450 GB) + D120S Disk Management Enclosure (12 x 450 GB)

Tape drive: HP LTO4

Integrated NIC (dual ports) + 1000M NIC (four ports)

1Port 8Gb Fibre HBA: 2

SAS card: 1

Accessories: DVD

Nastar client Client type: a common PC

CPU: E5300 or above

Memory: 4 GB

Hard disk: 320 GB or above

Accessories: DVD-RW/ NIC/19 inch wide LCD

Table 4-3 describes the requirements for the SAN network disk when the SAN is used.

Table 4-3 Requirements for the SAN network disk

Counter Requirement

I/O performance 5,000 IOPS or more

Bandwidth 4 GB or more

Delay 100 ms or less

HP Server (DL980) Table 4-4 describe the typical hardware configurations of the Nastar on the HP DL980 server.



of 46

Table 4-4 Typical hardware configuration of the Nastar (HP DL980)


Nastar server Server type: HP DL980G7 CPU: 8 x 2GHz E6540(six-core) Memory: 16 x 4GB Hard disk: 2 x 300 GB S2600 Storage Array (12 x 450 GB) + D120S Disk Management Enclosure (12 x 450 GB)

Tape drive: 1×HP LTO4 NIC: Integrated NIC (four ports)+ 1000M NIC (four ports) 1Port 8Gb Fibre HBA: 2 SAS card: 1 Accessories: DVD

Nastar client Client type: a common PC CPU: E5300 or above Memory: 4 GB Hard disk: 320 GB or above Accessories: DVD-RW/ NIC/19 inch wide LCD

Software Configuration Table 4-5 describes the typical software configuration of the Nastar server and client.

Table 4-5 Typical software configuration of the Nastar

Configuration Object

Configuration Item Configuration Requirement

Nastar server Operating system SUSE Linux10 SP3 (X86_64)

Database Oracle 11g

Nastar application software

Nastar V600R008 server software

Nastar client Operating system Windows 2000 Professional SP4 or a later version

Windows XP Professional SP1 or a later version

Windows 7 Professional 64bit

Nastar application software

Microsoft Office 2003 or a later version

Nastar V600R008 client software



of 46

4.3 Configuration Requirements of SAU

Hardware Configuration Table 4-6 and Table 4-7 describe the typical hardware configuration of the SAU.

Table 4-6 Typical hardware configuration of the SAU (GSM/UMTS)


Configuration Requirement

SAU Server type: Board CPU: 2 × Xeon 2130 MHz Memory: 2 GB Hard disk: 2 × 146 GB

Table 4-7 Typical hardware configuration of the SAU (LTE)


Configuration Requirement

SAU Server type: HP DL580G7

CPU: 4 x 2.0GHz E7540 or above (six-core)

Memory: 8 x 4 GB

Hard disk: 8 x 300 GB (RAID 5)

Integrated NIC (four ports)

Accessories: DVD

Software Configuration Table 4-8 and Table 4-9 describe the typical software configuration of the SAU.

Table 4-8 Typical software configuration of the SAU (GSM/UMTS)



SAU Operating system DOPRA Linux

Table 4-9 Typical software configuration of the SAU (LTE)



SAU Operating system SUSE Linux10 SP1 (64 bits)



of 46

5 Operation and Maintenance

5.1 Overview With the powerful backup restoration and well-developed system management functions, the Nastar can improve O&M efficiency greatly.

5.2 Functions

Comprehensive System Security Solution The Nastar provides comprehensive security hardening solutions for operating systems and databases. These solutions meet the security requirements for operating systems and databases. To enhance the security management feature, the Nastar provides the rights management, access control, and user monitoring functions. In addition, the OSS-related systems support single sign-on (SSO). With this feature, a user logs in once and gains access to all OSS-related systems without being prompted to log in again at each of them.

Powerful Backup Restoration Function With this function, users can set backup policies according to the actual situation and complete the data backup periodically through system backup tasks. When application data is corrupted or lost, users can restore the data by using the corresponding backup package. In addition, users can restore the data of the entire operating system by using the professional backup restoration tool provided by the Nastar.

Well-developed System Management Function To ensure the high-efficient running of the system, the Nastar provides the well-developed system management function, which enables users to set the operational parameters and monitor data of the system.



of 46

6 Technical Specifications

6.1 Management Capacity of the Nastar 6.1.1 Management Capacity of the Nastar (GSM)

Table 6-1 provides the management capacity of the Nastar on the GSM network.

Table 6-1 Management capacity of the Nastar (GSM)

Item Management Capacity

Number of carriers supported by the Nastar ≤ 100,000 (for HP DL785 server) ≤ 50,000 (for HP DL580 server) ≤ 100,000 (for HP DL980 server)

Number of cell groups supported by the Nastar

≤ 100 (for HP DL785 server) ≤ 100 (for HP DL580 server) ≤ 100 (for HP DL980 server)

6.1.2 Management Capacity of the Nastar (UMTS) Table 6-2 provides the management capacity of the Nastar on the UMTS network.

Table 6-2 Management capacity of the Nastar (UMTS)


Number of cells supported by the Nastar ≤ 100,000 (for HP DL785 server)

≤ 50,000 (for HP DL580 server)


Number of cell groups supported by the Nastar ≤ 100 (for HP DL785 server) ≤ 100 (for HP DL580 server) ≤ 100 (for HP DL980 server)



of 46

6.1.3 Management Capacity of the Nastar (GSM&UMTS) Table 6-3 provides the management capacity of the Nastar on the GSM and UMTS network.

Table 6-3 Management capacity of the Nastar (GSM&UMTS)


Number of TRXs supported by the Nastar ≤ 100,000 (for HP DL785 server)




6.1.4 Management Capacity of the Nastar (LTE) Table 6-4 provides the management capacity of the Nastar on the LTE network.

Table 6-4 Management capacity of the Nastar (LTE)






The management capacity of the Nastar on the LTE network is determined by the configuration of the SAU server.



of 46

6.1.5 Management Capacity of the Nastar (GSM&UMTS&LTE)

Table 6-5provides the management capacity of the Nastar on the GSM, UMTS and LTE network.

Table 6-5 Management capacity of the Nastar (GSM&UMTS&LTE)






6.2 Bandwidth Requirement of the Nastar 6.2.1 Bandwidth Requirement Between the Nastar Server and the Nastar Client/M2000

Table 6-6 describes the bandwidth requirement of the Nastar for ports.

Table 6-6 Bandwidth requirement of the Nastar for ports

Port Required Bandwidth

Between the Nastar server and the M2000 server

The required bandwidth is higher than 2 Mbit/s if the total number of TRXs or cells is smaller than or equal to 5,000 on the network.

The required bandwidth is higher than 10 Mbit/s if the total number of TRXs or cells is greater than 5,000 on the network.

The required bandwidth is higher than 2 Mbit/s for the LTE network.

Between the Nastar server and the Nastar client

The required bandwidth is higher than 10 Mbit/s.



of 46

The bandwidth requirement of the Nastar is controlled by the M2000. The bandwidth between each NE and the M2000 varies. For details, see the M2000 Product Description.

6.2.2 Additional Bandwidth Requirements of the Nastar Services for the M2000 Server

The additional bandwidth requirements of the Nastar services for the M2000 server vary according to the number of cells or frequencies under a single NE.

Table 6-7 describes the detailed requirements.

Table 6-7 Additional bandwidth requirements of the Nastar services for the M2000 server

Technology Number of Cells/Carriers Under a BSC/RNC Required Additional Bandwidth (kbit/s)

GSM Number of carriers < 360 64

360 <= Number of carriers <= 960 708

Number of carriers > 960 1856

UMTS Number of cells < 500 128

500 <= Number of cells <= 1500 768

Number of cells > 1500 2048

For the LTE network, only the command channel exists between the SAU and the M2000. Therefore, no additional bandwidth is required for data transmission. The requirements on the bandwidth between the SAU LTE and the eNodeB, however, are listed in Table 6-8.

Table 6-8 Requirements on the bandwidth between the SAU and the eNodeB

Number of NEs Required Physical Bandwidth

One eNodeB (serving three cells)

1.15 kbit/s

The requirements on the transmission bandwidth between the MME and the SAU server vary according to the number of eNodeBs managed by the MME. Table 6-9 lists the minimum bandwidth requirements for different NE configuration.

Table 6-9 Requirements on the bandwidth between the SAU server and the MME

BHCA Under One MME (Number of Cells)

Total Bandwidth Requirements of One MME (Mbit/s)

2,666,667 (10,000 cells) 21

266,667 (1,000 cells) 2.1



of 46

6.3 Task Management Capacity of the Nastar

6.3.1 Task Management Capacity of the Nastar (GSM)

GSM MR Analysis Table 6-10 describes the task management capacity for the GSM MR analysis of the Nastar.

Table 6-10 Task management capacity for the GSM MR analysis

Item Task Management Capacity

Execution Type One-time task Periodic task

Number of cells supported by one analysis task

≤ 1,000 cells

Number of concurrent tasks ≤ 5

Number of creating tasks ≤ 50

Number of E2E tasks by one OSS ≤ 200

Time range of analysis ≤ 7 days

Response time of task execution Negligible

During the initial installation of the Nastar, the measurement task required by the GSM MR

analysis needs to be registered on the M2000 manually. In later analysis, the measurement task need not be reregistered.

The Nastar server can run a maximum of five analysis tasks simultaneously. If only a certain type of theme analysis tasks are running on the Nastar, a maximum of five analysis tasks of this type can be executed simultaneously.

GSM Frequency Analysis Table 6-11 describes the task management capacity for the GSM frequency analysis of the Nastar.

Table 6-11 Task management capacity for the GSM frequency analysis


Execution Type One-time task


≤ 5,000 cells






of 46




The GSM frequency analysis and neighboring cell analysis use the same neighboring cell

measurement task. One GBSC supports only one neighboring cell measurement task at a time. For the GBSC of the version earlier than V900R011, if the BSC is not enabled with the

outgoing cell handover measurement function, a maximum of 200 cells can be registered on each BSC for the neighboring cell measurement task; if the BSC is enabled with the outgoing cell handover measurement function, the total number of measurement objects cannot exceed 200 cells. For the GBSC of the V900R011 version or a later version, a maximum of 500 cells can be registered on each BSC.


GSM Neighboring Cell Analysis Table 6-12 describes the task management capacity for the neighboring GSM cell analysis of the Nastar.

Table 6-12 Task management capacity for the neighboring GSM cell analysis




≤ 10,000 cells








of 46

The GSM frequency analysis and neighboring cell analysis use the same neighboring cell

measurement task. One GBSC supports only one neighboring cell measurement task at a time. For the GBSC of the version earlier than V900R011, if the BSC is not enabled with the

outgoing cell handover measurement function, a maximum of 200 cells can be registered on each BSC for the neighboring cell measurement task; if the BSC is enabled with the outgoing cell handover measurement function, the total number of measurement objects cannot exceed 200 cells. For the GBSC of the V900R011 version or a later version, a maximum of 500 cells can be registered on each BSC.


GSM/UMTS Neighboring Cell Analysis Table 6-13 describes the task management capacity for the inter-system neighboring GSM/UMTS cell analysis of the Nastar.

Table 6-13 Task management capacity for the inter-system neighboring GSM/UMTS cell analysis




≤ 10,000 cells






One GBSC supports only one neighboring GSM/UMTS cell measurement task at a time. In

addition, when a neighboring GSM/UMTS cell measurement task is in progress, neighboring GSM cell measurement tasks cannot be processed.


GSM Uplink Interference Analysis Table 6-14 describes the task management capacity for the GSM uplink interference analysis of the Nastar.



of 46

Table 6-14 Task management capacity for the GSM uplink interference analysis




≤ 500 cells






One GBSC supports only one uplink frequency scanning task at a time. One GBSC supports the execution of uplink frequency scanning on a maximum of 500 cells

at a time. One GBSC supports the execution of uplink frequency scanning on a maximum of 150

frequencies at a time. The Nastar server can run a maximum of five analysis tasks simultaneously. If only a

certain type of theme analysis tasks are running on the Nastar, a maximum of five analysis tasks of this type can be executed simultaneously.

GSM VIP Analysis Table 6-15 describes the task management capacity for the GSM VIP analysis of the Nastar.

Table 6-15 Task management capacity for the GSM VIP analysis



Number of defined VIP groups ≤ 100

Number of defined VIP subscribers ≤ 30,000

Number of VIP subscribers that report data sources

≤ 2,000

Number of subscribers supported by one analysis task

≤ 30,000 (for summarization analysis)

≤ 2,000 (for thoroughly analysis)






of 46

Time range of analysis data ≤ 7 days

Response time of task execution ≤ 60 minutes

In GSM&UMTS or GSM&UMTS&LTE hybrid network mode, the Nastar can analyze data

for a maximum of 30,000 VIP subscribers, which can be divided into a maximum of 100 VIP groups. Among these subscribers, data for a maximum of 2000 subscribers can be further analyzed.


GSM Complaint Analysis Support Table 6-16 describes the task management capacity for the GSM complaint analysis support of the Nastar.

Table 6-16 Task management capacity for the GSM complaint analysis support



Number of complaint subscribers supported by one analysis task

≤ 2,000




Time range of analysis Past 7 days


The Nastar sets a 45-minute timeout timer. If the Nastar does not receive complaint data

after the timer has expired due to a network fault, the complaint analysis support task fails to be executed.




of 46

GSM Cell Performance Analysis Table 6-17 describes the task management capacity for the GSM cell performance analysis of the Nastar.

Table 6-17 Task management capacity for the GSM cell performance analysis




≤ 2,048 cells







6.3.2 Task Management Capacity of the Nastar (UMTS)

Intra-Frequency Neighboring UMTS Cell Analysis Table 6-18 describes the task management capacity for the intra-frequency neighboring UMTS cell analysis of the Nastar.

Table 6-18 Task management capacity for the intra-frequency neighboring UMTS cell analysis




≤ 10,000 cells








of 46

The Nastar can only be used for measuring and analyzing the intra-frequency neighboring

UMTS cells in the case of soft handovers or softer handovers. One RNC supports only one measurement task at a time. The Nastar server can run a maximum of five analysis tasks simultaneously. If only a


UMTS/GSM Neighboring Cell Analysis Table 6-19 describes the task management capacity for the inter-system neighboring UMTS/GSM cell analysis of the Nastar.

Table 6-19 Task management capacity for the inter-system neighboring UMTS/GSM cell analysis




≤ 10,000 cells






One RNC supports only one inter-system neighboring UMTS/GSM cell measurement task

at a time. The Nastar server can run a maximum of five analysis tasks simultaneously. If only a


UMTS Coverage Analysis Table 6-20 describes the task management capacity for the UMTS coverage analysis.

Table 6-20 Task management capacity for the UMTS coverage analysis




≤ 1,000 cells



of 46






One RNC supports only one measurement task at a time. The Nastar server can run a maximum of five analysis tasks simultaneously. If only a


UMTS Uplink Interference Analysis Table 6-21 describes the task management capacity for the UMTS uplink interference analysis

Table 6-21 Task management capacity for the UMTS uplink interference analysis



Number of NE objects supported by one analysis task

≤ 100 sites






One RNC supports only one measurement task at a time. The Nastar server can run a maximum of five analysis tasks simultaneously. If only a


UMTS Pilot Pollution Analysis Table 6-22 describes the task management capacity for the UMTS pilot pollution analysis of the Nastar.



of 46

Table 6-22 Task management capacity for the UMTS pilot pollution analysis




≤ 10,000 cells






One RNC supports only one UMTS pilot pollution measurement task at a time. The Nastar server can run a maximum of five analysis tasks simultaneously. If only a


UMTS VIP Analysis Table 6-23 describes the task management capacity for the UMTS VIP analysis of the Nastar.

Table 6-23 Task management capacity for the UMTS VIP analysis






≤ 2,000



≤ 2,000 (for thoroughly analysis)








of 46

In GSM&UMTS or GSM&UMTS&LTE hybrid network mode, the Nastar can analyze data

for a maximum of 30,000 VIP subscribers, which can be divided into a maximum of 100 VIP groups. Among these subscribers, data for a maximum of 2000 subscribers can be further analyzed.


UMTS Complaint Analysis Support Table 6-24 describes the task management capacity for the UMTS complaint analysis support of the Nastar.

Table 6-24 Task management capacity for the UMTS complaint analysis support




≤ 2,000









UMTS Cell Performance Analysis Table 6-25 describes the task management capacity for the UMTS cell performance analysis of the Nastar.



of 46

Table 6-25 Task management capacity for the UMTS cell performance analysis




≤ 5,100 cells







6.3.3 Task Management Capacity of the Nastar (LTE)

LTE Coverage Analysis Table 6-26 describes the task management capacity for the LTE coverage analysis of the Nastar.

Table 6-26 Task management capacity for the LTE coverage analysis




≤ 1,000 eNodeBs








of 46


LTE Terminal Performance Analysis Table 6-27 describes the task management capacity for the LTE terminal performance analysis of the Nastar.

Table 6-27 Task management capacity for the LTE terminal performance analysis




≤ 10,000 eNodeBs







LTE Complaint Analysis Support Table 6-28 describes the task management capacity for the LTE complaint analysis support of the Nastar.

Table 6-28 Task management capacity for the LTE complaint analysis support




≤ 2,000







of 46






LTE VIP Analysis Table 6-29 describes the task management capacity for the LTE VIP analysis of the Nastar.

Table 6-29 Task management capacity for the LTE VIP analysis






-










of 46

In GSM&UMTS or GSM&UMTS&LTE hybrid network mode, the Nastar can analyze data for a maximum of 30,000 VIP subscribers, which can be divided into a maximum of 100 VIP groups. Among these subscribers, data for a maximum of 2000 subscribers can be further analyzed.


LTE Cell Performance Analysis Table 6-30 describes the task management capacity for the LTE cell performance analysis of the Nastar.

Table 6-30 Task management capacity for the LTE cell performance analysis




≤ 1,000 eNodeBs







LTE Cell Fault Analysis Table 6-31 describes the task management capacity for the LTE cell fault analysis of the Nastar.

Table 6-31 Task management capacity for the LTE cell fault analysis




≤ 1 eNodeB




of 46

Number of creating tasks ≤ 10,000





6.4 Storage Specifications of the Nastar 6.4.1 Storage Specification of the Configuration Data

Table 6-32 provides the storage specifications of the configuration data on the Nastar server.

Table 6-32 Storage specifications of the configuration data on the Nastar server

Data Type Execution Type Storage Duration on the Nastar Server Dsik (Days)

Storage Duration in the Nastar Database (Days)

GSM configuration data

One-time task

Periodic task

32 60

UMTS configuration data

One-time task

Periodic task

32 60

LTE configuration data

One-time task

Periodic task

32 60

6.4.2 Storage Specification of Engineering Parameters The specification for storing the engineering parameters on the Nastar server is Unlimited. Therefore, the engineering parameters are permanently saved on the Nastar server unless users delete the engineering parameters.



of 46

6.4.3 Storage Specification of Theme Analysis Data Table 6-33 provides the data storage capacity of the Nastar:

The specification for storing the theme analysis results (expect the analysis results of periodic theme tasks) on the Nastar server is unlimited. Therefore, the theme analysis data is permanently saved on the Nastar server unless users delete the theme analysis data.

Analysis results of periodic theme tasks can only be stored for a maximum of 30 days on the Nastar server.

Table 6-33 Storage specifications of the Nastar

Data Type Storage Duration on the Nastar Server Dsik (Days)


GSM MR analysis data 32 15

GSM Neighboring cell analysis data

32 15

GSM/UMTS Neighboring cell analysis data

32 15

GSM frequency analysis data 32 15

GSM uplink interference analysis data

32 15

GSM complaint analysis support data

32 -

GSM VIP analysis data 32 30

GSM cell performance analysis data

32 15

UMTS coverage analysis data 32 15

Inter-frequency neighboring UMTS cell analysis data

32 15

UMTS/GSM Neighboring cell analysis data

32 15

UMTS uplink interference analysis data

32 15

UMTS pilot pollution analysis data

32 15

UMTS complaint analysis support data

32 -

UMTS VIP analysis data 32 30

UMTS cell performance analysis data

32 15

LTE coverage analysis data 32 15



of 46

Data Type Storage Duration on the Nastar Server Dsik (Days)


LTE complaint analysis support data

32 -

LTE cell performance analysis data

32 15

LTE terminal performance analysis data

32 15

LTE VIP analysis data 32 30

LTE cell fault analysis data 32 30

6.5 Specifications of the SAU 6.5.1 Performance Specifications of the SAU

Table 6-34describes the performance specifications of the SAU.

Table 6-34 Performance specifications of the SAU

Type Performance Specification

Executing speed of one task ≥300 records / second

Processing time of one pre-processed task

Complaint analysis support: ≤ 6 minutes

Other analysis topics: ≤ 60 minutes

6.5.2 Storage Specifications of the SAU Table 6-35 describes the storage specifications of the SAU.

Table 6-35 Storage specifications of the SAU

Storage specifications of the SAUData Type Storage time (day) Strorage Capacity

(GB)

Raw data file CHR: ≤7 MR: ≤7

≤100

Pre-processing result file ≤7 ≤30

Log file ≤30 ≤100 MB

Program file - ≤10



of 46

6.6 Restrictions on the Clients Connected to the Nastar Table 6-36 describes the restrictions on the clients that can be connected to the Nastar.

Table 6-36 Restrictions on the clients connected to the Nastar

Item Restriction

Maximum number of clients that can be connected concurrently 30

Maximum number of clients where the same analysis result can be viewed 6

Maximum number of reports that can be concurrently opened on a client

16

Delay for the client to respond to a user operation ≤ 2 seconds

Delay for the client to respond to task management ≤ 5 seconds



of 46

7 Acronyms and Abbreviations

Acronym and Abbreviation

Expansion

CDMA Code Division Multiple Access

CME Configuration Management Express

CORBA Common Object Request Broker Architecture

CQT Call Quality Test

DT Drive Test

Ec/Io Chip Energy to other Interfere

EDGE Enhanced Data rates for GSM Evolution

FTP File Transfer Protocol

GPRS General Packet Radio Service

GUI Graphical User Interface

HSDPA High Speed Downlink Packet Access

HSUPA High Speed Uplink Packet Access

KPI Key Performance Indicator

JRE Java Runtime Environment

LTE Long Term Evolution

M2000 iManager M2000 Element Management System

MR Measurement Report

MTBF Mean Time Between Failures

MTTR Mean Time To Recovery

Nastar Network Analysis Star

PN Pseudo-random Number

RU Route Update message



of 46

Acronym and Abbreviation

Expansion

RAN Radio Access Network

RSSI Received Signal Strength Indicator

SAU Service Aware Unit

TA Timing Advance

UMTS Universal Mobile Telecommunications System

VIP Very Important Person

WCDMA Wideband CDMA

nastar v600r008 product description(gsmumtslte)

Documents

huawei trademarks

huawei proprietary

huawei industrial base

purchased products

product functions

purchased scope

partial products

application scenarios