2G, 3G and LTE Co-Transmission (ERAN12.1 - 01)

eRAN
2G, 3G and LTE Co-transmission

Feature Parameter Description
Issue 01
Date 2017-03-08
HUAWEI TECHNOLOGIES CO., LTD.

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

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

Copyright © Huawei Technologies Co., Ltd.
eRAN
2G, 3G and LTE Co-transmission Feature Parameter
Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between eNodeB Types.............................................................................................................................. 2
1.5 Functional Differences Between NB-IoT and FDD....................................................................................................... 3
2 Overview......................................................................................................................................... 4
2.1 Definition........................................................................................................................................................................4
2.2 Benefits........................................................................................................................................................................... 4
2.3 Architecture.................................................................................................................................................................... 4
3 Technical Description...................................................................................................................6
3.1 Overview........................................................................................................................................................................ 6
3.2 Co-transmission with a Convergence Device.................................................................................................................7
3.3 Co-transmission Without a Convergence Device........................................................................................................... 8
4 Related Features...........................................................................................................................11
5 Network Impact........................................................................................................................... 12
6 Engineering Guidelines............................................................................................................. 13
6.1 When to Use................................................................................................................................................................. 13
6.2 Required Information................................................................................................................................................... 13
6.3 Planning........................................................................................................................................................................ 13
6.4 Deployment.................................................................................................................................................................. 14
6.4.1 Process....................................................................................................................................................................... 14
6.4.2 Requirements............................................................................................................................................................. 14
6.4.3 Precautions.................................................................................................................................................................14
6.4.4 Hardware Adjustment................................................................................................................................................15
6.4.5 Data Preparation and Feature Activation...................................................................................................................15
6.4.5.1 Data Preparation..................................................................................................................................................... 15
6.4.5.2 Activation............................................................................................................................................................... 23
6.4.6 Activation Observation..............................................................................................................................................25
6.4.7 Reconfiguration......................................................................................................................................................... 25
6.4.8 Deactivation...............................................................................................................................................................25
Issue 01 (2017-03-08) Huawei Proprietary and Confidential ii

eRAN
Description Contents
6.5 Performance Monitoring...............................................................................................................................................25

6.6 Parameter Optimization................................................................................................................................................ 25
6.7 Possible Issues.............................................................................................................................................................. 25
7 Parameters..................................................................................................................................... 26
8 Counters........................................................................................................................................ 44
9 Glossary......................................................................................................................................... 46
10 Reference Documents............................................................................................................... 47
Issue 01 (2017-03-08) Huawei Proprietary and Confidential iii

eRAN
Description 1 About This Document
1 About This Document
1.1 Scope
This document describes 2G/3G and LTE co-transmission, including the technical principles,
related features, network impact, and engineering guidelines. The eNodeB serves as a
convergence node for co-transmission.
This document covers the LOFD-003002 2G/3G and LTE Co-transmission feature.
This document covers the following features:

l LOFD-003002 2G/3G and LTE Co-transmission
l MLOFD-003002 2G/3G and eNodeB Co-transmission
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
Unless otherwise specified, in this document, LTE, eNodeB, and eRAN always include both
FDD and NB-IoT. The "L" and "M" in RAT acronyms refer to LTE FDD and LTE NB-IoT,
respectively.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
"eNodeB" refers to LTE FDD eNodeBs, and "eRAN" refers to LTE FDD eRAN.
1.2 Intended Audience

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

This section provides information about the changes in different document versions. There are
two types of changes:
Issue 01 (2017-03-08) Huawei Proprietary and Confidential 1

eRAN
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN12.1 01 (2017-03-08)
This issue does not include any changes.
eRAN12.1 Draft A (2016-12-30)

Draft A (2016-12-30) of eRAN12.1 introduces the following changes to Issue 01
(2016-03-07) of eRAN11.1.
Change Change Description Parameter Affected
Type Change Entity
Feature Supported NB-IoT. For details, see the None Macro

change following sections: eNodeBs
l 1.5 Functional Differences Between
NB-IoT and FDD
l 2.3 Architecture
l 3.1 Overview
l 6.1 When to Use
l 6.2 Required Information
l 6.4 Deployment
Editorial None None N/A

change
1.4 Differences Between eNodeB Types

The feature described in this document is implemented in the same way on macro and
LampSite eNodeBs.
The features described in this document are implemented in the same way on macro and
LampSite eNodeBs. For NB-IoT, these features can be used only with macro eNodeBs.

eRAN
1.5 Functional Differences Between NB-IoT and FDD

NB-IoT NB-IoT FDD FDD Difference
Feature Feature Featur Feature
ID Name e ID Name
MLOF 2G/3G LOFD- 2G/3G There are no functional differences between

D-0030 and 003002 and LTE NB-IoT and FDD. The only difference is
02 eNodeB Co- that the main control board of an FDD
Co- Transmis eNodeB can be an LMPT, UMPT, or
transmiss sion UMDU, but the main control board of an
ion NB-IoT eNodeB can only be an LMPT or
UMPT.

eRAN
Description 2 Overview
2 Overview
2.1 Definition
With the 2G/3G and LTE Co-transmission feature, an eNodeB not only provides LTE
services, but also works as a hub to provide routing and Dynamic Host Configuration
Protocol (DHCP) relay functions for lower-level cascaded base stations (including GBTSs,
eGBTSs, and NodeBs) and to transmit data transparently to the base station controllers.
2.2 Benefits
2G/3G and LTE Co-transmission allows radio access networks to share physical ports and
transmission bandwidth, thereby simplifying transmission configuration and maintenance.
This reduces capital expenditure (CAPEX) and operational expenditure (OPEX).
2.3 Architecture
Table 2-1 describes typical scenarios for LOFD-003002 2G/3G and LTE Co-transmission/
MLOFD-003002 2G/3G and eNodeB Co-transmission.
Table 2-1 Typical scenarios

Cascaded Networking
Base
Station
GBTS l The LMPT/UMPT/UMDU of an eNodeB provides FE/GE ports to

connect to the BSC, MME, and serving gateway (S-GW), and provides FE
ports to connect to the GTMU of a GBTS.
l The UMPT/UMDU of an eNodeB provides IP over FE/GE ports to
connect to the BSC, MME, and S-GW, and provides IP over E1/T1 ports
to connect to the GTMU of a GBTS.

eRAN
Description 2 Overview
Cascaded Networking
Base
Station
eGBTS l The LMPT/UMPT/UMDU of an eNodeB provides FE/GE ports to

connect to the BSC, MME, and S-GW, and provides FE/GE ports to
connect to the UMPT/UMDU of an eGBTS.
l The UMPT/UMDU of an eNodeB provides FE/GE ports to connect to the
BSC, MME, and S-GW, and provides IP over E1/T1 ports to connect to
the UMPT/UMDU of an eGBTS.
NodeB l The LMPT/UMPT/UMDU of an eNodeB provides FE/GE ports to

connect to the RNC, MME, and S-GW, and provides FE ports to connect
to the WMPT of a NodeB.
l The LMPT/UMPT/UMDU of an eNodeB provides FE/GE ports to
connect to the RNC, MME, S-GW, and the UMPT/UMDU of a NodeB.
l The UMPT/UMDU of an eNodeB provides FE/GE ports to connect to the
RNC, MME, and S-GW, and provides IP over E1/T1 ports to connect to
the UMPT/WMPT/UMDU of a NodeB.
NOTE
A scenario where an eNodeB uses IP over E1/T1 ports to connect to the BSC, RNC, MME, and S-GW is
rarely used on live networks and is not, therefore, described in this document. Such a scenario is
uncommon because:
l The MME and S-GW generally do not support IP over E1/T1 ports.
l The eNodeB rarely uses IP over E1/T1 ports for transmission due to the low bandwidth provided by
the E1/T1 links.
For details about the cascading between an eNodeB and CDMA/WiMAX base stations, refer to the
cascading between an eNodeB and GSM/UMTS base stations in this document.
UMDUs cannot be used as the main control boards of LTE NB-IoT eNodeBs.

