NETNumen R38

NetNumenTM U31R58 Product
Description
NetNumenTM U31R58 Product Description

Version Date Author Reviewer Notes
V2.00 2011/11/08 Weng Yixin Not open to the third party
Update new feature description and U31

V2.10 2012/10/28 Weng Yixin
server configuration
Update northbound interface, U31 server
V2.20 2013/01/21 Weng Yixin
configuration and some function description
The description of Server software is in the
V2.21 2013/02/27 Weng Yixin
wrong sequence which has been modified
Update northbound interface, U31 server
V2.30 2013/06/07 Weng Yixin
configuration
V2.40 2013/11/07 Weng Yixin Update U31 server configuration
Update U31 feature description ,NBI and

V2.41 2014/08/05 Weng Yixin
server configuration
License feature description is new added.
V2.50 2015/05/15 Weng Yixin Update the description of version
management and E2E management.
Update U31 server configuration
V2.51 2015/05/27 Weng Yixin Add capacity of single server in performance
indexes
IM supports Corba
V3.00 2016/02/03 Weng Yixin
Update end-to-end description
© 2019 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 ............................................................................................................ 5
1.1 System Introduction ............................................................................................. 5
1.2 ZTE EMS Product Frame ..................................................................................... 6
1.3 Network Elements Managed by U31 .................................................................... 6
2 System Features................................................................................................ 7
2.1 Fault Management ............................................................................................... 8
2.2 Configuration Management ................................................................................ 12
2.3 Performance Management ................................................................................. 13
2.4 Security Management ........................................................................................ 15
2.4.1 Relation Model of Security Management ............................................................ 15
2.4.2 Security Management Features ......................................................................... 17
2.5 Log Management ............................................................................................... 19
2.6 Topology Management ...................................................................................... 21
2.7 Version Management ......................................................................................... 23
2.8 License Management......................................................................................... 26
2.9 Maintenance Management................................................................................. 28
2.10 Inventory Management ...................................................................................... 30
2.11 End to End Management ................................................................................... 30
2.12 Other Functions ................................................................................................. 34
2.12.1 Inspection Management ..................................................................................... 34
2.12.2 Inspection Report ............................................................................................... 35
2.12.3 Ping Test ........................................................................................................... 36
2.12.4 Route Tracing .................................................................................................... 36
2.12.5 Online Help ........................................................................................................ 36
3 System Architecture........................................................................................ 37
3.1 U31 Architecture and Networking ....................................................................... 37
3.1.1 LAN Networking ................................................................................................. 37
3.1.2 Remote Networking ........................................................................................... 38
3.2 Hardware & Software Configuration for U31 system .......................................... 38
3.3 Hardware & Software Configuration for Client .................................................... 40
3.4 System Interface ................................................................................................ 40
3.4.1 Northbound Interface ......................................................................................... 41
3.4.2 Southbound Interface......................................................................................... 42
4 System Reliability............................................................................................ 42
4.1 Backup & Restore Solution ................................................................................ 42
4.2 High Availability Solution .................................................................................... 44
2 ZTE Confidential & Proprietary

4.3 Disaster Recovery Solution ................................................................................ 45

4.4 Operation Security ............................................................................................. 48
4.5 Software Reliability ............................................................................................ 49
4.5.1 Network Transmission ....................................................................................... 49
5 Technical Indexes ........................................................................................... 50

5.1 Performance Indexes ......................................................................................... 50
5.2 Physical Performance ........................................................................................ 51
5.2.1 Dimension and Structure.................................................................................... 51
5.2.2 Typical Overall Weight and Ground Weight Capacity of Equipment Room ......... 51
5.3 Power Supply..................................................................................................... 51
5.3.1 Power Range ..................................................................................................... 52
5.3.2 Power Consumption Indexes ............................................................................. 52
6 Criteria ............................................................................................................. 52
7 Acronyms ......................................................................................................... 55

FIGURES
Figure 1-1 U31 Product Frame ........................................................................................... 6

Figure 2-1 Security Management Relational Model ............................................................17
Figure 2-2 Architecture of the Version Management Module ..............................................25
Figure 2-3 Architecture of the License Management Module .............................................27
Figure 3-1 LAN Networking ................................................................................................37
Figure 3-2 Remote Networking ..........................................................................................38
Figure 4-1 High Availability Solution ...................................................................................45
Figure 4-2 Disaster Recovery Solution ...............................................................................47
TABLES
Table 1-1 NEs Managed by U31 ......................................................................................... 6

Table 3-1 Hardware Configuration for U31 system ............................................................39
Table 3-2 Disk Array for U31..............................................................................................39
Table 3-3 Software Configuration for Server ......................................................................40
Table 3-4 Minimum Hardware Configuration for Client .......................................................40
Table 3-5 Software Configuration for Client .......................................................................40
Table 5-1 Performance Indexes of U31..............................................................................50
Table 5-2 Parameters of U31 Rack ....................................................................................51
Table 5-3 Typical Overall Weight and Ground Weight Capacity of Equipment Room .........51
Table 5-4 Range of U31 AC Power ....................................................................................52
Table 5-5 U31 Power Consumption Indexes ......................................................................52

1 Overview
1.1 System Introduction
ZTE NetNumen™ U31 microwave EMS has a leading and mature management system
architecture that perfectly conforms to all ITU-T TMN and 3GPP specifications. The high
scalability of U31 ensures a smooth upgrade having a minimum impact on the existing
system. It qualifies the following properties.
⚫ Based on the J2EE (Java 2 Enterprise Edition) platform.
⚫ Uniform management of microwave NEs.
⚫ Rich northbound interfaces such as: CORBA, SNMP, FILE and DB are available,
easily to be integrated to various OSSs.
⚫ High-level UNIX servers to enable high integration, high performance and good
security.
⚫ Multiple access methods such as: GUI and Web.
U31 supports many local, remote and reverse networking methods, flexible according to
different scenarios and can be assembled flexibly so as to form a diversified,
tridimensional management network. Dual-server high availability and cluster are
supported as well.
⚫ Local, remote and reverse networking methods to adapt to different implementation

environments.
⚫ Local & remote disaster recovery modes to guarantee high security of data.
⚫ Support of server cluster to enable favorable load sharing, ensuring a huge

capacity.
⚫ Hierarchical & decentralized management strategies to fit to carriers' OAM system;

systems can be constructed hierarchically according to size of managed network,
maintenance mode and carriers’ opinions.

1.2 ZTE EMS Product Frame
U31 is playing a more and more important role in the new generation
telecommunications.
U31 is located in the Element Management Layer of TMN (Telecommunication

Management Network) model, and interconnects with the upper level NMS (Network
Management System) through northbound interface. See Figure 1 for the role of U31 in
network.
Figure 1-1 U31 Product Frame
1.3 Network Elements Managed by U31
As is shown in Figure 1-1, the NEs managed by U31 is listed in Table 1-1.
Table 1-1 NEs Managed by U31
Product Type Product List
NR8000 Series、S200、S340、S400、S500、
Microwave product
E/V2000

2 System Features
General Introduction of Main Functions
The main functions of U31 includes: fault management, configuration management,

