Netnumen U31 r18 Unified Element Management System Configuration Application Operastion Guide PDF

NetNumen™ U31 R18
Unified Element Management System

Configuration Application Operation Guide
Version: 12.10.040
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2011-09–23 First Edition
Serial Number: SJ-20110823134613-010
Publishing Date: 2011-09-23(R1.0)

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview of Wireless Configuration Application................... 1-1
1.1 Purpose of Wireless Configuration Application ..................................................... 1-1
1.2 Wireless Configuration Application Functions ....................................................... 1-1
1.3 Implicit Prerequisites .......................................................................................... 1-3
Chapter 2 Wireless Configuration Application Operations .................... 2-1

2.1 Interconnection Parameter Management ............................................................. 2-1
2.1.1 Introduction to Interconnection Parameter Management ............................. 2-1
2.1.2 Comparing Interconnection Parameters in Batch ........................................ 2-2
2.1.3 Modifying Interconnection Parameters in Batch .......................................... 2-4
2.2 Network Element Relation Management .............................................................. 2-6
2.2.1 Introduction to Network Element Relation Management .............................. 2-6
2.2.2 Searching for Specific Network Element Relations...................................... 2-6
2.2.3 Exporting All Network Element Relations to an XLS File ............................. 2-8
2.3 Network Element Stability Management............................................................... 2-9
2.3.1 Introduction to Network Element Stability Management............................... 2-9
2.3.2 Managing Stability Events....................................................................... 2-10
2.3.3 Managing Maintenance Plans ................................................................. 2-17
2.4 Base Station Status Management ..................................................................... 2-22
2.4.1 Introduction to Base Station Status.......................................................... 2-22
2.4.2 Querying the Status of Base Stations ...................................................... 2-22
2.4.3 Setting the Status of a Base Station ........................................................ 2-25
2.4.4 Exporting the Status of Base Stations ...................................................... 2-27
2.4.5 Importing the Status of Base Stations From an XLS File ........................... 2-28
2.5 Base Station Priority Management..................................................................... 2-29
2.5.1 Introduction to Base Station Priority ......................................................... 2-29
2.5.2 Querying the Priorities of Base Stations ................................................... 2-29
2.5.3 Setting the Priority of a Base Station........................................................ 2-32
2.5.4 Exporting the Priority Information of Base Stations to an XLS File.............. 2-33
2.5.5 Importing the Priority Information of Base Stations From an XLS File......... 2-34
2.6 Inventory Management ..................................................................................... 2-35
2.6.1 Introduction to Inventory Management ..................................................... 2-35
2.6.2 Synchronizing Inventory Information From a Subnetwork .......................... 2-37
I
2.6.3 Synchronizing Inventory Information From All Subnetworks ...................... 2-38
2.6.4 Viewing Software and Firmware Inventory ............................................... 2-39
2.6.5 Exporting Inventory Information to a File .................................................. 2-40
2.6.6 Importing Inventory Information From a File ............................................. 2-41
2.6.7 Scheduling the Export of Inventory Information......................................... 2-41
2.7 Site Transfer .................................................................................................... 2-44
2.7.1 Introduction to Site Transfer .................................................................... 2-44
2.7.2 Exporting the Configuration Data of a Source Site .................................... 2-46
2.7.3 Transferring an Online Site ..................................................................... 2-47
2.7.4 Transferring an Offline Site ..................................................................... 2-48
2.7.5 Viewing the Operation Result Related to Site Transfer .............................. 2-50
2.7.6 Halting a Site Transfer Process ............................................................... 2-51
2.8 Import and Export Configuration Data Between NEs........................................... 2-52
2.8.1 Introduction to Inter-Element Import and Export of Configuration Data ....... 2-52
2.8.2 Exporting Configuration Data .................................................................. 2-52
2.8.3 Importing Configuration Data................................................................... 2-54
2.9 Neighbor Cell Relation Management ................................................................. 2-56
2.9.1 Introduction to Neighbor Cell Relation Management ................................. 2-56
2.9.2 Checking Neighbor Cell Relation ............................................................. 2-57
2.9.3 Importing Modification From a CSV File ................................................... 2-59
2.10 Consistency Check of User Labels .................................................................. 2-60
2.10.1 Introduction to User Label Relation Management.................................... 2-60
2.10.2 Checking Consistency of User Labels .................................................... 2-60
2.11 Cell Broadcast Management ........................................................................... 2-62
2.11.1 Overview.............................................................................................. 2-62
2.11.2 Channel Management........................................................................... 2-65
2.11.3 Cell Management ................................................................................. 2-67
2.11.4 Area Management ................................................................................ 2-69
2.11.5 Short Message Management................................................................. 2-72
2.12 Configuration Data Collection .......................................................................... 2-83
2.12.1 Introduction to Configuration Data Collection .......................................... 2-83
2.12.2 Creating a Template for Configuration Data Collection ............................ 2-84
2.12.3 Collecting Configuration Data ................................................................ 2-86
2.13 Radio Parameter Import.................................................................................. 2-88
2.13.1 Introduction to Radio Data Import .......................................................... 2-88
2.13.2 Importing Radio Data............................................................................ 2-88
Figures............................................................................................................. I
II
Tables ............................................................................................................ III
Glossary .........................................................................................................V
III
IV
About This Manual
The NetNumenTM U31 R18 Unified Element Management System (NetNumen U31 or
EMS) is a special network element management system that manages network elements
in radio access systems. By using NetNumen U31, users can configure and maintain
individual network elements, and manage radio access networks in a unified manner.
NetNumen U31 provides the following management functions:
l Configuration management
l Fault management
l Performance management
l Topology management
l Security management
As an object-oriented system designed on the J2EE platform, NetNumen U31 provides
unified standard interfaces to external devices.
Purpose
This guide provides explanations and instructions for the centralized configuration and
maintenance of wireless products in the NetNumen U31 system.
Intended Audience
l Maintenance engineers
l Network planning and optimization engineers
What Is in This Manual
Chapter Summary
Chapter 1, Overview of Wireless Gives the definition of the wireless configuration application, and
Configuration Application lists related operations supported by NetNumen U31.
Chapter 2, Wireless Configuration Introduces the wireless configuration application tools provided
Application Operations by NetNumen U31, and provides the operation instructions of
these tools, including:
l batch comparison and modification of interconnection
parameters
l network element relation management
l network element stability event management
l base station status management
l base station priority management
l inventory management
l base station transfer management
l neighbor cell relation check
I
Chapter Summary
l consistency check of user labels

l cell broadcast management
l configuration data collection
l radio data import.
II
Chapter 1
Overview of Wireless
Configuration Application
Table of Contents
Purpose of Wireless Configuration Application ...........................................................1-1
Wireless Configuration Application Functions .............................................................1-1
Implicit Prerequisites ..................................................................................................1-3
1.1 Purpose of Wireless Configuration Application

NetNumen U31 provides a wireless configuration application module that supports
centralized configuration and maintenance operations. A configuration or maintenance
operation may involve multiple Network Elements (NEs) in a network. Such configuration
or maintenance works cannot be independently completed by the Operation &
Maintenance Modules (OMMs) of these NEs. In this case, the wireless configuration
application module of the NetNumen U31 system can be used to perform the configuration
or maintenance operation in a centralized manner.
1.2 Wireless Configuration Application Functions

Table 1-1 lists the functions supported by the wireless configuration application module
of NetNumen U31 and the corresponding commands on the Configuration menu on the
client Graphic User Interface (GUI) that are used to perform these functions.
Table 1-1 Wireless Configuration Application Functions
Function Description
Interconnection parameter Compares interconnection parameters in batch between a base

management station controller and base stations connected to it, and modifies
detected inconsistent interconnection parameters in batch.
NE relation management Manages the relations between a base station controller and the
base stations connected to it.
NE stability management l Queries the stability events occurring in an NE during a

period and exports the query result as a stability report.
l Adds the information of an NE maintenance plan. The
stability events occurring in the period as scheduled in the
NE maintenance plan will be excluded in the stability report.
1-1
SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

NetNumen™ U31 R18 Configuration Application Operation Guide
Function Description
NE status management Queries, sets, imports, and exports the status of base stations,
such as normal status or testing status.
Base station priority management Queries, sets, imports and exports the priority of base stations,
such as VIP, Class-B and Class-C.
Inventory management Manages the hardware and software inventory information

uploaded from various boards in NEs.
Base station transfer management Supports the online and offline transfer of base stations.
Inter-element import and export of Exports and imports configuration data in file format between
configuration data different NEs for configuration adjustment in a network.
Neighbor cell relation check Checks the configuration of neighbor cell relations. If any
inappropriate configuration is found, you can modify the
configuration manually or initiate an automatic modification.
Consistency check of user labels Checks whether the user labels of local cells keeps the same
when these cells are configured as external cells in other base
stations, and overwrites the inconsistent user labels with the
local user labels.
Cell broadcast management Supports the creation, query, modification, and deletion of cell
broadcast messages in addition to the management of channels,
cells, and areas.
Configuration data collection Collects configuration data of NEs from their OMMs.
Radio data import Imports radio data configuration from an XML file to NEs. The
NEs will modify their configuration data according to the imported
information.
Note:
l NE = Network Element
l VIP = Very Important Person
l CBC = Cell Broadcast Center
l OMM = Operation & Maintenance Module
l CM = Configuration Management
Table 1-2 lists the wireless configuration application tools for products of different radio
systems.
Table 1-2 Wireless Configuration Application Tools
LTE-
Function WCDMA GSM GSM-R LTE-TDD TD-SCDMA
FDD
Interconnection
parameter √ √ - - - √
management
1-2

Chapter 1 Overview of Wireless Configuration Application
LTE-
Function WCDMA GSM GSM-R LTE-TDD TD-SCDMA
FDD
NE relation
√ √ √ √ √ √
management
NE stability
√ √ √ √ √ √
management
NE status
√ √ √ √ √ √
management
Base station priority

√ √ √ √ √ √
management
Inventory
√ √ √ √ √ √
management
Base station transfer

√ √ - - - √
management
Inter-element import
and export of √ √ - √ √ √
configuration data
Neighbor cell relation

√ √ √ - - √
check
Consistency check of
√ - - - - -
user labels
Cell broadcast
√ - - - - -
management
Configuration data
√ √ - - - √
collection
Radio data import √ √ - - - -
Note:
l WCDMA = Wide band Code Division Multiple Access
l GSM = Global System for Mobile communication
l GSM-R = GSM for Railway
l LTE-TDD = Long Term Evolution-Time Division Duplex
l LTE-FDD = Long Term Evolution-Frequency Division Duplex
l TD-SCDMA = Time Division-Synchronization Code Division Multiple Access
• “√” indicates that the function is supported for the radio network system.
• “-” indicates that the function is not supported for the radio network system.
1.3 Implicit Prerequisites

For all operations subsequent to this section, make sure that:
1-3

l The NetNumen U31 client has been started and successfully connected to the server.
l The communication between the NetNumen U31 server and the managed network
elements is normal.
l The network element agent of the network elements you want to operate on has been
successfully started.
l You have the authority of operations on wireless configuration applications.
1-4

Chapter 2
Wireless Configuration
Application Operations
Table of Contents
Interconnection Parameter Management ....................................................................2-1
Network Element Relation Management.....................................................................2-6
Network Element Stability Management .....................................................................2-9
Base Station Status Management ............................................................................2-22
Base Station Priority Management ...........................................................................2-29
Inventory Management.............................................................................................2-35
Site Transfer.............................................................................................................2-44
Import and Export Configuration Data Between NEs ................................................2-52
Neighbor Cell Relation Management ........................................................................2-56
Consistency Check of User Labels ...........................................................................2-60
Cell Broadcast Management ....................................................................................2-62
Configuration Data Collection ...................................................................................2-83
Radio Parameter Import ...........................................................................................2-88
2.1 Interconnection Parameter Management

2.1.1 Introduction to Interconnection Parameter Management
The interconnection parameter management application provided by NetNumen U31
supports the batch comparison of interconnection parameters between a base station
controller (BSC or RNC) and the base stations (BTS or Node B) controlled by this
controller in a GSM, WCDMA, or TD-SCDMA network. If any interconnection parameters
are found inconsistent, you can modify these parameters in batch.
Note:
The prerequisite of interconnection parameter management is that the relations between

the base station controller and the base stations connected to it have been specified,
that is, the base stations have been assigned to a base station controller when they are
configured in the network element management system.
2-1

To start interconnection parameter management, select Configuration > Wireless Config

Application > InterNE Compare on the menu bar of the client window.
2.1.2 Comparing Interconnection Parameters in Batch

