2G, 3G and LTE Co-Transmission

2G, 3G and LTE Co-transmission
Contents
7.2.1 2G, 3G and LTE Co-transmission
eRAN
2G, 3G and LTE Co-transmission Feature
Parameter Description
Issue 01
Date 2016-03-07
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
7.2.1 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between eNodeB Types
2 Overview
2.1 Definition
2.2 Benefits
2.3 Architecture
3 Technical Description
3.1 Overview
3.2 Co-transmission with a Convergence Device
3.3 Co-transmission Without a Convergence Device
4 Related Features
5 Network Impact
6 Other Impacts
6.1 LOFD-003002 2G/3G and LTE Co-transmission
6.1.1 NEs
6.1.2 Hardware
6.1.3 Inter-NE Interfaces
6.1.4 Operation and Maintenance
7 Engineering Guidelines
7.1 When to Use LOFD-003002 2G/3G and LTE Co-transmission
7.2 Required Information
7.3 Planning
7.4 Deployment
7.4.1 Process
7.4.2 Requirements
7.4.3 Precautions
7.4.4 Hardware Adjustment
7.4.5 Data Preparation and Feature Activation
7.4.5.1 Data Preparation
7.4.5.2 Activation
7.4.6 Activation Observation
7.4.7 Reconfiguration
7.4.8 Deactivation
7.5 Performance Monitoring
7.6 Parameter Optimization
7.7 Troubleshooting
8 Parameters
9 Counters
10 Glossary
11 Reference Documents
1 About This Document
1.1 Scope
This document describes the LOFD-003002 2G/3G and LTE Co-transmission feature including its implementation principles, feature
dependencies, network impact, and engineering guidelines. The eNodeB serves as a convergence node for the co-transmission.
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeBs
LampSite DBS3900 LampSite
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to the software release delivered with this
document. Any future updates will be described in the product documentation delivered with future software releases.
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:
Need to understand the feature described herein

Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are two types of changes:
Feature change
Changes in features and parameters of a specified version as well as the affected entities
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.
eRAN11.1 01 (2016-03-07)
This issue does not include any changes.

eRAN11.1 Draft A (2015-12-30)
Compared with Issue 01 (2015-03-23) of eRAN8.1, this issue includes the following changes.
Change Type Change Description Parameter Change Affected Entity
Feature change None None -
Editorial change Revised the descriptions of CME-based feature configuration None -

in engineering guidelines.
Optimized the descriptions in this document. None -
1.4 Differences Between eNodeB Types

The feature described in this document is implemented in the same way on macro and LampSite eNodeBs.
2 Overview
2.1 Definition
With the 2G/3G and LTE Co-transmission feature, an eNodeB not only provides LTE services, but also functions as a hub to provide
routing and Dynamic Host Configuration Protocol (DHCP) Relay functions to 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, simplifying
transmission configuration and maintenance. This reduces capital expenditure (CAPEX) and operational expenditure (OPEX). This
reduces capital expenditure (CAPEX) and operational expenditure (OPEX).
2.3 Architecture
Table 2-1 describes a typical scenario for 2G/3G and LTE Co-transmission.
Table 2-1 Typical scenario for 2G/3G and LTE Co-transmission
Cascaded Base Networking

Transceiver Station
GBTS The LMPT/UMPT/UMDU of an eNodeB provides FE/GE ports to connect to the BSC,
MME, and S-GW, and provides FE ports to connect to the GTMU of a GBTS.
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.
eGBTS 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.
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 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.
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.
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:
The MME and S-GW generally do not support IP-over-E1/T1 ports.

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, see the cascading between an eNodeB and
GSM/UMTS base stations in this document.
3 Technical Description
3.1 Overview
This section describes LOFD-003002 2G/3G and LTE Co-transmission.
With this feature, you can deploy eNodeBs in areas with Huawei base stations of other radio access technologies (RATs) deployed,
including GBTSs, eGBTSs, and NodeBs. Using FE/GE ports and IP-over-E1/T1 ports, the eNodeBs can be cascaded with and share the
transmission resources of these base stations.
NOTE:
The difference between the LOFD-003002 2G/3G and LTE Co-transmission feature and the MRFD-231501 IP-Based Multi-mode Co-
Transmission on BS side(eNodeB) 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 the MRFD-
231501 IP-Based Multi-mode Co-Transmission on BS side (eNodeB) feature, see Common Transmission Feature Parameter Description
for SingleRAN.
Figure 3-1 illustrates the co-transmission networking supported by an eNodeB.

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:
Co-transmission with a convergence device

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.
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 NE must be deployed.
NOTE:
In this scenario, a router is typically used as the convergence device. The router details are not described in this document.
3.3 Co-transmission Without a Convergence Device

If a convergence device is not used, GBTSs/eGBTSs/NodeBs use IP-over-E1/T1 or IP-over-FE/GE 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.
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 in them. The eNodeB cannot identify the service types of transit
data flows. The eNodeB forwards the transit data flows based on different routing policies.
If a destination IP route is used, the eNodeB searches for the output port based on the destination IP address and then
transmits the transit data flows from the output port to the destination service node.
If a source IP route is used, the eNodeB searches for the output port based on the source IP address and 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 to 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,
and 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 uses dedicated transmission resource groups.
The eNodeB data flows consume resources in other groups. The WRR scheduling function helps to control the data flows between the
transmission resource groups to ensure scheduling fairness.
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 each queue can use for
transmission. This ensures fairness between transmission resource groups, while maintaining the differentiation.
NOTE:
If the eNodeB provides IP 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.
4 Related Features
Prerequisite Features
None
Mutually Exclusive Features
None
Impacted Features
None
5 Network Impact
System Capacity
When this feature is enabled, the eNodeB forwards the data flows of cascaded base stations. The uplink and downlink traffic of the
cascaded base stations occupies the transmission bandwidth and affects the forwarding performance of the eNodeB.
Network Performance
When this feature is enabled, services of the cascaded base stations will fail if the eNodeB is faulty, being upgraded, or experiences
transmission interruption.
6 Other Impacts
6.1 LOFD-003002 2G/3G and LTE Co-transmission
6.1.1 NEs
No impact.
6.1.2 Hardware
No impact.
6.1.3 Inter-NE Interfaces

No impact.
6.1.4 Operation and Maintenance

License
N/A
Configuration Management
N/A
Performance Management
N/A
Fault Management
N/A
7 Engineering Guidelines
This chapter describes the engineering guidelines for 2G/3G and LTE Co-transmission deployment, including when to use the feature,
deployment requirements, deployment process, and data preparation.
7.1 When to Use LOFD-003002 2G/3G and LTE Co-transmission

