annex_06_03_zte netnumen u31-cn product description

NetNumen U31 (CN) Product Description (ETCA Platform)

V4


NetNumen U31(CN) Product Description (ETCA

Platform) Version Date Author Reviewer Notes

V1.0 2008-09-12 CN Product Line The First Version

V1.1 2010-02-01 CN Product Line Add Principle for Network Bandwidth

V2.0 2010-07-15 CN Product Line Add ETCA hardware structure description

V2.2 2011-07-18 CN Product Line Add and modify some system features

© 2011 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used

without the prior written permission of ZTE.

Due to update and improvement of ZTE products and technologies, information in this document is subjected to

change without notice.


II ZTE Confidential Proprietary

TABLE OF CONTENTS

1 Overview ................................................................................................................ 6

2 Highlight Features ................................................................................................. 6

2.1 Compliant with International Standard Protocol ....................................................... 6

2.2 Open System Structure and Interface ...................................................................... 6

2.3 Powerful Network Management Function ................................................................ 6

2.4 Unique Functions of Application Management ......................................................... 6

2.5 Flexible System Expansion ...................................................................................... 6

2.6 System Remote Upgrading and Installation ............................................................. 6

2.7 Support Dif-level and Dif-authorization Management ............................................... 6

2.8 Support Multi-Access Mode ..................................................................................... 6

3 System Principle ................................................................................................... 7

3.1 TMN Principle .......................................................................................................... 7

3.2 U31(CN) System Principle ....................................................................................... 8

4 System Architecture ............................................................................................. 9

4.1 Networking Architecture ........................................................................................... 9

4.2 Software Architecture ............................................................................................ 10

4.3 Logical Architecture ............................................................................................... 11

4.4 Functional Architecture .......................................................................................... 11

5 Networking Structure .......................................................................................... 12

5.1 Logic Structure ...................................................................................................... 12

5.2 Local Networking Scheme ..................................................................................... 13

5.3 Remote Networking Scheme ................................................................................. 13

5.3.1 DDN Mode ............................................................................................................. 14

5.3.2 E1 Mode ................................................................................................................ 15

5.3.3 HDSL Mode ........................................................................................................... 17

5.4 Integrated Networking Scheme .............................................................................. 17

6 Hardware Structure ............................................................................................. 18

6.1 Product Physical Structure ..................................................................................... 18

6.1.1 Rack Introduction ................................................................................................... 18

6.1.2 Shelf Introduction ................................................................................................... 19

6.1.3 Board Introduction ................................................................................................. 19

6.2 Hardware Architecture ........................................................................................... 20

6.2.1 ZTE ETCA Platform Features ................................................................................ 21

6.3 Reliability ............................................................................................................... 22

6.3.1 Hardware Reliability ............................................................................................... 22


ZTE Confidential Proprietary III

7 Functionality ........................................................................................................ 22

7.1 Fault Management ................................................................................................. 22

7.1.1 Fault Collection ...................................................................................................... 23

7.1.2 Fault Display .......................................................................................................... 23

7.1.3 Alarm Acknowledgement and Un-acknowledgement ............................................. 24

7.1.4 Alarm Clear............................................................................................................ 24

7.1.5 Alarm Synchronization ........................................................................................... 24

7.1.6 Alarm Manual Forward Function ............................................................................ 24

7.1.7 Alarm Data Export ................................................................................................. 24

7.1.8 Alarm Rules Management ..................................................................................... 25

7.1.9 Alarm Handling Suggestion ................................................................................... 26

7.1.10 Alarm Parameter Setting........................................................................................ 26

7.1.11 Fault Query and Statistics ...................................................................................... 27

7.1.12 Event (Notification) Management ........................................................................... 27

7.1.13 Alarm Box and Its Management ............................................................................. 27

7.2 Topology Management .......................................................................................... 27

7.2.1 Navigation Tree ..................................................................................................... 28

7.2.2 Display of Topology Map ....................................................................................... 28

7.2.3 Control of Topology Map Display ........................................................................... 28

7.2.4 Filter of Topology View .......................................................................................... 28

7.2.5 Displaying Topology Data According to User Authority .......................................... 28

7.2.6 Alarm Information of NE Node/Links between NEs ................................................ 28

7.2.7 Virtual NE/Virtual Link ............................................................................................ 28

7.2.8 Grouping Node ...................................................................................................... 29

7.3 Configuration Management .................................................................................... 29

7.3.1 Data Configuration ................................................................................................. 29

7.3.2 Dynamic Data Management .................................................................................. 30

7.3.3 Data Synchronization ............................................................................................. 30

7.3.4 Version Management ............................................................................................. 30

7.4 Performance Management .................................................................................... 30

7.4.1 Measurement Task Management .......................................................................... 30

7.4.2 QoS Task Management ......................................................................................... 30

7.4.3 Querying Performance Data .................................................................................. 31

7.4.4 Performance KPI ................................................................................................... 31

7.4.5 Statistics Analysis .................................................................................................. 31

7.4.6 Performance Report .............................................................................................. 31

7.5 Security Management ............................................................................................ 31

7.5.1 Department Management ...................................................................................... 31

7.5.2 Login Management ................................................................................................ 32

7.5.3 User Management ................................................................................................. 32

7.5.4 Setting Security Event ........................................................................................... 32

7.5.5 Role/Role Set Management ................................................................................... 32


IV ZTE Confidential Proprietary

7.5.6 User Account Management ................................................................................... 32

7.6 Log management ................................................................................................... 32

7.6.1 Log query .............................................................................................................. 33

7.6.2 Setting Log Filtering Conditions ............................................................................. 33

7.6.3 Log Export and Print .............................................................................................. 33

7.6.4 Log Policy .............................................................................................................. 33

7.7 Task Management ................................................................................................. 33

7.7.1 Task Management ................................................................................................. 33

7.8 System Management ............................................................................................. 34

7.8.1 Server Monitoring .................................................................................................. 34

7.8.2 Database Monitoring .............................................................................................. 34

7.9 Software Management ........................................................................................... 34

7.9.1 Installation and Upgrade ........................................................................................ 34

7.9.2 NE Software Version Management ........................................................................ 34

7.10 Inventory Management .......................................................................................... 34

7.10.1 Inventory Management .......................................................................................... 34

7.10.2 Inventory Statistics ................................................................................................. 34

7.11 Trace Management ................................................................................................ 34

7.11.1 Signaling Tracing Flow .......................................................................................... 35

7.11.2 Signaling Tracing Setting ....................................................................................... 35

7.11.3 Signaling View and Maintenance ........................................................................... 35

7.11.4 Clock Management ................................................................................................ 35

7.12 MML Terminal ........................................................................................................ 36

7.13 Report Management .............................................................................................. 36

7.14 Online Help ............................................................................................................ 36

8 System Interface ................................................................................................. 36

8.1 CORBA Interface ................................................................................................... 36

8.2 SNMP Interface ..................................................................................................... 37

8.3 MML Interface ........................................................................................................ 37

8.4 File Interface .......................................................................................................... 38

8.5 DB Interface........................................................................................................... 39

9 Reliability ............................................................................................................. 39

9.1 System Reliability .................................................................................................. 39

9.1.1 Data Security ......................................................................................................... 39

9.1.2 System Security ..................................................................................................... 40

9.2 Hardware Reliability ............................................................................................... 42

9.3 Software Reliability ................................................................................................ 43

9.4 Principle for Network Bandwidth ............................................................................ 44

9.4.1 Bandwidth Calculation between U31(CN) Server and NMS ................................... 44

9.4.2 Bandwidth Calculation between U31(CN) Server and Client .................................. 44


ZTE Confidential Proprietary V

9.4.3 Bandwidth Calculation between U31(CN) Server and NE ...................................... 44

10 Technical Indices ................................................................................................ 45

10.1 System Performance Indices ................................................................................. 45


VI ZTE Confidential Proprietary

FIGURES

Figure 3-1 Functional Layers of TMN ................................................................................... 7

Figure 4-1 Schematic Diagram of U31(CN) System Networking Structure ........................... 9

Figure 4-2 Schematic Diagram of U31(CN) System Software Architecture ........................ 10

Figure 4-3 Logic Structure Diagram of U31(CN) System ................................................... 11

Figure 4-4 Functional Architecture Diagram of U31(CN) System ....................................... 12

Figure 5-1 Networking of U31(CN)..................................................................................... 12

Figure 5-2 None-Layered Networking Scheme .................................................................. 13

Figure 5-3 Remote Networking Scheme ............................................................................ 13

Figure 5-4 Reverse Networking Scheme ........................................................................... 14

Figure 5-5 DDN Mode ........................................................................................................ 14

Figure 5-6 E1 Mode ........................................................................................................... 16

Figure 5-7 HDSL Mode ...................................................................................................... 17

Figure 5-8 Integrated Networking Scheme ......................................................................... 18

Figure 6-1 Rack Diagram of U31(CN) ................................................................................ 18

Figure 6-2 Front and Rear Panel of U31(CN) .................................................................... 19

Figure 6-3 View Management of ZTE ETCA platform ........................................................ 20

Figure 6-4 View of Internal Fabric ...................................................................................... 20

Figure 8-1 CORBA Interface of U31(CN) ........................................................................... 36

Figure 8-2 SNMP interface ................................................................................................ 37

Figure 8-3 MML Interface Command of U31(CN) .............................................................. 38

Figure 8-4 Medium DB interface Function .......................................................................... 39

Figure 9-1 System Redundancy based on Disk Array of Local Mode ................................. 42

Figure 9-2 System Redundancy based on Disk Array of Remote Mode ............................. 42

TABLES

Table 5-1 DDN Configuration ............................................................................................. 15

Table 5-2 Configuration of E1 Mode .................................................................................. 16


ZTE Confidential Proprietary VII

Table 5-3 Configuration of HDSL Mode ............................................................................. 17

Table 7-1 U31(CN) Alarm Information Details .................................................................... 23

Table 7-2 Alarm Rules ....................................................................................................... 25

Table 9-1 Required Bandwidth between U31(CN) Server and NE ..................................... 44

Table 10-1 System Performance Indices ........................................................................... 45


8 ZTE Confidential Proprietary

