Common Transmission (SRAN9.0 01)

SingleRAN
Common Transmission Feature

Parameter Description
Issue
01
Date
2014-04-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. 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 (2014-04-30)
Huawei Proprietary and Confidential

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.......................................................................................................................3
2 Overview.........................................................................................................................................4
2.1 Introduction....................................................................................................................................................................4
2.2 Benefits...........................................................................................................................................................................5
2.3 Usage Scenario...............................................................................................................................................................5
2.3.1 Co-Transmission on the MBSC Side...........................................................................................................................5
2.3.2 GU/GL/UL/GT/UT/LTGUL/GUT/GLT/ULT/GULT Co-Transmission on the Multimode Base Station Side.........6
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............................................................................................................................................................17
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.................................................................................................................................................................................32
4.2.3 UTRP-based Co-Transmission Through Panel Interconnection on the Separate-MPT Multimode Base Station Side
............................................................................................................................................................................................34
Issue 01 (2014-04-30)

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

Base Station Side................................................................................................................................................................35
4.2.5 UTRPc-based Co-Transmission Through Backplane Interconnection on the Separate-MPT Multimode Base Station
Side.....................................................................................................................................................................................36
4.2.6 Co-Transmission on the Co-MPT Multimode Base Station Side..............................................................................38
5 Related Features...........................................................................................................................40
5.1 Features Related to IP-based Co-Transmission on the MBSC Side.............................................................................40
5.1.1 Prerequisite Features..................................................................................................................................................40
5.1.2 Mutually Exclusive Features.....................................................................................................................................41
5.1.3 Affected Features.......................................................................................................................................................41
5.2 Features Related to Co-Transmission on the Multimode Base Station Side................................................................41
5.2.1 Prerequisite Features..................................................................................................................................................41
5.2.2 Mutually Exclusive Features.....................................................................................................................................42
5.2.3 Affected Features.......................................................................................................................................................42
6 Impact on the Network...............................................................................................................43

6.1 IP-based Co-Transmission on the MBSC Side.............................................................................................................43
6.1.1 Impact on System Capacity.......................................................................................................................................43
6.1.2 Impact on Network Performance...............................................................................................................................43
6.2 Co-Transmission on the Multimode Base Station Side................................................................................................43
6.2.1 Impact on System Capacity.......................................................................................................................................43
6.2.2 Impact on Network Performance...............................................................................................................................44
7 Engineering Guidelines.............................................................................................................45
7.1 When to Use Co-Transmission.....................................................................................................................................46
7.1.1 IP Co-Transmission on the MBSC Side....................................................................................................................46
7.1.2 Co-Transmission on the Multimode Base Station Side.............................................................................................46
7.2 Information to Be Collected.........................................................................................................................................46
7.3 Network Planning.........................................................................................................................................................47
7.4 Co-Transmission for Iub and Abis Interfaces on the MBSC Side...............................................................................47
7.4.1 Deployment Requirements........................................................................................................................................47
7.4.2 Data Preparation........................................................................................................................................................49
7.4.3 Precautions.................................................................................................................................................................53
7.4.4 Hardware Adjustment................................................................................................................................................53
7.4.5 Initial Configuration..................................................................................................................................................53
7.4.6 Activation Observation..............................................................................................................................................53
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.........................................................................................................................54
7.5.3 Precautions.................................................................................................................................................................58
Issue 01 (2014-04-30)

iii
SingleRAN
Contents

7.6 Main-Control-Board-based Co-Transmission Through Panel Interconnection on the Separate-MPT LU/TU Multimode
7.6.3 Precautions.................................................................................................................................................................66
7.7 Main-Control-Board-based Co-Transmission Through Panel Interconnection on the Separate-MPT LG/TG Multimode
7.7.3 Precautions.................................................................................................................................................................73
7.8 Main-Control-Board-based Co-Transmission Through Panel Interconnection on the Separate-MPT LGU/TGU
Multimode Base Station Side in IP over FE/GE Mode......................................................................................................77
7.8.3 Precautions.................................................................................................................................................................84
7.9 Main-Control-Board-based IP Co-Transmission Through Backplane Interconnection on the Separate-MPT LG/TG
Multimode Base Station Side.............................................................................................................................................89
7.9.3 Precautions.................................................................................................................................................................95
7.10 Main-Control-Board-based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG
Multimode Base Station Side in IP over FE/GE Mode......................................................................................................99
7.10.1 Deployment Requirements......................................................................................................................................99
7.10.2 Data Preparation....................................................................................................................................................100
7.10.3 Precautions.............................................................................................................................................................104
7.10.4 Hardware Adjustment............................................................................................................................................105
7.10.5 Initial Configuration..............................................................................................................................................105
7.10.6 Activation Observation..........................................................................................................................................108
7.11 UTRPc-based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG Multimode Base
Station Side in IP over FE/GE Mode................................................................................................................................108
Issue 01 (2014-04-30)

iv
SingleRAN
Contents
7.11.1 Deployment Requirements....................................................................................................................................108

7.11.3 Precautions.............................................................................................................................................................114
7.12 Main-Control-Board-based Co-Transmission Through Backplane Interconnection on the Separate-MPT UL/UT
Multimode Base Station Side in IP over FE/GE Mode....................................................................................................118
7.12.3 Precautions.............................................................................................................................................................124
7.13 UTRPc-based Co-Transmission Through Backplane Interconnection on the Separate-MPT UL/UT Multimode Base
7.13.3 Precautions.............................................................................................................................................................136
7.14 Main-Control-Board-based Co-Transmission Through Backplane Interconnection on the Separate-MPT LU/TU
7.14.3 Precautions.............................................................................................................................................................147
7.15 UTRPc-based Co-Transmission Through Backplane Interconnection on the Separate-MPT UG+L/UG+T Multimode
Base Station Side in IP over FE/GE Mode.......................................................................................................................151
7.15.3 Precautions.............................................................................................................................................................162
7.16 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..............................................................................................168
7.16.3 Precautions.............................................................................................................................................................180
Issue 01 (2014-04-30)

SingleRAN
Contents

7.17 Reconstruction from Transmission Through the Main Control Board Panel on a BTS 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...........................................................................................................................................................................187
7.17.3 Reconstruction Preparations and Procedure..........................................................................................................190
7.17.4 Precautions.............................................................................................................................................................192
7.17.5 Reconfiguration.....................................................................................................................................................192
7.17.6 Rollback.................................................................................................................................................................192
Co-Transmission Through Backplane Interconnection on the Separate-MPT LG/TG Multimode Base Station Side in IP
over FE/GE Mode.............................................................................................................................................................193
7.18.4 Precautions.............................................................................................................................................................198
7.18.6 Rollback.................................................................................................................................................................199
Co-Transmission Through Backplane Interconnection on the Separate-MPT UG Multimode Base Station Side..........199
7.19.4 Precautions.............................................................................................................................................................204
7.19.6 Rollback.................................................................................................................................................................205
7.20 Reconstruction from Transmission Through the Main Control Board Panel on a NodeB to Main-Control-Board-based
Co-Transmission Through Backplane Interconnection on the Separate-MPT UL/UT Multimode Base Station Side in IP
over FE/GE Mode.............................................................................................................................................................205
7.20.4 Precautions.............................................................................................................................................................210
7.20.6 Rollback.................................................................................................................................................................210
7.21 Reconstruction from Main-Control-Board-based IP Co-Transmission Through Panel Interconnection to UTRPcbased Co-Transmission Through Backplane Interconnection on the Separate-MPT UG Multimode Base Station Side in
IP over FE/GE Mode........................................................................................................................................................211
Issue 01 (2014-04-30)

vi
SingleRAN
Contents
7.21.4 Precautions.............................................................................................................................................................215
7.21.6 Rollback.................................................................................................................................................................216
7.22 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
7.22.4 Precautions.............................................................................................................................................................228
7.22.7 Rollback.................................................................................................................................................................232
7.23 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 SeparateMPT UG+L/UG+T Multimode Base Station Side...........................................................................................................232
7.23.4 Precautions.............................................................................................................................................................239
7.23.6 Rollback.................................................................................................................................................................240
7.24 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..........................................................................................................................241
7.24.4 Precautions.............................................................................................................................................................248
7.24.6 Rollback.................................................................................................................................................................249
7.25 Main-Control-Board-based Co-Transmission Through Panel Interconnection on the Separate-MPT UG Multimode
Base Station Side in IP over E1/T1 Mode........................................................................................................................250
7.25.3 Precautions.............................................................................................................................................................254
7.26 UTRP4-based Co-Transmission Through Panel Interconnection on the Separate-MPT UG Multimode Base Station
Side in IP over E1/T1 Mode.............................................................................................................................................256
Issue 01 (2014-04-30)

vii
SingleRAN
Contents
7.26.3 Precautions.............................................................................................................................................................260
7.27 GTMU-based TDM Co-Transmission on the Separate-MPT GU Multimode Base Station Side............................263
7.27.3 Precautions.............................................................................................................................................................264
7.28 Co-Transmission on the Co-MPT GU/GL/UL/GT/UT/LT Multimode Base Station Side in IP over FE/GE Mode
..........................................................................................................................................................................................265
7.28.3 Precautions.............................................................................................................................................................269
7.29 Co-Transmission on the Co-MPT GUL/GUT/GLT/ULT/GULT Multimode Base Station Side in IP over FE/GE Mode
..........................................................................................................................................................................................271
7.29.3 Precautions.............................................................................................................................................................276
7.30 Co-Transmission on the Hybrid-MPT GUL Multimode Base Station Side in IP over FE/GE Mode.....................278
7.30.3 Precautions.............................................................................................................................................................285
7.31 Main-control-board -based Co-Transmission Through Backplane Interconnection on the Separate-MPT LGU/TGU
7.31.3 Precautions.............................................................................................................................................................302
Issue 01 (2014-04-30)

viii
SingleRAN
Contents
7.32 Performance Monitoring...........................................................................................................................................308

7.32.1 IP Co-Transmission on the MBSC Side................................................................................................................308
7.32.2 IP Co-Transmission on the Multimode Base Station Side....................................................................................308
7.33 Parameter Optimization............................................................................................................................................308
7.34 Troubleshooting........................................................................................................................................................309
8 Parameters...................................................................................................................................311
9 Counters...................................................................................................................................... 344
10 Glossary.....................................................................................................................................350
11 Reference Documents.............................................................................................................351
Issue 01 (2014-04-30)

ix
SingleRAN
1 About This Document
About This Document
1.1 Scope
This document describes the common transmission (co-transmission) solutions on the
multimode base station controller (MBSC) and multimode base station sides and provides
engineering guidelines.
The document involves the following feature on the MBSC side:
l
MRFD-211502 IP-Based BSC and RNC Co-Transmission on MBSC Side
The document involves the following features on the multimode base station side:
l
MRFD-211504 TDM-Based Multi-mode Co-Transmission via Backplane on BS side

(GBTS)
MRFD-211501 IP-Based Multi-mode Co-Transmission on BS side(GBTS)
MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side(NodeB)

(NodeB)
MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)
MRFD-241501 IP-Based Multi-mode Co-Transmission on BS side(LTE TDD)

NOTE
For details about IP transmission, see IP Transmission Feature Parameter Description for SingleRAN.
In this document, the following naming conventions apply for LTE terms.
Issue 01 (2014-04-30)
Includes FDD and TDD
Includes FDD Only
Includes TDD Only
LTE
LTE FDD
LTE TDD
eNodeB
LTE FDD eNodeB
LTE TDD eNodeB
eRAN
LTE FDD eRAN
LTE TDD eRAN

SingleRAN
In addition, the "L" and "T" in RAT acronyms refer to LTE FDD and LTE TDD, respectively.
1.2 Intended Audience

This document is intended for personnel who:
l
Need to understand the features described herein
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
Editorial change
Changes in wording or addition of information that was not described in the earlier version
SRAN9.0 01 (2014-04-30)
This issue does not include any changes.
SRAN9.0 Draft A (2014-01-20)

Compared with 01 (2013-04-28) of SRAN8.0, Draft A (2014-01-20) of SRAN9.0 includes the
following changes.
Issue 01 (2014-04-30)

SingleRAN
Change Type
Change Description
Parameter
Change
Feature change
Added common transmission for the LTE TDD mode.
None
Huawei mobile network management system M2000

is renamed U2000.
Added UMPT+UMPT interconnection. For details,
see the following sections:
l 7.3 Network Planning
l 7.16 Main-Control-Board-based CoTransmission Through Backplane
Interconnection on the Separate-MPT UG+L/
UG+T Multimode Base Station Side in IP over
FE/GE Mode
l 7.24 Reconstruction from Main-ControlBoard-Panel-Interconnection Co-Transmission
on the Separate-MPT UG Multimode Base
Station Side to Main-Control-Board-PanelInterconnection Co-Transmission on the
Separate-MPT UG+L/UG+T Multimode Base
Station Side
l 7.31 Main-control-board -based CoTransmission Through Backplane
Interconnection on the Separate-MPT LGU/
TGU Multimode Base Station Side in IP over
FE/GE Mode
Editorial
change
None.
None
1.4 Differences Between Base Station Types

The features described in this document apply only to macro base stations.
Issue 01 (2014-04-30)

SingleRAN
2 Overview
Overview
2.1 Introduction
This document describes the co-transmission feature in which multiple modes of a GU, GL, UL,
or GUL multimode base station or multimode base station controller share transmission ports
and the transport network.
Table 2-1 lists the definitions of all kinds of base stations.
Table 2-1 Definitions of base stations
Issue 01 (2014-04-30)
Base Station Name
Definition
GBTS
GBTS refers to a base station deployed with

GTMU.
eGBTS
eGBTS refers to a base station deployed with

UMPT_G.
NodeB
NodeB refers to a base station deployed with

WMPT or UMPT_U.
eNodeB
eNodeB refers to a base station deployed with

LMPT or UMPT_L.
Co-MPT Multimode Base Station
Co-MPT multimode base station refers to a

base station deployed with UMPT_GU,
UMPT_GL, UMPT_UL, or UMPT_GUL,
and it functionally corresponds to any
combination of eGBTS, NodeB, and
eNodeB. For example, Co-MPT multimode
base station deployed with UMPT_GU
functionally corresponds to the combination
of eGBTS and NodeB.

SingleRAN
2 Overview
Base Station Name
Definition
Separate-MPT Multimode Base Station
Separate-MPT multimode base station refers

to a base station on which different modes use
different main control boards. For example,
base stations deployed with GTMU and
WMPT are called separate-MPT GSM/
UMTS dual-mode base station.
NOTE
l An MBSC mentioned in this document can be a GU MBSC, BSC, or 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 A multimode base station mentioned in this document can be a GU, GL, UL, GT, UT, or LT dual-mode
base station, a GUL, GUT, GLT, ULT triple-mode base station, or a GULT quadruple-mode base
station. In addition, the GSM side of a multimode base station is referred to as GBTS or eGBTS, the
UMTS side of a multimode base station is referred to as NodeB, and the LTE side of a multimode base
station is referred to as eNodeB in this document. The operation and maintenance (O&M) of a GBTS
is implemented by the BSC while the O&M of an eGBTS is implemented by the eGBTS itself.
2.2 Benefits
Co-transmission reduces the capital expenditure (CAPEX) and operating expense (OPEX) and
simplifies transport network maintenance in the following ways:
l
Sharing transmission ports reduces transmission bearer links.
Sharing the transport network simplifies transmission configuration and maintenance.
A smooth evolution from GSM to UMTS or LTE can be achieved with less transport
network adjustments.
2.3 Usage Scenario

2.3.1 Co-Transmission on the MBSC Side
Figure 2-1 shows the typical usage scenario for co-transmission on the MBSC side.
Issue 01 (2014-04-30)

SingleRAN
2 Overview
Figure 2-1 Typical usage scenario for co-transmission on the MBSC side
As shown in Figure 2-1 , the GSM and UMTS networks share an MBSC. In this situation, cotransmission is achieved 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).
The Iub and Abis interfaces of the MBSC share an IP transport network.
2.3.2 GU/GL/UL/GT/UT/LTGUL/GUT/GLT/ULT/GULT CoTransmission on the Multimode Base Station Side

Multimode base stations are categorized into separate-MPT multimode base stations and coMPT multimode base stations based on the deployment of main processing and transmission
(MPT) boards.
TDM-based co-transmission is supported only by separate-MPT GU multimode base stations.
For details, see section 4.1 TDM-based Co-Transmission.
IP-based co-transmission is supported by separate-MPT and co-MPT multimode base stations.
NOTE
GU: GSM and UMTS

GL: GSM and LTE
UL: UMTS and LTE
GUL: GSM, UMTS, and LTE
IP-based Co-Transmission of the Separate-MPT Multimode Base Station

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 operation and maintenance (O&M) channel.
Issue 01 (2014-04-30)

SingleRAN
2 Overview
Table 2-2 describes different types of co-transmission

Table 2-2 Different types of co-transmission
Co-Transmission Type
Co-transmission through
panel interconnection
Issue 01 (2014-04-30)
Description
Main-control-board-based
co-transmission through
panel interconnection
The main control board of a

mode provides the cotransmission port and the
main control boards of all
modes are connected through
panel interconnection. The
co-transmission port can
either be an FE/GE port or an
E1/T1 port. For details, see
4.2.2 Main-Control-Boardbased Co-Transmission
Through Panel
Interconnection of the
Separate-MPT Multimode
Base Station.
UTRP-based cotransmission through panel

interconnection
The UTRP of a mode

provides the co-transmission
port. The main control boards
of all modes are connected
through panel
interconnection or the main
control boards of other
modes are connected to the
UTRP through panel
interconnection. The cotransmission port can either
be an FE/GE port or an E1/T1
port. For details, see section
4.2.3 UTRP-based CoTransmission Through
Panel Interconnection on
the Separate-MPT
Multimode Base Station
Side.

SingleRAN
2 Overview
Co-Transmission Type
Co-transmission through
backplane interconnection
Description
Main-control-board-based
In this co-transmission mode,

the main control board of a
mode provides the cotransmission port and the
main control boards of all
modes are connected through
backplane interconnection.
The co-transmission port
must be an FE/GE port. For
details, see 4.2.4 MainControl-Board-based CoTransmission Through
Backplane Interconnection
on the Separate-MPT
Side.
UTRPc-based cotransmission through

The UTRPc of a mode

provides the co-transmission
port and the main control
boards of other modes are
connected to the UTRPc
through backplane
interconnection. The cotransmission port must be an
FE/GE port. For details, see
4.2.5 UTRPc-based CoTransmission Through
Backplane Interconnection
on the Separate-MPT
Side.
IP Based Co-Transmission of the Co-MPT Multimode Base Station

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 UMPT and one O&M channel.
The GSM side of a co-MPT multimode base station must be an eGBTS.
The UMPT of a co-MPT multimode base station provides the co-transmission port. The cotransmission port can either be an FE/GE port or an E1/T1 port. The co-transmission port for a
co-MPT GU multimode base station must be an FE/GE port.
Issue 01 (2014-04-30)

SingleRAN
2 Overview
NOTE
This document uses the distributed base station (DBS) as an example to describe the co-transmission on
the base station side. The co-transmission principle for macro base stations is the same as that for DBSs
and therefore is not described in this document.
A multimode base station supports IP-based co-transmission through panel interconnection since
V100R003, supports IP-based co-transmission through backplane interconnection since V100R007, and
supports co-MPT deployment since V100R008.
If the link between the co-transmission port and the transport network is disconnected, services of all modes
are interrupted.
Issue 01 (2014-04-30)

SingleRAN
3 IP-based Co-Transmission on the MBSC Side
IP-based Co-Transmission on the MBSC

Side
This chapter describes the feature MRFD-211502 IP-Based BSC and RNC Co-Transmission on
MBSC Side. Co-transmission on the MBSC side is described in the following topics:
l
Co-transmission for the Iub and Abis interfaces
Co-transmission for the Iu-CS and A interfaces
Co-transmission for the Iu-PS and Gb interfaces
IP-based GU co-transmission differs from IP transmission in the GSM or UMTS in terms of the
network topology and IP address configuration. The following sections describe the network
topologies, protocol stack, and protocol stack application in co-transmission.
Issue 01 (2014-04-30)

10
SingleRAN
3.1 Co-Transmission for the Iub and Abis Interfaces

3.1.1 Network Topologies
When the MBSC operates in GU mode, the Iub and Abis interfaces share the IP transport network
and the physical ports on the interface boards of the MBSC. Figure 3-1 shows the network
topology of the co-transmission in FE/GE/10GE mode. Figure 3-2 shows the network topology
of the 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 for the Iub and Abis interfaces in FE/GE mode on the MBSC side
Figure 3-2 Co-transmission for the Iub and Abis interfaces in IP over E1/T1 mode on the MBSC
side
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
Issue 01 (2014-04-30)

11
SingleRAN
The Abis/Iub 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.
3.1.2 Protocol Stack

Figure 3-3 shows the protocol stack of the IP-based co-transmission for the Iub and Abis
interfaces if the GSM base station is a GBTS.
Figure 3-3 Protocol stack of the 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 is responsible
for protocol processing at the physical layer, data link layer, network layer (IP), and transport
link layer (UDP and UDP MUX). The protocols at other layers are processed on the control
plane processing boards and user plane processing boards of UMTS and GSM separately.
Figure 3-4 shows the protocol stack of the IP-based co-transmission for the Iub and Abis
interfaces if the GSM base station is an eGBTS.
Figure 3-4 Protocol stack of the IP-based co-transmission for the Iub and Abis interfaces (2)
Issue 01 (2014-04-30)

12
SingleRAN
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 the IP-based co-transmission
for the Iub and Abis interfaces:
l
GE optical ports on a GOUa, GOUc or GOUe
FE/GE electrical ports on an FG2a or FG2c
10GE optical ports on a EXOUa
Channelized STM-1/OC-3 optical ports on a POUc or POUa
Data Link Layer

When FE/GE is used in co-transmission for the Iub and Abis interfaces, the Ethernet protocol
is used at the data link layer.
When E1/T1 over STM-1/OC-3 is used in co-transmission for the Iub and Abis interfaces, Pointto-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 and the timeslots must
be carried on the same E1/T1. A PPP link in an MLPPP link group is bound with at least eight
timeslots. In addition, the number of timeslots bound with each PPP link in the MLPPP link
group must be the same. BTS data and NodeB data can be transmitted over different PPP links
or MLPPP link groups. Alternatively, they can be transmitted over the same PPP link or MLPPP
link group, and BTS data and NodeB data are distinguished by UDP port numbers in this
scenario.
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 a port on an interface board. Port IP 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. Control-plane and user-plane IP addresses,
as well as operation and maintenance (OM) channel IP addresses on the Iub and Abis interfaces
can be either port IP addresses or device IP addresses. The IP address planning principles are as
follows:
l
Control-plane and user-plane IP addresses on the Iub interface

On the Iub interface, the control-plane IP address and user-plane IP address can be the same
or different.
Control-plane and user-plane IP addresses on the Abis interface

On the Abis interface, the control-plane IP address can be the same as or different from the
user-plane IP address.
The control-plane IP address and user-plane IP address can be the same or different on the
Iub and Abis interfaces.
Issue 01 (2014-04-30)

13
SingleRAN
OM channel IP address
On the Iub interface,
If the OM channel between the NodeB and the U2000 is established on the MBSC, the
OM channel IP address must be configured on the NodeB and U2000, and the OM
packet forwarding route must be configured on the MBSC. In this scenario, the MBSC
forwards the packets between the U2000 and the NodeB.
If the OM channel between the NodeB and the U2000 is not established on the MBSC,
the OM channel IP address must be configured on the NodeB and U2000.
On the Abis interface, the BTS IP addresses must be configured on the MBSC. If the
BSC is not enabled with the GBFD-118613 BTS Multi-IP Address feature, the OM
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 OM
channel IP address can be different from the control-plane or user-plane IP address of
the GBTS.
3.2 Co-Transmission for the Iu-CS and A Interfaces

When the MBSC operates in GU mode, the Iu-CS and A interfaces can share the IP transport
network and the physical ports on the interface boards of the MBSC. Figure 3-5 shows the
network topology of the co-transmission in FE/GE mode. Figure 3-6 shows the network
topology of the 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 A/Iu-CS 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-5 Co-transmission for the Iu-CS and A interfaces in FE/GE mode
Issue 01 (2014-04-30)

14
SingleRAN
Figure 3-6 Co-transmission for the Iu-CS and A interfaces in E1/T1 over STM-1/OC-3 mode
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 the IP-based co-transmission for the Iu-CS and A
interfaces.
Figure 3-7 Protocol stack of the 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 is responsible
Issue 01 (2014-04-30)

15
SingleRAN

Physical Layer
for the Iu-CS and A interfaces:
l
Channelized STM-1/OC-3 optical ports on a POUa or POUc
Data Link Layer

When FE/GE is used in co-transmission for the Iu-CS and A interfaces, the Ethernet protocol is
used at the data link layer.
When E1/T1 over STM-1/OC-3 is used in co-transmission 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 and the timeslots must be carried on the same E1/T1. A PPP link in an MLPPP link
group is bound with at least eight timeslots. In addition, the number of timeslots bound with
each PPP link in the MLPPP link group must be the same.
Network Layer
Control-plane and user-plane IP addresses on the Iu-CS and A interfaces can be either port IP
addresses or device IP addresses. The Iu-CS and A interfaces can share one port IP address or
use different port IP addresses. It is recommended the 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 share the same control-plane IP address. Generally, the
SCTP link uses two control-plane IP addresses for one interface board. One IP address is
used as the primary IP address and the other one as the secondary IP address. The SCTP
links over the Iu-CS and A interfaces on the MBSC side share the two IP addresses, and
Iu-CS data and A interface data are distinguished by SCTP port numbers in this scenario.
For details about the SCTP links on the Iu-CS and A interfaces, see IP Transmission Feature
Parameter Description .
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, a separate user-plane IP address must
be planned on the Iu-CS interface and A interface to distinguish the data on the Iu-CS
interface from the data on the A interface.
On the Iu-CS interface and the A interface, the control-plane IP address can be the same as the
user-plane IP address.
Issue 01 (2014-04-30)

16
SingleRAN
3.3 Co-Transmission for the Iu-PS and Gb Interfaces

When the MBSC operates in GU mode, the Iu-PS and Gb interfaces can share the IP transport
network and the physical ports on the interface board of the MBSC. The Gb interface does not
support IP over E1; therefore, the co-transmission for the Iu-PS and Gb interfaces is only based
on FE/GE. Figure 3-8 shows the network topology of the FE/GE-based co-transmission for the
Iu-PS and Gb interfaces.
The Gb/Iu-PS interface board on the MBSC identifies and processes the GSM/UMTS data, and
then sends the data to the corresponding GSM/UMTS service processing board and signaling
processing board.
Figure 3-8 Co-transmission for the Iu-PS and Gb interfaces in FE/GE mode
NOTE
IP_GSM: GSM IP address

IP_UMTS: UMTS IP address

Figure 3-9 shows the protocol stack of the IP-based co-transmission for the Iu-PS and Gb
interfaces.
Issue 01 (2014-04-30)

17
SingleRAN
Figure 3-9 Protocol stack of the 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 is responsible

Physical Layer
for the Iu-PS and Gb interfaces:
l
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.
Network Layer
Control-plane and user-plane IP addresses on the Iu-PS and Gb interfaces can be either port IP
addresses or device IP addresses. The Iu-PS and Gb interfaces can share one port IP address or
use different port IP addresses. It is recommended the interfaces use different port IP addresses.
l
Control-plane IP addresses
Generally, the SCTP link uses two control-plane IP addresses for one Iu-PS interface board.
One IP address is used as the primary IP address and the other one as the secondary IP
address. For details about the SCTP links on the Iu-PS interfaces, see IP Transmission
Feature Parameter Description .
Issue 01 (2014-04-30)

18
SingleRAN
No control-plane IP address is assigned on the Gb interface.

l
User-plane IP addresses
The Iu-PS and Gb interfaces can share a IP address or use different IP addresses.
On the Iu-PS interface, the Tunnel End Point Identifier (TEID) at the GPRS Tunneling
Protocol (GTP-U) layer is used to identify users. The GTP-U uses the fixed UDP port 2152.
Issue 01 (2014-04-30)

19
SingleRAN
4 Co-Transmission on the Multimode Base Station Side
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 relates to the
following optional features:
l

(NodeB)

(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 BTS cannot be carried on the coIssue 01 (2014-04-30)

20
SingleRAN
transmission link on the backplane; the OML must be carried on an E1 cable that is connected
to the BTS 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-connect function.
Figure 4-3 TDM timeslot sharing on the Abis interface
NOTE
If TDM-based co-transmission is used and the BTS shares E1/T1 transmission resources to the NodeB, it
is recommended that the E1/T1 clock source be configured on the BTS, and the NodeB uses the E1/T1
clock source provided by the BTS.
4.2 IP-based Co-Transmission

This section relates to the following optional features:
l
MRFD-211501 IP-Based Multi-mode Co-Transmission on BS side(GBTS)
MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side(NodeB)
MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)
MRFD-241501 IP-Based Multi-mode Co-Transmission on BS side(LTE TDD)
Issue 01 (2014-04-30)

21
SingleRAN
4.2.1 Overview
Introduction to Main Control Boards and Universal Transmission Processing Units
Co-transmission ports can be provided by main control boards or universal transmission
processing units of a multimode base station. Table 4-1 lists the main control boards and
universal transmission processing units of a multimode base station.
Table 4-1 Main control boards and universal transmission processing units of a multimode base
station
Board Type
Board Name
Supported
Mode
Description
Main control board
GTMU
GSM
l One 4-route IP over E1/T1

port
l One IP over FE electrical
port, and one IP over FE
optical port
NOTE
There are two types of GTMU
boards: GTMU and GTMUb.
Both the GTMU and GTMUb
support co-transmission
through panel interconnection,
and only the GTMUb supports
WMPT
UMTS
l One 4-route ATM/IP over

E1/T1 port
l One IP over FE electrical
port, and one IP over FE
optical port
LMPT
LTE
l Two IP over FE/GE

