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

SingleRAN

Bandwidth Sharing of MultimodeBase Station Co-TransmissionFeature Parameter Description

Issue 01Date 2014-04-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.comEmail: [email protected]

Issue 01 (2014-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

Contents

1 About This Document..................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................21.4 Differences Between Base Station Types.......................................................................................................................22 Overview.........................................................................................................................................42.1 Introduction....................................................................................................................................................................42.2 Benefits...........................................................................................................................................................................42.3 Application Networking.................................................................................................................................................53 Technical Description...................................................................................................................73.1 Introduction....................................................................................................................................................................73.2 Transmission Priorities...................................................................................................................................................83.3 Traffic Limiting and Shaping.......................................................................................................................................113.4 Load Control.................................................................................................................................................................123.5 Flow Control.................................................................................................................................................................134 Application Scenarios.................................................................................................................164.1 Unlimited Access Bandwidth for Multimode Base Stations........................................................................................164.1.1 Introduction...............................................................................................................................................................164.1.2 Transmission Resource Management Strategies.......................................................................................................174.2 Limited Access Bandwidth for Multimode Base Stations............................................................................................214.2.1 Introduction...............................................................................................................................................................214.2.2 Transmission Resource Management Strategies.......................................................................................................224.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios.................................................................304.3.1 Introduction...............................................................................................................................................................304.3.2 Transmission Resource Management Strategies.......................................................................................................305 Related Features...........................................................................................................................355.1 Prerequisite Features.....................................................................................................................................................355.2 Mutually Exclusive Features........................................................................................................................................355.3 Impacted Features.........................................................................................................................................................356 Network Impact...........................................................................................................................36

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description Contents


ii

6.1 System Capacity...........................................................................................................................................................366.2 Network Performance...................................................................................................................................................367 Engineering Guidelines.............................................................................................................377.1 When to Use Bandwidth Sharing of Multimode Base Station Co-Transmission.........................................................377.2 Required Information...................................................................................................................................................377.3 Planning........................................................................................................................................................................377.4 Deployment..................................................................................................................................................................387.4.1 Requirements.............................................................................................................................................................387.4.2 Data Preparation........................................................................................................................................................397.4.3 Precautions.................................................................................................................................................................497.4.4 Hardware Adjustment................................................................................................................................................497.4.5 Initial Configuration (Unlimited Access Bandwidth for GU Dual-Mode Base Stations).........................................497.4.6 Initial Configuration (Unlimited Access Bandwidth for GL/GT Dual-Mode Base Stations)...................................527.4.7 Initial Configuration (Unlimited Access Bandwidth for UL/UT/ULT Multimode Base Stations)...........................547.4.8 Initial Configuration (Unlimited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)..................567.4.9 Initial Configuration (Limited Access Bandwidth for GU Dual-Mode Base Stations).............................................597.4.10 Initial Configuration (Limited Access Bandwidth for GL/GT/GLT Multimode Base Stations)............................647.4.11 Initial Configuration (Limited Access Bandwidth for UL/UT/ULT Multimode Base Stations)............................677.4.12 Initial Configuration (Limited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)....................717.4.13 Initial Configuration (Limited Access Bandwidth for Each Operator in a UL/UT Dual-Mode Base Station in RANSharing Scenarios)..............................................................................................................................................................777.4.14 Activation Observation (Unlimited Access Bandwidth for Multimode Base Stations)..........................................857.4.15 Activation Observation (Limited Access Bandwidth for Multimode Base Stations)..............................................867.4.16 Activation Observation (Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios)...................907.5 Performance Monitoring...............................................................................................................................................927.6 Parameter Optimization................................................................................................................................................927.7 Troubleshooting............................................................................................................................................................928 Parameters.....................................................................................................................................939 Counters......................................................................................................................................11810 Glossary.....................................................................................................................................11911 Reference Documents.............................................................................................................120

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description Contents


iii

1 About This Document1.1 Scope

This document describes the Bandwidth Sharing of Multimode Base Station Co-Transmissionfeature, including the bandwidth sharing mechanism, recommended transmission configurationstrategies, application scenarios, related features, network impact, and engineering guidelines.This feature applies to GSM/UMTS, GSM/LTE, UMTS/LTE, and GSM/UMTS/LTE multimodebase stations in co-transmission scenarios.This document describes the following optional features:l MRFD-211505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(GBTS)l MRFD-221505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NodeB)l MRFD-231505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(eNodeB)l MRFD-241505 Bandwidth sharing of MBTS Multi-mode Co-Transmission(LTE TDD)In this document, the following naming conventions apply for LTE terms.

Includes FDD and TDD Includes FDD Only Includes TDD OnlyLTE LTE FDD LTE TDDeNodeB LTE FDD eNodeB LTE TDD eNodeBeRAN LTE FDD eRAN LTE TDD eRAN

In addition, the "L" and "T" in RAT acronyms refer to LTE FDD and LTE TDD, respectively.

1.2 Intended AudienceThis document is intended for personnel who:l Need to understand the features described herein

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description 1 About This Document


1

l Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes, which are defined as follows:l Feature change

Changes in features of a specific product versionl Editorial change

Changes in wording or addition of information that was not described in the earlier version

SRAN9.0 01 (2014-04-30)This issue does not include any changes.

SRAN9.0 Draft A (2014-01-20)Compared with 01 (2013-04-28) of SRAN8.0, Draft A (2014-01-20) of SRAN9.0 includes thefollowing changes.

Change Type Change Description ParameterChange

Feature change l Added the descriptions of the LTE(TDD) modesupport for Bandwidth Sharing of Multimode BaseStation Co-Transmission feature.

l Modified the flow control policy for a separate-MPT multimode base station where co-transmissionis implemented through backplane interconnection.

None.

Editorialchange

Added activation observation methods. For details, see7.4.15 Activation Observation (Limited AccessBandwidth for Multimode Base Stations) and 7.4.16Activation Observation (Limited Access Bandwidthfor Each Operator in RAN Sharing Scenarios).

None.

1.4 Differences Between Base Station TypesLampSite base stations are distributed base stations that provide indoor coverage. In thisdocument, LampSite base stations work in UMTS, LTE, or UMTS+LTE mode, but not in GSMmode.In this document, micro base stations are all integrated entities. They work in UMTS or LTEFDD mode, but not in GSM or LTE TDD mode. Descriptions of boards, cabinets, subracks,slots, and RRUs are not relevant to micro integrated base stations. The following base stationsare single-mode ones, without co-MPT or separate-MPT multimode applications:



2

l BTS3202El BTS3203El BTS3803El BTS3902E

Feature Support by Macro, Micro, and LampSite Base StationsFeature ID Feature Name Support

ed byMacroBaseStations

Supported byMicroBaseStations

Supported byLampSiteBaseStations

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

Yes No No

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

Yes No Yes

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

Yes No Yes

MRFD-241505 Bandwidth sharing of MBTSMulti-mode Co-Transmission(LTE TDD)

Yes No No

Function Implementation in Macro, Micro, and LampSite Base StationsNone.



3

2 Overview2.1 Introduction

