Common Transmission (SRAN12.0 01)

SingleRAN
SRAN12.0
Common Transmission Feature

Parameter Description
Issue 01
Date 2016-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2016-09-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
Common Transmission Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 2
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between Base Station Types....................................................................................................................... 4
1.5 Functional Differences Between NB-IoT and FDD....................................................................................................... 5
2 Overview......................................................................................................................................... 6
2.1 Introduction.................................................................................................................................................................... 6
2.2 Benefits........................................................................................................................................................................... 6
2.3 Application Scenarios.....................................................................................................................................................6
2.3.1 Co-Transmission on the MBSC Side...........................................................................................................................6
2.3.2 Co-Transmission on the MBTS Side........................................................................................................................... 7
3 IP-based Co-Transmission on the MBSC Side...................................................................... 10

3.1 Co-Transmission for the Iub and Abis Interfaces......................................................................................................... 11
3.1.1 Network Topologies...................................................................................................................................................11
3.1.2 Protocol Stack............................................................................................................................................................12
3.1.3 Protocol Stack Application........................................................................................................................................ 13
3.2 Co-Transmission for the Iu-CS and A Interfaces......................................................................................................... 14
3.2.2 Protocol Stack............................................................................................................................................................15
3.3 Co-Transmission for the Iu-PS and Gb Interfaces........................................................................................................17
3.3.2 Protocol Stack............................................................................................................................................................18
4 Co-Transmission on the Multimode Base Station Side....................................................... 20

4.1 TDM-based Co-Transmission.......................................................................................................................................20
4.2 IP-based Co-Transmission............................................................................................................................................21
4.2.1 Overview................................................................................................................................................................... 22
4.2.2 Main-Control-Board-based Co-Transmission Through Panel Interconnection of the Separate-MPT Multimode
Base Station........................................................................................................................................................................ 23
4.2.3 UTRP-based Co-Transmission Through Panel Interconnection on the Separate-MPT Multimode Base Station Side
............................................................................................................................................................................................ 25
Issue 01 (2016-09-30) Huawei Proprietary and Confidential ii

SingleRAN
4.2.4 Main-Control-Board-based Co-Transmission Through Backplane Interconnection on the Separate-MPT

Multimode Base Station Side............................................................................................................................................. 26
4.2.5 UTRPc-based Co-Transmission Through Backplane Interconnection on the Separate-MPT Multimode Base
Station Side.........................................................................................................................................................................28
4.2.6 Co-Transmission on the Co-MPT Multimode Base Station Side..............................................................................31
5 Related Features...........................................................................................................................33
5.1 MRFD-121101 IP-Based BSC and RNC Co-Transmission on MBSC Side................................................................33
5.2 MRFD-120111 TDM-Based Multi-mode Co-Transmission via Backplane on BS side(GBTS)................................. 34
5.3 MRFD-120121 TDM-Based Multi-mode Co-Transmission via Backplane on BS side(NodeB)................................ 34
5.4 MRFD-121114 IP-Based Multi-mode Co-Transmission on BS side(GBTS).............................................................. 34
5.5 MRFD-121124 IP-Based Multi-mode Co-Transmission on BS side(NodeB)............................................................. 35
5.6 MRFD-121134 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)........................................................... 35
5.7 MRFD-121144 IP-Based Multi-mode Co-Transmission on BS side(LTE TDD)........................................................ 36
5.8 MRFD-121154 IP-Based Multi-mode Co-Transmission on BS side(NB-IoT)............................................................36
6 Network Impact........................................................................................................................... 37
7 Engineering Guidelines............................................................................................................. 38
7.1 When to Use................................................................................................................................................................. 39
7.2 Required Information................................................................................................................................................... 39
7.3 Planning........................................................................................................................................................................ 39
7.4 Co-Transmission for Iub and Abis Interfaces on the MBSC Side................................................................................40
7.4.1 Requirements............................................................................................................................................................. 40
7.4.2 Data Preparation........................................................................................................................................................ 41
7.4.3 Precautions.................................................................................................................................................................45
7.4.4 Hardware Adjustment................................................................................................................................................45
7.4.5 Initial Configuration.................................................................................................................................................. 45
7.4.6 Activation Observation..............................................................................................................................................46
7.5 Main-Control-Board-based Co-Transmission Through Panel Interconnection on the Separate-MPT UG Multimode
Base Station Side in IP over FE/GE Mode.........................................................................................................................46
7.5.1 Requirements............................................................................................................................................................. 46
7.5.3 Precautions.................................................................................................................................................................48
7.6 Main-Control-Board-based Co-Transmission Through Panel Interconnection on the Separate-MPT LG/TG/MG
Multimode Base Station Side in IP over FE/GE Mode...................................................................................................... 52
7.6.1 Requirements............................................................................................................................................................. 53
7.6.3 Precautions.................................................................................................................................................................55
Issue 01 (2016-09-30) Huawei Proprietary and Confidential iii

SingleRAN
7.7 Main-Control-Board-based Co-Transmission Through Panel Interconnection on the Separate-MPT L+GU/T+GU/M

+GU Multimode Base Station Side in IP over FE/GE Mode............................................................................................. 59
7.7.1 Requirements............................................................................................................................................................. 59
7.7.3 Precautions.................................................................................................................................................................62
7.8 Main-Control-Board-based Co-Transmission Through Backplane Interconnection on the Separate-MPT LG/TG/MG
7.8.1 Requirements............................................................................................................................................................. 69
7.8.3 Precautions.................................................................................................................................................................71
7.9 Main-Control-Board-based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG
7.9.1 Requirements............................................................................................................................................................. 76
7.9.3 Precautions.................................................................................................................................................................78
7.10 UTRPc-based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG Multimode Base
Station Side in IP over FE/GE Mode..................................................................................................................................83
7.10.1 Requirements........................................................................................................................................................... 83
7.10.2 Data Preparation...................................................................................................................................................... 84
7.10.3 Precautions...............................................................................................................................................................86
7.10.4 Hardware Adjustment..............................................................................................................................................86
7.10.5 Initial Configuration................................................................................................................................................ 86
7.10.6 Activation Observation............................................................................................................................................90
7.11 UTRPc-based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG+L/UG+T/UG+M
7.11.1 Requirements........................................................................................................................................................... 90
7.11.2 Data Preparation...................................................................................................................................................... 91
7.11.3 Precautions...............................................................................................................................................................94
7.11.4 Hardware Adjustment.............................................................................................................................................. 94
7.11.5 Initial Configuration................................................................................................................................................ 94
7.11.6 Activation Observation.......................................................................................................................................... 100
7.12 Main-Control-Board-based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG+L/UG
+T/UG+M Multimode Base Station Side in IP over FE/GE Mode..................................................................................101
7.12.1 Requirements......................................................................................................................................................... 101
7.12.2 Data Preparation.................................................................................................................................................... 103
Issue 01 (2016-09-30) Huawei Proprietary and Confidential iv

SingleRAN
7.12.3 Precautions.............................................................................................................................................................106
7.12.4 Hardware Adjustment............................................................................................................................................106
7.12.5 Initial Configuration.............................................................................................................................................. 106
7.12.6 Activation Observation.......................................................................................................................................... 112
7.13 Reconstruction from Transmission Through the Main Control Board Panel on a GBTS to Main-Control-Board-
based Co-Transmission Through Panel Interconnection on the Separate-MPT UG Multimode Base Station Side in IP
over FE/GE Mode.............................................................................................................................................................113
7.13.1 Requirements......................................................................................................................................................... 113
7.13.3 Reconstruction Preparations and Procedure.......................................................................................................... 115
7.13.4 Precautions.............................................................................................................................................................117
7.13.5 Reconfiguration..................................................................................................................................................... 117
7.13.6 Rollback................................................................................................................................................................. 117
based Co-Transmission Through Backplane Interconnection on the Separate-MPT LG/TG/MG Multimode Base Station
Side in IP over FE/GE Mode............................................................................................................................................ 118
7.14.1 Requirements......................................................................................................................................................... 118
7.14.4 Precautions.............................................................................................................................................................123
7.14.6 Rollback.................................................................................................................................................................124
based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG Multimode Base Station Side
.......................................................................................................................................................................................... 124
7.15.1 Requirements......................................................................................................................................................... 124
7.15.4 Precautions.............................................................................................................................................................129
7.15.6 Rollback.................................................................................................................................................................130
7.16 Reconstruction from Main-Control-Board-based IP Co-Transmission Through Panel Interconnection to UTRPc-
based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG Multimode Base Station Side in
IP over FE/GE Mode........................................................................................................................................................ 130
7.16.1 Requirements......................................................................................................................................................... 130
7.16.4 Precautions.............................................................................................................................................................135
7.16.6 Rollback.................................................................................................................................................................136
7.17 Reconstruction from UTRPc-Backplane-Interconnection Co-Transmission on the Separate-MPT UG Multimode
Base Station Side to UTRPc-Backplane-Interconnection Co-Transmission on the Separate-MPT UG+L/UG+T
Multimode Base Station Side in IP over FE/GE Mode.................................................................................................... 137
7.17.1 Requirements......................................................................................................................................................... 137
Issue 01 (2016-09-30) Huawei Proprietary and Confidential v

SingleRAN

7.17.4 Precautions.............................................................................................................................................................143
7.17.7 Rollback.................................................................................................................................................................146
7.18 Reconstruction from Main-Control-Board-based Co-Transmission Through Panel Interconnection on the UG
Multimode Base Station Side to UTRPc-based Co-Transmission Through Backplane Interconnection on the Separate-
MPT UG+L/UG+T Multimode Base Station Side........................................................................................................... 146
7.18.1 Requirements......................................................................................................................................................... 147
7.18.4 Precautions.............................................................................................................................................................152
7.18.6 Rollback.................................................................................................................................................................153
7.19 Reconstruction from Main-Control-Board-Panel-Interconnection Co-Transmission on the Separate-MPT UG
Multimode Base Station Side to Main-Control-Board-Panel-Interconnection Co-Transmission on the Separate-MPT UG
+L/UG+T Multimode Base Station Side.......................................................................................................................... 154
7.19.1 Requirements......................................................................................................................................................... 154
7.19.4 Precautions.............................................................................................................................................................160
7.19.6 Rollback.................................................................................................................................................................161
7.20 Main-Control-Board-based Co-Transmission Through Panel Interconnection on the Separate-MPT UG Multimode
Base Station Side in IP over E1/T1 Mode........................................................................................................................ 162
7.20.1 Requirements......................................................................................................................................................... 162
7.20.3 Precautions.............................................................................................................................................................164
7.20.6 Activation Observation..........................................................................................................................................166
7.21 UTRP4-based Co-Transmission Through Panel Interconnection on the Separate-MPT UG Multimode Base Station
Side in IP over E1/T1 Mode............................................................................................................................................. 167
7.21.1 Requirements......................................................................................................................................................... 167
7.21.3 Precautions.............................................................................................................................................................169
7.22 GTMU-based TDM Co-Transmission on the Separate-MPT GU Multimode Base Station Side............................172
7.22.1 Requirements......................................................................................................................................................... 172
7.22.3 Precautions.............................................................................................................................................................173
Issue 01 (2016-09-30) Huawei Proprietary and Confidential vi

SingleRAN

7.23 Co-Transmission on the Co-MPT GU/GL/UL/GT/UT/LT/GM/UM/LM/TM Multimode Base Station Side in IP
over FE/GE Mode.............................................................................................................................................................174
7.23.1 Requirements......................................................................................................................................................... 174
7.23.3 Precautions.............................................................................................................................................................176
7.24 Co-Transmission on the Co-MPT GULTM Multimode Base Station Side in IP over FE/GE Mode.......................178
7.24.1 Requirements......................................................................................................................................................... 178
7.24.3 Precautions.............................................................................................................................................................181
7.25 Co-Transmission on the Hybrid-MPT GUL/GUT/GUM Multimode Base Station Side in IP over FE/GE Mode..184
7.25.1 Requirements......................................................................................................................................................... 184
7.25.3 Precautions.............................................................................................................................................................187
7.26 Main-Control-Board-based Co-Transmission Through Backplane Interconnection on the Separate-MPT
LGU/TGU/MGU Multimode Base Station Side in IP over FE/GE Mode....................................................................... 192
7.26.1 Requirements......................................................................................................................................................... 192
7.26.3 Precautions.............................................................................................................................................................196
7.27 Performance Monitoring...........................................................................................................................................203
7.27.1 IP-based Co-Transmission on the MBSC Side......................................................................................................203
7.27.2 IP-based Co-Transmission on the Multimode Base Station Side.......................................................................... 204
7.28 Possible Issues.......................................................................................................................................................... 204
7.28.1 IP-based Co-Transmission on the MBSC Side......................................................................................................204
7.28.2 IP-based Co-Transmission on the Multimode Base Station Side.......................................................................... 204
8 Parameters................................................................................................................................... 206
9 Counters...................................................................................................................................... 208
10 Glossary..................................................................................................................................... 214
Issue 01 (2016-09-30) Huawei Proprietary and Confidential vii

SingleRAN
11 Reference Documents............................................................................................................. 215
Issue 01 (2016-09-30) Huawei Proprietary and Confidential viii

SingleRAN
Common Transmission Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the common transmission (co-transmission) solutions that can be
implemented on the multimode base station controller (MBSC) and multimode base station
side (MBTS) and provides engineering guidelines for these solutions.
This document covers the following feature on the MBSC side:
l MRFD-121101 IP-Based BSC and RNC Co-Transmission on MBSC Side
This document covers the following features on the MBTS side:
l MRFD-120111 TDM-Based Multi-mode Co-Transmission via Backplane on BS

side(GBTS)
l MRFD-121114 IP-Based Multi-mode Co-Transmission on BS side(GBTS)
l MRFD-121124 IP-Based Multi-mode Co-Transmission on BS side(NodeB)
side(NodeB)
l MRFD-121134 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)
l MRFD-121144 IP-Based Multi-mode Co-Transmission on BS side(LTE TDD)
l MRFD-121154 IP-Based Multi-mode Co-Transmission on BS side(NB-IoT)
NOTE
For details about IP transmission, see IP Transmission Feature Parameter Description for SingleRAN.
For definitions of base stations described in this document, see section "Base Station
Products" in SRAN Networking and Evolution Overview Feature Parameter Description.
Unless otherwise specified, in this document, LTE, eNodeB, and eRAN always include FDD,
TDD, and NB-IoT. The "L", "T", and "M" in RAT acronyms refer to LTE FDD, LTE TDD,
and LTE NB-IoT, respectively.
The scenarios in which co-MPT base stations use a UMDU are similar to the scenarios in
which co-MPT base stations use a UMPT. Unless otherwise specified, the UMPT is used as
an example for descriptions and the UMDU is not described in this document. In the current
version, the base station using a UMDU as the main control board does not support NB-IoT.
Issue 01 (2016-09-30) Huawei Proprietary and Confidential 1

SingleRAN
The co-transmission principle of an eGBTS using a GTMUb/GTMUc as the main control

board is the same as that of a GBTS using a GTMUb/GTMUc as the main control board, but
their data configurations are different. This document uses the GBTS using a GTMUb/
GTMUc as an example to describe the co-transmission principle, and describes data
configurations for both the GBTS and eGBTS in different application scenarios.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version.
SRAN12.1 01 (2017-03-08)
This issue does not include any changes.
SRAN12.1 Draft B (2016-12-30)

This issue includes the following changes.

SingleRAN
Change Change Description Parameter Change

Type
Feature Changed the following features from optional None

change features to basic features, updated their feature
IDs, and removed their corresponding license
control items:
l Changed MRFD-211502 IP-Based BSC and
RNC Co-Transmission on MBSC Side into
MRFD-121101 IP-Based BSC and RNC Co-
Transmission on MBSC Side
l Changed MRFD-211504 TDM-Based Multi-
mode Co-Transmission via Backplane on BS
side(GBTS) into MRFD-120111 TDM-
Based Multi-mode Co-Transmission via
Backplane on BS side(GBTS)
l Changed MRFD-221504 TDM-Based Multi-
mode Co-Transmission via Backplane on BS
side(NodeB) into MRFD-120121 TDM-
Based Multi-mode Co-Transmission via
Backplane on BS side(NodeB)
l Changed MRFD-211501 IP-Based Multi-
mode Co-Transmission on BS side(GBTS)
into MRFD-121114 IP-Based Multi-mode
Co-Transmission on BS side(GBTS)
mode Co-Transmission on BS side(NodeB)
Co-Transmission on BS side(NodeB)
mode Co-Transmission on BS side(eNodeB)
Co-Transmission on BS side(eNodeB)
mode Co-Transmission on BS side(LTE
TDD) into MRFD-121144 IP-Based Multi-
mode Co-Transmission on BS side(LTE
TDD)
mode Co-Transmission on BS side(NB-IoT)
Co-Transmission on BS side(NB-IoT)

SingleRAN

Type
Supported NB-IoT. For details, see the None

following sections:
l 4.2.1 Overview
l 4.2.4 Main-Control-Board-based Co-
Transmission Through Backplane
Interconnection on the Separate-MPT
Multimode Base Station Side
l 5 Related Features
l 7 Engineering Guidelines
Editorial None None

change
SRAN12.1 Draft A (2016-10-30)

Draft A (2016-10-30) of SRAN12.1 introduces the following changes to Issue 01
(2016-02-29) of SRAN11.1.

Type
Feature Supported the EXOUb and FG2e boards. None

change
Editorial None None

change
1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations
Feature ID Feature Name Suppor Suppor Suppor
ted by ted by ted by
Macro Micro LampSi
Base Base te Base
Station Station Station
s s s
MRFD-121101 IP-Based BSC and RNC Co- Y N N

MRFD-120111 TDM-Based Multi-mode Co- Y N N

Transmission via Backplane on BS
side(GBTS)

SingleRAN
Feature ID Feature Name Suppor Suppor Suppor

ted by ted by ted by
Macro Micro LampSi
Base Base te Base
Station Station Station
s s s
MRFD-120121 TDM-Based Multi-mode Co- Y N N

Transmission via Backplane on BS
side(NodeB)
MRFD-121114 IP-Based Multi-mode Co- Y N N

Transmission on BS side(GBTS)
MRFD-121124 IP-Based Multi-mode Co- Y Y Y

Transmission on BS side(NodeB)
MRFD-121134 IP-Based Multi-mode Co- Y Y Y

Transmission on BS side(eNodeB)
MRFD-121144 IP-Based Multi-mode Co- Y N N

Transmission on BS side(LTE
TDD)
MRFD-121154 IP-Based Multi-mode Co- Y Y N

Transmission on BS side(NB-IoT)
Function Implementation in Macro, Micro, and LampSite Base Stations

The function implementation is the same for macro, micro, and LampSite base stations.
Among micro base stations, only the BTS3911E supports the IP-Based Multi-mode Co-
Transmission on BS side feature.
1.5 Functional Differences Between NB-IoT and FDD

NB-IoT NB-IoT FDD FDD Feature Difference
Feature ID Feature Feature ID Name
Name
MRFD-1211 IP-Based MRFD-12113 IP-Based None

54 Multi-mode 4 Multi-mode
Co- Co-
Transmission Transmission
on BS on BS
side(NB-IoT) side(eNodeB)

SingleRAN
Common Transmission Feature Parameter Description 2 Overview
2 Overview
2.1 Introduction
This document describes common transmission, which enables multiple modes of a GU, GL,
UL, GUL, GT, UT, or GUT MBTS or an MBSC to share transmission ports and the transport
network.
NOTE
l An MBSC mentioned in this document can be a GU MBSC, a BSC, or an RNC. In addition, the
GSM side of an MBSC is referred to as BSC, and the UMTS side of an MBSC is referred to as RNC
in this document.
l In this document, the GSM side of an MBTS is referred to as GBTS or eGBTS, the UMTS side of an
MBTS is referred to as NodeB, and the LTE side of an MBTS is referred to as eNodeB. The
operation and maintenance (O&M) of a GBTS is implemented by a BSC whereas the O&M of an
eGBTS is implemented by the eGBTS itself.
2.2 Benefits
For operators, co-transmission reduces the capital expenditure (CAPEX) and operating
expense (OPEX) and simplifies maintenance of the transport network in the following ways:
l Sharing transmission ports reduces transmission links.
l Sharing the transport network simplifies transmission configuration and maintenance.
l Smooth evolution from GSM to UMTS or LTE can be achieved with fewer transport
network adjustments.
2.3 Application Scenarios
2.3.1 Co-Transmission on the MBSC Side

Figure 2-1 shows a typical scenario of co-transmission on the MBSC side.

SingleRAN
Figure 2-1 Typical scenario of co-transmission on the MBSC side
As shown in Figure 2-1, the GSM and UMTS networks share an MBSC. In this situation, co-
transmission is implemented in the following ways:
l The Iu-CS and A interfaces as well as the Iu-PS and Gb interfaces of the MBSC share an
IP transport network when GSM and UMTS share the core network (including the MSC
server, MGW, and SGSN).
l The Iub and Abis interfaces of the MBSC share an IP transport network.
2.3.2 Co-Transmission on the MBTS Side

Multimode base stations are classified into separate-MPT multimode base stations and co-
MPT multimode base stations based on the deployment mode of main processing and
transmission (MPT) boards.
TDM-based co-transmission is supported only by separate-MPT GU multimode base stations.

For details, see 4.1 TDM-based Co-Transmission.
IP-based co-transmission is supported by separate-MPT and co-MPT multimode base

stations.
IP-based Co-Transmission of a Separate-MPT MBTS

NOTE
A separate-MPT multimode base station is a physical base station in which different modes use different
main control boards. Such a multimode base station consists of multiple logical base stations, each of
which has an independent O&M channel.
The BBU3910A is an outdoor BBU, which integrates the main control, transmission, and baseband
processing functions. It cannot be used in separate-MPT base stations.
Table 2-1 describes different types of co-transmission for a separate-MPT base station.

SingleRAN
Table 2-1 Different types of co-transmission for a separate-MPT base station

Co-Transmission Description
Type
Co- Main- The main control board of a mode provides an FE/GE port or an
trans control- E1/T1 port as the co-transmission port. The main control boards of
missi board-based all modes are connected through panel interconnection.
on co-
throu transmission
gh through
panel panel
interc interconnect
onne ion
ction
UTRP- The UTRP of a mode provides an FE/GE port or an E1/T1 port as
based co- the co-transmission port. The main control boards of all modes are
transmission connected through panel interconnection or the main control boards
through of other modes are connected to the UTRP through panel
panel interconnection.
interconnect
ion
Co- Main- The main control board of a mode provides an FE/GE port as the
trans control- co-transmission port. The main control boards of all modes are
missi board-based connected through backplane interconnection.
on co-
throu transmission
gh through
back backplane
plane interconnect
interc ion
onne
ction UTRPc- The UTRPc of a mode provides an FE/GE port as the co-
based co- transmission port. The main control boards of all modes are
transmission connected to the UTRPc through backplane interconnection.
through
backplane
interconnect
ion
IP-based Co-Transmission of a Co-MPT MBTS

NOTE
A co-MPT multimode base station is a physical base station in which different modes share one main
control board. Such a multimode base station has only one logical base station and one O&M channel.
Different modes of a co-MPT multimode base station share one main control board and one
O&M channel. The GSM side of a co-MPT multimode base station must be an eGBTS.
The main control board or UTRP board of a co-MPT multimode base station provides an
FE/GE port or an E1/T1 port as the co-transmission port.

SingleRAN
NOTE
The co-transmission principle for macro base stations is the same as that for distributed base stations
(DBSs). This document uses a DBS as an example to describe co-transmission on the base station side.
The BBU3910A is an integrated module, providing functions such as main control, transmission, and
baseband processing.
If the link between the co-transmission port and the transport network is disconnected, services of all
modes are interrupted.

SingleRAN
Common Transmission Feature Parameter Description 3 IP-based Co-Transmission on the MBSC Side
3 IP-based Co-Transmission on the MBSC

Side
This chapter describes the feature MRFD-121101 IP-Based BSC and RNC Co-Transmission
on MBSC Side. Co-transmission on the MBSC side can be classified into:
l Co-transmission for the Iub and Abis interfaces
l Co-transmission for the Iu-CS and A interfaces
l Co-transmission for the Iu-PS and Gb interfaces
IP-based BSC/RNC co-transmission differs from IP-based BSC/RNC separate-transmission in
terms of network topologies and IP address configurations. The following sections describe
the network topologies, protocol stack, and protocol stack application for IP-based BSC and
RNC co-transmission.

SingleRAN
3.1 Co-Transmission for the Iub and Abis Interfaces
3.1.1 Network Topologies

When an MBSC works in GU mode, the Iub and Abis interfaces share an IP transport
network and transmission ports on the interface boards of the MBSC. Figure 3-1 shows the
network topology of co-transmission in FE/GE/10GE mode. Figure 3-2 shows the network
topology of co-transmission in E1/T1 over STM-1/OC-3 mode. Co-transmission in FE/GE/
10GE mode is recommended because an FE/GE/10GE port has a wider bandwidth than an
E1/T1 port.
Figure 3-1 Co-transmission in FE/GE/10GE mode for the Iub and Abis interfaces on the
MBSC side
Figure 3-2 Co-transmission in E1/T1 over STM-1/OC-3 mode for the Iub and Abis interfaces
on the MBSC side

SingleRAN
NOTE
l IP_GCP: GSM control-plane IP address

l IP_GUP: GSM user-plane IP address
l IP_UCP: UMTS control-plane IP address
l IP_UUP: UMTS user-plane IP address
The MBSC Abis/Iub interface board identifies GSM data and UMTS data, and sends the data
to the corresponding GSM or UMTS service processing board and GSM or UMTS signaling
processing board.
3.1.2 Protocol Stack

Figure 3-3 shows the protocol stack of IP-based co-transmission for the Iub and Abis
interfaces when the GSM base station is a GBTS.
Figure 3-3 Protocol stack of IP-based co-transmission for the Iub and Abis interfaces (1)
As shown in Figure 3-3, the interface board shared by the Iub and Abis interfaces processes
protocols at the physical layer, data link layer, network layer (IP), and transport layer (UDP
and UDP MUX). The protocols at other layers are processed by the control-plane processing
boards and user-plane processing boards of UMTS and GSM separately.
Figure 3-4 shows the protocol stack of IP-based co-transmission for the Iub and Abis
interfaces when the GSM base station is an eGBTS.

SingleRAN
Figure 3-4 Protocol stack of IP-based co-transmission for the Iub and Abis interfaces (2)
For the protocol stack on the O&M plane for Iub and Abis co-transmission, see the "Transport
Protocol Stacks for Interfaces" section in IP Transmission Feature Parameter Description.
3.1.3 Protocol Stack Application

Physical Layer
The following types of ports on MBSC interface boards support IP-based co-transmission for
the Iub and Abis interfaces:
l GE optical ports on a GOUa/GOUc/GOUe
l FE/GE electrical ports on an FG2a/FG2c/FG2e
l 10GE optical ports on an EXOUa/EXOUb
l Channelized STM-1/OC-3 optical ports on a POUa/POUc
Data Link Layer

When co-transmission in FE/GE mode is used for the Iub and Abis interfaces, the Ethernet
protocol is used at the data link layer.
When co-transmission in E1/T1 over STM-1/OC-3 mode is used for the Iub and Abis
interfaces, Point-to-Point Protocol (PPP) or Multi-Link Point-to-Point Protocol (MLPPP) is
used at the data link layer. A PPP link can be bound with one to thirty-one 64 kbit/s timeslots
carried on the same E1/T1. In an MLPPP link group, each PPP link is bound with the same
number of timeslots (at least eight timeslots). GBTS/eGBTS data and NodeB data can be
transmitted over different PPP links or MLPPP link groups. Alternatively, GBTS/eGBTS data
and NodeB data can be transmitted over the same PPP link or MLPPP link group and be
distinguished by UDP port numbers.
Network Layer
Based on communication types, IP addresses can be classified into port IP addresses and
device IP addresses. A port IP address refers to a physical IP address of a port on an interface
board. A device IP address refers to a logical IP address of an interface board. Port IP

SingleRAN
addresses must be configured and device IP addresses are optional. The Iub and Abis
interfaces can share one port IP address or use different port IP addresses.
Either port IP addresses or device IP addresses can be used as the following types of IP
addresses:
l Control-plane and user-plane IP addresses on the Iub and Abis interfaces