electrical ports
l Two IP over FE/GE
optical ports
Issue 01 (2014-04-30)

22
SingleRAN
Board Type
Board Name
Supported
Mode
Description
UMPT
GSM/UMTS/LTE
l One 4-route ATM/IP over

E1/T1 port
l One FE/GE electrical
port, and one FE/GE
optical port
NOTE
UMPTs in the multimode base
stations of V100R007C00 are
only for NodeBs and eNodeBs.
UMPTs in the multimode base
stations of V100R008C00 can
be used for eGBTSs, NodeBs,
eNodeBs, and co-MPT
multimode base stations.
This document refers to the
UMPT on the eGBTS, NodeB,
and eNodeB side of a separateMPT multimode base station as
UMPT_G, UMPT_U,
UMPT_L, UMPT_T,
respectively.
This document refers to the
UMPT of a GU/ GL/GT/UL/
UT/GUL/GUT /GULT co-MPT
multimode base station as
UMPT_GU, UMPT_GL,
UMPT_GT, UMTP_UL,
UMTP_UT, UMPT_GUL,
UMPT_GUT, and
UMPT_GULT, respectively.
Universal
transmission
processing unit
UTRP2
UMTS
Two FE/GE optical ports
UTRP3
UMTS
Two 4-route ATM over E1/

T1 ports
UTRP4
UMTS
Two 4-route IP over E1/T1

ports
UTRPb4
GSM
Two 4-route TDM over E1/

T1 ports
UTRP9
UMTS
Four IP over FE/GE electrical

ports
UTRPc
GSM/UMTS/LTE
Four IP over FE/GE electrical

ports
Two IP over FE/GE optical
ports
Issue 01 (2014-04-30)

23
SingleRAN
NOTE
A co-MPT multimode base station only supports the UTRP2/UTRP3/UTRP4/UTRP9 but not the UTRPb4.
The UTRPs supported by the co-MPT multimode base station carry only UMTS services.
Co-Transmission Networking Scenarios

For co-transmission on the separate-MPT multimode base station side, the main control board
of an advanced RAT has higher processing capabilities than that of the other RAT. Therefore,
the co-transmission port is provided by the eNodeB, NodeB, or BTS in descending order of
priority. Table 4-2 lists the IP-based co-transmission scenarios on the multimode base station
side.
Table 4-2 IP-based co-transmission scenarios on the multimode base station side
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
Separate-MPT
Main-control-boardbased cotransmission through

panel
interconnection
GU
An FE or E1/T1 port
is used as a cotransmission port in
the scenario where an
FE port or E1/T1 port
is used as a cotransmission port,
the WMPT provides
an FE port as the cotransmission port to
be connected to the
MBSC. The GTMU
of the base station is
connected to the
WMPT through FE
port interconnection.
GL/GT
An FE/GE port is
used as a cotransmission port.
The LMPT provides
an FE/GE port as the
co-transmission port
to be connected to the
GBSC, MME, and SGW. The GTMU of
the base station is
connected to the
LMPT through FE
Issue 01 (2014-04-30)

24
SingleRAN
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
UL/UT
An FE/GE port is
The LMPT provides
an FE/GE port as the
co-transmission port
to be connected to the
RNC, MME, and SGW. The WMPT of
the NodeB is
connected to the
LMPT through FE
GUL/GUT
An FE/GE port is
Assume that the BTS
and the NodeB share
one BBU, and the
eNodeB uses another
BBU. The LMPT
provides an FE/GE
port as the cotransmission port to
be connected to the
MBSC, MME, and
S-GW. The GTMU
connected to the
WMPT through FE
interconnection.
WMPT and LMPT
are also connected
through FE port
interconnection.
Issue 01 (2014-04-30)

25
SingleRAN
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
UTRP-based cotransmission through

panel
interconnection
GU
An FE/GE or E1/T1
port is used as a cotransmission port.
Main-control-boardbased cotransmission through

backplane
interconnection
GL/GT
The UTRP provides

an FE/GE or E1/T1
be connected to the
MBSC. The GTMU
connected to the
WMPT through FE
or E1/T1 port
interconnection.
An FE/GE port is
The LMPT/
UMPT_L/UMPT_T
provides an FE/GE
be connected to the
GBSC, MME, and SGW. The GTMUb of
the base station is
connected to the
LMPT/UMPT_L/
UMPT_T through
the backplane.
GU
An FE/GE port is
The UMPT_U
provides an FE/GE
be connected to the
MBSC. The GTMUb
connected to the
UMPT_U through
the backplane.
Issue 01 (2014-04-30)

26
SingleRAN
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
UL/UT
An FE/GE port is
The UMPT_U
provides an FE/GE
be connected to the
RNC, MME, and SGW. The LMPT/
UMPT_L/UMPT_T
is connected to the
UMPT_U through
the backplane.
Issue 01 (2014-04-30)

27
SingleRAN
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
GUL/GUT
An FE/GE port is
l The UMPT_U of
the NodeB
provides an FE/
GE port as the cotransmission port
to be connected to
the MBSC,
MME, and SGW. The
GTMUb of the
BTS is connected
to the UMPT_U
through the
backplane, and
the UMPT_L/
UMTP_T of the
eNodeB is
connected to the
UMPT_U
through the
UCIU.
l The UMPT_L/
UMPT_T of the
eNodeB provides
an FE/GE port as
the cotransmission port
to be connected to
the MBSC,
MME, and SGW. The
GTMUb of the
BTS is connected
to the WMPT
through the
backplane, and
the WMPT of the
NodeB is
connected to the
UMPT_L/
UMPT_T
through the
UCIU.
Issue 01 (2014-04-30)

28
SingleRAN
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
l The UMPT_L/
UMPT_T of the
eNodeB provides
an FE/GE port as
the cotransmission port
to be connected to
the MBSC,
MME, and SGW. The
GTMUb of the
BTS is connected
to the UMPT_L/
UMPT_T
through the
backplane, and
the UMPT_L/
UMPT_T of the
eNodeB is
connected to the
UMPT_U
through the
UCIU.
l The UMPT_U of
the NodeB
provides an FE/
GE port as the cotransmission port
to be connected to
the MBSC,
MME, and SGW. The
GTMUb of the
BTS is connected
to the LMPT
through the
backplane, and
the LMPT of the
eNodeB is
connected to the
UMPT_U
through the
UCIU.
Issue 01 (2014-04-30)

29
SingleRAN
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
UTRPc-based cotransmission through

backplane
interconnection
GU
An FE/GE port is
The UTRPc is
managed by the
WMPT/UMPT_U of
the NodeB and
provides an FE/GE
be connected to the
MBSC. The GTMUb
is connected to the
UTRPc through the
backplane.
UL/UT
An FE/GE port is
The UTRPc is
managed by the
LMPT/UMPT_L of
the eNodeB and
provides an FE/GE
be connected to the
RNC, MME, and SGW. The WMPT/
UMPT_U/UMPT_T
is connected to the
UTRPc through the
backplane.
Issue 01 (2014-04-30)

30
SingleRAN
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
GUL/GUT
An FE/GE port is
The UTRPc is
managed by the
WMPT/UMPT_U of
the NodeB and
provides an FE/GE
be connected to the
MBSC, MME, and
S-GW. The GTMUb
connected to the
UTRPc through the
backplane, and the
UMPT_L/UMPT_T
of the eNodeB is
connected to the
UTRPc through the
UCIU.
Co-MPT
GU/UL/GL/GT/UT/
LT/GUL/GUT/GLT/
ULT/GULT
For the GU
multimode base
station, an E1/T1 or
FE/GE port is used as
a co-transmission
port.
For the UL/GL/GT/
UT/LT/GUL/GUT/
GLT/ULT/GULT
multimode base
station, an FE/GE
port is used as a cotransmission port.
The co-transmission
port connects the
base station and the
MBSC, MME, and
S-GW.
Issue 01 (2014-04-30)

31
SingleRAN
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.
A GTMUb board cannot transmit or receive a packet whose size is larger than 1500 bytes if co-transmission
is achieved through backplane interconnection.
Only the UTRPc supports co-transmission through backplane interconnection.
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 BTS 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 cotransmission 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 separateMPT 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 4.2.2 Main-Control-Board-based Co-Transmission Through Panel

Interconnection of the Separate-MPT Multimode Base Station, the WMPT of the NodeB
provides an FE port as the co-transmission port, and the GTMU is connected to the WMPT
through FE port interconnection. In this case, uplink data of the BTS is transmitted from the
GTMU to the WMPT and then to the IP transport network, and downlink data to the BTS is
transmitted from the IP transport network to the WMPT and then to the GTMU.
Issue 01 (2014-04-30)

32
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 FE port interconnection. In this case,
uplink data of the BTS is transmitted from the GTMU to the LMPT and then to the IP transport
network, and downlink data to the BTS 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 cotransmission 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 port interconnection. The WMPT
uses MLPPP to bind E1 links. In this case, uplink data of the BTS is transmitted from the GTMU
to the WMPT and then to the IP transport network, and downlink data to the BTS is transmitted
from the IP transport network to the WMPT and then to the GTMU.
Issue 01 (2014-04-30)

33
SingleRAN
4.2.3 UTRP-based Co-Transmission Through Panel

Interconnection on the Separate-MPT Multimode Base Station Side
The following passages use 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 cotransmission port, and the GTMU is connected to the UTRP2 through panel port interconnection.
In this case, uplink data of the BTS is transmitted from the GTMU to the UTRP2, and downlink
data to the BTS is transmitted from the UTRP2 to the GTMU.

The following passages use 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-8shows 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 port interconnection. The UTRP4 uses
MLPPP to bind E1 timeslots. In this case, uplink data of the GBTS is transmitted from the 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.
Issue 01 (2014-04-30)

34
SingleRAN
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 shown in Table 4-3.
Table 4-3 Main control board configuration of a separate-MPT multimode base station
Separate-MPT
Main Control Board

Configuration
Board Recommended to
Provide a CoTransmission Port
GU
GTMUb+UMPT_U
UMPT_U
GL/GT
GTMUb+UMPT_L/
UMPT_T/LMPT
LMPT/UMPT_L
UL/UT
WMPT+ LMPT
LMPT
WMPT+UMPT_L/
UMPT_T
UMPT_L/UMPT_T
UMPT_U+UMPT_L/
UMPT_T
UMPT_U
UMPT_U+LMPT
UMPT_U
GTMUb+ UMPT_U+
UMPT_L/UMPT_T
UMPT_U
GTMUb+ WMPT+
UMPT_L/UMPT_T
UMPT_L/UMPT_T
GTMUb+ UMPT_L/
UMPT_T+UMPT_U
UMPT_L/UMPT_T
GTMUb+ LMPT+UMPT_U
UMPT_U
GU+L/GU+T
GL/GT+U
Figure 4-9 uses the separate-MPT GL multimode base station as an example to show the maincontrol-board-based co-transmission through backplane interconnection.
Issue 01 (2014-04-30)

35
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 communicate through the backplane. In
this case, uplink data of the BTS is transmitted from the GTMUb to the LMPT and then to the
IP transport network, and downlink data to the BTS is transmitted from the IP transport network
to the LMPT 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 corresponding main control board, and is uniquely numbered within the corresponding
mode. Tunnels of different modes can have the same number. Here uses the network structure in Figure
4-9 as an example. The tunnel from the GTMUb to the LMPT is configured by running the ADD
BTSTUNNEL command on the GSM side, and the tunnel from the LMPT to the GTMUb is configured
by running the ADD TUNNEL command on the LTE side.
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 multimode 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-10 shows the UTRPc-based co-transmission through backplane interconnection on the
GU/UL multimode base station side as an example.
Issue 01 (2014-04-30)

36
SingleRAN
Figure 4-10 UTRPc-based co-transmission through backplane interconnection on the GU/UL

separate-MPT multimode base station side
As shown in Figure 4-10, 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.
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.
Each tunnel is managed only by the mode of the corresponding board, and is uniquely numbered within
the corresponding mode. Tunnels of different modes can have the same number. Use the network structure
in Figure 4-10 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 multimode base station side, two BBUs are required and they must be connected
through a Universal Cascading Interface Unit (UCIU). Figure 4-11 shows the UTRPc-based
co-transmission through backplane interconnection on the separate-MPT GUL multimode base
station side as an example.
Issue 01 (2014-04-30)

37
SingleRAN
Figure 4-11 UTRPc-based co-transmission through backplane interconnection on the separateMPT GUL multimode base station side
As shown in Figure 4-11, 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. During the main control board
reset or hot patch installation 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, then slot 0.
4.2.6 Co-Transmission on the Co-MPT Multimode Base Station

Side
In IP over FE/GE mode, the UMPT of the co-MPT GU/GL /UL/GT/UT/LT/GUL/GUT/ULT/
GULT multimode base station provides an FE/GE port as the co-transmission port. The
following paragraphs use the co-MPT GUL multimode base station as an example to describe
the co-transmission on the co-MPT multimode base station side in IP over FE/GE mode. Figure
4-12 shows the co-transmission on the co-MPT GUL multimode base station side in IP over FE/
GE mode.
Issue 01 (2014-04-30)

38
SingleRAN
Figure 4-12 Co-transmission on the Co-MPT GUL multimode base station side in IP over FE/
GE mode
NOTE
If the co-transmission on the Co-MPT GUL multimode base station side is in IP over FE/GE mode, each
mode uses the same OM IP address but different service IP addresses.

In IP over E1/T1 mode, the UMPT of the co-MPT GU multimode base station provides an E1/
T1 port as the co-transmission port. Figure 4-13 shows the co-transmission on the co-MPT GU
multimode base station side in IP over E1/T1 mode.
Figure 4-13 Co-transmission on the Co-MPT GUL multimode base station side in IP over E1/
T1 mode
Issue 01 (2014-04-30)

39
SingleRAN
5 Related Features
Related Features
5.1 Features Related to IP-based Co-Transmission on the

MBSC Side
Prerequisite Features
Co-transmission on the MBSC side depends on the following features:
l
IP-based co-transmission for the Abis and Iub interfaces

GBFD-118601 Abis over IP or GBFD-118611 Abis IP over E1/T1
WRFD-050402 IP Transmission Introduction on Iub Interface
IP-based co-transmission for the A and Iu-CS interfaces

GBFD-118602 A over IP or GBFD-118622 A IP over E1/T1
WRFD-050409 IP Transmission Introduction on Iu Interface
IP-based co-transmission for the Gb and Iu-PS interfaces

GBFD-118603 Gb over IP
Mutually Exclusive Features

None
Impacted Features
None
5.1.1 Prerequisite Features

Co-transmission on the MBSC side depends on the following features:
l
IP-based co-transmission for the Abis and Iub interfaces

GBFD-118601 Abis over IP or GBFD-118611 Abis IP over E1/T1
Issue 01 (2014-04-30)

40
SingleRAN
5 Related Features

l
IP-based co-transmission for the A and Iu-CS interfaces

GBFD-118602 A over IP or GBFD-118622 A IP over E1/T1
IP-based co-transmission for the Gb and Iu-PS interfaces

GBFD-118603 Gb over IP
5.1.2 Mutually Exclusive Features

None
5.1.3 Affected Features

None
5.2 Features Related to Co-Transmission on the Multimode

Base Station Side
Prerequisite Features
Co-transmission on the base station side depends on different features in different modes:
l
In GSM mode:
GBFD-118601 Abis over IP
In UMTS mode:
WRFD-050302 Fractional ATM Function on Iub Interface
WRFD-050411 Fractional IP Function on Iub Interface
In LTE mode:
None
Mutually Exclusive Features

None
Impacted Features
None
5.2.1 Prerequisite Features

Co-transmission on the base station side depends on different features in different modes:
l
In GSM mode:
Issue 01 (2014-04-30)

41
SingleRAN
5 Related Features
In UMTS mode:
In LTE mode:
None
5.2.2 Mutually Exclusive Features

This feature and the TDLOFD-001134 Virtual Routing & Forwarding feature (LTE TDD) are
mutually exclusive.
5.2.3 Affected Features

None
Issue 01 (2014-04-30)

42
SingleRAN
6 Impact on the Network
Impact on the Network
6.1 IP-based Co-Transmission on the MBSC Side

System Capacity
No impact.
Network Performance
No impact.
6.1.1 Impact on System Capacity

No impact.
6.1.2 Impact on Network Performance

No impact.
6.2 Co-Transmission on the Multimode Base Station Side

Impact on System Capacity
No impact.
Impact on Network Performance

No impact.
6.2.1 Impact on System Capacity

No impact.
Issue 01 (2014-04-30)

43
SingleRAN
6 Impact on the Network
6.2.2 Impact on Network Performance

No impact.
Issue 01 (2014-04-30)

44
SingleRAN
7 Engineering Guidelines
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, the UG multimode base
station indicates that the NodeB provides the co-transmission port. The UGL multimode base
station indicates that the NodeB provides the co-transmission port, the NodeB and the BTS share
one BBU, and the eNodeB uses an independent BBU.
This chapter uses LTE FDD as an example. Engineering guidelines are the same for LTE TDD
and LTE FDD, therefore those for the LTE TDD are not described in this chapter.
MRFD-241501 IP-Based Multi-mode Co-Transmission on BS side(LTE TDD) is under license
control.
Issue 01 (2014-04-30)
Feature
ID
Feature
Name
License Control Item
NE
Sales Unit
MRFD-24
1501
IP-Based
Multimode CoTransmissi
on on BS
side(LTE
TDD)
IP-Based Multi-mode CoTransmission on BS side

(TDD)
eNodeB
per eNodeB

45
SingleRAN
7.1 When to Use Co-Transmission

7.1.1 IP Co-Transmission on the MBSC Side
It is recommended that co-transmission in IP over FE/GE mode be enabled over the Abis and
Iub interfaces on the MBSC side during the evolution of a base station controller from singlemode to multi-mode. This section describes the engineering guidelines for IP co-transmission
for Iub and Abis interfaces on the MBSC side.
7.1.2 Co-Transmission on the Multimode Base Station Side

Both TDM and IP co-transmissions are supported on the base station side.
l
IP-based co-transmission
It is recommended that co-transmission in IP over FE/GE mode be enabled during the
evolution of a base station from single-mode to multimode or from multimode to multimode
when IP is used for the transport network.
For details about deploying the co-transmission on the separate-MPT multimode base
station side in IP over FE/GE mode, see section 7.5 Main-Control-Board-based CoTransmission Through Panel Interconnection on the Separate-MPT UG
Multimode Base Station Side in IP over FE/GE Mode and section Reconstruction
from Main-Control-Board-based Co-Transmission Through Panel Interconnection on
the Separate-MPT UG Multimode Base Station Side to Main-Control-Board-based CoTransmission Through Backplane Interconnection on the Separate-MPT UG+L
Multimode Base Station Side.
For details about deploying the co-transmission on the separate-MPT multimode base
station side in IP over E1/T1 mode, see section 7.25 Main-Control-Board-based CoTransmission Through Panel Interconnection on the Separate-MPT UG
Multimode Base Station Side in IP over E1/T1 Mode and section 7.26 UTRP4-based
Co-Transmission Through Panel Interconnection on the Separate-MPT UG
Multimode Base Station Side in IP over E1/T1 Mode.
For details about deploying the co-transmission on the co-MPT multimode base station
in IP over FE/GE mode, see section 7.28 Co-Transmission on the Co-MPT GU/GL/
UL/GT/UT/LT Multimode Base Station Side in IP over FE/GE Mode
TDM-based co-transmission
TDM-based co-transmission can be enabled only on separate-MPT GU multimode base
stations when TDM is used for the transport network. For details about deploying TDMbased co-transmission on the separate-MPT GU dual mode base station side, see section
"7.27 GTMU-based TDM Co-Transmission on the Separate-MPT GU Multimode
Base Station Side".
7.2 Information to Be Collected

None
Issue 01 (2014-04-30)

46
SingleRAN
7.3 Network Planning

RF Planning
N/A
Network Topology
l
Determine the RAT used by the base station that provides the co-transmission port. Due to
differences in transmission specifications between RATs used for multimode base stations,
it is recommended that the RAT used by the base station that provides the co-transmission
port be determined based on the following priorities in descending order: LTE > UMTS >
GSM.
Determine whether to use panel interconnection or backplane interconnection between

RATs for co-transmission. Multimode base stations of versions earlier than V100R007C00
support panel interconnection, while V100R007C00 and later support both panel
interconnection and backplane interconnection.
Determine the transmission bandwidth. It is recommended that transmission bandwidth for

each RAT be determined based on the actual traffic model.
Plan transmission parameters, including IP address, route (network segment route or host
route), virtual local area network (VLAN), SCTP link, IP path, 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.
A UTRPc is required when UTRPc-based co-transmission is implemented through

For co-transmission on a triple-mode base station, UCIU+UMPT interconnection or UMPT

+UMPT interconnection can be used to connect two BBUs.
For details about the slots available for newly added boards, see BBU Hardware Description in
the 3900 Series Base Station Product Documentation. This document only provides instances
of slots in which boards are installed in different scenarios.
7.4 Co-Transmission for Iub and Abis Interfaces on the

MBSC Side
7.4.1 Deployment Requirements
l
Deployment objective
One FE/GE or E1/T1 port on an interface board on the MBSC side is used to connect to
both the BTS and the NodeB. When co-transmission is enabled for the Iub and Abis
interfaces on the MBSC side, co-transmission is optional for both the BTS and the NodeB.
Issue 01 (2014-04-30)

47
SingleRAN
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.
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
Requirement for other features

The following features have been enabled:
Requirements for the license

The following license has been activated:
Issue 01 (2014-04-30)

48
SingleRAN
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
MBSC
IP-Based 2G/
3G CoTransmission
on MBSC Side
Function
LGW1COIPT
R
81201141
Per TRX
Per Mbit/s
Per Erl
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 in IP over FE/GE mode
for the Iub and Abis interfaces on the MBSC side.
Issue 01 (2014-04-30)

49
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 BTS 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 BTS 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, BTS, and NodeB.
Issue 01 (2014-04-30)

50
SingleRAN
Table 7-1 IP address plan

Item
Instance
Remarks
Device IP address of the

MBSC
10.10.10.10/32
Logical IP addresses of the

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 MBSC
21.21.21.1/24
Physical IP addresses of the

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.
Issue 01 (2014-04-30)
IP address of the port on the

router that is directly
connected to the MBSC
21.21.21.254/24
Port IP address of the NodeB
30.30.30.11/24
Port IP address of the BTS
20.20.20.188/24
Port IP address of the router

that is directly connected to
the NodeB
30.30.30.12/24

router that is directly
connected to the BTS
20.20.20.189/24

51
SingleRAN
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, BTS, and NodeB.
Issue 01 (2014-04-30)
Item
Instance
Remarks

MBSC
10.10.10.10/32
Logical IP addresses of the

on the MBSC side
Port IP address of the MBSC
21.21.21.1/24
Physical IP addresses of the

on the MBSC side
Port IP address of the NodeB
21.21.21.11/24
The MBSC terminates

messages that are compliant
with the Point-to-Point
Protocol (PPP)/Multi-Link

52
SingleRAN
Item
Instance
Remarks
Port IP address of the BTS
21.21.21.188/24
Point-to-Point Protocol
(MLPPP) from the NodeB or
BTS. Therefore, the port IP
addresses of the MBSC,
NodeB, and BTS 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 is
in IP over FE/GE mode, connect the FE/GE port on the Abis/Iub interface board to the next-hop
router. When co-transmission is in IP over E1/T1 mode, 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.
7.4.6 Activation Observation

Step 1 Run the MBSC MML command PING IP to ping the port IP address of the BTS or NodeB. If
the port IP address can be pinged, the transmission link between the MBSC and the BTS/NodeB
is normal.
Issue 01 (2014-04-30)

53
SingleRAN
PING IP: SRN=0, SN=16, SIPADDR="10.10.10.10", DESTIP="30.30.30.11", CONTPING=NO;

----End

Step 1 Run the MBSC MML command PING IP to ping the port IP address of the BTS or NodeB. If
the port IP address can be pinged, the transmission link between the MBSC and the BTS/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
l
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 dual mode base station and is connected to the MBSC. The GTMU of the BTS is
interconnected to the WMPT of the NodeB through FE ports.
Figure 7-5 Main-control-board-based IP co-transmission through panel interconnection on
the separate-MPT UG multimode base station side

Issue 01 (2014-04-30)

54
SingleRAN

The license is not required.

(Example) Key Data Preparation
Figure 7-6 shows an example of network topology for main-control-board-based IP cotransmission 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.

Issue 01 (2014-04-30)
Item
Instance
Remarks
Device IP address of the BSC
10.10.10.10/32
Port IP address of the BSC
21.21.21.1/24

RNC
11.11.11.11/32
Port IP address of the RNC
23.23.23.1/24

router that is connected to the
BSC
21.21.21.254/24

RNC
23.23.23.254/24

55
SingleRAN
Item
Instance
Remarks
IP address of FE port 1 on the

NodeB (FE port 1 is used for
interconnecting the NodeB to
the BTS.)
30.30.30.1/24
UMTS: device IP address

during configuration on the
CME

NodeB
20.20.20.188/24

CME

NodeB
20.20.20.1/24

BTS (FE port 0 is used for
interconnecting the BTS to
the NodeB.)
30.30.30.188/24
GSM: device IP address

CME
NOTE
IP addresses of two ports used for interconnecting the NodeB to the BTS 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 BTS.
Data Preparation on the GSM Side

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSIPRT
Forward Route
Address
NEXTHOP
Forward Route
Address
IPRT
Forward route
address
NEXTHOP
Forward route
address
Data Preparation on the UMTS Side
Issue 01 (2014-04-30)
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
ETHPORT
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type

56
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Port No.
PN
Port No.
Maximum
Transmission Unit
MTU
Maximum
Transmission Unit
Speed
SPEED
Speed
Duplex
DUPLEX
Duplex
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Next Hop IP
IFT
Next Hop IP
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWITC
H
DHCP Relay
Switch
ES
DHCP Switch
VLANMAP
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
DEVIP
IPRT
Issue 01 (2014-04-30)

57
SingleRAN
MO
VLANCLASS
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
7.5.3 Precautions
None

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
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 configuration steps described in 3900 Series Base Station Initial
Configuration Guide, perform the following steps:
l
Issue 01 (2014-04-30)
Using MML Commands

58
SingleRAN
Step 1 When configuring a route from the BTS 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 BTS to the BSC is
ADD BTSIPRT.
Step 2 (Optional) Configure two routes to the DHCP relay of the BTS 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 other route
to the lower-level transmission port. The BSC MML command for configuring the route to the
DHCP relay of the BTS is ADD IPRT.
----End
l
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the Data Preparation on the GSM Side section.
For instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.
Initial Configuration on the UMTS Side

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 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, 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 BTS are on the same network segment.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="30.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 BTS 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="20.20.20.1", PREF=60;
Step 4 (Optional) Add a downlink route from the BSC to the BTS through the NodeB.
The downlink route is required only if the logical IP address is used by the BTS. If the physical
port IP address is used by the BTS and the IP addresses of the panel interconnection ports on
the NodeB and the BTS are on the same network segment as the port IP address of the BTS, the
downlink route from the NodeB to the BTS is not required.
Step 5 (Optional) Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
Issue 01 (2014-04-30)

59
SingleRAN
When co-transmission is enabled for the BTS and NodeB, if the BTS 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.
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 BTS, 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.
ADD DHCPSVRIP: DHCPSVRIP="10.10.10.10";
//Add the IP address of the DHCP server for the BTS.
Step 7 (Optional) Configure VLAN. There are two methods of configuring differentiated VLAN data
for the BTS and NodeB:
l Method 1 (Recommended): Configure differentiated next-hop addresses. Specifically, the
uplink route from the BTS 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, 20.20.20.100) to the NodeB port connecting to the BSC so that the data from the
GBTS can be transmitted through different routes. In addition, you need to configure a
different next-hop address for the uplink route from the GBTS to the BSC through the NodeB,
for example, you can set the next-hop address of the uplink route from the GBTS to the BSC
through the NodeB to 20.20.20.101, which is different from the next-hop address (20.20.20.1)
of the uplink route for the NodeB. To add VLAN mapping, run the MML command ADD
VLANMAP
ADD VLANMAP: NEXTHOPIP="20.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 BTS and NodeB. For details about
DSCP values for the BTS and NodeB, see Bandwidth Sharing of Multimode Base Station
Co-Transmission Feature Parameter Description.
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 BTS 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.

VLANGROUP, VLANGROUPNO=1, SETPRIO=DISABLE;
//Configure the mapping between a VLAN group and the next hop.
----End
Issue 01 (2014-04-30)

60
SingleRAN

On the CME, set the parameters 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.

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 ping 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="20.20.20.188", DSTIP="10.10.10.10",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
----End
GSM Side
After the configuration file is delivered to the BTS and activated, perform the following step on
the BSC side to check whether the transmission link between the BSC and the BTS is normal:
Step 1 Run the BSC MML command PING IP to ping the IP link between the GTMU on the BTS and
the BSC. If the IP address can be pinged, the IP link is normal.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="30.30.30.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End

Panel Interconnection on the Separate-MPT LU/TU
Multimode Base Station Side in IP over FE/GE Mode
l
interconnection on the separate-MPT LU 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 LU multimode base station and is connected to the RNC and mobility
Issue 01 (2014-04-30)

61
SingleRAN
management entity (MME)/serving gateway (S-GW). The NodeB is interconnected to the

eNodeB through FE ports.
the separate-MPT LU multimode base station side

The following feature has been enabled:

NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

Figure 7-8 shows an example of network topology for main-control-board-based IP cotransmission through panel interconnection on the separate-MPT LU multimode base station
side.
Issue 01 (2014-04-30)

62
SingleRAN

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

Issue 01 (2014-04-30)
Item
Instance
Remarks

RNC
10.10.10.10/32
21.21.21.1/24

RNC
21.21.21.254/24
UMTS: next hop to the

NodeB route

eNodeB
20.20.20.1/24
LTE: next hop of the route

from the eNodeB to the SGW on the S1 interface and
next hop of the route from the
eNodeB to the MME on the
S1 interface

