netnumen u31 (gu) product description

Operator Logo

NetNumenTM

U31 (GU) Product Description

NetNumenTM U31 (GU) Product Description

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. I

NetNumenTM

U31 (GU) Product Description

Version Date Author Approved By Remarks

V1.00 2010-12-17 Zhang Beichen

Not open to the Third Party

V1.01 2011-03-04 Zhang Beichen

Add Business Object Module description

V2.00 2011-04-30 Zhu Bing

Add U31 system highlights detail description;

Refresh High availability, backup and restore, and disaster recovery solution;

Refresh northbound interfacing solution detail information;

Refresh U31 system index table.

V2.10 2011-05-20 Zhu Bing Change Typical storage cycle of history alarm data, hourly data and daily data of table 6-1

V2.20 2011-08-08 Zhu Bing

Put ERM description into System Features part. Put Meta-Frame solution into U31 Architecture and Networking part. Put High Availability Solution and Disaster Recovery Solution into System Reliability part. Refresh 4.2 and 6.1.

© 2013 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.


II ©2013ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

TABLE OF CONTENTS

1 Overview ......................................................................................................... 1 1.1 System Introduction .......................................................................................... 1 1.2 ZTE GU EMS Product Portfolio......................................................................... 1 1.3 Network Elements Managed by U31 ................................................................. 2

2 System Features ............................................................................................. 2 2.1 Fault Management ............................................................................................ 4 2.2 Configuration Management ............................................................................... 7 2.3 Performance Management ............................................................................... 9 2.4 Security Management ..................................................................................... 10 2.4.1 Nodes Consolidation ....................................................................................... 10 2.4.2 Relation Model of Security Management ........................................................ 11 2.4.3 Security Management Features ...................................................................... 12 2.4.4 Log Management ............................................................................................ 14 2.5 Topology Management ................................................................................... 14 2.6 Software Management .................................................................................... 16 2.7 System Management ...................................................................................... 17 2.8 Trace management......................................................................................... 17 2.9 Enhanced Report Management (ERM) ........................................................... 18

3 System Architecture ..................................................................................... 20 3.1 U31 Architecture and Networking ................................................................... 21 3.1.1 LAN Networking .............................................................................................. 21 3.1.2 Remote Networking ........................................................................................ 21 3.1.3 Meta-frame Solution ....................................................................................... 23 3.2 Hardware & Software Configuration for U31 system ....................................... 23 3.3 Hardware & Software Configuration for Client ................................................. 24 3.4 System Interface ............................................................................................. 25 3.4.1 Northbound Interface ...................................................................................... 25 3.4.2 Southbound Interface ..................................................................................... 26

4 System Reliability ......................................................................................... 26 4.1 Backup & Restore Solution ............................................................................. 26 4.2 High Availability Solution ................................................................................ 28 4.3 Disaster Recovery Solution ............................................................................. 29 4.4 Operation Security .......................................................................................... 31 4.5 Software Reliability ......................................................................................... 31

5 Technical Indices .......................................................................................... 31 5.1 Performance Indices ....................................................................................... 32 5.2 Physical Performance ..................................................................................... 32 5.2.1 Dimension and Structure ................................................................................ 32 5.2.2 Typical Overall Weight and Ground Weight Capacity of Equipment Room ..... 33 5.3 Power Supply ................................................................................................. 33 5.3.1 Power Range .................................................................................................. 33 5.3.2 Power Consumption Indices ........................................................................... 34 5.4 Environment Indices ....................................................................................... 34


ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. III

5.4.1 Ground Requirement ...................................................................................... 34 5.4.2 Temperature and Humidity Requirement ........................................................ 34 5.4.3 Cleanliness Requirement ................................................................................ 35 5.4.4 Lighting ........................................................................................................... 36 5.4.5 Barometric Requirement ................................................................................. 36 5.4.6 Air Pollution .................................................................................................... 36 5.4.7 Interface Indices ............................................................................................. 36

6 Acronyms ...................................................................................................... 36

7 Criteria ........................................................................................................... 37


IV ©2013ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

