NetNumen U31 RAN

NetNumen™ U31 RAN
Basic Feature Description

ZTE PARSIAN CO. Product Type Technical Proposal
NetNumen™ U31 RAN Basic Features Description
Version Date Author Approved By Remarks
V1.0 2010-07-15 ZhuBing Not open to the Third Party
© 2011 ZTE PARSIAN Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be
disclosed or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document
is subjected to change without notice.
ZTE Confidential Proprietary © 2011 ZTE PARSIAN Co. All rights reserved. 1
TABLE OF CONTENTS
1 Instruction ................................................................................................................ 4
2 Topology Management ............................................................................................ 5

2.1 ZXO-07-01-001 Topology View ................................................................................. 5
2.2 ZXO-07-01-002 Key CM/FM/PM Information Display ................................................ 8
3 Configuration Management ..................................................................................... 9

3.1 ZXO-07-02-001 Configuration Management (UTRAN) .............................................. 9
3.2 ZXO-07-02-002 Configuration Management (GERAN) ............................................ 11
3.3 ZXO-07-02-004 TC Configuration (GERAN) ............................................................ 12
3.4 ZXO-07-02-005 Multi-Mode Base Station Management (GERAN&UTRAN)............ 13
3.5 ZXO-07-02-006 Multi Configuration Sets (GERAN&UTRAN) .................................. 14
3.6 ZXO-07-02-007 Guide for Configuration .................................................................. 15
3.7 ZXO-07-02-008 Configuration Data Synchronization ............................................... 16
3.8 ZXO-07-02-009 Configuration Data Availability Check ............................................ 18
3.9 ZXO-07-02-010 Neighboring Cell Configuration Data Check (GERAN&UTRAN) .... 19
3.10 ZXO-07-02-011 Configuration Data Template (GERAN&UTRAN)........................... 20
3.11 ZXO-07-02-012 Fast Commissioning of Site (GERAN&UTRAN) ............................. 21
3.12 ZXO-07-02-013 Base Station Re-homing (GERAN&UTRAN) ................................. 22
3.13 ZXO-07-02-014 Configuration Data Upload (GERAN&UTRAN) .............................. 23
3.14 ZXO-07-02-015 Configuration Rack Map (GERAN&UTRAN) .................................. 23
3.15 ZXO-07-02-016 Status Monitoring ........................................................................... 24
3.16 ZXO-07-02-017 Centralized configuration Management (GERAN&UTRAN) ........... 27
3.17 ZXO-07-02-018 Configuration Data Output/Input .................................................... 28
3.18 ZXO-07-02-019 Configuration Data Collection (GERAN&UTRAN) .......................... 29
3.19 ZXO-07-02-020 Hardware Inventory ....................................................................... 30
4 Fault Management ................................................................................................. 32

4.1 ZXO-07-03-001 Alarm Monitoring ............................................................................ 32
4.2 ZXO-07-03-002 Alarm and Notification Query ......................................................... 34
4.3 ZXO-07-03-003 Alarm Handle ................................................................................. 35
4.4 ZXO-07-03-004 Alarm Correlation Rule................................................................... 37
4.5 ZXO-07-03-005 Alarm Filter Rule ............................................................................ 38
4.6 ZXO-07-03-006 Current Alarm Forwarding .............................................................. 39
4.7 ZXO-07-03-007 Alarm Synchronization ................................................................... 40
4.8 ZXO-07-03-008 Alarm Knowledge Database .......................................................... 41
4.9 ZXO-07-03-009 Visual Alarm................................................................................... 42
4.10 ZXO-07-03-010 Coloured and Audible Alarm .......................................................... 43
4.11 ZXO-07-03-011 Alarm Box Management ................................................................ 44
4.12 ZXO-07-03-012 External Alarm Access ................................................................... 44
4.13 ZXO-07-03-013 Diagnosis and Testing ................................................................... 45
4.14 ZXO-07-03-014 VIP Site Alarm Monitoring (GERAN&UTRAN) ............................... 46
5 Performance Management .................................................................................... 47

5.1 ZXO-07-04-001 Measurement Task Management .................................................. 47
5.2 ZXO-07-04-002 KPI Management ........................................................................... 48
5.3 ZXO-07-04-003 QoS Monitoring .............................................................................. 50
5.4 ZXO-07-04-004 Performance Data Management .................................................... 51
5.5 ZXO-07-04-005 Performance Report ...................................................................... 53
5.6 ZXO-07-04-006 Performance Data Real-time Query ............................................... 54
6 Software Management ........................................................................................... 55

6.1 ZXO-07-05-001 Software Management ................................................................... 55
6.2 ZXO-07-05-002 Nodes SW Version Check ............................................................. 57
6.3 ZXO-07-05-003 Software Installation and Upgrade ................................................. 57
6.4 ZXO-07-05-004 Software Inventory ......................................................................... 58
7 System Management ............................................................................................. 59

7.1 ZXO-07-06-001 Data Backup and Restore .............................................................. 59
7.2 ZXO-07-06-002 System Self-Monitoring .................................................................. 60
7.3 ZXO-07-06-003 Link Monitor ................................................................................... 61
8 Security Management ............................................................................................ 63

8.1 ZXO-07-07-001 Node Hardening ............................................................................. 63
8.2 ZXO-07-07-002 Network Secure Infrastructure ....................................................... 64
8.3 ZXO-07-07-003 User Management ......................................................................... 64
8.4 ZXO-07-07-004 User Authorization ......................................................................... 67
8.5 ZXO-07-07-005 Role Management ......................................................................... 67
8.6 ZXO-07-07-006 Log Management ........................................................................... 68
9 Trace Management ................................................................................................ 71

9.1 ZXO-07-08-001 Signaling Trace (GERAN) .............................................................. 71
9.2 ZXO-07-08-002 Signaling Trace (UTRAN) .............................................................. 72
10 O&M Infrastructure ................................................................................................ 73

10.1 ZXO-07-09-001 Telnet Access ................................................................................ 73
11 Tool ......................................................................................................................... 73

11.1 ZXO-07-10-001 Health Check(GERAN) .................................................................. 73
11.2 ZXO-07-10-002 Health Check (UTRAN).................................................................. 74
11.3 ZXO-07-10-003 MML Command Terminal .............................................................. 75
11.4 ZXO-07-10-004 Online Help .................................................................................... 77
1 Instruction
The complete set of Feature Description of Network Management system NetNumen™
U31 for radio access network: NetNumen™ U31 RAN Basic Feature Description and
NetNumen™ U31 RAN optional Feature Description.
Table 1 The Classification Definition of ZTE U31 Features
Class No. Class Description

01 Topology Management
02 Configuration Management
03 Fault Management
04 Performance Management
05 Software Management
06 System Management
07 Security Management
08 O&M Infrastructure
09 Northbound Interface
10 Tools
11 Others
2 Topology Management
The topology management of the U31 system provides a visual NE relation display and
a network topology map which can be operated. The topology map employs the industry
prevailing structure of left tree and right diagram. On the left of the view is the NE
topology tree, organized according to the configuration relation of NEs. On the right of
the view is the panorama display of the NE devices, and it can display the NE topology
structure by several levels. The panorama provides a panorama device display. The user
can customize the background of the map, and set the longitude and latitude of the map.
The functions of the topology map are closely connected with each management module.
The alarm information and configuration information off the NE can be viewed through
the topology map. Configuration, alarm, performance and diagnosis modules of NEs can
be invoked. The topology management provides the functions such as logic view,
grouping nodes, virtual NE, virtual link. The user can manage the devices and set virtual
NEs in group, convenient for network display and analysis. The panorama provides the
operations of part zooming in, searching, cascading display, and provides personalized
interface setting. The user can customize the interface setting as his like, for example
the icon, interface color, and view size. The U31 client GUI interface supports ToolTips
function. When the mouse stops at the tools icon, there will be a tip to explain the use of
the icon.
2.1 ZXO-07-01-001 Topology View

Basic/Optional: Basic
Feature change: N/A
HW&SW Dependencies: N/A
Commercial Attention: N/A
2.1.1 Summary
Topology view shows all network equipments (NE) on view and connections between
NEs.
This feature also provides navigating to configuration management, fault management,

and performance management.
The topology management module only displays NE device nodes that are allowed to be
operated by User.
2.1.2 Benefits
Topology management gives graphical overview of the whole network, which helps to
manage all NEs conveniently. It is very easy to find the connections between NEs or
sub-networks. This feature provides monitoring of the network with alarms and KPI.
This feature supports topology data display based on user authority.
Synchronization between topological data and configuration data is supported to ensure

the consistency.
Fast navigation to CM/FM/PM interfaces provides users quick entry to locate NE or sub-
network which they concern.
2.1.3 Description
The general layout of the topology view is as the topology management tree is shown in
the left pan and topology map is shown in the right pan. Topology tree shows all
topological nodes of network (GERAN/UTRAN). Topology map indicates network
architecture. Topology map shows inter-dependent relationship in a layers mode and
uses lines to show the interconnection of equipment. Topology map only shows all
nodes of present layer.
Topological View:
In topological view, nodes present geography location and NEs are contents of nodes,
which mean these NEs are in the location. A node also can be contained in another
node, that is, the contained node is a part of the containing node, etc: That a Node B is
included in a node means the Node B's location. And this node can be contained in a
regional node.
Each node or NE has an alarm counter. The color of the node or NE shows the current
alarm level.
User can search the NE with the name or its geographic information.
Topology Navigation Tree:
All physical devices information from configurations and collections are displayed in the
navigation tree mode. Nodes in the navigation tree and topological views are in one-to-
one correspondence relation. The navigation tree is synchronized with topological views.
The navigation tree provides the navigation function for topological views. The
topological view synchronously displays nodes related to the selected navigation tree
node. Through right-clicking a navigation tree node, functions related to this node are
available such as attribute view, modification of NE information, and statistic of sub
nodes.
Physical View and Logical View
Topology tree and topology map provides logical overview of all nodes and equipment of
the overall network in layers and by various sub-views. Sub-views include physical sub-
view and logical sub-view.
Physical sub-view is unique and cannot be deleted. It presents the basic relationship of
equipment managed by U31, for example, the architecture and inter-connection details.
The components of physical sub-view include NEs, link, virtual NEs, virtual links and
virtual link sets.
Logical sub-view is a user defied view which is defined by subscribers themselves for
their own convenience and understanding. Subscribers can create more than one logical
view. Each logical sub-view includes groups and equipment in corresponding group.
This equipment resource (NEs and links) is reflected in physical sub-view.
Display Control of Topological View:
A topological view supports the shift with the whole diagram, zoom-in by levels, zoom-
out by levels, restore, display of whole diagram, and partial zoom-in. User can select
one or more nodes in the topological view. User can browse the forward/backward
topological view. Any browsed layer can be located.
A topological view can be displayed in full screen. The designated NE device can be
searched in the topological view.
Topological View Automatic Layout:
The layout modes provided by the topology management module include layered layout,
tree layout, radial layout, explosive layout, and equidistance layout. The topological view
displays NE nodes according to the configured layout mode.
Map Setting:
When User configures a map, select a map file and configure the display range by
specifying the longitude and latitude. User can also use the default map provided by the
system.
NE Grouping in Logical View:
In logical view, provide functions such as creating grouping, modifying grouping, setting
members of the grouping, moving the grouping, deleting the grouping, and setting the
grouping rule.
In the logical view created by User, User can re-customize the structure relation of the
NE device node in the physical view. The grouping node is a logical node defined by
User. NE devices of the physical view can be allocated to the grouping node. Through
the grouping user, User can create the topology structure with any layer relation
according to the requirement.
Topological View Filtering:
The filtering of the topological view includes the filtering based on topological tree and
filtering based on conditions.
Filtering based on topological tree: Construct a filtering tree based on the node of NE,
grouping, link set, grouping name, NE name, and the number of links. User only needs
to select a node in the filtering tree. The filtering setting of the topological view is
completed.
Filtering based on conditions: Input the name of filtering NE to complete the filtering
setting.
Topology Data Display Based on User Authority:
This function allows the topology management module to display NE devices that the
login user has the right to operate only.
Virtual NE and Virtual Link:
The topology management module provides the functions such as creating a virtual NE,
modifying a virtual NE, and deleting a virtual NE. The operation and control of a virtual
NE is the same as the real physical node.
The topology management module provides functions such as creating virtual link,
modifying virtual link, deleting virtual link, and viewing link attributes. The operation and
control of a virtual link is the same as the real physical link node.
Logical Nodes and Link Control:
The control of the topology node includes: Search, move, save, lock, and unlock.
Specific functions include: Status display, type display, attribute view and modification,
link lock/unlock, tool tip window, right-click menu, and double-click info window.
Voluntary Synchronization of Topological Data:
Data of the topology management module is from the configuration and collection. Data
in the topology management module may be inconsistent with the configuration data
owing to various reasons. The synchronization function of topology data can ensure their
consistency.
Longitude and Latitude Coordinates:
The position information in the topological view can be displayed with the node
geographic position through the map and longitude and latitude coordinates.
Fast entry to CM/FM/PM Interfaces:
Navigation icons are provided for quick entry to Configuration Management/Fault

Management/Performance Management interfaces.
2.2 ZXO-07-01-002 Key CM/FM/PM Information Display

Feature change: N/A
HW&SW Dependencies: Topology View (SW)
2.2.1 Summary
This function can display alarms, performance and configuration information of NEs in
topology views. ALL the information is refreshed according to practical network.
2.2.2 Benefits
This feature helps to easily focus on NE configuration data, important alarms, and KPI
information in topology view. Easy navigation to CM/FM/PM interfaces is available.
2.2.3 Description
Configuration management information display:
Users can see a simple structure of every network element in the map.
User can also access to NE configuration interface to perform configuration operations

of NE.
Fault management information display:
The nodes’ color on topology tree indicates node status and alarm status. Alarm is only
indicated with highest severity level by color. The alarm is shown by color and times
icons on the topology map.
User can also access to fault management interface to perform fault operations of NE.
Performance management information display:
User can see KPI directly from the topology interface. It displays KPI of NE depending in
a tool tip at the cursor position. It only displays the important KPI of NE. User can
customize KPI to be displayed.
User can also access to performance management interface to perform performance