Prerequisites
Before you compare the interconnection parameters between a base station controller and
the base station(s) controlled by it, make sure that the relations between the base station
controller and the base stations have been specified in the system.
Context
The following example shows how to compare the interconnection parameters between
an RNC and the Node Bs controlled by it in a WCDMA network to check the consistency
of the interconnection parameters.
Steps
1. In the client window, select Configuration > Wireless Config Application > InterNE
Compare on the menu bar.
2. In the InterNE Manage Option dialog box, select a product type, for example,
WCDMA, and then click Next, as shown in Figure 2-1.
Figure 2-1 Selecting a Product Type
3. Select Compare, and then click Next, as shown in Figure 2-2.
2-2

Chapter 2 Wireless Configuration Application Operations
Figure 2-2 Selecting an Operation
4. Expand the NE tree, select one or more RNC(s) for comparing their interconnection
parameters, and then click Next, as shown in Figure 2-3.
Figure 2-3 Selecting an RNC
5. Select the Node B(s) for the comparison, and then click OK.
Figure 2-4 Selecting Node Bs
2-3

The InterNE Batch Compare Result dialog box opens, showing the comparison
result.
6. In the InterNE Batch Compare Result dialog box, expand the EMS Server tree in the
left pane, select an RNC to show the comparison result of interconnection parameters
between the selected RNC and all its Node B(s) on the Statistics tab page in the right
pane.
In the Comparative result (Y/N) column, Y indicates consistent interconnection
parameters between the RNC and corresponding Node B; while N indicates
inconsistent interconnection parameters between the RNC and corresponding Node
B.
To show the comparison details of the interconnection parameters between a Node B
and the RNC, click the tab corresponding to the Node B ID.
– End of Steps –
Follow-Up Action
To export and save the comparison result to an XLS file, do the following:
1. In the InterNE Batch Compare Result dialog box, click Export.
2. In the Save dialog box, select a directory where the comparison result is to be saved
from the Save in drop-down list box, type a name for the XLS file, and then click Save.
Open the XLS file to view the interconnection parameters exported from the system. If
any inconsistency of interconnection parameters is found, modify the wrongly-configured
parameters. For how to modify interconnection parameters, refer to Section 2.1.3
Modifying Interconnection Parameters in Batch.
2.1.3 Modifying Interconnection Parameters in Batch

Abstract
The following example shows how to modify inconsistent interconnection parameters
between an RNC and the controlled Node Bs in a WCDMA network.
Note:
The interconnection parameter modification function is not available for GSM products.
Prerequisites
Before modifying the interconnection parameters between a base station controller and
the base station(s) controlled by it, make sure that:
l The relations between the base station controller and the base stations have been
specified in the EMS.
2-4

l The comparison result of interconnection parameters has been exported to an XLS

file.
After interconnection parameter comparison, the comparison result can be exported to an
XLS file. Modify the inconsistent parameters if some interconnection parameters between
a base station controller and a base station are found inconsistent.
Steps
1. Open the XLS file containing the comparison result of interconnection parameters,
find and modify inconsistent parameters, and change the modification status
corresponding to the modified parameters to “Y”. After that, save and close the XLS
file.
2. In the client window, select Configuration > Wireless Config Application > InterNE
Compare on the menu bar. The InterNE Manage Option dialog box opens.
3. In the InterNE Manage Option dialog box, select a product type, for example,
WCDMA, and then click Next.
4. Select Modify, and then click Next.
The InterNE Modify dialog box opens, as shown in Figure 2-5.
Figure 2-5 InterNE Modify Dialog Box
5. In the InterNE Modify dialog box, click .

6. In the Open dialog box, select the directory where the XLS file containing the
modification information is saved from the Look in drop-down list box, click the XLS
file, and then click Open.
7. Click OK.
Result
The InterNE Batch Compare Result dialog box opens, showing the modification result of
interconnection parameters between an RNC and different Node Bs on separate tabs.
2-5

2.2 Network Element Relation Management

2.2.1 Introduction to Network Element Relation Management
In the NetNumen U31 system, base station controllers (BSC or RNC) and base stations
(BTS or Node B) can be deployed separately. For example, an RNC is managed by an
Operation & Maintenance Modules (OMM), but a Node B controlled by this RNC can be
managed by another OMM. In consideration of this possibility, when a Node B is configured
in the system, it is required to specify which RNC is used to control this Node B, that is,
the relation between the RNC and the Node B.
To view all specified relations in the system, select Configuration > Wireless Config
Application > NE Relation Management on the menu bar of the client window.
The NE Relation Management dialog box opens, as shown in Figure 2-6. This dialog
box lists all relations between base station controllers and base stations that have been
specified in the system.
Figure 2-6 NE Relation Management Dialog Box
In the NE Relation Management dialog box, users can:

l filter the information to show required relations.
l export all the network element relations to an XLS file.
2.2.2 Searching for Specific Network Element Relations

Abstract
The following example shows how to find the relations related to a specific Node B in a
WCDMA network by setting appropriate filtering conditions.
2-6

Steps
1. In the client window, select Configuration > Wireless Config Application > NE
Relation Management. The NE Relation Management dialog box opens, which
lists all relations specified in the system.
2. In the NE Relation Management dialog box, click Filter. The NE Relation Data Filter
dialog box opens.
3. In the NE Relation Data Filter dialog box, do the following to set filtering conditions:
a. Select a product type from the product drop-down list box, for example, WCDMA.
b. Type one or multiple keywords in the corresponding boxes. For example, type
“18” in the OMM-R SubnetWorkID box, as shown in Figure 2-7.
Figure 2-7 NE Relation Data Filter Dialog Box
4. Click OK.
Result
The system filters the relations in the NE Relation Management dialog box, only showing
the relations related to the RNC subnetworks whose IDs contain the keyword “18”, as
shown in Figure 2-8.
2-7

Figure 2-8 Filtering Result
Follow-Up Action
To show all NE relations in the NE Relation Management dialog box again, click Filter,
select “All” from the product drop-down list box, clear all filtering keywords, and then click
OK.
2.2.3 Exporting All Network Element Relations to an XLS File

Context
The following describes how to export all relations between base station controllers and
base stations that have been specified in the system to an XLS file.
Steps
Relation Management. The NE Relation Management dialog box opens, listing all
relations specified in the system.
2. In the NE Relation Management dialog box, click Export.
3. In the Save dialog box, select a directory where you want to save the XLS file from the
Save in drop-down list box, type a name for the file, and then click Save.
4. Click OK when prompted with the message of successful export.
Result
The XLS file containing the network element relations appears in the specified directory.
2-8

2.3 Network Element Stability Management

2.3.1 Introduction to Network Element Stability Management
The NetNumen U31 system collects the stability events from all managed Network
Elements (NEs), stores the collected events in the database of the system, and generates
statistical report as required. The collected events also include those occurring during the
maintenance of NEs. Users can add the information of the maintenance plan to exclude
the events during maintenance from the stability report because they cannot reflect the
actual stability of NEs.
l Stability Event
An NE collects the events occurring in all its boards and sends the collected event
information to the alarm mail box of the NetNumen U31 system. The stability
management application of the NetNumen U31 system listens this alarm mail box in
real time.
The NetNumen U31 system determines the weight of an event according to its board
type weight and board redundancy weight.
à Board Type Weight
The system sets the weight of an event according to the type of the board where
the event occurs. Boards in an NE can be classified into two types: interface
board and processing board. The weight of a processing board is higher than an
interface board.
à Board Redundancy Weight
The system sets the weight of an event according to the redundancy mode of the
board where the event occurs, as well as the quantity of redundant boards, board
type, and bandwidth. The board redundancy weight varies with the redundancy
mode, such as no redundancy, 1+1 backup, or load sharing.
l Maintenance Plan
If a maintenance plan is made for an NE, you need to specify the information of this
plan in the system, including the start time, end time, involved NE type, maintenance
operations, and maintenance objects, to exclude the stability events occurring during
the maintenance. After that, the system does not involve the events occurring during
the maintenance for the statistics of stability events when generating a stability report.
To start the management of stability events, select Configuration > Wireless Config
Application > NE Stability Management on the menu bar of the client window.
2-9

2.3.2 Managing Stability Events

2.3.2.1 Querying Stability Events
Abstract
This section describes how to query the stability events collected by the NetNumen U31
system during a specific period.
Steps
Stability Management. The NE Stability Manager dialog box opens.
2. On the Stability Event tab of the NE Stability Manager dialog box, set a query period
as follows:
a. Click the Begin Time drop-down list box, select a date in the pop-up calender,
and then click OK.
b. Click the End Time drop-down list box, select a date in the pop-up calender, and
then click OK.
c. Select a time zone from the Time Zone drop-down list box.
3. Click Search.
Result
The system queries the stability events occurring during the specified period, and displays
the query result in the NE Stability Manager dialog box, as shown in Figure 2-9.
2-10

Figure 2-9 Query Result of Stability Events
2.3.2.2 Exporting the Query Result of Stability Events to an XLS File
Abstract
This section describes how to export the queried stability events as a report to an XLS file.
Prerequisites
The query result of stability events is displayed in the NE Stability Manager dialog box.
Steps
1. On the Stability Event tab of the NE Stability Manager dialog box, where the query
result is displayed, click Export Result.
2. In the Save dialog box, do the following:

a. Select a directory where you want to save the XLS file from the Save in drop-down
list box.
b. Enter a name for the file in the File name box if you do not want to use the default
name.
c. Click Save.
2-11


Result
An XLS file containing the information of the stability events during the specified period
appears in the specified directory.
2.3.2.3 Exporting a Network Element Stability Report
Abstract
The system can generate a Network Element (NE) stability report based on the collected
stability events during a specific period. The following example shows how to export a
stability report to an XLS file.
Steps
Stability Management. The NE Stability Manager dialog box opens.
2. On the Stability Event tab of the NE Stability Manager dialog box, set a period as
follows:
a. Click the Begin Time drop-down list box, select a date in the pop-up calender,
and then click OK.
b. Click the End Time drop-down list box, select a date in the pop-up calender, and
then click OK.
3. Click Export Report.
list box.
name.
c. Click Save.
Result
An NE stability report in the format of XLS file appears in the specified directory.
Follow-Up Action
To view the contents in the NE stability report by double-clicking the file icon. Table 2-1
shows an example of the stability report.
2-12

Table 2-1 Stability Report
NE Stability Report
Part- Planned Stability Percent

All-Break Light-Break Instability Stability
NE ID Break Instability (Planned
Time(s) Time(s) Time(s) Percent
Time(s) Time Except)
RNC118-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
118
RNC123-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
123
RNC21-21 0.00 0.00 74.69 9.75 0.00 99.999% 99.999%
RNC225-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
225
RNC226-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
226
RNC228-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
228
RNC230-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
230
RNC231-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
231
RNC232-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
232
RNC234-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
234
RNC249-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
249
RNC250-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
250
RNC333-
0.00 0.00 0.00 0.00 0.00 100.000% 100.000%
333
Begin Date (Asia/Shanghai) 2011-07-01 End Date (Asia/Shanghai) 2011-07-21
2-13

2.3.2.4 Scheduling the Generation of Network Element Stability Reports
Abstract
In the NetNumen U31 system, a Man-Machine Language (MML) timing task can be created
for periodic generation of Network Element (NE) stability reports. The following example
shows how to schedule an MML timing task for generating NE stability reports weekly.
Steps
1. In the client window, select Maintenance > Task Management, and then click the
MML Timing Task node in the Task Management tree, as shown in Figure 2-10.
Figure 2-10 Task Management (MML Timing Task)
2. Click on the toolbar. The Create Task dialog box opens.

3. On the Base info tab of the Create Task dialog box, do the following:
a. In the Task Name box, type a name for the new task.
b. From the Task Status drop-down list box, select an initial status for the new task:
Activate or Suspend.
c. In the Task Description box, type additional information for the new task as
needed.
d. Under MML, type the MML command for generating an NE stability report as
follows:
MINOS CMD:TYPE=”STABILITYREPORT”[,ATTRIB=”period&path”]
The command is case-insensitive. The following describes two input parameters

in this command: period and path.
2-14

Parameter Description
period (Optional) Specifies the period during which the stability events are
required for the generation of an NE stability report.
Unit: day
Default value: 1
Example: Set the parameter value to 7. Then the system will query the
stability events occurring in the previous 7 days and generate an NE
stability report based on the query result.
path (Optional) Specifies the path where the generated NE stability reports
will be saved.
Note: If the value of this parameter is null, the system will save the NE
stability reports under \ums-server\rundata\ftp\stability\ne\
by default.
The value format of this parameter varies with the type of the operating
system where the NetNumen U31 server is installed. For example,
l Windows: use double slash (\\) while typing the path, for example,
D:\\EXPORT.
l Linux or UNIX: use single slash (/) while typing the path, for example,
/export/home/omc/netnumen/ums-server/rundata/ftp
/stability/ne.
Figure 2-11 shows an example of the basic information of an MML timing task.
Figure 2-11 Create Task Dialog Box (Base info Tab)
4. On the Policy tab, set the running policy as follows:
2-15