performance management, security management, topology management, system
management, version management, inventory management and E2E management, etc.
1. Fault management
Fault management helps the network operating & maintenance (O&M) engineers to
detect and position the network fault as quickly as possible. The centralized alarm
function of U31 reduces the management interface points for the O&M engineers,
which mainly implements:
i. Centralized monitoring of fault alarms: monitor the current status of the

network equipments is performed.
ii. Centralized processing of fault alarms: once the equipments fail, users can
receive alarm information from U31 immediately and take necessary
measures to deal with it.
2. Configuration management
U31 provides the configuration management of all the NEs (Network Elements) and
offers operations such as create, add, delete, modify and query data on NE.
Configuration management enables the users to synchronize of configuration data
of the whole network.
3. Performance management
Through the statistical analysis of the collected performance data, users will be able
to know the running status of the NEs and determine the choke point of the network,
thus providing data support for daily maintenance, network optimization and
capacity expansion.

Users can find out the problems in each NE’s operation and provide professional
support and guidance for the decision-making layer, by horizontal comparison and
analysis of the whole network ’s performance data collected by U31.
Performance management also provides real-time monitoring of the network and

generates real-time alarm to inform the user when the performance value exceeds
threshold.
4. Security management
Security management ensures that different users have different access rights to
the resources of U31. It provides the security management functions such as
authorization and authentication, and thus avoids illegal operation on the network
management system. Therefore the security management ensures the lasting,
normal and steady operation of the network management system.
5. Topology management
Topology management provides a convenient way to know the distribution and

organization of all the NEs in the network. U31 manages a huge number of NEs that
are of different types, and thus the centralized and grouping management of them
becomes very important.
U31 should provide a topology view that can be easy arranged according to the
user’s requirement. For example, the topology view may be customized in
accordance with the function or the equipment type. Each kind of the customized
topology view helps the users to conveniently position the object that they care
about and quickly manage the equipment through topology navigation function.
2.1 Fault Management
Fault management module receives and processes the alarms reported by equipments
through the interface, displaying them to users, and forwarding them to the designated
target as per the needs. It includes the following features:
1. Alarm monitoring

Users can realize real-time alarm monitoring of the whole network elements by U31
to understand the alarm-level, the alarm type, reasons, etc. Besides viewing the
monitor alarm through the client, U31 users also can receive and view alarms
through the various approaches, such as alarm box, EMAIL, SMS, etc.
2. Alarm query and statistical
Users may set up certain conditions to inquire current and history alarms. By
alarming statistical template which provided by the system, U31 users generate
related reported from the different needs, and export these reports in different
formats or the directly print out.
3. Alarm graphic display & location
The Alarm Graphic Display function is used to supervise the network alarm status
through a high-level user interface fast and conveniently.
U31 client opens the rack map and helps users to locate the board where an alarm
occurs. In addition, this function provides real-time monitoring for overall network
alarm statuses depending on NEs in different colors.
4. Correlation analysis
It makes the comprehensive correlation analysis through the alarms reported from
NEs, draws the key information, reduces the redundant information, and enables
the users to rapidly and accurately locate the equipments fault.
5. Alarms confirmation and negative confirmation
U31 supports users to confirm/ negatively confirm an alarm, meanwhile to record

the time of the operator and these operations.
6. Alarm forward
It supports to forward alarm by email and SMS. It also supports forward alarm by
Socket mode.
7. Alarm dump

The warning dump includes manual and automatic dumps. The automatic dump
can be divided into periodical and the database ultra-cap dumps. For periodical
dump, dump period, dump content and dump format can be set; for database
ultra-cap dump, database upper limit, dump content and dump format can be set.
The dump document format may be TXT, EXCEL, PDF, CSV and HTML.
8. Alarm processing
i. U31 system can re-define the level of alarm and customize alarm processing
rules. Alarm processing rules which system supports include: alarm filtration,
alarm delay, automatic confirmation, automatic recovery, automatic forwarding
and alarm correlation processing rules (alarm merger, alarm timing, alarm
count, and alarm suppression).
ii. Alarm filtration: it includes alarm global filtration, alarm warehousing filtration
and alarm user filtration. Alarm global filtration means if reported alarms meet
the rules, they will be only stored into the database and will not be displayed at
the Client. Alarm warehousing filtration means alarms are discarded directly,
neither stored into the database nor displayed at the Client. Alarm user
filtration doesn’t display alarm only at Client which the rule maker user loges in.
iii. Alarm delay: When reported alarms meet the rules, they will be delayed for a
specified period of time; if alarms recover during the delay time, they will be no
longer reported to the Client. Otherwise they will be displayed at the current
alarm real-time monitoring interface of the Client after the delay time.
iv. Automatic confirmation: U31 confirms the designated alarm automatically by

anonymously and alarm receiving time.
v. Automatic recovery: U31 recovers the designated alarm automatically.
vi. Automatic forwarding: If reported alarms meet the rules, the system will inform
the user who is specified in the rules by mail or SMS.
vii. Alarm correlation processing rules:
a) Alarm merger: all current alarms which meet the rules are merged and
displayed as one alarm at the Client.

b) Alarm timing: for current alarms which meet the rules or activity status, if
their time duration exceeds specified period of time, the system will raise
the level of these alarms or generate a new alarm.
c) Alarm count: for current alarms which meet the rules, if alarm time
exceed designated threshold during the specified period of time, the
system will generate a new alarm; reported alarms and count will be
stored in the database, and displayed at the Client.
d) Alarm suppression: as long as current main alarms exist or occur, the

ancillary alarms of the rules will not display at the Client. If an alarm has
been suppressed, it will not be re-submitted to display until all of its
suppression alarms are restored.
9. Alarm knowledge base
User can check or record the information of alarm processing. User can record the
fault processing information for the given NE to enhance the processing efficiency
of specified object. For example, how to deal with a certain link once occurred
quickly disconnection/recovery.
10. Alarm synchronization
Alarm synchronization includes manual alarm synchronization and automatic alarm

synchronization. Alarm synchronization ensures integrity and consistency of alarms
data in U31 system with NEs’ alarm data. In connection failure mode, automatic
alarm synchronization is triggered once certain failures occur.
11. External alarm access
External Alarm Access implementation and display external alarm, such as

temperature alarm, etc.
12. Alarm box management
U31 supports the use of alarm box to indicate alarms. Users can create, modify,
view, delete, disable, and enable an alarm box in the system. The system connects

an alarm box according to the preset rule and sends alarm information to the alarm
box.
13. Diagnosis and testing
Diagnosis and testing provides the test for the specified physical devices to verify
the communication status of the system in order to ensure the normal and stable
running of the system. It can also facilitate locating the fault in time.
2.2 Configuration Management
U31 provides the configuration management of all the NEs (Network Elements) and
offers operations such as adding, deleting, modifying and querying on NE data.
The configuration management includes following features:
1. Data configuration
U31 system configures various NE data by GUI, including creating, deleting, and
modifying, querying and valid checking of configuration data.
U31 Configuration management supports batch operation such as batch updating

software version for NE, cards and data, user port profile configuration, etc.
2. Data synchronization
U31 supports automatic and manual synchronization of configuration data, if the NE

