SJ-20140724091740-002-NetNumen U31 R18 (V12.13.50) Product Description

NetNumen U31 R18
Unified Element Management System

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

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Unified Element Management System ................................................................. 1-1
1.2 Features ............................................................................................................ 1-2
Chapter 2 System Architecture ................................................................. 2-1

2.1 Hardware Architecture ........................................................................................ 2-1
2.2 Software Architecture ......................................................................................... 2-4
Chapter 3 Configuration Requirements ................................................... 3-1

3.1 Server Configuration Requirements ..................................................................... 3-1
3.2 Client Configuration Requirements ...................................................................... 3-3
Chapter 4 System Principles ..................................................................... 4-1

4.1 Hierarchical Model.............................................................................................. 4-1
4.2 Embedded Remote Terminal ............................................................................... 4-2
Chapter 5 Product Functions .................................................................... 5-1

5.1 Topology Management ....................................................................................... 5-1
5.2 Fault Management ............................................................................................. 5-2
5.3 Performance Management.................................................................................. 5-4
5.4 Security Management......................................................................................... 5-5
5.5 Log Management ............................................................................................... 5-6
5.6 Maintenance Management.................................................................................. 5-7
5.7 Command Line Terminal ..................................................................................... 5-8
5.8 Wireless Configuration Application ...................................................................... 5-9
5.9 Network Element Management ........................................................................... 5-9
5.10 SON Functions............................................................................................... 5-10
5.11 Integrated Configuration Management ..............................................................5-11
5.12 Inventory Management ....................................................................................5-11
5.13 Version Management...................................................................................... 5-12
5.14 Remote Upgrade Management........................................................................ 5-12
Chapter 6 Interfaces and Protocols .......................................................... 6-1

6.1 Internal Interfaces .............................................................................................. 6-1
6.2 Southbound Interfaces........................................................................................ 6-1
6.3 Northbound Interfaces ........................................................................................ 6-1

6.3.1 CORBA Northbound Interfaces ................................................................. 6-2
6.3.2 FTP Northbound Interface......................................................................... 6-4
6.3.3 SNMP Northbound Interface ..................................................................... 6-5
6.3.4 SOCKET Northbound Interface ................................................................. 6-7
Chapter 7 Networking Modes .................................................................... 7-1

7.1 Local Networking Mode ...................................................................................... 7-1
7.2 Remote Networking Mode................................................................................... 7-2
7.3 Remote Client Networking Mode ......................................................................... 7-3
Chapter 8 Environmental Requirements .................................................. 8-1

8.1 Temperature and Humidity Requirements ............................................................ 8-1
8.2 Grounding Requirements .................................................................................... 8-2
8.3 Electromagnetic Interference Prevention.............................................................. 8-3
8.4 Lightning Protection Requirements ...................................................................... 8-3
8.5 Electrostatic Discharge Prevention ...................................................................... 8-4
8.6 Other Requirements ........................................................................................... 8-5
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II

About This Manual
Purpose
This manual describes the functions, features, working principles, networking modes, and
environmental requirements of the NetNumenTM U31 R18 Unified Element Management
System (NetNumen U31).
Intended Audience
This manual is intended for:
l Maintenance engineers
l Software debugging engineers
What Is in This Manual

This manual contains the following chapters.
Chapter 1, Overview Provides a brief overview of the NetNumen U31 system, including
the system location in a telecommunications management network
and system features.
Chapter 2, System Describes the hardware and software architecture of the NetNumen
Architecture U31 system.
Chapter 3, Configuration Provides the configuration requirements for the server and client of
Requirements the NetNumen U31 system.
Chapter 4, System Principles Describes the hierarchical model and remote client principle of the
NetNumen U31 system.
Chapter 5, Product Functions Describes the management functions of the NetNumen U31 system,
including topology management, fault management, performance
management, security management, log management, maintenance
management, command line terminal, wireless configuration
application, and network element management functions.
Chapter 6, Interfaces and Describes the internal interfaces and external interfaces provided by
Protocols the NetNumen U31 system and protocols supported by the interfaces.
Chapter 7, Networking Describes the networking modes of the NetNumen U31 system,
Modes including local networking mode, remote networking mode, and
remote client networking mode.
Chapter 8, Environmental Presents the requirements for the operating environment of the
Requirements NetNumen U31 system.
Conventions
This manual uses the following typographical conventions.

Typeface Meaning
Note: provides additional information about a certain topic.
II

Chapter 1
Overview
Table of Contents
Unified Element Management System........................................................................1-1
Features.....................................................................................................................1-2
1.1 Unified Element Management System

The NetNumen U31 system is a unified element management system that manages
network elements that support different radio access technologies. It provides northbound
interfaces for connecting to an upper-layer network management system. In the
NetNumen U31 system, individual network elements in a radio access system can be
configured, managed, and maintained in a unified manner.
In accordance with the network management model specified for a Telecommunications
Management Network (TMN), the NetNumen U31 system is located on the network
element management layer, see Figure 1-1.
Figure 1-1 Network Management Model
The NetNumen U31 system provides the following management functions:

l Topology management
l Configuration management
l Fault management
l Performance management
1-1

NetNumen U31 R18 Product Description
l Security management
l System management
l Log management
l Task management
The NetNumen U31 system receives various data (such as topology data, alarm data, and
performance data) from managed network elements, and displays the received data on a
GUI after data modeling and conversion. Management operations can be performed on
the GUI, through a command line terminal, or by special maintenance tools.
In addition, the NetNumen U31 system supports:
l Role-based and domain-based management
l Data backup and restoration
l Three-layered network architecture
l Network Time Protocol (NTP)
1.2 Features
Compliance to Standards
The NetNumen U31 system strictly complies with the network management
recommendations and standards specified by the following organizations:
l International Telecommunication Union-Telecommunication Standardization Sector
(ITU-T) SG2
l Telecommunication Management Forum (TMF)
l International Organization for Standardization (ISO)
l Internet Engineering Task Force (IETF)
l 3rd Generation Partnership Project (3GPP)
l China Communication Standard Association (CCSA) TC7 WG1
Integrated Network Management

The NetNumen U31 system can manage various ZTE radio equipment developed for
different radio access systems, including:
l Universal Mobile Telecommunication System (UMTS)
l Global System for Mobile Communication (GSM)
l Time Division-Synchronization Code Division (TD-SCDMA)
l Long Term Evolution (LTE), including LTE-Frequency Division Duplex (LTE-FDD) and
LTE-Time Division Duplex (LTE-TDD)
l Worldwide Interoperability for Microwave Access (WiMAX)
l Microwave access system
l Wireless Local Area Network (WLAN)
1-2

Chapter 1 Overview
System Expansion
The NetNumen U31 system is designed with a modularized structure, which provides a
strong expansion capability for managing new equipment and services.
System Openness
The following technologies ensure the openness of the NetNumen U31 system:
l Various standard northbound interfaces support data and service sharing between
the NetNumen U31 system and other service systems, including Common Object
Request Broker Architecture (CORBA), Simple Network Management Protocol
(SNMP), SOCKET interface, and FTP/Simple File Transfer Protocol (SFTP)
northbound interfaces.
l The Java platform allows the NetNumen U31 system to operate in a Windows or UNIX
operating system, depending on the scale of the network to be managed.
System Reliability
The NetNumen U31 system features a high reliability with the following capabilities:
l The NetNumen U31 server has redundant network ports and supports dual power
supplies and disk mirroring for hardware reliability of the system.
l The NetNumen U31 system supports different High Availability (HA) and disaster
recovery solutions. The switchover between the active and standby servers prevents
service interruption when the active server fails.
l The NetNumen U31 system provides the system management and monitoring
capability to ensure reliable operation of the system.
l The NetNumen U31 system supports disk mirroring and data backup for data security.
à Disk mirroring: All data on the active disk can be synchronized to and backed up
on the standby disk in the same server.
à Data backup: The system data can be backed up or dumped to a peripheral
storage device (such as a disk or a magnetic tape). Users can restore the system
data from the backup on the storage device when necessary.
l The NetNumen U31 system supports in-band management and out-of-band
management. In the out-of-band management mode, network management
data and service data are transmitted through different channels. In the in-band
management mode, two types of data are transmitted through the same channel. For
applications with high reliability requirements, the out-of-band management mode is
recommended.
System Security
The security of the NetNumen U31 system is ensured due to access control and complete
logs.
l The access control function enables users to perform permitted operations on
particular network elements.
1-3

