M2000 System Description

Chapter 1 System Introduction 1-1......................................................................

1.1 Overview of M2000 1-1................................................................................1.1.1 M2000 Management Function 1-1.......................................................1.1.2 M2000 Management Object 1-1...........................................................

1.2 Position of M2000 in Network 1-2.................................................................

Chapter 2 System Characteristics 2-1.................................................................

2.1 Overview of M2000 System Characteristics 2-1...........................................2.2 Multi-platform Component-based Architecture 2-1.......................................2.3 Itf-N Network Management Interfaces 2-1....................................................2.4 Software Management 2-1...........................................................................2.5 Custom Reports in the WEB Mode 2-1........................................................2.6 Time Synchronization 2-2.............................................................................2.7 Client Software Automatic Upgrade 2-2.......................................................2.8 Log Management 2-2...................................................................................2.9 IP Device Management 2-2..........................................................................

Chapter 3 System Architecture 3-1......................................................................

3.1 Overview of M2000 System Architecture 3-1...............................................3.2 Physical Architecture 3-1..............................................................................

3.2.1 Overview of Physical Architecture 3-1.................................................3.2.2 Typical Configuration of M2000 Server 3-2..........................................3.2.3 Typical Configuration of M2000 Client 3-2...........................................

3.3 Software Architecture 3-3.............................................................................3.3.1 Overview of Software Architecture 3-3.................................................3.3.2 M2000 Server Software 3-4.................................................................3.3.3 M2000 Client Software 3-4...................................................................3.3.4 Interfaces 3-4.......................................................................................

Chapter 4 Services and Functions 4-1.................................................................

4.1 Overview of M2000 Services and Functions 4-1..........................................4.2 Centralized Topology Management 4-1.......................................................

4.2.1 Overview of Topology Management 4-1..............................................4.2.2 Topological Objects Management 4-1.................................................4.2.3 Topological Navigation Tree 4-2..........................................................4.2.4 Topological Map 4-2.............................................................................

4.3 Centralized Configuration Management 4-2.................................................4.3.1 Overview of Centralized Configuration Management 4-2....................4.3.2 NE Configuration 4-3............................................................................4.3.3 Configuration Data Query 4-3..............................................................4.3.4 Report on NEs and Links 4-3...............................................................

4.3.5 Configuration Data Backup and Restoration 4-3..................................4.4 Centralized Fault Management 4-3..............................................................

4.4.1 Overview of Centralized Fault Management 4-3..................................4.4.2 Real-Time Alarm Browse 4-4...............................................................4.4.3 Alarm Statistic and Query 4-4..............................................................4.4.4 Alarm Correlation Analysis 4-4.............................................................4.4.5 Alarm Acknowledgement and Un-acknowledgement 4-4....................4.4.6 Alarm Database Auto Displacement 4-4..............................................4.4.7 Redefinition of Alarm Severity Levels 4-4............................................4.4.8 Alarm Handling Experience Management 4-5.....................................4.4.9 Remote Notification of Alarms 4-5.......................................................

4.5 Centralized Performance Management 4-5..................................................4.5.1 Overview of Centralized Performance Management 4-5.....................4.5.2 Performance Job Management 4-5......................................................4.5.3 Performance Data Management 4-6....................................................4.5.4 Performance Alarm 4-7........................................................................4.5.5 Customized Counters 4-7....................................................................4.5.6 Template Management 4-7..................................................................4.5.7 Customizable Performance Report System 4-7...................................

4.6 Centralized Software Management 4-8........................................................4.6.1 Overview of Software Management 4-8...............................................4.6.2 NE Software Version and License Management 4-8...........................4.6.3 NE Data Backup 4-8............................................................................4.6.4 File Transfer 4-8...................................................................................

4.7 Centralized Security Management 4-8.........................................................4.7.1 Overview of Security Management 4-8................................................4.7.2 User Account and Group Management 4-8.........................................4.7.3 Terminal Management 4-9...................................................................4.7.4 Log Management 4-9...........................................................................

4.8 System Management 4-9.............................................................................4.8.1 Overview of System Management 4-9.................................................4.8.2 Remote Maintenance 4-10.....................................................................4.8.3 Online Help 4-10....................................................................................4.8.4 System State Monitor 4-10.....................................................................4.8.5 System Data Backup and Restoration 4-10...........................................4.8.6 System Un-installation 4-10...................................................................

4.9 Itf-N Network Management Interface 4-10.....................................................4.10 Time Synchronization 4-11...........................................................................

Chapter 5 System Reliability 5-1..........................................................................

5.1 Overview of M2000 System Reliability 5-1...................................................

5.2 System Reliability 5-1...................................................................................5.2.1 Data Security 5-1.................................................................................5.2.2 Operation Security 5-2.........................................................................

5.3 Hardware Reliability 5-2...............................................................................5.4 Software Reliability 5-2.................................................................................

Chapter 6 System Specifications 6-1...................................................................

6.1 Overview of M2000 System Specifications 6-1............................................6.2 Performance Specifications 6-1....................................................................

6.2.1 Overview of Performance Specifications 6-1.......................................6.2.2 System Capacity 6-1............................................................................6.2.3 Performance Data Storage Capacity 6-2.............................................6.2.4 Alarm Data Storage Capacity 6-2........................................................6.2.5 Alarm Response 6-3............................................................................

6.3 Environment Parameters 6-3........................................................................6.4 Reliability Specifications 6-4.........................................................................

Appendix Acronyms and Abbreviations F-1.......................................................

Index .................................................................................................................

HUAWEI

iManager M2000 Mobile Element Management SystemSystem Description

