2G, 3G and LTE Co-Transmission (ERAN15.1 - Draft A)

eRAN
2G, 3G and LTE Co-transmission

Feature Parameter Description
Issue Draft A
Date 2018-12-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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 Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. i

eRAN
2G, 3G and LTE Co-transmission Feature Parameter
Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 Draft A (2018-12-30)................................................................................................................................... 1
2 About This Document.................................................................................................................. 2

2.1 General Statements......................................................................................................................................................... 2
2.2 Applicable RAT.............................................................................................................................................................. 3
2.3 Features in This Document.............................................................................................................................................3
2.4 Feature Differences Between NB-IoT and FDD............................................................................................................ 3
3 Overview......................................................................................................................................... 4
4 2G/3G and LTE Co-transmission................................................................................................6
4.1 Principles........................................................................................................................................................................ 6
4.1.1 Co-transmission with a Convergence Device..............................................................................................................7
4.1.2 Co-transmission Without a Convergence Device........................................................................................................ 7
4.2 Network Analysis........................................................................................................................................................... 9
4.2.1 Benefits........................................................................................................................................................................ 9
4.2.2 Impacts.........................................................................................................................................................................9
4.3 Requirements.................................................................................................................................................................. 9
4.3.1 Licenses..................................................................................................................................................................... 10
4.3.2 Software.....................................................................................................................................................................10
4.3.3 Hardware................................................................................................................................................................... 10
4.3.4 Others.........................................................................................................................................................................10
4.4 Operation and Maintenance.......................................................................................................................................... 11
4.4.1 Data Configuration.................................................................................................................................................... 11
4.4.1.1 Data Preparation..................................................................................................................................................... 11
4.4.1.2 Using MML Commands......................................................................................................................................... 21
4.4.1.3 Using the CME....................................................................................................................................................... 22
4.4.2 Activation Observation..............................................................................................................................................22
4.4.3 Network Monitoring.................................................................................................................................................. 22
5 Parameters..................................................................................................................................... 23
6 Counters........................................................................................................................................ 24
7 Glossary......................................................................................................................................... 25
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
Description Contents
8 Reference Documents................................................................................................................. 26
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
Description 1 Change History
1 Change History
This section describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
1.1 eRAN15.1 Draft A (2018-12-30)

This issue introduces the following changes to eRAN13.1 01 (2018-04-10).
Technical Changes
None
Editorial Changes
Reorganized this document using a new template.
Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
l The technical principles of features and their related parameters
l The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
l Requirements of the operating environment that must be met before feature activation
l Parameter configuration required for feature activation, verification of feature activation,
and monitoring of feature performance
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature Parameter
Description documents apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
Trial Features
Trial features are features that are not yet ready for full commercial release for certain
reasons. For example, the industry chain (terminals/CN) may not be sufficiently compatible.
However, these features can still be used for testing purposes or commercial network trials.
Anyone who desires to use the trial features shall contact Huawei and enter into a
memorandum of understanding (MoU) with Huawei prior to an official application of such
trial features. Trial features are not for sale in the current version but customers may try them
for free.
Customers acknowledge and undertake that trial features may have a certain degree of risk
due to absence of commercial testing. Before using them, customers shall fully understand not
only the expected benefits of such trial features but also the possible impact they may exert on
the network. In addition, customers acknowledge and undertake that since trial features are
free, Huawei is not liable for any trial feature malfunctions or any losses incurred by using the
trial features. Huawei does not promise that problems with trial features will be resolved in

eRAN
Description 2 About This Document
the current version. Huawei reserves the rights to convert trial features into commercial
features in later R/C versions. If trial features are converted into commercial features in a later
version, customers shall pay a licensing fee to obtain the relevant licenses prior to using the
said commercial features. If a customer fails to purchase such a license, the trial feature(s)
will be invalidated automatically when the product is upgraded.
2.2 Applicable RAT

This document applies to FDD/NB-IoT.
2.3 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Section
LOFD-003002 2G/3G and LTE Co- 4 2G/3G and LTE Co-

transmission transmission
This document describes the following NB-IoT features.
Feature ID Feature Name Section
MLOFD-003002 2G/3G and eNodeB Co- 4 2G/3G and LTE Co-

transmission transmission
2.4 Feature Differences Between NB-IoT and FDD

