Guide To The IManager M2000-CME V200R010 Configuration

Doc.
code
iManager M2000-CME
V200R010C00SPC220
Guide to NE Configuration on
the CME
Issue
01
Date
2010-11-20
INTERNAL
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2009. 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 contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in 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 the 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 01 (2010-11-20)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd
Page 3 of 21
INTERNAL
iManager M2000-CME V200R010C00SPC220
Guide to NE Configuration on the CME
Standalone CME and

Integrated CME
1.1 Feature Comparison

Feature
Integrated CME
Deployment
mode
The CME server and database are deployed

on the M2000 server.
The CME client, CME server, and

database are deployed on the same PC.
The CME client and M2000 client are

deployed on the same PC. The CME client is
started from the M2000 client.
The CME client is independent of the

M2000 client, that is, the M2000 client is
not used when the CME client is started.
The CME supports multiple clients, that is,

multiple users.
The CME supports the single user.
Position in
the OM
network
As a part of the OM network, the integrated

CME supports the authority management and
user management and accesses and modifies
the network configuration data through the OM
channel of the network management system
(NMS).
Importing
mode of the
network
configuration
data
Synchronizes the network configuration data

through the OM channel of the NMS.
Supports manual, periodical, and automatic

triggering of configuration data
synchronization.
Execution
mode of the
configuration
scripts
Configures the script executor.
Executes configuration scripts through the

OM channel of the NMS.
Supports manual or periodical execution of

configuration scripts.
Supports the execution of configuration

scripts in batches or the execution of a single
command.
Issue 01 (2010-11-20)
Standalone CME
The standalone CME may run normally

without accessing the OM network or
connecting to network elements (NE).
Supports the manual importing of

configuration data files of NEs.
Executes configuration scripts through the

LMT or the M2000 after the scripts are
exported.

Page 4 of 21
INTERNAL
Feature
Integrated CME
Standalone CME
NE
adaptation
All NEs supported by the CME V2R10
GBSS 9.0/12.0
WRAN 11.1/12.0
SRAN 3.0/5.0
TGW1000 V100R002
No current area or planned area
No support for the conflict detection
No script executor
No support for the northbound

configuration
Service
feature
Intended user
All features supported by the CME V2R10
O&M engineers of the operator or Huawei

technical support engineers
Huawei technical support engineers
1.2 Application Scenario and Precautions

To improve the configuration efficiency, the CME automatically generates non-negotiation
parameters. Therefore, the user does not need to plan these parameters. In this case, a couple
of planned areas of multiple standalone CMEs or an integrated CME are independent from
each other. Therefore, when more than one user performs configuration operations on the
same BSC by using the CME, non- negotiation parameters automatically generated by the
CME may conflict with each other. As a result, configuration commands fail to be executed
on the NE and the data duplication error is displayed, for example, Duplicate BTS Index.
Non- negotiated parameters automatically generated by the CME may conflict with each other
in one of the following scenarios:
When the integrated CME is used, multiple users create their own planned areas which
involve the same BSC. Then, users perform configuration operations on the NE in their
own planned area.
When the standalone CME is used, multiple users import the same bcp file to the CME,
and then perform configuration operations on the BSC through the CME.
To avoid configuration data conflicts, note the followings:
Ensure that different users manage different BSCs during network planning, that is,
multiple users perform configuration operations on different BSCs by using the CME,
such as create a site, add frequencies, add external cells, or add transmission links.
If different users perform operations on the same BSC, perform the following steps to
avoid data conflicts:
Issue 01 (2010-11-20)
Plan all non-negotiation parameters instead of using parameters generated

automatically by the CME.
Ensure that users perform configuration operations in turn, that is, after a user
completes the configuration and exports the scripts, another user is notified to start to
perform the configuration.

Page 5 of 21
INTERNAL
Creating an MBSC
This section describes the method of completing the initial configuration of the BSC6900 by
using the standalone CME.
2.1 Configuration Scenario and Method