eRAN
Description 3 Technical Description
3 Technical Description
3.1 Overview
This section describes LOFD-003002 2G/3G and LTE Co-transmission.
This section describes the following features:
l LOFD-003002 2G/3G and LTE Co-transmission
l MLOFD-003002 2G/3G and eNodeB Co-transmission
NOTE
The difference between the LOFD-003002 2G/3G and LTE Co-transmission/MLOFD-003002 2G/3G
and eNodeB Co-transmission feature and the IP-Based Multi-mode Co-Transmission on BS side feature
is that the eNodeB cascaded with single-mode base stations implements the former, whereas a multi-
mode base station using panel-based or backplane-based interconnection implements the latter. For
details about IP-based multi-mode co-transmission on the base station side, see Common Transmission
Feature Parameter Description for SingleRAN.
Co-transmission enables eNodeBs to be deployed in areas where GBTSs, eGBTSs, and

NodeBs have been deployed. Using FE/GE ports and IP over E1/T1 ports, the eNodeBs can
be cascaded with these base stations and share the transmission resources of these base
stations.
Figure 3-1 illustrates the co-transmission networking supported by an eNodeB.

eRAN
Figure 3-1 Co-transmission networking
In 2G/3G and LTE co-transmission, an eNodeB, functioning as a convergence node, provides

the DHCP Relay function to the lower-level cascaded base stations. The eNodeB configures
routes for and forwards transit data flows based on shared transmission resources. In addition,
users can configure the bandwidths of the specified resource groups to ensure the transmission
fairness between local data flows and transit data flows.
There are two scenarios for 2G/3G and LTE co-transmission:
l Co-transmission with a convergence device
l Co-transmission without a convergence device
3.2 Co-transmission with a Convergence Device

If a convergence device is used, data flows (for services, signaling, and O&M) of a GBTS/
eGBTS/NodeB and an eNodeB converge at the device and are then transmitted over the IP
network. Figure 3-2 shows co-transmission with a convergence device.

eRAN
Figure 3-2 Co-transmission with a convergence device
In this scenario, the convergence device provides the data convergence function. This does
not affect eNodeB operations; however, it does increase the OPEX and management workload
because an additional network element (NE) must be deployed.
NOTE
In this scenario, a router is generally used as the convergence device. The detailed functions of a router
are not described in this document.
3.3 Co-transmission Without a Convergence Device

If no convergence device is used, GBTSs/eGBTSs/NodeBs use IP over E1 or IP over Ethernet
ports to connect to an eNodeB. Data flows (for services, signaling, and O&M) from the
GBTSs/eGBTSs/NodeBs and those from the eNodeB converge at the eNodeB and are then
transmitted over the IP network. Figure 3-3 shows co-transmission without a convergence
device.
Figure 3-3 Co-transmission without a convergence device
The eNodeB implements co-transmission based on multiple ports, IP routing, DHCP relay,
and weighted round robin (WRR) scheduling.

eRAN
Multiple Ports
To achieve co-transmission, the eNodeB must provide at least two E1/T1 or FE/GE physical
ports. One port connects to a base station of another RAT and the other port connects to the IP
bearer network.
IP Routing
The eNodeB, functioning as a convergence node, uses IP routing to forward uplink and
downlink data flows of the lower-level cascaded base stations. By doing this, the eNodeB
implements co-transmission in IP networking mode.
The eNodeB considers data flows of cascaded base stations to be transit data flows and
performs differentiated service scheduling based on the value of the Differentiated Services
Code Point (DSCP) contained within them. The eNodeB cannot identify the service types of
transit data flows. The eNodeB forwards the transit data flows based on two different routing
policies:
l If a destination IP route is used, the eNodeB searches for the output port based on the
destination IP address. It then transmits the transit data flows from the output port to the
destination service node.
l If a source IP route is used, the eNodeB searches for the output port based on the source
IP address. It then transmits the transit data flows from the output port to the destination
service node.
DHCP Relay
Generally, base stations use DHCP to obtain the IP address of packets, requiring that the
DHCP client (the base station) and the DHCP server should be in the same broadcast domain.
In co-transmission mode, however, the cascaded GBTSs/eGBTSs/NodeBs are not in the same
broadcast domain as the DHCP server. In this case, the eNodeB must use the DHCP relay
function to complete the layer-3 DHCP process for all cascaded base stations. The eNodeB
converts DHCP broadcast messages from the cascaded GBTSs/eGBTSs/NodeBs into unicast
messages and then sends them to the DHCP server. After receiving a response from the
DHCP server, the eNodeB forwards the response to the GBTSs/eGBTSs/NodeBs over the
original port.
The eNodeB configures DHCP relay based on the parameters specified in the configuration
file. If DHCP relay is required, the eNodeB obtains information about the DHCP server. The
DHCP relay function can also be manually enabled and applies to all ports on the eNodeB.
Up to four DHCP servers can be configured for an eNodeB.
WRR Scheduling
To prevent GSM/UMTS transit data flows from affecting eNodeB data flows, the eNodeB
configures dedicated transmission resource groups for transit data flows. The eNodeB data
flows use resources in other transmission resource groups. The WRR scheduling function
helps to control the data flows between the transmission resource groups to ensure scheduling
equality.
To perform scheduling for queues in a transmission resource group, the LMPT/UMPT/
UMDU uses priority queue (PQ) or WRR scheduling (non-PQ) so that each queue has a
chance to be scheduled. Each queue is assigned a weighted value based on the bandwidth of
each transmission resource group. The weighted value specifies how much group bandwidth

eRAN
each queue can use for transmission. This ensures equality between transmission resource
groups, while maintaining the differentiation.
NOTE
If the eNodeB provides Internet Protocol Security (IPsec) for the cascaded GSM/UMTS base stations,
configure correct Access Control List (ACL) rules for the cascaded GBTSs/eGBTSs/NodeBs. If the
ACL rules are incorrect, the transmission for the cascaded base stations will fail.

eRAN
Description 4 Related Features
4 Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

eRAN
Description 5 Network Impact
5 Network Impact
System Capacity
After the feature is enabled, the data flows of cascaded base stations are forwarded by the
eNodeB. The uplink and downlink traffic of the cascaded base stations occupies the
transmission bandwidth and affects the forwarding performance of the eNodeB.
Network Performance
After the feature is enabled, services of the cascaded base stations will be interrupted if the
eNodeB is faulty, being upgraded, or experiences transmission interruption.

eRAN
Description 6 Engineering Guidelines
6 Engineering Guidelines
This chapter describes the engineering guidelines for LOFD-003002 2G/3G and LTE Co-
transmission/MLOFD-003002 2G/3G and eNodeB Co-transmission deployment, including
when to use the feature, deployment requirements, deployment process, and data preparation.
6.1 When to Use

eNodeBs rarely use IP over E1/T1 transmission, and IP over Ethernet transmission is
recommended for eNodeBs in LOFD-003002 2G/3G and LTE Co-transmission/
MLOFD-003002 2G/3G and eNodeB Co-transmission scenarios. This document provides
engineering guidelines only for IP over FE/GE scenarios.
For information about the cascaded base station types and networking modes for
LOFD-003002 2G/3G and LTE Co-transmission/MLOFD-003002 2G/3G and eNodeB Co-
transmission, see Table 2-1.
6.2 Required Information

Co-transmission mainly involves DHCP Relay, routing and address planning for IP addresses
of cascaded nodes, and transmission bandwidth planning for the hub. Before deploying
LOFD-003002 2G/3G and LTE Co-transmission/MLOFD-003002 2G/3G and eNodeB Co-
transmission, ensure that common transmission parameters have been configured. For details
about the configurations of common transmission parameters, see IP Transmission Feature
Parameter Description.
6.3 Planning
RF Planning
N/A
Network Planning
N/A

eRAN
Hardware Planning
N/A
6.4 Deployment
6.4.1 Process
You must configure common transmission parameters before enabling LOFD-003002 2G/3G
and LTE Co-transmission/MLOFD-003002 2G/3G and eNodeB Co-transmission. For details,
see IP Transmission Feature Parameter Description.
6.4.2 Requirements
Operating Environment
None
Transmission Networking
None
License
This feature requires the purchase and activation of the license controlling 2G/3G and LTE
Co-transmission. The following table lists the license information.
Feature ID Feature Name Model License Sales Unit

Control Item
LOFD-003002 2G/3G and LTE LT1SCOTRA 2G/3G and LTE Per eNodeB
Co-transmission N00 Co-
transmission(F
DD)
MLOFD-0030 2G/3G and ML1SCOTRA 2G/3G and Per eNodeB

02 eNodeB Co- N00 eNodeB Co-
transmission transmission(N
B-IoT)
6.4.3 Precautions
If a lower-level base station is a NodeB:
l The destination IP address of the DHCP Relay route to the NodeB is the IP address of an
eNodeB port. If the eNodeB has multiple port IP addresses, the routes to all the ports
must be set. You can set the destination IP address on the U2000.
l The next hop of the route from the NodeB to the RNC is the IP address of the eNodeB
port connected to the NodeB.