FIGURES

Figure 1-1 NetNumenTM U31 Product Portfolio ..................................................................... 2

Figure 2-1 Security Management Relational Model ............................................................ 12

Figure 4-1 LAN Networking ................................................................................................ 21

Figure 4-2 Remote Networking........................................................................................... 22

Figure 3-1 Meta-frame solution .......................................................................................... 23

Figure 3-2 Backup & Restore Solution ............................................................................... 27

Figure 3-3 High Availability Solution ................................................................................... 29

Figure 3-4 Disaster Recovery Solution ............................................................................... 30

TABLES

Table 4-1 Hardware Configuration for U31 system ............................................................. 23

Table 4-2 Software Configuration for Server ...................................................................... 24

Table 4-3 Minimum Hardware Configuration for Client ....................................................... 24

Table 4-4 Software Configuration for Client ........................................................................ 24

Table 6-1 Performance Indices of NetNumenTM U31 .......................................................... 32

Table 6-2 Parameters of NetNumenTM U31 Rack ............................................................... 32

Table 6-3 Typical Overall Weight and Ground Weight Capacity of Equipment Room ......... 33

Table 6-4 Range of NetNumenTM U31 DC Power ............................................................... 33

Table 6-5 Range of NetNumenTM U31 AC Power ............................................................... 33

Table 6-6 NetNumenTM U31 Power Consumption Indices .................................................. 34

Table 6-7 Requirements on Running Circumstances of NetNumenTM U31 ......................... 34

Table 6-8 Requirements on Temperature and Humidity ..................................................... 34

Table 6-9 Requirements on Dust Content and Particle Size ............................................... 35

Table 6-10 Restriction of Harmful Gas ............................................................................... 35


ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. 1

1 Overview

1.1 System Introduction

NetNumenTM

U31 is ZTE’s unified management system of mobile Network Elements

(hereinafter short as NEs), which deploy unified management on GERAN and UTRAN

networks.

U31 provides various management on the managed NEs such as fault management,

performance management, configuration management, software management, security

management, topology management and log management etc, which conforms to the

telecommunications specifications. In addition, U31 offers rich optional functions such as

northbounding interfacing, meta-framing, business objects, 3rd

party backup and

restoration, CBC solutions.

NetNumenTM

U31 system is developed on ZTE’s unified network management platform

architecture and adopts J2EE, which is available on various operating systems. Service

is independent from data layer, supporting various types of database. NetNumenTM

U31

manages and controls different networks via a network management work station that

interconnects with those networks. Centralized management is deployed so that the

management effect can be improved.

1.2 ZTE GU EMS Product Portfolio

NetNumenTM

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, which integrates with GSM and UMTS NEs, and

interconnects with the upper level NMS (Network Management System) through

northbound interface. See Figure 1 for the role of U31 in network.


2 © 2013ZTE CORPORATION. All rights reserved. ZTE Confidential Proprietary

Figure 1-1 NetNumenTM

U31 Product Portfolio

1.3 Network Elements Managed by U31

As is shown in Figure 1-1, the NEs managed by U31 can be divided into two types:

GERAN NEs and UTRAN NEs.

Wireless NEs managed by U31 include:

BSC and BTS of GERAN

RNC and Node B of UTRAN

SDR multi-mode base station

2 System Features

General Introduction of Main Functions

The main functions of NetNumenTM

U31 includes: fault management, configuration

management, performance management, security management, topology management,

system management, software management, signaling tracing and northbound interfaces,

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 NetNumenTM

U31 reduces the management interface points for the O&M

engineers, which mainly implements:

Centralized monitoring of fault alarms: monitor the current status of the network

equipments is performed

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

NetNumenTM

U31 provides the configuration management of all the NEs (Network

Elements) and offers operations such as adding, deleting, modifying and querying on NE

data. NetNumenTM

U31 provides a consolidated view of how the NEs are linked and

associated, which allows the operators to uniformly inquire and configure the link

parameters between NEs, thus enabling 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 potent support and

guidance for the decision-making layer, by horizontal comparison and analysis of the