l O&M channel IP addresses
The IP address planning principles are as follows:
l Control-plane and user-plane IP addresses of the Iub interface

The control-plane and user-plane IP addresses of the Iub interface can be the same or
different.
l Control-plane and user-plane IP addresses of the Abis interface
The control-plane and user-plane IP addresses of the Abis interface can be the same or
different.
The Iub and Abis interfaces can use the same or different control-plane and user-plane IP
addresses.
l O&M channel IP address
On the Iub interface:
– If the O&M channel between the NodeB and the U2000 passes through the MBSC,
the O&M channel IP address must be configured on the NodeB and U2000, and an
O&M packet forwarding route must be configured on the MBSC. In this scenario,
the MBSC forwards packets between the U2000 and the NodeB.
– If the O&M channel between the NodeB and the U2000 does not pass through the
MBSC, the O&M channel IP address must be configured on the NodeB and U2000.
On the Abis interface, the GBTS IP addresses must be configured on the MBSC. If
the BSC is not enabled with the GBFD-118613 BTS Multi-IP Address feature, the
O&M channel, control-plane, and user-plane IP addresses of the GBTS must be the
same. If the BSC is enabled with the GBFD-118613 BTS Multi-IP Address feature,
the O&M channel IP address of the GBTS can be different from the control-plane
and user-plane IP addresses of the GBTS.
3.2 Co-Transmission for the Iu-CS and A Interfaces

When the MBSC works in GU mode, the Iu-CS and A interfaces share an IP transport
network and transmission ports on the interface boards of the MBSC. Figure 3-5 shows the
network topology of co-transmission in FE/GE mode. Figure 3-6 shows the network topology
of co-transmission in E1/T1 over STM-1/OC-3 mode. Co-transmission in FE/GE mode is
recommended because an FE/GE port has a wider bandwidth than an E1/T1 port.
The MBSC Iu-CS/A interface board identifies GSM data and UMTS data and sends the data
to the corresponding GSM or UMTS service processing board and signaling processing
board.

SingleRAN
Figure 3-5 Co-transmission in FE/GE mode for the Iu-CS and A interfaces
Figure 3-6 Co-transmission in E1/T1 over STM-1/OC-3 mode for the Iu-CS and A interfaces
NOTE
IP_GCP: GSM control-plane IP address

IP_GUP: GSM user-plane IP address
IP_UCP: UMTS control-plane IP address
IP_UCP: UMTS user-plane IP address

Figure 3-7 shows the protocol stack of IP-based co-transmission for the Iu-CS and A
interfaces.

SingleRAN
Figure 3-7 Protocol stack of IP-based co-transmission for the Iu-CS and A interfaces
As shown in Figure 3-7, the interface board shared by the Iu-CS and A interfaces processes
and UDP MUX). The protocols at other layers are processed by the control-plane and user-
plane processing boards of UMTS and GSM separately.
Physical Layer
the Iu-CS and A interfaces:

l Channelized STM-1/OC-3 optical ports on a POUa/POUc
Data Link Layer

When co-transmission in FE/GE mode is used for the Iu-CS and A interfaces, the Ethernet
protocol is used at the data link layer.
When co-transmission in E1/T1 over STM-1/OC-3 mode is used for the Iu-CS and A
interfaces, PPP or MLPPP is used at the data link layer. A PPP link can be bound with one to
thirty-one 64 kbit/s timeslots carried on the same E1/T1. In an MLPPP link group, each PPP
link is bound with the same number of timeslots (at least eight timeslots).
Network Layer
Control-plane and user-plane IP addresses of the Iu-CS and A interfaces can be either port IP
addresses or device IP addresses. The Iu-CS and A interfaces can use the same or different

SingleRAN
port IP addresses. It is recommended that the Iu-CS and A interfaces use different port IP
addresses.
The IP address planning principles are as follows:
l Control-plane IP addresses
The Iu-CS and A interfaces can use the same control-plane IP address.
Generally, SCTP links are dual-homed. One interface board is configured with two
control-plane IP addresses, one IP address used as the primary IP address and the other
used as the secondary IP address. The SCTP links over the Iu-CS and A interfaces on the
MBSC side use the two IP addresses. Iu-CS interface data and A interface data are
distinguished by the SCTP port numbers in them. For details about SCTP links on the Iu-
CS and A interfaces, see IP Transmission Feature Parameter Description.
l User-plane IP addresses
The Iu-CS and A interfaces use different user-plane IP addresses.
The UDP MUX technique uses different Real-time Transfer Protocol (RTP) compression
algorithms on the Iu-CS and A interfaces. Therefore, different user-plane IP addresses
must be planned for the Iu-CS and A interfaces to distinguish Iu-CS interface data from
A interface data.
On the Iu-CS interface and the A interface, the control-plane IP address can be the same as
the user-plane IP address.
3.3 Co-Transmission for the Iu-PS and Gb Interfaces

When the MBSC works in GU mode, the Iu-PS and Gb interfaces share an IP transport
network and transmission ports on the interface boards of the MBSC. The Gb interface does
not support IP over E1. Therefore, the Iu-PS and Gb interfaces can only use co-transmission
in FE/GE mode. Figure 3-8 shows the network topology of co-transmission in FE/GE mode
for the Iu-PS and Gb interfaces.
The MBSC Gb/Iu-PS interface board identifies GSM data and UMTS data and sends the data
to the corresponding GSM or UMTS service processing board and signaling processing
board.
Figure 3-8 Co-transmission in FE/GE mode for the Iu-PS and Gb interfaces

SingleRAN
NOTE
IP_GSM: GSM IP address

IP_UMTS: UMTS IP address

Figure 3-9 shows the protocol stack of IP-based co-transmission for the Iu-PS and Gb
interfaces.
Figure 3-9 Protocol stack of IP-based co-transmission for the Iu-PS and Gb interfaces
As shown in Figure 3-9, the interface board shared by the Iu-PS and Gb interfaces processes
and UDP MUX). The protocols at other layers are processed by the control-plane and user-
plane processing boards of UMTS and GSM separately.
Physical Layer
the Iu-PS and Gb interfaces:

Data Link Layer

When co-transmission is implemented on the Iu-PS and Gb interfaces, the Ethernet protocol is
used at the data link layer.

SingleRAN
Network Layer
Control-plane and user-plane IP addresses of the Iu-PS and Gb interfaces can be either port IP
addresses or device IP addresses. The Iu-PS and Gb interfaces can use the same or different
port IP addresses. It is recommended that the Iu-PS and Gb interfaces use different port IP
addresses.
l Control-plane IP addresses
Generally, SCTP links on the Iu-PS interface are dual-homed. One interface board is
configured with two control-plane IP addresses, one IP address used as the primary IP
address and the other used as the secondary IP address. For details about SCTP links on
the Iu-PS interface, see IP Transmission Feature Parameter Description.
No control-plane IP address is assigned to the Gb interface.
l User-plane IP addresses
The Iu-PS and Gb interfaces can use the same or different IP addresses.
On the Iu-PS interface, the Tunnel End Point Identifier (TEID) at the GPRS Tunneling
Protocol-User plane (GTP-U) layer is used to identify users. GTP-U only uses UDP port
2152.
On the Iu-PS interface, the control-plane IP address can be the same as the user-plane IP
address.

SingleRAN
Common Transmission Feature Parameter Description 4 Co-Transmission on the Multimode Base Station Side
4 Co-Transmission on the Multimode Base

Station Side
4.1 TDM-based Co-Transmission

GU multimode base stations support TDM-based co-transmission. This section covers the
following optional features:
side(NodeB)
side(GBTS)
TDM-based co-transmission for the Iub and Abis Interfaces on the multimode base station
side can be implemented by TDM over packet (TOP). The GSM and UMTS traffic can be
multiplexed onto the same SDH/PDH network by using the TDM timeslot cross-connection
function. The RNC and NodeB can use the fractional ATM or fractional IP function to map
ATM cells or IP packets onto several E1 timeslots. The GSM and UMTS networks can share
TDM timeslots on the Abis and Iub interfaces. Figure 4-1 shows the principle of TDM-based
co-transmission.
Figure 4-1 Principle of TDM-based co-transmission
Figure 4-2 shows TDM timeslot sharing on the Iub interface. By using the fractional ATM or
fractional IP function, UMTS data is transmitted on some E1 timeslots, and GSM data is
transmitted on the remaining E1 timeslots. In this scenario, the UMTS equipment provides the
timeslot cross-connection function. The OML of the GBTS cannot be carried on the co-

SingleRAN
transmission link on the backplane; the OML must be carried on an E1 cable that is connected
to the GBTS panel.
Figure 4-2 TDM timeslot sharing on the Iub interface
Figure 4-3 shows TDM timeslot sharing on the Abis interface. By using the fractional ATM
or fractional IP function, GSM data is transmitted on some E1 timeslots, and UMTS data is
transmitted on the remaining E1 timeslots. In this solution, the GSM equipment provides the
timeslot cross-connection function.
Figure 4-3 TDM timeslot sharing on the Abis interface
NOTE
If TDM-based co-transmission is used and the GBTS shares E1/T1 transmission resources with the
NodeB, it is recommended that the E1/T1 clock source be configured on the GBTS and the NodeB use
the E1/T1 clock source shared by the GBTS.
4.2 IP-based Co-Transmission

This section covers the following optional features:
l MRFD-121114 IP-Based Multi-mode Co-Transmission on BS side(GBTS)

l MRFD-121124 IP-Based Multi-mode Co-Transmission on BS side(NodeB)
l MRFD-121134 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)
l MRFD-121144 IP-Based Multi-mode Co-Transmission on BS side(LTE TDD)
l MRFD-121154 IP-Based Multi-mode Co-Transmission on BS side(NB-IoT)

SingleRAN
4.2.1 Overview
Introduction to Main Control Boards and UTRPs
Co-transmission ports can be provided by main control boards or universal transmission
processing units (UTRPs) of a multimode base station. Table 4-1 lists the main control boards
and UTRPs of a multimode base station. For the descriptions of transmission ports on these
boards, see BBU Hardware Description.
Table 4-1 Main control boards and UTRPs of a multimode base station
Board Type Board Supported Description
Name Radio System
Main control GTMU GSM There are three types of GTMU

board boards: GTMU, GTMUb, and
GTMUc. They all support co-
transmission through panel
interconnection, and only the
GTMUb and GTMUc support co-
transmission through backplane
interconnection.
WMPT UMTS In the case of co-transmission

through backplane interconnection,
any port on the WMPT cannot serve
as the co-transmission port.
LMPT LTE None
UMPT/ GSM/UMTS/LTE None

UMDU
UTRP UTRP2/ UMTS The UTRPs supported by the co-

UTRP3/ MPT multimode base station carry
UTRP4/ only UMTS services.
UTRP9/
UTRPa
UTRPb4 GSM This board supports only GSM

services.
UTRPc GSM/UMTS/LTE In a GBTS, the GTMUb can manage

the UTRPc whereas the GTMUc
cannot.
In an eGBTS, the GTMUb/GTMUc
cannot manage the UTRPc.
Co-Transmission Networking Scenarios

For co-transmission on the separate-MPT multimode base station side, it is recommended that
a board having higher processing capabilities provide the co-transmission port. If the boards
of different RATs have the same processing capabilities, it is recommended that inventory

SingleRAN
boards provide the co-transmission port. For IP-based co-transmission scenarios on the
multimode base station side, see 7 Engineering Guidelines.
NOTE
In the scenarios of separate-MPT multimode base station co-transmission through backplane

interconnection, the base station of a mode that does not provide the co-transmission port cannot be
connected to the transport network through a port on a board panel.
If co-transmission is achieved through backplane interconnection, a GTMUb/GTMUc board cannot
transmit or receive a packet whose size is larger than 1500 bytes, for example, ping packet detection of
over 1500 bytes cannot be performed on a GTMUb/GTMUc board.
4.2.2 Main-Control-Board-based Co-Transmission Through Panel

Interconnection of the Separate-MPT Multimode Base Station
For co-transmission on the separate-MPT GU multimode base station side (GTMU and
WMPT are used), the co-transmission port is provided by the eNodeB, NodeB, or GBTS/
eGBTS in descending order of priority. This section uses the separate-MPT GU/GL
multimode base station as an example to describe the main-control-board-based IP co-
transmission through panel interconnection.
Co-Transmission in IP over FE/GE Mode

In IP over FE/GE mode, the main control board of each mode is interconnected through FE
port interconnection, and the main control board of a mode provides an FE/GE port as the co-
transmission port to be connected to the IP transport network. Figure 4-4 and Figure 4-5
show the main-control-board-based co-transmission through panel interconnection on the
separate-MPT GU/GL multimode base station sides in IP over FE/GE mode.
Figure 4-4 Main-control-board-based co-transmission through panel interconnection on the

separate-MPT GU multimode base station side in IP over FE mode
As shown in Figure 4-4, the WMPT of the NodeB provides an FE port as the co-transmission
port, and the GTMU is connected to the WMPT through panel interconnection. In this case,
uplink data of the GBTS/eGBTS is transmitted from the GTMU to the WMPT and then to the
IP transport network, and downlink data to the GBTS/eGBTS is transmitted from the IP
transport network to the WMPT and then to the GTMU.

SingleRAN

separate-MPT GL multimode base station side in IP over FE/GE mode
As shown in Figure 4-5, the LMPT of the eNodeB provides an FE/GE port as the co-
transmission port, and the GTMU is connected to the LMPT through panel interconnection. In
this case, uplink data of the GBTS/eGBTS is transmitted from the GTMU to the LMPT and
then to the IP transport network, and downlink data to the GBTS/eGBTS is transmitted from
the IP transport network to the LMPT and then to the GTMU.
Co-Transmission in IP over E1/T1 Mode

In IP over E1/T1 mode, the main control board of each mode is interconnected through
FE/GE port interconnection, and the main control board of a mode provides an E1/T1 port as
the co-transmission port to be connected to the IP transport network.

separate-MPT GU multimode base station side in IP over E1/T1 mode
As shown in Figure 4-6, the WMPT of the NodeB provides an E1/T1 port as the co-
transmission port, and the GTMU is connected to the WMPT through panel interconnection.
The WMPT uses MLPPP to bind E1 links. In this case, uplink data of the GBTS/eGBTS is
transmitted from the GTMU to the WMPT and then to the IP transport network, and downlink
data to the GBTS/eGBTS is transmitted from the IP transport network to the WMPT and then
to the GTMU.

SingleRAN
4.2.3 UTRP-based Co-Transmission Through Panel

Interconnection on the Separate-MPT Multimode Base Station
Side
This section uses the separate-MPT GU multimode base station as an example to describe the
UTRP2-based co-transmission through panel interconnection in IP over FE/GE mode. Figure
4-7 shows the UTRP2-based co-transmission through panel interconnection on the separate-
MPT GU multimode base station side in IP over FE/GE mode.
Figure 4-7 UTRP2-based co-transmission through panel interconnection on the separate-MPT

GU multimode base station side in IP over FE/GE mode
As shown in Figure 4-7, the UTRP2 managed by the NodeB provides an FE/GE port as the
co-transmission port, and the GTMU is connected to the UTRP2 through panel
interconnection. In this case, uplink data of the GBTS/eGBTS is transmitted from the GTMU
to the UTRP2, and downlink data to the GBTS/eGBTS is transmitted from the UTRP2 to the
GTMU.

This section uses the separate-MPT GU multimode base station as an example to describe the
UTRP4-based co-transmission through panel interconnection in IP over E1/T1 mode. Figure
4-8 shows the UTRP4-based co-transmission through panel interconnection on the separate-
MPT GU multimode base station side in IP over E1/T1 mode.
Figure 4-8 UTRP4-based co-transmission through panel interconnection on the separate-MPT

GU multimode base station side in IP over E1/T1 mode
As shown in Figure 4-8, the UTRP4 provides an E1/T1 port as the co-transmission port, and
the GTMU is connected to the WMPT through panel interconnection. The UTRP4 uses
MLPPP to bind E1 timeslots. In this case, uplink data of the GBTS is transmitted from the

SingleRAN
GTMU to the WMPT, then to the UTRP4, and downlink data to the GBTS is transmitted from
the UTRP4 to the WMPT, then to the GTMU.
4.2.4 Main-Control-Board-based Co-Transmission Through

Backplane Interconnection on the Separate-MPT Multimode Base
Station Side
Main-control-board-based co-transmission through backplane interconnection is supported by
separate-MPT multimode base stations. In this co-transmission mode, the main control boards
of the separate-MPT multimode base station must be configured as described in Table 4-2.
Table 4-2 Main control board configuration of a separate-MPT multimode base station
Separate-MPT Main Control Board Board Recommended to Provide
Multimode Configuration a Co-Transmission Port
Base Station
GU GTMUb/GTMUc+UMPT_U UMPT_U
GL/GT/GM GTMUb/GTMUc+UMPT_L/ UMPT_L/UMPT_T//LMPT/

UMPT_T//LMPT/UMPT_M UMPT_M
UL/UT/UM WMPT+LMPT LMPT
WMPT+UMPT_L/UMPT_T/ UMPT_L/UMPT_T/UMPT_M
UMPT_M
UMPT_U+UMPT_L/ UMPT_U or UMPT_L/UMPT_T/

UMPT_T/UMPT_M UMPT_M
UMPT_U+LMPT UMPT_U
GU+L/GU GTMUb/GTMUc+UMPT_U UMPT_U or UMPT_L/UMPT_T/

+T/GU+M +UMPT_L/UMPT_T/ UMPT_M
UMPT_M
GTMUb/GTMUc+WMPT UMPT_L/UMPT_T/UMPT_M
+UMPT_L/UMPT_T/
UMPT_M
GL/GT/GM+U GTMUb/GTMUc+UMPT_L/ UMPT_L/UMPT_T/UMPT_M

UMPT_T/UMPT_M
+UMPT_U
GTMUb/GTMUc+LMPT UMPT_U
+UMPT_U
Figure 4-9 uses the separate-MPT GL multimode base station as an example to show the
main-control-board-based co-transmission through backplane interconnection between the
GTMUb and the LMPT/UMPT_L.

SingleRAN
Figure 4-9 Main-control-board-based co-transmission through backplane interconnection on

the separate-MPT GL multimode base station side
As shown in Figure 4-9, the GTMUb and the LMPT/UMPT_L communicate with each other
through the backplane. In this case, uplink data of the GBTS/eGBTS is transmitted from the
GTMUb to the LMPT/UMPT_L and then to the IP transport network, and downlink data to
the GBTS/eGBTS is transmitted from the IP transport network to the LMPT/UMPT_L and
then to the GTMUb.
NOTE
When the main control boards of different modes communicate through the backplane, each main
control board must be configured with a tunnel to the peer main control board. Each tunnel is managed
only by the mode of the main control board on which the tunnel is configured, and is uniquely numbered
within the corresponding mode. Tunnels of different modes can have the same number. The following
parameters specify the tunnel IDs of different modes:
GBTS: BTSTUNNEL.TN(BSC6900,BSC6910)
eGBTS/NodeB/eNodeB: TUNNEL.TUNNELID
When a separate-MPT GUL/GUT multimode base station uses main-control-board-based IP

co-transmission through backplane interconnection, two BBUs must be configured. Figure
4-10 uses a separate-MPT GUL multimode base station (two BBUs in the separate-MPT
multimode base station are interconnected in UMPT+UMPT interconnection mode) as an
example to show the main-control-board-based IP co-transmission through backplane
interconnection.

SingleRAN
Figure 4-10 Main-control-board-based IP co-transmission through backplane interconnection

on the separate-MPT UG+L multimode base station side
NOTE
When two BBUs are interconnected in UMPT+UMPT interconnection mode, the root BBU must
provide the co-transmission port.
4.2.5 UTRPc-based Co-Transmission Through Backplane

Interconnection on the Separate-MPT Multimode Base Station
Side
When a UTRPc is used for co-transmission, the UTRPc forwards data for multiple modes but
is managed by only one mode. The management includes software management, hardware
management, and configuration management. The mode that manages the UTRPc is called
the managing mode, and other modes are called non-managing modes. If a multi-mode base
station has more than one BBU, the UTRPc must be managed by the main control board that
is located in the same BBU with the UTRPc. In a newly deployed site, it is recommended that
UMTS be preferentially used as the managing mode, then LTE and GSM. In the scenarios of
network reconstruction for co-transmission, select the managing mode that has minimum
impact on the services in the live network.
Figure 4-11 shows the UTRPc-based co-transmission through backplane interconnection on
the GU/UL multimode base station side as an example.

SingleRAN
Figure 4-11 UTRPc-based co-transmission through backplane interconnection on the

separate-MPT GU/UL multimode base station side
As shown in Figure 4-11, the UTRPc provides an FE/GE port as the co-transmission port.
The main control board of each mode communicates with the UTRPc through the backplane.
The data of the managing mode is transmitted directly between the baseband board and the
UTRPc. The data of the non-managing mode is transmitted between the baseband board and
the UTRPc through the main control board of the non-managing mode.
NOTE
When the main control board of the non-managing mode communicates with the UTRPc through the
backplane, both the main control board and the UTRPc must be configured with a tunnel to each other.
Use the network structure in Figure 4-11 as an example and assume that mode 1 is the managing mode.
The UTRPc must be configured with a tunnel to the main control board of mode 2, and the main control
board of mode 2 must be configured with a tunnel to the UTRPc.
In the UTRPc-based co-transmission through backplane interconnection on the separate-MPT

GUL/GUT/GUM multimode base station side, two BBUs are required and they must be
connected through a Universal Cascading Interface Unit (UCIU). Figure 4-12 shows the
UTRPc-based co-transmission through backplane interconnection on the separate-MPT GUL
multimode base station side as an example.

SingleRAN
Figure 4-12 UTRPc-based co-transmission through backplane interconnection on the

separate-MPT GUL multimode base station side
As shown in Figure 4-12, the UTRPc provides the co-transmission port and the main control
board of mode 3 is connected to the UCIU through the CI optical ports. The UCIU is
managed by mode 1 or mode 2 that is in the same BBU of the UCIU. It is recommended that
GSM be preferentially used as the managing mode of the UCIU, then UMTS, and the last
LTE. Service data of mode 1 and mode 2 is directly transmitted between the UTRPc and the
service board of each mode. Service data of mode 3 is transmitted between the UTRPc and
the UMPT through the UCIU.
NOTE
During the software upgrade, cold patch installation, or main control board replacement of the managing
mode, the UTRPc is reset and ongoing services on all modes are interrupted.
If the main control boards of the managing and non-managing modes are installed in the same BBU,
resetting the main control board of the managing mode does not affect ongoing services of non-
managing modes. If the main control boards of the managing and non-managing modes are installed in
different BBUs, resetting the main control board of the managing mode affects ongoing services of non-
managing modes.
During hot patch installation on the main control board of the managing mode, services on other modes
are not affected.
The UTRPc is invisible to the non-managing modes. The software upgrade, cold patch installation, or
main control board replacement of the non-managing mode does not affect the UTRPc. Therefore,
ongoing services on other modes are not affected.
It is recommended that the UCIU be preferentially installed in slot 4. If slot 4 is occupied by another
board, slot 0 is recommended for the UCIU.

SingleRAN
4.2.6 Co-Transmission on the Co-MPT Multimode Base Station

Side
Co-Transmission in IP over FE/GE/10GE Mode

In IP over FE/GE/10GE mode, the UMPT board of a co-MPT multimode base station
provides an FE/GE/10GE port as the co-transmission port, or the UMDU/UTRPc board of a
co-MPT multimode base station provides an FE/GE port as the co-transmission port. Figure
4-13, Figure 4-14, and Figure 4-15 use a co-MPT GUL multimode base station as an
example to show the co-transmission on the co-MPT multimode base station side in IP over
FE/GE mode.
NOTE
The BBU3910A is an outdoor BBU, which integrates main control, transmission, and baseband
processing. The BBU3910A does not support UTRP boards.
Figure 4-13 Co-transmission on the co-MPT GUL multimode base station side in IP over
FE/GE/10GE mode (UMPT provides the co-transmission port)
FE/GE mode (UMDU provides the co-transmission port)

SingleRAN
FE/GE mode (UTRPc provides the co-transmission port)
NOTE
If the co-transmission on the co-MPT GUL multimode base station side is in IP over FE/GE/10GE
mode, multiple modes use the same OM IP address but different service IP addresses.

In IP over E1/T1 mode, the UMPT_GU or UMDU_GU board of a co-MPT GU multimode
base station provides an E1/T1 port as the co-transmission port. Figure 4-16 and Figure 4-17
show the co-transmission on the co-MPT GU multimode base station side in IP over E1/T1
mode.
Figure 4-16 Co-transmission on the co-MPT GU multimode base station side in IP over
E1/T1 mode (the UMPT provides the co-transmission port)
Figure 4-17 Co-transmission on the co-MPT GU multimode base station side in IP over
E1/T1 mode (the UMDU provides the co-transmission port)

SingleRAN
Common Transmission Feature Parameter Description 5 Related Features
5 Related Features
5.1 MRFD-121101 IP-Based BSC and RNC Co-

Prerequisite Features
Feature ID Feature Name Description
GBFD-118603 Gb over IP GSM: This feature is required when the

Co-Transmission is applied on the Gb
interface.
GBFD-118601 Abis over IP GSM: This feature is required when the

Co-Transmission in FE/GE mode is
applied on the Abis interface.
GBFD-118611 Abis IP over E1/T1 GSM: This feature is required when the
Co-Transmission in IP over E1/T1
mode is applied on the Abis interface.
GBFD-118602 A over IP GSM: This feature is required when the

Co-Transmission in FE/GE mode is
applied on the A interface.
GBFD-118622 A IP over E1/T1 GSM: This feature is required when the

Co-Transmission in IP over E1/T1
mode is applied on the A interface.
WRFD-050402 IP Transmission UMTS: This feature is required when

Introduction on Iub the Co-Transmission is applied on the
Interface Iub interface.
WRFD-050409 IP Transmission UMTS: This feature is required when

Introduction on Iu the Co-Transmission is applied on the
Interface Iu interface.

SingleRAN
Mutually Exclusive Features

None
Impacted Features
None
5.2 MRFD-120111 TDM-Based Multi-mode Co-

Transmission via Backplane on BS side(GBTS)
None

None
Impacted Features
None
5.3 MRFD-120121 TDM-Based Multi-mode Co-

Transmission via Backplane on BS side(NodeB)
None

None
Impacted Features
None
5.4 MRFD-121114 IP-Based Multi-mode Co-Transmission

on BS side(GBTS)
GBFD-118601 Abis over IP N/A

SingleRAN

None
Impacted Features
None

on BS side(NodeB)
WRFD-050402 IP Transmission When the Co-Transmission in FE/GE

Introduction on Iub mode is applied on the Iub interface.
Interface
WRFD-050302 Fractional ATM Function When the Co-Transmission in ATM

on Iub Interface mode is applied on the Iub interface.
WRFD-050411 Fractional IP Function on When the Co-Transmission in IP over

Iub Interface E1/T1 mode is applied on the Iub
interface.

None
Impacted Features
None

on BS side(eNodeB)
None

None
Impacted Features
None

SingleRAN

on BS side(LTE TDD)
None

TDLOFD-001134 Virtual Routing and Forwarding N/A
Impacted Features
None

on BS side(NB-IoT)
None

None
Impacted Features
None

SingleRAN
Common Transmission Feature Parameter Description 6 Network Impact
6 Network Impact
System Capacity
No impact.
Network Performance
No impact.

SingleRAN
Common Transmission Feature Parameter Description 7 Engineering Guidelines
7 Engineering Guidelines
In this chapter, the first letter in the name of a separate-MPT multimode base station indicates
which base station provides the co-transmission port. For example:
l A UG multimode base station indicates that the NodeB provides the co-transmission
port.
l A UG+L multimode base station indicates that the NodeB provides the co-transmission
port, the NodeB and the GBTS/eGBTS share one BBU, and the eNodeB uses an
independent BBU.
This chapter uses LTE FDD as an example to describe engineering guidelines. The
engineering guidelines for LTE TDD and LTE NB-IoT are the same as those for LTE FDD.
The scenarios in which co-MPT base stations use the UMDU board are similar to the
scenarios in which co-MPT base stations use the UMPT board. Unless otherwise specified,
the UMPT board is used as an example for description, and the UMDU board is not described
separately.