NB-IoT Feature FDD Feature Difference Section
MLOFD-003002 LOFD-003002 This feature works the same way in 4 2G/3G and LTE Co-
2G/3G and 2G/3G and LTE NB-IoT and FDD. The only transmission
eNodeB Co- Co-transmission difference is that the main control
transmission board of an FDD eNodeB can be an
LMPT, UMPT, or UMDU, whereas
the main control board of an NB-IoT
eNodeB can only be an LMPT or
UMPT.

eRAN
Description 3 Overview
3 Overview
With the 2G/3G and LTE Co-transmission feature, an eNodeB not only provides LTE
services, but also works as a hub to provide routing and Dynamic Host Configuration
Protocol (DHCP) relay functions for lower-level cascaded base stations (including GBTSs,
eGBTSs, and NodeBs) and to transmit data transparently to the base station controllers.
The following table describes typical scenarios for 2G/3G and LTE Co-transmission.
Lower-Level Networking
Cascaded Base
Station
GBTS l The FE port on the LMPT/UMPT/UMDU of an eNodeB is

connected to the GTMU of a GBTS.
l The IP over E1/T1 port on the UMPT/UMDU of an eNodeB is
connected to the GTMU of a GBTS.
eGBTS l The FE/GE port on the LMPT/UMPT/UMDU of an eNodeB is

connected to the UMPT/UMDU of an eGBTS.
connected to the UMPT/UMDU of an eGBTS.
NodeB l The FE port on the LMPT/UMPT/UMDU of an eNodeB is

connected to the WMPT of a NodeB.
l The FE/GE port on the LMPT/UMPT/UMDU of an eNodeB is
connected to the UMPT/UMDU of a NodeB.
connected to the UMPT/UMDU/WMPT of a NodeB.
NOTE
UMDUs cannot be used as the main control boards of LTE NB-IoT eNodeBs.
When 2G/3G and LTE Co-transmission is used, it is recommended that the eNodeB provide
FE/GE ports to connect to the BSC/RNC/MME/S-GW. It is not recommended that the
eNodeB provide IP over E1/T1 ports to connect to the BSC/RNC/MME/S-GW. The causes
are as follows:

eRAN
Description 3 Overview
l The MME and S-GW do not support IP over E1/T1 ports. When the eNodeB provides
E1/T1 ports for co-transmission, the IP over E1/T1 connection must be terminated on a
router (seldom occurs).
l Generally, the service traffic of the eNodeB is heavy, and IP over E1/T1 ports cannot
meet the service bandwidth requirements of the LTE network.
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.

eRAN
Description 4 2G/3G and LTE Co-transmission
4 2G/3G and LTE Co-transmission
4.1 Principles
Co-transmission enables eNodeBs to be deployed in areas where GBTSs, eGBTSs, and
NodeBs have been deployed. eNodeBs can be cascaded with Huawei base stations of other
RATs through FE/GE ports or IP over E1/T1 ports. Transmission resources can be shared as
long as the cascaded base stations support the corresponding physical ports.
Figure 4-1 shows the networking for this feature. The differences between this feature and the
IP-Based Multi-mode Co-Transmission on BS side feature are as follows:
l 2G/3G and LTE Co-transmission is applicable to single-mode base stations to implement
co-transmission through cascading.
l The IP-Based Multi-mode Co-Transmission on BS side feature implements co-
transmission through panel or backplane interconnection of multimode base stations. For
details, see Common Transmission for SingleRAN.
Figure 4-1 2G/3G and LTE co-transmission
In a network enabled with 2G/3G and LTE Co-transmission, the eNodeB serves as a
convergence node to provide the DHCP relay function for lower-level cascaded base stations.

eRAN
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 evenly distributed transmission between local data flows and transit
data flows.
There are two networking scenarios for 2G/3G and LTE Co-transmission:
l Co-transmission with a convergence device
l Co-transmission without a convergence device
4.1.1 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 4-2 shows co-transmission with a convergence device.
Figure 4-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 cost and management workload.
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.
4.1.2 Co-transmission Without a Convergence Device

If no convergence device is used, GBTSs/eGBTSs/NodeBs use IP over E1 or IP over Ethernet
ports to connect to an eNodeB. Data flows (for services, signaling, and O&M) from the
GBTSs/eGBTSs/NodeBs are converged at the eNodeB and are then transmitted over the IP
network. Figure 4-3 shows co-transmission without a convergence device.