whole network’s performance data collected by NetNumen

TM 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 agilely 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 Locate Alarm

Users can locate the fault according to the alarm; U31 then activates the configuration

management and locates the alarm source.

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

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).

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.

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.

Automatic confirmation: U31 confirms the designated alarm automatically by

anonymously and alarm receiving time.

Automatic recovery: U31 recovers the designated alarm automatically.

Automatic forwarding: If reported alarms meet the rules, the system will inform the

user who is specified in the rules by mail or SMS.

Alarm correlation processing rules:

Alarm merger: all current alarms which meet the rules are merged and

displayed as one alarm at the Client.

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.



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.

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 dry contact

alarm. And dry contact alarm configuration refer to configure the port accessed by

external dry contact alarm signal and normal circuit, therefore to customize special

alarms in terms of base station types.

12 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.

13 VIP site alarm monitor

Time to solve fault of VIP site is limited, so U31 system can customize the query on alarm

occurred time and real-time refresh, mark the sites list according to the fault solved time

by countdown sequence. And for those sites that are set to require attention, users can

inquire and make a statistics of the alarm level and alarm quantity within the six time

periods: within 1 hour, 1~2 hours, 2~3 hours, 3~4 hours, 4~5 hours, 5 hours, and detailed

alarm list can be shown in the statistics result.



2.2 Configuration Management

NetNumenTM

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:

Data configuration

Data synchronization

State management

Data export

Data import

1 Data Configuration

NetNumenTM

U31 system configures various NE data by GUI and MML command,

including creating, deleting, and modifying, querying and valid checking of configuration

data.

NetNumenTM

U31 system executes the MML command for configuration in single or by

batch, and also pre-implements the MML command file. U31 also provides quick

configuration module and configuration guide function.

Configuration management also provides shortcut tool at the same time, which can

compare, copy, and paste between different NEs.

2 Data Synchronization

NetNumenTM

U31 supports the synchronization of configuration data, if the NE

configuration data was changed, the system will inform the NetNumenTM

U31, and user

also can trigger synchronization in the NetNumenTM

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 State Management



State management mainly provides the management and query for various dynamic

resources and NE state, and the management operation such as block, unblock, and

switching, etc.

5 Data Export

NetNumenTM

U31 provides configuration data export, it enables user to export

configuration data in XML, CSV, TXT and database script formats etc, and it can

automatically export data periodically through strategic task.

NetNumenTM

U31 offers site migration tools, with which user can conveniently move parts

of sites from one BSC to another, it also can re-assign sites managed by two BSCs in

order to balance load.

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 Hardware Inventory

U31 system can collect physical assets of NEs and store the information in physical

assets database. Real-time monitoring of physical assets of NEs can be traced. The

interface to acquire asset data is provided to upper layer system. On the inventory view

interface, the inventory type and resource could be added, deleted, modified, queried,

and refreshed. Inventory information can be input and output for backup.

Besides, NetNumenTM

U31 has the following features:

Configuration set: multiple configuration data can coexist in the server, as well as

flexible handover and convenient comparison, reducing the risks at the stage of

network adjustment greatly.

Comparison of configuration data: comparing with configuration object and then

gives result report.

Configuration object copy: copy the whole sub-tree of configuration.

Detection on neighboring cell consistency: offer detection on consistency of

neighboring cell, if one attribute is modified, the other attribution will be modified

accordingly; check the single configuration for neighboring cell in whole network.

Site migration: support migration of BTS from one BSC to another. According to

configuration of original BSC, the target BSC generates related configuration

automatically.

Automatic detection on neighboring cell: import files into candidate neighboring cell

by Excel file, or directly configure candidate neighboring cell by user, system selects



candidate neighboring regularly and quantitatively through scheduling system, and

then establishes related adjacent relationship to synchronize to NE, which collects

performance data of neighboring cell handover.

2.3 Performance Management

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

network performance indices, 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 QoS Task Management

This feature provides QoS task’s creation, deletion, query, modification, activation and

suspension, overdue deletion, detection and mark on QoS task when configuration

