cme v200r011 introduction to the working principles basics 20111106 b 1 1

8/12/2019 CME V200R011 Introduction to the Working Principles Basics 20111106 B 1 1

1/41

www.huawei.com

Security Level:Internal Only

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

Wireless Prod uct Ro l lout Dept.

Introduction to the Working

Principles of the M2000-CME

V200R011 (Basics)

ISSUE1.1


2/41

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 2

The CME is a GUI configuration solution of the Single

RAN.

Based on the typical application process, this document

describes the working principles of the CME from the

aspect of the location of the CME, configuration policies

of the CME software and hardware, and working

principles. In addition, it describes the frameworks of the

CME manuals.


3/41


You can understand the following contents through

this training:

Location of the CME in the OSS solution of the

Single RAN

Basic principles of the CME

Configuration Procedure of the CME

Integrated version

Standalone version


4/41


1CME of the Single RAN

2 Basic Concept of the CME

3 Working Principles and

Configuration Procedure of

the CME


5/41


Location of the CME

The CME is a part of the OSS solution, and is the core of the integrated configuration solution for multi-mode

radio network provided by Huawei. In addition, the CME supports typical scenarios of UMTS and GSM networks,

such as initial site deployment, network capacity expansion, BTS swapping, and routine configuration adjustment.

The CME11.0 provides a solution for the unified management configuration of the GSM/UMTS/LTE (GUL).

For the GSM network, the BSC6900 working with the CME provides the GUI data configuration function.

For the UMTS network, the CME is an evolution of the WRAN CME V100R008.

For the LTE, the CME works with the eRAN2.0/eRAN2.1 and provides functions such as site deployment and

routine maintenance.

The CME11.0 supports the SRAN6.0 and the downward overall solution.


6/41


7/41

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI ConfidentialPage 7

Delivery Features of the CME V200R011

Software Platform

Supporting Sun mini-server +

Solaris + Sybase

Supporting HP/ATAE mini-

server + Linux + Oracle

Sharing the platform with the

M2000

Providing a single-serverversion

Providing a Chinese version

Distributed mode

High availability (HA)

Security

Reliability

Component-based release

RAN 13.0/12.0/11.0 / 11.1

GBSS 13.0/12.0/9.0/8.x

LTE 2.0/ LTE 2.1

NE Access

Value-Added Service

MBTS integrated configuration

RRU resource allocation

BTS swapping crossing NEs

and versions

Frequency replanning on the

entire network

Site deployment in batches

Adjustment of neighboring cellrelations

Modification of algorithm

parameters in batches

3GPP northbound

configuration

Consistency check

Panoramic view


8/41


Advantages of the CME

GUL Multi-mode Configuration

The configuration on the GSM, UMTS, and the LTE is synchronized and the configuration consistency on the GSM, UMTS, and the LTE is checked to

ensure that the GUL resources are centrally managed.

In the BSC6900, the GSM, UMTS, LTE, and MBTS use the unified device panel to implement the centralized management of the GSM/UMTS devices.

GUI Enhancement

The TOPO site deployment, BTS networking, TRXs of each cell, and timeslot allocation can be viewed in GUI mode on the LMT of the BSC6000.

Therefore, the BTS configuration and resource allocation can be displayed clearly.

New TOPO site deploymentTraditional site deployment wizard

Display the transmission

relations intuitively.

Cascade,

multi-linkRing topology

Display the timeslot on the GUI.

Evolu

tion


9/41


Advantages of the CME (Continued)

Improvement on Operation Efficiency

The network-level configuration is centralized. Single BSC multiple BSC

Configuration of a single BTS Configuration of BTSs in batches through the templates

The BTS swapping within a BSC and that between the BSCs can be implemented. In addition, the data

adjustment of neighboring cells can be implemented automatically, saving time for script preparation by

network optimization engineers.

The files configured in offline mode dynamically take effect, improving the file configuration in offline mode.

