M2000 Product Description

iManager M2000 V200R011 Product
Description
Issue
V1.1
Date
2011-01-15
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. 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 a 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:
support@huawei.com
Issue V1.1 (2011-01-15)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Page 2 of 46
iManager M2000 V200R011 Product Description
Contents
1 Introduction.................................................................................................................................... 5
1.1 Positioning ....................................................................................................................................................... 5
1.2 Managed NEs ................................................................................................................................................... 5
1.2.1 WRAN NEs ............................................................................................................................................ 5
1.2.2 GBSS NEs............................................................................................................................................... 6
1.2.3 SingleRAN NEs ...................................................................................................................................... 6
1.2.4 GU CN NEs ............................................................................................................................................ 6
1.2.5 LTE-SAE NEs ......................................................................................................................................... 7
1.2.6 uBro NEs................................................................................................................................................. 7
1.2.7 IMS NEs ................................................................................................................................................. 7
1.2.8 Wireless Bearer Network Devices .......................................................................................................... 8
1.2.9 Auxiliary Networking Devices ................................................................................................................ 8
1.3 Benefits ............................................................................................................................................................ 8
2 Architecture .................................................................................................................................. 10
2.1 Overview ........................................................................................................................................................ 10
2.2 Hardware Structure ........................................................................................................................................ 10
2.3 Software Structure .......................................................................................................................................... 11
2.4 External Interfaces ......................................................................................................................................... 11
3 Products and Application Scenarios ....................................................................................... 13

3.1 Overview ........................................................................................................................................................ 13
3.2 OM Solutions ................................................................................................................................................. 13
3.3 Network Deployment ..................................................................................................................................... 19
3.4 Network Monitoring ....................................................................................................................................... 21
3.5 Network Adjustment ...................................................................................................................................... 24
3.6 Service Management ...................................................................................................................................... 26
4 Configuration............................................................................................................................... 27
5 Operation and Maintenance ..................................................................................................... 30
5.1 Overview ........................................................................................................................................................ 30
5.2 OM Features ................................................................................................................................................... 30
6 Technical Specifications ............................................................................................................ 33

6.1 Overview ........................................................................................................................................................ 33
Issue V1.1 (2011-01-15)

Page 3 of 46

6.2 Management Capability ................................................................................................................................. 33
6.3 Reliability Specifications ............................................................................................................................... 35
6.4 Compliant Safety Standards ........................................................................................................................... 36
6.5 EMC Specifications ....................................................................................................................................... 37
6.6 Environmental Requirements ......................................................................................................................... 37
6.6.1 Storage Environment ............................................................................................................................. 37
6.6.2 Transportation Environment ................................................................................................................. 40
6.6.3 Operating Environment ......................................................................................................................... 42
7 Acronyms and Abbreviations ................................................................................................... 45
Issue V1.1 (2011-01-15)

Page 4 of 46
Introduction
1.1 Positioning
This document is applicable to the iManager M2000 Mobile Element Management System
V200R011.
The iManager M2000 Mobile Element Management System (hereinafter referred to as the
M2000) manages Huawei mobile network elements (NEs) in a centralized manner. The NEs
include WRAN NEs, GBSS NEs, SingleRAN NEs, GU core network (CN) NEs, LTE-SAE
NEs, uBro NEs, and IMS NEs. In addition, the M2000 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.
The M2000 provides centralized operation and maintenance (OM) functions for the Huawei
mobile element management solution. The M2000 adopts a modular design where the
modules communicate with each other through the CORBA bus. In addition, the M2000
provides mediations for connecting NEs of various types.
The M2000 also provides external interfaces for interoperability with non-Huawei systems.
1.2 Managed NEs

1.2.1 WRAN NEs
The M2000 manages the following WRAN NEs:
Radio network controller: RNC
Multi-mode base station controller: BSC6900 UMTS
NodeB
IP clock server
Transmission gateway: TGW1000
Issue V1.1 (2011-01-15)

Page 5 of 46
1.2.2 GBSS NEs

The M2000 manages the following GBSS NEs:
Base station controller: BSC
Base station controller: GT800BSC
Base station controller: BSC6000
Multi-mode base station controller: BSC6900 GSM
Base transceiver station: BTS
IP clock server
Transmission gateway: TGW1000
Packet control unit: PCU35
1.2.3 SingleRAN NEs

The M2000 manages the following SingleRAN NEs:
Multi-mode base station controller (GU): BSC6900 GU
Multi-mode base station (GU): MBTS GU
Multi-mode base station (GL): MBTS GL
Multi-mode base station (UL): MBTS UL
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: MSC
Mobile switching center server: MSC server
Home location register: HLR36
Home location register: HLR9820
Home location register (data node): HLR-DC
Home location register (service node): HLR-SC
Media gateway: MGW
Fixed-mobile convergence media gateway: FMC MGW
Charging gateway: CG
Signaling gateway: SG7000
Interworking function: IWF
Issue V1.1 (2011-01-15)