module deleting measurement object, QoS task alarms and alarm synchronization etc.

QoS task management calculates the indices based on the data uploaded by the

corresponding QoS tasks. It will report an emergency once the data are over the

threshold value, and send the alarm information to the alarm module.

3 Indices Management

This feature manages indices addition, modification, delete, view, print, import and export,

etc.

NMS provides default KPI indices. However, users can define the KPI indices they need

according to their own requirements.

4 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 NMS

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.

5 Integrity check of performance data



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.

And U31 also support performance data recollection, automatic or manual recollection

ways to recollect missed data are supported.

6 Counter Inquiry Processing

User can query the counter and print or save the results as Excel, PDF, HTML, CSV or

Text files.

7 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.

8 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

NetNumenTM

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 Nodes Consolidation

Recommendations and scripts are provided to harden nodes like U31 server.

Detailed specifications are available and cover:

Solaris & Linux



Oracle

2.4.2 Relation Model of Security Management

1 Basic Glossary

Role, role group, and user are the basic glossaries used in security management of U31

system.

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.

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.

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:

A user's administration authorities are decided by his roles and role group.

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.

A role's authorities are defined by both operation permissions and management

resources.

2.4.3 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

Forceful disconnection of user access

Supreme administrator can disconnect user’s access compulsively, hindering illegal

operation to ensure system security.

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.

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.

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.

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.



2.4.4 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.

NetNumenTM

U31 log includes system, security and operation logs.

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.

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.

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:

Log inquiry

User can set conditions of inquiry filtration, inquiry log content, and the result can be

saved and printed out.

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.

Log deletion

User can delete log information, which is useless or had already been backed up.

2.5 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 Topology view filter

NetNumenTM

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.

5 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.

6 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.

7 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.

8 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.

2.6 Software Management

U31 software version management supports the software loading, upgrade and version

management of NE devices. It brings the following benefits:

Software upgrade and load is realizable without going to the site

More convenient to manage the devices

Software management enables U31 to offer the function of NE software information list

viewing and exporting.

U31 system can check the compatibility of NE software version and save several sets of

software version concurrently. It can roll back when NE software loading/upgrade fails so

as to avoid risks.

Software version management supports concurrent operation. Software of several NE

devices can be loaded concurrently, greatly saving loading time.



The functions of software version management are listed below:

Software storing: save the software used by the device in the server of U31

Software delivering: deliver the software of U31 to the device

Software activating: modify the software version of the running device

Software viewing: view the software version of the running device

2.7 System Management

System management provides the network management system with an operating

platform for unified maintenance and management. Users can monitor and maintain the

application server and database server by means of this platform.

System management mainly includes maintenance of device, application server and

database server.

Device information such as host name, IP and operating system can be displayed

and information of device location can be saved by maintenance device.

Maintenance application server supports enquiring server performance, configuring

server monitoring parameters, configuring directory monitoring parameters, viewing

& displaying network management system version and so on.

Maintenance database server supports viewing database resource, operating

database table/set (backup/clearing of the specified table), configuring database

monitoring parameters, and backing up database and so on.

U31 offers MML (Man Machine Language) commands to maintain NEs. The format of the

commands conforms to ITU-T specification. Management of network management object

can be realized by way of inputting single command or batch commands in the command

terminal.

Users can use the command terminal in the network management client or logs in directly

in telnet and uses command lines.

2.8 Trace management

The trace function of U31 includes: GERAN and UTRAN signaling trace.

GERAN

The primary tasks of this system are: to trace BSC-related signaling, to convert the

signaling flow into texts to facilitate observation, to save the traced signal for future

references, and to provide filtering function for the ease of observation. The protocols



concerned include: An interface No.7 MTP, SCCP and mobile application protocol (for

BSSMAP details, refer to specification 08.08), Abis interface layer three messages (for

RSL, refer to specification 08.58 and RR, MM, CC refer to 04.08) and Abis interface

internal management messages. It is used to facilitate the reference of signaling workflow

and the findings of signaling coordination errors.

