Bandwidth Sharing of Multimode Base Station Co-Transmission (SRAN9.0 - 02)

SingleRAN
Bandwidth Sharing of Multimode

Base Station Co-Transmission
Feature Parameter Description
Issue 02
Date 2014-12-30
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2014-12-30) 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...............................................................................................................................................................2
1.4 Differences Between Base Station Types.......................................................................................................................3
2 Overview.........................................................................................................................................4
2.1 Introduction....................................................................................................................................................................4
2.2 Benefits...........................................................................................................................................................................4
2.3 Application Networking.................................................................................................................................................5
3 Technical Description...................................................................................................................7
3.1 Introduction....................................................................................................................................................................7
3.2 Transmission Priorities...................................................................................................................................................8
3.3 Traffic Limiting and Shaping.......................................................................................................................................11
3.4 Load Control.................................................................................................................................................................12
3.5 Flow Control.................................................................................................................................................................13
4 Application Scenarios.................................................................................................................16
4.1 Unlimited Access Bandwidth for Multimode Base Stations........................................................................................16
4.1.1 Introduction...............................................................................................................................................................16
4.1.2 Transmission Resource Management Strategies.......................................................................................................17
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.................................................................30
4.3.1 Introduction...............................................................................................................................................................30
5 Related Features...........................................................................................................................36
5.1 Prerequisite Features.....................................................................................................................................................36
5.2 Mutually Exclusive Features........................................................................................................................................36
5.3 Impacted Features.........................................................................................................................................................36
6 Network Impact...........................................................................................................................37
Issue 02 (2014-12-30) Huawei Proprietary and Confidential ii

SingleRAN
Transmission Feature Parameter Description Contents
6.1 System Capacity...........................................................................................................................................................37

6.2 Network Performance...................................................................................................................................................37
7 Engineering Guidelines.............................................................................................................38
7.1 When to Use Bandwidth Sharing of Multimode Base Station Co-Transmission.........................................................38
7.2 Required Information...................................................................................................................................................38
7.3 Planning........................................................................................................................................................................38
7.4 Deployment..................................................................................................................................................................39
7.4.1 Requirements.............................................................................................................................................................39
7.4.2 Data Preparation........................................................................................................................................................40
7.4.3 Precautions.................................................................................................................................................................50
7.4.4 Hardware Adjustment................................................................................................................................................50
7.4.5 Initial Configuration (Unlimited Access Bandwidth for GU Dual-Mode Base Stations).........................................50
7.4.6 Initial Configuration (Unlimited Access Bandwidth for GL/GT Dual-Mode Base Stations)...................................53
7.4.7 Initial Configuration (Unlimited Access Bandwidth for UL/UT/ULT Multimode Base Stations)...........................55
7.4.8 Initial Configuration (Unlimited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)..................57
7.4.9 Initial Configuration (Limited Access Bandwidth for GU Dual-Mode Base Stations).............................................60
7.4.10 Initial Configuration (Limited Access Bandwidth for GL/GT/GLT Multimode Base Stations)............................65
7.4.11 Initial Configuration (Limited Access Bandwidth for UL/UT/ULT Multimode Base Stations)............................68
7.4.12 Initial Configuration (Limited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)....................72
7.4.13 Initial Configuration (Limited Access Bandwidth for Each Operator in a UL/UT Dual-Mode Base Station in RAN
Sharing Scenarios)..............................................................................................................................................................78
7.4.14 Activation Observation (Unlimited Access Bandwidth for Multimode Base Stations)..........................................86
7.4.15 Activation Observation (Limited Access Bandwidth for Multimode Base Stations)..............................................87
7.4.16 Activation Observation (Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios)...................91
7.5 Performance Monitoring...............................................................................................................................................93
7.6 Parameter Optimization................................................................................................................................................93
7.7 Troubleshooting............................................................................................................................................................93
8 Parameters.....................................................................................................................................94
9 Counters......................................................................................................................................119
10 Glossary.....................................................................................................................................120
11 Reference Documents.............................................................................................................121
Issue 02 (2014-12-30) 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-211505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(GBTS)

l MRFD-221505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NodeB)
l MRFD-231505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(eNodeB)
l MRFD-241505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(LTE TDD)
In this document, the following naming conventions apply for LTE terms.
Includes FDD and TDD Includes FDD Only Includes TDD Only
LTE LTE FDD LTE TDD
eNodeB LTE FDD eNodeB LTE TDD eNodeB
eRAN LTE FDD eRAN LTE TDD eRAN
In addition, the "L" and "T" in RAT acronyms refer to LTE FDD and LTE TDD, respectively.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
Issue 02 (2014-12-30) Huawei Proprietary and Confidential 1

SingleRAN
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, which are defined as follows:
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
SRAN9.0 02 (2014-12-30)
This issue includes the following changes.
Change Type Change Description Parameter

Change
Feature change None. None.
Editorial Optimized the document description of chapter 4 None.

change Application Scenarios.
SRAN9.0 01 (2014-04-30)
This issue does not include any changes.
SRAN9.0 Draft A (2014-01-20)

Compared with 01 (2013-04-28) of SRAN8.0, Draft A (2014-01-20) of SRAN9.0 includes the
following changes.
Change Type Change Description Parameter

Change
Feature change l Added the descriptions of the LTE(TDD) mode None.

support for Bandwidth Sharing of Multimode Base
Station Co-Transmission feature.
l Modified the flow control policy for a separate-
MPT multimode base station where co-transmission
is implemented through backplane interconnection.
Editorial Added activation observation methods. For details, see None.

change 7.4.15 Activation Observation (Limited Access
Bandwidth for Multimode Base Stations) and 7.4.16
Activation Observation (Limited Access Bandwidth
for Each Operator in RAN Sharing Scenarios).

SingleRAN
1.4 Differences Between Base Station Types

LampSite base stations are distributed base stations that provide indoor coverage. In this
document, LampSite base stations work in UMTS, LTE, or UMTS+LTE mode, but not in GSM
mode.
In this document, micro base stations are all integrated entities. They work in UMTS or LTE
FDD mode, but not in GSM or LTE TDD mode. Descriptions of boards, cabinets, subracks,
slots, and RRUs are not relevant to micro integrated base stations. The following base stations
are single-mode ones, without co-MPT or separate-MPT multimode applications:
l BTS3202E
l BTS3203E
l BTS3803E
l BTS3902E
Feature Support by Macro, Micro, and LampSite Base Stations

Feature ID Feature Name Support Supporte Supporte
ed by d by d by
Macro Micro LampSite
Base Base Base
Stations Stations Stations
MRFD-211505 Bandwidth sharing of MBTS Yes No No

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

(NodeB)
MRFD-231505 Bandwidth sharing of MBTS Yes No Yes

(eNodeB)
MRFD-241505 Bandwidth sharing of MBTS Yes No No

(LTE TDD)
Function Implementation in Macro, Micro, and LampSite Base Stations

None.

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
The Bandwidth Sharing of Multimode Base Station Co-Transmission feature provides the
following benefits:
l Saved transmission resources
GSM, UMTS, and LTE services have different peak hours. Therefore, the transmission resources
of one mode (for example, GSM) can be multiplexed by the other modes (for example, UMTS
and LTE) if GSM is not experiencing a traffic peak. For a multimode base station in co-
transmission scenarios, transmission resources can be shared by GSM, UMTS, and LTE. This
promotes resource utilization and ultimately uses fewer transmission resources.
As GSM services continuously shrink, the released GSM bandwidth is gradually occupied by
UMTS and LTE services, which promotes transmission resource utilization.
l Guaranteed service quality and user experience

SingleRAN
When uplink or downlink transmission resources are congested, this feature guarantees the
quality of service (QoS) of high-priority GSM, UMTS, and LTE services without compromising
user experience.
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).
NOTE
MME: mobility management entity

S-GW: serving gateway
MPT: main processing and transmission unit
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 triple-mode 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.

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.
l GBTS or eGBTS refers to the GSM side of a multimode base station. NodeB refers to the UMTS side
of a multimode base station. eNodeB refers to the LTE side of a multimode base station. LTE can be
LTE FDD, LTE TDD, or LTE FDD&LTE TDD.
l Multimode base stations are classified into co-MPT and separate-MPT multimode base stations, both
introduced in SRAN8.0. In a co-MPT multimode base station, different modes share one main control
board and one O&M channel. In a separate-MPT multimode base station, each mode has its own main
control board and its own O&M channel. 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.
l 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 multimode base station in co-transmission scenarios, the data of the mode that provides a
co-transmission port is called local data. The data of other modes that rely on the co-transmission
port for data transmission is called passing data.
l 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.
l 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.
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.
Table 3-1 lists the definitions of all kinds of base stations.
Table 3-1 Definitions of base stations
Base Station Name Definition
GBTS GBTS refers to a base station deployed with GTMU.
eGBTS eGBTS refers to a base station deployed with UMPT_G.

SingleRAN
Base Station Name Definition
NodeB NodeB refers to a base station deployed with WMPT or

UMPT_U.
eNodeB eNodeB refers to a base station deployed with LMPT, UMPT_L,

or UMPT_T.
Co-MPT Multimode Co-MPT multimode base station refers to a base station deployed
Base Station with UMPT_GU, UMPT_GL, UMPT_GT, UMPT_UL,
UMPT_UT, UMPT_LT, UMPT_GUL, UMPT_GUT,
UMPT_ULT, UMPT_GLT, or UMPT_GULT, and it
functionally corresponds to any combination of eGBTS, NodeB,
and eNodeB. For example, Co-MPT multimode base station
deployed with UMPT_GU functionally corresponds to the
combination of eGBTS and NodeB.
Separate-MPT Separate-MPT multimode base station refers to a base station on

Multimode Base Station which different modes use different main control boards. For
example, base stations deployed with GTMU and WMPT are
called separate-MPT GSM/UMTS dual-mode base station.
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 caused 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.
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 RAN, and Transport Resource Management Feature Parameter Description for eRAN,
respectively.
3.2 Transmission Priorities

The Bandwidth Sharing of Multimode Base Station Co-Transmission feature provides
differentiated services (DiffServ) for 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 base station controller sets the DSCP value for each IP packet based
on the QoS requirements of each service type. From the DSCP value, transmission devices
identify the traffic class and related QoS requirements of the service and perform per-hop