The Bandwidth Sharing of Multimode Base Station Co-Transmission feature centrally managesGSM, UMTS, and LTE transmission resources. When transmission resources are congested,this feature ensures the smooth processing of high-priority services and prevents GSM, UMTS,and LTE services from impacting each other. This ensures high service quality and good userexperience. Bandwidth Sharing of Multimode Base Station Co-Transmission includes thefollowing transmission resource management strategies: mapping between traffic classes andtransmission priorities, traffic limiting and shaping, load control, and flow control.If this feature is not enabled, the transmission resources of a multimode base station are managedin the same way as those of a single-mode base station. For details about transmission resourcemanagement strategies for GSM, UMTS, and LTE, see Transmission Resource ManagementFeature Parameter Description for GBSS and RAN, and Transport Resource ManagementFeature Parameter Description for eRAN, respectively.

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

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description 2 Overview


4

When uplink or downlink transmission resources are congested, this feature guarantees thequality of service (QoS) of high-priority GSM, UMTS, and LTE services without compromisinguser experience.

2.3 Application NetworkingThis feature applies to networking schemes where both the local end (the multimode base station)and the peer end (the base station controller, MME, or S-GW) use IP transmission (IP over FE/GE or IP over E1/T1).

NOTE

MME: mobility management entityS-GW: serving gatewayMPT: main processing and transmission unit

Figure 2-1 shows the networking scheme for a co-MPT GUL triple-mode base station in co-transmission scenarios.

Figure 2-1 Networking scheme for a co-MPT GUL triple-mode base station in co-transmissionscenarios

For details about the networking scheme for a multimode base station in co-transmissionscenarios, see Common Transmission Feature Parameter Description for SingleRAN.



5

NOTE

l In this document, a multimode base station can be a GU/GL/GT/UL/UT/LT dual-mode base station, aGUL/GLT/ULT/GUT triple-mode base station, or a GULT quadruple-mode base station.

l GBTS or eGBTS refers to the GSM side of a multimode base station. NodeB refers to the UMTS sideof a multimode base station. eNodeB refers to the LTE side of a multimode base station. LTE can beLTE FDD, LTE TDD, or LTE FDD&LTE TDD.

l Multimode base stations are classified into co-MPT and separate-MPT multimode base stations, bothintroduced in SRAN8.0. In a co-MPT multimode base station, different modes share one main controlboard and one O&M channel. In a separate-MPT multimode base station, each mode has its own maincontrol board and its own O&M channel. The GSM side of a separate-MPT multimode base stationcan be either an eGBTS or a GBTS. The GSM side of a co-MPT multimode base station must be aneGBTS.

l The GBTS is not recommended for providing a co-transmission port to a separate-MPT multimodebase station. This scenario is not covered in this document.



6

3 Technical Description3.1 Introduction

For a multimode base station in co-transmission scenarios, the data of the mode that provides aco-transmission port is called local data. The data of other modes that rely on the co-transmissionport for data transmission is called passing data.l For a separate-MPT multimode base station in co-transmission scenarios, the co-

transmission port transmits and receives the local data and the passing data. In this case,the co-transmission port centrally schedules and manages the data of multiple modes.

l For a co-MPT multimode base station in co-transmission scenarios, the co-transmissionport transmits and receives only the local data, which includes the data for all modes of thisbase station. In this case, the co-transmission port centrally schedules and manages the datafor all modes.

NOTE

l Differentiation: Transmission differentiation is used when transmission bandwidth is limited.Transmission differentiation prioritizes bandwidth use, with real-time services taking precedence overnon-real-time services.

l Fairness: If transmission congestion occurs, service differentiation ensures that real-time services arepreferentially processed. As a result, non-real-time services may experience packet losses, whichaffects fairness among non-real-time services. The transmission flow control function enables eachtype of service or each mode to be allocated a certain amount of bandwidth. This eliminates thepossibility that a certain service or a certain mode experiences service interruptions because of lack oftransmission bandwidth.

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

Table 3-1 Definitions of base stationsBase Station Name DefinitionGBTS GBTS refers to a base station deployed with GTMU.eGBTS eGBTS refers to a base station deployed with UMPT_G.

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description 3 Technical Description


7

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

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

or UMPT_T.Co-MPT MultimodeBase Station

Co-MPT multimode base station refers to a base station deployedwith UMPT_GU, UMPT_GL, UMPT_GT, UMPT_UL,UMPT_UT, UMPT_LT, UMPT_GUL, UMPT_GUT,UMPT_ULT, UMPT_GLT, or UMPT_GULT, and itfunctionally corresponds to any combination of eGBTS, NodeB,and eNodeB. For example, Co-MPT multimode base stationdeployed with UMPT_GU functionally corresponds to thecombination of eGBTS and NodeB.

Separate-MPTMultimode Base Station

Separate-MPT multimode base station refers to a base station onwhich different modes use different main control boards. Forexample, base stations deployed with GTMU and WMPT arecalled separate-MPT GSM/UMTS dual-mode base station.

To enable a co-transmission port to implement unified data scheduling and management,differentiation and fairness among different service types and modes must be ensured. Moreover,transmission resource congestion caused when all of the modes have overlapping traffic burstsmust also be addressed. To address these problems, Huawei introduces the Bandwidth Sharingof Multimode Base Station Co-Transmission feature.This feature adopts four recommended transmission resource management strategies: mappingbetween traffic classes and transmission priorities, traffic limiting and shaping, load control, andflow control. For details about transmission resource management strategies for GSM, UMTS,and LTE, see Transmission Resource Management Feature Parameter Description for GBSSand RAN, and Transport Resource Management Feature Parameter Description for eRAN,respectively.

3.2 Transmission PrioritiesThe Bandwidth Sharing of Multimode Base Station Co-Transmission feature providesdifferentiated services (DiffServ) for different service types based on transmission priorities.Transmission priorities include the DiffServ Code Point (DSCP), virtual local area network(VLAN) priority, and queue priority.

DSCPDSCP is a field in an IP packet header to indicate the QoS requirements. Each node implementsDiffServ based on the DSCP value.A multimode base station or base station controller sets the DSCP value for each IP packet basedon the QoS requirements of each service type. From the DSCP value, transmission devicesidentify the traffic class and related QoS requirements of the service and perform per-hop



8

behaviors (PHBs) accordingly. PHBs include transmission resource allocation, queuescheduling, and packet discarding.Table 3-2 describes how to use MML commands to configure the mapping between trafficclasses and DSCP values for each type of base station.

Table 3-2 Configuring the mapping between traffic classes and DSCP values for each type ofbase station

NE Command DescriptionGBTS SET BTSVLAN Used to set the mapping

between DSCP values anddata from the O&M plane,control plane (CP), and userplane (UP) on the GBTS side.

eGBTS andNodeB

SET DIFPRI Used to set the mappingbetween DSCP values anddata from the O&M planeand CP on the eGBTS orNodeB side.

ADD TRMMAP and SETPHBMAP

Used to set the mappingbetween DSCP values anddata from the UP on the BSCor RNC side.

eNodeB SET DIFPRI Used to set the mappingbetween DSCP values anddata from the O&M planeand CP plane on the eNodeBside.

MOD UDTPARAGRP Used to set the mappingbetween DSCP values anddata from the UP on theeNodeB side.