l The system provides three types of logs (system logs, security logs, and operation
logs) that record all operations performed by different users and events occurring in
the system.
Ease of Use
The NetNumen U31 system provides a friendly Graphical User Interface (GUI), on which
users can manage network elements in an intuitive way.
1-4

Chapter 2
System Architecture
Table of Contents
Hardware Architecture................................................................................................2-1
Software Architecture .................................................................................................2-4
2.1 Hardware Architecture

The NetNumen U31 system has a client/server architecture. An operating system, a
database, and key management modules of the NetNumen U31 system are installed on
the server. In addition, a large amount of data is stored on the server. The client provides
a GUI that supports various management operations. Users can log in to the server
through a client, and then access and manage resources on the server. The server sends
operation results to the client for display upon user requests.
The server can be logically divided into two parts: an application server and a storage
device.
l The application server, as a physical platform of the NetNumen U31 system,
processes all data received from managed elements. The system performance
greatly depends on the processor capability of the application server.
l The storage device is used to store a large amount of important data in the system.
In addition to internal disk drives in the application server, a separate storage device
is generally configured to expand the storage capacity and achieve high availability
for the system.
The NetNumen U31 system can be configured as a single-server system, a
high-availability system, or a disaster recovery system. The hardware architecture
varies with different system configurations. The NetNumen U31 system is delivered with
single-server configuration by default.
The following describes the hardware architecture of the NetNumen U31 system with three
different configurations.
Single-Server System
In a single-server NetNumen U31 system, only one workstation is used to provide
both application services and database services. For the hardware architecture of the
single-server system, see Figure 2-1.
2-1

Figure 2-1 Single-Server System
High Availability System

In a high availability NetNumen U31 system, two workstations (servers), an active server
and a standby server, are used in a Local Area Network (LAN) to provide high availability
of services for clients. These two servers, sharing a disk array, are connected with a
heartbeat cable. For the hardware architecture of the high availability system, see Figure
2-2.
2-2

Chapter 2 System Architecture
Figure 2-2 High Availability System
High availability software is used to manage the two servers. The active server provides
application and database services and stores data on the disk array in real time; while the
standby server does not provide services. If the active server fails, the standby server will
take over the applications and provides continuous services.
Disaster Recovery System

In a disaster recovery NetNumen U31 system, two workstations (servers), an active
server and a standby server, in different LANs are used for disaster recovery. The two
workstations are connected through a network. Each workstation has a disk array for data
storage. For the hardware architecture of the disaster recovery system, see Figure 2-3.
2-3

Figure 2-3 Disaster Recovery System
The active server provides application and database services and stores data on its disk
array in real time; while the standby server does not provide services. Cluster management
software is used to manage the two servers and implement data synchronization from the
active server to the standby server. If the active server fails, the standby server will take
over the applications and provides continuous services.
2.2 Software Architecture

The NetNumen U31 system has a client/server software architecture. The software
consists of two parts: server software and client software, which communicate with each
other through TCP/IP.
l Server software
The server software provides the following functions:
à Topology management
à Fault management
à Performance management
à Security management
à Log management
à Maintenance management
à Command line terminal
à Wireless configuration application
à Network element management
à Self-Organizing Network (SON) management
à Integrated configuration management (ICM)
à Inventory management
2-4

Chapter 2 System Architecture
à Version management
à Remote Upgrade Management
l Client software
The client software provides a GUI for users to access the server and perform
management and maintenance operations on managed network elements.
2-5

This page intentionally left blank.
2-6

Chapter 3
Configuration Requirements
Table of Contents
Server Configuration Requirements............................................................................3-1
Client Configuration Requirements .............................................................................3-3
3.1 Server Configuration Requirements

The NetNumen U31 server can be installed in a centralized or distributed way.
l Centralized installation: The server is installed on a minicomputer.
l Distributed installation: The server is deployed on a blade.
Hardware Configuration
For centralized installation, an IBM or Sun workstation is used as the NetNumen U31
server. For the recommended hardware configurations of an IBM workstation, refer to
Table 3-1. For the recommended hardware configurations of a Sun workstation, refer
to Table 3-2. For a description of the server hardware configuration in a distributed
environment, refer to Table 3-3.
Table 3-1 Server Hardware Configuration (IBM Workstation)
Hardware Configuration 1 (for a Network with Configuration 2 (for a Network with

5000 Cells) 10000 Cells)
Server Model: IBM P740 Model: IBM P740

CPU: 2×2 cores CPU: 4×2 cores
Memory: 32 GB Memory: 64 GB
Disk drives: 2×146 GB SAS drives Disk drives: 2×146 GB SAS drives
PCI adapter: dual port HBA PCI adapter: dual port HBA
Disk array NAS N6210 (14×300 GB, FC, 15 k NAS N6210 (28×300 GB, FC, 15 k
RPM) RPM)
Standby server Model: IBM P720 Model: IBM P720

Disk drives: 2×146 GB drives Disk drives: 2×146 GB drives
Tape TS3310 (11×1.5 TB) TS3310 (20×1.5 TB)
3-1

Table 3-2 Server Hardware Configuration (Sun Workstation)
Hardware Configuration 1 (for a Network with Configuration 2 (for a Network with

5000 Cells) 10000 Cells)
Server Model: Sun T4–1 SUN T4–1

Disk drives: 2×300 GB SAS drives Disk drives: 2×300 GB SAS drives
Disk array ST7320 (12×600 GB, SAS, 15 k RPM) ST7320 (20×600 GB, SAS, 15 k RPM)
Standby server Model: Sun T4–1 Model: Sun T4–1

Disk drives: 2×300 GB drives Disk drives: 2×300 GB drives
Tape SL 150 (11×1.5 TB) SL 150 (20×1.5 TB)
Table 3-3 Server Hardware Configuration (Distributed Mode)
Managed Object Configuration
Server HP BL460c Gen8 10GB FLB CTO Blade

CPU: 2×6 cores
Memory: 64 GB
Hard disk: 2×300 GB
Disk array IBMN3220 (450 GB)
Standby server N+M cluster configuration.

The hardware configuration is consistent with that for the server.
Software Configuration
For the recommended software configuration on the IBM workstation, refer to Table 3-4.
For the recommended software configuration on the Sun workstation, refer to Table 3-5.
For a description of the server software configuration in a distributed environment, refer to
Table 3-6.
Table 3-4 Server Software Configuration (IBM Workstation)
Software Version
Network management software NetNumen U31 R18
Operating system AIX 6107
Database Oracle Database Enterprise Edition (64-bit) Version 11.2.0.3.0 for

AIX
HA software (optional) PowerHA
3-2

Chapter 3 Configuration Requirements
Table 3-5 Server Software Configuration (Sun Workstation)
Software Version
Operating system Solaris 10 U10
Database Oracle Database Enterprise Edition (64-bit) Version 11.2.0.3.0 for So-
laris
HA software (optional) Symantec VCS and VVR 5.1
Table 3-6 Server Software Configuration (Distributed Mode)
Managed Object Configuration
Operating system Linux Radhat6.4
Database Oracle 11g Standard Edition, SybaseIQ
Note:
The HA software is only required in a NetNumen U31 system with high availability or
disaster recovery configuration.
3.2 Client Configuration Requirements

A PC is used as a NetNumen U31 client. For the recommended hardware configuration
of the PC, refer to Table 3-7.
Table 3-7 Client Hardware Configuration
CPU Pentium IV 3.0 GHz or higher
Memory 2 GB or higher
Disk drive 500 GB or higher
Disk array None
For the software configuration on a NetNumen U31 client, refer to Table 3-8.
3-3

Table 3-8 Client Software Configuration
Operating system Windows XP, or Windows 7
Browser Internet Explorer 7.0 or later
Document viewer Microsoft Office
Antivirus software Mcafee VirusScan 8.5, Norton, or Trend Micro
3-4

