3900 Series Multimode Base Station V100R011C10 Mode Transition Guide

3900 Series Multimode Base Station V100R011C10

Mode Transition Guide

Issue

01

Date

2015-12-30

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:

[email protected]

Issue 01 (2015-12-30)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

3900 Series Multimode Base Station Mode Transition Guide

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....................................................................................................................................................................6 3.2.1 Overall RF Planning Process.......................................................................................................................................6 3.2.2 Adding an RF Module.................................................................................................................................................7 3.2.3 Reusing the Original Multiband Module...................................................................................................................12 3.2.4 Applying SDR to the Original RF Module................................................................................................................15 3.2.5 Adding a Module to the Original SDR Module.........................................................................................................20 3.2.6 Replacing the Original Module with a New SDR Module........................................................................................26 3.3 Antenna and Feeder Networking..................................................................................................................................32 3.3.1 Overall Antenna and Feeder Planning Process..........................................................................................................32 3.3.2 Adding an Independent Antenna (Antenna Port) and an Independent Feeder..........................................................33 3.3.3 Adding an Independent Antenna (Antenna Port) and Sharing the Original Feeder..................................................44 3.3.4 Broadband Antenna (Antenna Port) Being Shared By the Original Mode and New Mode......................................55 3.3.5 SDR RF Module of the New Mode Using the Original Feeder................................................................................58 3.4 Co-MPT or Separate-MPT Planning............................................................................................................................59 3.4.1 Overall Co-MPT or Separate-MPT Planning Process...............................................................................................59 3.4.2 Adding a Main Control Board of the New Mode to the Original BBU....................................................................61 3.4.3 Adding a new BBU and a Main Control Board of the New Mode............................................................................65 3.4.4 Adding a New Mode to the Co-MPT Base Station...................................................................................................67 3.4.5 Co-MPT Reconstruction and Adding a New Mode to the Co-MPT Base Station....................................................69 3.5 BBU Interconnection....................................................................................................................................................87 3.5.1 Overall BBU Interconnection Planning Process.......................................................................................................87 3.5.2 Adding a BBU for BBU Interconnection Through UCIU+UMPT...........................................................................89 3.5.3 Adding a BBU for BBU Interconnection Through UMPT+UMPT..........................................................................93 3.6 Clock Planning.............................................................................................................................................................96 3.6.1 Overall Clock Planning Process................................................................................................................................96 3.6.2 New Mode Using an Independent Reference Clock with Separate-MPT Configuration..........................................98 Issue 01 (2015-12-30)


ii


Contents

3.6.3 New Mode and Original Mode Sharing Reference Clock with Separate-MPT Configuration.................................99 3.6.4 New Mode Requiring Modification to the Clock Source with Co-MPT Configuration.........................................100 3.7 Baseband Planning.....................................................................................................................................................102 3.7.1 Overall Baseband Planning Process........................................................................................................................103 3.7.2 Adding an Independent Baseband Board to the New Mode with Separate-MPT Configuration............................104 3.7.3 Adding an Independent Baseband Processing Board to the New Mode with Co-MPT Configuration...................106 3.7.4 Adding a New Mode to the Original Baseband Processing Board with Co-MPT Configuration...........................108 3.8 CPRI-based Topology Planning.................................................................................................................................110 3.8.1 Overall CPRI-based Topology Planning.................................................................................................................110 3.8.2 Chain Topology for RF Modules.............................................................................................................................111 3.8.3 Dual-Star Topology (Load Sharing) for SDR RF Modules.....................................................................................114 3.8.4 CPRI MUX for SDR RF Modules...........................................................................................................................118 3.9 Transmission Networking Planning...........................................................................................................................121 3.9.1 Transmission Networking Planning Process...........................................................................................................122 3.9.2 New Mode Using Independent Transmission with Separate-MPT Configuration..................................................124 3.9.3 New Mode Using the Transmission Port Provided by the Original Mode with Separate-MPT Configuration......126 3.9.4 New Mode Providing a Transmission Port Shared by the Original Mode with Separate-MPT Configuration......128 3.9.5 Co-Transmission for New and Original Modes with co-MPT Configuration.........................................................131 3.10 Equipment Auxiliary Planning.................................................................................................................................134 3.11 Summary of Mode Transition Planning....................................................................................................................140 3.11.1 License File Requirement......................................................................................................................................140 3.11.2 NE Software Version Requirement........................................................................................................................154 3.11.3 Board and Cable Installation Requirement............................................................................................................154 3.11.4 Data Configuration Requirement...........................................................................................................................157 3.11.5 Tool Requirements for Co-MPT Reconstruction...................................................................................................163

4 Mode Transition Examples.........................................................164 4.1 Example: Mode Transition from GU to GU+L (UCIU+UMPT)...............................................................................164 4.2 Example: Mode Transition from GO to GL...............................................................................................................177 4.3 Example: Mode Transition from GO to GU...............................................................................................................191 4.4 Example: Mode Transition from UO to UL...............................................................................................................200 4.5 Example: Mode Transition from GU to GU (CPRI MUX)+L (BBU Interconnection, Inter-BBU Triple-Mode SDR) ..........................................................................................................................................................................................207 4.6 Example: Mode Transition from GO to G*L.............................................................................................................221 4.7 Example: Mode Transition from UO to G*U.............................................................................................................229 4.8 Example: Mode Transition from GU to G[U*L]........................................................................................................238 4.9 Example: Mode Transition from GU to GU+L (UMPT+UMPT, BBU Interconnection)..........................................247 4.10 Example: Mode Transition from GU+L (UCIU+UMPT) to GU+LT (UCIU+UMPT)............................................258 4.11 Example: Mode Transition from LO to G*L CPRI Load Sharing4.8, 4.9...............................................................266 4.12 Example: Mode Transition from G*U to G*U*L (Outdoor BBU)..........................................................................273 4.13 Example: Mode Transition from LO (FDD) to LO (FDD+TDD)............................................................................282 4.14 Example: Mode Transition from LO (TDD) to LO (FDD+TDD)............................................................................288

Issue 01 (2015-12-30)


iii


Contents

5 Mode Transition Implementation................................................292 5.1 Policies.......................................................................................................................................................................292 5.2 Procedure for Implementing Mode Transition...........................................................................................................293

6 Upgrading Base Station Software...............................................294 6.1 Recording Base Station Status Before Mode Transition............................................................................................294 6.2 Upgrading Base Station Software..............................................................................................................................295 6.3 Upgrading Software of Base Stations in the Co-MPT Reconstruction Scenario.......................................................295

7 Preparing Data.......................................................................... 296 7.1 Adding a BBU Interconnection Link on the GSM Side (UCIU)................................................................................296 7.2 Synchronizing Data Configuration.............................................................................................................................297 7.3 Preparing Data for Co-MPT Reconstruction..............................................................................................................301 7.4 Configuring GSM Data..............................................................................................................................................301 7.4.1 Preparing Equipment Data......................................................................................................................................302 7.4.1.1 Adjusting RF Data (GBTS)..................................................................................................................................303 7.4.1.2 Adjusting Equipment Data in Co-MPT Scenarios................................................................................................303 7.4.2 Preparing Transmission Data...................................................................................................................................303 7.4.2.1 Adjusting GBTS Data...........................................................................................................................................303 7.4.2.2 Adjusting Co-MPT Data.......................................................................................................................................304 7.4.3 Preparing Radio Data..............................................................................................................................................304 7.4.3.1 Adjusting GBTS Data...........................................................................................................................................304 7.4.3.2 Adjusting Co-MPT Data.......................................................................................................................................305 7.4.4 Preparing Transmission, Equipment, and Radio Adjustment Data (Co-MPT).......................................................305 7.5 Configuring UMTS Data............................................................................................................................................306 7.5.1 Preparing Equipment Data......................................................................................................................................307 7.5.1.1 Separate-MPT.......................................................................................................................................................307 7.5.1.2 Co-MPT................................................................................................................................................................307 7.5.2 Preparing Transmission Data...................................................................................................................................308 7.5.2.1 Separate-MPT.......................................................................................................................................................308 7.5.2.2 Co-MPT................................................................................................................................................................308 7.5.3 Preparing Radio Data..............................................................................................................................................309 7.5.3.1 Separate-MPT.......................................................................................................................................................309 7.5.3.2 Co-MPT................................................................................................................................................................309 7.5.4 Adjusting Transmission, Device, and Radio Data...................................................................................................309 7.5.4.1 Separate-MPT.......................................................................................................................................................310 7.5.4.2 Co-MPT................................................................................................................................................................310 7.6 Configuring LTE Data................................................................................................................................................311 7.6.1 Preparing Equipment Data......................................................................................................................................312 7.6.1.1 Separate-MPT.......................................................................................................................................................312 7.6.1.2 Co-MPT................................................................................................................................................................312 7.6.2 Preparing Transmission Data...................................................................................................................................313 7.6.2.1 Separate-MPT.......................................................................................................................................................313 Issue 01 (2015-12-30)


iv


Contents

7.6.2.2 Co-MPT................................................................................................................................................................313 7.6.3 Preparing Radio Data..............................................................................................................................................313 7.6.3.1 Separate-MPT.......................................................................................................................................................313 7.6.3.2 Co-MPT................................................................................................................................................................314 7.6.4 Adjusting Transmission, Equipment, Radio Data (LTE Only)................................................................................314 7.6.4.1 Separate-MPT.......................................................................................................................................................315 7.6.4.2 Co-MPT................................................................................................................................................................315 7.6.5 Adjusting Transmission, Equipment, Radio Data (FDD+TDD).............................................................................315 7.7 Binding Base Station Multimode Relationships.........................................................................................................317 7.8 Checking MBTS Data Consistency............................................................................................................................318 7.9 Checking Data Preparations.......................................................................................................................................318

8 Setting NE Maintenance mode...................................................319 9 Adjusting Hardware...................................................................322 9.1 Adjusting Equipment..................................................................................................................................................322 9.2 Adjusting Feeders.......................................................................................................................................................323 9.3 Adjusting Transmission Cables..................................................................................................................................323

10 Activating Configuration Data and Commissioning.....................324 10.1 Activating Data in Incremental Scripts.....................................................................................................................324 10.2 Base Station Deployment by PnP.............................................................................................................................325 10.3 Base Station Deployment by USB...........................................................................................................................325 10.4 PnP-based Co-MPT Reconstruction.........................................................................................................................325

11 Ending Maintenance Mode for NEs............................................326 12 Appendix for Co-MPT Reconstruction........................................327 12.1 Paths for Saving Converted Data.............................................................................................................................327 12.2 Preparing GSM Licenses..........................................................................................................................................328 12.3 What Should I Do If an Error Prompting "Data Preparation failed" Occurs During the Execution of a PnP Task?333 12.4 How Can I Roll Back Base Stations When Co-MPT Reconstruction Fails?...........................................................333 12.5 Constraints and Limitations......................................................................................................................................335 12.6 Description about Co-MPT Data Conversion..........................................................................................................340 12.6.1 Application Scenarios and Restrictions of the MBSC Reconstruction Module....................................................341 12.6.2 Application Scenarios and Restrictions of the GBTS Reconstruction Module.....................................................342 12.6.3 Application Scenarios and Restrictions of the SRAN Reconstruction Module....................................................343 12.7 Co-MPT Reconstruction Scenarios..........................................................................................................................344 12.7.1 GSM Co-MPT Reconstruction Scenario...............................................................................................................345 12.7.2 UMTS Co-MPT Reconstruction Scenario.............................................................................................................346 12.7.3 LTE Co-MPT Reconstruction Scenario.................................................................................................................346 12.7.4 GSM and UMTS Co-MPT Reconstruction Scenario............................................................................................347 12.7.5 GSM and LTE Co-MPT Reconstruction Scenario................................................................................................349 12.7.6 UMTS and LTE Co-MPT Reconstruction Scenario..............................................................................................352 12.7.7 G&[U*L] or U&[G*L]/L&[G*U] Reconstruction Scenario................................................................................354 Issue 01 (2015-12-30)


v


Contents

12.7.8 GU+L Co-MPT Reconstruction Scenario.............................................................................................................356 12.7.9 GL+U Co-MPT Reconstruction Scenario.............................................................................................................359 12.7.10 G&[U*L]+[U*L] Reconstruction Scenario.........................................................................................................364 12.7.11 Two BBUs Combined into One Co-MPT Reconstruction...................................................................................366

13 Examples for Co-MPT Reconstruction and Mode Transition.........371

Issue 01 (2015-12-30)


vi


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 transmission. 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 01 (2015-12-30)


1


2 Mode Transition

2

Mode Transition

Figure 1.1 Mode transition procedure

Issue 01 (2015-12-30)


2


2 Mode Transition

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.

Implementation

Upgrading software

Skip this step if the base station uses the software of the target version.

Recording related information

Record the active alarms, cell status, service KPIs for comparison before and after mode transition.

Configuring data for coMPT reconstruction

An optional operation. In the transition from a singlemode base station to a coMPT 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.

Issue 01 (2015-12-30)

Configuring data for capacity expansion or mode addition

Configure data for capacity expansion or mode addition using the CME according to the data plan.

Adjusting hardware

Perform these two


3


Phase

Verification

2 Mode Transition

Item

Operation

Activating configuration data

operations in parallel to shorten the service interruption duration.

Commissioning base stations

For the mode that has not 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:

Outputting engineering reports



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

Summarize the reparenting 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 NEP-SD-Based Wireless Base Station Design Guidelines.

Issue 01 (2015-12-30)


4


3

3 Planning Mode Transition

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.

Issue 01 (2015-12-30)


5



Solid lines with arrows indicate the dependent objects and dotted lines with arrows point to further information of specific objects. Figure 1.1 Constraints of the subsystems and other items on each other

3.2 RF Planning This section describes RF planning.

3.2.1 Overall RF Planning Process Figure 1.1 RF planning process

Issue 01 (2015-12-30)


6



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 module supports the required 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. Table 1.1 Scenario analysis Categor y

New Band/Refa rming

Scenario

RF module

New band

Adding an RF Module Reusing the Original MultiBand Module

Refarming

Applying SDR to the Original RF Module Adding a Module to the Original SDR Module Replacing the Original Module with a New SDR Module

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 the selection, see GUL Base Station Overview and Selection Guide. 2. Precautions (hardware) Issue 01 (2015-12-30)


7



Pay attention to the following items: 

Mapping relationship between the added module and cabinet



Requirements for power supply or power distribution

3. Engineering guidelines 

Material requirement (hardware)

Material Type

Material Name

Quantity

Remarks

RF module

RRU and RFU

See SRAN&GBSS&RAN &eRAN BTS3900 Configuration Manual.

-

CPRI high-speed cable CPRI fiber optic cable



For the RFU For the RRU

Optical module

For the RRU

RRU power cable

For the RRU

RF interconnection cable

Required by the GSM, multimode, and UMTS RF modules

Software version requirement

For the mapping relationship between the RF modules and versions, see 3900 Series Base Station Software and Hardware Compatibility Description. 

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 Control Item Name (SBOM)

License Control Item Name (BBOM)

License BBOM

License Abbrevia tion

Sales Unit

Mode

First Mode First Band License for Multi-Band RF Module (UMTS)

Multi-Mode Multi-Band License for Multi-Band RF Module (UMTS) (Per Band per RRU)

82205398

LQW9RFB AND01

Per band

U

Multi-Mode

Multi-Mode

82205398

LQW9RFB

Per band

U

Issue 01 (2015-12-30)


8



License Control Item Name (SBOM)


License BBOM

Multi-Band License for Multi-Band RF Module (UMTS)

Multi-Band License for Multi-Band RF Module (UMTS) (Per Band per RRU)

First Mode First Band License for Multi-Band RF Module (LTE FDD)

Multi-Mode Multi-Band License for Multi-Band RF Module (LTE FDD) (Per Band per RRU)

82205382

Multi-Mode Multi-Band License for Multi-Band RF Module (LTE FDD)


82205382


Sales Unit

Mode

LLT1MML MBRM01

Per band

L

LLT1MML MBRM01

Per band

L

AND01

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. License Control Item Name (SBOM)


License BBOM

License Abbrevi ation

Sale s Unit

Mod e

RF 800M/900M Multi Band license


82204034

LLT1RFM B01

Per band per RRU

L

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.

Issue 01 (2015-12-30)


9



Sc en ari o

Module Type



Licen se BBO M


Sale s Unit

Mo de

GU

Non-blade module

GSM/UMTS Dual Mode license

The number of RF Units with GSM/UM TS dual mode function enabled

822011 99

LQW9MBT SRF02

Per sector

U

Blade&A AU

GSM/UMTS Dual Mode license for Blade&AAU


822011 99

LQW9MBT SRF02

Per sector

U

Non-blade module

GSM/LTE Dual Mode license

GSM/LTE Dual Mode license(per Sector)

822014 72

LLT1GLDM 01

Per sector

L

Blade&A AU

GSM/LTE Dual Mode license for Blade&AAU


822014 72

LLT1GLDM 01

Per sector

L

Non-blade module

UMTS/LTE Dual Mode license

UMTS/LT E Dual Mode license(per Sector)

822014 73

LLT1ULDM 01

Per sector

L

Blade&A AU

UMTS/LTE Dual Mode license for Blade&AAU


822014 73

LLT1ULDM 01

Per sector

L

Non-blade module

RF GSM/UMTS Dual Mode license + RF GSM/LTE Dual Mode

N/A

N/A

N/A

Per sector

U+ L

GL

UL

GU L

Issue 01 (2015-12-30)


10


Sc en ari o

Module Type




Licen se BBO M


Sale s Unit

Mo de

N/A

N/A

N/A

Per sector

U+ L

license or RF GSM/UMTS Dual Mode license + RF UMTS/LTE Dual Mode license Blade&A AU

GSM/UMTS Dual Mode 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



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. Guidelines: For details, 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. - Configure the working mode of an RF unit according to the live network deployment.

Issue 01 (2015-12-30)


11



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

Configur ation Object

MOC

Parame ter Name

Paramete r ID

Value (Example)

RF module

Adding an RXU

RRU

Cabinet No.

CN

0

Adding an RXU

RRU

Subrack No.

SRN

60

Adding an RXU

RRU

Slot No.

SN

3

Adding an RXU

RRU

RRU type

RT

MRRU

Adding an RXU

RRU

RRU Topo Position

TP

TRUNK (in the main chain or ring)

Adding an RXU

RRU

RRU Chain/Rin g No.

RCN

0

Adding an RXU

RRU

RRU Position

PS

0

Adding an RXU

RRU

RF Unit Working Mode

RS

GL

Adding an RXU

RRU

Number of RX channels

RXNUM

2

Adding an RXU

RRU

Number of TX channels

TXNUM

2



Service impact

Scenario

Impact on Services of the Original Mode

Adding a new RF mode and adjusting the antenna and feeder of the original RF module

Services of the original RF module are affected during the antenna and feeder adjustment.

Adding a new RF module and adjusting the data configuration of the original RF module

Services are affected during the data configuration and RF module adjustment.

Issue 01 (2015-12-30)


12



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. 3. Engineering guidelines 


Material Type

Material Name

Quantity

Remarks

RF module

CPRI fiber optic cable

Same as the number of RF modules

Determine whether to add a fiber optic cable based on the CPRI-based topology.

Optical module

Twice the number of RF modules




Version requirement (software)

For the mapping relationship between the baseband processing boards and versions, see GUL Base Station Overview and Selection Guide. 

License requirement (software)

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 Control Item Name (SBOM)


License BBOM


Sales Unit

Mode



82205398

LQW9RFB AND01

Per band

U

Issue 01 (2015-12-30)


13





License BBOM


Sales Unit

Mode

Multi-Mode Multi-Band License for Multi-Band RF Module (UMTS)


82205398

LQW9RFB AND01

Per band

U



82205382

LLT1MML MBRM01

Per band

L



82205382

LLT1MML MBRM01

Per band

L



License BBOM


Sale s Unit

Mod e



82204034

LLT1RFM B01

Per band per RRU

L




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.

Issue 01 (2015-12-30)


14



For details, 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: - Configure the working mode of an RF unit according to the live network deployment. - Configure sector equipment parameters according to the type of a multiband module: sharing the same DIN connector or using different DIN connectors. 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


MOC

Parame ter Name

Paramete r ID

Value (Example)

RF module

Modifying an RXU

RRU

Cabinet No.

CN

0

Modifying an RXU

RRU

Subrack No.

SRN

60

Modifying an RXU

RRU

Slot No.

SN

3

Modifying an RXU

RRU

RRU type

RT

MRRU

Modifying an RXU

RRU

RRU Topo Position

TP


Modifying an RXU

RRU

RRU Chain/Rin g No.

RCN

0

Modifying an RXU

RRU

RRU Position

PS

0

Modifying an RXU

RRU


RS

GL

Modifying an RXU

RRU


RXNUM

2

Modifying an RXU

RRU


TXNUM

2



Issue 01 (2015-12-30)

Service impact


15



Scenario


Starting a new mode or modifying RRU configuration affects services of the original mode.

The startup or modification duration is short (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 3. Engineering guidelines Material Type

Material Name

Quantity

Remarks

RF module


Same as the number of RF modules


Optical module

Twice the number of RF modules




Version requirement

For the mapping relationship between the RF modules and versions, see GUL Base Station Overview and Selection Guide. 

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 Control Item Name (SBOM)


License BBOM


Sales Unit

Mode

First Mode First Band

Multi-Mode Multi-Band

82205398

LQW9RFB

Per band

U

Issue 01 (2015-12-30)


16





License BBOM

License for Multi-Band RF Module (UMTS)

License for Multi-Band RF Module (UMTS) (Per Band per RRU)

Multi-Mode Multi-Band License for Multi-Band RF Module (UMTS)


82205398






Sales Unit

Mode

LQW9RFB AND01

Per band

U

82205382

LLT1MML MBRM01

Per band

L

82205382

LLT1MML MBRM01

Per band

L

AND01



License BBOM


Sale s Unit

Mod e



82204034

LLT1RFM B01

Per band per RRU

L

Issue 01 (2015-12-30)


17



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. Sc en ari o

Module Type



Licen se BBO M


Sale s Unit

Mo de

GU

Non-blade module



822011 99

LQW9MBT SRF02

Per sector

U

Blade&A AU



822011 99

LQW9MBT SRF02

Per sector

U

Non-blade module



822014 72

LLT1GLDM 01

Per sector

L

Blade&A AU



822014 72

LLT1GLDM 01

Per sector

L

Non-blade module



822014 73

LLT1ULDM 01

Per sector

L

Blade&A AU



822014 73

LLT1ULDM 01

Per sector

L

Non-blade module

RF GSM/UMTS Dual Mode license + RF

N/A

N/A

N/A

Per sector

U+ L

GL

UL

GU L

Issue 01 (2015-12-30)


18


Sc en ari o

Module Type




Licen se BBO M


Sale s Unit

Mo de

N/A

N/A

N/A

Per sector

U+ L

GSM/LTE Dual Mode license or RF GSM/UMTS Dual Mode license + RF UMTS/LTE Dual Mode license Blade&A AU





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. You can use the GUI, summary data file, or MML commands to configure the data. For details, 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: Issue 01 (2015-12-30)


19



- Determine the CPRI-based topology according to topology types supported by an RF module in multimode scenarios. - Configure the working mode of an RF unit according to the live network deployment. 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


MOC

Parame ter Name

Paramete r ID

Value (Example)

RF module

Modifying an RXU

RRU

Cabinet No.

CN

0

Modifying an RXU

RRU

Subrack No.

SRN

60

Modifying an RXU

RRU

Slot No.

SN

3

Modifying an RXU

RRU

RRU type

RT

MRRU

Modifying an RXU

RRU

RRU Topo Position

TP


Modifying an RXU

RRU

RRU Chain/Rin g No.

RCN

0

Modifying an RXU

RRU

RRU Position

PS

0

Modifying an RXU

RRU


RS

GL

Modifying an RXU

RRU


RXNUM

2

Modifying an RXU

RRU


TXNUM

2



Service impact

Scenario




The original RF module is a legacy V1

Adjusting the working mode of the original

Issue 01 (2015-12-30)


20



Scenario


or V2 RF module.

mode resets RRUs, interrupting services for one minute.

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 the selection, see GUL Base Station Overview and Selection 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. Greater RFU's transmit power indicates higher requirements for power distribution and heat dissipation of the cabinet. Therefore, RFUs of small power can work with all cabinets while RFUs of large power can work only with Ver.C cabinets, Ver.D cabinets (or the ones has equivalent capabilities after upgrade), and the BTS3900AL (Ver.A) cabinets.



Pay attention to requirements for power supply or power distribution.


Material requirement

Material Type

Material Name

Quantity

Remarks

Board

RRU/RFU

See SRAN&GBSS&RAN &eRAN BTS3900 Configuration Manual.

-

CPRI high-speed cable

Issue 01 (2015-12-30)

For the RFU. Replace the original CPRI cable if it cannot be reused.


For the RRU

Optical module

For the RFU. Replace the original optical module if it cannot be reused.

RRU power cable

For the RFU. Replace the original


21



Material Type

Material Name

Quantity

Remarks RRU power cable if it cannot be reused.





Version requirement


License requirement

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: 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. Multimode RF license 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 Control Item Name (SBOM)


License BBOM


Sale s Unit

Mod e

First Mode First Band License for MultiBand RF Module (UMTS)


82205398

LQW9RFB AND01

Per band

U

Multi-Mode MultiBand License for Multi-Band RF Module (UMTS)


82205398

LQW9RFB AND01

Per band

U

First Mode First Band

Multi-Mode

82205382

LLT1MML

Per

L

Issue 01 (2015-12-30)


22





License for MultiBand RF Module (LTE FDD)

Multi-Band License for Multi-Band RF Module (LTE FDD) (Per Band per RRU)

Multi-Mode MultiBand License for Multi-Band RF Module (LTE FDD)


License BBOM

82205382


Sale s Unit

MBRM01

band

LLT1MML MBRM01

Per band

Mod e

L



License BBOM


Sale s Unit

Mod e



82204034

LLT1RFM B01

Per band per RRU

L

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. Sc en ari o

Module Type



Licen se BBO M

License Abbreviati on

Sal es Un it

Mo de

GU

Non-blade module



822011 99

LQW9MBTSR F02

Per sect or

U

Blade&A

GSM/UMTS

The

822011

LQW9MBTSR

Per

U

Issue 01 (2015-12-30)


23


Sc en ari o

GL

UL

GU L


Module Type



Licen se BBO M


Sal es Un it

Mo de

AU

Dual Mode license for Blade&AAU

number of RF Units with GSM/UM TS dual mode function enabled

99

F02

sect or

Non-blade module


GSM/LTE Dual Mode license(pe r Sector)

822014 72

LLT1GLDM01

Per sect or

L

Blade&A AU


GSM/LTE Dual Mode license(pe r Sector)

822014 72

LLT1GLDM01

Per sect or

L

Non-blade module


UMTS/LT E Dual Mode license(pe r Sector)

822014 73

LLT1ULDM01

Per sect or

L

Blade&A AU


UMTS/LT E Dual Mode license(pe r Sector)

822014 73

LLT1ULDM01

Per sect or

L

Non-blade module

RF GSM/UMTS Dual Mode license + RF GSM/LTE Dual Mode license

N/A

N/A

N/A

Per sect or

U+ L

N/A

N/A

N/A

Per

U+

or RF GSM/UMTS Dual Mode license + RF UMTS/LTE Dual Mode license Blade&A Issue 01 (2015-12-30)

GSM/UMTS


24


Sc en ari o


Module Type


AU

Dual Mode license for Blade&AAU + GSM/LTE Dual Mode license for Blade&AAU


Licen se BBO M


Sal es Un it

Mo de

sect or

L

or GSM/UMTS Dual Mode license for Blade&AAU + UMTS/LTE Dual Mode license for Blade&AAU



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: 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. You can use the GUI, summary data file, or MML commands to configure the data. For details, 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. - Configure the working mode of an RF unit according to the live network deployment. 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.

Issue 01 (2015-12-30)


25



Domain


MOC

Parame ter Name

Paramete r ID

Value (Example)

RF module

Adding an RXU

RRU

Cabinet No.

CN

0

Adding an RXU

RRU

Subrack No.

SRN

60

Adding an RXU

RRU

Slot No.

SN

3

Adding an RXU

RRU

RRU type

RT

MRRU

Adding an RXU

RRU

RRU Topo Position

TP


Adding an RXU

RRU

RRU Chain/Rin g No.

RCN

0

Adding an RXU

RRU

RRU Position

PS

0

Adding an RXU

RRU


RS

GL

Adding an RXU

RRU


RXNUM

2

Adding an RXU

RRU


TXNUM

2



Service impact

Scenario




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: Issue 01 (2015-12-30)


26



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 Pay attention to the following items when replacing the original RF module: 

Mapping relationship between the added module and cabinet



Requirements for power supply or power distribution



Whether the optical module of the original RF module shall be replaced



Whether the RRU power cable of the original RF module shall be replaced



Material Type

Material Name

Quantity

Remarks

Board

RRU/RFU

Determined based on the plan

-




For the RFU. Replace the original CPRI cable if it cannot be reused.


For the RRU

Optical module

For the RFU. Replace the original optical module if it cannot be reused.

RRU power cable

For the RFU. Replace the original RRU power cable if it cannot be reused.

Version requirement


License requirement

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:

Issue 01 (2015-12-30)


27



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. Multimode RF license 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 Control Item Name (SBOM)


License BBOM


Sale s Unit

Mod e

First Mode First Band License for MultiBand RF Module (UMTS)


82205398

LQW9RFB AND01

Per band

U

Multi-Mode MultiBand License for Multi-Band RF Module (UMTS)


82205398

LQW9RFB AND01

Per band

U

First Mode First Band License for MultiBand RF Module (LTE FDD)


82205382

LLT1MML MBRM01

Per band

L

Multi-Mode MultiBand License for Multi-Band RF Module (LTE FDD)


82205382

LLT1MML MBRM01

Per band

L



License BBOM


Sale s Unit

Mod e

RF 800M/900M

RF

82204034

LLT1RFM

Per

L

Issue 01 (2015-12-30)


28





Multi Band license

800M/900M Multi Band license

License BBOM


Sale s Unit

B01

band per RRU

Mod e

If SDR is used on a band, the related RF multimode license of the mode shall be purchased. Sc en ari o

Module Type



Licen se BBO M

License Abbreviat ion

Sal es Uni t

Mo de

GU

Non-blade module



822011 99

LQW9MBTS RF02

Per secto r

U

Blade and AAU



822011 99

LQW9MBTS RF02

Per secto r

U

Non-blade module



822014 72

LLT1GLDM0 1

Per secto r

L

Blade and AAU



822014 72

LLT1GLDM0 1

Per secto r

L

Non-blade module



822014 73

LLT1ULDM0 1

Per secto r

L

GL

UL

Issue 01 (2015-12-30)


29


Sc en ari o

GU L


Module Type



Licen se BBO M

License Abbreviat ion

Sal es Uni t

Mo de

Blade and AAU



822014 73

LLT1ULDM0 1

Per secto r

L

Non-blade module

RF GSM/UMTS Dual Mode license + RF GSM/LTE Dual Mode license

N/A

N/A

N/A

Per secto r

U+ L

N/A

N/A

N/A

Per secto r

U+ L

or RF GSM/UMTS Dual Mode license + RF UMTS/LTE Dual Mode license Blade and AAU





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).

Issue 01 (2015-12-30)


30



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. You can use the GUI, summary data file, or MML commands to configure the data. For details, 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. - Configure the working mode of an RF unit according to the live network deployment. - 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. 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


MOC

Parame ter Name

Paramete r ID

Value (Example)

RF module

Adding an RXU

RRU

Cabinet No.

CN

0

Adding an RXU

RRU

Subrack No.

SRN

60

Adding an RXU

RRU

Slot No.

SN

3

Adding an RXU

RRU

RRU type

RT

MRRU

Adding an RXU

RRU

RRU Topo Position

TP


Adding an RXU

RRU

RRU Chain/Rin g No.

RCN

0

Adding an RXU

RRU

RRU Position

PS

0

Adding an RXU

RRU


RS

GL

Adding an RXU

RRU


RXNUM

2

Adding an RXU

RRU

Number of TX

TXNUM

2

Issue 01 (2015-12-30)


31


Domain



MOC

Parame ter Name

Paramete r ID

Value (Example)

channels



Service impact

Scenario


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.

3.3 Antenna and Feeder Networking This section describes antenna and feeder planning.

Issue 01 (2015-12-30)


32



3.3.1 Overall Antenna and Feeder Planning Process Figure 1.1 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. 

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. Issue 01 (2015-12-30)


33

3900 Series Multimode Base Station Mode Transition Guide 


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 1.1 Analysis of antenna and feeder planning scenarios Catego ry

RF modul e

Scenario

Antenna and feeder networki ng

New mode only

Adding an independent antenna (antenna port) and an independent feeder Adding an independent antenna (antenna port) and sharing the original feeder Broadband antenna (antenna port) being shared by the original mode and new mode

SDR RF module

SDR RF module of the new mode using the original feeder

3.3.2 Adding an Independent Antenna (Antenna Port) and an Independent Feeder 1. Scenario description and application scope

Issue 01 (2015-12-30)


34



Figure 1.1 Scenario without RET

Issue 01 (2015-12-30)


35



Figure 1.2 Scenario with RET

Issue 01 (2015-12-30)


36



Figure 1.3 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.

Issue 01 (2015-12-30)


37



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 3.1 Material requirement Material Type

Material Name

Quantity

Remarks

Antenna and feeder

Antenna

Same as the number of sectors in the new mode

Required when the original antenna is to be reconstructed or replaced

Feeder

Twice the number of sectors

Not required when the RRU and antenna are directly connected to each other. The length of the feeder needs to be determined according to the site survey.

Issue 01 (2015-12-30)

Jumper

-

The length of the feeder needs to be determined according to the site survey.

SBT

Same as the number of sectors

Required on the 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


Configured as required by the network plan.

RCU


Required when RET is required but no internal RET is


38



Material Type

Material Name

Quantity

Remarks available.



AISG cable from the SBT or TMA to the RCU


Required for connecting to the SBT or TMA when RET is required. The lengths of the AISG cable vary with scenarios.

AISG cable from the RRU to the RCU


Required when the RRU and RET are directly connected to each other.

Version requirement

None 

License requirement

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 3.2 License control items for optional features of RET management Feature Name

License Control Item

License Abbreviation

(LTE-FDD) LOFD-001024 Remote Electrical Tilt Control

Remote Electrical Tilt Control

LLT1RET01

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


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.

Issue 01 (2015-12-30)


39



- If a TMA is required, configure the TMA and TMA attenuation corresponding to the RRU or RFU's channel. For details, 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 3.3 Key parameters related to the RETPORT Domai n

Configu ration Object

MOC

Parameter Name

Param eter ID

Example Value

Antenna and feeder

Adding an RXU

RETPORT

Cabinet No.

CN

0

Adding an RXU

RETPORT

Subrack No.

SRN

62

Adding an RXU

RETPORT

Slot No.

SN

0

Adding an RXU

RETPORT

Port No.

PN

RET_PORT

Adding an RXU

RETPORT

ALD Power Switch

PWRSWI TCH

ON

Adding an RXU

RETPORT

Current Alarm Threshold

THRESH OLDTYP E

UER_SELF_DEF INE

Adding an RXU

RETPORT

Undercurrent Alarm Occur Threshold

UOTHD

40

Adding an RXU

RETPORT

Undercurrent Alarm Clear Threshold

UCTHD

60

Adding an RXU

RETPORT

Overcurrent Alarm Occur Threshold

OOTHD

850

Adding an RXU

RETPORT

Overcurrent Alarm Clear Threshold

OCTHD

750

The following table describes the key parameters that must be set when RET is controlled by the RRU or RFU through its ANTENNAPORT.

Issue 01 (2015-12-30)


40



Table 3.4 Key parameters related to the ANTENNAPORT Domain

Configurati on Object

MOC

Parame ter Name

Parame ter ID

Exampl e Value

Antenna and feeder

Adding an RXU

ANTENNAPO RT

Cabinet No.

CN

0

Adding an RXU

ANTENNAPO RT

Subrack No.

SRN

62

Adding an RXU

ANTENNAPO RT

Slot No.

SN

0

Adding an RXU

ANTENNAPO RT

Port No.

PN

R0A

Adding an RXU

ANTENNAPO RT

ALD Power Switch

PWRSWI TCH

ON

Adding an RXU

ANTENNAPO RT


THRESH OLDTYP E

UER_SEL F_DEFINE

Adding an RXU

ANTENNAPO RT

Undercurr ent Alarm Occur Threshold

UOTHD

40

Adding an RXU

ANTENNAPO RT

Undercurr ent Alarm Clear Threshold

UCTHD

60

Adding an RXU

ANTENNAPO RT

Overcurre nt Alarm Occur Threshold

OOTHD

850

Adding an RXU

ANTENNAPO RT

Overcurre nt Alarm Clear Threshold

OCTHD

750

Table 3.5 Key parameters related to the RET antenna Do ma in

Config uratio n Object

MO C

Parameter Name

Parameter ID

Example Value

Ant enn a

Adding RET

RET

Device No.

DEVICENO

1

Adding

RET

Control Port Cabinet

CTRLCN

0

Issue 01 (2015-12-30)


41



Do ma in


and feed er

RET

MO C

Parameter Name

Parameter ID

Example Value

No.

Adding RET

RET

Control Port Subrack No.

CTRLSRN

62

Adding RET

RET

Control Port Slot No.

CTRLSN

0

Adding RET

RET

Antenna Type

RETTYPE

Single antenna

Adding RET

RET

RET Subunit Number

SUBUNITNUM

1

Adding RET

RET

Polar Type

POLARTYPE

Equipment plan

Adding RET

RET

Antenna Scenario

SCENARIO

REGULAR

Table 3.6 Key parameters related to the RET subunit Domain


MOC

Paramet er Name

Paramet er ID

Example Value

Antenna and feeder

Adding RET

RETSUBU NIT

Device No.

DEVICEN O

1

Adding RET

RETSUBU NIT

Subunit No.

SUBUNITN O

1

Adding RET

RETSUBU NIT

Connect Port 1 Cabinet No.

CONNCN1

0

Adding RET

RETSUBU NIT

Connect Port 1 Subrack No.

CONNSRN 1

62

Adding RET

RETSUBU NIT

Connect Port 1 Slot No.

CONNSN1

0

Adding RET

RETSUBU NIT

Connect Port 1 Port No.

CONNPN1

R0A

Adding RET

RETSUBU NIT


CONNCN2

0

Adding RET

RETSUBU NIT

Connect Port 2 Subrack

CONNSRN

62

Issue 01 (2015-12-30)


42


Domain



MOC

Adding RET

RETSUBU NIT

Paramet er Name

Paramet er ID

No.

2

Tilt

TILT

Example Value

20

Table 3.7 Key parameters related to the TMA Do ma in


MO C

Parameter Name

Parameter ID

Example Value

Ant enn a and feed er

Adding a TMA

TMA

Device No.

DEVICENO

2

Adding a TMA

TMA

Control Port Cabinet No.

CTRLCN

0

Adding a TMA

TMA


CTRLSRN

62

Adding a TMA

TMA


CTRLSN

0

Adding a TMA

TMA

TMA Subunit Number

SUBUNITNUM

1

Table 3.8 Key parameters related to the TMA subunit Do mai n


MOC

Parameter Name

Parameter ID

Exampl e Value

Ante nna and feed er

Adding a TMA

TMA

Device No.

DEVICENO

2

Adding a TMA

TMA

Subunit No.

SUBUNITNO

1

Adding a TMA

TMA

Connect Port Cabinet No.

CONNCN

0

Adding a TMA

TMA

Connect Port Subrack No.

CONNSRN

62

Adding a TMA

TMA

Connect Port Slot No.

CONNSN

0

Adding a TMA

TMA

Connect Port No.

CONNPN

R0A

Issue 01 (2015-12-30)


43


Do mai n



MOC

Parameter Name

Parameter ID

Exampl e Value

Adding a TMA

TMA

Working Mode

MODE

NORMA L

Adding a TMA

TMA

Gain

GAIN

48

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 3.9 Key parameters related to RX channel attenuation Do mai n


MOC

Parameter Name

Parameter ID

Exampl e Value


Adding RXU RX channel 0

RXBRANCH

RX Channel No.

RXNO

0


RXBRANCH

Logical Switch of RX Channel

RXSW

ON


RXBRANCH

Attenuation

ATTEN

10


RXBRANCH

RX Channel No.

RXNO

1


RXBRANCH


RXSW

ON


RXBRANCH

Attenuation

ATTEN

10




Service impact

Table 3.10 Service impact Scenario


Adding an antenna or reusing the original multiband antenna

Technically, services of the original mode are not 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

Issue 01 (2015-12-30)


44



Scenario

Impact on Services of the Original Mode actual site conditions to ensure personal safety.

Replacing the original antenna with a multiband antenna

Services of the original mode are interrupted during antenna replacement.

3.3.3 Adding an Independent Antenna (Antenna Port) and Sharing the Original Feeder 1. Scenario description and application scope

Issue 01 (2015-12-30)


45



Figure 1.1 Shared feeder, independent antenna port, and no RET

Issue 01 (2015-12-30)


46



Figure 1.2 Shared feeder, independent antenna port, and RET

Issue 01 (2015-12-30)


47



Figure 1.3 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 Issue 01 (2015-12-30)


48



mode (frequency band). The insertion loss of an inter-band combiner is 0.X dB. For details, see the relevant combiner datasheet. This scenario has the following characteristics: 

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. 3. Engineering guidelines 



Material Name

Quantity

Remarks

Board

Antenna



Jumper

-


SBT


Required on the antenna side when the following conditions are met:

Issue 01 (2015-12-30)










The RRU and antenna are not directly 49



Material Type

Material Name

Quantity

Remarks connected to each other.



TMA



RCU


Required when RET is required but no internal RET is available.

AISG cable from the SBT or TMA to the RET



Combiner

Four times the number of sectors

The combiner model is determined by frequency bands where signals are to be combined.

Version requirement None



License requirement 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 3.2 License control items for optional features of RET management Feature Name

License Control Item

License Abbreviation

(LTE-FDD) LOFD-001024 Remote Electrical Tilt Control


LLT1RET01

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


LLT1RET01



Data configuration requirement 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:

Issue 01 (2015-12-30)


50



- 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 details, 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 3.3 Key parameters related to the RETPORT Domai n


MOC

Parameter Name

Param eter ID

Example Value

Antenna and feeder

Adding an RXU

RETPORT

Cabinet No.

CN

0

Adding an RXU

RETPORT

Subrack No.

SRN

62

Adding an RXU

RETPORT

Slot No.

SN

0

Adding an RXU

RETPORT

Port No.

PN

RET_PORT

Adding an RXU

RETPORT

ALD Power Switch

PWRSWI TCH

ON

Adding an RXU

RETPORT


THRESH OLDTYP E

UER_SELF_DEF INE

Adding an RXU

RETPORT

Undercurrent Alarm Occur Threshold

UOTHD

40

Adding an RXU

RETPORT

Undercurrent Alarm Clear Threshold

UCTHD

60

Adding an RXU

RETPORT

Overcurrent Alarm Occur Threshold

OOTHD

850

Adding an RXU

RETPORT

Overcurrent Alarm Clear Threshold

OCTHD

750

Issue 01 (2015-12-30)


51



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


MOC

Parame ter Name

Parame ter ID

Exampl e Value

Antenna and feeder

Adding an RXU

ANTENNAPO RT

Cabinet No.

CN

0

Adding an RXU

ANTENNAPO RT

Subrack No.

SRN

62

Adding an RXU

ANTENNAPO RT

Slot No.

SN

0

Adding an RXU

ANTENNAPO RT

Port No.

PN

R0A

Adding an RXU

ANTENNAPO RT

ALD Power Switch

PWRSWI TCH

ON

Adding an RXU

ANTENNAPO RT


THRESH OLDTYP E

UER_SEL F_DEFINE

Adding an RXU

ANTENNAPO RT

Undercurr ent Alarm Occur Threshold

UOTHD

40

Adding an RXU

ANTENNAPO RT

Undercurr ent Alarm Clear Threshold

UCTHD

60

Adding an RXU

ANTENNAPO RT

Overcurre nt Alarm Occur Threshold

OOTHD

850

Adding an RXU

ANTENNAPO RT

Overcurre nt Alarm Clear Threshold

OCTHD

750

Issue 01 (2015-12-30)


52



Table 3.5 Key parameters related to the RET antenna Do ma in


MO C

Parameter Name

Parameter ID

Example Value


Adding RET

RET

Device No.

DEVICENO

1

Adding RET

RET


CTRLCN

0

Adding RET

RET


CTRLSRN

62

Adding RET

RET


CTRLSN

0

Adding RET

RET

Antenna Type

RETTYPE

Single antenna

Adding RET

RET

RET Subunit Number

SUBUNITNUM

1

Adding RET

RET

Polar Type

POLARTYPE

Equipment plan

Adding RET

RET

Antenna Scenario

SCENARIO

REGULAR

Table 3.6 Key parameters related to the RET subunit Domain


MOC

Paramet er Name

Paramet er ID

Example Value

Antenna and feeder

Adding RET

RETSUBU NIT

Device No.

DEVICEN O

1

Adding RET

RETSUBU NIT

Subunit No.

SUBUNITN O

1

Adding RET

RETSUBU NIT


CONNCN1

0

Adding RET

RETSUBU NIT


CONNSRN 1

62

Adding RET

RETSUBU NIT

Connect Port 1 Slot No.

CONNSN1

0

Adding RET

RETSUBU NIT

Connect Port 1 Port No.

CONNPN1

R0A

Issue 01 (2015-12-30)


53


Domain



MOC

Paramet er Name

Paramet er ID

Example Value

Adding RET

RETSUBU NIT


CONNCN2

0

Adding RET

RETSUBU NIT


CONNSRN 2

62

Adding RET

RETSUBU NIT

Tilt

TILT

20

Table 3.7 Key parameters related to the TMA Do ma in


MO C

Parameter Name

Parameter ID

Example Value


Adding a TMA

TMA

Device No.

DEVICENO

2

Adding a TMA

TMA


CTRLCN

0

Adding a TMA

TMA


CTRLSRN

62

Adding a TMA

TMA


CTRLSN

0

Adding a TMA

TMA

TMA Subunit Number

SUBUNITNUM

1

Table 3.8 Key parameters related to the TMA subunit Do mai n


MOC

Parameter Name

Parameter ID

Exampl e Value


Adding a TMA

TMA

Device No.

DEVICENO

2

Adding a TMA

TMA

Subunit No.

SUBUNITNO

1

Adding a TMA

TMA

Connect Port Cabinet No.

CONNCN

0

Issue 01 (2015-12-30)


54


Do mai n



MOC

Parameter Name

Parameter ID

Exampl e Value

Adding a TMA

TMA

Connect Port Subrack No.

CONNSRN

62

Adding a TMA

TMA

Connect Port Slot No.

CONNSN

0

Adding a TMA

TMA

Connect Port No.

CONNPN

R0A

Adding a TMA

TMA

Working Mode

MODE

NORMA L

Adding a TMA

TMA

Gain

GAIN

48

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 3.9 Key parameters related to RX channel attenuation Do mai n


MOC

Parameter Name

Parameter ID

Exampl e Value



RXBRANCH

RX Channel No.

RXNO

0


RXBRANCH


RXSW

ON


RXBRANCH

Attenuation

ATTEN

10


RXBRANCH

RX Channel No.

RXNO

1


RXBRANCH


RXSW

ON


RXBRANCH

Attenuation

ATTEN

10




Issue 01 (2015-12-30)

Service impact Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

55






Technically, services of the original mode are not 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.



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 1. Scenario description and application scope

Issue 01 (2015-12-30)


56



Figure 1.1 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. This scenario has the following characteristics: 

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. Issue 01 (2015-12-30)


57






Material Name

Quantity

Remarks

Board

Antenna


Required when the original antenna is replaced.

Jumper

-


Combiner








License requirement None. The antenna and feeder license of the original mode is used.



Data configuration requirement None. The antenna and feeder configuration of the original mode is used.



Service impact




Technically, services of the original mode are not 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.



Installing a combiner

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

Issue 01 (2015-12-30)


58



3.3.5 SDR RF Module of the New Mode Using the Original Feeder 1. Scenario description and application scope Figure 1.1 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 3. Engineering guidelines 

Material requirement (hardware) None. The original antenna and feeder are used.



Version requirement

None Issue 01 (2015-12-30)


59



License requirement 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.1 Overall co-MPT or separate-MPT planning process

The following table provides the comparison between separate-MPT and co-MPT configurations. Table 1.1 Comparison between separate-MPT and co-MPT configurations Comparison Item

Co-MPT

Separate-MPT

Hardware

Only one main control board (UMPT or UMDU) is required.

One main control board (GTMU/WMPT/LMPT/UM PT) shall be configured for each mode. One more BBU is required for a triple-mode base station. UMDU boards do not support separateMPT in SRAN10.0.

Inter-RAT decoupling

Tight coupling: NMS, transmission, clock, and CPRI MUX are tightly

Loose coupling: dual-star SDR and independent NMS, transmission, and clock

Issue 01 (2015-12-30)


60



Comparison Item

Co-MPT

Separate-MPT

coupled.

Tight coupling: cotransmission, common reference clock, and the CPRI MUX feature

Shared resources

Natural sharing: NMS, transmission, clock, CPRI, and baseband resources can be shared.

Sharing is implemented through the following features: co-transmission, common reference clock, and CPRI MUX. Baseband resources cannot be shared between modes.

Low-cost smooth mode transition

New mode is deployed in the same way as the feature is enabled.

An OM channel must be enabled for the new mode and new baseband resources must be deployed.

UBBP co-baseband

Co-baseband is supported by UBBP or UMDU boards.

Co-baseband is not supported by UBBP boards.

Version upgrade

All-at-once upgrade

All-at-once upgrade. Modeby-mode upgrade must be customized.

O&M experience

Consistent GUL O&M experience reduces the learning cost.

O&M experience varies according to each mode of GUL.

Note that the BBU3910A supports only co-MPT mode transition but not separate-MPT mode transition.

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. 

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.

Issue 01 (2015-12-30)


61



Table 1.2 Scenario analysis of separate-MPT or co-MPT mode transition Categor y

SeparateMPT or CoMPT

Scenario

Co-MPT or separateMPT planning

Separate-MPT

Adding a Main Control Board of the New Mode to the Original BBU Adding a New BBU and a Main Control Board of the New Mode

Co-MPT mode expansion

Adding a New Mode to the Co-MPT Base Station Co-MPT Reconstruction and Adding a New Mode to the Co-MPT Base Station

3.4.2 Adding a Main Control Board of the New Mode to the Original BBU 1. Scenario description and application scope

The BBU3900 or BBU3910 supports a maximum of two main control boards. When separateMPT 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)

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 Issue 01 (2015-12-30)


62



1) 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. 2) 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 expansion. All these operations interrupt services of the original mode. 3) 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. 4) The BBU3910 supports only new types of main control boards such as the GTMUb, GTMUc, and UMPT. 3. Engineering guidelines 


Material Type

Material Name

Quantity

Remarks

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, and a false alarm may be generated during mode transition and

Issue 01 (2015-12-30)


63



Material Type

Material Name

Quantity

Remarks services of the newly deployed mode may be interrupted.

GTMU



1

A GSM main control board is added.

Version requirement

For the mapping relationship between the baseband processing boards and versions, see 3900 Series Base Station Software and Hardware Compatibility Description. 

License requirement

No specific license control item is available for the main control board working in a separateMPT 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 work in co-MPT and multimode concurrency is applied. If the UMPT/UMDU works only in 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), and UMPT Multi Mode license(LTE TDD). 


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 Guidelines: Creating Base Stations > Creating Separate-MPT Multimode Base Stations in 3900 Series Base Station Initial Configuration Guide

Issue 01 (2015-12-30)


64



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 Not

Scenario


No SDR

Installing a new main control board

None

Upgrading software of a new main control board

None

Activating data configuration of a new main control board

None

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.

Installing a new main control board

During the installation of the 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.


If the SDR RF module needs to be upgraded, services of the original mode carried by the SDR RF module will be interrupted for about one minute.


When a cell of the new mode is established on the SDR RF module, services of the original mode will be affected for a short period of 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.

SDR

Issue 01 (2015-12-30)


65



3.4.3 Adding a new BBU and a Main Control Board of the New Mode 1. Scenario description and application scope

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. 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 BBUs and main control boards, see the following references: Selection of BBUs: GUL Base Station Overview and Selection Guide Selection of main control boards: GUL Base Station Overview and Selection Guide 2. Precautions 1) BBUs must be interconnected for mode transition where a new BBU is added and the two BBUs work in multiple modes. For details, see BBU Interconnection Feature Parameter Description. 2) The GTMU must be deployed in the primary BBU subrack. 3) A BBU3900/BBU3910 cannot be interconnected with a BBU3910A. Therefore, mode addition cannot be performed between BBU3900/BBU3910 and BBU3910A. 3. Engineering guidelines 


Material Type

Material Name

Quantity

Board

BBU

1

UMPT

1

Issue 01 (2015-12-30)


Remarks

66





Version requirement

For the mapping relationship between the main control boards and versions, see 3900 Series Base Station Software and Hardware Compatibility Description. 

License requirement

No specific license control item is available for the main control board working in a separateMPT 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 work in co-MPT and multimode concurrency is applied. If the UMPT/UMDU works only in 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), and UMPT Multi Mode license(LTE TDD). 


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 BBU Interconnection Feature Parameter Description in this document. You can use the GUI, summary data file, or MML commands to configure the data. For details, see 3900 Series Base Station Initial Configuration Guide. The related descriptions can be obtained by choosing Creating Base Stations > Creating Separate-MPT Multimode Base Stations. 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


Scenario


No SDR

Installing a new main

None

Issue 01 (2015-12-30)


67




Scenario


control board

Inter-BBU SDR

Installing a BBU working in a new mode

None


None


None

Installing a main control board in the secondary BBU subrack

None

Installing a BBU working in a new mode

None


If the SDR RF module needs to be upgraded, services of the original mode carried by the SDR RF module will be interrupted for about one minute.


When a cell of the new mode is established on the SDR RF module, services of the original mode will be affected for a short period of 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 1. Scenario description and application scope 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 Issue 01 (2015-12-30)


68



need to set Deployment Mode to CONCURRENT(Concurrent) before adding a mode. This modification resets the base station. 2) 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. 3. Engineering guidelines 


N/A 

Version requirement

Only versions later than SRAN8.0 support this scenario. 

License requirement

UMPT multimode license The following table provides UMPT multimode licenses that need to be purchased. License Control Item Name

License BBOM

License Abbreviatio n

Sales Unit

Mode

UMPT Multi Mode License (GSM) (per UMPT)

82204202

LGB3UMML01

Per BTS

GSM

UMPT Multi Mode License (UMTS) (per UMPT)

82203981

LQW9GUDM0 1

Per NodeB

UMTS

UMPT Multi Mode License (per UMPT) (FDD)

82204259

LLT1UMML01

Per eNodeB

LTE

UMPT Multi Mode License (per UMPT) (TDD)

82204285

LLT1TUMML0 1

Per eNodeB

LTE

All the preceding multimode licenses are required only when co-MPT multimode concurrency is used for the UMPT/UMDU. 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: Issue 01 (2015-12-30)


69



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 during configuration (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. The following table provides the related MO and parameter. MO

Param eter Name

Paramet er ID

CME Paramet er Name

Setting Notes

NODE

Working Mode

WM

Working Mode

Set this parameter to CONCURRENT(Concurrent).



Service impact

Scenario


Adding a new mode for mode expansion with co-MPT configuration

Services of the original mode are not affected.

3.4.5 Co-MPT Reconstruction and Adding a New Mode to the Co-MPT Base Station 1. Scenario description and application scope 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 Co-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. 2. Precautions 1) If the original base station is a GBTS, reconstruct the GBTS into an eGBTS by abandoning the GTMU or using GTMU evolution. 

Issue 01 (2015-12-30)

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). Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

70



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. 2) The mode to be added after the co-MPT reconstruction must be of the same version as the existing mode. 3. Engineering guidelines 


Material Type

Material Name

Quantity

Remarks

Board

UMPT

1

Prepare UMPT boards if the base station does not use UMPT boards before coMPT 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.



Version requirement

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. 

License requirement: UMPT multimode license

The following table provides UMPT multimode licenses that need to be purchased. License Control Item Name

License BBOM


Sales Unit

Mode

UMPT Multi Mode License (GSM) (per UMPT)

82204202

LGB3UMML01

per BTS

GSM


82203981

LQW9GUDM0 1

per NodeB

UMTS


82204259

LLT1UMML01

per eNodeB

LTE

Issue 01 (2015-12-30)


71



License Control Item Name

License BBOM


Sales Unit

Mode


82204285

LLT1TUMML0 1

per eNodeB

LTE

All the preceding multimode licenses are required only when co-MPT multimode concurrency is used for the UMPT/UMDU. 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 12.2 Preparing GSM Licenses. In GBSS R15.0, the control mechanism of BTS license is changed. The main change is that eGBTS controls those features quoted in BTS independently. Before enable or use these features, GTS should allocate sufficient licenses on U2000 eGBTS License Management View. Otherwise, these features cannot be enabled and CS/PS transaction may even be infected. The following table describes how to allocate license of those BTS features for each eGBTS. 1.

The Features Included by eGBTS License File But Not Supported by the eGBTS Site

Featu re ID

License Descriptio n

Sale Unit

GBTS Suppo rted

eGBTS Suppor ted

License allocating guidance for newly built eGBTS

-

High Power (per TRX)

Per TRX

Yes

No

License = 0

-

TRU which works as Multitransceivers Resource of the 3rd generation BTS (per TRX)

Per TRX

Yes

No

License = 0

-

BBU Carrier Capacity License (per TRX)

per TRX

Yes

No

License = 0

GBFD115901

PBT(Power Boost Technology)

Per TRX

Yes

No

License = 0

Issue 01 (2015-12-30)


72


Featu re ID



Sale Unit

GBTS Suppo rted

eGBTS Suppor ted


(per TRX) GBFD115902

Transmit Diversity (per TRX)

Per TRX

Yes

No

License = 0

-

BTS3900B Transceiver Resource (per TRX)

Per TRX

Yes

No

License = 0

2.

-

The Features Supported by eGBTS Site R15.0

Multi-Carrier 60 W High Power License (per TRX)

Per TRX

Yes

Yes

License = the number of activated TRXs of GBTS with GBTS Power Type (w) set in [60 W, 80 W). Related BSC MML: LST GTRXDEV

-


Per TRX

Yes

Yes

License = the number of TRXs of GBTS with GBTS Power Type (w) set in (80 W). Related BSC MML: LST GTRXDEV

-

TRU which works as Multitransceivers Resource of 3900 (per TRX)

Per TRX

Yes

Yes

Non-SubSite scene: License = the number of logical TRXs of eGBTS – the number of include GSM TRX's Boards. SubSite scene(Supported begin eGBTS R16.0): (1) International and China Unicom: License = the number of logical TRXs of eGBTS * the number of location groups – the number of RXUs from all location groups. (2) China Mobile: License = the number of logical TRXs of eGBTS – the number of RXUs from the most RXUs location

Issue 01 (2015-12-30)


73



group. Related BSC MML: LST GTRX; LST BTSLOCGRPE; Related eGBTS MML: LST GTRXGROUPSECTOREQ M LST SECTOREQM MRFD211801

Multi-mode Dynamic Power Sharing(GSM) (per Site)

Per Site

Yes

Yes

license = 1 if eGBTS's Power Sharing Type set to GUPWRSHR (GU Power Sharing). Related eGBTS MML: LST GBTSPWRSHRGRP;

MRFD211703

2.0 MHz Central Frequency point separation between GSM and UMTS mode(GSM) (per Site)

Per Site

Yes

Yes

The license of this feature is not checked in BTS. When manually allocating the license to eGBTS, GTS should contact the Huawei salesman and allocate 1 license for each eGBTS for which the customer has bought this feature.

MRFD211804

GSM Power Control on Interference Frequency for GU Small Frequency gap(GSM) (per Site)

per BTS

Yes

Yes

License = 1 if at least one cell of the eGBTS set Frequency-based Power Control to ON.

MRFD211505

Bandwidth sharing of MBTS Multimode CoTransmission( GBTS) (per Site)

Per Site

Yes

Yes


MRFD211602

Multi-mode BS Common IPSec(GSM) (per Site)

per BTS

Yes

Yes

The license of this feature is not checked in BTS. When manually allocating the license to eGBTS, GTS should contact the Huawei salesman and allocate 1 license for each eGBTS for

Issue 01 (2015-12-30)

Related eGBTS MML: LST GLOCELLALGPARA


74



which the customer has bought this feature. MRFD211802

MRFD211803

GSM and UMTS Dynamic Spectrum Sharing(GSM) (per Site)

per BTS

Dynamic MA for GU Dynamic Spectrum Sharing(GSM) (per Site)

per BTS

Yes

Yes

License = 1 if Spectrum Sharing Allowed of eGBTS set to YES. Related BSC MML: LST GDSSPARA

Yes

Yes

License = 1 if in a eGBTS, at least one channel's FH Index Used After Frequency Spectrum Sharing set to value in range [0,63]. Related BSC MML: LST GTRXCHANHOP;

MRFD211806

GSM and LTE Dynamic Power Sharing(GSM) (per Site)

Per BTS

Yes

Yes

license = 1 if eGBTS's Power Sharing Type set to GLPWRSHR (GL Power Sharing). Related eGBTS MML: LST GBTSPWRSHRGRP;

MRFD211901

Multi-RAT Carrier Joint Shutdown(GB TS) (per Site)

Per BTS

Yes

Yes

License = 1 if in the eGBTS, at least one cell's Inter -RAT Cell Dynamic Shutdown set to ON. Related BSC MML: LST GCELLSOFT

GBFD116602

IPSec Bypass (per Site)

Per BTS

No

Yes

License = 1 If eGBTS need to open this feature by set IPSec Bypass Switch to ENABLE. Related eGBTS MML: LST IPSECBYPASSCFG

-

UMPT MultiMode License(GSM) (per UMPT)

Per UMPT

No

Yes

1. license = 0 for each eGBTS if in GO scenario building eGBTS. 2. license = 0 for each eGBTS if building multiRAT (with G) co-MPT SRAN BTS (GU/GL/GUL). 3. license = 1 for each eGBTS when expanding GRAT for multi-RAT (without G) co-MPT SRAN BTS (such as UL->GUL).

Issue 01 (2015-12-30)


75


-


Antenna Intermodulatio n Performance Detection (per TRX)

Per TRX

Yes

Yes

The license check of this feature is triggered by related maintaining MML. If this feature is needed, license = the number of activated logical TRXs of each eGBTS. Related eGBTS MML: STR RFTEST; STR GBTSRFTST

-

Extended Spectrum Scan (per TRX)

Per TRX

Yes

Yes

The license check of this feature is triggered by related eGBTS LMT GUI maintaining function. If this feature is needed, license = the number of activated logical TRXs of each eGBTS. Related eGBTS LMT GUI maintenance function: Offline spectrum scan monitoring

3.


Feature ID

License Descripti on

Sal e Uni t

GBTS Supp orted

eGBTS Suppor ted


GBFD151202

BTS IP Active Performance Measuremen t (per Site)

Per BTS

No

Yes

license = 1 if eGBTS's TWAMPCLIENT or TWAMPRESPONDER function is enabled. Related BTS MML: LST TWAMPCLIENT LST TWAMPRESPONDER

4.

Issue 01 (2015-12-30)



76



Featu re ID


Sale Unit

GB TS Su pp ort ed

eG BT S Su pp ort ed


-

SubSite Solution License (per Module)

Per Module

Yes

Yes

License = the number of RXUs which belong to the eGBTS location group – the number of RXUs which belong to the location group which has the most RXUs. Related BSC MML: LST BTSLOCGRPE Related BTS MML: LST SECTOR LST RRU

-

RFU co-cell Solution License (per Module)

Per Module

Yes

Yes

License = the number of RFUs which belong to the eGBTS location group Related BSC MML: LST BTSLOCGRPE Related BTS MML: LST SECTOR LST RRU

GBFD115903

4-Way Receiver Diversity (per TRX)

Per TRX

Yes

Yes

License = the number of TRXs which is configured 4-Way Receiver Diversity. Related BSC MML: LST GTRX Related BTS MML: LST GTRXGROUP

-

GBFD160209

GBFD160210

Issue 01 (2015-12-30)

UBBP MultiMode license (GSM) (Per Module)

Per Module

IPSec redundancy among multiSeGWs (per BTS)

Per BTS

BTS supporting PKI redundancy

Per BTS

Yes

Yes

License = the number of GBTSBBRES Related BTS MML: LST GBTSBBRES

No

Yes

license = 1 if eGBTS's IPSec redundancy function is enabled. Related BTS MML: LST IKEPEER

No

Yes


license = 1 if eGBTS's PKI redundancy function is enabled. Related BTS MML:

77


Featu re ID



Sale Unit

GB TS Su pp ort ed


(per BTS)


LST CA LST CRLTSK

MRFD261103

AAS RAT Specific Tilting (GSM) (Per RU)

Per RU

No

Yes

The license of this feature is not checked in BTS. When manually allocating the license to eGBTS, GTS should contact the Huawei salesman and allocate the number of licenses which equals the number of AASs which the customer has bought.

Not Commer cial

AAS Virtual Four Uplink Channels for GSM (per RU)

Per RU

No

Yes

License = the number of AARUs whose four virtual ports are used as the receiving channel by GTRXGROUP. Related BTS MML: LST GTRXGROUP LST GTRXGROUPSECTOREQM LST AARU

5.


Featu re ID


Sale Unit

GB TS Su pp ort ed

eG BTS Sup por ted


GBFD170205

GTMUb SingleOM (Per BTS)

per BTS

No

Yes

license = 1 if the GTMUb functions as the main control board of the eGBTS. Ralated eGBTS MML: DSP BRDMFRINFO

6.

Issue 01 (2015-12-30)



78



Featur e ID


Sale Unit

GB TS Sup por ted



GBFD171205

BTS Supporting Multi-Carrier PKI (per BTS)

per BTS

No

Yes

license = 1 if eGBTS's configuration MPT is GTMU.

GBFD171206

BTS Supporting IPSec Redirection (per BTS)

per BTS

No

Yes

The license of this feature is not checked in BTS. When manually allocating the license to eGBTS, GTS should contact the Huawei salesman and allocate 1 license to the base station which the customer has bought.

-

Multi-Mode Multi-Band License for Multi-Band RF Module (GSM) (Per Band per RRU)

per Band per RRU

Yes

Yes

Calculate the number of all the frequency bands used by multi-band RRU in all the GSM cells.

Related BTS MML: DSP BRD

Related BTS MML: LST GTRX Related BTS MML: LST GTRXGROUPSECTOREQM LST SECTOREQM

7.


Featur e ID


Sale Unit

GBT S Sup por ted



GBFD181202

BTS Supporting Digital Certificate Whitelist Management (Per BTS)

per BTS

No

Yes

license = 1 if eGBTS is opened the switch of IKECHECKSW.



Issue 01 (2015-12-30)

Related BTS MML: LST CERTCFG



79



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 during configuration (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. The following table provides the related MO and parameter. MO

Param eter Name

Paramet er ID

CME Paramet er Name

Setting Notes

NODE

Working Mode

WM

Working Mode

Set this parameter to CONCURRENT(Concurrent).

1. Filling in the data planning tables for co-MPT reconstruction



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. 

Issue 01 (2015-12-30)

Fill in the following fields when GSM mode is involved: a.

BscSctpIdBase must be configured, making different base stations controlled by one base station controller use different values.

b.

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.

c.

BtsOMCHPeerIP: Enter the IP address of the U2000. This field is mandatory for GO reconstruction and batch reconstruction scenarios.

d.

BtsOMCHPeerIPMask: Enter the IP mask of the U2000. This field is mandatory for GO reconstruction and batch reconstruction scenarios. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

80





e.

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.

f.

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.

g.

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.

h.

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.

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 hybridMPT 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 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. 

Issue 01 (2015-12-30)

ScenarioId: It is a reserved parameter and used for future expansion. It does not need to be specified.


81





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 hybridMPT 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-cotransmission or co-transmission based on panel interconnection is used, enter the nexthop IP address on the GSM side and the IP address must be on the same network 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.)



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 upperlevel 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 > IPCLK > SYNCETH > LINECLK > TOD > BITS > SYNCETH+IPCLK. 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.)

Issue 01 (2015-12-30)


82



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. The adjustment mode must be entered 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.



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 the MML reference of 3900 Series Base Station MML reference: ADD CPBEARER ADD SCTPLNK ADD ACL ADD ACLRULE ADD IPSECPOLICY ADD IKEPEER ADD SECURITYPEER ADD SCTPPEER

Issue 01 (2015-12-30)


83







UmptBrdspec indicates the type of a UMPT after reconstruction and its default value is UMPTa or UMPTb. Fill this field according to the actual situation. Otherwise, the configurations cannot take effect after reconstruction because the UMPTa/b and UMPTe support different cell specifications.



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.



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 method of manual configuration, see 3900 Series Base Station Initial Configuration Guide > Configuring Transport Data About the Co-MPT Base Station in 3900 Series Base Station Product Documentation.

Issue 01 (2015-12-30)


84



(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.

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 Issue 01 (2015-12-30)


85



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 multiplexing.

(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.

The adjustment mode must be entered 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

Issue 01 (2015-12-30)


86



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 yes, 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<E 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

Scenario


Adding a new mode for mode expansion with co-MPT configuration


Co-MPT reconstruction

Services of the original mode are interrupted.

Issue 01 (2015-12-30)


87



3.5 BBU Interconnection This section describes BBU interconnection planning.

3.5.1 Overall BBU Interconnection Planning Process Figure 1.1 Overall BBU interconnection planning process

Table 1.1 Comparison between interconnection through UCIU+UMPT and interconnection through UMPT+UMPT Comparis on Item

Interconnection Through UCIU+UMPT

Interconnection Through UMPT+UMPT

BBU hardware requirement

Only BBU3900s can be interconnected through UCIU+UMPT.

The following BBU combination is supported:

The BBU3910 does not support BBU interconnection through UCIU+UMPT.

BBU3900+BBU3910

The BBU3910A does not support BBU interconnection

The BBU3910A does not support BBU interconnection.

The length of cables for BBU

The length of cables for BBU

Requirement Issue 01 (2015-12-30)

BBU3900+BBU3900 BBU3910+BBU3910


88



Comparis on Item

Interconnection Through UCIU+UMPT

Interconnection Through UMPT+UMPT

for distance between BBUs

interconnection can be 2 meters or 10 meters.

interconnection can be 2 meters or 5 meters. BBUs cannot be installed over five meters apart.

Hardware requirement for the main control board

Primary BBU subrack: No special requirements are imposed on the main control board.

Primary BBU subrack: Only the UMPT can be configured.

Secondary BBU subrack: Only the UMPT can be configured.

Secondary BBU subrack: Only the UMPTb or UMTP of a later version 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 Limitations

The root BBU supports UMPT cold backup.

UMPT cold backup is not supported.

In single-mode or co-MPT and inter-subrack scenarios, a transmission port must be provided by a transmission board in the primary BBU subrack.

A transmission port must be provided by a transmission board in the primary BBU subrack.

RRUs connected to the secondary BBU subrack can be cascaded.

If a GTMU, WMPT, or LMPT is configured in the primary BBU subrack, 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 1.2 Scenario analysis of BBU interconnection Category

Scenario

BBU interconnection

Adding a BBU for BBU interconnection through UCIU+UMPT

Issue 01 (2015-12-30)

Adding a BBU for BBU interconnection through UMPT+UMPT


89



3.5.2 Adding a BBU for BBU Interconnection Through UCIU+UMPT Figure 1.1 BBU interconnection through UCIU+UMPT

1. Scenario description and application scope BBU interconnection applies to a separate-MPT triple-mode GUL base station or a separateMPT 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 3. Engineering guidelines 


BBU interconnection through UCIU+UMPT is supported from SRAN7.0 onwards. For the mapping relationship between the UMPTs and versions, see 3900 Series Base Station Software and Hardware Compatibility Description. 

Issue 01 (2015-12-30)

License requirement Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

90



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 1.1 MOC Domai n


MOC

Para mete r ID

Para mete r Name

Value (Example )

CME Type

BBU intercon nection

Mode in the root BBU

CTRLLNK

LN

Local Link No.

0

Equipment


All modes in the root

CTRLLNK

CN

Local Cabinet No.

0

Equipment

Issue 01 (2015-12-30)


91


Domai n



MOC

Para mete r ID

Para mete r Name

Value (Example )

CME Type

BBU BBU intercon nection

All modes in the root BBU

CTRLLNK

SRN

Local Subrack No.

1

Equipment



CTRLLNK

SN

Local Slot No.

7

Equipment



CTRLLNK

UPCN

Upper Cabinet No.

0

Equipment



CTRLLNK

UPSRN

Upper Subrack No.

0

Equipment



CTRLLNK

UPSN

Upper Slot No.

4

Equipment



CTRLLNK

UPPT

Upper Port No.

0

Equipment



CTRLLNK

LN

Local Link No.

0

Equipment



CTRLLNK

CN

Local Cabinet No.

0

Equipment



CTRLLNK

SRN

Local Subrack No.

1

Equipment



CTRLLNK

SN

Local Slot No.

7

Equipment

BBU

All

CTRLLNK

UPCN

Upper

0

Equipment

Issue 01 (2015-12-30)


92



Domai n


intercon nection

modes in the root BBU



CTRLLNK

UPSRN



CTRLLNK



CTRLLNK



MOC

Para mete r ID

Para mete r Name

Value (Example )

CME Type

Upper Subrack No.

0

Equipment

UPSN

Upper Slot No.

4

Equipment

UPPT

Upper Port No.

0

Equipment

Cabinet No.

Service impact

Scenario


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 document

BBU Interconnection Feature Parameter Description

Issue 01 (2015-12-30)


93



3.5.3 Adding a BBU for BBU Interconnection Through UMPT+UMPT Figure 1.1 BBU interconnection through UMPT+UMPT

1. Scenario description and application scope BBU interconnection applies to a separate-MPT triple-mode GUL base station or a separateMPT 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 3. Engineering guidelines 

Version requirement

BBU interconnection through UMPT+UMPT is supported from SRAN8.1 onwards. For the mapping relationship between the UMPTs and versions, see 3900 Series Base Station Software and Hardware Compatibility Description. 

Material requirement (hardware) 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.

Issue 01 (2015-12-30)


94



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. 

License requirement 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 1.1 MOC Domai n


MOC

Para mete r ID

Para mete r Name

Value (Example )

CME Type



CTRLLNK

LN

Local Link No.

0

Equipment



CTRLLNK

CN

Local Cabinet No.

0

Equipment



CTRLLNK

SRN

Local Subrack No.

1

Equipment



CTRLLNK

SN

Local Slot No.

7

Equipment

Issue 01 (2015-12-30)


95



Domai n


MOC

Para mete r ID

Para mete r Name

Value (Example )

CME Type



CTRLLNK

UPCN

Upper Cabinet No.

0

Equipment



CTRLLNK

UPSRN

Upper Subrack No.

0

Equipment



CTRLLNK

UPSN

Upper Slot No.

7

Equipment



CTRLLNK

UPPT

Upper Port No.

8

Equipment


Mode in the leaf BBU

CTRLLNK

LN

Local Link No.

0

Equipment



CTRLLNK

CN

Local Cabinet No.

0

Equipment



CTRLLNK

SRN

Local Subrack No.

1

Equipment



CTRLLNK

SN

Local Slot No.

7

Equipment



CTRLLNK

UPCN

Upper Cabinet No.

0

Equipment



CTRLLNK

UPSRN

Upper Subrack No.

0

Equipment



CTRLLNK

UPSN

Upper Slot No.

7

Equipment



CTRLLNK

UPPT

Upper Port No.

8

Equipment



Issue 01 (2015-12-30)

Service impact


96



Scenario


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 document

BBU Interconnection Feature Parameter Description

3.6 Clock Planning This section describes co-MPT or separate-MPT planning.

3.6.1 Overall Clock Planning Process Figure 1.1 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. 

Issue 01 (2015-12-30)

Check whether the new mode can reuse the original clock.


97



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

Compa rison Item

Independent Clock

Common Clock

Clock type

GPS clock, BITS clock, E1/T1 clock, IEEE1588v2 clock, synchronous Ethernet clock, and 1PPS+TOD clock

GPS clock, BITS clock, E1/T1 clock, IEEE1588v2 clock, and synchronous Ethernet clock.

Working mode

The working mode of the clock in a multimode base station cannot be set to 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-RAT decouplin g

Loose coupling: The inter-RAT external clock source works independently.

Loose coupling: Inter-RAT impact is small or none. If a base station fails to obtain clock signals, it works in free-run mode for a certain period of time. The period can be as long as three months if frequency synchronization is used.

Customer Requirem ents

An independent clock source is configured for the new mode 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.

No additional clock source requirement is posed by 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 to FDD+TDD (Adding the USCU clock board or other ways to obtain 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:

Issue 01 (2015-12-30)


98





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 1.1 Mode transition scenario analysis Category

Scenario

Clock

New mode using an independent reference clock with separate-MPT configuration New mode and original mode sharing clock source with separate-MPT configuration New 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 1. Scenario description and application scope In this scenario, a new mode uses an independent reference clock. 2. Precautions None 3. Engineering guidelines 







Data configuration requirement 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



Related document Synchronization Feature Parameter Description for GSM Synchronization Feature Parameter Description for UMTS Synchronization Feature Parameter Description for LTE FDD Synchronization Feature Parameter Description for LTE TDD

Issue 01 (2015-12-30)


99



3.6.3 New Mode and Original Mode Sharing Reference Clock with Separate-MPT Configuration 1. Scenario description and application scope Based on the preceding analysis, co-transmission is required. 2. Precautions None 3. Engineering guidelines 

Version requirement The version requirement of clock sharing varies with the reference clock. For details, see Common Clock Feature Parameter Description.



License requirement



License BBOM


Sales Unit

Mode

Multi-mode BS Common Reference Clock(GBT S)

None

None

None

per BTS

G

Multi-mode BS Common Reference Clock(Node B)

None

None

None

per NodeB

U

Multi-mode BS Common Reference Clock(eNod eB)

Multi-mode BS Common Reference Clock(eNod eB)(Per eNodeB)

88030QUW

LLT1MCRC 01

Per eNodeB

L




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

Issue 01 (2015-12-30)


100



MO

Param eter Name

Paramet er ID

CME Paramet er Name

Setting Notes

BTSCLK

Clock Type

ClkType

Clock Type

PEER_CLK

BTSCLK

Peer Mode

STANDAR D

Peer Mode

Set this parameter to the mode of the reference clock.

eGBTS, NodeB, eNodeB, or co-MPT multimode base station MO

Param eter Name

Paramet er ID

CME Paramet er Name

Setting Notes

CLKMO DE

Clock Working Mode

MODE

Clock Working Mode

Set this parameter to MANUAL(Manual).

CLKMO DE

Selected Clock Source

CLKSRC


Set this parameter to PEERCLK(Peer Clock).

PEERCL K

Peer Clock No.

PN

Peer Clock No

Set this parameter to 0.

PEERCL K

Peer Standard

PS

Peer Standard




Service impact

None 

Related document

Common Clock Feature Parameter Description

3.6.4 New Mode Requiring Modification to the Clock Source with Co-MPT Configuration 1. Scenario description and application scope 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 3. Engineering guidelines Issue 01 (2015-12-30)


101



Version requirement The reference clock of the new mode has requirements on the version. For details, see the following documents: Synchronization Feature Parameter Description for GSM Synchronization Feature Parameter Description for UMTS Synchronization Feature Parameter Description for LTE FDD Synchronization Feature Parameter Description for LTE TDD



License requirement

Do ma in

Feature Name


Licens e Contro l Item Name (BBOM )

License Abbrev iation

Sales Unit

Mode

Clo ck

Synchroniza tion with GPS

Synchronizati on with GPS

None

None

Per eNodeB

L

Clo ck

IEEE1588 V2 Clock Synchroniza tion

IEEE1588 V2 Clock Synchronizati on

LT1S00E NSY00

88030FK K

Per eNodeB

L



Data configuration requirement 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: Synchronization Feature Parameter Description for GSM Synchronization Feature Parameter Description for UMTS Synchronization Feature Parameter Description for LTE FDD Synchronization Feature Parameter Description for LTE TDD

Do mai n


MOC

Para mete r Name

Paramet er ID

Value (Example )

CME Type

Cloc k

New-mode base station

GPS

GPS Clock No.

GN

0

Equipment


GPS

Cable Length

CABLE_L EN

30

Equipment


GPS

GPS workin g mode

MODE

GPS

Equipment


GPS

Priority

PRI

1

Equipment

Issue 01 (2015-12-30)


102


Do mai n





MOC

Para mete r Name

Paramet er ID

Value (Example )

CME Type


IPCLK LNK

Link No.

LN

0

Equipment


IPCLK LNK

Client IPv4

CIP

82.0.1.107

Equipment


IPCLK LNK

Server IPv4

SIP

82.0.1.128

Equipment


IPCLK LNK

Domain

DM

0

Equipment


IPCLK LNK

Priority

PRI

1

Equipment


TASM

Clock Workin g Mode

MODE

MANUAL

Equipment


TASM

Selecte d Clock Source

CLKSRC

GPS

Equipment


TASM

Clock Source No.

SRCNO

0

Equipment


TASM

Clock Synchr onizatio n Mode

CLKSYNC MODE

TIME

Equipment

Service impact None



Related document Synchronization Feature Parameter Description for GSM Synchronization Feature Parameter Description for UMTS Synchronization Feature Parameter Description for LTE FDD Synchronization Feature Parameter Description for LTE TDD

3.7 Baseband Planning This section describes baseband planning.

Issue 01 (2015-12-30)


103



3.7.1 Overall Baseband Planning Process Figure 1.1 Overall baseband planning process



Comparison between co-baseband and independent baseband

Compariso n Item

Independent Baseband

Co-Baseband

Working mode

Single mode

Multimode concurrency

Hardware

All baseband processing boards support independent baseband.

Only the UBBP or UMDU supports co-baseband.

There are no special requirements for co-MPT configuration.

Co-MPT must be configured for cobaseband application. For hybrid-MPT scenarios, co-MPT must be configured for modes involved in co-baseband.

Inter-RAT decoupling

Baseband processing boards of each mode work independently. Baseband boards of each mode are loosely coupled. With CPRI MUX, IQ signals are exchanged through the BBU backplane.

Issue 01 (2015-12-30)


Baseband boards of each mode are tightly coupled. If one baseband processing board is faulty, the other processing baseband becomes faulty, too.

104



Table 1.1 Mode transition scenario analysis Categor y


Scenario

Baseband planning

Separate-MPT

Adding an independent baseband processing board to the new mode with separate-MPT configuration

Co-MPT mode expansion

Adding an independent baseband processing board to the new mode with co-MPT configuration Adding a new mode to the original baseband processing board with co-MPT configuration

3.7.2 Adding an Independent Baseband Board to the New Mode with Separate-MPT Configuration 1. Scenario description and application scope In a separate-MPT base station, an independent baseband board is added to the new mode for mode transition. The BBU3910A does not support mode transition when separate-MPT is used and therefore does not support this scenario. For details about selection of baseband processing boards, see GUL Base Station Overview and Selection Guide. 2. Precautions 1) 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. 2) The preceding constraint does not apply to the BBU3910 because it has a higher backplane switching capability. 3) 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. 3. Engineering guidelines 


Material Type

Material Name

Quantity

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

Issue 01 (2015-12-30)


Remarks

105



Material Type

Material Name

Quantity

Remarks

number of CEs UBRIb



The UBRI must be configured if it provides CPRI ports for the GSM mode.

Version requirement


License requirement

No specific license control item is available for the baseband processing 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. Mode licenses related to the UBBP must be purchased and delivered even when co-baseband is not used. Mode



License BBOM


GSM

UBBP First-Mode license (GSM)

UBBP Multi-Mode license (GSM)

82204551

LGMIUBB P



82204551

LGMIUBB P

UBBP First-Mode license (UMTS)

UBBP Multi-Mode license (UMTS)

82204657

LQW9UBP DM01



82204657

LQW9UBP DM01

UBBP First-Mode license (LTE FDD)

NA

88032BXR

WDMS0UF MLF00

UBBP Multi-Mode license (LTE FDD)

NA

UBBP First-Mode license (LTE TDD)

NA

UBBP Multi-Mode license (LTE TDD)

NA

UMTS

LTE

Issue 01 (2015-12-30)

(SBOM) 88032BXS (SBOM) 88032KLF (SBOM)


88032GDN (SBOM)

WDMS0U MMLF00 LT1SUMM LFL01 LT1SUMM LFL00

106



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 1. Scenario description and application scope 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 selection of baseband processing boards, see GUL Base Station Overview and Selection Guide. 2. Precautions 1) 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. 2) The preceding constraint does not apply to the BBU3910 because it has a higher backplane switching capability. 3) 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. 3. Engineering guidelines 


Material Type

Material Name

Quantity

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

Issue 01 (2015-12-30)


Remarks

107



Material Type

Material Name

Quantity

Remarks

provides CPRI ports for the GSM mode.



Version requirement


License requirement

No specific license control item is available for the baseband processing 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. Mode licenses related to the UBBP must be purchased and delivered even when co-baseband is not used. Mode



License BBOM


GSM



82204551

LGMIUBB P



82204551

LGMIUBB P



82204657

LQW9UBP DM01



82204657

LQW9UBP DM01


NA

88032BXR

WDMS0UF MLF00


NA


NA


NA

UMTS

LTE

(SBOM) 88032BXS (SBOM) 88032KLF (SBOM) 88032GDN (SBOM)


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. 

Issue 01 (2015-12-30)

Data configuration requirement Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

108



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. MO

Param eter Name

Paramet er ID

CME Paramet er Name

Setting Notes

BBP

Base Band Work Standard

BBWS


Determined by the UBBP configuration plan

MDU


BBWS


Determined by the mode planned for the UMDU



Service impact

None

3.7.4 Adding a New Mode to the Original Baseband Processing Board with Co-MPT Configuration 1. Scenario description and application scope 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 by referring to GUL Base Station Overview and Selection 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. 3. Engineering guidelines 

Material requirement 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.



Version requirement For the mapping relationship between the baseband processing boards and versions, see 3900 Series Base Station Software and Hardware Compatibility Description.



License requirement A license related to the new mode can be applied for in the same way as that for the license of each involved mode. The following table lists licenses that need to be purchased and delivered for the UBBP board.

Issue 01 (2015-12-30)


109



Mode



License BBOM


GSM



82204551

LGMIUBB P



82204551

LGMIUBB P



82204657

LQW9UBP DM01



82204657

LQW9UBP DM01


NA

88032BXR

WDMS0UF MLF00


NA


NA


NA

UMTS

LTE



(SBOM) 88032BXS (SBOM) 88032KLF (SBOM) 88032GDN (SBOM)


Data configuration requirement Baseband working mode must be configured for the UBBP board.

MO

Param eter Name

Paramet er ID

CME Paramet er Name

Setting Notes

BBP


BBWS


Determined by the UBBP configuration plan

MDU


BBWS


Determined by the mode planned for the UMDU



Service impact

Scenario


Modify the baseband working mode.

Services carried by the baseband processing board are interrupted for one minute.

Issue 01 (2015-12-30)


110



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.

3.8.1 Overall CPRI-based Topology Planning Figure 1.1 Overall CPRI-based topology planning process

Table 1.1 Mode transition scenario analysis Categ ory

Scenario

CPRIbased topology

Chain topology for RF modules Dual-star topology (load sharing) for SDR RF modules CPRI 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. Compa rison Item

Dual-Star Topology

CPRI MUX

Service impact

If CPRI fiber optical cables are installed on a tower and antennas and RRUs are installed for the

Replace the original baseband processing board because it does not support convergence, which interrupts

Issue 01 (2015-12-30)


111


Compa rison Item


Dual-Star Topology

CPRI MUX

new mode, existing services need to be interrupted to ensure personnel safety.

services. Optical modules of a higher data rate may be required to provide more bandwidth for supporting services of two modes. The optical module replacement interrupts services.

Material cost

N pairs of CPRI fiber optic cables and 2N optical modules. N varies with RF modules required for the new mode.

(Possible) 2N high-speed optical modules. The replaced optical modules can be reused for other purposes.

Labor Cost

Cost for hoisting (if applicable), installing N pairs of CPRI fiber optic cables (high), and installing optical modules

Cost for hoisting (if applicable) and replacing optical modules

Reliability

Services between different modes are not affected.

The converging party affects the converged party.

Applicatio n condition

The dual-star topology is supported by the following hardware: GTMUa/GTMUb/GTMUc, WBBPb/WBBPd/WBBPf, LBBPc/LBBPd, UBBPd, UBRIa/UBRIb, and V1/2/3 RF modules.

CPRI MUX is supported only by the WBBPf, LBBPd, UBBPd, and GTMUb/GTMUc (only being the converged party). Whether an RF module supports CPRI MUX depends on the actual RF module's capabilities as promoted by Huawei. Inter-BBU CPRI MUX is not supported.

3.8.2 Chain Topology for RF Modules 1. Scenario description and application scope 

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

Issue 01 (2015-12-30)


112



2. Precautions 1) 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. 2) 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. 3) 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. 4) 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. 3. Engineering guidelines 


Material Type

Material Name

Quantity

Remarks

CPRI-based topology

CPRI electrical cable

Same as the number of RRUs or RFUs. Each RFU requires one CPRI electrical cable.

Two ends of the CPRI electrical cable are connected to the RFU and BBU, respectively.


Same as the number of RRUs. Each RRU requires one CPRI fiber optic cable.

Two ends of the CPRI fiber optic cable are connected to the RRU and BBU, respectively.

CPRI optical module

Twice the number of RRUs or RFUs. Each RRU or RFU requires one CPRI cable and each of the CPRI cables must be configured with two optical modules.

Two ends of the CPRI cable are connected to the RRU and BBU, respectively.




None 

License requirement

None 


No special requirements are involved. The following table provides the related MOs.

Issue 01 (2015-12-30)


113



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 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 located. Value NULL is displayed for the RRU chain which does not have a tail CPRI port.

Tail Slot No.

Indicates the slot 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 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 Position1

Indicates the breakpoint position 1 on the chain/ring. When this 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

Issue 01 (2015-12-30)


114



MO Parameter

Meaning 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. 1.25: auto-negotiation mode is not supported and the CPRI rate is 1.25 Gbit/s. 2.5: auto-negotiation mode is not supported and the CPRI rate is 2.5 Gbit/s. 4.9: auto-negotiation mode is not supported and the CPRI rate is 4.9 Gbit/s. 6.1: auto-negotiation mode is not supported and the CPRI rate is 6.1 Gbit/s. 9.8: auto-negotiation mode is not supported and the CPRI rate is 9.8 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 1. Scenario description and application scope 

New RF modules work in multiple modes or the single mode of original RF modules is expanded to multiple modes.




Issue 01 (2015-12-30)


115





Limitation on RF modules: The RF module must be multimode RF modules (of M series).



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. 3. Engineering guidelines 

Material requirement 1) Expanding the mode of the original RF module to multiple modes

Material Type

Material Name

Quantity

Remarks

CPRI-based topology





Same as the number of RRUs. Each RRU requires one CPRI fiber optic cable.


Issue 01 (2015-12-30)


116


Material Type


Material Name

Quantity

Remarks

CPRI optical module



2) Adding a new RF module working in multiple modes Material Type

Material Name

Quantity

Remarks

CPRI-based topology


Twice the number of RRUs or RFUs. Each RFU requires two CPRI electrical cables.



Twice the number of RRUs. Each RRU requires two CPRI fiber optic cables.


CPRI optical module

Four times the number of the RRUs or RFUs Each RRU or RFU requires one CPRI cable and each of the CPRI cables must be configured with two optical modules.




Software version requirement Load sharing in co-MPT scenarios: SRAN8.0 and later






Data configuration requirement 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.

MO Parameter

Meaning

Chain No.

Indicates the ID of the RRU chain. It uniquely identifies a chain within

Issue 01 (2015-12-30)


117


MO Parameter


Meaning 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 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 located. Value NULL is displayed for the RRU chain which does not have a tail CPRI port.

Tail Slot No.

Indicates the slot 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 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

Issue 01 (2015-12-30)


118



MO Parameter

Meaning 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. 1.25: auto-negotiation mode is not supported and the CPRI rate is 1.25 Gbit/s. 2.5: auto-negotiation mode is not supported and the CPRI rate is 2.5 Gbit/s. 4.9: auto-negotiation mode is not supported and the CPRI rate is 4.9 Gbit/s. 6.1: auto-negotiation mode is not supported and the CPRI rate is 6.1 Gbit/s. 9.8: auto-negotiation mode is not supported and the CPRI rate is 9.8 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.4 CPRI MUX for SDR RF Modules 1. Scenario description and application scope 

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).



Issue 01 (2015-12-30)



119





Limitations: Restriction on service specifications: The maximum service specifications of CPRI MUX are less that 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 CPRI MUX Feature Parameter Description. 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 CPRI MUX Feature Parameter Description.

2. Precautions 1) 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. 2) 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. 3. Engineering guidelines 

Material requirement 1) If the mode of the original RXU is to expanded to multiple modes, no additional RXU is required. 2) A new RF module is added to serve multiple modes.

Material Type

Material Name

Quantity

Remarks

Auxiliary materials





Same as the number of RRUs. Each RRU requires one CPRI fiber optic

Two ends of the CPRI fiber optic

Issue 01 (2015-12-30)


120


Material Type


Material Name

CPRI optical module



Quantity

Remarks

cable.

cable are connected to the RRU and BBU, respectively.



Software version requirement CPRI MUX in separate-MPT scenarios: SRAN7.1






Data configuration requirement 1) 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. 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 PEERPORT(peer port).

Engineering design

Head Cabinet No.

HCN

Engineering design

Head Subrack No.

HSRN

Head Slot No.

HSN

Head Port No.

HPN

Set these parameters to the cabinet number, subrack number, slot number, and optical port number of the CPRI port on the baseband processing board of the peer end, respectively.

Local Slot No.

LSN

Issue 01 (2015-12-30)



For BBU3910s used in separateMPT GU or GL CPRI MUX and BBU3900s, the slot number does not need to be configured for the converged party. In this


Engineering design Engineering design Engineering design

Equipment plan

121



Parameter Name

Parameter ID

Setting Notes

Data Source

case, set this parameter to 255. 

For BBU3910s used in separateMPT scenarios with UL CPRI MUX, set this parameter to the slot number of board used by the converged party.

2) 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. 

Service impact

Scenario


Original mode as the converging party and no modification to the slot of the original baseband processing board


Original mode as the converging party and adjusting the slot or the original baseband processing board

Services carried by the baseband processing board of the original mode are affected. In addition, services are affected during the period from the adjustment of baseband board slot to the configuration completion of the original mode's data.

New mode as the converging party

Connect the original CPRI cable to an RF module of the 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.

Issue 01 (2015-12-30)


122



3.9.1 Transmission Networking Planning Process Figure 1.1 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 Item

Independent Transmission

Co-transmission

Port requirement for transmission devices

An independent transmission port must be configured for each mode.

Multiple modes share a transmission port.

IP addresses requirement

For each mode, the port IP address, O&M IP address, service IP address, and signaling IP address must be planned.

For each mode, the port IP address, O&M IP address, service IP address, and signaling IP address must be planned.

The service IP address is the same as the signaling IP address, and can be the same as or different from the O&M IP address.

The service IP address is the same as the signaling IP address, and can be the same as or different from the O&M IP address.

The service IP address or signaling IP address can be the same as the port IP address.

The service IP address or signaling IP address can be the same as the port IP address.

The O&M IP address can be the same as the port IP address.

The O&M IP address can be the same as the port IP address.

(minimum)

Issue 01 (2015-12-30)


123



Comparison Item

Independent Transmission

Co-transmission 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 bandwidth sharing

No sharing

Sharing

Co-IPsec/PKI

No sharing

Sharing is supported.

Reliability

All the modes are independent from each other.

A reset or fault on the main control board that provides a transmission port for co-transmission affects other modes. The mode that provides a transmission port for cotransmission 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. Table 1.1 Mode transition scenario analysis Categor y


Scenario

Transmissio n

Separate-MPT

New mode using independent transmission with separateMPT configuration New mode using the transmission port provided by the original mode with separate-MPT configuration New mode providing a transmission port shared by the original mode with separate-MPT configuration

Co-MPT mode Issue 01 (2015-12-30)

Co-transmission for new and original modes with co-


124


Categor y



Scenario

expansion

MPT configuration

3.9.2 New Mode Using Independent Transmission with Separate-MPT Configuration 1. Scenario description and application scope 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 3. Engineering guidelines 

Material requirement 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.

Material Type

Material Name

Quantity

Transmissio n

E1/T1 electrical cable

One, including four E1/T1 channels.

FE/GE electrical cable

One

FE/GE fiber

One

Issue 01 (2015-12-30)


Remarks

125


Material Type


Material Name

Quantity

Remarks

optic cable FE/GE optical module



One

Software version requirement None



License requirement Purchase the related license if the transmission type used by the new mode has license requirements.




The following table provides the related MOCs. Domain

Configuratio n Object

MOC

Parameter Name

CME Type

Transmission

New-mode main control board

E1T1

Transmis sion


ETHPORT


PPPLNK

For details, see section "Configuring Transport Data" in 3900 Series Base Station Initial Configuration Guide.


MPGRP

Transmis sion


MPLNK

Transmis sion


DEVIP

Transmis sion


IPRT

Transmis sion


OMCH

Transmis sion


SCTPLNK

Transmis sion


IPPATH

Transmis sion


EPGROUP

Transmis sion


USERPLANEHO ST

Transmis sion

Issue 01 (2015-12-30)


Transmis sion Transmis sion

126


Domain



MOC

Parameter Name

CME Type


USERPLANEPE ER

Transmis sion


SCTPHOST

Transmis sion


SCTPPEER

Transmis 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. 

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 1. Scenario description and application scope 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. 3. Engineering guidelines 

Material requirement No additional material is required.

Issue 01 (2015-12-30)


127



Software version requirement Backplane co-transmission: SRAN7.0 and later



License requirement Related co-transmission licenses must be purchased.

Doma in

Module Type


License SBOM

Sales Unit

Mod e

Transmi ssion

Cotransmissi on

IP-Based Multi-mode CoTransmission on BS side(GBTS)

88030QUG

Per BTS

G

Transmi ssion

Cotransmissi on

IP-Based Multi-mode CoTransmission on BS side(NodeB)

88030QUR

Per NodeB

U

Transmi ssion

Cotransmissi on

IP-Based Multi-mode CoTransmission on BS side(eNodeB)

88030QUR

Per eNodeB

L






MOC

Parameter Name

CME Type

Transmission


TUNNEL

Transmis sion


DEVIP


IPRT



OMCH

Transmis sion


SCTPLNK

Transmis sion


IPPATH

Transmis sion


EPGROUP

Transmis sion


USERPLANEHO ST

Transmis sion


USERPLANEPE ER

Transmis sion


SCTPHOST

Transmis sion

Issue 01 (2015-12-30)



128


Domain



MOC

Parameter Name

CME Type


SCTPPEER

Transmis sion

Original mode providing a transmission port

TUNNEL

Transmis sion


IPRT

Transmis sion


DHCPRELAYS WITCH

Transmis sion


DHCPSVRIP

Transmis sion

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 Co-Transmission Feature Parameter Description. 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 link, signaling link, and route of the new mode. For details, see section "Configuring Transport Data" in 3900 Series Base Station Initial Configuration Guide. 

Service impact 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 1. Scenario description and application scope

Issue 01 (2015-12-30)


129



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 3. Engineering guidelines 

Material requirement No additional material is required for backplane co-transmission.



Software version requirement Backplane co-transmission: SRAN7.0 and later




Doma in

Module Type


License SBOM

Sales Unit

Mod e

Transmi ssion

Cotransmissi on


88030QUG

Per BTS

G

Transmi ssion

Cotransmissi on


88030QUR

Per NodeB

U

Transmi ssion

Cotransmissi on


88030QUR

Per eNodeB

L






MOC

Parameter Name

CME Type

Transmission


E1T1

For details, see section

Transmis sion

Issue 01 (2015-12-30)


130


Domain

Issue 01 (2015-12-30)



MOC

Parameter Name

CME Type


ETHPORT

Transmis sion


PPPLNK


MPGRP

"Configuring Transport Data" in 3900 Series Base Station Initial Configuration Guide.


MPLNK

Transmis sion


TUNNEL

Transmis sion


DEVIP

Transmis sion


IPRT

Transmis sion


OMCH

Transmis sion


SCTPLNK

Transmis sion


IPPATH

Transmis sion


EPGROUP

Transmis sion


USERPLANEHO ST

Transmis sion


USERPLANEPE ER

Transmis sion


SCTPHOST

Transmis sion


SCTPPEER

Transmis sion


DHCPRELAYS WITCH

Transmis sion


DHCPSVRIP

Transmis sion

Original-mode main control board

TUNNEL

Transmis sion


DEVIP

Transmis sion



131


Domain



MOC


IPRT

Parameter Name

CME Type Transmis sion

Original mode: - Configure a backplane tunnel. - Add a device IP address. - Adjust the IP route. For details, see Co-Transmission Feature Parameter Description. 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 link, signaling link, and route of the new mode. For details, see section "Configuring Transport Data" in 3900 Series Base Station Initial Configuration Guide. 

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 1. Scenario description and application scope 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 3. Engineering guidelines Issue 01 (2015-12-30)


132



Material requirement No new material is required.



Software version requirement SRAN8.0 and later versions




Doma in

Module Type


License SBOM

Sales Unit

Mod e

Transmi ssion

Cotransmissi on


88030QUG

Per BTS

G

Transmi ssion

Cotransmissi on


88030QUR

Per NodeB

U

Transmi ssion

Cotransmissi on


88030QUR

Per eNodeB

L






MOC

Parameter Name

CME Type

Transmission

Node

DEVIP

Transmis sion

Node

SCTPLNK

Node

IPPATH


Node

EPGROUP

Transmis sion

Node

USERPLANEHO ST

Transmis sion

Node

USERPLANEPE ER

Transmis sion

Node

SCTPHOST

Transmis sion

Node

SCTPPEER

Transmis sion

Node

CPBEARER

Transmis sion

Issue 01 (2015-12-30)



133


Domain



MOC

Parameter Name

CME Type

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: 1) 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. 2) The service link, signaling link, and route of the new mode must be configured. New mode: For new mode GU: 1) CPBEARER referenced by NODE must be configured on the signaling plane of the new mode. 2) IPPATH or EPGROUP referenced by NODE must be configured on the user plane of the new mode. For new mode L: 1) CPBEARER or EPGROUP referenced by NODE must be configured on the signaling plane of the new mode. 2) IPPATH or EPGROUP referenced by NODE must be configured on the user plane of the new mode. For details, see section "Configuring Transport Data" in 3900 Series Base Station Initial Configuration Guide. Issue 01 (2015-12-30)


134



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 1.1 Focus for equipment auxiliary planning Equip ment

Scenari o

Func tion

Focus

BBU

Adding a new mode to the original BBU

Installa tion

A BBU has been installed and installation is not needed.

Power supply

Use the NEP-SD tool or PCT tool to determine whether 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 BBU3910 Boards > UPEU in 3900 Series Base Station Product Documentation.

Heat dissipa tion

In the high temperature areas, if an UPEU is added to the BBU3900 of an outdoor DC cabinet, a high-speed FANc 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 new BBU for mode transition

Installa tion

If the new and original BBUs are installed in the same cabinet, check whether the cabinet supports two BBUs. If the new BBU is installed in another cabinet, check the 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 supply Issue 01 (2015-12-30)

Circuit breaker ports must be available on the DCDU to provide power supply for the new BBU.


135


Equip ment

RF module


Scenari o

SDR RF module without new RF module

Adding an RFU

Func tion

Focus

Heat dissipa tion

Check the heat dissipation capabilities of the cabinet.

Installa tion

N/A

Power supply

N/A

Heat dissipa tion

N/A

Installa tion

1. Check whether the original cabinet supports the new 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.

Note: For the heat dissipation capability, see the section describing BBU/cabinet specifications.

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. 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 supply

1. RFU power 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,

Issue 01 (2015-12-30)


136


Equip ment


Scenari o

Func tion

Focus cable diameter, and circuit breaker, see "Cable diameter or circuit breaker calculation."

Adding an RRU

Heat dissipa tion

If a new RFU can be installed in the cabinet, the RFU heat dissipation requirement can be met.

Installa tion

Determine where the RRU is to be installed. The RRU 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 supply

1. RRU power 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. 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 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."

Transm ission equipm ent

Issue 01 (2015-12-30)

Original transmissi on equipment

Heat dissipa tion

N/A

Installa tion

N/A

Power supply

N/A

Heat dissipa

N/A


137


Equip ment


Scenari o

Func tion

Focus

tion

Others

Adding a new transmissi on equipment /Replacing the original transmissi on equipment

Installa tion

Check whether the cabinet has enough room for the new transmission equipment.

Power supply

Check whether power circuit breakers must be provided for the transmission equipment.

Heat dissipa tion

The power consumption of the transmission equipment and the total power consumption of other equipment must meet the heat dissipation capabilities of the cabinet.

Air conditione r in the equipment room

Heat dissipa tion

If a device is added to an indoor site, check the heat dissipation capability of the equipment room.

Equipment room

Installa tion

Pay attention to the feeder window, ground bar, and cable tray in the equipment room during the site survey.

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 followings: 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. 7. Engineering guidelines 

Material requirement Check whether a new material is required based on the planning descriptions in this section.



Issue 01 (2015-12-30)

Version requirement Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

138



None 




Data configuration requirement Pay attention to configuration of the cabinet and monitoring parts in the cabinet. For details, see Base Station Cabinets and Subracks (Including the BBU Subrack) Configuration Feature Parameter Description and Monitoring Management Feature Parameter Description.

Table 1.2 Key parameters related to the FMU Domai n


MOC

Parameter Name

Param eter ID

Example Value

Equipme nt

Adding an FMU

FMU

Manager Cabinet No.

MCN

0

Adding an FMU

FMU

Manager Subrack No.

MSRN

0

Adding an FMU

FMU

Serial Number

MPN

0

Adding an FMU

FMU

Address

ADDR

14

Adding an FMU

FMU

Smart Temperature Control

STC

ENABLE(Enable )

Table 1.3 Key parameters related to the TCU Domai n


MOC

Parameter Name

Parame ter ID

Example Value

Equipme nt

Adding a TCU

TCU

Manager Cabinet No.

MCN

0

Adding a TCU

TCU

Manager Subrack No.

MSRN

0

Adding a TCU

TCU

Serial Number

MPN

0

Adding a TCU

TCU

Address

ADDR

7

Issue 01 (2015-12-30)


139



Table 1.4 Key parameters related to the EMU Domai n


MOC

Parameter Name

Parame ter ID

Example Value

Equipme nt

Adding an EMU

EMU

Manager Cabinet No.

MCN

0

Adding an EMU

EMU

Manager Subrack No.

MSRN

0

Adding an EMU

EMU

Serial Number

MPN

0

Adding an EMU

EMU

Address

ADDR

2

Table 1.5 Key parameters related to the PMU Domai n


MOC

Parameter Name

Parame ter ID

Example Value

Equipme nt

Adding a PMU

PMU

Manager Cabinet No.

MCN

0

Adding a PMU

PMU

Manager Subrack No.

MSRN

0

Adding a PMU

PMU

Serial Number

MPN

0

Adding a PMU

PMU

Address

ADDR

3

Table 1.6 Key parameters related to the battery Domai n


MOC

Parameter Name

Parame ter ID

Example Value

Equipme nt

Adding a PMU

BATTERY

Battery Type

BTYPE

VRLA_BAT(VR LA Battery)

Adding a PMU

BATTERY

Battery 1 Capacity

BC1

30

Issue 01 (2015-12-30)


140



Table 1.7 Key parameters related to the CCU Domai n


MOC

Parameter Name

Parame ter ID

Example Value

Equipme nt

Adding a CCU

CCU

Manager Cabinet No.

MCN

0

Adding a CCU

CCU

Manager Subrack No.

MSRN

0

Adding a CCU

CCU

Serial Number

MPN

0

Adding a CCU

CCU

DirectConnectFl ag

DCF

YES (Yes)

Adding a CCU

CCU

Cascade No.

CCN

1

Adding a CCU

CCU

Connected RAT

CS

GSM



Service impact



Adjusting the power system

Services of the entire site are interrupted.

Installing a new cabinet


Expanding the capacity by adding a new module in the original cabinet


Reconstructing the original cabinet

Services of the original mode are interrupted during the 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.

Issue 01 (2015-12-30)


141



Table 1.1 Summary of multimode BBOM license allocation Do mai n

Mod ule Type



License BBOM


Sales Unit

Mod e

RF

Multiband RF modul es except for the RRU3 961.


MultiMode MultiBand License for MultiBand RF Module (UMTS) (Per Band per RRU)

82205398

LQW9RF BAND01

Per band

U

RF

MultiMode Multi-Band License for Multi-Band RF Module (UMTS)

MultiMode MultiBand License for MultiBand RF Module (UMTS) (Per Band per RRU)

82205398

LQW9RF BAND01

Per band

U

RF


MultiMode MultiBand License for MultiBand RF Module (LTE FDD) (Per Band per RRU)

82205382

LLT1MM LMBRM0 1

Per band

L

RF

MultiMode Multi-Band License for Multi-Band RF Module (LTE FDD)

MultiMode MultiBand License for MultiBand RF Module (LTE FDD) (Per Band per

82205382

LLT1MM LMBRM0 1

Per band

L

Issue 01 (2015-12-30)


142


Do mai n

Mod ule Type




License BBOM


Sales Unit

Mod e

RRU) RF

Must be purch ased for the RRU3 961 if both the 800 MHz and 900 MHz freque ncy bands are used.

RF 800M/900 M Multi Band license

RF 800M/900 M Multi Band license

82204034

LLT1RFM B01

Per band per RRU

L

RF GU

Nonblade modul e

GSM/UMT S Dual Mode license


82201199

LQW9MB TSRF02

Per sector

U

Blade &AA U

GSM/UMT S Dual Mode license for Blade&AA U


82201199

LQW9MB TSRF02

Per sector

U

Nonblade modul e



82201472

LLT1GLD M01

Per sector

L

Blade &AA U

GSM/LTE Dual Mode license for

GSM/LTE Dual Mode license(per

82201472

LLT1GLD M01

Per sector

L

RF GL

Issue 01 (2015-12-30)


143


Do mai n

RF UL

RF GUL

Mod ule Type




License BBOM


Sales Unit

Mod e

Blade&AA U

Sector)

Nonblade modul e



82201473

LLT1ULD M01

Per sector

L

Blade &AA U

UMTS/LTE Dual Mode license for Blade&AA U


82201473

LLT1ULD M01

Per sector

L

Nonblade modul e

RF GSM/UMT S Dual Mode license + RF GSM/LTE Dual Mode license

NA

NA

NA

Per sector

U+L

N/A

NA

NA

Per sector

U+L

or RF GSM/UMT S Dual Mode license + RF UMTS/LTE Dual Mode license Blade &AA U

GSM/UMT S Dual Mode license for Blade&AA U+ GSM/LTE Dual Mode license for Blade&AA U or GSM/UMT S Dual

Issue 01 (2015-12-30)


144


Do mai n

Mod ule Type




License BBOM


Sales Unit

Mod e

Mode license for Blade&AA U+ UMTS/LTE Dual Mode license for Blade&AA U MPT

Multi mode coMPT

UMPT Multi Mode License(GS M)

UMPT Multi Mode License (GSM)(per UMPT)

82204202

LGB3UM ML01

Per UMPT

G

MPT

Multi mode coMPT

UMPT Multi Mode License(U MTS)


82203981

LQW9GU DM01

Per UMPT

U

MPT

Multi mode coMPT

UMPT MultiMode license (LTE FDD)


82204259

LLT1UM ML01

Per UMPT

L

MPT

Multi mode coMPT



82204285

LLT1TUM ML01

Per UMPT

L

Clock

Clock sharin g

Multi-mode BS Common Reference Clock(eNo deB)

FunctionLTELLT1MCR C01-Multimode BS Common Reference Clock(eNo deB)(Per

81201529

LLT1MCR C01

Per eNode B

L

Issue 01 (2015-12-30)


145


Do mai n

Mod ule Type




License BBOM


Sales Unit

Mod e

eNodeB) Baseb and

Cobaseb and



82204551

LGMIUB BP

Per UBBP

G

Baseb and

Cobaseb and

UBBP MultiMode license (GSM)


82204551

LGMIUB BP

Per UBBP

G

Baseb and

Cobaseb and


UBBP MultiMode license (UMTS)

82204657

LQW9UB PDM01

Per UBBP

U

Baseb and

Cobaseb and



82204657

LQW9UB PDM01

Per UBBP

U

Baseb and

Cobaseb and


UBBP MultiMode license (FDD)

82205382

LLT1MM LMBRM0 1

Per UBBP

L

Baseb and

Cobaseb and



82205382

LLT1MM LMBRM0 1

Per UBBP

L

Baseb and

Cobaseb and


UBBP MultiMode license (TDD)

82204849

LLT1TUB MML01

Per UBBP

L

Baseb and

Cobaseb and

UBBP MultiMode

UBBP MultiMode

82204849

LLT1TUB MML01

Per UBBP

L

Issue 01 (2015-12-30)


146


Do mai n

Trans missi on

Mod ule Type

Cotrans missi on




license (TDD)

license (TDD)

IP-Based Multi-mode CoTransmissio n on BS side(eNode B)

FunctionLTELLT1IPM CT01-IPBased Multimode CoTransmissi on on BS side(eNode B)(Per eNodeB)

License BBOM


Sales Unit

Mod e

81201528

LLT1IPM CT01

Per eNode B

L

Table 1.2 Multimode SBOM licenses Doma in

Module Type


License SBOM

Sales Unit

Mod e

Clock

Clock sharing

Multi-mode BS Common Reference Clock(GBTS)

88030QUK

Per BTS

G

Clock

Clock sharing

Multi-mode BS Common Reference Clock(NodeB)

88030QUU

Per NodeB

U

Clock

Clock sharing

Multi-mode BS Common Reference Clock(eNodeB)

88030QUW

Per eNodeB

L

Transmi ssion

Cotransmissi on


88030QUG

Per BTS

G

Transmi ssion

Cotransmissi on


88030QUR

Per NodeB

U

Transmi ssion

Cotransmissi on


88030QUR

Per eNodeB

L



The license must be adjusted when a dependent GSM NE is to be reconstructed into an independent GSM NE.

In GBSS R15.0, the control mechanism of BTS license is changed. The main change is that eGBTS controls those features quoted in BTS independently. Before enable or use these features, GTS should allocate sufficient licenses on U2000 eGBTS License Management Issue 01 (2015-12-30)


147



View. Otherwise, these features cannot be enabled and CS/PS transaction may even be infected. The following table describes how to allocate license of those BTS features for each eGBTS. 1.

The Features Included by eGBTS License File But Not Supported by the eGBTS Site

Featu re ID


Sale Unit

GBTS Suppo rted

eGBTS Suppor ted


-

High Power (per TRX)

Per TRX

Yes

No

License = 0

-

TRU which works as Multitransceivers Resource of the 3rd generation BTS (per TRX)

Per TRX

Yes

No

License = 0

-

BBU Carrier Capacity License (per TRX)

per TRX

Yes

No

License = 0

GBFD115901

PBT(Power Boost Technology) (per TRX)

Per TRX

Yes

No

License = 0

GBFD115902

Transmit Diversity (per TRX)

Per TRX

Yes

No

License = 0

-

BTS3900B Transceiver Resource (per TRX)

Per TRX

Yes

No

License = 0

2.

-



Per TRX

Yes

Yes

License = the number of activated TRXs of GBTS with GBTS Power Type (w) set in [60 W, 80 W). Related BSC MML: LST GTRXDEV

-

Issue 01 (2015-12-30)

Multi-Carrier 80 W High

Per TRX

Yes

Yes


License = the number of TRXs of GBTS with GBTS 148



Power License (per TRX)

Power Type (w) set in (80 W). Related BSC MML: LST GTRXDEV

-

TRU which works as Multitransceivers Resource of 3900 (per TRX)

Per TRX

Yes

Yes

Non-SubSite scene: License = the number of logical TRXs of eGBTS – the number of include GSM TRX's Boards. SubSite scene(Supported begin eGBTS R16.0): (1) International and China Unicom: License = the number of logical TRXs of eGBTS * the number of location groups – the number of RXUs from all location groups. (2) China Mobile: License = the number of logical TRXs of eGBTS – the number of RXUs from the most RXUs location group. Related BSC MML: LST GTRX; LST BTSLOCGRPE; Related eGBTS MML: LST GTRXGROUPSECTOREQ M LST SECTOREQM

MRFD211801

Multi-mode Dynamic Power Sharing(GSM) (per Site)

Per Site

Yes

Yes

license = 1 if eGBTS's Power Sharing Type set to GUPWRSHR (GU Power Sharing). Related eGBTS MML: LST GBTSPWRSHRGRP;

MRFD211703

Issue 01 (2015-12-30)

2.0 MHz Central Frequency point separation between GSM and UMTS mode(GSM) (per Site)

Per Site

Yes

Yes


The license of this feature is not checked in BTS. When manually allocating the license to eGBTS, GTS should contact the Huawei salesman and allocate 1 license for each eGBTS for which the customer has bought this feature. 149


MRFD211804


GSM Power Control on Interference Frequency for GU Small Frequency gap(GSM) (per Site)

per BTS

MRFD211505

Bandwidth sharing of MBTS Multimode CoTransmission( GBTS) (per Site)

Per Site

Yes

Yes


MRFD211602

Multi-mode BS Common IPSec(GSM) (per Site)

per BTS

Yes

Yes


MRFD211802

GSM and UMTS Dynamic Spectrum Sharing(GSM) (per Site)

per BTS

Yes

Yes

License = 1 if Spectrum Sharing Allowed of eGBTS set to YES.

Dynamic MA for GU Dynamic Spectrum Sharing(GSM) (per Site)

per BTS

MRFD211803

Yes

Yes

License = 1 if at least one cell of the eGBTS set Frequency-based Power Control to ON. Related eGBTS MML: LST GLOCELLALGPARA

Related BSC MML: LST GDSSPARA Yes

Yes

License = 1 if in a eGBTS, at least one channel's FH Index Used After Frequency Spectrum Sharing set to value in range [0,63]. Related BSC MML: LST GTRXCHANHOP;

MRFD211806

GSM and LTE Dynamic Power Sharing(GSM) (per Site)

Per BTS

Yes

Yes

license = 1 if eGBTS's Power Sharing Type set to GLPWRSHR (GL Power Sharing). Related eGBTS MML: LST GBTSPWRSHRGRP;

MRFD211901 Issue 01 (2015-12-30)

Multi-RAT Carrier Joint Shutdown(GB

Per BTS

Yes

Yes

License = 1 if in the eGBTS, at least one cell's Inter -RAT Cell Dynamic Shutdown set


150



TS) (per Site)

to ON. Related BSC MML: LST GCELLSOFT

GBFD116602

IPSec Bypass (per Site)

Per BTS

No

Yes

License = 1 If eGBTS need to open this feature by set IPSec Bypass Switch to ENABLE. Related eGBTS MML: LST IPSECBYPASSCFG

-

UMPT MultiMode License(GSM) (per UMPT)

Per UMPT

No

Yes

1. license = 0 for each eGBTS if in GO scenario building eGBTS. 2. license = 0 for each eGBTS if building multiRAT (with G) co-MPT SRAN BTS (GU/GL/GUL). 3. license = 1 for each eGBTS when expanding GRAT for multi-RAT (without G) co-MPT SRAN BTS (such as UL->GUL).

-

Antenna Intermodulatio n Performance Detection (per TRX)

Per TRX

Yes

Yes

The license check of this feature is triggered by related maintaining MML. If this feature is needed, license = the number of activated logical TRXs of each eGBTS. Related eGBTS MML: STR RFTEST; STR GBTSRFTST

-

Extended Spectrum Scan (per TRX)

Per TRX

Yes

Yes

The license check of this feature is triggered by related eGBTS LMT GUI maintaining function. If this feature is needed, license = the number of activated logical TRXs of each eGBTS. Related eGBTS LMT GUI maintenance function: Offline spectrum scan monitoring

3. Issue 01 (2015-12-30)

The Features Supported by eGBTS Site R15.1 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

151



Feature ID

License Descripti on

Sal e Uni t

GBTS Supp orted

eGBTS Suppor ted


GBFD151202

BTS IP Active Performance Measuremen t (per Site)

Per BTS

No

Yes

license = 1 if eGBTS's TWAMPCLIENT or TWAMPRESPONDER function is enabled. Related BTS MML: LST TWAMPCLIENT LST TWAMPRESPONDER

4.


Featu re ID


Sale Unit

GB TS Su pp ort ed



-

SubSite Solution License (per Module)

Per Module

Yes

Yes

License = the number of RXUs which belong to the eGBTS location group – the number of RXUs which belong to the location group which has the most RXUs. Related BSC MML: LST BTSLOCGRPE Related BTS MML: LST SECTOR LST RRU

-

RFU co-cell Solution License (per Module)

Per Module

Yes

Yes

License = the number of RFUs which belong to the eGBTS location group Related BSC MML: LST BTSLOCGRPE Related BTS MML: LST SECTOR LST RRU

GBFD115903

4-Way Receiver Diversity (per TRX)

Per TRX

Yes

Yes

License = the number of TRXs which is configured 4-Way Receiver Diversity. Related BSC MML: LST GTRX Related BTS MML:

Issue 01 (2015-12-30)


152


Featu re ID



Sale Unit

GB TS Su pp ort ed



LST GTRXGROUP -

GBFD160209

GBFD160210


Per Module

IPSec redundancy among multiSeGWs (per BTS)

Per BTS

BTS supporting PKI redundancy (per BTS)

Per BTS

Yes

Yes

License = the number of GBTSBBRES Related BTS MML: LST GBTSBBRES

No

Yes

license = 1 if eGBTS's IPSec redundancy function is enabled. Related BTS MML: LST IKEPEER

No

Yes

license = 1 if eGBTS's PKI redundancy function is enabled. Related BTS MML: LST CA LST CRLTSK

MRFD261103

AAS RAT Specific Tilting (GSM) (Per RU)

Per RU

No

Yes

The license of this feature is not checked in BTS. When manually allocating the license to eGBTS, GTS should contact the Huawei salesman and allocate the number of licenses which equals the number of AASs which the customer has bought.

Not Commer cial

AAS Virtual Four Uplink Channels for GSM (per RU)

Per RU

No

Yes

License = the number of AARUs whose four virtual ports are used as the receiving channel by GTRXGROUP. Related BTS MML: LST GTRXGROUP LST GTRXGROUPSECTOREQM LST AARU

5.

Issue 01 (2015-12-30)



153



Featu re ID


Sale Unit

GB TS Su pp ort ed

eG BTS Sup por ted


GBFD170205

GTMUb SingleOM (Per BTS)

per BTS

No

Yes

license = 1 if the GTMUb functions as the main control board of the eGBTS. Ralated eGBTS MML: DSP BRDMFRINFO

6.


Featur e ID


Sale Unit

GB TS Sup por ted



GBFD171205

BTS Supporting Multi-Carrier PKI (per BTS)

per BTS

No

Yes

license = 1 if eGBTS's configuration MPT is GTMU.

GBFD171206

BTS Supporting IPSec Redirection (per BTS)

per BTS

No

Yes

The license of this feature is not checked in BTS. When manually allocating the license to eGBTS, GTS should contact the Huawei salesman and allocate 1 license to the base station which the customer has bought.

-

Multi-Mode Multi-Band License for Multi-Band RF Module (GSM) (Per Band per RRU)

per Band per RRU

Yes

Yes

Calculate the number of all the frequency bands used by multi-band RRU in all the GSM cells.

Related BTS MML: DSP BRD

Related BTS MML: LST GTRX Related BTS MML: LST GTRXGROUPSECTOREQM LST SECTOREQM

7.

Issue 01 (2015-12-30)



154



Featur e ID


Sale Unit

GBT S Sup por ted



GBFD181202

BTS Supporting Digital Certificate Whitelist Management (Per BTS)

per BTS

No

Yes

license = 1 if eGBTS is opened the switch of IKECHECKSW. Related BTS MML: 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 cobaseband requires SRAN8.0 or later, the NE must use SRAN9.0 or later versions. For details about the version mapping between related NEs and base stations, 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 1.1 Materials required for mode transition Material Type

Material Name

Quantity

RF

RRU/RFU




For the RFU



For the RRU

Optical module


For the RRU

RRU power cable


For the RRU




Issue 01 (2015-12-30)


Remarks

155



Material Type

Material Name

Quantity

Remarks

Antenna and feeder

Antenna



Feeder

Twice the number of sectors

Not required when 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

SBT

Issue 01 (2015-12-30)

The length of the jumper needs to be determined according to the site survey. Same as the number of sectors

Required on the antenna side when the following conditions are met: 







The RRU and antenna are not directly connected to each other.

TMA



RCU


Required when RET is required but no internal RET is available.

AISG cable




156



Material Type

MPT

Material Name

Quantity

Remarks

AISG cable from the RRU


Required when the RRU and RET are directly connected to each other.

Combiner



UMPT(L)/LMPT


An LTE main 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 services of the newly deployed mode may be interrupted.

UMPT(U)/WMPT


A UMTS main 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 services of the newly deployed mode may be interrupted.

GTMU Issue 01 (2015-12-30)

Determined based


A GSM main control 157



Material Type

BBU interconnection and BBU

Material Name

BBU subrack

Quantity

Remarks

on the plan

board is added.


Used for BBU expansion. 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 interconnection

Some

BBU 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


Used for BBU 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.

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.

Issue 01 (2015-12-30)


158



Domain

Configura tion Object

MOC

Paramete r Name

Para met er ID

Value (Examp le)

CM E Ty pe

RF module

Adding an RXU

RRU

Cabinet No.

CN

0

RF

Adding an RXU

RRU

Subrack No.

SRN

60

RF

Adding an RXU

RRU

Slot No.

SN

3

RF

Adding an RXU

RRU

RRU type

RT

MRRU

RF

Adding an RXU

RRU

RRU Topo Position

TP


RF

Adding an RXU

RRU

RRU Chain/Ring No.

RCN

0

RF

Adding an RXU

RRU

RRU Position

PS

0

RF

Adding an RXU

RRU


RS

GL

RF

Adding an RXU

RRU


RXN UM

2

RF

Adding an RXU

RRU


TXN UM

2

RF

Root BBU mode

CTRLLNK

Local Link No.

LN

0

Equ ipm ent

Root BBU mode

CTRLLNK

Local Cabinet No.

CN

0

Equ ipm ent

Root BBU mode

CTRLLNK

Local Subrack No.

SRN

1

Equ ipm ent

Root BBU mode

CTRLLNK

Local Slot No.

SN

7

Equ ipm ent

Root BBU mode

CTRLLNK

Upper Cabinet No.

UPCN

0

Equ ipm ent

BBU interconne ction

Issue 01 (2015-12-30)


159


Domain

Clock GBTS

Issue 01 (2015-12-30)



MOC

Paramete r Name

Para met er ID

Value (Examp le)

CM E Ty pe

Root BBU mode

CTRLLNK

Upper Subrack No.

UPSR N

0

Equ ipm ent

Root BBU mode

CTRLLNK

Upper Slot No.

UPSN

4

Equ ipm ent

Root BBU mode

CTRLLNK

Upper Port No.

UPPT

0

Equ ipm ent

Leaf BBU mode

CTRLLNK

Local Link No.

LN

0

Equ ipm ent

Leaf BBU mode

CTRLLNK

Local Cabinet No.

CN

0

Equ ipm ent

Leaf BBU mode

CTRLLNK

Local Subrack No.

SRN

1

Equ ipm ent

Leaf BBU mode

CTRLLNK

Local Slot No.

SN

7

Equ ipm ent

Leaf BBU mode

CTRLLNK

Upper Cabinet No.

UPCN

0

Equ ipm ent

Leaf BBU mode

CTRLLNK

Upper Subrack No.

UPSR N

0

Equ ipm ent

Leaf BBU mode

CTRLLNK

Upper Slot No.

UPSN

4

Equ ipm ent

Leaf BBU mode

CTRLLNK

Upper Port No.

UPPT

0

Equ ipm ent

Original mode/new mode

BTSCLK

Clock Type

ClkTy pe

PEER_CL K

Equ ipm ent

BTSCLK

Peer Mode

STAN DAR D

Set this parameter to the mode of the

Equ ipm ent


160


Domain



MOC

Paramete r Name

Para met er ID

Value (Examp le)

CM E Ty pe

reference clock. Clock


CLKMODE

Clock Working Mode

MOD E

Set this parameter to MANUAL (Manual).

Equ ipm ent

CLKMODE


CLKS RC

Set this parameter to PEERCL K(Peer Clock).

Equ ipm ent

PEERCLK

Peer Clock No.

PN

Set this parameter to 0.

Equ ipm ent

PEERCLK

Peer Standard

PS


Equ ipm ent

MPT


Working Mode

Working Mode

WM

Set this parameter to CONCUR RENT(Co ncurrent).

Equ ipm ent

Baseband


BBP


BBW S

Determine d by the UBBP configurati on plan

Equ ipm ent


MDU


BBW S

Determine d by the mode planned for the UMDU

Equ ipm ent


E1T1

Transmiss ion

Issue 01 (2015-12-30)


Tran smis sion

161


Domain

Issue 01 (2015-12-30)



MOC

Paramete r Name


ETHPORT

Tran smis sion


PPPLNK

Tran smis sion


MPGRP

Tran smis sion


MPLNK

Tran smis sion


TUNNEL

Tran smis sion


DEVIP

Tran smis sion


IPRT

Tran smis sion


OMCH

Tran smis sion


SCTPLNK

Tran smis sion


IPPATH

Tran smis sion


EPGROUP

Tran smis sion


and USERPLAN EHOST (in end point configuration mode)

Tran smis sion

New-mode main control

USERPLAN EPEER

Tran smis


Para met er ID

Value (Examp le)

CM E Ty pe

162


Domain



MOC

Paramete r Name

board

Para met er ID

Value (Examp le)

CM E Ty pe sion


SCTPHOST

Tran smis sion


SCTPPEER

Tran smis sion


DHCPRELA YSWITCH

Tran smis sion


DHCPSVRIP

Tran smis sion

Originalmode main control board

TUNNEL

Tran smis sion


DEVIP

Tran smis sion


IPRT

Tran smis sion

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 coMPT reconstruction configuration data conversion: SRANconvert_BSC Module_V***R***C **SPC***.zip

Obtain the corresponding co-MPT conversion components based on the versions.

BTS component coMPT reconstruction configuration data conversion: SRANconvert_GBTS

Obtain the corresponding co-MPT conversion components based on the versions.

Issue 01 (2015-12-30)

http://support.huawei.com/carrier/navi#col=software&path=PBI17851894/PBI1-7854240/PBI1-7275801/PBI1-19953556/PBI113761

http://support.huawei.com/carrier/navi#col=software&path=PBI17851894/PBI1-7854240/PBI1-7275801/PBI1-19953557/PBI113751


163



Tool Name

How to Obtain

&SRANModule_V** *R***C**SPC***.zi p Data planning template for co-MPT reconstruction configuration data conversion

NOTE Use the data planning template for the corresponding SRAN version during co-MPT reconstruction.

The following is the CME Client installation directory of the 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=PBI17851894/PBI1-7854702/PBI1-7275896/PBI1-21103986/PBI121044913

Issue 01 (2015-12-30)


164


4

4 Mode Transition Examples

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.

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 4-1 shows the hardware configurations before and after mode transition. Figure 4-2 shows the transmission networking topology before and after mode transition. Figure 1.1 Hardware configurations before and after mode transition

Issue 01 (2015-12-30)


165



Figure 1.2 Transmission networking topology before and after mode transition

Table 4-1 lists the major differences before and after mode transition. Table 2.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 in the 900 MHz frequency band, three sectors configured

GSM and UMTS operating in the 900 MHz frequency band, three sectors configured; GSM and LTE operating in the 1800 MHz frequency band, three sectors configured

900 MHz: GSM S2/2/2/, UMTS S2/2/2, 1T2R

900 MHz: GSM S2/2/2/, UMTS S2/2/2, 1T2R 1800 MHz: GSM S2/2/2, Issue 01 (2015-12-30)


166



Item

Before Transition

After Transition LTE S1/1/1 (1x5 MHz), 2T2R

BBU

One BBU; GSM and UMTS sharing the same BBU

Two BBUs interconnected through UCIU+UMPT GSM and UMTS sharing the same BBU; LTE using the other BBU

RF typology

Dual-star topology for GU RF modules

Dual-star topology for both GU RF modules and GL RF modules

Transmission scheme

Co-transmission through panel interconnection for GSM and UMTS, IP over Ethernet

Co-transmission through UMPT backplane, IP over Ethernet

Clock networking

GSM and UMTS sharing the IEEE 1588 V2 reference clock

GSM, UMTS, and LTE using an IEEE 1588 V2 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 2.2 LTE global data configuration Dom ain


MOC

Parameter

Recommen ded Value

Globa l

LTE

CnOperator

CN Operator ID

0

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 Server

10.141.142.22

Clock

NTPCP

Synchronization Period

1

Clock

TASM

Clock Working Mode

MANUAL

Clock

TASM

Clock Source No.

0

Clock

TASM


IPCLK

Issue 01 (2015-12-30)


167


Dom ain



MOC

Parameter

Recommen ded Value

Clock

TASM

Clock Synchronization Mode

FREQ

Clock

TASM

Quality Level

QL_PRC

Clock

IPCLKLNK

Link No.

0

Clock

IPCLKLNK

Protocol Type

PTP

Clock

IPCLKLNK

Cabinet No./Subrack No./Slot No.

0/1/7

Clock

IPCLKLNK

Server IPv4

170.179.179.34

Clock

IPCLKLNK

Client IPv4

160.70.7.10

Clock

IPCLKLNK

Domain

0

Table 2.3 LTE equipment data configuration Domain


MOC

Parameter

Recommend ed Value

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 topology

RRUCHAIN

Issue 01 (2015-12-30)


Three RRU chains are connected to optical fiber cables through three optical ports 0, 1, and 2 on the 168


Domain



MOC

Parameter

Recommend ed Value

baseband processing board. RF module

RRU


Configure an RRU on the new RRU 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 feeder

RET

RET Type

SINGLE_RET

Antenna and feeder

RET

Polar Type

DUAL

Antenna and feeder

RET

Antenna Scenario

REGULAR

Antenna and feeder

RET


0

Antenna and feeder

RET


63, 64, and 65

Antenna and feeder

RET


0

Antenna and feeder

RETSUBUNIT

Device No.

0, 1, and 2

Antenna and feeder

RETSUBUNIT

Subunit No.

0

Antenna and feeder

RETSUBUNIT

Connect to the following: 0\63\0 R0A0\63\0 R0B 0\64\0 R0A0\64\0 R0B 0\65\0 R0A-

Issue 01 (2015-12-30)


169


Domain



MOC

Parameter

Recommend ed Value

0\65\0 R0B

Table 2.4 LTE transmission data configuration Domain


MOC

Parameter

Recommen ded Value

Transmission

LTE

SCTPLNK

Link No.

0

Transmission

SCTPLNK


0/1/7

Transmission

SCTPLNK

First Local IP Address

160.70.7.13

Transmission

SCTPLNK

Local SCTP Port No.

2913

Transmission

SCTPLNK

First Peer IP Address

125.120.120.1

Transmission

SCTPLNK

Peer SCTP Port No.

2910

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


0/1/7

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

Issue 01 (2015-12-30)


170


Domain



MOC

Parameter

Recommen ded Value

Transmission

S1Interface

S1 Interface CP Bearer ID

0

Transmission

S1Interface

CN Operator ID

0

Transmission

S1Interface

MME Release

Release_R10

Transmission

S1Interface

S1 Interface Is Blocked

FALSE

Transmission

OMCH

Standby Status

MASETR

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


0\1\7

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

Issue 01 (2015-12-30)

IPRT


Route Index

Configure eight IP routes to the following items: U2000, clock, SG-W, MME, BSC, RNC, GSM tunnel, and UMTS 171


Domain



MOC

Parameter

Recommen ded Value 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. 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 Priority

DISABLE

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


Corresponding to those of the UMPT in subrack 1.

Transmission

ETHPORT

Subboard Type

BASE_BOARD

Transmission

ETHPORT

Port Attribute

Two values:

Issue 01 (2015-12-30)


172


Domain



MOC

Parameter

Recommen ded Value COPPER FIBER

Transmission

DHCPSVRIP

DHCP Server IP Address

Set the DHCP server IP address to the IP address of the U2000 and MBSC for deployment.

Transmission

DHCPRELAYS WITCH

DHCP Relay Switch

ENABLE

Transmission

DHCPSW

OMCH AutoEstablishment Switch

ENABLE

Transmission

DHCPSW

Vlanscan Switch

DISABLE

Table 2.5 LTE radio data configuration Domain


MOC

Parameter

Recommen ded 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 feeder

SECTOREQM

——

Three pieces of sector equipment are added. They correspond to sectors 0

Issue 01 (2015-12-30)


173


Domain



MOC

Parameter

Recommen ded Value 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 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 QM

Baseband Equipment Type

ULDL

Radio

BASEBANDE QM

UMTS UL Demodulation

DEM_4_CHAN

Issue 01 (2015-12-30)


174


Domain



MOC

Parameter

Recommen ded Value

Mode Radio

BASEBANDE QM

Baseband Equipment Board

0,1,3

Parameter

Recommen ded Value

Table 2.6 GSM data configuration Domain


MOC

CPRI-based topology

GSM

BTSRXUCHAI N

Configure three RRU chains on optical ports 3, 4, and 5 on the GTMU.

CPRI-based topology

BTSRXUBRD

Added one MRRU to position 1 of each of the newly added three chains.

RF module

BTSRXUBP

Working Standard

GSM_AND_LT E Note that the working mode of the new RF module must be set to GL.

Radio

GCELL

Radio

TRXINFO

Configure two TRXs in each cell using the main and diversity RX channels.

Radio

TRXBIND2PH YBRD

Bind three cells to the R0As of three RRUs, respectively.

Issue 01 (2015-12-30)


Freq. Band

Add three cells that are served by the DCS1800 frequency band.

175



Table 2.7 GSM transmission data configuration Domain


MOC

Parameter

Recommen ded Value

Transmission

GSM

BTSDEVIP

Port Type

LOOPINTERF ACE

Transmission

BTSDEVIP


Cabinet No./Subrack No./Slot No. of the GTMU

Transmission

BTSDEVIP

IP Address

88.200.8.241

Transmission

BTSIP

BTS Communication Type

LOGICIP

Transmission

BTSIP

BTS IP

88.200.8.241

Transmission

BTSIP

BSC IP

26.14.1.1

Transmission

BTSESN

BTS Interface Board Bar Code 1

21021127226T BA915704

Transmission

BTSESN

OM Bear Board

BACKBOARD

Transmission

BTSTUNNEL

--

From the GTMU to UMPT (LTE), the tunnel No. is 0.

Transmission

BTSIPRT

Destination IP Address

26.14.1.1 (BSC)

Transmission

BTSIPRT

Route Index

0

Transmission

BTSIPRT

Route Type

OUTIF

Transmission

BTSIPRT

Cabinet No./Subrack No./Slot No. of the ports


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 address

88.200.8.241

Transmission

IPRT

Next hop type

Gateway

Issue 01 (2015-12-30)


176


Domain



Transmission

MOC

Parameter

Recommen ded Value

IPRT

Forward route address

26.14.0.1

Table 2.8 UMTS equipment data configuration Domain


MOC

Parameter

Recommen ded Value

Clock

UMTS

PEERCLK

Peer Clock No.

0

Clock

PEERCLK

Peer Standard

LTE

Clock

TASM

Clock Working Mode

MANUAL

Clock

TASM

Clock Source No.

0

Clock

TASM


PEERCLK

Clock

TASM

Clock Synchronizatio n Mode

FREQ

Clock

TASM

Quality Level

QL-SSU-B

Table 2.9 UMTS transmission data configuration Domain

Configurat ion Object

MOC

Parameter

Recommen ded Value

Transmission

UMTS

DEVIP


Corresponding to the cabinet No./subrack No./slot No. of the WMPT

Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

LOOPINT

Transmission

DEVIP

Port No.

1

Transmission

DEVIP

IP Address

88.200.8.242

Transmission

DEVIP

Mask

255.255.0.0

Transmission

SCTPLNK

Issue 01 (2015-12-30)


Set the local IP address (base station side) and destination IP 177


Domain



MOC

Parameter

Recommen ded Value 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

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.

Local IP

Change it to an address on the LTE side.

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 4-3 shows the hardware configurations before and after mode transition. Figure 4-4 shows the transmission networking topology before and after mode transition.

Issue 01 (2015-12-30)


178



Figure 1.1 Hardware configurations before and after mode transition

Issue 01 (2015-12-30)


179





Before Transition

After Transition

Mode

GSM only single-mode

GSM and LTE dual-mode


GSM operating in the 900 MHz frequency band, three sectors configured; GSM operating in the 1800 MHz frequency band, three sectors configured

GSM operating in the 900 MHz frequency band, three sectors configured; GSM and LTE operating in the 1800 MHz frequency band, three sectors configured

900 MHz: GSM S4/4/4, 1T2R

900 MHz: GSM S4/4/4, 1T2R

1800 MHz: GSM S2/2/2,

1800 MHz: GSM S2/2/2,

Issue 01 (2015-12-30)


180



Item

BBU

Before Transition

After Transition

1T2R

LTE S1/1/1 (1x5 MHz), 2T2R

One BBU

One BBU GSM and LTE using the same BBU and GSM configured with UBRI

RF typology

Star topology for GO RF modules

Star topology for GO RF modules and dual-star topology for GL RF modules

Transmission scheme

Transmission through panel, IP over Ethernet

GSM and LTE cotransmission through backplane interconnection with LTE port connected to the transport network, IP over Ethernet

Clock networking

GO IEEE 1588 V2 reference clock

GSM and LTE sharing an IEEE 1588 V2 reference clock



MOC

Parameter

Recommen ded Value

LTE

CnOperator

CN Operator ID

0

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


10.141.142.22

Clock

NTPCP


1

Clock

TASM

Clock Working Mode

MANUAL

Clock

TASM

Clock Source No.

0

Clock

TASM


IPCLK

Issue 01 (2015-12-30)


181


Dom ain



MOC

Parameter

Recommen ded Value

Clock

TASM


FREQ

Clock

TASM

Quality Level

QL_PRC

Clock

IPCLKLNK

Link No.

0

Clock

IPCLKLNK

Protocol Type

PTP

Clock

IPCLKLNK


Corresponding to those of the main control board

Clock

IPCLKLNK

Server IPv4

170.179.179.34

Clock

IPCLKLNK

Client IPv4

160.70.7.10

Clock

IPCLKLNK

Domain

0

Globa l

APPLICATION

Application Maintenance Mode

INSTALL

Trans missi on

ETHPORT

Port No.

0

Trans missi on

ETHPORT



Trans missi on

ETHPORT

Subboard Type

BASE_BOARD



MOC

Parameter

Recommend ed Value

MPT

LTE

MPT

Cabinet No.

0

MPT

MPT

Subrack No.

0

MPT

MPT

Slot No.

7

MPT

MPT

Board Type

LMPT

Baseband

BBP

Cabinet No.

0

Baseband

BBP

Subrack No.

0

Issue 01 (2015-12-30)


182


Domain



MOC

Parameter

Recommend ed Value

Baseband

BBP

Slot No.

3

Baseband

BBP

Board Type

LBBP

Baseband

BBP

Work Mode

FDD

Equipment

CABINET

Cabinet No.

Cabinet No.: 0 and 1

Cabinet Type

Cabinet Type: BTS3900 Equipment

SUBRACK

Cabinet No.

Cabinet No.: 0

Subrack No.

Subrack 0: BBU3900

Subrack Type

Subrack 11: FMU Subrack 4: RFU CPRI-based topology

RRUCHAIN

RF

RFU

Six RRU chains are connected to the fiber optical cables through the six CPRI ports on the baseband processing board. Cabinet No./Subrack No./Slot No.

Add six RFUs: 1/4/0 - 1/4/5

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


GL

RF

RFU


2

RF

RFU


1

Antenna and feeder

RET

Device No.

0, 1, and 2

Antenna and feeder

RET

RET Type

SINGLE_RET

Issue 01 (2015-12-30)


183


Domain



MOC

Parameter

Recommend ed Value

Antenna and feeder

RET

Polar Type

DUAL

Antenna and feeder

RET

Antenna Scenario

REGULAR

Antenna and feeder

RET


1

Antenna and feeder

RET


4

Antenna and feeder

RET


0, 2, and 4

Antenna and feeder

RETSUBUNIT

Device No.

0, 1, and 2

Antenna and feeder

RETSUBUNIT

Subunit No.

1

Antenna and feeder

RETSUBUNIT


Connect to the 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



MOC

Parameter

Recommen ded Value

Transmission

LTE

SCTPLNK

Link No.

0

Transmission

SCTPLNK


The main control board provides transmission ports.

Transmission

SCTPLNK


160.70.7.10

Transmission

SCTPLNK

Local SCTP Port No.

2913

Transmission

SCTPLNK

First Peer IP

125.120.120.1

Issue 01 (2015-12-30)


184


Domain



MOC

Parameter

Recommen ded Value

Address Transmission

SCTPLNK

Peer SCTP Port No.

2910

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



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.10

Transmission

IPPATH

Peer IP

171.23.36.1

Transmission

S1Interface

S1 Interface ID

0

Transmission

S1Interface


0

Transmission

S1Interface

CN Operator ID

0

Transmission

S1Interface

MME Release

Release_R8

Transmission

S1Interface


FALSE

Transmission

OMCH

Standby Status

MASETR

Transmission

OMCH

Local IP

Base Station Transport Data\OM Plane\*OmCh LocalIP

Transmission

OMCH

Local Mask

Base Station Transport Data/OM Plane/*OmCh LocalMask

Issue 01 (2015-12-30)


185


Domain



MOC

Parameter

Recommen ded Value

Transmission

OMCH

Peer IP

Base Station Transport Data\OM Plane\OmCh DstIP

Transmission

OMCH

Peer Mask

Base Station Transport Data\OM Plane\OmCh DstMask

Transmission

DEVIP



Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

ETH

Transmission

DEVIP

Port No.

0

Transmission

DEVIP

IP Address

160.70.7.10

Transmission

DEVIP

Mask

255.255.0.0

Transmission

TUNNEL

Transmission

IPRT

The tunnel starts from the UMPT to the GTMU and the direction is downlink. 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

Issue 01 (2015-12-30)


186


Domain



MOC

Parameter

Recommen ded Value 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 Priority

DISABLE

Transmission

DHCPSVRIP



Transmission

DHCPRELAYS WITCH

DHCP Relay Switch

ENABLE

Transmission

DHCPSW


ENABLE

Transmission

DHCPSW

Vlanscan Switch

DISABLE



MOC

Parameter

Recommen ded Value

Antenna and feeder

LTE

SECTOR

Sector ID

Add three sectors.

Sector Name 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

Issue 01 (2015-12-30)


187


Domain Antenna and feeder



MOC

Parameter

Recommen ded Value

SECTOREQM

Sector Equipment ID

Three pieces of 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

Issue 01 (2015-12-30)


188


Domain



MOC

Parameter

Recommen ded Value through 2. Baseband equipment: share equipment 0.

Baseband

BASEBANDE QM

Baseband Equipment ID

0

Baseband

BASEBANDE QM


ULDL

Baseband

BASEBANDE QM

UMTS UL Demodulation Mode

DEM_4_CHAN

Baseband

BASEBANDE QM


0, 0, 3

Table 2.6 GSM configuration Domain


MOC

Parameter

Recommen ded 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 topology

BTSRXUCHAI N

Add six chains 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 Standard

GSM_AND_LT E Note that the

Issue 01 (2015-12-30)


189


Domain



MOC

Parameter

Recommen ded Value working mode of the new RF module must be set to GL.

RF

TRXBIND2PH YBRD

Bind the TRX of the cell served by the 1800 MHz to the 1800 MHz MRFU in cabinet 1.

Table 2.7 BSC Configuration Domain


MOC

Parameter

Recommen ded Value

Transmission

GSM

BTSDEVIP

Port Type

LOOPINTERF ACE

Transmission

BTSDEVIP

*Port No.

0

Transmission

BTSDEVIP


Corresponding to the cabinet No./subrack No./slot No. of the GTMU

Transmission

BTSDEVIP

IP Index

0

Transmission

BTSDEVIP

IP Address

88.200.8.37

Transmission

BTSDEVIP

IP Mask

255.255.255.0

Transmission

BTSDEVIP

BTS Inner IP Switch

NO

Transmission

BTSIP


LOGICIP

Transmission

BTSIP

BTS IP

88.200.8.37

Transmission

BTSIP

BSC IP

40.13.3.200

Transmission

BTSIP

BTS MultiIP Switch

NO

Transmission

BTSESN


21021127229T AB020269

Transmission

BTSESN

OM Bear Board

BACKBOARD

Issue 01 (2015-12-30)


190


Domain



MOC

Parameter

Recommen ded Value

Transmission

BTSTUNNEL

The tunnel starts from the GTMU to the UMPT and is used for interconnection through panel transmission.

Transmission

BTSIPRT

Route Index

0

Transmission

BTSIPRT


40.13.3.200

Transmission

BTSIPRT

Destination Address Mask

255.255.255.25 5

Transmission

BTSIPRT

Route Type

OUTIF

Transmission

BTSIPRT



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


Set the destination IP addresses to the IP addresses of the GBTS: 88.200.8.37 160.70.7.10

Transmission

IPRT

Destination address mask

255.255.255.25 5

Transmission

IPRT

Next hop type

Gateway

Transmission

IPRT


40.13.3.1

Transmission

IPRT

Priority

HIGH

Issue 01 (2015-12-30)


191



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 4-5 shows the hardware configurations before and after mode transition. Figure 4-6 shows the transmission networking topology before and after mode transition. Figure 1.1 Hardware configurations before and after mode transition

Issue 01 (2015-12-30)


192





Before Transition

After Transition

Mode




GSM operating in the 900 MHz frequency band, three sectors configured


900 MHz: GSM S4/4/4, 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


Transmission scheme

Independent transmission through panel, IP over Ethernet

GSM and UMTS independent transmission through panel, IP over

Issue 01 (2015-12-30)


193



Item

Before Transition

After Transition Ethernet

Clock networking

IP reference clock

GSM and UMTS using an independent IP 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 2.2 UMPT data configuration Domain


MOC

Parameter

Recomme nded Value

Clock

UMTS

IPCLKLNK

Link No.

0

Clock

IPCLKLNK

Protocol Type

PTP

Clock

IPCLKLNK


Cabinet No./Subrack No./Slot No. of the main control board

Clock

IPCLKLNK

Server IPv4

170.179.179.3 4

Clock

TIMESRC

Time Source

NTP

Clock

TASM

Clock Working Mode

MANUAL

Clock

TASM

Clock Source No.

0

Clock

TASM


IPCLK

Clock

TASM


FREQ

Clock

TASM

Quality Level

QL_PRC

Global

UNODEBMNT MODE

Maintenance Mode

INSTALL

Table 2.3 MBSC global data configuration Domain


MOC

Parameter

Recomme nded Value

Equipment

MBSC

NE

Network Element Name

U_Transition_ 100

Issue 01 (2015-12-30)


194


Domain


MOC

Parameter

Recomme nded Value

Equipment

NE

Product Type

BTS3900_WC DMA

Equipment

NE

NodeB Template

BTS3900_WC DMA_IP RAN_2Channels 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 Type

IP_TRANS

Equipment

NODEB

IP Transport Apart Ind

SUPPORT

Equipment

NODEB

NodeB Host Type

SINGLEHOS T

Equipment

NODEB

Sharing Type Of NodeB

DEDICATED

Equipment

NODEB

Cn Operator Index

1

Transmissio n

ETHIP

Subrack No.

0

Transmissio n

ETHIP

Slot No.

14

Transmissio n

ETHIP

Port No.

6

Transmissio n

ETHIP

IP address index

0

Transmissio n

ETHIP

Local IP address

26.14.1.1

Transmissio n

ETHIP

Subnet mask

255.255.0.0

Transmissio n

NCP

Bearing Link Type

SCTP

Transmissio n

NCP

Port No.

0

Issue 01 (2015-12-30)



195


Domain



MOC

Parameter

Recomme nded Value

Transmissio n

NCP

Bearing Link Type

SCTP

Transmissio n

NCP

SCTP link No.

1001

Transmissio n

NCP

SCTP link No.

1002

Transmissio n

ADJNODE

Adjacent Node ID

2340

Transmissio n

ADJNODE

Adjacent Node Name

U_Transition_ 100

Transmissio n

ADJNODE

Transport Type

IP

Transmissio n

IPCLKLNK

Client IPv4

26.14.7.15

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 n

SCTPLNK

Application type

Add two SCTP links. Both peer IP addresses are 26.14.7.15. Peer ports are port 1024 and port 1025.

Transmissio n

IPPATH

Adjacent Node ID

2340

Transmissio n

IPPATH

IP path ID

1 2 3 4

Transmissio n Issue 01 (2015-12-30)

IPPATH

Interface Type


IUB

196


Domain



MOC

Parameter

Recomme nded Value

Transmissio n

IPPATH

Transport Type

IP

Transmissio n

IPPATH

IP path type

EF AF43 AF23 AF13

Transmissio n

IPPATH

Local IP address

26.14.1.1

Transmissio n

IPPATH

Peer IP address

26.14.7.15

Transmissio n

NODEBALGO PARA

NodeB Name

U_Transition_ 100

Transmissio n

NODEBALGO PARA

NodeB LDC algorithm switch

000000

Transmissio n

NODEBALGO PARA

NodeB Max HSDPA User Number

6144

Transmissio n

NODEBALGO PARA

NodeB Max HSUPA User Number

6144

Transmissio n

NODEBALGO PARA

HSUPA Credit Consume Type

MBR

Transmissio n

NODEBALGO PARA

NodeB Algorithm Enhancement Switch

0

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 Action

1

Radio

CELLLDR

DL LDR twelfth action

3

Radio

CELLLDR

DL LDR-BE rate reduction RAB number

1

Radio

CELLLDR

DL LDR un-ctrl RT Qos re-nego RAB num

BERateRed

Radio

CELLLDR

UL LDR third action

1

Issue 01 (2015-12-30)


197


Domain



MOC

Parameter

Recomme nded Value

Radio

CELLLDR

UL LDR fourth action

1

Radio

CELLLDR

UL LDR fifth action

3

Radio

CELLLDR

UL LDR sixth action

1

Radio

CELLLDR

UL LDR seventh action

3

Radio

CELLLDR

UL LDR eighth action

1

Radio

CELLLDR

UL LDR Ninth Action

1

Radio

CELLLDR

UL LDR-BE rate reduction RAB number

2

Radio

CELLLDR

UL LDR un-ctrl RT Qos re-nego RAB num

SF8

Radio

CELLLDR

UL PS should be HO user number

SF8

Radio

CELLLDR

UL LDR-AMR rate reduction RAB number

SF8

Radio

NODEBOLC

DL OLC released RAB number

1

Radio

NODEBOLC

UL OLC released RAB number

1

Radio

NODEBOLC

MBMS Services Number Released

1

Radio

NODEBOLC

Sequence of User Release

MBMS_REL



MOC

Parameter

Recommen ded Value

MPT

UMTS

MPT

Cabinet No.

0

MPT

MPT

Subrack No.

0

MPT

MPT

Slot No.

7

MPT

MPT

Board Type

WMPT

MPT

MPT

Enable Flag

ENABLE

Issue 01 (2015-12-30)


198


Domain



MOC

Parameter

Recommen ded Value

Baseband

BBP

Cabinet No.

0

Baseband

BBP

Subrack No.

0

Baseband

BBP

Slot No.

3

Baseband

BBP

Board Type

WBBP

Baseband

BBP

Work Mode

FDD

Baseband

BASEBANDE QM


0

Baseband

BASEBANDE QM


ULDL

Baseband

BASEBANDE QM


DEM_2_CHAN

Baseband

BASEBANDE QM


0, 0, 3

CPRI-based topology

RRUCHAIN

Three RRU 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.



MOC

Parameter

Recommen ded 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.

Issue 01 (2015-12-30)


199


Domain



MOC

Parameter

Recommen ded Value Local ports are port 1024 and port 1025.

Transmission

CPBEARER

Transmission

IUBCP

Add two CP bearers with two corresponding SCTP links. 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

Standby Status

MASETR

Transmission

OMCH

Local IP

26.14.7.15

Transmission

OMCH

Local Mask

Base Station Transport Data/OM Plane/*OmCh LocalMask

Transmission

OMCH

Peer IP

10.141.142.22

Transmission

DEVIP

IP Address

IP address: 160.70.7.10 Type: ETH

Transmission

NTPCP


10.141.142.22

Transmission

NTPCP

IP Mode

IPV4

Transmission

NTPCP

Synchronizatio n Period(min)

10

Transmission

NTPCP

Port Number

123

Transmission

NTPCP

Authentication Mode

PLAIN

Transmission

NTPCP

Master Flag

Master

Issue 01 (2015-12-30)


200


Domain



Transmission

MOC

Parameter

IPRT

Recommen ded Value Add two IP routes. Destination IP addresses: 170.179.179.34 10.0.0.0

Table 2.6 UMTS radio data configuration Domain


MOC

Parameter

Recommen ded Value

Antenna and feeder

UMTS

SECTOR

Sector Antenna

0, 4, 0, R0A; 0, 4, 0, R0B 0, 4, 2, R0A; 0, 4, 2, R0B 0, 4, 4, R0A; 0, 4, 4, R0B

Table 2.7 GSM equipment data configuration Domain


MOC

Parameter

Recommen ded Value

RF

GSM

BTSRXUBP

Working Standard

GSM_AND_U 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 (MOs) to be configured during the transition. Figure 4-7 shows the hardware configurations before and after mode transition. Figure 4-8 shows the transmission networking topology before and after mode transition.

Issue 01 (2015-12-30)


201





Issue 01 (2015-12-30)


202




Before Transition

After Transition

Mode

UMTS only single-mode

UMTS and LTE dual-mode


UMTS operating in the 1700 MHz frequency band, three sectors configured 1700 MHz: UMTS S2/2/2, 1T2R

UMTS and LTE operating in the 1700 MHz frequency band, three sectors 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


UMTS and LTE independent transmission through panel, IP over Ethernet

Clock networking

IEEE 1588 V2 reference clock

UMTS and LTE sharing an IEEE 1588 V2 reference clock



MOC

Parameter

Recommen ded Value

Globa l

LTE

CnOperator

CN Operator ID

0

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

Issue 01 (2015-12-30)


203


Dom ain



MOC

Parameter

Recommen ded Value

Server Clock

NTPCP


1

Clock

TASM

Clock Working Mode

MANUAL

Clock

TASM

Clock Source No.

0

Clock

TASM


PEERCLK

Trans missi on

ETHPORT

Port No.

0

Trans missi on

ETHPORT



Trans missi on

ETHPORT

Subboard Type

BASE_BOARD



MOC

Parameter

Recommend ed Value

Baseband

LTE

BBP

Cabinet No.

0

Baseband

BBP

Subrack No.

0

Baseband

BBP

Slot No.

2

Baseband

BBP

Board Type

LBBP

Baseband

BBP

Work Mode

FDD

CPRI-based topology

RRUCHAIN

RF

RRU

Issue 01 (2015-12-30)

Add an RRU chain on optical port 0 on the baseband processing board. Cabinet No./Subrack No./Slot No.


Add three cascaded RRUs to the new RRU chain.

204




MOC

Parameter

Recommen ded Value

Transmission

SCTPLNK


Add an LMPT to provide transmission ports.

Transmission

SCTPLNK


160.70.7.12

Transmission

SCTPLNK

Local SCTP Port No.

2913

Transmission

SCTPLNK


125.120.120.1

Transmission

SCTPLNK

Peer SCTP Port No.

2910

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


Corresponding to the cabinet No./subrack No./slot No. of the LMPT.

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.12

Transmission

IPPATH

Peer IP

171.23.36.1

Transmission

S1Interface

S1 Interface ID

0

Transmission

S1Interface


0

Transmission

S1Interface

CN Operator ID

0

Transmission

S1Interface

MME Release

Release_R10

Transmission

S1Interface


FALSE

Issue 01 (2015-12-30)



205


Domain



MOC

Parameter

Recommen ded Value

Transmission

S1Interface

Control Mode

MANUAL_MO DE

Transmission

OMCH

Standby Status

MASETR

Transmission

OMCH

Local IP

160.70.7.12

Transmission

OMCH

Local Mask

255.255.0.0

Transmission

OMCH

Peer IP

10.141.142.22

Transmission

OMCH

Peer Mask

255.255.0.0

Transmission

DEVIP


Corresponding to the cabinet No./subrack No./slot No. of the LMPT.

Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

ETH

Transmission

DEVIP

Port No.

0

Transmission

DEVIP

IP Address

160.70.7.12

Transmission

DEVIP

Mask

255.255.0.0

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.

Transmission

VLANMAP

Next Hop IP

160.70.7.12

Transmission

VLANMAP

Mask

255.255.0.0

Transmission

VLANMAP

VLAN Mode

SINGLEVLAN

Transmission

VLANMAP

VLAN ID

446

Transmission

VLANMAP

Set VLAN Priority

DISABLE

Issue 01 (2015-12-30)


206





MOC

Parameter

Recommen ded Value

Antenna and feeder

LTE

SECTOR

Sector ID

Add three sectors.


They use the 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.

Issue 01 (2015-12-30)


207



Table 2.6 UMTS data configuration Domain


MOC

Parameter

Recomme nded Value

RF

UMTS

RRU


UL

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 4-9 shows the hardware configurations before and after mode transition. Figure 4-10 shows the transmission networking topology before and after mode transition. Figure 1.1 Hardware configurations before and after mode transition

Issue 01 (2015-12-30)


208





Before Transition

After Transition

Mode





GSM and UMTS operating in the 900 MHz frequency band, three sectors configured; LTE operating in the 800 MHz frequency band, three sectors configured

900 MHz: GSM S2/2/2/, UMTS S2/2/2, 1T2R

900 MHz: GSM S2/2/2/, UMTS S2/2/2, 1T2R 800 MHz: LTE S1/1/1 (1x10 Issue 01 (2015-12-30)


209



Item

Before Transition

After Transition MHz), 2T2R

BBU

One BBU; GSM and UMTS sharing the same BBU

Two BBUs interconnected through UCIU+UMPT GSM and UMTS sharing the same BBU; LTE using the other BBU

RF typology


CPRI MUX topology for GSM and UMTS, intersubrack dual-star topology for LTE

Transmission scheme

Co-transmission through panel interconnection for GSM and UMTS, IP over Ethernet

Co-transmission through UMPT backplane interconnection, IP over Ethernet

Clock networking


GSM, UMTS, and LTE using an IEEE 1588 V2 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 2.2 LTE global data configuration Domain


MOC

Parameter

Recomme nded Value

Global

LTE

CnOperator

CN Operator ID

0

CnOperator

CN Operator name

LTE

CnOperator

CN Operator type

CNOPERATO R_PRIMARY

CnOperator

Mobile Country code

502

CnOperator

Mobile network code

04

Clock

TIMESRC

Time Source

NTP

Clock

NTPCP


10.141.142.22

Clock

NTPCP


1

Clock

TASM

Clock Working Mode

MANUAL

Clock

TASM

Clock Source No.

0

Clock

TASM


IPCLK

Issue 01 (2015-12-30)


210


Domain



MOC

Parameter

Recomme nded Value

Clock

TASM


FREQ

Clock

TASM

Quality Level

QL_PRC

Equipment

EQUIPMENT

Maintenance Mode

INSTALL



MOC

Parameter

Recommen ded Value

Equipment

LTE

SUBRACK

Cabinet No.

0

Equipment

SUBRACK

Subrack No.

1

Equipment

SUBRACK

Subrack Type

BBU3900

MPT

MPT

Cabinet No.

0

MPT

MPT

Subrack No.

1

MPT

MPT

Slot No.

7

MPT

MPT

Board Type

UMPT

MPT

MPT

Enable Flag

ENABLE

Baseband

BBP

Cabinet No.

0

Baseband

BBP

Subrack No.

0

Baseband

BBP

Slot No.

3

Baseband

BBP

Board Type

LBBP

Baseband

BBP

Work Mode

FDD

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 topology

RRUCHAIN

Issue 01 (2015-12-30)


Configure three RRU chains to optical ports 0 through 2 on the LBBP board. 211


Domain



MOC

RF

RRU

BBU interconnection

CTRLLNK

Parameter

Recommen ded Value 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.

Local Link No.

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. being 0, 0, and 4, respectively.


MOC

Parameter

Recommen ded Value

Transmission

ETHPORT



Transmission

ETHPORT

Subboard Type

BASE_BOARD

Transmission

DEVIP



Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

ETH

Transmission

DEVIP

Port No.

0

Issue 01 (2015-12-30)



212


Domain


MOC

Parameter

Recommen ded Value

Transmission

DEVIP

IP Address

160.70.7.10

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.

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

Transmission

SCTPLNK


The main control board in subrack 1 provides transmission ports.

Transmission

SCTPLNK


160.70.7.10

Transmission

SCTPLNK

Local SCTP

2913

Issue 01 (2015-12-30)



213


Domain



MOC

Parameter

Recommen ded Value

Port No. Transmission

SCTPLNK


125.120.120.1

Transmission

SCTPLNK

Peer SCTP Port No.

2910

Transmission

OMCH

Standby Status

MASETR

Transmission

OMCH

Local IP

160.70.7.10

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

IPPATH

Path ID

0

Transmission

IPPATH



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.10

Transmission

IPPATH

Peer IP

171.23.36.1

Transmission

CPBEARER

CP Bear No.

0

Transmission

CPBEARER

Flag

MASTER

Transmission

CPBEARER

Bear Type

SCTP

Transmission

CPBEARER

Link No.

0

Transmission

S1Interface

S1 Interface ID

0

Transmission

S1Interface


0

Transmission

S1Interface

CN Operator ID

0

Transmission

S1Interface

MME Release

Release_R10

Transmission

S1Interface


FALSE

Transmission

VLANMAP

Next Hop IP

160.70.7.10

Issue 01 (2015-12-30)


214


Domain



MOC

Parameter

Recommen ded Value

Transmission

VLANMAP

Mask

255.255.0.0

Transmission

VLANMAP

VLAN Mode

SINGLEVLAN

Transmission

VLANMAP

VLAN ID

446

Transmission

VLANMAP

Set VLAN Priority

DISABLE

Transmission

DHCPSVRIP



Transmission

DHCPRELAYS WITCH

DHCP Relay Switch

ENABLE

Transmission

DHCPSW


ENABLE

Transmission

DHCPSW

Vlanscan Switch

DISABLE



MOC

Parameter

Recommen ded Value

Antenna and feeder

LTE

SECTOR

Sector ID

Add three sectors.


They use the 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

Antenna and feeder

Issue 01 (2015-12-30)

SECTOREQM


Sector Equipment ID

Three pieces of sector equipment are 215


Domain



MOC

Parameter

Recommen ded 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

Radio

Cell

Three LTE cells 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. Baseband

Issue 01 (2015-12-30)


216


Domain



MOC

Parameter

Recommen ded Value equipment: share equipment 0.



MOC

CPRI-based topology

GSM

BTSRXUCHAI N

RF

BTSRXUBP

Parameter

Recommen ded Value Set the Access Type column in the BTS RXU Chain area to PEERPORT and the Head Board No. column to that of the WBBP in slot 3.

Working Standard

GSM_AND_U MTS_AND_LT E Note: The working mode the RF module must be changed to GUL.



MOC

Parameter

Recommen ded Value

Transmission

GSM

BTSDEVIP

Port Type

LOOPINTERF ACE

Transmission

BTSDEVIP



Transmission

BTSDEVIP

IP Address

88.200.8.236

Transmission

BTSIP


LOGICIP

Issue 01 (2015-12-30)


217


Domain



MOC

Parameter

Recommen ded Value

Transmission

BTSIP

BTS IP

88.200.8.236

Transmission

BTSIP

BSC IP

25.14.1.1

Transmission

BTSESN


21021127226T A9025307

Transmission

BTSESN

OM Bear Board

BACKBOARD

Transmission

BTSTUNNEL

--

From the GTMU to UMPT (LTE), the tunnel No. is 0.

Transmission

BTSIPRT


25.14.1.1 (BSC)

Transmission

BTSIPRT

Route Index

0

Transmission

BTSIPRT

Route Type

OUTIF

Transmission

BTSIPRT

Cabinet No./Subrack No./Slot No. of the ports


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


88.200.8.236

Transmission

IPRT

Next hop type

Gateway

Transmission

IPRT


25.14.0.1

Table 2.8 BSC data configuration Domain


MOC

Parameter

Recommen ded Value

Transmission

BSC

BTSDEVIP

Port Type

LOOPINTERF ACE

BTSDEVIP

*Port No.

0

Transmission Issue 01 (2015-12-30)


218


Domain



MOC

Parameter

Recommen ded Value

Transmission

BTSDEVIP


Corresponding to the cabinet No./subrack No./slot No. of the GTMU

Transmission

BTSDEVIP

IP Index

0

Transmission

BTSDEVIP

IP Address

88.200.8.236

Transmission

BTSDEVIP

IP Mask

255.255.255.0

Transmission

BTSDEVIP

BTS Inner IP Switch

NO

Transmission

BTSIP


LOGICIP

Transmission

BTSIP

BTS IP

88.200.8.236

Transmission

BTSIP

BSC IP

25.14.1.1

Transmission

BTSIP

BTS MultiIP Switch

NO

Transmission

BTSESN


21021127226T A9025307

Transmission

BTSESN

OM Bear Board

BACKBOARD

BBU interconnection

BTSTUNNEL

Source: GTMU Destination: UMPT The tunnel is used for backplane transmission interconnection.

Transmission

BTSIPRT

Route Index

1

Transmission

BTSIPRT


Device IP address of the BSC: 25.14.1.1

Transmission

BTSIPRT

Destination Address Mask

255.255.255.25 5

Transmission

BTSIPRT

Route Type

OUTIF

Transmission

BTSIPRT



Issue 01 (2015-12-30)


219


Domain



MOC

Parameter

Recommen ded Value

Transmission

BTSIPRT

Interface Type

TUNNEL

Clock

BTSCLK

Clock Type

PEER_CLK

Clock

BTSCLK

Peer Mode

LTE

Transmission

IPRT

Subrack No.

0

Transmission

IPRT

Slot No.

14

Transmission

IPRT


88.200.8.236

Transmission

IPRT

Destination address mask

255.255.255.25 5

Transmission

IPRT

Next hop type

Gateway

Transmission

IPRT


25.14.0.1

Transmission

IPRT

Priority

HIGH



MOC

Parameter

Recommen ded Value

Clock

UMTS

PEERCLK

Peer Clock No.

0

Clock

PEERCLK

Peer Standard

LTE

RF

RRU


Set the working mode of RRUs in subracks 60 through 62 to GUL.



MOC

Parameter

Recommen ded Value

Transmission

UMTS

DEVIP


Corresponding to the cabinet No./subrack No./slot No. of the WMPT

Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

LOOPINT

Issue 01 (2015-12-30)


220


Domain



MOC

Parameter

Recommen ded Value

Transmission

DEVIP

Port No.

0

Transmission

DEVIP

IP Address

88.200.8.238

Transmission

DEVIP

Mask

255.255.0.0

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

BBU interconnection

TUNNEL

The tunnel 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.

Local IP

Change it to an address on the LTE side.

Route Type: IF Port Type: TUNNEL Issue 01 (2015-12-30)


221


Domain



MOC

Parameter

Recommen ded Value

Transmission

IPRT

Destination IP

Configure a route from the RNC to the NodeB.

Transmission

NODEBIP

NodeB TransType

IPTRANS_IP

Transmission

NODEBIP

NodeB IP_TRANS IP address

88.200.8.238

Transmission

NODEBIP

NodeB IP_TRANS IP Mask

255.255.255.25 5

Transmission

NODEBIP

NodeB IP_TRANS Subrack No.

0

Transmission

NODEBIP

NodeB IP_TRANS Slot No.

14

Transmission

NODEBIP

Whether Binding logical port or not

NO

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 (MOs) to be configured during the transition. Figure 4-11 shows the hardware configurations before and after mode transition. Figure 4-12 shows the transmission networking topology before and after mode transition.

Issue 01 (2015-12-30)


222





Issue 01 (2015-12-30)


223




Before Transition

After Transition

Mode


Co-MPT GSM and LTE dual-mode

Service configurat ion

GSM only in the 1800 MHz frequency band, three sectors configured

GSM and LTE operating in the 1800 MHz frequency band, three sectors 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 typology

Star topology for GO RF modules

GL CPRI MUX topology

Transmiss ion scheme

IP over Ethernet

GSM and LTE co-transmission, IP over Ethernet

Clock networkin g

IP reference clock

Co-MPT GL synchronous Ethernet clock

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

Issue 01 (2015-12-30)


224



PlanningXLSVer

Plan Table Version

SRAN11.1

Description

BscSctpIdBase

Start BSC SCTPID Default value: 5000

5000

GSM parameter, which is mandatory

BtsSctpPortBase

Start SCTP port of a base station Default value: 8001

8001

GSM parameter, which is optional

BtsTrxPerSctp

Number of TRXs supported by each SCTP of a base station Default value: 12

12

GSM parameter, which is optional

BtsOMCHPeerIP

Peer IP address of the OM channel in a base station

10.141.14.22


BtsOMCHPeerIPMa sk

Peer IP mask of the OM channel in a base station

255.255.255.0


SRANBaselineRAT

Primary mode during the SRAN data merge. Default value: L

This parameter does not need to be set for single-mode base stations, and it is optional for MBTSs.

WORKMODE

Work mode Default value: E1_UNBA

Mandatory when E1/T1 transmission is used in GSM

ActBTSSoftwareVer sion

Version number of the activated GBTS evolution software (GTMU software of a special V900 version)

GSM evolution, mandatory

BSCNodeRedundan cyBSCName

Name of the currently reconstructed BSC in the BSC node redundancy scenario

Mandatory in the BSC node redundancy scenario

ActGTMUSoftwareV ersion

Version number of the activated GTMU SingleOM reconstruction software (GTMU software of a special V900 version)

GTMU SingleOM, mandatory

2. Filling in the SitePlanning page

Issue 01 (2015-12-30)


225



Table 2.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 base station

Fill in the table according to actual conditions.

GTMU Abandoned

Whether to abandon the GTMU for GSM after the conversion. Default value: NO

YES

UMPTSlot

Slot number of the GSM main control board after the conversion. Default value: 7

7

The following tables list the MOs involved in the mode transition from an eGBTS to GL coMPT in different domains. The data in these tables can be the references for data configuration in summary tables. Table 2.3 LTE global data configuration Dom ain


MOC

Parameter

Recommen ded Value

Globa l

LTE

CnOperator

CN Operator ID

0

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


10.141.142.22

Clock

NTPCP


1

Clock

TASM

Clock Working Mode

MANUAL

Clock

TASM

Clock Source No.

0

Clock

TASM


PEERCLK

Trans missi on

ETHPORT

Port No.

0

Trans missi

ETHPORT

Cabinet No./Subrack

Corresponding to those of the

Issue 01 (2015-12-30)


226


Dom ain



MOC

on Trans missi on

ETHPORT

Parameter

Recommen ded Value

No./Slot No.

main control board

Subboard Type

BASE_BOARD



MOC

Parameter

Recommend ed Value

Baseband

LTE

BBP

Cabinet No.

0

Baseband

BBP

Subrack No.

0

Baseband

BBP

Slot No.

3

Baseband

BBP

Board Type

UBBP

Baseband

BBP

Work Mode

FDD

CPRI-based topology

RRUCHAIN

RF

RRU


Put the RRU as RRU 0 in the RRU chain.

RF

RRU


GL

Move the RRU 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.



MOC

Parameter

Recommen ded Value

Transmission

LTE

SCTPLNK

Link No.

0

SCTPLNK

Cabinet No./Subrack

A new added UMPT provides

Transmission

Issue 01 (2015-12-30)


227


Domain



MOC

Parameter

Recommen ded Value

No./Slot No.

transmission.

Transmission

SCTPLNK


160.70.7.12

Transmission

SCTPLNK

Local SCTP Port No.

2913

Transmission

SCTPLNK


125.120.120.1

Transmission

SCTPLNK

Peer SCTP Port No.

2910

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


Corresponding to the cabinet No./subrack No./slot No. of the UMPT

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.12

Transmission

IPPATH

Peer IP

171.23.36.1

Transmission

S1Interface

S1 Interface ID

0

Transmission

S1Interface


0

Transmission

S1Interface

CN Operator ID

0

Transmission

S1Interface

MME Release

Release_R10

Transmission

S1Interface


FALSE

Transmission

OMCH

Standby Status

MASETR

Transmission

OMCH

Local IP

160.70.7.12

Transmission

OMCH

Local Mask

255.255.0.0

Issue 01 (2015-12-30)


228


Domain



MOC

Parameter

Recommen ded Value

Transmission

OMCH

Peer IP

10.141.142.22

Transmission

OMCH

Peer Mask

255.255.0.0

Transmission

DEVIP


Corresponding to the cabinet No./subrack No./slot No. of the UMPT

Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

ETH

Transmission

DEVIP

Port No.

0

Transmission

DEVIP

IP Address

160.70.7.12

Transmission

DEVIP

Mask

255.255.0.0

Transmission

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.

Transmission

VLANMAP

Next Hop IP

160.70.7.12

Transmission

VLANMAP

Mask

255.255.0.0

Transmission

VLANMAP

VLAN Mode

SINGLEVLAN

Transmission

VLANMAP

VLAN ID

446

Transmission

VLANMAP

Set VLAN Priority

DISABLE

Issue 01 (2015-12-30)


229





MOC

Parameter

Recommen ded Value

Antenna and feeder

LTE

SECTOR

Sector ID

Add three sectors.


They use the 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


Issue 01 (2015-12-30)


230



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 coMPT 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 4-13 shows the hardware configurations before and after mode transition. Figure 4-14 shows the transmission networking topology before and after mode transition. Figure 1.1 Hardware configurations before and after mode transition

Issue 01 (2015-12-30)


231





Before Transition

After Transition

Mode

UMTS only single-mode

Co-MPT GSM and UMTS dual-mode


UMTS operating in the 900 MHz frequency band, three sectors configured


900 MHz: UMTS S2/2/2, Issue 01 (2015-12-30)


232



Item

Before Transition

After Transition

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


GSM and UMTS cotransmission, IP over Ethernet

Clock networking

IEEE 1588 V2 reference 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 Table 2.2 Fields to be filled in the SitePlanning page Field

Description

Examples

ConvertFlag

Conversion ID

Yes

NodeBName

NodeB name

NodeB_XX

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 2.3 UMTS data configuration Domain


MOC

Parameter

Recommend ed Value

CPRI-based topology

UMTS

RRUCHAIN

-

The slot housing the board which provides RRU chain ports is changed from slot

Issue 01 (2015-12-30)


233


Domain



MOC

Parameter

Recommend ed Value

3 to slot 1. 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.

Baseband

BASEBANDE QM


0

Baseband

BASEBANDE QM


ULDL

Baseband

BASEBANDE QM


ULDL

Baseband

BASEBANDE QM


0,0,0;0,0,3



MOC

Parameter

Recommen ded Value

Transmission

GSM

ADJNODE

Adjacent Node ID

14410

GCELL

-

Three cells working on the 900 MHz frequency band

Radio

Values of Local Cell ID are 0, 1, and 2, respectively. Values of TRX Group ID are 441, 442, and 443, respectively. Transmission Issue 01 (2015-12-30)

SCTPLNK Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Application

ABISCP 234


Domain



MOC

Parameter

Recommen ded Value

type Transmission

SCTPLNK

SCTP link ID

1441

Transmission

SCTPLNK

Signalling link mode

SERVER

Transmission

SCTPLNK

First local IP address

25.14.1.1

Transmission

SCTPLNK

First destination IP address

25.14.24.141

Transmission

SCTPLNK

Destination SCTP port No.

1026

Transmission

IPPATH

Adjacent Node ID

14410

Transmission

IPPATH

Path ID

0

Transmission

IPPATH

Interface Type

ABIS

Transmission

IPPATH

Is eGBTS

Yes

Transmission

IPPATH

IP path type

QoS

Transmission

IPPATH

Local IP address

25.14.1.1

Transmission

IPPATH

Peer IP address

25.14.24.141



MOC

Parameter

Recommend ed Value

Equipment

GSM

BRI

-

Add a UBRI to slot 1.

CPRI-based topology

RRUCHAIN

-

Change the board providing RRU chain ports from the WBBP to the UBRIb for CPRI connection.

RF

RRU


GU

Issue 01 (2015-12-30)


235





MOC

Parameter

Recommen ded Value

Transmission

GSM

DEVIP



Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

ETH

Transmission

DEVIP

Port No.

0

Transmission

DEVIP

IP Address

25.14.24.141

Transmission

DEVIP

Mask

255.255.0.0

Transmission

VLANMAP

Next Hop IP

25.14.0.1

Transmission

VLANMAP

Mask

255.255.0.0

Transmission

VLANMAP

VLAN Mode

SINGLEVLAN

Transmission

VLANMAP

VLAN ID

457

Transmission

VLANMAP

Set VLAN Priority

DISABLE

Transmission

SCTPLNK

Link No.

0

Transmission

SCTPLNK



Transmission

SCTPLNK


25.14.24.141

Transmission

SCTPLNK

Local SCTP Port No.

1026

Transmission

SCTPLNK


25.14.1.1

Transmission

SCTPLNK

Peer SCTP Port No.

58080

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

Issue 01 (2015-12-30)


236


Domain



MOC

Parameter

Recommen ded Value transition. Otherwise, the original data will be overwritten.)

Transmission

CPBEARER

CP Bear No.

0 Note that the CP Bear No. cannot be the same as that of UMTS before transition. Otherwise, the original data will be overwritten.)

Transmission

CPBEARER

Flag

MASTER

Transmission

CPBEARER

Bear Type

SCTP

Transmission

CPBEARER

Link No.

0

Transmission

IPPATH

Path ID

0

Transmission

IPPATH



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

25.14.24.141

Transmission

IPPATH

Peer IP

25.14.1.1

Transmission

GBTSABISCP

Control Port ID

0

Transmission

GBTSABISCP

CP Bear No.

0

Table 2.7 GSM radio data configuration Domain


MOC

Parameter

Recommen ded Value

Antenna and feeder

GSM

SECTOR

Sector ID

Add three

Issue 01 (2015-12-30)


237


Domain



MOC

Parameter

Recommen ded Value

Sector Name

sectors.

Sector Antenna

They use the 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

Antenna and feeder

SECTOREQM

Sector Equipment ID

Three pieces of sector 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

Issue 01 (2015-12-30)


238


Domain



MOC

Parameter

Recommen ded 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 Mode

MAINDIVERS 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 Equipment ID

0, 1, and 2

Global

APPLICATION


INSTALL

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 4-15 shows the hardware configurations before and after mode transition. Figure 4-16 shows the transmission networking topology before and after mode transition.

Issue 01 (2015-12-30)


239




Issue 01 (2015-12-30)


240





Before Transition

After Transition

Mode

Separate-MPT GSM and UMTS dual-mode

G[U*L] multimode



GSM and UMTS operating in the 900 MHz frequency band, three sectors configured; GSM and LTE operating in the 1800 MHz

900 MHz: UMTS S1/1/1, Issue 01 (2015-12-30)


241



Item

Before Transition

After Transition

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 MHz)

Dual-star topology (GU 900 MHz) and CPRI MUX topology (GL 1800 MHz)

Transmission scheme

GSM E1 transmission, UMTS transmission through panel, IP over Ethernet

GSM E1 transmission remains unchanged. UMTS and LTE co-transmission through IP over Ethernet

Clock networking

GSM using the E1 reference clock, UMTS sharing the GSM reference clock

GSM using the E1 reference clock, UMTS and LTE sharing the GSM reference 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 Table 2.2 Fields to be filled in the SitePlanning page Field

Description

Examples

ConvertFlag

Conversion ID

Yes

NodeBName

NodeB name

NodeB_XX

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 2.3 GSM configuration Domain


MOC

Parameter

Recommen ded Value

Radio

GSM

GCELL

Freq. Band

Add three cells that are served by the DCS1800

Issue 01 (2015-12-30)


242


Domain



MOC

Parameter

Recommen ded Value frequency band.

Radio

TRXINFO

——


Radio

TRXBIND2PH YBRD

——


CPRI-based topology

BTSRXUCHAI N

——

Add three RFU 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/ AIRU Sending Receiving Mode

DOUBLEDOU BLE_ANTENN A

RF

BTSRXUBP

Working

GSM_AND_LT

Issue 01 (2015-12-30)


243



Domain


MOC

Parameter

Recommen ded Value

Standard

E

Table 2.4 LTE global data configuration Domain


MOC

Parameter

Recommen ded Value

Global

LTE

CnOperator

CN Operator ID

0

Global

CnOperator

CN Operator name

LTE

Global

CnOperator

CN Operator type

CNOPERATOR _PRIMARY

Global

CnOperator

Mobile Country code

502

Global

CnOperator

Mobile network code

04

Transmission

SCTPPEER


125.120.120.1

USERPLANEP EER

Peer IP Address

171.23.36.1

APPLICATIO N


Transmission Global

(To MME) (To S-GW) INSTALL



MOC

Parameter

Recommend ed Value

Equipment

LTE

eNodeBFuncti on

eNodeB ID

380

CPRIbased topology

RRUCHAIN

——

Add three RRU chains to optical 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

Issue 01 (2015-12-30)


244


Domain



MOC

Parameter

Recommend ed Value cabinet No./subrack No./slot No. of the three RRUs are as follows: 0/60/0 - 0/62/0 Working mode: GL

Baseband

BBP


GSM-0&UMTS1<E_FDD1<E_TDD-0



MOC

Parameter

Recommen ded Value

Transmission

LTE

SCTPLNK

Link No.

6

Transmission

SCTPLNK



Transmission

SCTPLNK


160.70.7.15

Transmission

SCTPLNK

Local SCTP Port No.

2913

Transmission

SCTPLNK


125.120.120.1

Transmission

SCTPLNK

Peer SCTP Port No.

2910

Transmission

CPBEARER

CP Bear No.

6

Transmission

CPBEARER

Flag

MASTER

Transmission

CPBEARER

Bear Type

SCTP

Transmission

CPBEARER

Link No.

6

Transmission

IPPATH

Path ID

6

Transmission

IPPATH



Issue 01 (2015-12-30)


245


Domain



MOC

Parameter

Recommen ded Value

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.15

Transmission

IPPATH

Peer IP

171.23.36.1

Transmission

S1Interface

S1 Interface ID

0

Transmission

S1Interface


6

Transmission

S1Interface

CN Operator ID

0

Transmission

S1Interface

MME Release

Release_R8

Transmission

S1Interface


FALSE

Transmission

DEVIP



Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

ETH

Transmission

DEVIP

Port No.

0

Transmission

DEVIP

IP Address

160.70.7.15

Transmission

DEVIP

Mask

255.255.0.0

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.

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

Issue 01 (2015-12-30)


246


Domain



Transmission

MOC

Parameter

Recommen ded Value

VLANMAP

Set VLAN Priority

DISABLE



MOC

Parameter

Recommen ded Value

Antenna and feeder

LTE

SECTOR

Sector ID

Add three sectors.



Antenna and feeder

SECTOREQM

Sector Equipment ID

Three pieces of sector 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

Issue 01 (2015-12-30)


247


Domain



MOC

Parameter

Recommen ded Value 5: 0,62,0,R0A,RX TX_MODE,M ASTER;0,62,0, R0B,RXTX_M ODE,MASTER

Radio

Cell

——


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 4-17 shows the hardware configurations before and after mode transition. Figure 4-18 shows the transmission networking topology before and after mode transition.

Issue 01 (2015-12-30)


248




Issue 01 (2015-12-30)


249





Before Transition

After Transition

Mode



Service configurati on


GSM and UMTS operating in the 900 MHz frequency band, three sectors configured; GSM and LTE operating in the 1800 MHz frequency band, three sectors configured

900 MHz: GSM S2/2/2/, UMTS S2/2/2, 1T2R

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 Issue 01 (2015-12-30)

One BBU; GSM and UMTS

Two BBUs interconnected through


250


Item


Before Transition

After Transition

sharing the same BBU

UMPT+UMPT GSM and UMTS sharing the same BBU; LTE using the other BBU

RF typology



Transmissi on scheme

GSM and UMTS independent transmission, IP over Ethernet

GSM and UMTS independent transmission, LTE co-transmission through backplane with a port on UMTS connected to the transport network, IP over Ethernet

Clock networkin g

GSM and UMTS using an independent IEEE 1588 V2 reference clock, respectively

GSM and UMTS using an independent IEEE 1588 V2 reference clock, respectively, LTE and UMTS sharing one IEEE 1588 V2 reference clock



MOC

Parameter

Recommen ded Value

Globa l

LTE

CnOperator

CN Operator ID

0

Globa l

CnOperator

CN Operator name

LTE

Globa l

CnOperator

CN Operator type

CNOPERATOR _PRIMARY

Globa l

CnOperator

Mobile Country code

502

Globa l

CnOperator

Mobile network code

04

Clock

TIMESRC

Time Source

NTP

Clock

NTPCP


10.141.142.22

Clock

NTPCP


1

Clock

TASM

Clock Working Mode

MANUAL

Clock

TASM

Clock Source No.

0

Clock

TASM


PEERCLK

Clock

TASM

Clock Synchronization

FREQ

Issue 01 (2015-12-30)


251


Dom ain



MOC

Parameter

Recommen ded Value

Mode Clock

TASM

Quality Level

QL_PRC

Clock

PEERCLK

Peer Standard

UMTS

Clock

PEERCLK

Peer Clock No.

0

Equip ment

EQUIPMENT

Maintenance Mode

INSTALL



MOC

Parameter

Recommend ed Value

MPT

LTE

MPT

Cabinet No.

0

MPT

MPT

Subrack No.

1

MPT

MPT

Slot No.

7

MPT

MPT

Board Type

LMPT

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

Equipment

CABINET

Cabinet No.

Cabinet No.: 0

Cabinet Type

Type: BTS3900

Cabinet No.

Cabinet No.: 0

Subrack No.

Subrack 0: BBU3900

Equipment

SUBRACK

Subrack Type


Issue 01 (2015-12-30)

RRUCHAIN

——


Three RRU chains are connected to three optical ports 0, 2, and 4 on the baseband processing board.

252


Domain



MOC

Parameter

Recommend ed Value

RF

RFU


Configure an RFU on the new RRU 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.

Antenna and feeder

RET

Device No.

0, 1, and 2

Antenna and feeder

RET

RET Type

SINGLE_RET

Antenna and feeder

RET

Polar Type

DUAL

Antenna and feeder

RET

Antenna Scenario

REGULAR

Antenna and feeder

RET


1

Antenna and feeder

RET


4

Antenna and feeder

RET


3, 4, and 5

Antenna and feeder

RETSUBUNIT

Device No.

0, 1, and 2

Antenna and feeder

RETSUBUNIT

Subunit No.

1

Antenna and feeder

RETSUBUNIT


Connect to the following: 0\4\3 R0A- 0\4\3 R0B 0\4\4 R0A0\4\4R0B 0\4\5 R0A- 0\4\5 R0B

Issue 01 (2015-12-30)


253





MOC

Parameter

Recommen ded Value

Transmission

LTE

SCTPLNK

Link No.

0

Transmission

SCTPLNK


0/1/7

Transmission

SCTPLNK


160.133.3.12

Transmission

SCTPLNK

Local SCTP Port No.

2913

Transmission

SCTPLNK


125.120.120.1

Transmission

SCTPLNK

Peer SCTP Port No.

2910

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


0/1/7

Transmission

IPPATH

Subboard Type

BACK_BOAR D

Transmission

IPPATH

Port Type

TUNNEL

Transmission

IPPATH

Port No.

0

Transmission

IPPATH

Path Type

ANY

Transmission

IPPATH

Local IP

160.133.3.12

Transmission

IPPATH

Peer IP

171.23.36.1

Transmission

S1Interface

S1 Interface ID

0

Transmission

S1Interface


0

Transmission

S1Interface

CN Operator ID

0

Transmission

S1Interface

MME Release

Release_R10

Transmission

S1Interface


FALSE

Issue 01 (2015-12-30)


254


Domain



MOC

Parameter

Recommen ded Value

Transmission

OMCH

Standby Status

MASETR

Transmission

OMCH

Local IP

160.133.3.12

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


0/1/7

Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

LOOPINT

Transmission

DEVIP

Port No.

0

Transmission

DEVIP

IP Address

160.133.3.12

Transmission

DEVIP

Mask

255.255.0.0

BBU interconnection

TUNNEL

——

The tunnel 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 interconnection

CTRLLNK

Local Link No.

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 UMPT whose cabinet No., subrack

Issue 01 (2015-12-30)


255


Domain



MOC

Parameter

Recommen ded Value No., and slot No. being 0, 0, and 7, respectively.

Transmission

ETHPORT

Port No.

0

Transmission

ETHPORT



Transmission

ETHPORT

Subboard Type

BASE_BOARD

Transmission



MOC

Parameter

Recommen ded Value

Antenna and feeder

LTE

SECTOR

Sector ID

Add three sectors.


They use the 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

Antenna and feeder

SECTOREQM

Sector Equipment ID

Three pieces of sector 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:

Issue 01 (2015-12-30)


256


Domain



MOC

Parameter

Recommen ded 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

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. Baseband equipment: share equipment 0.



MOC

Parameter

Recommen ded Value

CPRI-based topology

GSM

BTSRXUCHAI N

——

Configure three RRU chains on optical ports 1, 3, and 5 on the

Issue 01 (2015-12-30)


257


Domain



MOC

Parameter

Recommen ded Value GTMU.

RF

BTSRXUBRD

——

Added one MRRU to position 0 of each of the newly added three chains.

RF

BTSRXUBP

Working Standard

GSM_AND_LT 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

——


Radio

TRXBIND2PH YBRD

——




MOC

Parameter

Recommend ed Value

BBU interconnection

UMTS

CTRLLNK

Local Link No.

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 UMPT whose

Issue 01 (2015-12-30)


258


Domain



MOC

Parameter

Recommend ed Value

cabinet No., subrack No., and slot No. being 0, 0, and 7, respectively. BBU interconnection

TUNNEL

——

Add a tunnel to the UMPT_L board. The tunnel direction is uplink.

Transmission

IPRT

——

Configure IP routes. Configure a tunnel to the UMPT_L board.

Transmission

DHCPSVRIP


Set the IP address of the DHCP server to that of the U2000. The IP address is used for base station deployment.

Transmission

DHCPRELAY SWITCH

DHCP Relay Switch

ENABLE

Transmission

DHCPSW


ENABLE

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 4-19 shows the hardware configurations before and after mode transition. Figure 4-20 shows the transmission networking topology before and after mode transition.

Issue 01 (2015-12-30)


259




Issue 01 (2015-12-30)


260





Before Transition

After Transition

Mode

GU+L triple mode

GU+LT quadruple-mode

Service configurati on

GSM and UMTS operating in the 900 MHz frequency band, GSM and LTE operating in the 1800 MHz frequency band, three sectors configured

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

Issue 01 (2015-12-30)


261


Item


Before Transition

After Transition

900 MHz: GSM S2/2/2/, UMTS S2/2/2, 1T2R

configured

1800 MHz: GSM S2/2/2, LTE S1/1/1, 2T2R

900 MHz: GSM S2/2/2/, UMTS S2/2/2, 1T2R 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 through UCIU+UMPT

Two BBUs interconnected through UCIU+UMPT

GSM and UMTS sharing the same BBU; LTE using the other BBU

GSM and UMTS sharing the same BBU, LTE using the other BBU. The TDD mode is configured for the BBU of the eNodeB.

RF typology


Dual-star topology for both GU and GL RF modules, star topology for TDD RF modules

Transmissi on scheme

GSM and UMTS cotransmission through backplane interconnection and connected to LTE, IP over Ethernet

Remains the same.

Clock networkin g

GSM and UMTS share the LTE IEEE 1588v2 reference clock. The frequency synchronization mode is configured.

LTE uses the GPS reference clock and the clock synchronization mode is time synchronization. GSM and UMTS share the LTE reference clock. The time synchronization mode is configured for GSM and UMTS. For the clock changes, see the following descriptions.

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 2.2 BSC data configuration Domain


MOC

Parameter

Recommend ed Value

Clock

BSC

BTSCLK

CLKSYNCMODE

TIMESYN

Issue 01 (2015-12-30)


262





MOC

Parameter

Recommend ed Value

Clock

UMTS

TASM


TIME

Table 2.4 LTE global data configuration Dom ain


MOC

Parameter

Recommen ded Value

Clock

LTE

GPS

GPS Clock No.

0

Clock

GPS


0/1/0

Clock

CnOperator

Way to Get Position

AUTO_SEARC H

Clock

GPS

GPS Work Mode

GPS

Clock

GPS

Mobile network code

04

Clock

TASM

Clock Working Mode

MANUAL

Clock

TASM

Clock Source No.

0

Clock

TASM


GPS

Clock

TASM


TIME

Clock

TASM

Quality Level

QL-SSU-B



MOC

Parameter

Recommend ed Value

Equipment

LTE

USCU

Cabinet No.

0

Equipment

USCU

Subrack No.

1

Equipment

USCU

Slot No.

0

Equipment

USCU

Board Type

LMPT

Baseband

BBP

Cabinet No.

0

Issue 01 (2015-12-30)


263


Domain



MOC

Parameter

Recommend ed Value

Baseband

BBP

Subrack No.

1

Baseband

BBP

Slot No.

3

Baseband

BBP

Board Type

LBBP

Baseband

BBP

Work Mode

FDD

Equipment

CABINET

Cabinet No.

Cabinet No.: 0 and 1

Cabinet Type

Cabinet Type: BTS3900 Equipment

SUBRACK

Cabinet No.

Cabinet No.: 0

Subrack No.

Subrack 0: BBU3900

Subrack Type


RRUCHAIN

——

Three RRU chains are connected to optical fiber cables through three optical ports 3, 4, and 53 on the baseband board.

RF

RFU


One RRU is added to the new RRU chain. Working mode: TDL

Antenna and feeder

RET

Device No.

0, 1, and 2

Antenna and feeder

RET

RET Type

SINGLE_RET

Antenna and feeder

RET

Polar Type

DUAL

Antenna and feeder

RET

Antenna Scenario

REGULAR

Antenna and feeder

RET

Control Port Cabinet No./Subrack No./Slot No.

Cabinet No./Subrack No./Slot No. of the three new

Issue 01 (2015-12-30)


264


Domain



MOC

Parameter

Recommend ed Value

RRUs Antenna and feeder

RETSUBUNIT

Device No.

0, 1, and 2

Antenna and feeder

RETSUBUNIT

Subunit No.

1

Antenna and feeder

RETSUBUNIT


Connected to channels A and B of the three RRUs



MOC

Parameter

Recommen ded Value

Antenna and feeder

LTE

SECTOR

Sector ID

Add three sectors.


They use the 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

Antenna and feeder

SECTOREQM

Sector Equipment ID

Three pieces of sector equipment are added. They correspond to sectors 0 through 2. The following sector antennas are used:

Issue 01 (2015-12-30)


265


Domain



MOC

Parameter

Recommen ded Value 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; 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

Radio

Cell

——

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 Transmit and receive mode: 4T4R Working mode: UL_DL Sector equipment: corresponding to sector equipment 3 through 5. Baseband equipment:

Issue 01 (2015-12-30)


266


Domain



MOC

Parameter

Recommen ded Value share equipment 0.

Radio

CellOp

——

Add for cell 4 and cell 5. With the related parameters set 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 4-21 shows the hardware configurations before and after mode transition. Figure 4-22 shows the transmission networking topology before and after mode transition.

Issue 01 (2015-12-30)


267





Issue 01 (2015-12-30)


268




Before Transition

After Transition

Mode

LTE single-mode

Co-MPT GSM and LTE dual-mode

Service configurat ion

LTE operating in the 1800 MHz frequency band, three sectors configured

GSM and LTE operating in the 1800 MHz frequency band, three sectors 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 coMPT, GSM configured with the UBRIb

RF typology

Star topology for LO RF modules

GL CPRI MUX load sharing

Transmiss ion scheme

IP over Ethernet

GSM and LTE co-transmission, IP over Ethernet

Clock networkin g

Synchronous Ethernet clock

Co-MPT GL synchronous Ethernet clock

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 2.2 Filling in fields in the SitePlanning page Field

Description

Examples

ConvertFlag

Conversion ID

Yes

eNodeBName

eNodeB name

eNodeB_XX

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.

Issue 01 (2015-12-30)


269



Table 2.3 LTE data configuration Domain


MOC

Parameter

Recommend ed Value

RF

LTE

RRU


GL

RRUCHAIN

Topo Type

LOADBALANCE

CPRI-based topology



MOC

Parameter

Recommen ded Value

Transmission

BSC

ADJNODE

Adjacent Node ID

523

GCELL

——

Three cells working on the 1800 MHz frequency band

Radio

Local Cell ID: 3, 4, and 5 TRX Group ID: 0, 1, and 2 Transmission

SCTPLNK

Application type

ABISCP

Transmission

SCTPLNK

SCTP link ID

523

Transmission

SCTPLNK

Signalling link mode

SERVER

Transmission

SCTPLNK

First local IP address

25.14.1.1

Transmission

SCTPLNK

First destination IP address

25.14.7.10

Transmission

SCTPLNK

Destination SCTP port No.

1024

Transmission

IPPATH

Adjacent Node ID

523

Transmission

IPPATH

IP path ID

1

Transmission

IPPATH

Interface Type

ABIS

Transmission

IPPATH

Is eGBTS

Yes

Transmission

IPPATH

IP path type

QoS

Issue 01 (2015-12-30)


270


Domain



MOC

Parameter

Recommen ded Value

Transmission

IPPATH

Local IP address

25.14.1.1

Transmission

IPPATH

Peer IP address

25.14.7.10



MOC

Parameter

Recommend ed Value

Equipment

GSM

BRI

——

Add an UBRI board to slot 1.

CPRI-based topology

RRUCHAIN

——

Change Topo Type to LOAD BALANCE for the RRU chain and add CPRI ports to the UBRIb board.

RF

RRU


GL



MOC

Parameter

Recommen ded Value

Transmission

GSM

DEVIP



Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

ETH

Transmission

DEVIP

Port No.

0

Transmission

DEVIP

IP Address

25.14.7.10

Transmission

DEVIP

Mask

255.255.0.0

Transmission

VLANMAP

Next Hop IP

25.14.0.1

Transmission

VLANMAP

Mask

255.255.0.0

Transmission

VLANMAP

VLAN Mode

SINGLEVLAN

Issue 01 (2015-12-30)


271


Domain



MOC

Parameter

Recommen ded Value

Transmission

VLANMAP

VLAN ID

457

Transmission

VLANMAP

Set VLAN Priority

DISABLE

Transmission

SCTPLNK

Link No.

1

Transmission

SCTPLNK



Transmission

SCTPLNK


25.14.7.10

Transmission

SCTPLNK

Local SCTP Port No.

1024

Transmission

SCTPLNK


25.14.1.1

Transmission

SCTPLNK

Peer SCTP Port No.

58080

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.)

Transmission

CPBEARER

CP Bear No.

1 Note that the CP Bear No. cannot be the same as that of UMTS before transition. Otherwise, the original data will be overwritten.)

Transmission

CPBEARER

Flag

MASTER

Transmission

CPBEARER

Bear Type

SCTP

Issue 01 (2015-12-30)


272


Domain



MOC

Parameter

Recommen ded Value

Transmission

CPBEARER

Link No.

1

Transmission

IPPATH

Path ID

1

Transmission

IPPATH



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

25.14.24.141

Transmission

IPPATH

Peer IP

25.14.1.1

Transmission

GBTSABISCP

Control Port ID

0

Transmission

GBTSABISCP

CP Bear No.

1

Table 2.7 GSM radio data configuration Domain


MOC

Parameter

Recommen ded Value

Antenna and feeder

GSM

SECTOREQM

Sector Equipment ID

Three pieces of sector 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

Issue 01 (2015-12-30)


273


Domain



MOC

Parameter

Recommen ded 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 feeder

GTRXGROUP

TRX Group ID

0, 1, and 2

Radio

GTRXGROUP

Local Cell ID

3, 4, and 5

Radio

GTRXGROUP

Sector Equipment ID

3, 4, and 5

Note that the TRX group IDs must be consistent with those on the BSC side.

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 4-23 shows the hardware configurations before and after mode transition. Figure 4-24 shows the transmission networking topology before and after mode transition.

Issue 01 (2015-12-30)


274




Issue 01 (2015-12-30)


275




Issue 01 (2015-12-30)


276




Before Transition

After Transition

Mode





GSM and UMTS operating in the 900 MHz frequency band, three sectors configured; LTE operating in the 1800 MHz frequency band, three sectors configured

900 MHz: UMTS S2/2/2, GSM S2/2/2, 1T2R

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 separate service bearers, IP over Ethernet

GUL co-transmission and separate service bearers, IP over Ethernet

Clock networking


GSM, UMTS, and LTE sharing the IEEE 1588 V2 reference clock



MOC

Parameter

Recommen ded Value

Globa l

LTE

CnOperator

CN Operator ID

0

Globa l

CnOperator

CN Operator name

LTE

Globa l

CnOperator

CN Operator type

CNOPERATOR _PRIMARY

Globa l

CnOperator

Mobile Country code

502

Globa l

CnOperator

Mobile network code

04

Issue 01 (2015-12-30)


277


Dom ain



Globa l

MOC

Parameter

Recommen ded Value

APPLICATION


INSTALL



MOC

Parameter

Recommend ed Value

Equipment

LTE

eNodeBFunctio n

eNodeB ID

49122

Baseband

MDU


GSM-1&UMTS1<E_FDD1<E_TDD-0

Equipment

CABINET

Cabinet No.

5

Equipment

CABINET

Cabinet Type

VIRTUAL

Equipment

SUBRACK

Subrack No.

7

Equipment

SUBRACK

Subrack Type

PMU

Equipment

PMU

Cabinet No.

0

Equipment

PMU

Subrack No.

7

Baseband

PMU

Slot No.

0

Equipment

PMU

Manager Cabinet No.

0

Equipment

PMU

Manager Subrack No.

0

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 No.

8

Equipment

SUBRACK

Subrack Type

TCU

Equipment

TCU

Cabinet No.

10

Issue 01 (2015-12-30)


278


Domain



MOC

Parameter

Recommend ed Value

Equipment

TCU

Subrack No.

8

Equipment

TCU

Slot No.

0

Equipment

TCU

Manager Cabinet No.

0

Equipment

TCU

Manager Subrack No.

0

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 topology

RRUCHAIN

——

Add three RRU 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.



MOC

Parameter

Recommen ded Value

Transmission

LTE

SCTPLNK

Link No.

3

Transmission

SCTPLNK


0\0\6

Transmission

SCTPLNK


160.70.11.91

Transmission

SCTPLNK

Local SCTP

2913

Issue 01 (2015-12-30)


279


Domain



MOC

Parameter

Recommen ded Value

Port No. Transmission

SCTPLNK


125.120.120.1

Transmission

SCTPLNK

Peer SCTP Port No.

2910

Transmission

CPBEARER

CP Bear No.

3

Transmission

CPBEARER

Flag

MASTER

Transmission

CPBEARER

Bear Type

SCTP

Transmission

CPBEARER

Link No.

3

Transmission

IPPATH

Path ID

0

Transmission

IPPATH


0\0\6

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.11.91

Transmission

IPPATH

Peer IP

171.23.36.1

Transmission

S1Interface

S1 Interface ID

0

Transmission

S1Interface


3

Transmission

S1Interface

CN Operator ID

0

Transmission

S1Interface

MME Release

Release_R10

Transmission

S1Interface


FALSE

Transmission

DEVIP


0\0\6

Transmission

DEVIP

Subboard Type

BASE_BOARD

Transmission

DEVIP

Port Type

ETH

Transmission

DEVIP

Port No.

0

Transmission

DEVIP

IP Address

160.70.11.91

Transmission

DEVIP

Mask

255.255.0.0

Issue 01 (2015-12-30)


280


Domain



Transmission

MOC

Parameter

Recommen ded Value

IPRT

Route Index

Configure two IP routes. Destination IP addresses: 125.120.120.1 171.23.36.1 The route type is set to NEXTHOP.

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 Priority

DISABLE



MOC

Parameter

Recommen ded Value

Antenna and feeder

LTE

SECTOR

Sector ID

Add three sectors.



Antenna and feeder

SECTOREQM

Sector Equipment ID

Three pieces of sector equipment are added. They correspond to sectors 63

Issue 01 (2015-12-30)


281


Domain



MOC

Parameter

Recommen ded Value through 65. The following sector antennas 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

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

Issue 01 (2015-12-30)


282


Domain



MOC

Parameter

Recommen ded Value equipment 63 through 65.

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 4-25 shows the hardware configurations before and after mode transition. Figure 1.1 Hardware configurations before and after mode transition

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.

Table 1.1 Major differences before and after mode transition Item

Before Transition

After Transition

Mode

LTE FDD

LTE (FDD+TDD)

Service configuratio n

LTE FDD, one sector

LTE FDD, one sector; LTE TDD, one sector

2100 MHz (FDD): LTE 1, 20 MHz, 2T2R


BBU

The BBU works in LTE only mode.

The BBU works in LTE only mode. An LBBPd2 board is added to slot 2 and the BBU is configured to support TDD.

RF typology

RRU chain

RRU chain. A TDD RRU chain is added on the newly added LBBPd2 board.

Issue 01 (2015-12-30)

2300 MHz (TDD): LTE 1, 20 MHz, 4T4R


283



Item

Before Transition

After Transition

Transmissio n scheme

IP over Ethernet

Remains the same.

Clock networking

The IEEE 1588 V2 reference clock is used and the clock synchronization mode is frequency synchronization.

LTE uses the GPS reference clock and the clock synchronization mode is time synchronization. In this scenario, the GPS reference clock is used as an example. NOTE To use the IEEE 1588 V2 reference clock, change the clock synchronization mode to time synchronization.

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 1.2 Common data configuration Domain


MOC

Parameter Name

Recommend ed Value

Clock

LTE

GPS Clock Link

GPS Clock No.

0

Cabinet No.

0

Subrack No.

0

Slot No.

7

Way to Get Position

AUTO_SEARCH

Clock Working Mode

MANUAL(Manua l)

CLKSYNCMODE

TIME


GPS

TASM



MOC

Parameter Name

Recommend ed Value

Baseband

LTE

BBP

Cabinet No.

0

Subrack No.

0

Slot No.

2

Issue 01 (2015-12-30)


284


Domain

CPRI-based topology

RF

Issue 01 (2015-12-30)



MOC

RRUCHAIN

RRU

Parameter Name

Recommend ed Value

Board Type

LBBP

Work Mode

TDD

Administrative State

UNBLOCKED

Chain No.

1

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

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 postprocessing switch

OFF

VSWR alarm postprocessing threshold(0.1)

30

VSWR alarm threshold(0.1)

20


TDL


4

Number of TX

4


285


Domain



MOC

Parameter Name

Recommend ed Value

channels Frequency Min Bandwidth(kHz)

5000

Low Current Protect Switch

Enable



MOC

Parameter Name

Recommen ded 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

Radio

Issue 01 (2015-12-30)

Cell


Sector Equipment ID

1

Sector ID

1

Sector Equipment Antenna

0, 61, 0, R0A, RXTX_MODE, MASTER; 0, 61, 0, R0B, RXTX_MODE, MASTER; 0, 61, 0, R0C, RXTX_MODE, MASTER; 0, 61, 0, R0D, RXTX_MODE, MASTER

Local Cell ID

1

Cell Name

1

Csg indicator

BOOLEAN_FA LSE

Uplink cyclic prefix length

NORMAL_CP

Downlink

NORMAL_CP 286


Domain



MOC

Parameter Name

Recommen ded Value

cyclic prefix length

Issue 01 (2015-12-30)


Frequency band

40

Uplink EARFCN indication

NOT_CFG

Downlink EARFCN

38900

Uplink bandwidth

CELL_BW_N1 00

Downlink bandwidth

CELL_BW_N1 00

Cell ID

1

Physical cell ID

1

Cell active state

CELL_ACTIV E

Cell admin state

CELL_UNBLO CK

Cell FDD TDD indication

CELL_TDD

Subframe assignment

SA1

Special subframe patterns

SSP5

Cell specific offset(dB)

dB0

Frequency offset(dB)

dB0

Root sequence index

1

High speed flag

LOW_SPEED

Preamble format

0

Customized bandwidth configure indicator

NOT_CFG

287


Domain

Baseband

Radio



MOC

Cell sector equipment

CellOp

Parameter Name

Recommen ded Value

Emergency Area Id indicator

NOT_CFG

Ue max power allowed configure indicator

NOT_CFG

Flag of MultiRRU Cell

BOOLEAN_FA LSE

CPRI Compression

NO_COMPRE SSION

Air Cell Flag

BOOLEAN_FA LSE

Cell transmission and reception mode

4T4R

Work mode

UL_DL

Cell Standby Mode

ACTIVE

Intra Frequency RAN Sharing Indication

BOOLEAN_TR UE

Local cell ID

1

Sector equipment ID

1

Reference signal power(0.1dBm)

32767

Baseband equipment ID

255

Local cell ID

Add for cell 1. With the related parameters set as follows: Local tracking area ID: 1 Cell reserved for operator: CELL_NOT_R ESERVED_FO

Issue 01 (2015-12-30)


288


Domain



MOC

Parameter Name

Recommen ded Value R_OP

Local tracking area ID

1

Cell reserved for operator

0

Operator uplink RB used ratio(%)

16

Operator downlink RB used ratio(%)

16

MME configure number

CELL_MME_C FG_NUM_0

Operator Ue Number Ratio(%)

16

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 4-26 shows the hardware configurations before and after mode transition. Figure 1.1 Hardware configurations before and after mode transition

Issue 01 (2015-12-30)


289



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.

Table 1.1 Major differences before and after mode transition Item

Before Transition

After Transition

Mode

LTE TDD

LTE (FDD+TDD)

Service configuratio n

LTE TDD, one sector

LTE FDD, one sector; LTE TDD, one sector



BBU

The BBU works in LTE only mode.

The BBU works in LTE only mode. An LBBPd2 board is added to slot 2 and the BBU is configured to support FDD.

RF typology

RRU chain

RRU chain. An FDD RRU chain is added on the newly added LBBPd2 board.

Transmissio n scheme

IP over Ethernet

Remains the same.

Clock networking

LTE uses the GPS reference clock and the clock synchronization mode is time synchronization. In this scenario, the GPS reference clock is used as an example.

Remains the same.


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



MOC

Parameter

Recommend ed Value

Baseband

LTE

BBP

Cabinet No.

0

BBP

Subrack No.

0

BBP

Slot No.

2

BBP

Board Type

LBBP

BBP

Work Mode

FDD

Issue 01 (2015-12-30)


290


Domain



MOC

CPRI-based topology

RRUCHAIN

RF

RRU

Parameter

Recommend ed Value

Add an RRU to optical port 0 on the newly added baseband processing board. Cabinet No. Slot No.

One RRU in subrack 61 is added to the new RRU chain.

RRU

RRU type

LRRU

RRU


LO

RRU


Actual number of transmit and receive antennas used by RRUs. For example, 2.

Subrack No.




MOC

Parameter

Recommen ded Value

Baseband

LTE

SECTOR

Sector ID

1

SECTOR

Sector Antenna

0, 61, 0, R0A; 0, 61, 0, R0B

SECTOREQM

Sector Equipment ID

Add one sector equipment corresponding to the newly added sector. 1 is an example.

Sector ID

SECTOREQM

Radio

Cell

Sector Equipment Antenna

0, 61, 0, R0A; 0, 61, 0, R0B Add one FDD LTE cell: cell 1. The related key parameters are set as follows: FrequencyBand :7

Issue 01 (2015-12-30)


291


Domain



MOC

Parameter

Recommen ded Value DlEarfcn: 3000 DlBandwidth: CELL_BW_N1 00 UlBandwidth: CELL_BW_N1 00 FddTddInd: CELL_FDD Cell transmission and reception mode: 2T2R Work mode: UL_DL

EUCELLSECT OREQM

CellOp

Local cell ID Sector equipment ID

Corresponding to the cell and sector equipment Add for cell 1. With the related parameters set as follows: Local tracking area ID: 1 Cell reserved for operator: CELL_NOT_R ESERVED_FO R_OP

CnOperatorTa

Add for cell 1. With the related parameters set as follows:

Issue 01 (2015-12-30)




Local tracking area ID: 1



CN Operator ID: 0



Tracking area code: 11

292


5

5 Mode Transition Implementation

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.

Issue 01 (2015-12-30)


293



5.2 Procedure for Implementing Mode Transition Figure 1.1 The following figure describes the procedure for implementing mode transition.

Issue 01 (2015-12-30)


294


Issue 01 (2015-12-30)



295


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 6-1. Table 1.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, ALM28211 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

Issue 01 (2015-12-30)


296


6 Upgrading Base Station Software

Alarm Type

Alarm

Remarks

Parameter Settings Conflict, ALM-26274 Inter-System Board Object Configuration Conflict, and ALM-26277 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 1.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 interRAT

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. For details about local USBassisted deployment procedure, see section "USB+U2000-based Commissioning" 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).

Issue 01 (2015-12-30)


297


7 Preparing Data

7

Preparing Data

This section describes the procedure for preparing data during mode transition.

7.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.)

Issue 01 (2015-12-30)


298


7 Preparing Data

----End

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

Issue 01 (2015-12-30)


299


7 Preparing Data

Step 2 Right-click the MBSC to which the GBTS belongs and choose Synchronize NE Configuration Data.

Step 3 Synchronize the UMTS data to the U2000, right-click the NodeB and choose Synchronize NE Configuration Data.

Issue 01 (2015-12-30)


300


7 Preparing Data

Step 4 Double-click CME on the Application Center tab page.

Step 5 On the CME, choose Area Management > Current Area > Synchronize NEs to synchronize data to the U2000. Issue 01 (2015-12-30)


301


7 Preparing Data

Step 6 In the displayed Synchronize NE(s) dialog box, select the MBSC and base station to be synchronized.

Step 7 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.

Issue 01 (2015-12-30)


302


7 Preparing Data

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

7.3 Preparing Data for Co-MPT Reconstruction

If co-MPT reconstruction involves the GSM mode and the corresponding BSC works in redundancy backup mode, convert data based on the data planning tables of the primarily BSC and secondarily BSC. Start the Converting co-MPT Reconstruction Data in the standalone CME to convert data for Reconstructing Base Stations into Co-MPT Base Stations

Step 1 Choose SRAN Application > MBTS Application > Co-MPT Data Conversion from the menu bar to start the reconstruction wizard. Step 2 Perform the following operations as required.

Issue 01 (2015-12-30)


303


7 Preparing Data

Option

Description

The data planning file for base stations to be reconstructed is available

Clear Export file and click Next.

The data planning file for 1. Select Export file. base stations to be 2. Select the base station controller that the base stations to be reconstructed belong reconstructed is unavailable to and select the base station version. and you expect to export the The base station controller name is required only when GBTSs or separate-MPT file first and then modify base stations that contain GBTSs are to be reconstructed. data 3. Select base stations whose data you want to export from the base station list. 4. Click Next. 5. Click Edit File on the right of Planning data file. 6. Modify parameters in the data planning file as required, and then save and close the file. Step 3 Import the edited data planning file. a.

Specify save paths for the prepared data planning file, base station conversion component, and base station controller conversion component.

i.

Click Next.

Step 4 Set common parameters for site deployment and click Next. Common parameters include the subnet mask, area, ESN, and hot patch version. Step 5 The CME starts the reconstruction. When the reconstruction is successful, the CME generates site deployment lists, base station configuration files, and an incremental script for the base station controller. Then, click Finish. You can directly deliver the generated files to NEs for them to take effect. You can continue to modify data on the CME to adjust the reconstructed base stations, for example, to introduce RATs and reconstruct the transmission. After the data is modified, use the function of exporting auto-deployment data provided by the CME to export the site deployment lists and base station configuration files. If base station controller data is modified, you also have to export an incremental script for the base station controller. 

For details about how to export auto-deployment data, see Exporting Auto-Deployment Data Files (Standalone). Note that you need to select Reconstruct site when selecting a specific site deployment scenario, and load the site deployment list exported in 5.



For details about how to export an incremental script, see Exporting Incremental Scripts (Standalone).

separate-MPT to co-MPT reconstruction.

Issue 01 (2015-12-30)


304


7 Preparing Data

7.4 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 Preparing 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 Scena rio

Data Type

CME Template

Reference

GBTS

Equipment data

The CME template provides a method of configuring equipment data on the common configuration interface or the device panel of the LMT.

Adjusting RF Data (GBTS)

Transmissi on data

The CME template is used for inter-BSC reparenting based on the TDM and IP.

Adjusting GBTS Transmission Data

Radio data

a) Cell and neighbor relationships: The CME template is used as a data file for Radio Network Planning (RNP).

Adjusting GBTS Radio Data

b) Cell algorithm parameters: The CME template is used as a parameter file for radio network optimization (RNO). eGBTS

Equipment data

a) The CME template is used to configure the summary data file in batches (GSM application).

Adjusting Co-MPT Device Data

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 on data

a) Adjust the transmission data of the base station and controller together through batch adjustment over the Abis interface.

Adjusting Co-MPT Transmission Data

b) Adjust the transmission data of the base station through batch configuration of the summary data file (GSM application). Radio data

Issue 01 (2015-12-30)

The CME template is used for batch configuration of the summary data file.


Adjusting Co-MPT Radio Data

305


7 Preparing Data

7.4.2 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.

7.4.2.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 For details, see Importing and Exporting GBTS RF Adjustment Data (Based on RNCs of SRAN9.0 or Later Versions) (standalone function). Importing and Exporting GBTS Data for RF Adjustment 

Export a data file for GBTS RF adjustment.

Step 1 Start the function of exporting GBTS data for RF adjustment. a.

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.

j.

Select the version of the base station controller managing base stations to be reconfigured.

k.

Set the base station type to GBTS.

l.

Click Next to start the wizard of exporting GBTS data for RF adjustment.

Step 2 Verify the selected base station controller version in the NE version drop-down list. Step 3 Click Add. Three modes for selecting base stations are available. You can select one of them based on site requirements. For details about the modes, see Object Selection Modes. Step 4 Click Next and perform operations based on application scenarios. Scenario

Operation

Perform operations when a data file for RF adjustment has been prepared. Then, the CME exports base station

1. Select Summary data file.

Issue 01 (2015-12-30)

2. Specify save paths for both the prepared data file for RF adjustment


306


7 Preparing Data

Scenario

Operation

data based on the configuration objects in the prepared data file.

and the file where base station data is to be exported.

Perform operations when no data file for RF adjustment is prepared. Then, the CME exports base station data based on the configuration objects selected in the wizard.

1. Select Custom MOC. 2. Select configuration objects of the base stations to be exported and specify a save path of the file where the base station data is to be exported. NOTE: By default, the CME selects the minimum set of mandatory MOCs.

Step 5 Click Next. The CME starts the export. Step 6 After the export succeeds, click Finish. NOTE: 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.

Step 1 Start the function of importing GBTS data for RF adjustment. a. 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. a.

Select the version of the base station controller managing base stations to be reconfigured.

m.

Set the base station type to GBTS.

n.

Click Next to start the wizard of importing GBTS data for RF adjustment.

Step 2 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. Step 3 Select the data file for RF adjustment to be imported. Step 4 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. 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.

For details about rules for loading the file, see File Rules.

Issue 01 (2015-12-30)


307


7 Preparing Data

Step 5 Optional: Select Best effort. 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.

Step 6 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: NOTE: 

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.

a.

Specify a save path for scripts.

o.

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. i.

Select Yes.

ii.

Click Set Password. In the displayed dialog box, enter the encryption password as required. The password must contain 6 to 32 characters.

iii.

Click OK. The exported encrypted script files are in .ecf format.

p.

Optional: If you need to activate scripts immediately after the wizard is complete, select Launch the script executor if the task is successful.

Step 7 Click Next. A dialog box is displayed for you to set attributes. Set attributes based on Table 1. To set FH Attributes and Channel Rule, you need to click Advanced. Table 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

Issue 01 (2015-12-30)


308


7 Preparing Data

Table 1 Setting attributes Attribute

Description

generates a new ID by automatically adding 1 to the reference TRX ID and allocates the new 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: FH Attributes



The minimum ID available under the NE selected in the wizard functions as the start value by

The CME generates data based on the FH type in the data file for RF adjustment. If the default on the CME. FH type is not specified in the data file, the CME generates data based on the FH type  When the imported data file contains different NEs, the CME searches for available IDs from the selected in the wizard. preset start value and allocates them. NOTE:

Channel Rule



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.

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.

Issue 01 (2015-12-30)



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.



When Channel Allocation Rule 1 for TRXs is selected, the 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.


309


7 Preparing Data


Description 3.

Allocate SDCCHs: Based on the sequence of TRX numbers, 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.

Step 8 Click Next. The CME starts the import. If...

Then...

The import is successful

Click Finish.

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 locates the error data cell in the file. 2. Modify error data based on the error message. 3. After the modification, click Retry to import the file.

7.4.2.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: 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 For details about how to use the summary data file for batch configuration, see Importing and Exporting Co-MPT BTS Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 

Export base station data to the summary data file.

Issue 01 (2015-12-30)


310


7 Preparing Data

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 Bulk Configuration Data (U2000 client mode). A dialog box is displayed for you to configure data in batches, as shown in Figure 1. Figure 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 Importing and Exporting 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.

Issue 01 (2015-12-30)


311


7 Preparing Data

NOTE: To export data based on the objects contained in a prepared summary data file, perform the following steps: For details about the export mechanism, see Introduction to the Export Mechanism for Exporting Data Based On an Existing File. a.

Select Bulk configuration template.

b.

In Bulk configuration data file, select the prepared file and export configuration data from the CME based on the MOs in this file.

c.

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. 



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.

Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application > 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 GSM The CME starts the wizard for importing Abis interface data. For detailed operations, see base station controllers Importing and Exporting Abis Interface Data for Batch Reconfiguration . and base stations in the preceding step You have selected The CME starts the wizard for importing Iub interface data. For detailed operations, see UMTS base station Importing and Exporting Iub Data for Batch Reconfiguration . controllers and base stations in the preceding step You have selected only base stations in the preceding step

Issue 01 (2015-12-30)

The CME starts the wizard for importing base station data for batch configuration. The procedure is as follows: 1. Select the file you want to import and click Next.


312


If...

7 Preparing Data

Then... NOTE: The CME supports the file import even if the RAT contained in the file is 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: 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.

For details about how to adjust RF data using the summary data file, see Importing and Exporting Co-MPT BTS RF Adjustment Data (standalone function). Importing and Exporting Co-MPT Base Station Data for RF Adjustment 

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.

Issue 01 (2015-12-30)


313


7 Preparing Data

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.


Step 3 Click Next. Then, specify the export mode, summary data file, and export path. Table 3 Setting an export mode Export Mode

Operation

Custom MOC: Select objects you

1. Select Custom MOC.

want to export in the wizard directly and enable the CME to export data based on the selected objects.

2. Select objects to be exported. NOTE: The CME adds objects that support adjustment by default. You can adjust the objects as required.

3. Specify a save path for the exported files in Export path. RF adjustment template: Export

1. Select RF adjustment template. data based on the objects contained 2. Select the prepared summary data file for adjustment in RF adjustment in a prepared file. data file. 3. Specify a save path for the exported files in Export path. Step 4 Click Next. The CME starts the export. Step 5 Click Finish. 

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 Click Next, select the base stations for which you want to import the file. 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. 



Issue 01 (2015-12-30)


314


7 Preparing Data

Step 4 Optional: To generate configuration scripts in the wizard, select Export scripts and perform the following operations: Select the mode of generating scripts.

a.





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 on the base station side (only base stations in SRAN10.1 and later support splitting scripts by RRU chain/ring): To generate RRU incremental scripts in different files by RRU chain/ring, select Split scripts by RRU chain. The CME automatically generates common incremental scripts and RRU chain/ring incremental scripts. For base stations whose RRU chain/ring fails to be separated, the CME generates scripts that are not separated. NOTE: If the common incremental script of the base station depends on the incremental RRU chain/ring script or if two incremental RRU chain/ring scripts are associated, scripts cannot be separated by RRU chain/ring.



q.


r.

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. i.

Select Yes.

ii.


iii.


Step 5 Click Next, set the parameters for GSM service. Table 4 Setting attributes Attribute

Description

Cell ID


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

Issue 01 (2015-12-30)


315


7 Preparing Data


Description

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 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. FH Attributes

NOTE: The generates basedunder on the in the datawizard file for RF adjustment. the by  CME The minimum IDdata available theFH NEtype selected in the functions as the startIfvalue default on the CME. in the data file, the CME generates data based on the FH type FH type is not specified

selected in the the imported wizard. data file contains different NEs, the CME searches for available IDs from the  When preset start value and allocates them. 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. 

Channel Rule














Issue 01 (2015-12-30)






When Channel Allocation Rule 1 for TRXs is selected, the CME allocates only channels of new TRXs based on the following rules: 1.


2.

Allocate PDCCHs: PDCCHs are allocated to channels 6, 5, 7, 4, 3, 2, 1, and 0 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

316


7 Preparing Data


Description of a TRX in sequence. 3.


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.

Step 6 Click Next, when the import is complete, click Finish. 




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: In the error message list, you can: 





Follow-up Procedure If you select Split scripts by RRU chain in the wizard of importing RF adjustment data, you need to activate common incremental scripts of a single base station during script activation and then activate RRU chain/ring incremental scripts in sequence by task. The CME does not allow you to activate multiple scripts of a base station simultaneously. After activating a script, ensure that the script takes effect on the base station side and the base station is connected before activating the next script.

7.4.3 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.

7.4.3.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. The configuration procedure is as follows: Step 1 Customize and obtain the template files based on the mode transition planning results. Issue 01 (2015-12-30)


317


7 Preparing Data

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 For the method of adjusting data of a GBTS using TDM transmission, perform the following steps: 1. Export GBTS data. For details, see the exporting function in section Importing and Exporting GBTS Data (Summary) 

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. For details about the modes, see Object Selection Modes. Step 4 Click Next. A dialog box is displayed for you to specify a save path. NOTE: 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. NOTE: 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.



Import GBTS data.

Issue 01 (2015-12-30)


318


7 Preparing Data

NOTE: The CME provides the Export scripts in separate files based on GBTSs option for you to export scripts. You can export scripts to separate files based on GBTSs and export shared objects to a file.





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.

Step 1 On the menu bar of the planned data area, choose GSM Application > Import Data > Import GBTS Summary Data (CME client mode) or CME > GSM Application > Import Data > Import GBTS Summary Data (U2000 client mode). A dialog box is displayed for you to select a summary data file. Step 2 In the NE version and NE drop-down lists, select the base station controller to which base stations to be created belong and its version. Step 3 Select the summary data 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 4 Click Next and select base stations you want to create. 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.







Step 5 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:



a.


s.






Issue 01 (2015-12-30)

Select Yes.


319


7 Preparing Data

Click Set Password. In the displayed dialog box, enter the encryption password as required.

ii.

The password must contain 6 to 32 characters. Click OK.

iii.

The exported encrypted script files are in .ecf format.

Optional: If you need to activate scripts immediately after the wizard is complete, select Launch the script executor if the task is successful.

t.

Step 6 Click Next. A dialog box is displayed for you to set attributes. Step 7 Set BTS ID, Cell ID, and TRX ID based on the planned data. 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.

Step 8 (Optional) Click Advanced. The advanced settings dialog box is displayed. On the FH Attributes tab page, set the FH type based on the planned data and determine whether to use the FH for GSM bands differentiated by the P-GSM band and E-GSM band

a.

NOTE: 




The configuration of the FH in PGSM/EGSM frequency band parameter is as follows:










u.

On the Channel Rule tab page, set the channel allocation rule for cells.

v.

Click OK.


Then...


Click Finish.

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 locates the error data cell in the file.

Issue 01 (2015-12-30)


320


If...

7 Preparing Data

Then... 2. Modify error data based on the error message. 3. After the modification, click Retry to import the file.

"Importing and Exporting GBTS Data (Summary)." 2. Import the Abis interface data that has been reconfigured in batches. For details, see the importing function in section Importing and Exporting Abis Interface Data for Batch Reconfiguration 

Export the Abis interface data for batch reconfiguration.

Step 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. Step 2 Select the base station controller version, base station version, and related base station, 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: 





Step 3 Perform operations based on application scenarios. If you need to...

Then...

Select objects you want to export in the wizard directly 1. Select Custom MOC. and enable the CME to export data based on the selected 2. Select objects you want to export and specify a save objects. path for the exported file. NOTE: This mode does not apply to GBTSs.

Export data based on the objects contained in a prepared 1. Select Bulk configuration template. 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. Issue 01 (2015-12-30)


321


7 Preparing Data


Import the Abis interface data that has been reconfigured in batches.

Step 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. Step 2 Perform operations as required. If you need to...

Then...

Import the file only (without generating a script immediately when the export is successful)

Select the file you want to import and click Next. The CME starts to import the file.

Generate a script file immediately when the import is successful

1. Select the file you want to import and select Export script by wizard. 2. Click Next. 3. Set the script generation information.

NOTE:

a.

This mode does not apply to GBTSs.

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.

c.

Specify a save path for the script file.

d. (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.

Issue 01 (2015-12-30)

1.

Select Yes.

2.



322


If you need to...

7 Preparing Data

Then... The password must contain 6 to 32 characters. 3.

Click OK. The exported encrypted script files are in .ecf format. e.

(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.

f.

Click Next. The CME starts to import the data.

Step 3 View the import report and click Finish. "Importing and Exporting Abis Interface Data for Batch Reconfiguration." For the method of adjusting data of a GBTS using IP transmission, see Reparenting IP GBTS within BSC. Preparing Reparenting Scripts

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. NOTICE: 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.

Issue 01 (2015-12-30)


323


7 Preparing Data

7.4.3.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. 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 For details about how to use the summary data file for batch configuration (GSM application), see Importing and Exporting Co-MPT BTS Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 


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 Bulk Configuration Data (U2000 client mode). A dialog box is displayed for you to configure data in batches, as shown in Figure 1.

Issue 01 (2015-12-30)


324


7 Preparing Data

Figure 1 Exporting base station bulk configuration data









Step 3 Select Custom MOC, set objects you want to export, and specify a save path for the exported file. NOTE: To export data based on the objects contained in a prepared summary data file, perform the following steps: For details about the export mechanism, see Introduction to the Export Mechanism for Exporting Data Based On an Existing File.

Issue 01 (2015-12-30)


325


7 Preparing Data

a.


b.


c.







Then...


The CME starts the wizard for importing base station data for batch configuration. The procedure is as follows: 1. Select the file you want to import and click Next. NOTE: The CME supports the file import even if the RAT contained in the file is 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.

Issue 01 (2015-12-30)


326


If...

7 Preparing Data

Then... 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. 












For details about how to use the Abis batch adjustment data, see Importing and Exporting Abis Batch Adjustment Data. Importing and Exporting Abis Interface Data for Batch Reconfiguration 







Step 3 Perform operations based on application scenarios.

Issue 01 (2015-12-30)


327


7 Preparing Data

If you need to...

Then...


Export data based on the objects contained in a prepared 1. Select Bulk configuration template. 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. 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. 



Then...





NOTE:

a.



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

Issue 01 (2015-12-30)


328


If you need to...

7 Preparing Data

Then... may conflict after being imported into the CME.



b.


c.


d.

(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.





1.

Select Yes.

2.


3.



f.


Step 3 View the import report and click Finish.

7.4.4 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.

7.4.4.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. 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

Issue 01 (2015-12-30)


329


7 Preparing Data

The detailed operation is as follows: For details about the data file for RNP, see Importing and Exporting Radio Plan Data. Importing and Exporting Planned Radio Data 

Export the planned radio data.

Step 1 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. Step 2 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 Objects in Batches.

to load common objects in batches. For details, see Loading Common

Step 3 Click Next. A dialog box is displayed for you to select export options. Step 4 Select one or more data types as required. 

Select one or more external cell types in the External Cell Type area.



Set the neighboring cell data that you need to export in the Neighboring Relationship Type area. a.

Select one or more neighbor relationship types.

w.

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.

NOTE: 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.

Step 5 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.

Step 6 Click Next. The CME exports neighbor relationship and external cell data. Step 7 When the export is successful, click Finish.

Issue 01 (2015-12-30)


330


7 Preparing Data

NOTE: 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.



Import the planned radio data.

Step 1 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. Step 2 Select a base station controller version from the NE version drop-down list. Step 3 Select the file to be imported in TXT, XLS, or XLSM format. Step 4 Click Add File to add the modified radio network data planning file. Step 5 Click Next. A dialog box is displayed for you to select an import mode. Step 6 Select the type of the data to be imported and an import mode as required. For details, see Table 2. Table 2 Description of import modes Import Mode

Whether the Object Data Exists on the CME

Whether Data Result on the CME After File Import the Object Data Exists in the File

Append

Yes

Yes

The CME overwrites the existing data with 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.



If the external cells related to the neighbor relationships to be imported 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:

Issue 01 (2015-12-30)


331


7 Preparing Data

Table 2 Description of import modes Import Mode





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.

Yes

Yes

NOTE:  Neighbor relationships are No updated on a cell basis.


Yes

The CME adds the data in the file.

No

The CME deletes the existing data.

Yes

Yes


No

Yes


Yes

No


Update



External cells are Yes updated on a base station controller basis.

Delete

Step 7 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. 

Issue 01 (2015-12-30)

If the CME displays the error information link, click the link and reconfigure the


332


If...

7 Preparing Data

Then... 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 succeeds

Click Finish to exit.

NOTE: 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.

For details about inter-BSC reparenting based on the TDM and IP, see Importing and Exporting Radio Network Optimization Data. Importing and Exporting Radio Network Optimization Data 

Export radio network optimization data

Step 1 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.

NOTE: Export *** can be Export Cell Parameter Data, Export Cell Frequency Data, and Export Neighboring Cell BA Data.

Step 2 Select cells whose data you want to export. If you need to...

Then...

Export data of all cells under an NE

1. Choose NE from the Selected by drop-down list. 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. You can click to load common objects in batches. For details, see Loading Common Objects in Batches.

Export data of certain cells under 1. Choose Cell from the Selected by drop-down list. 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

Issue 01 (2015-12-30)


333


If you need to...

7 Preparing Data

Then... Selection Modes.

NOTE: When you choose Export Cell Frequency Data, to filter other frequencies than those used by the TRXs and FH groups, select Remove redundant frequencies.

Step 3 (Optional and required when you choose Export Cell Parameter Data) Click Next. Select parameters you want to export, and click

.

NOTE: 



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.

Step 4 Click Next, and perform related operations based on the type of the data and file to be exported. Data Type File Type Export Cell Parameter Data

Operations

Negotiated 1. Select the file to be exported in TXT, XLS, or XLSM format. data file  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.




2. Specify a save path for the file to be exported. Negotiated 1. Select the file to be exported in TXT, XLS, or XLSM format. Export Neighboring data file  XLS and XLSM files contain all the configuration objects. Each configuration Cell BA Data 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 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. The TXT file name must not be changed. Otherwise, the CME fails to process data in the file during the import.



Issue 01 (2015-12-30)

If the data to be exported exceeds 65,535 rows, save the data as a TXT or an XLSM Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

334


Data Type File Type

7 Preparing Data

Operations

file. 2. Specify a save path for the file to be exported. Export Cell Frequency Data

Negotiated 1. Set the export type to Negotiated Data. data file 2. Select the file to be exported in TXT, XLS, or XLSM format. 

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 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. The TXT file name must not be changed. Otherwise, the CME fails to process data in the file during the import.




3. Specify a save path for the file to be exported. Summary data file

1. Set the export type to Summary Data. 2. Select the path of the summary data 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. If the data to be exported exceeds 65,535 rows, save the data as an XLSM file. 4. Specify a save path for the file to be exported.

Step 5 Click Next. The CME starts to export the data. Step 6 When the export is successful, click Finish. NOTE: 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.



Import radio network optimization data.

Step 1 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.

Issue 01 (2015-12-30)


335


7 Preparing Data

NOTE: Import *** can be Import Cell Parameter Data, Import Cell Frequency Data, and Import Neighboring Cell BA Data.

Step 2 Select a base station controller version from the NE version drop-down list. NOTE: If the file format of Import Cell Frequency Data is XLS or XLSM, no NE version needs to be specified.

Step 3 Select the file to be imported in TXT, XLS, or XLSM format. Step 4 Click Add File to add the modified files. NOTE: 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.

Step 5 Click Next, and perform related operations based on the type of the data to be imported. Data Type

Operations



Import Cell Parameter Data  Import Cell Frequency Data

The CME starts to import and verify the data.

Import 1. Select either of the following modes as required: Neighboring  Append: adds or modifies neighboring cell BA data. The CME overwrites Cell BA Data

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 data in the imported file.

2. Click Next. The CME starts to import and verify the data. Step 6 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 succeeds

Issue 01 (2015-12-30)

Click Finish to exit.


336


7 Preparing Data

7.4.4.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. 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 For details, see Importing and Exporting Co-MPT BTS Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 



Issue 01 (2015-12-30)


337


7 Preparing Data











Issue 01 (2015-12-30)


338


7 Preparing Data

a.


b.


c.







Then...



Issue 01 (2015-12-30)


339


If...

7 Preparing Data













7.4.5 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: 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 For the details, see Introducing RATs to Co-MPT Base Stations in Batches. Introducing RATs to Co-MPT Base Stations in Batches 

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. For details about how to customize a summary data file, see Manually Customizing a Summary Data File. In RAT introduction scenarios, you need to customize application maintenance mode parameters, including AT and APPMNTMODE, of each RAT to a summary data file. 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.

Issue 01 (2015-12-30)


340


7 Preparing Data

Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application > Export Data > Export Base Station Multimode Expansion Data (CME client mode) or CME > SRAN Application > MBTS Application > Export Data > Export Base Station 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 1. Figure 1 Export expansion data

NOTE: 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 a summary data file has been prepared. Then, the CME exports base station data based on the configuration objects in the prepared summary data file.

1. Select Summary data file. 2. Specify save paths for both the prepared summary data file and the file where base station data is to be exported.

Custom MOC: Select this option when no summary 1. Select Custom MOC. data file is prepared. Then, the CME exports base station 2. Select configuration objects of the base stations to be data based on the configuration objects selected in the exported and the save path for the file where the base wizard. station data is to be exported. Step 4 Click Next. The CME starts to export the data. Step 5 After the export is complete, click Finish.

Issue 01 (2015-12-30)


341


7 Preparing Data

NOTE: After the export is complete, you can click the link in the dialog box to open the exported file. 



Configure data in the exported file. 

Summary data file, see Editing a Summary Data File (Customization Tool-based).



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. Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application > Import Data > Import Base Station Multimode Expansion Data (CME client mode) or CME > SRAN Application > MBTS Application > Import Data > Import Base Station Multimode Expansion Data (U2000 client mode). A dialog box is displayed for you to 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 summary 1. Click Next and select base stations you want to create. data file contains only data 2. (Optional) Select Best Effort. about base stations NOTE:

The imported summary data file contains data about both base station controllers and 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.




1. Click Next and select base stations you want to create. 2. (Optional) Select Best Effort. NOTE: 





3. Optional: To generate configuration scripts in a wizard, select Export scripts and perform the following operations: 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.


4. (Optional) Set an encryption mode for exported scripts.

Issue 01 (2015-12-30)






Yes: The exported scripts have encryption passwords. When loading projects, you have to enter encryption passwords by performing the following operations: Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

342


If...

7 Preparing Data

Then... 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.


3.


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 succeeds

Click Finish to exit the wizard.

The import fails

1. View the failure report, or double-click the error message in the error list 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.

Follow-up Procedure After introducing RATs to the base station, use the function of exporting auto-deployment files to export the deployment list and data configuration file in the RAT introduction scenario. For detailed operations, see Exporting Files Related to Base Station Creation/RAT Introduction to Co-MPT Base Stations. NOTE: You can use either of the following methods to adjust other data after introducing RATs to a base station:

Issue 01 (2015-12-30)



Export the deployment list and data configuration file for RAT introduction, and deliver them to the live network for them to take effect. Then synchronize the data to the planned data area, adjust other data, and then export an incremental script.



Do not export the deployment list and data configuration file for RAT introduction. Instead, continue adjusting other data, and then use the function of exporting the site deployment list and data configuration files to combine and export data in the RAT introduction and adjustment scenarios.


343


7 Preparing Data

7.5 Configuring UMTS Data This section describes how to prepare and adjust UMTS data when UMTS is used as the original and new modes. The following table list the configuration method when UMTS works as the original mode. Table 1.1 UMTS working as the original mode Scena rio

Data Type

CME Template

Reference

Separate -MPT

Equipment data

a) The CME template is used to configure the summary data file in batches (UMTS application).

Adjusting Separate-MPT Device Data


a) Adjust the transmission data of the base station and controller together through batch adjustment over the Iub interface.

Adjusting Separate-MPT Transmission Data

b) Adjust the transmission data of the base station through batch configuration of the summary data file (UMTS application).

CoMPT

Radio data

The CME template is used to configure the summary data file in batches (UMTS application).

Adjusting Separate-MPT Radio Data

Equipment data

a) The CME template is used to configure the summary data file in batches (SRAN application).



The CME template is used to configure the summary data file in batches (SRAN application).


Radio data



The following table list the configuration method when UMTS works as the new mode.

Issue 01 (2015-12-30)


344


7 Preparing Data

Table 1.2 UMTS working as the new mode Scena rio

Data Type

CME Template

Reference

Separate -MPT

Equipment, transmissio n, and radio data

The CME template is used to deploy a new site using the summary data file. In this scenario, the equipment, transmission, and radio data shares one summary data file.

Configuring Separate-MPT Data

CoMPT


The CME template is used to introduce RATs using the summary data file (SRAN application).

Configuring CoMPT Data

7.5.2 Preparing Equipment Data This section describes how to adjust equipment data in co-MPT and separate-MPT scenarios when the original mode is UMTS. The equipment data to be adjusted includes the antenna and feeder, BBU, RXU, and CPRI.

7.5.2.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 board/TRX/cell capacity) needs to be adjusted, you can adjust RF data using the summary data file. 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 For details about how to use the summary data file for batch configuration, see Importing and Exporting NodeB Batch Configuration Data. Importing and Exporting NodeB Data for Batch Configuration 

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 mode). A dialog box is displayed for you to export the data you want to reconfigure in batches, as shown in Figure 1.

Issue 01 (2015-12-30)


345


7 Preparing Data


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. Step 4 Select Custom MOC, set objects you want to export, and specify a save path for the exported file. NOTE: To export data based on the objects contained in a prepared summary data file, perform the following steps: For details about the export mechanism, see Introduction to the Export Mechanism for Exporting Data Based On an Existing File. a.


b.


c.


Step 5 Click Next. The CME verifies the configuration data to be exported. If the verification fails, the CME does not export data. Step 6 After the export is complete, click Finish. 

Open the exported summary data file and modify the file as planned.

Issue 01 (2015-12-30)


346


7 Preparing Data

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). 

Import NodeB data for batch reconfiguration. Step 1 On the menu bar of the planned data area, choose UMTS Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode) or CME > UMTS 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 the file you want to import and click Next. Step 3 Select base stations whose data you want to import, 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. 


Step 4 After the import is complete, click Finish. 









For details about how to adjust RF data using the summary data file, see Importing and Exporting NodeB RF Adjustment Data (standalone function). Importing and Exporting Co-MPT Base Station Data for RF Adjustment 



Select Co-MPT BTS RF Adjustment from the Scenario drop-down list.







Issue 01 (2015-12-30)


347


7 Preparing Data

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








Operation








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 Click Next, select the base stations for which you want to import the file. 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.

Issue 01 (2015-12-30)


348


7 Preparing Data









a.













x.


y.






Select Yes.

ii.


The password must contain 6 to 32 characters. iii.


Step 5 Click Next, set the parameters for GSM service.

Issue 01 (2015-12-30)


349


7 Preparing Data


Description

Cell ID


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 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. 

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: 




Channel Rule














Issue 01 (2015-12-30)






When Channel Allocation Rule 1 for TRXs is selected, the CME allocates


350


7 Preparing Data


Description only channels of new TRXs based on the following rules: 1.


2.


3.














7.5.2.2 Co-MPT When the original mode is UMTS, you need to use the summary data file for batch configuration (SRAN 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. The configuration procedure is as follows: Step 1 Customize and obtain the summary data file based on the mode transition planning results.

Issue 01 (2015-12-30)


351


7 Preparing Data

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 For details about how to use the summary data file for batch configuration (SRAN application), see Importing and Exporting Co-MPT BTS Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 




Issue 01 (2015-12-30)

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


352


7 Preparing Data

single-mode base station. For detailed operations, see Importing and Exporting Abis Interface Data for Batch Reconfiguration. 






b.


c.


d.



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. Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application > 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 GSM The CME starts the wizard for importing Abis interface data. For detailed operations, see base station controllers Importing and Exporting Abis Interface Data for Batch Reconfiguration . and base stations in the preceding step Issue 01 (2015-12-30)


353


If...

7 Preparing Data

Then...

You have selected The CME starts the wizard for importing Iub interface data. For detailed operations, see UMTS base station Importing and Exporting Iub Data for Batch Reconfiguration . controllers and base stations in the preceding step You have selected only base stations in the preceding step

















Issue 01 (2015-12-30)

Select Co-MPT BTS RF Adjustment from the Scenario drop-down list. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

354


7 Preparing Data

















Operation









Issue 01 (2015-12-30)


355


7 Preparing Data









a.













z.


aa.






Select Yes.

ii.


iii.



Issue 01 (2015-12-30)


356


7 Preparing Data


Description

Cell ID


TRX ID


FH Attributes






Channel Rule














Issue 01 (2015-12-30)








357


7 Preparing Data




2.


3.














7.5.3 Preparing Transmission Data This section describes how to adjust equipment data in co-MPT and separate-MPT scenarios when the original mode is UMTS. The transmission data to be adjusted includes the following MOs: IP, IPPATH, SCTPLINK, CPBEAR, and IPRT.

7.5.3.1 Separate-MPT 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 Issue 01 (2015-12-30)


358


7 Preparing Data

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. 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 For details about how to use the summary data file for batch configuration (UMTS application), see Importing and Exporting NodeB Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 



Issue 01 (2015-12-30)


359


7 Preparing Data









Step 3 Select Custom MOC, set objects you want to export, and specify a save path for the exported file. NOTE: To export data based on the objects contained in a prepared summary data file, perform the following steps: For details about the export mechanism, see Introduction to the Export Mechanism for Exporting Data Based On an Existing File. a.


b.


c.






Import the modified summary data file. Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application > 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.

Issue 01 (2015-12-30)


360


If...

7 Preparing Data

Then...















For details about how to use the Iub batch configuration data, see Exporting Iub Batch Configuration Data Exporting Iub Data for Batch Reconfiguration

Step 1 On the menu bar of the planned data area, choose UMTS Application > Export Data > Export Iub Bulk Configuration Data (CME client mode) or CME > UMTS Application > Export Data > Export Iub Bulk Configuration Data (U2000 client

Issue 01 (2015-12-30)


361


7 Preparing Data

mode). A dialog box is displayed for you to export Iub bulk configuration data, as shown in Figure 1. Figure 1 Exporting Iub bulk configuration data

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 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. If you need to...

Then...

Export Iub data about both the base station controller and NodeBs

1. Select UMTS controller and select a base station controller version. 2. Select NodeB and select a NodeB version. NOTE: 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: 

Issue 01 (2015-12-30)

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.


362


If you need to...

7 Preparing Data

Then... 



Export Iub data only about the base station controller

1. Select UMTS controller and select a base station controller version. 2. Clear NodeB. 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 you expect to export data based on the objects contained in the file

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.

NOTE: 

The NE version in the Cover sheet of the selected file must be the same 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 1. Select Custom MOC. available 2. (Optional and required only when the base station controllers are in RAN16.0 and Issue 01 (2015-12-30)


363


If...

7 Preparing Data

Then... 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. 3. 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.

Step 5 Click Next. The CME verifies the configuration data to be exported. If the verification fails, the CME does not export data. Step 6 After the export is complete, click Finish.

Importing Iub Batch Configuration Data Importing Iub Data for Batch Reconfiguration

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

Configuration scripts do not need to be generated

Clear Export script by wizard and click Next.

Configuration scripts need to be generated

Select Export script by wizard and click Next. Then, set the sequence for generating scripts as required. 1. 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 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.

Issue 01 (2015-12-30)


364


If...

7 Preparing Data

Then... 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. 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: 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.


3.


Step 3 (Optional) Set information about transport data reconfiguration as required. If...

Then...

The NodeB in the selected file contains only Iub data on the RNC side and you need to enable automatic update of the Iub data on the NodeB side based on the control plane IP address, user plane IP address, OMCH IP address, and NodeB ATM address for the Iub interface on the RNC side

Select Update ATM/IP address from RNC to the NodeB that does not exist in the summary/IUB file.

Delete the existing transport data of the Iub interface and reconfigure the data based on the transport data in the summary data file



This option is available only when the imported file contains only controller data.



This function is available only when the following condition is met: On the RNC, the 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.

Select Overwrite the Iub data (Do not inherit the MOCs those do not exist in the summary file).

Step 4 Click Next. The CME starts to import data. Issue 01 (2015-12-30)


365


If...

Then...


Click Finish.

7 Preparing Data

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:

The import fails



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.


7.5.3.2 Co-MPT When the original mode is UMTS, you need to use the summary data file for batch configuration (SRAN application) on the CME to configure transmission 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 For details, see Importing and Exporting Co-MPT BTS Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 



Issue 01 (2015-12-30)


366


7 Preparing Data











Issue 01 (2015-12-30)


367


7 Preparing Data

a.


b.


c.







Then...



Issue 01 (2015-12-30)


368


If...

7 Preparing Data













7.5.4 Preparing Radio Data This section describes how to adjust radio data in co-MPT and separate-MPT scenarios when the original mode is UMTS. The radio data to be adjusted includes the MOs related to the cell, TRX, and sector.

7.5.4.1 Separate-MPT 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. 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 For details, see Importing and Exporting NodeB Batch Configuration Data. Importing and Exporting Abis Interface Data for Batch Reconfiguration 


Step 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 Issue 01 (2015-12-30)


369


7 Preparing Data

client mode). A dialog box is displayed for you to export the data you want to reconfigure in batches. Step 2 Select the base station controller version, base station version, and related base station, 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: 






Then...


Export data based on the objects contained in a prepared 1. Select Bulk configuration template. 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. 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. 


Step 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. Step 2 Perform operations as required.

Issue 01 (2015-12-30)


370


7 Preparing Data

If you need to...

Then...





NOTE:

a.






b.


c.


d.


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.


3.



f.



Issue 01 (2015-12-30)


371


7 Preparing Data

7.5.4.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. 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 For details, see Importing and Exporting Co-MPT BTS Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 



Issue 01 (2015-12-30)


372


7 Preparing Data











Issue 01 (2015-12-30)


373


7 Preparing Data

a.


b.


c.







Then...



Issue 01 (2015-12-30)


374


If...

7 Preparing Data













7.5.5 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. 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 following table lists the corresponding CME template and reference for each scenario. Table 1.1 UMTS working as the new mode Scena rio

Data Type

CME Template

Reference

Separate -MPT


The CME template is used to deploy a new site using the summary data file. In this scenario, the equipment, transmission, and radio data shares one summary data file.

Configuring Separate-MPT Data

Issue 01 (2015-12-30)


375


7 Preparing Data

Scena rio

Data Type

CME Template

Reference

CoMPT



Configuring CoMPT Data

7.5.5.2 Separate-MPT When the new mode is UMTS in separate-MPT scenarios, deploy a new site using the summary data file on the CME. The configuration procedure is as follows: 1

Set separate-MPT BTS primary mode.

Setting Primary and Secondary RATs for Base Stations

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 2 through 3.



If the current primary and secondary RATs are consistent with the planned ones, perform 3.

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

Step 5 Create a summary data file. 1.

Customize a summary data file (non-security).

Customizing a Summary Data File (Non-Secure Networking) Expand All 1.

Open the summary data file in the basic scenario by using the function of customizing a summary data file.

a.

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.

b.

Perform operations as required.

Issue 01 (2015-12-30)


376


7 Preparing Data



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. NOTE: 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, which reduces 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.

c.

After the configuration is complete, click OK. The main window for customizing a summary data file is displayed, as shown in Figure 1. Figure 1 Window for customizing a summary data file

Issue 01 (2015-12-30)


377


7 Preparing Data

1

Tab page, which displays a set of NE configuration parameters. This area can be customized.

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 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 can be deleted but cannot be modified are highlighted in

2.

; Records that

.

Start the wizard for customizing a summary data file, and customize basic and transport parameters in a summary data file. Figure 2 shows the operation example. NOTE: 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.

Issue 01 (2015-12-30)


378


7 Preparing Data

Figure 2 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 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 3.

Configure data based on the planned data in each step on the wizard.

(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 to...

Then...

Add a tab page

Figure 3 shows an operation example.

Add parameters on a Figure 4 shows an operation example. tab page

Issue 01 (2015-12-30)


379


7 Preparing Data

Figure 3 Example of adding a tab page

Figure 4 Example of adding parameters on a tab page

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.

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. NOTE: 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.



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. Issue 01 (2015-12-30)


380


2.

7 Preparing Data

Customize a summary data file (security).

Customizing a Summary Data File (Secure) Expand All 1.


a.


b.

Perform operations as required. 




To use a default summary data file, select Default, GBTS/NodeB/eNodeB Summary, NodeB, NodeB version, and Scenario Basic Summary Template in sequence. NOTE: You are advised to select the default summary data file Scenario Basic Summary Template. The causes are as follows: 











c.

After the configuration is complete, click OK. The main window for customizing a summary data file is displayed, as shown in Figure 1.

Issue 01 (2015-12-30)


381


7 Preparing Data

Figure 1 Window for customizing a summary data file

1


2


3


 







2.

; Records that

.

Start the wizard for customizing a summary data file, and customize basic, transport, and security data in the file. NOTE: 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.

Issue 01 (2015-12-30)


382

3900 Series Multimode Base Station Mode Transition Guide a.

7 Preparing Data

Use the customization wizard to customize basic and transport data. Figure 2 shows an operation example. Figure 2 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 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 b.

Configure data based on the planned data in each step on the wizard. Use the security wizard to customize security-related data. Figure 3 shows an operation example.

Issue 01 (2015-12-30)


383


7 Preparing Data

Figure 3 Operations on the wizard

NOTE: 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.



Tip 1

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.



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. 

Tip 4

3.

Values of Sequence number of SeGW corresponding to this tunnel corresponding to Sequence number of SeGW configured in the preceding step.

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.


Issue 01 (2015-12-30)


384


7 Preparing Data

If you need to...

Then...

Add a tab page


Add parameters on a Figure 5 shows an operation example. tab page Figure 4 Example of adding a tab page

















Parameter group names and parameter names cannot be empty.

Click to verify validity of the edited summary data file. Then, modify the file based on the verification result.

Issue 01 (2015-12-30)


385


7 Preparing Data

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. NOTE: 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.





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.

Specify a summary data file. Editing a Summary Data File Expand All

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.

For detailed operations, see Setting the Macro Security Level in an Excel File.

Step 3 Edit basic data. a.

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.

bb.

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. a.

Issue 01 (2015-12-30)

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.


386


7 Preparing Data

NOTE: 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. cc.

Edit clock data and time data on the Common Data sheet.

Step 5 Edit transport data. a.

Edit the data planned for each base station, such as the IP address, subnet, and port number, on the Base Station Transport Data sheet.

b.

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. 

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.

Issue 01 (2015-12-30)


387


7 Preparing Data

Figure 1 Example for using the reference function

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. 

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 address that meets the rule.

to convert the IP address to an IP

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 2.

Issue 01 (2015-12-30)


388


7 Preparing Data

Figure 2 Settings

Issue 01 (2015-12-30)


389


7 Preparing Data

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 the following operations:

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:

5



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.

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. NOTE: 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.

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.

Issue 01 (2015-12-30)


390


7 Preparing Data

Import the summary data file. Importing a Summary Data File

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. 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. 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: 





Step 4 (Optional) Select Best effort. This option is available only when the imported summary data file contains base station controller 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.


Then...


Click Finish.

Issue 01 (2015-12-30)


391


7 Preparing Data

If...

Then...

The import fails


Import a radio plan data file. Importing a Radio Data Planning File

Step 1 Obtain the radio data planning file 3G Radio Network Planning Data Template.xls from U2000 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. NOTE: 



a.

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 RNCs in the planned data area. For details about associated parameters, see the Associated_Parameter.xls file in U2000 client installation path\client\client\Data\Common\AssociatedParameter\language.



You can set Cell Parameter Auto-Synchronization Policy to ensure consistency between parameters on other BSCs and eNodeBs that are associated with this parameter or ensure consistency of the associated parameters of all cells in the current data area. For detailed operations, see Setting System Options..



You can use the inter-U2000 neighboring cell management function to ensure that the cell associated parameters are consistent in different U2000 systems. For detailed operations, see Synchronizing Inter-OSS System Neighboring Cell Data.

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. For detailed operations about the consistency check, see Checking and Correcting the Differentiated Data Between the Master RNC and Backup or Overflow RNCs.

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

Issue 01 (2015-12-30)


392


7 Preparing Data

Application > Import Data > Import Radio Network Planning Data (U2000 client

mode). A dialog box is displayed for you to select files. b.

Specify an NE version and TXT, XLS, or XLSM as the format of the file you want to import, and click Add File to select a data planning file.

c.

Click Next. A dialog box is displayed for you to select an import mode.

d.

Select configuration objects you want to import. 

Table 2 describes the configuration objects in Basic Info.



Table 3 describes the configuration objects in External Cell Type and Neighboring Cell Relationship Type and the import modes. NOTE: 

When adding a GSM cell, the CME allocates a new index to the added GSM cell if the index of the GSM cell conflicts with an existing index on the CME.



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.

Table 2 Configuration objects in Basic Info Configuration Object

Wheth er Data Exists on the CME

Wheth er Data Exists in the File

Results After the File Is Imported into the 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.

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:

Cell

Issue 01 (2015-12-30)



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


393


7 Preparing Data





NodeB

Yes

Yes


No

Yes

The CME adds the NodeB data in the file. 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.

Yes

No


Yes

Yes

The CME overwrites the existing data using the radio data of the physical NodeBs in the file.

Radio data of physical No NodeBs only in V100R016 can be Yes imported.

Yes


No


Physical NodeB radio data NOTE: 



You can reconfigure radio data of physical NodeBs in other versions in batches by using a summary data file.




Append

Yes

Yes

Issue 01 (2015-12-30)



394


7 Preparing Data





NodeB

Yes

Yes


No

Yes


No

Yes














NOTE:  BIDIRECTION in the file takes effect only in the Append mode. 

Yes

Issue 01 (2015-12-30)

No

If BIDIRECTION is set to Yes and inverse neighboring cells do not exist, the CME processes data in the following ways: 










395


7 Preparing Data





NodeB

Yes

Yes


No

Yes


Yes

Yes


Neighbor relationships are No updated on a cell basis.

Yes


External cells are Yes updated on a base station controller basis.

No


Yes

Yes


No

Yes


Yes

No


Update NOTE: 



Delete

e.

Click Next. The CME starts the import. NOTE: The CME automatically filters invalid parameters in the file when verifying the import.

f.

Perform operations based on the import result.

Table 4 Operation description If...

Then...


The CME displays a message stating that the import is successful. Click Finish.

The import fails 1. The dialog box displays a message stating that error data exists in the data 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. Issue 01 (2015-12-30)


396


7 Preparing Data

Table 4 Operation description If...

Then... 2. After reconfiguring data, you can click Retry to import the data again.

----End

7.5.5.3 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. 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 For details, see Expanding Mode of a Co-MPT BTS in Batches. Introducing RATs to Co-MPT Base Stations in Batches 




Export co-MPT base station data to the summary data file for introducing RATs. Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application > Export Data > Export Base Station Multimode Expansion Data (CME client mode) or CME > SRAN Application > MBTS Application > Export Data > Export Base Station 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 1.

Issue 01 (2015-12-30)


397


7 Preparing Data

Figure 1 Export expansion data



Operation

Summary data file: Select this option when a summary data file has been prepared. Then, the CME exports base station data based on the configuration objects in the prepared summary data file.

1. Select Summary data file. 2. Specify save paths for both the prepared summary data file and the file where base station data is to be exported.

Custom MOC: Select this option when no summary 1. Select Custom MOC. data file is prepared. Then, the CME exports base station 2. Select configuration objects of the base stations to be data based on the configuration objects selected in the exported and the save path for the file where the base wizard. station data is to be exported. Step 4 Click Next. The CME starts to export the data. Step 5 After the export is complete, click Finish. NOTE: After the export is complete, you can click the link in the dialog box to open the exported file. 



Configure data in the exported file. 





Import the summary data file in which data about RATs to be introduced has been edited into the CME. Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application > Import Data > Import Base Station Multimode Expansion Data (CME client mode) or CME > SRAN Application > MBTS Application >

Issue 01 (2015-12-30)


398


7 Preparing Data

Import Data > Import Base Station Multimode Expansion Data (U2000 client mode). A dialog box is displayed for you to import the summary data file for introducing RATs. Step 2 Click



Then...

The imported summary 1. Click Next and select base stations you want to create. data file contains only data 2. (Optional) Select Best Effort. about base stations NOTE:

The imported summary data file contains data about both base station controllers and base stations














NOTE: 





b.


4. (Optional) Set an encryption mode for exported scripts. 






1.

Select Yes.

2.


3.


Step 4 (Optional and required when the new RATs include GSM) Click Next to set import options. Issue 01 (2015-12-30)


399


7 Preparing Data

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 succeeds


The import fails


Follow-up Procedure After introducing RATs to the base station, use the function of exporting auto-deployment files to export the deployment list and data configuration file in the RAT introduction scenario. For detailed operations, see Exporting Files Related to Base Station Creation/RAT Introduction to Co-MPT Base Stations. NOTE: You can use either of the following methods to adjust other data after introducing RATs to a base station: 





7.6 Configuring LTE Data This section describes how to prepare and adjust LTE data when LTE works as the original and new modes. The following table list the configuration method when LTE works as the original mode. Table 1.1 LTE working as the original mode Scena rio

Data Type

CME Template

Reference

Separate -MPT

Equipment data

The CME template is used to configure the summary data file in batches (LTE application).

Adjusting SeparateMPT Device Data

Transmissi on data


Adjusting SeparateMPT Transmission Data

Issue 01 (2015-12-30)


400


Scena rio

CoMPT

7 Preparing Data

Data Type

CME Template

Reference

Radio data


Adjusting SeparateMPT Radio Data

Equipment data

The CME template is used to adjust RF data (SRAN application).


Transmissi on data



Radio data



The following table list the configuration method when LTE works as the new mode. Table 1.2 LTE working as the new mode Scena rio

Data Type

CME Template

Reference

Separate -MPT


The CME template is used to deploy a new site using the summary data file.

Adjusting SeparateMPT Data

CoMPT



Adjusting Co-MPT Data

7.6.1 Preparing Equipment Data This section describes how to adjust equipment data in co-MPT and separate-MPT scenarios when the original mode is LTE. The equipment data to be adjusted includes the antenna and feeder, BBU, RXU, and CPRI.

7.6.1.1 Separate-MPT 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. 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. Issue 01 (2015-12-30)


401


7 Preparing Data

Step 3 Import the template file. ----End For details about how to use the summary data file for batch configuration (LTE application), see Importing and Exporting eNodeB Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 




Issue 01 (2015-12-30)



402


7 Preparing Data









b.


c.







Then...



403


If...

7 Preparing Data

Then...















For details about how to adjust RF data using the summary data file, see Importing and Exporting eNodeB RF Adjustment Data (standalone function). Importing and Exporting Co-MPT Base Station Data for RF Adjustment 



Issue 01 (2015-12-30)


404


7 Preparing Data

















Operation









Issue 01 (2015-12-30)


405


7 Preparing Data








Step 4 Optional: To generate configuration scripts in the wizard, select Export scripts and perform the following operations: a.

Select the mode of generating scripts. 









b.


c.

Set an encryption mode for exported scripts. 





Select Yes.

ii.


iii.



Issue 01 (2015-12-30)


406


7 Preparing Data


Description

Cell ID


TRX ID


FH Attributes






Channel Rule














Issue 01 (2015-12-30)








407


7 Preparing Data




2.


3.














7.6.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 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: Step 1 Customize and obtain the summary data file based on the mode transition planning results.

Issue 01 (2015-12-30)


408


7 Preparing Data

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 For details about how to use the summary data file for batch configuration (LTE application), see Importing and Exporting Co-MPT BTS Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 




Issue 01 (2015-12-30)

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


409


7 Preparing Data

single-mode base station. For detailed operations, see Importing and Exporting Abis Interface Data for Batch Reconfiguration. 






e.


f.


g.







Then...



410


If...

7 Preparing Data

Then...


















Issue 01 (2015-12-30)


411


7 Preparing Data

















Operation









Issue 01 (2015-12-30)


412


7 Preparing Data








Step 4 Optional: To generate configuration scripts in the wizard, select Export scripts and perform the following operations: a.

Select the mode of generating scripts. 









b.


c.

Set an encryption mode for exported scripts. 





Select Yes.

ii.


iii.



Issue 01 (2015-12-30)


413


7 Preparing Data


Description

Cell ID


TRX ID


FH Attributes






Channel Rule














Issue 01 (2015-12-30)








414


7 Preparing Data




2.


3.














7.6.2 Preparing Transmission Data This section describes how to adjust radio data in co-MPT and separate-MPT scenarios when the original mode is LTE. The transmission data to be adjusted includes the following MOs: IP, IPPATH, SCTPLINK, CPBEAR, and IPRT.

7.6.2.1 Separate-MPT 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 to configure transmission data. Issue 01 (2015-12-30)


415


7 Preparing 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 For details, see Importing and Exporting eNodeB Batch Configuration Data. Importing and Exporting Abis Interface Data for Batch Reconfiguration 








Then...


Export data based on the objects contained in a prepared 1. Select Bulk configuration template. 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.

Issue 01 (2015-12-30)


416


7 Preparing Data




Then...





NOTE:

a.






b.


c.


d.


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: 

Issue 01 (2015-12-30)

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.



417


If you need to...

7 Preparing Data

Then... The password must contain 6 to 32 characters. 3.



f.



7.6.2.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 to configure transmission 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 For details, see Importing and Exporting Co-MPT BTS Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 



Issue 01 (2015-12-30)


418


7 Preparing Data











Issue 01 (2015-12-30)


419


7 Preparing Data

a.


b.


c.







Then...



Issue 01 (2015-12-30)


420


If...

7 Preparing Data













7.6.3 Preparing Radio Data This section describes how to adjust radio data in co-MPT and separate-MPT scenarios when the original mode is LTE. The radio data to be adjusted includes the MOs related to the cell, TRX, and sector.

7.6.3.1 Separate-MPT 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 to configure radio 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 For details, see Importing and Exporting eNodeB Batch Configuration Data. Importing and Exporting eNodeB Data for Batch Configuration 


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 Issue 01 (2015-12-30)


421


7 Preparing Data

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. NOTE: 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.



b.


c.



Open the local summary data file and reconfigure data in the summary data file based on 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).



Import the modified summary data file. 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.

Issue 01 (2015-12-30)


422


7 Preparing Data

NOTE: If Best effort is selected, the CME skips the error information and continues the import. When














7.6.3.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 to configure radio 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 For details, see Importing and Exporting Co-MPT BTS Batch Configuration Data. Importing and Exporting Co-MPT Base Station Data for Batch Configuration 



Issue 01 (2015-12-30)


423


7 Preparing Data











Issue 01 (2015-12-30)


424


7 Preparing Data

a.


b.


c.







Then...



Issue 01 (2015-12-30)


425


If...

7 Preparing Data













7.6.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. 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 following table lists the corresponding CME template and reference for each scenario. Table 1.1 LTE working as the new mode Scena rio

Data Type

CME Template

Reference

Separate -MPT


The CME template is used to deploy a new site using the summary data file.

Adjusting SeparateMPT Data

Co-

Equipment,

The CME template is used to introduce

Adjusting Co-MPT

Issue 01 (2015-12-30)


426


7 Preparing Data

Scena rio

Data Type

CME Template

Reference

MPT

transmissio n, and radio data

RATs using the summary data file (SRAN application).

Data

7.6.4.1 Separate-MPT 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. 1

Create a summary data file.

Customize a summary data file (non-security). Customizing a Summary Data File (Non-Secure Networking) Expand All 1.


a.


b.

Perform operations. 




To use a default summary data file, select Default, GBTS/NodeB/eNodeB Summary, eNodeB, eNodeB version, and Scenario Basic Summary Template in sequence. NOTE: You are advised to select the default summary data file Scenario Basic Summary Template. The causes are as follows: 











c.

After the configuration is complete, click OK. The main window for customizing a summary data file is displayed, as shown in Figure 1.

Issue 01 (2015-12-30)


427


7 Preparing Data


1


2


3


 







2.

; Records that

.

Start the wizard for customizing a summary data file, and customize basic and transport parameters in a summary data file. NOTE: 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.

a.

Use the customization wizard to customize basic and transport data. Figure 2 shows an operation example.

Issue 01 (2015-12-30)


428


7 Preparing Data

Figure 2 Operations in the wizard for creating eNodeBs

Tip1

The configuration sequence is displayed as "protocol layer + configuration object". Configure the information from bottom to top based on protocol layers. 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 b.

Configure data based on the planned data in each step on the wizard. Optional: Use the customization wizard to customize RAN sharing data. Figure 3 shows an operation example. Figure 3 Operations in the RAN sharing wizard

Issue 01 (2015-12-30)


429


7 Preparing Data

NOTE: 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.

3.


If you need to...

Then...

Add a tab page











A configuration object must not be allocated to different parameter groups on the Common Data tab page.

Issue 01 (2015-12-30)


430


7 Preparing Data

One configuration object can be customized only on one tab page or on one tab page and the Common Data tab page. 




Parameter group names and parameter names cannot be empty. NOTE: In LampSite scenarios, the default summary data file does not contain the cell sector equipment group object, and you need to delete the Cell Sector Equipment object from the LTE Cell tab page and add the Cell Sector equipment Group tab page. To customize a parameter that is negotiated and planned with a telecom operator, select the LLD column of the parameter. You can select or clear multiple records by using the Shift key.









Customize a summary data file (security). Customizing a Summary Data File (Secure) Expand All 1.


a.


b.

Perform operations. 




To use a default summary data file, select Default, GBTS/NodeB/eNodeB Summary, eNodeB, eNodeB version, and Scenario Basic Summary Template in sequence. NOTE: You are advised to select the default summary data file Scenario Basic Summary Template. The causes are as follows:

Issue 01 (2015-12-30)


431


7 Preparing Data











c.

After the configuration is complete, click OK. The main window for customizing a summary data file is displayed, as shown in Figure 1. Figure 1 Window for customizing a summary data file

Issue 01 (2015-12-30)


432


7 Preparing Data

1


2


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 save the summary data file.






2.

; Records that

.

Start the wizard for customizing a summary data file, and customize basic, transport, and security data in the file. NOTE: 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.

a.

Use the customization wizard to customize basic and transport data. Figure 2 shows an operation example.

Issue 01 (2015-12-30)


433


7 Preparing Data

Figure 2 Operations in the wizard for creating eNodeBs

Tip1

The configuration sequence is displayed as "protocol layer + configuration object". Configure the information from bottom to top based on protocol layers. 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 b.

Configure data based on the planned data in each step on the wizard. Use the security wizard to customize security-related data. Figure 3 shows an operation example. Figure 3 Operations on the wizard

Issue 01 (2015-12-30)


434


7 Preparing Data

NOTE: 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.



Tip 1

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.



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. 

Tip 4

c.

Values of Sequence number of SeGW corresponding to this tunnel corresponding to Sequence number of SeGW configured in the preceding step.

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. Optional: Use the customization wizard to customize RAN sharing data. Figure 4 shows an operation example. Figure 4 Operations in the RAN sharing wizard

Issue 01 (2015-12-30)


435


7 Preparing Data

NOTE: 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.

3.


If you need to...

Then...

Add a tab page











A configuration object must not be allocated to different parameter groups on the Common Data tab page.

Issue 01 (2015-12-30)


436


7 Preparing Data

One configuration object can be customized only on one tab page or on one tab page and the Common Data tab page. 




Parameter group names and parameter names cannot be empty. NOTE: In LampSite scenarios, the default summary data file does not contain the cell sector equipment group object, and you need to delete the Cell Sector Equipment object from the LTE Cell tab page and add the Cell Sector equipment Group tab page. To customize a parameter that is negotiated and planned with a telecom operator, select the LLD column of the parameter. You can select or clear multiple records by using the Shift key.









Specify a summary data file. Editing a Summary Data File Expand All

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.

For detailed operations, see Setting the Macro Security Level in an Excel File. 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. For the mapping between the LLD data file and the summary data file, see Introduction to the LLD Data File and Summary Data File. NOTE: This function is available only after you select the LLD column of related parameters when customizing a summary data file.

Issue 01 (2015-12-30)


437


7 Preparing Data

In the summary data file, click LLD data file.

to convert it into an

The sheet named Common Data maps COMMON. The other sheet names remain unchanged. dd.

Edit the prepared data in the LLD data file.

NOTE: 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 1. The existing data in the summary data file is overwritten.

Figure 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. ee.

Click data file.

to apply the data in the LLD data file to the summary

Step 4 Edit basic data. a.

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.

ff.

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.

Issue 01 (2015-12-30)


438


7 Preparing Data

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.

NOTE: 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. gg.

Edit clock data and time data on the Common Data sheet.

Step 6 Edit transport data. a.

Edit the data planned for each base station, such as the IP address, subnet, and port number, on the Base Station Transport Data sheet.

b.

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. 

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 2 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.

Issue 01 (2015-12-30)


439


7 Preparing Data

Figure 2 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. 

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 address that meets the rule.

to convert the IP address to an IP

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 3.

Issue 01 (2015-12-30)


440


7 Preparing Data

Figure 3 Settings

Issue 01 (2015-12-30)


441


7 Preparing Data

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 the following operations:

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.

Click OK. Excel starts the calculation based on the preset information.

5

Step 7 Add radio data. Click the cell sheet, set the value of each parameter and the template name based on the planned data. NOTE: 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.

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.

Import a summary data file. Importing a Summary Data File Issue 01 (2015-12-30)


442


7 Preparing Data

Step 1 On the menu bar of the planned data area, choose LTE Application > Import Data > Import Base Station Summary Data (CME client mode) or CME > LTE 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. Step 2 Click


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. Step 4 Click Next. The CME starts the import. If...

Then...


Click Finish.

The import fails


Prepare and specify a radio plan data file. Importing a Summary Data File

Step 1 On the menu bar of the planned data area, choose LTE Application > Import Data > Import Base Station Summary Data (CME client mode) or CME > LTE 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. Step 2 Click


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. Step 4 Click Next. The CME starts the import.

Issue 01 (2015-12-30)


443


7 Preparing Data

If...

Then...


Click Finish.

The import fails


Import the radio plan data file. Importing a Radio Data Planning File

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, and click Next. A dialog box is displayed for you to select eNodeBs. 

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 describes the import modes and import results. Table 1 Description of import modes Import Mode


Whether the Object Data Exists in the File

Data Result on the CME After File Import

Append

Yes

Yes


Issue 01 (2015-12-30)


444


7 Preparing Data





No

Yes














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: 








Yes

No


Yes

Yes

NOTE:  Neighbor relationships are No updated on a cell basis.


Yes


No


Update



External cells are Yes updated on a base

Issue 01 (2015-12-30)


445


7 Preparing Data


station




Yes

Yes


No

Yes


Yes

No


controller

Delete

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. Step 6 Table 2 Operation description If...

Then...

The import succeeds

The CME displays a message stating that the import is successful.

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

7.6.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. 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. Issue 01 (2015-12-30)


446


7 Preparing Data

----End For details, see Expanding Mode of a Co-MPT BTS in Batches. Introducing RATs to Co-MPT Base Stations in Batches 




Export co-MPT base station data to the summary data file for introducing RATs. Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application > Export Data > Export Base Station Multimode Expansion Data (CME client mode) or CME > SRAN Application > MBTS Application > Export Data > Export Base Station 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 1. Figure 1 Export expansion data



Operation

Summary data file: Select this option when a

1. Select Summary data file.

Issue 01 (2015-12-30)


447


7 Preparing Data

Option

Operation

summary data file has been prepared. Then, the CME exports base station data based on the configuration objects in the prepared summary data file.

2. Specify save paths for both the prepared summary data file and the file where base station data is to be exported.

Custom MOC: Select this option when no summary data file is prepared. Then, the CME exports base station data based on the configuration objects selected in the wizard.

1. Select Custom MOC. 2. Select configuration objects of the base stations to be exported and the save path for the file where the base station data is to be exported.

Step 4 Click Next. The CME starts to export the data. Step 5 After the export is complete, click Finish. NOTE: After the export is complete, you can click the link in the dialog box to open the exported file. 



Configure data in the exported file. 





Import the summary data file in which data about RATs to be introduced has been edited into the CME. Step 1 On the menu bar of the planned data area, choose SRAN Application > MBTS Application > Import Data > Import Base Station Multimode Expansion Data (CME client mode) or CME > SRAN Application > MBTS Application > Import Data > Import Base Station Multimode Expansion Data (U2000 client mode). A dialog box is displayed for you to import the summary data file for introducing RATs. Step 2 Click



Then...

The imported summary data file contains only data about base stations

1. Click Next and select base stations you want to create.

The imported summary data file contains data about both base station controllers and base Issue 01 (2015-12-30)

2. (Optional) Select Best Effort. NOTE: 






If Best effort is selected, the CME skips the error information and continues the import.


448


If...

7 Preparing Data

Then... When the import is complete, the CME rolls back only incorrect base station data.

stations 




NOTE: 





b.


6. (Optional) Set an encryption mode for exported scripts. 






1.

Select Yes.

2.


3.


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 succeeds


The import fails


Follow-up Procedure After introducing RATs to the base station, use the function of exporting auto-deployment files to export the deployment list and data configuration file in the RAT introduction

Issue 01 (2015-12-30)


449


7 Preparing Data

scenario. For detailed operations, see Exporting Files Related to Base Station Creation/RAT Introduction to Co-MPT Base Stations. NOTE: You can use either of the following methods to adjust other data after introducing RATs to a base station: 





7.6.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.



Select NodeB/eNodeB/USU Bulk Configuration for Scenario and choose corresponding version.

Issue 01 (2015-12-30)


450


7 Preparing Data



Click

1.

To reconstruct an FDD eNodeB into an FDD+TDD eNodeB, select Adjusting eNodeB Configurations > Reconstructing a FDD eNodeB into an FDD+TDD eNodeB from Scenario list.

2.

To reconstruct a TDD eNodeB into an FDD+TDD eNodeB, select Adjusting eNodeB Configurations > Reconstructing a TDD eNodeB into an FDD+TDD eNodeB from Scenario list.

Issue 01 (2015-12-30)

in the upper left corner and select corresponding scenario.


451


7 Preparing Data

For details about how to customize a summary data file, see Customizing eNodeB Batch Configuration Summary Data File. Customizing a Summary Data File for Batch eNodeB Configuration

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 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 following operations: 

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 1.

Issue 01 (2015-12-30)


452


7 Preparing Data


NOTE: 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 to...

Then...

Add a tab page



Issue 01 (2015-12-30)


453


7 Preparing Data















Parameter group names and parameter names cannot be empty. NOTE: 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.

Step 6 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. NOTE: 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 7 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. Follow-up Procedure After customizing a summary data file for batch eNodeB configuration, you can:

1. Export related configuration data based on the summary data file for batch eNodeB configuration. For detailed operations, see Export base station data to the summary data file.

Issue 01 (2015-12-30)


454


7 Preparing Data

2. Reconfigure data in the summary data file for batch eNodeB configuration based on site requirements and then import the edited file into the CME. For detailed operations, see Import the modified summary data file.

Based on the customized template, export the data to be adjusted and specify data in the template file as planned. a.

To reconstruct an FDD eNodeB into an FDD+TDD eNodeB, specify data by referring to 4.13 Example: Mode Transition from LO (FDD) to LO (FDD+TDD).

hh.

To reconstruct a TDD eNodeB into an FDD+TDD eNodeB, specify data by referring to 4.14 Example: Mode Transition from LO (TDD) to LO (FDD+TDD).

Import the template file. For details about how to import and export the summary data file, see Importing and Exporting eNodeB Batch Configuration Data. Importing and Exporting eNodeB Data for Batch Configuration 


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. NOTE: 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.



b.


c.


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.

Issue 01 (2015-12-30)


455


7 Preparing Data

Open the local summary data file and reconfigure data in the summary data file based on 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).



Import the modified summary data file. 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. NOTE: If Best effort is selected, the CME skips the error information and continues the import. When














----End

7.7 Binding Base Station Multimode Relationships Binding Relationships Between Separate-MPT Base Stations in Batches Binding Base Stations as Separate-MPT Base Stations in Batches 

Export the binding relationship table.

Step 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 Issue 01 (2015-12-30)


456


7 Preparing Data

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. Step 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.

ii.

Select one or more separate-MPT base stations whose binding relationships you want to export.

Step 3 Click Next. A dialog box is displayed for you to specify a save path. Step 4 Set the save path for the file you want to export. Step 5 Click Next. The CME starts to export the data. Step 6 When the export is successful, click Finish. 

Edit the binding relationship table.

Step 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 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.

Step 2 After editing the binding relationship table, save and close it. 

Import the binding relationship table.

Step 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. Step 2 Select the binding relationship file you want to import, and click Next. The CME starts checking the file format and importing the file. Step 3 When the import is successful, click Finish.

Issue 01 (2015-12-30)


457


7 Preparing Data

NOTE: 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.

7.8 Checking MBTS Data Consistency 

Manually Checking NE Data Consistency

Manually Checking NE Data Consistency

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 shows the window. Figure 1 Data consistency check window

Step 2 Start the check task. If you need to... Create a check task

Issue 01 (2015-12-30)

Then... 1. Click

in area 1 in Figure 1. The consistency check wizard is displayed. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

458


If you need to...

7 Preparing Data

Then... 2. Set the task name, and select the NEs whose data is to be checked. NOTE: 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. 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 Type of a result record is displayed as...

Then...

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. For details about the mapping between the options in the autofix wizard and check rules, see Introduction to the autofix Options. 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.

Issue 01 (2015-12-30)


459


7 Preparing Data

If Operation Type of a result record is displayed as...

Then...

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 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. The check results can only be viewed.

None

NOTE: You can perform the following operations in area 3 in Figure 1 as required: 



To filter a large number of check results by type for easier browsing, click name.

next to the column

To export the check results as a file, right-click in area 3 and choose Export Data from the shortcut menu.

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. NOTE: You can also compare the check results of two tasks in the following method:  



Right-click a task and choose Choose to compare on left window from the shortcut menu. Right-click the other task, and choose the related option from the shortcut menu to compare it with the selected task.

Checking MBTS Data Consistency

Checking Multimode Base Station Data Consistency

Issue 01 (2015-12-30)


460


7 Preparing Data

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 to...

Then...

Set check rule parameters

Perform 2.

Manage rule groups

Perform 3.

Create a consistency check task

Perform 2 and 8.

Step 2 (Optional and required when the default check parameter configurations do not meet your requirements) Set check rule parameters. If you need to... Then... Set check rule parameters

1. Click

. A dialog box is displayed for you to set check rule 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 severity of check rules

1. Click

. A dialog box is displayed for you to set check rule parameters.

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. Issue 01 (2015-12-30)


461


7 Preparing Data

Step 3 (Optional and required when the default check parameter configurations do not meet your requirements) Manage rule groups.

a.

Click

. A dialog box is displayed for you to manage rule groups.

jj.

Select a multimode base station type from the MBTS type drop-down list. 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.

kk.

Perform the following operations as required.

If you need to... Then... Delete a rule group

Select a rule group from the left pane of the dialog box, and click Delete.

Modify check rules

1. Select a rule group from the left pane of the dialog box, and select or clear check rules from the right pane. 2. Click Save.

ll.

Step 4 Click

Click Close. . 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. NOTE: 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. a.

Select a rule group from the Rule group drop-down list. All related check rules are displayed in the lower part.

mm.

(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.

nn.

(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 3.

Step 7 Click Next, and adjust check rule settings. NOTE: 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:

Issue 01 (2015-12-30)


462


7 Preparing Data



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. If Operation Type in a data record is displayed as... Refresh

Then... 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. NOTE: 



To filter a large number of check results by type for easier browsing, click name.

next to the column

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

.

.

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. NOTE: You can also compare the check results of two tasks in the following method:

Issue 01 (2015-12-30)

a.

Right-click a task and choose Choose to compare on left window from the shortcut menu.

b.

Right-click the other task, and choose Compare to name of last task from the shortcut menu.


463


7 Preparing Data

7.9 Checking Data Preparations Check the consistency between the customized configuration data and data planned for mode transition. Ensure no MO is missing.

Issue 01 (2015-12-30)


464


8

8 Setting NE Maintenance mode

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.

Step 2 Choose Setting > Maintenance Mode on the displayed interface. Issue 01 (2015-12-30)


465



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.

Issue 01 (2015-12-30)


466



These operations succeed. Maintenance mode has been successfully set.

----End

Issue 01 (2015-12-30)


467


9 Adjusting Hardware

9

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.

9.1 Adjusting Equipment The equipment to be adjusted during mode transition include BBUs, RXUs, CPRI cables, and antenna & feeder. 3 Planning Mode Transition shows the equipment configurations before and after mode transition.

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 reconstruction is retained and serves as the signaling extension board for the UMPTe.

Adjusting RF Modules For details about how to install RRUs, see the related RRU installation guide. Issue 01 (2015-12-30)


468


9 Adjusting Hardware

Adjusting Feeders Connect feeders to the newly added MRRUs.

9.2 Adjusting Feeders Connect feeders to the newly added RRUs.

9.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.

Issue 01 (2015-12-30)


469


10

10 Activating Configuration Data and Commissioning

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 10.1 Activating 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 10.2 Base 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 U2000based commissioning can be used. For the operation methods, see 10.2 Base Station Deployment by PnP and 10.3 Base 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 10.4 PnP-based Co-MPT Reconstruction and 10.3 Base Station Deployment by USB.

Issue 01 (2015-12-30)


470



10.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 script and use the script executor for data activation if base station controller data exists. 1

Perform the operation described in Exporting Incremental Scripts in the Planned Data Area.

Exporting Incremental Scripts from a Planned Data Area

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: The export stops immediately if an error occurs during the command

execution in the export. 

Best Effort: The CME continues with the export by running a command next to the

error command if an error occurs during the export. Step 5 (Optional) Set an encryption mode for exported scripts. 




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.

Issue 01 (2015-12-30)


471



a.

Select Yes.

b.


c.


Step 6 Select a mode for starting the script executor. If...

Then...

You do not need to activate scripts or check scripts in the script executor window

Select Do not launch script executor.

You need to check or edit scripts in the script executor window before activating scripts

Select Launch script executor only.

After the scripts are exported, you can click the save path link to navigate to the folder for saving the scripts. You need to manually start the script executor to activate incremental scripts in the future. For detailed operations, see the manual startup process in Activating Data Using the Script Executor.

Click OK. The CME then automatically uploads the exported scripts to the U2000 server. In addition, the CME automatically switches to the Summary tab page of the script executor and selects the planned data area node to which the new script project belongs. 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. NOTICE: Before performing this operation, ensure that you have the network device permission Modify Physical NE Data through CME. Otherwise, the scripts cannot be exported. For details about the permission, see Introduction to Authority Management.

You need to directly 1. Select Launch script executor and activate exported project. activate scripts 2. Select a script activation mode from the drop-down list. 

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. NOTICE: Before performing this operation, ensure that you have the network device permission Modify Physical NE Data through CME. Otherwise, the scripts cannot be exported. For details about the

Issue 01 (2015-12-30)


472


If...


Then... permission, see Introduction to Authority Management.

Step 7 Click OK to export the incremental scripts. NOTE: 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. 



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.

Proceed according to the script activation procedure. Activating Data Using the Script Executor This section describes how to activate data using the script executor.

Prerequisites 

You have exported and saved configuration scripts.



You have performed a conflict check to ensure that the activation can take effect.



You have the network device permission Modify Physical NE Data through CME. For details about the permission, see Introduction to Authority Management.

Context For details about the script executor, see CME Script Executor. Figure 1 shows the process of activating the data in the configuration scripts by using the script executor.

Issue 01 (2015-12-30)


473



Figure 1 Process of activating data using the script executor

NOTE: You can choose to manually start the script executor or enable automatic startup based on site requirements. The startup methods are described as follows: 

Manually starting the script executor: Manually start the script executor and upload the scripts saved on the local PC to the U2000 server.



Enabling automatic startup of the script executor: During the generation of scripts in the configuration wizard, select Launch the script executor. The CME then automatically imports and uploads the scripts.

Table 1 Process of activating data using the script executor Step

Description

Upload scripts Upload the configuration scripts to the U2000 server. For detailed operations, see Uploading Scripts. This operation is required only when you manually start the script executor. Check or edit scripts

You can check the content of uploaded scripts on the GUI. To adjust some parameters in an uploaded script, edit them in the script executor directly. For detailed operations, see Checking or Editing Scripts. NOTE:  After you modify parameters in the script executor, the CME does not verify the data. Ensure that the parameters are correctly modified.

Issue 01 (2015-12-30)


474



Table 1 Process of activating data using the script executor Step

Description If multiple parameters are to be modified, you are advised to reconfigure parameters in the planned data area, export a script, and then re-upload the script.



Activate data

Activate data in the uploaded configuration scripts. For detailed operations, see Activating Data.

Fallback based on the configuration steps

After configuration data takes effect on the live network, the network KPIs, however, do not meet related requirements after being detected. In such a case, you can use the script executor to activate a fallback script to fall back the configuration data to a state before the modification. For detailed operations, see Fallback Based on Configuration Steps.

View activation tasks

Manage projects and tasks, such as viewing task information and status. For detailed operations, see Viewing Activation Tasks.

Export configuration scripts in a project

Export configuration scripts by NE from the U2000 server to a local PC to exchange with other users. For detailed operations, see Exporting Configuration Scripts in a Project.

----End

10.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. Perform the following steps: 1

Export PnP data files.

Exporting Files Related to Base Station Creation/RAT Introduction to Co-MPT Base Stations

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 scenario, and click Next. Step 3 Select the base stations whose auto-deployment data you want to export, and click Next. NOTE: You can click Load to select base stations to be exported by loading a file. The method of obtaining the file and the file format rules are described as follows:

Issue 01 (2015-12-30)


475





Obtaining the file: Click Export. The CME then exports the file. You have to set values for the parameters in the exported file. File format rules: For details, see File Format Rules. 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 data from the current area



After Export NE security configuration data is selected, if the current user has the Obtain NE Security Configuration Data operation rights, NE sensitive data is displayed in plaintext in the exported data file; if the current user does not have the Obtain NE Security Configuration Data operation rights, a message is displayed on the CME, indicating that sensitive data cannot be exported. For details about the operating rights, see Introduction to Authority Management.



After Export NE security configuration data is cleared, sensitive data is displayed in ciphertext in the exported data file.

Export data from the planned area

Select the method for verifying data as required.

Step 5 View data in the base station deployment list, and click Next. The CME starts to verify data correctness and exports the data. NOTE: 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. 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.

Step 7 Click Finish. NOTE: The save paths for the exported data configuration scripts and deployment lists are as follows:

Issue 01 (2015-12-30)


476





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.

Starting 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. Figure 1.1 Starting an NE commissioning task

a.

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.

Issue 01 (2015-12-30)


477

3900 Series Multimode Base Station Mode Transition Guide oo.


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. 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 site

Download software

Select this procedure if you need to upgrade the software version of a main control board.

Download site configuration

Select this procedure if you 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

Issue 01 (2015-12-30)

Deliver license

Deliver commissioning license


Select this procedure if LTE services are to be 478


No.


Phase

Procedure

Selection Policy commissioned.

4

Test installation & deployment quality

Monitor RF module service status

The U2000 selects this procedure if installation and deployment quality testing is to be performed.

Intervene

The U2000 selects this procedure if installation and deployment quality testing is to be performed.


This procedure is optional but recommended. NOTE If a DBS3900 LampSite is to be commissioned, do not select Test installation & deployment quality. Otherwise, the commission task fails.

5

Waiting for confirmation

pp.


The system automatically selects this procedure.

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.

qq.

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

10.3 Base Station Deployment by USB The related deployment operations are as follows: 1

Preparing a Software Package, Data Configuration Files, and Deployment Lists

Procedure Step 1 Obtain the software package from Huawei engineers and decompressed the software package on a local PC.

Issue 01 (2015-12-30)


479





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 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 Deployment Lists and Data Configuration Files from the CME.

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\



Deployment lists: export directory\ADList\



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.

Issue 01 (2015-12-30)

a.

On the U2000 client, choose SON > Self Planning > Auto Deployment (Application style) or SON > Auto Deployment (Traditional style). The Auto Deployment window is displayed.

rr.

Click the Prepare File & Data tab and then the Deployment List tab.


480



Figure 1.1 Prepare File & Data > Deployment List tab

ss.

Click Transfer, and choose From OSS Client to OSS Server from the shortcut menu. The Upload Deployment List dialog box is displayed.

Figure 1.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.

Issue 01 (2015-12-30)


481



tt.

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.

uu.

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.

Preparing a USB Flash Drive (for NodeB, eNodeB, and BTS3900)

Procedure Step 1 Choose Start > Programs > iManager U2000 MBB Client > USB Making and Protection Tool to start the tool. 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.

Issue 01 (2015-12-30)


482



Figure 1.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 upgrading the software and updating configuration files



Software Path: mandatory, save path of the files decompressed from a specified version software package.



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. Issue 01 (2015-12-30)


483


Item


Information to Set 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 updating configuration Issue 01 (2015-12-30)

Auto Deployment List: mandatory. Select the deployment list exported from the CME. The exported deployment list is saved in export path/ADList/ by Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

484



Item

Information to Set

files only

default. Engineers must select the only .xml file in this directory. LTE Commissioning License: mandatory if LTE services are to be enabled. Select the LTE commissioning license you have obtained.

Directory for upgrading the software only



Software Path: mandatory, save path of the files decompressed from a specified version software package.



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.

Issue 01 (2015-12-30)


485



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.

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.

Local Path

Issue 01 (2015-12-30)



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.

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.



One USB for Multiple Sites: In this mode, save the information about all NEs to a


486


Option


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.

Step 7 Click Start. When making the USB directories, the USB making and protection tool automatically performs the following operations: 

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 1.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 1.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.

Issue 01 (2015-12-30)


487





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 1.1 File copy procedure in One USB for One Site mode

Issue 01 (2015-12-30)


488



Figure 1.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.

Preparing a USB Flash Drive (for GBTS)

Procedure 

Manually make a USB flash drive.

Step 1 Save the required files in the specified paths on the USB flash drive. Files required in different scenarios are listed in Error: Reference source not found. Save paths for different types of files on a USB flash drive are listed in Table 1.1. 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 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 (Precfg.ini)

usb:\BTS3900 GSM\Precfg.ini

Transmission configuration files (Trancfg.INI) and transmission mode configuration file (TranModeCfg.ini)

One USB flash drive can only contain either of Trancfg.INI and TranModeCfg.ini.

Issue 01 (2015-12-30)



For TranCfg.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.


489


File


Save Path 



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.

Figure 1.2 Directory Structure on a USB Flash Drive

Step 2 For details about how to perform integrity protection and encryption on the files stored on a USB flash drive, see Error: Reference source not foundError: Reference source not found or Error: Reference source not foundError: Reference source not found. 

Use the USB making and protection tool to make a USB flash drive.

Step 1 Choose Start > Programs > iManager U2000 MBB Client > USB Making and Protection Tool to start the tool.

Issue 01 (2015-12-30)


490



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.

Issue 01 (2015-12-30)


491



Figure 1.1 Path settings

Step 3 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.

Item

Information to Set

Directory for upgrading the software and updating configuration files

GBTS pre-configuration script (Precfg.ini): It is 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. Deployment lists and transmission mode configuration file (TranModeCfg.ini): Select these files based on the actual conditions. Deployment lists: Select this file when transmission

Issue 01 (2015-12-30)


492



Item

Information to Set 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. 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 configuration files only

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 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 the software only

GBTS pre-configuration script (Precfg.ini): It is 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.

Issue 01 (2015-12-30)


493



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

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

Local Path



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.

Save all the information to the specified directory on a local PC. 

Issue 01 (2015-12-30)

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


494


Item


Description folder. 

One USB for Multiple Sites: In this mode, save the information about all NEs to a 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.

Step 7 Click Start. When making the USB directories, the USB making and protection tool automatically performs the following operations: 

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.

Step 8 Click OK in the dialog box displayed after the tool completes the making of the USB flash drive. Step 9 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 99, 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.

Issue 01 (2015-12-30)


495



Step 10 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. Figure 1.1 File copy procedure for GBTS commissioning

Issue 01 (2015-12-30)


496



Starting 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. Figure 1.1 Starting an NE commissioning task

----End Step 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.

Issue 01 (2015-12-30)


497



Step 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 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 No.

Phase

Procedure

Selection Policy

1

Auto discover site

Check OM channel

The U2000 determines whether to select this procedure.

2

Auto configure site

Download site software

This procedure is not selected.

Download site configuration

If the data configuration file 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 license

If the commissioning license is stored on the USB flash drive, do not select this procedure. Otherwise, select this procedure.

4


Monitor RF module service status

The U2000 selects this procedure.

Intervene

The U2000 selects this procedure.


This procedure is optional but recommended.


The system automatically selects this procedure.

5


Step 3 Set Extended Parameters as planned. Issue 01 (2015-12-30)


498



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. Step 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

10.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. The procedures are as follows: 1

Export Auto Deployment Data

Exporting Files Related to Base Station Creation/RAT Introduction to Co-MPT Base Stations

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 scenario, and click Next. Step 3 Select the base stations whose auto-deployment data you want to export, and click Next. NOTE: You can click Load to select base stations to be exported by loading a file. The method of obtaining the file and the file format rules are described as follows: 



Obtaining the file: Click Export. The CME then exports the file. You have to set values for the parameters in the exported file. File format rules: For details, see File Format Rules. 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 data from the current area



After Export NE security configuration data is selected, if the current user has the Obtain NE Security Configuration Data operation rights, NE sensitive data is displayed in plaintext in the exported data file; if the current user does not have the Obtain NE Security Configuration Data operation rights, a message is displayed on the CME, indicating that sensitive data cannot be exported. For details about the operating rights, see Introduction to Authority Management.



After Export NE security configuration data is cleared, sensitive data is displayed in

Issue 01 (2015-12-30)


499


If...


Then... ciphertext in the exported data file.

Export data from the planned area

Select the method for verifying data as required.

Step 5 View data in the base station deployment list, and click Next. The CME starts to verify data correctness and exports the data. NOTE: 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. 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.

Step 7 Click Finish. NOTE: 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.

Starting Commissioning Tasks for Co-MPT Reconstruction in Mode Addition Scenarios Starting Commissioning Tasks for Co-MPT Reconstruction in Mode Addition Scenarios Step 1 Create a task of site reconstruction on the U2000.

Issue 01 (2015-12-30)

a.

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.

vv.

On the Site Configuration Data tab page, upload data configurations of a co-MPT site generated after site reconstruction to the U2000.

ww.

On the Controller Configuration Data tab page, upload MBSC reconstruction scripts generated after site reconstruction to the U2000. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

500



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.

xx.

To upload the GTMU conversion software, set NE type to GBTS. To upload the co-MPT software, set NE type to BTS3900. Step 2 Download the GTMU conversion software and co-MPT software. 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:

a.



Select Download GTMU evolution software and Download site software when separate-MPT GBTSs are reconstructed with GTMU conversion adopted.





Issue 01 (2015-12-30)

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.


501





yy.

Start a PnP-based co-MPT reconstruction task on the U2000.

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. a.

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.

Issue 01 (2015-12-30)


502



zz.

Click Restart to start the reconstruction.

aaa.

After the task is complete, click Confirm Completion.

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. a.

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 nexthop IP addresses for the router or Layer 3 switch for co-transmission after the reconstruction.

bbb.

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 omc/cme/system/activescript.html. 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.

Issue 01 (2015-12-30)


503





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, rightclick 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. Error: Reference source not foundError: Reference source not found Perform the following operations to verify the co-MPT reconstruction: Start the U2000, and check whether the target base station has become a co-MPT base station whose NE type is now BTS3900.

a.



Issue 01 (2015-12-30)

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.


504


Issue 01 (2015-12-30)



505


Issue 01 (2015-12-30)




Check whether the modes deployed on the target base station are displayed, as shown in the following figure.



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.


506




Issue 01 (2015-12-30)


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 coMPT 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 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

507



mode from the U2000 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.

ccc.

Check whether services of each mode are processed properly after reconstruction.

ddd.

Check whether new alarms are generated after co-MPT reconstruction. If new alarms are generated, clear them.

eee.

Issue 01 (2015-12-30)





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. 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. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

508

3900 Series Multimode Base Station Mode Transition Guide fff.


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

Issue 01 (2015-12-30)


509


11

11 Ending Maintenance Mode for NEs

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.

Issue 01 (2015-12-30)


510


12 Appendix for Co-MPT Reconstruction

12

Appendix for Co-MPT Reconstruction

This section describes the appendix for co-MPT reconstruction scenarios.

12.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 



Path for saving the configuration data 

2.

\BakData\ AutoDeployment_***\AdList\ Auto_Deployment_List_***.xml \BakData\AutoDeployment_***\CfgData\\***.xml

Path for saving reconstruction scripts Path for saving the GBTS reconstruction MML scripts \mml\\Convert\.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 



Path for saving the GBTS rollback MML scripts 

4.

\mml\\Fallback\scriptcfg.xml \mml\\Fallback\.txt

Path for saving the co-MPT data configuration file after reconstruction \AutoDeploymentData\CfgData\\CFGDATA.XML

5.

Path for saving the deployment list after reconstruction \AutoDeploymentData\ADList\***.xml

6.

Path for saving conversion logs \rpt\***.txt Logs recorded during the conversion are saved in this path.

Issue 01 (2015-12-30)


511



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

12.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 GBTSs 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.

Issue 01 (2015-12-30)


512



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: 

Revoke the BSC license file on the BSC and obtain the revocation code. a.

On the web LMT of the BSC6900/BSC6910 to which the eGBTS belongs, run the LST LICENSE command to query the current license file, as shown in the following figure.

 b.

On the same web LMT, run the RVK LICENSE command. Then enter the name of the license file to be revoked, as shown in the following figure.



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, as shown in the following figure.

Issue 01 (2015-12-30)


513





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.

Only licensed resources 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. Issue 01 (2015-12-30)


514



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.

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.

Issue 01 (2015-12-30)


515



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, 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, 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.

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.

Issue 01 (2015-12-30)


516



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.

12.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.

12.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.

Issue 01 (2015-12-30)


517





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). 

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;

12.5 Constraints and Limitations Limitations on the Standalone CME 1.

Issue 01 (2015-12-30)

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 after the co-MPT reconstruction during Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

518



the device reconstruction on the standalone CME. In the co-MPT reconstruction scenario where the GSM mode is included, after the co-MPT reconstruction, you cannot change the GTMU handling method when performing other reconstruction activities in offline mode. If you change the GTMU handling method, the deployment list exported by the standalone CME after configuration data is prepared will be abnormal. For example, GTMU evolution is adopted during co-MPT reconstruction, but the GTMU is abandoned during device reconstruction. 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.

Limitation on NE Equipment 1.

Data of only the following GSM base stations can be converted: DBS3900 (GSM), BTS3900 (GSM), BTS3900A (GSM), BTS3900L (GSM), and BTS3900AL (GSM).

2.

The conversion cannot be performed on super base stations.

3.

The conversion is not performed if a GBTS is configured with a DRFU or DRRU,UTRP.

Issue 01 (2015-12-30)


519



4.

The conversion is not performed if the parameter Send Mode of a GBTS is set to a value other than NOCOMB(No Combination) or DTIC(Transmit Independency or Combination).

5.

Omit the following functions when performing conversion if any of them are enabled for a GBTS: inter-module RF frequency hopping or inter-module power sharing, and interPA RF frequency hopping or inter-PA power sharing.

6.

Reconstruction cannot be performed if two sectors with different modes share a part of the antenna before reconstruction, or if two baseband devices with different modes share the same part of baseband processing units before reconstruction.

7.

Reconstruction cannot be performed 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, you need to 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. 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 coMPT base stations. Hardware configuration (subrack quantity, subrack type, subrack number, board quantity, board type, and slot number) remains unchanged after the reconstruction. 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 (added 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.

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, the co-MPT reconstruction is not supported.

2.

The conversion cannot be performed if a BSC pool is used and the transmission over the Abis interface is used by different operators (this configuration is added in SRAN9.0).

Issue 01 (2015-12-30)


520



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, the tool cannot automatically identify this scenario. In this situation, you need to assess the scenario before the reconstruction.

4.

The reconstruction cannot be performed if the networking changes after a GBTS is reconstructed into 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 must carry VLAN information in packets) to non-VLAN networking, or from non-VLAN networking to VLAN networking. In addition, the VLAN ID may change.

5.

The tool does not support the reconstruction if the Ethernet port configured for a base station is inconsistent with that actually used. For example, the IP address is configured on an electrical port but the cable is connected to an optical port in actual use.

6.

The reconstruction cannot be performed if non-64 kbit/s timeslots have been monitored.

7.

The reconstruction cannot be performed 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. For IPoE1-based GBTSs 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 converting base stations using DHCP servers, you are advised to convert 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:

Issue 01 (2015-12-30)

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.

ggg.

Scenarios where BBUs are interconnected through two front panels are not supported. If BBUs are interconnected through one front panel before co-MPT reconstruction, the cable used for interconnection must be reserved. If a GTMU is to be abandoned, BBU interconnection through either one or two front panels is not supported.

hhh.

E1/T1 co-transmission is not supported. Reconstruction from E1/T1 separate transmission to E1/T1 co-transmission is not supported.


521



iii.

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.

jjj.

Reconstruction from Ethernet trunk separate transmission to Ethernet trunk cotransmission is not supported.

kkk.

Reconstruction cannot be performed in UTRPc-, UTRP2-, or UTRP9-based cotransmission scenarios when GSM is involved in reconstruction. When a separateMPT UL base station uses UTRPc-based co-transmission, only the reference mode provides transmission ports during reconstruction.

lll.

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, it is difficult to determine which port is the co-transmission port and this scenario is not supported.

13. Co-MPT reconstruction restrictions on security are as follows: a.

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.

mmm. 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).

nnn.

Co-MPT reconstruction from a separate-MPT multimode base station is not supported if the following conditions are met:

ooo.

A UTRPc is configured to transmit data for the reference mode.

ppp.

IPsec is configured for the non-reference modes but not the reference mode.

qqq.

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. 15. Co-MPT reconstruction from a separate-MPT multimode base station is not supported if LTE is not the reference mode and the two ports of the LMPT are used as optical or electrical ports. 16. Co-MPT reconstruction from a separate-MPT multimode base station is not supported if 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, CoMPT 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.

Issue 01 (2015-12-30)


522



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: a.

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.

rrr.

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.

Limitation on Clock 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 the 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. 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.

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 The 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. Issue 01 (2015-12-30)


523



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 the 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 coMPT 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 the coMPT 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.

12.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 coMPT multimode base stations requires complex data reconfigurations. This tool is used to simplify the data reconfigurations.

Hardware Requirements for PCs Item

Requirement

CPU

x86 ≥ 2 GHz

Memory

≥ 2 GB

Available space on the hard disk

≥ 2000 MB

Software Requirements for PCs Item

Requirement

Operating system (OS)



Windows XP Professional 32-bit (SP3)



Windows 7 Professional 32-bit (SP1)

Issue 01 (2015-12-30)


524


Item


Requirement 

Windows 7 Professional 64-bit (SP1)

Excel version

Microsoft Office Excel 2003 or later

OS language

English

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.

12.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.

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. Issue 01 (2015-12-30)


525



Scenarios Where Manual Verification Is Required None

12.6.2 Application Scenarios and Restrictions of the GBTS Reconstruction Module 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 configuration data to determine whether to perform manual verification.


Convert the data of activated base station, cells and carriers only.

Scenarios Where Manual Verification Is Required 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.

12.6.3 Application Scenarios and Restrictions of the SRAN Reconstruction Module 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 configuration data to determine whether to perform manual verification.


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.

Issue 01 (2015-12-30)


526



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.

The reconstruction cannot be performed if two baseband devices with different modes share some of baseband processing units before the reconstruction. 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.

Scenarios Where Manual Verification Is Required 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 QoSrelated configurations (such as DIFPRI and DSCPMAP) need to be modified.

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.

Issue 01 (2015-12-30)


527



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 the Co-MPT reconstruction, the users manually configure the filter switch.

6.

In scenarios where a separate-MPT multimode base station is to be reconstructed, IP over FE on one transmission port is used after co-MPT reconstruction if the following conditions of the separate-MPT multimode base station are met: a.

Separate transmission is used.

sss.

IP over FE is used.

ttt.

The transmission port numbers are the same.

12.7 Co-MPT Reconstruction Scenarios Note: 1.

2.

3.

Issue 01 (2015-12-30)

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.



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.



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 reconstruction is retained and serves as the signaling extension board for the UMPTe.

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 coMPT base station. This type of reconstruction has the following constraints: a.

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.

uuu.

The reference mode must be the mode deployed on the co-MPT base station instead of the separate-MPT base station.

vvv.

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.

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 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

528



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.

12.7.1 GSM Co-MPT Reconstruction Scenario Sc en ari o No .

Before Reconstruc tion

After Reconstructio n

Main Contro l Board

Trans missi on

Main Control Board

Trans missio n

1

GTM Ub

IPoE 1

GTMUb (evolved) +UMPT_G

IPoE1

2

GTM Ub

IPoF E


IPoFE

3

GTM Ub

E1 back up


E1 backup

4

GTM Ua/b

IPoE 1

GTMU (abandone d) +UMPT_G

IPoE1

5

GTM Ua/b

IPoF E

GTMU (abandone d) +UMPT_G

IPoFE

6

GTM Ua/b

E1 back up

GTMUb (abandone d) +UMPT_G

E1 backup

Board and Cable Connection Adjustment Before and After Reconstruction

12.7.2 UMTS Co-MPT Reconstruction Scenario Sc en ari o No .

Issue 01 (2015-12-30)

Before Reconstruct ion


Main Contr ol Board

Main Control Board

Trans missio n


Trans missio n


529



1

WMP T

IPoFE/ IPoE1/ ATM/ ATM& IPoFE

UMPT_U


2

UMPT _U


UMPT_U


12.7.3 LTE Co-MPT Reconstruction Scenario Sc en ari o No .

Before Reconstruct ion


Main Contr ol Board

Trans missio n

Main Control Board

Trans missio n

1

LMPT

IPoFE

UMPT_L

IPoFE

2

UMPT _L

IPoFE

UMPT_L

IPoFE


12.7.4 GSM and UMTS Co-MPT Reconstruction Scenario Sc en ari o No .

Before Reconstruction

After Reconstruction

Main Contr ol Board

GS M Tra nsm issio n

UM TS Tran smis sion

Main Contr ol Board

GS M Tra nsm issi on

UM TS Tran smiss ion

1

GTM Ub+W MPT/ UMP T_U

IPo E1

IPoE 1/IPo FE/A TM/ ATM &IPo FE

GTM Ub (evolv ed) +UMP T_GU

IPo E1


Issue 01 (2015-12-30)


Board and Cable Connection Adjustment Before and After Reconstruction Note 1

530


2

GTM Ub+W MPT/ UMP T_U


IPo FE



IPo FE


1. If separate transmission is adopted for GSM and UMTS before the reconstruction, this transmission mode will still be adopted after the reconstruction.

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 Ua/b+ WMP T/UM PT_U

IPo E1

IPoE 1/IPo FE

GTM Ua/b (aband oned) +UMP T_GU

IPo E1

IPoE 1/IPo FE

1. The WBBP already exists and a UBRI is added to provide CPRI ports for the GSM mode.

2. The UBBP already exists and is used to provide CPRI ports for the GSM mode.

4

GTM Ua/b+ WMP T/UM PT_U

IPo FE

IPoF E/IP oE1/ ATM /AT M&I PoFE


IPo FE

IPoF E/IPo E1/A TM/ ATM &IPo FE

1. The WBBP already exists and a UBRI is added to provide CPRI port for the GSM mode (including separate transmission and cotransmission).

2. The UBBP already exists and is used to provide CPRI ports for the GSM mode (including separate transmission and co-transmission).

5 Issue 01 (2015-12-30)

GTM

IPo

IPoE

GTM

IPo

IPoE


Hybird-MPT reconstruction 531


Ub+ UMP T_U


E1

1/IPo FE/G E/AT M/A TM &IPo FE/G E

Ub (evolv ed) +UMP T_GU

E1

IPo FE/ GE

IPoE 1/IPo FE/G E/AT M/A TM &IPo FE/G E


IPo E1

IPoE 1/IPo FE/G E

IPoF E/GE /IPo E1/A TM/ ATM &IPo FE/G E

Note: U is a coMPT base station . 6

GTM Ub+ UMP T_U Note: U is a coMPT base station .

7

GTM Ua/b+ UMP T_U Note: U is a coMPT base station .

8

GTM Ua/b+ UMP T_U Note: U is a coMPT base station .

Issue 01 (2015-12-30)

IPo FE/ GE

1/IPo FE/G E/AT M/A TM& IPoF E/GE

scenario:

IPo FE/ GE

IPoE 1/IPo FE/G E/AT M/A TM& IPoF E/GE

Hybird-MPT reconstruction scenario:


IPo E1

IPoE 1/IPo FE/G E



IPo E1

IPoF E/GE /IPoE 1/AT M/A TM& IPoF E/GE



G&[U]->[G*U]

G&[U]->[G*U]

G&[U]->[G*U]

G&[U]->[G*U]

532



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.

12.7.5 GSM and LTE Co-MPT Reconstruction Scenario Sc en ari o No .

Before Reconstructio n


Main Cont rol Boar d


LT E Tra nsm issi on

Main Contr ol Board



1

GTM Ub+L MPT/ UMP T_L

IPoE 1/

IPo FE

GTMU b (evolve d) +UMP T_GL

IPoE 1/

IPo FE


IPoF E

GTMU a/b (aband oned) +UMP T_GL

IPoE 1/

2

3

GTM Ub+L MPT/ UMP T_L

GTM Ua/b +LM PT/U MPT _L

E1 back up

IPoF E

IPoE 1/ E1 back up

IPo FE

IPo FE

Board and Cable Connection Adjustment Before and After Reconstruction (Note 1)

1. The GSM transmission uses IP over E1 transmission.

E1 back up 2. The GSM transmission uses E1 backup transmission.

IPo FE

1. If GSM and LTE use separate transmission before the reconstruction, separate transmission will still be adopted after the reconstruction. 2. If GSM and LTE use cotransmission before the reconstruction, co-transmission will still be adopted after the reconstruction.

IPo FE

E1 back up

1. The GSM transmission uses IP over E1 transmission. The baseband processing board of LTE is LBBP.

The baseband processing board of Issue 01 (2015-12-30)


533



LTE is UBBP.

2. The GSM transmission uses E1 backup transmission. The baseband processing board of LTE is LBBP.

The baseband processing board of LTE is UBBP.

4

GTM Ua/b +LM PT/U MPT _L

IPoF E

IPo FE


IPoF E

IPo FE

1. The baseband processing board of LTE is LBBP. If separate transmission is adopted for GSM and LTE before the reconstruction, it will still be 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 reconstruction, it will still be adopted after the reconstruction.

If co-transmission is adopted for GSM and LTE before the reconstruction, it will still be adopted after the reconstruction.

5 Issue 01 (2015-12-30)

GTM

IPoE

IPo

GTMU

IPoE

IPo


Hybird-MPT reconstruction 534


Ub+ UMP T_L Note: L is a coMPT base statio n. 6

GTM Ub+ UMP T_L


1/

FE/ GE

b (evolve d) +UMP T_GL

1/

IPoF E/G E

IPo FE/ GE


IPoE 1/

IPo FE/ GE

IPo FE/ GE

E1 back up

Note: L is a coMPT base statio n. 7

GTM Ua/b +UM PT_L Note: L is a coMPT base statio n.

8

GTM Ua/b +UM PT_L Note: L is a coMPT base statio n.

Issue 01 (2015-12-30)

E1 back up

IPoF E/G E

FE/ GE

scenario:

IPoF E/G E

IPo FE/ GE



IPoE 1/

IPo FE/ GE



IPoF E/G E

IPo FE/ GE


E1 back up

E1 back up


G&[L]->[G*L]

G&[L]->[G*L]

G&[L]->[G*L]

G&[L]->[G*L]

535



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.

12.7.6 UMTS and LTE Co-MPT Reconstruction Scenario Sc en ari o No .

Before Reconstruction


Main Contr ol Board

UMT S Tran smiss ion

LTE Tra nsm issio n

Main Cont rol Boar d

UMT S Trans missio n

LTE Tra nsm issio n

1

WMP T/UM PT_U +LMP T/UM PT_L


IPoF E

UMP T_U L+L MPT (evol ved)

IPoE1 /IPoF E/AT M/AT M&IP oFE

IPoF E

Board and Cable Connection Adjustment Before and After Reconstruction (Note 1)

UMTS is the reference mode.

LTE is the reference mode.

Or WMP T (inpositi on but not used) +UM PT_U L

Issue 01 (2015-12-30)


536


2

3

UMP T_U+ UMP T_L

UMP T_U+ LMPT or WMP T+U MPT_ L



IPoF E

UMP T_U+ UMP T_L Note: Either U with a UMP T_U or L with a UMP T_L is a coMPT base station .

Issue 01 (2015-12-30)

Note 2

IPoE IPoF 1/IPo E/G FE/G E E/AT M/AT M&I PoFE /GE

UMP T_U L+L MPT (evol ved)

IPoE IPoF 1/IPo E/G FE/G E E/AT M/AT M&I PoFE /GE

UMP T_U L+U MPT _UL

Note: U with a UMP T_U and L with a UMP T_L are both coMPT base station s. 4

UMP T_U L+U MPT _UL

or UMP T_U L+W MPT (evol ved)

IPoE1 /IPoF E/AT M/AT M&IP oFE

IPoF E

UMTS is the reference mode.

IPoE1 /IPoF E/GE/ ATM/ ATM &IPoF E/GE

IPoF E/G E


IPoE1 /IPoF E/GE/ ATM/ ATM &IPoF E/GE

IPoF E/G E


LTE is the reference mode.


U&[L]->[U*L] and L&[U]>[U*L]

U&[L]->[U*L] and L&[U]>[U*L]

537



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.

12.7.7 G&[U*L] or U&[G*L]/L&[G*U] Reconstruction Scenario Sc en ari o No .

Before Reconstruction Mai n Con trol Boa rd


UM TS Tra nsm issi on

LT E Tra nsm issio n

Mai n Con trol Boa rd




1

GT MU b

IPo E1/ E1 bac kup

IPo E1/I PoF E/G E/A TM/ AT M& IPo FE/ GE

IPo FE/ GE

GT MU b (evo lved ) +U MP T_ GU L

IPo E1/ E1 bac kup


IPo FE/ GE


IPo FE/ GE


IPo FE/ GE


IPo FE/ GE


IPo FE/ GE


+U MP T_U L

2

GT MU b +U MP T_U L

Issue 01 (2015-12-30)




G&[U*L]->[G*U*L]

G&[U*L]->[G*U*L]

538


3

GT MU a/b

IPo E1/ E1 bac kup


IPo FE/ GE

GT MU a/G TM Ub (aba ndo ned) +U MP T_ GU L

IPo E1/ E1 bac kup


IPo FE/ GE


IPo FE/ GE


IPo FE/ GE


IPo FE/ GE


IPo FE/ GE


WM PT+ UM PT_ GL

IPo E1/I PoF E/G E


IPo FE/ GE

W MP T (inposi tion but not use d) +U MP T_ GU L

IPo E1/I PoF E/G E


IPo FE/ GE


UM PT_ U+ UM PT_ GL

IPo E1/I PoF E/G E

IPo E1/I PoF E/G E/A TM/ AT M& IPo FE/

IPo FE/ GE

UM PT_ GU L+ UM PT_ GU L

IPo E1/I PoF E/G E

IPo E1/I PoF E/G E/A TM/ AT M& IPo FE/

IPo FE/ GE


+U MP T_U L

4


GT MU a/b +U MP T_U L

5

6

Issue 01 (2015-12-30)


G&[U*L]->[G*U*L]

G&[U*L]->[G*U*L]

U&[G*L]->[G*U*L]

U&[G*L]->[G*U*L]

539



GE 7

8

GE

LM PT+ UM PT_ GU

IPo E1/I PoF E/G E


IPo FE/ GE

LM PT (evo lved ) +U MP T_ GU L

IPo E1/I PoF E/G E


IPo FE/ GE


UM PT_ L+U MP T_G U

IPo E1/I PoF E/G E


IPo FE/ GE

UM PT_ GU L+ UM PT_ GU L

IPo E1/I PoF E/G E


IPo FE/ GE


L&[G*U]->[G*U*L]

L&[G*U]->[G*U*L]

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.

12.7.8 GU+L Co-MPT Reconstruction Scenario Sc en ari o No .

Issue 01 (2015-12-30)




After Reconstruction LT E Tra nsm issio n







540



Mo de 1

GT MU b+ WM PT/ UM PT_ U

IPo E1

UM PT_ L

IPo E1/I PoF E/A TM/ AT M& IPo FE

IPo FE


IPo E1

IPo FE

IPo FE

The UCIU-based BBU interconnection and UMPT-based BBU interconnection are included.

IPo FE

IPo FE

IPo FE

1. If separate transmission is adopted for GSM, UMTS, and LTE before the reconstruction, it will still be adopted after the reconstruction no matter whether UCIU-based BBU interconnection or UMPTbased BBU interconnection is used.

UM PT_ GU L 2

GT MU b+ WM PT/ UM PT_ U UM PT_ L

IPo FE


IPo FE

GT MU b (evo lved ) +U MP T_ GU 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 Issue 01 (2015-12-30)


541



through UCIUs or UMPTs.

3

GT MU a/b+ WM PT/ UM PT_ U

IPo E1

IPo E1/I PoF E

IPo FE

UM PT_ L


IPo E1

IPo E1/I PoF E

IPo FE

UM PT_ GU L

4

GT MU a/b+ UM PT_ U UM PT_ L

IPo FE


IPo FE


The baseband processing board of UMTS is UBBP. The UCIU-based BBU interconnection and UMPT-based BBU interconnection are included.

IPo FE


UM PT_ Issue 01 (2015-12-30)

The baseband processing board of UMTS is WBBP. The UCIU-based BBU interconnection and UMPT-based BBU interconnection are included.


IPo FE

1. The BBUs are interconnected through UCIUs. The baseband processing board of UMTS is WBBP.

The baseband processing board of UMTS is WBBP. 2. The BBUs are interconnected through UMPTs. 542



GU L

The baseband processing board of UMTS is WBBP.

The baseband processing board of UMTS is UBBP.

12.7.9 GL+U Co-MPT Reconstruction Scenario Sc en ari o No .


GS M Tra nsm issi on Mo de







1

GT MU b+L MP T/U MP T_L

IPo E1/ E1 bac kup

IPo FE/I PoE 1/A TM/ AT M& IPo FE

IPo FE


IPo E1/ E1 bac kup


IPo FE

UM PT_ U


UM PT_ GU L


1. GSM uses IP over E1 transmission no matter whether UCIU-based BBU interconnection or UMPT-based BBU interconnection is used. 



2. GSM uses E1 backup transmission no matter whether UCIU-based BBU interconnection or UMPT-based BBU interconnection is used.

Issue 01 (2015-12-30)


543


2

GT MU b+L MP T/U MP T_L UM PT_ U

IPo FE



IPo FE


IPo FE


IPo FE

1. If GSM, UMTS, and LTE use separate transmission before the reconstruction, this transmission mode will still be adopted after the reconstruction no matter whether UCIU-based BBU interconnection or UMPTbased BBU interconnection is used.

UM PT_ GU L

2. If the UMPT_L in BBU 0 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.

Issue 01 (2015-12-30)


544



3. If the UMPT_U in BBU 1 provides co-transmission ports for GSM, UMTS, and LTE before the reconstruction, the UMPT_GUL in BBU 0 provides co-transmission ports for GSM, UMTS, and LTE after the reconstruction, no matter whether UCIU-based BBU interconnection or UMPTbased BBU interconnection is used.

3

GT MU a/b+ LM PT/ UM PT_ L UM PT_ U

IPo E1/ E1 bac kup

IPo E1/I PoF E

IPo FE


IPo E1/ E1 bac kup

IPo FE/ AT M/ AT M& IPo FE

UM PT_ GU L

IPo FE

Note: If the main control boards of both BBU 0 and BBU 1 are UMPTs before the reconstruction, the two BBUs can be interconnected through either UCIUs or UMPTs. As shown in the following figure, each sub-scenario adopts one interconnection. 1. The GSM mode uses IP over E1 transmission. The baseband processing board of LTE is LBBP.


Issue 01 (2015-12-30)


545



2. The GSM mode uses E1 backup transmission. The baseband processing board of LTE is LBBP.


4

GT MU a/b+ LM PT/ UM PT_ L UM PT_ U

IPo FE


IPo FE


IPo FE


UM PT_ GU L

Issue 01 (2015-12-30)


IPo FE

Note: If the main control boards of both BBU 0 and BBU 1 are UMPTs before the reconstruction, the two BBUs can be interconnected through either UCIUs or UMPTs. As shown in the following figure, each sub-scenario adopts one interconnection. 1. If separate transmission is adopted for GSM, UMTS, and LTE before the reconstruction, it will still be adopted after the reconstruction (an added UBRI or a UBBP can be used to carry CPRI cables of GSM when the GTMUa/GTMUb is to be abandoned).

546



2. If the UMPT_L in BBU 0 provides co-transmission ports for GSM, UMTS, and LTE before the reconstruction, the UMPT_GUL in BBU 0 provides co-transmission ports for GSM, UMTS, and LTE after the reconstruction (an added UBRI or a UBBP can be used to carry CPRI cables of GSM when the GTMUa/GTMUb is to be abandoned).

3. If the UMPT_U in BBU 1 provides co-transmission ports for GSM, UMTS, and LTE before the reconstruction, the UMPT_GUL in BBU 0 provides co-transmission ports for GSM, UMTS, and LTE after the reconstruction (an added UBRI or a UBBP can be used to carry CPRI cables of GSM when the GTMUa/GTMUb is to be Issue 01 (2015-12-30)


547



abandoned).

12.7.10 G&[U*L]+[U*L] Reconstruction Scenario Sc en ari o No .









1

GT MU b+L MP T/U MP T_L

IPo E1/ E1 bac kup


IPo FE


IPo E1/ E1 bac kup


IPo FE

IPo FE/ GE


IPo FE/ GE

UM PT_ U



Hybird-MPT reconstruction scenario: G&[U*L]+[U*L]>[G*U*L]+[G*U*L]

UM PT_ GU L 2

BB U0: GT MU b+U MP T_ UL BB U1: UM PT_ UL

Issue 01 (2015-12-30)

IPo FE/ GE


IPo FE/ GE

BB U0: GT MU b (evo lved ) +U MP T_ GU L


Hybird-MPT reconstruction scenario: G&[U*L]+[U*L]>[G*U*L]+[G*U*L]

548



BB U1: UM PT_ GU L 3

BB U0: GT MU a/b+ UM PT_ UL

IPo E1/ E1 bac kup

BB U1: UM PT_ UL


IPo FE/ GE

BB U0: GT MU a/G TM Ub (aba ndo ned) +U MP T_ GU L

IPo E1/ E1 bac kup


IPo FE/ GE


IPo FE/ GE


IPo FE/ GE


G&[U*L]+[U*L]>[G*U*L]+[G*U*L]

BB U1: UM PT_ GU L 4

BB U0: GT MU a/b+ UM PT_ UL BB U1: UM PT_ UL

IPo FE/ GE


IPo FE/ GE

BB U0: GT MU a/G TM Ub (aba ndo ned) +U MP T_ GU L

G&[U*L]+[U*L]>[G*U*L]+[G*U*L]

BB U1: UM PT_ GU L

Issue 01 (2015-12-30)


549



12.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


Issue 01 (2015-12-30)


550


Scenario No.



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


Issue 01 (2015-12-30)


551


Scenario No.



U, L -> U*L

G, U -> G*U

GTMUb evolution


G, L -> G*L

Issue 01 (2015-12-30)

GTMUb evolution:


552



Scenario No.



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 Reconstruction


BBUs Before Reconstruction (Two Combined into One)

G, UL -> G*U*L

GBTS

Co-MPT NodeB, separate-MPT eNodeB

Co-MPT GUL base station

GBTS

Separate-MPT NodeB, co-MPT eNodeB


GBTS

Co-MPT UL base station


GBTS, co-MPT NodeB

Separate-MPT eNodeB


GU, L -> G*U*L Issue 01 (2015-12-30)


553


Scenario




BBUs Before Reconstruction (Two Combined into One)

GBTS, separateMPT NodeB

Co-MPT eNodeB


Co-MPT GU base station

Separate-MPT eNodeB


GBTS, co-MPT eNodeB

Separate-MPT NodeB


GBTS, separateMPT eNodeB

Co-MPT NodeB


Co-MPT GL base station

Separate-MPT NodeB


Co-MPT NodeB

Separate-MPT eNodeB


Separate-MPT NodeB

Co-MPT eNodeB


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

GL, U -> G*U*L

U, L -> U*L

Issue 01 (2015-12-30)


554


13 Examples for Co-MPT Reconstruction and Mode Transition

13

Examples for Co-MPT

Reconstruction and Mode Transition Examples for Co-MPT Reconstruction and Mode Transition

Issue 01 (2015-12-30)


555

3900 Series Multimode Base Station V100R011C10 Mode Transition Guide

Recommend Documents