V200R002

iManager M2000 Mobile Element Management System

System Description

Manual Version T2-030206-20041010-C-2.20

Product Version V200R002

BOM 31026306

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

Website: http://www.huawei.com

Email: [email protected]

Copyright © 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co., Ltd.

All other trademarks mentioned in this manual are the property of their respective holders.

Notice

The information in this manual is subject to change without notice. Every effort has been made in the preparation of this manual to ensure accuracy of the contents, but all statements, information, and recommendations in this manual do not constitute the warranty of any kind, express or implied.

Summary of Updates

This section provides the update history of this manual and introduces the contents of subsequent updates.

Update History

This manual is updated for a major product version to maintain consistency with system hardware or software versions and to incorporate customer suggestions.

Manual Version Notes

T2-030235-20040225-C-2.10 Initial field trial release

T2-030235-20040528-C-2.11 Initial commercial release

T2-030206-20041010-C-2.20 Improved commercial release

Updates of Contents

Updates between manual versions are cumulative. Therefore, the latest manual version contains all updates made to previous versions.

Updates Made between Versions 2.20 and 2.11

The whole manul is optimized in structure and language.

Chapter 1 System Introduction

IP device, PCU, BSC and BTS are added to M2000 management object list.

Chapter 1 System Characteristics

Log management and IP device management features are added to M2000 characteristics list.

Chapter 6 System Specifications

The data of M2000 Reliability specifications are updated.

Updates Made between Versions 2.11 and 2.10

The whole manul is optimized in structure and language.


The data of M2000 Server power consumption are updated.

About This Manual

Release Notes

This manual applies to iManager M2000 Mobile Element Management System V200R002.

Organization

The manual introduces the system characteristics, architecture, services, functions and technical specifications.

There are seven chapters in the manual.

Chapter 1 System Introduction provides an overall introduction to M2000.

Chapter 2 System Characteristics introduces the main features of M2000.

Chapter 3 System Architecture introduces typical configuration and software architecture of M2000.

Chapter 4 Services and Functions introduces topology management, centralized configuration management, centralized fault management, centralized performance management, security management, log management.

Chapter 5 System Reliability introduces the reliability design, including the system reliability, hardware reliability and software reliability.

Chapter 6 System Specifications introduces the system performance indices, environment parameters and reliability indices.

Appendix Acronyms and Abbreviations

Intended Audience

The manual is intended for the following readers:

System engineer of mobile network Marketing staff Network maintenance personnel

Conventions

The manual uses the following conventions:

I. GeneralF conventions

Convention Description

Arial Normal paragraphs are in Arial.

Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.

Boldface Headings are in Boldface.

Courier New Terminal Display is in Courier New.

II. Symbols

Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. They are defined as follows:

Caution, Warning, Danger: Means reader be extremely careful during the

operation.

Note, Comment, Tip, Knowhow, Thought: Means a complementary description.

System Description iManager M2000 Mobile Element Management System Table of Contents

i

Table of Contents

Chapter 1 System Introduction .................................................................................................... 1-1 1.1 Overview of M2000............................................................................................................ 1-1

1.1.1 M2000 Management Function ................................................................................ 1-1 1.1.2 M2000 Management Object.................................................................................... 1-1

1.2 Position of M2000 in Network ............................................................................................ 1-2

Chapter 2 System Characteristics ............................................................................................... 2-1 2.1 Overview of M2000 System Characteristics...................................................................... 2-1 2.2 Multi-platform Component-based Architecture .................................................................. 2-1 2.3 Itf-N Network Management Interfaces............................................................................... 2-1 2.4 Software Management....................................................................................................... 2-1 2.5 Custom Reports in the WEB Mode.................................................................................... 2-1 2.6 Time Synchronization ........................................................................................................ 2-2 2.7 Client Software Automatic Upgrade................................................................................... 2-2 2.8 Log Management............................................................................................................... 2-2 2.9 IP Device Management ..................................................................................................... 2-2

Chapter 3 System Architecture.................................................................................................... 3-1 3.1 Overview of M2000 System Architecture .......................................................................... 3-1 3.2 Physical Architecture ......................................................................................................... 3-1

3.2.1 Overview of Physical Architecture........................................................................... 3-1 3.2.2 Typical Configuration of M2000 Server................................................................... 3-2 3.2.3 Typical Configuration of M2000 Client .................................................................... 3-2

3.3 Software Architecture ........................................................................................................ 3-3 3.3.1 Overview of Software Architecture.......................................................................... 3-3 3.3.2 M2000 Server Software .......................................................................................... 3-4 3.3.3 M2000 Client Software............................................................................................ 3-4 3.3.4 Interfaces................................................................................................................. 3-4

Chapter 4 Services and Functions .............................................................................................. 4-1 4.1 Overview of M2000 Services and Functions ..................................................................... 4-1 4.2 Centralized Topology Management................................................................................... 4-1

4.2.1 Overview of Topology Management ....................................................................... 4-1 4.2.2 Topological Objects Management........................................................................... 4-1 4.2.3 Topological Navigation Tree ................................................................................... 4-2 4.2.4 Topological Map...................................................................................................... 4-2

4.3 Centralized Configuration Management ............................................................................ 4-2 4.3.1 Overview of Centralized Configuration Management ............................................. 4-2 4.3.2 NE Configuration..................................................................................................... 4-3


ii

4.3.3 Configuration Data Query ....................................................................................... 4-3 4.3.4 Report on NEs and Links ........................................................................................ 4-3 4.3.5 Configuration Data Backup and Restoration........................................................... 4-3