UTRAN

Signaling trace objects are: UE (may be IMSI number), CELL (cell ID) and Node B (Node

B ID). It supports following tasks:

RNLC IU trace is to tail signaling at Iu interface, which refers to signaling interactivity

between RNC and CN. Main parameters are PS domain trace and CS domain trace.

RNLC IUB trace (IUB_CELL and IUB_Node B) is to tail signaling at Iub interface and

signaling between RNC and Node B. CELL and Node B are included.

RNLC IUR trace is to tail signaling at Iur interface, which is signaling among RNCs. Here

users refer to the neighboring RNC. Then it’s possible to tail signaling between current

connected RNC and the neighboring RNC.

RNLC UE trace is to tail UE signaling, which is signaling between UE and RNCs. Two

kinds of traces are included: Single UE and cell multi-UE trace.

RNL cell detection set trace is to tail signaling of RNL cell set.

RTV trace (RTV_CELL and RTV_UE) is to tail real-time UE or cell information.

2.9 Enhanced Report Management (ERM)

U31 system supports integrating with BO report system, adopting Business Objects

enterprise performance management software, U31 system can provide graphic display

and analysing function. With BO interactive visual models, it enable to quickly display

graphically, including network data model, such as alarms, configuration, performance

and other data, display as dynamic charts, graphs and interactive vivid analysis,

visualization, and convenient for user to search statistics relevant data.

Report System Architecture:



Support for multiple system to create unifying reporting

U31 system supports network element type of entire network and multi-function

integrated reports to meet the operators to analyze the whole network operations data.

Reporting system supports multiple system unifying reporting capabilities.

Performance report provides group reporting capability

BO reporting system support analyzing respective reporting functions all of the systems

management domain network element logical groups according to user-specified

category.

Comprehensive report customization

BO reporting system provides performance data of all management fields, supporting to

output reports, for the application scenarios of analyzing and querying performance data.

Performance reports provide cell busy hour statistics according to counter and KPI.

BO reporting system can define busy hour based on some counter and KPI, and

supporting statistical inquiry based on the counter or KPI busy hour.

Performance reports provide statistics based cell group busy hour

According to day busy hour statistics or cell busy hour of counter and KPI statistics,

performance reports support to create statistic reporting based on the cell group busy

hour. The day busy hour of cell group is the hour that maximum sum of all cells busy hour

of cell group.

Performance reports provide weekly and monthly busy hour statistics.



Performance reports provide weekly and monthly busy hour statistics based on day busy

hour statistics, cell busy hour of counter and KPI statistics, and cell group busy hour

statistics.

Performance reports provide indicators of coloring function

Performance statistics provided coloring function according to predefined coloring

template of indicator range, convenient for user to define logic statistics of object.

Provide reports unify analysis function of performance and alarm.

Performance reporting system provides unified report, analyzing performance statistics

data, alarms information and other data sources. Unified report can satisfy scenarios of

analyzing wireless indicator.

Provide data visualization capabilities

BO report provides creating data chart function, the chart of the data generated can be

specified column, dimensions.

OLAP drill-down capabilities

OLAP drill-down function supports to drill-down form KPI indicator to specific counter

value, convenient for user to locate problems.

Provide GUI and WEB format of the report

Standard KPI reporting and user-defined KPI report published on the server, customers

browse through the Brower. Customer can query statics by Brower, displaying as web

mode, convenient for user to query data and report, without installing of specialized client

software.

Provide regular reporting

Regular reporting system supports automatically generating regular reports.

Provides automatic forwarding the report

Report can be forward to FTP server or email box.

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 NMS Server applied IBM, SUN or HP Server, the

database uses Oracle. 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

Few types of equipment are required for LAN networking. Select certain quantity of

100M/1000M adaptive HUB and twisted pair which accords with primary equipments

numbers (Server numbers and Client numbers).

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:

RNC/BSC RNC/BSC

LAN

TCP/IP

Hub/Switch

Client Terminal U31 Server



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 HUB, NEs, Server and Client, constructs LAN. Therefore, remote