configuration data was changed, the system will inform to U31, and user also can
trigger synchronization in the U31 Client, synchronizing the edited configuration
data to NE, and data synchronization system will record the logs.
3. Configuration data availability check
U31 supports validity check of configuration data within its scope. This validity
check contains data validity and logic, such as integrity, accuracy and
completeness. Before users synchronize data to NE, they can check the validity of
data within its scope so as to reduce the possibility of abnormal service caused by
wrongly configured data.

4. Status management
Status management mainly provides the management and query for various
dynamic resources and NE status, and the management operation such as block,
unblock, and switching, etc.
5. Data export
U31 provides configuration data export, it enables user to export configuration data
in XML and CSV etc, and it can automatically export data periodically through
strategic task.
6. Data import
User can import valid configuration data files to U31, and system will check the
integrity and consistence of inputting files, testify the validity, and then accomplish
configuration automatically.
7. Multi configuration sets
User can save current configuration data during modification. User can roll back to
restore the saved configuration data in case of failure or unsuccessful modification.
This feature makes it easy for the user to compare modified configuration data with
the saved configuration data. U31 can monitor and maintain managed object during
modification and help the users to keep multi sets of configuration data, which will
be used in different conditions.
2.3 Performance Management
Performance management is used to collect network performance data, evaluate the

network performance indexes, as well as provide the performance report forms and
report QoS emergency. It produces evidence for the optimization and maintenance of the
whole network.
1. Measure task management

This feature provides performance measurement task ’s creation, deletion, query,

modification, activation and suspension, overdue deletion, query and deletion of
history measurement tasks, synchronization of measurement tasks etc. NE
equipments report collected data to Server in terms of measurement task
requirement.
2. Indexes management
This feature manages indexes add, modify, delete, view, print, import and export,
etc.
EMS provides default KPI indexes. However, users can define the KPI indexes they
need according to their own requirements.
3. Performance data processing
Users can query the performance data. The query result can be displayed by tables
or graphics and printed as well.
U31 can perform the functions of synchronizing the performance data both
automatically and manually, in order to ensure the consistency of the performance
data between EMS and NEs.
U31 can export and save the performance data as files, of which the format can be
appointed. They can be Excel, PDF, HTML, CSV or Text files.
4. Performance data integrity check
U31 can automatically check integrity of performance data is supported when it is

import to database, and corresponding data records integrity will be labeled.
Whether some counters’ data is missing; for summary data record of several time
granularities, it needs to check whether there is some data is missing.
U31 also support performance data recollection, automatic or manual recollection

ways to recollect missed data are supported.
5. Counter inquiry processing

User can query the counter and print or save the results as Excel, PDF, HTML, CSV
or Text files.
6. Performance report
U31 system can periodically create a performance report with multi-format files
according to the customization of user, and E-mail it to the user. The system can
use the default performance report, which is defined before the operation of the
system, as well as produce a performance report according to the customization of
the user during the operation of the system. Besides, system also supports
graphical reports.
7. Performance data real-time query
Performance data real-time query supports query based on conditions such as NE

type, object type, query granularity or location. The query granularity can be defined
by users. It supports minute-level and second-level query granularity. It is supported
that whether or not to customization for query object. The query results can be
saved automatically.
2.4 Security Management
U31 system security management is executed by distributing different authorities to

different users, roles and role groups. The system creates role/role group and then
assigns them different NM authorities. Then system allocates one or more roles/role
groups to a user, so the user gets the authorities.
Security management also includes nodes consolidation which used to protect system
from virus and intrusion.
2.4.1 Relation Model of Security Management
1. Basic glossary
Role, role group, and user are the basic glossaries used in security management of
U31 system.

i. Role
A Role means the management authority of a user, defining a group of user

management authorities by specifying the operation permissions and
management resources. Operation permissions define which functional
modules of U31 can be used by the role. For example: for the log management
module, it can be defined if the role is allowed to query or maintain the logs.
Management resources specify the sub-nets or specific NEs under the
sub-nets the role is able to operate. Operation permissions and management
resources are two aspects of a role. They are defined independently, but when
a role is used, the privileges of the role are the intersection of two aspects.
ii. Role group
A role group is an aggregate of roles. Therefore, authorities of a role group are

the aggregate of those assigned to the roles. Via role group, it becomes very
convenient to assign authorities to the system administrator or sub-net
administrators. This is because, generally, an administrator's authorities are
the aggregation of those assigned to common users. To assign authorities of
many roles to an administrator, use the role group directly. Therefore, role
group facilitates greatly assignment and management of user authorities.
iii. User
Users refer to the persons who are able to login and operate the U31 system.
While creating a user, the system administrator defines the authorities given to
the user by specifying his roles and role group; besides, by setting the user's
department, he determines which executive group the user belongs to. Overall
management of users is finally implemented.
2. Relational model
The following figure describes the relationships among user, role group, role, and
operation permissions and management resources which are defined in the role.

Figure 2-1 Security Management Relational Model
From the above figure, we can clearly come to the conclusion that:
i. A user's administration authorities are decided by his roles and role group.
ii. A role group is a collection of one or more roles, so the authorities of a role
group are the aggregate of those assigned to the roles.
iii. A role's authorities are defined by both operation permissions and

management resources.
2.4.2 Security Management Features
1. Security event
U31 records security event logs such as authentication failed, user blocked, and
user prohibited in terms of user settings to help administrator aware of accounts
status and manage users’ accounts.
2. Security alarm

If account is blocked, U31 generates corresponding alarm to remind administrator.
3. Login time
System is able to set login time period, only during that period when users are
available to login.
4. User account rules management
User may check and customize password length, password strategy, account lock
rules, expiration date of account and password and so on by security management
module. Customization satisfies security requirements at different levels. For
example: inputting wrong password for three times continuously, the user would be
blocked to avoid illegal login.
5. Login user management
i. Forceful disconnection of user access
Supreme administrator can disconnect user’s access compulsively, hindering

illegal operation to ensure system security.
ii. Set IPs supreme administrator can login
Since supreme administrator is able to do any operation with no restriction, IPs

available for a supreme administrator to login can be set in order to regulate
supreme administrator. Within IPs range set already, supreme administrator
can login; otherwise, it cannot even if the user name and password are correct.
iii. Modify all users’ passwords
Supreme administrator can change all users’ passwords except administrator,

with no restriction of cryptogram rules. It can change all users’ passwords into
an identical one. This enables administrator to initiate all users’ passwords at
one time and avoid other users, especially illegal ones logging in, better
guaranteeing system security.
iv. Check user’ block status, unblock user

Administrator knows about blocking status of user at anytime, and can unblock
them. System enables user to unblock automatically, which can be set with
automatic unblock time in account block rules.
v. Interface locked
If certain UE interface not be operated during a period of time, it would be

locked automatically. User has to re-login to avoid illegal users attack. User
also can lock the UE manually.
System administrator or current user can unlock the UE after entering the
password.
6. Node hardening
Node hardening includes a number of recommendations and scripts in order to

protect network nodes from accidental and malicious operations.
Recommendations and scripts are provided to harden nodes like U31 server.
Detailed specifications are available and cover:
i. Solaris, CGSL, and AIX
ii. Windows Server 2003 above
iii. Oracle and MS SQL
2.5 Log Management
Log management is an effective tool which used by system administrator to trace the
running status of system, failure position, and user ’s status of network. Common users
also could use it to review the history of operation and get to know the running status of
system.
U31 log includes system, security and operation logs.
1. Operation log