1 Overview NetNumen U31(CN) (hereafter, U31(CN) is used) system is built on a unified NM platform of ZTE, provides centralized management for all kinds of core network equipment of GSM/WCDMA/TD-SCDMA/CDMA/Wimax/IMS/EPC, such as MSC, MSC Server, MGW, HLR, SGSN, GGSN, MSCe, PDSN, AGW, AAA, MGCF, MME, SAE-GW, and CG. It provides functions of fault management, topology performance management, configuration management, security management, log management, trace management, inventory management, system management, U31(CN) is located in EMS layer of TMN model, and provides northbound interface such as CORBA, SNMP, File, and MML.

2 Highlight Features

2.1 Compliant with International Standard Protocol U31(CN) is strictly compatible with the TMN series recommendations of ITU-T, TMN, and 3GPP series NM protocol.

2.2 Open System Structure and Interface U31(CN) system employs J2EE platform frame, which is independent of the operating system platform and database. It provides various NM interfaces like CORBA, SNMP, MML, File and other interfaces.

2.3 Powerful Network Management Function U31(CN) system manages the whole GSM/WCDMA/TD-SCDMA/CDMA/WINMAX/IMS/EPS core network of ZTE, and provides standard management interfaces interconnected with the devices from other providers, so that different devices of the telecom network can be maintained and managed unitarily. U31(CN) provides an open cascading function, meeting the requirements of centralized management combined with distributed management.

2.4 Unique Functions of Application Management In addition to configuration management, fault management, performance management and security management, U31(CN) system provides a unique function of application management, including management capability of authority


ZTE Confidential Proprietary 9

and domain division, self-defined browsing of various data in the system, system fault relativity and fault treatment consulting function, customized report and time report management, and signaling tracing.

2.5 Flexible System Expansion The plug-in structure design of U31(CN) software structure ensures the system to be capable of fast developing new devices and new service management. The system supports management of NE devices and can be conveniently extended to the management of the network layer and service layer. Moreover, by customizing the protocol handling components in the NE adaptive frame, it can smoothly access various devices, and support the coexistence of multi-versions.

2.6 System Remote Upgrading and Installation U31(CN) system enables remote upgrading and installation of the system through the network, and implements the operation of device upgrading and installation through remote clients, meeting the rapid response of service requirements change, and reducing the costs of system software distribution and maintenance.

2.7 Support Dif-level and Dif-authorization Management With respect to the operator’s maintenance management strategy, the system can be implemented based on network dimension and maintenance strategy in the light of the operator’s recommendation.

2.8 Support Multi-Access Mode U31(CN) system provides GUI client access, telnet access, and Web access. Telnet access is convenient to make configuration of NEs from any PC client without installing client software. In addition, the GUI interface enables operators to perform all of the operations of NEs.

3 System Principle Designed on TMN (Telecommunication Management Network) concept and operating mechanism proposed by ITU, U31(CN) system satisfies the architecture and function requirements of TMN. U31(CN) system is in the EMS layer of the TMN, and provides a part of functions of the NMS layer.



3.1 TMN Principle The management method of the telecom network is progressing as the telecom network is expending and the science technology is developing. Its development can be divided into the following three stages: Manual management -> dispersed computer aided management -> integrated distributed management. The purpose of telecommunication network management is to utilize network resources to the maximum extent, reduce the enterprise operation cost, and provide telecom services of high quality and high reliability. The TMN just provides a complete solution for the implementation of telecommunication network management. It simplifies the management mode of telecom operation enterprises in hybrid networks with multiple vendors, reduces management cost of telecom operation, and thus brings more benefits to the carriers.

The TMN provides an organized network structure to achieve interconnection between the Operating Systems (OS) and between the OS and the telecom equipment. It is a management information exchange system that adopts interfaces of standard protocols and information to support planning, configuration, installation, operation and organization of the telecommunication networks and the telecom services.

As shown in the figure below, the functions of TMN are classified into five layers, from upper to lower layers, namely: Business management layer, Service management layer, Network management layer, Network element management layer and Network element layer in sequence. U31(CN) system is located in Network element management layer, and includes a part of functions of Network management layer. The layers directly related to U31(CN) system include Network management layer and Network element layer.

The business management layer consists of management functions that support the decision of the entire enterprise, such as generation of economic analysis reports and quality analysis reports, and setting of tasks and objectives. Its user is the top-level administrator of the telecom operator.

The service management layer comprises functions of service provision, service control and monitoring and service-related charging processing, which involves such services as telephone switching services, IN services, mobile communication services and leased data line services. Its user is the service operation administrator.

The network management layer provides network management functions, such as network traffic monitoring and control, dispatching of network protection routes, monitoring and measurement of the regenerator section/route quality, and comprehensive analysis and coordination of multiple network faults. Its user is the network organization administrator.



Figure 3-1 Functional Layers of TMN

The network element management layer implements operation and management of one or more NEs, such as remote operation and maintenance of the switches and the BSCs, and equipment software and hardware management. It is not responsible for the issues between the NE management layer and the NE. Its user is the equipment O&M operator.

The Network element layer is a network factor in the telecom network, realizing basic functions of the telecom network. It plays a managed role in the network management, providing original data of network management. In the WCN, the network elements include MSC, MSC Server, MGW, HLR, SGSN, GGSN, and CG.

TMN specifies that, the layers are interconnected with each other by Qx interface, and the CORBA interface may be employed, and the CORBA/MML interface to the upper NMS. Along with the TMN’s developing, the CORBA interface with simple

Business management layer Manager

MO

Network element layer

Network management layer

Network element management layer

Service management layer

Agent

MO

Q3

Q3

Q3/Corba

Qx

Agent

ManagerMO

Agent

ManagerMO

Agent

ManagerMO



realization, unified standard and object-oriented structure, has become the mainstream interface between the NMS layer and EMS layer.

3.2 U31(CN) System Principle U31(CN) system refers to the layer division design of the TMN. The whole U31(CN) system is located in the EMS layer, providing Itf-N interface to the NMS layer, such as CORBA, SNMP, and MML, and realizing the accessing of OMM to the NE layer and the management of NE. It realizes a unified monitoring and management on one or multiple types of devices.

U31(CN) system provides standard management functions defined by the TMN system, i.e., security management, fault management, performance management and configuration management, etc. For the ease of use, it provides functions of log management and report printing. In addition, it provides many supplementary tools in the NE layer (some of the tools are optional, i.e., not included in the standard software configuration of the system. The following is the same).

U31(CN) system realizes functions of Network element management layer and a part of functions of the Network management layer in the TMN. It is to make centralized management, monitoring and counting on the NE devices of the lower layer. The higher the management layer is, the weaker the function of the NE operation and maintenance is, and meanwhile, the function of the network centralized management is stronger.

The OMM system realizes NE management functions in the TMN. Besides the four management functions required by the TMN (the four functions are configuration, performance, fault, and security), OMM layer provides series of supplementary tools according to the needs of the device operation and maintenance (O&M), facilitating the local operation and maintenance to the most.

U31(CN) system adopts the general architecture of J2EE, and uses the excellent idea of JDMK (Java dynamic management tool set).

4 System Architecture

4.1 Networking Architecture U31(CN) system is flexibly applied to multiple networking modes. If NE devices and U31(CN) system are in the same site, allocate the NE and U31(CN) server in the same LAN. If the NE and U31(CN) server are not in the same site, the WAN (Wide Area Network) networking is used. Connect the NE with U31(CN) server through the router and link DDN/E1. U31(CN) client can also connect to U31(CN) server remotely. The figure below describes the network distribution structure of the



system networking.

Figure 4-1 Schematic Diagram of U31(CN) System Networking Structure

4.2 Software Architecture U31(CN) system is built on the unified NM platform of ZTE, realizing NM software functions by modules. The architecture of the system software is as shown in Figure 4-2.

l Work Station Function WSF: responsible for the friendly presentation of the NE information to user in the form of letter and graphic interface. Meanwhile, it transfers the operation of the operator to the Operating System Function (OSF). OSF organizes the application logic handling of the operation. WSF realizes the interface G and interface F in the TMN, among which interface G is man-machine interface, and interface F is the interface between WSF and OSF.

l Operating System Function OSF: handling the information related to the application of NE management, supporting and controlling the realization of NE device management function, and including several system management application functions, i.e., fault management, performance management, security management, configuration management.



Figure 4-2 Schematic Diagram of U31(CN) System Software Architecture

l NE Function NEF: the managed network devices of various kinds, such as MSC Server, SGSN, HLR.

l Northward interface Access Function NAF: the access agent function of upper layer NM system NMF, providing four kinds of access interfaces, MML, CORBA, DB and SNMP. Through the agent function, it can realize the accessing of management applications, to implement the network layer management functions of the integrated NM system.

l The operating system platform of U31(CN) system may select Windows NT/2000 or Sun Solaris, realizing the platform non-relativity through JVM. The database system can be purchased according to the user’s needs. The employed database is suggested to be ORACLE;

l It is allowed that some functions are not installed in the system (for example, performance management is not installed), and other functions can run normally (the basic functions such as configuration must be installed).

4.3 Logical Architecture The logical architecture of U31(CN) system is as shown in the following figure, and

NAF

OSF

WSF

MIF

NEF

NMF Application

NetNumen U31



three-layer architecture complies with TMN recommendations. The three layers are in the relations of manager and agent. In U31(CN), the agents NE provide the function of NE management, and reporting the management functions to NMS, so that the network management layer can realize the integrated management of the whole network. Between U31(CN) and NE, the interface Qx is employed to realize the interaction of management information, communicating with the NMS through the standard CORBA/SNMP/MML interface. OMM is a local maintenance system, realizing the local maintenance and operation of NE, and realizing the management and application of the equipment room at the local end. U31(CN) is composed of client and server. Between the client and the server, message is sent through interface F.

The logical structure of U31(CN) system is as shown in Figure 4-3.

Figure 4-3 Logic Structure Diagram of U31(CN) System

4.4 Functional Architecture The functions of U31(CN) system include configuration management, fault management, security management, topology management, performance management, report management, and character terminal. The client and the server communicate through the F interface message. The server and the NE communicate through internal interface message. U31(CN) provides CORBA, MML, SNMP and other kinds of interfaces to the upper layer NMS.