Chapter 4
System Principles
Table of Contents
Hierarchical Model......................................................................................................4-1
Embedded Remote Terminal ......................................................................................4-2
4.1 Hierarchical Model

The hierarchical model of a complete network management system is shown in Figure 4-1.
Figure 4-1 Hierarchical Model
A network management system has an architecture consisting of the following three logical
layers:
l Network Management Layer (NML)

The NML (NMS) provides management functions acting upon all NEs in the entire
network and supports the control and coordination of the NEs in the network view.
4-1

The NMS may comprise multiple subsystems, such as business analysis subsystem,
resource management subsystem, and electronic operation and maintenance
subsystem.
l Element Management Layer (EML)
The EML (EMS) provides management functions acting upon individual NEs, supports
management functions of the NML, and coordinates the communication between NEs.
The NetNumen U31 system is an EMS on this layer.
l Network Element Layer (NEL)
The NEL (OMM) provides management functions acting upon resources in an NE.
The NetNumen U31 system (EMS) connects to an NE through a local Operation &
Maintenance Module (OMM). The OMM reports the data collected from the NE to the
EMS regardless of the NE type, and converts the requests received from the EMS
into instructions that can be performed by the NE.
The NetNumen U31 system communicates with an NMS on the upper layer through
northbound interfaces, and communicates with managed NEs on the lower layer through
southbound interfaces.
The following describes the relations between the NetNumen U31 system and the other
two layers:
l To the upper layer (NMS), the NetNumen U31 system provides raw data for business
analysis, configuration information for resource management, and alarm information
for operation and maintenance.
l From the lower layer (OMM), the NetNumen U31 system collects various data from the
managed NEs, including topology data, alarm data, performance data, and reports. It
displays and manages the collected data after data modeling and conversion.
4.2 Embedded Remote Terminal

An Embedded Remote Terminal (ERT) is a client deployed in a remote area away from the
NetNumen U31 server to display data of NEs in this area. Figure 4-2 shows a NetNumen
U31 system with two ERTs, each located in a remote area.
4-2

Chapter 4 System Principles
Figure 4-2 Embedded Remote Client
The NetNumen U31 server collects data from managed NEs in different areas through
southbound interfaces. After being processed, all collected data can be displayed on the
GUI of a local client.
The ERT in an area gets access to the data on the server through TCP/IP, and supports
management operations on the NEs in the area. To ensure network security, the security
management functions can be used to assign ERT users specific authorities.
4-3

4-4

Chapter 5
Product Functions
Table of Contents
Topology Management ...............................................................................................5-1
Fault Management .....................................................................................................5-2
Performance Management .........................................................................................5-4
Security Management ................................................................................................5-5
Log Management .......................................................................................................5-6
Maintenance Management .........................................................................................5-7
Command Line Terminal.............................................................................................5-8
Wireless Configuration Application .............................................................................5-9
Network Element Management ..................................................................................5-9
SON Functions.........................................................................................................5-10
Integrated Configuration Management......................................................................5-11
Inventory Management.............................................................................................5-11
Version Management ...............................................................................................5-12
Remote Upgrade Management ................................................................................5-12
5.1 Topology Management

The topology management functions enable users to know the distribution of large amounts
of equipment in the entire network and manage various equipment by group in a centralized
manner.
The topology management window on the GUI of the NetNumen U31 system provides two
modes for displaying equipment layout in the network: topology graph and topology tree.
l On the topology graph, managed Network Elements (NEs) are organized by layers
in accordance with parent-child relations. Interconnections of NEs are displayed in
lines. A legend and the network’s panoramic view are displayed on the right part of
the topology graph. In addition, users can use a filter on the toolbar to determine the
NEs to be displayed on the topology graph.
l The topology tree lists all nodes in the entire network; while the topology graph only
displays all nodes on the current layer. Navigation is supported between the topology
tree and the topology graph. Any topology change is synchronized between the
topology graph and the topology tree.
The following describes topology management functions from three aspects: topology
display, operations on the topology, and monitoring functions on the topology.
5-1

Topology Display
The NetNumen U31 system uses a combination of resource tree (topology tree) and
network topology (topology graph) to show all resources in the entire network. Various
management views are available in respect of different management requirements.
Operations on the Topology

The following operations can be performed in the topology management window:
l Managing the topology graph
l Managing NE agents
l Managing NEs
l Managing virtual links
l Managing groups
l Customizing user interface elements
Monitoring Functions on the Topology

The NetNumen U31 system displays the operating status of managed NEs on the
topology graph dynamically in addition to the configuration information, alarm information,
and performance information in the network.
5.2 Fault Management

The fault management functions enable users to detect and locate faults in the managed
network. The NetNumen U31 system monitors NE failures by receiving alarm information
reported at the time of occurrence. The NetNumen U31 server and client cooperates with
each other to implement the centralized fault management functions.
The following describes available fault management functions in the NetNumen U31
system:
Alarm Data Collection

The NetNumen U31 system collects alarm data in real time and ensures the accuracy of
alarm data collected from managed NEs. Alarm reporting conditions can be set to filter
alarm information not required.
Alarm Information Synchronization

The alarm information synchronization prevents inconsistent alarm data between NEs and
the NetNumen U31 system. Data inconsistency may occur due to a network failure, server
failure, or NE failure. The NetNumen U31 system supports two synchronization modes to
ensure data consistency: manual synchronization and automatic synchronization.
Alarm Monitoring
The NetNumen U31 system displays received alarms in the form of charts or tables. The
following alarm monitoring functions are supported:
5-2

Chapter 5 Product Functions
l Monitoring alarms through the client GUI, an alarm box, short messages, and E-mails
l Monitoring alarms and notifications by NE and NE type
Alarm Query and Statistics

The following alarm query and statistics functions are supported:
l Querying all active alarms, historical alarms, and notifications
l Querying alarms by customized conditions
l Collecting basic, busy-time, and important alarm-code statistics of history alarms
l Counting the occurrence frequency and effective duration of alarms by predefined
conditions or customized conditions
l Scheduling a periodic alarm statistics task for exporting specific alarms to a file
l Counting alarms for VIP sites, Class-B sites, and Class-C sites
Alarm Management
The following operations are supported on an alarm displayed on the client GUI:
l Acknowledging an alarm
l Unacknowledging an alarm
l Clearing an alarm
l Commenting an alarm
l Forwarding an alarm
l Viewing the details of an alarm
l Supplementing handling suggestions for an alarm
l Creating a rule based on an alarm
l Querying related rules for an alarm
l Locating NEs related to an alarm
l Printing an alarm
l Exporting an alarm
l Opening the rack diagram
l Re-collecting an alarm
Other Functions
The following describes additional fault management functions available in the NetNumen
U31 system:
l Managing alarm rules
l Managing alarm handling suggestions
l Redefining alarm severity levels
l Managing alarm boxes
l Customizing alarm codes, possible causes, alarm forwarding templates, and alarm
prompts
l Merging intermittent alarms
5-3

5.3 Performance Management

The performance management functions enable users to monitor and analyze network
performance. The system collects performance data from managed NEs in the entire
network and provides operators with detailed data for network planning, business
analysis, and network optimization. In addition, operators can detect potential problems
in equipment and operation by analyzing the performance data.
The NetNumen U31 system provides the following performance management functions:
Measurement Task Management

A measurement task specifies the required information for collecting specific performance
data, including data collection mode, NE type, measured object type, performance object,
NE location, measured object, and collection period. After a measurement task is created,
the system collects performance data in accordance with a particular task scheduling rule
and the collection granularity defined in the task, and stores the data in the database.
Performance Data Query

Users can query performance data stored in the database by different conditions, and view
the query result displayed in different modes.
Counter and Index Management

The system defines basic counters and indexes for performance management. In addition
to viewing the information of counters and indexes, users can customize or import new
indexes as required. A user-defined index can be modified, exported, and deleted.
Threshold Task Management

A threshold task can be created for monitoring the measured performance data during
a preset period. When the calculation result of a performance object exceeds the
corresponding preset threshold, the system raises a threshold crossing alarm.
Template and Template Task Management