operations of NE.
3 Configuration Management
The configuration management of the U31 system provides the configuration function of
NE to the user. It can manage the NE devices topological nodes of network
(GERAN/UTRAN) such as iBSC, iTC, RNC, BTS, Node B, Multi-mode BS of ZTE. The
configuration management provides the function of adding, deleting, modifying and
viewing the NE data. And combined with topology management, the user can
conveniently view the configuration and modify the configured information conveniently.
The user can configure the information in the U31 server, and load the configuration
data to the NE at once by the way of data transporting. The configuration management
of the U31 system also provides the function of software version management, dynamic
data management, and secure variable management.
3.1 ZXO-07-02-001 Configuration Management

(UTRAN)
Feature change: N/A
3.1.1 Summary
System manages configuration of all the managed objects of UTRAN; customizes
network resource models (NRM) conforming to 3GPP; offers operations like add, delete,
modify and query on all objects (MO).
3.1.2 Benefits
Help to integrate resources and optimize network structure.
A comprehensive tool equipped with friendly and interactive GUI configuration interface.
3.1.3 Description
UTRAN Configuration Management (CM) is a user-driven (off-line) application. CM
supports multiple simultaneous users. As soon as any user changes data in a resource,
it will be locked for all other users.
Configuration management provides complete constraint checking set and visualized

information. All parameters can be exported and wireless parameters can be imported.
CM operation log is supported:
CM supports an Audit Trail, so all the user actions on individual resource objects are
logged and can be traced, as well as all operations on the nodes while committing the
changes.
RNC Configuration Categories:
Physical configuration includes configuration of rack, shelf, slot and board.
Transmission configuration includes ATM transmission, all-IP transmission and line-

sharing transmission (hybrid transmission).
Wireless configuration includes configuration of overall parameters, cell information,

channel information, service sub-category, measurement and neighboring cell
information.
Node B Configuration Categories:
Physical configuration includes configuration of rack, shelf, board, antenna, fan, tower
controller and electrically adjustable antenna (AISG).
Transmission configuration includes ATM transmission, all-IP transmission and line-

sharing transmission (hybrid transmission).
Wireless configuration includes configuration of sector information, cell information and

carrier information.
Bulk Parameters Modification:
Batch modification of the common parameter of several MOs under the same category
via GUI.
Execute files that contain several MML commands.
System provides corresponding templates in XLS format facility containing several

objects of various types. Users can modify different bulk parameters of all objects in the
template, and then import to system.
Site commissioning/Debugging setting:
Setting of single/bulk site commissioning/debugging status is supported. Users can

judge whether Node B or SDR is working or waiting for debugging from Node B or SDR
debugging identifier.
3.2 ZXO-07-02-002 Configuration Management

(GERAN)
Feature change: N/A
3.2.1 Summary
System manages configuration of all the managed objects of GERAN; customizes
network resource models (NRM) conforming to 3GPP; offers operations like add, delete,
modify and query on all objects (MO).
3.2.2 Benefits
3.2.3 Description
GERAN Configuration Management (CM) is a user-driven (off-line) application. CM
supports multiple simultaneous users. As soon as any user changes data in a resource,
it will be locked for all other users.
CM operation log is supported:
CM supports an Audit Trail, so all the user actions on individual resource objects are
logged and can be traced, as well as all operations on the nodes while committing the
changes.
CM offers the following data configurations:
Public resource configuration includes establishing GERAN sub-network, BSC network

elements management, configuration sets and BSC overall resources. It is the basis of
data configuration.
BSC physical equipment configuration mainly includes establishing data like BSC rack,
shelf, board, and daughter card.
Abis interface configuration whose bearing is E1, T1, IP or IPoverE1 is supported. PCM
configuration information, T1 configuration, interface board and IP interface board are
contained in this configuration domain.
A interface and Ater interface configuration whose bearing is E1 or IP is supported.
GB interface configuration whose bearing is E1 or IP is supported.
Other configurations includes basic configuration of clock board, power board alarm
parameter configuration and module parameter configuration
Wireless resource configuration mainly includes configuration of cell, frequency hopping,

transceiver, neighboring cell interference, neighboring cell handover, neighboring cell
reselection, neighboring cell handover and reselection, UTRAN neighboring cell
handover, UTRAN neighboring cell handover, UTRAN neighboring cell selection,
handover and reselection, GERAN external cell and UTRAN external cell.
Bulk Parameters Modification:
NE Parameter modification in batch is used for modifying the common parameters MOs,
such as BSC, cell, site, TRX, power control, Handover control, adjacent cell settings etc.
Three types of modification modes are supported.
Batch modification of the common parameter of several MOs under the same category
via GUI.
Execute files that contain several MML commands.
System provides corresponding templates in XLS format facility containing several

objects of various types. Users can modify different bulk parameters of all objects in the
template, and then import to system.

judge whether BTS is working or waiting for debugging from BTS debugging identifier.
3.3 ZXO-07-02-004 TC Configuration (GERAN)

Feature change: N/A
3.3.1 Summary
System manages configuration of iTC; offers operations like add, delete, modify and
query on all objects (MO).
3.3.2 Benefits
Finish the data configuration required for commissioning of iTC.
3.3.3 Description
CM offers the following data configurations:
Physical configuration includes configuration of exchange, rack, shelf, module, unit, sub-
unit; attribute configuration of the configuration bureau connected with unit includes the
configuration of this bureau and its neighboring bureau signaling point, basic
configuration parameter for office direction.
N7 MTP data configuration includes configuration of signaling link, signaling routing,

signaling office direction and physical channel that ensures signaling information bearing.
N7 SCCP data configuration mainly refers to the configuration of signaling sub-system.
Service configuration includes configuration of A interface, Ater interface, resource

circuit semi-fixed connection and physical channel that ensures service bearing.
3.4 ZXO-07-02-005 Multi-Mode Base Station

Management (GERAN&UTRAN)
Feature change: N/A
3.4.1 Summary
This feature offers unified management for multi-mode base station in GERAN and
UTRAN co-exist or smooth evolution scenario.
3.4.2 Benefits
This feature offers GERAN and UTRAN unified wireless base station management.
When multi-mode network deployed, all configuration of GERAN and UTRAN can be
supported via unified GUI.
3.4.3 Description
For one multi-mode base station, there is one set of software and hardware for GERAN
and UTRAN. Switch of mode is realized through modifying related configuration
parameters.
Three scenarios for multi-mode base station management:
One-mode network: there is either 2G NE or 3G NE.
Multi-mode network: 2G and 3G co-exist.
Multi-mode network: 2G evolve to 3G smoothly.
3.5 ZXO-07-02-006 Multi Configuration Sets

(GERAN&UTRAN)
Feature change: N/A
3.5.1 Summary
Each managed object can have multi configuration sets in U31.
This feature mainly describes the operations of management object in configuration

interface including enquiry, comparing bulk modificaiotn of MO, copy and paste of
managed objects.
3.5.2 Benefits
User can save current configuration data during modification. User can revert back to
restore the saved configuration data in case of failure or unsuccessful modification.
This feature makes it easy for the user to compare modified configuration data with the
saved configuration data. U31 can monitor and maintain managed object during
modification and help the users to keep multi sets of configuration data, which will be
used in different conditions.
3.5.3 Description
Multi Configuration Sets:
Multi configuration sets are kept in U31 system. User can create/delete/modify
configuration sets. User can set configuration by single and bulk mode. User can
compare data among different configuration sets and can choose a configuration from
the set of configurations as current configuration and download it to NE. User can export
and import configuration data by single and bulk mode.
Configuration operations can be performed in the current configuration set. For

scheduled configuration, backup configuration sets can be utilized. Network planning &
optimization, training, configuration in advance, configuration data backup, configuration
data restore, configuration sets switch over, rollback, etc. can also be executed based
on backup configuration sets.
Configuration Data Backup and Restore in U31:
Configuration data can be backed up and restored in U31 in ZTD format files.
Configuration Data Integrity Check:
U31 supports configuration data integrity check in the scope of configuration resource
tree. If there is configuration data miss or error, corresponding information shall be listed
with corresponding MO ID.
Managed Object Management Tool:
Find the object attribute in the management tree, for example: cell in the radio resource,
enter cell ID, commit rapid inquire to display the detailed parameters in the configuration
management interface, modify and inquire the parameters which have the same
attribute at the same time.
The configuration comparison function of U31 system enables users to make

configuration comparison at different levels. For example, the system supports managed
object comparison, configuration sub-tree comparison and configuration sets
comparison. So configuration data can be well checked and verified and configuration
error can be located easily. The comparison results are clear in the comparison list
which can also be saved.
Furthermore, U31 system supports the copy and paste of objects and object sub-trees to
facility operation and maintenance. Users can copy and then paste similar data during
data creation and modification, thus reducing repetitive work and improving the work
efficiency.
3.6 ZXO-07-02-007 Guide for Configuration

Feature change: N/A
HW&SW Dependencies: Configuration Management (SW)
3.6.1 Summary
This feature provides guide for configuration in bulk. Bulk boards’ creation and deletion
guide, transmission resource creation guide, re-homing guide for adjacent office and
adjacent base station, and fast configuration guide for bulk wireless cell/adjacent cell
configuration are supported.
3.6.2 Benefits
Provide guide for fast configuration for creating objects via configuration files import.
Provide guide for fast configuration with initialized physical and radio configuration data.
Provide guide for modification of configuration data in bulk.
3.6.3 Description
System offers configuration guide to complex objects management, the operations and
objects related are as below:
Bulk boards’ creation and deletion guide:
Users can create bulk boards by importing files as XLS and XML.
Transmission resource creation guide:
System support office transmission resource creation guide for adjacent RNC, BSC,
Node B, BTS, and SDR. Various transmission network types (such as ATM, IP, ATM+IP)
are supported.
Re-homing guide for adjacent office and adjacent base station:
System support one or more adjacent office Transmission resource inside RNC or BSC,
migrate from current transmission interface board to another board with the data of
interface not changed. When ground interface and radio data not changed, system can
support one or bulk base stations re-homing to different RNC/BSC.
Fast configuration guide for bulk wireless cell/adjacent cell configuration.
3.7 ZXO-07-02-008 Configuration Data Synchronization

Feature change: N/A
3.7.1 Summary
Configuration data synchronization from EMS server to NE is provided. Whole-table
synchronization and Increment-table synchronization are supported.
3.7.2 Benefits
Configuration data synchronization from EMS server to NE provides centralized
management for configuration data.
3.7.3 Description
ZTE U31 support data configuration offline by synchronizing all and modified tables to
go in effect.
Data synchronization is synchronizing ZTE U31 data in database to NE, the data
synchronized can only be the major configuration data set.
Data synchronization can be conducted in two modes: whole-table synchronization and

increment-table synchronization. The synchronization mode supported by an element is
decided by the parameter Synchronization State in the major configuration set of this
element.
Whole-table synchronization
Whole-table synchronization means to synchronize all the configuration data related

to this element in the database of the EMS server with network elements. Obviously,
each operation is time-consuming for it must process quantities of data. System
support bulk whole-report synchronization function, users can carry bulk base
station with same type whole-report synchronization.
Increment-table synchronization
Increment-table synchronization need not synchronize all configuration data but

only the latest updated data.
Users can synchronously download the current configuration set of ZTE U31 system to
the specified NE by using the operation object downloading function.
Users can also use the configuration data uploading function of an NE to obtain or
backup the current data of an NE through configuration management of ZTE U31
system.
3.8 ZXO-07-02-009 Configuration Data Availability

Check
Feature change: N/A
3.8.1 Summary
U31 supports validity check of configuration data within its scope. This validity check
contains data validity and logic, such as integrity, accuracy and completeness.
3.8.2 Benefits
Before users synchronize data to NE, they can check the validity of data within its scope
so as to reduce the pU31ibility of abnormal service caused by wrongly configured data.
Users can modify the abnormal data according to the data consistency check result.
3.8.3 Description
UTRAN Configuration Data Check:
Transmission parameter check between RNC and Node B/SDR
Radio parameter check between RNC and Node B/SDR
ATM address check
ATM parameter (AAL5, AAL2 VPI/VCI)
GERAN Configuration Data Check:
TS Data value check includes whether the BCCH TSC is the same with this Cell BCC
and frequency hopping restriction
Completeness check for cell includes whether there is HOC, POC in the cell, whether
there is TRX in the cell, and whether there is a single channel in the cell.
Configuration rules check includes whether the LAI+CI, and the MCC+MNC+LAC+CI of
all BSCs are unique, whether the neighboring cell frequency is same or adjacent in both
frequency hopping case and non frequency hopping case, and whether the cells are
mutually in each other’s adjacent cells list. For example, when cell 1 is in cell 2’s
adjacent cells list, then cell 2 should be in adjacent cells list of cell 1.
Configuration Data Consistency Check between U31 and NE:
It is possible that there is inconsistency between U31 and NE. When link of NE and U31
is established, it shall be automatically triggered that consistency check between U31
and NE. When inconsistency found, it shall remind users via GUI.
3.9 ZXO-07-02-010 Neighboring Cell Configuration

Data Check (GERAN&UTRAN)
Feature change: N/A
3.9.1 Summary
This feature provides configuration data check of serving cell and neighboring cell. And
serving cell without neighboring cell will also be checked.
3.9.2 Benefits
During configuration, it is usually occurred that serving cell without neighboring cell or
wrong data of serving cell and neighboring cell. This feature provides facilities for users
to focus on the problems. Through configuration data check of serving cell with
neighboring cell and serving cell without neighboring cell, check report will be generated
or automatic modification will be performed.
3.9.3 Description
This feature includes following functions:
All serving cell without neighboring cell within base station controller or different
controllers can be queried.
Neighboring cell configuration data check.
z Neighboring cell configuration data check shall be performed. Configuration data

