2-2 ZTE Radio Network EMS - ZTE NetNumen U31 Product Description

ZTE NetNumen U31 Product
Description
ZTE NetNumen U31 Product Description

Version Date Author Reviewer Notes
V1.0 2014/10/09 Li Xiaojuan First Release
Modify Corba interface description;

V1.11 2015/01/09 Li Xiaojuan
Modify Configuration part
2015 ZTE 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 1

TABLE OF CONTENTS
1 Overview ............................................................................................................ 4
2 Highlights........................................................................................................... 4
3 System Architecture.......................................................................................... 6
3.1 NetNumenTM U31 Product Portfolio ...................................................................... 7
3.2 NetNumenTM U31 Networking & Operation .......................................................... 8
3.2.1 LAN Networking ................................................................................................... 9
3.2.2 Remote Networking ........................................................................................... 10
3.2.3 Meta-frame Solution........................................................................................... 11
3.3 NetNumenTM U31 Server Configuration ............................................................. 12
3.4 NetNumenTM U31 Client Configuration ............................................................... 13
3.5 Northbound interface ......................................................................................... 14
3.5.1 CORBA .............................................................................................................. 14
3.5.2 DB ..................................................................................................................... 14
3.5.3 FTP .................................................................................................................... 15
3.5.4 SNMP ................................................................................................................ 15
4 Features and Functionalities .......................................................................... 16
5 System Reliability............................................................................................ 21
5.1 Backup & Restore Solution ................................................................................ 21
5.2 High Availability Solution .................................................................................... 23
5.3 Disaster Recovery Solution ................................................................................ 24
5.4 Operation Security ............................................................................................. 25
5.5 Software Reliability ............................................................................................ 25
6 Technical Specification................................................................................... 26
6.1 Performance Indices .......................................................................................... 26
6.2 Physical Dimensions .......................................................................................... 27
6.3 Power Supply..................................................................................................... 28
6.4 Environment....................................................................................................... 29
6.4.1 Grounding Requirement ..................................................................................... 29
6.4.2 Temperature and Humidity................................................................................. 29
6.4.3 Cleanliness Requirement ................................................................................... 29
6.4.4 Lighting .............................................................................................................. 30
7 Acronyms ......................................................................................................... 30
2 ZTE Confidential & Proprietary

FIGURES
Figure 3-1 NetNumen U31 Software Architecture ............................................................ 6

Figure 3-2 NetNumenTM U31 Hardware Architecture ......................................................... 7
Figure 3-3 NetNumen U31 typical Networking ................................................................. 8
Figure 3-4 LAN Networking ................................................................................................10
Figure 3-5 Remote Networking ..........................................................................................10
Figure 3-6 Meta-frame Networking.....................................................................................11
Figure 5-1 Backup & Restoration Solution .........................................................................22
Figure 5-2 High Availability Solution ...................................................................................23
Figure 5-3 Disaster Recovery Solution ...............................................................................24
TABLES
Table 3-1 NetNumenTM U31 IBM Hardware Configuration .................................................12
Table 3-2 NetNumenTM U31 SUN Hardware Configuration ................................................13
Table 3-3 Software Configuration for Server ......................................................................13
Table 3-4 Minimum Hardware Configuration for NetNumenTM U31 Client ..........................13
Table 3-5 Software Configuration for Client .......................................................................14
Table 6-1 NetNumen U31 Processing Capacity for Each RAT .......................................26
Table 6-2 Performance Indices of NetNumen U31 .........................................................27
Table 6-3 NetNumen U31 Rack Dimension ....................................................................27
Table 6-4 Typical NetNumenTM U31 requirements on Ground ...........................................27
Table 6-5 NetNumen U31 DC Power Supply Requirements ...........................................28
Table 6-6 NetNumen U31 AC Power Supply Requirements ...........................................28
Table 6-7 NetNumen U31 Power Consumption Indices ..................................................28
Table 6-8 NetNumen U31 Grounding Requirements ......................................................29
Table 6-9 Requirements on Temperature and Humidity .....................................................29
Table 6-10 Requirements on Dust Content and Particle Size .............................................29
Table 6-11 Restriction of Harmful Gas ...............................................................................30