Two types of templates can be defined in the system for performance data query: common
template and query template.
l A common template predefines all query conditions except NE location and Measured
Object (MO) location, which may be different in actual queries. Users need to select
NE location and MO location when using the template for performance data query.
l A query template predefines all query conditions, including indexes to be queried,
measured objects, and query period. By using an appropriate query template, users
can quickly query performance data at any time without setting the same query
conditions repeatedly.
5-4

A query template or common template can be used to schedule a performance data query
task (template task). The system will periodically query required performance data in
accordance with the template and task schedule.
Performance Data Monitoring

The system supports monitoring the latest data of specific indexes or counters of specific
NEs.
Performance Data Integrity Verification

The system provides the function of performance data integrity report as an assistant for
verifying the integrity of collected performance data. By using this function, users can
verify the integrity of performance data of each measurement type stored in the database
to locate the period(s) during which some performance data is absent.
5.4 Security Management

The purpose of security management is to ensure legal use of the system. The NetNumen
U31 system provides security control on security management operations through
appropriate relationship between users and roles, prevents illegal users from accessing
the system through login authentication, and provides security control on user operations
through operation authentication.
The system supports the following management operations for system security.
Role Management
A role specifies the management permissions for a user group, including operation
permissions and managed resources.
Users can create, modify, duplicate, and delete a role within the scope of authority assigned
by the system.
Role Set Management

A role set is a collection of roles. The permissions of a role set involves those of all roles
in the role set.
Users can create, modify, duplicate, and delete a role set after logging in to the system
with a user account granted with the operation permissions.
User Management
User management is the most important part of security management. The user
management functions enable the administrator to manage users of the system. The
following operations are supported:
l Creating a user
l Querying a user
5-5

l Modifying a user
l Assigning operation authorities to a user
l Setting the working period for a user
l Deleting a user
l Prohibiting a user
A created user can log in to the system with corresponding user name and password, and
perform network management operations within the scope of assigned authorities.
Department Management
A department can be specified to simulate an actual administrative department for
convenient management of users.
Security Domain Management

Security Domain Management manages multiple EMSs, which fall into higher-layer system
and lower-layer system:
l A higher-layer system has the security domain management subsystem.

l A lower-layer system will be connected to the security domain management
subsystem.
The users of an EMS can manage roles and logs in a higher-layer system and its
lower-layer systems. When creating users for a lower-layer system, you can assign roles
in a lower-layer system to the created users.
5.5 Log Management

The log management functions enable the system administrator to trace operational status
of the system, locate system faults, and trace the situation of users. A common user,
meaning a user other than the administrator, can also know the operational status of the
system through log management by reviewing previous operations.
The system provides three types of logs: operation log, security log, and system log.
l Operation logs record operation information of users.
l Security logs record login information of users.
l System logs record the completion status of system tasks on the server.
The following log management functions are supported:

l Querying logs by type
l Querying logs by conditions
l Exporting logs as files to a remote log server, either manually or by customizing an
exporting task
5-6

5.6 Maintenance Management

Task Management
The NetNumen U31 system predefines multiple periodic maintenance tasks for data
backup and deletion and supports customizing periodic tasks through MML commands.
The following describes these tasks:
l Historical data backup tasks
The historical data backup tasks back up and delete historical data in the database
periodically, such as log data, performance data, and alarm data, to maintain the
database capacity.
l Configuration data backup task
The configuration data backup task backs up the basic data of the system periodically,
meaning all data except table structures and historical data.
l Version and database backup tasks
The version and database backup tasks back up the entire database and the file
system (version files, configuration files, and runtime files) periodically.
l File clean-up tasks
The file clean-up tasks clears unnecessary data backup files and result files generated
by other management operations to maintain the hard disk capacity.
l Alarm background task
The alarm background task automatically acknowledges historical alarms that are
older than the specified number of days.
l MML tasks
An MML task can be scheduled by users to perform specific actions periodically in the
system.
System Backup and Restoration

The NetNumen U31 system supports the following manual backup and restoration
operations:
l Backup operations
à Backing up the entire database
à Backing up the basic data
à Backing up version files, configuration files, and/or runtime files
à Backing up and deleting log data
à Backing up and deleting alarm data
à Backing up and deleting performance data
l Restoration operations
5-7

à Restoring log data

à Restoring alarm data
à Restoring performance data
System Monitoring
The system monitoring functions enable users to maintain and manage the application
server and the database of the NetNumen U31 system.
l Application server monitoring
Users can view the server information and monitor the server performance, including
the real-time CPU usage, memory usage, and the hard disk space.
The system collects real-time performance data during each monitoring period,
compares the collected data with the preset thresholds, and decides whether to raise
an alarm.
l Database monitoring
Users can view the basic information of the database and the information of various
database resources, including table spaces, data tables, and processes.
The system can monitor the hard disk space of the database and specific table spaces
during a preset monitoring period. When the size of the used disk space exceeds the
preset threshold, the system raises an alarm.
IT Device Monitoring
The NetNumen U31 system can monitor various IT devices, including servers, databases,
routers, switches, clusters, and storage devices. The NetNumen U31 system detects the
operating status of an IT device by polling the device, and displays the performance data
of the IT device on the client GUI after processing the received trap messages. If an
exception or threshold crossing event is detected, an alarm is raised and displayed.
5.7 Command Line Terminal

The command line terminal is a command line tool through which users can enter single
commands or batch commands to perform management functions. Users can use the
command line terminal on a client Graphical User Interface (GUI), or access the terminal
through Telnet.
The command line terminal provides the following functions:
l Executing a single command
A single command is executed to perform a single action on a managed object, such
as create a managed object, delete a managed object, or refresh a view.
l Executing a batch of commands
A batch of commands are executed to perform continuous maintenance operations
on managed objects.
5-8

l Providing help information

With an online command help, users can conveniently obtain command syntax and
parameter requirements prior to modifying or adding command parameters.
5.8 Wireless Configuration Application

The NetNumen U31 system provides a wireless configuration application module that
supports configuration and maintenance operations involving multiple NEs in a radio
access network. Such configuration or maintenance operations cannot be independently
completed by separate OMMs of these NEs. The wireless configuration application
module can perform configuration or maintenance operations on multiple NEs in a
centralized manner.
The wireless configuration application module provides the following functions:
l Interconnection parameter management
l NE relation management
l NE stability management
l Base station status management
l Base station priority management
l Site transfer
l Inter-NE import and export of configuration data
l Neighbor cell relation verification
l Consistency verification of user labels
l Cell status management
l Cell broadcast management
l Configuration data collection
l Radio configuration data import
l GSM BCCH frequency scheduling tool
l TD carrier frequency maintenance management
5.9 Network Element Management

The Network Element (NE) management functions enable users to perform the operations
that are not directly supported by the NetNumen U31 system. After the NE management
is enabled, the NetNumen U31 system links to the operation and maintenance module of
the corresponding NE and displays the operation window on the client, on which users can
perform configuration and maintenance operations.
For available NE management functions of different radio access systems, refer to Table
5-1.
Table 5-1 Network Element Management Functions
System Function
UMTS Configuration management, diagnosis test, and software version

management
5-9

System Function
GSM Configuration management, software version management, dynamic data

management, cell broadcast management, diagnosis test, and base station
software version management
LTE-TDD Configuration management, diagnosis test, batch configuration management,

dynamic data management, alarm filtering rule setting, tool management,
base station version management, and AISG device management
LTE-FDD Configuration management, diagnosis test, batch configuration management,

dynamic data management, alarm filtering rule setting, tool management, data
tracking, base station version management, and AISG device management
TD-SCDMA Configuration management, diagnosis test, software version management,

dynamic data management, batch configuration management, alarm filtering
rule setting, data tracking, and base station version management.
Note:
l UMTS: Universal Mobile Telecommunication System
l GSM: Global System for Mobile communication
l LTE-TDD: Long Term Evolution-Time Division Duplex
l LTE-FDD: Long Term Evolution-Frequency Division Duplex
l TD-SCDMA: Time Division-Synchronization Code Division Multiple Access
l AISG: Antenna Interface Standards Group
5.10 SON Functions