eRAN
If a lower-level base station is a GBTS/eGBTS:

l The next hop of the route from the GBTS/eGBTS to the BSC is the IP address of the
eNodeB port connected to the GBTS/eGBTS.
l The destination IP address of the DHCP Relay route to the GBTS is the IP address of an
must be set. You can set the destination IP address on the BSC.
l The destination IP address of the DHCP Relay route to the eGBTS is the IP address of an
must be set. You can set the destination IP address on the U2000.
6.4.4 Hardware Adjustment

N/A
6.4.5 Data Preparation and Feature Activation
6.4.5.1 Data Preparation

This section describes the data that you need to collect before setting parameters. There are
three types of data sources:
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Prepare the following data before feature deployment:
l The ETHPORT MO, which specifies the attributes of the Ethernet port for cascading on
the eNodeB. The key parameters in this MO are described in the following table.
Paramete Paramete Data Setting Notes
r Name r ID Source
Subboard ETHPOR Network This parameter specifies the subboard type

Type T.SBT plan of the board that provides the Ethernet port.
(negotiation Set this parameter to BASE_BOARD(Base
not required) Board).

eRAN

r Name r ID Source
Port ETHPOR Network This parameter specifies whether an

Attribute T.PA plan Ethernet port is an electrical port or optical
(negotiation port.
not required) The port attributes of the physical port must
be consistent with that of the peer port. You
are advised to set this parameter to
AUTO(Automatic Detection).
You can also set this parameter based on the
attributes of the physical port.
NOTE
When this parameter is set to AUTO(Automatic
Detection), it takes about 1 minute to activate
the port. If the attribute of the optical port on the
peer device is modified, this modification takes
effect only after this optical port on the peer
device is reset or the Ethernet port on the local
eNodeB is reset by running the RST
ETHPORT command.
Maximum ETHPOR Network This parameter specifies the maximum IP

Transmissi T.MTU plan packet size (including the IP header) at the
on Unit (negotiation Ethernet port.
required) Set this parameter based on the transport
network plan.
Speed ETHPOR Network This parameter specifies the rate mode of

T.SPEED plan the Ethernet port. Set this parameter to the
(negotiation same value as that of the peer port.
required)
Duplex ETHPOR Network This parameter specifies the duplex mode

T.DUPLE plan of the Ethernet port. Set this parameter to
X (negotiation the same value as that of the peer port.
required)
l The DEVIP MO, which specifies the IP address of the port for cascading on the
eNodeB. The key parameters in this MO are described in the following table.
Paramete Paramet Data Setting Notes
r Name er ID Source
Subboard DEVIP.S Network This parameter specifies the subboard type

Type BT plan of the board that provides the Ethernet port.
(negotiation Set this parameter to BASE_BOARD(Base
not required) Board).

eRAN

r Name er ID Source
IP Address DEVIP.I Network This parameter specifies the IP address

P plan configured for a given port. The IP address
(negotiation must be in the same network segment as
not required) those of the lower-level cascaded base
stations.
Mask DEVIP. Network This parameter specifies the subnet mask of

MASK plan the device IP address configured on a port.
(negotiation The device IP address must be in the same
not required) network segment as the port IP addresses of
the lower-level cascaded base stations.
Port Type DEVIP.P Network This parameter specifies the type of the
T plan physical port.
(negotiation l If the eNodeB uses an E1/T1 port to
not required) connect to the transport network, set this
parameter to PPP(PPP Link) or
MPGRP(Multi-link PPP Group).
l If the eNodeB uses an Ethernet port to
connect to the transport network, set this
parameter to ETH(Ethernet Port) or
ETHTRK(Ethernet Trunk).
l The IPRT MO, which specifies a route from the co-transmission port on the eNodeB to
the port of a lower-level cascaded base station. If the cascaded base station is a GBTS or
a NodeB, routes to the BSC or to the RNC and U2000 must be set, respectively. The key
parameters in this MO are described in the following table.
r Name er ID Source
Route IPRT.RT Network This parameter specifies the route index of

Index IDX plan an IP route.
(negotiation
not required)
Destinatio IPRT.DS Network l You are advised not to set both of these
n IP TIP plan parameters to 0.0.0.0.
(negotiation l In cascading scenarios, a route to the
not required) RNC or BSC must be set. The
destination IP address and network
segment are the service IP address and
network segment of the RNC or BSC,
respectively.
l In cascading scenarios, a route to the
logical IP address of the cascaded base
station must be set. The destination IP
address and network segment are the

eRAN

r Name er ID Source
Mask IPRT.DS Network logical IP address and network segment

TMASK plan of the cascaded base station,
(negotiation respectively.
not required)
Subboard IPRT.SB Network This parameter specifies the sub-board type

Type T plan of the board where the IP route is
(negotiation established.
not required) Set this parameter to BASE_BOARD(Base
Board).
Route IPRT.RT Network This parameter specifies the type of route.

Type TYPE plan l If the eNodeB uses an Ethernet port to
(negotiation connect to the transport network, set this
not required) parameter to NEXTHOP(Next Hop).
l If the eNodeB uses an E1 port to
connect to the transport network, set this
parameter to IF(Exit Interface).
Port Type IPRT.IF Network This parameter specifies the type of a port.
T plan If the eNodeB uses an E1 port to connect to
(negotiation the transport network, set this parameter to
not required) PPP(PPP Link) or MPGRP(Multi-link
PPP Group).
Next Hop IPRT.NE Network This parameter specifies the IP address of

IP XTHOP plan the next hop.
(negotiation l This parameter is valid only when the
not required) IPRT.RTTYPE parameter is set to
NEXTHOP(Next Hop).
l Set the parameter to the IP address of
the gateway on the transport network to
which the eNodeB is connected.
Preference IPRT.PR Network This parameter specifies the priority of the

EF plan route.
(negotiation If a backup IP route is required, this
not required) parameter is required to specify the
priorities of the active and backup routes.
The route with the higher priority is
selected as the active route. A smaller value
indicates a higher priority.
The eNodeB does not support route-level
load balancing. Therefore, different routes
to the same destination network segment
must have different priorities.

eRAN
l (Optional) The DHCPRELAYSWITCH MO, which specifies whether to turn on the

DHCP Relay switch on the eNodeB. This switch is turned on only when plug-and-play
(PnP) is used to deploy the base stations cascaded to the eNodeB. The key parameter in
this MO is described in the following table.
r Name r ID Source
DHCP DHCPRE Transport This parameter specifies whether to turn on

Relay LAYSWI planning the DHCP Relay switch.
Switch TCH.ES (internal Set this parameter to ENABLE(Enable).
planning)
l (Optional) The DHCPSVRIP MO, which specifies the IP address of the DHCP server
for the cascaded base stations. The key parameters in this MO are described in the
following table.
r Name r ID Source
DHCP DHCPSV Transport This parameter specifies the IP address of

Server IP RIP.DHC planning the DHCP server.
Address PSVRIP (internal l If the cascaded base station is a NodeB,
planning) set this parameter to the IP address of
the U2000 or RNC.
l If the cascaded base station is a GBTS,
set this parameter to the IP address of
the BSC.
l (Optional) The RSCGRP MO, which specifies dedicated transmission resource groups
for services of the cascaded base stations. The eNodeB data flows use different
transmission resource groups from data flows of the cascaded base stations. The key
parameters in this MO are described in the following table.
Paramet Paramete Data Setting Notes
er Name r ID Source
Transmiss RSCGRP. Network Set this parameter based on the network

ion RSCGRPI plan plan.
Resource D (negotiation You are advised to set different
Group ID not required) transmission resource groups for data flows
of the cascaded base stations and the
eNodeB.
Add a transmission resource group ID only
if you need to measure the performance
counters.

eRAN

er Name r ID Source
Subboard RSCGRP. Network This parameter specifies the subboard type

Type SBT plan of the board where the transmission
(negotiation resource group is configured.
not required) Set this parameter to BASE_BOARD(Base
Board).
Bearing RSCGRP. Network This parameter specifies the type of a port

Port Type PT plan where a transmission resource group is
(negotiation carried.
not required) Set this parameter according to the type of
the physical port connecting the MME and
S-GW.
Tx RSCGRP. Network This parameter specifies the uplink

