SR@N12.0 Mode - Transition - Guide

3900 Series Multimode Base Station
V100R012C00
Mode Transition Guide(For NB)
Issue 03
Date 2016-12-09
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. 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 a 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 03 (2016-12-09) Huawei Proprietary and Confidential i

Copyright © Huawei
Technologies Co., Ltd.
Mode Transition Guide(For NB) Contents
Contents
1 Overview.........................................................................................................................................1
1.1 About This Document.....................................................................................................................................................1
1.2 Prerequisites...................................................................................................................................................................1
2 Mode Transition............................................................................................................................2
3 Planning Mode Transition...........................................................................................................5
3.1 Introduction....................................................................................................................................................................5
3.2 RF Planning....................................................................................................................................................................8
3.2.1 Overall RF Planning Process.......................................................................................................................................8
3.2.2 Adding an RF Module.................................................................................................................................................9
3.2.3 Reusing the Original Multiband Module...................................................................................................................16
3.2.4 Applying SDR to the Original RF Module................................................................................................................20
3.2.5 Adding a Module to the Original SDR Module.........................................................................................................27
3.2.6 Replacing the Original Module with a New SDR Module........................................................................................34
3.3 Antenna and Feeder Networking..................................................................................................................................42
3.3.1 Overall Antenna and Feeder Planning Process..........................................................................................................43
3.3.2 Adding an Independent Antenna (Antenna Port) and an Independent Feeder..........................................................44
3.3.3 Adding an Independent Antenna (Antenna Port) and Sharing the Original Feeder..................................................55
3.3.4 Broadband Antenna (Antenna Port) Being Shared By the Original Mode and New Mode......................................66
3.3.5 SDR RF Module of the New Mode Using the Original Feeder................................................................................69
3.4 Co-MPT or Separate-MPT Planning............................................................................................................................70
3.4.1 Overall Co-MPT or Separate-MPT Planning Process...............................................................................................70
3.4.2 Adding a Main Control Board of the New Mode to the Original BBU....................................................................72
3.4.3 Adding a new BBU and a Main Control Board of the New Mode............................................................................76
3.4.4 Adding a New Mode to the Co-MPT Base Station...................................................................................................78
3.4.5 Co-MPT Reconstruction and Adding a New Mode to the Co-MPT Base Station....................................................80
3.5 BBU Interconnection..................................................................................................................................................101
3.5.1 Overall BBU Interconnection Planning Process.....................................................................................................101
3.5.2 Adding a BBU for BBU Interconnection Through UCIU+UMPT.........................................................................103
3.5.3 Adding a BBU for BBU Interconnection Through UMPT+UMPT........................................................................107
3.6 Clock Planning...........................................................................................................................................................110
3.6.1 Overall Clock Planning Process..............................................................................................................................110
Issue 03 (2016-12-09) Huawei Proprietary and Confidential ii

Copyright © Huawei
3.6.2 New Mode Using an Independent Reference Clock with Separate-MPT Configuration........................................112
3.6.3 New Mode and Original Mode Sharing Reference Clock with Separate-MPT Configuration...............................113
3.6.4 New Mode Requiring Modification to the Clock Source with Co-MPT Configuration.........................................114
3.7 Baseband Planning.....................................................................................................................................................117
3.7.1 Overall Baseband Planning Process........................................................................................................................117
3.7.2 Adding an Independent Baseband Board to the New Mode with Separate-MPT Configuration............................118
3.7.3 Adding an Independent Baseband Processing Board to the New Mode with Co-MPT Configuration...................120
3.7.4 Adding a New Mode to the Original Baseband Processing Board with Co-MPT Configuration...........................122
3.8 CPRI-based Topology Planning.................................................................................................................................124
3.8.1 Overall CPRI-based Topology Planning.................................................................................................................125
3.8.2 Chain Topology for RF Modules.............................................................................................................................126
3.8.3 Dual-Star Topology (Load Sharing) for SDR RF Modules.....................................................................................129
3.8.4 CPRI MUX for SDR RF Modules...........................................................................................................................133
3.9 Transmission Networking Planning...........................................................................................................................136
3.9.1 Transmission Networking Planning Process...........................................................................................................137
3.9.2 New Mode Using Independent Transmission with Separate-MPT Configuration..................................................139
3.9.3 New Mode Using the Transmission Port Provided by the Original Mode with Separate-MPT Configuration......141
3.9.4 New Mode Providing a Transmission Port Shared by the Original Mode with Separate-MPT Configuration......144
3.9.5 Co-Transmission for New and Original Modes with co-MPT Configuration.........................................................146
3.10 Equipment Auxiliary Planning.................................................................................................................................149
3.11 Summary of Mode Transition Planning....................................................................................................................156
3.11.1 License File Requirement......................................................................................................................................156
3.11.2 NE Software Version Requirement........................................................................................................................174
3.11.3 Board and Cable Installation Requirement............................................................................................................174
3.11.4 Data Configuration Requirement...........................................................................................................................178
3.11.5 Tool Requirements for Co-MPT Reconstruction...................................................................................................183
4 Mode Transition Examples......................................................................................................184

4.1 Example: Mode Transition from GU to GU+L (UCIU+UMPT)...............................................................................184
4.2 Example: Mode Transition from GO to GL...............................................................................................................198
4.3 Example: Mode Transition from GO to GU...............................................................................................................212
4.4 Example: Mode Transition from UO to UL...............................................................................................................221
4.5 Example: Mode Transition from GU to GU (CPRI MUX)+L (BBU Interconnection, Inter-BBU Triple-Mode SDR)
..........................................................................................................................................................................................228
4.6 Example: Mode Transition from GO to G*L.............................................................................................................242
4.7 Example: Mode Transition from UO to G*U.............................................................................................................250
4.8 Example: Mode Transition from GU to G[U*L]........................................................................................................259
4.9 Example: Mode Transition from GU to GU+L (UMPT+UMPT, BBU Interconnection)..........................................268
4.10 Example: Mode Transition from GU+L (UCIU+UMPT) to GU+LT (UCIU+UMPT)............................................279
4.11 Example: Mode Transition from LO to G*L CPRI Load Sharing4.8, 4.9...............................................................287
4.12 Example: Mode Transition from G*U to G*U*L (Outdoor BBU)..........................................................................294
4.13 Example: Mode Transition from LO (FDD) to LO (FDD+TDD)............................................................................303
4.14 Example: Mode Transition from LO (TDD) to LO (FDD+TDD)............................................................................309
Issue 03 (2016-12-09) Huawei Proprietary and Confidential iii

Copyright © Huawei
4.15 Example: Mode Transition from G*U*L(F) to G*U*L(FT)....................................................................................312

4.16 Example: Mode Transition from GO to G&L(M)....................................................................................................320
4.17 Example: Mode Transition from UO to U&L(M)....................................................................................................334
4.18 Example: Mode Transition from G&U to G&[U*L(M)].........................................................................................344
4.19 Example: Mode Transition from GO&L(F) to G&L(FM).......................................................................................354
4.20 Example: Mode Transition from U&L(F) to U&L(FM)..........................................................................................369
4.21 Example: Mode Transition from GO to G*L(M).....................................................................................................378
4.22 Example: Mode Transition from UO to U*L(M).....................................................................................................387
4.23 Example: Mode Transition from UO to U&L(M) for China Unicom......................................................................397
4.24 Example: Mode Transition from L(F) to L(FM)......................................................................................................408
4.25 Example: Mode Transition from L(T) to L(TM) for China Mobile.........................................................................417
4.26 Example: Mode Transition from G*U*L(FT) to G*U*L(FTM)..............................................................................423
4.27 Example: Mode Transition from G&L(T) to G&L(TM)..........................................................................................432
5 Mode Transition Implementation..........................................................................................439

5.1 Policies.......................................................................................................................................................................439
5.2 Procedure for Implementing Mode Transition...........................................................................................................440
6 Upgrading Base Station Software..........................................................................................441

6.1 Recording Base Station Status Before Mode Transition............................................................................................441
6.2 Upgrading Base Station Software..............................................................................................................................442
6.3 Upgrading Software of Base Stations in the Co-MPT Reconstruction Scenario.......................................................442
7 Applying for Licenses...............................................................................................................443

8 Preparing Data...........................................................................................................................444
8.1 Adding a BBU Interconnection Link on the GSM Side (UCIU)................................................................................444
8.2 Synchronizing Data Configuration.............................................................................................................................445
8.3 Preparing Data Using the Summary Data File...........................................................................................................451
8.3.1 Configuring GSM Data...........................................................................................................................................451
8.3.1.1 Preparing Equipment Data...................................................................................................................................452
8.3.1.1.1 Adjusting RF Data (GBTS)...............................................................................................................................452
8.3.1.1.2 Adjusting Equipment Data in Co-MPT Scenarios.............................................................................................456
8.3.1.2 Preparing Transmission Data................................................................................................................................463
8.3.1.2.1 Adjusting GBTS Data........................................................................................................................................463
8.3.1.2.2 Adjusting Co-MPT Data....................................................................................................................................467
8.3.1.3 Preparing Radio Data...........................................................................................................................................471
8.3.1.3.1 Adjusting GBTS Data........................................................................................................................................471
8.3.1.3.2 Adjusting Co-MPT Data....................................................................................................................................478
8.3.1.4 Preparing Transmission, Equipment, and Radio Adjustment Data (Co-MPT)....................................................481
8.3.2 Configuring UMTS Data.........................................................................................................................................484
8.3.2.1.1 Separate-MPT....................................................................................................................................................486
8.3.2.1.2 Co-MPT.............................................................................................................................................................490
Issue 03 (2016-12-09) Huawei Proprietary and Confidential iv

Copyright © Huawei

8.3.2.2.1 Separate-MPT....................................................................................................................................................498
8.3.2.2.2 Co-MPT.............................................................................................................................................................505
8.3.2.3.1 Separate-MPT....................................................................................................................................................508
8.3.2.3.2 Co-MPT.............................................................................................................................................................510
8.3.2.4 Adjusting Transmission, Device, and Radio Data................................................................................................513
8.3.2.4.1 Separate-MPT....................................................................................................................................................514
8.3.2.4.2 Co-MPT.............................................................................................................................................................533
8.3.3 Configuring LTE Data.............................................................................................................................................536
8.3.3.1.1 Separate-MPT....................................................................................................................................................537
8.3.3.1.2 Co-MPT.............................................................................................................................................................541
8.3.3.2.1 Separate-MPT....................................................................................................................................................549
8.3.3.2.2 Co-MPT.............................................................................................................................................................551
8.3.3.3.1 Separate-MPT....................................................................................................................................................554
8.3.3.3.2 Co-MPT.............................................................................................................................................................555
8.3.3.4 Adjusting Transmission, Equipment, Radio Data (LTE Only).............................................................................558
8.3.3.4.1 Separate-MPT....................................................................................................................................................559
8.3.3.4.2 Co-MPT.............................................................................................................................................................577
8.3.3.5 Adjusting Transmission, Equipment, Radio Data (FDD+TDD)..........................................................................580
8.3.3.6 Adjusting Transmission, Equipment, Radio Data (FDD+NB-IoT)......................................................................587
8.3.3.7 Adjusting Transmission, Equipment, Radio Data (TDD+NB-IoT)......................................................................593
8.4 Preparing Data Through Co-MPT Reconstruction, Mode Addition, and RF Adjustment.........................................599
8.4.1 Creating a Customized Project................................................................................................................................600
8.4.2 Exporting the Project Template and Filling In Co-MPT Reconstruction Data.......................................................603
8.4.3 Exporting Reconstruction Project Data...................................................................................................................603
8.4.4 Filling In Reconstruction Project Data....................................................................................................................606
8.4.5 Importing Reconstruction Project Data...................................................................................................................612
8.4.6 Exporting Scripts.....................................................................................................................................................613
8.5 Preparing Data Through New Co-MPT Base Station Deployment and Cell/Radio Parameter Inheritance..............614
8.5.1 Customizing the Summary Data File and Creating a Project..................................................................................622
8.5.2 Specifying NE Mapping for RF Migration.............................................................................................................626
8.5.3 Exporting Existing Base Station Data.....................................................................................................................627
8.5.4 Filling In Data for New Base Station Deployment and RF Migration....................................................................628
8.5.5 Importing Data.........................................................................................................................................................635
8.5.6 Exporting Scripts.....................................................................................................................................................636
8.6 Binding Base Station Multimode Relationships.........................................................................................................638
8.7 Checking MBTS Data Consistency............................................................................................................................639
8.8 Checking Data Preparations.......................................................................................................................................645
Issue 03 (2016-12-09) Huawei Proprietary and Confidential v

Copyright © Huawei
9 Setting NE Maintenance mode...............................................................................................646

10 Adjusting Hardware...............................................................................................................649
10.1 Adjusting Equipment................................................................................................................................................649
10.2 Adjusting Feeders.....................................................................................................................................................650
10.3 Adjusting Transmission Cables................................................................................................................................650
11 Activating Configuration Data and Commissioning.......................................................651

11.1 Activating Data in Incremental Scripts.....................................................................................................................651
11.2 Base Station Deployment by PnP.............................................................................................................................662
11.3 Base Station Deployment by USB............................................................................................................................666
11.4 PnP-based Co-MPT Reconstruction.........................................................................................................................687
12 Ending Maintenance Mode for NEs....................................................................................697

13 Appendix for Co-MPT Reconstruction...............................................................................698
13.1 Paths for Saving Converted Data.............................................................................................................................698
13.2 Preparing GSM Licenses..........................................................................................................................................699
13.3 What Should I Do If an Error Prompting "Data Preparation failed" Occurs During the Execution of a PnP Task?704
13.4 How Can I Roll Back Base Stations When Co-MPT Reconstruction Fails?...........................................................705
13.5 Constraints and Limitations......................................................................................................................................706
13.6 Description about Co-MPT Data Conversion..........................................................................................................712
13.6.1 Application Scenarios and Restrictions of the MBSC Reconstruction Module....................................................713
13.6.2 Application Scenarios and Restrictions of the GBTS Reconstruction Module.....................................................714
13.6.3 Application Scenarios and Restrictions of the SRAN Reconstruction Module....................................................714
13.7 Co-MPT Reconstruction Scenarios..........................................................................................................................716
13.7.1 GSM Co-MPT Reconstruction Scenario...............................................................................................................717
13.7.2 UMTS Co-MPT Reconstruction Scenario.............................................................................................................717
13.7.3 LTE Co-MPT Reconstruction Scenario.................................................................................................................718
13.7.4 GSM and UMTS Co-MPT Reconstruction Scenario............................................................................................718
13.7.5 GSM and LTE Co-MPT Reconstruction Scenario................................................................................................721
13.7.6 UMTS and LTE Co-MPT Reconstruction Scenario..............................................................................................724
13.7.7 G&[U*L] or U&[G*L]/L&[G*U] Reconstruction Scenario................................................................................726
13.7.8 GU+L Co-MPT Reconstruction Scenario.............................................................................................................728
13.7.9 GL+U Co-MPT Reconstruction Scenario.............................................................................................................731
13.7.10 G&[U*L]+[U*L] Reconstruction Scenario.........................................................................................................736
13.7.11 Two BBUs Combined into One Co-MPT Reconstruction...................................................................................737
14 Examples for Co-MPT Reconstruction and Mode Transition........................................743
Issue 03 (2016-12-09) Huawei Proprietary and Confidential vi

Copyright © Huawei
Mode Transition Guide(For NB) 1 Overview
1 Overview
1.1 About This Document

This document provides mode transition guidance for a base station. It mainly describes
operations during the mode transition to guide site engineers to plan and implement mode
transition. Some operations involved in this document, such as software upgrade, data
configuration by using the Configuration Management Express (CME), and engineering
quality check, are not detailed here because they have been described in the procedures of
new site deployment and routine maintenance. Instead, this document only provides reference
information for these operations.
1.2 Prerequisites
None.
Issue 03 (2016-12-09) Huawei Proprietary and Confidential 1

Copyright © Huawei
Mode Transition Guide(For NB) 2 Mode Transition
2 Mode Transition
Figure 1.1 Mode transition procedure

Copyright © Huawei
The following table describes procedures in the mode transition process.
Table 1.1 Procedure for mode transition of multimode base stations

Phase Item Operation
Preparation Planning mode transition 1. Make a data plan before

and after transition on
power consumption after
mode transition, type and
number of each board,
cable connections,
transmission scheme,
CPRI topology, and
reference clock.
2. Use the cabling tool on
the CME to analyze the
radio frequency (RF)
modules, slots, and CPRI
connections.
3. Prepare hardware.
4. Prepare software and
license files.
5. Use the CME to make a
data configuration file
required after mode
transition.
Upgrading software Skip this step if the base
station uses the software of
the target version.
Recording related Record the active alarms,
information cell status, service KPIs for
comparison before and after
mode transition.
Implementation Configuring data for co- An optional operation. In the
MPT reconstruction transition from a single-
mode base station to a co-
MPT multimode base
station, co-MPT
reconstruction must be
firstly performed.
Use the CME to perform
data conversion for co-MPT
reconstruction according to
the data plan.
Configuring data for Configure data for capacity
capacity expansion or mode expansion or mode addition
addition using the CME according to
the data plan.
Adjusting hardware Perform these two
operations in parallel to
Activating configuration

Copyright © Huawei
Phase Item Operation
data shorten the service

interruption duration.
Verification Commissioning base For the mode that has not
stations been deployed before the
mode transition, you are
advised to commission a
new mode as a newly
deployed base station
because the commissioning
methods are the same.
For the mode that has been
deployed before the mode
transition, commission the
mode in either of the
following ways:
 Checking engineering
quality and conduct a
dialing test if no major
changes are made to the
main control board and
transmission scheme.
 Commissioning the mode
as a newly deployed base
station if major changes
are made to the main
control board or
transmission scheme
Outputting engineering Summarize the reparenting
reports and make engineering
reports.
The NEP-SD tool can be used to analyze mode transition planning and design and prepare
configuration data. For details, see Guide to NEP-SD-based Base Station Design.

Copyright © Huawei
Mode Transition Guide(For NB) 3 Planning Mode Transition
3 Planning Mode Transition
This section describes the mode transition planning in terms of the radio frequency (RF),
antenna and feeder networking, co-MPT or separate-MPT, BBU interconnection, clock,
baseband, CPRI-based topologies, transmission, and equipment auxiliary.
3.1 Introduction
The base station system mainly consists of subsystems and other items shown in the following
figure: antennas, radio frequency (RF), CPRI cables, and others.
The following sections will cover planning operations for all these items and mode transition
requirements for the material, version, and others.
The following figure describes the constraints of these subsystems and other items on each
other.

Copyright © Huawei
Solid lines with arrows indicate the dependent objects and dotted lines with arrows point to
further information of specific objects.
Figure 1.2 Constraints of the subsystems and other items on each other
NB-IoT is introduced in SRAN12.0. The mode transition planning involves the following
aspects:
 RF planning
1. Power configuration
2. RF module specifications
For details, see CIoT12.1 eNodeB Product Specification.
 Antenna and feeder planning: the same as that for LTE FDD
 MPT planning
Mode Single- Transitio Dual- Transitio Triple- Transition

Copyright © Huawei
mode n to NB- mode n to NB- mode to NB-IoT

IoT IoT
Separat G(GBTS) G&M G&U G&[U*M G&U+L G&U+L*M
e-MPT ]
U U&M U&L U&[L*M G&L+U G&[L*M]
] +U
G&L G&[L*M G&[U*L] G&[U*L*M
] ]
Co- G(eGBTS) G(eGBTS G*U G*U*M G*U*L G*U*L*M
MPT )*M
U U*M U*L U*L*M
L L*M G*L G*L*M
T T*M U+L U+L*M
L*T L*T*M
Transition path for NB-IoT: Co-MPT is recommended on existing sites for the addition of
NB-IoT.
› Co-MPT is recommended for the addition of NB-IoT. If LTE FDD exists, NB-IoT must
share an MPT with LTE FDD.
› Separate-MPT between NB-IoT and GSM or NB-IoT and UMTS is supported.
 BBU interconnection: the same as that for LTE FDD
 Clock planning: the same as that for LTE FDD
 BBP planning
BBP planning for NB-IoT: LBBPd or UBBP boards work in LM concurrency mode on
existing sites. Do not adjust board slots.
› The BBP slot assignment principles are the same as those for L(FM) and L(F). (The
number of boards working in FM concurrency mode is the same as that working in LTE
only mode, that is six.)
› The board configuration principles for the UM concurrency mode are the same as those
for the UL concurrency mode. (For example, the co-MPT scenarios must support UM
baseband concurrency. Baseband processing boards must be installed in slots 2 and 3 of
a BBU3900. The BBU3910 is not subject to any slot restriction. Both the BBU3910 and
BBU3900 support a maximum of two boards working in UM mode.)
 CPRI networking planning
CPRI networking for NB-IoT: It is recommended that the CPRI networking be not
changed when NB-IoT is added on existing sites.
› In NB-IoT co-SDR scenarios, CPRI MUX is recommended for both separate-MPT and
co-MPT base stations.
 Transmission planning: the same as that for LTE FDD
 Equipment planning: the same as that for LTE FDD
 Summary of mode transition planning: the same as that for LTE FDD

Copyright © Huawei
3.2 RF Planning
This section describes RF planning.
3.2.1 Overall RF Planning Process

Figure 1.3 RF planning process
The overall process of RF module planning is as follows:

 Check whether to add a new frequency band or perform refarming.
This is determined based on the network planning.
 Check whether the original multiband module supports the new frequency band.
This is determined based on the module type and specifications.
You can determine whether the RF module supports the new frequency band based on the
value of Frequency band in the RF module sheet in SingleRAN Multi-mode BTS Product
Specification.
 Check whether the original multiband module supports the specifications after mode
transition.
This is determined based on the following items that have been planned by the customer:
mode, number of TRXs, power, TRX frequency, and numbers of RX and TX channels.
For details, see the RF module and RF Configuration & Output power sheets in
SingleRAN Multi-mode BTS Product Specification.
 Check whether the original multiband module supports the specifications after
refarming.
This is determined based on the following items that have been planned by the customer:
mode, number of TRXs, power, TRX frequency, and numbers of RX and TX channels.
For details, see the RF module and RF Configuration & Output power sheets in
SingleRAN Multi-mode BTS Product Specification.

Copyright © Huawei
Table 3.1 Scenario analysis

Category New Scenario
Band/Refar
ming
RF module New band 3.2.2Adding an RF Module

3.2.3Reusing the Original Multiband Module
Refarming 3.2.4Applying SDR to the Original RF Module
3.2.5Adding a Module to the Original SDR Module
3.2.6Replacing the Original Module with a New SDR
Module
 Configure an RF module supporting LTE TDD mode if the LTE TDD mode is added.
For details about the specifications of RF modules, see "RRU Specification" in LTE
TDD Product Specification.
3.2.2 Adding an RF Module

1. Module selection
The following items shall be taken into consideration for selecting an RF module: mode,
frequency band, number of TRXs, power, TRX frequencies, and numbers of RX and TX
channels that have been planned by the customer.
 For details about how to select a GSM, UMTS, LTE FDD, or multimode RF module, see
GUL Base Station Overview and Selection Guide.
 For details about how to select an LTE TDD RF module, see LTE TDD Solution Guide.
2. Precautions (hardware)
 Pay attention to the mapping relationship between the added module and cabinet:
The maximum transmit power of a radio frequency unit (RFU) varies from model to
model. For an RFU with a high transmit power, it has high requirements for power
distribution and heat dissipation of cabinets. Low-power RFUs are applicable to all types
of cabinets. High-power RFUs are applicable only to Ver.C cabinets, Ver.D cabinets,
upgraded cabinets that have the same capabilities as Ver.D cabinets, new cabinets, and
BTS3900AL (Ver.A) cabinets.
 Pay attention to requirements for power supply or power distribution.
3. Engineering guidelines
 Material requirement (hardware)
Material Type Material Name Quantity Remarks
RF module RRU/RFU See N/A

SRAN&GBSS&RAN
CPRI high-speed &eRAN BTS3900 For the RFU
cable Configuration
Manual.
CPRI fiber optic For the RRU
cable

Copyright © Huawei
Optical module For the RRU

RRU power cable For the RRU
RF interconnection Required by the
cable GSM, multimode,
and UMTS RF
modules
 Software version requirement

For details about the mapping relationship between the RF modules and versions, see 3900
Series Base Station Software and Hardware Compatibility Description for SRAN12.0.
 License requirement
To support the new mode, the hardware license of this mode must be purchased for the new
RF module, such as the power license and TRX license. The way of purchasing such a license
is the same as that for a single-mode RF module, and therefore details are not described here.
For a multiband RF module (except the RRU3961), one multimode multiband license is
required for each frequency band of each mode (GSM, UMTS, or LTE).
License License License License Sales Unit Mode

Control Control BBOM Abbreviati
Item Name Item Name on
(SBOM) (BBOM)
First Mode Multi-Mode 82205540 LGMIMMM Per band per G

First Band Multi-Band BRM RRU
License for License for
Multi-Band Multi-Band
RF Module RF Module
(GSM) (GSM) (Per
Band per
RRU)
Multi-Mode Multi-Mode 82205540 LGMIMMM Per band per G
Multi-Band Multi-Band BRM RRU
RF Module RF Module
(GSM) (GSM) (Per
Band per
RRU)
First Mode Multi-Mode 82205398 LQW9RFB Per band per U
First Band Multi-Band AND01 RRU
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)

Copyright © Huawei

(SBOM) (BBOM)
Multi-Mode Multi-Mode 82205398 LQW9RFB Per band per U

Multi-Band Multi-Band AND01 RRU
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)
First Mode Multi-Mode 82205382 LLT1MML Per band per L
First Band Multi-Band MBRM01 RRU
RF Module RF Module
(LTE FDD) (LTE FDD)
(Per Band
per RRU)
Multi-Mode Multi-Mode 82205382 LLT1MML Per band per L
Multi-Band Multi-Band MBRM01 RRU
RF Module RF Module
(LTE FDD) (LTE FDD)
(Per Band
per RRU)
First Mode Multi-Mode 82207097 LML1MML Per band per L
First Band Multi-Band MBR01 RRU
RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)
Multi-Mode Multi-Mode 82207097 LML1MML Per band per L
Multi-Band Multi-Band MBR01 RRU
RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)
For the RRU3961, the RF 800 MHz/900 MHz multiband license must be purchased if the
RRU3961 works on both the 800 MHz and 900 MHz frequency bands.

Copyright © Huawei
License Control License License License Sales Mod

Item Name Control Item BBOM Abbreviati Unit e
(SBOM) Name on
(BBOM)
RF 800M/900M RF 82204034 LLT1RFM Per L

Multi Band license 800M/900M B01 band
Multi Band per
license RRU
For the RRU3961 and single-band module, the RF multimode license corresponding to each
mode must be purchased if SDR is used on one frequency band.
Sce Module License License Licens License Sales Mo

nar Type Control Control e Abbreviati Unit de
io Item Name Item BBOM on
(SBOM) Name
(BBOM)
GU Non-blade GSM/UMTS The 822011 LQW9MBT Per U

module Dual Mode number of 99 SRF02 sector
license RF Units
with
GSM/UM
TS dual
mode
function
enabled
Blade&A GSM/UMTS The 822011 LQW9MBT Per U
AU Dual Mode number of 99 SRF02 sector
license for RF Units
Blade&AAU with
GSM/UM
TS dual
mode
function
enabled
GL Non-blade GSM/LTE GSM/LTE 822014 LLT1GLDM Per L
module Dual Mode Dual 72 01 sector
license Mode
license(per
Sector)
Blade&A GSM/LTE GSM/LTE 822014 LLT1GLDM Per L
AU Dual Mode Dual 72 01 sector
license for Mode
Blade&AAU license(per
Sector)
UL Non-blade UMTS/LTE UMTS/LT 822014 LLT1ULDM Per L
module Dual Mode E Dual 73 01 sector
license Mode

Copyright © Huawei

(SBOM) Name
(BBOM)
license(per
Sector)
Blade&A UMTS/LTE UMTS/LT 822014 LLT1ULDM Per L
AU Dual Mode E Dual 73 01 sector
license for Mode
Sector)
GU Non-blade RF N/A N/A N/A Per U+
L module GSM/UMTS sector L
Dual Mode
license + RF
GSM/LTE
Dual Mode
license
or
RF
GSM/UMTS
Dual Mode
license + RF
UMTS/LTE
Dual Mode
license
Blade&A GSM/UMTS N/A N/A N/A Per U+
AU Dual Mode sector L
license for
Blade&AAU
+ GSM/LTE
Dual Mode
license for
Blade&AAU
or
GSM/UMTS
Dual Mode
license for
Blade&AAU
+
UMTS/LTE
Dual Mode
license for
Blade&AAU
NB- N/A N/A N/A N/A N/A N/A N/A
IoT
only
X+ Non-blade RF Multi- RF Multi- 822070 LML1RFML Per L

Copyright © Huawei

(SBOM) Name
(BBOM)
NB- module Mode Mode 96 01 sector

IoT license (NB- license
(X IoT) (per
indi Sector)
cate (NB-IoT)
s
GS Blade&A RF Multi- RF Multi- 822070 LML1RFML Per L
M, AU Mode Mode 96 01 sector
UM license for license
TS, Blade&AAU (per
or (NB-IoT) Sector)
LT (NB-IoT)
E.)
X+ Non-blade RF Multi- N/A N/A N/A N/A N/A
X+ module Mode
NB- license (NB-
IoT IoT) + (X+X)
(X Multi-Mode
indi Sector
cate license
s (stated
GU, above)
GL,
or Blade&A RF Multi- N/A N/A N/A N/A N/A
UL. AU Mode
) license for
Blade&AAU
(NB-IoT) +
(X+X) Multi-
Mode Sector
license
(stated
above)
 Data configuration requirement (software)

Data configuration for adding an RF module is the same as that in single-mode scenarios.
You can use the GUI, summary data file, or MML commands to configure the data.
For the data configuration guidelines, see section "Data Preparation" in "Engineering
Guidelines (Multimode Base Station)" of RF Unit and Topology Management Feature
Parameter Description.
Pay attention to the following during data configuration:
- Determine the CPRI-based topology according to topology types supported by an RF
module in multimode scenarios.

Copyright © Huawei
- Configure the working mode of an RF module according to the live network deployment.
- The following describes the working mode of an RF module for NB-IoT.
In a separate-MPT NB-IoT/GSM/UMTS scenario, the working mode of an RF module for
NB-IoT needs to be configured. On the NB-IoT side, set the working mode to the one in
which the RF module works. For example, if GSM and NB-IoT share an RF module, set the
working mode of the RF module to GM.
For other separate-MPT scenarios, such as the separate-MPT GSM/UMTS scenario, the
working mode of an RF module for NB-IoT cannot be configured if the base station version is
SRAN12.0 or earlier. In these scenarios, set the working mode of an RF module for NB-IoT
to LTE. For example, if GSM and NB-IoT share an RF module, set the working mode of the
RF module to GL. If GSM, UMTS, and NB-IoT share an RF module, set the working mode
of the RF module to GM. (The RF module runs normally and does not affect services if the
working mode is set to GL.)
Determine the parameters and their values to be configured according to the guide and specify
them in the following table. The following table provides the major eGBTS/UMTS/LTE
parameters and their value examples. The BTSTRXBRD MOC is for the GBTS.
Domain Configurat MOC Paramete Parameter Value

ion Object r Name ID (Example)
RF module Adding an RRU Cabinet CN 0

RXU No.
Adding an RRU Subrack SRN 60
RXU No.
Adding an RRU Slot No. SN 3
RXU
Adding an RRU RRU type RT MRRU
RXU
Adding an RRU Topo TP TRUNK(TRUNK
RXU Position )
Adding an RRU RRU RCN 0
RXU Chain/Rin
g No.
Adding an RRU RRU PS 0
RXU Position
Adding an RRU RF Unit RS GL
RXU Working
Mode
Adding an RRU Number of RXNUM 2
RXU RX
channels
Adding an RRU Number of TXNUM 2
RXU TX
channels

Copyright © Huawei
 Service impact
Scenario Impact on Services of the Original Mode
Adding a new RF mode and adjusting Services of the original RF module are affected
the antenna and feeder of the original RF during the antenna and feeder adjustment.
module
Adding a new RF module and adjusting Services are affected during the data
the data configuration of the original RF configuration and RF module adjustment.
module
3.2.3 Reusing the Original Multiband Module

1. Module selection
Reuse the original module.
2. Precautions (hardware)
Check whether the antenna and feeder subsystem supports the new frequency band that is
added to the original module.
RF module CPRI fiber optic Same as the number Determine whether

cable of RF modules to add a fiber optic
cable based on the
CPRI-based
topology.
Optical module Twice the number of Determine whether
RF modules to add a fiber optic
cable based on the
CPRI-based
topology.
 Version requirement (software)

For details about the mapping relationship between RF modules and versions, see 3900 Series
Base Station Software and Hardware Compatibility Description for SRAN12.0.
 License requirement (software)

Copyright © Huawei

(SBOM) (BBOM)

RF Module RF Module
(GSM) (GSM) (Per
Band per
RRU)
RF Module RF Module
(GSM) (GSM) (Per
Band per
RRU)
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)
RF Module RF Module
(LTE FDD) (LTE FDD)
(Per Band
per RRU)
RF Module RF Module
(LTE FDD) (LTE FDD)

Copyright © Huawei

(SBOM) (BBOM)
(Per Band
per RRU)
RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)
RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)

(SBOM) Name on
(BBOM)

Multi Band per
license RRU

Data configuration for adding an RF module is the same as that in single-mode scenarios.
For SRAN12.0, see section "Data Preparation" in "Engineering Guidelines (Multimode Base
Station)" of RF Unit and Topology Management Feature Parameter Description.
- Configure sector equipment parameters according to the type of a multiband module:
sharing the same DIN connector or using different DIN connectors.

Copyright © Huawei


RF module Modifying RRU Cabinet CN 0

an RXU No.
Modifying RRU Subrack SRN 60
an RXU No.
Modifying RRU Slot No. SN 3
an RXU
Modifying RRU RRU type RT MRRU
an RXU
Modifying RRU Topo TP TRUNK(TRUNK
an RXU Position )
Modifying RRU RRU RCN 0
an RXU Chain/Rin
g No.
Modifying RRU RRU PS 0
an RXU Position
Modifying RRU RF Unit RS GL
an RXU Working
Mode
Modifying RRU Number of RXNUM 2
an RXU RX
channels
Modifying RRU Number of TXNUM 2
an RXU TX
channels
 Service impact

Copyright © Huawei
Starting a new mode or modifying RRU Services of the original mode are affected
configurations during the short startup or modification
duration (no CS call drop but 2-3-second
interruption of PS services).
3.2.4 Applying SDR to the Original RF Module

1. Module selection
The original module is reused, and therefore no module selection is required.
2. Precautions
None
RF module CPRI fiber optic Same as the number Determine whether

cable of RF modules to add a fiber optic
cable based on the
CPRI-based
topology.
Optical module Twice the number of Determine whether
RF modules to add a fiber optic
cable based on the
CPRI-based
topology.
 Version requirement
For details about the mapping relationship between the RF modules and versions, see 3900
Series Base Station Software and Hardware Compatibility Description for SRAN12.0.

(SBOM) (BBOM)


Copyright © Huawei

(SBOM) (BBOM)

RF Module RF Module
(GSM) (GSM) (Per
Band per
RRU)
RF Module RF Module
(GSM) (GSM) (Per
Band per
RRU)
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)
RF Module RF Module
(LTE FDD) (LTE FDD)
(Per Band
per RRU)
RF Module RF Module
(LTE FDD) (LTE FDD)
(Per Band
per RRU)

Copyright © Huawei

(SBOM) (BBOM)

RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)
RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)

(SBOM) Name on
(BBOM)

Multi Band per
license RRU

(SBOM) Name
(BBOM)

license RF Units
with
GSM/UM
TS dual
mode

Copyright © Huawei

(SBOM) Name
(BBOM)
function
enabled
Blade&AAU with
GSM/UM
TS dual
mode
function
enabled
license Mode
license(per
Sector)
license for Mode
Sector)
license Mode
license(per
Sector)
license for Mode
Sector)
Dual Mode
license + RF
GSM/LTE
Dual Mode
license
or
RF
GSM/UMTS
Dual Mode
license + RF
UMTS/LTE

Copyright © Huawei

(SBOM) Name
(BBOM)
Dual Mode
license
license for
Blade&AAU
+ GSM/LTE
Dual Mode
license for
Blade&AAU
or
GSM/UMTS
Dual Mode
license for
Blade&AAU
+
UMTS/LTE
Dual Mode
license for
Blade&AAU
IoT
only
(X IoT) (per
indi Sector)
cate (NB-IoT)
s
TS, Blade&AAU (per
or (NB-IoT) Sector)
LT (NB-IoT)
E.)
X+ module Mode
NB- license (NB-
IoT IoT) + (X+X)
(X Multi-Mode
indi Sector
cate license
s (stated

Copyright © Huawei

(SBOM) Name
(BBOM)
GU, above)
GL,
UL. AU Mode
) license for
the blade
RRU and
AAU (NB-
IoT) + (X+X)
Multi-Mode
Sector
license
(stated
above)

Original mode:
The original working mode of the RF module must be changed.
New mode:
Data configuration is the same as that for adding an RF module. Note that the working mode
of the RF module must be correctly configured.

Copyright © Huawei

RF module Modifying RRU Cabinet CN 0

an RXU No.
Modifying RRU Subrack SRN 60
an RXU No.
Modifying RRU Slot No. SN 3
an RXU
Modifying RRU RRU type RT MRRU
an RXU
Modifying RRU Topo TP TRUNK(TRUNK
an RXU Position )
Modifying RRU RRU RCN 0
an RXU Chain/Rin
g No.
Modifying RRU RRU PS 0
an RXU Position
Modifying RRU RF Unit RS GL
an RXU Working
Mode
Modifying RRU Number of RXNUM 2
an RXU RX
channels
Modifying RRU Number of TXNUM 2
an RXU TX
channels
 Service impact
Starting a new mode or modifying RRU The startup or modification duration is short (no
configuration affects services of the CS call drop but 2-3-second interruption of PS
original mode. services).
The original RF module is a legacy V1 Adjusting the working mode of the original
or V2 RF module. mode resets RRUs, interrupting services for one
minute.

Copyright © Huawei
3.2.5 Adding a Module to the Original SDR Module

1. Module selection
The following items shall be taken into consideration for selecting an RF module:
Mode, frequency band, number of TRXs, power, TRX frequencies, and numbers of RX and
TX channels that have been planned by the customer.
 For details about how to select a GSM, UMTS, LTE FDD, or multimode RF module, see
GUL Base Station Overview and Selection Guide.
 For details about how to select an LTE TDD RF module, see LTE TDD Solution Guide.
Note:
 RF modules of the same type are preferred for capacity expansion in the same cell.
 If the original module is end of marketing (EOM) or cannot meet capacity requirements
after mode transition, modules of different types can be configured together. For details,
see GUL RF Module Mixed Configuration Guide.
2. Precautions
 Pay attention to the mapping relationship between the added module and cabinet:
The maximum transmit power of an RFU varies by RFU model. The higher transmit
power of an RFU indicates higher requirements for power distribution and heat
dissipation of the cabinet. Therefore, RFUs of low power can work with all cabinets
while RFUs of high power can work only with Ver.C cabinets, Ver.D cabinets (or the
ones have equivalent capabilities after upgrade), new cabinets, and the BTS3900AL
(Ver.A) cabinets.
 Material requirement
Board RRU/RFU See N/A

SRAN&GBSS&RAN
CPRI high-speed &eRAN BTS3900 For the RFU.
cable Configuration Replace the original
Manual. CPRI cable if it
cannot be reused.
cable
Optical module For the RFU.
Replace the original
optical module if it
cannot be reused.
RRU power cable For the RFU.
RRU power cable if
it cannot be reused.
RF interconnection Required by the
cable GSM, multimode,

Copyright © Huawei
and UMTS RF
modules
Hardware license of the single-mode RF module working in the original mode:
If the original module is a non-blade or non-AAS module, replace it with a blade or AAS
module. In such a case, the related hardware license of the single-mode RF module must be
purchased. The way of purchasing such a license is the same as that for a single-mode RF
module, and therefore details are not described here.
Hardware license of the single-mode RF module working in the new mode:
Multimode RF license

(SBOM) (BBOM)

RF Module RF Module
(GSM) (GSM) (Per
Band per
RRU)
RF Module RF Module
(GSM) (GSM) (Per
Band per
RRU)

Copyright © Huawei

(SBOM) (BBOM)
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)
RF Module RF Module
(LTE FDD) (LTE FDD)
(Per Band
per RRU)
RF Module RF Module
(LTE FDD) (LTE FDD)
(Per Band
per RRU)
RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)
RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)

Copyright © Huawei

(SBOM) Name on
(BBOM)

Multi Band per
license RRU

(SBOM) Name
(BBOM)

license RF Units
with
GSM/UM
TS dual
mode
function
enabled
Blade&AAU with
GSM/UM
TS dual
mode
function
enabled
license Mode
license(per
Sector)
license for Mode
Sector)

Copyright © Huawei

(SBOM) Name
(BBOM)

license Mode
license(per
Sector)
license for Mode
Sector)
Dual Mode
license + RF
GSM/LTE
Dual Mode
license
or
RF
GSM/UMTS
Dual Mode
license + RF
UMTS/LTE
Dual Mode
license
license for
Blade&AAU
+ GSM/LTE
Dual Mode
license for
Blade&AAU
or
GSM/UMTS
Dual Mode
license for
Blade&AAU
+
UMTS/LTE
Dual Mode
license for
Blade&AAU
IoT

Copyright © Huawei

(SBOM) Name
(BBOM)
only
(X IoT) (per
indi Sector)
cate (NB-IoT)
s
TS, Blade&AAU (per
or (NB-IoT) Sector)
LT (NB-IoT)
E.)
X+ module Mode
NB- license (NB-
IoT IoT) + (X+X)
(X Multi-Mode
indi Sector
cate license
s (stated
GU, above)
GL,
UL. AU Mode
) license for
Blade&AAU
(NB-IoT) +
(X+X) Multi-
Mode Sector
license
(stated
above)
 Data configuration requirement

Original mode:
 The original RF module's working mode must be adjusted.
 TRX configuration of the original mode may be changed, such as a decrease in the TRX
number due to refarming and changes in RF channels of TRXs).
New mode:

Copyright © Huawei


RXU No.
RXU No.
RXU
RXU
RXU Position )
RXU Chain/Rin
g No.
RXU Position

Copyright © Huawei

RXU Working
Mode
RXU RX
channels
RXU TX
channels
 Service impact
Starting a new mode or modifying RRU The startup or modification duration is short (no
configuration affects services of the CS call drop but 2-3-second interruption of PS
original mode. services).
3.2.6 Replacing the Original Module with a New SDR Module

1. Module selection
The following items shall be taken into consideration for selecting an RF module:
Mode, frequency band, number of TRXs, power, TRX frequencies, and numbers of RX and
TX channels that have been planned by the customer.
For details about the selection, see GUL Base Station Overview and Selection Guide.
2. Precautions
 To replace the RF module, pay attention to the mapping relationship between the new
module and cabinet:
The maximum transmit power of an RFU varies from model to model. For an RFU with
a high transmit power, it has high requirements for power distribution and heat
dissipation of cabinets. Low-power RFUs are applicable to all types of cabinets. High-
power RFUs are applicable only to Ver.C cabinets, Ver.D cabinets, upgraded cabinets
that have the same capabilities as Ver.D cabinets, new cabinets, and BTS3900AL (Ver.A)
cabinets.
 To replace the RF module, check whether the optical module needs to be replaced
according to the number of cells carried on the RF module and bandwidth specifications.
 To replace the RF module, check whether the RRU power cable needs to be replaced.

Copyright © Huawei
Board RRU/RFU Determined based N/A

on the plan
CPRI high-speed For the RFU.
cable Replace the original
CPRI cable if it
cannot be reused.
cable
Optical module For the RFU.
optical module if it
cannot be reused.
RRU power cable For the RFU.
RRU power cable if
it cannot be reused.
Hardware license of the single-mode RF module working in the original mode:
If the original module is a non-blade or non-AAS module, replace it with a blade or AAS
module. In such a case, the related hardware license of the single-mode RF module must be
purchased. The way of purchasing such a license is the same as that for purchasing a license
for a single-mode RF module, and therefore, details are not described here.
Hardware license of the single-mode RF module working in the new mode:
Multimode RF license

(SBOM) (BBOM)

RF Module RF Module

Copyright © Huawei

(SBOM) (BBOM)
(GSM) (GSM) (Per

Band per
RRU)
RF Module RF Module
(GSM) (GSM) (Per
Band per
RRU)
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)
RF Module RF Module
(UMTS) (UMTS)
(Per Band
per RRU)
RF Module RF Module
(LTE FDD) (LTE FDD)
(Per Band
per RRU)
RF Module RF Module
(LTE FDD) (LTE FDD)
(Per Band
per RRU)

Copyright © Huawei

(SBOM) (BBOM)
RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)
RF Module RF Module
(Per Band (Per Band
per RRU) per RRU)
(NB-IoT) (NB-IoT)

(SBOM) Name on
(BBOM)

Multi Band per
license RRU

(SBOM) Name
(BBOM)

license RF Units
with
GSM/UM
TS dual
mode
function
enabled

Copyright © Huawei

(SBOM) Name
(BBOM)

Blade&AAU with
GSM/UM
TS dual
mode
function
enabled
license Mode
license(per
Sector)
license for Mode
Sector)
license Mode
license(per
Sector)
license for Mode
Sector)
Dual Mode
license + RF
GSM/LTE
Dual Mode
license
or
RF
GSM/UMTS
Dual Mode
license + RF
UMTS/LTE
Dual Mode
license

Copyright © Huawei

(SBOM) Name
(BBOM)

license for
Blade&AAU
+ GSM/LTE
Dual Mode
license for
Blade&AAU
or
GSM/UMTS
Dual Mode
license for
Blade&AAU
+
UMTS/LTE
Dual Mode
license for
Blade&AAU
IoT
only
(X IoT) (per
indi Sector)
cate (NB-IoT)
s
TS, Blade&AAU (per
or (NB-IoT) Sector)
LT (NB-IoT)
E.)
X+ module Mode
NB- license (NB-
IoT IoT) + (X+X)
(X Multi-Mode
indi Sector
cate license
s (stated
GU, above)
GL,

Copyright © Huawei

(SBOM) Name
(BBOM)
UL. AU Mode
) license for
Blade&AAU
(NB-IoT) +
(X+X) Multi-
Mode Sector
license
(stated
above)

Original mode:
 The original RF module's working mode must be adjusted.
 TRX configuration of the original mode may be changed, such as a decrease in the TRX
number due to refarming and changes in RF channels of TRXs).
New mode:
- Set the RXUSPEC parameter to the name of the new RF module for the GBTS. The
RUSPEC parameter is optional for the eGBTS, NodeB, and eNodeB.

Copyright © Huawei


RXU No.
RXU No.
RXU
RXU
RXU Position )
RXU Chain/Rin
g No.
RXU Position
RXU Working
Mode
RXU RX
channels
RXU TX
channels
 Service impact
Replacing the RRU Services carried by the original RFU or RRU

will be affected when it is being replaced. The
interruption period varies by installation period.
If there is an extra slot for installing the new
RRU, you can pre-install the RRU and then
adjust the antenna & feeder and CPRI cables.
This can reduce the service interruption period
to a few minutes.

Copyright © Huawei
3.3 Antenna and Feeder Networking

This section describes antenna and feeder planning.
3.3.1 Overall Antenna and Feeder Planning Process

Figure 1.4 Overall antenna and feeder planning process
 Check whether the original antenna supports the new frequency band.
In this step, obtain the antenna model so that you can find the datasheet of the original
antenna.

Copyright © Huawei
 Check whether to replace the original antenna or add a new antenna.

This is determined based on customer's plan.
If you need to add a new antenna, pay attention to its installation position.
If replacement of the original antenna is required, be aware of the impact when compared
with the original mode. For example, difference between the benefits of the original and
replacement antennas may affect network performance.
 Check whether the new and original frequency bands share the same antenna port.
In this step, obtain the antenna model so that you can find the datasheet of the original
antenna.
The datasheet indicates whether the original antenna port supports the broadband antenna. If
the broadband antenna is supported, the new and original frequency bands can share the same
antenna port.
Note that if the original and new RF modules work on independent frequency bands, an
external inter-band combiner must be added for combing the original and new frequency
bands so that the two RF modules can share the same antenna port.
Generally, broadband antennas share the same port, and therefore two frequency bands on
these antennas do not support independent remote electrical tilt (RET).
Table 4.1 Analysis of antenna and feeder planning scenarios

Categor RF Scenario
y module
Antenna New 3.3.2Adding an Independent Antenna (Antenna Port) and an

and mode Independent Feeder
feeder only
networki 3.3.3Adding an Independent Antenna (Antenna Port) and Sharing
ng the Original Feeder
3.3.4Broadband Antenna (Antenna Port) Being Shared By the
Original Mode and New Mode
SDR RF 3.3.5SDR RF Module of the New Mode Using the Original Feeder
module
In F+T scenarios, intermodulation interference and spurious interference may occur on an

antenna working in LTE FDD and LTE TDD modes. It is recommended that LTE FDD and
LTE TDD use separate antennas and feeders. For details about how to add an antenna, see
section 3.3.2.
3.3.2 Adding an Independent Antenna (Antenna Port) and an

Independent Feeder
1. Scenario description and application scope

Copyright © Huawei
Figure 1.5 Scenario without RET

Copyright © Huawei
Figure 1.6 Scenario with RET

Copyright © Huawei
Figure 1.7 Scenario with TMA+RET
In this scenario of mode transition, an RF module working on the new frequency band uses an
independent set of antenna and feeder. In such a case, you can use an independent antenna or
reuse the original multiband multi-port antenna. In addition, customers may replace the
original antenna with a multiband multi-port antenna due to constraints on site conditions.
This scenario has the following characteristics:
 Independent antenna (antenna port)
 Independent feeder or jumper
 If an RET antenna is used, independent RET and electrical tilt configuration are
supported.
 If an independent antenna is used, you can independently set the mechanical tilt.
2. Precautions
 In scenarios of adding an RET or TMA, check the model, and hardware and software
versions of RET or TMA for compatibility. For details, contact Global Technical
Assistance Center (GTAC) or Technical Management Office (TMO) teams. A list of RET
or TMA models that have passed the interoperability test (IOT) compatibility test is
available. If the RET or TMA to be added is not included in the list, relevant tests by
R&D or field engineers are recommended.
 Pay attention to frequency bands supported by the TMA, especially the reused TMA.

Copyright © Huawei
 The RRU is directly connected to the RET through an RET port. Only AISG cables
delivered by Huawei can be used and special attention shall be paid to cable and length
constraints.
Table 7.1 Material requirement

Antenna and feeder Antenna Same as the number Required when the
of sectors in the new original antenna is to
mode be reconstructed or
replaced
Feeder Twice the number of Not required when
sectors the RRU and
antenna are directly
connected to each
other.
The length of the
feeder needs to be
determined
according to the site
survey.
Jumper N/A The length of the
feeder needs to be
determined
survey.
SBT Same as the number Required on the
of sectors antenna side when
the following
conditions are met:
 RET is configured
for the new
mode.
 No TMA is
configured.
 The RRU and
antenna are not
directly
connected to
each other.
TMA Same as the number Configured as
of sectors required by the
network plan.
RCU Same as the number Required when RET
of sectors is required but no
internal RET is

Copyright © Huawei
available.
AISG cable from the Same as the number Required for
SBT or TMA to the of sectors connecting to the
RCU SBT or TMA when
RET is required. The
lengths of the AISG
cable vary with
scenarios.
AISG cable from the Same as the number Required when the
RRU to the RCU of sectors RRU and RET are
directly connected to
each other.
None
The GSM and UMTS systems have no requirements for deploying this feature.
The feature license must be purchased when RET is used for LTE. The following table
provides the related license control items.
Table 7.2 License control items for optional features of RET management
Feature Name License Control Item License Abbreviation
(LTE-FDD) LOFD-001024 Remote Electrical Tilt LLT1RET01

Remote Electrical Tilt Control Control
(LTE-TDD) TDLOFD-001024 Remote Electrical Tilt LLT1RET01

Data configuration for a multimode antenna is the same as that for a set of single-mode
antenna.
Key points for the data configuration are listed as follows:
- Based on connections of the RFU/RRU, antenna, and feeder, configure RF transmit and
receive mode for the GBTS, and TxBranch/RxBranch/RFCONNGRP information about the
RF module for the eGBTS, NodeB, eNodeB, and co-MPT base station.
- If RET is required, configure the ALD power supply switch for the RRU or RFU and related
alarm threshold parameters. ALD is short for antenna line device. In addition, configure RET
for the RET antenna, download the RET configuration file, calibrate the RET antenna, and set
tilt angels.
- If a TMA is required, configure the TMA and TMA attenuation corresponding to the RRU or
RFU's channel.

Copyright © Huawei
For SRAN12.0, see section "Data Preparation" in "Engineering Guidelines (ALD Manual
Deployment on Multimode Base Station)" of ALD Management Feature Parameter
Description.
Examples:
The following table describes the key parameters that must be set when RET is controlled by
the RRU or RFU through its RETPORT.
Table 7.3 Key parameters related to the RETPORT

Domain Configur MOC Parameter Paramete Example Value
ation Name r ID
Object
Antenna Adding an RETPORT Cabinet No. CN 0

and RXU
feeder
Adding an RETPORT Subrack No. SRN 62
RXU
Adding an RETPORT Slot No. SN 0
RXU
Adding an RETPORT Port No. PN RET_PORT
RXU
Adding an RETPORT ALD Power PWRSWI ON
RXU Switch TCH
Adding an RETPORT Current Alarm THRESH UER_SELF_DEF
RXU Threshold OLDTYP INE
E
Adding an RETPORT Undercurrent UOTHD 40
RXU Alarm Occur
Threshold
Adding an RETPORT Undercurrent UCTHD 60
RXU Alarm Clear
Threshold
Adding an RETPORT Overcurrent OOTHD 850
RXU Alarm Occur
Threshold
Adding an RETPORT Overcurrent OCTHD 750
RXU Alarm Clear
Threshold
The following table describes the key parameters that must be set when RET is controlled by
the RRU or RFU through its ANTENNAPORT.

Copyright © Huawei
Table 7.4 Key parameters related to the ANTENNAPORT

Domain Configuratio MOC Paramete Paramete Example
n Object r Name r ID Value
Antenna and Adding an ANTENNAPO Cabinet CN 0

feeder RXU RT No.
Adding an ANTENNAPO Subrack SRN 62
RXU RT No.
Adding an ANTENNAPO Slot No. SN 0
RXU RT
Adding an ANTENNAPO Port No. PN R0A
RXU RT
Adding an ANTENNAPO ALD PWRSWI ON
RXU RT Power TCH
Switch
Adding an ANTENNAPO Current THRESH UER_SEL
RXU RT Alarm OLDTYP F_DEFINE
Threshold E
Adding an ANTENNAPO Undercurr UOTHD 40
RXU RT ent Alarm
Occur
Threshold
Adding an ANTENNAPO Undercurr UCTHD 60
RXU RT ent Alarm
Clear
Threshold
Adding an ANTENNAPO Overcurre OOTHD 850
RXU RT nt Alarm
Occur
Threshold
Adding an ANTENNAPO Overcurre OCTHD 750
RXU RT nt Alarm
Clear
Threshold
Table 7.5 Key parameters related to the RET antenna

Do Configu MO Parameter Name Parameter ID Example
mai ration C Value
n Object
Ant Adding RET Device No. DEVICENO 1

enn RET
a
and Adding RET Control Port Cabinet CTRLCN 0
feed RET No.

Copyright © Huawei

mai ration C Value
n Object
er Adding RET Control Port Subrack CTRLSRN 62

RET No.
Adding RET Control Port Slot No. CTRLSN 0
RET
Adding RET Antenna Type RETTYPE Single antenna
RET
Adding RET RET Subunit Number SUBUNITNUM 1
RET
Adding RET Polar Type POLARTYPE Equipment
RET plan
Adding RET Antenna Scenario SCENARIO REGULAR
RET
Table 7.6 Key parameters related to the RET subunit

Domain Configurat MOC Parameter Parameter Example
ion Object Name ID Value
Antenna and Adding RET RETSUBU Device No. DEVICEN 1

feeder NIT O
Adding RET RETSUBU Subunit No. SUBUNITN 1
NIT O
Adding RET RETSUBU Connect Port CONNCN1 0
NIT 1 Cabinet
No.
Adding RET RETSUBU Connect Port CONNSRN 62
NIT 1 Subrack 1
No.
Adding RET RETSUBU Connect Port CONNSN1 0
NIT 1 Slot No.
Adding RET RETSUBU Connect Port CONNPN1 R0A
NIT 1 Port No.
NIT 2 Cabinet
No.
NIT 2 Subrack 2
No.
Adding RET RETSUBU Tilt TILT 20

Copyright © Huawei

NIT
Table 7.7 Key parameters related to the TMA

mai ration C Value
n Object
Ant Adding a TMA Device No. DEVICENO 2

enn TMA
a
and Adding a TMA Control Port Cabinet CTRLCN 0
feed TMA No.
er
Adding a TMA Control Port Subrack CTRLSRN 62
TMA No.
Adding a TMA Control Port Slot No. CTRLSN 0
TMA
Adding a TMA TMA Subunit Number SUBUNITNUM 1
TMA
Table 7.8 Key parameters related to the TMA subunit

Do Configur MOC Parameter Name Parameter ID Example
mai ation Value
n Object
Ante Adding a TMA Device No. DEVICENO 2

nna TMA
and
feed Adding a TMA Subunit No. SUBUNITNO 1
er TMA
Adding a TMA Connect Port CONNCN 0
TMA Cabinet No.
Adding a TMA Connect Port CONNSRN 62
TMA Subrack No.
Adding a TMA Connect Port Slot CONNSN 0
TMA No.
Adding a TMA Connect Port No. CONNPN R0A
TMA
Adding a TMA Working Mode MODE NORMA
TMA L
Adding a TMA Gain GAIN 48

Copyright © Huawei

mai ation Value
n Object
TMA
If both RX channels of the RXU are configured with the TMA, attenuation must be
configured for the RXBRANCH of both RX channels. The following table describes the
parameters that must be set to configure RX channel attenuation.
Table 7.9 Key parameters related to RX channel attenuation

mai ation Value
n Object
Ante Adding RXBRANCH RX Channel No. RXNO 0

nna RXU RX
and channel 0
feed
er Adding RXBRANCH Logical Switch of RXSW ON
RXU RX RX Channel
channel 0
Adding RXBRANCH Attenuation ATTEN 10
RXU RX
channel 0
nna RXU RX
and channel 1
feed
RXU RX RX Channel
channel 1
RXU RX
channel 1
 Service impact
Table 7.10 Service impact

Adding an antenna or reusing Technically, services of the original mode are not
the original multiband antenna affected. However, the related operations are performed
around antennas, you are advised to evaluate whether
the original RF module shall be blocked based on the
actual site conditions to ensure personal safety.

Copyright © Huawei
Replacing the original antenna Services of the original mode are interrupted during
with a multiband antenna antenna replacement.
3.3.3 Adding an Independent Antenna (Antenna Port) and

Sharing the Original Feeder

Copyright © Huawei
Figure 1.8 Shared feeder, independent antenna port, and no RET

Copyright © Huawei
Figure 1.9 Shared feeder, independent antenna port, and RET

Copyright © Huawei
Figure 1.10 Shared feeder, independent antenna port, and TMA&RET
Note that parts highlighted with blue are new components in the preceding figures.
In this scenario of mode transition, the RF module working on the new frequency band uses
an independent antenna but shares the original feeder due to installation constraints. In such a
case, you can use an independent antenna or reuse the original multiband multi-port antenna.
In addition, customers may replace the original antenna with a multiband multi-port antenna
due to constraints on site conditions.
A combiner must be added because multiple modes (frequency bands) share the feeder. The
combiner brings about insertion loss, which slightly affects the performance of the original

Copyright © Huawei
mode (frequency band). The insertion loss of an inter-band combiner is 0.X dB. For details,
see the relevant combiner datasheet.
 Independent antenna (antenna port)
 No new feeder
 If an RET antenna is used, independent RET and electrical tilt configuration are
supported.
 If an independent antenna is used, you can independently set the mechanical tilt.
2. Precautions
In scenarios of adding an RET or TMA, check the model, and hardware and software versions
of RET or TMA for compatibility. For details, contact GTAC or TMO teams. A list of RET or
TMA models that have passed the IOT compatibility test is available. If the RET or TMA to
be added is not included in the list, relevant tests by R&D or field engineers are
recommended.
Pay attention to frequency bands supported by the TMA, especially the reused TMA.
When a combiner is used, pay attention to the design of the RET and TMA, and combiner's
capability of supporting DC power and OOK signals.
Determine connections between components in the antenna and feeder subsystem.

Board Antenna Same as the number Required when the

replaced
Jumper N/A The length of the
feeder needs to be
determined
survey.
the following
conditions are met:
for the new
mode.
 No TMA is
configured.
 The RRU and
antenna are not
directly

Copyright © Huawei
connected to
each other.
network plan.
internal RET is
available.
AISG cable from the Same as the number Required for
SBT or TMA to the of sectors connecting to the
RET SBT or TMA when
lengths of the AISG
cable vary with
scenarios.
Combiner Four times the The combiner model
number of sectors is determined by
frequency bands
where signals are to
be combined.
None
The GSM and UMTS systems have no requirements for deploying this feature.
The feature license must be purchased when RET is used for LTE. The following table
provides the related license control items.
Table 10.2 License control items for optional features of RET management
Feature Name License Control Item License Abbreviation
(LTE-FDD) LOFD-001024 Remote Electrical Tilt LLT1RET01

(LTE-TDD) TDLOFD-001024 Remote Electrical Tilt LLT1RET01

Data configuration for a multimode antenna is the same as that for a set of single-mode
antenna.
Key points for the data configuration are listed as follows:

Copyright © Huawei
- Based on connections of the RFU/RRU, antenna, and feeder, configure RF transmit and
receive mode for the GBTS, and TxBranch/RxBranch/RFCONNGRP information about
the RF module for the eGBTS, NodeB, eNodeB, and co-MPT base station.
- If RET is required, configure the ALD power supply switch for the RRU or RFU and
related alarm threshold parameters. In addition, configure RET for the RET antenna,
download the RET configuration file, calibrate the RET antenna, and set tilt angels.
- If a TMA is required, configure the TMA and TMA attenuation corresponding to the
RRU or RFU's channel.
For SRAN12.0, see section "Data Preparation" in "Engineering Guidelines (ALD
Manual Deployment on Multimode Base Station)" of ALD Management Feature
Examples:
The following table describes the key parameters that must be set when RET is
controlled by the RRU or RFU through its RETPORT.
Table 10.3 Key parameters related to the RETPORT

ation Name r ID
Object
Antenna Adding an RETPORT Cabinet No. CN 0

and RXU
feeder
Adding an RETPORT Subrack No. SRN 62
RXU
Adding an RETPORT Slot No. SN 0
RXU
Adding an RETPORT Port No. PN RET_PORT
RXU
Adding an RETPORT ALD Power PWRSWI ON
RXU Switch TCH
Adding an RETPORT Current Alarm THRESH UER_SELF_DEF
RXU Threshold OLDTYP INE
E
Adding an RETPORT Undercurrent UOTHD 40
RXU Alarm Occur
Threshold
Adding an RETPORT Undercurrent UCTHD 60
RXU Alarm Clear
Threshold
Adding an RETPORT Overcurrent OOTHD 850
RXU Alarm Occur
Threshold
Adding an RETPORT Overcurrent OCTHD 750
RXU Alarm Clear
Threshold

Copyright © Huawei
The following table describes the key parameters that must be set when RET is
controlled by the RRU or RFU through its ANTENNAPORT.
Table 10.4 Key parameters related to the ANTENNAPORT

Domain Configuratio MOC Paramete Paramete Example
n Object r Name r ID Value
Antenna and Adding an ANTENNAPO Cabinet CN 0

feeder RXU RT No.
Adding an ANTENNAPO Subrack SRN 62
RXU RT No.
Adding an ANTENNAPO Slot No. SN 0
RXU RT
Adding an ANTENNAPO Port No. PN R0A
RXU RT
Adding an ANTENNAPO ALD PWRSWI ON
RXU RT Power TCH
Switch
Adding an ANTENNAPO Current THRESH UER_SEL
RXU RT Alarm OLDTYP F_DEFINE
Threshold E
Adding an ANTENNAPO Undercurr UOTHD 40
RXU RT ent Alarm
Occur
Threshold
Adding an ANTENNAPO Undercurr UCTHD 60
RXU RT ent Alarm
Clear
Threshold
Adding an ANTENNAPO Overcurre OOTHD 850
RXU RT nt Alarm
Occur
Threshold
Adding an ANTENNAPO Overcurre OCTHD 750
RXU RT nt Alarm
Clear
Threshold

Copyright © Huawei
Table 10.5 Key parameters related to the RET antenna

mai ration C Value
n Object
Ant Adding RET Device No. DEVICENO 1

enn RET
a
and Adding RET Control Port Cabinet CTRLCN 0
feed RET No.
er
Adding RET Control Port Subrack CTRLSRN 62
RET No.
Adding RET Control Port Slot No. CTRLSN 0
RET
Adding RET Antenna Type RETTYPE Single antenna
RET
Adding RET RET Subunit Number SUBUNITNUM 1
RET
Adding RET Polar Type POLARTYPE Equipment
RET plan
Adding RET Antenna Scenario SCENARIO REGULAR
RET
Table 10.6 Key parameters related to the RET subunit

Antenna and Adding RET RETSUBU Device No. DEVICEN 1

feeder NIT O
Adding RET RETSUBU Subunit No. SUBUNITN 1
NIT O
NIT 1 Cabinet
No.
NIT 1 Subrack 1
No.
Adding RET RETSUBU Connect Port CONNSN1 0
NIT 1 Slot No.
Adding RET RETSUBU Connect Port CONNPN1 R0A
NIT 1 Port No.
NIT 2 Cabinet

Copyright © Huawei

No.
NIT 2 Subrack 2
No.
Adding RET RETSUBU Tilt TILT 20
NIT
Table 10.7 Key parameters related to the TMA

mai ration C Value
n Object
Ant Adding a TMA Device No. DEVICENO 2

enn TMA
a
and Adding a TMA Control Port Cabinet CTRLCN 0
feed TMA No.
er
Adding a TMA Control Port Subrack CTRLSRN 62
TMA No.
Adding a TMA Control Port Slot No. CTRLSN 0
TMA
Adding a TMA TMA Subunit Number SUBUNITNUM 1
TMA
Table 10.8 Key parameters related to the TMA subunit

mai ation Value
n Object
Ante Adding a TMA Device No. DEVICENO 2

nna TMA
and
feed Adding a TMA Subunit No. SUBUNITNO 1
er TMA
Adding a TMA Connect Port CONNCN 0
TMA Cabinet No.
Adding a TMA Connect Port CONNSRN 62
TMA Subrack No.
Adding a TMA Connect Port Slot CONNSN 0
TMA No.

Copyright © Huawei

mai ation Value
n Object
Adding a TMA Connect Port No. CONNPN R0A

TMA
Adding a TMA Working Mode MODE NORMA
TMA L
Adding a TMA Gain GAIN 48
TMA
If both RX channels of the RXU are configured with the TMA, attenuation must be
configured for the RXBRANCH of both RX channels. The following table describes the
parameters that must be set to configure RX channel attenuation.
Table 10.9 Key parameters related to RX channel attenuation

mai ation Value
n Object

nna RXU RX
and channel 0
feed
RXU RX RX Channel
channel 0
RXU RX
channel 0
nna RXU RX
and channel 1
feed
RXU RX RX Channel
channel 1
RXU RX
channel 1
 Service impact


Copyright © Huawei
Installing a combiner Services on the deployed frequency band are affected.
During the combiner installation, services are
interrupted.
3.3.4 Broadband Antenna (Antenna Port) Being Shared By the

Original Mode and New Mode

Copyright © Huawei
Figure 1.11 Broadband antenna
Note that parts highlighted with blue are new components in the preceding figures.
In this scenario of mode transition, a new frequency band of new mode shares the broadband
antenna with one or more frequency bands of the original mode. In such a case, an external
combiner combines signals transmitted on multiple frequency bands.
 Broadband antenna, multimode and multiband shared antenna port
 No new feeder
 All modes share the same antenna or antenna port and independent RET is not
supported.
2. Precautions
1) The combiner model is determined by frequency bands where signals are to be combined.
2) If the RF module is a broadband module providing the same output port for multiple bands
(for example, RRU3961), no external combiner is required.

Copyright © Huawei

Board Antenna Same as the number Required when the

of sectors in the new original antenna is
mode replaced.
Jumper - The length of the
feeder needs to be
determined
survey.
frequency bands
be combined.
None
None. The antenna and feeder license of the original mode is used.
None. The antenna and feeder configuration of the original mode is used.
 Service impact

Installing a combiner Services on the deployed frequency band are affected.
During the combiner installation, services are
interrupted.

Copyright © Huawei
3.3.5 SDR RF Module of the New Mode Using the Original

Feeder
Figure 1.12 SDR RF module using the original feeder
In this scenario of mode transition, an original antenna or feeder is available for refarming and
no modification is required.
2. Precautions
None
None. The original antenna and feeder are used.
None
Copyright © Huawei
None. The antenna and feeder license of the original mode is used.
None. The antenna and feeder configuration of the original mode is used.
 Service impact
None
3.4 Co-MPT or Separate-MPT Planning

This section describes co-MPT or separate-MPT planning.
3.4.1 Overall Co-MPT or Separate-MPT Planning Process

Figure 1.13 Overall co-MPT or separate-MPT planning process
The following table provides the comparison between separate-MPT and co-MPT
configurations.
Table 13.1 Comparison between separate-MPT and co-MPT configurations

Comparison Item Co-MPT Separate-MPT
Hardware Only one main control board One main control board
(UMPT or UMDU) is (GTMU/WMPT/LMPT/UM
required. PT) shall be configured for
each mode. One more BBU
is required for a GUL
multimode base station.
Inter-RAT decoupling Tight coupling: NMS, Loose coupling: dual-star
transmission, clock, and SDR and independent NMS,
CPRI MUX are tightly transmission, and clock
coupled. Tight coupling: co-
transmission, common
reference clock, and the

Copyright © Huawei
Comparison Item Co-MPT Separate-MPT
CPRI MUX feature

Shared resources Natural sharing: NMS, Sharing is implemented
transmission, clock, CPRI, through the following
and baseband resources can features: co-transmission,
be shared. common reference clock,
and CPRI MUX. Baseband
resources cannot be shared
between modes.
Low-cost smooth mode New mode is deployed in An OM channel must be
transition the same way as the feature enabled for the new mode
is enabled. and new baseband resources
must be deployed.
UBBP co-baseband Co-baseband is supported Co-baseband is not
by UBBP or UMDU boards. supported by UBBP boards.
Version upgrade All-at-once upgrade All-at-once upgrade. Mode-
by-mode upgrade must be
customized.
O&M experience Consistent GUL O&M O&M experience varies
experience reduces the according to each mode of
learning cost. GUL.
Note that the BBU3910A supports only co-MPT mode transition but not separate-MPT mode
transition. In SRAN12.0, the BBU3910A does not support NB-IoT.
Whether co-MPT or separate-MPT is used depends on whether the new main control board
works in a new mode independently. If multiple modes are added, you need to perform the
operations in the preceding process for each mode. For example, in mode transition from
GSM to G&[U*L], if UMTS is the first mode to be added, UMTS will be deployed on a new
main control board. In this case, separate-MPT is used for mode transition to UMTS but the
NodeB is a co-MPT base station. In addition, if LTE is the second mode to be added, LTE is
deployed on the UMTS main control board. In this case, co-MPT is used for mode transition.
LTE FDD, LTE TDD, and NB-IoT all belong to LTE and must be deployed only on the same
main control board and cannot be deployed on different main control boards.
 Whether co-MPT reconstruction is required

If the original base station is not a co-MPT base station, co-MPT reconstruction is
required. The following scenarios are included:
1. If the original base station is a separate-MPT base station, deploy all modes on one
main control board to implement co-MPT reconstruction.
2. If the original base station is a single-mode or separate-MPT base station, add a new
mode to an original mode to implement co-MPT reconstruction.

Copyright © Huawei
If the original base station supports one or two of LTE FDD, LTE TDD, and NB-IoT,
deploy the other one on the same main control board to implement co-MPT. In this case,
the co-MPT reconstruction is not required.
Table 13.2 Scenario analysis of separate-MPT or co-MPT mode transition

Category Separate-MPT Scenario
or Co-MPT
Co-MPT or Separate-MPT 3.4.2Adding a Main Control Board of the New Mode to

separate- the Original BBU
MPT
planning 3.4.3Adding a new BBU and a Main Control Board of
the New Mode
Co-MPT mode 3.4.4Adding a New Mode to the Co-MPT Base Station
expansion
3.4.5Co-MPT Reconstruction and Adding a New Mode
to the Co-MPT Base Station
LTE FDD and LTE TDD co-MPT is supported in SRAN8.1 and later versions. UMPTs
support LTE FDD and LTE TDD co-MPT but LMPTs do not.
3.4.2 Adding a Main Control Board of the New Mode to the

Original BBU
The BBU3900 or BBU3910 supports a maximum of two main control boards. When separate-
MPT is used, the BBU3900 and BBU3910 support mode transition from a single mode to
dual-mode, for example, transition from GSM to GU or GL, or from UMTS to UL.
This scenario is applicable to the mode transition from single-mode to dual-mode. The
following two applications are supported:
 Independent RF module working in the new mode (separate-MPT and co-cabinet)
 SDR RF module working in both the original mode and the new mode (separate-MPT
and common mode)

Copyright © Huawei
The BBU3910A does not support mode transition when separate-MPT is used and therefore
does not support this scenario.
For details about how to select main control boards, see GUL Base Station Overview and
Selection Guide.
2. Precautions
- In separate-MPT (excluding the hybrid-MPT) scenarios, a single BBU supports a maximum
of two modes, and the main control boards cannot work in active/standby mode.
- Constraints on BBU power supply and heat dissipation systems affect configurations after
mode transition. You can use the program comprehension tool (PCT) to obtain the
specifications of power supply and heat dissipation for the BBU after mode transition. If
necessary, you need to replace the BBU or the UPEU, or expand the UPEU's capacity. All
these operations interrupt services of the original mode.
- Pay attention to the impact of BBU capacity expansion on cabinet power support and heat
dissipation. For details, see section "Equipment Auxiliary Planning" in this document.
- The BBU3910 supports only new types of main control boards such as the GTMUb,
GTMUc, and UMPT.
Board UMPT(L)/LMPT 1 An LTE main

control board is
added.
NOTE
Use a newly delivered
board because such
boards work in the
maintenance mode by
default. If you do not
use a newly delivered
board, this board may
not work in the
maintenance mode,
and a false alarm may
be generated during
mode transition and
services of the newly
deployed mode may
be interrupted.
UMPT(U)/WMPT 1 A UMTS main

control board is
added.
NOTE
Use a newly delivered
board because such
boards work in the
maintenance mode by
default. If you do not
use a newly delivered
board, this board may
not work in the
maintenance mode,

Copyright © Huawei

and a false alarm may
be generated during
mode transition and
deployed mode may
be interrupted.
GTMU 1 A GSM main control

board is added.
For the mapping relationship between the main control board and version, see 3900 Series
Base Station Hardware and Software Compatibility Description for SRAN12.0.
No specific license control item is available for the main control board working in a separate-
MPT multimode base station.
Therefore, a license related to the new mode can be applied for in the same way as that for the
license of each involved mode.
UMPT multimode licenses must be applied for only when the UMPT or UMDU works in co-MPT and
multimode concurrency is applied. If the UMPT/UMDU serves only one mode, there is no need to apply
for such licenses. The UMPT multimode licenses include UMPT Multi Mode license(GSM), UMPT
Multi Mode license(UMTS), UMPT Multi Mode license(LTE FDD), UMPT Multi Mode license(LTE
TDD), and UMPT Multi Mode license(NB-IoT)(per UMPT).
There is no special data configuration for the newly added main control board working in a
separate-MPT multimode base station. Note that if a multimode feature is required, refer to
the related feature descriptions, such as descriptions about the RF module and common
reference.
For configuration of common resources in a multimode base station, pay attention to the
following items:
- Configure equipment data (such as the power supply, fan, and environment monitoring
board) only for one mode. It is recommended that the equipment data be configured on the
original mode so that no data migration is involved.
In separate-MPT, you are not advised to configure data of mechanical and electrical parts for multiple
modes together because data consistency issues may occur.
- The number of all common resources at the entire site shall be unique. For example, two
non-SDR RF modules working in two different modes cannot have the same cabinet No.,
subrack No., or slot No. The same cabinet No., subrack No., or slot No. must be configured
for SDR RF modules working in two different modes.
For details about data configurations, see the following:
Configuration mode: MML/GUI/SUMMARY
For SRAN12.0, see section "Creating Base Stations" in "Creating Separate-MPT Multimode
Base Stations" of 3900 Series Base Station Initial Configuration Guide.

Copyright © Huawei
Resources required for each mode are managed by a "brain." Environment alarms and fans are
managed by the mode specified manually. That is, you can configure parameters related to the
environment, alarm, and fan only for one mode.
 Service impact
Whether SDR Is Used or Scenario Impact on Services of the
Not Original Mode
No SDR Installing a new main None

control board
Upgrading software of a None
new main control board
Activating data None
configuration of a new main
control board
Replacing a BBU/UPEU Services of the entire site are
interrupted during the
replacement. During the
replacement of the BBU, if
the original mode is LTE,
the related license needs to
be updated.
SDR Installing a new main During the installation of the
control board main control board, if the
SDR is used, services of the
deployed mode may be
affected for a short period of
time due to timing loop.
Upgrading software of a If the SDR RF module needs
new main control board to be upgraded, services of
the original mode carried by
the SDR RF module will be
interrupted for about one
minute.
Activating data When a cell of the new
configuration of a new main mode is established on the
control board SDR RF module, services of
the original mode will be
time.
Replacing a BBU/UPEU Services of the entire site are
interrupted during the
replacement. During the
replacement of the BBU, if
the original mode is LTE,
the related license needs to
be updated.

Copyright © Huawei
3.4.3 Adding a new BBU and a Main Control Board of the New
Mode
A maximum of two main control boards can be configured in a BBU3900 or BBU3910.

Therefore, adding a BBU and a mode applies to mode transmission from dual modes to triple
modes. The related typical scenarios are mode transmission from G&U to G&U+L or G&L to
G&L+U.
For details about how to select BBUs and main control boards, see GUL Base Station
Overview and Selection Guide.
2. Precautions
- BBUs must be interconnected for mode transition where a new BBU is added and the two
BBUs work in multiple modes. For details, see section "3.5BBU Interconnection".
- The GTMU must be deployed in the primary BBU subrack.
- A BBU3900/BBU3910 cannot be interconnected with a BBU3910A. Therefore, mode
addition cannot be performed between BBU3900/BBU3910 and BBU3910A.
Board BBU 1
UMPT 1

Copyright © Huawei
No specific license control item is available for the main control board working in a separate-
MPT multimode base station.
multimode concurrency is applied. If the UMPT/UMDU serves only one mode, there is no need to apply
for such licenses. The UMPT multimode licenses include UMPT Multi Mode license(GSM), UMPT
Multi Mode license(UMTS), UMPT Multi Mode license(LTE FDD), UMPT Multi Mode license(LTE
TDD), and UMPT Multi Mode license (NB-IoT) (per UMPT).
There is no special data configuration for the newly added main control board working in a
separate-MPT multimode base station. Note that if a multimode feature is required, refer to
the related feature descriptions, such as descriptions about the RF module and common
reference.
For configuration of common resources in a multimode base station, pay attention to the
following items:
- Configure equipment data (such as the power supply, fan, and environment monitoring
board) only for one mode. It is recommended that the equipment data be configured on the
original mode so that no data migration is involved. When two BBUs are used, all the
equipment is connected to the primary BBU subrack and such equipment data is configured in
one mode of the primary BBU subrack.
- The number of all common resources at the entire site shall be unique. For example, two
non-SDR RF modules working in two different modes cannot have the same cabinet No.,
subrack No., or slot No. The same cabinet No., subrack No., or slot No. must be configured
for SDR RF modules working in two different modes.
- BBU interconnection data must be configured when two BBUs are used. For details, see
section "3.5BBU Interconnection" in this document.
For SRAN12.0, see section "Creating Base Stations" in "Creating Separate-MPT Multimode
Base Stations" of 3900 Series Base Station Initial Configuration Guide.
Resources required for each mode are managed by a "brain." Environment alarms and fans are
managed by the mode specified manually. That is, you can configure parameters related to the
environment, alarm, and fan only for one mode.
 Service impact
Not Original Mode
No SDR Installing a new main None

control board
Installing a BBU working in None
a new mode

Copyright © Huawei

Not Original Mode
Upgrading software of a None

new main control board
Activating data None
configuration of a new main
control board
Inter-BBU SDR Installing a main control None
board in the secondary BBU
subrack
Installing a BBU working in None
a new mode
Upgrading software of a If the SDR RF module needs
new main control board to be upgraded, services of
the original mode carried by
the SDR RF module will be
interrupted for about one
minute.
Activating data When a cell of the new mode
configuration of a new main is established on the SDR
control board RF module, services of the
original mode will be
time (No CS call drop but a
decrease in the PS service
rate within 3 seconds).
3.4.4 Adding a New Mode to the Co-MPT Base Station

If the original base station is a co-MPT multimode base station, add a new mode directly, for
example, a multimode co-MPT BTS3900 base station.
All types of BBUs support this scenario.
Main control board selection: None
2. Precautions
- A new mode can be added to the original base station if it is a co-MPT multimode base
station (such as BTS3900) and Deployment Mode of the MPT configuration is set to
CONCURRENT(Concurrent). If the Deployment Mode of the MPT configuration is set to
NON-CONCURRENT(Non-concurrent), a new mode cannot be added. In this case, you
need to set Deployment Mode to CONCURRENT(Concurrent) before adding a mode. This
modification resets the base station.
- A new mode to be added must be of the same version as the existing mode in most cases.
That is, the source mode of an original main control board must be upgraded to the target
version in advance.

Copyright © Huawei
N/A
Only versions later than SRAN8.0 support this scenario.
- UMPT multimode license
The following table provides UMPT multimode licenses that need to be purchased.
License Control License License Sales Mode

Item Name BBOM Abbreviation Unit
UMPT Multi Mode 82204202 LGB3UMML01 per GSM

License (GSM) (per UMPT
UMPT)
UMPT Multi Mode 82203981 LQW9GUDM0 per UMTS
License (UMTS) (per 1 UMPT
UMPT)
UMPT Multi Mode 82204259 LLT1UMML01 per LTE
License (per UMPT) UMPT
(FDD)
UMPT Multi Mode 82204285 LLT1TUMML0 per LTE
License (per UMPT) 1 UMPT
(TDD)
UMPT Multi Mode 82207098 LML1UMML0 per LTE
License (per UMPT) 1 UMPT
(NB-IoT)
multimode concurrency is applied. The UMPT multimode licenses include UMPT Multi Mode
license(GSM), UMPT Multi Mode license(UMTS), UMPT Multi Mode license(LTE FDD), UMPT
Multi Mode license(LTE TDD), and UMPT Multi Mode license (per UMPT) (NB-IoT). No license is
required for the first mode of a co-MPT base station. However, such licenses are required for other
modes of the base station.
- License related to the new mode

A new license of the new mode must be purchased.
Original mode:
No data modification is involved for the original mode in terms of MPT configuration.
New mode:

Copyright © Huawei
The configuration data of the new mode must be complete, including RAT data, RF data,
transmission data, and sector data.
For mode transition from FDD only or TDD only to FDD and TDD concurrency, MOs such
as Application, Function, and X2/S1 do not need to be configured (unless required by
customers), and the operations are similar to adding an inter-frequency cell in the same mode.
For example, if the original base station has only TDD cells working on the 2.3 GHz
frequency band, add TDD cells working on the 2.6 GHz frequency band. For details, see the
related description in 3900 Series Base Station Initial Configuration Guide > Cell Data
Reconfigurations.
Similarly, for mode transition from FDD only, TDD only, or FDD and TDD concurrency to
FDD and NB-IoT, TDD and NB-IoT, or FDD, TDD, and NB-IoT, MOs such as Application
and Function do not need to be configured. The operations are similar to adding NB-IoT cells
in the same mode.
SRAN12.0: Cell Reconfigurations
The following table provides the related MO and parameter.
MO Parame Parameter CME Setting Notes

ter ID Parameter
Name Name
NODE Working WM Working Set this parameter to

Mode Mode CONCURRENT(Concurrent).
 Service impact
Adding a new mode for mode Services of the original mode are not affected.
expansion with co-MPT
configuration
3.4.5 Co-MPT Reconstruction and Adding a New Mode to the Co-

MPT Base Station
If the original base station is a separate-MPT or single-mode base station, firstly perform the
co-MPT reconstruction, and add the new mode.
For scenarios where co-MPT reconstruction is supported, see 13.7Co-MPT Reconstruction
Scenarios.
Main control board selection
Only the UMPT series boards support the co-MPT mode. If the main control board does not
support co-MPT, replace the main control board. For example, the UMPTa6 does not support
co-MPT. For the specifications of UMPT boards, see BBU Hardware Description >
BBU3900 and BBU3910 Hardware Description > BBU3900 and BBU3910 Boards >
UMPT in 3900 Series Base Station Product Documentation. You can obtain the document by
visiting the following website:

Copyright © Huawei
SRAN12.0: UMPT
2. Precautions
- If the original base station is a GBTS, reconstruct the GBTS into an eGBTS by abandoning
the GTMU or using GTMU evolution.
 If the GTMU is to be abandoned, CPRI ports on the UBBP or a newly added UBRI can
be used for the GSM mode. The main control and transmission function can be
implemented on the UMPT board (the UMPT does not support TDM transmission).
 In GTMU evolution scenarios, CPRI ports remain on the GTMU. If the transmission
mode is IP over E1, the transmission ports remain on the GTMU. If the transmission
mode is IP over GE/FE, the transmission ports must be provided by the UMPT.
If the GBTS uses TDM transmission before the reconstruction, first change TDM
transmission into IP transmission and then perform a GBTS-to-eGBTS reconstruction.
- The mode to be added after the co-MPT reconstruction must be of the same version as the
existing mode.
Board UMPT 1 Prepare UMPT boards if the

base station does not use
UMPT boards before co-
MPT reconstruction.
UBRI 1 Prepare UBRI boards if
GSM co-MPT
reconstruction is required
and the UBRI board
provides CPRI fiber optical
cables for the GSM mode.
Only versions later than SRAN8.0 support this scenario.
If the GBTS is to be reconstructed into a co-MPT base station, prepare the GTMU evolution
software if you use the evolved GTMU. To obtain the GTMU evolution software (whose
version is V900), visit http://support.huawei.com/carrier/ and choose Support > Product
Support > Wireless Network > Wireless Network Common > SingleRAN >
SingleRAN_MBTS.
The following table provides UMPT multimode licenses that need to be purchased.

UMPT Multi Mode 82204202 LGB3UMML01 per BTS GSM

License (GSM) (per
UMPT)

Copyright © Huawei

UMPT Multi Mode 82203981 LQW9GUDM0 per UMTS

License (UMTS) 1 NodeB
(per UMPT)
UMPT Multi Mode 82204259 LLT1UMML01 per LTE
License (per UMPT) eNodeB
(FDD)
UMPT Multi Mode 82204285 LLT1TUMML0 per LTE
License (per UMPT) 1 eNodeB
(TDD)
multimode concurrency is applied. The UMPT multimode licenses include UMPT Multi Mode
license(GSM), UMPT Multi Mode license(UMTS), UMPT Multi Mode license(LTE FDD), UMPT
Multi Mode license(LTE TDD), and UMPT Multi Mode license (per UMPT) (NB-IoT). No license is
required for the first mode of a co-MPT base station. However, such licenses are required for other
modes of the base station.
2. License related to the new mode

A new license of the new mode must be purchased.
3. GSM License
If a GBTS to be reconstructed into an eGBTS through co-MPT reconstruction, the license of
the GBTS must be divided. For details, see 13.2Preparing GSM Licenses.
In GBSS15.0, the license control item changed significantly. The most significant change is
that the BTS quotation feature is controlled by the eGBTS. Before a feature is activated/used,
the GTS needs to allocate sufficient licenses to each eGBTS on the U2000. Otherwise, the
feature fails to be activated and CS/PS services may be affected. The following table
describes how to allocate the licenses of features supported by the eGBTS.
1. Features contained in the eGBTS license but not supported by the eGBTS
Feature ID License Sales Unit Supported Supported eGBTS
Control by the by the License
Item GBTS or eGBTS or Allocation
Not Not Instruction
N/A High Power Per TRX Yes No Set the

(per TRX) number of
licenses to
be allocated
to 0.
N/A TRU which Per TRX Yes No Set the
works as number of
Multi licenses to
transceivers be allocated
Resource of to 0.
3rd

Copyright © Huawei

Not Not Instruction
generation
BTS (per
TRX)
N/A BBU Carrier Per TRX Yes No Set the
Capacity number of
License (per licenses to
TRX) be allocated
to 0.
GBFD- PBT(Power Per TRX Yes No Set the
115901 Boost number of
Technology) licenses to
(per TRX) be allocated
to 0.
GBFD- Transmit Per TRX Yes No Set the
115902 Diversity number of
(per TRX) licenses to
be allocated
to 0.
N/A BTS3900B Per TRX Yes No Set the
Transceiver number of
Resource licenses to
to 0.
2. Features supported by GBSSR15.0

Featur License Sales Unit Support Supported eGBTS License
e ID Control ed by by the Allocation Instruction
Item the eGBTS or
GBTS or Not
Not
N/A Multi Per TRX Yes Yes The number of licenses to

Carrier be allocated equals the
60W total number of carriers
High displayed in the eGBTS
Power Power Type(w)
License parameter with the value
(per ranging from 60 W to 80
TRX) W.
Related BSC MML
command: LST
GTRXDEV
N/A Multi Per TRX Yes Yes The number of licenses to

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not

Power Power Type(w)
(per greater than or equal to 80
TRX) W.
Related BSC MML
command: LST
GTRXDEV
N/A TRU Per TRX Yes Yes Non-multi-site cell
which scenarios:
works as Number of licenses to be
Multi allocated = Number of
transceive activated logical TRXs
rs under an eGBTS –
Resource Number of TRX modules
of 3900 that support GSM
(per
TRX) Multi-site cell scenarios
(supported by
GBSSR16.0 and later):
(1) Number of licenses to
be allocated for sites
outside China and China
Unicom = Number of
subsites under eGBTS x
Number of logical TRXs
under a subsite – Number
of TRX modules under all
subsites
be allocated for China
Mobile = Number of
activated logical TRXs
under an eGBTS –
Number of TRX modules
of the subsite with the
maximum number of
TRX modules
Related BSC MML
commands:
LST GTRX
LST BTSLOCGRPE
Related BTS MML
commands:
LST

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not
GTRXGROUPSECTORE
QM
LST SECTOREQM
MRFD Multi- Per Site Yes Yes If the Power Sharing
- mode Type parameter (eGBTS)
211801 Dynamic is set to
Power GUPWRSHR(GU power
Sharing( sharing), a license needs
GSM) to be allocated.
(per Site) Related eGBTS MML
commands:
LST
GBTSPWRSHRGRP;
MRFD 2.0MHz Per Site Yes Yes The feature is controlled
- Central by a false control item.
211703 Frequenc Contact the frontline
y point marketing personnel when
separatio manually allocating a
n license to a customer's
between base station.
GSM and
UMTS
mode(GS
M) (per
Site)
MRFD GSM per BTS Yes Yes If the Frequency-based
- Power Power Control parameter
211804 Control of one or more local cells
on under eGBTS is set to
Interferen ON(On), a license needs
ce to be allocated to the
Frequenc eGBTS.
y for GU Related eGBTS MML
Small command:
Frequenc
y gap LST
(GSM) GLOCELLALGPARA
MRFD Bandwidt Per Site Yes Yes The feature is controlled

- h sharing by a false control item.
211505 of MBTS Contact the frontline
Multi- marketing personnel when
mode Co- manually allocating a
Transmis license to a customer's
sion(GBT base station.
S)

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not
MRFD Multi- per BTS Yes Yes The feature is controlled

- mode BS by a false control item.
211602 Common Contact the frontline
IPSec(GS marketing personnel when
M) (per manually allocating a
Site) license to a customer's
base station.
MRFD GSM and per BTS Yes Yes If the Spectrum Sharing
- UMTS Allowed parameter is set
211802 Dynamic to YES(Yes), a license
Spectrum needs to be allocated to
Sharing the eGBTS.
(GSM) Related BSC MML
command:
LST GDSSPARA
MRFD Dynamic per BTS Yes Yes If the FH Index Used
- MA for After Frequency
211803 GU Spectrum Sharing
Dynamic parameter of one or more
Spectrum channels under the
Sharing eGBTS is set to a value
(GSM) ranging from 0 to 63, a
license needs to be
allocated to the eGBTS.
Related BSC MML
command:
LST GTRXCHANHOP;
MRFD GSM and Per BTS Yes Yes If the Power Sharing
- LTE Type parameter (eGBTS)
Power GLPWRSHR(GL power
command:
LST
GBTSPWRSHRGRP;
MRFD Multi- Per BTS Yes Yes If the Inter-RAT Cell
- RAT Dynamic Shutdown
211901 Carrier parameter of one or more
Joint logical cells under the
Shutdown eGBTS is set to ON(On),
(GBTS) a license needs to be
(per Site) allocated to the eGBTS.

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not
Related BSC MML

command:
LST GCELLSOFT
GBFD IPSec Per BTS No Yes If the IPSec Bypass
- bypass Switch of the eGBTS is
116602 (per base turned on, a license needs
station) to be allocated to the
eGBTS.
Related eGBTS MML
command:
LST IPSECBYPASSCFG
N/A UMPT Per UMPT No Yes 1. No license is allocated
Multi to a new eGBTS that
Mode works in GSM only mode.
License 2. No license needs to be
(GSM) purchased and allocated to
(per a GU/GL/GUL co-MPT
UMPT) base station.
3. For a new co-MPT base
station that does not
support GSM, a license
needs to be purchased and
allocated to the base
station if mode transition
is performed, such as
mode transition from UL
to GUL.
N/A Antenna Per TRX Yes Yes License verification is
Intermod triggered by the related
ulation eGBTS maintenance
Performa commands. The number
nce of licenses that need to be
Detection allocated equals the
(per number of activated
TRX) logical TRXs under the
base station.
Related eGBTS MML
commands:
STR RFTEST;
STR GBTSRFTST
N/A Extended Per TRX Yes Yes License verification is
Spectrum triggered by the related
Scan (per GUI maintenance

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not
TRX) function. The number of

licenses that need to be
allocated equals the
number of activated
logical TRXs under the
base station.
Related LMT GUI
maintenance function of
the eGBTS:
Offline Frequency
Spectrum Scanning
3. New features supported by GBSSR15.1

Item the eGBTS or
GBTS Not
or Not
GBFD BTS IP Per BTS No Yes If the eGBTS uses the
- Active TWAMP client or
15120 Performa TWAMP responder
2 nce function, a license needs
Measure to be allocated.
ment Related eGBTS MML
(per Site) commands: LST
TWAMPCLIENT and
LST
TWAMPRESPONDER

Featur License Sales Unit Supporte Supported eGBTS License
e ID Control d by the by the Allocation Instruction
Item GBTS or eGBTS or
Not Not
N/A SubSite Per Module Yes Yes Licenses need to be
Solution allocated only to China
License Mobile.
(per Number of licenses to be
Module) allocated = Number of
RXU modules for multi-
site cells under the eGBTS

Copyright © Huawei
- Number of RXU
modules of the subsite
with the maximum
number of RXU modules.
Related BSC MML
command:
LST BTSLOCGRPE
Related BTS MML
commands:
LST SECTOR
LST RRU
N/A RFU co- Per Module Yes Yes Licenses need to be
cell allocated only to China
Solution Mobile.
License The number of licenses to
(per be allocated equals the
Module) number of RFUs for
multi-site cells under the
eGBTS.
Related BSC MML
command:
LST BTSLOCGRPE
Related BTS MML
commands:
LST SECTOR
LST RRU
GBFD 4-Way Per TRX Yes Yes The number of licenses to
- Receiver be allocated equals the
11590 Diversity number of activated
3 (per logical TRXs which are
TRX) set to the four-way receive
diversity mode under the
eGBTS.
Related BSC MML
command:
LST GTRX
Related BTS MML
command:
LST GTRXGROUP
N/A UBBP Per Module Yes Yes A license needs to be
Multi- allocated to each UBBP
Mode board that supports GSM.
license You can query details
(GSM) about the board through
(Per the eGBTS MML
Module) command: LST BBP.
GBFD IPsec Per BTS No Yes If the eGBTS is enabled

Copyright © Huawei
- redundan with the IPsec redundancy

16020 cy function, a license needs
9 among to be allocated to the
multi- eGBTS.
SeGWs Related eGBTS MML
(per command:
BTS)
LST IKEPEER
GBFD BTS Per BTS No Yes If the eGBTS is enabled
- supportin with the PKI redundancy
16021 g PKI function, a license needs
0 redundan to be allocated to the
cy (per eGBTS.
BTS) Related eGBTS MML
commands:
LST CA
LST CRLTSK
MRFD AAS Per RU No Yes The feature is controlled
- RAT by a false control item.
26110 Specific Contact the frontline
3 Tilting marketing personnel when
(GSM) manually allocating
(Per RU) licenses, of which the
number equals that of the
AAS, to a customer's base
station.
Related MML commands:
LST
GTRXGROUPSECTORE
QM
LST AARU
Not AAS Per RU No Yes The number of licenses to
comm Virtual be allocated equals the
erciall Four number of AARUs whose
y Uplink four virtual ports are used
deploy Channels by the TRX group as the
ed for GSM receive channel.
(per RU) Related MML commands:
LST GTRXGROUP
LST
GTRXGROUPSECTORE
QM
LST AARU

Featu License Sales Unit Supporte Supporte eGBTS License
re ID Control d by the d by the Allocation Instruction

Copyright © Huawei

Not Not
GBFD GTMUb Per BTS No Yes If the main control board
- SingleO of the eGBTS is GTMUb,
17020 M (per a license needs to be
5 BTS) allocated.
Related eGBTS MML
command:
DSP BRDMFRINFO

Not Not
GBFD BTS Per BTS No Yes If the eGBTS is configured
- Supportin with multiple CAs or
17120 g Multi- IkePeer uses multiple
5 operator certificates, a license needs
PKI (per to be allocated.
commands:
LST CA
LST IKEPEER
- Supportin with the IPsec redirection
17120 g IPsec function, a license needs to
6 Redirecti be allocated to the eGBTS.
on (Per Related eGBTS MML
BTS) command:
LST IKEPEER
N/A Multi- Per Band per Yes Yes Calculate the total number
Mode RRU of frequency bands used
Multi- by all multi-band RRUs
Band for GSM cells.
License Related BSC MML
for Multi- command:
Band RF
Module LST GTRX
(Per Band Related BTS MML
per RRU) commands:
LST
GTRXGROUPSECTORE
QM
LST SECTOREQM

Copyright © Huawei

Not Not
GBF BTS Per BTS No Yes If the IKE check switch for
D- Supportin the digital certificate
18120 g Digital whitelist is turned on for
2 Certificat the eGBTS, a license
e needs to be allocated.
Whitelist Related eGBTS MML
Managem command:
ent (Per
BTS) LST CERTCFG

Perform co-MPT reconstruction for the original mode and expand the capacity for the new
mode after the co-MPT reconstruction is finished.
The configuration data must be modified when the co-MPT reconstruction is performed.
New mode:
The configuration data of the new mode must be complete, including RAT data, RF data,
transmission data, and sector data.
For mode transition from FDD only or TDD only to FDD and TDD concurrency, MOs such
as Application, Function, and X2/S1 do not need to be configured (unless required by
customers), and the operations are similar to adding an inter-frequency cell in the same mode.
For example, if the original base station has only TDD cells working on the 2.3 GHz
frequency band, add TDD cells working on the 2.6 GHz frequency band. For details, see "Cell
Reconfiguration" in SRAN12.0 Reconfiguration Guide.
The following table provides the related MO and parameter.

ter ID Parameter
Name Name
NODE Working WM Working Set this parameter to

Mode Mode CONCURRENT(Concurrent).
1. Filling in the data planning tables for co-MPT reconstruction

Copyright © Huawei
 For the BSC redundancy scenario, two data planning tables need to be filled out. One is
for the primary BSC and the other for the secondary BSC.
 The BBU3910A only supports the co-MPT reconstruction in UMTS only or LTE only
scenario. Therefore, you only need to fill in the ConvertFlag, NodeBName, or
eNodeBName field in the SitePlanning page.
(1) Filling in the GlobalPlanning page
Enter information for all co-MPT scenarios on this page.

 Fill in the following fields when GSM mode is involved:
− BscSctpIdBase must be configured, making different base stations controlled by
one base station controller use different values.
− BtsSctpPortBase and BtsTrxPerSctp use the planned values. In the BSC node
redundancy scenario, BtsSctpPortBase and BtsTrxPerSctp must be set to the same
value in the data planning tables of the primary BSC and secondary BSC.
− BtsOMCHPeerIP: Enter the IP address of the U2000. This field is mandatory for
GO reconstruction and batch reconstruction scenarios.
− BtsOMCHPeerIPMask: Enter the IP mask of the U2000. This field is mandatory
for GO reconstruction and batch reconstruction scenarios.
− WORKMODE: Enter T1, E1_BA, or E1_UNBA according to the actual
transmission mode used by the GBTS. T1 means T1 transmission; E1_BA means
120 ohm impedance; E1_UNBA means 75 ohm impedance.
− ActBTSSoftwareVersion: If the GTMU is evolved into a board providing only
CPRI ports, enter the version of the GTMU evolution software. The GTMU
abandoning scenario is not involved.
− BSCNodeRedundancyBSCName: For the BSC redundancy scenario, fill in this
field in two data planning tables. In the table for the primary BSC, enter the primary
BSC's name. In the table for the secondary BSC, enter the secondary BSC's name.
In non-BSC-redundancy scenario, leave this field blank.
− ActGTMUSoftwareVersion: This field is used in the GTMU SingleOM
reconstruction scenario. Enter the version of the GTMU SingleOM reconstruction
package. The version of the GTMUb SingleOM reconstruction software is a special
V900 version, for example, BTS3900V900R011C00.
− GLOCELLIDRule: This field specifies the allocation policy of global cell IDs
when the BSC Node Redundancy feature is not used. This field can be set to CGI-
Rule (indicating that global cell IDs are allocated in ascending order) or
CELLINDEX-Rule (indicating that cell indexes are allocated in ascending order).
The default value is CGI-Rule. When the BSC Node Redundancy feature is used,
this field must be set to the default value.
 Fill in the following field when an MBTS is involved:
SRANBaselineRAT: Leave this field unspecified for a single mode base station. This
field is optional for an MBTS. If this field is left unspecified for an MBTS, data is
configured based on the more recent mode. Fill this field with SingleRAN in hybrid-
MPT reconstruction scenarios. For example, enter U for the GU co-MPT reconstruction
scenario, L for the GL co-MPT reconstruction scenario, and U or L for the UL co-MPT
reconstruction scenario. For the GU+L/GL+U BBU interconnection co-MPT
reconstruction scenario, enter the non-GSM RAT in the primary BBU. For the con-MPT

Copyright © Huawei
reconstruction scenarios where two BBUs are combined into one, enter the mode that the
OMCH channel is used for transmission after the co-MPT construction.
 The UMTS only or LTE only reconstruction scenario is not involved in this page.
(2) Filling in the SitePlanning page
If multiple base stations are reconstructed, the planning data of each base station must be
filled. Each row corresponds to a base station. Do not leave any blank row between two filled
rows. Otherwise, the data cannot be converted.
To reduce the GSM service interruption duration, load the GTMUb conversion software
before the GU/GL/GU+L/GL+U co-MPT reconstruction. In this scenario, you are advised to
perform reconstruction for ten sites at a time. The BSC script is executed in serial. If too many
sites are reconstructed in a batch, execution of the script may not be finished within the
required duration (8 to 12 minutes) of service interruption.
If GSM base stations are cascaded using IPoE1, it is recommended that the cascaded BTSs be
reconstructed in a batch. In the GO co-MPT reconstruction scenario, you are advised to
reconstruct all the cascaded base stations at the same time, which will reduce service
interruption duration. For the co-MPT reconstruction for GU, GL, and GUL base stations,
when activating the GTMU conversion software, you are advised to activate the base stations
from the lowest cascading level to the first level. When starting a PnP task, execute the
Download BSC Configuration Data command only on the base stations of the first
cascading level.
 ScenarioId: It is a reserved parameter and used for future expansion. It does not need to
be specified.
 ConvertFlag: "Yes" indicates that the configuration data for the site corresponding to
this row needs to be converted.
 BtsName, NodeBName, eNodeBName, or SRANNameBfConvert: name of the base
station to be reconstructed, mandatory. SRANNameBfConvert indicates the name of the
co-MPT base station before reconstruction.
 SRANName: name of the co-MPT base station after reconstruction. It must be different
from the base station name before reconstruction. If it is left blank, a name of the base
station with the reference mode will be created automatically. The name that is
automatically created uses the NE name of the reference mode specified by the
SRANBaselineRAT field. If SRANBaselineRAT is left unspecified, the NE name of a
more recent mode is used. SRANBaselineRAT must be set to SingleRAN for a hybrid-
MPT base station. If SRANName is unspecified for the hybrid-MPT base station, the
value of SRANNameBfConvert is used.
 OMCHLocalIP and OMCHLocalIPMask: Local IP address and mask of the OM
channel used by the eGBTS after reconstruction. It is used only for GO reconstruction
scenarios. The parameters are optional. If this parameter is not specified, the BTS IP and
mask of the original GBTS are automatically generated.
 NextHop: mandatory when the GBTS uses IPoFE. Enter the next-hop IP address of the
Ethernet interface of the GBTS. (When GSM uses Ethernet transmission, this parameter
must be specified to ensure that a correct route is generated on the GSM side. When the
Abis interface uses layer-2 networking mode, the IP address of the BTS gateway is the
interface IP address of board where the BSC IP address is located. When non-co-
transmission or co-transmission based on panel interconnection is used, enter the next-
hop IP address on the GSM side and the IP address must be on the same network

Copyright © Huawei
segment as the IP address of the Ethernet port type of the BTSDEVIP, and the IP address
cannot be the same as BTSDEVIP. When co-transmission through backplane
interconnection is used, enter the next-hop IP address of the board that provides
transmission, and it must be in the same network segment as the DEVIP of the board but
cannot be the same as the DEVIP.) This field can be left blank if GU co-transmission
through backplane interconnection is applied. This field can be left blank if GL co-
transmission through backplane interconnection is applied and E1 backup transmission is
not used. If GL co-transmission through backplane interconnection is applied and E1
backup transmission is used, this field must be set to the next-hop IP address of the
reference mode.
 IPHCSUBOPT: Fill in this field according to the actual situation (When the base station
directly connects to the base station controller using IP over E1 or connects to the upper-
level base station, set it to DISABLE. When the base station connects to a router using IP
over E1, set it to ENABLE).
 IPoE1OMIP: Enter the original BTSIP or an IP address in the same network segment as
the IP address of the original PPP/MP port. When GSM mode uses transmission of
IP_OVER_FE/GE_AND_E1(E1 backup), this parameter is mandatory.
 ClkSrc: used for base station clock data conversion. The default value NULL indicates
that the clock synchronization is performed in the default order of priority as follows:
GPS > SYNCETH+IPCLK > IPCLK > SYNCETH > LINECLK > TOD > BITS. For a
hybrid clock reference source, you are advised to run the SET CLKMODE command to
manually configure it.
 GTMU Abandoned, UMPTSlot, and GTMU CPRI Move TemplateName: For the
GTMU abandoning scenario, the parameters must be filled. They specify the slot that
holds the main control board where the GSM mode is deployed and the CPRI adjustment
mode of the abandoned GTMU. The CPRI adjustment method of the abandoned GTMU
depends on the information that is filled in the MultiCpriChainMoveTemplate sheet.
 RetainPeerMPT: Specifies whether a UMPT working in non-baseline mode continues
to be used.
If a UMPT working in non-baseline RAT continues to be used, set it to Yes. In this case,
the RAT of the board will be changed and the board will be degraded to a secondary or
standby board. (In this case, if the main control board working in non-baseline RAT is
not detected or powered on, the reconstruction fails.)
If a UMPT working in non-baseline RAT will not be used any longer, set it to No. In this
case, the peer main control processing unit will be degraded to a slave or standby board
using an MML command manually rather than during the reconstruction or the board can
be relocated to be used in other places.
If the peer main control processing unit is a GTMU/WMPT/LMPT, this field does not
affect the reconstruction process.
 MultiBBUCombFlag and MultiBBUCombTemplateName
If two BBUs that are combined into one BBU through co-MPT reconstruction, this field
is mandatory. It is used to plan the mode in which two BBUs are combined into one
BBU. Users must enter the adjustment mode in the MultiBBUCombTemplate sheet.
 MPTType
Main control board type after the co-MPT reconstruction, mandatory The default value is
UMPT if the parameter is not filled out.
In the GTMU SingleOM scenario, the field must be filled with GTMUb or GTMUc. The
fields used in the GTMU abandoning scenario must not be selected. The field and the
fields involved in the GTMU abandoning scenario are mutually exclusive.

Copyright © Huawei
If a UMPT is used as the main control board after reconstruction and the original main control
board uses optical ports, run the DSP ETHPORT command to query the data rate over the
port before replacing the board. This ensures that the data rate at the local end is the same as
that at the peer end. If the data rates are different, optical port negotiation fails and
transmission is interrupted.
 UmptBrdspec
Hardware type of the UMPT after the reconstruction, optional The default value is
UMPTa or UMPTb if the parameter is not filled out.
If the main control board for a co-MPT base station is the UMPTe in reconstruction
scenarios, fill this field with UMPTe.
The UMPTa/b and UMPTe with the same specifications have the same model but different
capabilities. The configured specifications after reconstruction may exceed the board
capability. Therefore, the configuration cannot take effect even though succeeds. It is
recommended that the configured specifications be checked to determine whether they have
exceeded the actual board capability. If they have exceeded the actual board capability, the
extra specifications cannot take effect. For details, see the notes for the following MML
commands in 3900 Series Base Station MML reference for SRAN12.0:
ADD CPBEARER
ADD SCTPLNK
ADD ACL
ADD ACLRULE
ADD IPSECPOLICY
ADD IKEPEER
ADD SECURITYPEER
ADD SCTPPEER

Copyright © Huawei
1. UmptBrdspec indicates the type of a UMPT after reconstruction and its default value is
UMPTa or UMPTb. Set this field to the type of the configured UMPT. If this field is
improperly set, configuration cannot take effect after conversion due to the different cell
specifications supported by the UMPTa/UMPTb and UMPTe.
2. If the base station before reconstruction uses E1/T1 transmission (including E1/T1 over IP
or E1/T1 over ATM), the UMPTe cannot serve as the main control board for the co-MPT
base station after reconstruction because the UMPTe does not support E1/T1 transmission.
3. If the UMPTe serves as the main control board for the co-MPT base station after
reconstruction, the main control boards (including WMPT and LMPT) before
reconstruction are abandoned and removed from the subrack, and the main control board
(UMPTa/b) before reconstruction is retained and serves as the signaling extension board
for the UMPTe.
 LmptEthPort0Attribute and LmptEthPort1Attribute

The two fields must be set if the main control board is reconstructed from an LMPT to a
UMPTe.
The two fields indicate the optical/electrical attributes of the Ethernet ports 0 and 1 on
the LMPT. If the two fields are not filled out, NULL is used by default. If Ethernet ports
0 and 1 on the LMPT are used and the optical/electrical attributes are not configured or
being set to AUTO, the two fields must be filled out.
The system converts the data configurations according to the following principles and
the actual transmission must also be deployed as follows:
LMPT electrical port 0 is converted to UMPTe electrical port 0.
LMPT electrical port 1 is converted to UMPTe electrical port 2.
LMPT optical port 0 is converted to UMPTe optical port 1.
LMPT optical port 1 is converted to UMPTe optical port 3.
 OnlyConvertBaselineTranFlag
From SRAN10.1 onwards, the transport data of only the reference mode is incorporated
into the co-MPT base station during co-MPT data conversion. Fill this field with Yes.
Its default value is No, indicating that transport data of both reference and non-reference
modes is incorporated.
If OnlyConvertBaselineTranFlag on the SitePlanning page is set to Yes, the transport data of only the
reference mode is incorporated into the co-MPT base station and that of the non-reference mode must be
manually entered according to the actual situation.
For the manual configuration method, see 3900 Series Base Station Initial Configuration Guide for
SRAN12.0 > Creating Base Stations > Creating Co-MPT Base Stations > Creating a Single Co-
MPT Base Station > Configuring Transport Data About the Co-MPT Base Station.

Copyright © Huawei
(3) Filling out the MultiCpriChainMoveTemplate Sheet
This template must be filled out in the reconstruction scenario where the GSM mode is included and the
GTMU is to be abandoned.
The CPRI adjustment method of the abandoned GTMU depends on the information that is
filled in the MultiCpriChainMoveTemplate sheet.
In scenarios where the GTMU is to be abandoned and GSM baseband signals are processed
by RF modules, a UBRI or UBBPd can be added during the reconstruction to carry CPRI
signals of GSM. Alternatively, the UBBPd for UMTS or LTE can also be used to carry the
CPRI signals of GSM. In scenarios where the baseband processing board of UMTS or LTE is
WBBP or LBBP, respectively, the WBBP or LBBP cannot be replaced with the UBBPd
during the reconstruction. Therefore, a UBRI is added to carry the CPRI signals of GSM.
For example, Default_Template is used in GTMU abandoning scenarios where the UMTS
baseband processing board is WBBP and a UBRI is to be added for processing GSM signals.
Move all the CPRI ports on the GTMU to the UBRI in slot 1, as shown in the following
templates.
The information of all CPRI ports on the GTMU to be abandoned must be filled in the
following table for the replacement. The GTMU CPRIPort field indicates a CPRI port on the
GTMU. The GTMU CPRIPort Need CpriMux field indicates whether CPRI-Sharing is
used by GSM CPRI ports after the relocation. The Dest UBRI/UBBP BrdType, Dest
UBRI/UBBP Slot, and Dest UBRI/UBBP CPRIPort fields indicate the positions where the
GTMU CPRI ports are located after being relocated.
In the GTMU abandoning scenario where the baseband processing board of UMTS or LTE is
the UBBPd, if there is no idle CPRI port on the UBBPd, you can set the GTMU CPRIPort

Copyright © Huawei
Need CpriMux field to convert the CPRI dual-star typology before the reconstruction to the
CPRI chain typology. As shown in the following table, move the CPRI cables on the GTMU
into the specified ports on the UBBPd in slot 2 and slot 3. CPRI port 0 on the GTMU does not
connect to any fiber optic cable. Instead, the fiber optic cable inserted in CPRI port 4 on the
UBBPd in slot 2 is converted to use CPRI sharing.
(4) Filling out the MultiBBUCombTemplate Sheet
This sheet needs to be filled out for con-MPT reconstruction scenarios where two BBUs are combined
into one.
Users must enter the adjustment mode in the MultiBBUCombTemplate sheet.

Fill in this template according to the guide in MultiBBUCombTemplate.
Ensure that the main control board deployed with the reference mode is retained after site
consolidation.
2. Adjusting data for WMPT/LMPT evolution

Copyright © Huawei
During a co-MPT reconstruction from a UO, LO, UL, or some hybrid-MPT base stations,
convert the replaced WMPT or LMPT.
If the UMPTe serves as the main control board for the co-MPT base station after
reconstruction, the main control boards (including WMPT and LMPT) before reconstruction
are abandoned and removed from the subrack, and the main control board (UMPTa/b) before
reconstruction is retained and serves as the signaling extension board for the UMPTe.
(1) Adjusting data for WMPT evolution

After the co-MPT base station works properly, run the ADD BRD command to add a WMPT
board with Board Type set to WMPT and Slot No. set to 6. You cannot abandon the WMPT
without customer's permission. The WMPT must be in position but not be used.
(2) Adjusting data for LMPT evolution
After the co-MPT base station works properly, run the ADD BRD command to add an LMPT
board with Board Type set to LMPT and Slot No. set to 6.
3. Modifying GSM clock parameters
For the reconstruction of UMTS and LTE, if the original base station is a GSM and UMTS or
GSM and LTE multimode base station, check whether ClkType is set to PEER_CLK and
STANDARD is set to UMTS or LTE. If ClkType is set to PEER_CLK and STANDARD is
set to UMTS or LTE, set STANDARD to COMM.
(1) On the BSC LMT, run the LST BTSCLK command to check whether ClkType is set to
PEER_CLK and STANDARD is set to UMTS or LTE.
(2) If ClkType is set to PEER_CLK and STANDARD is set to UMTS or LTE, run the SET
BTSCLK command to modify STANDARD to COMM.
4. Modifying the OMCH IP of NodeBs on the MBSC
If a UMTS&LTE separate-MPT base station is to be reconstructed into a co-MPT base station
with mode expansion, and the LTE main control board is to be used as the main control board
of the co-MPT base station, adjust the OMCH IP of the corresponding MBSC of NodeB.
(1) Run the LST OMCH command to query the OMCH IP of the eNodeB.
(2) Run the MOD UNODEBIP command to modify the OMCH IP of the NodeB. Make the
OMCH IP of eNodeBs consistent with the NodeB. The following is an example: MOD
UNODEBIP: IDTYPE=BYID, NODEBID=1, NBTRANTP=IPTRANS_IP,
NBIPOAMIP="10.171.35.123", NBIPOAMMASK="255.255.255.0", IPSRN=0, IPSN=18,
IPLOGPORTFLAG=NO;
 Service impact
Adding a new mode for mode Services of the original mode are not affected.
expansion with co-MPT
configuration
Co-MPT reconstruction Services of the original mode are interrupted.

Copyright © Huawei
3.5 BBU Interconnection

This section describes BBU interconnection planning.
3.5.1 Overall BBU Interconnection Planning Process

Figure 1.14 Overall BBU interconnection planning process
Table 14.1 Comparison between interconnection through UCIU+UMPT and interconnection

through UMPT+UMPT
Comparison Interconnection Through Interconnection Through
Item UCIU+UMPT UMPT+UMPT
BBU Only BBU3900s can be The following BBU combination is

hardware interconnected through supported:
requirement UCIU+UMPT. BBU3900+BBU3900
The BBU3910 does not BBU3900+BBU3910
support BBU interconnection
through UCIU+UMPT. BBU3910+BBU3910
The BBU3910A does not The BBU3910A does not support BBU
support BBU interconnection interconnection.
Requirement The length of cables for BBU The length of cables for BBU

Copyright © Huawei
Comparison Interconnection Through Interconnection Through

Item UCIU+UMPT UMPT+UMPT
for distance interconnection can be 2 interconnection can be 2 meters or 5

between meters or 10 meters. meters. BBUs cannot be installed over
BBUs five meters apart.
Hardware Primary BBU subrack: No Primary BBU subrack: Only the UMPT
requirement special requirements are can be configured.
for the main imposed on the main control Secondary BBU subrack: Only the
control board board. UMPTb or UMTP of a later version can
Secondary BBU subrack: Only be configured.
the UMPT can be configured.
Cost The UCIU must be purchased. No additional board is required. Replace
the main control board if its type does
not support BBU interconnection
through UMPT+UMPT.
Feature The root BBU supports UMPT UMPT cold backup is not supported.
Limitations cold backup.
In single-mode or co-MPT and A transmission port must be provided
inter-subrack scenarios, a by a transmission board in the primary
transmission port must be BBU subrack.
provided by a transmission
board in the primary BBU
subrack.
RRUs connected to the If a GTMU, WMPT, or LMPT is
secondary BBU subrack can configured in the primary BBU subrack,
be cascaded. RRUs connected to the secondary BBU
subrack cannot be cascaded.
Slot A UCIU occupies one slot. N/A
Installability N/A Special cables are used for BBU
interconnection through UMPT+UMPT
and the two ends of the cables are
different. If the cables are incorrectly
connected, mode transition may fail.
Table 14.2 Scenario analysis of BBU interconnection

Category Scenario
BBU 3.5.2Adding a BBU for BBU Interconnection Through UCIU+UMPT

interconnection
3.5.3Adding a BBU for BBU Interconnection Through UMPT+UMPT

Copyright © Huawei
3.5.2 Adding a BBU for BBU Interconnection Through

UCIU+UMPT
Figure 1.15 BBU interconnection through UCIU+UMPT

BBU interconnection applies to a separate-MPT triple-mode GUL base station or a separate-
MPT dual-mode base station. Two BBUs must be configured for the triple-mode GUL base
station. In the dual-mode scenarios, some customers prefer two BBUs working in different
modes. The two application scenarios (two BBU in different modes and two BBUs for triple
modes)are similar, and therefore details about BBU interconnection for dual-mode are not
provided.
2. Precautions
None
BBU interconnection through UCIU+UMPT is supported from SRAN7.0 onwards.
For the earliest mapping relationship between the UMPT board and version, see 3900 Series

Copyright © Huawei
None
A UCIU occupies one slot in the primary BBU subrack. The BBU that is configured with the
UCIU is the primary BBU subrack (BBU 0). You can configure the UCIU in slot 4, 5, 0, or 1
(in the descending order of priority) in BBU 0.
The main control board in the leaf BBU (BBU 1) for interconnection must be the UMPT.
An inter-BBU signal cable is used to connect an M port on the UCIU in BBU 0 to a CI port
on the UMPT in BBU 1. You are advised to use the following M ports on the UCIU in
sequence: M0, M1, M2, M3, and M4.
Be aware of the distance limitations for BBU interconnection. The maximum length of an
inter-BBU signal cable for BBU interconnection through UCIU+UMPT can be 10 meters. If
an inter-BBU signal cable of over 10 meters is required, you need to customize it first.
The BBU3910 cannot be configured with a UCIU.
When two BBUs are interconnected, the monitoring device must be connected to BBU 0 and
related software can be configured in and monitored by the mode configured in the primary
BBU subrack.
In separate-MPT scenarios, GSM (GBTS/eGBTS) must be deployed only in BBU 0.
A UCIU must be configured in the primary BBU subrack (BBU 0). If two modes are
configured in the primary BBU subrack, the UCIU can be configured only with one mode and
the mode's priority is GSM, UMTS, and LTE in a descending order.
The cabinet and subrack numbers of the primary BBU subrack and secondary BBU subrack
must be unique and do not conflict with each other.
The CTRLLNK or BTSCTRLLNK MO must be configured for all involved modes.
Ports of each control link and BTS control link must be determined for both sides. Links to
BBU 0 and BBU 1 are of different levels. By default, BBU 1 is the lower-level node and BBU
0 is the upper-level node.
Numbers of control links and BTS control links must be unique and do not conflict with each
other.
Data of control links and BTS control links must be the same for all modes in the root and leaf
BBUs.
Table 15.1 MOC

Domai Configu MOC Param Param Value CME Type
n ration eter ID eter (Example)
Object Name
BBU Mode in CTRLLNK LN Local 0 Equipment

intercon the root Link
nection BBU No.
BBU All CTRLLNK CN Local 0 Equipment
intercon modes in Cabinet
nection the root No.
BBU

Copyright © Huawei

Object Name
BBU All CTRLLNK SRN Local 1 Equipment

intercon modes in Subrack
BBU
BBU All CTRLLNK SN Local 7 Equipment
intercon modes in Slot
BBU
BBU All CTRLLNK UPCN Upper 0 Equipment
BBU
BBU All CTRLLNK UPSRN Upper 0 Equipment
BBU
BBU All CTRLLNK UPSN Upper 4 Equipment
BBU
BBU All CTRLLNK UPPT Upper 0 Equipment
intercon modes in Port
BBU
BBU All CTRLLNK LN Local 0 Equipment
intercon modes in Link
BBU
BBU All CTRLLNK CN Local 0 Equipment
BBU
BBU All CTRLLNK SRN Local 1 Equipment
BBU
BBU All CTRLLNK SN Local 7 Equipment
BBU
BBU All CTRLLNK UPCN Upper 0 Equipment
BBU

Copyright © Huawei

Object Name
BBU All CTRLLNK UPSRN Upper 0 Equipment

BBU
BBU All CTRLLNK UPSN Upper 4 Equipment
BBU
BBU All CTRLLNK UPPT Upper 0 Equipment
intercon modes in Port
BBU
 Service impact
No Inter-BBU SDR Services carried by the secondary BBU subrack do not

affect those carried by the primary BBU subrack.
Inter-BBU SDR Install interconnection cables first and then connect
cables for inter-BBU SDR. If the cables are installed in a
reverse order, SDR services will be affected.
 Related documents
BBU Interconnection Feature Parameter Description for SRAN12.0

Copyright © Huawei
3.5.3 Adding a BBU for BBU Interconnection Through

UMPT+UMPT
Figure 1.16 BBU interconnection through UMPT+UMPT

BBU interconnection applies to a separate-MPT triple-mode GUL base station or a separate-
MPT dual-mode base station. Two BBUs must be configured for the triple-mode GUL base
station. In the dual-mode scenarios, some customers prefer two BBUs working in different
modes. The two application scenarios (two BBU in different modes and two BBUs for triple
modes)are similar, and therefore details about BBU interconnection for dual-mode are not
provided.
In co-MPT scenarios, if the slots of baseband processing boards in one BBU are not
sufficient, one more BBU is required. In this case, the two BBUs must be interconnected.
2. Precautions
None
BBU interconnection through UMPT+UMPT is supported from SRAN8.1 onwards.
For the earliest mapping relationship between the UMPT board and version, see 3900 Series

Copyright © Huawei
The distance between BBU 0 (root BBU) and BBU 1 (leaf BBU) is less than or equal to
five meters. The end with rings in yellow of the BBU interconnection cable must be
connected to BBU0 while the other end with no ring must be connected to BBU1.
UMPTb boards must be deployed in BBU 1.
When a GTMU, WMPT, or LMPT board is deployed in BBU 0, BBU1 does not support
RRU cascading.
A BBU interconnection cable provided by Huawei must be used and BBU
interconnection using a fiber optic cable is not supported.
A transmission port must be provided by a transmission board in the primary BBU
subrack.
When two BBUs are interconnected, the monitoring device must be connected to BBU 0
and related software can be configured in and monitored by the mode configured in the
primary BBU subrack.
In separate-MPT scenarios, GSM (GBTS/eGBTS) must be deployed only in BBU 0.
None
The cabinet and subrack numbers of the primary BBU subrack and secondary BBU subrack
must be unique and do not conflict with each other.
The CTRLLNK or BTSCTRLLNK MO must be configured for all involved modes.
Ports of each control link and BTS control link must be determined for both sides. Links to
BBU 0 and BBU 1 are of different levels. By default, BBU 1 is the lower-level node and BBU
0 is the upper-level node.
Numbers of control links and BTS control links must be unique and do not conflict with each
other.
Data of control links and BTS control links must be the same for all modes in the root and leaf
BBUs.
Table 16.1 MOC

Object Name

intercon the root Link
nection BBU No.
BBU Mode in CTRLLNK CN Local 0 Equipment
intercon the root Cabinet
nection BBU No.
BBU Mode in CTRLLNK SRN Local 1 Equipment
intercon the root Subrack
nection BBU No.
BBU Mode in CTRLLNK SN Local 7 Equipment
intercon the root Slot
nection BBU No.

Copyright © Huawei

Object Name
BBU Mode in CTRLLNK UPCN Upper 0 Equipment

intercon the root Cabinet
nection BBU No.
BBU Mode in CTRLLNK UPSRN Upper 0 Equipment
intercon the root Subrack
nection BBU No.
BBU Mode in CTRLLNK UPSN Upper 7 Equipment
intercon the root Slot
nection BBU No.
BBU Mode in CTRLLNK UPPT Upper 8 Equipment
intercon the root Port
nection BBU No.
intercon the leaf Link
nection BBU No.
BBU Mode in CTRLLNK CN Local 0 Equipment
intercon the leaf Cabinet
nection BBU No.
BBU Mode in CTRLLNK SRN Local 1 Equipment
intercon the leaf Subrack
nection BBU No.
BBU Mode in CTRLLNK SN Local 7 Equipment
intercon the leaf Slot
nection BBU No.
BBU Mode in CTRLLNK UPCN Upper 0 Equipment
intercon the leaf Cabinet
nection BBU No.
BBU Mode in CTRLLNK UPSRN Upper 0 Equipment
intercon the leaf Subrack
nection BBU No.
BBU Mode in CTRLLNK UPSN Upper 7 Equipment
intercon the leaf Slot
nection BBU No.
BBU Mode in CTRLLNK UPPT Upper 8 Equipment
intercon the leaf Port
nection BBU No.
 Service impact
No Inter-BBU SDR Services carried by the secondary BBU subrack do not

Copyright © Huawei
affect those carried by the primary BBU subrack.

Inter-BBU SDR Install interconnection cables first and then connect
cables for inter-BBU SDR. If the cables are installed in a
reverse order, SDR services will be affected.
BBU Interconnection Feature Parameter Description for SRAN12.0
3.6 Clock Planning

This section describes co-MPT or separate-MPT planning.
3.6.1 Overall Clock Planning Process

Figure 1.17 Overall clock planning process
 Check whether the original clock can be shared.

Currently, the following reference clocks can be used in a separate-MPT base station:
GPS clock, BITS clock, E1/T1 clock, IEEE1588v2 clock, and synchronous Ethernet clock.
For UMTS, when the WMPT, UTRP2, or UTRP9 uses the IEEE1588v2 reference clock, the
reference clock cannot be shared by any other mode.
 Check whether the new mode can reuse the original clock.

Copyright © Huawei
If the new mode has time synchronization requirements and the original clock source is not of
the time synchronizing type, the original reference clock source cannot be shared.
 Comparison between independent clock and common clock
Compari Independent Clock Common Clock
son Item
Clock GPS clock, BITS clock, E1/T1 GPS clock, BITS clock, E1/T1 clock,
type clock, IEEE1588v2 clock, IEEE1588v2 clock, and synchronous
synchronous Ethernet clock, and Ethernet clock.
1PPS+TOD clock
Working The working mode of the clock in a multimode base station cannot be set to
mode AUTO(Automatic). Only one type of reference clock can be configured for
each mode and the main control board of each mode. Reference clock backup
is not supported.
Inter- Loose coupling: The inter-RAT Loose coupling: Inter-RAT impact is small
RAT external clock source works or none. If a base station fails to obtain
decouplin independently. clock signals, it works in free-run mode for
g a certain period of time. The period can be
as long as three months if frequency
synchronization is used.
Customer An independent clock source is No additional clock source requirement is
Requirem configured for the new mode posed by the new mode.
ents because the customer has
required for sufficient clock
source. For example, for
IEEE1588v2, a customer may
require capacity expansion of the
IP clock server to support the
clock source requirements of the
new mode.
 Requirements of new modes for the original reference clock source

Time synchronization (or phase synchronization) is available on the basis of frequency
synchronization. When the new mode has time synchronization requirements and SDR is
used for the original mode and new mode, the clock source of the original mode must
use time synchronization if either of the following events is true. Note that the reference
clock of time synchronization can be shared or not.
- GSM (GTMU used) is one of the original modes. If the reference clock source for time
synchronization is provided by the new mode, Clock Type and Peer Mode must be set
to PEER_CLK and the new mode, respectively.
- Inter-BBU SDR is used. If the secondary BBU subrack requires time synchronization,
time synchronization must be used for the reference clock of the primary BBU subrack.
- In mode transition from FDD/NB-IoT to FDD/NB-IoT+TDD, adding the USCU clock
board or other ways can be used to obtain the GPS clock.
When time synchronization clock source is configured for the GSM main control board, specify the
frame synchronization switch FRAMESYNCSW based on whether inter-site frame number
synchronization must be supported:

Copyright © Huawei
 Set FRAMESYNCSW to OFF if GBTS or eGBTS services do not need to support inter-site frame
number synchronization.
 Set FRAMESYNCSW to ON if the GBTS must support
Before setting FRAMESYNCSW to ON, you need to perform frame number offset and training
sequence code planning to prevent interference between GSM neighboring cells.
The GTMUa board does not support time synchronization. When time synchronization is required, the
GTMUa board cannot be used and must be replaced.
Table 17.1 Mode transition scenario analysis

Category Scenario
Clock 3.6.2New Mode Using an Independent Reference Clock with Separate-

MPT Configuration
3.6.3New Mode and Original Mode Sharing Reference Clock with
Separate-MPT Configuration
3.6.4New Mode Requiring Modification to the Clock Source with Co-
MPT Configuration
3.6.2 New Mode Using an Independent Reference Clock with

Separate-MPT Configuration
In this scenario, a new mode uses an independent reference clock.
2. Precautions
None
None
None
There is no special requirement. You can configure the data in the same way as that for
configuring a reference clock. For details, see the initial configuration guide of each
mode.
 Service impact
None
Synchronization Feature Parameter Description for GBSS19.0
Synchronization Feature Parameter Description for WCDMA RAN19.0
Synchronization Feature Parameter Description for eRAN12.0
Synchronization Feature Parameter Description for eRAN TDD 12.0

Copyright © Huawei
3.6.3 New Mode and Original Mode Sharing Reference Clock

with Separate-MPT Configuration
Based on the preceding analysis, co-transmission is required.
2. Precautions
None
The version requirement of clock sharing varies with the reference clock.
For details, see Common Clock Feature Parameter Description for SRAN12.0.
(SBOM) (BBOM)
Multi-mode None None None per BTS G

BS Common
Reference
Clock(GBT
S)
Multi-mode None None None per NodeB U
BS Common
Reference
Clock(Node
B)
Multi-mode Multi-mode 81201529 LLT1MCRC Per eNodeB L
BS Common BS Common 01
Reference Reference
Clock(eNod Clock(eNod
eB) eB)(Per
eNodeB)
Multi-mode Multi-mode 81202017 LLT1TMCR Per eNodeB L
BS Common BS Common C01
Reference Reference
Clock (per Clock(TDD)
eNodeB)
Multi-mode Multi-mode 81202567 LML1MCR Per eNodeB L
BS Common BS Common C01
Reference Reference
Clock(NB- Clock(NB-
IoT) (per IoT)
eNodeB)

Copyright © Huawei

Set the clock source of the new mode to PEER so that the new mode and original mode share
the same clock source. For details, see Common Clock Feature Parameter Description.
Reference for SRAN12.0: Common Clock Feature Parameter Description
Configure MOs related to the peer clock.
GBTS:

ter ID Parameter
Name Name
BTSCLK Clock ClkType Clock Type PEER_CLK

Type
BTSCLK Peer STANDAR Peer Mode Set this parameter to the mode of
Mode D the reference clock.
eGBTS, NodeB, eNodeB, or co-MPT multimode base station

ter ID Parameter
Name Name
CLKMO Clock MODE Clock Set this parameter to

DE Working Working MANUAL(Manual).
Mode Mode
CLKMO Selected CLKSRC Selected Set this parameter to
DE Clock Clock PEERCLK(Peer Clock).
Source Source
PEERCL Peer PN Peer Clock Set this parameter to 0.
K Clock No.
No.
PEERCL Peer PS Peer Set this parameter to the mode of
K Standard Standard the reference clock.
 Service impact
None
Reference for SRAN12.0: Common Clock Feature Parameter Description
3.6.4 New Mode Requiring Modification to the Clock Source with

Co-MPT Configuration

Copyright © Huawei
In co-MPT scenarios, a new mode requires a modification to the clock source of the original
mode. For example, if the new mode LTE TDD requires time synchronization, modify the
clock source type of the main control board of the original mode to support time
synchronization.
2. Precautions
None
The reference clock of the new mode has requirements on the version. For details, see
the following documents:
Do Feature License License License Sales Unit Mode
mai Name Control Item Control Abbrevi
n Name Item ation
(SBOM) Name
(BBOM)
Clo Enhanced Enhanced Enhanced LLT1ENS per eNodeB L

ck Synchroniza Synchronizati Synchron Y01
tion on (per ization(F
eNodeB) DD)
Clo Enhanced Enhanced Enhanced LLT1TE per eNodeB L
ck Synchroniza Synchronizati Synchron NSY01
tion on (per ization(T
eNodeB) DD)
Clo Enhanced Enhanced Enhanced LML1EN per eNodeB L
ck Synchroniza Synchronizati Synchron SY01
tion on (per ization(N
eNodeB) B-IoT)

There is no special requirement. You can configure the data in the same way as that for
configuring a reference clock. For details, see the following documents:
Cloc New-mode GPS GPS GN 0 Equipment

base station Clock

Copyright © Huawei
k No.
New-mode GPS Cable CABLE_L 30 Equipment
base station Length EN
New-mode GPS GPS MODE GPS Equipment
base station workin
g mode
New-mode GPS Priority PRI 1 Equipment
base station
New-mode IPCLK Link LN 0 Equipment
base station LNK No.
New-mode IPCLK Client CIP 82.0.1.107 Equipment
base station LNK IPv4
New-mode IPCLK Server SIP 82.0.1.128 Equipment
base station LNK IPv4
New-mode IPCLK Domain DM 0 Equipment
base station LNK
New-mode IPCLK Priority PRI 1 Equipment
base station LNK
New-mode TASM Clock MODE MANUAL Equipment
base station Workin
g Mode
New-mode TASM Selecte CLKSRC GPS Equipment
base station d Clock
Source
New-mode TASM Clock SRCNO 0 Equipment
base station Source
No.
New-mode TASM Clock CLKSYNC TIME Equipment
base station Synchr MODE
onizatio
n Mode
 Service impact
None

Copyright © Huawei
3.7 Baseband Planning

This section describes baseband planning.
3.7.1 Overall Baseband Planning Process

Figure 1.18 Overall baseband planning process
 Comparison between co-baseband and independent baseband

Comparison Independent Baseband Co-Baseband
Item
Working Single mode Multimode concurrency

mode
Hardware All baseband processing boards Only the UBBP or UMDU supports
support independent baseband. co-baseband. The UMDU does not
There are no special requirements support mode transition from LTE
for co-MPT configuration. TDD only to LTE FDD and LTE
TDD.
Co-MPT must be configured for co-
baseband application.
For hybrid-MPT scenarios, co-MPT
must be configured for modes
involved in co-baseband.
Inter-RAT Baseband processing boards of Baseband boards of each mode are
decoupling each mode work independently. tightly coupled. If one baseband
processing board is faulty, the other

Copyright © Huawei
Baseband boards of each mode processing baseband becomes

are loosely coupled. With CPRI faulty, too.
MUX, IQ signals are exchanged
through the BBU backplane.

or Co-MPT
Baseband Separate-MPT 3.7.2Adding an Independent Baseband Board to the New

planning Mode with Separate-MPT Configuration
Co-MPT mode 3.7.3Adding an Independent Baseband Processing Board
expansion to the New Mode with Co-MPT Configuration
3.7.4Adding a New Mode to the Original Baseband
Processing Board with Co-MPT Configuration
Currently, FDD and TDD co-BBP is unavailable on a UBBPd/UBBPe. If FDD and TDD co-
BBP is required, apply to the SRAN or LTE Requirement Management Team (RMT).
3.7.2 Adding an Independent Baseband Board to the New Mode

with Separate-MPT Configuration
In a separate-MPT base station, an independent baseband board is added to the new mode for
mode transition.
 For details about how to select a GSM, UMTS, or LTE FDD baseband processing board,
see GUL Base Station Overview and Selection Guide.
 For details about how to select an LTE TDD baseband processing board, see LTE TDD
Solution Guide.
2. Precautions
- Slots 2 and 3 in the BBU3900 serve as the switching center. The NodeB can provide CPRI
ports only in slot 2 or 3 to connect RRUs. LTE also requires a baseband processing board in
slot 2 or 3.
- The preceding constraint does not apply to the BBU3910 because it has a higher backplane
switching capability.
- Pay attention to the board types supported by the BBU3910 that no longer supports some old
types of baseband processing boards. For details, see Description > Hardware Description >
BBU Hardware Description > BBU3900 and BBU3910 Hardware Description > Boards
and Cabinets or Racks Supported by BBUs in 3900 Series Base Station Product
Documentation. For details about the specifications about baseband processing boards, see the

Copyright © Huawei
Baseband&Signalling and UBBP sheets in SingleRAN Multi-mode BTS Product

Specification.
Board LBBP/UBBP Determined by the

number of cells and
number of initial
TX/RX channels
WBBP/UBBP Determined by the
number of cells and
number of CEs
UBRIb The UBRI must be
configured if it
provides CPRI ports
for the GSM mode.
No specific license control item is available for the baseband processing board working in a
separate-MPT multimode base station.
Mode licenses related to the UBBP must be purchased and delivered even when co-baseband
is not used.
Mode License Control License Control License License

Item Name Item Name BBOM Abbreviat
(SBOM) (BBOM) ion
GSM UBBP First-Mode UBBP Multi-Mode 82204551 LGMIUBB

license (GSM) license (GSM) P
UBBP Multi-Mode UBBP Multi-Mode 82204551 LGMIUBB
license (GSM) license (GSM) P
UMTS UBBP First-Mode UBBP Multi-Mode 82204657 LQW9UBP
license (UMTS) license (UMTS) DM01
UBBP Multi-Mode UBBP Multi-Mode 82204657 LQW9UBP
license (UMTS) license (UMTS) DM01
LTE UBBP First-Mode N/A 88032BXR WDMS0UF
license (LTE FDD) (SBOM) MLF00

Copyright © Huawei
Mode License Control License Control License License

Item Name Item Name BBOM Abbreviat
(SBOM) (BBOM) ion
UBBP Multi-Mode N/A 88032BXS WDMS0U

license (LTE FDD) (SBOM) MMLF00
UBBP First-Mode N/A 88032KLF LT1SUMM

license (LTE TDD) (SBOM) LFL01
UBBP Multi-Mode N/A 88032GDN LT1SUMM

license (LTE TDD) (SBOM) LFL00
UBBP First-Mode N/A 88033TFB( ML1SUBB

license (NB-IoT) SBOM) PMM00
UBBP Multi-Mode N/A 88033TFC( ML1SUMP
license (NB-IoT) SBOM) TMM00
Note: In independent baseband scenarios, you only need to purchase the first-mode license for
the UBBP based on its working mode in terms of the SBOM. SBOM and BBOM information
about the related licenses is the same.
In separate-MPT or independent baseband scenarios, there is no impact on the data
configuration for the original mode, and the data configuration for the new mode is the same
as that for single-mode scenarios.
 Service impact
None
3.7.3 Adding an Independent Baseband Processing Board to the

New Mode with Co-MPT Configuration
In a co-MPT base station, an independent baseband processing board is added to the new
mode for mode transition.
The BBU3910A does not support BBU interconnection because only one baseband processing
board is configured.
For details about how to select a baseband processing board, see GUL Base Station Overview
and Selection Guide or LTE TDD Solution Guide.
2. Precautions
- Slots 2 and 3 in the BBU3900 serve as the switching center. The NodeB can provide CPRI
ports only in slot 2 or 3 to connect RRUs. LTE also requires a baseband processing board in
slot 2 or 3.
- The preceding constraint does not apply to the BBU3910 because it has a higher backplane
switching capability.

Copyright © Huawei
- Pay attention to the board types supported by the BBU3910 that no longer supports some old
types of baseband processing boards. For details, see Description > Hardware Description >
BBU Hardware Description > BBU3900 and BBU3910 Hardware Description > Boards
and Cabinets or Racks Supported by BBUs in 3900 Series Base Station Product
Documentation.
Board LBBP/UBBP Determined by the

number of cells and
number of initial
TX/RX channels
WBBP/UBBP Determined by the
number of cells and
number of CEs
UBRIb The UBRI must be
configured if it
provides CPRI ports
for the GSM mode.
For the mapping relationship between the baseband processing board and version, see 3900
Series Base Station Hardware and Software Compatibility Description for SRAN12.0.
No specific license control item is available for the baseband processing board working in a
separate-MPT multimode base station.
Mode licenses related to the UBBP must be purchased and delivered even when co-baseband
is not used.
Mode License Control Item License Control License License

Name (SBOM) Item Name BBOM Abbreviat
(BBOM) ion
GSM UBBP First-Mode license UBBP Multi-Mode 82204551 LGMIUBB

(GSM) license (GSM) P
UBBP Multi-Mode license UBBP Multi-Mode 82204551 LGMIUBB
UMTS UBBP First-Mode license UBBP Multi-Mode 82204657 LQW9UBP
(UMTS) license (UMTS) DM01
UBBP Multi-Mode license UBBP Multi-Mode 82204657 LQW9UBP

Copyright © Huawei

(BBOM) ion
LTE UBBP First-Mode license N/A 88032BXR WDMS0UF

(LTE FDD) (SBOM) MLF00
UBBP Multi-Mode license N/A 88032BXS WDMS0U

(LTE FDD) (SBOM) MMLF00
UBBP First-Mode license N/A 88032KLF LT1SUMM

(LTE TDD) (SBOM) LFL01
UBBP Multi-Mode license N/A 88032GDN LT1SUMM

UBBP First-Mode license N/A 88033TFB( ML1SUBB

(NB-IoT) SBOM) PMM00
UBBP Multi-Mode license N/A 88033TFC( ML1SUMP
(NB-IoT) SBOM) TMM00
Note: In independent baseband scenarios, you only need to purchase the first-mode license for
the UBBP based on its working mode in terms of the SBOM. SBOM and BBOM information
about the related licenses is the same.
In separate-MPT or independent baseband scenarios, there is no impact on the data
configuration for the original mode, and the data configuration for the new mode is the same
as that for single-mode scenarios.

ter ID Parameter
Name Name
BBP Base BBWS Base Band Determined by the UBBP

Band Work configuration plan
Work Standard
Standard
MDU Base BBWS Base Band Determined by the mode planned
Band Work for the UMDU
Work Standard
Standard
 Service impact
None

Copyright © Huawei
3.7.4 Adding a New Mode to the Original Baseband Processing

Board with Co-MPT Configuration
In a co-MPT base station, the new mode and original mode share the baseboard band.
Baseband processing board selection
If a baseband processing board needs to be added or replaced, select the baseband processing
board as instructed in GUL Base Station Overview and Selection Guide or LTE TDD Solution
Guide.
2. Precautions
Slot planning: Use the cabling tool on the CME to analyze board slots for base station mode
transition. For scenarios that are not supported by the tool, contact Huawei R&D engineers.
If the new mode and original mode share the original baseband processing board, no new
material is required.
If you need to replace the original baseband processing board, or expand the baseband
processing board's capacity, purchase a new UBBP board.
For the mapping relationship between the main control board and version, see 3900
Series Base Station Hardware and Software Compatibility Description for SRAN12.0.
A license related to the new mode can be applied for in the same way as that for the
The following table lists licenses that need to be purchased and delivered for the UBBP
board.
(BBOM) ion
GSM UBBP First-Mode license UBBP Multi-Mode 82204551 LGMIUBB

UBBP Multi-Mode license UBBP Multi-Mode 82204551 LGMIUBB
UMTS UBBP First-Mode license UBBP Multi-Mode 82204657 LQW9UBP
UBBP Multi-Mode license UBBP Multi-Mode 82204657 LQW9UBP
LTE UBBP First-Mode license N/A 88032BXR WDMS0UF
(LTE FDD) (SBOM) MLF00
UBBP Multi-Mode license N/A 88032BXS WDMS0U

(LTE FDD) (SBOM) MMLF00

Copyright © Huawei

(BBOM) ion
UBBP First-Mode license N/A 88032KLF LT1SUMM

UBBP Multi-Mode license N/A 88032GDN LT1SUMM

UBBP First-Mode license N/A 88033TFB( ML1SUBB

(NB-IoT) SBOM) PMM00
UBBP Multi-Mode license N/A 88033TFC( ML1SUMP
(NB-IoT) SBOM) TMM00

Baseband working mode must be configured for the UBBP board.
ter ID Parameter
Name Name
BBP Base BBWS Base Band Determined by the UBBP

Band Work configuration plan
Work Standard
Standard
MDU Base BBWS Base Band Determined by the mode planned
Band Work for the UMDU
Work Standard
Standard
 Service impact
Modify the baseband working Services carried by the baseband processing board are
mode. interrupted for one minute.
3.8 CPRI-based Topology Planning

This section describes CPRI-based topologies used by a base station to RF modules with the
BBU system and how to select a CPRI-based topology based on services. CPRI is short for
common public radio interface.

Copyright © Huawei
3.8.1 Overall CPRI-based Topology Planning

Figure 1.19 Overall CPRI-based topology planning process

Categor Scenario
y
CPRI- 3.8.2Chain Topology for RF Modules

based
topology 3.8.3Dual-Star Topology (Load Sharing) for SDR RF Modules
3.8.4CPRI MUX for SDR RF Modules
RF modules can use CPRI MUX or the dual-star topology in multimode concurrency
scenarios. The dual-star topology is recommended for separate-MPT scenarios while CPRI
MUX is recommended for co-MPT scenarios. The following table provides the comparison
between CPRI MUX and the dual-star topology.
Compari Dual-Star Topology CPRI MUX

son Item
Service If CPRI fiber optical cables are Replace the original baseband
impact installed on a tower and antennas processing board because it does not
and RRUs are installed for the support convergence, which interrupts
new mode, existing services need services. Optical modules of a higher
to be interrupted to ensure data rate may be required to provide
personnel safety. more bandwidth for supporting services
of two modes. The optical module
replacement interrupts services.
Material N pairs of CPRI fiber optic cables (Possible) 2N high-speed optical
cost and 2N optical modules. N varies modules. The replaced optical modules

Copyright © Huawei
Compari Dual-Star Topology CPRI MUX

son Item
with RF modules required for the can be reused for other purposes.
new mode.
Labor Cost for hoisting (if applicable), Cost for hoisting (if applicable) and
Cost installing N pairs of CPRI fiber replacing optical modules
optic cables (high), and installing
optical modules
Reliability Services between different modes The converging party affects the
are not affected. converged party.
Applicatio The dual-star topology is CPRI MUX is supported only by the
n supported by the following WBBPf, LBBPd, UBBPd, and
condition hardware: GTMUb/GTMUc (only being the
GTMUa/GTMUb/GTMUc, converged party). Whether an RF
WBBPb/WBBPd/WBBPf, module supports CPRI MUX depends on
LBBPc/LBBPd, UBBPd, the actual RF module's capabilities as
UBRIa/UBRIb, and V1/2/3 RF promoted by Huawei. Inter-BBU CPRI
modules. MUX is not supported.
3.8.2 Chain Topology for RF Modules

 A new RF module is added and it works in a single mode.
 The following figure is an example.
 Limitations on RF modules: none

 Other limitations: none
2. Precautions
 Limitations on the BBU3900 slot assignment (not applicable to the BBU3910): For
NodeBs, only the baseband processing board in slots 2 and 3 of the BBU in a NodeB is
allowed to provide CPRI ports for connection to RRUs. For eNodeBs, at least one
baseband processing board must be installed in slot 2 or slot 3 and CPRI ports can be
provided by the baseband processing board in slots other than slots 2 and 3.

Copyright © Huawei
 One RF module is connected to the BBU through one CPRI cable. Higher reliability
requires two CPRI cables for connecting the BBU in the ring topology.
 The length of the added CPRI cable is determined according to site survey. Determine
whether the CPRI fiber optic cable or the optical module works in a single mode or
multiple modes.
 If the fiber optic cable is to be reused, check whether the fiber optic cable type matches
the connector. If they do not match, the fiber optic cable must be transferred. For details,
see Reuse Guide and Checklist for CPRI Optical Cables in Distributed Base Stations.
 RF modules supporting LTE FDD cannot be cascaded with those supporting LTE TDD.
For details, see "Chain Topology with CPRI MUX" in CPRI MUX Feature Parameter
Description.
Material Material Quantity Remarks
Type Name
CPRI-based CPRI Same as the number of RRUs or Two ends of the

topology electrical RFUs. Each RFU requires one CPRI CPRI electrical cable
cable electrical cable. are connected to the
RFU and BBU,
respectively.
CPRI fiber Same as the number of RRUs. Each Two ends of the
optic cable RRU requires one CPRI fiber optic CPRI fiber optic
cable. cable are connected
to the RRU and
BBU, respectively.
CPRI optical Twice the number of RRUs or Two ends of the
module RFUs. Each RRU or RFU requires CPRI cable are
one CPRI cable and each of the connected to the
CPRI cables must be configured RRU and BBU,
with two optical modules. respectively.

None
None
No special requirements are involved. The following table provides the related MOs.
MO Parameter Meaning
Chain No. Indicates the ID of the RRU chain. It uniquely identifies a chain within
a base station.
Topo Type Indicates the type of the topology. In the ring topology, service data is
transferred through fiber optic cables on the HDLC links. In load

Copyright © Huawei
sharing, two CPRI fiber optic cables can be used for transferring
service data at the same time, which improves the transmission
capability. The physical states of the ring topology and load sharing
applications are similar.
Backup Mode Indicates the backup mode of the RRU chain or ring, including cold
backup and hot backup. Cold backup indicates that when the link on
one end of the chain or ring fails, the service is interrupted for a short
period of time, and then continues on the other end of the chain or
ring. In hot backup mode, if the link on one end of the chain or ring
fails, the service switches to the other end of the chain or ring
immediately. In hot backup mode, only one RRU can be configured on
each chain. When the Topo Type parameter is set to RING and the
Backup Mode parameter is set to HOT, the head and the tail of the
ring must be configured on different BBUs.
Head Cabinet No. Indicates the cabinet number of the board where the head CPRI port is
located.
Head Subrack No. Indicates the subrack number of the board where the head CPRI port is
located.
Head Slot No. Indicates the slot number of the board where the head CPRI port is
located.
Head Port No. Indicates the number of the head CPRI port.
Tail Cabinet No. Indicates the cabinet number of the board where the tail CPRI port is
located. Value NULL is displayed for the RRU chain which does not
have a tail CPRI port.
Tail Subrack No. Indicates the subrack number of the board where the tail CPRI port is
Tail Slot No. Indicates the slot number of the board where the tail CPRI port is
Tail Port No. Indicates the number of the tail CPRI port. Value NULL is displayed
for the RRU chain which does not have a tail CPRI port.
BreakPoint Indicates the breakpoint position 1 on the chain/ring. When this
Position1 parameter is set to 255, the breakpoint is disabled.
Access Type Indicates the access type of the RRU. The local port is used for the
connection of panels. The BBP is directly connected to the RRU/RFU.
The peer port is used for the convergence of backplane. The BBP is
connected to the IDX2 port to converge on other baseband processing
boards so that the BBP can be connected to the RRU/RFU.
CPRI Line Rate Indicates the user-defined rate. The values are as follows:
Auto: auto-negotiation mode.

Copyright © Huawei
1.25: auto-negotiation mode is not supported and the CPRI rate is 1.25
Gbit/s.
Gbit/s.
Gbit/s.
Gbit/s.
Gbit/s.
Local Slot No. Indicates the slot number of the converged party in CPRI MUX. When
this parameter is set to 255, no slot number of the converged party is
specified. When the BBU where CPRI MUX is used is BBU3900, this
parameter does not need to be specified. When the BBU where CPRI
MUX is used is BBU3910, this parameter must be specified.
Cascading Level Indicates the cascading level of the RRU chain/ring.
RRU No. Indicates the number of RRUs connected on the RRU chain/ring.
 Service impact
Technically, services of the original mode are not affected. However, the related operations
are performed around antennas, you are advised to disable the original RF module based on
the actual site conditions to ensure personal safety.
3.8.3 Dual-Star Topology (Load Sharing) for SDR RF Modules

 New RF modules work in multiple modes or the single mode of original RF modules is
expanded to multiple modes.
 Limitation on RF modules: The RF module must be multimode RF modules (of M

series).

Copyright © Huawei
 Other limitations: For an RRU or RFU whose version is earlier than V3, the dual-star
topology is used and CPRI rates on the two sides must be consistent. The system
automatically negotiates for a CPRI rate that is supported by both sides. Therefore,
during CPRI rate planning, pay attention to the CPRI rate that can be supported by the
optical module or CPRI interface board on the other side. For an RRU or RFU whose
version is later than V3, CPRI rates on the two sides can be different.
2. Precautions
1) In dual-star topology for separate-MPT scenarios, one CRPI link is for one mode and
services of a mode are not affected by other modes. In load sharing for co-MPT scenarios, two
CRPI links are shared by multiple modes and modes are randomly assigned to the CPRI link
based on load balancing rules.
2) The length of the added CPRI cable is determined according to site survey. Determine
whether the CPRI fiber optic cable or the optical module works in a single mode or multiple
modes.
3) If the optical fiber is to be reused, check whether the optical fiber type matches the optical
fiber connector. If they do not match, the optical fiber must be transferred. For details, see
Reuse Guide and Checklist for CPRI Optical Cables in Distributed Base Stations.
1) Expanding the mode of the original RF module to multiple modes
Type Name
CPRI-based CPRI Same as the number of RRUs or Two ends of the

topology electrical RFUs. Each RFU requires one CPRI CPRI electrical cable
RFU and BBU,
respectively.
to the RRU and
BBU, respectively.
2) Adding a new RF module working in multiple modes

Type Name
CPRI-based CPRI Twice the number of RRUs or Two ends of the

topology electrical RFUs. Each RFU requires two CPRI CPRI electrical cable
cable electrical cables. are connected to the
RFU and BBU,

Copyright © Huawei

Type Name
respectively.
CPRI fiber Twice the number of RRUs. Each Two ends of the
optic cable RRU requires two CPRI fiber optic CPRI fiber optic
cables. cable are connected
to the RRU and
BBU, respectively.
CPRI optical Four times the number of the RRUs Two ends of the
module or RFUs Each RRU or RFU requires CPRI cable are

Load sharing in co-MPT scenarios: SRAN8.0 and later
None
Values of the Networking Mode parameter of the RXU chain are changed. The ways to
change the parameter value are different for separate-MPT scenarios and load sharing
scenarios.
Dual-star topology for separate-MPT scenarios: Same as configuration for the chain
topology for the new mode.
Load sharing for co-MPT scenarios: Configure load sharing for the original RRU
configured with the chain topology.
The following table provides the related MOs.
Chain No. Indicates the ID of the RRU chain. It uniquely identifies a chain within
a base station.
Topo Type Indicates the type of the topology. In the ring topology, service data is
transferred through fiber optic cables on the HDLC links. In load
sharing, two CPRI fiber optic cables can be used for transferring
service data at the same time, which improves the transmission
capability. The physical states of the ring topology and load sharing
applications are similar.
Backup Mode Indicates the backup mode of the RRU chain or ring, including cold
backup and hot backup. Cold backup indicates that when the link on
one end of the chain or ring fails, the service is interrupted for a short
period of time, and then continues on the other end of the chain or
ring. In hot backup mode, if the link on one end of the chain or ring
fails, the service switches to the other end of the chain or ring
immediately. In hot backup mode, only one RRU can be configured on
each chain. When the Topo Type parameter is set to RING and the
Backup Mode parameter is set to HOT, the head and the tail of the

Copyright © Huawei
ring must be configured on different BBUs.

Head Cabinet No. Indicates the cabinet number of the board where the head CPRI port is
located.
Head Subrack No. Indicates the subrack number of the board where the head CPRI port is
located.
Head Slot No. Indicates the slot number of the board where the head CPRI port is
located.
Head Port No. Indicates the number of the head CPRI port.
Tail Cabinet No. Indicates the cabinet number of the board where the tail CPRI port is
Tail Subrack No. Indicates the subrack number of the board where the tail CPRI port is
Tail Slot No. Indicates the slot number of the board where the tail CPRI port is
Tail Port No. Indicates the number of the tail CPRI port. Value NULL is displayed
for the RRU chain which does not have a tail CPRI port.
Access Type Indicates the access type of the RRU. The local port is used for the
connection of panels. The BBP is directly connected to the RRU/RFU.
The peer port is used for the convergence of backplane. The BBP is
connected to the IDX2 port to converge on other baseband processing
boards so that the BBP can be connected to the RRU/RFU.
CPRI Line Rate Indicates the user-defined rate. The values are as follows:
Auto: auto-negotiation mode.
Gbit/s.
Gbit/s.
Gbit/s.
Gbit/s.
Gbit/s.
Local Slot No. Indicates the slot number of the converged party in CPRI MUX. When
this parameter is set to 255, no slot number of the converged party is

Copyright © Huawei
specified. When the BBU where CPRI MUX is used is BBU3900, this
parameter does not need to be specified. When the BBU where CPRI
MUX is used is BBU3910, this parameter must be specified.
Cascading Level Indicates the cascading level of the RRU chain/ring.
RRU No. Indicates the number of RRUs connected on the RRU chain/ring.
 Service impact
Technically, services of the original mode are not affected. However, the related
operations are performed around antennas, you are advised to disable the original RF
module based on the actual site conditions to ensure personal safety.
3.8.4 CPRI MUX for SDR RF Modules

 CPRI MUX applies to the following scenarios:
- RF modules work in multiple modes.
- Less optic fiber cables are preferred. Compared with the dual-star topology, CPRI
MUX uses less optic fiber cables though the relationship between modes lessens as well.
- Stadium, subway, and high-speed train scenarios (chain CPRI MUX with multiple
cascading levels).
 Limitations:
Restriction on service specifications: The maximum service specifications of CPRI
MUX are less than those of the dual-star topology. In CPRI MUX, the bandwidth of the
baseband processing board that connects to CPRI fiber optic cables and the backplane
bandwidth of the converging and converged parties of CPRI MUX are limited.
Therefore, the specifications must be calculated based on factors such as the number of
ports connecting to CPRI fiber optic cables, port rate, number of cascaded RF modules,
main control board combination, and baseband processing board type.
For details, see section "Specifications of the CPRI MUX Feature" in CPRI MUX
Feature Parameter Description for SRAN12.0.

Copyright © Huawei
Restriction on the slot and board type: CPRI MUX has requirements on board types that
can be supported by the converging party and converged party. In addition, if a
BBU3900 is used, the converging party must be configured in a certain slot.
For details, see section "BBUs and Boards That Support CPRI MUX" in CPRI MUX
Feature Parameter Description for SRAN12.0.
2. Precautions
- The length of the added CPRI cable is determined according to site survey. Determine
whether the CPRI fiber optic cable or the optical module works in a single mode or multiple
modes.
- If the optical fiber is to be reused, check whether the optical fiber type matches the optical
fiber connector. If they do not match, the optical fiber must be transferred. For details, see
Reuse Guide and Checklist for CPRI Optical Cables in Distributed Base Stations.
- If the mode of the original RXU is to expanded to multiple modes, no additional RXU
is required.
- A new RF module is added to serve multiple modes.
Type Name
Auxiliary CPRI Same as the number of RRUs or Two ends of the

materials electrical RFUs. Each RFU requires one CPRI CPRI electrical cable
RFU and BBU,
respectively.
to the RRU and
BBU, respectively.

CPRI MUX in separate-MPT scenarios: SRAN7.1
None
- CPRI MUX in separate-MPT scenarios: Both the converging and converged parties
must be configured.
Converging party: A link needs to be configured as regular.

Copyright © Huawei
Converged party: Configure a link by setting parameters listed in the following table.
Access Type must be set to PEERPORT(peer port) and the correlation between the
local and peer ends must be specified. The following table provides the example.
Parameter Name Parameter ID Setting Notes Data Source
Access Type AT Set this parameter to Engineering design

PEERPORT(peer
port).
Head Cabinet No. HCN Set these parameters Engineering design
to the cabinet
Head Subrack No. HSRN number, subrack Engineering design
number, slot
Head Slot No. HSN Engineering design
number, and optical
Head Port No. HPN port number of the Engineering design
CPRI port on the
baseband processing
board of the peer
end, respectively.
Local Slot No. LSN  For BBU3910s Equipment plan
used in separate-
MPT GU or GL
CPRI MUX and
BBU3900s, the
slot number does
not need to be
configured for
the converged
party. In this
case, set this
parameter to 255.
 For BBU3910s
used in separate-
MPT scenarios
with UL CPRI
MUX, set this
parameter to the
slot number of
board used by
the converged
party.
- CPRI MUX in co-MPT scenarios: A link is normally configured. The system

automatically assigns the converging and converged parties based on service
configurations.
For details, see CPRI MUX Feature Parameter Description for SRAN12.0.
 Service impact
Original mode as the Services of the original mode are not affected.
converging party and no

Copyright © Huawei
modification to the slot of the

original baseband processing
board
Original mode as the Services carried by the baseband processing board of the
converging party and adjusting original mode are affected. In addition, services are
the slot or the original affected during the period from the adjustment of
baseband processing board baseband board slot to the configuration completion of
the original mode's data.
New mode as the converging Connect the original CPRI cable to an RF module of the
party new mode. Data of the original data needs to be modified.
Services are interrupted during the period from the CPRI
cable adjustment to the configuration completion of the
original mode's data.
3.9 Transmission Networking Planning

This section describes transmission networking planning.

Copyright © Huawei
3.9.1 Transmission Networking Planning Process

Figure 1.20 Overall transmission networking planning process
Check whether independent transmission or co-transmission shall be used. The following

table provides the comparison between independent transmission and co-transmission.
Comparison Independent Transmission Co-transmission

Item
Port requirement An independent transmission port Multiple modes share a

for transmission must be configured for each transmission port.
devices mode.
IP addresses For each mode, the port IP For each mode, the port IP address,
requirement address, O&M IP address, service O&M IP address, service IP
(minimum) IP address, and signaling IP address, and signaling IP address
address must be planned. must be planned.
The service IP address is the same The service IP address is the same
as the signaling IP address, and as the signaling IP address, and
can be the same as or different can be the same as or different
from the O&M IP address. from the O&M IP address.
The service IP address or The service IP address or signaling
signaling IP address can be the IP address can be the same as the
same as the port IP address. port IP address.
The O&M IP address can be the The O&M IP address can be the
same as the port IP address.

Copyright © Huawei
Comparison Independent Transmission Co-transmission

Item
same as the port IP address.

For panel co-transmission, an IP
address must be configured for the
co-transmission port.
For backplane co-transmission, no
port IP address needs to be planned
for the mode that does not provide
a transmission port.
Transmission No sharing Sharing
bandwidth
sharing
Co-IPsec/PKI No sharing Sharing is supported.
Reliability All the modes are independent A reset or fault on the main control
from each other. board that provides a transmission
port for co-transmission affects
other modes.
The mode that provides a
transmission port for co-
transmission must be deployed
first.
Check whether the original mode provides the transmission port.

It is recommended that the transmission port be configured on the board or mode that has the
strongest transmission capability when co-transmission is used.
However, if co-transmission is implemented through UMPT+UMPT, the transmission port
shall be provided by the primary BBU subrack. Therefore, in such a case, if the new mode is
configured in the secondary BBU subrack and has a stronger transmission capability, the
primary BBU subrack provides the transmission port for co-transmission.
If the interface capabilities of the original and new modes are similar, the transmission port of
the original mode is preferred. This can avoid service interruption caused by transmission
adjustment in the original mode.

or Co-MPT
Transmissio Separate-MPT 3.9.2New Mode Using Independent Transmission with

n Separate-MPT Configuration
3.9.3New Mode Using the Transmission Port Provided
by the Original Mode with Separate-MPT Configuration
3.9.4New Mode Providing a Transmission Port Shared
by the Original Mode with Separate-MPT Configuration

Copyright © Huawei

or Co-MPT
Co-MPT mode 3.9.5Co-Transmission for New and Original Modes with

expansion co-MPT Configuration
3.9.2 New Mode Using Independent Transmission with Separate-

MPT Configuration
In separate-MPT mode transition scenarios, the new mode provides a transmission port for
co-transmission, as shown in the following figure.
Transmission networking selection:

The transmission networking of the new mode is determined by the transmission type
supported by the new mode and actual site transmission condition. For example, if an eNodeB
supports Ethernet transmission and both Ethernet transmission and E1 transmission exist at
the site, Ethernet transmission must be configured for the eNodeB. If the site does not support
the transmission type supported by the new mode, transmission reconstruction must be
performed at the site.
2. Precautions
None
Material requirements are determined by the transmission type of the new mode. For
details, see description about deployment of a base station of the new mode.
Type Name
Transmissio E1/T1 One, including four E1/T1 channels.

n electrical
cable
FE/GE One
electrical
cable
FE/GE fiber One

Copyright © Huawei

Type Name
optic cable
FE/GE One
optical
module

None
Purchase the related license if the transmission type used by the new mode has license
requirements.
The following table provides the related MOCs.
Domain Configuration MOC Parameter Name CME

Object Type
Transmission New-mode main E1T1 For details, see Transmis

control board section sion
"Configuring
New-mode main ETHPORT Transport Data" in Transmis
control board 3900 Series Base sion
Station Initial
New-mode main PPPLNK Transmis
Configuration
control board sion
Guide.
New-mode main MPGRP Transmis
control board sion
New-mode main MPLNK Transmis
control board sion
New-mode main DEVIP Transmis
control board sion
New-mode main IPRT Transmis
control board sion
New-mode main OMCH Transmis
control board sion
New-mode main SCTPLNK Transmis
control board sion
New-mode main IPPATH Transmis
control board sion
New-mode main EPGROUP Transmis
control board sion

Copyright © Huawei

Object Type
New-mode main USERPLANEHO Transmis

control board ST sion
New-mode main USERPLANEPE Transmis
control board ER sion
New-mode main SCTPHOST Transmis
control board sion
New-mode main SCTPPEER Transmis
control board sion
Original mode: No change is required.

New mode: Configure the port IP address, O&M IP address, service link, signaling link, and
route in the same way as that for deploying a new base station.
For details, see section "Configuring Transport Data" in 3900 Series Base Station Initial
Configuration Guide for SRAN12.0.
 Service impact
Services of the original mode are not affected. The new mode can provide services after
it is configured, transmission links are connected, and the base station is reset.
3.9.3 New Mode Using the Transmission Port Provided by the

Original Mode with Separate-MPT Configuration
In mode transmission of a separate-mode base station, the new mode and original mode share
a transmission port provided by the original mode. Backplane co-transmission is
recommended, as shown in the following figure.
Transmission networking selection: No change is required because the transmission for the
original mode remains unchanged.
2. Precautions
Backplane co-transmission is recommended because this requires no additional IP address or
panel interconnection cable.

Copyright © Huawei
No additional material is required.
Backplane co-transmission: SRAN7.0 and later
Related co-transmission licenses must be purchased.
Domai Module License Control Item License Sales Mode
n Type Name (SBOM) SBOM Unit
Transmi Co- IP-Based Multi-mode Co- 88030QUG Per BTS G

ssion transmissi Transmission on BS
on side(GBTS)
Transmi Co- IP-Based Multi-mode Co- 88030QUR Per U
ssion transmissi Transmission on BS NodeB
on side(NodeB)
Transmi Co- IP-Based Multi-mode Co- 88030QUV Per L
ssion transmissi Transmission on BS eNodeB
on side(eNodeB)
Transmi Co- IP-Based Multi-mode Co- 88031VYR Per L
ssion transmissi Transmission on BS side(per eNodeB
on eNodeB)
Transmi Co- IP-Based Multi-mode Co- 88033VPB Per L
ssion transmissi Transmission on BS side(NB- eNodeB
on IoT)


Object Type
Transmission New-mode main TUNNEL For details, see Transmis

"Configuring
New-mode main DEVIP Transport Data" in Transmis
Station Initial
Configuration
control board sion
Guide for
New-mode main OMCH SRAN12.0. Transmis
control board sion
control board sion
control board sion

Copyright © Huawei

Object Type
control board sion

control board sion
control board sion
Original mode TUNNEL Transmis
providing a sion
transmission port
Original mode IPRT Transmis
providing a sion
transmission port
Original mode DHCPRELAYS Transmis
providing a WITCH sion
transmission port
Original mode DHCPSVRIP Transmis
providing a sion
transmission port
Original mode:
The following items must be configured in the original mode:
- Backplane tunnel: The source slot number is set to the slot number of the board in the
original mode and the destination slot number is set to the slot number of the board in the new
mode.
- DHCP relay switch DHCPRELAYSWITCH and DHCP server IP address DHCPSVRIP
- uplink and downlink IP routes to the new mode
For details, see Common Transmission Feature Parameter Description for SRAN12.0.
New mode:
- Backplane tunnel: The source slot number is set to the slot number of the board in the new
mode and the destination slot number is set to the slot number of the board in the original
mode.
- Configure the O&M IP address, service links, signaling links, and routes for the new mode.
 Service impact

Copyright © Huawei
Services of the original mode are not affected. The new mode can provide services once
it is started after the configuration and power-on.
3.9.4 New Mode Providing a Transmission Port Shared by the

Original Mode with Separate-MPT Configuration
In mode transition of a separate-mode base station, the new mode provides a transmission port
connecting to the transmission network and the original mode shares the transmission port, as
shown in the following figure.
Transmission networking selection

None
2. Precautions
None
No additional material is required for backplane co-transmission.
Backplane co-transmission: SRAN7.0 and later

on side(GBTS)
on side(NodeB)
on side(eNodeB)

Copyright © Huawei

on eNodeB)
on IoT)


Object Type
Transmission New-mode main E1T1 For details, see Transmis

"Configuring
New-mode main ETHPORT Transport Data" in Transmis
Station Initial
New-mode main PPPLNK Transmis
Configuration
control board sion
Guide.
New-mode main MPGRP Transmis
control board sion
New-mode main MPLNK Transmis
control board sion
New-mode main TUNNEL Transmis
control board sion
New-mode main DEVIP Transmis
control board sion
control board sion
New-mode main OMCH Transmis
control board sion
control board sion
control board sion
control board sion

Copyright © Huawei

Object Type

control board sion
control board sion
New-mode main DHCPRELAYS Transmis
control board WITCH sion
New-mode main DHCPSVRIP Transmis
control board sion
Original-mode TUNNEL Transmis
main control board sion
Original-mode DEVIP Transmis
Original-mode IPRT Transmis
Original mode:
- Configure a backplane tunnel.
- Add a device IP address.
- Adjust the IP route.
For details, see Common Transmission Feature Parameter Description for SRAN12.0.
New mode:
- Configure the DHCP relay switch DHCPRELAYSWITCH and DHCP server IP address
DHCPSVRIP for the original mode.
- Configure a backplane tunnel.
- Configure an IP route for the original mode.
- Configure the O&M IP address, service links, signaling links, and routes for the new mode.
 Service impact
Services of the original mode are interrupted during the period from transmission cable
adjustment to new site deployment and activation of the original mode's data.
3.9.5 Co-Transmission for New and Original Modes with co-MPT

Configuration

Copyright © Huawei
A new mode is added to the co-MPT base station and co-transmission is used for the new and
original modes, as shown in the following figure
Transmission networking selection

No change is required because the new and original modes use co-transmission networking.
2. Precautions
None
No new material is required.
SRAN8.0 and later versions

on side(GBTS)
on side(NodeB)
on side(eNodeB)
on eNodeB)
on IoT)


Copyright © Huawei

Object Type
Transmission Node DEVIP For details, see Transmis

section sion
"Configuring
Node SCTPLNK Transport Data" in Transmis
3900 Series Base sion
Station Initial
Node IPPATH Transmis
Configuration
sion
Guide.
Node EPGROUP Transmis
sion
Node USERPLANEHO Transmis
ST sion
Node USERPLANEPE Transmis
ER sion
Node SCTPHOST Transmis
sion
Node SCTPPEER Transmis
sion
Node CPBEARER Transmis
sion
New RAT ABIS Transmis
sion
New RAT GBTSABISCP Transmis
sion
New RAT IUB Transmis
sion
New RAT IUBCP Transmis
sion
New RAT S1 Transmis
sion
New RAT S1INTERFACE Transmis
sion
New RAT X2 Transmis
sion
New RAT X2INTERFACE Transmis
sion
Original mode:
Data of the original mode does not need any modification.
Node-related data needs to the changed as follows:

Copyright © Huawei
- A port IP address DEVIP must be configured for the new mode. Note that this parameter is
required only when the port IP address is required for the new mode. If no new port IP address
is required, the new mode and original mode share the same port IP address.
- The service link, signaling link, and route of the new mode must be configured.
New mode:
For new mode GU:
- CPBEARER referenced by NODE must be configured on the signaling plane of the new
mode.
- IPPATH or EPGROUP referenced by NODE must be configured on the user plane of the
new mode.
For new mode L:
- CPBEARER or EPGROUP referenced by NODE must be configured on the signaling
plane of the new mode.
- IPPATH or EPGROUP referenced by NODE must be configured on the user plane of the
new mode.
 Service impact
Services of the original mode are not affected. The new mode can provide services once
the configuration is completed.
3.10 Equipment Auxiliary Planning

1. Focus for equipment auxiliary planning
Equipment auxiliary planning covers installation, power supply, and heat dissipation for the
BBU and RF module of the new mode. The original BBU can be reconstructed or a new BBU
can be added to support the new mode. The following table provides the details.
Table 20.2 Focus for equipment auxiliary planning

Equip Scenario Functi Focus
ment on
BBU Adding a Installa A BBU has been installed and installation is not needed.
new mode tion
to the
original Power Use the NEP-SD tool or PCT tool to determine whether
BBU supply UPEU capacity expansion is required. If the UPEU
capacity expansion is required, DC power supply needs
to be provided to the new UPEU.
Note:
1. UPEUs of different types cannot be used together.
2. For the power supply capability of one UPEU or two
UPEUs, see BBU Hardware Description > BBU3900
and BBU3910 Hardware Description > BBU3900 and

Copyright © Huawei

ment on
BBU3910 Boards > UPEU in 3900 Series Base Station

Product Documentation.
Heat In the high temperature areas, if an UPEU is added to the
dissipa BBU3900 of an outdoor DC cabinet, a high-speed FANc
tion must be added.
Note:
High temperature areas: areas where the number of days
during which the highest temperature exceeds 45°C is
greater than 10 days in a year
Adding a Installa If the new and original BBUs are installed in the same
new BBU tion cabinet, check whether the cabinet supports two BBUs. If
for mode the new BBU is installed in another cabinet, check the
transition power supply and heat dissipation capabilities of the new
cabinet.
Note:
For the number of BBUs that can be installed in a
cabinet, see the section describing BBU/cabinet
specifications.
Power Circuit breaker ports must be available on the DCDU to
supply provide power supply for the new BBU.
Heat Check the heat dissipation capabilities of the cabinet.
dissipa Note:
tion
For the heat dissipation capability, see the section
describing BBU/cabinet specifications.
RF SDR RF Installa N/A
module module tion
without
new RF Power N/A
module supply
Heat N/A
dissipa
tion
Adding an Installa 1. Check whether the original cabinet supports the new
RFU tion RF module (some Ver.A or Ver.B cabinets do not
support high-power RF modules). If the original cabinet
does not support the new RF module, a new cabinet shall
be added. Alternatively, you can upgrade or reconstruct
the original cabinet.
2. Check whether the original cabinet has sufficient
space. If no sufficient space is available, add a new
cabinet for the new RF module, such as a BTS3900,
BTS3900L, RFC, or BTS3910AL. When adding a new
cabinet, pay attention to the footprint for installing the
cabinet.

Copyright © Huawei

ment on
Note:
For the mapping between the RFUs and cabinets, see
Hardware Description > RFU Hardware Description
> Applicable Cabinets for RFUs.
For cabinet reconstruction, see "Installation guide for
enhancing existing cabinets" in this topic.
Power 1. RFU power supply:
supply If the original cabinet is used, check whether the DCDU
of the original cabinet can provide sufficient DC power
supply. If more DC power supply is required, use circuit
breakers with larger capacity or add an input to the
circuit breaker.
If a new cabinet is used, check whether the AC power
system provides DC power to the DCDU of the new
cabinet (pay attention to the cable and circuit breaker).
2. Check whether the AC power system can provide
sufficient power supply. If more power supply is
required, add a PSU or a power supply cabinet. When
adding a new power cabinet, pay attention to the
footprint for installing the cabinet.
Note:
For details about how to calculate the required cables,
cable diameter, and circuit breaker, see "Cable diameter
or circuit breaker calculation."
Heat If a new RFU can be installed in the cabinet, the RFU
dissipa heat dissipation requirement can be met.
tion
Adding an Installa Determine where the RRU is to be installed. The RRU
RRU tion can be installed on a pole, wall, or L-type stand. If the
RRU is installed on a pole or wall, pay attention to the
installation position and bearing capacity. If the RRU is
installed on the L-type stand, pay attention to the
installation position of the L-type stand.
Power 1. RRU power supply:
supply RRU power cable: Check the diameter and length of the
RRU power cable based on the RRU type and distance
between the RRU and BBU.
DC power supply for the RRU: Check whether a new
DCDU is required and whether the new DCDU's circuit
breaker meets the related requirements. In addition, if the
DC power supply cable is routed from the cabinet, check
the cabinet cabling capability.
2. AC power supply: Check whether the AC power
system can provide sufficient power supply. If more
power supply is required, add a PSU or a power supply
cabinet. In addition, check whether the power system

Copyright © Huawei

ment on
provides sufficient output circuit breakers.

Note:
1. For details about how to calculate the required cables,
cable diameter, and circuit breaker, see "Cable diameter
or circuit breaker calculation."
2. You can determine the number of cables that can be
provided by a cabinet based on the number of RRUs or
RFUs supported by the cabinet. For details, see
specifications in "BBU and cabinet specifications."
3. For the mapping between RRUs and a cabinet, see the
number of RRUs and power specifications supported by
the cabinet in "BBU and cabinet specifications."
Heat N/A
dissipa
tion
Transm Original Installa N/A
ission transmissi tion
equipm on
ent equipment Power N/A
supply
Heat N/A
dissipa
tion
Adding a Installa Check whether the cabinet has enough room for the new
new tion transmission equipment.
transmissi
on Power Check whether power circuit breakers must be provided
equipment supply for the transmission equipment.
/Replacing
Heat The power consumption of the transmission equipment
the
dissipa and the total power consumption of other equipment
original
tion must meet the heat dissipation capabilities of the cabinet.
transmissi
on
equipment
Others Air Heat If a device is added to an indoor site, check the heat
conditione dissipa dissipation capability of the equipment room.
r in the tion
equipment
room
Equipment Installa Pay attention to the feeder window, ground bar, and
room tion cable tray in the equipment room during the site survey.

Copyright © Huawei
If circuit breaker capacity does not satisfy the specifications, you can calculate the circuit breaker
capacity based on the actual base station configuration using NEP-SD V100R008C00 or later versions.
To obtain the NEP-SD and related documents, visit the following website:
http://support.huawei.com/carrier/navi#allProduct=true&col=product&path=PBI1-7851894/PBI1-
7854702/PBI1-7275896/PBI1-21744982/PBI1-19889332
2. Power consumption of the BBU or cabinet

Use the PCT tool for calculation.
3. BBU and cabinet specifications
For details about BBU and cabinet specifications, see SingleRAN Multi-mode BTS Product
Specification.
4. Cabinet selection
For details about how to select a cabinet, see GUL Base Station Overview and Selection
Guide.
5. Cable diameter or circuit breaker calculation
For details, see Engineering Interface Parameter Design Guide for Wireless BTSs.
6. Installation guide for enhancing existing cabinets
The cabinet upgrading and reconstruction guides include the following documents:
BTS3900 Installation Guide for Enhancing Existing Cabinets, BTS3900A Installation Guide
for Enhancing Existing Cabinets, BTS3900L Installation Guide for Enhancing Existing
Cabinets, and DBS3900 Installation Guide for Enhancing Existing Cabinets for SRAN12.0
Check whether a new material is required based on the planning descriptions in this
section.
None
None
Pay attention to configuration of the cabinet and monitoring parts in the cabinet.
For SRAN12.0, see Base Station Cabinets and Subracks (Including the BBU Subrack)
Configuration Feature Parameter Description and Monitoring Management Feature
Table 20.3 Key parameters related to the FMU

ation Name r ID
Object
Equipme Adding an FMU Manager Cabinet MCN 0

nt FMU No.
Adding an FMU Manager Subrack MSRN 0

Copyright © Huawei

ation Name r ID
Object
FMU No.
Adding an FMU Serial Number MPN 0
FMU
Adding an FMU Address ADDR 14
FMU
Adding an FMU Smart STC ENABLE(Enable
FMU Temperature )
Control
Table 20.4 Key parameters related to the TCU

ation Name r ID
Object
Equipme Adding a TCU Manager Cabinet MCN 0

nt TCU No.
Adding a TCU Manager MSRN 0
TCU Subrack No.
Adding a TCU Serial Number MPN 0
TCU
Adding a TCU Address ADDR 7
TCU
Table 20.5 Key parameters related to the EMU

ation Name r ID
Object
Equipme Adding an EMU Manager Cabinet MCN 0

nt EMU No.
Adding an EMU Manager MSRN 0
EMU Subrack No.
Adding an EMU Serial Number MPN 0
EMU
Adding an EMU Address ADDR 2
EMU

Copyright © Huawei
Table 20.6 Key parameters related to the PMU

ation Name r ID
Object
Equipme Adding a PMU Manager Cabinet MCN 0

nt PMU No.
Adding a PMU Manager MSRN 0
PMU Subrack No.
Adding a PMU Serial Number MPN 0
PMU
Adding a PMU Address ADDR 3
PMU
Table 20.7 Key parameters related to the battery

ation Name r ID
Object
Equipme Adding a BATTER Battery Type BTYPE VRLA_BAT(VR

nt PMU Y LA Battery)
Adding a BATTER Battery 1 BC1 30
PMU Y Capacity
Table 20.8 Key parameters related to the CCU

ation Name r ID
Object
Equipme Adding a CCU Manager Cabinet MCN 0

nt CCU No.
Adding a CCU Manager MSRN 0
CCU Subrack No.
Adding a CCU Serial Number MPN 0
CCU
Adding a CCU DirectConnectFl DCF YES (Yes)
CCU ag
Adding a CCU Cascade No. CCN 1
CCU
Adding a CCU Connected RAT CS GSM
CCU

Copyright © Huawei
 Service impact

Adjusting the power system Services of the entire site are interrupted.
Installing a new cabinet Services of the original mode are not affected.
Expanding the capacity by Services of the original mode are not affected.
adding a new module in the
original cabinet
Reconstructing the original Services of the original mode are interrupted during the
cabinet reconstruction.
3.11 Summary of Mode Transition Planning

3.11.1 License File Requirement
When adding a new mode, new RF modules, main control boards, or baseband processing
boards must be added, which requires the related single-mode licenses, for example, power or
TRX licenses. The way of purchasing such a license is the same as that for single-mode
equipment, and therefore, details are not described here.
This section uses multimode transition as an example to describe the license requirements.
Table 20.10 Summary of multimode BBOM license allocation

Dom Mod License License License License Sales Mode
ain ule Control Control BBOM Abbrevia Unit
Type Item Item tion
Name Name
(SBOM) (BBOM)
RF Multi- First Mode Multi- 82205398 LQW9RF Per U

band First Band Mode BAND01 band
RF License for Multi-
modul Multi-Band Band
es RF Module License for
except (UMTS) Multi-
for Band RF
the Module
RRU3 (UMTS)
961. (Per Band
per RRU)
RF Multi- Multi- 82205398 LQW9RF Per U
Mode Mode BAND01 band
Multi-Band Multi-

Copyright © Huawei

Type Item Item tion
Name Name
(SBOM) (BBOM)
License for Band

Multi-Band License for
RF Module Multi-
(UMTS) Band RF
Module
(UMTS)
(Per Band
per RRU)
RF First Mode Multi- 82205382 LLT1MM Per L
First Band Mode LMBRM0 band
License for Multi- 1
Multi-Band Band
RF Module License for
(LTE FDD) Multi-
Band RF
Module
(LTE
FDD) (Per
Band per
RRU)
RF Multi- Multi- 82205382 LLT1MM Per L
Mode Mode LMBRM0 band
Multi-Band Multi- 1
License for Band
Multi-Band License for
RF Module Multi-
(LTE FDD) Band RF
Module
(LTE
FDD) (Per
Band per
RRU)
RF RF Multi- RF Multi- 82207096 LML1RF Per L
Mode Mode ML01 sector
license license
(NB-IoT) (per
Sector)
(NB-IoT)
RF Must RF RF 82204034 LLT1RFM Per L
be 800M/900 800M/900 B01 band
purch M Multi M Multi per
ased Band Band RRU
for license license
the
RRU3
961 if

Copyright © Huawei

Type Item Item tion
Name Name
(SBOM) (BBOM)
both
the
800
MHz
and
900
MHz
freque
ncy
bands
are
used.
RF Non- GSM/UMT The 82201199 LQW9MB Per U
GU blade S Dual number of TSRF02 sector
modul Mode RF Units
e license with
GSM/UM
TS dual
mode
function
enabled
Blade GSM/UMT The 82201199 LQW9MB Per U
&AA S Dual number of TSRF02 sector
U Mode RF Units
license for with
Blade&AA GSM/UM
U TS dual
mode
function
enabled
RF Non- GSM/LTE GSM/LTE 82201472 LLT1GLD Per L
GL blade Dual Mode Dual Mode M01 sector
modul license license(per
e Sector)
Blade GSM/LTE GSM/LTE 82201472 LLT1GLD Per L
&AA Dual Mode Dual Mode M01 sector
U license for license(per
Blade&AA Sector)
U
RF Non- UMTS/LT UMTS/LT 82201473 LLT1ULD Per L
UL blade E Dual E Dual M01 sector
modul Mode Mode
e license license(per
Sector)
Blade UMTS/LT UMTS/LT 82201473 LLT1ULD Per L

Copyright © Huawei

Type Item Item tion
Name Name
(SBOM) (BBOM)
&AA E Dual E Dual M01 sector

U Mode Mode
license for license(per
Blade&AA Sector)
U
RF Non- RF NA NA NA Per U+L
GUL blade GSM/UMT sector
modul S Dual
e Mode
license +
RF
GSM/LTE
Dual Mode
license
or
RF
GSM/UMT
S Dual
Mode
license +
RF
UMTS/LT
E Dual
Mode
license
Blade GSM/UMT N/A NA NA Per U+L
&AA S Dual sector
U Mode
license for
Blade&AA
U+
GSM/LTE
Dual Mode
license for
Blade&AA
U
or
GSM/UMT
S Dual
Mode
license for
Blade&AA
U+
UMTS/LT
E Dual
Mode

Copyright © Huawei

Type Item Item tion
Name Name
(SBOM) (BBOM)
license for
Blade&AA
U
NB- NA NA NA NA NA NA NA
IoT
only
X+N Non- RF Multi- RF Multi- 82207096 LML1RF Per L
B-IoT blade Mode Mode ML01 sector
(X modul license license
indica e (NB-IoT) (per
tes Sector)
GSM, (NB-IoT)
UMT
S, or
LTE.)
Blade RF Multi- RF Multi- 82207096 LML1RF Per L
&AA Mode Mode ML01 sector
U license for license
the blade (per
RRU and Sector)
AAU (NB- (NB-IoT)
IoT)
X+X+ Non- RF Multi- NA NA NA NA NA
NB- blade Mode
IoT modul license
(X e (NB-IoT) +
indica (X+X)
tes Multi-
GU, Mode
GL, Sector
or license
UL.) (stated
above)
Blade RF Multi- NA NA NA NA NA
&AA Mode
U license for
the blade
RRU and
AAU (NB-
IoT) +
(X+X)
Multi-
Mode
Sector
license

Copyright © Huawei

Type Item Item tion
Name Name
(SBOM) (BBOM)
MPT Multi UMPT UMPT 82204202 LGB3UM Per G

mode Multi Mode Multi ML01 UMPT
co- License(GS Mode
MPT M) License
(GSM)
(per
UMPT)
MPT Multi UMPT UMPT 82203981 LQW9GU Per U
mode Multi Mode Multi DM01 UMPT
co- License(U Mode
MPT MTS) License
(UMTS)
(per
UMPT)
MPT Multi UMPT UMPT 82204259 LLT1UM Per L
mode Multi- Multi ML01 UMPT
co- Mode Mode
MPT license License
(LTE FDD) (per
UMPT)
(FDD)
MPT Multi UMPT UMPT 82204285 LLT1TUM Per L
co- License Mode
MPT (per License
UMPT) (per
(TDD) UMPT)
(TDD)
MPT Multi UMPT UMPT 82207098 LML1UM Per LTE
co- License Mode
MPT (per License
UMPT) (per
(NB-IoT) UMPT)
(NB-IoT)
Clock Clock Multi-mode Function- 81201529 LLT1MCR Per L
sharin BS LTE- C01 eNode
g Common LLT1MCR B
Reference C01-Multi-
Clock(eNo mode BS
deB) Common
Reference
Clock(eNo
deB)(Per
eNodeB)

Copyright © Huawei

Type Item Item tion
Name Name
(SBOM) (BBOM)
Baseb Co- UBBP UBBP 82204551 LGMIUB Per G

and baseb First-Mode Multi- BP UBBP
and license Mode
(GSM) license
(GSM)
(Per
Module)
Baseb Co- UBBP UBBP 82204551 LGMIUB Per G
and baseb Multi- Multi- BP UBBP
and Mode Mode
license license
(GSM) (GSM)
(Per
Module)
Baseb Co- UBBP UBBP 82204657 LQW9UB Per U
and baseb First-Mode Multi- PDM01 UBBP
and license Mode
(UMTS) license
(UMTS)
Baseb Co- UBBP UBBP 82204657 LQW9UB Per U
and baseb Multi- Multi- PDM01 UBBP
and Mode Mode
license license
(UMTS) (UMTS)
Baseb Co- UBBP UBBP 82205382 LLT1MM Per L
and baseb First-Mode Multi- LMBRM0 UBBP
and license Mode 1
(LTE FDD) license
(FDD)
Baseb Co- UBBP UBBP 82205382 LLT1MM Per L
and baseb Multi- Multi- LMBRM0 UBBP
and Mode Mode 1
license license
(FDD) (FDD)
Baseb Co- UBBP UBBP 82204849 LLT1TUB Per L
and baseb First-Mode Multi- MML01 UBBP
and license Mode
(LTE TDD) license
(TDD)
Baseb Co- UBBP UBBP 82204849 LLT1TUB Per L
and baseb Multi- Multi- MML01 UBBP
and Mode Mode
license license
(TDD) (TDD)

Copyright © Huawei

Type Item Item tion
Name Name
(SBOM) (BBOM)
Baseb Co- UBBP UBBP 82207099 LML1UB Per L

and baseb First-Mode Multi- MML01 UBBP
and license Mode
(NB-IoT) license
(NB-IoT)
Baseb Co- UBBP UBBP 82207099 LML1UB Per L
and baseb Multi- Multi- MML01 UBBP
and Mode Mode
license license
(NB-IoT) (NB-IoT)
Trans Co- IP-Based IP-Based 81201528 LLT1IPM Per L
missi trans Multi-mode Multi- CT01 eNode
on missi Co- mode Co- B
on Transmissi Transmissi
on on BS on on BS
side(eNode side(FDD)
B)
Trans Co- IP-Based IP-Based 81202015 LLT1TIP Per L
missi trans Multi-mode Multi- MCT01 eNode
on on BS on on BS
side(eNode side(TDD)
B)
Trans Co- IP-Based IP-Based 81202564 LML1IPM Per L
missi trans Multi-mode Multi- CT01 eNode
on on BS on on BS
side(NB- side(NB-
IoT) IoT)
Table 20.11 Multimode SBOM licenses

Clock Clock Multi-mode BS Common 88030QUK Per BTS G

sharing Reference Clock(GBTS)
Clock Clock Multi-mode BS Common 88030QUU Per U
sharing Reference Clock(NodeB) NodeB
Clock Clock Multi-mode BS Common 88030QUW Per L

Copyright © Huawei

sharing Reference Clock(eNodeB) eNodeB

Clock Clock Multi-mode BS Common 88031VYT Per L
sharing Reference Clock (per eNodeB
eNodeB)
Clock Clock Multi-mode BS Common 88033VPE Per L
sharing Reference Clock(NB-IoT) eNodeB
on side(GBTS)
on side(NodeB)
on side(eNodeB)
on eNodeB)
on IoT)
 The license must be adjusted when a dependent GSM NE is to be reconstructed into an

independent GSM NE.
In GBSS15.0, the license control item changed significantly. The most significant change is
that the BTS quotation feature is controlled by the eGBTS. Before a feature is activated/used,
the GTS needs to allocate sufficient licenses to each eGBTS on the U2000. Otherwise, the
feature fails to be activated and CS/PS services may be affected. The following table
describes how to allocate the licenses of features supported by the eGBTS.
1. Features contained in the eGBTS license but not supported by the eGBTS
Not Not Instruction
- High Power Per TRX Yes No Set the

(per TRX) number of
licenses to
be allocated
to 0.
- TRU which Per TRX Yes No Set the
works as number of
Multi licenses to

Copyright © Huawei

Not Not Instruction
transceivers be allocated
Resource of to 0.
3rd
generation
BTS (per
TRX)
- BBU Carrier per TRX Yes No Set the
Capacity number of
License (per licenses to
TRX) be allocated
to 0.
GBFD- PBT(Power Per TRX Yes No Set the
115901 Boost number of
Technology) licenses to
to 0.
GBFD- Transmit Per TRX Yes No Set the
115902 Diversity number of
(per TRX) licenses to
be allocated
to 0.
- BTS3900B Per TRX Yes No Set the
Transceiver number of
Resource licenses to
to 0.
2. Features supported by GBSSR15.0

Item the eGBTS or
GBTS or Not
Not
- Multi Per TRX Yes Yes The number of licenses to

Power Power Type(w)
(per ranging from 60 W to 80
TRX) W.
Related BSC MML
command: LST

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not
GTRXDEV
- Multi Per TRX Yes Yes The number of licenses to
Power Power Type(w)
(per greater than or equal to 80
TRX) W.
Related BSC MML
command: LST
GTRXDEV
- TRU Per TRX Yes Yes Non-multi-site cell
which scenarios:
works as Number of licenses to be
Multi allocated = Number of
transceive activated logical TRXs
rs under an eGBTS –
Resource Number of TRX modules
of 3900 that support GSM
(per
TRX) Multi-site cell scenarios
(supported by
GBSSR16.0 and later):
be allocated for sites
outside China and China
Unicom = Number of
subsites under eGBTS x
Number of logical TRXs
under a subsite – Number
of TRX modules under all
subsites
be allocated for China
Mobile = Number of
activated logical TRXs
under an eGBTS –
Number of TRX modules
of the subsite with the
maximum number of
TRX modules
Related BSC MML
commands:
LST GTRX
LST BTSLOCGRPE

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not
Related BTS MML

commands:
LST
GTRXGROUPSECTORE
QM
LST SECTOREQM
MRFD Multi- Per Site Yes Yes If the Power Sharing
- mode Type parameter (eGBTS)
Power GUPWRSHR(GU power
command:
LST
GBTSPWRSHRGRP;
MRFD 2.0MHz Per Site Yes Yes The feature is controlled
- Central by a false control item.
211703 Frequenc Contact the frontline
y point marketing personnel when
separatio manually allocating a
n license to a customer's
between base station.
GSM and
UMTS
mode(GS
M) (per
Site)
MRFD GSM per BTS Yes Yes If the Frequency-based
- Power Power Control parameter
211804 Control of one or more local cells
on under eGBTS is set to
Interferen ON(On), a license needs
ce to be allocated to the
Frequenc eGBTS.
y for GU Related eGBTS MML
Small command:
Frequenc
y gap LST
(GSM) GLOCELLALGPARA
MRFD Bandwidt Per Site Yes Yes The feature is controlled

- h sharing by a false control item.
211505 of MBTS Contact the frontline
Multi- marketing personnel when
mode Co- manually allocating a

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not
Transmis license to a customer's

sion(GBT base station.
S)
MRFD Multi- per BTS Yes Yes The feature is controlled
- mode BS by a false control item.
211602 Common Contact the frontline
IPSec(GS marketing personnel when
M) (per manually allocating a
Site) license to a customer's
base station.
MRFD GSM and per BTS Yes Yes If the Spectrum Sharing
- UMTS Allowed parameter is set
211802 Dynamic to YES(Yes), a license
Spectrum needs to be allocated to
Sharing the eGBTS.
(GSM) Related BSC MML
command:
LST GDSSPARA
MRFD Dynamic per BTS Yes Yes If the FH Index Used
- MA for After Frequency
211803 GU Spectrum Sharing
Dynamic parameter of one or more
Spectrum channels under the
Sharing eGBTS is set to a value
(GSM) ranging from 0 to 63, a
license needs to be
allocated to the eGBTS.
Related BSC MML
command:
LST GTRXCHANHOP;
MRFD GSM and Per BTS Yes Yes If the Power Sharing
- LTE Type parameter (eGBTS)
Power GLPWRSHR(GL power
command:
LST
GBTSPWRSHRGRP;
MRFD Multi- Per BTS Yes Yes If the Inter-RAT Cell
- RAT Dynamic Shutdown
211901 Carrier parameter of one or more

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not
Joint logical cells under the

Shutdown eGBTS is set to ON(On),
(GBTS) a license needs to be
(per Site) allocated to the eGBTS.
Related BSC MML
command:
LST GCELLSOFT
GBFD IPSec Per BTS No Yes If the IPSec Bypass
- bypass Switch of the eGBTS is
116602 (per base turned on, a license needs
station) to be allocated to the
eGBTS.
Related eGBTS MML
command:
LST IPSECBYPASSCFG
- UMPT Per UMPT No Yes 1. No license is allocated
Multi to a new eGBTS that
Mode works in GSM only mode.
License 2. No license needs to be
(GSM) purchased and allocated to
(per a GU/GL/GUL co-MPT
UMPT) base station.
3. For a new co-MPT base
station that does not
support GSM, a license
needs to be purchased and
allocated to the base
station if mode transition
is performed, such as
mode transition from UL
to GUL.
- Antenna Per TRX Yes Yes License verification is
Intermod triggered by the related
ulation eGBTS maintenance
Performa commands. The number
nce of licenses that need to be
Detection allocated equals the
(per number of activated
TRX) logical TRXs under the
base station.
Related eGBTS MML
commands:
STR RFTEST;
STR GBTSRFTST

Copyright © Huawei

Item the eGBTS or
GBTS or Not
Not
- Extended Per TRX Yes Yes License verification is

Spectrum triggered by the related
Scan (per GUI maintenance
TRX) function. The number of
licenses that need to be
allocated equals the
number of activated
logical TRXs under the
base station.
Related LMT GUI
maintenance function of
the eGBTS:
Offline Frequency
Spectrum Scanning

Item the eGBTS or
GBTS Not
or Not
GBFD BTS IP Per BTS No Yes If the eGBTS uses the
- Active TWAMP client or
15120 Performa TWAMP responder
2 nce function, a license needs
Measure to be allocated.
ment Related eGBTS MML
(per Site) commands: LST
TWAMPCLIENT and
LST
TWAMPRESPONDER

Featur License Sales Unit Supporte Supported eGBTS License
e ID Control d by the by the Allocation Instruction
Not Not
- SubSite Per Module Yes Yes Licenses need to be
Solution allocated only to China
License Mobile.
(per Number of licenses to be
Module)

Copyright © Huawei
allocated = Number of
RXU modules for multi-
site cells under the eGBTS
- Number of RXU
modules of the subsite
with the maximum
number of RXU modules.
Related BSC MML
command:
LST BTSLOCGRPE
Related BTS MML
commands:
LST SECTOR
LST RRU
- RFU co- Per Module Yes Yes Licenses need to be
cell allocated only to China
Solution Mobile.
License The number of licenses to
(per be allocated equals the
Module) number of RFUs for
multi-site cells under the
eGBTS.
Related BSC MML
command:
LST BTSLOCGRPE
Related BTS MML
commands:
LST SECTOR
LST RRU
GBFD 4-Way Per TRX Yes Yes The number of licenses to
- Receiver be allocated equals the
11590 Diversity number of activated
3 (per logical TRXs which are
TRX) set to the four-way receive
diversity mode under the
eGBTS.
Related BSC MML
command:
LST GTRX
Related BTS MML
command:
LST GTRXGROUP
- UBBP Per Module Yes Yes A license needs to be
Multi- allocated to each UBBP
Mode board that supports GSM.
license You can query details
(GSM) about the board through
(Per the eGBTS MML

Copyright © Huawei
Module) command: LST BBP.

GBFD IPsec Per BTS No Yes If the eGBTS is enabled
- redundan with the IPsec redundancy
16020 cy function, a license needs
9 among to be allocated to the
multi- eGBTS.
SeGWs Related eGBTS MML
(per command:
BTS)
LST IKEPEER
- supportin with the PKI redundancy
16021 g PKI function, a license needs
0 redundan to be allocated to the
cy (per eGBTS.
commands:
LST CA
LST CRLTSK
MRFD AAS Per RU No Yes The feature is controlled
- RAT by a false control item.
26110 Specific Contact the frontline
3 Tilting marketing personnel when
(GSM) manually allocating
(Per RU) licenses, of which the
number equals that of the
AAS, to a customer's base
station.
Related MML commands:
LST
GTRXGROUPSECTORE
QM
LST AARU
Not AAS Per RU No Yes The number of licenses to
comm Virtual be allocated equals the
erciall Four number of AARUs whose
y Uplink four virtual ports are used
deploy Channels by the TRX group as the
ed for GSM receive channel.
(per RU) Related MML commands:
LST GTRXGROUP
LST
GTRXGROUPSECTORE
QM
LST AARU

Copyright © Huawei

Not Not
GBFD GTMUb Per BTS No Yes If the main control board
- SingleO of the eGBTS is GTMUb,
17020 M (per a license needs to be
5 BTS) allocated.
Related eGBTS MML
command:
DSP BRDMFRINFO

Not Not
GBFD BTS Per BTS No Yes If the eGBTS is configured
- Supportin with multiple CAs or
17120 g Multi- IkePeer uses multiple
5 operator certificates, a license needs
PKI (per to be allocated.
commands:
LST CA
LST IKEPEER
- Supportin with the IPsec redirection
17120 g IPsec function, a license needs to
6 Redirecti be allocated to the eGBTS.
on (Per Related eGBTS MML
BTS) command:
LST IKEPEER
- Multi- Per band per Yes Yes Calculate the total number
Mode RRU of frequency bands used
Multi- by all multi-band RRUs
Band for GSM cells.
License Related BSC MML
for Multi- command:
Band RF
Module LST GTRX
(Per Band Related BTS MML
per RRU) commands:
LST
GTRXGROUPSECTORE
QM

Copyright © Huawei
LST SECTOREQM

Not Not
GBF BTS Per BTS No Yes If the IKE check switch for
D- Supportin the digital certificate
18120 g Digital whitelist is turned on for
2 Certificat the eGBTS, a license
e needs to be allocated.
Whitelist Related eGBTS MML
Managem command:
ent (Per
BTS) LST CERTCFG
3.11.2 NE Software Version Requirement

If multiple NEs are involved, the highest requirements for the NE software version must be
used. For example, if backplane co-transmission requires SRAN7.0 or later versions and co-
baseband requires SRAN8.0 or later, the NE must use SRAN9.0 or later versions. For details
about the version mapping between related NE and base station, see Multimode Base Station
Release Notes.
3.11.3 Board and Cable Installation Requirement.

The following table lists the materials required for mode transition.
The materials include the key materials required during mode transition but does not include
materials for new site deployment.
Table 20.12 Materials required for mode transition

RF RRU/RFU Determined based

on the plan
CPRI high-speed Determined based For the RFU
cable on the plan
CPRI fiber optic Determined based For the RRU
cable on the plan
Optical module Determined based For the RRU
on the plan
RRU power cable Determined based For the RRU
on the plan

Copyright © Huawei
RF interconnection Determined based Required by the

cable on the plan GSM, multimode,
and UMTS RF
modules
Antenna and feeder Antenna Same as the number Required when the
replaced
Feeder Twice the number of Not required when
sectors the RRU and
antenna are directly
connected to each
other.
The length of the
feeder needs to be
determined
survey.
Jumper The length of the
jumper needs to be
determined
survey.
the following
conditions are met:
for the new
mode.
 No TMA is
configured.
 The RRU and
antenna are not
directly
connected to
each other.
network plan.
internal RET is
available.
AISG cable Same as the number Required for
of sectors connecting to the
SBT or TMA when

Copyright © Huawei

lengths of the AISG
cable vary with
scenarios.
AISG cable from the Same as the number Required when the
RRU of sectors RRU and RET are
directly connected to
each other.
frequency bands
be combined.
MPT UMPT(L)/LMPT Determined based An LTE main
on the plan control board is
added.
Use a newly
delivered board
because such boards
work in the
maintenance mode
by default. If you do
not use a newly
delivered board, this
board may not work
in the maintenance
mode, and a false
alarm may be
generated during
mode transition and
deployed mode may
be interrupted.
UMPT(U)/WMPT Determined based A UMTS main
on the plan control board is
added.
Use a newly
delivered board
because such boards
work in the
maintenance mode
by default. If you do
not use a newly
delivered board, this
board may not work
in the maintenance
mode, and a false
alarm may be
generated during
mode transition and

Copyright © Huawei

deployed mode may
be interrupted.
GTMU Determined based A GSM main control
on the plan board is added.
BBU BBU subrack Determined based Used for BBU
interconnection and on the plan expansion.
BBU When BBU3900 and
BBU3910 are
interconnected, the
BBU3900 must be
used as the primary
BBU subrack.
Transmission cable Some Used for base station
transmission
Cable for BBU Some BBU
interconnection interconnection
through
UCIU+UMPT: One
optical fiber and two
optical modules are
required for BBU
interconnection.
BBU
interconnection
through
UMPT+UMPT: A
cable is required for
BBU
interconnection.
UCIU Determined based Used for BBU
on the plan interconnection
through
UCIU+UMPT.
The UCIU board
must be installed in
the same BBU as the
GTMU board is
installed because of
the GTMU hardware
limitation.

Copyright © Huawei
3.11.4 Data Configuration Requirement

This section summarizes the data configuration requirements for mode transition of a base
station (including the GBTS) during planning, helping users specify or import the related
parameters to the CME when the CME is used for creating scripts.
Domain Configurati MOC Parameter Para Value CM

on Object Name meter (Example E
ID ) Typ
e
RF Adding an RRU Cabinet No. CN 0 RF

module RXU
Adding an RRU Subrack No. SRN 60 RF
RXU
Adding an RRU Slot No. SN 3 RF
RXU
Adding an RRU RRU type RT MRRU RF
RXU
Adding an RRU RRU Topo TP TRUNK RF
RXU Position (in the
main chain
or ring)
Adding an RRU RRU RCN 0 RF
RXU Chain/Ring
No.
Adding an RRU RRU Position PS 0 RF
RXU
Adding an RRU RF Unit RS GL RF
RXU Working
Mode
Adding an RRU Number of RXN 2 RF
RXU RX channels UM
Adding an RRU Number of TXN 2 RF
RXU TX channels UM
BBU Root BBU CTRLLNK Local Link LN 0 Equ
interconne mode No. ipm
ction ent
Root BBU CTRLLNK Local Cabinet CN 0 Equ
mode No. ipm
ent
Root BBU CTRLLNK Local Subrack SRN 1 Equ
mode No. ipm
ent
Root BBU CTRLLNK Local Slot No. SN 7 Equ
mode ipm

Copyright © Huawei

ID ) Typ
e
ent
Root BBU CTRLLNK Upper Cabinet UPCN 0 Equ
mode No. ipm
ent
Root BBU CTRLLNK Upper UPSR 0 Equ
mode Subrack No. N ipm
ent
Root BBU CTRLLNK Upper Slot UPSN 4 Equ
mode No. ipm
ent
Root BBU CTRLLNK Upper Port UPPT 0 Equ
mode No. ipm
ent
Leaf BBU CTRLLNK Local Link LN 0 Equ
mode No. ipm
ent
Leaf BBU CTRLLNK Local Cabinet CN 0 Equ
mode No. ipm
ent
Leaf BBU CTRLLNK Local Subrack SRN 1 Equ
mode No. ipm
ent
Leaf BBU CTRLLNK Local Slot No. SN 7 Equ
mode ipm
ent
Leaf BBU CTRLLNK Upper Cabinet UPCN 0 Equ
mode No. ipm
ent
Leaf BBU CTRLLNK Upper UPSR 0 Equ
mode Subrack No. N ipm
ent
Leaf BBU CTRLLNK Upper Slot UPSN 4 Equ
mode No. ipm
ent
Leaf BBU CTRLLNK Upper Port UPPT 0 Equ
mode No. ipm
ent
Clock Original BTSCLK Clock Type ClkTy PEER_CL Equ
GBTS mode/new pe K ipm
mode ent

Copyright © Huawei

ID ) Typ
e
BTSCLK Peer Mode STAN Set this Equ

DAR parameter ipm
D to the ent
mode of
the
reference
clock.
Clock Original CLKMODE Clock MOD Set this Equ
mode/new Working E parameter ipm
mode Mode to ent
MANUAL
(Manual).
CLKMODE Selected CLKS Set this Equ
Clock Source RC parameter ipm
to ent
PEERCL
K(Peer
Clock).
PEERCLK Peer Clock PN Set this Equ
No. parameter ipm
to 0. ent
PEERCLK Peer Standard PS Set this Equ
parameter ipm
to the ent
mode of
the
reference
clock.
MPT Original Working Working WM Set this Equ
mode/new Mode Mode parameter ipm
mode to ent
CONCUR
RENT(Co
ncurrent).
Baseband Original BBP Base Band BBW Determine Equ
mode/new Work S d by the ipm
mode Standard UBBP ent
configurati
on plan
Original MDU Base Band BBW Determine Equ
mode/new Work S d by the ipm
mode Standard mode ent
planned
for the
UMDU

Copyright © Huawei

ID ) Typ
e
Transmiss New-mode E1T1 Tra

ion main control nsm
board issio
n
New-mode ETHPORT Tra
main control nsm
board issio
n
New-mode PPPLNK Tra
main control nsm
board issio
n
New-mode MPGRP Tra
main control nsm
board issio
n
New-mode MPLNK Tra
main control nsm
board issio
n
New-mode TUNNEL Tra
main control nsm
board issio
n
New-mode DEVIP Tra
main control nsm
board issio
n
New-mode IPRT Tra
main control nsm
board issio
n
New-mode OMCH Tra
main control nsm
board issio
n
New-mode SCTPLNK Tra
main control nsm
board issio
n
New-mode IPPATH Tra
main control nsm
board issio

Copyright © Huawei

ID ) Typ
e
n
New-mode EPGROUP Tra
main control nsm
board issio
n
New-mode and Tra
main control USERPLAN nsm
board EHOST (in issio
end point n
configuration
mode)
New-mode USERPLAN Tra
main control EPEER nsm
board issio
n
New-mode SCTPHOST Tra
main control nsm
board issio
n
New-mode SCTPPEER Tra
main control nsm
board issio
n
New-mode DHCPRELA Tra
main control YSWITCH nsm
board issio
n
New-mode DHCPSVRIP Tra
main control nsm
board issio
n
Original- TUNNEL Tra
mode main nsm
control board issio
n
Original- DEVIP Tra
mode main nsm
control board issio
n
Original- IPRT Tra
mode main nsm
control board issio

Copyright © Huawei

ID ) Typ
e
3.11.5 Tool Requirements for Co-MPT Reconstruction

Co-MPT reconstruction and mode expansion require special tools. These tools are deployed
on the standalone CME. The following table lists these tools.
Tool Name How to Obtain
BSC component co- Obtain the corresponding co-MPT conversion components based
MPT reconstruction on the versions.
configuration data http://support.huawei.com/carrier/navi#col=software&path=PBI1-
conversion: 7851894/PBI1-8132365/PBI1-7275801/PBI1-21466023/PBI1-
SRANconvert_BSC 13761
Module_V***R***C
**SPC***.zip
BTS component co- Obtain the corresponding co-MPT conversion components based
MPT reconstruction on the versions.
configuration data http://support.huawei.com/carrier/navi#amp%253Bpath=PBI1-
conversion: 7851894/PBI1-7854240/PBI1-7275801/PBI1-19953556/PBI1-
SRANconvert_GBTS 13761&col=software&path=PBI1-7851894/PBI1-8132365/PBI1-
&SRANModule_V** 7275801/PBI1-21465984/PBI1-13751
*R***C**SPC***.zi
p
Data planning NOTE
template for co-MPT Use the data planning template for the corresponding SRAN version during
reconstruction co-MPT reconstruction.
configuration data The following is the CME Client installation directory of the
conversion English version: U2000 installation
folder\client\client\Data\Common\SRANconvert\local\en_US
The following is the CME Client installation directory of the
Chinese version: U2000 installation
folder\client\client\Data\Common\SRANconvert\local\zh_CN
Standalone CME Obtain the software version of the standalone CME based on the
versions.
http://support.huawei.com/carrier/navi#col=software&path=PBI1-
7851894/PBI1-7854702/PBI1-7275896/PBI1-21103986/PBI1-
21044913

Copyright © Huawei
Mode Transition Guide(For NB) 4 Mode Transition Examples
4 Mode Transition Examples
This section describes mode transition using the MO involved in each domain for mode
transition planning based on application scenarios as an example. These mode transition
examples can be used as references for customizing the CME template during data creation.
The following describes the meanings of letters involved in mode transition:
 2. UL or U&L refers to a separate-MPT UMTS and LTE dual-mode base station. In a
UL/U&L base station, a single BBU is configured with two main control boards, in
which one works in UMTS mode and the other works in LTE(FDD) mode. Other cases,
such as GL and GU, are similar.
 U*L refers to a co-MPT UMTS and LTE dual-mode base station. In a U*L base station,
the main control board in a single BBU works in both UMTS and LTE(FDD)/LTE(TDD)
mode. Other cases, such as G*L and G*U, are similar.
 L(F), L(T), and L(M) refer to LTE (FDD), LTE (TDD), and LTE (NB-IoT), respectively.
 L(FM) refers to an eNodeB that supports both LTE (FDD) and LTE (NB-IoT). Other
cases, such as L(TM) and L(FTM), are similar.
For mode transition scenarios where LTE (FDD), LTE (TDD), and LTE (NB-IoT) are added,
such as mode transition from a UO base station to a U*L (FM) co-MPT base station, refer to
the mode transition example from UO to U*L, and then the example from L(F) to L(FM).
4.1 Example: Mode Transition from GU to GU+L

(UCIU+UMPT)
This chapter takes the transition from a GSM and UMTS dual-mode base station to a GU+L
(UCIU+UMPT) triple-mode base station as an example. This chapter lists the managed
objects (MOs) to be configured during the transition. Figure 1.21 shows the hardware
configurations before and after mode transition. Figure 1.22 shows the transmission
networking topology before and after mode transition.

Copyright © Huawei
Figure 1.21 Hardware configurations before and after mode transition

Copyright © Huawei
Figure 1.22 Transmission networking topology before and after mode transition
Table 22.1 lists the major differences before and after mode transition.
Table 22.1 Major differences before and after mode transition

Item Before Transition After Transition
Mode GSM and UMTS dual-mode GSM, UMTS, and LTE

triple-mode
Service configuration GSM and UMTS operating GSM and UMTS operating
in the 900 MHz frequency in the 900 MHz frequency
band, three sectors band, three sectors
configured configured; GSM and LTE
900 MHz: GSM S2/2/2/, operating in the 1800 MHz
UMTS S2/2/2, 1T2R frequency band, three
sectors configured
900 MHz: GSM S2/2/2/,
UMTS S2/2/2, 1T2R
1800 MHz: GSM S2/2/2,

Copyright © Huawei
LTE S1/1/1 (1x5 MHz),

2T2R
BBU One BBU; GSM and UMTS Two BBUs interconnected
sharing the same BBU through UCIU+UMPT
GSM and UMTS sharing the
same BBU; LTE using the
other BBU
RF typology Dual-star topology for GU Dual-star topology for both
RF modules GU RF modules and GL RF
modules
Transmission scheme Co-transmission through Co-transmission through
panel interconnection for UMPT backplane, IP over
GSM and UMTS, IP over Ethernet
Ethernet
Clock networking GSM and UMTS sharing the GSM, UMTS, and LTE
IEEE 1588 V2 reference using an IEEE 1588 V2
clock reference clock
The following tables list the MOs involved in the mode transition in different domains. The
data in these tables can be the references for data configuration in summary tables.
Table 22.2 LTE global data configuration

Dom Configurati MOC Parameter Recommended
ain on Object Value
Globa LTE CnOperator CN Operator ID 0

l
CnOperator CN Operator name LTE
CnOperator CN Operator type CNOPERATOR
_PRIMARY
CnOperator Mobile Country code 502
CnOperator Mobile network code 04
Clock TIMESRC Time Source NTP
Clock NTPCP IPv4 Address of NTP 10.141.142.22
Server
Clock NTPCP Synchronization Period 1
Clock TASM Clock Working Mode MANUAL
Clock TASM Clock Source No. 0
Clock TASM Selected Clock Source IPCLK
Clock TASM Clock Synchronization FREQ

Copyright © Huawei

ain on Object Value
Mode
Clock TASM Quality Level QL_PRC
Clock IPCLKLNK Link No. 0
Clock IPCLKLNK Protocol Type PTP
Clock IPCLKLNK Cabinet No./Subrack 0/1/7
No./Slot No.
Clock IPCLKLNK Server IPv4 170.179.179.34
Clock IPCLKLNK Client IPv4 160.70.7.10
Clock IPCLKLNK Domain 0
Table 22.3 LTE equipment data configuration

Domain Configu MOC Parameter Recommended
ration Value
Object
Equipment LTE SUBRACK Cabinet No. Cabinet No.: 0

Subrack No. Subrack No.: 1
Subrack Type Type: BBU3900
MPT MPT Cabinet No. 0
MPT MPT Subrack No. 1
MPT MPT Slot No. 7
MPT MPT Board Type UMPT
Baseband BBP Cabinet No. 0
Baseband BBP Subrack No. 1
Baseband BBP Slot No. 3
Baseband BBP Board Type LBBP
Baseband BBP Work Mode FDD
CPRI-based RRUCHAIN Three RRU chains
topology are connected to
optical fiber
cables through
three optical ports
0, 1, and 2 on the
baseband
processing board.

Copyright © Huawei

ration Value
Object
RF module RRU Cabinet Configure an RRU

No./Subrack on the new RRU
No./Slot No. chain. The subrack
No. of the RRU
must be different
from that of a
configured RRU
and the working
mode of the RRU
must be set to
GSM_LTE.
Subrack No. is
set to 63, 64, and
65 for the GL
RRUs.
Feeder RET Device No. 0, 1, and 2
Antenna and RET RET Type SINGLE_RET
feeder
Antenna and RET Polar Type DUAL
feeder
Antenna and RET Antenna Scenario REGULAR
feeder
Antenna and RET Control Port 0
feeder Cabinet No.
Antenna and RET Control Port 63, 64, and 65
feeder Subrack No.
Antenna and RET Control Port Slot 0
feeder No.
Antenna and RETSUBUNIT Device No. 0, 1, and 2
feeder
Antenna and RETSUBUNIT Subunit No. 0
feeder
Antenna and RETSUBUNIT Connect to the
feeder following:
0\63\0 R0A-
0\63\0 R0B
0\64\0 R0A-
0\64\0 R0B
0\65\0 R0A-
0\65\0 R0B

Copyright © Huawei
Table 22.4 LTE transmission data configuration

Domain Configuratio MOC Parameter Recommende
n Object d Value
Transmission LTE SCTPLNK Link No. 0

Transmission SCTPLNK Cabinet 0/1/7
No./Subrack
No./Slot No.
Transmission SCTPLNK First Local IP 160.70.7.13
Address
Transmission SCTPLNK Local SCTP 2913
Port No.
Transmission SCTPLNK First Peer IP 125.120.120.1
Address
Transmission SCTPLNK Peer SCTP Port 2910
No.
Transmission CPBEARER CP Bear No. 0
Transmission CPBEARER Flag MASTER
Transmission CPBEARER Bear Type SCTP
Transmission CPBEARER Link No. 0
Transmission IPPATH Path ID 0
Transmission IPPATH Cabinet 0/1/7
No./Subrack
No./Slot No.
Transmission IPPATH Subboard Type BASE_BOARD
Transmission IPPATH Port Type ETH
Transmission IPPATH Port No. 0
Transmission IPPATH Path Type ANY
Transmission IPPATH Local IP 160.70.7.13
Transmission IPPATH Peer IP 171.23.36.1
Transmission S1Interface S1 Interface ID 0
Transmission S1Interface S1 Interface CP 0
Bearer ID
Transmission S1Interface CN Operator ID 0
Transmission S1Interface MME Release Release_R10
Transmission S1Interface S1 Interface Is FALSE
Blocked
Transmission OMCH Standby Status MASETR

Copyright © Huawei

n Object d Value
Transmission OMCH Local IP 160.70.7.13

Transmission OMCH Local Mask 255.255.0.0
Transmission OMCH Peer IP 10.141.142.22
Transmission OMCH Peer Mask 255.255.255.0
Transmission DEVIP Cabinet 0\1\7
No./Subrack
No./Slot No.
Transmission DEVIP Subboard Type BASE_BOARD
Transmission DEVIP Port Type ETH
Transmission DEVIP Port No. 0
Transmission DEVIP IP Address 160.70.7.13
Transmission DEVIP Mask 255.255.0.0
Transmission TUNNEL Configure a
tunnel between
the UMPT and
GTMU boards,
and a tunnel
between the
UMPT and
WMPT boards
for backplane
transmission.
Both tunnels are
for downlink
transmission.
Transmission IPRT Route Index Configure eight
IP routes to the
following items:
U2000, clock,
SG-W, MME,
BSC, RNC,
GSM tunnel,
and UMTS
tunnel.
Set the route
type to Next
Hop for all the
IP routes except
for the two
routes to
tunnels and
specify the IP
addresses as
planned.

Copyright © Huawei

n Object d Value
Set the route

type to IF and
port type to
TUNNEL for
IP routes to
tunnels.
Transmission VLANMAP Next Hop IP 160.70.7.10
Transmission VLANMAP Mask 255.255.0.0
Transmission VLANMAP VLAN Mode SINGLEVLAN
Transmission VLANMAP VLAN ID 446
Transmission VLANMAP Set VLAN DISABLE
Priority
Transmission CTRLLNK The local board
is the UMPT
whose cabinet
No., subrack
No., and slot
No. being 0, 1,
and 7,
respectively.
The peer board
is the UCIU
whose cabinet
No., subrack
No., and slot
No. all being 0.
Transmission ETHPORT Port No. 0 and 1
Transmission ETHPORT Cabinet Corresponding
No./Subrack to those of the
No./Slot No. UMPT in
subrack 1.
Transmission ETHPORT Subboard Type BASE_BOARD
Transmission ETHPORT Port Attribute Two values:
COPPER
FIBER
Transmission DHCPSVRIP DHCP Server Set the DHCP
IP Address server IP
address to the
IP address of
the U2000 and
MBSC for
deployment.

Copyright © Huawei

n Object d Value
Transmission DHCPRELAYS DHCP Relay ENABLE

WITCH Switch
Transmission DHCPSW OMCH Auto- ENABLE
Establishment
Switch
Transmission DHCPSW Vlanscan DISABLE
Switch
Table 22.5 LTE radio data configuration

Domain Configuration MOC Parameter Recommende
Object d Value
Feeder LTE SECTOR —— Add three

sectors.
They use the
following
antennas:
0:
0,63,0,0;0,63,0,
1
1:
0,64,0,0;0,64,0,
1
2:
0,65,0,0;0,65,0,
1
Antenna and SECTOREQM —— Three pieces of
feeder sector
equipment are
added.
They
correspond to
sectors 0
through 2.
The following
sector antennas
are used:
0:
0,63,0,0,3,0;0,6
3,0,1,3,0
1:
0,64,0,0,3,0;0,6

Copyright © Huawei

Object d Value
4,0,1,3,0
2:
0,65,0,0,3,0;0,6
5,0,1,3,0
Radio Cell —— Three LTE cells
are added with
the following
key parameters
and the
corresponding
values:
FrequencyBand
:3
DlEarfcn: 1600
DlBandwidth:
CELL_BW_N5
0
UlBandwidth:
CELL_BW_N5
0
FddTddInd:
CELL_FDD
Transmit and
receive mode:
2T2R
Sector
equipment:
corresponding
to sector
equipment 0
through 2.
Radio BASEBANDE Baseband ULDL
QM Equipment
Type
Radio BASEBANDE UMTS UL DEM_4_CHAN
QM Demodulation
Mode
Radio BASEBANDE Baseband 0,1,3
QM Equipment
Board

Copyright © Huawei
Table 22.6 GSM data configuration

Object d Value
CPRI-based GSM BTSRXUCHAI Configure three

topology N RRU chains on
optical ports 3,
4, and 5 on the
GTMU.
CPRI-based BTSRXUBRD Added one
topology MRRU to
position 1 of
each of the
newly added
three chains.
RF module BTSRXUBP Working GSM_AND_LT
Standard E
Note that the
working mode
of the new RF
module must be
set to GL.
Radio GCELL Freq. Band Add three cells
that are served
by the
DCS1800
frequency band.
Radio TRXINFO Configure two
TRXs in each
cell using the
main and
diversity RX
channels.
Radio TRXBIND2PH Bind three cells
YBRD to the R0As of
three RRUs,
respectively.
Table 22.7 GSM transmission data configuration

Object d Value
Transmission GSM BTSDEVIP Port Type LOOPINTERF

ACE
Transmission BTSDEVIP Cabinet Cabinet
No./Subrack No./Subrack
No./Slot No. No./Slot No. of

Copyright © Huawei

Object d Value
the GTMU
Transmission BTSDEVIP IP Address 88.200.8.241
Transmission BTSIP BTS LOGICIP
Communication
Type
Transmission BTSIP BTS IP 88.200.8.241
Transmission BTSIP BSC IP 26.14.1.1
Transmission BTSESN BTS Interface 21021127226T
Board Bar Code BA915704
1
Transmission BTSESN OM Bear Board BACKBOARD
Transmission BTSTUNNEL -- From the
GTMU to
UMPT (LTE),
the tunnel No.
is 0.
Transmission BTSIPRT Destination IP 26.14.1.1 (BSC)
Address
Transmission BTSIPRT Route Index 0
Transmission BTSIPRT Route Type OUTIF
Transmission BTSIPRT Cabinet Cabinet
No./Slot No. of No./Slot No. of
the ports the GTMU
Transmission BTSIPRT Interface Type TUNNEL
Transmission BTSCLK Clock Type PEER_CLK
Transmission BTSCLK Peer Mode LTE
Transmission IPRT Subrack No 0
Transmission IPRT Slot No 14
Transmission IPRT Destination IP 88.200.8.241
address
Transmission IPRT Next hop type Gateway
Transmission IPRT Forward route 26.14.0.1
address

Copyright © Huawei
Table 22.8 UMTS equipment data configuration

Object d Value
Clock UMTS PEERCLK Peer Clock No. 0

Clock PEERCLK Peer Standard LTE
Clock TASM Clock Working MANUAL
Mode
Clock TASM Clock Source 0
No.
Clock TASM Selected Clock PEERCLK
Source
Clock TASM Clock FREQ
Synchronizatio
n Mode
Clock TASM Quality Level QL-SSU-B
Table 22.9 UMTS transmission data configuration

n Object d Value
Transmission UMTS DEVIP Cabinet Corresponding

No./Subrack to the cabinet
No./Slot No. No./subrack
No./slot No. of
the WMPT
Transmission DEVIP Port Type LOOPINT
Transmission SCTPLNK Set the local IP
address (base
station side) and
destination IP
address (base
station
controller side)
of an SCTP link
to LTE IP
addresses.
Transmission IPPATH Set the local IP

Copyright © Huawei

n Object d Value
address (base
station side) and
destination IP
address (base
station
controller side)
of an IP path to
LTE IP
addresses.
Transmission OMCH Local IP Change it to an
address on the
LTE side.
Transmission TUNNEL The tunnel
starts from the
WMPT to the
UMPT and the
direction is
uplink.
Transmission IPRT Configure IP
routes to the
U2000, RNC,
and UMPT.
Remove the
clock route.
Route Type: IF
Port Type:
TUNNEL
4.2 Example: Mode Transition from GO to GL

This chapter takes the transition from a GSM only (GO) single-mode base station to a GSM
and LTE dual-mode base station as an example. This chapter lists the managed objects (MOs)
to be configured during the transition. Figure 1.23 shows the hardware configurations before
and after mode transition. Figure 1.24 shows the transmission networking topology before and
after mode transition.

Copyright © Huawei

Copyright © Huawei

Mode GSM only single-mode GSM and LTE dual-mode

Service configuration GSM operating in the 900 GSM operating in the 900
MHz frequency band, three MHz frequency band, three
sectors configured; GSM sectors configured; GSM
operating in the 1800 MHz and LTE operating in the
frequency band, three 1800 MHz frequency band,
sectors configured three sectors configured
900 MHz: GSM S4/4/4, 900 MHz: GSM S4/4/4,
1T2R 1T2R
1800 MHz: GSM S2/2/2, 1800 MHz: GSM S2/2/2,

Copyright © Huawei
1T2R LTE S1/1/1 (1x5 MHz),

2T2R
BBU One BBU One BBU
GSM and LTE using the
same BBU and GSM
configured with UBRI
RF typology Star topology for GO RF Star topology for GO RF
modules modules and dual-star
topology for GL RF
modules
Transmission scheme Transmission through panel, GSM and LTE co-
IP over Ethernet transmission through
backplane interconnection
with LTE port connected to
the transport network, IP
over Ethernet
Clock networking GO IEEE 1588 V2 reference GSM and LTE sharing an
clock IEEE 1588 V2 reference
clock

ain on Object Value
LTE CnOperator CN Operator ID 0

_PRIMARY
Server

Copyright © Huawei

ain on Object Value

Mode
Clock IPCLKLNK Link No. 0
Clock IPCLKLNK Cabinet No./Subrack Corresponding
No./Slot No. to those of the
main control
board
Clock IPCLKLNK Client IPv4 160.70.7.10
Clock IPCLKLNK Domain 0
Globa APPLICATION Application INSTALL
l Maintenance Mode
Trans ETHPORT Port No. 0
missi
on
Trans ETHPORT Cabinet No./Subrack Corresponding
missi No./Slot No. to those of the
on main control
board
Trans ETHPORT Subboard Type BASE_BOARD
missi
on

ration Value
Object
MPT LTE MPT Cabinet No. 0

MPT MPT Slot No. 7
MPT MPT Board Type LMPT

Copyright © Huawei

ration Value
Object

Equipment CABINET Cabinet No. Cabinet No.: 0 and
Cabinet Type 1
Cabinet Type:
BTS3900
Equipment SUBRACK Cabinet No. Cabinet No.: 0
Subrack No. Subrack 0:
Subrack Type BBU3900
Subrack 11: FMU
Subrack 4: RFU
CPRI-based RRUCHAIN Six RRU chains
the fiber optical
cables through the
six CPRI ports on
the baseband
processing board.
RF RFU Cabinet Add six RFUs:
No./Subrack 1/4/0 - 1/4/5
No./Slot No.
RF RFU RRU Topo Position TRUCK
RF RFU RRU Chain No. 0-5
RF RFU RRU Position 0
RF RFU RRU type MRFU
RF RFU RF Unit Working GL
Mode
RF RFU Number of RX 2
channels
RF RFU Number of TX 1
channels
Antenna and RET Device No. 0, 1, and 2
feeder
feeder
feeder

Copyright © Huawei

ration Value
Object

feeder
feeder Cabinet No.
feeder Subrack No.
Antenna and RET Control Port Slot 0, 2, and 4
feeder No.
feeder
feeder
Antenna and RETSUBUNIT Connect Port 1 Connect to the
feeder Cabinet No. following:
1\4\0 R0A- 1\4\1
R0A
1\4\2 R0A- 1\4\3
R0A
1\4\4 R0A- 1\4\5
R0A

Object d Value

Transmission SCTPLNK Cabinet The main
No./Subrack control board
No./Slot No. provides
transmission
ports.
Address
Port No.
Address
No.

Copyright © Huawei

Object d Value

Transmission IPPATH Cabinet Corresponding
No./Slot No. main control
board
Bearer ID
Blocked
Transmission OMCH Local IP Base Station
Transport
Data\OM
Plane\*OmCh
LocalIP
Transmission OMCH Local Mask Base Station
Transport
Data/OM
Plane/*OmCh
LocalMask
Transmission OMCH Peer IP Base Station
Transport
Data\OM
Plane\OmCh

Copyright © Huawei

Object d Value
DstIP
Transmission OMCH Peer Mask Base Station
Transport
Data\OM
Plane\OmCh
DstMask
Transmission DEVIP Cabinet Corresponding
board
Transmission TUNNEL The tunnel
starts from the
UMPT to the
GTMU and the
direction is
downlink.
Transmission IPRT Route Index Configure six
IP routes: for
OMCH, for
IPCLK, to the
GBTS, S-GW,
MME, and
BSC,
respectively.
Set the route
type to Next
Hop for all the
IP routes except
for the two
routes to the
GBTS and
specify the IP
addresses as
planned.
Set the route
type to IF and
port type to
TUNNEL for
IP routes to
tunnels.

Copyright © Huawei

Object d Value

Priority
address to the
IP address of
the U2000 and
MBSC for
deployment.
Transmission DHCPRELAY DHCP Relay ENABLE
SWITCH Switch
Establishment
Switch
Switch

Object d Value
Antenna and LTE SECTOR Sector ID Add three

feeder Sector Name sectors.
Sector Antenna They use the
following
antennas:
0: 1, 4, 0, 0; 1,
4, 1, 0
1: 1, 4, 2, 0; 1,
4, 3, 0
2: 1, 4, 4, 0; 1,
4, 5, 0

Copyright © Huawei

Object d Value
Antenna and SECTOREQM Sector Three pieces of

feeder Equipment ID sector
equipment are
added.
They
correspond to
sectors 0
through 2.
The following
sector antennas
are used:
0:
1,4,0,0,3,0;1,4,1
,0,3,0
1:
1,4,2,0,3,0;1,4,3
,0,3,0
2:
1,4,4,0,3,0;1,4,5
,0,3,0
Cell Three LTE cells
are added with
the following
key parameters
and the
corresponding
values:
FrequencyBand
:3
DlEarfcn: 1250
DlBandwidth:
CELL_BW_N5
0
UlBandwidth:
CELL_BW_N5
0
FddTddInd:
CELL_FDD
Transmit and
receive mode:
2T2R
Sector
equipment:
corresponding
to sector
equipment 0

Copyright © Huawei

Object d Value
through 2.
Baseband
equipment:
share equipment
0.
Baseband BASEBANDE Baseband 0
QM Equipment ID
Baseband BASEBANDE Baseband ULDL
QM Equipment
Type
Baseband BASEBANDE UMTS UL DEM_4_CHAN
QM Demodulation
Mode
Baseband BASEBANDE Baseband 0, 0, 3
QM Equipment
Board
Table 24.6 GSM configuration

Object d Value
Equipment GSM BTSBRD —— Add a UBRI to

slot 2
(0_0_2_1).
Equipment BTSCABINET Cabinet No. Add a BTS3900
to cabinet 1.
CPRI-based BTSRXUCHAI Add six chains
topology N that are
connected to
fiber optical
cables through
six CPRI
optical ports on
the UBRI.
RF BTSRXUBRD Added one
MRFU to
position 1 of
each of the
newly added six
chains.
RF BTSRXUBP Working GSM_AND_LT
Standard E

Copyright © Huawei

Object d Value
Note that the

working mode
of the new RF
module must be
set to GL.
RF TRXBIND2PH Bind the TRX
YBRD of the cell
served by the
1800 MHz to
the 1800 MHz
MRFU in
cabinet 1.
Table 24.7 BSC Configuration

Object d Value

ACE
Transmission BTSDEVIP *Port No. 0
Transmission BTSDEVIP Cabinet Corresponding
No./slot No. of
the GTMU
Transmission BTSDEVIP IP Index 0
Transmission BTSDEVIP IP Mask 255.255.255.0
Transmission BTSDEVIP BTS Inner IP NO
Switch
Communication
Type
Transmission BTSIP BTS MultiIP NO
Switch
Board Bar Code AB020269
1

Copyright © Huawei

Object d Value

Transmission BTSTUNNEL The tunnel
starts from the
GTMU to the
UMPT and is
used for
interconnection
through panel
transmission.
Transmission BTSIPRT Destination IP 40.13.3.200
Address
Transmission BTSIPRT Destination 255.255.255.25
Address Mask 5
the GTMU
Transmission IPRT Subrack No. 0
Transmission IPRT Slot No. 14
Transmission IPRT Destination IP Set the
address destination IP
addresses to the
IP addresses of
the GBTS:
88.200.8.37
160.70.7.10
Transmission IPRT Destination 255.255.255.25
address mask 5
address
Transmission IPRT Priority HIGH

Copyright © Huawei
4.3 Example: Mode Transition from GO to GU

This chapter takes the transition from a GSM only (GO) single-mode base station to a GSM
and UMTS dual-mode base station as an example. This chapter lists the managed objects
(MOs) to be configured during the transition. Figure 1.25 shows the hardware configurations
before and after mode transition. Figure 1.26 shows the transmission networking topology
before and after mode transition.

Copyright © Huawei

Mode GSM only single-mode GSM and UMTS dual-mode

Service configuration GSM operating in the 900 GSM and UMTS operating
MHz frequency band, three in the 900 MHz frequency
sectors configured band, three sectors
900 MHz: GSM S4/4/4, configured
1T2R 900 MHz: GSM S4/4/4/,
UMTS S2/2/2, 1T2R
BBU One BBU GSM and UMTS sharing the
same BBU
RF typology Chain topology Dual-star topology for GU
RF modules
Transmission scheme Independent transmission GSM and UMTS
through panel, IP over independent transmission
Ethernet through panel, IP over

Copyright © Huawei
Ethernet
Clock networking IP reference clock GSM and UMTS using an
independent IP reference
clock
Table 26.2 UMPT data configuration

Domain Configurat MOC Parameter Recommend
ion Object ed Value
Clock UMTS IPCLKLNK Link No. 0

Clock IPCLKLNK Cabinet No./Subrack Cabinet
No./Slot No. No./Subrack
No./Slot No.
of the main
control board
4
Mode
Global UNODEBMNT Maintenance Mode INSTALL
MODE
Table 26.3 MBSC global data configuration

ion Object ed Value
Equipment MBSC NE Network Element U_Transition_

Name 100
Equipment NE Product Type BTS3900_WC
DMA

Copyright © Huawei

ion Object ed Value
Equipment NE NodeB Template BTS3900_WC

DMA_IP
RAN_2-
Channels
Demodulation
_3Sector
Equipment NODEB RNC Name MBSC252
Equipment NODEB NodeB ID 44
Equipment NODEB Subrack No. 0
Equipment NODEB Slot No. 2
Equipment NODEB Subsystem No. 3
Equipment NODEB IUB Transport Bearer IP_TRANS
Type
Equipment NODEB IP Transport Apart Ind SUPPORT
Equipment NODEB NodeB Host Type SINGLEHOS
T
Equipment NODEB Sharing Type Of DEDICATED
NodeB
Equipment NODEB Cn Operator Index 1
Transmissio ETHIP Subrack No. 0
n
Transmissio ETHIP Slot No. 14
n
Transmissio ETHIP Port No. 6
n
Transmissio ETHIP IP address index 0
n
Transmissio ETHIP Local IP address 26.14.1.1
n
Transmissio ETHIP Subnet mask 255.255.0.0
n
Transmissio NCP Bearing Link Type SCTP
n
Transmissio NCP Port No. 0
n
Transmissio NCP Bearing Link Type SCTP
n
Transmissio NCP SCTP link No. 1001

Copyright © Huawei

ion Object ed Value
n
Transmissio NCP SCTP link No. 1002
n
Transmissio ADJNODE Adjacent Node ID 2340
n
Transmissio ADJNODE Adjacent Node Name U_Transition_
n 100
Transmissio ADJNODE Transport Type IP
n
Transmissio IPCLKLNK Client IPv4 26.14.7.15
n
Radio ULOCELL Add two cells
to each of the
three new
RFUs with
1T2R.
Radio Cell Add two cells
to each of the
three new
RFUs with
1T2R.
Transmissio SCTPLNK Application type Add two
n SCTP links.
Both peer IP
addresses are
26.14.7.15.
Peer ports are
port 1024 and
port 1025.
Transmissio IPPATH Adjacent Node ID 2340
n
Transmissio IPPATH IP path ID 1
n 2
3
4
Transmissio IPPATH Interface Type IUB
n
Transmissio IPPATH Transport Type IP
n
Transmissio IPPATH IP path type EF
n

Copyright © Huawei

ion Object ed Value
AF43
AF23
AF13
Transmissio IPPATH Local IP address 26.14.1.1
n
Transmissio IPPATH Peer IP address 26.14.7.15
n
Transmissio NODEBALGO NodeB Name U_Transition_
n PARA 100
Transmissio NODEBALGO NodeB LDC algorithm 000000
n PARA switch
Transmissio NODEBALGO NodeB Max HSDPA 6144
n PARA User Number
Transmissio NODEBALGO NodeB Max HSUPA 6144
n PARA User Number
Transmissio NODEBALGO HSUPA Credit MBR
n PARA Consume Type
Transmissio NODEBALGO NodeB Algorithm 0
n PARA Enhancement Switch
Radio CELLLDR DL LDR first action BERateRed
Radio CELLLDR DL LDR second action NoAct
Radio CELLLDR DL LDR third action NoAct
Radio CELLLDR DL LDR eighth action 1
Radio CELLLDR DL LDR ninth action 1
Radio CELLLDR DL LDR tenth action 3
Radio CELLLDR DL LDR Eleventh 1
Action
Radio CELLLDR DL LDR twelfth action 3
Radio CELLLDR DL LDR-BE rate 1
reduction RAB number
Radio CELLLDR DL LDR un-ctrl RT BERateRed
Qos re-nego RAB num
Radio CELLLDR UL LDR third action 1
Radio CELLLDR UL LDR fourth action 1
Radio CELLLDR UL LDR fifth action 3

Copyright © Huawei

ion Object ed Value
Radio CELLLDR UL LDR sixth action 1

Radio CELLLDR UL LDR seventh 3
action
Radio CELLLDR UL LDR eighth action 1
Radio CELLLDR UL LDR Ninth Action 1
Radio CELLLDR UL LDR-BE rate 2
Radio CELLLDR UL LDR un-ctrl RT SF8
Qos re-nego RAB num
Radio CELLLDR UL PS should be HO SF8
user number
Radio CELLLDR UL LDR-AMR rate SF8
Radio NODEBOLC DL OLC released RAB 1
number
Radio NODEBOLC UL OLC released RAB 1
number
Radio NODEBOLC MBMS Services 1
Number Released
Radio NODEBOLC Sequence of User MBMS_REL
Release

Object d Value
MPT UMTS MPT Cabinet No. 0

MPT MPT Slot No. 7
MPT MPT Board Type WMPT
MPT MPT Enable Flag ENABLE
Baseband BBP Board Type WBBP

Copyright © Huawei

Object d Value

QM Equipment ID
QM Equipment
Type
Baseband BASEBANDE UMTS UL DEM_2_CHAN
QM Demodulation
Mode
Baseband BASEBANDE Baseband 0, 0, 3
QM Equipment
Board
CPRI-based RRUCHAIN Three RRU
topology chains are
connected to
three optical
ports 0, 2, and 4
on the baseband
processing
board.
RF RFU Add one RFU
to port 0 of each
of the three
newly added
chains.

Object d Value
Transmission UMTS NODEBPATH PATH ID Four paths 1

through 4.
Transmission SCTPLNK Add two new
SCTP links.
Both IP
addresses are
26.14.7.15.
Local ports are
port 1024 and
port 1025.
Transmission CPBEARER Add two CP
bearers with two
corresponding

Copyright © Huawei

Object d Value
SCTP links.
Transmission IUBCP Port Type NCP
CCP
Transmission IUBCP CP Port No. /
0
Transmission IUBCP Belong Flag MASTER
Transmission IUBCP CPBear ID 2
3
Transmission IPPATH Four IP paths.
The DSCPs are
46, 38, 22, and
14.
Transmission OMCH Local Mask Base Station
Transport
Data/OM
Plane/*OmCh
LocalMask
Transmission DEVIP IP Address IP address:
160.70.7.10
Type: ETH
Transmission NTPCP IPv4 Address 10.141.142.22
of NTP Server
Transmission NTPCP IP Mode IPV4
Transmission NTPCP Synchronizatio 10
n Period(min)
Transmission NTPCP Port Number 123
Transmission NTPCP Authentication PLAIN
Mode
Transmission NTPCP Master Flag Master
Transmission IPRT Add two IP
routes.
Destination IP
addresses:
170.179.179.34

Copyright © Huawei

Object d Value
10.0.0.0
Table 26.6 UMTS radio data configuration

Object d Value
Antenna and UMTS SECTOR Sector Antenna 0, 4, 0, R0A; 0,

feeder 4, 0, R0B
0, 4, 2, R0A; 0,
4, 2, R0B
0, 4, 4, R0A; 0,
4, 4, R0B
Table 26.7 GSM equipment data configuration

Object d Value
RF GSM BTSRXUBP Working GSM_AND_U

Standard MTS
4.4 Example: Mode Transition from UO to UL

This chapter takes the transition from a UMTS only (GO) single-mode base station to a
UMTS and LTE dual-mode base station as an example. This chapter lists the managed objects

Copyright © Huawei

Copyright © Huawei

Mode UMTS only single-mode UMTS and LTE dual-mode

Service configuration UMTS operating in the 1700 UMTS and LTE operating in
MHz frequency band, three the 1700 MHz frequency
sectors configured 1700 band, three sectors
MHz: UMTS S2/2/2, 1T2R configured
1700 MHz: UMTS S2/2/2,
LTE S1/1/1 (1x5 MHz),
2T2R
BBU One BBU UMTS and LTE share a
BBU, the WBBPf board is
configured for UMTS, and
the LBBPd board is
configured for LTE.
RF typology Chain topology Chain topology with UL
sharing CRPI links
Transmission scheme Transmission through panel, UMTS and LTE
IP over Ethernet independent transmission
through panel, IP over
Ethernet
Clock networking IEEE 1588 V2 reference UMTS and LTE sharing an
clock

ain on Object Value

l
_PRIMARY

Copyright © Huawei

ain on Object Value
Server
Clock TASM Selected Clock Source PEERCLK
missi
on
on main control
board
missi
on

ration Value
Object
Baseband LTE BBP Cabinet No. 0

CPRI-based RRUCHAIN Add an RRU
topology chain on optical
port 0 on the
baseband
processing board.
RF RRU Cabinet Add three
No./Subrack cascaded RRUs to
No./Slot No. the new RRU
chain.

Copyright © Huawei

Object d Value
Transmission SCTPLNK Cabinet Add an LMPT

No./Subrack to provide
No./Slot No. transmission
ports.
Address
Port No.
Address
No.
No./slot No. of
the LMPT.
Bearer ID
Blocked

Copyright © Huawei

Object d Value
Transmission S1Interface Control Mode MANUAL_MO

DE
No./slot No. of
the LMPT.
Transmission IPRT Route Index Configure three
IP routes: one
for OMCH, one
to the S-GW,
and one to the
MME.
OMCH
TO SG-W
TO MME
Set the route
type to Next
Hop and
specify the IP
addresses as
planned.
Priority

Copyright © Huawei

Object d Value

following
antennas:
0:
0,60,0,R0A;0,6
0,0,R0B
1: 0, 61, 0,
R0A; 0, 61, 0,
R0B
2: 0, 62, 0,
R0A; 0, 62, 0,
R0B
Radio Cell Three LTE cells
are added with
the following
key parameters
and the
corresponding
values:
FrequencyBand
:3
DlEarfcn: 1450
DlBandwidth:
CELL_BW_N5
0
UlBandwidth:
CELL_BW_N5
0
FddTddInd:CE
LL_FDD
Transmit and
receive mode:
1T2R
Sector
equipment:
corresponding
to sector
equipment 0
through 2.

Copyright © Huawei
Table 28.6 UMTS data configuration

ion Object ed Value
RF UMTS RRU RF Unit Working UL

Mode
4.5 Example: Mode Transition from GU to GU (CPRI

MUX)+L (BBU Interconnection, Inter-BBU Triple-Mode
SDR)
This chapter takes the transition from a GSM and UMTS (GU) dual-mode base station with
dual-star topology to a GU (CPRI MUX)+L (inter-BBU SDR and BBU interconnection)
triple-mode base station as an example. This chapter lists the managed objects (MOs) to be
configured during the transition. Figure 1.29 shows the hardware configurations before and
after mode transition. Figure 1.30 shows the transmission networking topology before and

Copyright © Huawei


triple-mode
configured configured; LTE operating
900 MHz: GSM S2/2/2/, in the 800 MHz frequency
UMTS S2/2/2, 1T2R band, three sectors
configured
900 MHz: GSM S2/2/2/,
UMTS S2/2/2, 1T2R
800 MHz: LTE S1/1/1 (1x10

Copyright © Huawei
MHz), 2T2R
BBU One BBU; GSM and UMTS Two BBUs interconnected
sharing the same BBU through UCIU+UMPT
GSM and UMTS sharing the
same BBU; LTE using the
other BBU
RF typology Dual-star topology for GU CPRI MUX topology for
RF modules GSM and UMTS, inter-
subrack dual-star topology
for LTE
Transmission scheme Co-transmission through Co-transmission through
panel interconnection for UMPT backplane
GSM and UMTS, IP over interconnection, IP over
Ethernet Ethernet
IEEE 1588 V2 reference using an IEEE 1588 V2

ion Object ed Value
Global LTE CnOperator CN Operator ID 0

CnOperator CN Operator type CNOPERATO
R_PRIMARY
Server
Clock NTPCP Synchronization 1
Period

Copyright © Huawei

ion Object ed Value

Mode
Equipment EQUIPMENT Maintenance Mode INSTALL

Object d Value
Equipment LTE SUBRACK Cabinet No. 0

Equipment SUBRACK Subrack No. 1
Equipment SUBRACK Subrack Type BBU3900
MPT MPT Cabinet No. 0
MPT MPT Slot No. 7
MPT MPT Board Type UMPT
MPT MPT Enable Flag ENABLE
Equipment BBUFAN Cabinet No. 0
Equipment BBUFAN Subrack No. 1
Equipment BBUFAN Slot No. 16
Equipment PEU Cabinet No. 0
Equipment PEU Subrack No. 1
Equipment PEU Slot No. 19
CPRI-based RRUCHAIN Configure three
topology RRU chains to
optical ports 0
through 2 on the
LBBP board.

Copyright © Huawei

Object d Value
RF RRU Configure an
RRU on the
new RRU
chain. The RRU
working mode
must be set to
GUL. The GUL
RRU subracks
must be
assigned with
numbers 60, 61,
and 62.
BBU CTRLLNK Local Link No. The local board
interconnection is the UMPT
whose cabinet
No., subrack
No., and slot
No. being 0, 1,
and 7,
respectively.
The peer board
is the UCIU
whose cabinet
No., subrack
No., and slot
No. being 0, 0,
and 4,
respectively.

Object d Value

subrack 1.
subrack 1.

Copyright © Huawei

Object d Value

Transmission TUNNEL Configure a
tunnel between
the UMPT and
GTMU boards,
and a tunnel
between the
UMPT and
WMPT boards
for backplane
transmission.
Transmission IPRT Configure
routes from the
base station to
the U2000,
BSC, RNC,
MME, S-GW,
IP clock, the
GTMU board,
and the WMPT
board. The
routes to the
U2000, BSC,
RNC, MME,
and S-GW are
panel routes,
and two tunnels
must be
configured for
the transmission
through
backplane for
GTMU and
WMPT boards.
Transmission SCTPLNK Link No. 0
No./Subrack control board in
No./Slot No. subrack 1
provides
transmission
ports.
Address

Copyright © Huawei

Object d Value
Port No.
Address
No.
board
Bearer ID
Blocked

Copyright © Huawei

Object d Value

Priority
address to the
IP address of
the U2000 and
MBSC for
deployment.
Transmission DHCPRELAY DHCP Relay ENABLE
SWITCH Switch
Establishment
Switch
Switch

Object d Value

following
antennas:
0:
0, 60, 0, 0; 0,
60, 0, 1
1:
0, 61, 0, 0; 0,
61, 0, 1
2:
0, 62, 0, 0; 0,
62, 0, 1
equipment are

Copyright © Huawei

Object d Value
added.
They
correspond to
sectors 0
through 2.
The following
sector antennas
are used:
0:
0, 60, 0, 0, 3, 0;
0, 60, 0, 1, 3, 0
1:
0, 61, 0, 0, 3, 0;
0, 61, 0, 1, 3, 0
2:
0, 62, 0, 0, 3, 0;
0, 62, 0, 1, 3, 0
are added with
the following
key parameters
and the
corresponding
values:
FrequencyBand
: 20
DlEarfcn:
6200
DlBandwidth:
CELL_BW_N5
0
UlBandwidth:
CELL_BW_N5
0
FddTddInd:
CELL_FDD
Transmit and
receive mode:
2T2R
Sector
equipment:
corresponding
to sector
equipment 0
through 2.

Copyright © Huawei

Object d Value
Baseband
equipment:
share equipment
0.

Object d Value
CPRI-based GSM BTSRXUCHAI Set the Access

topology N Type column in
the BTS RXU
Chain area to
PEERPORT
and the Head
Board No.
column to that
of the WBBP in
slot 3.
RF BTSRXUBP Working GSM_AND_U
Standard MTS_AND_LT
E
Note: The
working mode
the RF module
must be
changed to
GUL.

Object d Value

ACE
Transmission BTSDEVIP Cabinet Cabinet
the GTMU
Communication
Type

Copyright © Huawei

Object d Value

Board Bar Code A9025307
1
Transmission BTSTUNNEL -- From the
GTMU to
UMPT (LTE),
the tunnel No.
is 0.
Transmission BTSIPRT Destination IP 25.14.1.1 (BSC)
Address
No./Slot No. of No./Slot No. of
the ports the GTMU
Transmission IPRT Subrack No 0
Transmission IPRT Slot No 14
address
address
Table 30.8 BSC data configuration

Object d Value
Transmission BSC BTSDEVIP Port Type LOOPINTERF

ACE
Transmission BTSDEVIP *Port No. 0

Copyright © Huawei

Object d Value
Transmission BTSDEVIP Cabinet Corresponding

No./slot No. of
the GTMU
Transmission BTSDEVIP IP Index 0
Transmission BTSDEVIP IP Mask 255.255.255.0
Transmission BTSDEVIP BTS Inner IP NO
Switch
Communication
Type
Transmission BTSIP BTS MultiIP NO
Switch
Board Bar Code A9025307
1
BBU BTSTUNNEL Source: GTMU
interconnection Destination:
UMPT
The tunnel is
used for
backplane
transmission
interconnection.
Transmission BTSIPRT Destination IP Device IP
Address address of the
BSC: 25.14.1.1
Transmission BTSIPRT Destination 255.255.255.25
Address Mask 5

Copyright © Huawei

Object d Value

the GTMU
Clock BTSCLK Clock Type PEER_CLK
Clock BTSCLK Peer Mode LTE
Transmission IPRT Subrack No. 0
Transmission IPRT Slot No. 14
address
Transmission IPRT Destination 255.255.255.25
address mask 5
address
Transmission IPRT Priority HIGH

Object d Value
Clock UMTS PEERCLK Peer Clock No. 0

Clock PEERCLK Peer Standard LTE
RF RRU RF Unit Set the working
Working Mode mode of RRUs
in subracks 60
through 62 to
GUL.

n Object d Value
Transmission UMTS DEVIP Cabinet Corresponding

No./slot No. of
the WMPT

Copyright © Huawei

n Object d Value

Transmission SCTPLNK Set the local IP
address (base
station side) and
destination IP
address (base
station
controller side)
of an SCTP link
to LTE IP
addresses.
Transmission IPPATH Set the local IP
address (base
station side) and
destination IP
address (base
station
controller side)
of an IP path to
LTE IP
addresses.
Transmission OMCH Local IP Change it to an
address on the
LTE side.
BBU TUNNEL The tunnel
interconnection starts from the
WMPT to the
UMPT and the
direction is
uplink.
Transmission IPRT Reconfigure IP
routes.
Configure
tunnel routes to
the U2000,
RNC, and
UMPT board,
and remove the
routes to the
BSC and IP
clock server.

Copyright © Huawei

n Object d Value
Route Type: IF
Port Type:
TUNNEL
Transmission IPRT Destination IP Configure a
route from the
RNC to the
NodeB.
Transmission NODEBIP NodeB IPTRANS_IP
TransType
Transmission NODEBIP NodeB 88.200.8.238
IP_TRANS IP
address
Transmission NODEBIP NodeB 255.255.255.25
IP_TRANS IP 5
Mask
Transmission NODEBIP NodeB 0
IP_TRANS
Subrack No.
Transmission NODEBIP NodeB 14
IP_TRANS Slot
No.
Transmission NODEBIP Whether NO
Binding logical
port or not
4.6 Example: Mode Transition from GO to G*L

This chapter takes the transition from a GSM only (GO) single-mode base station to a G*L
(CPRI MUX) dual-mode base station as an example. This chapter lists the managed objects

Copyright © Huawei

Copyright © Huawei

Mode GSM only single-mode Co-MPT GSM and LTE dual-mode

Service GSM only in the 1800 MHz GSM and LTE operating in the 1800
configurat frequency band, three sectors MHz frequency band, three sectors
ion configured configured
1800 MHz: GSM S2/2/2, 1T2R 1800 MHz: GSM S2/2/2, LTE S1/1/1,
GSM 1T2R, LTE 2T2R
BBU One BBU One BBU configured with UMPT_GL
RF Star topology for GO RF modules GL CPRI MUX topology
typology
Transmiss IP over Ethernet GSM and LTE co-transmission, IP
ion over Ethernet
scheme
Clock IP reference clock Co-MPT GL synchronous Ethernet
networkin clock
g
In this scenario, the GBTS must be reconstructed into an eGBTS, and the data plan must be
filled out. The filling method is described in the following table.
Data plan filling for reconstruction from a GBTS to an eGBTS
1. Filling in the GlobalPlanning page
PlanningXLSVer Plan Table Version SRAN11.1 Description
BscSctpIdBase Start BSC SCTPID 5000 GSM parameter,

Default value: 5000 which is
mandatory
BtsSctpPortBase Start SCTP port of a 8001 GSM parameter,
base station Default which is optional
value: 8001
BtsTrxPerSctp Number of TRXs 12 GSM parameter,
supported by each which is optional
SCTP of a base
station Default value:
12
BtsOMCHPeerIP Peer IP address of the 10.141.14.22 GSM parameter,
OM channel in a base which is
station mandatory

Copyright © Huawei
BtsOMCHPeerIPMask Peer IP mask of the 255.255.255.0 GSM parameter,

OM channel in a base which is
station mandatory
SRANBaselineRAT Primary mode during This parameter
the SRAN data does not need to be
merge. Default value: set for single-mode
L base stations, and it
is optional for
MBTSs.
WORKMODE Work mode Default Mandatory when
value: E1_UNBA E1/T1 transmission
is used in GSM
ActBTSSoftwareVersio Version number of GSM evolution,
n the activated GBTS mandatory
evolution software
(GTMU software of a
special V900 version)
BSCNodeRedundancyB Name of the currently Mandatory in the
SCName reconstructed BSC in BSC node
the BSC node redundancy
redundancy scenario scenario
ActGTMUSoftwareVer Version number of GTMU SingleOM,
sion the activated GTMU mandatory
SingleOM
reconstruction
software (GTMU
software of a special
V900 version)
2. Filling in the SitePlanning page
Table 32.2 Fields to be filled in the SitePlanning page

Field Description Examples
ConvertFlag Conversion ID Yes

BtsName GBTS name GBTS_XX
NextHop Gateway IP address of the Fill in the table according to
base station actual conditions.
GTMU Abandoned Whether to abandon the YES
GTMU for GSM after the
conversion. Default value: NO
UMPTSlot Slot number of the GSM main 7
control board after the
conversion. Default value: 7

Copyright © Huawei
The following tables list the MOs involved in the mode transition from an eGBTS to GL co-
MPT in different domains. The data in these tables can be the references for data
configuration in summary tables.

ain on Object Value

l
_PRIMARY
Server
missi
on
on main control
board
missi
on

ration Value
Object


Copyright © Huawei

ration Value
Object
Baseband BBP Board Type UBBP

CPRI-based RRUCHAIN Move the RRU
topology chain to the
optical port 0 to 2
on the baseband
processing board
and add a new
RRU chain in the
optical port 0 to 2,
respectively.
RF RRU Cabinet Put the RRU as
No./Subrack RRU 0 in the
No./Slot No. RRU chain.
RF RRU RF Unit Working GL
Mode

Object d Value

Transmission SCTPLNK Cabinet A new added
No./Subrack UMPT provides
No./Slot No. transmission.
Address
Port No.
Address
No.

Copyright © Huawei

Object d Value

No./slot No. of
the UMPT
Bearer ID
Blocked
No./slot No. of
the UMPT
Transmission IPRT Route Index Configure three
IP routes.

Copyright © Huawei

Object d Value
The functions
are as follows:
OMCH
TO SG-W
TO MME
Set the route
type to Next
Hop and
specify the IP
addresses as
planned.
Priority

Object d Value

following
antennas:
0:
0,60,0,R0A;0,6
0,0,R0B
1: 0, 61, 0,
R0A; 0, 61, 0,
R0B
2: 0, 62, 0,
R0A; 0, 62, 0,
R0B
are added with
the following
key parameters
and the
corresponding

Copyright © Huawei

Object d Value
values:
FrequencyBand
:3
DlEarfcn: 1450
DlBandwidth:
CELL_BW_N5
0
UlBandwidth:
CELL_BW_N5
0
FddTddInd:
CELL_FDD
Transmit and
receive mode:
1T2R
Sector
equipment:
corresponding
to sector
equipment 0
through 2.
4.7 Example: Mode Transition from UO to G*U

This chapter takes the transition from a UMTS only (UO) single-mode base station to a co-
MPT GSM and UMTS (GU) dual-mode base station that uses CPRI MUX star topology as an
example. This chapter lists the managed objects (MOs) to be configured during the transition.
Figure 1.33 shows the hardware configurations before and after mode transition. Figure 1.34
shows the transmission networking topology before and after mode transition.

Copyright © Huawei

Copyright © Huawei

Mode UMTS only single-mode Co-MPT GSM and UMTS

dual-mode
Service configuration UMTS operating in the 900 GSM and UMTS operating
MHz frequency band, three in the 900 MHz frequency
sectors configured band, three sectors
900 MHz: UMTS S2/2/2, configured

Copyright © Huawei
1T2R 900 MHz: UMTS S2/2/2,

GSM S2/2/2, 1T2R
BBU One BBU One BBU configured with
UMPT_GU
RF typology Chain topology The GU star topology using
CPRI MUX is used. A
UBRIb is added on the
eGBTS side. A WBBPf is
added on the NodeB side
and the original WBBPd is
moved to slot 0.
Transmission scheme Transmission through panel, GSM and UMTS co-
IP over Ethernet transmission, IP over
Ethernet
Clock networking IEEE 1588 V2 reference GSM and UMTS sharing the
clock
Data plan filling involved in the transition from a separate-MPT UMTS only base
station to a co-MPT UMTS only base station
1. GlobalPlanning page: No filling is required.
2. SitePlanning page


NodeBName NodeB name NodeB_XX

ration Value
Object
CPRI-based UMTS RRUCHAIN - The slot housing

topology the board which
provides RRU
chain ports is
changed from slot
3 to slot 1.

Copyright © Huawei

ration Value
Object
RF RRU - The working

mode of RRUs is
changed from
UMTS single
mode to GU dual
mode.
Baseband BBP - Add a WBBPf to
slot 3 and change
the slot housing
the original
WBBPd to slot 0.
QM Equipment ID
QM Equipment Type
Baseband BASEBANDE UMTS UL ULDL
QM Demodulation Mode
Baseband BASEBANDE Baseband 0,0,0;0,0,3
QM Equipment Board

Object d Value
Transmission GSM ADJNODE Adjacent Node 14410

ID
Radio GCELL - Three cells
working on the
900 MHz
frequency band
Values of Local
Cell ID are 0, 1,
and 2,
respectively.
Values of TRX
Group ID are
441, 442, and
443,
respectively.
Transmission SCTPLNK Application ABISCP
type
Transmission SCTPLNK SCTP link ID 1441

Copyright © Huawei

Object d Value
Transmission SCTPLNK Signalling link SERVER

mode
Transmission SCTPLNK First local IP 25.14.1.1
address
Transmission SCTPLNK First destination 25.14.24.141
IP address
Transmission SCTPLNK Destination 1026
SCTP port No.
Transmission IPPATH Adjacent Node 14410
ID
Transmission IPPATH Interface Type ABIS
Transmission IPPATH Is eGBTS Yes
Transmission IPPATH IP path type QoS
address
Transmission IPPATH Peer IP address 25.14.24.141

ration Value
Object
Equipment GSM BRI - Add a UBRI to

slot 1.
CPRI-based RRUCHAIN - Change the board
topology providing RRU
chain ports from
the WBBP to the
UBRIb for CPRI
connection.
RF RRU RF Unit Working GU
Mode

Copyright © Huawei

Object d Value
Transmission GSM DEVIP Cabinet Corresponding

board
Priority
transmission
ports.
Address
Port No.
Address
No.
Transmission GBTSPATH Path ID 0
Configure an IP
path ID for the
eGBTS. (Note
that the IP path
ID cannot be
the same as that
of UMTS
before

Copyright © Huawei

Object d Value
transition.
Otherwise, the
original data
will be
overwritten.)
Note that the
CP Bear No.
cannot be the
same as that of
UMTS before
transition.
Otherwise, the
original data
will be
overwritten.)
board
Transmission GBTSABISCP Control Port ID 0
Transmission GBTSABISCP CP Bear No. 0
Table 34.7 GSM radio data configuration

Object d Value
Antenna and GSM SECTOR Sector ID Add three

feeder

Copyright © Huawei

Object d Value
Sector Name sectors.

following
antennas:
0:
0,60,0,R0A;0,6
0,0,R0B
1:
0,61,0,R0A;0,6
1,0,R0B
2:
0,62,0,R0A;0,6
2,0,R0B
equipment are
added.
They
correspond to
sectors 0
through 2.
The following
sector antennas
are used:
0:
0,60,0,R0B,RX
_MODE,;0,60,0
,R0A,RXTX_M
ODE,MASTER
1:
0,61,0,R0B,RX
_MODE,;0,61,0
,R0A,RXTX_M
ODE,MASTER
2:
0,62,0,R0B,RX
_MODE,;0,62S,
0,R0A,RXTX_
MODE,MASTE
R
Radio GTRXGROUP TRX Group ID 441, 442, and
443
Note that the
TRX group IDs
must be

Copyright © Huawei

Object d Value
consistent with
those on the
BSC side.
Radio GTRXGROUP Local Cell ID 0, 1, and 2
Radio GTRXGROUP Sending Mode SINGLESND
Radio GTRXGROUP Receiving MAINDIVERS
Mode ITY
Note that the
configuration of
transmit and
receive mode
must be
consistent with
the number of
sector
equipment
antennas.
Radio GTRXGROUP Working Mode INDEPENDEN
T
Radio GTRXGROUP Sector 0, 1, and 2
Equipment ID
Global APPLICATIO Application INSTALL
N Maintenance
Mode
4.8 Example: Mode Transition from GU to G[U*L]

This section takes the transition from a separate-MPT GSM and UMTS (GU) dual-mode base
station to a GSM (GTMU), UMTS, and LTE (G+UL) multimode base station with dual-star
topology (GU 900 MHz) and CPRI MUX topology (GL 1800 MHz) as an example. This
chapter lists the managed objects (MOs) to be configured during the transition. Figure 1.35
shows the hardware configurations before and after mode transition. Figure 1.36 shows the
transmission networking topology before and after mode transition.

Copyright © Huawei

Copyright © Huawei

Mode Separate-MPT GSM and G[U*L] multimode

UMTS dual-mode
configured configured; GSM and LTE
900 MHz: UMTS S1/1/1, operating in the 1800 MHz

Copyright © Huawei
1T2R; GSM S2/2/2, 1T2R frequency band, three

sectors configured
900 MHz: UMTS S1/1/1,
GSM S2/2/2
1800 MHz: LTE S1/1/1,
GSM S2/2/2
BBU One BBU One BBU. UMTS and LTE
sharing the MPT and LTE
configured with LBBPd
RF typology Dual-star topology (GU 900 Dual-star topology (GU 900
MHz) MHz) and CPRI MUX
topology (GL 1800 MHz)
Transmission scheme GSM E1 transmission, GSM E1 transmission
UMTS transmission through remains unchanged. UMTS
panel, IP over Ethernet and LTE co-transmission
through IP over Ethernet
Clock networking GSM using the E1 reference GSM using the E1 reference
clock, UMTS sharing the clock, UMTS and LTE
GSM reference clock sharing the GSM reference
clock
2. SitePlanning page



n Object d Value
Radio GSM GCELL Freq. Band Add three cells

that are served
by the

Copyright © Huawei

n Object d Value
DCS1800
frequency band.
Radio TRXINFO —— Configure two
TRXs in each
cell using the
main and
diversity RX
channels.
Radio TRXBIND2PH —— Bind three cells
YBRD to the R0As of
three RRUs,
respectively.
CPRI-based BTSRXUCHAI —— Add three RFU
topology N or RRU chains
that connect to
optical ports 3,
4, and 5 on the
board in slot 3
of subrack 0 of
cabinet 0. The
chain numbers
are 3, 4, and 5,
which must be
different those
for the GSM
macro base
station. If the
chain numbers
are the same,
related data will
be overwritten.
RF BTSRXUBRD —— Add one RRU
to position 1 of
each of the
three newly
added chains.
The cabinet
No., subrack
No., and slot
No. of the three
RRUs 0/60/0,
0/61/0,
and0/62/0,
respectively
RF BTSRXUBP MRRU/GRRU/ DOUBLEDOU
AIRU Sending BLE_ANTENN
Receiving A
Mode

Copyright © Huawei

n Object d Value

Standard E

Domain Configurat MOC Parameter Recommended
ion Object Value

Global CnOperator CN Operator name LTE
Global CnOperator CN Operator type CNOPERATOR
_PRIMARY
Global CnOperator Mobile Country 502
code
Global CnOperator Mobile network 04
code
Transmission SCTPPEER First Peer IP 125.120.120.1
Address (To MME)
Transmission USERPLANEP Peer IP Address 171.23.36.1
EER (To S-GW)
N Maintenance Mode

Domain Configurati MOC Parameter Recommended
on Object Value
Equipment LTE eNodeBFuncti eNodeB ID 380

on
CPRI- RRUCHAIN —— Add three RRU
based chains to optical
topology ports 3 through 5
on the interface
board in slot 3.
RF RRU —— Added one RRU
to position 0 of
each of the newly
added three
chains. The
cabinet

Copyright © Huawei
Domain Configurati MOC Parameter Recommended

on Object Value
No./subrack
No./slot No. of the
three RRUs are as
follows:
0/60/0 - 0/62/0
Working mode:
GL
Baseband BBP Base Band Work GSM-0&UMTS-
Standard 1&LTE_FDD-
1&LTE_TDD-0

Object d Value

transmission
ports.
Address
Port No.
Address
No.
board

Copyright © Huawei

Object d Value

Bearer ID
Blocked
board
Transmission IPRT Route Index Configure two
IP routes.
Destination IP
addresses:
171.23.36.1
125.120.120.1
The route type
is set to
NEXTHOP.

Copyright © Huawei

Object d Value
Priority

Object d Value

following
antennas:
3:
0,60,0,R0A;0,6
0,0,R0B
4:
0,61,0,R0A;0,6
1,0,R0B
5:
0,62,0,R0A;0,6
2,0,R0B
equipment are
added.
They
correspond to
sectors 3
through 5.
The following
sector antennas
are used:
3:
0,60,0,R0A,RX
TX_MODE,M
ASTER;0,60,0,
R0B,RXTX_M
ODE,MASTER
4:
0,61,0,R0A,RX
TX_MODE,M
ASTER;0,61,0,
R0B,RXTX_M
ODE,MASTER

Copyright © Huawei

Object d Value
5:
0,62,0,R0A,RX
TX_MODE,M
ASTER;0,62,0,
R0B,RXTX_M
ODE,MASTER
are added with
the following
key parameters
and the
corresponding
values:
FrequencyBand
:3
DlEarfcn: 1600
DlBandwidth:
CELL_BW_N5
0
UlBandwidth:
CELL_BW_N5
0
FddTddInd:
CELL_FDD
Transmit and
receive mode:
1T2R
Sector
equipment:
corresponding
to sector
equipment 3
through 5.
4.9 Example: Mode Transition from GU to GU+L

(UMPT+UMPT, BBU Interconnection)
This chapter takes the transition from a GSM and UMTS dual-mode base station to a GU+L
(UMPT+UMPT) triple-mode base station as an example. This chapter lists the managed
objects (MOs) to be configured during the transition. Figure 1.37 shows the hardware
configurations before and after mode transition. Figure 1.38 shows the transmission

Copyright © Huawei

Copyright © Huawei

Mode GSM and UMTS dual-mode GSM, UMTS, and LTE triple-mode
Service GSM and UMTS operating in GSM and UMTS operating in the 900
configurati the 900 MHz frequency band, MHz frequency band, three sectors
on three sectors configured configured; GSM and LTE operating in
900 MHz: GSM S2/2/2/, UMTS the 1800 MHz frequency band, three
S2/2/2, 1T2R sectors configured
900 MHz: GSM S2/2/2/, UMTS S2/2/2,
1T2R
1800 MHz: GSM S2/2/2, LTE S1/1/1
(1x10 MHz), 2T2R
BBU One BBU; GSM and UMTS Two BBUs interconnected through

Copyright © Huawei
sharing the same BBU UMPT+UMPT

GSM and UMTS sharing the same BBU;
LTE using the other BBU
RF Dual-star topology for GU RF Dual-star topology for both GU RF
typology modules modules and GL RF modules
Transmissi GSM and UMTS independent GSM and UMTS independent
on scheme transmission, IP over Ethernet transmission, LTE co-transmission
through backplane with a port on UMTS
connected to the transport network, IP
over Ethernet
Clock GSM and UMTS using an GSM and UMTS using an independent
networkin independent IEEE 1588 V2 IEEE 1588 V2 reference clock,
g reference clock, respectively respectively, LTE and UMTS sharing one
IEEE 1588 V2 reference clock

ain on Object Value

l
Globa CnOperator CN Operator name LTE
l
Globa CnOperator CN Operator type CNOPERATOR
l _PRIMARY
Globa CnOperator Mobile Country code 502
l
Globa CnOperator Mobile network code 04
l
Server

Copyright © Huawei

ain on Object Value
Mode
Clock PEERCLK Peer Standard UMTS
Clock PEERCLK Peer Clock No. 0
Equip EQUIPMENT Maintenance Mode INSTALL
ment

ration Value
Object

MPT MPT Slot No. 7
MPT MPT Board Type LMPT
Equipment CABINET Cabinet No. Cabinet No.: 0
Cabinet Type Type: BTS3900
Subrack 11: FMU
Subrack 4: RFU
CPRI-based RRUCHAIN —— Three RRU chains
three optical ports
0, 2, and 4 on the
baseband
processing board.
RF RFU Cabinet Configure an RFU
No./Subrack on the new RRU

Copyright © Huawei

ration Value
Object
No./Slot No. chain. The RFU

slot number must
be different from
that of the
configured RFU
for GU, and the
working mode of
the RFU must be
set to GSM_LTE.
feeder
feeder
feeder
feeder
feeder Cabinet No.
feeder Subrack No.
Antenna and RET Control Port Slot 3, 4, and 5
feeder No.
feeder
feeder
Antenna and RETSUBUNIT Connect Port 1 Connect to the
feeder Cabinet No. following:
0\4\3 R0A- 0\4\3
R0B
0\4\4 R0A-
0\4\4R0B
0\4\5 R0A- 0\4\5
R0B

Copyright © Huawei

Object d Value

Transmission SCTPLNK Cabinet 0/1/7
No./Subrack
No./Slot No.
Address
Port No.
Address
No.
Transmission IPPATH Cabinet 0/1/7
No./Subrack
No./Slot No.
Transmission IPPATH Subboard Type BACK_BOAR
D
Transmission IPPATH Port Type TUNNEL
Bearer ID
Blocked

Copyright © Huawei

Object d Value

Transmission DEVIP Cabinet 0/1/7
No./Subrack
No./Slot No.
BBU TUNNEL —— The tunnel
interconnection starts from the
UMPT to the
GTMU and the
direction is
downlink.
Transmission IPRT Route Index Configure the
IP routes for the
U2000, MME,
and S-GW. If
co-transmission
through
backplane
interconnection
is used, the
tunnel provides
routing.
BBU CTRLLNK Local Link No. The local board
interconnection is the UMPT
whose cabinet
No., subrack
No., and slot
No. being 0, 1,
and 7,
respectively.
The peer board
is the UMPT
whose cabinet
No., subrack

Copyright © Huawei

Object d Value
No., and slot

No. being 0, 0,
and 7,
respectively.
Transmission ETHPORT Port No. 0
subrack 1.
Transmission

Object d Value

following
antennas:
0:
0,4,3,0;0,4,3,1
1:
0,4,4,0;0,4,4,1
2:
0,4,5,0;0,4,5,1
equipment are
added.
They
correspond to
sectors 0
through 2.
The following
sector antennas
are used:
0:
0,4,3,0,3,0;0,4,3
,1,3,0
1:

Copyright © Huawei

Object d Value
0,4,4,0,3,0;0,4,4
,1,3,0
2:
0,4,5,0,3,0;0,4,5
,1,3,0
are added with
the following
key parameters
and the
corresponding
values:
FrequencyBand
:3
DlEarfcn: 1600
DlBandwidth:
CELL_BW_N5
0
UlBandwidth:
CELL_BW_N5
0
FddTddInd:
CELL_FDD
Transmit and
receive mode:
2T2R
Sector
equipment:
corresponding
to sector
equipment 0
through 2.
Baseband
equipment:
share equipment
0.

Object d Value
CPRI-based GSM BTSRXUCHAI —— Configure three

topology N RRU chains on
optical ports 1,
3, and 5 on the

Copyright © Huawei

Object d Value
GTMU.
RF BTSRXUBRD —— Added one
MRRU to
position 0 of
each of the
newly added
three chains.
Standard E
Note that the
working mode
of the new RF
module must be
set to GL.
Radio GCELL Freq. Band Add three cells
that are served
by the
DCS1800
frequency band.
Radio TRXINFO —— Configure two
TRXs in each
cell using the
main and
diversity RX
channels.
Radio TRXBIND2PH —— Bind three cells
YBRD to the R0As of
three RRUs,
respectively.

ration Value
Object
BBU UMTS CTRLLNK Local Link No. The local board is

interconnection the UMPT whose
cabinet No.,
subrack No., and
slot No. being 0,
1, and 7,
respectively.
The peer board is
the UMPT whose
cabinet No.,

Copyright © Huawei

ration Value
Object
subrack No., and

slot No. being 0,
0, and 7,
respectively.
BBU TUNNEL —— Add a tunnel to
interconnection the UMPT_L
board.
The tunnel
direction is uplink.
Transmission IPRT —— Configure IP
routes. Configure
a tunnel to the
UMPT_L board.
Transmission DHCPSVRIP DHCP Server IP Set the IP address
Address of the DHCP
server to that of
the U2000. The IP
address is used for
base station
deployment.
Transmission DHCPRELAY DHCP Relay Switch ENABLE
SWITCH
Establishment
Switch
Transmission DHCPSW Vlanscan Switch DISABLE
4.10 Example: Mode Transition from GU+L

(UCIU+UMPT) to GU+LT (UCIU+UMPT)
This chapter takes the transition from a GU+L (UCIU+UMPT) triple-mode base station to a
GU+LT (UCIU+UMPT) quadruple-mode base station as an example. This chapter lists the
managed objects (MOs) to be configured during the transition. Figure 1.39 shows the
hardware configurations before and after mode transition. Figure 1.40 shows the transmission

Copyright © Huawei

Copyright © Huawei

Mode GU+L triple mode GU+LT quadruple-mode

configurati the 900 MHz frequency band, MHz frequency band, GSM and LTE
on GSM and LTE operating in the operating in the 1800 MHz frequency
1800 MHz frequency band, band, LTE TDD operating in the 2600
three sectors configured MHz frequency band, three sectors

Copyright © Huawei
900 MHz: GSM S2/2/2/, UMTS configured

S2/2/2, 1T2R 900 MHz: GSM S2/2/2/, UMTS S2/2/2,
1800 MHz: GSM S2/2/2, LTE 1T2R
S1/1/1, 2T2R 1800 MHz: GSM S2/2/2, LTE S1/1/1,
2T2R
2600 MHz: TDD S1/1/1 (1 x 20 MHz),
4T4R
BBU Two BBUs interconnected Two BBUs interconnected through
through UCIU+UMPT UCIU+UMPT
GSM and UMTS sharing the GSM and UMTS sharing the same BBU,
same BBU; LTE using the other LTE using the other BBU. The TDD mode
BBU is configured for the BBU of the eNodeB.
RF Dual-star topology for both GU Dual-star topology for both GU and GL
typology RF modules and GL RF RF modules, star topology for TDD RF
modules modules
Transmissi GSM and UMTS co- Remains the same.
on scheme transmission through backplane
interconnection and connected
to LTE, IP over Ethernet
Clock GSM and UMTS share the LTE LTE uses the GPS reference clock and the
networkin IEEE 1588v2 reference clock. clock synchronization mode is time
g The frequency synchronization synchronization. GSM and UMTS share
mode is configured. the LTE reference clock. The time
synchronization mode is configured for
GSM and UMTS. For the clock changes,
see the following descriptions.

ration Value
Object
Clock BSC BTSCLK CLKSYNCMODE TIMESYN

ration Value
Object
Clock UMTS TASM Clock TIME

Copyright © Huawei

ration Value
Object
Synchronization
Mode

ain on Object Value
Clock LTE GPS GPS Clock No. 0

Clock GPS Cabinet No./Subrack 0/1/0
No./Slot No.
Clock CnOperator Way to Get Position AUTO_SEARC
H
Clock GPS GPS Work Mode GPS
Clock GPS Mobile network code 04
Clock TASM Selected Clock Source GPS
Clock TASM Clock Synchronization TIME
Mode

ration Value
Object
Equipment LTE USCU Cabinet No. 0

Equipment USCU Subrack No. 1
Equipment USCU Slot No. 0
Equipment USCU Board Type LMPT

Copyright © Huawei

ration Value
Object

Cabinet Type 1
Cabinet Type:
BTS3900
Subrack 11: FMU
Subrack 4: RFU
optical fiber
cables through
three optical ports
3, 4, and 53 on the
baseband board.
RF RFU Cabinet One RRU is added
No./Subrack to the new RRU
No./Slot No. chain.
Working mode:
TDL
feeder
feeder
feeder
feeder
Antenna and RET Control Port Cabinet
feeder Cabinet No./Subrack
No./Subrack No./Slot No. of
No./Slot No. the three new
RRUs
feeder
feeder

Copyright © Huawei

ration Value
Object
Antenna and RETSUBUNIT Connect Port 1 Connected to

feeder Cabinet No. channels A and B
of the three RRUs

Object d Value

following
antennas:
3:
0, 60, 0, 0; 0,
60, 0, 1; 0, 60,
0, 2; 0, 60, 0, 3
4:
0, 61, 0, 0; 0,
61, 0, 1; 0, 61,
0, 2; 0, 61, 0, 3
5:
0, 62, 0, 0; 0,
62, 0, 1; 0, 62,
0, 2; 0, 62, 0, 3
equipment are
added.
They
correspond to
sectors 0
through 2.
The following
sector antennas
are used:
3:
0, 60, 0, 0, 3, 0;
0, 60, 0, 1, 3, 0;
0, 60, 0, 2, 3, 0;
0, 60, 0, 3, 3, 0
4:
0, 61, 0, 0, 3, 0;

Copyright © Huawei

Object d Value
0, 61, 0, 1, 3, 0;
0, 61, 0, 2, 3, 0;
0, 61, 0, 3, 3, 0
5:
0, 62, 0, 0, 3, 0;
0, 62, 0, 1, 3, 0;
0, 62, 0, 2, 3, 0;
0, 62, 0, 3, 3, 0
are added with
the following
key parameters
and the
corresponding
values:
FrequencyBand
: 38
DlEarfcn:
38150
DlBandwidth:
CELL_BW_N2
5
UlBandwidth:
CELL_BW_N2
5
FddTddInd:
CELL_TDD
Transmit and
receive mode:
4T4R
Working mode:
UL_DL
Sector
equipment:
corresponding
to sector
equipment 3
through 5.
Baseband
equipment:
share equipment
0.
Radio CellOp —— Add for cell 4
and cell 5.
With the related
parameters set

Copyright © Huawei

Object d Value
as follows:
Local tracking
area ID: 4 and 5
Cell reserved
for operator:
CELL_NOT_R
ESERVED_FO
R_OP
Radio CnOperatorTa —— Add for cell 4
and cell 5.
With the related
parameters set
as follows:
Local tracking
area ID: 4 and 5
CN Operator
ID: 0
Tracking area
code: 4 and 5
4.11 Example: Mode Transition from LO to G*L CPRI

Load Sharing4.8, 4.9
This chapter takes the transition from an LTE single-mode base station to a co-MPT GSM and
LTE (GL) dual-mode base station using CPRI MUX load sharing as an example. This chapter
lists the managed objects (MOs) to be configured during the transition. Figure 1.41 shows the
hardware configurations before and after mode transition. Figure 1.42 shows the transmission

Copyright © Huawei

Copyright © Huawei

Mode LTE single-mode Co-MPT GSM and LTE dual-mode

Service LTE operating in the 1800 MHz GSM and LTE operating in the 1800
configurat frequency band, three sectors MHz frequency band, three sectors
ion configured configured
1800 MHz: LTE S1/1/1, 2T2R 1800 MHz: GSM S2/2/2, LTE S1/1/1,
GSM 1T2R, LTE 2T2R
BBU One BBU One BBU configured with GL co-
MPT, GSM configured with the
UBRIb
RF Star topology for LO RF modules GL CPRI MUX load sharing
typology
Transmiss IP over Ethernet GSM and LTE co-transmission, IP
ion over Ethernet
scheme
Clock Synchronous Ethernet clock Co-MPT GL synchronous Ethernet
networkin clock
g
Data plan filling involved in the transition from a separate-MPT LTE only base station
to a co-MPT LTE only base station
 Filling in the GlobalPlanning page
No
 Filling in the SitePlanning page
Table 42.2 Filling in fields in the SitePlanning page


eNodeBName eNodeB name eNodeB_XX

Copyright © Huawei
Table 42.3 LTE data configuration

ration Value
Object
RF LTE RRU RF Unit Working GL

Mode
CPRI-based RRUCHAIN Topo Type LOADBALANCE
topology

Object d Value
Transmission BSC ADJNODE Adjacent Node 523

ID
Radio GCELL —— Three cells
working on the
1800 MHz
frequency band
Local Cell ID:
3, 4, and 5
TRX Group ID:
0, 1, and 2
Transmission SCTPLNK Application ABISCP
type
Transmission SCTPLNK SCTP link ID 523
Transmission SCTPLNK Signalling link SERVER
mode
Transmission SCTPLNK First local IP 25.14.1.1
address
Transmission SCTPLNK First destination 25.14.7.10
IP address
Transmission SCTPLNK Destination 1024
SCTP port No.
Transmission IPPATH Adjacent Node 523
ID
Transmission IPPATH IP path ID 1
Transmission IPPATH Interface Type ABIS
Transmission IPPATH Is eGBTS Yes
Transmission IPPATH IP path type QoS

Copyright © Huawei

Object d Value

address
Transmission IPPATH Peer IP address 25.14.7.10

ration Value
Object
Equipment GSM BRI —— Add an UBRI

board to slot 1.
CPRI-based RRUCHAIN —— Change Topo
topology Type to LOAD
BALANCE for
the RRU chain
and add CPRI
ports to the
UBRIb board.
RF RRU RF Unit Working GL
Mode

Object d Value
Transmission GSM DEVIP Cabinet Corresponding

board

Copyright © Huawei

Object d Value

Priority
transmission
ports.
Address
Port No.
Address
No.
Transmission GBTSPATH Path ID 1
Configure an IP
path ID for the
eGBTS. (Note
that the IP path
ID cannot be
the same as that
of UMTS
before
transition.
Otherwise, the
original data
will be
overwritten.)
Note that the
CP Bear No.
cannot be the
same as that of
UMTS before
transition.
Otherwise, the
original data
will be
overwritten.)

Copyright © Huawei

Object d Value

board
Transmission GBTSABISCP Control Port ID 0
Transmission GBTSABISCP CP Bear No. 1
Table 42.7 GSM radio data configuration

Object d Value
Antenna and GSM SECTOREQM Sector Three pieces of

equipment are
added.
They
correspond to
sectors 0
through 2.
The following
sector antennas
are used:
3:
0,60,0,R0B,RX
_MODE,SLAV
E;0,60,0,R0A,R
XTX_MODE,
MASTER
4:
0,61,0,R0B,RX

Copyright © Huawei

Object d Value
_MODE,SLAV
E;0,61,0,R0A,R
XTX_MODE,
MASTER
5:
0,62,0,R0B,RX
_MODE,SLAV
E;0,62,0,R0A,R
XTX_MODE,
MASTER
Antenna and GTRXGROUP TRX Group ID 0, 1, and 2
feeder Note that the
TRX group IDs
must be
consistent with
those on the
BSC side.
Radio GTRXGROUP Local Cell ID 3, 4, and 5
Radio GTRXGROUP Sector 3, 4, and 5
Equipment ID
4.12 Example: Mode Transition from G*U to G*U*L

(Outdoor BBU)
This chapter takes the transition from a GSM and UMTS (GU) dual-mode base station
configured with outdoor BBUs to a GU900 (CPRI MUX) + L1800 triple-mode base station as
an example. This chapter lists the managed objects (MOs) to be configured during the
transition. Figure 1.43 shows the hardware configurations before and after mode transition.
Figure 1.44 shows the transmission networking topology before and after mode transition.

Copyright © Huawei

Copyright © Huawei

Copyright © Huawei


triple-mode
configured configured; LTE operating
900 MHz: UMTS S2/2/2, in the 1800 MHz frequency
GSM S2/2/2, 1T2R band, three sectors
configured
900 MHz: UMTS S2/2/2,
GSM S2/2/2, 1T2R
1800 MHz: LTE S1/1/1
(1x10 MHz), 1T2R
RF typology GU CPRI MUX GU CPRI MUX + LTE star
topology
Transmission scheme GU co-transmission and GUL co-transmission and
separate service bearers, IP separate service bearers, IP
over Ethernet over Ethernet
IEEE 1588 V2 reference sharing the IEEE 1588 V2

ain on Object Value

l
Globa CnOperator CN Operator name LTE
l
Globa CnOperator CN Operator type CNOPERATOR
l _PRIMARY
Globa CnOperator Mobile Country code 502
l
Globa CnOperator Mobile network code 04
l

Copyright © Huawei

ain on Object Value
l Maintenance Mode

ration Value
Object
Equipment LTE eNodeBFunctio eNodeB ID 49122

n
Baseband MDU Base Band Work GSM-1&UMTS-
Standard 1&LTE_FDD-
1&LTE_TDD-0
Equipment CABINET Cabinet No. 5
Equipment CABINET Cabinet Type VIRTUAL
Equipment SUBRACK Subrack Type PMU
Equipment PMU Cabinet No. 0
Equipment PMU Subrack No. 7
Baseband PMU Slot No. 0
Equipment PMU Manager Cabinet 0
No.
Equipment PMU Manager Subrack 0
No.
Equipment PMU Manager Port No. 0
Equipment PMU Address 4
Equipment PMU Power System Type ETP
Equipment CABINET Cabinet No. 10
Equipment CABINET Cabinet Type BBC
Equipment SUBRACK Cabinet No. 10
Equipment SUBRACK Subrack Type TCU
Equipment TCU Cabinet No. 10
Equipment TCU Subrack No. 8
Equipment TCU Slot No. 0

Copyright © Huawei

ration Value
Object
Equipment TCU Manager Cabinet 0

No.
Equipment TCU Manager Subrack 0
No.
Equipment TCU Manager Port No. 0
Equipment TCU Address 24
Equipment BATTERY Cabinet No. 5
Equipment BATTERY Subrack No. 7
Equipment BATTERY Slot No. 0
Equipment BATTERY Installation Type OUTER
Equipment BATTERY Battery Type VRLA_BAT
CPRI-based RRUCHAIN —— Add three RRU
topology chains to optical
ports 3 through 5
on the board in
slot 6.
RF RRU —— Added one RRU
to position 0 of
each of the newly
added three
chains. The RRUs
work in LO mode.

Object d Value

Transmission SCTPLNK Cabinet 0\0\6
No./Subrack
No./Slot No.
Address
Port No.
Address

Copyright © Huawei

Object d Value

No.
Transmission IPPATH Cabinet 0\0\6
No./Subrack
No./Slot No.
Bearer ID
Blocked
Transmission DEVIP Cabinet 0\0\6
No./Subrack
No./Slot No.
Transmission IPRT Route Index Configure two
IP routes.
Destination IP

Copyright © Huawei

Object d Value
addresses:
125.120.120.1
171.23.36.1
The route type
is set to
NEXTHOP.
Priority

Object d Value

following
antennas:
63:
0,63,0,R0A;0,6
3,0,R0B
64:
0,64,0,R0A;0,6
4,0,R0B
65:
0,65,0,R0A;0,6
5,0,R0B
equipment are
added.
They
correspond to
sectors 63
through 65.
The following
sector antennas

Copyright © Huawei

Object d Value
are used:
63:
0,63,0,R0B,RX
TX_MODE,M
ASTER;0,63,0,
R0A,RXTX_M
ODE,MASTER
64:
0,64,0,R0B,RX
TX_MODE,M
ASTER;0,64,0,
R0A,RXTX_M
ODE,MASTER
65:
0,65,0,R0B,RX
TX_MODE,M
ASTER;0,65,0,
R0A,RXTX_M
ODE,MASTER
are added with
the following
key parameters
and the
corresponding
values:
FrequencyBand
:3
DlEarfcn: 1600
DlBandwidth:
CELL_BW_N5
0
UlBandwidth:
CELL_BW_N5
0
FddTddInd:
CELL_FDD
Transmit and
receive mode:
2T2R
Sector
equipment:
corresponding
to sector
equipment 63
through 65.

Copyright © Huawei
4.13 Example: Mode Transition from LO (FDD) to LO

(FDD+TDD)
This chapter takes the transition from an LTE FDD base station without co-BBP to an LTE
(FDD+TDD) base station as an example. Figure 1.45 shows the hardware configurations
The LMPT cannot be shared by LTE FDD and LTE TDD to form a co-MPT base station. If an LMPT is
used, replace the LMPT with the UMPT, and then perform mode transition. For the operation guide of
replacing the LMPT with the UMPT, see section "Replacing the Main Control Board When No SeGW Is
Deployed" or "Replacing the Main Control Board When an SeGW Is Deployed" in eRAN
Reconfiguration Guide.

Mode LTE FDD LTE (FDD+TDD)

Service LTE FDD, one sector LTE FDD, one sector; LTE TDD, one sector
configuratio 2100 MHz (FDD): LTE 1, 2100 MHz (FDD): LTE 1, 20 MHz, 2T2R
n 20 MHz, 2T2R 2300 MHz (TDD): LTE 1, 20 MHz, 4T4R
BBU The BBU works in LTE The BBU works in LTE only mode. An
only mode. LBBPd2 board is added to slot 2 and the
BBU is configured to support TDD.
RF RRU chain RRU chain. A TDD RRU chain is added on
topology the newly added LBBPd2 board.
Transmissio IP over Ethernet Remains the same.
n scheme
Clock The IEEE 1588 V2 LTE uses the GPS reference clock and the
networking reference clock is used and clock synchronization mode is time
the clock synchronization synchronization. In this scenario, the GPS

Copyright © Huawei
mode is frequency reference clock is used as an example.

synchronization. NOTE
To use the IEEE 1588 V2 reference clock, change
the clock synchronization mode to time
synchronization.
Table 45.2 Common data configuration

Domain Configu MOC Parameter Name Recommended
ration Value
Object
Clock LTE GPS Clock GPS Clock No. 0

Link
Cabinet No. 0
Subrack No. 0
Slot No. 7
Way to Get Position AUTO_SEARCH
TASM Clock Working MANUAL(Manua
Mode l)
CLKSYNCMODE TIME
Selected Clock GPS
Source

ration Value
Object

Subrack No. 0
Slot No. 2
Board Type LBBP
Work Mode TDD
Administrative State UNBLOCKED
CPRI-based RRUCHAIN Chain No. 1

Copyright © Huawei

ration Value
Object
topology Topo Type CHAIN

Backup Mode COLD
Access Type LOCALPORT
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 2
Head Port No. 0
RF module RRU Cabinet No. 0
Subrack No. 61
Slot No. 0
RRU Topo Position TRUNK
RRU Chain No. 1
RRU Position 0
RRU type LRRU
RRU Name TDD_RRU1
Administrative State UNBLOCKED
VSWR alarm post- OFF
processing switch
VSWR alarm post- 30
processing
threshold(0.1)
VSWR alarm 20
threshold(0.1)
RF Unit Working TDL
Mode
Number of RX 4
channels
Number of TX 4
channels
Frequency Min 5000
Bandwidth(kHz)
Low Current Protect Enable
Switch

Copyright © Huawei

Object Name d Value
Baseband LTE SECTOR Sector ID 1

Sector Name sector_1
Sector Antenna 0, 61, 0, R0A;
0, 61, 0, R0B
0, 61, 0, R0C;
0, 61, 0, R0D
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Sector 0,61,0,R0A,RX
Equipment TX_MODE,M
Antenna ASTER;0,61,0,
R0B,RXTX_M
ODE,MASTER
;0,61,0,R0C,RX
TX_MODE,M
ASTER;0,61,0,
R0D,RXTX_M
ODE,MASTER
Radio Cell Local Cell ID 1
Cell Name 1
Csg indicator BOOLEAN_FA
LSE
Uplink cyclic NORMAL_CP
prefix length
Downlink NORMAL_CP
cyclic prefix
length
Frequency band 40
Uplink NOT_CFG
EARFCN
indication
Downlink 38900
EARFCN
Uplink CELL_BW_N1
bandwidth 00
Downlink CELL_BW_N1

Copyright © Huawei

Object Name d Value
bandwidth 00
Cell ID 1
Physical cell ID 1
Cell active state CELL_ACTIV
E
Cell admin state CELL_UNBLO
CK
Cell FDD TDD CELL_TDD
indication
Subframe SA1
assignment
Special SSP5
subframe
patterns
Cell specific dB0
offset(dB)
Frequency dB0
offset(dB)
Root sequence 1
index
High speed flag LOW_SPEED
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
Ue max power NOT_CFG
allowed
configure
indicator
Flag of Multi- BOOLEAN_FA
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
Air Cell Flag BOOLEAN_FA

Copyright © Huawei

Object Name d Value
LSE
Cell 4T4R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
Intra Frequency BOOLEAN_TR
RAN Sharing UE
Indication
Baseband Cell sector Local cell ID 1
equipment
Sector 1
equipment ID
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
Radio CellOp Local cell ID 1
Local tracking 1
area ID
Cell reserved CELL_NOT_R
for operator ESERVED_FO
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
MME configure CELL_MME_C
number FG_NUM_0
Operator Ue 16
Number
Ratio(%)

Copyright © Huawei
4.14 Example: Mode Transition from LO (TDD) to LO

(FDD+TDD)
This chapter takes the transition from an LTE TDD base station without co-BBP to an LTE
(FDD+TDD) base station as an example. Figure 1.46 shows the hardware configurations
The LMPT cannot be shared by LTE FDD and LTE TDD to form a co-MPT base station. If an LMPT is
used, replace the LMPT with the UMPT, and then perform mode transition. For the operation guide of
replacing the LMPT with the UMPT, see section "Replacing the Main Control Board When No SeGW Is
Deployed" or "Replacing the Main Control Board When an SeGW Is Deployed" in eRAN
Reconfiguration Guide.

Mode LTE TDD LTE (FDD+TDD)

Service LTE TDD, one sector LTE FDD, one sector; LTE TDD, one sector
configuratio 2300 MHz (TDD): LTE 1, 2300 MHz (TDD): LTE 1, 20 MHz, 4T4R
n 20 MHz, 4T4R 2600 MHz (FDD): LTE 1, 20 MHz, 2T2R
BBU The BBU works in LTE The BBU works in LTE only mode. An
only mode. LBBPd2 board is added to slot 2 and the
BBU is configured to support FDD.
RF RRU chain RRU chain. An FDD RRU chain is added on
topology the newly added LBBPd2 board.
Transmissio IP over Ethernet Remains the same.
n scheme
Clock LTE uses the GPS reference Remains the same.
networking clock and the clock
synchronization mode is
time synchronization. In
this scenario, the GPS
reference clock is used as
an example.

Copyright © Huawei
NOTE
The LTE TDD mode supports
GPS/RGPS, IEEE1588 V2 or
1PPS+TOD reference clock.

ration Value
Object

BBP Subrack No. 0
BBP Slot No. 2
BBP Board Type LBBP
BBP Work Mode FDD
CPRI-based RRUCHAIN Add an RRU to
topology optical port 0 on
the newly added
baseband
processing board.
RF module RRU Cabinet No. One RRU in
Subrack No. subrack 61 is
added to the new
Slot No. RRU chain.
RRU RRU type LRRU
RRU RF Unit Working LO
Mode
RRU Number of RX Actual number of
channels transmit and
Number of TX receive antennas
channels used by RRUs.
For example, 2.

Object Name d Value
Baseband LTE SECTOR Sector ID 1

SECTOR Sector Antenna 0, 61, 0, R0A;
0, 61, 0, R0B

Copyright © Huawei

Object Name d Value
SECTOREQM Sector Add one sector

Equipment ID equipment
Sector ID corresponding
to the newly
added sector. 1
is an example.
SECTOREQM Sector 0,61,0,R0A,RX
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;0,61,0,R0C,RX
TX_MODE,M
ASTER;0,61,0,
R0D,RXTX_M
ODE,MASTER
Cell Name 1
Cell ID 1
Physical cell ID 1
FrequencyBand 7
DlEarfcn 3000
DlBandwidth CELL_BW_N1
00
UlBandwidth CELL_BW_N1
00
FddTddInd CELL_FDD
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Root sequence 1
index
EUCELLSECT Local cell ID Corresponding
OREQM Sector to the cell and
equipment ID sector
equipment
CellOp Local tracking 1
area ID

Copyright © Huawei

Object Name d Value

R_OP
CnOperatorTa Local tracking 1
area ID
CN Operator ID 0
Tracking area 11
code
4.15 Example: Mode Transition from G*U*L(F) to

G*U*L(FT)
This chapter takes the transition from a G*U*L(F) co-MPT base station to a G*U*L(F+T) co-
MPT base station as an example. Figure 1.47 shows the hardware configurations before and
after mode transition. Figure 1.48 shows the transmission networking before and after mode
transition.

Copyright © Huawei
Figure 1.48 Transmission networking before and after mode transition

Mode GSM, UMTS, and LTE FDD GSM, UMTS, LTE FDD, and LTE TDD
triple-mode quadruple-mode
configurati the 900 MHz frequency band; MHz frequency band with three sectors
on GSM and LTE operating in the configured; GSM and LTE operating in
1800 MHz frequency band with the 1800 MHz frequency band with three
three sectors configured sectors configured; LTE TDD operating in
900 MHz: GSM S2/2/2/; UMTS the 2300 MHz frequency band with three
S2/2/2, 1T2R sectors configured

Copyright © Huawei
1800 MHz: GSM S2/2/2; LTE 900 MHz: GSM S2/2/2/; UMTS S2/2/2,
S1/1/1, 2T2R 1T2R
1800 MHz: GSM S2/2/2, LTE S1/1/1,
2T2R
2300 MHz: TDD S1/1/1 (1 x 20 MHz),
4T4R
BBU GUL co-MPT co-BBU GULT co-MPT and GUL co-BBU
RF Star topology with CPRI MUX Star topology with CPRI MUX deployed
topology deployed for GU and GL for GU and GL, and star topology for LTE
TDD
Transmissi GSM and UMTS co- Remains the same.
on scheme transmission through backplane
interconnection and connected
to LTE, IP over Ethernet
Clock IEEE 1588 V2 reference clock GULT uses the GPS reference clock and
networkin and GUL common clock The the clock synchronization mode is time
g frequency synchronization mode synchronization. For the clock changes,
is configured. see the following descriptions.
1. When planning mode transition from G*U*L(F) to G*U*L(F+T), pay attention to the
following:
 RF planning
LTE FDD and LTE TDD cannot share RF modules. Add LTE TDD RF modules during mode
transition.
 Antenna and feeder networking
 In F+T scenarios, intermodulation interference and spurious interference may occur on
an antenna working in LTE FDD and LTE TDD modes. It is recommended that LTE
FDD and LTE TDD use separate antennas and feeders, and therefore LTE TDD antennas
must be added.
 Clock planning
LTE TDD basic services require time synchronization. After mode transition, time
synchronization instead of frequency synchronization must be used. That is, the base station
uses a GPS clock source instead of an IEEE1588 V2 clock source as the system clock.
 Baseband planning
An LTE TDD baseband processing board must be added during mode transition if LTE TDD
is added.
 CPRI-based topology
LTE TDD RF modules are added. LTE TDD uses the star topology and no CPRI connection
reconstruction is required.
 Transmission networking planning

Copyright © Huawei
Co-transmission is used before and after mode transition. Therefore, transmission

reconstruction is not required.
2. During mode transition from G*U*L(F) to G*U*L(F+T), consolidate LTE FDD and LTE
TDD licenses. For detailed operations, see EGD-LTE License Guide for GTS Engineers
(ESDP).
3. Check whether the status of LTE TDD cells is normal after mode transition from G*U*L(F)
to G*U*L(F+T). For detailed operations, see 3900 Series Base Station Commissioning Guide.

ain on Object Value
Clock LTE GPS GPS Clock No. 0

Clock GPS Cabinet No. 0/1/0
Subrack No.
Slot No.
Clock GPS Way to Get Position AUTO_SEARC
H
Clock GPS GPS Work Mode GPS
Clock GPS Mobile network code 04
Clock TASM Selected Clock Source GPS
Clock TASM Clock Synchronization TIME
Mode
Clock TASM GSM Frame Sync OFF
Switch

ration Value
Object
Equipment LTE USCU Cabinet No. 0

Equipment USCU Subrack No. 1
Equipment USCU Slot No. 0

Copyright © Huawei

ration Value
Object
Equipment USCU Board Type LMPT

Cabinet Type 1
Cabinet Type:
BTS3900
Subrack 11: FMU
Subrack 4: RFU
fiber optic cables
through optical
ports 3, 4, and 5
on the baseband
board.
RF module RFU Cabinet No. One RRU is added
Subrack No. to the new RRU
chain.
Slot No.
Working mode:
TDL
feeder
feeder
feeder
feeder
Antenna and RET Control Port Cabinet
feeder Cabinet No. No./Subrack
Control Port No./Slot No. of
Subrack No. the three new

Copyright © Huawei

ration Value
Object
Control Port Slot RRUs

No.
feeder
feeder
Antenna and RETSUBUNIT Connect Port 1 Connected to
feeder Cabinet No. channels A and B
of the three RRUs

Object Name d Value
Baseband LTE SECTOR Sector ID Three sectors

are added.
The sector IDs
are 0, 1, and 2.
Sector Name Three sectors
are added. The
sector names
are Sector1,
Sector2, and
Sector3.
Sector Antenna 0:
0,60,0,R0A;0,6
0,0,R0B
1:
0,61,0,R0A;0,6
1,0,R0B
2:
0,62,0,R0A;0,6
2,0,R0B
Baseband SECTOREQM Sector Three pieces of
Equipment ID sector
equipment are
added.
They
correspond to
sectors 0
through 2. The

Copyright © Huawei

Object Name d Value
sector
equipment IDs
are 3, 4, and 5.
Sector ID Sector ID:0,1,2
Sector 3:
Equipment 0,60,0,R0B,RX
Antenna TX_MODE,M
ASTER;0,60,0,
R0A,RXTX_M
ODE,MASTER
4:
0,61,0,R0B,RX
TX_MODE,M
ASTER;0,61,0,
R0A,RXTX_M
ODE,MASTER
5:
0,62,0,R0B,RX
TX_MODE,M
ASTER;0,62,0,
R0A,RXTX_M
ODE,MASTER
Radio Cell FrequencyBand Three LTE cells
are added with
the following
key parameters
and the
corresponding
values:
FrequencyBand
: 38
DlEarfcn 38150
DlBandwidth CELL_BW_N2
5
UlBandwidth CELL_BW_N2
5
FddTddInd CELL_TDD
Cell 4T4R
transmission
and reception
mode
Work mode UL_DL
Radio CellOp Local tracking Add the

Copyright © Huawei

Object Name d Value
area ID following for

cells 4 and 5:
Local tracking
area ID: 4 and 5
R_OP
Radio CnOperatorTa Local tracking Add the
area ID following for
cells 4 and 5:
Local tracking
area ID: 4 and 5
CN Operator ID 0
Tracking area 4 and 5
code
4.16 Example: Mode Transition from GO to G&L(M)

This chapter takes the transition from a GSM base station (GBTS) to a G(GBTS)&L(M)
separate-MPT base station with co-BBP as an example. Figure 1.49 shows the details.
In this scenario, separate-MPT CPRI MUX is used. New main control board and baseband processing
board that work on NB-IoT are added. The UBBP board is connected to the CPRI fiber optic cables.

Copyright © Huawei

Mode GBTS G(GBTS)&L(M)

Service GSM 3 TRXs GSM 3 TRXs
configurati L(M) 3 cells
on
BBU The BBU works in GSM GSM and NB-IoT share a BBU. The baseband
only mode. processing board and main control board that
work in NB-IoT are added in slots 3 and 7,
respectively.
RF RRU chain If the module supports NB-IoT, the CPRI
topology MUX topology is used and the baseband
processing board that works in NB-IoT
provides the CPRI port. If the module does
not support NB-IoT, change the module.
Transmissi GO transmission through GL co-transmission through backplane
on scheme panel, IP over Ethernet interconnection with the LTE port connected

Copyright © Huawei
to the transport network, IP over Ethernet

Clock The IEEE 1588 V2 The IEEE 1588 V2 reference clock is
networking reference clock is used and configured on the LTE side and can be shared
the clock synchronization by GSM. The clock synchronization mode is
mode is frequency frequency synchronization.
synchronization.

ain on Object Value

l
CN Operator name LTE
CN Operator type CNOPERATOR
_PRIMARY
Mobile Country code 502
Mobile network code 04
NTPCP IPv4 Address of NTP 10.141.42.22
Server
Synchronization Period 1
TASM Clock Working Mode MANUAL
Clock Source No. 0
Selected Clock Source IPCLK
Clock Synchronization FREQ
Mode
Quality Level QL_PRC
IPCLKLNK Link No. 0
Protocol Type PTP
Cabinet No./Subrack Corresponding
main control
board
Server IPv4 170.179.179.34

Copyright © Huawei

ain on Object Value
Client IPv4 160.70.7.10

Domain 0
l Maintenance Mode
missi
on Cabinet No./Subrack Corresponding
main control
board
Subboard Type BASE_BOARD

ration Value
Object

Subrack No. 0
Slot No. 7
Board Type UMPT
BBP BBP Cabinet No. 0
Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Base Band Work NBIOT-1
Standard
SUBRACK Cabinet No. Cabinet No.: 0

topology
Topo Type CHAIN

Copyright © Huawei

ration Value
Object
Backup Mode COLD

Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 3
Head Port No. 0
Subrack No. 60
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RF Unit Working GM
Mode
Number of RX 2
channels
Number of TX 2
channels
Antenna and RET Device No. 0
feeder
RET Type SINGLE_RET
Polar Type DUAL
Antenna Scenario REGULAR
Control Port 0
Cabinet No.
Control Port 60
Subrack No.
Control Port Slot 0
No.
RETSUBUNIT Device No. 0
Subunit No. 1
Connect Port 1 0
Cabinet No.

Copyright © Huawei

ration Value
Object
Connect Port 1 60
Subrack No.
Connect Port 1 Slot 0
No.

Object d Value

Cabinet The main
transmission
ports.
First Local IP 160.70.7.10
Address
Local SCTP 2913
Port No.
First Peer IP 125.120.120.1
Address
Peer SCTP Port 2910
No.
CPBEARER CP Bear No. 0
Flag MASTER
Bear Type SCTP
Link No. 0
IPPATH Path ID 0
Cabinet Corresponding
board
Port Type ETH
Port No. 0
Path Type ANY

Copyright © Huawei

Object d Value
Local IP 160.70.7.10
Peer IP 171.23.36.1
S1Interface S1 Interface ID 0
S1 Interface CP 0
Bearer ID
CN Operator ID 0
MME Release Release_R8
S1 Interface Is FALSE
Blocked
OMCH Standby Status MASTER
Local IP Base Station
Transport
Data\OM
Plane\*OmCh
LocalIP
Local Mask Base Station
Transport
Data\OM
Plane\*OmCh
LocalMask
Peer IP Base Station
Transport
Data\OM
Plane\OmCh
DstIP
Peer Mask Base Station
Transport
Data\OM
Plane\OmCh
DstMask
DEVIP Cabinet Corresponding
board
Port Type ETH
Port No. 0
IP Address 160.70.7.10
Mask 255.255.0.0

Copyright © Huawei

Object d Value
TUNNEL N/A Source: UMPT

Destination:
GTMU
Both tunnels are
for downlink
transmission.
IPRT Route Index Configure six
IP routes.
The functions
are as follows:
OMCH
IPCLK
TO GBTS
TO SG-W
TO MME
TO BSC
Set the route
type to Next
Hop for all the
IP routes except
for the routes to
the GBTS and
specify the IP
addresses as
planned.
Set the route
type to IF and
port type to
TUNNEL for
IP routes to
tunnels.
VLANMAP Next Hop IP 160.70.0.1
Mask 255.255.0.0
VLAN Mode SINGLEVLAN
VLAN ID 446
Set VLAN DISABLE
Priority
DHCPSVRIP DHCP Server Set the DHCP
address to the
IP address of
the U2000 and
MBSC for

Copyright © Huawei

Object d Value
deployment.
DHCPRELAY DHCP Relay ENABLE
SWITCH Switch
DHCPSW OMCH Auto- ENABLE
Establishment
Switch
Vlanscan DISABLE
Switch

Object Name d Value
BBP LTE SECTOR Sector ID 1

Sector Antenna 0,60,0,R0A;0,6
0,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Cell ID 1

Copyright © Huawei

Object Name d Value
Physical cell ID 1
E
CK
Cell FDD TDD CELL_FDD
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
BBP Cell sector Local cell ID 1
equipment
Sector 1
equipment ID

Copyright © Huawei

Object Name d Value
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
Radio MMECAPINF MME 0
O Capability
Configuration
ID
S1CfgType S1INTERFACE
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
CNOPERATO Local tracking 1
RTA area ID
CN Operator ID 0
Tracking area 1
code
NB-IoT TA BOOLEAN_TR
Flag UE
CellOp Local cell ID 1
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16

Copyright © Huawei

Object Name d Value
Number
Ratio(%)
PRB Local Cell ID 1
PRB ID 0
Deployment STAND_ALO
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset
To bind PRBs to sector equipment on the NE side, run the MML command
PRBTOEUCELLSECTOREQM.
To bind PRBs to sector equipment on the CME side, run the PRB ID LIST command.

Domain Configura MOC Parameter Recommende
tion d Value
Object
RF module GSM BTSRXUBP Working Standard GSM_AND_N

BIOT
Node: Change
the working
mode of RRUs
to GM.
CPRI-based GSM BTSRXUCHAIN Access Type Set the Access
topology Type column in
the BTS RXU
Chain area to
PEERPORT
and the Head
Board No.
column to that
of the UBBP in

Copyright © Huawei
Domain Configura MOC Parameter Recommende

tion d Value
Object
slot 3.
Table 50.7 BSC configuration

Object d Value

ACE
Port No. 0
No./slot No. of
the GTMU
IP Index 0
IP Mask 255.255.255.0
BTS Inner IP NO
Switch
BTSIP BTS LOGICIP
Communication
Type
BTS IP 88.200.8.37
BSC IP 40.13.3.200
BTS MultiIP NO
Switch
BTSESN BTS Interface 21021127229T
Board Bar Code AB020269
1
OM Bear Board BACKBOARD
BTSTUNNEL N/A Source: GTMU
Destination:
UMPT
The tunnel is
used for
backplane
transmission
interconnection.

Copyright © Huawei

Object d Value
BTSIPRT Route Index 0

Destination IP 40.13.3.200
Address
Destination 255.255.255.25
Address Mask 5
Route Type OUTIF
Cabinet Cabinet
the GTMU
Interface Type TUNNEL
BTSCLK Clock Type PEER_CLK
Peer Mode LTE
IPRT Subrack No. 0
Slot No. 14
Destination IP Set the
address destination IP
addresses to the
IP addresses of
the GBTS:
88.200.8.37
160.70.7.10
Destination 255.255.255.25
address mask 5
Next hop type Gateway
Forward route 40.13.3.1
address
Priority HIGH
4.17 Example: Mode Transition from UO to U&L(M)

This chapter takes the transition from a UO base station to a UO&L(M) separate-MPT station
with co-BBP as an example. Figure 1.51 shows the details.

Copyright © Huawei
In this scenario, separate-MPT CPRI MUX is used. New main control board and baseband processing
board that work on NB-IoT are added. The UMTS board is connected to the CPRI fiber optic cables.

Copyright © Huawei

Mode UO UO&L(M)
Service UO 3 sectors UO 3 sectors
on
BBU The BBU works in UMTS UMTS and NB-IoT share a BBU. The
only mode. baseband processing board and main control
board that work in NB-IoT are added in slots
3 and 6, respectively.
topology MUX topology is used and the CPRI cable
connections remain unchanged. If the module
does not support NB-IoT, change the module.
Transmissi UO transmission through UL co-transmission through backplane
on scheme panel, IP over Ethernet interconnection with the UMTS port
connected to the transport network, IP over
Ethernet
networking reference clock is used and configured on the UMTS side and can be
the clock synchronization shared by LTE. The clock synchronization
mode is frequency mode is frequency synchronization.
synchronization.

ain on Object Value

l
_PRIMARY
Server

Copyright © Huawei

ain on Object Value
Clock Source No. 0

Selected Clock Source PEERCLK
missi
main control
board

ration Value
Object

Subrack No. 0
Slot No. 7
Board Type UMPT
Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Standard

topology
Topo Type CHAIN
Backup Mode COLD

Copyright © Huawei

ration Value
Object
Access Type PEERPORT

Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 2
Head Port No. 0
Subrack No. 60
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RF Unit Working UM
Mode
Number of RX 2
channels
Number of TX 2
channels
feeder
RET Type SINGLE_RET
Polar Type DUAL
Control Port 0
Cabinet No.
Control Port 60
Subrack No.
Control Port Slot 0
No.
Subunit No. 1
Connect Port 1 0
Cabinet No.
Connect Port 1 60

Copyright © Huawei

ration Value
Object
Subrack No.
No.

Object d Value
Transmission LTE SCTPLNK Cabinet A new added

Address
Local SCTP 2913
Port No.
Address
Peer SCTP Port 2910
No.
Flag MASTER
Bear Type SCTP
Link No. 0
IPPATH Path ID 0
No./slot No. of
the UMPT
Port Type ETH
Port No. 0
Path Type ANY
Local IP 160.70.7.10
Peer IP 171.23.36.1

Copyright © Huawei

Object d Value
S1 Interface CP 0
Bearer ID
CN Operator ID 0
Blocked
Control Mode MANUAL_MO
DE
OMCH Standby Status MASETR
Local IP 160.70.7.10
Local Mask 255.255.0.0
Peer IP 10.141.42.22
Peer Mask 255.255.0.0
No./slot No. of
the UMPT
Port Type ETH
Port No. 0
Mask 255.255.0.0
IPRT Route Index Configure three
IP routes.
The functions
are as follows:
OMCH
TO SG-W
TO MME
Set the route
type to Next
Hop and
specify the IP
addresses as
planned.

Copyright © Huawei

Object d Value

Mask 255.255.0.0
VLAN ID 446
Set VLAN DISABLE
Priority

Object Name d Value

0,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Cell ID 1
Physical cell ID 1

Copyright © Huawei

Object Name d Value

E
CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID

Copyright © Huawei

Object Name d Value
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
O Capability
Configuration
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
RTA area ID
CN Operator ID 0
Tracking area 1
code
Flag UE
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16

Copyright © Huawei

Object Name d Value
Number
Ratio(%)
PRB Local Cell ID 1
PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset

ion Object ed Value
RF module UMTS RRU RF Unit Working UM

Mode
4.18 Example: Mode Transition from G&U to G&[U*L(M)]

This chapter takes the transition from a G(GBTS)&U separate-MPT base station to a
G(GBTS)&[U*L(M)] hybrid-MPT base station with co-BBP as an example. Figure 1.53
shows the details.

Copyright © Huawei
In this scenario, hybrid-MPT CPRI MUX is used. New baseband processing board that works in NB-IoT
are added. The NB-IoT board is connected to the CPRI fiber optic cables. UM co-MPT is applied.

Mode G(GBTS)&U G(GBTS)&[U*L(M)]

Copyright © Huawei

configurati UMTS 3 cells UMTS 3 cells
on
L(M) 3 cells
BBU GSM and UMTS sharing GSM, UMTS, and NB-IoT share a BBU. The
the same BBU baseband processing board that works in NB-
IoT is added in slot 3. Co-MPT for NB-IoT
and UMTS is applied.
topology MUX topology is used and the baseband
processing board that works in NB-IoT
provides the CPRI port. If the module does
not support NB-IoT, change the module.
Transmissi GSM E1 transmission, GSM E1 transmission remains unchanged.
on scheme UMTS transmission UMTS and NB-IoT co-transmission through
through panel, IP over IP over Ethernet
Ethernet
Clock GSM using the E1 GSM using the E1 reference clock, UMTS
networking reference clock, UMTS and NB-IoT sharing the GSM reference clock
sharing the GSM reference
clock
Data plan filling of Conversion Plan Data File SRANXX involved in the transition from a
separate-MPT UMTS only base station to a co-MPT UMTS only base station
2. Fill in the SitePlanning page.



n Object d Value
CPRI-based GSM BTSRXUCHAI Access Type Set the Access

topology N Type column in
the BTS RXU

Copyright © Huawei

n Object d Value
Chain area to
PEERPORT
and the Head
Board No.
column to that
of the UBBP in
slot 3.
RF module BTSRXUBP Working GSM_AND_N
Standard BIOT
Node: Change
the working
mode of RRUs
to GM.

ion Object Value

_PRIMARY
Mobile Country 502
code
Mobile network 04
code
Address (To MME)
USERPLANEP Peer IP Address 171.23.36.1
EER (To S-GW)
N Maintenance Mode

ration Value
Object

Copyright © Huawei

ration Value
Object
Subrack No. 0
Slot No. 7
Board Type UMPT
Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Standard

topology
Topo Type CHAIN
Backup Mode COLD
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 3
Head Port No. 0
Subrack No. 60
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RF Unit Working GM

Copyright © Huawei

ration Value
Object
Mode
Number of RX 2
channels
Number of TX 2
channels
feeder
RET Type SINGLE_RET
Polar Type DUAL
Control Port 0
Cabinet No.
Control Port 60
Subrack No.
Control Port Slot 0
No.
Subunit No. 1
Connect Port 1 0
Cabinet No.
Connect Port 1 60
Subrack No.
No.

Object d Value

Cabinet The main
transmission
ports.
Address

Copyright © Huawei

Object d Value
Local SCTP 2913

Port No.
Address
Peer SCTP Port 2910
No.
Flag MASTER
Bear Type SCTP
Link No. 6
IPPATH Path ID 6
board
Port Type ETH
Port No. 0
Path Type ANY
Local IP 160.70.7.10
Peer IP 171.23.36.1
S1 Interface CP 6
Bearer ID
CN Operator ID 0
Blocked
board
Port Type ETH
Port No. 0

Copyright © Huawei

Object d Value
Mask 255.255.0.0
IPRT Route Index Configure two
IP routes.
Destination IP
addresses:
171.23.36.1
125.120.120.1
The route type
is set to
NEXTHOP.
Mask 255.255.0.0
VLAN ID 446
Set VLAN DISABLE
Priority

Object Name d Value

0,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1

Copyright © Huawei

Object Name d Value

LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Cell ID 1
Physical cell ID 1
E
CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE

Copyright © Huawei

Object Name d Value
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
O Capability
Configuration
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
RTA area ID
CN Operator ID 0
Tracking area 1
code
Flag UE
Local tracking 1
area ID

Copyright © Huawei

Object Name d Value

R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16
Number
Ratio(%)
PRB Local Cell ID 1
PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset
4.19 Example: Mode Transition from GO&L(F) to

G&L(FM)
This chapter takes the transition from a G(GBTS)&L(F) separate-MPT base station to a
G(GBTS)&L(FM) separate-MPT base station with co-BBP as an example. Figure 1.55 shows
the details.

Copyright © Huawei
The new modules work on the 900 MHz frequency band, and support GSM and NB-IoT.

Copyright © Huawei

Mode G&L(F) G&L(FM)

configurati L(F) 3 cells L(F) 3 cells
on
L(M) 3 cells
BBU GL co-BBU GL(FM) co-BBU

Copyright © Huawei
RF RRU chain Adds the RRU and CPRI cable connection.

topology
Transmissi IP over Ethernet Remains the same.
on scheme
Clock The IEEE 1588 V2 Remains the same.
networking reference clock is used and
the clock synchronization
mode is frequency
synchronization.

n Object d Value
CPRI-based GSM BTSRXUCHAI Chain No. 1

topology N
Topo Type CHAIN
Head Cabinet 0
No.
Head Subrack 0
No.
Head Slot No. 3
Head Port No. 0
RF module BTSRXUBRD Board Type MRRU
RXU Set this
Specification parameter based
on the RRU
type.
Cabinet No. 0
Subrack No. 60
Slot No. 0
RXU Name RRU_GM
RXU Chain No. 1
RXU Board 1
Position

Copyright © Huawei

n Object d Value
BTSRXUBP Cabinet No. 0

Subrack No. 60
Slot No. 0
RXU Board MRRU
Type
Working GSM_AND_N
Standard BIOT

Object d Value
Radio GSM GSM CELL BTS Name Set the

parameter based
on the network
plan.
Cell Name GCELL_NBIO
T
Freq. Band GSM900
MCC Set the
parameter based
on the network
plan.
MNC Set the
parameter based
on the network
plan.
Cell LAC Set the
parameter based
on the network
plan.
Cell CI Set the
parameter based
on the network
plan.
TRX Info Frequency of 55
BCCH
GBTS Power 10W
Type(w)
Power Level 0

Copyright © Huawei

Object d Value
Receive Mode MAINDIVERS

ITY
Send Mode NOCOMB
BCCH Type MBCCH
Number of 0
PDCH
Number of 1
SDCCH
Number of 0
BCH
Cell-OSP OSP Code Set the
Mapping parameter based
on the network
plan.
Binding Board No. 0_60_0_1
between
Logical TRX TRX Board 0
and Channel on Pass No.
TRX Board
Antenna Pass A
No

ion Object Value

_PRIMARY
Mobile Country 502
code
Mobile network 04
code
Address (To MME)
EER (To S-GW)

Copyright © Huawei

ion Object Value

N Maintenance Mode

ration Value
Object

Subrack No. 0
Slot No. 7
Board Type UMPT
Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Standard

topology
Topo Type CHAIN
Backup Mode COLD
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 3
Head Port No. 0

Copyright © Huawei

ration Value
Object
Subrack No. 60
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RF Unit Working GM
Mode
Number of RX 2
channels
Number of TX 2
channels
feeder
RET Type SINGLE_RET
Polar Type DUAL
Control Port 0
Cabinet No.
Control Port 60
Subrack No.
Control Port Slot 0
No.
Subunit No. 1
Connect Port 1 0
Cabinet No.
Connect Port 1 60
Subrack No.
No.

Copyright © Huawei

Object d Value

Cabinet The main
transmission
ports.
Address
Local SCTP 2913
Port No.
Address
Peer SCTP Port 2910
No.
Flag MASTER
Bear Type SCTP
Link No. 6
IPPATH Path ID 6
board
Port Type ETH
Port No. 0
Path Type ANY
Local IP 160.70.7.10
Peer IP 171.23.36.1
S1 Interface CP 6
Bearer ID
CN Operator ID 0

Copyright © Huawei

Object d Value
Blocked
board
Port Type ETH
Port No. 0
Mask 255.255.0.0
IP routes.
Destination IP
addresses:
171.23.36.1
125.120.120.1
The route type
is set to
NEXTHOP.
Mask 255.255.0.0
VLAN ID 446
Set VLAN DISABLE
Priority

Object Name d Value

0,0,R0B;
SECTOREQM Sector 1
Equipment ID

Copyright © Huawei

Object Name d Value
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Cell ID 1
Physical cell ID 1
E
CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator

Copyright © Huawei

Object Name d Value
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
O Capability
Configuration
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
RTA area ID
CN Operator ID 0

Copyright © Huawei

Object Name d Value
Tracking area 1
code
Flag UE
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16
Number
Ratio(%)
1. Standalone

Object Name d Value
Radio LTE PRB Local Cell ID 1

PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN

Copyright © Huawei

Object Name d Value
Downlink NEG_0DOT5
Frequency
Offset
2. Guardband

Object Name d Value

PRB ID 0
Deployment GUARD_BAN
Mode D
Frequency Band 8
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_2
Frequency
Offset
LTE Bandwidth LTE_SYSTEM
_BW_10M
LTE Downlink 3597
EARFCN
3. In-band

Object Name d Value

PRB ID 0
Deployment IN_BAND
Mode
Frequency Band 8
Uplink CFG
EARFCN

Copyright © Huawei

Object Name d Value
Configuration
Indicator
Uplink 21469
EARFCN
Uplink NEG_2
Frequency
Offset
Downlink 3513
EARFCN
Downlink POS_0
Frequency
Offset
Related LTE 0
Cell ID
Uplink All TRUE
Symbol Send
Flag
CELLRBRESE Local Cell ID 0
RVE
Index 0
RB Reserve NB_DEPLOY
Mode MENT
RB Reserve DOWNLINK_
Type MODE
RB Reserve 4
Start Index
RB Reserve 4
End Index
RVE
Index 1
Mode MENT
RB Reserve UPLINK_MOD
Type E
RB Reserve 0
Start Index
RB Reserve 0
End Index

Copyright © Huawei
4.20 Example: Mode Transition from U&L(F) to U&L(FM)

This chapter takes the transition from a U&L(F) separate-MPT base station to a U&L(FM)
separate-MPT base station with co-BBP as an example. Figure 1.57 shows the details.
The inventory modules work on the 800 MHz frequency band, and support LTE and NB-IoT.

Copyright © Huawei

Mode U&L(F) U&L(FM)

Service UMTS 3 cells UMTS 3 cells
configurati L(F) 3 cells L(F) 3 cells
on
L(M) 3 cells
BBU UL co-BBU UL (FM) co-BBU
topology cable connections remain unchanged. If the
module does not support NB-IoT, change the
module.
on scheme

Copyright © Huawei
Clock GPS clock Remains the same.

networking

ration Value
Object

Link
Cabinet No. 0
Subrack No. 0
Slot No. 7
Mode l)
CLKSYNCMODE TIME
Selected Clock GPS
Source

ration Value
Object
BBP LTE BBP Cabinet No. 0

Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Base Band Work LTE_FDD-
Standard 1&NBIOT-1
Administrative UNBLOCKED
State
topology
Topo Type CHAIN
Backup Mode COLD

Copyright © Huawei

ration Value
Object

Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 2
Head Port No. 0
Subrack No. 61
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RRU Name FDDNB_RRU
State
processing switch
VSWR alarm post- 30
processing
threshold(0.1)
VSWR alarm 20
threshold(0.1)
RF Unit Working LM
Mode
Number of RX 2
channels
Number of TX 2
channels
Frequency Min 5000
Bandwidth(kHz)
Switch

Copyright © Huawei

Object Name d Value

1,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Coverage Level COVERAGE_L
Type EVEL_0-1
Cell ID 1
Physical cell ID 1
E
CK
indication
Root sequence 1
index

Copyright © Huawei

Object Name d Value
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
O Capability
Configuration
ID
_CFG
S1 Interface ID 0

Copyright © Huawei

Object Name d Value
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
RTA area ID
CN Operator ID 0
Tracking area 1
code
Flag UE
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16
Number
Ratio(%)
1. Standalone

Object Name d Value

PRB ID 0

Copyright © Huawei

Object Name d Value
Mode NE
Frequency 20
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 6300
EARFCN
Downlink NEG_0DOT5
Frequency
Offset
2. Guardband

Object Name d Value

PRB ID 0
Mode D
Frequency Band 20
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 6252
EARFCN
Downlink NEG_2
Frequency
Offset
_BW_10M
LTE Downlink 6300
EARFCN
3. In-band

Copyright © Huawei

Object Name d Value

PRB ID 0
Deployment IN_BAND
Mode
Frequency Band 20
Uplink CFG
EARFCN
Configuration
Indicator
Uplink 24256
EARFCN
Uplink NEG_2
Frequency
Offset
Downlink 6218
EARFCN
Downlink POS_0
Frequency
Offset
Related LTE 0
Cell ID
Uplink All TRUE
Symbol Send
Flag
RVE
Index 0
Mode MENT
Type MODE
RB Reserve 4
Start Index
RB Reserve 4
End Index
RVE
Index 1
Mode MENT

Copyright © Huawei

Object Name d Value
Type E
RB Reserve 0
Start Index
RB Reserve 0
End Index
4.21 Example: Mode Transition from GO to G*L(M)

This chapter takes the transition from a GSM base station (eGBTS) to a G(eGBTS)*L(M) co-
MPT base station with co-BBP as an example. Figure 1.59 shows the details.
The inventory modules work on the 900 MHz frequency band, and support LTE and NB-IoT. A new
baseband processing board that works in NB-IoT needs to be added. Co-MPT reconstruction is required.

Copyright © Huawei

Mode G(eGBTS) G(eGBTS)&L(M)

on
BBU The BBU works in one GM co-BBU
mode.
module.
on scheme
Clock The IEEE 1588 V2 Remains the same.
networking reference clock is used and
the clock synchronization
mode is frequency
synchronization.

Copyright © Huawei

ain on Object Value

l
_PRIMARY
Server

ration Value
Object

Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Standard

topology
Topo Type CHAIN
Backup Mode COLD

Copyright © Huawei

ration Value
Object

Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 2
Head Port No. 0
Subrack No. 60
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RF Unit Working GM
Mode
Number of RX 2
channels
Number of TX 2
channels
feeder
RET Type SINGLE_RET
Polar Type DUAL
Control Port 0
Cabinet No.
Control Port 60
Subrack No.
Control Port Slot 0
No.
Subunit No. 1
Connect Port 1 0
Cabinet No.
Connect Port 1 60

Copyright © Huawei

ration Value
Object
Subrack No.
No.

Object d Value

Address
Local SCTP 2913
Port No.
Address
Peer SCTP Port 2910
No.
Flag MASTER
Bear Type SCTP
Link No. 0
IPPATH Path ID 0
No./slot No. of
the UMPT
Port Type ETH
Port No. 0
Path Type ANY
Local IP 160.70.7.10
Peer IP 171.23.36.1

Copyright © Huawei

Object d Value
S1 Interface CP 0
Bearer ID
CN Operator ID 0
Blocked
DE
Local IP 160.70.7.10
Peer IP 10.141.142.22
Peer Mask 255.255.0.0
No./slot No. of
the UMPT
Port Type ETH
Port No. 0
Mask 255.255.0.0
IP routes.
The functions
are as follows:
OMCH
TO SG-W
TO MME
Set the route
type to Next
Hop and
specify the IP
addresses as
planned.

Copyright © Huawei

Object d Value

Mask 255.255.0.0
VLAN ID 446
Set VLAN DISABLE
Priority

Object Name d Value

0,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Cell ID 1

Copyright © Huawei

Object Name d Value
Physical cell ID 1
E
CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID

Copyright © Huawei

Object Name d Value
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
O Capability
Configuration
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
RTA area ID
CN Operator ID 0
Tracking area 1
code
Flag UE
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16

Copyright © Huawei

Object Name d Value
Number
Ratio(%)
PRB Local Cell ID 1
PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset

Object Name d Value
RF module GSM RRU RF Unit GM

Working Mode
4.22 Example: Mode Transition from UO to U*L(M)

This chapter takes the transition from a UO base station to a U*L(M) co-MPT station with co-
BBP as an example. Figure 1.61 shows the details.

Copyright © Huawei
The inventory modules work on the 900 MHz frequency band, and support LTE and NB-IoT. A new
baseband processing board that works in NB-IoT needs to be added. Co-MPT reconstruction is required.

Copyright © Huawei

Mode UO UO*L(M)
on
BBU The BBU works in one UL(M) co-BBU
mode.
module.
Transmissi IP over Ethernet IP over Ethernet
on scheme
the clock synchronization shared by NB-IoT. The clock synchronization
synchronization.
2. Fill in the SitePlanning page.


Table 62.3 UMTS configuration

n Object d Value
RF module UMTS RRU RF Unit UM

Working Mode

Copyright © Huawei

ion Object Value

_PRIMARY
CnOperator Mobile Country 502
code
CnOperator Mobile network 04
code
Address (To MME)
EER (To S-GW)
N Maintenance Mode

ration Value
Object

Subrack No. 0
Slot No. 7
Board Type UMPT
Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Standard

Copyright © Huawei

ration Value
Object
Subrack No.
Subrack Type Subrack 0:
BBU3900
topology
Topo Type CHAIN
Backup Mode COLD
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 3
Head Port No. 0
Subrack No. 60
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RF Unit Working UM
Mode
Number of RX 2
channels
Number of TX 2
channels
feeder
RET Type SINGLE_RET
Polar Type DUAL
Control Port 0
Cabinet No.
Control Port 60
Subrack No.
Control Port Slot 0

Copyright © Huawei

ration Value
Object
No.
Subunit No. 1
Connect Port 1 0
Cabinet No.
Connect Port 1 60
Subrack No.
No.

Object d Value

Cabinet The main
transmission
ports.
Address
Local SCTP 2913
Port No.
Address
Peer SCTP Port 2910
No.
Flag MASTER
Bear Type SCTP
Link No. 6
IPPATH Path ID 6

Copyright © Huawei

Object d Value
board
Port Type ETH
Port No. 0
Path Type ANY
Local IP 160.70.7.10
Peer IP 171.23.36.1
S1 Interface CP 6
Bearer ID
CN Operator ID 0
Blocked
board
Port Type ETH
Port No. 0
Mask 255.255.0.0
IP routes.
Destination IP
addresses:
171.23.36.1
125.120.120.1
The route type
is set to
NEXTHOP.
Mask 255.255.0.0

Copyright © Huawei

Object d Value
VLAN ID 446
Set VLAN DISABLE
Priority

Object Name d Value

0,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Cell ID 1
Physical cell ID 1
E

Copyright © Huawei

Object Name d Value

CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID
Reference 32767
signal
power(0.1dBm)
Baseband 255

Copyright © Huawei

Object Name d Value
equipment ID
O Capability
Configuration
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
RTA area ID
CN Operator ID 0
Tracking area 1
code
Flag UE
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16
Number
Ratio(%)
PRB Local Cell ID 1

Copyright © Huawei

Object Name d Value
PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset
4.23 Example: Mode Transition from UO to U&L(M) for

China Unicom
This chapter takes the transition from a UO base station to a U&L(M) separate-MPT base
station with co-BBP as an example. Figure 1.63 shows the details.

Copyright © Huawei
The inventory modules work on the 900 MHz frequency band, and support LTE and NB-IoT. New
baseband processing board and main control board that work in NB-IoT needs to be added.

Mode UO UO&L(M)
on
BBU The BBU works in one UL(M) co-BBU
mode.
RF RRU chain The network topology is changed from chain
topology topology to star topology.
Transmissi IP over Ethernet UMTS and NB-IoT independent transmission,
on scheme IP over Ethernet
the clock synchronization shared by LTE. The clock synchronization

Copyright © Huawei
synchronization.

ain on Object Value

l
_PRIMARY
Server
Clock Source No. 0
Selected Clock Source PEERCLK
missi
main control
board

ration Value
Object

Subrack No. 0

Copyright © Huawei

ration Value
Object
Slot No. 6
Board Type UMPT
Subrack No. 0
Slot No. 2
Board Type UBBP
Work Mode FDD
Standard

topology
Topo Type CHAIN
Backup Mode COLD
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 2
Head Port No. 0
Subrack No. 60
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RF Unit Working UM
Mode

Copyright © Huawei

ration Value
Object
Number of RX 2
channels
Number of TX 2
channels
feeder
RET Type SINGLE_RET
Polar Type DUAL
Control Port 0
Cabinet No.
Control Port 60
Subrack No.
Control Port Slot 0
No.
Subunit No. 1
Connect Port 1 0
Cabinet No.
Connect Port 1 60
Subrack No.
No.

Object d Value

Address
Local SCTP 2913
Port No.
Address

Copyright © Huawei

Object d Value
Peer SCTP Port 2910

No.
Flag MASTER
Bear Type SCTP
Link No. 0
IPPATH Path ID 0
No./slot No. of
the UMPT
Port Type ETH
Port No. 0
Path Type ANY
Local IP 160.70.7.10
Peer IP 171.23.36.1
S1 Interface CP 0
Bearer ID
CN Operator ID 0
Blocked
DE
Local IP 160.70.7.10
Peer IP 10.141.42.22
Peer Mask 255.255.0.0

Copyright © Huawei

Object d Value
No./slot No. of
the UMPT
Port Type ETH
Port No. 0
Mask 255.255.0.0
IP routes.
The functions
are as follows:
OMCH
TO SG-W
TO MME
Set the route
type to Next
Hop and
specify the IP
addresses as
planned.
Mask 255.255.0.0
VLAN ID 446
Set VLAN DISABLE
Priority

Object Name d Value

0,0,R0B;
SECTOREQM Sector 1
Equipment ID

Copyright © Huawei

Object Name d Value
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Cell ID 1
Physical cell ID 1
E
CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator

Copyright © Huawei

Object Name d Value
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
O Capability
Configuration
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
RTA area ID
CN Operator ID 0

Copyright © Huawei

Object Name d Value
Tracking area 1
code
Flag UE
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16
Number
Ratio(%)
PRB Local Cell ID 1
PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset

Copyright © Huawei

ion Object ed Value
CPRI-based UMTS RRUCHAIN Chain No. 1

topology Note: Delete
the 900 MHz
module from
link 0 and add
it to link 1.
Topo Type CHAIN
Backup Mode COLD
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 2
Head Port No. 0
Subrack No. 60
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RF Unit Working UM
Mode Note: Modify
the RF module
that works on
900 MHz to
support UMTS
and NB-IoT.
Number of RX 2
channels
Number of TX 2
channels

Copyright © Huawei
4.24 Example: Mode Transition from L(F) to L(FM)

This chapter takes the transition from an L(F) base station to an L(FM) base station with co-
LTE FDD and LTE NB-IoT share an RRU module. If the baseband processing board and main control
board meet the specifications, new hardware or co-MPT reconstruction is not required.
FDD RRU: RRU3953
If a UBBPd board that supports LTE FDD is changed to support LTE FDD and NB-IoT, the UBBPd
board must be reset. FDD-related data is automatically configured in LTE cells, which takes three
minutes.
If an LBBPd board that supports LTE FDD is changed to support LTE FDD and NB-IoT, the LBBPd
board must be reset. FDD-related data is automatically configured in LTE cells, which takes five
minutes.

Mode L(F) L(FM)

Service L(F) 3 cells L(F) 3 cells
on
BBU The BBU works in LTE LTE (FDD) and LTE (NB-IoT) share a BBU.
FDD only mode.
RF RRU chain The CPRI cable connections in a LM base
topology station that share a CPRI port remain
unchanged.
RF power LTE: 2x40 W LTE: 2x40 W, NB-IoT: 2x6 W

Copyright © Huawei

on scheme
networking

ration Value
Object

Link
Cabinet No. 0
Subrack No. 0
Slot No. 7
Mode l)
CLKSYNCMODE TIME
Selected Clock GPS
Source

ration Value
Object

Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Standard 1&NBIOT-1

Copyright © Huawei

ration Value
Object
State
topology
Topo Type CHAIN
Backup Mode COLD
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 3
Head Port No. 0
Subrack No. 61
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RRU Name FDDNB_RRU
State
processing switch
VSWR alarm post- 30
processing
threshold(0.1)
VSWR alarm 20
threshold(0.1)
RF Unit Working LM
Mode
Number of RX 2
channels
Number of TX 2
channels
Frequency Min 5000

Copyright © Huawei

ration Value
Object
Bandwidth(kHz)
Switch

Object Name d Value

1,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Type EVEL_0-1
Cell ID 1
Physical cell ID 1

Copyright © Huawei

Object Name d Value

E
CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID
Reference 32767
signal

Copyright © Huawei

Object Name d Value
power(0.1dBm)
Baseband 255
equipment ID
O Capability
Configuration
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
RTA area ID
CN Operator ID 0
Tracking area 1
code
Flag UE
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16
Number

Copyright © Huawei

Object Name d Value
Ratio(%)
1. Standalone

Object Name d Value

PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset
2. Guardband

Object Name d Value

PRB ID 0
Mode D
Frequency Band 8
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_2

Copyright © Huawei

Object Name d Value
Frequency
Offset
_BW_10M
LTE Downlink 3597
EARFCN
3. In-band

Object Name d Value

PRB ID 0
Deployment IN_BAND
Mode
Frequency Band 8
Uplink CFG
EARFCN
Configuration
Indicator
Uplink 21469
EARFCN
Uplink NEG_2
Frequency
Offset
Downlink 3513
EARFCN
Downlink POS_0
Frequency
Offset
Related LTE 0
Cell ID
Uplink All TRUE
Symbol Send
Flag
RVE
Index 0

Copyright © Huawei

Object Name d Value
Mode MENT
Type MODE
RB Reserve 4
Start Index
RB Reserve 4
End Index
RVE
Index 1
Mode MENT
Type E
RB Reserve 0
Start Index
RB Reserve 0
End Index
Adjust the power as required.
Table 65.5 LTE radio power data configuration

Object Name d Value
Radio LTE PDSCHCFG ReferenceSigna 300

lPwr
Remarks: Set the radio power for NB-IoT to 6 W.

Copyright © Huawei
4.25 Example: Mode Transition from L(T) to L(TM) for

China Mobile
This chapter takes the transition from an L(T) base station to an L(TM) base station with co-
LTE TDD and LTE NB-IoT cannot share an RRU module. New baseband processing board, RRU
module, and antenna system need to be added. Co-MPT reconstruction is not required.
NB-IoT RRU: RRU3953

Mode L(T) L(TM)

Service L(T) 3 cells L(T) 3 cells
on
BBU The BBU works in LTE LTE (TDD) and LTE (NB-IoT) share a BBU.
TDD only mode.
RF RRU chain New RRU, baseband processing board, and
topology CPRI connections are added.
RF power LTE FDD is not supported. NB-IoT: 2x20 W
on scheme
networking

Copyright © Huawei

ration Value
Object

Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Standard
State
topology
Topo Type CHAIN
Backup Mode COLD
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 3
Head Port No. 0
Subrack No. 61
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RRU Name NB_RRU
State
processing switch
VSWR alarm post- 30
processing

Copyright © Huawei

ration Value
Object
threshold(0.1)
VSWR alarm 20
threshold(0.1)
RF Unit Working MO
Mode
Number of RX 2
channels
Number of TX 2
channels
Frequency Min 5000
Bandwidth(kHz)
Switch

Object Name d Value

1,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length

Copyright © Huawei

Object Name d Value
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Type EVEL_0-1
Cell ID 1
Physical cell ID 1
E
CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception

Copyright © Huawei

Object Name d Value
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16
Number
Ratio(%)
RTA area ID
CN Operator ID 0
Tracking area 1
code
Flag UE
MMECAPINF MME 0
O Capability
Configuration

Copyright © Huawei

Object Name d Value
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
Radio PRB Local Cell ID 1
PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset
Remarks:

Domain Configuration MOC Parameter Name Recommended
Object Value
Radio LTE PDSCHCFG ReferenceSignalPwr 322

Copyright © Huawei
4.26 Example: Mode Transition from G*U*L(FT) to

G*U*L(FTM)
This chapter takes the transition from a G(eGBTS)*U*L(FT) co-MPT base station to a
G(eGBTS)*U*L(FTM) co-MPT base station with co-BBP as an example. Figure 1.67 shows
the details.
In this scenario, a GUL(FT) co-MPT base station in reconstructed into to a GUL(FTM) base station,
which has no impact on GSM and UMTS. LTE FDD and LTE NB-IoT share the antenna system and
baseband processing board.

Mode G(eGBTS)*U*L(F) G(eGBTS)*U*L(FTM)

configurati UMTS 3 cells UMTS 3 cells
on
LTE FDD 3 cells LTE FDD 3 cells
LTE TDD 3 cells LTE TDD 3 cells
NB-IoT 3 cells
BBU GSM, UMTS, and LTE GSM, UMTS, and LTE (FTM) share a BBU.
(FT) share a BBU.
module.
Transmissi GUL co-transmission and Remains the same.
on scheme separate service bearers, IP

Copyright © Huawei
over Ethernet
networking

ration Value
Object

Link
Cabinet No. 0
Subrack No. 0
Slot No. 7
Mode l)
CLKSYNCMODE TIME
Selected Clock GPS
Source

ration Value
Object

Subrack No. 0
Slot No. 3
Board Type UBBP
Work Mode FDD
Standard 1&NBIOT-1
State

Copyright © Huawei

ration Value
Object

topology
Topo Type CHAIN
Backup Mode COLD
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 3
Head Port No. 0
Subrack No. 61
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RRU Name FDDNB_RRU
State
processing switch
VSWR alarm post- 30
processing
threshold(0.1)
VSWR alarm 20
threshold(0.1)
RF Unit Working LM
Mode
Number of RX 2
channels
Number of TX 2
channels
Frequency Min 5000
Bandwidth(kHz)

Copyright © Huawei

ration Value
Object
Switch

Object Name d Value

1,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag
Type EVEL_0-1
Cell ID 1
Physical cell ID 1
E

Copyright © Huawei

Object Name d Value
CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 2T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode
equipment
Sector 1
equipment ID
Reference 32767
signal
power(0.1dBm)

Copyright © Huawei

Object Name d Value
Baseband 255
equipment ID
O Capability
Configuration
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS
Optimization
Capability
MME Support SUPPORT
LTE Capability
RTA area ID
CN Operator ID 0
Tracking area 1
code
Flag UE
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16
Number
Ratio(%)

Copyright © Huawei
1. Standalone

Object Name d Value

PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset
2. Guardband

Object Name d Value

PRB ID 0
Mode D
Frequency Band 8
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_2
Frequency
Offset
_BW_10M

Copyright © Huawei

Object Name d Value
LTE Downlink 3597

EARFCN
3. In-band

Object Name d Value

PRB ID 0
Deployment IN_BAND
Mode
Frequency Band 8
Uplink CFG
EARFCN
Configuration
Indicator
Uplink 21469
EARFCN
Uplink NEG_2
Frequency
Offset
Downlink 3513
EARFCN
Downlink POS_0
Frequency
Offset
Related LTE 0
Cell ID
Uplink All TRUE
Symbol Send
Flag
RVE
Index 0
Mode MENT
Type MODE

Copyright © Huawei

Object Name d Value
RB Reserve 4
Start Index
RB Reserve 4
End Index
RVE
Index 1
Mode MENT
Type E
RB Reserve 0
Start Index
RB Reserve 0
End Index
Adjust the power as required.

Object Name d Value

lPwr
4.27 Example: Mode Transition from G&L(T) to G&L(TM)

This chapter takes the transition from a GSM&L(TDD) base station to a GSM&L(TDD+NB-
IoT) base station with co-BBP as an example. Figure 1.68 shows the details.

Copyright © Huawei
New baseband processing board, RRU module, CRPI connections, and antenna system need to be
added. Co-MPT reconstruction is not required.
NB-IoT RRU: RRU3953

Mode GSM&L(TDD) GSM&L(TDD+NB-IoT)

configurati L(TDD) 3 cells L(TDD) 3 cells
on
L(M) 3 cells
BBU GSM and LTE TDD share GSM, LTE TDD, and LTE NB-IoT share a
a BBU. BBU.
RF RRU chain For 900 M RRUs, the CPRI port is on the NB-
topology IoT baseband processing board instead of on
the GTMUb.
RF power None NB-IoT: 1x20 W
on scheme
networking

Domain Configuratio MOC Parameter Name Recommended
n Object Value

Subrack No. 0

Copyright © Huawei

n Object Value
Slot No. 3
Board Type UBBP
Work Mode FDD
Standard
State
CPRI- RRUCHAIN Chain No. 1
based
topology Topo Type CHAIN
Backup Mode COLD
Head Cabinet No. 0
Head Subrack No. 0
Head Slot No. 3
Head Port No. 0
RF RRU Cabinet No. 0
module
Subrack No. 61
Slot No. 0
RRU Chain No. 1
RRU Position 0
RRU type MRRU
RRU Name NB_RRU
State
processing switch
VSWR alarm post- 30
processing
threshold(0.1)
VSWR alarm 20
threshold(0.1)
RF Unit Working GM
Mode

Copyright © Huawei

n Object Value
Number of RX 2
channels
Number of TX 1
channels
Frequency Min 5000
Bandwidth(kHz)
Switch

Object Name d Value

1,0,R0B;
SECTOREQM Sector 1
Equipment ID
Sector ID 1
Equipment TX_MODE,M
R0B,RXTX_M
ODE,MASTER
;
Cell Name 1
LSE
prefix length
Downlink NORMAL_CP
cyclic prefix
length
NB-IoT Cell TRUE
Flag

Copyright © Huawei

Object Name d Value
Type EVEL_0-1
Cell ID 1
Physical cell ID 1
E
CK
indication
Root sequence 1
index
Preamble 0
format
Customized NOT_CFG
bandwidth
configure
indicator
Emergency NOT_CFG
Area Id
indicator
allowed
configure
indicator
RRU Cell LSE
CPRI NO_COMPRE
Compression SSION
LSE
Cell 1T2R
transmission
and reception
mode
Work mode UL_DL
Cell Standby ACTIVE
Mode

Copyright © Huawei

Object Name d Value
equipment Sector 1
equipment ID
Reference 32767
signal
power(0.1dBm)
Baseband 255
equipment ID
Local tracking 1
area ID
R_OP
Operator uplink 16
RB used
ratio(%)
Operator 16
downlink RB
used ratio(%)
number FG_NUM_0
Operator Ue 16
Number
Ratio(%)
RTA area ID
CN Operator ID 0
Tracking area 1
code
Flag UE
MMECAPINF MME 0
O Capability
Configuration
ID
_CFG
S1 Interface ID 0
NB-IoT CIoT CP
EPS

Copyright © Huawei

Object Name d Value
Optimization
Capability
MME Support SUPPORT
LTE Capability
Radio PRB Local Cell ID 1
PRB ID 0
Mode NE
Frequency 8
Band
Uplink NOT_CFG
EARFCN
Configuration
Indicator
Downlink 3550
EARFCN
Downlink NEG_0DOT5
Frequency
Offset
Remarks:

Object Name d Value

lPwr

n Object d Value
CPRI-based GSM BTSRXUCHAI Chain No. 1

Copyright © Huawei

n Object d Value
topology N Topo Type CHAIN

Head Cabinet 0
No.
Head Subrack 0
No.
Head Slot No. 3
Head Port No. 0
RF module BTSRXUBP Cabinet No. 0
Subrack No. 61
Slot No. 0
RXU Board MRRU
Type
Working GSM_AND_N
Standard BIOT

Copyright © Huawei
Mode Transition Guide(For NB) 5 Mode Transition Implementation
5 Mode Transition Implementation
5.1 Policies
Because the live network is affected during mode transition of a multimode base station, you
are advised to make preparations and perform the operations that do not affect services in
advance, and perform the operations that affect services in parallel. This can shorten the
service interruption duration.
During mode transition, data configuration and hardware adjustment are key operations and
the services are interrupted during these operations. Services can be restored only when these
two operations are consistent because they are interdependent. For example, when a CPRI
link is moved to a new port on the BBU during the transition, data related to the CPRI link
must be adjusted accordingly. Services of a multimode base station can be restored only when
the port adjustment is consistent with data configured for the CPRI link.
During mode transition, adjusting hardware and activating data configuration interrupt
services. Therefore, you are advised to perform these two operations in parallel. This
minimizes the service interruption duration during mode transition.
1. Complete operations that do not affect services in advance, such as pre-installation of
equipment of the new mode. Perform operations that affect services in parallel if possible to
shorten the duration.
2. During mode transition, hardware adjustment is required and must be performed with data
configuration in some transition scenarios. Only in this way the services can be restored
normally. Such hardware adjustment can be adjustment of CPRI links or transmission links. In
this case, perform hardware adjustment and data configuration activation in parallel to shorten
the service interruption period.
3. Upgrade the original mode before mode transition.
4. Before mode transition, perform refarming on the original mode to allocate a new
frequency to the new mode if necessary. Refarming shall be completed before site
reconstruction. In addition, ensure that a sufficient buffer zone is reserved for site
reconstruction during refarming.

Copyright © Huawei
Mode Transition Guide(For NB) 5 Mode Transition Implementation
5.2 Procedure for Implementing Mode Transition

Figure 1.69 The following figure describes the procedure for implementing mode transition.

Copyright © Huawei
Mode Transition Guide(For NB) 6 Upgrading Base Station Software
6 Upgrading Base Station Software
6.1 Recording Base Station Status Before Mode Transition

Record the alarm status and service KPIs of a base station before mode transition for future
comparison.
Alarms must be cleared before mode transition. For details, see Table 69.1.
Table 69.1 Alarms to be cleared

Alarm Type Alarm Remarks
Hardware Alarms such as ALM-26200 -

Board Hardware Fault and
ALM-26532 RF Unit
Hardware Fault
Service Alarms such as ALM-28010 -
Carrier Configuration Error,
ALM-28011 RF Unit RX
Channel Fault, ALM-28203
Local Cell Unusable, ALM-
28211 Cell Configuration
Abnormal, and ALM-28201
Local Cell Blocked
Communication Alarms such as ALM-26235 -
RF Unit Maintenance Link
Failure, ALM-25901
Remote Maintenance Link
Failure, and ALM-26270
Inter-System
Communication Failure
Inter-system conflict Alarms such as ALM-26272
Inter-System RF Unit
Parameter Settings Conflict,
ALM-26274 Inter-System
Board Object Configuration
Conflict, and ALM-26277

Copyright © Huawei
Mode Transition Guide(For NB) 6 Upgrading Base Station Software
Alarm Type Alarm Remarks
Inter-System Control Rights

Conflict
The service KPIs need to be collected based on site requirements. The following table lists the
common KPIs to be checked.
Table 69.2 Common KPIs

KPI Check Item Counter to Check
Traffic volume CS Erlang, PS services of 64 kbit/s, 128

kbit/s, or 384 kbit/s, HSDPA, HSUPA, RRC
setups, and RAB setups (CS, PS, and
HSPA)
Service setup success rate RRC, RAB, and HSPA
Handover success rate Intra-frequency, inter-frequency, and inter-
RAT
Service drop rate AMR, PS, HSDPA, and HSUPA
Others KPIs specified by customers
6.2 Upgrading Base Station Software

Check whether the original versions of the GBTS and NodeB are the target versions of
SRAN. If the versions are not SRAN11.0, upgrade the base stations to the target version.
Refer to the upgrade guide of the target version during upgrade. If a USB flash drive is used
for the upgrade, see section "USB+U2000-based Commissioning" for SRAN11.1 or
"USB+U2000-based Commissioning" for SRAN12.0 in 3900 Series Base Station
Commissioning Guide.
6.3 Upgrading Software of Base Stations in the Co-MPT

Reconstruction Scenario
If the base station to be reconstructed includes a GBTS and the GBTS is to be reconstructed
into an eGBTS, the GTMU board must be converted. Before the conversion, download the
GTMU evolution software.
Visit http://support.huawei.com/carrier/, download the GTMU evolution software
corresponding to the MBTS'version (the software version is the V900 version).

Copyright © Huawei
Mode Transition Guide(For NB) 7 Applying for Licenses
7 Applying for Licenses
For details, see the following documents:

GBSS:
Guide to Application for BSC6900&BSC6910 License
http://support.huawei.com/carrier/docview!docview?nid=SE0000478505&path=PBI1-
7851894/PBI1-8132365/PBI1-7275801/PBI1-4110505
UMTS:
Guide to Application for RAN18.1 License
http://support.huawei.com/carrier/navi?lang=en#col=knowledge&kbDT=DT-TG&path=PBI1-
7851894/PBI1-7854240/PBI1-7275805
LTE FDD:
EGD-LTE License Guide for GTS Engineers (ESDP)
http://support.huawei.com/carrier/docview!docview?nid=KB1000325076&path=PBI1-
7851894/PBI1-21433538/PBI1-7854329
LTE TDD:
EGD-LTE License Guide for GTS Engineers (ESDP)
http://support.huawei.com/carrier/docview!docview?nid=SE0000617486&path=PBI1-
7851894/PBI1-7854238/PBI1-7854325/PBI1-21454014/PBI1-14069
Note: In mode transition from LTE FDD/LTE TDD/NB-IoT to multimode, the inventory
FDD/TDD/NB-IoT licenses need to be combined with the TDD/FDD/NB-IoT licenses. For
details, see EGD-LTE License Guide for GTS Engineers (ESDP)

Copyright © Huawei
Mode Transition Guide(For NB) 8 Preparing Data
8 Preparing Data
This section describes the procedure for preparing data during mode transition.
The CME provides different configuration methods for mode transition scenarios. The
following figure shows the process of selecting the configuration method.
The mode transition procedure is complex if great differences occur between base station configurations,
and transmission and hardware reconstruction is required at the same time.

Copyright © Huawei
8.1 Adding a BBU Interconnection Link on the GSM Side

(UCIU)
Step 1 For GBTSs, UCIU boards cannot be added using a summary data file. Instead, you can use
MML commands on the MBSC to add the UCIU boards before data synchronization. (The
MML command is ADD BTSBRD.)
Step 2 For GBTSs, BBU interconnection links cannot be added using a summary data file. Instead,
you can run MML commands on the MBSC to add the interconnect links before data
synchronization. (The MML command is ADD BTSCTRLLNK.)
----End

Copyright © Huawei
8.2 Synchronizing Data Configuration
Step 1 On the U2000, click in the upper left corner. Then, on the Application Center panel
of the U2000, double-click Topo View.
Step 2 Right-click the MBSC to which the GBTS belongs and choose Synchronize NE
Configuration Data.

Copyright © Huawei
Step 3 Synchronize the UMTS data to the U2000, right-click the NodeB and choose Synchronize
NE Configuration Data.

Copyright © Huawei
Step 4 Synchronize the LTE data to the U2000, right-click the eNodeB and choose Synchronize NE
Configuration Data
.
Step 5 Double-click CME on the Application Center tab page.

Copyright © Huawei
Step 6 On the CME, choose Area Management > Current Area > Synchronize NEs to
synchronize data to the U2000.
Step 7 In the displayed Synchronize NE(s) dialog box, select the MBSC and base station to be
synchronized.

Copyright © Huawei
Step 8 In the created planned data area, choose Area Management > Planned Area > Create
Planned Area. In the displayed Create Planned Area dialog box, add the MBSC and base
station, and click OK.

Copyright © Huawei
----End
You are advised to save configuration data on each base station side by referring to Saving
Configuration Data on the Base Station Side Before Mode Transition after synchronization for data
configuration rollback. For details about how to perform data configuration rollback, see Rolling Back
Base Station Configurations.
8.3 Preparing Data Using the Summary Data File

8.3.1 Configuring GSM Data
This section describes how to prepare and adjust GSM data when the GSM is used as the
original and new modes.
Only the eGBTS is supported in scenarios where the GSM works as a new mode. In this case,
all the data is configured using the summary data file for introducing RATs (SRAN
application) on the CME. For details about the configuration method, see 8.3.1.4Preparing
Transmission, Equipment, and Radio Adjustment Data (Co-MPT).
The following table list the configuration method when the GSM works as the original mode.
Table 1.1 GSM working as the original mode

Scenari Data CME Template Reference
o Type
GBTS Equipment The CME template provides a method of 8.3.1.1.1Adjusting

data configuring equipment data on the RF Data (GBTS)
common configuration interface or the
device panel of the LMT.
Transmissi The CME template is used for inter-BSC 8.3.1.2.1Adjusting
on data reparenting based on the TDM and IP. GBTS Data
Radio data a) Cell and neighbor relationships: The 8.3.1.2.1Adjusting
CME template is used as a data file for GBTS Data
Radio Network Planning (RNP).
b) Cell algorithm parameters: The CME
template is used as a parameter file for
radio network optimization (RNO).
eGBTS Equipment a) The CME template is used to configure Adjusting Co-MPT
data the summary data file in batches (GSM Device Data
application).
b) The CME template is used to adjust RF
data using the summary data file. It only
applies to RF-related data adjustment and
RXU board/TRX/cell capacity expansion
or decrease.
Transmissi a) Adjust the transmission data of the base Adjusting Co-MPT
on data station and controller together through Transmission Data
batch adjustment over the Abis interface.

Copyright © Huawei

o Type
b) Adjust the transmission data of the base

station through batch configuration of the
summary data file (GSM application).
Radio data The CME template is used for batch Adjusting Co-MPT
configuration of the summary data file. Radio Data
8.3.1.1 Preparing Equipment Data

This section describes how to adjust equipment data in co-MPT and separate-MPT scenarios
when the original mode is GSM. The equipment data to be adjusted includes the antenna and
feeder, BBU, RXU, and CPRI.
8.3.1.1.1 Adjusting RF Data (GBTS)

You can adjust GBTS data only on the common configuration interface or the device panel of
the LMT.
If only the RF-related equipment and radio data needs to be adjusted, use the summary data
file to adjust RF data. The configuration procedure is as follows:
Step 1 Customize and obtain the summary data file based on the mode transition planning results.
Step 2 Based on the customized template, export the data to be adjusted and specify data in the
template file as planned.
Step 3 Import the template file.
----End
The procedure for exporting and importing the GBTS data for RF adjustment is as follows:
Procedure
 Export a data file for GBTS RF adjustment.
a. Start the function of exporting GBTS data for RF adjustment.
i. On the menu bar of the planned data area, choose GSM Application > Export
Data > Export RF Adjustment Data (CME client mode) or CME > GSM
Application > Export Data > Export RF Adjustment Data (U2000 client
mode). A dialog box is displayed for you to select NE versions and base
station types.
ii. Select the version of the base station controller managing base stations to be
reconfigured.
iii. Set the base station type to GBTS.
iv. Click Next to start the wizard of exporting GBTS data for RF adjustment.
b. Verify the selected base station controller version in the NE version drop-down list.
c. Click Add. Three modes for selecting base stations are available. You can select
one of them based on site requirements.
d. Click Next and perform operations based on application scenarios.

Copyright © Huawei
Scenario Operation
Perform operations when a 1. Select Summary data file.

data file for RF adjustment 2. Specify save paths for both the prepared data file for RF
has been prepared. Then, the adjustment and the file where base station data is to be
CME exports base station exported.
data based on the
configuration objects in the
prepared data file.
Perform operations when no 1. Select Custom MOC.
data file for RF adjustment is 2. (Applies only to CME R17 and later versions.)To
prepared. Then, the CME export a summary data file with the Operation column,
exports base station data select Add the Operation column.
based on the configuration 3. Select configuration objects of the base stations to be
objects selected in the exported and specify a save path of the file where the
wizard. base station data is to be exported.
NOTE
By default, the CME selects the minimum set of mandatory
MOCs.
e. Click Next. The CME starts the export.

f. After the export succeeds, click Finish.
After the export succeeds, you can click the link in the dialog box to open the exported file.
 Import a data file for GBTS RF adjustment.
a. Start the function of importing GBTS data for RF adjustment.
i. On the menu bar of the planned data area, choose GSM Application > Import
Data > Import RF Adjustment Data (CME client mode) or CME > GSM
Application > Import Data > Import RF Adjustment Data (U2000 client
mode). A dialog box is displayed for you to select NE versions and base
station types.
ii. Select the version of the base station controller managing base stations to be
reconfigured.
iii. Set the base station type to GBTS.
iv. Click Next to start the wizard of importing GBTS data for RF adjustment.
b. Verify the selected base station controller version in the NE version drop-down list
and select the base station controller managing base stations whose RF data is to be
reconfigured from the NE drop-down list.
c. Select the data file for RF adjustment to be imported.
d. (Applies only to CME R17C10 and later versions.)Optional:Select Delete
redundant RF equipment data.
After this option is selected, the CME will automatically delete device
configuration objects and the subobjects that are not referenced by cells if
redundant device configuration objects exist in the summary data file.
e. Click Next and select base stations whose RF data is to be reconfigured.
You can select base stations in the NE list. You can also click Load to quickly select
base stations defined in the file by importing a file.

Copyright © Huawei
 When selecting base stations in the NE list, you can select base stations and then click Export to
export the selected base stations as a file for future selections.
 If the file is unavailable when you select base stations by importing a file, you can click Export to
obtain a file, edit the file, and then click Load to import the file into the CME.
For details about rules for loading the file, see File Rules.
f. Optional: Select Best effort.
 If Best effort is selected, the CME skips the error information and continues the import. When the
import is complete, the CME rolls back only incorrect base station data.
 If Best effort is not selected, the CME rolls back all the imported data if the import fails.
g. Optional: If you need to export scripts to separate files based on GBTSs, select
Export scripts in separate files based on GBTSs, and perform the following
operations:
 If data in the current planned data area has been reconfigured, and you want to export scripts using
the Export scripts in separate files based on GBTSs option, you have to export the scripts for
reconfiguring the data first.
 If you adjust RFs for co-group and co-coverage cells that do not belong to the same base station, you
cannot generate scripts in separate files by base station.
i. Specify a save path for scripts.
ii. Set an encryption mode for exported scripts.
□ No: The exported scripts do not have encryption passwords and no
encryption passwords are required when you loading projects.
□ Yes: The exported scripts have encryption passwords. When loading
projects, you have to enter encryption passwords by performing the
following operations:
If an encrypted password has been set for the exproted script, you cannot check the script on the local
PC. Instead, you have to check it using the script executor.
1) Select Yes.
2) Click Set Password. In the displayed dialog box, enter the encryption
password as required.
3) Click OK.
The exported encrypted script files are in .ecf format.
iii. Optional:If you need to activate scripts immediately after the wizard is
complete, select Launch the script executor if the task is successful.
h. Click Next. A dialog box is displayed for you to set attributes.
Set attributes based on Table 1.1.
Table 1.1 Setting attributes

Attribute Description
Cell ID The CME can automatically allocate IDs to new cells and TRXs.
TRX ID Automatic allocation rules: After you enter a reference ID in the
wizard, the CME searches for available IDs from the reference ID and
allocates them to new cells and TRXs. For example, after allocating a
reference TRX ID to the first TRX, the CME generates a new ID by
automatically adding 1 to the reference TRX ID and allocates the new

Copyright © Huawei
ID to the second TRX. If the generated ID has been used, the CME
automatically adds 1 to the ID until it is available and allocates the ID
to the second TRX.
NOTE
 The minimum ID available under the NE selected in the wizard functions as
the start value by default on the CME.
 When the imported data file contains different NEs, the CME searches for
available IDs from the preset start value and allocates them.
FH Attributes The CME generates data based on the FH type in the data file for RF
adjustment. If the FH type is not specified in the data file, the CME
generates data based on the FH type selected in the wizard.
NOTE
 FH type has the following values: NO_FH, RF_FH,
BaseBand_FH(BCCH HOP), and BaseBand_FH(BCCH NOT HOP),
indicating no FH, RF FH, baseband FH (BCCH TRX involved), and
baseband FH (BCCH TRX not involved), respectively.
 The configuration of the FH in PGSM/EGSM frequency band parameter is
as follows:
 When FH type is NO_FH, the configuration of FH in PGSM/EGSM
frequency band does not take effect.
 When FH type is RF_FH, FH in PGSM/EGSM frequency band can be set
to In Different MAGroup or In One MAGroup.
 When FH type is BaseBand_FH(BCCH HOP) or BaseBand_FH(BCCH
NOT HOP), FH in PGSM/EGSM frequency band can be set to In
Different MAGroup, In One MAGroup, or EGSM Frequency Not In Any
MAGroup.
Channel Rule Set channel allocation rules based on the RF adjustment scenarios.
 New Cells Channel Rule: configured when the data file for RF
adjustment contains new cells or you need to re-allocate channels of
existing cells. For details about channel allocation rules, see
Channel Allocation Rules.
NOTE
In the data file for RF adjustment, if Cell Extension Type is set to Double
Timeslot Extension Cell, the configuration of Channel Rule does not take
effect. The CME automatically allocates timeslots 0 and 2 on the BCCH TRX to
the BCCH and SDCCH, respectively, and allocates all the other timeslots in the
cell to TCHs.
 Existed Cells Channel Rule: configured when the data file for RF
adjustment contains only new TRXs or you need to add TRXs in an
existing cell.
− When Channel Allocation Rule 0 for TRXs is selected, the
CME re-allocates all channels of the imported cells based on the
channel allocation rule specified by New Cells Channel Rule.
CME allocates only channels of new TRXs based on the
following rules:
1. Rank TRXs by TRX No. in ascending order.
2. Allocate PDCCHs: PDCCHs are allocated to channels 6, 5, 7, 4,
3, 2, 1, and 0 of a TRX in sequence.
3. Allocate SDCCHs: Based on the sequence of TRX numbers,

Copyright © Huawei
allocate SDCCHs to channel 0 of all new TRXs in the current

cell, channel 1, and so on.
NOTE
■ The rules do not take effect when the cell to which a TRX belongs is a double
timeslot extension cell.
■ The number of available channels is the difference between the sum of
Number of PDCH and Number of SDCCH specified in the data file for RF
adjustment and the number of configured channels of the cell to which new TRXs
belong.
i. Click Next, when the import is complete, click Finish.

나 If the CME displays a message stating that the operation is successful,
configuration data has been successfully imported.
다 If the CME displays a message stating that the import failed, base station
configuration data failed to be imported. If this occurs, you have to reconfigure
the data based on the error information.
In the error message list, you can:

 Click an error message to view the details at the bottom of the wizard.
 Double-click an error message to switch to the corresponding location in the imported file. Then,
reconfigure the data based on the error information.
 If data of some base stations fails to be imported when Best effort is selected, reconfigure the data
and import it again.
8.3.1.1.2 Adjusting Equipment Data in Co-MPT Scenarios

When the original mode is GSM in co-MPT scenarios, you need to use the summary data file
for batch configuration on the CME. If only the RF-related equipment data (RXU
board/TRX/cell capacity) needs to be adjusted, you can adjust RF data using the summary
data file.
The configuration procedure is as follows:
----End
The procedure for exporting and importing the summary data file for batch configuration is as
follows:
Procedure
 Export base station data to the summary data file.
Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application
> Export Data > Export Base Station Bulk Configuration Data (CME client mode) or
CME > SRAN Application > MBTS Application > Export Data > Export Base Station

Copyright © Huawei
Bulk Configuration Data (U2000 client mode). A dialog box is displayed for you to
configure data in batches, as shown in Figure 1.1.
Figure 1.1 Exporting base station bulk configuration data
Step 2 Select a reconfiguration scenario, RAT of NEs, versions of base stations and base station
controllers, and list of base stations. Then, click Next.
 If you select the GSM base station controller and base station data, the implementation
of the function is the same as that of importing and exporting Abis interface data of a
single-mode base station. For detailed operations, see Importing and Exporting Abis
Interface Data for Batch Reconfiguration.
 If you select the UMTS base station controller and base station data, the implementation
of the function is the same as that of importing and exporting Iub interface data of a
single-mode base station. For detailed operations, see Exporting Iub Data for Batch
Reconfiguration and Importing Iub Data for Batch Reconfiguration.
 If two or more RATs are selected, base station data and controller data cannot be
reconfigured together.
Step 3 Select Custom MOC, set objects you want to export, and specify a save path for the exported
file.
 (Applies only to CME R17 and later versions.)To export a summary data file with the Operation
column, select Add the Operation column.
 To export data based on the objects contained in a prepared summary data file, perform the
following steps.

Copyright © Huawei
(Applies only to CME R17C10 and later versions.)If you need to use a summary data file with
scenarios differentiated, customize the summary data file. For detailed operations, see Customizing
the Summary Data File with Scenarios Differentiated (Example).
1. Select Bulk configuration template.
2. In Bulk configuration data file, select the prepared file and export configuration data from the
CME based on the MOs in this file.
3. In Export path, specify a save path for the file that contains the exported data.
Step 4 Click Next. The CME verifies the configuration data to be exported.
If the verification fails, the CME does not export data.
Step 5 After the export is complete, click Finish.
----End
 Open the local summary data file and reconfigure data in the summary data file based on
planned data.If parameters to be reconfigured for each base station are the same and
numbers of parameter records are the same, it is convenient to reconfigure them in the
MOC-integration view. For detailed operations, see Editing a Summary Data File for
Batch Configuration (MOC-Integration View).
 Import the modified summary data file.
> Import Data > Import Base Station Bulk Configuration Data (CME client mode) or
CME > SRAN Application > MBTS Application > Import Data > Import Base Station
Bulk Configuration Data (U2000 client mode). A dialog box is displayed for you to import
data for batch configuration.
Step 2 Specify the RAT of NEs to be imported, determine whether to import base station controller
data (base station data must be selected), and click Next.
If two or more RATs are selected, base station data and controller data cannot be reconfigured
together.
Step 3 Start a wizard based on scenarios.
If... Then...
You have selected The CME starts the wizard for importing Abis interface data. For
GSM base station detailed operations, see Importing and Exporting Abis Interface Data
controllers and for Batch Reconfiguration.
base stations in
the preceding step
You have selected The CME starts the wizard for importing Iub interface data. For
UMTS base detailed operations, see Importing Iub Data for Batch Reconfiguration.
station controllers
and base stations
in the preceding
step
You have selected The CME starts the wizard for importing base station data for batch
only base stations configuration. The procedure is as follows:
in the preceding 1. Select the file you want to import and click Next.
step
NOTE
The CME supports the file import even if the RAT contained in the file is

Copyright © Huawei
If... Then...
different from the selected RAT. For example, if GSM is selected but the RAT
contained in the file is UMTS or LTE, the file can still be imported.
2. Select the base stations for which you want to import the file and
click Next.
NOTE
 If Best effort is selected, the CME skips the error information and continues
the import. When the import is complete, the CME rolls back only incorrect
base station data.
 If Best effort is not selected, the CME rolls back all the imported data if the
import fails.
3. After the import is complete, click Finish.
 If the CME displays a message stating that the operation is
successful, configuration data has been successfully imported.
 If the CME displays a message stating that the import failed, base
station configuration data failed to be imported. If this occurs, you
have to reconfigure the data based on the error information.
NOTE
 Double-click an error message to switch to the corresponding location in the
imported file. Then, reconfigure the data based on the error information.
----End
The procedure for exporting and importing the summary data file for RF adjustment is as
follows:
Procedure
 Export the summary data file for RF adjustment.
Step 1 On the menu bar of the CME, choose SRAN Application > MBTS Application > Export
Data > Export Base Station RF Adjustment Data. A dialog box is displayed.
Step 2 Set parameters displayed in the dialog box and specify the base stations whose data you want
to export.
 Select Co-MPT BTS RF Adjustment from the Scenario drop-down list.
 Specify the RATs of the base stations whose data you want to export.
 Specify the versions of the base stations and base station controller whose data you want
to export.
 Select the base stations whose data you want to export.
You can select base stations in the NE list. You can also click Load to quickly select base
stations defined in the file by importing a file.

Copyright © Huawei
Step 3 Click Next. Then, specify the export mode, summary data file, and export path.
Table 1.1 Setting an export mode

Export Mode Operation
Custom MOC: Select 1. Select Custom MOC.

objects you want to export 2. If you need to manually edit sector equipment data in the
in the wizard directly and exported summary data file, select Manually edit sector
enable the CME to export equipment data.
data based on the selected 3. (Applies only to CME R17 and later versions.)To export
objects. a summary data file with the Operation column, select
Add the Operation column.
The Manually edit sector equipment data option is
selected by default.
4. Select objects to be exported.
NOTE
The CME adds objects that support adjustment by default. You can
adjust the objects as required.
5. Specify a save path for the exported files in Export path.
RF adjustment template: Select RF adjustment template.
Export data based on the 1. Select the prepared summary data file for adjustment in
objects contained in a RF adjustment data file.
prepared file.
Step 4 Click Next. The CME starts the export.

Step 5 Click Finish.
----End
 Import the summary data file for RF adjustment.

Step 1 On the menu bar of the CME, choose SRAN Application > MBTS Application > Import
Data > Import Base Station RF Adjustment Data. A dialog box is displayed.
Step 2 Select the file you want to import.
Step 3 Optional: (Applies only to CME R17C10 and later versions.)Select Delete redundant RF
equipment data.
If redundant device configuration objects exist in the summary data file, after Delete
redundant RF equipment data is selected, the CME will automatically delete device
configuration objects and the subobjects that are not referenced by cells.
Step 4 Click Next, select the base stations for which you want to import the file.

Copyright © Huawei
Step 5 (Optional) Select Best effort for the import.
Step 6 Optional: To generate configuration scripts in the wizard, select Export scripts and perform
the following operations:
1. Select the mode of generating scripts.
− Scripts on the controller side:
가 To save scripts of logical base stations in the same file, select Batch.
나 To save scripts of logical base stations in separate files by base station, select
One by one.
− Scripts of base stations:
To save the incremental scripts in separate files by RRU chain/ring, separate the
scripts by RRU chain/ring trunk or branch RRU chain/ring. The CME automatically
generates common incremental scripts and incremental RRU chain/ring scripts. For
base stations whose RRU chain/ring fails to be separated, the CME generates scripts
that are not separated.
 Script separation by RRU chain/ring applies only to base stations in SRAN10.1 or later.
 Script separation by RRU chain/ring trunk or branch applies only to base stations (using RMU) in
SRAN12.0 or later.
 If the common incremental scripts of base stations depend on the incremental RRU chain/ring scripts
or if two incremental RRU chain/ring scripts are associated, scripts cannot be separated by RRU
chain/ring.
 For concepts of RRU chain/ring trunk and branch, and scenarios supported by this function, see
Supported Scenarios.
2. Specify a save path for scripts.
3. Set an encryption mode for exported scripts.
− No: The exported scripts do not have encryption passwords and no encryption
passwords are required when you loading projects.
− Yes: The exported scripts have encryption passwords. When loading projects, you
have to enter encryption passwords by performing the following operations:
가 Select Yes.
나 Click Set Password. In the displayed dialog box, enter the encryption
다 Click OK.
Step 7 Click Next, set the parameters for GSM service.

Copyright © Huawei

to the second TRX.
NOTE
NOTE
1. FH type has the following values: NO_FH, RF_FH, BaseBand_FH(BCCH
HOP), and BaseBand_FH(BCCH NOT HOP), indicating no FH, RF FH,
baseband FH (BCCH TRX involved), and baseband FH (BCCH TRX not
involved), respectively.
2. The configuration of the FH in PGSM/EGSM frequency band parameter is
as follows:
MAGroup.
NOTE
cell to TCHs.
existing cell.

Copyright © Huawei

following rules:
NOTE
 The rules do not take effect when the cell to which a TRX belongs is a double
 The number of available channels is the difference between the sum of
adjustment and the number of configured channels of the cell to which new
TRXs belong.
Step 8 Click Next, when the import is complete, click Finish.

 If the CME displays a message stating that the operation is successful, configuration data
has been successfully imported.
 If the CME displays a message stating that the import failed, base station configuration
data failed to be imported. If this occurs, you have to reconfigure the data based on the
error information.

 If data of some base stations fails to be imported when Best effort is selected,
reconfigure the data and import it again.
----End
8.3.1.2 Preparing Transmission Data

This section describes how to adjust transmission data in co-MPT and separate-MPT
scenarios when the original mode is GSM. The transmission data to be adjusted includes the
following MOs: IP, IPPATH, SCTPLINK, CPBEAR, and IPRT.
8.3.1.2.1 Adjusting GBTS Data

When the GBTS works as the original mode, use the following functions on the CME to
adjust GBTS data: Export GBTS data, Import the Abis interface data that has been
reconfigured in batches, and Reparent IP GBTS within BSC.
Step 1 Customize and obtain the template files based on the mode transition planning results.

Copyright © Huawei
----End
To adjust data of a GBTS using TDM transmission, perform the following steps:
The procedure for exporting and importing the GBTS data is as follows:
Export GBTS Data

Step 1 On the menu bar of the planned data area, choose GSM Application > Export Data > Export
GBTS Summary Data (CME client mode) or CME > GSM Application > Export Data >
Export GBTS Summary Data (U2000 client mode). A dialog box is displayed for you to
select GBTSs.
Step 2 Select a base station controller version from the NE version drop-down list.
Step 3 Click Add. Three GBTS selection modes are available. Select a mode as required.
Step 4 Click Next. A dialog box is displayed for you to specify a save path.
If manual timeslots are configured in selected GBTSs, a dialog box is displayed to ask whether to
continue and provide GBTSs for which manual timeslots are configured.
 Click Yes. A dialog box is displayed for you to specify a save path.
 Click No to return to the dialog box for selecting GBTSs.
Step 5 Select a summary data file and specify a save path.

The CME uses the selected summary data file as a template for the exported GBTS
configuration data and exports the file to the specified path.
Step 6 Click Next. The CME starts to export the data.
Step 7 When the export is successful, click Finish.
After the file is exported, you can click the path link in the dialog box to navigate to the folder where the
exported file is located.
----End
The procedure for exporting and importing the Abis interface data for batch reconfiguration is
as follows:
Import Abis Interface Data for Batch Reconfiguration

1. On the menu bar of the planned data area, choose GSM Application > Import Data >
Import Abis Bulk Configuration Data (CME client mode) or CME > GSM
Application > Import Data > Import Abis Bulk Configuration Data (U2000 client
mode). A dialog box is displayed for you to import the Abis data that has been
reconfigured in batches.
2. Perform operations as required.

Copyright © Huawei
If you need to... Then...
Import the file only 1. Select the file you want to import.
(without generating a 2. Optional: Select Best effort (this option is available for
script immediately when eGBTS reconfiguration).
the export is successful) NOTE
 If Best effort is selected, the CME skips the error information and
continues the import. When the import is complete, the CME rolls
back only incorrect base station data.
 If Best effort is not selected, the CME rolls back all the imported
data if the import fails.
3. Click Next and select base stations whose data you want to
import.
4. Click Next. The CME starts to import the file.
Generate a script file 1. Select the file you want to import and select Export script
immediately when the by wizard.
import is successful 2. Optional: Select Best effort.
NOTE NOTE
 If Best effort is selected, the CME skips the error information and
This mode does not apply
continues the import. When the import is complete, the CME rolls
to GBTSs. back only incorrect base station data.
 If Best effort is not selected, the CME rolls back all the imported
data if the import fails.
3. Click Next, and select NEs and a mode for generating
script.
a. Select Batch or One by one to generate all logical base
station scripts in one script file or generate scripts by
base station, respectively.
NOTE
When multiple base stations share MOs at the bottom link layer, such
as MOs ETHIP, PPPLNK, and MPGRP, if the script generation
mode is set to One by one, primary information (information about
the subrack and slot numbers of an interface board) about these MOs
cannot be modified if the related IP addresses are not changed.
Otherwise, data may conflict after being imported into the CME.
b. (Optional) If One by one is selected, click Up or Down
to adjust the sequence for running base station scripts.
4. Set the script generation information.
a. Specify a save path for the script file.
b. (Optional) Set an encryption mode for exported scripts.
■ No: The exported scripts do not have encryption
passwords and no encryption passwords are required
when you loading projects.
■ Yes: The exported scripts have encryption passwords.
When loading projects, you have to enter encryption
passwords by performing the following operations:
NOTE
If an encrypted password has been set for the exproted script, you
cannot check the script on the local PC. Instead, you have to check it
using the script executor.
① Select Yes.

Copyright © Huawei
② Click Set Password. In the displayed dialog box,

enter the encryption password as required.
③ Click OK.
c. (Optional) To enable the CME to automatically start the
script executor after a script is generated successfully in
the wizard, select Launch the script executor if the
task is successful.
d. Click Next. The CME starts to import the data.
3. View the import report and click Finish.

To adjust data of a GBTS using IP transmission, perform the following steps:
The procedure for migrating an IP-based GBTS within a BSC is as follows:
Procedure
Step 1 On the main menu of the planned data area, choose CME> GSM Application> Reparent IP
GBTS within BSC (U2000 client mode) or GSM Application> Reparent IP GBTS within
BSC (CME client mode). A dialog box is displayed for you to configure reparenting
information.
Step 2 Clear Export File.
Step 3 Click Next. In the displayed dialog box, select the reparenting data planning file you want to
import.
You are advised to import a reparenting data planning file that is edited in and exported from CMEs of
the same version.
Step 4 Click Next. The CME verifies the reparenting data planning file and displays the verification
result.
 If the verification is successful, a message is displayed stating that the verification is
successful.
 If the verification fails, the CME displays a dialog box showing the parameters whose
values are incorrectly configured in the file. You can click Retry to edit the file again.
Step 5 Click Finish to exit the wizard.
Step 6 Export the reparenting scripts. For detailed operations, see Exporting Incremental Scripts
from a Planned Data Area.
The CME automatically generates reparenting rollback scripts when exporting reparenting
scripts.
----End

Copyright © Huawei
8.3.1.2.2 Adjusting Co-MPT Data

In co-MPT scenarios where the original mode is GSM, if only the base station data needs to
be adjusted, use the summary data file for batch configuration (GSM application) on the CME
to configure transmission data. If the data of the base station and controller needs to be
adjusted together, use the Abis batch adjustment data.
----End
The procedure for exporting and importing the summary data file for batch configuration
(GSM application) is as follows:
Procedure

Copyright © Huawei
file.
following steps.

Copyright © Huawei
----End
together.
If... Then...
base stations in
the preceding step
station controllers
and base stations
in the preceding
step
step
NOTE
click Next.
NOTE

Copyright © Huawei
If... Then...
base station data.
import fails.
NOTE
----End
The procedure for exporting and importing the Abis interface data for batch reconfiguration is
as follows:
Export the Abis interface data for batch reconfiguration.

1. On the menu bar of the planned data area, choose GSM Application > Export Data >
Export Abis Bulk Configuration Data (CME client mode) or CME > GSM
Application > Export Data > Export Abis Bulk Configuration Data (U2000 client
mode). A dialog box is displayed for you to export the data you want to reconfigure in
batches.
2. Select the base station controller version, base station version, and related base station,
and click Next.
3. Perform operations based on application scenarios.
Select objects you want to export in the 1. Select Custom MOC.

wizard directly and enable the CME to 2. To export a summary data file with the
export data based on the selected objects. Operation column, select Add the
NOTE Operation column.
3. Select objects you want to export and
This mode does not apply to GBTSs.
specify a save path for the exported file.
Export data based on the objects contained 1. Select Bulk configuration template.

Copyright © Huawei
in a prepared file. 2. In Bulk configuration data file, select

the prepared file and export
configuration data from the CME based
on the MOs in this file.
3. In Export path, specify a save path for
the file that contains the exported data.
4. Click Next. The CME verifies the configuration data to be exported.

5. After the export is complete, click Finish.
8.3.1.3 Preparing Radio Data

This section describes how to adjust radio data in co-MPT and separate-MPT scenarios when
the original mode is GSM. The radio data to be adjusted includes the MOs related to the cell,
TRX, and sector.
8.3.1.3.1 Adjusting GBTS Data

When the original mode is GSM where the GBTS is used, you need to use the data file for
RNP and inter-BSC reparenting based on the TDM and IP on the CME to configure cells and
neighbor relationships and cell algorithm parameters, respectively.
----End
The procedure for exporting and importing the data file for RNP is as follows:
Procedure
 Export the planned radio data.
a. On the menu bar of the planned data area, choose GSM Application > Export
Data > Export Radio Network Planning Data (CME client mode) or CME >
GSM Application > Export Data > Export Radio Network Planning Data
(U2000 client mode). A dialog box is displayed for you to select NEs.
b. Select the base station controller and version of the NE to which the cells whose
neighboring and external cell data you need to export belong.
You can click to load common objects in batches.

c. Click Next. A dialog box is displayed for you to select export options.
d. Select one or more data types as required.
라 Select one or more external cell types in the External Cell Type area.

Copyright © Huawei
마 Set the neighboring cell data that you need to export in the Neighboring
Relationship Type area.
1) Select one or more neighbor relationship types.
2) Click Add. Three cell selection modes are available. Select cells in any
mode based on site requirements. For details about the modes, see Object
Selection Modes.
To configure two cells under different base station controllers as neighboring cells, you need to export
data of external cells and neighboring cells and add the corresponding external cells to the exported file.
Otherwise, the neighbor relationships fail to be configured.
e. Click Next to specify a file format (TXT, XLS, or XLSM) and a save path.
바 XLS and XLSM files contain all the configuration objects. Each configuration
object corresponds to a sheet.
Sheet names must not be changed. Otherwise, the CME fails to process data in
the file during the import.
사 The TXT file contains only the selected configuration objects. Each
configuration object corresponds to a TXT file.
The TXT file name must not be changed. Otherwise, the CME fails to process
data in the file during the import.
아 If the data to be exported exceeds 65,535 rows, save the data as a TXT or an
XLSM file.
f. Click Next. The CME exports neighbor relationship and external cell data.
g. When the export is successful, click Finish.
 Import the planned radio data.
a. On the menu bar of the planned data area, choose GSM Application > Import
Data > Import Radio Network Planning Data (CME client mode) or CME >
GSM Application > Import Data > Import Radio Network Planning Data
(U2000 client mode). A dialog box is displayed for you to select files.
b. Select a base station controller version from the NE version drop-down list.
c. Select the file to be imported in TXT, XLS, or XLSM format.
d. Click Add File to add the modified radio network data planning file.
e. Click Next. A dialog box is displayed for you to select an import mode.
f. Select the type of the data to be imported and an import mode as required. For
details, see Table 1.1.
Table 1.1 Description of import modes

Import Mode Whethe Whether Data Result on the CME After File
r the the Import
Object Object
Data Data
Exists Exists in
on the the File
CME
Append Yes Yes The CME overwrites the existing data with

Copyright © Huawei
r the the Import
Object Object
Data Data
Exists Exists in
on the the File
CME
the data in the file.

No Yes  For the external cell data, the CME adds the
data in the file.
 The CME processes neighbor relationships
in the following methods:
− If the external cells related to the
neighbor relationships to be imported
have been configured on the CME, the
CME adds the neighboring cell data in
the file.
have not been configured on the CME
and the source cell cannot be found,
the CME does not process the data.
− If the local cell related to the neighbor
relationships to be imported does not
exist on the CME, the CME does not
process the data.
NOTE
 BIDIRECTION in the file takes effect only in
the Append mode.
 If BIDIRECTION is set to Yes and inverse
neighboring cells do not exist, the CME
processes data in the following ways:
 Parameter values for the inverse neighboring
cells come from the source cell.
 If no external cell exists, the CME also
automatically configures external cells and
uses the default NE values for the parameters
of the external cells.
 If any external cells exist and the parameter
configurations of the external cells are different
from those of the source cell, the CME does
not reconfigure external cell parameters and
obtains the parameter values of neighboring
cells from the source cell.
Yes No No data in the CME changes.

Update Yes Yes The CME overwrites the existing data with
NOTE the data in the file.
 Neighbor
No Yes The CME adds the data in the file.
relationships
are updated
on a cell
Yes No The CME deletes the existing data.

Copyright © Huawei
r the the Import
Object Object
Data Data
Exists Exists in
on the the File
CME
basis.
 External cells
are updated
on a base
station
controller
basis.
Delete Yes Yes The CME deletes the existing data.

No Yes No data in the CME changes.
g. Click Next. The CME starts to import and verify the data.
If... Then...
The verification fails 1. Modify data according to the displayed verification error
information.
 If the CME displays the error information link, click the link
and reconfigure the related data.
 If the CME displays the error information description, locate
the error manually based on the description and reconfigure
the related data.
2. Click Retry to import the reconfigured data.
The verification Click Finish to exit.
succeeds NOTE
(Applies only to CME R17C10 and later versions.)To prevent frequency
band conflicts occur in GUL multi-mode base stations after frequency
refarming, you can select Start frequency overlapping check and
bandwidth verification on RF channels of MBTSs after closing the
wizard after the data is imported. The CME starts to verify cell frequency
and bandwidth configuration data of the GUL multi-mode base stations.
When importing the planned radio data, the CME automatically shields the invalid parameters in the file
without affecting the import of the other data. For example, the CME automatically shields the neighbor
relationships that fail to be imported because the related cells do not exist.
The procedures for migrating a TDM-based or IP-based GBTS within a BSC is as follows:
Procedure
 Export radio network optimization data.

Copyright © Huawei
a. On the menu bar of the planned data area, choose GSM Application > Export
Data > Export *** (CME client mode) or CME > GSM Application > Export
Data > Export *** (U2000 client mode). A dialog box is displayed for you to select
cells.
Export *** can be Export Cell Parameter Data, Export Cell Frequency Data, and Export
Neighboring Cell BA Data.
b. Select cells whose data you want to export.
Export data of all cells 1. Choose NE from the Selected by drop-down list.
under an NE 2. Select a base station controller version from the NE
version drop-down list.
3. Select a base station controller whose cell data you want to
export.
Use the following buttons as required:
 You can click to select RAT. If you select a

RAT, only base stations of this RAT are displayed. If
you select All, all base stations are displayed.
 You can click to load common objects in

batches. For details, see Loading Common Objects in
Batches.
Export data of certain 1. Choose Cell from the Selected by drop-down list.
cells under an NE 2. Select a base station controller version from the NE
version drop-down list.
3. Click Add. Three modes for selecting cells are displayed.
Select a mode as required. For details about the modes, see
Object Selection Modes.
When you choose Export Cell Frequency Data, to filter other frequencies than those used by the TRXs
and FH groups, select Remove redundant frequencies.
c. (Optional and required when you choose Export Cell Parameter Data) Click
Next. Select parameters you want to export, and click .
 You can click Save To File in the lower part of the dialog box to save the selected objects as a file.
You can directly load the file if you need to export these objects again.
 You can click Load From File in the lower part of the dialog box to load the exported file that
contains the selected parameters. In this way, you do not need to manually select parameters.
d. Click Next, and perform related operations based on the type of the data and file to
be exported.
Data File Operations
Type Type
Export Negotia 1. Select the file to be exported in TXT, XLS, or XLSM format.
Cell ted data  XLS and XLSM files contain all the configuration objects.
Parame file

Copyright © Huawei

Type Type
ter Data Each configuration object corresponds to a sheet.

Sheet names must not be changed. Otherwise, the CME fails
to process data in the file during the import.
 The TXT file contains only the selected configuration objects.
Each configuration object corresponds to a TXT file.
The TXT file name must not be changed. Otherwise, the CME
fails to process data in the file during the import.
 If the data to be exported exceeds 65,535 rows, save the data
as a TXT or an XLSM file.
2. Specify a save path for the file to be exported.
Export Negotia 1. Select the file to be exported in TXT, XLS, or XLSM format.
Neighbo ted data  XLS and XLSM files contain all the configuration objects.
ring file Each configuration object corresponds to a sheet.
Cell BA
Data
 The TXT file contain all the configuration objects. Each
configuration object corresponds to a TXT file. If a
configuration object is empty, no TXT file is generated for it.
Export Negotia 1. Set the export type to Negotiated Data.
Cell ted data 2. Select the file to be exported in TXT, XLS, or XLSM format.
Freque file  XLS and XLSM files contain all the configuration objects.
ncy Each configuration object corresponds to a sheet.
Data
 The TXT file contain all the configuration objects. Each
configuration object corresponds to a TXT file. If a
configuration object is empty, no TXT file is generated for it.
Summa 1. Set the export type to Summary Data.
ry data 2. Select the path of the summary data file.
file You can obtain the default summary data file Summary Data
File-2G Cell Frequency Data.xls from U2000 client installation
path\client\client\Data\BSC
version\Model\summarytemplates\GSM\language.
3. Select a file format, XLS or XLSM.

Copyright © Huawei

Type Type
If the data to be exported exceeds 65,535 rows, save the data as

an XLSM file.
e. Click Next. The CME starts to export the data.

f. When the export is successful, click Finish.
 Import radio network optimization data.
a. On the menu bar of the planned data area, choose GSM Application > Import
Data > Import *** (CME client mode) or CME > GSM Application > Import
Data > Import *** (U2000 client mode). A dialog box is displayed for you to select
files.
Import *** can be Import Cell Parameter Data, Import Cell Frequency Data, and Import
Neighboring Cell BA Data.
b. Select a base station controller version from the NE version drop-down list.
If the file format of Import Cell Frequency Data is XLS or XLSM, no NE version needs to be
specified.
c. Select the file to be imported in TXT, XLS, or XLSM format.
d. Click Add File to add the modified files.
If the controller version is not BSC6000 V901R013 and the file format of Import Cell Frequency Data
is XLS or XLSM, you can select files of different controller versions to import at a time.
e. Optional:If the type of data to be imported is Import Cell Parameter Data, select
Select some cells and select the cell list file containing data of some cells.
You can click Obtain Template to obtain the cell list file and set data of cells to be imported.
f. Click Next, and perform related operations based on the type of the data to be
imported.
Data Type Operations
 Import Cell The CME starts to import and verify the data.
Parameter Data
 Import Cell
Frequency Data
Import Neighboring 1. Select either of the following modes as required:
Cell BA Data  Append: adds or modifies neighboring cell BA data. The
CME overwrites the existing neighboring cell BA data with
the data in the imported file.
 Update: updates neighboring cell BA data. The CME
updates the existing neighboring cell BA data based on the

Copyright © Huawei
Data Type Operations
data in the imported file.

2. Click Next. The CME starts to import and verify the data.
g. Perform related operations based on the verification result.

If... Then...
The verification fails 1. Modify data according to the displayed verification error
information.
 If the CME displays the error information link, click the link
and reconfigure the related data.
 If the CME displays the error information description, locate
the error manually based on the description and reconfigure
the related data.
2. Click Retry to import the reconfigured data.
The verification Click Finish to exit.
succeeds NOTE
To prevent frequency band conflicts occur in GUL multi-mode base stations
after frequency refarming, you can select Start frequency overlapping
check and bandwidth verification on RF channels of MBTSs after
closing the wizard after the data is imported. The CME starts to verify cell
frequency and bandwidth configuration data of the GUL multi-mode base
stations.
8.3.1.3.2 Adjusting Co-MPT Data

When the original mode is GSM in co-MPT scenarios, you need to use the summary data file
for batch configuration on the CME to configure radio data.
----End
The procedure for exporting and importing data of a co-MPT base station for batch
configuration is as follows:
Procedure

Copyright © Huawei
file.
following steps.

Copyright © Huawei
----End
together.
If... Then...
base stations in
the preceding step
station controllers
and base stations
in the preceding
step
step
NOTE

Copyright © Huawei
If... Then...
click Next.
NOTE
base station data.
import fails.
NOTE
----End
8.3.1.4 Preparing Transmission, Equipment, and Radio Adjustment Data

(Co-MPT)
This section describes how to configure data where GSM works as a new mode. All the data
is configured using the summary data file for introducing RATs (SRAN application) on the
CME. The configuration procedure is as follows:
----End
The procedure for performing mode addition on a co-MPT base station in batch is as follows:
Procedure
 Before exporting data based on a customized summary data file, use the function of
customizing a summary data file to customize a summary data file for RAT introduction.
In RAT introduction scenarios, you need to customize application maintenance mode
parameters, including AT and APPMNTMODE, of each RAT to a summary data file.

Copyright © Huawei
When setting parameter values, you are advised to set APPMNTMODE of the RAT to
be introduced to TESTING.
 Export co-MPT base station data to the summary data file for introducing RATs.
> Export Data > Export Base Station Multimode Expansion Data (CME client mode) or
Multimode Expansion Data (U2000 client mode). A dialog box is displayed for you to
export co-MPT base station data.
Step 2 Select a scenario, RAT to be introduced to the co-MPT base station (for example, select LTE
for a co-MPT (GU) base station to be expanded to a co-MPT (GUL) base station), controller
version, base station version, base station to which RATs are to be introduced, and sample
base station, as shown in Figure 2.1.
Figure 2.1 Export expansion data
If you need to select base stations in batches by using a file, click Export to obtain an Excel file, edit the
file, and click Load to import it.
Step 3 Click Next and perform operations based on application scenarios.
Option Operation
Summary data file: Select this option when 1. Select Summary data file.
a summary data file has been prepared. 2. Specify save paths for both the prepared
Then, the CME exports base station data summary data file and the file where
based on the configuration objects in the base station data is to be exported.
prepared summary data file.
Custom MOC: Select this option when no 1. Select Custom MOC.
summary data file is prepared. Then, the 2. Select configuration objects of the base
CME exports base station data based on the stations to be exported and the save path
configuration objects selected in the wizard. for the file where the base station data is
to be exported.

Copyright © Huawei

After the export is complete, you can click the link in the dialog box to open the exported file.
----End
 Configure data in the exported file.

− Summary data file, see Editing a Summary Data File (Customization Tool-based).
 (Applies only to CME R17C10 and later versions.)For details about how to edit a summary data file
with scenarios differentiated, see Customizing and editing the Summary Data File with Scenarios
Differentiated (Example).
 (Applies only to CME R17C10 and later versions.)If you have added the Function Type field in the
Base Station Transport Data sheet when customizing a summary data file, you can set this
parameter to the RAT you want to import when editing the file. For example, UMTS and LTE data is
specified in the file. If you want to import only the UMTS data into the CME, set Function Type to
UO.
− Custom MOC, see Editing a Summary Data File (MOC Export-based).
 Import the summary data file in which data about RATs to be introduced has been edited
into the CME.
> Import Data > Import Base Station Multimode Expansion Data (CME client mode) or
import the summary data file for introducing RATs.
Step 2 Click and select the summary data file to be imported.
Step 3 Click Next and select co-MPT base stations for which you want to expand RATs.
If... Then...
The imported 1. Click Next and select base stations you want to create.
summary data file 2. (Optional) Select Best Effort.
contains only data NOTE
about base stations  If Best effort is selected, the CME skips the error information and
continues the import. When the import is complete, the CME rolls back
only incorrect base station data.
 If Best effort is not selected, the CME rolls back all the imported data if
the import fails.
contains data about NOTE
both base station  If Best effort is selected, the CME skips the error information and
controllers and base continues the import. When the import is complete, the CME rolls back
stations only incorrect base station data.
the import fails.
3. Optional: To generate configuration scripts in a wizard, select
Export scripts and perform the following operations:

Copyright © Huawei
If... Then...
a. Select a mode for generating scripts.

NOTE
 To generate scripts of logical base stations in the same file, select Batch.
 To generate scripts of logical base stations in different files by base

station, select One by one.
b. Specify a save path for scripts.
4. (Optional) Set an encryption mode for exported scripts.
 No: The exported scripts do not have encryption passwords
and no encryption passwords are required when you loading
projects.
 Yes: The exported scripts have encryption passwords. When
loading projects, you have to enter encryption passwords by
performing the following operations:
NOTE
If an encrypted password has been set for the exproted script, you cannot
check the script on the local PC. Instead, you have to check it using the script
executor.
1. Select Yes.
2. Click Set Password. In the displayed dialog box, enter the encryption
3. Click OK.
Step 4 (Optional and required when the new RATs include GSM) Click Next to set import options.
Set the start ID, frequency hopping attributes, and channel rules based on planned data.
Step 5 Click Next. The CME starts the import.
If... Then...
The import Click Finish to exit the wizard.

succeeds
The import 1. View the failure report, or double-click the error message in the error list
fails to open the summary data file and locate the cell where the error data
exists.
2. Modify error data based on the error message.
3. After data is corrected, click Retry to import the summary data file
again.
----End
8.3.2 Configuring UMTS Data

This section describes how to prepare and adjust UMTS data when UMTS is used as the
original and new modes.

Copyright © Huawei
The following table list the configuration method when UMTS works as the original mode.
Table 1.1 UMTS working as the original mode

o Type
Separate Equipment a) The CME template is used to configure Adjusting

-MPT data the summary data file in batches (UMTS Separate-MPT
application). Device Data
or decrease.
Transmissi a) Adjust the transmission data of the base Adjusting
on data station and controller together through Separate-MPT
batch adjustment over the Iub interface. Transmission Data
b) Adjust the transmission data of the base
station through batch configuration of the
summary data file (UMTS application).
Radio data The CME template is used to configure Adjusting
the summary data file in batches (UMTS Separate-MPT
application). Radio Data
Co- Equipment a) The CME template is used to configure Adjusting Co-MPT
MPT data the summary data file in batches (SRAN Device Data
application).
or decrease.
Transmissi The CME template is used to configure Adjusting Co-MPT
on data the summary data file in batches (SRAN Transmission Data
application).
Radio data The CME template is used to configure Adjusting Co-MPT
the summary data file in batches (SRAN Radio Data
application).
The following table list the configuration method when UMTS works as the new mode.
Table 1.2 UMTS working as the new mode

o Type
Separate Equipment, The CME template is used to deploy a 8.3.2.4.1Separate-

-MPT transmissio new site using the summary data file. In MPT
n, and this scenario, the equipment, transmission,

Copyright © Huawei

o Type
radio data and radio data shares one summary data

file.
Co- Equipment, The CME template is used to introduce 8.3.2.4.2Co-MPT
MPT transmissio RATs using the summary data file (SRAN
n, and application).
radio data

when the original mode is UMTS. The equipment data to be adjusted includes the antenna and
8.3.2.1.1 Separate-MPT
When the original mode is UMTS, you need to use the summary data file for batch
configuration (UMTS application) on the CME. If only the RF-related equipment data (RXU
data file.
----End
The procedure for exporting and importing the summary data file for batch configuration is as
follows:
Procedure
 Exporting NodeB data for batch configuration.
Step 1 On the menu bar of the planned data area, choose UMTS Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode) or CME > UMTS
Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client
batches.

Copyright © Huawei
Step 2 In the Scenario drop-down list, select NodeB Bulk Configuration or Co-MPT BTS Bulk
Configuration based on the NodeB configuration.
Step 3 Select NodeBs whose data you want to reconfigure and click Next.
file.
 (Applies only to CME R17 and later versions.) To export a summary data file with the Operation
following steps:
 (Applies only to CME R17C10 and later versions.) If you need to use a summary data file with
and editing the Summary Data File with Scenarios Differentiated (Example).
----End
 Open the exported summary data file and modify the file as planned.

Copyright © Huawei
You are advised to convert the summary data file to an MOC-integration view and edit
the data. For detailed operations, see Editing a Summary Data File for Batch
Configuration (MOC-Integration View).
follows:
Procedure
 Export a summary data file for NodeB RF adjustment.
Step 1 On the menu bar, choose UMTS Application > Export Data > Export Base Station RF
Adjustment Data. A dialog box is displayed for you to export NodeB data for RF capacity
expansion.
Step 2 Set parameters displayed in the dialog box and specify the base station controller and base
station whose data you want to export.
1. Select an RF adjustment scenario.
2. Select the versions of the base station controller and base stations whose data is to be
exported.
3. In the NE list, select the base stations whose data you want to export.

Export Mode Step

MOs you want to export in 2. If you need to manually edit sector equipment data in the
the wizard directly and exported summary data file, select Manually edit sector
MOs. a summary data file with the Operation column, select
4. Select MOs to be exported.
NOTE
 This export mode is not applicable to adjustment of only RF data
on the base station controller side.
 The CME adds MOs that support reconfiguration. You can adjust
the MOs as required. If the MOs to be reconfigured do not exist
in the list, you can use the tool for customizing a summary data
file to customize a summary data file for RF adjustment and then
perform operations in RF adjustment template mode.
RF adjustment template: 1. Select RF adjustment template.
Export data based on the 2. Select the prepared summary data file in RF adjustment
MOs contained in a data file.
prepared file.

Copyright © Huawei
Export Mode Step


Step 5 After the export succeeds, click Finish.
----End
 Import the summary data file for NodeB RF adjustment.

Step 1 On the menu bar of the CME, choose UMTS Application > Import Data > Import Base
Station RF Adjustment Data. A dialog box is displayed.
Step 3 Optional: Select Delete redundant RF equipment data.
When selecting base stations in the NE list, you can select base stations and then click Export to export
the selected base stations as a file for future selections.
If the file is unavailable when you select base stations by importing a file, you can click Export to
Step 6 To generate configuration scripts in the wizard, select Export scripts and perform the
To save scripts of logical base stations in the same file, select Batch.
To save scripts of logical base stations in separate files by base station, select One
by one.
If you have reconfigured cell frequencies, the CME generates scripts only using Batch. In the
reconfiguration scenario, the CME generates neighboring cell adjustment scripts, which cannot be
separated by base station.

Copyright © Huawei
SRAN12.0 or later.
chain/ring.
i. Select Yes.
ii. Click Set Password. In the displayed dialog box, enter the encryption
iii. Click OK.
error information.

----End
8.3.2.1.2 Co-MPT
configuration (SRAN application) on the CME. If only the RF-related equipment data (RXU

Copyright © Huawei
data file.
----End
(SRAN application) is as follows:
Procedure

Copyright © Huawei
file.
following steps.
----End
together.

Copyright © Huawei
If... Then...
base stations in
the preceding step
station controllers
and base stations
in the preceding
step
step
NOTE
click Next.
NOTE
base station data.
import fails.
NOTE
----End
follows:
Procedure

Copyright © Huawei
to export.
to export.


NOTE
prepared file.

----End

Copyright © Huawei
equipment data.
One by one.
SRAN12.0 or later.
chain/ring.

Copyright © Huawei
가 Select Yes.
다 Click OK.

to the second TRX.
NOTE
NOTE
as follows:
MAGroup.

Copyright © Huawei
NOTE
cell to TCHs.
existing cell.
following rules:
NOTE
TRXs belong.

error information.

----End

Copyright © Huawei

when the original mode is UMTS. The transmission data to be adjusted includes the following
MOs: IP, IPPATH, SCTPLINK, CPBEAR, and IPRT.
In separate-MPT scenarios where the original mode is UMTS, if only the base station data
needs to be adjusted, use the summary data file for batch configuration (GSM application) on
the CME to configure transmission data. If the data of the base station and controller needs to
be adjusted together, use the Iub batch adjustment data.
----End
(UMTS application) is as follows:
Procedure
batches.

Copyright © Huawei
file.
following steps:
----End

Copyright © Huawei
To reconfigure Iub interface data in batch, perform the following steps:
The procedure for exporting the Iub interface data for batch reconfiguration is as follows:
Procedure
Export Iub Bulk Configuration Data (CME client mode) or CME > UMTS Application
> Export Data > Export Iub Bulk Configuration Data (U2000 client mode). A dialog box
is displayed for you to export Iub bulk configuration data, as shown in Figure 1.1.
Figure 1.1 Exporting Iub bulk configuration data
Step 3 Select NEs whose data is to be reconfigured and the NE versions.
The CME can export Iub data about both the base station controller and base stations and can
also export Iub data only about the base station controller.
Export Iub data 1. Select UMTS controller and select a base station controller
about both the version.
base station 2. Select NodeB and select a NodeB version.

Copyright © Huawei
controller and NOTE

NodeBs NodeBCommon indicates that the NodeB version is V100R016.
3. Select NodeBs from the list, and click Next.
You can select base stations in the NE list. You can also click
Load to quickly select base stations defined in the file by
importing a file.
NOTE
 When selecting base stations in the NE list, you can select base stations and
then click Export to export the selected base stations as a file for future
selections.
 If the file is unavailable when you select base stations by importing a file,
you can click Export to obtain a file, edit the file, and then click Load to
import the file into the CME.
Export Iub data 1. Select UMTS controller and select a base station controller
only about the version.
base station 2. Clear NodeB.
controller 3. Select a base station controller in the NE list, and click Next.
You can select base station controllers in the NE list. You can also
click Load to quickly select base station controllers defined in the
file by importing a file.
NOTE
 When selecting base station controllers in the NE list, you can select base
station controllers and then click Export to export the selected base station
controllers as a file for future selections.
 If the file is unavailable when you select base station controllers by
importing a file, you can click Export to obtain a file, edit the file, and then
click Load to import the file into the CME.
Step 4 Select an export mode.
If... Then...
A summary data file is available and 1. Select Bulk configuration template.

you expect to export data based on 2. In Bulk configuration data file, select the
the objects contained in the file prepared file and export configuration data from
NOTE the CME based on the MOs in this file.
 The NE version in the Cover sheet 3. In Export path, specify a save path for the file
of the selected file must be the same that contains the exported data.
as that selected in 3.
 To export NodeB data between
products, you have to select the
summary data file for the destination
base station controller. The version
of the base station controller
contained in the summary data file
must be the same as the SPC version
under the same R version for the
base station controller selected in 3.
No summary data file is available 1. Select Custom MOC.

2. (Applies only to CME R17 and later versions.)

Copyright © Huawei
If... Then...
To export a summary data file with the
Operation column, select Add the Operation
column.
For NodeB V100R016, a summary data file with
the Operation column is not supported.
3. (Optional and required only when the base
station controllers are in RAN16.0 and later
versions and you have to export base station
data between products) Select Other UMTS
controller version and select a version.
The version must be the same as the SPC
version under the same R version of the base
station controller selected in 3.
4. Select objects you want to export and specify a
save path for the exported file.
NOTE
By default, objects related to the Iub interface have been
added. You can adjust the objects as required.
----End
The procedure for importing the Iub interface data for batch reconfiguration is as follows:
Procedure
Step 1 On the menu bar of the planned data area, choose UMTS Application > Import Data >
Import Iub Bulk Configuration Data (CME client mode) or CME > UMTS Application >
Import Data > Import Iub Bulk Configuration Data (U2000 client mode). A dialog box is
displayed for you to import Iub batch reconfiguration data.
Step 2 Select a file to be imported and set whether to generate configuration scripts through a wizard.
If... Then...
Configurat Clear Export script by wizard and click Next.

ion scripts
do not
need to be
generated
using a

Copyright © Huawei
If... Then...
wizard
(scripts are
generated
by
exporting
increment
al scripts
in the
future.)
Configurat Select Export script by wizard and click Next. Then, set the sequence for
ion scripts generating scripts as required.
need to be 1. Select Batch or One by one to generate all logical base station scripts in
generated one script file or generate scripts by base station, respectively.
NOTE
When multiple NodeBs share MOs at the bottom link layer, such as MOs ETHIP,
PPPLNK, and MPGRP, if the script generation mode is set to One by one, primary
information (information about the subrack and slot numbers of an interface board)
about these MOs cannot be modified if the related IP addresses are not changed.
Otherwise, data may conflict after being imported into the CME.
2. (Optional) If One by one is selected, click Up or Down to adjust the
sequence for running base station scripts.
3. Specify a save path for the script file.
4. (Optional) To enable the CME to automatically start the script executor
after a script is generated successfully in the wizard, select Launch the
script executor if the task is successful.
 No: The exported scripts do not have encryption passwords and no
encryption passwords are required when you loading projects.
 Yes: The exported scripts have encryption passwords. When loading
projects, you have to enter encryption passwords by performing the
NOTE
If an encrypted password has been set for the exproted script, you cannot check the
script on the local PC. Instead, you have to check it using the script executor.
1. Select Yes.
3. Click OK.
Step 3 (Optional) Set information about transport data reconfiguration as required.
If... Then...
The NodeB in the selected file Select Update ATM/IP address from RNC to
contains only Iub data on the RNC the NodeB that does not exist in the
side and you need to enable summary/IUB file.
automatic update of the Iub data on

Copyright © Huawei
If... Then...
the NodeB side based on the control  This option is available only when the
plane IP address, user plane IP imported file contains only controller data.
address, OMCH IP address, and  This function is available only when the
NodeB ATM address for the Iub following condition is met: On the RNC, the
interface on the RNC side same local IP address is configured for
multiple SCTPLNK records on the RNC,
and the same local IP address is configured
for multiple IPPATH records.
 The base station script is generated only when
the logical NodeB in the imported Iub bulk
configuration data has the corresponding
physical NodeB.
 This function applies only to single-mode
base stations and co-MPT base stations
(UO). For co-MPT base stations that contain
multiple RATs, the CME does not
automatically update the transport data on
the NodeB base on the Iub interface data on
the RNC.
Delete the existing transport data of Select Overwrite the Iub data (Do not inherit
the Iub interface and reconfigure the MOCs those do not exist in the summary
the data based on the transport data file).
in the summary data file This option is available only for a summary
data file without the Operation column.
Step 4 Click Next. The CME starts to import data.
If... Then...
The import Click Finish.

is successful If you do not select Launch the script executor and load the project after
the wizard is closed, you need to manually start the script executor to load
the project in the future. For detailed operations, see the manual startup
process in Activating Data Using the Script Executor.
NOTE
If the CME detects that the parameter values of a shared object in the imported
summary data file conflict, it displays the conflict information in the following
scenarios:
 If a parameter value in the summary data file conflicts with an existing value in the
planned data area, the CME displays the conflict information and the conflict
locating information.
 If multiple parameter values conflict in the summary data file (for example, the
parameter values of the same object are the same under different base stations), the
CME displays only conflict information.
 If a parameter has the preceding two types of conflicts, the CME provides locating
information about only one data conflict, and displays other conflict information.
You can check whether to modify the configuration data based on the displayed
information.
The import 1. You can view the error report. You can also double-click an error

Copyright © Huawei
If... Then...
fails message in the error list area. The CME opens the imported file and
locates the error data cell in the file.
3. After the modification, click Retry to import the file.
----End
8.3.2.2.2 Co-MPT
configuration (SRAN application) on the CME to configure transmission data.
----End
Procedure

Copyright © Huawei
file.
following steps.

Copyright © Huawei
----End
together.
If... Then...
base stations in
the preceding step
station controllers
and base stations
in the preceding
step
step
NOTE
click Next.
NOTE

Copyright © Huawei
If... Then...
base station data.
import fails.
NOTE
----End

the original mode is UMTS. The radio data to be adjusted includes the MOs related to the cell,
TRX, and sector.
When the original mode is UMTS in separate-MPT scenarios, you need to use the summary
data file for batch configuration (SRAN application) on the CME to configure radio data.
----End
The procedure for exporting and importing data of a separate-MPT base station (with the
original mode of UMTS) for batch configuration is as follows:
Procedure

Copyright © Huawei
batches.
file.
following steps:
----End

Copyright © Huawei
8.3.2.3.2 Co-MPT
When the original mode is UMTS in co-MPT scenarios, you need to use the summary data
file for batch configuration (SRAN application) on the CME to configure radio data.
----End
Procedure

Copyright © Huawei
file.
following steps.

Copyright © Huawei
----End
together.
If... Then...
base stations in
the preceding step
station controllers
and base stations
in the preceding
step
step
NOTE
click Next.
NOTE

Copyright © Huawei
If... Then...
base station data.
import fails.
NOTE
----End
8.3.2.4 Adjusting Transmission, Device, and Radio Data

This section describes how to configure data in both separate-MPT and co-MPT scenarios
when UMTS works as the new mode. The CME templates for the two scenarios are different.
----End
The following table lists the corresponding CME template and reference for each scenario.
Table 1.1 UMTS working as the new mode

o Type

-MPT transmissio new site using the summary data file. In MPT
n, and this scenario, the equipment, transmission,
radio data and radio data shares one summary data
file.
radio data

Copyright © Huawei
When the new mode is UMTS in separate-MPT scenarios, deploy a new site using the
summary data file on the CME.
Configure the primary mode of a separate-MPT base station.
Procedure
Step 1 On the menu bar of the planned data area, choose CME > SRAN Application > MBTS
Application > MBTS RAT Priority Settings (U2000 client mode) or SRAN Application >
MBTS Application > MBTS RAT Priority Settings (CME client mode). A dialog box is
displayed for you to set priorities of the RATs that comprise a multimode base station.
 If the current primary and secondary RATs are inconsistent with the planned ones,
perform Step2 through Step3.
 If the current primary and secondary RATs are consistent with the planned ones, perform
Step3.
Step 2 Change the primary and secondary RATs according to the separate-MPT base station type.
The selected RAT is the primary RAT, and the other is the secondary RAT.
LTE_TDD indicates only the LTE TDD base stations that are supported since SRAN11.0, and
no LTE FDD or NB-IoT cells can be added for such base stations.
Step 3 Click OK. A dialog box is displayed, indicating that the settings are successful.
Step 4 Click OK.
----End
Create a summary data file.

 Customize a summary data file (insecure networking).
Procedure
Step 1 Open the summary data file in the basic scenario by using the function of customizing a
summary data file.
1. On the menu bar, choose Advanced > Customize Summary Data File (CME client
mode) or CME > Advanced > Customize Summary Data File (U2000 client mode). A
dialog box is displayed for you to open the summary data file.
− To adjust the sheets, configuration objects, and parameter names in a user-defined
summary data file, select Custom to select a user-defined summary data file.
− To use a default summary data file, select Default, GBTS/NodeB/eNodeB
Summary, NodeB, NodeB version, and Scenario Basic Summary Template in
sequence.

Copyright © Huawei
You are advised to select the default summary data file Scenario Basic Summary Template. The causes
are as follows:
 Scenario Basic Summary Template is the minimum set of configuration parameters for base
station creation. After you select information required for creating base stations, such as the link
mode, telecom operator sharing mode, and security information on the customization wizard, the
CME automatically adds related parameters to the summary data file according to your selection.
You can use the customization wizard to combine base station creation scenarios, reducing
redundant parameters generated in the summary data file.
 Other default summary data files are classified by scenario and contain all parameters in the related
scenarios. Therefore, the following problems may occur:
 Redundant parameters are generated.
 A summary data file fails to be verified due to data collision when the customization wizard is used.
You can learn the introduction to scenarios by checking the information displayed on the GUI of the
summary data file.
3. After the configuration is complete, click OK. The main window for customizing a
summary data file is displayed, as shown in Figure 1.1.
Figure 1.1 Window for customizing a summary data file
1 Tab page, which displays a set of NE configuration parameters. This area can be
customized.
NOTE
You can drag a sheet to adjust its sequence.
2 NE configuration parameter navigation tree, which consists of NE configuration

objects and parameters. An NE configuration object consists of multiple NE
configuration parameters. This area cannot be modified.
3 Table, which lists the mappings between the parameter groups and parameters in a
summary data file and the NE configuration objects and parameters, respectively.
NE configuration objects and parameters are not editable. Parameter groups and
parameters in a summary data file can be customized.
 : indicates a modified record.
 : indicates an added record. Such tags will not be displayed next time after you

Copyright © Huawei
save the summary data file.

NOTE
 When the values of NE MOC and NE Attribute are empty in a record, the parameter is a
new one in the summary data file and there is no mapping between the parameter and NE
configuration objects.
This parameter is referenced by other configuration parameters. If this parameter is not
referenced, the parameter value does not take effect.
 If multiple NE configuration parameters are in the same summary parameter group and
share the same name, they are combined into a column in the generated summary data
file.
 Editable records are highlighted in white; Records that are not editable are highlighted in
; Records that can be deleted but cannot be modified are highlighted in .
Step 2 Start the wizard for customizing a summary data file, and customize basic and transport
parameters in a summary data file. Figure 2.1 shows the operation example.
The parameter specifications defined in the basic base station creation wizard must be lower than those
provided by NEs. If the planned data exceeds the defined parameter specifications, you can manually
customize data after completing operations by following the wizard.
Figure 2.1 Operations on the wizard
Tip1 The configuration sequence is displayed as "protocol layer + configuration

object." Configure data from the bottom to the top and from base stations

Copyright © Huawei
to base station controllers based on the protocol layers and NE types.

After the operations in the wizard are complete, a customization report is
generated. The report displays user-specified information, automatically
added MOs and planned parameter values (excluding default values), and
information that needs to be set manually.
Tip2 Configure data based on the planned data in each step on the wizard.
Step 3 (Optional and required when the summary data file customized on the wizard does not contain
all parameters to be configured) Manually customize parameters to be configured in the
summary data file.
If you need Then...

to...
Add a tab page Figure 3.1 shows an operation example.

Add Figure 3.2 shows an operation example.
parameters on
a tab page
Figure 3.1 Example of adding a tab page
Figure 3.2 Example of adding parameters on a tab page

Copyright © Huawei
Observe the following items during the customization:

 The parameter marked in red is the primary key parameter under the configuration
object. When adding a parameter, you must add the primary key parameter under the
configuration object to which the parameter belongs.
 Only one configuration object can be customized on the XXXX Pattern orXXXX List
tab page.
 A configuration object must not be allocated to different parameter groups on the
Common Data tab page.
One configuration object can be customized only on one tab page or on one tab page and
the Common Data tab page.
 Parameter names in the same parameter group cannot be duplicate.
 Parameter group names and parameter names cannot be empty.
Step 4 Click to verify validity of the edited summary data file. Then, modify the file based on the
verification result.
If the verification fails, you can double-click the error message. Then, the CME automatically
locates the error. You have to rectify the error until the verification succeeds.
If an alarm is generated indicating that the branch parameter does not exist in the verification result, you
need to determine whether to customize the parameter to the summary data file based on the planned
data. The alarm does not affect the subsequent operation of saving data.
Step 5 When the verification is successful, click to save the summary data file (this button applies
only to a user-defined summary data file), or click to save the file to a local PC. If you
perform copy and paste operations when saving the file, the file will fail to be saved.
----End
 Customize a summary data file (secure networking).
Procedure
summary data file.
Summary, NodeB, NodeB version, and Scenario Basic Summary Template in
sequence.
are as follows:

Copyright © Huawei
 Scenario Basic Summary Template is the minimum set of configuration parameters for base
 Other default summary data files are classified by scenario and contain all parameters in the related
summary data file.
customized.
NOTE

NOTE

Copyright © Huawei
file.
Step 2 Start the wizard for customizing a summary data file, and customize basic, transport, and
security data in the file.
1. Use the customization wizard to customize basic and transport data. Figure 2.1 shows an
operation example.

object." Configure data from the bottom to the top and from base stations
to base station controllers based on the protocol layers and NE types.

Copyright © Huawei
2. Use the security wizard to customize security-related data. Figure 2.2 shows an operation
example.
When configuring data in the wizard, observe the following:

 Parameters with * in the wizard are mandatory.
Optional parameters are configured based on site requirements. For example, when configuring the
CRL file, you need to set the user name and password for the CRL server based on site requirements.
 Steps in a wizard to be emphasized on are marked with Tip in the preceding figure. You can view
related descriptions based on site requirements.
Tip 1  When multi-level CA certificates in the certificate chain provided by you are
stored separately, configure multiple CA records.
 When you provide a certificate chain file, configure a certificate chain record.
Tip 2 Configure security gateway information records based on collected IKE and
IPsec algorithms and combination status of these algorithms provided by you.
For example, two IKE algorithms, two IPsec algorithms, and only three IKE and
IPsec algorithm combination methods are provided. You need to configure only
three security gateway information records.
Tip 3  Sequence Number of IPsec tunnel of IPsec tunnels configured for the same
port cannot be duplicate.
 Values of Sequence number of SeGW corresponding to this tunnel
corresponding to Sequence number of SeGW configured in the preceding
step.
Tip 4 After the operations in the wizard are complete, a customization report is
generated. The report displays user-specified information, automatically added
MOs and planned parameter values (excluding default values), and information
that needs to be set manually.

Copyright © Huawei
summary data file.
If you need Then...

to...

parameters on
a tab page

tab page.

Copyright © Huawei
----End
Edit a summary data file.
Procedure
Step 1 Open a user-defined summary data file.
Step 2 On the menu bar of the Excel file, click Add-Ins.
If the macro function is not displayed under Add-Ins, verify the following settings:
 In Microsoft Office Excel 2003, the macro function must be enabled and the macro
security level must be set to Medium.
 In Microsoft Office Excel 2007 and Excel 2010, the macro function must be enabled.
Step 3 Edit basic data.
1. Edit global data, which is the same for all base stations, on the Common Data sheet.
Such parameters include the telecom operator information and OSS IP address.
2. Edit basic information, which is different for all base stations, on the Base Station
Transport Data sheet or the MO list sheet (XXXX List). For example:
− Edit the basic base station information including the base station name and type on
the Base Station Transport Data sheet.
− Edit base station functions and locations on the corresponding MO list sheet
(XXXX List).
Step 4 Edit device data.
1. The configuration data of devices uses the values in the base station template. Therefore,
you need to set the name of the prepared base station template on the Base Station
Transport Data sheet.

Copyright © Huawei
Only the default template name is displayed in the drop-down list for selecting a template in the
summary data file. Therefore, before selecting a user-defined template, you have to click
to add the user-defined template name to the drop-down
list.
Information about the user-defined template must be consistent with that about the existing template on
the CME.
2. Edit clock data and time data on the Common Data sheet.
Step 5 Edit transport data.
1. Edit the data planned for each base station, such as the IP address, subnet, and port
number, on the Base Station Transport Data sheet.
2. Edit the parameters for the MOs corresponding to each interface on the corresponding
MO sheets (XXXX List or XXXX Pattern). For example, device IP addresses and SCTP
links are MOs.
a. If the value of a parameter on the XXXX Pattern sheet varies among base stations,
you can click and select the parameter that needs to be referenced.
Microsoft Excel automatically generates the reference path for the parameter in the
summary data file. Figure 1 provides an example for using the reference function.
Advantage of the reference function: The value of one parameter can be referenced
on multiple XXXX Pattern sheets. Therefore, after a reference relationship is set,
you only need to change the referenced parameter value and do not need to modify
the parameters on the XXXX Pattern sheets even if the referenced parameter value
changes.
Restriction of the reference function:
가 The parameters to be referenced must be on the Common Data or Base
Station Transport Data sheet.
나 If a branch parameter has been set to be referenced by another parameters, the
summary data file does not enable or disable the parameters controlled by the
branch parameter. The CME will still check accuracy of all the parameters
during the import.
Figure 5.1 Example for using the reference function

Copyright © Huawei
Under the Device IP Address object in the preceding figure, to retain the parameter
value of IP Address on port 0 in slot 7 of subrack 0 in cabinet 0 the same as the
parameter value of IP 1 under the NodeB IP address object on the Base Station
Transport Data sheet, you have to enter the path of the referenced parameter Base
Station Transport Data\NodeB IP address\IP 1 as the parameter value of IP
Address on port 0 in slot 7 of subrack 0 in cabinet 0. The CME assigns a parameter
value based on the reference path.
b. During IP route configuration, if the value obtained after a logic AND operation is
performed on the IP address and subnet mask is not equal to the IP address, you
need to use the macro function to convert the IP address to
an IP address that meets the rule.
The IP address verification rule is the same as the NE configuration rule. That is,
after a logical AND operation is performed on the IP address and subnet mask, the
obtained value is equal to the IP address.
For detailed operations related to macro functions, see Figure 5.2.
Figure 5.2 Settings
1 Specify the sheet, parameter group, and parameter name that correspond
to the IP addresses and subnet masks to be calculated.
2 Specify locations in the summary data file for the calculated IP addresses
and subnet masks.
 To use the calculated IP addresses and subnet masks to overwrite
existing data in the summary data file, perform the following
operations:

Copyright © Huawei
1. Select Select Filling Column.

2. Specify the names of the parameter group and parameter mapped
to the data to be overwritten.
 To add a row next to the parameter specified in step 1 and show the
calculated IP addresses and subnet masks in the added row, perform
1. Select Add Filling Column.
2. Enter the names of the parameter group and parameter to be
displayed in the row.
3 Click Add and add a conversion rule. You can repeat steps 1 and 2 to add
multiple conversion rules.
4 This function provides the following calculation methods:
 Non-32-bit subnet mask: After you enter IP addresses and subnet
masks, a logic AND operation is performed on them. The obtained
network codes replace the IP addresses, and the subnet masks are
replaced with 255.255.255.255.
 32-bit subnet mask: The IP addresses remain the same. The entered
subnet masks are replaced with 255.255.255.255.
5 Click OK. Excel starts the calculation based on the preset information.
Step 6 Add radio data.

Click the cell sheet, set the value of each parameter and the template name based on the
planned data.
to add the user-defined template name to the drop-down
list.
the CME.
Step 7 Configure automatic deployment data about the base stations to be created.
Click the Auto Deployment sheet and set the value of each parameter based on the planned
data.
Step 8 Close the modified summary data file.
----End
Import the summary data file.
Procedure
Step 1 On the menu bar of the planned data area, choose UMTS Application > Import Data >
Import Base Station Summary Data (CME client mode) or CME > UMTS Application >
Import Data > Import Base Station Summary Data (U2000 client mode). A dialog box is
displayed for you to create base stations using a summary data file.

Copyright © Huawei
Step 2 Click and select the file you want to import.

If redundant device objects exist after the data for creating base stations in the summary data
file and data in the template are combined, after Delete redundant RF equipment data is
selected, the CME automatically deletes the device objects and subobjects that have not been
referenced by the cell.
Step 3 Click Next and select base stations you want to create.
You are advised not to select sample base stations.
Step 4 (Optional) Select Best effort.

This option is available only when the imported summary data file contains base station
controller data.
 If Best effort is selected, the CME skips the error information and continues the import.
When the import is complete, the CME rolls back only incorrect base station data.
Step 5 (Optional and required when the CME generates scripts during the import of the summary
data file) Select Export Scripts and specify a save path for the scripts.
 If Batch is selected, NodeB scripts are generated in the same file.
 If One by one is selected, the generated scripts are divided by NodeB. One file is
generated for each NodeB, and shared object data is generated in an independent file.
If... Then...
The import Click Finish.

is successful
The import 1. You can view the error report. You can also double-click an error
fails message in the error list area. The CME opens the imported file and
----End
Import the RNP data file.

Copyright © Huawei
Procedure
Step 1 Obtain the radio data planning file 3G Radio Network Planning Data Template.xls from
client installation path\client\client\Data\BSC version\Model\local\language\Template.
Step 2 Open the file and reconfigure the data as planned.
You are not allowed to modify the parameters marked in gray in the file.
Step 3 Import the radio data planning file.
The CME imports the file by NE. For example, the CME contains data about 10 NEs and data
only about one of the NEs is contained in the file to be imported. After the file is imported, the
CME reconfigures data only about the specified NE in the file. For data about the other NEs,
the CME reconfigures only the interlocked data.
 When you modify a parameter that supports automatic synchronization in UCELL, the CME
automatically updates the parameters (for example, external cell information) that are associated
with this parameter on other NEs in the planned data area. For details about associated parameters,
see the Associated_Parameter.xls file in client installation
path\client\client\Data\Common\AssociatedParameter\language. You can use the inter-U2000
neighboring cell management function to ensure that the cell associated parameters are consistent in
different U2000 systems.
 In the RNC in Pool management scenario, you need to configure neighboring cell data only on the
master RNC and then import the configured data. After the master RNC is configured, you can
synchronize the configuration of the backup RNC with the configuration of the master RNC using
the consistency check function.
1. On the menu bar of the planned data area, choose UMTS Application > Import Data >
Import Radio Network Planning Data (CME client mode) or CME > UMTS
Application > Import Data > Import Radio Network Planning Data (U2000 client
mode). A dialog box is displayed for you to select files.
2. Specify TXT, XLS, or XLSM as the format of the file you want to import, and click Add
File to select a data planning file.
3. Click Next. A dialog box is displayed for you to select an import mode.
4. Select configuration objects you want to import.
− Table 1.1 describes the configuration objects in Basic Info.
− Table 1.2 describes the configuration objects in External Cell Type and
Neighboring Cell Relationship Type and the import modes.
 When importing neighbor relationships, the CME automatically skips those involving cells that do
not exist.
 If cell indexes are not set for the external cell data in the imported file, the CME allocates the related
cell indexes based on whether the cell names exist on the CME. The allocation mechanism is as
follows:
 If an external cell exists on the CME, the CME changes the cell index to the existing one.
 If an excel cell does not exist on the CME, the CME automatically allocates a cell index.

Copyright © Huawei
Table 1.1 Configuration objects in Basic Info

Configuration Whet Whet Results After the File Is Imported into the
Object her her CME
Data Data
Exists Exists
on in the
the File
CME
NodeB Yes Yes The CME contains the existing data and the
NodeB data in the file and reallocates NodeB
IDs.
No Yes The CME adds the NodeB data in the file.
Yes No Data on the CME remains unchanged.
Cell Yes Yes The CME overwrites the existing data using the
cell data in the file.
No Yes The CME adds the cell data in the file. The
principles for selecting a cell template are as
follows:
 In the data planning file, if the
TEMPLATENAME parameter of the cell is
empty, the CME creates the cell by using the
cell template selected in the dialog box.
 In the data planning file, if you specify a cell
template name in the TEMPLATENAME
parameter, the CME creates the cell by using
the cell template specified in the file. In this
case, the cell template selected in the dialog
box does not take effect.
NOTE
 If data about the URA, LAC, SAC, RAC, and SPG
referenced by the cell does not exist on the CME,
the CME automatically adds the data.
 You need to manually delete the URA, LAC, SAC,
RAC, and SPG that are no longer referenced by any
cell from the general configuration window.
Yes No Data on the CME remains unchanged.

Physical NodeB Yes Yes The CME overwrites the existing data using the
radio data radio data of the physical NodeBs in the file.
NOTE No Yes Data on the CME remains unchanged.
 Radio data of
physical NodeBs Yes No Data on the CME remains unchanged.
only in
V100R016 can
be imported.
 You can
reconfigure radio
data of physical
NodeBs in other
versions in
batches by using

Copyright © Huawei
Configuration Whet Whet Results After the File Is Imported into the
Object her her CME
Data Data
Exists Exists
on in the
the File
CME
a summary data
file.

r the the Import
Object Object
Data Data
Exists Exists in
on the the File
CME
data in the file.
the file.
process the data.
NOTE
the Append mode.
 Parameter values for the inverse neighboring
 If no external cell exists, the CME also

Copyright © Huawei
r the the Import
Object Object
Data Data
Exists Exists in
on the the File
CME
 If any external cells exist and the parameter

 Neighbor
relationships
are updated
on a cell
basis.
 External cells
are updated
on a base
station
controller
basis.

5. Click Next. The CME starts the import.
The CME automatically filters invalid parameters in the file when verifying the import.
6. Perform operations based on the import result.
Table 1.3 Operation description

If... Then...
The import The CME displays a message stating that the import is successful. Click
is Finish.
successful NOTE
To prevent frequency band conflicts occur in GUL multi-mode base stations after
frequency refarming, you can select Start frequency overlapping check and
bandwidth verification on RF channels of MBTSs after closing the wizard after the
data is imported. The CME starts to verify cell frequency and bandwidth configuration
data of the GUL multi-mode base stations.

Copyright © Huawei
If... Then...
The import 1. The dialog box displays a message stating that error data exists in the data
fails planning file. You can view the error report or double-click the error
record in the lower part of the dialog box to open the data file. The CME
locates the error data row in the file according to the error information in
the dialog box. Then, you can reconfigure data based on the information.
If the location information in the error record is incomplete, the CME
cannot automatically locate the row in the file.
2. After reconfiguring data, you can click Retry to import the data again.
NOTE
If rule verification fails during the import of multiple files, all data is rolled back.
----End
8.3.2.4.2 Co-MPT
When the new mode is UMTS, you need to use the summary data file for introducing RATs
(SRAN application) on the CME to configure data.
----End
Procedure

Copyright © Huawei
Option Operation
to be exported.

----End


Copyright © Huawei
UO.
into the CME.
If... Then...
the import fails.
the import fails.
NOTE

projects.
NOTE

Copyright © Huawei
If... Then...
executor.
1. Select Yes.
3. Click OK.
If... Then...

succeeds
exists.
again.
----End
8.3.3 Configuring LTE Data

The following is data for LTE (FDD), LTE (TDD), and LTE (NB-IoT).
This section describes how to prepare and adjust LTE data when LTE works as the original
and new modes.
The following table lists the configuration method when LTE works as the original mode.
Table 1.1 LTE working as the original mode

o Type
Separate Equipment The CME template is used to configure 8.3.3.1.1Separate-

-MPT data the summary data file in batches (LTE MPT
application).
Transmissi The CME template is used to configure 8.3.3.2.1Separate-
on data the summary data file in batches (LTE MPT
application).

Copyright © Huawei

o Type
Radio data The CME template is used to configure 8.3.3.3.1Separate-

the summary data file in batches (LTE MPT
application).
Co- Equipment The CME template is used to adjust RF 8.3.3.1.2Co-MPT
MPT data data (SRAN application).
Transmissi The CME template is used to configure 8.3.3.2.2Co-MPT
on data the summary data file in batches (SRAN
application).
Radio data The CME template is used to configure 8.3.3.3.2Co-MPT
the summary data file in batches (SRAN
application).
The following table lists the configuration method when LTE works as the new mode.
Table 1.2 LTE working as the new mode

o Type

-MPT transmissio new site using the summary data file. MPT
n, and
radio data
radio data

when the original mode is LTE. The equipment data to be adjusted includes the antenna and
When the original mode is LTE in separate-MPT scenarios, you need to use the summary data
file for batch configuration (LTE application) on the CME. If only the RF-related equipment
data (RXU board/TRX/cell capacity) needs to be adjusted, you can adjust RF data using the
summary data file.

Copyright © Huawei

----End
(LTE application) is as follows:
Procedure
Step 1 On the menu bar of the planned data area, choose LTE Application > Export Data > Export
Base Station Bulk Configuration Data (CME client mode) or CME > LTE Application >
Export Data > Export Base Station Bulk Configuration Data (U2000 client mode). A
dialog box is displayed for you to export the data you want to reconfigure in batches.
Step 2 Select the batch reconfiguration scenario, base station version, and related base stations, and
click Next.
If users need to adjust only global radio parameters, cell parameters, and cell algorithm parameters, set
Adjust Data by to Cell. Then, the CME will automatically displays cell-related parameters, which helps
users filter and select cells.
file.
following steps.
----End
planned data. For detailed operations, see Editing a Summary Data File for Batch
Configuration.
If you want to change the values of multiple parameters to the same value, for example,
in scenarios where you want to change device IP addresses, you can convert the
summary data file into the MOC-integration view and then edit the data. For detailed
operations, see Editing a Summary Data File for Batch Configuration (MOC-Integration
View).

Copyright © Huawei
Step 1 On the menu bar of the planned data area, choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode) or CME > LTE
Application > Import Data > Import Base Station Bulk Configuration Data (U2000
client mode). A dialog box is displayed for you to import the data that has been reconfigured
in batches.
Step 2 Select files to import and data types to adjust, and click Next.
Step 3 Select base stations whose data you want to import, and click Next.
Step 4 After the import is complete, click Finish.

error information.

----End
Th procedure for exporting and importing the summary data file for RF adjustment is as
follows:
Procedure
 Export a data file for RF adjustment.
Base Station RF Adjustment Data (CME client mode) or CME > LTE Application >
Export Data > Export Base Station RF Adjustment Data (U2000 client mode). The wizard
dialog box is displayed.
Step 2 Configure parameters in the wizard and select base stations whose data you want to export.
1. Select a scenario where you want to export base station data.
2. Select a version of base stations whose data you want to export.
3. Select base stations whose data you want to export from the NE list.

Copyright © Huawei


objects you want to export 2. (Applies only to CME R17C10 and later versions.)If you
in the wizard directly and need to manually edit sector equipment data in the
enable the CME to export exported summary data file, select Manually edit sector
data based on the selected equipment data.
objects. 3. (Applies only to CME R17 and later versions.)To export
a summary data file with the Operation column, select
(Applies only to CME R17C10 and later versions.)The
Manually edit sector equipment data option is selected
by default.
NOTE
prepared file.

----End
 Import the data file for RF adjustment.

Import Base Station RF Adjustment Data (CME client mode) or CME > LTE
Application > Import Data > Import Base Station RF Adjustment Data (U2000 client
mode). The wizard dialog box is displayed.
equipment data.

Copyright © Huawei
For details about rules for loading the file, see File Rules.
Step 5 Select Best effort.
Step 6 To generate configuration scripts in the wizard, select Export scripts and perform the
i. Select Yes.
ii. Click Set Password. In the displayed dialog box, enter the encryption
iii. Click OK.
error information.

----End
8.3.3.1.2 Co-MPT
When the original mode is LTE in co-MPT scenarios, you need to use the summary data file
for batch configuration (SRAN application) on the CME. If only the RF-related equipment

Copyright © Huawei
data (RXU board/TRX/cell capacity) needs to be adjusted, you can adjust RF data using the
summary data file.
----End
(LTE application) is as follows:
Procedure

Copyright © Huawei
file.
following steps.
----End
together.

Copyright © Huawei
If... Then...
base stations in
the preceding step
station controllers
and base stations
in the preceding
step
step
NOTE
click Next.
NOTE
base station data.
import fails.
NOTE
----End
follows:
Procedure

Copyright © Huawei
to export.
to export.


NOTE
prepared file.

----End

Copyright © Huawei
equipment data.
One by one.
SRAN12.0 or later.
chain/ring.

Copyright © Huawei
가 Select Yes.
다 Click OK.

to the second TRX.
NOTE
NOTE
as follows:
MAGroup.

Copyright © Huawei
NOTE
cell to TCHs.
existing cell.
following rules:
NOTE
TRXs belong.

error information.

----End

Copyright © Huawei

the original mode is LTE. The transmission data to be adjusted includes the following MOs:
IP, IPPATH, SCTPLINK, CPBEAR, and IPRT.
file for batch configuration (LTE application) on the CME to configure transmission data.
----End
original mode of LTE) for batch configuration is as follows:
Procedure
click Next.
file.
following steps.

Copyright © Huawei
----End
Configuration.
View).
in batches.

error information.

----End
8.3.3.2.2 Co-MPT
for batch configuration (SRAN application) on the CME to configure transmission data.

Copyright © Huawei
----End
Procedure

Copyright © Huawei
file.
following steps.
----End
together.
If... Then...

Copyright © Huawei
If... Then...
base stations in
the preceding step
station controllers
and base stations
in the preceding
step
step
NOTE
click Next.
NOTE
base station data.
import fails.
NOTE
----End

the original mode is LTE. The radio data to be adjusted includes the MOs related to the cell,
TRX, and sector.
file for batch configuration (LTE application) on the CME to configure radio data.

Copyright © Huawei

----End
original mode of LTE) for batch configuration is as follows:
Procedure
click Next.
file.
following steps.
----End
Configuration.

Copyright © Huawei
View).
in batches.

error information.

----End
8.3.3.3.2 Co-MPT
for batch configuration (SRAN application) on the CME to configure radio data.
----End

Copyright © Huawei
Procedure
file.

Copyright © Huawei
following steps.
----End
together.
If... Then...
base stations in
the preceding step
station controllers
and base stations
in the preceding
step

Copyright © Huawei
If... Then...
step
NOTE
click Next.
NOTE
base station data.
import fails.
NOTE
----End
8.3.3.4 Adjusting Transmission, Equipment, Radio Data (LTE Only)

This section describes how to configure data in both separate-MPT and co-MPT scenarios
when LTE works as the new mode. The CME templates for the two scenarios are different.
----End
The following table lists the corresponding CME template and reference for each scenario.

Copyright © Huawei
Table 1.1 LTE working as the new mode

o Type

-MPT transmissio new site using the summary data file. MPT
n, and
radio data
radio data
To add LTE as a new mode using a summary template for new site deployment is similar to
add an eNodeB. For detailed operations, see section "Creating eNodeBs" in "Creating Base
Stations" in 3900 Series Base Station Initial Configuration Guide.
Create a summary data file.
 Customize a summary data file (insecure networking).
Procedure
summary data file.
2. Perform operations.
Summary, eNodeB, eNodeB version, and Scenario Basic Summary Template in
sequence.
are as follows:
1. Scenario Basic Summary Template is the minimum set of configuration parameters for base
2. Other default summary data files are classified by scenario and contain all parameters in the related
summary data file.

Copyright © Huawei
customized.
NOTE

NOTE
file.
Step 2 Start the wizard for customizing a summary data file, and customize basic and transport
parameters in a summary data file.

Copyright © Huawei
operation example.
Figure 2.1 Operations in the wizard for creating eNodeBs

object". Configure the information from bottom to top based on protocol
layers.
2. Optional: Use the customization wizard to customize RAN sharing data. Figure 2.2
shows an operation example.

Copyright © Huawei
Figure 2.2 Operations in the RAN sharing wizard
Parameters with * in the wizard are mandatory. Optional parameters are configured based on site
requirements.
After the operations in the wizard are complete, a customization report is generated. The report displays
user-specified information, automatically added MOs and planned parameter values (excluding default
values), and information that needs to be set manually.
summary data file.
If you need Then...

to...

parameters on
a tab page

Copyright © Huawei

tab page.
----End
 Customize a summary data file (secure networking).
Procedure
summary data file.
2. Perform operations.

Copyright © Huawei

Summary, eNodeB, eNodeB version, and Scenario Basic Summary Template in
sequence.
are as follows:
1. Scenario Basic Summary Template is the minimum set of configuration parameters for base
2. Other default summary data files are classified by scenario and contain all parameters in the related
summary data file.
customized.
NOTE


Copyright © Huawei
NOTE
file.
Step 2 Start the wizard for customizing a summary data file, and customize basic, transport, and
security data in the file.
operation example.
Figure 2.1 Operations in the wizard for creating eNodeBs

object". Configure the information from bottom to top based on protocol
layers.

Copyright © Huawei

2. Use the security wizard to customize security-related data. Figure 2.2 shows an operation
example.
When configuring data in the wizard, observe the following:

 Parameters with * in the wizard are mandatory.
Optional parameters are configured based on site requirements. For example, when configuring the
CRL file, you need to set the user name and password for the CRL server based on site requirements.
 Steps in a wizard to be emphasized on are marked with Tip in the preceding figure. You can view
related descriptions based on site requirements.
Tip 1  When multi-level CA certificates in the certificate chain provided by you are
stored separately, configure multiple CA records.
 When you provide a certificate chain file, configure a certificate chain record.
Tip 2 Configure security gateway information records based on collected IKE and
IPsec algorithms and combination status of these algorithms provided by you.
For example, two IKE algorithms, two IPsec algorithms, and only three IKE and
IPsec algorithm combination methods are provided. You need to configure only
three security gateway information records.
Tip 3  Sequence Number of IPsec tunnel of IPsec tunnels configured for the same
port cannot be duplicate.
 Values of Sequence number of SeGW corresponding to this tunnel
corresponding to Sequence number of SeGW configured in the preceding
step.
Tip 4 After the operations in the wizard are complete, a customization report is
generated. The report displays user-specified information, automatically added
MOs and planned parameter values (excluding default values), and information
that needs to be set manually.

Copyright © Huawei
3. Optional: Use the customization wizard to customize RAN sharing data. Figure 2.3
shows an operation example.
Figure 2.3 Operations in the RAN sharing wizard
Parameters with * in the wizard are mandatory. Optional parameters are configured based on site
requirements.
After the operations in the wizard are complete, a customization report is generated. The report displays
user-specified information, automatically added MOs and planned parameter values (excluding default
values), and information that needs to be set manually.
summary data file.
If you need Then...

to...

parameters on
a tab page

Copyright © Huawei

tab page.

Copyright © Huawei
----End
Edit a summary data file.
Procedure
Step 1 Open a user-defined summary data file.
Step 2 On the menu bar of the Excel file, click Add-Ins.
If the macro function is not displayed under Add-Ins, verify the following settings:
 In Microsoft Office Excel 2003, the macro function must be enabled and the macro
security level must be set to Medium.
 In Microsoft Office Excel 2007 and Excel 2010, the macro function must be enabled.
Step 3 (Optional) Edit the data that has been negotiated with telecom operators in the LLD data file.
Only eNodeBs support the LLD data file.
You need to convert a summary data file into an LLD data file first. After configuring data in
the LLD data file, convert the LLD data file into a summary data file.
This function is available only after you select the LLD column of related parameters when customizing
a summary data file.
1. In the summary data file, click to convert it into an LLD data file.
The sheet named Common Data maps COMMON. The other sheet names remain
unchanged.
2. Edit the prepared data in the LLD data file.
By default, the CME provides the parameter values of Qos based on the network design. You can
manually delete records from or add records to Qos as required. After the LLD data file has been
converted into the summary data file, parameters are automatically edited in the corresponding locations
in the summary data file according to the conversion principles shown in Figure 3.1. The existing data in
the summary data file is overwritten.
Figure 3.1 Conversion principles for the parameters under the Qos object
If Service Type has two records IKE and Ping under the Qos object in the LLD data
file, the mapping (1) does not map the two records.

Copyright © Huawei
3. Click to apply the data in the LLD data file to the summary data
file.
Step 4 Edit basic data.
1. Edit global data, which is the same for all base stations, on the Common Data sheet.
Such parameters include the telecom operator information and OSS IP address.
2. Edit basic information, which is different for all base stations, on the Base Station
Transport Data sheet or the MO list sheet (XXXX List). For example:
− Edit the basic base station information including the base station name and type on
the Base Station Transport Data sheet.
− Edit base station functions and locations on the corresponding MO list sheet
(XXXX List).
Step 5 Edit device data.
1. The configuration data of devices uses the values in the base station template. Therefore,
you need to set the name of the prepared base station template on the Base Station
Transport Data sheet.
to add the user-defined template name to the drop-down list.
the CME.
2. Edit clock data and time data on the Common Data sheet.
Step 6 Edit transport data.
1. Edit the data planned for each base station, such as the IP address, subnet, and port
number, on the Base Station Transport Data sheet.
2. Edit the parameters for the MOs corresponding to each interface on the corresponding
MO sheets (XXXX List or XXXX Pattern). For example, device IP addresses and SCTP
links are MOs.
a. If the value of a parameter on the XXXX Pattern sheet varies among base stations,
you can click and select the parameter that needs to be referenced.
Microsoft Excel automatically generates the reference path for the parameter in the
summary data file. Figure 6.1 provides an example for using the reference function.
Advantage of the reference function: The value of one parameter can be referenced
on multiple XXXX Pattern sheets. Therefore, after a reference relationship is set,
you only need to change the referenced parameter value and do not need to modify
the parameters on the XXXX Pattern sheets even if the referenced parameter value
changes.
Restriction of the reference function:
가 The parameters to be referenced must be on the Common Data or Base
Station Transport Data sheet.
나 If a branch parameter has been set to be referenced by another parameters, the
summary data file does not enable or disable the parameters controlled by the
branch parameter. The CME will still check accuracy of all the parameters
during the import.

Copyright © Huawei
Figure 6.1 Example for using the reference function
Under the DevIPPattern object in the preceding figure, to retain the parameter
value of Mask on port 0 in slot 7 of subrack 0 in cabinet 0 the same as the
parameter value of PeerMask under the OMCH object on the Base Station
Transport Data sheet, you have to enter the path of the referenced parameter
eNodeB Transport Data\OMCH\PeerMask as the parameter value of Mask on
port 0 in slot 7 of subrack 0 in cabinet 0. The CME assigns a parameter value based
on the reference path.
b. During IP route configuration, if the value obtained after a logic AND operation is
performed on the IP address and subnet mask is not equal to the IP address, you
need to use the macro function to convert the IP address to an
IP address that meets the rule.
The IP address verification rule is the same as the NE configuration rule. That is,
after a logical AND operation is performed on the IP address and subnet mask, the
obtained value is equal to the IP address.
For detailed operations related to macro functions, see Figure 6.2.

Copyright © Huawei
Figure 6.2 Settings
1 Specify the sheet, parameter group, and parameter name that correspond
to the IP addresses and subnet masks to be calculated.
2 Specify locations in the summary data file for the calculated IP addresses
and subnet masks.
 To use the calculated IP addresses and subnet masks to overwrite
existing data in the summary data file, perform the following
operations:
1. Select Select Filling Column.
2. Specify the names of the parameter group and parameter mapped
to the data to be overwritten.
 To add a row next to the parameter specified in step 1 and show the
calculated IP addresses and subnet masks in the added row, perform
1. Select Add Filling Column.
2. Enter the names of the parameter group and parameter to be
displayed in the row.
3 Click Add and add a conversion rule. You can repeat steps 1 and 2 to add
multiple conversion rules.
4 This function provides the following calculation methods:
 Non-32-bit subnet mask: After you enter IP addresses and subnet
masks, a logic AND operation is performed on them. The obtained
network codes replace the IP addresses, and the subnet masks are
replaced with 255.255.255.255.

Copyright © Huawei
 32-bit subnet mask: The IP addresses remain the same. The entered
subnet masks are replaced with 255.255.255.255.
5 Click OK. Excel starts the calculation based on the preset information.
Step 7 Add radio data.

Click the cell sheet, set the value of each parameter and the template name based on the
planned data.
to add the user-defined template name to the drop-down list.
the CME.
Step 8 Configure automatic deployment data about the base stations to be created.
Click the Auto Deployment sheet and set the value of each parameter based on the planned
data.
Step 9 Close the modified summary data file.
----End
Import the summary data file.
Procedure
Import Base Station Summary Data (CME client mode) or CME > LTE Application >

If... Then...
The import is Click Finish.

successful
The import fails 1. You can view the error report. You can also double-click an error
message in the error list area. The CME opens the imported file and

Copyright © Huawei
If... Then...
----End
Prepare and specify the RNP data file.
Procedure
Import Base Station Summary Data (CME client mode) or CME > LTE Application >

If... Then...
The import is Click Finish.

successful
The import fails 1. You can view the error report. You can also double-click an error
message in the error list area. The CME opens the imported file and
----End
Import the RNP data file.
Procedure
Step 1 On the menu bar of the planned data area, choose CME > LTE Application > Import Data
> Import Radio Network Planning Data (U2000 client mode) or LTE Application >
Import Data > Import Radio Network Planning Data (CME client mode). A dialog box is
displayed for you to import planned radio data.
Step 2 Click Add, select the prepared radio data planning file(s) or directories containing the files,
and click Next. A dialog box is displayed for you to select eNodeBs.

Copyright © Huawei
 If you edit the eNodeBs to be imported on the SiteList sheet in the file, the dialog box
displays the eNodeBs that are available in both the file and the current planned data area.
By default, the eNodeBs on the SiteList sheet are selected.
 If you do not edit the SiteList sheet in the file, the dialog box displays the eNodeBs that
are available in both the file and the current planned data area. By default, all eNodeBs
are selected.
Step 3 Select the eNodeBs you want to import and click Next.
Step 4 Select cells and neighbor relationships you want to import into the CME, and select an import
mode. Then, click Next.
After you select an import mode, the CME uses the primary key (such as cell ID) to determine
whether the objects exist on the CME and in the file, and then determines how to process the
data. Table 1.1 describes the import modes and import results.

r the the Import
Object Object
Data Data
Exists Exists in
on the the File
CME
data in the file.
the file.
process the data.
NOTE
the Append mode.
1. Parameter values for the inverse neighboring

Copyright © Huawei
r the the Import
Object Object
Data Data
Exists Exists in
on the the File
CME
2. If no external cell exists, the CME also
3. If any external cells exist and the parameter

 Neighbor
relationships
are updated
on a cell
basis.
 External cells
are updated
on a base
station
controller
basis.

Step 5 The CME starts to import the data. During the import, the CME automatically corrects
external LTE cell data based on the adjusted source cell data to ensure data consistency. After
the data is imported, click Finish.
Table 1.1 Operation description

If... Then...
The import The CME displays a message stating that the import is successful.
succeeds NOTE
(Applies only to CME R17C10 and later versions.)To prevent frequency band
conflicts occur in GUL multi-mode base stations after frequency refarming, you
can select Start frequency overlapping check and bandwidth verification on
RF channels of MBTSs after closing the wizard after the data is imported. The
CME starts to verify cell frequency and bandwidth configuration data of the GUL

Copyright © Huawei
If... Then...
multi-mode base stations.
The import fails The dialog box displays errors in the data planning file. You can view
the error report, or double-click an error record in the lower part of the
dialog box to open the file. The CME locates the error data row in the
file. Then, you can reconfigure data. If the location information in the
error record is incomplete, the CME cannot automatically locate the
row in the file.
----End
8.3.3.4.2 Co-MPT
When the new mode is LTE, you need to use the summary data file for introducing RATs
(SRAN application) on the CME to configure data.
----End
Procedure

Copyright © Huawei
Option Operation
to be exported.

----End


Copyright © Huawei
UO.
into the CME.
If... Then...
the import fails.
the import fails.
NOTE

projects.
NOTE

Copyright © Huawei
If... Then...
executor.
1. Select Yes.
3. Click OK.
If... Then...

succeeds
exists.
again.
----End
8.3.3.5 Adjusting Transmission, Equipment, Radio Data (FDD+TDD)

1. Obtain and customize the LTE summary data file.
 In the CME tool, choose CME > Advanced > Customize Summary Date File.

Copyright © Huawei
 Select the scenario and choose the corresponding version.

To reconstruct an FDD eNodeB or a TDD eNodeB into an FDD+TDD eNodeB, set
Scenario to NodeB/eNodeB/USU Bulk Configuration.
To reconstruct a G*U*L(FDD) base station into a G*U*L(FDD+TDD) base station, set

Scenario to Co-MPT BTS Bulk Configuration.

Copyright © Huawei
 Click in the upper left corner and select the corresponding scenario.
1. To reconstruct an FDD eNodeB to an FDD+TDD eNodeB or reconstruct a
G*U*L(FDD) base station to a G*U*L(FDD+TDD) base station, select Adjusting
eNodeB Configurations > Reconstructing an FDD eNodeB into an FDD+TDD
eNodeB from Scenario list.
2. To reconstruct a TDD eNodeB into an FDD+TDD eNodeB, choose Adjusting eNodeB
Configurations > Reconstructing a TDD eNodeB into an FDD+TDD eNodeB from
Scenario list.

Copyright © Huawei
The procedure for customizing a summary data file is as follows:
Procedure
Step 1 On the menu bar, choose Advanced > Customize Summary Data File (CME client mode)
or CME > Advanced > Customize Summary Data File (U2000 client mode). A dialog box
is displayed for you to open the summary data file.
Step 2 Perform operations as required.
 To adjust the sheets, configuration objects, and parameter names in a user-defined
 To use a default summary data file, select related information in sequence. To select
information for a single-mode base station or co-MPT base station (LO), perform the
− For a single-mode base station, select Default, NodeB/eNodeB Bulk
Configuration, eNodeB, and base station version.
− For the co-MPT base station (LO), select Default, Co-MPT BTS Bulk
Configuration, LTE, and base station version.
Step 3 After the configuration is complete, click OK. The main window for customizing a summary
data file is displayed, as shown in Figure 3.1.

Copyright © Huawei
Parameters marked with * in area 3 are mandatory, and parameters in gray cannot be deleted or
modified.
Step 4 In the upper left part of the customization window, click . The application scenario dialog
box is displayed. Select a scenario-based template as required.
Step 5 Optional: If the scenario-based template does not contain all parameters to be configured,
you need to manually customize the parameters in the summary data file.
If you need Then...

to...

parameters on
a tab page

Copyright © Huawei

tab page.
It is recommended that, on the Base Station Transport Data tab page, each eNodeB is configured with
one or no configuration data record under the MO to be customized.
----End
2. Based on the customized template, export the data to be adjusted and specify data in the
1. To reconstruct an FDD eNodeB into an FDD+TDD eNodeB, specify data by referring to
Example: Mode Transition from LO (FDD) to LO (FDD+TDD).

Copyright © Huawei
2. To reconstruct a TDD eNodeB into an FDD+TDD eNodeB, specify data by referring to

Example: Mode Transition from LO (TDD) to LO (FDD+TDD).
3. To reconstruct a G*U*L(FDD) base station a G*U*L(FDD+TDD) base station, specify
data by referring to Example: Mode Transition from G*U*L(FDD) to
G*U*L(FDD+TDD).
3. Import the template file.
The procedure for exporting and importing the summary data file is as follows:
Procedure
click Next.
file.
following steps.
----End
Configuration.

Copyright © Huawei
View).
in batches.

error information.

----End
8.3.3.6 Adjusting Transmission, Equipment, Radio Data (FDD+NB-IoT)

 Specify the scenario and choose the corresponding version.

Copyright © Huawei
To reconstruct an FDD eNodeB to an FDD+NB-IoT eNodeB, specify Scenario to

NodeB/eNodeB/USU Bulk Configuration.
To reconstruct a G*U*L(F) co-MPT base station to a G*U*L(FM) co-MPT base station,

specify Scenario to Co-MPT BTS Bulk Configuration.

Copyright © Huawei
To reconstruct an FDD eNodeB to an FDD+NB-IoT eNodeB or reconstruct a G*U*L(F) co-

MPT base station to a G*U*L(FM) co-MPT base station, select Adjusting eNodeB
Configurations > Reconstructing an FDD eNodeB into an FDD+TDD eNodeB from
Scenario list.
The procedure for customizing a summary data file is as follows:
Procedure

Copyright © Huawei
modified.
If you need Then...

to...

parameters on
a tab page

Copyright © Huawei

tab page.
----End
To reconstruct an FDD eNodeB into an FDD+NB-IoT eNodeB, specify data by referring to
4.24Example: Mode Transition from L(F) to L(FM).

Copyright © Huawei
For details about how to export and import the summary data file, see the following
procedure:
Procedure
click Next.
file.
following steps.
----End
Configuration.
View).

Copyright © Huawei
in batches.

error information.

----End
8.3.3.7 Adjusting Transmission, Equipment, Radio Data (TDD+NB-IoT)

 Specify the scenario and choose the corresponding version.

To reconstruct a TDD eNodeB to a TDD+NB-IoT eNodeB, specify Scenario to
NodeB/eNodeB/USU Bulk Configuration.

Copyright © Huawei
To reconstruct a G*U*L(T) co-MPT base station to a G*U*L(TM) co-MPT base station,

specify Scenario to Co-MPT BTS Bulk Configuration.
To reconstruct a TDD eNodeB to a TDD+NB-IoT eNodeB or reconstruct a G*U*L(T) co-
MPT base station to a G*U*L(TM) co-MPT base station, select Adjusting eNodeB

Copyright © Huawei
Configurations > Reconstructing a TDD eNodeB into a TDD+NB-IoT eNodeB from

Scenario list.
The procedure for customizing the summary data file is as follows:
Procedure

Copyright © Huawei
modified.
If you need Then...

to...

parameters on
a tab page

Copyright © Huawei

tab page.
----End
To reconstruct a TDD eNodeB into a TDD+NB-IoT eNodeB, specify data by referring to
4.25Example: Mode Transition from L(T) to L(TM) for China Mobile.

Copyright © Huawei
The procedure for exporting and importing the summary data file is as follows:
Procedure
click Next.
file.
following steps.
----End
Configuration.
View).

Copyright © Huawei
in batches.

error information.

----End
8.4 Preparing Data Through Co-MPT Reconstruction,

Mode Addition, and RF Adjustment
You can perform mode transition by referring to this section if base station configurations are
similar, and transmission reconstruction and hardware reconstruction are not required.
The scenario described in this section involves co-MPT reconstruction, mode addition, and
RF adjustment.
Description:
A NodeB is to be reconstructed into a UL co-MPT base station. The name of the NodeB is
U3706 and that of the eNodeB is L3706. Capacity expansion and RF adjustment are to be
performed on boards after reconstruction into a co-MPT base station.
Suggestion:
You can use the Base Station Reconstruction Express function on the standalone CME to
create a customized project and perform co-MPT reconstruction, mode addition, and RF
adjustment in the project.
Configuration information about inherited equipment data:
 If data is to be migrated from the source base station, equipment data is specified in the
Board Style sheet of the summary data file. For detailed data configurations, see 8.4.4
Filling In Reconstruction Project Data.
 If data is to be inherited using the NEP-SD tool:

Copyright © Huawei
The base station design file generated by the NEP-SD tool is required, and the Board
Style sheet of the summary data file does not take effect.
To reuse the existing equipment in the source base station during co-MPT reconstruction,
perform the following steps:
1. On the NEP-SD main window, click or choose Project > New Project to create a
project. In the displayed dialog box, set Scene to Single-Site Expansion, Swap, and
Reconstruction or Batch-Site Expansion, Swap, and Reconstruction. Click OK.
2. Import existing configuration data and inventory data of the base station.
3. After the data is imported, right-click the base station name and choose Reconstruction
to modify the configurations.
4. After the modification, choose Data > Export BTS Configuration on the NEP-SD main
menu bar to export a base station design file.
As described in 8.4.4 Filling In Reconstruction Project Data, BTS Design File in the
Base Station Transport Data sheet will refer to this base station design file, and BTS
Design Cell ID in the cell-related sheets will refer to the cell IDs planned in this base
station design file. When importing data described in 8.4.5 Importing Reconstruction
Project Data, select Use BTS design file and select the directory in which the BTS
design file is saved.
8.4.1 Creating a Customized Project

On the menu bar of the CME, choose Advanced > Base Station Reconstruction Express >
Customize Reconstruction Project. In the displayed dialog box, perform the following
steps.
You can customize a project using either of the following methods on the CME:
 Selecting project types
You need to customize the list of MOs to be exported for each project type.

Copyright © Huawei
Figure 4.1 Selecting project types
Tip: Click Export or Import under each sub-project to select export or import options (the
CME provides defualt settings). No node data operations are involved.
 Selecting scenarios
You only need to perform simple configurations according to the scenario-specific
guideline on the CME. The CME automatically adds MOs to the summary data file and
configures the related parameters. Customization and edition of the summary data file
are simplified.

Copyright © Huawei
Figure 4.2 Selecting scenarios

Copyright © Huawei
8.4.2 Exporting the Project Template and Filling In Co-MPT

Reconstruction Data
This step is required because you need to reconstruct the NodeB into a co-MPT base station
first in this scenario.
1. Click to export the project template.
If the edited data in a project template needs to be inherited, select Inherited existing reconstruction
project data and the corresponding file. The CME copies data from corresponding parameter lists of the
Base Station Transport Data, Pattern, and List sheets to a new project template. (Data in the
following sheets cannot be inherited: base station name sheet of summary data files in the MOC-
Integration MOC View mode, RF Migration NEs Relationship, Auto Deployment, Board Style,
MBTS_BindInfo, Base Station CN SRN Adjustment, and co-MPT reconstruction-related sheets.)
2. In the exported template, fill in co-MPT reconstruction data in the following sheets:
GlobalPlanning, SitePlanning, MultiCpriChainMoveTemplate,
MultiBBUCombTemplate, and Auto Deployment.
Fill in the data according to the example.
3. After editing the file, save and close it.
8.4.3 Exporting Reconstruction Project Data

The following figure shows the detailed operations.
Skip this step if reconstruction data can be obtained from an LLD data file.To obtain the tool for
conversion from an LLD data file to a summary data file, contact the CME representative, Zhang Yi
(employee ID: 00334527).
If you need to configure the reconstruction data based on the configurations on the live network, export
the data on the live network and then modify the exported data.

Copyright © Huawei
Figure 4.3 Exporting the reconstruction project data

Copyright © Huawei

Copyright © Huawei
In this scenario, the NodeB must be reconstructed into a co-MPT base station first. You need to export
the project by template in step 2 and select the template edited in 8.4.2 Exporting the Project Template
and Filling In Co-MPT Reconstruction Data.
The CME reconstructs the NodeB into a co-MPT base station, and then exports the co-MPT base station
data to a summary data file.
After data is exported, the NE icon is changed from to and co-

MPT reconstruction from the NodeB is complete.
8.4.4 Filling In Reconstruction Project Data

Configure mode addition and RF adjustment data in the following sheets based on the data
plan:
Base Station Transport Data, UMTS Cell, LTE Cell, CELLOP, DEVIP, IPRT,
CPBEARER, IPPATH, SCTPLNK, EPGROUP, SCTPHOST, SCTPPEER,
SCTPTEMPLATE, USERPLANEHOST, USERPLANEPEER, ENODEBPATH,
CNOPERATOR, CNOPERATORTA, S1, X2, S1INTERFACE, X2INTERFACE, and
Board Style.
To prevent alarms generated during the mode transition from affecting other modes, set the
existing mode in the base station to the maintenance mode. The maintenance mode can be set
in the Application sheet when the reconstruction project data is filled in. This method is
supported by the base stations of SRAN11.0 and later versions. When the maintenance mode
is set in this sheet, the operations in Setting NE Maintenance mode are not required.
 You can use the tool for automatic coversion from an LLD data file to the List and Common sheets
of a summary data file in batches.
 For details about the tool for converting the LLD data, see Training Document_iManager U2000-
CME V200R017_Interconnection Between LLD Data File and Summary Data File. To obtain the
tool for conversion from an LLD data file to a summary data file, contact the CME representative,
Zhang Yi (employee ID: 00334527).
 If equipment data is to be inherited using the NEP-SD tool, BTS Design File in the Base Station
Transport Data sheet of the summary data file refers to the base station design file generated using
the NEP-SD tool. BTS Design Cell ID in the cell-related sheet of the summary data file refers to the
planned cell ID in this design file. The following figures show an example.
Example provides an example of data filling. You can fill in the file based on site conditions
by referring to the example.
Macro functions of Excel can help you set parameters. The following table lists the available
macro functions in this scenario.

Copyright © Huawei
Table 3.1 Macro functions

Macro Button Location Description
Base Station Only the default template

Transport Data, name is displayed in the
UMTS Cell, and drop-down list for selecting
LTE Cell sheets a template in the summary
data file. Therefore, before
selecting a user-defined
template, you have to click
this button to add the user-
defined template name to the
drop-down list.
Information about the user-
defined template must be
consistent with that about
the existing template on the
CME.
Sheets related to This function is used to
mode addition and convert the summary data
RF adjustment file into the style in which
sheets are displayed by base
station.
 Board Style sheet This function is used to
 Pattern sheet customize differentiated
parameters on the Base
 Sheet of a summary Station Transport Data
data file, which is sheet by adding reference
converted into the relationships. Then, the
MOC-integration parameter values on the
view by using Base Station Transport
Data sheet are used, and the
related data on each base
station sheet is updated
based on the reference
relationships.
Base Station This function is used to
Transport Data update the Base Station
sheet of a summary Transport Data sheet based
data file, which is on existing base station data
converted into the so that base station data can
MOC-integration be checked before the
view by using reconfiguration in the Base
Station Transport Data
sheet.
Base Station After data reconfiguration,
Transport Data this function is used to
sheet of a summary update each base station
data file, which is sheet based on reference
converted into the relationships and values on
MOC-integration the Base Station Transport
view by using Data sheet.

Copyright © Huawei
UMTS Cell and After the base station

LTE Cell sheets serving a cell is specified,
this function is used to
adjust the antenna ports of
the cell in the UMTS Cell or
LTE Cell sheet.
Board Style sheet This function is used to
specify or adjust baseband
processing boards for
baseband equipment.
Examples:
Example 1: Modify the location of a WBBP
Example 2: Add a baseband processing board

Copyright © Huawei
Tips:
 Added cells are in green. Mandatory cells are in blue. Cells that must be left blank are in
gray.
 The value of Board No. (Cabinet No._Subrack No._Slot No._n) can automatically be
generated. n indicates that the board is added. Specify other parameters according to the
data plan.
 When you need to associate an object with a board, select the number of the board to be
associated from the drop-down list box of the related parameter.
Example 3: Modify the relationship between antenna ports and cells under base station
named "nodeb"

Copyright © Huawei
Example 4: Add or adjust baseband equipment

Copyright © Huawei
Tip: If no baseband equipment is to be added, skip steps 1 to 4.

Example 5: Modify the relationship between TRX channels and cells under base station
named "01-GBTS"

Copyright © Huawei
8.4.5 Importing Reconstruction Project Data

Click to import the edited summary data file into the CME to complete the reconstruction.
If equipment data is to be inherited using the NEP-SD tool, select Use BTS design file and select the
directory of the base station design file, as shown in the following figure. Ensure that the summary data
file refers to the base station design file.

Copyright © Huawei
After data is exported, the NE icon is changed from to and

the reconstruction project is complete.
8.4.6 Exporting Scripts

To export auto-deployment data files, perform the following steps:
1. On the menu bar, choose Advanced > Export Auto Deployment Data. A dialog box is
displayed.
2. Select a deployment scenario, and click Next.
Select Site reconstruction and select the deployment list generated after operations in
8.4.3 Exporting Reconstruction Project Data are performed.

Copyright © Huawei
3. Select the base stations whose auto-deployment data is to be exported, and click Next.
4. Select a save path for the exported file and a method for processing data, and click Next.
5. View data in the base station deployment list, and click Next. The CME verifies data
correctness and exports the data.
If the parameter values displayed on the GUI are different from the data plan, you need to change the
parameter values based on the data plan. Otherwise, the deployment may fail.
6. Click Finish.
8.5 Preparing Data Through New Co-MPT Base Station

Deployment and Cell/Radio Parameter Inheritance
Overview
In mode transition, co-MPT reconstruction cannot be used if data on the live network needs
massive adjustments, such as transmission adjustment, conflict of subrack and slot numbers
among base stations in different modes, change of cabinet types, and inconformity of sector or
sector device numbers with site requirements after reconstruction. For these scenarios, new
base station deployment+RF migration can be used to perform mode transition, that is, deploy
a new co-MPT base station and migrate the radio data on the live network to the new base
station.
During migration of the radio data, RF, antenna, and baseband resources of the existing base
station can be reused, that is, these resources can be migrated to the target base station
together with the radio data. If the target base station is newly deployed, the radio global
parameters of a certain source base station can be migrated to it to improve the data
preparation efficiency of the target base station.

Copyright © Huawei
Principles
The CME supports migration of the baseband, RF unit, and cell data. If the data to be
migrated is inherited from the base station on the live network, it does not need to be filled in
the summary data file.
Table 1.1 Inheritance of data types of a base station

Data Type Support for Migration
Cabinet and subrack data No

Baseband data Yes
RF data Yes
Antenna data Yes
Cell data (including neighboring cell data) Yes
Radio global data Yes
Transmission data No
 If cells are migrated from the source base station to the target base station, network
optimization parameters are inherited automatically and the neighbor relationships are
automatically reconfigured.
 (Optional) Global radio objects of the source base station (for GSM/UMTS/LTE) can be
inherited to the target base station.
The following figure shows the migration (for detailed operations, see 8.5.4 Filling In Data
for New Base Station Deployment and RF Migration).

Copyright © Huawei

Copyright © Huawei
Operation Procedure
You can combine the repeated operations in the base station deployment scenario and data
migration scenario using the Base Station Reconstruction Express function on the CME to
improve reconstruction efficiency.

Copyright © Huawei
This document describes the base station deployment and RF migration operations that are
performed simultaneously using the Base Station Reconstruction Express function. For
separate operations, see 3900 Series Base Station Initial Configuration Guide and Base
Station RF Migration Guide respectively.
Specifications and Constraints

 The following lists the restrictions in RF migration.
− Only 3900 series base stations are supported. Micro base stations or LmapSites are
not supported.
− The base station version is the same before and after migration.
− Only 3900 series base stations are supported. Only intra-BSC/RNC migration is
allowed for GSM/UMTS base stations. For inter-BSC/RNC base stations, migration
to the same BSC/RNC must be performed at first.
− The RF data of multiple base stations can be migrated to one target base station.
However, global radio parameters of only one source base station can be inherited.
− The data of one base station can be migrated to only one target base station.
− RRUs under a base station can either be migrated out of or into the base station
during one migration.
− Inter-site cells are not allowed, for example, inter-site SFN cells.
− A summary data file excluding the Operation column does not support inter-site
SFN cells.
− A maximum of 70 base stations can be migrated at a time, that is, the total number
of source base stations or target base station is 35.

Copyright © Huawei
− Automatic function creation for a certain mode is not allowed on a co-MPT base
station. If the target base station lacks the function for the corresponding mode,
create the function manually.
− The following types of base stations are supported.
가 GSM site types
Scenario Source Base Station Target Base Station
RF data migration between  DBS3900_GSM  DBS3900_GSM

two GBTSs  BTS3900_GSM  BTS3900_GSM
 BTS3900A_GSM  BTS3900A_GSM
 BTS3900L_GSM  BTS3900L_GSM
 BTS3900AL_GSM  BTS3900AL_GSM
RF data migration from a  DBS3900_GSM  DBS3900
GBTS to an eGBTS  BTS3900_GSM  BTS3900
 BTS3900A_GSM  BTS3900A
 BTS3900L_GSM  BTS3900L
 BTS3900AL_GSM  BTS3900AL
RF data migration between  DBS3900  DBS3900
two eGBTSs  BTS3900  BTS3900
 BTS3900A  BTS3900A
 BTS3900L  BTS3900L
 BTS3900AL  BTS3900AL
나 UMTS site types

RF data migration  DBS3900_WCDMA  DBS3900_WCDMA

between two NodeBs  BTS3900_WCDMA  BTS3900_WCDMA
 BTS3900A_WCDMA  BTS3900A_WCDMA
 BTS3900L_WCDMA  BTS3900L_WCDMA
 BTS3900AL_WCDMA  BTS3900AL_WCDMA
 DBS3900-1U_WCDMA  DBS3900-1U_WCDMA
 BTS3900-1U_WCDMA  BTS3900-1U_WCDMA
다 LTE site types

RF data migration between 1. DBS3900_LTE 1. DBS3900_LTE

two eNodeBs 2. BTS3900_LTE 2. BTS3900_LTE
3. BTS3900A_LTE 3. BTS3900A_LTE
4. BTS3900L_LTE 4. BTS3900L_LTE
5. BTS3900AL_LTE 5. BTS3900AL_LTE

Copyright © Huawei

6. DBS3900A_LTE 6. DBS3900A_LTE
라 Co-MPT site types

Migration of RF data  DBS3900  DBS3900

between two GUL co-MPT  BTS3900  BTS3900
base stations
 BTS3900A  BTS3900A
 BTS3900L  BTS3900L
 BTS3900AL  BTS3900AL
 If new base station deployment and RF migration are performed using the Base Station
Reconstruction Express function and NE names of a mode of the new co-MPT base
station are the same as those of the source base station for RF migration on the live
network, the CME supports site overwriting, that is, the base station on the live network
is deleted and the new target base station inherits the transport data of the source base
station. This scenario has the following constraints:
− Site overwriting only supports the migration from a single-mode base station to a
co-MPT base station, but not from a co-MPT base station to another co-MPT base
station.
− If other adjustments are required in the reconstruction (such as primary key
adjustments), new base station deployment and RF migration must be performed
before other adjustments in customizing a project, that is, complete new base station
deployment and RF migration before performing other data adjustments.
− For multiple new co-MPT base stations, if NE names of a mode are the same as
those of some base stations in the live network, and different from those of some
base stations in the live network, RF migration must be performed in batches. (This
is only confined to the same mode.) For example, if NE names of GSM of the new
co-MPT base stations are the same as those of the base station in the live network
and the NE names of UMTS of the new co-MPT base stations are different from
those of the base station in the live network, RF migration can be performed at the
same time.
− If the NE names of LTE of a new co-MPT base station are the same as those of the
base station in the live network and site overwriting is required, it is recommended
that cell associated parameters be not modified in RF migration. That is because the
CME does not automatically reconfigures the associated radio parameters in this
scenario.
For details about cell associated parameters, see Associated_Parameter.xls under the client installation
path\client\client\Data\Common\AssociatedParameter\language directory.
− The following describes the base station-level data to be inherited on the base
station controller side in site overwriting scenarios.
가 If the transmission-related MOs listed in the following table are not defined in
the summary data file, they are inherited from the live network.

Copyright © Huawei
Primary keys of these MOs cannot be modified.
Mode MO to be Inherited
GSM ADJMAP, ADJNODE, IPMUX, IPPATH, IPPATHBIND, IPPM, BTSCTRLEX,

BTSSHARING
UMTS NCP, CCP, ADJNODE, ADJMAP, NODEBIP, SCTPLNK, ADJNODEIPBIND,
IPPATH, IPPATHBIND, IPMUX, IPPM, ADJNODEDIP, NODEBESN,
UNODEBLICENSE, IPPOOLMUX, IPOOLPM
나 For other MOs whose primary key parameters are defined in the summary data
file, their non-primary key parameters are inherited from the live network.
Script Export Mode

Figure 1.1 shows the scrip export mode.
Figure 1.1 Description of script export mode
Configuration About Inherited Equipment Data

 If data is to be migrated from the source base station, equipment data is specified in the
Board Style sheet of the summary data file. For detailed data configurations, see 8.5.4
Filling In Data for New Base Station Deployment and RF Migration.
 If data is to be inherited using the NEP-SD tool:
The base station design file generated by the NEP-SD tool is required, and the Board
Style sheet of the summary data file does not take effect.

Copyright © Huawei
To reuse the existing equipment in the source base station during co-MPT reconstruction,
perform the following steps:
a. On the NEP-SD main window, click or choose Project > New Project to create
a project. In the displayed dialog box, set Scene to Single-Site Expansion, Swap,
and Reconstruction or Batch-Site Expansion, Swap, and Reconstruction. Click
OK.
b. Import existing configuration data and inventory data of the base station.
c. After the data is imported, right-click the base station name and choose
Reconstruction to modify the configurations.
d. After the modification, choose Data > Export BTS Configuration on the NEP-SD
main menu bar to export a base station design file.
As described in 8.5.4 Filling In Data for New Base Station Deployment and RF
Migration, BTS Design File in the Base Station Transport Data sheet will refer to
this base station design file, and BTS Design Cell ID in the cell-related sheets will
refer to the cell IDs planned in this base station design file. When importing data
described in 8.5.5 Importing Data, select Use BTS design file and select the
directory in which the BTS design file is saved.
8.5.1 Customizing the Summary Data File and Creating a Project

1. (Optional) Customize the summary data file for base station deployment and RF
migration.
The customized summary data file is used for subsequent data exportation and filling. If the summary
data file is not customized, it can be automatically generated by the CME through selecting the MO after
a customized project is created.
From the main menu bar, choose Advanced > Customize Summary Data File. For
detailed customization operations, press F1 on the CME to view the Online Help.
− The following CME template is used to deploy a new base station using the
summary data file.

Copyright © Huawei
After customization, if the value of a parameter on a Pattern sheet varies among

base stations, you can add a reference relationship through the
function. After a reference relationship is set, you only need to change the
referenced parameter value.
For details about the customized template, see Summary Data File for Base Station
Deployment.
− The following CME template is used to migrate RF data using the summary data
file.
The CME provides three default templates according to scenarios in the following
table.

Copyright © Huawei
Scenario Sub-Scenario Recommended Remarks

Template Type
 Only cells are  Only RF modules RF migration Sector equipment
migrated and RF are involved, and summary data file and baseband
modules are not allocation of excluding the equipment are
migrated. sector equipment Operation column automatically
 RF modules and IDs is not configured.
cells are involved. If a summary data
migrated, and the  The complete data file excluding the
positions of RF of the target base Operation column
modules on the station instead of is used, you are
chain are the modified data advised to export the
replanned. is involved. data of both the
 Capacity  Hardware data in source and target
expansion or the site design base stations and
reduction (for document modify data
example, adding planned using the according to the
or deleting a cell) NEP-SD tool is final data of the base
is performed involved. station.
during migration.
 Sector equipment RF migration The binding
IDs are manually summary data file relationship between
configured including the cells and RF
instead of Operation column modules and the
automatic topology
allocation. information of the
 Only the data RRU chain are
modified during inherited from the
migration is source base station.
involved. If a summary data
file including the
RF modules and N/A RF migration Operation column
cells are migrated, summary data file is used, you can only
and the cell including the plan the modified
coverage and Operation column data.
positions of RF (migration by chain)
modules on the
chain remains
unchanged.
The sample summary data file includes the operators. For the customized summary
data file, see Summary Data File for RF Migration.
2. Create a customized project and define the new base station deployment and RF
migration as a reconstruction project.
On the menu bar of the CME, choose Advanced > Base Station Reconstruction Express
> Customize Reconstruction Project. The Customize Reconstruction Project dialog box
is displayed.

Copyright © Huawei
Figure 1.1 Creating a customized project
Tip 1: Basic information to be configured varies with the project type. The basic information
to be configured may include scenarios, RATs, and NE versions. For Base Station RF
Migration under SRAN, you need to select conversion tools for base station controller (BSC)
and base transceiver station (BTS) modules when RF data is to be migrated from a GBTS to
an eGBTS or co-MPT base station whose RATs include GSM.
 Name of the conversion tool for BSC modules:
SRANconvert_BSCModule_V***R***C**SPC***.zip To obtain the tool, visit the
http://support.huawei.com/carrier/ website, choose Support > Product Support > Wireless
Network > Wireless Network Common > SingleRAN > SingleRAN_MBSC > BSC6900
or choose Support > Product Support > Wireless Network > Wireless Network Common
> SingleRAN > SingleRAN_MBSC > BSC6910. Then, search for the name.
 Name of the conversion tool for BTS modules:
SRANconvert_GBTS&SRANModule_V***R***C**SPC***.zip To obtain the tool,

Copyright © Huawei
visit the http://support.huawei.com/carrier/ website, choose Support > Product Support

> Wireless Network > Wireless Network Common > SingleRAN >
SingleRAN_MBTS > BTS3900, and search for the name.
Tip 2: Select the import and export options of each function (the CME provides default option
settings) and set the parameters. No setting is required for NE data.
When setting the export options, you can select the summary data file customized in step 1 or
select the MO if the summary data file is not customized.
To set the export options, select Export Scripts. The CME generates script files on the base
station controller side after the data is imported.
 If One by one is selected, the CME separates the scripts on the base station controller side
by base station, which facilitates further delivery by base station.
 If Batch is selected, the scripts on the base station controller side are not separated, which
applies to the scenario where data of all base stations is uniformly delivered.
Tip 3: (Refer to this tip if the summary data file is not customized) Select the migration
scenario as planned when setting the export options for RF migration. (The summary data file
type to be exported on the CME and the default MO vary according to different scenarios.)
 If only Migrate CPRI chain and RXUs, CXUs, sectors, and sector equipment on the
chain. is selected, the CME exports the RF migration summary data file including the
Operation column.
 If only Migrate cell and its subobjects is selected, the CME exports the RF migration
summary data file excluding the Operation column. If hardware data needs to be
planned in the base station design file using the NEP-SD tool, select Plan hardware
data in the BTS design file.
 If both options are selected, the CME exports the RF migration summary data file
including the Operation column (migration by chain).
Click View and edit detailed information to configure the MOs to be exported.
8.5.2 Specifying NE Mapping for RF Migration

This step is required because you need to specify the source and target base stations for RF
migration first in this scenario.

Copyright © Huawei
In this scenario, the target base station is the new co-MPT base station to be deployed. You
need to specify the name of the base station before deployment.
1. Click to export the project template.
If the edited data in a project template needs to be inherited, select Inherited existing reconstruction
project data and the corresponding file. The CME copies data from corresponding parameter lists of the
Base Station Transport Data, Pattern, and List sheets to a new project template. (Data in the
following sheets cannot be inherited: base station name sheet of summary data files in the MOC-
Integration MOC View mode, RF Migration NEs Relationship, Auto Deployment, Board Style,
MBTS_BindInfo, Base Station CN SRN Adjustment, and co-MPT reconstruction-related sheets.)
2. In the RF Migration NEs Relationship sheet of the exported template, specify the
source and target base stations.
When specifying the source and target base stations, pay attention to the following:
 The Source NE and Target NE fields must be set to NE names.
 You can specify multiple source NEs and define the number of NEs using macro button Configure
Source NE Columns. Each column corresponds to a source base station.
 The Global Radio Reference field specifies the source base station of which the global radio
parameter settings are inherited by the target base station. Set this field to the identity of the base
station. For example, set Global Radio Reference to NodeB1 if the NE name of NodeB1 is n111,
the NE name of NodeB2 is n222, and the target base station inherits the global radio parameter
settings of n111. The target base station automatically inherits global radio data after migration. The
global radio data excludes transmission interface objects, external cell objects, objects referencing
cell objects or sub-objects of cell objects, and objects referencing transmission objects or equipment
objects.
 You need to delete the default data in the template example.
Refer to the following figure to fill in the data.
3. After editing the file, save and close it.
8.5.3 Exporting Existing Base Station Data

The CME exports the data from the source base station according to RF Migration NEs
Relationship filled by the user. The following figure shows the detailed operations.
Skip this step if reconstruction data can be obtained from an LLD data file.To obtain the tool for
conversion from an LLD data file to a summary data file, contact the CME representative, Zhang Yi
(employee ID: 00334527).
If you need to configure the reconstruction data based on the configurations on the live network, export
the data on the source base station and then modify the exported data.

Copyright © Huawei
Figure 1.2 Exporting the reconstruction project data
In this scenario, the CME exports data based on the specified source base station. You need to
export the project by template in step 2 and select the template edited in 8.5.2 Specifying NE
Mapping for RF Migration.
When the CME exports the reconstruction project data, data in the RF Migration NEs
Relationship sheet of the specified source base station is exported to the summary data file.
8.5.4 Filling In Data for New Base Station Deployment and RF

Migration
Fill in the sheets other than RF Migration NEs Relationship based on the data plan.
Example provides an example for data configurations. You can fill in data based on onsite
conditions by referring to the example.
The following describes the scenario in the example.
 Names of the base stations on the live network:
GBTS: 8984 and 1354

Copyright © Huawei
NodeB: U8984 and U1354

eNodeB: L08984 and L01354
 The IP-based GUL co-MPT base stations 8984 and 1354 need to be deployed and inherit
the names of the base stations as listed above and the cell data on the live network.
 The tool for converting the LLD data file to a summary data file can be used to improve efficiency.
Only List and Common sheets are supported.
 For details about the tool for converting the LLD data, see Training Document_iManager U2000-
CME V200R017_Interconnection Between LLD Data File and Summary Data File. To obtain the
tool for conversion from an LLD data file to a summary data file, contact the CME representative,
Zhang Yi (employee ID: 00334527). To obtain the tool for conversion from an LLD data file to a
summary data file, contact the CME representative, Zhang Yi (employee ID: 00334527).
 If equipment data is to be inherited using the NEP-SD tool, BTS Design File in the Base Station
Transport Data sheet of the summary data file refers to the base station design file generated using
the NEP-SD tool. BTS Design Cell ID in the cell-related sheet of the summary data file refers to the
planned cell ID in this design file. (The NEP-SD tool is not used in the sample data.) The following
figures show an example.
1. Fill in the data for new base station deployment.

The transport data cannot be inherited. You need to plan and fill in the data in the Base
Station Transport Data sheet. (Reference relationships with the parameter on the
Pattern sheet have been defined.)
The data exported by the CME is the data on the source base station. When filling in the data,
you need to change the base station name and base station ID to those of the target base
station as planned.
The maintenance mode can be set in the Application sheet when the data for new base
station deployment is filled in. This method is supported by the base stations of
SRAN11.0 and later versions. When the maintenance mode is set, the operations in
Setting NE Maintenance mode are not required.
2. Fill in the data for RF migration.
Details are as follows:
− Migrate the baseband board.

Copyright © Huawei
− Migrate the CPRI.

For example, migrate the RRU chain whose Source RRU Chain No. is 0 on the
U0971 source base station to the U0972 target base station as the RRU chain whose
Source RRU Chain No. is 1.
Click Move or Copy in Excel to add a Board Style sheet for new base station
deployment.
 For a summary data file excluding the Operation column, only items filled in the file can be
migrated when the summary data file is imported to the CME. For example, only the RRU chain
filled in the file can be migrated but the RRU or CXU on the RRU chain cannot be migrated. To
migrate these items, fill in the corresponding migration information in the file.
 For a summary data file including the Operation column, migration by chain is supported. For
example, if the RRU chain is filled in the file, the RRU and CXU on the RRU chain, and the sectors
and sector devices that use the RF module can be migrated together.
In the Board Style2 sheet used by the U0972 base station, click
to specify Expand/Migrate Object to RRU Chain and
Expand/Migrate Rows count to 1.

Copyright © Huawei
If all data on the source base station is to be migrated, click

and perform the following operations.
− Migrate the cell.

For example, migrate the cell whose Local Cell ID is 38456 from the U0917 base
station to the U0972 base station with the Local Cell ID as 22751. Change the Cell
Name to 972C1.

Copyright © Huawei
In the UMTS Cell sheet, migrate the cell on the source base station to the target
base station.
If cell subobjects to be migrated are defined in the summary data file, modify Cell
Name and Local Cell ID of the cell subobjects to those after migration. Fill in the
configuration data used after migrating on the target base station.
If cells are migrated from the source base station to the target base station, network
optimization parameters are inherited automatically and the neighbor relationships
are automatically reconfigured.
If names of the source base station and target base station are the same before and after migration, the
data of cells to be migrated does not need to be adjusted and only cells that require no migration need to
be deleted from the sheet.
− In the summary data file (excluding the Operation column) for RF migration,
modify the RF board used for cell migration.
Migrate the cell from the U0971 base station to the U0972 base station (Local Cell
ID: 22751) and then bind the cell to the RFU board that has been migrated.

Copyright © Huawei
Appendix
Macro functions of Excel can help you set parameters. The following table lists the available
macro functions in this scenario.
Table 2.1 Macro functions

non-MOC-Integration Only the default template

view, sheets other than name is displayed in the
RF Migration NEs drop-down list for selecting
Relationship a template in the summary
data file. Therefore, before
selecting a user-defined
template, you have to click
this button to add the user-
defined template name to the
drop-down list.
Information about the user-
defined template must be
consistent with that about
the existing template on the
CME.

Copyright © Huawei
non-MOC-Integration This function is used to

view, sheets other than convert the summary data
RF Migration NEs file into the style in which
Relationship sheets are displayed by base
station.
non-MOC-Integration During IP route
view, sheets other than configuration, this function
RF Migration NEs is used to convert an IP
Relationship address into an IP address
compliant with related rules
if the IP address changes
after performing an AND
logic operation with the
subnet mask.
 Board Style sheet This function is used to
 Pattern sheet customize differentiated
parameters on the Base
 Sheet of a summary Station Transport Data
data file, which is sheet by adding reference
converted into the relationships. Then, the
MOC-integration parameter values on the
view by using Base Station Transport
Data sheet are used, and the
related data on each base
station sheet is updated
based on the reference
relationships.
Base Station This function is used to
Transport Data sheet update the Base Station
of a summary data file, Transport Data sheet based
which is converted on existing base station data
into the MOC- so that base station data can
integration view by be checked before the
using reconfiguration in the Base
Station Transport Data
sheet.
Base Station After data reconfiguration,
Transport Data sheet this function is used to
of a summary data file, update each base station
which is converted sheet based on reference
into the MOC- relationships and values on
integration view by the Base Station Transport
using Data sheet.
GSM Cell, UMTS After the base station

Cell, and LTE Cell serving a cell is specified,
sheets this function is used to
adjust the antenna ports of
the cell in the UMTS Cell or

Copyright © Huawei
LTE Cell sheet.

Board Style sheet This function is used to
specify or adjust baseband
processing boards for
baseband equipment.
Board Style sheet This function is used to add
rows of records to specified
MOs, or migrate the data on
the source base station to the
target base station.
8.5.5 Importing Data

Click to import the edited summary data file into the CME to complete the reconstruction.
If equipment data is to be inherited using the NEP-SD tool, select Use BTS design file and select the
directory of the base station design file, as shown in the following figure. Ensure that the summary data
file refers to the base station design file. The following figure shows an example.

Copyright © Huawei
After the reconstruction project data is imported successfully, the target base station is created
and the data on the live network is successfully migrated. The CME generates the script files
on the base station controller side. You need to export the script files on the base station side.
8.5.6 Exporting Scripts

Script Export Mode
For details, see Figure 1.1.
Scripts on the Base Station Controller Side

The scripts on the base station controller side is generated by the Base Station Reconstruction
Express.
Scripts on the Base Station Side

1. On the menu bar, choose Advanced > Export Auto Deployment Data. A dialog box is
displayed.
2. Select a deployment scenario, and click Next.
Select Site creation/expansion.

Copyright © Huawei
3. Select the base stations whose auto deployment data is to be exported, and click Next.
4. Select a save path for the exported file and a method for processing data, and click Next.
5. View data in the base station deployment list, and click Next. The CME verifies data
If the parameter values displayed on the GUI are different from the data plan, you need to change the
parameter values based on the data plan. Otherwise, the deployment may fail.
6. Click Finish.
The exported data configuration scripts and deployment lists are stored in the following
paths:
− Data configuration script: export directory\CfgData\base station name
− Deployment lists: export directory\ADList\
 If you modified the associated parameters for GSM or UMTS cells, the CME automatically adjusts
external cell parameters of the corresponding NEs that have neighbor relationships with the GSM or
UMTS cells. The auto-deployment data can be exported only for new base stations. If data of the
base station in the live network is changed, you need to export the incremental scripts by choosing
Planned Area > Export Incremental Scripts.
 To activate scripts, it is recommended that the CME script executor be used for scripts on the
BSC/RNC side and for base station scripts.
 If the scripts on the base station controller side are activated by the script executor and the scripts are
exported in "One by one" mode using the Base Station Reconstruction Express, you can check the
base station name of each corresponding script in the Description field. The CME adds dependencies
between scrips. Execute the base station addition scripts before executing the RF migration scripts.

Copyright © Huawei
8.6 Binding Base Station Multimode Relationships

Procedure
Step 1 Export the binding relationship table.
1. On the menu bar of the planned data area, choose SRAN Application > MBTS
Application > Export Data > Export Binding Relation Data (CME client mode) or
CME > SRAN Application > MBTS Application > Export Data > Export Binding
Relation Data (U2000 client mode). A dialog box is displayed for you to export the
binding relationship table.
2. Select separate-MPT base stations whose binding relationships you want to export.
a. Select a separate-MPT base station type from the MBTS type drop-down list. If
ALL is selected, the CME exports the data of all base stations in the planned data
area.
b. Select one or more separate-MPT base stations whose binding relationships you
want to export.
3. Click Next. A dialog box is displayed for you to specify a save path.
4. Set the save path for the file you want to export.
5. Click Next. The CME starts to export the data.
6. When the export is successful, click Finish.
Step 2 Edit the binding relationship table.
1. Set the names of base stations to be bound in NE1, NE2, and NE3, set the deployment
ID, and select a target RAT type from the MBTS Type drop-down list.
− LTE_TDD in the MBTS Type drop-down list indicates only the LTE TDD base
stations that are supported since SRAN11.0, and no LTE FDD or NB-IoT cells can
be added for such base stations.
− If a GBTS is to be bound, BSC Name must also be set.
− If the deployment ID is not set, the CME automatically allocates an ID.
2. After editing the binding relationship table, save and close it.
Step 3 Import the binding relationship table.
1. On the menu bar of the planned data area, choose SRAN Application > MBTS
Application > Import Data > Import MBTS Relationship Data (CME client mode) or
CME > SRAN Application > MBTS Application > Import Data > Import MBTS
Relationship Data (U2000 client mode). A dialog box is displayed for you to import the
binding relationship table.
2. Select the binding relationship file you want to import, and click Next. The CME starts
checking the file format and importing the file.
3. When the import is successful, click Finish.
 If the import fails, click a link to view the error report. After modifying data based on the report,
click Retry to return to the step where the error occurs, and perform the operation again.
 In the BSC node redundancy scenario, if the primary and secondary homing base stations are
available in the planned data area, only the primary homing base station can be bound. If the
secondary homing base station is bound, an error message is displayed. If only the primary homing
base station or secondary homing base station is available in the planned data area, either can be
bound.

Copyright © Huawei
----End
8.7 Checking MBTS Data Consistency

 The procedure for manually checking NE data consistency is as follows:
Procedure
Step 1 On the menu bar of the current data area or a planned data area, choose Advanced >
Consistency Check (CME client mode) or CME > Advanced > Consistency Check (U2000
client mode). The data consistency check window is displayed, Figure 1.1 shows the window.
Figure 1.1 Data consistency check window
Step 2 Start the check task.
If you need Then...

to...
Create a check 1. Click in area 1 in Figure 1.1. The consistency check wizard is
task displayed.
2. Set the task name, and select the NEs whose data is to be checked.
NOTE
Use the following buttons as required:
 You can click to select RAT. If you select a RAT, only base stations of
this RAT are displayed. If you select All, all base stations are displayed.
 You can click to load common objects in batches. For details, see
Loading Common Objects in Batches.
3. Click Next, and select a filter.For detailed operations about filters,
see Managing Rule Groups.

Copyright © Huawei
If you need Then...

to...
4. Select related check rules.
After you select a check rule, the details about the rule are displayed
in the right pane.
NOTE
For common check rules, you can click Save As in the upper right part to save the
check rules as a filter.
5. Click Next. The CME displays the selected NEs and check rules.
When you check data about multiple NEs, related check items may
be different. You can select the required check items for NEs.
6. Click Finish. The CME starts to check data.
Restart a task Right-click a task from the historical check records in the left pane, and
choose Restart Task from the shortcut menu. The CME starts to check
data.
Step 3 View check results.

You can perform Autofix, Edit, or Refresh only on the latest check result.
If Operation Then...
Type of a result
record is
displayed as...
Autofix The CME automatically fixes all check results for related check rules.
NOTE
Operation Type is Autofix for a check rule that has specified how to modify
the check result and has only one check result.
1. Click or double-click a record to be fixed. The autofix wizard

is displayed.
2. Select the required fix type. The CME then automatically
reconfigures data.
Edit You need to manually reconfigure data in the general configuration
window.
Double-click the data record to open the general data configuration
window, and manually reconfigure the data.
Refresh You can select check results to be fixed as required. The CME then
automatically refreshes these check results.
NOTE
The operation type is defined as Refresh for the check rules whose check result
can be either fixed or not fixed.
Double-click the data record to open the data update wizard, and
reconfigure the data by using the wizard.
NOTE
 The CME corrects all records for one check rule by default. In addition, the
CME allows you to check a maximum of 9999 records in the update wizard

Copyright © Huawei
If Operation Then...
Type of a result
record is
displayed as...
at a time. If you want to check more than 9999 records, the CME does not
display the additional records, but it corrects all records.
 You can click Edit to add or delete records in the update wizard in the
displayed dialog box.
The CME does not correct deleted records. In addition, the CME adds the
records that have not been added to the update wizard. The total number of
records cannot exceed 9999.
If a security policy record is selected, the CME displays the parameter
column name as Parameter Name (Reference Value) in the Refresh
wizard of the security policy. You can check both the reference values
and current values of parameters to be reconfigured.
None The check results can only be viewed.
You can perform the following operations in area 3 in Figure 1.1 as required:
 To filter a large number of check results by type for easier browsing, click next to the column
name.
 To export the check results as a file, right-click in area 3 and choose Export Data from the shortcut
menu.
----End
Follow-up Procedure
After creating two or more data consistency check tasks, you can select two tasks in the task
list in area 2 of the Figure 1 area at the same time, right-click them, and choose Compare
Task Result from the shortcut menu to compare the check results.
You can also compare the check results of two tasks in the following method:
1. Right-click a task and choose Choose to compare on left window from the shortcut menu.
2. Right-click the other task, and choose the related option from the shortcut menu to compare it with
the selected task.
 The procedure for manually checking MBTS data consistency is as follows:
Procedure
Step 1 On the menu bar of the current data area or planned data area, choose SRAN Application >
MBTS Application > MBTS Consistency Check (CME client mode) or CME > SRAN
Application > MBTS Application > MBTS Consistency Check (U2000 client mode). A
window is displayed for you to perform operations.
If you need Then...

to...
Set check rule Perform Step 2.

Copyright © Huawei
If you need Then...

to...
parameters
Manage rule Perform Step 3.

groups
Create a Perform Step 2 and Step8.

consistency
check task
Step 2 (Optional and required when the default check parameter configurations do not meet your
requirements) Set check rule parameters.
If you need Then...

to...
Set check rule 1. Click . A dialog box is displayed for you to set check rule
parameters parameters.
2. Click the Parameters tab, and set TRX board attributes.
 Power Overload: indicates whether the carrier power on the
RXU can exceed the maximum value designed for the hardware.
When excessive power is allowed, the RXU can provide higher
transmit power by sharing power between carriers.
 Co-Power Amplifier: indicates whether the carriers in GU or
GL mode can be configured on one power amplifier of the RXU.
 Environment Temperature Spec.: indicates the working
temperature of the RF module.
- General Spec.: indicates that the temperature is higher than or
equal to 50°C.
- Low Temperature: indicates that the temperature is lower
than 50°C.
The temperature can be set to General Spec. in normal cases,
and Low Temperature in low temperature areas. The MRRU at
the GSM900 band supports larger transmit power when it works
at a low temperature.
3. Click OK.
Set the error 1. Click . A dialog box is displayed for you to set check rule
severity of parameters.
check rules 2. Click the Levels tab, and set the error severity of check rules.
 Warning: A potential or impending service-affecting fault is
detected.
 Error: A fault that currently does not affect services occurs and
a corrective action must be taken to prevent a more serious fault.
 Major: A service-affecting fault occurs. If the fault is not
rectified in time, it will lead to a serious result.
3. Click OK.

Copyright © Huawei
Step 3 (Optional and required when the default check parameter configurations do not meet your
requirements) Manage rule groups.
1. Click . A dialog box is displayed for you to manage rule groups.

2. Select the multimode base station type from the MBTS type drop-down list (For
example, select GSM and UMTS for GU). The existing rule groups are displayed in the
left pane of the dialog box and the related check rules are displayed in the right pane.
3. Perform the following operations as required.
If you need Then...
to...
Delete a rule Select a rule group from the left pane of the dialog box, and click
group Delete.
Modify check 1. Select a rule group from the left pane of the dialog box, and select
rules or clear check rules from the right pane.
2. Click Save.
4. Click Close.
Step 4 Click . The wizard dialog box is displayed.

Step 5 Set the task name in the Check task name area, select a multimode base station type from the
MBTS type drop-down list, and select multimode base stations to be checked from the list in
the lower part of the area.
In the BSC node redundancy scenario, if the primary and secondary homing base stations are available
under the MBTS, only the primary homing base station is displayed in the NE list. If only one of the
primary and secondary homing base stations is available in the MBTS, the base station is displayed in
the NE list.
Step 6 Click Next, and set check rules.

1. Select a rule group from the Rule group drop-down list. All related check rules are
displayed in the lower part.
2. (Optional) Select or clear related rules as required.
After you select a check rule, the details about the rule are displayed in the right pane.
3. (Optional and required when you want to use the modified rule group for future checks)
Click Save As to save the rules as a rule group.
After you exit the wizard, you can view the new rule group by performing Step 3.
Step 7 Click Next, and adjust check rule settings.
All NE check rules are displayed in the lower part and are selected by default. To modify the rules, clear
related rules. You can adjust the settings in the following scenarios:
 Reconfigure the NE to be checked: Clear all check rules related to the NE.
 Modify a check rule for one or multiple NEs: Clear the rule.
Step 8 Click Finish. The CME starts to check the data and displays check results.

Copyright © Huawei
If Operation Type Then...

in a data record is
displayed as...
Refresh Double-click the data record. The CME reconfigures the data
automatically according to the primary mode set for the multi-
mode base station.
NOTE
For the conflict result record of the RXU resources, double-click the
record. The dialog box for reconfiguring the RXU resources is displayed.
You need to reallocate the RXU resources before the CME starts
reconfiguring the data automatically.
Edit Double-click the data record to open the general data

configuration window, and manually reconfigure the data.
None Modify the configuration data as prompted.
 To filter a large number of check results by type for easier browsing, click next to the column
name.
 To export the check results as a file, right-click a data record, and choose Export Data from the
shortcut menu.
 To restart a check task, right-click a historical task in the History Check Results area, and choose
Restart Task from the shortcut menu. The CME starts to check data based on the existing settings.
 The CME allows you to delete historical tasks in either of the following methods:
- Select one or multiple tasks in the History Check Results, and click .
- Select a record from the check record list on the right of the History Check Results area and click
.
----End
Follow-up Procedure
After creating two or more data consistency check tasks, you can select two tasks in the task
navigation tree in the left pane of the check result window, right-click them, and choose
Compare Task Result from the shortcut menu to compare check results.
You can also compare the check results of two tasks in the following method:
1. Right-click a task and choose Choose to compare on left window from the shortcut menu.
2. Right-click the other task, and choose Compare to name of last task from the shortcut menu.
8.8 Checking Data Preparations

Check the consistency between the customized configuration data and data planned for mode
transition. Ensure no MO is missing.

Copyright © Huawei
Mode Transition Guide(For NB) 9 Setting NE Maintenance mode
9 Setting NE Maintenance mode
The board at delivery works in maintenance mode by default. No setting is required.
To prevent alarms generated during the mode transition from affecting other modes, you must
set the existing mode in the base station to maintenance mode. You can set the maintenance
mode by NE or by mode. In the co-MPT scenario, you are advised to set the maintenance
mode by mode to reduce the impact of mode transition to the northbound.
The detailed operations are described as follows (you can perform the operations by NE or by
mode):
Step 1 Double-click Configuration on the Application Center tab page.

Copyright © Huawei
Step 2 Choose Setting > Maintenance Mode on the displayed interface.
Step 3 Click Set Maintenance Mode.
Step 4 In the displayed Set Maintenance Mode dialog box, select a target base station and set the
engineering mode.
If BTS3900 is selected from the NE navigation tree, the maintenance mode of the physical
NE BTS3900, logical GBTS, and logical NodeB must be set.
If eNodeBFunction, NodeBFunction, or GbtsFunction is selected from the NE navigation
tree, maintenance mode of the Function and its corresponding base station must be set.

Copyright © Huawei
These operations succeed. Maintenance mode has been successfully set.
----End

Copyright © Huawei
Mode Transition Guide(For NB) 10 Adjusting Hardware
10 Adjusting Hardware
Adjusting hardware may affect services. For details, see section 3.1.2 "General Impacts" in
3900 Series Multimode Base Station V100R010C10 Mode Transition Guide.
10.1 Adjusting Equipment

The equipment to be adjusted during mode transition include BBUs, RXUs, CPRI cables, and
antenna & feeder. 3Planning Mode Transition shows the equipment configurations before and
Adjusting BBUs
For details about BBU installation, see the installation guide of the corresponding base
station. For details about board installation, see the hardware maintenance guides of the
corresponding base station.
In the co-MPT reconstruction involving mode expansion scenario for UO, LO, UL, or some
hybrid-MPT base stations, convert the replaced WMPT or LMPT.
If the UMPTe serves as the main control board for the co-MPT base station after
reconstruction, the main control boards (including WMPT and LMPT) before reconstruction
are abandoned and removed from the subrack, and the main control board (UMPTa/b) before

Copyright © Huawei
Mode Transition Guide(For NB) 10 Adjusting Hardware
Adjusting RF Modules
For details about how to install RRUs, see the related RRU installation guide.
Adjusting Feeders
Connect feeders to the newly added MRRUs.
10.2 Adjusting Feeders

Connect feeders to the newly added RRUs.
10.3 Adjusting Transmission Cables

Two steps are involved in transmission adjustment:
1. Disconnect transmission cables before mode transition.
2. Add and connect transmission cables to FE ports on the transmission boards after mode
transition.

Copyright © Huawei
Mode Transition Guide(For NB) 11 Activating Configuration Data and Commissioning
11 Activating Configuration Data and

Commissioning
For details about the remote commissioning and USB flash drive-based commissioning, see 3900 Series
Base Station Commissioning Guide.
The LTE data configuration must be activated before the GSM and UMTS data configuration
because GUL co-transmission is implemented through the backplane and transmission ports
are provided on the LTE side after mode transition. Connect the transmission cable on the
GSM side to the LTE side and then activate the UMTS and GSM data configuration
successively if only one transmission cable is used. If two transmission cables are used,
connect the unused cable to the LTE side and then activate the UMTS and GSM data
configuration successively. There is no requirement on whether the other transmission cable
connected to the GSM side must be disconnected or not.
When you adjust the data of the original mode or when the data of the new mode includes
controller data, you must export an incremental script and use the script executor to activate
the script. For the operation methods, see 11.1Activating Data in Incremental Scripts.
For the newly added mode to the co-MPT multimode base station, the remote U2000-based
commissioning without auxiliary equipment is recommended. For the operation methods, see
11.2Base Station Deployment by PnP.
For the newly added mode to the separate-MPT multimode base station, either the remote
U2000-based commissioning without auxiliary equipment or the local USB + remote U2000-
based commissioning can be used. For the operation methods, see 11.2Base Station
Deployment by PnP and 11.3Base Station Deployment by USB.
For the newly added mode to the co-MPT reconstruction and capacity expansion, if the main
control board of the co-MPT base station is WMPT or LMPT, replace the WMPT or LMPT
with UMPT. The local USB + remote U2000-based commissioning can be used. If the main
control board of the co-MPT base station is UMPT, the remote U2000-based commissioning
can be used. For the operation methods, see 11.4PnP-based Co-MPT Reconstruction and
11.3Base Station Deployment by USB.

Copyright © Huawei
11.1 Activating Data in Incremental Scripts

For the original mode, export the incremental scripts and use the script executor for data
activation during data adjustment.
For the new mode, export the incremental scripts and use the script executor for data
activation if data on the base station controller side exists.
1. The procedure for exporting the incremental scripts of the planned area is as follows:
Procedure
Step 1 On the menu bar of the planned data area, choose Area Management > Planned Area >
Export Incremental Scripts (CME client mode) or CME > Planned Area > Export
Incremental Scripts (U2000 client mode). A dialog box is displayed for you to export
scripts.
 If NE data in the planned data area has been modified, the CME automatically adds the
related NEs to the right pane.
 If data in the planned data area is not modified, the CME displays a message indicating
that incremental scripts cannot be generated.
Step 2 Specify a save path for scripts.
Step 3 (Optional) Set description for the scripts in Project description.
The CME uses the user-defined information in Project description as the file name prefix for
the folder saving the exported scripts to easily identify the exported scripts and identify
loaded projects in the script.
Step 4 Select a script export mode, for example, Break on Failure or Best Effort.
 Break on Failure: If an error occurs on any NE during the export, the import stops
immediately and no scripts are exported.
 Best Effort: The CME skips the NEs where errors occur and continues the export, and
the exported scripts do not contain NEs where errors occur.
Step 5 (Optional) Set an encryption mode for exported scripts.
 No: The exported scripts do not have encryption passwords and no encryption passwords
are required when you loading projects.
 Yes: The exported scripts have encryption passwords. When loading projects, you have
to enter encryption passwords by performing the following operations:
1. Select Yes.
2. Click Set Password. In the displayed dialog box, enter the encryption password as
required.
3. Click OK.
Step 6 Select a mode for starting the script executor.

Copyright © Huawei
If... Then...
You do not Select Do not launch script executor.

need to After the scripts are exported, you can click the save path link to navigate
activate scripts to the folder for saving the scripts.
or check
scripts in the You need to manually start the script executor to activate incremental
script executor scripts in the future. For detailed operations, see the manual startup
window process in Activating Data Using the Script Executor.
You need to Select Launch script executor only.

check or edit Click OK. The CME then automatically uploads the exported scripts to
scripts in the the U2000 server. In addition, the CME automatically switches to the
script executor Summary tab page of the script executor and selects the planned data
window before area node to which the new script project belongs.
activating
scripts In the list in the right pane of the planned data area, select the latest script
project (based on the creation time). You can check or edit scripts in the
list and need to manually activate the scripts in the future. For detailed
operations, see the automatic startup process in Activating Data Using the
Script Executor.
NOTE
Before performing this operation, ensure that you have the network device
permission Modify Physical NE Data through CME. Otherwise, the scripts
cannot be exported.
You need to 1. Select Launch script executor and activate exported project.
directly 2. Select a script activation mode from the drop-down list.
activate scripts  Break on failure: If any error occurs when the scripts are being
activated, the CME immediately stops the activation. Commands that
are executed before the error occurs can be executed successfully.
 Best effort: If any errors occur when the scripts are being activated, the
CME skips the error commands and proceeds with the activation.
Commands other than the error commands can be executed
successfully.
For XML scripts, the CME performs operations based on the
predefined mode, regardless of your selection. Processing method: If
an error occurs during the activation, the CME immediately stops the
activation and restores configuration data to the status before the
activation.
After scripts are exported, the CME automatically starts the script
executor to activate the scripts.
NOTE
Before performing this operation, ensure that you have the network device
permission Modify Physical NE Data through CME. Otherwise, the scripts
cannot be exported.
Step 7 Click OK to export the incremental scripts
For security purposes, the CME displays the NE cipher key as *****. If you have changed the cipher
key in the planned data area, the CME displays either of the following information based on the change.
You can check the details in the drop-down list.

Copyright © Huawei
 If Yes is displayed in the Is Fallback column, you have changed the NE cipher key from the default
value to another value and the NE cipher key in the fallback script is replaced with the default value.
 If No is displayed in the Is Fallback column, you have changed the NE cipher key from another
value to the default value and the NE cipher key in the positive script is replaced with the default
value.
----End
2. The procedure for activating the scripts is as follows:

 Perform the following steps to upload the scripts:
Procedure
Step 1 On the menu bar of the CME main window, choose System > Script Executor (CME client
mode) or CME > Script Executor (U2000 client mode). The script executor window is
displayed in the right pane.
Step 2 On the menu bar of the script executor window, choose Project > Load Project. A dialog box
is displayed for you to select the folder saving scripts.
Step 3 Select the project folder saving the script to be activated, and click Select. The script executor
window is displayed.
 The scriptcfg.xml file must be directly saved in the selected folders.

If configuration fallback is supported in a certain scenario, the folder also contains a Fallback file,
which saves the fallback script. For details about the scenarios where fallback is supported, see
Fallback Based on Configuration Steps.
 If an encryption password is required for a script to be imported, a dialog box is displayed, asking
you to enter the encryption password that is set during the script export.
Step 4 (Optional) Right-click tasks and choose the required menu items from the shortcut menu to
configure the tasks in batches.
Modify Task Description, Modify Task Dependency, and Modify NE Name can be performed only
before the project upload. After the project is uploaded successfully, they cannot be performed.
Set a task to be Select Change Suspension Status. You can check the task status in
suspended (a the Suspend column of the task list area.
suspended task NOTE
cannot be activated) After a script is uploaded, you can modify it as required.
NOTE
Imported tasks are
not in the suspended
status by default.
Set script Select Modify Task Description. In the displayed dialog box, set
differentiation the task description.
labels
NOTE
The task
differentiation label
is task description.
You can

Copyright © Huawei

differentiated
uploaded tasks using
the task description.
Adjust task 1. Select Modify Task Dependency. In the displayed task list
dependencies dialog box, adjust the task dependencies.
NOTE The wizard displays task items that the selected task can depend
A task dependency on. If a task item is unavailable, the selected task cannot depend
indicate the task on the task item.
execution sequence.
One task can be 2. Adjust the task dependencies as required.
executed only after 3. Click OK. The serial numbers (SNs) of the tasks that depend on
the task it depends the current task are displayed in the Depended On field.
on is executed first.
For details about the operation legend, see Figure 4.1.
Change an NE 1. Choose Modify NE Name. In the displayed dialog box, the left
name in the current pane lists the NE names in the current script, and the right pane
script to be the lists the NE names on the U2000. You can select an NE name
same as the NE from the right pane or enter the name of an NE on which the
name on the U2000 script will take effect so that the new NE name is consistent with
the NE name on the U2000.
NOTE
If an NE name in the 2. Click OK to save the modification and close the dialog box.
script executor is not
the same as that on
the U2000, script
activation will fail.
Figure 4.1 Example of changing task dependencies

Copyright © Huawei
 During the activation, tasks are activated based on task dependencies.

As shown in Figure 4.1, set task 1 to be the task that task 2 depends on. Then, when activating the
script, the CME activates task 1 and task 2 in sequence.
 By default, the CME concurrently activates the tasks whose dependencies are not set.
Step 5 Right-click the project to be uploaded and choose Upload Project from the shortcut menu. A
dialog box is displayed, asking you to set project description.
Step 6 Set the project description and click Confirm to upload the scripts to be activated to the
U2000 server.
----End
 Perform the following steps to view or edit the scripts:
Procedure
Step 1 Click the Summary tab in the script executor window.
In the project list in the right pane, right-click a project and choose View High-Risk Operations from the
shortcut menu.
If high-risk operations exist in the project, a message dialog box is displayed. Click the link in the dialog
box to check details about the high-risk operations, including NE names, operations, and information to
be confirmed.
Step 2 Double-click a project in the project list in the right pane. A project tab page is displayed,
showing information about all the tasks in the current project.
Double-click a project in the project list in the right pane. A project tab page is displayed, showing
information about all the tasks in the current project.
Step 3 Right-click a task and choose Edit Script from the shortcut menu. The system switches to the
script editing mode.
When the script is in editing mode, the CME automatically suspends the corresponding task.
A suspended task cannot be edited. You need to resume it and then edit it. You can check whether the
required task is suspended in the Status column. If it is suspended, right-click it and choose Resume
from the shortcut menu.
MML scripts and XML scripts in text format support data addition, modification (all parameters), and
deletion.
Step 4 Select a task and check the details about its script in the lower part.
The GUI display and related operations vary according to script types.
Step 5 Right-click the script and choose Update Script from the shortcut menu. The client uploads
the modified script to the server.
----End
 Perform the following steps to activate data:

Copyright © Huawei
Procedure
 Preactivate the project.
a. On the menu bar of the CME main window, chooseor . The script executor window
is displayed in the right pane.
b. In the Script Executor window, click the Summary tab.
c. In the right pane of the window, right-click a project you want to preactivate and
choose an activation mode from the shortcut menu. The available activation modes
are as follows:
가 If a project containing XML scripts is to be preactivated, the CME uses the
"break on failure" activation mode.
If Preactivate Project is selected, If an error occurs during the activation, the
CME immediately stops the activation and restores configuration data to the
data before the activation.
나 If an MML script is to be preactivated, the CME uses either of the following
modes:
□ Break on failure
Choose Preactivate Project > Break on Failure. The CME stops the
activation immediately if an error occurs during the activation.
□ Best effort
Choose Preactivate Project > Best Effort. The CME continues with the
activation by running a command next to the error command if an error
occurs during activation.
 If some suspended tasks are available in the project, the CME displays a message asking you
whether to resume these suspended tasks and then activate the project:
Click Yes to enable the CME to resume the suspended tasks and then preactivate the project.
Click No to enable the CME to preactivate only tasks that are not suspended.
 If some activated tasks are available in the project, the CME displays a message asking you whether
to reactivate the entire project:
Click Yes to enable the CME to reactivate the entire project.
Click No to enable the CME to activate only the tasks that are not activated.
Click Cancel to cancel the activation.
d. Check whether to activate data.
e. (Optional and applied only to an MML project) In the project list in the right pane,
right-click a project for which you want to cancel preactivation and choose Cancel
Operation from the shortcut menu.
 You can activate tasks of multiple NEs at a time.
 If tasks are mutually dependent, you must wait until a task is activated and then activate
the next task.
 Gray tasks are automatically processed by the CME. You cannot perform operations on
these tasks.
 You can perform the following operations on tasks as required:
To suspend a task, right-click in the Project-xxx dialog box and choose Suspend Task
from the shortcut menu.
To activate a suspended task in a project, right-click the suspended task on the displayed
Project-xxx tab page, and then choose Resume Task from the shortcut menu to resume
the task. Then, perform the activation.

Copyright © Huawei
You can view information about the NEs being activated on the NE Status tab page.
To check whether a task has been successfully activated, click the Summary tab and
check the value of Result.
 Perform the following steps for fallback based on the configuration steps.
Procedure
 View the fallback project.
b. In thewindow, click thetab.
c. Right-click a project whose fallback project is available and choose View Fallback
Project from the shortcut menu.
d. (Optional) Activate rollback scripts by task. The operation is as follows: On the
displayed Fallback Project-xxx tab page, right-click a task and choose an
activation mode from the shortcut menu:
다 If a task containing XML scripts is to be rolled back, the CME uses the "break
on failure" activation mode.
If Activate Task is selected, If an error occurs during the activation, the CME
immediately stops the activation and restores configuration data to the data
before the activation.
라 If a task containing MML scripts is to be rolled back, the CME uses either of
the following activation modes:
Choose Activate Task > Break on Failure. The CME stops the
□ Best effort
Choose Activate Task > Best Effort. The CME continues with the
 You can activate tasks for multiple NEs at a time.

 If tasks are mutually dependent, you must wait until a task is activated and then activate the next
task.
 Gray tasks are automatically processed by the CME. Users cannot perform operations on these tasks.
To suspend a task, right-click on the Fallback Project-xxx tab page and choose Suspend Task from
the shortcut menu.
To activate a suspended task in a rollback project, right-click a rollback task to be activated on the
displayed Fallback Project-xxx tab page and choose Resume Task from the shortcut menu to
resume the task. Then, activate the task.
 Preactivate the fallback project.
c. Right-click a project whose rollback project is available and choose an activation
mode from the shortcut menu:
마 If a project containing XML scripts is to be rolled back, the CME uses the

Copyright © Huawei

바 If a project containing MML scripts is to be rolled back, the CME uses either
of the following modes:
□ Best effort
 Activate the fallback project.
mode from the shortcut menu: Activate Fallback Project > Break on Failure or
Activate Fallback Project > Best Effort
사 If a project containing XML scripts is to be rolled back, the CME uses the
아 If Activate Fallback Project is selected, If an error occurs during the
activation, the CME immediately stops the activation and restores
configuration data to the data before the activation.
자 If a project containing MML scripts is to be rolled back, the CME uses either
Choose Activate Fallback Project > Break on Failure. The CME stops
the activation immediately if an error occurs during the activation.
□ Best effort
Choose Activate Fallback Project > Best Effort. The CME continues
with the activation by running a command next to the error command if
an error occurs during activation.
 View the fallback project.
c. Right-click a project whose fallback project is available and choose View Fallback
Project from the shortcut menu.
d. (Optional) Activate rollback scripts by task. The operation is as follows: On the
displayed Fallback Project-xxx tab page, right-click a task and choose an
activation mode from the shortcut menu:
차 If a task containing XML scripts is to be rolled back, the CME uses the "break
on failure" activation mode.
If Activate Task is selected, If an error occurs during the activation, the CME
immediately stops the activation and restores configuration data to the data
before the activation.

Copyright © Huawei
카 If a task containing MML scripts is to be rolled back, the CME uses either of
the following activation modes:
Choose Activate Task > Break on Failure. The CME stops the
□ Best effort
Choose Activate Task > Best Effort. The CME continues with the
 You can activate tasks for multiple NEs at a time.

 If tasks are mutually dependent, you must wait until a task is activated and then activate the next
task.
 Gray tasks are automatically processed by the CME. Users cannot perform operations on these tasks.
To suspend a task, right-click on the Fallback Project-xxx tab page and choose Suspend Task from
the shortcut menu.
To activate a suspended task in a rollback project, right-click a rollback task to be activated on the
displayed Fallback Project-xxx tab page and choose Resume Task from the shortcut menu to
resume the task. Then, activate the task.
 Preactivate the fallback project.
mode from the shortcut menu:
타 If a project containing XML scripts is to be rolled back, the CME uses the
파 If a project containing MML scripts is to be rolled back, the CME uses either
□ Best effort
 Activate the fallback project.
mode from the shortcut menu: Activate Fallback Project > Break on Failure or
Activate Fallback Project > Best Effort

Copyright © Huawei
하 If a project containing XML scripts is to be rolled back, the CME uses the
가 If Activate Fallback Project is selected, If an error occurs during the
activation, the CME immediately stops the activation and restores
configuration data to the data before the activation.
나 If a project containing MML scripts is to be rolled back, the CME uses either
Choose Activate Fallback Project > Break on Failure. The CME stops
the activation immediately if an error occurs during the activation.
□ Best effort
Choose Activate Fallback Project > Best Effort. The CME continues
with the activation by running a command next to the error command if
an error occurs during activation.
5. Perform the following steps to view the activation task:
Procedure
Step 1 Double-click the project information in the right pane of the Summary window. The
corresponding tab page is displayed.
On the Summary tab page or any project information tab page, you can drag the table headings to adjust
the display sequence of the columns.
Step 2 Right-click a task and choose Report > Report Type from the shortcut menu to view the task
execution results.
 If the activation fails because the activated NE is disconnected from the U2000, execution results are
unavailable.
 In execution result reports, preactivation reports are displayed by NE, and activation reports are
displayed by task.
 If scripts in the activation task are MML scripts, the following report types are available:
All: contains all information about successful and failed activation.
Succeeded: contains only information about successful activation.
Failed: contains only information about failed activation.
 If scripts in the activation task are XML scripts, the following report types are available:
Recent: checks details about the script execution results.
History: displays a dialog box for selecting historical operations. You can select historical
operations on the script and click OK to check details about the selected operations.
For base station controllers, if the activation report contains failure information, you can double-click
the error record in the error information list in the lower part of the window. The CME then
automatically locates the configuration object where the error in the script occurs, helping you view and
correct the information.
If you cannot double-click the error to locate the configuration object where the script is incorrect, you
can check the error information (Messages column) in the information list and then check the XML
script file based on the error information to find the operations that cause this error and correct it.
After the scripts are activated, the following execution results returned from NEs are available:
 If is displayed in front of the NE node in the navigation tree, the activated scripts contain error
information. In this case, you can select Browse errors to check only the error information.

Copyright © Huawei
 If is displayed in front of the NE node in the navigation tree, the script activation is successful
but some information needs to be observed.
----End
6. Perform the following steps to export the project:
Procedure
Step 1 On the menu bar of the CME main window, choose System > Script Executor or CME >
Script Executor. The script executor window is displayed.
Step 2 On the Summary or Project-xxx tab page, select a project in which the scripts need to be
exported, and choose Project > Export Project on the menu bar. The Export Project dialog
box is displayed.
Step 3 In the upper part of the dialog box, specify a folder for saving exported scripts and set project
description.
Step 4 Perform operations based on application scenarios.
You need to export configuration scripts by Select Export By NEs.

NE NOTE
The CME exports scripts for all tasks in the
project by default.
You need to export configuration scripts by Select Export By Tasks.

task NOTE
 The CME exports scripts for all tasks in the
project by default.
 Users can filter scripts based on task status.
Step 5 Click Export. The CME starts to export the scripts.

Step 6 After the scripts are exported, you can click the link to navigate to the folder where the scripts
are saved. Click Close to close the dialog box.
----End
11.2 Base Station Deployment by PnP

If a mode is added, base station data can take effect through the procedure for BTS
deployment by PNP.
1. Perform the following steps to export the auto-deployment data file.

Copyright © Huawei
Procedure
Step 1 On the menu bar, choose Advanced > Export Auto Deployment Data (CME client mode) or
CME > Advanced > Export Auto Deployment Data (U2000 client mode). A dialog box is
displayed for you to export auto-deployment data.
Step 2 Select Site creation/expansion, and click Next.
Step 3 Select the base stations whose auto-deployment data you want to export, and click Next.
You can click Load to select base stations to be exported by loading a file. The method of obtaining the
file, Click Export. The CME then exports the file. You have to set values for the parameters in the
exported file.
If the check boxes and buttons are unavailable, you can only view information in the dialog box.
Step 4 Select a save path for the exported file and a method for processing data, and click Next.
If... Then...
Export  After Export NE security configuration data is selected, if the current

data user has the Obtain NE Security Configuration Data operation rights,
from the NE sensitive data is displayed in plain text in the exported data file; if the
current current user does not have the Obtain NE Security Configuration Data
area operation rights, a message is displayed on the CME, indicating that
sensitive data cannot be exported.
 After Export NE security configuration data is cleared, sensitive data is
displayed as ***** in the exported data file.
Export Select the method for verifying data as required.
data
from the
planned
area
Step 5 View data in the base station deployment list, and click Next. The CME starts to verify data
 If the parameter values displayed on the GUI are different from planned values, you need to change
the parameter values based on the planned values. Otherwise, the deployment may fail.
 You can only set the first level subnet information. To specify subnets at other levels, adjust the
subnet information in the U2000 topology view after base station commissioning.
If the user-specified subnet information does not exist on the U2000, the U2000 automatically
generates the subnet during the import of auto-deployment data in the commissioning.
 If Auto assigned is selected from the Subarea drop-down list, the U2000 automatically assigns
subareas for NEs by following the subarea load balancing principle when auto-deployment data is
imported into the U2000.
 When editing data, you can use Ctrl+C and Ctrl+V to copy information from one cell to multiple
cells.
Step 6 If the export is successful in U2000 client mode, set the following options:
 Select Do not open the Auto Deployment window to close the wizard.

Copyright © Huawei
 Select Open the Auto Deployment window. The CME automatically switches to the
auto-deployment window and creates a commissioning task.
 Select Open the Auto Deployment window and start Auto Deployment task. The
CME automatically switches to the auto-deployment window and starts a commissioning
task.
The save paths for the exported data configuration scripts and deployment lists are as follows:
 Data configuration scripts: export directory\CfgData\base station name
 Deployment lists: export directory\ADList\
You can use the script executor to check and edit the exported data configuration scripts.
----End
2. Perform the following steps to start an NE commissioning task:
Procedure
Step 1 On the U2000 client, choose SON > Self Planning > Auto Deployment (application style) or
SON > Auto Deployment (traditional style). The Auto Deployment window is displayed.
Step 2 Start the NE commissioning task, as shown in the following figure.

Copyright © Huawei
Figure 2.1 Starting an NE commissioning task
1. Select one or multiple commission tasks and right-click these commissioning tasks.
Click Start. The Task Parameter Settings window is displayed.
If global parameters have been set before the start of a commissioning task, parameters in the Task
Parameter Settings dialog box use the global parameter settings. Engineers can modify the parameter
settings based on the actual data plan. Global parameters can be set as follows: Right-click the
commissioning task list area and choose Global Parameter Settings.
2. Set Step Parameters as planned.
Tip 1: Choose the corresponding operations as planned.
 : indicates that this step is mandatory and cannot be changed manually.

 : indicates that this step is optional and executed by default.
 : indicates that this step is optional and not executed by default.
For details about the U2000-based commissioning process for a newly deployed base
station, see Table 1.1.

Copyright © Huawei
Table 1.1 U2000-based commissioning process for a newly deployed base station
No. Phase Procedure Selection Policy
1 Auto discover site Check OM channel The U2000 determines

whether to select this
procedure.
2 Auto configure Download software Select this procedure if you
site need to upgrade the software
version of a main control
board.
Download site Select this procedure if you
configuration need to upgrade the
configuration of a main
control board or newly
deploy a base station .
NOTE
This check box does not exist if
the NE to be commissioned is
the GBTS.
Activate site The system automatically

selects this procedure if
Download site
configuration is selected.
You need to manually select
this check box if only
Download site software is
selected.
NOTE
Software and configurations
are activated simultaneously if
you select Download site
software and Download site
configuration. Only the
selected item is activated if you
select either Download site
software or Download site
configuration.
3 Deliver license Deliver commissioning Select this procedure if LTE

license services are to be
commissioned.
4 Test installation & Monitor RF module The U2000 selects this
deployment service status procedure if installation and
quality deployment quality testing is
to be performed.
Intervene The U2000 selects this
procedure if installation and
deployment quality testing is
to be performed.
Test installation & This procedure is optional
deployment quality but recommended.

Copyright © Huawei
NOTE
If a DBS3900 LampSite is to
be commissioned, do not select
Test installation &
deployment quality.
Otherwise, the commission task
fails.
5 Waiting for Waiting for The system automatically

confirmation confirmation selects this procedure.
3. Set Extended Parameters as planned.

Tip 2: Extended Parameters defines threshold parameters for commissioning the
antenna system in the Test installation & deployment quality phase. If there are no
special requirements, default values of these parameters are used. If there are special
requirements, set these parameters as required.
4. Click OK.
Tip 3: After the start of an NE commissioning task is confirmed, the U2000 checks the
required data configuration file:
If the data configuration file is available, the U2000 starts commissioning and the
corresponding task is in the Running state.
----End
11.3 Base Station Deployment by USB

1. Perform the following steps to prepare the software packet, configuration file, and
deployment list:
Procedure
Step 1 Obtain the software package from Huawei engineers and decompressed the software package
on a local PC.
 If the preconfigured software of the main control board of the base station to be deployed is
SRAN8.0 or later, obtain the software package "BTS3900
V100R011C00SPCXXX_ALL(Software)support from SRAN8.0 and later Versions.7z." If the NE
type of an NE to be deployed is BTS3900 and a GTMUb serves as the main control board, you also
need to obtain the software package BTS3900V900R011C00SPCXXX.zip for implementing the
GTMUb SingleOM reconstruction.
 If the preconfigured software of the main control board of the base station to be deployed is earlier
than SRAN8.0 or unknown, obtain the software package "BTS3900
V100R011C00SPCXXX_ALL(Software).7z."
Option Description
NodeB, eNodeB, and BTS3900 Obtain the software package of the target
base station version.
GBTS Obtain the software package of the target

Copyright © Huawei
Option Description
GBTS version for GBTS upgrade through a

USB flash drive.
Step 2 Export a deployment list and data configuration files from the Configuration Management
Express (CME). For details, see Exporting Files Related to Base Station Creation/RAT
Introduction to Co-MPT Base Stations.
After the deployment list and data configuration files are exported from the CME, choose Do
not open the Auto Deployment window.
Data configuration files and deployment lists exported from the CME are saved in the
following paths. Do not modify any exported files or the directory structure of any exported
files.
 Data configuration files: export directory\CfgData\base station name\
 Do not copy the .xml files from a remote desktop to a local PC. Otherwise, base station
deployment will fail. You are advised to compress the required files into a .rar or .zip file
for file transfer.
Step 3 Save the data configuration files on the local PC. Then, perform the following steps to upload
the deployment list to the U2000 server.
1. On the U2000 client, choose SON > Self Planning > Auto Deployment (Application
style) or SON > Auto Deployment (Traditional style). The Auto Deployment window
is displayed.
2. Click the Prepare File & Data tab and then the Deployment List tab.
Figure 3.1 Prepare File & Data > Deployment List tab

Copyright © Huawei
3. Click Transfer, and choose From OSS Client to OSS Server from the shortcut menu.
The Upload Deployment List dialog box is displayed.
Figure 3.2 Upload deployment list
The File Path in the Destination Path area shows the file save path on the server. This path cannot be
modified.
4. Click in the Source Path area. The Open dialog box is displayed. Select the
deployment list (.xml) to be uploaded, and click Open. The Upload Deployment List
dialog box is displayed.
5. Click OK. The Upload Deployment List dialog box is closed, and the upload starts.
The File Transfer Task tab page at the bottom of the Auto Deployment dialog box
displays detailed operation information, including Operation, Status, Object, Progress,
Start Time, End Time, and Information. When Progress is 100%, the upload is
complete.
----End
2. Perform the following steps to prepare a USB flash drive for local commissioning
(applicable to the NodeB, eNodeB, and BTS3900).
Procedure
Step 1 Choose Start > Programs > iManager U2000 MBB Client > USB Making and Protection
Tool to start the tool.

Copyright © Huawei
Figure 1.1 USB making and protection tool
Step 2 Choose Make USB > Path Settings. The Path Settings dialog box is displayed, as shown in
the following figure.

Copyright © Huawei
Figure 2.1 Path settings
Step 3 Set the local save paths for the software and files, NE type, and working mode based on the
types of USB flash drive directories. Then click OK.
When making different types of directories on a USB flash drive, specify items listed in the
Information to Set column only and do not set items that are not listed in this column.
You need to set the NE Type and Service Mode parameter only when the USB flash drive directory of
software is to be upgraded.
Item Information to Set
Directory for  Software Path: mandatory, save path of the files decompressed from
upgrading the a specified version software package.
software and  Cold Patch Path: optional, save path of the files decompressed from
updating a specified cold patch package.
configuration
files
 Hot Patch Path: optional, save path of the files decompressed from a
specified hot patch package.
Based on different version combinations of NEs to be deployed in the
deployment list, select Software Path, Cold Patch Path, or Hot Patch
Path. Then, click Add to add the path to the software version list.
Based on the target version information in the deployment list, the USB
making and protection tool copies different versions to the
corresponding directories of the NEs to be deployed. If an unnecessary
software version is added, you can click Delete to remove this software
version.

Copyright © Huawei
Auto Deployment List: mandatory. Select the deployment list exported

from the CME.
The exported deployment list is saved in export path/ADList/ by
default. Engineers must select the only .xml file in this directory.
NodeB/eNodeB/BTS3900 Precfg file: recommended. Select the
created Precfg.ini file.
If Precfg.ini is not selected, base station software is downloaded based
on the latest configurations that take effect. After the software and data
configuration files are loaded from the USB flash drive and the base
station is restarted, the software version of the newly added board will
be automatically added. If Precfg.ini is selected, the base station
downloads the software based on the board type specified in the
Precfg.ini file.
LTE Commissioning License: mandatory if LTE services are to be
enabled. Select the LTE commissioning license you have obtained.
Do not copy .csp file: this item is selected by default. If the prepared
directories need to be delivered to other engineers, select this item. In
this case, all files and integrity protection information except the .csp
files are saved in the directories and you can send them through emails.
Copy these files to the USB flash drive containing the intact software
package. Use this USB flash drive to upgrade the software and update
configuration files.
NOTE
The Do not copy .csp file item is not configured for the USB making and
protection tool of earlier versions. After the USB directories are prepared, you
need to manually delete the software directories MBTS\Software,
eNodeB\Software, and NodeB\Software to deliver the USB directories. Then,
copy these USB directories to the USB flash drive containing the intact software
package. Use this USB flash drive to upgrade the software and update
configuration files.
Support xMPT with SRAN7.0: If the preconfigured version of the

main control board of the NE to be deployed is SRAN7.0 or an earlier
version, select Support xMPT with SRAN7.0 so that the NE to be
deployed can be upgraded to SRAN11.0. If the preconfigured version
of the main control board of the NE to be deployed is SRAN8.0 or a
later version, do not select Support xMPT with SRAN7.0.
GTMU SingleOM Software: Configure this parameter if the BTS3900
to be deployed uses the GTMUb as the main control board. Select the
.csp file in the SingleOM software package supported by the GTMUb.
NOTE
When the USB making and protection tool copies the .csp file of the GTMUb
SingleOM, it checks whether the Precfg.ini file is under the same directory. If
yes, it also copies this Precfg.ini file to the USB:\BTS3900 GSM directory in the
USB flash drive.
Directory for Auto Deployment List: mandatory. Select the deployment list exported
updating from the CME.
configuration The exported deployment list is saved in export path/ADList/ by
files only default. Engineers must select the only .xml file in this directory.

Copyright © Huawei
LTE Commissioning License: mandatory if LTE services are to be

enabled. Select the LTE commissioning license you have obtained.
Directory for  Software Path: mandatory, save path of the files decompressed from
upgrading the a specified version software package.
software only  Cold Patch Path: optional, save path of the files decompressed from
a specified cold patch package.
 Hot Patch Path: optional, save path of the files decompressed from a
specified hot patch package.
Based on different version combinations of NEs to be deployed in the
deployment list, select Software Path, Cold Patch Path, or Hot Patch
Path. Then, click Add to add the path to the software version list.
Based on the target version information in the deployment list, the USB
making and protection tool copies different versions to the
corresponding directories of the NEs to be deployed. If an unnecessary
software version is added, you can click Delete to remove this software
version.
NodeB/eNodeB/BTS3900 Precfg file: recommended. Select the
created Precfg.ini file.
If Precfg.ini is not selected, base station software is downloaded based
on the latest configurations that take effect. After the software and data
configuration files are loaded from the USB flash drive and the base
station is restarted, the software version of the newly added board will
be automatically added. If Precfg.ini is selected, the base station
downloads the software based on the board type specified in the
Precfg.ini file.
NE Type and Service Mode: mandatory. Select
NodeB/eNodeB/BTS3900 and select one or multiple items among
GSM, UMTS, and LTE based on the working mode of the NE.
Do not copy .csp file: this item is recommended not to select.
NOTE
The Do not copy .csp file item is not configured for the USB making and
protection tool of earlier versions.
Support xMPT with SRAN7.0: If the preconfigured version of the

main control board of the NE to be deployed is SRAN7.0 or an earlier
version, select Support xMPT with SRAN7.0 so that the NE to be
deployed can be upgraded to SRAN11.0. If the preconfigured version
of the main control board of the NE to be deployed is SRAN8.0 or a
later version, do not select Support xMPT with SRAN7.0.
Step 4 The USB making and protection tool automatically parses the information of the target NE
and displays the information on the USB Making and Protection Tool interface. Select the
NE that requires a USB flash drive. After all NE information is correctly specified, select a
deployment mode in the USB Flash Drive Type area.
If the specified software package is a package for a single mode, you can only select NEs of this mode
when making a USB flash drive.

Copyright © Huawei
Option Description
One USB for One Site In this mode, save the information about
each NE to an independent USB flash drive.
One USB for Multiple Sites In this mode, save the information about all
NEs to a USB flash drive.
This mode requires that each NE be
configured with its ESN. This mode also
requires that the ESN and the main control
board's slot number of an NE cannot be both
the same as those of another NE.
Step 5 In the Protection Mechanism area, select an encryption algorithm from the Encryption
Algorithm drop-down list and select an integrity protection algorithm from the Integrity
Algorithm drop-down list.
 Encryption Algorithm is optional. It is selected by default and can be cleared. The
values of Encryption Algorithm include DES3_CBC, AES192_CBC, and
AES256_CBC. The default value DES3_CBC is recommended.
 Integrity Algorithm is mandatory. It is selected forcibly and cannot be cleared. The
values of Integrity Algorithm include HMAC_SHA1 and HMAC_SHA256. The
default value HMAC_SHA1 is recommended.
Step 6 In the Output Path area, specify a save path.
Option Description
USB Flash Drive Path Output all the information to a USB flash
drive. This path can store the directories of
one USB flash drive at one time.
 One USB for One Site: In this mode,
select only one NE and save this NE's
information to the USB flash drive.
 One USB for Multiple Sites: In this mode,
save the information about all NEs to a
USB flash drive. The software package
is shared by all NEs and the data
configuration files are distinguished by
ESN-named directories.
Local Path Save all the information to the specified
directory on a local PC.
 One USB for One Site: In this mode, a
folder is created in this directory for this
NE and named based on the NE name. In
addition, NE information is saved in this
folder.
specified directory. The software
package is shared by all NEs and the
data configuration files are distinguished

Copyright © Huawei
Option Description
by ESN-named directories.
The existing data configuration files may be damaged when being copied, encrypted, or integrity
protected. To prevent any damages, USB Flash Drive Path and Local Path must not contain any files
or directories.
Step 7 Click Start.
When making the USB directories, the USB making and protection tool automatically performs the
 Applies integrity protection and encryption protection to files under the USB directories according
to manual settings.
 Copies the configuration files to the USB directories of corresponding NEs according to the saving
path of configuration files in the deployment list.
 Copies all files under the directory specified by Software Path to the USB directories of
corresponding NEs according to the directory structure of the USB flash drive.
Step 8 Click OK in the dialog box displayed after the tool completes the making of the USB flash
drive.
Step 9 Optional: If Output Path is set to Local Path, copy the files to the USB flash drive. If Local
Path is set to Computer/DataCenter(D:)/USB File in Step 6.
 One USB for one site: Choose Computer >DataCenter(D:) > USB File, as shown in
Figure 9.1. If the NE to be deployed is site 1, copy the MBTS, NodeB, and eNodeB
folders from the Site1 folder to the USB flash drive.
 One USB for multiple sites: Choose Computer > DataCenter(D:) > USB File, as
shown in Figure 9.2. Copy the MBTS, NodeB, and eNodeB folders from the USB File
folder to the USB flash drive.
If you have not selected Support xMPT with SRAN7.0 in Path Settings, the MBTS
directory is generated. If you have selected Support xMPT with SRAN7.0 in Path Settings,
the generated directory has the following file folders: MBTS, NodeB, and eNodeB. Folders
NodeB and eNodeB are used for an upgrade of a main control board from SRAN7.0 or earlier
to SRAN10.0.

Copyright © Huawei
 After a file is copied from a computer to a USB flash drive, the file may change due to
faults on hardware or the Window OS, but this seldom occurs. In this case, you can copy
the file from another computer, to another USB flash drive, or restart the OS and copy the
file again.
 After the folders are copied to the USB flash drive, eject or safely remove the USB flash
drive from the Windows operating system. You can only remove the USB flash drive from
the PC after either of the preceding operations. If the USB flash drive is forcibly ejected,
the files in the USB flash drive may be damaged. As a result, software and data
configuration files cannot be loaded by using the USB flash drive.
 When transferring files for a making USB flash drive, do not copy the .xml files from a
remote desktop to a local PC. Otherwise, base station deployment will fail. You are
advised to compress the required files into a .rar or .zip file for file transfer.
You can use file comparison software, such as the BCCompare, to compare whether the file copied to
the USB flash drive is consistent with that on the computer.
Figure 9.1 File copy procedure in One USB for One Site mode

Copyright © Huawei
Figure 9.2 File copy procedure in One USB for Multiple Sites mode
When the base station with a GTMUb serving as the main control board is reconstructed for supporting
SingleOM, the BTS3900 GSM directory is generated. You need to copy this directory to the USB flash
drive.
----End
3. Perform the following steps to prepare a USB flash drive for local commissioning
(applicable to the GBTS).
Procedure
 Manually make a USB flash drive.
a. Save the required files in the specified paths on the USB flash drive.
Files required in different scenarios are listed in Table 1.1. Save paths for different
types of files on a USB flash drive are listed in Table 1.2. The directory structure on
a USB flash drive is shown in Figure 1.2.
 Path names are case sensitive.

 The name of the save path for TranCfg.INI cannot contain Chinese characters or double-byte
characters. Otherwise, the deployment fails.
Table 1.1 Files required for preparing a USB flash drive

Method of USB Flash Required Files
Preparing a Drive
USB Flash Directory
Drive
Creating Directory for  Software package and Pre-configuration script

manually upgrading the (Precfg.ini)
software and  Transmission configuration files (Trancfg.INI)
updating
configuration
 Transmission mode configuration file
files (TranModeCfg.ini)
Directory for  Transmission configuration files (Trancfg.INI)

Copyright © Huawei
Method of USB Flash Required Files

Preparing a Drive
USB Flash Directory
Drive
updating  Transmission mode configuration file

configuration (TranModeCfg.ini)
files only
Directory for Software package and Pre-configuration script
upgrading the (Precfg.ini)
software only
Using the USB Directory for  Software package and Pre-configuration script
making and upgrading the (Precfg.ini)
protection tool software and  Deployment lists and transmission mode
updating configuration file (TranModeCfg.ini)
configuration
files
Directory for Deployment lists and transmission mode
updating configuration file (TranModeCfg.ini)
configuration
files only
Directory for Software package and Pre-configuration script
upgrading the (Precfg.ini)
software only
Table 1.2 Save paths for different types of files on a USB flash drive
File Save Path
Software package usb:\BTS3900 GSM\software package name.csp

Pre-configuration script usb:\BTS3900 GSM\Precfg.ini
(Precfg.ini)
Transmission configuration One USB flash drive can only contain either of
files (Trancfg.INI) and Trancfg.INI and TranModeCfg.ini.
transmission mode  For TranCfg.INI:
configuration file
(TranModeCfg.ini) − If only one TranCfg.INI file is stored on the USB
flash drive, the save path is usb:\BTS3900
GSM\base station name\TranCfg.INI.
− If multiple TranCfg.INI files are stored on the USB
flash drive, the save path is usb:\BTS3900
GSM\ESN\TranCfg.INI.
 For TranModeCfg.ini: The save path is usb:\BTS3900
GSM\TranModeCfg.ini.

Copyright © Huawei
Figure 1.2 Directory Structure on a USB Flash Drive
b. For details about how to perform integrity protection and encryption on the files
stored on a USB flash drive, see Applying Integrity and Encryption Protection to
Files in a Single USB Flash Drive or Applying Integrity and Encryption Protection
to Files in Multiple USB Flash Drives.
 Use the USB making and protection tool to make a USB flash drive.
a. Choose Start > Programs > iManager U2000 MBB Client > USB Making and
Protection Tool to start the tool.

Copyright © Huawei
Figure 1.3 USB making and protection tool
b. Choose Make USB > Path Settings. The Path Settings dialog box is displayed, as

Copyright © Huawei
Figure 1.4 Path settings
c. Set save paths for the deployment list, pre-configuration script (Precfg.ini), and
transmission mode configuration file (TranModeCfg.ini). Then click OK.
When making different types of directories on a USB flash drive, specify items listed in the
Information to Set column only and do not set items that are not listed in this column.
You need to set the NE Type and Service Mode parameter only when the USB flash drive directory of
software is to be upgraded.
Directory for upgrading GBTS pre-configuration script (Precfg.ini): It is

the software and updating recommended that the save path of this file be configured.
configuration files Select the prepared Precfg.ini file.
When the Precfg.ini file is not selected, the NE only
downloads the software of the main control board. In this
case, after the NE restarts, it reconnects to the BSC and
downloads software of other boards from the BSC. When the
Precfg.ini file is not selected, the NE downloads the
corresponding software of the boards specified in the
Precfg.ini.
Deployment lists and transmission mode configuration file
(TranModeCfg.ini): Select these files based on the actual
conditions.
Deployment lists: Select this file when transmission
configuration files are used. The deployment list is saved

Copyright © Huawei
under Exported directory/ADList/ when exported from the

CME. The operation personnel can only select the unique
.xml file under this directory, and the tool automatically
copies the TranCfg.INI file to the specified directory.
GBTS transmission mode configuration file
(TranModeCfg.ini): Select this file when transmission mode
configuration files are used. When selecting such a file, find
the file, and the tool automatically copies TranModeCfg.ini to
the specified directory.
Do not copy .csp file: Software Path is not set, and
therefore Do not copy .csp file does not take effect regardless
of whether it is selected or not.
Support xMPT with SRAN7.0: This parameter does not take
effect regardless of whether it is selected or not.
Directory for updating Deployment lists and transmission mode configuration file
configuration files only (TranModeCfg.ini): Select these files based on the actual
conditions.
Deployment lists: Select this file when transmission
configuration files are used. The deployment list is saved
under Exported directory/ADList/ when exported from the
CME. The operation personnel can only select the unique
.xml file under this directory, and the tool automatically
copies the TranCfg.INI file to the specified directory.
GBTS transmission mode configuration file
(TranModeCfg.ini): Select this file when transmission mode
configuration files are used. When selecting such a file, find
the file, and the tool automatically copies TranModeCfg.ini to
the specified directory.
Directory for upgrading GBTS pre-configuration script (Precfg.ini): It is
the software only recommended that the save path of this file be configured.
Select the prepared Precfg.ini file.
When the Precfg.ini file is not selected, the NE only
downloads the software of the main control board. In this
case, after the NE restarts, it reconnects to the BSC and
downloads software of other boards from the BSC. When the
Precfg.ini file is not selected, the NE downloads the
corresponding software of the boards specified in the
Precfg.ini.
NE Type and Service Mode: GSM under GBTS must be
selected .
Do not copy .csp file: Software Path is not set, and
therefore Do not copy .csp file does not take effect regardless
of whether it is selected or not.
Support xMPT with SRAN7.0: This parameter does not take
effect regardless of whether it is selected or not.

Copyright © Huawei
d. The USB making and protection tool automatically parses the information of the
target NE and displays the information on the USB Making and Protection Tool
interface. Select the NE that requires a USB flash drive. After all NE information is
correctly specified, select a deployment mode in the USB Flash Drive Type area.
Item Description
One USB for One Site In this mode, save the information about
each NE to an independent USB flash drive.
One USB for Multiple Sites In this mode, save the information about all
NEs to a USB flash drive.
This mode requires that each NE be
configured with its ESN. This mode also
requires that the ESN and the main control
board's slot number of an NE cannot be both
the same as those of another NE.
e. In the Protection Mechanism area, select an encryption algorithm from the

Encryption Algorithm drop-down list and select an integrity protection algorithm
from the Integrity Algorithm drop-down list.
다 Encryption Algorithm is optional. It is selected by default and can be cleared.
The values of Encryption Algorithm include DES3_CBC, AES192_CBC,
and AES256_CBC. The default value DES3_CBC is recommended.
라 Integrity Algorithm is mandatory. It is selected forcibly and cannot be
cleared. The values of Integrity Algorithm include HMAC_SHA1 and
HMAC_SHA256. The default value HMAC_SHA1 is recommended.
f. In the Output Path area, specify a save path.
Item Description
USB Flash Drive Path Output all the information to a USB flash
drive. This path can store the directories of
one USB flash drive at one time.
 One USB for One Site: In this mode,
select only one NE and save this NE's
information to the USB flash drive.
USB flash drive. The software package
is shared by all NEs and the data
configuration files are distinguished by
ESN-named directories.
Local Path Save all the information to the specified
directory on a local PC.
 One USB for One Site: In this mode, a
folder is created in this directory for this
NE and named based on the NE name. In
addition, NE information is saved in this
folder.

Copyright © Huawei
Item Description
specified directory. The software

package is shared by all NEs and the
data configuration files are distinguished
by ESN-named directories.
The existing data configuration files may be damaged when being copied, encrypted, or integrity
protected. To prevent any damages, USB Flash Drive Path and Local Path must not contain any files
or directories.
g. Click Start.
When making the USB directories, the USB making and protection tool automatically performs the
 Applies integrity protection and encryption protection to files under the USB directories according
to manual settings.
 Copies the configuration files to the USB directories of corresponding NEs according to the saving
path of configuration files in the deployment list.
h. Click OK in the dialog box displayed after the tool completes the making of the
USB flash drive.
i. If the Local Path option is selected in the Output Path area, copy the files to the
USB flash drive. In the save path specified by Local Path in ii, select the folders of
the NEs to be deployed and copy the folders to the USB flash drive.
 After a file is copied from a computer to a USB flash drive, the file may change due to
faults on hardware or the Window OS, but this seldom occurs. In this case, you can copy
the file from another computer, to another USB flash drive, or restart the OS and copy the
file again.
 After the folders are copied to the USB flash drive, eject or safely remove the USB flash
drive from the Windows operating system. You can only remove the USB flash drive from
the PC after either of the preceding operations. If the USB flash drive is forcibly ejected,
the files in the USB flash drive may be damaged. As a result, software and data
configuration files cannot be loaded by using the USB flash drive.
 When transferring files for a making USB flash drive, do not copy the .xml files from a
remote desktop to a local PC. Otherwise, base station deployment will fail. You are
advised to compress the required files into a .rar or .zip file for file transfer.
You can use file comparison software, such as the BCCompare, to compare whether the file copied to
the USB flash drive is consistent with that on the computer.
j. Open the BTS3900 GSM directory on a USB flash drive, decompress the software
package of the target version-BTS3900
V100RXXXCXXSPCXXX_GBTS(Tools).zip file, and copy the .csp file for
upgrading the GBTS using a USB flash drive to this directory.

Copyright © Huawei
Figure 1.5 File copy procedure for GBTS commissioning
4. Perform the following steps to start an NE commissioning task:

Copyright © Huawei
Procedure
Step 1 On the U2000 client, choose SON > Self Planning > Auto Deployment (application style) or
SON > Auto Deployment (traditional style). The Auto Deployment window is displayed.
Step 2 Start the NE commissioning task, as shown in the following figure.
Figure 2.1 Starting an NE commissioning task
----End
1. Select one or multiple commission tasks and right-click these commissioning tasks.
Click Start. The Task Parameter Settings window is displayed.
If global parameters have been set before the start of a commissioning task, parameters in the Task
Parameter Settings dialog box use the global parameter settings. Engineers can modify the parameter
settings based on the actual data plan. Global parameters can be set as follows: Right-click the
commissioning task list area and choose Global Parameter Settings.
2. Set Step Parameters as planned.
Tip 1: Choose the corresponding operations as planned.
 : indicates that this step is mandatory and cannot be changed manually.

Copyright © Huawei
 : indicates that this step is optional and executed by default.

 : indicates that this step is optional and not executed by default.
For details about the USB+U2000-based commissioning process for a newly deployed
base station, see Table 1.1.
Table 1.1 USB+U2000-based commissioning process for a newly deployed base station
1 Auto discover site Check OM channel The U2000 determines

whether to select this
procedure.
2 Auto configure Download site software This procedure is not
site selected.
Download site If the data configuration file
configuration is stored on the USB flash
drive, do not select this
procedure. Otherwise, select
this procedure.
NOTE
This check box does not exist if
the NE to be commissioned is
the GBTS.
Activate site The U2000 selects this

procedure if Download site
configuration is selected.
3 Deliver license Deliver commissioning If the commissioning license
license is stored on the USB flash
drive, do not select this
procedure. Otherwise, select
this procedure.
4 Test installation & Monitor RF module The U2000 selects this
deployment service status procedure.
quality
Intervene The U2000 selects this
procedure.
Test installation & This procedure is optional
deployment quality but recommended.
5 Waiting for Waiting for The system automatically
confirmation confirmation selects this procedure.
3. Set Extended Parameters as planned.

Tip 2: Extended Parameters defines threshold parameters for commissioning the
antenna system in the Test installation & deployment quality phase. If there are no
special requirements, default values of these parameters are used. If there are special
requirements, set these parameters as required.
4. Click OK.

Copyright © Huawei
Tip 3: After the start of an NE commissioning task is confirmed, the U2000 checks the
required data configuration file:
If the data configuration file is available, the U2000 starts commissioning and the
corresponding task is in the Running state.
11.4 PnP-based Co-MPT Reconstruction

If a separate-MPT base station is to be reconstructed into a co-MPT base station and new
mode is to be added, PnP-based co-MPT reconstruction must be performed to deliver and
validate base station data.
1. Perform the following steps to export the auto-deployment data file.
Procedure
Step 1 On the menu bar, choose Advanced > Export Auto Deployment Data (CME client mode) or
CME > Advanced > Export Auto Deployment Data (U2000 client mode). A dialog box is
displayed for you to export auto-deployment data.
Step 2 Select Site creation/expansion, and click Next.
Step 3 Select the base stations whose auto-deployment data you want to export, and click Next.
You can click Load to select base stations to be exported by loading a file. The method of obtaining the
file, Click Export. The CME then exports the file. You have to set values for the parameters in the
exported file.
If the check boxes and buttons are unavailable, you can only view information in the dialog box.
Step 4 Select a save path for the exported file and a method for processing data, and click Next.
If... Then...
Export  After Export NE security configuration data is selected, if the current

data user has the Obtain NE Security Configuration Data operation rights,
from the NE sensitive data is displayed in plain text in the exported data file; if the
current current user does not have the Obtain NE Security Configuration Data
area operation rights, a message is displayed on the CME, indicating that
sensitive data cannot be exported.
 After Export NE security configuration data is cleared, sensitive data is
displayed as ***** in the exported data file.
Export Select the method for verifying data as required.
data
from the
planned
area
Step 5 View data in the base station deployment list, and click Next. The CME starts to verify data

Copyright © Huawei
 If the parameter values displayed on the GUI are different from planned values, you need to change
the parameter values based on the planned values. Otherwise, the deployment may fail.
 You can only set the first level subnet information. To specify subnets at other levels, adjust the
subnet information in the U2000 topology view after base station commissioning.
If the user-specified subnet information does not exist on the U2000, the U2000 automatically
generates the subnet during the import of auto-deployment data in the commissioning.
 If Auto assigned is selected from the Subarea drop-down list, the U2000 automatically assigns
subareas for NEs by following the subarea load balancing principle when auto-deployment data is
imported into the U2000.
 When editing data, you can use Ctrl+C and Ctrl+V to copy information from one cell to multiple
cells.
Step 6 If the export is successful in U2000 client mode, set the following options:
 Select Do not open the Auto Deployment window to close the wizard.
 Select Open the Auto Deployment window. The CME automatically switches to the
auto-deployment window and creates a commissioning task.
 Select Open the Auto Deployment window and start Auto Deployment task. The
CME automatically switches to the auto-deployment window and starts a commissioning
task.
The save paths for the exported data configuration scripts and deployment lists are as follows:
 Data configuration scripts: export directory\CfgData\base station name
You can use the script executor to check and edit the exported data configuration scripts.
----End
2. Perform the following steps to start an NE commissioning task for the scenario where
modes are added in co-MPT reconstruction.
Step 1 Create a task of site reconstruction on the U2000.
1. On the U2000, choose SON > Auto Deployment. On the Deployment List tab page,
right-click a site and choose Import Deployment List to import the deployment list
generated during data conversion.
2. On the Site Configuration Data tab page, upload data configurations of a co-MPT site
generated after site reconstruction to the U2000.
3. On the Controller Configuration Data tab page, upload MBSC reconstruction scripts
generated after site reconstruction to the U2000.
4. On the Software&Cold Patch tab page, upload GTMU conversion software and co-
MPT software to the U2000 if required based on site reconstruction requirements.
To upload the GTMU conversion software, set NE type to GBTS. To upload the co-MPT
software, set NE type to BTS3900.

Copyright © Huawei
Step 2 Download the GTMU conversion software and co-MPT software.

1. During PnP task settings, site software needs to be loaded beforehand to reduce the time
for software loading at night. For batch reconstruction of multiple sites, finish data
configuration in the Task Parameter Settings dialog box for each site beforehand.
Details are as follows:
− Select Download GTMU evolution software and Download site software when
separate-MPT GBTSs are reconstructed with GTMU conversion adopted.
− Select only Download site software when separate-MPT GBTSs/eGBTSs are

reconstructed with GTMU abandonment adopted or when modes are added during
co-MPT reconstruction with the GSM mode not involved.
2. Start a PnP-based co-MPT reconstruction task on the U2000.

Copyright © Huawei
After this task is executed, the status of the task will be Waiting for Confirmation. In this
case, do not confirm it. Then, you can repeat the task subsequently. If you confirm it, you
have to create another PnP task later.
Step 3 Restart the site reconstruction task. Specifically, execute reconstruction scripts (when a base
station controller is involved), and download and activate the configuration file.
1. Restart the PnP task.
In BSC node redundancy scenarios, perform the PnP tasks on the master and slave BSCs at the same
time.
Finish data configuration in the Task Parameter Settings dialog box before
reconstruction. Specifically, select Download BSC configuration data, Query GBTS
license information, Deliver license, Download site software, Download site
configuration, and Activate site. Then click Restart to start the batch reconstruction.
For the reconstruction scenarios of GU+L/GL+U with BBUs interconnected, select Change
the peer main control board to co-MPT to ensure that BBU 1 works as the secondary BBU
after reconstruction; or select Activate GTMU evolution software when the preceding steps
are performed for a co-MPT base station using the UMPT after reconstruction.
2. Click Restart to start the reconstruction.

3. After the task is complete, click Confirm Completion.

Copyright © Huawei
Ensure a reachable route between the U2000 and IP address of the base station after
reconstruction before clicking Confirm Completion. In this way, licenses can be successfully
delivered, and the PnP task will be complete.
Step 4 Adjust data of intermediate devices.
This step is required only when co-transmission is not used before reconstruction and GSM uses the IP
over FE transmission.
1. If gateways of the separate-MPT multimode base stations before the reconstruction use
different next-hop IP addresses, use either of the original IP addresses and next-hop IP
addresses for the router or Layer 3 switch for co-transmission after the reconstruction.
2. If the gateways of the separate-MPT multimode base stations before the reconstruction
use the same next-hop IP address, skip this step.
Step 5 Deliver incremental BSC scripts (when GSM/UMTS is to be added).
Manage activation data using the CME executor. For details, see Activating Data.
Step 6 Adjust and deliver the license.
The following describes how to adjust "UMPT Multi Mode License" for an eGBTS when
GSM is involved in reconstruction.
 On the U2000, synchronize configurations, and the eGBTS that is newly deployed on the
BSC will be displayed.
 On the eGBTS licensed-resource allocation page of the U2000, choose a BSC, right-
click the newly deployed eGBTS, and choose Modify. In the displayed window, set
UMPT Multi Mode License(GSM) (per UMPT) to 1, and click OK.
 On the licensed-resource allocation page, right-click the eGBTS and choose Allocate
Remaining Resources to BSC. The licensed value of the GBTS (BSC) is automatically
modified.
 Right-click the activated eGBTS license file and choose Distribute.
Step 7 Verify the reconstruction.
Check whether the reconstruction succeeds. If it succeeds, adjust the DHCP server, and then
modes are successfully added. If it fails, perform the following operations to roll back base
stations to the status before reconstruction.
13.4 How Can I Roll Back Base Stations When Co-MPT Reconstruction Fails?
Perform the following operations to verify the co-MPT reconstruction:
1. Start the U2000, and check whether the target base station has become a co-MPT base
station whose NE type is now BTS3900.
− Right-click the target base station and choose Properties. In the displayed NE
Properties dialog box, check whether the value of NE Type is BTS3900.

Copyright © Huawei

Copyright © Huawei
− Check whether the modes deployed on the target base station are displayed, as
− Right-click the target base station and choose Device Maintenance to check
whether the mode information about each board is correct, as shown in the
following figures. Note that the UMPT serves multiple modes, the WBBP serves
the UMTS mode, the LBBP serves the LTE mode, and the
UBRI/UTRP/FAN/UCIU/UEIU/UPEU/PSU/TCU serves multiple modes.

Copyright © Huawei
− For the reconstruction scenarios of GU+L/GL+U/UL, the system will automatically

convert the base station deployed with the reference mode to a co-MPT base station
during the reconstruction, but will not handle the base station deployed with the
non-reference mode. In this case, you need to manually check whether the
reconstruction succeeds and whether the rollback is required (the rollback is not
required after the reconstruction succeeds). If the reconstruction succeeds, manually
remove the base station deployed with the non-reference mode from the U2000

Copyright © Huawei
MBTS topology. After the base station is removed, its historical alarms and traffic
statistics are all deleted and you cannot query them. The status of the base station
deployed with the non-reference mode is unavailable. Delete such a base station as
follows:
가 Select the name of the base station to be deleted on the topology.
나 Right-click the base station and choose Delete.
다 Click Yes in the Confirm dialog box.
2. Check whether services of each mode are processed properly after reconstruction.
3. Check whether new alarms are generated after co-MPT reconstruction. If new alarms are
generated, clear them.
− Check whether alarms related to separate-MPT NEs indicate errors. If they do not,
manually clear them.
− If alarms are user-defined alarms before reconstruction, such as an environmental
alarm, you need to define alarms for the co-MPT base station after reconstruction
because the NE type has changed to BTS3900.
4. After the reconstruction, check whether boards are functioning properly, software
versions of these boards are correct, and the status of cells is normal. Check whether the
software versions of the UMPT, GTMU, and LMPT meet expectations. Note that the
GTMU works as an interface board and the LMPT works as a signaling capacity
expansion board after reconstruction.

Copyright © Huawei
5. Check whether the values of service KPIs specific to each mode are normal and whether
these values unexpectedly fluctuate after co-MPT reconstruction.
For measurement items registered on the U2000 before reconstruction, you need to register
measurement items for the co-MPT base station because the NE type has changed to
BTS3900.
Step 8 Adjust the DHCP server.
The DHCP server must be deployed on the U2000 after the reconstruction. If the DHCP
server is deployed on the BSC before the reconstruction, you need to switch it from the BSC
to the U2000. If the DHCP server is deployed on the U2000 before the reconstruction, skip
this step.
----End

Copyright © Huawei
Mode Transition Guide(For NB) 12 Ending Maintenance Mode for NEs
12 Ending Maintenance Mode for NEs
Restore the maintenance mode for the base station when it is operating properly after the
commissioning.
You may restore the maintenance mode by NE or by mode, which must be consistent with the
granularity when you set the maintenance mode. Use the same way to set the maintenance
mode to Normal.

Copyright © Huawei
Mode Transition Guide(For NB) 13 Appendix for Co-MPT Reconstruction
13 Appendix for Co-MPT Reconstruction
This section describes the appendix for co-MPT reconstruction scenarios.
13.1 Paths for Saving Converted Data

1. Paths for saving the deployment list and configuration data of a separate-MPT base
station
− Path for saving the deployment list
<OUT_PUTDIR>\BakData\ AutoDeployment_***\AdList\
Auto_Deployment_List_***.xml
− Path for saving the configuration data
<OUT_PUTDIR>\BakData\AutoDeployment_***\CfgData\<site name>\***.xml
2. Path for saving reconstruction scripts
Path for saving the GBTS reconstruction MML scripts
<OUT_PUTDIR>\mml\<BSC name>\Convert\<site name>.txt
3. Path for saving rollback scripts
− Path for saving the project file which is used to creat a rollback task and will be
imported to the CME executor
<OUT_PUTDIR>\mml\<controller name>\Fallback\scriptcfg.xml
− Path for saving the GBTS rollback MML scripts
<OUT_PUTDIR>\mml\<BSC name>\Fallback\<site name>.txt
4. Path for saving the co-MPT data configuration file after reconstruction
<OUT_PUTDIR>\AutoDeploymentData\CfgData\<site name>\CFGDATA.XML
5. Path for saving the deployment list after reconstruction
<OUT_PUTDIR>\AutoDeploymentData\ADList\***.xml
6. Path for saving conversion logs
<OUT_PUTDIR>\rpt\***.txt
Logs recorded during the conversion are saved in this path.
When separate-MPT multimode base stations are reconstructed into one co-MPT base
station, the conversion tool consolidates the node MOs of the multiple modes to those for

Copyright © Huawei
the co-MPT base station. When configuration data differs with modes, the tool modifies
the configuration data for the modes involved based on the value of the
SRANBaselineRAT parameter in the data planning template. If this parameter is not
specified, the tool applies the configuration data used on the more advanced mode to the
other modes of the MBTS in question. For example, the tool applies the configuration
data used on the UMTS side to the GSM of a GU dual-mode base station. If this
parameter is specified, the tool applies the configuration data used on the specified mode
to the other modes of the MBTS in question.
If consolidated data affects the system, alarms will be generated and displayed in the
result area and conversion logs. You need to determine whether the data needs to be
adjusted based on actual network conditions.
13.2 Preparing GSM Licenses

For the reconstruction where the GSM mode is involved, an eGBTS license file introduced in
SRAN8.0 is required in addition to a BSC license file. From SRAN8.0 onwards, the license
management system is consistent between GSM and UMTS in co-MPT reconstruction
scenarios. Specifically, the licensed resources for a BSC are contained in a BSC license file,
and the licensed resources for the GBTSs are contained in an eGBTS license file. In versions
earlier than SRAN8.0, the licensed resources for both the BSC and GBTS are contained in a
BSC license file. For co-MPT reconstruction, you need to split the existing permanent
commercial or permanent&temporary license file of a BSC into a BSC license file (containing
the licensed resources for the BSC only) and an eGBTS license file (containing the licensed
resources for eGBTSs only). In addition, you may need to purchase certain licenses for
features deployed on base stations (the licenses are quoted by sales personnel). Then global
technical service (GTS) personnel merge a newly delivered eGBTS license file with the
eGBTS license file after splitting on the license website. The following figure shows an
example. Steps boxed in the dotted line are optional and can be performed by frontline
personnel according to the actual situation.

Copyright © Huawei
If a BSC uses a commissioning license or temporary commercial license, you cannot obtain
an eGBTS license file by splitting the license on the FNO. In this scenario, you need to apply
for a commissioning license or temporary commercial license for the eGBTS by using the
eGBTS license template at least one week in advance.
Note that Huawei now supports two license distribution platforms: FNO and ESDP. You can
apply for licenses on either of them. This document uses the FNO as an example to describe
license application.
GSM license preparation is required only when the first batch of base stations to be
reconstructed are all GBTSs.
(Recommended) Using a Permanent Commercial License or

Permanent&Temporary Commercial License
Step 1 Split the license.
After the reconstruction, obtain the license file for the eGBTS and that for the corresponding
BSC by splitting the original BSC license file. The following describes how to split the BSC
license file:
 On the Web LMT of the BSC6900/BSC6910 to which the eGBTS belongs, revoke the
BSC license file on the BSC and obtain the revocation code.
a. Run the LST LICENSE command to query the activated license file.
b. Run the RVK LICENSE command. In this step, enter the name of the license file
to be revoked.
 Log in to the FNO on the website of license.huawei.com. Choose GTS Portal > Split
GSM License.
 Enter the revocation code and click Search. Then the resources to be split are listed.

Copyright © Huawei
 Click Submit. The system will split a BSC license file into a new BSC license file and
an eGBTS license file.
After the task is complete, the FNO will send the results to your mailbox. If the task fails,
click Error Repair. If the error persists, contact the IT hotline or License Fulfillment
Department.
Click My Task and then download the license files. You can also download the license files
from your mailbox.

Copyright © Huawei
Only licensed control items for features supported by both eGBTSs and GBTSs and those
supported only by GBTSs can be split through the preceding steps. (License control items for
features supported only by GBTSs can be delivered by the U2000 to the BSC in order to
control the GBTSs. In this way, license files do not need to be replaced when the eGBTSs
support such features subsequently.) The UMPT Multi Mode License(GSM)(per UMPT)
supported by eGBTSs needs to be separately applied for, and is not required in GO co-MPT
reconstruction. Such license control items for eGBTSs as the IPSec bypass (per BTS), UMPT
Multi Mode License(GSM), Antenna Feeder Intermodulation Test (per TRX), and Spectrum
Scan (per TRX) must be applied for in other ways. For details, see GBSS18.1 eGBTS License
Application Guide.
Only a permanent commercial license and the permanent license in a permanent&temporary
license can be split into an eGBTS license file. A commissioning license or a temporary
commercial license cannot be split into an eGBTS license file on the FNO. You need to apply
for a commissioning license or temporary commercial license for the eGBTS using the license
application template at least one week early.
Step 2 Apply for new license control items that cannot be obtained from step 1 for the eGBTS, such
as the license control item "UMPT Multi Mode License(GSM)", and incorporate them into
the eGBTS license file after splitting.
----End
If a commissioning license or a temporary commercial license is used for reconstruction, skip

this step. You can obtain all the licenses for the eGBTS using the eGBTS license application
template by performing step 1.
To incorporate license files, perform the following operations:

1. Visit license.huawei.com to log in to the FNO.
2. On the FNO, choose GTS Portal > Manage Licenses > Manage Licenses.
3. In the displayed window, choose ESN from the drop-down list of Search By. Enter an
ESN in the text box of Search For. Click to query all the license files of this NE.

Copyright © Huawei
4. Select the NE license files for the same product. Click Consolidate and the window
shown in the following figure will be displayed. Select the incorporated license files to
be downloaded and click Save to File to save these files on the local PC.
The license control item "UMPT Multi Mode License(GSM)" must be applied for when
multimode base stations to be reconstructed serve GSM. In this scenario, the license
control item should be quoted first by sales personnel, and then the GTS personnel apply
for the license control item. For more information, see steps 1 to 5 of section "Applying
for a License During Version Upgrade, Capacity Expansion, or New Feature
Deployment" in chapter "License Application Operations Guidance in Different
Scenarios" in GBSS18.1 eGBTS License Application Guide. For the license control items
"Antenna Feeder Intermodulation Test (per TRX) and "Spectrum Scan (per TRX)", only
a temporary license can be applied for when a permanent commercial license or
permanent&temporary commercial license is used. For more information, see steps 1 to
4 of section "Applying for a Permanent&Temporary/Trial License" in chapter "License
Application Operations Guidance in Different Scenarios" in GBSS18.1 eGBTS License
Application Guide.
"IPSec bypass (per BTS)" is a customized license control item, and is usually not
required during the reconstruction. If it is required, the license control item should be
quoted first by sales personnel, and then the GTS personnel apply for the license control
item. For more information, see steps 1 to 5 of section "Applying for a License During
Version Upgrade, Capacity Expansion, or New Feature Deployment" in chapter "License
Application Operations Guidance in Different Scenarios" in GBSS18.1 eGBTS License
Application Guide.

Copyright © Huawei
The steps above have covered the operations for obtaining the eGBTS license and
incorporating new license control items.
(Not Recommended) Using a Temporary Commercial License or Commissioning

License for GSM
If no permanent commercial license or permanent&temporary license for a BSC is available
during the reconstruction, apply for temporary commercial or commissioning licenses for the
eGBTS and BSC.
If the permanent commercial license or permanent&temporary license for a BSC is available
during the reconstruction and the eGBTS will be restored to a GBTS after the reconstruction,
retain the existing BSC license and apply for a temporary commercial or commissioning
license for the eGBTS.
When these two types of license files are used for reconstruction, all license control items for
an eGBTS (the license control item "UMPT Multi Mode License(GSM)" must be contained)
must be directly applied for instead of being obtained by splitting the BSC license file.
For details on how to apply for a temporary commercial license for the eGBTS, see section
"Applying for a License in Exceptional Cases" of chapter "License Application Operations
Guidance in Different Scenarios" in GBSS18.1 eGBTS License Application Guide.
For details on how to apply for a commissioning license for the eGBTS, see section
"Manually Applying for a Commissioning License" of chapter "License Application
Operations Guidance in Different Scenarios" in GBSS18.1 eGBTS License Application Guide.
13.3 What Should I Do If an Error Prompting "Data

Preparation failed" Occurs During the Execution of a PnP
Task?
An error occurs during the PnP task execution, as shown in the following figure.
The error indicates that the version of GTMU conversion software saved on the U2000 is
inconsistent with that in the auto-deployment list. First, check whether the parameter
ActBTSSoftwareVersion is specified in the data planning template and whether the value is
correct. If the parameter is not specified or the parameter value is incorrect, specify or correct
it and convert data again. If the parameter is correctly specified, check whether the GTMU
conversion software package has been uploaded to the U2000 and whether the version is
consistent with the specified one. If the software package has not been uploaded or the
package version is inconsistent with the specified one, upload the specified software package
and execute the PnP task again.

Copyright © Huawei
13.4 How Can I Roll Back Base Stations When Co-MPT

Reconstruction Fails?
1. Adjust site hardware.
Restore the hardware to the status before the reconstruction.
 Replace the transmission and main control boards with those used before reconstruction
and insert the original boards to the corresponding slots.
 Replace the baseband processing boards with those used before reconstruction and insert
the original boards to the corresponding slots. In addition, remove the newly added
baseband processing boards or UBRI boards.
 Replace the RF modules with those used before reconstruction and insert the original
units to the corresponding boards. In addition, adjust the antenna system.
 Connect the transmission cables to the original ports before reconstruction.
 Connect the CPRI cables to the original ports before reconstruction.
 Reset the RF boards whose CPRI cable connections are adjusted.
2. Roll back data configurations on the BSC side.
This operation is required when the GSM mode is involved in the reconstruction.
Upload scripts through the CME script executor. Specifically, select the directory where the
rollback scripts described in 3 are saved to import the BSC rollback scripts. Then execute the
rollback scripts to roll back BSC data configuration.
3. Create a NodeB or an eNodeB on the U2000.
Create the same separate-MPT NEs as those before reconstruction through the Auto
Deployment function.
4. Perform a power-off reset on the GTMU.
When GSM is involved in reconstruction and the GTMU is converted, a power-off reset is
required on the GTMU for rollback to prevent the GTMU from exceptions after the GTMU
software version is rolled back and the GTMU works as a main control unit again.
Perform this operation once the NodeB/eNodeB is normal. You can run the following
command to power off the GTMU: RST BRDPWROFF:CN=0,SRN=0,SN=6;
5. Change the NodeB's OMCH IP address configured on an RNC.
Change the NodeB's OMCH IP address configured on an RNC to the OMCH IP address of the
NodeB before the reconstruction for rollback in the following reconstruction scenarios: UL
site reconstruction (LTE is deployed as the reference mode), GL+U site reconstruction, and
two BBUs are consolidated (including UMTS and LTE, with LTE as the reference mode).

Copyright © Huawei
 Run the LST OMCH command to query the OMCH IP address of the NodeB.
 Run the MOD UNODEBIP command to change the NodeB's OMCH IP address
configured on the RNC to the OMCH IP address of the NodeB before reconstruction.
The following is a command example: MOD UNODEBIP: IDTYPE=BYID,
NODEBID=1, NBTRANTP=IPTRANS_IP, NBIPOAMIP="10.171.35.123",
NBIPOAMMASK="255.255.255.0", IPSRN=0, IPSN=18, IPLOGPORTFLAG=NO;
13.5 Constraints and Limitations

Limitations on the Standalone CME
1. After the standalone CME is used to prepare co-MPT configuration data in offline mode,
the cabinet No., subrack No., and slot No. of the main control board cannot be adjusted
and the main control board cannot be removed during the device reconstruction on the
standalone CME. In the co-MPT reconstruction scenario where the GSM mode is
included, the GTMU handling method cannot be changed during other reconstruction
activities in offline mode after co-MPT reconstruction. For example, GTMU evolution is
adopted during co-MPT reconstruction, and the GTMU cannot be abandoned during
device reconstruction. If you change the GTMU handling method, the deployment list
exported by the standalone CME after configuration data is prepared will be abnormal.
2. The configuration data of the GBTS can be converted only in By ID mode by using the
standalone CME. To set the By ID mode, select By ID in the GSM Script Index Type
Options dialog box.

Copyright © Huawei
Limitation on NE Equipment
1. Data of only the following GSM base stations can be reconstructed: DBS3900 (GSM),
BTS3900 (GSM), BTS3900A (GSM), BTS3900L (GSM), and BTS3900AL (GSM).
2. Co-MPT reconstruction is not supported on super base stations.
3. Co-MPT reconstruction is not supported if a GBTS is configured with a DRFU, DRRU,
or UTRP.
4. Co-MPT reconstruction is not supported if the Send Mode parameter of a GBTS is set to
a value other than NOCOMB(No Combination) or DTIC(Transmit Independency or
Combination).
5. Omit the following functions during co-MPT reconstruction if any of them are enabled
for a GBTS: inter-module RF frequency hopping or inter-module power sharing, and
inter-PA RF frequency hopping or inter-PA power sharing.
6. Co-MPT reconstruction is not supported if two sectors in different modes share part of
antennas before reconstruction, or if two baseband devices in different modes share part
of baseband processing units before reconstruction.
7. Co-MPT reconstruction is not supported if alarms related to configuration conflicts
persist. The configuration may conflict when the baseband processing boards or RF units
(except those in the dual-star topology) are configured in the same place for two modes
or different boards are configured in the same place for two modes.
8. The GTMUa boards for the GSM sites can only fall into disuse and cannot be converted
after the reconstruction.
9. If the replaced LMPT and WMPT boards are used as main control boards in other sites,
the IP configuration data retained in the boards may conflict with that of other sites. In
this scenario, download the data configuration using the USB or LMT before connecting
them to the transmission network.
10. Only one user can convert the GBTSs under the same BSC for one time.
11. In the BSC node redundancy scenarios, the scenario where the GBTSs can be
reconstructed to eGBTSs only after the BSC switchover is not considered. (This is new
in SRAN9.0.)
12. When the GBTS includes RFU and RRU and the RRUs are connected to the UBRI and
RFU to the GTMU through the CPRI cables, the GBTS is reconstructed into the eGBTS
through GTMU evolution. This is because a new UBRI is required if the GTMU is
abandoned, and the Multi-site Cell feature for GBTS does not support co-cell between
two transmission boards.
13. The separate-MPT base stations configured with BBU3910 can be reconstructed to co-
MPT base stations. Hardware configuration (subrack quantity, subrack type, subrack

Copyright © Huawei
number, board quantity, board type, and slot number) remains unchanged after the
reconstruction. (This is new in SRAN9.0.)
14. The BBU3910A has only one main control unit, and therefore it supports multiple modes
implemented only by the co-MPT. In this case, it involves the UO/LO co-MPT
reconstruction only. If the BBU3910A needs to support multimode co-MPT, it is
recommended that a new multimode co-MPT base station be deployed or modes be
added to the main control board after single-mode co-MPT reconstruction. The
BBU3910A neither supports a GBTS nor BBU interconnection. (This is new in
SRAN10.0.)
15. After a separate-MPT multimode base station enabled with the CPRI MUX feature is
reconstructed into a co-MPT base station, the UBRIb or UBBPd serves as the converging
board if CPRI ports of the co-MPT base station carry GU/GL services. For details, see
CPRI MUX Feature Parameter Description in 3900 Series Base Station Product
Documentation.
16. To reduce the GSM service interruption duration, load the GTMUb/GTMUc conversion
software before co-MPT reconstruction from GU/GL/GU+L/GL+U base station. In this
scenario, you are advised to perform reconstruction for ten base stations in a batch.
Reconstruction for too many base stations at a time may fail within the specified period
of service interruption because the BSC scripts are executed one by one. If multiple
MBTSs to be reconstructed have the same reference mode, reconstruction can be
implemented at a time. If multiple MBTSs to be reconstructed have different reference
modes, reconstruction must be implemented in different batches.
17. If different BSCs have GBTSs with the same name, faults may occur during
configuration data conversion. In this scenario, run the MOD BTS command on the BSC
LMT to modify the name of the GBTSs. Similarly, before co-MPT reconstruction for
GU, UL, GUL, UO base stations, query the names of NodeBs on the following three
sides: on the RNC (by running the LST UNODEB command), on the U2000, and in the
NodeB configuration data (by running the LST NE command). Ensure that the names
are consistent on all three sides. Otherwise, if NE names on the U2000 are changed
during reconstruction when the deployment list is imported, functions of these NodeBs
cannot be displayed on the U2000 topology.
Limitation on Transmission
1. If the GBTS uses TDM or HDLC transmission (TDM over E1 for GTMU or other
transmission), change the TDM over E1 transmission to IP over E1 or IP over FE.
Otherwise, co-MPT reconstruction is not supported.
2. Co-MPT reconstruction is not supported if a BSC pool is used and the transmission over
the Abis interface is used by different operators.
3. In the E1 backup scenario, if configuration data of the GBTS indicates that the primary
channel of the base station uses IP over E1 transmission and the secondary channel of
the base station uses IP over FE transmission, co-MPT reconstruction is not supported. If
the BTS IP address of the GBTS is non-logical, set the BTS IP address to the loopback
interface IP address which is logical and then performed co-MPT reconstruction using
the conversion tool. Otherwise, co-MPT reconstruction is not supported.
4. Co-MPT reconstruction is not supported if the networking changes during reconstruction
from a GBTS to an eGBTS. The networking may change from IP over E1 to IP over FE,
from IP over FE to IP over E1, from VLAN networking (in this scenario, the base station
carries VLAN information in packets) to non-VLAN networking, or from non-VLAN
networking to VLAN networking. In addition, the VLAN ID may change.
5. Co-MPT reconstruction is not supported if the configured and actual Ethernet port is
inconsistent. For example, the IP address is configured on an electrical port but the cable
is connected to an optical port in actual use.

Copyright © Huawei
6. Co-MPT reconstruction is not supported if non-64 kbit/s timeslots have been monitored.
7. Co-MPT reconstruction is not supported if an ARP session has been configured.
8. If the GBTS uses IP over FE/GE transmission (FE port on the GTMU), the GTMUb
conversion board does not support IP over FE/GE after reconstruction. (If separate
transmission was used before reconstruction, intermediate transmission needs to be
adjusted.) Assume that a base station deployed with both UMTS and LTE which use
separate transmission supporting IP over FE needs to be reconstructed into a co-MPT
base station which uses co-transmission supporting port sharing and IP over FE, and the
base station has UMTS and LTE inclusive route relationship and preferentially matches
the route of the non-reference mode (this route complies with the longest matching
principle or has the highest priority under the same length). In this scenario, you need to
configure the VLAN and route of the non-reference mode and reference mode for
transmission device. Otherwise, the OMCH and co-MPT reconstruction fail.
9. Scenarios where IP addresses for GU and GL conflict are not considered for data
verification. If the IP addresses conflict, reconstruction fails.
10. If a BTS using IP over E1 transmission is configured with the monitor timeslot, the
monitor timeslot configuration cannot be automatically converted for the co-MPT base
stations. You need to manually add the configuration of monitor timeslot after the
reconstruction.
11. When reconstructing base stations using DHCP servers, you are advised to reconstruct
base stations configured on the same port of the base station controller at the same batch.
If one base station is not reconstructed together with other base stations, the base station
will obtain incorrect IP configuration data when it goes through the DHCP server-based
deployment procedure after a reset. As a result, the base station fails to start.
12. Co-MPT reconstruction restrictions on co-transmission are as follows:
a. In the scenario where a GU base station uses co-IP transmission, the internal IP
address on the GSM side is on the same network segment as the default local IP
address. As a result, the generated data fails the verification. In addition, the tool for
converting the GBTS data to eGBTS data cannot identify such a scenario, and
therefore the tool used for co-MPT reconstruction from a separate-MPT GU base
station to a co-MPT GU base station does not support this scenario.
b. Scenarios where BBUs are interconnected through two front panels are not
supported. If a GTMU is to be abandoned, BBU interconnection through either one
or two front panels is not supported. If co-transmission through panel
interconnection in one BBU is deployed before co-MPT reconstruction, the
interconnection cables must be reserved. The cables must be connected to ports 0
and 1 on the UMPTe in the same way as the UMPTa or UMPTb. Data can be
converted only if the cables are connected to ports 0 and 1.
c. E1/T1 co-transmission is not supported. Reconstruction from E1/T1 separate
transmission to E1/T1 co-transmission is not supported.
d. If co-transmission is applied before and after reconstruction, scenarios where the
cascaded main control board transfer data to other boards as well as the cascading
board are not supported.
e. Reconstruction from Ethernet trunk separate transmission to Ethernet trunk co-
transmission is not supported.
f. Co-MPT reconstruction is performed in UTRPc-based co-transmission scenarios
when GSM is involved in reconstruction. When a separate-MPT UL base station
uses UTRPc-based co-transmission, only the reference mode provides transmission
ports during reconstruction.
g. In the case of co-transmission through a backplane, the two ports of the board that
provides a co-transmission port are configured with device IP addresses. Therefore,

Copyright © Huawei
it is difficult to determine which port is the co-transmission port and co-MPT

reconstruction is not supported in this scenario.
h. Multiple tunnels are configured, and it is difficult to determine the slot number of
the board that provides the transmission port. Therefore, co-MPT reconstruction is
not supported in this scenario.
13. Co-MPT reconstruction restrictions on security are as follows:
− For a separate-MPT multimode base station to be reconstructed, if security objects
are set for both the reference mode and non-reference modes, only security objects
for the reference mode are reserved after co-MPT reconstruction.
− If a separate-MPT multimode base station is to be reconstructed, only the digital
certificate for the reference mode is supported. Security objects of non-reference
modes cannot reference digital certificates. In the GSM configuration data, the
following items are not supported: digital certificates, IPsec, PACKETFILTER,
PINGFILTER, IPGUARD, or DOT1X (802.1x-based authentication).
− Co-MPT reconstruction from a separate-MPT multimode base station is not
supported if the following conditions are met:
− A UTRPc is configured to transmit data for the reference mode.
− IPsec is configured for the non-reference modes but not the reference mode.
− An operator's certificate is used for SSL.
14. Co-MPT reconstruction from a separate-MPT multimode base station is not supported if
both Ethernet and Ethernet trunk are used.
LTE is not the reference mode and the two ports of the LMPT are used as optical or
electrical ports.
PA of the main control board of a non-reference mode is set to AUTO(Automatic
Detection) because whether the Ethernet port is an optical or electrical port is not clear.
You can query the value of PA using the LST ETHPORT command. In addition, Co-
MPT reconstruction from an LO base station is not supported if PA of the LMPT board
is set to AUTO(Automatic Detection).
17. If the E1/T1 ports on one board will work in two bearing modes, such as IP and ATM
bearing modes after reconstruction, co-MPT reconstruction is not supported.
18. Co-MPT reconstruction is not supported if conflicts in the VLANMAP MO exist (the
values of Next Hop IP are the same or the subnet of a base station contains that of
another) and the values of VLAN Group No. are different.
19. Co-MPT reconstruction is not supported if boards working in active/standby mode are
configured on multiple separate-MPT multimode base stations.
20. In scenarios where a separate-MPT multimode base station is to be reconstructed, only
one type of route, source route or destination route, must be used for both the reference
and non-reference modes. Otherwise, co-MPT reconstruction is not supported.
21. The transmission port cannot be specified during reconstruction but can be specified
during transmission reconfiguration after reconstruction.
22. After the reconstruction, multiple next hop IP addresses, instead of one next hop IP
address, are used for the BTS maintenance plane, controller plane, and service plane.
Specifically, for the original GBTS, only one next hop IP address is used. If multiple
next hop IP addresses are required after the reconstruction, this configuration is not
supported by the tool. In this case, configure the route data after the reconstruction. The
following describes how to manually configure the route:

Copyright © Huawei
− If the next hop IP address of the BTS maintenance plane after the reconstruction is
different from the original next hop IP address, delete the original route to the IP
address of the U2000, and then run the ADD IPRT command to add a new route
and configure the actual next hop IP address.
− If the next hop IP address of the BTS control plane after the reconstruction is
different from the original next hop IP address, configure the route and next hop IP
address in the same way.
Note that the new next hop IP address planned for the BTS maintenance or control plane
must fall in the same network segment as the IP address of the Ethernet port configured
in the BTS parameter DEVIP. If they fall in different network segments, plan the IP
addresses of new BTS ports by running the ADD DEVIP command.
23. If a board is added or replaced due to reconstruction, a UMPT is used as the main control
board after reconstruction and the original main control board uses optical ports, run the
DSP ETHPORT command to query the data rate over the port before replacing the
board. This ensures that the data rate at the local end is the same as that at the peer end.
If the data rates are different, optical port negotiation fails and transmission is
interrupted.
Table 1.1 Port numbers before and after data conversion

Before conversion After conversion
GTMU:IPoE1 GTMU:IPoE1
GTMU:IPoFE/IPoGE:Port 0 UMPT:IPoFE/IPoGE: Port 0
GTMU:IPoFE/IPoGE: Port 1 UMPT:IPoFE/IPoGE: Port 1
WMPT:ATM/IPoE1 UMPT:ATM/IPoE1
WMPT: IPoFE/IPoGE: Port 0 UMPT:IPoFE/IPoGE: Port 0
WMPT: IPoFE/IPoGE: Port 1 UMPT:IPoFE/IPoGE: Port 1
LMPT:IPoFE/IPoGE: electrical port 0 UMPT:IPoFE/IPoGE: port 0
LMPT:IPoFE/IPoGE: electrical port 1 UMPT:IPoFE/IPoGE: port 0
LMPT:IPoFE/IPoGE: optical port 0 UMPT:IPoFE/IPoGE: port 1
LMPT:IPoFE/IPoGE: optical port 1 UMPT:IPoFE/IPoGE: port 1
Limitation on Clock
Co-MPT reconstruction is not supported in the following scenarios:
1. The reference clock planned by the customer is not included in the configuration data of
existing base stations.
2. The reference clock planned by the customer supports only frequency synchronization,
but time synchronization is used for the configuration data of existing base stations. In
this case, it is recommended that the planned reference clock be adjusted to correct the
planned data before co-MPT reconstruction.
3. The reference clock planned by the customer does not support TOD clock cascading, but
TOD clock cascading data is included in the configuration data of existing base stations.

Copyright © Huawei
In this case, it is recommended that the reference clock be changed to a TOD clock to
correct the planned data or you run the RMV TOD command to modify the
configuration data of existing base stations.
4. The reference clock planned by the customer does not support synchronous Ethernet
clock cascading, but synchronous Ethernet clock cascading data is included in the
configuration data of existing base stations. In this case, it is recommended that the
reference clock be changed to a synchronous Ethernet clock to correct the planned data
or you run the RMV SYNCETH command to modify the configuration data of existing
base stations.
5. If a GBTS is to be reconstructed to a eGBTS and the BSC has been configured with the
NTP server, the tool does not support the reconstruction when the NTP uses encrypted
authentication. In this case, re-configure the encryption information after the BTS starts
upon the configuration activation.
Limitation on Co-MPT Reconstruction in Independent RAT Upgrade Scenarios

Co-MPT reconstruction when a RAT is upgraded separately is supported from SRAN10.1.
Specifically, each RAT bound to multimode base stations before reconstruction runs different
versions, and the mapping relationships between each mode satisfy the software whitelist
requirements. The multimode base stations can be directly reconstructed as a co-MPT base
station. In the co-MPT base station after reconstruction, each RAT retains the original version,
and the node runs the latest version. Such a co-MPT reconstruction has the following
limitations:
1. The GBTS must run a version no later than that of NodeB and eNodeB, and the mapping
relationships between these three base stations satisfy the software whitelist
requirements.
2. Only the standalone CME supports co-MPT reconstruction when a RAT is upgraded
separately. The online CME does not support such a reconstruction.
3. When the independent RAT upgrade function is supported, the software whitelist
contains the mapping relationships about V/R/C/SPC versions. Therefore, such a co-
MPT reconstruction is supported when RATs differ in the SPC version, instead of the
SPH version.
4. Base station software supports a disguised version. However, the name of the base
station conversion component released at the support website must have a true version. If
the name have a disguised version, unpredictable exceptions may occur during co-MPT
reconstruction when a RAT is upgraded separately.
5. If the reconstruction is performed in batches, the base stations with the same RAT must
have the RAT running the same version. If base stations with the same RAT have the
RAT running different version, they must be classified into different batches for
reconstruction.
13.6 Description about Co-MPT Data Conversion

Background
This tool is used for converting the configuration data for separate-MPT multimode base
stations, BTSs, NodeBs, and eNodeBs to that for co-MPT multimode base stations.
Reconstructing separate-MPT multimode base stations, BTSs, NodeBs, and eNodeBs to co-
MPT multimode base stations requires complex data reconfigurations. This tool is used to
simplify the data reconfigurations.

Copyright © Huawei
Hardware Requirements for PCs

X86 PC or notebook computer
CPU frequency ≥ 2.4 GHz
Memory ≥ 4 GB
Available space on the hard disk ≥ 8 GB
Software Requirements for PCs

Operating system: Windows 7 Professional SP1
Microsoft Office Excel 2003 or later
Both Chinese and English OSs are supported.
Requirements for Base Stations to Be Reconstructed

 The GBTSs involved in a reconstruction must belong to one BSC.
 A maximum of 50 base stations can be reconstructed at a time, and therefore do not enter
data for more than 50 base stations in the reconstruction data planning file.
13.6.1 Application Scenarios and Restrictions of the MBSC

Reconstruction Module
By default, an MBSC reconstruction module supports verification of configuration data
before reconstruction. If the verification results show that the configuration data does not
support the reconstruction, related information will be displayed to inform users of modifying
the configuration data. In addition, if the tool does not support the verification, query the
configuration data to determine whether to perform manual verification.
Scenarios Where Tool-Based Verification Is Supported

1. If License Share in BBU Carrier Pool is set to YES(Yes), run the MOD BTS
command to change the setting.
2. If Cell Extension Type is set DualTS_ExtCell, run the MOD GCELL command to
change the setting.
3. If Support BTS Local Switch is set to YES(Yes), run the SET BTSLSW command to
change the setting.
4. If Transmission Mode is set to TER_AND_SAT_TRANS(Terrestrial and Satellite)
or PICO_AND_SAT_TRANS(Pico and Satellite), run the SET BTSTRANS
command to change the setting.
5. If NCH Occupy Block Number is set to a value other than 0, run the SET
GCELLGSMR command to change the setting.
6. If ICB Allowed is set to YES(YES) or NULL(NULL), run the SET
GCELLBASICPARA command to change the setting.
7. If Dynamic Transmission Div Supported is set to DDIVERSITY(DDIVERSITY) or
DPBT(DPBT), run the SET GCELLCHMGBASIC command to change the setting.
8. If EGPRS2-A is set to YES(YES), run the SET GCELLGPRS command to change the
setting.

Copyright © Huawei
9. If Support Reduced Latency Capability is set to SUPPORT(Support), run the SET

GCELLGPRS command to change the setting.
10. If Support Downlink Dual-Carrier is set to SUPPORT(Support), run the SET
GCELLGPRS command to change the setting.
11. If Move Immediate Assignment Down to BTS is set to YES(Support), run the SET
GCELLPSOTHERPARA command to change the setting.
12. If Move Packet Assignment Down to BTS is set to YES(Support), run the SET
GCELLPSOTHERPARA command to change the setting.
Scenarios Where Manual Verification Is Required

None
13.6.2 Application Scenarios and Restrictions of the GBTS

By default, a GBTS reconstruction module supports verification of configuration data before
reconstruction. If the verification results show that the configuration data does not support the
reconstruction, related information will be displayed to inform users of modifying the
configuration data. In addition, if the tool does not support the verification, query the

1. Convert the data of activated base station, cells and carriers only.

1. In the Ethernet OAM CC scenario, after the BTS is reconstructed into an eGBTS, run the
ACT CFMCC command to perform corresponding activation and check.
2. Before the reconstruction, Ethernet OAM 802.1ag is configured for the GBTS, and the
MAC-based RMEP is configured for the equipment interconnected to the GBTS: After
the reconstruction, Ethernet ports for interconnection are configured for the UMPT
instead of the GTMU. Therefore, in the given scenario, after the reconstruction, the data
configuration of the equipment interconnected to the GBTS needs to be changed to
ensure that the configured MAC address is the MAC address of the Ethernet port on the
UMPT.
3. After a GBTS is changed to an eGBTS, if the NTP protocol is required for the clock
synchronization, the reconstruction tool will by default use the NTP server used by the
BSC as the NTP server for the eGBTS. Therefore, the route from the NTP server to the
eGBTS must exist. Otherwise, you need to add one. If another NTP server is required by
the eGBTS after reconstruction, a new NTP address must be configured.
13.6.3 Application Scenarios and Restrictions of the SRAN

By default, an SRAN reconstruction module supports verification of configuration data before
reconstruction. If the verification results show that the configuration data does not support the
reconstruction, related information will be displayed to inform users of modifying the
configuration data. In addition, if the tool does not support the verification, query the

Copyright © Huawei

1. CTRLLNK: The scenario where no control link is configured for both main control
boards when inter-BBU separate-MPT is used for a dual-mode base station is not
supported. In addition, a control link can be added by running the ADD CTRLLNK
command.
2. The dual-star topology of RF modules in a BBU will be automatically changed to the
load-sharing networking.
3. If both the primary and secondary modes have the same chain number under
RRUCHAIN, reassign a chain number to the secondary mode, that is, using the
maximum value among available values.
4. If ALDs of both modes have the same device number, reassign a device number to the
secondary mode, that is, using the minimum value among available values.
5. If the SRAN name after the reconstruction is not included in the reconstruction planning
file, the NE name of the primary mode will be used by default. However, the
reconstruction is not supported if the SRAN name is excluded and the NE name is blank.
In this case, the NE name can be configured by running the SET NENAME command.
6. For ALDs of the primary and secondary modes, the vendor code, serial number, and
device name cannot be the same value except the value of null.
7. If two sectors with different modes share the same antenna before the reconstruction,
combine the two sectors into one, using the parameters of the primary mode
preferentially, such as the sector number and sector name.
8. If two baseband devices with different modes share the same baseband processing units
before the reconstruction, combine the two devices into one, using the parameters of the
primary mode preferentially.
9. If DEVIP and ETHTRK are configured for the Ethernet, the configurations of the
primary mode will be used.
10. The OMCH configurations of the UMTS or LTE mode will be used to ensure the OMCH
connectivity in the scenario in GU or GL reconstruction scenarios.
11. For E1 backup, the network segments of the routes for the OMCH cannot overlap with
those of the routes for the user plane and data plane. If a route of the LTE mode can
reach U2000 as well as MME or SGW, users need to split this route into multiple routes.
The network segment of the destination IP address of the route to the U2000 cannot
contain the network segment of the route to the MME or SGW. For details about the
configurations, see Abis Transmission Backup. (You can obtain this document from
GBSS Feature Documentation on Hedex. On the GBSS Feature Documentation web
page, choose Description > Reliability > Abis Transmission Backup from the
navigation tree.). The OMCH configurations will not be combined. The configurations
related to E1 backup in UDPSESSION and GTRANSPARA will be combined.
12. For RRUs serving one GSM cell and two UMTS/LTE sectors, configure the RRU for
one UMTS/LTE sector before the combination.

1. If multiple default routes for the IPRT exist, the default route of the primary mode will
be used. Users need to analyze the impact and solve the issue.
2. The QoS-related configurations of the primary mode will be used after the
reconstruction. As a result, the QoS of the secondary mode will be affected. After the
reconstruction, a warning will be generated. The warning indicates the configurations of
each mode before the reconstruction, and users need to determine whether the QoS-
related configurations (such as DIFPRI and DSCPMAP) need to be modified.

Copyright © Huawei
3. The tool cannot automatically convert interconnected sectors through two systems into
one sector in one system.
4. If the maintenance IP of GBTS is the same as 192.168 network segment, need to replan
IP address. Otherwise the maintenance IP of GBTS and default maintenance IP of
UMPT are in the same segment caused co-MPT reconstruction failed.
5. The rule for merging the transmission configuration data (the PACKETFILTER MO) is
as follows: all the PACKETFILTER MOs for baseline RAT and non-baseline RAT and
set the filter switch in the EPGROUP MO to disable. If users need packet filtering after
co-MPT reconstruction, the users manually configure the filter switch.
6. For a separate-MPT multimode base station, the co-MPT base station after
reconstruction applies IP over FE transmission using the same port if multiple modes are
configured with resource groups, the transmission port numbers of different modes are
the same, and the base station applies IP over FE. In this scenario, adjust the bandwidth
configuration of resource groups base on service types.
7. If a GBTS cell is configured with multiple RF modules, other modes must share the RF
modules in the same sector. Otherwise, the tool does not support the conversion.
13.7 Co-MPT Reconstruction Scenarios

Note:
1. The UMPT in co-MPT reconstruction scenarios described in this document includes
UMPTa, UMPTb, and UMPTe. The types of the UMPT are consistent before and after
reconstruction. For example, if the main control board of a separate-MPT base station is
UMPTb and the mode of this base station is used as the reference mode before
reconstruction, the main control board of the co-MPT base station after reconstruction
must also be UMPTb.
1. If the base station before reconstruction uses E1/T1 transmission (including E1/T1 over IP
or E1/T1 over ATM), the UMPTe cannot serve as the main control board for the co-MPT
base station after reconstruction because the UMPTe does not support E1/T1 transmission.
2. If the UMPTe serves as the main control board for the co-MPT base station after
reconstruction, the main control boards (including WMPT and LMPT) before
reconstruction are abandoned, and the main control board (UMPTa/b) before
2. From SRAN11.1 onwards, hybrid-MPT base stations can be reconstructed. That is, the
co-MPT base station and separate-MPT base station can be reconstructed into a new co-
MPT base station. This type of reconstruction has the following constraints:
− The separate-MPT base station and co-MPT base station before reconstruction
cannot have the same NE types. For example, in the case of G[G*U]->[G*U], G
indicates the separate-MPT base station and G*U the co-MPT base station before
reconstruction.
− The reference mode must be the mode deployed on the co-MPT base station instead
of the separate-MPT base station.

Copyright © Huawei
− The following reconstruction scenarios are not supported: Two or more co-MPT
base stations are involved before reconstruction; The co-MPT base station to be
reconstructed is an eGBTS.
3. In SRAN11.0 and earlier versions, the GTMUc supports only the legacy scenarios and
does not support SingleOM co-MPT or evolution mode. Therefore, the GTMUc serves
as a GTMUa during the reconstruction. In SRAN11.1 and later versions, the GTMUc
supports SingleOM and evolution modes. Therefore, the GTMUc serves as a GTMUb
during the reconstruction.
13.7.1 GSM Co-MPT Reconstruction Scenario

Sce Before After Reconstruction Board and Cable Connection Adjustment
nari Reconstruction Before and After Reconstruction
o
No. Main Trans Main Trans
Contro missi Control missio
l on Board n
Board
1 GTM IPoE GTMUb IPoE1
Ub 1 (evolved)
+UMPT_G
2 GTM IPoF GTMUb IPoFE
Ub E (evolved)
+UMPT_G
3 GTM E1 GTMUb E1
Ub back (evolved) backup
up +UMPT_G
4 GTM IPoE GTMU IPoE1

Ua/b 1 (abandone
d)
+UMPT_G
5 GTM IPoF GTMU IPoFE
Ua/b E (abandone
d)
+UMPT_G
6 GTM E1 GTMUb E1
Ua/b back (abandone backup
up d)
+UMPT_G
13.7.2 UMTS Co-MPT Reconstruction Scenario

Sce Before After Board and Cable Connection
nari Reconstruction Reconstruction Adjustment Before and After
o Reconstruction
Contr missio Control missio
ol

Copyright © Huawei
Board n Board n
1 WMP IPoFE/ UMPT_U IPoFE/
T IPoE1/ IPoE1/
ATM/ ATM/
ATM ATM
&IPoF &IPoF
E E
2 UMPT IPoFE/ UMPT_U IPoFE/
_U IPoE1/ IPoE1/
ATM/ ATM/
ATM ATM
&IPoF &IPoF
E E
13.7.3 LTE Co-MPT Reconstruction Scenario

o Reconstruction
Contr missio Control missio
ol n Board n
Board
1 LMPT IPoFE UMPT_L IPoFE
2 UMPT IPoFE UMPT_L IPoFE

_L
13.7.4 GSM and UMTS Co-MPT Reconstruction Scenario

o Reconstruction
No. Main GS UM Main GS UM
Contr M TS Contr M TS Note 1
ol Tra Tran ol Tra Tran
Board nsm smis Board nsm smiss
issio sion issi ion
n on
1 GTM IPo IPoE GTM IPo IPoE
Ub+W E1 1/IPo Ub E1 1/IPo
MPT/ FE/A (evolv FE/A
UMP TM/ ed) TM/
T_U ATM +UMP ATM
&IPo T_GU &IPo

Copyright © Huawei
FE FE
2 GTM IPo IPoE GTM IPo IPoE 1. If separate transmission is
Ub+W FE 1/IPo Ub FE 1/IPo adopted for GSM and UMTS
MPT/ FE/A (evolv FE/A before the reconstruction, this
UMP TM/ ed) TM/ transmission mode will still be
T_U ATM +UMP ATM adopted after the reconstruction.
&IPo T_GU &IPo
FE FE
2. If co-transmission is adopted for

GSM and UMTS before the
reconstruction, this transmission
mode will still be adopted after the
reconstruction.
3 GTM IPo IPoE GTM IPo IPoE 1. The WBBP already exists and a
Ua/b+ E1 1/IPo Ua/b E1 1/IPo UBRI is added to provide CPRI
WMP FE (aband FE ports for the GSM mode.
T/UM oned)
PT_U +UMP
T_GU
2. The UBBP already exists and is
used to provide CPRI ports for the
GSM mode.
4 GTM IPo IPoF GTM IPo IPoF 1. The WBBP already exists and a
Ua/b+ FE E/IP Ua/b FE E/IPo UBRI is added to provide CPRI
WMP oE1/ (aband E1/A port for the GSM mode (including
T/UM ATM oned) TM/ separate transmission and co-
PT_U /AT +UMP ATM transmission).
M&I T_GU &IPo
PoFE FE
2. The UBBP already exists and is

used to provide CPRI ports for the
GSM mode (including separate
transmission and co-transmission).

Copyright © Huawei
5 GTM IPo IPoE GTM IPo IPoE Hybird-MPT reconstruction

Ub+ E1 1/IPo Ub E1 1/IPo scenario:
UMP FE/G (evolv FE/G G&[U]->[G*U]
T_U E/AT ed) E/AT
Note: M/A +UMP M/A
U is a TM T_GU TM&
co- &IPo IPoF
MPT FE/G E/GE
base E
station
.
Ub+ FE/ 1/IPo Ub FE/ 1/IPo scenario:
UMP GE FE/G (evolv GE FE/G G&[U]->[G*U]
T_U E/AT ed) E/AT
Note: M/A +UMP M/A
U is a TM T_GU TM&
co- &IPo IPoF
MPT FE/G E/GE
base E
station
.
Ua/b+ E1 1/IPo Ua/b E1 1/IPo scenario:
UMP FE/G (aband FE/G G&[U]->[G*U]
T_U E oned) E
Note: +UMP
U is a T_GU
co-
MPT
base
station
.
8 GTM IPo IPoF GTM IPo IPoF Hybird-MPT reconstruction
Ua/b+ FE/ E/GE Ua/b E1 E/GE scenario:
UMP GE /IPo (aband /IPoE G&[U]->[G*U]
T_U E1/A oned) 1/AT
Note: TM/ +UMP M/A
U is a ATM T_GU TM&
co- &IPo IPoF
MPT FE/G E/GE
base E
station
.

Copyright © Huawei
Note 1: Assume that GSM and UMTS use IP over FE transmission and separate transmission
before reconstruction. If GSM and UMTS data are transmitted from Ethernet ports of
different numbers on different boards before reconstruction, the GSM and UMTS data will be
transmitted from different Ethernet ports after reconstruction; if GSM and UMTS data are
transmitted from Ethernet ports of the same number on different boards before reconstruction,
the GSM and UMTS data will be transmitted from the same Ethernet port after reconstruction.
13.7.5 GSM and LTE Co-MPT Reconstruction Scenario

o Reconstruction (Note 1)
No. Main GS LT Main GS LT
Cont M E Contr M E
rol Tra Tra ol Tra Tra
Boar nsm nsm Board nsm nsm
d issio issi issio issi
n on n on
1 GTM IPoE IPo GTMU IPoE IPo 1. The GSM transmission uses IP
Ub+L 1/ FE b 1/ FE over E1 transmission.
MPT/ E1 (evolve E1
UMP back d) back
T_L up +UMP up
T_GL
2. The GSM transmission uses E1
backup transmission.
2 GTM IPoF IPo GTMU IPoF IPo 1. If GSM and LTE use separate
Ub+L E FE b E FE transmission before the
MPT/ (evolve reconstruction, separate
UMP d) transmission will still be adopted
T_L +UMP after the reconstruction.
T_GL 2. If GSM and LTE use co-
transmission before the
reconstruction, co-transmission will
still be adopted after the
reconstruction.
3 GTM IPoE IPo GTMU IPoE IPo 1. The GSM transmission uses IP
Ua/b 1/ FE a/b 1/ FE over E1 transmission.
+LM E1 (aband E1 The baseband processing board of
PT/U back oned) back LTE is LBBP.
MPT up +UMP up
_L T_GL
The baseband processing board of

LTE is UBBP.

Copyright © Huawei
2. The GSM transmission uses E1

LTE is LBBP.

LTE is UBBP.
4 GTM IPoF IPo GTMU IPoF IPo 1. The baseband processing board of
Ua/b E FE a/b E FE LTE is LBBP.
+LM (aband If separate transmission is adopted
PT/U oned) for GSM and LTE before the
MPT +UMP reconstruction, it will still be
_L T_GL adopted after the reconstruction.
If co-transmission is adopted for

GSM and LTE before the
reconstruction, it will still be
adopted after the reconstruction.
2. The baseband processing board of

LTE is UBBP.
If separate transmission is adopted
for GSM and LTE before the
If co-transmission is adopted for

GSM and LTE before the
5 GTM IPoE IPo GTMU IPoE IPo Hybird-MPT reconstruction

Ub+ 1/ FE/ b 1/ FE/ scenario:

Copyright © Huawei
UMP E1 GE (evolve E1 GE G&[L]->[G*L]

T_L back d) back
Note: up +UMP up
L is a T_GL
co-
MPT
base
statio
n.
6 GTM IPoF IPo GTMU IPoF IPo Hybird-MPT reconstruction
Ub+ E/G FE/ b E/G FE/ scenario:
UMP E GE (evolve E GE G&[L]->[G*L]
T_L d)
Note: +UMP
L is a T_GL
co-
MPT
base
statio
n.
7 GTM IPoE IPo GTMU IPoE IPo Hybird-MPT reconstruction
Ua/b 1/ FE/ a/b 1/ FE/ scenario:
+UM E1 GE (aband E1 GE G&[L]->[G*L]
PT_L back oned) back
Note: up +UMP up
L is a T_GL
co-
MPT
base
statio
n.
8 GTM IPoF IPo GTMU IPoF IPo Hybird-MPT reconstruction

Ua/b E/G FE/ a/b E/G FE/ scenario:
+UM E GE (aband E GE G&[L]->[G*L]
PT_L oned)
Note: +UMP
L is a T_GL
co-
MPT
base
statio
n.

Copyright © Huawei
Note 1: Assume that GSM and LTE use IP over FE transmission and separate transmission
before reconstruction. If GSM and LTE data are transmitted from Ethernet ports of different
numbers on different boards before reconstruction, the GSM and LTE data will be transmitted
from different Ethernet ports after reconstruction; if GSM and LTE data are transmitted from
Ethernet ports of the same number on different boards before reconstruction, the GSM and
LTE data will be transmitted from the same Ethernet port after reconstruction.
13.7.6 UMTS and LTE Co-MPT Reconstruction Scenario

Sce Before After Reconstruction Board and Cable Connection
nari Reconstruction Adjustment Before and After
o Reconstruction (Note 1)
No. Main UMT LTE Main UMT LTE
Contr S Tra Cont S Tra
ol Tran nsm rol Trans nsm
Board smiss issio Boar missio issio
ion n d n n
1 WMP IPoE IPoF UMP IPoE1 IPoF UMTS is the reference mode.
T/UM 1/IPo E T_U /IPoF E
PT_U FE/A L+L E/AT
+LMP TM/ MPT M/AT
T/UM ATM (evol M&IP LTE is the reference mode.
PT_L &IPo ved) oFE
FE Or
WMP
T (in-
positi
on
but
not
used)
+UM
PT_U
L

Copyright © Huawei
2 UMP IPoE IPoF UMP IPoE1 IPoF UMTS is the reference mode.
T_U+ 1/IPo E T_U /IPoF E
UMP FE/A L+U E/AT
T_L TM/ MPT M/AT
ATM _UL M&IP LTE is the reference mode.
&IPo Note oFE
FE 2
3 UMP IPoE IPoF UMP IPoE1 IPoF Hybird-MPT reconstruction

T_U+ 1/IPo E/G T_U /IPoF E/G scenario:
LMPT FE/G E L+L E/GE/ E U&[L]->[U*L] and L&[U]-
or E/AT MPT ATM/ >[U*L]
WMP M/A (evol ATM
T+U TM& ved) &IPoF
MPT_ IPoF or E/GE
L E/GE UMP
Note: T_U
U with L+W
a MPT
UMP (evol
T_U ved)
and L
with a
UMP
T_L
are
both
co-
MPT
base
station
s.
4 UMP IPoE IPoF UMP IPoE1 IPoF Hybird-MPT reconstruction
T_U+ 1/IPo E/G T_U /IPoF E/G scenario:
UMP FE/G E L+U E/GE/ E U&[L]->[U*L] and L&[U]-
T_L E/AT MPT ATM/ >[U*L]
Note: M/A _UL ATM
Either TM& &IPoF
U with IPoF E/GE
a E/GE
UMP
T_U
or L
with a
UMP
T_L is
a co-
MPT
base
station
.

Copyright © Huawei
Note 1: Assume that UMTS and LTE use IP over FE separate transmission before
reconstruction. If UMTS and LTE services are transmitted from Ethernet ports of different
numbers before reconstruction, the UMTS and LTE services will be transmitted still from
different Ethernet ports after reconstruction; if UMTS and LTE services are transmitted from
Ethernet ports of the same number before reconstruction, the UMTS and LTE services will be
transmitted from the same Ethernet port after reconstruction.
Note 2: If the main control boards of UMTS and LTE are both UMPT of the same type before
reconstruction, the two UMPTs can work in active/standby mode after the UMTS and LTE
co-MPT reconstruction. If the two UMPTs are of different types, they cannot work in
active/standby mode, and then the UMPT with lower specifications will be abandoned.
13.7.7 G&[U*L] or U&[G*L]/L&[G*U] Reconstruction Scenario

Sce Before Reconstruction After Reconstruction Board and Cable
nari Connection Adjustment
o Mai GS UM LTE Mai GS UM LT Before and After
No. n M TS Tra n M TS E Reconstruction
Cont Tra Tra nsm Con Tra Tra Tra
rol nsm nsm issio trol nsm nsm nsm
Boar issi issi n Boa issi issi issi
d on on rd on on on
1 GT IPo IPo IPo GT IPo IPo IPo Hybird-MPT
MU E1/ E1/I FE/ MU E1/ E1/I FE/ reconstruction scenario:
b E1 PoF GE b E1 PoF GE G&[U*L]->[G*U*L]
+U bac E/G (evo bac E/G
MP kup E/A lved kup E/A
T_U TM/ ) TM/
L AT +U AT
M& MP M&
IPo T_ IPo
FE/ GU FE/
GE L GE
MU FE/ E1/I FE/ MU FE/ E1/I FE/ reconstruction scenario:
b GE PoF GE b GE PoF GE G&[U*L]->[G*U*L]
+U E/G (evo E/G
MP E/A lved E/A
T_U TM/ ) TM/
L AT +U AT
M& MP M&
IPo T_ IPo
FE/ GU FE/
GE L GE
MU E1/ E1/I FE/ MU E1/ E1/I FE/ reconstruction scenario:
a/b E1 PoF GE a/G E1 PoF GE G&[U*L]->[G*U*L]
+U bac E/G TM bac E/G
MP kup E/A Ub kup E/A
T_U TM/ (aba TM/
L AT ndo AT
M& ned) M&

Copyright © Huawei
IPo +U IPo
FE/ MP FE/
GE T_ GE
GU
L

MU FE/ E1/I FE/ MU FE/ E1/I FE/ reconstruction scenario:
a/b GE PoF GE a/G GE PoF GE G&[U*L]->[G*U*L]
+U E/G TM E/G
MP E/A Ub E/A
T_U TM/ (aba TM/
L AT ndo AT
M& ned) M&
IPo +U IPo
FE/ MP FE/
GE T_ GE
GU
L
5 WM IPo IPo IPo W IPo IPo IPo Hybird-MPT

PT+ E1/I E1/I FE/ MP E1/I E1/I FE/ reconstruction scenario:
UM PoF PoF GE T PoF PoF GE U&[G*L]->[G*U*L]
PT_ E/G E/G (in- E/G E/G
GL E E/A posi E E/A
TM/ tion TM/
AT but AT
M& not M&
IPo use IPo
FE/ d) FE/
GE +U GE
MP
T_
GU
L
6 UM IPo IPo IPo UM IPo IPo IPo Hybird-MPT
PT_ E1/I E1/I FE/ PT_ E1/I E1/I FE/ reconstruction scenario:
U+ PoF PoF GE GU PoF PoF GE U&[G*L]->[G*U*L]
UM E/G E/G L+ E/G E/G
PT_ E E/A UM E E/A
GL TM/ PT_ TM/
AT GU AT
M& L M&
IPo IPo
FE/ FE/
GE GE
7 LM IPo IPo IPo LM IPo IPo IPo Hybird-MPT
PT+ E1/I E1/I FE/ PT E1/I E1/I FE/ reconstruction scenario:
UM PoF PoF GE (evo PoF PoF GE L&[G*U]->[G*U*L]
PT_ E/G E/G lved E/G E/G
GU E E/A ) E E/A
TM/ +U TM/
AT MP AT

Copyright © Huawei
M& T_ M&
IPo GU IPo
FE/ L FE/
GE GE
8 UM IPo IPo IPo UM IPo IPo IPo Hybird-MPT

PT_ E1/I E1/I FE/ PT_ E1/I E1/I FE/ reconstruction scenario:
L+U PoF PoF GE GU PoF PoF GE L&[G*U]->[G*U*L]
MP E/G E/G L+ E/G E/G
T_G E E/A UM E E/A
U TM/ PT_ TM/
AT GU AT
M& L M&
IPo IPo
FE/ FE/
GE GE
Note 1: Assume that UMTS and LTE use IP over FE separate transmission before
reconstruction. If UMTS and LTE services are transmitted from Ethernet ports of different
numbers before reconstruction, the UMTS and LTE services will be transmitted still from
different Ethernet ports after reconstruction; if UMTS and LTE services are transmitted from
Ethernet ports of the same number before reconstruction, the UMTS and LTE services will be
transmitted from the same Ethernet port after reconstruction.
Note 2: If the main control boards of UMTS and LTE are both UMPT of the same type before
reconstruction, the two UMPTs can work in active/standby mode after the UMTS and LTE
co-MPT reconstruction. If the two UMPTs are of different types, they cannot work in
active/standby mode, and then the UMPT with lower specifications will be abandoned.
13.7.8 GU+L Co-MPT Reconstruction Scenario

o Mai GS UM LT Mai GS UM LT Before and After
No. n M TS E n M TS E Reconstruction
Con Tra Tra Tra Con Tra Tra Tra
trol nsm nsm nsm trol nsm nsm nsm
Boa issi issi issio Boa issi issi issi
rd on on n rd on on on
Mo
de
1 GT IPo IPo IPo GT IPo IPo IPo The UCIU-based BBU
MU E1 E1/I FE MU E1 FE FE interconnection and
b+ PoF b UMPT-based BBU
WM E/A (evo interconnection are

Copyright © Huawei
PT/ TM/ lved included.

UM AT )
PT_ M& +U
U IPo MP
UM FE T_
PT_ GU
L L
UM
PT_
GU
L
2 GT IPo IPo IPo GT IPo IPo IPo 1. If separate transmission
MU FE E1/I FE MU FE FE FE is adopted for GSM,
b+ PoF b UMTS, and LTE before
WM E/A (evo the reconstruction, it will
PT/ TM/ lved still be adopted after the
UM AT ) reconstruction no matter
PT_ M& +U whether UCIU-based BBU
U IPo MP interconnection or UMPT-
UM FE T_ based BBU interconnection
PT_ GU is used.
L L
UM
PT_
GU
L
2. If the UMPT_L in BBU

1 provides co-transmission
ports for GSM, UMTS, and
LTE before the
reconstruction, the
UMPT_GUL in BBU 0
provides transmission ports
for GSM, UMTS, and LTE
after the reconstruction,
regardless of whether
BBUs are interconnected
through UCIUs or UMPTs.

Copyright © Huawei
3 GT IPo IPo IPo GT IPo IPo IPo The baseband processing

MU E1 E1/I FE MU E1 E1/I FE board of UMTS is WBBP.
a/b+ PoF a/G PoF The UCIU-based BBU
WM E TM E interconnection and
PT/ Ub UMPT-based BBU
UM (aba interconnection are
PT_ ndo included.
U ned)
UM +U
PT_ MP
L T_
GU
L
UM
PT_
GU The baseband processing
L board of UMTS is UBBP.
The UCIU-based BBU
interconnection and
UMPT-based BBU
interconnection are
included.
4 GT IPo IPo IPo GT IPo IPo IPo 1. The BBUs are

MU FE E1/I FE MU FE E1/I FE interconnected through
a/b+ PoF a/G PoF UCIUs.
UM E/A TM E/A The baseband processing
PT_ TM/ Ub TM/ board of UMTS is WBBP.
U AT (aba AT
UM M& ndo M&
PT_ IPo ned) IPo
L FE +U FE
MP The baseband processing
T_ board of UMTS is WBBP.
GU
L 2. The BBUs are
interconnected through
UM UMPTs.
PT_
GU The baseband processing
L board of UMTS is WBBP.

Copyright © Huawei
The baseband processing

board of UMTS is UBBP.
13.7.9 GL+U Co-MPT Reconstruction Scenario

Mo
de
1 GT IPo IPo IPo GT IPo IPo IPo 1. GSM uses IP over E1
MU E1/ FE/I FE MU E1/ FE/I FE transmission no matter
b+L E1 PoE b E1 PoE whether UCIU-based
MP bac 1/A (evo bac 1/A BBU interconnection or
T/U kup TM/ lved kup TM/ UMPT-based BBU
MP AT ) AT interconnection is used.
T_L M& +U M&
UM IPo MP IPo
PT_ FE T_ FE
U GU
L
UM
PT_
GU 2. GSM uses E1 backup
L transmission no matter
whether UCIU-based
BBU interconnection or
UMPT-based BBU
interconnection is used.
2 GT IPo IPo IPo GT IPo IPo IPo 1. If GSM, UMTS, and

Copyright © Huawei
MU FE FE/I FE MU FE FE/I FE LTE use separate

b+L PoE b PoE transmission before the
MP 1/A (evo 1/A reconstruction, this
T/U TM/ lved TM/ transmission mode will still
MP AT ) AT be adopted after the
T_L M& +U M& reconstruction no matter
UM IPo MP IPo whether UCIU-based BBU
PT_ FE T_ FE interconnection or UMPT-
U GU based BBU interconnection
L is used.
UM
PT_
GU
L

LTE before the
reconstruction, the
UMPT_GUL in BBU 0
provides transmission ports
for GSM, UMTS, and LTE
after the reconstruction,
regardless of whether
BBUs are interconnected
through UCIUs or UMPTs.
3. If the UMPT_U in BBU

LTE before the
reconstruction, the

Copyright © Huawei
UMPT_GUL in BBU 0
provides co-transmission
LTE after the
reconstruction, no matter
whether UCIU-based BBU
interconnection or UMPT-
based BBU interconnection
is used.
3 GT IPo IPo IPo GT IPo IPo IPo Note: If the main control
MU E1/ E1/I FE MU E1/ FE/ FE boards of both BBU 0 and
a/b+ E1 PoF a/G E1 AT BBU 1 are UMPTs before
LM bac E TM bac M/ the reconstruction, the two
PT/ kup Ub kup AT BBUs can be
UM (aba M& interconnected through
PT_ ndo IPo either UCIUs or UMPTs.
L ned) FE As shown in the following
UM +U figure, each sub-scenario
PT_ MP adopts one interconnection.
U T_ 1. The GSM mode uses IP
GU over E1 transmission.
L
UM board of LTE is LBBP.
PT_
GU
L

board of LTE is UBBP.

Copyright © Huawei
2. The GSM mode uses E1

board of LTE is LBBP.

board of LTE is UBBP.
4 GT IPo IPo IPo GT IPo IPo IPo Note: If the main control
MU FE E1/I FE MU FE FE/I FE boards of both BBU 0 and
a/b+ PoF a/G PoE BBU 1 are UMPTs before
LM E/A TM 1/A the reconstruction, the two
PT/ TM/ Ub TM/ BBUs can be
UM AT (aba AT interconnected through
PT_ M& ndo M& either UCIUs or UMPTs.
L IPo ned) IPo As shown in the following
UM FE +U FE figure, each sub-scenario
PT_ MP adopts one interconnection.
U T_ 1. If separate transmission
GU is adopted for GSM,
L UMTS, and LTE before the
UM reconstruction, it will still
PT_ be adopted after the
GU reconstruction (an added
L UBRI or a UBBP can be
used to carry CPRI cables
of GSM when the
GTMUa/GTMUb is to be
abandoned).

Copyright © Huawei

LTE before the
reconstruction, the
UMPT_GUL in BBU 0
LTE after the
reconstruction (an added
UBRI or a UBBP can be
of GSM when the
abandoned).
3. If the UMPT_U in BBU

LTE before the
reconstruction, the
UMPT_GUL in BBU 0
LTE after the
reconstruction (an added
UBRI or a UBBP can be
of GSM when the
abandoned).

Copyright © Huawei
13.7.10 G&[U*L]+[U*L] Reconstruction Scenario

1 GT IPo IPo IPo GT IPo IPo IPo Hybird-MPT reconstruction
MU E1/ FE/I FE MU E1/ FE/I FE scenario:
b+L E1 PoE b E1 PoE G&[U*L]+[U*L]-
MP bac 1/A (evo bac 1/A >[G*U*L]+[G*U*L]
T/U kup TM/ lved kup TM/
MP AT ) AT
T_L M& +U M&
UM IPo MP IPo
PT_ FE T_ FE
U GU
L
UM
PT_
GU
L
2 BB IPo IPo IPo BB IPo IPo IPo Hybird-MPT reconstruction
U0: FE/ E1/I FE/ U0: FE/ E1/I FE/ scenario:
GT GE PoF GE GT GE PoF GE G&[U*L]+[U*L]-
MU E/G MU E/G >[G*U*L]+[G*U*L]
b+U E/A b E/A
MP TM/ (evo TM/
T_ AT lved AT
UL M& ) M&
BB IPo +U IPo
U1: FE/ MP FE/
UM GE T_ GE
PT_ GU
UL L
BB
U1:

Copyright © Huawei
UM
PT_
GU
L
U0: E1/ E1/I FE/ U0: E1/ E1/I FE/ scenario:
GT E1 PoF GE GT E1 PoF GE G&[U*L]+[U*L]-
MU bac E/G MU bac E/G >[G*U*L]+[G*U*L]
a/b+ kup E/A a/G kup E/A
UM TM/ TM TM/
PT_ AT Ub AT
UL M& (aba M&
BB IPo ndo IPo
U1: FE/ ned) FE/
UM GE +U GE
PT_ MP
UL T_
GU
L
BB
U1:
UM
PT_
GU
L
U0: FE/ E1/I FE/ U0: FE/ E1/I FE/ scenario:
GT GE PoF GE GT GE PoF GE G&[U*L]+[U*L]-
MU E/G MU E/G >[G*U*L]+[G*U*L]
a/b+ E/A a/G E/A
UM TM/ TM TM/
PT_ AT Ub AT
UL M& (aba M&
BB IPo ndo IPo
U1: FE/ ned) FE/
UM GE +U GE
PT_ MP
UL T_
GU
L
BB
U1:
UM
PT_
GU
L

Copyright © Huawei
13.7.11 Two BBUs Combined into One Co-MPT Reconstruction

Table 1.1
Scenario No. Main Control Board and Baseband Processing Board
Adjustment Before and After Reconstruction
G, UL -> G*U*L GTMUb evolution
GTMUa/GTMUb (abandoned)
GU, L -> G*U*L GTMUb evolution

Copyright © Huawei

Hybird-MPT reconstruction scenario:

GBTS, co-MPT NodeB, separate-MPT eNodeB->[G*U*L]
GBTS, separate-MPT NodeB, co-MPT eNodeB->[G*U*L]
GBTS, co-MPT base station [U*L] -> [G*U*L]
GL, U -> G*U*L GTMUb evolution

Copyright © Huawei

U, L -> U*L
G, U -> G*U GTMUb evolution
G, L -> G*L GTMUb evolution:

Copyright © Huawei

The following table describes the hybrid-MPT reconstruction scenarios.
Table 1.2 Hybrid-MPT reconstruction scenarios where two BBUs are combined into one BBU
Scenario BBU1 Before BBU2 Before BBUs Before
Reconstruction Reconstruction Reconstruction (Two
Combined into One)
G, UL -> GBTS Co-MPT NodeB, Co-MPT GUL base

G*U*L separate-MPT station
eNodeB
GBTS Separate-MPT Co-MPT GUL base
NodeB, co-MPT station
eNodeB
GBTS Co-MPT UL base Co-MPT GUL base
station station
GU, L -> GBTS, co-MPT Separate-MPT Co-MPT GUL base
G*U*L NodeB eNodeB station
GBTS, separate- Co-MPT eNodeB Co-MPT GUL base
MPT NodeB station
Co-MPT GU base Separate-MPT Co-MPT GUL base
station eNodeB station
GL, U -> GBTS, co-MPT Separate-MPT NodeB Co-MPT GUL base
G*U*L eNodeB station
GBTS, separate- Co-MPT NodeB Co-MPT GUL base
MPT eNodeB station
Co-MPT GL base Separate-MPT NodeB Co-MPT GUL base

Copyright © Huawei
Scenario BBU1 Before BBU2 Before BBUs Before

Reconstruction Reconstruction Reconstruction (Two
Combined into One)
station station
U, L -> U*L Co-MPT NodeB Separate-MPT Co-MPT UL base
eNodeB station
Separate-MPT Co-MPT eNodeB Co-MPT UL base
NodeB station
G, U -> G*U GBTS Co-MPT NodeB Co-MPT GU base
station
G, L -> G*L GBTS Co-MPT eNodeB Co-MPT GL base
station

Copyright © Huawei
3900 Series Multimode Base Station 14 Examples for Co-MPT Reconstruction and Mode
Mode Transition Guide(For NB) Transition
14 Examples for Co-MPT Reconstruction

and Mode Transition
Examples for Co-MPT Reconstruction and Mode Transition

Delivery Key Points for FDD and TDD Convergence Networking
FDD and TDD Co-MPT Base Station Deployment

Copyright © Huawei

SR@N12.0 Mode - Transition - Guide

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SR@N12.0 Mode - Transition - Guide

Hochgeladen von

Copyright:

Verfügbare Formate

3900 Series Multimode Base Station

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2016-12-09) Huawei Proprietary and Confidential i

Issue 03 (2016-12-09) Huawei Proprietary and Confidential ii

4 Mode Transition Examples......................................................................................................184

Issue 03 (2016-12-09) Huawei Proprietary and Confidential iii

4.15 Example: Mode Transition from G*U*L(F) to G*U*L(FT)....................................................................................312

5 Mode Transition Implementation..........................................................................................439

6 Upgrading Base Station Software..........................................................................................441

7 Applying for Licenses...............................................................................................................443

Issue 03 (2016-12-09) Huawei Proprietary and Confidential iv

8.3.2.2 Preparing Transmission Data................................................................................................................................498

Issue 03 (2016-12-09) Huawei Proprietary and Confidential v

9 Setting NE Maintenance mode...............................................................................................646

11 Activating Configuration Data and Commissioning.......................................................651

12 Ending Maintenance Mode for NEs....................................................................................697

14 Examples for Co-MPT Reconstruction and Mode Transition........................................743

Issue 03 (2016-12-09) Huawei Proprietary and Confidential vi

1.1 About This Document

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 1

Figure 1.1 Mode transition procedure

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 2

The following table describes procedures in the mode transition process.

Table 1.1 Procedure for mode transition of multimode base stations

Preparation Planning mode transition 1. Make a data plan before

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 3

Phase Item Operation

data shorten the service

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 4

3 Planning Mode Transition

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 5

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 6

mode n to NB- mode n to NB- mode to NB-IoT

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 7

3.2.1 Overall RF Planning Process

The overall process of RF module planning is as follows:

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 8

Table 3.1 Scenario analysis

RF module New band 3.2.2Adding an RF Module

3.2.2 Adding an RF Module

RF module RRU/RFU See N/A

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 9

Material Type Material Name Quantity Remarks

Optical module For the RRU

 Software version requirement

License License License License Sales Unit Mode

First Mode Multi-Mode 82205540 LGMIMMM Per band per G

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 10

License License License License Sales Unit Mode

Multi-Mode Multi-Mode 82205398 LQW9RFB Per band per U

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 11

License Control License License License Sales Mod

RF 800M/900M RF 82204034 LLT1RFM Per L

Sce Module License License Licens License Sales Mo

GU Non-blade GSM/UMTS The 822011 LQW9MBT Per U

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 12

Sce Module License License Licens License Sales Mo

Issue 03 (2016-12-09) Huawei Proprietary and Confidential 13

Sce Module License License Licens License Sales Mo

NB- module Mode Mode 96 01 sector

 Data configuration requirement (software)

4.15 Example: Mode Transition from GUL(F) to GUL(FT)....................................................................................312