eNodeB (FE port 1 is used for
interconnecting the eNodeB
to the NodeB.)
30.30.30.1/24
LTE: device IP address

CME

eNodeB
20.20.20.188/24

CME
IP address of the MME
40.40.40.40/24
LTE: peer IP address for the

SCTP link

63
SingleRAN
Item
Instance
Remarks
IP address of the S-GW
50.50.50.50/24

IP path

to the NodeB.)
30.30.30.188/24
IP address of the U2000
70.70.70.70/24
IP address of the U2000 or

DHCP server
NOTE
IP addresses of two Ethernet ports used for interconnecting the eNodeB to the NodeB 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 Ethernet ports used for interconnecting the eNodeB to the NodeB.

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
IPRT
Route Index
VRFIDX
Route Index
Next Hop IP
NEXTHOP
Next Hop IP
Data Preparation on the eNodeB Side
Issue 01 (2014-04-30)
MO
MML Parameter Name
MML Parameter ID
CME Parameter
Name
ETHPORT
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port No.
PN
Port No.
Port Attribute
PA
Port Attribute
Speed
SPEED
Speed
Duplex
DUPLEX
Duplex

64
SingleRAN
MO
MML Parameter Name
MML Parameter ID
CME Parameter
Name
DEVIP
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Port No.
DHCPSVR
IP
DHCP Server IP Address
DHCPSVRIP
DHCP Server IP
Address
DHCPREL
AYSWITC
H
DHCP Relay Switch
ES
DHCP Relay
Switch
VLANMA
P
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Priority
VLANPRIO
VLAN Priority
IPRT
Issue 01 (2014-04-30)

65
SingleRAN
MO
VLANCLA
SS
MML Parameter Name
MML Parameter ID
CME Parameter
Name
VLAN Group No.
VLANGROUPNO
VLAN Group No.
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
7.6.3 Precautions
None

Table 7-6 Panel interconnection modes
Base Station
Mode
LU
Mode 1: An outbound electrical port on the LMPT is connected to the

RNC and MME/S-GW, and an outbound optical port on the LMPT is
connected to an optical port on the WMPT.
Mode 2: An outbound optical port on the LMPT is connected to the RNC
and MME/S-GW, and an outbound electrical port on the LMPT is
connected to an electrical port on the WMPT.
Mode 3: An outbound electrical port on the LMPT is connected to the
RNC and MME/S-GW, and an outbound electrical port on the LMPT
is connected to an electrical port on the WMPT.
Mode 4: An outbound optical port on the LMPT is connected to the RNC
and MME/S-GW, and an outbound optical port on the LMPT is
connected to an optical port on the WMPT.
Issue 01 (2014-04-30)

66
SingleRAN

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

Documentation. In addition to the configuration steps described in 3900 Series Base Station
Initial Configuration Guide, perform the following steps:
l
Using MML Commands

When configuring a route from the NodeB to the RNC, 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 LMPT. The NodeB MML command for configuring the route
from the NodeB to the RNC is ADD IPRT.

On the CME, set the parameters listed in the Data Preparation on the UMTS Side section.
Initial Configuration on the LTE Side

l
Using MML Commands
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: SN=6, SBT=BASE_BOARD, PN=1, PA=COPPER, SPEED=AUTO, DUPLEX=AUTO;
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 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.
MASK="255.255.255.0";
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 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.
Issue 01 (2014-04-30)

67
SingleRAN

//Add a route from the eNodeB to the RNC.
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 (Optional) Run the eNodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay. When co-transmission is enabled for the NodeB and eNodeB, if the NodeB is deployed
using DHCP, the NodeB 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 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 IP address of the DHCP server is the IP
address of the RNC or U2000. In this step, assume that the U2000 works as the DHCP server.
//Add the IP address of the DHCP server for the NodeB.
for the NodeB and eNodeB:
----End
l
Method 1 (Recommended): Configure differentiated next-hop addresses. Specifically, 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 NodeB to the RNC through the eNodeB to
20.20.20.101, which is different from the next-hop address (20.20.20.1) of the uplink route
for the eNodeB. To add VLAN mapping, run the MML command ADD VLANMAP
ADD VLANMAP: NEXTHOPIP="20.20.20.101", MASK="255.255.255.0",
VLANMODE=SINGLEVLAN, VLANID=22, SETPRIO=DISABLE;
Method 2 (Not recommended): Configure differentiated DSCP values. This method

requires differentiated DSCP values for the NodeB and eNodeB. For details about DSCP
values for the NodeB and eNodeB, see Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description.
1.
Run the eNodeB 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 differentiated data needs to be configured for the eNodeB and NodeB and
TRAFFIC is set to USERDATA, SRVPRIO cannot be set to 40 on the eNodeB.
//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.
Issue 01 (2014-04-30)

68
SingleRAN
2.
Run the eNodeB MML command ADD VLANMAP.

VLANMODE=VLANGROUP, VLANGROUPNO=1;

On the CME, set the parameters listed in the Data Preparation on the eNodeB Side
section. For instructions on how to perform the CME single configuration, see CME Single

device.
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.
----End
UMTS Side
on the RNC side to verify whether the transmission link between the RNC and the NodeB is
normal:
Step 1 Run the RNC MML command PING IP to ping the IP address of the WMPT.
----End

Panel Interconnection on the Separate-MPT LG/TG
l
interconnection on the separate-MPT LG multimode base station side. In this scenario, an
Issue 01 (2014-04-30)

69
SingleRAN
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/SGW. The BTS is interconnected to the eNodeB through FE ports.
the separate-MPT LG multimode base station side


NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

Figure 7-10 shows an example of network topology for main-control-board-based IP cotransmission through panel interconnection on the separate-MPT LG multimode base station
side.
Issue 01 (2014-04-30)

70
SingleRAN

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

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

BSC
21.21.21.254/24

eNodeB
20.20.20.1/24

to the BTS.)
30.30.30.1/24

CME

eNodeB
20.20.20.188/24

CME
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path

the eNodeB.)
30.30.30.188/24

71
SingleRAN
NOTE
IP addresses of two Ethernet ports used for interconnecting the eNodeB to the BTS 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 BTS.

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSIPRT
Forward Route
Address
NEXTHOP
Forward Route
Address
IPRT
Forward route
address
NEXTHOP
Forward route
address
Data Preparation on the LTE Side

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
ETHPORT
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port No.
PN
Port No.
Port Attribute
PA
Port Attribute
Speed
SPEED
Speed
Duplex
DUPLEX
Duplex
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Cabinet No.
CN
Cabinet No.
DEVIP
IPRT
Issue 01 (2014-04-30)

72
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Port Type
Mask
DSTMASK
Port No.
Route Type
RTTYPE
Route Type
Port Type
IFT
IP Address
Next Hop IP
NEXTHOP
Mask
Port No.
IFNO
Port No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Relay Switch
VLANMAP
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Priority
VLANPRIO
VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
VLANCLASS
7.7.3 Precautions
None
Issue 01 (2014-04-30)

73
SingleRAN

Base Station
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 connected
Mode 2: An outbound optical port on the LMPT is connected to the BSC
connected to an electrical port on the GTMU.
Mode 3: An outbound electrical port on the LMPT is connected to the BSC
connected to an electrical port on the GTMU.
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 connected

l
Using MML Commands
from the IP address of the directly connected router to the IP address of interconnection port on
the LMPT. The BSC MML command for configuring the route from the BTS to the BSC is
ADD BTSIPRT.
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 BTS is ADD IPRT.
----End
l
Issue 01 (2014-04-30)

74
SingleRAN

l
Using MML Commands
the LMPT that is used for interconnecting to the GTMU.
SET ETHPORT: SN=7, SBT=BASE_BOARD, PN=1, PA=COPPER, SPEED=AUTO, DUPLEX=AUTO;
for interconnecting the LMPT to the GTMU.
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 BTS are on the same network segment.
MASK="255.255.255.0";
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 BTS 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 BTS to the BSC through the eNodeB.
Step 4 (Optional) Add a downlink route from the BSC to the BTS through the eNodeB.
the eNodeB and the BTS are on the same network segment as the port IP address of the BTS,
the downlink route from the eNodeB to the BTS is not required.
Step 5 (Optional)Run the eNodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
When co-transmission is enabled for the BTS and eNodeB, if the BTS is deployed using DHCP,
the eNodeB needs to work as the relay. Therefore, DHCP relay needs to be enabled 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 BTS and eNodeB, the eNodeB needs to work as the
relay if the BTS is deployed using DHCP. Therefore, the IP address of the DHCP server needs
to be added on the eNodeB. For the BTS, the IP address of the DHCP server is the IP address
Issue 01 (2014-04-30)

75
SingleRAN
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.
for the BTS and eNodeB:
uplink route from the BTS 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 BTS to the BSC through the eNodeB to 20.20.20.101, which is different
from the next-hop address (20.20.20.1) of the uplink route for the eNodeB. To add VLAN
mapping, run the MML command ADD VLANMAP
l Method 2 (Not recommended): Configure differentiated DSCP values. This method requires
differentiated DSCP values for the BTS and eNodeB. For details about DSCP values for the
BTS and eNodeB, see Bandwidth Sharing of Multimode Base Station Co-Transmission
Feature Parameter Description.
1.

set TRAFFIC to USERDATA for all passerby flows through the eNodeB. If
differentiated data needs to be configured for the eNodeB and BTS and TRAFFIC
is set to USERDATA, SRVPRIO cannot be set to 40 on the eNodeB.
2.

ADD VLANMAP: NEXTHOPIP="20.20.20.1", MASK="255.255.255.0", VLANMODE=VLANGROUP,
VLANGROUPNO=1;
----End
l

On the CME, set the parameters listed in the Data Preparation on the LTE Side section.

device.
LTE Side
on the eNodeB side to verify whether the transmission link between the eNodeB and the MME/
S-GW is normal:
Issue 01 (2014-04-30)

76
SingleRAN
----End
GSM Side
the BSC side to verify whether the transmission link between the BSC and the BTS is normal:
Step 1 Run the BSC MML command PING IP to ping the IP address of the GTMU.
----End

Panel Interconnection on the Separate-MPT LGU/TGU
l
interconnection on the separate-MPT UGL multimode base station side. In this scenario,
main-control-board-based IP co-transmission through panel interconnection on the
separate-MPT UGL multimode base station side is enabled by cascading FE ports on the
panels in different subracks. The BTS and NodeB are cascaded in one BBU subrack through
the panel where FE ports are located, while the eNodeB uses another BBU subrack. The
BTS and NodeB are interconnected 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 cotransmission port of the separate-MPT GUL multimode base station and is connected to
the MBSC and MME/S-GW. The GTMU of the BTS is interconnected to the WMPT of
the NodeB through FE ports.
Issue 01 (2014-04-30)

77
SingleRAN
Figure 7-11 Main-control-board-based IP co-transmission through panel interconnection on the

separate-MPT UGL multimode base station side


NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

Figure 7-12 shows an example of network topology for main-control-board-based IP cotransmission through panel interconnection on the separate-MPT UGL multimode base station
side.
Issue 01 (2014-04-30)

78
SingleRAN

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

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

RNC
11.11.11.11/32
23.23.23.1/24

BSC
21.21.21.254/24

RNC
23.23.23.254/24

to the BTS and NodeB.)
60.60.60.1/24

CME

79
SingleRAN
Item
Instance
Remarks

eNodeB
20.20.20.188/24

CME

eNodeB
20.20.20.1/24

the eNodeB.)
60.60.60.188/24

the BTS.)
30.30.30.1/24

the NodeB.)
30.30.30.188/24
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
70.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 BTS 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 BTS and interconnecting the NodeB to
the eNodeB.
Issue 01 (2014-04-30)
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSIPRT
Forward Route
Address
NEXTHOP
Forward Route
Address

80
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
IPRT
Forward route
address
NEXTHOP
Forward route
address

MO
MML Parameter Name
MML Parameter ID
CME Parameter
Name
ETHPORT
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port No.
PN
Port No.
Maximum Transmission
Unit
MTU
Maximum
Transmission Unit
Speed
SPEED
Speed
Duplex
DUPLEX
Duplex
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
DEVIP
IPRT
Issue 01 (2014-04-30)

81
SingleRAN
MO
MML Parameter Name
MML Parameter ID
CME Parameter
Name
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCPSVRI
P
DHCPSVRIP
DHCP Server IP
Address
DHCPREL
AYSWITC
H
DHCP Relay Switch
ES
DHCP Switch

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
ETHPORT
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port No.
PN
Port No.
Port Attribute
PA
Port Attribute
Speed
SPEED
Speed
Duplex
DUPLEX
Duplex
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
DEVIP
Issue 01 (2014-04-30)

82
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Mask
MASK
Mask
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Port No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Relay Switch
VLANMAP
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Priority
VLANPRIO
VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
IPRT
VLANCLASS
Issue 01 (2014-04-30)

83
SingleRAN
7.8.3 Precautions
None

no additional hardware is required, but the FE electrical or optical ports for interconnecting main
control board panels are required. Table 7-10 describes the panel interconnection mode.
Table 7-10 Panel interconnection mode
Base
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 connected
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
connected to an optical port on the GTMU.
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
connected to an optical port on the GTMU.
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 connected

(Optional)Initial Configuration on the U2000 Side

Issue 01 (2014-04-30)

84
SingleRAN
Using MML Commands
from the IP address of the directly connected router to the IP address of interconnection port on
the WMPT. The BSC MML command for configuring the route from the BTS to the BSC is
ADD BTSIPRT.
Step 2 (Optional) Configure two routes to the DHCP relay of the BTS. 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 BTS is ADD IPRT.
----End
l


l
Using MML Commands
MASK="255.255.255.0";
of the interconnection port on the LMPT.
//Add a route from the NodeB to the BSC.
Issue 01 (2014-04-30)

85
SingleRAN
Step 5 (Optional)Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
Step 6 (Optional)Run the NodeB MML command ADD DHCPSVRIP to add the IP address of the
DHCP server.
When co-transmission is enabled for the BTS and NodeB, the NodeB needs to work as the relay
if the BTS is deployed using DHCP. Therefore, the IP address of the DHCP server needs to be
added on the NodeB. For the BTS, the IP address of the DHCP server is the IP address of the
----End
l


NOTE
The number of the BBU subrack used by the eNodeB must be different from the number of the BBU subrack
shared by the BTS and NodeB. The following description is based on the assumption that the number of
the BBU subrack used by the eNodeB is 1.
l
Using MML Commands
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;
for interconnecting the LMPT to the WMPT.
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.
Issue 01 (2014-04-30)

86
SingleRAN
ADD DEVIP: CN=0, SRN=1,
MASK="255.255.255.0";
//Set the IP address of
for interconnecting the
same network segment as
SN=7, SBT=BASE_BOARD, PT=ETH, PN=1, IP="60.60.60.1",

the Ethernet port (port 1 on board in slot 7) that is used
LMPT to the WMPT and ensure that the IP address is on the
the port IP address of the WMPT.
Step 3 Add an uplink route from the BTS/NodeB to the BSC 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="11.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 BTS 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 BTS 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 Run the eNodeB MML command ADD IPRT to add a downlink route from the BSC to the BTS
through the eNodeB.
The downlink route to the BTS needs to be configured on the eNodeB side regardless of whether
the port IP address or logical IP address is used by the BTS. In this step, set DSTIP to the port
IP address or logical IP address of the BTS and NEXTHOP to the IP address of the port on the
NodeB for interconnecting to the eNodeB. This step takes the port IP address configuration of
the BTS as an example. When configuring a route to the logical IP address of the BTS, change
the value of DSTIP in the following command:
//Add a route from the BSC to the BTS.
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 works as the DHCP server.
Issue 01 (2014-04-30)

87
SingleRAN

for the BTS, NodeB, and eNodeB:
uplink route from the BTS 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 BTS to the BSC through the eNodeB to 20.20.20.101 and set the next-hop address of the
uplink route from the NodeB to the RNC through the eNodeB to 20.20.20.201, which is
different from the next-hop address (20.20.20.1) of the uplink route for the eNodeB. To add
VLAN mapping, run the MML command ADD VLANMAP
differentiated DSCP values for the BTS, NodeB, and eNodeB. For details about DSCP values
for the BTS, NodeB, and eNodeB, see Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description.
1.

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

VLANGROUPNO=1;
----End
l


device.
Issue 01 (2014-04-30)

88
SingleRAN
LTE Side
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
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.
Step 2 Run the RNC MML command PING IP to ping the IP address of the WMPT.
----End
7.9 Main-Control-Board-based IP Co-Transmission

Through Backplane Interconnection on the Separate-MPT
LG/TG Multimode Base Station Side
l
Figure 7-13 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 BTS is interconnected to the eNodeB through backplanes.
Issue 01 (2014-04-30)

89
SingleRAN
Figure 7-13 Main-control-board-based IP co-transmission through backplane interconnection

on the separate-MPT LG multimode base station side


NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

Figure 7-14 shows an example of network topology for main-control-board-based IP cotransmission through backplane interconnection on the separate-MPT LG multimode base
station side.
Issue 01 (2014-04-30)

90
SingleRAN

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

Table 7-11 Data plan
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

BSC
21.21.21.254/24

eNodeB
20.20.20.1/24

eNodeB
20.20.20.188/24

CME
OM IP address of the
eNodeB
31.31.31.188/24
LTE: management plane IP

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

plane IP address. This is a
logical IP address and is
configured on the main
control board.

91
SingleRAN
Item
Instance
Remarks
60.60.60.60/24

OM channel
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
IP address of the BTS
35.35.35.188/24
GSM: communication IP
address of the BTS. This is a
configured on the BTS main
control board.
BTS electronic serial number

(ESN)
abcdefghijklmn
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.

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSTUNNEL
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
Source Cabinet No.
SRCCN
Source Cabinet No.
Source Subrack No.
SRCSRN
Source Subrack No.
Source Slot No.
SRCSN
Source Slot No.
BTS Tunnel No.
TN
BTS Tunnel No.
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
Destination Slot No.
DSTSN
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
BTSDEVIP
Issue 01 (2014-04-30)

92
SingleRAN
MO
BTSIP
BTSIPRT
BTSESN
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Port No.
PN
Port No.
Port Cabinet No.
CN
Port Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
BTS
Communication
Type
BTSCOMTYPE
BTS
Communication
Type
BTS IP
BTSIP
BTS IP
BSC IP
BSCIP
BSC IP
BTS MultiIP Switch
BTSMUTIP
BTS MultiIP Switch
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Route Index
RTIDX
Route Index
Destination IP
Address
DSTIP
Destination IP
Address
Destination Address
Mask
DSTMASK
Destination Address
Mask
Route Type
RTTYPE
Route Type
Port Cabinet No.
CN
Port Cabinet No.
Port Subrack No.
SRN
Port Subrack No.
Port Slot No.
SN
Port Slot No.
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
BTS Index Type
IDTYPE
BTS Index
BTSID
BTS Index

93
SingleRAN
MO
IPRT
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
OM Bear Board
OMBEARBOARD
OM Bear Board
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Destination IP
address
DSTIP
Destination IP
address
Destination address
mask
DSTMASK
Destination address
mask
Forward route
address
NEXTHOP
Forward route
address

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
IPRT
Issue 01 (2014-04-30)

94
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Port No.
IFNO
Port No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Relay Switch
VLANMAP
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Priority
VLANPRIO
VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Priority
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
VLANCLASS
7.9.3 Precautions
None

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

Issue 01 (2014-04-30)

95
SingleRAN
Using MML Commands
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 to add a route from the BSC to the eNodeB.
When two routes to the DHCP relay of the BTS are configured on the BSC side, one source IP
address working as the DHCP relay of the eNodeB is the OM IP address of the eNodeB and the
other source IP address is the lower-level transmission port of the eNodeB. Therefore, one route
whose destination IP address is the OM channel IP address of the eNodeB and the other route
whose destination IP address is the lower-level transmission port of the eNodeB need to be
configured on the BSC side.
ADD IPRT: SRN=0, SN=16, DSTIP="20.20.20.188", DSTMASK="255.255.255.255",
NEXTHOP="21.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="35.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 BTS.
Unlike non-co-transmission scenarios, this scenario requires that the BTS uses 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="35.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 BTS 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 BTS.
ADD BTSESN: IDTYPE=BYID, BTSID=10, MAINDEVTAB="abcdefghijklmn",
OMBEARBOARD=BACKBOARD;
//OMBEARBOARD must be set to BACKBOARD.
----End
l


Issue 01 (2014-04-30)

96
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.
ADD DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=1, IP="20.20.20.188",
MASK="255.255.255.0";
//Add an IP address for Ethernet port 1 on the LMPT/UMPT_L in slot 7.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="32.32.32.1",
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 BTS 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.
Step 4 Run the eNodeB MML command ADD IPRT to add a downlink route from the BSC to the BTS
through the eNodeB.
When co-transmission for the BTS and the eNodeB is implemented through tunnels on the
backplanes, the downlink route from the BSC to the BTS 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 IPRT: RTIDX=1, SN=0, SBT=BACK_BOARD, DSTIP="35.35.35.188",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a downlink route from the BSC to the BTS through the eNodeB.
relay.
relay if the BTS is deployed using DHCP. Therefore, DHCP relay needs to be enabled for the
eNodeB.
DHCP server.
relay if the BTS is deployed using DHCP. Therefore, the IP address of the DHCP server needs
to be added on the eNodeB. For the BTS, 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.
for the BTS and eNodeB:
Issue 01 (2014-04-30)

97
SingleRAN

uplink route from the BTS 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 BTS to the BSC through the eNodeB to 20.20.20.101, which is different
from the next-hop address (20.20.20.1) of the uplink route for the eNodeB. To add VLAN
differentiated DSCP values for the BTS and eNodeB. For details about DSCP values for the
BTS and eNodeB, see Bandwidth Sharing of Multimode Base Station Co-Transmission
1.

differentiated data needs to be configured for the eNodeB and BTS and TRAFFIC
is set to USERDATA, SRVPRIO cannot be set to 40 on the eNodeB.
2.

VLANGROUPNO=1;
----End
l


device.
LTE Side
----End
Issue 01 (2014-04-30)

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

Backplane Interconnection on the Separate-MPT UG
l
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.
Figure 7-15 Main-control-board-based IP co-transmission through backplane
interconnection on the separate-MPT UG multimode base station side


Issue 01 (2014-04-30)

99
SingleRAN

Figure 7-16 shows an example of network topology for main-control-board-based IP cotransmission through backplane interconnection on the separate-MPT UG multimode base
station side.
through backplane interconnection on the separate-MPT UG multimode base station side

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

BSC
21.21.21.254/24

RNC
11.11.11./24

NodeB
20.20.20.1/24
OM channel IP address of the

NodeB
30.30.30.1/24
UMTS: management plane

IP address. This is a logical IP

100
SingleRAN
Item
Instance
Remarks
of the NodeB
32.32.32.1/24
UMTS: control plane/user

control board.

UMPT_U of the NodeB
20.20.20.188/24

CME
This IP address is configured
on the co-transmission port.

RNC
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24
UMTS: OM channel peer IP

address
35.35.35.188/24
address of the BTS.
This is a logical IP address
and is configured on the BTS
main control board.
BTS ESN
abcdefghijklmn
NOTE
mode and rate because the GTMUb communicates with the UMPT_U through the backplane.
Issue 01 (2014-04-30)
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSTUNNEL
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
Source Cabinet No.
SRCCN
Source Cabinet No.
Source Subrack No.
SRCSRN
Source Subrack No.
Source Slot No.
SRCSN
Source Slot No.
BTS Tunnel No.
TN
BTS Tunnel No.

101
SingleRAN
MO
BTSDEVIP
BTSIP
BTSIPRT
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
DSTSN
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
Port No.
PN
Port No.
Port Cabinet No.
CN
Port Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
BTS
Communication
Type
BTSCOMTYPE
BTS
Communication
Type
BTS IP
BTSIP
BTS IP
BSC IP
BSCIP
BSC IP
BTS MultiIP Switch
BTSMUTIP
BTS MultiIP Switch
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Route Index
RTIDX
Route Index
Destination IP
Address
DSTIP
Destination IP
Address
Destination Address
Mask
DSTMASK
Destination Address
Mask
Route Type
RTTYPE
Route Type

102
SingleRAN
MO
BTSESN
IPRT
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Port Cabinet No.
CN
Port Cabinet No.
Port Subrack No.
SRN
Port Subrack No.
Port Slot No.
SN
Port Slot No.
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
BTS Index Type
IDTYPE
BTS Index
BTSID
BTS Index
OM Bear Board
OMBEARBOARD
OM Bear Board
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Destination IP
address
DSTIP
Destination IP
address
Destination address
mask
DSTMASK
Destination address
mask
Forward route
address
NEXTHOP
Forward route
address
Issue 01 (2014-04-30)
MO
MML Parameter Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack
No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet No.
DCN
Destination
Cabinet No.
Destination Subrack No.
DSRN
Destination
Subrack No.
DSN
Destination Slot
No.

103
SingleRAN
MO
MML Parameter Name
MML Parameter
ID
CME Parameter
Name
IPRT
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCPSVR
IP
DHCPSVRIP
DHCP Server IP
Address
DHCPREL
AYSWITC
H
DHCP Relay Switch
ES
DHCP Switch
VLANMA
P
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLANCLA
SS
7.10.3 Precautions
None
Issue 01 (2014-04-30)

104
SingleRAN


l
Using MML Commands
UMPT_U.
DSTSRN=0, DSTSN=7;
//Add a tunnel from the GTMUb in slot 6 to the UMPT_U in slot 7.
Step 2 (Optional)Run the BSC MML command ADD IPRT to add a route from the BSC to the NodeB.
address working as the DHCP relay of the NodeB is the OM channel IP address of the NodeB
and the other source IP address is the lower-level transmission port of the NodeB. Therefore,
one route whose destination IP address is the OM channel IP address of the NodeB and the other
route whose destination IP address is the lower-level transmission port of the NodeB need to be
IP="35.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;
Issue 01 (2014-04-30)

105
SingleRAN
----End
l


l
Using MML Commands
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="20.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="20.20.20.1";
//Add a route from the BTS 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 BTS
through the NodeB.
When co-transmission for the BTS and the NodeB is implemented through tunnels on the
UMPT_U backplane, the downlink route from the BSC to the BTS 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="35.35.35.188",
//Add a downlink route from the BSC to the BTS through the NodeB for the UMPT_U in
slot 7.
relay.
Issue 01 (2014-04-30)

106
SingleRAN

DHCP server.
from the uplink route for the NodeB. For example, you can set the next-hop address of the
uplink route from the BTS to the BSC through the NodeB to 20.20.20.101, which is different
from the next-hop address (20.20.20.1) of the uplink route for the NodeB. To add VLAN
ADD VLANMAP: NEXTHOPIP="20.20.20.101", MASK=255.255.255.255,
differentiated DSCP values for the BTS and NodeB. For details about DSCP values for the
BTS and NodeB, see Bandwidth Sharing of Multimode Base Station Co-Transmission
1.

2.
Run the NodeB MML command ADD VLANMAP to configure the DSCP value.
----End
l

Issue 01 (2014-04-30)

107
SingleRAN

device.
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.
----End
GSM Side
----End
7.11 UTRPc-based Co-Transmission Through Backplane

Interconnection on the Separate-MPT UG Multimode Base
Station Side in IP over FE/GE Mode
l
Figure 7-17 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 BTS is interconnected to the UTRPc through
backplanes.
Issue 01 (2014-04-30)

108
SingleRAN
Figure 7-17 UTRPc-based IP co-transmission through backplane interconnection on the

separate-MPT UG 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 multimode base station side.
Figure 7-18 Example of network topology for UTRPc-based IP co-transmission through
backplane interconnection on the separate-MPT UG multimode base station side
Issue 01 (2014-04-30)

109
SingleRAN

Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

BSC
21.21.21.254/24

RNC
11.11.11./24

NodeB
20.20.20.1/24
OM channel IP address of the

NodeB
30.30.30.1/24

of the NodeB
32.32.32.1/24

control board.

UTRPc of the NodeB
20.20.20.188/24

CME

RNC
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24
UMTS: OM channel peer IP

address
35.35.35.188/24
address of the BTS.
main control board.
BTS ESN
Issue 01 (2014-04-30)
abcdefghijklmn

110
SingleRAN
NOTE
mode and rate because the GTMUb communicates with the UTRPc through the backplane.

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSTUNNEL
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
Source Cabinet No.
SRCCN
Source Cabinet No.
Source Subrack No.
SRCSRN
Source Subrack No.
Source Slot No.
SRCSN
Source Slot No.
BTS Tunnel No.
TN
BTS Tunnel No.
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
DSTSN
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
Port No.
PN
Port No.
Port Cabinet No.
CN
Port Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
BTS
Communication
Type
BTSCOMTYPE
BTS
Communication
Type
BTS IP
BTSIP
BTS IP
BTSDEVIP
BTSIP
Issue 01 (2014-04-30)

111
SingleRAN
MO
BTSIPRT
BTSESN
IPRT
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BSC IP
BSCIP
BSC IP
BTS MultiIP Switch
BTSMUTIP
BTS MultiIP Switch
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Route Index
RTIDX
Route Index
Destination IP
Address
DSTIP
Destination IP
Address
Destination Address
Mask
DSTMASK
Destination Address
Mask
Route Type
RTTYPE
Route Type
Port Cabinet No.
CN
Port Cabinet No.
Port Subrack No.
SRN
Port Subrack No.
Port Slot No.
SN
Port Slot No.
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
BTS Index Type
IDTYPE
BTS Index
BTSID
BTS Index
OM Bear Board
OMBEARBOARD
OM Bear Board
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Destination IP
address
DSTIP
Destination IP
address
Destination address
mask
DSTMASK
Destination address
mask
Forward route
address
NEXTHOP
Forward route
address

112
SingleRAN

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BRD
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Board Type
BT
SubBoard Type
SBT
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Switch
TUNNEL
IPRT
Issue 01 (2014-04-30)

113
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
VLANMAP
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
VLAN Mode
MASK
VLAN Mode
VLAN ID
VLANMODE
VLAN ID
Set VLAN Priority
VLANID
Set VLAN Priority
VLAN Group No.
SETPRIO
VLAN Group No.
Traffic Type
VLANGROUPNO
Traffic Type
User Data Service