eRAN
Figure 4-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
The eNodeB must provide at least two E1/T1 or FE/GE ports to achieve 2G/3G and LTE co-
transmission:
l One port connects to a base station of another RAT.
l The other port connects to the IP transport 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. This is specifically introduced
to allow the eNodeB to implement co-transmission 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) contained within. The eNodeB forwards the transit data flows based on two different
routing policies:
l If destination-based routing is used, the eNodeB searches for the output port based on the
destination IP address. It then transmits the transit data flows from the output port to the
destination service node.
l If source-based routing is used, the eNodeB searches for the output port based on the
source IP address. It then transmits the transit data flows from the output port to the
destination service node.
DHCP Relay
Generally, base stations use DHCP to obtain the IP address of packets, requiring the DHCP
client (the base station) and the DHCP server to ideally be in the same broadcast domain.
However, in co-transmission mode the cascaded GBTSs/eGBTSs/NodeBs are not in the same
broadcast domain as the DHCP server. In this case, the eNodeB must use the DHCP relay
function to complete the layer-3 DHCP process for all cascaded base stations. The eNodeB
converts DHCP broadcast messages from the cascaded GBTSs/eGBTSs/NodeBs into unicast
messages, which are then sent 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

eRAN
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
The eNodeB configures dedicated transmission resource groups to prevent GSM/UMTS
transit data flows from affecting eNodeB data flows. The eNodeB data flows use resources in
other transmission resource groups. The WRR scheduling function helps to control the data
flows between the transmission resource groups to ensure equality during scheduling.
The LMPT/UMPT/UMDU uses priority queue (PQ) or WRR scheduling (non-PQ) to perform
scheduling for queues in a transmission resource group, ensuring 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 allocated group
bandwidth is reserved for each queue during transmission. This ensures equality between
transmission resource groups, while maintaining differentiation.
NOTE
If the eNodeB provides Internet Protocol Security (IPsec) for the cascaded base stations, configure
correct Access Control List (ACL) rules for the cascaded base stations. If the ACL rules are incorrect,
the transmission for the cascaded base stations will fail.
4.2 Network Analysis
4.2.1 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 operating expense (OPEX).
4.2.2 Impacts
Network Impacts
After the feature is enabled, services of the lower-level cascaded base stations will be
interrupted if the eNodeB is faulty, is upgraded, or experiences transmission interruption.
After the feature is enabled, the data flows of lower-level cascaded base stations are
forwarded by the eNodeB. The uplink and downlink traffic of these cascaded base stations
occupies the eNodeB's transmission bandwidth and affects the eNodeB's forwarding
performance.
Function Impacts
None
4.3 Requirements

eRAN
4.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit
FDD LOFD-003002 2G/3G and LTE LT1SCOTRAN0 per eNodeB

Co-transmission 0
NB-IoT MLOFD-003002 2G/3G and ML1SCOTRAN0 per eNodeB

eNodeB Co- 0
transmission
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been activated and
mutually exclusive functions have been deactivated. For detailed operations, see the relevant
feature documents.
Prerequisite Functions
None
Mutually Exclusive Functions

None
4.3.3 Hardware
Base Station Models
For FDD, the following base stations are compatible with this function:
l 3900 and 5900 series base stations
l DBS3900 LampSite and DBS5900 LampSite
Boards
N/A
RF Modules
N/A
4.3.4 Others
If a lower-level base station is a NodeB:
l The destination IP address of the route from the U2020 to the NodeB's DHCP relay is
the IP address of an eNodeB port. If the eNodeB has multiple port IP addresses,
configure routes to all port IP addresses.
l The next hop of the route from the NodeB to the RNC is the IP address of the eNodeB
port connected to the NodeB.

eRAN
If a lower-level base station is a GBTS/eGBTS:
l The next hop of the route from the GBTS/eGBTS to the GBSC is the IP address of the
eNodeB port connected to the GBTS/eGBTS.
l The destination IP address of the route from the GBSC to the GBTS's DHCP relay is the
IP address of an eNodeB port. If the eNodeB has multiple port IP addresses, configure
routes to all port IP addresses.
l The destination IP address of the route from the U2020 to the eGBTS's DHCP relay is
the IP address of an eNodeB port. If the eNodeB has multiple port IP addresses,
configure routes to all port IP addresses.
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation

Before enabling this feature, ensure that common transmission parameters have been
configured. For details about how to configure common transmission parameters, see IPv4
Transmission.
l The ETHPORT MO 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 Setting Notes

Name
Subboard Type ETHPORT.SBT Set this parameter to

BASE_BOARD(Base Board).
Port Attribute ETHPORT.PA 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),
approximately 1 minute is required to
activate the port. If the attribute of the optical
port on the peer device is modified, this
modification takes effect only after this
optical port on the peer device is reset or the
Ethernet port on the local eNodeB is reset by
running the RST ETHPORT command.
Maximum ETHPORT.MTU Set this parameter based on the transport

Transmission network plan.
Unit

eRAN

Name
Speed ETHPORT.SPEED The value of this parameter must be

consistent with that of the interconnected
port.
Duplex ETHPORT.DUPLEX The value of this parameter must be

consistent with that of the peer end.
NOTE
In GL co-transmission, if the panels of the GTMU and the LTE main control board are
interconnected through fiber optic cables, the ports on the GSM side must be 100 Mbit/s full-
duplex optical ports. In this case, the following requirements must be met on the eNodeB side:
ETHPORT.PA must be set to FIBER(Fiber), ETHPORT.SPEED to 100M(100M), and
ETHPORT.DUPLEX to FULL(Full Duplex).
A transmission configuration model can be either old or new. The data preparation and
configuration for this feature vary according to the transmission configuration model. For
details about the old and new models, see IPv4 Transmission.
When the value of GTRANSPARA.TRANSCFGMODE is OLD, the old transmission
configuration model is used:
l The DEVIP MO specifies the IP address of the port for cascading on the eNodeB. The
key parameters in this MO are described in the following table.
Name
Subboard Type DEVIP.SBT Set this parameter to

IP Address DEVIP.IP This IP address must be in the same

network segment as those of the lower-
level cascaded base stations.
Mask DEVIP.MASK The network segment specified by this

parameter must be identical to the
network segment of the port IP addresses
of the lower-level cascaded base
stations.
Port Type DEVIP.PT l If the eNodeB uses an 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 an Ethernet port
to connect to the transport network,
set this parameter to ETH(Ethernet
Port) or ETHTRK(Ethernet
Trunk).

eRAN
l The IPRT MO 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 NodeB, routes to
the RNC and U2020 must be configured. If the cascaded base station is a GBTS, a route
to the BSC must be configured. The key parameters in this MO are described in the
following table.
Name
Route Index IPRT.RTIDX -
Destination IP IPRT.DSTIP l You are not advised to set both of

these parameters to 0.0.0.0.
Mask IPRT.DSTMASK
l In cascading scenarios, a route to the
RNC or BSC must be configured.
The destination IP address and
network segment are the service IP
address and network segment,
respectively, of the RNC or BSC.
logical IP address of the cascaded
base station must be set. The
destination IP address and network
segment are the logical IP address
and network segment of the cascaded
base station, respectively.
Subboard Type IPRT.SBT Set this parameter to

Route Type IPRT.RTTYPE l If the eNodeB uses an Ethernet port

set this parameter to
NEXTHOP(Next Hop).
l Set this parameter to IF(Exit
Interface) in an E1 networking
scenario.
Port Type IPRT.IFT If the eNodeB uses an E1 port to connect

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

IPRT.RTTYPE parameter is set to
NEXTHOP(Next Hop). Set the
parameter to the IP address of the
gateway on the transport network to
which the eNodeB is connected.

eRAN

Name
Preference IPRT.PREF If a backup IP route is required, this

parameter is required to specify the
priorities of the active and backup
routes. A smaller value indicates a
higher priority.
The eNodeB does not support route-
level load sharing. Therefore, different
routes to the same destination network
segment must have different priorities.
l (Optional) The DHCPRELAYSWITCH MO specifies whether to turn on the DHCP

relay switch on the eNodeB. This switch must be turned on only when the lower-level
cascaded base stations of the eNodeB need to be deployed by PnP. The key parameter in
this MO is described in the following table.
Name
DHCP Relay DHCPRELAYSWIT Set this parameter to