SingleRAN
behaviors (PHBs) accordingly. PHBs include transmission resource allocation, queue

scheduling, and packet discarding.
Table 3-2 describes how to use MML commands to configure the mapping between traffic
classes and DSCP values for each type of base station.
Table 3-2 Configuring 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

NodeB between DSCP values and
data from the O&M plane
and CP on the eGBTS or
NodeB side.
ADD TRMMAP and SET Used to set the mapping

PHBMAP between DSCP values and
data from the UP on the BSC
or RNC side.
eNodeB SET DIFPRI Used to set the mapping

data from the O&M plane
and CP plane on the eNodeB
side.
MOD UDTPARAGRP Used to set the mapping

data from the UP on the
eNodeB side.
Pay attention to the following when mapping traffic classes to 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.
VLAN Priority
The VLAN tag defines an IP packet's VLAN priority. Based on the VLAN priority, Layer 2
devices can implement DiffServ.
VLAN priorities of packets with different traffic classes can be determined by DSCP values.
Table 3-3 provides the default mapping between DSCP values and VLAN priorities on the
multimode base station side.
Table 3-3 Default mapping between DSCP values and VLAN priorities
DSCP Value 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.
WRR is short for weighted round robin. WFQ4 through WFQ7 have the same weight.
Queue priorities are determined by the mapping between DSCP values and queue priorities, as
listed in Table 3-4 and Table 3-5. You are not advised to modify the default mapping between
DSCP values and queue priorities.

SingleRAN
Table 3-4 Default mapping between DSCP values and queue priorities for the GBTS
DSCP Value 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-5 Default mapping between DSCP values and queue priorities for the eGBTS, NodeB,
and eNodeB in a co-MPT multimode base station
DSCP Value 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, transmission devices may be incapable of receiving
excess packets that arrive at the co-transmission port in a multimode base station. To prevent
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 prevent packet discarding and congestion caused by
traffic bursts. These functions use the Generic Traffic Shaping (GTS) technology, which shapes
irregular data flows to balance the bandwidth between upstream and downstream nodes.
The traffic limiting and shaping functions apply only to non-real-time services.

SingleRAN
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 bottleneck bandwidth planned for the 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.
l Base-station-level traffic limiting and shaping

– Separate-MPT multimode base station
If the eGBTS, NodeB, or eNodeB provides a co-transmission port, you can run the SET
LR command and specify the CIR parameter to set the bandwidth after rate limitation
for a base station.
– Co-MPT multimode base station
You can run the SET LR command and specify the CIR parameter to set the bandwidth
after rate limitation for a base station.
l Logical-port-level traffic limiting and shaping
– Separate-MPT multimode base station
If the eGBTS, NodeB, or eNodeB provides a co-transmission port, you can run the
ADD RSCGRP command and specify the TXBW parameter to set the bandwidth after
rate limitation for a logical port.
– Co-MPT multimode base station
You can run the ADD RSCGRP command and specify the TXBW parameter to set the
bandwidth after rate limitation for a logical port.
l Multimode base station controller
You can run the ADD IPLOGICPORT command and specify the CIR
(BSC6900,BSC6910) parameter to set the bandwidth after rate limitation for a logical port.
NOTE
To implement rate limitation for a logical port,

l You are advised to set bandwidth after rate limitation using the SET LR command and set logical
port bandwidth using the ADD RSCGRP command.
l 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 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 rate limitation and data
shaping.
l Each mode uses different non-default transport resource groups to implement rate limitation and
data shaping.
3.4 Load Control

Load control includes admission control, load reshuffling (LDR), and overload control (OLC).
LTE does not support LDR.

SingleRAN
l Admission control: ensures quality of the admitted services by preventing excessive

admissions.
l LDR: promotes admission success rates and system capacity by relieving transmission load
and preventing transmission resource congestion.
l 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 load is 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 and RAN, and Transport Resource
Management Feature Parameter Description for eRAN, respectively.
3.5 Flow Control

When transmission bandwidth dynamically changes, the bandwidth available for the bottleneck
nodes may be smaller than the bandwidth after rate limitation on the shared port. If the base
station keeps transmitting data at the bandwidth after rate limitation, the transport network may
be congested. To prevent transport network congestion, the flow control algorithm is introduced.
This algorithm first estimates the bottleneck bandwidth based on the transmission quality test
and then dynamically adjusts the transmit bandwidth to ensure that the transmit bandwidth does
not exceed the bottleneck bandwidth.
Table 3-6 lists whether GSM, UMTS, and LTE support the flow control algorithm.
Table 3-6 Whether GSM, UMTS, and LTE support the flow control algorithm
Mode NE Support 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, and it includes the NodeB
uplink bandwidth adaptive adjustment algorithm and the NodeB HSDPA adaptive flow control

SingleRAN
algorithm. The NodeB uplink bandwidth adaptive adjustment algorithm is controlled by the
HSUPA congest control switch (TNLCONGCTRLSWITCH) and the traffic control switch
(TCSW) on the NodeB. The NodeB HSDPA adaptive flow control algorithm is controlled by
SWITCH on the NodeB.For working principles and implementation of the NodeB uplink
bandwidth adaptive adjustment algorithm and NodeB HSDPA adaptive flow control algorithm,
see Transmission Resource Management Feature Parameter Description for RAN.
For a co-MPT UL or GUL multimode base station in co-transmission scenarios, if UMTS

HSDPA services are undergoing flow control, the released UMTS bandwidth may be occupied
by LTE services. Consequently, bandwidth available for UMTS services may decrease
considerably. To protect UMTS bandwidth, enable the fair flow control switch
(FAIRSWITCH) on the NodeB side. The fair switch ensures that at least 30% of the actual
receive bandwidth is retained for UMTS HSDPA services. For example, if the total bandwidth
for UMTS HSDPA services decreases to 30% of the actual receive bandwidth, data rates for
UMTS HSDPA services will not be reduced.
The fair flow control switch can be configured either on a physical port of a co-MPT UL dual-
mode base station or on the corresponding loopback interface (also called logical port) of the
physical port, with the physical port preferred. When configured on the loopback interface, the
fair flow control switch 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-1.
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-2.
Figure 3-1 One loopback interface corresponding to one physical port; UMTS and LTE
services carried on the same physical port

SingleRAN
Figure 3-2 One loopback interface corresponding to multiple physical ports; UMTS and LTE
services carried on different physical ports
NOTE
The loopback interface is a virtual interface that resides on a router. It is not connected to any other device.
It is recommended that you configure the FAIRSWITCH on the loopback interface in scenario 2 because
this scenario is not a multimode base station co-transmission networking scenario.
For details about the flow control algorithm, see Transmission Resource Management Feature
Parameter Description for WCDMA RAN.

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

Stations
4.1.1 Introduction
Unlimited access bandwidth 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 the three multimode base stations is the
maximum bandwidth 100 Mbit/s and bandwidth for intermediate transmission devices is also
the maximum bandwidth 100 Mbit/s.
Figure 4-1 Unlimited access bandwidth for multimode base stations

SingleRAN
4.1.2 Transmission Resource Management Strategies