1 Overview
TM
NetNumen U31 is ZTEs unified network operation and management system in
Network Element layer (hereinafter short as NEs) in mobile networks, capable of
managing multiple radio access technology networks simultaneously including GERAN,
UTRAN, FDD and TDD LTE radio networks.
TM
NetNumen U31 provides various managements on radio equipment such as fault
management, performance management, configuration management, software
packages management, security management, topology management, log management
and etc, which is fully compliant to the international telecommunication specifications. In
TM
addition, NetNumen U31 also provides rich optional functions such as northbound
rd
interface, meta-framing networking, Enhanced Report Management, integration with 3
party backup and restoration solutions, and CBC solutions (GERAN&UTRAN).
TM
NetNumen U31 system is developed based on ZTE s unified network management
platform architecture and adopts J2EE which is available on various operating systems
TM
which makes NetNumen U31 system have higher reliability. Services are independent
from data storage which is compatible with various types of database, and the services
development, upgrade, activation and de-activation has no impact against data storage,
TM
and it is easy to expand existing NetNumen U31 system from single mode to
multi-mode during network evolution and upgrade.
2 Highlights
NetNumen U31 is a unified element management system in radio network, capable to
provide consolidated network operation and maintenance for all ZTE equipments and
networks. It has the following benefits:
High-efficient Centralized EMS System
Centralized management of multi-RAT network equipments, it can manage GERAN,

UTRAN, FDD & TDD LTE equipments simultaneously, reducing CAPEX and OPEX.
The JAVA/J2EE platform-based design is convenient for operators to select

different hardware & software platforms.

Smoothly integration with the management system of IT/IP equipment and software
systems such as routers, Ethernet switches, firewalls, servers, OS, DB, HA to
implement centralized network management system.
Support of various types of northbound interfaces: CORBA, DB, FTP, and SNMP.
TM
NetNumen U31 can be integrated to upper-layer systems through these
interfaces, to build the BSS/OSS system.
Unified configuration management and data consistency checking functions to

guarantee configuration consistency.
Network health check and intelligent in-process inspection of full-network

equipment to lower O&M cost.
Advanced Network Security
Strict access rights control, hierarchical and role-based management strategies,

authorized network views, and complete log records.
Secure networking solutions to prevent malicious attacks with the support of all
IPSec, SSH, and SFTP protocols.
Various disaster recovery & backup solutions: the local high-availability cluster to
provide hot backup policy, and remote disaster recovery to ensure high network
data security.
LDAP interface to 4A server provides account management and accessing

authentication. NetNumen U31 supports account management via this interface
based on JDNI and LDAP V3, including account creation, modification and deletion,
right group creation, modification and deletion.
Intelligent Networking and Flexible Network O&M
GUI, MML and Web (Citrix access) modes to adapt to different application
requirements, user behavior, networking requirements, bandwidth limitations and
etc.
Daylight saving time management meets the time management requirements of

different time zones.

Various Report templates. In addition to some built-in Report templates, users can
customize their own report templates as needed.
The Enhanced Report Management (ERM) module is a flexible, rich format report
generation subsystem. It can fulfill the quick changed/complicated format report
requirements, extract data from many EMSs running fitful version, and export joint
reports.
Integrated Tools Enhancing Service Efficiency
End-to-end protocol tracing tool supports various types of NEs, multiple signaling
tracing methods and presentation modes. The end-to-end trace tools help operators
to improve daily O&M efficiency and streamline the subscriber complaint settlement
workflow, end-to-end tracing tool needs to interface with Core network, CTS can
interface with other vends Core network.
ZTE SON solution improves the operational expense (OPEX) efficiency for
multi-radio access technology (RAT) and multi-layer mobile networks, enabling
operators to increase throughput requirements and implement long-term
development in multi-RAT networks.
3 System Architecture
TM
The following figure shows NetNumen U31 software architecture:
Figure 3-1 NetNumen U31 Software Architecture

3.1 NetNumenTM U31 Product Portfolio

TM
NetNumen U31 is located in the Element Management Layer in TMN
(Telecommunication Management Network) model, integrating with the base stations in
GERAN, UTRAN, FDD & TDD LTE networks via southbound interface and integrating
with upper level 3th NMS (Network Management System) via northbound interface.
TM
NetNumen U31 employs the C/S mode, consisting of server, clients, disk array and
other transmission equipments. Alarm box are optional. The following figure shows the
TM
NetNumen U31 hardware architecture.
Figure 3-2 NetNumenTM U31 Hardware Architecture
The two servers in the architecture are in active/standby mode. The NetNumen U31
servers are from main stream vendors. The requirements of processing capacity of the
server depend on the network scale.
NetNumen U31 is a multi mode Operation & Management system, and it can manage
the following radio access networks elements simultaneously:

BSC and BTS in GSM radio network
RNC and Node B in UMTS radio network
eNodeB in FDD LTE radio network
eNodeB in TDD LTE radio network
The software of the server is multi-RAT capable, managing GERAN, UTRAN, FDD &
TDD LTE simultaneously. The northbound interface to NMS is open interface, and can
be used for integration smoothly with 3th party NMS system. The southbound interface to
radio network is proprietary interfaces.
3.2 NetNumenTM U31 Networking & Operation
NetNumen U31 deploys very flexibility to satisfy needs of various operators, it can
operate by centralized operation, Operator can manage NetNumen U31 system in
province or city.
Figure 3-3 NetNumen U31 typical Networking