The Self-Organizing Network (SON) functions allow an LTE network to automatically check
and handle network problems and maintain the best operating status of the network. The
following strategies can be configured in the NetNumen U31 system to implement SON
functions for an LTE network:
l X2 strategy for establishing X2 connections between eNodeBs
l ANR strategy for automatic setting of neighbor relations
l PCI strategy for eliminating PCI conflicts between cells
l PnP strategy for automatic initiation upon power-on of eNodeBs
l MRO strategy for automatic modification of handover-related parameters of cells
l RO strategy for self-optimization of resources
l ES strategy for energy saving of cells
l MLB strategy for self-optimization of cell load
l Self-healing strategy for improving service capacity of networks by decreasing the
sleep cells
5-10

l CMP strategy for adjusting the home relationship among cells and modules of the
CMP board in accordance with the GSM system load and supporting automatic
adjustment for load balancing.
l License strategy for automatically implementing dynamic carrier configuration in
the network in accordance with the traffic condition, reducing the number of carrier
licenses, and reducing the workload and costs in manual carrier capacity expansion.
5.11 Integrated Configuration Management

NE configuration requires frequent optimization and adjustment during network
engineering and maintenance. The integrated configuration management (ICM) function
is designed to simplify the configuration process in the entire network.
The ICM module is specific for saving, managing, checking, and transforming configuration
data of all devices in the entire network. Users can create planning areas, export the
data in the planning areas to templates, and use a network optimization and planning tool
to modify the data. Users can also import the configuration data optimized manually or
automatically by a network optimization and planning tool, and issue the imported data to
each NE to take effect.
The ICM module compares the data in the existing network, planned data, and backup
data in the planning areas. The comparison result can provide reference for data planning
and configuration.
In addition, the ICM module provides the site transfer function that transfers the related
ground parameters and radio parameters from a source site to a destination site.
5.12 Inventory Management

The inventory management allows users to collect and manage software and hardware
information in a network in a unified manner. The inventory management functions
are divided into three categories: inventory management, spare parts and repair parts
management, and inventory query and statistics.
Inventory Management
l Collecting hardware and software information in the entire network
l Synchronizing inventory data manually or automatically to obtain the latest hardware
and software information in the network
l Adding and modifying inventory data manually
l Importing and exporting inventory data
Spare Parts and Repair Parts Management

l Managing spare parts and changing the statuses of spare parts
l Recording maintenance information
l Querying board maintenance records
5-11

Inventory Query and Statistics

l Querying inventory data by query conditions
l Querying the usage information of specific software
l Querying board replacements
l Counting hardware inventories by type or object
5.13 Version Management

The version management functions are divided into two categories: software version
management and upgrade management.
Software Version Management

The software version management allows users to register and maintain software versions
of all EMSs and NEs that are connected to the NetNumen U31 system. The registered
software versions can be used for upgrade management.
The following software version management functions are available:
l Refreshing the resource tree to obtain the latest information of versions
l Registering software versions
l Querying software versions
Upgrade Management
The upgrade management allows users to implement remote software upgrade for the
managed EMSs and NEs. Compared with the upgrade mode that requires maintenance
personnel to perform operations on site, the remote upgrade through the NetNumen
U31 system simplifies the upgrade procedure, improves the upgrade success ratio, and
reduces the upgrade time.
The following upgrade management functions are available:
l Upgrading the software of one or more EMSs and NEs in batches
l Creating, starting, suspending, and deleting upgrade tasks
l Customizing upgrade steps in upgrade tasks
l Monitoring upgrade process and displaying upgrade progress
l Highlighting different task statuses in specific colors
l Providing upgrade results and reports
5.14 Remote Upgrade Management

Remote upgrade is a proxy program resided on the OMM server during the OMM upgrade
process. It is used for receiving EMS instructions and executing OMM upgrade operations.
l The task mechanism is the core mechanism in remote upgrade. All upgrades are
executed as tasks.
5-12

l The attributes of a task include upgrade parameters, upgrade objects, and upgrade
steps. Each upgrade object corresponds to a subtask, and all subtasks have the same
upgrade steps.
l A task supports operations including creation, deletion, modification, and confirmation.
l Upgrade operations use subtask as the minimum granularity, and support batch op-
erations on multiple subtasks.
l Subtasks support operations including starting, continuing, retrying, stopping,
cancelling, and rollback.
A base station upgrade task can include multiple upgrade objects, that is, multiple
subtasks. For upgrade objects (OMMR/OMMB/RNC) outside the base station, one task
can only include one upgrade object, that is, a single subtask.
5-13

5-14

Chapter 6
Interfaces and Protocols
Table of Contents
Internal Interfaces ......................................................................................................6-1
Southbound Interfaces ...............................................................................................6-1
Northbound Interfaces ................................................................................................6-1
6.1 Internal Interfaces

The internal interfaces are interfaces between the server and clients of the NetNumen U31
system, which support TCP/IP communication over a Local Area Network (LAN) or Wide
Area Network (WAN) with a bandwidth not lower than 256 kbps.
6.2 Southbound Interfaces

The southbound interfaces are communication interfaces between the NetNumen U31
system and OMMs of managed NEs, which support the adaptation of data in different
formats during data transmission.
The supported interface protocols include MML, FTP, SFTP, and SOCKET.
6.3 Northbound Interfaces

The northbound interfaces are interfaces between the NetNumen U31 system (EMS) and
a Network Management System (NMS). The northbound interfaces comply with special
interface standards that specify the information model, technical modes and functions for
connection between the EMS and the NMS. The use of northbound interfaces provides a
basis for centralized network management and maintenance.
Note:
The supported northbound interfaces may vary with different radio access systems
managed by the NetNumen U31 system.
The following lists all northbound interfaces supported by the NetNumen U31 system:
l CORBA northbound alarm interface
l CORBA northbound configuration interface
l CORBA northbound performance interface
6-1

l CORBA northbound inventory interface

l SNMP northbound alarm interface
l Socket northbound alarm interface
l FTP northbound configuration interface
l FTP northbound performance interface
l FTP northbound inventory interface
l FTP northbound alarm interface
6.3.1 CORBA Northbound Interfaces

CORBA Overview
The Common Object Request Broker Architecture (CORBA) is an open,
client/server-based and object-oriented industrial standard. The CORBA specifies a set
of communication protocols between objects, which enables the interaction between
the objects that comply with the CORBA protocols, regardless of language, device,
or operating system. Any application systems that provide CORBA interfaces can
interconnect with each other easily.
The CORBA consists of the following parts:
l Object request broker
The Object Request Broker (ORB) is the basis for constructing distributed object
applications, and inter-operability of applications in heterogeneous or homogeneous
environment. The ORB receives and transmits requests and responses transparently
in a distributed environment.
l Object service
The object service is a set of basic objects that can be used to implement and use
objects. The object service is independent of the application domain.
l Public facility
The public facility provides users with a set of interfaces for service sharing, such as
system management, compound document and E-mail.
l Application interface
The application interface is used for application extension, which is similar to the
application presentation layer.
l Domain interface
The domain interface is provided for services in the application domain.
CORBA Northbound Interfaces

The NetNumen U31 system supports the following four types of CORBA northbound
interfaces:
l CORBA northbound alarm interface
l CORBA northbound configuration interface
6-2

Chapter 6 Interfaces and Protocols
l CORBA northbound performance interface

l CORBA northbound inventory interface
CORBA Northbound Alarm Interface

The CORBA northbound alarm interface supports the following functions:
l Reporting alarms
l Synchronizing alarms
l Acknowledging alarms
l Unacknowledging alarms
l Acquiring the number of alarms
l Adding alarm description
l Clearing alarms
l Reporting an alarm occurrence notification
l Reporting an alarm clearing notification
l Reporting an alarm change notification
l Reporting a notification of potential wrong alarms
l Notifying the change of alarm acknowledgement status
l Reporting the addition of alarm description
l Reporting the reestablishment of alarm information list
CORBA Northbound Configuration Interface

The CORBA northbound configuration interface supports the following functions:
l Basic configuration functions
Creating, deleting, querying and modifying configuration information
l Notifying the change of configuration information
When the configuration of an NE changes, NetNumen U31 notifies the NMS of the
configuration information change, including object creation, object deletion, or the
change of attribute values.
l Synchronizing configuration information
When the network configuration changes, a synchronization process can be initiated
to synchronize the latest configuration from the NetNumen U31 to the NMS.
CORBA Northbound Performance Interface