This section describes how to configure transmission resource management strategies in this
scenario. These strategies also apply to scenarios in which multiple operators share one
multimode base station and the access bandwidth of one operator is shared by other operators.
(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
chapter 3 Technical Description.
Table 4-1 Recommended transmission priorities for different traffic classes if access bandwidth
is unlimited for multimode base stations
NE Traffic Class PHB DSCP Value VLAN

Priority
GBTS ESL/OML/RSL CS6 48 6
CS Voice EF 46 5
CS Data/PS AF41 34 4
High PRI
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
High PRI
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
NodeB Iub Signal CS6 48 6

SingleRAN

Priority
CCH&SRB&A EF 46 5
MR
Conversational AF41 34 4
&Streaming
R99 AF21 18 2
interactive&bac
kground
HSxPA AF11 10 1
interactive&bac
kground
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, transmission devices support queue scheduling. Layer 3 and Layer 2 transmission
devices support eight queues. However, if 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 transmission
devices support six queues, packets whose DSCP values are 48 and 46 can be put into one queue.

SingleRAN
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 Queues DSCP Value Combining VLAN Priority Combing

Strategy Strategy
6 DSCP values for the six VLAN priorities for the six
queues are (48+46), 34, 26, queues are (6+5), 4, 3, 2, 1,
18, 10, and 0, respectively. and 0, respectively.
5 DSCP values for the five VLAN priorities for the five
queues are (48+46), (34+26), queues are (6+5), (4+3), 2, 1,
4 DSCP values for the four VLAN priorities for the four
queues are (48+46), (34+26 queues are (6+5), (4+3+2), 1,
+18), 10, and 0, respectively. and 0, respectively.
3 DSCP values for the three VLAN priorities for the three
queues are (48+46), (34+26 queues are (6+5), (4+3+2+1),
+18+10), and 0, respectively. and 0, respectively.
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 access bandwidth is unlimited for multimode base stations
Base Station Type Setting of the Setting of the Setting of the

HSUPA HSDPA Adaptive HSDPA Fair Flow
Congestion Flow Control Control Switch
Control Switch Algorithm Switch
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

SingleRAN

Separate-MPT UL OFF(Off) l BW_SHAPING N/A

dual-mode base _ONOFF_TOG
station GLE
(BW_SHAPING
_ONOFF_TOG
GLE) (default
value): if the
bearer network
supports three or
more queues
l NO_BW_SHAP
ING
(NO_BW_SHA
PING): if the
bearer network
supports only two
queues
Co-MPT UL dual- OFF(Off) l BW_SHAPING ENABLE(Enable)

mode base station _ONOFF_TOG
GLE
(BW_SHAPING
_ONOFF_TOG
GLE) (default
value): if the
bearer network
supports three or
more queues
l NO_BW_SHAP
ING
(NO_BW_SHA
PING): if the
bearer network
supports only two
queues

SingleRAN

Separate-MPT GUL OFF(Off) l BW_SHAPING N/A

triple-mode base _ONOFF_TOG
station GLE
(BW_SHAPING
_ONOFF_TOG
GLE) (default
value): if the
bearer network
supports three or
more queues
l NO_BW_SHAP
ING
(NO_BW_SHA
PING): if the
bearer network
supports only two
queues
Co-MPT GUL triple- OFF(Off) l BW_SHAPING ENABLE(Enable)

mode base station _ONOFF_TOG
GLE
(BW_SHAPING
_ONOFF_TOG
GLE) (default
value): if the
bearer network
supports three or
more queues
l NO_BW_SHAP
ING
(NO_BW_SHA
PING): if the
bearer network
supports only two
queues
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:

SingleRAN
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

scenario. These strategies also apply to scenarios in which multiple operators share one
multimode base station, the access bandwidth of one operator is shared by other operators, and
the access bandwidth for multimode base stations is limited.
Configuring Traffic Limiting and Shaping on the Base Station Controller Side
Set the bandwidth after rate limitation to the access bandwidth planned by the operator for a
Configuring Traffic Limiting and Shaping on the Co-Transmission Port of the Base
Station Side
Set the bandwidth after rate limitation to the access bandwidth planned by the operator for a

SingleRAN
Configuring the Mapping Between Traffic Classes and DSCP Values

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

Priority
GBTS ESL/OML/RSL CS6 48 6
CS Voice EF 46 5
High PRI
IP Clock CS6 46 6
EML AF21 18 2
eGBTS SCTP CS6 48 6
CS Voice EF 46 5
High PRI
OM High EF 46 5
OM Low AF21 18 2
IP Clock CS6 46 6
CCH&SRB&A EF 46 5
MR
&Streaming
R99 AF21 18 2
interactive&bac
kground
HSxPA AF11 10 1
interactive&bac
kground
OM High EF 46 5
OM Low AF21 18 2

SingleRAN

Priority
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 multimode base stations

Strategy Strategy
queues are (48+46), (34+26), queues are (6+5), 4, 3, 2, (1
18, 10, and 0, respectively. +0), respectively.

SingleRAN

Strategy Strategy

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 Traffic HSUPA HSDPA HSDPA Fair
Control Congestion Adaptive Flow Control
Switch Control Flow Control Switch
Switch Algorithm
Switch
Separate-MPT ENABLE ON(On) BW_SHAPING N/A

GU dual-mode (Enable) (default value) _ONOFF_TOG
base station (default value) GLE
(BW_SHAPIN
Co-MPT GU G_ONOFF_TO
dual-mode base GGLE) (default
station value)
Separate-MPT ENABLE N/A N/A N/A

GL dual-mode (Enable)
base station (default value)
Co-MPT GL
dual-mode base
station

SingleRAN
Switch Algorithm
Switch
Separate-MPT l ENABLE OFF(Off) l BW_SHAP N/A

UL dual-mode (Enable) ING_ONO
base station (default FF_TOGG
value): if co- LE
transmission (BW_SHAP
is ING_ONO
implemente FF_TOGG
d through LE) (default
backplane value): if the
interconnect bearer
ion network
l DISABLE supports
(Disable):if three or
co- more queues
transmission l NO_BW_S
is HAPING
implemente (NO_BW_S
d through HAPING):
panel if the bearer
interconnect network
ion supports
only two
queues

SingleRAN
Switch Algorithm
Switch
Co-MPT UL ENABLE OFF(Off) l BW_SHAP ENABLE

dual-mode base (Enable) ING_ONO (Enable)
station (default value) FF_TOGG
LE
(BW_SHAP
ING_ONO
FF_TOGG
LE) (default
value): if the
bearer
network
supports
three or
more queues
l NO_BW_S
HAPING
(NO_BW_S
HAPING):
if the bearer
network
supports
only two
queues

SingleRAN
Switch Algorithm
Switch
Separate-MPT l ENABLE OFF(Off) l BW_SHAP N/A

GUL triple- (Enable) ING_ONO
mode base (default FF_TOGG
station value): if co- LE
transmission (BW_SHAP
is ING_ONO
implemente FF_TOGG
interconnect bearer
ion network
l DISABLE supports
co- more queues
transmission l NO_BW_S
is HAPING
implemente (NO_BW_S
d through HAPING):
panel if the bearer
ion supports
only two
queues

SingleRAN
Switch Algorithm
Switch
Co-MPT GUL ENABLE OFF(Off) l BW_SHAP ENABLE

triple-mode (Enable) ING_ONO (Enable)
base station (default value) FF_TOGG
LE
(BW_SHAP
ING_ONO
FF_TOGG
LE) (default
value): if the
bearer
network
supports
three or
more queues
l NO_BW_S
HAPING
(NO_BW_S
HAPING):
if the bearer
network
supports
only two
queues
NOTE
l TCSW is set to ENABLE by default. If you want to set TCSW to DISABLE, first run the ADD
RSCGRP command to add a default transmission resource group to the co-transmission port with
RSCGRPID set to DEFAULTPORT. Then set TCSW to DISABLE for the default transmission
resource group you have added.
l If a separate-MPT multimode base station uses backplane interconnection to implement co-
transmission, the tunnel type (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 for SingleRAN.
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.

SingleRAN
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.
Figure 4-3 Limited access bandwidth for each operator in RAN sharing scenarios

scenario.
Configuring Traffic Limiting and Shaping on the Base Station Controller Side
Configure a logical port for each operator on the base station controller side. Set the bandwidth
after rate limitation on the logical port to the access bandwidth planned by the operator.

SingleRAN
Configuring Traffic Limiting and Shaping on the Co-Transmission Port of the Base
Station Side
Configure a logical port for each operator on the co-transmission port of the base station side.
Set the bandwidth after rate limitation on the logical port to the access bandwidth planned by
the operator.
Configuring the Mapping Between Traffic Classes and DSCP Values

Table 4-7 lists recommended transmission priorities for different traffic classes.
is limited for each operator in RAN sharing scenarios

Priority
CCH&SRB&A EF 46 5
MR
&Streaming
R99 AF21 18 2
interactive&bac
kground
HSxPA AF11 10 1
interactive&bac
kground
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

SingleRAN

Priority
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

Strategy Strategy
queues are (48+46), (34+26), queues are (6+5), 4, 3, 2, (1
18, 10, and 0, respectively. +0), respectively.


SingleRAN
flow control switch if access bandwidth is limited for each operator in RAN sharing scenarios
Switch Algorithm
Switch
Separate-MPT l ENABLE OFF(Off): l BW_SHAP N/A

UL dual-mode (Enable) ING_ONO
base station (default FF_TOGG
value): if co- LE
transmissio (BW_SHAP
n is ING_ONO
implemente FF_TOGG
interconnect bearer
ion network
l DISABLE supports
co- more queues
transmissio l NO_BW_S
n is HAPING
implemente (NO_BW_S
d through HAPING):
panel if the bearer
ion supports
only two
queues

SingleRAN
Switch Algorithm
Switch
Co-MPT UL ENABLE OFF(Off) l BW_SHAP ENABLE

dual-mode base (Enable) ING_ONO (Enable)
station (default value) FF_TOGG
LE
(BW_SHAP
ING_ONO
FF_TOGG
LE) (default
value): if the
bearer
network
supports
three or
more queues
l NO_BW_S
HAPING
(NO_BW_S
HAPING):
if the bearer
network
supports
only two
queues
NOTE
l TCSW is set to ENABLE by default. If you want to set TCSW to DISABLE, first run the ADD
RSCGRP command to add a default transmission resource group to the co-transmission port with
RSCGRPID set to DEFAULTPORT. Then set TCSW to DISABLE for the default transmission
resource group you have added.
l If a separate-MPT multimode base station uses backplane interconnection to implement co-
transmission, the tunnel type (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 for SingleRAN.
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 how to configure the load control algorithm for UMTS and LTE, see

SingleRAN
Transmission Resource Management Feature Parameter Description for GBSS and RAN, and
Transport Resource Management Feature Parameter Description for eRAN, respectively.

SingleRAN
Transmission Feature Parameter Description 5 Related Features
5 Related Features
5.1 Prerequisite Features

l MRFD-211501 IP-Based Multi-mode Co-Transmission on BS side(GBTS)
l MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side(NodeB)
l MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)
l MRFD-241501 IP-Based Multi-mode Co-Transmission on BS side(LTE TDD)
5.2 Mutually Exclusive Features

None
5.3 Impacted Features

None

SingleRAN
Transmission Feature Parameter Description 6 Network Impact
6 Network Impact
6.1 System Capacity

No impact.
6.2 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 Bandwidth Sharing of Multimode Base

Station Co-Transmission
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

SingleRAN
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 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
l 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:
– Layer 3 devices support DSCP-priority-based QoS management.
– Layer 2 devices support VLAN-priority-based QoS management.
– Transmission devices support the PQ+WRR queue scheduling function, and at least two
PQ queues are supported. (WRR stands for weighted round robin.)
l Other features
– If the GBTS provides a co-transmission port, the MRFD-211501 IP-Based Multi-mode
Co-Transmission on BS side(GBTS) feature must be activated on the BTS.
– If the NodeB provides a co-transmission port, the MRFD-221501 IP-Based Multi-mode
Co-Transmission on BS side(NodeB) feature must be activated on the NodeB.
– If the eNodeB provides a co-transmission port, the MRFD-231501 IP-Based Multi-
mode Co-Transmission on BS side(eNodeB) feature must be activated on the eNodeB.

SingleRAN
– If the LTE TDD eNodeB provides a co-transmission port, the MRFD-241501

Bandwidth sharing of MBTS Multi-mode Co-Transmission(LTE TDD) feature must
be activated on the LTE TDD eNodeB.
l License
The license for the Bandwidth Sharing of Multimode Base Station Co-Transmission feature
has been activated.
Table 7-1 License control items
Featu Feature Name License Control License NE Sales

re ID Item ID Control Item Unit
MRFD Bandwidth LGMIBSMCT Bandwidth BSC per BTS

-21150 sharing of MBTS sharing of
5 Multi-mode Co- MBTS Multi-
Transmission mode Co-
(GBTS) Transmission
(GBTS)
MRFD Bandwidth LQW9BSMCT0 Bandwidth NodeB per

-22150 sharing of MBTS 1 sharing of NodeB
(NodeB) Transmission
(NodeB)
MRFD Bandwidth LT1S0COMBS0 Bandwidth eNode per

-23150 sharing of MBTS 0 sharing of B eNodeB
(eNodeB) Transmission
(FDD)
MRFD Bandwidth LT1SBSMMCT0 Bandwidth eNode Per

-24150 sharing of MBTS 0 sharing of B eNodeB
(LTE TDD) Transmission
(LTE TDD)
7.4.2 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-2 lists
the data to prepare for configuring traffic limiting and shaping.

SingleRAN
Table 7-2 Data to prepare for configuring traffic limiting and shaping if access bandwidth is
limited for multimode base stations
MO Parameter Parameter Setting Notes Data

Name ID Source
LR UL CIR Set this parameter to the Network

Committed access bandwidth planned plan
Information by the operator.
Rate
Committed CBS l If the CIR value is Network

Burst Size smaller than 500 Mbit/s, plan
set CBS to the CIR value
Excessive EBS multiplied by 2 and Network
Burst Size set EBS to 0 Mbit/s. plan
l If the CIR value is
greater than 500 Mbit/s,
set CBS to 1000 Mbit/s
to ensure that the sum of
CBS and EBS is twice
the CIR value.
If access bandwidth is limited for each operator in RAN sharing scenarios, data for traffic limiting
and shaping must be prepared on the base station side that provides a co-transmission port. Table
7-3 lists the data to prepare for configuring traffic limiting and shaping.
Table 7-3 Data to prepare for configuring traffic limiting and shaping if access bandwidth is
limited for each operator in RAN sharing scenarios
MO Parameter Name Paramete Setting Notes Data Source

r ID
RSCGRP Tx Bandwidth TXBW Set this Network plan

parameter to the
access
bandwidth
planned by the
operator.
TX Committed Burst TXCBS l If the Network plan

Size TXBW value
is smaller
than 500
Mbit/s, set
TXCBS to
the TXBW
value
multiplied
by 2 and set

SingleRAN
MO Parameter Name Paramete Setting Notes Data Source

r ID
TX Excessive Burst TXEBS TXEBS to 0 Network plan

Size Mbit/s.
l If the
TXBW value
is greater
than 500
Mbit/s, set
TXCBS to
1000 Mbit/s
to ensure
that the sum
of TXCBS
and TXEBS
is twice the
TXBW
value.
If access bandwidth is unlimited for multimode base stations and limited for each operator in
RAN sharing scenarios, data for traffic limiting and shaping must be prepared on the BSC or
RNC side. Table 7-4 lists the data to prepare for configuring traffic limiting and shaping.
Table 7-4 Data to prepare for configuring traffic limiting and shaping
MO Parameter Parameter ID Setting Notes Data Source

Name
IPLOGICPORT Logic Port No. LPN Set this Network plan

(BSC6900, parameter to the
BSC6910) number of the
BSC/RNC
logical port.

SingleRAN

Name
Bandwidth CIR Set this Network plan

(BSC6900, parameter to the
BSC6910) access
bandwidth
planned by the
operator or
bandwidth
calculated by
the traffic
model. When
the access
bandwidth is
limited for each
operator in RAN
sharing
scenarios, set
this parameter to
the access
bandwidth
planned by each
operator.
Transport QoS
l Transport QoS for GSM services
– Table 7-5 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.
and data from the O&M plane and CP of an eGBTS.
and data from the O&M plane and CP of a BSC. Table 7-9 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
and data from the O&M plane and CP of a NodeB.
and data from the O&M plane, CP, and UP of an RNC.
l Transport QoS for LTE services
and data from the O&M plane and CP of an eNodeB.
and data from the UP of an eNodeB.

SingleRAN
Table 7-5 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 SERVICETYP See the Network plan

E recommended
parameter
DSCP DSCP configurations
in chapter 4
Application
Scenarios.
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 Network plan

parameter to the
DSCP value.
Signaling SIGPRI See the

Priority recommended
parameter
OM High OMHIGHPRI configurations
Priority in chapter 4
OM Low OMLOWPRI Application
Priority Scenarios.
IP Clock IPCLKPRI
Priority

SingleRAN
UP of an eNodeB

Name
UDTPARAGR User Data Type UDTPARAGR Set this Network plan

P Transfer PID parameter to
Parameter 40–48. This
Group ID value
corresponds to
the value of the
User Data
Type (1–9) by
default.
Priority PRI See the Network plan

recommended
parameter
configurations
in chapter 4
Application
Scenarios.
O&M plane and CP of a BSC

Name
BSCABISPRI OML DSCP OMLDSCP See the Network plan

MAP recommended
RSL DSCP RSLDSCP parameter Network plan
EML DSCP EMLDSCP configurations Network plan

in chapter 4
ESL DSCP ESLDSCP Application Network plan
Scenarios.
UP of a BSC

Name
TRMMAP CS voice path CSVOICEPAT See the Network plan

H recommended
parameter
CS data path CSDATAPAT configurations Network plan
H in chapter 4

SingleRAN

Name
PS high PRI PSHPRIDATA Application Network plan

data path PATH Scenarios.
PS low PRI data PSLPRIDATA Network plan

path PATH
Table 7-10 Data to prepare for configuring the mapping between DSCP values and data from
the CP and UP of an RNC

Name
TRMMAP Common CCHPRIPATH See the Network plan

channel primary recommended
path parameter
configurations
IMS SRB SIPPRIPATH in chapter 4 Network plan
primary path Application
SRB primary SRBPRIPATH Scenarios. Network plan
path
AMR voice VOICEPRIPA Network plan

primary path TH
R99 CS CSCONVPRIP Network plan

conversational ATH
primary path
R99 CS CSSTRMPRIP Network plan

streaming ATH
primary path
R99 PS PSCONVPRIP Network plan

conversational ATH
primary path
R99 PS PSSTRMPRIP Network plan

streaming ATH
primary path
R99 PS high PSINTHGHPR Network plan

PRI interactive IPATH
primary path
R99 PS middle PSINTMIDPR Network plan

primary path

SingleRAN

Name
R99 PS low PRI PSINTLOWPR Network plan

interactive IPATH
primary path
R99 PS PSBKGPRIPA Network plan

background TH
primary path
HSDPA Signal HDSRBPRIPA Network plan

primary path TH
HSDPA IMS HDSIPPRIPA Network plan

Signal primary TH
path
HSDPA Voice HDVOICEPRI Network plan

primary path PATH
HSDPA HDCONVPRI Network plan

conversational PATH
primary path
HSDPA HDSTRMPRIP Network plan

streaming ATH
primary path
HSDPA high HDINTHGHP Network plan

PRI interactive RIPATH
primary path
HSDPA middle HDINTMIDPR Network plan

primary path
HSDPA low HDINTLOWP Network plan

primary path
HSDPA HDBKGPRIPA Network plan

background TH
primary path
HSUPA Signal HUSRBPRIPA Network plan

primary path TH
HSUPA IMS HUSIPPRIPA Network plan

Signal primary TH
path
HSUPA Voice HUVOICEPRI Network plan

primary path PATH

SingleRAN

Name
HSUPA HUCONVPRI Network plan

conversational PATH
primary path
HSUPA HUSTRMPRIP Network plan

streaming ATH
primary path
HSUPA high HUINTHGHP Network plan

primary path
HSUPA middle HUINTMIDPR Network plan

primary path
HSUPA low HUINTLOWP Network plan

primary path
HSUPA HUBKGPRIPA Network plan

background TH
secondary path
Flow Control
Table 7-11 lists the data to prepare for setting the flow control algorithm on the NodeB side.
Table 7-11 Data to prepare for setting the flow control algorithm on the NodeB side
MO Parameter Parameter ID Setting Data Source
Name Description
RSCGRPALG Traffic Control TCSW See the Negotiated by

Switch recommended the peer end
parameter
configurations
in chapter 4
Application
Scenarios.
ULFLOWCTR Congestion Ctrl TNLCONGCT See the Negotiated by

LPARA Switch RLSWITCH recommended the peer end
parameter
DLFLOWCTR Flow Control SWITCH configurations
LPARA Switch in chapter 4
Fair Switch FAIRSWITCH Application
Scenarios.

SingleRAN
Other Data
Table 7-12 lists other data to prepare if access bandwidth is limited for multimode base stations.
Table 7-12 Other data to prepare if access bandwidth is limited for multimode base stations
Data Item Sample Value Remarks
Limited access bandwidth for 20 Mbit/s This data specifies the uplink
a base station and downlink limited access
bandwidth for a base station.
Downlink bandwidth on the 20 Mbit/s This data 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 traffic
model of the multimode 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
IP address of an Iub port on 172.16.100.140 None

the RNC side
Table 7-13 lists other data to prepare if access bandwidth is limited for each operator in RAN
sharing scenarios.
Table 7-13 Other data to prepare if access bandwidth is limited for each operator in RAN sharing
scenarios
operator A and downlink limited access
bandwidth for operator A.
operator B 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)
7.4.3 Precautions
None
7.4.4 Hardware Adjustment

N/A
7.4.5 Initial Configuration (Unlimited Access Bandwidth for GU

Dual-Mode Base Stations)
Using MML Commands

Step 1 Configure a transport resource mapping (TRM) table on the base station controller side.
Configure a TRM table for the RNC and BSC, respectively. For details, see 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 and CP on the Iub interface.
from the UP on the Abis interface.

SingleRAN
3. Run the SET BSCABISPRIMAP command to set the mapping between DSCP values and
data from the CP on the Abis interface.
4. Run the ADD ADJMAP command to add the mapping from the Iub interface to the
TRMMAP index.
5. 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.
Configure a TRM table for the GBTS/eGBTS and NodeB, respectively. For details, see section
4.1.2 Transmission Resource Management Strategies.
1. Run the SET BTSVLAN command to set the mapping between DSCP values and data
from the CP and UP of the GBTS. Run the SET DIFPRI command to set the mapping
between DSCP values and data from the CP of the eGBTS.
2. Run the SET DIFPRI command to set the mapping between DSCP values and data from
the CP of the 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

//Configuring a TRM table on the base station controller side
//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;
//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,PSLPRIDATAPATH=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 Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Adding the mapping from the Abis interface to the TRMMAP index
ADD ADJMAP: ANI=3, ITFT=ABIS, TMIGLD=111, FTI=1;

SingleRAN
//Configuring a TRM table on the base station side
Configuring a TRM table on the GBTS side of a multimode base station

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;
Configuring a TRM table on the eGBTS side of a multimode base station

SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;
//Configuring a TRM table on the NodeB side of a multimode base station

//Configuring the uplink bandwidth adaptive flow control switch and HSDPA flow control
switch on the NodeB side
//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;
//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;
Single Configuration 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.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 7-14. For instructions on how to perform the CME single configuration, see
CME Single Configuration Operation Guide.
Table 7-14 MOs related to this feature
SN MO NE
1 a TRMMAP BSC and RNC
b BSCABISPRIMAP BSC
c ADJMAP BSC and RNC
2 a BTSVLAN/DIFPRI GBTS or eGBTS
b DIFPRI NodeB
3 a ULFLOWCTRLPA NodeB
RA

SingleRAN
SN MO NE
b DLFLOWCTRLPA NodeB
RA
7.4.6 Initial Configuration (Unlimited Access Bandwidth for GL/

GT Dual-Mode Base Stations)
Using MML Commands
Step 1 Configure a TRM table on the base station controller side.
Configure a TRM table for the BSC. For details, see section 4.1.2 Transmission Resource
Management Strategies.
TRMMAP index.
Configure a TRM table for the GBTS/eGBTS and eNodeB, respectively. For details, see section
from the CP and UP of the GBTS. Run the SET DIFPRI command to set the mapping
between DSCP values and data from the CP of the eGBTS.
the CP of the eNodeB.
3. Run the MOD UDTPARAGRP command to set the mapping between DSCP values and
data from the UP of the eNodeB.
----End

ADD

SingleRAN
//Setting the mapping between DSCP values and data from the CP and UP of a GBTS
//Setting the mapping between DSCP values and data from the CP of an eGBTS
//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
MOD UDTPARAGRP: UDTPARAGRPID=40, PRIRULE=DSCP, PRI=46, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=44, PRI=46;

SN MO NE
1 a TRMMAP BSC
b BSCABISPRIMAP BSC
c ADJMAP BSC
b DIFPRI eNodeB
c UDTPARAGRP eNodeB

SingleRAN
7.4.7 Initial Configuration (Unlimited Access Bandwidth for UL/

UT/ULT Multimode Base Stations)
Using MML Commands

Configure a TRM table for the RNC. For details, see section 4.1.2 Transmission Resource
TRMMAP index.

the CP of the NodeB.
the CP of the eNodeB.
data from the UP of the eNodeB.
----End

ADD
TMIBRZ=110, FTI=1;
//Setting the mapping between DSCP values and data from the CP of the NodeB

SingleRAN
//Setting the mapping between DSCP values and data from the CP of the eNodeB
//Setting the mapping between DSCP values and data from the UP of the eNodeB
//Configuring the dynamic flow control algorithm for the NodeB
//If the bearer network supports three or more queues in the case of a separate-MPT multimode
base station

//In the case of a separate-MPT multimode base station

//In the case of a co-MPT multimode base station

SWITCH=BW_SHAPING_ONOFF_TOGGLE, FAIRSWTICH=ENABLE;
//If the bearer network supports two queues

BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=OFF;
//Adding an HSDPA flow control parameter in the case of a separate-MPT multimode base
station
SWITCH= NO_BW_SHAPING;
//Adding an HSDPA flow control parameter in the case of a co-MPT multimode base station
SWITCH= NO_BW_SHAPING, FAIRSWTICH=ENABLE;


SingleRAN
SN MO NE
1 a TRMMAP RNC
b ADJMAP RNC
2 a DIFPRI NodeB
b DIFPRI eNodeB
c UDTPARAGRP eNodeB
RA
RA
7.4.8 Initial Configuration (Unlimited Access Bandwidth for GUL/

GUT/GULT Multimode Base Stations)
Using MML Commands

TRMMAP index.
TRMMAP index.

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

SingleRAN
the CP of a NodeB.
the CP of an eNodeB.
data from the UP of an eNodeB.
----End

ADD
ADD
TMIBRZ=110, FTI=1;

SingleRAN

//Setting the mapping between DSCP values and data from the CP of a NodeB

//If the bearer network supports three or more queues
ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP,
PT=ETH, PN=0, BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;


station

SingleRAN

SN MO NE
1 a TRMMAP BSC
b TRMMAP RNC
c BSCABISPRIMAP BSC
d ADJMAP BSC
e ADJMAP RNC
b DIFPRI NodeB
c DIFPRI eNodeB
d UDTPARAGRP eNodeB
RA
RA
7.4.9 Initial Configuration (Limited Access Bandwidth for GU

Dual-Mode Base Stations)
Using MML Commands

Step 1 Configure traffic limiting and shaping on the co-transmission port.
l Run the SET LR command to configure traffic limiting and shaping if the eGBTS or NodeB
side of a separate-MPT multimode base station provides a co-transmission port.
l Run the SET LR command to configure traffic limiting and shaping if a co-MPT multimode
base station provides a co-transmission port.
Step 2 Configure logical ports on the base station controller side.

1. Run the ADD IPLOGICPORT command to add an IP logical port on the Abis interface.
2. Run the ADD IPLOGICPORT command to add an IP logical port on the Iub interface.

SingleRAN
3. Bind a user-plane link and an IP logical port on the Abis interface.

l For a GBTS, you can run the SET BTSIP command to bind an IP logical port and a
GBTS.
l For an eGBTS, you can run the ADD IPPATH command to bind an IP path and an IP
logical port if the peer end is a BSC6900.
l For an eGBTS, you can run the ADD ADJLOGICPORTBIND command to bind an
adjacent node and an IP logical port if the peer end is a BSC6910.
4. Bind a user-plane link and an IP logical port on the Iub interface.
l 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.
l 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.
TRMMAP index.
Configure a TRM table for the GBTS/eGBTS and NodeB, respectively. For details, see section
the CP of a NodeB.
----End

SingleRAN

//Configuring traffic limiting and shaping on the co-transmission port
//Configuring traffic limiting and shaping if the eGBTS 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 traffic limiting and shaping if the NodeB side of a separate-MPT multimode base
CBS=40000, EBS=0;
//Configuring traffic limiting and shaping if a co-MPT multimode base station provides a co-
transmission port
CBS=40000, EBS=0;
//Configuring logical ports on the base station controller side
//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 10,048 kbit/s.

ADD IPLOGICPORT: SRN=1, SN=24, BT=GOUc, LPNTYPE=Leaf, FLOWCTRLSWITCH=ON, CIR=157,
LPN=1, CARRYT=IPPOOL, IPADDR="172.16.140.140";//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 10,048 kbit/s.
//Adding a logical port on the Iub interface

RSCMNGMODE=SHARE, BWADJ=OFF, CIR=313, 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 313 means that the configured bandwidth is 20,032 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

SingleRAN
ADD ADJLOGICPORTBIND: ANI=3, SRN=1, SN=24, LPN=1;
//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
ADD
TMIBRZ=110, FTI=1;

Configuring a TRM table on the GBTS side of a multimode base station
Configuring a TRM table on the eGBTS side of a multimode base station

//Configuring a TRM table on the NodeB side of a multimode base station

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


SN MO NE
1 a LR/LR/LR eGBTS, NodeB, or

co-MPT multimode
base stations
2 a IPLOGICPORT BSC and RNC
b BTSIP/IPPATH/ BSC
ADJLOGICPORTB
IND
c IPPATH/ RNC
ADJLOGICPORTB
IND
3 a TRMMAP BSC and RNC
b BSCABISPRIMAP BSC
c ADJMAP BSC and RNC
b DIFPRI NodeB
RA
RA

SingleRAN
7.4.10 Initial Configuration (Limited Access Bandwidth for GL/GT/

GLT Multimode Base Stations)
Using MML Commands
l Run the SET LR command to configure traffic limiting and shaping if the eGBTS or eNodeB
l For a GBTS, you can run the SET BTSIP command to bind an IP logical port and a GBTS.
l For an eGBTS, you can run the ADD IPPATH command to bind an IP path and an IP logical
port if the peer end is a BSC6900.
Configure a TRM table for the BSC. For details, see section 4.2.2 Transmission Resource
TRMMAP index.
Configure a TRM table for the GBTS/eGBTS and eNodeB, respectively. For details, see section
----End


SingleRAN
CBS=40000, EBS=0;
//Configuring traffic limiting and shaping if the eNodeB side of a separate-MPT multimode base
CBS=40000, EBS=0;
transmission port
CBS=40000, EBS=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 10,048 kbit/s.

157 means that the configured bandwidth is 10,048 kbit/s.
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.
is a BSC6900
AbisLnkBKFLAG=OFF;
end is a BSC6910

ADD

SingleRAN

SN MO NE
1 a LR/LR/LR eGBTS, eNodeB, or

co-MPT multimode
base stations
2 a IPLOGICPORT BSC
b BTSIP/IPPATH/ BSC
ADJLOGICPORTB
IND

SingleRAN
SN MO NE
3 a TRMMAP BSC
b BSCABISPRIMAP BSC
c ADJMAP BSC
b DIFPRI eNodeB
c UDTPARAGRP eNodeB
7.4.11 Initial Configuration (Limited Access Bandwidth for UL/UT/

ULT Multimode Base Stations)
Using MML Commands

l Run the SET LR command to configure traffic limiting and shaping if the NodeB or eNodeB

run the ADD IPPATH command to bind an IP path and an IP logical port on the Iub interface.
port on the Iub interface.
TRMMAP index.

the CP of a NodeB.

SingleRAN
Step 6 Disable the traffic control switch of the default transport resource group configured on the co-
transmission port.
If the NodeB or eNodeB 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 transport 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

CBS=40000, EBS=0;
CBS=40000, EBS=0;
transmission port
CBS=40000, EBS=0;


SingleRAN

ADD
TMIBRZ=110, FTI=1;



SingleRAN



station
//Disabling the traffic control switch of the default transport resource group configured on the
co-transmission port
//Configuring a default transport resource group on the co-transmission port in a separate-MPT

multimode base station where co-transmission is implemented through panel interconnection
ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT, RU=KBPS;
//Disabling the traffic control switch on the default transport resource group you have configured
SET RSCGRPALG: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT,
TCSW=DISABLE;

SN MO NE
1 a LR/LR/LR NodeB, eNodeB, or

co-MPT multimode
base stations
2 a IPLOGICPORT RNC

SingleRAN
SN MO NE
b IPPATH/ RNC
ADJLOGICPORTB
IND
3 a TRMMAP RNC
b ADJMAP RNC
4 a DIFPRI NodeB
b DIFPRI eNodeB
c UDTPARAGRP eNodeB
RA
RA
6 a RSCGRP NodeB, eNodeB, or

multimode base
stations
b RSCGRPALG NodeB, eNodeB, or

multimode base
stations
7.4.12 Initial Configuration (Limited Access Bandwidth for GUL/

GUT/GULT Multimode Base Stations)
Using MML Commands

l Run the SET LR command to configure traffic limiting and shaping if the eGBTS, NodeB,
or eNodeB side of a separate-MPT multimode base station provides a co-transmission port.

l For a GBTS, you can run the SET BTSIP command to bind an IP logical port and a
GBTS.
l For an eGBTS, you can run the ADD IPPATH command to bind an IP path and an IP
logical port if the peer end is a BSC6900.

SingleRAN
run the ADD IPPATH command to bind an IP path and an IP logical port.
port.
Configure a TRM table for the RNC and BSC, respectively. For details, see 4.2.2 Transmission
Resource Management Strategies.
TRMMAP index.
TRMMAP index.
the CP of a NodeB.
transmission port.
bandwidth from the local data. This deteriorates user experience.

SingleRAN
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

CBS=40000, EBS=0;
CBS=40000, EBS=0;
CBS=40000, EBS=0;
transmission port
CBS=40000, EBS=0;

Therefore, the CIR value 157 means that the configured bandwidth is 10048 kbit/s.

157 means that the configured bandwidth is 10048 kbit/s.

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.

SingleRAN
is a BSC6900
AbisLnkBKFLAG=OFF;
end is a BSC6910
ADD
ADD
TMIBRZ=110, FTI=1;

SingleRAN


//If the bearer network supports three or more queues in the case of a separate-MPT multimode
base station
In the case of a separate-MPT multimode base station



station

SingleRAN


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

SN MO NE
1 a LR/LR/LR/LR eGBTS, NodeB,

eNodeB, or co-MPT
multimode base
stations
2 a IPLOGICPORT BSC and RNC
b BTSIP/IPPATH/ BSC
ADJLOGICPORTB
IND
c IPPATH/ RNC
ADJLOGICPORTB
IND
3 a TRMMAP BSC
b TRMMAP RNC
c BSCABISPRIMAP BSC
d ADJMAP BSC
e ADJMAP RNC
b DIFPRI NodeB

SingleRAN
SN MO NE
c DIFPRI eNodeB
d UDTPARAGRP eNodeB
RA
RA
6 a RSCGRP eGBTS, NodeB,

eNodeB, or co-MPT
multimode base
stations
b RSCGRPALG eGBTS, NodeB,

eNodeB, or co-MPT
multimode base
stations
7.4.13 Initial Configuration (Limited Access Bandwidth for Each

Operator in a UL/UT Dual-Mode Base Station in RAN Sharing
Scenarios)
Using MML Commands
l Scenario 1: The NodeB side of a separate-MPT multimode base station provides a co-
transmission port.
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 transport resource
group on the base station side.
NOTE
A user-plane link can be configured either in link mode or in end-point mode. In link mode, users
configure an IP path. In end-point mode, users configure an end point group that includes the IP
addresses of the local and peer ends.
l If you use link mode to configure a user-plane link:
a. Run the ADD IPPATH command to add an IP path and bind this IP path and the
configured transport resource group.
b. Run the ADD NODEBPATH command to bind a NodeB and the added IP path.
l If you use end-point mode to configure a user-plane link:
a. Run the ADD EPGROUP command to add an end point group on the base station
side.
b. Run the ADD USERPLANEHOST command to add a user-plane host on the base
station side.

SingleRAN
c. Run the ADD USERPLANEPEER command to add a user-plane peer on the base
station side.
d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host and
the added end point group on the base station side.
e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer and
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 and a transport resource group on the base station side.
l Scenario 2: The eNodeB side of a separate-MPT multimode base station provides a co-
transmission port.
2. Bind a user-plane link for transmitting local data and the configured transport resource
group on the base station side.
b. Run the ADD ENODEBPATH command to bind an eNodeB and the added IP path.
side.
station side.
station side.
3. Run the ADD IP2RSCGRP command to bind a user-plane link for transmitting passing
data and a transport resource group on the base station side.
l Scenario 3: A co-MPT multimode base station provides a co-transmission port.
2. Bind a user-plane link and the configured transport resource group on the base station side.
configured transport resource group. In this step, set Peer IP to the RNC IP address.
b. Run the ADD NODEBPATH command to bind a NodeB and the added IP path.
c. Run the ADD IPPATH command to bind the added IP path and the configured
transport resource group. In this step, set Peer IP to the SeGW IP address.

SingleRAN
d. Run the ADD ENODEBPATH command to bind an eNodeB and the added IP path.
side.
station side.
station 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.
the CP of a NodeB.
transmission port.

SingleRAN
bandwidth from the local data. This deteriorates user experience. Run the SET RSCGRPALG
command to disable the traffic control switch of the default transport resource group you have
configured.
----End

//Two operators share one multimode base station
//If the NodeB side of a separate-MPT multimode base station provides a co-transmission port
//Configuring a transport 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;
//If you use link mode to configure a user-plane link
//Binding an IP path and the configured transport 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;
//If you use end-point mode to configure a user-plane link
//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, LOCIPV4="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 transport resource group
ADD IP2RSCGRP: SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1, DSTIP="172.15.90.140",
DSTMASK="255.255.255.255";
DSTMASK="255.255.255.255";
//If the eNodeB side of a separate-MPT multimode base station provides a co-transmission port

SingleRAN


ADD ENODEBPATH: IpPathId=1, AppType=S1, S1InterfaceId=0;
//Binding the passing data and the configured transport resource group
DSTMASK="255.255.255.255";
DSTMASK="255.255.255.255";
//If a co-MPT multimode base station provides a co-transmission port



SingleRAN



RSCMNGMODE=EXCLUSIVE, 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 10,048 kbit/
s.
RSCMNGMODE=EXCLUSIVE, 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 10,048 kbit/
s.
//Binding an IP path and the logical port you have added on the Iub interface

ADD

SingleRAN
TMIBRZ=110, FTI=1;




station

SingleRAN

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

SN MO NE
1 a RSCGRP NodeB, eNodeB, or

co-MPT multimode
base stations
b IPPATH NodeB, eNodeB, or

co-MPT multimode
base stations
c NODEBPATH NodeB or co-MPT

multimode base
stations
d ENODEBPATH eNodeB or co-MPT

multimode base
stations
e IP2RSCGRP NodeB or eNodeB
2 a IPLOGICPORT RNC
b IPPATH/ RNC
ADJLOGICPORTB
IND
3 a TRMMAP RNC
b ADJMAP RNC
4 a DIFPRI NodeB

SingleRAN
SN MO NE
b DIFPRI eNodeB
c UDTPARAGRP eNodeB
RA
RA
6 a RSCGRPALG NodeB, eNodeB, or

multimode base
stations
7.4.14 Activation Observation (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:
l Separate-MPT multimode base station
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

SingleRAN
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 Co-MPT multimode base station

l If GSM services are initiated, start IP or MAC tracing on the LMT of the co-MPT multimode
base station.
l If UMTS services are initiated, start IP or MAC tracing on the LMT of the co-MPT multimode
base station.
l If LTE services are initiated, start IP or MAC tracing on the LMT of the co-MPT multimode
base station.
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 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.15 Activation Observation (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.
Step 3 Query the value of the VS.RscGroup.FlowOverloadTime counter for the co-transmission port.
If the value is greater than 0, this feature has been activated.
----End

SingleRAN
If you need to check whether the configured service priority has taken effect, perform the
l The eGBTS side of a separate-MPT 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.
----End
l The NodeB side of a separate-MPT 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.
l If yes, this feature has been activated.

SingleRAN
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 separate-MPT 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
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
l A co-MPT 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 LMT.

l If UMTS services are initiated, start transport link flux monitoring on the LMT. Choose
Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring.
l If LTE services are initiated, start transport link flux monitoring on the LMT. Choose
the bearer network.
Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meter
NOTE
Step 4 is performed only in a separate-MPT GU/GL dual-mode base station or a separate-MPT GUL triple-
mode base station.

l If GSM services are initiated, start IP or MAC tracing on the 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.
Trace dialog box,specify Local MAC Address and Peer MAC Address of the packets to
be traced.
l If UMTS services are initiated, start IP or MAC tracing on the LMT.
Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to
be traced.
l If LTE services are initiated, start IP or MAC tracing on the LMT.

SingleRAN
Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to
be traced.
----End
7.4.16 Activation Observation (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
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.FlowOverloadTime 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
l Separate-MPT multimode base station
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.

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
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
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.

l Start IP or MAC tracing on the NodeB 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
l Start IP or MAC tracing on the eNodeB LMT.
----End
l Co-MPT multimode base station
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.

l If UMTS services are initiated, start transport link flux monitoring on the NodeB LMT.
Choose Monitor > Realtime Performance Monitoring > Transport Link Flux
Monitoring.
l If LTE services are initiated, start transport link flux monitoring on the eNodeB LMT. Choose
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.

l If UMTS services are initiated, start IP or MAC tracing on the NodeB LMT.
l If LTE services are initiated, start IP or MAC tracing on the eNodeB LMT.

SingleRAN
----End
7.5 Performance Monitoring

Transmission resource congestion in a base station is indicated by the congestion duration of
transport resource groups calculated by the VS.RscGroup.FlowOverloadTime counter.
7.6 Parameter Optimization

None
7.7 Troubleshooting
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 Parameter description
Parame NE MML Feature Feature Description

ter ID Comma ID Name
nd
CIR BTS390 SET LR WRFD- HSDPA Meaning: Indicates the UL committed information rate
0, LST LR 0106101 Flow after rate limitation is configured at a port. The precision
BTS390 0 Control of the UL committed information rate supported by the
0 UMPTb is 64 Kbit/s, the precision supported by the
WCDM LOFD-0 Transpo other board is 32 Kbit/s. If the configured UL committed
A, 0301101 rt information rate is not a multiple of the precision, the
BTS390 / Overboo UL committed information rate is rounded up.
0 LTE TDLOF king
D-00301 Transpo GUI Value Range: 32~1000000
101 rt Unit: Kbit/s
LOFD-0 Differen Actual Value Range: 32~1000000
0301102 tiated
Flow Default Value: None
/
TDLOF Control
D-00301
102 IP QOS
GBFD-1
18605

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. This
0 MOD e parameter value is used as the uplink transport
WCDM LOFD-0 Sharing admission bandwidth and TX traffic shaping
RSCGR 03011 /
A, P on Iub/ bandwidth.The LMPT can be configured with a
BTS390 TDLOF Iur maximum of 360 Mbit/s TX bandwidth.The WMPT can
0 LTE DSP D-00301 Interface be configured with a maximum of 300 Mbit/s TX
RSCGR 1 bandwidth.The UMPT or UTRPc can be configured
P Enhance with a maximum of 1 Gbit/s TX bandwidth.The value
GBFD-1 d
LST 18605 of TX bandwidth is set to the maximum value of TX
RSCGR Transmi bandwidth supported by the board when it bigger than
P ssion the maximum one. For a WMPT and a UTRP (excluding
QoS UTRPa), this parameter does not specify the TX traffic
Manage shaping bandwidth of the transmission resource group
ment that is carried on the PPP link.
IP QOS GUI Value Range: 32~1000000
Unit: None
Actual Value Range: 32~1000000
Default Value: None
CIR BSC690 ADD WRFD- Overboo Meaning: Bandwidth of the logical port
0 IPLOGI 050408 king on GUI Value Range: 1~1562
CPORT WRFD- IP
Transmi Unit: 64kbit/s
MOD 140208
IPLOGI ssion Actual Value Range: 64~64000(FG2a/GOUa/UOIa
WRFD- (IP)), 256~99968(FG2c/GOUc/POUc(IP)/PEUc(IP)/
CPORT 021311 Iub
Transmi GOUe)
WRFD- ssion Default Value: None
140207 Resourc
e Pool in
RNC
MOCN
Introduc
tion
Package
Iu/Iur
Transmi
ssion
Resourc
e Pool in
RNC

SingleRAN

nd
CIR BSC691 ADD WRFD- Overboo Meaning: Bandwidth of the logical port.
0 IPLOGI 050408 king on GUI Value Range: 4~1562
CPORT IP
Transmi Unit: 64kbit/s
MOD
IPLOGI ssion Actual Value Range: 256~99968
CPORT Default Value: None
TNLCO BTS390 ADD None None Meaning: Indicates whether to perform congestion
NGCTR 0, ULFLO control. When this switch is turned on, the BS lowers
LSWIT BTS390 WCTRL the TX rate if the BS detects that links experience
CH 0 PARA transmission delay or packet loss.It is recommended
WCDM SET that this switch be turned off if UMTS and LTE services
A ULFLO are configured in the same transmission resource group.
WCTRL The purpose is to prevent UMTS flow control from
PARA affecting LTE services.
LST GUI Value Range: OFF(Off), ON(On)

ULFLO Unit: None
WCTRL Actual Value Range: OFF, ON
PARA
Default Value: ON(On)

SingleRAN

nd
TCSW BTS390 SET LOFD-0 Transpo Meaning: Indicates whether to enable the backpressure
0, RSCGR 0301101 rt algorithm of a transmission resource group. The BS
BTS390 PALG / Overboo monitors the data buffered in the queues of each
0 LST TDLOF king transmission resource group, determines whether the
WCDM RSCGR D-00301 Transpo transmission resource group is congested, and transmits
A, PALG 101 rt the backpressure signals (number and congestion status
BTS390 LOFD-0 Differen of the transmission resource group) to each flow control
0 LTE 0301102 tiated service. If the number of data packets in the buffer of
/ Flow any backpressure queue exceeds 75% of the queue
TDLOF Control capacity, the BS regards this transmission resource
D-00301 group as congested and transmits congestion signals. If
102 the buffered back-pressure packets are less than 50% of
the total buffer capacity, the BS decides that the
transmission resource group is not congested. In this
situation, no congestion signal or congestion release
signal is transmitted. When this parameter is set to
ENABLE, both intra-mode and inter-mode traffic
controls are supported. The inter-mode traffic control
for transmission resource groups applies only to
separate-MPT base stations with co-transmission
implemented through backplane interconnection.
However, it does not apply to cascaded base stations,
base stations with co-transmission implemented
through panel interconnection, or base stations enabled
with route load sharing. When the inter-mode traffic
control function is enabled for a separate-MPT base
station with co-transmission implemented through
backplane interconnection, the Tunnel Type parameter
must be set to DL(DL) for the tunnel of the mode
providing transmission ports and must be set to UL(UL)
for the tunnel of the mode providing no transmission
port.
GUI Value Range: DISABLE(Disable), ENABLE
(Enable)
Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: ENABLE(Enable)

SingleRAN

nd
SWITC BTS390 ADD WRFD- HSDPA Meaning: Indicates the switch for the DL flow control
H 0, DLFLO 0106101 Flow algorithm. If this parameter is set to
BTS390 WCTRL 0 Control DYNAMIC_BW_SHAPING, flow allocation for
0 PARA HSDPA users is performed according to the delay and
WCDM SET packet loss of the transmission interface board in
A DLFLO STATIC_BW_SHAPING mode. This function requires
WCTRL the network controller using the switch of the 3GPP R6
PARA protocol. Therefore, you are advised to use this function
with the RNC that complies with the 3GPP R6 protocol.
LST If this parameter is set to NO_BW_SHAPING, the BS
DLFLO does not allocate bandwidth according to the
WCTRL configuration and delay of the transmission interface
PARA board. The BS reports the air interface conditions to the
controller, and then the controller allocates bandwidth.
When this parameter is set to NO_BW_SHAPING, the
backpressure function must be enabled on the controller
side. If this parameter is set to
BW_SHAPING_ONOFF_TOGGLE, the BS
automatically selects either DYNAMIC_BW_SHAP-
ING or NO_BW_SHAPING during a flow congestion
detection on a port. That is, DYNAMIC_BW_SHAP-
ING is selected if congestion is detected;
NO_BW_SHAPING is selected if congestion is not
detected for a certain period of time.
GUI Value Range: STATIC_BW_SHAPING
(STATIC_BW_SHAPING), DYNAMIC_BW_SHAP-
ING(DYNAMIC_BW_SHAPING),
NO_BW_SHAPING(NO_BW_SHAPING),
BW_SHAPING_ONOFF_TOGGLE
(BW_SHAPING_ONOFF_TOGGLE)
Unit: None
Actual Value Range: STATIC_BW_SHAPING,
DYNAMIC_BW_SHAPING, NO_BW_SHAPING,
BW_SHAPING_ONOFF_TOGGLE
Default Value: BW_SHAPING_ONOFF_TOGGLE
(BW_SHAPING_ONOFF_TOGGLE)

SingleRAN

nd
FAIRS BTS390 ADD WRFD- HSDPA Meaning: Indicates the switch controlling downlink
WITCH 0, DLFLO 0106101 Flow fairness flow control. When multiple modes share
BTS390 WCTRL 0 Control transmission bandwidth and congestion occurs, the
0 PARA UMTS data rate may decrease due to downlink flow
WCDM SET control and the LTE data rate may increase due to
A DLFLO bandwidth preemption. When the fairness flow control
WCTRL switch is turned on, the system guarantees the minimum
PARA downlink transmission bandwidth of the UMTS
mode.This switch only support ETH(Ethernet Port)and
LST ETHTRK(Ethernet Trunk) and LOOPINT(Loop
DLFLO Interface) , the loopint's actual interface is ETH or
WCTRL ETHTRK.
PARA
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
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 minimum
BTS390 ssion rate supported by the UMPTb is 64 Kbit/s.
0 LOFD-0 Introduc
0301101 GUI Value Range: 32~1000000
WCDM tion on
A, / Iub Unit: Kbit
BTS390 TDLOF Interface Actual Value Range: 32~1000000
0 LTE D-00301
101 Transpo Default Value: None
LOFD-0 rt
0301102 Overboo
/ king
TDLOF Transpo
D-00301 rt
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~1000000
0 LOFD-0 Introduc
WCDM 0301101 tion on Unit: Kbit
A, / Iub Actual Value Range: 0~1000000
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 Iub/ size.The WMPT can be configured with a maximum of
BTS390 TDLOF Iur 600 Mbit/s TX committed burst size.The UMPT or
0 LTE LST D-00301 Interface UTRPc can be configured with a maximum of 1 Gbit/s
RSCGR 1 TX committed burst size.The value of TX committed
P Enhance burst size is set to the maximum value of TX committed
GBFD-1 d
18605 burst size supported by the board when it bigger than
Transmi the maximum one.
ssion
QoS GUI Value Range: 64~1000000
Manage Unit: Kbit
ment Actual Value Range: 64~1000000
IP QOS 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 excessive
0 MOD e burst size.The WMPT can be configured with a
WCDM LOFD-0 Sharing maximum of 600 Mbit/s TX excessive burst size.The
RSCGR 03011 /
A, P on Iub/ UMPTor UTRPc can be configured with a maximum of
BTS390 TDLOF Iur 1 Gbit/s TX excessive burst size.The value of TX
0 LTE LST D-00301 Interface excessive burst size is set to the maximum value of TX
RSCGR 1 excessive burst size supported by the board when it
P Enhance bigger than the maximum one.
GBFD-1 d
18605 Transmi GUI Value Range: 64~1000000
ssion Unit: Kbit
QoS Actual Value Range: 64~1000000
Manage
ment Default Value: 1000000
IP QOS
LPN BSC690 ADD WRFD- Iub Meaning: Logical port number. It is uniquely numbered
0 IPLOGI 140208 Transmi within the active/standby boards.
CPORT WRFD- ssion GUI Value Range: 0~988;1024~1535
MOD 140207 Resourc
e Pool in Unit: None
IPLOGI
CPORT RNC Actual Value Range: 0~119(FG2a/GOUa/UOIa(IP));
Iu/Iur 0~489, 512~767(FG2c); 0~499, 512~767(GOUc/
RMV GOUe); 0~988, 1024~1535(POUc(IP)); 0~127,
IPLOGI Transmi
ssion 1024~1087(PEUc(IP))
CPORT
Resourc Default Value: None
e Pool in
RNC
LPN BSC691 ADD None None Meaning: Logical port number.

0 IPLOGI GUI Value Range: 0~2047
CPORT
Unit: None
MOD
IPLOGI Actual Value Range: 0~489(FG2c, GOUc, GOUe),
CPORT 512~767(FG2c, GOUc, GOUe);0~1499(EXOUa),
1536~2047(EXOUa)
RMV
IPLOGI Default Value: None
CPORT

SingleRAN

nd
PRIRUL BTS390 SET WRFD- IP Meaning: Indicates the rule for prioritizing traffic to
E 0, DIFPRI 050402 Transmi meet service requirements. If this parameter is set to
BTS390 LST ssion IPPRECEDENCE, the protocol stack of the earlier
0 LBFD-0 Introduc version is adopted, which firstly converts a Type of
DIFPRI 0300201
WCDM tion on Service (TOS) to a DSCP and then prioritizes 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 this
BTS390 LST ssion 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
OMHIG BTS390 SET WRFD- IP Meaning: Indicates the priority of the high-level OM
HPRI 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

SingleRAN

nd
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 of
0 LBFD-0 Introduc 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
IPCLKP BTS390 SET None None Meaning: Indicates the priority of the IP clock. If the IP
RI 0, DIFPRI clock that follows the Precision Time Protocol (PTP) is
BTS390 LST used, set this parameter to the DSCP of the PTP packets.
0 DIFPRI If the IP clock that follows the Huawei proprietary
WCDM protocol is used, set this parameter to the DSCP of these
A, packets that follow the Huawei proprietary protocol.
BTS390 GUI Value Range: 0~63
0 LTE
Unit: None
Actual Value Range: 0~63
Default Value: 46
CCHPR BSC690 ADD WRFD- ATM Meaning: Primary path that carries the common channel
IPATH 0 TRMM 050406 QoS services.
AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE, LQAF11,
AP Node B LQAF12, LQAF13, LQAF21, LQAF22, LQAF23,
(Overbo LQAF31, LQAF32, LQAF33, LQAF41, LQAF42,
oking on LQAF43, LQEF
Hub
Node B Unit: None
Transmi Actual Value Range: CBR, RT_VBR, NRT_VBR,
ssion) UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF42, LQAF43, LQEF
Default Value: None

SingleRAN

nd
SIPPRIP BSC690 ADD WRFD- ATM Meaning: This parameter is used to set IMS SRB
ATH 0 TRMM 050406 QoS primary path.
AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
Hub
Node B Unit: None
Default Value: None
SRBPRI BSC690 ADD WRFD- ATM Meaning: Signaling service bearer primary path.
PATH 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE, LQAF11,
TRMM Hub LQAF12, LQAF13, LQAF21, LQAF22, LQAF23,
(Overbo LQAF43, LQEF
oking on
Hub Unit: None
Node B Actual Value Range: CBR, RT_VBR, NRT_VBR,
Transmi UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
ssion) AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
Default Value: None

SingleRAN

nd
VOICE BSC690 ADD WRFD- ATM Meaning: AMR voice service bearer primary path.
PRIPAT 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
H AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
oking on
Hub Unit: None
Default Value: None
CSCON BSC690 ADD WRFD- ATM Meaning: R99 CS conversational service primary path.
VPRIPA 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
CSSTR BSC690 ADD WRFD- ATM Meaning: R99 CS streaming service bearer primary
MPRIP 0 TRMM 050406 QoS path.
ATH AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
Hub
Node B Unit: None
Default Value: None
PSCON BSC690 ADD WRFD- ATM Meaning: R99 PS conversational service primary path.
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
PSSTR BSC690 ADD WRFD- ATM Meaning: R99 PS streaming service bearer primary
Hub
Node B Unit: None
Default Value: None
PSINTH BSC690 ADD WRFD- ATM Meaning: R99 PS high PRI interactive primary path.
GHPRIP 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
ATH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
PSINT BSC690 ADD WRFD- ATM Meaning: R99 PS middle PRI interactive primary path.
MIDPRI 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
PATH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
oking on
Hub Unit: None
Default Value: None
PSINTL BSC690 ADD WRFD- ATM Meaning: R99 PS low PRI interactive primary path.
OWPRI 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
PSBKG BSC690 ADD WRFD- ATM Meaning: R99 PS background service bearer primary
PRIPAT 0 TRMM 050406 QoS path.
H AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
Hub
Node B Unit: None
Default Value: None
HDSRB BSC690 ADD WRFD- ATM Meaning: HSDPA signaling bearer primary path.
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
HDSIPP BSC690 ADD WRFD- ATM Meaning: HSDPA IMS signaling bearer primary path.
RIPAT 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
oking on
Hub Unit: None
Default Value: None
HDVOI BSC690 ADD WRFD- ATM Meaning: HSDPA voice service bearer primary path.
CEPRIP 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
HDCON BSC690 ADD WRFD- ATM Meaning: HSDPA conversational service bearer
VPRIPA 0 TRMM 050406 QoS primary path.
TH AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
Hub
Node B Unit: None
Default Value: None
HDSTR BSC690 ADD WRFD- ATM Meaning: HSDPA streaming service bearer primary
Hub
Node B Unit: None
Default Value: None

SingleRAN

nd
HDINT BSC690 ADD WRFD- ATM Meaning: HSDPA high PRI interactive primary path.
HGHPR 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
IPATH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
oking on
Hub Unit: None
Default Value: None
HDINT BSC690 ADD WRFD- ATM Meaning: HSDPA middle PRI interactive primary path.
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
HDINT BSC690 ADD WRFD- ATM Meaning: HSDPA low PRI interactive primary path.
LOWPR 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
oking on
Hub Unit: None
Default Value: None
HDBKG BSC690 ADD WRFD- ATM Meaning: HSDPA background service bearer primary
Hub
Node B Unit: None
Default Value: None

SingleRAN

nd
HUSRB BSC690 ADD WRFD- ATM Meaning: HSUPA signaling bearer primary path.
oking on
Hub Unit: None
Default Value: None
HUSIPP BSC690 ADD WRFD- ATM Meaning: HSUPA IMS signaling bearer primary path.
RIPAT 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
HUVOI BSC690 ADD WRFD- ATM Meaning: HSUPA voice service bearer primary path.
CEPRIP 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
oking on
Hub Unit: None
Default Value: None
HUCON BSC690 ADD WRFD- ATM Meaning: HSUPA conversational service primary path.
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
HUSTR BSC690 ADD WRFD- ATM Meaning: HSUPA streaming service bearer primary
Hub
Node B Unit: None
Default Value: None
HUINT BSC690 ADD WRFD- ATM Meaning: HSUPA high PRI interactive primary path.
HGHPR 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
HUINT BSC690 ADD WRFD- ATM Meaning: HSUPA middle PRI interactive primary path.
oking on
Hub Unit: None
Default Value: None
HUINT BSC690 ADD WRFD- ATM Meaning: HSUPA low PRI interactive primary path.
LOWPR 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
oking on
Hub Unit: None
Default Value: None

SingleRAN

nd
HUBKG BSC690 ADD WRFD- ATM Meaning: HSUPA background service bearer primary
Hub
Node B Unit: None
Default Value: None

SingleRAN
Transmission Feature Parameter Description 9 Counters
9 Counters
Table 9-1 Counter description
Counter ID Counter Name Counter NE Feature ID Feature Name

Description
1542455378 VS.RscGroup.T Congestion NodeB Multi-mode: Bandwidth

xFlowOverload- duration of MRFD-211505 sharing of
Time transmit data in MRFD-221505 MBTS Multi-
the resource mode Co-
group MRFD-231505 Transmission
MRFD-241505 (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 (SRAN9.0 - 02)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Bandwidth Sharing of Multimode Base Station Co-Transmission (SRAN9.0 - 02)

Încărcat de

Drepturi de autor:

Formate disponibile

SingleRAN

Bandwidth Sharing of Multimode

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2014-12-30) Huawei Proprietary and Confidential i

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

Issue 02 (2014-12-30) Huawei Proprietary and Confidential ii

6.1 System Capacity...........................................................................................................................................................37

Issue 02 (2014-12-30) Huawei Proprietary and Confidential iii

1 About This Document

This document describes the following optional features:

l MRFD-211505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(GBTS)

LTE LTE FDD LTE TDD

eNodeB LTE FDD eNodeB LTE TDD eNodeB

eRAN LTE FDD eRAN LTE TDD eRAN

1.2 Intended Audience

l Need to understand the features described herein

Issue 02 (2014-12-30) Huawei Proprietary and Confidential 1

l Work with Huawei products

1.3 Change History

Change Type Change Description Parameter

Feature change None. None.

Editorial Optimized the document description of chapter 4 None.

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

Change Type Change Description Parameter

Feature change l Added the descriptions of the LTE(TDD) mode None.

Editorial Added activation observation methods. For details, see None.

Issue 02 (2014-12-30) Huawei Proprietary and Confidential 2

1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations

MRFD-211505 Bandwidth sharing of MBTS Yes No No

MRFD-221505 Bandwidth sharing of MBTS Yes No Yes

MRFD-231505 Bandwidth sharing of MBTS Yes No Yes

MRFD-241505 Bandwidth sharing of MBTS Yes No No

Function Implementation in Macro, Micro, and LampSite Base Stations

Issue 02 (2014-12-30) Huawei Proprietary and Confidential 3

l Saved transmission resources

l Guaranteed service quality and user experience

Issue 02 (2014-12-30) Huawei Proprietary and Confidential 4

2.3 Application Networking

MME: mobility management entity

Issue 02 (2014-12-30) Huawei Proprietary and Confidential 5

Issue 02 (2014-12-30) Huawei Proprietary and Confidential 6

l For a separate-MPT multimode base station in co-transmission scenarios, the co-

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

Table 3-1 lists the definitions of all kinds of base stations.

Table 3-1 Definitions of base stations

Base Station Name Definition

GBTS GBTS refers to a base station deployed with GTMU.

eGBTS eGBTS refers to a base station deployed with UMPT_G.

Issue 02 (2014-12-30) Huawei Proprietary and Confidential 7

Base Station Name Definition

NodeB NodeB refers to a base station deployed with WMPT or

eNodeB eNodeB refers to a base station deployed with LMPT, UMPT_L,

Separate-MPT Separate-MPT multimode base station refers to a base station on

To enable a co-transmission port to implement unified data scheduling and management,

3.2 Transmission Priorities

Issue 02 (2014-12-30) Huawei Proprietary and Confidential 8

behaviors (PHBs) accordingly. PHBs include transmission resource allocation, queue

GBTS SET BTSVLAN Used to set the mapping

eGBTS and SET DIFPRI Used to set the mapping

ADD TRMMAP and SET Used to set the mapping