Scenario
Method
The first BSC6900 is

configured or the
configuration of the new
BSC6900 is different from
configurations of all
existing BSC6900s.
The standalone CME provides the bcp file which involves

the typical configuration of the BSC6900 (in GU mode) with
the single subrack. When creating a BTS, the user can use
this file and configure the global data, device data, clock
data, and interface data by following the process of creating a
BTS in the product manual.
The configuration plan

(hardware and interfaces)
of the BSC6900 to be
created is similar to that of
an existing BSC6900.
After a typical BSC is created, the user can export the

configuration data of the BSC to create another BSC. The
configuration data can be exported through one of the
following methods:
Issue 01 (2010-11-20)
After the previous user executes the configuration scripts

on the BSC, the next user exports the bcp file to the CME
from the BSC and then performs configuration operations
based on the file.
The bcp file cannot be obtained on the field, but the BSC
configuration needs to be copied to create another BSC. In
this case, after completing the BSC configuration, the
previous user exports the configuration scripts, packs these
scripts into a zip file, and delivers this zip file to the next
user. Then, the next user imports this zip file and performs
the configuration operations based on this file.

Page 6 of 21
INTERNAL
2.1.1 Principle of Selecting a Typical BSC (GSM)
Select the BSC whose configuration is similar to that of the BSC to be created. Then, the
user only needs to make a few modifications on global data and device data.
Select the BSC which accesses the same core network with the BSC to be created. In this
case, the user only needs to make a few modifications on the data related to the signaling
point, A interface, and Gb interface.
2.1.2 Principle of Exporting Configuration Data of

the Typical BSC (GSM)
The configuration data of different BTSs controlled by different BSCs has little
similarity. Therefore, before BTSs are configured on the typical BSC, export the
configuration data to provide a guide for the configurations of other BSCs.
The configuration data of external cells served by different BSCs has little similarity.
Therefore, before external cells are configured on the typical BSC, export the
configuration data to provide a guide for the configurations of other BSCs.
2.1.3 Principle of Selecting a Typical RNC (UMTS)
Select the RNC whose hardware configuration is similar to that of the RNC to be
created. In this case, the user only needs to make a few modifications on global data and
device data.
Select the RNC which accesses the same core network with the RNC to be created. In
this case, the user only needs to make a few modifications on the signaling point data.
2.1.4 Principle of Exporting Configuration Data of

the Typical RNC (UMTS)
Most of Iu interface data cannot be modified. To reduce the data modification workload,
export the configuration data of the typical RNC to provide a guide for the
configurations of other RNCs before the Iu interface is configured.
The configuration data of NodeBs served by different RNCs has little similarity.
Therefore, before BTSs are configured on the typical RNC, export the configuration data
to provide a guide for the configurations of other RNCs.
The configuration data of external cells served by different RNCs has little similarity.
Therefore, before external cells are configured on the typical RNC, export the
configuration data to provide a guide for the configuration of other RNCs.
Issue 01 (2010-11-20)

Page 7 of 21
INTERNAL
Creating a BTS
The CME supports the BTS creation in the GUI or by importing the negotiation data file. That
is, the user sets the planning data in the GUI or prepares the planning data in the negotiation
data file and then imports the data.
To reduce the number of parameters to be set during the configuration and ensure the
consistency of parameters of multiple BTSs and cells, the CME provides the templates to
encapsulate parameters that can be reused by multiple BTSs. The user can specify a template
in the GUI or in the negotiation data file and configure the BTS rapidly. If the planning data
overlaps certain parameters, the planning data prevails.
Templates such as the BTS template and cell template may be involved during the BTS
creation.
3.1 Custom BTS Template

