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

8/18/2019 Bandwidth Sharing of MBTS Multi-Mode Co-Transmission(SRAN7.0_02)

1/41

Bandwidth Sharing of MBTS Multi-ModeCo-TransmissionSRAN7.0

Feature Parameter Description

Issue 02

Date 2012-08-30

HUAWEI TECHNOLOGIES CO., LTD.


2/41

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 orrepresentations 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: [email protected]

http://www.huawei.com/http://www.huawei.com/mailto:[email protected]:[email protected]:[email protected]://www.huawei.com/


3/41

SingleRAN

Bandwidth Sharing of MBTS Multi-Mode

Co-Transmission Contents

Issue 02 (2012-08-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

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


4/41

SingleRAN


Co-Transmission Contents



ii

9 Glossary ...................................................................................................................................... 9-1

10 Reference Documents ......................................................................................................... 10-1


5/41

SingleRAN


Co-Transmission 1 About This Document



1-1

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, andparameters. This feature uses IP-based co-transmission and applies to GU, GL, UL and GUL multi-modebase stations.

Before reading this document, familiarize yourself with Transmission Resource Management FeatureParameter Descriptionf or GBSS and WCDMA RAN and Transport Resource Management FeatureParameter 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-Transmissionfeature

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-Transmissionfeature of a specific product version

Editorial change: refers to a change in wording or the addition of information that was not described inthe 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 asfollows.

http://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htm


6/41

SingleRAN


Co-Transmission 1 About This Document



1-2

ChangeType

Change Description Parameter Change

Featurechange

None None

Editorialchange

Modified contents related to how to setDSCP values for NodeB service ,seesection 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 thefollowing table.

ChangeType

Change Description Parameter Change

Featurechange

Added the optional feature MRFD-231505Bandwidth Sharing of MBTS Multi-ModeCo-Transmission(eNodeB).

None

Editorialchange

Edited the document again for clarity andreadability purposes and optimized chapter6 "Engineering Guidelines."

None


7/41

SingleRAN


Co-Transmission 2 Overview



2-1

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

To address this possibility, Huawei introduced the feature Bandwidth Sharing of MBTS Multi-ModeCo-Transmission. With this feature, a unified transmission resource management policy applies to theBTS, 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 proceedwithout 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 beachieved in the following ways:

− UTRP-based co-transmission through panel interconnection

− Main-control-board-based co-transmission through panel interconnection

− UTRP-based 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 Iubinterfaces are deployed.

CN: Co-transmission with IP over FE/GE is applied to the mobility management entity (MME) orserving gateway (S-GW).

When the Common Transmission feature is activated on an MBTS, each mode has an independent algorithm to manageits own transmission resources. For transmission resource management on a BTS or NodeB, see Transmission ResourceManagement Feature Parameter Description for GBSS and WCDMA RAN. For transmission resource management on aneNodeB, 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)

http://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htm


8/41

SingleRAN


Co-Transmission 3 Technical Description



3-1

3 Technical Description

3.1 Transmission Resource Scheduling and QoS Management

To prevent transmission resource congestion, the Bandwidth Sharing of MBTS Multi-ModeCo-Transmission feature schedules transmission resources for non-real-time services but preferentiallyforwards IP packets for high-priority services.

During the early stage of network deployment, operators must ensure that the minimum bandwidth oftransmission devices in the transport network is higher than the total bandwidth of all MBTSs in the livenetwork.

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 differentiatedservices code point.

Layer-2 devices support VLAN-priority-based QoS management. VLAN stands for virtual local areanetwork.

Transmission devices support the PQ+WRR queue scheduling function, and at least two PQ queuesare 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 uplinkbecause 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 andreceives 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 basestations. 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 theBTS bandwidth.

If the port is located on the NodeB or eNodeB, operators can run the SET LR command and set CIR tolimit 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'sheader. 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, controlstraffic, 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 relatedQoS requirements and perform per-hop behavior (PHB) accordingly. PHB includes transmissionresource allocation, queue scheduling, and packet discarding.

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cir.html


9/41

SingleRAN





3-2

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 thecommands listed in the following table.

NE

Command To Set…

BTS SET BTSVLAN Mapping between signaling or traffic classes andDSCP values

NodeB

SET DIFPRI Mapping between signaling and DSCP values

Note that the mapping between the service calssesand DSCP values cannot be configured on theNodeB side. To configure the mapping, run theADD TRMMAP and SET PHBMAP command onthe RNC side.

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 thesame mapping between traffic classes and DSCPvalues.)