4.4 Centralized Fault Management.......................................................................................... 4-3 4.4.1 Overview of Centralized Fault Management........................................................... 4-3 4.4.2 Real-Time Alarm Browse ........................................................................................ 4-4 4.4.3 Alarm Statistic and Query ....................................................................................... 4-4 4.4.4 Alarm Correlation Analysis...................................................................................... 4-4 4.4.5 Alarm Acknowledgement and Un-acknowledgement ............................................. 4-4 4.4.6 Alarm Database Auto Displacement ....................................................................... 4-4 4.4.7 Redefinition of Alarm Severity Levels ..................................................................... 4-4 4.4.8 Alarm Handling Experience Management .............................................................. 4-5 4.4.9 Remote Notification of Alarms................................................................................. 4-5

4.5 Centralized Performance Management............................................................................. 4-5 4.5.1 Overview of Centralized Performance Management .............................................. 4-5 4.5.2 Performance Job Management............................................................................... 4-5 4.5.3 Performance Data Management ............................................................................. 4-6 4.5.4 Performance Alarm ................................................................................................. 4-7 4.5.5 Customized Counters.............................................................................................. 4-7 4.5.6 Template Management ........................................................................................... 4-7 4.5.7 Customizable Performance Report System............................................................ 4-7

4.6 Centralized Software Management ................................................................................... 4-8 4.6.1 Overview of Software Management........................................................................ 4-8 4.6.2 NE Software Version and License Management .................................................... 4-8 4.6.3 NE Data Backup...................................................................................................... 4-8 4.6.4 File Transfer ............................................................................................................ 4-8

4.7 Centralized Security Management..................................................................................... 4-8 4.7.1 Overview of Security Management ......................................................................... 4-8 4.7.2 User Account and Group Management .................................................................. 4-8 4.7.3 Terminal Management ............................................................................................ 4-9 4.7.4 Log Management .................................................................................................... 4-9

4.8 System Management......................................................................................................... 4-9 4.8.1 Overview of System Management .......................................................................... 4-9 4.8.2 Remote Maintenance ............................................................................................ 4-10 4.8.3 Online Help............................................................................................................ 4-10 4.8.4 System State Monitor............................................................................................ 4-10 4.8.5 System Data Backup and Restoration .................................................................. 4-10 4.8.6 System Un-installation .......................................................................................... 4-10

4.9 Itf-N Network Management Interface............................................................................... 4-10 4.10 Time Synchronization .................................................................................................... 4-11

Chapter 5 System Reliability ........................................................................................................ 5-1 5.1 Overview of M2000 System Reliability .............................................................................. 5-1


iii

5.2 System Reliability............................................................................................................... 5-1 5.2.1 Data Security........................................................................................................... 5-1 5.2.2 Operation Security .................................................................................................. 5-2

5.3 Hardware Reliability........................................................................................................... 5-2 5.4 Software Reliability ............................................................................................................ 5-2

Chapter 6 System Specifications................................................................................................. 6-1 6.1 Overview of M2000 System Specifications ....................................................................... 6-1 6.2 Performance Specifications ............................................................................................... 6-1

6.2.1 Overview of Performance Specifications ................................................................ 6-1 6.2.2 System Capacity ..................................................................................................... 6-1 6.2.3 Performance Data Storage Capacity ...................................................................... 6-2 6.2.4 Alarm Data Storage Capacity.................................................................................. 6-2 6.2.5 Alarm Response...................................................................................................... 6-3

6.3 Environment Parameters ................................................................................................... 6-3 6.4 Reliability Specifications .................................................................................................... 6-4

Appendix Acronyms and Abbreviations.................................................................................... F-1

Index ................................................................................................................................................ i-1

System Description iManager M2000 Mobile Element Management System Chapter 1 System Introduction

1-1

Chapter 1 System Introduction

1.1 Overview of M2000

iManager M2000 Mobile Element Management System (M2000 for short) serves to manage and maintain Huawei mobile network products.

1.1.1 M2000 Management Function

The management functions of M2000 include the following aspects:

Centralized fault management Centralized performance management Centralized configuration management Centralized software management Centralized topology management Centralized security management System management

1.1.2 M2000 Management Object

Table 1-1 shows Huawei mobile network products that M2000 can access to.

Table 1-1 The network products that M2000 can access to

NE Type Description Model

NodeB WCDMA BTS BTS3812/BTS3806A/BTS3806/BTS3802C

RNC Radio Network Controller BSC6800

SGSN Serving GPRS support node

SGSN9810

GGSN Gateway GPRS support node

GGSN9811

MSC Server Mobile switching center server

MSOFTX3000

MSC Server Mobile switching center MSC9800

MGW Media gateway UMG8900

HLR Home location register HLR9820/HLR36

CG Charging Gateway CG9812

System Description iManager M2000 Mobile Element Management System Chapter 1 System Introduction

1-2

NE Type Description Model

PCU Packet Control Unit /

BSC Base Station Controller /

BTS Base Transceiver Station BTS20/BTS30/BTS312/BTS3001C/BTS3002C/BTS3012A

M2000 also can manage Huawei IP device, such as LAN Switch, Router.

1.2 Position of M2000 in Network

M2000 is located at the element management (EM) layer in the telecommunication management network (TMN) model. It provides interfaces in compliance with 3GPP network management standards to network management system (NMS). Figure 1-1 shows a M2000 networking application.

Figure 1-1 M2000 networking application

System Description iManager M2000 Mobile Element Management System Chapter 2 System Characteristics

2-1

Chapter 2 System Characteristics

2.1 Overview of M2000 System Characteristics