Central room in Province

NetNumen U31
TCP/IP
Client Client
A City room A City
BSC/RNC
TCP/IP
Client client eNodeB NodeB
3.2.1 LAN Networking
LAN networking is the simplest and the most common networking mode. All
TM
NetNumen U31 Server, Client and radio network equipments are placed inside one
TM
LAN. This networking mode requires NetNumen U31 and network equipments
deployed in the same physical location.
TM
The following figure shows the networking of NetNumen U31 managing BSCs and
RNCs simultaneously in a local LAN network.

Figure 3-4 LAN Networking
Few types of transmission equipment are required for LAN networking, only several
100M/1000M adaptive HUB and switches are needed.
3.2.2 Remote Networking
If some network equipments are deployed in different physical locations and the physical
locations are in different LAN, the remote networking should be adopted to inter-connect
TM
these LANs. The following figure shows one NetNumen U31 server manages three set
BSC/RNCs and one eNodeB which are deployed in three separated LANs:
Figure 3-5 Remote Networking

TM
There are three LANs in the network, and NetNumen U31 server is deployed in LAN 1.
TM
The NetNumen U31 clients in LAN 2 and LAN 3 can operate the whole GSM & UMTS
& LTE radio network via remote accessing.
3.2.3 Meta-frame Solution
Citrix provides remote access software for delivering applications over a network or
internet for enterprises, government and educational institutions. Citrix Access Suite is
the most complete solution available for providing secure, on-demand access to
TM
NetNumen U31 system anywhere, with any device, over any network. Basically Citrix
Presentation Server and Citrix Password Manager are included in the Citrix solution.
TM
The following figure shows the networking between Citrix and NetNumen U31 system
TM
to extend NetNumen U31 client to users desktop.
Figure 3-6 Meta-frame Networking
In this solution, NetNumen U31 clients are installed on the Citrix server. Citrix clients
are connected to the NetNumen U31 server through the NetNumen U31 clients.
Multiple Citrix servers can form a Farm, providing services in a joint effort so that load
balancing is achieved.

Users don't need to install NetNumen U31 clients in the local terminal, instead of a
Citrix client which is a software application with the size of 2MBytes about. An ICA
Session is created Between Citrix clients and Citrix servers, with that the Citrix clients
access the NetNumen U31 clients running on the Citrix servers and login to the
NetNumen U31 servers.
NetNumen U31 clients request many system resources. A single Citrix server,
however, allows a limited number of concurrent access requests. To solve this problem,
we choose to publish the NetNumen U31 clients on all Citrix servers in a Farm.
Therefore through the auto load balancing finally, the numbers of concurrent accesses
are enlarged greatly.
3.3 NetNumenTM U31 Server Configuration

TM
The hardware of NetNumen U31 system is the server from main vendors, such as IBM,
SUN, HP and DELL. Generally NetNumen U31 server is compatible with all types of
servers. Depending on the network scale and services, the server type, the number of
CPU, the size of hard disk and the size of memory will be different. The choice of server
and hardware should be fully verified in laboratory before commercial utilization.
For example, the following table shows verified server configuration for active
NetNumen U31 server based on IBM and SUN server.
TM
Table 3-1 NetNumen U31 IBM Hardware Configuration
Network Scale (Cells)

Server <5000 >5000 >10000 >15000 >20000
<10000 <15000 <20000 <30000
P7 740 6C32G 4.2GHzCPU
P7 740 8C128G 4.2GHzCPU

TM
Table 3-2 NetNumen U31 SUN Hardware Configuration
Network Scale (Cells)

Server <5000 >5000 >10000 >15000 >20000
<10000 <15000 <20000 <30000
SUN T4-1 8C32G 2.85GHzCPU
The following Database and Operation System is recommended.
Table 3-3 Software Configuration for Server
Object Server Configuration
Operation System AIX/Solaris/Linux
Database Oracle/SysbaseIQ
Redundancy Solution Power HA/VERITAS
TM
NetNumen U31 can manage 100,000cells using blade server.
ZTE blade server used distributed solutions, dividing into alarm module, performance
module, TOPO module and etc. This can fully utilize physical resource, and improve
handling efficiency.
3.4 NetNumenTM U31 Client Configuration
The minimum hardware configuration of Client for PC workstation is shown below:
TM
Table 3-4 Minimum Hardware Configuration for NetNumen U31 Client
Object Configuration