a. Under Plan Types, set a running cycle of the new task. In this example, select
Weekly from the drop-down list box, and then select Monday.
b. Under Execution Time, type the time when the task shall be run on the specified
day, for example, 00:00:00.
c. Under Duration Period, set the effective period of the task. If you do not set the
period, the default start date is the current date.
Figure 2-12 Create Task Dialog Box (Policy Tab)
5. Click OK.
Result
The created MML timing task for generating stability reports appears in the task list. If the
initial status of this task is active, the system will generate an NE stability report based
on the stability events occurring in the previous 7 days every Monday (as specified in this
example), and then save the generated report file in the specified path.
2-16

2.3.3 Managing Maintenance Plans

2.3.3.1 Adding a Maintenance Plan
Abstract
If a network element or board is involved in a maintenance plan, users can specify the
maintenance information in the NetNumen U31 system to exclude stability events caused
by maintenance operations, ensuring the accuracy of the stability report.
The following describes how to add a maintenance plan in the NetNumen U31 system.
Steps
Stability Management on the menu bar. In the NE Stability Manager dialog box,
click the Maintain Plan tab, as shown in Figure 2-13.
Figure 2-13 NE Stability Manager Dialog Box (Maintain Plan Tab)
2. On the Maintain Plan tab, right-click a row in the plan list, and then click Add Plan.
The Add Maintain Plan dialog box opens, as shown in Figure 2-14.
2-17

Figure 2-14 Add Maintain Plan Dialog Box
3. In the Add Maintain Plan dialog box, set the parameters according to the information
of the actual maintenance plan.
Table 2-2 describes the parameters that shall be set in the Add Maintain Plan dialog
box.
Table 2-2 Description of the Parameters in the Add Maintain Plan Dialog Box
Start Date Specifies the start date of the maintenance plan.
End Date Specifies the end date of the maintenance plan.
Time Zone Provides the time zones used for determining the start time and end time
of the maintenance plan.
NE Type Specifies the type of NE that will be maintained in the format of “NE
type-Subnetwork ID-NE ID”, for example, RNC280–280
Operation Type Provides the types of operation objects, NE or Board (board).
2-18

Operation Object Specifies the operation object. The format varies with the operation type.
l If NE is selected, specify the operation object in the format of
“Subnetwork ID-NE ID”, for example, 280–280.
l If Board is selected, specify the operation object in the format of
“Rack No.-Shelf No.-Slot No.”, for example, 1–2–11.
Operation Desc Specifies the other information of the maintenance plan when necessary.
Service Impacting Selects whether the maintenance plan impacts services.
Emergency Selects whether the maintenance plan is emergent.
Retrospective Selects whether the system can be restored after the maintenance plan
fails.
Closure State Selects whether all maintenance operations in the plan are completed
during the specified period.
Comments Adds a comment to the maintenance plan.
4. Click OK.
A dialog box opens, prompting the successful adding of the maintenance plan and
asking you whether to add another maintenance plan.
5. Click No if you do not want to add another maintenance plan. The procedure is
concluded.
Result
The added maintenance plan appears in the plan list on the Maintain Plan tab in the
NE Stability Manager dialog box. The system will not involve the events of related NEs
occurring during the maintenance period when generating a stability report.
Follow-Up Action
l To modify an existing maintenance plan, right-click the corresponding row, and then
click Modify Plan. In the Modify Maintain Plan dialog box, modify the information of
the maintenance plan.
l To delete a maintenance plan, right-click the corresponding row, and then click Delete
Plan.
2.3.3.2 Querying Maintenance Plans
Abstract
This section describes how to query maintenance plans that have been added in the
NetNumen U31 system by operation type and start date.
2-19

Steps
Stability Management on the menu bar. In the NE Stability Manager dialog box,
click the Maintain Plan tab.
2. Under Operation Type, select an operation type: NE or Board.
3. From the Start Date drop-down list box, select a date and click OK.
4. From the Time Zone drop-down list box, select a time zone as required.
5. Click Search.
Result
The system queries all maintenance plans meeting the query conditions, and displays the
query result on the Maintain Plan tab, as shown in Figure 2-15.
Figure 2-15 Result of Querying Maintenance Plans
If no maintenance plan meets the specified conditions, the system will prompt the query
failure and require you to reset query conditions.
2.3.3.3 Exporting the Query Result of Maintenance Plans
Abstract
This section describes how to export the information of queried maintenance plans to an
XLS file.
2-20

Prerequisites
The query result of maintenance plans is displayed in the NE Stability Manager dialog
box.
Steps
1. On the Maintain Plan tab of the NE Stability Manager dialog box, click Export
Result.
list box.
name.
c. Click Save.
Result
An XLS file containing the information of exported maintenance plans appears in the
specified directory.
2.3.3.4 Importing Maintenance Plans From a CSV File
Abstract
This section describes how to add the information of maintenance plans by importing a
predefined CSV file.
Prerequisites
The NE Stability Manager dialog box is open.
Steps
1. Prepare the CSV file to be imported. An XLS file containing the exported query result of
maintenance plan can be used as a template for editing the information of maintenance
plans to be imported.
2. On the Maintain Plan tab of the NE Stability Manager dialog box, click Import.
3. In the Open dialog box, select the directory where the CSV file is saved from the Look
in drop-down list box, and then click Open.
2-21

Result
l If the system succeeds to import the maintenance plan information from the file, a
message box opens, prompting the successful import of maintenance plans.
l If the system fails to import the maintenance plan information from the file, a message
box opens, prompting the import failure. At the same time, a log file is generated in
the directory where the CSV file is saved. You can open the log file to find the cause
of the import failure.
2.4 Base Station Status Management

2.4.1 Introduction to Base Station Status
Generally, a base station works in either of the following four status.
l Normal status
The base station is operating properly.
l Testing status
The base station is under test or maintenance. In this status, large amounts of
alarms are generated. The alarm and performance data generated during the test or
maintenances is not reported to the network element management system because
such data does not make sense for performance analysis of the base station.
The testing status does not influence the report of configuration data.
l Fault Management (FM) testing status
The base station in FM testing status does not report all or part of its alarm data to the
EMS.
l Performance Management (PM) testing status
The base station in PM testing status does not report all or part of its performance
data to the EMS.
To start the management of base station status, select Configuration > Wireless Config
Application > Maintain Status Query and Set on the menu bar of the client window. The
Maintain Status Query and Set dialog box opens. In this dialog box, users can:
l query the status of specific base stations,
l set the status of a base station,
l export the query result of base station status,
l change the status of base stations by importing a predefined file.
2.4.2 Querying the Status of Base Stations

Abstract
This section describes how to query the status of specific base stations.
2-22

Prerequisites
The base stations to be queries have been configured in the NetNumen U31 system. In
addition, the connections between the base stations and their base station controllers are
normal.
Steps
1. In the client window, select Configuration > Wireless Config Application > Maintain
Status Query and Set on the menu bar. The Maintain Status Query and Set dialog
box opens.
2. In the Maintain Status Query and Set dialog box, set the query conditions as follows:
a. In the EMS Server tree, select the subnetwork that the base stations belong to.
b. Select the base station status you want to query: All, Normal, Testing, FM
Testing, or PM Testing.
c. To query the status of base stations according to a keyword in the IDs of the
managed base stations, select = or like from the ME ID drop-down list box, type
a keyword in the blank box, and then click Add.
d. To query the status of base stations according to a keyword in the names of the
managed base stations, select = or like from the ME Name drop-down list box,
type a keyword in the blank box, and then click Add.
Note:
In the topology tree, each node is identified with a string combining ME Name and ME
ID. Users can query the status of base stations by ME name or/and ID.
l If “=” is selected, the system will query the status of base stations whose ME name
or ID equals to the string set in the corresponding box.
l If “like” is selected, the system will query the status of base stations whose ME
name or ID contains the string set in the corresponding box.
If multiple query conditions related to ME name and ID are added, the system will
query the status of base stations whose ME name and ID meet all these conditions.
If no query condition of ME name and ID is added, the system will query the status of
all base stations belonging to the selected subnetwork.
For example, the system will query the status of the base stations whose ME IDs
contain the keyword “3” according to the conditions in Figure 2-16, including the base
stations in Normal status and Testing status.
2-23

Figure 2-16 Setting Conditions for Status Query
3. Click OK.
Result
The Maintain Status Query and Set dialog box shows the status of the base stations
meeting the query conditions, as shown in Figure 2-17.
Figure 2-17 Query Result of Maintenance Status
Note:
If you query the status of WCDMA equipment, the query result will also involve related
office information.
2-24

Follow-Up Action
In the Maintain Status Query and Set dialog box, appropriate buttons can be used to
perform the following operations:
Button Operation
Execute Sets the status of a base station.
Export Exports the query result to an XLS file.
Import Sets the status of base station(s) by importing an XLS file.
Refresh Refreshes the status of base stations in the query result.
Option Resets the query conditions to initiate another query.
2.4.3 Setting the Status of a Base Station

Abstract
The following example shows how to set the status of a base station from “Normal” to
“Testing”.
Prerequisites
l The base station to be set has been configured in the NetNumen U31 system. In
addition, the connection between the base station and its base station controller is
normal.
l You have successfully queried the status of the base station, and the query result is
displayed in the Maintain Status Query and Set dialog box.
Steps
1. In the Maintain Status Query and Set dialog box, right-click the row corresponding
to the base station, and then click Testing, as shown in Figure 2-18.
2-25

Figure 2-18 Setting the Status of a Base Station (1)
Tip:
To set the status of multiple base stations at a time, press and hold the Ctrl key, click
the row of each base station to be set, right-click any selected row, and then select a
new status.
2. Click Execute. When prompted with the message that the command has been
executed, click OK.
“Success” is displayed in the cell on the Result column, as shown in Figure 2-19.
2-26

Note:
When prompted with a result of “Exception”, check related logs to find the cause of
the failure.
3. Click Refresh. The current status of the base station is refreshed and displayed in the
Maintain Status Query and Set dialog box, as shown in Figure 2-20.
Follow-Up Action
If the status of a base station is changed from “Normal” to “Testing”, be sure to set the
status of the base station to “Normal” after completing the test or maintenance of the base
station because a base station in “Testing” status does not report alarm and performance
data to the NetNumen U31 system.
2.4.4 Exporting the Status of Base Stations

Abstract
The queried status of base stations can be exported to an XLS file. Users can modify the
status of some base stations in the XLS file, and then import this file to the system to set
the status of multiple base stations at a time.
The following describes how to export the status of base stations displayed in the Maintain
Status Query and Set dialog box to an XLS file.
2-27

Prerequisites
l Related base stations have been configured in the NetNumen U31 system. In
addition, the connections between these base stations and their base station
controllers are normal.
l You have successfully queried the status of the base stations, and the query result is
displayed in the Maintain Status Query and Set dialog box.
Steps
1. In the Maintain Status Query and Set dialog box, click Export.
2. In the Save dialog box, select a directory where you want to save the XLS file from the
Save in drop-down list box, type a name for the XLS file, and then click Save.
Result
An XLS file containing the status information of the base stations displayed in the Maintain
Status Query and Set dialog box appears in the specified directory.
2.4.5 Importing the Status of Base Stations From an XLS File

Abstract
This section describes how to import the status of base stations from a predefined XLS
file.
Prerequisites
l Related base stations have been configured in the NetNumen U31 system, and the
connections between them and their base station controllers are normal.
l You have queried the status of the base stations, and the query result is displayed in
the Maintain Status Query and Set dialog box.
l The XLS file you want to import only contains the status information related to the
base stations involved in the Maintain Status Query and Set dialog box.
l The content format in the XLS file complies with the format specified by the system.
An XLS file containing the export result of base station status is recommended as the
template for editing the XLS file to be imported.
Steps
1. In the Maintain Status Query and Set dialog box, click Import.
2. In the Open dialog box, select the directory where the XLS file is saved from the Look
in drop-down list box, select the XLS file, and then click Open.
2-28

Result
The imported status of related base stations overwrites the original status displayed in the
Maintain Status Query and Set dialog box.
2.5 Base Station Priority Management

2.5.1 Introduction to Base Station Priority
NetNumen U31 defines the managed base stations into four classes according to their
priorities. They are VIP, Class-B, Class-C, and Normal base stations in descending priority
order. The priority attribute of a base station can be used in other functional modules of
the NetNumen U31 system. For example, users can use the fault management module
to get the alarm statistics of VIP base stations, Class-B base stations, and Class-C base
stations separately.
To start the management of base station priority, select Configuration > Wireless Config
Application > VIP NodeB Priority Query and Set to open the VIP NodeB Priority Query
and Set dialog box. In this dialog box, users can perform the following operations:
l query the priorities of base stations
l set the priority of a base station
l export the queried priority information to an XLS file
l import the priority information of base stations from an XLS file.
2.5.2 Querying the Priorities of Base Stations