Switch CH.ES ENABLE(Enable).
l (Optional) The DHCPSVRIP MO specifies the IP address of the DHCP server for the
cascaded base stations. The key parameters in this MO are described in the following
table.
Name
DHCP Server IP DHCPSVRIP.DHCP l If the cascaded base station is a

Address SVRIP NodeB, set this parameter to the IP
address of the U2020 or RNC.
l If the cascaded base station is a
GBTS, set this parameter to the IP
address of the GBSC.
l (Optional) The RSCGRP MO specifies dedicated transmission resource groups for

services of the cascaded base stations. The data flows of the eNodeB and cascaded base
stations use different transmission resource groups. The key parameters in this MO are
described in the following table.
Name
Transmission RSCGRP.RSCGRPI Set this parameter based on the network

Resource Group D plan.
ID

eRAN

Name
Subboard Type RSCGRP.SBT Set this parameter to

Bearing Port RSCGRP.PT Set this parameter according to the type

Type of the physical port connecting the MME
and S-GW.
Tx Bandwidth RSCGRP.TXBW Set the maximum TX bandwidth for the

transmission resource group based on
the network plan. This parameter is used
in single-rate mode.
Rx Bandwidth RSCGRP.RXBW Set the maximum RX bandwidth for the

transmission resource group based on
the network plan. This parameter is used
in single-rate mode.
The RX bandwidth does not take effect
on transit data flows. It is mainly used
for local flow admission based on the
bandwidth.
Tx Committed RSCGRP.TXCBS Set this parameter based on the network

Burst Size plan. The value of RSCGRP.TXCBS
must be greater than or equal to that of
RSCGRP.TXBW.
TX Excessive RSCGRP.TXEBS Set this parameter based on the network

Burst Size plan. You are advised to set this
parameter to two times that of the TX
Bandwidth value.
Scheduling RSCGRP.WEIGHT Set this parameter based on the network

Weight plan in case of physical bandwidth
restriction. The default value is
recommended.
TX Committed RSCGRP.TXCIR Set this parameter based on the network

Information plan. This parameter is used in double-
Rate rate mode.
RX Committed RSCGRP.RXCIR Set this parameter based on the network

Rate rate mode.
TX Peak RSCGRP.TXPIR Set this parameter based on the network

Rate rate mode.
RX Peak RSCGRP.RXPIR Set this parameter based on the network

Rate rate mode.

eRAN

Name
TX Peak Burst RSCGRP.TXPBS Set this parameter based on the network

Size plan.
The value of RSCGRP.TXPBS in a
transmission resource group must be
greater than or equal to that of
RSCGRP.TXCBS.
The value of RSCGRP.TXPBS in a
transmission resource group must be
greater than or equal to that of
RSCGRP.TXPIR.
l (Optional) The IP2RSCGRP MO 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
Transmission Resource Management. The key parameters in this MO are described in the
following table.
Name
Mapping Index IP2RSCGRP.MAPID N/A

X
Transmission IP2RSCGRP.BEAR Set this parameter to IP(IP).

Resource Group
Bear Type
Bearing Port IP2RSCGRP.PT Set this parameter based on the network

Type plan.
Bearing Port No. IP2RSCGRP.PN Set this parameter based on the network
plan.
Transmission IP2RSCGRP.RSCGR Set this parameter based on the network

Resource Group PID plan.
ID
Destination IP IP2RSCGRP.DSTIP Set this parameter based on the network

plan.
Mask IP2RSCGRP.DSTMA Set this parameter based on the network

SK plan.
When the value of GTRANSPARA.TRANSCFGMODE is NEW, the new transmission

configuration model is used:
l The INTERFACE MO specifies the attributes of the interface for cascading on the
eNodeB. The key parameters in this MO are described in the following table.

eRAN

Name
Interface ID INTERFACE.ITFID Set this parameter based on the network

plan.
Interface Type INTERFACE.ITFTY Set this parameter based on the network

PE plan.
Port Type INTERFACE.PT Set this parameter based on the network

plan.
Port ID INTERFACE.PORTI Set this parameter based on the network

D plan.
VLAN Tagged INTERFACE.TAGG Set this parameter based on the network

Switch ED plan.
VLAN ID INTERFACE.VLANI Set this parameter based on the network