VLAN Priority

The VLAN tag in a frame defines an IP packet's VLAN priority. Based on the VLAN priority, layer-2devices 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 0

8-15 1

16-23 2

24-31 3

32-39 4

40-47 5

48-55 6

56-63 7


10/41

SingleRAN





3-3

Queue Priority

Queue priority defines the scheduling priority of a queue. Each IP port has eight queues, Queue 1 toQueue 8, arranged in descending order of scheduling priority. The MBTS puts different service data intodifferent queues to implement DiffServ.

Table 3-2 provides the mapping between DSCP values/queues and queue priorities for GSM and UMTSservices. Table 3-3 provides the mapping between DSCP values/queues and queue priorities for LTEservices.

Table 3-2 Mapping between DSCP values/queues and queue priorities for GSM and UMTS services

DSCP Value Queue Queue Priority

40-63 PQ1 0

Reserved PQ2 1

Reserved PQ3 2

32-39 WFQ4 3

24-31 WFQ5 4

16-23 WFQ6 5

8-15 WFQ7 6

0-7 WFQ8 7

Table 3-3 Mapping between DSCP values/queues and queue priorities for LTE services

DSCP Value Queue Queue Priority

46-63 PQ1 0

34-45 PQ2 1

26-33 PQ3 2

18-25 WFQ4 3

10-17 (excluding14)

WFQ5 4

0-9 WFQ6 5

Unused WFQ7 6

14 (for FTPservices only)

WFQ8 7

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.


11/41

SingleRAN





3-4

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 usersprocessing 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 itsown load. The base station controller and eNodeB manage the local data only.

For details about BTS and NodeB load control, see Transmission Resource Management FeatureParameter Description for GBSS and WCDMA RAN. For details about eNodeB load control, seeTransport 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 bandwidthadaptive adjustment algorithm and the HSDPA adaptive flow control algorithm. The latter two algorithmsare controlled by two switches on the NodeB.

For details about the two algorithms, see Transmission Resource Management Feature ParameterDescription for GBSS and WCDMA RAN.

On an eNodeB, the flow control function is disabled by default. To enable the function, operators mustuse 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 AdaptiveAdjustment Algorithm

HSDPA Adaptive Flow ControlAlgorithm

GUco-transmission

Activated Activated

GLco-transmission

N/A N/A

UL

co-transmission

Deactivated Activated.

Deactivated, if transmission

devices do not support PQ+WRRqueue scheduling.

GULco-transmission

Deactivated Activated

Deactivated, if transmissiondevices do not support PQ+WRRqueue scheduling.

http://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_1/Transmission%20Resource%20Management.htm


12/41

SingleRAN


Co-Transmission 4 Related Features



4-1

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.


13/41

SingleRAN


Co-Transmission 5 Impact on the Network



5-1

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.


14/41

SingleRAN


Co-Transmission 6 Engineering Guidelines



6-1

6 Engineering Guidelines

6.1 When to Use Bandwidth Sharing of MBTS Multi-Mode

Co-TransmissionIt is recommended that the Bandwidth Sharing of MBTS Multi-Mode Co-Transmission feature beactivated 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 resourcesavailable 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 forthe 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 circuitswitched (CS) services be classified as real-time services and packet switched (PS) services asnon-real-time services.

Set real-time services to a higher priority than non-real-time services to ensure the continuity of signalingand CS services when transmission resources become congested.

Activate the Transport Dynamic Flow Control Algorithm feature to allow it to properly allocatetransmission 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 mappingbetween 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-3and layer-2 devices.

Bandwidth Planning for the Transport Network

Make a bandwidth plan for the transport network based on services' bandwidth requirements andavailable bandwidth resources.


15/41

SingleRAN





6-2

When planning transmission bandwidth on the RAN side, ensure that the bandwidth between a basestation and a base station controller is higher than the total bandwidth of real-time services to avoidreducing the service quality of real-time services.

6.3.3 Hardware Planning

N/A

6.4 Activating Bandwidth Sharing of MBTS Multi-ModeCo-Transmission

6.4.1 Prerequisites

Requirements for other features

− If the BTS provides a co-transmission port, the MRFD-231501 IP-Based Multi-modeCo-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-modeCo-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-modeCo-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 Bandwidth sharing of MBTSMulti-modeCo-Transmission(NodeB)

