Bandwidth Sharing of Multimode Base Station Co-Transmission (SRAN12.1 - 01)

SingleRAN
SRAN12.1
Bandwidth Sharing of Multimode

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

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

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

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
Bandwidth Sharing of Multimode Base Station 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 Base Station Types....................................................................................................................... 3
1.5 Functional Differences Between NB-IoT and FDD....................................................................................................... 4
2 Overview......................................................................................................................................... 5
2.1 Introduction.................................................................................................................................................................... 5
2.2 Benefits........................................................................................................................................................................... 5
2.3 Application Networking................................................................................................................................................. 6
3 Technical Description...................................................................................................................7
3.1 Introduction.................................................................................................................................................................... 7
3.2 Transmission Priorities................................................................................................................................................... 7
3.3 Traffic Limiting and Shaping....................................................................................................................................... 10
3.4 Load Control.................................................................................................................................................................12
3.5 Flow Control.................................................................................................................................................................12
4 Application Scenarios.................................................................................................................17
4.1 Unlimited Access Bandwidth for Multimode Base Stations........................................................................................ 17
4.1.1 Introduction............................................................................................................................................................... 17
4.1.2 Transmission Resource Management Strategies....................................................................................................... 18
4.2 Limited Access Bandwidth for Multimode Base Stations............................................................................................21
4.2.1 Introduction............................................................................................................................................................... 21
4.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios................................................................. 26
4.3.1 Introduction............................................................................................................................................................... 26
4.4 Satellite Transmission for Multimode Base Stations (Without Distinguishing Transmission Priorities).................... 30
4.4.1 Introduction............................................................................................................................................................... 30
5 Related Features...........................................................................................................................34
5.1 MRFD-121115 Bandwidth sharing of MBTS Multi-mode Co-Transmission(GBTS)................................................. 34
5.2 MRFD-121125 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NodeB)................................................34
Issue 01 (2017-03-08) Huawei Proprietary and Confidential ii

SingleRAN
Transmission Feature Parameter Description Contents
5.3 MRFD-121135 Bandwidth sharing of MBTS Multi-mode Co-Transmission(eNodeB)..............................................35

5.4 MRFD-121145 Bandwidth sharing of MBTS Multi-mode Co-Transmission(LTE TDD)...........................................35
5.5 MRFD-121155 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NB-IoT).............................................. 36
6 Network Impact........................................................................................................................... 37
7 Engineering Guidelines............................................................................................................. 38
7.1 When to Use................................................................................................................................................................. 38
7.2 Required Information................................................................................................................................................... 38
7.3 Planning........................................................................................................................................................................ 38
7.4 Deployment.................................................................................................................................................................. 39
7.4.1 Requirements............................................................................................................................................................. 39
7.4.2 Precautions.................................................................................................................................................................39
7.4.3 Hardware Adjustment................................................................................................................................................40
7.4.4 Data Preparation........................................................................................................................................................ 40
7.4.5 Initial Configuration.................................................................................................................................................. 48
7.4.5.1 Access Bandwidth Unlimited for GUL/GUT/GULT Triple-Mode Base Stations..................................................48
7.4.5.2 Unlimited Access Bandwidth for GU Dual-Mode Base Stations...........................................................................52
7.4.5.3 Unlimited Access Bandwidth for GL/GT Dual-Mode Base Stations.....................................................................53
7.4.5.4 Unlimited Access Bandwidth for UL/UT/ULT Multimode Base Stations.............................................................54
7.4.5.5 Limited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations........................................................56
7.4.5.6 Limited Access Bandwidth for GU Dual-Mode Base Stations.............................................................................. 62
7.4.5.7 Limited Access Bandwidth for GL/GT/GLT Multimode Base Stations................................................................ 65
7.4.5.8 Limited Access Bandwidth for UL/UT/ULT Multimode Base Stations................................................................ 65
7.4.5.9 Access Bandwidth Limited for Each Operator in a UL/UT Dual-Mode Base Station in RAN Sharing Scenarios
............................................................................................................................................................................................ 68
7.4.5.10 GU Dual-Mode Base Stations Using Satellite Transmission............................................................................... 75
7.4.6 Activation Observation..............................................................................................................................................78
7.4.6.1 Unlimited Access Bandwidth for Multimode Base Stations.................................................................................. 78
7.4.6.2 Limited Access Bandwidth for Multimode Base Stations......................................................................................78
7.4.6.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios........................................................... 81
7.5 Performance Monitoring...............................................................................................................................................82
7.6 Parameter Optimization................................................................................................................................................ 82
7.7 Possible Issues.............................................................................................................................................................. 82
8 Parameters..................................................................................................................................... 83
9 Counters........................................................................................................................................ 94
10 Glossary....................................................................................................................................... 95
11 Reference Documents............................................................................................................... 96
Issue 01 (2017-03-08) Huawei Proprietary and Confidential iii

SingleRAN
Transmission Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the Bandwidth Sharing of Multimode Base Station Co-Transmission
feature, including the bandwidth sharing mechanism, recommended transmission
configuration strategies, application scenarios, related features, network impact, and
engineering guidelines. This feature applies to GSM/UMTS, GSM/LTE, UMTS/LTE, and
GSM/UMTS/LTE multimode base stations in co-transmission scenarios.
This document describes the following optional features:
l MRFD-121115 Bandwidth sharing of MBTS Multi-mode Co-Transmission(GBTS)
l MRFD-121125 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NodeB)
l MRFD-121135 Bandwidth sharing of MBTS Multi-mode Co-Transmission(eNodeB)
l MRFD-121145 Bandwidth sharing of MBTS Multi-mode Co-Transmission(LTE TDD)
l MRFD-121155 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NB-IoT)
Unless otherwise specified, in this document, LTE, eNodeB, and eRAN always include FDD,
TDD, and NB-IoT. The "L", "T", and "M" in RAT acronyms refer to LTE FDD, LTE TDD,
and LTE NB-IoT, respectively.
For definitions of base stations described in this document, see section "Base Station
Products" in SRAN Networking and Evolution Overview Feature Parameter Description.
1.2 Intended Audience

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

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

SingleRAN
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
SRAN12.1 01 (2017-03-08)
This issue does not include any changes.
SRAN12.1 Draft A (2016-12-30)

Draft A (2016-12-30) of SRAN12.1 introduces the following changes to Issue 01
(2016-02-29) of SRAN11.1.
Change Change Description Parameter Change

Type
Feature Added Bandwidth Sharing of Multimode Base None

change Station Co-Transmission for NB-IoT. For
details, see the following sections:
l 1.5 Functional Differences Between NB-
IoT and FDD
l 3.2 Transmission Priorities
l 4 Application Scenarios
l 5 Related Features
l 7.4.1 Requirements
l 7.4.5 Initial Configuration
Changed the following features from optional to None

basic, deleted their licenses, and updated feature
IDs:
l ID of Bandwidth sharing of MBTS Multi-
mode Co-Transmission(GBTS) changed
from MRFD-211505 to MRFD-121115
mode Co-Transmission(NodeB) changed
mode Co-Transmission(eNodeB) changed
mode Co-Transmission(LTE TDD)changed
mode Co-Transmission(NB-IoT) changed

SingleRAN
Change Change Description Parameter Change

Type
Editorial None None

change
1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations
Feature ID Feature Name Suppo Suppo Suppo
rted rted rted
by by by
Macro Micro Lamp
Base Base Site
Statio Statio Base
ns ns Statio
ns
MRFD-121115 Bandwidth sharing of MBTS Multi- Yes No No

mode Co-Transmission(GBTS)
MRFD-121125 Bandwidth sharing of MBTS Multi- Yes Yes Yes

mode Co-Transmission(NodeB)
MRFD-121135 Bandwidth sharing of MBTS Multi- Yes Yes Yes

mode Co-Transmission(eNodeB)
MRFD-121145 Bandwidth sharing of MBTS Multi- Yes No Yes

mode Co-Transmission(LTE TDD)
MRFD-121155 Bandwidth sharing of MBTS Multi- Yes Yes No

mode Co-Transmission(NB-IoT)
Function Implementation in Macro, Micro, and LampSite Base Stations

The function implementation is the same for macro, micro, and LampSite base stations.
Among micro base stations, only the BTS3911E supports the Bandwidth sharing of MBTS
Multi-mode Co-Transmission feature.

SingleRAN
1.5 Functional Differences Between NB-IoT and FDD

Feature Feature Featur Feature Functional Difference
ID for Name e ID Name
NB-IoT for NB- for for FDD
IoT FDD
MRFD- Bandwidt MRFD- Bandwid NB-IoT supports mapping between traffic

121155 h sharing 121135 th classes and transmission priorities, and
of MBTS sharing traffic limiting and shaping, but does not
Multi- of MBTS support load control or flow control.
mode Multi- When the user plane Cellular Internet of
Co- mode Things (CIoT) EPS optimization function is
Transmis Co- implemented on the NB-IoT eNodeB and
sion(NB- Transmis evolved packet core (EPC), the S1-C and S1-
IoT) sion(eNo U interfaces are supported. When the control
deB) plane CIoT EPS optimization function is
implemented on the NB-IoT eNodeB and
EPC, only the S1-C interface is supported.
For details about the user plane CIoT EPS
optimization function and control plane
CIoT EPS optimization function, see NB-
IoT Radio and Performance Basics Feature
Parameter Description.

SingleRAN
Transmission Feature Parameter Description 2 Overview
2 Overview
2.1 Introduction
The Bandwidth Sharing of Multimode Base Station Co-Transmission feature centrally
manages GSM, UMTS, and LTE transmission resources. When transmission resources are
congested, this feature ensures the smooth processing of high-priority services and prevents
GSM, UMTS, and LTE services from impacting each other. This ensures high service quality
and good user experience. Bandwidth Sharing of Multimode Base Station Co-Transmission
includes the following transmission resource management strategies: mapping between traffic
classes and transmission priorities, traffic limiting and shaping, load control, and flow control.
If this feature is not enabled, the transmission resources of a multimode base station are
managed in the same way as those of a single-mode base station. For details about
transmission resource management strategies for GSM, UMTS, and LTE, see Transmission
Resource Management Feature Parameter Description for GBSS and RAN, and Transport
Resource Management Feature Parameter Description for eRAN, respectively.
2.2 Benefits
GSM, UMTS, and LTE services have different peak hours. Therefore, transmission resources
of one mode can be multiplexed by other modes if this mode is not experiencing a traffic
peak. The Bandwidth Sharing of Multimode Base Station Co-Transmission feature provides
the following benefits:
l For a multimode base station in co-transmission scenarios, transmission resources can be
dynamically shared by GSM, UMTS, and LTE.
l As GSM services continuously shrink, the released GSM bandwidth can be used by
UMTS and LTE services.
l When uplink or downlink transmission resources of a multimode base station are
congested, the quality of service (QoS) of high-priority GSM, UMTS, and LTE services
can be guaranteed.

SingleRAN
Transmission Feature Parameter Description 2 Overview
2.3 Application Networking

This feature applies to networking schemes where both the local end (the multimode base
station) and the peer end (the base station controller, MME, or S-GW) use IP transmission (IP
over FE/GE or IP over E1/T1).
Figure 2-1 shows the networking scheme for a co-MPT GUL triple-mode base station in co-
transmission scenarios.
Figure 2-1 Networking scheme for a co-MPT GUL multimode base station in co-
transmission scenarios
For details about the networking scheme for a multimode base station in co-transmission
scenarios, see Common Transmission Feature Parameter Description for SingleRAN.
NOTE
l In this document, a multimode base station can be a GU/GL/GT/UL/UT/LT dual-mode base station,
a GUL/GLT/ULT/GUT triple-mode base station, or a GULT quadruple-mode base station. The
GSM, UMTS, or LTE side of a multimode base station is referred to as the GBTS/eGBTS, NodeB,
or eNodeB. LTE can be LTE FDD, LTE TDD, or LTE NB-IoT.
l Multimode base stations are classified into co-MPT and separate-MPT multimode base stations. The
GSM side of a separate-MPT multimode base station can be either an eGBTS or a GBTS. The GSM
side of a co-MPT multimode base station must be an eGBTS. The GBTS is not recommended for
providing a co-transmission port to a separate-MPT multimode base station. This scenario is not
covered in this document.

SingleRAN
Transmission Feature Parameter Description 3 Technical Description
3 Technical Description
3.1 Introduction
For a separate-MPT multimode base station in co-transmission scenarios, the co-transmission
port transmits and receives the local data and the passing data. In this case, the co-
transmission port centrally schedules and manages the data of multiple modes. For a co-MPT
multimode base station in co-transmission scenarios, the co-transmission port transmits and
receives only the local data, which includes the data for all modes of this base station. In this
case, the co-transmission port centrally schedules and manages the data for all modes.
To enable a co-transmission port to implement unified data scheduling and management,
differentiation and fairness among different service types and modes must be ensured.
Moreover, transmission resource congestion when all of the modes have overlapping traffic
bursts must also be addressed. To address these problems, Huawei introduces the Bandwidth
Sharing of Multimode Base Station Co-Transmission feature.
NOTE
l Differentiation: Transmission differentiation is used when transmission bandwidth is limited.

Transmission differentiation prioritizes bandwidth use, with real-time services taking precedence
over non-real-time services.
l Fairness: If transmission congestion occurs, service differentiation ensures that real-time services are
preferentially processed. As a result, non-real-time services may experience packet losses, which
affects fairness among non-real-time services. The transmission flow control function enables each
type of service or each mode to be allocated a certain amount of bandwidth. This eliminates the
possibility that a certain service or a certain mode experiences service interruptions because of lack
of transmission bandwidth.
This feature adopts four recommended transmission resource management strategies:

mapping between traffic classes and transmission priorities, traffic limiting and shaping, load
control, and flow control. For details about transmission resource management strategies for
GSM, UMTS, and LTE, see Transmission Resource Management Feature Parameter
Description for GBSS and WCDMA RAN, and Transport Resource Management Feature
Parameter Description for eRAN, respectively.
3.2 Transmission Priorities

In the Bandwidth Sharing of Multimode Base Station Co-Transmission feature, the mapping
between GSM/UMTS/LTE traffic classes and transmission priorities must be configured to

SingleRAN
ensure that differentiated services (DiffServ) are provided to different service types based on
transmission priorities. Transmission priorities include the DiffServ Code Point (DSCP),
virtual local area network (VLAN) priority, and queue priority.
DSCP
DSCP is a field in an IP packet header to indicate the QoS requirements. Each node
implements DiffServ based on the DSCP value.
A multimode base station or a base station controller sets the DSCP value for each IP packet
based on the QoS requirements of each service type. From the DSCP value, intermediate
transmission devices identify the traffic class and related QoS requirements of the service and
perform per-hop behavior (PHB) accordingly. PHB includes transmission resource allocation,
queue scheduling, and packet discarding. All nodes in the network comply with PHB policies
according to the DSCP in the IP packet.
The following table describes how to use MML commands to configure the mapping between
traffic classes and DSCP values for each type of base station.
NE Command Description
GBTS SET BTSVLAN Used to set the mapping between DSCP values
and data from the O&M plane, control plane (CP),
and user plane (UP) on the GBTS side.
eGBTS and SET DIFPRI Used to set the mapping between DSCP values
NodeB and data from the O&M plane and CP plane on
the eGBTS or NodeB side.
ADD TRMMAP Used to set the mapping between DSCP values