SingleRAN
7.1 When to Use

It is recommended that co-transmission for the Iub and Abis interfaces in IP over FE/GE
mode be enabled on the MBSC side if a BSC is reconstructed from single-mode to
multimode. This section describes the engineering guidelines for IP-based co-transmission for
Iub and Abis interfaces on the MBSC side.
It is recommended that co-transmission be enabled in IP over FE/GE mode during the

evolution of an IP-based base station from single-mode to multimode or from dual-mode to
triple-mode.
It is recommended that TDM-based co-transmission be enabled on separate-MPT GU MBTSs

when TDM is used for the transport network.
7.2 Required Information

None
7.3 Planning
RF Planning
N/A
Network Planning
l Determine the RAT that provides the co-transmission port. Due to differences in
transmission specifications among RATs used in a multimode base station, it is
recommended that the RAT that provides the co-transmission port be determined based
on the RAT priorities in descending order as follows: LTE > UMTS > GSM.
l Determine whether to use panel interconnection or backplane interconnection between
RATs for co-transmission.
l Determine the transmission bandwidth. It is recommended that transmission bandwidth
for each RAT be determined based on the actual traffic model.
l Plan transmission parameters, including IP addresses, routes (network segment routes or
host routes), virtual local area networks (VLANs), SCTP links, IP paths, and Dynamic
Host Configuration Protocol (DHCP). The detailed parameter plan can be provided by
Huawei.
Hardware Planning
l When main-control-board-based co-transmission is implemented through panel
interconnection, only the panel interconnection cable is required, and no additional board
is required.
l A UTRPc is required when UTRPc-based co-transmission is implemented through
backplane interconnection.
l For co-transmission on a triple-mode base station, UCIU+UMPT interconnection or
UMPT+UMPT interconnection can be used to connect two BBUs.

SingleRAN
For details about the slots available for new boards, see BBU Hardware Description in the
3900 Series Base Station Product Documentation. This document only provides example slots
in which boards are installed.
7.4 Co-Transmission for Iub and Abis Interfaces on the

MBSC Side
7.4.1 Requirements
l Deployment objective
One FE/GE or E1/T1 port on an interface board of the MBSC is connected to both the
GBTS/eGBTS and the NodeB. When co-transmission is enabled for the Iub and Abis
interfaces on the MBSC side, co-transmission is optional for the GBTS/eGBTS and the
NodeB.
Figure 7-1 shows the network topology of co-transmission for the Iub and Abis
interfaces on the MBSC side in FE/GE mode.
Figure 7-1 Network topology of co-transmission for the Iub and Abis interfaces on the
MBSC side in FE/GE mode
Figure 7-2 shows the network topology of co-transmission for the Iub and Abis
interfaces on the MBSC side in end-to-end E1/T1 over STM-1/OC-3 mode.

SingleRAN
Figure 7-2 Network topology of co-transmission on the Iub and Abis interfaces on the
MBSC side in end-to-end E1/T1 over STM-1/OC-3 mode
l Requirement for other features

The following features have been enabled:
GBFD-118601 Abis over IP
WRFD-050402 IP Transmission Introduction on Iub Interface
l Requirements for the license
This function is not under license control.
7.4.2 Data Preparation

This section describes the data to be prepared for co-transmission for the Iub and Abis
interfaces on the MBSC side in IP over FE/GE and IP over E1/T1 modes.
Co-Transmission for the Iub and Abis Interfaces on the MBSC Side in IP over
FE/GE Mode
Figure 7-3 shows an example of network topology for co-transmission for the Iub and Abis
interfaces on the MBSC side in IP over FE/GE mode.

SingleRAN
Figure 7-3 Example of network topology for co-transmission for the Iub and Abis interfaces
on the MBSC side in IP over FE/GE mode
NOTE
The port IP address of the Abis/Iub co-transmission interface board on the MBSC side must be on the
same network segment as the port IP address of the next-hop router in FE/GE mode. If the MBSC is
directly connected to a GBTS/eGBTS or NodeB, the port IP address of the Abis/Iub co-transmission
interface board must be on the same network segment as the port IP address of the GBTS/eGBTS or
NodeB.
Data configurations at the physical layer, such as the duplex mode and rate in FE/GE mode, must be
consistent between the MBSC and the next-hop port.
Table 7-1 describes the IP address plan for the MBSC, GBTS/eGBTS, and NodeB.

SingleRAN
Table 7-1 IP address plan

Item Instance Remarks
Device IP address of the 10.10.10.10/32 Logical IP addresses of the

MBSC Iub and Abis interface
boards on the MBSC side.
The logical IP address of the
Iub interface board on the
RNC side and the logical IP
address of the Abis interface
board on the BSC side must
be configured on the same
board. This table assumes
that the logical IP address of
the Iub interface board on
the RNC side is the same as
that of the Abis interface
board on the BSC side.
Port IP address of the 10.21.21.1/24 Physical IP addresses of the

boards on the MBSC side.
The physical IP address of
the Iub interface board on
the RNC side and the
physical IP address of the
Abis interface board on the
BSC side must be
configured on the same port
of the same board. This
table assumes that the
physical IP address of the
Iub interface board on the
RNC side is the same as that
of the Abis interface board
on the BSC side.
IP address of the port on the 10.21.21.254/24 -

router that is directly
connected to the MBSC
Port IP address of the 10.30.30.11/24 -

NodeB

GBTS/eGBTS
Port IP address of the router 10.30.30.12/24 -

that is directly connected to
the NodeB

SingleRAN

router that is directly
connected to the GBTS/
eGBTS
Co-Transmission for the Iub and Abis Interfaces on the MBSC Side in IP over
E1/T1 Mode
Figure 7-4 shows an example of network topology for co-transmission for the Iub and Abis
interfaces on the MBSC side in IP over E1/T1 mode.
Figure 7-4 Example of network topology for co-transmission for the Iub and Abis interfaces
on the MBSC side in IP over E1/T1 mode
Table 7-2 describes the IP address plan for the MBSC, GBTS/eGBTS, and NodeB.
Device IP address of the 10.10.10.10/32 Logical IP addresses of the

boards on the MBSC side

SingleRAN
Port IP address of the 10.21.21.1/24 Physical IP addresses of the

boards on the MBSC side
Port IP address of the 10.21.21.11/24 The MBSC terminates

NodeB messages that are compliant
with the Point-to-Point
Port IP address of the 10.21.21.188/24 Protocol (PPP)/Multi-Link
GBTS/eGBTS Point-to-Point Protocol
(MLPPP) from the NodeB
or GBTS/eGBTS.
Therefore, the port IP
addresses of the MBSC,
NodeB, and GBTS/eGBTS
must be on the same
network segment.
7.4.3 Precautions
None
7.4.4 Hardware Adjustment

No additional hardware is required. You only need to connect the FE/GE or E1/T1 port on the
Abis/Iub interface board to the intermediate transmission equipment. When co-transmission
in IP over FE/GE mode is used, connect the FE/GE port on the Abis/Iub interface board to the
next-hop router. When co-transmission in IP over E1/T1 mode is used, connect the Abis/Iub
interface board to the intermediate synchronous digital hierarchy (SDH)/plesiochronous
digital hierarchy (PDH) transmission equipment.
7.4.5 Initial Configuration

For details about data configurations at the data link layer and network layer on the BSC side,
see "Configuring a BTS and Its Cells" > "Configuring the Transmission Data" in BSC6900
GU Initial Configuration Guide of the BSC6900 GU Product Documentation or BSC6910 GU
Initial Configuration Guide of the BSC6910 GU Product Documentation.
For details about data configurations at the data link layer and network layer on the RNC side,
see "Configuring the UMTS Interfaces" > "Configuring the Iub Interface (over IP)" in
BSC6900 GU Initial Configuration Guide in the BSC6900 GU Product Documentation CD-
ROM. Compared with independent transmission, co-transmission has no configuration
change. Only the following information needs to be noted: The physical IP addresses of the
BSC and the RNC must be configured on the same port of the same board. The logical IP
addresses of the Abis and Iub interfaces for the BSC and RNC must be configured on the
same board. According to the data plan, port IP addresses or device IP addresses of the BSC
and RNC can be the same or different.

SingleRAN
7.4.6 Activation Observation

Step 1 Run the MBSC MML command PING IP to ping the port IP address of the GBTS/eGBTS or
NodeB. If the port IP address can be pinged, the transmission link between the MBSC and the
GBTS/eGBTS/NodeB is normal.
PING IP: SIPADDR="10.10.10.10", DESTIP="10.30.30.11", CONTPING=NO;
PING IP: SIPADDR="10.10.10.10", DESTIP=""10.20.20.188" CONTPING=NO;
----End

Step 1 Run the MBSC MML command PING IP to ping the port IP address of the GBTS/eGBTS or
NodeB. If the port IP address can be pinged, the transmission link between the MBSC and the
GBTS/eGBTS/NodeB is normal.
----End
7.5 Main-Control-Board-based Co-Transmission Through

Panel Interconnection on the Separate-MPT UG
Multimode Base Station Side in IP over FE/GE Mode
In this scenario, if the GSM base station is a GBTS, the main control board must be a GTMU/
GTMUb/GTMUc; if the GSM base station is an eGBTS, the main control board must be a
GTMUb/GTMUc. This section uses a GTMU as an example to describe the engineering
guidelines.
7.5.1 Requirements
Figure 7-5 shows the main-control-board-based IP co-transmission through panel
interconnection on the separate-MPT UG multimode base station side. In this scenario,
an outbound FE port on the WMPT of the NodeB serves as the co-transmission port of
the UG multimode base station and is connected to the MBSC. The GTMU of the
GBTS/eGBTS is connected to the WMPT of the NodeB through FE ports.

SingleRAN
Figure 7-5 Main-control-board-based IP co-transmission through panel interconnection

on the separate-MPT UG multimode base station side

– GBFD-118601 Abis over IP
– WRFD-050402 IP Transmission Introduction on Iub Interface
The license is not required.

(Example) Key Data Preparation
Figure 7-6 shows an example of network topology for main-control-board-based IP co-
transmission through panel interconnection on the separate-MPT UG multimode base station
side.
Figure 7-6 Example of network topology for main-control-board-based IP co-transmission

through panel interconnection on the separate-MPT UG multimode base station side
Table 7-3 describes the IP address plan.

SingleRAN

Device IP address of the 10.10.10.10/32 -

BSC
Port IP address of the BSC 10.21.21.1/24 -

RNC
Port IP address of the RNC 10.23.23.1/24 -

router that is connected to
the BSC

the RNC
IP address of FE port 1 on 10.30.30.1/24 UMTS: device IP address

the NodeB (FE port 1 is during configuration on the
used for interconnecting the CME
NodeB to the GBTS/
eGBTS.)

the NodeB during configuration on the
CME

the NodeB
IP address of FE port 0 on 10.30.30.188/24 GSM: device IP address

the GBTS/eGBTS (FE port during configuration on the
0 is used for interconnecting CME
the GBTS/eGBTS to the
NodeB.)
NOTE
IP addresses of two ports used for interconnecting the NodeB to the GBTS/eGBTS must be on the same
network segment.
Data configurations at the physical layer, such as the duplex mode and rate, must be consistent between
the two ports used for interconnecting the NodeB to the GBTS/eGBTS.
7.5.3 Precautions
None

SingleRAN

When main-control-board-based co-transmission is implemented through panel
interconnection, no additional hardware is required, but the cables between main control
board panels are required. Table 7-4 describes the panel interconnection modes.
Table 7-4 Main control board panel interconnection modes

Base Station Mode Panel Interconnection Mode
UG Mode 1: An outbound electrical port on the WMPT is connected to

the MBSC, and an outbound optical port on the WMPT is
connected to an optical port on the GTMU.
Mode 2: An outbound optical port on the WMPT is connected to

the MBSC, and an outbound electrical port on the WMPT is
connected to an electrical port on the GTMU.
Initial Configuration on the GSM Side (GBTS and BSC)

For details about data configurations at the data link layer and transport layer, see 3900 Series
Base Station Initial Configuration Guide of the 3900 Series Base Station Product
Documentation. In addition to the configuration steps described in 3900 Series Base Station
Initial Configuration Guide, perform the following steps:
l Using MML commands
Step 1 To configure a route from the GBTS to the BSC, change the next-hop address of the route
from the IP address of the directly connected router to the IP address of the interconnection
port on the WMPT. The BSC MML command for configuring the route from the GBTS to the
BSC is ADD BTSIPRT.
Step 2 (Optional) Configure two routes to the DHCP relay of the GBTS on the BSC side. In this
step, set the destination IP address of one route to the O&M channel IP address and that of the
other route to the lower-level transmission port. The BSC MML command for configuring the
route to the DHCP relay of the GBTS is ADD IPRT.
----End
l Using the CME to perform single configuration
On the CME, set the parameters based on the data plan listed in the 7.5.2 Data
Preparation section. For instructions on how to perform the CME single configuration,
see CME Single Configuration Operation Guide.
Initial Configuration on the GSM Side (eGBTS and BSC)


SingleRAN
Step 1 When configuring a route from the eGBTS to the BSC, change the next-hop address of the
route from the IP address of the directly connected router to the IP address of the
interconnection port on the WMPT. The eGBTS MML command for configuring the route
from the eGBTS to the BSC is ADD IPRT.
Step 2 (Optional) Configure two routes to the DHCP relay of the eGBTS on the BSC side. In this
step, set the destination IP address of one route to the OM channel IP address and that of the
route to the DHCP relay of the eGBTS is ADD IPRT.
----End
On the CME, set the parameters based on the data plan listed in the 7.5.2 Data Preparation
section. For instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.
Initial Configuration on the UMTS Side

Step 1 Run the NodeB MML command SET ETHPORT to set the attributes of the Ethernet port on
the WMPT that is used for interconnecting to the GTMU.
SET ETHPORT: SN=7, SBT=BASE_BOARD, PN=0, PA=COPPER, SPEED=AUTO, DUPLEX=AUTO;
//Set the parameters for the Ethernet port (port 0 on board in slot 7) that is
used for interconnecting the WMPT to the GTMU.
Step 2 Run the NodeB MML command ADD DEVIP to set the device IP address of the Ethernet
port on the WMPT that is used for interconnecting to the GTMU. In this step, ensure that IP
addresses of two ports used for interconnecting the NodeB to the GBTS/eGBTS are on the
same network segment.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="10.30.30.1",
MASK="255.255.255.0";
//Set the IP address of the Ethernet port (port 0 on board in slot 7) that is
used for interconnecting the WMPT to the GTMU and ensure that the IP address is
on the same network segment as the IP address of the interconnection port on the
GTMU.
Step 3 Run the NodeB MML command ADD IPRT to add an uplink route from the GBTS/eGBTS
to the BSC through the NodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP to
the IP address of the router that is directly connected to the NodeB.
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="10.20.20.1", PREF=60;
Step 4 (Optional) Add a downlink route from the BSC to the GBTS/eGBTS through the NodeB.
The downlink route is required only if the logical IP address is used by the GBTS/eGBTS. If
the physical port IP address is used by the GBTS/eGBTS and the IP addresses of the panel
interconnection ports on the NodeB and the GBTS/eGBTS are on the same network segment
as the port IP address of the GBTS/eGBTS, the downlink route from the NodeB to the GBTS/
eGBTS is not required.

SingleRAN
Step 5 (Optional) Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
When co-transmission is enabled for the GBTS/eGBTS and NodeB, if the GBTS/eGBTS is
deployed using DHCP, the NodeB needs to work as the relay. Therefore, DHCP relay needs to
be enabled for the NodeB.
SET DHCPRELAYSWITCH: ES=ENABLE;
//Enable DHCP relay for the NodeB.
Step 6 (Optional) Run the NodeB MML command ADD DHCPSVRIP to add the IP address of the
DHCP server.
deployed using DHCP, the NodeB needs to work as the relay. Therefore, the IP address of the
DHCP server needs to be added on the NodeB. For the GBTS, the IP address of the DHCP
server is the IP address of the BSC. For the eGBTS, the IP address of the DHCP server is the
IP address of the U2000.
ADD DHCPSVRIP: DHCPSVRIP="10.10.10.10";
//Add the IP address of the DHCP server for the GBTS.
//Add the IP address of the DHCP server for the eGBTS.
Step 7 (Optional) Configure VLAN. There are two methods of configuring differentiated VLAN data
for the GBTS/eGBTS and NodeB:
l Method 1 (Recommended): Configure differentiated next-hop addresses. Specifically,
the uplink route from the GBTS/eGBTS to the BSC through the NodeB added in step 2
must be different from the uplink route for the NodeB. For example, you need to add a
port IP address (for example, 10.20.20.100) to the NodeB port connecting to the BSC so
that the data from the GBTS/eGBTS can be transmitted through different routes. In
addition, you need to configure a different next-hop address for the uplink route from the
GBTS/eGBTS to the BSC through the NodeB, for example, you can set the next-hop
address of the uplink route from the GBTS/eGBTS to the BSC through the NodeB to
10.20.20.101, which is different from the next-hop address (10.20.20.1) of the uplink
route for the NodeB. To add VLAN mapping, run the MML command ADD
VLANMAP.
ADD VLANMAP: NEXTHOPIP="10.20.20.101", MASK=255.255.255.255, VLANMODE=
SINGLEVLAN, VLANID=22, SETPRIO=DISABLE;
l Method 2 (not recommended): Configure differentiated services code point (DSCP)

values. This method requires differentiated DSCP values for the GBTS/eGBTS and
NodeB. For details about DSCP values for the GBTS/eGBTS and NodeB, see
Bandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter
Description for SingleRAN.
1. Run the NodeB MML command ADD VLANCLASS.
ADD VLANCLASS: VLANGROUPNO=1, TRAFFIC=USERDATA, SRVPRIO=40, VLANID=22;
//Set VLANID to 22 for the data flow with SRVPRIO set to 40. In VLAN group
mode, set TRAFFIC to USERDATA for all passerby flows through the NodeB. If
differentiated data needs to be configured for the NodeB and GBTS/eGBTS and
TRAFFIC is set to USERDATA, SRVPRIO cannot be set to 40 on the NodeB.
//Set VLANID to 22 for the data flow with SRVPRIO set to 0. The DSCP value in
DHCP packets is fixed at 0. If DHCP relay is enabled on the network where
VLAN data is configured, set the DSCP value to 0 for VLAN. If the DSCP value
is not set to 0, DHCP packets sent to the DHCP server do not contain the VLAN
field. In addition, set TRAFFIC to USERDATA.
2. Run the NodeB MML command ADD VLANMAP.

SingleRAN

VLANGROUP, VLANGROUPNO=1, SETPRIO=DISABLE;
//Configure the mapping between a VLAN group and the next hop.
----End

After co-transmission is enabled on the multimode base station side, check whether the
feature is enabled by verifying the status of the IP link between the multimode base station
and the peer device.
UMTS Side
After the configuration file is delivered to the NodeB and activated, perform the following
step on the NodeB side to verify whether the transmission link between the NodeB and the
BSC/RNC is normal:
Step 1 Run the NodeB MML command PING to check the connectivity of the IP link between the
NodeB and the BSC/RNC. If the IP address can be pinged, the IP link is normal.
PING: CN=0, SRN=0, SN=7, SRCIP="10.20.20.188", DSTIP="10.10.10.10",
CONTPING=DISABLE, APPTIF=NO;
----End
GSM Side
After the configuration file is delivered to the GBTS/eGBTS and activated, perform the
following step on the BSC side to check whether the transmission link between the BSC and
the GBTS/eGBTS is normal:
Step 1 Run the BSC MML command PING IP to check the connectivity of the IP link between the
GTMU on the GBTS/eGBTS and the BSC. If the IP address can be pinged, the IP link is
normal.
PING IP: SIPADDR="10.10.10.10", DESTIP="10.30.30.188", NEXTHOP="10.21.21.254",
CONTPING=NO;
----End

Panel Interconnection on the Separate-MPT LG/TG/MG
guidelines.

SingleRAN
7.6.1 Requirements
interconnection on the separate-MPT LG multimode base station side. In this scenario,
an outbound FE/GE port on the LMPT of the eNodeB serves as the co-transmission port
of the separate-MPT LG multimode base station and is connected to the BSC and
MME/S-GW. The GBTS/eGBTS is interconnected to the eNodeB through FE ports.

on the separate-MPT LG multimode base station side

The following feature has been enabled:

transmission through panel interconnection on the separate-MPT LG multimode base station
side.

SingleRAN

through panel interconnection on the separate-MPT LG multimode base station side


BSC

the BSC

the eNodeB
IP address of FE port 1 on 10.30.30.1/24 LTE: device IP address

the eNodeB (FE port 1 is during configuration on the
eNodeB to the GBTS/
eGBTS.)

the eNodeB during configuration on the
CME
IP address of the MME 10.40.40.40/24 LTE: peer IP address for the

SCTP link
IP address of the S-GW 10.50.50.50/24 LTE: peer IP address for the

IP path

SingleRAN
IP address of FE port 0 on 10.30.30.188/24 -

the GBTS/eGBTS (FE port
0 is used for interconnecting
eNodeB.)
NOTE
IP addresses of two Ethernet ports used for interconnecting the eNodeB to the GBTS/eGBTS must be on
the same network segment.
Data configurations at the data link layer, such as the duplex mode and rate, must be consistent between
the two Ethernet ports used for interconnecting the eNodeB to the GBTS/eGBTS.
7.6.3 Precautions
None

interconnection, no additional hardware is required, but electrical or optical ports on main
control board panels must be interconnected. Table 7-6 describes the panel interconnection
modes.
Table 7-6 Panel interconnection modes

Base Station Panel Interconnection Mode
Mode
LG Mode 1: An outbound electrical port on the LMPT is connected to the

BSC and MME/S-GW, and an outbound optical port on the LMPT is
Mode 2: An outbound optical port on the LMPT is connected to the BSC

and MME/S-GW, and an outbound electrical port on the LMPT is
Mode 3: An outbound electrical port on the LMPT is connected to the

BSC and MME/S-GW, and an outbound electrical port on the LMPT is
Mode 4: An outbound optical port on the LMPT is connected to the BSC

and MME/S-GW, and an outbound optical port on the LMPT is

SingleRAN

l Using MML Commands
Step 1 When configuring a route from the GBTS to the BSC, change the next-hop address of the
interconnection port on the LMPT. The BSC MML command for configuring the route from
the GBTS to the BSC is ADD BTSIPRT.
step, set the destination IP address of one route to the OM channel IP address of the eNodeB
and that of the other route to the lower-level transmission port of the eNodeB. The BSC MML
command for configuring the route to the DHCP relay of the GBTS is ADD IPRT.
----End
l Using the CME to Perform Single Configuration


interconnection port on the LMPT. The eGBTS MML command for configuring the route
----End


SingleRAN
Initial Configuration on the LTE Side

Step 1 Run the eNodeB MML command SET ETHPORT to set the attributes of the Ethernet port
on the LMPT that is used for interconnecting to the GTMU.
used for interconnecting the LMPT to the GTMU.
Step 2 Run the eNodeB MML command ADD DEVIP to set the device IP address of the Ethernet
port on the LMPT that is used for interconnecting to the GTMU. In this step, ensure that IP
addresses of two ports used for interconnecting the eNodeB to the GBTS/eGBTS are on the
MASK="255.255.255.0";
used for interconnecting the LMPT to the GTMU and ensure that the IP address is
on the same network segment as the port IP address of the GTMU.
Step 3 Run the eNodeB MML command ADD IPRT to add an uplink route from the GBTS/eGBTS
to the BSC through the eNodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP to
the IP address of the router that is directly connected to the eNodeB.
//Add an uplink route from the GBTS/eGBTS to the BSC through the eNodeB.
Step 4 (Optional) Add a downlink route from the BSC to the GBTS/eGBTS through the eNodeB.
interconnection ports on the eNodeB and the GBTS/eGBTS are on the same network segment
as the port IP address of the GBTS/eGBTS, the downlink route from the eNodeB to the
GBTS/eGBTS is not required.
Step 5 (Optional) Run the eNodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
When co-transmission is enabled for the GBTS/eGBTS and eNodeB, if the GBTS/eGBTS is
deployed using DHCP, the eNodeB needs to work as the relay. Therefore, DHCP relay needs
to be enabled for the eNodeB.
//Enable DHCP relay for the eNodeB.
Step 6 (Optional) Run the eNodeB MML command ADD DHCPSVRIP to add the IP address of the
DHCP server.
When co-transmission is enabled for the GBTS/eGBTS and eNodeB, the eNodeB needs to
work as the relay if the GBTS/eGBTS is deployed using DHCP. Therefore, the IP address of
the DHCP server needs to be added on the eNodeB. For the GBTS, the IP address of the
DHCP server is the IP address of the BSC. For the eGBTS, the IP address of the DHCP server
is the IP address of the U2000.

SingleRAN

for the GBTS/eGBTS and eNodeB:
the uplink route from the GBTS/eGBTS to the BSC through the eNodeB added in step 3
must be different from the uplink route for the eNodeB. For example, you can set the
next-hop address of the uplink route from the GBTS/eGBTS to the BSC through the
eNodeB to 10.20.20.101, which is different from the next-hop address (10.20.20.1) of
the uplink route for the eNodeB. To add VLAN mapping, run the MML command ADD
VLANMAP.
ADD VLANMAP: NEXTHOPIP="10.20.20.101", MASK="255.255.255.0",
VLANMODE=SINGLEVLAN, VLANID=22, SETPRIO=DISABLE;
l Method 2 (Not recommended): Configure differentiated DSCP values. This method

requires differentiated DSCP values for the GBTS/eGBTS and eNodeB. For details
about DSCP values for the GBTS/eGBTS and eNodeB, see Bandwidth Sharing of
Multimode Base Station Co-Transmission Feature Parameter Description.
1. Run the eNodeB MML command ADD VLANCLASS.
mode, set TRAFFIC to USERDATA for all passerby flows through the eNodeB. If
differentiated data needs to be configured for the eNodeB and GBTS/eGBTS and
TRAFFIC is set to USERDATA, SRVPRIO cannot be set to 40 on the eNodeB.
2. Run the eNodeB MML command ADD VLANMAP.

VLANMODE=VLANGROUP, VLANGROUPNO=1;
----End

LTE Side
After the configuration file is delivered to the eNodeB and activated, perform the following
step on the eNodeB side to verify whether the transmission link between the eNodeB and the
MME/S-GW is normal:
Step 1 Run the eNodeB MML command PING to ping the IP address of the MME/S-GW. If the IP
address can be pinged, the transmission link is normal.

SingleRAN

----End
GSM Side
following step on the BSC side to verify whether the transmission link between the BSC and
Step 1 Run the BSC MML command PING IP to ping the IP address of the GTMU.
CONTPING=NO;
----End

Panel Interconnection on the Separate-MPT L+GU/T
+GU/M+GU Multimode Base Station Side in IP over
FE/GE Mode
guidelines.
7.7.1 Requirements
interconnection on the separate-MPT L+GU multimode base station side. In this
scenario, main-control-board-based IP co-transmission through panel interconnection on
the separate-MPT L+GU multimode base station side is enabled by cascading FE ports
on the panels in different subracks. The GBTS/eGBTS and NodeB are cascaded in one
BBU subrack through FE ports on the panel, while the eNodeB uses another BBU
subrack. The GBTS/eGBTS and NodeB are connected to the LMPT on the eNodeB
through the WMPT on the NodeB. An outbound FE/GE port on the LMPT of the
eNodeB serves as the co-transmission port of the separate-MPT L+GU multimode base
station and is connected to the MBSC and MME/S-GW. The GTMU of the GBTS/
eGBTS is connected to the WMPT of the NodeB through FE ports.

SingleRAN

on the separate-MPT L+GU multimode base station side


transmission through panel interconnection on the separate-MPT UGL multimode base station
side.

SingleRAN

through panel interconnection on the separate-MPT UGL multimode base station side


BSC

RNC

the BSC

the RNC

SingleRAN

the eNodeB (FE port 1 is during configuration on the
eNodeB to the GBTS/
eGBTS and NodeB.)

CME

the eNodeB

the NodeB (FE port 0 is
used for interconnecting the
NodeB to the eNodeB.)

the NodeB (FE port 1 is
used for interconnecting the
NodeB to the GBTS/
eGBTS.)