CPU > dual-core
Memory >= 2G
Built-in Hard Disc >=80G
TM
Software configuration for NetNumen U31 Client is shown below:
Table 3-5 Software Configuration for Client
Object Configuration
Operation System MS Windows2003 above/Linux
Document Browsing Tool MS Office2003 above/Acrobat reader
Anti-virus Software MacAfee/Norton/ Trend
3.5 Northbound interface

TM
Several options are available for NetNumen U31 system integration with NMS system,
final decision is based on actual requirements.
3.5.1 CORBA
CORBA (Common Object Request Broker Architecture) is a standard object-oriented

application program system specification established by OMG. CORBA comprises the
Object Request Broker (ORB), object service, public facilities, domain interfaces, and
application interfaces. The core of CORBA is the ORB, which provides a mechanism by
which objects can transparently send requests and receive response.
3.5.2 DB
DB is one way interface to view the data in the database, and can be used for
Performance management and Fault management (GERAN & UTRAN).
With DB interface, NMS can get, display and analyze the performance data.
TM
NetNumen U31 provides the table view of each counter, user name and password of
the interface, but not opens the database directly.

The interface also enables NMS to get alarm view data. NMS can get and show the
TM
alarm data. NMS gets data in active mode. NetNumen U31 provides the user name
and password of the interface, but not opens the database directly.
NMS only has the read priority on these views. NMS may ensure the alarm view of
TM
NetNumen U31 through SQL statement.
3.5.3 FTP
File Transfer Protocol (FTP) is a bidirectional transfer protocol. The NetNumen U31
adopts FTP as the NBI protocol for transferring mass data files such as performance
data files, inventory files, configuration files and topology/resource data files.
FTP has the following characteristics:
Supports the file transfer between different operating systems.
Supports mass data transmission.
Embraces high reliability.
Exhibits moderate security.
3.5.4 SNMP
Simple Network Management Protocol (SNMP) is a simple network management

protocol established by IETF, which has become the industry standard of network
management. Based on a manager/agent model, the SNMP protocol adopts a
Management Information Base (MIB) and a relevant command set for information
interaction. In addition, SNMP Trap indicates the active message reporting mechanism of
SNMP.
SNMP has the following characteristics:
SNMP features simple design, high scalability, and easy use.
SNMP supports various mature standard-compliant MIBs and thus supports wide
application.

SNMP transmission is based on UDP and thus is highly efficient and independent.
SNMP enables easy reporting of events, alarms, and messages.
The functions of SNMP in NetNumen U31 are to report alarm to NMS layer and do
alarm synchronization.
TM
Currently the NetNumen U31 supports SNMP version of V1, V2c and V3.
4 Features and Functionalities

TM
The main functions of NetNumen U31 includes fault management, configuration
management, performance management, security management, topology management,
system management, software management, signaling tracing, northbound interfaces,
and etc.
Topology Management
The topology management of the NetNumen U31 system provides a visual network
topology map and NE relationship. The main GUI has a tree view for NE organization
display/select and a graphic aero for main display.
The graphic aero will show the detail info of selected node. If the selected node is whole
network or a sub network, the graphic aero shows NE/Sub-network/NE group distribution,
user can click the icon to change the selected node and entry new detail info. The
graphic aero supports zooming, searching, cascading display. User can define
background map and the mode of icon arrange of each node. User can define that status
info, alarm counter or KPI info show with the icon in graphic aero.
User can select a NE from tree view or graphic aero and entry CM/PM/FM GUI to certain
NE, to change configurations, check statuses, handle alarms, get reports and make
other operations.
User can customize the interface setting as his like, for example the icon size, color
setting, and size. NetNumen 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.
Configuration Management
The configuration management of the NetNumen U31 system can manage ZTEs

various type of GERAN, UTRAN and eUTRAN NE, include BSC, RNC, BTS, Node B,
eNode B, multi-modes BS (SDR).
The configuration management provides functions to adding, deleting, modifying and

querying whole networks configuration data. Combined with topology management, user
can do these jobs conveniently.
NetNumen U31 supports online and offline data modify, multi data plane for parallel
work, status management and secure variable management.
Fault Management
Fault management of NetNumen U31 provides last functions:
1. Monitor current status and alarms of NE equipment & logical unit in real time.
2. Provides alarm query and suggestions to handle faults.
3. Provides alarm filter and correlation process to reduce amount of alarm or find the
root/most important alarm.
4. Provides knowledge DB to record the history experiences of alarm handling.
5. Provides diagnose tools to help user make certain which is the real problem of
network.
6. Provides alarm trigging script makes system can react to certain alarm with
pre-defined MML script to solve problem quickly and automatically.
Fault management also integrate with topology view to make user check alarm status via
icon color and alarm counter via popup display. It also possible to select a NE from
topology view and guide to alarm list/rack map of this NE.
Performance Management
Performance management functions of NetNumen U31 are used to gather