LQW9MBTSTR01

82201908 Per NodeB

eNodeB Bandwidth sharing of MBTSMulti-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 keyparameters related to traffic shaping as follows:

MO MMLParameterName

MMLParameterID

CME Parameter Name Setting Description DataSource

BTSLR ULCommittedInformationRate

CIR UL CommittedInformation Rate

Set this parameter to theamount of bandwidthavailable for thetransport network.

Networkplan

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cir.html


16/41

SingleRAN





6-3

MO MMLParameterName

MMLParameterID

CME Parameter Name Setting Description DataSource

CommittedBurst Size

CB S Committed Burst Size Set this parameter to theCIR value multiplied by2, but ensure that theproduct is not larger than1000.

Networkplan

ExcessiveBurst Size

EBS Excessive Burst Size If the CIR value issmaller than 500, setEBS to 0. If the CIR value is larger than 500,set CBS to 1000 andensure that the sum ofCBS and EBS is twice

the CIR value.

Networkplan

If the NodeB provides a co-transmission port and GU, UL, or GUL co-transmission is applied, set the keyparameters related to traffic shaping as follows:

MO MMLParameterName

MMLParameterID

CME ParameterName

Setting Description Data Source

LR UL CommittedInformation Rate

CIR UL CommittedInformation Rate

Set this parameter tothe amount of

bandwidth available forthe transport network.

Network plan

Committed BurstSize

CB S Committed BurstSize

Set this parameter tothe CIR valuemultiplied by 2, butensure that the productis not larger than 1000.

Network plan

Excessive BurstSize

EBS Excessive BurstSize

If the CIR value issmaller than 500, setEBS to 0. If the CIR value is larger than

500, set CBS to 1000 and ensure that thesum 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 thekey parameters related to traffic shaping as follows:

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cbs.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cbs.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_ebs.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_ebs.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedBurstSize.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedBurstSize.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-ExcessBurstSize.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-ExcessBurstSize.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-ExcessBurstSize.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedBurstSize.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_ebs.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btslr_cbs.html


17/41

SingleRAN





6-4

MO MML ParameterName

MMLParameterID

Setting Description DataSource

LR UL CommittedInformation Rate

CIR Set this parameter to the amount ofbandwidth available for thetransport network.

Networkplan

Committed BurstSize

CBS Set this parameter to the CIR valuemultiplied by 2, but ensure that theproduct is not larger than 1000.

Networkplan

Excessive BurstSize

EBS If the CIR value is smaller than 500,set EBS to 0. If the CIR value islarger than 500, set CBS to 1000 and ensure that the sum of CBS and EBS is twice the CIR value.

Networkplan

When GU, GL, or GUL co-transmission is applied, set the bandwidth for the BTS logical port on the BSCside as follows:

MO MMLParameterName

MMLParameterID

CME ParameterName


IPLOGICPORT Logic PortNo.

LPN Logic Port No. Number of the BTSlogical port

Networkplan

Bandwidth CIR Bandwidth Bandwidth of the BTSlogical port

Networkplan

Transport QoS

Table 6-2 provides the transmission resource mapping (TRMMAP) between GSM/UMTS traffic classesand 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

NodeB Iub Signal 48

CCH&SRB&AMR 46

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_lpn.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_lpn.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_lpn.html


18/41

SingleRAN





6-5


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 GLco-transmission is applied.

Table 6-3 TRMMAP between GSM/LTE traffic classes and DSCP values


GBTS ESL/OML/RSL 48

CS Voice 46


PS Low PRI 26

IP Clock 46

EML 18

eNodeB SCTP 48

QCI1 46

QCI2 26

QCI3 34

QCI4 26

QCI5 46

QCI6 18QCI7 18

QCI8 10

QCI9 0

OM High 46

OM Low 18

IP Clock 46


19/41

SingleRAN





6-6

Table 6-4 provides the TRMMAP between UMTS/LTE traffic classes and DSCP values when ULco-transmission is applied.

Table 6-4 TRMMAP between UMTS/LTE traffic classes and DSCP values

NE Traffic Class DSCP ValueNodeB Iub Signal 48

CCH & SRB & AMR 46




OM High 46

OM Low 18

IP Clock 46

eNodeB SCTP 48

QCI1 46

QCI2 26

QCI3 34

QCI4 26

QCI5 46

QCI6 18

QCI7 18

QCI8 10

QCI9 0

OM High 46

OM Low 18