M2000 has the following characteristics:

Multi-platform component-based architecture Itf-N network management interfaces Software management Custom reports in the WEB mode Time synchronization Client software automatic upgrade Log management IP device management

2.2 Multi-platform Component-based Architecture

M2000 supports several kinds of hardware platforms, including Sun and Personal Computer (PC) Server, and Sybase database. Adopting the common object request broker architecture (CORBA) technology enables M2000 to expand capacity smoothly to meet network management requirements.

2.3 Itf-N Network Management Interfaces

M2000 supports 3GPP R99/R4 IRP CORBA solution sets. It provides customized Itf-N interfaces that facilitate the NMS to manage itself and the EMSs of other vendors.

M2000 provides FTP-based and Telnet-based interfaces.

2.4 Software Management

M2000 can upload or download NE-related software, patch, license, data and other files from or to managed network elements (NE). It also manages software versions, including querying, activating and falling back the software.

2.5 Custom Reports in the WEB Mode

You can customize templates and contents of performance reports, print, query and perform statistics to reports generated.

System Description iManager M2000 Mobile Element Management System Chapter 2 System Characteristics

2-2

2.6 Time Synchronization

M2000 provides network time protocol (NTP) services to ensure that NEs and M2000 can synchronize in time.

2.7 Client Software Automatic Upgrade

M2000 supports automatic upgrade of the Client. When the version of the Client does not match that of the Server, the Client obtains the matched Client version from the Server and upgrades itself automatically.

2.8 Log Management

There are three types of logs: operation logs, system logs and debugging logs. Operation logs record all user operations on both the M2000 and on NEs.

Log management includes log query, log statistics analysis and log displacement.

2.9 IP Device Management

IP device of mobile network can be as a specific NE managed by M2000. You can query configuration data and alarms of IP device.

M2000 only supports to manage Huawei IP device now.

System Description iManager M2000 Mobile Element Management System Chapter 3 System Architecture

3-1

Chapter 3 System Architecture

3.1 Overview of M2000 System Architecture

The M2000 system architecture consists of two aspects:

Physical architecture Software architecture

3.2 Physical Architecture

3.2.1 Overview of Physical Architecture

A typical M2000 system includes a Server, several Clients, Alarm Boxes, and some sets of networking equipment. You can perform remote operation and maintenance through public switched telephone network (PSTN) using a dial-up Server. Figure 3-1 illustrates the typical configuration of M2000.

PSTN

Alarm Box M2000 Client

M2000 Client

M2000 Server

Dial-up Server

Figure 3-1 Typical M2000 configuration

Note:

The Dial-up Server is not as part of the standard configuration.


3-2

3.2.2 Typical Configuration of M2000 Server

According to the total number of NEs managed by M2000, many types of equipment can serve as M2000 Server. The typical equipment is Sun Netra 20, Sun Fire V880 or Sun Fire 4800.

Table 3-1 lists the configuration of M2000 Server.

Table 3-1 Configuration of M2000 Server

Equipment

Type

Item

Sun Netra 20 Sun Fire V880 Sun Fire 4800

CPU 2 CPU/1.2 GHz 4 CPU/1.2 GHz 4 CPU/1.2 GHz

Memory 4 GB 8 GB 16 GB

Hard disk 2 x 36 GB or 2 x 73 GB 2 x 73 GB 2 x 36 GB

Disk array None 3310 (8 x 36 GB) 2 x T3 (9 x 36 GB)

Accessories DVD/Network Adapter/Tape drive DDS4/English Documentation

DVD/Network Adapter/Tape drive DDS4/English Documentation

DVD/Network Adapter/Tape drive DDS4/English Documentation

Operating system Solaris 8/English Documentation

Solaris 8/English Documentation

Solaris 8/English Documentation

Database Sybase 12.0/English Documentation

Sybase 12.0/English Documentation

Sybase 12.0/English Documentation

Application software M2000 Server application software

M2000 Server application software

M2000 Server application software

3.2.3 Typical Configuration of M2000 Client

The M2000 Client can run on PCs using Win2000. Table 3-2 lists the basic configuration of the PC.

Table 3-2 Configuration of M2000 Client

Item configuration

CPU P4/2.4 GHz

Memory 256 MB

Hard disk 40 GB


3-3

Item configuration

Accessories CDROM/Floppy Driver/Network Adapter/Sound Card/17” Display

Operating system Windows 2000 professional

Application software M2000 Client application software

3.3 Software Architecture

3.3.1 Overview of Software Architecture

M2000 comprises three sub-systems, M2000 Server software, M2000 Client software and report system (optional). M2000 Client and Server software communicate with each other through a CORBA software bus. The report system provides an optional function, customizable performance reports. Figure 3-2 shows the software modules of M2000.

Figure 3-2 Software modules of M2000


3-4

3.3.2 M2000 Server Software

M2000 Server software consists of eight software modules, which are:

Topology management module Configuration management module Performance management module Security management module Fault management module Software management module Itf-N interface module

It provides an interface to the NMS through CORBA IDL in accordance with a number of 3GPP network management standards.

Mediation module

It is an adapter to NE interfaces. It is responsible for dealing with interface differences between M2000 and different NEs and IP devices.

All inter-M2000 modules communicate with each other through a CORBA software bus and communicate with lower-level NEs (e.g. SGSN, CG) via proprietary MML commands over TCP/IP links. M2000 communicate with IP devices via SNMP data over TCP/IP links.

3.3.3 M2000 Client Software

The M2000 Client software provides graphic user interface (GUI) for users. Through GUI, you can manage and maintain all the NEs, including:

Observing operation status Getting alarm information in real time Creating performance jobs and querying performance job results Configuring data Managing software

3.3.4 Interfaces

M2000 resides between the NMS and NE and provides interfaces to both sides.

M2000 provides 3GPP-compliant CORBA interfaces to make itself easily managed by a NMS.

M2000 manages mobile network elements (NEs) through man machine language (MML) interfaces and IP devices through SNMP interfaces.

System Description iManager M2000 Mobile Element Management System Chapter 4 Services and Functions

4-1

Chapter 4 Services and Functions

4.1 Overview of M2000 Services and Functions

M2000 provides the following functions:

Centralized topology management Centralized configuration management Centralized fault management Centralized performance management Centralized software management Centralized security management System management Itf-N network management interface Time synchronization

4.2 Centralized Topology Management

4.2.1 Overview of Topology Management

M2000 provides topology management for all NEs in the entire network, including the following aspects:

Topological objects Topological navigation tree Topological map

4.2.2 Topological Objects Management

Topological object management includes the following aspects:

Topological object creation, modification and deletion NE status view Search for specified NE Bulk operations on NEs NE display filtering

I. Topological Object Creation, Modification and Deletion

You can create topological objects, which comprise NEs, virtual NEs and links, directly on a topology map, modify configured data of topological objects, drag or delete topological objects.


4-2

II. NE Status View

On the topology map, you can view status of all NEs managed by M2000, including normal status and faulty status (four severity levels) as well as communication status between NE and M2000, such as synchronization, disconnection and configuration.

III. Search for Specified NE

You can search a specified NE on the topological map by NE name, location (longitude and latitude), software version, equipment supplier or IP address. Both “precise” search and “fuzzy” search are supported.

IV. Bulk Operations on NEs

M2000 provides bulk operations on NEs, with which you can create, delete and synchronize multiple NEs at one time.

V. NE Display Filtering

The system displays or shields certain types of NEs as required.

4.2.3 Topological Navigation Tree

When the system is very large, there will be many topological objects. You can easily find these NEs through the topological navigation tree.

4.2.4 Topological Map

You can change background map and choose suitable locations for NEs as needed. The background map can be a vector map, which can locate NEs accurately.

You can display NEs on the map hierarchically using subnets.

You can activate NE LMTs from the NEs on the topology map.

4.3 Centralized Configuration Management

4.3.1 Overview of Centralized Configuration Management

M2000 provides centralized configuration management for all NEs in the entire network, including the following aspects:

NE configuration Configuration data query Report on NEs and links


4-3

Configuration data backup and restoration

4.3.2 NE Configuration

Through the MML interfaces of M2000, you can send one or more MML commands to NEs to configure them.

You can edit a MML command script file and execute the script file through MML interface of M2000.

4.3.3 Configuration Data Query

You can query NE configuration data as required. M2000 displays the query result in a report.

4.3.4 Report on NEs and Links

M2000 provides reports on the configuration data of NEs and links.

4.3.5 Configuration Data Backup and Restoration

M2000 supports configuration data backup. The storage media can be hard disks or tapes. It also supports configuration data restoration from backup data.

4.4 Centralized Fault Management

4.4.1 Overview of Centralized Fault Management

M2000 provides centralized fault management for all NEs in the entire network, including the following aspects:

Real-time alarm browse Alarm and statistic query Alarm correlation analysis Alarm acknowledgement Alarm database auto displacement Redefinition of alarm severity levels Alarm handling experience management Remote notification of alarms


4-4

4.4.2 Real-Time Alarm Browse

You can browse real-time alarms of all NEs and M2000 to find out severities and types.

M2000 highlights fault alarms unprocessed for a long time.

M2000 provides audible and visual alarms through the alarm window on M2000 Client or its alarm box.

4.4.3 Alarm Statistic and Query

You can query current alarms, event alarms and history alarms according to specified conditions. You can get statistic results.

4.4.4 Alarm Correlation Analysis

M2000 stores key information in the database and drops redundant information after performing correlation analysis on all received alarms. In this way, M2000 assists operators to locate faults quickly.

4.4.5 Alarm Acknowledgement and Un-acknowledgement

You may acknowledge alarms to identify themselves as taking corrective action. You can also un-acknowledge the alarms that you have acknowledged, meaning that the alarm has not been processed yet.

4.4.6 Alarm Database Auto Displacement

It includes two types of displacement: periodical displacement and displacement when the alarm database capacity exceeds the upper limit. The former includes setting of displacement cycle, displacement content and displacement format, while the latter includes setting of upper limit of the database capacity, displacement content and displacement format. The format of a displaced file can be TXT, XML or HTML.

4.4.7 Redefinition of Alarm Severity Levels

You can redefine alarm severity levels as needed.


4-5

4.4.8 Alarm Handling Experience Management

You can put the alarm handling experiences, such as fault location and handling suggestions, to the alarm knowledge database. You can also query the database for information you need according to the alarm Identity (ID) and knowledge content. This function is very helpful for troubleshooting.

4.4.9 Remote Notification of Alarms

As per the preset conditions, M2000 can forward alarm information by pager, E-mail or SMS. You can configure the conditions through M2000 Client.

4.5 Centralized Performance Management

4.5.1 Overview of Centralized Performance Management

Centralized performance management is to authenticate the network performance specifications, so as to provide references for network planning and maintenance.

Centralized performance management includes the following aspects:

Performance job management Performance data management Performance alarm Customized counters Template management Customized performance report system

4.5.2 Performance Job Management

Performance job management includes the following aspects:

Performance job creation Performance job modification Job-related information view Performance job backup and restoration Import and export of performance job

I. Performance Job Creation

You can create performance jobs on multiple NEs and set counters, collection cycles and result saving days.

NEs provide cache mechanism for performance job results to avoid loss of performance data when the network is busy or communications are interrupted.


4-6

II. Performance Job Modification

You can modify such job parameters as measurement object, measurement time segment and counters.

III. Job-related information View

You can view the basic information of a job and the detailed parameter information, and suspend, resume, modify, and delete jobs.

IV. Performance Job Backup and Restoration

M2000 supports backup/restoration of information and results of performance jobs.

V. Import and Export of Performance Job

You can export the information of performance job to a file or import the information from a file. The information includes job time, job objects and job counters. The file is in extensible markup language (XML) format.

4.5.3 Performance Data Management

Performance data management includes the following aspects:

Job result report Job result storage Job result query Job missing result query Statistic of job results Flexible report Job result subscription

I. Job Result Report

M2000 reports job results to multiple NMSs. It supports both active report and passive query.

II. Job Result Storage

M2000 can export performance job results to files in a specified format. The format can be TXT, hyper text markup language (HTML) or CSV.

III. Job Result Query

You can query, sort, display and print performance job results.


4-7

IV. Job Missing Result Query

You can query missing performance job results to ensure the result consistency between M2000 and NE.

V. Statistic of Job Results

You can perform statistics to job results according to location, office direction and trunk. M2000 can display statistic results in tables, line chart and bar chart.

VI. Flexible Report

M2000 provides some commonly used or standard report templates. You can also create report templates based on created jobs.

VII. Job Result Subscription

You can subscribe the results of jobs. After subscription, you can browse job results according to the measurement cycle.

4.5.4 Performance Alarm

You can set alarm thresholds for created jobs. M2000 generates the corresponding alarm when a result exceeds the relative threshold.

4.5.5 Customized Counters

You can combine existing performance counters to define new measurement counters. You can also share your customized counters with other users.

4.5.6 Template Management

You can define commonly used parameter templates such as time template, object template and counter template. You can also modify or delete the templates created.

4.5.7 Customizable Performance Report System

M2000 provides a customizable performance report system in Web style. You can select report formats and contents as required.


4-8

4.6 Centralized Software Management

4.6.1 Overview of Software Management

M2000 provides centralized management on software versions and data of all NEs in the entire network. Software management includes the following aspects:

NE software version and license management NE data backup File transfer

4.6.2 NE Software Version and License Management

M2000 stores different software version, license information and files of managed NEs. You can load and activate a version to single or multiple NEs through M2000.

4.6.3 NE Data Backup

M2000 backs up data of managed NEs, including configuration, performance, alarm and log data.

4.6.4 File Transfer

M2000 provides fast and convenient file transfer between M2000 Client and M2000 Server and between M2000 Server and NEs. You can transmit a batch of files from M2000 to multiple NEs or from multiple NEs to M2000 at a time.

4.7 Centralized Security Management

4.7.1 Overview of Security Management

Security management includes the following aspects:

User account and group management Terminal management Log management

4.7.2 User Account and Group Management

To log in to and use M2000, you must have a user account. M2000 user account information consists of four main components:

User name: A name that a user uses to log in to M2000.


4-9

Password: A secret combination of characters that a user must enter with a user name to gain access to M2000.

Login time: A time segment when a user can log in to M2000. User group: Each user account belongs to one or more user groups to have

specified operation and maintenance rights on NEs, or to have administration rights on M2000.

M2000 automatically creates the user account “admin” and the user group “Administrators” during installation of the system. The user “admin” belongs to “Administrators” and has all the administration, operation and maintenance rights.

4.7.3 Terminal Management

To avoid illegal login, the system will lock a terminal that has been idle for a certain period. The user also can lock the terminal manually.

To conduct operations, the user should log in to the system again.

4.7.4 Log Management

There are three types of logs, operation logs, system logs and debugging logs. Operation logs record all user operation events both in M2000 and in NEs. System logs record all system important events, such as network failures and attacks against the system, to facilitate troubleshooting and analysis of system status. Debugging logs help locate system problems.

Log management includes the following three aspects to operation logs:

Log query: You can set query conditions to view logs, print or save the query results as files.

Log statistics analysis: You can quickly find out system operation status using this function, for example, which period contains most of operations and what are the most commonly performed operations.

Log displacement: M2000 performs automatic log displacement when the capacity exceeds the limit. You can also manually displace logs.

4.8 System Management

4.8.1 Overview of System Management

System management includes the following aspects:

Remote maintenance Online Help System state monitoring


4-10

System data backup and restoration System un-installation

4.8.2 Remote Maintenance

M2000 supports TCP/IP. By means of dial-up server, M2000 supports dial-up access through PSTN.

M2000 monitors and records remote operations in real time.

4.8.3 Online Help

M2000 provides detailed and convenient help information of MML commands, alarms and performance counters of all the managed NEs and instructions on system operations and maintenance.

To invoke the online help, you can:

Select [Help/Topics] in the window titled with “iManager M2000 Mobile Element Management System”, or

Press <F1> when any M2000 window or dialog box is active, or Select [Start/Program/ iManager M2000 Client/ M2000 Client Help].

4.8.4 System State Monitor

You can view the status of each service and utilization of resources, such as CPU, memory, hard disk, database.

4.8.5 System Data Backup and Restoration

The system data, including security data, log date, NE alarm data and performance data, can be backed up periodically or manually, and the backup data should be restored manually.

4.8.6 System Un-installation

