ZTE NetNumen U31 (RAN) Optional Features Description - V1.10 - 20120705

NetNumen U31 RAN
Optional Feature Description

NetNumen U31 RAN Optional Feature Description
2017 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.
Version Date Author Reviewer Notes
Due to update and improvement of ZTE products and technologies, information in this document is
subjected to change without notice.
V1.0 2012-07-28 First Release
New Items:
ZXO-08-05-007 Services Observe Part

(FDL)
ZXO-08-09-006 SON Effect Evaluation
ZXO-08-09-006 Radio Parameter

Reconfiguration (FDL)
ZXO-08-10-003 Sleeping Cells Self-healing

(FDL)
NetNumen U31
V2.0 2013-06-21 Dongjia RAN Planning
team ZXO-08-10-004 Performance Cells Self-
healing (FDL)
ZXO-08-12-001 Script IDE
ZXO-08-12-002 Server Part Script Project

management
Modified Items
ZXO-08-07-001 Web Based Report

(GERAN & UTRAN & FDL)
TABLE OF CONTENT
ZTE Confidential & Proprietary 1

Introduction 8
1 Security Management.......................................................................................10
1.1 ZXO-08-03-001 Firewall Supported.....................................................................10
1.1.1 Summary.............................................................................................................10
1.1.2 Benefits............................................................................................................... 10
1.1.3 Description........................................................................................................... 11
1.2 ZXO-08-03-002 LDAP Interface to 4A Center......................................................11
1.2.1 Summary............................................................................................................. 11
1.2.2 Benefits............................................................................................................... 11
1.2.3 Description........................................................................................................... 11
1.3 ZXO-08-03-003 Two - Factor Authentication - USB Token...................................12
1.3.1 Summary.............................................................................................................12
1.3.2 Benefits............................................................................................................... 13
1.3.3 Description..........................................................................................................13
2 O&M Infrastructure...........................................................................................13
2.1 ZXO-08-04-001 Backup & Restore Solution........................................................13
2.1.1 Summary.............................................................................................................14
2.1.2 Benefits............................................................................................................... 14
2.1.3 Description..........................................................................................................14
2.2 ZXO-08-04-002 High Availability Solution............................................................15
2.2.1 Summary.............................................................................................................15
2.2.2 Benefits............................................................................................................... 15
2.2.3 Description..........................................................................................................16
2.3 ZXO-08-04-003 Meta-Frame Solution.................................................................16
2.3.1 Summary.............................................................................................................16
2.3.2 Benefit................................................................................................................. 16
2.3.3 Description..........................................................................................................16
2.4 ZXO-08-04-004 ITMP (IT node Management Platform) integration.....................17
2.4.1 Summary.............................................................................................................17
2.4.2 Benefits............................................................................................................... 17
2.4.3 Description..........................................................................................................17
2.5 ZXO-08-04-005 Microwave Management integration..........................................18
2.5.1 Summary.............................................................................................................18
2.5.2 Benefits............................................................................................................... 18
2.5.3 Description..........................................................................................................18
2.6 ZXO-08-04-011 Disaster Recovery Solution........................................................19
2.6.1 Summary.............................................................................................................19
2.6.2 Benefits............................................................................................................... 19
2.6.3 Description..........................................................................................................19
3 Tools..................................................................................................................20
3.1 ZXO-08-05-001 Internal CBC (GERAN & UTRAN)..............................................20
3.1.1 Summary.............................................................................................................21

3.1.2 Benefits............................................................................................................... 21
3.1.3 Description..........................................................................................................21
3.2 ZXO-08-05-002 External CBC System Interface (GERAN).................................22
3.2.1 Summary.............................................................................................................22
3.2.2 Benefits............................................................................................................... 22
3.2.3 Description..........................................................................................................23
3.3 ZXO-08-05-003 Intelligent Inspection..................................................................23
3.3.1 Summary.............................................................................................................23
3.3.2 Benefits............................................................................................................... 24
3.3.3 Description..........................................................................................................24
3.4 ZXO-08-05-004 Alarm Analysis...........................................................................25
3.4.1 Summary.............................................................................................................25
3.4.2 Benefits............................................................................................................... 25
3.4.3 Description..........................................................................................................26
3.5 ZXO-08-05-005 Site Status Analysis...................................................................27
3.5.1 Summary.............................................................................................................27
3.5.2 Benefits............................................................................................................... 27
3.5.3 Description..........................................................................................................27
3.6 ZXO-08-05-006 Out of Service Analysis..............................................................28
3.6.1 Summary.............................................................................................................28
3.6.2 Benefits............................................................................................................... 28
3.6.3 Description..........................................................................................................28
3.7 ZXO-08-05-007 Services Observe Part (FDL).....................................................29
3.7.1 Summary.............................................................................................................29
3.7.2 Benefits............................................................................................................... 29
3.7.3 Description..........................................................................................................29
4 Northbound Interface.......................................................................................30
4.1 ZXO-08-06-001 Itf-N CORBA FM........................................................................30
4.1.1 Summary.............................................................................................................31
4.1.2 Benifits................................................................................................................ 31
4.1.3 Descripition......................................................................................................... 31
4.2 ZXO-08-06-002 Itf-N CORBA CM (TDS & TDL)..................................................33
4.2.1 Summary.............................................................................................................34
4.2.2 Benefits............................................................................................................... 34
4.2.3 Description..........................................................................................................34
4.3 ZXO-08-06-003 Itf-N CORBA PM (TDS & TDL)...................................................34
4.3.1 Summary.............................................................................................................35
4.3.2 Benefits............................................................................................................... 35
4.3.3 Description..........................................................................................................35
4.4 ZXO-08-06-005 Itf-N Open Database View PM...................................................36
4.4.1 Summary.............................................................................................................36
4.4.2 Benefits............................................................................................................... 37
4.4.3 Description..........................................................................................................37
4.5 ZXO-08-06-006 Itf-N Open Database View FM(GERAN & UTRAN)....................37
4.5.1 Summary.............................................................................................................37
4.5.2 Benefits............................................................................................................... 38
4.5.3 Description..........................................................................................................38
4.6 ZXO-08-06-007 Itf-N FTP CM..............................................................................38
4.6.1 Summary.............................................................................................................38
4.6.2 Benefits............................................................................................................... 39

4.6.3 Description..........................................................................................................39
4.7 ZXO-08-06-008 Itf-N FTP PM..............................................................................39
4.7.1 Summary.............................................................................................................40
4.7.2 Benefits............................................................................................................... 40
4.7.3 Description..........................................................................................................40
4.8 ZXO-08-06-009 Itf-N SNMP FM..........................................................................41
4.8.1 Summary.............................................................................................................41
4.8.2 Benefits............................................................................................................... 41
4.8.3 Description..........................................................................................................41
4.9 ZXO-08-06-010 Itf-N FTP IM...............................................................................42
4.9.1 Summary.............................................................................................................43
4.9.2 Benefits............................................................................................................... 43
4.9.3 Description..........................................................................................................43
4.10 ZXO-08-06-011 Itf-N Import Radio & Transmission CM Data..............................44
4.10.1 Summary.............................................................................................................44
4.10.2 Benefits............................................................................................................... 44
4.10.3 Description..........................................................................................................44
5 Enhanced Report Management.......................................................................45

5.1 ZXO-08-07-001 Web Based Report (GERAN & UTRAN & FDL).........................45
5.1.1 Summary.............................................................................................................45
5.1.2 Benefits............................................................................................................... 45
5.1.3 Description..........................................................................................................46
5.1.4 Update record......................................................................................................47
5.2 ZXO-08-07-002 Data Extraction Filter (GERAN & UTRAN & FDL).....................47
5.2.1 Summary.............................................................................................................47
5.2.2 Benefits............................................................................................................... 47
5.2.3 Description..........................................................................................................47
5.3 ZXO-08-07-003 Radio Business Report (GERAN & UTRAN & FDL)..................48
5.3.1 Summary.............................................................................................................48
5.3.2 Benefits............................................................................................................... 48
5.3.3 Description..........................................................................................................48
5.4 ZXO-08-07-004 Report Customizable (GERAN & UTRAN & FDL).....................49
5.4.1 Summary.............................................................................................................49
5.4.2 Benefits............................................................................................................... 50
5.4.3 Description..........................................................................................................50
5.5 ZXO-08-07-005 Dashboard Support(GERAN & UTRAN)...................................52
5.5.1 Summary.............................................................................................................52
5.5.2 Benefits............................................................................................................... 52
5.5.3 Description..........................................................................................................53
6 RAN Sharing Support.......................................................................................53

6.1 ZXO-08-08-001 Security Enhancement for RAN Sharing....................................53
6.1.1 Summary.............................................................................................................54
6.1.2 Benefits............................................................................................................... 54
6.1.3 Description..........................................................................................................54
6.2 ZXO-08-08-002 CM/FM/PM Enhancement for RAN Sharing...............................55
6.2.1 Summary.............................................................................................................55
6.2.2 Benefits............................................................................................................... 55
6.2.3 Description..........................................................................................................55
6.3 ZXO-08-08-003 Itf-N for RAN Sharing.................................................................57

6.3.1 Summary.............................................................................................................57
6.3.2 Benefits............................................................................................................... 57
6.3.3 Description..........................................................................................................57
7 SON Infrastructure............................................................................................58
7.1 ZXO-08-09-001 SON Policy Configuration..........................................................58
7.1.1 Summary.............................................................................................................59
7.1.2 Benefits............................................................................................................... 59
7.1.3 Description..........................................................................................................59
7.2 ZXO-08-09-002 SON Monitoring & Control.........................................................60
7.2.1 Summary.............................................................................................................60
7.2.2 Benefits............................................................................................................... 60
7.2.3 Description..........................................................................................................60
7.3 ZXO-08-09-003 Planning Data Integration..........................................................61
7.3.1 Summary.............................................................................................................61
7.3.2 Benefits............................................................................................................... 61
7.3.3 Description..........................................................................................................61
7.4 ZXO-08-09-004 Automatic Multi-mode Base Station Software Installation &
Upgrade..............................................................................................................62
7.4.1 Summary.............................................................................................................62
7.4.2 Benefits............................................................................................................... 62
7.4.3 Description..........................................................................................................62
7.5 ZXO-08-09-005 Automatic Configuration Data Download and Activation............63
7.5.1 Summary.............................................................................................................63
7.5.2 Benefits............................................................................................................... 63
7.5.3 Description..........................................................................................................63
7.6 ZXO-08-09-006 SON Effect Evaluation...............................................................64
7.6.1 Summary.............................................................................................................64
7.6.2 Benefits............................................................................................................... 64
7.6.3 Description..........................................................................................................65
7.7 ZXO-08-09-006 Radio Parameter Reconfiguration (FDL)....................................65
7.7.1 Summary.............................................................................................................66
7.7.2 Benefits............................................................................................................... 66
7.7.3 Description..........................................................................................................66
8 SON Functions..................................................................................................66
8.1 ZXO-08-10-001 Automatic PCI Configuration Based on Centralized Assignment
(FDL & TDL)........................................................................................................67
8.1.1 Summary.............................................................................................................67
8.1.2 Benefits............................................................................................................... 67
8.1.3 Description..........................................................................................................67
8.2 ZXO-08-10-002 Automatic PCI Configuration Based on Distributed Assignment
(FDL & TDL)........................................................................................................69
8.2.1 Summary.............................................................................................................69
8.2.2 Benefits............................................................................................................... 69
8.2.3 Description..........................................................................................................69
8.3 ZXO-08-10-003 Sleeping Cells Self-healing (FDL).............................................70
8.3.1 Summary.............................................................................................................70
8.3.2 Benefits............................................................................................................... 70
8.3.3 Description..........................................................................................................70
8.4 ZXO-08-10-004 Performance Cells Self-healing (FDL).......................................71