check of serving cell with neighboring cell and serving cell without neighboring cell
are available for users. U31 system then notifies all NE to generate their serving
cells, neighboring cells and neighboring relations. NE finishes the work, sends data
to U31 and informs U31 of detailed data from other NE.
When U31 gets the data, data package from NE is sent to the target NE by ftp, and
neighboring cell configuration data check shall be performed on NE. U31 will
gather all the results from NE and generate check reports, and remind user of the
path where check reports saved.
z Automatic configuration data modification of neighboring cell when disagreement
When check reports generated, user can determine to modify the configuration data
according to the check reports. When modification operations performed, user can
perform automatic configuration data execution. U31 will gather all the results from NE
and generate check reports, and remind user of the path where check reports saved.
3.10 ZXO-07-02-011 Configuration Data Template

(GERAN&UTRAN)
Feature change: N/A
3.10.1 Summary
This feature provides system configuration data template and configuration data
template which users can modify.
3.10.2 Benefits
This feature provides facilities for users using system configuration data template and
configuration data template which users can modify. With configuration data template
which users can modify, users can save typical configuration data as templates for
backup to reduce massive human resource and mistake.
3.10.3 Description
Two modes of configuration data templates are supported:
System Configuration Data Template:
When users create or modify an NE, users can use this configuration data template as
the standard configuration template for all the NE in the network. The system provides
RNC/BSC device templates and Base station device templates, rack templates, and
wireless resource templates.
Configuration Data Template Which Users Can Modify:
Users can edit the parameters for an NE in an XLS file and set all the relevant fields, the
system will generate configuration data for all the sites according to the template. The
system provides physical and transmission templates, and wireless resource templates
for users to modify and use.
3.11 ZXO-07-02-012 Fast Commissioning of Site

(GERAN&UTRAN)
Feature change: N/A
3.11.1 Summary
This feature converts planning data of SDR to SDR configuration data. User prepares
planning data of SDR through XLS or XML format template and import to U31 to
complete the data configuration.
3.11.2 Benefits
This feature provides a very convenient way to configure bulk data of U31. It reduces the
workload of bulk physical repetition and radio parameter configuration.
Fast commissioning function can improve commissioning and maintaining efficiency, so

as to save resource of users especially in commissioning of sites.
3.11.3 Description
Configuration Template:
Base station data planning configuration template is mainly composed of physical data
and wireless resource data of base station. XLS format file is adopted to arrange this
data. This template is regarded as the input port of U31, supporting following functions:
Configure physical and wireless data of SDR in batch.
Check the validity and logic of configuration data, and provide information to prevent the
system from interference.
New Site Commissioning:
U31 system supports fast commissioning of SDR. In field test, configuration data needed
configured of each SDR is too much and the process is also complicated, so it is easy to
make mistake. Fast commissioning of SDR is mainly used for field test.
U31 system can generate XML bulk file based on XLS configuration file written in
advance, then synchronize to site by whole table synchronization. Direct import and
export in XML format is supported. And direct XLS format files import and export is also
supported to facility check and edit for user.
Current Site Configuration Data Modification in Bulk:
It is also used in bulk modification of the current base station data, users can enter bulk
export interface, select NE and export path wanted, and transfer XML format to XLS
format for the configuration file, then modify the XLS file to generate new whole table
configuration file, so it is convenient to phase modified configuration data into new sites
as backup configuration data set.
3.12 ZXO-07-02-013 Base Station Re-homing

(GERAN&UTRAN)
Feature change: N/A
3.12.1 Summary
This feature supports migrating some of the sites under one BSC/RNC to another inside
EMS, or reallocating the BTS/Node B in different BSC/RNC to balance traffic load.
3.12.2 Benefits
Rapid construction and cutover of sites accelerates engineering and enhances working
efficiency.
Make good use of resource, optimize bandwidth allocation between controller and
BTS/Node B, and enhance the wireless accessing performance of UE.
3.12.3 Description
This Feature Supports Following Functions:
Intra-BSC/RNC re-homing: bandwidth adjust at interface board
RNC: ATM re-homing among interface boards to adjust bandwidth because of

bandwidth variance of interface boards and ATM port of other links.
Inter-BSC/RNC re-homing:
It is performed that configuration data of sites is sent intra ZTE U31 system. ZTE U31
system activates and sends configuration data of two RNC or BSC. On-line and offline
planning data or source data sent from one RNC/BSC to another RNC/BSC are
supported. Planning data or source data include cell and neighbor cell information.
Inter-U31 server:
It is performed that configuration data of sites is sent inter ZTE U31 system. ZTE U31
system activates and sends configuration data of two RNC or BSC. On-line and offline
planning data or source data sent from one RNC/BSC to another RNC/BSC are
supported. Planning data or source data include cell and neighbor cell information.
Online re-homing of base station:
This function is performed that base station migrate from one RNC or BSC to idle links of
another RNC or BSC. MML commands are utilized for base station re-homing to
accomplish serving cell and neighboring cell re-homing.
3.13 ZXO-07-02-014 Configuration Data Upload

(GERAN&UTRAN)
Feature change: N/A
3.13.1 Summary
This feature supports configuration data upload from NE to ZTE U31 system.
Configuration data gotten from managed NE can be kept in U31 system for backup.
3.13.2 Benefits
Configuration data in NE can be utilized in ZTE U31 system when U31 restore from
system fault.
3.13.3 Description
Configuration data upload is a process that data configured in NE uploaded to ZTE U31.
U31 gets the configuration data file from NE, saves it into appointed directory for backup
and displays it in U31 operation interface.
This feature can also launch configuration data upload of multi SDR in parallel. After
configuration data uploaded successfully, user can launch active-standby switchover of
configuration set for NE.
3.14 ZXO-07-02-015 Configuration Rack Map

(GERAN&UTRAN)
Feature change: N/A
3.14.1 Summary
Configuration rack map information is used to display shelf, rack &board running state of
whole system, it support adding, deleting and modifying attribute etc.
3.14.2 Benefits
It provides facilities for users to get to know configuration information in the configuration
rack map. Information like operation status related with configured boards is displayed in
the map.
3.14.3 Description
This feature supports fast creating rack map, configuration management can offer rack-
map module for various network scale. If you select NE in topology view, it can navigate
to rack map corresponding.
The board in the configuration management rack map cans real-display management
state, operation state, master-slave state of RNC/BSC CPU with small icons.
In addition, in the rack map of alarm management, the state of every board can
response its alarm information intuitively.
3.15 ZXO-07-02-016 Status Monitoring

Feature change: N/A
3.15.1 Summary
The status monitoring function helps the EMS manage the status data in the NE
database. When users operate and maintain the system or an NE, the system can
conveniently query and monitor the status data of the system equipment, so that users
can check and monitor the system resources such as circuits, signaling links, offices,
connections, and AAL2 paths in real time.
3.15.2 Benefits
It is convenient to inquire and monitor the resource status information when debugging
and maintaining NEs.
3.15.3 Description
Status Management provides the function of observing the status of various managed
object resources as a GUI interface. User can also obtain dynamic statistics of managed
object such as radio channel, signaling link, terrestrial circuit etc. User can perform the
operations such as block/unblock, activate/deactivate managed object.
GERAN:
Physical: BTS equipment management mainly includes Abis timeslot management and
Lapd status management.
Operations related with boards include observing BSC board system clock, BSC board
CPU occupation rate, BSC/BTS board status and EAM board status, switch BSC board
and reset BSC/BTS board.
Transmission: BSC status management includes management of A interface, NSVC, N7

signaling, Ater interface, reflection over A interface, IP GB, IP A, SGSN office direction
and Sigtran resource.
Wireless: wireless resource management includes management of cells, transceivers,

channels, modules, BVC and cell channels.
UTRAN:
The dynamic data management function includes numerous operations, such as

dynamic data query, dynamic data operation, dynamic data reporting, logical resource
reset (Iub/Iu/cell/AAL2 reset), and N7 blocking/unblocking.
Monitor settings are required for message processing such as status reporting so that
the system properly processes the received messages. When receiving a status report
message, the system identifies the status and updates the status information on the
corresponding object.
The dynamic data management procedure may be initiated from a specific object or
from the rack diagram.
Dynamic Data Management Initiated from a Specific Object:
• Signaling link: querying the status of SSCOP links and querying the status of layer
management links.
• No.7 signaling link: querying the status of MTP3 links, disabling/restarting the
specific MTP3 link, querying the service status of MTP3 links, observing/de-
observing the service status of MTP3 links, reporting the service status of MTP3
links, and blocking/unblocking MTP3 links.
• Signaling office: querying the status of a signaling office, observing/de-observing

the reach-ability status of a signaling office, and reporting the reach ability status of
a signaling office.
• AAL2 path: querying the path status of appointed AAL2,AAL2 blocking, and
unblocking
• AS configuration: querying the status of an AS.
• Connection: querying the status of SCTP connections and establishing/releasing

connections.
• IMA group: querying/observing/de-observing/reporting the status of IMA groups,

and enabling/disabling/restarting IMA groups.
• IMA link: querying the status of UNI links, querying/observing/de-

observing/reporting the status of IMA links, and enabling/disabling IMA links.
• PVC: querying/observing/de-observing/reporting the status of PVCs.
• Node B port: querying/observing/de-observing/reporting the status of Node B ports.
• CCP/NCP port: querying/observing/de-observing/reporting the status;
• Cell: querying/observing/de-observing/reporting the status of cells and resetting

cells.
• Channel: querying/observing/de-observing/reporting the status
• Node B: resetting the IUB interface.
• Others: resetting the IU interface, resetting the RNC, and synchronizing/ querying
NE clocks.
Dynamic Data Management Initiated from the Rack Map:
• Unit: status query, blocking, and unblocking.
• Sub-unit: status query, blocking, and unblocking.
• Board: normal reset, forced reset, normal active/standby switchover, forced

active/standby switchover, CPU load query, APS switching, APS status query, and
optical interface switchover.
• CPU: version querying, normal reset, forced reset, occupying coefficient query
3.16 ZXO-07-02-017 Centralized configuration

Management (GERAN&UTRAN)
Feature change: N/A
3.16.1 Summary
U31 system offers centralized monitoring interface for managed NE, users can view
operation& maintenance state of appointed NE, and setup the state. System also
supports query configuration information of standing wave ratio for single NE and multi
NE.
3.16.2 Benefits
The centralized data management function provides comprehensive operation methods
and a wizard-based configuration process to simplify the operation procedure and
enable centralized operations for the dynamic data and status management of resources.
Users can check, create, delete, and modify a batch of objects such as NE, PVC and
E1s through the centralized data management function.
The centralized configuration management function helps users better configure bulk
data with the U31 system:
1 Quick and convenient configuration
2 Quick initialization of physical configuration and radio resource configuration
3 Batch modification of configuration data
4 RNC/BSC centralized configuration
3.16.3 Description
RNC/BSC Centralized Configuration Management:
U31 support dynamic data (such as unit, sub-unit, and IMA group) managed objects
operated, user can query state of managed objects, and also integrated information
query of base station. User can query base station record by base station configuration
information, IMA link information and PVC mark.
Base Station Centralized Configuration Management:
• AISG device centralized management: Users can observe basic static parameter
and real-state of multi devices from one interface. And this function supports
operation in parallel.
• support bulk copy of similar NE;
• Cell centralized monitoring: U31 offers the interface for centralized monitoring of cell.
Users can observe basic static parameter and state of multi cells, and can launch
cell blocking or cell unblocking;
• Bulk upgrade online for managed NE: U31 supports multi configuration sets, and
offers to complete configuration data switchover between various versions when NE
version upgraded. Unified management of current compatible versions in system is
supported.
3.17 ZXO-07-02-018 Configuration Data Output/Input

Feature change: N/A
3.17.1 Summary
The ZTE U31 system supports configuration data import and export offline, so that users
can export configuration data to other systems so as to backup the configuration data of
a specific NE, or import the configuration data from another ZTE U31 system to the
current ZTE U31 system.
3.17.2 Benefits
This feature realizes configuration data output and input so as to reduce the O&M
workload of the network.
3.17.3 Description
Configuration Data Output:
Through the configuration data export function, users can export configuration data to
XLS files or XML format. ZTE U31 system supports scheduled task to export the
configuration data for use of third-party systems.
Configuration Data Input:
Users can also import wireless configuration data in XLS format to the ZTE U31 system.
The system will check the integrity and consistency of the imported file, verify the legality
of the parameters, and then automatically complete the configuration. It also support
configuration data import in bulk.
Configuration Data Template:
Parameters can be modified using XLS table for users. User can edit different
parameters for different NE. When all parameters modified, system shall generate
configuration data information for corresponding sites. Physical/transmission
configuration data template and wireless configuration data template are provided.
3.18 ZXO-07-02-019 Configuration Data Collection

(GERAN&UTRAN)
Feature change: N/A
3.18.1 Summary
The configuration collection function enables system administrators to output the
important configuration data in the form of reports. System administrators can obtain the
brief configuration information of NE nodes and output unified report data so as to better
monitor the NE node configuration through the EMS and to further locate faults or adjust
and optimize the system configuration.
3.18.2 Benefits
With the configuration report management function, users can more
conveniently obtain configuration data statistics and manage the configuration data
through ZTE U31 system, and can customize reports about certain configuration data.
The customized configuration reports can be exported when necessary.
3.18.3 Description
Users can complete the following tasks through configuration collection management:
• Specifying the NE whose data needs to be obtained.
• Obtaining NE data, such as network configuration data, physical configuration data,

radio resource configuration data and software version.
• Saving the data in CSV format to the local client, so as to understand the
configuration data of ZTE U31 system and further perform check, analysis and
decision-making based on the data.
• ZTE U31 supports export ground and radio parameter configuration report, which
can be restored to default and specified path as CSV. ZTE U31 can also export
Network Planning and Optimization report once to one or more CSV files.
3.19 ZXO-07-02-020 Hardware Inventory

