Security Level:Internal Only

Introduction to the Working

Principles of the M2000-CME
V200R011 (Basics)

ISSUE1.1 www.huawei.com

Wireless Product Rollout Dept.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

 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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 2

 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

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 3

 1 CME of the Single RAN

2 Basic Concept of the CME

3 Working Principles and

Configuration Procedure of

the CME

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 4

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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 5

Features of the CME
Scenario/workflow optimization
Advanced Tools
Batch data configuration
Configuration of parameters
for site deployment,
neighboring cells, and
algorithms
BTS swapping
ARFCN modification
3GPP northbound interface
Quality Assurance
Consistency check based on
the entire network
Check for the data validity
and service rules
HUAWEI TECHNOLOGIES Co., Ltd.
Planning in advance
Concurrent operation
Frequency replanning
workflow
Swapping workflow
Reduction of Operation and
Maintenance Cost
Reducing the complexity during the
site deployment
Unifying the maintenance solution
for the M2000
Unifying the management of
activating configuration scripts
Page 6
HUAWEI Confidential
Delivery Features of the CME V200R011

Software Platform Value-Added Service

Supporting Sun mini-server + MBTS integrated configuration

Solaris + Sybase RRU resource allocation
Supporting HP/ATAE mini- BTS swapping crossing NEs
and versions
server + Linux + Oracle Frequency replanning on the
Sharing the platform with the
entire network
M2000 Site deployment in batches
Providing a single-server Adjustment of neighboring cell

version NE Access relations

Providing a Chinese version Modification of algorithm

Distributed mode parameters in batches

3GPP northbound
High availability (HA) RAN 13.0/12.0/11.0 / 11.1
configuration
Security GBSS 13.0/12.0/9.0/8.x
Consistency check
Reliability LTE 2.0/ LTE 2.1 Panoramic view
Component-based release

Page 7
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential
 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.

Display the transmission

relations intuitively.

Display the timeslot on the

GUI.

Cascade, Ring topology

multi-
Traditional site deployment
link
New TOPO site deployment
wizard

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 8

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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 9

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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 10

 1 CME of the Single RAN

2 Basic Concept of the CME

3 Working Principles and

Configuration Procedure of

the CME

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 11

Version of the CME
The CME can be installed on the M2000 (integrated version) or installed independently (standalone version),
depending on the OSS network and project process.

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.

GBTS NodeB

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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 12

Software and Hardware Deployment (1)

Integrated into the M2000

Software platform
Solaris + Sybase
Linux + Oracle
Hardware platform
Sun
HP
ATAE

Page 13
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential
Software and Hardware Deployment (2)

Citrix networking
solution

Page 14
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential
Deployment CME Integrated Version
NMS

The CME is installed on the

CME Client
MBSC/MBTS
Business
GBSS
Business
WRAN
Business
LTE
Business
M2000 server.
Client Framework Data is exchanged in the

Corba
following modes:
Extracting network configuration
N-Itf(Corba)
CME Adapter data through channels of the
CME Business Server
iMAP Platform iMAP Platform M2000
M2K Mediation
DB Link Delivering configuration data
through channels of the M2000 by
DB
M2K Master Server M 2K Slave Server
executing related commands

NE

Page 15
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential
Deployment CME Standalone Version

The standalone CME is for internal use only.

CME Client
The CME is installed on a PC.
MBSC/MBTS GBSS WRAN LTE
The Windows operating system is supported.
Business Business Business Business
The standalone CME is independent of the M2000 or
Client Framework
other NEs.
The CME is used in the pure offline scenario.
Corba
Data is exchanged in the following modes:
Extracting NE configuration data by importing the
configuration files exported by NEs
CME Business Server
MBSC: bcp file
NodeB: XML configuration file
DB Link
eNodeB: XML configuration file
Supporting backing up or recovering NE
SQL Server configuration data of the CME
CME Server
Recovering or exchanging data between CME
standalone (offline) versions by backing up data

Page 16
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential
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..

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 17

 Comparison Between Integrated Version and
Standalone Version
Integrated Version Standalone Version

Recommended Online data configuration based on the M2000, such as BTS swapping, Initial data configuration and capacity expansion in a large scale.
scenario network optimization adjustment, and resource statistics.

License The functions are controlled by the license of the M2000. Huawei engineers: A temporary license whose validity is three months is
Basic function package: The GBSS 9.0 version is provided in the CME released on the Support Web site.
V200R011 basic function package for free when the GBSS is upgraded.
The CME V200R011 must be charged in new markets.