D plan.
IPv4 Maximum INTERFACE.MTU4 Set this parameter based on the network

Transmission plan.
Unit
l The IPADDR4 MO specifies the attributes of the interface for cascading on the eNodeB.
The key parameters in this MO are described in the following table.
Name
Interface ID IPADDR4.ITFID Set this parameter based on the network

plan.
IP Address IPADDR4.IP Set this parameter based on the network

plan. This IP address must be in the
same network segment as those of the
lower-level cascaded base stations.
Mask IPADDR4.MASK Set this parameter based on the network

plan. The network segment specified by
this parameter must be identical to the
network segment of the port IP addresses
of the lower-level cascaded base
stations.
l The IPROUTE4 MO 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 NodeB,
routes to the RNC and U2020 must be configured. If the cascaded base station is a
GBTS, a route to the BSC must be configured. The key parameters in this MO are
described in the following table.

eRAN

Name
Route Index IPROUTE4.RTIDX N/A
Destination IP IPROUTE4.DSTIP l You are not advised to set both of

these parameters to 0.0.0.0.
Mask IPROUTE4.DSTMAS
K l In cascading scenarios, a route to the
RNC or BSC must be configured.
The destination IP address and
network segment are the service IP
address and network segment,
respectively, of the RNC or BSC.
logical IP address of the cascaded
base station must be set. The
destination IP address and network
segment are the logical IP address
and network segment of the cascaded
base station, respectively.
Route Type IPROUTE4.RTTYPE l If the eNodeB uses an Ethernet port

set this parameter to
NEXTHOP(Next Hop).
l Set this parameter to IF(Exit
Interface) in an E1 networking
scenario.
Next Hop IP IPROUTE4.NEXTH This parameter is valid only when the

OP IPRT.RTTYPE parameter is set to
NEXTHOP(Next Hop). Set the
parameter to the IP address of the
gateway on the transport network to
which the eNodeB is connected.
Preference IPROUTE4.PREF If a backup IP route is required, this

parameter is required to specify the
priorities of the active and backup
routes. A smaller value indicates a
higher priority.
The eNodeB does not support route-
level load sharing. Therefore, different
routes to the same destination network
segment must have different priorities.
l (Optional) The DHCPRELAYSWITCH MO specifies whether to turn on the DHCP

relay switch on the eNodeB. This switch must be turned on only when the lower-level
cascaded base stations of the eNodeB need to be deployed by PnP. The key parameter in
this MO is described in the following table.

eRAN

Name
DHCP Relay DHCPRELAYSWIT Set this parameter to

Switch CH.ES ENABLE(Enable).
l (Optional) The DHCPSVRIP MO specifies the IP address of the DHCP server for the
cascaded base stations. The key parameters in this MO are described in the following
table.
Name
DHCP Server IP DHCPSVRIP.DHCP l If the cascaded base station is a

Address SVRIP NodeB, set this parameter to the IP
address of the U2020 or RNC.
l If the cascaded base station is a
GBTS, set this parameter to the IP
address of the GBSC.
l (Optional) The IPRSCGRP MO specifies dedicated transmission resource groups for

services of the cascaded base stations. The data flows of the eNodeB and cascaded base
stations use different IP transmission resource groups. The key parameters in this MO
are described in the following table.
Name
IP Transmission IPRSCGRP.IPRSCG Set this parameter based on the network

Resource Group RPID plan.
ID
Bearing Port IPRSCGRP.PT Set this parameter based on the network

Type plan.
Bearing Port ID IPRSCGRP.PORTID Set this parameter based on the network

plan.
Resource Group IPRSCGRP.RSCGRP Set this parameter based on the network

Number NO plan.
TX Bandwidth IPRSCGRP.TXBW Set this parameter based on the network

plan.
RX Bandwidth IPRSCGRP.RXBW Set this parameter based on the network

plan.
TX Committed IPRSCGRP.TXCBS Set this parameter based on the network

Burst Size plan.
TX Excessive IPRSCGRP.TXEBS Set this parameter based on the network

Burst Size plan.

eRAN

Name
TX Committed IPRSCGRP.TXCIR Set this parameter based on the network

Information plan.
Rate
RX Committed IPRSCGRP.RXCIR Set this parameter based on the network

Information plan.
Rate
TX Peak IPRSCGRP.TXPIR Set this parameter based on the network