Operation log records the information about user operation, such as log ID,
operation level, user name, operation name, host computer address, command
function, detailed information, operation result, failure reason, access mode,
operation object, operation start time, operation finish time, and associated log
information.
2. Security log
Security log records the users logging in information, including log ID, user name,
host computer address, log name, operation time, access mode, and detailed
information.
3. System log
System log records the mission completed situation of server. That includes log ID,
level, origination, log name, detail information, host computer address, operation
start time, operation end time, associate log information.
Log management includes the following log operations:
1. Log inquiry
User can set conditions of inquiry filtration, inquiry log content, and the result can be
saved and printed out.
2. Log backup
System can backup log information as files. The log could backup automatically or
manually before it achieves the threshold of storage capacity or days. And the
threshold is set by user.
3. Log deletion
User can delete log information, which is useless or had already been backed up.

2.6 Topology Management
U31 topology management provides users with vivid display of the relationship between
NEs and operable network topology views. The topology interface adopts the popular
style: NE topology tree is on the left of the view and panoramic display of NE device on
the right. Users can define the map background and the latitude/longitude. The topology
functions are closely combined to each management module. Alarm information and
configuration can be viewed through the topology. Modules concerned with the
configuration, alarm, performance and diagnosis of each NE can be invoked. Topology
management provides with functions such as logical views, packet nodes, virtual NEs,
virtual links and so on. Users can manage the device and set the virtual NEs in packets,
which makes it easier for network display and analysis. The panoramic view can be
partially enlarged, searched and hierarchically displayed. Personalized interface setting
is available. Users can define their own interfaces, such as modifying icon type, color of
the interface and the size of the view and so on.
Topology management has the following functions:
1. Navigation tree
There forms the navigation tree when NE device is displayed in the form of a tree on
the interface. The correlation between topology views and the navigation tree nodes
is one-to-one correspondence. The navigation tree and topology views synchronize
each other. The navigation tree provides topology views with navigation and
topology views display the nodes specified by the navigation tree. The navigation
tree nodes provide functions related with these nodes, such as view of attributes,
modification of NE information and statistics of sub-nodes.
2. Topology display
Topology view displays a panorama of the whole network device’s topological

structure so that the NE device can be located on the topology view promptly. Users
can lock the location of the NE device icon so that it cannot be moved to other
location until it is unlocked. The node icon in the topology view shows the statistics
of the NE device, such as the number of NEs, links and packets and alarm
information under this node.

3. Topology display control
U31 supports the following operation on topology views: panoramic translation,

cascade zoom in, cascade zoom out, recovery, panoramic display and local zoom
in; browsing forward, backward and location to any layer of the topology that has
been browsed are supported; specified NE device can be searched on the topology
view; background map of the topology view can be replaced; map of the
world/China can be configured to realize large-scale NE device management; even
local map or map of the equipment room can be configured to make the display of
topology more humanized.
U31 will refresh the client after data synchronization is finished so as to ensure the
consistence of the topology data and configuration data. The NE device location set
in the topology will not be affected. Topology management module can be set in the
layout of topology view NE and deploy the display of NE according to the set layout.
Layout includes hierarchical layout, tree layout, radical layout, explosive layout and
equidistance layout.
4. Key CM/FM/PM information display
This function can display alarms, performance and configuration information of NEs
in topology views. All the information is refreshed according to practical network.
This feature helps to easily focus on NE configuration data, important alarms, and
KPI information in topology view. Easy navigation to CM/FM/PM interfaces is
available.
5. Topology view filter
U31 system topology view can be filtered by a filter tree made up of NE, packet, link
set, packet name, NE name and indication of link number. Or the filter can be
accomplished directly according to the NE names input by user.
6. Display topology data according to user authority
U31 will not display those NE device nodes or topology management modules on
which users do not have authority. In this way, the system security is enhanced.

7. NE device Node/alarm information of links between NEs
In U31 system, NE device node icon/icon of links between NEs can reflect the color
of the alarm that has the highest level on its corresponding physical device real time.
And the number and status of alarms that have different layers can be prompted.
Meanwhile, enquiry of alarms and notification is available.
8. Virtual NE/ virtual link
U31 system offers to establish virtual NEs/virtual links. Users can set virtual NEs to
indicate the external device or device nodes; or users can set virtual links to indicate
there is interaction or correlation between two NE nodes.
9. Logical view and packet Node
User of U31 system can establish a logical view of any hierarchy topology. In logical
view, the packet node is the logical node defined by users. NE device of physical
views can be allocated to the packet nodes.
10. Automatic discovery
GUI visualization interface can configure the conditions of automatic discovery by

SNMP protocol and IP protocol, including the conditions of single NE or bulk NEs
automatic detection. After NE automatic discovery, the system can automatically
create NE, also automatically create TDM link or Ethernet link between NEs.
11. NE poll function
User can set the poll tasks to enable automatic polling of the NE performance or
alarm data. In this way, users can detect whether the managed NEs are online.
The parameters of the polling tasks, including polling activate, the type of NE,
polling interval, polling retries time.
2.7 Version Management
U31 system provides version management functions to maintain and manage software
packages of Network Elements (NEs) by version in a unified way. By using the version

management functions in the client window of U31 system, users can distribute version
packages to NEs, control the status of version packages on NEs, view the version
packages on NEs, and manage the version packages of specific NEs.
The version management functions provided by U31 can be classified as two functions
sets: version repository management and NE version package management.
1. Version repository management
In U31 system, version packages that can be used by NEs are stored in a version
repository on an FTP server. Users can perform the following operations on the
version repository.
i. View the information about version packages stored in the version repository.
ii. Import a version package to the version repository.
iii. Delete a version package from the version repository.
2. Microwave NE version package management
Users can perform the following operations to manage and control the version
package(s) on a managed NE.
i. Query the version package information of an NE.
ii. Download a version package to an NE or multiple NEs, and check the

download result.
iii. Activate a version package on an NE or multiple NEs.
The activation operation only applies to the version packages in initializing or standby
status. The versions of the version packages cannot be lower than the current one.
1. Switch a version package on an NE from standby to active.
2. Delete a version package from an NE.
This function only supports the version packages in standby status on the NR8250,
NR8150, NR8120, and NR8950 NEs.

3. Fall back a version package on an NE in batches.
This function only supports the NR8250, NR8150, NR8120, and NR8950.
In addition, U31 system provides the patch and hot patch functions.
1. Patch: When a microwave NE is updated with a patch, you need to activate the
patch of the NE in U31 system.
2. Hot patch: This function helps to download patch versions for the running versions
without NE restart. You can activate a hot patch, activate hot patches in batches,
switch the hot patch status, and delete a hot patch.
Architecture of the Version Management Module
The version management module of the NetNumen™ U31 system includes three parts:
the client, the server, and the version repository. Figure 2-2 shows the architecture of the
version management module.
Figure 2-2 Architecture of the Version Management Module
The function of each part is described as follows:
1. Client
The client provides a GUI supporting user operations in the system.
2. Server