3.1.1 Principle of Using a Custom BTS Template
During the BTS planning, the user prepares custom templates through the following
principles:
Customize templates based on the BTS type. At least, each type of BTSs matches a
template, for example, separately define a template for the BTS3900 S444 and BTS3900
S666.
If BTSs of the same type differ in hardware configuration, determine whether to define
more than one template according to the configuration difference, for example, S444
series BTSs.
Issue 01 (2010-11-20)
If there are few inconsistent hardware configurations, only one template is defined for
the creation of S444 series BTSs. Then, the user can adjust the inconsistent
configurations in the GUI.
If there are many inconsistent hardware configurations, more than one template are
defined for S444 series BTSs according to the configuration differences, for example,
templates with the bypasses or without bypasses.

Page 8 of 21
INTERNAL
3.1.2 Creating a Custom BTS Template

During the BTS creation, first select a system-carried template whose configuration is similar
to the template to be customized. Then, configure the BTS (serving as a base BTS) in the GUI
or by importing the data file. Finally, save the data of the base BTS as a custom template.
3.2 Custom Cell Template

3.2.1 Principle of Using a Custom Cell Template
During the BTS planning, the user prepares custom templates through the following
principles:
Customize templates based on the planned cell type. At least, each type of cells matches one
template, for example, separately define a template for EDGE cells and half-rate EDGE cells.
3.2.2 Creating a Custom Cell Template

During the BTS creation, select a system-carried template whose configuration is similar to
the cell template to be customized. Then, configure the BTS (serving as a base BTS) in the
GUI or by importing the data file. Finally, save the cell data of the base BTS as a custom
template.
3.3 Creating a BTS

Adopt different policies to create BTSs in the following scenarios divided based on the
number of BTSs to be created.
Scenario
Method
A small
number of
BTSs (equal to
or smaller than
ten) are
created.
Issue 01 (2010-11-20)
Many BTS types, for

example, the ratio of
the number of BTSs to
the number of BTS
types is less than 2.
1. In the GUI, configure the data related to

devices, transmission, cells, and TRXs of other
BTSs of the same type by using custom
templates.
2. Import the wireless network planning data to
configure external cells and neighboring cells.

Page 9 of 21
INTERNAL
Scenario
Method
Few BTS types, for
example, the ratio of
the number of BTSs to
the number of BTS
types is greater than 2.
1. Select a base BTS for each BTS type. Then,

export the negotiation data to an Excel
document (negotiation data file).
2. Copy the base BTS data in the Excel
document. Then, modify the planning
parameters in the Excel document, such as the
BTS name, upper-level ports, cell indexes, cell
names, CGI, and frequencies. Specify the BTS
template and cell template to be used.
3. Import the modified Excel file and create
BTSs in batch.
4. Import the wireless network planning data to
5. If certain planning parameters are
inconsistent with those of the BTS template,
make some modifications.
A batch of
BTSs (more
than ten) are
created.
Issue 01 (2010-11-20)
The scenario features a great number of BTSs

and a small number of BTS types. Then, the
user can create BTSs in batches by importing
the negotiation data file.

Page 10 of 21
INTERNAL
Creating a NodeB
To reduce the number of parameters to be set during the configuration and ensure the
consistency of parameters of multiple NodeBs and cells, the CME provides the templates to
encapsulate parameters that can be reused by multiple NodeBs. The user can specify a
template in the negotiation data file to configure the NodeB rapidly. If the planning data in the
negotiation data file overlaps certain parameters, the planning data prevails.
Templates such as the NodeB template and cell template may be involved during the NodeB
creation.
4.1 Custom NodeB Template

4.1.1 Principle of Using a Custom NodeB Template
During the NodeB planning, the user prepares custom templates through the following
principles:
Customize templates based on the NodeB type. At least, each type of NodeBs matches a
template, for example, separately define a template for the BTS3900 3x1 and BTS3900
3x2.
If NodeBs of the same type differ in hardware configuration, determine whether to