Feature change: N/A
3.19.1 Summary
ZTE U31 system collects physical assets of NEs and stores them into physical assets
database. Real-time monitoring of physical assets of NEs can be traced.
The interface to acquire asset data is provided to upper layer system. On the inventory
view interface, the inventory type and resource could be added, deleted, modified,
queried, and refreshed. Inventory information can be input and output for backup.
3.19.2 Benefits
Automatically collecting inventory information helps get the real time information of asset
data of NE. Asset data can be managed and maintained by operators. The ex-factory
date and the latest maintenance date can guarantee the accuracy of data.
Automatic trace of asset data reduces human resources workload and mistakes caused
by manual input.
The interface to acquire asset data is provided to upper layer systems for whole network
assets monitoring and managing.
3.19.3 Description
Description of Asset Data：
The data comes from two sources: a) the data is automatically obtained from the NE; b)
if the asset data cannot be automatically obtained from the NE, users can manually input
asset information. The data obtained from the NE takes precedence. The user-input
data will be automatically overwritten by the data from the NE after the data from the NE
is updated.
Asset Data Can Be Obtained in the Following Modes:
• Automatically obtained from the NE.
• Batch import. For example, users can scan data with tools or import the data from
other systems to files and then import the asset data files to the system in CSV or
XML.
• Manual input. The data from the NE takes precedence. The user-input data (the
data obtained in the second and third modes are both regarded as user-input data)
will be automatically overwritten if the data from the NE is updated.
Description of Asset Data Management Interface:
An independent client view is used for asset management. The NE topology tree is used
for display during asset management. The left NE tree displays the nodes hierarchically,
and another node is added below a top node. To view asset information, select a tree
node. The system will list all the asset information about this node.
Asset Data Type:
According to 3GPP specifications, the management granularity of hardware assets

should be Field Replaceable Units (FRUs), such as racks, shelves, slots, boards, and
physical ports.
Currently, the management granularity of the asset management system can be as

follows according to the actual situation of mobile products:
• Integrated equipment information (designed according to the actual situation)
• Racks
• Power supply
• Fans
• Shelves (plug-in boxes and backplanes)
• Boards, including front boards, rear boards, and modules
Inventory Information View and Operations:
The asset data contain asset ID, asset identifier, asset category, equipment version and
equipment of IT data, etc. Asset data can be added/deleted/modified/enquired.
Inventory Information Input and Output:
Asset data can be imported and exported in XML and CSV format.
Northbound Interface Inventory Management:
Inventory management of NMS is supported in Northbound Interface Adapter Function

(NAF) for asset data management. Users can have access to asset information
database and create user-defined report of asset data.
4 Fault Management
The fault management module of the U31 system monitors the current use condition of
the devices in real time, providing device alarm information and solution to common
faults, convenient for the user to know the current use condition of the devices. The user
can avoid the device fault by analyzing the alarm information. Since there is a lot of
alarm information when the device fails, the U31 provides the function of alarm
information filtering and alarm relativity setting. There may only display the alarm
information about which the user is most concerned. In addition, the system provides
alarm knowledge database. For common alarm, the user can solve it by referring to the
help information in the alarm knowledge database. The alarm information and the
topology management of the U31 are combined together. It is convenient to see the
alarm of each NE device in the topology map. And the alarm condition and quantity can
be known according to the displaying color and prompt. The alarm information can
generate work dispatching card. The dispatching card system informs the device
maintenance staff to solve the fault, thus implementing fault solution automation. When
the fault is inexistent, the NE will send restore alarm to U31. U31 will clear this alarm in
the current alarm pool and put it into the history alarm pool. Users can use kinds of
alarm rules specialty to filter alarms, only show the alarm that we are concerned. The
user also can combine different alarm rules together to filter alarms.
4.1 ZXO-07-03-001 Alarm Monitoring

Feature change: N/A
4.1.1 Summary
ZTE U31 system collects alarm information from NEs and stores them into alarm
database after format conversion. Real-time monitoring of current alarms, history alarms
and notifications are supported. In addition, special monitoring of alarms and switching
to topology interface are offered. In Engineering mode alarms from NEs can be shielded
under the mode of site commissioning & debugging.
4.1.2 Benefits
Current alarms, history alarms and notifications can be monitored in real-time. It is easy
for users to know and trace the running status and recovery of the network in real-time.
Special monitoring of alarms makes it convenient for users to monitor the current alarms
that need special attention.
Multiple display methods like customized display, exporting and printing are supported
for users. It benefits users that displaying and dumping what they need in different ways
such as GUI, database, CD, DVD, Tape, printer, email, SMS and so on.
Switching to topology interface provides users viewing topology of the network

associated with alarms.
Engineering mode can avoid the situation that a large quantity of alarms are sent to U31
caused by debugging in the period of commissioning. Hence users feel more convenient
and resources are saved.
4.1.3 Description
When any failure of the network occurs, an alarm or a notification is generated and then
collected by ZTE U31. The alarm can be saved in the alarm database in specified format
(ITU X.733). Meanwhile the alarm can be displayed in an alarm list in alarm monitoring
interface. Alarm list can be classified by alarm level. Once a new alarm generated or
alarm recovered, the alarm list will be updated automatically.
The notification can be saved in the notification database. Meanwhile the notification can
be displayed in a notification list in notification monitoring interface. Notification list can
be classified by alarm level.
Real-time monitoring of current alarms:
The current alarm real-time monitoring function starts when fault management module
starts. An alarm occurred in the whole network will be sent and displayed in the real-time
monitoring interface. Alarm information can be acquired, such as location, happen time,
level, type, possible reason, and other detailed information.
Operations like counting, customized display, exporting and printing are supported.
Real-time monitoring of current alarm can be displayed in full screen.
For a current alarm, operations like acknowledging, negatively acknowledging, clearing,

forwarding, rules creating, specially monitoring, switching to topology interface and
alarm assigning can be performed.
Additionally, current alarm which requires special attention can place into one dialogue
box for special monitoring.
Real-time monitoring of history alarms:
The history alarms interface gives the situation of the alarms handled or recovered;
Alarm information can be acquired, such as location, happen time, level, type, possible
reason, and other detailed information.
Real-time monitoring of current alarm can be displayed in full screen. All history alarms
can be removed from monitoring interface.
For a history alarm, operations like acknowledging, negatively acknowledging, clearing,

forwarding, rules creating, specially monitoring, switching to topology interface and
alarm assigning can be performed.
Real-time monitoring of notifications:
The notification monitoring in real time allows displaying instant detection of the runtime
fault of the system. Notification information can be acquired, such as location, happen
time, level, type, possible reason, and other detailed information.
Real-time monitoring of current alarm can be displayed in full screen. All notification can
be removed from monitoring interface.

avoid the situation that a large quantity of alarms are sent to U31 caused by debugging
in the period of commissioning.
4.2 ZXO-07-03-002 Alarm and Notification Query

Feature change: N/A
4.2.1 Summary
Alarms and notifications query includes query of current alarms, history alarms and
notifications saved in database. Various query conditions are supported for users to
easily inquire the information they need.
4.2.2 Benefits
It is equipped with all advantages of real-time current alarms, history alarms, and
notifications monitoring.
Alarms and notifications that conform to certain conditions can be displayed in real-time.
4.2.3 Description
Users can set certain conditions to query current alarms and history alarms or
notification messages. The query results are displayed on the client GUI. Users can
manually refresh the query results as required. The system supports the saving of alarm
query conditions, so as to facilitate alarm query again in the future. The query results
can be exported as report files in XLS, TXT, HTM, PDF and CSV formats.
Users can set combined query conditions to query alarms. The system will query the
corresponding alarm information according to the set conditions (e.g. alarm code, alarm
level, the type of the system generating the alarm, the location where the alarm is
generated, alarm description, alarm cause, or alarm time). The query results are
displayed as a list in the alarm view.
Real-time query of current alarms:
Current alarms can be queried according to conditions such as system type, location,
alarm code, severity, alarm type, probable cause, happen time, acknowledgement status,
(un)acknowledgement operator, (un)acknowledging time, NE type, details, other
information, original ID, visibility. Real-time query of current alarms, different from other
queries, all current alarms information is refreshed automatically.
Real-time query of history alarms:
History alarms can be queried according to conditions such as system type, location,
alarm code, severity, alarm type, probable cause, happen time, acknowledgement status,
(un)acknowledgement operator, (un)acknowledging time, NE type, details, other
information, original ID, visibility. Besides, history alarms can also be queried by
conditions of recovery mode, user who clears this alarm and recovery time.
Real-time query of notifications:
Notifications can be queried according to conditions such as system type, location,

notification code, probable cause, happen time, NE type, details, other information,
original ID, visibility.
4.3 ZXO-07-03-003 Alarm Handle

Feature change: N/A
4.3.1 Summary
Operations related with alarm handling include alarm acknowledging and alarm negative
acknowledging, automatic alarm acknowledging rule, current alarm clearing, automatic
alarm clearing rule, alarm severity level re-definition, and operations on NE boards when
alarms on NE.
4.3.2 Benefits
Acknowledged alarms and unacknowledged alarms are distinguished with a flag for user
to obviously know alarm acknowledgement status.
Automatic acknowledging rule benefits for users auto-acknowledging massive alarms.

Usually these alarms cost users’ massive time and human resource.
Automatic clearing rule benefits for users auto-clearing massive alarms. Usually these
alarms cost users’ massive time and human resource.
Alarm severity level re-definition enables user focusing on key alarms in practical need.
NE operations can be directly performed on NE boards when alarms on NE.
4.3.3 Description
Alarm acknowledging and alarm negative acknowledging:
Current alarms and history alarms acknowledging indicates that the user has paid
attention to this alarm. When alarm acknowledging done, alarm status will convert from
“unacknowledged” to “acknowledged”. Alarm negative acknowledging is in a reverse
process. In the acknowledging and negative acknowledging operations, relevant
acknowledging and negative acknowledging information can be put into relevant space.
Automatic alarm acknowledging rule:
Automatic current alarms and history alarm acknowledging rule enables that the alarms
conforming to some conditions pre-defined to be acknowledged automatically when new
alarms or alarm recovery message are reported. Acknowledging status, acknowledging
time and acknowledging information of alarms can be set automatically by system. The
alarm automatic acknowledgement rule provides functions such as adding, deleting,
modifying, and viewing the automatic acknowledgement rule.
Current alarm clearing:
Current alarm clearing indicates that the user has known this current alarm and it should
be cleared. Alarms can be cleared from the current alarms interface and saved in history
alarm library for future query.
Automatic alarm clearing rule:
Automatic alarm clearing rule enables an alarm conforming to some certain conditions
pre-defined to be cleared automatically when an alarm is reported. Clearing information
of alarms can be set automatically by system. The auto-cleared alarm is stored into the
history library. Therefore, not only this alarm can be recorded, but the number of current
alarms is decreased. So users just focus on the key alarms. The alarm automatic
clearing rule provides functions such as adding, deleting, modifying, and viewing the
automatic clearing rule.
Alarm severity level re-definition:
The alarm severity level re-definition allows user re-defining the alarm severity level
according to practical need. In default, the alarm severity level corresponding to the
alarm code is set during system initialization. Users can change alarm severity level.
Primary severity level of alarms code can certainly be recovered. Query and modification
of the alarm severity level re-definition issue can be performed by users. Import and
export of alarm re-definition results can also be supported.
NE handling when alarms on NE:
Operations such as normal reset, mandatory reset, normal switch, mandatory switch,
and reset can be performed on BSC/RNC/BTS/Node B/SDR boards when alarms on NE.
4.4 ZXO-07-03-004 Alarm Correlation Rule

Feature change: N/A
4.4.1 Summary
Alarm correlation rules includes alarm merge rule, alarm timing rule, alarm counting rule,
alarm delay rule and alarm restriction rule. General operations of these rules are
described. Detailed descriptions of these rules are also concerned.
4.4.2 Benefits
Correlation rules concerned with alarms are used to reduce repetition displaying of
alarms via GUI or other terminals and to make it more convenient for user to find the
problems fast and accurately.
4.4.3 Description
The following general operations about these alarm rules are supported by ZTE network
management system: creating, modifying, activating, pausing, deleting, updating, etc.
All alarm correlation rules support the correlation according to conditions such as the
alarm system type, alarm occurrence location, alarm description information, alarm
reason information, alarm time, alarm level, alarm type, and alarm status.
Alarm merge rule:
The same alarms within some certain MO can be merged by system based on alarm
merge rule. After alarm merge rule takes effect, only one alarm will be displayed on GUI
or other terminals.
Alarm timing rule:
When the activity duration of current alarm exceeds the period specified by alarm timing
rule, the alarm level will be enhanced or a new alarm will be generated. On the rule
setting interface, enhancing alarm level can be set by user and generating a new alarm
includes alarm level and detailed information.
Alarm counting rule:
If the number of the same alarms exceeds the threshold set by user, a new alarm will be
generated and reported. On the rule setting interface, generating a new alarm includes
alarm level and detailed information.
Alarm delay rule:
It is not necessary to display the alarm which is able to recover within the specified delay
period set by user on client. If not, they will be reported. On the rule setting interface, the
delay time can be set and certain conditions can be chosen as the rule effect scope.
Alarm restriction rule:
When a lot of alarms are generated simultaneously, usually there are major alarm and
minor alarms. When alarm restriction rule take effect, only the major alarm will be sent to
user side, with the minor alarms left on NE side. However, the minor alarms can be sent
after the major alarm recovers if required.
4.5 ZXO-07-03-005 Alarm Filter Rule