Page 6 of 46
MSCs are categorized as follows:
MSC based on the 32-module architecture, also called MSC33 or G3
iMSC based on the 128-module architecture, also called MSC60, VMSC60, IGATE, or G6
tMSC in the GT800 trunk communication system, which adopts the iMSC architecture
rMSC in the GSM-R railway dispatch system, which adopts the iMSC architecture
1.2.5 LTE-SAE NEs

The M2000 manages the following LTE-SAE NEs:
eNodeB
SAE-home subscriber server: SAE-HSS
Unified serving node: USN
Unified gateway: UGW
Charging gateway: CG
Resource and policy control system: RM (RM9000)
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
IP security gateway (IPSec gateway)
AP management system: AP Manager

The M2000 does not directly manage APs. The alarm and performance data of APs is reported to the
M2000 through the AP Manager. Users can query the data on the M2000.
1.2.7 IMS NEs

The M2000 manages the following IMS NEs:
Media gateway: MGW
Session border controller: SBC (SE2300)
Unified access controller: UAC (UAC3200)
Home subscriber server: HSS (HSS9820)
Calling session control function: CSCF (CSC3300)
Resource and policy control system: RM (RM9000)
Charging collection function: CCF (iCG9815)
Advanced telephony server: ATS (ATS9900)
Multimedia exchange server: MEDIAX (MediaX3600)
IP Centrex: IPCTRX (ETAS9960)
Multimedia resource function controller: MRFC (MRC6600)
Issue V1.1 (2011-01-15)

Page 7 of 46
Multimedia resource function processor: MRFP (MRP6600)
USC database: USCDB
Attachment information management system: AIM (AIM6300)
Service provisioning gateway (SPG) (SPG2800)
Unified gateway controller: UGC (UGC3200)
1.2.8 Wireless Bearer Network Devices

The M2000 manages the following wireless bearer network devices:
Metro1000V3
OSN3500
RTN
BITS
1.2.9 Auxiliary Networking Devices

The M2000 manages the following auxiliary networking devices:
NE08-series routers
Eudemon-series firewalls
S-series LAN switches
AR46-series LAN switches
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 CG
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 continuous efforts that telecom operators have made for network OM and inherits
the existing OM experience.
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
uBro solution, CN, 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.
Issue V1.1 (2011-01-15)

Page 8 of 46
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.
To meet the demand, 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 implements the
smooth expansion of networks. During network expansion, users can enhance the
management capability of the M2000 by adding a server in the SLS system or adding a
service blade in the ATAE cluster system. This protects telecom operator's hardware
investments and reduces network deployment costs.
Efficient and Intelligent Functions Help 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 the configuration data
of cells with that of the baseline cell. This facilitates data configuration of the entire radio
access network. The CME enables users to create sites in batches remotely, expand network
capacity quickly, optimize a network efficiently, and reparent base stations easily. This
improves the configuration efficiency and accuracy.
The iSStar enhancement maintenance platform enables OM engineers to customize the
service process by editing programs. Thus, the M2000 can automatically handle OM tasks in
batches.
In addition, the M2000 provides a series of featured functions, including the network health
check, remote upgrade and batch upgrade of NEs, automatic planning of base stations,
automatic optimization of neighboring cell relationships, remote commissioning of base
stations, device panel, maintenance-mode alarm setting, and RAN sharing management.
These functions greatly improve the working efficiency of OM engineers and thus reduce the
total cost of operation (TCO).
Issue V1.1 (2011-01-15)

Page 9 of 46
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

A typical M2000 system 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
Issue V1.1 (2011-01-15)

Page 10 of 46
2.3 Software Structure

As shown in Figure 2-2, the M2000 software is classified into the following types:
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, and queries M2000 configuration data.
CORBA security interface

Through the CORBA security interface, the NMS manages M2000 users and user rights,
such as the rights for creating users. The NMS also maintains user information, and
queries and modifies user attributes.
Issue V1.1 (2011-01-15)

Page 11 of 46
File interface
The M2000 saves alarm data, performance data, configuration data, and LTE tracing data
as .txt files. Through the file interface, the NMS obtains and processes these files. The
performance file interface supports multi-NMS access and northbound user management.
Performance files are stored on a per telecom operator basis.
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. Therefore,
data planning, modification, and activation are automatically performed through the
configuration file interface. The configuration file interface is applicable to OM
scenarios such as site creation, site relocation, network parameter optimization, and
optimization of neighboring cell relationships.
Alarm streaming interface

