2G 3G and LTE Co-Transmission (eRAN7.0 - 01) PDF

eRAN
2G/3G and LTE Co-transmission

Feature Parameter Description
Issue
01
Date
2014-04-26
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2014-04-26)
Huawei Proprietary and Confidential

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
2 Overview.........................................................................................................................................3
2.1 Definition........................................................................................................................................................................3
2.2 Benefits...........................................................................................................................................................................3
2.3 Architecture....................................................................................................................................................................3
3 Feature Component.......................................................................................................................5
3.1 Overview........................................................................................................................................................................5
3.2 Co-transmission with a Convergence Device.................................................................................................................6
3.3 Co-transmission Without a Convergence Device...........................................................................................................7
4 Related Features...........................................................................................................................10
4.1 Features Related to LOFD-003002 2G/3G and LTE Co-transmission........................................................................10
5 Network Impact...........................................................................................................................11
5.1 LOFD-003002 2G/3G and LTE Co-transmission........................................................................................................11
6 Other Impacts...............................................................................................................................12
6.1 LOFD-003002 2G/3G and LTE Co-transmission........................................................................................................12
6.1.1 NEs............................................................................................................................................................................12
6.1.2 Hardware...................................................................................................................................................................12
6.1.3 Inter-NE Interfaces....................................................................................................................................................12
6.1.4 Operation and Maintenance.......................................................................................................................................12
7 Engineering Guidelines.............................................................................................................13
7.1 When to Use LOFD-003002 2G/3G and LTE Co-transmission..................................................................................14
7.2 Required Information...................................................................................................................................................14
7.3 Planning........................................................................................................................................................................14
7.4 Deployment..................................................................................................................................................................14
7.4.1 Process.......................................................................................................................................................................14
7.4.2 Requirements.............................................................................................................................................................14
Issue 01 (2014-04-26)

ii
eRAN
Description
Contents
7.4.3 Data Preparation........................................................................................................................................................15

7.4.4 Precautions.................................................................................................................................................................23
7.4.5 Hardware Adjustment................................................................................................................................................24
7.4.6 Initial Configuration..................................................................................................................................................24
7.4.7 Activation Observation..............................................................................................................................................28
7.4.8 Reconfiguration.........................................................................................................................................................28
7.4.9 Deactivation...............................................................................................................................................................28
7.5 Performance Monitoring...............................................................................................................................................28
7.6 Parameter Optimization................................................................................................................................................28
7.7 Troubleshooting............................................................................................................................................................28
8 Parameters.....................................................................................................................................29
9 Counters........................................................................................................................................30
10 Glossary.......................................................................................................................................31
11 Reference Documents...............................................................................................................32
Issue 01 (2014-04-26)

iii
eRAN
Description
1 About This Document
About This Document
1.1 Scope
This document describes the LOFD-003002 2G/3G and LTE Co-transmission feature including
implementation principles, feature dependencies, network impact, and engineering guidelines.
The eNodeB servers as a convergence node for the co-transmission.
This document applies to the following types of eNodeBs.
eNodeB Type
Model
Macro
3900 series eNodeB
LampSite
DBS3900
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, and
"eNodeB" refers to LTE FDD eNodeB.
1.2 Intended Audience

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

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
Issue 01 (2014-04-26)

eRAN
Description
1 About This Document
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.
eRAN7.0 01 (2014-04-26)
This is the first official release.This issue does not include any changes.
eRAN7.0 Draft A (2014-01-20)

This document is created for eRAN7.0.
1.4 Differences Between eNodeB Types

The features described in this document are implemented in the same way on macro and
LampSite eNodeBs.
Issue 01 (2014-04-26)

eRAN
Description
2 Overview
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
The 2G/3G and LTE Co-transmission feature allows sharing physical ports and transmission
bandwidth between radio access networks and simplifies configuration and maintenance
operations for transmission. This reduces capital expenditure (CAPEX) and operational
expenditure (OPEX).
2.3 Architecture
Table 2-1 describes a typical scenario for the 2G/3G and LTE Co-transmission feature.
Table 2-1 Typical scenario for the 2G/3G and LTE Co-transmission feature
Cascaded
Base
Transceiver
Station
Networking
GBTS
l The LMPT/UMPT 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.
l The UMPT 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.
Issue 01 (2014-04-26)