After being uninstalled, the system will be restored to the status before installation.

4.9 Itf-N Network Management Interface

M2000 provides standard CORBA interfaces in compliance with the 3GPP R99/R4 network management standards for NMS.

M2000 also provides FTP-based and Telnet-based interfaces.


4-11

4.10 Time Synchronization

M2000 provides NTP services to ensure that NEs and M2000 can synchronize in time.

System Description iManager M2000 Mobile Element Management System Chapter 5 System Reliability

5-1

Chapter 5 System Reliability

5.1 Overview of M2000 System Reliability

M2000 system reliability is based on reliability design. The reliability design of M2000 comprises:

System reliability Hardware reliability Software reliability

5.2 System Reliability

System reliability design includes the following aspects:

Data security Operation security

5.2.1 Data Security

All the M200 system data, including performance data, alarm data, configuration data, security data and log data, is collectively saved at the database of M2000 Server. High security of the database and backup and restoration function for the system data ensure the reliability of system data.

I. Backup Mechanism

M2000 provides automatic and manual backup function.

It automatically backs up system data every day, every week or every month. With manual backup function, you can perform the backup command anytime.

The backup data can be output to external media.

II. Restoration Mechanism

In case there is data damaged due to system failure or upgrade failure, you can execute the restoration command to restore the system data.

System Description iManager M2000 Mobile Element Management System Chapter 5 System Reliability

5-2

5.2.2 Operation Security

I. Limit to Login

M2000 limits the number of login attempts (the number is configurable). If the number of login attempts of a user exceeds the maximum, M2000 will lock the user, records the failure information in the system log and generates an internal alarm at the same time. After a period time (normally 30 minutes), M2000 will unlock the user.

II. User Monitor

M2000 monitors operations of all users, and generates maintenance reports. The user “admin” has the right to kick out any user.

III. Operation Confirmation

M2000 provides confirmation function for important or global operations.

5.3 Hardware Reliability

M2000 hardware supports dual-system mode. Two servers constitute a symmetrical high availability (HA) system through dual-system software and work in active/standby mode. M2000 features high reliability and running without interruption. It also supports single-system mode for the purposes of installation convenience and cost saving. In this mode, it adopts disk mirror.

5.4 Software Reliability

M2000 provides self-protection mechanism and checks the states of all M2000 services periodically. For any fault detected, M2000 records the failure information in the system log, resumes the service automatically or generates an alarm to get manual assistance.

System Description iManager M2000 Mobile Element Management System Chapter 6 System Specifications

6-1


6.1 Overview of M2000 System Specifications

This chapter introduces system specifications, including

Performance specifications Environment parameters Reliability specifications

6.2 Performance Specifications

6.2.1 Overview of Performance Specifications

The system performance depends on following aspects:

System capacity Performance data storage capacity Alarm data storage capacity Alarm response

6.2.2 System Capacity

Table 6-1 describes the system capacity.

Table 6-1 M2000 system capacity

Item Typical configuration 1

Typical configuration 2

Typical configuration 3

Network scale (number of equivalent NEs)

< 28 < 42 < 84

Hardware configuration

One Sun Netra 20 Server

One Sun Fire V880 Server

One Sun Fire 4800 Server

The number of equivalent NEs depends on the complexity of NEs used, as described in Table 6-2.


6-2

Table 6-2 Equivalent NEs

NE type Complexity Number of equivalent NEs

MSC Server 1 1

MSC 1.1 1.1

MGW 0.2 0.2

SGSN 0.8 0.8

RNC 0.8 0.8

GGSN 0.6 0.6

CG 0.2 0.2

HLR 0.3 0.3

NodeB 0.008 0.008

The number of supported simultaneous client sessions is 20.

6.2.3 Performance Data Storage Capacity

M2000 stores all performance data of managed NEs in the Performance Database.

In the default configuration, the system allocates 12.3-GB disk space to the Performance Database. In this case, the maximum number of jobs allowed by the system is 300, and the maximum number of recorded results of a job that can be stored in the Performance Database is 432,000.

In the default configuration, the maximum number of counters allowed for a job is 128, and the counters must belong to objects of the same type and the maximum number of the objects allowed for a job is 200.

6.2.4 Alarm Data Storage Capacity

M2000 stores all the alarm data of managed NEs in Alarm Database.

In the default configuration, the system allocates 4-GB disk space to the Alarm Database. Table 6-3 lists the maximum numbers of alarms.

Table 6-3 Alarm data storage capacity

Alarm type Maximum number of

alarms

Alarm meaning

Current fault alarm

100,000 Current fault alarms refer to the alarms generated when faults occur in the system. Current fault alarms can be cleared when the


6-3

Alarm type Maximum number of

alarms

Alarm meaning

faults are removed and the system is back to normal operation.

Event alarm 2,000,000 Event alarms refer to the reports on instantaneous running states of the system.

History fault alarm

2,000,000 History alarms refer to the fault alarms that have been acknowledged and cleared by the operator.

6.2.5 Alarm Response

Generally, when an alarm occurs on NE, it will be displayed on M2000 Client in 5 to 6 seconds.

Hardware configuration of M2000 server determines alarm-handling capacity. For Sun Netra 20, it is up to 60 alarms per second for 40 minutes, for Sun Fire V880, it is up to 100 alarms per second for 40 minutes, for Sun Fire 4800, it is up to 160 alarms per second for 40 minutes.

6.3 Environment Parameters

Table 6-4 lists parameters of system operational environment.


6-4

Table 6-4 System operational environment parameters

Equipment

Item M2000 Client M2000 Server