IP Clock 46

Table 6-5 provides the TRMMAP between GSM/UMTS/LTE traffic classes and DSCP values when GULco-transmission is applied.

Table 6-5 TRMMAP between GSM/UMTS/LTE traffic classes and DSCP values


GBTS ESL/OML/RSL 48

CS Voice 46



20/41

SingleRAN





6-7


PS Low PRI 26

IP Clock 46

EML 18

NodeB Iub Signal 48

CCH & SRB & AMR 46




OM High 46

OM Low 18

IP Clock 46

eNodeB SCTP 48

QCI1 46

QCI2 26

QCI3 34

QCI4 26

QCI5 46

QCI6 18

QCI7 18

QCI8 10

QCI9 0

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 beturned on. Otherwise, backpressure cannot be performed on services whose data is put into the same queue as the OMFTP service whose traffic class is OM low when transmission resources are congested. FTP stands for File TransferProtocol.

Table 6-6 provides the recommended settings for the key parameters related to the TRMMAP of theBTS.


21/41

SingleRAN





6-8

Table 6-6 Recommended settings for the key parameters related to the TRMMAP of the BTS

MO MMLParameterName

MMLParameter ID

CME ParameterName


BTSVLAN ServiceType

SERVICETYPE Service Type If GUco-transmission isapplied, set theparameters basedon the settingsprovided in Table6-2.

If GLco-transmission isapplied, set theparameters based

on the settingsprovided in Table6-3.

If GULco-transmission isapplied, set theparameters basedon the settingsprovided in Table6-5.

Negotiationwith thepeer

DSCP DSCP DSCP

Table 6-7 provides the recommended settings for the key parameters related to the TRMMAP of theNodeB.

Table 6-7 Recommended settings for the key parameters related to the TRMMAP of the NodeB

MO MMLParameterName

MMLParameterID

CME ParameterName


DIFPRI PriorityRule

PRIRULE Priority Rule Set this parameter toDSCP.


Signaling

Priority

SIGPRI Signaling Priority If GU co-transmission

is applied, set theparameter based onthe settings providedin Table 6-2.

If UL co-transmissionis applied, set the

OM HighPriority

OMHPRI OM High Priority

OM LowPriority

OMLPRI OM Low Priority

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btsvlan_servicetype.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btsvlan_servicetype.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btsvlan_dscp.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btsvlan_dscp.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-PriRule.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-PriRule.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-SigPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-OMHPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-OMHPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-OMLPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-OMLPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-OMLPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-OMHPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-SigPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-PriRule.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btsvlan_dscp.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/btsvlan_servicetype.html


22/41

SingleRAN





6-9

MO MMLParameterName

MMLParameterID

CME ParameterName


PTPPriority

PTPPRI PTP Priority parameter based on

the settings providedin Table 6-4.

If GULco-transmission isapplied, set theparameter based onthe settings providedin Table 6-5.

Table 6-8 provides the recommended settings for the key parameters related to the TRMMAP of the

eNodeB.

Table 6-8 Recommended settings for the key parameters related to the TRMMAP of the eNodeB

MO MMLParameterName

MMLParameterID

CME ParameterName


DIFPRI Priority Rule PRIRULE Priority Rule Set this parameter toDSCP.


SignalingPriority

SIGPRI Signaling Priority If GL co-transmissionis applied, set theparameter based on

the settings providedin Table 6-3.

If UL co-transmissionis applied, set theparameter byreferring to Table6-4.

If GULco-transmission isapplied, set theparameter by

referring to Table6-5.

OM HighPriority

OMHIGHPRI OM High Priority

OM LowPriority

OMLOWPRI OM Low Priority

IP ClockPriority

PTPPRI IP Clock Priority

User Data 1Priority~UserData 9Priority

DT1PRI~DT9PRI

User Data 1Priority~User Data 9Priority

6.4.3 Precautions

None.

6.4.4 Hardware Adjustment

N/A

http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-PTPPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-PTPPri.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DIFPRI-PTPPri.html


23/41

SingleRAN





6-10

6.4.5 Feature Activation/Initial Configuration

It is recommended that a logical port be configured for the Abis interface to improve feature performancewhen 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

AvailableTransmissionBandwidth

20 Mbit/s Available bandwidth between abase station and a base stationcontroller

Bandwidth of theBTS Logic Port