eRAN
Description
2 Overview
Cascaded
Base
Transceiver
Station
Networking
eGBTS

the BSC, MME, and S-GW and provides FE/GE ports to connect to the
UMPT of an eGBTS.
l The UMPT 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 of an eGBTS.
NodeB

the RNC, MME, and S-GW and provides FE ports to connect to the
WMPT of a NodeB.
the RNC, MME, S-GW, and the UMPT of a NodeB.
l The UMPT of an eNodeB provides FE/GE ports to connect to the RNC,
MME, and S-GW and IP-over-E1/T1 ports to connect to the UMPT/
WMPT 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 itself 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.
Issue 01 (2014-04-26)

eRAN
Description
3 Feature Component
Feature Component
3.1 Overview
This section describes the LOFD-003002 2G/3G and LTE Co-transmission feature.
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 implement the former, whereas a multi-mode base station using
panel-based or backplane-based interconnection implement 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.
With this feature, you can deploy eNodeBs in areas where Huawei base stations of other radio
access technologies (RATs), including GBTSs, eGBTSs, and NodeBs, have been deployed.
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.
Figure 3-1 shows the co-transmission networking supported by an eNodeB.
Issue 01 (2014-04-26)

eRAN
Description
3 Feature Component
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 transit data flows, based on shared transmission resources, to forward the data flows.
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
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 GSM/UMTS
base station 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.
Issue 01 (2014-04-26)

eRAN
Description
3 Feature Component
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 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 a convergence device is not used, GSM/UMTS base stations use IP-over-E1/T1 or IP-overFE/GE ports to connect to an eNodeB. Data flows (for services, signaling, and O&M) from the
GSM/UMTS base stations 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.
Issue 01 (2014-04-26)

eRAN
Description
3 Feature Component
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 connects to the bearer
network for IP transmission.
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 cotransmission in IP networking mode.
The eNodeB considers data flows of cascaded base stations as transit data flows and performs
differentiated service scheduling based on the value of the Differentiated Services Code Point
(DSCP). The eNodeB cannot identify the service types of transit data flows. The eNodeB
functions as a router to forward the transit data flows based on their destination IP addresses.
DHCP Relay
Generally, a base station uses DHCP to obtain the IP address of packets, requiring that the DHCP
client (the base station) and DHCP server to be in the same broadcast domain.
In co-transmission mode, however, the cascaded GSM/UMTS base stations are not in the same
broadcast domain as the DHCP server. This requires that the eNodeB perform 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 GSM/UMTS base stations into unicast
Issue 01 (2014-04-26)

eRAN
Description
3 Feature Component
messages and then sends them to the DHCP server. After receiving a response from the DHCP
server, the eNodeB forwards the response to the GSM/UMTS base stations through the original
port.
The eNodeB configures the DHCP Relay function based on the parameters specified in the
configuration file. If it must configure the DHCP function, 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 for the transit data flows. 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 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 the fairness between transmission resource groups, while
maintaining the differentiation.
Issue 01 (2014-04-26)

eRAN
Description
4 Related Features
Related Features
4.1 Features Related to LOFD-003002 2G/3G and LTE Cotransmission

This section describes the dependency of the LOFD-0030002 2G/3G and LTE Co-transmission
feature on other features.
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None
Issue 01 (2014-04-26)

10
eRAN
Description
5 Network Impact
Network Impact
5.1 LOFD-003002 2G/3G and LTE Co-transmission

This section describes the network impact of the LOFD-003002 2G/3G and LTE Cotransmission feature.
System Capacity
After you enable this feature, 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
After you enable this feature, services of the cascaded base stations will fail if the eNodeB is
faulty, being upgraded, or experiences transmission interruption.
Issue 01 (2014-04-26)

11
eRAN
Description
6 Other Impacts
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
Issue 01 (2014-04-26)