the GBTS/eGBTS (FE port
0 is used for interconnecting
NodeB.)

SCTP link

IP path
IP address of the U2000 10.70.70.70/24 IP address of the U2000 is

used as the IP address of the
DHCP server for the NodeB
and eNodeB
NOTE
IP addresses of two Ethernet ports used for interconnecting the NodeB to the GBTS/eGBTS and
interconnecting the NodeB to the eNodeB must be on the same network segment.
the two Ethernet ports used for interconnecting the NodeB to the GBTS/eGBTS and interconnecting the
NodeB to the eNodeB.
7.7.3 Precautions
None

SingleRAN

interconnection, no additional hardware is required, but the FE electrical or optical ports for
interconnecting main control board panels are required. Table 7-8 describes the panel
interconnection modes.

Base Panel Interconnection Mode
Station
Mode
LGU Mode 1: An outbound electrical port on the LMPT is connected to the MBSC
and MME/S-GW, an outbound optical port on the LMPT is connected to an
optical port on the WMPT, and an outbound electrical port on the WMPT is
Mode 2: An outbound optical port on the LMPT is connected to the MBSC and
MME/S-GW, an outbound electrical port on the LMPT is connected to an
electrical port on the WMPT, and an outbound optical port on the WMPT is
Mode 3: An outbound electrical port on the LMPT is connected to the MBSC

and MME/S-GW, an outbound electrical port on the LMPT is connected to an
electrical port on the WMPT, and an outbound optical port on the WMPT is
Mode 4: An outbound optical port on the LMPT is connected to the MBSC and
MME/S-GW, and an outbound optical port on the LMPT is connected to an
optical port on the WMPT, and an outbound electrical port on the WMPT is
(Optional) Initial Configuration on the U2000 Side

Configure two routes to the DHCP relay of the NodeB on the U2000 side. In this step, set the
destination IP address of one route to the OM channel IP address of the eNodeB and that of
the other route to the lower-level transmission port of the eNodeB.


SingleRAN
interconnection port on the WMPT. The BSC MML command for configuring the route from
Step 2 (Optional) Configure two routes to the DHCP relay of the GBTS. In this step, set the
destination IP address of one route to the OM channel IP address of the NodeB and that of the
other route to the lower-level transmission port of the NodeB. The BSC MML command for
configuring the route to the DHCP relay of the GBTS is ADD IPRT.
----End

Initial Configuration on the GSM eGBTS Side

interconnection port on the WMPT. The eGBTS MML command for configuring the route
----End



SingleRAN
addresses of two ports used for interconnecting the NodeB to the GBTS/eGBTS are on the
MASK="255.255.255.0";
GTMU.
the IP address of the interconnection port on the LMPT.
//Add a route from the NodeB to the BSC.
Step 4 (Optional) Add a downlink route from the BSC to the GBTS/eGBTS through the NodeB.
interconnection ports on the NodeB and the GBTS/eGBTS are on the same network segment
as the port IP address of the GBTS/eGBTS, the downlink route from the NodeB to the GBTS/
eGBTS is not required.
relay.
DHCP server.
When co-transmission is enabled for the GBTS/eGBTS and NodeB, the NodeB needs to work
as the relay if the GBTS/eGBTS is deployed using DHCP. Therefore, the IP address of the
----End

SingleRAN

NOTE
The number of the BBU subrack used by the eNodeB must be different from the number of the BBU
subrack shared by the GBTS/eGBTS and NodeB. The following description is based on the assumption
that the number of the BBU subrack used by the eNodeB is 1.
Step 1 Run the eNodeB MML command SET ETHPORT to set the attributes of the Ethernet port
on the LMPT that is used for interconnecting to the WMPT.
SET ETHPORT: CN=0, SRN=1, SN=7, SBT=BASE_BOARD, PN=1, PA=COPPER, SPEED=AUTO,
DUPLEX=AUTO;
used for interconnecting the LMPT to the WMPT.
Step 2 Run the eNodeB MML command ADD DEVIP to set the device IP address of the Ethernet
port on the LMPT that is used for interconnecting the LMPT to the WMPT. In this step,
ensure that IP addresses of two ports used for interconnecting the eNodeB to the NodeB are
on the same network segment.
ADD DEVIP: CN=0, SRN=1, SN=7, SBT=BASE_BOARD, PT=ETH, PN=1, IP="10.60.60.1",
MASK="255.255.255.0";
used for interconnecting the LMPT to the WMPT and ensure that the IP address is
on the same network segment as the port IP address of the WMPT.
Step 3 Add an uplink route from the GBTS/eGBTS/NodeB to the BSC/RNC through the eNodeB.
1. Run the eNodeB MML command ADD IPRT to add an uplink route from the NodeB to
the RNC through the eNodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP
to the IP address of the router that is directly connected to the eNodeB.
ADD IPRT: RTIDX=0, CN=0, SRN=1, SN=7, SBT=BASE_BOARD, DSTIP="10.11.11.11",
//Add a route from the NodeB to the RNC.
2. Run the eNodeB MML command ADD IPRT to add an uplink route from the GBTS/
eGBTS to the BSC through the eNodeB. In this step, set RTTYPE to NEXTHOP and
NEXTHOP to the IP address of the router that is directly connected to the eNodeB.
//Add a route from the GBTS/eGBTS to the BSC.
Step 4 (Optional) Add a downlink route from the RNC to the NodeB through the eNodeB.
The downlink route is required only if the logical IP address is used by the NodeB. If the
physical port IP address is used by the NodeB and the IP addresses of the panel
interconnection ports on the eNodeB and the NodeB are on the same network segment as the
port IP address of the NodeB, the downlink route from the eNodeB to the NodeB is not
required.
Step 5 Add a downlink route from the BSC to the GBTS/eGBTS through the eNodeB.
The downlink route to the GBTS/eGBTS needs to be configured on the eNodeB side
regardless of whether the port IP address or logical IP address is used by the GBTS/eGBTS.
In this step, set DSTIP to the port IP address or logical IP address of the GBTS/eGBTS and
NEXTHOP to the IP address of the port on the NodeB for interconnecting to the eNodeB.

SingleRAN
This step takes the port IP address configuration of the GBTS/eGBTS as an example. When
configuring a route to the logical IP address of the GBTS/eGBTS, change the value of DSTIP
in the following command:
//Add a route from the BSC to the GBTS/eGBTS.
relay. When co-transmission is enabled for the NodeB and eNodeB, the eNodeB needs to
work as the relay if the NodeB is deployed using DHCP. Therefore, DHCP relay needs to be
enabled for the eNodeB.
DHCP server.
When co-transmission is enabled for the NodeB and eNodeB, if the NodeB is deployed using
DHCP, the eNodeB needs to work as the relay. Therefore, the IP address of the DHCP server
needs to be added on the eNodeB. For the NodeB, the U2000 or RNC works as the DHCP
server. The U2000 working as the DHCP server is used as an example.
//Add the IP address of the DHCP server for the NodeB.
for the GBTS/eGBTS, NodeB, and eNodeB:
the uplink route from the GBTS/eGBTS to the BSC through the eNodeB and the uplink
route from the NodeB to the RNC through the eNodeB added in step 3 must be different
from the uplink route for the eNodeB. For example, you can set the next-hop address of
the uplink route from the GBTS/eGBTS to the BSC through the eNodeB to 10.20.20.101
and set the next-hop address of the uplink route from the NodeB to the RNC through the
VLANMAP.
ADD VLANMAP: NEXTHOPIP="10.20.20.101" MASK="255.255.255.0",

requires differentiated DSCP values for the GBTS/eGBTS, NodeB, and eNodeB. For
details about DSCP values for the GBTS/eGBTS, NodeB, and eNodeB, see Bandwidth
Sharing of Multimode Base Station Co-Transmission Feature Parameter Description.
differentiated data needs to be configured for the eNodeB and NodeB and

SingleRAN

----End


LTE Side
step on the eNodeB side to verify whether the transmission link to the eNodeB is normal:
Step 1 Run the eNodeB MML command PING to ping the IP address of the next-hop route. If the IP
----End
UMTS Side
step on the NodeB side to verify whether the transmission link to the NodeB is normal:
Step 1 Run the NodeB MML command PING to ping the IP address of the next-hop route. If the IP
----End
GSM Side
Step 1 Run the BSC MML command PING IP to ping the IP address of the GTMU.
CONTPING=NO;
Step 2 Run the RNC MML command PING IP to ping the IP address of the WMPT.
CONTPING=NO;
----End

SingleRAN

Backplane Interconnection on the Separate-MPT
LG/TG/MG Multimode Base Station Side in IP over
FE/GE Mode
In this scenario, the GSM base station can be a GBTS or an eGBTS, and the main control
board must be a GTMUb/GTMUc. This section uses a GTMUb as an example to describe the
engineering guidelines.
7.8.1 Requirements
Figure 7-11 shows the main-control-board-based IP co-transmission through backplane
interconnection on the separate-MPT LG multimode base station side. In this scenario,
an outbound FE/GE port on the LMPT/UMPT_L of the eNodeB serves as the co-
transmission port of the separate-MPT LG multimode base station and is connected to
the BSC and MME/S-GW. The GTMUb is connected to the LMPT/UMPT_L through
the backplane to implement IP-based co-transmission.
Figure 7-11 Main-control-board-based IP co-transmission through backplane

interconnection on the separate-MPT LG multimode base station side

The following feature has been enabled:

SingleRAN

transmission through backplane interconnection on the separate-MPT LG multimode base
station side.

through backplane interconnection on the separate-MPT LG multimode base station side
Table 7-9 describes the data plan.
Table 7-9 Data plan


BSC

the BSC

the eNodeB

CME

SingleRAN
OM IP address of the 10.31.31.188/24 LTE: management plane IP

eNodeB address. This is a logical IP
address and is configured on
the main control board.
Signaling/service IP address 10.33.33.188/24 LTE: control plane/user

of the eNodeB plane IP address. This is a
logical IP address and is
configured on the main
control board.
IP address of the U2000 10.60.60.60/24 LTE: peer IP address for the

OM channel

SCTP link

IP path
IP address of the GBTS 10.35.35.188/24 GSM: communication IP

address of the GBTS. This is
a logical IP address and is
configured on the GBTS
main control board.
OM/signaling/service IP 10.35.35.188/24 The same IP address is used

address of the eGBTS for O&M, signaling, and
services for the eGBTS.
GBTS electronic serial abcdefghijklmn For the GBTS, the ESN

number (ESN) needs to be planned. For the
eGBTS, the ESN does not
need to be planned.
NOTE
In this scenario, the GTMUb does not need to be configured with Ethernet port attributes such as duplex
mode and rate because the GTMUb communicates with the LMTP or UMPT_L through the backplane.
7.8.3 Precautions
None

When main-control-board-based co-transmission is implemented through backplane
interconnection, no additional hardware is required.

SingleRAN

Step 1 Run the BSC MML command ADD BTSTUNNEL to add a tunnel from the GTMUb to the
LMPT/UMPT_L.
ADD BTSTUNNEL: IDTYPE=BYID, BTSID=10, SRCCN=0, SRCSRN=0, SRCSN=6, TN=1, DSTCN=0,
DSTSRN=0, DSTSN=7;
//Add a tunnel from the GTMUb in slot 6 to the LMPT/UMPT_L in slot 7.
Step 2 (Optional) Run the BSC MML command ADD IPRT twice to configure two routes to the
DHCP relay of the GBTS on the BSC side. In this step, set the destination IP address of one
route to the OM channel IP address of the eNodeB and that of the other route to the port IP
address of the eNodeB.
ADD IPRT: SRN=0, SN=16, DSTIP="10.20.20.188", DSTMASK="255.255.255.255",
NEXTHOP="10.21.21.254", PRIORITY=HIGH, REMARK="relay";
Step 3 Run the BSC MML command ADD BTSDEVIP to add the IP address of the GTMUb.
ADD BTSDEVIP: IDTYPE=BYID, BTSID=10, PT=LOOPINTERFACE, PN=0, CN=0, SRN=0, SN=6,
IP="10.35.35.188", MASK="255.255.255.0";
//PT must be set to LOOPINTERFACE.
Step 4 Run the BSC MML command SET BTSIP to set the communication IP address of the GBTS.
Unlike non-co-transmission scenarios, this scenario requires that the GBTS use the logical IP
address. Specifically, set BTSCOMTYPE to LOGICIP. In non-co-transmission scenarios,
BTSCOMTYPE is optional.
SET BTSIP: IDTYPE=BYID, BTSID=10, BTSCOMTYPE=LOGICIP, BTSIP="10.35.35.188",
BSCIP="10.10.10.10", BTSMUTIP=NO;
//Set BTSCOMTYPE to LOGICIP and BTSIP to an appropriate value.
Step 5 Run the BSC MML command ADD BTSIPRT to add a route from the GBTS to the BSC.
Unlike non-co-transmission scenarios, set RTTYPE to OUTIF, ITFType to TUNNEL, and
IFNO to the number of the tunnel added in step 1.
ADD BTSIPRT: IDTYPE=BYID, BTSID=10, RTIDX=1, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=OUTIF, CN=0, SRN=0, SN=6, ITFType=TUNNEL,
IFNO=1;
Step 6 Run the BSC MML command ADD BTSESN to add the ESN of the GBTS.
ADD BTSESN: IDTYPE=BYID, BTSID=10, MAINDEVTAB="abcdefghijklmn",
OMBEARBOARD=BACKBOARD;
//OMBEARBOARD must be set to BACKBOARD.
----End

SingleRAN

NOTE
Compared with configuration steps described in 3900 Series Base Station Initial Configuration Guide,
the following Step 1 is added.
Step 1 Run the eGBTS MML command ADD TUNNEL to add a tunnel from the GTMUb to the
UMPT_L.
ADD TUNNEL: SSN=6, DSN=7, TUNNELTYPE=UL;
//Add a tunnel from the GTMUb in slot 6 to the UMPT_L in slot 7.
NOTE
According to the co-transmission networking plan, modify parameter values in the following Step 2
through Step 4.
Step 2 Run the eGBTS MML command ADD DEVIP to add the IP address of the eGBTS.
Unlike non-co-transmission scenarios, this scenario requires that the eGBTS use the logical IP
address. In non-co-transmission scenarios, the IP address of the eGBTS can be set as required.
ADD DEVIP: SN=6, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="10.35.35.188",
MASK="255.255.255.0";
//Set the OM/signaling/service IP address of the eGBTS and set Port Type to
LOOPINT.
Step 3 Run the eGBTS MML command ADD IPRT to add a route from the eGBTS to the BSC/
U2000.
Unlike non-co-transmission scenarios, set Subboard Type to BACK_BOARD, Route Type
to IF, Port Type to TUNNEL, and Port No. to the number of the tunnel added in Step 1.
ADD IPRT: RTIDX=0, SN=6, SBT=BACK_BOARD, DSTIP="10.21.21.1",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eGBTS to the BSC.
//Add a route from the NodeB to the U2000.
Step 4 Run the eGBTS MML command ADD OMCH to add an OM channel.
ADD OMCH: IP="10.35.35.188", MASK="255.255.255.0", PEERIP="10.60.60.60",
PEERMASK="255.255.255.0", BEAR=IPV4, CHECKTYPE=NONE, BRT=NO;
//Add an OM channel.
----End


SingleRAN
Step 1 Run the eNodeB MML command ADD TUNNEL to add a tunnel from the LMPT/UMPT_L
to the GTMUb.
ADD TUNNEL: SSN=7, DSN=6, TUNNELTYPE=DL;
//Add a tunnel from the LMPT/UMPT_L in slot 7 to the GTMUb in slot 6.
Step 2 Run the eNodeB MML command ADD DEVIP to add IP addresses for the eNodeB.
MASK="255.255.255.0";
//Add an IP address for Ethernet port 1 on the LMPT/UMPT_L in slot 7.
MASK="255.255.255.0";
//Add a signaling/service IP address for the LMPT/UMPT_L in slot 7.
Step 3 Run the eNodeB MML command ADD IPRT to add an uplink route from the GBTS/eGBTS
to the BSC through the eNodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP to
the IP address of the router that is directly connected to the eNodeB.
//Add an uplink route from the GBTS/eGBTS to the BSC through the eNodeB.
Step 4 Run the eNodeB MML command ADD IPRT to add a downlink route from the BSC to the
GBTS/eGBTS through the eNodeB.
When co-transmission for the GBTS/eGBTS and the eNodeB is implemented through tunnels
on the backplanes, the downlink route from the BSC to the GBTS/eGBTS through the
eNodeB must be configured on the eNodeB. In addition, SBT must be set to BACK_BOARD
and IFT must be set to TUNNEL.
//Add a downlink route from the BSC to the GBTS/eGBTS through the eNodeB with
Subboard Type set to BACK_BOARD and Port Type set to TUNNEL.
relay.
work as the relay if the GBTS/eGBTS is deployed using DHCP. Therefore, DHCP relay needs
to be enabled for the eNodeB.
DHCP server.
work as the relay if the GBTS/eGBTS is deployed using DHCP. Therefore, the IP address of
the DHCP server needs to be added on the eNodeB. For the GBTS, the IP address of the
DHCP server is the IP address of the BSC. For the eGBTS, the IP address of the DHCP server
is the IP address of the U2000.
Step 7 (Optional) Configure VLANs. There are two methods of configuring differentiated VLAN
data for the GBTS/eGBTS and eNodeB:

SingleRAN

the uplink route from the GBTS/eGBTS to the BSC through the eNodeB added in step 3
must be different from the uplink route for the eNodeB. For example, you can set the
VLANMAP.

requires differentiated DSCP values for the GBTS/eGBTS and eNodeB. For details
about DSCP values for the GBTS/eGBTS and eNodeB, see Bandwidth Sharing of

----End


LTE Side
step on the eNodeB side to verify whether the transmission link to the eNodeB is normal:
----End

SingleRAN
GSM Side
Step 1 Run the BSC MML command PING IP to ping the IP address of the GTMUb.
CONTPING=NO;
----End

Backplane Interconnection on the Separate-MPT UG
7.9.1 Requirements
interconnection on the separate-MPT UG multimode base station side. In this scenario,
an outbound FE port on the UMPT_U of the NodeB serves as the co-transmission port of
the separate-MPT UG multimode base station and is connected to the MBSC. The
GTMUb of the base station is interconnected to the UMPT_U through backplanes.

interconnection on the separate-MPT UG multimode base station side


SingleRAN


transmission through backplane interconnection on the separate-MPT UG multimode base
station side.

through backplane interconnection on the separate-MPT UG multimode base station side
Table 7-10 Data plan


BSC

the BSC

the RNC

the NodeB

SingleRAN
Port IP address of the 10.20.20.188/24 UMTS: device IP address

NodeB during configuration on the
CME
This IP address is
configured on the co-
transmission port.
O&M channel IP address of 10.30.30.188/24 UMTS: management plane

the NodeB IP address. This is a logical
IP address configured on the
main control board.
Signaling/service IP address 10.32.32.188/24 UMTS: control plane/user

of the NodeB plane IP address. This is a
logical IP address
control board.

RNC
IP address of the U2000 10.60.60.60/24 UMTS: OM channel peer IP

address

address of the GBTS.
This is a logical IP address
main control board.

GBTS ESN abcdefghijklmn For the GBTS, the ESN

needs to be planned. For the
need to be planned.
NOTE
In this scenario, the GTMUb of the GBTS/eGBTS does not need to be configured with Ethernet port
attributes such as duplex mode and rate because the GTMUb communicates with the UMPT_U through
the backplane.
7.9.3 Precautions
None

SingleRAN

When main-control-board-based co-transmission is implemented through backplane
interconnection, no additional hardware is required.

UMPT_U.
DSTSRN=0, DSTSN=7;
//Add a tunnel from the GTMUb in slot 6 to the UMPT_U in slot 7.
route to the OM channel IP address of the NodeB and that of the other route to the port IP
address of the NodeB.
IP="10.35.35.188", MASK="255.255.255.0";
address. Specifically, set BTSCOMTYPE to LOGICIP. In non-co-transmission scenarios, set
BTSCOMTYPE to an appropriate value based on individual needs.
IFNO=0;
----End

SingleRAN


Initial Configuration Guide, the following steps are added or modified.
NOTE
Compared with configuration steps described in 3900 Series Base Station Initial Configuration
Guide, the following Step 1 is added.
UMPT_U.
NOTE
According to the co-transmission networking plan, modify parameter values in the following steps.
address, that is, Port Type must be set to LOOPINT. In non-co-transmission scenarios, the
IP address of the eGBTS can be set as required.
ADD DEVIP: SRN=0, SN=6, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="10.35.35.188",
MASK="255.255.255.0";
//Set the signaling/service IP address of the eGBTS and set Port Type to LOOPINT.
U2000.
ADD IPRT: RTIDX=0, SRN=0, SN=6, SBT=BACK_BOARD, DSTIP="10.21.21.1",
//Add a route from the eGBTS to the U2000.
----End

SingleRAN

Step 1 Run the NodeB MML command ADD DEVIP to add IP addresses for the NodeB.
ADD DEVIP: CN=0, SRN=0, SN=7, SBT= BASE_BOARD, PT=ETH, PN=1, IP="10.20.20.188",
MASK="255.255.255.0";
//Add an IP address for Ethernet port 1 on the UMPT_U.
MASK="255.255.255.0";
//Add a signaling/service IP address for the NodeB.
Step 2 Run the NodeB MML command ADD TUNNEL to add a tunnel from the UMPT_U to the
GTMUb.
//Add a tunnel from the UMPT_U in slot 7 to the GTMUb in slot 6.
ADD IPRT: RTIDX=0, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="10.20.20.1";
//Add a route from the GBTS/eGBTS to the BSC through the NodeB for the UMPT_U in
slot 7.
Step 4 Run the NodeB MML command ADD IPRT to add a downlink route from the BSC to the
GBTS/eGBTS through the NodeB.
When co-transmission for the GBTS/eGBTS and the NodeB is implemented through tunnels
on the UMPT_U backplane, the downlink route from the BSC to the GBTS/eGBTS through
the NodeB must be configured on the NodeB. In addition, SBT must be set to
BACK_BOARD and IFT must be set to TUNNEL.
ADD IPRT: RTIDX=1, CN=0, SN=7, SBT=BACK_BOARD, DSTIP="10.35.35.188",
//Add a downlink route from the BSC to the GBTS/eGBTS through the NodeB for the
UMPT_U in slot 7.
relay.
DHCP server.

SingleRAN

for the BTS and NodeB:
must be different from the uplink route for the NodeB. For example, you can set the
NodeB to 10.20.20.101, which is different from the next-hop address (10.20.20.1) of the
uplink route for the NodeB. To add VLAN mapping, run the MML command ADD
VLANMAP.
ADD VLANMAP: NEXTHOPIP="10.20.20.101", MASK=255.255.255.255,

requires differentiated DSCP values for the GBTS/eGBTS and NodeB. For details about
DSCP values for the GBTS/eGBTS and NodeB, see Bandwidth Sharing of Multimode
Base Station Co-Transmission Feature Parameter Description.
2. Run the NodeB MML command ADD VLANMAP to configure the DSCP value.
----End


UMTS Side
Step 1 Run the NodeB MML command PING to ping the IP address of the RNC. If the IP address
can be pinged, the transmission link is normal.

SingleRAN

----End
GSM Side
CONTPING=NO;
----End
7.10 UTRPc-based Co-Transmission Through Backplane

Interconnection on the Separate-MPT UG Multimode
Base Station Side in IP over FE/GE Mode
7.10.1 Requirements
Figure 7-15 shows the UTRPc-based IP co-transmission through backplane
interconnection on the Separate-MPT UG multimode base station side. In this scenario,
an outbound FE port on the UTRPc controlled by the WMPT/UMPT_U of the NodeB
serves as the co-transmission port of the Separate-MPT UG multimode base station and
is connected to the MBSC. The GTMUb of the GBTS/eGBTS is interconnected to the
UTRPc through backplanes.
Figure 7-15 UTRPc-based IP co-transmission through backplane interconnection on the

separate-MPT UG multimode base station side

SingleRAN


Figure 7-16 shows an example of network topology for UTRPc-based IP co-transmission
through backplane interconnection on the separate-MPT UG multimode base station side.
Figure 7-16 Example of network topology for UTRPc-based IP co-transmission through

backplane interconnection on the separate-MPT UG multimode base station side

BSC

the BSC

SingleRAN

the RNC

the NodeB
OM channel IP address of 10.30.30.1/24 UMTS: management plane

the NodeB IP address. This is a logical
main control board.

logical IP address
control board.

the UTRPc of the NodeB during configuration on the
CME
This IP address is
transmission port.

RNC
IP address of the U2000 10.60.60.60/24 UMTS: OM channel peer IP

address

main control board.


need to be planned.
NOTE
mode and rate because the GTMUb communicates with the UTRPc through the backplane.

SingleRAN
7.10.3 Precautions
None

l Compared with non-co-transmission scenarios, UTRPc-based IP co-transmission
through backplane interconnection on the UG multimode base station side requires the
UTRPc.
l Cables to the UTRPc on the UG multimode base station side are used to connect to the
transport network.

UTRPc.
DSTSRN=0, DSTSN=4;
//Add a tunnel from the GTMUb in slot 6 to the UTRPc in slot 4.
route to the OM channel IP address of the NodeB and that of the other route to the port IP
address of the NodeB.
IP="10.35.35.188", MASK="255.255.255.0";


SingleRAN

IFNO=0;
----End

Initial Configuration Guide, the following steps are added or modified.
NOTE
UTRPc.
NOTE
MASK="255.255.255.0";
U2000.

SingleRAN

PEERMASK="255.255.255.0", BEAR=IPV4, SRN=0, SN=6, SBT=BACK_BOARD, BRT=NO;
//Add an OM channel and set Subboard Type to BACK_BOARD.
----End

Step 1 Run the ADD BRD command to add a UTRPc.

ADD BRD: CN=0, SRN=0, SN=4, BT=UTRP, SBT=UTRPc;
//Add a UTRPc to slot 4.
Step 2 Run the SET ETHPORT command to set the Ethernet port attribute for the UTRPc.
SET ETHPORT: CN=0, SRN=0, SN=4, SBT=ETH_COVERBOARD, PN=1, PA=COPPER, SPEED=AUTO,
DUPLEX=AUTO;
//Set parameters related to Ethernet port 1 on the UTRPc in slot 4. Both data
rate and duplex mode are set to auto-negotiation.
ADD DEVIP: CN=0, SRN=0, SN=4, SBT= ETH_COVERBOARD, PT=ETH, PN=1,
IP="10.20.20.188", MASK="255.255.255.0";
//Add an IP address for Ethernet port 1 on the UTRPc.
MASK="255.255.255.0";
Step 4 Run the NodeB MML command ADD TUNNEL to add a tunnel from the UTRPc to the
GTMUb.
//Add a tunnel from the UTRPc in slot 4 to the GTMUb in slot 6.
ADD IPRT: RTIDX=0, CN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="10.10.10.10",
//Add a route from the GBTS/eGBTS to the BSC through the NodeB for the UTRPc in
slot 4.
GBTS/eGBTS through the NodeB.
When co-transmission for the GBTS/eGBTS and the NodeB is implemented through tunnels
on the UTRPc backplane, the downlink route from the BSC to the GBTS/eGBTS through the
NodeB must be configured on the NodeB. In addition, SBT must be set to BACK_BOARD
and IFT must be set to TUNNEL.

SingleRAN
UTRPc in slot 4.
relay.
DHCP server.
must be different from the uplink route for the NodeB. For example, you can set the
NodeB to 10.20.20.101, which is different from the next-hop address (10.20.20.1) of the
uplink route for the NodeB. To add VLAN mapping, run the MML command ADD
VLANMAP.