Local Maintenance Function LMT is integrated into U31(CN), including trace management, service watching, voice management, file management, and clock



management.

The functional architecture diagram of U31(CN) system is as shown in Figure 4-4.

Figure 4-4 Functional Architecture Diagram of U31(CN) System

5 Networking Structure

5.1 Logic Structure

Networking of U31(CN) system is very flexible. CN equipments can be managed in the integrated way with an integrated version, or independently with their respective versions. When the managed NEs are widely scattered, distributed management can be used. First, deploy U31(CN) Servers by areas; then fulfill concatenation among U31(CN) Servers.

The out-of-band (transmission of NM data is separated from that of business data) network management mode is recommended for networking to ensure that services can run normally and service data is separated from network management data. If the investment is high, the in-band (transmission of NM data is the same as business data) NM networking mode is also practical.

Logical structure of U31(CN) networking is shown in Figure 5-1.



Figure 5-1 Networking of U31(CN)

The above figure shows the networking of a local area network. If the network condition is complex and the network crosses different areas, networking by area is recommended.

5.2 Local Networking Scheme This is the simplest scheme. In this case, U31(CN) server, client and NE are all in the same LAN, connected with Ethernet together. It is shown in Figure 5-2:

Figure 5-2 None-Layered Networking Scheme



5.3 Remote Networking Scheme In this case, the client is in the remote LAN or the CN equipment and client both are in the remote LAN, including the access modes as follows: DDN, E1, HDSL, and X.25 (its max bandwidth is 64kbps-not-recommended.It is shown in Figure 5-3:

Figure 5-3 Remote Networking Scheme

There is another remote networking scheme named ‘Reverse’. In this case, the reverse client only can manage local NEs through the remote U31(CN) server, as shown in Figure 5-4:

Figure 5-4 Reverse Networking Scheme



5.3.1 DDN Mode

DDN mode has a high speed and stable transmission. Its bandwidth is from 64kbps to 2Mbps with routers and modems. It is shown in the Figure 5-5 as follows:

Figure 5-5 DDN Mode

Table 5-1 DDN Configuration

No. Type Spec. Num. Note

1 Router ZXR10 GAR 1+n N is decided by the number of remote RNC-LAN

2 Switch ZXR10 1816 Decided by need

16 Ports, to connect server, client and RNC in the LAN, the number is decided by the practical need

3 Twisted-pair 3 or 5 class X(m) Decided by need

4 Router sub-card RA-4HS 1+n To access MODEM for the local

U31(CN) client

5 Router cable V.35C1 1+n To connect router and MODEM




6 MODEM ASM-40 (1+n) To connect DDN, the max bandwidth is 2048kbps

Note: the rented DDN speed rate depends on the bandwidth, and the needed bandwidth is calculated by the number of remote RNC and clients.

5.3.2 E1 Mode

To transfer IP packages through E1 with 2Mbps, it is necessary to pick up time-slots at the end of E1.The maximum rate of each time-slot is 64kbps. With the CHANNEL technology, it will reach the rate of N*64kbps, and will satisfy different needs. Moreover, the router is the best choice for E1 module to extract time-slots, which can provide more stable performance. The topology map is shown in Figure 5-6:

Figure 5-6 E1 Mode



Table 5-2 Configuration of E1 Mode



2 Router sub-card RA-4CE1-75 1+n

N is decided by the number of remote RNC-LAN ,with using E1 coaxial interface board

3 Switch ZXR10 1816 By needs

To connect the equipment in the LAN such as server, client, RNC, etc. The interface number is decided by practical needs.

4 Twisted-pair 3 or 5 class X(m) It is decided by needs.

5 E1 DT75/3- n+1 To access E1 transferring network from router.

5.3.3 HDSL Mode

HDSL (High-data-rate Digital Subscriber Line) has modems on two ends of one or more twisted pairs. HDSL provides a symmetrical transfer rate; viz. the UL rate is equal to the DL rate. The effective transferring distance can reach 5km by only one twisted-pair. However, if HDSL is not stable, it is not recommended to be used in the network, with reference to Figure 5-7:

Figure 5-7 HDSL Mode



Table 5-3 Configuration of HDSL Mode

No. Type Spec. Num. Notes


2 Switch ZXR10 1816 By needs

16 ports, To connect the equipment in LAN such as server, client, RNC, etc. The interface number is decided by practical needs.

3 Twisted-pair 3 or 5 class X(m) By needs

4 Router sub-card RA-4HS 1+n To access HDSL modem on the end of OMCR

5 Router cable V.35C1 1+n To connect router and HDSL MODEM

6 HDSL MODEM Consistent with bureau equipments

(1+n) Provide the V.35 network interface

Notes: Nowadays, HDSL has already been updated to G.SHDSL. If G.SHDSL is used, the HDSL modem above will be replaced by SHDSL modem. Its spec. type is ASMi-52 product.

5.4 Integrated Networking Scheme It is combined with local LAN and remote LAN, and is often used. In this case, there coexist the local CN equipment and the remote CN equipment. The integrated networking scheme with DDN mode is shown in Figure 5-8 as follows:



Figure 5-8 Integrated Networking Scheme

6 Hardware Structure

6.1 Product Physical Structure The introduction of U31(CN) hardware deployment consists of:

l Introduction of Rack

l Introduction of Shelf

6.1.1 Rack Introduction

Normally, U31(CN) shares the rack with other NEs, which are based on ZTE ETCA platform.

U31(CN) cabinet adopts international standard 19-inch cabinet, in the dimension of 2200mm * 600mm * 800mm (H * W * D).



Figure 6-1 Rack Diagram of U31(CN)

6.1.2 Shelf Introduction

U31(CN) ETCA shelf follows PICMG3.0 standard, and the form factor is 619.5mm*482.6mm*415mm (H*W*D). U31(CN) shelf uses dual-insert structure, which is based on ETCA architecture. There are 14 slots, Slots 1~6 and 9~14 are only used for installing the blade server and Slots 7~8 are only used for installing switching network boards.

The diagrams of shelf are shown as below.

Figure 6-2 Front and Rear Panel of U31(CN)



6.1.3 Board Introduction

ETCA platform adopts the following hardware boards:

l OPB: Operate Process Blade;

l SWB: Switching Board;

SWB is ETCA switch sub-system developed by ZTE, which realizes Giga Ethernet switching function of system BASE and FABRIC plane, and provides 16 GE inter-shelf cascade ports by backboard externally.

OPB board provides 4 GE electrical ports and 1 RS232 port is provided by back board.

6.2 Hardware Architecture ZTE ETCA platform is oriented to all CN services and control NEs, such as MSC Server, CSCF, MGCF, CG etc.

Figure 6-3 View Management of ZTE ETCA platform



ETCA plug-in box has an intelligent hardware management system based on IPMI specification. CMM board realizes physical resource management and monitoring of manageable equipment in ETCA plug-in box, provides out-of-band system management interface for external or embedded system manager to realize bottom management of the entire system. CMM is the managing center of ETCA plug-in box; it is responsible for power-on control, status management, sensor data management of whole plug-in box. CMM is the key equipment for other suppliers ETCA boards to realize interconnection and interworking test. IPMC controller connects with boards by IPMB and makes them work under IPMI architecture management. It mainly fulfills monitoring, control and management of ETCA boards or key hardware resources of other shelf components; it also communicates with CMM by intelligent IPMB, reports various events to CMM and accept management and control from CMM.

Figure 6-4 View of Internal Fabric

Internal Fabric consists of Base Channel Network, Fabric Channel Network, Update Channel Network and Clock Synchronization Network.

IPMC

Front Board

IPMC

Front Board

IPMC

Front Board

IPMC

Front Board

IPMC

Front Board

IPMC

Front Board

IPMC

Front Board

IPMC

Front Board

Rear Board

Rear Board

Rear Board

Rear Board

Rear Board

Rear Board

Rear Board

Rear Board

IPMC IPMC

CMM CMM

IPMC

FanTray

IPMC

FanTray

IPMC

PowerEntry

Module

IPMC

PowerEntry

Module

IPMB0IPMB1



6.2.1 ZTE ETCA Platform Features

l Follow ETCA standard architecture

Products follow ETCA standard system design, including power supply input and distribution, engine structure, system intelligent management, backplane topological structure, connector, optical/electric channel, switch function and I/O interfaces.

l Strong shelf management

Products follow IPMI standard, establish an integrate equipment management system by independent CMM, dual-star IPMB and each FRU, provide resource sharing (backplane, fan plug-in shelf, power supply module), equipment management, sensor and evens management, user management, fan plug-I shelf, power supply module and remote maintenance.

l Easy-to-expand

It can improve products operating performance by addling blade server or cascade shelf; it supports smooth upgrading and expansion.

l Highly-reliable

Redundancy Protection

− Provide redundancy protection for key functional modules, when there is some fault, system will automatically switch to backup modules.

− DC power supply module adopts 1+1 redundancy protection; each module supports 2 circuits of -48V DC input.

− CMM supports 1+1 active & standby redundancy protection, and automatic data synchronization between active and standby modes.

− Board support 1+1 redundancy protection.

− Management and service bus adopt dual-star redundancy design.

Fault-tolerance

− Provide rich fault-tolerance functions; ensure reliability in terms of hardware and software design.

− Provide multi-level protection of software and data; be capable of self-detection and automatic restore. Provide protection for board software overload interruption.

− Board support mis-insert protection design.



− Provide anti-reverse connection for power supply and isolation design for power fault.

− Software support patch and on-line load.

Fault management

− Provide rich fault management functions to ensure system reliability, including fault detection, fault diagnosis position, independent fault information report etc.

− FRU unit realize fault detection and report by its IPMC module.

− Provide fault detection for fan plug-in shelf and access power supply module.

− Provide heartbeat detection for management channel.

− Provide fault detection for backup channel.

− Provide automatic fault position diagnosis.

l Easy-to-maintain

− Board, CMM, power supply and fan etc support hot-plug.

− Provide on-line upgrading of application programs.

− Chute is easy to wire routing before and back of the shelf.

6.3 Reliability

6.3.1 Hardware Reliability

U31(CN) adopts abundant redundancy technologies to improve system reliability. Moreover, U31(CN) also improves system maintainability with the system failure detection/isolation technology.

l Adopt high-reliable hardware

U31(CN) adopts ZTE new-generation V4 platform, it uses ETCA architecture, and strictly follows telecom equipment standard, and perfect design in tele-magnetic compatibility, over/under-voltage protection, ventilation and heat elimination, intelligent management, which effectively ensures system reliability and stability.

U31(CN) also adopts IP-SAN disc array for data storing, and this disc array adopts RAID5+hotspare technology, to ensure data security.



l Adopt 1+1 active & standby

U31(CN) system adopts 1+1 active & standby for all boards, system performs automatic detection for important resources (network interface, hard disc, etc) of boards, switch automatically for boards fault and alarm, which effectively ensures system reliability.

l Adopt large-capacity and expandable disk array

U31(CN) uses commercial IP-SAN disk array, which is capable of hard disc capacity expansion and is convenient for operators to expand capacity.

l Adopt redundant network link

U31(CN) adopts dual network ports to make a redundancy of key links such as links connected with core network NEs and link among GES switchboards, which guarantees the security of transmission.

7 Functionality

7.1 Fault Management The fault management module of U31(CN) system monitors the current use condition of the devices in real time, providing device alarm information and solutions to common faults, convenient for the user to know the current use condition of the devices. The user can avoid the device fault by analyzing the alarm information. Since there is a lot of alarm information when the device fails, U31(CN) provides the function of alarm information filtering and alarm relativity setting. It may only display the alarm information about which the user is most concerned. In addition, the system provides an alarm knowledge database. For common alarms, the user can solve it by referring to the help information in the alarm knowledge database. The alarm information and the topology management of U31(CN) are combined together. It is convenient to see the alarm of each NE device in the topology map. In addition, the alarm condition and quantity can be known according to the displaying color and prompt. The alarm information can generate work-dispatching card. The dispatching card system informs the device maintenance staff to solve the fault, thus implementing fault solution automation.

The fault management of U31(CN) system includes the following functions.

7.1.1 Fault Collection

The abnormal statuses generated by the NE will generate alarm information. The information includes serial number (sequence number), alarm type, alarm severity,



the NE generating the alarm and location information, alarm generating time, and alarm reason. The alarm information details are shown in the following table.

Table 7-1 U31(CN) Alarm Information Details

Alarm Information Parameter Meaning

Node code Number of U31(CN) server which handles the alarm;

System type Type of system which generates the alarm;

Serial number Unique number of the alarm, unique under the NE;

Generating position Alarm generating position

Description Situation description of the device causing the alarm

Level Alarm Level: critical alarm, major alarm, minor alarm and warning alarm.

Type

Alarm Type: telecommunication alarm, device alarm, QoS alarm, processor alarm, and environment alarm.

Possible Cause Cause generating alarm;

Confirm/Anti-confirm operator Name of person performing confirm/anti-confirm operation;

Confirm/Anti-confirm information Information input during confirming/anti-confirming;

Confirming type Alarm confirming status, ‘not confirm’ or ‘confirm’;

Time of occurrence: Alarm occurring time

Change time: If there is any change after the alarm occurs, it is the time when the change occurs;

Confirm/anti-confirm time Time of performing confirm/anti-confirm operation;

Detailed information Device status or other information when the alarm occurs, convenient for the maintenance personnel to further locate the alarm;

Extension property: NE distinct alarm information

7.1.2 Fault Display

The client of the fault management displays current alarm situation of the NE. The alarm information, which can be displayed, includes all the contents collected in the fault collection.

The way of viewing alarms include list way and rack diagram way. The rack diagram way displays the physical location and level of each alarm by showing the real rack physically. The alarm list and rack diagram can differentiate different levels of



alarms by colors.

In the list way, a user can sort alarms according to any displayed information category, for example, serial number (sequence number), alarm type, time information, location information, and alarm status sequence, which is convenient for comparing and handling the alarms. Additionally, current alarms and history alarms are separately displayed.

The alarm and its recovery information are sent to the topology management interface for displaying. Meanwhile, they are sent to the alarm box for broad and attractive displaying.

All the displayed information will be influenced by the user setting, such as alarm filtering and re-definition information set by the user.

7.1.3 Alarm Acknowledgement and Un-acknowledgement

”Alarm acknowledge” is to change the status of one alarm from un-acknowledgement to acknowledgement. ”Alarm UN-acknowledge” is to change the status of one alarm from acknowledge to un-acknowledge.

The alarm acknowledge/un-acknowledge are convenient for maintenance staff. When the alarm is found and maintenance staff has taken some measures, if this alarm need not be observed any more, the maintenance staff can set the alarm status as ‘Acknowledged’; after the alarm is acknowledged, if it is found that this problem has not been solved yet and needs to be observed again, the maintenance staff can set the alarm status back to ‘Un-acknowledged’.

The normal user with alarm operation right can only un-acknowledge his/her own alarm. Admin users can un-acknowledge all the alarms.

7.1.4 Alarm Clear

Alarm clear can clear one alarm data from network equipment and network management system. This function is used when the manual clearing is needed since alarms cannot be resumed due to some reasons. When the network management system cannot connect with the alarmed equipment, the alarm clear operation will fail.

7.1.5 Alarm Synchronization

Alarm synchronization is to make the present alarm information consistent between background U31(CN) system and the front-end alarm source. This includes automatic synchronization and manual synchronization.

1. Automatic synchronization includes 3 scenes:



l When the link is recovered between client and server, client will automatically synchronize with server.

l The alarm synchronization is triggered automatically between server and alarm source in the following cases:

− The broken link between front end and foreground equipment is recovered.

− U31(CN) server is restarted.

− The switchover of active/standby of front end equipment

l Timing synchronization function: this function will automatically be taken during a fixed time, between client and server, server and alarm source.

2. Manual synchronization

When a user finds the alarm data of NM system may be different from the network equipment, Manual synchronization can be used on client to synchronize the alarm data of specific network equipment.

7.1.6 Alarm Manual Forward Function

Alarm manual forward function is to forward the alarms in system by email or SMS to the maintenance staff.

7.1.7 Alarm Data Export

Alarm data export function is to export all alarm data in alarm view to files. The supported file formats include: TXT, EXCEL, PDF, HTML, CSV, etc.

7.1.8 Alarm Rules Management

When server receives the alarm and notification message, it will decide the processing manner according to the predefined rules. The rule customization function on client can conveniently view, modify, and delete the rules in server, or create new rules and submit them to server. All the rules are available only for the alarms and notifications generated after these rules are created.

Alarm rules are introduced below.



Table 7-2 Alarm Rules

Rule Name Function Description Alarm Re-definition setting

Set Alarm severity class according system type and alarm code.

Alarm Re-definition rule

Set the unified severity class for the alarms satisfying the rules.

Alarm storage filtering rule

If reported alarms satisfy the rule, discard them directly, neither storing into database, nor displaying in the present alarm real-time monitoring interface of client.

Notification storage filtering rule

If reported notifications satisfy the rule, discard them directly, neither storing into database, nor displaying in the present notification real-time monitoring interface of client.

Alarm Global Filtering rule

If reported alarms satisfy the rule, store them into database, but does not display in the present alarm real-time monitoring interface of client.

Alarm automatic forward rule

If reported alarms satisfy the rule, notify the designated users by email and short message.

Alarm automatic acknowledgement rule

If reported alarms satisfy the rule, change the state of this alarm to ‘acknowledged’.

Alarm automatic clearing rule

If reported alarms satisfy the rules, directly clear the alarm from the present alarm and put them into history alarm database.

Alarm delay rule If reported alarms satisfy the rules, delay a certain time and display them in the present alarm real-time monitoring interface of client.

Alarm suppression rule

Set the alarm sources and alarm codes of the suppression alarm (also called ‘primary alarm’) and the suppressed alarm (also called ‘secondary alarm’). When the primary alarm exists, the secondary alarm is suppressed to report.

Alarm merge rule

Only the alarm of the alarm code is reported when multiple alarms with the specified location and specified alarm code are generated, and the alarm of this alarm code is not reported in the future. When all alarms of this alarm code are cleared, the reported alarm of this alarm code is recovered.

Alarm Counting Rule

Applicable for the alarms of specified location and specified alarm code. When the count of the alarms of this specified alarm code reaches a certain number in the set period, a new alarm will be generated.

Alarm User Filtering Rule

Applicable to the Client. After the Client receives alarms from the Server, screen alarms through the alarm user filtering condition of the login user. Alarms meeting the condition can be displayed.

Alarm Box rule If reported alarms satisfy the alarm box rule, automatically forward the alarms to designated alarm box.



7.1.9 Alarm Handling Suggestion

The system equipment summarizes some alarm handling experiences after the long-time operation as a reference for the similar problem in the future. The summary of these handling experiences is the alarm handling suggestion.

The alarm handling suggestion interface displays the alarm system type index. For each alarm, the system provides the default handling suggestion. Users can record the handling suggestions according to their experiences. These alarm-handling suggestions can either be imported or exported. The file formats include Excel, PDF, HTML, and Txt.

7.1.10 Alarm Parameter Setting

Fault management module allows users to modify parameters related with alarms:

Alarm box setting: to set a series of actions after the alarms are sent to the alarm box. For example, voice alarms are only generated for Class one or Class two alarms.

Alarm color setting: different alarm classes have corresponding colors in client interface. Users can set the corresponding relationship between the alarm class and color according to their own situation.



Environment parameter setting: alarm is generated when the peripheral environment (temperature, humidity, smoke, etc.) is not in the scope of default or pre-defined setting. Fault management module allows users to set these threshold values.

7.1.11 Fault Query and Statistics

The user can obtain various detailed and desired fault information by fault browsing.

The user can set various alarm browsing conditions, including location of device, alarm level, current alarm status, alarm type, fault reason, time of alarm generating, recovering and confirming.

The browsing result can generate a report, which can be printed or saved as a file.

The user can count the current alarms and history alarms of the system in frequency. The statistics result can be used as the basis for analyzing system faults. The statistics can be made according to the alarm time, alarm type, alarm level, and NE where the alarm occurs. The statistics filter condition can be set by alarm location, alarm level, alarm category, alarm time, and status. The statistics result can be shown by a diagram.

7.1.12 Event (Notification) Management

Event (notification) is generated in NE, describing information of the status change occurring in the running process. These status changes do not indicate that the system fails, but they are the information that needs to be known in monitoring system running and deciding fault reason.

Event (notification) can be viewed by the list way, and can be queried.

7.1.13 Alarm Box and Its Management

The alarm box is usually placed at an outstanding position of the NM equipment room, and displays various faults of the system in the form of sound and light to remind maintenance personnel to focus on and handle the faults.

Moreover, the alarm box can send the alarm information to the maintenance personnel who have mobile phone and email address in the form of short message and email, so that the maintenance personnel will not miss important alarm information when he is not in the equipment room.

U31(CN) fault management system provides the function of alarm box setting, including the setting of short message user and the setting of alarm box parameters. The information of the maintenance personnel and what level of alarm will be sent to the personnel may be set, controlling the alarm level sent to the alarm box and



the sound & light displaying situation.

7.2 Topology Management The topology management of U31(CN) system provides a visual NE relation display and a network topology map, which can be opened. The topology map employs the industry prevailing structure of left tree and right diagram. On the left of the view is the NE topology tree, organized according to the configuration relation of NEs. On the right of the view is the panorama display of the NE devices, and it can display the NE topology structure by several levels. The panorama provides a panorama device display. The user can customize the background of the map, and set the longitude and latitude of the map. The functions of the topology map are closely connected with each management module. The alarm information and configuration information off the NE can be viewed through the topology map. Configuration, alarm, performance and diagnosis modules of NEs can be invoked. The topology management provides the functions such as logic view, grouping nodes, virtual NE, virtual link. The user can manage the devices and set virtual NEs in group, convenient for network display and analysis. The panorama provides the operations of part zooming in, searching, cascading display, and provides personalized interface setting. The user can customize the interface setting as his like, for example the icon, interface color, and view size.

The topology management includes the following functions:

7.2.1 Navigation Tree

Display the NE devices as a tree in the interface, and the navigation tree is formed. The topology map and the node of the navigation tree are in one to one correspondence. The navigation tree and the topology view are synchronized with each other. The navigation tree provides navigation function to the topology view, and the topology map displays the nodes of the related layer of the selected node in the navigation tree. The node of the navigation tree provides the functions related to the node, such as viewing the property, modifying the NE information, counting the sub nodes.

7.2.2 Display of Topology Map

The topology map of U31(CN) provides the panorama display of the device topology structure of the whole network. The NE device can be quickly located in the topology map. The topology map employs the coordinates of longitude and latitude, supporting geographical information system. The icon of NE device can be displayed in the actual geographical location of the map. The user can lock the setting of the NE device icon, so that it cannot be moved to other position, and can be moved only when it is unlocked. The node icon of the topology map can display the statistics information of the NE device, such as NE number under the node, link



number, group number, and alarm information.

7.2.3 Control of Topology Map Display

U31(CN) system supports moving the whole map, zooming in by each level, zooming out by each level, back to the original, whole view display, and partial zooming in. It supports forwarding and rewinding of browsing the topology map layers, and locating to any browsed map layer, and finding a specified NE device in the topology map. It supports changing background map of the topology. It can be configured as world map and China map to realize the NE device management of a large scope. In addition, it can be configured as a local area map and equipment room display map, so that the display of topology view is more human.

After the data synchronization of U31(CN) system is finished, the client will be refreshed, ensuring that the topology data are consistent with configuration data, while the relation of NE devices set in the topology map will not be influenced. The topology management module can set the layout way of NEs in the topology view, and deploy the display of NEs according to the set layout way. The layout includes five ways: cascading layout, tree layout, actinomorphic layout, explosion layout, and equidistant layout.

7.2.4 Filter of Topology View

The topology view of U31(CN) system can use NE, group, link set, group name, NE name, link number prompt to build a filter tree to filter the topology view, and it can implement the filtering directly according to the NE name input by the user.

7.2.5 Displaying Topology Data According to User Authority

U31(CN) system does not display the NE node and topology management module that the user is not authorized to operate, improving the security of the system and being convenient for the user to use at the same time.

7.2.6 Alarm Information of NE Node/Links between NEs

The icon of NE device/links between NEs in U31(CN) system can display the color of the highest level alarm in the corresponding physical devices. In addition, it can prompt the number of each alarm level and confirm the status. Additionally, the function of querying alarm and notification is provided.

7.2.7 Virtual NE/Virtual Link

U31(CN) system provides the function of creating virtual NE/virtual link. The user can set the NE to indicate peripheral device or device node, or set virtual link to



indicate that two NE nodes are interacted or interconnected.

7.2.8 Grouping Node

The grouping nodes are logic nodes defined by the user, and distributes the NE devices of physical view to the grouping nodes.

7.3 Configuration Management The configuration management of U31(CN) system provides the configuration function of CN NE to the user. It can manage the NE devices such as MSC/VLR (R99), MSC Server, MGW, GGSN, SGSN, HLR/AuC, CG, GMLC, and POC Server of ZTE. The configuration management provides the function of adding, deleting, modifying and viewing the NE data. Moreover, combined with topology management, the user can conveniently view the configuration and modify the configured information conveniently. The user can configure the information in U31(CN) server, and load the configuration data to the NE at once by the way of data transporting. The configuration management of U31(CN) system also provides the function of software version management, dynamic data management, and secure variable management.

The configuration management of U31(CN) system includes the following functions:

7.3.1 Data Configuration

The data configuration function of U31(CN) system supports the data configuration function of various NEs, including the creating, deleting, modifying and querying of configuration data. It manages various NE data in a centralized way, and saves multiple sets of configuration data of NE. It supports the function of batch creating and related creation of the configuration data. The configuration of U31(CN) system is organized in the way of tree structure, convenient for the user to select and browse in the configuration object visually.

The configuration of U31(CN) system supports the following parameters and contents:

Configuration of physical resources: physical resources refer to the physical entity of the NE devices and their relation, mapping relation, such as the situation of rack, chassis, slot, ant port, and the connection situation of each physical entity. Name of physical entity: number and working mode are configured in the physical resources configuration too. It provides a real rack diagram for configuration, convenient and visual.

Configuration of wireless parameters and SS7 signaling: including the parameter configuration of cell, carrier frequency, SS7 signaling link, office direction, route,



parameters of switching office.

The number analysis configuration is to determine network addresses and service processing modes corresponding to all kinds of numbers to ensure that the switch can correctly perform signaling interaction and voice speech channel connection.

The modification of the configuration will perform the consistency check, ensuring that no error occurs in the configured data of the system.

The modification on the configuration parameters made by the user will be recorded in the log in detail, convenient for tracing the configuration modification later. It includes the name of operator, modification time and the information of parameter value before and after being modified.

It is possible to export the current configuration data of the NE to a plain text file (xls, xml), and supports configuring the NE by importing a plain text file (xls, xml).

7.3.2 Dynamic Data Management

The dynamic data management of U31(CN) system provides the function of observing and managing the resources such as circuit, signaling link, route office direction, Sigtran coupling, AAL2 path.

7.3.3 Data Synchronization

The data transmission of U31(CN) system can synchronize the configuration data in the NE. The transmission schedule can be displayed at the client, and the detailed transmission log can be recorded.

7.3.4 Version Management

U31(CN) system provides the version control function to manage the software running in the NE. Including the functions such as file management of software version, version file downloaded to NE, NE uploading version file, and software version querying. Through software version management, it is convenient to upload NE software, control NE software version, and obtain NE software information.

When discovering the downloaded software version runs abnormally, you can roll over the version to the original one. To shorten the upgrade time, U31(CN) provides batch downloading and distribution to improve the efficiency.

7.4 Performance Management The performance management of U31(CN) system provides a large number of network performance counters and KPIs. The network administrator can count the



performance counters by creating performance measuring tasks, and analyze the network performance by checking the measured results of the counter to provide a basis for network planning and system maintenance. In addition, the network administrator can monitor the service quality and device performance. The performance management also provides the function of performance measuring threshold QoS. The network administrator can set the system performance threshold by creating QoS measuring tasks. When the system performance exceeds the threshold, the preset alarm occurs. The property of performance measuring task includes: logic task number, task name, collection granularity, start time, end time, time period mask, data mask, task number of the parent NE, server number, subnet number, office number, NE number, measuring type, measuring object. The property of QoS task includes: QoS task number, QoS task name, monitoring granularity, start time, end time, monitoring time period mask, date mask, server number, subnet number, office number, NE number, measuring type, measuring object, indices counting item, monitoring direction, four level alarm setting, monitoring object type.

The performance management of U31(CN) system includes the following functions:

7.4.1 Measurement Task Management

The measurement task management of U31(CN) system includes functions such as creating, deleting, querying, modifying the measurement task, activating/suspending measurement task, deleting expiring task, querying and deleting history measurement task, synchronizing measurement task with the foreground. The NE device will report the collected data to U31(CN) server according to the requirements of the measurement tasks.

7.4.2 QoS Task Management

QoS task management includes the functions such as creating, deleting, querying, modifying the QoS task, activating/suspending QoS task, deleting expiring task, detecting and identifying QoS task when configuration module deletes measurement object, QoS task alarm and alarm synchronization. QoS task management makes index settlement according to the data reported by the corresponding QoS task, generates 4-level alarms if the threshold is reached, and transfers the alarm information to the alarm module.

7.4.3 Querying Performance Data

The user can view the performance data saved in the database and the original data. The result of querying the original data is shown in the form of list, and it can be printed or saved as a file. For the query mode, the user can set the query scope (office or NE), query date and time, traffic type, and performance object.



U31(CN) provides performance counting functions to help the user count the performance indices of the system. The user can count through the template provided by the system, and freely customize some data template to count. In addition, the user can modify, view and delete related templates. This function enables the user to flexibly count the indices of the system according to various combinations.

U31(CN) system adds the statistics project that users are especially concerned with to the database as default statistics indices. Users can view the definition way, realizing method and algorithm of these statistics projects. For some statistics projects that users are quite concerned with, users may tailor the statistic project by customizing the project functions, including its name and algorithm.

The queried and counted result of the reports can be indicated by the form of the data list and diagram. It can be saved as the file in the form of Excel, text or HTML.

7.4.4 Performance KPI

KPI is a key index of NE performance. It may be a statistics item under the measurement item, and can be a new statistics item obtained by the multiple statistics items under the interface by some formula editor. The performance KPI management of U31(CN) system includes functions of adding, modifying, deleting KPI items, and querying the KPI data.

7.4.5 Statistics Analysis

The statistics analysis function of U31(CN) system can make a second counting of the performance data according to the statistics counting formula, and get the data of statistics analysis. The analysis ways are statistics analysis of fixed conditions, and statistics analysis of customized conditions.

7.4.6 Performance Report

U31(CN) system periodically generates reports in a user-defined format and sends them to the user by email. The system can use the fixed performance report defined before system running or generate the performance report customized during system running. In addition, the system also supports graphical report.

7.5 Security Management The security management of U31(CN) system assigns the authorities of NM function to users through the way of user role authority management. The system creates user role and assigns different NM function authorities through the function of user role management. It assigns one or more user roles to the user through user



management, so that the user has the NM function authority of the user role, while he is assigned with the user role. The authorities combined in user roles include: adding, deleting, and modifying each NE, and viewing its operation authorities; modifying NE property, viewing its operation authority; use authority of each module in U31(CN); use authority of sub function item in each function module.

The security management of U31(CN) system includes the following functions:

7.5.1 Department Management

The department management provides function of maintenance department information, convenient for the NM operator to manage, including the function of creating a new department, querying information of all departments, querying information of a department, modifying department property, and deleting a department.

7.5.2 Login Management

Login management authenticates an identity of a login user, including login time of the user, login IP, whether the user is locked, whether the user is disabled, and whether the number of the current users reaches the maximum login threshold.

7.5.3 User Management

A super user is automatically generated while the system is being installed, and the super user has the highest authority. The super user can create other users and assign authorities to other users. Other users can also create users and assign authorities to them, but the authorities of the created users cannot exceed the authorities of the creators.

7.5.4 Setting Security Event

The security management module can generate some user-concerned security events, for example, authentication failed, user locked, and user disabled. These events are recorded to the log module for user query in log management.

7.5.5 Role/Role Set Management

Role is a set of some operation authorities. One role can be assigned to multiple users, and the system authenticates the user according to the user role. Roles can be locked. If one role is locked, the users of this role lose the authorities of the role.

Role set is a collection of a group of roles. To assign a role set to a user is to assign multiple roles of this role set to the user. Role set can also be locked. If a role set is



locked, the users with this role set lose the authorities corresponding to the role set.

7.5.6 User Account Management

U31(CN) system sets rules of user account through the function, including password policy, password length, and account length.

l Password policy

− Support weak password check, such as minimum length, must include at least three kinds of characters, etc.

l Account lock rule: include never lock, lock permanently, lock temporary, lock after wrong password entering for N times, etc.

Account check: Cannot be same with nearly N day’s deleted accounts, Notify account expiry before N days.

7.6 Log management Managing login users: view login user information, including the user login IP, login time, and connection type.

l Forcefully Disconnecting Users: the super administrator can forcefully disconnect department users when finding these users are attempting illegal operations.

l Log Management

Log management records logs and manages logs. In terms of log contents, there are three log types as follows.

l Operation log

Records users’ operation information, including the user names, operation levels, operation names, command functions, operation objects, NE groups, NE addresses, start time, results, failure causes, host address and access modes.

l Security log

Records information of user login and logout, include the user names, host address, log names, operation time, access modes and detailed information.

l System log

Record the completion status of the severs’ timed tasks, including sources, levels, log names, detailed information, host address, start time, end time and associated



logs. Using the log management function, the operator can query logs, view detailed information, as well as set and query log-filtering conditions.

The log management of U31(CN) system includes the following functions:

7.6.1 Log query

U31(CN) system records detailed log information, including operation log, system log, and security log.

The operator can query all kinds of logs, and specify log query conditions, including user name, time range, operation permission, etc.

The operator can sort the displayed log records in an ascending or descending order according to a field.

7.6.2 Setting Log Filtering Conditions

The user can set the filtering conditions (such as a filtering level), and the logs lower than the level are filtered.

7.6.3 Log Export and Print

U31(CN) system supports exporting and printing queried results or log data of the current page to the specified path. After data exporting, the system still keeps the log records.

U31(CN) supports kinds of file formats, such as TXT, HTML, PDF, excel, etc.

7.6.4 Log Policy

U31(CN) system provides log backup policy, and the policy of log recovering and being saved in the database. Through the log backup scheme, the log can be exported to a file format in a fixed time or periodically. Through the scheme of log recovering and being saved in the database, the log which failed in being written in the database can be recorded in the database again.

7.7 Task Management

7.7.1 Task Management Through task management, provide data backup, file size monitoring, and resource management. Supports customized task management.



7.7.1.1 Common Task

l History Data Archival

It provides backup and deleting of log, performance, and alarm history data. It modifies task-executing conditions and views the execution log.

l Configuration Data Backup

It provides OMM database backup, makes backup of all basic data, it only backs up the data record, not including table structure and history alarms, notifications, log, primary performance data etc, the alarm data has independent backup functions.

l Version and Database Backup

It provides backup for both database and file system, the database backup is for all database structure(including all database objects structure ) for OMM , and basic data records, not including history alarms, notifications, log, primary performance data etc, these history data has independent backup functions. The required file types in file system include: version file, configuration, and operation period files.

l File Cleanup

It monitors performance, alarms, log, database files etc directories, which stores data, to prevent the size from being to large, and provides regular cleanup function for directories.

l MML Timing Task

It customizes MML task according to specific requirements, to meet individualized requirements.

7.8 System Management

7.8.1 Server Monitoring

It provides monitoring functions for OMM server, system administrator queries server performance in daily maintenance work, and monitors application server’s CPU usage rate, memory usage rate, hard disc usage rate etc KPI. Users set corresponding monitoring threshold according to actual configuration of application server, system automatically initiates monitoring on corresponding indices and sends related alarm information.

7.8.2 Database Monitoring

For OMM database server, system administrator monitors database resource in



daily maintenance work, such as query table space, data table information etc; execute data table import & export, data table cleanup. maintenance, etc. Users set corresponding monitoring threshold according to actual configuration of application server, system automatically initiates monitoring on corresponding indices and sends related alarm information.

7.9 Software Management

7.9.1 Installation and Upgrade

U31(CN) provides a completely integrated setup package with GUI interface for the user to install U31(CN) database, U31(CN) client, and U31(CN) server. User can upgrade the U31(CN) client, server, or database from a certain old version to a new version by executing the scripts that exist under a certain directory of the setup package. U31(CN) also supports centralized update. U31(CN) sends the NE software for updating to NE side. NE received the update order, it will update automatically with the update software getting from U31(CN).

7.9.2 NE Software Version Management

System can provide a unified, centralized, batch, remote, automatic update function for variant network elements. The NE Version Management supports the following functions: Customized upgrade for both back end (BE) software and front end (FE) service version; Batch and remote upgrade according to the NE type; Batch and remote upgrade according to the area type; Supports rollback when upgrade fail; Supports scheduled version upgrade; Supports upgrade detailed log.

7.10 Inventory Management

7.10.1 Inventory Management

It maintains and manages software and hardware inventory information in NE layer, and provides this information to subordinate OMM by Itf-N, as per operator requirements on unified management of telecom inventory. Now the management covers rack, frame, board, host etc main inventory, as well as router, switch, network concentrator, electricity, alarm box, printer, firewall, DNS, NTP, CGSL server etc affiliated equipment. Users view related inventory resources, and provides inventory export function in file format.

7.10.2 Inventory Statistics

It provides separate presence of inventory according to NEs, and views asset type



and quantity. It also provides asset exporting function, the exported files support xml, txt, xls, csv, etc.

7.11 Trace Management U31(CN) system provides the function of user information and signaling information tracing. The tracing system can trace the information such as user location, service and location update according to the user number identification. Required by the project maintenance, the tracing functions can also trace various signaling message of NE device, such as MAP message, BICC message, and M3UA signaling message. The tracing function is applied during project maintenance and fault location, which is a very practical local maintenance tool.

7.11.1 Signaling Tracing Flow

Signaling tracing is from client in the way of task. This task is then transferred to the signaling tracing front-end module through server. In the task, some tracing conditions such as signaling type are defined. When the service process generates a signaling, the signaling will first be checked if it is satisfied with the pre-defined condition set by signaling tracing front-end module. If satisfied, the signaling will be sent to the signaling tracing front-end module, processed in server, stored in database, and finally transferred to client.

7.11.2 Signaling Tracing Setting

The general information of the signaling is displayed in client in form of list. If user needs to check the detailed information of one signaling, it can be displayed in form of tree through decoding program.

The tracing condition of signaling tracing task includes: subscriber tracing select (for all or partial subscriptions), network element module number select, signaling type select, tracing duration, signaling tracing number (after tracing one certain number of signaling, the tracing will pause), self-defined tracing beginning/ending time.

7.11.3 Signaling View and Maintenance

There are three ways to view signaling data on client:

l Signaling list: overview of the general signaling; the order of signals, signals missing or not, used to identify if the service flow is right.

l Signaling detail information: check if the content of each field of each signaling is right; check if process and service state is right.



l Signaling codec information: check the original hex information of the signaling; compare the detailed information of the codec and signaling; limit the scope of error signaling; check if codec is right.

l There are three ways to maintain signaling data on client:

l Signaling specific format: save signaling list and signaling detail information as the particular file format, this can only be opened by signaling program.

l Excel format: save signaling details into Excel.

l Text format: save decoded signaling detail information into TXT file. Use can view the content with other particular tools.

7.11.4 Clock Management

U31(CN) supports NTP clock synchronization mode.

Network Time Protocol (NTP) is a protocol for computer time synchronization, it helps the computer synchronize the time resource or server, to keep time synchronization for the system and an accurate time resource, and prevent malicious protocol attack by encryption. It is usually used for hosts in LAN to synchronize the clock with other NTP hosts via Internet, and then continues to provide time synchronization to other clients in LAN.

EMS system is based on standard SNTP protocol; it realizes time synchronization among different hosts in the same LAN. EMS OMM, as NTP server, provides NTP clock resource, it pushes other OMMs in the LAN work as NTP client and performs time synchronization; EMS OMM works as NTP client, and synchronize the third-party clock server.

U31(CN) system provides clock function to query and set the clock and timer of the NE devices. The clock consistency function can keep the clock of the internal MSC NEs, NE and U31(CN) consistent. The clock modification function can modify the time employed by NE or U31(CN).

7.12 MML Terminal U31(CN) can execute various operations of NE client in the way of character terminal function, and simplify the repeated operations by executing batch processing script command. The character terminal will check and pre-process the grammar of the command/script. The execution result will be displayed after the execution is finished.



7.13 Report Management U31(CN) report management module provides strong report management functions, which can manage various reports, generated by U31(CN) system, such as performance report, alarm report, configuration management report. U31(CN) system provides the report server function. Set a server as the report server, and the reports are sent to the report server. The client visits the report server to view the reports. The report management module provides report designer, report template management. The users can customize the report format and report template by the two functions. The report management module also provides the function of report task management, report file management, report output/print, etc.

7.14 Online Help U31(CN) system provides online help function. The operator can learn the operation of the related module by searching the help content of each module, and solve some common problems through the help system. By F1 hot key invoking or menu invoking, the help system provides two help searching ways, i.e., by functional tree diagram and by key word.

8 System Interface U31(CN) system provides kinds of NM interfaces to the upper level NMS, CORBA, SNMP, and MML interface. The NMS can realize the operations such as configuration management, fault management, performance statistics, security management etc. through the NM interface.

8.1 CORBA Interface The CORBA interface of U31(CN) is built on the commercial CORBA platform, with the bottom communication protocol as TCP/IP. Through the CORBA interface, NMC can use the management function of different management function domains, such as configuration management, performance management, and fault management, dynamically obtaining the information of network configuration, performance and fault, to realize the management function of network layer.

The application process of the NMC and U31(CN) are running on ORB. The communication between ORBs employs the IIOP protocol running on TCP/IP. Any protocol of data link layer and physical layer is applicable only if TCP/IP is supported. The CORBA interface of U31(CN) is as shown in the following figure.



Figure 8-1 CORBA Interface of U31(CN)

The CORBA interface complies with 3GPP32, and has done IOT with some operators; it has been used in the network for Chine Mobile, China Telecom, etc.

8.2 SNMP Interface Core network management system can both provide SNMP manager function and SNMP Agent function, shown in the following figure.

Figure 8-2 SNMP interface

NMS

NE

Message ofCORBA interface

Configurationinterface

Fault interface Performanceinterface

Man-machinecommand

CORBA interfaceprocess

Server application processZXWN OMC server



SNMP manager function is used when network element system can be managed by SNMP. At this time, network elements act as SNMP Agent to manage by NMS.

SNMP agent function is used when upper network management requires managing core network management in SNMP (for example, the upper network management system is HP NNM). At this time, the upper network management system acts as SNMP Manager.

Core network management system implements fault management and performance statistic data management.

8.3 MML Interface The MML interface of U31(CN) is based on the TCP/IP protocol, with interface command employing MML format, used for accessing upper level NM command to NE or U31(CN) server. The supported TCP networking ways include DDN/E1, ISDN, X.25, PSTN etc. Through MML interface, the NMS can dynamically obtain the message of the network configuration, performance and fault. The user may send man-machine command to configure NE, create measurement tasks and set alarm related parameters, to realize the management function on the network layer. The MML interface of U31(CN) can set different message ports for different NM functions. Users can self-define the configuration according to their own needs. The ports of each function domain can be combined freely, for instance, the alarm port and the port of performance data report can be combined into one. While the system is running normally, U31(CN) server keeps monitoring these ports all through. If any NMS sends a connection request, a TCP channel will be created, implementing the communication interaction between U31(CN) server and NMS. To each port, multiple NMS terminals can be connected, and the mutual non-relativity of multiple NMS connection can be ensured.

The MML interface of U31(CN) is as shown in the following figure.



Figure 8-3 MML Interface Command of U31(CN)

8.4 File Interface According to database view, the booked data is transformed to the defined file and report to NMS periodically through FTP. It is also possible to save in the specified path NMS can pick the information periodically.

Convention between Itf-N and NMS:

l Data file format

l Data file organization method

l Data file name rule

l Time data picking time

l Data file complimentarily getting rule

l Local save time of T file

l Data file get method

l Data file compress method

User can define the period of data file saving. The default value is 3 days. Data file from U31(CN) to NMC, at most 20 minutes is needed. U31(CN) inventory information stored includes as a minimum physical location (building, floor, suite, rack, shelf, slot, port), equipment electronic serial numbers, firmware level, and

OMCServer

NMS

NE

MMLcommand

Statusmonitoring port

Alarm reportport

Port of performancedata report

Man-machinecommand port

MML interfacecommand

Server application process



software level information. U31(CN) provides inventory information to NMS fined interface via north interface in a standard file formats such as XML/CSV format. File interface also can be used for inventory information transmission.

8.5 DB Interface U31(CN) DB interface is the interface of middle database, which acts as the medium to establish the data connection channel between U31(CN) system and NMS.

Middle DB has two parts: DB management function and DB. DB management function is in charge of:

l Read the data (performance data, configuration data) in OMM system in fixed time, and save to local database according to some filtering rule.

l Manage the local DB.

DB is used to save the filtered data. The interface of DB is provided for upper NMS system for DB access.

Figure 8-4 Medium DB interface Function

9 Reliability

9.1 System Reliability Considering the disaster recovery function of the system, to prevent the data from being lost due to accident, U31(CN) can back up and recover all the performance



data, alarm data, configuration data, user self-defined data according to the definition of users, ensuring the highest security of the system data.

9.1.1 Data Security

9.1.1.1 Backup Mechanism

U31(CN) supports the following backup operations:

For U31(CN) software, it can be completely backed up, or just backup some pivotal configuration files, such as INI file.

For the configuration network resource data, the backup is done to different modules, such as configuration management data, alarm management data, performance statistic data.

For all the data, such as statistic data, alarm data, log, etc, they can be exported or imported.

For the log files, they can be deleted automatically and periodically after backup, in order to release the system space.

All the above backup operation, the system supports the following methods:

Manually or automatically, for the latter method, the backup period, content can be configured.

Complete backup and incremental backup are supported.

When export or backup the data, the system will prompt the operator if need to delete the original data.

9.1.1.2 Recovery Mechanism

Corresponding to the backup mechanism, U31(CN) can recover the data backed up to the NM system. The recovering process can recover all the backup data, or recover part of the data of the switching office. The recovery mechanism can be combined with the backup mechanism to completely copy the data of some offices into a new switching office. This function is also used in the deployment and maintenance of the switching office.

9.1.2 System Security

NetNumen system takes much consideration on the security, provides a full-scale solution to protect the system against attacking and unlawful accessing.



9.1.2.1 System Authentication & Authorization

l Access authentication for U31(CN) client access: password, numeric certificate, radius, etc.

l For password authentication, the storage and transmission of the password is encrypted, and it is displayed by cryptograph.

l Support the access restriction for the IP address of U31(CN) client, thus to prevent the accessing by unlawful client.

l Provide encryption and authentication for the interface between NMS and U31(CN), to prevent the accessing of unlawful NMS.

l Provide perfect management mechanism and support the dividable permission and dividable domain management function. All the permission is divided into multi levels, the operator can only do the operation under his permission, thus to prevent operating mistakes.

9.1.2.2 Accounts Management

l NETNUMEN U31(CN) supports the management of user valid period; the following parameters can be configured: the login time duration, useful-life of accounts and password, the prompt in advance is also supported.

l NETNUMEN U31(CN) supports simple password detection, such as: empty, all digits, all letters; accounts name cannot be the same as the telephone number, cannot be the repetition of accounts name and telephone, cannot be the backformation of accounts name and telephone number; the max repeated time of one character can be configured (2-10); when the password is expired, it must be modified forcibly, and cannot be the same as the latest one or some.

l If the user fails to log in, the failed times is limited, and if the max times is up to, the user will be locked by the system, and this event will be reported to U31(CN) as an alarm. The user just can be unlocked by the administrator or the limited time duration is expired.

l Support account storage of Radius format, management permission through Radius/LDAP, and can support authentication through Radius/LDAP API.

9.1.2.3 System Audit

NETNUMEN U31(CN) provides perfect log management and audit functions. The user operation, login and authentication, interface accessing, system running status and others are written into log files, and the content includes: user ID, login time, logout time, date and time of important operation, operation content and result;



friendly audit interface is offered and query can be done under different conditions.

9.1.2.4 Network Transmission

l Separate Multi-IP network segment are designed, the IP segment within the equipment is individual, it is divided with U31(CN) and this can guarantee the safety of NE.

l NetNumen U31(CN) supports SSH, SFTP and other third party software, Telnet/FTP is seldom used; SSL VPN, IPSec VPN are also supported, all of these can guarantee the safety of transmission.

l When NetNumen U31(CN) is connected with external network, firewall will be installed, in order to prevent the virus and Junk mails.

9.1.2.5 System Safety

l Screen lock function is supported to prevent the operating of unlawful users.

l NetNumen U31(CN) adopts high-performance server and OS, such as SUN Solaris.

l If users login and do some operation, it will be reported to U31(CN), so the operation status can be known.

l Monitor operations of all users, and generates maintenance reports. The user ‘admin’ has the right to kick out any user.

l NetNumen U31(CN) provides perfect log management and audit function. The user operation, login and authentication, interface accessing, system running status and others are written into log files, and the content includes: user ID, login time, logout time, date and time of important operation, operation content and result; friendly audit interface is offered and query can be done under different conditions.

If the OS is windows, the following protections are provided:

l Install anti-virus software on U31(CN) server, such as NORTON Antivirus Corporation Edition and McAfee Antivirus.

l Close some unsafe communication ports of U31(CN) server.

In Windows 2000 system, TCP/IP is normally used. By default, there isn’t any restriction for the communication ports, some of which is special for certain services, such as port 25 is used for SMTP (Simple Mail Transfer Protocol) , because these ports are known as the special ports, which can be easily attacked. Therefore, if these services are not needed, the corresponding ports should be closed.



l Close irrespective sharing directory

In Windows 2000 system, there are some default sharing directory and files, there is not any safeguard for them and they may be attacked. Therefore, the sharing directory of U31(CN) should be closed.

l Configure the system service

Many services are default startup items in Windows 2000 system, but some of there services are not very safe, such as Telnet. Therefore, these services should be forbidden, and for others, which are not so unsafe, the startup type should be configured.

l Close IIS service

IIS (Internet Information Server) service has the default configuration; there are some safety leaks, so it should be closed.

l System accounts configuration

This can prevent the operation by the attacker if the accounts or the password is interpreted by the attacker.

l Security configuration of database

For the database management software, there are some default parameters or configurations that may be attacked, this will damage the database, causing the important data to be lost or be decrypted and the database may even be broken forever. Through the configuration of the management parameters, the system will be safer.

9.2 Hardware Reliability l Di-hosts redundancy design with local and remote modes

U31(CN) system server can employ the physical configuration of dual server + shared disk array, as in the following figure. One server works as active server, the other works as backup server. In normal running, the system is running in the server, and the backup server does not bear any system load. While the active server fails, it is automatically switched to the backup server.



Figure 9-1 System Redundancy based on Disk Array of Local Mode

l RAID hard disks for standby including OS backup and U31(CN) backup

Remote redundancy solution includes 1+1, 2+2 and others. The following figure shows 2+2 solutions.

Node B has the same configuration with Node A. The data on disk array on the two nodes keeps synchronization.

Figure 9-2 System Redundancy based on Disk Array of Remote Mode



l Network disaster recovery backup

Dual Ethernet is used for links among the NEs and U31(CN) Server for mutual backup. The system uses two 3-layer switches and has a metric with two sets of unequal routes. Usually data flows go through the small link of the metric. When one link fails, data flows go through the other link automatically. The OSPF is used as the routing protocol. It can automatically calculate the metric. It takes network congestion as a metric. When one route is congested, the other route is used.

9.3 Software Reliability The various software security settings of U31(CN) system are:

l Link detecting mechanism. There is heartbeat-detecting mechanism between the client and server, between the server and NE, between the upper level NM interface and upper level NM, detecting the communication of each link in a fixed time. Alarm information will occur if the NE and server link are blocked.

l Connection server at the client. In the interaction between the server and the foreground, there is version-detecting mechanism to check whether the software versions of them are consistent. The software version which is not consistent will not be normally connected.



While the service of the system gets abnormal, and the process of the server gets abnormal, the system will record the failure information in the system log, resume the service automatically or generate alarm information. To prevent data loss due to unpredictable problems like system abnormality, network failure and natural disasters and human accidents, the following backup solutions are required:

l Remote data backup

If one database backup server is used in an area, the solution is to be determined by the actual situation. If the network condition is favorable and fibers are used for interconnection, then Managed Snapshot Services (MSS) can be used to provide snapshot for database running in real time. If the network condition is below the standard, daily FTP mode can be used to download database backup files.

9.4 Principle for Network Bandwidth The bandwidth requirement in U31(CN) system is include the following parts:

l Bandwidth between U31(CN) Server and NE

l Bandwidth between U31(CN) Server and Client

l Bandwidth between U31(CN) Server and NMS

Normally Client and U31(CN) Server are located in the same site, so they are in the same LAN and bandwidth between them can be ignored. However, when the LMT is put in the remote site, the bandwidth should be considered.

U31(CN) will realize the NE integrated management function, so it is based on different LANs between U31(CN) Server and NEs. The bandwidth between them should be considered.

Normally, it is based on different LANs between U31(CN) Server and NMS, so the bandwidth between them should be considered.

9.4.1 Bandwidth Calculation between U31(CN) Server and NMS

The message between U31(CN) Serve and NMS is mainly include alarm data, performance data and configuration operation (query, modify, delete and data report).

Normally the size of an alarm is 2K bytes. U31(CN) Serve will not report notification to NMS, only report alarm, and almost 0.05 pieces alarm per second for one NE, so the bandwidth requirement of alarm from U31(CN) Serve to NMS is 0.05*2048*8/1024=0.8 kpbs.



Normally the configuration operation of NMS is seldom. The operation includes configuration query or data synchronization. Supposing the uplink data is 2K for every operation from NMS to NE and 3 times per minute for the operation, the bandwidth required is 2*3*8/60=0.8 kbps.

The statistic granularity of the performance job setting by the NMS is normally less 15 minutes, so U31(CN) Serve will report statistic data to NMS every 15 minutes at most. The data will be transferred to NMS by FTP file. Supposing every time the file is 60K bytes, the bandwidth required is 60*8/60=8 kbps.

Therefore, the bandwidth required between U31(CN) and NMS is (when all the NE is in the normal state.)

2*(0.8*Nn+0.8*Nn+8*Nn)=19.2*Nn Kbps.

Here, Nn is the number of the equivalent NE that is managed by U31(CN).

9.4.2 Bandwidth Calculation between U31(CN) Server and Client

The bandwidth between U31(CN) Server and Client is

=2*(2*1024*0.05*Nn+1*1024*0.5*Nn+2*1024*3/60+1024*20*50*1/100+10*1024/8+5*1024/8) Byte/s

= 2*(0.6*Nn+12)*8 Kbps= 9.6*Nn+192 Kbps

Here, Nn is the number of NE that managed by U31(CN).

9.4.3 Bandwidth Calculation between U31(CN) Server and NE

The message between U31(CN) and NE is mainly including system communication data, alarm data report, performance data report and configuration operation (query, modify, delete and synchronization), the bandwidth between U31(CN) and NE is different from different NE type. Detailed information is listed as following table:

Table 9-1 Required Bandwidth between U31(CN) Server and NE

NE type bandwidth MSC Server/MSCe 256K MGW 32K SGSN 96K CG 16K HLR(FE) 128K HLR(BE) 64K MME 16K



NE type bandwidth GGSN/SAE-GW 64K CSCF 256K PSS 32K MGCF 256K IM-MGW 32K AGCF 32K HSS 64K

10 Technical Indices This chapter provides the technical indices of U31(CN) system, which can be used as the reference of the project.

10.1 System Performance Indices

Table 10-1 System Performance Indices

Capability Index

Maximum managed NEs 300 standard NEs Alarm Processing Capability

Normal:30/s; Peak: 200/s; The alarm can keep, without losing at least for 15 minutes

Performance counter warehousing capability

247500/s

Maximum number of simultaneous online client

100

Maximum number of simultaneous operating client

50

System Index

System software installation time

<30 minutes

System software upgrade time

<30 minutes

Rollback time when fail to upgrade

<4 hours

Patch upgrade time <30 minutes

Start up Time

Start up time of system client

<7s

User login delay <5s Delay of open the client view

<3s



Server hot start up time <5 minutes

Operation Performance

Current alarm query delay <2s History alarm query delay <5s Alarm report delay <2s Alarm report delay through northbound interface

<10s

Performance data query delay

<10s

Data batch export delay <10s The minimum granularity of performance data collection

15 minutes

Log query delay <2s

Storage Capacity (depend on the hard disk

capacity)

Maximum number of alarm 10 million History alarm storage time 3 month Maximum number of performance counter

140 million

Original performance data storage time

1 month (granularity: 15 minutes); 3 months (granularity: 1 hour)

Report performance data storage time

13 months

Log storage time 3 months

System Availability MTBF 6480 hours MTTR 30 minutes Availability 99.992%



AppA Appendixes

A.1 ZTE-Joined Standard Organizations

ZTE joins the making of WCDMA standards inside China and all over the world. The major standard organizations are as follows:

App Table A-1 ZTE-Joined Standard Organizations

Standardization Organization Remarks Chinese Communication Standards Association Full Member Open Base Station Architecture Initiative One of 5 organizers 3rd Generation Partnership Project Independent Member 3rd Generation Partnership Project 2 Independent Member Asia Info-communication Council Full Member CDMA Development Group Vander Member Communication Power Supply Standard Research Team Full Member DSL Forum Auditing Member IPV6 Forum Member IP and Multimedia Technology Research Team Full Member International Telecommunication Union Sector Member Internet Society of China Vice Director of Council Metro Ethernet Forum Principle Member Mobile Wireless Internet Forum Auditing Member MPEG4 Industry Forum Full Member

Multi Protocol Label Switching Forum Large Company Principle Member

Multi-service Switch Forum Principle Member Network and Switch Standard Research Team Full Member Network Management Standard Research Team Full Member Network Processing Forum Member Resilient Packet Ring Alliance Participate Member TD-SCDMA Technology Forum Council Member Tele Management Forum Affiliate Member The Optical Internetworking Form Auditing Member Transmission Network and Access Network Standard Research Team Full Member

Wireless Communication Standard Research Team Full Member



A.2 Acronyms and Abbreviations

The acronyms and abbreviations used in this document are shown in the following table:

App Table A-2 Acronyms and Abbreviations

Abbreviations Full Name ATM Asynchronous Transfer Mode CG Charge Gateway CN Core Network CS Circuit Service DSL Digital Subscriber Line GGSN Gateway GPRS Support Node GSM Global System for Mobile communications HLR Home Location Register MGW Media Gate Way MSC Mobile Switching Center MTBF Mean Time Between Failures NM Network Management U31(CN) Operation and Maintenance Center PHS Personal Handyphone System PLMN Public Land Mobile Network PS Packet Service PSTN Public Switched Telephone Network QoS Quality of Service SGSN Serving GPRS Support Node SMS Short Message Service SMSC Short Message Service Center SS7 Signaling System Number 7 TCP/IP Transmission Control Protocol/Internet Protocol WCDMA Wideband Code Division Multiple Access WCN WCDMA Core Network uMAC Universal Mobility Access Controller xGW Extended Gateway

annex_06_03_zte netnumen u31-cn product description

Documents

cn product line

system architecture

u31cn system principle

open system structure

zte corporation

networking architecture

proprietary information

system remote upgrading