Priority
TRAFFIC
User Data Service

Priority
VLAN ID
SRVPRIO
VLAN ID
VLANCLASS
7.11.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.
Cables to the UTRPc on the UG multimode base station side are used to connect to the
transport network.

l
Using MML Commands
UTRPc.
DSTSRN=0, DSTSN=4;
//Add a tunnel from the GTMUb in slot 6 to the UTRPc in slot 4.
Step 2 (Optional)Run the BSC MML command ADD IPRT to add a route from the BSC to the NodeB.
address working as the DHCP relay of the NodeB is the OM channel IP address of the NodeB
Issue 01 (2014-04-30)

114
SingleRAN
and the other source IP address is the lower-level transmission port of the NodeB. Therefore,
one route whose destination IP address is the OM channel IP address of the NodeB and the other
route whose destination IP address is the lower-level transmission port of the NodeB need to be
IP="35.35.35.188", MASK="255.255.255.0";
IFNO=0;
----End
l


l
Using MML Commands
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.
Issue 01 (2014-04-30)

115
SingleRAN
SET ETHPORT: CN=0, SRN=0, SN=4, SBT=ETH_COVERBOARD, PN=1, 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="20.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 BTS to the BSC through the NodeB for the UTRPc in slot 4.
through the NodeB.
When co-transmission for the BTS and the NodeB is implemented through tunnels on the UTRPc
backplane, the downlink route from the BSC to the BTS 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 a downlink route from the BSC to the BTS through the NodeB for the UTRPc in
slot 4.
relay.
DHCP server.
----End
Issue 01 (2014-04-30)

116
SingleRAN
Method 1 (Recommended): Configure differentiated next-hop addresses. Specifically, the

from the uplink route for the NodeB. For example, you can set the next-hop address of the
uplink route from the BTS to the BSC through the NodeB to 20.20.20.101, which is different
from the next-hop address (20.20.20.1) of the uplink route for the NodeB. To add VLAN
Method 2 (Not recommended): Configure differentiated DSCP values. This method

requires differentiated DSCP values for the BTS and NodeB. For details about DSCP values
for the BTS and NodeB, see Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description.
1.

mode, set TRAFFIC to USERDATA for all passerby flows through the NodeB. If
differentiated data needs to be configured for the NodeB and BTS and
TRAFFIC is set to USERDATA, SRVPRIO cannot be set to 40 on the NodeB.
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.


device.
UMTS Side
----End
GSM Side
Issue 01 (2014-04-30)

117
SingleRAN
----End

Backplane Interconnection on the Separate-MPT UL/UT
l
This section uses UMPT_U + UMPT_L based multimode base station as an example to
describe the main-control-board-based IP co-transmission through backplane
interconnection on the separate-MPT UL multimode base station side, as shown in Figure
7-19, In this scenario, an outbound FE/GE port on the UMPT_U of the NodeB serves as
the co-transmission port of the separate-MPT UL multimode base station and is connected
to the RNC and MME/S-GW. The UMPT_L is interconnected to the UMPT_U through
backplanes.
interconnection on the separate-MPT UL multimode base station side


Issue 01 (2014-04-30)

118
SingleRAN
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

Figure 7-20 shows an example of network topology for main-control-board-based IP cotransmission through backplane interconnection on the separate-MPT UL multimode base
station side.
through backplane interconnection on the separate-MPT UL multimode base station side

Issue 01 (2014-04-30)
Item
Instance
Remarks

RNC
15.15.15.15/32

119
SingleRAN
Item
Instance
Remarks
11.11.11.11/24

RNC
11.11.11.254/24

UMPT_U
20.20.20.1/24
OM IP address of the NodeB
30.30.30.1/24
NodeB: management plane

IP address.
and is configured on the
NodeB main control board.
of the NodeB
32.32.32.1/24

plane IP address.
of the eNodeB
33.33.33.188/24

configured on the eNodeB
main control board.
eNodeB
31.31.31.188/24

the eNodeB main control
board.

UMPT_U of the NodeB
20.20.20.188/24

CME
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
60.60.60.60/24
UMTS/LTE: peer IP address

for the OM channel
NOTE
In this scenario, the UMPT_L does not need to be configured with Ethernet port attributes such as duplex
mode and rate because the UMPT_L communicates with the UMPT_U through the backplane.
Issue 01 (2014-04-30)

120
SingleRAN

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Switch
VLANMAP
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
IPRT
Issue 01 (2014-04-30)

121
SingleRAN
MO
VLANCLASS
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
DEVIP
IPRT
Issue 01 (2014-04-30)

122
SingleRAN
MO
RSCGRP
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Port No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Transmission
Resource Group
Bear Type
BEAR
Transmission
Resource Group
Bear Type
Subboard Type
SBT
Subboard Type
Bearing Port Type
PT
Bearing Port Type
Bearing Port No.
PN
Bearing Port No.
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
Rate Unit
RU
Rate Unit
Tx Bandwidth
TXBW
Tx Bandwidth
Rx Bandwidth
RXBW
Rx Bandwidth
TX Committed Burst
Size
TXCBS
TX Committed Burst
Size
TX Excessive Burst
Size
TXEBS
TX Excessive Burst
Size
Operator ID
OID
Operator ID
Scheduling Weight
WEIGHT
Scheduling Weight
TX Committed
Information Rate
TXCIR
TX Committed
Information Rate
RX Committed
Information Rate
RXCIR
RX Committed
Information Rate

123
SingleRAN
MO
IPPath
OMCH
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TX Peak Information
Rate
TXPIR
TX Peak Information
Rate
RX Peak Information
Rate
RXPIR
RX Peak Information
Rate
TX Peak Burst Size
TXPBS
TX Peak Burst Size
IP Path ID
PATHID
IP Path ID
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
Join Transmission
Resource Group
JNRSCGRP
Join Transmission
Resource Group
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
Local IP
LOCALIP
Local IP
Peer IP
PEERIP
Peer IP
Path Type
PATHTYPE
Path Type
Local IP
IP
Local IP
Local Mask
MASK
Local Mask
Peer IP
PEERIP
Peer IP
Peer Mask
PEERMASK
Peer Mask
Bearer Type
BEAR
Bearer Type
Binding Route
BRT
Binding Route
7.12.3 Precautions
None
Issue 01 (2014-04-30)

124
SingleRAN


Configure two routes from the U2000 to the DHCP relay of the eNodeB. 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. If the NodeB has multiple port IP
addresses, configure a route for each port IP address.

l
Using MML Commands
MASK="255.255.255.0";
MASK="255.255.255.0";
LMPT/UMPT_L.
//Add a tunnel from the UMPT_U in slot 7 to the UMPT_L in slot 6.
Step 3 Run the NodeB MML command ADD IPRT to add 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 eNodeB to the MME through the NodeB for the UMPT_U in slot
7.
//Add a route from the eNodeB to the S-GW through the NodeB for the UMPT_U in slot
7.
//Add a route from the eNodeB to the U2000 through the NodeB for the UMPT_U in slot
7. Skip this step if the UMPT_U has already been configured with a route to the
U2000.
Step 4 Run the NodeB MML command ADD IPRT to add a downlink route from the MME/S-GW/
U2000 to the eNodeB through the NodeB.
Issue 01 (2014-04-30)

125
SingleRAN
When co-transmission for the eNodeB and the NodeB is implemented through tunnels on the
UMPT_U backplane, the downlink route from the MME/S-GW/U2000 to the eNodeB 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.
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=0;
//Add a route from the MME/S-GW/U2000 to the eNodeB through the NodeB for the UMPT_U
in slot 7.
relay.
When co-transmission is enabled for the eNodeB and NodeB, if the eNodeB 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 eNodeB, the IP address of the DHCP server is the IP
address of the U2000.
//Add the IP address of the DHCP server for the eNodeB.
uplink route from the eNodeB to the MME/S-GW through the NodeB added in step 3 must
be different from the uplink route for the NodeB. For example, you can set the next-hop
address of the uplink route from the eNodeB to the MME/S-GW through the NodeB to
for the NodeB. To add VLAN mapping, run the MML command ADD VLANMAP
differentiated DSCP values for the eNodeB and NodeB. For details about DSCP values for
the eNodeB and NodeB, see Bandwidth Sharing of Multimode Base Station Co-Transmission
1.

differentiated data needs to be configured for the NodeB and eNodeB and
Issue 01 (2014-04-30)

126
SingleRAN
DHCP packets is fixed at 0.
data is configured, set the
set to 0, DHCP packets sent
In addition, set TRAFFIC to
2.
If DHCP relay is enabled on the network where VLAN
DSCP value to 0 for VLAN. If the DSCP value is not
to the DHCP server do not contain the VLAN field.
USERDATA.
----End
l


l
Using MML Commands
Step 1 Run the eNodeB MML command ADD TUNNEL to add a tunnel from the UMPT_L to the
UMPT_U.
ADD TUNNEL: SSN=6, DSN=7,TUNNELTYPE=UL;
//Add a tunnel from the UMPT_L in slot 6 to the UMPT_U in slot 7.
Step 2 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.
ADD DEVIP: SRN=0, SN=6, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="33.33.33.188",
MASK="255.255.255.0";
//When configuring the signaling/service IP address for the eNodeB, set SRN to 0,
SN to 6, and PT to LOOPINT.
Step 3 Run the eNodeB MML command ADD IPRT to add a route from the eNodeB to the MME/SGW/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 1.
ADD IPRT: RTIDX=0, SRN=0, SN=6, SBT=BACK_BOARD, DSTIP="40.40.40.40",
//Add a route from the eNodeB to the MME.
//Add a route from the eNodeB to the S-GW.
Issue 01 (2014-04-30)

127
SingleRAN
//Add a route from the eNodeB to the U2000.
Step 4 (Optional) Run the eNodeB MML command ADD RSCGRP to add a transmission resource
group.
ADD RSCGRP: SRN=0, SN=6, 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 5 Run the eNodeB MML command ADD IPPATH to add an IP path.
ADD IPPATH: PATHID=0, SRN=0, SN=6, SBT=BACK_BOARD, PT=TUNNEL, PN=0,
JNRSCGRP=DISABLE, LOCALIP="33.33.33.188", PEERIP="50.50.50.50", PATHTYPE=ANY;
//When adding an IP path, set SBT to BACK_BOARD and PT to TUNNEL.
Step 6 Run the eNodeB MML command ADD OMCH to add an OM channel.
ADD OMCH: IP="31.31.31.188", MASK="255.255.255.0", PEERIP="60.60.60.60",
PEERMASK="255.255.255.0", BEAR=IPV4, SRN=0, SN=6, SBT=BACK_BOARD, BRT=NO;
//When adding an OM channel, set SBT to BACK_BOARD.
----End
l


device.
UMTS Side
----End
LTE Side
Issue 01 (2014-04-30)

128
SingleRAN

----End

Interconnection on the Separate-MPT UL/UT Multimode
l
Figure 7-21shows the UTRPc-based IP co-transmission through backplane
interconnection on the separate-MPT UL multimode base station side. In this scenario, an
outbound 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 UL multimode base station and is
connected to the RNC and MME/S-GW. The LMPT/UMPT_L is interconnected to the
UTRPc through backplanes.

separate-MPT UL multimode base station side


Issue 01 (2014-04-30)

129
SingleRAN
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

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

Issue 01 (2014-04-30)
Item
Instance
Remarks

RNC
15.15.15.15/32

130
SingleRAN
Item
Instance
Remarks
11.11.11.11/24

RNC
11.11.11.254/24

UTRPc
20.20.20.1/24
30.30.30.1/24

IP address.
of the NodeB
32.32.32.1/24

configured on the NodeB
main control board.
of the eNodeB
33.33.33.188/24

main control board.
eNodeB
31.31.31.188/24

board.

UTRPc of the NodeB
20.20.20.188/24

CME
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
60.60.60.60/24

for the OM channel
NOTE
In this scenario, the LMPT/UMPT_L does not need to be configured with Ethernet port attributes such as
duplex mode and rate because the LMPT/UMPT_L communicates with the UTRPc through the backplane.
Issue 01 (2014-04-30)

131
SingleRAN

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BRD
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Board Type
BT
SubBoard Type
SBT
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Switch
TUNNEL
IPRT
Issue 01 (2014-04-30)

132
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
VLANMAP
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLANCLASS

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
DEVIP
Issue 01 (2014-04-30)

133
SingleRAN
MO
IPRT
RSCGRP
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
IP Address
IP
IP Address
Mask
MASK
Mask
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Port No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Transmission
Resource Group
Bear Type
BEAR
Transmission
Resource Group
Bear Type
Subboard Type
SBT
Subboard Type
Bearing Port Type
PT
Bearing Port Type
Bearing Port No.
PN
Bearing Port No.
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
Rate Unit
RU
Rate Unit
Tx Bandwidth
TXBW
Tx Bandwidth
Rx Bandwidth
RXBW
Rx Bandwidth
TX Committed Burst
Size
TXCBS
TX Committed Burst
Size
TX Excessive Burst
Size
TXEBS
TX Excessive Burst
Size
Operator ID
OID
Operator ID

134
SingleRAN
MO
IPPath
OMCH
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Scheduling Weight
WEIGHT
Scheduling Weight
TX Committed
Information Rate
TXCIR
TX Committed
Information Rate
RX Committed
Information Rate
RXCIR
RX Committed
Information Rate
TX Peak Information
Rate
TXPIR
TX Peak Information
Rate
RX Peak Information
Rate
RXPIR
RX Peak Information
Rate
TX Peak Burst Size
TXPBS
TX Peak Burst Size
IP Path ID
PATHID
IP Path ID
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
Join Transmission
Resource Group
JNRSCGRP
Join Transmission
Resource Group
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
Local IP
LOCALIP
Local IP
Peer IP
PEERIP
Peer IP
Adjacent Node ID
ANI
Adjacent Node ID
Path Type
PATHTYPE
Path Type
Local IP
IP
Local IP
Local Mask
MASK
Local Mask
Peer IP
PEERIP
Peer IP
Peer Mask
PEERMASK
Peer Mask
Bearer Type
BEAR
Bearer Type
Cabinet No.
CN
Cabinet No.

135
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Binding Route
BRT
Binding Route
7.13.3 Precautions
None

l
Compared with non-co-transmission scenarios, UTRPc-based IP co-transmission through

backplane interconnection on the UL multimode base station side requires the UTRPc.
Cables to the UTRPc on the LU multimode base station side are used to connect to the
transport network.

Configure a route from the U2000 to the DHCP relay of the eNodeB. In this step, set the
destination IP address to the port IP address of the NodeB. If the NodeB has multiple port IP
addresses, configure a route for each port IP address.

l
Using MML Commands
Step 1 Run the ADD BRD command to add a UTRPc.

//Add a UTRPc to slot 4.
MASK="255.255.255.0";
Issue 01 (2014-04-30)

136
SingleRAN

MASK="255.255.255.0";
Step 4 Run the NodeB MML command ADD TUNNEL to add a tunnel from the UTRPc to the LMPT/
UMPT_L.
ADD TUNNEL: SSN=4, DSN=6,TUNNELTYPE=DL;
//Add a tunnel from the UTRPc in slot 4 to the LMPT/UMPT_L in slot 6.
Step 5 Run the NodeB MML command ADD IPRT to add 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 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 slot
U2000.
Step 6 Run the NodeB MML command ADD IPRT to add a downlink route from the MME/S-GW/
U2000 to the eNodeB through the NodeB.
When co-transmission for the eNodeB and the NodeB is implemented through tunnels on the
UTRPc backplane, the downlink route from the MME/S-GW/U2000 to the eNodeB 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 a route from the MME/S-GW/U2000 to the eNodeB through the NodeB for the UTRPc
in slot 4.
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
Issue 01 (2014-04-30)

137
SingleRAN
needs to be added on the NodeB. For the eNodeB, the IP address of the DHCP server is the IP
address of the U2000.
uplink route from the eNodeB to the MME/S-GW through the NodeB added in step 5 must
be different from the uplink route for the NodeB. For example, you can set the next-hop
address of the uplink route from the eNodeB to the MME/S-GW through the NodeB to
for the NodeB. To add VLAN mapping, run the MML command ADD VLANMAP
differentiated DSCP values for the eNodeB and NodeB. For details about DSCP values for
the eNodeB and NodeB, see Bandwidth Sharing of Multimode Base Station Co-Transmission
1.

2.
----End
l


l
Issue 01 (2014-04-30)
Using MML Commands

138
SingleRAN
UTRPc.
ADD TUNNEL: SSN=6, DSN=4;
//Add a tunnel from the UMPT_L in slot 6 to the UTRPc in slot 4.
MASK="255.255.255.0";
//When configuring the signaling/service IP address for the eNodeB, set SRN to 0
group.
TUNNEL.
----End
l

Issue 01 (2014-04-30)

139
SingleRAN

device.
UMTS Side
----End
LTE Side
----End

Backplane Interconnection on the Separate-MPT LU/TU
l
interconnection on the separate-MPT LU multimode base station side. In this scenario, an
outbound FE/GE port on the UMPT_L of the eNodeB serves as the co-transmission port
of the separate-MPT LU multimode base station and is connected to the RNC and MME/
S-GW. The UMPT_U is interconnected to the UMPT_L through backplanes.
Issue 01 (2014-04-30)

140
SingleRAN

interconnection on the separate-MPT LU multimode base station side


NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

Figure 7-24 shows an example of network topology for main-control-board-based IP cotransmission through backplane interconnection on the separate-MPT LU multimode base
station side. Table 7-16 describes the IP address plan.
Issue 01 (2014-04-30)

141
SingleRAN

through backplane interconnection on the separate-MPT LU multimode base station side

Item
Instance
Remarks

RNC
15.15.15.15/32
11.11.11.11/24

RNC
11.11.11.254/24

UMPT_L
20.20.20.1/24
30.30.30.1/24

IP address.
of the NodeB
32.32.32.1/24

plane IP address.
Issue 01 (2014-04-30)

142
SingleRAN
Item
Instance
Remarks
of the eNodeB
33.33.33.188/24

main control board.
eNodeB
31.31.31.188/24

board.

UMPT_L of the NodeB
20.20.20.188/24

CME
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
60.60.60.60/24

for the OM channel

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
DCN
Destination Cabinet
No.
DSRN
Destination Subrack
No.
DSN
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
DEVIP
Issue 01 (2014-04-30)

143
SingleRAN
MO
IPRT
RSCGRP
IPPATH
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Transmission Resource
Group Bear Type
BEAR
Subboard Type
SBT
Subboard Type
Bearing Port Type
PT
Carrier Type
Bearing Port No.
PN
Link No.
Group ID
RSCGRPID
Transmission
Resource Group ID
Rate Unit
RU
Rate Unit
Tx Bandwidth
TXBW
Tx Bandwidth
Rx Bandwidth
RXBW
Rx Bandwidth
IP Path ID
PATHID
IP Path ID

144
SingleRAN
MO
OMCH
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Carrier Type
Port No.
PN
Link No.
Join Transmission
Resource Group
JNRSCGRP
Join Transmission
Resource Group
Local IP
LOCALIP
Local IP
Peer IP
PEERIP
Peer IP
DSCP
DSCP
DSCP
RX Bandwidth
RXBW
RX Bandwidth
TX Bandwidth
TXBW
TX Bandwidth
TX Committed Burst
Size
TXCBS
TX Committed Burst
Size
TX Excessive Burst Size
TXEBS
TX Excessive Burst
Size
Local IP
IP
Local IP
Local Mask
MASK
Local Mask
Peer IP
PEERIP
Peer IP
Peer Mask
PEERMASK
Peer Mask
Bearer Type
BEAR
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Binding Route
BRT
Binding Route

145
SingleRAN

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Port No.
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DEVIP
IPRT
DHCPSVRIP
Issue 01 (2014-04-30)

146
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Relay Switch
VLANMAP
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Priority
VLANPRIO
VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
VLANCLASS
7.14.3 Precautions
None


Configure two routes from the U2000 to the DHCP relay of the NodeB. In this step, set the

Issue 01 (2014-04-30)

147
SingleRAN
l
Using MML Commands
UMPT_L.
ADD TUNNEL: SSN=7, DSN=6,TUNNELTYPE=UL;
//Add a tunnel from the UMPT_U in slot 7 of the NodeB to the UMPT_L in slot 6.
Step 2 Run the NodeB MML command ADD DEVIP to configure the DSCP value.
Unlike non-co-transmission scenarios, this scenario requires that the IP address of the NodeB
must 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";
Step 3 Run the NodeB MML command ADD IPRT to add a route from the NodeB to the RNC/U2000.
//Add a route from the NodeB to the U2000.
Step 4 (Optional) Run the NodeB MML command ADD RSCGRP to add a transmission resource
group.
ADD RSCGRP: SN=7, BEAR=IPV4, SBT=BACK_BOARD, PT=TUNNEL, RSCGRPID=0, RU=KBPS,
TXBW=4000, RXBW=4000;
TUNNEL.
Step 5 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="32.32.32.1", PEERIP="15.15.15.15", DSCP=22, RXBW=1000, TXBW=1000,
TXCBS=15000, TXEBS=2000, FPMUXSWITCH=DISABLE;
Step 6 Run the NodeB MML command ADD OMCH to add an O&M channel.
PEERMASK="255.255.255.0", BEAR=IPV4, SN=7, SBT=BACK_BOARD, BRT=NO;
//When adding an O&M channel, set SBT to BACK_BOARD.
----End
l
Issue 01 (2014-04-30)

148
SingleRAN

l
Using MML Commands
UMPT_U.
MASK="255.255.255.0";
//Add an IP address for Ethernet port 1 on the UMPT_L in slot 6.
MASK="255.255.255.0";
//Add a signaling/service IP address for the UMPT_L in slot 6.
//Add a tunnel from the UMPT_L in slot 6 to the UMPT_U in slot 7.
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, SN=6, SBT= BASE_BOARD, DSTIP="15.15.15.15",
//Add a route from the NodeB to the RNC through the eNodeB for the UMPT_L in slot
6.
Step 4 Run the eNodeB MML command ADD IPRT to add a downlink route from the U2000/RNC to
the NodeB through the eNodeB.
When co-transmission for the NodeB and the eNodeB is implemented through the backplane,
the downlink route from the RNC to the NodeB 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 U2000 to the NodeB through the eNodeB.
//Add a downlink route from the RNC to the NodeB through the eNodeB.
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.
Issue 01 (2014-04-30)

149
SingleRAN

DHCP server.
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, the IP address of the DHCP server needs
to be added on the eNodeB. If the DHCP server is shared by the NodeB and eNodeB, the IP
address of the DHCP server is the IP address of the U2000.
for the NodeB and eNodeB:
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. Run the eNodeB MML command ADD
VLANMAP to change the next-hop address of the uplink route from the NodeB to the BSC
through the eNodeB. In this step, assume that the next-hop address of the uplink route from
the NodeB to the BSC through the eNodeB changes to 20.20.20.101, which is different from
the next-hop address (20.20.20.1) of the uplink route for the eNodeB.
l Method 2 (Not recommended): Configure differentiated DSCP values. This method allows
consistency between the uplink route from the NodeB to the RNC through the eNodeB and
the uplink route for the eNodeB, but requires differentiated DSCP values for the NodeB and
eNodeB. For details about DSCP values for the NodeB and eNodeB, see Bandwidth Sharing
of Multimode Base Station Co-Transmission Feature Parameter Description.
1.

2.

VLANGROUPNO=1;
----End
l

Issue 01 (2014-04-30)

150
SingleRAN

device.
LTE Side
----End
UMTS Side
----End

Interconnection on the Separate-MPT UG+L/UG+T
l
Figure 7-25 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 BBU are interconnected
by using backplanes. The UMPT_L and UTRPc are interconnected by using backplanes
through the UCIU.
Issue 01 (2014-04-30)

151
SingleRAN

separate-MPT UG+L multimode base station side


NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

through backplane interconnection on the separate-MPT UG+L multimode base station side.
Issue 01 (2014-04-30)

152
SingleRAN

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

Issue 01 (2014-04-30)
Item
IP Address
Remarks
10.10.10.10/32
21.21.21.1/24
Device IP address of the RNC
15.15.15.15/32
11.11.11.11/24

RNC
11.11.11.254/24

BSC
21.21.21.254/24

UTRPc
20.20.20.1/24

153
SingleRAN
Item
IP Address
Remarks
30.30.30.1/24

IP address. This IP address is
control board.
of the NodeB
32.32.32.1/24

control board.

UTRPc of the NodeB
20.20.20.188/24

CME
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
60.60.60.60/24
UMTS: peer IP address for

the OM channel
OM IP address of the eNodeB
31.31.31.188/24

of the eNodeB
33.33.33.188/24

control board.
35.35.35.188/24
address of the BTS.
main control board.
BTS ESN
abcdefghijklmn
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.
Issue 01 (2014-04-30)

154
SingleRAN

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSBRD
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Board Type
BT
Board Type
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
Link No.
LN
Link No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Upper Node Cabinet

No.
UPCN
Upper Node Cabinet

No.
Upper Node Subrack

No.
UPSRN
Upper Node Subrack

No.
Upper Node Slot No.
UPSN
Upper Node Slot No.
Upper Node Port No.
UPPT
Upper Node Port No.
BTS Index Type
IDTYPE
BTS Index Type
BTS Index
BTSID
BTS Index
Source Cabinet No.
SRCCN
Source Cabinet No.
Source Subrack No.
SRCSRN
Source Subrack No.
Source Slot No.
SRCSN
Source Slot No.
BTS Tunnel No.
TN
BTS Tunnel No.
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
BTSCTRLLNK
BTSTUNNEL
Issue 01 (2014-04-30)

155
SingleRAN
MO
BTSDEVIP
BTSIP
BTSIPRT
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
DSTSN
BTS Index Type
IDTYPE
BTS Index Type
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
Port No.
PN
Port No.
Port Cabinet No.
CN
Port Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
BTS Index Type
IDTYPE
BTS Index Type
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
BTS
Communication
Type
BTSCOMTYPE
BTS
Communication
Type
BTS IP
BTSIP
BTS IP
BSC IP
BSCIP
BSC IP
BTS MultiIP Switch
BTSMUTIP
BTS MultiIP Switch
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Route Index
RTIDX
Route Index
Destination IP
Address
DSTIP
Destination IP
Address
Destination Address
Mask
DSTMASK
Destination Address
Mask
Route Type
RTTYPE
Route Type
Port Cabinet No.
CN
Port Cabinet No.
Port Subrack No.
SRN
Port Subrack No.
Port Slot No.
SN
Port Slot No.

156
SingleRAN
MO
BTSESN
IPRT
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
BTS Index Type
IDTYPE
BTS Index
BTSID
BTS Index
OM Bear Board
OMBEARBOARD
OM Bear Board
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Destination IP
address
DSTIP
Destination IP
address
Destination address
mask
DSTMASK
Destination address
mask
Forward route
address
NEXTHOP
Forward route
address

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BRD
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Board Type
BT
SubBoard Type
SBT
Local Link No.
LN
Local Link No.
Local Cabinet No.
CN
Local Cabinet No.
Local Subrack No.
SRN
Local Subrack No.
Local Slot No.
SN
Local Slot No.
Upper Cabinet No.
UPCN
Upper Cabinet No.
Upper Subrack No.
UPSRN
Upper Subrack No.
Upper Slot No.
UPSN
Upper Slot No.
CTRLLNK
Issue 01 (2014-04-30)

157
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Upper Port No.
UPPT
Upper Port No.
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Switch
VLANMAP
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
TUNNEL
IPRT
Issue 01 (2014-04-30)

158
SingleRAN
MO
VLANCLASS
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CTRLLNK
Local Link No.
LN
Local Link No.
Local Cabinet No.
CN
Local Cabinet No.
Local Subrack No.
SRN
Local Subrack No.
Local Slot No.
SN
Local Slot No.
Upper Cabinet No.
UPCN
Upper Cabinet No.
Upper Subrack No.
UPSRN
Upper Subrack No.
Upper Slot No.
UPSN
Upper Slot No.
Upper Port No.
UPPT
Upper Port No.
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
TUNNEL
DEVIP
Issue 01 (2014-04-30)

159
SingleRAN
MO
IPRT
RSCGRP
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Port No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Transmission
Resource Group
Bear Type
BEAR
Transmission
Resource Group
Bear Type
Subboard Type
SBT
Subboard Type
Bearing Port Type
PT
Bearing Port Type
Bearing Port No.
PN
Bearing Port No.
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
Rate Unit
RU
Rate Unit
Tx Bandwidth
TXBW
Tx Bandwidth
Rx Bandwidth
RXBW
Rx Bandwidth

160
SingleRAN
MO
IPPath
OMCH
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TX Committed Burst
Size
TXCBS
TX Committed Burst
Size
TX Excessive Burst
Size
TXEBS
TX Excessive Burst
Size
Operator ID
OID
Operator ID
Scheduling Weight
WEIGHT
Scheduling Weight
TX Committed
Information Rate
TXCIR
TX Committed
Information Rate
RX Committed
Information Rate
RXCIR
RX Committed
Information Rate
TX Peak Information
Rate
TXPIR
TX Peak Information
Rate
RX Peak Information
Rate
RXPIR
RX Peak Information
Rate
TX Peak Burst Size
TXPBS
TX Peak Burst Size
IP Path ID
PATHID
IP Path ID
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
Join Transmission
Resource Group
JNRSCGRP
Join Transmission
Resource Group
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
Local IP
LOCALIP
Local IP
Peer IP
PEERIP
Peer IP
Path Type
PATHTYPE
Path Type
Local IP
IP
Local IP
Local Mask
MASK
Local Mask
Peer IP
PEERIP
Peer IP

161
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Peer Mask
PEERMASK
Peer Mask
Bearer Type
BEAR
Bearer Type
Binding Route
BRT
Binding Route
7.15.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
BTS side.
The UCIU in the BBU subrack accommodating the NodeB and BTS is connected to the
UMPT_L in the BBU subrack accommodating the eNodeB by using inter-subrack
interconnection cables.
Cables to the UTRPc on the UG+L multimode base station side are used to connect to the
transport network.