and SET and data from the UP on the BSC or RNC side.
PHBMAP
eNodeB SET DIFPRI Used to set the mapping between DSCP values
and data from the O&M plane and CP plane on
the eNodeB side.
MOD Used to set the mapping between DSCP values

UDTPARAGRP and data from the UP on the eNodeB side.
Pay attention to the following when mapping traffic classes and DSCP values:
l For separate-MPT multimode base stations in co-transmission scenarios, run the

necessary MML commands to individually map the DSCP values to the data from the
O&M plane and CP for the GBTS, eGBTS, NodeB, and eNodeB. For co-MPT
multimode base stations in co-transmission scenarios, run the SET DIFPRI command
once to map the DSCP values to the data from the O&M plane and CP for the eGBTS,
NodeB, and eNodeB.
l For multimode base stations in co-transmission scenarios, run the necessary MML
commands to individually map the DSCP values to the data from the UP for the GBTS,
eGBTS, NodeB, and eNodeB.

SingleRAN
NOTE
The mapping between traffic classes and DSCP values for GSM, UMTS, and LTE services should be
consistent on the base station, the base station controller, and the CN.
If control-plane EPS optimized transmission is used, NB-IoT services are carried only on SCTP links.
The priority for the control-plane data is the priority for NB-IoT services.
VLAN Priority
The VLAN tag defines the VLAN priority of an IP packet. Based on the VLAN priority,
Layer 2 devices can implement DiffServ.
VLAN priorities of packets with different traffic classes are determined by DSCP values.
Table 3-1 provides the default mapping between DSCP values and VLAN priorities on the
multimode base station side.
Table 3-1 Default mapping between DSCP values and VLAN priorities
DSCP VLAN Priority
0-7 0
8-15 1
16-23 2
24-31 3
32-39 4
40-47 5
48-55 6
56-63 7
Queue Priority
Queue priority defines the scheduling priority of a queue. Each Ethernet port or Point-to-Point
Protocol (PPP) link supports eight queues: PQ1, PQ2, PQ3, and WRR (which includes WFQ4
through WFQ8). The queues are displayed in descending order of scheduling priority. A
multimode base station puts packets with different traffic classes into different queues to
implement DiffServ.
NOTE
PQ is short for priority queue.

WFQ is short for weighted fair queuing, which involves the bandwidth allocation weight factors. With
WFQ, the bandwidth is allocated to each queue based on their weight factors and each queue is
cyclically scheduled.
WRR is short for weighted round robin. WFQ4 through WFQ7 have the same weight.
Queue priorities are determined for different traffic types according to the mapping between
DSCP values and queue priorities. Table 3-2 and Table 3-3 list the default mapping between
DSCP values of GSM, UMTS, and LTE services and queue priorities for multimode base
stations. You are not advised to modify the default mapping.

SingleRAN
Table 3-2 Default mapping between DSCP values and queue priorities for the GBTS
DSCP Queue Queue Priority
40-63 PQ1 0
Reserved PQ2 1
Reserved PQ3 2
32-39 WFQ4 3
24-31 WFQ5 3
16-23 WFQ6 3
8-15 WFQ7 3
0-7 WFQ8 3
Table 3-3 Default mapping between DSCP values and queue priorities for the eGBTS,
NodeB, eNodeB, and co-MPT multimode base station
DSCP Queue Queue Priority
48-63 PQ1 0
40-47 PQ2 1
32-39 PQ3 2
24-31 WFQ4 3
16-23 WFQ5 3
8-15 WFQ6 3
0-7 WFQ7 3
3.3 Traffic Limiting and Shaping

When transmission resources are limited, intermediate transmission devices may be incapable
of receiving excess packets that arrive at the co-transmission port in a multimode base station.
To prevent intermediate transmission devices from discarding packets, the traffic limiting
function is introduced. PS services have unstable data rates due to unexpected traffic bursts.
The traffic shaping function is introduced to ensure stable rates in a multimode base station.
The traffic limiting and shaping functions use the Generic Traffic Shaping (GTS) technology,
which shapes irregular data flows to balance the bandwidth between upstream and
downstream nodes. These functions minimize packet discarding and congestion caused by
traffic bursts. Figure 3-1 shows the working principles of traffic limiting and shaping.

SingleRAN
Figure 3-1 Working principles of traffic limiting and shaping
The traffic limiting and shaping functions apply only to non-real-time services.
NOTE
Base stations cannot dynamically adjust the data rates of real-time services. To prevent real-time service
congestion, at the early stage of network deployment, the minimum bandwidth of the intermediate
transmission devices must be greater than the total bandwidth planned for real-time services in a GU,
GL, UL, or GUL multimode base station.
The traffic limiting and shaping functions can be configured at both the base station level and
the logical port level.
Base-station-level traffic limiting and shaping
If the eGBTS, NodeB, or eNodeB provides a co-transmission port, you can run the SET LR
command and specify the LR.CIR parameter to set the bandwidth after traffic limiting for a
base station.
Logical-port-level traffic limiting and shaping
l Separate-MPT multimode base station

SingleRAN
If the eGBTS, NodeB, or eNodeB provides a co-transmission port, you can run the ADD
RSCGRP command and specify the RSCGRP.TXBW parameter to set the bandwidth
after traffic limiting for a logical port.
l Co-MPT multimode base station
You can run the ADD IPLOGICPORT command and specify the
IPLOGICPORT.CIR(BSC6910,BSC6900) parameter to set the bandwidth after traffic
limiting for logical port.
NOTE
You are not advised to modify the rate using the ADD ETHPORT command.
Transport resource groups are classified into default port transport resource groups and non-default port
transport resource groups. One physical port can be configured with one or more default port transport
resource group and multiple non-default port transport resource groups. The following transport resource
group configuration policy is recommended for a co-MPT multimode base station:
l All modes use the same default transport resource group to implement traffic limiting and shaping.
l Each mode uses different non-default transport resource groups to implement traffic limiting and
shaping.
3.4 Load Control

Load control consists of the following functions:
l Admission control
Ensures the quality of admitted services by preventing excessive admission.
l Load reshuffling (LDR)
Increases the admission success rate and system capacity by relieving transmission load
and preventing transmission resource congestion. LTE does not support LDR.
l Overload control (OLC)
Alleviates the negative impact of overload on high-priority users by quickly reducing
transmission load.
Load control for each mode in a multimode base station in co-transmission scenarios is the
same as load control in a single-mode base station. GSM and UMTS loads are controlled by
the related base station controller and LTE load is controlled by the eNodeB. For details about
load control for GSM, UMTS, and LTE, see Transmission Resource Management Feature
Parameter Description for GBSS, RAN, and eRAN, respectively.
NOTE
NB-IoT services do not support load control.
3.5 Flow Control

When transmission bandwidth dynamically changes, the minimum bandwidth of the
intermediate transmission devices in the transmission network may be lower than the
bandwidth limited on the shared port. If the base station keeps transmitting data at the
bandwidth limited, the transport network may be congested. To prevent transport network
congestion, the flow control algorithm is introduced. This algorithm first estimates the
minimum bandwidth of the transmission network based on the transmission quality test result
and then dynamically adjusts the transmit bandwidth to ensure that the transmit bandwidth
does not exceed the minimum bandwidth of the transmission network. GSM, UMTS, and LTE
support the flow control algorithm in different ways:

SingleRAN
Table 3-4 Support for flow control on GSM, UMTS, and LTE
Mode NE Support for Flow Remarks
Control
GSM GBTS/eGBTS and No None

BSC
UMTS NodeB and RNC Yes The flow control

algorithm is also
called the dynamic
flow control
algorithm.
LTE eNodeB Yes The flow control

algorithm is disabled
by default.
The flow control algorithm on a NodeB calculates the transmission delay, the number of
discarded packets, and bandwidth resources available and then performs traffic shaping. In
this way, packet discarding caused by Iub interface congestion is prevented. This algorithm
takes effect only on HSDPA and HSUPA services. The NodeB dynamic flow control
algorithm is classified into two types, as listed in Table 3-5.
Table 3-5 Classification of the NodeB dynamic flow control algorithm

NodeB Dynamic Flow Control Switch Reference Document
Control Algorithm
NodeB uplink bandwidth l Congestion control Transmission Resource

adaptive adjustment switch: Management Feature
algorithm ULFLOWCTRLPARA. Parameter Description for
TNLCONGCTRLSWIT RAN.
CH
l Back pressure algorithm
switch:
RSCGRPALG.TCSW
NodeB HSDPA adaptive Flow control switch:

flow control algorithm DLFLOWCTRLPARA.S
WITCH
For a co-MPT UL or GUL multimode base station in co-transmission scenarios, the NodeB
sends the results of the uplink bandwidth adaptive adjustment algorithm to the eNodeB by
default. The eNodeB then performs uplink flow control according to the results. If the
eNodeB is not expected to use the results of the algorithm, two transmission resource groups
can be configured to carry UMTS and LTE services separately. In this situation, the eNodeB
performs LTE uplink flow control. For details, see Transport Resource Management Feature
Parameter Description for eRAN.
When packet loss (for example, packet loss caused by a bit error) occurs in the transmission
network due to non-congestion reasons, it is recommended that the enhanced function of

SingleRAN
HSDPA flow control and the enhanced function of HSUPA Iub flow control in case of Iub
congestion be enabled to prevent the bandwidth from being falsely decreased by the flow
control algorithm.
l For details about the enhanced function of HSDPA flow control, see HSDPA Feature
Parameter Description.
l For details about the enhanced function of HSUPA Iub flow control in case of Iub
congestion, see Transmission Resource Management Feature Parameter Description for
RAN.
As described in Table 3-6, in UL and GUL co-transmission scenarios, if UMTS HSDPA
services are under flow control, the released UMTS bandwidth may be occupied by LTE
services. Consequently, the bandwidth available for UMTS services may decrease
considerably. To protect the bandwidth for UMTS HSDPA services, turn on the fair flow
control switch DLFLOWCTRLPARA.FAIRSWITCH on the NodeB side.
Table 3-6 Fair flow control switch on the NodeB side in co-transmission scenarios
Co-Transmission Whether the Fair Flow Control Switch Takes Effect
Scenario
Separate-MPT UL No
multimode base station
using panel
interconnection
Separate-MPT GUL
using panel
interconnection
Co-MPT UL multimode The fair flow control switch

base station DLFLOWCTRLPARA.FAIRSWITCH takes effect only if
the NodeB configurations meet the following conditions:
Separate-MPT UL
l Link mode
The value of the PT parameter in the
using backplane
DLFLOWCTRLPARA MO is the same as that of the PT
interconnection
parameter in the IPPATH MO of the UMTS mode.
Co-MPT GUL triple- l Endpoint mode
mode base station The value of the PT parameter in the
DLFLOWCTRLPARA MO is the same as that of the PT
Separate-MPT GUL parameter corresponding to the local IP address configured
multimode base station in the USERPLANEHOST MO of the UMTS mode.
using backplane
interconnection
It is recommended that the DLFLOWCTRLPARA.FAIRRATIO parameter be set to a value

between 30% (included) and 70% (included). Otherwise, the actual bandwidth of UMTS
HSDPA services may be inconsistent with the guard bandwidth configured for fair flow
control. The default value of the DLFLOWCTRLPARA.FAIRRATIO parameter is equal to
30% of the actual receive bandwidth of the base station. That is, when the total bandwidth of
UMTS HSDPA services decreases to 30% of the actual receive bandwidth of the base station,
rate reduction will no longer be performed on these services.

SingleRAN
The fair flow control switch can be configured either on a physical port (preferred) of a co-
MPT UL dual-mode base station or on the corresponding loopback interface (also called a
logical port) of the physical port. When configured on the loopback interface, the fair flow
control switch for co-MPT multimode base stations applies only to the following scenarios:
l Scenario 1: One loopback interface corresponds to one physical port, and UMTS and
LTE services are carried on the same physical port, as shown in Figure 3-2.
l Scenario 2: One loopback interface corresponds to multiple physical ports, and UMTS
and LTE services are carried on different physical ports, as shown in Figure 3-3.
Figure 3-2 Scenario 1
Figure 3-3 Scenario 2
NOTE
Scenario 2 does not belong to the multimode base station co-transmission networking scenario. It is
recommended that you configure the DLFLOWCTRLPARA.FAIRSWITCH for the loopback interface
in scenario 2.
The fair flow control switch ensures that at least 30% of the actual receive bandwidth is retained for
UMTS HSDPA services. This does not mean that the bandwidth retained for UMTS USDPA services is
equal to 30% of the actual receive bandwidth.
For details about the flow control algorithm, see Transmission Resource Management Feature
Parameter Description for RAN.

SingleRAN
NOTE
NB-IoT services do not support flow control.

SingleRAN
Transmission Feature Parameter Description 4 Application Scenarios
4 Application Scenarios
4.1 Unlimited Access Bandwidth for Multimode Base

Stations
4.1.1 Introduction
Access bandwidth unlimited for multimode base stations refers to scenarios in which:
l The operator cannot or has not planned access bandwidth for each multimode base
station.
l The bandwidth of the converging device, which converges the data of multimode base
stations, is either limited or unlimited.
For example, in Figure 4-1, the access bandwidth for each multimode base station is 100
Mbit/s and the bandwidth for intermediate transmission devices is also 100 Mbit/s.
Figure 4-1 Access bandwidth unlimited for multimode base stations

SingleRAN
4.1.2 Transmission Resource Management Strategies
(Optional) Configuring Traffic Limiting and Shaping on the Base Station

Controller Side
Traffic limiting and shaping can be configured on the base station controller side if the
operator can dimension transmission bandwidth required by a base station based on the traffic
model. The bandwidth after rate limitation is calculated based on the service model.
Configuring the Mapping Between Traffic Classes and Transmission Priorities

Table 4-1 lists recommended transmission priorities for different traffic classes. For details
about the mapping between DSCP values and traffic classes, see descriptions about DSCP in
3.2 Transmission Priorities.
Table 4-1 Recommended transmission priorities for different traffic classes if access
bandwidth is unlimited for multimode base stations
NE Traffic Class PHB DSCP VLAN

Priority
GBTS ESL/OML/RSL CS6 48 6
CS Voice EF 46 5
CS Data/PS High PRI AF41 34 4
PS Low PRI AF31 26 3
IP Clock EF 46 5
EML AF21 18 2
eGBTS SCTP CS6 48 6
CS Voice EF 46 5
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
NodeB SCTP CS6 48 6
CCH&SRB&AMR EF 46 5
Conversational&Streami AF41 34 4
ng
R99 AF21 18 2
interactive&background

SingleRAN