requires differentiated DSCP values for the GBTS/eGBTS and NodeB. For details about
DSCP values for the GBTS/eGBTS and NodeB, see Bandwidth Sharing of Multimode
Base Station Co-Transmission Feature Parameter Description.
a. Run the NodeB MML command ADD VLANCLASS.
//Set VLANID to 22 for the data flow with SRVPRIO set to 40. In VLAN
group mode, set TRAFFIC to USERDATA for all passerby flows through the
NodeB. If differentiated data needs to be configured for the NodeB and
GBTS/eGBTS and TRAFFIC is set to USERDATA, SRVPRIO cannot be set to 40
on the NodeB.
//Set VLANID to 22 for the data flow with SRVPRIO set to 0. The DSCP
value in DHCP packets is fixed at 0. If DHCP relay is enabled on the
network where VLAN data is configured, set the DSCP value to 0 for VLAN.
If the DSCP value is not set to 0, DHCP packets sent to the DHCP server
do not contain the VLAN field. In addition, set TRAFFIC to USERDATA.
b. Run the NodeB MML command ADD VLANMAP to configure the DSCP value.
----End

SingleRAN


UMTS Side
----End
GSM Side
CONTPING=NO;
----End
7.11 UTRPc-based Co-Transmission Through Backplane

Interconnection on the Separate-MPT UG+L/UG+T/UG
+M Multimode Base Station Side in IP over FE/GE Mode
7.11.1 Requirements
Figure 7-17 shows the UTRPc-based IP co-transmission through backplane
interconnection on the separate-MPT UG+L multimode base station side. In this
scenario, an FE/GE port on the UTRPc controlled by the WMPT/UMPT_U of the
NodeB serves as the co-transmission port of the separate-MPT UGL multimode base
station and is connected to the MBSC and MME/S-GW. The GTMUb and UTRPc in one

SingleRAN
BBU are interconnected by using backplanes. The UMPT_L and UTRPc are
interconnected by using backplanes through the UCIU.
Figure 7-17 UTRPc-based IP co-transmission through backplane interconnection on the

separate-MPT UG+L multimode base station side


Figure 7-18 shows an example of network topology for UTRPc-based IP co-transmission
through backplane interconnection on the separate-MPT UG+L multimode base station side.

SingleRAN
Figure 7-18 Example of network topology for UTRPc-based IP co-transmission through

backplane interconnection on the separate-MPT UG+L multimode base station side

Item IP Address Remarks

BSC

RNC

the RNC

the BSC

the UTRPc

SingleRAN
OM IP address of the NodeB 10.30.30.1/24 UMTS: management plane

IP address. This IP address
is configured on the main
control board.

control board.

CME
This IP address is
transmission port.

SCTP link

IP path
IP address of the U2000 10.60.60.60/24 UMTS: peer IP address for

the OM channel


control board.

and is configured on the
GBTS main control board.

BTS ESN abcdefghijklmn For the GBTS, the ESN

need to be planned.

SingleRAN
NOTE
mode and rate because the GTMUb communicates with the UTRPc through the backplane. In addition,
the UMPT_L does not need to be configured with Ethernet port attributes because the UMPT_L
communicates with the UCIU through the CI interface.
7.11.3 Precautions
None

l Unlike non-co-transmission scenario, this scenario requires that the UMPT_L and
UTRPc must be configured on the eNodeB side. In addition, the UCIU must be
configured on the GBTS/eGBTS side.
l The UCIU in the BBU subrack accommodating the NodeB and GBTS/eGBTS is
connected to the UMPT_L in the BBU subrack accommodating the eNodeB by using
inter-subrack interconnection cables.
l Cables to the UTRPc on the UG+L multimode base station side are used to connect to
the transport network.

Configure two routes from the U2000 to the DHCP relay of the eNodeB. In this step, set the
other route to the lower-level transmission port of the NodeB.

Step 1 Run the ADD BTSBRD command to add a UCIU.

ADD BTSBRD: IDTYPE=BYID, BTSID=10, CN=0, SRN=0, SN=0, BT=UCIU;
//Add a UCIU to slot 0.
Step 2 Run the ADD BTSCTRLLNK command to add a BBU interconnection control link between
GSM and LTE.
ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=10, LN=0, CN=0, SRN=1, SN=7, UPCN=0, UPSRN=0,
UPSN=0, UPPT=0;
//Add a BBU interconnection control link between the board in slot 7 of subrack 1
and the board in slot 0 of subrack 0.
UTRPc.
DSTSRN=0, DSTSN=4;

SingleRAN
IP="10.35.35.188", MASK="255.255.255.0";
Step 6 Run the BSC MML command ADDBTSIPRT to add a route from the GBTS to the BSC.

IFNO=0;
Step 8 (Optional) Run the BSC MML command ADD IPRT to add a route to the DHCP relay of the
GBTS. In this step, set DSTIP to the OM channel IP address of the NodeB. Run this
command again to add another route and set DSTIP to the lower-level transmission port of
the NodeB.
NEXTHOP="10.21.21.254", PRIORITY=HIGH, REMARK="relay;
----End



NOTE
Guide, the following steps are added.
Step 1 Run the eGBTS MML command ADD BRD to add a UCIU board.
ADD BRD: CN=0, SRN=0, SN=0, BT=UCIU;
//Add a UCIU board to slot 0.

SingleRAN
Step 2 Run the eGBTS MML command ADD CTRLLNK to add a BBU interconnection control
link.
ADD CTRLLNK: LN=0, CN=0, SRN=1, SN=7, UPCN=0, UPSRN=0, UPSN=0, UPPT=0;
//Add a BBU interconnection control link between slot 7 of subrack 1 and slot 0
of subrack 0.
UTRPc.
//Add a tunnel from the GTMUb in slot 6 of subrack 0 to the UTRPc in slot 4 of
subrack 0.
NOTE
MASK="255.255.255.0";
U2000.

----End



SingleRAN
NOTE
In this scenario, the eNodeB uses the CI interface for communication. Therefore, Ethernet ports are not
required.
Step 1 Run the ADD BTSCTRLLNK command to add a BBU interconnection control link.
Step 2 Run the eNodeB MML command ADD TUNNEL to add a tunnel from the UMPT_L to the
UTRPc.
ADD TUNNEL: SSRN=1, SSN=7, DSN=4, TUNNELTYPE=UL;
//Add a tunnel from the UMPT_L of the eNodeB in slot 7 of subrack 1 to the UTRPc
in slot 4 of subrack 0.
Step 3 Run the eNodeB MML command ADD DEVIP to set the IP address of the eNodeB.
Unlike non-co-transmission scenarios, this scenario requires that the eNodeB uses the logical
IP address. Specifically, set PT to LOOPINT. In non-co-transmission scenarios, set PT based
on individual needs.
MASK="255.255.255.0";
//When configuring the signaling/service IP address for the eNodeB, set SRN to 1,
SN to 7, and PT to LOOPINT.
Step 4 Run the eNodeB MML command ADD IPRT to add a route from the eNodeB to the MME/S-
GW/U2000.
Unlike non-co-transmission scenarios, set SBT to BACK_BOARD, RTTYPE to IF, IFT to

TUNNEL, and IFNO to the number of the tunnel added in step 2.
//Add a route from the eNodeB to the MME.
//Add a route from the eNodeB to the S-GW.
//Add a route from the eNodeB to the U2000.
Step 5 (Optional) Run the eNodeB MML command ADD RSCGRP to add a transmission resource
group.
ADD RSCGRP: SRN=1, SN=7, BEAR=IP, SBT=BACK_BOARD, PT=TUNNEL, RSCGRPID=0, RU=KBPS,
TXBW=3000, RXBW=3000, TXCBS=4000, TXEBS=4000, TXCIR=4000, RXCIR=4000, TXPIR=4000,
RXPIR=4000, TXPBS=4000;
//When adding a transmission resource group, set SBT to BACK_BOARD and PT to
TUNNEL.
Step 6 Run the eNodeB MML command ADD IPPATH to add an IP path.
ADD IPPATH: PATHID=0, SRN=1, SN=7, SBT=BACK_BOARD, PT=TUNNEL, PN=0,
JNRSCGRP=DISABLE, LOCALIP="10.33.33.188", PEERIP="10.50.50.50", PATHTYPE=ANY;
//When adding an IP path, set SBT to BACK_BOARD and PT to TUNNEL.
Step 7 Run the eNodeB MML command ADD OMCH to add an OM channel.
----End

SingleRAN

Step 1 Run the NodeB MML command ADD BRD to add a UTRPc.
//Add a UTRPc in slot 4.
Step 2 Run the SET ETHPORT command to set the Ethernet port attribute for the UTRPc.
SET ETHPORT: CN=0, SRN=0, SN=4, SBT=ETH_COVERBOARD, PN=1, PA=COPPER, SPEED=AUTO,
DUPLEX=AUTO;
//Set parameters related to Ethernet port 1 on the UTRPc in slot 0. Both data
rate and duplex mode are set to auto-negotiation.
ADD DEVIP: CN=0, SRN=0, SN=4, SBT= ETH_COVERBOARD, PT=ETH, PN=1,
IP="10.20.20.188", MASK="255.255.255.0";
//Add an IP address for Ethernet port 1 on the UTRPc.
MASK="255.255.255.0";
Step 4 Run the ADD BTSCTRLLNK command to add a BBU interconnection control link.
Step 5 Run the NodeB MML command ADD TUNNEL to add tunnels from the UTRPc to the
GTMUb and UMPT_L.
//Add a tunnel from the UTRPc in slot 4 to the GTMUb in slot 6.
ADD TUNNEL: SSN=4, TUNNELID=1, DSRN=1, DSN=7, TUNNELTYPE=DL;
//Add a tunnel from the UTRPc in slot 4 of subrack 0 to the UMPT_L in slot 7 of
subrack 1.
to the BSC through the NodeB and an uplink route from the eNodeB to the MME/S-GW/
U2000 through the NodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP to the IP
address of the router that is directly connected to the NodeB.
//Add a route from the GBTS/eGBTS to the BSC through the NodeB for the UTRPc in
slot 4.
//Add a route from the eNodeB to the MME through the NodeB for the UTRPc in slot
4.
//Add a route from the eNodeB to the S-GW through the NodeB for the UTRPc in slot
4.
//Add a route from the eNodeB to the U2000 through the NodeB for the UTRPc in

SingleRAN
slot 4. Skip this step if the UMPT_U has already been configured with a route to
the U2000.
GBTS/eGBTS through the NodeB and a downlink route from the MME/S-GW/U2000 to the
eNodeB through the NodeB.
When co-transmission for the GBTS/eGBTS, eNodeB, and NodeB is implemented through
tunnels on the UTRPc backplane, the downlink route from the BSC to the GBTS/eGBTS
through the NodeB and the downlink route from the MME/S-GW/U2000 must be configured
on the NodeB. In addition, Subboard Type must be set to BACK_BOARD and Port Type
must be set to TUNNEL.
UTRPc in slot 4.
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
//Add a downlink route from the MME/S-GW/U2000 to the eNodeB through the NodeB
for the UTRPc in slot 4.
relay.
When co-transmission is enabled for the GBTS/eGBTS, eNodeB, and NodeB, the NodeB
needs to work as the relay if the GBTS/eGBTS and eNodeB are deployed using DHCP.
Therefore, DHCP relay needs to be enabled for the NodeB.
DHCP server.
When co-transmission is enabled for the GBTS/eGBTS, eNodeB and NodeB, the NodeB
needs to work as the relay if the GBTS/eGBTS and eNodeB are deployed using DHCP.
Therefore, the IP address of the DHCP server needs to be added on the NodeB. The DHCP
server of the GBTS is BSC, the DHCP server of the eGBTS is U2000, and the DHCP server
of the eNodeB is U2000.
//Add the IP address of the DHCP server for the eGBTS/eNodeB.
the uplink route from the GBTS/eGBTS to the BSC through the NodeB and the uplink
route from the eNodeB to the MME/S-GW through the NodeB added in step 6 must be
different from the uplink route for the NodeB. For example, you can set the next-hop
10.20.20.101, and set the next-hop address of the uplink route from the eNodeB to the
MME/S-GW through the NodeB to 10.20.20.201, which is different from the next-hop
address (10.20.20.1) of the uplink route for the NodeB. To add VLAN mapping, run the
MML command ADD VLANMAP.

SingleRAN

ADD VLANMAP: NEXTHOPIP=""10.20.20.201" MASK=255.255.255.255,

requires differentiated DSCP values for the GBTS/eGBTS, eNodeB, and NodeB. For
differentiated data needs to be configured for the NodeB and eNodeB and

----End

UMTS Side
RNC is normal:
----End

SingleRAN
GSM Side
CONTPING=NO;
----End
LTE Side
address can be pinged, the transmission link between the eNodeB and the MME/S-GW is
normal.
----End

Backplane Interconnection on the Separate-MPT UG
+L/UG+T/UG+M Multimode Base Station Side in IP over
FE/GE Mode
7.12.1 Requirements
scenario, an FE/GE port on the UMPT_U of the NodeB serves as the co-transmission
port of the separate-MPT UG+L multimode base station and is connected to the MBSC
and MME/S-GW. The GTMUb and UMPT_U in one BBU are interconnected by using
backplanes. The UMPT_L and UMPT_U are interconnected by using interconnection
cables.

SingleRAN

interconnection on the separate-MPT UG+L multimode base station side (UMPT
+UMPT interconnection)

scenario, an FE/GE port on the UMPT_U of the NodeB serves as the co-transmission
port of the separate-MPT UG+L multimode base station and is connected to the MBSC
and MME/S-GW. The GTMUb and UMPT_U in one BBU are interconnected by using
backplanes. The UMPT_L and UMPT_U are interconnected by using backplanes
through the UCIU. This co-transmission mode is not recommended for new deployment.

SingleRAN

interconnection on the separate-MPT UG+L multimode base station side (UCIU+UMPT
interconnection)
This document provides only the engineering guidelines for the scenario shown in Figure
7-19. The engineering guidelines for the scenario shown in Figure 7-20 is similar to those for
the scenario shown in Figure 7-19.

transmission through backplane interconnection on the separate-MPT UG+L multimode base
station side.

SingleRAN

through backplane interconnection on the separate-MPT UG+L multimode base station side


BSC

RNC

the RNC

the BSC

the UMPT_U

SingleRAN
OM IP address of the 10.30.30.1/24 UMTS: management plane

NodeB IP address. This IP address
is configured on the main
control board.

control board.

the UMPT_U of the NodeB during configuration on the
CME. This IP address is
transmission port.

SCTP link

IP path

the OM channel


control board.

main control board.


need to be planned.

SingleRAN
NOTE
mode and rate because the GTMUb communicates with the UMPT_U through the backplane. In
addition, the UMPT_L does not need to be configured with Ethernet port attributes because the
UMPT_L communicates with the UMPT_U through the CI interface.
7.12.3 Precautions
None

l Unlike non-co-transmission scenario, this scenario requires that the UMPT_L be
configured on the eNodeB side.
l The UMPT_U in the BBU subrack accommodating the NodeB and GBTS/eGBTS is
connected to the UMPT_L in the BBU subrack accommodating the eNodeB by using
inter-subrack interconnection cables.
l A cable to the UMPT_U on the UG+L multimode base station side is used to connect to
the transport network.

Configure two routes from the U2000 to the DHCP relay of the eNodeB. In this step, set the
other route to the lower-level transmission port of the NodeB.


NOTE
Compared with the steps in 3900 Series Base Station Initial Configuration Guide, the following Step 1
and Step 2 are added.
Step 1 Run the BSC MML command ADD BTSCTRLLNK to add a BBU interconnection control
link between GSM and LTE.
UPSN=7, UPPT=8;
of subrack 0.
UMPT_U.
DD BTSTUNNEL: IDTYPE=BYID, BTSID=10, SRCCN=0, SRCSRN=0, SRCSN=6, TN=0, DSTCN=0,
DSTSRN=0, DSTSN=7;

SingleRAN
NOTE
According to co-transmission network plan, the following Step 3 through Step 7 is modified.
IP="10.35.35.188", MASK="255.255.255.0";
IFNO=0;
GBTS. In this step, set DSTIP to the OM channel IP address of the NodeB. Run this
the NodeB.
NEXTHOP="10.21.21.254", PRIORITY=HIGH, REMARK="relay;
----End

NOTE
Guide, the following steps are added.
link.

SingleRAN
of subrack 0.
UMPT_U.
//Add a tunnel from the GTMUb in slot 6 of subrack 0 to the UMPT_U in slot 7 of
subrack 0.
NOTE
MASK="255.255.255.0";
U2000.

----End



NOTE
required.

SingleRAN
Step 1 Run the eNodeB MML command ADD CTRLLNK to add a BBU interconnection control
link.
of subrack 0. The BBU subrack number for the eNodeB must be different from that
for the GBTS/eGBTS and NodeB. It is assumed that the BBU subrack number for the
eNodeB is 1 here.
Step 2 Run the eNodeB MML command ADD TUNNEL to add a tunnel from the UMPT_L to the
UMPT_U.
ADD TUNNEL: SSRN=1, SSN=7, DSN=7,TUNNELTYPE=UL;
//Add a tunnel from the UMPT_L of the eNodeB in slot 7 of subrack 1 to the UMPT_U
in slot 7 of subrack 0.
Step 3 Run the eNodeB MML command ADD DEVIP to set the IP address of the eNodeB.
Unlike non-co-transmission scenarios, this scenario requires that the eNodeB uses the logical
IP address. Specifically, set PT to LOOPINT. In non-co-transmission scenarios, set PT based
on individual needs.
MASK="255.255.255.0";
//When configuring the signaling/service IP address for the eNodeB, set SRN to 1,
SN to 7, and PT to LOOPINT.
Step 4 Run the eNodeB MML command ADD IPRT to add a route from the eNodeB to the MME/S-
GW/U2000.
Unlike non-co-transmission scenarios, set SBT to BACK_BOARD, RTTYPE to IF, IFT to

TUNNEL, and IFNO to the number of the tunnel added in step 2.
//Add a route from the eNodeB to the MME.
//Add a route from the eNodeB to the S-GW.
//Add a route from the eNodeB to the U2000.
group.
//When adding a transmission resource group, set SBT to BACK_BOARD and PT to
TUNNEL.
//When adding an IP path, set SBT to BACK_BOARD and PT to TUNNEL.
Step 7 Run the eNodeB MML command ADD OMCH to add an OM channel.
----End

SingleRAN

MASK="255.255.255.0";
//Add an IP address for Ethernet port 1 on the UMPT_U.
MASK="255.255.255.0";
Step 2 Run the NodeB MML command ADD CTRLLNK to add a BBU interconnection control
link.
of subrack 0.
Step 3 Run the NodeB MML command ADD TUNNEL to add tunnels from the UMPT_U to the
GTMUb and UMPT_L.
//Add a tunnel from the UMPT_U in slot 7 to the GTMUb in slot 6.
ADD TUNNEL: SSN=7, TUNNELID=1, DSRN=1, DSN=7, TUNNELTYPE=DL;
//Add a tunnel from the UMPT_U in slot 7 of subrack 0 to the UMPT_L in slot 7 of
subrack 1.
to the BSC through the NodeB and an uplink route from the eNodeB to the MME/S-GW/
U2000 through the NodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP to the IP
//Add a route from the GBTS/eGBTS to the BSC through the NodeB for the UMPT_U in
slot 7 of subrack 0.
//Add a route from the eNodeB to the MME through the NodeB for the UMPT_U in slot
7 of subrack 0.
//Add a route from the eNodeB to the S-GW through the NodeB for the UMPT_U in
//Add a route from the eNodeB to the U2000 through the NodeB for the UMPT_U in
slot 7 of subrack 0. Skip this step if the UMPT_U has already been configured
with a route to the U2000.
GBTS/eGBTS through the NodeB and a downlink route from the MME/S-GW/U2000 to the
eNodeB through the NodeB.
When co-transmission for the GBTS/eGBTS, eNodeB, and NodeB is implemented through
tunnels on the UMPT_U backplane, the downlink route from the BSC to the GBTS/eGBTS

SingleRAN
through the NodeB and the downlink route from the MME/S-GW/U2000 must be configured
on the NodeB. In addition, SBT must be set to BACK_BOARD and IFT must be set to
TUNNEL.
UMPT_U in slot 7 of subrack 0.
//Add a downlink route from the MME/S-GW/U2000 to the eNodeB through the NodeB
for the UMPT_U in slot 7 of subrack 0.
relay.
as the relay if the GBTS/eGBTS is deployed using DHCP. Therefore, DHCP relay needs to be
enabled for the NodeB.
DHCP server.
as the relay if the GBTS/eGBTS is deployed using DHCP. Therefore, the IP address of the
DHCP server needs to be added on the NodeB. The DHCP server of the GBTS/eGBTS is
BSC, while the DHCP server of the eNodeB is U2000.
//Add the IP address of the DHCP server for the eGBTS/eNodeB.
the uplink route from the GBTS/eGBTS to the BSC through the NodeB and the uplink
route from the eNodeB to the MME/S-GW through the NodeB added in step 4 must be
different from the uplink route for the NodeB. For example, you can set the next-hop
10.20.20.101, and set the next-hop address of the uplink route from the eNodeB to the
MME/S-GW through the NodeB to 10.20.20.201, which is different from the next-hop
address (10.20.20.1) of the uplink route for the NodeB. To add VLAN mapping, run the
MML command ADD VLANMAP.
ADD VLANMAP: NEXTHOPIP="10.20.20.201" MASK=255.255.255.255,

requires differentiated DSCP values for the GBTS/eGBTS, eNodeB, and NodeB. For

SingleRAN

differentiated data needs to be configured for the NodeB and eNodeB and

----End


UMTS Side
RNC is normal:
----End
GSM Side
CONTPING=NO;
----End

SingleRAN
LTE Side
normal.
----End
7.13 Reconstruction from Transmission Through the Main

Control Board Panel on a GBTS to Main-Control-Board-
based Co-Transmission Through Panel Interconnection on
the Separate-MPT UG Multimode Base Station Side in IP
over FE/GE Mode
This section describes how to reconstruct the transmission mode from transmission through
the main control board panel on a GBTS to main-control-board-based IP co-transmission
through panel interconnection on the separate-MPT UG multimode base station side. The
GSM base stations in this scenario can only be GBTSs.
7.13.1 Requirements
Figure 7-22 shows the network topologies before and after reconstruction.
Figure 7-22 Network topologies before and after reconstruction

SingleRAN


Figure 7-23 shows an example of reconstruction from transmission through the main control
board panel on a GBTS to main-control-board-based IP co-transmission through panel
interconnection on the separate-MPT UG multimode base station side.
Figure 7-23 Example of reconstruction from transmission through the main control board
panel on a GBTS to main-control-board-based IP co-transmission through panel

Device IP address of the 10.10.10.10/32 When DHCP relay is

BSC enabled for the NodeB, the
IP address of the DHCP
server is 10.10.10.10, which
is the device IP address of
the BSC.

SingleRAN

RNC

U2000
IP address of the port on 10.21.21.254/24 -

router 1 that is connected to
the BSC

the RNC

the NodeB
IP address of FE 0 port on 10.22.22.1/24 -

the NodeB

the NodeB
OM IP address of the 10.24.24.24/24 -

NodeB

the GBTS
NOTE
IP addresses of two ports used for interconnecting the NodeB to the GBTS must be on the same network
segment. Data configurations at the data link layer, such as the duplex mode and rate, must be consistent
between the two ports used for interconnecting the NodeB to the GBTS.
7.13.3 Reconstruction Preparations and Procedure
Introduction to IP Rehoming
The IP rehoming function is introduced to facilitate IP co-transmission reconstruction on the
GSM side. The IP rehoming function remotely delivers new IP transmission configuration
data to the GBTS using messages before reconstruction. After receiving the new data, the
GBTS saves it to the flash memory. Once the GBTS resets, it uses the new data to attempt to
set up links to the BSC within a period of time. This saves the detection time. After setting up
links to the BSC, the GBTS deletes the old IP transmission configuration data.
Reconstruction Preparations
1. Check the system.

SingleRAN
– Perform a health check on the system to check whether network KPIs are normal
and whether major alarms were reported. If network KPIs are abnormal or major
alarms were reported, record them for KPI or alarm comparison before and after
reconstruction.
– Run the BSC MML command DSP BTSVER to check the software version of a
GBTS.
2. Get boards ready and obtain software versions.
– Get NodeB hardware ready.
– Obtain the software versions of the MBSC, U2000, CME, and multimode base
station.
3. Back up data.
– Back up the measurement results of original performance counters reported one
week before reconstruction.
– Back up GBTS data configurations before reconstruction on the CME. (CME:
Main View > Right-click a site > Export MML for Creating BTS.)
4. Make the reconfiguration scripts.
– For details about reconfiguration on the UMTS side, see Reconfiguration on the
UMTS Side.
– Reconfiguration on the GSM side has the following scripts:
n IP rehoming scripts. For details, see Reconfiguration on the GSM Side.
n Scripts for reconstruction. For details, see Initial Configuration on the GSM
Side (GBTS and BSC) in section 7.5 Main-Control-Board-based Co-
Transmission Through Panel Interconnection on the Separate-MPT UG
Multimode Base Station Side in IP over FE/GE Mode.
5. Make the rollback scripts.
– For details about rollback scripts on the UMTS side, see Rollback on the UMTS
Side.
– For details about rollback scripts on the GSM side, see Rollback on the GSM Side.
Reconstruction Procedure
Step 1 Upgrade the software.
If the GBTS software version does not meet the reconstruction requirements, upgrade the
software before reconstruction.
Step 2 Reconstruct hardware and modify data configurations.

1. Execute the BSC IP rehoming MML command scripts.
NOTE
Performing the following steps will interrupt GBTS services. Before performing the following
steps, power off the GTMU. Power on the GTMU after NodeB deployment is complete. This is
because the BSC IP rehoming MML command scripts take effect after the next GBTS reset.
2. Remove the GTMU and install the WMPT/UMPT_U at the site. Connect the GTMU to
the WMPT/UMPT_U through panel interconnection, and connect the transmission cable
to the planned port on the WMPT/UMPT_U.
3. Deactivate the GBTS on the BSC. Execute the prepared GBTS reconstruction scripts to
reactivate the GBTS.

SingleRAN
4. Use the prepared NodeB reconstruction scripts to perform automatic NodeB deployment.
5. Install and power on the GTMU, and wait for GBTS deployment.
Verify services after reconstruction. For details, see section 7.5.6 Activation Observation.
Step 3 (Optional) Perform the rollback operation if reconstruction fails.

l Execute the rollback scripts. For details about the rollback scripts, see section 7.13.6
Rollback.
l Restore the hardware configuration and network topology to those before reconstruction.
----End
7.13.4 Precautions
None
7.13.5 Reconfiguration
Reconfiguration on the UMTS Side

For details, see section 7.5 Main-Control-Board-based Co-Transmission Through Panel
Interconnection on the Separate-MPT UG Multimode Base Station Side in IP over
FE/GE Mode.
Reconfiguration on the GSM Side

Step 1 Run the BSC MML command IMP BTSIPRT to import the configuration of the next-hop
route from the GBTS to the BSC.
IMP BTSIPRT: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, CN=0, SRN=0, SN=6,
NEXTHOP="10.22.22.1";
Step 2 Run the BSC MML command ACT BTSIMPDATA to activate the IP rehoming data.
ACT BTSIMPDATA: IDTYPE=BYID, BTSID=10;
----End
7.13.6 Rollback
Rollback on the UMTS Side

Remove the NodeB on the CME. (CME: Base Station > UMTS > Right-click a site >
Delete.)
Rollback on the GSM Side

Step 1 Run the BSC MML command DEA BTS to deactivate the GBTS. (CME: Base Station >
GSM > Right-click a site > Deactivate Site.)
DEA BTS: IDTYPE=BYID, BTSID=10;
Step 2 Run the BSC MML command RMV IPPATH to remove an IP path. (CME: Controller >
Transmission View > GSM > Abis > Abis Configuration Express > IP Transport > IP
Path.)

SingleRAN
RMV IPPATH: ANI=1017, PATHID=0;

//Remove the IP path between the GBTS and the BSC.
Step 3 Run the BSC MML command RMV ADJNODE to remove an adjacent node. (CME:
Controller > Transmission View > GSM > Abis > Abis Configuration Express > IP
Transport > Adjacent Node.)
RMV ADJNODE: ANI=1017;
//Remove an Abis adjacent node.
Step 4 Run the BSC MML command RMV BTS to remove the GBTS. (CME: Base Station >
GSM> Right-click a site > Delete Site.)
RMV BTS: IDTYPE=BYID, BTSID=10;
Step 5 Execute the configuration scripts that are backed up before reconstruction. (CME: Script
Executor > Project > Load Project > Upload Project > Activate Project.)
----End

