Beruflich Dokumente
Kultur Dokumente
01
Date
2014-04-30
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.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2014-04-30)
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
ii
SingleRAN
Common Transmission Feature Parameter Description
Contents
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
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.1 Deployment Requirements........................................................................................................................................54
7.5.2 Data Preparation........................................................................................................................................................55
7.5.3 Precautions.................................................................................................................................................................58
7.5.4 Hardware Adjustment................................................................................................................................................58
7.5.5 Initial Configuration..................................................................................................................................................58
Issue 01 (2014-04-30)
iii
SingleRAN
Common Transmission Feature Parameter Description
Contents
iv
SingleRAN
Common Transmission Feature Parameter Description
Contents
SingleRAN
Common Transmission Feature Parameter Description
Contents
vi
SingleRAN
Common Transmission Feature Parameter Description
Contents
7.21.4 Precautions.............................................................................................................................................................215
7.21.5 Reconfiguration.....................................................................................................................................................216
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
Station Side in IP over FE/GE Mode................................................................................................................................217
7.22.1 Deployment Requirements....................................................................................................................................217
7.22.2 Data Preparation....................................................................................................................................................219
7.22.3 Reconstruction Preparations and Procedure..........................................................................................................227
7.22.4 Precautions.............................................................................................................................................................228
7.22.5 Reconfiguration.....................................................................................................................................................229
7.22.6 Hardware Adjustment............................................................................................................................................231
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.1 Deployment Requirements....................................................................................................................................233
7.23.2 Data Preparation....................................................................................................................................................234
7.23.3 Reconstruction Preparations and Procedure..........................................................................................................237
7.23.4 Precautions.............................................................................................................................................................239
7.23.5 Reconfiguration.....................................................................................................................................................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.1 Deployment Requirements....................................................................................................................................241
7.24.2 Data Preparation....................................................................................................................................................244
7.24.3 Reconstruction Preparations and Procedure..........................................................................................................246
7.24.4 Precautions.............................................................................................................................................................248
7.24.5 Reconfiguration.....................................................................................................................................................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.1 Deployment Requirements....................................................................................................................................250
7.25.2 Data Preparation....................................................................................................................................................251
7.25.3 Precautions.............................................................................................................................................................254
7.25.4 Hardware Adjustment............................................................................................................................................254
7.25.5 Initial Configuration..............................................................................................................................................254
7.25.6 Activation Observation..........................................................................................................................................256
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
7.26.1 Deployment Requirements....................................................................................................................................257
7.26.2 Data Preparation....................................................................................................................................................257
Issue 01 (2014-04-30)
vii
SingleRAN
Common Transmission Feature Parameter Description
Contents
7.26.3 Precautions.............................................................................................................................................................260
7.26.4 Hardware Adjustment............................................................................................................................................260
7.26.5 Initial Configuration..............................................................................................................................................261
7.26.6 Activation Observation..........................................................................................................................................262
7.27 GTMU-based TDM Co-Transmission on the Separate-MPT GU Multimode Base Station Side............................263
7.27.1 Deployment Requirements....................................................................................................................................263
7.27.2 Data Preparation....................................................................................................................................................263
7.27.3 Precautions.............................................................................................................................................................264
7.27.4 Hardware Adjustment............................................................................................................................................264
7.27.5 Initial Configuration..............................................................................................................................................264
7.27.6 Activation Observation..........................................................................................................................................265
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.1 Deployment Requirements....................................................................................................................................265
7.28.2 Data Preparation....................................................................................................................................................266
7.28.3 Precautions.............................................................................................................................................................269
7.28.4 Hardware Adjustment............................................................................................................................................269
7.28.5 Initial Configuration..............................................................................................................................................269
7.28.6 Activation Observation..........................................................................................................................................271
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.1 Deployment Requirements....................................................................................................................................271
7.29.2 Data Preparation....................................................................................................................................................272
7.29.3 Precautions.............................................................................................................................................................276
7.29.4 Hardware Adjustment............................................................................................................................................276
7.29.5 Initial Configuration..............................................................................................................................................276
7.29.6 Activation Observation..........................................................................................................................................278
7.30 Co-Transmission on the Hybrid-MPT GUL Multimode Base Station Side in IP over FE/GE Mode.....................278
7.30.1 Deployment Requirements....................................................................................................................................279
7.30.2 Data Preparation....................................................................................................................................................279
7.30.3 Precautions.............................................................................................................................................................285
7.30.4 Hardware Adjustment............................................................................................................................................285
7.30.5 Initial Configuration..............................................................................................................................................285
7.30.6 Activation Observation..........................................................................................................................................288
7.31 Main-control-board -based Co-Transmission Through Backplane Interconnection on the Separate-MPT LGU/TGU
Multimode Base Station Side in IP over FE/GE Mode....................................................................................................289
7.31.1 Deployment Requirements....................................................................................................................................289
7.31.2 Data Preparation....................................................................................................................................................293
7.31.3 Precautions.............................................................................................................................................................302
7.31.4 Hardware Adjustment............................................................................................................................................302
7.31.5 Initial Configuration..............................................................................................................................................302
7.31.6 Activation Observation..........................................................................................................................................307
Issue 01 (2014-04-30)
viii
SingleRAN
Common Transmission Feature Parameter Description
Contents
8 Parameters...................................................................................................................................311
9 Counters...................................................................................................................................... 344
10 Glossary.....................................................................................................................................350
11 Reference Documents.............................................................................................................351
Issue 01 (2014-04-30)
ix
SingleRAN
Common Transmission Feature Parameter Description
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
The document involves the following features on the multimode base station side:
l
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)
LTE
LTE FDD
LTE TDD
eNodeB
eRAN
SingleRAN
Common Transmission Feature Parameter Description
In addition, the "L" and "T" in RAT acronyms refer to LTE FDD and LTE TDD, respectively.
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.
Issue 01 (2014-04-30)
SingleRAN
Common Transmission Feature Parameter Description
Change Type
Change Description
Parameter
Change
Feature change
None
None.
None
Issue 01 (2014-04-30)
SingleRAN
Common Transmission Feature Parameter Description
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)
Definition
GBTS
eGBTS
NodeB
eNodeB
SingleRAN
Common Transmission Feature Parameter Description
2 Overview
Definition
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
A smooth evolution from GSM to UMTS or LTE can be achieved with less transport
network adjustments.
Issue 01 (2014-04-30)
SingleRAN
Common Transmission Feature Parameter Description
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.
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
Common Transmission Feature Parameter Description
2 Overview
Issue 01 (2014-04-30)
Description
Main-control-board-based
co-transmission through
panel interconnection
SingleRAN
Common Transmission Feature Parameter Description
2 Overview
Co-Transmission Type
Co-transmission through
backplane interconnection
Description
Main-control-board-based
co-transmission through
backplane interconnection
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
Common Transmission Feature Parameter Description
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
Common Transmission Feature Parameter Description
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
Common Transmission Feature Parameter Description
Figure 3-2 Co-transmission for the Iub and Abis interfaces in IP over E1/T1 mode on the MBSC
side
NOTE
Issue 01 (2014-04-30)
11
SingleRAN
Common Transmission Feature Parameter Description
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.
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
Common Transmission Feature Parameter Description
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.
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
Issue 01 (2014-04-30)
13
SingleRAN
Common Transmission Feature Parameter Description
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.
Issue 01 (2014-04-30)
14
SingleRAN
Common Transmission Feature Parameter Description
Figure 3-6 Co-transmission for the Iu-CS and A interfaces in E1/T1 over STM-1/OC-3 mode
NOTE
As shown in Figure 3-7, the interface board shared by the Iu-CS and A 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.
Issue 01 (2014-04-30)
15
SingleRAN
Common Transmission Feature Parameter Description
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
Common Transmission Feature Parameter Description
NOTE
Issue 01 (2014-04-30)
17
SingleRAN
Common Transmission Feature Parameter Description
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
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.
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
Common Transmission Feature Parameter Description
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
Common Transmission Feature Parameter Description
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
Common Transmission Feature Parameter Description
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.
Issue 01 (2014-04-30)
21
SingleRAN
Common Transmission Feature Parameter Description
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
GTMU
GSM
WMPT
UMTS
LMPT
LTE
Issue 01 (2014-04-30)
22
SingleRAN
Common Transmission Feature Parameter Description
Board Type
Board Name
Supported
Mode
Description
UMPT
GSM/UMTS/LTE
Universal
transmission
processing unit
UTRP2
UMTS
UTRP3
UMTS
UTRP4
UMTS
UTRPb4
GSM
UTRP9
UMTS
UTRPc
GSM/UMTS/LTE
Issue 01 (2014-04-30)
23
SingleRAN
Common Transmission Feature Parameter Description
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.
Scenario
Sub-Scenario
Co-Transmission
Solution
Separate-MPT
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
port interconnection.
Issue 01 (2014-04-30)
24
SingleRAN
Common Transmission Feature Parameter Description
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
UL/UT
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
RNC, MME, and SGW. The WMPT of
the NodeB is
connected to the
LMPT through FE
port interconnection.
GUL/GUT
An FE/GE port is
used as a cotransmission port.
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
of the base station is
connected to the
WMPT through FE
interconnection.
WMPT and LMPT
are also connected
through FE port
interconnection.
Issue 01 (2014-04-30)
25
SingleRAN
Common Transmission Feature Parameter Description
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
GU
An FE/GE or E1/T1
port is used as a cotransmission port.
GL/GT
An FE/GE port is
used as a cotransmission port.
The UMPT_U
provides an FE/GE
port as the cotransmission port to
be connected to the
MBSC. The GTMUb
of the base station is
connected to the
UMPT_U through
the backplane.
Issue 01 (2014-04-30)
26
SingleRAN
Common Transmission Feature Parameter Description
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
UL/UT
An FE/GE port is
used as a cotransmission port.
The UMPT_U
provides an FE/GE
port as the cotransmission port to
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
Common Transmission Feature Parameter Description
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
GUL/GUT
An FE/GE port is
used as a cotransmission port.
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
Common Transmission Feature Parameter Description
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
Common Transmission Feature Parameter Description
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
GU
An FE/GE port is
used as a cotransmission port.
The UTRPc is
managed by the
WMPT/UMPT_U of
the NodeB and
provides an FE/GE
port as the cotransmission port to
be connected to the
MBSC. The GTMUb
is connected to the
UTRPc through the
backplane.
UL/UT
An FE/GE port is
used as a cotransmission port.
The UTRPc is
managed by the
LMPT/UMPT_L of
the eNodeB and
provides an FE/GE
port as the cotransmission port to
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
Common Transmission Feature Parameter Description
Multimode Base
Station Type
Scenario
Sub-Scenario
Co-Transmission
Solution
GUL/GUT
An FE/GE port is
used as a cotransmission port.
The UTRPc is
managed by the
WMPT/UMPT_U of
the NodeB and
provides an FE/GE
port as the cotransmission port to
be connected to the
MBSC, MME, and
S-GW. The GTMUb
of the base station is
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
Common Transmission Feature Parameter Description
NOTE
Issue 01 (2014-04-30)
32
SingleRAN
Common Transmission Feature Parameter Description
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.
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
Common Transmission Feature Parameter Description
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.
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
Common Transmission Feature Parameter Description
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
Common Transmission Feature Parameter Description
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.
Issue 01 (2014-04-30)
36
SingleRAN
Common Transmission Feature Parameter Description
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.
Issue 01 (2014-04-30)
37
SingleRAN
Common Transmission Feature Parameter Description
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.
38
SingleRAN
Common Transmission Feature Parameter Description
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.
Issue 01 (2014-04-30)
39
SingleRAN
Common Transmission Feature Parameter Description
5 Related Features
Related Features
Impacted Features
None
Issue 01 (2014-04-30)
40
SingleRAN
Common Transmission Feature Parameter Description
5 Related Features
In GSM mode:
GBFD-118601 Abis over IP
In UMTS mode:
WRFD-050402 IP Transmission Introduction on Iub Interface
WRFD-050302 Fractional ATM Function on Iub Interface
WRFD-050411 Fractional IP Function on Iub Interface
In LTE mode:
None
Impacted Features
None
In GSM mode:
GBFD-118601 Abis over IP
Issue 01 (2014-04-30)
41
SingleRAN
Common Transmission Feature Parameter Description
5 Related Features
In UMTS mode:
WRFD-050402 IP Transmission Introduction on Iub Interface
WRFD-050302 Fractional ATM Function on Iub Interface
WRFD-050411 Fractional IP Function on Iub Interface
In LTE mode:
None
Issue 01 (2014-04-30)
42
SingleRAN
Common Transmission Feature Parameter Description
Network Performance
No impact.
43
SingleRAN
Common Transmission Feature Parameter Description
Issue 01 (2014-04-30)
44
SingleRAN
Common Transmission Feature Parameter Description
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
NE
Sales Unit
MRFD-24
1501
IP-Based
Multimode CoTransmissi
on on BS
side(LTE
TDD)
eNodeB
per eNodeB
45
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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".
Issue 01 (2014-04-30)
46
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
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
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.
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Issue 01 (2014-04-30)
48
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
Issue 01 (2014-04-30)
21.21.21.254/24
30.30.30.11/24
20.20.20.188/24
30.30.30.12/24
20.20.20.189/24
51
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
Table 7-2 IP address plan
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
21.21.21.11/24
52
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
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
53
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
----End
----End
Deployment objective
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
11.11.11.11/32
23.23.23.1/24
21.21.21.254/24
23.23.23.254/24
55
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
30.30.30.1/24
20.20.20.188/24
20.20.20.1/24
30.30.30.188/24
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.
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.
Subboard Type
SBT
Subboard Type
56
SingleRAN
Common Transmission Feature Parameter Description
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
VLANGROUPNO
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
DEVIP
IPRT
Issue 01 (2014-04-30)
7 Engineering Guidelines
57
SingleRAN
Common Transmission Feature Parameter Description
MO
VLANCLASS
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
VLAN ID
VLANID
VLAN ID
SETPRIO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
7.5.3 Precautions
None
UG
58
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
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, 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.
2.
----End
Issue 01 (2014-04-30)
60
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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;
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="11.11.11.11",
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
Deployment objective
Figure 7-7 shows the main-control-board-based IP co-transmission through panel
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
Issue 01 (2014-04-30)
62
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
21.21.21.254/24
20.20.20.1/24
30.30.30.1/24
20.20.20.188/24
40.40.40.40/24
63
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
50.50.50.50/24
30.30.30.188/24
70.70.70.70/24
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.
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
IPRT
Route Index
VRFIDX
Route Index
Next Hop IP
NEXTHOP
Next Hop IP
Issue 01 (2014-04-30)
MO
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
Common Transmission Feature Parameter Description
MO
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
DHCPSVRIP
DHCP Server IP
Address
DHCPREL
AYSWITC
H
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
SETPRIO
VLAN Priority
VLANPRIO
VLAN Priority
IPRT
Issue 01 (2014-04-30)
7 Engineering Guidelines
65
SingleRAN
Common Transmission Feature Parameter Description
MO
VLANCLA
SS
7 Engineering Guidelines
MML Parameter ID
CME Parameter
Name
VLANGROUPNO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
7.6.3 Precautions
None
LU
Issue 01 (2014-04-30)
66
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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;
//Set the parameters for the Ethernet port (port 1 on board in slot 6) that is used
for interconnecting the LMPT to the WMPT.
Step 2 Run the eNodeB MML command ADD DEVIP to set the device IP address of the Ethernet port
on the LMPT that is used for interconnecting to the WMPT. In this step, ensure that IP addresses
of two ports used for interconnecting the eNodeB to the NodeB are on the same network segment.
ADD DEVIP: SN=6, SBT=BASE_BOARD, PT=ETH, PN=1, IP="30.30.30.1",
MASK="255.255.255.0";
//Set the IP address of the Ethernet port (port 1 on board in slot 6) that is used
for interconnecting the LMPT to the WMPT and ensure that the IP address is on the
same network segment as the port IP address of the WMPT.
Step 3 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
SET DHCPRELAYSWITCH: ES=ENABLE;
//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 DHCPSVRIP: DHCPSVRIP="70.70.70.70";
//Add the IP address of the DHCP server for the NodeB.
Step 7 (Optional) Configure VLAN. There are two methods of configuring differentiated VLAN data
for the NodeB and eNodeB:
----End
l
Issue 01 (2014-04-30)
68
SingleRAN
Common Transmission Feature Parameter Description
2.
7 Engineering Guidelines
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.
PING: CN=0, SRN=0, SN=6, SRCIP="20.20.20.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
PING: CN=0, SRN=0, SN=6, SRCIP="20.20.20.188", DSTIP="50.50.50.50",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
----End
UMTS Side
After the configuration file is delivered to the NodeB and activated, perform the following step
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.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="30.30.30.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End
Deployment objective
Figure 7-9 shows the main-control-board-based IP co-transmission through panel
interconnection on the separate-MPT LG multimode base station side. In this scenario, an
Issue 01 (2014-04-30)
69
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
Figure 7-9 Main-control-board-based IP co-transmission through panel interconnection on
the separate-MPT LG multimode base station side
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
Issue 01 (2014-04-30)
70
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
21.21.21.254/24
20.20.20.1/24
30.30.30.1/24
20.20.20.188/24
40.40.40.40/24
50.50.50.50/24
30.30.30.188/24
71
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
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
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
Common Transmission Feature Parameter Description
MO
7 Engineering Guidelines
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
ES
VLANMAP
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
SETPRIO
VLAN Priority
VLANPRIO
VLAN Priority
VLANGROUPNO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
VLANCLASS
7.7.3 Precautions
None
Issue 01 (2014-04-30)
73
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
LG
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 interconnection port on
the LMPT. 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 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
Step 1 Run the eNodeB MML command SET ETHPORT to set the attributes of the Ethernet port on
the LMPT that is used for interconnecting to the GTMU.
SET ETHPORT: SN=7, SBT=BASE_BOARD, PN=1, PA=COPPER, SPEED=AUTO, DUPLEX=AUTO;
//Set the parameters for the Ethernet port (port 1 on board in slot 7) that is used
for interconnecting the LMPT to the GTMU.
Step 2 Run the eNodeB MML command ADD DEVIP to set the device IP address of the Ethernet port
on the LMPT that is used for interconnecting to the GTMU. In this step, ensure that IP addresses
of two ports used for interconnecting the eNodeB to the BTS are on the same network segment.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=1, IP="30.30.30.1",
MASK="255.255.255.0";
//Set the IP address of the Ethernet port (port 1 on board in slot 7) that is used
for interconnecting the LMPT to the GTMU and ensure that the IP address is on the
same network segment as the port IP address of the GTMU.
Step 3 Run the eNodeB MML command ADD IPRT to add an uplink route from the 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 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;
//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 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 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.
SET DHCPRELAYSWITCH: ES=ENABLE;
//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 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 eNodeB:
l Method 1 (Recommended): Configure differentiated next-hop addresses. Specifically, the
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
ADD VLANMAP: NEXTHOPIP="20.20.20.101", MASK="255.255.255.0",
VLANMODE=SINGLEVLAN, VLANID=22, SETPRIO=DISABLE;
l Method 2 (Not recommended): Configure differentiated DSCP values. This method requires
differentiated DSCP values for the 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.
2.
----End
l
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:
Issue 01 (2014-04-30)
76
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="50.50.50.50",
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 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.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="30.30.30.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End
Deployment objective
Figure 7-11 shows the main-control-board-based IP co-transmission through panel
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
Issue 01 (2014-04-30)
78
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
11.11.11.11/32
23.23.23.1/24
21.21.21.254/24
23.23.23.254/24
60.60.60.1/24
79
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
20.20.20.188/24
20.20.20.1/24
60.60.60.188/24
30.30.30.1/24
30.30.30.188/24
40.40.40.40/24
50.50.50.50/24
70.70.70.70/24
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.
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 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
IPRT
Forward route
address
NEXTHOP
Forward route
address
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
Common Transmission Feature Parameter Description
MO
7 Engineering Guidelines
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
ES
DHCP Switch
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
Common Transmission Feature Parameter Description
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
ES
VLANMAP
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
SETPRIO
VLAN Priority
VLANPRIO
VLAN Priority
VLANGROUPNO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
IPRT
VLANCLASS
Issue 01 (2014-04-30)
7 Engineering Guidelines
83
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.8.3 Precautions
None
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
to an electrical port on the GTMU.
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
to an electrical port on the GTMU.
84
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 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
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=1, SPEED=AUTO, DUPLEX=AUTO;
//Set the parameters for the Ethernet port (port 1 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=1, IP="30.30.30.1",
MASK="255.255.255.0";
//Set the IP address of the Ethernet port (port 1 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 interconnection port on the LMPT.
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="60.60.60.1", PREF=60;
//Add a route from the NodeB to the BSC.
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
Issue 01 (2014-04-30)
85
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
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.
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
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.
----End
l
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.
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
Step 1 Run the eNodeB MML command SET ETHPORT to set the attributes of the Ethernet port on
the LMPT that is used for interconnecting to the WMPT.
SET ETHPORT: CN=0, SRN=1, SN=7, SBT=BASE_BOARD, PN=1, PA=COPPER, SPEED=AUTO,
DUPLEX=AUTO;
//Set the parameters for the Ethernet port (port 1 on board in slot 7) that is used
for interconnecting the LMPT to the WMPT.
Step 2 Run the eNodeB MML command ADD DEVIP to set the device IP address of the Ethernet port
on the LMPT that is used for interconnecting the LMPT to the WMPT. In this step, ensure that
IP addresses of two ports used for interconnecting the eNodeB to the NodeB are on the same
network segment.
Issue 01 (2014-04-30)
86
SingleRAN
Common Transmission Feature Parameter Description
ADD DEVIP: CN=0, SRN=1,
MASK="255.255.255.0";
//Set the IP address of
for interconnecting the
same network segment as
7 Engineering Guidelines
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",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1", PREF=60;
//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 IPRT: RTIDX=1, CN=0, SRN=1, SN=7, SBT=BASE_BOARD, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1", PREF=60;
//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 IPRT: RTIDX=2, CN=0, SRN=1, SN=7, SBT=BASE_BOARD, DSTIP="30.30.30.188",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="60.60.60.188", PREF=60;
//Add a route from the BSC to the BTS.
Step 6 (Optional)Run the eNodeB MML command SET DHCPRELAYSWITCH to enable DHCP
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.
SET DHCPRELAYSWITCH: ES=ENABLE;
//Enable DHCP relay 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 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 8 (Optional) Configure VLAN. There are two methods of configuring differentiated VLAN data
for the BTS, NodeB, and eNodeB:
l Method 1 (Recommended): Configure differentiated next-hop addresses. Specifically, the
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
ADD VLANMAP: NEXTHOPIP="20.20.20.101", MASK="255.255.255.0",
VLANMODE=SINGLEVLAN, VLANID=22, SETPRIO=DISABLE;
ADD VLANMAP: NEXTHOPIP="20.20.20.201", MASK="255.255.255.0",
VLANMODE=SINGLEVLAN, VLANID=33, SETPRIO=DISABLE;
l Method 2 (Not recommended): Configure differentiated DSCP values. This method requires
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.
2.
----End
l
Issue 01 (2014-04-30)
88
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 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
address can be pinged, the transmission link is normal.
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="20.20.20.1",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
----End
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 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
address can be pinged, the transmission link is normal.
PING: CN=0, SRN=0, SN=7, SRCIP="60.60.60.188", DSTIP="20.20.20.1",
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 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.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="30.30.30.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
Step 2 Run the RNC MML command PING IP to ping the IP address of the WMPT.
PING IP: SRN=1, SN=16, SIPADDR="11.11.11.11", DESTIP="60.60.60.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End
Deployment objective
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
Issue 01 (2014-04-30)
90
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
21.21.21.254/24
20.20.20.1/24
20.20.20.188/24
OM IP address of the
eNodeB
31.31.31.188/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
91
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
60.60.60.60/24
40.40.40.40/24
50.50.50.50/24
35.35.35.188/24
GSM: communication IP
address of the BTS. This is a
logical IP address and is
configured on the BTS main
control board.
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.
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSTUNNEL
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
SRCCN
SRCSRN
SRCSN
TN
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
BTSDEVIP
Issue 01 (2014-04-30)
92
SingleRAN
Common Transmission Feature Parameter Description
MO
BTSIP
BTSIPRT
BTSESN
Issue 01 (2014-04-30)
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Port No.
PN
Port No.
CN
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
BTSMUTIP
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
CN
SRN
SN
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
IDTYPE
BTS Index
BTSID
BTS Index
93
SingleRAN
Common Transmission Feature Parameter Description
MO
IPRT
7 Engineering Guidelines
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
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
SCN
SSRN
SSN
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
Common Transmission Feature Parameter Description
MO
7 Engineering Guidelines
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
ES
VLANMAP
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
SETPRIO
VLAN Priority
VLANPRIO
VLAN Priority
VLANGROUPNO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
VLANCLASS
7.9.3 Precautions
None
95
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
96
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Documentation. In addition to configuration steps described in 3900 Series Base Station Initial
Configuration Guide, perform the following steps:
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.
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;
//Add an uplink route from the BTS to the BSC through the eNodeB.
Step 4 Run the eNodeB MML command ADD IPRT to add a downlink route from the BSC to the 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.
Step 5 (Optional)Run the eNodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
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, DHCP relay needs to be enabled for the
eNodeB.
SET DHCPRELAYSWITCH: ES=ENABLE;
//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 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
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 eNodeB:
Issue 01 (2014-04-30)
97
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
2.
----End
l
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 to the eNodeB 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.
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="50.50.50.50",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
----End
Issue 01 (2014-04-30)
98
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
GSM Side
After the configuration file is delivered to the BTS and activated, perform the following step on
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 GTMUb.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="35.35.35.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End
Deployment objective
Figure 7-15 shows the main-control-board-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 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
21.21.21.254/24
11.11.11./24
20.20.20.1/24
30.30.30.1/24
100
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
Signaling/service IP address
of the NodeB
32.32.32.1/24
20.20.20.188/24
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24
35.35.35.188/24
GSM: communication IP
address of the BTS.
This is a logical IP address
and is configured on the BTS
main control board.
BTS 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 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
SRCCN
SRCSRN
SRCSN
TN
101
SingleRAN
Common Transmission Feature Parameter Description
MO
BTSDEVIP
BTSIP
BTSIPRT
Issue 01 (2014-04-30)
7 Engineering Guidelines
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.
CN
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
BTSMUTIP
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
Common Transmission Feature Parameter Description
MO
BTSESN
IPRT
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CN
SRN
SN
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
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
ID
CME Parameter
Name
TUNNEL
SCN
SSRN
Source Subrack
No.
SSN
Tunnel No.
TUNNELID
Tunnel No.
DCN
Destination
Cabinet No.
DSRN
Destination
Subrack No.
DSN
Destination Slot
No.
103
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MO
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
ES
DHCP Switch
VLANMA
P
VLANGROUPNO
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
SETPRIO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLANCLA
SS
7.10.3 Precautions
None
Issue 01 (2014-04-30)
104
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 1 Run the BSC MML command ADD BTSTUNNEL to add a tunnel from the GTMUb to the
UMPT_U.
ADD BTSTUNNEL: IDTYPE=BYID, BTSID=10, SRCCN=0, SRCSRN=0, SRCSN=6, TN=0, DSTCN=0,
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.
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 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
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, set
BTSCOMTYPE to an appropriate value based on individual needs.
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=0;
Issue 01 (2014-04-30)
105
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="32.32.32.1",
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 TUNNEL: SSN=7, DSN=6, TUNNELTYPE=DL;
//Add a tunnel from the UMPT_U in slot 7 to the GTMUb in slot 6.
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, 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",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a downlink route from the BSC to the BTS through the NodeB for the UMPT_U in
slot 7.
Step 5 (Optional)Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
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.
Issue 01 (2014-04-30)
106
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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, if the BTS is deployed using DHCP,
the NodeB needs to work as the relay. Therefore, the IP address of the DHCP server needs to
be added on the NodeB. For the 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 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 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
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 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.
2.
Run the NodeB MML command ADD VLANMAP to configure the DSCP value.
ADD VLANMAP: NEXTHOPIP="20.20.20.1", MASK=255.255.255.255, VLANMODE=
VLANGROUP, VLANGROUPNO=1, SETPRIO=DISABLE;
//Configure the mapping between a VLAN group and the next hop.
----End
l
Issue 01 (2014-04-30)
107
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 to the NodeB is normal:
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.
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="15.15.15.15",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
----End
GSM Side
After the configuration file is delivered to the BTS and activated, perform the following step on
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 GTMUb.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="35.35.35.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End
Deployment objective
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
109
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
21.21.21.254/24
11.11.11./24
20.20.20.1/24
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
20.20.20.188/24
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24
35.35.35.188/24
GSM: communication IP
address of the BTS.
This is a logical IP address
and is configured on the BTS
main control board.
BTS ESN
Issue 01 (2014-04-30)
abcdefghijklmn
110
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 UTRPc through the backplane.
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSTUNNEL
Index Type
IDTYPE
Index Type
BTS Index
BTSID
BTS Index
SRCCN
SRCSRN
SRCSN
TN
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.
CN
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
Common Transmission Feature Parameter Description
MO
BTSIPRT
BTSESN
IPRT
Issue 01 (2014-04-30)
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BSC IP
BSCIP
BSC IP
BTSMUTIP
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
CN
SRN
SN
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
SCN
SSRN
SSN
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
ES
DHCP Switch
TUNNEL
IPRT
Issue 01 (2014-04-30)
113
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
VLANMAP
VLANGROUPNO
Next Hop IP
NEXTHOPIP
Next Hop IP
VLAN Mode
MASK
VLAN Mode
VLAN ID
VLANMODE
VLAN ID
VLANID
SETPRIO
Traffic Type
VLANGROUPNO
Traffic Type
TRAFFIC
VLAN ID
SRVPRIO
VLAN ID
VLANCLASS
7.11.3 Precautions
None
Cables to the UTRPc on the UG multimode base station side are used to connect to the
transport network.
Step 1 Run the BSC MML command ADD BTSTUNNEL to add a tunnel from the GTMUb to the
UTRPc.
ADD BTSTUNNEL: IDTYPE=BYID, BTSID=10, SRCCN=0, SRCSRN=0, SRCSN=6, TN=0, DSTCN=0,
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.
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 NodeB is the OM channel IP address of the NodeB
Issue 01 (2014-04-30)
114
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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, set
BTSCOMTYPE to an appropriate value based on individual needs.
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=0;
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
Step 2 Run the SET ETHPORT command to set the Ethernet port attribute for the UTRPc.
Issue 01 (2014-04-30)
115
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 3 Run the NodeB MML command ADD DEVIP to add IP addresses for the NodeB.
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.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="32.32.32.1",
MASK="255.255.255.0";
//Add a signaling/service IP address for the NodeB.
Step 4 Run the NodeB MML command ADD TUNNEL to add a tunnel from the UTRPc to the
GTMUb.
ADD TUNNEL: SSN=4, DSN=6, TUNNELTYPE=DL;
//Add a tunnel from the UTRPc in slot 4 to the GTMUb in slot 6.
Step 5 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, CN=0, SN=4, SBT=ETH_COVERBOARD, 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 UTRPc in slot 4.
Step 6 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 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 IPRT: RTIDX=1, CN=0, SN=4, 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 NodeB for the UTRPc in
slot 4.
Step 7 (Optional)Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
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 8 (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, if the BTS is deployed using DHCP,
the NodeB needs to work as the relay. Therefore, the IP address of the DHCP server needs to
be added on the NodeB. For the 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 9 (Optional) Configure VLAN. There are two methods of configuring differentiated VLAN data
for the BTS and NodeB:
----End
Issue 01 (2014-04-30)
116
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
2.
Run the NodeB MML command ADD VLANMAP to configure the DSCP value.
ADD VLANMAP: NEXTHOPIP="20.20.20.1", MASK=255.255.255.255, VLANMODE=
VLANGROUP, VLANGROUPNO=1, SETPRIO=DISABLE;
//Configure the mapping between a VLAN group and the next hop.
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 to the NodeB is normal:
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.
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="15.15.15.15",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
----End
GSM Side
After the configuration file is delivered to the BTS and activated, perform the following step on
the BSC side to verify whether the transmission link between the BSC and the BTS is normal:
Issue 01 (2014-04-30)
117
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 1 Run the BSC MML command PING IP to ping the IP address of the GTMUb.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="35.35.35.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End
Deployment objective
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.
Figure 7-19 Main-control-board-based IP co-transmission through backplane
interconnection on the separate-MPT UL multimode base station side
Issue 01 (2014-04-30)
118
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
Issue 01 (2014-04-30)
Item
Instance
Remarks
15.15.15.15/32
119
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
11.11.11.11/24
11.11.11.254/24
20.20.20.1/24
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
OM IP address of the
eNodeB
31.31.31.188/24
20.20.20.188/24
40.40.40.40/24
50.50.50.50/24
60.60.60.60/24
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
SCN
SSRN
SSN
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
ES
DHCP Switch
VLANMAP
VLANGROUPNO
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
Common Transmission Feature Parameter Description
MO
VLANCLASS
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
SETPRIO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
SCN
SSRN
SSN
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
Common Transmission Feature Parameter Description
MO
RSCGRP
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
PT
PN
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
Common Transmission Feature Parameter Description
MO
IPPath
OMCH
7 Engineering Guidelines
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
TXPBS
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="32.32.32.1",
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
LMPT/UMPT_L.
ADD TUNNEL: SSN=7, DSN=6, TUNNELTYPE=DL;
//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 IPRT: RTIDX=0, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="40.40.40.40",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the eNodeB to the MME through the NodeB for the UMPT_U in slot
7.
ADD IPRT: RTIDX=1, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the eNodeB to the S-GW through the NodeB for the UMPT_U in slot
7.
ADD IPRT: RTIDX=2, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
ADD IPRT: RTIDX=3, SN=7, SBT=BACK_BOARD, DSTIP="31.31.31.188",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=0;
ADD IPRT: RTIDX=4, SN=7, SBT=BACK_BOARD, DSTIP="33.33.33.188",
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.
Step 5 (Optional)Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP
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.
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.
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, 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 DHCPSVRIP: DHCPSVRIP="60.60.60.60";
//Add the IP address of the DHCP server for the eNodeB.
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 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
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 DSCP values. This method requires
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
Feature Parameter Description.
1.
Issue 01 (2014-04-30)
126
SingleRAN
Common Transmission Feature Parameter Description
DHCP packets is fixed at 0.
data is configured, set the
set to 0, DHCP packets sent
In addition, set TRAFFIC to
2.
7 Engineering Guidelines
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.
Run the NodeB MML command ADD VLANMAP to configure the DSCP value.
ADD VLANMAP: NEXTHOPIP="20.20.20.1", MASK=255.255.255.255, VLANMODE=
VLANGROUP, VLANGROUPNO=1, SETPRIO=DISABLE;
//Configure the mapping between a VLAN group and the next hop.
----End
l
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",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eNodeB to the MME.
ADD IPRT: RTIDX=1, SRN=0, SN=6, SBT=BACK_BOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eNodeB to the S-GW.
ADD IPRT: RTIDX=2, SRN=0, SN=6, SBT=BACK_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
Issue 01 (2014-04-30)
127
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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 to the NodeB is normal:
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.
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="15.15.15.15",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
----End
LTE Side
After the configuration file is delivered to the eNodeB and activated, perform the following step
on the eNodeB side to verify whether the transmission link to the eNodeB 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.
PING: CN=0, SRN=0, SN=6, SRCIP="33.33.33.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
Issue 01 (2014-04-30)
128
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
----End
Deployment objective
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.
Issue 01 (2014-04-30)
129
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
Issue 01 (2014-04-30)
Item
Instance
Remarks
15.15.15.15/32
130
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
11.11.11.11/24
11.11.11.254/24
20.20.20.1/24
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
OM IP address of the
eNodeB
31.31.31.188/24
20.20.20.188/24
40.40.40.40/24
50.50.50.50/24
60.60.60.60/24
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
SCN
SSRN
SSN
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
ES
DHCP Switch
TUNNEL
IPRT
Issue 01 (2014-04-30)
132
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
VLANMAP
VLANGROUPNO
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
SETPRIO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLANCLASS
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
SCN
SSRN
SSN
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
Common Transmission Feature Parameter Description
MO
IPRT
RSCGRP
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
PT
PN
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
Common Transmission Feature Parameter Description
MO
IPPath
OMCH
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
TXPBS
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
Common Transmission Feature Parameter Description
MO
7 Engineering Guidelines
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
Cables to the UTRPc on the LU multimode base station side are used to connect to the
transport network.
Step 2 Run the SET ETHPORT command to set the Ethernet port attribute for the UTRPc.
SET ETHPORT: CN=0, SRN=0, SN=4, SBT=ETH_COVERBOARD, PN=1, 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.
Step 3 Run the NodeB MML command ADD DEVIP to add IP addresses for the NodeB.
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";
Issue 01 (2014-04-30)
136
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 IPRT: RTIDX=0, CN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="40.40.40.40",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the eNodeB to the MME through the NodeB for the UTRPc in slot
4.
ADD IPRT: RTIDX=1, CN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the eNodeB to the S-GW through the NodeB for the UTRPc in slot
4.
ADD IPRT: RTIDX=2, CN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the eNodeB to the U2000 through the NodeB for the UTRPc in slot
4. Skip this step if the UMPT_U has already been configured with a route to the
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 IPRT: RTIDX=3, SN=4, SBT=BACK_BOARD, DSTIP="31.31.31.188",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=0;
ADD IPRT: RTIDX=4, SN=4, SBT=BACK_BOARD, DSTIP="33.33.33.188",
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 UTRPc
in slot 4.
Step 7 (Optional)Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP
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.
SET DHCPRELAYSWITCH: ES=ENABLE;
//Enable DHCP relay for the NodeB.
Step 8 (Optional)Run the NodeB MML command ADD DHCPSVRIP to add the IP address of the
DHCP server.
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, the IP address of the DHCP server
Issue 01 (2014-04-30)
137
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 DHCPSVRIP: DHCPSVRIP="60.60.60.60";
//Add the IP address of the DHCP server for the eNodeB.
Step 9 (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 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
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 DSCP values. This method requires
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
Feature Parameter Description.
1.
2.
Run the NodeB MML command ADD VLANMAP to configure the DSCP value.
ADD VLANMAP: NEXTHOPIP="20.20.20.1", MASK=255.255.255.255, VLANMODE=
VLANGROUP, VLANGROUPNO=1, SETPRIO=DISABLE;
//Configure the mapping between a VLAN group and the next hop.
----End
l
138
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 1 Run the eNodeB MML command ADD TUNNEL to add a tunnel from the UMPT_L to the
UTRPc.
ADD TUNNEL: SSN=6, DSN=4;
//Add a tunnel from the UMPT_L in slot 6 to the UTRPc in slot 4.
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",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eNodeB to the MME.
ADD IPRT: RTIDX=1, SRN=0, SN=6, SBT=BACK_BOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eNodeB to the S-GW.
ADD IPRT: RTIDX=2, SRN=0, SN=6, SBT=BACK_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//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
Issue 01 (2014-04-30)
139
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 to the NodeB is normal:
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.
PING: CN=0, SRN=0, SN=4, SRCIP="20.20.20.188", DSTIP="15.15.15.15",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
----End
LTE Side
After the configuration file is delivered to the eNodeB and activated, perform the following step
on the eNodeB side to verify whether the transmission link to the eNodeB 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.
PING: CN=0, SRN=0, SN=6, SRCIP="33.33.33.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
PING: CN=0, SRN=0, SN=6, SRCIP="33.33.33.188", DSTIP="50.50.50.50",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
----End
Deployment objective
Figure 7-23 shows the main-control-board-based IP co-transmission through backplane
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
Issue 01 (2014-04-30)
141
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Instance
Remarks
15.15.15.15/32
11.11.11.11/24
11.11.11.254/24
20.20.20.1/24
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
Issue 01 (2014-04-30)
142
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
Signaling/service IP address
of the eNodeB
33.33.33.188/24
OM IP address of the
eNodeB
31.31.31.188/24
20.20.20.188/24
40.40.40.40/24
50.50.50.50/24
60.60.60.60/24
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
SCN
SSRN
SSN
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
Common Transmission Feature Parameter Description
MO
IPRT
RSCGRP
IPPATH
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
PT
Carrier Type
PN
Link 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
IP Path ID
PATHID
IP Path ID
144
SingleRAN
Common Transmission Feature Parameter Description
MO
OMCH
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
SCN
SSRN
SSN
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
DHCPRELAYSWI
TCH
ES
VLANMAP
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
SETPRIO
VLAN Priority
VLANPRIO
VLAN Priority
VLANGROUPNO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
VLANCLASS
7.14.3 Precautions
None
147
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Documentation. In addition to configuration steps described in 3900 Series Base Station Initial
Configuration Guide, perform the following steps:
l
Step 1 Run the NodeB MML command ADD TUNNEL to add a tunnel from the UMPT_U to the
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.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="32.32.32.1",
MASK="255.255.255.0";
//Add a signaling/service IP address for the NodeB.
Step 3 Run the NodeB MML command ADD IPRT to add a route from the NodeB to the RNC/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, SN=7, SBT=BACK_BOARD, DSTIP="15.15.15.15",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the NodeB to the RNC.
ADD IPRT: RTIDX=1, SN=7, SBT=BACK_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//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;
//When adding a transmission resource group, set SBT to BACK_BOARD and PT to
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;
//When adding an IP path, set SBT to BACK_BOARD and PT to TUNNEL.
Step 6 Run the NodeB MML command ADD OMCH to add an O&M channel.
ADD OMCH: IP="30.30.30.1", MASK="255.255.255.0", PEERIP="60.60.60.60",
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
On the CME, set the parameters listed in the Data Preparation on the UMTS Side section.
For instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.
Step 1 Run the eNodeB MML command ADD TUNNEL to add a tunnel from the UMPT_L to the
UMPT_U.
Step 2 Run the eNodeB MML command ADD DEVIP to add IP addresses for the eNodeB.
ADD DEVIP: CN=0, SRN=0, SN=6, 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_L in slot 6.
ADD DEVIP: SN=6, 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 UMPT_L in slot 6.
ADD TUNNEL: SSN=6, DSN=7, TUNNELTYPE=DL;
//Add a tunnel from the UMPT_L in slot 6 to the UMPT_U in slot 7.
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.
ADD IPRT: RTIDX=0, CN=0, SN=6, SBT= BASE_BOARD, DSTIP="15.15.15.15",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//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 IPRT: RTIDX=1, CN=0, SN=6, SBT=BACK_BOARD, DSTIP="30.30.30.1",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a downlink route from the U2000 to the NodeB through the eNodeB.
ADD IPRT: RTIDX=2, CN=0, SN=6, SBT=BACK_BOARD, DSTIP="32.32.32.1",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a downlink route from the RNC to the NodeB through the eNodeB.
Step 5 (Optional)Run the eNodeB MML command SET DHCPRELAYSWITCH to enable DHCP
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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, 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.
ADD DHCPSVRIP: DHCPSVRIP="60.60.60.60";
//Add the IP address of the DHCP server for the NodeB.
Step 7 (Optional) Configure VLAN. There are two methods of configuring differentiated VLAN data
for the NodeB and eNodeB:
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. 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.
ADD VLANMAP: NEXTHOPIP="20.20.20.101", MASK="255.255.255.0",
VLANMODE=SINGLEVLAN, VLANID=22, SETPRIO=DISABLE;
l Method 2 (Not recommended): Configure differentiated DSCP values. This method 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.
----End
l
Issue 01 (2014-04-30)
150
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 to the eNodeB 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.
PING: CN=0, SRN=0, SN=6, SRCIP="20.20.20.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
PING: CN=0, SRN=0, SN=6, SRCIP="20.20.20.188", DSTIP="50.50.50.50",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
----End
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 to the NodeB is normal:
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.
PING: CN=0, SRN=0, SN=7, SRCIP="32.32.32.1", DSTIP="15.15.15.15",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
----End
Deployment objective
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
152
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
IP Address
Remarks
10.10.10.10/32
21.21.21.1/24
15.15.15.15/32
11.11.11.11/24
11.11.11.254/24
21.21.21.254/24
20.20.20.1/24
153
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
IP Address
Remarks
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
20.20.20.188/24
40.40.40.40/24
50.50.50.50/24
60.60.60.60/24
31.31.31.188/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
35.35.35.188/24
GSM: communication IP
address of the BTS.
This is a logical IP address
and is configured on the BTS
main control board.
BTS 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 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
UPCN
UPSRN
UPSN
UPPT
IDTYPE
BTS Index
BTSID
BTS Index
SRCCN
SRCSRN
SRCSN
TN
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
BTSCTRLLNK
BTSTUNNEL
Issue 01 (2014-04-30)
155
SingleRAN
Common Transmission Feature Parameter Description
MO
BTSDEVIP
BTSIP
BTSIPRT
Issue 01 (2014-04-30)
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
DSTSN
IDTYPE
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
Port No.
PN
Port No.
CN
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
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
BTSMUTIP
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
CN
SRN
SN
156
SingleRAN
Common Transmission Feature Parameter Description
MO
BTSESN
IPRT
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
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
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
LN
CN
SRN
SN
UPCN
UPSRN
UPSN
CTRLLNK
Issue 01 (2014-04-30)
157
SingleRAN
Common Transmission Feature Parameter Description
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
UPPT
SCN
SSRN
SSN
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
ES
DHCP Switch
VLANMAP
VLANGROUPNO
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)
7 Engineering Guidelines
158
SingleRAN
Common Transmission Feature Parameter Description
MO
VLANCLASS
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
SETPRIO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CTRLLNK
LN
CN
SRN
SN
UPCN
UPSRN
UPSN
UPPT
SCN
SSRN
SSN
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
Common Transmission Feature Parameter Description
MO
IPRT
RSCGRP
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
PT
PN
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
Common Transmission Feature Parameter Description
MO
IPPath
OMCH
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
TXPBS
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
Common Transmission Feature Parameter Description
MO
7 Engineering Guidelines
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
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.
Step 2 Run the BSC MML command ADD BTSTUNNEL to add a tunnel from the GTMUb to the
UTRPc.
ADD BTSTUNNEL: IDTYPE=BYID, BTSID=10, SRCCN=0, SRCSRN=0, SRCSN=6, TN=0, DSTCN=0,
DSTSRN=0, DSTSN=4;
Issue 01 (2014-04-30)
162
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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, set
BTSCOMTYPE to an appropriate value based on individual needs.
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 3.
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=0;
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.
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.
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;
----End
l
163
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
NOTE
In this scenario, the eNodeB uses the CI interface for communication. Therefore, Ethernet ports are not
required.
Step 1 Run the eNodeB MML command ADD TUNNEL to add a tunnel from the UMPT_L to the
UTRPc.
ADD TUNNEL: SSRN=1, SSN=7, DSN=4, TUNNELTYPE=UL;
//Add a tunnel from the UMPT_L of the eNodeB in slot 7 of subrack 1 to the UTRPc in
slot 4 of subrack 0.
Step 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=1, SN=7, 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 1,
SN to 7, 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 2.
ADD IPRT: RTIDX=0, SRN=1, SN=7, SBT=BACK_BOARD, DSTIP="40.40.40.40",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eNodeB to the MME.
ADD IPRT: RTIDX=1, SRN=1, SN=7, SBT=BACK_BOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eNodeB to the S-GW.
ADD IPRT: RTIDX=2, SRN=1, SN=7, SBT=BACK_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//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=1, SN=7, BEAR=IP, SBT=BACK_BOARD, PT=TUNNEL, RSCGRPID=0, RU=KBPS,
TXBW=3000, RXBW=3000, TXCBS=4000, TXEBS=4000, TXCIR=4000, RXCIR=4000, TXPIR=4000,
RXPIR=4000, TXPBS=4000;
//When adding a transmission resource group, set SBT to BACK_BOARD and PT to
TUNNEL.
Step 5 Run the eNodeB MML command ADD IPPATH to add an IP path.
ADD IPPATH: PATHID=0, SRN=1, SN=7, SBT=BACK_BOARD, PT=TUNNEL, PN=0,
JNRSCGRP=DISABLE, LOCALIP="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=1, SN=7, SBT=BACK_BOARD, BRT=NO;
//When adding an OM channel, set SBT to BACK_BOARD.
----End
Issue 01 (2014-04-30)
164
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 1 Run the NodeB MML command ADD BRD to add a UTRPc.
ADD BRD: CN=0, SRN=0, SN=4, BT=UTRP, SBT=UTRPc;
//Add a UTRPc in slot 4.
Step 2 Run the SET ETHPORT command to set the Ethernet port attribute for the UTRPc.
SET ETHPORT: CN=0, SRN=0, SN=4, SBT=ETH_COVERBOARD, PN=1, SPEED=AUTO, DUPLEX=AUTO;
//Set parameters related to Ethernet port 1 on the UTRPc in slot 0. Both data rate
and duplex mode are set to auto-negotiation.
Step 3 Run the NodeB MML command ADD DEVIP to add IP addresses for the NodeB.
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.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="32.32.32.1",
MASK="255.255.255.0";
//Add a signaling/service IP address for the NodeB.
Step 4 Run the NodeB MML command ADD TUNNEL to add tunnels from the UTRPc to the GTMUb
and UMPT_L.
ADD TUNNEL: SSN=4, DSN=6, TUNNELTYPE=DL;
//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.
Step 5 Run the NodeB MML command ADD IPRT to add an uplink route from the BTS to the BSC
through the NodeB and an uplink route from the eNodeB to the MME/S-GW/U2000 through
the NodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP to the IP address of the
router that is directly connected to the NodeB.
ADD IPRT: RTIDX=0, CN=0, SN=4, SBT=ETH_COVERBOARD, 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 UTRPc in slot 4.
ADD IPRT: RTIDX=1, CN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="40.40.40.40",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the eNodeB to the MME through the NodeB for the UTRPc in slot
4.
ADD IPRT: RTIDX=2, CN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the eNodeB to the S-GW through the NodeB for the UTRPc in slot
4.
ADD IPRT: RTIDX=3, CN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
Issue 01 (2014-04-30)
165
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
//Add a route from the eNodeB to the U2000 through the NodeB for the UTRPc in slot
4. Skip this step if the UMPT_U has already been configured with a route to the
U2000.
Step 6 Run the NodeB MML command ADD IPRT to add a downlink route from the BSC to the BTS
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 IPRT: RTIDX=4, CN=0, SN=4, 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 NodeB for the UTRPc in
slot 4.
ADD IPRT: RTIDX=5, SN=4, SBT=BACK_BOARD, DSTIP="31.31.31.188",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
ADD IPRT: RTIDX=6, SN=4, SBT=BACK_BOARD, DSTIP="33.33.33.188",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
ADD IPRT: RTIDX=7, SN=4, SBT=BACK_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
//Add a downlink route from the MME/S-GW/U2000 to the eNodeB through the NodeB for
the UTRPc in slot 4.
Step 7 (Optional)Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP
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.
SET DHCPRELAYSWITCH: ES=ENABLE;
//Enable DHCP relay for the NodeB.
Step 8 (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, 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.
ADD DHCPSVRIP: DHCPSVRIP="60.60.60.60";
//Add the IP address of the DHCP server for the eNodeB.
ADD DHCPSVRIP: DHCPSVRIP="21.21.21.1";
//Add the IP address of the DHCP server for the BTS.
Step 9 (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 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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=32, SETPRIO=DISABLE;
ADD VLANMAP: NEXTHOPIP="20.20.20.201", MASK=255.255.255.255,
VLANMODE=SINGLEVLAN, VLANID=32, SETPRIO=DISABLE;
l Method 2 (Not recommended): Configure differentiated DSCP values. This method requires
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.
2.
----End
l
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 RNC is
normal:
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.
Issue 01 (2014-04-30)
167
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
----End
GSM Side
After the configuration file is delivered to the BTS and activated, perform the following step on
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 GTMUb.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="35.35.35.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End
LTE Side
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 between the eNodeB and the MME/S-GW is normal.
PING: CN=0, SRN=1, SN=7, SRCIP="33.33.33.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
PING: CN=0, SRN=1, SN=7, SRCIP="33.33.33.188", DSTIP="50.50.50.50",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
----End
Deployment objective
Figure 7-27 shows the main-control-board-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 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
169
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
IP Address
Remarks
10.10.10.10/32
21.21.21.1/24
15.15.15.15/32
11.11.11.11/24
11.11.11.254/24
171
SingleRAN
Common Transmission Feature Parameter Description
Issue 01 (2014-04-30)
7 Engineering Guidelines
Item
IP Address
Remarks
21.21.21.254/24
20.20.20.1/24
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
20.20.20.188/24
40.40.40.40/24
50.50.50.50/24
60.60.60.60/24
OM IP address of the
eNodeB
31.31.31.188/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
35.35.35.188/24
GSM: communication IP
address of the BTS. This is a
logical IP address and is
configured on the BTS main
control board.
BTS ESN
abcdefghijklmn
172
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 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.
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.
UPCN
UPSRN
UPSN
UPPT
IDTYPE
BTS Index
BTSID
BTS Index
SRCCN
BTSCTRLLNK
BTSTUNNEL
Issue 01 (2014-04-30)
173
SingleRAN
Common Transmission Feature Parameter Description
MO
BTSDEVIP
BTSIP
BTSIPRT
Issue 01 (2014-04-30)
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
SRCSRN
SRCSN
TN
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
DSTSN
IDTYPE
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
Port No.
PN
Port No.
CN
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
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
BTSMUTIP
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
Route Index
RTIDX
Route Index
Destination IP
Address
DSTIP
Destination IP
Address
174
SingleRAN
Common Transmission Feature Parameter Description
MO
BTSESN
IPRT
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Destination Address
Mask
DSTMASK
Destination Address
Mask
Route Type
RTTYPE
Route Type
CN
SRN
SN
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
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
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
LN
CN
CTRLLNK
Issue 01 (2014-04-30)
175
SingleRAN
Common Transmission Feature Parameter Description
MO
TUNNEL
IPRT
DHCPSVRIP
Issue 01 (2014-04-30)
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
SRN
SN
UPCN
Upper Subrack
No.
UPSRN
UPSN
UPPT
Source Cabinet
No.
SCN
Source Subrack
No.
SSRN
SSN
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
DHCPRELAYSWITC
H
DHCP Relay
Switch
ES
DHCP Switch
VLANMAP
VLANGROUPNO
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
Set VLAN
Priority
SETPRIO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLANCLASS
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CTRLLNK
LN
CN
SRN
SN
UPCN
UPSRN
UPSN
UPPT
SCN
SSRN
SSN
Tunnel No.
TUNNELID
Tunnel No.
TUNNEL
Issue 01 (2014-04-30)
177
SingleRAN
Common Transmission Feature Parameter Description
MO
DEVIP
IPRT
RSCGRP
Issue 01 (2014-04-30)
7 Engineering Guidelines
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.
Transmission Resource
Group Bear Type
BEAR
Transmission
Resource Group
Bear Type
Subboard Type
SBT
Subboard Type
178
SingleRAN
Common Transmission Feature Parameter Description
MO
IPPath
Issue 01 (2014-04-30)
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
PT
PN
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
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
TXPBS
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
Common Transmission Feature Parameter Description
MO
OMCH
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
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.16.3 Precautions
None
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.
180
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 1 (UCIU+UMPT interconnection) Run the ADD BTSBRD command to add a UCIU.
ADD BTSBRD: IDTYPE=BYID, BTSID=10, CN=0, SRN=0, SN=0, BT=UCIU;
//Add a UCIU to slot 0.
Step 2 Run the 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,
SRN=1, SN=7, UPCN=0, UPSRN=0, UPSN=7, UPPT=8;
//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
Step 3 Run the BSC MML command ADD BTSTUNNEL to add a tunnel from the GTMUb to the
UMPT_U.
ADD BTSTUNNEL: IDTYPE=BYID, BTSID=10, SRCCN=0, SRCSRN=0, SRCSN=6, TN=0, DSTCN=0,
DSTSRN=0, DSTSN=7;
//Add a tunnel from the GTMUb in slot 6 to the UMPT_U in slot 7.
Step 4 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 5 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, set
BTSCOMTYPE to an appropriate value based on individual needs.
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 6 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 3.
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=0;
Step 7 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.
Issue 01 (2014-04-30)
181
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
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;
----End
l
In this scenario, the eNodeB uses the CI interface for communication. Therefore, Ethernet ports are not
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;
//Add a BBU interconnection control link between slot 7 of subrack 1 and slot 7 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.
Step 2 Run the eNodeB MML command ADD TUNNEL to add a tunnel from the UMPT_L to the
UMPT_U.
ADD TUNNEL: SSRN=1, SSN=7, DSN=7,TUNNELTYPE=UL;
//Add a tunnel from the UMPT_L of the eNodeB in slot 7 of subrack 1 to the UMPT_U
in slot 7 of subrack 0.
Step 3 Run the eNodeB MML command ADD DEVIP to set the IP address of the eNodeB.
Unlike non-co-transmission scenarios, this scenario requires that the eNodeB uses the logical
IP address. Specifically, set PT to LOOPINT. In non-co-transmission scenarios, set PT based
on individual needs.
Issue 01 (2014-04-30)
182
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 4 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 2.
ADD IPRT: RTIDX=0, SRN=1, SN=7, SBT=BACK_BOARD, DSTIP="40.40.40.40",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eNodeB to the MME.
ADD IPRT: RTIDX=1, SRN=1, SN=7, SBT=BACK_BOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eNodeB to the S-GW.
ADD IPRT: RTIDX=2, SRN=1, SN=7, SBT=BACK_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the eNodeB to the U2000.
Step 5 (Optional) Run the eNodeB MML command ADD RSCGRP to add a transmission resource
group.
ADD RSCGRP: SRN=1, SN=7, BEAR=IP, SBT=BACK_BOARD, PT=TUNNEL, RSCGRPID=0, RU=KBPS,
TXBW=3000, RXBW=3000, TXCBS=4000, TXEBS=4000, TXCIR=4000, RXCIR=4000, TXPIR=4000,
RXPIR=4000, TXPBS=4000;
//When adding a transmission resource group, set SBT to BACK_BOARD and PT to
TUNNEL.
Step 6 Run the eNodeB MML command ADD IPPATH to add an IP path.
ADD IPPATH: PATHID=0, SRN=1, SN=7, SBT=BACK_BOARD, PT=TUNNEL, PN=0,
JNRSCGRP=DISABLE, LOCALIP="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 7 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=1, SN=7, SBT=BACK_BOARD, BRT=NO;
//When adding an OM channel, set SBT to BACK_BOARD.
----End
l
183
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="32.32.32.1",
MASK="255.255.255.0";
//Add a signaling/service IP address for the NodeB.
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.
Step 3 Run the NodeB MML command ADD TUNNEL to add tunnels from the UMPT_U to the
GTMUb and UMPT_L.
ADD TUNNEL: SSN=7, DSN=6, TUNNELTYPE=DL;
//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.
Step 4 Run the NodeB MML command ADD IPRT to add an uplink route from the BTS to the BSC
through the NodeB and an uplink route from the eNodeB to the MME/S-GW/U2000 through
the NodeB. In this step, set RTTYPE to NEXTHOP and NEXTHOP to the IP address of the
router that is directly connected to the NodeB.
ADD 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.
ADD IPRT: RTIDX=1, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="40.40.40.40",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the eNodeB to the MME through the NodeB for the UMPT_U in slot
7.
ADD IPRT: RTIDX=2, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the eNodeB to the S-GW through the NodeB for the UMPT_U in slot
7.
ADD IPRT: RTIDX=3, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//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 5 Run the NodeB MML command ADD IPRT to add a downlink route from the BSC to the BTS
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
UMPT_U backplane, the downlink route from the BSC to the BTS through the NodeB and the
Issue 01 (2014-04-30)
184
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 IPRT: RTIDX=4, CN=0, SN=7, 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 NodeB for the UMPT_U in
slot 7.
ADD IPRT: RTIDX=5, SN=7, SBT=BACK_BOARD, DSTIP="31.31.31.188",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
ADD IPRT: RTIDX=6, SN=7, SBT=BACK_BOARD, DSTIP="33.33.33.188",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
ADD IPRT: RTIDX=7, SN=7, SBT=BACK_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
//Add a downlink route from the MME/S-GW/U2000 to the eNodeB through the NodeB for
the UMPT_U in slot 7.
Step 6 (Optional)Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP
relay.
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, DHCP relay needs to be enabled for the NodeB.
SET DHCPRELAYSWITCH: ES=ENABLE;
//Enable DHCP relay for the NodeB.
Step 7 (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. The DHCP server of the BTS is BSC, while the DHCP server of the eNodeB
is U2000.
ADD DHCPSVRIP: DHCPSVRIP="60.60.60.60";
//Add the IP address of the DHCP server for the eNodeB.
ADD DHCPSVRIP: DHCPSVRIP="10.10.10.10";
//Add the IP address of the DHCP server for the BTS.
Step 8 (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 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
ADD VLANMAP: NEXTHOPIP="20.20.20.101", MASK=255.255.255.255,
VLANMODE=SINGLEVLAN, VLANID=32, SETPRIO=DISABLE;
ADD VLANMAP: NEXTHOPIP="20.20.20.101", MASK=255.255.255.255,
VLANMODE=SINGLEVLAN, VLANID=32, SETPRIO=DISABLE;
l Method 2 (Not recommended): Configure differentiated DSCP values. This method requires
differentiated DSCP values for the BTS, eNodeB, and NodeB. For details about DSCP values
Issue 01 (2014-04-30)
185
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
for the BTS, NodeB, and eNodeB, see Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description.
1.
2.
----End
l
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 RNC is
normal:
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.
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="15.15.15.15",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
----End
GSM Side
After the configuration file is delivered to the BTS and activated, perform the following step on
the BSC side to verify whether the transmission link between the BSC and the BTS is normal:
Issue 01 (2014-04-30)
186
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 1 Run the BSC MML command PING IP to ping the IP address of the GTMUb.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="35.35.35.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End
LTE Side
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 between the eNodeB and the MME/S-GW is normal.
PING: CN=0, SRN=1, SN=7, SRCIP="33.33.33.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
PING: CN=0, SRN=1, SN=7, SRCIP="33.33.33.188", DSTIP="50.50.50.50",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
----End
Deployment objective
Figure 7-31 shows the network topologies before and after reconstruction.
Issue 01 (2014-04-30)
187
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
188
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
21.21.21.1/24
11.11.11.11/24
15.15.15.15/32
21.21.21.254/24
189
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
11.11.11.254/24
20.20.20.1/24
22.22.22.1/24
20.20.20.188/24
24.24.24.24/24
22.22.22.188/24
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 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.
Reconstruction Preparations
1.
2.
Issue 01 (2014-04-30)
190
SingleRAN
Common Transmission Feature Parameter Description
3.
7 Engineering Guidelines
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.
5.
Reconstruction Procedure
Step 1 Upgrade the software.
If the BTS software version does not meet the reconstruction requirements, upgrade the software
before reconstruction.
Step 2 Reconstruct hardware and modify data configurations.
1.
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
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.)
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 5 Execute the configuration scripts that are backed up before reconstruction. (CME: Script
Executor > Project > Load Project > Upload Project > Activate Project.)
----End
Deployment objective
Figure 7-33 shows the network topologies before and after reconstruction.
Figure 7-33 Network topologies before and after reconstruction
Issue 01 (2014-04-30)
193
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
Issue 01 (2014-04-30)
194
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Figure 7-34 Example of reconstruction from transmission through the main control 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)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
21.21.21.254/24
20.20.20.1/24
195
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
20.20.20.188/24
OM IP address of the
eNodeB
Signaling/service IP address
of the eNodeB
33.33.33.188/24
60.60.60.60/24
40.40.40.40/24
50.50.50.50/24
35.35.35.188/24
GSM: communication IP
address of the BTS. This is a
logical IP address and is
configured on the main
control board.
abcdefghijklmn
2.
Issue 01 (2014-04-30)
196
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
l Obtain the software versions of the MBSC, U2000, CME, and multimode base station.
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.
5.
6.
Reconstruction Procedure
Step 1 Upgrade the software.
If the BTS software version does not meet the reconstruction requirements, upgrade the software
before reconstruction.
Step 2 Reconstruct hardware and modify data configurations.
1.
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.
Deactivate the BTS on the BSC and prepare for scripts for BTS reconstruction to reactivate
the BTS.
Issue 01 (2014-04-30)
197
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
Step 3 Verify services after reconstruction. For details, see section 7.9.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.18.6
Rollback
l Restore the hardware configuration and network topology to those before reconstruction.
----End
7.18.4 Precautions
None
7.18.5 Reconfiguration
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 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.
IMP BTSIPRT: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=OUTIF, CN=0, SRN=0, SN=6, ITFType=TUNNEL,
IFNO=1;
Step 5 Run the BSC MML command ACT BTSIMPDATA to activate the IP rehoming data.
ACT BTSIMPDATA: IDTYPE=BYID, BTSID=10;
----End
Issue 01 (2014-04-30)
198
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.18.6 Rollback
Rollback on the LTE Side
Remove the eNodeB on the CME. (CME: Base Station > LTE > Right-click a site > Delete.)
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;
Step 5 Execute the configuration scripts that are backed up before reconstruction. (CME: Script
Executor> Project > Load Project > Activate Project.)
----End
Deployment objective
Figure 7-35 shows the network topologies before and after reconstruction.
Issue 01 (2014-04-30)
199
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
200
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Figure 7-36 Example of reconstruction from transmission through the main control 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)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
21.21.21.254/24
11.11.11./24
20.20.20.1/24
201
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
20.20.20.188/24
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24
35.35.35.188/24
GSM: communication IP
address of the BTS.
This is a logical IP address
and is configured on the BTS
main control board.
BTS ESN
abcdefghijklmn
2.
Issue 01 (2014-04-30)
202
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
5.
6.
Reconstruction Procedure
Step 1 Upgrade the software.
If the BTS software version does not meet the reconstruction requirements, upgrade the software
before reconstruction.
Step 2 Reconstruct hardware and modify data configurations.
1.
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.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
203
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
3.
Deactivate the BTS on the BSC and prepare for scripts for BTS reconstruction to reactivate
the BTS.
4.
Perform automatic NodeB deployment. For details about automatic deployment, see 3900
Series Base Station Commissioning Guide.
5.
Install and power on the GTMUb, and wait for BTS deployment.
Step 3 Verify services after reconstruction. For details, see section 7.10.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.19.6
Rollback.
l Restore the hardware configuration and network topology to those before reconstruction.
----End
7.19.4 Precautions
None
7.19.5 Reconfiguration
Reconfiguration on the UMTS Side
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.
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.
IMP BTSIPRT: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=OUTIF, CN=0, SRN=0, SN=6, ITFType=TUNNEL,
IFNO=1;
Step 5 Run the BSC MML command ACT BTSIMPDATA to activate the IP rehoming data.
ACT BTSIMPDATA: IDTYPE=BYID, BTSID=10;
----End
Issue 01 (2014-04-30)
204
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.19.6 Rollback
Rollback on the UMTS Side
Remove the NodeB on the CME. (CME: Base Station > UMTS > Right-click a site >
Delete.)
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;
Step 5 Execute the configuration scripts that are backed up before reconstruction. (CME: Script
Executor> Project > Load Project > Activate Project.)
----End
Deployment objective
Figure 7-37 shows the network topologies before and after reconstruction.
Issue 01 (2014-04-30)
205
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
15.15.15.15/32
11.11.11.11/24
207
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
11.11.11.254/24
20.20.20.1/24
30.30.30.1/24
Issue 01 (2014-04-30)
Signaling/service IP address
of the NodeB
32.32.32.1/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
OM IP address of the
eNodeB
31.31.31.188/24
20.20.20.188/24
40.40.40.40/24
50.50.50.50/24
60.60.60.60/24
208
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
2.
3.
Back up data.
l Back up the measurement results of original performance counters reported one week
before reconstruction.
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.
5.
6.
Issue 01 (2014-04-30)
209
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Reconstruction Procedure
Step 1 Reconstruct hardware.
1.
2.
3.
Perform automatic NodeB deployment. For details about automatic deployment, see 3900
Series Base Station Commissioning Guide.
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
Series Base Station Commissioning Guide.
Step 4 Verify services after reconstruction. For details, see section 7.12.6 Activation Observation.
Step 5 Perform the rollback operation if reconstruction fails.
l Restore the hardware configuration and network topology to those before reconstruction.
l Execute the rollback scripts. For details about the rollback scripts, see section 7.20.6
Rollback.
----End
7.20.4 Precautions
None
7.20.5 Reconfiguration
Reconfiguration on the UMTS Side
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.
7.20.6 Rollback
Rollback on the UMTS Side
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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 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.
Deployment objective
Figure 7-39 shows the network topologies before and after reconstruction.
Figure 7-39 Network topologies before and after reconstruction
l
Issue 01 (2014-04-30)
211
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
212
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
11.11.11.11/24
15.15.15.15/32
60.60.60.60/24
21.21.21.254/24
11.11.11.254/24
20.20.20.1/24
20.20.20.188/24
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
30.30.30.188/24
abcdefghijklmn
Issue 01 (2014-04-30)
213
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 to check the software version for a BTS.
Multimode base stations of V100R007C00 and later support IP-based co-transmission
through backplane interconnection.
2.
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.)
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.
5.
6.
Issue 01 (2014-04-30)
214
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Reconstruction Procedure
Step 1 Upgrade the software.
If the software version of the multimode base station does not meet the reconstruction
requirements, upgrade the software before reconstruction.
Step 2 Reconstruct hardware and modify data configurations.
1.
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.
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.
Step 4 Perform the rollback operation if reconstruction fails.
l Execute the rollback scripts. For details about the rollback scripts, see section 7.21.6
Rollback.
l Restore the hardware configuration and network topology to those before reconstruction.
----End
7.21.4 Precautions
None
Issue 01 (2014-04-30)
215
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.21.5 Reconfiguration
Reconfiguration on the UMTS Side
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.
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 UTRPc.
IMP BTSTUNNEL: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, SRCCN=0, SRCSRN=0, SRCSN=6,
TN=0, DSTCN=0, DSTSRN=0, DSTSN=4;
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.
IMP BTSIPRT: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=OUTIF, CN=0, SRN=0, SN=6, ITFType=TUNNEL,
IFNO=0;
Step 5 Run the BSC MML command ACT BTSIMPDATA to activate the IP rehoming data.
ACT BTSIMPDATA: IDTYPE=BYID, BTSID=10;
----End
7.21.6 Rollback
Rollback on the GSM Side
Step 1 Run the BSC MML command DEA BTS to deactivate the BTS.
DEA BTS: IDTYPE=BYID, BTSID=10;
Step 2 Run the BSC MML command RMV IPPATH to remove an 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.
RMV ADJNODE: ANI=1017;
//Remove an Abis adjacent node.
Step 4 Run the BSC MML command RMV BTS to remove the BTS.
RMV BTS: IDTYPE=BYID, BTSID=10;
Issue 01 (2014-04-30)
216
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 5 Execute the configuration scripts that are backed up before reconstruction.
----End
Deployment objective
Figure 7-41 shows the network topologies before and after reconstruction.
Issue 01 (2014-04-30)
217
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
219
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
220
SingleRAN
Common Transmission Feature Parameter Description
Issue 01 (2014-04-30)
7 Engineering Guidelines
Item
Instance
Remarks
21.21.21.1/24
21.21.21.254/24
15.15.15.15/32
11.11.11.11/24
11.11.11.254/24
40.40.40.40/24
50.50.50.50/24
60.60.60.60/24
20.20.20.1/24
20.20.20.188/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
30.30.30.1/24
OM IP address of the
eNodeB
31.31.31.188/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
221
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
35.35.35.188/24
GSM: communication IP
address of the BTS. This is a
logical IP address and is
configured on the main
control board.
abcdefghijklmn
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.
UPCN
UPSRN
UPSN
UPPT
BTSCTRLLNK
Issue 01 (2014-04-30)
222
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
LN
CN
SRN
SN
UPCN
UPSRN
UPSN
UPPT
SCN
SSRN
SSN
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
Common Transmission Feature Parameter Description
MO
7 Engineering Guidelines
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
ES
DHCP Switch
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CTRLLNK
LN
CN
SRN
SN
UPCN
UPSRN
UPSN
UPPT
SCN
SSRN
SSN
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
Common Transmission Feature Parameter Description
MO
IPRT
RSCGRP
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
PT
PN
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
Rate Unit
RU
Rate Unit
Tx Bandwidth
TXBW
Tx Bandwidth
225
SingleRAN
Common Transmission Feature Parameter Description
MO
IPPath
OMCH
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
TXPBS
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
Common Transmission Feature Parameter Description
MO
7 Engineering Guidelines
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
2.
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.)
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.
Issue 01 (2014-04-30)
227
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
l For details about reconfigurations on the LTE side, see Reconfiguration on the LTE
Side.
5.
6.
Reconstruction Procedure
Step 1 Upgrade the software.
If the software version of the multimode base station does not meet the reconstruction
requirements, upgrade the software before reconstruction.
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.
Step 5 Perform the rollback operation if reconstruction fails.
l Execute the rollback scripts. For details about the rollback scripts, see section 7.22.7
Rollback
l Restore the hardware configuration and network topology to those before reconstruction.
----End
7.22.4 Precautions
None
Issue 01 (2014-04-30)
228
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.22.5 Reconfiguration
Reconfiguration 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
Step 2 Run the BSC MML command ADD BTSCTRLLNK to add a BBU interconnection control link
between GSM and LTE.
ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=0, 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 7 of
subrack 0.
----End
l
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;
ADD IPRT: RTIDX=1, CN=0, SRN=0, SN=4, SBT=BACK_BOARD, DSTIP="33.33.33.188",
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",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
3.
Issue 01 (2014-04-30)
229
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 3 Run the NodeB MML command SET DHCPRELAYSWITCH to enable DHCP relay.
SET DHCPRELAYSWITCH: ES=ENABLE;
//Enable DHCP relay for the NodeB.
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.
ADD DHCPSVRIP: DHCPSVRIP="60.60.60.60";
----End
l
In this scenario, the eNodeB uses the CI interface for communication. Therefore, Ethernet ports are not
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
2.
3.
Step 5 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, CN=0, SRN=1, SN=7, SBT=BACK_BOARD, BRT=NO;
Step 6 (Optional) Run the eNodeB MML command ADD RSCGRP to add a transmission resource
group.
ADD RSCGRP: SRN=1, SN=7, BEAR=IP, SBT=BACK_BOARD, PT=TUNNEL, RSCGRPID=0, RU=KBPS,
TXBW=3000, RXBW=3000, TXCBS=4000, TXEBS=4000, TXCIR=4000, RXCIR=4000, TXPIR=4000,
RXPIR=4000, TXPBS=4000;
//Set parameters for a transmission resource group. In this step, set SBT to
BACK_BOARD and PT to TUNNEL.
Step 7 Run the eNodeB MML command ADD IPPATH to add an IP path.
ADD IPPATH: PATHID=0, SRN=1, SN=7, SBT=BACK_BOARD, PT=TUNNEL, PN=0,
JNRSCGRP=DISABLE, LOCALIP="33.33.33.188", PEERIP="50.50.50.50", PATHTYPE=ANY;
//Add an IP path. In this step, set SBT to BACK_BOARD and PT to TUNNEL.
----End
l
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.22.7 Rollback
Rollback on the GSM Side
Step 1 Run the RMV BTSCTRLLNK command to remove the BBU interconnection control link
between GSM and LTE.
RMV BTSCTRLLNK: IDTYPE=BYID, BTSID=0, LN=0;
//Remove the BBU interconnection control link between slot 7 of subrack 1 and slot
0 of subrack 0.
----End
2.
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
232
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Deployment objective
Figure 7-43 shows the network topologies before and after reconstruction.
Figure 7-43 Network topologies before and after reconstruction
Issue 01 (2014-04-30)
233
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
NE
License
Control Item
Description
Abbreviation
Code
Sales Unit
eNodeB
IP-Based
Multi-mode
CoTransmission
on BS side
(eNodeB)
LLT1IPMCT0
1
81201528
Per eNodeB
Issue 01 (2014-04-30)
234
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
235
SingleRAN
Common Transmission Feature Parameter Description
Issue 01 (2014-04-30)
7 Engineering Guidelines
Item
Instance
Remarks
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24
21.21.21.254/24
11.11.11.254/24
20.20.20.1/24
20.20.20.188/24
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
35.35.35.188/24
GSM: communication IP
address of the BTS. This is a
logical IP address and is
configured on the BTS main
control board.
OM IP address of the
eNodeB
31.31.31.188/24
236
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
Signaling/service IP address
of the eNodeB
33.33.33.188/24
40.40.40.40/24
50.50.50.50/24
abcdefghijklmn
2.
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.)
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.
Issue 01 (2014-04-30)
237
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
6.
Reconstruction Procedure
Step 1 Upgrade the software.
If the software version of the multimode base station does not meet the reconstruction
requirements, upgrade the software before reconstruction.
Step 2 Reconstruct hardware and modify data configurations.
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)
ADD BRD: CN=0, SRN=0, SN=4, BT=UTRP, SBT=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.)
ADD BTSBRD: IDTYPE=BYID, BTSID=10, CN=0, SRN=0, SN=0, BT=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.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
238
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
BTS and NodeB services are interrupted when steps 5 to 10 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.
7.
Run the U2000 MML command SET CFGFILEENB to activate the NodeB configuration
file.
SET CFGFILEENB: FLAG=ENABLE, RSTMODE=IMMEDIATELY;
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.
Deactivate the BTS on the BSC, and execute the scripts for reconstruction to reactivate the
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.
Step 3 Verify services after reconstruction. For details, see section 7.15.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.23.6
Rollback
l Restore the hardware configuration and network topology to those before reconstruction.
----End
7.23.4 Precautions
None
7.23.5 Reconfiguration
Reconfiguration on the UMTS Side
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
Multimode Base Station Side in IP over FE/GE Mode.
Issue 01 (2014-04-30)
239
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 UTRPc.
IMP BTSTUNNEL: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, SRCCN=0, SRCSRN=0, SRCSN=6,
TN=0, DSTCN=0, DSTSRN=0, DSTSN=4;
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.
IMP BTSIPRT: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=OUTIF, CN=0, SRN=0, SN=6, ITFType=TUNNEL,
IFNO=0;
Step 5 Run the BSC MML command ACT BTSIMPDATA to activate the IP rehoming data.
ACT BTSIMPDATA: IDTYPE=BYID, BTSID=10;
----End
7.23.6 Rollback
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.)
Issue 01 (2014-04-30)
240
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 5 Execute the configuration scripts that are backed up before reconstruction. (CME: Script
Executor> Project > Load Project > Activate Project.)
----End
Deployment objective
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
244
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
15.15.15.15/32
11.11.11.11/24
60.60.60.60/24
21.21.21.254/24
11.11.11.254/24
20.20.20.1/24
20.20.20.188/24
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
35.35.35.188/24
GSM: communication IP
address of the BTS. This is a
logical IP address and is
configured on the BTS main
control board.
245
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
OM IP address of the
eNodeB
31.31.31.188/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
40.40.40.40/24
50.50.50.50/24
abcdefghijklmn
NOTE
The IP address plan for IP co-transmission in UCIU+UMPT interconnection is the same as that in UMPT
+UMPT interconnection.
2.
3.
Back up data.
l Back up the measurement results of original performance counters reported one week
before reconstruction.
Issue 01 (2014-04-30)
246
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
l Back up BTS data configurations before reconstruction on the CME. (CME: Main
View > Right-click a site > Export MML for Creating BTS.)
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.
5.
6.
Reconstruction Procedure
Step 1 Upgrade the software.
If the multimode base station software version does not meet the reconstruction requirements,
upgrade the software before reconstruction.
Step 2 Reconstruct hardware and modify data configurations.
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.)
ADD BTSBRD: IDTYPE=BYID, BTSID=10, CN=0, SRN=0, SN=0, BT=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.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
247
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
BTS and NodeB services are interrupted when steps 5 to 10 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.
6.
Run the U2000 MML command SET CFGFILEENB to activate the NodeB configuration
file.
SET CFGFILEENB: FLAG=ENABLE, RSTMODE=IMMEDIATELY;
7.
8.
Deactivate the BTS on the BSC, and execute the scripts for reconstruction to reactivate the
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
Step 4 Perform the rollback operation if reconstruction fails.
----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
7.24.5 Reconfiguration
Reconfiguration on the UMTS Side
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."
248
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 UMPT_U.
IMP BTSTUNNEL: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, SRCCN=0, SRCSRN=0, SRCSN=6,
TN=0, 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.
IMP BTSIPRT: IDTYPE=BYID, BTSID=10, CFGSW=ENABLE, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=OUTIF, CN=0, SRN=0, SN=6, ITFType=TUNNEL,
IFNO=0;
Step 5 Run the BSC MML command ACT BTSIMPDATA to activate the IP rehoming data.
ACT BTSIMPDATA: IDTYPE=BYID, BTSID=10;
----End
7.24.6 Rollback
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)
249
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 5 Execute the configuration scripts that are backed up before reconstruction. (CME: Script
Executor> Project > Load Project > Activate Project.)
----End
Deployment objective
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
11.11.11.11/32
23.23.23.1/24
21.21.21.254/24
23.23.23.254/24
251
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
30.30.30.1/24
20.20.20.188/24
20.20.20.1/24
30.30.30.188/24
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 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.
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
Common Transmission Feature Parameter Description
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
ES
DHCP Switch
DEVIP
IPRT
Issue 01 (2014-04-30)
7 Engineering Guidelines
253
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.25.3 Precautions
None
UG
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 of the NodeB and that of
Issue 01 (2014-04-30)
254
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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 1 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 1 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.
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.
Issue 01 (2014-04-30)
255
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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, 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.
----End
l
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;
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="11.11.11.11",
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 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 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", CONTPING=NO;
----End
256
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Deployment objective
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
Issue 01 (2014-04-30)
257
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
11.11.11.11/32
23.23.23.1/24
21.21.21.254/24
23.23.23.254/24
30.30.30.1/24
20.20.20.188/24
20.20.20.1/24
30.30.30.188/24
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 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.
Issue 01 (2014-04-30)
258
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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
Common Transmission Feature Parameter Description
MO
7 Engineering Guidelines
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
ES
DHCP Switch
7.26.3 Precautions
None
UG
Issue 01 (2014-04-30)
260
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
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 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
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 1 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 1 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.
Issue 01 (2014-04-30)
261
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
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.
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, 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.
----End
l
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=4, SRCIP="20.20.20.188", DSTIP="10.10.10.10",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
PING: CN=0, SRN=0, SN=4, SRCIP="20.20.20.188", DSTIP="11.11.11.11",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=0;
----End
Issue 01 (2014-04-30)
262
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
GSM Side
After the configuration file is delivered to the BTS and activated, perform the following step on
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 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", CONTPING=NO;
----End
7.27 GTMU-based TDM Co-Transmission on the SeparateMPT GU Multimode Base Station Side
7.27.1 Deployment Requirements
l
Deployment objective
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
263
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.27.3 Precautions
In Figure 7-52, this scenario only supports the WMPT.
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
Issue 01 (2014-04-30)
264
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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;
Deployment objective
265
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Figure 7-53 Network topology for co-transmission on the co-MPT GU multimode base station
side in IP over FE/GE mode
266
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Instance
Remarks
10.10.10.10/32
21.21.21.1/24
21.21.21.254/24
11.11.11.254/24
20.20.20.1/24
20.20.20.188/24
OM IP address
30.30.30.1/32
Issue 01 (2014-04-30)
Signaling/service IP address
of the NodeB
32.32.32.1/24
15.15.15.15/24
11.11.11.11/24
60.60.60.60/24
Signaling/service IP address
of the BTS
35.35.35.188/24
267
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
MO
VLANMAP
VLANCLASS
7 Engineering Guidelines
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.
VLANGROUPNO
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
SETPRIO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
7.28.3 Precautions
None
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.
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
Step 1 Run the ADD DEVIP command to add the IP address of the NodeB.
Issue 01 (2014-04-30)
269
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 2 Run the ADD DEVIP command to add the IP address of the BTS.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="35.35.35.188",
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 IPRT: RTIDX=0, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="15.15.15.15",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the multimode base station to the RNC on the UMPT_GU in slot 7.
Step 4 Run the ADD IPRT command to add an uplink route from the multimode base station to the
BSC.
ADD IPRT: RTIDX=1, CN=0, SN=7, SBT=BACK_BOARD, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the multimode base station to the BSC on the UMPT_GU in slot 7.
Step 5 (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 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.
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 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.
2.
----End
l
Issue 01 (2014-04-30)
270
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
Step 2 Run the PING command to ping the IP address of the BSC.
PING: CN=0, SRN=0, SN=7, SRCIP="35.35.35.1", DSTIP="10.10.10.10",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
----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.
Deployment objective
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Figure 7-55 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)
272
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
21.21.21.254/24
11.11.11.254/24
20.20.20.1/24
20.20.20.188/24
273
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
OM IP address
30.30.30.1/24
Issue 01 (2014-04-30)
Signaling/service IP address
of the NodeB
32.32.32.1/24
15.15.15.15/24
11.11.11.11/24
60.60.60.60/24
Signaling/service IP address
of the BTS
35.35.35.188/24
40.40.40.40/24
50.50.50.50/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
ESN
abcdefghijklmn
274
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
VLANMAP
VLANGROUPNO
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
SETPRIO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLANCLASS
7.29.3 Precautions
None
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.
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
Step 1 Run the ADD DEVIP command to add the IP address of the NodeB.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="32.32.32.1",
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.
Issue 01 (2014-04-30)
276
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 3 Run the ADD DEVIP command to add the IP address of the eNodeB.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=3, IP="33.33.33.188",
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 multimode base station to the
RNC. Set Route Type to Next Hop and then set Next Hop IP to the IP address of the directly
connected router.
ADD IPRT: RTIDX=0, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="15.15.15.15",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the multimode base station to the RNC on the UMPT_GUL in slot
7.
Step 5 Run the ADD IPRT command to add an uplink route from the multimode base station to the
BSC.
ADD IPRT: RTIDX=1, CN=0, SN=7, SBT=BACK_BOARD, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the multimode base station to the BSC on the UMPT_GUL in slot
7.
Step 6 Run the ADD IPRT command to add an uplink route from the multimode base station to the
MME and SGW.
ADD IPRT: RTIDX=2, CN=0, SN=7, SBT=BACK_BOARD, DSTIP="40.40.40.40",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the multimode base station to the MME on the UMPT_GUL in slot 7
ADD IPRT: RTIDX=3, CN=0, SN=7, SBT=BACK_BOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the multimode base station to the SGW on the UMPT_GUL in slot 7
Step 7 (Optional) Configure VLAN. There are two methods of configuring differentiated VLAN data
for the BTS, NodeB, and eNodeB:
l Method 1 (Recommended): Configure differentiated next-hop addresses. Specifically, the
uplink route from the multimode base station to the BSC added in step 3, the uplink route
from the multimode base station to the RNC added in step 4, and the uplink route from the
multimode base station to the MME and SGW in step 5 must be different from 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.101", MASK=255.255.255.255,
VLANMODE=SINGLEVLAN, VLANID=22, SETPRIO=DISABLE;
ADD VLANMAP: NEXTHOPIP="20.20.20.10", MASK=255.255.255.255,
VLANMODE=SINGLEVLAN, VLANID=20, SETPRIO=DISABLE;
ADD VLANMAP: NEXTHOPIP="20.20.20.1", MASK=255.255.255.255, VLANMODE=SINGLEVLAN,
VLANID=20, SETPRIO=DISABLE;
l Method 2 (Not recommended): Configure differentiated DSCP values. This method requires
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.
Issue 01 (2014-04-30)
277
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
2.
----End
Step 2 Run the PING command to ping the IP address of the BSC.
PING: CN=0, SRN=0, SN=7, SRCIP="35.35.35.1", DSTIP="10.10.10.10",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
Step 3 Run the PING command to ping the IP address of the MME.
PING: CN=0, SRN=0, SN=7, SRCIP="33.33.33.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
Step 4 Run the PING command to ping the IP address of the SGW.
PING: CN=0, SRN=0, SN=7, SRCIP="33.33.33.188", DSTIP="50.50.50.50",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
----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.
278
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Deployment objective
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
279
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
21.21.21.254/24
11.11.11.254/24
20.20.20.1/24
20.20.20.188/24
280
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Item
Instance
Remarks
OM IP address
30.30.30.1/24
UMTS<E: Management
plane IP address. This is a
logical IP address and is
configured on the
UMPT_UL.
NOTE
In this scenario, only one OM
IP address is configured
because the co-MPT UL
multimode base station is
configured with one OM
channel.
Issue 01 (2014-04-30)
Signaling/service IP address
of the NodeB
32.32.32.1/24
15.15.15.15/24
11.11.11.11/24
60.60.60.60/24
UMTS<E: Peer IP
address for the OM channel
Signaling/service IP address
of the BTS
35.35.35.188/24
40.40.40.40/24
50.50.50.50/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
ESN
abcdefghijklmn
281
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
BTSTUNNEL
Index Type
IDTYPE
BTS Index
BTSID
BTS Index
SRCCN
SRCSRN
SRCSN
TN
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.
CN
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
BTSMUTIP
BTSDEVIP
BTSIP
Issue 01 (2014-04-30)
282
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
CN
SRN
SN
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
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
Issue 01 (2014-04-30)
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
SCN
283
SingleRAN
Common Transmission Feature Parameter Description
MO
DEVIP
IPRT
DHCPSVRIP
Issue 01 (2014-04-30)
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Source Subrack
No.
SSRN
Source Subrack
No.
SSN
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
DHCPRELAYSWITC
H
DHCP Relay
Switch
ES
DHCP Switch
VLANMAP
VLANGROUPNO
Next Hop IP
NEXTHOPIP
Next Hop IP
Mask
MASK
Mask
VLAN Mode
VLANMODE
VLAN Mode
VLAN ID
VLANID
VLAN ID
SETPRIO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLANCLASS
7.30.3 Precautions
None
Step 1 Run the MML command ADD BTSTUNNEL to add a tunnel from the GTMUb to the
UMPT_UL.
ADD BTSTUNNEL: IDTYPE=BYID, BTSID=10, SRCCN=0, SRCSRN=0, SRCSN=6, TN=0, DSTCN=0,
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
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 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 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 BTSIP: IDTYPE=BYID, BTSID=10, BTSCOMTYPE=LOGICIP, BTSIP="35.35.35.188",
BSCIP="10.10.10.10", BTSMUTIP=NO;
//Set BTSCOMTYPE to LOGICIP.
Step 5 Run the MML command ADD BTSIPRT to add a route from the GBTS to the BSC.
Unlike non-co-transmission scenarios, set RTTYPE to OUTIF, ITFType to TUNNEL, and
IFNO to the number of the tunnel added in step 1.
ADD BTSIPRT: IDTYPE=BYID, BTSID=10, RTIDX=1, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=OUTIF, CN=0, SRN=0, SN=6, ITFType=TUNNEL,
IFNO=0;
Step 6 Run the MML command ADD BTSESN to add the ESN of the GBTS.
ADD BTSESN: IDTYPE=BYID, BTSID=10, MAINDEVTAB="abcdefghijklmn",
OMBEARBOARD=BACKBOARD;
//OMBEARBOARD must be set to BACKBOARD.
----End
l
Step 1 Run the MML command ADD TUNNEL to add a tunnel from the UMPT_UL to the GTMUb.
ADD TUNNEL: SSN=7, DSN=6, TUNNELTYPE=DL;
//Add a tunnel from the UMPT_UL in slot 7 to the GTMUb in slot 6.
Step 2 Run the ADD DEVIP command to add the IP address of the NodeB.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="32.32.32.1",
MASK="255.255.255.0";
//Add the signaling/service IP address of the NodeB.
Issue 01 (2014-04-30)
286
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 3 Run the ADD DEVIP command to add the IP address of the eNodeB.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="33.33.33.188",
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 IPRT: RTIDX=0, CN=0, SN=7, SBT=BASE_BOARD, DSTIP="15.15.15.15",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//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 IPRT: RTIDX=1, CN=0, SN=7, SBT=BACK_BOARD, DSTIP="40.40.40.40",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//Add a route from the multimode base station to the MME on the UMPT_UL.
ADD IPRT: RTIDX=2, CN=0, SN=7, SBT=BACK_BOARD, DSTIP="50.50.50.50",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.1";
//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 IPRT: RTIDX=3, 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 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",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//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.
SET DHCPRELAYSWITCH: ES=ENABLE;
//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
device IP address, set the IP address of the DHCP server to the device IP address.
Issue 01 (2014-04-30)
287
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 10 (Optional) Configure VLAN. There are two methods of configuring differentiated VLAN data
for the BTS, NodeB, and eNodeB:
l Method 1 (Recommended): Configure differentiated next-hop addresses. Specifically, the
uplink route from the multimode base station to the BSC added in step 4, the uplink route
from the multimode base station to the RNC added in step 5, and the uplink route from the
multimode base station to the MME and SGW in step 6 must be different from each other.
For example, you can set the next-hop address of the uplink route from the multimode base
station to the BSC to 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.101", MASK=255.255.255.255,
VLANMODE=SINGLEVLAN, VLANID=22, SETPRIO=DISABLE;
ADD VLANMAP: NEXTHOPIP="20.20.20.10", MASK=255.255.255.255,
VLANMODE=SINGLEVLAN, VLANID=20, SETPRIO=DISABLE;
ADD VLANMAP: NEXTHOPIP="20.20.20.1", MASK=255.255.255.255, VLANMODE=SINGLEVLAN,
VLANID=20, SETPRIO=DISABLE;
l Method 2 (Not recommended): Configure differentiated DSCP values. This method requires
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.
2.
----End
l
Issue 01 (2014-04-30)
288
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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 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.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="35.35.35.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
Step 2 Run the Ping command on the multimode base station to ping the IP address of the RNC. If the
IP address can be pinged, the transmission link is normal.
PING: CN=0, SRN=0, SN=7, SRCIP="32.32.32.1", DSTIP="15.15.15.15",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
Step 3 Run the Ping command on the multimode base station to ping the IP address of the MME.
PING: CN=0, SRN=0, SN=7, SRCIP="33.33.33.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
Step 4 Run the Ping command on the multimode base station to ping the IP address of the SGW.
PING: CN=0, SRN=0, SN=7, SRCIP="33.33.33.188", DSTIP="50.50.50.50",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
----End
Deployment objective
Figure 7-59 shows the main-control-board-based IP co-transmission through backplane
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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
290
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
291
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
LLT1IPMCT01
81201528
Per eNodeB
292
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Issue 01 (2014-04-30)
Item
IP Address
Remarks
10.10.10.10/32
21.21.21.1/24
15.15.15.15/32
11.11.11.11/24
11.11.11.254/24
293
SingleRAN
Common Transmission Feature Parameter Description
Issue 01 (2014-04-30)
7 Engineering Guidelines
Item
IP Address
Remarks
21.21.21.254/24
20.20.20.1/24
30.30.30.1/24
Signaling/service IP address
of the NodeB
32.32.32.1/24
20.20.20.188/24
40.40.40.40/24
50.50.50.50/24
60.60.60.60/24
OM IP address of the
eNodeB
31.31.31.188/24
Signaling/service IP address
of the eNodeB
33.33.33.188/24
35.35.35.188/24
GSM: communication IP
address of the BTS. This is a
logical IP address and is
configured on the BTS main
control board.
BTS ESN
abcdefghijklmn
294
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
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.
UPCN
UPSRN
UPSN
UPPT
IDTYPE
BTS Index
BTSID
BTS Index
SRCCN
SRCSRN
SRCSN
BTSCTRLLNK
BTSTUNNEL
Issue 01 (2014-04-30)
295
SingleRAN
Common Transmission Feature Parameter Description
MO
BTSDEVIP
BTSIP
BTSIPRT
Issue 01 (2014-04-30)
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TN
Destination Cabinet
No.
DSTCN
Destination Cabinet
No.
Destination Subrack
No.
DSTSRN
Destination Subrack
No.
DSTSN
IDTYPE
BTS Index
BTSID
BTS Index
Port Type
PT
Port Type
Port No.
PN
Port No.
CN
Subrack No.
SRN
Subrack No.
Slot No.
SN
Slot No.
IP Address
IP
IP Address
IP Mask
MASK
IP Mask
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
BTSMUTIP
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
Common Transmission Feature Parameter Description
MO
BTSESN
IPRT
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Route Type
RTTYPE
Route Type
CN
SRN
SN
Interface Type
ITFType
Interface Type
Outgoing Interface
No.
IFNO
Outgoing Interface
No.
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
LN
CN
SRN
SN
UPCN
UPSRN
UPSN
UPPT
297
SingleRAN
Common Transmission Feature Parameter Description
MO
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
TUNNEL
SCN
SSRN
SSN
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
PT
Carrier Type
PN
Link No.
Transmission
Resource Group ID
RSCGRPID
Transmission
Resource Group ID
IPRT
RSCGRP
Issue 01 (2014-04-30)
7 Engineering Guidelines
298
SingleRAN
Common Transmission Feature Parameter Description
MO
IPPath
OMCH
Issue 01 (2014-04-30)
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
MO
7 Engineering Guidelines
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
Binding Route
BRT
Binding Route
MML Parameter
Name
MML Parameter
ID
CME Parameter
Name
CTRLLNK
LN
CN
SRN
SN
UPCN
UPSRN
UPSN
UPPT
SCN
TUNNEL
DEVIP
Issue 01 (2014-04-30)
Source Subrack
No.
SSN
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
Common Transmission Feature Parameter Description
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
SETPRIO
VLAN Priority
VLANPRIO
VLAN Priority
VLANGROUPNO
VLANGROUPNO
Traffic Type
TRAFFIC
Traffic Type
SRVPRIO
VLAN ID
VLANID
VLAN ID
VLAN Priority
VLANPRIO
VLAN Priority
IPRT
VLANCLASS
Issue 01 (2014-04-30)
7 Engineering Guidelines
301
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.31.3 Precautions
None
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.
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.
ADD BTSBRD: IDTYPE=BYID, BTSID=10, CN=0, SRN=0, SN=0, BT=UCIU;
//Add a UCIU to slot 0.
Step 2 Run the ADD BTSCTRLLNK command to add a BBU interconnection control link between
GSM and LTE.
(UCIU+UMPT interconnection)ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=10, LN=0, CN=0,
SRN=1, SN=7, UPCN=0, UPSRN=0, UPSN=0, UPPT=0;
//Add a BBU interconnection control link between slot 7 of subrack 1 and slot 0 of
subrack 0.
(UMPT+UMPT interconnection) ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=10, LN=0, CN=0,
SRN=1, SN=7, UPCN=0, UPSRN=0, UPSN=7, UPPT=8;
//Add a BBU interconnection control link between slot 7 of subrack 1 and slot 7 of
subrack 0.
Step 3 Run the BSC MML command ADD BTSTUNNEL to add a tunnel from the GTMUb to the
UMPT_L.
ADD BTSTUNNEL: IDTYPE=BYID, BTSID=10, SRCCN=0, SRCSRN=0, SRCSN=6, TN=0, DSTCN=0,
DSTSRN=1, DSTSN=7;
Issue 01 (2014-04-30)
302
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
//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.
Step 4 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 5 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 use the logical IP
address. Specifically, set BTSCOMTYPE to LOGICIP. In non-co-transmission scenarios, set
BTSCOMTYPE to an appropriate value based on the actual situations.
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 6 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 3.
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=0;
Step 7 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.
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.
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;
----End
l
303
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
(UMPT+UMPT interconnection) ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=10, LN=0, CN=0,
SRN=1, SN=7, UPCN=0, UPSRN=0, UPSN=7, UPPT=8;
//Add a BBU interconnection control link between slot 7 of subrack 1 and slot 7 of
subrack 0.
Step 2 Run the NodeB MML command ADD TUNNEL to add a tunnel from the WMPT to the
UMPT_L.
ADD TUNNEL: SSN=7, DSRN=1, DSN=7;
//Add a tunnel from the WMPT in slot 7 of BBU subrack 0 to the UMPT_L in slot 7 of
BBU subrack 1.
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.
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=1, IP="32.32.32.1",
MASK="255.255.255.0";
//Add a signaling/service IP address for the NodeB.
Step 4 Run the NodeB MML command ADD IPRT to add a route from the NodeB to the RNC/U2000.
Unlike non-co-transmission scenarios, set SBT to BACK_BOARD, RTTYPE to IF, IFT to
TUNNEL, and IFNO to the number of the tunnel added in step 2.
ADD IPRT: RTIDX=0, SN=7, SBT=BACK_BOARD, DSTIP="15.15.15.15",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a route from the NodeB to the RNC.
ADD IPRT: RTIDX=1, SN=7, SBT=BACK_BOARD, DSTIP="60.60.60.60",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
Step 7 Run the NodeB MML command ADD OMCH to add an O&M channel.
ADD OMCH: IP="30.30.30.1", MASK="255.255.255.0", PEERIP="60.60.60.60",
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
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.
(UMPT+UMPT interconnection) ADD BTSCTRLLNK: IDTYPE=BYID, BTSID=10, LN=0, CN=0,
SRN=1, SN=7, UPCN=0, UPSRN=0, UPSN=7, UPPT=8;
//Add a BBU interconnection control link between slot 7 of subrack 1 and slot 7 of
subrack 0.
Step 2 Run the eNodeB MML command ADD TUNNEL to add tunnels from the UMPT_L to the
WMPT and GTMUb.
ADD TUNNEL: SSRN=1, SSN=7, DSN=7;
//Add a tunnel from the UMPT_L in slot 7 of subrack 1 to the WMPT in slot 7 of
subrack 0.
ADD TUNNEL: TUNNELID=1, SSRN=1, SSN=7, DSN=6;
//Add a tunnel from the UMPT_L in slot 7 of subrack 1 to the GTMUb in slot 6 of
subrack 0.
Step 3 Run the eNodeB MML command ADD DEVIP to add IP addresses for the eNodeB.
ADD DEVIP: SRN=1, SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="33.33.33.188",
MASK="255.255.255.0";
//Add a signaling/service IP address for the UMPT_L in slot 7.
ADD DEVIP: CN=0, SRN=1, 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_L in slot 7.
Step 4 Run the eNodeB MML command ADD IPRT to add an uplink route from the NodeB to the
RNC/U2000 through the eNodeB, and an uplink route from the 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
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
When co-transmission for the BTS, eNodeB, and NodeB is implemented through tunnels on the
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 IPRT: RTIDX=3, CN=0, SRN=1, SN=7, SBT=BACK_BOARD, DSTIP="30.30.30.1",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//Add a downlink route from the U2000 to the NodeB through the eNodeB.
ADD IPRT: RTIDX=4, CN=0, SRN=1, SN=7, SBT=BACK_BOARD, DSTIP="32.32.32.1",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL;
//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",
DSTMASK="255.255.255.255", RTTYPE=IF, IFT=TUNNEL, IFNO=1;
//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.
SET DHCPRELAYSWITCH: ES=ENABLE;
//Enable DHCP relay 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 DHCPSVRIP: DHCPSVRIP="60.60.60.60";
//Add the IP address of the DHCP server for the NodeB.
ADD DHCPSVRIP: DHCPSVRIP="10.10.10.10";
// Add the IP address of the DHCP server for the GBTS.
Step 8 (Optional) Configure VLAN. There are two methods of configuring differentiated VLAN data
for the BTS, NodeB, and eNodeB:
l Method 1 (Recommended): Configure differentiated next-hop addresses. Specifically, the
uplink route from the BTS to the BSC through the eNodeB and the uplink route from the
Issue 01 (2014-04-30)
306
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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.
ADD VLANMAP: NEXTHOPIP="20.20.20.101", MASK="255.255.255.0",
VLANMODE=SINGLEVLAN, VLANID=22, SETPRIO=DISABLE;
ADD VLANMAP: NEXTHOPIP="20.20.20.201", MASK="255.255.255.0",
VLANMODE=SINGLEVLAN, VLANID=32, SETPRIO=DISABLE;
l Method 2 (Not recommended): Configure differentiated DSCP values. This method requires
differentiated DSCP values for the BTS, NodeB, and eNodeB. For details about DSCP values
for the BTS, NodeB, and eNodeB, see the Bandwidth Sharing of Multimode Base Station
Co-Transmission Feature Parameter Description.
1.
2.
----End
l
LTE Side
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 between the eNodeB and the MME/S-GW is normal.
PING: CN=0, SRN=0, SN=7, SRCIP="20.20.20.188", DSTIP="40.40.40.40",
CONTPING=DISABLE, APPTIF=YES, SBT=BASE_BOARD, PT=ETH, PN=1;
Issue 01 (2014-04-30)
307
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
----End
UMTS Side
After the configuration file is delivered to the NodeB and activated, perform the following step
on the NodeB side to check whether the transmission link between the NodeB and the RNC is
normal:
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.
PING: CN=0, SRN=0, SN=7, SRCIP="32.32.32.1", DSTIP="15.15.15.15",
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 address of the GTMUb.
PING IP: SRN=1, SN=16, SIPADDR="10.10.10.10", DESTIP="35.35.35.188",
NEXTHOP="21.21.21.254", CONTPING=NO;
----End
308
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
7.34 Troubleshooting
7.34.1 IP Co-Transmission on the MBSC Side
None
Issue 01 (2014-04-30)
309
SingleRAN
Common Transmission Feature Parameter Description
7 Engineering Guidelines
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
Common Transmission Feature Parameter Description
8 Parameters
Parameters
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
CN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
ETHPO
RT
None
None
DSP
ETHPO
RT
Unit: None
RMV
ETHPO
RT
Default Value: 0
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
Issue 01 (2014-04-30)
311
SingleRAN
Common Transmission Feature Parameter Description
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
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
DSP
ETHPO
RT
Unit: None
RMV
ETHPO
RT
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
Issue 01 (2014-04-30)
312
SingleRAN
Common Transmission Feature Parameter Description
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
DSP
ETHPO
RT
Unit: None
Actual Value Range: BASE_BOARD,
ETH_COVERBOARD
RMV
ETHPO
RT
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
RMV
ETHPO
RT
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT
Issue 01 (2014-04-30)
313
SingleRAN
Common Transmission Feature Parameter Description
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
SET
ETHPO
RT
DSP
ETHPO
RT
LST
ETHPO
RT
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
Issue 01 (2014-04-30)
314
SingleRAN
Common Transmission Feature Parameter Description
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
SET
ETHPO
RT
DSP
DHCPR
SLT
LST
ETHPO
RT
CN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
DEVIP
None
None
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
DSP
DEVIP
MOD
DEVIP
RMV
DEVIP
Unit: None
Default Value: 0
LST
DEVIP
Issue 01 (2014-04-30)
315
SingleRAN
Common Transmission Feature Parameter Description
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
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
RMV
DEVIP
Unit: None
DSP
DEVIP
LST
DEVIP
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
316
SingleRAN
Common Transmission Feature Parameter Description
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
MOD
DEVIP
Unit: None
RMV
DEVIP
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
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
Fraction
al IP
Function
on Iub
Interface
317
SingleRAN
Common Transmission Feature Parameter Description
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
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
DSP
IPRT
MOD
IPRT
Unit: None
Default Value: 0
LST
IPRT
None
None
DSP
IPRT
MOD
IPRT
Unit: None
Default Value: 0
LST
IPRT
None
None
DSP
IPRT
MOD
IPRT
LST
IPRT
Unit: None
Default Value: None
318
SingleRAN
Common Transmission Feature Parameter Description
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
MOD
IPRT
LST
IPRT
Unit: None
Actual Value Range: BASE_BOARD,
UNCHANNELLED_COVERBOARD,
E1_COVERBOARD, BACK_BOARD,
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
IP
routing
Based
Hub
Node B
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
IP
routing
Based
Hub
Node B
319
SingleRAN
Common Transmission Feature Parameter Description
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
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
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
IP
routing
Based
Hub
Node B
NodeB
Selfdiscover
y Based
on IP
Mode
LST
DHCPS
VRIP
320
SingleRAN
Common Transmission Feature Parameter Description
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)
WRFD031101
LST
DHCPR
ELAYS
WITCH
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
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
LST
VLAN
MAP
Issue 01 (2014-04-30)
321
SingleRAN
Common Transmission Feature Parameter Description
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)
MOD
VLAN
MAP
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
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
322
SingleRAN
Common Transmission Feature Parameter Description
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
MOD
VLAN
MAP
LST
VLAN
MAP
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
RMV
VLANC
LASS
Issue 01 (2014-04-30)
323
SingleRAN
Common Transmission Feature Parameter Description
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
MOD
VLANC
LASS
RMV
VLANC
LASS
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
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
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
324
SingleRAN
Common Transmission Feature Parameter Description
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
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
IP
routing
Based
Hub
Node B
None
None
MOD
IPRT
Unit: None
LST
IPRT
Default Value: 0
DSP
TUNNE
L
MOD
TUNNE
L
MRFD221501
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
RMV
TUNNE
L
LST
TUNNE
L
Issue 01 (2014-04-30)
325
SingleRAN
Common Transmission Feature Parameter Description
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)
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
DSP
TUNNE
L
MOD
TUNNE
L
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
RMV
TUNNE
L
LST
TUNNE
L
Issue 01 (2014-04-30)
326
SingleRAN
Common Transmission Feature Parameter Description
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)
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
IPBased
Multimode
CoTransmi
ssion on
BS side
(NodeB)
DSP
TUNNE
L
MOD
TUNNE
L
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
LST
TUNNE
L
DSN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
TUNNE
L
MOD
TUNNE
L
DSP
TUNNE
L
MRFD221501
LST
TUNNE
L
Issue 01 (2014-04-30)
327
SingleRAN
Common Transmission Feature Parameter Description
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
LST
UTRP
Unit: None
MOD
UTRP
SET
BRDRA
T
SRN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
DSP
BRDRA
T
None
None
LST
UTRP
Unit: None
MOD
UTRP
SET
BRDRA
T
SN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
DSP
BRDRA
T
None
None
LST
UTRP
Unit: None
MOD
UTRP
SET
BRDRA
T
Issue 01 (2014-04-30)
328
SingleRAN
Common Transmission Feature Parameter Description
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)
MOD
TUNNE
L
DSP
TUNNE
L
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
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
329
SingleRAN
Common Transmission Feature Parameter Description
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
DSP
RSCGR
P
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
RMV
RSCGR
P
LST
RSCGR
P
Issue 01 (2014-04-30)
330
SingleRAN
Common Transmission Feature Parameter Description
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
DSP
RSCGR
P
MOD
RSCGR
P
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
RMV
RSCGR
P
LST
RSCGR
P
Issue 01 (2014-04-30)
331
SingleRAN
Common Transmission Feature Parameter Description
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
DSP
RSCGR
P
MOD
RSCGR
P
Unit: None
RMV
RSCGR
P
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
None
LST
RSCGR
P
Issue 01 (2014-04-30)
332
SingleRAN
Common Transmission Feature Parameter Description
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
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
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
Transmi
ssion
Recours
e
Sharing
on Iub/
Iur
Interface
LST
RSCGR
P
Issue 01 (2014-04-30)
333
SingleRAN
Common Transmission Feature Parameter Description
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
MOD
RSCGR
P
DSP
RSCGR
P
LST
RSCGR
P
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
Issue 01 (2014-04-30)
334
SingleRAN
Common Transmission Feature Parameter Description
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
None
DSP
IPPATH
LST
IPPATH
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
MOD
IPPATH
LST
IPPATH
Unit: None
Default Value: 0
None
None
MOD
IPPATH
LST
IPPATH
Unit: None
Default Value: None
335
SingleRAN
Common Transmission Feature Parameter Description
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
MOD
IPPATH
LST
IPPATH
Unit: None
Actual Value Range: BASE_BOARD,
E1_COVERBOARD, BACK_BOARD,
ETH_COVERBOARD
Default Value: None
PT
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
IPPATH
None
None
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
MOD
IPPATH
LST
IPPATH
MOD
IPPATH
LST
IPPATH
Unit: None
Default Value: 0
WRFD0213040
6
Transmi
ssion
Recours
e
Sharing
on Iub/
Iur
Interface
Issue 01 (2014-04-30)
336
SingleRAN
Common Transmission Feature Parameter Description
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
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
WRFD050402
MOD
IPPATH
LST
IPPATH
WRFD050402
MOD
IPPATH
LST
IPPATH
WRFD0106101
0
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
HSDPA
Flow
Control
Issue 01 (2014-04-30)
337
SingleRAN
Common Transmission Feature Parameter Description
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
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
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
IP
Transmi
ssion
Introduc
tion on
Iub
Interface
338
SingleRAN
Common Transmission Feature Parameter Description
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
PEERM
ASK
BEAR
MOD
OMCH
DSP
OMCH
Unit: None
Actual Value Range: Valid IP address
LST
OMCH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
OMCH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
OMCH
MOD
OMCH
ATM/IP
Dual
Stack
Node B
DSP
OMCH
LST
OMCH
WRFD050404
MOD
OMCH
ATM/IP
Dual
Stack
Node B
DSP
OMCH
LST
OMCH
CN
BTS390
0,
BTS390
0
WCDM
A
ADD
OMCH
None
MOD
OMCH
DSP
OMCH
LST
OMCH
Issue 01 (2014-04-30)
None
Unit: None
Default Value: 0
339
SingleRAN
Common Transmission Feature Parameter Description
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
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
ADD
OMCH
MOD
OMCH
DSP
OMCH
LST
OMCH
None
None
Issue 01 (2014-04-30)
340
SingleRAN
Common Transmission Feature Parameter Description
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
MOD
OMCH
DSP
OMCH
LST
OMCH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
None
None
LST
CTRLL
NK
Unit: None
MOD
CTRLL
NK
RMV
CTRLL
NK
CN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
DSP
CTRLL
NKSTA
T
None
None
MOD
CTRLL
NK
LST
CTRLL
NK
Issue 01 (2014-04-30)
341
SingleRAN
Common Transmission Feature Parameter Description
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
DSP
CTRLL
NKSTA
T
Unit: None
Actual Value Range: 0~1
Default Value: None
MOD
CTRLL
NK
LST
CTRLL
NK
SN
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
ADD
CTRLL
NK
None
None
DSP
CTRLL
NKSTA
T
Unit: None
Actual Value Range: 0~7
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.
GUI Value Range: 0~7
MOD
CTRLL
NK
Unit: None
LST
CTRLL
NK
342
SingleRAN
Common Transmission Feature Parameter Description
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
None
None
MOD
CTRLL
NK
Unit: None
LST
CTRLL
NK
MOD
CTRLL
NK
LST
CTRLL
NK
None
None
343
SingleRAN
Common Transmission Feature Parameter Description
9 Counters
Counters
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
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None
Issue 01 (2014-04-30)
344
SingleRAN
Common Transmission Feature Parameter Description
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
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None
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
Issue 01 (2014-04-30)
345
SingleRAN
Common Transmission Feature Parameter Description
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
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None
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
Issue 01 (2014-04-30)
346
SingleRAN
Common Transmission Feature Parameter Description
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
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None
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
Issue 01 (2014-04-30)
347
SingleRAN
Common Transmission Feature Parameter Description
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
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None
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
Issue 01 (2014-04-30)
348
SingleRAN
Common Transmission Feature Parameter Description
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
MRFD-221501
MRFD-231501
MRFD-241501
GSM: None
UMTS: None
LTE: None
Issue 01 (2014-04-30)
349
SingleRAN
Common Transmission Feature Parameter Description
10 Glossary
10
Glossary
Issue 01 (2014-04-30)
350
SingleRAN
Common Transmission Feature Parameter Description
11
11 Reference Documents
Reference Documents
1.
2.
3.
Issue 01 (2014-04-30)
351