Priority
HSxPA AF11 10 1
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
eNodeB SCTP CS6 48 6
QCI1 EF 46 5
QCI2 AF41 34 4
QCI3 AF41 34 4
QCI4 AF41 34 4
QCI5 EF 46 5
QCI6 AF21 18 2
QCI7 AF21 18 2
QCI8 AF21 18 2
QCI9 BE 0 0
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
In most cases, intermediate transmission devices support queue scheduling. Layer 3 and Layer
2 intermediate transmission devices support eight queues. However, if intermediate
transmission devices in the bearer network support less than eight queues, transmission
priority combining strategies listed in Table 4-2 are recommended. You can combine packets
with different DSCP values into one queue and combine packets with different VLAN
priorities into one queue. For example, if the intermediate transmission devices support six
queues, packets whose DSCP values are 48 and 46 can be put into one queue. Accordingly,
packets whose VLAN priorities are 6 and 5 can be put into one queue. This queue has the
highest transmission priority.
Table 4-2 Recommended transmission priority combining strategies if access bandwidth is

unlimited for multimode base stations
Number of DSCP Value for Each Queue VLAN Priority for Each Queue
Queues
6 (48+46), 34, 26, 18, 10, 0 (6+5), 4, 3, 2, 1, 0

SingleRAN
Queues
5 (48+46), (34+26), 18, 10, 0 (6+5), (4+3), 2, 1, 0
4 (48+46), (34+26+18), 10, 0 (6+5), (4+3+2), 1, 0
3 (48+46), (34+26+18+10), 0 (6+5), (4+3+2+1), 0
NOTE
If there are only two queues, obtain from Huawei technical support personnel the method of combining
DSCP values.
If control-plane EPS optimized transmission is used, NB-IoT services are carried on SCTP links. The
transmission priority mapping for NB-IoT services is the transmission priority mapping for SCTP
services.
Configuring the Flow Control Algorithm

Table 4-3 provides recommended settings for the NodeB dynamic flow control algorithm and
the HSDPA fair flow control switch.
Table 4-3 Recommended settings for the NodeB flow control algorithm and the HSDPA fair
flow control switch if the access bandwidth is unlimited for multimode base stations
Base Station Type Setting of the Setting of the Setting of the
ULFLOWCTRLP DLFLOWCTRLP DLFLOWCTRLP
ARA.TNLCONGC ARA.SWITCH ARA.FAIRSWITC
TRLSWITCH H
Separate-MPT GU ON(On) (default BW_SHAPING_O N/A

dual-mode base value) NOFF_TOGGLE(
station BW_SHAPING_O
NOFF_TOGGLE)
Co-MPT GU dual- (default value)
mode base station
Separate-MPT GL N/A N/A N/A

dual-mode base
station
Co-MPT GL dual-
mode base station
Separate-MPT UL ON(On) (default BW_SHAPING_O ENABLE

dual-mode base value) NOFF_TOGGLE(
station BW_SHAPING_O
NOFF_TOGGLE)
Co-MPT UL dual- (default value)
mode base station
The bearer network
Separate-MPT GUL must support two or
triple-mode base more queues.
station

SingleRAN
Base Station Type Setting of the Setting of the Setting of the

ULFLOWCTRLP DLFLOWCTRLP DLFLOWCTRLP
ARA.TNLCONGC ARA.SWITCH ARA.FAIRSWITC
TRLSWITCH H
Co-MPT GUL
triple-mode base
station
NOTE
NB-IoT services do not support flow control.
4.2 Limited Access Bandwidth for Multimode Base

Stations
4.2.1 Introduction
Limited access bandwidth for multimode base stations refers to scenarios in which:
l The maximum data rate for each multimode base station must not exceed the planned
bandwidth.
l The bandwidth of intermediate transmission devices is either limited or unlimited.
The access bandwidth for a base station is limited if the bearer network is leased or if the base
station uses satellite, microwave, or xPON to receive data.
For example, in Figure 4-2, the access bandwidth for the three multimode base stations is
limited to 10 Mbit/s.
Figure 4-2 Limited access bandwidth for multimode base stations

SingleRAN
Configuring Traffic Limiting and Shaping on the Base Station Controller Side
Configure traffic limiting and shaping on the base station controller side and set the
bandwidth limit to the access bandwidth planned by the operator for a multimode base station.
Configuring Traffic Limiting and Shaping on the Co-Transmission Port of the

Base Station Side
Configure traffic limiting and shaping on the con-transmission port of the base station side
and set the bandwidth limit to the access bandwidth planned by the operator for a multimode
base station.
Configuring the Mapping Between Traffic Classes and DSCP Values

Table 4-4 lists recommended transmission priorities for different traffic classes.
bandwidth is limited for multimode base stations

Priority
CS Voice EF 46 5
IP Clock CS6 46 6
EML AF21 18 2
eGBTS SCTP CS6 48 6
CS Voice EF 46 5
OM High EF 46 5
OM Low AF21 18 2
IP Clock CS6 46 6
NodeB SCTP CS6 48 6
CCH&SRB&AMR EF 46 5
Conversational&Strea AF41 34 4
ming

SingleRAN

Priority
R99 AF21 18 2
interactive&backgroun
d
HSxPA AF11 10 1
interactive&backgroun
d
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
QCI1 EF 46 5
QCI2 AF41 34 4
QCI3 AF41 34 4
QCI4 AF41 34 4
QCI5 EF 46 5
QCI6 AF21 18 2
QCI7 AF21 18 2
QCI8 AF21 18 2
QCI9 BE 0 0
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5

SingleRAN

limited for multimode base stations
Queues
6 (48+46), 34, 26, 18, 10, 0 (6+5), 4, 3, 2, 1, 0
5 (48+46), (34+26), 18, 10, 0 (6+5), 4, 3, 2, (1+0)
4 (48+46), (34+26+18), 10, 0 (6+5), (4+3+2), 1, 0
3 (48+46), (34+26+18+10), 0 (6+5), (4+3+2+1), 0
NOTE
DSCP values.
services.

Table 4-6 provides recommended settings for the NodeB flow control algorithm and the
HSDPA fair flow control switch. Pay attention to the following in data configurations:
l The RSCGRPALG.TCSW parameter is set to ENABLE by default. If you want to set
this parameter to DISABLE, first run the ADD RSCGRP command to add a default
transmission resource group to the co-transmission port with RSCGRP.RSCGRPID set
to DEFAULTPORT. Then set RSCGRPALG.TCSW to DISABLE for the default
transmission resource group you have added.
If the co-transmission port is configured with a transmission resource group whose
RSCGRP.RSCGRPID is set to AUTOPORT, first run the RMV RSCGRP command
to delete this group and then run the ADD RSCGRP command with
RSCGRP.RSCGRPID set to DEFAULTPORT to add a transmission resource group.
If the co-transmission port is not configured with a transmission resource group, run the
ADD RSCGRP command with RSCGRP.RSCGRPID set to DEFAULTPORT to add a
transmission resource group.
l If the configured UL committed information rate (CIR) is less than or equal to 2 Mbit/s,
you need to set RSCGRPALG.TCSW to DISABLE. Otherwise, the OM service rate
may decrease dramatically.
l If a separate-MPT multimode base station uses backplane interconnection to implement
co-transmission, the tunnel type (TUNNEL.TUNNELTYPE) of the main control board
that provides the co-transmission port must be set to DL and that of the main control
board that does not provide the co-transmission port must be set to UL. If the tunnel type
is incorrect, the traffic control function cannot work properly. For details about tunnel
type configuration, see Common Transmission Feature Parameter Description.
l NB-IoT services do not support flow control.

SingleRAN
flow control switch if access bandwidth is limited for multimode base stations
Base Station Setting of the Setting of the Setting of the Setting of the
Type RSCGRPALG. ULFLOWCTR DLFLOWCT DLFLOWCT
TCSW LPARA.TNLC RLPARA.SWI RLPARA.FAI
ONGCTRLSW TCH RSWITCH
ITCH
Separate-MPT ENABLE(Enabl ON(On) BW_SHAPING N/A

GU dual-mode e) (default (default value) _ONOFF_TOG
base station value) GLE(BW_SHA
PING_ONOFF
Co-MPT GU _TOGGLE)
dual-mode base (default value)
station
Separate-MPT ENABLE(Enabl N/A N/A N/A

GL dual-mode e) (default
base station value)
Co-MPT GL
dual-mode base
station
Separate-MPT l ENABLE(E ON(On) BW_SHAPIN ENABLE

UL dual-mode nable) (default value) G_ONOFF_T
base station (default OGGLE(BW_
value): if co- SHAPING_O
Separate-MPT transmission NOFF_TOGG
GUL triple- is LE) (default
mode base implemented value)
station through The bearer
backplane network must
interconnecti support two or
on more queues.
l DISABLE(
Disable): if
co-
transmission
is
implemented
through
panel
interconnecti
on
Co-MPT UL ENABLE(Enab ON(On) BW_SHAPIN ENABLE

dual-mode base le) (default (default value) G_ONOFF_T
station value) OGGLE(BW_
SHAPING_O
NOFF_TOGG
LE) (default
value)

SingleRAN
Type RSCGRPALG. ULFLOWCTR DLFLOWCT DLFLOWCT
TCSW LPARA.TNLC RLPARA.SWI RLPARA.FAI
ONGCTRLSW TCH RSWITCH
ITCH
Co-MPT GUL The bearer

triple-mode network must
base station support two or
more queues.
Configuring the Load Control Algorithm

When co-transmission is applied, the load control algorithm for each mode in a multimode
base station is configured in the same way as the load control algorithm in a single-mode base
station. For details about load control for GSM, UMTS, and LTE, see Transmission Resource
Management Feature Parameter Description for GBSS and RAN, and Transport Resource
Management Feature Parameter Description for eRAN, respectively.
NOTE
4.3 Limited Access Bandwidth for Each Operator in RAN

Sharing Scenarios
4.3.1 Introduction
Limited access bandwidth for each operator in radio access network (RAN) sharing scenarios
refer to scenarios in which:
l Multiple operators share one multimode base station.
l Access bandwidth of one operator is not shared by other operators.
l Access bandwidth of one operator is shared among services of each mode run by this
operator.
l Access bandwidth for each operator is limited.
Access bandwidth for each operator is limited when the bearer network is leased. In
RAN15.0, limited access bandwidth for multiple operators in RAN sharing scenarios
applies only to UL dual-mode base stations. For example, in Figure 4-3, the access
bandwidth for each operator is limited to 10 Mbit/s.

SingleRAN
Figure 4-3 Limited access bandwidth for each operator in RAN sharing scenarios

Configure a logical port for each operator on the base station controller side. Set the
bandwidth limited on the logical port to the access bandwidth planned by the operator.

Base Station Side
Configure a logical port for each operator on the co-transmission port of the base station side.
Set the bandwidth limited on the logical port to the access bandwidth planned by the operator.

bandwidth is limited for each operator in RAN sharing scenarios
Priority
NodeB SCTP CS6 48 6
CCH&SRB&AMR EF 46 5
Conversational&Streaming AF41 34 4
R99 AF21 18 2
HSxPA AF11 10 1
OM High EF 46 5

SingleRAN

Priority
OM Low AF21 18 2
IP Clock EF 46 5
QCI1 EF 46 5
QCI2 AF41 34 4
QCI3 AF41 34 4
QCI4 AF41 34 4
QCI5 EF 46 5
QCI6 AF21 18 2
QCI7 AF21 18 2
QCI8 AF21 18 2
QCI9 BE 0 0
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5

limited for each operator in RAN sharing scenarios
Queues
6 (48+46), 34, 26, 18, 10, 0 (6+5), 4, 3, 2, 1, 0
5 (48+46), (34+26), 18, 10, 0 (6+5), 4, 3, 2, (1+0)
4 (48+46), (34+26+18), 10, 0 (6+5), (4+3+2), 1, 0
3 (48+46), (34+26+18+10), 0 (6+5), (4+3+2+1), 0

SingleRAN
NOTE
DSCP values.
services.

Table 4-9 provides recommended settings for the NodeB flow control algorithm and the
HSDPA fair flow control switch. The configuration notes are the same as those of
Configuring the Flow Control Algorithm in 4.2.2 Transmission Resource Management
Strategies.
flow control switch if access bandwidth is limited for each operator in RAN sharing scenarios
Scenario Setting of the Setting of the Setting of the Setting of the
RSCGRPALG ULFLOWCTR DLFLOWCT DLFLOWCT
.TCSW LPARA.TNLC RLPARA.SWI RLPARA.FAI
ONGCTRLS TCH RSWITCH
WITCH
Separate-MPT l ENABLE(E ON(On) BW_SHAPIN ENABLE

UL dual-mode nable) (default value) G_ONOFF_T
base station (default OGGLE(BW_
value): if co- SHAPING_O
transmission NOFF_TOGG
is LE) (default
implemente value)
d through The bearer
backplane network must
interconnect support two or
ion more queues.
ENABLE(E
nable)
(default
value)
l DISABLE(
Disable): if
co-
transmission
is
implemente
d through
panel
interconnect
ion

SingleRAN
Scenario Setting of the Setting of the Setting of the Setting of the

RSCGRPALG ULFLOWCTR DLFLOWCT DLFLOWCT
.TCSW LPARA.TNLC RLPARA.SWI RLPARA.FAI
ONGCTRLS TCH RSWITCH
WITCH
Co-MPT UL ENABLE(Enab
dual-mode base le) (default
station value)

station. For details about how to configure the load control algorithm for UMTS and LTE, see
Transmission Resource Management Feature Parameter Description for RAN and
Transport Resource Management Feature Parameter Description for eRAN, respectively.
NOTE
4.4 Satellite Transmission for Multimode Base Stations

(Without Distinguishing Transmission Priorities)
4.4.1 Introduction
Satellite transmission for multimode base stations (without distinguishing transmission
priorities) refers to scenarios in which differentiated services cannot be performed on satellite
transmission networks based on their transmission priorities. This scenario is applicable only
to GU dual-mode base stations.
Figure 4-4 uses an example of two GU dual-mode base stations for illustrating satellite
transmission. The access bandwidth for each GU dual-mode base station is limited to 4 Mbit/s
and the satellite transmission network where the GU dual-mode base stations access cannot
distinguish their transmission priorities. In this case, transmission packets are processed
according to the first-come first-served policy.

SingleRAN
Figure 4-4 Satellite transmission for GU dual-mode base stations

Configure traffic limiting and shaping on the base station controller side. The bandwidth after
rate limitation for GSM mode is the access bandwidth for multimode base stations planned by
the operator. The bandwidth after rate limitation for UMTS mode is the access bandwidth for
UMTS planned by the operator. The access bandwidth for UMTS mode must be less than that
for multimode base stations, so that the access bandwidth for UMTS mode cannot preempt
that for GSM mode.

Base Station Side
Configure traffic limiting and shaping on the co-transmission port of the base station side.


SingleRAN
Table 4-10 Recommended transmission priorities for different traffic classes if satellite
transmission is used for GU dual-mode base stations
Priority
CS Voice EF 46 5
IP Clock CS6 46 6
EML AF21 18 2
eGBTS SCTP CS6 48 6
CS Voice EF 46 5
OM High EF 46 5
OM Low AF21 18 2
IP Clock CS6 46 6
NodeB SCTP CS6 48 6
CCH&SRB&AMR EF 46 5
Conversational&Streamin AF41 34 4
g
R99 AF21 18 2
HSxPA AF11 10 1
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
NOTE
In this scenario, the satellite transmission does not distinguish transmission priorities. Therefore, the
transmission priorities for the preceding traffic classes take effect on the multimode base station side.