The server is the core of U31 system and provides a diversity of functions for the
centralized management and maintenance of network elements in a network, including
the version management function.
3. Version Repository
The version repository is used to store software packages of different versions, which
can be downloaded to NEs as needed.
Note:
The version repository and U31 server can be deployed on the same physical server or
different physical servers as needed.
2.8 License Management
License management is used to control the availability of functions on each microwave

NE. You can view the license information of an NE and manage the licenses on U31
client.
SR10 SR340 Microwave NE License Management Description
S340 license management includes the following operations:
1. Viewing license information of a microwave NE
2. Synchronizing license information of a microwave NE
3. Applying the license for a microwave NE
4. Exporting license information of microwave NEs in batches
NR8000 Microwave NE License Management Description
NR8000 license management includes the following operations:
1. Recovering license information of a microwave NE

2. Recycling license information of a microwave NE
Architecture of the NE License Management Module
The license management module is includes the server, the client, and the database.
The architecture of these components are in the displayed in Figure 2-3.
Figure 2-3 Architecture of the License Management Module
1. U31 server
The server is installed with U31 server software, which provides the functions for
managing the subordinate equipment in a centralized way.
2. U31 client
U31 client provides the GUI on which you can perform operations on the whole U31
system.
3. Database
The database is used to store license information of NEs in a unified way.
Note:

The database and NetNumen™ U31 server software can be installed on the same server,
or on separate servers.
2.9 Maintenance Management
U31 system provides the following modules for system maintenance and monitoring:
⚫ Task management module
⚫ System backup and restore module
⚫ System monitoring module
⚫ IT device monitoring module (optional)
The IT device monitoring module is only available when the IT management product
(ITMP) is selected during the installation of U31 server and client software.
1. Task management
The task management module predefines multiple maintenance tasks and

organizes these tasks by type in a navigation tree on the client GUI. When the start
time of a maintenance task is reached, the system automatically executes the task
in accordance with the default settings.
i. Automatically exporting microwave radio link information
ii. Automatically exporting inventory information
iii. Automatically backing up configuration data
iv. Setting a scheduled inspection
2. System backup and restoration
The system backup and restore module supports manual backup and restoration in
U31 system, including:

i. Backup
a) Entire database structure backup
b) Basic data backup
c) File backup
d) Log data backup and deletion
e) Alarm data backup and deletion
f) Performance data backup and deletion
ii. Restoration
a) Log data restoration
b) Alarm data restoration
c) Performance data restoration
Users can determine a path for storing backup data, delete unused data from
the system, and restore data from a backup file as needed.
3. System monitoring
The system monitoring module automatically identifies the application server and
the database server of U31 system and displays the server information on the client
GUI. The system monitoring functions include:
i. Monitoring the application server, including the memory usage, CPU usage,
and hard disk usage.
ii. Monitoring the database, including the database usage, table spaces, data
tables, and processes.
4. IT device monitoring
The IT device monitoring module detects the operating status of an IT device by

polling the device and receiving trap messages. After processing the received

messages, the module displays the performance data of the IT device on the client
GUI. If an exception or threshold crossing event is detected, an alarm is raised and
displayed.
2.10 Inventory Management
Inventory management is an important module in the U31 system. This module is used to
manage the inventory data of each Network Element (NE) managed by U31 system.
There is a predefined database that saves the inventory data in the system. The
inventory management module is used to keep the consistency between the actual
inventory information of NEs and the information in the system database.
The inventory management module provides the following functions:
1. Collecting inventory data of single Network Element (NE), single group, or all NEs in
the network.
Basic attributes of an NE unit. For example, the attributes of a board include its
serial number, manufacturer, and version information.
2. Querying inventory data of single NE, single group, or all NEs in the network.
This function is used to display the inventory data in the U31 system.
3. Exporting the query results to a designated file.
Users can export the inventory data to a file in the format of CSV, XML, TXT,
PDF,PRN, HTM, XLS, or XLSX.
2.11 End to End Management
The end-to-end management is used to create cross connections between the start and
end NEs of a route by specifying the restrictions. The system computes the routes
between NEs on both ends automatically.

The end-to-end management manages the TDM service and Ethernet service, and
perform troubleshooting on the two types of services as follows:
1. TDM service: Through specifying the route start point, route end point, and
constraint conditions, this function establishes a cross connection between the start
point and end point, and thus two points can connect to each other. The system
selects a route automatically between the two points.
Constraint conditions can also be set to restrict route selection.
2. Ethernet service: Refers to the group data service that uses the Ethernet signaling
architecture and the interface standard.
U31 EMS supports the following three Ethernet service types:
i. E-LINE: point-to-point service type.
ii. E-LAN: multipoint-to-multipoint service type.
iii. E-TREE: point to multipoint service type.
3. CES service: The circuit simulation service (CES) is a technology that carries
traditional TDM data and provides end-to-end transmission for the PDH and SDH
data stream on the packet switching network.
4. Clock topology: Through the clock topology view, you can check the clock topology
information of a network and log in to the NE LMT page to manage the clock.
The system provides a service management window for configuring and managing
microwave services by using end-to-end mode. This is more effective than configuring
microwave services on a single NE.
Note:
The end-to-end management functions should be supported by license.
End-to-end management includes the following functions:

1. Setting the display effects for the service topology graph
2. Querying services: queries the information of services meeting the specified

conditions.
The following service querying functions are provided:
i. Filtering services
ii. Querying the services carried by microwave
iii. Querying the client-layer services carried over the server layer
iv. Querying the subnet links of a service
3. Operating services in batches
The following batch functions can be performed on end-to-end services:
i. Discovering service automatically
ii. Importing services in batches
iii. Exporting services in batches
4. Maintaining services
The following service maintenance functions are provided:
i. Querying current alarms (including server-layer alarms)
ii. Querying current performance (including the server-layer performance)
iii. Setting the service loopback
5. E2E service diagnosis
The following E2E service troubleshooting functions are provided
i. TDM service troubleshooting
a) Automatic discovery of a TDM service

b) Checking TDM service consistency
c) Automatic fault diagnosis of a TDM service
d) BER test
ii. ETH service diagnosis
a) ETH service link trace test
b) ETH service loss measurement test
6. CES services
i. Managing CES Services
a) Creating CES services
b) Modifying CES services
c) Activating or deactivating CES services
d) Querying CES history performance data
e) Automatically discovering CES services
f) Deleting CES services
g) Querying CES historical alarms
h) Querying CES real-time alarms
ii. Configuring CES alarm thresholds
7. Clock topology
i. Checking Clock information
ii. Managing Clock services

2.12 Other Functions
2.12.1 Inspection Management
The microwave NE inspection function is used to check whether the NE is operating

properly by viewing the Indoor Unit (IDU) data, static routing, port status, inventory data,
alarms, performance data, log data and the hardware and software status of U31 server
The functions related to NE inspection are described as follows:
The inspections of the IDU, static routing, inventory information, and port status check
different data, which are introduced as follows:
1. Inspecting the IDU information
The data for inspection includes NE name, NE IP address, time zone, NE version,
device capacity, transmission/reception frequencies, modulation/demodulation, link
ID and bandwidth.
2. Inspecting the static routing information
The data for inspection includes NE name, NE IP, index, destination address,
gateway, subnet mask and enable status.
3. Inspecting the inventory data
The data for inspection includes NE name, NE IP, board type, board type
description, vendor, serial number, Boot version, software version, hardware
version, Erasable Programmable Logic Device (EPLD) version, last service time
and service times.
4. Inspecting the port status
The data for inspection includes Ethernet port, E1 port, STM1 port, air interface, and
whether the optical fiber is inserted.
5. Setting automatic export