Pay attention to the following when mapping traffic classes to DSCP values:l For separate-MPT multimode base stations in co-transmission scenarios, run the necessary

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

l For multimode base stations in co-transmission scenarios, run the necessary MMLcommands to individually map the DSCP values to the data from the UP for the GBTS,eGBTS, NodeB, and eNodeB.



9

NOTE

The mapping between traffic classes and DSCP values for GSM, UMTS, and LTE services should beconsistent on the base station, the base station controller, and the CN.

VLAN PriorityThe VLAN tag defines an IP packet's VLAN priority. Based on the VLAN priority, Layer 2devices can implement DiffServ.VLAN priorities of packets with different traffic classes can be determined by DSCP values.Table 3-3 provides the default mapping between DSCP values and VLAN priorities on themultimode base station side.

Table 3-3 Default mapping between DSCP values and VLAN prioritiesDSCP Value VLAN Priority07 0815 11623 22431 33239 44047 54855 65663 7

Queue PriorityQueue priority defines the scheduling priority of a queue. Each Ethernet port or Point-to-PointProtocol (PPP) link supports eight queues: PQ1, PQ2, PQ3, and WRR (which includes WFQ4through WFQ8). The queues are displayed in descending order of scheduling priority. Amultimode base station puts packets with different traffic classes into different queues toimplement DiffServ.

NOTE

PQ is short for priority queue.WFQ is short for weighted fair queuing.WRR is short for weighted round robin. WFQ4 through WFQ7 have the same weight.

Queue priorities are determined by the mapping between DSCP values and queue priorities, aslisted in Table 3-4 and Table 3-5. You are not advised to modify the default mapping betweenDSCP values and queue priorities.



10

Table 3-4 Default mapping between DSCP values and queue priorities for the GBTSDSCP Value Queue Queue Priority4063 PQ1 0Reserved PQ2 1Reserved PQ3 23239 WFQ4 32431 WFQ5 31623 WFQ6 3815 WFQ7 307 WFQ8 3

Table 3-5 Default mapping between DSCP values and queue priorities for the eGBTS, NodeB,and eNodeB in a co-MPT multimode base station

DSCP Value Queue Queue Priority4863 PQ1 04047 PQ2 13239 PQ3 22431 WFQ4 31623 WFQ5 3815 WFQ6 307 WFQ7 3

3.3 Traffic Limiting and ShapingWhen transmission resources are limited, transmission devices may be incapable of receivingexcess packets that arrive at the co-transmission port in a multimode base station. To preventtransmission devices from discarding packets, the traffic limiting function is introduced.PS services have unstable data rates due to unexpected traffic bursts. The traffic shaping functionis introduced to ensure stable rates in a multimode base station.The traffic limiting and shaping functions prevent packet discarding and congestion caused bytraffic bursts. These functions use the Generic Traffic Shaping (GTS) technology, which shapesirregular data flows to balance the bandwidth between upstream and downstream nodes.The traffic limiting and shaping functions apply only to non-real-time services.



11

NOTE

Base stations cannot dynamically adjust the data rates of real-time services. To prevent real-time servicecongestion, at the early stage of network deployment, the bottleneck bandwidth planned for the transmissiondevices must be greater than the total bandwidth planned for real-time services in a GU, GL, UL, or GULmultimode base station.

The traffic limiting and shaping functions can be configured at both the base station level andthe logical port level.l Base-station-level traffic limiting and shaping

Separate-MPT multimode base stationIf the eGBTS, NodeB, or eNodeB provides a co-transmission port, you can run the SETLR command and specify the CIR parameter to set the bandwidth after rate limitationfor a base station. Co-MPT multimode base station

You can run the SET LR command and specify the CIR parameter to set the bandwidthafter rate limitation for a base station.

l Logical-port-level traffic limiting and shaping Separate-MPT multimode base station

If the eGBTS, NodeB, or eNodeB provides a co-transmission port, you can run theADD RSCGRP command and specify the TXBW parameter to set the bandwidth afterrate limitation for a logical port. Co-MPT multimode base station

You can run the ADD RSCGRP command and specify the TXBW parameter to set thebandwidth after rate limitation for a logical port.

l Multimode base station controllerYou can run the ADD IPLOGICPORT command and specify the CIR(BSC6900,BSC6910) parameter to set the bandwidth after rate limitation for a logical port.

NOTE

To implement rate limitation for a logical port,l You are advised to set bandwidth after rate limitation using the SET LR command and set logical

port bandwidth using the ADD RSCGRP command.l You are not advised to modify the rate using the ADD ETHPORT command.Transport resource groups are classified into default port transport resource groups and non-defaultport transport resource groups. One physical port can be configured with one default port transportresource group and multiple non-default port transport resource groups. The following transportresource group configuration policy is recommended for a co-MPT multimode base station:l All modes use the same default transport resource group to implement rate limitation and data

shaping.l Each mode uses different non-default transport resource groups to implement rate limitation and

data shaping.

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



12

l Admission control: ensures quality of the admitted services by preventing excessiveadmissions.

l LDR: promotes admission success rates and system capacity by relieving transmission loadand preventing transmission resource congestion.

l OLC: alleviates the negative impact of overload on high-priority users by quickly reducingtransmission load.

Load control for each mode in a multimode base station in co-transmission scenarios is the sameas load control in a single-mode base station. GSM and UMTS load is controlled by the relatedbase station controller and LTE load is controlled by the eNodeB.For details about load control for GSM, UMTS, and LTE, see Transmission ResourceManagement Feature Parameter Description for GBSS and RAN, and Transport ResourceManagement Feature Parameter Description for eRAN, respectively.

3.5 Flow ControlWhen transmission bandwidth dynamically changes, the bandwidth available for the bottlenecknodes may be smaller than the bandwidth after rate limitation on the shared port. If the basestation keeps transmitting data at the bandwidth after rate limitation, the transport network maybe congested. To prevent transport network congestion, the flow control algorithm is introduced.This algorithm first estimates the bottleneck bandwidth based on the transmission quality testand then dynamically adjusts the transmit bandwidth to ensure that the transmit bandwidth doesnot exceed the bottleneck bandwidth.Table 3-6 lists whether GSM, UMTS, and LTE support the flow control algorithm.

Table 3-6 Whether GSM, UMTS, and LTE support the flow control algorithmMode NE Support Flow

ControlRemarks

GSM GBTS/eGBTS andBSC

No None

UMTS NodeB and RNC Yes The flow controlalgorithm is alsocalled the dynamicflow controlalgorithm.

LTE eNodeB Yes The flow controlalgorithm is disabledby default.

The flow control algorithm on a NodeB calculates the transmission delay, the number ofdiscarded packets, and bandwidth resources available and then performs traffic shaping. In thisway, packet discarding caused by Iub interface congestion is prevented.This algorithm takes effect only on HSDPA and HSUPA services, and it includes the NodeBuplink bandwidth adaptive adjustment algorithm and the NodeB HSDPA adaptive flow control



13