Table 4-11 provides recommended settings for the NodeB flow control algorithm.

SingleRAN
Table 4-11 Recommended settings for the NodeB flow control algorithm if satellite
transmission is used for GU dual-mode base stations
Type RSCGRPALG ULFLOWCTR DLFLOWCT DLFLOWCTR
.TCSW LPARA.TNLC RLPARA.SW LPARA.FAIR
ONGCTRLSW ITCH SWITCH
ITCH
Separate-MPT ENABLE(Enabl ON(On) BW_SHAPIN N/A

GU dual-mode e) (default (default value) G_ONOFF_T
base station value) OGGLE(BW_
SHAPING_O
Co-MPT GU NOFF_TOGG
dual-mode base LE) (default
station value)
NOTE
If the configured UL committed information rate (CIR) is less than or equal to 2 Mbit/s, you need to set
RSCGRPALG.TCSW to DISABLE. Otherwise, the OM service rate may decrease dramatically.

station. For details about how to configure the load control algorithms for GSM and UMTS,
see Transmission Resource Management Feature Parameter Description for GSM BSS and
WCDMA RAN, respectively.

SingleRAN
Transmission Feature Parameter Description 5 Related Features
5 Related Features
5.1 MRFD-121115 Bandwidth sharing of MBTS Multi-

mode Co-Transmission(GBTS)
Prerequisite Features
Feature ID Feature Name Description
MRFD-121114 IP-Based Multi-mode Co-Transmission on BS -

side(GBTS)
Mutually Exclusive Features

None
Impacted Features
None

mode Co-Transmission(NodeB)

side(NodeB)

SingleRAN

None
Impacted Features
None

mode Co-Transmission(eNodeB)

side(eNodeB)

None
Impacted Features
None

mode Co-Transmission(LTE TDD)

side(LTE TDD)

None
Impacted Features
None

SingleRAN

mode Co-Transmission(NB-IoT)

side (NB-IoT)

None
Impacted Features
None

SingleRAN
Transmission Feature Parameter Description 6 Network Impact
6 Network Impact
System Capacity
No impact.
Network Performance
If the settings of inter-RAT parameters, such as inter-RAT bandwidth allocation and inter-RAT
QoS planning, are inappropriate, activating this feature will have the following impacts:
l Increased service congestion rates
l Reduced data rates of low-priority services, for example, best effort (BE) services
l Increased packet loss rates of low-priority services

SingleRAN
Transmission Feature Parameter Description 7 Engineering Guidelines
7 Engineering Guidelines
7.1 When to Use

It is recommended that the Bandwidth Sharing of Multimode Base Station Co-Transmission
feature be activated for a multimode base station where IP-based co-transmission is applied.
7.2 Required Information

To provide guide on how to plan transmission bandwidth and transmission priorities for
multimode base stations and multimode base station controllers, you need to know the
network topology and transmission bandwidth plan, which include transmission bandwidth
available in the bearer network and the queues available on transmission devices.
7.3 Planning
This section describes planning activities you need to complete before you implement the
feature.
RF Planning
N/A
Network Planning
l Transmission bandwidth plan for radio services
Make a transmission bandwidth plan each for the GBTS/eGBTS, NodeB, and eNodeB of
a multimode base station based on the service plan and the corresponding bandwidth
requirements.
l QoS plan for radio services
For a GU, GL, UL, or GUL multimode base station in co-transmission scenarios, it is
recommended that signaling and circuit switched (CS) services be classified as real-time
services and packet switched (PS) services as non-real-time services. Set real-time
services to a higher priority than non-real-time services to ensure the continuity of
signaling and CS services when transmission resources become congested. Activate the

SingleRAN
flow control algorithm for each mode to properly allocate transmission resources across
non-real-time services when transmission resources become congested.
l Traffic class and transmission priority mapping
Plan traffic classes, DSCP values, VLAN priorities, and the mapping between traffic
classes and DSCP values based on the QoS plan of services.
l QoS plan for the bearer network
Plan DSCP values, VLAN priorities, and the number of PQ queues for layer-3 and
layer-2 devices based on service priorities.
l Bandwidth plan for the bearer network
Plan bandwidth for the bearer network based on services' bandwidth requirements and
available bandwidth resources.
When planning transmission bandwidth on the RAN side, ensure that the bandwidth
between a base station and a base station controller is higher than the total bandwidth of
real-time services to avoid reducing the service quality of real-time services.
Hardware Planning
N/A
7.4 Deployment
This section describes how to deploy the Bandwidth Sharing of Multimode Base Station Co-
Transmission feature.
7.4.1 Requirements
Intermediate Transmission Devices

To implement the Bandwidth Sharing of Multimode Base Station Co-Transmission feature,
the bearer network must support QoS management. Otherwise, this feature becomes invalid
when the bearer network is congested. QoS management includes the following aspects:
l Layer-3 devices support DSCP-priority-based QoS management.

l Layer-2 devices support VLAN-priority-based QoS management.
l Intermediate transmission devices support the PQ+WRR queue scheduling function and
at least two PQ queues are supported. (WRR stands for weighted round robin.)
Other Features
For details, see 5 Related Features.
License
This feature has been changed to basic, and is not under license control.
7.4.2 Precautions
None

SingleRAN
7.4.3 Hardware Adjustment

N/A
7.4.4 Data Preparation
Traffic Limiting and Shaping

If access bandwidth is limited for multimode base stations, data for traffic limiting and
shaping must be prepared on the base station side that provides a co-transmission port. Table
7-1 lists the data to prepare for configuring traffic limiting and shaping.
Table 7-1 Data to prepare for configuring traffic limiting and shaping if access bandwidth is
limited for multimode base stations
MO Parameter Parameter ID Setting Notes

Name
LR UL CIR Set this parameter to the access

Committed bandwidth planned by the operator.
Information
Rate
Committed CBS If CIR is set to a value less than 500

Burst Size Mbit/s, set CBS to a value two times
that of CIR, and set EBS to 0 Mbit/s.
Excessive EBS
Burst Size If CIR is set to a value greater than
500 Mbit/s, set CBS to 1000 Mbit/s.
In addition, the sum of the values of
CBS and EBS must be two times that
of CIR
If access bandwidth is limited for each operator in multi-operator scenarios, data for traffic
limiting and shaping must be prepared on the base station side that provides a co-transmission
port. Table 7-2 lists the data to prepare for configuring traffic limiting and shaping.
Table 7-2 Data to prepare for configuring traffic limiting and shaping if access bandwidth is
limited for each operator in multi-operator scenarios

Name
RSCGR Tx TXBW Set this parameter to the access

P Bandwidth bandwidth planned by the operator.
TX TXCBS If TXBW is set to a value less than 500

Committed Mbit/s, set TXCBS to a value two times
Burst Size that of TXBW, and set TXEBS to 0
Mbit/s.

SingleRAN

Name
TX TXEBS If TXBW is set to a value greater than

Excessive 500 Mbit/s, set TXCBS to 1000 Mbit/s.
Burst Size In addition, the sum of the values of
TXCBS and TXEBS must be two times
that of TXBW.
If access bandwidth is unlimited for multimode base stations and limited for each operator in
multi-operator scenarios, data for traffic limiting and shaping must be prepared on the BSC or
RNC side. Table 7-3 lists the data to prepare for configuring traffic limiting and shaping.
Table 7-3 Data to prepare for traffic limiting and shaping on the BSC or RNC side

Name
IPLOGICP Logic Port LPN(BSC6900,BSC691 Set this parameter to the

ORT No. 0) number of the BSC/RNC
logical port.
Bandwidth CIR(BSC6900,BSC691 Set this parameter to the access

0) bandwidth planned by the
operator or bandwidth
calculated by the traffic model.
When the access bandwidth is
limited for each operator in
multi-operator scenarios, set
this parameter to the access
bandwidth planned by each
operator.
Transport QoS
l Transport QoS for GSM services
– Table 7-4 lists the data to prepare for configuring the mapping between DSCP
values and data from the O&M plane, CP, and UP of a GBTS.
values and data from the O&M plane and CP of an eGBTS.
values and data from the O&M plane and CP of a BSC. Table 7-8 lists the data to
prepare for configuring the mapping between DSCP values and data from the UP of
a BSC.
l Transport QoS for UMTS services
values and data from the O&M plane and CP of a NodeB.

SingleRAN
values and data from the O&M plane, CP, and UP of an RNC.
l Transport QoS for LTE services
values and data from the O&M plane and CP of an eNodeB. Table 7-6 lists the data
to prepare for configuring the mapping between DSCP values and data from the UP
of an eNodeB.
Table 7-4 Data to prepare for configuring the mapping between DSCP values and data from
the O&M plane, CP, and UP of a GBTS
Name
BTSVLAN Service Type SERVICETYPE(BS See the recommended

C6900,BSC6910) parameter configurations in
4 Application Scenarios.
DSCP DSCP(BSC6900,BS
C6910)
the O&M plane and CP of the eGBTS, NodeB, and eNodeB side of a co-MPT multimode
base station
Name
DIFPRI Priority Rule PRIRULE Set this parameter to

DSCP(DSCP).
Signaling SIGPRI See the recommended

Priority parameter configurations in
OM High OMHIGHPRI
Priority
OM Low OMLOWPRI
Priority
IP Clock Priority IPCLKPRI

SingleRAN
the UP of an eNodeB
Name
UDTPARAGRP User Data Type UDTPARAGRPID Set this parameter to a value

Transfer ranging from 40 to 48 for
Parameter Group user data types 1 to 9.
ID
Priority PRI See the recommended

parameter configurations in
the O&M plane and CP of a BSC
Name
BSCABISPRIM OML DSCP OMLDSCP(BSC690 See the recommended

AP 0,BSC6910) parameter configurations in
RSL DSCP RSLDSCP(BSC690
0,BSC6910)
EML DSCP EMLDSCP(BSC691

0,BSC6900)
ESL DSCP ESLDSCP(BSC690

0,BSC6910)
the UP of a BSC
MO Parameter Name Parameter ID Setting Notes
TRMMAP CS voice path CSVOICEPATH See the recommended

parameter configurations in
CS data path CSDATAPATH 4 Application Scenarios.
PS high PRI data path PSHPRIDATAPAT
H
PS low PRI data path PSLPRIDATAPAT

H

SingleRAN
the CP and UP of an RNC
TRMMAP Common channel primary CCHPRIPATH See the recommended

path parameter
configurations in 4
IMS SRB primary path SIPPRIPATH Application
SRB primary path SRBPRIPATH Scenarios.
AMR voice primary path VOICEPRIPATH
R99 CS conversational CSCONVPRIPATH

primary path
R99 CS streaming primary CSSTRMPRIPATH

path
R99 PS conversational PSCONVPRIPATH

primary path
R99 PS streaming primary PSSTRMPRIPATH

path
R99 PS high PRI PSINTHGHPRIPAT

interactive primary path H
R99 PS middle PRI PSINTMIDPRIPAT

R99 PS low PRI PSINTLOWPRIPAT

R99 PS background PSBKGPRIPATH

primary path
HSDPA Signal primary HDSRBPRIPATH

path
HSDPA IMS Signal HDSIPPRIPATH

primary path
HSDPA Voice primary HDVOICEPRIPAT

path H
HSDPA conversational HDCONVPRIPATH

primary path
HSDPA streaming primary HDSTRMPRIPATH

path
HSDPA high PRI HDINTHGHPRIPA

interactive primary path TH
HSDPA middle PRI HDINTMIDPRIPAT


SingleRAN
HSDPA low PRI HDINTLOWPRIPA

HSDPA background HDBKGPRIPATH

primary path
HSUPA Signal primary HUSRBPRIPATH

path
HSUPA IMS Signal HUSIPPRIPATH

primary path
HSUPA Voice primary pat HUVOICEPRIPAT

H
HSUPA conversational HUCONVPRIPATH

primary path
HSUPA streaming primary HUSTRMPRIPATH

path
HSUPA high PRI HUINTHGHPRIPA

HSUPA middle PRI HUINTMIDPRIPAT

HSUPA low PRI HUINTLOWPRIPA

HSUPA background HUBKGPRIPATH

primary path
Flow Control
Table 7-10 Data to prepare for setting the flow control algorithm on the NodeB side
Name
RSCGRPALG Traffic Control TCSW See the recommended

Switch parameter configurations
in 4 Application
Scenarios.
ULFLOWCTRLPA Congestion Ctrl TNLCONGCTRL See the recommended

RA Switch SWITCH parameter configurations
in 4 Application
DLFLOWCTRLPA Flow Control SWITCH Scenarios.
RA Switch
Fair Switch FAIRSWITCH

SingleRAN
Other Data
Table 7-11 lists other data to prepare if access bandwidth is limited for multimode base
stations.
Table 7-11 Other data to prepare if access bandwidth is limited for multimode base stations
Data Item Sample Value Remarks
Limited access bandwidth 20 Mbit/s This item specifies the

for a base station uplink and downlink limited
access bandwidth for a base
station.
Downlink bandwidth on the 20 Mbit/s This item specifies the

logical port of the RNC downlink limited access
bandwidth for a base station.
Downlink bandwidth on the 10 Mbit/s Calculates the bandwidth for

logical port of the BSC this port based on the GSM
traffic model of the base
station.
BTS index 1 None
Logical IP address of the 16.16.90.201 None

BTS
Port IP address of the BSC 172.16.140.140 None

NodeB
Iub IP address on the RNC 172.16.100.140 None

side
Table 7-12 Other data to prepare if access bandwidth is limited for each operator in RAN
sharing scenarios

for operator A uplink and downlink limited
access bandwidth for
operator A.

for operator B uplink and downlink limited
access bandwidth for
operator B.

NodeB (for operator A)

SingleRAN

NodeB (for operator B)

eNodeB (for operator A)

eNodeB (for operator B)
Logical IP address of an Iub 172.16.90.140 None

port on the RNC side (for
operator A)
Logical IP address of an Iub 172.16.80.140 None

port on the RNC side (for
operator B)

serving gateway (S-GW)
(for operator A)

serving gateway (S-GW)
(for operator B)
Table 7-13 Other data to prepare if satellite transmission is used for GU dual-mode base
station

for a base station uplink and downlink limited
access bandwidth for a base
station.
Limited access bandwidth in 3 Mbit/s This item specifies the

UMTS mode downlink limited access
bandwidth planned for the
UMTS mode, which must
be lower than the downlink
limited access bandwidth for
the GU dual-mode base
station.

SingleRAN

for GSM mode downlink limited access
bandwidth planned for the
GSM mode, which must be
lower than the downlink
limited access bandwidth for
the GU dual-mode base
station.
BTS index 1 None

BTS
Port IP address of the BSC 172.16.140.140 None

NodeB
Iub IP address on the RNC 172.16.100.140 None

side
7.4.5 Initial Configuration
7.4.5.1 Access Bandwidth Unlimited for GUL/GUT/GULT Triple-Mode Base

Stations
Using MML Commands (GSM Side)

