cme system description(v100r002)

5/21/2018 CME System Description(V100R002)

1/33

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

www.huawei.com

Internal

CME System Description

CMEV100R002


2/33

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 2

Upon completion of this course, you will

be able to:

Understand the system description

and the feature of CME

Understand the procedure of CME

data configuration.


3/33


References

RAN CME User Guide

RNC Initial Configuration Guide

(CME-Based)

RAN Reconfiguration Guide (CME-

Based)


4/33


Chapter 1 the System Description of CME

Chapter 2 the Conception of CME

Chapter 3 the procedure of CME data configuration


5/33


Functions of the CME

The CME is an auxiliary project design tool

for RAN equipment. The GUI-based CME

has the following functions:

Providing integrated solutions to RANdata configuration

Improving data configuration efficiency

Reducing daily maintenance cost


6/33


Components of the CME

Components of the CME

Logically, the CME consists of the following

components:

CME server:

It is installed with the database software and

processes core data logically.

CME client:

It is installed with the CME application and

provides GUIs.

Physically, the CME client and CME server

can be located either on the same PC or on

different PCs.

CME Client

Network Equipments

LAN

CME

Server

CME Client

CME

Server


7/33HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 7

CME in RNC Disconnected Mode

In RNC disconnected mode, the CME is disconnected

from the RNC. The data is transferred between the CME

client and the CME server.

CMEserver CME client

Read data

Save data



CME in RNC Connected Mode

In RNC connected mode, the CME is connected to the RNC. The data is

transferred between the CME client, CME server, and RNC BAM server.

Synchronizationchannel

CMEserver CMEclient

CME

system

RNC

M2000

server

M2000 FTP

server

M2000server

MML fi les XML files

NodeB

IPoA PVC



Features of the CME

Overview of CME Features:

Automatic Data Refreshing on the Iub Interface

Distributed Client and Server

Convenient Resource Management

Intelligent Data Operation

Diverse Data Sources

Multiple Types of Data for Export

User-Centered Design

Project-Based Data Management

Auxiliary Data Modification Tool

User-Friendly Online Help



Features of the CME

Automatic Data Refreshing on the Iub Interface

When configuring Iub interface data, configure the transport network layer

data to the RNC, and then start the data refreshing function to

synchronize the data at the NodeB with the configured data at the RNC.

Thus, the Iub interface data in the Radio Network System (RNS).

Automatic data refreshing on the Iub interface simplifies data configuration,

ensures data consistency for the Iub interface, and fulfills integratedWRAN data configuration.

Distributed Client and Server

The CME works in distributed mode, in which the client and server are

separated and work as follows:

A CME server can connect to several CME clients at the same time.

A CME client can connect to different CME servers, but can only connect

to one CME server at a time.

The distributed mode ensures flexibility in applying the CME.



Features of the CME

Convenient Resource Management

The resource indication on the CME client shows in real time the usage of

transmission resources, such as the bandwidth and physical links.

The device panel on the CME client shows the NodeB hardware data

configuration in real time.

Intelligent Data Operation

The CME automatically operates the key data of neighboring cells, SAAL

links, IP routes, and ATM addresses. And then the CME collects available

resources, puts them into the resource pool, and displays them on the

GUIs.

The CME configures the data available in the resource pool in batches.



Features of the CME

Diverse Data Sources

Negotiated Data File

RNC BAM Database

NodeB Template

NodeB Data Configuration File

Multiple Types of Data for Export

NodeB Data Configuration File

NodeB Template

RNC Data Configuration File

Negotiated Data File

Field Engineering Design File


13/33


Features of the CME

User-Centered Design (UCD)

The CME provides multiple information navigation modes, such as

navigation by Network Element (NE) and by protocol stack. Some

configuration, such as adding a NodeB or cell or removing a NodeB or cell,

can be performed through the wizard.

UCD simplifies data configuration.

Project-Based Data Management

All configuration data of the CME is stored on the database of the CME

server. You can create multiple projects. Database space separated byprojects enables you to configure different RAN data.

Project-based data management facilitates data backup.


14/33


Features of the CME

Auxiliary Data Modification Tool

The CME can synchronize data with the RNC BAM server. In addition, the

CME provides the wizard for operations in RNC connected mode. The

operations include the following: adding NodeBs in batches, adding cells

in batches, modifying cell algorithm parameters in batches, modifying cell

frequencies, modifying neighboring cell relationships

These operations support MML-based data transfer to NEs in real timeand are applicable to scenarios such as routine maintenance and network

optimization.

User-Friendly Online Help

With the online help, you can query information of parameters on a

configuration interface by the interface name. The parameter information

includes the value range, description, unit, and default value.

The introduction to the CME and description of project operations are also

available from the online help for you to check, browse, import, or export data.


15/33






16/33


Views of the CME Application


17/33


Concepts of the CME -Project

Concept

A project is a RAN data configuration task with a complete set

of data.

Project Management

Creating a project

Opening a project

Closing a project

Deleting a project

Backing up or restoring a project


18/33


Concepts of the CME -Negotiated Data File

Concept