algorithm. The NodeB uplink bandwidth adaptive adjustment algorithm is controlled by theHSUPA congest control switch (TNLCONGCTRLSWITCH) and the traffic control switch(TCSW) on the NodeB. The NodeB HSDPA adaptive flow control algorithm is controlled bySWITCH on the NodeB.For working principles and implementation of the NodeB uplinkbandwidth adaptive adjustment algorithm and NodeB HSDPA adaptive flow control algorithm,see Transmission Resource Management Feature Parameter Description for RAN.For a co-MPT UL or GUL multimode base station in co-transmission scenarios, if UMTSHSDPA services are undergoing flow control, the released UMTS bandwidth may be occupiedby LTE services. Consequently, bandwidth available for UMTS services may decreaseconsiderably. To protect UMTS bandwidth, enable the fair flow control switch(FAIRSWITCH) on the NodeB side. The fair switch ensures that at least 30% of the actualreceive bandwidth is retained for UMTS HSDPA services. For example, if the total bandwidthfor UMTS HSDPA services decreases to 30% of the actual receive bandwidth, data rates forUMTS HSDPA services will not be reduced.The fair flow control switch can be configured either on a physical port of a co-MPT UL dual-mode base station or on the corresponding loopback interface (also called logical port) of thephysical port, with the physical port preferred. When configured on the loopback interface, thefair flow control switch applies only to the following scenarios:l Scenario 1: One loopback interface corresponds to one physical port, and UMTS and LTE

services are carried on the same physical port, as shown in Figure 3-1.l Scenario 2: One loopback interface corresponds to multiple physical ports, and UMTS and

LTE services are carried on different physical ports, as shown in Figure 3-2.

Figure 3-1 One loopback interface corresponding to one physical port; UMTS and LTEservices carried on the same physical port



14

Figure 3-2 One loopback interface corresponding to multiple physical ports; UMTS and LTEservices carried on different physical ports

NOTE

The loopback interface is a virtual interface that resides on a router. It is not connected to any other device.It is recommended that you configure the FAIRSWITCH on the loopback interface in scenario 2 becausethis scenario is not a multimode base station co-transmission networking scenario.

For details about the flow control algorithm, see Transmission Resource Management FeatureParameter Description for WCDMA RAN.



15

4 Application Scenarios4.1 Unlimited Access Bandwidth for Multimode BaseStations4.1.1 Introduction

Unlimited access bandwidth for multimode base stations refers to scenarios in which:l The operator cannot or has not planned access bandwidth for each multimode base station.l The bandwidth of the converging device, which converges the data of multimode base

stations, is either limited or unlimited.For example, in Figure 4-1, the access bandwidth for the three multimode base stations is themaximum bandwidth 100 Mbit/s and bandwidth for intermediate transmission devices is alsothe maximum bandwidth 100 Mbit/s.

Figure 4-1 Unlimited access bandwidth for multimode base stations

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description 4 Application Scenarios


16

4.1.2 Transmission Resource Management StrategiesThis section describes how to configure transmission resource management strategies in thisscenario. These strategies also apply to scenarios in which multiple operators share onemultimode base station and the access bandwidth of one operator is shared by other operators.

(Optional) Configuring Traffic Limiting and Shaping on the Base StationController Side

Traffic limiting and shaping can be configured on the base station controller side if the operatorcan dimension transmission bandwidth required by a base station based on the traffic model.The bandwidth after rate limitation is calculated based on the service model.

Configuring the Mapping Between Traffic Classes and Transmission PrioritiesTable 4-1 lists recommended transmission priorities for different traffic classes. For detailsabout the mapping between DSCP values and traffic classes, see descriptions about DSCP inchapter 3 Technical Description.

Table 4-1 Recommended transmission priorities for different traffic classes if access bandwidthis unlimited for multimode base stations

NE Traffic Class PHB DSCP Value VLANPriority

GBTS ESL/OML/RSL CS6 48 6CS Voice EF 46 5CS Data/PSHigh PRI

AF41 34 4

PS Low PRI AF31 26 3IP Clock EF 46 5EML AF21 18 2

eGBTS SCTP CS6 48 6CS Voice EF 46 5CS Data/PSHigh PRI

AF41 34 4

PS Low PRI AF31 26 3OM High EF 46 5OM Low AF21 18 2IP Clock EF 46 5

NodeB Iub Signal CS6 48 6



17


CCH&SRB&AMR

EF 46 5

Conversational&Streaming

AF41 34 4

R99interactive&background

AF21 18 2

HSxPAinteractive&background

AF11 10 1

OM High EF 46 5OM Low AF21 18 2IP Clock EF 46 5

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

In most cases, transmission devices support queue scheduling. Layer 3 and Layer 2 transmissiondevices support eight queues. However, if transmission devices in the bearer network supportless than eight queues, transmission priority combining strategies listed in Table 4-2 arerecommended. You can combine packets with different DSCP values into one queue andcombine packets with different VLAN priorities into one queue. For example, if the transmissiondevices support six queues, packets whose DSCP values are 48 and 46 can be put into one queue.



18

Accordingly, packets whose VLAN priorities are 6 and 5 can be put into one queue. This queuehas the highest transmission priority.

Table 4-2 Recommended transmission priority combining strategies if access bandwidth isunlimited for multimode base stations

Number of Queues DSCP Value CombiningStrategy

VLAN Priority CombingStrategy

6 DSCP values for the sixqueues are (48+46), 34, 26,18, 10, and 0, respectively.

VLAN priorities for the sixqueues are (6+5), 4, 3, 2, 1,and 0, respectively.

5 DSCP values for the fivequeues are (48+46), (34+26),18, 10, and 0, respectively.

VLAN priorities for the fivequeues are (6+5), (4+3), 2, 1,and 0, respectively.

4 DSCP values for the fourqueues are (48+46), (34+26+18), 10, and 0, respectively.

VLAN priorities for the fourqueues are (6+5), (4+3+2), 1,and 0, respectively.

3 DSCP values for the threequeues are (48+46), (34+26+18+10), and 0, respectively.

VLAN priorities for the threequeues are (6+5), (4+3+2+1),and 0, respectively.

Configuring the Flow Control AlgorithmTable 4-3 provides recommended settings for the NodeB dynamic flow control algorithm andthe HSDPA fair flow control switch.

Table 4-3 Recommended settings for the NodeB flow control algorithm and the HSDPA fairflow control switch if access bandwidth is unlimited for multimode base stations

Base Station Type Setting of theHSUPACongestionControl Switch

Setting of theHSDPA AdaptiveFlow ControlAlgorithm Switch

Setting of theHSDPA Fair FlowControl Switch

Separate-MPT GUdual-mode basestation

ON(On) (defaultvalue)

BW_SHAPING_ONOFF_TOGGLE(BW_SHAPING_ONOFF_TOGGLE)(default value)

N/A

Co-MPT GU dual-mode base stationSeparate-MPT GLdual-mode basestation

N/A N/A N/A

Co-MPT GL dual-mode base station



19




Separate-MPT ULdual-mode basestation

OFF(Off) l BW_SHAPING_ONOFF_TOGGLE(BW_SHAPING_ONOFF_TOGGLE) (defaultvalue): if thebearer networksupports three ormore queues

l NO_BW_SHAPING(NO_BW_SHAPING): if thebearer networksupports only twoqueues

N/A

Co-MPT UL dual-mode base station



ENABLE(Enable)



20




Separate-MPT GULtriple-mode basestation



N/A

Co-MPT GUL triple-mode base station