define more than one template according to the difference, for example, 3x1 series
NodeBs.
If there are few inconsistent hardware configurations, only one template is defined for
the creation of 3x1 series NodeBs. Then, the user can adjust the inconsistent
configurations in the GUI.
If there are many inconsistent hardware configurations, more than one template are
defined for 3x1 series NodeBs according to the configuration differences.
4.1.2 Creating a Custom NodeB Template

During the NodeB creation, select a system-carried template whose configuration is similar to
the NodeB template to be customized. Then, configure the NodeB (serving as a base NodeB)
by importing the negotiation data file. Finally, save the data of the base NodeB as a custom
template.
Issue 01 (2010-11-20)

Page 11 of 21
INTERNAL
4.2 Custom Cell Template

4.2.1 Principle of Using a Custom Cell Template
During the NodeB planning, the user prepares custom cell templates through the following
principles:
Customize templates based on the planned cell types. At least, each type of cells matches one
template, for example, separately define a template for R99 cells and cells supporting the H
service.
4.2.2 Creating a Custom Cell Template

During the NodeB creation, first select a system-carried template whose configuration is
similar to the cell template to be customized. Then, configure the cell (serving as a base cell)
by importing the negotiation data file. Finally, save the data of the base cell as a custom
template.
4.3 Creating a NodeB

Step 1 Export the Iub negotiation data, including the physical NodeB data.
Select a base NodeB for each NodeB type. Then, export the Iub negotiation data file.
Step 2 Modify the data in the exported Iub negotiation data file, including the physical NodeB data.
Copy the base NodeB data in the negotiation data file for the creation of other NodeBs.
Then, change settings of planning parameters, such as the NodeB name, NodeB index, and
Iub transmission parameters.
Step 3 Import the Iub negotiation data, including the physical NodeB data.
Import the modified Iub negotiation data file. Specify the NodeB template to be used. Then,
configure the logic NodeB and physical NodeB and configure the Iub interface on the RNC
side.
Step 4 Import the wireless network planning data.
Import the wireless network planning data file. Specify the cell template to be used and
Step 5 Modify the configuration. This step is optional.
Adjust necessary parameter settings in batch or in the configuration interface.
----End
Issue 01 (2010-11-20)

Page 12 of 21
INTERNAL
Adjusting Parameter
Settings
The CME supports the adjustment of parameter settings through the GUI or by importing the
negotiation data file, which is applicable to the adjustment of few parameter settings or in
batch.
5.1 GSM
Global parameters, device parameters, and transmission parameters of the BSC
Device parameters are set on the device panel, whereas other parameters are set in the GUI
(configuration express).
Network planning parameters, network optimization parameters, TRX parameters, and

channel parameters of the cell
Scenario
Method
Parameter settings of a single cell or fewer cells need

to be adjusted.
GUI (configuration express)
Parameter settings of more than one cell need to be

consistent.
GUI (bulk modification center)

inconsistent.
Importing the negotiation data file
BTS parameters
Board parameters are set on the device panel.

If parameter settings of multiple BTSs need to be consistent, adjust parameter settings in
batches. Otherwise, adjust parameter settings in the GUI (configuration express).
Issue 01 (2010-11-20)

Page 13 of 21
INTERNAL
5.2 UMTS
Global parameters, device parameters, and transmission parameters of the RNC
Device parameters are set on the device panel, whereas other parameters are set in the GUI
(configuration express).
Network planning parameters of cells
Scenario
Method
Parameter settings of a single cell or fewer cells

need to be adjusted.
GUI (configuration express)

consistent.
GUI (bulk modification center)

inconsistent.
Importing the negotiation data file
Network optimization parameters of cells
If parameter settings of multiple cells need to be consistent, adjust parameter settings in

batches. Otherwise, adjust parameter settings in the GUI (configuration express).
Physical NodeB parameters
Unit parameters are set on the device panel.

If parameter settings of multiple NodeBs need to be adjusted, adjust parameter settings in
batches. Otherwise, adjust parameter settings on the NodeB configuration interface.
Issue 01 (2010-11-20)