eNodeBs rarely use IP-over E1/T1 transmission, and IP-over Ethernet transmission is recommended for eNodeBs in 2G/3G and LTE 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 2G/3G and LTE co-transmission, see Table 2-1.
7.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 2G/3G and LTE 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.
7.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
7.4 Deployment
7.4.1 Process
You must configure common transmission parameters before enabling 2G/3G and LTE Co-transmission. For details, see IP Transmission
Feature Parameter Description.
7.4.2 Requirements
Operating Environment
None
Transmission Networking
None
License
This feature requires the purchase and activation of a license. The following table lists the license information.
Feature ID Feature Name Model License Control Item NE Sales Unit
LOFD-003002 2G/3G and LTE Co- LT1SCOTRAN00 2G/3G and LTE eNodeB per eNodeB
transmission Co-transmission
(FDD)
7.4.3 Precautions
If a lower-level base station is a NodeB,
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.
The next hop of the route from the NodeB to the RNC is the IP address of the eNodeB port connected to the NodeB.
If a lower-level base station is a GBTS/eGBTS,
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.
The destination IP address of the DHCP Relay route to the GBTS 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 BSC.
The destination IP address of the DHCP Relay route to the eGBTS 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.
7.4.4 Hardware Adjustment

N/A
7.4.5 Data Preparation and Feature Activation

7.4.5.1 Data Preparation
This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all
scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario.
There are three types of data sources:
Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer
transmission equipment
Network plan (negotiation not required): parameter values planned and set by the operator
User-defined: parameter values set by users
Prepare the following data before the feature deployment:
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.
Parameter Parameter ID Data Source Setting Notes