Bandwidt TXBW plan transport admission bandwidth for a
h (negotiation transmission resource group that carries
not required) eNodeB data flows and TX traffic shaping
bandwidth. This parameter is used in
single-rate mode. Set this parameter based
on the network plan.
Rx RSCGRP. Network This parameter specifies the downlink

Bandwidt RXBW plan transport admission bandwidth for a
h (negotiation transmission resource group that carries
not required) eNodeB data flows and has no impact on
transit data flows.
This parameter is used in single-rate mode.
Set this parameter based on the network
plan.
Tx RSCGRP. Network This parameter specifies the TX committed

Committe TXCBS plan burst size of a transmission resource group.
d Burst (negotiation Set this parameter based on the network
Size not required) plan. The value of RSCGRP.TXCBS must
be greater than or equal to that of
RSCGRP.TXBW for traffic shaping of the
transmission resource group.
TX RSCGRP. Network This parameter specifies the TX excessive

Excessive TXEBS plan burst size of a transmission resource group.
Burst Size (negotiation Set this parameter based on the network
not required) plan. You are advised to set this parameter
to two times that of the TX Bandwidth
value.

eRAN

er Name r ID Source
Schedulin RSCGRP. Network This parameter specifies the scheduling

g Weight WEIGHT plan weight of a transmission resource group.
(negotiation This parameter is used in calculating the
not required) bandwidth scheduled to a resource group,
which helps achieve the user admission
control.
plan in case of physical bandwidth
restriction. You are advised to retain the
default value.
TX RSCGRP. Network This parameter specifies the transmit

Committe TXCIR plan committed information rate (CIR) of the
d (negotiation transmission resource group, which is a
Informati not required) guaranteed rate assigned by the operator.
on Rate Set this parameter based on the network
plan. This parameter is used in double-rate
mode. The parameter value is used as the
uplink transport admission bandwidth for a
transmission resource group that carries
eNodeB data flows and TX traffic shaping
bandwidth for eNodeB or transit data
flows.
RX RSCGRP. Network This parameter specifies the receive CIR of

Committe RXCIR plan the transmission resource group, which is a
d (negotiation guaranteed rate assigned by the operator.
Informati not required) This parameter value is used as the
on Rate downlink transport admission bandwidth
for services that do not need flow control.
downlink transport admission bandwidth
for a transmission resource group that
carries eNodeB data flows.
TX Peak RSCGRP. Network This parameter specifies the peak

Informati TXPIR plan information rate (PIR) of the transmission
on Rate (negotiation resource group.
not required) Set this parameter based on the network
uplink transport admission bandwidth for a
transmission resource group that carries
eNodeB data flows and TX traffic shaping
bandwidth for eNodeB or transit data
flows.

eRAN

er Name r ID Source
RX Peak RSCGRP. Network This parameter specifies the receive PIR of

Informati RXPIR plan the transmission resource group. This
on Rate (negotiation parameter value is used as the downlink
not required) transport admission bandwidth for a
transmission resource group.
This parameter is used in double-rate mode.
plan.
TX Peak RSCGRP. Network This parameter specifies the size of the

Burst Size TXPBS plan peak burst transmitted from the
(negotiation transmission resource group.
not required) Set this parameter based on the network
plan. The value of RSCGRP.TXPBS must
be greater than or equal to that of
RSCGRP.TXCBS. The value of
RSCGRP.TXPBS must be greater than or
equal to that of RSCGRP.TXPIR.
l (Optional) The IP2RSCGRP MO, which specifies a dedicated transmission resource

group for services of the cascaded base stations. This document does not describe how to
specify a transmission resource group for local data flows. For detailed operations, see
Transport Resource Management Feature Parameter Description. The key parameters in
this MO are described in the following table.
r Name r ID Source
Mapping IP2RSCG Network This parameter specifies the mapping

Index RP.MAPI plan between an IP address and the transmission
DX (negotiation resource group. This parameter is used to
not required) specify the mapping transmission resource
group for transit data flows.
Transmiss IP2RSCG Network This parameter specifies the bearer type of

ion RP.BEAR plan a transmission resource group. Set this
Resource (negotiation parameter to IP(IP).
Group not required)
Bear Type
Bearing IP2RSCG Network This parameter specifies the type of a port

Port Type RP.PT plan where a transmission resource group is
(negotiation carried. This parameter is used to specify
not required) the type of eNodeB port, which transit data
flows are transmitted through.

eRAN

r Name r ID Source
Bearing IP2RSCG Network This parameter specifies the number of a

Port No. RP.PN plan port where a transmission resource group is
(negotiation carried. This parameter is used to specify
not required) the number of an eNodeB port, which
transit data flows are transmitted through.
Transmiss IP2RSCG Network This parameter specifies the ID of a

ion RP.RSCG plan transmission resource group. This
Resource RPID (negotiation parameter is used to specify the ID of a
Group ID not required) transmission resource group for transit data
flows that are sent through the eNodeB.
Destinatio IP2RSCG Network This parameter specifies the destination IP

n IP RP.DSTI plan address of the data flow that is bound to a
P (negotiation transmission resource group. This
not required) parameter is used to specify a destination IP
address for transit data flows.
Mask IP2RSCG Network This parameter specifies the subnet mask of

RP.DSTM plan the destination IP address of the data flow
ASK (negotiation that is bound to a transmission resource
not required) group. This parameter is used to specify a
subnet mask of the destination IP address
for transit data flows.
6.4.5.2 Activation
Using the CME

l Fast batch activation
This feature can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Feature Operation and Maintenance.
l Single/batch configuration
This feature can be activated for a single eNodeB or a batch of eNodeBs on the CME.
For detailed operations, see CME-based Feature Configuration.
Using MML Commands

Perform the following steps on the eNodeB:
Step 1 Run the SET ETHPORT command to set the attribute of the Ethernet port cascaded to the
eNodeB.
Step 2 Run the ADD DEVIP command to add the device IP address of the Ethernet port cascaded to
the eNodeB. Ensure that the IP addresses of the interconnected ports are on the same network
segment.

eRAN
Step 3 Run the ADD IPRT command to add the routes from the eNodeB to the peer devices of the
lower-level cascaded base stations.
l If the cascaded base station is a GBTS/eGBTS, the peer device is the BSC.
l If the cascaded base station is a NodeB, the peer devices are the RNC and U2000.
Step 4 (Optional) Run the SET DHCPRELAYSWITCH command to turn on the DHCP Relay
switch.
Step 5 (Optional) Run the ADD DHCPSVRIP command to set the IP address of the DHCP server
for the cascaded base stations.
l If the cascaded base station is a GBTS/eGBTS, the DHCP server is the BSC.
l If the cascaded base station is a NodeB, the DHCP server is the RNC or U2000.
Step 6 (Optional) If transit data flows need to be classified for transmission, run the ADD RSCGRP
command to add a transmission resource group for user-plane resource management.
Step 7 (Optional) If transit data flows need to be classified for transmission, run the ADD
IP2RSCGRP command to add the transit data flows to a specified transmission resource
group.
----End
MML Command Examples

//Setting the attribute of the Ethernet port cascaded to the eNodeB
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=1, PA=FIBER,
MTU=1500, SPEED=1000M, DUPLEX=FULL, ARPPROXY=ENABLE, FC=OPEN,
FERAT=10, FERDT=10;
//Setting the device IP address of the Ethernet port cascaded to the eNodeB
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=1, IP="10.2.2.2",
MASK="255.255.255.0";
//Adding the route from the eNodeB to the peer device of the lower-level cascaded base
station (GBTS in this example)
//Using a destination IP route
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="100.3.3.3",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.2", PREF=60;
//Using a source IP route
ADD SRCIPRT:
SRCRTIDX=1,SN=7,SBT=BASE_BOARD,SRCIP="10.2.2.1",RTTYPE=NEXTHOP,NEXT
HOP="10.1.1.2";
//Turning on the DHCP Relay switch on the eNodeB
SET DHCPRELAYSWITCH: ES=ENABLE;
//Setting the IP address of the DHCP server for the GBTS
ADD DHCPSVRIP: DHCPSVRIP="100.3.3.3";
//Adding a transmission resource group for transit data flows

eRAN
ADD RSCGRP:SN=7,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0,RU=KBPS;
//Adding the transit data flows to a specified transmission resource group
ADD
IP2RSCGRP:MAPIDX=0,SN=7,SBT=BASE_BOARD,PT=ETH,DSTIP="100.3.3.3",DSTM
ASK="255.255.255.0";
6.4.6 Activation Observation