Hardware platform P4 CPU/256M memory/40G Hard Disk (HD) or above

Sun Netra 20, Sun Fire V880 or Sun Fire 4800

Software platform Windows 2000 professional operating system

Operating system: Sun Solaris 8;

Database: Sybase 12.0

Power consumption 250 W

Sun Netra 20: Single Server 620W, Dual Server 1700W

Sun Fire V880: Single Server 1975W, Dual Server 3490W

Sun Fire 4800: Single Server 3940W, Dual Server 6980W

Normal working range:15°C - 35°C Temperature

Safe working range: 0 °C - 45 °C

Normal working range: 30% - 65% Humidity

Safe working range: 10% - 90%

6.4 Reliability Specifications

M2000 possesses different reliabilities if it is configured with different servers, as shown in Table 6-5:

Table 6-5 Single server reliability specification

Server Type Sun Netra 20 Sun Fire V880 Sun Fire 4800 Dual server

MTBF 35,833 hours 26,636 hours 19,097 hours 11,586,838 hours

Total system failure duration every year 1.096524 hours 2.122436 hours 1.241116 hours 0.048835 hours

System availability 99.987483% 99.975771% 99.985832% 99.99944%

MTTR 1.4823 hours 1.2570 hours 0.5701 hours 1.0158 hours

System Description iManager M2000 Mobile Element Management System Appendix Acronyms and Abbreviations

F-1

Appendix Acronyms and Abbreviations

Numerics

3GPP 3rd Generation Partnership Project

C

CG Charging Gateway

CORBA Common Object Request Broker Architecture

CPU Center Processing Unit

CSV Comma Separation Value

E

EM Element Management

EMS Element Management System

G

GB Gigabyte

GHz Gigahertz

GGSN Gateway GPRS Support Node

GUI Graphic User Interface

H

HA High Availability

HD Hard Disk

HLR Home Location Register

HTML Hyper Text Markup Language

I

ID Identity

IRP Integration Reference Point

L

LAN Local Area Network

LMT Local Maintenance Terminal

M

MSC Mobile Service Switching Center

MSC Server Mobile Service Switching Center Server

MTBF Mean Time Between Failures

System Description iManager M2000 Mobile Element Management System Appendix Acronyms and Abbreviations

F-2

MTTR Mean Time To Repair

MGW Media Gate-Way

MML Man Machine Language

N

NE Network Element

NMS Network Management System

NodeB WCDMA base station

NTP Network Time Protocol

P

PC Personal Computer

PSTN Public Switched Telephone Network

R

RNC Radio Network Controller

S

SGSN Serving GPRS Support Node

SNMP Simple Network Management Protocol

SMS Short Message Service

T

TMN Telecommunications Management Network

W

WCDMA Wideband Code Division Multiple Access

X

XML Extensible Markup Language

System Description iManager M2000 Mobile Element Management System Index

i-1

Index

C centralized cofiguration management

configuration data backup, 4-3

configuration data restoration, 4-3

configuration date query, 4-3

function description, 4-2

link report, 4-3

NE configuration, 4-3

NE report, 4-3

centralized fault management

alarm acknowledgement, 4-4

alarm correlation analysis, 4-4

alarm database auto displacement, 4-4

alarm query, 4-4

alarm statistic, 4-4

alarm un-acknowledgement, 4-4


handing experience management, 4-5

level redefinition, 4-4

real-time alarm browse, 4-4

remote notification, 4-5

centralized performance management

customizable report, 4-7

customized counter management, 4-7

data management, 4-6


job management, 4-5

performance alarm, 4-7

template management, 4-7

centralized security management


log management, 4-9

terminal management, 4-9

user account management, 4-8

user group management, 4-8

centralized software management

file transmission, 4-8


license management, 4-8

NE data backup, 4-8

NE version management, 4-8

centralized topology management


topological map, 4-2

topological navigation tree, 4-2

topological object management, 4-1

E environment parameter

hardware platform, 6-3

humidity, 6-3

power consumption, 6-3

software platform, 6-3

temperature, 6-3

H hardware reliability, 5-2

I Itf-N interface, 4-10

M management function, 1-1

management object, 1-1

IP device, 1-2

network product, 1-1

N network application, 1-2

network position, 1-2

P physical architecture

client configuration, 3-2

System Description iManager M2000 Mobile Element Management System Index

i-2

server configuration, 3-2

typical configuration, 3-1

R reliability

hardware, 5-2

software, 5-2

system, 5-1

reliability specification

MTBF, 6-4

MTTR, 6-4

system availability, 6-4

total system failure duration every year, 6-4

S software architecture, 3-3

client, 3-4

interface, 3-4

server, 3-4

software module, 3-3

software reliability, 5-2

system capacity

NE scale, 6-1

system capacity

client session, 6-2

system characteristic

client software automatic upgrade, 2-2

custom reports, 2-1

IP device management, 2-2

Itf-N interface, 2-1

log management, 2-2

muti-platform component-based architecture, 2-1

software management, 2-1

time synchronization, 2-2

system management

data backup, 4-10

data restoration, 4-10


online help, 4-10

remote maintenance, 4-10

state monitoring, 4-10

un-installation, 4-10

system reliability, 5-1

data security, 5-1

operation security, 5-2

system specification

alarm data storage capacity, 6-2

alarm response, 6-3

environment parameter, 6-3

performance, 6-1

performance data storage capacity, 6-2

reliability, 6-4

system capacity, 6-1

T time synchronization, 4-11

typical configuration

client, 3-2

server, 3-2

system, 3-1

i.

Documents

M2000 System Description