other route to the lower-level transmission port of the NodeB.

l
Using MML Commands
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.
UTRPc.
DSTSRN=0, DSTSN=4;
Issue 01 (2014-04-30)

162
SingleRAN
//Add a tunnel from the GTMUb in slot 6 to the UTRPc in slot 4.
IP="35.35.35.188", MASK="255.255.255.0";
IFNO=0;
Step 7 (Optional)Run the BSC MML command ADD IPRT to add a route to the DHCP relay of the
BTS. 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="21.21.21.254", PRIORITY=HIGH, REMARK="relay;
----End
l


l
Issue 01 (2014-04-30)
Using MML Commands

163
SingleRAN
NOTE
In this scenario, the eNodeB uses the CI interface for communication. Therefore, Ethernet ports are not
required.
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.
MASK="255.255.255.0";
group.
TUNNEL.
----End
Issue 01 (2014-04-30)

164
SingleRAN


l
Using MML Commands
Step 1 Run the NodeB MML command ADD BRD to add a UTRPc.
//Add a UTRPc in slot 4.
MASK="255.255.255.0";
MASK="255.255.255.0";
Step 4 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.
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 BTS 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.
Issue 01 (2014-04-30)

165
SingleRAN
//Add a route from the eNodeB to the U2000 through the NodeB for the UTRPc in slot
U2000.
through the NodeB and a downlink route from the MME/S-GW/U2000 to the eNodeB through
the NodeB.
When co-transmission for the BTS, eNodeB, and NodeB is implemented through tunnels on the
UTRPc backplane, the downlink route from the BSC to the BTS 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.
//Add a downlink route from the BSC to the BTS through the NodeB for the UTRPc in
slot 4.
//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 BTS, eNodeB and NodeB, the NodeB needs to work
as the relay if the BTS 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 BTS, eNodeB and NodeB, the NodeB needs to work
as the relay if the BTS 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 BTS is BSC, while the
DHCP server of the eNodeB is U2000.
uplink route from the BTS 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 address of the uplink route
from the BTS to the BSC through the NodeB to 20.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 20.20.20.201,
Issue 01 (2014-04-30)

166
SingleRAN
which is different from the next-hop address (20.20.20.1) of the uplink route for the NodeB.
To add VLAN mapping, run the MML command ADD VLANMAP
differentiated DSCP values for the BTS, eNodeB, and NodeB. For details about DSCP values
for the NodeB, eNodeB and eNodeB, see Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description.
1.

differentiated data needs to be configured for the NodeB and eNodeB and TRAFFIC
2.

----End
l


device.
UMTS Side
on the NodeB side to verify whether the transmission link between the NodeB and the RNC is
normal:
Issue 01 (2014-04-30)

167
SingleRAN

----End
GSM Side
----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 Multimode Base Station Side in IP over FE/GE Mode
l
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/SGW. 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.
Issue 01 (2014-04-30)

168
SingleRAN

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

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/SGW. 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.
interconnection on the separate-MPT UG+L multimode base station side (UMPT+UMPT
interconnection)
Issue 01 (2014-04-30)

169
SingleRAN

interconnection on the UG+L multimode base station side. In this scenario, an FE/GE port on
the UMPT_U of the NodeB serves as the co-transmission port of the U+GL multimode base
station and is connected to the MBSC and MME/S-GW. The GTMUb and UMPT_U are
interconnected by using backplanes through the UCIU. The LMPT and UMPT_U are
interconnected by using backplanes through the UCIU.
on the UG+L multimode base station side
This document provides only the engineering guidelines for the scenario shown in Figure
7-27. The engineering guidelines for the scenario shown in Figure 7-29 is similar to those for
the scenario shown in Figure 7-29.
l


Issue 01 (2014-04-30)
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

170
SingleRAN

Figure 7-30 shows an example of network topology for main-control-board-based IP cotransmission through backplane interconnection on the separate-MPT UG+L multimode base
station side.
through backplane interconnection on the separate-MPT UG+L multimode base station side

Issue 01 (2014-04-30)
Item
IP Address
Remarks
10.10.10.10/32
21.21.21.1/24

RNC
15.15.15.15/32
11.11.11.11/24

RNC
11.11.11.254/24

171
SingleRAN
Issue 01 (2014-04-30)
Item
IP Address
Remarks

BSC
21.21.21.254/24

UMPT_U
20.20.20.1/24
30.30.30.1/24

control board.
of the NodeB
32.32.32.1/24

control board.

UMPT_U of the NodeB
20.20.20.188/24

CME. This IP address is
configured on the cotransmission port.
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
60.60.60.60/24

the OM channel
eNodeB
31.31.31.188/24

of the eNodeB
33.33.33.188/24

control board.
35.35.35.188/24
control board.
BTS ESN
abcdefghijklmn

172
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 UCIU through the CI interface.
The IP address plan for IP co-transmission in UCIU+UMPT interconnection is the same as that in UMPT
+UMPT interconnection.

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSBRD
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Board Type
BT
Board Type
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
Link No.
LN
Link No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Upper Node Cabinet

No.
UPCN
Upper Node Cabinet

No.
Upper Node Subrack

No.
UPSRN
Upper Node Subrack

No.
Upper Node Slot No.
UPSN
Upper Node Slot No.
Upper Node Port No.
UPPT
Upper Node Port No.
BTS Index Type
IDTYPE
BTS Index Type
BTS Index
BTSID
BTS Index
Source Cabinet No.
SRCCN
Source Cabinet No.
BTSCTRLLNK
BTSTUNNEL
Issue 01 (2014-04-30)

173
SingleRAN
MO
BTSDEVIP
BTSIP
BTSIPRT
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Source Subrack No.
SRCSRN
Source Subrack No.
Source Slot No.
SRCSN
Source Slot No.
BTS Tunnel No.
TN
BTS Tunnel No.
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
DSTSN
BTS Index Type
IDTYPE
BTS Index Type
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
Port No.
PN
Port No.
Port Cabinet No.
CN
Port Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
BTS Index Type
IDTYPE
BTS Index Type
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
BTS
Communication
Type
BTSCOMTYPE
BTS
Communication
Type
BTS IP
BTSIP
BTS IP
BSC IP
BSCIP
BSC IP
BTS MultiIP Switch
BTSMUTIP
BTS MultiIP Switch
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Route Index
RTIDX
Route Index
Destination IP
Address
DSTIP
Destination IP
Address

174
SingleRAN
MO
BTSESN
IPRT
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Destination Address
Mask
DSTMASK
Destination Address
Mask
Route Type
RTTYPE
Route Type
Port Cabinet No.
CN
Port Cabinet No.
Port Subrack No.
SRN
Port Subrack No.
Port Slot No.
SN
Port Slot No.
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
BTS Index Type
IDTYPE
BTS Index
BTSID
BTS Index
OM Bear Board
OMBEARBOARD
OM Bear Board
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Destination IP
address
DSTIP
Destination IP
address
Destination address
mask
DSTMASK
Destination address
mask
Forward route
address
NEXTHOP
Forward route
address

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BRD
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Board Type
BT
SubBoard Type
SBT
Local Link No.
LN
Local Link No.
Local Cabinet No.
CN
Local Cabinet No.
CTRLLNK
Issue 01 (2014-04-30)

175
SingleRAN
MO
TUNNEL
IPRT
DHCPSVRIP
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Local Subrack No.
SRN
Local Subrack No.
Local Slot No.
SN
Local Slot No.
Upper Cabinet No.
UPCN
Upper Cabinet No.
Upper Subrack
No.
UPSRN
Upper Subrack No.
Upper Slot No.
UPSN
Upper Slot No.
Upper Port No.
UPPT
Upper Port No.
Source Cabinet
No.
SCN
Source Cabinet No.
Source Subrack
No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination
Cabinet No.
DCN
Destination Cabinet
No.
Destination
Subrack No.
DSRN
Destination
Subrack No.
Destination Slot
No.
DSN
Destination Slot
No.
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address

176
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
DHCPRELAYSWITC
H
DHCP Relay
Switch
ES
DHCP Switch
VLANMAP
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN
Priority
SETPRIO
Set VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLANCLASS

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CTRLLNK
Local Link No.
LN
Local Link No.
Local Cabinet No.
CN
Local Cabinet No.
Local Subrack No.
SRN
Local Subrack No.
Local Slot No.
SN
Local Slot No.
Upper Cabinet No.
UPCN
Upper Cabinet No.
Upper Subrack No.
UPSRN
Upper Subrack No.
Upper Slot No.
UPSN
Upper Slot No.
Upper Port No.
UPPT
Upper Port No.
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
TUNNEL
Issue 01 (2014-04-30)

177
SingleRAN
MO
DEVIP
IPRT
RSCGRP
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
DCN
Destination Cabinet
No.
DSRN
Destination Subrack
No.
DSN
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Port No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Group Bear Type
BEAR
Transmission
Resource Group
Bear Type
Subboard Type
SBT
Subboard Type

178
SingleRAN
MO
IPPath
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Bearing Port Type
PT
Bearing Port Type
Bearing Port No.
PN
Bearing Port No.
Group ID
RSCGRPID
Transmission
Resource Group ID
Rate Unit
RU
Rate Unit
Tx Bandwidth
TXBW
Tx Bandwidth
Rx Bandwidth
RXBW
Rx Bandwidth
TX Committed Burst
Size
TXCBS
TX Committed Burst
Size
TX Excessive Burst Size
TXEBS
TX Excessive Burst
Size
Operator ID
OID
Operator ID
Scheduling Weight
WEIGHT
Scheduling Weight
TX Committed
Information Rate
TXCIR
TX Committed
Information Rate
RX Committed
Information Rate
RXCIR
RX Committed
Information Rate
TX Peak Information
Rate
TXPIR
TX Peak Information
Rate
RX Peak Information
Rate
RXPIR
RX Peak Information
Rate
TX Peak Burst Size
TXPBS
TX Peak Burst Size
IP Path ID
PATHID
IP Path ID
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
Join Transmission
Resource Group
JNRSCGRP
Join Transmission
Resource Group

179
SingleRAN
MO
OMCH
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Group ID
RSCGRPID
Transmission
Resource Group ID
Local IP
LOCALIP
Local IP
Peer IP
PEERIP
Peer IP
Path Type
PATHTYPE
Path Type
Local IP
IP
Local IP
Local Mask
MASK
Local Mask
Peer IP
PEERIP
Peer IP
Peer Mask
PEERMASK
Peer Mask
Bearer Type
BEAR
Bearer Type
Binding Route
BRT
Binding Route
7.16.3 Precautions
None

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

other route to the lower-level transmission port of the NodeB.

Issue 01 (2014-04-30)

180
SingleRAN
Using MML Commands
Step 1 (UCIU+UMPT interconnection) 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.
(UCIU+UMPT interconnection) ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=10,
SRN=1, SN=7, UPCN=0, UPSRN=0, UPSN=0, UPPT=0;
//Add a BBU interconnection control link between slot 7 of subrack
subrack 0.
(UMPT+UMPT interconnection) ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=10,
//Add a BBU interconnection control link between slot 7 of subrack
subrack 0.
LN=0, CN=0,
1 and slot 0 of
LN=0, CN=0,
1 and slot 7 of
UMPT_U.
DSTSRN=0, DSTSN=7;
//Add a tunnel from the GTMUb in slot 6 to the UMPT_U in slot 7.
IP="35.35.35.188", MASK="255.255.255.0";
IFNO=0;
Issue 01 (2014-04-30)

181
SingleRAN
Step 8 (Optional) Run the BSC MML command ADD IPRT to add a route to the DHCP relay of the
BTS. 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.
----End
l

On the CME, set the parameters listed in Data Preparation on the GSM Side section. For
instructions on how to perform the CME single configuration, see CME Single
Initial Configuration on the eNodeB Side

l
Using MML Commands

NOTE
required.
Step 1 Run the eNodeB MML command ADD CTRLLNK to add a BBU interconnection control link.
(UCIU+UMPT interconnection) 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. The BBU subrack number for the eNodeB must be different from that for
the BTS and NodeB. It is assumed that the BBU subrack number for the eNodeB is 1
here.
(UMPT+UMPT interconnection) ADD CTRLLNK: LN=0, CN=0, SRN=1, SN=7, UPCN=0, UPSRN=0,
UPSN=7, UPPT=8;
subrack 0. The BBU subrack number for the eNodeB must be different from that for
the BTS and NodeB. It is assumed that the BBU subrack number for the eNodeB is 1
here.
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.
Issue 01 (2014-04-30)

182
SingleRAN

MASK="255.255.255.0";
group.
TUNNEL.
----End
l

On the CME, set the parameters listed in Data Preparation on the eNodeB Side section.

Issue 01 (2014-04-30)

183
SingleRAN
Using MML Commands
MASK="255.255.255.0";
MASK="255.255.255.0";
Step 2 Run the NodeB MML command ADD CTRLLNK to add a BBU interconnection control link.
(UCIU+UMPT interconnection)
UPSN=0, UPPT=0;
//Add a BBU interconnection
subrack 0.
(UMPT+UMPT interconnection)
UPSN=7, UPPT=8;
//Add a BBU interconnection
subrack 0.
ADD CTRLLNK: LN=0, CN=0, SRN=1, SN=7, UPCN=0, UPSRN=0,

control link between slot 7 of subrack 1 and slot 0 of
ADD CTRLLNK: LN=0, CN=0, SRN=1, SN=7, UPCN=0, UPSRN=0,
control link between slot 7 of subrack 1 and slot 7 of
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.
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 BTS to the BSC through the NodeB for the UMPT_U in slot 7.
//Add a route from the eNodeB to the MME through the NodeB for the UMPT_U in slot
7.
//Add a route from the eNodeB to the S-GW through the NodeB for the UMPT_U in slot
7.
//Add a route from the eNodeB to the U2000 through the NodeB for the UMPT_U in slot
U2000.
through the NodeB and a downlink route from the MME/S-GW/U2000 to the eNodeB through
the NodeB.
UMPT_U backplane, the downlink route from the BSC to the BTS through the NodeB and the
Issue 01 (2014-04-30)

184
SingleRAN
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.
//Add a downlink route from the BSC to the BTS through the NodeB for the UMPT_U in
slot 7.
//Add a downlink route from the MME/S-GW/U2000 to the eNodeB through the NodeB for
the UMPT_U in slot 7.
relay.
if the BTS is deployed using DHCP. Therefore, DHCP relay needs to be enabled for the NodeB.
DHCP server.
if the BTS is deployed using DHCP. Therefore, the IP address of the DHCP server needs to be
added on the NodeB. The DHCP server of the BTS is BSC, while the DHCP server of the eNodeB
is U2000.
uplink route from the BTS 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 address of the uplink route
from the BTS to the BSC through the NodeB to 20.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 20.20.20.201,
which is different from the next-hop address (20.20.20.1) of the uplink route for the NodeB.
To add VLAN mapping, run the MML command ADD VLANMAP
differentiated DSCP values for the BTS, eNodeB, and NodeB. For details about DSCP values
Issue 01 (2014-04-30)

185
SingleRAN
for the BTS, NodeB, and eNodeB, see Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description.
1.

2.

----End
l

On the CME, set the parameters listed in the Data Preparation on the UMTS Side. For

device.
UMTS Side
on the NodeB side to verify whether the transmission link between the NodeB and the RNC is
normal:
----End
GSM Side
Issue 01 (2014-04-30)

186
SingleRAN
----End
LTE Side
----End
7.17 Reconstruction from Transmission Through the Main

Control Board Panel on a BTS 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 BTS to main-control-board-based IP co-transmission through
panel interconnection on the separate-MPT UG multimode base station side.

l
Figure 7-31 shows the network topologies before and after reconstruction.
Issue 01 (2014-04-30)

187
SingleRAN
Figure 7-31 Network topologies before and after reconstruction


Figure 7-32 shows an example of reconstruction from transmission through the main control
board panel on a BTS to main-control-board-based IP co-transmission through panel
interconnection on the separate-MPT UG multimode base station side.
Issue 01 (2014-04-30)

188
SingleRAN
Figure 7-32 Example of reconstruction from transmission through the main control board panel
on a BTS to main-control-board-based IP co-transmission through panel interconnection on the
separate-MPT UG multimode base station side

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
When DHCP relay is 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.
21.21.21.1/24
11.11.11.11/24

RNC
15.15.15.15/32
Port IP address of the U2000
60. 60. 60.60/24
IP address of the port on

router 1 that is connected to
the BSC
21.21.21.254/24

189
SingleRAN
Item
Instance
Remarks

the RNC
11.11.11.254/24

the NodeB
20.20.20.1/24
IP address of FE 0 port on the

NodeB
22.22.22.1/24

NodeB
20.20.20.188/24
24.24.24.24/24

BTS
22.22.22.188/24
NOTE
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 BTS.
7.17.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 BTS using messages before reconstruction. After receiving the new data, the BTS saves
it to the flash memory. Once the BTS 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 BTS deletes the old IP transmission configuration data.
Reconstruction Preparations
1.
Check the system.

l 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.
l Run the BSC MML command DSP BTSVER or NodeB MML command LST VER
to check the software version for a BTS or NodeB.
2.
Get ready boards and obtain software versions.

l Get ready a WMPT.
l Obtain the software versions of the MBSC, U2000, CME, and multimode base station.
Issue 01 (2014-04-30)

190
SingleRAN
3.
Back up data.
l Back up the measurement results of original performance counters reported one week
before reconstruction.
l Back up BTS data configurations before reconstruction on the CME. (CME: Main
View > Right-click a site > Export MML for Creating BTS.)
4.
Make the reconfiguration scripts.

l For details about reconfiguration on the UMTS side, see Reconfiguration on the
UMTS Side.
l Reconfiguration on the GSM side has the following scripts:
IP rehoming scripts. For details, see Reconfiguration on the GSM Side.
Scripts for reconstruction. For details, see Initial Configuration on the GSM
Side 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.

l For details about rollback scripts on the UMTS side, see Rollback on the UMTS
Side.
l For details about rollback scripts on the GSM side, see Rollback on the GSM Side
Reconstruction Procedure
Step 1 Upgrade the software.
If the BTS software version does not meet the reconstruction requirements, upgrade the software
Step 2 Reconstruct hardware and modify data configurations.
1.
Execute the BSC IP rehoming MML command scripts.

NOTE
Upgrade the software Remove the GTMU and install the WMPT at the site. Connect the GTMU to
the WMPT through panel interconnection, and connect the transmission cable to the planned port on
the WMPT.
2.
Deactivate the BTS on the BSC and prepare for scripts for BTS reconstruction to reactivate
the BTS.
3.
Use the scripts for BTS reconstruction to perform automatic NodeB deployment.
4.
Install and power on the GTMU, and wait for BTS deployment.
Step 3 Verify services after reconstruction. For details, see section 7.5.6 Activation Observation.
Step 4 Perform the rollback operation if reconstruction fails.
l Execute the rollback scripts. For details about the rollback scripts, see section 7.17.6
Rollback
l Restore the hardware configuration and network topology to those before reconstruction.
----End
Issue 01 (2014-04-30)

191
SingleRAN
7.17.4 Precautions
None
7.17.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 BTS 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="30.30.30.1";
Step 2 Run the BSC MML command ACT BTSIMPDATA to activate the IP rehoming data.
ACT BTSIMPDATA: IDTYPE=BYID, BTSID=10;
----End
7.17.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 BTS. (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.)
RMV IPPATH: ANI=1017, PATHID=0;
//Remove the IP path between the BTS 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 BTS. (CME: Base Station > GSM >
Right-click a site > Delete Site.)
RMV BTS: IDTYPE=BYID, BTSID=10;
Issue 01 (2014-04-30)

192
SingleRAN
Step 5 Execute the configuration scripts that are backed up before reconstruction. (CME: Script
Executor > Project > Load Project > Upload Project > Activate Project.)
----End

Co-Transmission Through Backplane Interconnection on
the Separate-MPT LG/TG Multimode Base Station Side in
IP over FE/GE Mode
backplane interconnection on the separate-MPT LG multimode base station side.

l
Issue 01 (2014-04-30)

193
SingleRAN

NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

board panel on a BTS to main-control-board-based IP co-transmission through backplane
interconnection on the separate-MPT LG multimode base station side.
Issue 01 (2014-04-30)

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

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

BSC
21.21.21.254/24

eNodeB
20.20.20.1/24

195
SingleRAN
Item
Instance
Remarks

eNodeB
20.20.20.188/24

CME
eNodeB
31. 31. 31.188/24

of the eNodeB
33.33.33.188/24

plane IP address.
and is configured on the main
control board.
60.60.60.60/24

OM channel
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
35.35.35.188/24
control board.
ESN of the BTS
abcdefghijklmn

1.
Check the system.

l Run the BSC MML command DSP BTSVER to check the software version for a BTS.
Multimode base stations of V100R007C00 and later support IP-based co-transmission
through backplane interconnection.
2.

l Check whether the main control board of the BTS is a GTMUb. If the main control
board of the BTS is not a GTMUb, get ready a GTMUb.
l Get ready an LMPT/UMPT_L.
Issue 01 (2014-04-30)

196
SingleRAN
3.
Back up data.
4.

l For details about reconfigurations on the eNodeB side, see Reconfiguration on the
eNodeB Side.
Side "in section 7.9 Main-Control-Board-based IP Co-Transmission Through
Backplane Interconnection on the Separate-MPT LG/TG Multimode Base
Station Side
5.

l For details about rollback scripts on the eNodeB side, see Rollback on the LTE
Side.
l For details about rollback scripts on the BTS side, see Rollback on the GSM Side.
6.
Prepare for automatic deployment.

l 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 BTS before the reconstruction. The second USB
flash drive is used for the automatic deployment in case that the reconstruction fails.
l 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.
1.

NOTE
BTS 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 eNodeB is deployed. This is because the IP rehoming
scripts take effect only after the BTS 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.
the BTS.
Issue 01 (2014-04-30)

197
SingleRAN
4.
Perform automatic eNodeB deployment. For details about automatic deployment, see 3900
Series Base Station Commissioning Guide.
5.
Install and power on the GTMUb, and wait for BTS deployment.
Rollback
----End
7.18.4 Precautions
None
Reconfiguration on the eNodeB Side
For details, see Initial Configuration on the LTE Side in section 7.9 Main-Control-Boardbased IP Co-Transmission Through Backplane Interconnection on the Separate-MPT LG/
TG Multimode Base Station Side.

Step 1 Run the BSC MML command IMP BTSIPPARA to import the communication IP address of
the BTS.
IMP BTSIPPARA: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, IPPHYTRANSTYPE=IP_OVER_FE/GE,
BTSCOMTYPE=LOGICIP, BTSIP="35.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 BTS.
IMP BTSDEVIP: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, PT=LOOPINTERFACE, PN=0, CN=0,
SRN=0, SN=6, IPIDX=0, IP="35.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 BTS to the BSC.
IFNO=1;
----End
Issue 01 (2014-04-30)

198
SingleRAN
7.18.6 Rollback
Rollback on the LTE Side
Remove the eNodeB on the CME. (CME: Base Station > LTE > Right-click a site > Delete.)

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

Co-Transmission Through Backplane Interconnection on
the Separate-MPT UG Multimode Base Station Side
backplane interconnection on the separate-MPT UG multimode base station side.

l
Issue 01 (2014-04-30)

199
SingleRAN


board panel on a BTS to main-control-board-based IP co-transmission through backplane
interconnection on the separate-MPT UG multimode base station side.
Issue 01 (2014-04-30)

200
SingleRAN
on a BTS to main-control-board-based IP co-transmission through backplane interconnection
on the separate-MPT UG multimode base station side

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

BSC
21.21.21.254/24

RNC
11.11.11./24

NodeB
20.20.20.1/24

201
SingleRAN
Item
Instance
Remarks
30.30.30.1/24

of the NodeB
32.32.32.1/24

control board.

UMPT_U of the NodeB
20.20.20.188/24

CME

RNC
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24

the OM channel
35.35.35.188/24
address of the BTS.
main control board.
BTS ESN
abcdefghijklmn

1.
Check the system.

2.

l Check whether the main control board of the BTS is a GTMUb. If the main control
board of the BTS is not a GTMUb, get a GTMUb ready.
Issue 01 (2014-04-30)

202
SingleRAN
l Get ready a UMPT_U.

l Obtain the software versions of the MBSC, U2000, CME, and MULTIMODE BASE
STATION.
3.
Back up data.
4.

l For details about reconfigurations on the NodeB side, see Reconfiguration on the
UMTS Side.
Side in section 7.10 Main-Control-Board-based Co-Transmission Through
Backplane Interconnection on the Separate-MPT UG Multimode Base Station
Side in IP over FE/GE Mode.
5.

l For details about rollback scripts on the eNodeB side, see Rollback on the UMTS
Side.
l For details about rollback scripts on the BTS side, see Rollback on the GSM Side.
6.

flash drive for the reconstructed UG multimode base station, and prepare another
commissioning USB flash drive for the BTS before the reconstruction. The second USB
flash drive is used for the automatic deployment in case that the reconstruction fails.
l 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.
1.

NOTE
BTS 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 BTS resets. In addition, the IP rehoming scripts are effective within
specified time.
2.
Issue 01 (2014-04-30)
Remove the GTMUb and install the UMPT_U at the site. Connect the transmission cable
to the planned port on the UMPT_U.
203
SingleRAN
3.
the BTS.
4.
Perform automatic NodeB deployment. For details about automatic deployment, see 3900
5.
Install and power on the GTMUb, and wait for BTS deployment.
Rollback.
----End
7.19.4 Precautions
None
For details, see Initial Configuration on the UMTS Side in section 7.10 Main-Control-Boardbased Co-Transmission Through Backplane Interconnection on the Separate-MPT UG
Multimode Base Station Side in IP over FE/GE Mode.

the BTS.
the GTMUb to the LMPT/UMPT_L.
IFNO=1;
----End
Issue 01 (2014-04-30)

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

Path.)
----End

Control Board Panel on a NodeB to Main-Control-Boardbased Co-Transmission Through Backplane
Interconnection on the Separate-MPT UL/UT Multimode
main control board panel on a NodeB to main-control-board-based IP co-transmission through
backplane interconnection on the UL multimode base station side.

l
Issue 01 (2014-04-30)

205
SingleRAN

Issue 01 (2014-04-30)
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

206
SingleRAN

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

Issue 01 (2014-04-30)
Item
Instance
Remarks

RNC
15.15.15.15/32
11.11.11.11/24

207
SingleRAN
Item
Instance
Remarks

RNC
11.11.11.254/24

UMPT_U
20.20.20.1/24
30.30.30.1/24

IP address.
Issue 01 (2014-04-30)
of the NodeB
32.32.32.1/24

configured on the NodeB
main control board.
of the eNodeB
33.33.33.188/24

main control board.
eNodeB
31.31.31.188/24

board.

UMPT_U of the NodeB
20.20.20.188/24

CME
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
60.60.60.60/24

for the OM channel

208
SingleRAN

1.
Check the system.

l Run the NodeB MML command LST VER to check the software version for a NodeB.
2.

l Get ready the optical modules, and eNodeB hardware. 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 the 3900 Series Base Station Initial Configuration Guide.
3.
Back up data.
l 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.)
4.

UMTS Side.
l For details about reconfigurations on the eNodeB side, see Initial Configuration on
the LTE Side in section 7.12 Main-Control-Board-based Co-Transmission
Through Backplane Interconnection on the Separate-MPT UL/UT Multimode
Base Station Side in IP over FE/GE Mode.
5.

l For details about rollback scripts on the GSM side, see Rollback on the UMTS Side.
Side.
6.

flash drive for the reconstructed UL multimode base station, and prepare another
commissioning USB flash drive for the NodeB before the reconstruction. The second
USB flash drive is used for the automatic deployment in case that the reconstruction
fails.
l 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:
New configuration files for the NodeB and eNodeB
Issue 01 (2014-04-30)

209
SingleRAN
NodeB configuration file backed up before the reconstruction
Step 1 Reconstruct hardware.
1.
Replace the WMPT with the UMPT_U.
2.
Connect the transmission cable to the planned port on the UMPT_U.
3.
Install the eNodeB.
Step 2 Modify data configurations for NodeB.

1.
Perform automatic NodeB deployment. For details about automatic deployment, see 3900
2.
Wait for 10 minutes, and check that services processed on the NodeB are normal on the
U2000.
Step 3 Perform automatic eNodeB deployment. For details about automatic deployment, see 3900
Rollback.
----End
7.20.4 Precautions
None
For details, see Initial Configuration on the UMTS Side in section 7.12 Main-Control-Boardbased Co-Transmission Through Backplane Interconnection on the Separate-MPT UL/
UT Multimode Base Station Side in IP over FE/GE Mode.
Reconfiguration on the LTE Side

For details, see Initial Configuration on the LTE Side in section 7.12 Main-Control-Boardbased Co-Transmission Through Backplane Interconnection on the Separate-MPT UL/
UT Multimode Base Station Side in IP over FE/GE Mode.
7.20.6 Rollback
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.
Issue 01 (2014-04-30)

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

7.21 Reconstruction from Main-Control-Board-based IP CoTransmission Through Panel Interconnection to UTRPcbased Co-Transmission Through Backplane
Station Side in IP over FE/GE Mode
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.

l
l
Issue 01 (2014-04-30)

211
SingleRAN

Figure 7-40 shows an example of reconstruction from main-control-board-based IP cotransmission through panel interconnection to UTRPc-based IP co-transmission through
backplane interconnection on the separate-MPT UG multimode base station side.
Figure 7-40 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 UG multimode base station side
Issue 01 (2014-04-30)

212
SingleRAN

Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
11.11.11.11/24

RNC
15.15.15.15/32
60.60.60.60/24

the OM channel

BSC
21.21.21.254/24

RNC
11.11.11.254/24

NodeB
20.20.20.1/24

UTRPc of the NodeB
20.20.20.188/24
30.30.30.1/24

of the NodeB
32.32.32.1/24

control board.
30.30.30.188/24
ESN of the BTS
abcdefghijklmn