Perform the following steps on the eNodeB to check whether the transmission links from the
eNodeB to the MME and S-GW are normal:
Step 1 Ping the IP addresses of the MME and the S-GW on the eNodeB. If the ping operations
succeed, the transmission links are normal.
Step 2 Ping the IP address of the NodeB on the RNC and the IP addresses of the GBTS and eGBTS
on the BSC. If the ping operations succeed, the feature has been enabled.
----End
6.4.7 Reconfiguration
None
6.4.8 Deactivation
None
6.5 Performance Monitoring

You can monitor transit data flows using the Monitoring Local Pass-By Traffic function on
the eNodeB LMT.
If transit data flows are added to an independent transmission resource group, you can
monitor the transmit/receive rate and throughput of the transmission resource group using the
Monitoring Transport Port Traffic function.
6.6 Parameter Optimization

N/A
6.7 Possible Issues

For details about IP transmission fault location and troubleshooting, see the eRAN
troubleshooting guide.

eRAN
Description 7 Parameters
7 Parameters
Table 7-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
ETHPO SBT ADD None None Meaning: Indicates the type of sub-board on the board
RT ETHPO where the Ethernet port is located.
RT GUI Value Range: BASE_BOARD(Base Board),
DSP ETH_COVERBOARD(Ethernet Cover Board)
ETHPO Unit: None
RT
Actual Value Range: BASE_BOARD,
RMV ETH_COVERBOARD
ETHPO
RT Default Value: None
RST
ETHPO
RT
SET
ETHPO
RT
LST
ETHPO
RT

eRAN

nd
ETHPO PA ADD WRFD- IP Meaning: Indicates whether an Ethernet port is an

RT ETHPO 050402 Transmi electrical port or optical port. When the system starts,
RT ssion the system binds an Ethernet port to an electrical port
SET Introduc preferentially if the default value of the port attribute
ETHPO tion on is AUTO. If the BS does not support cascading, the
RT Iub port attribute is set to AUTO. If this parameter is
Interface incorrectly set, services of a base station will be
DSP interrupted after the base station is reset.
DHCPR
SLT GUI Value Range: COPPER(Copper), FIBER(Fiber),
AUTO(Automatic Detection), UNCONFIG(Not
DSP Configured)
ETHPO
RT Unit: None
LST Actual Value Range: COPPER, FIBER, AUTO,
ETHPO UNCONFIG
RT Default Value: None
ETHPO MTU ADD WRFD- IP Meaning: Indicates the maximum IP packet size
RT ETHPO 050402 Transmi (including the IP header) at the Ethernet port. For the
RT ssion UMPT, UMDU, LMPT, UCCU, and UTRPc, the
SET Introduc value of this parameter ranges from 46 to 1800. For
ETHPO tion on the WMPT, GTMUb, GTMUc, UQEC, and UEOC,
RT Iub the value of this parameter ranges from 46 to 1500. If
Interface this parameter is set to a value greater than the
DSP maximum allowed value, the maximum allowed value
ETHPO takes effect. A value greater than or equal to 776 is
RT recommended, because broadcast packets, such as
LST DHCP packets, may experience reception or
ETHPO transmission failures if the maximum transmission
RT unit is smaller than 776. If the Ethernet port is added
to an Ethernet trunk, this parameter becomes invalid.
The actual maximum transmission unit depends on the
value set for the Ethernet trunk.
GUI Value Range: 46~1800
Unit: byte
Actual Value Range: 46~1800
Default Value: 1500

eRAN

nd
ETHPO SPEED ADD WRFD- IP Meaning: Indicates the speed mode of the Ethernet
RT ETHPO 050402 Transmi port. This parameter must be set to the same value as
RT ssion that of the peer port. GE electrical ports of base board
SET Introduc support 1000 Mbit/s only when working in auto-
ETHPO tion on negotiation mode. If SPEED of a GE optical port is set
RT Iub to AUTO, the port works at 1000 Mbit/s in auto-
Interface negotiation mode. If SPEED of a GE optical port is set
DSP to 1000M, the port works at 1000 Mbit/s in manual
DHCPR configuration mode.
SLT
GUI Value Range: 10M(10M), 100M(100M),
LST 1000M(1000M), AUTO(Automatic Negotiation),
ETHPO 10G(10G), 40G(40G), UNCONFIG(Not Configured)
RT
Unit: None
Actual Value Range: 10M, 100M, 1000M, AUTO,
10G, 40G, UNCONFIG
Default Value: AUTO(Automatic Negotiation)
ETHPO DUPLE ADD WRFD- IP Meaning: Indicates the duplex mode of the Ethernet
RT X ETHPO 050402 Transmi port.
RT ssion GUI Value Range: FULL(Full Duplex),
SET Introduc AUTO(Automatic Negotiation), UNCONFIG(Not
ETHPO tion on Configured)
RT Iub
Interface Unit: None
DSP Actual Value Range: FULL, AUTO, UNCONFIG
DHCPR
SLT Default Value: FULL(Full Duplex)
LST
ETHPO
RT
DEVIP SBT ADD None None Meaning: Indicates the type of sub-board on the board
DEVIP where a port is located.
MOD GUI Value Range: BASE_BOARD(Base Board),
DEVIP E1_COVERBOARD(E1 Cover Board),
RMV BACK_BOARD(Back Board),
DEVIP ETH_COVERBOARD(Ethernet Cover Board)
DSP Unit: None
DEVIP Actual Value Range: BASE_BOARD,
LST E1_COVERBOARD, BACK_BOARD,
DEVIP ETH_COVERBOARD
Default Value: None

eRAN

nd
DEVIP IP ADD WRFD- IP Meaning: Indicates the IP address configured for the
DEVIP 050402 Transmi port.
MOD WRFD- ssion GUI Value Range: Valid IP address
DEVIP 050411 Introduc
tion on Unit: None
RMV Iub Actual Value Range: Valid IP address
DEVIP Interface Default Value: None
DSP Fraction
DEVIP al IP
DSP Function
MULTI on Iub
CASTIP Interface
LST
DEVIP
DEVIP MASK ADD WRFD- IP Meaning: Indicates the subnet mask of the device IP
DEVIP 050402 Transmi address configured on the port.
DSP WRFD- ssion GUI Value Range: Valid subnet mask
DEVIP 050411 Introduc
tion on Unit: None
LST Iub Actual Value Range: Valid subnet mask
DEVIP Interface Default Value: None
Fraction
al IP
Function
on Iub
Interface
DEVIP PT ADD None None Meaning: Indicates the type of the port. The UMTS
DEVIP currently does not support SUBIF.
MOD GUI Value Range: PPP(PPP Link), MPGRP(Multi-
DEVIP link PPP Group), ETH(Ethernet Port),
RMV ETHTRK(Ethernet Trunk), LOOPINT(Loopback
DEVIP Interface), SUBIF(Sub-interface), ETHCI(Ethernet CI
Port)
DSP
DEVIP Unit: None
LST Actual Value Range: PPP, MPGRP, ETH, ETHTRK,
DEVIP LOOPINT, SUBIF, ETHCI
Default Value: None

eRAN

nd
IPRT RTIDX ADD GBFD-1 Abis Meaning: Indicates the index of an IP route.
IPRT 18601 over IP GUI Value Range: 0~149
MOD GBFD-1 Abis IP Unit: None
IPRT 18611 over
E1/T1 Actual Value Range: 0~149
RMV
IPRT Default Value: None
LST
IPRT
IPRT DSTIP ADD WRFD- IP Meaning: Indicates the destination IP address of the
IPRT 050402 Transmi route.
MOD WRFD- ssion GUI Value Range: Valid IP address
IPRT 050107 Introduc
tion on Unit: None
DSP Iub Actual Value Range: Valid IP address
IPRT Interface Default Value: None
LST IP
IPRT routing
Based
Hub
Node B
IPRT DSTMA ADD WRFD- IP Meaning: Indicates the subnet mask for the destination
SK IPRT 050402 Transmi IP address of the route.
MOD WRFD- ssion GUI Value Range: Valid subnet mask
IPRT 050107 Introduc
tion on Unit: None
DSP Iub Actual Value Range: Valid subnet mask
IPRT Interface Default Value: None
LST IP
IPRT routing
Based
Hub
Node B

eRAN

