CME Overview

Why Is the CME Necessary?

Multiple RATs require

unified configuration
experience and fast
network deployment.

Cross-NE reparenting
and inter-RAT
parameter
synchronization require
efficient configuration
methods.

The MML method has

high requirements on
users and the humanmachine interface is
not easy to use.

Massive data on the

entire network needs
accurate check
methods.

What Is the CME?

What Can the CME Do for Us?

The CME is the data configuration management

system for Huawei radio access networks (RANs),
such as GBSS, WRAN, eRAN, and SRAN. It uses
GUIs and provides the integrated solutions for
devices in typical O&M scenarios, such as initial
deployment, transmission reconfiguration,
parameter optimization, and base station
reparenting.

Network
Planning

Network
Deployment

Summary data file

for site deployment
Radio network
planning data file

So easy!

Network
Maintenance

Network Adjustment
or Optimization

Batch modification
center
Batch configuration
adjustment file (summary
data file)
Frequency modification
wizard
Base station reparenting
wizard
Data conversion wizard

Single base station

creation wizard
Batch base station
creation wizard (by
importing and exporting a
summary data file)
Carrier resource
management
All types of data templates
Feature query and
activation wizard

Template management
Parameter check
Parameter comparison
Report management
Script executor
management
Northbound data
management

What's the Position of the

CME on the Network?
The CME lies at the element management system (EMS) layer and is integrated into the
U2000 as its configuration tool.
NMS
NMS

NBI

PRS : Performance Surveillance

Network/Terminal/Service/End user

TranSight

SONMaster

MBB E2E Network Visibility

SingleSON Management

CME
Configuration
Management Express

U2000

wSight

Network Management

WLAN Management

EMS
NE

SBI
Core

Radio
GSM
CDMA

UMTS

PS
Wireline

WiMAX

EPC

LTE

IP & Transmission

CS
Router

LAN
switch

Microwave

Firewall

IMS

WLAN
Other
vendors

AC
MAG9811

network

SingleSDB

How Is CME Hardware Deployed?

Client-based
Deployment

NSS

U2000 Client
(CME Client)

U2000 Server
(CME Server)

LAN

LAN

U2000 Client
(CME Client)

Install the U2000 client on the

PC on the O&M network and
start the CME on the U2000
client.

IP Backbone

Controller

Site

Site

Site

Citrix-based
Deployment

Citrix Client
NSS

IP Backbone
U2000 Server
(CME Server)

Deploy the Citrix server on the

O&M network and install and
release clients of multiple
applications such as the U2000
on the Citrix server.
Install the Citrix client on the
PC, invoke the U2000 client on
the Citrix server using the ICA,
log in to the CME server, and
perform related operations.

LAN
LAN

Citrix Server
(CME Client, U2000
Client, etc)

U2000 Client
(CME Client)

IP Backbone

Controller

Site

Site

Site

What Are the Structure and Release and

Installation Methods of the CME Version Package?

Version Package

Basic version package: According to the ATAE,

Sun, and HP platforms and database types,
multiple installation packages are available for
basic versions. Users need to choose the
packages based on the onsite U2000 server types.
Component package: Component packages are
not differentiated by platform. Users can choose
the packages based on onsite NE versions.

Version Installation

Basic version package: It is used to install the basic

framework of the CME.
Component package: It is used to install and adapt
to different NE versions.

Version Release
Mode

The basic version package and related component

package are installed on the server. No independent
installation DVD-ROM is released for the client. After
the server is installed, the client is installed in CAU
mode by using a web browser.

What Are Relationships Between the CME,

LMT, and MML Operation Platform?
The U2000 provides multiple configuration methods:
Use the CME on the U2000 client.
Start the LMT remotely on the U2000 client.
Use the MML operation platform on the U2000 client.
Tool
CME

LMT

NEs that Can Be

Operated Each Time

Description

Multiple.
Provides GUIs for users to directly perform operations without
The CME can manage
using/remembering MML commands.
NEs of different RATs Encapsulates complicated functions for scenarios and provides crossand perform batch
RAT and cross-NE operations, improving configuration efficiency.
operations on them.
Provides only the data configuration function and does not provide the
following functions: alarm display, message trace, performance
monitoring, and device maintenance.
Users are advised to use the other two tools for fine-tuning tasks that
require a single or a few commands.
One.
Uses MML commands to perform operations.
Users can start the
Provides configuration commands to configure data for NEs and the
LMT remotely on the
following functions: alarm display, message trace, performance
U2000. The LMT allows
monitoring, and device maintenance.
users to perform
Applies to the maintenance scenario where users need to fine-tune
operations on one NE
parameters of a single site.
each time.

MML
Multiple.

operation The MML operation

platform platform allows users to

run MML commands in
batches for multiple

NEs.

Uses MML commands to perform operations.

Provides configuration and maintenance commands, and allows users
to create MML script tasks to deliver MML commands for NEs of the
same type in batches, improving maintenance efficiency.
Does not provide the following functions: as alarm display, message
trace, performance monitoring, and device maintenance.
Applies to the scenario where users need to fine-tune parameters in
batches.

Role
New users or
users who are
unfamiliar with
how to use MML
commands.

Existing users
who are familiar
with how to use
MML commands.

Existing users
who are familiar
with how to use
MML commands.