Step 1 Configure a transmission resource mapping (TRM) table on the BSC side by referring to
section 4.1.2 Transmission Resource Management Strategies.
1. Run the ADD TRMMAP command to set the mapping between DSCP values and data
from the UP on the Abis interface.
2. Run the SET BSCABISPRIMAP command to set the mapping between DSCP values
and data from the CP on the Abis interface.
3. Run the ADD ADJMAP command to add the mapping from the Abis interface to the
TRMMAP index.
Step 2 Configure a TRM table on the base station side.

l Run the SET BTSVLAN command to set the mapping between DSCP values and data
from the CP and UP of a GBTS.
l Run the SET DIFPRI command to set the mapping between DSCP values and data from
the CP of an eGBTS.
----End

SingleRAN
MML Command Examples (GSM Side)

//Configuring a TRM table on the BSC side
//Setting the mapping between DSCP values and data from the UP on the Abis interface
ADD TRMMAP:
TMI=111,ITFT=ABIS,TRANST=IP,CSVOICEPATH=EF,CSDATAPATH=AF41,PSHPRIDATAPATH=AF41,PSL
PRIDATAPRI=AF31;
//Setting the mapping between DSCP values and data from the CP on the Abis interface
SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=1, TRANSTYPE=IP, OMLDSCP=48, RSLDSCP=48,
EMLDSCP=18, ESLDSCP=48;
//Adding the mapping from the Abis interface to the TRMMAP index
ADD ADJMAP: ANI=3, ITFT=ABIS, TMIGLD=111, FTI=1;
//Configuring a TRM table on the base station side

//Setting the mapping between DSCP values and data from the CP and UP of a GBTS
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=OML, DSCP=48;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=RSL, DSCP=48;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=EML, DSCP=18;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=ESL, DSCP=48;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSVOICE, DSCP=46;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSDATA, DSCP=34;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= PSHIGHPRI, DSCP=34;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= PSLOWPRI, DSCP=26;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= OTHERDATA, DSCP=46;
//Setting the mapping between DSCP values and data from the CP of an eGBTS
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;
Using MML Commands (UMTS Side)

Step 1 Configure a TRM table on the RNC side by referring to section 4.1.2 Transmission Resource
Management Strategies.
from the UP and CP on the Iub interface.
2. Run the ADD ADJMAP command to add the mapping from the Iub interface to the
TRMMAP index.
Step 2 Run the SET DIFPRI command to set the mapping between DSCP values and data from the
CP of a NodeB.
Step 3 Configure the dynamic flow control algorithm for the NodeB.
1. Run the ADD ULFLOWCTRLPARA command to add an HSUPA flow control
parameter to set the uplink bandwidth adaptive flow control switch.
2. Run the ADD DLFLOWCTRLPARA command to add an HSDPA flow control
parameter to set the HSDPA flow control switch.
----End
MML Command Examples (UMTS Side)

//Configuring a TRM table on the RNC side

SingleRAN
//Setting the mapping between DSCP values and data from the CP and UP on the Iub interface
ADD
TRMMAP:TMI=110,ITFT=IUB,TRANST=IP,CCHPRIPATH=EF,SIPPRIPATH=EF,SRBPRIPATH=EF,VOICEP
RIPATH=EF,CSCONVPRIPATH=AF41,CSSTRMPRIPATH=AF41,PSCONVPRIPATH=AF41,PSSTRMPRIPATH=A
F41,PSINTHGHPRIPATH=AF21,PSINTLOWPRIPATH=AF21,PSBKGPRIPATH=AF21,HDSRBPRIPATH=EF,HD
SIPPRIPATH=EF,HDVOICEPRIPATH=EF,HDCONVPRIPATH=AF41,HDSTRMPRIPATH=AF41,HDINTHGHPRIP
ATH=AF11,HDINTMIDPRIPATH=AF11,HDINTLOWPRIPATH=AF11,HDBKGPRIPATH=AF11,HUSRBPRIPATH=
EF,HUSIPPRIPATH=EF,HUVOICEPRIPATH=EF,HUCONVPRIPATH=AF41,HUSTRMPRIPATH=AF41,HUINTHG
HPRIPATH=AF11,HUINTMIDPRIPATH=AF11,HUINTLOWPRIPATH=AF11,HUBKGPRIPATH=AF11;
//Adding the mapping from the Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Configuring a TRM table on the NodeB side

//Configuring the dynamic flow control algorithm for the NodeB (when the bearer network
supports two or more queues)
//Adding an HSUPA flow control parameter
ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0,
BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;
//In the case of a separate-MPT multimode base station

//Adding an HSDPA flow control parameter
ADD DLFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0,
SWITCH=BW_SHAPING_ONOFF_TOGGLE, FAIRSWITCH=ON;
//In the case of a co-MPT multimode base station

Using MML Commands (LTE Side)

Step 1 Configure a TRM table on the eNodeB side by referring to the recommended settings
described in 4.1.2 Transmission Resource Management Strategies.
1. Run the SET DIFPRI command to set the mapping between DSCP values and data from
the CP of an eNodeB.
2. Run the MOD UDTPARAGRP command to set the mapping between DSCP values and
user plane data from the UP of an eNodeB.
----End
NOTE
If control-plane EPS optimized transmission is used, NB-IoT services are carried on SCTP links. No
configuration for the user-plane MO UDTPARAGRP is required.
MML Command Examples (LTE Side)

//Configuring a TRM table on the eNodeB side
//Setting the mapping between DSCP values and data from the CP of an eNodeB

SingleRAN
//Setting the mapping between DSCP values and user-plane data of an eNodeB. If the control
plane CIoT EPS optimization function is implemented between the NB-IoT eNodeB and
EPC, no user-plane data configuration is required.
MOD UDTPARAGRP: UDTPARAGRPID=40, PRIRULE=DSCP, PRI=46, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=44, PRI=46;
Using the CME

The parameters related to this feature cannot be modified in batches. This section only
describes how to use the CME to perform a single configuration.
Step 1 Set GSM, UMTS, and LTE parameters on the CME according to the operation sequence
described in Table 7-14, Table 7-15, and Table 7-16. For instructions on how to perform the
CME single configuration, see CME Single Configuration Operation Guide.
Table 7-14 MOs on the GSM side

SN MO NE
1 a TRMMAP GBSC
b BSCABISPRIMAP GBSC
c ADJMAP GBSC
2 a BTSVLAN/DIFPRI GBTS/eGBTS
Table 7-15 MOs on the UMTS side

SN MO NE
1 a TRMMAP RNC
b ADJMAP RNC
2 a DIFPRI NodeB
b ULFLOWCTRLPARA NodeB
c DLFLOWCTRLPARA NodeB

SingleRAN
Table 7-16 MOs on the LTE side

SN MO NE
1 a DIFPRI eNodeB
b UDTPARAGRP eNodeB
----End
7.4.5.2 Unlimited Access Bandwidth for GU Dual-Mode Base Stations

See "Using MML Commands (GSM Side)" in section 7.4.5.1 Access Bandwidth
Unlimited for GUL/GUT/GULT Triple-Mode Base Stations.

See "MML Command Examples (GSM Side)MML Command Examples (GSM Side)" in
section 7.4.5.1 Access Bandwidth Unlimited for GUL/GUT/GULT Triple-Mode Base
Stations.

Step 1 Configure a TRM table for the RNC side by referring to section 4.1.2 Transmission
Resource Management Strategies.
TRMMAP index.
CP of the NodeB.
----End
MML Command Examples

ADD

SingleRAN
TMIBRZ=110, FTI=1;

//Configuring the uplink bandwidth adaptive flow control switch and HSDPA flow control
switch on the NodeB side


SWITCH=BW_SHAPING_ONOFF_TOGGLE;
Single Configuration Using the CME

Set parameters GSM and UMTS on the CME according to the operation sequence described
in Table 7-14 and Table 7-17. For instructions on how to perform the CME single
configuration, see CME Single Configuration Operation Guide.

SN MO NE
1 a TRMMAP RNC
b ADJMAP RNC
2 a DIFPRI NodeB
b ULFLOWCTRLPA NodeB
RA
c DLFLOWCTRLPA NodeB
RA
7.4.5.3 Unlimited Access Bandwidth for GL/GT Dual-Mode Base Stations

See "Using MML Commands (GSM Side)" in section 7.4.5.1 Access Bandwidth

SingleRAN

See "MML Command Examples (GSM Side)" in section 7.4.5.1 Access Bandwidth

See "Using MML Commands (LTE Side)" in section 7.4.5.1 Access Bandwidth Unlimited
for GUL/GUT/GULT Triple-Mode Base Stations.

See "MML Command Examples (LTE Side)" in section 7.4.5.1 Access Bandwidth

Set parameters GSM and LTE on the CME according to the operation sequence described in
Table 7-14 and Table 7-16. For instructions on how to perform the CME single configuration,
see CME Single Configuration Operation Guide.
7.4.5.4 Unlimited Access Bandwidth for UL/UT/ULT Multimode Base Stations

TRMMAP index.
CP of a NodeB.
----End

ADD

SingleRAN
TMIBRZ=110, FTI=1;





The operations are the same as those for the LTE side in GUL/GUT/GULT triple-mode base
stations with unlimited access bandwidth. For details, see Using MML Commands (LTE
Side).

The command examples are the same as those for the LTE side in GUL/GUT/GULT triple-
mode base stations with unlimited access bandwidth. For details, see MML Command
Examples (LTE Side).
Using the CME

Step 1 Set parameters on the CME according to the operation sequence described in Table 7-18 and
Table 7-16. For instructions on how to perform the CME single configuration, see CME
Single Configuration Operation Guide.

SingleRAN

SN MO NE
1 a TRMMAP RNC
b ADJMAP RNC
2 a DIFPRI NodeB
----End
7.4.5.5 Limited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations

Step 1 Configure logical ports on the BSC side.
1. Run the ADD IPLOGICPORT command to add an IP logical port on the Abis
interface.
2. Bind a user-plane link to an IP logical port on the Abis interface.
– For a GBTS, you can run the SET BTSIP command to bind an IP logical port to a
GBTS.
– For an eGBTS, you can run the ADD IPPATH command to bind an IP path to an IP
logical port if the peer end is a BSC6900.
– For an eGBTS, you can run the ADD ADJLOGICPORTBIND command to bind
an adjacent node to an IP logical port if the peer end is a BSC6910.
Step 2 Configure a TRM table on the BSC side by referring to section 4.2.2 Transmission Resource
from the UP on the Abis interface.
2. Run the SET BSCABISPRIMAP command to set the mapping between DSCP values
and data from the CP on the Abis interface.
3. Run the ADD ADJMAP command to add the mapping from the Abis interface to the
TRMMAP index.
Step 3 Configure a TRM table on the base station side.
l Run the SET BTSVLAN command to set the mapping between DSCP values and data
from the CP and UP of a GBTS.
l Run the SET DIFPRI command to set the mapping between DSCP values and data from
the CP of an eGBTS.
----End

//Configuring logical ports on the BSC side

SingleRAN
//Adding a logical port on the Abis interface (BSC6900)

ADD IPLOGICPORT: SRN=1, SN=24, BT=GOUc, LPNTYPE=Leaf, LPN=1, CARRYT=ETHER, PN=0,
RSCMNGMODE=SHARE, BWADJ=OFF, CIR=157, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;
//In the preceding script, the unit of bandwidth configured on a logical port is
64 kbit/s. Therefore, the CIR value 157 means that the configured bandwidth is
10048 kbit/s.
//Adding a logical port on the Abis interface (BSC6910)

ADD IPLOGICPORT: SRN=1, SN=24, BT=GOUc, LPNTYPE=Leaf, FLOWCTRLSWITCH=ON, CIR=157,
LPN=1, CARRYT=IPPOOL, IPADDR="172.16.140.140";
10048 kbit/s.
//For a GBTS, binding an IP logical port and a GBTS on the Abis interface
SET BTSIP: IDTYPE=BYID, BTSID=1, BTSCOMTYPE=LOGICIP, BTSIP="16.16.90.201",
BSCIP="172.16.140.140", CFGFLAG=IPLGCPORT, SN=24, LPN=1;
//In the preceding script, the base station is identified by its base station
index.
//For an eGBTS, binding an IP path and an IP logical port on the Abis interface if the peer end
is a BSC6900
ADD IPPATH: ANI=3, PATHID=0, ITFT=ABIS, ISEGBTS=Yes, PATHT=QoS,
IPADDR="172.16.140.140", PEERIPADDR="16.16.90.201", TXBW=10000, RXBW=10000,
CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=1, VLANFLAG=DISABLE, PATHCHK=DISABLED,
AbisLnkBKFLAG=OFF;
//For an eGBTS, binding an adjacent node and an IP logical port on the Abis interface if the
peer end is a BSC6910
ADD ADJLOGICPORTBIND: ANI=3, SRN=1, SN=24, LPN=1;
//Configuring a TRM table on the BSC side

//Setting the mapping between DSCP values and data from the UP on the Abis interface
ADD
TRMMAP:TMI=111,ITFT=ABIS,TRANST=IP,CSVOICEPATH=EF,CSDATAPATH=AF41,PSHPRIDATAPATH=A
F41,PSLPRIDATAPRI=AF31;
//Setting the mapping between DSCP values and data from the CP on the Abis interface
SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=1, TRANSTYPE=IP, OMLDSCP=48, RSLDSCP=48,
EMLDSCP=18, ESLDSCP=48;
//Adding the mapping from the Abis interface to the TRMMAP index
ADD ADJMAP: ANI=3, ITFT=ABIS, TMIGLD=111, FTI=1;
//Configuring a TRM table on the base station side

//Setting the mapping between DSCP values and data from the CP and UP of a GBTS
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=OML, DSCP=48;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=RSL, DSCP=48;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=EML, DSCP=18;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=ESL, DSCP=48;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSVOICE, DSCP=46;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSDATA, DSCP=34;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= PSHIGHPRI, DSCP=34;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= PSLOWPRI, DSCP=26;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= OTHERDATA, DSCP=46;
//Setting the mapping between DSCP values and data from the CP of an eGBTS

SingleRAN

Step 1 Run the SET LR command to configure traffic limiting and shaping if the NodeB side of a
separate-MPT multimode base station provides a co-transmission port.
Step 2 Configure logical ports on the RNC side.
1. Run the ADD IPLOGICPORT command to add an IP logical port on the Iub interface.
2. Bind a user-plane link and an IP logical port on the Iub interface.
– If the transmission resource pool feature is not implemented on the Iub interface,
you can run the ADD IPPATH command to bind an IP path and an IP logical port.
– If the transmission resource pool feature is implemented on the Iub interface, you
can run the ADD ADJLOGICPORTBIND command to bind an adjacent node and
an IP logical port.
TRMMAP index.
CP of a NodeB.
Step 6 If the NodeB side of a separate-MPT multimode base station provides a co-transmission port
and co-transmission is implemented through panel interconnection, the traffic control switch
for a transmission resource group must be disabled on the co-transmission port. Otherwise,
when transmission resources become congested, passing data will preempt bandwidth from
the local data. This deteriorates user experience.
1. Run the ADD RSCGRP command to configure a default transport resource group on the
co-transmission port.
2. Run the SET RSCGRPALG command to disable the traffic control switch of the default
transport resource group you have configured.
----End