8.4.1 Summary.............................................................................................................71
8.4.2 Benefits............................................................................................................... 72
8.4.3 Description..........................................................................................................72
9 Integrated Configuration Management...........................................................73

9.1 ZXO-08-11-001 Global Configuration Management.............................................73
9.1.1 Summary.............................................................................................................73
9.1.2 Benefits............................................................................................................... 73
9.1.3 Description..........................................................................................................74
9.2 ZXO-08-11-002 Global Data Consistency Check.................................................74
9.2.1 Summary.............................................................................................................74
9.2.2 Benefits............................................................................................................... 75
9.2.3 Description..........................................................................................................75
9.3 ZXO-08-11-003 Global Configuration Report.......................................................76
9.3.1 Summary.............................................................................................................76
9.3.2 Benefits............................................................................................................... 76
9.3.3 Description..........................................................................................................76
9.4 ZXO-08-11-004 Multiple Planning Area Management..........................................77
9.4.1 Summary.............................................................................................................77
9.4.2 Benefits............................................................................................................... 77
9.4.3 Description..........................................................................................................77
9.5 ZXO-08-11-005 Configuration Project Wizard.....................................................78
9.5.1 Summary.............................................................................................................78
9.5.2 Benefits............................................................................................................... 79
9.5.3 Description..........................................................................................................79
10 Script IDE Toolset.............................................................................................79

10.1 ZXO-08-12-001 Script IDE..................................................................................79
10.1.1 Summary.............................................................................................................80
10.1.2 Benefits............................................................................................................... 80
10.1.3 Description..........................................................................................................80
10.2 ZXO-08-12-002 Server Part Script Project management.....................................81
10.2.1 Summary.............................................................................................................81
10.2.2 Benefits............................................................................................................... 82
10.2.3 Description..........................................................................................................82
11 Acronyms and Abbreviations..........................................................................82

Introduction
This set of documents about feature description refers to:
Feature Description of Network Management system NetNumen U31 for radio access
network:
ZTE NetNumen U31 (RAN) Basic Feature Description;
ZTE NetNumen U31 (RAN) Optional Feature Description;
How to read this document using Feature ID?
The following table gives the features class.
The Classification Definition of ZTE U31 Features: ZXO-08-XX-YYY, the field 08 means
optional features, while XX field means as follows:
Class No. Class Description
01 Security Management
02 O&M Infrastructure
03 Tools
04 Northbound Interface
05 Enhanced Report Management
06 RAN Sharing Support
07 SON Infrastructure
08 SON Functions
09 Integrated Configuration Management
10 Script IDE Toolset
Related RAT and NE Type
The RATs managed by NetNumen U31(RAN) include GSM, UTRAN, TD-SCDMA,

eUTRAN FDD (LTE FDD), eUTRAN TDD (LTE TDD). U31 can manage AG for femto
solution as well as regular RAN.
NE type managed by U31 is:
Multi-mode base stations for GSM, UTRAN and eUTRAN:
Distribute base station: BS8700
Indoor base station: BS8800

Outdoor base station: BS8900A, BS8900B
Micro base station: BS8912
Base station for GSM and UTRAN only:
Micro base station: BS8906, BS8908
Pico base station: BS8112
BS8906, BS8908, BS8112
Base station for TD-SCDMA and eUTRAN TDD only:
Indoor macro base station: BS8300
Base station for eUTRAN TDD only:
Compact indoor base station BS8102
Relay base station: BS8912R
BS controller:
ZXG 10 iBSC for GSM
ZXWR RNC for UTRAN
ZXTR RNC for TDS-CDMA
UR9000 for GSM & UTRAN
AG: AG9000
1 Security Management
Security management makes the administrator of U31 able to management the security
policy of the U31 system, including U31 server hardening, IP network design and
transmission security in U31 and between U31 and managed NE.
U31 provides user management, user authorization and access authentication, these
functions are important to make system can be used safely and smoothly. Some
optional feature will make it easy to fit operators security policy, like LDAP client/ 4A
access control, two factors authentication.
Log management uses to check the problem of U31 executing and check operations to
audit the usage of system.

1.1 ZXO-08-03-001 Firewall Supported

First Release Time: 2012R1 or before
Basic/Optional: Optional
Feature Change: N/A
HW&SW Dependencies: N/A
Commercial Attention: Firewall Supported includes firewall function, but excludes the
firewall hardware; Hardware needs to be configured additionally.
1.1.1 Summary
U31 provides the facility for required ports to support the firewall.
1.1.2 Benefits
Firewall ports can be set in U31 server to improve system security and avoid malicious
attacks, ensuring U31 systems stability.
1.1.3 Description
In order to integrate a firewall, the operator needs to specify the numbers of the ports to
be used. And the user only needs to enable these ports. The other ports are disabled for
firewall.
1.2 ZXO-08-03-002 LDAP Interface to 4A Center

Feature Change: N/A
Commercial Attention: Need a connection to existing 4A server
1.2.1 Summary
U31 connect to 4A server via this interface, provide account management and access
authentication to each function / module / indicate components of U31.

1.2.2 Benefits
User can manage account in 4A center and authorize U31 access rights to account. The
4A server also can manage other systems account at same time.
User can use this account login each indicate part of U31 and NEs.
1.2.3 Description
The LDAP interface to 4A center is a part of centralize security solution of U31. It makes
U31 accounts can be managed by any 4A center use LDAP, to fulfill the requirement that
manage one account list using on several and increasing EMS and OSS applications.
U31 supports account management via this interface base on JDNI and LDAP V3,
include account create, modify and delete, right group create, modify and delete, to
make it possible to assign right groups to account and pass these authentication info
from 4A center to U31.
The right group is a set of operation and the scope of management object, it means
assinged user is allowed or forbided to apply these operation to certain object. U31
create these right groups and send the list of it to 4A center, it will use to authrity rights
to accounts.
When user use certain account login on U31, U31 will send authenticate request to 4A
server and get the rights of account, then promise user access system if the connection
between U31 and 4A center keep alive. If the connection interrupted, U31 will use stored
account info to authenticate access, these info got from 4A center before connection
break.
1.3 ZXO-08-03-003 Two - Factor Authentication - USB

Token
Feature Change: N/A
HW&SW Dependencies: needs HW&SW of PKI system include CA/RA and PKI
publisher. Needs USB Tokens for each user
Commercial Attention: N/A
1.3.1 Summary
U31 supports two-factor authentication based on USB token. Besides username and

password, user needs an USB key to access U31 system.
1.3.2 Benefits
Two-factor authentication enhances access security of U31. USB Token is a low cost
solution to implement.
1.3.3 Description
Digital certificate ( carried by USB token ) authentication is based of asymmetric
encryption algorithm and digital signature principle, it binds to user account and uses
when system needs to authenticate the access rights.
The digital certificate U31 using follow CA X509 standard, and USB token provides
PKCS #11 API interface. U31 supports local authenticate base on JCA/JCE and
PKCS#11, and supports to 3rd part CA/RA centralize authenticate.
As a part of solution, ZTE can provide CA/RA and LADP authenticate server base on
windows system.
2 O&M Infrastructure
The U31s O&M infrastructure is used to fit the high availability requirements from
operator. It includes the U31 server local high availability, remote disaster recovery, data
backup and restore.
The O&M infrastructure also includes the Access Mode except the client of U31. There
include telnet mode and WEB client via Citrix solution.
2.1 ZXO-08-04-001 Backup & Restore Solution

Feature Change: N/A
HW&SW Dependencies: 3rd party server hardware, 3 rd party backup and restore
software
Commercial Attention: ZXO-08-04-001 Backup & Restore solution based on third party
Hardware and third party backup and restore Software. This third party Hardware and
Software are not included in the feature of ZXO-08-04-001 Backup & Restore solution,
need to be configured additionally.

2.1.1 Summary
The Backup Solution performs backup and restore of U31 servers and other deployed
servers. The backup and restore solution is based on 3 rd party backup and restore
software.
2.1.2 Benefits
The backup solution can minimize the down-time of backing-up and restoring in case of
system failure.
The backup solution supports setting backup policy for the backup of the complete data
of U31 server, including system file, database file and application file. Using this policy,
U31 server can backup files during low system load, usually at night, the data could be
backed up without shutting it down into single user mode.
2.1.3 Description
Backup solution based on third party software.
Backup policy:
The backup server administrates the backup procedure and for each system a backup
policy is created. This backup policy includes information what shall backup and when it
shall be performed. A backup can also be initiated manually.
Backup type:
Incremental backups, differential backup and full backups are supported.
Backup data:
It enables the user to backup, archive log, and restore files that include NE and O&M
data files, OS, and DB etc.
External storage media:
The backup procedure allows storing data to both hard disk and tape or other removable
storage media. For example, when tape used, the element management server must be
connected to an attached magnetic tape library.
The backup system is connected to a separate high-speed network. There is no impact

on the U31 traffic during backup since all transactions are done on the backup VLAN
(Virtual Local Area Network).

2.2 ZXO-08-04-002 High Availability Solution

Feature Change: N/A
HW&SW Dependencies: 3rd party server hardware, 3rd party HA software
Commercial Attention: ZXO-08-04-002 High Availability Solution needs to configure third

party Hardware and third party HA Software. This third party Hardware and Software not
including in the feature of ZXO-08-04-002 High Availability Solution, it needs to be
configured additionally.
2.2.1 Summary
U31 has the 1+1 redundancy support for the server, as active and standby server. In
case of failure of the active server, standby servers will take over the job, without
affecting the functions of the system.
2.2.2 Benefits
Ensure high availability of the U31 system.
2.2.3 Description
The HA setting of the U31 system server physically deploys the dual server + shared
disk array. One server works as active server, the other works as standby server. In
normal running, the system is running on the active server, and the standby server does
not bear any system load. When the active server fails, it is automatically switched to the
standby server.
2.3 ZXO-08-04-003 Meta-Frame Solution

Feature Change: N/A
HW&SW Dependencies: Dedicated server hardware and Citrix software set
Commercial Attention: ZXO-08-04-003 Meta-Frame solution needs to configure third

party Hardware, such as PC server or switch, and third party Software. This third party

Hardware and Software not including in the feature of ZXO-08-04-003 Meta-Frame

solution, it needs to be configured additionally.
2.3.1 Summary
U31 provides web based access through Citrix solution presently.
2.3.2 Benefit
U31 supports web based access function which is able to realize accessing network
management system through web browser. By using browser, users shall connect to
U31 server and use relevant network management function without installing U31 client.
2.3.3 Description
U31 provides remote access function without installation of client and provides the
concurrent control to multi remote clients 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.
2.4 ZXO-08-04-004 ITMP (IT node Management

Platform) integration
Feature Change: N/A
HW&SW Dependencies: There needs 1 CPU core and 80G storage space to manage
less than 30 IT node, if it deploy on EMS server. The HW&SW requirement for dedicate
deployment, check the PD of ITMP.
Commercial Attention: N/A.
2.4.1 Summary
NetNumen U31 can integrate ITMP module to manage IT equipments/ nodes via
SNMP interface. It can manage server, DBMS, disk array, firewall, DNS server,
switch and router.

