Bandwidth Sharing of MBTS Multi-Mode Co-Transmission (SRAN7.0 - 02)

Bandwidth Sharing of MBTS Multi-Mode
Co-Transmission
SRAN7.0
Feature Parameter Description
Issue
02
Date
2012-08-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. 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 the 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
SingleRAN
Co-Transmission
Contents
Contents
1 About This Document ..............................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview......................................................................................................................................2-1
3 Technical Description ..............................................................................................................3-1
3.1 Transmission Resource Scheduling and QoS Management ........................................................ 3-1
3.2 Transmission Resource Allocation ................................................................................................ 3-1
3.3 Transmission Priority ..................................................................................................................... 3-1
3.4 Load Control .................................................................................................................................. 3-3
3.5 Flow Control .................................................................................................................................. 3-4
4 Related Features .......................................................................................................................4-1

4.1 Required Features......................................................................................................................... 4-1
4.2 Mutually Exclusive Features ......................................................................................................... 4-1
4.3 Affected Features .......................................................................................................................... 4-1
5 Impact on the Network.............................................................................................................5-1

5.1 System Capacity ........................................................................................................................... 5-1
5.2 Network Performance ................................................................................................................... 5-1
6 Engineering Guidelines ...........................................................................................................6-1

6.1 When to Use Bandwidth Sharing of MBTS Multi-Mode Co-Transmission .................................... 6-1
6.2 Information to Be Collected ........................................................................................................... 6-1
6.3 Network Planning .......................................................................................................................... 6-1
6.3.1 RF Planning .......................................................................................................................... 6-1
6.3.2 Network Topology ................................................................................................................. 6-1
6.3.3 Hardware Planning ............................................................................................................... 6-2
6.4 Activating Bandwidth Sharing of MBTS Multi-Mode Co-Transmission ......................................... 6-2
6.4.1 Prerequisites ......................................................................................................................... 6-2
6.4.2 Data Preparation................................................................................................................... 6-2
6.4.3 Precautions ........................................................................................................................... 6-9
6.4.4 Hardware Adjustment ........................................................................................................... 6-9
6.4.5 Feature Activation/Initial Configuration ............................................................................... 6-10
6.4.6 Activation Observation ........................................................................................................ 6-17
6.5 Performance Optimization ........................................................................................................... 6-18
6.6 Troubleshooting ........................................................................................................................... 6-18
7 Parameters..................................................................................................................................7-1
8 Counters ......................................................................................................................................8-1
Issue 02 (2012-08-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
SingleRAN
Co-Transmission
Contents
9 Glossary ......................................................................................................................................9-1
10 Reference Documents .........................................................................................................10-1
Issue 02 (2012-08-30)

ii
SingleRAN
Co-Transmission
1 About This Document

1.1 Scope
This document describes the Bandwidth Sharing of MBTS Multi-Mode Co-Transmission feature,
including basic principles, feature dependencies, network impact, engineering guidelines, and
parameters. This feature uses IP-based co-transmission and applies to GU, GL, UL and GUL multi-mode
base stations.
Before reading this document, familiarize yourself with Transmission Resource Management Feature
Parameter Descriptionfor GBSS and WCDMA RAN and Transport Resource Management Feature
Parameter Description for eRAN.
In this document:
Multi-mode base transceiver station (MBTS) refers to a GU, GL, UL or GUL multi-mode base station.
Multi-mode base station controller (MBSC) refers to a GU dual-mode base station controller.
BTS, NodeB, and eNodeB refer to the GSM, UMTS, and LTE modes of an MBTS, respectively.
1.2 Intended Audience

This document is intended for:
Personnel who are familiar with LTE, UMTS, and GSM basics
Personnel who need to understand the Bandwidth Sharing of MBTS Multi-Mode Co-Transmission
feature
Personnel who work with Huawei MBTS 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:
Feature change: refers to a change in the Bandwidth Sharing of MBTS Multi-Mode Co-Transmission
feature of a specific product version
Editorial change: refers to a change in wording or the addition of information that was not described in
the earlier version
Document Issues
The document issue is as follows:
02 (2012-08-30)
01 (2012-04-30)
Draft A (2012-02-15)
02 (2012-08-30)
This is the second commercial release of SRAN7.0.
Compared with 01 (2012-04-30) of SRAN7.0, 02 (2012-08-30) of SRAN7.0 incorporates changes as
follows.
Issue 02 (2012-08-30)

1-1
SingleRAN
Co-Transmission
Change
Type
Change Description
Parameter Change
Feature
change
None
None
Editorial
change
Modified contents related to how to set

DSCP values for NodeB service ,see
section 3.3 "Transmission Priority."
None
01 (2012-04-30)
This is the first commercial release of SRAN7.0
Compared with draft A (2012-02-15) of SRAN7.0, 01 (2012-04-30) of SRAN7.0 incorporates no changes.
Draft A (2012-02-15)
This is the draft.
Compared with issue 01 (2011-03-30) of SRAN6.0, this issue incorporates the changes described in the
following table.
Change
Type
Change Description
Parameter Change
Feature
change
Added the optional feature MRFD-231505

Co-Transmission(eNodeB).
None
Editorial
change
Edited the document again for clarity and

readability purposes and optimized chapter
6 "Engineering Guidelines."
None
Issue 02 (2012-08-30)

1-2
SingleRAN
Co-Transmission
2 Overview
2 Overview
There is a wide margin for multiplexing transmission resources because peak load shifts between GSM,
UMTS, and LTE services. Operators can employ the GU, GL, or UL co-transmission solution to save
transmission resources. The solution, however, may cause resource congestion in the transport
network.
To address this possibility, Huawei introduced the feature Bandwidth Sharing of MBTS Multi-Mode
Co-Transmission. With this feature, a unified transmission resource management policy applies to the
BTS, NodeB, and eNodeB of an MBTS. The policy specifies the transmission priority of the BTS, NodeB,
and eNodeB and details flow control measurements.
When transmission resources become congested, this feature helps high-priority services proceed
without compromising user experience, prevents mutual impacts among GSM, UMTS, and LTE services,
and improves the utilization of transmission resources.
This feature imposes the following restrictions on the MBTS, MBSC, and core network (CN):
MBTS: Co-transmission with IP over FE/GE or with IP over E1/T1 is applied. Co-transmission can be
achieved in the following ways:
UTRP-based
co-transmission through panel interconnection
Main-control-board-based
UTRP-based
co-transmission through panel interconnection
co-transmission through backplane interconnection
Main-control-board-based
co-transmission through backplane interconnection
MBSC: Co-transmission with IP over FE/GE or with IP over E1/T1 is applied, and the Abis and Iub
interfaces are deployed.
CN: Co-transmission with IP over FE/GE is applied to the mobility management entity (MME) or
serving gateway (S-GW).
When the Common Transmission feature is activated on an MBTS, each mode has an independent algorithm to manage
its own transmission resources. For transmission resource management on a BTS or NodeB, see Transmission Resource
Management Feature Parameter Description for GBSS and WCDMA RAN. For transmission resource management on an
eNodeB, see Transport Resource Management Feature Parameter Description for eRAN.
This document is only in reference to transmission resource congestion in the uplink.
This document describes the following optional features:
MRFD-211505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(GBTS)
MRFD-221505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NodeB)
MRFD-231505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(eNodeB)
Issue 02 (2012-08-30)