Users can export the inspection result to the inspection directory on U31 server as
required.
6. Setting scheduled inspection
Users can schedule a time for inspection by year, month, or day. The system
performs the inspection automatically when the scheduled time is reached and
saves the inspection result to U31 server.
7. Exporting the inspection report immediately
Users can export the inspection result in accordance with the user specified
conditions, including inspection data objects and NEs.
2.12.2 Inspection Report
The inspection report function enhances the existing inspection function, making it more
suitable for on-site commissioning, maintenance, and acceptance. An automatically
generated report on the system saves much further manual processing and improves the
inspection efficiency.
The inspection report function is described as follows:
1. Automatically generates a report in XLS format. Shows the result in various formats
such as data, tables, and charts. No data collection from multiple sources is
required.
2. A report includes three parts:
i. Network inspection information and inspection result overview
ii. Inspection conclusion summary
iii. Details
3. If you click an inspection item in the summary page, the system shows the details of
the item, including the data, tables, and charts.

4. One-click inspection can be performed on NR8000 V2 NEs (NR8250 V2.0,

NR8150,NR8120, and NR8950), and the new NE types are compatible.
2.12.3 Ping Test
Users can perform the ping test to verify that the connection between U31 system and
microwave NE is normal. After the Ping operation is initiated, U31 system sends the
32-byte data packet to the NE. When receiving the data packet, the microwave NE sends
back the packet to the system. The system records the duration of sending and receiving
the packet to decide whether the connection is in good condition.
Steps:
1. In the NE tree or on the topology graph, right-click an NE, and select Ping. The Ping
dialog box is displayed.
2. The system performs the ping test. Information about the connection status
between U31 system and NE is displayed in the Ping dialog box
2.12.4 Route Tracing
Users can trace the route information of a managed microwave NE if the NE is not in the
same network segment as U31 server.
Select NE and click right bottom in ping menu, check network status between the system
and NE. Right-click to select the Trace Route menu, can trace the route information
about NE.
2.12.5 Online Help
Rapid and convenient operation guide is provided for user. This function helps the user
to get the system help quickly, operate efficiently and avoid or reduce mistakes.
By clicking F1, “help” can be directly opened. Online help can be displayed in active page
form and clicking on the F1 at different interface, displays different topics. When the user
meets question, it can be easily to find the solution.
User can locate certain help page by index and search function.

3 System Architecture
Architecture “client/server” is adopted by U31. Software includes client software and
server software, which are independent but are able to run on the same device.
Server, which is the core part, manages EMS Server applied IBM or DELL Server, the
database uses Oracle or MSSQL. Client applied Windows workstation, local Client and
remote Client.
3.1 U31 Architecture and Networking
3.1.1 LAN Networking
LAN networking is the simplest and the most common networking form. All U31 Server,
Client and NE are placed inside one LAN by Ethernet. U31 Server connects with NE that
it manages by LAN directly. This method requires U31 and NE that it manages in the
same position physically. See networking indications below:
Figure 3-1 LAN Networking

3.1.2 Remote Networking
If some NEs are placed in different networks from LAN where U31 resides, remote
networking should be adopted. Refer to the indication below:
Figure 3-2 Remote Networking
In terms of different transmission approaches, it can be divided into E1, TCP/IP, and so
on.
Remote networking has the unified basic topology structure and principles in spite of its
various forms. It utilizes appointed transmission equipments to realize accessing to WAN,
standard interface is equipped between transmission equipments and router; and router,
which is combined with switch, NEs, Server and Client, constructs LAN. Therefore,
remote networking is possible only if transmission equipments and router support remote
internetworking.
3.2 Hardware & Software Configuration for U31 system
Configuration Principle

Server hardware configuration should follow the following principles:
1. During hardware configuration planning, based on the size of the network, planning
future network expansion and hardware cost reasons. The hardware configuration
can be higher than the current network size requirements, but can’t be lower than
the current size of the network.
2. If select high availability system deployment program, it is recommended to use the

IBM UNIX server and the primary and secondary server’s configuration
requirements are the same.
The recommended hardware of U31 system is described below:
Table 3-1 Hardware Configuration for U31 system
Equipment Selection NT Server UNIX Server
DELL PER730: 2*Xeon IBM P7 740 Single Server:

Type I E5-2630V3 8C 2.4GHz 2*8GB 6*4.2G/32G/2*146G
DDR4 RDIMM /8*300G
DELL PER920: 4*Xeon IBM P7 740 Single Server:

E7-4809v2 6Core 1.9GHz 8*4.2G/64G/2*146G
Type II
8*4GB DDR3 RDIMM
1333MHz/2*300G
Table 3-2 Disk Array for U31
NT Server UNIX Server
Disk Array DELL MD3800F IBM V3700
U31 server software is composed of several modules to implement different functions,

including configuration management, fault management, security management, topology
management, performance management, inventory management, report management,
and so on. U31 server software provides the interface to NMS through network
management northbound interface module and offers interfaces to each NE through NE
adaptation module.
Software configuration of U31 system is shown as following table.

Table 3-3 Software Configuration for Server
Management Object NT Server UNIX Server
Operating system CGSL V4 AIX V6.1
Database Oracle EE/SE 11gR2 Oracle EE/SE 11g
Redundancy scheme software Skybility HA Service V2.6 IBM Power HA
3.3 Hardware & Software Configuration for Client
Minimum hardware configuration of Client that adopts PC workstation is shown below:
Table 3-4 Minimum Hardware Configuration for Client
Object Configuration
CPU > Dual-Core
Memory ≥ 2G
Built-in Hard Disc ≥ 80G
Software configuration for Client is shown below:
Table 3-5 Software Configuration for Client
Object Configuration
Operation System MS Windows XP/2007
Document Browsing Tool MS Office 2003 above/Acrobat reader
Anti-virus Software MacAfee/Norton/ Trend
3.4 System Interface
As is shown in Figure 1-1, U31 is located between NE layer and NMS layer, providing
interfaces to these two layers respectively.

3.4.1 Northbound Interface
U31 provides several types of northbound network management interfaces, accessible to

various NMS management system.
3.4.1.1 CORBA Northbound Accessing
Interoperation between U31 and NMS can be realized via CORBA interface, which
conforms to 3GPP R99/R4 specification.
CORBA (Common Object Request Broker Architecture) is open and distributed

calculation environment, a standard for computer network interconnection.
CORBA northbound interface of U31 supports alarm, performance, inventory and

configuration management.
3.4.1.2 Database Northbound Accessing
Data are got through database interface between U31 and NMS. U31 can customize DB
northbound interface and provide database views of corresponding configuration and
performance objects according to requirements and update the views real time.
Functions realized by this database northbound interface include:
1. Performance database interface
2. Configuration database interface
3. Inventory database interface
3.4.1.3 SNMP Northbound Accessing
U31 provides alarm interface in the form of SNMP and sends the processed alarms in
text to upper level network management.
Functions realized by this SNMP northbound interface include:
1. Alarm report