performance data from NE, analysis and illustrate to operator.
User can manage measurement tasks to control gathering performance data process. By
setting data storage period, user can keep it sufficient to maintain network and clear old
data to keep system long-term running.

User can set formula to calculate PI & KPI, it can be used to monitor QoS index or make
reports. For QoS monitor, user need to set QoS jobs, system will gather data and
calculate index periodically and raise alarm events automatically.
The real time PM query makes user can get PM data instantly or monitor certain KPI
continuously. Usually use to quickly evaluate network performance when configuration
changed or monitor important cell.
Software Management
Software management function use to control software of NE and NetNumen U31

system.
To manage NE software, NetNumen U31 stores multi software version in system.

User can choose certain version to download to NE, which stores one or more software
version in its memory, and active one version stored in NE. NetNumen U31 will
prepare fitful configuration data and download to NE with the active process.
NetNumen U31 supports to query current running version on NE and check is it fit
with assigned version on EMS.
NetNumen U31 supports the software management of itself. User can install, recover
and upgrade software of NetNumen U31.
System Management
System management of NetNumen U31 uses to help administrator of NetNumen

U31 to maintain it. The security and log part of system do not listed in this chapter, these
two parts is also useful to administrator.
Administrator can use system management functions to
1. Backup/restore system
2. Check system status and connect condition of NEs and clients.
3. Adjust time of whole network via NTP
4. Management license of whole network
Security Management
Security management makes administrator of NetNumen U31 can management the

security policy and setting of NetNumen U31 system, include NetNumen U31
server hardening, IP network design and transmission security in NetNumen U31 and
between NetNumen U31 and managed NE.
NetNumen U31 provides user management, user authorization and access

authentication, these functions are important to make system can be used safely and
smoothly.
Log management uses to check the problem of NetNumen U31 executing and check
operations to audit the usage of system.
Trace Management
Trace management is important to find out network problem by get / illustrate / analysis
signaling and internal events from NE.
ZTE solution of trace management includes two part local trace and globe trace. Local
trace directly connects to BSC/RNC or eNodeB gets signaling and internal events, to
support single node tuning and trouble shooting. Globe trace gets signaling and standard
events from all NE of the network, to supports long time supervise of whole network. The
globe trace is going to follow 3GPP 32.42X specifications at 2014.
Local trace tools are part of NetNumen U31. RCT is use to trace GSM, and UMTS, it
connect to BSC/RNC and can trace NodeBs and cells within the RAN. UDT is use to
trace FDD-LTE and TDD-LTE, it connect to the eNodeB and get the trace and event from
it.
Globe trace called CTS is a standalone product. Current version is an exclusive system
only can connects to ZTE NEs and trace it. There are no chance to integrate with other
vendors equipment and no open interface to other post analysis system.
ZTE is planning to upgrade CTS to follow 3GPP 32. 42X, it will have three parts: trace
control, TCE and post analysis. TCE collect events and provide the results to post
processor in standard file format. The trace control and post analysis part of CTS can
integrate with other vendors equipments / TCE, with certain interface adapter.
Inventory Management
The inventory management of NetNumen U31 collects the hardware and software
inventory info from current network. User can manually input inventory info for dumb
equipments like RF combiner and antenna. It supports user query the inventory info,
statistical and report. It also supports output the query results to files or input manually

input inventory info from file.
The inventory data can be collected from NE by MML command user can choose the
granularity by EMS or NE. Inventory management can periodically execute it and update
the database.
A message will be generate by EMS, NE or License center when inventory info changes.
The situation includes NE reboot / reconnect, circuit pull out or plug in, the software has
upgraded, license usage changed and other events. Inventory management records
these messages and updates the current data.
Tools
These tools use to support O&M operations. Health check and stability report makes it
easy to evaluate the network condition and the maintain workload.
MML command terminal use to simplify the usage of MML. The online help supports to
get certain usage info and management information structure when user using GUI or
MML.
O&M Infrastructure
The NetNumen U31s O&M infrastructure is use to fit the high available requirements
from operator. It includes the NetNumen U31 server local high availability, remote
disaster recovery, data backup and restore.
The O&M infrastructure also includes the Access Mode except the client of NetNumen
U31. There include telnet mode and WEB client via Citrix solution.
Other Function Modules
Other functions and features include Enhanced Management Report, Integrated

Configuration Management, Internal CBC (GERAN&UTRAN)and etc.
The Enhanced Report Management (ERM) module is a flexible, rich format report
generation subsystem. It is based on BO report engine, and can fulfill the quick
changed/complicated format report requirements, can extract data from many EMSs
running fitful version, and export joint reports.
Integrated Configuration Management (ICM) is application which provides the whole

network configuration management, and can use in multi-EMS situation. It is also useful

