U31 R18 Configuration Application Operation Guide

NetNumen U31 R18
Unified Element Management System
Configuration Application Operation Guide

Version: V12.12.43
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 2013 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
2013-06-20
First edition
Serial Number: SJ-20130524154927-012

Publishing Date: 2013-06-20 (R1.0)
SJ-20130524154927-012|2013-06-20 (R1.0)
ZTE Proprietary and Confidential
Contents
About This Manual ......................................................................................... I
Chapter 1 Wireless Configuration Application Overview ....................... 1-1
1.1 Functions........................................................................................................... 1-1
1.2 Implicit Prerequisites .......................................................................................... 1-3
Chapter 2 Wireless Configuration Application Operations .................... 2-1

2.1 Interconnection Parameter Management ............................................................. 2-1
2.1.1 Comparing Interconnection Parameters in Batches .................................... 2-2
2.1.2 Modifying Interconnection Parameters in Batches ...................................... 2-4
2.2 NE Relation Management ................................................................................... 2-6
2.2.1 Filtering NE Relations ............................................................................... 2-6
2.2.2 Exporting NE Relations to an XLS File....................................................... 2-8
2.3 NE Stability Management.................................................................................... 2-8
2.3.1 Managing Stability Events....................................................................... 2-10
2.3.2 Managing Maintenance Plans ................................................................. 2-15
2.4 Base Station Status Management ..................................................................... 2-19
2.4.1 Querying Base Station Statuses .............................................................. 2-20
2.4.2 Setting the Status of a Base Station ........................................................ 2-23
2.4.3 Exporting Base Station Statuses ............................................................. 2-25
2.4.4 Importing Base Station Statuses.............................................................. 2-26
2.5 Base Station Priority Management..................................................................... 2-27
2.5.1 Querying Base Station Priorities .............................................................. 2-28
2.5.2 Setting the Priority of a Base Station........................................................ 2-30
2.5.3 Exporting Base Station Priorities ............................................................. 2-31
2.5.4 Importing Base Station Priorities.............................................................. 2-32
2.6 Site Transfer .................................................................................................... 2-33
2.6.1 Exporting Configuration Data of a Source Site.......................................... 2-35
2.6.2 Transferring an Online Site ..................................................................... 2-36
2.6.3 Transferring an Offline Site ..................................................................... 2-36
2.6.4 Viewing Operation Results Related to Site Transfer .................................. 2-38
2.6.5 Halting a Site Transfer Process ............................................................... 2-39
2.7 Inter-Element Configuration Data Import and Export ........................................... 2-40
2.7.1 Exporting Configuration Data .................................................................. 2-40
2.7.2 Importing Configuration Data................................................................... 2-43
I
SJ-20130524154927-012|2013-06-20 (R1.0)
2.8 Neighbor Cell Tool ............................................................................................ 2-44

2.8.1 Verifying Attributes Consistency .............................................................. 2-45
2.8.2 Importing Modified Attributes................................................................... 2-48
2.9 User Label Relation Management ..................................................................... 2-49
2.9.1 Verifying User Label Consistency ............................................................ 2-49
2.10 Cell Maintenance Status Management............................................................. 2-52
2.10.1 Querying Cell Statuses ......................................................................... 2-52
2.10.2 Setting Cell Statuses ............................................................................ 2-53
2.11 Cell Broadcast Management ........................................................................... 2-55
2.11.1 Short Message Status........................................................................... 2-55
2.11.2 Opening the CBC Management Window ................................................ 2-57
2.11.3 Channel Management........................................................................... 2-57
2.11.4 Cell Management ................................................................................. 2-59
2.11.5 Area Management ................................................................................ 2-64
2.11.6 Short Message Management................................................................. 2-66
2.12 Configuration Data Collection .......................................................................... 2-75
2.12.1 Creating a Configuration Data Collection Template ................................. 2-76
2.12.2 Collecting Configuration Data ................................................................ 2-78
2.13 Radio Configuraiton Data Import ..................................................................... 2-80
2.13.1 Overview ............................................................................................. 2-80
2.13.2 Importing Radio Configuration Data ....................................................... 2-81
2.14 GSM BCCH Frequency Scheduling Tool .......................................................... 2-82
2.14.1 Importing the Frequency List ................................................................. 2-83
2.14.2 Generating a Scheduled Task................................................................ 2-85
2.15 TD Carrier Frequency Maintenance Management............................................. 2-87
2.15.1 Querying the Maintenance Status of a Carrier Frequency........................ 2-88
2.15.2 Setting the Maintenance Status of a Carrier Frequency........................... 2-90
Figures............................................................................................................. I
Tables .............................................................................................................V
Glossary .......................................................................................................VII
II
SJ-20130524154927-012|2013-06-20 (R1.0)
About This Manual

Purpose
This manual provides instructions for the centralized configuration and maintenance of
radio access network products in the NetNumenTM U31 R18 Unified Element Management
System (NetNumen U31).
Intended Audience
This manual is intended for:
l
l
Maintenance engineers
Network planning and optimization engineers
What Is in This Manual

This manual contains the following chapters:
Chapter
Summary
1, Wireless Configuration
Provides an overview of the wireless configuration application
Application Overview
module in the NetNumen U31 system, including supported

functions and radio access systems.
2, Wireless Configuration
Describes how to use the wireless configuration application
Application Operations
module for centralized configuration and maintenance.
Related Documentation
The following documentation is related to this manual:
l
l
NetNumen U31 R18 Unified Element Management System Topology Management

Operation Guide
NetNumen U31 R18 Unified Element Management System MML Command
Reference
Conventions
This manual uses the following typographical conventions:
Typeface
Meaning
Caution: indicates a potentially hazardous situation. Failure to comply can result in
moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a certain topic.
I
SJ-20130524154927-012|2013-06-20 (R1.0)
II
SJ-20130524154927-012|2013-06-20 (R1.0)
Chapter 1
Wireless Configuration
Application Overview
The NetNumen U31 system provides a wireless configuration application module that
supports centralized configuration and maintenance of radio access network products. A
configuration or maintenance operation may be required on multiple Network Elements
(NEs) at the same time. Such inter-NE operation cannot be completed by individual
Operation & Maintenance Modules (OMMs) of these NEs. The wireless configuration
application module can be used to implement interNE configuration and maintenance
operations in a centralized manner.
Table of Contents
Functions ...................................................................................................................1-1
Implicit Prerequisites ..................................................................................................1-3
1.1 Functions
For a description of the functions supported by the wireless configuration application
module, refer to Table 1-1.
Table 1-1 Wireless Configuration Application Functions
Function
Description
Interconnection parameter
Compares interconnection parameters in batches between a
management
BSC/RNC and corresponding BTSs/Node Bs, and modifies

inconsistent interconnection parameters in batches.
NE relation management
Manages the relations between a BSC/RNC and the BTSs/Node

Bs under its control.
NE stability management
Queries stability events occurring in an NE during a period

and exports the query results as a stability report.
Adds the information of an NE maintenance plan to exclude

the stability events occurring during maintenance in the
stability report.
Base station status management
Queries, sets, imports, and exports base station statuses.
Base station priority management
Queries, sets, imports and exports base station priorities.
Inventory management
Manages the hardware, software, and firmware inventory

uploaded from NEs.
1-1
SJ-20130524154927-012|2013-06-20 (R1.0)
NetNumen U31 R18 Configuration Application Operation Guide
Function
Description
Site transfer
Supports online and offline site transfer.
Inter-element configuration data
Exports and imports configuration data in file format between
import and export
different NEs for quick configuration.
Neighbor cell tool
Verifies the consistency of attributes between an OMM and

related external cells to ensure correct neighbor relations, and
verifies the integrity of neighbor relations for a cell.
User label relation management
Verifies the consistency between the user labels of local cells

and those specified in neighbor relations.
Cell broadcast management
Provides management functions for the cell broadcast

service, including channel management, cell management,
area (broadcast domain) management, and short message
management.
Cell status management
Queries and sets cell statuses.
Configuration data collection
Collects configuration data of NEs from corresponding OMMs.
Radio configuration data import
Imports radio configuration data from a predefined XML file to

specific NEs.
Note:
l
BSC = Base Station Controller
RNC = Radio Network Controller
BTS = Base Transceiver Station
CBC = Cell Broadcast Center
The available wireless configuration application functions vary with different radio access
systems. For a description of supported functions for different systems, refer to Table 1-2.
Table 1-2 Supported Functions for Different Radio Access Systems
Function
UMTS
GSM
GSM-R
LTE-TDD
LTE-FDD
TD-SCDMA
Interconnection
parameter
management
NE relation
management
NE stability
management
Base station status
management
Base station priority
management
1-2
SJ-20130524154927-012|2013-06-20 (R1.0)
Chapter 1 Wireless Configuration Application Overview
Function
UMTS
GSM
GSM-R
LTE-TDD
LTE-FDD
TD-SCDMA
Inventory management
Site transfer
Inter-element
configuration data
import and export
Neighbor cell tool
User label relation
management
Cell broadcast
management
Cell status
management
Configuration data
collection
Radio configuration
data import
Note:
l
UMTS = Universal Mobile Telecommunication System
GSM = Global System for Mobile communication
GSM-R = GSM for Railway
LTE-TDD = Long Term Evolution-Time Division Duplex
LTE-FDD = Long Term Evolution-Frequency Division Duplex
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.2 Implicit Prerequisites

For all operations subsequent to this section, the following prerequisites are presumed to
have been met:
l
l
l
l
The NetNumen U31 client has been started and successfully connected to the server.
The communication between the NetNumen U31 server and managed NEs is normal.
Users have successfully started the NE agent of the NEs that are to be configured or
maintained.
The permissions for wireless configuration application operations have been acquired.
1-3
SJ-20130524154927-012|2013-06-20 (R1.0)
This page intentionally left blank.
1-4
SJ-20130524154927-012|2013-06-20 (R1.0)
Chapter 2
Wireless Configuration
Application Operations
Table of Contents
Interconnection Parameter Management ....................................................................2-1
NE Relation Management ..........................................................................................2-6
NE Stability Management ...........................................................................................2-8
Base Station Status Management ............................................................................2-19
Base Station Priority Management ...........................................................................2-27
Site Transfer.............................................................................................................2-33
Inter-Element Configuration Data Import and Export.................................................2-40
Neighbor Cell Tool ....................................................................................................2-44
User Label Relation Management ............................................................................2-49
Cell Maintenance Status Management .....................................................................2-52
Cell Broadcast Management ....................................................................................2-55
Configuration Data Collection ...................................................................................2-75
Radio Configuraiton Data Import ..............................................................................2-80
GSM BCCH Frequency Scheduling Tool ..................................................................2-82
TD Carrier Frequency Maintenance Management ....................................................2-87
2.1 Interconnection Parameter Management

The interconnection parameter management allows users to compare and modify
interconnection parameters in batches to ensure parameter consistency between a Base
Station Controller (BSC)/Radio Network Controller (RNC) and the Base Transceiver
Stations (BTSs)/Node Bs under its control in a GSM, UMTS, or TD-SCDMA network.
Note:
Before performing interconnection parameter management, users must specify the
BSC/RNC to which each BTS/Node B belongs in the NetNumen U31 system.
2-1
SJ-20130524154927-012|2013-06-20 (R1.0)
2.1.1 Comparing Interconnection Parameters in Batches

This procedure describes how to compare the interconnection parameters between an
RNC and the Node Bs under its control in a UMTS network to verify the consistency of the
interconnection parameters.
Prerequisite
Users have specified the RNC to which each Node B belongs in the NetNumen U31
system.
Steps
1. In the client window, select Configuration > Common Wireless Configuration
Application > InterNE Compare from the menu bar. The InterNE Manage Option
dialog box is displayed, see Figure 2-1.
Figure 2-1 InterNE Manage Option Dialog BoxSelecting the Product Type
2. Select the product type (for example, TD-SCDMA), and click Next. The available
operations are displayed, see Figure 2-2.
2-2
SJ-20130524154927-012|2013-06-20 (R1.0)
Chapter 2 Wireless Configuration Application Operations
Figure 2-2 InterNE Manage Option Dialog BoxSelecting the Management Type
3. Select Compare, and then click Next. An NE tree containing all managed RNCs in
the system is displayed, see Figure 2-3.
Figure 2-3 InterNE Manage Option Dialog BoxSelecting RNCs
4. Select the required RNCs, and then click Next. The selected RNCs and the Node Bs
under its control are displayed in the NE tree, see Figure 2-4.
2-3
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-4 InterNE Manage Option Dialog BoxSelecting the NODEBs
5. Select the required NodeBs, and then click OK. The InterNE Batch Compare Result
dialog box is displayed.
6. Expand the NE tree in the left pane, and select the RNC. The comparison result of
interconnection parameters between the RNC and the selected Node Bs is displayed
on the Statistics tab in the right pane.
Note:
In the Comparative result (Y/N) column, Y indicates consistent interconnection
parameters, and N indicates inconsistent interconnection parameters.
7. To show the comparison details of the interconnection parameters between a specific

Node B and the RNC, click the tab corresponding to the Node B ID.
8. To export the comparison result to an XLS file, do the following:
a. In the InterNE Batch Compare Result dialog box, click Export. The Save dialog
box is displayed.
b. Select a directory for saving the comparison result, enter a file name, and then
click Save. A message confirming the successful data export is displayed.
An XLS file containing the comparison result is available in the selected directory.
Users can open the XLS file to view the interconnection parameters exported from the
system.
End of Steps
2.1.2 Modifying Interconnection Parameters in Batches