Configuration One current area, multiple planned areas and multiple fallback areas. No current area, one planned area, and one fallback area.
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 Synchronize data on the BSC, NodeB, and eNodeB (through the data Export data by running the EXP CFGSYNFILE command after logging in
the live network channel between the M2000 and NEs). to the NE through the Web LMT.

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

Database Sybase (working with the SUN server on the M2000) MSDE (SQL Server 2005 is recommended.)
Oracle (working with the HP or ATAE server on the M2000)

Documentation Product manuals and version documents Version documents for standalone version:
Installation guide
Operation guide
For detailed configuration operations, see the product manuals.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 18

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.

In the standalone version: The

CME client, CME server, and the
database are installed on the same
PC.

Software structure in the

integrated version

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 19

Version Compatibility
M2000
The recommended matching version is M2000 V200R011.
BSC
The recommended matching version is BSC6900 V900R013, BSC6900 V900R012, and BSC6900 V900R011, which can
provide configuration capability on transmission, device, and radio parameters.
The matching BSC6000 only provides the capability for radio layer and BTS swapping that works with the GBSS CME
V100R005.
The matching BSC6800 and BSC6810 are used only for the BTS swapping crossing specified versions.
GBTS
The GBTS does not directly match the CME. In this case, the CME matches the GBTS versions that are supported by the
BSC6900 versions that match the CME.
NodeB
The NodeB versions that work with the CME are the NodeB versions that work with the BSC6900/RNC.
The CME only matches the baseline versions of the NodeB, such as SPC100, SPC 200, and SPC 300 and their non-
baseline versions. The interface configured for NodeB products remains unchanged. For example, if the CME works with
SPC 100, then the CME works with versions such as SPC1XX or SPH1XX.
The following are principles of the CME to release the NodeB components.
For NodeB versions released after a CME version is released, the matching components are required and are released

with the NodeB version. When the component is used, refer to the Release Notes of the component to confirm the
CME version working with the component.
The preceding components will be contained in the following CME version.
LTE
The eRAN 2.1/eRAN 2.0 is recommended.
MBTS
The MBTS versions working with the CME depend on the versions of LTE, NodeB, and GBTS working with the MBTS.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 20

Data Configuration Method General 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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 21

Data Configuration Method Configuration 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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 22

Data Configuration Method Batch 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.

Right-click the
configuration NE to
display the GUI for
batch data
modification.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 23

Data Configuration Method Import 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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 24

Data Configuration Method Device 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

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 25

Data Configuration Method Typical Scenario

The typical scenario function is designed focusing on typical configuration scenarios, such as swapping, TOPO site deployment,
and HSPA.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 26

 1 CME of the Single RAN

2 Basic Concept of the CME

3 Working Principles and

Configuration Procedure of

the CME

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 27

General Operation Procedure Integrated 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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 28

Data Flow
Three areas: live network, current area, and
planned area.
Interaction of data flow
Planned
Planned area Current area: Data area
modification in the planned area does not
affect data in the current area. Generating and Creating,
Planned area live network: Data activating scripts synchronization
modification in the planned area takes
Live
effect on the live network by generating Current area
network
and activating data scripts. Before the
changed data is delivered, data on the live Synchronization
network is not affected.
Live network current 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 area planned area: By
creating/synchronizing data in the planned
area, some data in the current area is
synchronized to the planned area.
Current area live network: Data in the
current area is read-only and does not
affect the live network.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 29

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 is
overwritten 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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 30

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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 31

Data Editing in the Planned Area
General configuration: Users can configure the
attribute of each object on the general configuration
interface in GUI mode. The general configuration can
be displayed in the following configuration views:
Navigation tree: Object tree view, transmission tree view
Configuration area: Device panel view, configuration ObjectTree
object
Network topology view
Batch data modification view
Configuration express view
Wizard configuration: Users can complete the complex
configuration task through the wizard.
TOPO site deployment
Swapping wizard
Consistency check wizard Network
File import and export: The configuration data topology
generated by the external tools can be imported to
implement batch configuration in an efficient manner.
Importing the data negotiated for the site deployment
Device
Importing and exporting radio parameters panel
Modifying cell attributes, frequencies, and TRX attributes
in batches

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 32