12
eRAN
Description
7 Engineering Guidelines
Engineering Guidelines
This chapter describes the engineering guidelines for 2G/3G and LTE Co-transmission
deployment, including when to use the feature, requirements, deployment process, data
preparation, and initial configuration.
Issue 01 (2014-04-26)

13
eRAN
Description
7.1 When to Use LOFD-003002 2G/3G and LTE Cotransmission

Co-transmission mainly involves the DHCP Relay function, routing and address planning for
IP addresses of cascaded nodes, and transmission bandwidth planning for the eNodeB. IP-overFE/GE transmission is recommended for 2G/3G and LTE co-transmission because, due to the
low bandwidth provided by the E1/T1 links, the eNodeB rarely uses IP-over E1/T1 transmission.
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

Users can deploy the 2G/3G and LTE Co-transmission feature when the 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 the common transmission parameters before enabling the 2G/3G and LTE
Co-transmission feature. For details about how to configure these parameters, see IP
Transmission Feature Parameter Description.
7.4.2 Requirements
Operating Environment
None
Issue 01 (2014-04-26)

14
eRAN
Description
Transmission Networking
None
License
This feature requires the purchase and activation of a license. Table 7-1 lists the license
information.
Table 7-1 License information for 2G/3G and LTE Co-transmission
Feature ID
Feature Name
License
Control Item
NE
Sales Unit
LOFD-003002
2G/3G and LTE

Cotransmission
2G/3G and LTE

Cotransmission
(FDD)
eNodeB
per eNodeB
7.4.3 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:
l
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 deployment:

l
The ETHPORT MO, which specifies the attribute of the Ethernet port for cascading on
the eNodeB. The key parameters in this MO are described in the following table.
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
Subboard
Type
ETHPOR
T.SBT
Network plan
This parameter specifies the type of the
(negotiation not sub-board on the board where the
required)
Ethernet port is located.
Set this parameter to BASE_BOARD
(Base Board).
Issue 01 (2014-04-26)

15
eRAN
Description
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
Port
Attribute
ETHPOR
T.PA
Network plan
This parameter specifies whether an
(negotiation not Ethernet port is an electrical port or
required)
optical port.
The port attribute 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 attribute of the physical port.
NOTE
When the parameter is set to AUTO
(Automatic Detection), it takes about 1
minute to activate the port. If the electrical/
optical attribute of peer port is modified, run
the RST ETHPORT command to reset the
peer port or the local Ethernet port.
Maximum
Transmissi
on Unit
ETHPOR
T.MTU
Network plan
(negotiation
required)
This parameter specifies the maximum IP

packet size (including the IP header) at the
Ethernet port.
Set this parameter according to the
transport network plan.
Speed
ETHPOR
T.SPEED
Network plan
(negotiation
required)
This parameter specifies the speed mode

of the Ethernet port. This parameter must
be set to the same value as that of the peer
port.
Duplex
ETHPOR
T.
DUPLEX
Network plan
(negotiation
required)
This parameter specifies the duplex mode

of the Ethernet port. This parameter must
be set to the same value 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.
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
Subboard
Type
DEVIP.
SBT
Network plan
(negotiation not
required)

sub-board on the board where a port is
located.
(Base Board).
Issue 01 (2014-04-26)

16
eRAN
Description
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
IP Address
DEVIP.IP
Network plan
(negotiation not
required)
This parameter specifies the IP address

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

of the device IP address configured on a
port.
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
(negotiation not
required)

physical port.
l If the eNodeB uses the E1/T1 port to
connect to the transport network, set
this parameter to PPP(PPP Link) or
MPGRP(Multi-link PPP Group).
l If the eNodeB uses the Ethernet port
to connect to the transport network, set
this parameter to ETH(Ethernet
Port) or ETHTRK(Ethernet
Trunk).
l In cascading scenarios, set this
parameter to the IP address of the
physical port.
Issue 01 (2014-04-26)
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 M2000 must be set, respectively. The key
parameters in this MO are described in the following table.
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
Route
Index
IPRT.
RTIDX
Network plan
(negotiation not
required)
This parameter specifies the route index