//Configuring traffic limiting and shaping on the NodeB side
//Configuring traffic limiting and shaping if the NodeB side of a separate-MPT multimode
base station provides a co-transmission port
SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000,
CBS=40000, EBS=0;
//Configuring logical ports on the RNC side

SingleRAN
//Adding a logical port on the Iub interface

20,032 kbit/s.
//Binding an IP path and an IP logical port if the transmission resource pool feature is not
implemented on the Iub interface
ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS,
CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Binding an adjacent node and an IP logical port if the transmission resource pool feature is

ADD
TMIBRZ=110, FTI=1;



//Turning off the traffic control switch of the default transmission resource group configured
on the co-transmission port if the NodeB side of a separate-MPT multimode base station
provides a co-transmission port and co-transmission is implemented through panel
interconnection

SingleRAN
//Configuring a default transmission resource group on the co-transmission port

ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT, RU=KBPS;
//Disabling the traffic control switch on the default transmission resource group you have
configured
SET RSCGRPALG: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT,
TCSW=DISABLE;

Step 1 Run the SET LR command to configure traffic limiting and shaping if the eNodeB side of a
Step 2 Configure a TRM table on the eNodeB side.

1. Run the SET DIFPRI command to set the mapping between DSCP values and data from
the CP of an eNodeB.
data from the UP of an eNodeB.
Step 3 If the eNodeB side of a separate-MPT multimode base station provides a co-transmission port
1. Run the ADD RSCGRP command to configure a default transport resource group on the
co-transmission port.
transport resource group you have configured.
----End
NOTE
If control-plane EPS optimized transmission is used, NB-IoT services are carried on SCTP links. No
configuration for the user-plane MO UDTPARAGRP is required. NB-IoT does not support the traffic
control switch for a transmission resource group.
If user-plane EPS optimized transmission is used for NB-IoT, NB-IoT does not support the traffic
control switch for a transmission resource group.

//Configuring traffic limiting and shaping on the eNodeB side
//Configuring traffic limiting and shaping if the eNodeB side of a separate-MPT multimode
CBS=40000, EBS=0;
//Setting the mapping between DSCP values and user-plane data of an eNodeB. If the control

SingleRAN

on the co-transmission port if the eNodeB side of a separate-MPT multimode base station
interconnection. NB-IoT does not support the traffic control switch for a transmission
resource group.

//Disabling the traffic control switch on the default transmission resource group you have
configured
TCSW=DISABLE;
Using the CME

Step 1 Set parameters GSM, UMTS, and LTE on the CME according to the operation sequence
described in Table 7-19, Table 7-20, and Table 7-21. For instructions on how to perform the
CME single configuration, see CME Single Configuration Operation Guide.
Table 7-19 MOs on the GSM side
SN MO NE
1 a IPLOGICPORT GBSC
b BTSIP/IPPATH/ADJLOGICPORTBIND GBSC
c TRMMAP GBSC
d BSCABISPRIMAP GBSC
e ADJMAP GBSC
4 a BTSVLAN/DIFPRI GBTS/eGBTS
SN MO NE
1 a LR NodeB

SingleRAN
SN MO NE
2 a IPLOGICPORT RNC
b IPPATH/ADJLOGICPORTBIND RNC
c TRMMAP RNC
d ADJMAP RNC
3 a DIFPRI NodeB
d RSCGRP NodeB
e RSCGRPALG NodeB
SN MO NE
1 a LR eNodeB
b DIFPRI eNodeB
c UDTPARAGRP eNodeB
d RSCGRP eNodeB
e RSCGRPALG eNodeB
----End
7.4.5.6 Limited Access Bandwidth for GU Dual-Mode Base Stations

See "Using MML Commands (GSM Side)" in section 7.4.5.5 Limited Access Bandwidth
for GUL/GUT/GULT Multimode Base Stations.

See "MML Command Examples (GSM Side)" in section 7.4.5.5 Limited Access
Bandwidth for GUL/GUT/GULT Multimode Base Stations.

separate-MPT GU dual-mode base station provides a co-transmission port.

SingleRAN
Step 2 Configure logical ports on the RNC side..

you can run the ADD IPPATH command to bind an IP path and an IP logical port.
can run the ADD ADJLOGICPORTBIND command to bind an adjacent node and
an IP logical port.
TRMMAP index.
CP of a NodeB.
----End

//Configuring traffic limiting and shaping on the NodeB side
CBS=40000, EBS=0;

20,032 kbit/s.

SingleRAN

ADD
TMIBRZ=110, FTI=1;



Set parameters GSM and UMTS on the CME according to the operation sequence described

SN MO NE
1 a LR NodeB
2 a IPLOGICPORT RNC
c TRMMAP RNC
d ADJMAP RNC
3 a DIFPRI NodeB

SingleRAN
7.4.5.7 Limited Access Bandwidth for GL/GT/GLT Multimode Base Stations

See "Using MML Commands (GSM Side)" in section 7.4.5.5 Limited Access Bandwidth

See "MML Command Examples (GSM Side)" in section 7.4.5.5 Limited Access

See "Using MML Commands (LTE Side)" in section 7.4.5.5 Limited Access Bandwidth

See "MML Command Examples (LTE Side)" in section 7.4.5.5 Limited Access

Set parameters GSM and LTE on the CME according to the operation sequence described in
7.4.5.8 Limited Access Bandwidth for UL/UT/ULT Multimode Base Stations

run the ADD IPPATH command to bind an IP path and an IP logical port on the
Iub interface.
– If the transmission resource pool feature is implemented on the Iub interface, run
the ADD ADJLOGICPORTBIND command to bind an adjacent node and an IP
logical port on the Iub interface.
Step 3 Configure a TRM table on the RNC side by referring to 4.2.2 Transmission Resource

SingleRAN
on the UP and CP of the Iub interface.
TRMMAP index.
Step 4 Run the SET DIFPRI command to set the mapping between DSCP values and data on the CP
of a NodeB.
1. Run the ADD ULFLOWCTRLPARA command to add an HSUPA bandwidth adaptive
flow control switch.
2. Run the ADD DLFLOWCTRLPARA command to add an HSDPA flow control switch.
Step 6 If the NodeB side of a separate-MPT multimode base station provides a co-transmission port
when transmission resources become congested, passerby data will preempt bandwidth from
1. Run the ADD RSCGRP command to configure a default transmission resource group on
the co-transmission port.
transmission resource group you have configured.
----End

//Configuring traffic limiting and shaping on the base station side
CBS=40000, EBS=0;

20,032 kbit/s.

SingleRAN
//Setting the mapping between DSCP values and data on the CP and UP of the Iub interface
ADD
TMIBRZ=110, FTI=1;


In the case of a separate-MPT multimode base station


Turn off the traffic control switch of the default transmission resource group configured on
the co-transmission port if the NodeB side of a separate-MPT multimode base station
interconnection.

//Turning off the traffic control switch on the default transmission resource group you have
configured
TCSW=DISABLE;

The command configurations are the same as those for the LTE side in GUL/GUT/GULT
multimode base stations with limited access bandwidth. For details, see Using MML
Commands (LTE Side).

SingleRAN

The command examples are the same as those for the LTE side in GUL/GUT/GULT
multimode base stations with limited access bandwidth. For details, see MML Command
Examples (LTE Side).
Using the CME

Step 1 Set UMTS and LTE parameters on the CME according to the operation sequence described in

SN MO NE
1 a LR NodeB
2 a IPLOGICPORT RNC
c TRMMAP RNC
d ADJMAP RNC
3 a DIFPRI NodeB
d RSCGRP NodeB
e RSCGRPALG NodeB
----End
7.4.5.9 Access Bandwidth Limited for Each Operator in a UL/UT Dual-Mode Base
Station in RAN Sharing Scenarios

Step 1 Configure traffic limiting and shaping on the co-transmission port if the NodeB side of a
1. Run the ADD RSCGRP command to configure a transport resource group.
Step 2 Bind a user-plane link for transmitting local data and the configured transport resource group
on the base station side.
l Link mode:

SingleRAN
a. Run the ADD IPPATH command to add an IP path and bind this IP path and the
configured transmission resource group.
b. Run the ADD NODEBPATH command to bind a NodeB and the added IP path.
l End-point mode:
a. Run the ADD EPGROUP command to add an end point group on the NodeB side.
b. Run the ADD USERPLANEHOST command to add a user-plane host on the NodeB
side.
c. Run the ADD USERPLANEPEER command to add a user-plane peer on the NodeB
side.
d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host and the
added end point group on the NodeB side.
e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer and the
added end point group on the NodeB side.
f. Run the ADD EP2RSCGRP command to bind the added end point group and the
1. Run the ADD IP2RSCGRP command to bind a user-plane link for transmitting passing
data and a transmission resource group on the NodeB side.

2. Run the ADD IPPATH command to bind a user-plane link and an IP logical port on the
Iub interface on the base station controller side.
TRMMAP index.
CP of a NodeB.
Step 7 Turn off the traffic control switch of the default transmission resource group configured on
If the NodeB side of a separate-MPT multimode base station provides a co-transmission port

SingleRAN
Run the SET RSCGRPALG command to turn off the traffic control switch of the default
transmission resource group you have configured.
----End

//If two operators share one multimode base station
//Configuring traffic limiting and shaping on the co-transmission port
//Configuring a transmission resource group
ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=1, RU=KBPS,
TXBW=10000, RXBW=10000, TXCBS=20000, TXEBS=64, OID=0, WEIGHT=100, TXCIR=10000,
RXCIR=10000, TXPIR=10000, RXPIR=10000, TXPBS=20000;
//Link mode
//Binding an IP path and the configured transmission resource group
ADD IPPATH: PATHID=1, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=1,
LOCALIP="16.16.70.201", PEERIP="172.16.90.140", PATHTYPE=ANY;
ADD NODEBPATH: PATHID=1;
ADD NODEBPATH: PATHID=2;
//End-point mode
//Binding an end point group and the configured transport resource group
ADD EPGROUP: EPGROUPID=0;
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="16.16.70.201";
ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="172.16.90.140";
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0;
ADD EP2RSCGRP: ENDPOINTID=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1;
//Binding the passing data and the configured transmission resource group
ADD IP2RSCGRP: MAPIDX=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1,
DSTIP="172.15.90.140", DSTMASK="255.255.255.255";
DSTIP="172.15.80.140", DSTMASK="255.255.255.255";

RSCMNGMODE=EXCLUSIVE, BWADJ=OFF, CIR=157, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;
10048 kbit/s.

SingleRAN

RSCMNGMODE=EXCLUSIVE, BWADJ=OFF, CIR=157, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;
10048 kbit/s.
//Binding an IP path and the logical port you have added on the Iub interface
ADD
TMIBRZ=110, FTI=1;
//Setting the mapping between DSCP values and control-plane data of a NodeB

//Adding an HSDPA flow control parameter in the case of a separate-MPT multimode base
station
//Adding an HSDPA flow control parameter in the case of a co-MPT multimode base station
on the co-transmission port in a separate-MPT multimode base station where co-transmission
is implemented through panel interconnection

SET RSCGRPALG: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1, TCSW=DISABLE;

SingleRAN

Step 1 Configure traffic limiting and shaping on the co-transmission port if the eNodeB side of a
1. Run the ADD RSCGRP command to configure a transport resource group.
2. Bind a user-plane link for transmitting local data and the configured transmission
resource group on the base station side. If the control plane CIoT EPS optimization
function is implemented between the NB-IoT eNodeB and EPC, no user-plane data
configuration is required.
– Link mode
a. Run the ADD IPPATH command to add an IP path and bind this IP path and the
b. Run the ADD ENODEBPATH command to bind an eNodeB and the added IP
path.
– End-point mode
a. Run the ADD EPGROUP command to add an end point group on the eNodeB
side.
b. Run the ADD USERPLANEHOST command to add a user-plane host on the
NodeB side.
c. Run the ADD USERPLANEPEER command to add a user-plane peer on the
eNodeB side.
d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host
and the added end point group on the eNodeB side.
e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer
and the added end point group on the eNodeB side.
f. Run the ADD EP2RSCGRP command to bind the added end point group and the
3. Run the ADD IP2RSCGRP command to bind a user-plane link for transmitting passing
data to a transmission resource group on the NodeB side.
Step 2 Configure a TRM table on the eNodeB side. If the control plane CIoT EPS optimization
function is implemented between the NB-IoT eNodeB and EPC, no user-plane data
configuration is required.
1. Run the SET DIFPRI command to set the mapping between DSCP values and control-
plane data of an eNodeB.
user-plane data of an eNodeB.
Step 3 Turn off the traffic control switch of the default transmission resource group configured on
If the eNodeB side of a separate-MPT multimode base station provides a co-transmission port
when transmission resources become congested, passerby data will preempt bandwidth from
Run the SET RSCGRPALG command to turn off the traffic control switch of the default
transmission resource group you have configured. NB-IoT does not support the traffic control
switch for a transmission resource group.

SingleRAN
----End

//If two operators share one multimode base station
//Configuring traffic limiting and shaping if the eNodeB side of a separate-MPT multimode
//Configuring a transmission resource group
//Link mode
//Binding an IP path to the configured transmission resource group. If the control plane CIoT
EPS optimization function is implemented between the NB-IoT eNodeB and EPC, no user-
plane data configuration is required.
ADD ENODEBPATH: IpPathId=1, AppType=S1, S1InterfaceId=0;
ADD ENODEBPATH: IpPathId=2, AppType=S1, S1InterfaceId=0;
//End-point mode
//Binding an end point group and the configured transmission resource group. If the control
//Binding the passing data and the configured transmission resource group
DSTIP="172.16.90.140", DSTMASK="255.255.255.255";
DSTIP="172.16.80.140", DSTMASK="255.255.255.255";

//Setting the mapping between DSCP values and data from the CP of an eNodeB
//Setting the mapping between DSCP values and data from the UP of an eNodeB

SingleRAN

on the co-transmission port if the eNodeB side of a separate-MPT multimode base station
provides a co-transmission port. NB-IoT does not support the traffic control switch for a
transmission resource group.
Using the CME

Step 1 Set UMTS and LTE parameters on the CME according to the operation sequence described in

SN MO NE
1 a RSCGRP NodeB
b IPPATH NodeB
c NODEBPATH NodeB
d IP2RSCGRP NodeB
2 a IPLOGICPORT RNC
c TRMMAP RNC
d ADJMAP RNC
3 a DIFPRI NodeB
d RSCGRPALG NodeB

SingleRAN

SN MO NE
1 a RSCGRP eNodeB
b IPPATH eNodeB
c ENODEBPATH eNodeB
d IP2RSCGRP eNodeB
2 a DIFPRI eNodeB
b UDTPARAGRP eNodeB
c RSCGRPALG eNodeB
----End
7.4.5.10 GU Dual-Mode Base Stations Using Satellite Transmission

The command examples are the same as those for the GSM side in GUL/GUT/GULT
multimode base stations with limited access bandwidth. For details, see Using MML
Commands (GSM Side).

The command examples are the same as those for the GSM side in GUL/GUT/GULT
multimode base stations with limited access bandwidth. For details, see MML Command
Examples (GSM Side).