Feature change: N/A
4.5.1 Summary
Alarm filter rules includes alarm shield rule, alarm warehousing rule, alarm global filter
rule, alarm users filter rule. General operations of these rules are described. Detailed
descriptions of these rules are also concerned.
4.5.2 Benefits
Rules concerned with alarms are used to reduce repetition displaying of alarms via GUI
or other terminals and to make it more convenient for user to find the problems fast and
accurately.
This feature makes users focus on the alarms they concerned, improving efficiency and
locating faults easily.
4.5.3 Description
The following general operations about these alarm rules are supported by ZTE network
management system: creating, modifying, activating, pausing, deleting, updating, etc.
All alarm filtering rules support the filtering according to conditions such as the alarm
system type, alarm occurrence location, alarm description information, alarm reason
information, alarm time, alarm level, alarm type, and alarm status.
Alarm shield rule:
The alarm shield rule means customizing alarms that the system needs not to collect.
The qualified alarms are just kept in equipment, and not sent to U31 system.
Alarm warehousing rule:
The alarm warehousing filtering rule means customizing alarms that the system needs
not to pay attention to. After the server receives alarms meeting the condition, discard it
directly. That is, the alarm is not saved in the database or memory, and is not sent to the
Client for display. Through the alarm warehousing filtering setting interface, user can
query, add, modify, and delete the alarm warehousing filtering rule.
Alarm global filter rule:
The alarm global filtering rule means screening alarms when the NM server performs the
alarm pre-processing. The selected alarm will not be sent to the Client, but is stored in
the database for the analysis and query in the future.
Alarm users filter rule:
The alarm user filtering rule is functional for a specific login user. It is not functional for
the client with using other login users. After the specific client receives alarms from the
server, screen alarms by using the filtering condition of this login user. The selected
alarm is discarded by the client and is not displayed in the alarm list. It is not counted.
4.6 ZXO-07-03-006 Current Alarm Forwarding

Feature change: N/A
4.6.1 Summary
Current alarm forwarding indicates that important alarms complying to certain conditions
to the appointed users by e-mail or short message automatically or manually.
Manually current alarm forwarding and automatic current alarm forwarding by setting
automatic forwarding rule and templates are supported by system.
4.6.2 Benefits
Important alarms can be reported to related users by email or short message (SMS) for
the convenience of users to locate faults rapidly.
Automatic current alarm forwarding benefits for appointed users anytime, even though
users are not in equipments room or central control room.
4.6.3 Description
Current alarm forwarding prerequisite:
For email forwarding, the system is connected to SMTP Server in normal running status.
For SMS forwarding, the system is connected to SMS module in normal running status.
Current alarm forwarding type:
Current alarm forwarding type includes manually current alarm forwarding and automatic
current alarm forwarding by setting automatic forwarding rule and templates.
Automatic current alarm forwarding operation interface:
An engineer or multi-engineers can be selected firstly. Then forwarding type, SMS or

email, is chosen. Next step is alarm conditions selecting combined by alarm generation
location, description, cause, time, level, type and status. Automatic forwarding interface
to view, add, modify and delete are supported.
4.7 ZXO-07-03-007 Alarm Synchronization

Feature change: N/A
4.7.1 Summary
Alarm synchronization includes manual alarm synchronization and automatic alarm
synchronization. This feature ensures integrity and consistency of alarms data in U31
system with NEs’ alarm data.
4.7.2 Benefits
Manual alarm synchronization and automatic alarm synchronization can keep integrity
and consistency of alarms data in alarm view interface.
In connection failure mode, automatic alarm synchronization is triggered once certain

failures occur.
Scheduled alarm synchronization task is supported for users to avoid frequent alarm
synchronization because of transient interruption. In scheduled alarm synchronization
task, timing duration can be customized by XML file based on estimate of period of
transient interruption.
4.7.3 Description
Manual alarm synchronization:
In case of connection failure between NE and the U31 system, newly generated alarms
of NE will not be reported to U31 system.
To keep integrity and consistency of alarms data in alarm view interface, manual alarm
synchronization in appointed location is supported.
Automatic alarm synchronization:
Automatic alarm synchronization works under two modes, connection failure mode or
scheduled synchronization mode.
Automatic alarm synchronization is triggered once OMM firstly accesses to U31 system,
OMM reconnects U31 system after OMM disconnection, NE switches over, NE restarts
or U31 system restarts.
However, transient interruption should be considered. To avoid frequent alarm

synchronization because of transient interruption, scheduled alarm synchronization task
is supported. Timing duration can be set by XML file based on estimate of period of
transient interruption.
4.8 ZXO-07-03-008 Alarm Knowledge Database

Feature change: N/A
4.8.1 Summary
Knowledge database provides alarm handling experience database for users. Users can
add their own experience and knowledge of alarm handling into the database which can
also be recorded, queried by other users.
4.8.2 Benefits
Users can record their alarm handling experience into knowledge database, to enhance
the maintenance ability of all users. Good and mature alarm handling experience can be
co-shared between users. After the long-time operation, alarm knowledge database can
be a reference for the similar problem in the future.
4.8.3 Description
For each alarm, system provides with default suggestions. Users can organize their own
suggestions or corresponding information into a record of the knowledge base, such as
alarm type, time, code, reason, description, processing advice and so on. Users can
also delete and modify the experience in the knowledge base.
Alarm handle suggestion can be imported or exported in such formats as XLS, PDF,
HTML, or TXT.
4.9 ZXO-07-03-009 Visual Alarm

Feature change: N/A
4.9.1 Summary
Visual alarm provides a fast and convenient measure to supervise the network alarm
status through a high-level user interface, displaying current network alarm status in the
form of alarm lists. It is refreshed automatically by the system whenever there is a new
alarm or alarm recovery.
Each alarm can be viewed via monitoring alarms interface. It also can be located to the
board.
4.9.2 Benefits
Many kinds of alarm view ways are supplied by U31 system to users. It helps
supervising the network alarms status quickly and conveniently.
It provides real-time monitoring of overall network alarm status depending on the

different colors of NE, obviously.
The current alarms of the specified rack, shelf and boards can be expanded on the rack
diagram.
Man-machine commands of the active/standby switchover and restart in the rack

diagram are supported. Diagnosis and test of the specified device is supported.
4.9.3 Description
Topology graph view:
At the high-level user interface, the overall network structure is displayed in the mode of
Tree View or Geographic View, in which different color represents different level of alarm.
The legend standing for a NE is painted with the color corresponding to the most serious
alarm under this NE, and the amount of alarms at each level under this NE is shown with
ID. When new alarm information or alarm recovery messages related to this NE arrive,
the system automatically makes a judgment that whether to re-fresh the color of the new
NE legend. In this way, the convenient and direct real-time monitoring of overall network
alarm status is realized.
Monitoring interface view:
User can find the probable reasons, location, and other information of one alarm in the
monitoring interface of current alarms and history alarms.
Alarm location to rack-shelf-board graph view:
With the alarm location function, user can query the real-time alarms in the rack-shelf-
board graph by clicking the popup menu item on one board with some alarms. The color
of the board shows the highest level color of these alarms.
4.10 ZXO-07-03-010 Coloured and Audible Alarm

Feature change: N/A
4.10.1 Summary
Coloured and Audible Alarm shows alarm status of the whole network by the
corresponding GUI alarms interface color and sound on U31 client. The color and sound
of each alarm level can be customized by users.
4.10.2 Benefits
Coloured and audible alarm can make users easily get to know alarm status. Alarm
colour and sound can be changed by users according to practice.
4.10.3 Description
One or more new alarms announced by graphic panels with audible signal (especially for
critical and major alarms).
The quantity of alarms for each severity is shown in corresponding graphic panel.
A color palette is provided for color selection. After the alarm color is modified, it will take
effect in real time.
The system supports two audio modes, that is, continuous audio and short audio. A trial
hearing is allowed when the alarm audio is customized.
4.11 ZXO-07-03-011 Alarm Box Management

Feature change: N/A
4.11.1 Summary
Alarm box management, an important telecom device, indicates equipment faults
promptly, accurately and intuitionally for O&M engineer’s convenience to locate and
solve faults in time.
The alarm box setting includes functions such as creating, modifying, querying, and
setting control parameters of the alarm box, and enabling/disabling the alarm box.
4.11.2 Benefits
Continuous monitoring of alarms in equipment room is supported.
Key alarms (critical and major) filtered according to severity and managed object make
users focus on major issue.
Sound and color of alarm displayed on alarm box are for users to hear and see directly.
4.11.3 Description
Alarm box is commonly placed in equipment room, and connected to U31 system via IP
protocol. Alarm box displaying rules and control contents can be set through U31 system.
And qualified alarms will be sent to alarm box according to alarm system type, alarm
location, etc., and then alarm indication displayed on alarm box. Contents set by users
can be alarm box name, alarm box description, initial status, IP address, port number,
LCD displaying level, sound level. Displaying rule of alarm box can also be modified,
viewed, refreshed, paused, enabled, disenabled, and deleted.
4.12 ZXO-07-03-012 External Alarm Access

Feature change: N/A
4.12.1 Summary
Implementation and display of external alarm such as dry contact configuration refer to
configure the port accessed by external dry contact alarm signal and normal circuit,
therefore to customize special alarms in terms of base station types.
4.12.2 Benefits
Due to the different user demands for external alarms, various alarm signal source and
level can be tailored and saved into templates to manage the accessed alarm
information.
4.12.3 Description
This function provides collecting and displaying external alarm, dry contact alarm signals
for external equipments according to its base station and rack in network management
system. Dry contact is passive signal, if normal circuit is open, and then alarm will be
generated when circuit is short; if normal circuit is short, alarm will be generated when
circuit is open. To definite the dry contact template, dry contact alarm, alarm level, alarm
content, alarm type and break-make mode can be set for sites.
4.13 ZXO-07-03-013 Diagnosis and Testing

Feature change: N/A
4.13.1 Summary
Diagnosis and testing provides the test for the specified physical devices to verify the
communication status of the system to ensure the normal and stable running of the
system. It can also facilitate locating the fault in time.
Diagnosis test provides the test of NE object to get more detailed information for the
convenience to locate the fault for users.
4.13.2 Benefits
Upon detection of any fault, if the information of the reported alarm is not enough for
locating the fault source, this test can be used to locate the fault.
In the normal running of the NE, diagnosis test is used to find any fault in time.
When the fault source is handled or replaced, the test can be used to make sure that the
fault is cleared before service restoration.
The results of both instant test and routine test are saved in the database. The query to
the test results by test type, test time and device are supported. The queried test results
are displayed in list. The statistics, deletion, printing and report customization of the test
results are supported.
4.13.3 Description
The diagnosis test can be divided into instant test and routine test. The diagnosis test
comprises the tests to the physical device and communication links. The instant test
provides real-time diagnosis test, and returns the test result to the user immediately. At
the same time, the test result is saved into the database for query in the future.
In the routine test, the user selects the test object and test item as required, and presets
the test time. The test result will be saved into the database for future reference. In daily
maintenance, routine diagnostic tests are conducted to test the physical equipment and
communication links. If the test result shows that the physical equipment and
communication links are almost abnormal, engineers should take care and take proper
measures to prevent possible faults. When a fault occurs, the instant test can help
engineers to find the causes quickly, locate the fault accurately, and remove the fault as
soon as possible. After the fault is removed, the routine test can also help the engineers
to verify whether the equipment has resumed to the normal status and the whole system
is running normally.
Diagnosis test is mainly used for finding the current working condition and finding the
faults and it can be used to test the NE after the fault recovery to check the stability of
the NE. Moreover, if a fault is found during the routine test, a further test can be
performed through instant test. After the instant test, the results are saved and displayed.
Instant test is the test performed immediately; routine test is to daily supervision of the
link. Users are allowed to set the test items, interval and test time of the routine test.
Once the conditions are satisfied, the test process will start test tasks. Users can also
suspend, restart or delete the scheduled test according to requirements.
User can query the result of the test to get link or unit information and to analyze the
fault.
4.14 ZXO-07-03-014 VIP Site Alarm Monitoring

(GERAN&UTRAN)
Feature change: N/A
4.14.1 Summary
Query, real-time monitoring and statistics of the sites alarms that require attention are
supported by system.
4.14.2 Benefits
Users can perform statistics of site alarms which they pay close attention to.
4.14.3 Description
Statistics of site alarms paid close attention to:
Statistics of site alarms paid close attention to is supported by U31. VIP sites can be
queried via MML. In alarms view, query, real-time monitoring and statistics of the sites
alarms that require attention can be made. Alarms that need attention refer to VIP sites,
B-level sites and C-level sites. VIP sites are most important for users, B-level sites less
important, C-level sites even less important. For those sites that are set to require
attention, users can inquire and make a statistics of the alarm level and alarm quantity
within the six time periods: within 1 hour; 1~2 hours; 2~3 hours; 3~4 hours; 4~5 hours; 5
hours; and detailed alarm list can be shown in the statistics result.
5 Performance Management
5.1 ZXO-07-04-001 Measurement Task Management

Feature change: N/A
5.1.1 Summary
Measurement task management manages NE or U31 system performance data.
Creating, deleting, and querying and modifying of performance measurement tasks are
also supported.
5.1.2 Benefits
NEs performance data can be organized according to performance measurement tasks
set by users.
Key performance index (KPI) can be picked up by users to create measurement task as
per their own requirements.
5.1.3 Description
Performance measurement task can provide that required data from corresponding NEs
can be tailored. It also supports 15 minutes granularity collection of primary data, daily
granularity and weekly granularity collection of data.
Creation, deletion, query, modification, activation and suspension, overdue deletion, of

current measurement task query and deletion of history measurement tasks,
synchronization of measurement tasks etc. NE reports collected data to U31 system in
terms of measurement task.
Measurement task of U31 system includes current measurement task, history

measurement task, and primary measurement task.
Current measurement task:
After current measurement task created, U31 system automatically collects specified
performance parameters according to the collection granularity set by users. After
current task deleted, it automatically becomes history measurement task.
History measurement task:
After current task deleted, it automatically becomes history measurement task. When
end time of current task is coming, system will automatically delete current measurement
task. And the measurement task will turn to be history measurement task automatically.
Primary measurement task:
The primary task in system is a basic measurement task. It is running in NEs. It is

activated when NEs turned on, while deactivated when NEs turned off. Users can not
create and delete it. Basic measurement task can be classified by measurement objects;
it also can be defined in terms of KPI requirements from users.
5.2 ZXO-07-04-002 KPI Management