Abstract
This section describes how to query the priorities of base stations managed by a Network
Element (NE) agent.
Prerequisites
The communication between the base stations to be queried and the NetNumen U31
system is normal.
Steps
1. In the client window, select Configuration > Wireless Config Application > VIP
NodeB Priority Query and Set on the menu bar. The VIP NodeB Priority Query
and Set dialog box opens, as shown in Figure 2-21
2-29

Figure 2-21 VIP NodeB Priority Query and Set Dialog Box
2. In the VIP NodeB Priority Query and Set dialog box, set the query conditions as
follows:
a. In the EMS Server tree, select the subnetwork that the base stations belong to.
b. Select the base station priority you want to query: All, VIP, B Class, C Class, or
Normal.
c. To query the priority of base stations according to a keyword in the IDs of the
managed base stations, select = or like from the ME ID drop-down list box, type
a keyword in the blank box, and then click Add.
d. To query the priority of base stations according to a keyword in the names of the
managed base stations, select = or like from the ME Name drop-down list box,
type a keyword in the blank box, and then click Add.
2-30

Note:
In the topology tree, each node is identified with a string combining ME Name and ME
ID. Users can query the priority of base stations by ME name or/and ID.
l If “=” is selected, the system will query the priority of base stations whose ME
name or ID equals to the string set in the corresponding box.
l If “like” is selected, the system will query the priority of base stations whose ME
name or ID contains the string set in the corresponding box.
If multiple query conditions related to ME name and ID are added, the system will
query the priority of base stations whose ME name and ID meet all these conditions.
If no query condition of ME name and ID is added, the system will query the priority of
all base stations belonging to the selected subnetwork.
3. Click OK
Result
The VIP NodeB Priority Query and Set dialog box shows the priorities of all base stations
meeting the query conditions, as shown in Figure 2-22.
Figure 2-22 Priority Query Result
2-31

2.5.3 Setting the Priority of a Base Station

Abstract
The following example shows how to change the priority of a base station from Normal to
Class-B.
Prerequisites
l The communication between the base station and the NetNumen U31 system is
normal.
l You have queried the priority of this base station, and the query result is displayed in
the VIP NodeB Priority Query and Set dialog box.
Steps
1. In the VIP NodeB Priority Query and Set dialog box, right-click the row corresponding
to the base station, and then click B Class, as shown in Figure 2-23.
Figure 2-23 Setting the Priority of a Base Station (1)
Note:
To set the priorities of multiple base stations to the same priority at a time, press and
hold the Ctrl key, click each base station to be set, right-click any selected base station,
and then select a new priority.
2. Click Execute. When prompted with the message that the command has been
executed, click OK.
“Success” is displayed in the cell on the Result column, as shown in Figure 2-24.
2-32

3. Click Refresh. The current priority of the base station is displayed in the VIP NodeB
Priority Query and Set dialog box, as shown in Figure 2-25. The contents in the
Priority After and Result columns are cleared.
2.5.4 Exporting the Priority Information of Base Stations to an XLS

File
Abstract
The following describes how to export the priority information of base stations displayed in
the VIP NodeB Priority Query and Set dialog box to an XLS file.
2-33

Prerequisites
l The communication between the base stations and the NetNumen U31 system is
normal.
l You have queries the priority information of the base stations, and the query result is
displayed in the VIP NodeB Priority Query and Set dialog box.
Steps
1. In the VIP NodeB Priority Query and Set dialog box, click Export.
2. In the Save dialog box, select a directory where you want to save the XLS file from
the Save in drop-down list box, type a name for the XLS file, and then click the Save
button.
Result
An XLS file containing the priority information displayed in the VIP NodeB Priority Query
and Set dialog box appears in the specified directory.
2.5.5 Importing the Priority Information of Base Stations From an

XLS File
Abstract
The following describes how to import the priority information of base stations from an XLS
file.
Prerequisites
l The communication between the base stations and the NetNumen U31 system is
normal.
l You have queried the priority information of the base stations, and the query result is
displayed in the VIP NodeB Priority Query and Set dialog box.
l The XLS file you want to import only contains the priority information related to the
base stations involved in the VIP NodeB Priority Query and Set dialog box.
l The content format in the XLS file complies with the format required by the system.
An XLS file containing the export result of base station priority is recommended as the
template for editing the XLS file to be imported.
Steps
1. In the VIP NodeB Priority Query and Set dialog box, click Import.
2-34

2. In the Open dialog box, select the directory where the XLS file is saved from the Look
in drop-down list box, select the XLS file, and then click Open.
Result
The imported priority information of related base stations overwrites the original priority
information displayed in the VIP NodeB Priority Query and Set dialog box.
2.6 Inventory Management

2.6.1 Introduction to Inventory Management
NetNumen U31 provides the inventory management functions for managing and
maintaining the information of boards and software versions uploaded from the managed
Network Elements (NEs). The prerequisite of inventory management is the normal
communication between NetNumen U31 and the managed NEs.
In addition to the uploaded inventory information, some inventory information that cannot
be obtained from the managed NEs can be manually added into the system. However,
the added inventory information is subject to the actual data of the NEs. That means
the manually-added inventory information will be overwritten if NetNumen U31 gets the
corresponding information from the NEs. The synchronization of inventory information is
recommended to ensure the data consistency between NetNumen U31 and the managed
NEs.
Before inventory management operations, select Configuration > Wireless Config
Application > Inventory Management on the menu bar in the client window to open the
Inventory Management dialog box.
Figure 2-26 shows a Inventory Management dialog box with the TOP tree expanded in
the navigation pane. The TOP tree only lists the NE agents that have been started in
the NetNumen U31 system. To show the inventory information of an NE, double-click the
corresponding node in the TOP tree.
2-35

Figure 2-26 Inventory Management Dialog Box
1. Menu bar 4. Network element agent 6. Network element node

2. Navigation pane node
3. Inventory list 5. Subnetwork node
Table 2-3 describes the functions of commands on the menus of the Inventory
Management dialog box.
Table 2-3 Description of Menus in the Inventory Management Dialog Box
Menu Command Function
File Import File Import inventory information from an XML or CSV file.
Export File Export all inventory information displayed in the

inventory list to an XML or CSV file.
Exit Exit the inventory management application.
Edit Select All Select all inventory information in the inventory list.
Unselect All Cancel the selection of all inventory information in the

inventory list.
View SW/FW Inventory Show the SW/FW inventory, that is, the software version
information of Operation & Maintenance Modules of
managed NEs, in the inventory list.
Operation Synchronize All Subnet Load the inventory information of the managed NEs
in all subnetworks and show the loaded information in
the dialog box.
Synchronize Single Subnet Load the inventory information of the managed NEs
in the selected subnetwork and show the loaded
information in the dialog box.
2-36

2.6.2 Synchronizing Inventory Information From a Subnetwork

Abstract
The information of boards configured in all network elements in a subnetwork can be
loaded to the NetNumen U31 system through the Operation & Maintenance Module (OMM)
that manage these NEs. The uploaded inventory information can be displayed in the
Inventory Management dialog box.
The following describes how to load the board information from a subnetwork to the
NetNumen U31 system by inventory synchronization.
Prerequisites
Before synchronizing inventory information from a subnetwork, make sure that the
communication between the NetNumen U31 system and the network elements in the
subnetwork is normal.
Steps
l In the Inventory Management dialog box, expand the TOP tree in the navigation
pane, select the subnetwork node, and then select Operation > Synchronize Single
Subnet.
Result
An Operating message box appears, prompting that the system is loading the inventory
information from the subnetwork. After the system completes the synchronization, a
Synchronize Result message box opens, showing the synchronization result.
Follow-Up Action
To show the loaded inventory information in the Inventory Management dialog box, click
a network element node under the subnetwork node on the TOP tree, as shown in Figure
2-27.
2-37

Figure 2-27 Inventory Information of a Network Element
2.6.3 Synchronizing Inventory Information From All Subnetworks

Abstract
By synchronizing the inventory information from all subnetworks, the board information of
all managed NEs in these subnetworks is loaded to NetNumen U31 system through their
Operation & Maintenance Modules (OMMs).
The following describes how to load the board information from all subnetworks of the NE
agents that have been started in the NetNumen U31 system.
Prerequisites
The communications between the NetNumen U31 system and all network elements in
these subnetwork are normal.
Steps
l In the Inventory Management dialog box, select Operation > Synchronize All
Subnet.
Result
An Operating message box appears, prompting that the system is loading the inventory
information from the subnetworks. After the system completes the synchronization, a
Synchronize Result message box appears, showing the synchronization result.
2-38

2.6.4 Viewing Software and Firmware Inventory

Abstract
The Software (SW) and Firmware (FW) inventory refers to the version packages in the
Operation & Maintenance Modules (OMMs) corresponding to the managed network
elements managed by the NetNumen U31 system.
The following describes how to view the SW and FW inventory information in the
NetNumen U31 system.
Prerequisites
The Inventory Management dialog box is open.
Steps
1. In the Inventory Management dialog box, select View > SW/FW Inventory.
2. In the SW/FW Inventory dialog box, click View to show all software and firmware
information in the system, as shown in Figure 2-28.
Figure 2-28 SW and FW Inventory Dialog Box
Follow-Up Action
In the SW/FW Inventory dialog box, appropriate buttons can be used to perform
corresponding operations, as described in Table 2-4.
Table 2-4 Operations in the SW/FW Inventory Dialog Box
Button Operation
Import Imports software and firmware inventory information from an XML or

CSV file to the NetNumen U31 system.
2-39

Button Operation
Export Exports the selected software and firmware inventory information in the
dialog box to an XML or CSV file.
Select All Selects all software and firmware inventory information displayed in
the dialog box.
Unselect All Cancels the selection of all software and firmware inventory information
in the dialog box.
Close Closes the SW/FW Inventory dialog box.
2.6.5 Exporting Inventory Information to a File

Abstract
This section describes how to export the inventory information in the Inventory
Management dialog box to an XML or CSV file.
Prerequisites
The inventory information to be exported is displayed in the Inventory Management dialog
box.
Steps
1. In the Inventory Management dialog box, select the check boxes on the Selection
column to select the inventory information to be exported.
Tip:
To export all inventory information in the dialog box, select Edit > Select All on the
menu bar.
2. Select File > Export File.
3. In the Save dialog box, select a directory where you want to save the file from the
Save in drop-down list box, type a name for the file, select a file type from the Files
of type drop-down box, and then click Save.

2-40

Result
The selected inventory information is exported to an XML or CSV file in the specified
directory.
2.6.6 Importing Inventory Information From a File

Abstract
Users can import inventory information from an XML or CSV file to the NetNumen
U31 system. The imported inventory information does not affect the actual inventory
information of the managed NEs. After the system synchronizes the inventory information
from the NEs, the imported inventory information will be replaced by the actual information
obtained from the corresponding NEs.
The following describes how to import inventory information from an XML or CSV file.
Prerequisites
l The Inventory Management dialog box is open.
l The XML or CSV file containing the inventory information to be imported is available.
The file containing the export result of inventory information can be used as a template,
in which you can edit the inventory information in required format.
l The inventory unit ID of each inventory to be imported is different from any existing
one in the NetNumen U31 system.
Steps
l In the Inventory Management dialog box, select File > Import File.
l In the Open dialog box, select the directory where the XML or CSV file is saved from
the Look in drop-down list box, select the file type from the Files of type drop-down
list box, click the file you want to import, and then click the Open button.
l Click OK when prompted with the message of successful import.
Result
The imported inventory information appears in the Inventory Management dialog box.
2.6.7 Scheduling the Export of Inventory Information

Abstract
In the NetNumen U31 system, users can create a Man-Machine Language (MML) timing
task for periodically exporting the inventory information in the system to an XML or CSV file
in the ums-server/works/minos/tmp/ftp/inventory/db/all/ directory on the
server. One to seven days are recommended as the period.
2-41

The following describes how to schedule an MML timing task for exporting the inventory
information periodically.
Steps
1. In the client window, select Maintenance > Task Management, and then click the
MML Timing Task node in the Task Management tree, as shown in Figure 2-29.
Figure 2-29 Task Management (MML Timing Task)
2. Click on the toolbar. The Create Task dialog box opens.

3. On the Base info tab of the Create Task dialog box, do the following:
a. In the Task Name box, type a name for the new task.
b. From the Task Status drop-down list box, select an initial status for the new task:
Activate or Suspend.
c. In the Task Description box, type additional information for the new task as
needed.
d. Under MML, type the MML command for exporting inventory information as
follows:
MINOS CMD:TYPE=”ExportInventory”,ATTRIB=”file type";
The command is case-insensitive. The file type may be XML or CSV. Figure 2-30
shows an example of the basic information of an MML timing task for exporting
inventory information to XML files.
2-42

Figure 2-30 Creating an Inventory Export Task (1)
4. On the Policy tab, set the running policy as follows:

a. Under Plan Types, set the running period of the new task. For example, select
Weekly from the drop-down list box, and then select Monday.
b. Under Execution Time, type the time when the task shall be run on the specified
day, for example, 01:00:00.
c. Under Duration Period, set the effective period of the task. If you do not set the
period, the default start date is the current date.
2-43

Figure 2-31 Creating an Inventory Export Task (2)
5. Click OK.
Result
The created MML timing task for exporting inventory information appears in the task list.
If the initial status of this task is active, the system will export the inventory information in
the system to an XML file every Monday (as specified in this example), and then save the
XML file in the default path.
2.7 Site Transfer

2.7.1 Introduction to Site Transfer
NetNumen U31 provides a tool supporting the transfer and swap of equipment in the same
network or between two networks of the same system (GSM, WCDMA, or TD-SCDMA).
Before transferring the configuration data of a site in the NetNumen U31 system, a
transfer plan file in XLS format must be made by professional engineers, which includes
the information of source node and destination node, and the necessary modification of
the configuration information.
The NetNumen U31 system provides the following functions to support site transfer.
l Export configuration data
2-44

Export the configuration information of the source node specified by the transfer plan
file from the system to a ZIP file, which can be used for site transfer later.
l Transfer the configuration data in the case of online source node
Transfer the configuration data of the source node specified by the transfer plan file
to the destination node, and then remove the source node from the system.
l Transfer the configuration data in the case of offline source node
Transfer the configuration data of the source node from a ZIP file, which is prepared
in advance, to the destination node. If the source node is managed by the same
NetNumen U31 system, remove the source node from the system.
The offline transfer of configuration data can be used for transferring equipment
managed by a NetNumen U31 system to another NetNumen U31 system.
Note:
If the process of data export, online transfer, or offline transfer has not been completed
within 15 minutes, the system will forcibly end the process. This time limit is determined
by three parameters in the minos-movesite-wsf-time.xml file in the ums-client
\procs\ppus\minos.ppu\minos-cmc.pmu\minos-movesite-wsf.par\conf\
directory. Users can change the values of these parameters to modify the time limit.
l getsite waitting="15"
l transfersite waitting="15"
l deletesite waitting="15"
Before data export, online or offline transfer operations, select Configuration > Wireless
Config Application > Transfer Site on the menu bar of the client window to open the
Transfer Base Station dialog box, as shown in Figure 2-32.
Figure 2-32 Transfer Base Station Dialog Box
2-45

2.7.2 Exporting the Configuration Data of a Source Site

Abstract
This sections describes how to export the configuration data of the source site from the
system to a ZIP file.
Prerequisites
l The Transfer Base Station dialog box is open.
l The transfer plan file in XLS format has been prepared, which contains the information
of the source site to be transferred.
Steps
1. In the Transfer Base Station dialog box, click Select.
2. In the Open dialog box, select the directory where the transfer plan file is saved from
the Look in drop-down list box, select the file, and then click Open.
3. From the Operation drop-down list box, select Export Data.
4. Select the type of configuration data to be exported according to the equipment type.
l For the transfer of a base station controller in a GSM or WCDMA network, select
Bind OMCR for exporting the configuration data of the RNC or BSC of the source
site.
Note:
The configuration data of a base station (BTS or Node B) can only be exported
via a tool provided by Operation & Maintenance Module (OMM).
l For the transfer of a site in a TD-SCDMA network, select both Bind OMCR and
Bind OMCB for exporting the configuration data of the RNC and Node B together.
5. Click Execute.
Result
The system starts exporting the configuration data of the source site to a ZIP file in the um
s-client/works/full/tmp/ftp/movesite/data/ directory. The export process,
the path and name of the ZIP file is displayed under Output Info in the Transfer Base
Station dialog box.
2-46

2.7.3 Transferring an Online Site

Abstract
This section describes how to transfer the configuration data from the source site to the
destination site as specified in the transfer plan file when the source site is online in the
Prerequisites
of the source site and destination site involved in the site transfer.
Steps
1. In the Transfer Base Station dialog box, click the Select button.
the Look in drop-down list box, select the file, and then click the Open button.
3. From the Operation drop-down list box, select Online Transfer.
4. Select the type of configuration data to be transferred according to the equipment type.
Bind OMCR for transferring the configuration data of the RNC or BSC of the
source site.
Note:
l For the transfer of a site in a TD-SCDMA network, select both Bind OMCR
and Bind OMCB for transferring the configuration data of the RNC and Node B
together.
Note:
If you do not want to remove the source site from the system after the successful site
transfer, cancel the selection of the Delete Site check box.
5. Click Execute.
2-47

Result
The system gets the configuration data from the source site, and then transfers the
configuration data to the destination site. The transfer process is indicated under Output
Info.
If Delete Site in the Transfer Base Station dialog box is selected, the system will remove
the source site after the successful site transfer.
2.7.4 Transferring an Offline Site

Abstract
The configuration data of an offline site can be transferred from a ZIP file that contains the
configuration data previously exported from the system. The offline transfer function can
be used to transfer a site managed a NetNumen U31 system to another NetNumen U31
system.
The following describes how to transfer the configuration data from the source site to the
destination site as specified in the transfer plan file when the source site is offline in the
Prerequisites
of the source site and destination site involved in the site transfer.
l The ZIP file containing the configuration data of the offline source site is available.
Steps
1. In the Transfer Base Station dialog box, click Select.
the Look in drop-down list box, select the file, and then click Open.
3. From the Operation drop-down list box, select Offline Transfer.
4. Select the type of configuration data to be transferred according to the equipment type.
Bind OMCR for transferring the configuration data of the RNC or BSC of the
source site.
Note:
2-48

l For the transfer of a site in a TD-SCDMA network, select both Bind OMCR
and Bind OMCB for transferring the configuration data of the RNC and Node B
together.
Note:
If you do not want to remove the source site from the system after the successful site
transfer, cancel the selection of the Delete Site check box.
5. Click Execute. In the Offline Data dialog box, click the Select button. Then select
the ZIP file that contains the configuration data of the source site, and then click Open
in the Open dialog box.
The information in the ZIP file is displayed in the Offline Data dialog box, as shown in
Figure 2-33.
Figure 2-33 Offline Data Dialog Box
Note:
To view the information of a source site in the Offline Data dialog box, select the
source site from the Site Info drop-down list box and then click View.
6. Click Ok.
Result
The system transfers the configuration data from the ZIP file to the destination site
according to the specification in the transfer plan file. The transfer process is indicated
under Output Info in the Transfer Base Station dialog box.
2-49

If Delete Site is selected in the Transfer Base Station dialog box and the source site is
managed by this NetNumen U31 system too, the system will remove the source site after
the successful site transfer.
Note:
If the transfer plan file specifies multiple source sites and destination sites, the system will
transfer the configuration data of all source sites to the corresponding destination sites.
2.7.5 Viewing the Operation Result Related to Site Transfer

Abstract
The result of the latest operation related to site transfer is saved in a CSV file in the
default directory. The following table lists the default directories where the result files of
the transfer-related operations are saved.
Operation Default Directory of Result File
Obtain the configuration data from ums-client/works/full/tmp/ftp/movesite/result

the source site for data export or /collect/
online transfer
Transfer the configuration data from ums-client/works/full/tmp/ftp/movesite/resu

the source site to the destination site lt/transfer/
Remove the source site ums-client/works/full/tmp/ftp/movesite/resul

t/delete/
Note:
A result file only records the result of the latest operation. The previously-recorded result
will be cleared.
Users can open a result file to view the detailed information about the result, or view the
operation result in the Transfer Base Station dialog box as follows.
Prerequisites
l You have performed some operation related to site transfer, for example, configuration
data export, online site transfer, or offline site transfer.
2-50

Steps
1. In the Transfer Base Station dialog box, click View Result. The Result Data dialog
box opens.
2. From the Result Type drop-down list box, select the operation result to be viewed, as
Figure 2-34 Result Data Dialog Box
2.7.6 Halting a Site Transfer Process

Abstract
If the system does not complete the export or transfer of configuration data after a long
time, the process can be halted as needed. After the process is halted, the system will not
run the commands that have not been issued to the corresponding site.
Caution!
Do not halt an export or transfer process unless absolutely necessary. Improper halting
of a process may result in the inconsistency of configuration data (for example, the
configuration data in the base station controller changes due to transfer operation but the
configuration data in the base station is not modified yet), or incompleted site transfer (for
example, a new site is created but the source site is not deleted from the system).
Prerequisites
l The system is exporting or transferring configuration data of a source site.
2-51

Steps
l In the Transfer Base Station dialog box, click Halt Operation.
Result
The system halts the export or transfer process, and shows the halt result in under Output
Info.
2.8 Import and Export Configuration Data Between NEs

2.8.1 Introduction to Inter-Element Import and Export of
Configuration Data
The NetNumen U31 system provides a tool supporting the export and import of
configuration data in WCDMA and LTE networks. Users can export configuration data
from multiple managed elements to XLS or XML files, and import the configuration data
to other managed elements from XLS or XML files.
The following lists the prerequisites for successful export and import of configuration data
between different NEs:
l The NEs supports the function of configuration data import and export.
l The type of the NE(s) to which the configuration data is imported is the same as that
of the NE(s) from which the configuration data is exported.
l The content and format of the configuration data in the XLS or XML file are correct.
l The configuration data in the file is applicable to the version of the NE(s) to which the
file will be imported.
Before the export and import of configuration data, select Configuration > Wireless
Config Application > Inter ME Import and Export on the menu bar of the client window
to open the Inter Me Configuration Import and Export dialog box.
2.8.2 Exporting Configuration Data

Abstract
This section describes how to export the configuration data of multiple managed element(s)
in the NetNumen U31 system to an XLS or XML file.
Prerequisites
The Inter Me Configuration Import and Export dialog box is open.
2-52

Steps
1. In the Inter Me Configuration Import and Export dialog box, select Operation >
Config Data Export, as show in Figure 2-35.
Figure 2-35 Configuration Data Export
2. In the Operation Template Selection pane, select a template to be used, for example,
wcdma-Radio Data Batch Import and Export.
3. Click Add Operate Object. The Add Network Element dialog box opens, as shown
in Figure 2-36.
Figure 2-36 Add Network Element Dialog Box
4. Select one or more NEs, and then click OK to return to the Inter Me Configuration
Import and Export dialog box.
2-53

Tip:
To remove an added network element, select the network element and then click
Remove Operate Object.
5. Click the cell on the Export Format column, and then select a file format for each NE,
xls or xml, as shown in Figure 2-37.
Figure 2-37 Selecting a File Format
6. Click OK.
Result
The system starts exporting configuration data of the selected NEs one by one. After the
configuration data of an NE is successfully exported, an XLS or XML file appears in the
default directory on the NetNumen U31 server (ums-client\works\full\tmp\ftp\c
entralimpexp\WCDMA or ums-client\works\full\tmp\ftp\centralimpexp\L
TE), and the file name appears in the corresponding cell on the File Name column.
2.8.3 Importing Configuration Data

Abstract
This section describes how to import the configuration data of some NEs to other NEs from
XLS or XML files.
Prerequisites
l The configuration data files in XLS or XML format are available, which contain the
configuration data to be imported.
l The Inter Me Configuration Import and Export dialog box is open.
2-54

Steps
1. In the Inter Me Configuration Import and Export dialog box, select Operation >
Config Data Import, as shown in Figure 2-38.
Figure 2-38 Configuration Data Import
2. In the Operation Template Selection pane, select a template to be used, for example,
wcdma-Radio Data Batch Import and Export.
3. Click Add Data File. In the Open dialog box, do the following:
a. Select the directory where the configuration data files are saved from the Look in
drop-down list box.
b. Select the file type from the Files of type drop-down list box.
c. Select a configuration data file to be imported, and then click Open.

The name of the selected file appears in the Selected Data File List.
4. Repeat Step 4 to add the other configuration data files to be import.
Tip:
To remove an added configuration data file, select the file and then click Remove Data
File.
5. For each configuration file, click the corresponding cell in the Operate Object No.
column, and then select the NE to which that the configuration data will be imported,
as shown in Figure 2-39.
2-55

Figure 2-39 Selecting an Operate Object Number
6. Click OK.
Result
The system starts importing the configuration data from the selected files one by one. Each
cell on the Progress column shows the import process of the corresponding configuration
data file. After the system completes the import of configuration data, a success or failure
message appears in each cell on the Result column.
2.9 Neighbor Cell Relation Management

2.9.1 Introduction to Neighbor Cell Relation Management
Cell Tool
The NetNumen U31 system provides a cell tool for checking neighbor cell relations,
including:
l Checking the consistency of interconnection parameters between a cell and its
neighbor cell.
l Checking the configuration of neighbor cell relation of a cell.
In addition, this cell tool also supports automatic and manual modification of inconsistent
neighbor cell relations.
Cell Tool Dialog Box

Before using the cell tool, select Configuration > Wireless Config Application > Cell
Tool on the menu bar of the client window to open the Cell Tool dialog box, as shown in
Figure 2-40.
2-56