The CORBA northbound performance interface supports the following functions:
l Performance collection management function set
à Creating collection activities
à Stopping collection activities
à Suspending collection activities
à Restoring collection activities
6-3

à Querying collection activity parameters

à Re-collecting performance data
à Reporting performance data
à Reporting the status change of collection activities
l Performance threshold management function set
à Creating performance thresholds
à Deleting performance thresholds

à Suspending performance thresholds
à Restoring performance thresholds
à Querying performance threshold parameters
à Reporting performance threshold-crossing alarms

à Reporting the status change of performance thresholds
CORBA Northbound Inventory Interface

The NetNumen U31 system can obtain a detailed inventory of software and hardware
resources in the managed network, including the physical location of equipment (building,
floor, room, rack, shelf, slot, port, and serial number), electronic serial numbers, firewall
level, and software level. The wireless configuration application module enables users
to query hardware information of managed NEs, and the software version management
function enables users to query software information.
The NetNumen U31 system transfers inventory information in XML or CSV file format to
an NMS through the CORBA northbound inventory interface or FTP northbound inventory
interface.
6.3.2 FTP Northbound Interface

The FTP northbound interfaces are used for file transfer between the NetNumen U31
system and an NMS. After selecting specific data in the NetNumen U31 system, users
can transfer the data to a particular file that will be periodically transferred to the NMS
through FTP, or save the data in a particular path as a file that will be periodically acquired
by the NMS.
Three types of FTP northbound interfaces are available to support the transfer of
configuration data, performance data, and inventory data in XML or CSV file format from
the NetNumen U31 system to an NMS.
In addition, the NetNumen U31 system supports the Secure File Transfer Protocol (SFTP)
developed on Secure Shell SSH, which ensures file transmission security over northbound
interfaces.
6-4

6.3.3 SNMP Northbound Interface

The Simple Network Management Protocol (SNMP) is an application-layer protocol
used for management information exchange between network equipment. As a part
of TCP/IP stack, the SNMP is based on the User Datagram Protocol (UDP), which
specifies the encapsulation format of data units. The SNMP has been widely used in the
telecommunications field due to its simple and practical characteristics, and has become
the most widely used management frame of TCP/IP networks.
The SNMP protocol has three versions: SNMPv1, SNMPv2c and SNMPv3.
SNMP Network Management Model

The network management model of SNMP consists of the following four parts:
l Management node
The management node runs the SNMP agent program. It maintains a local database,
describes the status and history of the node, and influences the node operation.
l Management station
The management station runs a special network management program (manager) to
implement communication with the SNMP agent on the managed node, and maintains
the management information base.
l Management information base
Each management station uses one or more variables to describe its status. These
variables are objects that form the Management Information Base (MIB).
l Management protocol
The management protocol is used by the management station to query and modify
the status of the managed node. The management node can use the management
protocol to send Trap messages to the management station.
SNMP Message Types

There are five types of SNMP messages:
l Get_Request
The SNMP manager uses a Get_Request message to search for information in a
network device with SNMP agent.
l Get_Next_Request
Get_Request and Get_Next_Request messages can be used to get an object in
a table, where Get_Request is used for getting a specific object in the table and
Get_Next_Request is used for getting the next object in the same table.
l Get_Response
The SNMP agent responds to the Get_Request message with a Get_Response
message. It exchanges information with the SNMP manager, such as system name,
6-5

how long the system operates properly after starting automatically, and the number
of network interfaces in the system.
l Set_Request
The SNMP agent can use the Set_Request message to remotely configure the
parameters of a device.
l Trap
Trap is a non-request message sent by the SNMP agent to the management station.
It is used to notify the server of a particular event.
Application of SNMP in an NMS

The SNMP protocol can provide SNMP manager and SNMP agent functions in a network
management system, see Figure 6-1.
Figure 6-1 Application of SNMP in an NMS
On one hand, the NetNumen U31 system serves as an SNMP Manager when managing
a network element, which acts as an SNMP agent. On the other hand, the NetNumen
U31 system serves as an SNMP agent when an NMS (SNMP manager) manages the
NetNumen U31 system through SNMP.
SNMP manager functions and SNMP agent functions have no coupling relation. The
NetNumen U31 provides SNMP manager and SNMP agent functions in accordance with
the actual requirements.
6-6

Functions of SNMP Northbound Alarm Interface of the NetNumen U31

The SNMP northbound alarm interface complies with the IETF specification. It provides
the following functions for an NMS:
l Reporting alarms
l Clearing reported alarms
l Getting a list of alarms
l Getting the number of alarms
l Querying and acknowledging alarms
l Clearing alarms
l Querying and modifying alarm comments
l Filtering reported alarms
6.3.4 SOCKET Northbound Interface

The SOCKET northbound alarm interface is used to transfer alarm information to an NMS
through TCP/IP. It provides the following functions:
l Reporting heartbeat messages

l Reporting alarm events
l Clearing reported alarm events
l Synchronizing alarms
l Filtering reported alarms
6-7

6-8

Chapter 7
Networking Modes
Table of Contents
Local Networking Mode ..............................................................................................7-1
Remote Networking Mode ..........................................................................................7-2
Remote Client Networking Mode ................................................................................7-3
7.1 Local Networking Mode

The local networking mode is the simplest and the most common networking mode used by
centralized network management systems. In this networking mode, the NetNumen U31
server and clients are located in the same LAN and are connected with each other through
the Ethernet, and the server can connect managed NEs through transmission networks.
Few network devices are needed for the local networking mode. In accordance with the
quantity of hosts (the number of NetNumen U31 servers and clients), proper 10/100 Mbps
adaptive switches with enough ports and necessary twisted pairs (Ethernet cables) are
required to construct a network management network.
Figure 7-1 shows the topology of the local networking mode.
7-1

Figure 7-1 Local Networking Mode
7.2 Remote Networking Mode

In the NetNumen U31 system using a remote networking mode, the clients are located
remotely from the NetNumen U31 server. Different remote networking modes have similar
network topology and follow the same networking principle. An appropriate mode should
be used depending on the actual networking requirements.
In a remote networking mode, the system gets access to a WAN through special
transmission equipment, which is connected to routers through standard interfaces.
Routers, switches, the NetNumen U31 server, and local clients are located in the same
LAN.
The remote networking mode can be implemented over different transmission mediums:
DDN dedicated line, E1 line, and HDSL.
Figure 7-2 shows an example of the remote networking mode. The NetNumen U31 server
and NEs are located in the same LAN. The remote clients connect to the local NetNumen
U31 server through DCN.
7-2

Chapter 7 Networking Modes
Figure 7-2 Remote Networking Mode Over DCN
7.3 Remote Client Networking Mode

In the remote client networking mode, the NetNumen U31 clients and managed NEs are
located in a LAN while the NetNumen U31 server is located in a remote site. The clients
connect to the remote server through DCN and manage the local NEs through the server.
Figure 7-3 shows a remote client networking example.
7-3

Figure 7-3 Remote Client Networking Mode
7-4

Chapter 8
Environmental Requirements
Table of Contents
Temperature and Humidity Requirements...................................................................8-1
Grounding Requirements ...........................................................................................8-2
Electromagnetic Interference Prevention ....................................................................8-3
Lightning Protection Requirements.............................................................................8-3
Electrostatic Discharge Prevention .............................................................................8-4
Other Requirements ...................................................................................................8-5
8.1 Temperature and Humidity Requirements

Too high or too low temperature or humidity may have a negative impact on equipment
life. For example,
l The equipment life is halved when the temperature in the equipment room is 50℉
(10℃) higher than the ordinary temperature. Too low temperature may cause poor
performance of optical and crystal components.
l Too high relative humidity for a long time degrades the properties of insulating
materials and even causes current leakage. It also results in the corrosion of metal
components in equipment.
Too low relative humidity for a long time may cause the shrinkage of insulating washers
and result in the loosening of fastening screws, which increase the possibility of strong
electrostatic discharge and cause damage on CMOS circuits in equipment.
To maintain the temperature and humidity in the equipment room within the normal ranges,
the air conditioners in the equipment room should operate properly.
For the requirements for the temperature and humidity in the equipment room where the
system is located, refer to Table 8-1.
Table 8-1 Temperature and Humidity Requirements
Item Requirement
Temperature Long-term operating condition 50℉ to 86℉