This procedure describes how to modify inconsistent interconnection parameters between
an RNC and the controlled Node Bs in a UMTS network.
2-4
SJ-20130524154927-012|2013-06-20 (R1.0)
Note:
The interconnection parameter modification function is only available for UMTS and
TD-SCDMA products.
Prerequisite
Users have compared the interconnection parameters between the RNC and the Node Bs
and exported the comparison results to an XLS file.
Steps
1. Open the XLS file containing the comparison results.
2. Modify inconsistent parameters, and change the modification status corresponding to
the modified parameters to "Y".
3. Save and close the XLS file.
Application > InterNE Compare from the menu bar. The InterNE Manage Option
5. Select UMTS, and then click Next.
6. Select Modify, and then click Next. The InterNE Modify dialog box is displayed, see
Figure 2-5.
Figure 2-5 InterNE Modify Dialog Box
7. Click
. The Open dialog box is displayed.
8. Select the directory where the modified XLS file is saved, click the XLS file, and then
click Open. The selected file path is displayed in the InterNE Modify dialog box.
9. Click OK. The InterNE Batch Compare Result dialog box is displayed, showing the
modification results of interconnection parameters between the RNC and different
Node Bs on separate tabs.
End of Steps
2-5
SJ-20130524154927-012|2013-06-20 (R1.0)
2.2 NE Relation Management

In the NetNumen U31 system, a BSC/RNC and the BTSs/Node Bs under its control can
be deployed separately. For example, an RNC is configured and maintained by an OMM,
but a Node B under its control is managed by another OMM. Considering this possibility,
users are required to add an NE relation for each BTS/Node B in the system. The NE
relation specifies which BSC/RNC is used to control a BTS/Node B.
The NE relation management allows users to view, filter, and export the NE relations
between BSCs/RNCs and BTSs/Node Bs managed by the NetNumen U31 system.
2.2.1 Filtering NE Relations

This procedure describes how to filter out specific NE relations in the system.
Prerequisite
l
l
The NE Relation Management dialog box is displayed.

The NE relation has been configured in the NE Relation Management dialog box.
Steps
1. Click Filter. The NE Relation Data Filter dialog box is displayed, see Figure 2-6.
2-6
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-6 NE Relation Data Filter Dialog Box
2. Set the related parameters. For a description of the parameters, refer to Table 2-1.
Table 2-1 Description of NE Relation Filtration Parameters
Parameter
Description
Product
Options:
l
GSM
TD
UMTS
All
In this example, All is selected.

OMM-R Name/OMM-R SubnetWorkID/OMM-R
Set the filtration keywords.
NE ID/OMM-B Name/OMM-B
In this example, set OMM-B NEID to 8.
SubnetWorkID/OMM-B NEID
3. Click OK. All NE relations related to the subnets whose IDs contain the keyword "7"
are displayed in the NE Relation Management dialog box, see Figure 2-7.
2-7
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-7 NE Relation Filtration Results
4. To show all NE relations in the NE Relation Management dialog box again, click
Filter, select All from the Product list, clear all filtering keywords, and then click OK.
End of Steps
2.2.2 Exporting NE Relations to an XLS File

This procedure describes how to export NE relations from the NetNumen U31 system to
an XLS file.
Steps
Application > NE Relation Management. The NE Relation Management dialog
box is displayed, showing all NE relations specified in the system.
2. Click Export. The Save dialog box is displayed.
3. Select a directory for saving the exported NE relations, enter a file name, and then click
Save. A message confirming the successful export of the NE relations is displayed.
4. Click OK. An XLS file containing the NE relations is generated in the selected directory.
End of Steps
2.3 NE Stability Management

The NetNumen U31 system collects stability events from all managed NEs, stores
the collected events in the database, and generates statistical reports as required.
The collected events include those occurring during maintenance. Users can add the
maintenance information in the system to exclude the events during maintenance from
the stability report because these events do not reflect the actual stability of NEs.
The following explains two concepts involved in NE stability management: stability event
and maintenance plan.
2-8
SJ-20130524154927-012|2013-06-20 (R1.0)
Stability Event
A stability event refers to a failure event occurring in a board of an NE that influences
the NE stability. An NE collects stability events from all its boards and sends the collected
information to the alarm mail box of the NetNumen U31 system. The stability management
application monitors the alarm mail box in real time and determines the severity level of
each stability event in accordance with the weight of board type and the weight of board
redundancy mode.
l
Weight of board type

The system sets the weight of board type for an event depending on the type of the
board where the event occurs. Boards in an NE are classified into two types: interface
board and processing board. The weight of a processing board event is higher than
that of an interface board event.
Weight of board redundancy mode

The system sets the weight of board redundancy mode for an event depending on
the redundancy mode of the board where the event occurs, the quantity of redundant
boards, board type, and bandwidth. A board supports various redundancy modes,
including no redundancy, 1+1 backup, and load sharing. The weight of board
redundancy of an event that occurs in a board configured with no redundancy mode
is higher than the weight of an event that occurs in a board configured with the 1+1
backup or load sharing mode.
The system defines three severity levels in descending order: All, Part, and Light. For
example, the severity level (All) of an event reported by a processing board (higher weight
of board type) in no redundancy mode (higher weight of board redundancy) is higher than
the severity level (Light) of an event reported by an interface board (lower weight of board
type) in redundancy mode (lower weight of board redundancy).
The system can count the duration of stability events occurring in an NE during a period
by severity level and generate an NE stability report. The statistical result in the report
contains the following four parts:
l
l
l
l
Total duration of stability events at the severity level "All"

Total duration of stability events at the severity level "Part"
Total duration of stability events at the severity level "Light"
Total duration of stability events occurring during maintenance
Maintenance Plan
The stability of an NE may be influenced during routine NE maintenance. The stability
events occurring during maintenance should be neglected to ensure appropriate
evaluation of the NE stability. Users can specify a maintenance 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.
When generating an NE stability report, the system does not count the events occurring
during the maintenance.
2-9
SJ-20130524154927-012|2013-06-20 (R1.0)
2.3.1 Managing Stability Events

2.3.1.1 Querying Stability Events
This procedure describes how to query stability events received by the NetNumen U31
system during a specific period.
Steps
Application > NE Stability Management. The NE Stability Management dialog
box is displayed, see Figure 2-8.
Figure 2-8 NE Stability Management Dialog Box (Stability Event Tab)
2. From the Begin Time list, select a start date in the pop-up calendar, and then click
OK.
3. From the End Time list, select an end date in the pop-up calendar, and then click OK.
4. Select a time zone from the Time Zone list.
5. Click Search. The stability events during the specified period are displayed on the
Stability Event tab, see Figure 2-9.
2-10
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-9 Stability Event Query Result
The Event Class column shows the original classes of the alarms corresponding to
the events reported by the NEs. The classes will be updated in the report generated
after NE stability is analyzed.
End of Steps
2.3.1.2 Exporting Stability Events

This procedure describes how to export stability events to an XLS file.
Prerequisite
Users have successfully queried the stability events to be exported in the NE Stability
Management dialog box.
Steps
1. In the NE Stability Management dialog box, click Export Result on the Stability
Event tab. The Save dialog box is displayed.
2. Select a directory for saving the stability events, enter a file name, and then click Save.
A message confirming the successful export of the stability events is displayed.
3. Click OK. An XLS file containing the exported stability events is generated in the
selected directory.
End of Steps
2.3.1.3 Exporting an NE Stability Report

This procedure describes how to export the stability events during a specific period as an
NE stability report to an XLS file.
Prerequisite
Users have successfully queried the stability events during the period in the NE Stability
2-11
SJ-20130524154927-012|2013-06-20 (R1.0)
Steps
1. In the NE Stability Management dialog box, click Export Report on the Stability
Event tab. The Save dialog box is displayed.
2. Select a directory for saving the NE stability report, enter a file name, and then
click Save. A message confirming the successful export of the NE stability report is
displayed.
3. Click OK. An NE stability report in XLS format is generated in the selected directory.
4. To view the contents in the NE stability report, double-click the XLS file. The NE
stability report is displayed, see Table 2-2.
Table 2-2 NE Stability Report
NE Stability Report
NE ID
All-Break
Time(s)
Part-
Light-
Break
Break
Time(s)
Time(s)
Instability
Time(s)
Planned
Instability
Time
BSC1-1
0.00
0.00
0.00
0.00
0.00
BSC10-10
0.00
0.00
0.00
0.00
0.00
BSC1023-1023
7562.00
0.00
0.00
7562.00
0.00
BSC1024-1024
0.00
0.00
0.00
0.00
0.00
BSC11-11
80119.00
0.00
0.00
80119.00
0.00
BSC12-12
0.00
0.00
0.00
0.00
0.00
BSC123-123
12062.00
0.00
0.00
12062.00
0.00
BSC133-133
0.00
0.00
0.00
0.00
0.00
BSC135-135
0.00
0.00
0.00
0.00
0.00
BSC14-14
0.00
0.00
38731.78
0.00
BSC15-15
0.00
0.00
0.00
0.00
0.00
BSC151-151
0.00
0.00
0.00
0.00
0.00
154927
.12
Stability
Useless
Stability
Percent
Time
Percent
(Planned
in Year
Except)
(minute)
100.000
100.000
100.000
100.000
99.743%
99.743%
100.000
100.000
97.273%
97.273%
100.000
100.000
99.589%
99.589%
100.000
100.000
100.000
100.000
98.682%
98.682%
100.000
100.000
100.000
100.000
0.00
0.00
126.00
0.00
1335.31
0.00
201.03
0.00
0.00
0.00
0.00
0.00
2-12
SJ-20130524154927-012|2013-06-20 (R1.0)
Begin Date (Asia/Shanghai)
201204-25
End Date (Asia/Shanghai)
2012-04-25
End of Steps
2.3.1.4 Generating NE Stability Reports on Schedule

In the NetNumen U31 system, a Man Machine Language (MML) task can be created for
periodic generation of required NE stability reports.
This procedure describes how to schedule an MML task for generating NE stability reports
weekly.
Steps
1. In the client window, select Maintenance > Task Management from the menu bar.
The Task Management window is displayed.
2. In the left pane, click the MML Timing Task node in the Task Management tree, and
then click on the toolbar. The Create Task dialog box is displayed, see Figure 2-10.
Figure 2-10 Create Task Dialog BoxBasic Information Tab
3. On the Base Information tab, perform the following operations:

a. In Task Name, enter a task name.
b. From Task Status, select Active.
c. In Task Description, enter additional information for the new task as needed.
d. Click Edit Command.
e. Under MML, enter an appropriate MML command for generating an NE stability
report.
2-13
SJ-20130524154927-012|2013-06-20 (R1.0)
The following describes the MML command used for report generation.
MINOS CMD:TYPE="STABILITYREPORT"[,ATTRIB="period&path"]
The command is case-insensitive. For a description of two input parameters
(period and path) in the command, refer to Table 2-3.
Table 2-3 Command Parameter Descriptions
Parameter
Description
period
(Optional) Specifies the period during which the stability events are
required for report generation.
Unit: day
Default value: 1
Example: Set the parameter value to 7. Then the system queries the
stability events occurring in the previous seven days and generates an
NE stability report based on the query result.
path
(Optional) Specifies the path for saving the generated NE stability reports.
Note: If the value of this parameter is null, the system saves the NE
stability reports in \ums-server\rundata\ftp\stability\ne\
by default.
The parameter value format varies with different operating systems on
the NetNumen U31 server.
l
Windows: The double-backslash (\\) is used as the delimiting

character in the path, for example, D:\\EXPORT.
Linux or UNIX: The slash (/) is used as the delimiting character in

the path, for example, /export/home/omc/netnumen/ums-ser
ver/rundata/ftp/stability/ne.
4. Click the Policy tab. The schedule parameters are displayed, see Figure 2-11.
2-14
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-11 Create Task Dialog BoxPolicy Tab
5. On the Policy tab, perform the following operations:

a. Under Plan Type, select Weekly from the list, and then select Monday.
b. Under Execution Time, enter the time when the task shall be run on the specified
day, for example, 00:00:00.
c. Under Duration, set an effective period for the task or use the default start date
(current date).
6. Click OK. The MML task for generating stability reports is displayed in the Task
Management window. The system generates an NE stability report based on the
stability events occurring in the previous seven days every Monday and saves the
generated report in the required path.
End of Steps
2.3.2 Managing Maintenance Plans

2.3.2.1 Adding a Maintenance Plan
If an NE 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 so as to ensure the accuracy of corresponding NE stability report.
This procedure describes how to add a maintenance plan in the NetNumen U31 system.
Steps
Application > NE Stability Management from the menu bar. The NE Stability
Management dialog box is displayed.
2-15
SJ-20130524154927-012|2013-06-20 (R1.0)
2. Click the Maintain Plan tab. The Maintain Plan tab is displayed, see Figure 2-12.
Figure 2-12 NE Stability Management Dialog BoxMaintain Plan Tab
3. Click the Add Plan button, or right-click a row in the maintenance plan list and select
Add Plan from the shortcut menu. The Add Maintain Plan dialog box is displayed,
see Figure 2-13.
Figure 2-13 Add Maintain Plan Dialog Box
2-16
SJ-20130524154927-012|2013-06-20 (R1.0)
4. Set required parameters in accordance with the actual maintenance information.
Note:
The start date of a maintenance plan cannot be earlier than the current date. In
addition, a new maintenance plan cannot overlap with an existing plan.
For a description of the parameters in the Add Maintain Plan dialog box, refer to Table
2-4.
Table 2-4 Parameter Descriptions for the Add Maintain Plan Dialog Box
Parameter
Description
Begin Time
Start time of the maintenance plan
End Time
End time of the maintenance plan
Time Zone
Time zone for determining the start time and end time of the maintenance
plan
Operation Type
Select the operation type, meaning the type of the object on which
maintenance operations are to be performed.
The options are: NE and Board.
NE
Select the NE to be maintained.