Figure 2-40 Cell Tool Dialog Box
1. Function and attribute 2. Subnetwork pane

setting pane 3. Check result pane
2.9.2 Checking Neighbor Cell Relation

Abstract
Users can use the cell tool to check whether the relations between a cell and all its neighbor
cells have been appropriately configured. After the check operation, a result file will be
generated on the server.
l If the checked equipment only supports one system, such as WCDMA, only one result
file will be generated.
l If the checked equipment supports multiple systems, for example, GSM and WCDMA,
multiple result files will be generated.
The following describes how to check the neighbor cell relation configuration of a cell.
Prerequisites
l The Cell Tool dialog box is open.
l If some neighbor cell is managed by another NetNumen U31 system, make sure that
a ZIP file containing the information of this neighbor cell is available.
Steps
1. In the left pane of the Cell tool dialog box, click check lone for checking whether
some neighbor cell relation has not been properly configured.
2-57

Note:
To check whether the interconnection parameters of a cell and its neighbor cells are
consistent, select check accord.
2. Click set attribute on the lower part of the left pane, select a product type (for example,
W), and then select the subnetwork(s) to be checked in the subnetwork pane, as shown
in Figure 2-41.
Figure 2-41 Selecting Subnetworks
3. If some neighbor cells are managed by another NetNumen U31 system, export the
information of these cells to a ZIP file, and then load the ZIP file to this NetNumen U31
system as follows:
a. Click Browse after the relation file box.
b. In the Open dialog box, select the directory where the ZIP file is saved from the
Look in drop-down list box, select the ZIP file, and then click Open.
c. Click the Upload button to load the neighbor cell information from the ZIP file to
the NetNumen U31 server.
4. Click Browse after the result file box.

5. In the Open dialog box, select a directory where you want to save the result file(s)
from the Look In drop-down list box, and then click Open.
6. Click Execute.
The system starts checking the neighbor cell relation or comparing the interconnection
parameters. After completing the check, CSV file(s) containing the check result appear
2-58

in the specified directory, and the information of the check operation appears in the
check result pane, as shown in Figure 2-42.
Figure 2-42 Check Result
7. To view the details of a check result, right-click the corresponding row, and then click
show result.
The action result dialog box opens, in which “SUCCESS” is prompted for the cell
configured with complete neighbor cell relation.
In the action result dialog box, the following operations can be performed:
l To supplement the neighbor cell relation for a cell that does not pass the check,
select the corresponding record, and then click modify start.
The system automatically modifies the configuration of neighbor cell relation and
shows the modification result in the check result pane of the Cell Tool dialog box.
l To export the check result to a CSV file on the local client, click export.
Follow-Up Action
To clear a check result and remove the result file from the server, click the corresponding
row in the check result pane of the Cell Tool dialog box, and then click Clear.
2.9.3 Importing Modification From a CSV File

Abstract
The system may fail to supplement the configuration of neighbor cell relation or modify the
inconsistent interconnection parameters. In this case, users can export the check result
to a CSV file on the local client, check and modify the neighbor cell relation or inconsistent
interconnection parameters in the file, and then import the modified information to the
system.
The following describes how to modify the neighbor cell relation by importing a CSV file to
the system.
2-59

Prerequisites
l You have performed operations to check the neighbor cell relation or interconnection
parameter consistency in the Cell Tool dialog box, and the result file is successfully
generated under the specified directory on the local client.
l You have exported the result file and modified the inappropriate configuration in the
CSV file.
Steps
1. On the local client, find the result file, open the file, modify the neighbor cell relation in
the file according to the actual configuration in the network, and then save the modified
file.
2. In the Cell Tool dialog box, right-click the check result, and then click import data.
3. In the Open dialog box, find and select the modified CSV file, and then click Open.
Result
The modified neighbor cell relation is imported from the CSV file to the system. If the
modification is correct, you can find that “SUCCESS” is prompted in the action result
dialog box for the cell(s) that failed to pass the check.
2.10 Consistency Check of User Labels

2.10.1 Introduction to User Label Relation Management
A local cell may be referred to as an external cell by a base station. In this base station, the
user label of the external cell is identical to that of the local cell. If a user modifies the user
label of the local cell or the external cell, an inconsistency occurs in two user labels. In
this case, the function of managing user label relations can be used to overwrite the user
label of the external cell with the local one when the consistency of user labels is required
between a local cell and corresponding external cell.
In addition, the NetNumen U31 system can show the user labels of all local cells of a
managed element and those of corresponding external cells, and highlight the local cells
with inconsistent user labels.
2.10.2 Checking Consistency of User Labels

Abstract
This section describes how to check the consistency between the user labels of local cells
in a base station and the user labels of these cells when they are configured as external
cells in other base stations.
2-60

Steps
1. On the menu bar of the client window, select Configuration > Wireless Config
Application > Relation User Label Management. The Relation User Label
Manage dialog box opens.
2. In the Relation User Label Manage dialog box, expand the NE tree in the left pane,
click the managed element to be checked (for example, ME (WCDMA) (90)), and then
click Show.
Note:
At most 20 local cells can be displayed in the Relation User Label Manage dialog box
at a time. If you want to check specific local cells, set filtering conditions by entering a
start CID and an end CID in the From and To boxes before clicking Show. If no CID
range is set, the system will search for local cells with CIDs ranging from 0 through
200 by default, and only show the information of the first 20 local cells.
After the system completes the consistency check of user labels for the local cells
of the managed element, the Cell IDs (CIDs) and user labels of the local cells are
displayed in the right pane, as shown in Figure 2-43.
Figure 2-43 Relation User Label Manage Dialog Box
l A local cell in blue font indicates that the user label of this cell keeps the same
when it is configured as an external cell of another base station.
l A local cell in red font indicates that the user label of this cell changes when they
are configured as an external cell of another base station.
2-61

3. In the right pane of the Relation User Label Manage dialog box, expand each local
cell to show the information of corresponding external cell(s), as shown in Figure 2-44.
Figure 2-44 Local Cells and External Cells
1. Local cell 2. External cell
l The information format of a local cell is: CID:user label.

l The information format of an external cell is: RNCID:CID:user label:<details of the
external cell>.
4. To overwrite all different user labels of external cells with the local ones, click Modify.
5. When a message box appears, indicating the modification is completed, click OK.
6. When a dialog box appears, prompting you to update the user label information, click
Yes.
After the information update is completed, the Relation User Label Manage dialog
box shows the latest user label information after the modification.
2.11 Cell Broadcast Management

2.11.1 Overview
2.11.1.1 Cell Broadcast Management Functions
As an important service in mobile telecommunications system, the cell broadcast service
allows telecommunications operators to send short messages to all mobile users in a
geographic area. Cell broadcast service is different from point-to-point short message
2-62

service. A point-to-point short message is sent to a specific mobile user, while a cell
broadcast message is sent to all mobile users in an area, including roaming subscribers
in this area.
The NetNumen U31 system offers the following cell broadcast management functions:
l Creating, querying, modifying, and deleting a cell broadcast message
l Managing channels, cells, and areas
l Viewing the status of a cell broadcast message
l Viewing the history of operations on a cell broadcast message
l Resetting a cell and checking the reset result
2.11.1.2 Explanation of Short Message Status

The status of a short message created in the NetNumen U31 system may be Unsent,
Sending, or Finished, as illustrated in Figure 2-45.
Figure 2-45 Status Change of Short Message
l Unsent
If a short message is required to be sent on schedule, the system does not send the
short message to the specified NEs until the sending time is reached. The status of
the short message is “Unsent”.
l Sending
à If a short message is required to be sent immediately, the NetNumen U31
system sends the short message to the specified NEs immediately after the short
message is successfully created. The status of the short message is “Sending”.
à The status of a scheduled short message changes from “Unsent” to “Sending”
when the system starts sending it to the specified NEs on schedule.
l Finished
2-63

à If the NetNumen U31 system fails to send a short message to specified NEs, the
status of the short message changes to “Finished”.
à If all NEs succeed to send the short message as required, the status of the short
message changes to “Finished”.
à If an NE fails to send the short message, the status of the short message changes
to “Finished”.
à If a short message in “Sending” status is deleted by a user, the status of the short
message changes to “Finished”.
à If a short message in “Sending” status is modified by a user, the status of the short
message changes to “Finished” and the system creates a new short message
according to the modification.
2.11.1.3 Starting the Cell Broadcast Center
Abstract
This section describes how to start the Cell Broadcast Center (CBC) before managing
channels, cells, areas, and short messages for the cell broadcast service.
Steps
l Click on the toolbar.
l Select Configuration > Wireless Config Application > CBC Management on the
menu bar.
Result
The CBC Management window is displayed, as shown in Figure 2-46.
2-64

Figure 2-46 CBC Management Window
1. Navigation tree 2. Query bar 3. Information pane
To show the information of messages, channels, cells, or areas in the information pane,
click the corresponding node in the navigation tree.
2.11.2 Channel Management

Channels are used by mobile telecommunications operators to categorise short messages,
for example, create a channel for short messages of a specific issue, such as weather
forecast or entertainment news. To receive cell broadcast messages through a channel,
mobile users must subscribe the channel through their mobile terminals.
The NetNumen U31 system provides the following channel management functions:
l Creating a channel
l Modifying a channel
l Deleting a channel
l Refreshing the information of channels
2.11.2.1 Creating a Channel
Abstract
This section describes how to create a channel and how to specify the channel ID, name,
and description for this channel.
Steps
1. In the left pane of the CBC Management window, expand ZTE > Resource
management, and then do one of the following to open the Create channel dialog
box.
l Right-click the Channel node, and then click Create.
2-65

l Click the Channel node, right-click an existing channel (if there is one) in the right
pane, and then click Create.
2. In the Create channel dialog box, set necessary parameters for the new channel, as
Figure 2-47 Create Channel Dialog Box
Table 2-5 describes the parameters in the Create channel dialog box.
Table 2-5 Channel Parameters
Parameter Description Value Range
Channel ID Channel No. 1 to 65535
User label Channel alias 1 to 20 characters
Description Channel description 1 to 50 characters
3. Click Add.
The created channel appears in the Create channel dialog box.
4. Click Close.
The created channel appears in the right pane of the CBC Management window.
Result
The created channel can be selected during the creation of a short message.
2-66

Follow-Up Action
In the CBC Management window showing the channel information, the following
operations can be performed as required:
l To modify the information of an existing channel, right-click the channel, and then click
Modify.
l To delete an existing channel, right-click the channel, and then click Delete.
l To show the latest channel information in the system, including the channels created
via other clients, right-click any existing channel, and then click Refresh.
2.11.3 Cell Management

A cell is the minimum scope in which broadcast messages are sent. An area (broadcast
domain) has one or multiple cells.
The NetNumen U31 system provides the following cell management functions:
l Refreshing the information of cells
l Resetting a cell
l Viewing the reset result of a cell
2.11.3.1 Refreshing Information of Cells
Abstract
This section describes how to refresh the information of cells displayed on the local client.
After the information of a cell is changed by a user through a client, another client can
receive the update information when the connection between the client and the server is
normal. If the connection between the client and the server has any problem, the cell
information cannot be updated in time for the client. In this case, you can perform the
refreshing operation to get the latest cell information from the server after the connection
between the client and the server recovers.
Steps
management, and then do one of the following to obtain the latest cell information
from the server:
l Right-click the Cell node, and then click Refresh.
l Click the Cell node, right-click any cell in the right pane, and then click Refresh.
2-67

2.11.3.2 Resetting a Cell
Abstract
This section describes how to reset a cell. After a cell is successfully reset, all short
messages to be broadcast in the cell are removed from related NEs.
Steps
management, and then do one of the following to open the Reset cell dialog box.
l Right-click the Cell node, and then click Reset.
l Click the Cell node, right-click any cell in the right pane, and then click Reset.
2. In the Reset cell dialog box, select the cell(s) to be reset, as shown in Figure 2-48.
Figure 2-48 Reset Cell Dialog Box
3. Click Ok.
2.11.3.3 Viewing Restart Result of Cells
Abstract
This section describes how to view the restart result of cells, including the information and
reset time of cells that succeeded or failed to restart.
Steps
management, right-click the Cell node, and then click Restart result to open The
history of Restart/Failure message box, as shown in Figure 2-49.
2-68

Figure 2-49 The History of Restart/Failure Message Box
The history of Restart/Failure message box shows the restart result of cells in two
list boxes.
l Restart Cell List shows the restart time and information of cells that succeeded
to restart.
l Failure Cell List shows the restart time and information of cells that failed to
restart.
Each cell in the list box is indicated in the format of MCC–MNC-LAC-SAC of the
broadcast domain that the cell belongs to.
2.11.4 Area Management