2-1
SingleRAN
Co-Transmission
3 Technical Description
3.1 Transmission Resource Scheduling and QoS Management
To prevent transmission resource congestion, the Bandwidth Sharing of MBTS Multi-Mode
Co-Transmission feature schedules transmission resources for non-real-time services but preferentially
forwards IP packets for high-priority services.
During the early stage of network deployment, operators must ensure that the minimum bandwidth of
transmission devices in the transport network is higher than the total bandwidth of all MBTSs in the live
network.
This feature takes effect only when the transport network supports quality of service (QoS) management.
QoS management is supported only when the following conditions are met:
Layer-3 devices support DSCP-priority-based QoS management. DSCP stands for differentiated
services code point.
Layer-2 devices support VLAN-priority-based QoS management. VLAN stands for virtual local area
network.
Transmission devices support the PQ+WRR queue scheduling function, and at least two PQ queues
are supported. PQ stands for priority queue and WRR stands for weighted round robin.
3.2 Transmission Resource Allocation

There is a low probability of transmission resource congestion of non-real-time services in the uplink
because of relatively low traffic in the downlink and sufficient bandwidth resources in the uplink.
With the common transmission function activated on an MBTS, the co-transmission port transmits and
receives MBTS data. Some of the data is "local" data designated for the mode managing the port. The
other data is "bypass" data which is designated for the other modes or designated for cascaded base
stations. By applying traffic shaping to the port, the MBTS centrally manages the local and bypass data.
If the port is located on the BTS, operators can run the SET BTSLR command and set CIR to limit the
BTS bandwidth.
If the port is located on the NodeB or eNodeB, operators can run the SET LR command and set CIR to
limit the NodeB or eNodeB bandwidth.
The SET BTSLR command is available only in SRAN7.0 and later versions.
3.3 Transmission Priority

DSCP
Differentiated Services (DiffServ) uses a 6-bit DSCP field in an IP packet header for packet classification.
On a transmission path that an IP packet travels, each router can read the DSCP field in the packet's
header. Based on the DSCP value, layer-3 devices can implement DiffServ.
Based on QoS requirements of each specific service, an MBTS or MBSC classifies IP packets, controls
traffic, and sets the DSCP field value for each IP packet.
From the DSCP value, transmission devices in the transport network learn the traffic class and related
QoS requirements and perform per-hop behavior (PHB) accordingly. PHB includes transmission
resource allocation, queue scheduling, and packet discarding.
Issue 02 (2012-08-30)

3-1
SingleRAN
Co-Transmission
Note that all the DiffServ-aware devices in the transport network perform PHB based on DSCP values.
To set the mapping between signaling or traffic classes and DSCP values, operators can run the
commands listed in the following table.
NE
Command
To Set
BTS
SET BTSVLAN
Mapping between signaling or traffic classes and

DSCP values
SET DIFPRI
Mapping between signaling and DSCP values

Note that the mapping between the service calsses
and DSCP values cannot be configured on the
NodeB side. To configure the mapping, run the
ADD TRMMAP and SET PHBMAP command on
the RNC side.
NodeB
eNodeB
SET DIFPRI
Mapping between signaling or traffic classes and

DSCP values
MBSC
ADD TRMMAP and SET PHBMAP
Mapping between traffic classes and DSCP values

(Note that the MBTS,MBSC and CN must have the
same mapping between traffic classes and DSCP
values.)
VLAN Priority
The VLAN tag in a frame defines an IP packet's VLAN priority. Based on the VLAN priority, layer-2
devices can implement DiffServ.
Table 3-1 provides the mapping between DSCP values and VLAN priorities for MBTSs.
Table 3-1 Mapping between DSCP values and VLAN priorities for MBTSs
DSCP Value
VLAN Priority
0-7
8-15
16-23
24-31
32-39
40-47
48-55
56-63
Issue 02 (2012-08-30)

3-2
SingleRAN
Co-Transmission
Queue Priority
Queue priority defines the scheduling priority of a queue. Each IP port has eight queues, Queue 1 to
Queue 8, arranged in descending order of scheduling priority. The MBTS puts different service data into
different queues to implement DiffServ.
Table 3-2 provides the mapping between DSCP values/queues and queue priorities for GSM and UMTS
services. Table 3-3 provides the mapping between DSCP values/queues and queue priorities for LTE
services.
Table 3-2 Mapping between DSCP values/queues and queue priorities for GSM and UMTS services
DSCP Value
Queue
Queue Priority
40-63
PQ1
Reserved
PQ2
Reserved
PQ3
32-39
WFQ4
24-31
WFQ5
16-23
WFQ6
8-15
WFQ7
0-7
WFQ8
Table 3-3 Mapping between DSCP values/queues and queue priorities for LTE services
DSCP Value
Queue
Queue Priority
46-63
PQ1
34-45
PQ2
26-33
PQ3
18-25
WFQ4
10-17 (excluding
14)
WFQ5
0-9
WFQ6
Unused
WFQ7
14 (for FTP
services only)
WFQ8
3.4 Load Control

Load control includes the following functions:
Admission control: helps prevent transmission resource congestion, packet discarding, and excessive
admissions caused by retransmission on convergence nodes, ensuring quality of ongoing services.
Issue 02 (2012-08-30)

3-3
SingleRAN
Co-Transmission
Load reshuffling: helps reduce MBTS load, improve the admission rate, and increase system capacity.
Overload control: helps quickly reduce MBTS load and alleviate the impact of high-priority users
processing a large amount of data.
The load control function takes effect on all modes of an MBTS where Common Transmission is
activated. The related base station controller controls BTS and NodeB load while the eNodeB controls its
own load. The base station controller and eNodeB manage the local data only.
For details about BTS and NodeB load control, see Transmission Resource Management Feature
Parameter Description for GBSS and WCDMA RAN. For details about eNodeB load control, see
Transport Resource Management Feature Parameter Description for eRAN.
3.5 Flow Control

The BTS does not support the flow control function.
The flow control function on a NodeB is implemented by the Transport Dynamic Flow Control Algorithm,
which calculates delay, detects packet discarding, and performs traffic shaping based on available
bandwidth resources. This algorithm helps prevent packet discard caused by Iub interface congestion.
This algorithm takes effect only on HSDPA and HSUPA services, and it includes the uplink bandwidth
adaptive adjustment algorithm and the HSDPA adaptive flow control algorithm. The latter two algorithms
are controlled by two switches on the NodeB.
For details about the two algorithms, see Transmission Resource Management Feature Parameter
Description for GBSS and WCDMA RAN.
On an eNodeB, the flow control function is disabled by default. To enable the function, operators must
use a Huawei MME or S-GW and set parameters associated with the function.
Table 3-4 provides recommended settings for the two algorithms in different scenarios.
Table 3-4 Recommended settings for the two algorithms in different scenarios
Usage Scenario
Uplink Bandwidth Adaptive