On the LMT, DAT files configured in offline mode can take effect only after the BSC is reset. In this

case, services are greatly affected.

On the CME, after files are configured in offline mode, corresponding MML scripts are generated so

that these files can take effect when the MML scripts are delivered dynamically. In this case, the BSC is

not reset and services are not affected.

Compared with the LMT of BSC6000, the CME supports the multi-user concurrent configuration in online

mode.

The data browsing capability and retrieval capability on the entire network are greatly improved.

Security The CME provides the function of data check on the entire network before data is activated, including the

check for completeness, redundancy, and consistency.

The CME supports the data rollback in key scenarios.

The CME supports the parameter comparison. That is, the CME compares the data that has taken effect and

the template to check whether data configuration is correct.


10/41


Advantages of the CME (Continued)

Functions of SingleRAN6.0 Working with the CME

MBTS data is configured through the GUI or exporting the negotiation data. The menu entrance is unified and the operations are simple. In addition, the GU/GL multi-mode MBTS can be created

integrally, using the method for single-mode MBTS configuration.

This ensures the consistency of common parameters in G/U or G/L mode.

Capacity of a single-mode MBTS is expanded.

A single-mode MBTS can be expanded to a dual-mode MBTS in any mode from GSM, UMTS, or LTE.

This ensures the consistency of common parameters in G/U or G/L mode.

Capacity of a dual-mode MBTS is expanded.

A dual-mode MBTS can be expanded to a triple-mode MBTS in any mode from G/U, U/L, or G/L. This ensures the consistency of common parameters in G/U /L mode.

The MBTS uses the unified device panel to configure the dual-mode device panel so that data can take effect on both G/U and

G/L side simultaneously.

The MBTS device data is configured intuitively.

The MBTS device boards in G/U, G/L, and G/U/L mode can be displayed in a unified way.

The configuration parameters of MBTS common boards are modified.

Parameters of the MBTS common boards are configured in a unified way.

Parameters of common boards are configured intuitively.

Parameters of common boards in G/U, G/L, and G/U/L mode are displayed in a unified way.

This ensures the consistency of common board parameters in G/U, G/L, and G/U/L mode.

MBTS templates are managed in a unified way.

The consistency check result is enhanced.

The list of MBTSs to be deployed is exported.

The dynamic spectrum sharing (DSS) is supported.


11/41


1 CME of the Single RAN




the CME


12/41


Version of the CME

Integrated version (or online, network mode)

The CME is installed on the M2000.

The communication between the CME and NEs is

implemented through the M2000 client.

Standalone version (or offline mode)

The CME is installed on a PC.

The CME cannot communicate with NEs directly. NE data is obtained

manually and scripts are delivered manually.

The Windows operating system is supported.

The CME can be installed on the M2000 (integrated version) or installed independently (standalone version),

depending on the OSS network and project process.

GBTS NodeB


13/41


Software and Hardware Deployment (1)

Integrated into the M2000

Software platform

Solaris + Sybase

Linux + Oracle

Hardware platform Sun

HP

ATAE


14/41


Software and Hardware Deployment (2)

Citrix networking

solution


15/41


DeploymentCME Integrated Version

The CME is installed on the

M2000 server.

Data is exchanged in the

following modes:

Extracting network configurationdata through channels of the

M2000

Delivering configuration data

through channels of the M2000 by

executing related commandsM 2K Slave ServerM 2K Master Server

Corba

NE

DB

DB Link

CME Adapter

iMAP Platform

M 2 K Mediation

iMAP Platform

CME Business Server

N -Itf ( Corba)

NMS

CME Client

Client Framework

GBSS

Business

WRAN

Business

MBSC/MBTS

Business

LTE

Business


16/41


DeploymentCME Standalone Version

The standalone CME is for internal use only.

The CME is installed on a PC.

The Windows operating system is supported.

The standalone CME is independent of the M2000 or

other NEs.

The CME is used in the pure offline scenario.

Data is exchanged in the following modes:

Extracting NE configuration data by importing the

configuration files exported by NEs

MBSC: bcp file

NodeB: XML configuration file

eNodeB: XML configuration file

Supporting backing up or recovering NE

configuration data of the CME

Recovering or exchanging data between CME

standalone (offline) versions by backing up data

CME Server

Corba

SQL Server

DB Link

CME Business Server

CME Client

Client Framework

GBSS

Business

WRAN

Business

MBSC/MBTS

Business

LTE

Business


17/41


Triple Area

Triple area: current area, planned area, and fallback area

Current area

Current area is a network data mirroring area used to save the configuration data of the live network.

Data in the current area is read-only and cannot be modified directly to ensure the security of the

network.

Only one current area is available for a network system.

Through the CME, the data of the live network can be periodically or automatically synchronized to the

current area. Alternatively, users can manually synchronize the data of the live network to the current

area.

Planned area

Planned area is a data planning area that is created with the data of a certain NE system.

Users can perform data planning in the planned area. Different users can create their respective

planned areas. The planned areas are independent of each other.

After implementing data planning in the planned area, users can export the generated data scripts.

After executing the data scripts to the NE, users can make the data take effect.

Fallback area

The rollback command scripts are generated in the fallback area to perform rollback.

When configuration adjustment effects are not ideal, the CME can quickly roll back to the original

configuration status.

Currently, the CME supports the rollback on the GSM side in only three scenarios: RNP import,

modification of radio algorithm parameters in batches, ARFCN import. In addition, the CME supports

the rollback in all adjustment scenarios on the UMTS side in versions later than BSC6900

V900R012C01 (UMTS only). For LTE, CME supports the rollback in all adjustment scenarios..

C i B t I t t d V i d


18/41


Comparison Between Integrated Version and

Standalone Version

Integrated Version Standalone Version

Recommended

scenario

Online data configuration based on the M2000, such as BTS swapping,

network optimization adjustment, and resource statistics.

Initial data configuration and capacity expansion in a large scale.

License The functions are controlled by the license of the M2000.

Basic function package: The GBSS 9.0 version is provided in the CME

V200R011 basic function package for free when the GBSS is upgraded.

The CME V200R011 must be charged in new markets.

Huawei engineers: A temporary license whose validity is three months is

released on the Support Web site.

Configuration

area

One current area, multiple planned areas and multiple fallback areas. No current area, one planned area, and one fallback area.

Function 1. Configuration functions, such as site deployment and site swapping, are the same.

2. In the standalone version, current area-based functions, such as AVC, are unavailable. The script executor is unavailable.

Obtaining data of

the live network

Synchronize data on the BSC, NodeB, and eNodeB (through the data

channel between the M2000 and NEs).

Export data by running the EXP CFGSYNFILEcommand after logging in

to the NE through the Web LMT.

Activating the

script

Script executor Script configuration/processing in batches on the Web LMT

Database Sybase (working with the SUN server on the M2000)Oracle (working with the HP or ATAE server on the M2000)

MSDE (SQL Server 2005 is recommended.)

Documentation Product manuals and version documents Version documents for standalone version:

Installation guide

Operation guide

For detailed configuration operations, see the product manuals.


19/41


Software Structure

CME client software, which is used to display the GUI

In the integrated version, the CME client software is installed on the maintenance terminal where the M2000 client is installed.

In the standalone version, the CME client software is installed on the PC.

CME server software, which is used to control the traffic flow and execute configuration operations by communicating

with the CME client

In the integrated version, the CME server software is installed on the M2000 server and communicates with applications on

the M2000 to obtain the NE information.

In the standalone version, the CME server software is installed on the PC.

Database

In the integrated version, the CME and the M2000 share one database, which is used to store NE configuration data.

In the standalone version, the MSDE database is used and is installed on the PC.

Software structure in the

integrated version

In the standalone version: The

CME client, CME server, and thedatabase are installed on the same

PC.


20/41


21/41