nd
IPRT SBT ADD None None Meaning: Indicates the type of sub-board on the board
IPRT where the IP route is established.
MOD GUI Value Range: BASE_BOARD(Base Board),
IPRT UNCHANNELLED_COVERBOARD(Unchannelled
LST Cover Board), E1_COVERBOARD(E1 Cover Board),
IPRT BACK_BOARD(Back Board),
ETH_COVERBOARD(Ethernet Cover Board)
Unit: None
Actual Value Range: BASE_BOARD,
UNCHANNELLED_COVERBOARD,
E1_COVERBOARD, BACK_BOARD,
ETH_COVERBOARD
Default Value: None
IPRT RTTYP ADD WRFD- IP Meaning: Indicates the type of route. If this parameter
E IPRT 050402 Transmi is set to NEXTHOP, all the IP packets that meet the
MOD WRFD- ssion route direction are first forwarded to the specified next
IPRT 050107 Introduc hop IP address. If this parameter is set to IF, all the IP
tion on packets that meet the route direction are first
DSP Iub forwarded to the specified egress port.
IPRT Interface GUI Value Range: NEXTHOP(Next Hop), IF(Exit
LST IP Interface)
IPRT routing Unit: None
Based
Hub Actual Value Range: NEXTHOP, IF
Node B Default Value: None
IPRT IFT ADD WRFD- IP Meaning: Indicates the port type.

IPRT 050402 Transmi GUI Value Range: PPP(PPP Link), MPGRP(Multi-
MOD WRFD- ssion link PPP Group), TUNNEL(Tunnel), IPOA(IP Over
IPRT 050107 Introduc ATM Interface), AIRLNK(Air Link)
tion on
LST Iub Unit: None
IPRT Interface Actual Value Range: PPP, MPGRP, TUNNEL, IPOA,
IP AIRLNK
routing Default Value: PPP(PPP Link)
Based
Hub
Node B

eRAN

nd
IPRT NEXTH ADD WRFD- IP Meaning: Indicates the IP address of the next hop.
OP IPRT 050402 Transmi GUI Value Range: Valid IP address
MOD WRFD- ssion
Introduc Unit: None
IPRT 050107
tion on Actual Value Range: Valid IP address
DSP Iub
IPRT Default Value: 0.0.0.0
Interface
LST IP
IPRT routing
Based
Hub
Node B
IPRT PREF ADD WRFD- IP Meaning: Indicates the priority of the routing table
IPRT 050402 Transmi entry. A smaller parameter value indicates a higher
MOD WRFD- ssion priority.
IPRT 050107 Introduc GUI Value Range: 1~255
tion on
DSP Iub Unit: None
IPRT Interface Actual Value Range: 1~255
LST IP Default Value: 60
IPRT routing
Based
Hub
Node B
DHCPR ES SET MRFD- IP- Meaning: Indicates whether to enable the DHCP relay
ELAYS DHCPR 121124 Based switch.
WITCH ELAYS WRFD- Multi- GUI Value Range: DISABLE(Disable),
WITCH 031101 mode ENABLE(Enable)
LST Co-
Transmi Unit: None
DHCPR
ELAYS ssion on Actual Value Range: DISABLE, ENABLE
WITCH BS Default Value: DISABLE(Disable)
side(No
deB)
NodeB
Self-
discover
y Based
on IP
Mode

eRAN

nd
DHCPS DHCPS ADD WRFD- NodeB Meaning: Indicates the IP address of the DHCP server.
VRIP VRIP DHCPS 031101 Self- GUI Value Range: Valid IP address
VRIP MRFD- discover
y Based Unit: None
MOD 121124
DHCPS on IP Actual Value Range: Valid IP address
VRIP Mode Default Value: None
RMV IP-
DHCPS Based
VRIP Multi-
mode
LST Co-
DHCPS Transmi
VRIP ssion on
BS
side(No
deB)
RSCGR RSCGR ADD WRFD- Transmi Meaning: Indicates the ID of a transmission resource
P PID RSCGR 0213040 ssion group. When you use an MML command to add a PPP
P 6 Recours link, an MP group, an Ethernet port, an Ethernet trunk,
DSP e a tunnel, or a PPPoE link, the system automatically
RSCGR Sharing creates a transmission resource group with
P on Transmission Resource Group ID set to
Iub/Iur DEFAULTPORT(Default Port). When you remove
MOD Interface any of the preceding objects, the system automatically
RSCGR removes the transmission resource group. When you
P add a PPP link, an MP group, an Ethernet port, an
RMV Ethernet trunk, or an uplink tunnel on the CME, if the
RSCGR default transmission resource group does not exist, the
P system automatically creates a transmission resource
LST group with Transmission Resource Group ID set to
RSCGR AUTOPORT(Autoport Port). When you remove any
P of the preceding objects, the system automatically
removes the transmission resource group.
GUI Value Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,
13, 14, 15, AUTOPORT(Auto Port),
DEFAULTPORT(Default Port)
Unit: None
Actual Value Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,
12, 13, 14, 15, AUTOPORT, DEFAULTPORT
Default Value: None

eRAN

nd
RSCGR SBT ADD None None Meaning: Indicates the type of sub-board on the
P RSCGR transmission group. The LTE currently does not
P support UNCHANNELLED_COVERBOARD.
DSP GUI Value Range: BASE_BOARD(Base Board),
RSCGR UNCHANNELLED_COVERBOARD(Unchannelled
P Cover Board), E1_COVERBOARD(E1 Cover Board),
MOD BACK_BOARD(Back Board),
RSCGR ETH_COVERBOARD(Ethernet Cover Board)
P Unit: None
RMV Actual Value Range: BASE_BOARD,
RSCGR UNCHANNELLED_COVERBOARD,
P E1_COVERBOARD, BACK_BOARD,
LST ETH_COVERBOARD
RSCGR Default Value: None
P
RSCGR PT ADD None None Meaning: Indicates the type of port where a
P RSCGR transmission resource group is carried. The LTE
P currently does not support STM1, IMA, UNI, or
DSP FRAATM.
RSCGR GUI Value Range: IMA(IMA Group), UNI(UNI
P Link), STM1(STM1), FRAATM(FRAATM Link),
MOD PPP(PPP Link), MPGRP(Multi-link PPP Group),
RSCGR ETH(Ethernet Port), ETHTRK(Ethernet Trunk),
P TUNNEL(Tunnel)
RMV Unit: None
RSCGR Actual Value Range: IMA, UNI, STM1, FRAATM,
P PPP, MPGRP, ETH, ETHTRK, TUNNEL
LST Default Value: None
RSCGR
P

eRAN

nd
RSCGR TXBW ADD WRFD- Transmi Meaning: Indicates the maximum uplink bandwidth of
P RSCGR 0213040 ssion a transmission resource group at the MAC layer when
P 6 Recours the transmission resource group is carried over IP.
MOD e This parameter value is used as the uplink transport
RSCGR Sharing admission bandwidth and TX traffic shaping
P on bandwidth. The minimum rate supported by the
Iub/Iur UMPTa, UMPTb, UMPTe, UMDU, GTMUb or
DSP Interface GTMUc is 64 kbit/s. The LMPT can be configured
RSCGR with a maximum of 360 Mbit/s TX bandwidth. The
P WMPT, GTMUb or GTMUc can be configured with a
LST maximum of 300 Mbit/s TX bandwidth. The UMPTa,
RSCGR UMPTb, UMDU or UTRPc can be configured with a
P maximum of 1 Gbit/s TX bandwidth. The UMPTe or
UCCU can be configured with a maximum of 10
Gbit/s TX bandwidth. The UBBPe, UBBPei,
UBBPep, UBBPem, UBBPex2, UBBPf0 or LCOP can
be configured with a maximum of 40 Gbit/s TX
bandwidth. If the parameter is set to a value greater
than the maximum TX bandwidth supported by a
board, the maximum TX bandwidth supported by the
board takes effect. For a WMPT and a UTRP
(excluding UTRPa), this parameter does not specify
the TX traffic shaping bandwidth of the transmission
resource group that is carried on the PPP link.
Unit: None
Default Value: None

eRAN

nd
RSCGR RXBW ADD WRFD- Transmi Meaning: Indicates the RX bandwidth of a