networking is possible only if transmission equipments and router support remote

internetworking.

Hub

Router

LAN

RNC/BSC

RNC/BSC

Remote Client

LAN TCP/IP Hub/Switch

Client Terminal U31 Server

Router

Router WAN Hub/Switch

Remote Client RNC/BSC

RNC/BSC



3.1.3 Meta-frame Solution

Figure 3-3 Meta-frame solution

U31 provides remote access function without installation of client and provides the

concurrent control to multi remote client’s access management and centralized access

for one entrance of multi-application. Provides a safe isolation between access point of

remote client and U31 server, also provides remote access solution for U31 management

as the requirement of low bandwidth of remote client.

U31 software can be installed on Citrix server, Multiple Citrix client connect with U31

server by Citrix server, and multiple Citrix server made as Farm group, providing service

and load balance.

Citrix client is no need to install U31 client software, just need to install Citrix client

software, and it is only severy Mbyte. ICA Session can be set up between Citrix client and

Citrix server, Citrix client use ICA Session to run U31 client software and log on U31

server.

3.2 Hardware & Software Configuration for U31 system

The hardware of U31 system is described below:

Table 3-1 Hardware Configuration for U31 system

Capacity



Brand 5000 CS or

12500 TRX

10000 CS or 25000 TRX

15000 CS or

37500 TRX

IBM Server+

EMC Disc Array

CPU: 4*4.2GHz

(2CPU, 2 core)

RAM: 32G

Disc:

7*300G (GSM)

9*300G (UMTS)

CPU: 6*4.2GHz

(3CPU, 2 core)

RAM: 64G

Disc:

10*300G (GSM)

15*300G (UMTS)

CPU: 8*4.2GHz

(4CPU, 2 core)

RAM: 64G

Disc:

13*300G (GSM)

23*300G (UMTS)

SUN Server+

EMC Disc Array

CPU: 8*1.4GHz

(1CPU, 1 core)

RAM: 32G

Disc:

7*300G (GSM)

9*300G (UMTS)

CPU: 8*2.53GHz

(2CPU, 4 core)

RAM: 32G

Disc:

10*300G (GSM)

15*300G (UMTS)

CPU: 16*2.53GHz

(4CPU, 4 core)

RAM: 64G

Disc:

13*300G (GSM)

23*300G (UMTS)

U31 server software is composed of several modules to realize different functions,

including configuration management, fault management, security management, topology

management, performance management, report management, character terminal, 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-2 Software Configuration for Server

Object Server Configuration

Operation System AIX/Solaris/Linux

Database Oracle

Redundancy Solution Power HA/VERITAS

3.3 Hardware & Software Configuration for Client

Minimum hardware configuration of Client that adopts PC workstation is shown below:

Table 3-3 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-4 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.4 System Interface

As is shown in Figure 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 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 Alarm database interface

2 Performance 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.4.1.4 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 connects GERAN and UTRAN network devices via MML (Man Machine Language)

interface. Performance files via FTP/sFTP protocol is transferred to ZTE EMS from NEs.

4 System Reliability

4.1 Backup & Restore Solution

ZTE NetNumenTM

U31 System can provide backup & restoration Solution.

Usually, ZTE NetNumenTM

U31 System backup & restoration Solution can use following

scenarios:

1. NetNumenTM

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. NetNumenTM

U31 application Collapse Scenario

The NetNumenTM

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.

ZTE NetNumenTM

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 OMC server, including system file, database file and application

file. Using this policy, OMC 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 4-1 Backup & Restore Solution

U31 backup and restoration system including OMC Server, backup server, disk array,

and tape library. And network use dual 1000M switch LAN.

Backup solution based on third party software IBM TSM or Symantec NetBackup.

Backup Mode and Policy:

Data can be backed up via IBM TSM or Symantec NetBackup software in any one of

the following three modes.

1. 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.

2. 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).

3. Differential Backup

A special type of Cumulative Incremental Backup copies the files that have been modified

or created since a previous Full Backup.

Disk Array Tape Library

OMC Server Backup Server