1.
Issue 01 (2014-04-30)
Check the system.

213
SingleRAN
2.

l Get ready a GTMUb if the main control board of the BTS is not a GTMUb.
l Get ready a UTRPc.
3.
Back up data.
Files.)
4.

UMTS Side..
IP rehoming scripts. For details, see Reconfiguration on the GSM Side..
Side in section 7.11 UTRPc-based Co-Transmission Through Backplane
Interconnection on the Separate-MPT UG Multimode Base Station Side in IP
over FE/GE Mode.
5.

l For details about rollback scripts on the UMTS side, see Rollback on the GSM Side.
l For details about rollback scripts on the GSM side, see Rollback on the UMTS Side"
6.

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.
Issue 01 (2014-04-30)

214
SingleRAN
If the software version of the multimode base station does not meet the reconstruction
requirements, upgrade the software before reconstruction.
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 LST VER to check whether the
UTRPc software version is correct.
DSP BRD: CN=0, SRN=0, SN=4;
LST VER: 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.
4.

NOTE
BTS and NodeB services are interrupted when steps 5 to 9 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 BTS 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 BTS on the BSC, and execute the scripts for reconstruction to reactivate the
BTS.
8.
Check that the NodeB maintenance links are normal on the U2000. Install and power on
the GTMUb of the BTS to make the BTS IP rehoming scripts take effect.
9.
Wait for 10 minutes, and check that services processed on the BTS and NodeB are normal
on the U2000.
Step 3 Verify services after reconstruction. For details, see 7.11.6 Activation Observation.
Rollback.
----End
7.21.4 Precautions
None
Issue 01 (2014-04-30)

215
SingleRAN
For details, see Initial Configuration on the UMTS Side in section 7.11 UTRPc-based CoTransmission 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:
the BTS.
the GTMUb to the UTRPc.
IFNO=0;
----End
7.21.6 Rollback
Step 1 Run the BSC MML command DEA BTS to deactivate the BTS.
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 BTS.
Issue 01 (2014-04-30)

216
SingleRAN
Step 5 Execute the configuration scripts that are backed up before reconstruction.
----End

7.22 Reconstruction from UTRPc-BackplaneInterconnection Co-Transmission on the Separate-MPT UG

Multimode Base Station Side to UTRPc-BackplaneInterconnection Co-Transmission on the Separate-MPT 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 cotransmission 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.

l
Issue 01 (2014-04-30)

217
SingleRAN

Issue 01 (2014-04-30)
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

218
SingleRAN

Figure 7-42 shows an example of reconstruction from UTRPc-based IP co-transmission through
backplane interconnection on the separate-MPT UG multimode base station side to UTRPcbased IP co-transmission through backplane interconnection on the separate-MPT UG+L
multimode base station side.
Issue 01 (2014-04-30)

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

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

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32

220
SingleRAN
Issue 01 (2014-04-30)
Item
Instance
Remarks
21.21.21.1/24

BSC
21.21.21.254/24

RNC
15.15.15.15/32
11.11.11.11/24

RNC
11.11.11.254/24
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
60.60.60.60/24

OM channel

UTRPc of the NodeB
20.20.20.1/24

UTRPc of the NodeB
20.20.20.188/24

CME
of the NodeB
32.32.32.1/24

control board.
30.30.30.1/24

eNodeB
31.31.31.188/24

CME
of the eNodeB
33.33.33.188/24

control board.

221
SingleRAN
Item
Instance
Remarks
35.35.35.188/24
control board.
ESN of the BTS
abcdefghijklmn

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSBRD
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Board Type
BT
Board Type
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
Link No.
LN
Link No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Upper Node Cabinet

No.
UPCN
Upper Node Cabinet

No.
Upper Node Subrack

No.
UPSRN
Upper Node Subrack

No.
Upper Node Slot No.
UPSN
Upper Node Slot No.
Upper Node Port No.
UPPT
Upper Node Port No.
BTSCTRLLNK
Issue 01 (2014-04-30)

222
SingleRAN

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BRD
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Board Type
BT
SubBoard Type
SBT
Local Link No.
LN
Local Link No.
Local Cabinet No.
CN
Local Cabinet No.
Local Subrack No.
SRN
Local Subrack No.
Local Slot No.
SN
Local Slot No.
Upper Cabinet No.
UPCN
Upper Cabinet No.
Upper Subrack No.
UPSRN
Upper Subrack No.
Upper Slot No.
UPSN
Upper Slot No.
Upper Port No.
UPPT
Upper Port No.
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
CTRLLNK
TUNNEL
IPRT
Issue 01 (2014-04-30)

223
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Switch

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CTRLLNK
Local Link No.
LN
Local Link No.
Local Cabinet No.
CN
Local Cabinet No.
Local Subrack No.
SRN
Local Subrack No.
Local Slot No.
SN
Local Slot No.
Upper Cabinet No.
UPCN
Upper Cabinet No.
Upper Subrack No.
UPSRN
Upper Subrack No.
Upper Slot No.
UPSN
Upper Slot No.
Upper Port No.
UPPT
Upper Port No.
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Cabinet No.
CN
Cabinet No.
TUNNEL
DEVIP
Issue 01 (2014-04-30)

224
SingleRAN
MO
IPRT
RSCGRP
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Port No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Transmission
Resource Group
Bear Type
BEAR
Transmission
Resource Group
Bear Type
Subboard Type
SBT
Subboard Type
Bearing Port Type
PT
Bearing Port Type
Bearing Port No.
PN
Bearing Port No.
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
Rate Unit
RU
Rate Unit
Tx Bandwidth
TXBW
Tx Bandwidth

225
SingleRAN
MO
IPPath
OMCH
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Rx Bandwidth
RXBW
Rx Bandwidth
TX Committed Burst
Size
TXCBS
TX Committed Burst
Size
TX Excessive Burst
Size
TXEBS
TX Excessive Burst
Size
Operator ID
OID
Operator ID
Scheduling Weight
WEIGHT
Scheduling Weight
TX Committed
Information Rate
TXCIR
TX Committed
Information Rate
RX Committed
Information Rate
RXCIR
RX Committed
Information Rate
TX Peak Information
Rate
TXPIR
TX Peak Information
Rate
RX Peak Information
Rate
RXPIR
RX Peak Information
Rate
TX Peak Burst Size
TXPBS
TX Peak Burst Size
IP Path ID
PATHID
IP Path ID
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
Join Transmission
Resource Group
JNRSCGRP
Join Transmission
Resource Group
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
Local IP
LOCALIP
Local IP
Peer IP
PEERIP
Peer IP
Path Type
PATHTYPE
Path Type
Local IP
IP
Local IP
Local Mask
MASK
Local Mask

226
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Peer IP
PEERIP
Peer IP
Peer Mask
PEERMASK
Peer Mask
Bearer Type
BEAR
Bearer Type
Binding Route
BRT
Binding Route

1.
Check the system.

to check the software version for a BTS or NodeB. Multimode base stations of
V100R007C00 and later support IP-based co-transmission through backplane
interconnection.
2.

l Get ready the UCIU, optical modules, and eNodeB hardware. 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).
3.
Back up data.
Files.)
4.

l For details about reconfiguration on the GSM side, see Reconfiguration on the GSM
Side.
l For details about reconfiguration on the UMTS side, see "Reconfiguration on the
UMTS Side.".
Issue 01 (2014-04-30)

227
SingleRAN
l For details about reconfigurations on the LTE side, see Reconfiguration on the LTE
Side.
5.

l For details about rollback scripts on the GSM side, see Rollback on the GSM Side.
Side.
l For details about rollback scripts on the LTE side, see Rollback on the LTE Side
6.

flash drive for the reconstructed UGL multimode base station, and prepare another
Step 2 Reconstruct hardware. For details, see section 7.22.6 Hardware Adjustment.
Step 3 Modify data configurations.
l Execute reconstruction scripts for the NodeB on the U2000 side.
Step 4 Execute the site deployment scripts for the eNodeB on the U2000 according to the procedure
for deploying an eNodeB. For details about how to make site deployment scripts, see eNodeB
Initial Configuration(CME) or eNodeB Initial Configuration Guide. For details about the
changes related to co-transmission, see "Reconfiguration on the eNodeB Side." Verify services
after reconstruction. For details, see section 7.15.6 Activation Observation.
Rollback
----End
7.22.4 Precautions
None
Issue 01 (2014-04-30)

228
SingleRAN
l
Using MML Commands
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
ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=0, LN=0, CN=0, SRN=1, SN=7, UPCN=0, UPSRN=0,
UPSN=0, UPPT=0;
subrack 0.
----End
l


l
Using MML Commands
Step 1 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 2 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="31.31.31.188",
DSTM2ASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
DSTM2ASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
2.
Add a next-hop route from the UTRPc to the S1 signaling plane on the MME.
ADD IPRT: RTIDX=2, CN=0, SRN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="40.40.40.40",
3.
Issue 01 (2014-04-30)
Add a next-hop route from the UTRPc to the S-GW.

229
SingleRAN
ADD IPRT: RTIDX=3, CN=0, SRN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="50.50.50.50",

Step 3 Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP relay.
Step 4 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 IP address list. In this scenario, DHCP server can forward DHCP packets for
the eNodeB.
----End
l


l
Using MML Commands

NOTE
required.
Step 1 Run the eNodeB MML command ADD CTRLLNK to add a control link between BBU
subracks.
ADD CTRLLNK: LN=0, CN=0, SRN=1, SN=7, UPCN=0, UPSRN=0, UPSN=0, UPPT=0;
//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 BTS 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;
Step 3 Run the eNodeB MML command ADD DEVIP to set the IP address of the eNodeB. In this step,
set PT to LOOPINT.
ADD DEVIP: CN=0, SRN=1, SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="33.33.33.188",
MASK="255.255.255.0";
//CN specifies the number of the cabinet accommodating the board where the Ethernet
port is located. SRN specifies the number of the subrack accommodating the board
where the Ethernet port is located. SN specifies the number of the slot
accommodating the board where the Ethernet port is located. PN specifies the number
Issue 01 (2014-04-30)

230
SingleRAN
of the Ethernet port.
Step 4 Run the eNodeB MML command ADD IPRT to add a route to a tunnel. In this step, set
IFNO to the number of the tunnel on the backplane of the eNodeB (0).
1.
Add a route from the eNodeB to the MME.

ADD IPRT: RTIDX=0, CN=0, SRN=1, SN=7, SBT= BACK_BOARD, DSTIP="40.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.

PEERMASK="255.255.255.0", BEAR=IPV4, CN=0, SRN=1, SN=7, SBT=BACK_BOARD, BRT=NO;
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


l
Insert a UCIU into the original BBU subrack.
Install the eNodeB. The main control board for the eNodeB is UMPT_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.
Issue 01 (2014-04-30)

231
SingleRAN
7.22.7 Rollback
Step 1 Run the RMV BTSCTRLLNK command to remove the BBU interconnection control link
RMV BTSCTRLLNK: IDTYPE=BYID, BTSID=0, LN=0;
//Remove the BBU interconnection control link between slot 7 of subrack 1 and slot
0 of subrack 0.
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


Step 1 Run the NodeB MML command RMV IPRT to remove routes.
1.
Remove a route to the tunnel from the UTRPc to the eNodeB.

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, DCN=0, DSRN=1, DSN=7;
----End
7.23 Reconstruction from Main-Control-Board-based CoTransmission Through Panel Interconnection on the UG

Multimode Base Station Side to UTRPc-based CoTransmission Through Backplane Interconnection on the
Separate-MPT UG+L/UG+T Multimode Base Station Side
IP co-transmission 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.
Issue 01 (2014-04-30)

232
SingleRAN

l

Issue 01 (2014-04-30)

233
SingleRAN
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

Figure 7-44 shows an example of reconstruction from main-control-board-based IP cotransmission through panel interconnection on the separate-MPT UG multimode base station
side to UTRPc-based IP co-transmission through backplane interconnection on the separateMPT UG+L multimode base station side.
Issue 01 (2014-04-30)

234
SingleRAN

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

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

235
SingleRAN
Issue 01 (2014-04-30)
Item
Instance
Remarks

RNC
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24

BSC
21.21.21.254/24

RNC
11.11.11.254/24

NodeB
20.20.20.1/24


UTRPc of the NodeB
20.20.20.188/24

30.30.30.1/24

of the NodeB
32.32.32.1/24

control board.
35.35.35.188/24
control board.
eNodeB
31.31.31.188/24


236
SingleRAN
Item
Instance
Remarks
of the eNodeB
33.33.33.188/24

main control board.
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
ESN of the BTS
abcdefghijklmn

1.
Check the system.

interconnection.
2.

l Get ready the UTRPc, UCIU, optical modules, and eNodeB hardware. 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.
3.
Back up data.
Files.)
4.

Issue 01 (2014-04-30)

237
SingleRAN

Side in section 7.15 UTRPc-based Co-Transmission Through Backplane
Interconnection on the Separate-MPT UG+L/UG+T Multimode Base Station
Side in IP over FE/GE Mode.
UMTS Side.
l For details about reconfigurations on the eNodeB side, see Reconfiguration on the
GSM Side.
5.

Side.
l For details about rollback scripts on the GSM side, see Rollback on the GSM Side.
Side.
6.

flash drive for the reconstructed UGL multimode base station, and prepare another
1.
Run the ADD BRD command to add a UTRPc. (CME: Main View > Right-click a site >
Device Panel > BBU3900 > Right-click a slot > ADD UTRP > Right-click the UTRP >
ADD UTRPc)
2.
Run the BTS MML command ADD BTSBRD to add a UCIU. (CME: Root > Right-click
a site > Device Panel > Right-click a slot > ADD UCIU.)
3.
Issue 01 (2014-04-30)
Insert the UCIU and UTRPc into appropriate slots on the NodeB. Meanwhile, 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.
238
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.
5.
6.
Get ready the eNodeB configuration file and the eNodeB deployment list on the U2000.
NOTE
7.
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.
9.
BTS.
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 BTS to make the BTS
rehoming scripts take effect.
11. Wait for 10 minutes, and check that services processed on the BTS and NodeB are normal
on the U2000.
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.
Rollback
----End
7.23.4 Precautions
None
For details, see Initial Configuration on the UMTS Side in section 7.15 UTRPc-based CoTransmission Through Backplane Interconnection on the Separate-MPT UG+L/UG+T
Issue 01 (2014-04-30)

239
SingleRAN

IP rehoming scripts:
the BTS.
the GTMUb to the UTRPc.
IFNO=0;
----End

For details, see Initial Configuration on the LTE Side in section 7.15 UTRPc-based CoTransmission Through Backplane Interconnection on the Separate-MPT UG+L/UG+T
7.23.6 Rollback
Path.)
Issue 01 (2014-04-30)

240
SingleRAN
----End


7.24 Reconstruction from Main-Control-Board-PanelInterconnection Co-Transmission on the Separate-MPT UG

Multimode Base Station Side to Main-Control-BoardPanel-Interconnection Co-Transmission on the SeparateMPT UG+L/UG+T Multimode Base Station Side
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

l
Figure 7-45 shows the network topologies before and after reconstruction. After the
reconstruction, UCIU+UMPT interconnection is used.
Issue 01 (2014-04-30)

241
SingleRAN
Figure 7-45 Network topologies before and after reconstruction (UCIU+UMPT

interconnection)
Figure 7-46 shows the network topologies before and after reconstruction. After the
reconstruction, UMPT+UMPT interconnection is used.
Issue 01 (2014-04-30)

242
SingleRAN
Figure 7-46 Network topologies before and after reconstruction (UMPT+UMPT

interconnection)

Issue 01 (2014-04-30)
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB

243
SingleRAN

Figure 7-47 shows an example of reconstruction from main-control-board-based IP cotransmission through panel interconnection on the UG multimode base station side to maincontrol-board-based IP co-transmission through backplane interconnection on the UG+L
multimode base station side. After the reconstruction, UCIU+UMPT interconnection is used.
through panel interconnection on the separate-MPT UG multimode base station side to maincontrol-board-based IP co-transmission through backplane interconnection on the separate-MPT
UGL multimode base station side (UCIU+UMPT interconnection)
Issue 01 (2014-04-30)

244
SingleRAN

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

RNC
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24

BSC
21.21.21.254/24

RNC
11.11.11.254/24

NodeB
20.20.20.1/24


UMPT_U of the NodeB
20.20.20.188/24

30.30.30.1/24

of the NodeB
32.32.32.1/24

control board.
35.35.35.188/24
control board.

245
SingleRAN
Item
Instance
Remarks
eNodeB
31.31.31.188/24

of the eNodeB
33.33.33.188/24

main control board.
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
ESN of the BTS
abcdefghijklmn
NOTE
The IP address plan for IP co-transmission in UCIU+UMPT interconnection is the same as that in UMPT
+UMPT interconnection.

1.
Check the system.

interconnection.
2.

l Get ready the UCIU, optical modules, and eNodeB hardware. The main control board
for the eNodeB is UMPT_L. Optical modules on the UCIU, UMPT_U, and UMPT_L
must meet specifications. For details about the specifications of optical modules, see
"BBU Cascading" in the3900 Series Base Station Initial Configuration Guide.
3.
Back up data.
Issue 01 (2014-04-30)

246
SingleRAN
Files.)
4.

IP rehoming scripts. For details, see Reconfiguration on the GSM Side..
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.
l For details about reconfigurations on the LTE side, see Reconfiguration on the LTE
Side.
5.

l For details about rollback scripts on the UMTS side, see Rollback on the GSM Side.
l For details about rollback scripts on the GSM side, see Rollback on the UMTS Side.
l For details about rollback scripts on the LTE side, see Rollback on the LTE Side.
6.

flash drive for the reconstructed GUL multimode base station, and prepare another
commissioning USB flash drive for the GU multimode base station before the
If the multimode base station software version does not meet the reconstruction requirements,
upgrade the software before reconstruction.
1.
Run the BTS MML command ADD BTSBRD to add a UCIU. (CME: Root > Right-click
a site > Device Panel > Right-click a slot > ADD UCIU.)
2.
Issue 01 (2014-04-30)
Insert the UCIU into appropriate slots on the NodeB. Meanwhile, the UCIU software is
upgraded automatically. Run the DSP BTSBRD command to check whether the UCIU is
operating normally and of the correct version.
247
SingleRAN
DSP BTSBRD: CN=0, SRN=0, SN=0;
3.
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.
5.
Get ready the eNodeB configuration file and the eNodeB deployment list on the U2000.
NOTE
6.
file.
7.
Instruct field engineers to remove the GTMUb.
8.
BTS.
9.
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 BTS to make the BTS
rehoming scripts take effect.
10. Wait for 10 minutes, and check that services processed on the BTS and NodeB are normal
on the U2000.
11. 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 3 Verify services after reconstruction. For details, see section 7.16.6 Activation Observation
----End
l
Execute the rollback scripts. For details about the rollback scripts, see section 7.24.6
Rollback.
Restore the hardware configuration and network topology to those before reconstruction.
7.24.4 Precautions
None
For details, "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:
Issue 01 (2014-04-30)

248
SingleRAN
the BTS.
the GTMUb to the UMPT_U.
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.24.6 Rollback
Path.)
Issue 01 (2014-04-30)

249
SingleRAN
----End



Panel Interconnection on the Separate-MPT UG Multimode
Base Station Side in IP over E1/T1 Mode
l
Figure 7-48 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 BTS is interconnected to the WMPT of the NodeB through FE ports.
Figure 7-48 Main-control-board-based co-transmission through panel interconnection on
the separate-MPT UG multimode base station side in IP over E1/T1 mode

Issue 01 (2014-04-30)

250
SingleRAN


Figure 7-49 shows an example of network topology for main-control-board-based cotransmission through panel interconnection on the separate-MPT UG multimode base station
side in IP over E1/T1 mode.
Figure 7-49 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

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

RNC
11.11.11.11/32
23.23.23.1/24

BSC
21.21.21.254/24

RNC
23.23.23.254/24

251
SingleRAN
Item
Instance
Remarks

the BTS.)
30.30.30.1/24

CME

NodeB
20.20.20.188/24

CME

NodeB
20.20.20.1/24

the NodeB.)
30.30.30.188/24

CME
NOTE
segment.

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSIPRT
Forward Route
Address
NEXTHOP
Forward Route
Address
IPRT
Forward route
address
NEXTHOP
Forward route
address
Issue 01 (2014-04-30)
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
ETHPORT
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.

252
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Subboard Type
SBT
Subboard Type
Port No.
PN
Port No.
Maximum
Transmission Unit
MTU
Maximum
Transmission Unit
Speed
SPEED
Speed
Duplex
DUPLEX
Duplex
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Switch
DEVIP
IPRT
Issue 01 (2014-04-30)

253
SingleRAN
7.25.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-28 describes the panel interconnection modes.
Table 7-28 Main control board panel interconnection modes
Base Station Mode
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.

l
Using MML Commands
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 BTS to the BSC is
ADD BTSIPRT.
the destination IP address of one route to the OM channel IP address of the NodeB and that of
Issue 01 (2014-04-30)

254
SingleRAN
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 BTS is ADD IPRT.
----End
l


l
Using MML Commands
MASK="255.255.255.0";
relay.
DHCP server.
Issue 01 (2014-04-30)

255
SingleRAN
----End
l

On the CME, set the parameters listed in the Data Preparation on the UMTS Side. For

device.
UMTS Side
RNC is normal:
----End
GSM Side
----End
7.26 UTRP4-based Co-Transmission Through Panel

Station Side in IP over E1/T1 Mode
Issue 01 (2014-04-30)

256
SingleRAN

l
Figure 7-50 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 BTS is
interconnected to the WMPT of the NodeB through FE ports.
Figure 7-50 UTRP4-based co-transmission through panel interconnection on the separateMPT UG multimode base station side in IP over E1/T1 mode



Figure 7-51 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-51 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
Issue 01 (2014-04-30)

257
SingleRAN

Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

RNC
11.11.11.11/32
23.23.23.1/24

BSC
21.21.21.254/24

RNC
23.23.23.254/24

the BTS.)
30.30.30.1/24

CME
IP address of the E1 port on

the NodeB
20.20.20.188/24

CME

NodeB
20.20.20.1/24

the NodeB.)
30.30.30.188/24

CME
NOTE
segment.
Issue 01 (2014-04-30)

258
SingleRAN

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSIPRT
Forward Route
Address
NEXTHOP
Forward Route
Address
IPRT
Forward route
address
NEXTHOP
Forward route
address

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
ETHPORT
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port No.
PN
Port No.
Maximum
Transmission Unit
MTU
Maximum
Transmission Unit
Speed
SPEED
Speed
Duplex
DUPLEX
Duplex
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
DEVIP
IPRT
Issue 01 (2014-04-30)

259
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWI
TCH
DHCP Relay Switch
ES
DHCP Switch
7.26.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-30 describes the panel interconnection modes.
Base Station Mode
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.
Issue 01 (2014-04-30)

260
SingleRAN

l
Using MML Commands
Step 1 When configuring a route from the BTS to the BSC, change the next hop 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 BTS to the BSC is ADD
BTSIPRT.
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 BTS is ADD IPRT.
----End
l


l
Using MML Commands
MASK="255.255.255.0";
// Set the IP address of the Ethernet port (port 1 on board in slot 7) that is used
Issue 01 (2014-04-30)

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

relay.
DHCP server.
----End
l


device.
UMTS Side
RNC is normal:
----End
Issue 01 (2014-04-30)

262
SingleRAN
GSM Side
----End
7.27 GTMU-based TDM Co-Transmission on the SeparateMPT GU Multimode Base Station Side
l
Figure 7-52 shows the GTMU-based TDM co-transmission on the separate-MPT GU
multimode base station side. In this scenario, an outbound 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.
Figure 7-52 GTMU-based TDM co-transmission on the separate-MPT GU multimode base
station side


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-52 to the WMPT.
Issue 01 (2014-04-30)

263
SingleRAN
7.27.3 Precautions
In Figure 7-52, this scenario only supports the WMPT.

No additional hardware is required.

l
Using MML Commands
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 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 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&TS12
-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&TS12
-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
When E1 transmission resources on the BTS side are shared by the NodeB, set Port Type to
TOPEXTOUTPORT.
----End
l

On the CME, set the parameters listed in the "" section. For instructions on how to perform
the CME single configuration, see CME Single Configuration Operation Guide.
Issue 01 (2014-04-30)

264
SingleRAN

Step 1 Run the MML command ADD BACKE1T1 to add a backplane E1/T1 link.
l Set Subrack No. and Slot No. to 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.
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.28 Co-Transmission on the Co-MPT GU/GL/UL/GT/UT/

LT Multimode Base Station Side in IP over FE/GE Mode
l
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-53 shows the network topology for co-transmission on the co-MPT GU multimode
base station side.
Issue 01 (2014-04-30)

265
SingleRAN
Figure 7-53 Network topology for co-transmission on the co-MPT GU multimode base station
side in IP over FE/GE mode



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

Issue 01 (2014-04-30)

266
SingleRAN

Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

BSC
21.21.21.254/24

RNC
11.11.11.254/24

UMPT_GU
20.20.20.1/24

UMPT_GU
20.20.20.188/24
Device IP address during

configuration on the CME.
OM IP address
30.30.30.1/32
GSM: management plane 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.
Issue 01 (2014-04-30)
of the NodeB
32.32.32.1/24

configured on the
UMPT_GU.

RNC
15.15.15.15/24
11.11.11.11/24
60.60.60.60/24
GSM: peer IP address for the

OM channel
of the BTS
35.35.35.188/24
GSM: control plane/user

configured on the
UMPT_GU.

267
SingleRAN
Item
Instance
Remarks
ESN
abcdefghijklmn
Data Preparation
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
ETHPORT
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port No.
PN
Port No.
Maximum
Transmission Unit
MTU
Maximum
Transmission Unit
Speed
SPEED
Speed
Duplex
DUPLEX
Duplex
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
DEVIP
IPRT
Issue 01 (2014-04-30)

268
SingleRAN
MO
VLANMAP
VLANCLASS
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
7.28.3 Precautions
None


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.
l
Using MML Commands
Step 1 Run the ADD DEVIP command to add the IP address of the NodeB.
Issue 01 (2014-04-30)

269
SingleRAN

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 BTS.
MASK="255.255.255.0";
//Add the signaling/service IP address of the BTS.
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.
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 20.20.20.101, which is different from the next-hop address (20.20.20.1) of the uplink
route from the multimode base station to the RNC. Run the ADD VLANMAP command to
add VLAN mapping.
differentiated DSCP values for the BTS and NodeB. For details about DSCP values for the
BTS and NodeB, see Bandwidth Sharing of Multimode Base Station Co-Transmission
1.
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;
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 ADD VLANMAP command.

----End
l
Issue 01 (2014-04-30)

270
SingleRAN
On the CME, set the parameters listed in the Data Preparation section. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.

device.
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:
Step 1 Run the PING command to ping the IP address of the RNC. If the IP address can be pinged, the
transmission link is normal.
Step 2 Run the PING command to ping the IP address of the BSC.
----End
NOTE
In this scenario, the GU multimode base station is configured with only one UMPT_GU. As a result, the
activation observation is for multimode base station as a whole instead of for the UMTS and GSM sides
separately.
7.29 Co-Transmission on the Co-MPT GUL/GUT/GLT/ULT/

GULT Multimode Base Station Side in IP over FE/GE Mode
l
The UMPT_GUL of a multimode base station provides an FE/GE port as the cotransmission port to connect the base station to the MBSC, MME, and S-GW. Figure
7-55 shows the network topology for co-transmission on the co-MPT GUL multimode base
station side.
Issue 01 (2014-04-30)

271
SingleRAN
Figure 7-55 Network topology for co-transmission on the co-MPT GUL multimode base
station side in IP over FE/GE mode



Figure 7-56 shows an example of network topology for co-transmission on the co-MPT GUL
Issue 01 (2014-04-30)

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

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

BSC
21.21.21.254/24

RNC
11.11.11.254/24
P address of the port on the

UMPT_GUL
20.20.20.1/24

UMPT_GUL
20.20.20.188/24


273
SingleRAN
Item
Instance
Remarks
OM IP address
30.30.30.1/24
GSM: Management plane IP

the UMPT_GUL.
NOTE
because the multimode base
station is configured with one
OM channel.
Issue 01 (2014-04-30)
of the NodeB
32.32.32.1/24

configured on the
UMPT_GUL.

RNC
15.15.15.15/24
11.11.11.11/24
60.60.60.60/24
GSM: Peer IP address for the

OM channel
of the BTS
35.35.35.188/24

configured on the
UMPT_GUL.
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
of the eNodeB
33.33.33.188/24

configured on the
UMPT_GUL.
ESN
abcdefghijklmn

274
SingleRAN
Data Preparation
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
ETHPORT
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port No.
PN
Port No.
Maximum
Transmission Unit
MTU
Maximum
Transmission Unit
Speed
SPEED
Speed
Duplex
DUPLEX
Duplex
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DEVIP
IPRT
Issue 01 (2014-04-30)

275
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
VLANMAP
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLANCLASS
7.29.3 Precautions
None


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.
l
Using MML Commands
MASK="255.255.255.0";
Step 2 Run the ADD DEVIP command to add the IP address of the BTS.
Issue 01 (2014-04-30)

276
SingleRAN