GU separate-MPT base station provides a co-transmission port.

2. Bind a user-plane link to an IP logical port on the Iub interface.
you can run the ADD IPPATH command to bind an IP path to an IP logical port.
can run the ADD ADJLOGICPORTBIND command to bind an adjacent node to
an IP logical port.
3. Run the ADD SCTPLNK command to bind an SCPT link to an IP logical port on the
Iub interface.

SingleRAN
TRMMAP index.
CP of a NodeB.
----End

CBS=8000, EBS=0;

3008 kbit/s.
//Binding an IP path to an IP logical port if the transmission resource pool feature is not
CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=1, PATHCHK=DISABLED;
//Binding an adjacent node to an IP logical port if the transmission resource pool feature is
//Binding an SCPT link to an IP logical port on the Iub interface

ADD SCTPLNK: SRN=1, SN=26, SCTPLNKN=12, MODE=SERVER, APP=NBAP,
LOCIP1="172.16.100.140", PEERIP1="16.16.70.201", PEERPN=2010, LOGPORTFLAG=YES,
LOGPORTSN=0, LOGPORTNO=1, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE,
SWITCHBACKFLAG=YES;

ADD

SingleRAN
TMIBRZ=110, FTI=1;



Using the CME

Step 1 Set GSM and UMTS parameters on the CME according to the operation sequence described
SN MO NE
1 a LR NodeB
2 a IPLOGICPORT RNC
b IPPATH/ ADJLOGICPORTBIND RNC
c SCTPLNK RNC
d TRMMAP RNC
e ADJMAP RNC
3 a DIFPRI NodeB
----End

SingleRAN
7.4.6 Activation Observation
7.4.6.1 Unlimited Access Bandwidth for Multimode Base Stations

After the Bandwidth Sharing of Multimode Base Station Co-Transmission feature is activated,
check whether UEs can properly process CS and PS services when transmission resources are
congested and whether the DSCP value of each packet is configured as expected.
l If yes to both, this feature has been activated.
l If no to either, this feature has not been activated.
Perform the following steps to determine whether this feature has been activated:
Step 1 Start IP or MAC tracing on the LMT.

l If the eGBTS provides a co-transmission port, start IP or MAC tracing on the eGBTS
LMT.
For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace.
For MAC tracing: Choose Trace > Common Services > MAC Trace.
l If the NodeB provides a co-transmission port, start IP or MAC tracing on the NodeB
LMT.
l If the eNodeB provides a co-transmission port, start IP or MAC tracing on the eNodeB
LMT.
Step 2 For IP tracing: In the displayed IP Layer Protocol Trace dialog box, specify Local IP
Address and Peer IP Address of the packets to be traced.
For MAC tracing: In the displayed MAC Trace dialog box, specify Local MAC Address and
Peer MAC Address of the packets to be traced.
Step 3 Use the TrafficReview tool to check the TOS (type of service) field in the Layer 3 IP packet
header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the
TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN
priorities are the same as DSCP values or VLAN priorities planned, this feature has been
activated.
----End
7.4.6.2 Limited Access Bandwidth for Multimode Base Stations

If you do not need to check whether the configured service priority has taken effect, perform
the following steps to check whether the feature has been activated:
Step 1 Run the LST RSCGRP command on the base station that provides the co-transmission port
to check whether a transport resource group has been configured for the co-transmission port.
If not, go to method 2.
Step 2 Initiate a UMTS or LTE PS service and set the maximum data rate to a value greater than the
CIR to simulate transmission resource congestion.

SingleRAN
Step 3 Query the value of the VS.RscGroup.TxFlowOverloadTime counter for the co-transmission
port. If the value is greater than 0, this feature has been activated.
----End
If you need to check whether the configured service priority has taken effect, perform the
following steps to check whether the feature has been activated:
l The eGBTS side of a multimode base station provides a co-transmission port.
Step 1 Initiate a UMTS or LTE PS service and set the maximum data rate higher than the CIR value
to simulate transmission resource congestion.
Step 2 Start transport link flux monitoring on the eGBTS LMT. Choose Monitor > Realtime
Performance Monitoring > Transport Link Flux Monitoring.
Step 3 Initiate a GSM or UMTS CS service if the traffic flux approaches the bandwidth available for
the bearer network.
Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant.
Step 5 Initiate a GSM PS service, connect a personal computer (PC) to the multimode base station,
and use the DU Meter on the PC to check whether the GSM PS service is successfully set up
and the data rate is stable.
l If yes to both, this feature has been activated.
l If no to either, this feature has not been activated.
Step 6 Start IP or MAC tracing on the eGBTS LMT.
For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the
displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP
Address of the packets to be traced.
For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC
Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be
traced.
Step 7 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the
VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOS field
indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities are
the same as DSCP values or VLAN priorities planned, this feature has been activated.
----End
l The NodeB side of a multimode base station provides a co-transmission port.
Step 1 Initiate a UMTS PS service and set the maximum data rate higher than the CIR value to
simulate transmission resource congestion.
Step 2 Start transport link flux monitoring on the NodeB LMT. Choose Monitor > Realtime
the bearer network.
Step 5 Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meter
on the PC to check whether the GSM PS service is successfully set up and the data rate is
stable.

SingleRAN
l If yes, this feature has been activated.

l If no, this feature has not been activated.
NOTE
Step 5 is performed only in a separate-MPT GU dual-mode base station or a separate-MPT GUL triple-
mode base station.
Step 6 Start IP or MAC tracing on the NodeB LMT.

For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC
traced.
----End
l The eNodeB side of a multimode base station provides a co-transmission port.
Step 1 Initiate an LTE PS service and set the maximum data rate higher than the CIR value to
simulate transmission resource congestion.
Step 2 Start transport link flux monitoring on the eNodeB LMT. Choose Monitor > Realtime
the bearer network.
Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meter
on the PC to check whether the GSM PS service is successfully set up and the data rate is
stable.
l If yes, this feature has been activated.
l If no, this feature has not been activated.
NOTE
Step 4 is performed only in a separate-MPT GL dual-mode base station or a separate-MPT GUL triple-
mode base station.
Step 5 Start IP or MAC tracing on the eNodeB LMT.

For MAC tracing:Choose Trace > Common Services > MAC Trace. In the displayed MAC
traced.

SingleRAN
----End
7.4.6.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios
If you do not need to check whether the configured service priority has taken effect, perform
the following steps to check whether the feature has been activated:
Step 1 Run the LST RSCGRP command on the base station that provides the co-transmission port
to check whether a transport resource group has been configured for the co-transmission port.
If not, go to method 2.
Step 2 Initiate a UMTS or LTE PS service for an operator and set the maximum data rate to a value
greater than the TXBW value to simulate transmission resource congestion.
Step 3 Query the value of the VS.RscGroup.TxFlowOverloadTime counter for the co-transmission
port. If the value is greater than 0, this feature has been activated.
----End
If you need to check whether the configured service priority has taken effect, perform the
following steps to check whether the feature has been activated:
Step 1 Initiate a UMTS or LTE PS service for operator A and set the maximum data rate higher than
the TXBW value to simulate transmission resource congestion.
Step 2 Start transport link flux monitoring on the LMT.

l If the NodeB side of a separate-MPT multimode base station provides a co-transmission
port, start transport link flux monitoring on the NodeB LMT. Choose Monitor >
Realtime Performance Monitoring > Transport Link Flux Monitoring.
l If the eNodeB side of a separate-MPT multimode base station provides a co-transmission
port, start transport link flux monitoring on the eNodeB LMT. Choose Monitor >
Realtime Performance Monitoring > Transport Link Flux Monitoring.
Step 3 Initiate a UMTS CS service for operator A if the traffic flux approaches the bandwidth
available for the bearer network. Terminate the CS service if the call is successfully set up and
the voice is clear and constant.
Step 4 Perform the first three steps to verify services of other operators.
Step 5 Start IP or MAC tracing on the LMT.

l Start IP or MAC tracing on the NodeB LMT.
For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed
MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the
packets to be traced.
l Start IP or MAC tracing on the eNodeB LMT.

SingleRAN
For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed
MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the
packets to be traced.
----End
7.5 Performance Monitoring

None
7.6 Parameter Optimization

None
7.7 Possible Issues

If bandwidth resources across all modes of a multimode base station are inappropriately
allocated, reallocate the bandwidth resources based on the traffic model.

SingleRAN
Transmission Feature Parameter Description 8 Parameters
8 Parameters
Table 8-1 Parameters

Parame NE MML Feature Feature Description
ter ID Comma ID Name
nd
CIR BTS390 SET LR WRFD- HSDPA Meaning: Indicates the UL committed information
0, LST LR 0106101 Flow rate after rate limitation is configured at a port. The
BTS390 0 Control precision of the UL committed information rate
0 supported by the UMPTa, UMPTb, UMPTe, UMDU
WCDM LOFD-0 Transpo or GTMUc is 64 kbit/s, the precision supported by the
A, 0301101 rt other board is 32 kbit/s. If the configured UL
BTS390 / Overboo committed information rate is not a multiple of the
0 LTE TDLOF king precision, the UL committed information rate is
D-00301 Transpo rounded up. For the GTMUb, the value of CIR ranges
101 rt from 64 to 100000. If this parameter is set to a value
LOFD-0 Differen greater than the maximum allowed value or less than
0301102 tiated the minimum allowed value, the maximum or the
/ Flow minimum allowed value takes effect.
TDLOF Control
GUI Value Range: 32~40000000
D-00301
102 IP QOS Unit: kbit/s
GBFD-1 Actual Value Range: 32~40000000

18605 Default Value: None

SingleRAN

nd
TXBW BTS390 ADD WRFD- Transmi Meaning: Indicates the maximum uplink bandwidth of
0, RSCGR 0213040 ssion a transmission resource group at the MAC layer when
BTS390 P 6 Recours the transmission resource group is carried over IP.
0 MOD e This parameter value is used as the uplink transport
WCDM LOFD-0 Sharing admission bandwidth and TX traffic shaping
RSCGR 03011 /
A, P on bandwidth. The minimum rate supported by the
BTS390 TDLOF Iub/Iur UMPTa, UMPTb, UMPTe, UMDU, GTMUb or
0 LTE DSP D-00301 Interface GTMUc is 64 kbit/s. The LMPT can be configured
RSCGR 1 with a maximum of 360 Mbit/s TX bandwidth. The
P Enhance WMPT, GTMUb or GTMUc can be configured with a
GBFD-1 d
LST 18605 maximum of 300 Mbit/s TX bandwidth. The UMPTa,
RSCGR Transmi UMPTb, UMDU or UTRPc can be configured with a
P ssion maximum of 1 Gbit/s TX bandwidth. The UMPTe or
QoS UCCU can be configured with a maximum of 10
Manage Gbit/s TX bandwidth. The UBBPe, UBBPei, UBBPep
ment or UBBPem can be configured with a maximum of 40
IP QOS Gbit/s TX bandwidth. If the parameter is set to a value
greater than the maximum TX bandwidth supported
by a board, the maximum TX bandwidth supported by
the board takes effect. For a WMPT and a UTRP
(excluding UTRPa), this parameter does not specify
the TX traffic shaping bandwidth of the transmission
resource group that is carried on the PPP link.
Unit: None
Actual Value Range: 32~40000000
Default Value: None
CIR BSC691 ADD GBFD-1 IP QOS Meaning: Bandwidth of the logical port.
0 IPLOG 18605 GUI Value Range: 4~1562
ICPOR
T Unit: 64kbit/s
MOD Actual Value Range: 256~99968

IPLOG Default Value: None
ICPOR
T

SingleRAN

nd
CIR BSC690 ADD MRFD- Bandwi Meaning: Bandwidth of the logical port
0 IPLOG 121115 dth GUI Value Range: 1~1562
ICPOR GBFD-1 sharing
T of Unit: 64kbit/s
18605
MOD MBTS Actual Value Range: 64~64000(FG2a/GOUa),
IPLOG Multi- 256~99968(FG2c/FG2e/FG2d/GOUc/GOUd/
ICPOR mode POUc(IP)/PEUc(IP)/GOUe)
T Co- Default Value: None
Transmi
ssion(G
BTS)
IP QOS
CBS BTS390 SET LR WRFD- IP Meaning: Indicates the Committed Burst Size (CBS)
0, LST LR 050402 Transmi after rate limitation is configured at a port. The
BTS390 ssion minimum rate supported by the UMPTa, UMPTb,
0 LOFD-0 Introduc UMPTe, UMDU or GTMUc is 64 kbit/s. For the
WCDM 0301101 tion on GTMUb, the value of CBS ranges from 63 kbit to 256
A, / Iub kbit. If this parameter is set to a value greater than the
BTS390 TDLOF Interface maximum allowed value or less than the minimum
0 LTE D-00301 allowed value, the maximum or the minimum allowed
101 Transpo value takes effect.
LOFD-0 rt
Overboo GUI Value Range: 32~40000000
0301102
/ king Unit: kbit
TDLOF Transpo Actual Value Range: 32~40000000
D-00301 rt Default Value: None
102 Differen
tiated
GBFD-1 Flow
18605 Control
IP QOS

SingleRAN

nd
EBS BTS390 SET LR WRFD- IP Meaning: Indicates the Excess Burst Size (EBS) after
0, LST LR 050402 Transmi rate limitation is configured at a port.
BTS390 ssion GUI Value Range: 0~40000000
0 LOFD-0 Introduc
WCDM 0301101 tion on Unit: kbit
A, / Iub Actual Value Range: 0~40000000
BTS390 TDLOF Interface
D-00301 Default Value: None
0 LTE
101 Transpo
LOFD-0 rt
0301102 Overboo
/ king
TDLOF Transpo
D-00301 rt
102 Differen
tiated
GBFD-1 Flow
18605 Control
IP QOS
TXCBS BTS390 ADD WRFD- Transmi Meaning: Indicates the TX committed burst size of a
0, RSCGR 0213040 ssion transmission resource group. The LMPT can be
BTS390 P 6 Recours configured with a maximum of 400 Mbit/s TX
0 MOD e committed burst size. The WMPT can be configured
WCDM LOFD-0 Sharing with a maximum of 600 Mbit/s TX committed burst
RSCGR 03011 /
A, P on size. The WMPT, GTMUb or GTMUc can be
BTS390 TDLOF Iub/Iur configured with a maximum of 600 Mbit/s TX
0 LTE LST D-00301 Interface committed burst size. The UMPTa, UMPTb, UMDU
RSCGR 1 or UTRPc can be configured with a maximum of 1
P Enhance Gbit/s TX committed burst size. The UMPTe or
GBFD-1 d
18605 UCCU can be configured with a maximum of 10
Transmi Gbit/s TX committed burst size. The UBBPe,
ssion UBBPei, UBBPep or UBBPem can be configured
QoS with a maximum of 40 Gbit/s TX committed burst
Manage size. The value of TX committed burst size is set to
ment the maximum value of TX committed burst size
IP QOS supported by the board when it bigger than the
maximum one.
Unit: kbit
Default Value: 64

SingleRAN