Fiber Fiber

Switch

1000M



ZTE NetNumenTM

U31 System Backup and Restore Solution provides following

backup policy:

1. Manual immediate Backup policy

After abundant data is mended, operator can trigger immediate Backup policy manually,

to backup data.

2. Auto scheduled Backup policy

Operator can set scheduled Backup policy automatically.

ZTE NetNumenTM

U31 System Backup and Restore Solution support to backup

following kinds of data:

1. OS and application data

2. OMC system and application data

3. Oracle Database

4.2 High Availability Solution

ZTE NetNumenTM

U31 System can provide High Availability Solution.


U31 High Availability solution can use in following scenarios:

1. Software failures scenarios for High Availability

Application software breakdown caused by misuse

Operating system errors

2. Hardware failures scenarios for High Availability

LAN failure

Server failure

ZTE NetNumenTM

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 1000M switch LAN, so 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-2 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

ZTE NetNumenTM

U31 System can provide Disaster Recovery Solution.


U31 Disaster Recovery Solution can use following scenarios:

1. Software failures scenarios for Disaster Recovery

Application system breakdown caused by misuse

Operating system errors

2. Hardware failures scenarios for Disaster Recovery

LAN failure

Server failure



Storage device damages

3. Environment disaster for Disaster Recovery

Fire disaster

Earthquake disaster

Flood disaster

ZTE NetNumenTM

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-3 Disaster Recovery Solution

ZTE Disaster Recovery solution adapts dual OMC 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.

4.4 Operation Security

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.

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.

Employ SSL, SFTP, and etc. software; install firewall to prevent system from external

illegal attacks; adopt anti-virus software to scan virus.

5 Technical Indices

This section introduces main technical indices, including performance indices, physical

indices, power parameters, external interfaces, and so on.



5.1 Performance Indices

See performance indices of NetNumenTM

U31 in the following Table:

Change Typical storage cycle of history alarm data, hourly data and daily data of table

6-1

Table 5-1 Performance Indices of NetNumenTM

U31

Items Index

Max online user numbers 50

MML response delay <2 s

Alarm processing delay <5 s

Performance data processing delay <1 m

Typical storage capacity of history alarm data 90 days

Typical storage capacity of performance raw data 7 days (with 15 min. granularity)

Typical storage capacity of performance hourly data

60 days

Typical storage capacity of performance daily data 365 days

Typical storage capacity of history operation logs 90 days

MTBF (HA solution) 6480 hours

MTTR (HA solution) 0.5 hours