P RSCGR 0213040 ssion transmission resource group. To LTE, this parameter
P 6 Recours value is also used as the downlink transport admission
MOD WRFD- e bandwidth. The minimum rate supported by the
RSCGR 0106101 Sharing UMPTa, UMPTb, UMPTe, UMDU, GMTUb or
P 0 on GTMUc is 64 kbit/s. The LMPT can be configured
Iub/Iur with a maximum of 540 Mbit/s RX bandwidth. The
DSP Interface WMPT, GTMUb or GTMUc can be configured with a
RSCGR maximum of 300 Mbit/s RX bandwidth. The UMPTa,
P HSDPA
Flow UMPTb, UMDU or UTRPc can be configured with a
LST Control maximum of 1 Gbit/s RX bandwidth. The UMPTe or
RSCGR UCCU can be configured with a maximum of 10
P Gbit/s RX bandwidth. The UBBPe, UBBPei,
UBBPep, UBBPem, UBBPex2, UBBPf0 or LCOP can
be configured with a maximum of 40 Gbit/s RX
bandwidth. The value of RX bandwidth is set to the
maximum value of RX bandwidth supported by the
board when it bigger than the maximum one.
Unit: None
Default Value: None
RSCGR TXCBS ADD WRFD- Transmi Meaning: Indicates the TX committed burst size of a
P RSCGR 0213040 ssion transmission resource group. The LMPT can be
P 6 Recours configured with a maximum of 400 Mbit/s TX
MOD e committed burst size. The WMPT can be configured
RSCGR Sharing with a maximum of 600 Mbit/s TX committed burst
P on size. The WMPT, GTMUb or GTMUc can be
Iub/Iur configured with a maximum of 600 Mbit/s TX
LST Interface committed burst size. The UMPTa, UMPTb, UMDU
RSCGR or UTRPc can be configured with a maximum of 1
P Gbit/s TX committed burst size. The UMPTe or
UCCU can be configured with a maximum of 10
Gbit/s TX committed burst size. The UBBPe,
UBBPei, UBBPep, UBBPem, UBBPex2, UBBPf0 or
LCOP can be configured with a maximum of 40
Gbit/s TX committed burst size. The value of TX
committed burst size is set to the maximum value of
TX committed burst size supported by the board when
it bigger than the maximum one.
Unit: kbit
Default Value: 64

eRAN

nd
RSCGR TXEBS ADD WRFD- Transmi Meaning: Indicates the TX excessive burst size of a
MOD e excessive burst size. The WMPT, GTMUb or GTMUc
RSCGR Sharing can be configured with a maximum of 600 Mbit/s TX
P on excessive burst size. The UMPTa, UMPTb, UMDU or
Iub/Iur UTRPc can be configured with a maximum of 1
LST Interface Gbit/s TX excessive burst size. The UMTPe or UCCU
RSCGR can be configured with a maximum of 10 Gbit/s TX
P excessive burst size. The UBBPe, UBBPei, UBBPep,
UBBPem, UBBPex2, UBBPf0 or LCOP can be
configured with a maximum of 40 Gbit/s TX
excessive burst size. The value of TX excessive burst
size is set to the maximum value of TX excessive
burst size supported by the board when it bigger than
the maximum one.
Unit: kbit
Default Value: 1000000
RSCGR WEIGH ADD WRFD- Transmi Meaning: Indicates the scheduling weight of a
P T RSCGR 0213040 ssion transmission resource group. This parameter is used in
P 6 Recours calculating the bandwidth scheduled to a resource
MOD e group, which helps achieve the user admission
RSCGR Sharing control.
P on GUI Value Range: 1~100
Iub/Iur
LST Interface Unit: None
RSCGR Actual Value Range: 1~100
P
Default Value: 100

eRAN

nd
RSCGR TXCIR ADD WRFD- Transmi Meaning: Indicates the transmit CIR of the
MOD e committed information rate. The UMPTa, UMPTb,
RSCGR Sharing UMDU or UTRPc can be configured with a maximum
P on of 1 Gbit/s TX committed information rate. The
Iub/Iur GTMUb or GTMUc can be configured with a
LST Interface maximum of 300 Mbit/s TX committed information
RSCGR rate. The UMPTe or UCCU can be configured with a
P maximum of 10 Gbit/s TX committed information
rate. The UBBPe, UBBPei, UBBPep, UBBPem,
UBBPf0 or LCOP can be configured with a maximum
of 40 Gbit/s TX committed information rate. The
value of TX committed information rate is set to the
maximum value of TX committed information rate
supported by the board when it bigger than the
maximum one.
Unit: None
Default Value: None
RSCGR RXCIR ADD WRFD- Transmi Meaning: Indicates the receive CIR of the
P RSCGR 0213040 ssion transmission resource group. This parameter value is
P 6 Recours used as the downlink transport admission bandwidth
MOD e for non-flow-control services. The LMPT can be
RSCGR Sharing configured with a maximum of 540 Mbit/s RX
P on committed information rate. The UMPTa, UMPTb,
Iub/Iur UMDU or UTRPc can be configured with a maximum
LST Interface of 1 Gbit/s RX committed information rate. The
RSCGR UMPTe or UCCU can be configured with a maximum
P of 10 Gbit/s RX committed information rate. The
UBBPe, UBBPei, UBBPep, UBBPem, UBBPex2,
UBBPf0 or LCOP can be configured with a maximum
of 40 Gbit/s RX committed information rate. The
value of RX committed information rate is set to the
maximum value of RX committed information rate
supported by the board when it bigger than the
maximum one. Only the LTE supports this function
currently.
Unit: None
Default Value: None

eRAN

nd
RSCGR TXPIR ADD WRFD- Transmi Meaning: Indicates the transmit PIR of the
P 6 Recours configured with a maximum of 360 Mbit/s TX peak
MOD e information rate. The UMPTa, UMPTb, UMDU or
RSCGR Sharing UTRPc can be configured with a maximum of 1
P on Gbit/s TX peak information rate. The GTMUb or
Iub/Iur GTMUc can be configured with a maximum of 300
LST Interface Mbit/s TX peak information rate. The UMPTe or
RSCGR UCCU can be configured with a maximum of 10
P Gbit/s TX peak information rate. The UBBPe,
UBBPei, UBBPep, UBBPem, UBBPex2, UBBPf0 or
Gbit/s TX peak information rate. The value of TX
peak information rate is set to the maximum value of
TX peak information rate supported by the board
when it bigger than the maximum one.
Unit: None
Default Value: None
RSCGR RXPIR ADD WRFD- Transmi Meaning: Indicates the receive PIR of the
P RSCGR 0213040 ssion transmission resource group. This parameter value is
P 6 Recours used as the downlink transport admission bandwidth.
MOD e The LMPT can be configured with a maximum of 540
RSCGR Sharing Mbit/s RX peak information rate. The UMPTa,
P on UMPTb, UMDU or URTPc can be configured with a
Iub/Iur maximum of 1 Gbit/s RX peak information rate. The
LST Interface UMPTe or UCCU can be configured with a maximum
RSCGR of 10 Gbit/s RX peak information rate. The UBBPe,
P UBBPei, UBBPep, UBBPem, UBBPex2, UBBPf0 or
Gbit/s RX peak information rate. The value of RX
peak information rate is set to the maximum value of
RX peak information rate supported by the board
when it bigger than the maximum one. Only the LTE
supports this function currently.
Unit: None
Default Value: None

eRAN

nd
RSCGR TXPBS ADD WRFD- Transmi Meaning: Indicates the size of the peak burst
P RSCGR 0213040 ssion transmitted from the transmission resource group. The
P 6 Recours LMPT can be configured with a maximum of 540
MOD e Mbit/s TX peak burst size. The UMPTa, UMPTb,
RSCGR Sharing UMDU or UTRPc can be configured with a maximum
P on of 1 Gbit/s TX peak burst size. The GTMUb or
Iub/Iur GTMUc can be configured with a maximum of 300
LST Interface Mbit/s TX peak burst size. The UMPTe or UCCU can
RSCGR be configured with a maximum of 10 Gbit/s TX peak
P burst size. The UBBPe, UBBPei, UBBPep, UBBPem,
UBBPex2, UBBPf0 or LCOP can be configured with
a maximum of 40 Gbit/s TX peak burst size. If the
parameter is set to a value greater than the maximum
TX peak burst size supported by a board, the
maximum TX peak burst size supported by the board
takes effect.
Unit: kbit
Default Value: None
IP2RSC MAPID ADD None None Meaning: Indicates the mapping between IP addresses
GRP X IP2RSC and Transport Resource Groups.
GRP GUI Value Range: 0~127
RMV Unit: None
IP2RSC
GRP Actual Value Range: 0~127
LST Default Value: None

IP2RSC
GRP