The optional NEs are displayed in the format of "NE type-Subnetwork
ID-NE ID", for example, BSC1010.
Operation Object
Select the object on which maintenance operations are to be performed.

The object display format depends on the operation type.
l
If the operation type is NE, the optional objects are displayed in the
format of "Subnetwork ID-NE ID", for example, 280280.
If the operation type is Board, the optional objects are displayed in

the format of "Rack No.-Shelf No.-Slot No.", for example, 1211.
Operation Description
Maintenance plan description
Service Impacting
Whether the maintenance plan affects services

Default: Yes
Emergency
Whether the maintenance plan is urgent

Default: Yes
Roolback
Whether the system can be restored when the maintenance plan fails
Default: Yes
Closure State
Whether all maintenance operations in the plan are completed during

the specified period
Default: Yes
Comments
Additional information about the maintenance plan

2-17
SJ-20130524154927-012|2013-06-20 (R1.0)
5. Click OK. A confirmation box is displayed, prompting the successful creation of the
maintenance plan and asking users whether to add another maintenance plan.
6. Click No. The added maintenance plan is displayed on the Maintain Plan tab.
End of Steps
Related Task
Users can modify or delete the added maintenance plan as required.
2.3.2.2 Querying Maintenance Plans

This procedure describes how to query maintenance plans that have been added in the
NetNumen U31 system by operation type and start date.
Steps
2. Click the Maintain Plan tab.
3. From Operation Type, select an operation type: NE, Board, or All.
4. From Start Date, select a date and click OK.
5. From Time Zone, select a time zone as required.
6. Click Search. The maintenance plans meeting the query conditions are displayed on
the Maintain Plan tab.
End of Steps
2.3.2.3 Exporting Maintenance Plans

This procedure describes how to export maintenance plans to an XLS file.
Prerequisite
Users have successfully queried the maintenance plans to be exported in the NE Stability
Steps
1. In the NE Stability Management dialog box, click Export Result on the Maintain
Plan tab. The Save dialog box is displayed.
2. Select a directory for saving the maintenance plans, enter a file name, and then click
Save. An XLS file containing the exported maintenance plans is generated in the
selected directory.
End of Steps
2-18
SJ-20130524154927-012|2013-06-20 (R1.0)
2.3.2.4 Importing Maintenance Plans

This procedure describes how to add maintenance plans to the NetNumen U31 system by
importing a predefined XLS file.
Note:
An XLS file containing exported maintenance plans can be used as a template for editing
maintenance plans to be imported.
Prerequisite
The XLS file to be imported is available and has an appropriate content structure.
Steps
2. Click the Maintain Plan tab, and then click the Import button. The Open dialog box
is displayed.
3. Select the directory where the XLS file is saved, click the XLS file, and then click Open.
A message confirming the successful import of the maintenance plans is displayed.
End of Steps
2.4 Base Station Status Management

A base station works in one of the following four statuses:
l
Normal status
The base station operates properly.
Testing status
The base station is under test or maintenance. In this status, large amounts of alarms
are generated. All or some alarm and performance data generated during the test or
maintenance are not reported to the NetNumen U31 system.
The testing status does not influence the reporting of configuration data.
Fault Management (FM) testing status

The base station does not report all or some alarm data to the NetNumen U31 system.
Performance Management (PM) testing status

The base station does not report all or some performance data to the system.
Base station status management supports the following operations:

2-19
SJ-20130524154927-012|2013-06-20 (R1.0)
l
l
l
l
Querying base station statuses

Setting base station statuses
Exporting the query results of base station statuses
Importing base station statuses
2.4.1 Querying Base Station Statuses

This procedure describes how to query the statuses of specific base stations in a GSM
network.
Note:
For base stations (Node Bs) in a UMTS network, the statuses of the related RNCs are also
displayed in the query result.
Prerequisite
l
l
The base stations have been configured in the NetNumen U31 system.
The connections between the base stations and the corresponding BSCs (OMMs) are
normal.
Steps
Application > Maintain Status Query and Setting from the menu bar. The Maintain
Status Query and Setting dialog box is displayed, see Figure 2-14.
2-20
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-14 Maintain Status Query and Setting Dialog Box
In the topology tree, each Managed Element (ME) is identified by a string combining
ME name and ME ID. Users can query the statuses of specific base stations by ME
name and/or ID.
l
l
If = is selected, the system queries the status of each base station with an ME
name or ID that is the same as the entered keyword.
If like is selected, the system queries the status of each base station with an ME
name or ID containing the entered keyword.
Note:
If users set multiple query conditions related to ME name and ID, the system queries
the statuses of base stations whose ME name and ID meet all the query conditions.
If users do not set any query condition, the system queries the statuses of all base
stations belonging to the selected subnet.
2. In the EMS Server tree, click a subnet or an NE.

3. Click the status to be queried: All, Normal, Testing, FM Testing, or PM Testing.
4. Select = or like from the ME ID list, enter a keyword (for example, 1) in the text box,
and then click Add. The query conditions are displayed in the lower area, see Figure
2-15.
2-21
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-15 Query Conditions
5. Select = or like from the ME Name list, enter a keyword in the text box, and then click
Add. The query conditions are displayed in the lower area.
6. Click OK. The base station statuses meeting the query conditions are displayed in the
Maintain Status Query and Setting dialog box.
l If an NE is selected in the EMS Server tree, see Figure 2-16 for the displayed
dialog box.
l If a subnet is selected in the EMS Server tree, see Figure 2-17 for the displayed
dialog box.
Figure 2-16 Query Results of Base Station Statuses (with NodeB Office Information)
2-22
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-17 Query Results of Base Station Statuses (without NodeB Office
Information)
For a description of the buttons in the dialog box, refer to Table 2-5.
Table 2-5 Buttons in the Maintain Status Query and Setting Dialog Box
Button
Description
Execute
Sets the status of a base station.
Export
Exports the query results to an XLS file.
Import
Sets the statuses of base stations by importing an XLS file.
Refresh
Refreshes the base station statuses in the query result.
Option
Resets query conditions to initiate another query.
Close
Closes the dialog box.
End of Steps
2.4.2 Setting the Status of a Base Station

Context
Users can set the status of one or multiple base stations as required.
The following procedure describes how to set the status of a base station from "Normal"
to "Testing".
Prerequisite
l
l
Users have successfully queried the status of the base station, and the query result
is displayed in the Maintain Status Query and Setting dialog box.
The connection between the base station and the NetNumen U31 server is normal.
2-23
SJ-20130524154927-012|2013-06-20 (R1.0)
Steps
1. In the Maintain Status Query and Setting dialog box, click a row and right-click on
the selected row. A shortcut menu is displayed, see Figure 2-18.
Figure 2-18 Shortcut Menu for Setting Base Station Status
Note:
To set the statuses of multiple base stations to the same status at a time, users can
press and hold the Ctrl or Shift key while selecting each base station to be set.
2. Select Testing from the shortcut menu.

3. Click Execute. The Setting Reason dialog box is displayed, see Figure 2-19.
Figure 2-19 Setting Reason Dialog Box
4. Enter the reason for setting the base station status, and then click OK. A message
confirming the successful execution of the status setting command is displayed.
5. Click OK. "Success" is displayed in the corresponding cell in the Result column.
2-24
SJ-20130524154927-012|2013-06-20 (R1.0)
Note:
If "Exception" is displayed in the cell, users can check the related logs to locate the
failure cause.
6. Click Refresh. The status of the base station in the Status Before column changes
to "Testing".
End of Steps
Related Task
After the testing process is completed, users must set the status of the base station to
Normal, so that the alarm and performance information can be reported to the NetNumen
U31 system.
2.4.3 Exporting Base Station Statuses

Context
This procedure describes how to export base station statuses to a file.
Prerequisite
l
l
normal.
Steps
1. Perform either of the following operations as required.
To...
Do...
Save all base station status data in the Maintain
i.
Status Query and Setting dialog box to a file
In the Maintain Status Query and Setting

dialog box, click Export. The Save dialog box
is displayed.
ii.
Select a directory for saving the exported

base station statuses, enter a file name, and
then click Save. A message confirming the
successful export of the base station statuses
is displayed.
2-25
SJ-20130524154927-012|2013-06-20 (R1.0)
To...
Do...
iii. Click OK. An XLS file containing the exported
base station statuses is generated in the
selected directory.
Save all base station status data in the system
i.
to a file
In the Maintain Status Query and Setting

dialog box, click Export All Data. The Save
ii.
Select a directory, enter a file name, and

then click Save. A message confirming the
successful export of the base station statuses
is displayed.
iii. Click OK. A ZIP file containing all the base

station statuses in the system is generated in
the selected directory.
End of Steps
2.4.4 Importing Base Station Statuses

This procedure describes how to import base station statuses from a predefined XLS file.
Context
The base station status import function can be used to modify the statuses of multiple base
stations at a time. Users can export the original base station statuses to an XLS file, enter
new statuses for multiple base stations in the Status After column in the XLS file (see
Figure 2-20), and then import the modified XLS file to the NetNumen U31 system. The
new statuses are displayed in the Maintain Status Query and Setting dialog box.
Figure 2-20 Base Station Statuses in an XLS File
2-26
SJ-20130524154927-012|2013-06-20 (R1.0)
Prerequisite
l
l
l
l
normal.
The XLS file does not contain base stations that are not configured in the NetNumen
U31 system.
Steps
Application > Maintain Status Query and Setting from the menu bar. The Maintain
Status Query and Setting dialog box is displayed.
2. Click Import. The Open dialog box is displayed.
The imported base station statuses are displayed in the Maintain Status Query and
Setting dialog box, see Figure 2-21.
Figure 2-21 Example of Imported Base Station Statuses
End of Steps
2.5 Base Station Priority Management

In the NetNumen U31 system, the managed base stations can be divided into VIP, Class-B,
Class-C, and Normal base stations in descending order of priority. 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 obtain the alarm statistics of VIP
base stations, Class-B base stations, and Class-C base stations separately.
Base station priority management supports the following operations:
l
l
Querying base station priorities

Setting base station priorities
2-27
SJ-20130524154927-012|2013-06-20 (R1.0)
l
l
Exporting base station priorities

Importing base station priorities
2.5.1 Querying Base Station Priorities

This procedure describes how to query the priorities of specific base stations.
Prerequisite
The connections between the base stations and the NetNumen U31 server are normal.
Steps
Application > VIP NodeB Priority Query and Setting from the menu bar. The VIP
NodeB Priority Query and Setting dialog box is displayed, see Figure 2-22.
Figure 2-22 VIP NodeB Priority Query and Setting Dialog Box
In the topology tree, each Managed Element (ME) is identified by a string combining
ME name and ME ID. Users can query the priorities of specific base stations by ME
name and/or ID.
l
l
If = is selected, the system queries the priority of each base station with an ME
name or ID that is the same as the entered keyword.
If like is selected, the system queries the priority of each base station with an ME
name or ID containing the entered keyword.
2-28
SJ-20130524154927-012|2013-06-20 (R1.0)
Note:
If users set multiple query conditions related to ME name and ID, the system queries
the priorities of base stations whose ME name and ID meet all the query conditions.
If users do not set any query condition, the system queries the priorities of all base
stations belonging to the selected subnet.
2. In the EMS Server tree, select one or multiple subnets.

3. Select the priority to be queried: All, VIP, B Class, C Class, or Normal.
4. Select = or like from the ME ID list, enter a keyword in the text box, and then click
Add. The query conditions are displayed in the lower area.
5. Select = or like from the ME Name list, enter a keyword (for example, 12) in the text
box, and then click Add. The query conditions are displayed in the lower area, see
Figure 2-23.
Figure 2-23 Priority Query Condition Setting
6. Click OK. The base station priorities meeting the query conditions are displayed in the
VIP NodeB Priority Query and Setting dialog box, see Figure 2-24.
2-29
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-24 Query Results of Base Station Priorities
For a description of the buttons in the dialog box, refer to Table 2-6.
Table 2-6 Buttons in the VIP NodeB Priority Query and Setting Dialog Box
Button
Description
Execute
Sets the priority of a base station.
Export
Exports the query results to an XLS file.
Import
Sets the priorities of base stations by importing an XLS file.
Refresh
Refreshes the base station priorities in the query result.
Option
Displays VIP NodeB Priority Query and Setting dialog box, where
the query conditions can be reset to initiate another query.
Close
Closes the dialog box.
End of Steps
2.5.2 Setting the Priority of a Base Station