(10℃ to 30℃)
Short-term operating condition 32℉ to 113℉

(0℃ to 45℃)
8-1

Item Requirement
Relative Humidity Long-term operating condition 30% to 85%
Short-term operating condition 20% to 90%
• The temperature and humidity of the operating environment inside the equipment room is measured
15.8 inch (0.4 m) in front of the equipment and 59.1 inch (1.5 m) above the floor when there is no
protective plate in front of or at the back of the equipment rack.
• The short-term operating condition is that the consecutive operation period does not exceed 48 hours
and the accumulative operation period within a year does not exceed 15 days.
8.2 Grounding Requirements

Grounding plays an important role for ensuring a good electromagnetic condition in
the operating environment of the main and auxiliary devices of the system and good
anti-interference capability of the devices. The grounding of the system must meet the
following requirements:
l A joint grounding mode is adopted for the system, meaning that the working ground,
protection ground of all telecommunications devices, and the lightning-proof ground
of the building are connected to the same set of grounding electrodes.
l The ground resistance of the lightning protection device in the equipment room is
less than 1Ω when the device adopts a joint grounding mode, and is less than 10Ω
when the device adopts an independent grounding mode. The factors that may impact
the ground resistance should be taken into consideration, including the soil condition,
temperature, humidity, the resistance of the ground post, and the cables used for
grounding.
A ground resistance measurement is required prior to system commissioning. If
the ground resistance does not meet the specified requirement, the commissioning
should be suspended. A written promise claiming responsibility for any future
grounding-related problems is required for ZTE’s approval to continue the
commissioning regardless of the unsatisfactory ground resistance.
After the system is put into operation, the ground resistance should be measured
and recorded regularly. If the ground resistance increases greatly, proper measures
should be taken to reduce the ground resistance.
l At a place with unfavorable soil condition, proper chemical agents (such as

acrylamide) should be applied to the soil around the ground post to reduce the soil
resistivity and the contact resistance between the soil and the ground post because
the ground resistance varies greatly with different soil types.
l The ground post is buried deeper or chemical agents are applied around the ground
post to get a satisfactory ground resistance when the temperature is below 32℉ (0℃)
or the humidity is inadequate because too low temperature or humidity results in a
great change in the ground resistance.
l The ground post is an angle iron post with the length at least 78.7 inch (2 m). If
possible, a ground grid is preferred.
8-2

Chapter 8 Environmental Requirements
l A copper-core cable with the cross-section area of at least 0.078 square inch (50 mm2)
is used to connect the ground post and the ground bolt on the principal device of the
system. If a cable longer than 1968.5 inch (50 m) is needed for the connection, a
cable with a greater cross-section area must be used.
l Tin plating or hot-dip tinning processing must be performed on both ends of the cable
and the coating, varnish, oil paint and oxidized layer must be removed from the
fastening points to ensure a good contact between metal surfaces.
l Anticorrosion protection is required for all connecting pieces for grounding. A
mechanical method is required to fasten the ground bolts to ensure low-resistance
connection.
8.3 Electromagnetic Interference Prevention

The location of the equipment room must meet the following requirements:
l The equipment room is far away from high-power radio transmission stations, radar
transmission stations, and high-frequency and high-current equipment.
l The radiation to the equipment room is less than 7.62 mV per inch (300 mV/m), and
the intensity of magnetic field around the equipment room is less than 11 GS.
The following lists anti-radiation and anti-interference requirements that should be met.
l The equipment room is shielded against a definite electromagnetic radiation
interference source.
l A shield wall is installed between the principal equipment of the system and the
equipment containing a transmitter with high-frequency radiation, and separate
power supply lines are used for them.
l All the cables and conductor wires that are routed through pipes are connected to the
ground. The shielding layer of all cables should also be grounded.
l Signal cables and return cables are twisted for counteracting the induced voltages
generated by radiated interference on the cables.
l Power cables and signal cables are routed separately without being paralleled.
l The grounding cable of the AC power supply and that of the DC power supply are
routed separately in the equipment room.
8.4 Lightning Protection Requirements

Lightning protection is important to ensure the operation safety of the system. The
following principles should be followed during the lightning protection design:
l Effective lightning protection measures are taken in accordance with the lightning
protection requirements for Class-II civil buildings and structures when the main
building or its auxiliary facilities is higher than 590.6 inch (15 m).
l Appropriate measures are taken against direct lightning strikes and electric shocks.
In lightning-prone areas where side flash happens often, additional lightning
protection measures against side flash are required for an equipment room in high
buildings. For example, the outer metal windows of the building are connected with
8-3

down conductors, or horizontal metal straps are mounted on the outer wall at a
particular spacing.
The following lists the requirements for the main building lightning protection of the
equipment room.
l Lightning protection nets or straps are installed on the parts that are subject to
lightning.
l Overhead conductors or arrestors are installed on the top of protruding parts of the
building, such as the chimney, antenna and water tower.
l The cross-section area of down conductors for lightning protection is no less than 0.3
square inches (200 mm2) and the distance between them cannot be more than 1181.1
inch (30 m).
l Metal components of the building (such as reinforcement steel bars inside walls or
poles) are used as the down conductors for lightning protection grounding, which are
connected electrically to maintain potential equalization in the building.
l The ground resistance cannot be more than 1 Ω when a joint grounding mode is
adopted. If an independent grounding mode is adopted, the ground resistance cannot
be more than 10 Ω.
The joint grounding mode is preferable for the lightning protection grounding of the
building. In the joint grounding mode, the following ground terminals should be
connected together:
à Working ground and protection ground of telecommunications equipment,
à The lightning protection ground of the building, and
à The ground of the AC power supply system.
The joint grounding mode has a higher requirement for grounding resistance than the
independent grounding mode.
l The ground resistance depends on the minimum resistance values required by
different grounding devices because the requirement for the ground resistance
depends on the actual type of telecommunications devices. The ground resistance
required for telecommunication systems is far lower than 10 Ω.
l The outdoor cables and metal ducts are grounded before being routed into the
building.
l A proper lightning protective device is installed on the line that introduces the mains
supply into the equipment room.
8.5 Electrostatic Discharge Prevention

Accumulated static electric charge damages the components in equipment gradually,
causing intermittent failure or performance degradation of the equipment. In addition,
Electrostatic Discharge (ESD) may result in software failure, and malfunction of electric
switches and control circuits. The major sources of electrostatic induction are:
l External electrical fields, such as outdoor high-voltage power transmission lines and
lightning.
8-4

Chapter 8 Environmental Requirements
l Internal systems, such as indoor environment, floor material and cabinet structure.
l Electrostatic discharge caused by direct contact between human body and equipment.
The following lists the ESD prevention requirements for minimizing the damages incurred
by electrostatic discharge:
l The equipment is grounded properly.
l An ESD preventive floor is laid and properly grounded in the equipment room.
l Users must wear an ESD wrist strap and connect it to the ESD jack on the equipment
rack prior to any operation on the equipment.
8.6 Other Requirements

Cleanness Requirements
The cleanness of the equipment room must meet the following requirements:
l The percentage of fresh air in the equipment room is at least 5%, ensuring the
freshness of the air.
l In addition to percentage of dust and the size of dust particles, there are also strict
requirements on the concentration of salt, acid and sulfide in the air, which may cause
the erosion of metal and aging of particular parts.
l Harmful gases, such as SO2 and H2S, is kept out of the equipment room to protect
the health of the maintenance personnel.
l The concentration of dust particles with a diameter larger than 1.97×10-4 inch (5 μm)
is equal to or smaller than 0.49 particles per cubic inches (3×104 particles/m3).
Erosive gases, smog and smoking are prohibited in the equipment room.
Quakeproof Requirements
The earthquake resistance level of the equipment room building must be higher than that
required for the other common buildings by one level. If the building where the equipment
room is located do not meet the requirement for earthquake resistance, a consultation with
the institute designing this building is required to obtain a reinforcement solution before
organizing labours to reinforce the building.
Telecommunications equipment must be strong enough to resist a magnitude 7
earthquake.
Illumination Requirements
The following lists the requirements for illumination in the equipment room:
l Incandescent lamps or emergency lighting facilities are installed at proper locations
between racks so that the environment is bright enough for equipment installation and
maintenance.
l Long-term exposure of the equipment to sunlight and lamp-light should be avoided to
prevent the ageing and deformation of circuit boards and components due to ultra-high
temperatures.
8-5