The M2000 forwards processed NE alarms to the NMS in the form of character stream.
SNMP interface
Through the SNMP alarm interface, the M2000 forwards processed alarms to the NMS
in the form of text. The SNMP interface supports 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. Through this interface, the NMS can operate and
maintain the related NEs by running MML commands.
Issue V1.1 (2011-01-15)

Page 12 of 46
Products and Application Scenarios
3.1 Overview
The M2000 provides various OM 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.
SLS, remote HA, and emergency systems are developed based on the Sun platform.
The local HA system is supported by Sun, HP, and ATAE platforms.
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. Thus, the costs for operating and maintaining multiple M2000 systems are reduced.
Figure 3-1 shows the physical structure of an M2000 SLS system.
Issue V1.1 (2011-01-15)

Page 13 of 46
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.
Management
console
The management console, generally a Sun Netra240 server, provides

local management and maintenance for M2000 servers.
ATAE Cluster Solution

Developed on the ATAE platform, the ATAE cluster system allows the deployment of multiple
blades to provide powerful management capability.
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
Issue V1.1 (2011-01-15)

Page 14 of 46
OSMU intelligent management
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
and the PRS, 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
An ATAE subrack can be configured with 14 blades. The typical

configuration in the scenario where the M2000 is deployed in an
ATAE subrack is as follows:
The OSMU monitors and manages the entire ATAE cluster system
and can be accessed through a Web browser.
Two switching blades provide the functions of a switch.
One master service blade, one slave service blade, one standby
blade, and one database blade form the M2000 system.
One standby database blade provides the hot backup service for the
database blades of the M2000 and the PRS.
Three reserved blades are used for capacity expansion.
Three reserved blades are used for deploying both the PRS and the
M2000.
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.
Issue V1.1 (2011-01-15)

Page 15 of 46
The active and standby servers are placed together 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 gain access to 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 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 losses caused by power failures, earthquakes, fires, wars, tsunamis, and mudflows.
Thus, remote protection is implemented on both the M2000 servers and the disaster recovery
capability of the M2000 is improved.
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 gain access to different disk arrays. Figure 3-4 shows the physical structure
of a remote HA system.
Issue V1.1 (2011-01-15)