Data Configuration MethodGeneral Configuration

The general configuration function provides a general method for editing non-equipment parameters on the table.

On the GUI, select the level of the configuration object, such as BSC, BTS, cell, TRX, or sector cell (LTE) level. Then,

select a configuration object with the selected level to display the configuration GUI.

On the GUI, all data of the configuration object is displayed on the table. Users can filter or edit data on the table.

Level of the configuration

object, which can be a

BSC, BTS, cell, TRX, or

sector cell (LTE) level

List of objects

with the selectedlevel

Editing area

of the tableArea for editing

a single object


22/41


Data Configuration MethodConfiguration Express

The configuration express function provides a method for editing data of a NE based on the table, depending on service

requirements. The configuration express function is similar to the general configuration function. The difference is that

the configuration express function is more convenient for some service requirements. The configuration express function varies with supported objects and can be divided into several types, such as

BSC/radio express, NodeB/BTS express, cell configuration express, and neighboring cell configuration express.

Entrance of the

configuration express

Working area of the

configuration express

The GUI may vary with

configuration expresses.

Data Configuration Method Batch Data


23/41


Data Configuration MethodBatch Data

Modification

The batch data modification function provides a method for quickly modifying multiple

parameter values of objects with the same type to the same value under one or several NEs.

Entrance for batch

data modification in

the application menu

Configuration objectsunder one or several

NEs can be modified

in batches.

Parameter values

of several objects

can be modified to

the same value.

Right-click the

configuration NE to

display the GUI for

batch data

modification.


24/41


Data Configuration MethodImport and Export

The data import and export functions are provided based on different scenarios.

The data import and export functions are used to modify or create object data in batches. Different from

the batch data configuration function, the data import function does not require changing the parameter

values to the same. Instead, the planned data can be imported.


25/41


Data Configuration MethodDevice Panel

The device panel function is used to add or delete device parameters of the NEs.

Whether data configuration of common boards is conflicted can be displayed on the MBTS

device panel.

Right-click the selected NE to

display the GUI of the device panel


26/41


Data Configuration MethodTypical Scenario

The typical scenario function is designed focusing on typical configuration scenarios, such

as swapping, TOPO site deployment, and HSPA.


27/41


1 CME of the Single RAN




the CME

G O


28/41


General Operation ProcedureIntegrated Version

0. Get data from the live network to current area

Current area is stored in M2000.

Every user of one M2000 has the same current area.

This action is called Synchronize NE.

1. Create a planned area

Planned area is stored in M2000.

Each user has a planned area.

Copy NE data from the current area.

2. Data configuration in planned area

Create, delete, move or modify BSC, BTS, or NodeB.

Adjust parameters.

3. Scripts Check the data conflict between the planned area and the current area.

Generate MML/XML scripts.

Activate scripts in NEs by the script executor.

4. AVC (Attribute Value Change)

After the scripts are activated, the related NE sends an AVC message to the

current area, indicating the changes in the data configuration on the live network.

The AVC message is also reported for changes in the data configuration due to

other causer except for activated scripts. The synchronization of data between the planned area and the current area is

triggered in firm real time.

M2000

GBSS

Current Configuration

0.Upload

1.Create

2.Adjust

Parameters

3. Incremental scripts

are generated

and activated in NE

4. AVC

Planned

Configuration

Local

Configuration

Local

Configuration

Planned

Configuration

Other

Other

D t Fl


29/41


Data Flow

Three areas: live network, current area, and

planned area.

Interaction of data flow

Planned areaCurrent area: Datamodification in the planned area does not

affect data in the current area.

Planned arealive network: Data

modification in the planned area takes

effect on the live network by generating

and activating data scripts. Before the

changed data is delivered, data on the live

network is not affected.

Live networkcurrent area/planned area:

Data modification on the live network will

be updated in the current area but cannot

be updated in the planned area.

Current areaplanned area: By

creating/synchronizing data in the planned

area, some data in the current area is