Check for Data Conflict
Data conflict can be divided into the following types:
Warning: Data conflict of this type may lead to activation failures.
Users add a configuration object in the planned area but the object has been available on the live network.
Users modify a configuration object in the planned area but the object has been deleted on the live network.
Users delete a configuration object in the planned area but the object has been deleted on the live network.
Note that the data conflict is not checked between objects that have parent-child relations.
Hint: Data conflict of this type occurs because a user modifies data in the planned area but the data has
been modified by another user and has been updated to the current area. Whether activation failures occur
depends on configuration rules on the live network.
During the data configuration, users can check the data modification on the live network
through the AVC message and adjust data configuration in time.
After the data configuration is complete, users need to check whether data is conflicted.
Compare user configuration data in the planned area with configuration data of the live network in the
current area to locate conflicted data.
Users can adjust configuration data in the planned area based on the check result to ensure that the
subsequent activation is successful.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 33

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 as
parameter 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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 34

Activation of Scripts
Activation Type
START Manual start
Run the Bulk_Configuration command in
batches.
Upload
The efficiency for scripts to take effect is high.
The entire script needs to be modified after the Auto start
Active data
script activation fails.
Run the MML command one by one.
The efficiency for scripts to take effect is low. MML
Modify MML
The user interaction is large in number. has
errors
A single command is modified after the script
activation fails.
Browse task

Activation Methods End

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.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 35

 General Operation Procedure Standalone Version

Network Expansion
Site Deployment Description
and Adjustment
Network expansion and adjustment scenarios: Users export the current
configuration data (BSC: .ZIP file, by using the Web LMT (EXP CFGSYNFILE;
Obtaining data from
eNodeB: export from M2000). The exported data will be imported to the CME.
the live network

Users start the client software before using the CME to configure data.
Starting the client Starting the client
software software
Site deployment scenario: GU: The CME provides the basic unit of data
configuration files (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.
Adding NEs Adding NEs Network expansion and adjustment: Users create an NE on the CME and import the
corresponding 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.
Configuring data Configuring data
Users check the correctness of data through the consistency check function provided
by the CME.
Checking data Checking data
After data configuration and data check are complete, users export the MML/XML
scripts for activating data on the live network.
Exporting MML/XML Exporting MML /XML
Users activate data by using the Web LMT.
(Note: The frequency refarming scripts exported from the standalone CME must be
Activating MML/XML Activating MML/XML activated through the script executor provided by the integrated CME.)

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 36

Data in the Standalone Version
BSC/eNodeB Data NodeB Data Configuration Data

Source BSC: 1. Users can export the BSC data by running the EXP NodeB data is exported through Configuration data is transmitted among standalone
CFGSYNFILE command after logging in to the BSC6900 through the LMT or M2000 of the versions and is generated by choosing Data
the Web LMT. NodeB. Management > Export Data.
2. An example of minimal data is provided in the installation
directory of the CME.
LTE: export using LMT or M2000

Content BCP files of a single BSC XML files of a single NodeB Compressed data packages in standalone versions
eNodeB: XML file for one or more selected BSCs (including all NodeBs
under the BSCs)

Default name BSC: CMECfgSyncView.zip NodeBCfg.xml NEData.zip

eNodeB: LMT.xml or M2000.xml

Entrance

NE is selected
based on each
BSC/eNdeB.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 37

 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 adjustment the incremental xml scripts generated by CME could not be activated
using Web LMT.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 38

 Incremental Scripts Activation: Method 1 Scripts Executor
The Incremental Scripts generated by CME could be activated using Scripts
Executor.
Scripts Executor is embedded in integrated CME.
The difference between execution in standalone and integrated CME is:
For standalone CME, the incremental scripts generated by standalone CME needs to be imported to
integrated CME( Open scripts executor, create project, upload incremental scripts, and activate projects
manually).
For integrated CME, it could jump to scripts executor and activate project automatically after exporting
incremental scripts.
Frequency refarming scenario: The verification of commands are different from batch commands.

When exporting incremental scripts, if scripts are service affected, the CME will pop out
messages for user to confirm the operations.
Operation steps on integrated CME:

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 39

 Incremental Scripts Activation : Method 2 MML Commands

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 Batch window 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 (Unit:
Mode
Second)
Consuming Time in Typical Scenarios
4489 scripts are executed during the swapping of five BTSs, including
adjustment of network optimization data. Batch Configuration 647
Based on the preceding condition, it is calculated that the swapping of
50 BTSs takes about two hours and six hours respectively in batch
Batch Processing 1767
configuration and batch processing modes.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 40

Thank You
www.huawei.com