to manage large-scale network by supporting parallel modification with multiple planning

area functions.
Internal Cell Broadcasting Center (CBC) offers the basic operational function which
includes message edit, message send and message query. Meanwhile, CBC can
provide the planning and management function of CBC service.
5 System Reliability
5.1 Backup & Restore Solution

TM
Backup & restoration solution of NetNumen U31 System is to rescue the system failure
or unexpected problems, possibly as shown in the following scenarios:
NetNumen U31 System Collapse
OS Collapse
NetNumen U31 application Collapse
DB Collapse or some DB file lost.
TM
ZTE NetNumen U31 System Backup and Restore Solution are based on third party
hardware and software. The backup solution supports to set backup policy for the backup
TM
of the complete data of NetNumen U31 server, including system file, database file and
TM
application file. Using this policy, NetNumen U31 server can backup files during low
system load, usually in the night, the data could be backup without shutting it down into
single user mode.

Figure 5-1 Backup & Restoration Solution
NetNumenTM U31 Server Backup Server

Switch
1000M
Fiber Fiber
Disk Array
Tape Library
TM TM
NetNumen U31 backup and restoration solution includes active NetNumen U31
TM
Server, backup NetNumen U31 Server, disk array, and tape library. And network use
dual 1000M switch LAN.
The backup & restoration solution is based on third party software. This software
supports three backup & restoration modes:
Full Backup: In a full backup, all of the Primary Storage on a target system is
backed up. The data backed up in a Full Backup includes file data such as
directories, folders, filenames, file attributes, access control lists and other security
information.
Cumulative Incremental Backup: A Cumulative Incremental Backup will back up

the files that have been modified or created since the most recent lower level
backup (level n-1 or lower).
Differential Backup: A special type of Cumulative Incremental Backup copies the

files that have been modified or created since a previous Full Backup.
The execution of backup & restoration solutions can be in manual operation or

automatically scheduled by system, and backup contents can be OS and application
TM
data, NetNumen U31 system and application data, and Database.

5.2 High Availability Solution
NetNumen U31 High Availability solution is to guarantee the availability of software

and hardware.
NetNumen U31 Availability Solution is based on third party hardware and software,
including Active Server, Standby server, and disk array. The networking is shown in the
following figure.
Figure 5-2 High Availability Solution
In ZTE High Availability Solution, the active server and standby server are installed with
third party High Availability software, and use network to detect the status of active
server and network card.
Between active server and standby server, there are two heartbeat lines at least, these
heartbeat lines provide detect function, include the operating system software and
hardware, network communications and applications running, etc. Once the other host is
not running properly, the fault device on the application will stop running, the standby
device will start same application which running on fault device, and take over all the
application which running on fault device, and also including the IP address automatically,
without human intervention.

5.3 Disaster Recovery Solution
Disaster Recovery solution is to deploy NetNumen U31 servers in separated physical

locations to improve whole system redundancy. Disaster Recovery Solution can be used
in the following scenarios:
Software failures scenarios
Hardware failures scenarios
Equipment room disaster, fire, earthquake or flood for example
ZTE NetNumen U31 System High Availability Solution is based on third party
TM TM
hardware and software, includes Active NetNumen U31 Server, Standby NetNumen
U31 server, and disk array. The networking is shown in the following figure.
Figure 5-3 Disaster Recovery Solution
TM
ZTE Disaster Recovery solution adapts dual NetNumen U31 system for 1+1 backup,
including active server, active disc array, standby server and standby disc array. Active
server use fiber to connect with active disc array and standby server also use fiber to
connect with standby disc array.
Transmission network adapts dual lines, both lines are used as data backup line and
heartbeat line. When network cards or network is failure, it will automatically switch to
another device on standby to return to work.

In ZTE Disaster Recovery solution, between active system in site A and standby system
in site B, there are dual heartbeat lines, and transition network can use IP or Fiber. And
these dual heartbeat lines provide detect function, include the operating system software
and hardware, network communications and applications running, etc. Once the other
host is not running properly, the fault device on the application will stop running, the
standby device will immediately start same application which running on fault device, and
take over all the application which running on fault device, and also including the IP
address automatically, without human intervention.
After disaster in site A is recovered, the whole system data needs to rollback. Data
reverse replication copies only the changed data during disaster, unless all of the data is
lost, it not need to reverse replication all of the data.
5.4 Operation Security

TM
NetNumen U31 sets users authorities by role and user management. System
combines various operations (such as add MO, delete MO, modify attribute, alarm view,

and so on.) and NE modules to set users authorities, which can be accurate to certain

operation in certain NE. Users authorities check mechanism is set in server, which