Page 16 of 46
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. The emergency system is applicable to the M2000 single-server 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 N (no more than four) M2000 single-server systems or N
(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 a primary system, it
cannot take over the services of any other primary system.
Issue V1.1 (2011-01-15)

Page 17 of 46
Figure 3-5 shows the physical structure of the emergency system that backs up N M2000
single-server systems. Figure 3-6 shows the physical structure of the emergency system that backs
up an M2000 SLS system.
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.
Issue V1.1 (2011-01-15)

Page 18 of 46
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, only one server is 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 where the M2000 client is running
Lowering the requirements for the operating system environment of the PC where the
M2000 client is running
Network Time Synchronization Solution

The M2000 supports the Network Time Protocol (NTP)/Simple Network Time Protocol
(SNTP) so that the time of NEs on the entire network is synchronized.
The clock source and NTP server are provided by a telecom operator, and the M2000
server functions as the NTP client or intermediate NTP server. This ensures that the
M2000 can synchronize time with the upper-layer NTP server and provide a clock source
for managed NEs to synchronize.
A dedicated clock server is provided, which can be installed in the cabinet of the M2000
server. In addition, two NTP service channels working in active/standby mode are
provided. The clock source server can be deployed as the top NTP clock server as a
medium NTP click server.
Veritas System Backup and Restore Solution

The M2000 adopts the Veritas system backup and restore solution. This solution enables users
to back up and restore the key data on the entire network, for example, the operating system
data of the M2000 server, applications, key files, data stored in the database, and key 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, upgrade NE mediation patches, or
uninstall NE mediations 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.
Issue V1.1 (2011-01-15)

Page 19 of 46
Remote and Centralized Initial Configuration

The M2000 provides the remote and centralized initial configuration function during initial
network configuration.
Through a GUI
The M2000 provides the CME for users to configure the GSM, WRAN, LTE, and SRAN
NEs. The M2000 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 issue 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 issue MML commands in debugging mode or task
mode. When issuing commands in debugging mode, users can check script execution
information and execution result of each command in real time. When issuing commands
in task mode, users only need to select a required script and then 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 microwaves 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.
Base Station Auto-Deployment

The M2000 provides the auto-deployment function for NodeBs, GBTSs, MBTS (GU, GL,
UL), and eNodeBs. 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 auto-deployment
function implements automatic remote commissioning, thus avoiding site operation and
maintenance.
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 some radio parameters of BTS3902E UMTS and
BTS3902E LTE based on the auto-deployment function.
Issue V1.1 (2011-01-15)

Page 20 of 46
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
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. In addition, the M2000
supports the following operations on license information, which help users know and allocate
license resources in real time:
Query
Periodic synchronization
Manual synchronization
Scheduled check
Threshold monitoring
Scheduled export
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. After users disable a license, the 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
learn about and monitor the running status of the entire network.
Performance Monitoring
The performance monitoring function enables users to learn about device security, device
running status, and system resource usage in time. This function can meet diversified
requirements in different scenarios, for example, network deployment, routine network
maintenance, and special scenarios such as holidays and festivals. The data obtained from
Issue V1.1 (2011-01-15)

Page 21 of 46
performance monitoring can be used for further analysis, which provides a basis for the
measurement, design, and operation management of communications networks.
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 solve 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. In the alarm monitoring window, users can browse, query, and collect statistics on
maintenance mode alarms by maintenance mode to meet user requirements in specified
scenarios. In common OM scenarios, 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 through short message
services (SMSs) and emails to ensure that the information can be transmitted in time
even when the site is unmanned.
To help users to quickly locate the required information in 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, alarm/event
occurrence time, alarm/event severity, and alarm/event 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, and filtering maintenance
mode alarms.
To help users to 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 the
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
Issue V1.1 (2011-01-15)

Page 22 of 46
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.
To help users to query configuration data, the configuration query function enables users
to obtain the configuration status of the network in real time. The configuration data
provides a basis 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
operating status and management status of objects such as cells, boards, and links on the
network in time.
The M2000 generates link status reports on a scheduled basis. This helps users identify
link exceptions when links are disconnected or the link 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 user tracing, cell tracing, and interface tracing functions through GUIs
and supports the centralized tracing management over the entire network. The FARS helps
OM engineers to locate call-related faults and network faults, optimize the network coverage,
and solve interconnection problems. This reduces the OM costs for telecom operators. A
tracing server is deployed on the LTE network to trace a large amount of tracing data.
The device panel displays the board structures of physical devices on a GUI. It also displays
board status and alarm information in real time. The M2000 displays the relationships
between RRUs for distributed base stations in a topology view. This helps users to locate
problems.
The GBSS and WRAN antenna fault detection systems enable users to identify and locate
faults related to GBSS and WRAN antenna line devices (ALDs).
An LTE service aware unit (SAU) server is added to the M2000 system to enable
troubleshooting, system performance management, and self-organizing system (SON)
functions in the LTE network. This server collects and stores tracing data of network devices
and provides a data access interface for operations support systems (OSSs) of telecom
operators. The LTE SAU server and the M2000 are deployed in the same equipment room and
their IP addresses are in the same network segment. These servers belong to the same security
domain, and no firewall is deployed between them. The LTE SAU server is an HP server. An
M2000 system (Sun-based single-server system, HA system, or SLS system) is configured
with an LTE SAU server. If the LTE SAU server is an HP DL580 G5 server or a server with
higher configuration, this server can collect tracing data of up to 2,000 eNodeBs (assuming
that each eNodeB has three cells) at a time. The LTE SAU server can store tracing data for up
to seven days. Data whose storage duration exceeds seven days will be deleted.
Issue V1.1 (2011-01-15)

Page 23 of 46
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 the repeated and effort-consuming routine maintenance 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 the bearer network management function such as the quality of service
(QoS) dialing test for users to check whether a network fault or a device fault is related to data
transmission. This facilitates fault locating and improves troubleshooting efficiency.
WRAN QoS detection: 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 simulating the process of
delivering service packets from NEs.
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 Layer 2 Ethernet.
LTE QoS detection: The M2000 provides the functions of monitoring IP link alarms and
key performance counters and testing IP links.
3.5 Network Adjustment

Configuration Adjustment
The M2000 provides the remote and centralized configuration adjustment function for
network troubleshooting and network optimization.
Through a GUI
The M2000 provides the CME for users to adjust the configuration of the GSM, WRAN,
LTE, and SRAN NEs. The M2000 provides the basic configuration function for all the
CS NEs on the CN. Users can adjust configuration data on a GUI.
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
provides the functions of automatically optimizing the frequencies, capacities, and
neighboring cell relationships for GSM Compact BTSs.
The M2000 provides the following functions for eNodeBs:
Issue V1.1 (2011-01-15)
Mobility Robust Optimization (MRO) optimization policies
Inter-Cell Interference Co-ordination (ICIC) optimization policies

Page 24 of 46
Mobility Load Balancing (MLB) optimization policies
Automatic PCI optimization
Automatic TA and RF optimization
The M2000 records network optimization steps and results in logs during network
optimization. In addition, the M2000 provides optimization evaluation reports.
Power-Saving Management
The M2000 provides power-saving management functions for base stations in LTE, GBSS,
WRAN, and SRAN 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
Statistical collection on power consumption 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 NodeBs and SRAN BTSs:
Statistical collection on power consumption before and after power-saving policies

are applied
The M2000 periodically generates working power levels of GBTSs based on the
available electricity of batteries, predicted electricity, and predicted power consumption.
This significantly reduces power consumption of GBTSs and prolongs GBTS service
duration while ensuring the QoS. Accordingly, configuration of renewable energy is
optimized and configuration costs are reduced.
MBTS Dynamic Power Sharing

The M2000 provides the MBTS dynamic power-sharing function. This function can be
enabled when GSM and UMTS carriers share the same power amplifier. This significantly
improves power usage and quality of both the GSM network and the UMTS network in
scenarios where 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 spectrums and shared spectrums. Shared spectrums can be
automatically switched between GSM and UMTS networks. This function enables telecom
operators to reuse their spectrum resources; thus improving spectrum usage and data
throughput.
Issue V1.1 (2011-01-15)

Page 25 of 46
NE Data Backup and Restoration

The M2000 provides the NE data backup and restoration function to ensure that NE data can
be restored when a fault occurs in NE devices or when an exception occurs in case of NE
upgrade and network adjustment.
3.6 Service Management

MSC Pool/SGSN Pool/USC Pool
Through the M2000, users can group CN NEs such as MSC servers, SGSNs, and USCs 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 through the
M2000 client.
RNC Pool/BSC pool

The M2000 enables users to group NodeBs and RNCs or BTSs and BSCs into an RNC pool
or a BSC pool. 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 impacts 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.
Dual-Homing
The dual-homing function provides a disaster recovery mechanism for the CN. It 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, it can ensure the privacy, independency,
and sharing of resources from different telecom operators.
Authority-Based and Domain-Based Management on a Large Local Network

The management of a large local network becomes a trend on a network 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 the objects on a large local network into different
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.
Issue V1.1 (2011-01-15)

Page 26 of 46
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 the typical server configuration.
The M2000 server supports the Solaris and SUSE Linux operating systems. It uses the Sybase
or Oracle database. The M2000 client can be installed on a PC or connected to the M2000
system through the Citrix solution by using a web browser.
Table 4-2 lists the minimum hardware requirements of the M2000 server. Table 4-3 lists the
minimum configuration items of the M2000 client.
ATAE-based single-server and HA systems manage devices only on the uBro and WiMAX
networks.
Table 4-1 M2000 server configuration

Platform
Networking
Server Type
Operating
System and
Database
Sun
Single-server system
Sun Sparc Enterprise

T5220 server (does not
support the remote HA
system and SLS
system), Sun Sparc
Enterprise M4000
Server, or Sun Sparc
Enterprise M5000
Server
Solaris and Sybase
HP rx2660 (does not

support the HA system)
or
SUSE Linux and

Oracle
HA system
SLS system
Remote HA system
Emergency system
HP
HA system
HP rx7640
ATAE
Issue V1.1 (2011-01-15)
One blade
HA system
Two blades

Page 27 of 46
Platform
Operating
System and
Database
Networking
Server Type
Cluster system
Four blades (one master

service blade, one slave
service blade, one
standby blade, and one
database blade)
Table 4-2 M2000 server minimum hardware requirements

Server Model
CPU
Memory
Hard Disk
Sun Netra240
2 x 1.5 GHz
8 Gb
Local:2 x 146 GB
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

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
16 Gb

146 GB
Sun M5000
4 x 2.4 GHz/16
Core
32 Gb

146 GB
HP RX2660
2 x 1.4 GHZ/4
Core
8 Gb
Local:4 x 146 GB
HP RX7640
2 x 1.6 GHZ/4
Core
16 Gb

146 GB
The Sun Netra240, Sun Fire V890, Sun Fire E4900, Sun T5220, HP RX2660, HP RX7640 servers are no
longer delivered for installing M2000V200R011. If the customer is using these servers whose
configurations include the items described in Table 4-2, M2000V200R011 can still be installed on these
servers and can run properly.
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
Operating system
Windows XP professional (or a later version)
Issue V1.1 (2011-01-15)

Page 28 of 46
Item
Configuration
Application software
M2000 client application software
Issue V1.1 (2011-01-15)

Page 29 of 46
Operation and Maintenance
5.1 Overview
The M2000 provides functions such as powerful data backup and restoration, comprehensive
system monitoring, and flexible NE upgrade and mediation. These functions significantly
improve OM efficiency.
5.2 OM 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.
To protect the M2000 system against attacks of Trojan horse programs and viruses, the
M2000 provides an antivirus solution for the Linux system. This solution ensures the
security of network OM data. A server functioning as an antivirus server is added to the
network where the M2000 system is deployed. The antivirus software is deployed on
each M2000 server.The antivirus server communicates with the supplier of the antivirus
software through a firewall. In this way, the antivirus server can obtain the latest virus
library and antivirus software upgrade package and then deliver them to each M2000
server.
To enhance the security management feature, the M2000 provides the rights management,
access control, and user monitoring functions. In addition, the OSS-related systems
support single sign-on (SSO). With this feature, a user logs in once and gains access to
all OSS-related systems without being prompted to log in again at each of them.
To ensure secure data transfer between the M2000 server and NEs and between the
M2000 server and the M2000 client, the M2000 provides functions such as the digital
certificate authentication and data transfer security and encryption.
Powerful Data Backup and Restore

The M2000 allows users to set flexible backup policies, based on which users can back up
M2000 applications and data using periodical backup tasks. When the M2000 application data
is damaged or missing, users can restore the system quickly by using the corresponding
Issue V1.1 (2011-01-15)

Page 30 of 46
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 set monitored objects and thresholds on the M2000 to monitor the status of all the
M2000 services and the usage of the system resources on each server in real time. In the case
of service interruption or when the usage of system resources reaches a threshold, the system
generates an alarm and quickly notifies users of the fault.
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
Running on a separate board, the OSMU provides centralized maintenance by enabling

users to change IP addresses, time, routes, user passwords in batches, and power on and
power off the boards in batches. This improves the 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 the function of centralized task management, which enables users
to query the system tasks in real time. By querying the system tasks before performing a
major operation, users can learn the operation and maintenance performed by 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 maintenance and device check, the M2000 provides the
following web-based functions:
Query of basic information about cluster status, database status, and service status
Alarm maintenance tool
Mediation installation
Data clearance
Inspection (OMC Autostar)
Information collection (Trace Collection)
Service startup and stop
Issue V1.1 (2011-01-15)

Page 31 of 46
Startup and stop of relevant component services by network technology
Automatic upgrade of the M2000 server and automatic patch installation
Northbound interface management
Centralized Task Management

Based on the centralized task management function, the M2000 performs routine scheduled
operations such as data synchronization, log synchronization, scheduled data backup, data
capacity management, and file export, thus automating routine OM tasks.
Issue V1.1 (2011-01-15)

Page 32 of 46
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 single-server system and HA system.
Sun servers are installed with the Solaris10 operating system and the Sybase15 database. HP
servers use the SUSE10 operating system and the Oracle10g 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 (single-server system and HA system)
Hardware Platform
Management Capability (Number of Equivalent NEs)
1 CPU Sun T5220(8C)
45
2 CPU Sun M4000
100
4 CPU Sun M4000
190
4 CPU Sun M5000
190
Issue V1.1 (2011-01-15)

Page 33 of 46
Hardware Platform
Management Capability (Number of Equivalent NEs)
6 CPU Sun M5000
270
8 CPU Sun M5000
340
2 CPU HP RX2660
50
2 CPU HP RX7640
90
4 CPU HP RX7640
170
6 CPU HP RX7640
230
8 CPU HP RX7640
280
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 lists the relation between the server
quantity and the coefficient.
Table 6-2 Estimation of the management capability on NEs in the Sun SLS system
Number of
Servers
Distribution Mode of
Management Capability
Total Management
Capability Coefficient
1 + 0.6 (Master shares 0.6)
1.6
2 + 0.3 (Master shares 0.3)
2.3
The management capability of the ATAE cluster system depends on the number of blades in
use. With the typical configuration, the ATAE cluster system can manage 400 equivalent NEs.
Table 6-3 lists the management capability of the ATAE cluster system.
Table 6-3 Management capability of the ATAE cluster system
Hardware Configuration
Management Capability (Number of

Equivalent NEs)
Two M2000 service blades and one

M2000 database blade
400
The number of equivalent NEs is determined by the following factors:
Issue V1.1 (2011-01-15)

Page 34 of 46
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 V200R011 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-4 and Table 6-5 describe the specifications for configuring the Sun-based
single-server system and HA system.
Table 6-6 and Table 6-7 describe the specifications for configuring the HP-based single-server
system and HA system.
Table 6-8 describes the specifications for configuring the ATAE cluster server.
Table 6-4 Hardware reliability specifications (Sun-based single-server system)
Server Model
MTBF (Hour)
MTTR (Hour)
Annual Mean
Failure Time (Hour)
Availability
1 CPU T5220
95082
4.0113945
0.369558206
0.999957813
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-5 Hardware reliability specifications (Sun-based HA system)

Server Model
MTBF (Hour)
MTTR (Hour)
Annual Mean
Failure Time (Hour)
Availability
1 CPU T5220
95082
0.58333333
0.053742755
0.999993865
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
Issue V1.1 (2011-01-15)

Page 35 of 46
6 CPU M5000
40980
0.81666667
0.174569484
0.999980072
8 CPU M5000
31629
0.96666667
0.267720801
0.999969438
Table 6-6 Hardware reliability specifications (HP-based single-server system)

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

(Hour)
Availability
RX2660
96192
3.9738737
0.361877241
0.99995869
RX7640 (2 CPUs)
86259
3.2147269
0.326458203
0.999962733
RX7640 (4 CPUs)
80324
3.3481292
0.365126106
0.999958319
RX7640 (6 CPUs)
61567
3.4583774
0.492044185
0.999943831
RX7640 (8 CPUs)
55298
3.4921258
0.553168112
0.999936853
Table 6-7 Hardware reliability specifications (HP-based HA system)

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

Time (Hour)
Availability
RX7640 (2 CPUs)
86259
0.63333333
0.064317454
0.999992658
RX7640 (4 CPUs)
80324
0.76666667
0.083610576
0.999990455
RX7640 (6 CPUs)
61567
0.86666667
0.123311078
0.999985923
RX7640 (8 CPUs)
55298
0.98333333
0.155771399
0.999982218
Table 6-8 Hardware reliability specifications (ATAE cluster system with typical M2000
configuration)
Annual Mean
Failure Time
(Minute)
MTTR
(Hour)
MTBF
(Hour)
MTBF
(Year)
Availability
2.87
549,482
62.72
0.9999945
6.4 Compliant Safety Standards

The M2000 complies with the following safety standards:
IEC 60950-1
IEC/EN41003
Issue V1.1 (2011-01-15)

Page 36 of 46
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
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.
Issue V1.1 (2011-01-15)

Page 37 of 46
Table 6-9 Climatic requirements for equipment storage

Item
Range
Altitude
5,000 m (16,404 ft.)
Air pressure
70 kPa to 106 kPa
Temperature
0C (32 F) to +40C (104 F)
Temperature change rate
1oC (33.8 F)/min
Relative humidity
10% to 100%
Solar radiation
1,120 W/s
Heat radiation
600 W/s
Wind speed
30 m (98.42 ft.)/s
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
Issue V1.1 (2011-01-15)

Page 38 of 46

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
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 (65.62
ft.)/s
Frequency range
2 Hz to 9 Hz
9 Hz to 200 Hz
Impact response spectrum

II
250 m (820.20 ft.)/s
Static payload
5 kPa
Unsteady impact
Issue V1.1 (2011-01-15)

Page 39 of 46

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.
Table 6-13 Climatic requirements for transporting the equipment
Item
Range
Altitude
5,000 m (16,404 ft.)
Air pressure
70 kPa to 106 kPa
Temperature
0 C (32 F) to 40 C (104 F)
3C (37.4 F)/min
Humidity
5% to 100%
Solar radiation
1,120 W/s
Heat radiation
600 W/s
Wind speed
30 m (98.42 ft.)/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.
Issue V1.1 (2011-01-15)

Page 40 of 46
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
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
Unit
Density
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.30
in.)
N/A
--
Accelerated speed
N/A
20.0 m (65.62
ft.)/s
40.0 m (131.23
ft.)/s
Frequency range
2 Hz to 9 Hz
9 Hz to 200 Hz
200 Hz to 500 Hz
Issue V1.1 (2011-01-15)