ENABLE(Enable)

4.2 Limited Access Bandwidth for Multimode Base Stations4.2.1 Introduction

Limited access bandwidth for multimode base stations refers to scenarios in which:



21

l The maximum data rate for each multimode base station must not exceed the plannedbandwidth.

l The bandwidth of intermediate transmission devices is either limited or unlimited.The access bandwidth for a base station is limited if the bearer network is leased or if the basestation uses satellite, microwave, or xPON to receive data.For example, in Figure 4-2, the access bandwidth for the three multimode base stations is limitedto 10 Mbit/s.

Figure 4-2 Limited access bandwidth for multimode base stations

4.2.2 Transmission Resource Management StrategiesThis section describes how to configure transmission resource management strategies in thisscenario. These strategies also apply to scenarios in which multiple operators share onemultimode base station, the access bandwidth of one operator is shared by other operators, andthe access bandwidth for multimode base stations is limited.

Configuring Traffic Limiting and Shaping on the Base Station Controller SideSet the bandwidth after rate limitation to the access bandwidth planned by the operator for amultimode base station.

Configuring Traffic Limiting and Shaping on the Co-Transmission Port of the BaseStation Side

Set the bandwidth after rate limitation to the access bandwidth planned by the operator for amultimode base station.



22

Configuring the Mapping Between Traffic Classes and DSCP ValuesTable 4-4 lists recommended transmission priorities for different traffic classes.

Table 4-4 Recommended transmission priorities for different traffic classes if access bandwidthis limited for multimode base stations


GBTS ESL/OML/RSL CS6 48 6CS Voice EF 46 5CS Data/PSHigh PRI

AF41 34 4

PS Low PRI AF31 26 3IP Clock CS6 46 6EML AF21 18 2

eGBTS SCTP CS6 48 6CS Voice EF 46 5CS Data/PSHigh PRI

AF41 34 4

PS Low PRI AF31 26 3OM High EF 46 5OM Low AF21 18 2IP Clock CS6 46 6

NodeB Iub Signal CS6 48 6CCH&SRB&AMR

EF 46 5


AF41 34 4


AF21 18 2


AF11 10 1

OM High EF 46 5OM Low AF21 18 2



23


IP Clock EF 46 5eNodeB SCTP CS6 48 6

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

In most cases, transmission devices support queue scheduling. Layer 3 and Layer 2 transmissiondevices support eight queues. However, if transmission devices in the bearer network supportless than eight queues, transmission priority combining strategies listed in Table 4-5 arerecommended. You can combine packets with different DSCP values into one queue andcombine packets with different VLAN priorities into one queue. For example, if the transmissiondevices support six queues, packets whose DSCP values are 48 and 46 can be put into one queue.Accordingly, packets whose VLAN priorities are 6 and 5 can be put into one queue. This queuehas the highest transmission priority.

Table 4-5 Recommended transmission priority combining strategies if access bandwidth islimited for multimode base stations






VLAN priorities for the fivequeues are (6+5), 4, 3, 2, (1+0), respectively.



24








Table 4-6 Recommended settings for the NodeB flow control algorithm and the HSDPA fairflow control switch if access bandwidth is limited for multimode base stations

Base StationType

Setting of theTrafficControlSwitch

Setting of theHSUPACongestionControlSwitch

Setting of theHSDPAAdaptiveFlow ControlAlgorithmSwitch

Setting of theHSDPA FairFlow ControlSwitch

Separate-MPTGU dual-modebase station

ENABLE(Enable)(default value)

ON(On)(default value)

BW_SHAPING_ONOFF_TOGGLE(BW_SHAPING_ONOFF_TOGGLE) (defaultvalue)

N/A

Co-MPT GUdual-mode basestation

Separate-MPTGL dual-modebase station


N/A N/A N/A

Co-MPT GLdual-mode basestation



25

Base StationType





Separate-MPTUL dual-modebase station

l ENABLE(Enable)(defaultvalue): if co-transmissionisimplemented throughbackplaneinterconnection

l DISABLE(Disable):ifco-transmissionisimplemented throughpanelinterconnection

OFF(Off) l BW_SHAPING_ONOFF_TOGGLE(BW_SHAPING_ONOFF_TOGGLE) (defaultvalue): if thebearernetworksupportsthree ormore queues

l NO_BW_SHAPING(NO_BW_SHAPING):if the bearernetworksupportsonly twoqueues

N/A



26

Base StationType





Co-MPT ULdual-mode basestation




ENABLE(Enable)



27

Base StationType





Separate-MPTGUL triple-mode basestation

l ENABLE(Enable)(defaultvalue): if co-transmissionisimplemented throughbackplaneinterconnection

l DISABLE(Disable):ifco-transmissionisimplemented throughpanelinterconnection



N/A



28

Base StationType





Co-MPT GULtriple-modebase station




ENABLE(Enable)

NOTE

l TCSW is set to ENABLE by default. If you want to set TCSW to DISABLE, first run the ADDRSCGRP command to add a default transmission resource group to the co-transmission port withRSCGRPID set to DEFAULTPORT. Then set TCSW to DISABLE for the default transmissionresource group you have added.

l If a separate-MPT multimode base station uses backplane interconnection to implement co-transmission, the tunnel type (TUNNELTYPE) of the main control board that provides the co-transmission port must be set to DL and that of the main control board that does not provide the co-transmission port must be set to UL. If the tunnel type is incorrect, the traffic control function cannotwork properly. For details about tunnel type configuration, see Common Transmission FeatureParameter Description for SingleRAN.

When co-transmission is applied, the load control algorithm for each mode in a multimode basestation is configured in the same way as the load control algorithm in a single-mode base station.For details about load control for GSM, UMTS, and LTE, see Transmission ResourceManagement Feature Parameter Description for GBSS and RAN, and Transport ResourceManagement Feature Parameter Description for eRAN, respectively.



29

4.3 Limited Access Bandwidth for Each Operator in RANSharing Scenarios

4.3.1 IntroductionLimited access bandwidth for each operator in radio access network (RAN) sharing scenariosrefer to scenarios in which:l Multiple operators share one multimode base station.l Access bandwidth of one operator is not shared by other operators.l Access bandwidth of one operator is shared among services of each mode run by this

operator.l Access bandwidth for each operator is limited.Access bandwidth for each operator is limited when the bearer network is leased. In RAN15.0,limited access bandwidth for multiple operators in RAN sharing scenarios applies only to ULdual-mode base stations. For example, in Figure 4-3, the access bandwidth for each operator islimited to 10 Mbit/s.

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

4.3.2 Transmission Resource Management StrategiesThis section describes how to configure transmission resource management strategies in thisscenario.

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



30

Configuring Traffic Limiting and Shaping on the Co-Transmission Port of the BaseStation Side

Configure a logical port for each operator on the co-transmission port of the base station side.Set the bandwidth after rate limitation on the logical port to the access bandwidth planned bythe operator.

Configuring the Mapping Between Traffic Classes and DSCP ValuesTable 4-7 lists recommended transmission priorities for different traffic classes.

Table 4-7 Recommended transmission priorities for different traffic classes if access bandwidthis limited for each operator in RAN sharing scenarios