checks all operations user made. Those operations that do not pass the check won t be
executed. User locked feature is also provided. Invalid user could be locked and not
allowed to log on the system. Customized setting on user logon, user password, user
expiration data, IP address check, and so on is allowed, for example, users who fail
logging on over 3 times will be locked.
In addition, Operation log, system log, and security log are traced and recorded in the
system. Query of logs based on different conditions, export and print of logs are
supported. Log policy is also provided.
5.5 Software Reliability
Several methods are available to monitor software reliability of NetNumen U31 server:
Link check mechanism: heartbeat check mechanism is adopted between Client

and Server, Server and NE, up-level NMS interface and NMS to check the

communication status of links periodically. No alarm message of link between NE

and Server will be occurred.
Version check mechanism: it is adopted between Client and Server, Server and
NE to check their versions consistency. Inconsistent software version fails to
connect them normally. Meanwhile, language check will be performed between
Client and Server. If languages they use are different, they cannot be connected
normally.
Access Control List: System controls and sets IP address restriction of Client and
superior NMS by accessing IP (port) of security management module, certain IP
address will not be allowed to log on, improving system security.
Alarm Message: When services and process of Server go wrong, system

generates alarm messages.
Node Hardening: it offers a number of recommendations and scripts in order to

protect network nodes from accidental and malicious operations, and ensures
confidentiality, integrity and availability of OS/DB.
rd
In addition to this, the operator can also install 3 party security software like SSL, SFTP,
anti-virus and etc. other security software need to be verified by ZTE Corporation before
installation. Firewall is also needed to prevent system from external illegal attacks.
6 Technical Specification
6.1 Performance Indices
The following table shows NetNumen U31 maximum processing capability for each
single RAT.
Table 6-1 NetNumen U31 Processing Capacity for Each RAT
Items Index
Maximum processing capability for UMTS 100000 Cells

Maximum processing capability for GSM 250000 TRXs
Maximum processing capability for FDD LTE 100000 Cells
Maximum processing capability for TDD LTE 100000 Cells
One UMTS/FDD LTE/TDD LTE cell occupy equivalent resources as 2.5 GSM TRXs in
NetNumen U31 system.
The following tables show storage reliability capabilities:
Table 6-2 Performance Indices of NetNumen U31
Items Index
MTBF (HA solution) 6480 hours
MTTR (HA solution) 0.5 hours
Availability indicator (HA solution) 0.99992
6.2 Physical Dimensions

TM
Server and disk array of NetNumen U31 adopt rack-mounted devices, installed inside
standard 19 rack. Client employs PC or workstation which is fully compliant with
industrial standards.
Table 6-3 NetNumen U31 Rack Dimension
Item Value
2000 mm, without footprint margin;

Height
Dimension 2100 mm, with footprint margin.
(mm) Width 600
Depth 1000

Rack s weight depends on actual configuration, and the following table shows typical
weight and the according requirements on ground.
TM
Table 6-4 Typical NetNumen U31 requirements on Ground
Item Value

Weight of Rack 300 kg

2
Primary equipment room 450 kg/m
Ground Weight Capacity
2
Other than primary equipment room 300 kg/m
6.3 Power Supply
The power supply of NetNumen U31 system can be in DC or AC.
Table 6-5 NetNumen U31 DC Power Supply Requirements
Item Value
Working power supply -48 V
Voltage range -57 V~-40 V
Voltage output ripple < 200 mV
Table 6-6 NetNumen U31 AC Power Supply Requirements
Item Value
Working power supply 220 V,110V 50 Hz
Voltage range 176 V~264 V
Voltage frequency range 45 Hz~65 Hz
Power consumption is different due to different hardware servers, and the following table
shows power consumption for the servers from IBM.
Table 6-7 NetNumen U31 Power Consumption Indices
Item Value
Operational current 35 A
Power 740 (6C 4.2GHz,32G) 248 W
Power 740 (6C 4.2GHz,64G) 312 W

System Power consumption
Power 740 (8C 4.2GHz,96G) 342 W
Power 740 (8C 4.2GHz,118G) 374 W

6.4 Environment
6.4.1 Grounding Requirement
Table 6-8 NetNumen U31 Grounding Requirements
Item Value
Rack pick-up resistance 0.1 ~0.3
Ground resistance 1
6.4.2 Temperature and Humidity
Table 6-9 Requirements on Temperature and Humidity
Temperature Relative Humidity

Equipment Long Term Short Term Long Term Short Term
Operation Operation Operation Operation
TM
NetNumen U31 0 C~40 C -5C ~ 45C 20%~90% 5%~95%
Note 1: Measurement point of operating temperature and humidity in equipment room