Adjustment Algorithm
HSDPA Adaptive Flow Control

Algorithm
GU
co-transmission
Activated
Activated
GL
co-transmission
N/A
N/A
Deactivated
Activated.
UL
co-transmission
Deactivated, if transmission
devices do not support PQ+WRR
queue scheduling.
Deactivated
GUL
co-transmission
Issue 02 (2012-08-30)
Activated
Deactivated, if transmission
devices do not support PQ+WRR
queue scheduling.

3-4
SingleRAN
Co-Transmission
4 Related Features
4 Related Features
4.1 Required Features
Bandwidth sharing for MBTSs in common transmission depends on the following features:
MRFD-211501 IP-Based Multi-mode Co-Transmission on BS side(GBTS)
MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side(NodeB)
MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)
4.2 Mutually Exclusive Features

None.
4.3 Affected Features

None.
Issue 02 (2012-08-30)

4-1
SingleRAN
Co-Transmission
5 Impact on the Network
5 Impact on the Network

5.1 System Capacity
This feature has no impact on system capacity.
5.2 Network Performance

If 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:
Increase the service congestion rate.
Decrease the data rate of low-priority services, for example, best effort (BE) services.
Increase the packet loss rate of low-priority services.
Issue 02 (2012-08-30)

5-1
SingleRAN
Co-Transmission
6 Engineering Guidelines
6.1 When to Use Bandwidth Sharing of MBTS Multi-Mode
Co-Transmission
It is recommended that the Bandwidth Sharing of MBTS Multi-Mode Co-Transmission feature be
activated on an MBTS where IP-based co-transmission is applied.
6.2 Information to Be Collected

The information to be collected is transport network topology and bandwidth plan (bandwidth resources
available for the transport network).
6.3 Network Planning

This section describes planning activities you need to complete before you implement the feature.
6.3.1 RF Planning
RF planning is not applicable for this feature.
6.3.2 Network Topology

Transmission Bandwidth Planning
Based on the service plan and bandwidth requirements, make a transmission bandwidth plan each for
the BTS, NodeB, and eNodeB of an MBTS.
QoS Planning for Services

When GU, GL, UL, or GUL co-transmission is applied, it is recommended that signaling and circuit
switched (CS) services be classified as real-time services and packet switched (PS) services as
non-real-time services.
Set real-time services to a higher priority than non-real-time services to ensure the continuity of signaling
and CS services when transmission resources become congested.
Activate the Transport Dynamic Flow Control Algorithm feature to allow it to properly allocate
transmission resources across non-real-time services when transmission resources become congested.
Traffic Class and Transmission Priority Mapping

Based on the QoS plan of services, plan traffic classes, DSCP values, VLAN priorities, and the mapping
between traffic classes and DSCP values.
QoS Planning for the Transport Network

Based on service priorities, plan DSCP values VLAN priorities, and the number of PQ queues for layer-3
and layer-2 devices.
Bandwidth Planning for the Transport Network

Make a bandwidth plan for the transport network based on services' bandwidth requirements and
available bandwidth resources.
Issue 02 (2012-08-30)

6-1
SingleRAN
Co-Transmission
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.
6.3.3 Hardware Planning

N/A
6.4 Activating Bandwidth Sharing of MBTS Multi-Mode

Co-Transmission
6.4.1 Prerequisites
Requirements for other features

If
the BTS provides a co-transmission port, the MRFD-231501 IP-Based Multi-mode

Co-Transmission on BS side(BTS) feature must be activated on the BTS.
If
the NodeB provides a co-transmission port, the MRFD-211501 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-221501 IP-Based Multi-mode

Co-Transmission on BS side(eNodeB) feature must be activated on the eNodeB.
Requirements for License

One of the license control items listed in Table 6-1 must have been activated as required.
Table 6-1 License control items

NE
License Control Item
Abbreviation
Code
Sales Unit
GBTS
Bandwidth sharing of MBTS

Multi-mode Co-Transmission (BTS)
LGMIBSMCT
82201896
Per BTS
NodeB

Multi-mode
Co-Transmission(NodeB)
LQW9MBTSTR
01
82201908
Per NodeB
eNodeB

Multi-mode Co-Transmission
LLT1BSMCT01
81201732
Per eNodeB
6.4.2 Data Preparation

Transmission Bandwidth
If the BTS provides a co-transmission port and GU, GL, or GUL co-transmission is applied, set the key
parameters related to traffic shaping as follows:
MO
MML
Parameter
Name
MML
Parameter
ID
CME Parameter Name
Setting Description
Data
Source
BTSLR
UL
Committed
Information
Rate
CIR
UL Committed
Information Rate
Set this parameter to the

amount of bandwidth
available for the
transport network.
Network
plan
Issue 02 (2012-08-30)

6-2
SingleRAN
Co-Transmission
MO
MML
Parameter
Name
MML
Parameter
ID
CME Parameter Name
Setting Description
Data
Source
Committed
Burst Size
CBS
Committed Burst Size
Set this parameter to the

CIR value multiplied by
2, but ensure that the
product is not larger than
1000.
Network
plan
Excessive
Burst Size
EBS
Excessive Burst Size
If the CIR value is

smaller than 500, set
EBS to 0. If the CIR
value is larger than 500,
set CBS to 1000 and
ensure that the sum of
CBS and EBS is twice
the CIR value.
Network
plan
If the NodeB provides a co-transmission port and GU, UL, or GUL co-transmission is applied, set the key
parameters related to traffic shaping as follows:
MO
MML
Parameter
Name
MML
Parameter
ID
CME Parameter
Name
Setting Description
Data Source
LR
UL Committed
Information Rate
CIR
UL Committed
Information Rate
Set this parameter to

the amount of
bandwidth available for
the transport network.
Network plan
Committed Burst
Size
CBS
Committed Burst
Size

the CIR value
multiplied by 2, but
ensure that the product
is not larger than 1000.
Network plan
Excessive Burst
Size
EBS
Excessive Burst
Size
If the CIR value is

smaller than 500, set
EBS to 0. If the CIR
value is larger than
500, set CBS to 1000
and ensure that the
sum of CBS and EBS
is twice the CIR value.
Network plan
If the eNodeB provides a co-transmission port and GL, UL, or GUL co-transmission is applied, set the
key parameters related to traffic shaping as follows:
Issue 02 (2012-08-30)

6-3
SingleRAN
Co-Transmission
MO
MML Parameter
Name
MML
Parameter
ID
Setting Description
Data
Source
LR
UL Committed
Information Rate
CIR
Set this parameter to the amount of