NodeB Iub Signal CS6 48 6CCH&SRB&AMR

EF 46 5


AF41 34 4


AF21 18 2


AF11 10 1

OM High EF 46 5OM Low AF21 18 2IP Clock EF 46 5

eNodeB SCTP CS6 48 6QCI1 EF 46 5QCI2 AF41 34 4QCI3 AF41 34 4QCI4 AF41 34 4QCI5 EF 46 5QCI6 AF21 18 2QCI7 AF21 18 2QCI8 AF21 18 2



31


QCI9 BE 0 0OM High EF 46 5OM Low AF21 18 2IP Clock EF 46 5

In most cases, transmission devices support queue scheduling. Layer 3 and Layer 2 transmissiondevices support eight queues. However, if transmission devices in the bearer network supportless than eight queues, transmission priority combining strategies listed in Table 4-8 arerecommended. You can combine packets with different DSCP values into one queue andcombine packets with different VLAN priorities into one queue. For example, if the transmissiondevices support six queues, packets whose DSCP values are 48 and 46 can be put into one queue.Accordingly, packets whose VLAN priorities are 6 and 5 can be put into one queue. This queuehas the highest transmission priority.

Table 4-8 Recommended transmission priority combining strategies if access bandwidth islimited for each operator in RAN sharing scenarios






VLAN priorities for the fivequeues are (6+5), 4, 3, 2, (1+0), respectively.








32

Table 4-9 Recommended settings for the NodeB flow control algorithm and the HSDPA fairflow control switch if access bandwidth is limited for each operator in RAN sharing scenarios

Base StationType





Separate-MPTUL dual-modebase station

l ENABLE(Enable)(defaultvalue): if co-transmission isimplemented throughbackplaneinterconnection

l DISABLE(Disable):ifco-transmission isimplemented throughpanelinterconnection

OFF(Off): l BW_SHAPING_ONOFF_TOGGLE(BW_SHAPING_ONOFF_TOGGLE) (defaultvalue): if thebearernetworksupportsthree ormore queues


N/A



33

Base StationType





Co-MPT ULdual-mode basestation




ENABLE(Enable)

NOTE

l TCSW is set to ENABLE by default. If you want to set TCSW to DISABLE, first run the ADDRSCGRP command to add a default transmission resource group to the co-transmission port withRSCGRPID set to DEFAULTPORT. Then set TCSW to DISABLE for the default transmissionresource group you have added.

l If a separate-MPT multimode base station uses backplane interconnection to implement co-transmission, the tunnel type (TUNNELTYPE) of the main control board that provides the co-transmission port must be set to DL and that of the main control board that does not provide the co-transmission port must be set to UL. If the tunnel type is incorrect, the traffic control function cannotwork properly. For details about tunnel type configuration, see Common Transmission FeatureParameter Description for SingleRAN.

When co-transmission is applied, the load control algorithm for each mode in a multimode basestation is configured in the same way as the load control algorithm in a single-mode base station.For details about how to configure the load control algorithm for UMTS and LTE, seeTransmission Resource Management Feature Parameter Description for GBSS and RAN, andTransport Resource Management Feature Parameter Description for eRAN, respectively.



34

5 Related Features5.1 Prerequisite Features

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

5.2 Mutually Exclusive FeaturesNone

5.3 Impacted FeaturesNone

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description 5 Related Features


35

6 Network Impact6.1 System Capacity

No impact.

6.2 Network PerformanceIf the settings of inter-RAT parameters, such as inter-RAT bandwidth allocation and inter-RATQoS planning, are inappropriate, activating this feature will have the following impacts:l Increased service congestion ratesl Reduced data rates of low-priority services, for example, best effort (BE) servicesl Increased packet loss rates of low-priority services

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description 6 Network Impact


36

7 Engineering Guidelines7.1 When to Use Bandwidth Sharing of Multimode BaseStation Co-Transmission

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

7.2 Required InformationTo provide guide on how to plan transmission bandwidth and transmission priorities formultimode base stations and multimode base station controllers, you need to know the networktopology and transmission bandwidth plan, which include transmission bandwidth available inthe bearer network and the queues available on transmission devices.

7.3 PlanningThis section describes planning activities you need to complete before you implement thefeature.

RF PlanningN/A

Network Planningl Transmission bandwidth plan for radio services

Make a transmission bandwidth plan each for the GBTS/eGBTS, NodeB, and eNodeB ofa multimode base station based on the service plan and the corresponding bandwidthrequirements.

l QoS plan for radio servicesFor a GU, GL, UL, or GUL multimode base station in co-transmission scenarios, it isrecommended that signaling and circuit switched (CS) services be classified as real-time

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description 7 Engineering Guidelines


37

services and packet switched (PS) services as non-real-time services. Set real-time servicesto a higher priority than non-real-time services to ensure the continuity of signaling and CSservices when transmission resources become congested. Activate the flow controlalgorithm for each mode to properly allocate transmission resources across non-real-timeservices when transmission resources become congested.

l Traffic class and transmission priority mappingPlan traffic classes, DSCP values, VLAN priorities, and the mapping between traffic classesand DSCP values based on the QoS plan of services.

l QoS plan for the bearer networkPlan DSCP values, VLAN priorities, and the number of PQ queues for layer-3 and layer-2devices based on service priorities.

l Bandwidth plan for the bearer networkPlan bandwidth for the bearer network based on services' bandwidth requirements andavailable bandwidth resources.When planning transmission bandwidth on the RAN side, ensure that the bandwidthbetween a base station and a base station controller is higher than the total bandwidth ofreal-time services to avoid reducing the service quality of real-time services.

Hardware PlanningN/A

7.4 DeploymentThis section describes how to deploy the Bandwidth Sharing of Multimode Base Station Co-Transmission feature.

7.4.1 Requirementsl Transmission devices

To implement the Bandwidth Sharing of Multimode Base Station Co-Transmission feature,the bearer network must support QoS management. Otherwise, this feature becomes invalidwhen the bearer network is congested. QoS management includes the following aspects: Layer 3 devices support DSCP-priority-based QoS management. Layer 2 devices support VLAN-priority-based QoS management. Transmission devices support the PQ+WRR queue scheduling function, and at least two

PQ queues are supported. (WRR stands for weighted round robin.)l Other features

If the GBTS provides a co-transmission port, the MRFD-211501 IP-Based Multi-modeCo-Transmission on BS side(GBTS) feature must be activated on the BTS. If the NodeB provides a co-transmission port, the MRFD-221501 IP-Based Multi-mode

Co-Transmission on BS side(NodeB) feature must be activated on the NodeB. If the eNodeB provides a co-transmission port, the MRFD-231501 IP-Based Multi-

mode Co-Transmission on BS side(eNodeB) feature must be activated on the eNodeB.



38

If the LTE TDD eNodeB provides a co-transmission port, the MRFD-241501Bandwidth sharing of MBTS Multi-mode Co-Transmission(LTE TDD) feature mustbe activated on the LTE TDD eNodeB.

l LicenseThe license for the Bandwidth Sharing of Multimode Base Station Co-Transmission featurehas been activated.

Table 7-1 License control itemsFeature ID

Feature Name License Control Item NE Sales Unit

MRFD-211505