2. Alarm synchronization
3. Heartbeat Trap report
3.4.1.4 FILE (FTP) Northbound Accessing
It is a file interface. U31 saves inventory, performance and configuration data as files for
upper level network management to process.
3.4.2 Southbound Interface
U31 supports southbound interfaces as SNMP, FILE and HTTP.
Performance files via FILE protocol is transferred to ZTE EMS from NEs.
Alarm information via SNMP protocol is transferred to ZTE EMS from NEs.
4 System Reliability
4.1 Backup & Restore Solution
U31 System can provide backup & restoration Solution.
Usually, U31 System backup & restoration Solution can use following scenarios:
1. U31 system collapse scenario
The whole system collapse scenario is generally unusual. The system collapse is
classified into three cases: OS collapse, Oracle system collapse, U31 system
collapse, and database collapse.
2. OS collapse scenario
The OS collapse or some OS file lost.
3. U31 application collapse scenario

The U31 system collapse or some U31 system file lost.
4. DB collapse scenario
DB collapse or some DB file lost.
The backup solution enables integration of U31 and its environment with other
similar equipment connected to the network to a complete backup solution. The
backup solution can minimize the down-time of backing-up and restoring in case of
system failure.
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 of the
complete data of active server, including system file, database file and application
file. Using this policy, active 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.
Backup Mode and Policy:
1. Data can be backed up via IBM TSM or Symantec NetBackup software in any one
of the following three modes.
i. 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.
ii. 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).
iii. Differential backup

A special type of Cumulative Incremental Backup copies the files that have
been modified or created since a previous Full Backup.
2. U31 System Backup and Restore Solution provides following backup policy:
i. Manual immediate backup policy
After abundant data is mended, operator can trigger immediate Backup policy
manually, to backup data.
ii. Auto scheduled backup policy
Operator can set scheduled Backup policy automatically.
3. U31 System Backup and Restore Solution support to backup following kinds of
data:
i. OS and application data
ii. U31 system and application data
iii. Oracle database
4.2 High Availability Solution
U31 System can provide High Availability Solution.
Usually, U31 High Availability solution can use in following scenarios:
1. Software failures scenarios for High Availability
i. Application software breakdown caused by misuse
ii. Operating system errors
2. Hardware failures scenarios for High Availability
i. LAN failure
ii. Server failure

U31 System High Availability Solution is based on third party hardware and software,
includes Active Server, Standby server, and disk array. The network of High Availability
System use heartbeat line, Active Server and Standby server are in the same LAN.
Disk Array store U31 data and Oracle data, and adopted fiber to connect to Active Server
and Standby server.
Figure 4-1 High Availability Solution
In ZTE HA Solution, the active server and standby server are installed 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.
4.3 Disaster Recovery Solution
U31 System can provide Disaster Recovery Solution.

Usually, U31 Disaster Recovery Solution can use following scenarios:
1. Software failures scenarios for Disaster Recovery
i. Application system breakdown caused by misuse
ii. Operating system errors
2. Hardware failures scenarios for Disaster Recovery
i. LAN failure
ii. Server failure
iii. Storage device damages
3. Environment disaster for Disaster Recovery
i. Fire disaster
ii. Earthquake disaster
iii. Flood disaster
U31 System High Availability Solution is based on third party hardware and software,
includes Active U31 Server, Standby U31 server, and disk array. The network of Disaster
Recovery System can use IP or fiber.
Disk Array store U31 data and Oracle data, and adopted fiber to connect to Active U31
Server and Standby U31 server.

Figure 4-2 Disaster Recovery Solution
ZTE Disaster Recovery solution adapts dual server 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.

4.4 Operation Security
U31 sets users’ authorities by role and user management. 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.
The operation security function has the following features:
1. Screen lock
This function can prevent the operations of illegal users.
2. High-performance server and OS, such as IBM AIX,SUN Solaris, Linux CGSL and
Windows Server
3. Operation recording
If a user logs in and operates the system, the system reports this event to the U31.
4. Operations monitoring
The U31 system monitors the operations of all users and generates maintenance
reports about the operations. The admin user has the right to delete any user.
5. Complete log management and query function
Logs record system running statuses and user operations such as login,
authentication, and interface access. The detailed information includes user ID,
login time, logout time, date and time of important operations, and contents and
results of operations. The U31 system offers friendly interfaces for users to query
information under different conditions.

4.5 Software Reliability
U31 has many kinds of software security settings as follows:
1. 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.
2. Version check mechanism 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.
3. 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.
4. When services and process of Server go wrong, system generates alarm

messages.
4.5.1 Network Transmission
The network transmission function has the following features:
1. Separate multi-IP address network segment
The multi-IP address segment within the equipment is independent from U31. This
feature guarantees the safety of NEs.
2. SSH, SFTP and other third party software supported
The U31 system also supports SSL VPN, IPSec VPN but barely uses Telnet/FTP.
The protocols complied by the U31 system guarantee the safety of transmission.
3. Firewall required

The firewall must be installed and activated when the U31 system connects to the
external network to prevent the system from virus and junk mails.
5 Technical Indexes
This section introduces main technical indexes, including performance indexes, physical
indexes, power parameters, external interfaces, and so on.
5.1 Performance Indexes
See performance indexes of U31 in the following Table:
Table 5-1 Performance Indexes of U31
Items Index
Capacity of single server max number of NEs: 15000 equivalent NEs
Maximum online user numbers ≤100
Maximum number of concurrent users ≤40
Alarm query delay <2s
Performance data query delay <10s
Typical storage capacity of history alarm data 180 days (can be customized)
Typical storage capacity of performance raw data

30 days (can be customized)
(15 min granularity)
Typical storage capacity of performance hourly

90 days (can be customized)
data
Typical storage capacity of performance daily data 365 days (can be customized)
Typical storage capacity of history operation logs 90 days (can be customized)
MTBF (HA solution) 6480 hours
MTTR (HA solution) 0.5 hours
Availability index (HA solution) 0.99992

5.2 Physical Performance
It mainly refers to parameters such as dimension, weight, etc.
5.2.1 Dimension and Structure
Server and disk array of U31 adopt rack-mounted devices, installed inside standard 19”
rack. Client employs PC or workstation which accords with industrial standards. Server
and disk array are installed inside the same rack. See rack structure in the following
figure. Rack’s weight depends on actual configuration.
Table 5-2 Parameters of U31 Rack
Item Value
Without footprint margin: 2000; with footprint margin:

Height
Dimension 2100
(mm) Width 600
Depth 1000
5.2.2 Typical Overall Weight and Ground Weight Capacity of Equipment

Room
Typical overall weight and ground weight capacity of equipment room are shown below:
Table 5-3 Typical Overall Weight and Ground Weight Capacity of Equipment Room
Item Value
Weight of Rack ≤300 kg
Primary equipment room ≥450 kg/m2

Ground Weight Capacity
Other than primary equipment room ≥300 kg/m2
5.3 Power Supply
This type of indexes includes power range and power consumption.