based Co-Transmission Through Backplane
Interconnection on the Separate-MPT LG/TG/MG
through backplane interconnection on the separate-MPT LG multimode base station side. In
this example, a GTMUb is used as the main control board of the GSM base station. The GSM
base stations in this scenario can only be GBTSs.
7.14.1 Requirements

SingleRAN


board panel on a GBTS to main-control-board-based IP co-transmission through backplane
interconnection on the separate-MPT LG multimode base station side.

SingleRAN
panel on a GBTS to main-control-board-based IP co-transmission through backplane
interconnection on the separate-MPT LG multimode base station side

BSC

the BSC

the eNodeB

SingleRAN

CME


of the eNodeB plane IP address.
and is configured on the
main control board.

OM channel

SCTP link

IP path

control board.
ESN of the GBTS abcdefghijklmn -

reconstruction.
– Run the BSC MML command DSP BTSVER to check the software version for a
GBTS.
– Check whether the main control board of the GBTS is a GTMUb/GTMUc. If not,
get a GTMUb/GTMUc ready. A GTMUb is used as an example in this scenario.
– Get an LMPT/UMPT_L ready.
station.

SingleRAN
3. Back up data.
Main View> Right-click a site >Export MML for Creating BTS.)
– For details about reconfigurations on the eNodeB side, see Reconfiguration on the
eNodeB Side.
Side (GBTS and BSC)" in section 7.8 Main-Control-Board-based Co-
Transmission Through Backplane Interconnection on the Separate-MPT
LG/TG/MG Multimode Base Station Side in IP over FE/GE Mode.
– For details about rollback scripts on the eNodeB side, see Rollback on the LTE
Side.
– For details about rollback scripts on the GBTS side, see Rollback on the GSM
Side.
6. Prepare for automatic deployment.
– If the USB + U2000 based deployment is to be applied, prepare a commissioning
USB flash drive for the reconstructed GL multimode base station, and prepare
another commissioning USB flash drive for the GBTS before the reconstruction.
The second USB flash drive is used for the automatic deployment in case that the
reconstruction fails.
– If the U2000-based deployment is to be applied, upload the configuration file for
the eNodeB to the U2000, and enable the DHCP relay function for the router that is
connected to the eNodeB.
NOTE
GBTS services are interrupted when steps 2 to 5 are performed. Before performing the following
steps, power off the GTMUb, and power it on after the eNodeB is deployed. This is because the IP
rehoming scripts take effect only after the GBTS resets. In addition, the IP rehoming scripts are
effective within specified time.
2. Remove the GTMUb and install the LMPT/UMPT_L at the site. Connect the
transmission cable to the planned port on the LMPT/UMPT_L.
3. Deactivate the GBTS on the BSC and prepare for scripts for GBTS reconstruction to
4. Perform automatic eNodeB deployment. For details about automatic deployment, see
3900 Series Base Station Commissioning Guide.

SingleRAN
5. Install and power on the GTMUb, and wait for GBTS deployment.
Step 3 Verify services after reconstruction. For details, see section 7.8.6 Activation Observation.

Rollback.
----End
7.14.4 Precautions
None
Reconfiguration on the eNodeB Side

For details, see Initial Configuration on the LTE Side in section 7.8 Main-Control-Board-
based Co-Transmission Through Backplane Interconnection on the Separate-MPT
LG/TG/MG Multimode Base Station Side in IP over FE/GE Mode.

Step 1 Run the BSC MML command IMP BTSIPPARA to import the communication IP address of
the GBTS.
IMP BTSIPPARA: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, IPPHYTRANSTYPE=IP_OVER_FE/GE,
BTSCOMTYPE=LOGICIP, BTSIP="10.35.35.188", BSCIP="10.10.10.10";
Step 2 Run the BSC MML command IMP BTSDEVIP to import the device IP address of the
GBTS.
IMP BTSDEVIP: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, PT=LOOPINTERFACE, PN=0, CN=0,
SRN=0, SN=6, IPIDX=0, IP="10.35.35.188", MASK="255.255.255.0";
Step 3 Run the BSC MML command IMP BTSTUNNEL to import the configuration of a tunnel
from the GTMUb to the LMPT/UMPT_L.
IMP BTSTUNNEL: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, SRCCN=0, SRCSRN=0, SRCSN=6,
TN=1, DSTCN=0, DSTSRN=0, DSTSN=7;
Step 4 Run the BSC MML command IMP BTSIPRT to import the configuration of a route to the
tunnel from the GBTS to the BSC.
IFNO=1;
----End

SingleRAN
7.14.6 Rollback
Rollback on the LTE Side

Remove the eNodeB on the CME. (CME: Base Station > LTE > Right-click a site >
Delete.)

Path.)
//Remove the IP path between the BTS and the BSC.
Step 4 Run the BSC MML command RMV BTS to remove the GBTS. (CME: Base Station > GSM
> Right-click a site > Delete Site.)
Executor > Project > Load Project > Activate Project.)
----End

based Co-Transmission Through Backplane
Base Station Side
through backplane interconnection on the separate-MPT UG multimode base station side. In
this example, a GTMUb is used as the main control board of the GSM base station. The GSM
base stations in this scenario can only be GBTSs.
7.15.1 Requirements

SingleRAN


board panel on a GBTS to main-control-board-based IP co-transmission through backplane
interconnection on the separate-MPT UG multimode base station side.

SingleRAN
panel on a GBTS to main-control-board-based IP co-transmission through backplane

Device IP address of the 10.10.10.10/32 The DHCP relay function is

BSC enabled on the UMTS side.
The IP address of the DHCP
the BSC.

the BSC

the RNC

SingleRAN

the NodeB

NodeB IP address. This is a logical
main control board.

logical IP address
control board.
Port IP address of the 10.20.20.188/24 UMTS: device IP address

UMPT_U of the NodeB during configuration on the
CME

RNC

the OM channel

main control board.
GBTS ESN abcdefghijklmn -

reconstruction.
GBTS. Multimode base stations of V100R007C00 and later support IP-based co-
transmission through backplane interconnection.
– Check whether the main control board of the GBTS is a GTMUb/GTMUc. If not,
get a GTMUb/GTMUc ready. A GTMUb is used as an example in this scenario.

SingleRAN
– Get a UMPT_U ready.

station.
3. Back up data.
Main View > Right-click a site > Export MML for Creating BTS)
– For details about reconfigurations on the UMTS side, see Reconfiguration on the
UMTS Side.
Side (GBTS and BSC) in section 7.9 Main-Control-Board-based Co-
Transmission Through Backplane Interconnection on the Separate-MPT
UG Multimode Base Station Side in IP over FE/GE Mode.
Side.
– If the USB+U2000 based deployment is to be applied, prepare a commissioning
USB flash drive for the reconstructed UG multimode base station, and prepare
another commissioning USB flash drive for the GBTS before the reconstruction.
The second USB flash drive is used for the automatic deployment in case that the
reconstruction fails.
– If the U2000-based deployment is to be applied, upload the configuration file for
the NodeB to the U2000, and enable the DHCP relay function for the router that is
connected to the NodeB.

NOTE
GBTS services are interrupted when steps 2 to 5 are performed. Before performing the following
steps, power off the GTMUb, and power on it after the NodeB is deployed. This is because the IP
rehoming scripts take effect only after the GBTS resets. In addition, the IP rehoming scripts are
effective within specified time.
2. Remove the GTMUb and install the UMPT_U at the site. Connect the transmission cable
to the planned port on the UMPT_U.

SingleRAN
3. Deactivate the GBTS on the BSC and prepare for scripts for BTS reconstruction to
4. Perform automatic NodeB deployment. For details about automatic deployment, see
3900 Series Base Station Commissioning Guide.
5. Install and power on the GTMUb, and wait for GBTS deployment.

Rollback.
----End
7.15.4 Precautions
None

For details, see Initial Configuration on the UMTS Side in section 7.9 Main-Control-
Board-based Co-Transmission Through Backplane Interconnection on the Separate-
MPT UG Multimode Base Station Side in IP over FE/GE Mode.

the GBTS.
GBTS.
from the GTMU to the UMPT_U.
IFNO=0;
----End

SingleRAN
7.15.6 Rollback
Remove the NodeB on the CME. (CME: Base Station > UMTS > Right-click a
site>Delete.)

Transmission View> GSM > Abis > Abis Configuration Express > IP Transport > IP
Path.)
> Right-click a site> Delete Site.)
----End
7.16 Reconstruction from Main-Control-Board-based IP

Co-Transmission Through Panel Interconnection to
UTRPc-based Co-Transmission Through Backplane
This section describes how to reconstruct the transmission mode from main-control-board-
based IP co-transmission through panel interconnection to UTRPc-based IP co-transmission
through backplane interconnection on the separate-MPT UG multimode base station side in IP
over FE/GE mode. In this example, a GTMUb is used as the main control board of the GSM
base station. The GSM base stations in this scenario can only be GBTSs.
7.16.1 Requirements
Figure 7-28 shows the network topologies before and after reconstruction. After
reconstruction, the UTRPc is managed by the NodeB.

SingleRAN


Figure 7-29 shows an example of reconstruction from main-control-board-based IP co-
transmission through panel interconnection to UTRPc-based IP co-transmission through
backplane interconnection on the separate-MPT UG multimode base station side.

SingleRAN
Figure 7-29 Example of reconstruction from main-control-board-based IP co-transmission

through panel interconnection to UTRPc-based IP co-transmission through backplane

Device IP address of 10.10.10.10/32 The DHCP relay function is enabled on the

the BSC UMTS side. The IP address of the DHCP
server is 10.10.10.10, which is the device IP
address of the BSC.

BSC

SingleRAN
Device IP address of 10.15.15.15/24 -

the RNC

RNC
Port IP address of the 10.60.60.60/24 UMTS: peer IP address for the OM channel
U2000
IP address of the port 10.21.21.254/24 -

on the router that is
connected to the BSC

connected to the RNC

connected to the NodeB
IP address of FE port 1 10.20.20.188/24 -

on the UTRPc of the
NodeB
OM IP address of the 10.30.30.1/24 UMTS: management plane IP address. This

NodeB is a logical IP address configured on the
main control board.
Signaling/service IP 10.32.32.1/24 UMTS: control plane/user plane IP address.

address of the NodeB This is a logical IP address configured on
IP address of the GBTS 10.35.35.188/24 GSM: communication IP address of the

GBTS. This is a logical IP address
configured on the main control board.
reconstruction.
GBTS. Multimode base stations of V100R007C00 and later support UTRPc boards.

SingleRAN

– Get a GTMUb ready if the main control board of the GBTS is not a GTMUb.
– Get a UTRPc ready.
station and the required license file.
3. Back up data.
Main View > Right-click a site > Export MML for Creating BTS)
– Run the NodeB MML command BKP CFGFILE to back up the NodeB
configuration file before reconstruction. The configuration file is in .xml format.
Then, run the NodeB MML command ULD CFGFILE to upload the configuration
file to the local PC. (CME: UMTS Application > Physical NodeB Management >
Export Configuration Files)
UMTS Side.
Side (GBTS and BSC) in section 7.10 UTRPc-based Co-Transmission
Through Backplane Interconnection on the Separate-MPT UG Multimode
Base Station Side in IP over FE/GE Mode.
– For details about rollback scripts on the UMTS side, see Rollback on the GSM
Side.
– For details about rollback scripts on the GSM side, see Rollback on the UMTS
Side"
USB flash drive for the reconstructed UG multimode base station, and prepare
another commissioning USB flash drive for the UG multimode base station before
the reconstruction. The second USB flash drive is used for the automatic
deployment in case that the reconstruction fails.
– If the U2000-based deployment is to be applied, upload the new configuration file
for the NodeB to the U2000 and enable the DHCP relay function for the router that
is connected to the NodeB.
If the software version of the multimode base station does not meet the reconstruction
requirements, upgrade the software before reconstruction.

SingleRAN
1. Run the NodeB MML command ADD BRD to add a UTRPc.

2. Insert the UTRPc into its slot in the NodeB. Then, the UTRPc software is upgraded
automatically. Run the NodeB MML command DSP BRD to check whether the UTRPc
is running properly and run the NodeB MML command DSP BRDVER to check
whether the UTRPc software version is correct.
DSP BRD: CN=0, SRN=0, SN=4;
DSP BRDVER: CN=0, SRN=0, SN=4;
3. Download the configuration file in .xml format from the U2000 to the NodeB by
choosing Software > NE File Transfer > From OSS Client to NE on the U2000.
NOTE
GBTS and NodeB services are interrupted when steps 5 to 9 are performed. Before performing the
following steps, power off the GTMUb, and power it on after the NodeB is deployed. This is
because the IP rehoming scripts take effect only after the GBTS resets. In addition, the IP
rehoming scripts are effective within specified time.
5. Run the U2000 MML command SET CFGFILEENB to activate the NodeB
configuration file.
SET CFGFILEENB: FLAG=ENABLE, RSTMODE=IMMEDIATELY;
6. Instruct field engineers to remove the Ethernet cable from the WMPT/UMPT_U and
connect the cable to the port on the UTRPc. Then, remove the GTMUb.
7. Deactivate the GBTS on the BSC, and execute the scripts for reconstruction to reactivate
the GBTS.
8. Check that the NodeB maintenance links are normal on the U2000. Install and power on
the GTMUb of the GBTS to make the GBTS IP rehoming scripts take effect.
9. Wait for 10 minutes, and check that services processed on the GBTS and NodeB are
normal on the U2000.
Verify services after reconstruction. For details, see 7.10.6 Activation Observation.
Rollback.
----End
7.16.4 Precautions
None
For details, see Initial Configuration on the UMTS Side in section 7.10 UTRPc-based Co-
Transmission Through Backplane Interconnection on the Separate-MPT UG Multimode
Base Station Side in IP over FE/GE Mode.

Perform the following steps to generate an IP rehoming script:

SingleRAN
the GBTS.
GBTS.
from the GTMUb to the UTRPc.
IFNO=0;
----End
7.16.6 Rollback

Step 1 Run the BSC MML command DEA BTS to deactivate the GBTS.
Step 2 Run the BSC MML command RMV IPPATH to remove an IP path.
Step 3 Run the BSC MML command RMV ADJNODE to remove an adjacent node.
Step 4 Run the BSC MML command RMV BTS to remove the GBTS.
Step 5 Execute the configuration scripts that are backed up before reconstruction.
----End

If the transmission link between the NodeB and the U2000 is normal, download the backed up
original configuration files from the U2000 to the NodeB.
If the transmission link between the NodeB and the U2000 is disconnected, the NodeB
performs automatic deployment by using the backed up original configuration files.

SingleRAN
7.17 Reconstruction from UTRPc-Backplane-

Interconnection Co-Transmission on the Separate-MPT
UG Multimode Base Station Side to UTRPc-Backplane-
UG+L/UG+T Multimode Base Station Side in IP over
FE/GE Mode
This section describes how to reconstruct the transmission mode from UTRPc-based IP co-
transmission through backplane interconnection on the UG multimode base station side to
UTRPc-based IP co-transmission through backplane interconnection on the UG+L multimode
base station side.
7.17.1 Requirements

SingleRAN


Figure 7-31 shows an example of reconstruction from UTRPc-based IP co-transmission
through backplane interconnection on the separate-MPT UG multimode base station side to
UTRPc-based IP co-transmission through backplane interconnection on the separate-MPT
UG+L multimode base station side.

SingleRAN
Figure 7-31 Example of reconstruction from UTRPc-based IP co-transmission through

backplane interconnection on the separate-MPT UG multimode base station side to UTRPc-
based IP co-transmission through backplane interconnection on the separate-MPT UG+L
multimode base station side

SingleRAN


BSC

the BSC

RNC

the RNC

SCTP link

IP path

OM channel

the UTRPc of the NodeB

CME

control board.

IP address and is configured
on the main control board.


SingleRAN

control board.

control board.

ESN of the GBTS abcdefghijklmn For the GBTS, the ESN

need to be planned.
reconstruction.
GBTS. Run the eGBTS MML command LST VER to check the software version
for an eGBTS. Multimode base stations of V100R007C00 and later support UTRPc
boards.
– Get the UCIU, optical modules, and eNodeB hardware ready. The main control
board for the eNodeB is UMPT_L. Optical modules on the UCIU and UMPT_L
must meet specifications. For details about the specifications of optical modules,
see "BBU Interconnection" in the MBTS Initial Configuration(GUL).
station.
3. Back up data.
– Back up GBTS/eGBTS data configurations before reconstruction on the CME.
(CME: Main View > Right-click a site > Export MML for Creating BTS)

SingleRAN
Export Configuration Files)
– For details about reconfiguration on the GSM side, see Reconfiguration on the
GSM Side (GBTS and BSC).
UMTS Side.
– For details about reconfigurations on the LTE side, see Reconfiguration on the
LTE Side.
Side.
– For details about rollback scripts on the LTE side, see Rollback on the LTE Side.
USB flash drive for the reconstructed UGL multimode base station, and prepare
– If the U2000-based deployment is to be applied, upload the following files to the
U2000 and enable the DHCP relay function for the router that is connected to the
NodeB:
n New configuration files for the NodeB and eNodeB
n NodeB configuration file backed up before the reconstruction
Step 2 Reconstruct hardware. For details, see section 7.17.6 Hardware Adjustment.
Step 3 Modify data configurations.

l Execute reconstruction scripts for the NodeB on the U2000 side.
Step 4 Perform automatic eNodeB deployment. For details, see 3900 Series Base Station
Commissioning Guide.
Step 5 Verify services after reconstruction. For details, see section 7.11.6 Activation Observation in
7.11 UTRPc-based Co-Transmission Through Backplane Interconnection on the
Separate-MPT UG+L/UG+T/UG+M Multimode Base Station Side in IP over FE/GE
Mode.
Rollback.

SingleRAN
----End
7.17.4 Precautions
None
Reconfiguration on the GSM Side (GBTS and BSC)

Step 1 Run the ADD BTSBRD command to add a UCIU.

Step 2 Run the BSC MML command ADD BTSCTRLLNK to add a BBU interconnection control
link between GSM and LTE.
UPSN=0, UPPT=0;
of subrack 0.
----End
Reconfiguration on the GSM Side (eGBTS and BSC)

//Add a UCIU board to slot 0.
link.
of subrack 0.
----End


SingleRAN
Step 1 Run the ADD CTRLLNK command to add a BBU interconnection control link.
Step 2 Run the NodeB MML command ADD TUNNEL to add a tunnel from the UTRPc to the
eNodeB.
ADD TUNNEL: SCN=0, SSRN=0, SSN=4, TUNNELID=1, DCN=0, DSRN=1, DSN=7, TUNNELTYPE=DL;
Step 3 Run the NodeB MML command ADD IPRT to add a route.
1. Add a route from the UTRPc to the OM IP address of the eNodeB, and add a route from
the UTRPc to the signaling/service IP address of the eNodeB.
ADD IPRT: RTIDX=0, CN=0, SRN=0, SN=4, SBT=BACK_BOARD, DSTIP="10.31.31.188",
2. Add a next-hop route from the UTRPc to the MME.

ADD IPRT: RTIDX=2, CN=0, SRN=0, SN=4, SBT=ETH_COVERBOARD,
DSTIP="10.40.40.40", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="10.30.30.1";
3. Add a next-hop route from the UTRPc to the S-GW.

ADD IPRT: RTIDX=3, CN=0, SRN=0, SN=4, SBT=ETH_COVERBOARD,
DSTIP="10.50.50.50", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="10.30.30.1";
relay.
Step 5 Run the NodeB MML command ADD DHCPSVRIP to add the IP address of the DHCP
server.
The eNodeB uses the U2000 as the DHCP server. Therefore, the IP address of the U2000
needs to be added to the DHCP server IP address list so that the U2000 can forward DHCP
packets for the eNodeB.
----End
Reconfiguration on the LTE Side


NOTE
In this scenario, the eNodeB uses the CI interface for communication. Therefore, Ethernet ports do not
need to be configured.

SingleRAN
Step 1 Run the eNodeB MML command ADD CTRLLNK to add a control link between BBU
subracks.
//Add a control link from the board in slot 7 of BBU subrack 1 to the board in
slot 0 of BBU subrack 0. The number of the BBU subrack accommodating the eNodeB
must be different from the number of the BBU subrack accommodating the GBTS/eGBTS
and NodeB. This section assumes that the number of the BBU subrack accommodating
the eNodeB is 1.
Step 2 Run the eNodeB MML command ADD TUNNEL to add a tunnel from the LMPT/UMPT_L
to the UTRPc controlled by the NodeB.
ADD TUNNEL: SSRN=1, SSN=7, DSN=4, TUNNELTYPE=UL;
NOTE
The parameter settings in the following configuration steps described in 3900 Series Base Station Initial
Configuration Guide are modified according to the co-transmission network plan.
Step 3 Run the eNodeB MML command ADD DEVIP to set the IP address of the eNodeB. In this
step, set Port Type to LOOPINT.
ADD DEVIP: CN=0, SRN=1, SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=0,
IP="10.33.33.188", MASK="255.255.255.0";
//Add a signaling/service IP address for the eNodeB.
Step 4 Run the eNodeB MML command ADD IPRT to add a route to a tunnel. In this step, set
Route Type to IF, Port Type to TUNNEL, and Port No. to the number (that is, 0) of the
tunnel on the backplane of the eNodeB.
1. Add a route from the eNodeB to the MME.
ADD IPRT: RTIDX=0, CN=0, SRN=1, SN=7, SBT= BACK_BOARD, DSTIP="10.40.40.40",
DSTMASK="255.255.255.255 ", RTTYPE=IF, IFT=TUNNEL, IFNO=0;
2. Add a route from the eNodeB to the U2000.

3. Add a route from the eNodeB to the S-GW.

Step 5 Run the eNodeB MML command ADD OMCH to add an OM channel. In this step, set
Subboard Type to BACK_BOARD, and do not bind the OM channel with any route.
group.
//Set parameters for a transmission resource group. In this step, set SBT to
BACK_BOARD and PT to TUNNEL.
//Add an IP path. In this step, set SBT to BACK_BOARD and PT to TUNNEL.
----End

l Insert a UCIU into the original BBU subrack.

SingleRAN
l Install the eNodeB. The main control board for the eNodeB is UMPT_L.
l Insert optical modules into the UCIU and UMPT_L. Connect optical cables between the
UCIU and UMPT_L.
For details, see Installation Guide of the 3900 Series Base Station Product Documentation.
7.17.7 Rollback
Step 1 Run the RMV BTSCTRLLNK command to remove the BBU interconnection control link
between GSM and LTE.
RMV BTSCTRLLNK: IDTYPE=BYID, BTSID=0, LN=0;
//Remove the BBU interconnection control link between slot 7 of subrack 1 and
Step 2 Run the RMV BTSBRD command to remove the UCIU.

RMV BTSBRD: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=0;
//Remove the UCIU in slot 0.
----End

Remove the eNodeB on the CME. (CME: Base Station > LTE > Right-click a site > Delete)

Step 1 Run the NodeB MML command RMV IPRT to remove routes.
1. Remove the tunnel routes from the UTRPc to the eNodeB OM channel IP address and
signaling/service IP address.
RMV IPRT: RTIDX=0;
RMV IPRT: RTIDX=1;
2. Remove a next-hop route from the UTRPc to the MME.
RMV IPRT: RTIDX=2;
3. Remove a next-hop route from the UTRPc to the S-GW.
RMV IPRT: RTIDX=3;
Step 2 Run the NodeB MML command RMV TUNNEL to remove a tunnel from the UTRPc to the
eNodeB.
RMV TUNNEL: SCN=0, SSRN=0, SSN=4, TUNNELID=1;
----End
7.18 Reconstruction from Main-Control-Board-based Co-

Transmission Through Panel Interconnection on the UG
Multimode Base Station Side to UTRPc-based Co-
Transmission Through Backplane Interconnection on the
Separate-MPT UG+L/UG+T Multimode Base Station Side
based IP co-transmission through panel interconnection on the separate-MPT UG multimode

SingleRAN
base station side to UTRPc-based IP co-transmission through backplane interconnection on

the separate-MPT UG+L multimode base station side. In this example, a GTMUb is used as
the main control board of the GSM base station. The GSM base stations in this scenario can
only be GBTSs.
7.18.1 Requirements



SingleRAN
side to UTRPc-based IP co-transmission through backplane interconnection on the separate-

MPT UG+L multimode base station side.

through panel interconnection on the separate-MPT UG multimode base station side to
UTRPc-based IP co-transmission through backplane interconnection on the separate-MPT
UG+L multimode base station side

SingleRAN


BSC

RNC

U2000

the BSC

the RNC
IP address of the port on the 10.20.20.1/24 When DHCP relay is

router that is connected to enabled for the NodeB, the
the NodeB IP address of the DHCP
the BSC.

transmission port.


control board.

main control board.

SingleRAN


configured on the eNodeB
main control board.

SCTP link

IP path

reconstruction.
– Run the BSC MML command DSP BTSVER or NodeB MML command LST
VER to check the software version for a GBTS or NodeB. Multimode base stations
of V100R007C00 and later support UTRPc boards.
– Get the UTRPc, UCIU, optical modules, and eNodeB hardware ready. The main
control board for the eNodeB is UMPT_L. Optical modules on the UCIU and
UMPT_L must meet specifications. For details about the specifications of optical
modules, see "BBU Cascading" in 3900 Series Base Station Initial Configuration
Guide.
station.
3. Back up data.

SingleRAN
Export Configuration Files.)
Side (GBTS and BSC) in section 7.11 UTRPc-based Co-Transmission
Through Backplane Interconnection on the Separate-MPT UG+L/UG
+T/UG+M Multimode Base Station Side in IP over FE/GE Mode.
UMTS Side.
– For details about reconfigurations on the eNodeB side, see Reconfiguration on the
LTE Side.
Side.
– For details about rollback scripts on the eNodeB side, see Rollback on the LTE
Side.
USB flash drive for the reconstructed UGL multimode base station, and prepare
NodeB:

1. Run the ADD BRD command to add a UTRPc on the NodeB side.
2. Run the GBTS MML command ADD BTSBRD to add a UCIU.

3. Insert the UCIU and UTRPc into appropriate slots on the NodeB. The UCIU and UTRPc
software is upgraded automatically. Then, run the DSP BRD command to check whether
the UTRPc is operating normally, run the DSP BRDVER command to check whether
the UTRPc is of the correct version, and run the DSP BTSBRD command to check
whether the UCIU is operating normally and of the correct version.

SingleRAN
DSP BRD: CN=0, SRN=0, SN=4;

DSP BRDVER: CN=0, SRN=0, SN=4;
DSP BTSBRD: CN=0, SRN=0, SN=0;
4. Download the NodeB configuration file in .xml format from the U2000 to the NodeB by
choosing Software > NE File Transfer > From OSS Client to NE.
6. Get the eNodeB configuration file and the eNodeB deployment list ready on the U2000.
NOTE
GBTS and NodeB services are interrupted when steps 5 to 10 are performed. Before performing
the following steps, power off the GTMUb, and power it on after the NodeB is deployed. This is
configuration file.
8. Instruct field engineers to remove the GTMUb, and remove the Ethernet cable from the
WMPT/UMPT_U and connect the cable to the port on the UTRPc.
the GBTS.
10. Check that the NodeB maintenance links are normal on the U2000. After the NodeB is
automatically deployed, install and power on the GTMUb of the GBTS to make the
GBTS rehoming scripts take effect.
12. Install the eNodeB and connect the cable between the UMPT_L and the UCIU on the
eNodeB. Then, power on the BBU subrack of the eNodeB to deploy the eNodeB.
Step 4 Perform the rollback operation if reconstruction fails.

Rollback.
----End
7.18.4 Precautions
None
For details, see Initial Configuration on the UMTS Side in section 7.11 UTRPc-based Co-
Transmission Through Backplane Interconnection on the Separate-MPT UG+L/UG

IP rehoming scripts:

SingleRAN
the GBTS.
GBTS.
from the GTMUb to the UTRPc.
IFNO=0;
----End

For details, see Initial Configuration on the LTE Side in section 7.11 UTRPc-based Co-
Transmission Through Backplane Interconnection on the Separate-MPT UG+L/UG
7.18.6 Rollback