Page 41 of 46
Item
Subitem
Range
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
Impact response spectrum II
300 m (984.24 ft.)/s
Static payload
10 kPa
Unsteady
impact
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
Normal
Safe
Normal
Safe
15C (59 F) to 30C (86

F)
0C (32 F) to 40C (104

F)
20% to 80%
20% to 90%
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.20 ft.)
Air pressure
70 kPa to 106 kPa
3 C (37.4 F)/min
Solar radiation
700 W/m
Issue V1.1 (2011-01-15)

Page 42 of 46
Heat radiation
600 W/m
Wind speed
1 m (3.28 ft.)/s
Ensure that the place for storing the equipment is free of:
Fungus or mildew
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
Unit
Density
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.
Issue V1.1 (2011-01-15)

Page 43 of 46
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 (32.81 ft.)/s
Frequency range
2 Hz to 9 Hz
9 Hz to 200 Hz
Impact response spectrum II
100 m (328.08 ft.)/s
Static payload
Unsteady impact
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.
Issue V1.1 (2011-01-15)

Page 44 of 46
Acronyms and Abbreviations
Abbreviation
Expansion
3GPP
3rd Generation Partnership Project
AAA
Authorization, Authentication, and Accounting
AHR
AP Home Register
ATAE
Advanced Telecommunications Application Environment
BSC
Base Station Controller
BTS
Base Transceiver Station
CG
Charging Gateway
CME
Configuration Management Express
CN
Core Network
CORBA
Common Object Request Broker Architecture
CSC
Call Session Control
DC
Direct Current
DDN
Digital Data Network
EMC
Electromagnetic Compatibility
ETS
European Telecommunication Standards
ETSI
European Telecommunications Standards Institute
GBSS
GSM Base Station Subsystem
GGSN
Gateway General Packet Radio Service (GPRS) Support Node
GSM
Global System for Mobile communications
GUI
Graphical User Interface
HA
High Availability
HLR
Home Location Register
Issue V1.1 (2011-01-15)