l Colored window glass, and dark and nontransparent curtains are recommended.
l Fluorescent lamps inlaid in the ceiling are used as the major illuminators in the equip-
ment room. The average illumination intensity is kept within the range from 150 lx to
200 lx.
Fire Prevention
The equipment room building must meet the requirements of the fire prevention regulation
for the building, including:
l The building is equipped with fireproof facilities, which are placed at proper positions
for easy access.
l Qualified fire-fighting passages are reserved.
l "No Open Flame Area" signs are posted at proper places.
l No dangerous articles are stored in the equipment room, such as flammables and
explosives.
l Warnings such as "No Smoking" or "No Smoking and Open Flames" are posted at
conspicuous places.
l Effective water supply facilities are available, and the fire-fighting water reserve should
be sufficient for 2 hours use.
l No water supply pipes, or rain and water drainage pipes are laid cross the equipment
room.
l Fire hydrants are placed outside of the equipment room.
Atmospheric Pressure
The atmospheric pressure in the equipment room of the NetNumen U31 system must be
within the range from 70 kPa to 106 kPa.
8-6

Figures
Figure 1-1 Network Management Model ................................................................... 1-1
Figure 2-1 Single-Server System .............................................................................. 2-2
Figure 2-2 High Availability System........................................................................... 2-3
Figure 2-3 Disaster Recovery System....................................................................... 2-4
Figure 4-1 Hierarchical Model ................................................................................... 4-1
Figure 4-2 Embedded Remote Client ........................................................................ 4-3
Figure 6-1 Application of SNMP in an NMS............................................................... 6-6
Figure 7-1 Local Networking Mode ........................................................................... 7-2
Figure 7-2 Remote Networking Mode Over DCN ...................................................... 7-3
Figure 7-3 Remote Client Networking Mode.............................................................. 7-4

Figures
II

Tables
Table 3-1 Server Hardware Configuration (IBM Workstation) .................................... 3-1
Table 3-2 Server Hardware Configuration (Sun Workstation) .................................... 3-2
Table 3-3 Server Hardware Configuration (Distributed Mode).................................... 3-2
Table 3-4 Server Software Configuration (IBM Workstation)...................................... 3-2
Table 3-5 Server Software Configuration (Sun Workstation)...................................... 3-3
Table 3-6 Server Software Configuration (Distributed Mode) ..................................... 3-3
Table 3-7 Client Hardware Configuration................................................................... 3-3
Table 3-8 Client Software Configuration .................................................................... 3-4
Table 5-1 Network Element Management Functions ................................................. 5-9
Table 8-1 Temperature and Humidity Requirements.................................................. 8-1
III

Tables
IV

Glossary
3GPP
- 3rd Generation Partnership Project
AC
- Alternating Current
AISG
- Antenna Interface Standards Group
AIX
- Advanced Interactive Executive
ANR
- Automatic Neighbor Relation
BCCH
- Broadcast Control Channel
CCSA
- China Communication Standards Association
CMOS
- Complementary Metal-Oxide-Semiconductor
CORBA
- Common Object Request Broker Architecture
CPU
- Central Processing Unit
CSV
- Comma Separated Value
DC
- Direct Current
DCN
- Data Communications Network
DDN
- Digital Data Network
EML
- Element Management Layer
EMS
- Element Management System
ERT
- Embedded Remote Terminal

ESD
- Electrostatic Discharge
FDD
- Frequency Division Duplex
FTP
- File Transfer Protocol
GSM
- Global System for Mobile Communications
GUI
- Graphical User Interface
HA
- High Availability
HDSL
- High-data-rate Digital Subscriber Line
ICM
- Integrated Configuration Management
IETF
- Internet Engineering Task Force
IP
- Internet Protocol
ISO
- International Organization for Standardization
IT
- Information Technology
ITU-T
- International Telecommunication Union - Telecommunication Standardization
Sector
LAN
- Local Area Network
LTE
- Long Term Evolution
MIB
- Management Information Base
MML
- Man Machine Language
MO
- Measured Object
MRO
- Mobility Robustness Optimization
VI

Glossary
NE
- Network Element
NEL
- Network Element Layer
NML
- Network Management Layer
NMS
- Network Management System
NTP
- Network Time Protocol
OMM
- Operation & Maintenance Module
ORB
- Object Request Broker
PC
- Personal Computer
PCI
- Physical Cell Identity
PnP
- Plug and Play
SFTP
- Secure File Transfer Protocol
SNMP
- Simple Network Management Protocol
SON
- Self-Organizing Network
SSH
- Secure Shell
TCP
- Transmission Control Protocol
TD-SCDMA
- Time Division-Synchronization Code Division Multiple Access
TDD
- Time Division Duplex
TMF
- Telecommunication Management Forum
TMN
- Telecommunications Management Network
VII

UDP
- User Datagram Protocol
UMTS
- Universal Mobile Telecommunication System
VCS
- Veritas Cluster Server
VIP
- Very Important Person
VVR
- Veritas Volume Replicator
WAN
- Wide Area Network
WLAN
- Wireless Local Area Network
WiMAX
- Worldwide Interoperability for Microwave Access
XML
- Extensible Markup Language
eNodeB
- Evolved NodeB
VIII

SJ-20140724091740-002-NetNumen U31 R18 (V12.13.50) Product Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20140724091740-002-NetNumen U31 R18 (V12.13.50) Product Description

Uploaded by

Copyright:

Available Formats

NetNumen U31 R18

Unified Element Management System

Revision No. Revision Date Revision Reason

R1.0 2014-07-30 First edition

Serial Number: SJ-20140724091740-002

Publishing Date: 2014-07-30 (R1.0)

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

Chapter 2 System Architecture ................................................................. 2-1

Chapter 3 Configuration Requirements ................................................... 3-1

Chapter 4 System Principles ..................................................................... 4-1

Chapter 5 Product Functions .................................................................... 5-1

Chapter 6 Interfaces and Protocols .......................................................... 6-1

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

Chapter 7 Networking Modes .................................................................... 7-1

Chapter 8 Environmental Requirements .................................................. 8-1

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

What Is in This Manual

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

Note: provides additional information about a certain topic.

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

1.1 Unified Element Management System

Figure 1-1 Network Management Model

The NetNumen U31 system provides the following management functions:

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

Integrated Network Management

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

2.1 Hardware Architecture

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

Figure 2-1 Single-Server System

High Availability System

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

Figure 2-2 High Availability System

Disaster Recovery System

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

Figure 2-3 Disaster Recovery System

2.2 Software Architecture

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

3.1 Server Configuration Requirements

Table 3-1 Server Hardware Configuration (IBM Workstation)

Hardware Configuration 1 (for a Network with Configuration 2 (for a Network with

Server Model: IBM P740 Model: IBM P740

Standby server Model: IBM P720 Model: IBM P720

Tape TS3310 (11×1.5 TB) TS3310 (20×1.5 TB)

SJ-20140724091740-002|2014-07-30 (R1.0) ZTE Proprietary and Confidential

Table 3-2 Server Hardware Configuration (Sun Workstation)

Hardware Configuration 1 (for a Network with Configuration 2 (for a Network with

Server Model: Sun T4–1 SUN T4–1

Standby server Model: Sun T4–1 Model: Sun T4–1

Tape SL 150 (11×1.5 TB) SL 150 (20×1.5 TB)

Table 3-3 Server Hardware Configuration (Distributed Mode)

Managed Object Configuration

Server HP BL460c Gen8 10GB FLB CTO Blade

Disk array IBMN3220 (450 GB)

Standby server N+M cluster configuration.

Table 3-4 Server Software Configuration (IBM Workstation)

Network management software NetNumen U31 R18

Operating system AIX 6107

Database Oracle Database Enterprise Edition (64-bit) Version 11.2.0.3.0 for

HA software (optional) PowerHA