Path.)
Controller > Transmission View > GSM > Abis> Abis Configuration Express > IP
> Right-click a site > Delete Site.)

SingleRAN
Executor > Project>Load Project > Activate Project.)
----End


Remove the eNodeB on the CME. (CME: Base Station > LTE > Right-click a site > Delete.)
7.19 Reconstruction from Main-Control-Board-Panel-

UG Multimode Base Station Side to Main-Control-Board-
Panel-Interconnection Co-Transmission on the Separate-
MPT UG+L/UG+T Multimode Base Station Side
based IP co-transmission through panel interconnection on the UG multimode base station
side to main-control-board-based IP co-transmission through backplane interconnection on
the UGL multimode base station side. In this example, a GTMUb is used as the main control
board of the GSM base station. The GSM base stations in this scenario can only be GBTSs.
7.19.1 Requirements
Figure 7-34 shows the network topologies before and after reconstruction. After the
reconstruction, UMPT+UMPT interconnection is used.

SingleRAN


transmission through panel interconnection on the UG multimode base station side to main-
control-board-based IP co-transmission through backplane interconnection on the UG+L
multimode base station side.

SingleRAN

through panel interconnection on the separate-MPT UG multimode base station side to main-
control-board-based IP co-transmission through backplane interconnection on the separate-
MPT UGL multimode base station side


BSC

SingleRAN

RNC
Port IP address of the 10.60.60.60/24 UMTS/LTE: peer IP address

U2000 of the OMCH

the BSC

the RNC
IP address of the port on the 10.20.20.1/24 When DHCP relay is

router that is connected to enabled for the NodeB, the
the NodeB IP address of the DHCP
the BSC.

the UMPT_U of the NodeB during configuration on the
transmission port.


control board.

main control board.


SingleRAN

configured on the eNodeB
main control board.

SCTP link

IP path
reconstruction.
– Run the BSC MML command DSP BTSVER or NodeB MML command LST
VER to check the software version for a GBTS or NodeB. Multimode base stations
of V100R007C00 and later support IP-based co-transmission through backplane
interconnection.
– Get the NodeB and eNodeB hardware ready. The main control board for the NodeB
is UMPT_U, and the main control board for the eNodeB is UMPT_L. Optical
modules on the UMPT_U and UMPT_L must meet specifications. For details about
the specifications of optical modules, see "BBU Cascading" in 3900 Series Base
Station Initial Configuration Guide.
station.
3. Back up data.
Export Configuration Files.)

SingleRAN

n Scripts for reconstruction. For details, see "Initial Configuration on the GSM
Side" in section "Main-Control-Board-based Co-Transmission Through
Backplane Interconnection on the Separate-MPT UG+L/UG+T Multimode
Base Station Side.".
UMTS Side.
– For details about reconfigurations on the LTE side, see Reconfiguration on the
LTE Side.
Side.
– For details about rollback scripts on the LTE side, see Rollback on the LTE Side.
USB flash drive for the reconstructed GUL multimode base station, and prepare
another commissioning USB flash drive for the GU multimode base station before
NodeB:
If the multimode base station software version does not meet the reconstruction requirements,
upgrade the software before reconstruction.
1. Replace the WMPT with a UMPT_U, and connect the transmission cable to the planned
port on the UMPT_U.
2. Download the NodeB configuration file in .xml format from the U2000 to the NodeB by
choosing Software > NE File Transfer > From OSS Client to NE.
4. Get the eNodeB configuration file and the eNodeB deployment list ready on the U2000.
NOTE
GBTS and NodeB services are interrupted when steps 5 to 10 are performed. Before performing
the following steps, power off the GTMUb, and power it on after the NodeB is deployed. This is
configuration file.

SingleRAN
6. Instruct field engineers to remove the GTMUb.

the GBTS.
8. Check that the NodeB maintenance links are normal on the U2000. After the NodeB is
automatically deployed, install and power on the GTMUb of the GBTS to make the
GBTS rehoming scripts take effect.
10. Install the eNodeB and connect the cable between the UMPT_L and the UMPT_U on the
eNodeB. Then, power on the BBU subrack of the eNodeB to deploy the eNodeB.
Rollback.
----End
7.19.4 Precautions
None
For details, see "Initial Configuration on the UMTS Side" in section "Main-Control-Board-
based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG+L/UG
+T Multimode Base Station Side in IP over FE/GE Mode."

IP rehoming scripts:
the GBTS.
GBTS.
from the GTMUb to the UMPT_U.

SingleRAN

IFNO=0;
----End

For details, see "Initial Configuration on the LTE Side" in section "Main-Control-Board-based
Co-Transmission Through Backplane Interconnection on the Separate-MPT UG+L/UG+T
Multimode Base Station Side in IP over FE/GE Mode."
7.19.6 Rollback

Path.)
//Remove the IP path between the BTS and the BSC.
>Right-click a site > Delete Site.)
----End


Remove the eNodeB on the CME. (CME: Base Station > LTE > Right-click a site >Delete.)

SingleRAN

Panel Interconnection on the Separate-MPT UG
Multimode Base Station Side in IP over E1/T1 Mode
7.20.1 Requirements
Figure 7-36 shows the main-control-board-based co-transmission through panel
interconnection on the separate-MPT UG multimode base station side in IP over E1/T1
mode. In this scenario, an outbound E1/T1 port on the WMPT of the NodeB serves as
the co-transmission port of the UG multimode base station and is connected to the
MBSC. The GTMU of the GBTS is interconnected to the WMPT of the NodeB through
FE ports. The GSM base stations in this scenario can only be GBTSs.
Figure 7-36 Main-control-board-based co-transmission through panel interconnection on

the separate-MPT UG multimode base station side in IP over E1/T1 mode


Figure 7-37 shows an example of network topology for main-control-board-based co-
side in IP over E1/T1 mode.

SingleRAN
Figure 7-37 Example of network topology for main-control-board-based co-transmission

through panel interconnection on the separate-MPT UG multimode base station side in IP
over E1/T1 mode

BSC

RNC

the BSC

the RNC

NodeB to the GBTS.)

CME

the NodeB

SingleRAN

the GBTS (FE port 0 is used during configuration on the
for interconnecting the CME
GBTS to the NodeB.)
NOTE
segment.
the two ports used for interconnecting the NodeB to the GBTS.
7.20.3 Precautions
None

When main-control-board-based IP over E1/T1 co-transmission is implemented through panel
interconnection, no additional hardware is required, but the Ethernet cables between main
control board panels are required. Table 7-22 describes the panel interconnection modes.
Table 7-22 Main control board panel interconnection modes

UG Mode 1: An outbound FE optical port on the

WMPT is connected to the GTMU.
For example, the outbound E1/T1 port on
the WMPT is connected to the transmission
device, and the optical port (FE 1) on the
WMPT is connected to the optical port (FE
1) on the GTMU.
Mode 2: An outbound FE electrical port on
the WMPT is connected to the GTMU.
For example, the outbound E1/T1 port on
the WMPT is connected to the transmission
device, and the electrical port (FE 0) on the
WMPT is connected to the electrical port
(FE 0) on the GTMU.

Initial Configuration on the GSM Side

SingleRAN
step, set the destination IP address of one route to the OM channel IP address of the NodeB
and that of the other route to the lower-level transmission port of the NodeB. The BSC MML
----End


addresses of two ports used for interconnecting the NodeB to the GBTS are on the same
network segment.
MASK="255.255.255.0";
GTMU.
Step 3 Run the NodeB MML command ADD IPRT to add an uplink route from the GBTS to the
BSC through the NodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP to the IP
Step 4 (Optional) Add a downlink route from the BSC to the GBTS through the NodeB.
The downlink route is required only if the logical IP address is used by the GBTS. If the
physical port IP address is used by the GBTS and the IP addresses of the panel

SingleRAN
interconnection ports on the NodeB and the GBTS are on the same network segment as the
port IP address of the GBTS, the downlink route from the NodeB to the GBTS is not required.
relay.
When co-transmission is enabled for the GBTS and NodeB, if the GBTS is deployed using
DHCP, the NodeB needs to work as the relay. Therefore, DHCP relay needs to be enabled for
the NodeB.
DHCP server.
DHCP, the NodeB needs to work as the relay. Therefore, the IP address of the DHCP server
needs to be added on the NodeB. For the GBTS, the IP address of the DHCP server is the IP
address of the BSC. If the data plan shows that the IP-based Abis interface board on the BSC
side uses the device IP address, set the IP address of the DHCP server to the device IP
address.
----End

UMTS Side
BSC/RNC is normal:
----End

SingleRAN
GSM Side
After the configuration file is delivered to the GBTS and activated, perform the following step
on the BSC side to verify whether the transmission link between the BSC and the GBTS is
normal:
GTMU on the GBTS and the BSC. If the IP address can be pinged, the IP link is normal.
----End
7.21 UTRP4-based Co-Transmission Through Panel

Base Station Side in IP over E1/T1 Mode
7.21.1 Requirements
Figure 7-38 shows the UTRP4-based co-transmission through panel interconnection on
the separate-MPT UG multimode base station side in IP over E1/T1 mode. In this
scenario, an outbound E1/T1 port on the UTRP4 of the NodeB serves as the co-
transmission port of the UG multimode base station and is connected to the MBSC. The
GTMU of the GBTS is interconnected to the WMPT of the NodeB through FE ports.
The GSM base stations in this scenario can only be GBTSs.
Figure 7-38 UTRP4-based co-transmission through panel interconnection on the

separate-MPT UG multimode base station side in IP over E1/T1 mode


SingleRAN

Figure 7-39 shows an example of network topology for UTRP4-based co-transmission
through panel interconnection on the separate-MPT UG multimode base station side in IP
over E1/T1 mode.
Figure 7-39 Example of network topology for UTRP4-based co-transmission through panel
interconnection on the separate-MPT UG dual-mode base station side in IP over E1/T1 mode

BSC

RNC

the BSC

the RNC

NodeB to the GBTS.)

SingleRAN
IP address of the E1 port on 10.20.20.188/24 UMTS: device IP address

CME

the NodeB

the GBTS (FE port 0 is used during configuration on the
for interconnecting the CME
GBTS to the NodeB.)
NOTE
segment.
the two ports used for interconnecting the NodeB to the GBTS.
7.21.3 Precautions
None

When UTRP4-based IP over E1/T1 co-transmission is implemented through panel
interconnection, additional UTRP4 hardware is required, and the Ethernet cables between the
WMPT and the GTMU are required. Table 7-24 describes the panel interconnection modes.

UG Mode 1: An outbound FE optical port on the WMPT is connected

to the GTMU.
For example, the outbound E1/T1 port on the UTRP4 of the NodeB
is connected to the transmission device, and the optical port (FE 1)
on the WMPT is connected to the optical port (FE 1) on the
GTMU.
Mode 2: An outbound FE electrical port on the WMPT is
connected to the GTMU.
For example, the outbound E1/T1 port on the UTRP4 of the NodeB
is connected to the transmission device, and the electrical port (FE
0) on the WMPT is connected to the electrical port (FE 0) on the
GTMU.

SingleRAN

step, set the destination IP address of one route to the OM channel IP address of the NodeB
and that of the other route to the lower-level transmission port of the NodeB. The BSC MML
----End

addresses of two ports used for interconnecting the NodeB to the GBTS are on the same
network segment.
MASK="255.255.255.0";
// Set the IP address of the Ethernet port (port 1 on board in slot 7) that is
GTMU.
Step 3 Run the NodeB MML command ADD IPRT to add an uplink route from the GBTS to the
BSC through the NodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP to the IP

SingleRAN
ADD IPRT: RTIDX=0, SN=4, SBT=E1_COVERBOARD, DSTIP="10.10.10.10",

Step 4 (Optional) Add a downlink route from the BSC to the GBTS through the NodeB.
The downlink route is required only if the logical IP address is used by the GBTS. If the
physical port IP address is used by the GBTS and the IP addresses of the panel
interconnection ports on the NodeB and the GBTS are on the same network segment as the
port IP address of the GBTS, the downlink route from the NodeB to the GBTS is not required.
relay.
DHCP, the NodeB needs to work as the relay. Therefore, DHCP relay needs to be enabled for
the NodeB.
DHCP server.
DHCP, the NodeB needs to work as the relay. Therefore, the IP address of the DHCP server
needs to be added on the NodeB. For the GBTS, the IP address of the DHCP server is the IP
address of the BSC. If the data plan shows that the IP-based Abis interface board on the BSC
side uses the device IP address, set the IP address of the DHCP server to the device IP
address.
----End

UMTS Side
BSC/RNC is normal:
----End

SingleRAN
GSM Side
After the configuration file is delivered to the GBTS and activated, perform the following step
on the BSC side to verify whether the transmission link between the BSC and the GBTS is
normal:
GTMU on the GBTS and the BSC. If the IP address can be pinged, the IP link is normal.
----End
7.22 GTMU-based TDM Co-Transmission on the Separate-

MPT GU Multimode Base Station Side
7.22.1 Requirements
Figure 7-40 shows the GTMU-based TDM co-transmission on the separate-MPT GU
multimode base station side. In this scenario, an E1/T1 port on the GTMU serves as the
co-transmission port of the separate-MPT GU multimode base station and is connected
to the BSC and RNC. The WMPT is interconnected to the GTMU through the
backplane. The GSM base stations in this scenario can only be GBTSs.
Figure 7-40 GTMU-based TDM co-transmission on the separate-MPT GU multimode

base station side

– WRFD-050302 Fractional ATM Function on Iub Interface
– WRFD-050411 Fractional IP Function on Iub Interface

Prepare the GU timeslot allocation. For example, allocate all the timeslots on E1 port 2 and
E1 port 3 on the GTMU shown in Figure 7-40 to the WMPT.

SingleRAN
7.22.3 Precautions
As shown in Figure 7-40, this scenario only supports the WMPT.

No additional hardware is required.

Step 1 Run the MML command ADD BTSCONNECT to add a connection between a GTMU port
and the NodeB. Set Dest Node Type to OTHER.
ADD BTSCONNECT: IDTYPE=BYID, BTSID=255, INPN=1, INCN=0, INSRN=0, INSN=6,
DESTNODE=OTHER;
Step 2 Run the MML command ADD BTSTOPCONFIG to configure the TOP switching
parameters.
l Set Port Subrack No. and Port Slot No. to the numbers of the subrack and slot where
the BTS port connected to the NodeB interface board is located. Set TOP Board
Subrack No. and TOP Board Slot No. to the numbers of the subrack and slot where the
NodeB interface board is located.
l Set Port Type to TOPEXTOUTPORT.
l Set TS Mask to the timeslot of the NodeB backplane.
ADD BTSTOPCONFIG: IDTYPE=BYID, BTSID=255, CN=0, SRN=0, SN=6, E1T1PORTNO=16,
TOPBOARDCN=0, TOPBOARDSRN=0, TOPBOARDSLOTNO=7, PORTTYPE=TOPEXTOUTPORT,
ORIPORT=2,
TSMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS1
2-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23
-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;
ADD BTSTOPCONFIG: IDTYPE=BYID, BTSID=255, CN=0, SRN=0, SN=6, E1T1PORTNO=17,
TOPBOARDCN=0, TOPBOARDSRN=0, TOPBOARDSLOTNO=7, PORTTYPE=TOPEXTOUTPORT,
ORIPORT=3,
TSMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS1
2-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23
-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;
NOTE
If E1 transmission resources on the NodeB side are shared by the BTS, set Port Type to
TOPEXTOUTPORT.
----End

Step 1 Run the MML command ADD BACKE1T1 to add a backplane E1/T1 link.
l Set Subrack No. and Slot No. to the numbers of the subrack and slot that house the Iub
interface board.
l Set Subboard Type to BACK_BOARD.
l Set Destination Slot No. to the number of the slot that houses the GTMU.
ADD BACKE1T1: SRN=0, SN=7, SBT=BACK_BOARD, DSTSN=6;

SingleRAN
NOTE
Similar to a common E1, the backplane E1 can be configured with the upper-layer bearer. It, however,
does not support the configuration of the operating work mode and loopback mode, and online and
offline tests. The upper-layer link bearer of the backplane E1 can be UNILNK/IMALNK/
FRAATMLNK/PPLNK/MPLNK. You need to configure the link bearer according to actual networking
mode.
----End

GSM Side
Run the MML command STR BTSE1T1TST to check whether the communication on the
E1/T1 port on the GTMU is normal.
STR BTSE1T1TST: IDTYPE=BYID, BTSID=100, CN=0, SRN=0, SN=6, PN=0, SW=OFF;
UMTS Side
Run the MML command STR E1T1ONLTST to check whether the communication on the
E1/T1 port on the WMPT is normal.
STR E1T1ONLTST: CN=0, SRN=0, SN=7, SBT=E1_COVERBOARD, PN=0, SW=ON;
7.23 Co-Transmission on the Co-MPT

GU/GL/UL/GT/UT/LT/GM/UM/LM/TM Multimode Base
Station Side in IP over FE/GE Mode
7.23.1 Requirements
The UMPT_GU, UMPT_GL, or UMPT_UL of a multimode base station provides an FE/GE
port as the co-transmission port to connect the base station to the MBSC, MME, and S-GW.
Figure 7-41 shows the network topology for co-transmission on the co-MPT GU multimode
base station side.
Figure 7-41 Network topology for co-transmission on the co-MPT GU multimode base
station side in IP over FE/GE mode

SingleRAN

No license is required.

Figure 7-42 shows an example of network topology for co-transmission on the co-MPT GU
Figure 7-42 Example of network topology for co-transmission on the co-MPT GU multimode
base station side in IP over FE/GE mode


BSC

the BSC

the RNC

SingleRAN

the UMPT_GU
IP address of the port on the 10.20.20.188/24 Device IP address during

UMPT_GU configuration on the CME.
This IP address is
transmission port.
OM IP address 10.30.30.1/32 GSM: management plane IP

address. This is a logical IP
the UMPT_GU.
NOTE
In this scenario, only one OM
IP address is configured
because the multimode base
station is configured with one
OM channel.

configured on the
UMPT_GU.

RNC
IP address of the U2000 10.60.60.60/24 GSM: peer IP address for

the OM channel
Signaling/service IP address 10.35.35.188/24 GSM: control plane/user

of the eGBTS plane IP address. This is a
configured on the
UMPT_GU.
ESN abcdefghijklmn -
7.23.3 Precautions
None


SingleRAN

NOTE
In this scenario, the GU multimode base station is configured with only one UMPT_GU. As a result, the
initial configuration is for multimode base station as a whole instead of for the UMTS and GSM sides
separately.
Step 1 Run the ADD DEVIP command to add the IP address of the NodeB.
MASK="255.255.255.0";
//Add the signaling/service IP address of the NodeB.
Step 2 Run the ADD DEVIP command to add the IP address of the eGBTS.
MASK="255.255.255.0";
//Add the signaling/service IP address of the eGBTS.
Step 3 Run the ADD IPRT command to add an uplink route from the multimode base station to the
RNC. Set RTTYPE to NEXTHOP and then set Next Hop IP to the IP address of the directly
connected router.
//Add a route from the multimode base station to the RNC on the UMPT_GU in slot 7.
BSC.
//Add a route from the multimode base station to the BSC on the UMPT_GU in slot 7.
for the eGBTS and NodeB:
the uplink route from the multimode base station to the BSC added in step 3 must be
different from the uplink route from the multimode base station to the RNC in step 4. For
example, you can set the next-hop address of the uplink route from the multimode base
station to the BSC to 10.20.20.101, which is different from the next-hop address
(10.20.20.1) of the uplink route from the multimode base station to the RNC. Run the
ADD VLANMAP command to add VLAN mapping.

requires differentiated DSCP values for the eGBTS and NodeB. For details about DSCP
values for the eGBTS and NodeB, see Bandwidth Sharing of Multimode Base Station
Co-Transmission Feature Parameter Description.
a. Run the ADD VLANCLASS command.
//Set VLANID to 22 for the data flow with SRVPRIO set to 40.
ADD VLANCLASS: VLANGROUPNO=1, TRAFFIC=USERDATA, SRVPRIO=0, IVLANID=22;

SingleRAN
//Set VLANID to 22 for the data flow with SRVPRIO set to 0. The DSCP
value in DHCP packets is fixed at 0. If DHCP relay is enabled on the
network where VLAN data is configured, set the DSCP value to 0 for VLAN.
If the DSCP value is not set to 0, DHCP packets sent to the DHCP server
do not contain the VLAN field. In addition, set TRAFFIC to USERDATA.
b. Run the ADD VLANMAP command.

----End

After the configuration file is delivered to the multimode base station and activated, perform
the following steps on the multimode base station side to verify whether the transmission link
between the multimode base station and the MBSC is normal. If the IP address can be pinged,
the transmission link is normal.
Step 1 Run the PING command to ping the IP address of the RNC.
Step 2 Run the PING command to ping the IP address of the BSC.
----End
7.24 Co-Transmission on the Co-MPT GULTM Multimode

7.24.1 Requirements
The UMPT_GUL of a multimode base station provides an FE/GE port as the co-
transmission port to connect the base station to the MBSC, MME, and S-GW. Figure
7-43 shows the network topology for co-transmission on the co-MPT GUL multimode
base station side.

SingleRAN
Figure 7-43 Network topology for co-transmission on the co-MPT GUL multimode base


Figure 7-44 shows an example of network topology for co-transmission on the co-MPT GUL

SingleRAN
Figure 7-44 Example of network topology for co-transmission on the co-MPT GUL
multimode base station side in IP over FE/GE mode

BSC

the BSC

the RNC
P address of the port on the 10.20.20.1/24 -

the UMPT_GUL

UMPT_GUL configuration on the CME.
This IP address is
transmission port.

SingleRAN
OM IP address 10.30.30.1/24 GSM: Management plane IP

address. This is a logical IP
the UMPT_GUL.
NOTE
because the multimode base
station is configured with one
OM channel.

configured on the
UMPT_GUL.

RNC
IP address of the U2000 10.60.60.60/24 GSM: Peer IP address for

the OM channel

of the eGBTS plane IP address. This is a
configured on the
UMPT_GUL.

SCTP link

IP path

configured on the
UMPT_GUL.
7.24.3 Precautions
None


SingleRAN

NOTE
In this scenario, the GUL multimode base station is configured with only one UMPT_GUL. As a result,
the initial configuration is for the multimode base station as a whole instead of for the GSM, UMTS, and
LTE sides separately.
MASK="255.255.255.0";
Step 2 Run the ADD DEVIP command to add the IP address of the eGBTS.
MASK="255.255.255.0";
//Add the signaling/service IP address of the eGBTS.
Step 3 Run the ADD DEVIP command to add the IP address of the eNodeB.
MASK="255.255.255.0";
//Add the signaling/service IP address of the eNodeB.
RNC. Set Route Type to Next Hop and then set Next Hop IP to the IP address of the directly
connected router.
//Add a route from the multimode base station to the RNC on the UMPT_GUL in slot
7.
BSC.
//Add a route from the multimode base station to the BSC on the UMPT_GUL in slot
7.
MME and SGW.
//Add a route from the multimode base station to the MME on the UMPT_GUL in slot 7
//Add a route from the multimode base station to the SGW on the UMPT_GUL in slot 7
for the eGBTS, NodeB, and eNodeB:
the uplink route from the multimode base station to the BSC added in step 3, the uplink
route from the multimode base station to the RNC added in step 4, and the uplink route
from the multimode base station to the MME and SGW in step 5 must be different from

SingleRAN
each other. For example, you can set the next-hop address of the uplink route from the
multimode base station to the BSC to 10.20.20.101, which is different from the next-hop
address (10.20.20.1) of the uplink route from the multimode base station to the RNC and
the next-hop IP address (10.20.20.10) of the uplink route from the multimode base
station to the MME and SGW. Run the ADD VLANMAP command to add VLAN
mapping.

requires differentiated DSCP values for the eGBTS, NodeB, and eNodeB. For details
about DSCP values for the eGBTS, NodeB and eNodeB, see Bandwidth Sharing of
1. Run the ADD VLANCLASS command.
field. In addition, set TRAFFIC to USERDATA
2. Run the ADD VLANMAP command.

----End


between the multimode base station and the base station controller is normal. If the IP address
Step 1 Run the PING command to ping the IP address of the RNC.
Step 2 Run the PING command to ping the IP address of the BSC.
Step 3 Run the PING command to ping the IP address of the MME.

SingleRAN
Step 4 Run the PING command to ping the IP address of the S-GW.
----End
7.25 Co-Transmission on the Hybrid-MPT

GUL/GUT/GUM Multimode Base Station Side in IP over
FE/GE Mode
7.25.1 Requirements
The UMPT_UL of a multimode base station provides an FE/GE port as the co-transmission
port to connect the base station to the MBSC, MME, and S-GW. The GTMUb and UMPT_UL
are connected through the backplane. Figure 7-45 shows the network topology for co-
transmission on the hybrid-MPT GUL multimode base station side.
Figure 7-45 Network topology for co-transmission on the hybrid-MPT GUL multimode base

SingleRAN


Figure 7-46 shows an example of network topology for co-transmission on the hybrid-MPT
GUL multimode base station side.
Figure 7-46 Example of network topology for co-transmission on the hybrid-MPT GUL
multimode base station side in IP over FE/GE mode

BSC

SingleRAN

the BSC

the RNC

the UMPT_UL

UMPT_UL configuration on the CME.
This IP address is
transmission port.
OM IP address 10.30.30.1/24 UMTS&LTE: Management

plane IP address. This is a
configured on the
UMPT_UL.
NOTE
because the co-MPT UL
multimode base station is
configured with one OM
channel.

configured on the
UMPT_UL.

RNC
IP address of the U2000 10.60.60.60/24 UMTS&LTE: Peer IP

address for the OM channel

of the GBTS plane IP address. This is a
configured on the
UMPT_UL.


SingleRAN

SCTP link

IP path

configured on the
UMPT_UL.
7.25.3 Precautions
None


Step 1 Run the MML command ADD BTSTUNNEL to add a tunnel from the GTMUb to the
UMPT_UL.
DSTSRN=0, DSTSN=7;
//Add a tunnel from the GTMUb in slot 6 to the UMPT_UL in slot 7.
Step 2 Run the MML command ADD IPRT to add a route from the BSC to co-MPT multimode base
station.
A route to the DHCP relay of the GBTS is configured on the BSC side. The co-MPT
multimode base station functions as the DHCP relay.
Step 3 Run the MML command ADD BTSDEVIP to add the IP address of the GTMUb.
IP="10.35.35.188", MASK="255.255.255.0";

SingleRAN
Step 4 Run the MML command SET BTSIP to set the communication IP address of the GBTS.
address. Specifically, set BTSCOMTYPE to LOGICIP. In non-co-transmission scenarios,
BTSCOMTYPE is optional.
//Set BTSCOMTYPE to LOGICIP.
Step 5 Run the MML command ADD BTSIPRT to add a route from the GBTS to the BSC.
IFNO=0;
Step 6 Run the MML command ADD BTSESN to add the ESN of the GBTS.
----End

NOTE
UMPT_UL.
//Add a tunnel from the GTMUb in slot 6 of subrack 0 to the UMPT_UL in slot 7 of
subrack 0.
NOTE
MASK="255.255.255.0";

SingleRAN
U2000.
----End
Initial Configuration on the Co-MPT UL Multimode Base Station Side

Step 1 Run the MML command ADD TUNNEL to add a tunnel from the UMPT_UL to the
GTMUb.
//Add a tunnel from the UMPT_UL in slot 7 to the GTMUb in slot 6.
MASK="255.255.255.0";
Step 3 Run the ADD DEVIP command to add the IP address of the eNodeB.
MASK="255.255.255.0";
//Add the signaling/service IP address of the eNodeB
Step 4 Run the ADD IPRT command to add an uplink route from the co-MPT UL multimode base
station to the RNC. Set RTTYPE to NEXTHOP and then set Next Hop IP to the IP address
of the directly connected router.
//Add a route from the multimode base station to the RNC on the UMPT_UL in slot 7.
Step 5 Run the ADD IPRT command to add an uplink route from the co-MPT UL multimode base
station to the MME and SGW.
//Add a route from the multimode base station to the MME on the UMPT_UL.

SingleRAN