Information plan.
Rate In an IP transmission resource group, the
value of IPRSCGRP.TXPIR must be
greater than or equal to the value of
IPRSCGRP.TXCIR.
RX Peak IPRSCGRP.RXPIR Set this parameter based on the network

Information plan.
Rate In an IP transmission resource group, the
value of IPRSCGRP.RXPIR must be
IPRSCGRP.RXCIR.
TX Peak Burst IPRSCGRP.TXPBS Set this parameter based on the network

Size plan.
In an IP transmission resource group, the
value of IPRSCGRP.TXPBS must be
IPRSCGRP.TXCBS.
l (Optional) The IP2IPRSCGRP MO specifies a dedicated IP transmission resource

group for services of the cascaded base stations. This document does not describe how to
specify an IP transmission resource group for local data flows. For detailed operations,
see Transmission Resource Management. The key parameters in this MO are described
in the following table.
Name
IP to IP IP2IPRSCGRP.IP2I Set this parameter based on the network

Transmission PRSCGRPID plan.
Resource Group
ID
IP Transmission IP2IPRSCGRP.IPRS Set this parameter based on the network

Resource Group CGRPID plan.
ID
IP Version IP2IPRSCGRP.IPVE Set this parameter based on the network

RSION plan.

eRAN

Name
Destination IPv4 IP2IPRSCGRP.DSTI Set this parameter based on the network

Address PV4 plan.
Subnet Mask IP2IPRSCGRP.DST Set this parameter based on the network

MASK plan.
Destination IPv6 IP2IPRSCGRP.DSTI Set this parameter based on the network

Address PV6 plan.
Prefix Length IP2IPRSCGRP.PFX Set this parameter based on the network

LEN plan.
4.4.1.2 Using MML Commands
Activation Command Examples

When GTRANSPARA.TRANSCFGMODE is set to OLD:
//Setting the attributes of the Ethernet port for cascading on the eNodeB
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=1, PA=FIBER, MTU=1500,
SPEED=1000M, DUPLEX=FULL, ARPPROXY=ENABLE, FC=OPEN, FERAT=10, FERDT=10;
//Adding the device IP address of the Ethernet port for cascading on the eNodeB
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=1, IP="10.2.2.2",
MASK="255.255.255.0";
//Adding the route from the eNodeB to the peer device of a lower-level cascaded
base station (GBTS in this example)
//Using destination-based routing
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="100.3.3.3",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.2", PREF=60;
//Using source-based routing
ADD SRCIPRT:
SRCRTIDX=1,SN=7,SBT=BASE_BOARD,SRCIP="10.2.2.1",RTTYPE=NEXTHOP,NEXTHOP="10.1.1.2";
//Turning on the DHCP relay switch on the eNodeB
SET DHCPRELAYSWITCH: ES=ENABLE;
//Setting the IP address of the DHCP server for the GBTS
ADD DHCPSVRIP: DHCPSVRIP="100.3.3.3";
//Adding a transmission resource group for transit data flows
ADD RSCGRP: SN=7,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0,RU=KBPS;
//Adding transit data flows to a specified transmission resource group
ADD IP2RSCGRP:
MAPIDX=0,SN=7,SBT=BASE_BOARD,PT=ETH,DSTIP="100.3.3.3",DSTMASK="255.255.255.0";
When GTRANSPARA.TRANSCFGMODE is set to NEW:

//Setting the attributes of the Ethernet port for cascading on the eNodeB
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=1, PA=FIBER, MTU=1500,
SPEED=1000M, DUPLEX=FULL, ARPPROXY=ENABLE, FC=OPEN, FERAT=10, FERDT=10;
//Adding an interface to the Ethernet port for cascading on the eNodeB
ADD INTERFACE: ITFID=1, ITFTYPE=NORMAL, PT=ETH, PORTID=1, TAGGED=DISABLE,;
//Adding the device IP address of the Ethernet port for cascading on the eNodeB
ADD IPADDR4: ITFID=1, IP="10.2.2.2", MASK="255.255.255.0";
//Adding the route from the eNodeB to the peer device of a lower-level cascaded
base station (GBTS in this example)
//Using destination-based routing
ADD IPROUTE4: RTIDX=0, DSTIP="100.3.3.3", DSTMASK="255.255.255.0",
RTTYPE=NEXTHOP, NEXTHOP="10.1.1.2", PREF=60;
//Turning on the DHCP relay switch on the eNodeB
SET DHCPRELAYSWITCH: ES=ENABLE;
//Setting the IP address of the DHCP server for the GBTS