Availability indicator (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 NetNumenTM

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 NetNumenTM

U31 Rack

Item Value

Dimension (mm)

Height Without footprint margin: 2000; with footprint margin: 2100

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

Ground Weight Capacity Primary equipment room ≥450 kg/m

2

Other than primary equipment room ≥300 kg/m2

5.3 Power Supply

This type of indices includes power range and power consumption.

5.3.1 Power Range

Input power nominal value, including DC and AC.

DC power supply -48 V DC, output voltage ripple is less than 200mV, sophomorically

weighted noise is less than 2 mV. Allowable working voltage ranges from -57 V to -40 V

DC. See the table below for the range of DC power:

Table 5-4 Range of NetNumenTM

U31 DC Power

Item Value

Working power supply -48 V

Voltage range -57 V~-40 V

Voltage output ripple < 200 mV

220 V single-phase AC power is supplied, allowable input voltage ranges from 176 V to

264 V AC, frequency varies from 45 Hz to 65 Hz. See the table below for the range of AC

power:

Table 5-5 Range of NetNumenTM

U31 AC Power

Item Value

Working power supply 220 V, 50 Hz

Voltage range 176 V~264 V

Voltage frequency range 45 Hz~65 Hz



5.3.2 Power Consumption Indices

See following table for power consumption indices of NetNumenTM

U31. It is decided by

actual configuration.

Table 5-6 NetNumenTM

U31 Power Consumption Indices

Item Value

Operational current ≤35 A

Power consumption of system

IBM 550 (4C 4.2GHz,32G) 695W

IBM 550 (6C 4.2GHz,64G) 916W

IBM 550 (8C 4.2GHz,64G) 1187W

SUN T5220( High Configured) 494W

SUN M4000( High Configured) 1447 W

EMC CX4-120C 685 W

HP RX2660 567 W

HP RX7640 2128 W

HP EVA 4400 346 W

5.4 Environment Indices

This type of indices includes ground requirements, temperature, humidity, etc.

5.4.1 Ground Requirement

Rack’s pick-up resistance is 0.1 Ω~0.3 Ω, ground resistance should be less than 1 Ω, and

protective grounding wire is able to be connected to earth by separated pile.

Adequate space between protection ground and surrounding signals, power and ground

should be spared in order to avoid damages on devices due to the high voltage.

NetNumenTM

U31 has following requirements on running circumstances:

Table 5-7 Requirements on Running Circumstances of NetNumenTM

U31

Item Value

Rack pick-up resistance 0.1 Ω~0.3 Ω

Ground resistance ≤1 Ω

5.4.2 Temperature and Humidity Requirement

NetNumenTM

U31 has following requirement on temperature and humidity:

Table 5-8 Requirements on Temperature and Humidity



Equipment

Temperature Relative Humidity

Long Term Operation

Short Term Operation

Long Term Operation

Short Term Operation

NetNumenTM

U31 0 °C~40 °C -5°C ~ 45°C 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.

5.4.3 Cleanliness Requirement

Dust inside equipment poses electrostatic absorption, which makes poor contact of

socket connector, impacting equipments’ life time and causing failure easily.

Following table shows the requirement of dust content and particle size:

Table 5-9 Requirements on Dust Content and Particle Size

Item Value

Max diameter (μm) 0.5 1 3 5

Max consistency (particle count/m3) 14×10

5 7×10

5 24×10

4 3×10

4

Description:

Dust is non-conducting, -magnetic and -corrosive.

Besides, specified requirements about salt, acid and sulfide content in air are made.

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. Refer to the following table for details:

Table 5-10 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



5.4.4 Lighting

Prevent direct sunlight from aging deformation of circuit board. Average illumination is

300 LX~450 LX free from glare.

5.4.5 Barometric Requirement

NetNumenTM

U31 requires barometric ranges from 70 kPa to 106 kPa.

5.4.6 Air Pollution

Causticity gas and smog are prohibited, and no smoking in equipment room.

5.4.7 Interface Indices

NetNumenTM

U31 provides following interfaces:

1 Communication Interface

1) Communication interface between NetNumenTM

U31 and its NEs, bearing

protocol is TCP/IP.

2) Document transmission interface between NetNumenTM

U31 and its NEs,

bearing protocol is FTP.

2 Physical Interface

1) Adaptive 10M/100M Ethernet interface.

2) Easy to expand to gigabit Ethernet as per requirements.

3) X.25 interface offered as per requirements.

6 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

GGSN Gateway GPRS Support Node

GSM Global System for Mobile Communication



GUI Graphical User Interface

HLR Home Location Register

ITU International Telecommunication Union

KPI Key Performance Indicator

MGW Media Gate Way

MIF Management Information Function

MML Man Machine Language

MSC Mobile Switching Center

MTBF Mean Time Between Failures

NAF Network management Access Function

NEF Network Element Function

NMC Network Management Center

NMF Network Management Function

OMC Operations & Maintenance Center

OMCR Operations & Maintenance Center –Radio

OMM Operation Maintenance Module

OSF Operation System Function

PAL Platform Application Layer

PFL Platform Framework Layer

QoS Quality of Service

SGSN Serving GPRS Support Node

SMS Short Message Service

TCP/IP Transmission Control Protocol/Internet Protocol

VPN Virtual private network

WCDMA Wideband Code Division Multiple Access

ERM Enhanced Report Management

7 Criteria

NetNumen TM

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

netnumen u31 (gu) product description

Documents

system management

zte corporation

u31 system highlights

proprietary information

fault management

configuration management

performance management

log management