MASK="255.255.255.0";
//Add the signaling/service IP address of the BTS.
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
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 each other.
For example, you can set the next-hop address of the uplink route from the multimode base
station to the BSC to 20.20.20.101, which is different from the next-hop address (20.20.20.1)
of the uplink route from the multimode base station to the RNC and the next-hop IP address
(20.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.
ADD VLANMAP: NEXTHOPIP="20.20.20.1", MASK=255.255.255.255, VLANMODE=SINGLEVLAN,
VLANID=20, SETPRIO=DISABLE;
for the BTS, NodeB and eNodeB, see Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description.
1.

Issue 01 (2014-04-30)

277
SingleRAN

In addition, set TRAFFIC to USERDATA
2.

----End

device.
between the multimode base station and the base station controller is normal:
Step 1 Run the PING command to ping the IP address of the RNC. If the IP address can be pinged, the
transmission link is normal.
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.
Step 4 Run the PING command to ping the IP address of the SGW.
----End
NOTE
In this scenario, the GUL multimode base station is configured with only one UMPT_GUL. As a result,
the activation observation is for multimode base station as a whole instead of for the GSM, UMTS, and
LTE sides separately.
7.30 Co-Transmission on the Hybrid-MPT GUL Multimode

Issue 01 (2014-04-30)

278
SingleRAN

l
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-57 shows the network topology
for co-transmission on the hybrid-MPT GUL multimode base station side.
Figure 7-57 Network topology for co-transmission on the hybrid-MPT GUL multimode base
station side in IP over FE/GE mode



Figure 7-58 shows an example of network topology for co-transmission on the hybrid-MPT
GUL multimode base station side.
Issue 01 (2014-04-30)

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

Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24

BSC
21.21.21.254/24

RNC
11.11.11.254/24

UMPT_UL
20.20.20.1/24

UMPT_UL
20.20.20.188/24


280
SingleRAN
Item
Instance
Remarks
OM IP address
30.30.30.1/24
UMTS&LTE: Management
configured on the
UMPT_UL.
NOTE
because the co-MPT UL
multimode base station is
configured with one OM
channel.
Issue 01 (2014-04-30)
of the NodeB
32.32.32.1/24

configured on the
UMPT_UL.

RNC
15.15.15.15/24
11.11.11.11/24
60.60.60.60/24
UMTS&LTE: Peer IP
address for the OM channel
of the BTS
35.35.35.188/24

configured on the
UMPT_UL.
40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
of the eNodeB
33.33.33.188/24

configured on the
UMPT_UL.
ESN
abcdefghijklmn

281
SingleRAN
Data Preparation on the GBTS Side

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSTUNNEL
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Source Cabinet No.
SRCCN
Source Cabinet No.
Source Subrack No.
SRCSRN
Source Subrack No.
Source Slot No.
SRCSN
Source Slot No.
BTS Tunnel No.
TN
BTS Tunnel No.
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
DSTSN
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
Port No.
PN
Port No.
Port Cabinet No.
CN
Port Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
BTS
Communication
Type
BTSCOMTYPE
BTS
Communication
Type
BTS IP
BTSIP
BTS IP
BSC IP
BSCIP
BSC IP
BTS MultiIP Switch
BTSMUTIP
BTS MultiIP Switch
BTSDEVIP
BTSIP
Issue 01 (2014-04-30)

282
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSIPRT
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Route Index
RTIDX
Route Index
Destination IP
Address
DSTIP
Destination IP
Address
Destination Address
Mask
DSTMASK
Destination Address
Mask
Route Type
RTTYPE
Route Type
Port Cabinet No.
CN
Port Cabinet No.
Port Subrack No.
SRN
Port Subrack No.
Port Slot No.
SN
Port Slot No.
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
BTS Index Type
IDTYPE
BTS Index
BTSID
BTS Index
OM Bear Board
OMBEARBOARD
OM Bear Board
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Destination IP
address
DSTIP
Destination IP
address
Destination address
mask
DSTMASK
Destination address
mask
Forward route
address
NEXTHOP
Forward route
address
BTSESN
IPRT
Data Preparation on the Co-MPT UL Multimode Base Station Side
Issue 01 (2014-04-30)
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
Source Cabinet No.
SCN
Source Cabinet No.

283
SingleRAN
MO
DEVIP
IPRT
DHCPSVRIP
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Source Subrack
No.
SSRN
Source Subrack
No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination
Cabinet No.
DCN
Destination
Cabinet No.
Destination
Subrack No.
DSRN
Destination
Subrack No.
Destination Slot
No.
DSN
Destination Slot
No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.
IP Address
IP
IP Address
Mask
MASK
Mask
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address

284
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
DHCPRELAYSWITC
H
DHCP Relay
Switch
ES
DHCP Switch
VLANMAP
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLANCLASS
7.30.3 Precautions
None


Initial Configuration on the GBTS Side
l
Using MML Commands
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.
Issue 01 (2014-04-30)

285
SingleRAN
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.
NEXTHOP="21.21.21.254", PRIORITY=HIGH, REMARK="relay";
Step 3 Run the MML command ADD BTSDEVIP to add the IP address of the GTMUb.
IP="35.35.35.188", MASK="255.255.255.0";
Step 4 Run the MML command SET BTSIP to set the communication IP address of the GBTS.
Unlike non-co-transmission scenarios, this scenario requires that the GBTS uses the logical IP
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
l

On the CME, set the parameters listed in the Data Preparation on the GBTS Side. For
Initial Configuration on the Co-MPT UL Multimode Base Station Side

l
Using MML Commands
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";
Issue 01 (2014-04-30)

286
SingleRAN
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.
//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 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 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 through the
co-MPT UL multimode base station.
When co-transmission for the GBTS and co-MPT UL multimode base station is implemented
through tunnels on the backplane, the downlink route from the BSC to the GBTS 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="35.35.35.188",
//Add a downlink route from the BSC to the GBTS through the NodeB on the UMPT_UL in
slot 7.
Step 8 Run the MML command SET DHCPRELAYSWITCH to enable DHCP relay.
If the GBTS 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 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. If the data plan shows that the IP-based Abis interface board on the BSC side uses the
Issue 01 (2014-04-30)

287
SingleRAN

//Add the IP address of the DHCP server for the GBTS.
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 20.20.20.101, which is different from the next-hop address (20.20.20.1)
of the uplink route from the multimode base station to the RNC and the next-hop IP address
(20.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.
ADD VLANMAP: NEXTHOPIP="20.20.20.1", MASK=255.255.255.255, VLANMODE=SINGLEVLAN,
VLANID=20, SETPRIO=DISABLE;
for the BTS, NodeB and eNodeB, see Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description.
1.

// Set VLANID to 22 for the data flow with SRVPRIO set to 0. The DSCP value in
2.

----End
l

On the CME, set the parameters listed in the "Data Preparation on the Co-MPT UL
Multimode Base Station Side" section. For instructions on how to perform the CME single
configuration, see CME Single Configuration Operation Guide.

device.
Issue 01 (2014-04-30)

288
SingleRAN
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.
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 SGW.
----End
7.31 Main-control-board -based Co-Transmission Through

Backplane Interconnection on the Separate-MPT LGU/TGU
l
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/SGW. 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.
Issue 01 (2014-04-30)

289
SingleRAN

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-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.
Issue 01 (2014-04-30)

290
SingleRAN

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

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.
Issue 01 (2014-04-30)

291
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-61. The engineering guidelines for the scenario shown in Figure 7-61 is similar to those for
the scenario shown in Figure 7-59.
l


Issue 01 (2014-04-30)
NE
License Control
Item
Abbreviation
Code
Sales Unit
eNodeB
IP-Based Multimode CoTransmission on

BS side(eNodeB)
LLT1IPMCT01
81201528
Per eNodeB

292
SingleRAN

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

Issue 01 (2014-04-30)
Item
IP Address
Remarks
10.10.10.10/32
21.21.21.1/24

RNC
15.15.15.15/32
11.11.11.11/24

RNC
11.11.11.254/24

293
SingleRAN
Issue 01 (2014-04-30)
Item
IP Address
Remarks

BSC
21.21.21.254/24

UMPT_L
20.20.20.1/24
30.30.30.1/24

control board.
of the NodeB
32.32.32.1/24

control board.

UMPT_L of the eNodeB
20.20.20.188/24

40.40.40.40/24

SCTP link
50.50.50.50/24

IP path
60.60.60.60/24

for the OM channel
eNodeB
31.31.31.188/24

of the eNodeB
33.33.33.188/24

control board.
35.35.35.188/24
control board.
BTS ESN
abcdefghijklmn

294
SingleRAN
NOTE
In this scenario, the GTMUb and WMPT do not need to be configured with Ethernet port attributes such
as duplex mode and rate because the GTMUb and WMPT communicate with the UMPT_L through the

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSBRD
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Board Type
BT
Board Type
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
Link No.
LN
Link No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Upper Node Cabinet

No.
UPCN
Upper Node Cabinet

No.
Upper Node Subrack

No.
UPSRN
Upper Node Subrack

No.
Upper Node Slot No.
UPSN
Upper Node Slot No.
Upper Node Port No.
UPPT
Upper Node Port No.
BTS Index Type
IDTYPE
BTS Index Type
BTS Index
BTSID
BTS Index
Source Cabinet No.
SRCCN
Source Cabinet No.
Source Subrack No.
SRCSRN
Source Subrack No.
Source Slot No.
SRCSN
Source Slot No.
BTSCTRLLNK
BTSTUNNEL
Issue 01 (2014-04-30)

295
SingleRAN
MO
BTSDEVIP
BTSIP
BTSIPRT
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTS Tunnel No.
TN
BTS Tunnel No.
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
DSTSN
BTS Index Type
IDTYPE
BTS Index Type
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
Port No.
PN
Port No.
Port Cabinet No.
CN
Port Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
BTS Index Type
IDTYPE
BTS Index Type
BTS Index
BTSID
BTS Index
BTS Name
BTSNAME
BTS Name
BTS
Communication
Type
BTSCOMTYPE
BTS
Communication
Type
BTS IP
BTSIP
BTS IP
BSC IP
BSCIP
BSC IP
BTS MultiIP Switch
BTSMUTIP
BTS MultiIP Switch
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Route Index
RTIDX
Route Index
Destination IP
Address
DSTIP
Destination IP
Address
Destination Address
Mask
DSTMASK
Destination Address
Mask

296
SingleRAN
MO
BTSESN
IPRT
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Route Type
RTTYPE
Route Type
Port Cabinet No.
CN
Port Cabinet No.
Port Subrack No.
SRN
Port Subrack No.
Port Slot No.
SN
Port Slot No.
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
BTS Index Type
IDTYPE
BTS Index
BTSID
BTS Index
OM Bear Board
OMBEARBOARD
OM Bear Board
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Destination IP
address
DSTIP
Destination IP
address
Destination address
mask
DSTMASK
Destination address
mask
Forward route
address
NEXTHOP
Forward route
address
Issue 01 (2014-04-30)
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CTRLLNK
Local Link No.
LN
Local Link No.
Local Cabinet No.
CN
Local Cabinet No.
Local Subrack No.
SRN
Local Subrack No.
Local Slot No.
SN
Local Slot No.
Upper Cabinet No.
UPCN
Upper Cabinet No.
Upper Subrack No.
UPSRN
Upper Subrack No.
Upper Slot No.
UPSN
Upper Slot No.
Upper Port No.
UPPT
Upper Port No.

297
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
Source Cabinet No.
SCN
Source Cabinet No.
Source Subrack No.
SSRN
Source Subrack No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination Cabinet
No.
Destination Subrack
No.
DSRN
Destination Subrack
No.
DSN
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Port Type
IFT
Carrier Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Link No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Transmission
Resource Group
Bear Type
BEAR
Subboard Type
SBT
Subboard Type
Bearing Port Type
PT
Carrier Type
Bearing Port No.
PN
Link No.
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
IPRT
RSCGRP
Issue 01 (2014-04-30)

298
SingleRAN
MO
IPPath
OMCH
Issue 01 (2014-04-30)
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Rate Unit
RU
Rate Unit
Tx Bandwidth
TXBW
Tx Bandwidth
Rx Bandwidth
RXBW
Rx Bandwidth
IP Path ID
PATHID
IP Path ID
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Carrier Type
Port No.
PN
Link No.
Join Transmission
Resource Group
JNRSCGRP
Join Transmission
Resource Group
Local IP
LOCALIP
Local IP
Peer IP
PEERIP
Peer IP
DSCP
DSCP
DSCP
RX Bandwidth
RXBW
RX Bandwidth
TX Bandwidth
TXBW
TX Bandwidth
TX Committed Burst
Size
TXCBS
TX Committed Burst
Size
TX Excessive Burst
Size
TXEBS
TX Excessive Burst
Size
Local IP
IP
Local IP
Local Mask
MASK
Local Mask
Peer IP
PEERIP
Peer IP
Peer Mask
PEERMASK
Peer Mask
Bearer Type
BEAR
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type

299
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Binding Route
BRT
Binding Route

MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CTRLLNK
Local Link No.
LN
Local Link No.
Local Cabinet No.
CN
Local Cabinet No.
Local Subrack No.
SRN
Local Subrack No.
Local Slot No.
SN
Local Slot No.
Upper Cabinet No.
UPCN
Upper Cabinet No.
Upper Subrack No.
UPSRN
Upper Subrack No.
Upper Slot No.
UPSN
Upper Slot No.
Upper Port No.
UPPT
Upper Port No.
Source Cabinet No.
SCN
Source Cabinet No.
TUNNEL
DEVIP
Issue 01 (2014-04-30)
Source Subrack No. SSRN
Source Subrack
No.
Source Slot No.
SSN
Source Slot No.
Tunnel No.
TUNNELID
Tunnel No.
Destination Cabinet
No.
DCN
Destination
Cabinet No.
Destination
Subrack No.
DSRN
Destination
Subrack No.
DSN
Destination Slot
No.
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Port Type
PT
Port Type
Port No.
PN
Port No.

300
SingleRAN
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
IP Address
IP
IP Address
Mask
MASK
Mask
Route Index
VRFIDX
Route Index
Cabinet No.
CN
Cabinet No.
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
Subboard Type
SBT
Subboard Type
Destination IP
DSTIP
Destination IP
Mask
DSTMASK
Mask
Route Type
RTTYPE
Route Type
Port Type
IFT
Port Type
Next Hop IP
NEXTHOP
Next Hop IP
Port No.
IFNO
Port No.
DHCPSVRIP
DHCP Server IP
Address
DHCPSVRIP
DHCP Server IP
Address
DHCPRELAYSWITC
H
DHCP Relay
Switch
ES
DHCP Relay
Switch
VLANMAP
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN Priority
SETPRIO
Set VLAN Priority
VLAN Priority
VLANPRIO
VLAN Priority
VLAN Group No.
VLANGROUPNO
VLAN Group No.
VLAN Group No.
VLANGROUPNO
VLAN Group No.
Traffic Type
TRAFFIC
Traffic Type
User Data Service

Priority
SRVPRIO
User Data Service

Priority
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
IPRT
VLANCLASS
Issue 01 (2014-04-30)

301
SingleRAN
7.31.3 Precautions
None

l
Unlike non-co-transmission scenario, this scenario requires that the UMPT_L be

configured on the eNodeB side. In addition, the UCIU must be configured on the BTS side.
The UCIU in the BBU accommodating the NodeB and BTS is connected to the UMPT_L
in the BBU accommodating the eNodeB by using inter-subrack interconnection cables.
A cable is used to connect the UMPT_L on the separate-MPT LGU multimode base station
side to the transport network.

(Optional) Initial Configuration on the U2000 Side

For details about the data configurations at the data link layer and network layer, see
"Configuring a BTS" > "Configuring the Transmission Data" in the 3900 Series Base Stations
Initial Configuration.
l
Using MML Commands

NOTE
In addition to configuration steps described in the 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)ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=10, LN=0, CN=0,
subrack 0.
(UMPT+UMPT interconnection) ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=10, LN=0, CN=0,
subrack 0.
UMPT_L.
DSTSRN=1, DSTSN=7;
Issue 01 (2014-04-30)

302
SingleRAN
//Add a tunnel from the GTMUb in slot 6 of BBU subrack 0 to the UMPT_L in slot 7 of
BBU subrack 1.
NOTE
According to the co-transmission networking plan, modify the parameters in the following steps described
in the 3900 Series Base Stations Initial Configuration.
IP="35.35.35.188", MASK="255.255.255.0";
Unlike non-co-transmission scenarios, this scenario requires that the BTS use the logical IP
BTSCOMTYPE to an appropriate value based on the actual situations.
IFNO=0;
Step 8 (Optional) Run the BSC MML command ADD IPRT to add a route to the DHCP relay of the
BTS. In this step, set DSTIP to the OM channel IP address of the eNodeB. Run this command
again to add another route and set DSTIP to the lower-level transmission port of the eNodeB.
----End
l

On the CME, set the parameters listed in the "Data Preparation on the GSM Side" section.

Base Stations Initial Configuration.
Issue 01 (2014-04-30)

303
SingleRAN
Using MML Commands

NOTE
In addition to the configuration steps described in the 3900 Series Base Stations Initial Configuration,
perform the following steps for co-transmission.
Step 1 Run the NodeB MML command ADD CTRLLNK to add a control link between BBUs.
(UCIU+UMPT interconnection) ADD CTRLLNK: LN=0, CN=0, SRN=1, SN=7, UPCN=0, UPSRN=0,
UPSN=0, UPPT=0;
//Add a control link from the board in slot 7 of BBU subrack 1 to the board in slot
0 of BBU subrack 0.
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.
NOTE
According to the co-transmission networking plan, modify the parameters in the following steps described
in the 3900 Series Base Stations Initial Configuration.
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";
Step 4 Run the NodeB MML command ADD IPRT to add a route from the NodeB to the RNC/U2000.
//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=IPV4, SBT=BACK_BOARD, PT=TUNNEL, RSCGRPID=0, RU=KBPS,
TXBW=4000, RXBW=4000;
//When adding a transmission resource group set SBT to BACK_BOARD and PT 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="32.32.32.1", PEERIP="15.15.15.15", DSCP=22, RXBW=1000, TXBW=1000,
TXCBS=15000, TXEBS=2000, FPMUXSWITCH=DISABLE;
Issue 01 (2014-04-30)

304
SingleRAN
Step 7 Run the NodeB MML command ADD OMCH to add an O&M channel.
PEERMASK="255.255.255.0", BEAR=IPV4, SN=7, SBT=BACK_BOARD, BRT=NO;
//When adding an O&M channel, set SBT to BACK_BOARD.
----End
l

On the CME, set the parameters listed in the "Data Preparation on the UMTS Side" section.
Initial Configuration on the eNodeB Side

For details about data configurations at the data link layer and transport layer, see the 3900 Series
Base Stations Initial Configuration.
l
Using MML Commands

NOTE
In addition to configuration steps described in the 3900 Series Base Stations Initial Configuration 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)ADD CTRLLNK: LN=0, CN=0, SRN=1, SN=7, UPCN=0, UPSRN=0,
UPSN=0, UPPT=0;
//Add a control link from the UMPT_L in slot 7 of subrack 1 to the UCIU in slot 0
of subrack 0.
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.
MASK="255.255.255.0";
//Add a signaling/service IP address for the UMPT_L in slot 7.
MASK="255.255.255.0";
/Add an IP address for Ethernet port 1 on the UMPT_L in slot 7.
RNC/U2000 through the eNodeB, and an uplink route from the BTS 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.
Issue 01 (2014-04-30)

305
SingleRAN
ADD IPRT: RTIDX=0, CN=0, SRN=1, SN=7, SBT= BASE_BOARD, DSTIP="15.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="60.60.60.60",
//Add a route from the NodeB to the RNC through the eNodeB.
ADD IPRT: RTIDX=2, CN=0, SRN=1, SBT=BASE_BOARD, DSTIP="10.10.10.10",
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 BSC to the BTS through the
eNodeB.
UMPT_U backplane, the downlink route from the BSC to the BTS through the NodeB and the
downlink route from the /U2000 must be configured on the NodeB. In addition, SBT must be
set to BACK_BOARD and IFT 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, SBT=BACK_BOARD, DSTIP="35.35.35.188",
//Add a downlink route from the BSC to the BTS through the eNodeB.
Step 6 (Optional) Run the eNodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
When co-transmission is enabled for the BTS, NodeB and eNodeB, the eNodeB needs to work
as the relay if the BTS and NodeB are deployed using DHCP. Therefore, DHCP relay needs to
be enabled for the eNodeB.
Step 7 (Optional) Run the eNodeB MML command ADD DHCPSVRIP to add the IP address of the
DHCP server.
When co-transmission is enabled for the BTS, NodeB and eNodeB, the eNodeB needs to work
as the relay if the BTS, NodeB is deployed using DHCP. Therefore, the IP address of the DHCP
server needs to be added on the eNodeB. For the BTS, the BSC works as the DHCP server. If
the DHCP server is shared by the NodeB and eNodeB, the IP address of the DHCP server is the
IP address of the U2000.
// Add the IP address of the DHCP server for the GBTS.
uplink route from the BTS to the BSC through the eNodeB and the uplink route from the
Issue 01 (2014-04-30)

306
SingleRAN
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 BTS to the BSC through the NodeB to 20.20.20.101, and set the next-hop address of the
uplink route from the NodeB to the RNC through the eNodeB to 20.20.20.201, which is
different from the next-hop address (20.20.20.1) of the uplink route for the eNodeB. To add
VLAN mapping, run the MML command ADD VLANMAP.
for the BTS, NodeB, and eNodeB, see the Bandwidth Sharing of Multimode Base Station
Co-Transmission Feature Parameter Description.
1.

mode, set TRAFFIC to USERDATA for all passerby flows through the eNodeB. If
differentiated data needs to be configured for the eNodeB and BTS and
ADD VLANCLASS: VLANGROUPNO=1, TRAFFIC=USERDATA, SRVPRIO=26 VLANID=32;
mode, set TRAFFIC to USERDATA for all passerby flows through the NodeB. If
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.

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

On the CME, set the parameters listed in the "Data Preparation on the LTE Side" section.

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
Issue 01 (2014-04-30)

307
SingleRAN

----End
UMTS Side
on the NodeB side to check whether the transmission link between the NodeB and the RNC is
normal:
----End
GSM Side
the BSC side to check whether the transmission link between the BSC and the BTS is normal:
----End
7.32 Performance Monitoring

None
7.32.2 IP Co-Transmission on the Multimode Base Station Side

None
7.33 Parameter Optimization

None

None
Issue 01 (2014-04-30)

308
SingleRAN
7.34 Troubleshooting
None

An alarm will be reported on the eNodeB, BTS, or NodeB side if a fault exists.
The following alarms may be reported on the eNodeB side:
l
ALM-25860 PPP/MLPPP Link Fault
ALM-25861 MLPPP Group Fault
ALM-25862 MLPPP Group Excessive Packet Loss Rate
ALM-25863 PPP Link Excessive Frame Error Rate
ALM-25880 Ethernet Link Fault
ALM-25881 MAC Excessive Frame Error Rate
ALM-25885 IP Address Conflict
ALM-25888 SCTP Link Fault
ALM-25886 IP Path Fault
ALM-29201 S1 Interface Fault
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
ALM-25835 NCP Fault/ALM-2010 NCP Faulty Alarm
ALM-25836 CCP Fault/RNC: ALM-2011 CCP Faulty Alarm
ALM-28203 Local Cell Unusable/ALM-2006 Cell Unavailable Alarm
The following alarms may be reported on the BTS side:

l
Issue 01 (2014-04-30)

309
SingleRAN
ALM-28006 Radio Signaling Link Disconnected
ALM-21512 LAPD Link Fault
ALM-21805 ESL Link Fault
ALM-21801 GSM Cell out of Service
If any of preceding alarm is reported on the transmission port on the eNodeB, BTS, or NodeB
side, handle the alarm according to the alarm reference.
Issue 01 (2014-04-30)

310
SingleRAN
8 Parameters
Parameters
Table 8-1 Parameter description

Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
CN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
ETHPO
RT
None
None
Meaning: Indicates the cabinet number of the board

where the Ethernet port is located.
GUI Value Range: 0~7
DSP
ETHPO
RT
Unit: None
RMV
ETHPO
RT
Default Value: 0
Actual Value Range: 0~7
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
Issue 01 (2014-04-30)

311
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SRN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
ETHPO
RT
None
None
Meaning: Indicates the subrack number of the board

DSP
ETHPO
RT
Unit: None
RMV
ETHPO
RT
Default Value: 0
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
SN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
ETHPO
RT
None
None
Meaning: Indicates the slot number of the board where

the Ethernet port is located.
DSP
ETHPO
RT
Unit: None
RMV
ETHPO
RT
Default Value: None
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
Issue 01 (2014-04-30)

312
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SBT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
ETHPO
RT
None
None
Meaning: Indicates the type of sub-board on the board

GUI Value Range: BASE_BOARD(Base Board),
ETH_COVERBOARD(Ethernet Cover Board)
DSP
ETHPO
RT
Unit: None
Actual Value Range: BASE_BOARD,
ETH_COVERBOARD
RMV
ETHPO
RT
Default Value: None
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
PN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
ETHPO
RT
DSP
ETHPO
RT
None
None
Meaning: Indicates the number of the Ethernet port.

Unit: None
Default Value: None
RMV
ETHPO
RT
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
Issue 01 (2014-04-30)

313
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
MTU
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
ETHPO
RT
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the maximum IP packet size

(including the IP header) at the Ethernet port. For the
UMPT, LMPT, and UTRPc, the value of this parameter
ranges from 46 to 1800. For the WMPT, UQEC, and
UEOC, the value of this parameter ranges from 46 to
1500. If this parameter is set to a value greater than the
maximum allowed value, the maximum allowed value
takes effect. A value greater than or equal to 776 is
recommended, because broadcast packets, such as
DHCP packets, may experience reception or
transmission failures if the maximum transmission unit
is smaller than 776. If the Ethernet port is added to an
Ethernet trunk, this parameter becomes invalid. The
actual maximum transmission unit depends on the value
set for the Ethernet trunk.
SET
ETHPO
RT
DSP
ETHPO
RT
LST
ETHPO
RT

Unit: byte
Default Value: 1500
SPEED
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
ETHPO
RT
SET
ETHPO
RT
DSP
DHCPR
SLT
LST
ETHPO
RT
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the speed mode of the Ethernet port.

This parameter must be set to the same value as that of
the peer port. GE electrical ports of base board support
1000 Mbit/s only when working in auto-negotiation
mode. If SPEED of a GE optical port is set to AUTO,
the port works at 1000 Mbit/s in auto-negotiation mode.
If SPEED of a GE optical port is set to 1000M, the port
works at 1000 Mbit/s in manual configuration mode.
GUI Value Range: 10M(10M), 100M(100M), 1000M
(1000M), AUTO(Automatic Negotiation)
Unit: None
Actual Value Range: 10M, 100M, 1000M, AUTO
Default Value: AUTO(Automatic Negotiation)
Issue 01 (2014-04-30)

314
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DUPLE
X
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
ETHPO
RT
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the duplex mode of the Ethernet

port.
SET
ETHPO
RT
DSP
DHCPR
SLT
GUI Value Range: FULL(Full Duplex), AUTO

(Automatic Negotiation)
Unit: None
Actual Value Range: FULL, AUTO
Default Value: FULL(Full Duplex)
LST
ETHPO
RT
CN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
DEVIP
None
None

where the port is located.
DSP
DEVIP
MOD
DEVIP
Unit: None
Default Value: 0
RMV
DEVIP
LST
DEVIP
SRN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
DEVIP
None
None

where the port is located.
DSP
DEVIP
MOD
DEVIP
RMV
DEVIP
Unit: None
Default Value: 0
LST
DEVIP
Issue 01 (2014-04-30)

315
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
DEVIP
None
None

the port is located.
DSP
DEVIP
MOD
DEVIP
Unit: None
Default Value: None
RMV
DEVIP
LST
DEVIP
SBT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
DEVIP
None
None
MOD
DEVIP

where a port is located.
E1_COVERBOARD(E1 Cover Board),
BACK_BOARD(Back Board), ETH_COVERBOARD
(Ethernet Cover Board)
RMV
DEVIP
Unit: None
DSP
DEVIP

E1_COVERBOARD, BACK_BOARD,
ETH_COVERBOARD
LST
DEVIP
Default Value: None

PT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
DEVIP
MOD
DEVIP
RMV
DEVIP
DSP
DEVIP
LST
DEVIP
Issue 01 (2014-04-30)
None
None
Meaning: Indicates the type of the physical port. The

UMTS currently does not support SUBIF.
GUI Value Range: PPP(PPP Link), MPGRP(Multi-link
PPP Group), ETH(Ethernet Port), ETHTRK(Ethernet
Trunk), LOOPINT(Loopback Interface), SUBIF(Subinterface)
Unit: None
Actual Value Range: PPP, MPGRP, ETH, ETHTRK,
LOOPINT, SUBIF
Default Value: None

316
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
PN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
DEVIP
None
None
Meaning: Indicates the number of a port.

MOD
DEVIP
Unit: None
RMV
DEVIP
Default Value: None
DSP
DEVIP
LST
DEVIP
IP
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
DEVIP
WRFD050402
MOD
DEVIP
WRFD050411
RMV
DEVIP
DSP
DEVIP
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the IP address configured for the

port.
GUI Value Range: Valid IP address
Unit: None
Actual Value Range: Valid IP address
Default Value: None
Fraction
al IP
Function
on Iub
Interface
DSP
MULTI
CASTIP
LST
DEVIP
MASK
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
Issue 01 (2014-04-30)
ADD
DEVIP
WRFD050402
DSP
DEVIP
WRFD050411
LST
DEVIP
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the subnet mask of the device IP

address configured on the port.
GUI Value Range: Valid Mask address
Unit: None
Actual Value Range: Valid Mask address
Default Value: None
Fraction
al IP
Function
on Iub
Interface

317
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
VRFID
X
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
None
None
Meaning: Indicates the index of a VRF instance. The

UMTS currently supports default routes domain only
(VRF index is 0).
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
CN
SRN
SN
Issue 01 (2014-04-30)
MOD
IPRT
DSP
IPRT
Unit: None
LST
IPRT
Default Value: 0
None
None

where the IP route is located.
DSP
IPRT
MOD
IPRT
Unit: None
Default Value: 0
LST
IPRT
None
None

where the IP route is located.
DSP
IPRT
MOD
IPRT
Unit: None
Default Value: 0
LST
IPRT
None
None

the IP route is located.
DSP
IPRT
MOD
IPRT
LST
IPRT
Unit: None
Default Value: None

318
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SBT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
None
None

where the IP route is established.
MOD
IPRT