of an IP route.
Destinatio
n IP
IPRT.
DSTIP
Network plan
(negotiation not
required)
l You are advised not to set both of

these parameters to 0.0.0.0.
l In cascading scenarios, a route to the
RNC or BSC must be set. The
destination IP address is the service IP
address of the RNC or BSC.

17
eRAN
Description
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
Mask
IPRT.
DSTMAS
K
Network plan
(negotiation not
required)
l 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
cascaded base station.
Subboard
Type
IPRT.SBT
Network plan
(negotiation not
required)
This parameter specifies the type of subboard on the board where the IP route is
established.
(Base Board).
Route
Type
IPRT.
RTTYPE
Network plan
(negotiation not
required)
This parameter specifies the type of route.

l If the eNodeB uses the Ethernet port
to connect to the transport network, set
this parameter to NEXTHOP(Next
Hop).
l If the eNodeB uses the E1 port to
connect to the transport network, set
this parameter to IF(Exit Interface).
Port Type
Next Hop
IP
IPRT.IFT
IPRT.
NEXTHO
P
Network plan
(negotiation not
required)
This parameter specifies the type of a

port.
Network plan
(negotiation not
required)
This parameter specifies the IP address of

the next hop.
If the eNodeB uses the E1 port to connect

to the transport network, set this
parameter to PPP(PPP Link) or
MPGRP(Multi-link PPP Group).
l This parameter is valid only when the

IPRT.RTTYPE parameter is set to
NEXTHOP(Next Hop).
l Set this parameter to the IP address of
the gateway on the transport network
to which the eNodeB is connected.
Issue 01 (2014-04-26)

18
eRAN
Description
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
Priority
IPRT.
PREF
Network plan
(negotiation not
required)
This parameter specifies the priority of

the route.
If a backup IP route is required, this
parameter is required to specify the
priorities of the active and backup routes.
The route with a 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, 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.
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
DHCP
Relay
Switch
DHCPRE
LAYSWI
TCH.ES
Transport
planning
(internal
planning)
This parameter specifies whether to turn

on the 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.
Parameter
Name
Paramete
r ID
Data Source
Setting Notes
DHCP
Server IP
Address
DHCPSV
RIP.
DHCPSV
RIP
Transport
planning
(internal
planning)
This parameter specifies the IP address of

