IManager M2000 V200R012 Product Description(GSM&UMTS&LTE) 03(20120530)[1]

iManager M2000 V200R012

Product Description

Issue 03

Date 2012-05-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without

prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other

trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the commercial contract made

between Huawei and the customer. All or partial products, services and features described in this

document may not be within the purchased scope or the usage scope. Unless otherwise agreed by

the contract, all statements, information, and recommendations in this document are provided “AS

IS” without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in

the preparation of this document to ensure accuracy of the contents, but all statements, information,

and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/

mailto:[email protected]


Product Description

Issue 03 (2012-05-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

Page 3 of 47

Contents

1 Introduction.................................................................................................................................... 5

1.1 Positioning ....................................................................................................................................................... 5

1.2 NEs Managed by the M2000 ............................................................................................................................ 5

1.2.1 WRAN NEs ............................................................................................................................................ 5

1.2.2 GBSS NEs ............................................................................................................................................... 5

1.2.3 SingleRAN NEs ...................................................................................................................................... 6

1.2.4 GU CN NEs ............................................................................................................................................ 6

1.2.5 LTE/EPC NEs ......................................................................................................................................... 7

1.2.6 uBro NEs ................................................................................................................................................. 7

1.2.7 STP NEs .................................................................................................................................................. 7

1.2.8 NGN NEs ................................................................................................................................................ 7

1.2.9 IMS NEs ................................................................................................................................................. 8

1.2.10 Wireless Bearer Network Devices ........................................................................................................ 8

1.2.11 Auxiliary Networking Devices .............................................................................................................. 9

1.3 Benefits ............................................................................................................................................................ 9

2 Architecture .................................................................................................................................. 11

2.1 Overview ........................................................................................................................................................ 11

2.2 Hardware Structure ........................................................................................................................................ 11

2.3 Software Structure .......................................................................................................................................... 11

2.4 External Interfaces ......................................................................................................................................... 12

3 Products and Application Scenarios ....................................................................................... 14

3.1 Overview ........................................................................................................................................................ 14

3.2 OM Solutions ................................................................................................................................................. 14

3.3 Network Deployment ..................................................................................................................................... 20

3.4 Network Monitoring ....................................................................................................................................... 22

3.5 Network Adjustment ...................................................................................................................................... 25

3.6 Service Management ...................................................................................................................................... 27

4 Configuration ............................................................................................................................... 29

5 Operation and Maintenance ..................................................................................................... 32

5.1 Overview ........................................................................................................................................................ 32

5.2 O&M Features ................................................................................................................................................ 32

6 Technical Specifications ............................................................................................................ 35


Product Description



Page 4 of 47

6.1 Overview ........................................................................................................................................................ 35

6.2 Management Capability ................................................................................................................................. 35

6.3 Reliability Specifications ............................................................................................................................... 36

6.4 Compliant Safety Standards ........................................................................................................................... 38

6.5 EMC Specifications ....................................................................................................................................... 38

6.6 Environmental Requirements ......................................................................................................................... 39

6.6.1 Storage Environment ............................................................................................................................. 39

6.6.2 Transportation Environment ................................................................................................................. 41

6.6.3 Operating Environment ......................................................................................................................... 44

A Acronyms and Abbreviations .................................................................................................. 47


Product Description



Page 5 of 47

1 Introduction

1.1 Positioning

This document is applicable to the iManager M2000 V200R012, a mobile element

management system (EMS).

The iManager M2000 centrally manages Huawei mobile network elements (NEs), including

WRAN NEs, GBSS NEs, SingleRAN NEs, GU core network (CN) NEs, LTE/EPC NEs, uBro

NEs, NGN NEs, STP NEs, and IMS NEs. It also manages the wireless bearer network devices

and auxiliary networking devices used in the mobile network. The M2000 provides basic

functions such as configuration management, performance management, fault management,

security management, log management, topology management, software management, and

system management. It also provides various optional functions.

By default, SingleRAN NEs are managed by one M2000 system.

The M2000 provides centralized operation and maintenance (OM) functions for the Huawei

mobile element management solution. The M2000 adopts a modular design that allows the

modules to communicate with one another through the CORBA bus. In addition, the M2000

provides mediations for connecting various types of NEs.

The M2000 also provides external interfaces for interoperability with non-Huawei systems.

1.2 NEs Managed by the M2000

1.2.1 WRAN NEs

The M2000 manages the following WRAN NEs:

Radio network controller: BSC6800, BSC6810

Multi-mode base station controller: BSC6900 UMTS, BSC6910 UMTS

Base station: NodeB

IP clock server

1.2.2 GBSS NEs

The M2000 manages the following GBSS NEs:


Product Description



Page 6 of 47

Base station controller: BSC32, GT800BSC, BSC6000(GSM-R), BSC6000

Multi-mode base station controller: BSC6900 GSM, BSC6910 GSM

Base station: GSM BTSs except BTS3900B and BTS3900E

GSM Pico BTS: BTS3900B

GSM Compact BTS: BTS3900E

IP clock server

Packet control unit: PCU35, PCU33, PCU6000

1.2.3 SingleRAN NEs

The M2000 manages the following SingleRAN NEs:

Multi-mode base station controller: BSC6900 GU, BSC6910 GU

Multi-mode base station: MBTS(GU) , MBTS(GL) , MBTS(UL) , MBTS(GUL) ,

MBTS(WL)

1.2.4 GU CN NEs

GU CN NEs consist of UMTS CN NEs and GSM CN NEs. Huawei CN NEs can be used on

both UMTS and GSM networks. The M2000 manages the following GU CN NEs:

Serving GPRS support node: SGSN

Gateway GPRS support node: GGSN

Report server: SUR

Mobile switching center server: MSC server

Home location register: HLR9820

Home location register (service node): HLR-FE

Media gateway: MGW

Fixed-mobile convergence media gateway: FMCMGW

Charging gateway: CG

Signaling gateway: SG7000

Interworking function: IWF

Enhanced name server: ENS

Unified number portability: UNP

Unified identity management: UIM

Unified equipment identity register: UEIR

Unified subscriber center database: USCDB

Visual IP

Security immunity gateway: SIG

Embedded Edge Router: EER

SigProbe

SigProbeTDM

Home subscriber server: HSS9860

User Profile Agent: UPA


Product Description



Page 7 of 47

1.2.5 LTE/EPC NEs

The M2000 manages the following LTE/EPC NEs:

eNodeB: DBS3900 LTE, BTS3900 LTE, BTS3900A LTE, BTS3900L LTE, BTS3900AL

LTE

Pico eNodeB: BTS3202E

BTS3202B

SAE-home subscriber server: SAE-HSS

Unified serving node: USN

Unified gateway: UGW

Charging gateway: CG

Unified policy and charging controller: UPCC

Signaling service processing system: SPSV3

Home subscriber server: HSS9860

Universal switching unit: USU

Wireless backhaul system: eRelay, including eRelay BS and eRelay Remote Node

(RRN)

1.2.6 uBro NEs

The M2000 manages the following uBro NEs:

UMTS access point: AP

Access gateway: AG

AP home register: AHR

IP clock server

Authentication, authorization, and accounting: AAA

Security gateway

AP management system: AP Manager

The M2000 does not directly manage APs. The alarm and performance data of APs are reported to the

M2000 through the AP Manager.

1.2.7 STP NEs

The M2000 manages the following STP NEs:

Convergent Application Server: CAS9910

Signaling Service Processing System: SPS

Signaling Gateway: SG7000

1.2.8 NGN NEs

The M2000 manages the following NEs involved in the NGN solution:

Softswitch System: SoftX3000

Media Gateway: MGW


Product Description



Page 8 of 47

Signaling Gateway: SG7000

Signaling Service Processing System: SPS

Media Switch Server: MediaX3600

Session Border Controller: SE2300/SE2600

Media Resource Server: MRS6100

iGateway Bill: iGWB

Signaling Transfer Point: STP

Smart Home Location Register: SHLR9200


1.2.9 IMS NEs

The M2000 manages the following IMS NEs:

Media gateway: MGW

Session border controller: SBC (SE2300, SE2600)

Home subscriber server: HSS (HSS9820)

Calling session control function: CSCF (CSC3300)

Unified policy and charging controller: UPCC

Charging collection function: CCF (iCG9815)

Advanced telephony server: ATS (ATS9900)

Multimedia exchange server: MediaX (MediaX3600)

IP Centrex: IPCTRX (ETAS9960)

Multimedia resource function processor: MRFP (MRP6600)

Unified subscriber center database: USCDB

Attachment information management system: AIM (AIM6300)

Service provisioning gateway : SPG (SPG2800)

Unified gateway controller: UGC (UGC3200)

E.164 Number: ENUM


Mediation

Presence server, Group server, Messaging server: PGM

Enhanced name server: ENS

ViewPoint

Open Service Gateway: OSG

Access Gateway Control Function: AGCF (UAC3000)

Rich Communication Suite: RCS (RCS9100)

Terminal Management System: TMS9950

Networking Recorder Server: NRS

Universal Media Gateway: UGW9500

1.2.10 Wireless Bearer Network Devices

The M2000 manages the following wireless bearer network devices:


Product Description



Page 9 of 47

Metro1000V3

OSN3500

RTN

BITS

1.2.11 Auxiliary Networking Devices

The M2000 manages the following auxiliary networking devices:

NE08-series routers

Eudemon-series firewalls

S-series LAN switches

AR46-series routers (AR4640)

Domain name server (DNS)

Dynamic host configuration protocol server: DHCP server

NE bearing server, a server bearing the services of the SG7000, MSC server, and iGWB

Wi-Fi device: Skyway Excel XL5810 from the third-party

Security Access Gateway: SVN

When the enhanced management functions such as DNS and DHCP are required, users need to purchase

Huawei customization services.

1.3 Benefits

Open Structure Allows for Smooth Evolution

The M2000 is a future-proof solution for managing mobile networks. It provides a centralized

network management platform for supporting telecom operators in their long-term network

evolution and shielding the differences between various network technologies. The M2000

focuses on the continuous efforts of telecom operators toward better network OM and retains

the O&M experience of previous network management systems.

The M2000 is a centralized wireless network management platform. The M2000 server

software consists of the main version software and mediation software. The main version

software implements system functions, and the mediation software is used for the adaptation

of different NE interfaces. The M2000 can manage new NEs after the corresponding

mediation software is installed. The M2000 adopts an open structure so that it can manage the

CN, NGN, STP, IMS, and radio networks of various technologies such as GSM, WCDMA,

and LTE. In addition, the M2000 can evolve accordingly when the network evolves.

The M2000 provides standard CORBA, SNMP, file, and alarm streaming interfaces. In

addition, the M2000 allows for interoperability with other systems provided by HP, Aircom,

IBM, Inspur, Remedy, Vallent, Mycom, and Bright Oceans.

Powerful Network Management

Centralized management of large-sized networks requires high system performance. In

addition, today's market demand focuses on hardware reuse and smooth expansion.


Product Description



Page 10 of 47

To address these requirements, the M2000 provides the multi-server load-sharing (SLS)

system based on the Sun platform and the cluster solution based on the ATAE platform. This

enables smooth network expansion, during which users can enhance the management

capability of the M2000 by adding one or more servers to the SLS system or by adding

service boards to the ATAE cluster system. This protects the telecom operator's hardware

investments and reduces network deployment costs.

Reduce OPEX

The Configuration Management Express (CME), a radio configuration solution, provides

powerful functions through wizards, templates, and GUIs. It enables users to plan

configuration items, check the data of the entire network, and compare cell configuration data

against the baseline cell. This facilitates data configuration for the entire radio access network.

The CME enables users to create sites in batches remotely, expand network capacity quickly,

optimize network efficiently, and reparent base stations easily. This improves the

configuration efficiency and accuracy.

The iSStar enhancement maintenance platform enables O&M engineers to customize the

service process by editing programs. With it, the M2000 can automatically handle O&M tasks

in batches.

In addition, the M2000 provides a series of featured functions, including a network health

check, remote and batch upgrade of NEs, automatic base station planning, automatic

optimization of neighboring cell relationships, remote base station commissioning, device

panels, maintenance-mode alarm setting, and RAN sharing management.

These functions greatly facilitate operation and maintenance and therefore reduce the total

cost of operation (TCO).


Product Description



Page 11 of 47

2 Architecture

2.1 Overview

The M2000 system works in client/server (C/S) mode.

The M2000 software consists of the client software, server software, and NE mediation

software. The client software runs on the M2000 client, and the server software and mediation

software run on the M2000 server.

This chapter describes the hardware and software structures of the M2000 system.

2.2 Hardware Structure

The M2000 system typically consists of M2000 servers, M2000 clients, alarm boxes, and

some networking devices. Figure 2-1 shows the hardware structure of the M2000

single-server system. The M2000 provides multiple solutions to meet the specific scenario

requirements of telecom operators. For details about these solutions, see section 3.2 "OM

Solutions".

Figure 2-1 Hardware structure of the M2000 single-server system

2.3 Software Structure

As shown in Figure 2-2, the M2000 software is classified into the following types:


Product Description



Page 12 of 47

M2000 server software

M2000 client software

NE mediation software

NE mediation software varies according to the NE version. Through the adaptation of the NE

mediation software, the M2000 connects to the NE of the corresponding version.

Figure 2-2 Software structure of the M2000 system

2.4 External Interfaces

To interconnect with external systems and software, the M2000 provides the following

interfaces:

CORBA interface

The CORBA interface is based on CORBA interface specifications and is in compliance

with 3GPP R6 specifications.

Through the CORBA interface, the NMS manages M2000 alarms, sets performance

measurement tasks, queries M2000 configuration data, and queries and delivers

configuration parameters in batches.

CORBA security interface

Through the CORBA security interface, the NMS manages M2000 users and user rights,

such as creating users and maintaining user information.

File interface

The M2000 saves alarm data, performance data, configuration data, inventory data, and

LTE tracing data as files. Through the file interface, the NMS obtains and processes

these files.


Product Description



Page 13 of 47

The NMS can use the configuration file interface to obtain configuration data from the

M2000. In addition, after the CME is installed, the configuration file interface can be

used to integrate the data planning tools of telecom operators into the M2000. That way,

data planning, modification, and activation are automatically performed through the

configuration file interface. The configuration file interface is applicable to O&M

scenarios such as site creation, site relocation, network parameter optimization, and the

optimization of neighboring cell relationships.

Alarm streaming interface

The M2000 forwards NE alarms to the NMS in the form of character stream in real time.

The NMS can actively obtain the list of active alarms from the M2000.

SNMP interface

Through the SNMP alarm interface, the M2000 forwards alarms to the NMS for

handling in real time. The SNMP interface supports the SNMPv1, SNMPv2, and

SNMPv3 protocols.

MML transparent transmission interface

The MML transparent transmission interface serves as a proxy for transferring MML

commands between the NMS and NEs. With this interface, the NMS can operate and

maintain the related NEs using MML commands.

Syslog interface

The M2000 forwards operating system logs, M2000 logs, and NE logs using the Syslog

protocol.

LDAP user management interface

This interface complies complies with LDAP. Through this interface, a third-party’s

security management system can create, modify, delete, and query Huawei OSS systems

accounts.

LDAP user authentication interface

This interface supports the account authentication based on LDAP as well as remote

authentication of user names and passwords.

RADIUS user authentication interface

This interface supports the account authentication based on RADIUS as well as remote

authentication of user names and passwords.

Northbound line test interface

The line test system connects to the NEs managed by the M2000 server through the

northbound interfaces for line test. In this way, the line test system works with the NEs

to automatically handle and manage subscriber complaints, conduct test, and rectify

faults.

TL1 northbound interface

The TL1 northbound interface of the M2000 is used to interconnect the EMS with the

OSS, which provides encryption for transferred information by using the SSH

technology to ensure that TL1 messages are transferred securely. By using the TL1

northbound interface, the OSS can provide services and perform O&M operations for

integrated access devices (IADs), multimedia terminals, voice subscribers, basic rate

access (BRA) subscribers, primary rate adaptation (PRA) subscribers, and multimedia

subscribers. In addition, the OSS manages NGN resources and services of the SHLR,

AGCF and SoftX3000 by using the TL1 northbound interface. NEs report notification

messages to the OSS by using the TL1 northbound interface of the M2000.


Product Description



Page 14 of 47

3 Products and Application Scenarios

3.1 Overview

The M2000 provides various O&M solutions for telecom operators to meet the requirements

of network deployment, network monitoring, network adjustment, and service management.

Telecom operators can select proper M2000 systems as required.

3.2 OM Solutions

The M2000 provides various OM solutions based on M2000 system solutions and platforms:

ATAE-based single-server and HA systems manage devices only on uBro and WiMAX

networks.

The SLS, remote HA, and emergency systems are developed based on the Sun platform.

The ATAE cluster system is developed based on the ATAE platform.

The local HA system is supported by Sun, HP, and ATAE platforms.

The low-cost solution, which uses the single-server system based on the IBM platform,

manages devices only on IMS networks.

Sun-Based SLS System

Developed on the Sun platform, the SLS system allows the deployment of multiple servers to

implement the centralized management of large-sized networks.

In the M2000 SLS system, multiple servers are deployed to form an EMS, and services are

loaded and processed on different servers in a distributed manner. The SLS system manages

multiple M2000 servers in a centralized manner and supports the smooth expansion of the

M2000. Therefore, the costs for operating and maintaining multiple M2000 systems are

reduced. Figure 3-1 shows the physical structure of an M2000 SLS system.


Product Description



Page 15 of 47

Figure 3-1 Physical structure of an M2000 SLS system

Table 3-1 describes the devices on the server side in the SLS system.

Table 3-1 Devices on the server side in the SLS system

Device Description

Master server The master server runs the M2000 server software and balances load

with slave servers.

Slave server Slave servers run the M2000 server software and balance load with the

master server.

Standby server The standby server functions as a backup for the master or slave

server. If the master server or the slave server becomes unavailable,

the services carried by the master or slave server are switched over to

the standby server through the cluster software.

Disk array The disk array provides reliable storage for the master and slave

servers. When an exception occurs on the master server or on a slave

server, the cluster software mounts the disk array to the standby

server.

ATAE Cluster Solution

Developed on the ATAE platform, the ATAE cluster system allows the deployment of multiple

blades to provide powerful management capabilities.

Consisting of multiple server blades, switching blades, OSS self management unit (OSMU),

and disk arrays, the ATAE cluster system has the following features:

High integration

High performance

N:1 redundancy

Hardware redundancy

Blade plug-and-play

OSMU intelligent management


Product Description



Page 16 of 47

With the increasing demand of enhanced management capability, users can implement

capacity expansion by adding blades. In addition, multiple OSS products, such as the M2000,

the PRS, and the Nastar, can be deployed on the ATAE cluster system in a centralized manner.

This enables telecom operators to use multiple OSS products at the same time. Figure 3-2

shows the physical structure of the ATAE cluster system.

Figure 3-2 Physical structure of the ATAE cluster system

Table 3-2 describes the devices on the server side in the ATAE cluster system.

Table 3-2 Devices on the server side in the ATAE cluster system

Device Description

ATAE subrack The typical configuration is as follows:

The OSMU board monitors and manages the entire ATAE cluster

system and can be accessed through a Web browser.

Solution for 400 equivalent NEs: three service boards (one active,

one slave, and one standby) and one database board. A Trace Server

board must be configured when an M2000 is created in the LTE

network.

Solution for 800 equivalent NEs: four service boards (one active,

two slave, and one standby) and two database boards. A Trace

Server board must be configured when an M2000 is created in the

LTE network.

Two switching blades provide the functions of a switch.

One standby database blade provides the hot backup service for the

database blades of the M2000 and the PRS.

Disk array Other server blades except the OSMU use the disk array as a storage

device.

Local Disaster Recovery

Huawei provides an M2000 high availability (HA) system where services are automatically

switched over from the active server to the standby server when an exception occurs in the

active server. In this way, the reliability of the M2000 system is improved.


Product Description



Page 17 of 47

The active and standby servers are located at the same place to constitute an HA system

through the cluster software. The active and standby servers communicate with each other on

a local area network (LAN) and access the same disk array. Figure 3-3 shows the physical

structure of an M2000 HA system.

Figure 3-3 Physical structure of the M2000 HA system

Table 3-3 describes the devices on the server side in the HA system.

Table 3-3 Devices on the server side in the M2000 HA system

Device Description

Active server The active server functions as the M2000 system active server. It runs

the M2000 server software. The active server, together with the

standby server, performs resource monitoring and service switchover

through the cluster software.

Standby server The standby server functions as a backup for the active server. When

the active server becomes unavailable, the resources carried by the

active server are switched over to the standby server through the

cluster software.

Disk array Two disk arrays, one of which is the mirror of the other, provide

reliable storage space. When an exception occurs on the active server,

the cluster software mounts the disk array to the standby server.

Sun-Based Remote Disaster Recovery

Huawei remote HA system provides software and hardware redundancy. It also effectively

reduces the impact of power failures, earthquakes, fires, wars, tsunamis, and mudslides.

Remote protection is implemented on both the M2000 servers and the disaster recovery

capability of the M2000 is improved.


Product Description



Page 18 of 47

The active and standby servers in different locations constitute a remote HA system through

the cluster software. The active and standby servers communicate with each other through the

OM network and access different disk arrays. Figure 3-4 shows the physical structure of a

remote HA system.

Figure 3-4 Physical structure of a remote HA system

Table 3-4 describes the devices on the server side in the remote HA system.

Table 3-4 Devices on the server side in the remote HA system

Device Description

Server The server functions as the M2000 system server. It runs the M2000

server software. The servers in equipment rooms I and II perform resource

monitoring and service switchover through the cluster software.

Disk array The disk array provides the server with reliable storage.

Sun-Based Emergency System

The emergency system has lower hardware requirements than typical local and remote HA

systems and is applicable to M2000 single-servers, HA systems, and SLS systems that are

based on the Sun platform. The emergency system functions as a backup for the M2000

primary system. It provides basic network management services when the primary system

fails to provide services properly. The emergency system and the primary system can be

deployed on the same LAN. They can also be deployed on different LANs and in this case

they communicate with each other through an IP network.

An emergency system can back up no more than four M2000 single-server systems and HA

systems, or no more than two M2000 SLS systems. The system to be backed up is referred to

as a primary system. When the emergency system takes over the services of one primary

system, it cannot take over the services of any other primary system.

Figure 3-5 shows the physical structure of the emergency system that backs up no more than

four M2000 single-server systems. Figure 3-6 shows the physical structure of the emergency

system that backs up no more than two M2000 SLS system.


Product Description



Page 19 of 47

Figure 3-5 Physical structure of the M2000 emergency system when it backs up N (N ≤ 4)M2000

single-server system

Figure 3-6 Physical structure of the M2000 emergency system when it backs up N (N ≤ 2) M2000

SLS systems

Table 3-5 describes the devices on the server side.

Table 3-5 Devices on the server side of the emergency system

Device Description

Server The server of the emergency system functions as a backup for the

server of the primary system. When the server of the primary system

becomes unavailable, the carried services are manually switched over

to the server of the emergency system.

Disk array The disk array provides the server with reliable storage.

Low-Cost Solution

The M2000 provides a low-cost solution, which uses the single-server system based on the

IBM platform to manage IMS networks. This solution meets users' demands for routine

network OM operations. In addition, it helps operators or users to reduce their purchase cost.

For example, the Sun-based single-server system uses disk arrays. However, the single-server

system based on the IBM platform uses IBM PC server and does not need disk arrays.


Product Description



Page 20 of 47

Web-Based Client Access

The M2000 provides the Citrix access solution, which enables users to log in to the M2000

client and perform routine OM operations through a Web browser on a PC with low

configurations.

In the Citrix access solution, one or more servers are added to the existing M2000 system.

The Citrix access solution has the following advantages:

Solving the problem that the number of connected clients is restricted by the hardware

capacity of the M2000 server

Reducing the costs of upgrading and maintaining the M2000 client

Reducing the hardware configuration costs of the PC that the M2000 client is running on

Lowering the requirements for the operating system environment of the PC that the

M2000 client is running on

Network Time Synchronization Solution

The M2000 supports the Network Time Protocol (NTP)/Simple Network Time Protocol

(SNTP), so the time of NEs on the entire network is synchronized.

The clock source and NTP server are provided by the telecom operator, and the M2000

server functions as the NTP client or intermediate NTP server. When functioning as an

intermediate NTP server, the M2000 can synchronize time with the upper-layer NTP

server and provide a clock source that managed NEs can synchronize with.

A dedicated clock server is provided, along with two NTP service channels working in

active/standby mode. The clock source server can be deployed as the top NTP clock

server, or as a medium NTP clock server.

Veritas System Backup and Restore Solution

The M2000 adopts the Veritas system backup and restore solution. Through this solution,

users can back up and restore the database software, application software, system

configuration files, service data stored in the database, and important NE data.

3.3 Network Deployment

Flexibly Managing and Mediating NEs

The mediation software can be installed to convert data between NEs and the M2000 so that

the M2000 can manage NEs.

The M2000 can dynamically install NE mediations, or upgrade NE mediation patches without

disrupting M2000 services on a web-based GUI or command line interface. When managing

various types of NEs, the M2000 can install mediations in batches without disrupting M2000

services. This reduces the costs of manual operations and interventions.

Remote and Centralized Initial Configuration

The M2000 provides the remote and centralized initial configuration function during initial

network configuration either through a GUI or a command-line interface.


Product Description



Page 21 of 47

Through a GUI

The M2000 provides the CME for users to configure the GBSS, WRAN, eRAN, and

SingleRAN NEs. The M2000 also provides a basic configuration function for all NEs in

the CS domain on the CN. Users can prepare configuration data in batches and remotely

configure basic device data in a centralized manner through a GUI. NEs can provide

basic services after being configured initially.

Through a command-line interface

The M2000 provides a command-line interface, which enables users to deliver MML

commands to multiple NEs of the same type on the M2000 client.

Users can save MML commands in a script and then schedule and deliver the script to

NEs through the M2000. Users can deliver MML commands in debugging mode or task

mode. When delivering commands in debugging mode, users can check script execution

information and execution result of each command in real time. When delivering

commands in task mode, users only need to select the desired script and create a task by

using the centralized task management function.

Radio Transmission Device Search

The M2000 can manage a large number of transmission devices such as microwave devices in

mobile networks in a centralized manner. The radio transmission device search function

enables users to search for all the transmission devices that meet specified search conditions.

Then, users can select the required devices from the search result and create the related NEs in

a topology view. In this way, these devices are connected to the M2000 quickly.

Auto-Deployment for Base Stations and RTN

The M2000 provides the automatic deployment function for NodeBs, GBTSs, MBTSs,

eNodeBs and RTN. After the hardware a base station is installed and then the base station is

powered on, users can enable the M2000 to remotely perform automatic commissioning on

the base station so that the base station provides services properly. The automatic deployment

function implements automatic remote commissioning, so onsite operation and maintenance is

unnecessary.

Automatic Network Planning

The M2000 automatically plans and delivers the data of small-sized GSM BTSs to quickly

enable BTS services. This reduces BTS deployment duration, manual interventions, and BTS

deployment costs.

The M2000 automatically plans the frequencies, base station identity code (BSIC), cell

global identification (CGI), routing area identity (RAI), and neighboring cell

relationships for GSM Pico BTSs.

The M2000 automatically plans the frequencies, BSIC, and neighboring cell

relationships for GSM Compact BTSs.

The M2000 automatically plans the frequencies, PCI, TAC, root sequence index, and

neighboring cell relationships for Pico eNodeBs.

Remote and Centralized NE Upgrade

NE device upgrade is a common OM operation for service evolution. The M2000 can

remotely upgrade NE devices in batches in a centralized manner. Users can implement


Product Description



Page 22 of 47

dynamic mediation simply by upgrading NE software versions through the M2000. This

minimizes the impact of NE upgrade on the OM of the entire network.

NE Health Check

The NE health check function is used to check NE status and identify and locate potential

network problems before and after an NE upgrade, during routine network maintenance, or

when an exception occurs in the network. This facilitates troubleshooting.

NodeB License Management

The M2000 manages NodeB licenses by RAN. All the NodeBs in a RAN system share the

resources controlled by the same license. The M2000 enables users to allocate license

resources to the NodeBs in a RAN system in a centralized manner. The M2000 also enables

users to keep track of license resources and allocate them in real time. The M2000 enables

users to disable a license in scenarios such as network capacity expansion, ESN change, user

name change, and version upgrades. In this way, users can quickly apply for a new license. A

disabled license automatically applies a grace period. This ensures that services in the existing

network are running properly until a new license is applied. The M2000 also enables users to

use a trial license containing some features with a validity period and then determine whether

to purchase these features.

3.4 Network Monitoring

Topology Monitoring

The M2000 provides an integrated topology window, through which users can create and

manage the topology view of the entire network. The topology view displays the networking

status, geographical locations of devices, alarms generated during device operation, link status

between devices, and connection status between devices and the M2000. This helps users to

monitor the running status of the entire network.

Performance Monitoring

Using the performance monitoring function, the M2000 collects KPIs in real time, provides

associated data analysis, threshold alarm settings, and threshold warnings, and displays the

network operating status in a graph correctly. This facilitates routine network maintenance

and fault location. In addition, the M2000 provides performance monitoring functions based

on scenarios such as network deployment, routine maintenance, and operations during

holidays, meeting various user requirements.

Alarm and Event Monitoring

In scenarios such as NE deployment, upgrade, commissioning, and capacity expansion, NEs

report a large number of unnecessary alarms to the M2000. These alarms severely affect the

monitoring of alarms on devices that are not in maintenance mode. To address this problem,

the M2000 provides the maintenance mode alarm function. After users set maintenance modes

for an NE, alarms generated in the NE maintenance modes are regarded as maintenance mode

alarms. By default, the M2000 does not display maintenance mode alarms, generate an audio

or visual alarm message, send an alarm notification, or forward these alarms to an external

system. From the alarm monitoring window, users can browse, query, and collect statistics on


Product Description



Page 23 of 47

maintenance mode alarms by maintenance mode to meet user requirements in specified

scenarios. In a common O&M scenario, the M2000 enables users to view the alarm and event

information about all NEs on the network in real time. The M2000 provides various functions

based on the requirements for monitoring system performance and handling alarms.

To ensure that alarm data is accurate and intact, the M2000 provides the functions of

automatically and manually synchronizing alarm data in case of NE or network

disconnection.

To ensure that information can be effectively transmitted to users in real time, the M2000

provides audio and visual alarm notification through topology tips, alarm boxes, and

alarm boards. The M2000 can also send alarm information in short messages and emails

to ensure that the information is transmitted in time even when the site is unattended.

To help users to quickly locate the required information in the midst of a large amount of

alarm or event information, the M2000 provides the filtering function based on various

conditions. For example, users can filter alarm/event information by alarm/event source,

occurrence time, severity, and name.

To ensure that users can identify the required key alarms and events during routine

operation and maintenance, the M2000 provides the functions of redefining alarm

severities, converting events to Auto Detected Manual Cleared (ADMC) alarms,

shielding alarms on the M2000, shielding alarms on NEs, filtering maintenance mode

alarms, summarized parallel alarms, and alarm frequency analysis.

To help users handle alarms in time, the M2000 provides the functions of locating alarms

in a topology view, automatically clearing alarms, manually clearing alarms, and

displaying and analyzing alarms based on alarm correlations. In addition, the information

about how to handle alarms can be recorded on the M2000 for sharing purposes.

Security Monitoring

The M2000 provides security monitoring functions, which enable users to obtain information

about unauthorized activities or audit user operations in time. You can perform the following

operations through the M2000:

Querying and exporting users' NE operation logs

Monitoring online NE users and related user operations and forcing a user to exit

Configuration Data Query

Users can query the configuration information about the devices on the entire network

through the M2000. When an exception occurs on the network or when the network needs to

be adjusted, users can easily obtain the configuration information and then perform

troubleshooting or adjust the configurations.

To ensure that the configuration data is accurate and valid, the M2000 provides the

functions of synchronizing configuration data automatically, manually, and on a

scheduled basis in cases of configuration modification and network disconnection.

The M2000 enables users to query network configuration information in real time for

troubleshooting and configuration adjustment. In addition, the M2000 provides NE

reports, CN resource reports, NE statistical reports, link reports, and RAN configuration

reports.

The M2000 provides the status monitoring function, which enables users to obtain the

management status of objects such as cells, boards, and links, in the network in time.


Product Description



Page 24 of 47

The M2000 generates link status reports on a set schedule. This helps users identify link

exceptions when links are disconnected or the alarm information is unclear.

Inventory Information Query

The inventory management function enables users to manage the physical and logical asset

information on the network in a centralized manner. Users can view, query, maintain,

synchronize, import, or export the inventory information.

Troubleshooting

The M2000 provides subscriber tracing, cell tracing, interface tracing, and real-time NE

resource monitoring functions through GUIs and supports centralized tracing management for

the entire network. This helps OM engineers locate call-related faults and network faults,

optimize the network coverage, and solve interconnection problems. This reduces the OM

costs for telecom operators. For the LTE network, the M2000 deploys a Trace Server to trace

a large amount of data. Trace Server supports deployed in ATAE platform and HP DL580

servers. The M2000 is deployed in the ATAE platform, Trace Server is configured in ATAE

platform by default. The M2000 is deployed in SUN server, Trace Server can choose

deployed in ATAE platform alone, also can be deployed in HP DL580 server.

The device panel displays the boards of physical devices in a graph and displays the board

status and alarm information in real time. In addition, the M2000 provides a topology view of

RRUs for distributed base stations. This helps users keep track of the relationships between

sites and locate faults.

GBSS and WRAN antenna fault detection systems detect faults on GBSS and WRAN

antennas and help users detect and locate antenna faults.

iSStar

The M2000 provides a powerful script enhancement maintenance platform, HFC library

function, and an easy-to-use High level Script Language (HSL).Users can create an HSL

script for routine maintenance, which is time-consuming and tedious, and then use the iSStar

to edit, debug, and run the HSL script. This automates routine maintenance, reduces the

workload, and improves the work efficiency.

Bearer Network Management

The M2000 provides bearer network management functions such as the QoS management for

users to check whether a network fault is related to data transmission. This facilitates fault

locating and improves troubleshooting efficiency.

WRAN QoS management: When IP networking is adopted, the M2000 can monitor IP

link alarms and key transmission counters and test IP links. When ATM networking is

adopted, the M2000 can test network transmission quality by instructing NEs to deliver

simulation service packets.

Ethernet OAM: According to the ETH OAM specifications defined in IEEE 802.1ag and

IEEE 802.3ah, the M2000 provides the Ethernet OAM function, which improves the

maintenance of the Layer 2 Ethernet.

LTE QoS management: The M2000 provides the functions of managing IP link alarms

and monitoring key performance counters.


Product Description



Page 25 of 47

NGN Test Management

While operating a device, users need to test the connected user terminals and lines regularly to

check whether these devices work properly. If a device fails, users need to identify the cause

by using a line test. Before deployment or during equipment operation, O&M personnel can

perform QoS and trunk testing to check the voice quality of a bearer network.

NGN test management reduces O&M costs as it eliminates the need for separate line and

bearer network test tools.

Signaling Link Management

The functions of the STP signaling link management consist of device topology management,

resource status statistics, port check, and backup data management. The functions help you

monitor and analyze configuration data and status data on DSPs, links, link sets, associations,

and association sets.

Device topology management enables the system to monitor the networking conditions

and running status of the signaling network devices in real time, improves the

maintainability of signaling network devices, ensures the network security and reliability

of SS7 network, and promotes network optimization.

Resource status statistics enables the system to take statistics on and analyze the key

configurations of signaling network devices. Therefore, the system can obtain the global

network resource status and discover faults in time.

Port check enables the system to obtain the port usage and compare the port usage with

the planning data. Therefore, the system can rectify port faults in time, improving port

security.

Backup data management enables the system to back up key data tables of signaling

network devices. Users can query the difference of backup data tables to learn about the

data configuration changes of signaling network devices.

IMS Subscriber Information Inquiry

During routine maintenance or fault identification, maintenance engineers have to use

multiple tools to query subscriber information, and the work efficiency is greatly affected. The

M2000 provides the IMS subscriber information inquiry function, helping maintenance

personnel engineers query all information (including basic information, service information,

and status information) about a subscriber served by an IMS NE, which facilitates customer

complaint handling and fault identification.

3.5 Network Adjustment

Configuration Adjustment

The M2000 provides the remote and centralized configuration adjustment function for

network troubleshooting and optimization through a GUI or a command-line interface.

Through a GUI

The M2000 provides the CME with which users can adjust the configuration of the

GBSS, WRAN, eRAN, and SingleRAN NEs. The M2000 provides the basic

configuration function for all the CS NEs on the CN.


Product Description



Page 26 of 47

Through a command-line interface

The M2000 provides a command-line interface, which enables users to issue MML

commands to multiple NEs of the same type to adjust configuration data.

Automatic Network Optimization

The M2000 provides the automatic optimization function for small-sized GSM BTSs and

eNodeBs. This improves the self-adaptation capability of networks and reduces the costs of

manual analysis and interventions.

The M2000 provides the frequency optimization function for GSM Pico BTSs. It allows

users to automatically optimize the frequencies, capacities, and neighboring cells for

GSM Compact BTSs.

The M2000 provides the following functions for eNodeBs:

− Mobility robust optimization (MRO) policies

− Inter-cell interference coordination (ICIC) optimization policies

− Mobility load balancing (MLB) optimization policies

− Automatic PCI optimization

− Automatic TA optimization

− Automatic neighboring cell optimization

− Detection and restoration of cells in outage

The M2000 also logs network optimization procedures and results and provides evaluation

reports.

Power-Saving Management

The M2000 provides power-saving management functions for base stations in LTE, GBSS,

WRAN, and SingleRAN networks. This meets power-saving requirements and reduces OPEX

for telecom operators.

The M2000 provides the following functions for eNodeBs:

− Scheduled BS power-on and power-off

− Intelligent RF channel shutdown

− TRX power amplifier intelligent shutdown

− Low-power consumption mode

− Dynamic adjustment of PA voltage

− Power consumption statistics before and after power-saving policies are applied

− Real-time query of power-saving policies applied on NEs

The M2000 provides the following functions for WRAN and SingleRAN BTSs:

− Power consumption statistics before and after power-saving policies are applied

The M2000 periodically sends the commands for adjusting working power levels to

GBTSs based on the charge remaining on batteries, predicted electricity, and predicted

power consumption. This significantly reduces GBTS power consumption and prolongs

GBTS service duration while ensuring the QoS. Accordingly, the configuration of

renewable energy is optimized and configuration costs are reduced.


Product Description



Page 27 of 47

MBTS Dynamic Power Sharing

The MBTS dynamic power-sharing function can be enabled when GSM and UMTS carriers

share the same power amplifier. This significantly improves the power usage and quality of

both the GSM network and the UMTS network when the busy hours of GSM and UMTS

traffic fall on different time segments or the traffic in GSM and UMTS networks is

unbalanced. The M2000 enables users to monitor the power usage of GSM and UMTS

carriers and the power sharing of carriers for the MBTS GU.

MBTS Dynamic Spectrum Sharing

Using the MBTS dynamic spectrum-sharing function, the M2000 divides the spectrums in the

GSM network into basic and shared spectrums. Shared spectrums can automatically switch

between GSM and UMTS networks. This function enables telecom operators to reuse their

spectrum resources, improving spectrum usage and data throughput.

NE Data Backup and Restoration

The M2000 provides the NE data backup and restoration function to ensure that NE data can

be restored by using backup data when a fault occurs on NE devices.

RTN Network Adjustment

Network adjustment is simplified by using a wizard, which reduces the requirements for

professional skills of OM engineers.

The following network adjustment scenarios are added:

Adding one or more nodes to a ring or chain topology

Expanding links

Before network expansion, network resources are verified. After network expansion,

network quality comparison report is provided. In this way, if network expansion fails,

services are automatically rolled back.

3.6 Service Management

MSC Pool/SGSN Pool/SingleSDB/CSCF Pool/MME Pool

With the M2000, users can group CN NEs such as MSC servers, SGSNs, GU-HLRs/

HSS9860/IMS-HSSs/SAE-HSSs/USCDBs, CSCFs, and USNs into resource pools for

resource sharing and service balancing. This improves hardware resource usage. In addition,

users can configure, monitor, and maintain the resource pools using the M2000 client.

RNC Pool/BSC Pool

The M2000 enables users to group NodeBs and RNCs into RNC pools or BTSs and BSCs

into a BSC pools. When the primary RNC or BSC is faulty, the services processed by the

NodeBs under the primary RNC or by the BTSs under the primary BSC are automatically

switched over to the secondary RNC or BSC. This reduces the impact on network services.

The M2000 also enables users to view the homing status of NodeBs or BTSs and monitor the

status of the RNC pool or BSC pool in the topology view in real time.


Product Description



Page 28 of 47

Dual-Homing

The dual-homing function provides a disaster recovery mechanism for the CN. This prevents

network services from being interrupted when softswitches break down or an exception

occurs. In this way, this function ensures uninterrupted communications. In addition, the

M2000 provides a dual-homing topology view and the functions of synchronizing

dual-homing configuration data and automatically checking data consistency. The purposes

are to facilitate routine dual-homing maintenance.

RAN Sharing Management

The RAN sharing management function is introduced to facilitate multi-operator device

sharing and reduce hardware costs. This function enables multiple telecom operators to share

one communications network. It achieves the cell-sharing mode through the sharing of

physical devices provided by Huawei. In addition, this function can ensure the privacy,

independence, and resource sharing of different telecom operators.

Authority-Based and Domain-Based Management on a Large Local Network

The management of a large local network has become a trend for networks where the bearer

part and the control part are separated. The authority-based and domain-based management

function is introduced to address this issue. Based on the centralized user management of the

M2000, this function can be used to divide objects on a large local network into domains so

that users and user operation rights can be controlled on a per domain basis. This ensures that

the operations of each user are controlled properly.

NGN Service Management

The NGN service management function of the M2000 enables users to configure the data of

softswitches and gateways and allocate services to devices and users.

NGN service management supports one-stop service provisioning without having to

repeatedly send commands to different NEs for subscription, which reduces O&M workload.


Product Description



Page 29 of 47

4 Configuration

The M2000 system can be installed on different types of servers. Telecom operators can select

appropriate servers according to the number of managed NEs.

Table 4-1 describes a typical server configuration.

The M2000 server supports the Solaris and SUSE Linux operating systems and uses either the

Sybase or Oracle database. The M2000 client can be installed on a PC or it can connect to the

M2000 system through the Citrix solution by using a web browser.

The single-server system based on the IBM platform manages devices only on IMS networks.

ATAE-based single-server and HA systems manage devices only on uBro and WiMAX networks.

Table 4-1 M2000 typical server configuration

Platform Networking Server Type Operating System and Database

Sun Single-server system Sun Sparc Enterprise

M4000 Server, or Sun

Sparc Enterprise M5000

Server

Solaris and Sybase

HA system

SLS system

Remote HA system

Emergency system

IBM Single-server system IBM x3850 X5 SUSE Linux and Oracle

ATAE Single-server system ATAE blades SUSE Linux and Oracle

HA system

Cluster system

The Sun Fire V890, Sun Fire E4900, Sun T5220, HP RX2660, HP RX7640 servers are no

longer delivered for installing M2000V200R012. Customers using servers configured with

any of the items described in Table 4-2 can still install and run M2000V200R012 on their

servers. Table 4-3 lists the minimum configuration items of the M2000 client.


Product Description



Page 30 of 47

Table 4-2 M2000 server minimum hardware requirements

Server Model CPU Memory

Hard Disk

Sun Fire V890 2 x 1.8 GHz 8 GB Local:6 x 146 GB

Diskarray:16 x 146 GB

Sun Fire E4900 4 x 1.8GHz 8 GB Local:2 x 146 GB


Sun T5220 1 x 1.2 GHz/4

Core

8 GB Local:4 x 146 GB

Sun M4000 2 x 2.4 GHz/8

Core



Sun M5000 4 x 2.4 GHz/16

Core



HP RX2660 2 x 1.4 GHZ/4

Core


HP RX7640 2 x 1.6 GHZ/4

Core



IBM x3850 X5 4 x 2.0GHz/8Core 32 GB Local:8 x 300 GB

ATAE

Cluster

OSMU

board

1 x 2.4GHz/4Core 16GB Local:2 x 300 GB

service

board

1 x 2.4GHz/6Core 48GB None

database

board

1 x 2.4GHz/6Core 48GB None

Table 4-3 M2000 client minimum requirements

Item Configuration

CPU E5300 or above

Memory 2 GB

Hard disk 160 GB

Accessories DVDRW-Integrated Ethernet adapter-Integrated audio

adapter-Built-in sound box-19'' LCD


Product Description



Page 31 of 47

Item Configuration

Operating system The following operating systems are supported:

Windows XP (32-bit)

Windows Vista (32-bit)

Windows 7 (32-bit) and (64-bit)

Windows 2003 Server(32-bit) and (64-bit)

Windows 2003 R2 Server(32-bit) and (64-bit)

Windows 2008 Server(64-bit)

Windows 2008 R2 Server(64-bit)

Application software M2000 client application software

If the M2000 client is installed with the Windows 7 Professional operating system, Internet Explorer 8

32-bit must be used as the Web browser, if necessary.


Product Description



Page 32 of 47

5 Operation and Maintenance

5.1 Overview

The M2000 provides a comprehensive system security solution, powerful data backup and

restoration, and efficient OM functions, all of which significantly improve O&M efficiency.

5.2 O&M Features

Comprehensive System Security Solution The M2000 provides comprehensive security hardening solutions for operating systems

and databases. These solutions meet the security requirements for operating systems and

databases.

The M2000 provides an OSS antivirus solution to protect the M2000 system against

viruses, worms, and spyware and to ensure the security of network O&M data. By

deploying the OfficeScan, this solution protects Windows-based M2000 clients, Citrix

clients, and Citrix servers against viruses. Meanwhile ServerProtect for Linux 3.0 and

Control Manager protects SUSE Linux-based M2000 servers against viruses.

The M2000 provides rights management, access control, and user monitoring functions

to ensure user security. The M2000 provides centralized OSS user management and

single sign-on (SSO) for the centralized authentication of multiple OSS applications. The

M2000 provides an LDAP-based, centralized user -management interface for telecom

operators to manage user information on their own user account management platforms.

The M2000 also provides an LDAP/RADIUS-based user authentication interface to

enhance the security of M2000 user management.

The M2000 provides transmission encryption to enhance the security of data

transmission between the M2000 client and server, between the M2000 server and NEs,

and between the M2000 and the NMS.

To ensure the security of subscribers' sensitive information such as IMSI, IMEI,

MSISDN, MAC address and IP address during troubleshooting, the M2000 provides the

anonymous policy to ensure that the sensitive information remains anonymous while

being transmitted between NEs and the M2000 and while being displayed on the M2000

during input and output.


Product Description



Page 33 of 47

Powerful Data Backup and Restore

The M2000 allows users to set flexible backup policies, based on which users can back up

M2000 applications and real-time data using periodical backup tasks. When the M2000

application real-time data is damaged or missing, users can restore the system quickly by

using the corresponding backup package. In addition, the M2000 provides dedicated backup

and restore tools, with which users can back up and restore the data of the entire operating

system.

Comprehensive System Monitoring

Users can monitor the status of all M2000 services and the usage of system resources on each

server in real time. Users can set thresholds for the system status. When the service is

interrupted or the usage of system resources reaches the threshold, the system generates an

alarm and quickly notifies users.

ATAE Cluster System Intelligent Management

All the boards except for the OSMU involved in the Advanced Telecommunications

Application Environment (ATAE) cluster system solution are not configured with any hard

disk. The boards without hard disks use the SAN Boot technology and boot the operating

system from the disk array. If a fault occurs on a board, the SAN Boot technology maps the

boot volume of the faulty board onto the substitute board to quickly resume the services.

OSMU intelligent hardware management includes the following functions:

Running on a separate board, the OSMU provides centralized maintenance by enabling

users to change IP addresses, time, routes, and user passwords in batches, and power the

boards off and on in batches. This improves maintenance efficiency.

The OSMU provides a device panel, which enables users to view the device status in real

time. The information about the board status displayed on the device panel in real time

provides references for board maintenance operations. Error information is included in

alarms and the alarms are automatically sent to the M2000 for uniform hardware alarm

monitoring.

The OSMU provides centralized task management, which enables users to query system

tasks in real time. By querying system tasks before performing a major operation, users

can learn the tasks being performed on the OSMU in advance to make a preliminary

decision on the major operation.

The OSMU provides a built-in function of centralized backup. With this function, data

on each service board is backed up to the backup media through the OSMU in a

centralized manner. The backup media for centralized backup through the OSMU is disk

array. In comparison with traditional backup mode, the centralized backup is faster, more

efficient, and more cost-effective.

The OSMU provides the automatic deployment of the operating system and database

software during the commissioning process.

Graphical System Maintenance

In addition to command-based routine commissioning and maintenance, the M2000 provides

the following web-based functions to reduce costs and improve OM efficiency:

Querying basic server information

Upgrading M2000 server software


Product Description



Page 34 of 47

Installing mediations

Starting and stopping relevant components by radio access technology

Clearing data

Inspection

Collecting fault locating information

Managing northbound interfaces

Centralized Task Management

Based on the centralized task management function, the M2000 performs routine maintenance

tasks related to the system.

System-scheduled tasks include database capacity management tasks, data export tasks,

synchronization tasks, and M2000 backup tasks.

User-scheduled tasks include NE license backup, network-wide NE backup, BSC/RNC

license activation, NodeB license allocation, health check, MML script execution, iSStar

script execution, software download, remote service upgrade verification, dual-homing

management, configuration report generation, configuration data synchronization (CME),

consistency check (CME), and data export from the current data area (CME).


Product Description



Page 35 of 47

6 Technical Specifications

6.1 Overview

This chapter describes the following system specifications:

Management capability

Reliability specifications

Compliant safety standards

EMC specifications

Environmental requirements

6.2 Management Capability

The management capability of the M2000 is calculated according to equivalent NEs, and the

NMS server is configured according to the number of equivalent NEs.

If the M2000 server hardware configurations are the same, the capability of managing NEs

varies according to the versions of the operating system and database on the M2000 server.

Table 6-1 describes the capability of the M2000.

Sun servers are installed with the Solaris10 operating system and the Sybase15 database. The

IBM PC server uses the SUSE Linux10 operating system and Oracle 11g database. Table 6-1

provides the NE management capability data that is calculated when the CME and M2000 are

deployed on one server. If the PRS and the M2000 are deployed on one server, the NE

management capability decreases by 30%.

Table 6-1 NE management capability of the M2000 (except SLS system)

Hardware Platform Management Capability (Number of Equivalent NEs)

2 CPU Sun M4000 ≤ 100

4 CPU Sun M4000 ≤ 190

4 CPU Sun M5000 ≤ 190

6 CPU Sun M5000 ≤ 270


Product Description



Page 36 of 47

Hardware Platform Management Capability (Number of Equivalent NEs)

8 CPU Sun M5000 ≤ 340

4 CPU IBM x3850 X5 ≤ 40

The management capability of an SLS system depends on the number of servers. Assume that

the management capability of one single server is 1, the total management capability is the

result of multiplying 1 by a coefficient if another server is added. This coefficient varies

according to the number of added servers. Table 6-2 shows an example of the management

capability of the full configuration M5000 server.

Table 6-2 Estimation of the management capability on NEs in the Sun SLS system(M5000)

Number of Servers Total Management Capability Coefficient

Single 1

2:1 1.6

3:1 2.3

4:1 3.6

5:1 4.8

6:1 6

The management capability of the ATAE cluster system depends on the number of blades in

use. The ATAE cluster system can manage a maximum of 800 equivalent NEs.

The number of equivalent NEs is determined by the following factors:

NE type

Performance measurement period

Performance measurement object

Performance measurement counter

The number of equivalent NEs for the same type of NEs varies according to performance

measurement requirements of users. For details, see the table of calculating equivalent NEs in

the iManager M2000 V200R012 Configuration Principles. Users can ask Huawei engineers to

analyze and calculate the number of equivalent NEs for the measurement unavailable in the

table.

6.3 Reliability Specifications

The reliability of the M2000 system varies according to the server model and the hardware

configuration.

Table 6-3, Table 6-4 and Table 6-5 describe the specifications for configuring the Sun-based

single-server system, HA system and SLS system.


Product Description



Page 37 of 47

Table 6-7 describes the specifications for configuring the IBM PC server.

Table 6-6 and Table 6-8 describe the specifications for configuring the ATAE HA system and

ATAE cluster server.

Table 6-3 Hardware reliability specifications (Sun-based single-server system)

Server Model MTBF (Hour) MTTR (Hour) Annual Mean Failure Time (Hour)

Availability

2 CPU M4000 64776 3.4376545 0.464867472 0.999946933

4 CPU M4000 57110 3.372342 0.51724692 0.999940954

4 CPU M5000 49238 3.3053582 0.588021329 0.999932874

6 CPU M5000 40980 3.3493621 0.715910545 0.999918275

8 CPU M5000 31629 3.3989344 0.941271176 0.999892549

Table 6-4 Hardware reliability specifications (Sun-based HA system)


Availability

2 CPU M4000 64776 0.61666667 0.083394291 0.99999048

4 CPU M4000 57110 0.68333333 0.104814015 0.999988035

4 CPU M5000 49238 0.71666667 0.127501292 0.999985445

6 CPU M5000 40980 0.81666667 0.174569484 0.999980072

8 CPU M5000 31629 0.96666667 0.267720801 0.999969438

Table 6-5 Hardware reliability specifications (Sun-based SLS system)


Availability

2 CPU M4000 50993.76207 0.616666667 0.10593324 0.999987907

4 CPU M4000 38385.24089 0.683333333 0.15594258 0.999982198

4 CPU M5000 32572.64978 0.716666667 0.19273415 0.999977998

6 CPU M5000 26077.96584 0.816666667 0.27432262 0.999968685

8 CPU M5000 20382.88129 0.966666667 0.41542696 0.999952577


Product Description



Page 38 of 47

Table 6-6 Hardware reliability specifications (ATAE HA system)

MTBF (Hour) MTTR (Hour) Annual Mean Failure Time (Hour)

Availability

244140 0.178679623 0.006411208 0.999999268

Table 6-7 Hardware reliability specifications (IBM PC server)

Server Configuration MTBF (Hour) Annual Mean Failure Time (Hour)

Availability

4 CPU IBM x3850 X5 86021 0.70956 0.999919

Table 6-8 Hardware reliability specifications (ATAE cluster system with typical M2000

configuration)

MTBF (Year) MTBF (Hour) MTTR (Hour) Annual Mean Failure Time (Minute)

Availability

62.72 549482 3 2.87 0.9999945

6.4 Compliant Safety Standards

The M2000 complies with the following safety standards:

IEC 60950-1

IEC/EN41003

EN 60950-1

UL 60950-1

CSA C22.2 No 60950-1

AS/NZS 60950-1

BS EN 60950-1

IS 13252

GB4943

6.5 EMC Specifications

The M2000 complies with the following Electromagnetic Compatibility (EMC) standards:

CISPR22 Class A

EN55022 Class A


Product Description



Page 39 of 47

EN50024

ETSI EN 300 386 Serial Class A

ETSI EN 301 489 Class A

ICES 003 Class A

AS/NZS CISPR22 Class A

GB9254 Class A

VCCI Class A

CNS 13438 Class A

6.6 Environmental Requirements

Environmental requirements include the requirements for the storage, transportation, and

operation of the equipment.

The environmental requirements comply with the following standards:

ETS 300019 "Equipment Engineering (EE); Environmental conditions and environmental

tests for telecom equipment"

IEC 60721 "Classification of environmental conditions"

6.6.1 Storage Environment

This section describes the climatic, waterproof, biological, air purity, and mechanical stress

requirements for storing the equipment.

Climatic Requirements

Table 6-9 lists the climatic requirements for equipment storage.

Table 6-9 Climatic requirements for equipment storage

Item Range

Temperature -20°C (-4 ºF) to +60°C (140 ºF)

Relative humidity 8% to 93%

Altitude 5,000 m (16404.20 ft.)

Air pressure 70 kPa to 106 kPa

Solar radiation 1,120 W/s²

Heat radiation 600 W/s²

Wind speed 30 m/s


Product Description



Page 40 of 47

Waterproof Requirements

The equipment must be stored in a room where:

Water does not accumulate on the ground or fall on the package.

Water sources such as a hydrant and air-conditioner are placed at a distance.

If the equipment is placed outdoors, ensure that:

The package is intact.

Waterproof measures are taken to prevent water penetration.

Water does not accumulate on the ground or flow into the package.

The package is not exposed directly to sunlight.

Biological Requirements

Ensure that the place for equipment storage is free of:

Fungus or mildew

Rodents, such as rats

Air Purity Requirements

The air must be free of explosive, conductive, magnetic conductive or corrosive dust.

The density of physically active materials must comply with the requirements listed in Table

6-10.

Table 6-10 Storage requirements for physically active materials

Physically Active Material Unit Density

Suspended dust mg/m³ 5.00

Falling dust mg/m²·h 20.0

Sand mg/m³ 300

NOTE

Suspended dust: Diameter 75 m

Falling dust: 75 m Diameter 150 m

Sand: 150 m Diameter 1 000 m

The density of chemically active materials must comply with the requirements listed in Table

6-11.

Table 6-11 Storage requirements for chemically active materials

Chemically Active Material Unit Density

SO2 mg/m³ 0.30


Product Description



Page 41 of 47


H2S mg/m³ 0.10

NO2 mg/m³ 0.50

NH3 mg/m³ 1.00

Cl2 mg/m³ 0.10

HCl mg/m³ 0.10

HF mg/m³ 0.01

O3 mg/m³ 0.05

Mechanical Stress Requirements

Table 6-12 lists the mechanical stress that the equipment can endure during storage.

Table 6-12 Storage requirements regarding mechanical stress

Item Subitem Range

Sinusoidal vibration Offset 7.0 mm (0.28

in.)

None

Accelerated speed None 20.0 m/s²

Frequency range 2 Hz to 9 Hz 9 Hz to 200

Hz

Unsteady impact Impact response spectrum II 250 m/s²

Static payload 5 kPa

NOTE

Impact response spectrum: refers to the maximum acceleration response curve generated by the

equipment under specified excitation. Impact response spectrum II means that the duration of semi-sine

impact response spectrum is 6 microseconds.

Static payload: refers to the capability of the equipment to bear the pressure from the top when it is

packed in the normal pile-up method.

6.6.2 Transportation Environment


requirements for transporting the equipment.


Table 6-13 lists the climatic requirements for transporting the equipment.


Product Description



Page 42 of 47

Table 6-13 Climatic requirements for transporting the equipment

Item Range

Temperature -20 °C (-4 ºF) to 60 °C (140 ºF)

Humidity 8% to 93%

Altitude 5,000 m (16404.20 ft.)


Solar radiation 1,120 W/s²

Heat radiation 600 W/s²

Wind speed 30 m/s

Waterproof Requirements

Before transporting the equipment, ensure that:

The package is intact.

Waterproof measures are taken to prevent water penetration.

There is no water in the vehicle.


Ensure that the vehicle is free of:

Fungus or mildew

Rodents such as rats


The air must be free of explosive, conductive, magnetic conductive or corrosive dust.


6-14.

Table 6-14 Requirements for physically active materials in the transportation environment

Physically Active Material Unit Density

Suspended dust mg/m³ No requirement

Falling dust mg/m²·h 3.0

Sand mg/m³ 100


Product Description



Page 43 of 47

NOTE

Suspended dust: diameter 75 m

Falling dust: 75 m diameter 150 m

Sand: 150 m diameter 1,000 m


6-15.

Table 6-15 Requirements for physically active materials in the transportation environment


SO2 mg/m³ 0.30

H2S mg/m³ 0.10

NO2 mg/m³ 0.50

NH3 mg/m³ 1.00

Cl2 mg/m³ 0.10

HCl mg/m³ 0.10

HF mg/m³ 0.01

O3 mg/m³ 0.05


Table 6-16 lists the mechanical stress that the equipment can endure during transportation.

Table 6-16 Transportation requirements regarding mechanical stress

Item Subitem Range

Sinusoidal

vibration

Offset 7.5 mm (0.3

in.)

N/A --

Accelerated speed N/A 20.0 m/s² 40.0 m/s²

Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500 Hz

Random

vibration

Spectrum density of accelerated

speed

10 m²/s³ 3 m²/s³ 1 m²/s³

Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500 Hz

Unsteady

impact

Impact response spectrum II 300 m/s²

Static payload 10 kPa


Product Description



Page 44 of 47

Item Subitem Range

NOTE

Impact response spectrum: refers to the maximum acceleration response curve generated by the equipment under specified

impact excitation. Impact response spectrum II means that the duration of semi-sine impact response spectrum is 6

microseconds.

Static payload: refers to the capability of the equipment to bear the pressure from the top when it is packed in the normal pile-up

method.

6.6.3 Operating Environment


requirements for operating the equipment.


Table 6-17 and Table 6-18 list the climatic requirements for operating the equipment.

Table 6-17 Temperature and humidity requirements for operating the M2000

Temperature Relative Humidity

5°C (41 ºF) to 35°C (95 ºF) 20% to 80%

NOTE

The values are measured 1.5 meters above the floor and 0.4 meters in front of the equipment, without

protective panels in front of or behind the cabinet.

Safe operation refers to continuous operation for not more than 48 hours or operation of not more than

15 days accumulated in a year.

Table 6-18 Other climatic requirements for the operation of the M2000

Item Range

Altitude 4,000 m (13,123.36 ft.)


Solar radiation 700 W/m²

Heat radiation 600 W/m²

Wind speed 1 m/s


Ensure that the place for storing the equipment is free of:

Fungus or mildew


Product Description



Page 45 of 47

Rodents such as rats


The air must be free of explosive, conductive, magnetic, conductive, or corrosive dust.


6-19.

Table 6-19 Operation requirements for physically active materials

Physically Active Material

Unit Density

Dust particles Particles/m³ 3 x 104

(Ensure that the dust accumulated for

three days on the desktop is not visible.)

NOTE

Dust particles: diameter 5 m


6-20.

Table 6-20 Operation requirements for chemically active materials


SO2 mg/m³ 0.20

H2S mg/m³ 0.006

NH3 mg/m³ 0.05

Cl2 mg/m³ 0.01


Table 6-21 lists the mechanical stress that the equipment can endure during its operation.

Table 6-21 Operation requirements regarding mechanical stress

Item Subitem Range

Sinusoidal

vibration

Offset 3.5 mm (0.14 in.) N/A

Accelerated speed N/A 10.0 m/s²

Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz


Product Description



Page 46 of 47

Unsteady

impact

Impact response

spectrum II 100 m/s²

Static payload 0

NOTE

Impact response spectrum: refers to the maximum acceleration response curve generated by the

equipment under specified impact excitation. Impact response spectrum II means that the duration of

semi-sine impact response spectrum is 6 ms.

Static payload: refers to the capability of the equipment to bear the pressure from the top when it is

packed in the normal pile-up method.


Product Description



Page 47 of 47

A Acronyms and Abbreviations

Abbreviation Expansion

3GPP 3rd Generation Partnership Project

ATAE Advanced Telecommunications Application Environment

CORBA Common Object Request Broker Architecture

EMC Electromagnetic Compatibility

ETS European Telecommunication Standards

ETSI European Telecommunications Standards Institute

IEC International Electrotechnical Commission

LTE Long Term Evolution

MML Man-Machine Language

MTBF Mean Time Between Failures

MTTR Mean Time To Repair

NMS Network Management System

NGN Next Generation Network

NTP Network Time Protocol

OPEX Operation Expenditure

PC Personal Computer

RTN Radio Transmission Node

SLS Multi-Server Load-Sharing

SNMP Simple Network Management Protocol

STP Signaling Transfer Point

Documents

IManager M2000 V200R012 Product Description(GSM&UMTS&LTE) 03(20120530)[1]