10 Mbit/s Calculate the bandwidth for thisport based on the traffic model ofthe MBTS. If the MBTSbandwidth has an upper limitand this upper limit is lower thanthe calculation result, then setthis data item to this upper limit.

BTS Index 1 None

Logic IP Address ofthe BTS

16.16.90.201 None

Port IP Address ofthe BSC

172.16.140.140 None

In an MBTS, co-transmission can be achieved through a UTRP or main control board. In the follow-upfeature activation procedures, co-transmission is achieved through a main control board, and thereforethe 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 thebandwidth over the port(CME: "Root > BTS tranmission link > BTS Line Rate"). The following is anexample:

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 thebandwidth over the port. (CME: "Main View > Right-click a site> IP Transport Layer > FeatureConfiguration > 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 anexample:


24/41

SingleRAN





6-11

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 CommunicationAddress") 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") Thefollowing 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 anexample:

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 anexample:

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 followingis 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") Thefollowing is an example:

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/servicedata and DSCP values. (CME: "Root > BTS Extend Attributes> VLANID and VLAN Priority") Thefollowing are examples:

SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=OML, DSCP=48;

SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=RSL, DSCP=48;

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_cir.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iplogicport_cir.html


25/41

SingleRAN





6-12

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;

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") Thefollowing is an example:

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 GSMand UMTS packet loss, which may affect user experience.

1. Run the NodeB MML command ADD HSUPAFLOWCTRLRAPA to turn on the switchesBWPRTSWITCH , TNLCONGCTRLSWITCH , and BACKPRESSURESWITCH . (CME: "Main View >

Right-click a site> IP Transport Layer > Feature Configuration > HspaFlowCtrl") The following isan 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 theBW_SHAPING_ONOFF_TOGGLE switch. (CME: "Main View > Right-click a site> IP TransportLayer > 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


If the BTS provides a co-transmission port, run the BSC6900 MML command SET BTSLR to limit thebandwidth over the port. (CME: "Root > BTS tranmission link > BTS Line Rate") The following is anexample:


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.

http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.html


26/41

SingleRAN





6-13

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 anexample:



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 MBTStogether. (CME: "Root > BTS tranmission link > BTS Line Rate > IP BTS CommunicationAddress") The following is an example:





1. 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 anexample:

ADD

TRMMAP:TMI=111,ITFT=ABIS,TRANST=IP,CSVOICEPATH=EF,CSDATAPATH=AF41,PSHPRIDATAPATH=AF41,PSLPRIDATAPATH=

AF31;

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


3. Run the BSC6900 MML command ADD ADJMAP to add a TRMMAP to the Abis interface.(CME:"Transmission View>GSM > Abis > IP Transport > Adjacent Node Mapping") Thefollowing is an example:







SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=ESL, DSCP=48;

SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSVOICE, DSCP=46;





2. Run the eNodeB MML command SET DIFPRI to set the mapping between signaling/service data andDSCP values. (CME: "Root > Transport > Transport Layer Information >DIFPRI") The following isan 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;



27/41

SingleRAN





6-14

----End

UL Co-Transmission

Step 1 Set the parameters related to traffic shaping on the MBTS. 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 > FeatureConfiguration > LimitRate") The following is an example:



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=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=DEFAULTPORT, RU=KBPS,


TXPBS=360000;




1. Run the BSC6900 MML command ADD TRMMAP to create a TRMMAP for Iub signaling and Iubservice data. (CME:"Transmission View > UMTS > RNC > Transport Resource Mapping") The

following is an example: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 ") Thefollowing is an example:









28/41

SingleRAN





6-15

Step 4 Set the parameters related to the Transport Dynamic Flow Control Algorithm to prevent UMTSservices from preempting transmission resources allocated to LTE services when transmissionresource 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: "MainView > Right-click a site> IP Transport Layer > Feature Configuration > HspaFlowCtrl") Thefollowing is an example:


TNLCONGCTRLSWITCH=OFF, BACKPRESSURESWITCH=ON;




----End

GUL Co-Transmission


If the BTS provides a co-transmission port, run the BSC6900 MML command SET BTSLR to limit thebandwidth over the port. (CME: "Root > BTS tranmission link > BTS Line Rate") The following is anexample:


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 > FeatureConfiguration > LimitRate") The following is an example:



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=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=DEFAULTPORT, RU=KBPS,


TXPBS=360000;



Step 2 Add a logical port to 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 anexample:



http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.html


29/41

SingleRAN





6-16