Context
Users can set the priority of one or multiple base stations as required.
This procedure describes how to set the priority of a base station from "Normal" to
"Class-B".
Prerequisite
l
l
Users have successfully queried the priority of the base station, and the query result
is displayed in the VIP NodeB Priority Query and Setting dialog box.
The connection between the base station and the NetNumen U31 server is normal.
2-30
SJ-20130524154927-012|2013-06-20 (R1.0)
Steps
1. In the VIP NodeB Priority Query and Setting dialog box, click a row and right-click
on the selected row. A shortcut menu is displayed, see Figure 2-25.
Figure 2-25 Shortcut Menu for Setting Base Station Priority
Note:
To set the priorities of multiple base stations to the same priority at a time, users can
press and hold the Ctrl or Shift key while selecting each base station to be set.
2. Select B Class from the shortcut menu.

3. Click Execute. A message confirming the successful execution of the priority setting
command is displayed.
5. Click Refresh. The priority of the base station in the Priority Before column changes
to "B Class".
End of Steps
2.5.3 Exporting Base Station Priorities

Context
After querying required base station priorities, users can export the query results to an
XLS file.
The following procedure describes how to export base station priorities to an XLS file.
2-31
SJ-20130524154927-012|2013-06-20 (R1.0)
Prerequisite
Users have successfully queried the base station priorities to be exported in the VIP NodeB
Priority Query and Setting dialog box.
Steps
1. In the VIP NodeB Priority Query and Setting dialog box, click Export. The Save
2. Select a directory for saving the exported base station priorities, enter a file name,
and then click Save. A message confirming the successful export of the base station
priorities is displayed.
3. Click OK. An XLS file containing the exported base station priorities is generated in
the selected directory.
End of Steps
2.5.4 Importing Base Station Priorities

This procedure describes how to import base station priorities from a predefined XLS file.
Context
The base station priority import function can be used to modify the priorities of multiple
base stations at a time. Users can export the original base station priorities to an XLS file,
enter new priorities for multiple base stations in the Priority After column in the XLS file
(see Figure 2-26), and then import the modified XLS file to the NetNumen U31 system.
The new priorities will be displayed in the VIP NodeB Priority Query and Setting dialog
box.
Figure 2-26 Base Station Priorities in an XLS File
Prerequisite
l
l
The connections between the base stations and the NetNumen U31 server are normal.
2-32
SJ-20130524154927-012|2013-06-20 (R1.0)
The XLS file does not contain base stations that are not configured in the NetNumen
U31 system.
Steps
Application > VIP NodeB Priority Query and Setting from the menu bar. The VIP
NodeB Priority Query and Setting dialog box is displayed.
2. In the VIP NodeB Priority Query and Setting dialog box, click Import. The Open
The imported base station priorities are displayed in the VIP NodeB Priority Query
and Setting dialog box, see Figure 2-27.
Figure 2-27 Imported Base Station Priorities
4. Click Execute. A message confirming the successful execution of the priority setting
command is displayed.
5. Click OK. "Success" is displayed in each related cell in the Result column.
6. Click Refresh. The priorities of the base stations in the Priority Before column change
in accordance with the settings in the imported XLS file.
End of Steps
2.6 Site Transfer