Name
Subboard ETHPORT.SBT Network plan This parameter specifies the type of the sub-board
Type (negotiation not on the board where the Ethernet port is located.
required) Set this parameter to BASE_BOARD(Base Board).
Port Attribute ETHPORT.PA Network plan This parameter specifies whether an Ethernet port is
(negotiation not an electrical port or optical port.
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 electrical/optical
attributes of peer port are modified, run the RST ETHPORT
command to reset the peer port or the local Ethernet port.
Maximum ETHPORT.MTU Network plan This parameter specifies the maximum IP packet
Transmission (negotiation size (including the IP header) at the Ethernet port.
Unit required) Set this parameter based on the transport network
plan.
Speed ETHPORT.SPEED Network plan This parameter specifies the speed mode of the
(negotiation Ethernet port. Set this parameter to the same value
required) as that of the peer port.
Duplex ETHPORT.DUPLEX Network plan This parameter specifies the duplex mode of the
(negotiation Ethernet port. Set this parameter to the same value
required) as that of the peer port.
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.
Parameter Name Parameter ID Data Source Setting Notes
Subboard Type DEVIP.SBT Network plan This parameter specifies the type of the sub-board on
(negotiation not the board where a port is located.
IP Address DEVIP.IP Network plan This parameter specifies the IP address configured for
(negotiation not a given port. The IP address must be in the same
required) network segment as those of the lower-level cascaded
base stations.
Mask DEVIP.MASK Network plan This parameter specifies the subnet mask of the
(negotiation not device IP address configured on a port.
required)
The device IP address must be in the same network
segment as the port IP addresses of the cascaded
base stations.
Port Type DEVIP.PT Network plan This parameter specifies the type of the physical port.
(negotiation not If the eNodeB uses the E1/T1 port to
required) connect to the transport network, set this
parameter to PPP(PPP Link) or MPGRP
(Multi-link PPP Group).
If the eNodeB uses the Ethernet port to
connect to the transport network, set this
parameter to ETH(Ethernet Port) or
ETHTRK(Ethernet Trunk).
In cascading scenarios, set this parameter
to the IP address of the physical port.
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.
Route Index IPRT.RTIDX Network plan This parameter specifies the route index of an IP
(negotiation not route.
required)
Destination IP IPRT.DSTIP Network plan You are advised not to set both of these
(negotiation not parameters to 0.0.0.0.
required) In cascading scenarios, a route to the RNC
or BSC must be set. The destination IP
Mask IPRT.DSTMASK Network plan
address is the service IP address of the
(negotiation not
RNC or BSC.
required)
In cascading scenarios, a route to the
logical IP address of the cascaded base
station must be set. The destination IP
address is the logical IP address of the
Subboard Type IPRT.SBT Network plan This parameter specifies
cascaded basethe type of sub-board on the
station.
(negotiation not board where the IP route is established.
Route Type IPRT.RTTYPE Network plan This parameter specifies the type of route.
(negotiation not If the eNodeB uses an Ethernet port to
required) connect to the transport network, set this
parameter to NEXTHOP(Next Hop).
If the eNodeB uses the E1 port to connect
to the transport network, set this parameter
to IF(Exit Interface).
Port Type IPRT.IFT Network plan This parameter specifies the type of a port.
(negotiation not If the eNodeB uses the E1 port to connect to the
required) transport network, set this parameter to PPP(PPP
Link) or MPGRP(Multi-link PPP Group).
Next Hop IP IPRT.NEXTHOP Network plan This parameter specifies the IP address of the next
(negotiation not hop.
required) This parameter is valid only when the
IPRT.RTTYPE parameter is set to
NEXTHOP(Next Hop).
Set this parameter to the IP address of the
gateway on the transport network to which
the eNodeB is connected.
Priority IPRT.PREF This parameter specifies the priority of the route.

Network plan If a backup IP route is required, this parameter is
(negotiation not required to specify the priorities of the active and
required) 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.
(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.

Name
DHCP Relay DHCPRELAYSWITCH.ES Transport planning This parameter specifies whether to turn on the
Switch (internal planning) DHCP Relay switch.
Set this parameter to ENABLE(Enable).
(Optional) The DHCPSVRIP MO, which specifies the IP address of the DHCP server for the cascaded base stations. The key
parameter in this MO is described in the following table.

Name
DHCP DHCPSVRIP.DHCPSVRIP Transport This parameter specifies the IP address of the

Server IP planning (internal DHCP server.
Address planning) If the cascaded base station is a
NodeB, set this parameter to the IP
address of the U2000 or RNC.
If the cascaded base station is a
GBTS, set this parameter to the IP
address of the BSC.
(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 with data flows of the cascaded base stations.
The key parameters in this MO are described in the following table.

Name
Transmission RSCGRP.RSCGRPID Network plan Set this parameter based on the network plan.
Resource (negotiation not You are advised to set different transmission
Group ID required) resource groups for data flows of the cascaded
base stations and the eNodeB.
Add transmission resource group ID only if you
need to measure the performance counters.
Subboard RSCGRP.SBT Network plan This parameter specifies the type of sub-board on
Type (negotiation not the board where the IP route is established.
required) Set this parameter to BASE_BOARD(Base
Board).
Bearing Port RSCGRP.PT Network plan This parameter specifies the type of a port where a
Type (negotiation not transmission resource group is carried.
required) Set this parameter according to the type of the
physical port connecting the MME and S-GW.
Tx Bandwidth RSCGRP.TXBW Network plan This parameter specifies the uplink transport
(negotiation not admission bandwidth for a transmission resource
required) group that carries eNodeB data flows and TX traffic
shaping bandwidth. This parameter is used in
Name
single-rate mode. Set this parameter based on the
network plan.
Rx Bandwidth RSCGRP.RXBW Network plan This parameter specifies the downlink transport
(negotiation not admission bandwidth for a transmission resource
required) group that carries 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 Committed RSCGRP.TXCBS Network plan This parameter specifies the TX committed burst
Burst Size (negotiation not size of a transmission resource group.
required) Set this parameter based on the network 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 Excessive RSCGRP.TXEBS Network plan This parameter specifies the TX excessive burst
Burst Size (negotiation not size of a transmission resource group.
required) Set this parameter based on the network plan. You
are advised to set this parameter to two times that
of the TX Bandwidth value.
Scheduling RSCGRP.WEIGHT Network plan This parameter specifies the scheduling weight of a
Weight (negotiation not transmission resource group. This parameter is
required) used in calculating the bandwidth scheduled to a
resource group, which helps achieve the user
admission control.
Set this parameter based on the network plan in
case of physical bandwidth restriction. You are
advised to retain the default value.
TX Committed RSCGRP.TXCIR Network plan This parameter specifies the transmit committed
Information (negotiation not information rate (CIR) of the transmission resource
Rate required) group, which is a guarantee rate assigned by the
operator.
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.RXCIR Network plan This parameter specifies the receive CIR of the
Committed (negotiation not transmission resource group, which is a guarantee
Information required) rate assigned by the operator. This parameter value
Rate is used as the downlink transport admission
bandwidth for services that do not need flow
control.
Set this parameter based on the network plan. This
parameter value is used as the downlink transport
group that carries eNodeB data flows.
TX Peak RSCGRP.TXPIR Network plan This parameter specifies the peak information rate
Information (negotiation not (PIR) of the transmission resource group.
Rate required) Set this parameter based on the network plan. This
parameter value is used as the uplink transport
group that carries eNodeB data flows and TX traffic
shaping bandwidth for eNodeB or transit data flows.
RSCGRP.RXPIR
Name
RX Peak Network plan This parameter specifies the receive PIR of the
Information (negotiation not transmission resource group. This parameter value
Rate required) is used as the downlink transport admission
bandwidth for a transmission resource group.
This parameter is used in double-rate mode. Set
this parameter based on the network plan.
TX Peak Burst RSCGRP.TXPBS Network plan This parameter specifies the size of the peak burst
Size (negotiation not transmitted from the transmission resource group.
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
RSCGRP.TXPBS must be greater than or equal to
that of RSCGRP.TXPIR.
(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.

Name
Mapping IP2RSCGRP.MAPIDX Network plan This parameter specifies the mapping between an
Index (negotiation not IP address and the transmission resource group.
required) This parameter is used to specify the mapping
transmission resource group for transit data flows.
Transmission IP2RSCGRP.BEAR Network plan This parameter specifies the bearer type of a
Resource (negotiation not transmission resource group. Set this parameter to
Group Bear required) IP(IP).
Type
Bearing Port IP2RSCGRP.PT Network plan This parameter specifies the type of a port where a
Type (negotiation not transmission resource group is carried. This
required) parameter is used to specify the type of eNodeB
port, which transit data flows are transmitted
through.
Bearing Port IP2RSCGRP.PN Network plan This parameter specifies the number of a port
No. (negotiation not where a transmission resource group is carried.
required) This parameter is used to specify the number of an
eNodeB port, which transit data flows are
transmitted through.
Transmission IP2RSCGRP.RSCGRPID Network plan This parameter specifies the ID of a transmission

Resource (negotiation not resource group. This parameter is used to specify
Group ID required) the ID of a transmission resource group for transit
data flows that are transmitted through the
eNodeB.
Destination IP2RSCGRP.DSTIP Network plan This parameter specifies the destination IP

IP (negotiation not address of the data flow that is bound to a
required) transmission resource group. This parameter is
used to specify a destination IP address for transit
data flows.
Mask IP2RSCGRP.DSTMASK Network plan This parameter specifies the subnet mask of the
(negotiation not destination IP address of the data flow that is
required) bound to a transmission resource group. This
parameter is used to specify a subnet mask of the
destination IP address for transit data flows.
7.4.5.2 Activation
Using the CME
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.
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:
1. Run the SET ETHPORT command to set the attribute of the Ethernet port cascaded to the eNodeB.
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.
3. Run the ADD IPRT command to add the routes from the eNodeB to the peer devices of the lower-level cascaded base
stations.
If the cascaded base station is a GBTS/eGBTS, the peer device is the BSC.
If the cascaded base station is a NodeB, the peer devices are the RNC and U2000.
4. (Optional) Run the SET DHCPRELAYSWITCH command to turn on the DHCP Relay switch.
5. (Optional) Run the ADD DHCPSVRIP command to set the IP address of the DHCP server for the cascaded base stations.
If the cascaded base station is a GBTS/eGBTS, the DHCP server is the BSC.
If the cascaded base station is a NodeB, the DHCP server is the RNC or U2000.
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.
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.
MML Command Examples
To set the attribute of the Ethernet port cascaded to the eNodeB, run the following command:
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;
To set the device IP address of the Ethernet port cascaded to the eNodeB, run the following command:
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=1, IP="10.2.2.2", MASK="255.255.255.0";
To add the route from the eNodeB to the peer device of the lower-level cascaded base station (GBTS in this example), run the following
command:
To use a destination IP route, run the following command:
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;
To use a source IP route, run the following command:
ADD SRCIPRT: SRCRTIDX=1,SN=7,SBT=BASE_BOARD,SRCIP="10.2.2.1",RTTYPE=NEXTHOP,NEXTHOP="10.1.1.2";
To turn on the DHCP Relay switch on the eNodeB, run the following command:
SET DHCPRELAYSWITCH: ES=ENABLE;
To set the IP address of the DHCP server for the GBTS, run the following command:
ADD DHCPSVRIP: DHCPSVRIP="100.3.3.3";
To add a transmission resource group for transit data flows, run the following command:
ADD RSCGRP:SN=7,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0,RU=KBPS;
To add the transit data flows to a specified transmission resource group, run the following command:
ADD IP2RSCGRP:MAPIDX=0,SN=7,SBT=BASE_BOARD,PT=ETH,DSTIP="100.3.3.3",DSTMASK="255.255.255.0";
7.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:
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.
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.
7.4.7 Reconfiguration
None
7.4.8 Deactivation
None
7.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.
7.6 Parameter Optimization

N/A
7.7 Troubleshooting
For details about IP transmission fault location and troubleshooting, see eRAN Troubleshooting Guide.
8 Parameters
Table 8-1 Parameters
MO Parameter ID MML Command Feature ID Feature Name Description
ETHPORT SBT ADD ETHPORT None None Meaning: Indicates the type of sub-
DSP ETHPORT board on the board where the
RMV ETHPORT Ethernet port is located.
RST ETHPORT GUI Value Range: BASE_BOARD
(Base Board), ETH_COVERBOARD
SET ETHPORT
(Ethernet Cover Board)
LST ETHPORT
Unit: None
Actual Value Range:
BASE_BOARD,
ETH_COVERBOARD
Default Value: None
ETHPORT PA ADD ETHPORT WRFD- IP Meaning: Indicates whether an

SET ETHPORT 050402 Transmission Ethernet port is an electrical port or
DSP DHCPRSLT GBFD- Introduction optical port. When the system
118601 on Iub starts, the system binds an Ethernet
DSP ETHPORT
Interface port to an electrical port
LST ETHPORT preferentially if the default value of
Abis over IP
the port attribute is AUTO. If the BS
does not support cascading, the
port attribute is set to AUTO. If this
parameter is incorrectly set,
services of a base station will be
interrupted after the base station is
reset.
GUI Value Range: COPPER
(Copper), FIBER(Fiber), AUTO
(Automatic Detection), UNCONFIG
(Not Configured)
Unit: None
Actual Value Range: COPPER,
FIBER, AUTO, UNCONFIG
Default Value: None
ETHPORT MTU ADD ETHPORT WRFD- IP Meaning: Indicates the maximum IP
SET ETHPORT 050402 Transmission packet size (including the IP
DSP ETHPORT GBFD- Introduction header) at the Ethernet port. For the
118601 on Iub UMPT, UMDU, LMPT, UCCU, and
LST ETHPORT
Interface UTRPc, the value of this parameter
Abis over IP ranges from 46 to 1800. For the
WMPT, GTMUb, GTMUc, UQEC,
and UEOC, the value of this
parameter ranges from 46 to 1500.
If this parameter is set to a value
greater than the maximum allowed
value, the maximum allowed value
takes effect. A value greater than or
equal to 776 is recommended,
because broadcast packets, such
as DHCP packets, may experience
reception or transmission failures if
the maximum transmission unit is
smaller than 776. If the Ethernet
port is added to an Ethernet trunk,
this parameter becomes invalid. The
actual maximum transmission unit
depends on the value set for the
Ethernet trunk.
GUI Value Range: 46~1800
Unit: byte
Actual Value Range: 46~1800
Default Value: 1500
ETHPORT SPEED ADD ETHPORT WRFD- IP Meaning: Indicates the speed mode
SET ETHPORT 050402 Transmission of the Ethernet port. This parameter
DSP DHCPRSLT GBFD- Introduction must be set to the same value as
118601 on Iub that of the peer port. GE electrical
LST ETHPORT
Interface ports of base board support 1000
Abis over IP Mbit/s only when working in auto-
negotiation mode. If SPEED of a GE
optical port is set to AUTO, the port
works at 1000 Mbit/s in auto-
negotiation mode. If SPEED of a GE
optical port is set to 1000M, the port
works at 1000 Mbit/s in manual
configuration mode.
GUI Value Range: 10M(10M), 100M
(100M), 1000M(1000M), AUTO
(Automatic Negotiation), 10G(10G),
40G(40G), UNCONFIG(Not
Configured)
Unit: None
Actual Value Range: 10M, 100M,
1000M, AUTO, 10G, 40G,
UNCONFIG
Default Value: AUTO(Automatic
Negotiation)
ETHPORT DUPLEX ADD ETHPORT WRFD- IP Meaning: Indicates the duplex mode
SET ETHPORT 050402 Transmission of the Ethernet port.
DSP DHCPRSLT GBFD- Introduction GUI Value Range: FULL(Full
118601 on Iub Duplex), AUTO(Automatic
LST ETHPORT
Interface Negotiation), UNCONFIG(Not
Abis over IP Configured)
Unit: None
Actual Value Range: FULL, AUTO,
UNCONFIG
Default Value: FULL(Full Duplex)
DEVIP SBT ADD DEVIP None None Meaning: Indicates the type of sub-
MOD DEVIP board on the board where a port is
RMV DEVIP located.
DSP DEVIP GUI Value Range: BASE_BOARD
(Base Board), E1_COVERBOARD
LST DEVIP
(E1 Cover Board), BACK_BOARD
(Back Board), ETH_COVERBOARD
Unit: None
Actual Value Range:
BASE_BOARD,
E1_COVERBOARD,
BACK_BOARD,
ETH_COVERBOARD
Default Value: None
DEVIP IP ADD DEVIP WRFD- IP Meaning: Indicates the IP address

MOD DEVIP 050402 Transmission configured for the port.
RMV DEVIP WRFD- Introduction GUI Value Range: Valid IP address
050411 on Iub Unit: None
DSP DEVIP
GBFD- Interface
DSP MULTICASTIP Actual Value Range: Valid IP
118601 Fractional IP address
LST DEVIP Function on
GBFD- Default Value: None
118611 Iub Interface
Abis over IP
Abis IP over
E1/T1
DEVIP MASK ADD DEVIP WRFD- IP Meaning: Indicates the subnet mask
DSP DEVIP 050402 Transmission of the device IP address configured
LST DEVIP WRFD- Introduction on the port.
050411 on Iub GUI Value Range: Valid Mask
GBFD- Interface address
118601 Fractional IP Unit: None
GBFD- Function on Actual Value Range: Valid Mask
118611 Iub Interface address
Abis over IP Default Value: None
Abis IP over
E1/T1
DEVIP PT ADD DEVIP None None Meaning: Indicates the type of the
MOD DEVIP physical port. The UMTS currently
RMV DEVIP does not support SUBIF.
DSP DEVIP GUI Value Range: PPP(PPP Link),
MPGRP(Multi-link PPP Group),
LST DEVIP
ETH(Ethernet Port), ETHTRK
(Ethernet Trunk), LOOPINT
(Loopback Interface), SUBIF(Sub-
interface), ETHCI(Ethernet CI Port)
Unit: None
Actual Value Range: PPP, MPGRP,
ETH, ETHTRK, LOOPINT, SUBIF,
ETHCI
Default Value: None
IPRT RTIDX ADD IPRT GBFD- Abis over IP Meaning: Indicates the index of an
MOD IPRT 118601 Abis IP over IP route.
RMV IPRT GBFD- E1/T1 GUI Value Range: 0~149
LST IPRT 118611 Unit: None
Default Value: None
IPRT DSTIP ADD IPRT WRFD- IP Meaning: Indicates the destination

050402 Transmission IP address of the route.
MOD IPRT WRFD- Introduction GUI Value Range: Valid IP address
DSP IPRT 050107 on Iub Unit: None
LST IPRT GBFD- Interface Actual Value Range: Valid IP
118601 IP routing address
GBFD- Based Hub Default Value: None
118611 Node B
LOFD- Abis over IP
003006 Abis IP over
E1/T1
IP Route
Backup
IPRT DSTMASK ADD IPRT WRFD- IP Meaning: Indicates the subnet mask
MOD IPRT 050402 Transmission for the destination IP address of the
DSP IPRT WRFD- Introduction route.
050107 on Iub GUI Value Range: Valid Mask
LST IPRT
GBFD- Interface address
118601 IP routing Unit: None
GBFD- Based Hub Actual Value Range: Valid Mask
118611 Node B address
LOFD- Abis over IP Default Value: None
003006 Abis IP over
E1/T1
IP Route
Backup
IPRT SBT ADD IPRT None None Meaning: Indicates the type of sub-
MOD IPRT board on the board where the IP
LST IPRT route is established.
GUI Value Range: BASE_BOARD
(Base Board),
UNCHANNELLED_COVERBOARD
(Unchannelled Cover Board),
E1_COVERBOARD(E1 Cover
Board), BACK_BOARD(Back
Board), ETH_COVERBOARD
Unit: None
Actual Value Range:
BASE_BOARD,
UNCHANNELLED_COVERBOARD,
E1_COVERBOARD,
BACK_BOARD,
ETH_COVERBOARD
Default Value: None
IPRT RTTYPE ADD IPRT WRFD- IP Meaning: Indicates the type of

MOD IPRT 050402 Transmission route. If this parameter is set to
DSP IPRT WRFD- Introduction NEXTHOP, all the IP packets that
050107 on Iub meet the route direction are first
LST IPRT
GBFD- Interface forwarded to the specified next hop
118601 IP routing IP address. If this parameter is set
Based Hub to IF, all the IP packets that meet
GBFD-
Node B the route direction are first
118611
Abis over IP forwarded to the specified egress
LOFD- port.
003006 Abis IP over
E1/T1 GUI Value Range: NEXTHOP(Next
Hop), IF(Exit Interface)
IP Route
Backup Unit: None
Actual Value Range: NEXTHOP, IF
Default Value: None
IPRT IFT ADD IPRT WRFD- IP Meaning: Indicates the type of port.
MOD IPRT 050402 Transmission
LST IPRT WRFD- Introduction GUI Value Range: PPP(PPP Link),
050107 on Iub MPGRP(Multi-link PPP Group),
GBFD- Interface TUNNEL(Tunnel), IPOA(IP Over
118601 IP routing ATM Interface), AIRLNK(Air Link)
GBFD- Based Hub Unit: None
118611 Node B Actual Value Range: PPP, MPGRP,
LOFD- Abis over IP TUNNEL, IPOA, AIRLNK
003006 Abis IP over Default Value: PPP(PPP Link)
E1/T1
IP Route
Backup
IPRT NEXTHOP ADD IPRT WRFD- IP Meaning: Indicates the IP address

MOD IPRT 050402 Transmission of the next hop.
DSP IPRT WRFD- Introduction GUI Value Range: Valid IP address
050107 on Iub Unit: None
LST IPRT
GBFD- Interface
Actual Value Range: Valid IP
118601 IP routing address
GBFD- Based Hub
Default Value: 0.0.0.0
118611 Node B
LOFD- Abis over IP
003006 Abis IP over
E1/T1
IP Route
Backup
IPRT PREF ADD IPRT WRFD- IP Meaning: Indicates the priority of the
MOD IPRT 050402 Transmission routing table entry. A smaller
DSP IPRT WRFD- Introduction parameter value indicates a higher
050107 on Iub priority.
LST IPRT
GBFD- Interface GUI Value Range: 1~255
118601 IP routing Unit: None
GBFD- Based Hub Actual Value Range: 1~255
118611 Node B
Default Value: 60
LOFD- Abis over IP
003006 Abis IP over
E1/T1
IP Route
Backup
DHCPRELAYSWITCH ES SET MRFD- IP-Based Meaning: Indicates whether to

DHCPRELAYSWITCH 221501 Multi-mode enable the DHCP relay switch.
LST WRFD- Co- GUI Value Range: DISABLE
DHCPRELAYSWITCH 031101 Transmission (Disable), ENABLE(Enable)
MRFD- on BS side Unit: None
231501 (NodeB)
Actual Value Range: DISABLE,
LBFD- NodeB Self- ENABLE
00300102 discovery
Default Value: DISABLE(Disable)
/ Based on IP
TDLBFD- Mode
00300102 IP-Based
LBFD- Multi-mode
00300103 Co-
/ Transmission
TDLBFD- on BS side
00300103 (eNodeB)
MRFD- Chain
211501 Topology
Tree
Topology
IP-Based
Multi-mode
Co-
Transmission
on BS side
(GBTS)
DHCPSVRIP DHCPSVRIP ADD DHCPSVRIP WRFD- NodeB Self- Meaning: Indicates the IP address
MOD DHCPSVRIP 031101 discovery of the DHCP server.
RMV DHCPSVRIP MRFD- Based on IP GUI Value Range: Valid IP address
211501 Mode Unit: None
LST DHCPSVRIP
LBFD- IP-Based Actual Value Range: Valid IP
00300102 Multi-mode address
/ Co-
Default Value: None
TDLBFD- Transmission
00300102 on BS side
LBFD- (GBTS)
00300103 Chain
/ Topology
TDLBFD- Tree
00300103 Topology
RSCGRP RSCGRPID ADD RSCGRP WRFD- Transmission Meaning: Indicates the ID of a

DSP RSCGRP 02130406 Recourse transmission resource group. When
MOD RSCGRP LOFD- Sharing on you use MML command to add a
003011 / Iub/Iur PPP link, an MP group, an Ethernet
RMV RSCGRP
TDLOFD- Interface port, an Ethernet trunk, a tunnel, or
LST RSCGRP a PPPoE link, the system
003011 Enhanced
GBFD- Transmission automatically creates a transmission
118605 QoS resource group with Transmission
Management Resource Group ID set to
IP QOS DEFAULTPORT(Default Port).
When you remove any of the
preceding objects, the system
automatically removes the
transmission resource group. When
you add a PPP link, an MP group,
an Ethernet port, an Ethernet trunk,
or an uplink tunnel on the CME, if
the default transmission resource
group does not exist, the system
automatically creates a transmission
resource group with Transmission
Resource Group ID set to
AUTOPORT(Autoport Port). When
you remove any 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
RSCGRP SBT ADD RSCGRP None None Meaning: Indicates the type of sub-
DSP RSCGRP board on the transmission group.
MOD RSCGRP The LTE currently does not support
UNCHANNELLED_COVERBOARD.
RMV RSCGRP
GUI Value Range: BASE_BOARD
LST RSCGRP
(Base Board),
UNCHANNELLED_COVERBOARD
(Unchannelled Cover Board),
E1_COVERBOARD(E1 Cover
Board), BACK_BOARD(Back
Board), ETH_COVERBOARD
Unit: None
Actual Value Range:
BASE_BOARD,
UNCHANNELLED_COVERBOARD,
E1_COVERBOARD,
BACK_BOARD,
ETH_COVERBOARD
Default Value: None
RSCGRP PT ADD RSCGRP None None Meaning: Indicates the type of port
DSP RSCGRP where a transmission resource
MOD RSCGRP group is carried. The LTE currently
does not support STM1, IMA, UNI,
RMV RSCGRP
or FRAATM.
LST RSCGRP
GUI Value Range: IMA(IMA Group),
UNI(UNI Link), STM1(STM1),
FRAATM(FRAATM Link), PPP(PPP
Link), MPGRP(Multi-link PPP
Group), ETH(Ethernet Port),
ETHTRK(Ethernet Trunk), TUNNEL
(Tunnel)
Unit: None
Actual Value Range: IMA, UNI,
STM1, FRAATM, PPP, MPGRP,
ETH, ETHTRK, TUNNEL
Default Value: None
RSCGRP TXBW ADD RSCGRP WRFD- Transmission Meaning: Indicates the maximum
MOD RSCGRP 02130406 Recourse uplink bandwidth of a transmission
DSP RSCGRP LOFD- Sharing on resource group at the MAC layer
003011 / Iub/Iur when the transmission resource
LST RSCGRP
TDLOFD- Interface group is carried over IP. This
003011 Enhanced parameter value is used as the
GBFD- Transmission uplink transport admission
118605 QoS bandwidth and TX traffic shaping
Management bandwidth. The minimum rate
IP QOS supported by the UMPTa, UMPTb,
UMPTe, UMDU, GTMUb or GTMUc
is 64 kbit/s. The LMPT can be
configured with a maximum of 360
Mbit/s TX bandwidth. The WMPT,
GTMUb or GTMUc can be
Mbit/s TX bandwidth. The UMPTa,
UMPTb, UMDU or UTRPc can be
Gbit/s TX bandwidth. The UMPTe or
UCCU can be configured with a
maximum of 10 Gbit/s TX
bandwidth. The value of TX
bandwidth is set to the maximum
value of TX bandwidth supported by
the board when it bigger than the
maximum one. For a WMPT and a
UTRP (excluding UTRPa), this
parameter does not specify the TX
traffic shaping bandwidth of the
transmission resource group that is
carried on the PPP link.
Unit: None
Default Value: None
RSCGRP RXBW ADD RSCGRP WRFD- Transmission Meaning: Indicates the RX

MOD RSCGRP 02130406 Recourse bandwidth of a transmission
DSP RSCGRP WRFD- Sharing on resource group. To LTE, this
01061010 Iub/Iur parameter value is also used as the
LST RSCGRP
LOFD- Interface downlink transport admission
003011 / HSDPA Flow bandwidth. The minimum rate
TDLOFD- Control supported by the UMPTa, UMPTb,
003011 Enhanced UMPTe, UMDU, GMTUb or GTMUc
Transmission is 64 kbit/s. The LMPT can be
GBFD-
QoS configured with a maximum of 540
118605
Management Mbit/s RX bandwidth. The WMPT,
GTMUb or GTMUc can be
IP QOS
Mbit/s RX bandwidth. The UMPTa,
Gbit/s RX bandwidth. The UMPTe
or UCCU can be configured with a
maximum of 10 Gbit/s RX
bandwidth.
Unit: None
Default Value: None
RSCGRP TXCBS ADD RSCGRP WRFD- Transmission Meaning: Indicates the TX

MOD RSCGRP 02130406 Recourse committed burst size of a
LST RSCGRP LOFD- Sharing on transmission resource group. The
003011 / Iub/Iur LMPT can be configured with a
TDLOFD- Interface maximum of 400 Mbit/s TX
003011 Enhanced committed burst size. The WMPT
GBFD- Transmission can be configured with a maximum
118605 QoS of 600 Mbit/s TX committed burst
Management size. The WMPT, GTMUb or
IP QOS GTMUc can be configured with a
maximum of 600 Mbit/s TX
committed burst size. The UMPTa,
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 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
RSCGRP TXEBS ADD RSCGRP WRFD- Transmission Meaning: Indicates the TX

MOD RSCGRP 02130406 Recourse excessive burst size of a
LST RSCGRP LOFD- Sharing on transmission resource group. The
TDLOFD- Interface maximum of 450 Mbit/s TX
003011 Enhanced excessive burst size. The WMPT,
GBFD- Transmission GTMUb or GTMUc can be
118605 QoS configured with a maximum of 600
Management Mbit/s TX excessive burst size. The
IP QOS UMPTa, UMPTb, UMDU or UTRPc
can be configured with a maximum
of 1 Gbit/s TX excessive burst size.
The UMTPe or UCCU can be
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
maximum one.
Unit: kbit
Default Value: 1000000
RSCGRP WEIGHT ADD RSCGRP WRFD- Transmission Meaning: Indicates the scheduling
MOD RSCGRP 02130406 Recourse weight of a transmission resource
LST RSCGRP LOFD- Sharing on group. This parameter is used in
003011 / Iub/Iur calculating the bandwidth scheduled
TDLOFD- Interface to a resource group, which helps
003011 Enhanced achieve the user admission control.
GBFD- Transmission GUI Value Range: 1~100
118605 QoS Unit: None
Management Actual Value Range: 1~100
IP QOS Default Value: 100
RSCGRP TXCIR ADD RSCGRP WRFD- Transmission Meaning: Indicates the transmit CIR
MOD RSCGRP 02130406 Recourse of the transmission resource group.
LST RSCGRP LOFD- Sharing on The LMPT can be configured with a
003011 / Iub/Iur maximum of 360 Mbit/s TX
TDLOFD- Interface committed information rate. The
003011 Enhanced UMPTa, UMPTb, UMDU or UTRPc
GBFD- Transmission can be configured with a maximum
118605 QoS of 1 Gbit/s TX committed
Management information rate. The GTMUb or
IP QOS GTMUc can be configured with a
maximum of 300 Mbit/s TX
committed information rate. The
UMPTe or UCCU can be configured
with a maximum of 10 Gbit/s TX
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
RSCGRP RXCIR ADD RSCGRP WRFD- Transmission Meaning: Indicates the receive CIR
LST RSCGRP LOFD- Sharing on This parameter value is used as the
003011 / Iub/Iur downlink transport admission
TDLOFD- Interface bandwidth for non-flow-control
003011 Enhanced services. The LMPT can be
GBFD- Transmission configured with a maximum of 540
118605 QoS Mbit/s RX committed information
Management rate. The UMPTa, UMPTb, UMDU
IP QOS or UTRPc can be configured with a
maximum of 1 Gbit/s RX committed
information rate. The UMPTe or
maximum of 10 Gbit/s RX
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
RSCGRP TXPIR ADD RSCGRP WRFD- Transmission Meaning: Indicates the transmit PIR
LST RSCGRP LOFD- Sharing on The LMPT can be configured with a
003011 / Iub/Iur maximum of 360 Mbit/s TX peak
TDLOFD- Interface information rate. The UMPTa,
003011 Enhanced UMPTb, UMDU or UTRPc can be
GBFD- Transmission configured with a maximum of 1
118605 QoS Gbit/s TX peak information rate. The
Management GTMUb or GTMUc can be
IP QOS configured with a maximum of 300
Mbit/s TX peak information rate.
The UMPTe or UCCU can be
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
maximum one.
Unit: None
Default Value: None
RSCGRP RXPIR ADD RSCGRP WRFD- Transmission Meaning: Indicates the receive PIR
LST RSCGRP LOFD- Sharing on This parameter value is used as the
003011 / Iub/Iur downlink transport admission
TDLOFD- Interface bandwidth. The LMPT can be
003011 Enhanced configured with a maximum of 540
GBFD- Transmission Mbit/s RX peak information rate.
118605 QoS The UMPTa, UMPTb, UMDU or
Management URTPc can be configured with a
IP QOS maximum of 1 Gbit/s RX peak
information rate. The UMPTe or
maximum of 10 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
RSCGRP TXPBS ADD RSCGRP

MOD RSCGRP WRFD- Transmission Meaning: Indicates the size of the
LST RSCGRP 02130406 Recourse peak burst transmitted from the
LOFD- Sharing on transmission resource group. The
TDLOFD- Interface maximum of 540 Mbit/s TX peak
003011 Enhanced burst size. The UMPTa, UMPTb,
GBFD- Transmission UMDU or UTRPc can be configured
118605 QoS with a maximum of 1 Gbit/s TX peak
Management burst size. The GTMUb or GTMUc
IP QOS can be configured with a maximum
of 300 Mbit/s TX peak burst size.
The UMPTe or UCCU can be
Gbit/s TX peak burst size. The value
of TX peak burst size is set to the
maximum value of TX peak burst
size supported by the board when it
bigger than the maximum one.
Unit: kbit
Default Value: None
IP2RSCGRP MAPIDX ADD IP2RSCGRP None None Meaning: Indicates the mapping
RMV IP2RSCGRP between IP and Transport Resource
LST IP2RSCGRP Groups.
Unit: None
Default Value: None
IP2RSCGRP BEAR ADD IP2RSCGRP MRFD- IP-Based Meaning: Indicates the bearer type
LST IP2RSCGRP 221501 Multi-mode of transmission resource group.
WRFD- Co- GUI Value Range: IP(IP)
02130406 Transmission Unit: None
MRFD- on BS side
Actual Value Range: IP
231501 (NodeB)
Default Value: IP(IP)
LOFD- Transmission
003002 / Recourse
TDLOFD- Sharing on
003002 Iub/Iur
Interface
MRFD-
211501 IP-Based
Multi-mode
Co-
Transmission
on BS side
(eNodeB)
2G/3G and
LTE Co-
transmission
IP-Based
Multi-mode
Co-
Transmission
on BS side
(GBTS)
IP2RSCGRP PT ADD IP2RSCGRP None None Meaning: Indicates the type of port
LST IP2RSCGRP where a transmission resource
group is carried.
GUI Value Range: PPP(PPP Link),
MPGRP(Multi-link PPP Group),
ETH(Ethernet Port), ETHTRK
(Ethernet Trunk), TUNNEL(Tunnel)
Unit: None
Actual Value Range: PPP, MPGRP,
ETH, ETHTRK, TUNNEL
Default Value: None
IP2RSCGRP PN ADD IP2RSCGRP None None Meaning: Indicates the number of

LST IP2RSCGRP the port where the transmission
resource group is configured.
Unit: None
Default Value: 0
IP2RSCGRP RSCGRPID ADD IP2RSCGRP MRFD- IP-Based Meaning: Indicates the ID of a

LST IP2RSCGRP 221501 Multi-mode transmission resource group.
WRFD- Co- GUI Value Range: 0~15
02130406 Transmission Unit: None
MRFD- on BS side
231501 (NodeB)
Default Value: 0
LOFD- Transmission
003002 / Recourse
TDLOFD- Sharing on
003002 Iub/Iur
Interface
MRFD-
211501 IP-Based
Multi-mode
Co-
Transmission
on BS side
(eNodeB)
2G/3G and
LTE Co-
transmission
IP-Based
Multi-mode
Co-
Transmission
on BS side
(GBTS)
IP2RSCGRP DSTIP ADD IP2RSCGRP MRFD- IP-Based Meaning: Indicates the destination
LST IP2RSCGRP 221501 Multi-mode IP address of the service flow that is
WRFD- Co- bound to a transmission resource
02130406 Transmission group.
MRFD- on BS side GUI Value Range: Valid IP address
231501 (NodeB) Unit: None
LOFD- Transmission Actual Value Range: Valid IP
003002 / Recourse address
TDLOFD- Sharing on
Default Value: None
003002 Iub/Iur
Interface
MRFD-
211501 IP-Based
Multi-mode
Co-
Transmission
on BS side
(eNodeB)
2G/3G and
LTE Co-
transmission
IP-Based
Multi-mode
Co-
Transmission
on BS side
(GBTS)
IP2RSCGRP DSTMASK ADD IP2RSCGRP MRFD- IP-Based Meaning: Indicates the subnet mask
LST IP2RSCGRP 221501 Multi-mode of the destination IP address of the
WRFD- Co- service traffic bound to a
02130406 Transmission transmission resource group.
MRFD- on BS side GUI Value Range: Valid Mask
231501 (NodeB) address
LOFD- Transmission Unit: None
003002 / Recourse Actual Value Range: Valid Mask
TDLOFD- Sharing on address
003002 Iub/Iur
Default Value: None
Interface
MRFD-
211501 IP-Based
Multi-mode
Co-
Transmission
on BS side
(eNodeB)
2G/3G and
LTE Co-
transmission
IP-Based
Multi-mode
Co-
Transmission
on BS side
(GBTS)
9 Counters
Table 9-1 Counters
Counter ID Counter Name Counter Description Feature ID Feature Name
1526733176 L.TRPIP.TxBytes Number of bytes of the Multi-mode: None 2G/3G and LTE Co-
control-plane and user- GSM: None transmission
plane data sent at the UMTS: None
IP layer over the
LTE: LOFD-003002
eNodeB transmission
interfaces
1526733177 L.TRPIP.RxBytes Number of bytes of the Multi-mode: None 2G/3G and LTE Co-
plane data received at UMTS: None
the IP layer over the
LTE: LOFD-003002
eNodeB transmission
interfaces
1526733178 L.TRPIP.TxPackets Number of the control- Multi-mode: None 2G/3G and LTE Co-
plane and user-plane GSM: None transmission
packets sent at the IP UMTS: None
layer over the eNodeB
LTE: LOFD-003002
transmission interfaces
1526733179 L.TRPIP.RxPackets Number of the control- Multi-mode: None 2G/3G and LTE Co-
plane and user-plane transmission
Counter ID Counter Name Counter Description Feature ID Feature Name
packets received at the GSM: None
IP layer over the UMTS: None
eNodeB transmission LTE: LOFD-003002
interfaces
1526733180 L.TRPIP.TxMeanSpeed Average TX rate of the Multi-mode: None 2G/3G and LTE Co-
plane data at the IP UMTS: None
LTE: LOFD-003002
1526733181 L.TRPIP.TxMaxSpeed Maximum TX rate of Multi-mode: None 2G/3G and LTE Co-
the control-plane and GSM: None transmission
user-plane data at the UMTS: None
IP layer over the
LTE: LOFD-003002
eNodeB transmission
interfaces
1526733182 L.TRPIP.RxMeanSpeed Average RX rate of the Multi-mode: None 2G/3G and LTE Co-
plane data at the IP UMTS: None
LTE: LOFD-003002
1526733183 L.TRPIP.RxMaxSpeed Maximum RX rate of Multi-mode: None 2G/3G and LTE Co-
the control-plane and GSM: None transmission
user-plane data at the UMTS: None
IP layer over the
LTE: LOFD-003002
eNodeB transmission
interfaces
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
11 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

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

Uploaded by

Copyright:

Available Formats

2G, 3G and LTE Co-transmission

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.

Huawei Technologies Co., Ltd.

1 About This Document

eNodeB Type Model

Macro 3900 series eNodeBs

LampSite DBS3900 LampSite

1.2 Intended Audience

Need to understand the feature described herein

1.3 Change History

This issue does not include any changes.

Change Type Change Description Parameter Change Affected Entity

Feature change None None -

Editorial change Revised the descriptions of CME-based feature configuration None -

Optimized the descriptions in this document. None -

1.4 Differences Between eNodeB Types

Table 2-1 Typical scenario for 2G/3G and LTE Co-transmission

Cascaded Base Networking

The MME and S-GW generally do not support IP-over-E1/T1 ports.

Figure 3-1 illustrates the co-transmission networking supported by an eNodeB.

Co-transmission with a convergence device

3.2 Co-transmission with a Convergence Device

3.3 Co-transmission Without a Convergence Device

Mutually Exclusive Features

6.1 LOFD-003002 2G/3G and LTE Co-transmission

6.1.3 Inter-NE Interfaces

6.1.4 Operation and Maintenance

7.1 When to Use LOFD-003002 2G/3G and LTE Co-transmission

Feature ID Feature Name Model License Control Item NE Sales Unit

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

7.4.4 Hardware Adjustment

7.4.5 Data Preparation and Feature Activation

Prepare the following data before the feature deployment:

Parameter Parameter ID Data Source Setting Notes

Parameter Name Parameter ID Data Source Setting Notes

Parameter Name Parameter ID Data Source Setting Notes

Priority IPRT.PREF This parameter specifies the priority of the route.

Parameter Parameter ID Data Source Setting Notes

Parameter Parameter ID Data Source Setting Notes

DHCP DHCPSVRIP.DHCPSVRIP Transport This parameter specifies the IP address of the

Parameter Parameter ID Data Source Setting Notes

Parameter Parameter ID Data Source Setting Notes

Transmission IP2RSCGRP.RSCGRPID Network plan This parameter specifies the ID of a transmission

Destination IP2RSCGRP.DSTIP Network plan This parameter specifies the destination IP

Fast Batch Activation

Using MML Commands

Perform the following steps on the eNodeB:

MML Command Examples

7.4.6 Activation Observation

7.5 Performance Monitoring

7.6 Parameter Optimization

Table 8-1 Parameters

MO Parameter ID MML Command Feature ID Feature Name Description

ETHPORT PA ADD ETHPORT WRFD- IP Meaning: Indicates whether an

DEVIP IP ADD DEVIP WRFD- IP Meaning: Indicates the IP address

IPRT DSTIP ADD IPRT WRFD- IP Meaning: Indicates the destination

IPRT RTTYPE ADD IPRT WRFD- IP Meaning: Indicates the type of

IPRT NEXTHOP ADD IPRT WRFD- IP Meaning: Indicates the IP address

DHCPRELAYSWITCH ES SET MRFD- IP-Based Meaning: Indicates whether to

RSCGRP RSCGRPID ADD RSCGRP WRFD- Transmission Meaning: Indicates the ID of a

RSCGRP RXBW ADD RSCGRP WRFD- Transmission Meaning: Indicates the RX

RSCGRP TXCBS ADD RSCGRP WRFD- Transmission Meaning: Indicates the TX