Page 14 of 21
INTERNAL
Configuring an MBTS
This section describes the principle of configuring an MBTS and the relevant parameter
settings.
6.1 MBTS
In an MBTS, each NE has an independent control board. That is, each NE functions
independently and has a complete set of configuration data.
A GU MBTS consists of a GBTS and a NodeB.
A GL MBTS consists of a GBTS and an eNodeB.
6.2 Principle of Configuring an MBTS

The MBTS supports the following deployment modes:
Co-cabinet
The NEs that form an MBTS share a common set of electromechanical units, such as the fans,
temperature control unit, power monitoring unit, and environment monitoring unit.
When the user configures or manages the common electromechanical units on one NE, ensure
that the parameter settings on this NE are consistent with those on the other NE. Otherwise,
an alarm is triggered due to conflicting parameter settings on two NEs.
Common devices include:
Electromechanical devices in the BBU
The parameter settings of the unit in each slot of each subrack in the cabinet must be
consistent between the NEs.
Local RS485 electromechanical devices
The parameter settings of the unit in each slot of each subrack in the cabinet must be
consistent between the NEs.
Issue 01 (2010-11-20)

Page 15 of 21
INTERNAL
The RS485 fieldbus address of the local RS485 electromechanical unit, whose cabinet,
subrack, and slot information is consistent between the NEs, must be consistent between the
NEs. Likewise, the slot, subrack, and cabinet information about the electromechanical unit
whose RS485 fieldbus address is consistent between the NEs must be consistent between the
NEs.
Remote electromechanical devices and RET antennas
The cabinet, subrack, and slot information about each remote electromechanical unit must not
conflict between the NEs, and each RET antenna number must be unique within the MBTS.
Co-RF
In the MBTS deployed in this mode, the NEs share both common electromechanical units and
the MRFU/MRRU. The software-defined radio (SDR) technology enables the TRXs and
carriers to be transmitted through one MRFU/MRRU in the MBTS.
In co-RF mode, the MBTS adopts the dual-star structure in connecting the physical MRRU to
the NEs. The cabinet, subrack, and slot information about the MRRU on one NE must be
consistent with that on the other NE. The cabinet, subrack, and slot information about the
physical MRRUs not shared by the NodeB and GBTS must be different between the NEs.
The MSR for 3GPP co-RF MBTSs is to be released in July 2010. Currently, the user is
recommended to configure independent transmit channels for GU MBTSs. That is, the NEs in
the MBTS do not share the power amplifier (PA).
An MRFU provides one transmit channel. Therefore, a GU MBTS needs two MRFUs.
An MRRU provides two transmit channels. Currently, the NEs do not share the PA if the
MBTS is configured with an MRRU.
The hardware specifications of the RF modules of an MBTS have limitations in terms of the
number of TRXs and carriers, bandwidth, and power. That is, ensure that the sum of TRXs
and carriers configured for the NEs does not exceed the specifications.
6.3 MBTS Types

SRAN 5.0 supports the following types of MBTSs:
GU MBTS
GL MBTS
UL MBTS
GU MBTSs and GL MBTSs can be deployed in co-cabinet and co-RF modes, which are
typical configuration scenarios. The CME provides functions of configuring these types of
MBTSs. For details about the functions, see the description in later sections.
UL MBTSs can only be deployed in co-cabinet mode, which is a non-typical configuration
scenario. The CME provides consistency check on the parameter settings of common
electromechanical units for this type of MBTSs. For details about the functions, see the
function description of SRAN 3.0.
Issue 01 (2010-11-20)