Feature change: N/A
5.2.1 Summary
KPI Management refers to mathematical and logical operation in editor formula, handle
operations, correlated KPI, curve diagram for KPI display, three main application
scenarios of KPI management.
5.2.2 Benefits
Intuition statistics is easy to monitor network quality and analyze performance data to
instruct network planning and optimizing.
Mathematical and logical operation in editor formula is supported for users to combine
dynamic KPI what they want.
QoS is supported by KPI to alarm users that network performance is not so good.
Curve diagram can be used for users to see performance index obviously.
5.2.3 Description
Key performance index (KPI) is statistics value combined by counters using certain
formula; it reflects network quality and operation status.
Mathematical and logical operation in editor formula:
ZTE U31 system provides default performance index, while users can define its own
performance index according to their own needs. The editor formula supports various
mathematical operations such as +, -, *, /. Various logical operations such as >, >=, <,
<=, =, <>, AND, OR are also supported.
Handle operations:
System supports creating, deleting, modifying and querying customized index. But for
system preset (default) indices, users can only query it, no deletion and modification is
allowed. Both customized and preset indices support import and export.
Correlated KPI are supported:
System can display correlated KPI by layer tree, which is a layer-by-layer analyzing
course. System classified KPI on actual demands; primary index indicates the current
running status, such as wireless access success rate, call drop rate, congestion rate,
handover success rate, traffic flow, error block rate, etc. When selecting certain primary
index, users can open its subordinate index, up to 6 layers are supported.
Curve diagram for KPI display:
System also can display index by curve diagram. In curve diagram whose index varying
with time of RNC/BSC data analysis and cell data analysis, different index are displayed
by different colors or icons; users may compare different index or different objects of
same index in this curve diagram.
Three main application scenarios of KPI management:
Creating QoS task based on default KPI, when the index value exceeds threshold set by
the user, QoS alarm is generated to notify the user;
Querying KPI index value and sending to clients after calculation by KPI formula. History
query calculates values after inquiring corresponding counters from database and show
results to Client; it reflects the indices’ changes in the past periods.
Generate report forms in terms of templates offered by index formula. Users adopt it to
make statistics of index changes during busy hours to indicate network running status.
5.3 ZXO-07-04-003 QoS Monitoring

Feature change: N/A
5.3.1 Summary
QoS task is supported by U31 system as a measurement task. Creation, deletion,
modification, query, suspension/activation, completion and overdue automatic deletion
of QoS task are supported.
QoS alarm is supplied for users’ real-time monitoring whole network quality.
U31 system supports QoS task data exported and printed.
5.3.2 Benefits
Quality of network services based on KPI supports users focus on what they really care
about and real-time monitoring of network quality.
And it also can generate QoS alarm to inform users KPI exceeds threshold what they
have defined.
QoS task data exported and printed is also supported for post-comparison and post-
analyzing.
5.3.3 Description
QoS task and QoS alarm:
QoS monitoring can be realized by QoS task. It can monitor measurement data during
preset time length. When certain index exceeds or lowers than preset threshold, alarm is
generated.
QoS task can be regarded as a common measurement task. Data collection is

completed measurement task of corresponding NE. Data collected by QoS task is not
input into performance database. It is only used to calculate QoS index and triggers
performance alarm according to threshold and calculated index.
QoS task handling:
Creating, deleting, querying, modifying, activating /suspending of QoS tasks are also
supported via XML file.
QoS task data exported:
Data which is monitored by QoS task can be exported as XLS file and be printed.
QoS task notification when a measurement object is deleted:
If a QoS task has a measurement object (which is obtained from the configuration
module), but this measurement object has been deleted by the configuration module,
then the QoS task can monitor and automatically identify it to indicate that the
measurement object of this task has been deleted.
5.4 ZXO-07-04-004 Performance Data Management

Feature change: N/A
5.4.1 Summary
Performance data management supports collecting history data in database. Users can
obtain performance data based on primary granularity according to query conditions and
appoint certain approach for data collection and statistics. Users also can calculate
these primary granularity performance data.
Integrity check of performance data is supported, and automatic and manual recollection
ways to re-collect missed data are also supported.
5.4.2 Benefits
Performance data is crucial for O&M engineers and network optimization engineers to
analyze and locate system fault to optimize network performance.
This feature displays performance statistics information by diagram to effectively help

user analyze system performance.
Integrity check of performance data provides users accurate and reliable data which
they care about.
5.4.3 Description
U31 system can monitor and check performance data real-time, and the data can be
exported to XLS file, supporting print function in addition. It displays performance index
and counter that user defined as table mode.
U31 system supports query by selected condition by NE type, object type, query
granularity, query pattern and collect pattern etc. During which the query granularity can
set as original 15 minutes, hour, day, week and month, user also can define all time
summary, all date summary.
Certain column can be ordering when query data successfully, U31 system can render
performance data query results for users viewing.
U31 system supports query statistics patterns as bellows:
• Performance data query composition:
• U31 supports Performance data query composition by index/counter. System also

supports “TopN” (top max/top minimum) operation and “query by object” and set top
filter for one counter/index, system supports dynamic busy hour filter, that is system
discover cell busy hour automatically, responding cell network status to users.
• U31 system supports index/counter render, user can query and grouped query
performance data by start/close time, time slot and query object filtering.
• System supports define cell group and site group manually, and query performance
data by group.
• Performance history data grouped query
• Users can group performance data by time, and set time granularity as
15minutes/hour/day/week and month
• Measurement task query
• Timing task query
• Templet query
Query of history performance data:
Users can set data query range to inquire history performance data. Following items are
available for users query setting: counter (index) list, query object (including stratification
wildcard), query time period (date, week, month, customized), query time duration,
granularity group. Meanwhile history data performance statistics also supports other
direct statistics, such as: query by measurement task, by template, timing task etc.
Graphical monitoring of performance data:
System supports refresh collection results of performance data from database on

graphical monitoring interface for users real-time monitoring KPI and counters. Users
can use this to follow the trends of KPI change for network optimization.
Conditions can be set via monitoring interface, such as KPI, counters, location,
granularity, start time and end time. Collection results of performance data can be
refreshed on the monitoring interface. System offers bar chart, line chart and pie chart.
Performance data export:
Users can export selected performance data in different file format. Excel, CSV, HTML,
TXT and PNG format are supported.
Performance data backup and recovery:
Both manual and automatic backup of performance data are supported.
Primary backup granularity of data is 30 days, hour granularity data 90 days and day
granularity data 180 days in default. Performance backup data file can be recovered to
database.
Integrity check of performance data:
Automatic check of performance data integrity is supported when it is imported to

database, and corresponding data records integrity will be labeled. Performance data
integrity includes:
Whether some counters’ data is missing; for summary data record of several time
granularities, it needs to check whether there is some data is missing.
Performance data recollection:
Automatic and manual recollection ways to re-collect missed data are supported.
5.5 ZXO-07-04-005 Performance Report

Feature change: N/A
5.5.1 Summary
U31 supports to export all performance data as report in a unified format, helping
conveniently monitor NE running.
5.5.2 Benefits
This feature provides flexible and convenient report template management and report
export and supports timing report generating and e-report management.
5.5.3 Description
This feature has following functions:
Performance data query:
Different operators have different requirements of network report According to these

different report and KPI requirements, this feature provides a comprehensive report
services. System automatically or manually generates report at appointed time duration,
such as: daily report, weekly report, monthly report, busy hour report and TopN report.
For TopN report, TopN of time and object are supported. Time TopN inquires max
unique record each hour; object TopN inquires max unique record of each object in
certain query time period.
Configuration attribute can be displayed in report. Performance report may contain

configuration attribute operator concerns to generate joint report of performance and
configuration.
Graphical colored report:
Users can customize color palette for counters and indices. Data in different ranges is
shows by different colors.
Data query template management:
Users can easily put queries in the same mode by setting query template. NE types,
counter and index can be set for this template. Predefined template and user-defined
template can be imported and exported among different system. Creation, modification
and deletion of templates is allowed.
Report task management:
System supports timing query task, which generates appointed report automatically.
This task mainly accomplish file’s timing generation, file’s format setting is unavailable.
Following functions are supported: task creation, modification, view, deletion, activation,
suspension, completion; parameters setting includes: NE type, template, measurement
objects, collecting time duration, collecting granularity, task start and end time, task
running period, etc. One set of template is available for one task. According to users’
setting, system automatically runs report task to generate report in appointed directory
regularly. In addition, users can also select one report task to make one-time query and
generate report. XLS, XML, TXT format files are supported.
5.6 ZXO-07-04-006 Performance Data Real-time Query

Feature change: N/A
5.6.1 Summary
This feature provides performance data real-time query from NE, and displays the query
results via table or graph.
5.6.2 Benefits
Users can fast query current performance status of the network to response and deal
with the problems because of decrease of network quality.
5.6.3 Description
Performance data real-time query supports query based on conditions such as NE type,
object type, query granularity or location. The query granularity can be defined by users.
It supports minute-level and second-level query granularity. It is supported that whether
or not to customization for query object. The query results can be saved automatically.
6 Software Management
6.1 ZXO-07-05-001 Software Management

Feature change: N/A
6.1.1 Summary
Software management provides users with an efficient and smooth way to download and
upgrade NE version. Therefore, it will be easy to download software from U31 for newly-
added equipment, and users can operate and control the whole period of software
downloading, including software version warehousing, downloading, activating,
switching, deleting, roll-backing, and querying etc. Continuous feedback is provided to
the user (such as percent-done progress indicators) for operations.
6.1.2 Benefits
Unified and integrative software management for different NEs in network is supported.
It’s convenient to download and activate software version in single or bulk way during
fast commissioning.
Percent-done progress indicator of every operation helps users to get process status
more intuitively.
User can recover to the previous environment without any risk with software rollback to
the previous version.
6.1.3 Description
Software version supports following NEs:
BSC/BTS, RNC/Node B and SDR are supported.
Software downloading in bulk:
Besides version downloading for a single NE is supported (such as RNC version

downloading), system also supports version downloading in bulk for the same type NE
(such as downloading for multi-Node B simultaneously).
Software maintenance release and patch:
To reduce operation complexity, software maintenance release and patch are supported.
Software maintenance release package contains all kinds of software version
information. User only need to execute software downloading once, all version
information are included. When patch is needed, all patches can be put into one patch
package to be released. Patch package downloading operation is the same as software
maintenance release package. One software package can include several patch
packages, there is no need to cover previous released patch in later one.
System supports following software handle operations:
1. There are two kinds of version warehousing, single and batch. Software warehousing
refers to importing software version documents into ZTE U31 system.
2. Version downloading refers to downloading software versions to NE.
3. Version activating refers to activating software versions in NE.
4. Version switching, including single and batch switching, refers to switching certain
version which is running in NE to another version.
5. Version deleting includes deleting versions from NE and ZTE U31.
6. Version querying refers to query version information in terms of appointed board type.
7. Version backing-up and recovering refer to backup version to appointed directory, and
recovering it according to backup information.
8. Version synchronizing refers to synchronizing NE version to ZTE U31.
9. Version consistency comparison refers to comparing version consistency between

ZTE U31 and NE, and providing “Synchronize to NE” and “Delete from NE” operations in
comparison results.
10. Patch can be got automatically from ZTE U31 system with which the current version
is compared.
11. Rollback of the current version can be done in case that there are some reasons for
the new version problems.
6.2 ZXO-07-05-002 Nodes SW Version Check

Feature change: N/A
6.2.1 Summary
Nodes SW version check function checks whether version running in foreground is the
same as activated version in background and generates report according to comparison
results.
6.2.2 Benefits
It’s easy to find possible problems related with software versions in running system,
supporting trouble shooting and locating.
6.2.3 Description
Nodes SW version check is executed to get boards’ version information of
BSC/RNC/Node B/BTS and appointed BTS/Node Bs (major and standby boards
included). After consistency comparison, result is displayed on client terminal via GUI,
which can be exported as XLS file for the reference of O&M engineers.
6.3 ZXO-07-05-003 Software Installation and Upgrade

Feature change: N/A
6.3.1 Summary
Software installation and upgrade describes the installation and upgrade of ZTE U31
server and client.
GUI is supported for users to install and upgrade software of system.
ZTE U31 client can check the compatibility and get the proper version from server
automatically.
6.3.2 Benefits
It is easy to monitor installing and upgrading of software via GUI software management
interface for users.
It is easy to install and upgrade ZTE U31 for users.
6.3.3 Description
ZTE U31 provides a whole integrated setup package via GUI for the user to install the
ZTE U31 database, ZTE U31 client, ZTE U31 server.
User can upgrade ZTE U31 client or server or database from a certain old version to a
new version by executing the scripts that exist in the certain directory of the setup
package.
6.4 ZXO-07-05-004 Software Inventory

Feature change: N/A
6.4.1 Summary
ZTE U31 system shows software of NEs and stores them into software database. Real-
time monitoring of software of NEs can be traced.
On the inventory view interface, software inventory can be viewed and exported.
6.4.2 Benefits
Software inventory information management interface helps get the real time information
of software asset data of NE. Software asset data can be managed and maintained by
operators.
6.4.3 Description
Software management provides view and export functions for all NE software
information list.
Consistency check of client and server is supported. At the same time, running version
information also can be viewed.
7 System Management
7.1 ZXO-07-06-001 Data Backup and Restore