The NetNumen U31 system supports the transfer and swap of equipment in the same
network or between two networks of the same system (GSM, UMTS, 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. The transfer
plan file contains the information of source nodes and destination nodes, and necessary
modification of the configuration information.
2-33
SJ-20130524154927-012|2013-06-20 (R1.0)
Users can obtain transfer plan templates for different products in a specific path in the
installation directory of the client. The paths of these transfer plan templates follow the
same rule:
\EMS\ERT\folder obtained from remote OMM (name format:
product and version\the path of templates on the OMM. For example, the
transfer plan templates for non-MO GSM products are located in the \EMS\ERT\ISMG
-R6.20.713b-B4.00.200m-\ums-clnt\deploy\template\rnc\template_EN
folder in the installation directory of the client.
The NetNumen U31 system provides the following functions to support site transfer:
l
Exporting configuration data

Users can export the configuration information of the source nodes specified in the
transfer plan file from the system to a ZIP file. This ZIP file can be used for site transfer
later.
Transferring the configuration data for online source nodes

Users can transfer the configuration data of the source nodes specified in the transfer
plan file to the destination nodes, and then remove the source nodes from the system.
Transferring the configuration data for offline source nodes

Users can transfer the configuration data of the source nodes from a predefined
ZIP file to the destination nodes. If the source nodes are managed by the same
NetNumen U31 system, users can remove the source nodes from the system after
the site transfer.
The offline site transfer function can be used for transferring equipment managed by
a NetNumen U31 system to another NetNumen U31 system.
Note:
For a GSM or UMTS site, only the configuration data of base station controllers (BSC
or RNC) can be exported and transferred in the NetNumen U31 system. Users can
only export and transfer the configuration data of a base station (BTS or Node B) by
using a tool provided by the corresponding Operation & Maintenance Module (OMM).
For a TD-SCDMA site, the configuration data of both RNC and Node B can be
exported and transferred in the NetNumen U31 system.
If the process of data export, online transfer, or offline transfer is not completed within
15 minutes, the system will forcibly end the process. The time limit is determined by
the following 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:
l
l
l
getsite waitting="15"
transfersite waitting="15"
deletesite waitting="15"
2-34
SJ-20130524154927-012|2013-06-20 (R1.0)
Users can change the parameter values to modify the time limit.
2.6.1 Exporting Configuration Data of a Source Site

This procedure describes how to export the configuration data of the source site from the
system to a ZIP file.
Prerequisite
The transfer plan file to be used is available, which contains the information of the source
site to be transferred.
Steps
Application > Transfer Site from the menu bar. The Transfer Site dialog box is
displayed, see Figure 2-28.
Figure 2-28 Transfer Site Dialog Box
2. Click Select. The Open dialog box is displayed.

3. Select the directory where the transfer plan file is saved, click the file, and then click
Open. The file name is displayed in File Path.
4. Select the type(s) of configuration data to be exported in accordance with the
equipment type: Bind OMMR and/or Bind OMMB.
5. Click Execute. The export progress is displayed under Output Info. After the
configuration data export is completed, the path and name of the generated ZIP file
are displayed too. The ZIP file is generated in the ums-client/works/full/tmp
/ftp/movesite/data/ directory.
End of Steps
2-35
SJ-20130524154927-012|2013-06-20 (R1.0)
2.6.2 Transferring an Online Site

This procedure describes how to transfer the configuration data from a source site to a
destination site when the source site is online in the NetNumen U31 system.
Prerequisite
The transfer plan file to be used is available, which contains the information of the source
site and destination site for the site transfer.
Steps
displayed.
4. Select Online Transfer from the Operation list.
5. Select the type(s) of configuration data to be transferred in accordance with the
6. To delete the source site when the transfer is completed, select Delete Site.
7. Click Execute. The transfer progress is displayed under Output Info. If Delete Site
is selected, the source site will be deleted from the NetNumen U31 system after the
site transfer is completed.
End of Steps
2.6.3 Transferring an Offline Site

This procedure describes how to transfer the configuration data from a source site to a
destination site when the source site is offline in the NetNumen U31 system.
Prerequisite
l
l
The transfer plan file to be used is available, which contains the information of the
source site and destination site for the site transfer.
The ZIP file containing the configuration data of the offline source site is available.
Steps
displayed.
2-36
SJ-20130524154927-012|2013-06-20 (R1.0)
4. Select Offline Transfer from the Operation list.
5. Select the type(s) of configuration data to be transferred in accordance with the
6. To delete the source site when the transfer is completed, select Delete Site.
7. Click Execute. The Offline Data dialog box is displayed, see Figure 2-29.
Figure 2-29 Offline Data Dialog Box

9. Select the ZIP file that contains the configuration data of the source site, and then click
Open. The file path is displayed in File Path.
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. Users can view the attributes of a specific source site by selecting the site from
the Site Info list and then clicking View in the Offline Data dialog box.
10. Click Ok. The transfer progress is displayed under Output Info in the Transfer Site
dialog box. If Delete Site is selected and the source site is managed by this NetNumen
U31 system, the source site will be deleted from the system after successful site
transfer.
End of Steps
2-37
SJ-20130524154927-012|2013-06-20 (R1.0)
2.6.4 Viewing Operation Results Related to Site Transfer

This procedure describes how to view the results of site transfer operations on the client
GUI.
Context
After a configuration data export, online site transfer, or offline site transfer operation is
performed, the system generates one to three CSV files containing the results of different
operations. The recorded result in these files will be overwritten after another operation is
performed. For a description of the result files and the default file paths, refer to Table 2-7.
Table 2-7 Result File Descriptions
Result File
Possible Operation
Default File Path
CSV file containing
Configuration data export
ums-client/works/full/tmp/ft
the result of obtaining
Online site transfer
p/movesite/result/collect/
CSV file containing the
result of transferring
Offline site transfer
p/movesite/result/transfer/
CSV file containing the
result of deleting a source
Offline site transfer
p/movesite/result/delete/
configuration data from a

source site
configuration data from a

source site to a destination
site
site
Users can open a result file to view the result details or view the previous operation result
on the client GUI.
Prerequisite
A configuration data export, online site transfer, or offline site transfer operation has been
performed in the NetNumen U31 system.
Steps
displayed.
2. Click View Result. The Result Data dialog box is displayed, see Figure 2-30.
2-38
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-30 Result Data Dialog Box
3. Select a result type from the Result Type list. The operation result saved in the
corresponding CSV file is displayed, see Figure 2-31.
Figure 2-31 Result Data Dialog Box
End of Steps
2.6.5 Halting a Site Transfer Process

This procedure describes how to halt a site transfer process.
Context
If the NetNumen U31 system does not complete the export or transfer of configuration data
after a long time, the process can be halted as required. After the process is halted, the
system will not execute the commands that have not been sent to the corresponding site.
2-39
SJ-20130524154927-012|2013-06-20 (R1.0)
Caution!
Do not halt an export or transfer process unless absolutely necessary. Improper halting
of a process may result in inconsistent 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).
Prerequisite
l
l
The Transfer Site dialog box is open.

The system is exporting or transferring configuration data of a source site.
Steps
l
In the Transfer Site dialog box, click Halt Operation. The halting result is displayed
under Output Info.
End of Steps
2.7 Inter-Element Configuration Data Import and Export

The NetNumen U31 system supports the export and import of configuration data in GSM,
UMTS, and LTE networks. The following export and import operations are supported:
l
l
Exporting configuration data from multiple NEs to XLS or XML files.

Importing configuration data to multiple NEs from XLS or XML files for quick
configuration.
For NEs in different radio access networks, the system provides several configuration data
templates by data type, such as radio data batch import and export template, and RNC
equipment and transmission parameter import and export template. Users can obtain a
configuration data template for a specific NE type and version by exporting configuration
data from an NE of this type. This template can be used for editing a file containing required
configuration data for another NE of the same type and version.
2.7.1 Exporting Configuration Data

This procedure describes how to export configuration data from multiple NEs to individual
XLS files.
Steps
Application > Inter ME Import and Export from the menu bar. The Inter ME
Configuration Import and Export dialog box is displayed, see Figure 2-32.
2-40
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-32 Inter ME Configuration Import and Export Dialog Box
2. (Optional) To modify the path where the configuration data is to be saved, select
System > Config Export Result File Path on the main menu. The Config Export
Result File Path dialog box is displayed.
a. Click Config. The Open dialog box is displayed.
b. Select a path and then click Open.
c. In the Config Export Result File Path dialog box, click OK.
3. Click Config Data Export under Operation Type Selection, and click a template
under Operation Template Selection. The Add Operate Object and Remove
Operate Object buttons are activated on the lower part of the right pane, see Figure
2-33.
Figure 2-33 Operation Type Config Data Export
2-41
SJ-20130524154927-012|2013-06-20 (R1.0)
4. Click Add Operate Object. The Add Object dialog box is displayed, see Figure 2-34.
Figure 2-34 Add Object Dialog Box
5. Select one or multiple objects in the NE tree, and then click OK. The selected objects
and corresponding files are displayed in the Inter ME Configuration Import and
Export dialog box, see Figure 2-35.
Figure 2-35 Inter ME Configuration Import and Export Dialog Box Objects Selected
6. (Optional) To change the format of configuration data file to be saved, click the
corresponding cell in the Export Format column, and then select xls or xml from the
list.
2-42
SJ-20130524154927-012|2013-06-20 (R1.0)
7. Click OK. After the system successfully exports the required configuration data for an
object, "Success" is displayed in the corresponding cell in the Result column and an
XLS or XML file is generated in the selected path.
End of Steps
2.7.2 Importing Configuration Data

This procedure describes how to import configuration data from predefined XLS or XML
files to multiple NEs.
Note:
To prepare a configuration data file in XLS format for an NE to be configured, users are
recommended to edit the configuration data based on an appropriate template. Users can
export configuration data from an existing NE of the same type and version to obtain the
template.
Prerequisite
l
l
l
The NEs to be configured support the configuration data import function.

The XLS or XML files to be imported are available and comply with the corresponding
configuration data templates.
The configuration data to be imported is correct and applicable to the type and version
of the NEs.
Steps
Application > Inter ME Import and Export from the menu bar. The Inter ME
Configuration Import and Export dialog box is displayed.
2. (Optional) To modify the path where the configuration data is to be saved, select
System > Config Export Result File Path on the main menu. The Config Export
Result File Path dialog box is displayed.
a. Click Config. The Open dialog box is displayed.
b. Select a path and then click Open.
c. In the Config Export Result File Path dialog box, click OK.
3. Click an appropriate template under Operation Template Selection.
4. Click Add Data File. The Open dialog box is displayed.
5. Select the directory where the configuration data files are saved from the Look in list.
6. Select .xml file or .xls file from the Files of Type list.
2-43
SJ-20130524154927-012|2013-06-20 (R1.0)
7. Select a configuration data file to be imported, and then click Open. The file name is
displayed in the Selected Data File List, see Figure 2-36.
Figure 2-36 Record in the Selected Data File List
8. Click the corresponding cell in the Operate Object No. column, and then select the
NE to which the configuration data will be imported from the list.
9. Repeat Step 3 to Step 7 to add the other configuration data files and select
corresponding NEs as required.
10. Click OK. The Please input verification code dialog box is displayed, see Figure
2-37.
Figure 2-37 Please Input Verification Code Dialog Box
11. Enter the verification code as required, and click OK. After the system successfully
imports configuration data from a selected file to the required NE, "Success" is
displayed in the corresponding cell in the Result column.
End of Steps
2.8 Neighbor Cell Tool

The NetNumen U31 system provides a neighbor cell tool for checking neighbor relations,
including:
2-44
SJ-20130524154927-012|2013-06-20 (R1.0)
l
l
Verifying that the external cell attributes on an OMM are consistent with those of the
actual external cells
Verifying the integrity of neighbor relations for a cell
In addition, the neighbor cell tool supports automatic and manual modification of
inconsistent attributes.
The procedure for verifying neighbor relation integrity is similar to that for verifying attribute
consistency. The subsequent section only describes how to verify the attribute consistency.
2.8.1 Verifying Attributes Consistency

Context
In the NetNumen U31 system, the attributes of some external cells may be specified for a
subnet (OMM). The external cells can be configured as neighbor cells of a local cell. Users
can verify that appropriate attributes are specified on the OMM to ensure correct neighbor
relations.
Note:
If an external cell is managed by another NetNumen U31 system, a ZIP file containing the
attributes of this external cell is required for consistency verification. Users can contact
ZTE's maintenance engineers for how to obtain the ZIP file.
The following procedure describes how to verify the consistency between the external cell
attributes specified on a UMTS OMM and those of the actual external cells.
Steps
Application > Neighbour Cell Tool from the menu bar. The Neighbour Cell Tool
2-45
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-38 Neighbour Cell Tool Dialog Box
2. Under Operate Functions List, click check accord.

3. Under Product Type, click UMTS. All available subnets are displayed under Operate
Object Area, see Figure 2-39.
Figure 2-39 Operate Object Area
4. Select the check box corresponding to the subnet to be checked.

5. (Optional) If related external cells are managed by another NetNumen U31 system,
perform the following operations:
a. Select Upload extern files. Additional buttons are activated in the Operate
Object Area, see Figure 2-40.
2-46
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-40 Operate Object Area (External Files)
b. Click Browse. The Open dialog box is displayed.

c. Select the directory where the ZIP file containing the external cell attributes is
located, and then click Open. The file path is displayed in External Files.
d. Click Upload. A progress shows the uploading progress and is closed after the
attributes uploading is completed.
6. Click Execute. A record containing the verification result is displayed under Operate
History Area, see Figure 2-41.
Figure 2-41 Operate History Area
7. To view the verification result, right-click the record and then click Show Action Result.
The consistency verification result is displayed under Detail Information Area, see
Figure 2-42.
Figure 2-42 Consistency Verification Result in the Detail Information Area (Show
Action Result)
8. To view inconsistent attributes, right-click the record and then click Show Result. The
detected inconsistent attributes are displayed under Detail Information Area, see
Figure 2-43.
2-47
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-43 Detected Inconsistent Attributes in the Detail Information Area (Show
Result)
Note:
The system supports automatic and manual modification of inconsistent attributes.
9. To automatically modify inconsistent attributes, click Modify start. A progress is

displayed, showing the modification progress. After the modification is completed, a
message box is displayed, showing the operation result ID.
10. Click OK.
11. Under Operate History Area, rightclick the record of the modification operation and
then click Show Action Result. The modification result is displayed under Detail
Information Area.
End of Steps
2.8.2 Importing Modified Attributes

When the automatic modification of inconsistent attributes fails, users can export the
inconsistent attributes to a CSV file, check and modify the inconsistent attributes manually
as required. The modified CSV file can be imported to the NetNumen U31 system to
complete the attribute modification.
The following procedure describes how to modify inconsistent attributes manually.
Prerequisite
l
l
The Neighbour Cell Tool dialog box is open.

An attribute verification operation has been performed and inconsistent attributes are
detected.
2-48
SJ-20130524154927-012|2013-06-20 (R1.0)
Steps
1. In the Neighbour Cell Tool dialog box, locate the operation result record under
Operate History Area.
2. Right-click the record and then click Show Result. The inconsistent attributes are
displayed under Detail Information Area.
3. Click export. The Save dialog box is displayed.
4. Select a directory for saving the exported attributes, use the default file name or enter
a new file name, and then click Save. A message confirming the successful export of
the attributes is displayed.
5. Locate the generated CSV file containing the exported attributes in the selected
directory on the client.
6. Open the CSV file and modify the inconsistent attributes as required, and then save
the file.
7. Under Operate History Area, right-click the operation result record, and then click
Import Data. The Open dialog box is displayed.
8. Select the directory where the modified CSV file is saved, click the file, and then click
Open. A progress scroll bar is displayed, indicating the modification progress. After
the modification is completed, a message showing the operation result ID is displayed.
9. Click OK.
10. Under Operate History Area, rightclick the record of the modification operation
and click Show Action Result. The modification result is displayed under Detail
Information Area.
End of Steps
2.9 User Label Relation Management

The user label of a local cell should be specified in a neighbor relation between the local
cell and an adjacent cell. If a user modifies the local cell's user label or the user label in the
neighbor relation, an inconsistency occurs. The function of managing user label relations
can be used to overwrite the user label in the neighbor relation with the local cell's user
label when the user label consistency is required.
The NetNumen U31 system can show the user labels of the local cells and those in
corresponding neighbor relations for a managed element and highlight the local cells with
inconsistent user labels.
2.9.1 Verifying User Label Consistency

This procedure describes how to verify the consistency between the user labels of local
cells and those specified in neighbor relations and how to modify inconsistent user labels
as required.
2-49
SJ-20130524154927-012|2013-06-20 (R1.0)
Steps
Application > Relation User Label Management. The Relation User Label
Management dialog box is displayed, see Figure 2-44.
Figure 2-44 Relation User Label Management Dialog Box
2. Expand the NE tree in the left pane, and click the managed element to be checked.
Note:
In general, the system checks the user label consistency for local cells with Cell IDs
(CIDs) ranging from 0 to 200. Only the check results of a maximum of 20 local cells
can be displayed in the Relation User Label Management dialog box.
3. (Optional) Enter a start CID in From and an end CID in To for checking local cells with
CIDs in a specific range.
4. Click View. The corresponding CIDs and user labels are displayed in the right pane
after the system completes the consistency check for the required local cells, see
Figure 2-45.
2-50
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-45 Local Cells and User Labels
l
l
A local cell in blue font indicates that the same user label is specified in each
neighbor relation of the local cell.
A local cell in red font indicates that a different user label is specified in a neighbor
relation of the local cell.
5. Expand each local cell in the right pane. The information of corresponding neighbor
relation(s) is displayed, see Figure 2-46.
Figure 2-46 Local Cells and Neighbor Relations
1. Local cell
l
l
2. Neighbor relation
The information format of a local cell is: Local cell CID:User label.
The information format of a neighbor relation is: Adjacent cell's RNC ID:Adjacent
cell's CID:user label:<details of the adjacent cell>.
2-51
SJ-20130524154927-012|2013-06-20 (R1.0)
6. To overwrite all inconsistent user labels in neighbor relations with the user labels of
corresponding local cells, click Modify. A message confirming the modification of the
user labels is displayed.
7. Click OK. A confirmation box is displayed, prompting users to update user label
information in neighbor relations.
8. Click Yes. After the information update is completed, the Relation User Label
Management dialog box shows the latest user label information.
End of Steps
2.10 Cell Maintenance Status Management

A cell works in one of the following four maintenance statuses:
l
Normal
The cell is operating normally. The EMS can receive all data reported by the cell.
Testing
The cell is under test or maintenance. In this status, large amounts of alarms are
generated. All or some alarm and performance data generated during the test or
maintenances are not reported to the NetNumen U31 system.
Fault Management (FM) testing status

The cell base station does not report all or some alarm data to the NetNumen U31
system.
Performance Management (PM) testing status

The cell does not report all or some performance data to the NetNumen U31 system.
The maintenance status of a cell has a lower priority than that of the associated base
station. For example, if the base station is operating in testing status, and one of the cells
belonging to the base station is operating in normal status, part of performance and alarm
data related to this cell is not reported to the NetNumen U31 system.
Cell maintenance status management supports the following operations:
l
l
Querying cell maintenance statuses

Setting cell maintenance statuses
2.10.1 Querying Cell Statuses

This procedure describes how to query the statuses of one or more cells.
Prerequisite
The connections between the NetNumen U31 and the corresponding BSCs (OMMs) are
normal.
2-52
SJ-20130524154927-012|2013-06-20 (R1.0)
Steps
Application > Cell Maintain Status Management. The Cell Maintain Status
Management dialog box is displayed, see Figure 2-47.
Figure 2-47 Cell Maintain Status Management Dialog Box
2. In the EMS tree, click an ME.

3. (Optional) Enter the range of cell IDs to be queried.
If no range is specified, all cells managed by the selected ME are queried.
4. Click Search. The statuses of the required cells are displayed, see Figure 2-48.
Figure 2-48 Query Results of Cell Statuses
End of Steps
2.10.2 Setting Cell Statuses

Context
Users can set the status of one or multiple cells as required.
2-53
SJ-20130524154927-012|2013-06-20 (R1.0)
Note:
If the status of a cell is set from "Normal" to "Testing", users must set the status to "Normal"
after completing testing or maintenance operations on the cell to ensure that the required
alarm and performance data can be reported to the NetNumen U31 system.
The following procedure describes how to set the status of a cell from "Normal" to "Testing".
Prerequisite
l
l
The connections between the NetNumen U31 and the corresponding BSCs (OMMs)
are normal.
Users have successfully queried the cell status, and the query result is displayed in
the Cell Maintain Status Management dialog box.
Steps
1. In the Cell Maintain Status Management dialog box, click a row and right-click on
the selected row. A shortcut menu is displayed, see Figure 2-49.
Figure 2-49 Shortcut Menu for Setting Cell Status
Note:
To set the statuses of multiple cells to the same status at a time, users can press and
hold the Ctrl or Shift key while selecting each cell to be set.
2. Select Testing from the shortcut menu.

3. Click Execute. A message box is displayed, indicating that the command has been
issued to the NE(s).
2-54
SJ-20130524154927-012|2013-06-20 (R1.0)
Note:
If exceptions occur, the failure cause is displayed.
5. Click Refresh. The cell status in the Status Before column changes to "Testing".
End of Steps
2.11 Cell Broadcast Management

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. The cell broadcast service is different from the point-to-point short
message 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 provides the following cell broadcast management functions:
l
l
l
l
Channel management
Cell management
Area management
Short message management
2.11.1 Short Message Status

The status of a short message created in the NetNumen U31 system may be Unsent,
Sending, or Finished. Figure 2-50 illustrates how the status a short message changes
with different operations performed in the system.
2-55
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-50 Status Change of a Short Message
The following explains three short message statuses:

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 required time is reached and the status
of the short message is "Unsent".
Sending
If a short message is required to be sent immediately, the NetNumen U31 system

sends the short message to 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 the short message to the specified NEs on
schedule.
Finished
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 any 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 in
accordance with the modification.
2-56
SJ-20130524154927-012|2013-06-20 (R1.0)
2.11.2 Opening the CBC Management Window

This procedure describes how to open the Cell Broadcast Center (CBC) window before
managing channels, cells, areas, and short messages.
Steps
1. In the client window, perform either of the following operations:
l Select Configuration > Common Wireless Configuration Application > CBC
Management from the menu bar.
on the toolbar.
l Click
The CBC Management window is displayed, see Figure 2-51.
Figure 2-51 CBC Management Window
1. Navigation tree
2. Query bar
3. Information pane
Users can click a node in the navigation tree to show the corresponding information in
the information pane, such as all created messages, channels, cells, or areas.
End of Steps
2.11.3 Channel Management

Channels are used by mobile telecommunications operators to categorize short
messages, for example, create a channel for short messages containing 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
l
l
Creating a channel
Modifying a channel
Deleting a channel
2-57
SJ-20130524154927-012|2013-06-20 (R1.0)
Refreshing channels
2.11.3.1 Creating a Channel

This procedure describes how to create a channel.
Steps
1. In the CBC Management window, perform either of the following operations:
l Right-click the Channel node in the navigation tree, and then click Create.
l Click the Channel node in the navigation tree, right-click an existing channel (if
there is one) in the right pane, and then click Create.
The Create channel dialog box is displayed, see Figure 2-52.
Figure 2-52 Create Channel Dialog Box
For a description of the channel parameters, refer to Table 2-8.

Table 2-8 Channel Parameter Descriptions
Parameter
Description
Channel ID
Channel number
Value range: 1 to 65535
User label
Channel alias
Value range: 1 to 20 characters
Description
Channel description
2. Set necessary parameters.

2-58
SJ-20130524154927-012|2013-06-20 (R1.0)
3. Click Add. The created channel is displayed in the channel list on the upper part of
the Create channel dialog box.
4. Click Close. The Create channel dialog box is closed, and the created channel is
displayed in the CBC Management window.
End of Steps
2.11.4 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
l
l
l
l
Refreshing cell information

Resetting a cell
Querying the CBCH load
Setting the DRX mode
Viewing the cell restart history
2.11.4.1 Refreshing Cell Information

This procedure describes how to refresh the cell information displayed on the local client.
Context
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 is broken, the cell information
cannot be updated in time for the client. Users can perform the refreshing operation to get
the latest cell information from the NetNumen U31 server after the connection between
the client and the server recovers.
Steps
l Right-click the Cell node in the navigation tree, and then click Refresh.
l Click the Cell node in the navigation tree, right-click a cell displayed in the right
pane (if there is one), and then click Refresh.
The cell information in the right pane of the CBC Management window is refreshed.
End of Steps
2.11.4.2 Resetting a Cell

Users can reset a cell to remove all short messages to be broadcast from related NEs.
The following procedure describes how to reset a cell.
2-59
SJ-20130524154927-012|2013-06-20 (R1.0)
Steps
l Right-click the Cell node in the navigation tree, and then click Reset.
l Click the Cell node in the navigation tree, right-click a cell displayed in the right
pane (if any), and then click Reset.
The Reset cell dialog box is displayed, see Figure 2-53.
Figure 2-53 Reset Cell Dialog Box
2. Select the cell to be reset, and then click Ok. A message confirming the successful
reset of the selected cell is displayed.
End of Steps
2.11.4.3 Querying the CBCH Load

This procedure describes how to query the CBCH load of a cell. If the CBCH load is too
high, for example, reaches 100%, it is recommended to reduce the number of broadcast
short messages.
Context
Only GSM cells support CBCH load query.
Steps
1. In the CBC Management window, right-click the Cell node in the navigation tree, and
then click Query CBCH (Not for UMTS). The Query cell load dialog box is displayed,
see Figure 2-54.
2-60
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-54 Query Cell Load Dialog Box
2. Select the required cell and click OK. The Result dialog box is displayed, see Figure
2-55.
Figure 2-55 Result Dialog Box
If the query succeeds, the cell information is displayed in the Success cell table.
The CBCH load, in percentage, is displayed in the Load column. The value range
is 0100, with a greater value indicating a higher load.
If the query fails, the cell information is displayed in the Failure cell table.
End of Steps
2-61
SJ-20130524154927-012|2013-06-20 (R1.0)
2.11.4.4 Setting the DRX Mode

This procedure describes how to set whether a cell supports the DRX mode, meaning
whether the terminals of the cell listen to and receive short messages continuously or not.
Context
Only GSM cells support DRX mode setting.
If a cell has messages, its DRX mode setting can be changed only after it is reset to remove
all the messages.
Steps
1. In the CBC Management window, right-click the Cell node in the navigation tree,
and then click Set DRX (Not for UMTS). The Set cell's parameters dialog box is
Figure 2-56 Set Cell's Parameter Dialog Box
2. Select the required cell, and then set a value in the Set DRX text box.
l
l
To enable the cell to support the DRX mode, set the value to 0. By default, a cell
supports the DRX mode.
To disable the cell from supporting the DRX mode, set the value to 40.
3. Click OK. The Result dialog box is displayed, see Figure 2-57.
2-62
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-57 Result Dialog Box
l
l
If the DRX mode setting succeeds, the cell information is displayed in the Success
cell table.
If the DRX mode setting fails, the cell information is displayed in the Failure cell
table. The failure cause is also provided.
End of Steps
2.11.4.5 Viewing the Cell Restart History

This procedure describes how to view the history of cell restarts, including successful and
failed restarts.
Steps
1. In the CBC Management window, right-click the Cell node in the navigation tree,
and then click Restart result. The The history of Restart/Failure message box is
2-63
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-58 The History of Restart/Failure Message Box
l
l
The Restart Cell List shows the restart time of cells that succeeded to restart.
The Failure Cell List shows the restart time of cells that failed to restart.
A cell in the message box is indicated in the format of Mobile Country Code
(MCC)Mobile Network Code (MNC)-Location Area Code (LAC)-Service Area Code
(SAC) of the broadcast domain that the cell belongs to, for example, 460310.
End of Steps
2.11.5 Area Management

An area (broadcast domain) specifies the scope in which short messages are broadcast. In
the NetNumen U31 system, an area may comprise multiple cells of the same base station
controller. The maximum number of cells that can be managed by an area varies with
different base station controllers. For example,
l
l
An area can include a maximum of 200 cells of a GSM BSC.

An area can include a maximum of 600 cells of a UMTS RNC.
The NetNumen U31 system provides the following area management functions:
l
l
l
l
Creating an area
Modifying an area
Deleting an area
Refreshing the information of areas
2.11.5.1 Creating an Area

This procedure describes how to create an area.
Steps
2-64
SJ-20130524154927-012|2013-06-20 (R1.0)
l
l
Right-click the Area node in the navigation tree, and then click Create.
Click the Area node in the navigation tree, right-click an existing area (if any) in
the right pane, and then click Create.
The Create area dialog box is displayed, see Figure 2-59.

Figure 2-59 Create Area Dialog Box
2. In Area ID, enter an area number within the range of 1 to 255.

3. In User label, enter a string containing 1 to 20 characters as the area alias.
4. Click Scan. The Select Cell List dialog box is displayed, see Figure 2-60.
Figure 2-60 Select Cell List Dialog Box
2-65
SJ-20130524154927-012|2013-06-20 (R1.0)
Note:
Only the cells controlled by the same base station controller can be selected for an
area.
5. Select the cells for the area to be created, and then click Ok. The selected cells are
displayed in Cell list.
6. Click Add. The created area is displayed in the Create area dialog box.
7. Click Close. The created area is displayed in the right pane of the CBC Management
window.
End of Steps
2.11.6 Short Message Management

The NetNumen U31 system provides the following short message management functions:
l
l
l
l
l
l
Creating, modifying, and deleting a short message

Sending the alias of a cell
Creating short messages in batches
Exporting short messages
Viewing the history of operations on a short message
Viewing the status of a short message
2.11.6.1 Creating a Short Message

This procedure describes how to create a short message to be broadcast in specific cells.
Context
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 types of base station controllers. For example,
l
l
A short message can be broadcast in a maximum of 200 cells of a GSM BSC.

A short message can be broadcast in a maximum of 600 cells of a UMTS RNC.
Steps
1. In the CBC Management window, right-click the Message node in the navigation tree,
and then click Create message. The Create message dialog box is displayed, see
Figure 2-61.
2-66
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-61 Create Message Dialog Box
2. Set the parameters. For a description of the short message parameters, refer to Table
2-9.
Table 2-9 Short Message Parameter Descriptions
Parameter
Set parameters
Description
Channel
Available channels (all created channels)
Language
Language of the short message to be created

The options are: Chinese simplified and English.
Priority
Priority of the short message

The options are: High, Background, and Normal.
l
A short message with High priority is immediately

broadcast after related NEs receive the message
from the system.
A short message with Background priority is

broadcast only when there is no short message with
High or Normal priority.
2-67
SJ-20130524154927-012|2013-06-20 (R1.0)
Parameter
Description
l
A short message with Normal priority is broadcast

only when there is no short message with High
priority.
Set time
Send mode
Sending mode of the short message

The options are:
l
Send by timer for sending a short message on

schedule.
Send immediately for sending a short message

immediately.
Start time
Time when the short message shall be sent

This parameter is available only when Send by timer is
selected from the Send mode list, meaning that it is not
necessary to set the start time for a short message to
be sent immediately.
The start time must be later than the current system time.
Interval
Broadcast interval of the short message

Value range: 2 to 2048 seconds
Repeated times
Number of times that the short message is to be

broadcast
"0" indicates that the short message will be broadcast
indefinitely.
Area
Determines the scope (cell or area) in which the short

message is broadcast.
The options are:
l
Cell immediate display: The scope is determined

by selected cells. Mobile terminals display the
short message on their screens immediately upon
receiving it.
Cell: The scope is determined by selected cells.

Mobile terminals store the short message into the
message inbox instead of displaying the message
on their screens.
Area immediate display: The scope is determined

by selected areas. Mobile terminals display the
short message on their screens immediately upon
receiving it.
Area: The scope is determined by selected areas.

Mobile terminals store the short message into the
message inbox instead of displaying the message
on their screens.
2-68
SJ-20130524154927-012|2013-06-20 (R1.0)
Parameter
Description
Message content
Enter or load the short message contents to be broadcast

3. Under Set parameters, select a channel, a language, and a priority for the short
message as required.
4. Under Set time, select a sending mode, set the start time when Send by timer is
selected, and set the broadcast interval and the number of repeating times as required.
5. Under Area, select a scope mode.
l If Cell immediate display or Cell is selected, the Select Area dialog box is
Figure 2-62 Select Area Dialog Box
If Area immediate display or Area is selected, the Select GS dialog box is

Figure 2-63 Select GS Dialog Box
2-69
SJ-20130524154927-012|2013-06-20 (R1.0)
6. Select cells or areas as required, and then click Ok. The Select Area or Select GS
dialog box is closed and the scope information is displayed under GS Info.
7. Under Message content, enter the short message contents, or load the message
contents from a predefined TXT file.
8. Click Ok. A message confirming the successful creation of the short message is
displayed.
l If the sending mode of the created short message is Send immediately, a message prompting the creation failure is displayed when the system fails to send the
short message to the selected cells.
l If the sending mode of the short message is Send by timer, a message prompting
successful creation of the short message is displayed even if the links to the
selected cells are broken. The short message is sent to the selected cells when
the start time is reached. If the links recover at that time, the short message can
be successfully sent.
End of Steps
2.11.6.2 Creating Short Messages in Batches

This procedure describes how to create multiple short messages in batches by importing
a predefined TXT file.
Context
Users can import a TXT file that predefines multiple short messages to the NetNumen U31
system for creating short messages in batches. The BSMS command is used to specify a
short message to be created in the TXT file. The command syntax is as follows:
BSMS:Sending mode,Channel,Area,Cell list,Start
date,Start time,Interval,Repeat times,Language,Encoding
form,Content,Priority;
For a description of the command parameters, refer to Table 2-10.
Table 2-10 BSMS Command Parameter Descriptions
Parameter
Description
Sending mode
Short message sending mode

Value range: 0 and 1
l
0: send immediately
1: send on schedule
If this parameter value is set to 0, the parameters Start date and Start
time are not required.
Channel
Channel that a short message belongs to
2-70
SJ-20130524154927-012|2013-06-20 (R1.0)
Parameter
Description
Area
Broadcast scope type that determines the selection of broadcast cells

or areas
Value range: 13, 10, 3, and 0
Cell list
13: area
10: area, supporting immediate short message display
3: cell
0: cell, supporting immediate short message display
List of cells where a short message is to be broadcast

Cell format: "MCC-MNC-LAC-SAC of the broadcast domain that the
cell belongs to".
Multiple cells in the cell list are separated by &.
Start date
Date when a short message is to be sent to related NEs by the system

Date format: YYYY-MM-DD
Start time
Time when a short message is to be sent to related NEs by the system

Time format: HH-MM-SS
Interval
Broadcast interval
Unit: second
Repeat times
Number of times that a short message is to be broadcast

Language
Short message language

Valuer range: 0 and 1
Encoding form
0: Simplified Chinese
1: English
Short message encoding mode

Value range: 1 and 2
l
1: UCS-2 encoding
2: 7-bit encoding
Content
Short message contents enclosed by double quotation marks
Priority
Short message priority

Value range: 0, 1, and 2
l
0: high priority
1: medium priority
2: low priority
The values 0, 1, and 2 correspond to the options (High, Normal, and

Background) in the Priority list in the Create message dialog box.
Multiple command lines in a TXT file are separated by semicolons. For example, the
following contents in a TXT file can be used to create two short messages:
BSMS:0,1,3,"460-3-1-1",2011-07-01,19:15:47,2,55,0,17,"test 1",0;
2-71
SJ-20130524154927-012|2013-06-20 (R1.0)
BSMS:0,1,3,"460-3-1-1",2011-07-01,19:15:47,2,55,0,17,"test 2",0;
Steps
1. In the CBC Management window, right-click the Message node in the navigation tree,
and then click Send Batch Message. The Open dialog box is displayed.
2. Select the directory where the predefined TXT file is saved, click the TXT file, and then
click Open. A message confirming the successful creation of the short messages is
displayed.
3. Click OK. The created short messages are displayed in the CBC Management
window.
End of Steps
2.11.6.3 Broadcasting a Cell Alias

This procedure describes how to create a short message for broadcasting the alias (user
label) of a cell to all mobile terminals in the cell.
Steps
1. In the CBC Management window, right-click the Message node, and then click
SendBtsAlias. The Select Area dialog box is displayed, see Figure 2-64.
Figure 2-64 Select Area Dialog Box
Note:
Only the cells of the same base station controller can be selected.
Users can enter a keyword and click Search to quickly find the target cell.
2-72
SJ-20130524154927-012|2013-06-20 (R1.0)
2. Select one or multiple cells as required.

3. Click Ok. The Send message by cell's user label dialog box is displayed, see Figure
2-65.
Figure 2-65 Send Message by Cell's User Label Dialog Box
4. Set necessary parameters.

5. Click Ok. The NetNumen U31 system sends a short message containing the cell alias
to the selected cell when the start time is reached. This message will then be broadcast
to mobile terminals in the cell.
End of Steps
2.11.6.4 Exporting Short Messages

Context
Users can export all short messages or short messages in a specific status (Unsent,
Sending, or Finished ) from the NetNumen U31 system to an XLS or CSV file.
The following procedure describes how to export all short messages in the NetNumen U31
system to an XLS or CSV file.
Steps
1. In the CBC Management window, right-click the All node under Message in the
navigation tree, and then click Report all. The Open dialog box is displayed.
2-73
SJ-20130524154927-012|2013-06-20 (R1.0)
2. Select a directory for saving the exported short messages, enter a file name, select
a file format, and then click Save. An XLS or CSV file containing all exported short
messages is generated in the selected directory.
End of Steps
2.11.6.5 Viewing the History of Operations on a Short Message

Context
The NetNumen U31 system allows users to view the history of operations on a short
message, including operation time, channel ID, message ID, action, and response related
to each operation.
The following procedure describes how to view the history of operations on a short
message in Finished status.
Steps
1. In the CBC Management window, click the Finished node under Message in the
navigation tree. All short messages in Finished status are displayed in the right pane.
2. Right-click the short message to be viewed, and then click Query historical message.
A dialog box showing the information of historical operations on the short message is
Figure 2-66 Query Historical Message Dialog Box
End of Steps
2-74
SJ-20130524154927-012|2013-06-20 (R1.0)
2.11.6.6 Viewing the Sending Result of a Short Message

This procedure 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 CBC Management window, click the Sending node under Message in the
navigation tree. All short messages in sending status are displayed in the right pane.
2. Right-click the short message to be viewed, and then click Query Sending State. The
The Result of sending message box is displayed, see Figure 2-67.
Figure 2-67 The Result of Sending Message Box
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.
End of Steps
2.12 Configuration Data Collection

The NetNumen U31 system can collect configuration data of managed NEs from the
corresponding OMMs, store the collected data on the server, and then transfer the
configuration data to the client. The client saves the received configuration data in CSV
files in the default directory. Users can view the configuration data details in the CSV
files on the client GUI. A default or user-defined data collection template can be used for
collecting specific configuration data.
2-75
SJ-20130524154927-012|2013-06-20 (R1.0)
Note:
The configuration data collection function is only available when the corresponding OMMs
also support the collection of configuration data.
2.12.1 Creating a Configuration Data Collection Template

Context
The NetNumen U31 system predefines several configuration data collection templates.
The default templates provided by the system cannot be modified or deleted. Users can
create a template as required for collecting specific configuration data. User-defined
templates can be modified, viewed, and deleted.
The following procedure describes how to create a configuration data collection template.
Steps
Application > CM Data Collect > Template Manager from the menu bar. The
Template Management tab is displayed, see Figure 2-68.
Figure 2-68 Template Management Tab
2. On the Template Management tab, click

on the toolbar. The Create template
2-76
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-69 Create Template Dialog Box
For a description of the template parameters, refer to Table 2-11.

Table 2-11 Template Parameter Descriptions
Parameter
Description
Name
Template name
Creator
Template creator
The default creator is the current user. It cannot be modified.
Ne Type
Type of the NEs whose configuration data is to be collected.
Description
Template description
Object for select
Select one or multiple object types, options:

l
By default, the MERGE option is selected. This means

to generate a report file for the same configuration object
corresponding to multiple subnetworks.
If the NO MERDED option is selected, the system generates

one report file for each configuration object based on the
subnetwork.
Attribute for select
Available attributes of the selected object type

Dimmed attributes are those that must be collected when the
corresponding object type is selected. Users can only change the
selection of those activated check boxes.
2-77
SJ-20130524154927-012|2013-06-20 (R1.0)
3. Set required parameters, and click OK. The created template is displayed on the
Template Management tab.
End of Steps
2.12.2 Collecting Configuration Data

This procedure describes how to use a template for collecting configuration data.
Prerequisite
The configuration data collection template to be used is available.
Steps
Application > CM Data Collect > Report Manager from the menu bar. The
Configuration Report management tab is displayed, see Figure 2-70.
Figure 2-70 Configuration Report Management Tab
2. On the Configuration Report management tab, click

Report dialog box is displayed.
on the toolbar. The Get
3. Select an NE type from the NE TYPE list. The available NEs and configuration data
collection templates are displayed, see Figure 2-71.
2-78
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-71 Get Report Dialog Box
4. Select the NEs whose configuration data is to be collected in the SUBNET tree.
5. Select the configuration data template to be used.
6. Click OK. The system collects the required configuration data and transfers the
generated configuration data report file(s) to the default directory on the local client.
The information of generated files are displayed on the Configuration Report
management tab, see Figure 2-72.
Figure 2-72 Collection Result of Configuration Data
7. To view the configuration data in a report file, perform the following operations:
a. Double-click the corresponding row on the Configuration Report management
tab. The directory where the report file is saved is displayed.
b. Double-click the file icon.
configuration data.
The report file is opened, showing the collected
8. To save a report file in another directory, perform the following operations:

a. Click the report file to be saved, and then click
box is displayed.
on the toolbar. The Open dialog
2-79
SJ-20130524154927-012|2013-06-20 (R1.0)
b. Select a directory for saving the report file, and then click Open. The report file is
saved in the selected directory.
End of Steps
2.13 Radio Configuraiton Data Import

2.13.1 Overview
The NetNumen U31 system allows users to import radio configuration data from a
predefined XML file to an NE in a radio access network, such as a Universal Mobile
Telecommunication System (UMTS), Global System for Mobile Communications (GSM),
or Long Term Evolution Frequency Division Duplex (LTE FDD) network. The NE reports
the importing process, modifies the original radio configuration accordingly, and records
the importing result in a log file.
The prerequisites for radio data import are as follows:
l
The corresponding products (radio access systems) are selected during the
installation of the NetNumen U31 server software. For detailed information about the
software installation, refer to the NetNumen U31 R18 Unified Element Management
System Software Installation.
The radio data import function for the radio access system (for example, UMTS) is
enabled in the configuration center on the NetNumen U31 server, see Figure 2-73.
Figure 2-73 Configuration Center Window (UMTS Radio Config Data Import
Enabled)
2-80
SJ-20130524154927-012|2013-06-20 (R1.0)
2.13.2 Importing Radio Configuration Data

The procedures for importing radio configuration data to NEs in GSM and LTE FDD
networks are similar. The following procedure only describes how to import radio
configuration data from an XML file to a UMTS NE.
Prerequisite
The XML file containing the required radio configuration data is ready.
Steps
1. In the client window, select Configuration > UMTS Configuration Application >
Radio Config Data Import. The Radio Config Data Import dialog box is displayed,
see Figure 2-74.
Figure 2-74 Radio Config Data Import Dialog Box

3. Select the XML file to be imported, and then click Open. The selected file path is
displayed in File Path.
4. Select the target NE from the Select RNC list.
5. Click Execute. The importing process and result are displayed in the Output Info
area, see Figure 2-75.
2-81
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-75 Importing Wireless Parameters
6. Click View Log. The Result Data message box is displayed, showing all information
recorded during the importing process, see Figure 2-76.
Figure 2-76 Log Information During the Importing Process
End of Steps
2.14 GSM BCCH Frequency Scheduling Tool

Before the frequency optimization of each cell in the GSM network, it is required to send
a frequency list (consisting of the frequencies of the cells adjacent to all cells and test
frequencies) to mobile phones in batches. Mobile phones then report the six frequencies
2-82
SJ-20130524154927-012|2013-06-20 (R1.0)
with the strongest signals in the list during the test process, which assists network planning
and optimization tools in implementing frequency optimization.
The GSM BCCH frequency scheduling tool sends the frequency list to the OMM in batches,
and the OMM sends the list to mobile phones through the base station controller and base
stations.
2.14.1 Importing the Frequency List

The frequency list contains the frequencies of the cells adjacent to all cells and test
frequencies, and is written in a *.csv-format file by network planning and optimization
personnel. Before the list is sent to mobile phones in batches, the file including the
frequency list must be imported to the NetNumen U31 system.
Prerequisite
The *.csvformat file including the frequency list is ready.
Steps
1. Select Configuration > GSM Configuration Application > GSM BCCH Frequency
Dispatch Tools. The BCCH Frequency Dispatch Tools dialog box is displayed, see
Figure 2-77.
Figure 2-77 BCCH Frequency Dispatch Tools Dialog Box
2. Right-click the root node, and select Import from the shortcut menu. The dialog box
for importing the frequency list is displayed, see Figure 2-78.
2-83
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-78 Dialog Box for Importing the Frequency List
3. Set the time and path parameters. For a description of the parameters, refer to Table
2-12.
Table 2-12 Parameter Descriptions for Importing the Frequency List
Parameter
Description
Start Time
Start time of the scheduled task.

The setting is based on the time of the NetNumen U31 system's
client. If the client time is earlier than the server time, the scheduled
task cannot be executed, and therefore the client should keep time
synchronized with the server.
In addition, due to some time being taken to import the frequency
list and generate the scheduled task, it is recommended to set the
start time at least 10 minutes later than the client time.
Interval
Time interval (in minutes) between each turn of the scheduled task.
The recommended setting is 60.
Create Mode
Mode for importing the frequency list.

Select Optim.
Choose File
Select the *.csv-format file including the frequency list.
4. Click the OK button. The progress bar is displayed.

After the file is imported, a confirmation dialog box is displayed.
5. Click the OK button. The dialog box for importing the frequency list is updated.
2-84
SJ-20130524154927-012|2013-06-20 (R1.0)
A new scheduling node is added under the corresponding node, see Figure 2-79.
Figure 2-79 Newly-Added Scheduling Node
End of Steps
2.14.2 Generating a Scheduled Task

After a scheduled task is generated, when the execution time arrives, the system executes
the corresponding MML to send the frequency list corresponding to a cell to mobile phones,
and displays the execution result.
Prerequisite
The frequency list has been imported, and the scheduling node has been generated.
Steps
1. Right-click the newly added scheduling node, and select View Schedule from the
shortcut menu. All scheduling information corresponding to the scheduling node is
displayed in the right pane of the BCCH Frequency Dispatch Tools dialog box, see
Figure 2-80.
2-85
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-80 Viewing Scheduling Information
The first four records shown in Figure 2-80 indicate that all frequencies corresponding
to cell 1 of base station 1 belonging to BSC 2805 are sent to mobile phones through
four turns. The system specifies the start and end time of each turn based on the
user-defined interval.
2. Click the Generate Task button. The corresponding scheduled task is generated.
The status icon before the scheduling node changes, indicating the task has been
started, see Figure 2-81.
Figure 2-81 Status Icon of the Scheduling Node
3. Right-click the scheduling node, and select View Task from the shortcut menu. All
task information corresponding to the scheduling node is displayed in the right pane,
see Figure 2-82.
2-86
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-82 Viewing the Task Information
The first three records shown in Figure 2-82 are a scheduled task generated to send
the frequency list to mobile phones during the first turn. The tasks in each turn are
executed through the following MMLs:
i.
Update: sends the frequency list to the controller.
ii.
Begin: sends the frequency list from the base station controller to base stations.
iii. End: completes the sending of the frequency list.

When the specified time arrives, the system executes the corresponding MML, and
the execution result is displayed in the ERROR INFO column.
End of Steps
2.15 TD Carrier Frequency Maintenance Management

Description
The NetNumen U31 system provides the query and setting of the maintenance statuses
of carrier frequencies for TD-SCDMA NEs.
A carrier frequency operates in one of the following maintenance statuses:
l
Normal
The carrier frequency is operating properly.
Testing
The carrier frequency is being tested, and the status is not stable (a large number
of alarms may arise). In this status, the analysis of the corresponding alarm and
performance data is meaningless. All or part of alarm and performance data related
to the carrier frequency is not reported to the NetNumen U31 system.
2-87
SJ-20130524154927-012|2013-06-20 (R1.0)
When the carrier frequency is in testing status, configurations can still be reported.
l
FM testing status
In this status, all or part of alarm data related to the carrier frequency is not reported
to the NetNumen U31 system.
PM testing status
In this status, all or part of performance data related to the carrier frequency is not
reported to the NetNumen U31 system.
The maintenance status of a carrier frequency has a lower priority than that of a cell. For
example, if the cell is operating in testing status, and one of the carrier frequencies for the
cell is in normal status, part of alarm and performance data related to the carrier frequency
is not reported to the NetNumen U31 system.
Access Mode
Select Configuration > TD Configuration Application > TD Carrier Maintain Status
Management from the menu bar.
2.15.1 Querying the Maintenance Status of a Carrier Frequency

This procedure describes how to query the maintenance status of a carrier frequency. The
maintenance status of the carrier frequency can be set only after the maintenance status
is known.
Prerequisite
The NetNumen U31 system is connected to the lower-level network management system,
and the system is connected to the BSC.
Steps
1. Select Configuration > TD Configuration Application > TD Carrier Maintain Status
Management. The TD Carrier Maintain Status Management dialog box is displayed,
see Figure 2-83.
2-88
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-83 TD Carrier Maintain Status Management Dialog Box
2. In the left pane, select an NE node from the navigation tree.

3.
(Optional) Specify a cell ID range in the Cell ID text box or enter a keyword in the
Cell Name text box.
If nothing is entered, the maintenance statuses of the carrier frequencies of all cells
corresponding to the NE are displayed.
4. Click the Search button. The maintenance statuses of the carrier frequencies of each
cell corresponding to the NE are displayed, see Figure 2-84.
2-89
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-84 Querying the Maintenance Statuses of the Carrier Frequencies
End of Steps
Related Task
Users can specify the search conditions to query the maintenance status of each carrier
frequency as needed.
2.15.2 Setting the Maintenance Status of a Carrier Frequency

This procedure describes how to set the maintenance status of a carrier frequency.
Prerequisite
l
l
The NetNumen U31 system is connected to the lower-layer network management

system, and the NetNumen U31 system is connected to the BSC.
The TD Carrier Maintain Status Management dialog box is opened, and the
maintenance status of the carrier frequency is displayed.
Steps
1. Select one or multiple carrier frequencies, and set the maintenance status in the
corresponding lists, see Figure 2-85.
2-90
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-85 Setting the Maintenance Statuses of Carrier Frequencies
To change the maintenance statuses of carrier frequencies in batches, select Batch

Process.
2. Click the Modify button. A prompt dialog box is displayed, indicating that the
maintenance status is successfully set.
3. Click the Update button. A prompt dialog box is displayed, indicating that the update
is successful. The maintenance status of each carrier frequency is displayed.
End of Steps
Related Task
Users must change the maintenance status of the carrier frequency to Normal, so that
alarm and performance information can be reported to the NetNumen U31 system.
2-91
SJ-20130524154927-012|2013-06-20 (R1.0)
2-92
SJ-20130524154927-012|2013-06-20 (R1.0)
Figures
Figure 2-1 InterNE Manage Option Dialog BoxSelecting the Product Type.............. 2-2
Figure 2-2 InterNE Manage Option Dialog BoxSelecting the Management
Type ....................................................................................................... 2-3
Figure 2-3 InterNE Manage Option Dialog BoxSelecting RNCs ............................. 2-3
Figure 2-4 InterNE Manage Option Dialog BoxSelecting the NODEBs .................... 2-4
Figure 2-5 InterNE Modify Dialog Box ....................................................................... 2-5
Figure 2-6 NE Relation Data Filter Dialog Box .......................................................... 2-7
Figure 2-7
NE Relation Filtration Results ................................................................. 2-8
Figure 2-8 NE Stability Management Dialog Box (Stability Event Tab)..................... 2-10
Figure 2-9 Stability Event Query Result .................................................................. 2-11
Figure 2-10 Create Task Dialog BoxBasic Information Tab .................................... 2-13
Figure 2-11 Create Task Dialog BoxPolicy Tab ...................................................... 2-15
Figure 2-12 NE Stability Management Dialog BoxMaintain Plan Tab ..................... 2-16
Figure 2-13 Add Maintain Plan Dialog Box.............................................................. 2-16
Figure 2-14 Maintain Status Query and Setting Dialog Box ..................................... 2-21
Figure 2-15 Query Conditions ................................................................................. 2-22
Figure 2-16 Query Results of Base Station Statuses (with NodeB Office
Information) .......................................................................................... 2-22
Figure 2-17 Query Results of Base Station Statuses (without NodeB Office
Information) .......................................................................................... 2-23
Figure 2-18 Shortcut Menu for Setting Base Station Status..................................... 2-24
Figure 2-19 Setting Reason Dialog Box .................................................................. 2-24
Figure 2-20 Base Station Statuses in an XLS File .................................................. 2-26
Figure 2-21 Example of Imported Base Station Statuses ........................................ 2-27
Figure 2-22 VIP NodeB Priority Query and Setting Dialog Box ................................ 2-28
Figure 2-23 Priority Query Condition Setting ........................................................... 2-29
Figure 2-24 Query Results of Base Station Priorities............................................... 2-30
Figure 2-25 Shortcut Menu for Setting Base Station Priority.................................... 2-31
Figure 2-26 Base Station Priorities in an XLS File ................................................... 2-32
Figure 2-27 Imported Base Station Priorities ........................................................... 2-33
Figure 2-28 Transfer Site Dialog Box ...................................................................... 2-35
Figure 2-29 Offline Data Dialog Box........................................................................ 2-37
Figure 2-30 Result Data Dialog Box ........................................................................ 2-39
I
SJ-20130524154927-012|2013-06-20 (R1.0)
Figure 2-31 Result Data Dialog Box ........................................................................ 2-39

Figure 2-32 Inter ME Configuration Import and Export Dialog Box .......................... 2-41
Figure 2-33 Operation Type Config Data Export................................................... 2-41
Figure 2-34 Add Object Dialog Box ......................................................................... 2-42
Figure 2-35 Inter ME Configuration Import and Export Dialog Box Objects
Selected ............................................................................................... 2-42
Figure 2-36 Record in the Selected Data File List ................................................... 2-44
Figure 2-37 Please Input Verification Code Dialog Box ........................................... 2-44
Figure 2-38 Neighbour Cell Tool Dialog Box............................................................ 2-46
Figure 2-39 Operate Object Area ............................................................................ 2-46
Figure 2-40 Operate Object Area (External Files).................................................... 2-47
Figure 2-41 Operate History Area ........................................................................... 2-47
Figure 2-42 Consistency Verification Result in the Detail Information Area (Show
Action Result) ....................................................................................... 2-47
Figure 2-43 Detected Inconsistent Attributes in the Detail Information Area (Show
Result) .................................................................................................. 2-48
Figure 2-44 Relation User Label Management Dialog Box ...................................... 2-50
Figure 2-45 Local Cells and User Labels................................................................. 2-51
Figure 2-46 Local Cells and Neighbor Relations ..................................................... 2-51
Figure 2-47 Cell Maintain Status Management Dialog Box...................................... 2-53
Figure 2-48 Query Results of Cell Statuses ............................................................ 2-53
Figure 2-49 Shortcut Menu for Setting Cell Status................................................... 2-54
Figure 2-50 Status Change of a Short Message...................................................... 2-56
Figure 2-51 CBC Management Window .................................................................. 2-57
Figure 2-52 Create Channel Dialog Box.................................................................. 2-58
Figure 2-53 Reset Cell Dialog Box .......................................................................... 2-60
Figure 2-54 Query Cell Load Dialog Box ................................................................. 2-61
Figure 2-55 Result Dialog Box ................................................................................ 2-61
Figure 2-56 Set Cell's Parameter Dialog Box .......................................................... 2-62
Figure 2-57 Result Dialog Box ................................................................................ 2-63
Figure 2-58 The History of Restart/Failure Message Box ........................................ 2-64
Figure 2-59 Create Area Dialog Box ....................................................................... 2-65
Figure 2-60 Select Cell List Dialog Box ................................................................... 2-65
Figure 2-61 Create Message Dialog Box................................................................. 2-67
Figure 2-62 Select Area Dialog Box ........................................................................ 2-69
Figure 2-63 Select GS Dialog Box .......................................................................... 2-69
II
SJ-20130524154927-012|2013-06-20 (R1.0)
Figures
Figure 2-64 Select Area Dialog Box ........................................................................ 2-72

Figure 2-65 Send Message by Cell's User Label Dialog Box ................................... 2-73
Figure 2-66 Query Historical Message Dialog Box .................................................. 2-74
Figure 2-67 The Result of Sending Message Box ................................................... 2-75
Figure 2-68 Template Management Tab .................................................................. 2-76
Figure 2-69 Create Template Dialog Box................................................................. 2-77
Figure 2-70 Configuration Report Management Tab................................................ 2-78
Figure 2-71 Get Report Dialog Box ......................................................................... 2-79
Figure 2-72 Collection Result of Configuration Data................................................ 2-79
Figure 2-73 Configuration Center Window (UMTS Radio Config Data Import
Enabled) ............................................................................................... 2-80
Figure 2-74 Radio Config Data Import Dialog Box................................................... 2-81
Figure 2-75 Importing Wireless Parameters ............................................................ 2-82
Figure 2-76 Log Information During the Importing Process ..................................... 2-82
Figure 2-77 BCCH Frequency Dispatch Tools Dialog Box ....................................... 2-83
Figure 2-78 Dialog Box for Importing the Frequency List......................................... 2-84
Figure 2-79 Newly-Added Scheduling Node............................................................ 2-85
Figure 2-80 Viewing Scheduling Information .......................................................... 2-86
Figure 2-81 Status Icon of the Scheduling Node ..................................................... 2-86
Figure 2-82 Viewing the Task Information ............................................................... 2-87
Figure 2-83 TD Carrier Maintain Status Management Dialog Box ........................... 2-89
Figure 2-84 Querying the Maintenance Statuses of the Carrier Frequencies ........... 2-90
Figure 2-85 Setting the Maintenance Statuses of Carrier Frequencies .................... 2-91
III
SJ-20130524154927-012|2013-06-20 (R1.0)
Figures
IV
SJ-20130524154927-012|2013-06-20 (R1.0)
Tables
Table 1-1 Wireless Configuration Application Functions ............................................ 1-1
Table 1-2 Supported Functions for Different Radio Access Systems ......................... 1-2
Table 2-1 Description of NE Relation Filtration Parameters ....................................... 2-7
Table 2-2 NE Stability Report .................................................................................. 2-12
Table 2-3 Command Parameter Descriptions .......................................................... 2-14
Table 2-4 Parameter Descriptions for the Add Maintain Plan Dialog Box ................. 2-17
Table 2-5 Buttons in the Maintain Status Query and Setting Dialog Box .................. 2-23
Table 2-6 Buttons in the VIP NodeB Priority Query and Setting Dialog Box ............. 2-30
Table 2-7 Result File Descriptions........................................................................... 2-38
Table 2-8 Channel Parameter Descriptions ............................................................. 2-58
Table 2-9 Short Message Parameter Descriptions................................................... 2-67
Table 2-10 BSMS Command Parameter Descriptions ............................................. 2-70
Table 2-11 Template Parameter Descriptions .......................................................... 2-77
Table 2-12 Parameter Descriptions for Importing the Frequency List....................... 2-84
V
SJ-20130524154927-012|2013-06-20 (R1.0)
Tables
VI
SJ-20130524154927-012|2013-06-20 (R1.0)
Glossary
BCCH
- Broadcast Control Channel
BSC
- Base Station Controller
BTS
- Base Transceiver Station
CBC
- Cell broadcast center
CBCH
- Cell Broadcast Channel
CID
- Cell ID
DRX
- Discontinuous Reception
FDD
- Frequency Division Duplex
GSM
- Global System for Mobile Communications
GSM-R
- GSM for Railway
LAC
- Location Area Code
LTE
- Long Term Evolution
MCC
- Mobile Country Code
MML
- Man Machine Language
MNC
- Mobile Network Code
NE
- Network Element
Node B
- Node B
VII
SJ-20130524154927-012|2013-06-20 (R1.0)
OMM
- Operation & Maintenance Module
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
VIII
SJ-20130524154927-012|2013-06-20 (R1.0)

U31 R18 Configuration Application Operation Guide

Uploaded by

Document Information

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

U31 R18 Configuration Application Operation Guide

Uploaded by

Copyright:

Available Formats

NetNumen U31 R18

Unified Element Management System

Configuration Application Operation Guide

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Serial Number: SJ-20130524154927-012

ZTE Proprietary and Confidential

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

ZTE Proprietary and Confidential

2.8 Neighbor Cell Tool ............................................................................................ 2-44

ZTE Proprietary and Confidential

About This Manual

What Is in This Manual

Provides an overview of the wireless configuration application

module in the NetNumen U31 system, including supported

Describes how to use the wireless configuration application

module for centralized configuration and maintenance.

NetNumen U31 R18 Unified Element Management System Topology Management

ZTE Proprietary and Confidential

ZTE Proprietary and Confidential

Compares interconnection parameters in batches between a

BSC/RNC and corresponding BTSs/Node Bs, and modifies

Manages the relations between a BSC/RNC and the BTSs/Node

Queries stability events occurring in an NE during a period

Adds the information of an NE maintenance plan to exclude

Base station status management

Queries, sets, imports, and exports base station statuses.

Base station priority management

Queries, sets, imports and exports base station priorities.

Manages the hardware, software, and firmware inventory

ZTE Proprietary and Confidential

NetNumen U31 R18 Configuration Application Operation Guide

Supports online and offline site transfer.

Inter-element configuration data

Exports and imports configuration data in file format between

import and export

different NEs for quick configuration.

Neighbor cell tool

Verifies the consistency of attributes between an OMM and

User label relation management

Verifies the consistency between the user labels of local cells

Cell broadcast management

Provides management functions for the cell broadcast

Cell status management

Queries and sets cell statuses.

Configuration data collection

Collects configuration data of NEs from corresponding OMMs.

Radio configuration data import

Imports radio configuration data from a predefined XML file to

BSC = Base Station Controller

RNC = Radio Network Controller

BTS = Base Transceiver Station

CBC = Cell Broadcast Center

ZTE Proprietary and Confidential

Chapter 1 Wireless Configuration Application Overview

UMTS = Universal Mobile Telecommunication System

GSM = Global System for Mobile communication

GSM-R = GSM for Railway

LTE-TDD = Long Term Evolution-Time Division Duplex

LTE-FDD = Long Term Evolution-Frequency Division Duplex

TD-SCDMA = Time Division-Synchronization Code Division Multiple Access

1.2 Implicit Prerequisites

ZTE Proprietary and Confidential

NetNumen U31 R18 Configuration Application Operation Guide