Bandwidth sharing ofMBTS Multi-mode Co-Transmission(GBTS)

Bandwidth sharing ofMBTS Multi-mode Co-Transmission(GBTS)

BSC per BTS

MRFD-221505

Bandwidth sharing ofMBTS Multi-mode Co-Transmission(NodeB)

Bandwidth sharing ofMBTS Multi-mode Co-Transmission(NodeB)

NodeB per NodeB

MRFD-231505

Bandwidth sharing ofMBTS Multi-mode Co-Transmission(eNodeB)

Bandwidth sharing ofMBTS Multi-mode Co-Transmission(FDD)

eNodeB

per eNodeB

MRFD-241505

Bandwidth sharing ofMBTS Multi-mode Co-Transmission(LTETDD)

Bandwidth sharing ofMBTS Multi-mode Co-Transmission(LTETDD)

eNodeB

Per eNodeB

7.4.2 Data PreparationTraffic Limiting and Shaping

If access bandwidth is limited for multimode base stations, data for traffic limiting and shapingmust be prepared on the base station side that provides a co-transmission port. Table 7-2 liststhe data to prepare for configuring traffic limiting and shaping.

Table 7-2 Data to prepare for configuring traffic limiting and shaping if access bandwidth islimited for multimode base stations

MO ParameterName

ParameterID

Setting Notes DataSource

LR ULCommittedInformationRate

CIR Set this parameter to theaccess bandwidth plannedby the operator.

Networkplan



39

MO ParameterName

ParameterID

Setting Notes DataSource

CommittedBurst Size

CBS l If the CIR value issmaller than 500 Mbit/s,set CBS to the CIR valuemultiplied by 2 andset EBS to 0 Mbit/s.

l If the CIR value isgreater than 500 Mbit/s,set CBS to 1000 Mbit/sto ensure that the sum ofCBS and EBS is twicethe CIR value.

Networkplan

ExcessiveBurst Size

EBS Networkplan

If access bandwidth is limited for each operator in RAN sharing scenarios, data for traffic limitingand shaping must be prepared on the base station side that provides a co-transmission port. Table7-3 lists the data to prepare for configuring traffic limiting and shaping.

Table 7-3 Data to prepare for configuring traffic limiting and shaping if access bandwidth islimited for each operator in RAN sharing scenarios

MO Parameter Name Parameter ID

Setting Notes Data Source

RSCGRP Tx Bandwidth TXBW Set thisparameter to theaccessbandwidthplanned by theoperator.

Network plan

TX Committed BurstSize

TXCBS l If theTXBW valueis smallerthan 500Mbit/s, setTXCBS tothe TXBWvaluemultipliedby 2 and setTXEBS to 0Mbit/s.

l If theTXBW valueis greaterthan 500

Network plan



40

MO Parameter Name Parameter ID

Setting Notes Data Source

TX Excessive BurstSize

TXEBS Mbit/s, setTXCBS to1000 Mbit/sto ensurethat the sumof TXCBSand TXEBSis twice theTXBWvalue.

Network plan

If access bandwidth is unlimited for multimode base stations and limited for each operator inRAN sharing scenarios, data for traffic limiting and shaping must be prepared on the BSC orRNC side. Table 7-4 lists the data to prepare for configuring traffic limiting and shaping.

Table 7-4 Data to prepare for configuring traffic limiting and shapingMO Parameter

NameParameter ID Setting Notes Data Source

IPLOGICPORT Logic Port No. LPN(BSC6900,BSC6910)

Set thisparameter to thenumber of theBSC/RNClogical port.

Network plan



41

MO ParameterName

Parameter ID Setting Notes Data Source

Bandwidth CIR(BSC6900,BSC6910)

Set thisparameter to theaccessbandwidthplanned by theoperator orbandwidthcalculated bythe trafficmodel. Whenthe accessbandwidth islimited for eachoperator in RANsharingscenarios, setthis parameter tothe accessbandwidthplanned by eachoperator.

Network plan

Transport QoSl Transport QoS for GSM services

Table 7-5 lists the data to prepare for configuring the mapping between DSCP valuesand data from the O&M plane, CP, and UP of a GBTS. Table 7-6 lists the data to prepare for configuring the mapping between DSCP values

and data from the O&M plane and CP of an eGBTS. Table 7-8 lists the data to prepare for configuring the mapping between DSCP values

and data from the O&M plane and CP of a BSC. Table 7-9 lists the data to prepare forconfiguring the mapping between DSCP values and data from the UP of a BSC.

l Transport QoS for UMTS services Table 7-6 lists the data to prepare for configuring the mapping between DSCP values

and data from the O&M plane and CP of a NodeB. Table 7-10 lists the data to prepare for configuring the mapping between DSCP values

and data from the O&M plane, CP, and UP of an RNC.l Transport QoS for LTE services

Table 7-6 lists the data to prepare for configuring the mapping between DSCP valuesand data from the O&M plane and CP of an eNodeB. Table 7-7 lists the data to prepare for configuring the mapping between DSCP values

and data from the UP of an eNodeB.



42

Table 7-5 Data to prepare for configuring the mapping between DSCP values and data from theO&M plane, CP, and UP of a GBTS

MO ParameterName


BTSVLAN Service Type SERVICETYPE

See therecommendedparameterconfigurationsin chapter 4ApplicationScenarios.

Network plan

DSCP DSCP

Table 7-6 Data to prepare for configuring the mapping between DSCP values and data from theO&M plane and CP of the eGBTS, NodeB, and eNodeB side of a co-MPT multimode basestation

MO ParameterName


DIFPRI Priority Rule PRIRULE Set thisparameter to theDSCP value.

Network plan

SignalingPriority

SIGPRI See therecommendedparameterconfigurationsin chapter 4ApplicationScenarios.

OM HighPriority

OMHIGHPRI

OM LowPriority

OMLOWPRI

IP ClockPriority

IPCLKPRI



43

Table 7-7 Data to prepare for configuring the mapping between DSCP values and data from theUP of an eNodeB

MO ParameterName


UDTPARAGRP

User Data TypeTransferParameterGroup ID

UDTPARAGRPID

Set thisparameter to4048. Thisvaluecorresponds tothe value of theUser DataType (19) bydefault.

Network plan

Priority PRI See therecommendedparameterconfigurationsin chapter 4ApplicationScenarios.

Network plan

Table 7-8 Data to prepare for configuring the mapping between DSCP values and data from theO&M plane and CP of a BSC

MO ParameterName


BSCABISPRIMAP

OML DSCP OMLDSCP See therecommendedparameterconfigurationsin chapter 4ApplicationScenarios.

Network planRSL DSCP RSLDSCP Network planEML DSCP EMLDSCP Network planESL DSCP ESLDSCP Network plan

Table 7-9 Data to prepare for configuring the mapping between DSCP values and data from theUP of a BSC

MO ParameterName


TRMMAP CS voice path CSVOICEPATH

See therecommendedparameterconfigurationsin chapter 4

Network plan

CS data path CSDATAPATH

Network plan



44

MO ParameterName


PS high PRIdata path

ApplicationScenarios.

PSHPRIDATAPATH

Network plan

PS low PRI datapath

PSLPRIDATAPATH

Network plan

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

MO ParameterName