An area (broadcast domain) specifies the scope in which short messages are broadcast.
In the NetNumen U31 system, an area may comprise of several cells of the same base
station controller.
The NetNumen U31 system provides the following area management functions:
l Creating an area
l Modifying an area
l Deleting an area
l Refreshing the information of areas
2.11.4.1 Creating an Area
Abstract
This section describes how to create an area and how to specify the ID, name, and involved
cells for the area.
2-69

An area can only contain the cells of the same base station controller. The maximum
number of cells that can be managed by an area varies with different kinds of base station
controllers. For example,
l An area can include at most 200 cells of a GSM BSC.
l An area can include at most 600 cells of a WCDMA RNC.
Steps
management, and then do one of the following to open the Create area dialog box.
l Right-click the Area node, and then click Create.
l Click the Area node, right-click an existing area (if there is one) in the right pane,
and then click Create.
The Create area dialog box opens, as shown in Figure 2-50.
Figure 2-50 Create Area Dialog Box
Table 2-6 describes the parameters in the Create area dialog box.
Table 2-6 Area Parameters
Area ID Area No. 1 to 255
User label Area alias 1 to 20 characters
Cell list Cells involved in the area Cells of the same base station controller
2. In the Create area dialog box, set necessary parameters as follows:
2-70

a. Type a number in Area ID.
b. Type a name for the area in User label.

c. Click Scan. In the pop-up Select Cell List dialog box, select cells of the same
base station controller for the area, as shown in Figure 2-51. Then click Ok to
return to the Create area dialog box.
Figure 2-51 Select Cell List Dialog Box
3. Click Add.
The created area appears in the Create area dialog box.
4. Click Close.
The created area appears in the right pane of the CBC Management window.
Result
The created area can be selected during the creation of a short message.
Follow-Up Action
In the CBC Management window showing the area information, the following operations
can be performed as required:
l To modify the information of an existing area, right-click the area, and then click
Modify.
l To delete an existing area, right-click the area, and then click Delete.
l To show the latest area information in the system, including the areas created via
other clients, right-click any existing area, and then click Refresh.
2-71

2.11.5 Short Message Management

The NetNumen U31 system provides the following short message management functions:
l Creating, modifying, and deleting a short message
l Sending the alias of a cell
l Creating short messages in batch
l Exporting short messages
l Viewing the history of operations on a short message
l Viewing the sending status of a short message
2.11.5.1 Creating a Short Message
Abstract
This section describes how to create a short message and how to set the parameters of
the short message, including the channel, language, priority, sending mode, start time,
interval, repeat times, area, and the message content.
A short message can only be broadcast in the cells of the same base station controller.
The maximum number of cells in which a short message can be broadcast varies with
different kinds of base station controllers. For example,
l A short message can be broadcast in at most 200 cells of a GSM BSC.
l A short message can be broadcast in at most 600 cells of a WCDMA RNC.
Steps
management, right-click the Message node, and then click Create message.
The Create message dialog box, as shown in Figure 2-52.
2-72

Figure 2-52 Create Message Dialog Box
Table 2-7 describes the parameters that need to be set in the Create message dialog
box.
Table 2-7 Short Message Parameters
Set pa- Channel Provides the optional All created channels

rameters channels.
Language Specifies the language of l Chinese simplified

the short message. l English
Priority Specifies the priority of the l High: If the priority of a short

short message. message is High, this short
message will be immediately
broadcast after related NEs receive
it from the system.
l Background: If the priority of a
short message is Background, this
short message will be broadcast
2-73

only when there is no short message

with the priority of High or Normal.
l Normal: If the priority of a short
message is Normal, this short
message will be broadcast only
when there is no short message
with the priority of High.
Set time Send Provides the optional l Send by timer: The short message
mode sending modes of the short is sent on schedule.
message. l Send immediately: The short
message is sent immediately upon
being created.
Start time Specifies the start time The start time must be later than the
when the short message current system time.
shall be sent.
This drop-down list box
is activated only when
Send by timer is selected
from the Send mode
drop-down list box. That
means, it is not necessary
to set the start time for a
short message to be sent
immediately.
Interval Specifies the broadcast 2 to 2048 seconds

interval of the short
message.
Repeated Specifies the number 0 to 65535

times of times that the short 0 indicates that the short message will
message is broadcast be broadcast indefinitely.
repeatedly.
Area Specifies the scope (cell l Cell immediate display: The

or area) in which the short scope is determined by selected
message is broadcast. cells. Mobile terminals display the
Only the cells of the same short message on their screens
base station controller can immediately upon receiving it.
be selected. l Cell: The scope is determined by
selected cells. The short message
will be put into the message inbox
of mobile terminals instead of being
displayed on their screens.
2-74

l Area immediate display: The

scope is determined by selected
areas. Mobile terminals display the
short message on their screens
immediately upon receiving it.
l Area: The scope is determined by
selected areas. The short message
will be put into the message inbox
of mobile terminals instead of being
displayed on their screens.
Message content Specifies the content of the 0 to 1200 characters

short message.
2. In the Create message dialog box, set the parameters for the short message as
follows:
a. Under Set parameters, select a channel, language, and a priority for the short
message as required.
b. Under Set time, select a sending mode, set the start time when Send by timer is
selected, and set the broadcast interval and the repeat times.
c. Under Area, select a mode to set the broadcast scope.
l If Cell immediate display or Cell is selected, the Select Area dialog box
opens, as shown in Figure 2-53. Select the cells of the same base station
controller as required, and then click Ok.
Figure 2-53 Select Area Dialog Box
l If Area immediate display or Area is selected, the Select GS dialog box

opens, as shown in Figure 2-54. Select the area(s) as required, and then
click Ok.
2-75

Figure 2-54 Select GS Dialog Box
d. Under Message content, type the content of the short message, or click Load to
load the message content from a predefined TXT file.
3. Click Ok.
Result
A message box appears, prompting the successful creation of the short message.
Note:
l When the sending mode of the short message is Send immediately, a message box
will appear to prompt the creation failure if the system fails to send the short message
to the selected cells.
l When the sending mode of the short message is Send by timer, a message box will
appear to prompt the successful creation of the short message even the links to the
selected cells are broken because the system does not send the short message to
these cells immediately. The short message is sent to the selected cells only when
the start time is reached, and therefore, the short message can be successfully sent
when the links recover at that time.
Follow-Up Action
In the CBC Management window showing the short message information, the following
operations can be performed as required:
l To modify the information of an existing short message, right-click the short message,
and then click Modify.
l To delete an existing short message, right-click the short message, and then click
Delete.
2-76

l To view the history of operations on a short message, right-click the short message,
and then click Query historical message.
2.11.5.2 Sending the Alias of a Cell
Abstract
This section describes how to create a short message to broadcast the alias (user label)
of a cell to all mobile terminals in the cell.
Steps
management, right-click the Message node, and then click SendBtsAlias.
The Select Area dialog box opens, as shown in Figure 2-55.
Figure 2-55 Select Area Dialog Box
2. In the Select Area dialog box, select the cell for broadcasting its alias, and then click
Ok.
Note:
Multiple cells of the same base station controller can be selected in the dialog box.
The Send message by cell’s user label dialog box opens, as shown in Figure 2-56.
2-77

Figure 2-56 Send Message by Cell’s User Label Dialog Box
3. In the Send message by cell’s user label dialog box, set necessary parameters for
the short message. For the description of each parameter in the dialog box, refer to
the previous section “Creating a Short Message”.
4. Click Ok.
Follow-Up Action
The NetNumen U31 system sends the short message containing the cell alias to the
selected cell(s), which will then broadcast the short message to mobile terminals in the
cell(s).
2.11.5.3 Creating Short Messages in Batch
Abstract
This section describes how to create multiple short messages in batch by importing a
predefined TXT file, which contains the information of multiple short messages.
Context
A TXT file can be predefined to specify the information of multiple short messages, which
are separated by semicolon. The following is the content format in a TXT file containing
only one short message.
2-78

Command:Sending mode,Channel,Area,Cell list,Start

date,Start time,Interval,Repeat times,Language,Encoding
form,Content,Priority;
For example, a TXT file has a content as follows:
BSMS:0,1,3,"460-3-1-1",2011-07-01,19:15:47,2,55,0,17,"test",0;
Table 2-8 describes each field in the information of a short message in addition to the
command for the batch sending of multiple short messages.
Table 2-8 Field Description
Field Description Example
Command Specifies the command (BSMS) used to create BSMS

and send multiple short messages in batch.
Sending mode Specifies the sending mode of short messages. 0

l 0: send immediately.
If the value of this field is set to 0, the Start
date and Start time fields are invalid. The
short messages will be sent immediately
after they are created.
l 1: send on schedule.
Channel Specifies the channel to which the short 1

messages belong.
Area Specifies the cells or areas in which the short 3

messages shall be broadcast.
l 13: area
l 10: area, supporting immediate display of
short messages
l 3: cell
l 0: cell, supporting immediate display of
short messages
Cell list Specifies the cells in which the short messages "460-3-1-1&460-3-1-1"
shall be broadcast.
The information format of each cell is:
"MCC-MNC-LAC-SAC of the broadcast domain
that the cell belongs to”. Multiple cells in a cell
list are separated by &.
Start date Specifies the start date when the system starts 2011-07-01
sending the short messages to related NEs. The
date format is: YYYY-MM-DD.
Start time Specifies the start time when the system starts 19:15:47
sending the short messages to related NEs. The
date format is: HH-MM-SS.
2-79

Field Description Example
Interval Specifies the broadcast interval of the short 2

messages. The field value ranges from 2 to
2048.
Repeat times Specifies the number of repeat times of the short 55

messages. The field value ranges from 0 to
65535.
Language Specifies the language of the short messages to 1

be broadcast.
l 0: Simplified Chinese
l 1: English
Encoding form Specifies the encoding form for the short

messages.
l 1: UCS2
l 2: 7bit
Content Specifies the content of the short message, “test”

which should be enclosed by double quotation
marks.
Priority Specifies the priority of the short message. 0

l 0: high
l 1: medium
l 2: low
The values (0, 1, and 2) of this field correspond
to the options (High, Normal, and Background)
in the Priority drop-down box in the Create
message dialog box as described in the previous
section “Creating a Short Message”.
Steps
1. In the left pane of the CBC Management window, right-click the Message node, and
then click Send Batch Message.
2. In the pop-up Open dialog box, select the directory where the predefined TXT file is
saved, select the TXT file, and then click Open.
A message box appears, indicating the batch creation of short messages succeeds.
2.11.5.4 Exporting Short Messages
Abstract
This section describes how to export the existing short messages in the NetNumen U31
system to an XLS or CSV file.
2-80

Context
In addition to exporting all short messages, the NetNumen U31 system supports exporting
short messages by status, for example, exporting the short messages in Unsent, Sending,
or Finished status.
The following example shows how to export all existing short messages in the NetNumen
U31 system to a file.
Steps
1. In the left pane of the CBC Management window, right-click the All node under
Message, and then click Report all.
2. In the Open dialog box, select a directory where you want to save the file, type a file
name, select a file format, and then click Save.
Result
A file containing the information of all short messages appears in the specified directory.
2.11.5.5 Viewing the History of Operations on a Short Message
Abstract
The NetNumen U31 system allows you to view the history of operations on a short
message, including the time, channel ID, message ID, action, and response related to
each operation. The following example shows how to view the history of operations on a
short message in Finished status.
Steps
1. In the left pane of the CBC Management window, click the Finished node under
Message to show all short messages in Finished status in the right pane.
2. Right-click the short message to be viewed, and then click Query historical message.
The Query historical message dialog box opens, as shown in Figure 2-57.
2-81

Figure 2-57 Query Historical Message Dialog Box
All operations that have been performed on the short message are listed in the Query
historical message dialog box.
2.11.5.6 Viewing the Sending Result of a Short Message
Abstract
This section describes how to view the sending result of a short message in Sending
status, including the number of times that the short message has been successfully sent,
and the cause of sending failures.
Steps
1. In the left pane of the CBC Management window, click the Sending node under
Message to show all short messages in sending status in the right pane.
2. Right-click the short message to be viewed, and then click Query Sending State.
2-82

Figure 2-58 Sending Result
The Success cell list box shows the number of times that the short message has
been successfully sent. The Failure cell list box shows the cause of message sending
failures.
2.12 Configuration Data Collection

2.12.1 Introduction to Configuration Data Collection
The NetNumen U31 system provides a configuration data collection tool for collecting
configuration data from Operation & Maintenance Modules (OMM) of managed Network
Elements (NEs). It generates a file for each type of configuration data and stores all
configuration data files on the server. You can get these files from the server, and view the
contents in the files on the client.
Note:
NetNumen U31, that is, the network Element Management System (EMS), can only
successfully complete the configuration data collection when the OMMs also support the
collection of configuration data.
Before collecting configuration data, you need to create a template to specify the
configuration data you want to collect.
2-83

2.12.2 Creating a Template for Configuration Data Collection