bandwidth available for the
transport network.
Network
plan
Committed Burst
Size
CBS
Set this parameter to the CIR value

multiplied by 2, but ensure that the
product is not larger than 1000.
Network
plan
Excessive Burst
Size
EBS
If the CIR value is smaller than 500,

set EBS to 0. If the CIR value is
larger than 500, set CBS to 1000
and ensure that the sum of CBS
and EBS is twice the CIR value.
Network
plan
When GU, GL, or GUL co-transmission is applied, set the bandwidth for the BTS logical port on the BSC
side as follows:
MO
MML
Parameter
Name
MML
Parameter
ID
CME Parameter
Name
Setting Description
Data
Source
IPLOGICPORT
Logic Port
No.
LPN
Logic Port No.
Number of the BTS

logical port
Network
plan
Bandwidth
CIR
Bandwidth
Bandwidth of the BTS

logical port
Network
plan
Transport QoS
Table 6-2 provides the transmission resource mapping (TRMMAP) between GSM/UMTS traffic classes
and DSCP values when GU co-transmission is applied.
Table 6-2 TRMMAP between GSM/UMTS traffic classes and DSCP values
NE
Traffic Class
DSCP Value
GBTS
ESL/OML/RSL
48
CS Voice
46
CS Data/PS High PRI
34
PS Low PRI
26
IP Clock
46
EML
18
Iub Signal
48
CCH&SRB&AMR
46
NodeB
Issue 02 (2012-08-30)

6-4
SingleRAN
Co-Transmission
NE
Traffic Class
DSCP Value
Conversational & Streaming
34
R99 interactive & background
18
HSxPA interactive & background
10
OM High
46
OM Low
18
IP Clock
46
Table 6-3 provides the TRMMAP between GSM/LTE traffic classes and DSCP values when GL
co-transmission is applied.
Table 6-3 TRMMAP between GSM/LTE traffic classes and DSCP values
NE
Traffic Class
DSCP Value
GBTS
ESL/OML/RSL
48
CS Voice
46
CS Data/PS High PRI
34
PS Low PRI
26
IP Clock
46
EML
18
SCTP
48
QCI1
46
QCI2
26
QCI3
34
QCI4
26
QCI5
46
QCI6
18
QCI7
18
QCI8
10
QCI9
OM High
46
OM Low
18
IP Clock
46
eNodeB
Issue 02 (2012-08-30)

6-5
SingleRAN
Co-Transmission
Table 6-4 provides the TRMMAP between UMTS/LTE traffic classes and DSCP values when UL
Table 6-4 TRMMAP between UMTS/LTE traffic classes and DSCP values
NE
Traffic Class
DSCP Value
NodeB
Iub Signal
48
CCH & SRB & AMR
46
34
18
10
OM High
46
OM Low
18
IP Clock
46
SCTP
48
QCI1
46
QCI2
26
QCI3
34
QCI4
26
QCI5
46
QCI6
18
QCI7
18
QCI8
10
QCI9
OM High
46
OM Low
18
IP Clock
46
eNodeB
Table 6-5 provides the TRMMAP between GSM/UMTS/LTE traffic classes and DSCP values when GUL
Table 6-5 TRMMAP between GSM/UMTS/LTE traffic classes and DSCP values
NE
Traffic Class
DSCP Value
GBTS
ESL/OML/RSL
48
CS Voice
46
CS Data/PS High PRI
34
Issue 02 (2012-08-30)

6-6
SingleRAN
Co-Transmission
NE
NodeB
eNodeB
Traffic Class
DSCP Value
PS Low PRI
26
IP Clock
46
EML
18
Iub Signal
48
CCH & SRB & AMR
46
34
18
10
OM High
46
OM Low
18
IP Clock
46
SCTP
48
QCI1
46
QCI2
26
QCI3
34
QCI4
26
QCI5
46
QCI6
18
QCI7
18
QCI8
10
QCI9
OM High
46
OM Low
18
IP Clock
46
It is recommended that the preceding TRMMAP be concerned when setting DSCP values.
If the eNodeB provides a co-transmission port, the OMTCSW switch in the SET RSCGRPALG command must be
turned on. Otherwise, backpressure cannot be performed on services whose data is put into the same queue as the OM
FTP service whose traffic class is OM low when transmission resources are congested. FTP stands for File Transfer
Protocol.
Table 6-6 provides the recommended settings for the key parameters related to the TRMMAP of the
BTS.
Issue 02 (2012-08-30)

6-7
SingleRAN
Co-Transmission
Table 6-6 Recommended settings for the key parameters related to the TRMMAP of the BTS
MO
MML
Parameter
Name
MML
Parameter ID
CME Parameter
Name
Setting Description
Data
Source
BTSVLAN
Service
Type
SERVICETYPE
Service Type
DSCP
DSCP
DSCP
If GU
co-transmission is
applied, set the
parameters based
on the settings
provided in Table
6-2.
Negotiation
with the
peer
If GL
co-transmission is
applied, set the
parameters based
on the settings
provided in Table
6-3.
If GUL
co-transmission is
applied, set the
parameters based
on the settings
provided in Table
6-5.
NodeB.
Table 6-7 Recommended settings for the key parameters related to the TRMMAP of the NodeB
MO
MML
Parameter
Name
MML
Parameter
ID
CME Parameter
Name
Setting Description
Data
Source
DIFPRI
Priority
Rule
PRIRULE
Priority Rule

DSCP.
Signaling
Priority
SIGPRI
Signaling Priority
OM High
Priority
OMHPRI
OM High Priority
If GU co-transmission
is applied, set the
parameter based on
the settings provided
in Table 6-2.
Negotiation
with the
peer
OM Low
Priority
OMLPRI
OM Low Priority
Issue 02 (2012-08-30)
If UL co-transmission
is applied, set the

6-8
SingleRAN
Co-Transmission
MO
MML
Parameter
Name
MML
Parameter
ID
CME Parameter
Name
Setting Description
PTP
Priority
PTPPRI
PTP Priority
parameter based on
in Table 6-4.
Data
Source
If GUL
co-transmission is
applied, set the
parameter based on
in Table 6-5.
eNodeB.
Table 6-8 Recommended settings for the key parameters related to the TRMMAP of the eNodeB
MO
MML
Parameter
Name
MML
Parameter
ID
CME Parameter
Name
Setting Description
Data
Source
DIFPRI
Priority Rule
PRIRULE
Priority Rule

DSCP.
Signaling
Priority
SIGPRI
Signaling Priority
OM High
Priority
OMHIGHPRI
OM High Priority
If GL co-transmission
is applied, set the
parameter based on
in Table 6-3.
Negotiation
with the
peer
OM Low
Priority
OMLOWPRI
OM Low Priority
IP Clock
Priority
PTPPRI
IP Clock Priority
User Data 1
Priority~User
Data 9
Priority
DT1PRI~
DT9PRI
User Data 1
Priority~User Data 9
Priority
If UL co-transmission
is applied, set the
parameter by
referring to Table
6-4.
If GUL
co-transmission is
applied, set the
parameter by
referring to Table
6-5.
6.4.3 Precautions
None.
6.4.4 Hardware Adjustment