eRAN
ADD DHCPSVRIP: DHCPSVRIP="100.3.3.3";

//Adding an IP transmission resource group for transit data flows
ADD IPRSCGRP: IPRSCGRPID=1,PT=ETH,PORTID=1,RSCGRPNO=1,RU=KBPS;
//Adding transit data flows to a specified IP transmission resource group
ADD IP2RSCGRP: MAPID=0,IPRSCGRPID=1,DSTIP="100.3.3.3",DSTMASK="255.255.255.0";
4.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.
4.4.2 Activation Observation

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

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

eRAN
Description 5 Parameters
5 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.
l eNodeBFunction Parameter Reference: contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
NOTE
You can find the EXCEL files of parameter reference for the software version used on the live network
from the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from parameter
reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and choose
Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End

eRAN
Description 6 Counters
6 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l eNodeBFunction Performance Counter Summary: contains all counters related to radio
access functions, including air interface management, access control, mobility control,
and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 1 Open the EXCEL file of performance counter reference.
Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

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

eRAN
Description 8 Reference Documents
8 Reference Documents
This chapter lists the reference documents related to 2G/3G and LTE Co-transmission.
1. IPv4 Transmission
2. Transmission Resource Management
3. Common Transmission
4. eRAN Troubleshooting Guide

2G, 3G and LTE Co-Transmission (ERAN15.1 - Draft A)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

2G, 3G and LTE Co-Transmission (ERAN15.1 - Draft A)

Загружено:

Авторское право:

Доступные форматы

eRAN

2G, 3G and LTE Co-transmission

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.................................................................................................................. 2

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. ii

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. iii

1.1 eRAN15.1 Draft A (2018-12-30)

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 1

2 About This Document

2.1 General Statements

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 2

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Section

LOFD-003002 2G/3G and LTE Co- 4 2G/3G and LTE Co-

This document describes the following NB-IoT features.

Feature ID Feature Name Section

MLOFD-003002 2G/3G and eNodeB Co- 4 2G/3G and LTE Co-

2.4 Feature Differences Between NB-IoT and FDD

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 3

GBTS l The FE port on the LMPT/UMPT/UMDU of an eNodeB is

eGBTS l The FE/GE port on the LMPT/UMPT/UMDU of an eNodeB is

NodeB l The FE port on the LMPT/UMPT/UMDU of an eNodeB is

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 4

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 5

4 2G/3G and LTE Co-transmission

Figure 4-1 2G/3G and LTE co-transmission

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 6

4.1.1 Co-transmission with a Convergence Device

Figure 4-2 Co-transmission with a convergence device

4.1.2 Co-transmission Without a Convergence Device

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 7

Figure 4-3 Co-transmission without a convergence device

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 8

4.2 Network Analysis

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 9

FDD LOFD-003002 2G/3G and LTE LT1SCOTRAN0 per eNodeB

NB-IoT MLOFD-003002 2G/3G and ML1SCOTRAN0 per eNodeB

Mutually Exclusive Functions

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 10

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

4.4 Operation and Maintenance

4.4.1 Data Configuration

4.4.1.1 Data Preparation

Parameter Parameter ID Setting Notes

Subboard Type ETHPORT.SBT Set this parameter to

Port Attribute ETHPORT.PA The port attributes of the physical port

Maximum ETHPORT.MTU Set this parameter based on the transport

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 11

Parameter Parameter ID Setting Notes

Speed ETHPORT.SPEED The value of this parameter must be

Duplex ETHPORT.DUPLEX The value of this parameter must be

Subboard Type DEVIP.SBT Set this parameter to

IP Address DEVIP.IP This IP address must be in the same

Mask DEVIP.MASK The network segment specified by this

Port Type DEVIP.PT l If the eNodeB uses an E1/T1 port to

Issue Draft A (2018-12-30) Copyright © Huawei Technologies Co., Ltd. 12

Route Index IPRT.RTIDX -

Destination IP IPRT.DSTIP l You are not advised to set both of

Subboard Type IPRT.SBT Set this parameter to