refers to the measurement made when no guide plates in front and back of rack, and
where 1.5m above the floor and 0.4m away from the front of the rack.
Note 2: Short term operation refers to continuous operation less than 48 hours and
accumulated operation every year less than 5 days.
6.4.3 Cleanliness Requirement
Dust could hazard electrostatic equipment, which makes poor contact of socket

connector, impacting equipments life time and causing failure easily.
Table 6-10 Requirements on Dust Content and Particle Size
Item Value
Max diameter (m) 0.5 1 3 5

3 5 5 4 4
Max consistency (particle count/m ) 1410 710 2410 310

Requirements on salt, acid and sulfide content in air are required. These hazardous
substances accelerate metal erosion and aging process of some parts. Equipment room
should be prevented from harmful gas intrusion such as SO2, H2S, NH3, NO2, etc.
Table 6-11 Restriction of Harmful Gas
Name Average (mg/m3) Max (mg/m3)

SO2 0.2 1.5
H2S About 0.006 0.03
NO2 0.04 0.15
NH3 0.05 0.15
Cl2 0.01 0.3
6.4.4 Lighting
Prevent direct sunlight from aging deformation of circuit board.
Average illumination is 300 LX~450 LX free from glare.
7 Acronyms
Acronyms English
CORBA Common Object Request Broker Architecture
EMS Element Management System
ERM Enhanced Report Management
FM Fault Management
GSM Global System for Mobile Communication
GUI Graphical User Interface
MML Man Machine Language
MTBF Mean Time Between Failures
OMC Operations & Maintenance Center
OMCR Operations & Maintenance Center Radio
OMM Operation Maintenance Module
TCP/IP Transmission Control Protocol/Internet Protocol

UMTS Universal Mobile Telecommunications System

2-2 ZTE Radio Network EMS - ZTE NetNumen U31 Product Description

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

2-2 ZTE Radio Network EMS - ZTE NetNumen U31 Product Description

Transféré par

Droits d'auteur :

Formats disponibles

ZTE NetNumen U31 Product

ZTE NetNumen U31 Product Description

V1.0 2014/10/09 Li Xiaojuan First Release

Modify Corba interface description;

2015 ZTE Corporation. All rights reserved.

ZTE Confidential & Proprietary 1

4 Features and Functionalities .......................................................................... 16

2 ZTE Confidential & Proprietary

Figure 3-1 NetNumen U31 Software Architecture ............................................................ 6

ZTE Confidential & Proprietary 3

High-efficient Centralized EMS System

Centralized management of multi-RAT network equipments, it can manage GERAN,

The JAVA/J2EE platform-based design is convenient for operators to select

4 ZTE Confidential & Proprietary

Unified configuration management and data consistency checking functions to

Network health check and intelligent in-process inspection of full-network

Advanced Network Security

Strict access rights control, hierarchical and role-based management strategies,

LDAP interface to 4A server provides account management and accessing

Intelligent Networking and Flexible Network O&M

Daylight saving time management meets the time management requirements of

ZTE Confidential & Proprietary 5

Integrated Tools Enhancing Service Efficiency

Figure 3-1 NetNumen U31 Software Architecture

6 ZTE Confidential & Proprietary

3.1 NetNumenTM U31 Product Portfolio

Figure 3-2 NetNumenTM U31 Hardware Architecture

ZTE Confidential & Proprietary 7

BSC and BTS in GSM radio network

RNC and Node B in UMTS radio network

eNodeB in FDD LTE radio network

eNodeB in TDD LTE radio network

3.2 NetNumenTM U31 Networking & Operation

Figure 3-3 NetNumen U31 typical Networking

8 ZTE Confidential & Proprietary

Central room in Province

A City room A City

Client client eNodeB NodeB

3.2.1 LAN Networking

ZTE Confidential & Proprietary 9

Figure 3-4 LAN Networking

3.2.2 Remote Networking

Figure 3-5 Remote Networking

10 ZTE Confidential & Proprietary

3.2.3 Meta-frame Solution

Figure 3-6 Meta-frame Networking

ZTE Confidential & Proprietary 11

3.3 NetNumenTM U31 Server Configuration

Network Scale (Cells)

P7 740 6C32G 4.2GHzCPU

P7 740 6C64G 4.2GHzCPU

P7 740 6C96G 4.2GHzCPU

P7 740 8C96G 4.2GHzCPU

P7 740 8C128G 4.2GHzCPU

12 ZTE Confidential & Proprietary

Network Scale (Cells)

SUN T4-1 8C64G 2.85GHzCPU

SUN T4-1 8C128G 2.85GHzCPU

SUN T4-1 8C128G 2.85GHzCPU

SUN T4-1 8C128G 2.85GHzCPU

The following Database and Operation System is recommended.

Table 3-3 Software Configuration for Server

Object Server Configuration

Operation System AIX/Solaris/Linux