synchronized to the planned area.

Current arealive network: Data in thecurrent area is read-only and does not

affect the live network.

Planned

area

Current areaLive

network

Creating,

synchronization

Synchronization

Generating and

activating scripts

S h i ti i th C t A


30/41


Synchronization in the Current Area

Synchronization mechanism

Full synchronization: All configuration data is uploaded from the NE to

the current area and the data previously saved in the current area isoverwritten completely. The history data of the current area cannot be

saved.

Differentiated synchronization: The data modified in the MOC tables of

the NE is uploaded to the current area. Therefore, the synchronization

efficiency is improved. The incremental synchronization is always used

for daily operations.

The incremental synchronization is supported since BSC6900.

Synchronization method

The data synchronization can be performed periodically, automatically,or manually. The data synchronization of the current area is performed

in firm real time.

The data synchronization is performed automatically in the following

cases:

The CME receives the AVC message reported by the NE and

receives no other messages within two minutes.

A BSC is created on the M2000 and data synchronization has

been complete.

Data synchronization has been performed on the NodeB or TGW

on the M2000.

The script data has been successfully activated.

M2000

Current Area

1.Upload

Planning area ...

Current data browse

Current area mgt.

Planning area

...

MBSC BSC6000NodeB

...LocalConfiguration

LocalConfiguration

LocalConfiguration

...

BSC6810

Creating a Planned Area


31/41


Creating a Planned Area

Planning a planned area

Based on the data in the current area, multiple planned areas can

be created and a network can be planned concurrently.

The data conflicts between the planned areas can be found only

when the data in the planned areas takes effect on the live network.

If the data conflicts between the planned areas occur, the data in the

planned areas fails to take effect and are mutually overwritten. As a

result, the operation of the NE is affected.

To prevent the data conflicts between the planned areas, data

planning engineers should rationally plan the data in the planned

areas (such as cell index or TRX index) to ensure that the data in the

planned areas is not mutually overlapped.

Creating a planned area:copy the data of NEs from the current

area to the planned area.

M2000

Current Area

Planning area ...

Manage planning area

Modify planning data

Planning area

Create planning area

with current area data


32/41


33/41

Generation of Scripts


34/41


Generation of Scripts

The CME supports two types of MML/XML file: differentiated data MML/XML file and full data

MML/XML file.

BSC and BTS: MML commands will be generated; NodeB and eNodeB: XML file will be generated. Differentiated data MML/XML scripts: MML/XML configuration scripts are generated based on

modified contents.

This type of command is generated during the configuration of the planned area and is related to the

configuration process.

This type of command supports the exporting of modified contents separately by exporting multiple

differentiated scripts in the same planned area.

This type of command supports all configuration operations and is applicable to the scenarios such asparameter modification, radio network planning, and optimization.

Full data MML/XML scripts: MML configuration scripts are generated based on objects.

This type of command supports the exporting of all configuration scripts based on the object selected

by users

The exported objects include:

BSC data, including data on the BSC, equipment, transmission, and radio network

BTS data, including data on the BTS equipment, transmission, and radio network

NodeB and eNodeB data, including all data of site.

This type of command is generated according to the data in the planned area and is not related to the

configuration process.

This type of command is applicable to special scenarios such as initial network deployment or site

deployment.

Activation of Scripts


35/41


Activation of Scripts

Activation Type

Run the Bulk_Configurationcommand in

batches. The efficiency for scripts to take effect is high.

The entire script needs to be modified after the

script activation fails.

Run the MML command one by one.

The efficiency for scripts to take effect is low.

The user interaction is large in number.

A single command is modified after the script

activation fails.

Activation Methods Timed activation: The configuration script is activated at the time specified by the user.

Stopped once an error occurs: The script activation is stopped immediately after an error occurs during a

command execution. In this case, the script activation resumes after the command is modified or skipped.

Skipping the error command: When error occurs during a command execution for activating the script, the

error command is skipped and the script activation resumes from the next command.