Page 16 of 21
INTERNAL
Creating an MBTS
The CME provides configuration templates that provide the common parameters shared by
the NEs in an MBTS. During MBTS deployment through the GUI or negotiation data files,
the user can specify a suitable template and then complete the configuration of common
electromechanical units of the MBTS quickly. In this way, the user can reduce the number of
input parameters and ensure the consistency of parameters settings between the NEs.
As the interface protocol stack for each RAT is different, the user needs to plan and configure
the transport layer data on each NE separately.
As each NE adopts a different RAT, the user needs to plan and configure the data of the radio
layer on each NE separately.
The CME provides the functions of configuring GU MBTSs and GL MBTSs. The following
section takes the creation of a GU MBTS as an example.
7.1 Custom MBTS Template

7.1.1 Principle of Using a Custom MBTS Template
The user needs to customize a template for each typical configuration scenario according to
the actual configuration of common electromechanical units.
A custom MBTS template consists of the common parameters of the GBTS template and the
NodeB template.
7.1.2 Creating a Custom MBTS Template

Create a golden MBTS, complete the configuration of each NE in the MBTS through the GUI
or negotiation data files, and save the configuration data of the golden MBTS as a custom
template. For details about how to create a golden MBTS, see the SRAN 3.0 guide.
7.2 Creating an MBTS

The user can deploy an MBTS through the GUI or negotiation data files.
Issue 01 (2010-11-20)

Page 17 of 21
INTERNAL
7.2.1 Importing the Planning Data

The user needs to plan the MBTS deployment data, edit the negotiation data files, and import
the planning data from the negotiation data files to the CME. This mode is applicable to batch
MBTS deployment.
The procedure is as follows:
Figure 1.1 Creating an MBTS through negotiation data files
The operation procedure of the MBTS creation wizard on the CME is as follows:
Issue 01 (2010-11-20)

Page 18 of 21
INTERNAL
Figure 1.2 Operation procedure of the MBTS creation wizard
The operation procedure of the MBTS creation wizard is as follows:

Step 1 Specify the MBTS deployment scenario.
The user needs to specify whether to deploy a new MBTS or reconstruct a single-RAT GBTS
or NodeB into an MBTS.
Step 2 Specify the negotiation data files.
GBTS negotiation data file: The user needs to specify the GBTS negotiation data file, which
is the same as that for deploying a single-RAT GBTS.
Iub data negotiation file: The user needs to specify the Iub negotiation data file, which is the
same as that for deploying a single-RAT NodeB.
MBTS data negotiation file: The user needs to specify the mapping between the GBTS and
NodeB in this file.
Step 3 Import the negotiation data files.
The user needs to import the negotiation data files to the CME.
Step 4 Check/adjust the common parameters.
The user needs to check the consistency of common parameter settings and adjust inconsistent
parameter settings.
Issue 01 (2010-11-20)

Page 19 of 21
INTERNAL
Note: The user does not need to specify the Iub negotiation data file when reconstructing a
GBTS and does not need to specify the GBTS negotiation data file when reconstructing a
NodeB.
The user can also adopt the configuration mode introduced in SRAN 3.0 to deploy MBTSs
through negotiation data files.
Step 1 Import the GBTS negotiation data file.
The user needs to create a GBTS by importing the GBTS negotiation data file.
Step 2 Import the Iub negotiation data file.
The user needs to create a NodeB by importing the Iub negotiation data file.
Step 3 Configure the GBTS and NodeB into an MBTS.
The user needs to configure the GBTS created in step 1 and the NodeB created in step 2 into
an MBTS in the MBTS configuration/browsing window.
Step 4 Check/adjust the common parameters.
The user needs to check the consistency of common parameter settings and adjusts
inconsistent parameter settings.
7.2.2 Creating an MBTS Through the GUI