In the preceding script, the IP logical port is numbered 1, and the bandwidth of the port is the CIR valuemultiplied 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 CommunicationAddress") The following is an example:





1. Run the BSC6900 MML command ADD TRMMAP to create a TRMMAP for Iub signaling and Iubservice data. (CME:"Transmission View>UMTS > RNC > Transport Resource Mapping") Thefollowing is an example:

ADD







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 anexample:

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 anexample:


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 followingis an example:


5. Run the BSC6900 MML command ADD ADJMAP to add a TRMMAP to the Abis interface.

(CME:"Transmission View>GSM > Abis > IP Transport > Adjacent Node Mapping") Thefollowing is an example:







SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=ESL, DSCP=48;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSVOICE, DSCP=46;



30/41

SingleRAN





6-17










Step 5 Set the parameters related to the Transport Dynamic Flow Control Algorithm to prevent UMTSservices 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 andBACKPRESSURESWITCH switches and turn off the TNLCONGCTRLSWITCH switch. (CME: "MainView > Right-click a site> IP Transport Layer > Feature Configuration > HspaFlowCtrl") Thefollowing is an example:


TNLCONGCTRLSWITCH=OFF, BACKPRESSURESWITCH=ON;




----End

6.4.6 Activation Observation

After the Bandwidth Sharing of MBTS Multi-Mode Co-Transmission feature is activated, check whetherUEs 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 tosimulate 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 availablefor the transport network.

Step 4 Terminate the CS service if the service is successfully set up and the voice is clear.

http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-TNLCongctrlSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.html


31/41

SingleRAN





6-18

Step 5 Initiate a GSM PS service, connect a personal computer (PC) to the MBTS, and use DU Meteron the PC to check whether the GSM PS service is successfully set up and the data rate isstable.

− 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 simulatetransmission resource congestion.

Step 2 Log in to the RNC LMT, and choose Monitor > UMTS Monitoring > Connector PerformanceMonitoring > UL Throughput Bandwidth.

Step 3 Initiate a GSM or UMTS CS service after the traffic volume approaches the bandwidth available

for the transport network.


Step 5 Initiate a GSM PS service, connect a PC to the MBTS, and use DU Meter on the PC to checkwhether the GSM PS service is successfully set up and the data rate is stable.



----End

If the eNodeB 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 Log in to the eNodeB LMT, and choose Monitor > Transport Performance Monitoring.

Step 3 Initiate a GSM or UMTS CS service after the traffic volume approaches the bandwidth availablefor the transport network.


Step 5 Initiate a GSM PS service, connect a PC to the MBTS, and use DU Meter on the PC to checkwhether the GSM PS service is successfully set up and the data rate is stable.



----End

6.5 Performance Optimization

None.

6.6 Troubleshooting

If bandwidth resources across all modes of an MBTS are inappropriately allocated, reallocate thebandwidth resources based on the traffic model.

http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LR-CommittedInformationRate.html


32/41

SingleRAN


Co-Transmission 7 Parameters



7-1

7 Parameters

Table 7-1 Parameter description

Parameter ID NE MML Command Feature ID FeatureName Description

BACKPRESSURESWITCH

NodeB ADDHSUPAFLOWCTRLPARA

SETHSUPAFLOWCTRLPARA

None None Meaning:Indicateswhether to perform ULreverse pressure.When this switch isturned on, the BSperforms reversepressure on the airinterface to lower theUE transmit rate if thebuffer of the egress port

exceeds the specifiedthreshold.

GUI ValueRange:OFF(Off),ON(On)

Actual ValueRange:OFF, ON

Unit:None

Default Value:ON(On)

BWPRTSWITCH NodeB ADDHSUPAFLOWCTRLPARA

SETHSUPAFLOWCTRLPARA

WRFD-010692

HSUPA FDE Meaning:Indicateswhether to adjust theavailable UL bandwidth.When this parameter isset to ON, the BS stopsadjusting the availableUL bandwidth of thephysical port if the biterror rate (BER) on thetransmission lineexceeds the specified

alarm threshold. Thisparameter does nottake effect for loopbackports or tunnelsbecause the error MACframe reporting functionis not implemented forloopback ports andtunnels.

GUI ValueRange:OFF(Off),ON(On)

http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BackPressureSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/HSUPAFLOWCTRLPARA-BWPRTSwitch.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_hsupaflowctrlpara.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_hsupaflowctrlpara.htmlhttp://localhost/var/ww

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

Documents

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