Pre-activation: The NE creates a simulative digital environment for the M2000 to perform the pre-activation

function. In this case, the M2000 can confirm whether data in the configuration files to be activated takes

effect.

START

Upload

Active data

Modify MML

Browse task

End

MML has

errors

Manual start

Auto start

General Operation Procedure Standalone Version


36/41


Site DeploymentNetwork Expansion

and AdjustmentDescription

Network expansion and adjustment scenarios:Users export the currentconfiguration data (BSC: .ZIP file, by using the Web LMT (EXP CFGSYNFILE; eNodeB:

export from M2000). The exported data will be imported to the CME.

Users start the client software before using the CME to configure data.

Site deployment scenario:GU: The CME provides the basic unit of data configurationfiles (ZIP files) based on NEs. Users can import a ZIP file to create an NE. They can

also reconfigure an NE based on this file. LTE: create site using GUI or sumary.

Network expansion and adjustment:Users create an NE on the CME and import thecorresponding NE data obtained from the live network.

Users reconfigure the data of an NE by using the CME client. The procedure is the

same as that by using the integrated CME.

Users check the correctness of data through the consistency check function provided

by the CME.

After data configuration and data check are complete, users export the MML/XMLscripts for activating data on the live network.

Users activate data by using the Web LMT.

(Note: The frequency refarming scripts exported from the standalone CME must be

activated through the script executor provided by the integrated CME.)

Obtaining data from

the live network

Starting the client

software

Adding NEs

Configuring data

Checking data

Exporting MML /XML

Activating MML/XML

Starting the client

software

Adding NEs

Configuring data

Checking data

Exporting MML/XML

Activating MML/XML

General Operation ProcedureStandalone Version


37/41

Full Data XML Scripts Activation


38/41


Full Data XML Scripts Activation

Scripts generated by CME could be activated in many ways:

Remote Commissioning on the M2000;

Local Commissioning Using a USB Storage Device in Combination with Remote Commissioning

on the M2000; Local eNodeB Commissioning on the LMT .

Refer to base station Commissioning Guide

Operation Steps of Remote Commissioning on the M2000;

In CME, create site by GUI or summary importing;

In CME, Export Auto Deployment Configuration Data

After exporting from CME, user needs to create commissioning tasks, upload data, version

file etc.

On M2000: Start commissioning task. M2000 will commission NodeB/eNodeB automatically.

Full Data XML Scripts of NodeB and eNodeB could also be activated by MML:

On Web LMT, using command: DLD CFGFILE, ACT CFGFILE to download and activate full data

XML scripts

Configuration adjustmentthe incremental xml scripts generated by CME could not be activated

using Web LMT.


39/41

Incremental Scripts Activation : Method 2MML Commands


40/41


p

This is only for GU BSC and BTS . The incremental scripts for

NodeB and eNodeB are XML file which could not be downloaded

and activated by MML commands. Batch Processing

Scripts are executed through the Batchwindow on the WEB LMT.

Multiple execution methods are provided for a better man-machine

interaction.

The efficiency for delivering scripts to take effect is low.

Batch Configuration

Scripts are delivered in batches by running the RUN BATCHFILE

command on the WEB LMT. The efficiency for delivering scripts to take effect is high.

Script Executor

Scripts are uploaded to the script executor provided by the integrated

CME.

The script executor is used in the frequency replanning scenario and

the method for checking commands in the scripts is different from that

in the batch configuration and batch processing.

Consuming Time in Typical Scenarios

4489 scripts are executed during the swapping of five BTSs, including

adjustment of network optimization data.

Based on the preceding condition, it is calculated that the swapping of

50 BTSs takes about two hours and six hours respectively in batch

configuration and batch processing modes.

ModeConsuming Time (Unit:

Second)

Batch Configuration 647

Batch Processing 1767


41/41

Thank You

www.huawei.com

cme v200r011 introduction to the working principles basics 20111106 b 1 1

Documents