The mode of creating the MBTS through the GUI is applicable to a new MBTS. The user
needs to run the ADD UNODEB command to create the logical NodeB on the RNC/MBSC
for the NodeB in the MBTS.
The user needs to set the following parameters in the GUI when deploying a new MBTS:
1.
Basic GBTS parameters, including the ID, name, site type, and Abis interface
2.
Basic NodeB parameters, including the site type and version
3.
Parameters in the MBTS template
After a new MBTS is deployed, the user needs to perform the following GUI operations:
1.
Configure the radio layer for the GBTS.
2.
Configure the transport and radio layers for the NodeB.
Note: When reconstructing a single-RAT GBTS or NodeB into an MBTS, the user does not
need to import the existing data and needs to set only the following parameters:
Basic parameters of the GBTS or NodeB to be reconstructed
Parameters in the MBTS template
Issue 01 (2010-11-20)

Page 20 of 21
INTERNAL
Adjusting MBTS
Parameter Settings
The CME provides functions of configuring GU MBTSs and GL MBTSs. This section takes
the configuration of a GU MBTS as an example to describe the adjustment of MBTS
parameter settings.
The CME provides an MBTS device panel for configuring common electromechanical units,
which supports the following functions:
Displaying all MBTS units (including all GBTS and NodeB units) and identifying the
common electromechanical units shared by the GBTS and NodeB.
Ensuring the consistency of common parameter settings between the GBTS and NodeB.
The settings of common parameters performed on one NE take effect on both NEs in the
MBTS.
The CME provides data check and adjustment for the RF module of the MBTS deployed in
co-RF mode.
The CME supports the check of the carriers and TRXs on the RF module in terms of
bands, bandwidth, and power and generates an error report on the items incompliant with
the hardware specifications.
The CME provides one-touch adjustment of inconsistent parameter settings. The CME
collects and lists the optional adjustment suggestions for the user to choose and then
completes the adjustment automatically.
Issue 01 (2010-11-20)

Page 21 of 21

Guide To The IManager M2000-CME V200R010 Configuration

Uploaded by

Document Information

Original Title

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

Guide To The IManager M2000-CME V200R010 Configuration

Uploaded by

Copyright:

Available Formats

Doc.

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

Standalone CME and

1.1 Feature Comparison

The CME server and database are deployed

The CME client, CME server, and

The CME client and M2000 client are

The CME client is independent of the

The CME supports multiple clients, that is,

The CME supports the single user.

As a part of the OM network, the integrated

Synchronizes the network configuration data

Supports manual, periodical, and automatic

Configures the script executor.

Executes configuration scripts through the

Supports manual or periodical execution of

Supports the execution of configuration

The standalone CME may run normally

Supports the manual importing of

Executes configuration scripts through the

Huawei Proprietary and Confidential

All NEs supported by the CME V2R10

No current area or planned area

No support for the conflict detection

No support for the northbound

All features supported by the CME V2R10

O&M engineers of the operator or Huawei

Huawei technical support engineers

1.2 Application Scenario and Precautions

To avoid configuration data conflicts, note the followings:

Plan all non-negotiation parameters instead of using parameters generated

Huawei Proprietary and Confidential

2.1 Configuration Scenario and Method

The first BSC6900 is

The standalone CME provides the bcp file which involves

The configuration plan

After a typical BSC is created, the user can export the

After the previous user executes the configuration scripts

Huawei Proprietary and Confidential

2.1.1 Principle of Selecting a Typical BSC (GSM)

2.1.2 Principle of Exporting Configuration Data of

2.1.3 Principle of Selecting a Typical RNC (UMTS)

2.1.4 Principle of Exporting Configuration Data of

Huawei Proprietary and Confidential

3.1 Custom BTS Template

Huawei Proprietary and Confidential

3.1.2 Creating a Custom BTS Template

3.2 Custom Cell Template

3.2.2 Creating a Custom Cell Template

3.3 Creating a BTS

Many BTS types, for

1. In the GUI, configure the data related to

Huawei Proprietary and Confidential

1. Select a base BTS for each BTS type. Then,

The scenario features a great number of BTSs

Huawei Proprietary and Confidential

4.1 Custom NodeB Template

If NodeBs of the same type differ in hardware configuration, determine whether to