Page 45 of 46
Abbreviation
Expansion
HSS
Home Subscriber Server
IEC
International Electrotechnical Commission
IMS
IP Multimedia Subsystem
IWF
The Shared InterWorking Function
LTE
Long Term Evolution
MRFC
Multimedia Resource Function Controller
MRFP
Multimedia Resource Function Processor
MSC
Mobile Service Switching Center
MSC Server
Mobile Service Switching Center Server
MTTR
Mean Time To Repair
MGW
Media Gateway
MML
Man-Machine Language
NMS
Network Management System
NodeB
WCDMA Base Station
NTP
Network Time Protocol
OPEX
Operation Expenditure
PC
Personal Computer
PCU
Packet Control Unit
RNC
Radio Network Controller
SG
Signaling Gateway
SGSN
Serving GPRS Support Node
SLS
Multi-Server Load-Sharing
SNMP
Simple Network Management Protocol
UMTS
Universal Mobile Telecommunications System
VPN
Virtual Private Network
WCDMA
Wideband Code Division Multiple Access
Issue V1.1 (2011-01-15)

Page 46 of 46

M2000 Product Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M2000 Product Description

Uploaded by

Copyright:

Available Formats

iManager M2000 V200R011 Product

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Issue V1.1 (2011-01-15)

Huawei Proprietary and Confidential