N/A
Issue 02 (2012-08-30)

6-9
SingleRAN
Co-Transmission
6.4.5 Feature Activation/Initial Configuration

It is recommended that a logical port be configured for the Abis interface to improve feature performance
when GU, GL, or GUL co-transmission is applied.
The data items listed in Table 6-9 are related to the logical port and must be set before feature activation.
Note that the values listed in this table are used in the follow-up feature activation procedures.
Table 6-9 Data items that must be set before feature activation
Data Item
Sample Value
Remarks
Available
Transmission
Bandwidth
20 Mbit/s
Available bandwidth between a

base station and a base station
controller
Bandwidth of the
BTS Logic Port
10 Mbit/s
Calculate the bandwidth for this

port based on the traffic model of
the MBTS. If the MBTS
bandwidth has an upper limit
and this upper limit is lower than
the calculation result, then set
this data item to this upper limit.
BTS Index
None
Logic IP Address of
the BTS
16.16.90.201
None
Port IP Address of
the BSC
172.16.140.140
None
In an MBTS, co-transmission can be achieved through a UTRP or main control board. In the follow-up
feature activation procedures, co-transmission is achieved through a main control board, and therefore
the main control board is configured with the logic IP address of the BTS.
GU Co-Transmission
Step 1 Set the parameters related to traffic shaping on the MBTS.
If the BTS provides a co-transmission port, run the BSC6900 MML command SET BTSLR to limit the
bandwidth over the port(CME: "Root > BTS tranmission link > BTS Line Rate"). The following is an
example:
SET BTSLR: IDTYPE=BYID, BTSID=1, CN=0, SRN=0, SN=6, PT=ETHPORT, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000,
EBS=0;
If the NodeB provides a co-transmission port, run the NodeB MML command SET LR to limit the
bandwidth over the port. (CME: "Main View > Right-click a site> IP Transport Layer > Feature
Configuration > LimitRate") The following is an example:
SET LR: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000, EBS=0;
Step 2 Add an IP logical port to the Abis interface on the MBSC.

1. Run the BSC6900 MML command ADD IPLOGICPORT to add an IP logical port to the Abis interface.
(CME:"Transmission View > GSM > Abis > IP Transport > IP Logical Port" )The following is an
example:
Issue 02 (2012-08-30)

6-10
SingleRAN
Co-Transmission
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 IP logical port is numbered 1, and the bandwidth of the port is the CIR value multiplied by 64,
that is, 10048 kbit/s.
2. Run the BSC6900 MML command SET BTSIP to bind the newly added IP logical port and the MBTS
together. (CME: "Root > BTS tranmission link > BTS Line Rate > IP BTS Communication
Address") The following is an example:
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 BYID value indicates that the MBTS is located by its base station index.
Step 3 Configure a TRMMAP for the MBSC, as described in Table 6-2.

1. Run the BSC6900 MML command ADD TRMMAP to create a TRMMAP for Iub signaling and Iub
service data.(CME:"Transmission View > UMTS > RNC > Transport Resource Mapping") The
following is an example:
ADD
TRMMAP:TMI=110,ITFT=IUB,TRANST=IP,CCHPRIPATH=EF,SIPPRIPATH=EF,SRBPRIPATH=EF,VOICEPRIPATH=EF,CSCONVPRI
PATH=AF41,CSSTRMPRIPATH=AF41,PSCONVPRIPATH=AF41,PSSTRMPRIPATH=AF41,PSINTHGHPRIPATH=AF21,PSINTLOWPRIPA
TH=AF21,PSBKGPRIPATH=AF21,HDSRBPRIPATH=EF,HDSIPPRIPATH=EF,HDVOICEPRIPATH=EF,HDCONVPRIPATH=AF41,HDSTRM
PRIPATH=AF41,HDINTHGHPRIPATH=AF11,HDINTMIDPRIPATH=AF11,HDINTLOWPRIPATH=AF11,HDBKGPRIPATH=AF11,HUSRBPR
IPATH=EF,HUSIPPRIPATH=EF,HUVOICEPRIPATH=EF,HUCONVPRIPATH=AF41,HUSTRMPRIPATH=AF41,HUINTHGHPRIPATH=AF11
,HUINTMIDPRIPATH=AF11,HUINTLOWPRIPATH=AF11,HUBKGPRIPATH=AF11;
2. Run the BSC6900 MML command ADD TRMMAP to create a TRMMAP for Abis service data.
(CME:"Transmission View > GSM > BSC > Transport Resource Mapping") The following is an
example:
ADD
TRMMAP:TMI=111,ITFT=ABIS,TRANST=IP,CSVOICEPATH=EF,CSDATAPATH=AF41,PSHPRIDATAPATH=AF41,PSLPRIDATAPATH=
AF31;
3. Run the BSC6900 MML command SET BSCABISPRIMAP to create a TRMMAP for Abis signaling.
(CME: "Root > BTS tranmission link > BSC Side Aibs Priority Mapping")The following is an
example:
SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=1, TRANSTYPE=IP, OMLDSCP=48, RSLDSCP=48, EMLDSCP=18, ESLDSCP=48;
4. Run the BSC6900 MML command ADD ADJMAP to add a TRMMAP index to the Iub interface.
(CME:"Transmission View>UMTS > lub > IP Transport > Adjacent Node Mapping") The following
is an example:
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110, TMIBRZ=110, FTI=1;
5. Run the BSC6900 MML command ADD ADJMAP to add a TRMMAP index to the Abis interface.
(CME:"Transmission View>GSM > Abis > IP Transport > Adjacent Node Mapping") The
ADD ADJMAP: ANI=3, ITFT=ABIS, TMIGLD=111, FTI=1;
Step 4 Create a TRMMAP for the MBTS.

1. Run the BSC6900 MML command SET BTSVLAN to set the mapping between signaling/service
data and DSCP values. (CME: "Root > BTS Extend Attributes> VLANID and VLAN Priority") The
following are examples:
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=OML, DSCP=48;
SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=RSL, DSCP=48;
Issue 02 (2012-08-30)

6-11
SingleRAN
Co-Transmission
SET
SET
SET
SET
SET
SET
SET
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
SERVICETYPE=EML, DSCP=18;
SERVICETYPE=ESL, DSCP=48;
SERVICETYPE= CSVOICE, DSCP=46;
SERVICETYPE= CSDATA, DSCP=34;
SERVICETYPE= PSHIGHPRI, DSCP=34;
SERVICETYPE= PSLOWPRI, DSCP=26;
SERVICETYPE= OTHERDATA, DSCP=46;
2. Run the NodeB MML command SET DIFPRI to set the mapping between signaling and DSCP values.
(CME: "Main View > Right-click a site> IP Transport Layer > Basic Configuration > IPQoS") The
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHPRI=46, OMLPRI=18, PTPPRI=46;
Step 5 Set the parameters related to the Transport Dynamic Flow Control Algorithm to prevent GSM
and UMTS packet loss, which may affect user experience.
1. Run the NodeB MML command ADD HSUPAFLOWCTRLRAPA to turn on the switches
BWPRTSWITCH, TNLCONGCTRLSWITCH, and BACKPRESSURESWITCH. (CME: "Main View >
Right-click a site> IP Transport Layer > Feature Configuration > HspaFlowCtrl") The following is
an example:
ADD HSUPAFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IPV4, PT=ETH, PN=0, BWPRTSWITCH=ON,
TNLCONGCTRLSWITCH=ON, BACKPRESSURESWITCH=ON;
2. Run the NodeB MML command ADD HSDPAFLOWCTRLRAPA and set the
BW_SHAPING_ONOFF_TOGGLE switch. (CME: "Main View > Right-click a site> IP Transport
Layer > Feature Configuration > HspaFlowCtrl") The following is an example:
ADD HSDPAFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IPV4, PT=ETH, PN=0,
SWITCH=BW_SHAPING_ONOFF_TOGGLE;
----End
GL Co-Transmission
bandwidth over the port. (CME: "Root > BTS tranmission link > BTS Line Rate") The following is an
example:
EBS=0;
If the eNodeB provides a co-transmission port:
1. Run the eNodeB MML command SET LR to limit the bandwidth over the port. (CME: "Root >
Transport > Link Layer Information >LR") The following is an example:
2. Run the eNodeB MML command ADD RSCGRP to add a transmission resource group. (CME:
"Root > Transport > Transport Layer Information > RSCGRP") The following is an example:
ADD RSCGRP: CN=0, SRN=0, SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=DEFAULTPORT, RU=KBPS,
TXBW=360000, RXBW=540000, TXCBS=360000, TXCIR=360000, RXCIR=540000, TXPIR=360000, RXPIR=540000,
TXPBS=360000;
3. Run the eNodeB MML command SET RSCGRPALG to turn on the OMTCSW switch. (CME: "Root >
Transport > Algorithm Information > RSCGRPALG") The following is an example:
SET RSCGRPALG: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=DEFAULTPORT, OMTCSW=ENABLE;
Step 2 Add a logical port to the Abis interface.
Issue 02 (2012-08-30)

6-12
SingleRAN
Co-Transmission
(CME:"Transmission View>GSM > Abis > IP Transport > IP Logical Port" ) The following is an
example:
In the preceding script, the IP logical port is numbered 1, and the bandwidth of the port is the CIR value multiplied by 64,
that is, 10048 kbit/s.

(CME:"Transmission View>GSM > BSC > Transport Resource Mapping") The following is an
example:
ADD
AF31;
(CME: "Root > BTS tranmission link > BSC Side Aibs Priority Mapping") The following is an example:
3. Run the BSC6900 MML command ADD ADJMAP to add a TRMMAP to the Abis interface.

SET
SET
SET
SET
SET
SET
SET
SET
SET
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
SERVICETYPE=OML, DSCP=48;
SERVICETYPE=RSL, DSCP=48;
SERVICETYPE= CSDATA, DSCP=34;
SERVICETYPE= PSHIGHPRI, DSCP=34;
SERVICETYPE= PSLOWPRI, DSCP=26;
SERVICETYPE= OTHERDATA, DSCP=46;
2. Run the eNodeB MML command SET DIFPRI to set the mapping between signaling/service data and
DSCP values. (CME: "Root > Transport > Transport Layer Information >DIFPRI") The following is
an example:
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, PTPPRI=46, DT1PRI=46, DT2PRI=26, DT3PRI=34,
DT4PRI=26, DT5PRI=46, DT6PRI=18, DT7PRI=18, DT8PRI=10, DT9PRI=0;
Issue 02 (2012-08-30)

6-13
SingleRAN
Co-Transmission
----End
UL Co-Transmission
TXPBS=360000;

service data. (CME:"Transmission View > UMTS > RNC > Transport Resource Mapping") The
ADD
2. Run the BSC6900 MML command ADD ADJMAP to add a TRMMAP to the Iub interface.
(CME:"Transmission View > UMTS > lub > IP Transport > Adjacent Node Mapping ") The

an example:
Issue 02 (2012-08-30)

6-14
SingleRAN
Co-Transmission
Step 4 Set the parameters related to the Transport Dynamic Flow Control Algorithm to prevent UMTS
services from preempting transmission resources allocated to LTE services when transmission
resource congestion occurs.
1. Run the NodeB MML command ADD HSUPAFLOWCTRLRAPA to turn on the BWPRTSWITCH and
BACKPRESSURESWITCH switches and turn off the TNLCONGCTRLSWITCH switch. (CME: "Main
View > Right-click a site> IP Transport Layer > Feature Configuration > HspaFlowCtrl") The
TNLCONGCTRLSWITCH=OFF, BACKPRESSURESWITCH=ON;
----End
GUL Co-Transmission
bandwidth over the port. (CME: "Root > BTS tranmission link > BTS Line Rate") The following is an
example:
EBS=0;
TXPBS=360000;
Step 2 Add a logical port to the MBSC.

(CME:"Transmission View>GSM > Abis > IP Transport > IP Logical Port" ) The following is an
example:
Issue 02 (2012-08-30)

6-15
SingleRAN
Co-Transmission
In the preceding script, the IP logical port is numbered 1, and the bandwidth of the port is the CIR value
multiplied by 64, that is, 10048 kbit/s.

service data. (CME:"Transmission View>UMTS > RNC > Transport Resource Mapping") The
ADD
(CME:"Transmission View>GSM > BSC > Transport Resource Mapping") The following is an
example:
ADD
AF31;
(CME: "Root > BTS tranmission link > BSC Side Aibs Priority Mapping") The following is an
example:
4. Run the BSC6900 MML command ADD ADJMAP to add a TRMMAP to the Iub interface.
(CME:"Transmission View>UMTS > lub > IP Transport > Adjacent Node Mapping ")The following
is an example:
5. Run the BSC6900 MML command ADD ADJMAP to add a TRMMAP to the Abis interface.

SET
SET
SET
SET
SET
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
Issue 02 (2012-08-30)
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
SERVICETYPE=OML, DSCP=48;
SERVICETYPE=RSL, DSCP=48;

6-16
SingleRAN
Co-Transmission
SET
SET
SET
SET
BTSVLAN:
BTSVLAN:
BTSVLAN:
BTSVLAN:
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
BTSID=1,
BTSID=1,
BTSID=1,
BTSID=1,
SERVICETYPE=
SERVICETYPE=
SERVICETYPE=
SERVICETYPE=
CSDATA, DSCP=34;
PSHIGHPRI, DSCP=34;
PSLOWPRI, DSCP=26;
OTHERDATA, DSCP=46;
an example:
Step 5 Set the parameters related to the Transport Dynamic Flow Control Algorithm to prevent UMTS
services from preempting transmission resources allocated to LTE services when transmission
resource congestion occurs.
1. Run the NodeB MML command ADD HSUPAFLOWCTRLRAPA to turn on the BWPRTSWITCH and
BACKPRESSURESWITCH switches and turn off the TNLCONGCTRLSWITCH switch. (CME: "Main
View > Right-click a site> IP Transport Layer > Feature Configuration > HspaFlowCtrl") The
TNLCONGCTRLSWITCH=OFF, BACKPRESSURESWITCH=ON;
----End
6.4.6 Activation Observation

After the Bandwidth Sharing of MBTS Multi-Mode Co-Transmission feature is activated, check whether
UEs can properly process CS and PS services when transmission resource congestion occurs.
If yes, the feature is activated.
If no, the feature failed to be activated.
Perform the following steps to determine whether the feature is activated:
If the BTS 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 Log in to the BSC local maintenance terminal (LMT), and choose Monitor > GSM Monitoring >
BTS IP Link Performance Monitoring.
Step 3 Initiate a GSM or UMTS CS service after the traffic volume approaches the bandwidth available
for the transport network.
Step 4 Terminate the CS service if the service is successfully set up and the voice is clear.
Issue 02 (2012-08-30)

6-17
SingleRAN
Co-Transmission
Step 5 Initiate a GSM PS service, connect a personal computer (PC) to the MBTS, and use DU Meter
on the PC to check whether the GSM PS service is successfully set up and the data rate is
stable.
If
yes, the feature is activated.
If
no, the feature failed to be activated.
----End
If the NodeB 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 Log in to the RNC LMT, and choose Monitor > UMTS Monitoring > Connector Performance
Monitoring > UL Throughput Bandwidth.
Step 5 Initiate a GSM PS service, connect a PC to the MBTS, and use DU Meter on the PC to check
whether the GSM PS service is successfully set up and the data rate is stable.
If
If
----End
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 Log in to the eNodeB LMT, and choose Monitor > Transport Performance Monitoring.
Step 5 Initiate a GSM PS service, connect a PC to the MBTS, and use DU Meter on the PC to check
whether the GSM PS service is successfully set up and the data rate is stable.
If
If
----End
6.5 Performance Optimization

None.
6.6 Troubleshooting
If bandwidth resources across all modes of an MBTS are inappropriately allocated, reallocate the
bandwidth resources based on the traffic model.
Issue 02 (2012-08-30)

6-18
SingleRAN
Co-Transmission
7 Parameters
7 Parameters
Table 7-1 Parameter description
Parameter ID
NE
MML Command
Feature ID
None
BACKPRESSURESW NodeB ADD
ITCH
HSUPAFLOWCTRL
PARA
Feature
Name
Description
None
Meaning:Indicates
whether to perform UL
reverse pressure.
When this switch is
turned on, the BS
performs reverse
pressure on the air
interface to lower the
UE transmit rate if the
buffer of the egress port
exceeds the specified
threshold.
SET
HSUPAFLOWCTRL
PARA
GUI Value
Range:OFF(Off),
ON(On)
Actual Value
Range:OFF, ON
Unit:None
Default Value:ON(On)
BWPRTSWITCH
NodeB ADD
WRFD-01069 HSUPA FDE Meaning:Indicates
HSUPAFLOWCTRL 2
whether to adjust the
PARA
available UL bandwidth.
When this parameter is
SET
set to ON, the BS stops
HSUPAFLOWCTRL
adjusting the available
PARA
UL bandwidth of the
physical port if the bit
error rate (BER) on the
transmission line
exceeds the specified
alarm threshold. This
parameter does not
take effect for loopback
ports or tunnels
because the error MAC
frame reporting function
is not implemented for
loopback ports and
tunnels.
GUI Value
Range:OFF(Off),
ON(On)
Issue 02 (2012-08-30)

7-1
SingleRAN
Co-Transmission
Parameter ID
NE
MML Command
7 Parameters
Feature ID
Feature
Name
Description
Actual Value
Range:OFF, ON
Unit:None
CBS
NodeB SET LR
WRFD-05040 IP
Meaning:Indicates the
2
Transmission Committed Burst Size
Introduction (CBS) after rate
on Iub
limitation is configured
Interface
at a port.
GUI Value
Range:32~1000000
Actual Value
Range:32~1000000
Unit:Kbit
Default Value:None
CBS
BSC69 SET BTSLR

00
GBFD-11860 Abis over IP Meaning:Indicates the

1
committed burst size
after rate limitation is
configured at a port.
GUI Value
Range:32~1000000
Actual Value
Range:32~1000000
Unit:kbit
Default Value:None
CIR
NodeB SET LR
WRFD-01061 HSDPA Flow Meaning:Indicates the

010
Control
UL committed
information rate after
rate limitation is
GUI Value
Range:32~1000000
Actual Value
Range:32~1000000
Unit:Kbit/s
Default Value:None
CIR
Issue 02 (2012-08-30)
BSC69 SET BTSLR

7-2
SingleRAN
Co-Transmission
Parameter ID
NE
MML Command
00
7 Parameters
Feature ID
Feature
Name
Description
UL committed
information rate after
rate limitation is
GUI Value
Range:32~1000000
Actual Value
Range:32~1000000
Unit:kbit/s
Default Value:None
CIR
BSC69 ADD IPLOGICPORT GBFD-11860 IP QOS

Meaning:Bandwidth of
00
5
the logical port
MOD
Overbooking
IPLOGICPORT
WRFD-05040 on IP
GUI Value
8
Transmission Range:1~1562
Actual Value
Range:64~100000
Unit:64kbit/s
Default Value:None
DSCP
BSC69 SET BTSVLAN

00
GBFD-11860 IP QOS
5
Meaning:DSCP to be
contained in the header
of an IP packet.
According to this
parameter, the router
provides differentiated
services for packet
streams. The greater
the value of this
parameter, the higher
the service level. This
parameter is valid only
if the transport type is
set to IP.
GUI Value Range:0~63
Actual Value
Range:0~63
Unit:None
Default Value:0
EBS
Issue 02 (2012-08-30)
NodeB SET LR
WRFD-05040 IP
2
Transmission Excess Burst Size
Introduction (EBS) after rate

7-3
SingleRAN
Co-Transmission
Parameter ID
NE
MML Command
7 Parameters
Feature ID
Feature
Name
Description
on Iub
Interface
limitation is configured
at a port.
GUI Value
Range:0~1000000
Actual Value
Range:0~1000000
Unit:Kbit
Default Value:None
EBS
BSC69 SET BTSLR

00

1
excess burst size after
rate limitation is
GUI Value
Range:0~1000000
Actual Value
Range:0~1000000
Unit:kbit
Default Value:None
LPN
BSC69 ADD IPLOGICPORT MRFD-21150

00
2
MOD
IPLOGICPORT
RMV IPLOGICPORT
IP-Based
BSC and
RNC
Co-Transmis
sion on
MBSC Side
Meaning:Logical port
number. It is uniquely
numbered within the
active/standby boards.
GUI Value
Range:0~988;1024~15
35
Actual Value
Range:FG2a/GOUa/U
OIa(IP)
board:0~119;FG2d/FG
2c board:0~489,
512~767;GOUd/GOUc
board:0~499,
512~767;POUc(IP)
board:0~988,
1024~1535
Unit:None
Default Value:None
OMHPRI
Issue 02 (2012-08-30)
NodeB SET DIFPRI
None
None

priority of the high-level
OM data. The priority
7-4
SingleRAN
Co-Transmission
Parameter ID
NE
MML Command
7 Parameters
Feature ID
Feature
Name
Description
has a positive
correlation with the
value of this parameter.
The high-level OM data
includes the packets
related to remote
maintenance channel
switchover and DHCP
relay.
Actual Value
Range:0~63
Unit:None
Default Value:34
OMLPRI
NodeB SET DIFPRI
None
None
priority of the low-level
OM data, such as the
data to be uploaded or
downloaded. The
priority has a positive
correlation with the
value of this parameter.
The low-level OM data
includes the packets
related to File Transfer
Protocol (FTP).
Actual Value
Range:0~63
Unit:None
Default Value:22
PRIRULE
Issue 02 (2012-08-30)
NodeB SET DIFPRI
WRFD-05040 IP
2
Transmission rule for prioritizing
Introduction traffic to meet service
on Iub
requirements. If this
Interface
parameter is set to
IPPRECEDENCE, the
protocol stack of the
earlier version is
adopted, which firstly
converts types of
service (TOSs) to
DSCPs and then
prioritizes traffic.

7-5
SingleRAN
Co-Transmission
Parameter ID
NE
MML Command
7 Parameters
Feature ID
Feature
Name
Description
GUI Value
Range:IPPRECEDENC
E(IP Precedence),
DSCP(DSCP)
Actual Value
Range:IPPRECEDENC
E, DSCP
Unit:None
Default
Value:DSCP(DSCP)
PTPPRI
NodeB SET DIFPRI
WRFD-05040 IP
2
Transmission DSCP of the Precision
Introduction Time Protocol (PTP)
on Iub
packet. The priority has
Interface
a positive correlation
with the value of the
parameter. If the clock
that follows the Huawei
proprietary protocol is
used, the DSCP of the
protocol packet takes
effect, which is
permanently set to 63.
Actual Value
Range:0~63
Unit:None
Default Value:34
SERVICETYPE
BSC69 SET BTSVLAN

00
GBFD-11860 Abis over IP Meaning:Service type

1
of the BTS. The QoS
processing depends on
the DSCP, VLAN ID,
and VLAN priority that
vary according to the
service type.
GUI Value
Range:OML(OML),
RSL(RSL), EML(EML),
ESL(ESL),
CSVOICE(CS Voice),
CSDATA(CS Data),
PSHIGHPRI(PS High
PRI), PSLOWPRI(PS
Low PRI),
Issue 02 (2012-08-30)

7-6
SingleRAN
Co-Transmission
Parameter ID
NE
MML Command
7 Parameters
Feature ID
Feature
Name
Description
OTHERDATA(Other
Data)
Actual Value
Range:OML, RSL,
EML, ESL, CSVOICE,
CSDATA, PSHIGHPRI,
PSLOWPRI,
OTHERDATA
Unit:None
Default Value:None
SIGPRI
NodeB SET DIFPRI
WRFD-05040 IP
2
Transmission priority of signaling
Introduction data. This parameter
on Iub
value is the same as
Interface
the DSCP priority of the
common channel.A
larger value indicates a
higher priority.
Actual Value
Range:0~63
Unit:None
Default Value:48
None
TNLCONGCTRLSWI NodeB ADD
TCH
HSUPAFLOWCTRL
PARA
None
SET
HSUPAFLOWCTRL
PARA
Meaning:Indicates
whether to perform
congestion control.
When this switch is
turned on, the BS
lowers the TX rate if the
BS detects that links
experience
transmission delay or
packet loss.
GUI Value
Range:OFF(Off),
ON(On)
Actual Value
Range:OFF, ON
Unit:None
Issue 02 (2012-08-30)

7-7
SingleRAN
Co-Transmission
8 Counters
8 Counters
There are no specific counters associated with this feature.
Issue 02 (2012-08-30)

8-1
SingleRAN
Co-Transmission
9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 02 (2012-08-30)

9-1
SingleRAN
Co-Transmission
10 Reference Documents
10 Reference Documents
[1] Transmission Resource Management Feature Parameter Description for GBSS and WCDMA RAN.
[2] Transport Resource Management Feature Parameter Description for eRAN
Issue 02 (2012-08-30)

10-1

Bandwidth Sharing of MBTS Multi-Mode Co-Transmission (SRAN7.0 - 02)

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Bandwidth Sharing of MBTS Multi-Mode Co-Transmission (SRAN7.0 - 02)

Enviado por

Direitos autorais:

Formatos disponíveis

Bandwidth Sharing of MBTS Multi-Mode

Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

4 Related Features .......................................................................................................................4-1

5 Impact on the Network.............................................................................................................5-1

6 Engineering Guidelines ...........................................................................................................6-1

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1 About This Document

1 About This Document

1.2 Intended Audience

Personnel who work with Huawei MBTS products

1.3 Change History

Huawei Proprietary and Confidential

1 About This Document

Modified contents related to how to set

Added the optional feature MRFD-231505

Edited the document again for clarity and

Huawei Proprietary and Confidential

co-transmission through panel interconnection

co-transmission through panel interconnection

co-transmission through backplane interconnection

co-transmission through backplane interconnection

This document describes the following optional features:

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

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

MRFD-231505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(eNodeB)

Huawei Proprietary and Confidential

3.2 Transmission Resource Allocation

3.3 Transmission Priority

Huawei Proprietary and Confidential

Mapping between signaling or traffic classes and

Mapping between signaling and DSCP values

Mapping between signaling or traffic classes and

ADD TRMMAP and SET PHBMAP

Mapping between traffic classes and DSCP values

Huawei Proprietary and Confidential

3.4 Load Control

Huawei Proprietary and Confidential

3.5 Flow Control

Uplink Bandwidth Adaptive

HSDPA Adaptive Flow Control

Huawei Proprietary and Confidential

MRFD-211501 IP-Based Multi-mode Co-Transmission on BS side(GBTS)

MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side(NodeB)

MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB)

4.2 Mutually Exclusive Features

4.3 Affected Features

Huawei Proprietary and Confidential

5 Impact on the Network

5 Impact on the Network

5.2 Network Performance

Increase the service congestion rate.

Increase the packet loss rate of low-priority services.

Huawei Proprietary and Confidential

6.2 Information to Be Collected

6.3 Network Planning

6.3.2 Network Topology

QoS Planning for Services