Feature change: N/A
7.1.1 Summary
Data backup mechanism is supported manually or automatically saved to the backup
server periodically to backup and restore files if necessary.
Backup mechanism in two ways is supported: online and offline.
7.1.2 Benefits
Prevent the data from being lost due to accident, improving system reliability.
Backup scheduled plan is supported for users to ensure data safety.
Data can be backed up without ZTE U31 server shutting down.
7.1.3 Description
This feature supports user customized scheduling of automatic backup and ensures
database space availability. User can create/delete/modify a scheduled plan to realize
the backup and restore by some demands on the system view.
Considering the disaster recovery function of the system, to prevent the data from being
lost due to accident, the U31 system provides data backup mechanism. The data can be
manually or automatically saved to the backup server periodically. The backup function
can backup all the data in the switching office, or select to backup some of the data in
the switching office.
Besides the disaster recovery, the backup mechanism can be combined with the
recovery backup to completely copy the data of some offices into a new switching office.
The Information can be backed up online as follows:
1 ZTE U31 server configuration files.
2 NE configuration data in ZTE U31 server.
3 Performance data (increment auto periodically, or certain time period manually).
4 History alarms (increment auto periodically, or certain time period manually).
5 Diagnose results.
Performance Data Dump Function:
This function is also used in the deployment and maintenance of the switching office.
Performance data dump function ensures the data size in database. Basic Database
Table can be saved three months at most, and Report Database Table can be saved
one year at most, and user can set whether to dump details. Common Measurement
Task Database Table Timer can be saved three month at most
7.2 ZXO-07-06-002 System Self-Monitoring

Feature change: N/A
7.2.1 Summary
System Self-Monitoring module monitors the status of U31 system in real time.
Support automatic managing job. It will generate the alarms depending on the threshold
values.
7.2.2 Benefits
This feature helps users get to know the status such as occupation of CPU, RAM, and
hard disk in effective and efficient maintenance of U31 system.
7.2.3 Description
System Self-Monitoring module includes two sub-modules:
GUI interface, used to check current status and monitoring jobs defining tool.
Supervision function: Performance supervision and catalogue supervision.
Performance supervision is to supervise the occupation of CPU, RAM, and hard disk.
While reaching the threshold, alarm is generated.
Catalogue supervision is to supervise the catalogue which stores performance,

configuration alarm files. When reaching the threshold, the clearance is done by setting
rules.
7.3 ZXO-07-06-003 Link Monitor

Feature change: N/A
7.3.1 Summary
Link monitor function provides monitoring the connections established between ZTE U31
server and NEs, and also disconnecting them. Heartbeat detection mechanism is
adopted between U31 and NEs.
7.3.2 Benefits
It helps the user monitor the connection status between ZTE U31 server and NEs.
7.3.3 Description
Disconnection information on the status bar on client side can be viewed when
disconnected between NEs and ZTE U31 server.
Heartbeat detection mechanism is adopted between ZTE U31 server and NEs. When
links disconnected, report is to be generated to ZTE U31 server.
7.4 ZXO-07-06-004 Time Management

Feature change: N/A
7.4.1 Summary
System uses NTP network time protocol to synchronize all NEs clock to the same time.
DST (daylight saving time) and multi-time zone are supported. System can switch
between DST and multi-time zone.
7.4.2 Benefits
The system can synchronize all network elements’ clock to be the same time
automatically. The clock of NE devices localization is realized, easy for maintenance.
7.4.3 Description
Clock synchronization:
In the whole network, ZTE U31 server and NEs are using the same time source server
(GPS). Network Time Protocol (NTP) is employed. All synchronization methods comply
with RFC 2030.
Configuration files are offered in ZTE U31 to configure time source server IP address
and port. In common cases, time source server is deployed by side of ZTE U31. When
activating server, it will automatically synchronize time as time source server, ZTE U31
server operation time is updated at the same time. When NE connected to ZTE U31
server, time information is synchronized to NE by ZTE U31 server. Meanwhile system
supports timing synchronization; its interval can be set.
DST and Multi-time zone:
ZTE U31 server supports Daylight Saving Time (DST) of NE management and system
time zone management. A star time synchronization network is established among ZTE
U31 server and NEs. When activating ZTE U31 server, to turn on clock synchronization
at the same time to access to the clock synchronization network. System can switch
between DST or multi-time zone, ensuring system’s correct display and operation when
the network is in multi-time zone.
7.5 ZXO-07-06-005 License Management

Feature change: N/A
7.5.1 Summary
License management controls license of system capacity and function.
7.5.2 Benefits
It’s convenient for users to purchase License on actual demand.
And users also can purchase some Features to save investment.
7.5.3 Description
This feature controls system capacity and license, providing display, update license
documents and set license alarm. Feature control and capacity adjustment can be
achieved by license document.
ZTE U31 server supports license expiration alarm. When license is about to expire,
alarm is generated to inform users. Then users may update license, or register new
license to ensure normal operation.
License can keep when base station controller or base station modified in a domain of
certain scale, and licenses for modified node don’t need to be updated.
8 Security Management
8.1 ZXO-07-07-001 Node Hardening

Feature change: N/A
8.1.1 Summary
Node hardening includes a number of recommendations and scripts in order to protect
network nodes from accidental and malicious operations.
8.1.2 Benefits
Node hardening protects ZTE U31 server from being subject to internal and external
malicious attacks.
8.1.3 Description
Recommendations and scripts are provided to harden nodes like ZTE U31 server.
Detailed specifications are available and cover:
• Solaris & Linux
• Windows 2003
• Oracle
8.2 ZXO-07-07-002 Network Secure Infrastructure

Feature change: N/A
8.2.1 Summary
Recommendations are provided to set up network secure infrastructure for O&M network
correctly.
8.2.2 Benefits
Network secure infrastructure protects the data in the O&M network from being subject
to internal and external malicious attacks.
8.2.3 Description
It is important to make security as one of the primary objectives while designing O&M
networks. Firewalls, filtering routers and VPN gateway are just some of the devices and
techniques that are used in designing secure O&M networks.
Recommendations of network secure infrastructure include the following devices.
• Firewalls
• VPN
• Router
• Anti-virus
• ID authentication
• Windows patch management
8.3 ZXO-07-07-003 User Management

Feature change: N/A
8.3.1 Summary
User Management is composed of client and server. On the client, user login window is
used to perform login functions. The server then accomplishes logical processing of
login authentication and operation authentication.
Creating, modifying, and deleting users are supported. And login history is recorded.
8.3.2 Benefits
User management helps ensuring the legal usage of the system. Specific & reasonable
user-role relationship provides security control for operators while performing network
management operations.
Login authentication prevents illegal users from entering the system and operation
authentication helps in restricting the user roles.
The right allocation information of this user can be queried.
8.3.3 Description
User and role definition:
User refers to the operator who logins and uses the U31 system. While creating a user,
the system administrator defines the access rights given to the user by specifying his
role. The user can not modify own rights, and his or her operations are related with own
rights except for administrator. Through the role management and user management,
U31 ensures the security of the system.
System administrator can restrict a user from certain operation, it means if a user group
is restricted from doing some operation, then even if a user of that group gets right from
another group (one user can be in one more user groups), user will not be able to
perform the restricted task.
Creating, modifying, and deleting users are supported:
Creating user: create a new user include, defining user name, password, password
expiry limits, password length, other users’ information (e-mail address, telephone
number etc.), assigned role for user, operation authority.
Modifying user: include modify certain user’s name, password, password expiry
conditions, password length, other users’ information (e-mail address, telephone number
etc.), assigned role for user, operation authority.
Deleting user: delete appointed user.
Password policy can be set:
At least six characters;
Password includes at least three of the following four types: numbers, lowercase letters,
uppercase letters and other characters.
Login history is recorded:
The user login time can be queried and set, and the user locking history record can be
queried.
User account rule management:
User can view, customize log on password length, user password strategy, and also can
define maximum/minimum password length, set account limit rule, including accounts
lockup status and lockup rule. User also can define password wrong number and
release time, also can carry out overdue accounts check and password overdue check.
User can launch authorization failure number continuously, for example, if authorization
failure for 5, system will forbid this user, which can prevent illegal users log on system.
Logon user management:
• Log on period
U31 system can set log on period for user, user can only log on during specified
period.
• Forced disconnection of a user
A super administrator can force disconnection of a login user to prevent illegal

operation and ensure system security.
• Setting a login IP range for a super administrator
Upon login, a super administrator is entitled to any operation without control. To

regulate and control an administrator’s login range, it is allowed to set a specific
login IP range for a super administrator, who can only log in to an IP address within
this range, but can‘t log in to any IP address without this range even through the
username and password are both correct.
• Modifying all user passwords
A super administrator can modify the password of any user other than
administrators. This modification is not restricted by any password rules. All users’
passwords can be modified into a single password. This password modification way
enables a super administrator to unify an initial user password and prevent other
users, especially illegal users from login, so as to better ensure system security.
• Viewing user locking details and de-locked users
An administrator can have a real-time knowledge of user locking details and unlock
any locked user whenever necessary. The system can also provide a locked user
with automatic unlocking function, with which the user can customize automatic
unlocking time within the account locking restriction rules.
• Interface locking
If a terminal interface is not operated within a period of time, this terminal will be
locked automatically, and users must log in again to prevent illegal users from
operating this terminal. Users can also lock a terminal manually to prevent illegal
operation.
8.4 ZXO-07-07-004 User Authorization

Feature change: N/A
8.4.1 Summary
U31 is able to authorize system user. It assigns different operation authorities and
access resources to different users.
8.4.2 Benefits
It prevents users’ unauthorized mis-operation or maliciously damages of key data.
8.4.3 Description
System assigns operation authority and access resources to users by assigning different
roles.
Operations scope: Operator can specify the functional modules of the U31 available for
the specified role. For example for the Log Management, they can define if the user is
allowed to query or maintain the logs.
Resources scope: Operator can specify the subnets or specific NEs under the subnets
the issuer will be able to operate.
Operations and resources are the two aspects of a role. They are defined independently,
but when a role is used, the final access rights are the intersection of the two aspects.
For example, if a user’s role is set to "log management" and resource to "BSC40", it
indicates that the user is authorized to operate and manage the logs of “BSC40” device.
8.5 ZXO-07-07-005 Role Management

Feature change: N/A
8.5.1 Summary
Role is defined as the administration and operation rights assigned to users. Virtually,
the rights for a group of users are defined by specifying their operations and resources.
8.5.2 Benefits
Role management helps in ensuring the legal usage of the system. Specific and
reasonable user-role relationship provides security control for operators while performing
network management operations.
8.5.3 Description
A role is a set of operation scope and resource scope. A role can be assigned to
different users. Role can be locked. Role management provides creating, querying,
modifying, and deleting of role. Role stands for rights. Operators can copy role, query
the information of a role, query the information of all roles, and query role assignment.
Different roles shall be generated through modifying rights assignment in security

management. Easy to be used, role set is introduced. System provides default super-
role.
Role assignment includes operation scope and resource scope. Operation scope refers
to all operations for managed objects and resource scope refers to all managed objects.
When a role locked, all rights for users shall be cancelled.
8.6 ZXO-07-07-006 Log Management

Feature change: N/A
8.6.1 Summary
Operation log, system log, and security log are supported. Query of logs based on
different conditions are also supported. Export and print of log are supported. Log policy
is also provided.
8.6.2 Benefits
Information about all operations carried out by users is supported as well as system
working status as and when required.
The logs can be queried by classification, deleted, filtered, exported and printed.
The user can customize the log policy freely.
8.6.3 Description
ZTE U31 server can record the origination of the subscriber’s login, operation
commands and execution results.
Log Management provides 3 types of log:
Operation log:
Operation log record refers to the log for the operations initiated at the interface like
user's operation information, such as the creation or deletion of NE, or modification of
NE parameters, and so on. Other operations through other access modes such as
CORBA, Telnet and Web-based modes are also recorded. At present, these logs are
basically recorded through the F interface uniformly, or they can be also recorded by
invoking the log interface at the client or server side. For example, such access modes
as CORBA and Telnet modes need to invoke the log interface by themselves to record
logs. In the log item, there is a flag to indicate whether the operation is successful or
failed.
System log:
The system log records some operations performed at the server background, such as
performance collection scheduled task and scheduled backup task. Others are the
system logs when the notification information is sent from the northbound interface. For
example, the data can be reported if a notification is sent to ZTE U31 when the NE
reports performance data, and then ZTE U31 will record a system log. The system log
also provides interfaces at the server and client. The processing mode is the same as
that for the operation log.
Security log:
Security log records the log when the user logs on the system, such as login success,
login failure and failure cause, and it provides the interface at the server. Security log
need not record two time points, but only one operation time. That is, the security log
need be recorded once only. At login at different access modes the security log should
also be record now.
Except for above three types of logs, event report is also recorded into alarm database.
Event report log: Event report log records a log when the event message is reported. For
example, a log is recorded when an alarm event is reported. Currently, the reported
event is recorded in its own module usually. For example, the alarm event is recorded in
the database of the alarm module.
Log query is provided for log statistics:
Query and statistics can be calculated according to different conditions, such as user
name, operation terminal, operation time, operation type, completion status for the
tracing and location of modification to the NE.
Operation log query:
Supporting querying by the user name, operation command, operation command set,
operation resource, operation result, operation time, log level and access mode; The
querying result is displayed in pages.
System log query:
Querying by level, log name, log source and time is supported.
Security log query:
Supporting qeurying by user name, log name, time and access mode is supported
Event report log query:
Supporting qeurying by level and time is supported.
Querying the detailed information of a single log: After a type of logs are queried, the
user can click a log in the log table to display its details below.
Setting Log Filtering Conditions:
At present, filtering conditions can be set for system log only to perform filtering by level.
After a level is set, the logs lower than this level will be filtered away if system logs are
recorded later.
Log deleting is provided:
Delete operation logs: Provides operation logs deletion function based on date
Auto delete operation logs: Automatically deletes the operation logs after the user
defined time frame.
Operating system event record:
Operating system event is supported, for example: close and start of server, link setup
and break.
Software download and activation record:
Destination NE for download, download time, and version, activation time.
Backup and restoration record:
Backup time and content, restoration time, restoration of content are also recorded.
Log exporting and printing:
Log exporting refers to exporting according to the current querying condition, and the
exported records should be all the records that satisfy the current querying condition.
The exported logs can be saved in XLS format at the client. The same as log exporting,
the printed records are all of the records satisfying the current querying condition.
Log policy:
In policy management, the user can create a log backup policy and system can
periodically execute it (the default log backup policy period is one month). When this
policy is executed, logs will be exported under the log directory of the platform, and all
the log contents are cleared at the same time. The database write-in log will be recorded
in a temporary file, and the user can create a log recovery storing policy in policy
management. When the database connection is recovered, the log will record the log
record in the temporary file to the database again. User can define the minimum log
period in configuration i.e. 1 day, 30 days, 90 days, etc.
9 Trace Management
9.1 ZXO-07-08-001 Signaling Trace (GERAN)