nd
TXEBS BTS390 ADD WRFD- Transmi Meaning: Indicates the TX excessive burst size of a
0, RSCGR 0213040 ssion transmission resource group. The LMPT can be
BTS390 P 6 Recours configured with a maximum of 450 Mbit/s TX
0 MOD e excessive burst size. The WMPT, GTMUb or GTMUc
WCDM LOFD-0 Sharing can be configured with a maximum of 600 Mbit/s TX
RSCGR 03011 /
A, P on excessive burst size. The UMPTa, UMPTb, UMDU or
BTS390 TDLOF Iub/Iur UTRPc can be configured with a maximum of 1
0 LTE LST D-00301 Interface Gbit/s TX excessive burst size. The UMTPe or UCCU
RSCGR 1 can be configured with a maximum of 10 Gbit/s TX
P Enhance excessive burst size. The UBBPe, UBBPei, UBBPep
GBFD-1 d
18605 or UBBPem can be configured with a maximum of 40
Transmi Gbit/s TX excessive burst size. The value of TX
ssion excessive burst size is set to the maximum value of
QoS TX excessive burst size supported by the board when
Manage it bigger than the maximum one.
ment
IP QOS Unit: kbit
Default Value: 1000000
LPN BSC690 ADD GBFD-1 IP QOS Meaning: Logical port number

0 IPLOG 18605 GUI Value Range: 0~1535
ICPOR
T Unit: None
MOD Actual Value Range: 0~119(FG2a/GOUa); 0~489,

IPLOG 512~767(FG2d/FG2c/FG2e); 0~499, 512~767(GOUd/
ICPOR GOUc/GOUe); 0~988, 1024~1535(POUc(IP));
T 0~127, 1024~1087(PEUc(IP))
RMV Default Value: None

IPLOG
ICPOR
T
LPN BSC691 ADD None None Meaning: Logical port number.

0 IPLOG GUI Value Range: 0~2047
ICPOR
T Unit: None
MOD Actual Value Range: 0~489(FG2d, GOUd, FG2c,

IPLOG FG2e, GOUc, GOUe), 512~767(FG2d, GOUd, FG2c,
ICPOR FG2e, GOUc, GOUe);0~988(POUc(IP)),
T 1024~1535(POUc(IP));0~1499(EXOUa/EXOUb/
EXOUc), 1536~2047(EXOUa/EXOUb/EXOUc)
RMV
IPLOG Default Value: None
ICPOR
T

SingleRAN

nd
SERVI BSC690 SET GBFD-1 Abis Meaning: Service type of the BTS. The QoS
CETYP 0 BTSVL 18601 over IP processing depends on the DSCP, VLAN ID, and
E AN VLAN priority that vary according to the service type.
GUI Value Range: OML(OML), RSL(RSL),
EML(EML), ESL(ESL), CSVOICE(CS Voice),
CSDATA(CS Data), PSHIGHPRI(PS High PRI),
PSLOWPRI(PS Low PRI), OTHERDATA(Other
Data)
Unit: None
Actual Value Range: OML, RSL, EML, ESL,
CSVOICE, CSDATA, PSHIGHPRI, PSLOWPRI,
OTHERDATA
Default Value: None
SERVI BSC691 SET GBFD-1 Abis Meaning: Service type of the BTS. The QoS
CETYP 0 BTSVL 18601 over IP processing depends on the DSCP, VLAN ID, and
E AN VLAN priority that vary according to the service type.
GUI Value Range: OML(OML), RSL(RSL),
EML(EML), ESL(ESL), CSVOICE(CS Voice),
CSDATA(CS Data), PSHIGHPRI(PS High PRI),
PSLOWPRI(PS Low PRI), OTHERDATA(Other
Data)
Unit: None
Actual Value Range: OML, RSL, EML, ESL,
CSVOICE, CSDATA, PSHIGHPRI, PSLOWPRI,
OTHERDATA
Default Value: None
DSCP BSC690 SET MRFD- Bandwi Meaning: DSCP to be contained in the header of an IP
0 BTSVL 121115 dth packet. According to this parameter, the router
AN GBFD-1 sharing provides differentiated services for packet streams.
18605 of The greater the value of this parameter, the higher the
MBTS service level. This parameter is valid only if the
Multi- transport type is set to IP.
mode GUI Value Range: 0~63
Co-
Transmi Unit: None
ssion(G Actual Value Range: 0~63
BTS) Default Value: 0
IP QOS

SingleRAN

nd
DSCP BSC691 SET MRFD- Bandwi Meaning: DSCP to be contained in the header of an IP
0 BTSVL 121115 dth packet. According to this parameter, the router
AN GBFD-1 sharing provides differentiated services for packet streams.
18605 of The greater the value of this parameter, the higher the
MBTS service level. This parameter is valid only if the
Multi- transport type is set to IP.
mode GUI Value Range: 0~63
Co-
Transmi Unit: None
ssion(G Actual Value Range: 0~63
BTS) Default Value: 0
IP QOS
PRIRU BTS390 SET WRFD- IP Meaning: Indicates the rule for prioritizing traffic. If
LE 0, DIFPRI 050402 Transmi this parameter is set to IPPRECEDENCE, the protocol
BTS390 LST ssion stack of the earlier version is adopted and the base
0 LBFD-0 Introduc station converts TOSs to DSCPs and then prioritizes
DIFPRI 0300201
WCDM tion on traffic.
A, / Iub
TDLBF GUI Value Range: IPPRECEDENCE(IP Precedence),
BTS390 Interface DSCP(DSCP)
0 LTE D-00300
201 DiffServ Unit: None
QoS Actual Value Range: IPPRECEDENCE, DSCP
GBFD-1 Support
18605 Default Value: DSCP(DSCP)
IP QOS
SIGPRI BTS390 SET WRFD- IP Meaning: Indicates the priority of signaling. The
0, DIFPRI 050402 Transmi priority has a positive correlation with the value of
BTS390 LST ssion this parameter.
0 LBFD-0 Introduc
DIFPRI 0300201 GUI Value Range: 0~63
WCDM tion on
A, / Iub Unit: None
BTS390 TDLBF Interface Actual Value Range: 0~63
0 LTE D-00300
201 DiffServ Default Value: 48
QoS
GBFD-1 Support
18605
IP QOS

SingleRAN

nd
OMHI BTS390 SET WRFD- IP Meaning: Indicates the priority of the high-level OM
GHPRI 0, DIFPRI 050402 Transmi data. The priority has a positive correlation with the
BTS390 LST ssion value of this parameter.
0 LBFD-0 Introduc
DIFPRI 0300201 GUI Value Range: 0~63
WCDM tion on
A, / Iub Unit: None
BTS390 TDLBF Interface Actual Value Range: 0~63
0 LTE D-00300
201 DiffServ Default Value: 46
QoS
GBFD-1 Support
18605
IP QOS
OMLO BTS390 SET WRFD- IP Meaning: Indicates the priority of the low-level OM
WPRI 0, DIFPRI 050402 Transmi data, such as the data to be uploaded or downloaded.
BTS390 LST ssion The priority has a positive correlation with the value
0 LBFD-0 Introduc of this parameter. The low-level OM data includes the
DIFPRI 0300201
WCDM tion on packets related to File Transfer Protocol (FTP).
A, / Iub
TDLBF GUI Value Range: 0~63
BTS390 Interface
0 LTE D-00300 Unit: None
201 DiffServ Actual Value Range: 0~63
QoS
GBFD-1 Support Default Value: 18
18605
IP QOS
IPCLK BTS390 SET None None Meaning: Indicates the priority of the IP clock. If the
PRI 0, DIFPRI IP clock that follows the PTP is used, this parameter is
BTS390 LST set to the DSCP of the PTP packets. If the IP clock
0 DIFPRI that follows the Huawei proprietary protocol is used,
WCDM this parameter is set to the DSCP of these packets that
A, follow the Huawei proprietary protocol.
BTS390 GUI Value Range: 0~63
0 LTE
Unit: None
Default Value: 46

SingleRAN

nd
OMLD BSC690 SET GBFD-1 Abis Meaning: Differentiated service code of the specified
SCP 0 BSCAB 18601 over IP OML.
ISPRI MRFD- Bandwi GUI Value Range: 0~63
MAP 121115 dth Unit: None
sharing
of Actual Value Range: 0~63
MBTS Default Value: 0
Multi-
mode
Co-
Transmi
ssion(G
BTS)
OMLD BSC691 SET GBFD-1 O&M of Meaning: Differentiated service code of the specified
SCP 0 BSCAB 11202 BTS OML.
ISPRI GUI Value Range: 0~63
MAP
Unit: None
Default Value: 0
RSLDS BSC690 SET GBFD-1 Abis Meaning: Differentiated service code of the specified
CP 0 BSCAB 18601 over IP RSL.
sharing
Multi-
mode
Co-
Transmi
ssion(G
BTS)
RSLDS BSC691 SET GBFD-1 O&M of Meaning: Differentiated service code of the specified
CP 0 BSCAB 11202 BTS RSL.
MAP
Unit: None
Default Value: 0

SingleRAN

nd
EMLDS BSC691 SET GBFD-1 O&M of Meaning: Differentiated service code of the specified
CP 0 BSCAB 11202 BTS EML.
MAP
Unit: None
Default Value: 0
EMLDS BSC690 SET GBFD-1 Abis Meaning: Differentiated service code of the specified
CP 0 BSCAB 18601 over IP EML.
sharing
Multi-
mode
Co-
Transmi
ssion(G
BTS)
ESLDS BSC690 SET GBFD-1 Abis Meaning: Differentiated service code of the specified
CP 0 BSCAB 18601 over IP ESL.
sharing
Multi-
mode
Co-
Transmi
ssion(G
BTS)
ESLDS BSC691 SET GBFD-1 O&M of Meaning: Differentiated service code of the specified
CP 0 BSCAB 11202 BTS ESL.
MAP
Unit: None
Default Value: 0

SingleRAN

nd
CSVOI BSC690 ADD GBFD-1 IP QOS Meaning: CS voice path.

CEPAT 0 TRMM 18605 GUI Value Range: BE, AF11, AF12, AF13, AF21,
H AP AF22, AF23, AF31, AF32, AF33, AF41, AF42,
MOD AF43, EF, CS1, CS2, CS3, CS4, CS5, CS6, CS7
TRMM Unit: None
AP
Actual Value Range: BE, AF11, AF12, AF13, AF21,
AF22, AF23, AF31, AF32, AF33, AF41, AF42,
AF43, EF, CS1, CS2, CS3, CS4, CS5, CS6, CS7
Default Value: None
CSDAT BSC690 ADD GBFD-1 IP QOS Meaning: CS data path.

APATH 0 TRMM 18605 GUI Value Range: BE, AF11, AF12, AF13, AF21,
AP AF22, AF23, AF31, AF32, AF33, AF41, AF42,
TRMM Unit: None
AP
AF22, AF23, AF31, AF32, AF33, AF41, AF42,
Default Value: None
PSHPR BSC690 ADD GBFD-1 IP QOS Meaning: PS high PRI data path.
IDATA 0 TRMM 18605 GUI Value Range: BE, AF11, AF12, AF13, AF21,
PATH AP AF22, AF23, AF31, AF32, AF33, AF41, AF42,
TRMM Unit: None
AP
AF22, AF23, AF31, AF32, AF33, AF41, AF42,
Default Value: None
PSLPRI BSC690 ADD GBFD-1 IP QOS Meaning: PS low PRI data path.
DATAP 0 TRMM 18605 GUI Value Range: BE, AF11, AF12, AF13, AF21,
ATH AP AF22, AF23, AF31, AF32, AF33, AF41, AF42,
TRMM Unit: None
AP
AF22, AF23, AF31, AF32, AF33, AF41, AF42,
Default Value: None

SingleRAN
Transmission Feature Parameter Description 9 Counters
9 Counters
Table 9-1 Counters

Counter ID Counter Counter NE Feature ID Feature Name
Name Description
1542455378 VS.RscGroup. Congestion eGBTS Multi-mode: Bandwidth

TxFlowOverlo duration of MRFD-121115 sharing of
adTime transmit data in MRFD-121125 MBTS Multi-
the resource mode Co-
group MRFD-121135 Transmission
MRFD-121145 (GBTS)
GSM: None Bandwidth
UMTS: None sharing of
MBTS Multi-
LTE: None mode Co-
Transmission
(NodeB)
Bandwidth
sharing of
MBTS Multi-
mode Co-
Transmission
(eNodeB)
Bandwidth
sharing of
MBTS Multi-
mode Co-
Transmission
(LTE TDD)

SingleRAN
Transmission Feature Parameter Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

SingleRAN
Transmission Feature Parameter Description 11 Reference Documents
11 Reference Documents
1. Transmission Resource Management Feature Parameter Description for GBSS and

RAN
2. Transport Resource Management Feature Parameter Description for eRAN
3. Common Transmission Feature Parameter Description for SingleRAN


Bandwidth Sharing of Multimode Base Station Co-Transmission (SRAN12.1 - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bandwidth Sharing of Multimode Base Station Co-Transmission (SRAN12.1 - 01)

Uploaded by

Copyright:

Available Formats

SingleRAN

Bandwidth Sharing of Multimode

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

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

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

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

5.3 MRFD-121135 Bandwidth sharing of MBTS Multi-mode Co-Transmission(eNodeB)..............................................35

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

1 About This Document

1.2 Intended Audience

1.3 Change History

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

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

Change Change Description Parameter Change

Feature Added Bandwidth Sharing of Multimode Base None

Changed the following features from optional to None

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

Change Change Description Parameter Change

Editorial None None

1.4 Differences Between Base Station Types

MRFD-121115 Bandwidth sharing of MBTS Multi- Yes No No

MRFD-121125 Bandwidth sharing of MBTS Multi- Yes Yes Yes

MRFD-121135 Bandwidth sharing of MBTS Multi- Yes Yes Yes

MRFD-121145 Bandwidth sharing of MBTS Multi- Yes No Yes

MRFD-121155 Bandwidth sharing of MBTS Multi- Yes Yes No

Function Implementation in Macro, Micro, and LampSite Base Stations

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

1.5 Functional Differences Between NB-IoT and FDD

MRFD- Bandwidt MRFD- Bandwid NB-IoT supports mapping between traffic

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

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

2.3 Application Networking

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

l Differentiation: Transmission differentiation is used when transmission bandwidth is limited.

This feature adopts four recommended transmission resource management strategies:

3.2 Transmission Priorities

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

ADD TRMMAP Used to set the mapping between DSCP values

MOD Used to set the mapping between DSCP values

l For separate-MPT multimode base stations in co-transmission scenarios, run the

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

PQ is short for priority queue.

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

3.3 Traffic Limiting and Shaping

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

Figure 3-1 Working principles of traffic limiting and shaping

Base-station-level traffic limiting and shaping

Logical-port-level traffic limiting and shaping

l Separate-MPT multimode base station

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

3.4 Load Control

NB-IoT services do not support load control.

3.5 Flow Control

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

GSM GBTS/eGBTS and No None

UMTS NodeB and RNC Yes The flow control

LTE eNodeB Yes The flow control

Table 3-5 Classification of the NodeB dynamic flow control algorithm

NodeB uplink bandwidth l Congestion control Transmission Resource

NodeB HSDPA adaptive Flow control switch:

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