UNCHANNELLED_COVERBOARD(Unchannelled
Cover Board), E1_COVERBOARD(E1 Cover Board),
LST
IPRT
Unit: None
UNCHANNELLED_COVERBOARD,
ETH_COVERBOARD
Default Value: None
DSTIP
DSTMA
SK
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
WRFD050402
MOD
IPRT
WRFD050107
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
WRFD050402
MOD
IPRT
WRFD050107
Issue 01 (2014-04-30)
DSP
IPRT
LST
IPRT
DSP
IPRT
LST
IPRT
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the destination IP address of the

route.
Unit: None
Default Value: None
IP
routing
Based
Hub
Node B
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the subnet mask for the destination

IP address of the route.
Unit: None
Default Value: None
IP
routing
Based
Hub
Node B

319
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
RTTYP
E
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
WRFD050402
MOD
IPRT
WRFD050107
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the type of route. If this parameter

is set to NEXTHOP, all the IP packets that meet the
route direction are first forwarded to the specified next
hop IP address. If this parameter is set to IF, all the IP
packets that meet the route direction are first forwarded
to the specified egress port.
IFT
DHCPS
VRIP
DSP
IPRT
LST
IPRT
IP
routing
Based
Hub
Node B
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
WRFD050402
MOD
IPRT
WRFD050107
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
DHCPS
VRIP
Issue 01 (2014-04-30)
LST
IPRT
RMV
DHCPS
VRIP
WRFD031101
GUI Value Range: NEXTHOP(Next Hop), IF(Exit

Interface)
Unit: None
Actual Value Range: NEXTHOP, IF
Default Value: None
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the type of port.
IP
routing
Based
Hub
Node B
Default Value: PPP(PPP Link)
NodeB
Selfdiscover
y Based
on IP
Mode
Meaning: Indicates the IP address of the DHCP server.

PPP Group), TUNNEL(Tunnel), IPOA(IP Over ATM
Interface)
Unit: None
Actual Value Range: PPP, MPGRP, TUNNEL, IPOA

Unit: None
Default Value: None
LST
DHCPS
VRIP

320
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
ES
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
SET
DHCPR
ELAYS
WITCH
MRFD221501
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
Meaning: Indicates whether to enable the DHCP relay

switch.
WRFD031101
LST
DHCPR
ELAYS
WITCH
GUI Value Range: DISABLE(Disable), ENABLE

(Enable)
Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: DISABLE(Disable)
NodeB
Selfdiscover
y Based
on IP
Mode
VLANG
ROUPN
O
NEXTH
OPIP
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
VLAN
MAP
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
VLAN
MAP
WRFD050402
MOD
VLAN
MAP
LST
VLAN
MAP
MOD
VLAN
MAP
RMV
VLAN
MAP
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the VLAN group number.
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the next hop IP address used for

mapping the VLAN.

Unit: None
Default Value: 0

Unit: None
Default Value: None
LST
VLAN
MAP
Issue 01 (2014-04-30)

321
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
MASK
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
VLAN
MAP
LBFD-0
03003 /
TDLBF
D-00300
3
VLAN
Support
(IEEE
802.1p/
q)
Meaning: Indicates the subnet mask of the next hop IP

address used for mapping the VLAN.
MOD
VLAN
MAP

Unit: None
Default Value: 255.255.255.255
RMV
VLAN
MAP
LST
VLAN
MAP
VLAN
MODE
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
VLAN
MAP
WRFD050402
MOD
VLAN
MAP
LST
VLAN
MAP
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the VLAN mode. When this

parameter is set to SINGLEVLAN, the configured
VLAN ID and VLAN priority can be directly used to
label the VLAN tag. If this parameter is set to
VLANGROUP, the next hop IP addresses are mapped
to the VLAN groups, and then mapped to the VLAN
tags in the VLAN groups according to the DSCPs of the
IP packets. In VLAN group mode, ensure that the
VLAN groups have been configured by running the
ADD VLANCLASS command. Otherwise, the
configuration does not take effect.
GUI Value Range: SINGLEVLAN(Single VLAN),
VLANGROUP(VLAN Group)
Unit: None
Actual Value Range: SINGLEVLAN, VLANGROUP
Default Value: None
VLANI
D
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
Issue 01 (2014-04-30)
ADD
VLAN
MAP
MOD
VLAN
MAP
LST
VLAN
MAP
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the VLAN ID in the VLAN tag.

Unit: None
Default Value: 1

322
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SETPRI
O
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
VLAN
MAP
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates whether to set the priority of a single

VLAN. When this parameter is set to ENABLE, the
VLAN priority is configured by running the ADD
VLANMAP command. When this parameter is set to
DISABLE, the VLAN priority is determined by the
mapping between DSCP and VLAN priority. This
mapping can be configured by running the SET
DSCPMAP command. The default mapping between
DSCP and VLAN priority is as follows: If the DSCP is
within the range from 0 to 7, the default priority is 0; If
the DSCP is within the range from 8 to 15, the default
priority is 1; If the DSCP is within the range from 16 to
23, the default priority is 2; If the DSCP is within the
range from 24 to 31, the default priority is 3; If the DSCP
is within the range from 32 to 39, the default priority is
4; If the DSCP is within the range from 40 to 47, the
default priority is 5; If the DSCP is within the range from
48 to 55, the default priority is 6; If the DSCP is within
the range from 56 to 63, the default priority is 7.
MOD
VLAN
MAP
LST
VLAN
MAP

(Enable)
Unit: None
Default Value: ENABLE(Enable)
VLANG
ROUPN
O
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
VLANC
LASS
LST
VLANC
LASS
MOD
VLANC
LASS
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the VLAN group that the added

VLAN mapping belongs to. Multiple VLAN groups are
used in the scenario in which telecom operators share
transport resources and use different VLAN policies.
Unit: None
Default Value: 0
RMV
VLANC
LASS
Issue 01 (2014-04-30)

323
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
TRAFFI
C
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
VLANC
LASS
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the traffic type. Traffic of different

types is transmitted through different VLANs. OTHER
data is the data except the user data, signaling, highpriority OM data, and low-priority OM data. OTHER
data includes the data of the IEEE 1588 V2 clock, clock
over IP, and Address Resolution Protocol (ARP)
services. OM_HIGH data includes the data of the NTP/
SNTP, switchover between remote maintenance
channels, and TCP services.
MOD
VLANC
LASS
RMV
VLANC
LASS
GUI Value Range: USERDATA(User Data), SIG

(Signaling Data), OM(Maintenance Data), OTHER
(Other Data), OM_HIGH(High Level Maintenance
Data), OM_LOW(Low Level Maintenance Data)
LST
VLANC
LASS
Unit: None
Actual Value Range: USERDATA, SIG, OM, OTHER,
OM_HIGH, OM_LOW
Default Value: None
SRVPRI
O
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
VLANC
LASS
WRFD050402
MOD
VLANC
LASS
RMV
VLANC
LASS
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the DSCP priority of user data.
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the VLAN ID that the service data

belongs to.

Unit: None
Default Value: 0
LST
VLANC
LASS
VLANI
D
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
Issue 01 (2014-04-30)
ADD
VLANC
LASS
MOD
VLANC
LASS
LST
VLANC
LASS
WRFD050402

Unit: None
Default Value: 1

324
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
NEXTH
OP
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
WRFD050402
Meaning: Indicates the IP address of the next hop.
MOD
IPRT
WRFD050107
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPRT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
TUNNE
L
IFNO
SCN
DSP
IPRT
LST
IPRT

Unit: None
Default Value: 0.0.0.0
IP
routing
Based
Hub
Node B
None
None
Meaning: Indicates the port number.

MOD
IPRT
Unit: None
LST
IPRT
Default Value: 0
DSP
TUNNE
L
MOD
TUNNE
L
MRFD221501
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
Meaning: Indicates the number of the source cabinet

where the tunnel is configured.
Unit: None
Default Value: 0
RMV
TUNNE
L
LST
TUNNE
L
Issue 01 (2014-04-30)

325
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SSRN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
TUNNE
L
MRFD221501
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
Meaning: Indicates the number of the source subrack

where the tunnel is configured.
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
Meaning: Indicates the number of the source slot where

the tunnel is configured.
DSP
TUNNE
L
MOD
TUNNE
L

Unit: None
Default Value: 0
RMV
TUNNE
L
LST
TUNNE
L
SSN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
TUNNE
L
DSP
TUNNE
L
MOD
TUNNE
L
MRFD221501

Unit: None
Default Value: None
RMV
TUNNE
L
LST
TUNNE
L
Issue 01 (2014-04-30)

326
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
TUNNE
LID
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
TUNNE
L
MRFD221501
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
Meaning: Indicates the index of the tunnel.
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
Meaning: Indicates the number of the destination

cabinet where the tunnel is located.
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
Meaning: Indicates the number of the destination slot

where the tunnel is located.
DSP
TUNNE
L
MOD
TUNNE
L

Unit: None
Default Value: None
RMV
TUNNE
L
LST
TUNNE
L
DCN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
TUNNE
L
MRFD221501
MOD
TUNNE
L
DSP
TUNNE
L

Unit: None
Default Value: None
LST
TUNNE
L
DSN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
TUNNE
L
MOD
TUNNE
L
DSP
TUNNE
L
MRFD221501

Unit: None
Default Value: None
LST
TUNNE
L
Issue 01 (2014-04-30)

327
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
CN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
DSP
BRDRA
T
None
None
Meaning: Indicates the cabinet number of the extension

transmission board.
LST
UTRP
Unit: None
MOD
UTRP
Default Value: None
SET
BRDRA
T
SRN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
DSP
BRDRA
T
None
None
Meaning: Indicates the subrack number of the extension

transmission board.
LST
UTRP
Unit: None
MOD
UTRP
Default Value: None
SET
BRDRA
T
SN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
DSP
BRDRA
T
None
None
Meaning: Indicates the slot number of the extension

transmission board.
LST
UTRP
Unit: None
MOD
UTRP
Default Value: None
SET
BRDRA
T
Issue 01 (2014-04-30)

328
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DSRN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
TUNNE
L
MRFD221501
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
Meaning: Indicates the number of the destination

subrack where the tunnel is located.
Meaning: Indicates the type of the IP path. FIXED

indicates that this IP path is used to carry the service
with specified Quality of Service (QoS), that is, with a
specified DSCP. ANY indicates that this IP Path can be
used to carry services of any QoS and hence is used to
carry the service without a specified DSCP.
MOD
TUNNE
L
DSP
TUNNE
L

Unit: None
Default Value: None
LST
TUNNE
L
PATHT
YPE
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
GBFD-1
18601
Abis
over IP
MOD
IPPATH
GBFD-1
18611
Abis IP
over E1/
T1
LST
IPPATH
GUI Value Range: FIXED(Fixed QoS), ANY(Any

QoS)
Unit: None
Actual Value Range: FIXED, ANY
Default Value: FIXED(Fixed QoS)
IP
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
Issue 01 (2014-04-30)
ADD
OMCH
MOD
OMCH
DSP
OMCH
LST
OMCH
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the local IP address of a remote

maintenance channel.
Unit: None
Default Value: None

329
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
CN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
None
None
Meaning: Indicates the number of the cabinet that

houses the board where a transmission resource group
is established.
DSP
RSCGR
P

Unit: None
MOD
RSCGR
P
Default Value: 0
RMV
RSCGR
P
LST
RSCGR
P
SRN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
DSP
RSCGR
P
MOD
RSCGR
P
None
None
Meaning: Indicates the number of the subrack that

houses the board where a transmission resource group
is established.
Unit: None
Default Value: 0
RMV
RSCGR
P
LST
RSCGR
P
Issue 01 (2014-04-30)

330
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
None
None
Meaning: Indicates the number of the slot

corresponding to the board where a transmission
resource group is established.
DSP
RSCGR
P

Unit: None
MOD
RSCGR
P
Default Value: None
RMV
RSCGR
P
LST
RSCGR
P
BEAR
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
DSP
RSCGR
P
MOD
RSCGR
P
WRFD050404
ATM/IP
Dual
Stack
Node B
Meaning: Indicates the bearer type of the transmission

group. The LTE currently does not support ATM.
GUI Value Range: ATM(ATM), IP(IP)
Unit: None
Actual Value Range: ATM, IP
Default Value: None
RMV
RSCGR
P
LST
RSCGR
P
Issue 01 (2014-04-30)

331
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SBT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
None
None
Meaning: Indicates the type of sub-board on the

transmission group. The LTE currently does not support
UNCHANNELLED_COVERBOARD.
DSP
RSCGR
P

MOD
RSCGR
P
Unit: None
RMV
RSCGR
P

ETH_COVERBOARD
LST
RSCGR
P
PT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
DSP
RSCGR
P
MOD
RSCGR
P
RMV
RSCGR
P
Default Value: None

None
None
Meaning: Indicates the type of port where a

transmission resource group is carried. The LTE
currently does not support STM1, IMA, UNI, or
FRAATM.
GUI Value Range: IMA(IMA Group), UNI(UNI Link),
STM1(STM1), FRAATM(FRAATM Link), PPP(PPP
Link), MPGRP(Multi-link PPP Group), ETH(Ethernet
Port), ETHTRK(Ethernet Trunk), TUNNEL(Tunnel)
Unit: None
Actual Value Range: IMA, UNI, STM1, FRAATM,
PPP, MPGRP, ETH, ETHTRK, TUNNEL
Default Value: None
LST
RSCGR
P
Issue 01 (2014-04-30)

332
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
PN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
None
None
Meaning: Indicates the number of the port where the

transmission resource group is configured.
DSP
RSCGR
P
Unit: None
MOD
RSCGR
P
Default Value: 0
RMV
RSCGR
P
LST
RSCGR
P
RSCGR
PID
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
WRFD0213040
6
DSP
RSCGR
P
MOD
RSCGR
P
Transmi
ssion
Recours
e
Sharing
on Iub/
Iur
Interface
GUI Value Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,

13, 14, 15, DEFAULTPORT(Default Port)
RMV
RSCGR
P
Unit: None
Actual Value Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,
12, 13, 14, 15, DEFAULTPORT
LST
RSCGR
P
RU
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
MOD
RSCGR
P
DSP
RSCGR
P
Meaning: Indicates the ID of a transmission resource

group.When you add a PPP link, an MP group, an
Ethernet port, an Ethernet trunk, a tunnel, or a PPPoE
link, the system automatically creates an algorithm for
the transmission resource group with Transmission
Resource Group ID set to DEFAULTPORT(Default
Port). When you remove any of the preceding objects,
the system automatically removes the algorithm for the
transmission resource group.
Default Value: None

WRFD0213040
6
Transmi
ssion
Recours
e
Sharing
on Iub/
Iur
Interface
Meaning: Indicates the rate unit of the TX bandwidth,

RX bandwidth, TX CIR, RX CIR, TX PIR and RX PIR
of the transmission resource group. The LTE currently
does not support CELL/S.
GUI Value Range: KBPS(Kbit/s), CELL/S(cell/s)
Unit: None
Actual Value Range: KBPS, CELL/S
Default Value: KBPS(Kbit/s)
LST
RSCGR
P
Issue 01 (2014-04-30)

333
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
TXBW
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
WRFD0213040
6
Transmi
ssion
Recours
e
Sharing
on Iub/
Iur
Interface
Meaning: Indicates the maximum uplink bandwidth of

a transmission resource group at the MAC layer when
the transmission resource group is carried over IP. This
parameter value is used as the uplink transport
admission bandwidth and TX traffic shaping
bandwidth.The LMPT can be configured with a
maximum of 360 Mbit/s TX bandwidth.The WMPT can
be configured with a maximum of 300 Mbit/s TX
bandwidth.The UMPT or UTRPc can be configured
with a maximum of 1 Gbit/s TX bandwidth.The value
of TX bandwidth is set to the maximum value of TX
bandwidth supported by the board when it bigger than
the maximum one. For a WMPT and a UTRP (excluding
UTRPa), this parameter does not specify the TX traffic
shaping bandwidth of the transmission resource group
that is carried on the PPP link.
MOD
RSCGR
P
DSP
RSCGR
P
LST
RSCGR
P

Unit: None
Default Value: None
RXBW
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
RSCGR
P
WRFD0213040
6
MOD
RSCGR
P
WRFD0106101
0
DSP
RSCGR
P
LST
RSCGR
P
Transmi
ssion
Recours
e
Sharing
on Iub/
Iur
Interface
HSDPA
Flow
Control
Meaning: Indicates the RX bandwidth of a transmission

resource group.To LTE, this parameter value is also
used as the downlink transport admission
bandwidth.The minimum rate supported by the UMPTb
is 64 Kbit/s.The LMPT can be configured with a
maximum of 540 Mbit/s RX bandwidth.The WMPT can
be configured with a maximum of 300 Mbit/s RX
bandwidth.The UMPT or UTRPc can be configured
with a maximum of 1 Gbit/s RX bandwidth.The value
of RX bandwidth is set to the maximum value of RX
bandwidth supported by the board when it bigger than
the maximum one.
Unit: None
Default Value: None
Issue 01 (2014-04-30)

334
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
PATHI
D
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the ID of an IP path.
None

where the IP path is located.
DSP
IPPATH
LST
IPPATH

Unit: None
Default Value: None
MOD
IPPATH
RMV
IPPATH
CN
SRN
SN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
Issue 01 (2014-04-30)
None
MOD
IPPATH
LST
IPPATH
Unit: None
Default Value: 0
None
None

where the IP path is located.
MOD
IPPATH
LST
IPPATH
Unit: None
Default Value: 0
None
None

the IP path is located.
MOD
IPPATH
LST
IPPATH
Unit: None
Default Value: None

335
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SBT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
None
None

where the IP path is established.
MOD
IPPATH

E1_COVERBOARD(E1 Cover Board),
LST
IPPATH
Unit: None
ETH_COVERBOARD
Default Value: None
PT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
None
None
Meaning: Indicates the physical port type of the IP path.

PPP Group), ETH(Ethernet Port), ETHTRK(Ethernet
Trunk), LOOPINT(Loopback Interface), TUNNEL
(Tunnel)
MOD
IPPATH
LST
IPPATH
Unit: None
Actual Value Range: PPP, MPGRP, ETH, ETHTRK,
LOOPINT, TUNNEL
Default Value: None
PN
JNRSC
GRP
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
None
None
Meaning: Indicates the number of the port where the IP

path is configured.
MOD
IPPATH
LST
IPPATH
MOD
IPPATH
LST
IPPATH
Unit: None
Default Value: 0
WRFD0213040
6
Transmi
ssion
Recours
e
Sharing
on Iub/
Iur
Interface
Meaning: Indicates whether the IP path joins a

transmission resource group. If this parameter is set to
DISABLE, the IP path is established on the default
transmission resource group on a specific physical port.
(Enable)
Unit: None
Default Value: DISABLE(Disable)
Issue 01 (2014-04-30)

336
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
LOCAL
IP
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the local IP address of an IP path.

The value 0.0.0.0 indicates that the local IP address
needs to be negotiated.
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
BTS390
0
WCDM
A
None
PEERIP
DSCP
RXBW
MOD
IPPATH
LST
IPPATH

Unit: None
Default Value: None
WRFD050402
MOD
IPPATH
LST
IPPATH
WRFD050402
MOD
IPPATH
LST
IPPATH
WRFD0106101
0
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the peer IP address of the IP path.
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the differentiated services code

point (DSCP) of the services carried on an IP path.
HSDPA
Flow
Control
Meaning: Indicates the RX bandwidth of the IP path.

When the IP path is not added to a transmission resource
group, the RX bandwidth cannot be greater than the
maximum RX bandwidth of the physical port. When the
IP path is added to a transmission resource group, the
RX bandwidth cannot be greater than the maximum RX
bandwidth of the physical port on which the
transmission resource group is established.

Unit: None
Default Value: None

Unit: None
Default Value: None

Unit: Kbit/s
Default Value: 8
Issue 01 (2014-04-30)

337
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
TXBW
BTS390
0
WCDM
A
None
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the TX bandwidth of an IP path.

When the IP path is not added to a transmission resource
group, the TX bandwidth cannot be greater than the
maximum TX bandwidth of the physical port. When the
IP path is added to a transmission resource group, the
TX bandwidth cannot be greater than the maximum TX
bandwidth of the physical port on which the
transmission resource group is established.
Unit: Kbit/s
Default Value: 8
TXCBS
TXEBS
MASK
BTS390
0
WCDM
A
BTS390
0
WCDM
A
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
Issue 01 (2014-04-30)
None
None
ADD
OMCH
MOD
OMCH
DSP
OMCH
LST
OMCH
WRFD050402
WRFD050402
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the TX committed burst size at the

IP path.
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the TX excessive burst size at the IP

path.
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates the local subnet mask of a remote

maintenance channel.

Unit: bit
Default Value: 15000

Unit: bit
Default Value: 0

Unit: None
Default Value: None

338
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
PEERIP
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
OMCH
WRFD050404
ATM/IP
Dual
Stack
Node B
Meaning: Indicates the peer IP address of the remote

maintenance channel, indicates the IP address of the
U2000 in an IP network and the device IP address of the
RNC in an ATM network.
PEERM
ASK
BEAR
MOD
OMCH
DSP
OMCH
Unit: None
LST
OMCH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
OMCH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
OMCH
Default Value: None

WRFD050404
MOD
OMCH
ATM/IP
Dual
Stack
Node B
DSP
OMCH
Meaning: Indicates the subnet mask of the peer IP

address for the remote maintenance channel.
Unit: None
Default Value: None
LST
OMCH
WRFD050404
MOD
OMCH
ATM/IP
Dual
Stack
Node B
DSP
OMCH
LST
OMCH
Meaning: Indicates the bearer type of a remote

maintenance channel. This parameter can be set to ATM
or IPV4. If this parameter is set to ATM, the Element
Management System (EMS) uses the ATM transport
network to maintain the device. If this parameter is set
to IPV4, the EMS uses the IP transport network to
maintain the device.
GUI Value Range: ATM(ATM), IPV4(IPV4)
Unit: None
Actual Value Range: ATM, IPV4
Default Value: IPV4(IPV4)
CN
BTS390
0,
BTS390
0
WCDM
A
ADD
OMCH
None

where the remote maintenance channel is located.
MOD
OMCH
DSP
OMCH
LST
OMCH
Issue 01 (2014-04-30)
None
Unit: None
Default Value: 0

339
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SRN
BTS390
0,
BTS390
0
WCDM
A
ADD
OMCH
None
None

where the remote maintenance channel is located.
MOD
OMCH
DSP
OMCH
Unit: None
Default Value: 0
LST
OMCH
SN
BTS390
0,
BTS390
0
WCDM
A
ADD
OMCH
None
None
MOD
OMCH
DSP
OMCH
Unit: None
Default Value: None
LST
OMCH
SBT
BTS390
0,
BTS390
0
WCDM
A

the remote maintenance channel is located.
ADD
OMCH
MOD
OMCH
DSP
OMCH
LST
OMCH
None
None

where a remote maintenance channel is established.
BACK_BOARD(Back Board)
Unit: None
E1_COVERBOARD, BACK_BOARD
Default Value: None
Issue 01 (2014-04-30)

340
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
BRT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
OMCH
WRFD050402
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
Meaning: Indicates whether a route is bound to the

remote maintenance channel. If the peer IP of the remote
maintenance channel and device IP addresses are not in
the same network segment and the network segment of
the device IP address cannot cover that of the peer IP
address, run the ADD IPRT command to add a route to
the remote maintenance channel. If this parameter is set
to YES, a route is bound to the remote maintenance
channel, and the route takes effect only when the remote
maintenance takes effect. If this parameter is set to NO,
no route is bound to the remote maintenance channel,
and a remote maintenance channel switchover does not
trigger a route status switchover.
MOD
OMCH
DSP
OMCH
LST
OMCH
GUI Value Range: NO(No), YES(Yes)

Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
LN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
None
None
Meaning: Indicates the number of the control link at the

local end.
LST
CTRLL
NK
Unit: None
MOD
CTRLL
NK
Default Value: None
RMV
CTRLL
NK
CN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
DSP
CTRLL
NKSTA
T
None
None
Meaning: Indicates the cabinet number of the local node

at one end of the control link.
Unit: None
Default Value: None
MOD
CTRLL
NK
LST
CTRLL
NK
Issue 01 (2014-04-30)

341
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SRN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
None
None
Meaning: Indicates the subrack number of the local

node at one end of the control link.
DSP
CTRLL
NKSTA
T
Unit: None
Default Value: None
MOD
CTRLL
NK
LST
CTRLL
NK
SN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
None
None
Meaning: Indicates the slot number of the local node at

one end of the control link.
DSP
CTRLL
NKSTA
T
Unit: None
Default Value: None
MOD
CTRLL
NK
LST
CTRLL
NK
UPCN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
Issue 01 (2014-04-30)
ADD
CTRLL
NK
None
None
Meaning: Indicates the cabinet number of the upperlevel node at the other end of the control link.
MOD
CTRLL
NK
Unit: None
LST
CTRLL
NK
Default Value: None

342
SingleRAN
8 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
UPSRN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
None
None
Meaning: Indicates the subrack number of the upperlevel node at the other end of the control link.
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
UPSN
UPPT
Issue 01 (2014-04-30)
MOD
CTRLL
NK
Unit: None
LST
CTRLL
NK
Default Value: None
None
None
Meaning: Indicates the slot number of the upper-level

node at the other end of the control link.
MOD
CTRLL
NK
Unit: None
LST
CTRLL
NK
Default Value: None
MOD
CTRLL
NK
LST
CTRLL
NK
None
None
Meaning: Indicates the port number of the upper-level

node at the other end of the control link. Values 0 to 4
indicate the ports M0 to M4 on the UCIU, and value 8
indicates the CI port on the UMPT.
GUI Value Range: 0~4,8
Unit: None
Actual Value Range: 0~4,8
Default Value: None

343
SingleRAN
9 Counters
Counters
Table 9-1 Counter description

Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
1542455856
VS.TUNNEL.T
xBytes
Number of
Bytes
Transmitted in
the Tunnel
NodeB
Multi-mode:
MRFD-211501

BS side(GBTS)
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
Issue 01 (2014-04-30)

344
SingleRAN
9 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
1542455857
VS.TUNNEL.T
xPackets
Number of
Packets
Transmitted in
the Tunnel
NodeB
Multi-mode:
MRFD-211501

BS side(GBTS)
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
1542455858
VS.TUNNEL.R
xBytes
Number of
Bytes Received
in the Tunnel
NodeB
Multi-mode:
MRFD-211501
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(GBTS)
BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
Issue 01 (2014-04-30)

345
SingleRAN
9 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
1542455859
VS.TUNNEL.R
xPackets
Number of
Packets
Received in the
Tunnel
NodeB
Multi-mode:
MRFD-211501

BS side(GBTS)
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
1542455860
VS.TUNNEL.T
xMaxSpeed
Maximum
Transmit Rate in
the Tunnel
NodeB
Multi-mode:
MRFD-211501
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(GBTS)
BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
Issue 01 (2014-04-30)

346
SingleRAN
9 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
1542455861
VS.TUNNEL.T
xMinSpeed
Minimum
Transmit Rate in
the Tunnel
NodeB
Multi-mode:
MRFD-211501

BS side(GBTS)
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
1542455862
VS.TUNNEL.T
xMeanSpeed
Average
Transmit Rate in
the Tunnel
NodeB
Multi-mode:
MRFD-211501
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(GBTS)
BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
Issue 01 (2014-04-30)

347
SingleRAN
9 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
1542455863
VS.TUNNEL.R
xMaxSpeed
Maximum
Receive Rate in
the Tunnel
NodeB
Multi-mode:
MRFD-211501

BS side(GBTS)
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
1542455864
VS.TUNNEL.R
xMinSpeed
Minimum
Receive Rate in
the Tunnel
NodeB
Multi-mode:
MRFD-211501
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(GBTS)
BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
Issue 01 (2014-04-30)

348
SingleRAN
9 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
1542455865
VS.TUNNEL.R
xMeanSpeed
Average
Receive Rate in
the Tunnel
NodeB
Multi-mode:
MRFD-211501

BS side(GBTS)
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None

BS side(NodeB)
BS side
(eNodeB)
BS side(LTE
TDD)
Issue 01 (2014-04-30)

349
SingleRAN
10 Glossary
10
Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue 01 (2014-04-30)

350
SingleRAN
11
11 Reference Documents
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
Issue 01 (2014-04-30)

351

Common Transmission (SRAN9.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 (SRAN9.0 01)

Uploaded by

Copyright:

Available Formats

SingleRAN

Common Transmission Feature

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

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

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

Huawei Proprietary and Confidential

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

6 Impact on the Network...............................................................................................................43

Huawei Proprietary and Confidential

7.5.6 Activation Observation..............................................................................................................................................61

Huawei Proprietary and Confidential

7.11.1 Deployment Requirements....................................................................................................................................108

Huawei Proprietary and Confidential

7.16.4 Hardware Adjustment............................................................................................................................................180

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

7.32 Performance Monitoring...........................................................................................................................................308

Huawei Proprietary and Confidential

1 About This Document

About This Document

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

MRFD-211504 TDM-Based Multi-mode Co-Transmission via Backplane on BS side

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

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

MRFD-221504 TDM-Based Multi-mode Co-Transmission via Backplane on BS side

MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)

MRFD-241501 IP-Based Multi-mode Co-Transmission on BS side(LTE TDD)

Includes FDD and TDD

Includes FDD Only

Includes TDD Only

LTE FDD eNodeB

LTE TDD eNodeB

LTE FDD eRAN

LTE TDD eRAN

Huawei Proprietary and Confidential

1 About This Document

1.2 Intended Audience

Need to understand the features described herein

Work with Huawei products

1.3 Change History

SRAN9.0 Draft A (2014-01-20)

Huawei Proprietary and Confidential

1 About This Document

Added common transmission for the LTE TDD mode.

Huawei mobile network management system M2000

1.4 Differences Between Base Station Types

Huawei Proprietary and Confidential

Base Station Name

GBTS refers to a base station deployed with

eGBTS refers to a base station deployed with

NodeB refers to a base station deployed with

eNodeB refers to a base station deployed with

Co-MPT Multimode Base Station

Co-MPT multimode base station refers to a

Huawei Proprietary and Confidential

Base Station Name

Separate-MPT Multimode Base Station