iManager M2000 V200R011 Product Description

3 Products and Application Scenarios ....................................................................................... 13

6 Technical Specifications ............................................................................................................ 33

Issue V1.1 (2011-01-15)

Huawei Proprietary and Confidential

iManager M2000 V200R011 Product Description

7 Acronyms and Abbreviations ................................................................................................... 45

Issue V1.1 (2011-01-15)

Huawei Proprietary and Confidential

iManager M2000 V200R011 Product Description

1.2 Managed NEs

Radio network controller: RNC

Multi-mode base station controller: BSC6900 UMTS

Transmission gateway: TGW1000

Issue V1.1 (2011-01-15)

Huawei Proprietary and Confidential

iManager M2000 V200R011 Product Description

1.2.2 GBSS NEs

Base station controller: BSC

Base station controller: GT800BSC

Base station controller: BSC6000

Multi-mode base station controller: BSC6900 GSM

Base transceiver station: BTS

Transmission gateway: TGW1000

Packet control unit: PCU35

Packet control unit: PCU33

Packet control unit: PCU6000

1.2.3 SingleRAN NEs

Multi-mode base station controller (GU): BSC6900 GU

Multi-mode base station (GU): MBTS GU

Multi-mode base station (GL): MBTS GL

Multi-mode base station (UL): MBTS UL

Serving GPRS support node: SGSN

Gateway GPRS support node: GGSN

Report server: SUR

Mobile switching center: MSC

Mobile switching center server: MSC server

Home location register: HLR36

Home location register: HLR9820

Home location register (data node): HLR-DC

Home location register (service node): HLR-SC

Media gateway: MGW

Fixed-mobile convergence media gateway: FMC MGW

Signaling gateway: SG7000

Interworking function: IWF

Issue V1.1 (2011-01-15)

Huawei Proprietary and Confidential

iManager M2000 V200R011 Product Description

MSCs are categorized as follows:

MSC based on the 32-module architecture, also called MSC33 or G3

1.2.5 LTE-SAE NEs

SAE-home subscriber server: SAE-HSS

Unified serving node: USN

Unified gateway: UGW

Resource and policy control system: RM (RM9000)

1.2.6 uBro NEs