5.3.1 Power Range
Input power nominal value:
220 V single-phase AC power is supplied, allowable input voltage ranges from 200 V to
240 V AC, frequency varies from 45 Hz to 65 Hz. See the table below for the range of AC
power:
Table 5-4 Range of U31 AC Power
Item Value
Working power supply 220 V, 50 Hz
Voltage range 200 V~240 V
Voltage frequency range 45 Hz~65 Hz
5.3.2 Power Consumption Indexes
See following table for power consumption indexes of U31. It is decided by actual
configuration.
Table 5-5 U31 Power Consumption Indexes
Item Value
IBM 740 610/488W
DELL PER730 1100/750W
Power consumption of system DELL PER920 1100/750W
IBM V3700 405W

DELL MD3800F 600W
6 Criteria
U31 abides by the following criteria:
ITU-T Proposal
ITU-T M.3000, Overview of TMN recommendations

ITU-T M.3010, Principles for a Telecommunications management network
ITU-T M.3016, TMN security overview
ITU-T M.3020, TMN Interface Specification Methodology
ITU-T M.3100, Generic Network Information Model
ITU-T M.3101, Managed Object Conformance Statements for the Generic
Network Information Model
ITU-T M.3200, TMN management services and telecommunications managed areas:

overview
ITU-T M.3300, TMN F interface requirements
ITU-T M.3400, TMN Management Function
ITU-T Temporary Document 69 (IP Experts) Revised draft document on IP access

network architecture
ITU-T X.701-X.709, Systems Management framework and architecture
ITU-T X.710-X.719, Management Communication Service and Protocol
ITU-T X.720-X.729, Structure of Management Information
ITU-T X.730-X.799, Management functions
RFC Proposal
RFC1157, Simple Network Management Protocol
RFC1213, Management Information Base for Network Management of TCP/IP based

internets: MIB-II
RFC1901, Introduction to Community-based SNMPv2

RFC1902, Structure of Management Information for Version 2 of the Simple Network

Management Protocol (SNMPv2)
RFC1903, Textual Conventions for Version 2 of the Simple Network
Management Protocol (SNMPv2)
RFC1905, Protocol Operations for Version 2 of the Simple Network Management

Protocol (SNMPv2)
RFC2037, Entity MIB using SMIv2
RFC2233, The Interface Group MIB using SMIv2
RFC1558, A String Representation of LDAP Search Filters
RFC1777, Lightweight Directory Access Protocol
RFC1778, String Representation of Standard Attribute Syntaxes
RFC1959, LDAP URL Format
RFC2251, Lightweight Directory Access Protocol ( v3)
TMF Proposal
GB901, A Service management Business Process Model
GB921, Enhanced Telecom Operations Map
GB909, Generic Requirements for Telecommunications Management Building Blocks
GB908, Network Management Detailed Operations Map
GB914, System Integration Map
GB917, SLA Management Handbook V1.5
NMF038, Bandwidth Management Ensemble V1.0

TMF508, Connection and Service Management Information Model Business Agreement
TMF801, Plug and Play Service Fulfillment Phase 2 Validation Specifications V1.0
TMF605, Connection and Service Management Information Model
NMF037, Sub-System Alarm Surveillance Ensemble V1.0
OMG Criterion
Interworking Between CORBA and TMN System Specification V1.0
Ministry of Information Industry (MII) and telecommunication criteria in China
YD/T 852-1996 TMN Design Principle
YD/T 871-1996 TMN Common Information Model
7 Acronyms
Acronyms English
3GPP 3rd Generation Partnership Project
CORBA Common Object Request Broker Architecture
CN Core Network
EMF Element Mediator Function
EMS Element Management System
FM Fault Management
GUI Graphical User Interface
ITU International Telecommunication Union
KPI Key Performance Indicator
MIF Management Information Function
MML Man Machine Language
MTBF Mean Time Between Failures

NAF Network management Access Function
NEF Network Element Function
NMC Network Management Center
NMF Network Management Function
QoS Quality of Service
SMS Short Message Service
TCP/IP Transmission Control Protocol/Internet Protocol
VPN Virtual private network

NETNumen R38

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

NETNumen R38

Încărcat de

Drepturi de autor:

Formate disponibile

NetNumenTM U31R58 Product

NetNumenTM U31R58 Product Description

V2.00 2011/11/08 Weng Yixin Not open to the third party

Update new feature description and U31

V2.40 2013/11/07 Weng Yixin Update U31 server configuration

Update U31 feature description ,NBI and

© 2019 ZTE Corporation. All rights reserved.

ZTE Confidential & Proprietary 1

2 ZTE Confidential & Proprietary

4.3 Disaster Recovery Solution ................................................................................ 45

5 Technical Indexes ........................................................................................... 50

ZTE Confidential & Proprietary 3

Figure 1-1 U31 Product Frame ........................................................................................... 6

Table 1-1 NEs Managed by U31 ......................................................................................... 6

4 ZTE Confidential & Proprietary

1.1 System Introduction

⚫ Based on the J2EE (Java 2 Enterprise Edition) platform.

⚫ Uniform management of microwave NEs.

⚫ Multiple access methods such as: GUI and Web.

⚫ Local, remote and reverse networking methods to adapt to different implementation

⚫ Support of server cluster to enable favorable load sharing, ensuring a huge

⚫ Hierarchical & decentralized management strategies to fit to carriers' OAM system;

ZTE Confidential & Proprietary 5

1.2 ZTE EMS Product Frame

U31 is located in the Element Management Layer of TMN (Telecommunication

Figure 1-1 U31 Product Frame

1.3 Network Elements Managed by U31

Table 1-1 NEs Managed by U31

Product Type Product List

6 ZTE Confidential & Proprietary

The main functions of U31 includes: fault management, configuration management,

i. Centralized monitoring of fault alarms: monitor the current status of the

ZTE Confidential & Proprietary 7

Performance management also provides real-time monitoring of the network and

Topology management provides a convenient way to know the distribution and

2.1 Fault Management

8 ZTE Confidential & Proprietary

2. Alarm query and statistical

3. Alarm graphic display & location

5. Alarms confirmation and negative confirmation

U31 supports users to confirm/ negatively confirm an alarm, meanwhile to record

ZTE Confidential & Proprietary 9

iv. Automatic confirmation: U31 confirms the designated alarm automatically by

v. Automatic recovery: U31 recovers the designated alarm automatically.

vii. Alarm correlation processing rules:

10 ZTE Confidential & Proprietary

d) Alarm suppression: as long as current main alarms exist or occur, the

9. Alarm knowledge base

10. Alarm synchronization

Alarm synchronization includes manual alarm synchronization and automatic alarm

11. External alarm access

External Alarm Access implementation and display external alarm, such as

12. Alarm box management

ZTE Confidential & Proprietary 11

13. Diagnosis and testing

2.2 Configuration Management

The configuration management includes following features:

U31 Configuration management supports batch operation such as batch updating

U31 supports automatic and manual synchronization of configuration data, if the NE

3. Configuration data availability check

12 ZTE Confidential & Proprietary

7. Multi configuration sets

2.3 Performance Management

Performance management is used to collect network performance data, evaluate the