eRAN

nd
IP2RSC BEAR ADD MRFD- IP- Meaning: Indicates the bearer type of a transmission
GRP IP2RSC 121124 Based resource group.
GRP WRFD- Multi- GUI Value Range: IP(IP)
LST 0213040 mode
Co- Unit: None
IP2RSC 6
GRP Transmi Actual Value Range: IP
ssion on Default Value: IP(IP)
BS
side(No
deB)
Transmi
ssion
Recours
e
Sharing
on
Iub/Iur
Interface
IP2RSC PT ADD None None Meaning: Indicates the type of port where a
GRP IP2RSC transmission resource group is carried.
GRP GUI Value Range: PPP(PPP Link), MPGRP(Multi-
LST link PPP Group), ETH(Ethernet Port),
IP2RSC ETHTRK(Ethernet Trunk), TUNNEL(Tunnel)
GRP Unit: None
Actual Value Range: PPP, MPGRP, ETH, ETHTRK,
TUNNEL
Default Value: None
IP2RSC PN ADD None None Meaning: Indicates the number of the port where a
GRP IP2RSC transmission resource group is carried.
GRP GUI Value Range: 0~15
LST Unit: None
IP2RSC
GRP Actual Value Range: 0~15
Default Value: 0

eRAN

nd
IP2RSC RSCGR ADD MRFD- IP- Meaning: Indicates the ID of a transmission resource
GRP PID IP2RSC 121124 Based group.
GRP WRFD- Multi- GUI Value Range: 0~15
LST 0213040 mode
Co- Unit: None
IP2RSC 6
GRP Transmi Actual Value Range: 0~15
ssion on Default Value: 0
BS
side(No
deB)
Transmi
ssion
Recours
e
Sharing
on
Iub/Iur
Interface
IP2RSC DSTIP ADD MRFD- IP- Meaning: Indicates the destination IP address of the
GRP IP2RSC 121124 Based service flow that is bound to a transmission resource
GRP WRFD- Multi- group.
LST 0213040 mode GUI Value Range: Valid IP address
IP2RSC 6 Co-
Transmi Unit: None
GRP
ssion on Actual Value Range: Valid IP address
BS Default Value: None
side(No
deB)
Transmi
ssion
Recours
e
Sharing
on
Iub/Iur
Interface

eRAN

nd
IP2RSC DSTMA ADD MRFD- IP- Meaning: Indicates the subnet mask of the destination
GRP SK IP2RSC 121124 Based IP address of the service traffic bound to a
GRP WRFD- Multi- transmission resource group.
LST 0213040 mode GUI Value Range: Valid subnet mask
IP2RSC 6 Co-
Transmi Unit: None
GRP
ssion on Actual Value Range: Valid subnet mask
BS Default Value: None
side(No
deB)
Transmi
ssion
Recours
e
Sharing
on
Iub/Iur
Interface

eRAN
Description 8 Counters
8 Counters
Table 8-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526733176 L.TRPIP.TxBytes Number of bytes of Multi-mode: None 2G/3G and LTE

the control-plane GSM: None Co-transmission
and user-plane data 2G/3G and LTE
sent at the IP layer UMTS: None
Co-transmission
over the eNodeB LTE:
transmission LBFD-003008 2G/3G and eNodeB
interfaces Co-transmission
TDLOFD-003002
MLOFD-003002
1526733177 L.TRPIP.RxBytes Number of bytes of Multi-mode: None 2G/3G and LTE

the control-plane GSM: None Co-transmission
received at the IP UMTS: None
Co-transmission
layer over the LTE:
eNodeB LBFD-003008 2G/3G and eNodeB
transmission Co-transmission
TDLOFD-003002
interfaces
MLOFD-003002
1526733178 L.TRPIP.TxPackets Number of the Multi-mode: None 2G/3G and LTE

control-plane and GSM: None Co-transmission
user-plane packets 2G/3G and LTE
sent at the IP layer UMTS: None
Co-transmission
over the eNodeB LTE:
TDLOFD-003002
MLOFD-003002

eRAN
Description 8 Counters
Counter ID Counter Name Counter Feature ID Feature Name

Description
1526733179 L.TRPIP.RxPackets Number of the Multi-mode: None 2G/3G and LTE

control-plane and GSM: None Co-transmission
user-plane packets 2G/3G and LTE
received at the IP UMTS: None
Co-transmission
layer over the LTE:
eNodeB LBFD-003008 2G/3G and eNodeB
transmission Co-transmission
TDLOFD-003002
interfaces
MLOFD-003002
1526733180 L.TRPIP.TxMeanS Average TX rate of Multi-mode: None 2G/3G and LTE

peed the control-plane GSM: None Co-transmission
at the IP layer over UMTS: None
Co-transmission
the eNodeB LTE:
TDLOFD-003002
MLOFD-003002
1526733181 L.TRPIP.TxMaxSp Maximum TX rate Multi-mode: None 2G/3G and LTE

eed of the control-plane GSM: None Co-transmission
Co-transmission
the eNodeB LTE:
TDLOFD-003002
MLOFD-003002
1526733182 L.TRPIP.RxMeanS Average RX rate of Multi-mode: None 2G/3G and LTE

peed the control-plane GSM: None Co-transmission
Co-transmission
the eNodeB LTE:
TDLOFD-003002
MLOFD-003002
1526733183 L.TRPIP.RxMaxSp Maximum RX rate Multi-mode: None 2G/3G and LTE

eed of the control-plane GSM: None Co-transmission
Co-transmission
the eNodeB LTE:
TDLOFD-003002
MLOFD-003002

eRAN
Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Description 10 Reference Documents
10 Reference Documents
1. IP Transmission Feature Parameter Description

2. Transport Resource Management Feature Parameter Description
3. Common Transmission Feature Parameter Description


2G, 3G and LTE Co-Transmission (ERAN12.1 - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2G, 3G and LTE Co-Transmission (ERAN12.1 - 01)

Uploaded by

Copyright:

Available Formats

eRAN

2G, 3G and LTE Co-transmission

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2017-03-08) Huawei Proprietary and Confidential i

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

Issue 01 (2017-03-08) Huawei Proprietary and Confidential ii

6.5 Performance Monitoring...............................................................................................................................................25

Issue 01 (2017-03-08) Huawei Proprietary and Confidential iii

1 About This Document

This document covers the following features:

1.2 Intended Audience

1.3 Change History

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 1

eRAN12.1 Draft A (2016-12-30)

Feature Supported NB-IoT. For details, see the None Macro

Editorial None None N/A

1.4 Differences Between eNodeB Types

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 2

1.5 Functional Differences Between NB-IoT and FDD

MLOF 2G/3G LOFD- 2G/3G There are no functional differences between

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 3

Table 2-1 Typical scenarios

GBTS l The LMPT/UMPT/UMDU of an eNodeB provides FE/GE ports to

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 4

eGBTS l The LMPT/UMPT/UMDU of an eNodeB provides FE/GE ports to

NodeB l The LMPT/UMPT/UMDU of an eNodeB provides FE/GE ports to

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 5

Co-transmission enables eNodeBs to be deployed in areas where GBTSs, eGBTSs, and

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 6

Figure 3-1 Co-transmission networking

In 2G/3G and LTE co-transmission, an eNodeB, functioning as a convergence node, provides

3.2 Co-transmission with a Convergence Device

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 7

Figure 3-2 Co-transmission with a convergence device

3.3 Co-transmission Without a Convergence Device

Figure 3-3 Co-transmission without a convergence device

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 8

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 9

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 10

Mutually Exclusive Features

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 11

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 12

6.1 When to Use

6.2 Required Information

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 13

Feature ID Feature Name Model License Sales Unit

MLOFD-0030 2G/3G and ML1SCOTRA 2G/3G and Per eNodeB

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 14

If a lower-level base station is a GBTS/eGBTS:

6.4.4 Hardware Adjustment

6.4.5 Data Preparation and Feature Activation

6.4.5.1 Data Preparation

Subboard ETHPOR Network This parameter specifies the subboard type

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 15

Paramete Paramete Data Setting Notes

Port ETHPOR Network This parameter specifies whether an

Maximum ETHPOR Network This parameter specifies the maximum IP

Speed ETHPOR Network This parameter specifies the rate mode of

Duplex ETHPOR Network This parameter specifies the duplex mode

Subboard DEVIP.S Network This parameter specifies the subboard type

Issue 01 (2017-03-08) Huawei Proprietary and Confidential 16