the DHCP server.
l If the cascaded base station is a
NodeB, set this parameter to the IP
address of the M2000 or RNC.
l If the cascaded base station is a GBTS,
set this parameter to the IP address of
the BSC.
Issue 01 (2014-04-26)
(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.
19
eRAN
Description
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
Transmissi
on
Resource
Group ID
RSCGRP.
RSCGRPI
D
Network plan
(negotiation not
required)
Set this parameter based on the network

plan.
You are advised to set different
transmission 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
Type
RSCGRP.
SBT
Network plan
(negotiation not
required)
This parameter specifies the type of subboard on the board where the IP route is
established.
(Base Board).
Bearing
Port Type
RSCGRP.
PT
Network plan
(negotiation not
required)
This parameter specifies the type of a port

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

transport admission bandwidth for a
transmission resource group that carries
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
Bandwidth
RSCGRP.
RXBW
Network plan
(negotiation not
required)
This parameter specifies the downlink

transmission resource 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
Burst Size
RSCGRP.
TXCBS
Network plan
(negotiation not
required)
This parameter specifies the TX

committed burst size of a transmission
resource group.
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.
Issue 01 (2014-04-26)

20
eRAN
Description
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
TX
Excessive
Burst Size
RSCGRP.
TXEBS
Network plan
(negotiation not
required)
This parameter specifies the TX

excessive burst size of a transmission
resource group.
plan. You are advised to set this
parameter to two times that of the TX
Bandwidth value.
Scheduling
Weight
RSCGRP.
WEIGHT
Network plan
(negotiation not
required)
This parameter specifies the scheduling

weight of a transmission resource group.
This parameter is used in calculating the
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
Committed
Informatio
n Rate
RSCGRP.
TXCIR
Network plan
(negotiation not
required)
This parameter specifies the transmit

committed information rate (CIR) of the
transmission resource group, which is a
guarantee rate assigned by the operator.
plan. This parameter is used in doublerate 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
Committed
Informatio
n Rate
RSCGRP.
RXCIR
Network plan
(negotiation not
required)
This parameter specifies the receive CIR

of the transmission resource group, which
is a guarantee rate assigned by the
operator. This parameter value is used as
the downlink transport admission
bandwidth for services that do not need
flow control.
the downlink transport admission
bandwidth for a transmission resource
group that carries eNodeB data flows.
Issue 01 (2014-04-26)

21
eRAN
Description
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
TX Peak
Informatio
n Rate
RSCGRP.
TXPIR
Network plan
(negotiation not
required)
This parameter specifies the peak

information rate (PIR) of the
transmission resource group.
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 Peak
Informatio
n Rate
RSCGRP.
RXPIR
Network plan
(negotiation not
required)
This parameter specifies the receive PIR

of the transmission resource group. This
parameter value is used as the downlink
This parameter is used in double-rate
mode. Set this parameter based on the
network plan.
TX Peak
Burst Size
RSCGRP.
TXPBS
Network plan
(negotiation not
required)
This parameter specifies the size of the

peak burst transmitted from the
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.
Issue 01 (2014-04-26)
(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.
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
Mapping
Index
IP2RSCG
RP.
MAPIDX
Network plan
(negotiation
not required)
This parameter specifies the mapping

between an IP address and the
transmission resource group. This
parameter is used to specify the mapping
transmission resource group for transit
data flows.

22
eRAN
Description
Paramete
r Name
Paramete
r ID
Data Source
Setting Notes
Transmissi
on
Resource
Group Bear
Type
IP2RSCG
RP.BEAR
Network plan
(negotiation
not required)
This parameter specifies the bearer type

of a transmission resource group. Set this
parameter to IP(IP).
Bearing
Port Type
IP2RSCG
RP.PT
Network plan
(negotiation
not required)
This parameter specifies the type of a port

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

port where a transmission resource group
is carried. This parameter is used to
specify the number of an eNodeB port,
through which transit data flows are
transmitted.
Transmissi
on
Resource
Group ID
IP2RSCG
RP.
RSCGRPI
D
Network plan
(negotiation
not required)
This parameter specifies the ID of a

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

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

of the destination IP address of the data
flow that is 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.4 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 M2000.
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,

Issue 01 (2014-04-26)

23
eRAN
Description
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
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
be set. You can set the destination IP address on the M2000.
7.4.5 Hardware Adjustment

N/A
7.4.6 Initial Configuration

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 7-2 in a summary data file, which also contains
other data for the new eNodeBs to be deployed. Then, import the summary data file into the
CME for batch configuration. For detailed instructions, see section "Creating eNodeBs in
Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l
The MOs in Table 7-2 are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
Some MOs in Table 7-2 are not contained in a scenario-specific summary data file. In this
situation, customize a summary data file to include the MOs before you can set the
parameters.
The template Basic Scenario: using for the scenario of vlan and without security, etc is
used in non-security scenarios.
The template Security Scenario: using for the Scenario of ACL, Pre-Shared key or RSA
Digital Certificate Signature, etc is used in security scenarios.
Table 7-2 Parameters related to 2G/3G and LTE Co-transmission
Issue 01 (2014-04-26)
MO
Sheet in the
Summary
Data File
MO Name
Parameter Group
Remarks
ETHPOR
T
Base Station
Transport
Data
Ethport
Attribute
PortNo1, PortAttr1

24
eRAN
Description
MO
Sheet in the
Summary
Data File
MO Name
Parameter Group
Remarks
DEVIP
DevIPPattern
DevIPPatter
n
CabinetNo,
SubrackNo, SlotNo,
SubboardType,
PortType, PortNo, IP,
Mask, Description
This sheet
references the IP
address information
about S1 interface,
X2 interface, OM, or
clock channels in the
Base Station
Transport Data
sheet.
IPRT
IPRoutePatter
n
IPRoute
CabinetNo,
SubrackNo, SlotNo,
SubboardType,
PortType, PortNo,
RouteType, DstIP,
Mask, NextHopIP,
RoutePriority,
*Description Info
This sheet
references the
Destination IP1,
Destination
Mask1, and Next
Hop IP Address1 of
the eNodeB
parameter group in
the Base Station
Transport Data
sheet.
DHCPRE
LAYSWI
TCH
Common Data
DHCPREL
AYSWITC
H
DHCP Relay Switch
DHCPSV
RIP
Common Data
DHCPSVRI
P
DHCP Server IP
Address
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure is as follows:
Step 1 After creating a planned data area, choose CME > Advanced > Customize Summary Data File
(U2000 client mode), or choose Advanced > Customize Summary Data File (CME client mode),
to customize a summary data file for batch reconfiguration.
NOTE
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into
the customized summary data file.
Issue 01 (2014-04-26)

25
eRAN
Description
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-2 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME,
and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts
(U2000 client mode), or choose Area Management > Planned Area > Export Incremental
Scripts (CME client mode), to export and activate the incremental scripts.
----End
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.
Figure 7-1 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All the parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Issue 01 (2014-04-26)

26
eRAN
Description
Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export
and activate the incremental scripts.
----End
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 set the device IP address of the Ethernet port cascaded to
the eNodeB. The IP addresses of the interconnected ports must be in the same network segment.
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 M2000.
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 M2000.
----End
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:
ADD IPRT: 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 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";
Issue 01 (2014-04-26)

27
eRAN
Description
7.4.7 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 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
7.4.8 Reconfiguration
None
7.4.9 Deactivation
None
7.5 Performance Monitoring

None
7.6 Parameter Optimization

N/A
7.7 Troubleshooting
For details about IP transmission fault location and troubleshooting, see eRAN Troubleshooting
Guide.
Issue 01 (2014-04-26)

28
eRAN
Description
8 Parameters
Issue 01 (2014-04-26)

Parameters
29
eRAN
Description
9 Counters
Issue 01 (2014-04-26)

Counters
30
eRAN
Description
10 Glossary
10
Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue 01 (2014-04-26)

31
eRAN
Description
11
11 Reference Documents
Reference Documents
1.
IP Transmission Feature Parameter Description
2.
Transport Resource Management Feature Parameter Description
3.
Common Transmission Feature Parameter Description
Issue 01 (2014-04-26)

32

2G 3G and LTE Co-Transmission (eRAN7.0 - 01) PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

2G 3G and LTE Co-Transmission (eRAN7.0 - 01) PDF

Hochgeladen von

Copyright:

Verfügbare Formate

eRAN

2G/3G and LTE Co-transmission

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

7.4.3 Data Preparation........................................................................................................................................................15

Huawei Proprietary and Confidential

1 About This Document

About This Document

3900 series eNodeB

1.2 Intended Audience

Need to understand the features described herein

Work with Huawei products

1.3 Change History

Huawei Proprietary and Confidential

1 About This Document

eRAN7.0 Draft A (2014-01-20)

1.4 Differences Between eNodeB Types

Huawei Proprietary and Confidential

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

Huawei Proprietary and Confidential

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

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

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Figure 3-1 Co-transmission networking

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

Co-transmission with a convergence device

Co-transmission without a convergence device

3.2 Co-transmission with a Convergence Device

Huawei Proprietary and Confidential

Figure 3-2 Co-transmission with a convergence device

3.3 Co-transmission Without a Convergence Device

Huawei Proprietary and Confidential

Figure 3-3 Co-transmission without a convergence device

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

4.1 Features Related to LOFD-003002 2G/3G and LTE Cotransmission

Mutually Exclusive Features

Huawei Proprietary and Confidential

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

Huawei Proprietary and Confidential

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

6.1.3 Inter-NE Interfaces

6.1.4 Operation and Maintenance

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

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

7.2 Required Information

Huawei Proprietary and Confidential

2G/3G and LTE

2G/3G and LTE

7.4.3 Data Preparation

User-defined: parameter values set by users

Prepare the following data before the deployment:

Huawei Proprietary and Confidential

This parameter specifies the maximum IP

This parameter specifies the speed mode