//Add a route from the multimode base station to the SGW on the UMPT_UL.
Step 6 Run the ADD IPRT command to add an uplink route from the GBTS/eGBTS to the BSC
through the co-MPT UL multimode base station. Set RTTYPE to NEXTHOP and then set
Next Hop IP to the IP address of the directly connected router.
//Add a route from the GBTS/eGBTS to the BSC through the co-MPT UL multimode base
station on the UMPT_UL in slot 7.
Step 7 Run the ADD IPRT command to add a downlink route from the BSC to the GBTS/eGBTS
through the co-MPT UL multimode base station.
When co-transmission for the GBTS/eGBTS and co-MPT UL multimode base station is
implemented through tunnels on the backplane, the downlink route from the BSC to the
GBTS/eGBTS through the co-MPT UL multimode base station must be configured on the co-
MPT UL multimode base station. In addition, SBT must be set to BACK_BOARD and IFT
must be set to TUNNEL.
ADD IPRT: RTIDX=4,CN=0, SN=7, SBT=BACK_BOARD, DSTIP="10.35.35.188",
//Add a downlink route from the BSC to the GBTS/eGBTS through the co-MPT UL
multimode base station on the UMPT_UL.
Step 8 Run the MML command SET DHCPRELAYSWITCH to enable DHCP relay.
If the GBTS/eGBTS is deployed using DHCP, the co-MPT UL multimode base station needs
to work as the relay. Therefore, DHCP relay needs to be enabled for the co-MPT UL
multimode base station.
//Enable DHCP relay for the co-MPT UL multimode base station.
Step 9 Run the MML command ADD DHCPSVRIP to add the IP address of the DHCP server.
If the GBTS/eGBTS is deployed using DHCP, the co-MPT UL multimode base station needs
to work as the relay. Therefore, the IP address of the DHCP server needs to be added on the
co-MPT UL multimode base station. For the GBTS, the IP address of the DHCP server is the
IP address of the BSC. For the eGBTS, the IP address of the DHCP server is the IP address of
the U2000.
the uplink route from the multimode base station to the BSC added in step 4, the uplink
route from the multimode base station to the RNC added in step 5, and the uplink route
from the multimode base station to the MME and SGW in step 6 must be different from
each other. For example, you can set the next-hop address of the uplink route from the
multimode base station to the BSC to 10.20.20.101, which is different from the next-hop
address (10.20.20.1) of the uplink route from the multimode base station to the RNC and
the next-hop IP address (10.20.20.10) of the uplink route from the multimode base
station to the MME and SGW. Run the ADD VLANMAP command to add VLAN
mapping.

SingleRAN


1. Run the ADD VLANCLASS command.
// Set VLANID to 22 for the data flow with SRVPRIO set to 0. The DSCP value
in DHCP packets is fixed at 0. If DHCP relay is enabled on the network where
2. Run the ADD VLANMAP command.

----End


between the multimode base station and the base station controller is normal:
Step 1 Run the Ping command on the BSC to ping the IP address of the GTMUb on the BSC side.
CONTPING=NO;
Step 2 Run the Ping command on the multimode base station to ping the IP address of the RNC. If
the IP address can be pinged, the transmission link is normal.
Step 3 Run the Ping command on the multimode base station to ping the IP address of the MME.
Step 4 Run the Ping command on the multimode base station to ping the IP address of the S-GW.
----End

SingleRAN

Backplane Interconnection on the Separate-MPT
LGU/TGU/MGU Multimode Base Station Side in IP over
FE/GE Mode
7.26.1 Requirements
interconnection on the separate-MPT LGU multimode base station side. In this scenario,
an FE/GE port on the UMPT_L of the eNodeB serves as the co-transmission port of the
separate-MPT LGU multimode base station and is connected to the MBSC and MME/S-
GW. The GTMUb and UMPT_L are interconnected by using backplanes through the
UCIU. The WMPT and UMPT_L are interconnected by using backplanes through the
UCIU.

interconnection on the separate-MPT LGU multimode base station side

interconnection on the separate-MPT LGU multimode base station side. In this scenario, an
FE/GE port on the UMPT_L of the eNodeB serves as the co-transmission port of the separate-

SingleRAN
MPT LGU multimode base station and is connected to the MBSC and MME/S-GW. The
GTMUb and UMPT_L in one BBU are interconnected by using backplanes. The UMPT_U
and UMPT_L are interconnected by using backplanes through the UCIU.
interconnection on the separate-MPT LGU multimode base station side. In this scenario, an
FE/GE port on the UMPT_L of the eNodeB serves as the co-transmission port of the separate-
MPT LGU multimode base station and is connected to the MBSC and MME/S-GW. The
GTMUb and UMPT_L in one BBU are interconnected by using backplanes. The UMPT_U
and UMPT_L are interconnected by using interconnection cables.

on the separate-MPT LGU multimode base station side (UCIU+UMPT interconnection)

SingleRAN

on the separate-MPT LGU multimode base station side (UMPT+UMPT interconnection)
This document provides only the engineering guidelines for the scenario shown in Figure
7-47. The engineering guidelines for the scenarios shown in Figure 7-48 and Figure 7-49 are
similar to those for the scenario shown in Figure 7-47.

Key Data Preparation
Figure 7-50 shows an example of the network topology for main-control-board-based IP co-
transmission through backplane interconnection on the LGU MBTS side.

SingleRAN
Figure 7-50 Example of the network topology for main-control-board-based IP co-

transmission through backplane interconnection on the LGU MBTS side


BSC

BSC

RNC

RNC

the router that is
connected to the RNC

the router that is
connected to the BSC

SingleRAN

the router that is
connected to the
UMPT_U
OM IP address of the 10.30.30.1/24 UMTS: management plane IP address. This

NodeB IP address is configured on the main
control board.
Signaling/service IP 10.32.32.1/24 UMTS: control plane/user plane IP address.

address of the NodeB This is a logical IP address configured on
IP address of the FE1 10.20.20.188/24 LTE: device IP address during

port on the UMPT_L of configuration on the CME. This IP address
the eNodeB is configured on the co-transmission port.
IP address of the MME 10.40.40.40/24 LTE: peer IP address for the SCTP link
IP address of the S-GW 10.50.50.50/24 LTE: peer IP address for the IP path
IP address of the U2000 10.60.60.60/24 UMTS/LTE: peer IP address for the OM

channel
OM IP address of the 10.31.31.188/24 LTE: management plane IP address. This is

eNodeB a logical IP address configured on the main
control board.
Signaling/service IP 10.33.33.188/24 LTE: control plane/user plane IP address.

address of the eNodeB This is a logical IP address configured on
IP address of the GBTS 10.35.35.188/24 GSM: communication IP address of the

GBTS. This is a logical IP address and is
configured on the GBTS main control
board.
OM/signaling/service IP 10.35.35.188/24 The same IP address is used for O&M,

address of the eGBTS signaling, and services for the eGBTS.
ESN of the GBTS abcdefghijklmn For the GBTS, the ESN needs to be
planned. For the eGBTS, the ESN does not
need to be planned.
NOTE
In this scenario, the GTMUb and WMPT/UMPT_U do not need to be configured with Ethernet port
attributes such as duplex mode and rate because the GTMUb and WMPT/UMPT_U communicate with
the UCIU through the backplane and UCIU communicates with the UMPT_L through the M interface.
7.26.3 Precautions
None

SingleRAN

Unlike non-co-transmission scenario, this scenario does not require additional hardware.

Configure two routes to the DHCP relay of the NodeB on the U2000 side. In this step, set the
destination IP address of one route to the OM channel IP address of the eNodeB and that of
the other route to the lower-level transmission port of the eNodeB.

For details about the data configurations at the data link layer and network layer, see 3900
Series Base Stations Initial Configuration.
NOTE
In addition to the configuration steps described in 3900 Series Base Stations Initial Configuration
Guide, perform the following steps for co-transmission:
Step 1 (UCIU+UMPT interconnection) Run the ADD BTSBRD command to add a UCIU.
Step 2 Run the ADD BTSCTRLLNK command to add a BBU interconnection control link between
GSM and LTE.
(UCIU+UMPT interconnection)
UPSN=0, UPPT=0;
of subrack 0.
(UMPT+UMPT interconnection)
UPSN=7, UPPT=8;
of subrack 0.
UMPT_L.
DSTSRN=1, DSTSN=7;
//Add a tunnel from the GTMUb in slot 6 to the UMPT_L in slot 7.
NOTE
According to the co-transmission networking plan, modify the parameters in the following steps
described in 3900 Series Base Stations Initial Configuration Guide.
IP="10.35.35.188", MASK="255.255.255.0";
//Port Type must be set to LOOPINTERFACE.
address. Specifically, set BTS Communication Type to LOGICIP. In non-co-transmission
scenarios, set BTS Communication Type to an appropriate value based on the actual
situations.

SingleRAN

//Set BTS Communication Type to LOGICIP and BTSIP to an appropriate value.
Unlike non-co-transmission scenarios, set Route Type to OUTIF, Interface Type to

TUNNEL, and Outgoing Interface No. to the number of the tunnel added in step 3.
IFNO=0;
//OM BEAR BOARD must be set to BACKBOARD.
GBTS. In this step, set DSTIP to the OM channel IP address of the eNodeB. Run this
the eNodeB.
----End


NOTE
Guide, the following steps 1 through 3 are added.
link.
(UCIU+UMPT interconnection)
of subrack 0.
(UMPT+UMPT interconnection)
of subrack 0.
UMPT_U.
//Add a tunnel from the GTMUb in slot 6 of subrack 0 to the UMPT_U in slot 7 of
subrack 0.

SingleRAN
NOTE
address, that is, Port Type must be set to LOOPINT. In non-co-transmission scenarios, Port
Type can be set as required.
MASK="255.255.255.0";
U2000.

to IF, Port Type to TUNNEL, and Port No. to the number of the tunnel added in step 3.
----End

Base Stations Initial Configuration Guide.
NOTE
Guide, perform the following steps for co-transmission.
link.
//UCIU+UMPT interconnection
//Add a control link from the board in slot 7 of BBU subrack 1 to the board in
slot 0 of BBU subrack 0.
//UMPT+UMPT interconnection
UPSN=7, UPPT=8;
of subrack 0.
Step 2 Run the NodeB MML command ADD TUNNEL to add a tunnel from the WMPT to the
UMPT_L.
ADD TUNNEL: SSN=7, DSRN=1, DSN=7;
//Add a tunnel from the WMPT in slot 7 of BBU subrack 0 to the UMPT_L in slot 7
of BBU subrack 1.

SingleRAN
NOTE
According to the co-transmission networking plan, modify the parameters in the following steps
described in 3900 Series Base Stations Initial Configuration Guide.
Step 3 Run the NodeB MML command ADD DEVIP to configure the IP address.
Unlike non-co-transmission scenarios, this scenario requires that the IP address of the NodeB
be configured as the logical IP address. In non-co-transmission scenarios, the IP address of
the NodeB can be set as required.
MASK="255.255.255.0";
//Add a signaling/service IP address for the NodeB and set Port Type to LOOPINT.
Step 4 Run the NodeB MML command ADD IPRT to add a route from the NodeB to the RNC/
U2000.
to IF, Port Type to TUNNEL, and Port No. to the number of the tunnel added in step 2.
//Add a route from the NodeB to the RNC.
//Add a route from the NodeB to the U2000.
Step 5 (Optional) Run the NodeB MML command ADD RSCGRP to add a transmission resource
group.
ADD RSCGRP: SN=7, BEAR=IP, SBT=BACK_BOARD, PT=TUNNEL, RSCGRPID=0, RU=KBPS,
TXBW=4000, RXBW=4000;
//When adding a transmission resource group set Subboard Type to BACK_BOARD and
Bearing Port Type to TUNNEL.
Step 6 Run the NodeB MML command ADD IPPATH to add an IP path.
ADD IPPATH: PATHID=0, SN=7, SBT=BACK_BOARD, PT=TUNNEL, JNRSCGRP=DISABLE,
LOCALIP="10.32.32.1", PEERIP="10.15.15.15", PATHTYPE=ANY;
//Add an IP path with Subboard Type set to BACK_BOARD and Port Type set to TUNNEL.
Step 7 Run the NodeB MML command ADD OMCH to add an O&M channel.
//Add an O&M channel.
----End

Base Stations Initial Configuration Guide.
NOTE
required. The number of the BBU used for LTE must be different from the number of the BBU used for
GU. In this example, the number of the BBU for LTE is 1.
Guide, perform the following steps for co-transmission.
Step 1 Run the eNodeB MML command ADD CTRLLNK to add a control link between BBUs.
//(UCIU+UMPT interconnection)

SingleRAN
of subrack 0.
//(UMPT+UMPT interconnection)
UPSN=7, UPPT=8;
of subrack 0.
Step 2 Run the eNodeB MML command ADD TUNNEL to add tunnels from the UMPT_L to the
WMPT and GTMUb.
ADD TUNNEL: SSRN=1, SSN=7, DSN=7;
//Add a tunnel from the UMPT_L in slot 7 of subrack 1 to the WMPT in slot 7 of
subrack 0. ADD TUNNEL: TUNNELID=1, SSRN=1, SSN=7, DSN=6;
//Add a tunnel from the UMPT_L in slot 7 of subrack 1 to the GTMUb in slot 6 of
subrack 0.
NOTE
The parameter settings in the following steps described in 3900 Series Base Station Initial Configuration
Guide are modified according to the co-transmission network plan.
Step 3 Run the eNodeB MML command ADD DEVIP to add IP addresses for the eNodeB.
MASK="255.255.255.0";
//Add a signaling/service IP address for the UMPT_L in slot 7 of subrack 1.
MASK="255.255.255.0";
//Add an IP address for Ethernet port 1 on the UMPT_L in slot 7 of subrack 1.
Step 4 Run the eNodeB MML command ADD IPRT to add an uplink route from the NodeB to the
RNC/U2000 through the eNodeB, and an uplink route from the GBTS/eGBTS to the GBSC
through the eNodeB.
ADD IPRT: RTIDX=0, CN=0, SRN=1, SN=7, SBT= BASE_BOARD, DSTIP="10.15.15.15",
//Add a route from the NodeB to the RNC through the eNodeB.
ADD IPRT: RTIDX=1, CN=0, SRN=1, SN=7, SBT= BASE_BOARD, DSTIP="10.60.60.60",
//Add a route from the NodeB to the RNC through the eNodeB.
//Add an uplink route from the GBTS/eGBTS to the GBSC through the eNodeB.
Step 5 Run the eNodeB MML command ADD IPRT to add a downlink route from the U2000/RNC
to the NodeB through the eNodeB, and a downlink route from the GBSC to the GBTS/eGBTS
through the eNodeB.
When IP-based co-transmission for the GBTS/eGBTS, eNodeB, and NodeB is implemented
through tunnels on the UMPT_U backplane, the downlink route from the GBSC to the GBTS/
eGBTS through the eNodeB and the downlink route from the RNC/U2000 to the NodeB
through the eNodeB must be configured on the eNodeB. In addition, Subboard Type must be
set to BACK_BOARD and Port Type must be set to TUNNEL.
//Add a downlink route from the U2000 to the NodeB through the eNodeB.
//Add a downlink route from the RNC to the NodeB through the eNodeB.
ADD IPRT: RTIDX=5, CN=0, SRN=1, SN=7,SBT=BACK_BOARD, DSTIP="10.35.35.188",
//Add a downlink route from the BSC to the GBTS/eGBTS through the eNodeB.
relay.

SingleRAN
When co-transmission is enabled for the GBTS/eGBTS, NodeB, and eNodeB, the eNodeB
needs to work as the relay if the GBTS/eGBTS and NodeB are deployed using DHCP.
Therefore, DHCP relay needs to be enabled for the eNodeB.
DHCP server.
When co-transmission is enabled for the GBTS/eGBTS, NodeB, and eNodeB, the eNodeB
needs to work as the relay if the GBTS/eGBTS, NodeB are deployed using DHCP. Therefore,
the IP address of the DHCP server needs to be added on the eNodeB. For the NodeB, the
RNC or U2000 works as the DHCP server. For the eGBTS, the U2000 works as the DHCP
server.
//Add the IP address of the DHCP server for the eGBTS/NodeB.
the uplink route from the GBTS/eGBTS to the BSC through the eNodeB and the uplink
route from the NodeB to the RNC through the eNodeB added in step 4 must be different
from the uplink route for the eNodeB. For example, you can set the next-hop address of
the uplink route from the GBTS/eGBTS to the BSC through the NodeB to 10.20.20.101,
and set the next-hop address of the uplink route from the NodeB to the RNC through the
VLANMAP.
Method 2 (Not recommended): Configure differentiated DSCP values. This method

details about DSCP values for the GBTS/eGBTS, NodeB, and eNodeB, see the
Bandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter
Description.
Step 9 Run the NodeB MML command ADD VLANCLASS.
//Set VLANID to 22 for the data flow with SRVPRIO set to 40. In VLAN group mode,
set TRAFFIC to USERDATA for all passerby flows through the eNodeB. If
//Set VLANID to 32 for the data flow with SRVPRIO set to 26. In VLAN group mode,
set TRAFFIC to USERDATA for all passerby flows through the NodeB. If
differentiated data needs to be configured for the eNodeB and NodeB and TRAFFIC
is set to USERDATA, SRVPRIO cannot be set to 26 on the eNodeB.
DHCP packets is fixed at 0. If DHCP relay is enabled on the network where VLAN
data is configured, set the DSCP value to 0 for VLAN. If the DSCP value is not
set to 0, DHCP packets sent to the DHCP server do not contain the VLAN field. In
addition, set TRAFFIC to USERDATA.
Step 10 Run the NodeB MML command ADD VLANMAP.

SingleRAN
ADD VLANMAP: NEXTHOPIP="10.20.20.1", MASK="255.255.255.0", VLANMODE=VLANGROUP,

VLANGROUPNO=1;
----End

After co-transmission is enabled on the MBTS side, check whether the feature is enabled
based on the status of the IP link between the MBTS and the peer device.
LTE Side
normal.
----End
UMTS Side
step on the NodeB side to check whether the transmission link between the NodeB and the
RNC is normal:
----End
GSM Side
following step on the GBSC side to check whether the transmission link between the GBSC
and the GBTS/eGBTS is normal:
CONTPING=NO;
----End
7.27 Performance Monitoring
7.27.1 IP-based Co-Transmission on the MBSC Side

None

SingleRAN
7.27.2 IP-based Co-Transmission on the Multimode Base Station

Side
None
7.28 Possible Issues
7.28.1 IP-based Co-Transmission on the MBSC Side

None
7.28.2 IP-based Co-Transmission on the Multimode Base Station

Side
An alarm will be reported on the eNodeB, GBTS/eGBTS, or NodeB side if a fault exists.
The following alarms may be reported on the eNodeB side:
l ALM-25860 PPP/MLPPP Link Fault
l ALM-25861 MLPPP Group Fault
l ALM-25862 MLPPP Group Excessive Packet Loss Rate
l ALM-25863 PPP Link Excessive Frame Error Rate
l ALM-25880 Ethernet Link Fault

l ALM-25881 MAC Excessive Frame Error Rate
l ALM-25885 IP Address Conflict
l ALM-25888 SCTP Link Fault
l ALM-25886 IP Path Fault
l ALM-29201 S1 Interface Fault
l ALM-29240 Cell Unavailable
The following alarms may be reported on the NodeB side:

l ALM-25888 SCTP Link Fault/ALM-1851 SCTP Link Down
l ALM-25835 NCP Fault/ALM-2010 NCP Faulty Alarm
l ALM-25836 CCP Fault/RNC: ALM-2011 CCP Faulty Alarm
l ALM-28203 Local Cell Unusable/ALM-2006 Cell Unavailable Alarm
The following alarms may be reported on the GBTS/eGBTS side:

SingleRAN

l ALM-28006 Radio Signaling Link Disconnected
l ALM-21512 LAPD Link Fault
l ALM-21805 ESL Link Fault
l ALM-25888 SCTP Link Fault
l ALM-21801 GSM Cell out of Service
If any of the preceding alarms is reported on a transmission port on the eNodeB, GBTS/
eGBTS, or NodeB side, handle the alarm according to the alarm reference.

SingleRAN
Common Transmission Feature Parameter Description 8 Parameters
8 Parameters
Table 8-1 Parameters

Parame NE MML Feature Feature Description
ter ID Comma ID Name
nd
TN BSC690 ADD GBFD-1 Abis Meaning: Index of a tunnel.

0 BTSTU 18601 over IP GUI Value Range: 0~14
NNEL
Unit: None
MOD
BTSTU Actual Value Range: 0~14
NNEL Default Value: None
RMV
BTSTU
NNEL
TN BSC691 ADD GBFD-1 Abis Meaning: Index of a tunnel.

0 BTSTU 18601 over IP GUI Value Range: 0~14
NNEL
Unit: None
MOD
BTSTU Actual Value Range: 0~14
NNEL Default Value: None
RMV
BTSTU
NNEL

SingleRAN
Common Transmission Feature Parameter Description 8 Parameters
Parame NE MML Feature Feature Description

ter ID Comma ID Name
nd
TUNNE BTS390 ADD MRFD- IP- Meaning: Indicates the index of the tunnel.
LID 0, TUNNE 121124 Based GUI Value Range: 0~14
BTS390 L Multi-
0 MRFD- mode Unit: None
DSP 121134
WCDM TUNNE Co- Actual Value Range: 0~14
A, L LOFD-0 Transmi Default Value: None
BTS390 03002 / ssion on
0 LTE MOD TDLOF BS
TUNNE D-00300 side(No
L 2 deB)
RMV
TUNNE MRFD- IP-
L 121114 Based
Multi-
LST mode
TUNNE Co-
L Transmi
ssion on
BS
side(eN
odeB)
2G/3G
and LTE
Co-
transmis
sion
IP-
Based
Multi-
mode
Co-
Transmi
ssion on
BS
side(GB
TS)

SingleRAN
Common Transmission Feature Parameter Description 9 Counters
9 Counters
Table 9-1 Counters

Counter ID Counter Counter NE Feature ID Feature Name
Name Description
1542455856 VS.TUNNEL.T Number of eGBTS Multi-mode: IP-Based Multi-

xBytes Bytes MRFD-121114 mode Co-
Transmitted in MRFD-121124 Transmission on
the Tunnel BS side(GBTS)
MRFD-121134
IP-Based Multi-
MRFD-121144 mode Co-
GSM: None Transmission on
UMTS: None BS side(NodeB)
LTE: None IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)

SingleRAN

Name Description
1542455857 VS.TUNNEL.T Number of eGBTS Multi-mode: IP-Based Multi-

xPackets Packets MRFD-121114 mode Co-
Transmitted in MRFD-121124 Transmission on
the Tunnel BS side(GBTS)
MRFD-121134
IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)
1542455858 VS.TUNNEL. Number of eGBTS Multi-mode: IP-Based Multi-

RxBytes Bytes Received MRFD-121114 mode Co-
in the Tunnel MRFD-121124 Transmission on
BS side(GBTS)
MRFD-121134
IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)

SingleRAN

Name Description
1542455859 VS.TUNNEL. Number of eGBTS Multi-mode: IP-Based Multi-

RxPackets Packets MRFD-121114 mode Co-
Received in the MRFD-121124 Transmission on
Tunnel BS side(GBTS)
MRFD-121134
IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)
1542455860 VS.TUNNEL.T Maximum eGBTS Multi-mode: IP-Based Multi-

xMaxSpeed Transmit Rate MRFD-121114 mode Co-
BS side(GBTS)
MRFD-121134
IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)

SingleRAN

Name Description
1542455861 VS.TUNNEL.T Minimum eGBTS Multi-mode: IP-Based Multi-

xMinSpeed Transmit Rate MRFD-121114 mode Co-
BS side(GBTS)
MRFD-121134
IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)
1542455862 VS.TUNNEL.T Average eGBTS Multi-mode: IP-Based Multi-

xMeanSpeed Transmit Rate MRFD-121114 mode Co-
BS side(GBTS)
MRFD-121134
IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)

SingleRAN

Name Description
1542455863 VS.TUNNEL. Maximum eGBTS Multi-mode: IP-Based Multi-

RxMaxSpeed Receive Rate in MRFD-121114 mode Co-
the Tunnel MRFD-121124 Transmission on
BS side(GBTS)
MRFD-121134
IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)
1542455864 VS.TUNNEL. Minimum eGBTS Multi-mode: IP-Based Multi-

RxMinSpeed Receive Rate in MRFD-121114 mode Co-
BS side(GBTS)
MRFD-121134
IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)

SingleRAN

Name Description
1542455865 VS.TUNNEL. Average eGBTS Multi-mode: IP-Based Multi-

RxMeanSpeed Receive Rate in MRFD-121114 mode Co-
BS side(GBTS)
MRFD-121134
IP-Based Multi-
mode Co-
Transmission on
BS
side(eNodeB)
IP-Based Multi-
mode Co-
Transmission on
BS side(LTE
TDD)

SingleRAN
Common Transmission Feature Parameter Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

SingleRAN
Common Transmission Feature Parameter Description 11 Reference Documents
11 Reference Documents
1. IP Transmission Feature Parameter Description for SingleRAN

2. Bandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter
Description for SingleRAN
3. 3900 Series Base Station Initial Configuration Guide


Common Transmission (SRAN12.0 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Common Transmission (SRAN12.0 01)

Uploaded by

Copyright:

Available Formats

SingleRAN

Common Transmission Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2016-09-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

3 IP-based Co-Transmission on the MBSC Side...................................................................... 10

4 Co-Transmission on the Multimode Base Station Side....................................................... 20

Issue 01 (2016-09-30) Huawei Proprietary and Confidential ii

4.2.4 Main-Control-Board-based Co-Transmission Through Backplane Interconnection on the Separate-MPT

Issue 01 (2016-09-30) Huawei Proprietary and Confidential iii

7.7 Main-Control-Board-based Co-Transmission Through Panel Interconnection on the Separate-MPT L+GU/T+GU/M

Issue 01 (2016-09-30) Huawei Proprietary and Confidential iv

Issue 01 (2016-09-30) Huawei Proprietary and Confidential v

7.17.3 Reconstruction Preparations and Procedure.......................................................................................................... 141

Issue 01 (2016-09-30) Huawei Proprietary and Confidential vi

7.22.5 Initial Configuration.............................................................................................................................................. 173

Issue 01 (2016-09-30) Huawei Proprietary and Confidential vii

11 Reference Documents............................................................................................................. 215

Issue 01 (2016-09-30) Huawei Proprietary and Confidential viii

1 About This Document

This document covers the following feature on the MBSC side:

l MRFD-121101 IP-Based BSC and RNC Co-Transmission on MBSC Side

This document covers the following features on the MBTS side:

l MRFD-120111 TDM-Based Multi-mode Co-Transmission via Backplane on BS

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 1

The co-transmission principle of an eGBTS using a GTMUb/GTMUc as the main control

1.2 Intended Audience

1.3 Change History

SRAN12.1 Draft B (2016-12-30)

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change

Feature Changed the following features from optional None

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 3

Change Change Description Parameter Change

Supported NB-IoT. For details, see the None

Editorial None None

SRAN12.1 Draft A (2016-10-30)

Change Change Description Parameter Change

Feature Supported the EXOUb and FG2e boards. None

Editorial None None

1.4 Differences Between Base Station Types

MRFD-121101 IP-Based BSC and RNC Co- Y N N

MRFD-120111 TDM-Based Multi-mode Co- Y N N

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 4

Feature ID Feature Name Suppor Suppor Suppor

MRFD-120121 TDM-Based Multi-mode Co- Y N N

MRFD-121114 IP-Based Multi-mode Co- Y N N

MRFD-121124 IP-Based Multi-mode Co- Y Y Y

MRFD-121134 IP-Based Multi-mode Co- Y Y Y

MRFD-121144 IP-Based Multi-mode Co- Y N N

MRFD-121154 IP-Based Multi-mode Co- Y Y N

Function Implementation in Macro, Micro, and LampSite Base Stations

1.5 Functional Differences Between NB-IoT and FDD

MRFD-1211 IP-Based MRFD-12113 IP-Based None

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 5

2.3 Application Scenarios

2.3.1 Co-Transmission on the MBSC Side

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 6

Figure 2-1 Typical scenario of co-transmission on the MBSC side

2.3.2 Co-Transmission on the MBTS Side

TDM-based co-transmission is supported only by separate-MPT GU multimode base stations.