2.4.2 Benefits
User can conveniently manage and monitor IP devices.
2.4.3 Description
The ITMP module is an optional module use to manage IT nodes like server, DBMS,
disk array, firewall, DNS server, switch and router.
The ITMP module will be released as dedicate module of NetNumen U31. Not
included in Uni-RAN EMS which product name NetNumen U31 R18. User can install
ITMP module in existing EMS, with the suitable version.
The ITMP module can manage various type of IT equipment and 3 rd part software as
listed in ITMP module documents.
ITMP module can monitor the status, get alarms, measure performance of SNMP node
if the node support. IT nodes appear in topological view, alarms of it will display and
process as same as NEs alarms in Alarm Management functions, performance data can
be accessed by standard PM tools of EMS.
2.5 ZXO-08-04-005 Microwave Management integration

Feature Change: N/A
HW&SW Dependencies: There needs 1 CPU core/ 2G memory and 100G storage
space to manage less than 500 microwave node, if it deploy on EMS server.
Commercial Attention: N/A.
2.5.1 Summary
NetNumen U31 can integrate microwave management module to manage

microwave transmission equipments.
2.5.2 Benefits
RAN and microwave transmission can share EMS hardware and software.

2.5.3 Description
The microwave module is a plug in package use to manage microwave equipments, as
same as the package for RAT. These two packages can work together on one
NetNumen platform. User can treat microwave management as an optional package of
U31.
Microwave equipment often uses between site and other NE, and include in the whole
RAN project. It will be low cost and easy to maintain, if Microwave equipment and RAN
equipment share an EMS server.
2.6 ZXO-08-04-011 Disaster Recovery Solution

Feature Change: N/A
HW&SW Dependencies: 3rd party server hardware, 3rd party DR software
Commercial Attention: ZXO-08-04-011 Disaster Recovery Solution needs to configure

third party Hardware and third party DR Software. This third party Hardware and
Software not including in the feature of ZXO-08-04-011 Disaster Recovery Solution, it
needs to be configured additionally.
2.6.1 Summary
ZTE Disaster Recovery system provides software and hardware redundancy. It can
reduce the losses because of local power failures, flood, earthquakes, cyclone, fire, war,
tsunami, and mudflow effectively.
2.6.2 Benefits
Ensure high availability of the U31 system.
2.6.3 Description
ZTE Disaster Recovery solution adapts dual U31 system for 1+1 backup, including
active server, active disc array, standby server and standby disc array. Active server use
fiber to connect with active disc array and standby server also use fiber to connect with
standby disc array.
Transmission network adapts dual lines. Both lines are used as data backup line and
heartbeat line. Data changes will be replicated to standby system via backup 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 active
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 devicewithout 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.
3 Tools
These tools use to support O&M operations. Health check and stability report makes it
easy to evaluate the network condition and the maintain workload.
MML command terminal use to simplify the usage of MML. The online help supports to
get certain usage info and management information structure when user using GUI or
MML.
The optional features provide additional function like CBC, and deeply analysis functions
of EMS data.
3.1 ZXO-08-05-001 Internal CBC (GERAN & UTRAN)

Feature Change: N/A
3.1.1 Summary
Internal Cell Broadcasting Center (CBC) offers the basic operational function which
includes message edit, message send and message query. Meanwhile, CBC can
provide the planning and management function of CBC service.

As CBC operation client, U31 client is in charge of launching short message broadcast.
As CBC server, U31 server is in charge of broadcast receiving broadcast scheduling,
broadcast storage, the whole system operation, and maintenance management
functions.
3.1.2 Benefits
The basic function is implemented in U31, which can save the cost of buying CBC
center.
By using existing link of network transmission, extra network transmission equipment

can be saved.
User can plan and manage CBC simply and easily by the resource management of
CBC.
Friendly interface of message management can generate batch commands, which may
decrease workload of user.
3.1.3 Description
The internal CBC is integrated in U31, so user can launch CBC function through the link
between U31 and BSC. The CBC client and server communicate through internal
message; the mechanism uses request and response functions.
Main functions of internal CBC include:
Manage the basic resource as frequency, cell and broadcast zone.
Submit cell broadcast message.
Query cell broadcast message.
Delete cell broadcast message.
Modify or replace cell broadcast message.
Query message status in every cell.
Query history message.
Query load status in every cell.
Reset cell.

3.2 ZXO-08-05-002 External CBC System Interface

(GERAN)
Feature Change: N/A
Commercial Attention: ZXO-08-07-002 External CBC System Interface (GERAN)

includes CBC system interface, but excludes third party CBC system.
3.2.1 Summary
Cell Broadcast Center accesses U31 to forward message between CBC and BSC
through TCP/IP socket interface.
3.2.2 Benefits
Messages between CBC and BSC reuse the link between U31 and BSC to save
transmission resource.
Fast access ensures high-efficiency, prime-quality and rich value-added services.
3.2.3 Description
The interface between U31 and the third party CBC includes two parts: configuration
data and CBC message interface.
Daily configuration data organized by cell is stored in predefined folder and CBC gets
the configuration data periodically through FTP.
CBC connects to U31 through TCP/IP socket; the interface message is transmitted in
binary format. When CBC logs in U31, U31 provides a link to relay the message
between CBC and BSC through standard Asn.1 code flow. The interaction includes
replacing short message, deleting short message, inquiring short message, inquiring
CBCH load of cell, cell reset and cell broadcast mode setting etc. Heartbeat detection
mechanism is used to ensure the reliability of link and link is released when CBC user
signs out.
3.3 ZXO-08-05-003 Intelligent Inspection


Feature Change: N/A
3.3.1 Summary
Intelligent Inspection is adopted one-touch inspection for RAN U31 and NE equipments
automatically or manually, in order to keep the normal operation of systems and find
some system potential risks.
3.3.2 Benefits
Intelligent Inspection is used to replace the manual inspection before. It can check the
running RAN U31 and NE equipments regularly and automatically, which can save
OPEX for carrier.
Intelligent Inspection can help operators to get useful inspection item that is displayed
report to users with good readability.
3.3.3 Description
Intelligent Inspection can be divided into 4 function modules: Inspection Items
Management, Inspection Scenario Management, Inspection Task Management and
Inspection Report management.
Inspection Items Management:
It displays and manages all inspection items. Users can double click any item to display
its detailed configuration information. User also can set and modify the threshold of
inspection items.
Inspection Scenario management:
According to user habits and demand, one or more inspection items are organized into
the inspection set and save it as a scene template for user inspection tasks, reducing
complexity. The scene template contains the default scenarios and user-defined
scenarios.
1. Default scenarios
The default scenarios provide a common-mode version, the user can define scenarios
according to special scenarios. It support export and modify scenarios template.

2. User-defined scenarios
Can import and export as template, and can add, modify and delete scenarios template
Inspection Tasks Management:
Task management includes one-touch inspection task management, regular inspection

task management and one-touch collecting fault management. Task management
supports these three types of inspection tasks to create, activate, delete, and modify. It
can create, activate and delete for these three types task management.
Inspection Report Management:
When inspection tasks are finished, intelligent inspection tool will generate inspection
report. The inspection report contains the detailed inspection items information, such as
number of inspection items, time that the inspection tool costs, successful inspection
items and unsuccessful inspection items. The inspection report can be saved as MS
Excel or MS Word format.
The report in MS Excel format will be a series of file to difference object, the MS
Word format is one file which contents all info in chapters, easy to edit and add
conclusions.
3.4 ZXO-08-05-004 Alarm Analysis

Feature Change: N/A
3.4.1 Summary
U31 system can do statistics analysis about dedicated service alarms and
comprehensive alarm analysis, by which, the network status can be evaluated.
3.4.2 Benefits
This function can help users do specified alarm statistic and analysis; also it can bring
multiple service including diagram view and customized report.
3.4.3 Description
System can do statistics analysis of NE alarms and U31 alarms.

The detail function description can be viewed as below
1. The alarm statistics analysis function supports multiple filter condition including
different time, space and service type, by time, the time period and time
summarizing is supported, by space, the site type and summarized by site type are
supported, by service, different query setting which consists of wireless type, alarm
type and alarm code are supported
2. System supports alarm analysis according to alarm level, alarm location, and
second analysis to the summarized result is also supported.
3. System can do real-time analysis, alarm frequency analysis, alarm comparison