A negotiated data file contains a set of configuration data that is obtained asrequired during site preparation to simplify the initial configuration and expansion.

The data set includes the following data: NodeB basic data at the RNC, cell data

at the RNC, neighboring cell data, neighboring cell relationship data. The

negotiated data template file is saved in .xls format.

Role of the Negotiated Data File in the CME The negotiated data file can be a data source for CME initial configuration and

expansion.

Method of Obtaining the Negotiated Data File

The negotiated data file is provided with the CME software. The file is available

from

\CMEV100R002\import, where

stands for the CME installationdirectory

Scenarios of the Negotiated Data File

During RAN initial configuration and expansion on the CME, import data in the

negotiated data file into the CME to generate CME configuration data.


19/33


Concepts of the CME -NodeB Template

Concept

A NodeB template contains a set of recommended data predefined with

common configuration types, demodulation modes, and Iub transmission

modes to simplify NodeB data configuration.

Role of the NodeB Template in the CME

The NodeB template can be a data source for NodeB data configuration on

the CME.

Method of Obtaining the NodeB Template

The NodeB template is provided with the CME software. The template is

available from\CMEV100R002\template\NodeB.

Scenarios of the NodeB Template

During NodeB initial configuration on the CME, import a NodeB template

according to the NodeB type.


20/33


Concepts of the CME -NodeB Data Configuration File Concept

A NodeB data configuration file contains a complete set of NodeB configuration

data for proper operation of the NodeB.

Role of the NodeB Data Configuration File in the CME

The NodeB data configuration file can be directly loaded to the NodeB as an

export file after NodeB data configuration. In addition, the NodeB data

configuration file is an optional data source for NodeB configuration on the CME.

Method of Obtaining the NodeB Data Configuration File

You can export a NodeB data configuration file either after configuring the

NodeB data or from the current network. The file then serves as the data source

for NodeB data configuration.

Scenarios of the NodeB Data Configuration File

Export the NodeB data configuration file to the NodeB LMT after the RAN initial

configuration is complete on the CME. Then load the file to the NodeB and

validate the file.

When reconfiguring the RAN on the CME, import the NodeB data configuration

file to the CME server to synchronize new NodeB data with existing NodeB data.


21/33


Concepts of the CME -RNC Data Configuration File

Concept

An RNC data configuration file contains a complete set of RNC configuration

data for specific RNC operations.

Role of the RNC Data Configuration File in the CME

The RNC data configuration file can be loaded to the RNC as an export fileafter RNC data configuration.

Method of Obtaining the RNC Data Configuration File

Export the RNC data configuration file after data configuration on the CME.

Scenarios of RNC Data Configuration Files

The RNC initial configuration file applies to RAN initial configuration.

The RNC incremental configuration file applies to RAN reconfiguration.


22/33


Concepts of the CME -Field Engineering Design File

Concept

A field engineering design file is the one exported with a template to guide

field engineering and to export engineering reports.

Role of the Field Engineering Design File in the CME

The field engineering design file can be an export file after data configuration

on the CME.

Method of Obtaining the Field Engineering Design File

After configuring data on the CME, export the field engineering design file

with the template.

Scenarios of the Field Engineering Design File The field engineering design file applies to the following two scenarios:

RAN initial configuration

RAN reconfiguration


23/33






24/33


Work Flow for RAN Initial Configuration


25/33


Work Flow for RAN Initial Configuration

Work Flow for Reconfiguring the NodeB to a Large Scale:


26/33


RNC Initial Configuration on CME (with No Data Imported)


27/33


RNC initial configuration on the CME (with negotiated data imported)


28/33


Work Flow for RAN Reconfiguration


29/33


Principle for CME-Based RAN Reconfiguration


30/33


Procedure of CME-Based RAN Reconfiguration


31/33


CME-Based RAN Reconfiguration Tasks

Adding a NodeB (on the RNC)

Adding a NodeB (on the RNC and the NodeB)

Batch Adding NodeBs

Setting the NodeB Configuration Type

Deleting a NodeB (on the RNC)

Batch Deleting NodeBs (on the RNC)

Setting the Tilt of RET

Setting the ALD Power Switch

Setting the Gain of the TMA

Setting the RTWP Initial Value of the MTRU or MRRU

Setting the Transmission Unit Switch of the MTRU or MRRU

Setting the IF Offset of the MTRU or MRRU


32/33


CME-Based RAN Reconfiguration Tasks

Setting the RX Attenuation of the MAFU or MRRU

Set the RF Desensitivity of the RRU

Adding a Cell

Modifying the Frequency or the Scrambling Code

Modifying the Maximum Transmit Power

Modifying the AICH or PICH Power Offset

Modifying the Neighboring Cell Relationship

Modifying the Algorithm Switch

Modifying Parameters of the RRM Algorithm

Modifying the Cell Access Restriction Information

Comparing Radio Algorithm Parameters

Deleting a Cell (on the RNC)

Batch Deleting Cells (on the RNC)


33/33

www.huawei.com

Thank You

cme system description(v100r002)

Documents

cme overview of cme

cme components

cme servercan

cme automatic data refreshing

huawei technologies

rights reserved page

configured data

iub interface data