Feature change: N/A
9.1.1 Summary
Trace signaling flow and observe signal processing. To judge whether signal process is
in normal status.
9.1.2 Benefits
Signaling trace is an auxiliary tool of EMS, fulfilling the functions as signaling analyzer in
O&M. It helps O&M engineer observe real-time signaling procession more conveniently,
and allows developer to debug the foreground program. Through analysis of signaling,
network and equipments status are easily to be obtained, which is helpful to locate faults.
9.1.3 Description
The primary tasks of this system are:
To trace BSC-related signaling, to convert the signaling flow into texts to facilitate
observation, to save the traced signal for future references, and to provide filtering
function for the ease of observation.
The protocols concerned include:
A interface No.7 MTP, SCCP and mobile application protocol (for BSSMAP details, refer
to specification 08.08), Abis interface layer three messages (for RSL, refer to
specification 08.58 and RR, MM, CC refer to 04.08) and Abis interface internal
management messages. It is used to facilitate the reference of signaling workflow and
the findings of signaling coordination errors.
Application of this function:
The main working environment of this system is to realize the trace of a BSC by a
terminal under the condition of small traffic volume in the course of debugging. And at
the same time, it saves the trace messages into a file for future observation. The size of
the trace file depends on the disk capacity while the observation trace file doesn't have
this restriction.
9.2 ZXO-07-08-002 Signaling Trace (UTRAN)

Feature change: N/A
9.2.1 Summary
Trace signaling flow and observe signal processing. To judge whether signal process is
in normal status.
9.2.2 Benefits
Signaling trace is an auxiliary tool of EMS, fulfilling the functions as signaling analyzer in
O&M. It helps O&M engineer observe real-time signaling procession more conveniently,
and allows developer to debug the foreground program. Through analysis of signaling,
network and equipments status are easily to be obtained, which is helpful to locate faults.
9.2.3 Description
Signaling trace objects are:
UE (may be IMSI number), CELL (cell ID) and Node B (NODEBID). It supports following
tasks:
RNLC IU trace is to tail signaling at Iu interface.
RNLC IUB trace (IUB_CELL and IUB_NODEB) is to tail signaling at Iub interface and
signaling between RNC and NODEB. CELL and NODEB are included.
RNLC IUR trace is to tail signaling at Iur interface, which is signaling among RNCs. Here
users refer to the neighboring RNC. Then it’s possible to tail signaling between current
connected RNC and the neighboring RNC.
RNLC UE trace is to tail UE signaling, which is signaling between UE and RNCs. Two
kinds of traces are included: Single UE and cell multi-UE trace.
RNL cell detection set trace is to tail signaling of RNL cell set.
RTV trace (RTV_CELL and RTV_UE) is to tail real-time UE or cell information.
10 O&M Infrastructure
10.1 ZXO-07-09-001 Telnet Access

Feature change: N/A
10.1.1 Summary
ZTE U31 system provides telnet access function.
10.1.2 Benefits
ZTE U31 system supports low-bandwidth Telnet access; it suits for various low-
bandwidth network environments to reducing networking investment.
10.1.3 Description
With the help of a telnet access server, user can remotely avail SSH encrypted access to
ZTE U31 system.
The telnet console can be a VT terminal or an X-window based on ASCII.
11 Tool
11.1 ZXO-07-10-001 Health Check(GERAN)

Feature change: N/A
11.1.1 Summary
Health check tools can check the running status online, and generate report according to
data and diagnosis. Health check on GERAN includes checking of BSS and U31.
11.1.2 Benefits
Simplify users’ daily O&M jobs to find existed issues and emerging issues by continuous
checking, and locate the points to be improved or adjusted of running circumstances.
Improving capability to prevent problems, find, locate and resolve problems in time.
11.1.3 Description
Users can customize complete system parameters and health check setting on health
check tool to activate BSS and U31 status analysis and generate report.
By task setting, users can realize timing check just by entering checking period and
turning on the start time.
Health check on BSS:
Key status check of Abis/A/Ater/G interface, including No.7 signaling link’s status,
NSEI/NSVCI status, relay link’s sum and status etc.;
BTS status check: whether running normally, whether there is some blocking, channels’
status, quantity statistics etc.
Key board load check, including CPU load, standby status, master/standby switching
times, board’s booting time, etc.
Capacity check, including modules number, site number, TRX number, CS traffic
channel number, PS traffic channel number, commissioned site, un-commissioned site,
etc. managed by a BSC.
11.2 ZXO-07-10-002 Health Check (UTRAN)

Feature change: N/A
11.2.1 Summary
Health check on ZTE U31 system includes two parts: NE and ZTE U31 system, aims to
automatically check NEs’ running status to make daily O&M convenient.
11.2.2 Benefits
It is in favor of engineering inspection, reducing human resources.
11.2.3 Description
Health check contains following items:
1. NE Health Check
1) Interface status
2) Radio status
3) Processor status
4) Capacity report
5) Alarm
2. EMS Health Check
1) Version information
2) Disk capacity
3) Database running status
4) Backup data
5) Key directory
6) Configuration file
7) Environment variables
11.3 ZXO-07-10-003 MML Command Terminal

Feature change: N/A
11.3.1 Summary
ZTE U31 system provides Man-Machine-Language interface to maintain network
elements with GUI interface. The MML follows ITU-T specifications, and it also supports
XML format comply users' re-development.
11.3.2 Benefits
The MML command terminal provides a man-machine interaction shortcut measure, with
friendly interface and diversified man-machine commands. It provides powerful support
and help to the system O&M.
1 Convenient and shortcut: Through delivered man-machine command, it

conveniently and directly obtains the specified system running status information,
facilitating user’s analysis of current system running status and helping to locate the
system running abnormity.
2 Friendly and convenient interface: It provides friendly and convenient interface,

supporting these functions: Command processing, result displaying, command
prompt, help and auxiliary setting.
3 Abundant man-machine commands: It provides configuration management,

performance management, fault management and other man-machine commands,
capable of adding, deleting, querying and modifying system running status and
condition parameters. It effectively supports the system O&M.
11.3.3 Description
All operations of radio configuration management and fault management in U31 GUI
interface can be translated into the command(s) of F interface to send to the U31 server.
U31 has a MML GUI interface to let user Edit and execute MML commands.
U31 provides functions such as opening, saving, editing, and executing MML script.
U31 server has an interface to let other system access with MML command through an
IP socket.
The following functions are provided:
1 Input of man-machine commands in character mode: The user can directly input the
command in the command input area.
2 Input of man-machine commands in graphic mode: Through the graphic input

interface, the user only needs to set the required parameter value of the command.
3 Man-machine command prompt: The user inputs the command code or name and
presses <F4>, and then the prompt of the related command will be displayed. It also
supports “fuzzy” matching function of commands. The user can only input partial
command code or name, and then the related command can be matched.
4 Help of man-machine command: The user inputs the complete command

code/mnemonic symbol and presses <F5>, and the details of this command will be
displayed.
5 Copying and pasting of man-machine command; automatic reorganization after

pasting multiple lines
6 Supplementary of partial parameters of man-machine command: Based on the

topology node selected by the user, the partial paratmers are supplemented.
7 History buffer of man-machine command
8 Creation, editing, syntax check, saving and execution of batch commands
9 Execution of man-machine command: Providing shortcut button and shortcut key of

command execution (the user should press <Enter> in the command input area to
execute the current command)
10 Repeated execution of history command: The user selects a history command, and
presses <Enter> or click shortcut key to execute it.
11 Displaying of man-machine command response: The responses can be displayed in

single or multiple pages.
12 Multi-batch browsing of man-machine command: If the execution result of the man-

machine command contains multiple batches of data, the character terminal
provides viewing navigation.
13 Displaying of history man-machine command
14 Copying and file saving of man-machine command result
15 Topology navigation: It provides a topology navigation tree, listing the basic

topology information of the current access devices and NEs, for the sake of man-
machine command delivery.
16 Navigation of man-machine command set: It supports the organization of all kinds of

man-machine commands in tree format, to facilitate search.
17 Auxiliary setting of character terminal: Including setting of history command buffer

quantity and command displaying in single or multiple pages.
Customization of man-machine command set: Different types of applications can

customize own command set. After system startup, man-machine command set and
other auxiliary functions can be switched through application type switching.
Users can carry out complex operation using script, which is helpful for rollback
operation and reducing logical faults.
NetNumen U31supports MML interface, which can bring much convenience to client
operation as bellows:
• Bulk operation to data
• Data configuration and status management command executing;
• Version management
• Open, store, edit and execute MML script
11.4 ZXO-07-10-004 Online Help

Feature change: N/A

11.4.1 Summary
ZTE U31 system provides online help function.
11.4.2 Benefits
Rapid and convenient operation guide is provided for user. This function helps the user
to get the system help quickly, operate efficiently and avoid or reduce mistakes.
11.4.3 Description
By clicking F1, “help” can be directly opened. Online help can be displayed in active
page form and clicking on the F1 at different interface, displays different topics. When
the user meets question, it can be easily to find the solution.
Online help can provide all the description of function including GUI interface and MML
method.
User can locate certain help page by index and search function.
Acronyms and Abbreviations

Abbreviations Full names
3GPP 3rd Generation Partnership Project
BSS Base Station Subsystem
BTS Base Transceiver Station
CBC Cell Broadcast Center
DB Data Base
DIF Database Interface Function
EDGE Enhanced Data rate for Global Evolution
EGPRS Enhanced General packet Radio Service
FTP File Transfer Protocol
GERAN GPRS EDGE Radio Access Network
GGSN Gateway GPRS Support Node
GSM Global System for Mobile Communication
GUI Graphical User Interface
IM Inventory Management
IP Internet Protocol
KPI Key Performance Indicator
LA Link Adaptation
LLC Logical Link Control
LMT Local Maintenance Terminal
MAC Medium Access Control
MML Man Machine Language
MO Managed Object
MOS Mean Opinion Score
MS Mobile Station
MSC Mobile Switching Center
NAF Network Adaptation Function
NE Network Element
NMC Network Management Center
Node B WCDMA base station
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
PCU Packet Control Unit
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
QoS Quality of Service
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
RLC Radio Link Control
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
RLP Radio Link Protocol
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
RNC Radio Network Controller
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
SGSN Serving GPRS Support Node
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
SMS Short Message Service
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
TBF Temporary Block Flow
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
TDMA Time Division Multiple Access
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
TS Time Slot
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
UDP User Datagram Protocol
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
UNC Universal Nodes Controller
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
UTRAN Universal Terrestrial Radio Access Network
DB Data Base
LA Link Adaptation
MO Managed Object
MS Mobile Station
NE Network Element
WCDMA Wideband Code Division Multiple Access

NetNumen U31 RAN

Uploaded by

Document Information

Original Title

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

NetNumen U31 RAN

Uploaded by

Copyright:

NetNumen™ U31 RAN

Basic Feature Description

NetNumen™ U31 RAN Basic Features Description

Version Date Author Approved By Remarks

V1.0 2010-07-15 ZhuBing Not open to the Third Party

© 2011 ZTE PARSIAN Corporation. All rights reserved.

2 Topology Management ............................................................................................ 5

3 Configuration Management ..................................................................................... 9

4 Fault Management ................................................................................................. 32

5 Performance Management .................................................................................... 47

6 Software Management ........................................................................................... 55

7 System Management ............................................................................................. 59

8 Security Management ............................................................................................ 63

9 Trace Management ................................................................................................ 71

10 O&M Infrastructure ................................................................................................ 73

11 Tool ......................................................................................................................... 73

Table 1 The Classification Definition of ZTE U31 Features

Class No. Class Description

2.1 ZXO-07-01-001 Topology View

Feature change: N/A

HW&SW Dependencies: N/A

Commercial Attention: N/A

This feature also provides navigating to configuration management, fault management,

This feature supports topology data display based on user authority.

Synchronization between topological data and configuration data is supported to ensure

Topology Navigation Tree:

Physical View and Logical View

Display Control of Topological View:

Topological View Automatic Layout:

NE Grouping in Logical View:

Topological View Filtering:

Topology Data Display Based on User Authority:

Virtual NE and Virtual Link:

Logical Nodes and Link Control:

Voluntary Synchronization of Topological Data:

Longitude and Latitude Coordinates:

Fast entry to CM/FM/PM Interfaces:

Navigation icons are provided for quick entry to Configuration Management/Fault

2.2 ZXO-07-01-002 Key CM/FM/PM Information Display

Feature change: N/A

HW&SW Dependencies: Topology View (SW)

Commercial Attention: N/A

User can also access to NE configuration interface to perform configuration operations

Fault management information display:

Performance management information display:

User can also access to performance management interface to perform performance

3.1 ZXO-07-02-001 Configuration Management

Feature change: N/A

HW&SW Dependencies: N/A

Commercial Attention: N/A

Configuration management provides complete constraint checking set and visualized

CM operation log is supported:

RNC Configuration Categories:

Physical configuration includes configuration of rack, shelf, slot and board.

Transmission configuration includes ATM transmission, all-IP transmission and line-

Wireless configuration includes configuration of overall parameters, cell information,

Node B Configuration Categories:

Transmission configuration includes ATM transmission, all-IP transmission and line-

Wireless configuration includes configuration of sector information, cell information and

Bulk Parameters Modification:

Execute files that contain several MML commands.

System provides corresponding templates in XLS format facility containing several

Site commissioning/Debugging setting:

Setting of single/bulk site commissioning/debugging status is supported. Users can

3.2 ZXO-07-02-002 Configuration Management

Feature change: N/A