Abstract
This section describes how to create specify the configuration data to be collected in a
template before configuration data collection.
Steps
1. In the client window, select Configuration > CM DataCollect > Template Manager
on the menu bar.
The Template Management tab appears, as shown in Figure 2-59.
Figure 2-59 Template Management Tab
2. On the Template Management tab, click on the toolbar to open the Create
template dialog box, as shown in Figure 2-60.
2-84

Figure 2-60 Create Template Dialog Box
3. In the Create template dialog box, set the parameters for the template as follows:
a. In the Name box, type a name for the new template.
b. From the Ne Type drop-down list box, select an NE type.
c. In the Description box, type additional information of the template when

necessary.
d. Under Object for select, select the type(s) of configuration data you want to
collect.
If MERGE is selected, the system will merge the same type of configuration data
collected from multiple subnetworks in one file when this template is used.
If NO MERGED is selected, the system will save the same type of configuration
data collected from multiple subnetworks in multiple files separately.
e. Under Attribute for select list box, select specific configuration data to be
collected.
Note:
The dimmed attributes are those must be collected when the corresponding type
is selected. You can only change the selection of those activated check boxes.
4. Click OK.
2-85

Result
The created template appears on the Template Management tab. It can be used for report
management.
Follow-Up Action
You can modify, view, or delete an existing template on the Template Management tab by
clicking an appropriate button on the toolbar or an appropriate command on the shortcut
menu.
2.12.3 Collecting Configuration Data

Abstract
Users can use a collection template to start the collection of specific configuration data.
The system collects the required configuration data from Operation & Maintenance
Modules (OMMs), stores the collected data on the server, and then transfers the
configuration data to the client. The client saves the received configuration data in CSV
files in the default directory.
The following describes how to use a template for collecting configuration data.
Prerequisites
The configuration data collection template to be used has been created.
Steps
1. In the client window, select Configuration > CM DataCollect > Report Manager. The
Configuration Report management tab appears.
2. On the Configuration Report management tab, click on the toolbar. The Get
Report dialog box opens.
3. In the Get Report dialog box, select an NE type from the NE TYPE drop-down list box,
select the NE(s) on the SUBNET tree, and then select the template to be used in the
template list, as shown in Figure 2-61.
2-86

Figure 2-61 Get Report
4. Click OK.
Result
The system collects the required configuration data from the selected NEs according to the
template, and generates the configuration data report file(s) on the local client, as shown
in Figure 2-62.
Figure 2-62 Collection Result of Configuration Data
Follow-Up Action
After collecting configuration data, the following operations can be performed:
l View the configuration data in a report file as follows:
Double-click the corresponding row on the Configuration Report management tab,
and in the opened folder where the report file is saved, double-click the file to open
the file.
l Save the report file in another directory as follows:
2-87

1. Click the report file to be saved, and then click on the toolbar. Or right-click the
report file and then click Export current report list.
2. In the Open dialog box, select a directory where you want to save the report file
from the Look in drop-down list box, and then click Open.
2.13 Radio Parameter Import

2.13.1 Introduction to Radio Data Import
The NetNumen U31 system provides several radio data import modules to support the
import of radio configuration data from XML files to managed NEs. These NEs modify
their radio configuration according to the imported configuration information, report the
importing process, and generate log files containing the import result.
The radio data import module varies with the type of NEs, such as UMTS, GSM, and LTE
FDD NEs. However, the procedures for importing radio data to different types of NEs are
similar.
2.13.2 Importing Radio Data

Abstract
This section provides an example showing how to import radio configuration data from an
XML file to specific UMTS NEs.
Prerequisites
The XML file containing the configuration information is available.
Steps
1. In the client window, select Configuration > UMTS Configuration Application >
Radio Config Data Import. The Radio Config Data Import dialog box opens, as
2-88

Figure 2-63 Radio Config Data Import Dialog Box
2. Click Select. In the Open dialog box, select the XML file to be imported, and then click
Open. The file path appears in the File Path box.
3. Select the target NE from the Select RNC drop-down list box.
4. Click Execute.
The system starts importing the radio configuration data from the XML file to the
selected NE, and displays the import process in the Output Info pane.
5. After the import is completed, click View Log. The Result Data message box opens,
showing all information recorded during the import process.
2-89

This page intentionally left blank.
2-90

Figures
Figure 2-1 Selecting a Product Type ......................................................................... 2-2
Figure 2-2 Selecting an Operation ............................................................................ 2-3
Figure 2-3 Selecting an RNC .................................................................................... 2-3
Figure 2-4 Selecting Node Bs ................................................................................... 2-3
Figure 2-5 InterNE Modify Dialog Box ....................................................................... 2-5
Figure 2-6 NE Relation Management Dialog Box ...................................................... 2-6
Figure 2-7 NE Relation Data Filter Dialog Box .......................................................... 2-7
Figure 2-8 Filtering Result......................................................................................... 2-8
Figure 2-9 Query Result of Stability Events............................................................. 2-11
Figure 2-10 Task Management (MML Timing Task) ................................................. 2-14
Figure 2-11 Create Task Dialog Box (Base info Tab) ............................................... 2-15
Figure 2-12 Create Task Dialog Box (Policy Tab) .................................................... 2-16
Figure 2-13 NE Stability Manager Dialog Box (Maintain Plan Tab) .......................... 2-17
Figure 2-14 Add Maintain Plan Dialog Box.............................................................. 2-18
Figure 2-15 Result of Querying Maintenance Plans ................................................ 2-20
Figure 2-16 Setting Conditions for Status Query ..................................................... 2-24
Figure 2-17 Query Result of Maintenance Status .................................................... 2-24
Figure 2-18 Setting the Status of a Base Station (1)................................................ 2-26
Figure 2-21 VIP NodeB Priority Query and Set Dialog Box ..................................... 2-30
Figure 2-22 Priority Query Result............................................................................ 2-31
Figure 2-23 Setting the Priority of a Base Station (1)............................................... 2-32
Figure 2-26 Inventory Management Dialog Box ...................................................... 2-36
Figure 2-27 Inventory Information of a Network Element......................................... 2-38
Figure 2-28 SW and FW Inventory Dialog Box ........................................................ 2-39
Figure 2-29 Task Management (MML Timing Task) ................................................. 2-42
Figure 2-30 Creating an Inventory Export Task (1) .................................................. 2-43
Figure 2-31 Creating an Inventory Export Task (2) .................................................. 2-44
Figure 2-32 Transfer Base Station Dialog Box ........................................................ 2-45
I
Figure 2-33 Offline Data Dialog Box........................................................................ 2-49

Figure 2-34 Result Data Dialog Box ........................................................................ 2-51
Figure 2-35 Configuration Data Export.................................................................... 2-53
Figure 2-36 Add Network Element Dialog Box ........................................................ 2-53
Figure 2-37 Selecting a File Format ........................................................................ 2-54
Figure 2-38 Configuration Data Import .................................................................... 2-55
Figure 2-39 Selecting an Operate Object Number................................................... 2-56
Figure 2-40 Cell Tool Dialog Box............................................................................. 2-57
Figure 2-41 Selecting Subnetworks......................................................................... 2-58
Figure 2-42 Check Result ....................................................................................... 2-59
Figure 2-43 Relation User Label Manage Dialog Box .............................................. 2-61
Figure 2-44 Local Cells and External Cells.............................................................. 2-62
Figure 2-45 Status Change of Short Message......................................................... 2-63
Figure 2-46 CBC Management Window .................................................................. 2-65
Figure 2-47 Create Channel Dialog Box.................................................................. 2-66
Figure 2-48 Reset Cell Dialog Box .......................................................................... 2-68
Figure 2-49 The History of Restart/Failure Message Box ........................................ 2-69
Figure 2-50 Create Area Dialog Box ....................................................................... 2-70
Figure 2-51 Select Cell List Dialog Box ................................................................... 2-71
Figure 2-52 Create Message Dialog Box................................................................. 2-73
Figure 2-53 Select Area Dialog Box ........................................................................ 2-75
Figure 2-54 Select GS Dialog Box .......................................................................... 2-76
Figure 2-55 Select Area Dialog Box ........................................................................ 2-77
Figure 2-56 Send Message by Cell’s User Label Dialog Box................................... 2-78
Figure 2-57 Query Historical Message Dialog Box .................................................. 2-82
Figure 2-58 Sending Result .................................................................................... 2-83
Figure 2-59 Template Management Tab .................................................................. 2-84
Figure 2-60 Create Template Dialog Box................................................................. 2-85
Figure 2-61 Get Report ........................................................................................... 2-87
Figure 2-62 Collection Result of Configuration Data................................................ 2-87
Figure 2-63 Radio Config Data Import Dialog Box................................................... 2-89
II
Tables
Table 1-1 Wireless Configuration Application Functions ............................................ 1-1
Table 1-2 Wireless Configuration Application Tools ................................................... 1-2
Table 2-1 Stability Report ........................................................................................ 2-13
Table 2-2 Description of the Parameters in the Add Maintain Plan Dialog
Box ........................................................................................................ 2-18
Table 2-3 Description of Menus in the Inventory Management Dialog Box............... 2-36
Table 2-4 Operations in the SW/FW Inventory Dialog Box....................................... 2-39
Table 2-5 Channel Parameters................................................................................ 2-66
Table 2-6 Area Parameters ..................................................................................... 2-70
Table 2-7 Short Message Parameters ..................................................................... 2-73
Table 2-8 Field Description...................................................................................... 2-79
III
Tables
This page intentionally left blank.

Glossary
BSC
- Base Station Controller
BTS
- Base Transceiver Station
CBC
- Cell broadcast center
CID
- Cell ID
EMS
- Network Element Management System
FDD
- Frequency Division Duplex
GSM
- Global System for Mobile Communication
GSM-R
- GSM for Railway
GUI
- Graphical User Interface
J2EE
- JAVA 2 platform Enterprise Edition
LAC
- Location Area Code
LTE
- Long Term Evolution
MCC
- Mobile Country Code
MML
- Man Machine Language
MNC
- Mobile Network Code
NE
- Network Element
OMM
- Operation & Maintenance Module
V
RNC
- Radio Network Controller
SAC
- Service Area Code
TD-SCDMA
- Time Division-Synchronization Code Division Multiple Access
TDD
- Time Division Duplex
UMTS
- Universal Mobile Telecommunication System
VIP
- Very Important Person
WCDMA
- Wideband Code Division Multiple Access
VI

Netnumen U31 r18 Unified Element Management System Configuration Application Operastion Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Netnumen U31 r18 Unified Element Management System Configuration Application Operastion Guide PDF

Uploaded by

Copyright:

Available Formats

NetNumen™ U31 R18

Unified Element Management System

Revision No. Revision Date Revision Reason

R1.0 2011-09–23 First Edition

Serial Number: SJ-20110823134613-010

Publishing Date: 2011-09-23(R1.0)

Chapter 2 Wireless Configuration Application Operations .................... 2-1

What Is in This Manual

l consistency check of user labels

1.1 Purpose of Wireless Configuration Application

1.2 Wireless Configuration Application Functions

Table 1-1 Wireless Configuration Application Functions

Interconnection parameter Compares interconnection parameters in batch between a base

NE stability management l Queries the stability events occurring in an NE during a

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

Inventory management Manages the hardware and software inventory information

Table 1-2 Wireless Configuration Application Tools

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

Base station priority

Base station transfer

Neighbor cell relation

Radio data import √ √ - - - -

1.3 Implicit Prerequisites

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

2.1 Interconnection Parameter Management

The prerequisite of interconnection parameter management is that the relations between

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

To start interconnection parameter management, select Configuration > Wireless Config

2.1.2 Comparing Interconnection Parameters in Batch

Figure 2-1 Selecting a Product Type

3. Select Compare, and then click Next, as shown in Figure 2-2.

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

Figure 2-2 Selecting an Operation

Figure 2-3 Selecting an RNC

Figure 2-4 Selecting Node Bs

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

2.1.3 Modifying Interconnection Parameters in Batch

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

l The comparison result of interconnection parameters has been exported to an XLS

Figure 2-5 InterNE Modify Dialog Box

5. In the InterNE Modify dialog box, click .

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

2.2 Network Element Relation Management

Figure 2-6 NE Relation Management Dialog Box

In the NE Relation Management dialog box, users can:

2.2.2 Searching for Specific Network Element Relations

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

Figure 2-7 NE Relation Data Filter Dialog Box

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

Figure 2-8 Filtering Result

2.2.3 Exporting All Network Element Relations to an XLS File

4. Click OK when prompted with the message of successful export.

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

2.3 Network Element Stability Management

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

2.3.2 Managing Stability Events

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

Figure 2-9 Query Result of Stability Events

2.3.2.2 Exporting the Query Result of Stability Events to an XLS File

2. In the Save dialog box, do the following:

SJ-20110823134613-010|2011-09-23(R1.0) ZTE Proprietary and Confidential

3. Click OK when prompted with the message of successful export.