analysis and specified alarm code analysis
4. The query result can be displayed as tablet, pie and bar diagram, and it can be
exported.
Alarm Integrated Query
Users can set different filter condition including product type, query time, the alarm code,
alarm type to query the alarm result they concerned.
Alarm frequency and threshold statistics
Users can set different filter condition including product type, query time, the alarm code,
alarm type and frequency threshold value, to query alarm statistics result which exceeds
the threshold value.
Alarm comparative analysis
Users can set different filter condition including product type, query time and the alarm
code to find the alarm within a specified period of time, displaying result of the number of
new reported alarms and recovery alarms compared to the analysis of the number of
specified time (the time before the specified time.
Statistical analysis of historical alarm
Users can set different filter condition including product type, query time and statistical
objects, to query the history alarms of the period set by the users, also support alarm
summary by alarm level and subnets; and all history alarms can be displayed in a
subnet (if the alarm number over 20,000, and only displays the most recent 20000)
3.5 ZXO-08-05-005 Site Status Analysis


Feature Change: N/A
3.5.1 Summary
U31 supports site status analysis and statistics function.
3.5.2 Benefits
It can help users to understand site status easily and conveniently.
3.5.3 Description
By multiple filter condition set, including product type, query time, statistic object, the
specified sites status during specified time period can be summarized, also with the first
half and second half of the time period site status can be summarized.
Site Status analysis function is mainly used for statistical user-specified period of time,
the state statistics of the specified site, where the state includes: link-broken, fault and
working.
The output items of site status analysis include: EMS ID, sub network ID, Site ID, Site
Name, Statistic Time, Site Status and Out of Service Time.
The Site Status Analysis can be saved as excel file.
3.6 ZXO-08-05-006 Out of Service Analysis

Feature Change: N/A
3.6.1 Summary
U31 system can do statistics analysis about out of service which includes cell/base-
station/RRU out of service alarm analysis

3.6.2 Benefits
This function can help users to view the service alarm statistic more conveniently.
3.6.3 Description
Base-station out of service analysis
Users can set the query and filter condition by product type, query time, busy-hour time,
statistics object and etc, to query the base-station out of service information such as out
of service rate and the length in a set time period.
Cell out of service analysis
RRU out of service analysis
Also, it can be summarized by different NEID and sub-network.
The Out of Service Analysis can be saved as excel file.
3.7 ZXO-08-05-007 Services Observe Part (FDL)

First Release Time: 2013R1
Basic/Optional: Basic
Feature change: N/A
FDL: N/A
3.7.1 Summary
SOP collects and displays internal messages of key signaling process of certain cell in
real time, helps to confirm the signaling process problem of eNodeB. The key processes
include connection establish, release and handover.

3.7.2 Benefits
It is a real time application, do not need expansive equipment support and complex
trace control / collect process.
It is a light-weight application, collects less messages than regular tracing.
It focus on key process, make it easy to judge most of problem, and reduce the
knowledge level of user.
3.7.3 Description
The SOP supports to trace 20 UEs in 15 cells. The message type SOP collects is traffic
connection establish, connect release, handover and ERAB info.
The report time and content of the message is below:
1. Connect establish: reports when connect establish success or failure, the

information segments includes call type, GID, IMSI, RNTI, call result, failure cause,
begin and end time, connect establish process time, ERAB info.
2. Connection release: reports after the connection release, the information segments
includes release type, GID, IMSI, RNTI, release cause, ERAB info.
3. Handover (in and out): reports when the handover success or failure, the
information segments includes eNBID, cell ID, handover cause, handover result,
ERAB info, RSRP and RSRQ.
4. Additional ERAB info: reports when it success or failure to add or modify ERAB, or
finished to release RAB, the information segments includes ERAB info.
The observe tool supports to list the message, sort by column and calculate the success
rate.
4 Northbound Interface
Northbound interface use to communicate with 3rd part system to integrate U31 with
operators existing or higher level maintain or operation system.
The Northbound interface can be divided with the interface protocol and the information
type transmitting on it.
The interface protocol include CORBA, open DB, FTP file transmit, SNMP, SOAP.
The information type include CM, FM, PM and IM.

4.1 ZXO-08-06-001 Itf-N CORBA FM

Feature Change: N/A
Commercial Attention: ZXO-08-06-001 Itf-N CORBA FM provide CORBA FM interface,

but not including the cost of engineering implement, after-sale service, any other third
party hardware or software of NMS.
4.1.1 Summary
U31 supports Alarm IRP, which is used to describe controlled objects in FM,
accomplishing alarm information management.
U31 has abundant commercial experiences are integration with HP TeMIP on AM

module.
U31 also has abundant commercial experiences of integration with IBM NetCool.
4.1.2 Benifits
Itf-N lies in the middle of NMS and U31; northbound interface is offered from U31 to
NMS. In this case, CORBA Itf-N realizes inter-connection between NMS interface and
different suppliers U31.
4.1.3 Descripition
Via standard Itf-N CORBA interface, users can enter U31 system from different frame
NMS. U31 system offers standard CORBA interface and connect to upper O&M center
as supplement function of it.
Fault management function set case can be decomposed as: alarm reporting, alarm
synchronization, alarm processing and etc.
1. Alarm reporting function
It applies inform reporting function in inform management function, the alarm and
notification type is as below:
New alarm inform;
alarm change inform;

alarm clear inform
2. alarm information synchronization

Alarm information synchronization can be divided into two types: one is NMS query
alarm information during specified period from U31, another is NMS query alarm
information list of U31 (including not cleared and unconfirmed alarm).
The caller of alarm synchronization is NMS, the trigger points of NMS call alarm
synchronization has two cases: one is NMS launch call on its own when initiation
and link recover upon disconnect, another is U31 discover problem of itself, for
example, when it discover data in NE disagree with current data. Then U31 will
deliver request alarm synchronization inform to NMS.
3. Alarm acknowledgement
U31 interface supports NMS confirm alarm, once NMS acknowledged alarm, U31
will deliver alarm acknowledgement status changing inform to NMS which ordered.
4. Canceling alarm acknowledgement
U31 interface supports NMS cancel acknowledgement to alarms, U31 should

inform alarm acknowledgement status changing notification to NMS ordered.
5. Get alarm count function
U31 interface supports alarm count of different state and levels, user can import
parameter as relative filter, and the results will include alarm numbers of different
levels.
6. Add alarm description function
U31 interface supports adding alarm description, it is good for alarm information
process in multi NMS.
7. Clear alarm function
U31 should support clear alarm actively, on some special state, once NMS clear an
alarm, U31 will deliver the alarm clear notification to all NMS that ordered.
8. Notify ack state changed function
When certain alarm being acknowledged or cancelled acknowledgement, U31

should deliver changing notification of relative alarm acknowledgement state to
NMS that ordered.
9. Notify comments adding function
U31 will deliver inform to all NMS that ordered when completing adding alarm
comment.

10. Notify potential faulty alarm list function
U31 will deliver potential fault alarm information list notification to all NMS.
11. Notify alarm list rebuilt function
After U31 and NE connect again, or U31 discover that active alarm information is
not consistent with actual network resource, or it is suspicious of its alarm list, U31
can check data in alarm information list. After completing part of or all alarm
information list rebuild, U31 delivers alarm information list rebuild notification to
NMS, if the data check carried out after potential fault alarm information list
notification delivered, U31 should deliver alarm information list rebuild notification
even if not need rebuilding it, this notice will indicate whether need NMS
synchronization alarm.
4.2 ZXO-08-06-002 Itf-N CORBA CM (TDS & TDL)

Feature Change: N/A
Commercial Attention: ZXO-08-06-002 Itf-N CORBA CM (TDS&TDL) provide CORBA

CM interface, but not including the cost of engineering implement, after-sale service, any
other third party hardware or software of NMS.
4.2.1 Summary
U31 supports basic CMIRP, which is used to describe controled objects in CM,
accomplishing query, creation, modification, deletion operations, etc. of whole network
resource.
4.2.2 Benefits
4.2.3 Description
As the typical and efficient NBI in telecommunication domain, CORBA can satisfy the
need of unified Northbound interface of multi-vendor. CORBA is adopted by 3GPP 32

series. And CORBA mechanism mainly contains: IDL, ORB and IIOP (Internet Inter-ORB
Protocol). ORB is the middleware to establish Client/Server mechanism.
Users can access to U31 from different NMS systems through Itf-N CORBA interface.
U31 is fully compliant with TMN. As supplement function of U31, U31 supports standard
CORBA interface to be available to the upper layer.
U31 CORBA CM funciton includes, basic CM function, configuration information change

notification, and configuration informaiton synchronization.
4.3 ZXO-08-06-003 Itf-N CORBA PM (TDS & TDL)

Feature Change: N/A
Commercial Attention: ZXO-08-06-003 Itf-N CORBA PM (TDS&TDL) provide CORBA

PM interface, but not including the cost of engineering implement, after-sale service, any
other third party hardware or software of NMS.
4.3.1 Summary
U31 supports basic PMIRP, which is used to describe controled objects in PM,
accomplishing performence data collections, threshold monitoring and measurement
task management.
4.3.2 Benefits
4.3.3 Description
Performance management functionality includes performance data collection &
management, performance threshold management, and history performance data
management.
1 Performance measurement task
NMS users can deliver measurement tasks to U31 through the U31 CORBA interface.
The performance data that users want to obtain is specified in the tasks.

Users can create, suspend, resume, and stop the measurement tasks. Users are
allowed to query the measurement task parameters, including the MO, start/end time,
collection granularity, report interval, task details, and task status. If users find that the
collected performance data is not integrated or some data is missing, they can request
U31 to recollect the necessary performance data.
The collected performance data is saved as files. NMS periodically obtains the
performance data files or recollected performance data from U31.
2 Performance threshold tasks
NMS users can deliver threshold tasks to U31 through the U31 CORBA interface. When
thresholds are exceeded, U31 generates alarms and sends them to NMS.
Users can create, suspend, resume, and delete the performance tasks. Moreover, users
are allowed to query the threshold task parameters, including the MO, thresholds,
collection granularity, delta, direction, possible cause, and alarm severity.
3 History performance data query
NMS users can query the performance data files saved on U31 by specifying the query
criteria.
As the typical and efficient NBI in telecommunication domain, CORBA can satisfy the
need of unified Northbound interface of multi-vendor. CORBA is adopted by 3GPP 32
series. And CORBA mechanism mainly contains: IDL, ORB and IIOP (Internet Inter-ORB
Protocol). ORB is the middleware to establish Clent/Server mechanism.
Users can access to U31 from different NMS systems through Itf-N CORBA interface.
U31 is fully compliant with TMN. As supplement function of U31, U31 supports standard
CORBA interface to be available to the upper layer.
4.4 ZXO-08-06-005 Itf-N Open Database View PM

Feature Change: N/A
Commercial Attention: ZXO-08-06-005 Itf-N Open Database View PM provide Open

Database PM interface, but not including the cost of engineering implement, after-sale
service, any other third party hardware or software of NMS.

4.4.1 Summary
U31 could connect to NMS system through northbound database interface. It enables
NMS to get performance view data customized by U31 to open user name, password
and server port of database to NMS.
4.4.2 Benefits
The interface is quite simple and its developing period is fast. It saves R&D manpower
and shortens deployment period.
4.4.3 Description
Database Itf-N provides connecting path to NMS. NMS can get, display and analyze the
performance data. U31 provides the table view of each counter, user name and
password of the interface, but not open the database directly.
NMS only has the read priority on these views. NMS may ensure the performance view
of U31 through SQL statement.
4.5 ZXO-08-06-006 Itf-N Open Database View

FM(GERAN & UTRAN)
Feature Change: N/A
Commercial Attention: ZXO-08-06-006 Itf-N Open Database View FM provide Open

Database FM interface, but not including the cost of engineering implement, after-sale
service, any other third party hardware or software of NMS.
4.5.1 Summary
U31 could connect to NMS system through northbound database interface. It enables
NMS to get alarm view data customized by U31 and open a user name, password and
server port of database to NMS.
4.5.2 Benefits
The interface is quite simple and its developing period is fast. It saves R&D manpower

and shortens deployment period.
4.5.3 Description
Open Database Itf-N provides connecting path to NMS, NMS can get and show the
alarm data. NMS gets data in active mode. U31 provides the user name and password
of the interface, but not open the database directly.
NMS only has the read priority on these views. NMS may ensure the alarm view of U31
through SQL statement.
4.6 ZXO-08-06-007 Itf-N FTP CM

Feature Change: N/A
Commercial Attention: ZXO-08-06-007 Itf-N FTP CM provide FTP CM interface, but not
including the cost of engineering implement, after-sale service, any other third party
hardware or software of NMS.
4.6.1 Summary
According to configuration database, the selected data is transformed to the defined file
and reported to NMS periodically through FTP. It is also possible to give a specific path
where NMS can pick the information periodically. U31 supports file interface user name
and password.
4.6.2 Benefits
Itf-N FTP ensures high security, high reliability and easy-to-implement.
4.6.3 Description
U31 could connect with NMS system via northbound file interface. U31 exports the data
required by NMS from file to specified location regularly; NMS gets data files via FTP.
To ensure the consistency of interfaces, U31 makes regulations for following items:
1. File naming rule

2. File type
3. File generating period
4. File access time
5. File access directory
6. File getting way
7. File compression format
8. File keeping time
U31 reorganizes configuration data into defined files by NEs. File format can be CSV
and XML. NMS can get configuration file access to FTP.
4.7 ZXO-08-06-008 Itf-N FTP PM

Feature Change: N/A
Commercial Attention: ZXO-08-06-008 Itf-N FTP PM provide FTP PM Interface, but not
4.7.1 Summary
According to performance database, the selected data is transformed to the defined file
and reported to NMS periodically through FTP. It is also possible to define a specific
path where NMS can pick the information periodically. U31 supports file interface user
name and password.
4.7.2 Benefits
Itf-N FTP ensures high security,high reliability and easy-to-implement fucntions.
4.7.3 Description
U31 could connect with NMS system via northbound file interface. U31 exports the data
required by NMS from file to specified location regularly; NMS gets data files via FTP.

Convention between Itf-N and NMS:
1. File naming rule
2. File type
4. File data granularity
5. File access time
7. File getting way
8. File compression format
9. File keeping time
U31 reorganizes performance data into defined files by NEs. File format can be CSV
and XML. NMS can get performance file access to FTP.
4.8 ZXO-08-06-009 Itf-N SNMP FM

Feature Change: N/A
Commercial Attention: ZXO-08-06-009 Itf-N SNMP FM provide SNMP FM Interface, but

not including the cost of engineering implement, after-sale service, any other third party
4.8.1 Summary
U31 supports SNMP V1, V2c and V3 protocol. As an EMS working in Element
Management layer, U31 supports fault management access to NMS system through
northbound SNMP interface.
4.8.2 Benefits
NMS. In this case, SNMP Itf-N realizes inter-connection between NMS interface and

4.8.3 Description
U31 supports SNMP protocols as following:
SNMP protocol standard operations
SNMP Get Request
SNMP Get Next Request
SNMP Set Request
SNMP Trap
Community-based SNMP security model
U31 can support inter-connection with NMS through northbound SNMP interface. U31
northbound SNMP interface offers NMS with fault management function, including items
below:
Real-time Alarm Report
U31 initiatively sends alarm events generated on NE to NMS by this function.
Get Alarm IRP Version
NMS can get Alarm IRP version information via this interface.
Get Alarm Heartbeat IRP Version
NMS can get Alarm Heartbeat IRP version information via this interface.
Inquire and Set Heartbeat Period
NMS can inquire and set heartbeat period via this interface.
Inquiry on Current Alarm
4.9 ZXO-08-06-010 Itf-N FTP IM

Feature Change: N/A

Commercial Attention: ZXO-08-06-010 Itf-N FTP IM provide FTP IM Interface, but not
4.9.1 Summary
U31 can inter-connect with NMS system via northbound file interface to provide
inventory information.
4.9.2 Benefits
With Itf-N FTP IM , supplier can collect NE inventory information of whole network.
4.9.3 Description
U31 can inter-connect with NMS system via northbound file interface. U31 exports the
data required by NMS from file to specified location regularly. NMS gets data files via
FTP or U31 puts data files to specified location via FTP regularly.
U31inventory information includes asset ID, asset type, vendor name, asset identifier
(serial number), asset category, equipment version, asset position, and update time etc.
To ensure the consistency of interfaces, U31 makes regulations for following items:
1. File naming rule
2. File type
4. File access time
6. File getting way
U31 reorganizes Inventory data into defined files by NEs. File format can be CSV and
XML.
4.10 ZXO-08-06-011 Itf-N Import Radio &

Transmission CM Data

Feature Change: N/A
Commercial Attention: ZXO-08-06-011 provide to import configuration data files

Interface, but not including the cost of engineering implementation, after-sale service,
any other third party hardware or software of NMS.
4.10.1 Summary
The NMS imports the modified radio parameters and transmission parameters into U31
through the NBI for importing files. After that, U31 synchronizes the configuration data to
NEs for the modification to take effect.
4.10.2 Benefits
The NBIs for importing and exporting files help normalize the devices of different NMS
providers. This enables users to quickly and correctly configure and manage the NEs
based on the planned data. The exporting & importing files for NBI have same format..
4.10.3 Description
Through the NBI for importing files whose format is XML, users can add, delete, and
modify GERAN and UTRAN radio parameters and transmission parameters. U31
checks the validity of the configuration data. If these parameters pass the check, U31
delivers the parameters to NEs. Otherwise, U31 generates an error report.
5 Enhanced Report Management

The ERM (Enhanced Report Management) module is a flexible, rich format report
generation subsystem. It used to fulfill the quick changed / complicate format report
requirements.
ERM can extract data from many EMSs running fitful version, and export joint reports.
The ERM module based on BO report engine, it means this module needs additional
software license, maybe need expand DBMS license.
The ERM need much calculation and storage consumption, it is recommend to run it on
dedicate hardware platform.

5.1 ZXO-08-07-001 Web Based Report (GERAN &

UTRAN & FDL)
Feature Change: N/A
HW&SW Dependencies: this function is based on U31 Performance Management basic

function.
Commercial Attention: ZXO-08-02-001 Web Based Report includes Web Based Report
function, but excludes the hardware; Hardware needs to be configured additionally.
5.1.1 Summary
Provide web based graphical report, support report rendering, coloring, and exporting.
5.1.2 Benefits
Provide graphical display of report, which is convenient to view and export.
5.1.3 Description
Support B/S architecture report:
Support major browsers such as IE and other browsers, support W3C standard. Provide
web based view and export function.
Support mobile WEB view, reports can be put in mobile catalog on server part and
display on iPAD via SAP BO app.
All functions provide GUI.
Provide various format of graphical report and the format is easy to customize.
Provide table, graphical and hybrid report.
Provide 3D data display.
Provide common graphics, such as bar charts, line charts, pie charts, scatter diagrams
and line graphical columnar mixed report
Report rendering and coloring:
Support highlighting display of concerned data, support color mark, highlighting, change

font, size, etc.
Support settling thresholds for index. Numeric index supports 4 levels and every level
supports separate rendering method.
Tables and graphics support rendering and coloring.
Report export:
Support exporting report in common format such as PDF, XLS, and CSV. The
corresponding reader software is needed such as Microsoft office.
Support exporting report in WEBI format, and it can be viewed in ERM without any other
reader software.
5.1.4 Update record

2013R1:
Add mobile web view via iPAD.
5.2 ZXO-08-07-002 Data Extraction Filter (GERAN &

UTRAN & FDL)
Feature Change: N/A

function.
Commercial Attention: ZXO-08-02-002 Data Extraction Filter includes Data Extraction

Filter function, but excludes the hardware; Hardware needs to be configured additionally.
5.2.1 Summary
Provide filtering function so that operators can define the scope of data to be acquired.
User can define the performance measurement type to be acquired by editing the
configuration file.
5.2.2 Benefits
Only needed data will be extracted and preprocessed then stored into the ERM

database. This can remove the redundancy information, save database access time,
and accelerate the report generating time.
5.2.3 Description
This feature enables users to flexibly filter the reports, namely users are allowed to
extract data in terms of related performance measurement types, so as to ensure the
validity of the data, avoiding extracting too much useless data to heavy the system load.
5.3 ZXO-08-07-003 Radio Business Report (GERAN &

UTRAN & FDL)
Feature Change: N/A
HW&SW Dependencies: this function is based on ZTE Performance Management basic

function. It is also based on ZXO-08-02-001 Web Based Report.
Commercial Attention: ZXO-08-02-003 Radio Business Report includes Radio Business

Report function, but excludes the hardware; Hardware needs to be configured
additionally.
5.3.1 Summary
Support general OLAP analysis, busy time report and multi U31 integrated reports.
5.3.2 Benefits
It is convenient to view summary data of every level, to define busy time report and to
define multi U31 integrated reports.
5.3.3 Description
This feature includes below functions:
General OLAP analysis:
Support drilling up and down in time dimension such as month, week, day and hour.
Support drilling up and down in object dimension such as BSC/RNC, base station, cell,
object group.

Support KPI hierarchical and associative relations display, it means display the indexes
composed the object KPI by the hierarchical and associative relation and it can be
drilling down to get much details level by level until to raw counters.
Busy time report:
System busy time report provided by report system calculates busy time and exports
report according to pre-defined busy time rules. The Busy time can be defined by user.
Another busy time definition is set the busy time index and the busy time is the most
high or low time of a day. Support calculating busy time according to single index or
multi indices.
5.4 ZXO-08-07-004 Report Customizable (GERAN &

UTRAN & FDL)
Feature Change: N/A

function. It is also based on ZXO-08-02-002 Data Extraction Filter.
Commercial Attention: ZXO-08-02-004 Report Customization includes Report

Customization function, but excludes the hardware; Hardware needs to be configured
additionally.
5.4.1 Summary
Provide GUI for report designing. All report elements support customization, such as
multi-headers, report data sources, report display format, report graphics, rendering,
headers, and footers. Support pre-defined report. Support timing send report in PDF or
XLS format to users through FTP and EMAIL.
5.4.2 Benefits
It is convenient to design report by clicking and dragging. Support report template and
templates can be shared with other users.
Operators can receive concerned reports automatically by customizing report output

rules in timing task. It is convenient to view reports offline, or receive and view report
while travelling it in other places.

5.4.3 Description
ERM function is base on BO report architect. It supports customize report model with
general conceptions. It means the report model can support most of end-user
requirements, but it also difficult to use for too much detail. This feature describes all
detail customizable points U31 can support.
To simplify customize, ZTE provides predefined semi-models which called analysis

scene, user just choice the index they need and the object / time scope, and then get
the report or graphic diagram they want. It is convenience to temporary query something
and define report model without special requirement.
Support report format customization, including:
Set multi-headers, merging fields in header column, set header colors.
Set titles, headers, footers.
Support dynamic column display.
Set graphics in report, rendering and coloring.
Set index in report, rendering and coloring on data and text.
Support TOPN report:
Support TOPN report to display data and related KPI, using concerned index or
combined index as keywords.
Support setting KPI as keywords of TOPN.
Support setting customized index as keyword of TOPN
Support customization of N in TOPN
TOPN report supports other indices of the cell display simultaneously for comparing.
Analytical parameters support time dimension and NE dimension.
Support object grouping:
User-defined object group; operators can define associated objects such as cells or
RNC as a group and obtain statistical data according to this group.
Support group automatic defining according to configuration attributes, and object

information in the group can update automatically.
Support statics by object group. Typical object group includes cell, base station, and
base station controller.

Object group is a logical entity and supports the following operations:
Support real-time query and timing report by group.
Support busy time automatic detect and busy time report by group.
Object group can be a object level in OLAP
Support index management:
System indices are provided in default, and they are read only.
User-defined index supports create, modify, delete, display in GUI. Equation Editor
supports arithmetic and logic operations, and provides many functions.
User-defined index can be saved as templates and exported.
Support import index template.
Support report template management:
User-defined report can be saved as templates in the system. Operators can classify
templates according to their business requirement and save them separately.
Support task management:
Set report templates, timing task triggering condition, report period, report format (XLS,
PDF, WEBI), destination address, transmission (FTP, EMAIL).
Period setting support hour, day, week, month.
Timing task supports suspend, delete, and modify.
Records are kept for actual trigger time and results of timing tasks.
Set retry time and retry interval while task fails.
5.5 ZXO-08-07-005 Dashboard Support(GERAN &

UTRAN)
Feature Change: N/A
HW&SW Dependencies: need a dedicated server; it is also based on ZXO-08-02-002

Data Extraction Filter.

5.5.1 Summary
Support dashboard to help user get whole network information in just one interface.
5.5.2 Benefits
It is convenient to view data in one interface and response to users actions.
5.5.3 Description
Via introducing new component of SAP Business Objects, Report system provides
dashboard function. Large amount of data can be presented in only one interface.
Dashboard can response user clicking in the report and present required data
dynamically.
Switch based on objects:
Entry interface is based on some business main indicators. User can switch among
different controllers and generate trend report based on time interval of the controller.
Scroll is provided for user to choose the interval for detailed analysis.
Switch based on time:
Entry interface is based on some business main indicators. User can switch among
different granularity such as hourly, daily and weekly. Via choosing the current data and
previews data, user can generate comparison report.
Indicator filter
User chooses and filters the indicator in the report and the report will generate based on
the filter setting. Via this function, user can analyze the report more conveniently and
easily.
6 RAN Sharing Support

RAN sharing function supports to share a physical network to multi operator. These
functions makes operator has a fair, easy to access, right isolated way to use U31 or
get Itf-N from U31.

6.1 ZXO-08-08-001 Security Enhancement for RAN

Sharing
Feature Change: N/A
HW&SW Dependencies: After using RAN Sharing, the system load of U31 may increase
25%. Need to consider expansion of U31 server.
Commercial Attention:
6.1.1 Summary
In RAN Sharing, there shall be a main operator who is responsible for building and
maintaining the network, and other operators who rent some of the network resources,
such as carriers, cells. The renting operators may need to monitor the part of network
they rent, but only the main operator has the right to control the whole network.
U31 offers operator information management, where one can add, modify and delete the
renting operators information. After using this information in user management, U31 can
control the access of resources by operators.
6.1.2 Benefits
In RAN Sharing, U31 offers a unified control and management of multiple operators who
share the network, and gives operators different operation and resource access right.
6.1.3 Description
U31 offers operator information management, where one can add, modify and delete the
renting operators information. The information includes MCC, MNC, operator name and
whether be able to view public data.
User management can using operator information to build the relationship between
users and operators. Users without operator information are considered as main
operator users. One user can only belong to one operator.
U31 also offers a pre-defined renting operator role, which have a read-only right. It can
be used for the renting users.
U31 considers the operator information when authentication. After common

authentication, U31 will verify the operator information of user and the resource. This
means that the main operator users can be authorized to all the resources and the

renting operator users only to their renting resources. For example, if a users operator
is set to "460-01" and resource is "460-00", it indicates that the user is unauthorized to
the resource.
6.2 ZXO-08-08-002 CM/FM/PM Enhancement for RAN

Sharing
Feature Change: N/A
HW&SW Dependencies: After using RAN Sharing, the system load of U31 may increase
25%. Need to consider expansion of U31 server.
Commercial Attention: .
6.2.1 Summary
In RAN Sharing, U31 offers CM/FM/PM enhancement to make both main operator and
renting operators can using U31.
6.2.2 Benefits
In RAN Sharing, U31 offers a unified CM/FM/PM for multiple operators who share the
network, and gives operators a new maintenance experience.
6.2.3 Description
Configuration Management
Main operator users can view and configure all the managed objects according to their
rights. This means they can be authorized to maintain the shared resources.
Renting operator users can view their renting resources. They can not view the detail of
the shared resources, but can view which objects are shared with them.
Renting resources for GSM: BSSFunction, IBSCMPLMN, ExternalUtranCell,

ExternalGsmCell, GsmCell, IBTS3GHO, IBTS3GHORS, IBTS3GRS, IBTSHO,
IBTSRESEL, IBTSHORES.
Renting resources for UMTS: Rncfunction, Utrancell, Externalutrancell, Externalgsmcell.
Renting resources for LTE: ENBFunction, GlobleSwitchInformation, EutranCell,

ExternalEUtranCell.
Fault Management
Main operator users can manage the alarms according to their rights.
Renting operator users can view the alarms of their renting resources, which can be
distinguished by the operator information. They also can be authorized to view the
alarms of shared resources. But any write operation of alarms, such as alarm clearing,
create alarm rules, etc., cannot be authorized to the renting users.
The alarms with operator information: Cell alarms.
Performance Management
Main operator users can be authorized to all the performance management such as
measurement task management.
Renting operator users can view the measurement data and KPI data of their renting
resources. They also can be authorized to view the performance data of shared
resources. But any write operation of performance, such as create measurement task,
cannot be authorized to the renting users. The performance report templates which are
defined by main operator can be assigned to renting users. They can use these
templates to query and collect the performance data.
6.3 ZXO-08-08-003 Itf-N for RAN Sharing

Feature Change: N/A
HW&SW Dependencies: if cell enables RAN Sharing, the EMS resource consumed by
the cell will increase 25%.
6.3.1 Summary
U31 can provide different northbound interfaces for multiple operators access.
Northbound interfaces including CM, FM and PM are separate for different operators.
6.3.2 Benefits
In RAN Sharing mode, operators can access operator-dedicated data on northbound

interface.
6.3.3 Description
U31 can provide user management on northbound interface. Users of different operators
are assigned different user name and password, and U31 provide dedicated access
control when users access U31 system.
In Ran Sharing mode, U31 provide separate access for CM, FM and PM on northbound
interface. Four operators are the limitation for access.
Northbound interfaces for CM, FM and PM are differential for operators. For instance, if
operator A is secondary, the cell alarms managed by operator A can only be reported to
NMS of operator A, same as it, performance data and configuration data can only be
acquired by operator A users.
CORBA is used on northbound interface for FM. Main operator users can get all alarms
managed by both main operator and secondary operator, while secondary operator can
only query its own alarms. The operations like alarm acknowledge can be processed by
main operator.
FILE interface in CSV format is used on northbound interface for CM and PM. Main
operator users can get all configuration data and performance data managed by both
main operator and secondary operator, while secondary operator can only query its own
configuration parameters and performance data.
7 SON Infrastructure
The SON infrastructure use to support the general SON management requirements, the
content of these feature will be expand with new SON functions implemented.
The policy configuration use to management SON parameters to apply to network.
The SON monitor & control use to control the modification of network parameter which
SON functions decided or suggested. Planning data integration use to fulfill NE
configuration with planning system output, with Automatic Multi-Mode BS Software
Installation & Upgrade and Automatic Configuration Data Download and Activation
supports multi-mode base station plug and play procedure.
7.1 ZXO-08-09-001 SON Policy Configuration


Feature Change: N/A
7.1.1 Summary
This feature is used to set parameters of SON functions, and make it apply to network
as SON policies.
7.1.2 Benefits
Make it easy to configurate SON fuctions in an integrated UI. It is flexibe to add new
SON functions.
7.1.3 Description
The feature provides customizable policy definition, which involves self configuration,
self optimization and self healing.
The policies about self configuration include:
Function switches of self configuration
How to generate configuration data from planning data
How to prepare software versions to be downloaded
Chance to trigger software and configuration data downloading and activating to the
NEs associated with
Items to be tested on NEs when new software and configuration data activated
Breakpoints of the process and how to handle the fails.
The policies about self optimization include:
Function switches of self-optimization
Ranges and step intervals of parameters tuning,
How to coordinate different self-optimization principle related with same parameters and
KPI.
The threshold to trigger the self-optimization process and the target of effect.

7.2 ZXO-08-09-002 SON Monitoring & Control

Feature Change: N/A
7.2.1 Summary
This feature is used to monitor the condition of the SON function related resources, for
example the cells current PCI.
It also use to control apply or cancel the network modification exported by SON
decision-maker module.
7.2.2 Benefits
The feature enables to build trust and confidence on SON function and avoid
unexpected EUTRAN quality degradation.
7.2.3 Description
The feature of SON monitoring and control includes the following aspects:
Information reference point reporting
eNode B reports process messages of self-configuration & self-optimization & re-

configuration to U31. U31 is capable of showing and recording..
Log management
The log of the dedicated SON function can be recorded, retrieved and audited,
which can be ultilized to track and analyse the detail information of the procedure..
Enable/Disable switches of SON functions
For each SON function, it can be switched between enable and disable via the U31
by operator.
Management & control
U31 supports setting the execution modes, which includes controlled mode (open
loop) and autonomous mode (closed loop), and manual intervention in control.

7.3 ZXO-08-09-003 Planning Data Integration

Feature Change: N/A
7.3.1 Summary
U31 supports to integration plan data of the network and make it complete to each NE
and assort between NEs.
7.3.2 Benefits
Reduce data prepare effort.
7.3.3 Description
U31 supports planning data file integration so that the NE can be configured
automatically. U31 has capability of self-configuration of radio and site parameter
according to the imported planning data and generates data file which can bring the
eNode B into full commercial operation.
7.4 ZXO-08-09-004 Automatic Multi-mode Base Station

Software Installation & Upgrade
Feature Change: N/A
7.4.1 Summary
U31 supports to intallation new software to connecting eNode Bs, and Upgrade eNode B

software on run time. It is a part of eNode B plug & play procedure supports multi RAT at
same time.
7.4.2 Benefits
The feature enables to reduce manual intervention during software installation or
upgrade.
7.4.3 Description
The feature includes three processes below:
eNode B unique ID check
It can be realized in U31 to judge whether the eNode B is managed by the U31;
U31 judges whether the eNode B versions need upgrade or not;
Software download and activation.
The scenarios to trigger the fuction are as following:
After the eNode B self discovery
Scheduled check as policies to update
7.5 ZXO-08-09-005 Automatic Configuration Data

Download and Activation
Feature Change: N/A
7.5.1 Summary
U31 supports to generate eNode B configuration file, download and active it when
eNode B connect in or U31 user launched. It is a part of eNode B plug & play procedure
supports multi RAT at same time.

7.5.2 Benefits
Reduce manual effort during configuration upgrading and software version activation.
7.5.3 Description
U31 provides configuration file downloading and activation management function.
Operator can use the function to define which configuration file is to be used for each
eNode B independently.
The feature involves the following aspects:
Data file downloading and upgrading along with software downloading and
upgrading when eNode B initially connect to U31;
When software is upgraded, the corresponding version data file downloading and
upgrading;
Upgrading data file only.
In the case it is necessary to update data file in accordance with the need for O&M, U31
downloads data file automatically according to downloading strategy(including eNode B
blacklist and white-list of upgrading, downloading period, post-strategy after
downloading failure, network element parameters, etc ), and eNode B statuses. But,
data activation strategies, such as immediate activation, time delay activation, action for
failure processing are also available for configuration data activation management.
7.6 ZXO-08-09-006 SON Effect Evaluation

Feature Change: N/A
7.6.1 Summary
U31 Supports effect evaluation to SON functions, it means operator can check the
performance statistic to ensure the SON policies is work good or not, and decided how
to adjust it or not.

7.6.2 Benefits
Quick reference the policy effect by assignment certain network resource and certain
SON function. The report is performance chart with the mark of parameter changing
time.
7.6.3 Description
U31 provides quick report about certain SON function. Check the KPI alteration between
the time before and after policy/ parameter changed to ensure the effect and decide to
keep or recover the changes.
Operator can assign time period, RAT type, involved NE/network resource and SON
function. U31 will output the report about related KPIs within time period and the time
points which parameter changed by SON policy is marked in the chart report. Operator
can choose KPI display or not to make it more focus.
This quick reference embeds in SON management GUI, operator didnt need to switch
to PM module to get the same report. And the KPI associate to SON function is
predefined make it easy to find and use. The multi change time marks make it easy to
distinguish performance KPI regions relate to parameter changes.
The function types supported by the function are as following:
PCI
Mobile Robust Optimization(MRO)
Mobile Load Balance(MLB)
7.7 ZXO-08-09-006 Radio Parameter Reconfiguration

(FDL)
Feature Change: N/A
7.7.1 Summary
U31 supports to generate the planning data about radio parameter for the existing cells

and make the new data apply to eNodeBs automatically. And the feature can be used for
the radio parameter configuration flexibly.
7.7.2 Benefits
Easy planning releated dedicated radio parameters and reduce the manual operation of
the process.
7.7.3 Description
U31 provides the GUI for the automatic reconfiguration of a dedicated kind of radio
parameter for one or more exiting cells contained in the same U31 system. And for the
process, operators can select the cells which need reconfiguration of the dedicated
parameter type, and after the parameter generation with new value operators can
decide to make effect the configuration to the responding eNodeBs automatically.
The parameter types supported by the function are as following:
PCI
ICIC
PRACH
After the reconfiguration request, the reconfiguration result will be shown in the EMS
GUI. After confirmed by operators, the data change will apply to eNodeB automatically. If
success, the data will be shown in the EMS configuration tools.
8 SON Functions
SON functions listed in this document has been implemented in U31 totally or partly.
Some SON functions maybe managed by U31 but decision and executing not in U31 will
be list in equipment feature list or planning/optimization system feature list.
8.1 ZXO-08-10-001 Automatic PCI Configuration Based

on Centralized Assignment (FDL & TDL)
Feature Change: N/A

8.1.1 Summary
U31 supports to generate PCI centralizly for each eUTRAN cell, and assign it with other
configuration data to eNode B.
8.1.2 Benefits
Assign initial PCI for cell without conflict & confusion; reducing manual effort on PCI
assignment.
8.1.3 Description
The feature includes centralized PCI assignment, PCI conflict and confusion detection
and resolving based on centralized assignment, PCI assignment management.
Centralized PCI assignment
U31 assigns cell's PCI according to radio planning data such as frequency of cell,
longitude and latitude of cell site, azimuth of cell, radius of cell, available range of
cell PCI and the maximum distance of PCI reused.
Result displaying of PCI conflict and confusion and resolving based on centralized
assignment
U31 can show the result of PCI conflict and confusion detected by eNode B. U31
support conflict and confusion resolving according to the detection result and the
function of centralized PCI assignment, and support the process management and
decision-making.
PCI assignment management
U31 provides PCI assignment management and control capability to support PCI
assignment enable/disable, monitor and transmit between open/closed loop mode,
and support north-interface PCI assignment management.
PCI assignment enable/disable:
U31 provide GUI view for operator to enable/disable PCI assignment function
per eNode B or group of eNode Bs;
Monitor and transmit between open/closed loop modes:
Both centralized and distributed assignment support every step and result to

PCI assignment GUI view. Operator can monitor the procedure of PCI
assignment. Operator can set PCI assignment mode and breakpoint to control
execution of the feature, and before the execution of PCI validation user can
modify the attribution generated by system.
North-interface PCI assignment management
Support PCI assignment capabilities as defined in 3GPP TS 32.76x series (E-

UTRAN NRM IRP) and 3GPP TS 32.61x series (Configuration Management
Bulk CM IRP) and Release 8 in a NM-centralized architecture (as defined in
TS 32.500). PCI configuration files can be imported from / exported to / their
EMS.
The PCI data can be export from EMS. The data model is compliant with to
3GPP TS 32.762 and 32.765(E-UTRAN NRM IRP Information Service)
Release 8.
8.2 ZXO-08-10-002 Automatic PCI Configuration Based

on Distributed Assignment (FDL & TDL)
Feature Change: N/A
8.2.1 Summary
U31 supports to generate available PCI list for each eUTRAN cell, and assign it with
other configuration data to eNode B.
eNode B choose PCI from PCI list for each cell and modify it, by the algorithmic of
distribute assignment.
8.2.2 Benefits
The feature provides the available PCI list generation for distributed assignment easily.
8.2.3 Description
The available PCI list is an important entry for the implementation of distributed PCI

assignment. The generation of the list depends on the following conditions:
Frequency of the cell
Longitude and latitude of site location;
Azimuth of the cell
Available range of cell PCI;
The maximum distance of the PCI reuse
8.3 ZXO-08-10-003 Sleeping Cells Self-healing (FDL)

Feature Change: N/A
8.3.1 Summary
U31 provdes the sleeping cells detection, recovery and compenzation.
8.3.2 Benefits
Reduce the difficuty to detect sleeping cells and quick the dealing, so the users in the
cell can be affected for less time.
8.3.3 Description
A sleeping cell is in a normal status without any faults, but cannot provide coverage and
traffic service. As usual, sleeping cells can only be detected by users complaint or
manual inspection.
U31 can automatically monitor the related KPIs and the cell status fo detect the sleeping
cells, recovery and compensate the sleeping cells, as defined policies by operators.
Sleeping cell detection
To detect the sleeping cell, the running cells associated KPIs will be monitored, like
maximum active users, RRC connection establishment request, and handover in
request times and so on. To avoid the mistaken detection the historic data in the same

period will be referred to judge whether the cell is a real sleeping cell and not a common
one. And the judgment conditions value can be configured in the policy management.
After the sleeping cell is detected, U31 will show the result in the monitoring
management and a notification in the fault management.
Sleeping cell recovery
After the detection of the sleeping cell, a sequence will be done to recovery it. The
actions include resetting all the logic and physical units in sequence, which are the logic
cell, the responding RRU, the responding BPL, the eNodeB. Between each action, there
is an evaluation for the operation, and if the cell is still in the sleeping status, the next
action will be done till all actions are done.
Sleeping cell compensation
If the sleeping cell cannot be recovered after the recovery actions, the related
compensation will be done to isolate the effect to the surrounding cells. The
compensation includes shutting down the sleeping cell, modify the HO parameters of the
neighbor cells to ensure no HO to the sleeping cell.
The isolated cells should be inferred manually, and U31 provides falloff to the old value
before compensation by one touch.
8.4 ZXO-08-10-004 Performance Cells Self-healing

(FDL)
Feature Change: N/A
8.4.1 Summary
U31 provdes the poor-performance cells detection, recovery and compenzation.
8.4.2 Benefits
Reduce the difficuty to detect poor-performance cells and quick the dealing, so the users
in the cell can be affected for less time, and the affect to the surrounding cells can be
reduced.

8.4.3 Description
Compared to sleeping cells, the poor-performance cells can work but not efficiently,
which KPI is low and the UEs residing in it are affected in a certain extent. As sleeping
cells, poor-performance cells can only be detected by users complaint or manual
analysis of the performance data and QoS alarms. .
U31 can automatic monitor the related KPIs fo detect the poor-performance cells,
recovery and compensate the poor-performance cells, as defined policies by operators.
poor-performance cell detection
To detect the poor-performance cell, the KPIs will be monitored, like RRC connection
establishment success rate, eRAB connection establishment success rate and so on.
The judgment conditions value and type can be configured in the policy management.
After the poor-performance cell is detected, U31 will show the result in the monitoring
management and a notification in the fault management.
poor-performance cell recovery
After the detection of the poor-performance cell, the cell reestablishment will be done in
the controlled mode to try to recover the poor-performance cell. Before the recovery
action, the UEs residing in the cell will be handed over to keep the user experience.After
that, a recovery evaluation will be done to judge whether the poor-performance cell is
still in the poor-performance status. If still, the compensation action will be taken.
poor-performance cell compensation
For poor-performance cells, compensation will be done to eliminate poor performance

phenomenon. The compensation will adjust the parameter of HO and
selection/Reselection, which will affect the CIO in U-interface.
The compensated cells will persist till manual interference happens, and U31 provides
falloff to the old value before compensation by one touch.
9 Integrated Configuration Management

The ICM is a stand alone application provides whole network configuration management
upon multi EMS situation. It also useful to management large scale network by
supporting parallel modification with multiple planning area functions.
9.1 ZXO-08-11-001 Global Configuration Management


Feature Change: N/A
HW&SW Dependencies: Needs dedicate server and suitable 3rd part platform software.
9.1.1 Summary
The ICM is an optional module of U31, which can deploy on dedicate server to perform
global configuration management to NEs managed by multi EMS.
9.1.2 Benefits
User can manage whole networks configuration regardless the NE managed by which
EMS.
Some useful functions and facilities support user management configurations of huge
number of NE.
9.1.3 Description
The ICM is an optional module of U31. It deploys on dedicate server and connects to
multi U31 systems to provide global CM function. It is useful if user has many EMS or
wants to have strict modification control rules.
ICM supports most of CM functions descript in U31 basic feature. In additional, it

provides more function to handle mass data.
Global data consistency use to check data of whole network before it apply to EMS
and NE
Global configuration report use to gather and make configuration reports for whole
network without and additional interface and post process.
Multiple planning area use to support many user planning data simultaneity, and
check the confliction between it. It can be use to support complicate data modify
control rules
Configuration project wizard use to guide the process of data planning.
9.2 ZXO-08-11-002 Global Data Consistency Check


Feature Change: N/A
Commercial Attention: It builds upon the feature ZXO-08-14-001Global Configuration

Management.
9.2.1 Summary
ICM supports check configuration data distributing on many EMS. It supports external
cell parameter check, single direction neighbor relationship, Iub link parameter check.
ICM Outputs the check report and supports confliction batch modify.
9.2.2 Benefits
It uses to ensure there are not conflict between the data from each EMS and NE, make
it efficient than manually check and correct.
9.2.3 Description
Iub link parameter check:
For 2/3G network, the incorrect Iub link parameter set on BSC/RNC and BTS/NodeB will
causes link establish fail and the NodeB cant work. This function use to:
1. It can find out BTS/NodeB missing, it means IuB link has been set on BSC/RNC
but no related BTS/NodeB or BTS/NodeB existed but no Iub link configed on
BSC/RNC.
2. Can find out different Iub link parameters between related BSC/RNC and
BTS/NodeB.
It output check resualt grouped by NE.
External cell parameter check:
In the scope of selected sub-network, get all external cell info for all RATs in every NE.
According the keyword of the external cell info find out if it map to a real cell in the scope
of ICM, and find out is it should be but missed real cell. If the source cell existed, check
the external cells parameter coincident to source cells parameter.
Check result is outputted as Excel file, it contains two parts: first, reports of detail conflict
info, second, the suggestion of how to modify conflict external parameter reference the
source cell. The suggestion sheet can import in planning area and apply to network.
Single direction neighbor relationship check:

In the scope of selected sub-network, find all single direction neighbor relationship and
output report. The Single direction neighbor relationship means cell A has an adjacent
relation to cell B but cell B do not has an adjacent relation to cell A.
The outputted report can be modified as a neighbor relationship update file, and can be
used to input to certain planning area and apply to network.
9.3 ZXO-08-11-003 Global Configuration Report

Feature Change: N/A

Management.
9.3.1 Summary
ICM can get configuration data from multiple EMS, and provide a variety of configuration
reports. The user can choose the objects and attributes, to make customized report
templates.
9.3.2 Benefits
The user can easily browse the original data or summary of the whole network.
9.3.3 Description
ICM supports to statistics by user specified condition and use the summary result and
original data to create report follow the given templete.
The output file format support for CSV and Excel. User can export report via GUI or
MML command, it also supports custom schedule / periodic output to certain dircetion.
The report templetes is belong to certian user. Every user can customize a set of
templetes for himself.
9.4 ZXO-08-11-004 Multiple Planning Area Management


Feature Change: N/A

Management.
9.4.1 Summary
ICM supports multiple planning. Multiple users can parallelly edit data in planning area
created by theirself.
9.4.2 Benefits
Users can edit data at same time in different planning areas. It has minimize confliction
on the stage to apply modification to network if there has a good scope division to each
user.
9.4.3 Description
ICM supports multiple planning and backup area, the data areas independently to each
other.
ICM has planning areas, living area, and backup areas as descript below:
Multiple planning areas:
When user creates a planning area with selected sub-networks, ICM will copy current
data stored in living area. User can edit in this planning area, do any data check in it with
unselected sub-networks data in living area if needed, create incremental MML script for
each sub-network and apply to network. After apply to network, the living area will be
updated automatically.
Multiple planning areas make it possible to isolate modification jobs within one planning
area and apply these areas one by one. It avoids that uncompleted job been apply to
network by other user, and avoids access limitation in simultaneity access situation.
Living area:
There is only one living area in ICM, it is a mirror of running network configurations. It
will update when receive NE configuration modification events, in other condition, it will
update by automatic synchronization when EMS / NE connection established, or by
manually synchronization.
Backup areas:

ICM provide the functionality of copy living area to a backup area, to provide a rollback
basis. User can make multiple backup areas to ensure network can back to a workable
condition.
9.5 ZXO-08-11-005 Configuration Project Wizard

Feature Change: N/A

Management.
9.5.1 Summary
ICM provides a graphical wizard guides the user to complete the configuration operation
step to step.
9.5.2 Benefits
It is easy to use and reduce the time of operator training. It also reduces the risk of
unreasonable usage from unskillful user.
9.5.3 Description
There are 5 stages in project wizard, user can create or open planning area at START
stage, and manually modify or import / output batch modify file at EDIT stage, and
check validity, integrality, confliction of modified data at Check stage, and apply to
network at Activate stage. At last, system will delete planning area after user confirmed
changes.
The wizard provides control method at every stage, display data status of editing or
submitted. It also provides operation history record to review.
10Script IDE Toolset

The U31 script IDE toolset (Octopus) supports a develop environment to make a scripts
which supports normal program control, execute MML commands and analysis MML
result. The script can execute on the terminal or server by instance mode or schedule
mode.

Operator will feel convenience to deal bulk MML commands by generate it with variable
and loop execution. The programmable MML result treat also minimize the manually
control.
Operator can put schedule jobs on server part to execute daily maintain procedure, the
result will be recorded in log.
10.1 ZXO-08-12-001 Script IDE

Feature Change: N/A
10.1.1 Summary
Operators create, edit and debug scripts in the script IDE.
The script supports program control includes variable, condition execute and loop
execute.
The script supports to connect to U31 server, execute MML command and analysis the
result.
The script supports GUI commands to get input or display result in run time.
10.1.2 Benefits
It is convenient to operator to generate bulk MML command with program to avoid
mistake.
Variable, condition execution, loop execution and programmable MML result treatment
minimize the manually control in the script run time.
10.1.3 Description
Operators create, edit and debug scripts in the script IDE. A project is use to stand a
execute environment for a script, user must create a project before make script.
In a project, user can create or open a script file. User can edit it, step execute it and run
it from terminal part.

The script supports variable, condition execute and loop execute to provide general
program control. It supports function to make the script more readable and minimize
the repeat.
The script supports follow catalog predefined functions:
1. Internal functions: use to convert data types, input/output and mathematic

calculate.
2. MML operate functions: use to connect to U31 server, execute MML and deal with
the responds.
3. Network resource functions: use to sort management NEs from U31 server to
support the MML generate and assign the execute target.
4. File functions: use to open / read / write / close binary files and especially deal with
excel files.
5. FTP functions: use to transmit file to or from FTP server.
6. Time functions: use to get date/time and sleep certain period
7. GUI functions: use to define simple GUI form to get input or display output.
10.2 ZXO-08-12-002 Server Part Script Project

management
Feature Change: N/A
Commercial Attention: This feature depends on the feature ZXO-08-12-001 Script IDE.
10.2.1 Summary
The script project can be saved and executed in server part. The script execution can be
scheduled as jobs.
The scheduled script execute result will be record in log and can check by IDE in
terminal.

10.2.2 Benefits
It is convenient to share script between operators.
It provides flexible schedule ability to execute in right time or repeat in periods.
10.2.3 Description
User can put local projects to U31 server. The script on server part can be executed by
any other operator, the authority check depends the U31 MML authentic.
User can manage script on server via local script IDE, it includes follow operates:
1. Publish: user put local project to server.
2. Execute: user execute the project on server.
3. Download: user get project from server to local terminal.
4. Delete: the publisher can delete project on server.
User can set job to execute script on schedule, it can execute once at assigned time or
repeat by period.
The operation about job includes create, modify, delete, query, suspend, active and
query the log contents execute result.
11Acronyms and Abbreviations

3GPP 3rd Generation Partnership Project
Account Authentication Authorization Audit, stand for a function
4A
definition of security center for general IT system
A
Authentication Authorization Accounting, use to determine whether or
AAA not a network element (especially FEMTO AP) or user can access
network
ACS Auto-Configuration Server, uses for FEMTO AP management system
AG Access Gateway, FEMTO AP use to connect to network
AP Access Point, FEMTO equipment let UE access
B
Base Band Unit, part of Node B, content Node B management and
BBU
baseband process
BO Business Objects, a report framework from SAP

BS Base Station
BSC Base Station controller
BSS Base Station Subsystem
BSSMAP Base Station Subsystem Management Application Part
BTS Base Transceiver Station
C
Certificate Authority / Registration Authority, security solution use any
CA/RA
token should use CA/RA to issue and verify digital certificate
CAPEX Capital Expense
CBC Cell Broadcast Center
Code Division Multiple Access, it also stand a radio access technology
CDMA
defined by 3GPP2
CM Configuration Management
CN Core Network
CORBA Common Object Request Broker Architecture
CSV Comma Separated Value, a kind of text file format
CTS Call Trace System
D
DB Data Base
DBMS Data Base Management System
DIF Database Interface Function
DNS Domain Name System
DR Disaster Recovery
DST Daylight Saving Time
E
EDGE Enhanced Data rate for Global Evolution
EGPRS Enhanced General packet Radio Service
EML Element Management Layer
EMS Element Management Subsystem
eNode B evolved Node B, the base station of eUTRAN
ERM Enhanced Report Module
EUTRAN Evolved Universal Terrestrial Radio Access Network
F
FDL Frequency Division duplexing LTE
Femto A type of base station solution, which solve family usage
FM Fault Management

FTP File Transfer Protocol
G
GERAN GPRS EDGE Radio Access Network
GGSN Gateway GPRS Support Node
GIS Geographic Information System
GPS Globe Position System
GSM Global System for Mobile Communication
GUI Graphical User Interface
H
HA High Available
I
IAMS Integrated AP Management System, ZTE solution of ACS
ICM Integrated Configuration Module
IDL Interface Description Language
IIOP Internet Inter-ORB Protocol
IM Inventory Management
IMEI International Mobile Equipment Identity
IMS IP Multimedia Subsystem
IMSI International Mobile Subscriber Identity
IP Internet Protocol
IRP Integrated Reference Point
Itf-N Interface Northbound
ITMP IT Management Part
International Telecommunication Union - Telecommunication
ITU-T
Standardization Sector
Iu A interface between RNC and CN
Iub A interface between Node B and RNC
Iu-CS Circuit Service part of Iu interface
Iu-PS Package Service part of Iu interface
J
JCA/JCE J2EE Connector Architecture/Java Cryptography Extension
JNDI Java Naming and Directory Interface
K
KPI Key Performance Indicator

L
LA Link Adaptation
LDAP Lightweight Directory Access Protocol
LLC Logical Link Control
LMT Local Maintenance Terminal
LTE Long Term Evolution
M
MAC Medium Access Control
MML Man Machine Language
MO Managed Object
MOS Mean Opinion Score
MS Mobile Station
MSC Mobile Switching Center
MTP Media Transfer Protocol
N
NAF Network Adaptation Function
NBI Northbound Interface
NE Network Element
NetNumen Merchant name of ZTE EMS product
NMC Network Management Center
NMS Network Management System
Signaling system defined by CCITT (International Telephone and
No.7/N7
Telegraph Consultative Committee)
Node B WCDMA base station
NRM Network Resource Model
NTP Network Time Protocol
O
OLAP On-Line Analytical Processing
OPEX Operating Expense
ORB Object Request Broker
OTN Optical Transport Network
P
PCI Physical-layer Cell Identity
PCU Packet Control Unit

PI Performance Index
PKCS #11 Public-Key Cryptography Standards API definition
PKI Public Key Infrastructure
PLMN Public Land Mobile Network
PM Performance Management
Q
QoS Quality of Service
R
RAN Radio Access Network
RAT Radio Access Technology
RCT Radio part Call Trace
RLC Radio Link Control
RLP Radio Link Protocol
RNC Radio Network Controller
RNS Radio Network Subsystem
RRU Radio Remote Unit
S
SCCP Signal Connection Control Part, part of N7 signaling protocol stock
SDR Software Definition Radio, a solution of ZTE multi-mode base station
SeGW Secure GateWay
SFTP Secure File Transfer Protocol
SGSN Serving GPRS Support Node
SMS Short Message Service
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SON Self-Organizing Networks
SQL Structured Query Language
SSH Secure Shell
T
TBF Temporary Block Flow
TDL Time Division duplexing LTE
TDMA Time Division Multiple Access
TS Time Slot

UDP User Datagram Protocol

UE User Equipment
UMTS Universal Mobile Telecommunications System
UNC Universal Nodes Controller
Uni-RAN ZTE's multi-mode RAN solution
UTRAN Universal Terrestrial Radio Access Network
V
VLAN Virtual Local Network
VPN Virtual Private Network
W
WCDMA Wideband Code Division Multiple Access
X
XML Extensible Markup Language
Z
ZIP A kind of file compress format

ZTE NetNumen U31 (RAN) Optional Features Description - V1.10 - 20120705

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZTE NetNumen U31 (RAN) Optional Features Description - V1.10 - 20120705

Uploaded by

Copyright:

Available Formats

NetNumen U31 RAN

Optional Feature Description

2017 ZTE Corporation. All rights reserved.

ZXO-08-05-007 Services Observe Part

ZXO-08-09-006 SON Effect Evaluation

ZXO-08-09-006 Radio Parameter

ZXO-08-10-003 Sleeping Cells Self-healing

ZXO-08-12-001 Script IDE

ZXO-08-12-002 Server Part Script Project

ZXO-08-07-001 Web Based Report

ZTE Confidential & Proprietary 1

ZTE Confidential & Proprietary 3

ZTE Confidential & Proprietary 5

5 Enhanced Report Management.......................................................................45

6 RAN Sharing Support.......................................................................................53

ZTE Confidential & Proprietary 7

ZTE Confidential & Proprietary 9

9 Integrated Configuration Management...........................................................73

10 Script IDE Toolset.............................................................................................79

11 Acronyms and Abbreviations..........................................................................82

ZTE Confidential & Proprietary 11

ZTE NetNumen U31 (RAN) Basic Feature Description;

ZTE NetNumen U31 (RAN) Optional Feature Description;

How to read this document using Feature ID?

The following table gives the features class.

Related RAT and NE Type

The RATs managed by NetNumen U31(RAN) include GSM, UTRAN, TD-SCDMA,

NE type managed by U31 is:

Multi-mode base stations for GSM, UTRAN and eUTRAN:

Distribute base station: BS8700

Indoor base station: BS8800

ZTE Confidential & Proprietary 13

Outdoor base station: BS8900A, BS8900B

Micro base station: BS8912

Base station for GSM and UTRAN only:

Micro base station: BS8906, BS8908

Pico base station: BS8112

BS8906, BS8908, BS8112

Base station for TD-SCDMA and eUTRAN TDD only:

Indoor macro base station: BS8300

Base station for eUTRAN TDD only:

Compact indoor base station BS8102

Relay base station: BS8912R

ZXG 10 iBSC for GSM

ZXWR RNC for UTRAN

ZXTR RNC for TDS-CDMA

UR9000 for GSM & UTRAN

ZTE Confidential & Proprietary 15

1.1 ZXO-08-03-001 Firewall Supported

Feature Change: N/A

HW&SW Dependencies: N/A

1.2 ZXO-08-03-002 LDAP Interface to 4A Center

Feature Change: N/A

HW&SW Dependencies: N/A

Commercial Attention: Need a connection to existing 4A server

ZTE Confidential & Proprietary 17

1.3 ZXO-08-03-003 Two - Factor Authentication - USB

Feature Change: N/A

Commercial Attention: N/A

ZTE Confidential & Proprietary 19

password, user needs an USB key to access U31 system.

2.1 ZXO-08-04-001 Backup & Restore Solution

Feature Change: N/A