TRMMAP Commonchannel primarypath

CCHPRIPATH See therecommendedparameterconfigurationsin chapter 4ApplicationScenarios.

Network plan

IMS SRBprimary path

SIPPRIPATH Network plan

SRB primarypath

SRBPRIPATH Network plan

AMR voiceprimary path

VOICEPRIPATH

Network plan

R99 CSconversationalprimary path

CSCONVPRIPATH

Network plan

R99 CSstreamingprimary path

CSSTRMPRIPATH

Network plan

R99 PSconversationalprimary path

PSCONVPRIPATH

Network plan

R99 PSstreamingprimary path

PSSTRMPRIPATH

Network plan

R99 PS highPRI interactiveprimary path

PSINTHGHPRIPATH

Network plan

R99 PS middlePRI interactiveprimary path

PSINTMIDPRIPATH

Network plan



45

MO ParameterName


R99 PS low PRIinteractiveprimary path

PSINTLOWPRIPATH

Network plan

R99 PSbackgroundprimary path

PSBKGPRIPATH

Network plan

HSDPA Signalprimary path

HDSRBPRIPATH

Network plan

HSDPA IMSSignal primarypath

HDSIPPRIPATH

Network plan

HSDPA Voiceprimary path

HDVOICEPRIPATH

Network plan

HSDPAconversationalprimary path

HDCONVPRIPATH

Network plan

HSDPAstreamingprimary path

HDSTRMPRIPATH

Network plan

HSDPA highPRI interactiveprimary path

HDINTHGHPRIPATH

Network plan

HSDPA middlePRI interactiveprimary path

HDINTMIDPRIPATH

Network plan

HSDPA lowPRI interactiveprimary path

HDINTLOWPRIPATH

Network plan

HSDPAbackgroundprimary path

HDBKGPRIPATH

Network plan

HSUPA Signalprimary path

HUSRBPRIPATH

Network plan

HSUPA IMSSignal primarypath

HUSIPPRIPATH

Network plan

HSUPA Voiceprimary path

HUVOICEPRIPATH

Network plan



46

MO ParameterName


HSUPAconversationalprimary path

HUCONVPRIPATH

Network plan

HSUPAstreamingprimary path

HUSTRMPRIPATH

Network plan

HSUPA highPRI interactiveprimary path

HUINTHGHPRIPATH

Network plan

HSUPA middlePRI interactiveprimary path

HUINTMIDPRIPATH

Network plan

HSUPA lowPRI interactiveprimary path

HUINTLOWPRIPATH

Network plan

HSUPAbackgroundsecondary path

HUBKGPRIPATH

Network plan

Flow ControlTable 7-11 lists the data to prepare for setting the flow control algorithm on the NodeB side.

Table 7-11 Data to prepare for setting the flow control algorithm on the NodeB sideMO Parameter

NameParameter ID Setting

DescriptionData Source

RSCGRPALG Traffic ControlSwitch

TCSW See therecommendedparameterconfigurationsin chapter 4ApplicationScenarios.

Negotiated bythe peer end

ULFLOWCTRLPARA

Congestion CtrlSwitch

TNLCONGCTRLSWITCH

See therecommendedparameterconfigurationsin chapter 4ApplicationScenarios.

Negotiated bythe peer end

DLFLOWCTRLPARA

Flow ControlSwitch

SWITCH

Fair Switch FAIRSWITCH



47

Other DataTable 7-12 lists other data to prepare if access bandwidth is limited for multimode base stations.

Table 7-12 Other data to prepare if access bandwidth is limited for multimode base stationsData Item Sample Value RemarksLimited access bandwidth fora base station

20 Mbit/s This data specifies the uplinkand downlink limited accessbandwidth for a base station.

Downlink bandwidth on thelogical port of the BSC

10 Mbit/s Calculates the bandwidth forthis port based on the trafficmodel of the multimode basestation.

BTS index 1 NoneLogical IP address of theBTS

16.16.90.201 None

Port IP address of the BSC 172.16.140.140 NoneLogical IP address of theNodeB

16.16.70.201 None

IP address of an Iub port onthe RNC side

172.16.100.140 None

Table 7-13 lists other data to prepare if access bandwidth is limited for each operator in RANsharing scenarios.

Table 7-13 Other data to prepare if access bandwidth is limited for each operator in RAN sharingscenarios

Data Item Sample Value RemarksLimited access bandwidth foroperator A

10 Mbit/s This data specifies the uplinkand downlink limited accessbandwidth for operator A.

Limited access bandwidth foroperator B

10 Mbit/s This data specifies the uplinkand downlink limited accessbandwidth for operator B.

Logical IP address of theNodeB (for operator A)

16.16.70.201 None

Logical IP address of theNodeB (for operator B)

16.16.60.201 None



48

Data Item Sample Value RemarksLogical IP address of theeNodeB (for operator A)

16.15.70.201 None

Logical IP address of theeNodeB (for operator B)

16.15.60.201 None

Logical IP address of an Iubport on the RNC side (foroperator A)

172.16.90.140 None

Logical IP address of an Iubport on the RNC side (foroperator B)

172.16.80.140 None

Logical IP address of theserving gateway (S-GW) (foroperator A)

172.15.90.140 None

Logical IP address of theserving gateway (S-GW) (foroperator B)

172.15.80.140 None

7.4.3 PrecautionsNone

7.4.4 Hardware AdjustmentN/A

7.4.5 Initial Configuration (Unlimited Access Bandwidth for GUDual-Mode Base Stations)Using MML Commands

Step 1 Configure a transport resource mapping (TRM) table on the base station controller side.Configure a TRM table for the RNC and BSC, respectively. For details, see section 4.1.2Transmission Resource Management Strategies.1. Run the ADD TRMMAP command to set the mapping between DSCP values and data

from the UP and CP on the Iub interface.2. Run the ADD TRMMAP command to set the mapping between DSCP values and data

from the UP on the Abis interface.3. Run the SET BSCABISPRIMAP command to set the mapping between DSCP values and

data from the CP on the Abis interface.



49

4. Run the ADD ADJMAP command to add the mapping from the Iub interface to theTRMMAP index.

5. Run the ADD ADJMAP command to add the mapping from the Abis interface to theTRMMAP index.

Step 2 Configure a TRM table on the base station side.Configure a TRM table for the GBTS/eGBTS and NodeB, respectively. For details, see section4.1.2 Transmission Resource Management Strategies.1. Run the SET BTSVLAN command to set the mapping between DSCP values and data

from the CP and UP of the GBTS. Run the SET DIFPRI command to set the mappingbetween DSCP values and data from the CP of the eGBTS.

2. Run the SET DIFPRI command to set the mapping between DSCP values and data fromthe CP of the NodeB.

Step 3 Configure the dynamic flow control algorithm for the NodeB.1. Run the ADD ULFLOWCTRLPARA command to add an HSUPA flow control parameter

to set the uplink bandwidth adaptive flow control switch.2. Run the ADD DLFLOWCTRLPARA command to add an HSDPA flow control parameter

to set the HSDPA flow control switch.----End

MML Command Examples//Con

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

Documents

Transcript of Bandwidth Sharing of Multimode Base Station Co-Transmission(SRAN9.0_01).pdf