bandwidth sharing of multimode base station co-transmission(sran9.0_draft a)

SingleRAN

Bandwidth Sharing of MultimodeBase Station Co-TransmissionFeature Parameter Description

Issue Draft A

Date 2014-01-20

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

Email: [email protected]

Issue Draft A (2014-01-20) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

Contents

1 About This Document..................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................2

2 Overview.........................................................................................................................................32.1 Introduction....................................................................................................................................................................32.2 Benefits...........................................................................................................................................................................32.3 Application Networking.................................................................................................................................................4

3 Technical Description...................................................................................................................63.1 Introduction....................................................................................................................................................................63.2 Transmission Priorities...................................................................................................................................................73.3 Traffic Limiting and Shaping.......................................................................................................................................103.4 Load Control.................................................................................................................................................................113.5 Flow Control.................................................................................................................................................................12

4 Application Scenarios.................................................................................................................154.1 Unlimited Access Bandwidth for Multimode Base Stations........................................................................................154.1.1 Introduction...............................................................................................................................................................154.1.2 Transmission Resource Management Strategies.......................................................................................................164.2 Limited Access Bandwidth for Multimode Base Stations............................................................................................204.2.1 Introduction...............................................................................................................................................................204.2.2 Transmission Resource Management Strategies.......................................................................................................214.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios.................................................................294.3.1 Introduction...............................................................................................................................................................294.3.2 Transmission Resource Management Strategies.......................................................................................................29

5 Related Features...........................................................................................................................345.1 Prerequisite Features.....................................................................................................................................................345.2 Mutually Exclusive Features........................................................................................................................................345.3 Impacted Features.........................................................................................................................................................34

6 Network Impact...........................................................................................................................356.1 System Capacity...........................................................................................................................................................35

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


ii

6.2 Network Performance...................................................................................................................................................35

7 Engineering Guidelines.............................................................................................................367.1 When to Use Bandwidth Sharing of Multimode Base Station Co-Transmission.........................................................367.2 Required Information...................................................................................................................................................367.3 Planning........................................................................................................................................................................367.4 Deployment..................................................................................................................................................................377.4.1 Requirements.............................................................................................................................................................377.4.2 Data Preparation........................................................................................................................................................387.4.3 Precautions.................................................................................................................................................................487.4.4 Hardware Adjustment................................................................................................................................................487.4.5 Initial Configuration (Unlimited Access Bandwidth for GU Dual-Mode Base Stations).........................................487.4.6 Initial Configuration (Unlimited Access Bandwidth for GL/GT Dual-Mode Base Stations)...................................517.4.7 Initial Configuration (Unlimited Access Bandwidth for UL/UT/ULT Multimode Base Stations)...........................537.4.8 Initial Configuration (Unlimited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)..................557.4.9 Initial Configuration (Limited Access Bandwidth for GU Dual-Mode Base Stations).............................................587.4.10 Initial Configuration (Limited Access Bandwidth for GL/GT/GLT Multimode Base Stations)............................637.4.11 Initial Configuration (Limited Access Bandwidth for UL/UT/ULT Multimode Base Stations)............................667.4.12 Initial Configuration (Limited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)....................707.4.13 Initial Configuration (Limited Access Bandwidth for Each Operator in a UL/UT Dual-Mode Base Station in RANSharing Scenarios)..............................................................................................................................................................767.4.14 Activation Observation (Unlimited Access Bandwidth for Multimode Base Stations)..........................................847.4.15 Activation Observation (Limited Access Bandwidth for Multimode Base Stations)..............................................857.4.16 Activation Observation (Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios)...................897.5 Performance Monitoring...............................................................................................................................................917.6 Parameter Optimization................................................................................................................................................917.7 Troubleshooting............................................................................................................................................................91

8 Parameters.....................................................................................................................................92

9 Counters......................................................................................................................................174

10 Glossary.....................................................................................................................................175

11 Reference Documents.............................................................................................................176

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


iii

1 About This Document

1.1 ScopeThis 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 Only

LTE LTE FDD LTE TDD

eNodeB LTE FDD eNodeB LTE TDD eNodeB

eRAN LTE FDD eRAN LTE TDD eRAN

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

1.2 Intended 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 changeChanges in features of a specific product version

l Editorial changeChanges in wording or addition of information that was not described in the earlier version

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.

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


2

2 Overview

2.1 IntroductionThe 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 resources

GSM, 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


3

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 entity

S-GW: serving gateway

MPT: main processing and transmission unit

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

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

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



4

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.



5

3 Technical Description

3.1 IntroductionFor 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 stations

Base Station Name Definition

GBTS GBTS refers to a base station deployed with GTMU.

eGBTS eGBTS refers to a base station deployed with UMPT_G.

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


6

Base Station Name Definition

NodeB NodeB refers to a base station deployed with WMPT orUMPT_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.

DSCP

DSCP 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



7

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 Description

GBTS SET BTSVLAN Used to set the mappingbetween 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 necessaryMML 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.



8

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 priorities

DSCP Value VLAN Priority

0–7 0

8–15 1

16–23 2

24–31 3

32–39 4

40–47 5

48–55 6

56–63 7

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



9

Table 3-4 Default mapping between DSCP values and queue priorities for the GBTS

DSCP Value Queue Queue Priority

40–63 PQ1 0

Reserved PQ2 1

Reserved PQ3 2

32–39 WFQ4 3

24–31 WFQ5 3

16–23 WFQ6 3

8–15 WFQ7 3

0–7 WFQ8 3

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

DSCP Value Queue Queue Priority

48–63 PQ1 0

40–47 PQ2 1

32–39 PQ3 2

24–31 WFQ4 3

16–23 WFQ5 3

8–15 WFQ6 3

0–7 WFQ7 3

3.3 Traffic Limiting and 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.



10

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 station

If 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 controller

You can run the ADD IPLOGICPORT command and specify the CIR parameter to setthe 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 logicalport 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 datashaping.

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

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



11

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 algorithm

Mode NE Support FlowControl

Remarks

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



12

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 LTEservices 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 andLTE 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



13

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.



14

4 Application Scenarios

4.1 Unlimited Access Bandwidth for Multimode BaseStations

4.1.1 IntroductionUnlimited 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


15

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 Priorities

Table 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 6

CS Voice EF 46 5

CS Data/PSHigh PRI

AF41 34 4

PS Low PRI AF31 26 3

IP Clock EF 46 5

EML AF21 18 2

eGBTS SCTP CS6 48 6

CS Voice EF 46 5

CS Data/PSHigh PRI

AF41 34 4


OM High EF 46 5

OM Low AF21 18 2

IP Clock EF 46 5

NodeB Iub Signal CS6 48 6



16


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 5

OM Low AF21 18 2

IP Clock EF 46 5

eNodeB SCTP CS6 48 6

QCI1 EF 46 5

QCI2 AF41 34 4

QCI3 AF41 34 4

QCI4 AF41 34 4

QCI5 EF 46 5

QCI6 AF21 18 2

QCI7 AF21 18 2

QCI8 AF21 18 2

QCI9 BE 0 0

OM High EF 46 5

OM Low AF21 18 2

IP Clock EF 46 5

In most cases, transmission devices support queue scheduling. Layer 3 and Layer 2 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.



17

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 Algorithm

Table 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 station

Separate-MPT GLdual-mode basestation

N/A N/A N/A

Co-MPT GL dual-mode base station



18




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)



19




Separate-MPT GULtriple-mode basestation



N/A

Co-MPT GUL triple-mode base station



ENABLE(Enable)

4.2 Limited Access Bandwidth for Multimode Base Stations

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



20

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 Side

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



21

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 6

CS Voice EF 46 5

CS Data/PSHigh PRI

AF41 34 4


IP Clock CS6 46 6

EML AF21 18 2

eGBTS SCTP CS6 48 6

CS Voice EF 46 5

CS Data/PSHigh PRI

AF41 34 4


OM High EF 46 5

OM Low AF21 18 2

IP Clock CS6 46 6


CCH&SRB&AMR

EF 46 5


AF41 34 4


AF21 18 2


AF11 10 1

OM High EF 46 5

OM Low AF21 18 2



22


IP Clock EF 46 5


QCI1 EF 46 5

QCI2 AF41 34 4

QCI3 AF41 34 4

QCI4 AF41 34 4

QCI5 EF 46 5

QCI6 AF21 18 2

QCI7 AF21 18 2

QCI8 AF21 18 2

QCI9 BE 0 0

OM High EF 46 5

OM Low AF21 18 2

IP Clock EF 46 5

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.



23







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

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



24

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



25

Base StationType





Co-MPT ULdual-mode basestation




ENABLE(Enable)



26

Base StationType





Separate-MPTGUL triple-mode basestation

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

l DISABLE(Disable):ifco-transmissionisimplemented throughpanelinterconnection



N/A



27

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.



28

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

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 Side

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



29

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 Values

Table 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



CCH&SRB&AMR

EF 46 5


AF41 34 4


AF21 18 2


AF11 10 1

OM High EF 46 5

OM Low AF21 18 2

IP Clock EF 46 5


QCI1 EF 46 5

QCI2 AF41 34 4

QCI3 AF41 34 4

QCI4 AF41 34 4

QCI5 EF 46 5

QCI6 AF21 18 2

QCI7 AF21 18 2

QCI8 AF21 18 2



30


QCI9 BE 0 0

OM High EF 46 5

OM Low AF21 18 2

IP Clock EF 46 5

In most cases, transmission devices support queue scheduling. Layer 3 and Layer 2 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.





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



31

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



32

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.



33

5 Related Features

5.1 Prerequisite Featuresl 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


34

6 Network Impact

6.1 System CapacityNo 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


35

7 Engineering Guidelines

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

N/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 services

For 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


36

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 mapping

Plan 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 network

Plan 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 network

Plan 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 Planning

N/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 twoPQ 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-modeCo-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.



37

– 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 License

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

Table 7-1 License control items

Feature 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 Preparation

Traffic 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



38

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



39

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 shaping

MO ParameterName

Parameter ID Setting Notes Data Source

IPLOGICPORT Logic Port No. LPN Set thisparameter to thenumber of theBSC/RNClogical port.

Network plan



40

MO ParameterName


Bandwidth CIR 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 valuesand 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 valuesand 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 valuesand 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 valuesand 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 valuesand data from the UP of an eNodeB.



41

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



42

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 to40–48. Thisvaluecorresponds tothe value of theUser DataType (1–9) 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 plan

RSL DSCP RSLDSCP Network plan

EML DSCP EMLDSCP Network plan

ESL 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



43

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



44

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



45

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 side

MO ParameterName

Parameter ID SettingDescription

Data 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



46

Other Data

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

Table 7-12 Other data to prepare if access bandwidth is limited for multimode base stations

Data Item Sample Value Remarks

Limited access bandwidth 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 None

Logical IP address of theBTS

16.16.90.201 None

Port IP address of the BSC 172.16.140.140 None

Logical 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


Limited 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



47


Logical 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 datafrom the UP and CP on the Iub interface.

2. Run the ADD TRMMAP command to set the mapping between DSCP values and datafrom the UP on the Abis interface.

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



48

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 datafrom 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 parameterto set the uplink bandwidth adaptive flow control switch.

2. Run the ADD DLFLOWCTRLPARA command to add an HSDPA flow control parameterto set the HSDPA flow control switch.

----End

MML Command Examples//Configuring a TRM table on the base station controller side

//Setting the mapping between DSCP values and data from the CP and UP on the Iub interface

ADD TRMMAP:TMI=110,ITFT=IUB,TRANST=IP,CCHPRIPATH=EF,SIPPRIPATH=EF,SRBPRIPATH=EF,VOICEPRIPATH=EF,CSCONVPRIPATH=AF41,CSSTRMPRIPATH=AF41,PSCONVPRIPATH=AF41,PSSTRMPRIPATH=AF41,PSINTHGHPRIPATH=AF21,PSINTLOWPRIPATH=AF21,PSBKGPRIPATH=AF21,HDSRBPRIPATH=EF,HDSIPPRIPATH=EF,HDVOICEPRIPATH=EF,HDCONVPRIPATH=AF41,HDSTRMPRIPATH=AF41,HDINTHGHPRIPATH=AF11,HDINTMIDPRIPATH=AF11,HDINTLOWPRIPATH=AF11,HDBKGPRIPATH=AF11,HUSRBPRIPATH=EF,HUSIPPRIPATH=EF,HUVOICEPRIPATH=EF,HUCONVPRIPATH=AF41,HUSTRMPRIPATH=AF41,HUINTHGHPRIPATH=AF11,HUINTMIDPRIPATH=AF11,HUINTLOWPRIPATH=AF11,HUBKGPRIPATH=AF11;

//Setting the mapping between DSCP values and data from the UP on the Abis interface

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

//Setting the mapping between DSCP values and data from the CP on the Abis interface

SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=1, TRANSTYPE=IP, OMLDSCP=48, RSLDSCP=48, EMLDSCP=18, ESLDSCP=48;

//Adding the mapping from the Iub interface to the TRMMAP index

ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110, TMIBRZ=110, FTI=1;

//Adding the mapping from the Abis interface to the TRMMAP index

ADD ADJMAP: ANI=3, ITFT=ABIS, TMIGLD=111, FTI=1;

//Configuring a TRM table on the base station side



49

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

SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=OML, DSCP=48;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=RSL, DSCP=48;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=EML, DSCP=18;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=ESL, DSCP=48;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSVOICE, DSCP=46;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSDATA, DSCP=34;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= PSHIGHPRI, DSCP=34;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= PSLOWPRI, DSCP=26;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= OTHERDATA, DSCP=46;

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

SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;

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


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

//Adding an HSUPA flow control parameter

ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;

//Adding an HSDPA flow control parameter

ADD DLFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, SWITCH=BW_SHAPING_ONOFF_TOGGLE;

Single Configuration Using the CME

The parameters related to this feature cannot be modified in batches. This section only describeshow to use the CME to perform a single configuration.

Set parameters on the CME configuration interface according to the operation sequencedescribed in Table 7-14. For instructions on how to perform the CME single configuration, seeCME Single Configuration Operation Guide.

Table 7-14 MOs related to this feature

SN MO NE

1 a TRMMAP BSC and RNC

b BSCABISPRIMAP BSC

c ADJMAP BSC and RNC

2 a BTSVLAN/DIFPRI GBTS or eGBTS

b DIFPRI NodeB

3 a ULFLOWCTRLPARA

NodeB



50

SN MO NE

b DLFLOWCTRLPARA

NodeB

7.4.6 Initial Configuration (Unlimited Access Bandwidth for GL/GT Dual-Mode Base Stations)

Using MML Commands

Step 1 Configure a TRM table on the base station controller side.

Configure a TRM table for the BSC. For details, see section 4.1.2 Transmission ResourceManagement Strategies.





Configure a TRM table for the GBTS/eGBTS and eNodeB, 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 datafrom 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 eNodeB.

3. Run the MOD UDTPARAGRP command to set the mapping between DSCP values anddata from the UP of the eNodeB.

----End









51



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


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


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


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

MOD UDTPARAGRP: UDTPARAGRPID=40, PRIRULE=DSCP, PRI=46, ACTFACTOR=100;MOD UDTPARAGRP: UDTPARAGRPID=41, PRIRULE=DSCP, PRI=26, ACTFACTOR=100;MOD UDTPARAGRP: UDTPARAGRPID=42, PRIRULE=DSCP, PRI=34, ACTFACTOR=100;MOD UDTPARAGRP: UDTPARAGRPID=43, PRIRULE=DSCP, PRI=26, ACTFACTOR=100;MOD UDTPARAGRP: UDTPARAGRPID=44, PRI=46;MOD UDTPARAGRP: UDTPARAGRPID=45, PRI=18;MOD UDTPARAGRP: UDTPARAGRPID=46, PRI=18;MOD UDTPARAGRP: UDTPARAGRPID=47, PRI=18;MOD UDTPARAGRP: UDTPARAGRPID=48, PRI=0;

Single Configuration Using the CMEThe parameters related to this feature cannot be modified in batches. This section only describeshow to use the CME to perform a single configuration.



SN MO NE

1 a TRMMAP BSC

b BSCABISPRIMAP BSC

c ADJMAP BSC


b DIFPRI eNodeB

c UDTPARAGRP eNodeB



52

7.4.7 Initial Configuration (Unlimited Access Bandwidth for UL/UT/ULT Multimode Base Stations)

Using MML Commands


Configure a TRM table for the RNC. For details, see section 4.1.2 Transmission ResourceManagement Strategies.




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

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

3. Run the MOD UDTPARAGRP command to set the mapping between DSCP values anddata from the UP of the eNodeB.




----End







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



53


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


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


//Configuring the dynamic flow control algorithm for the NodeB

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


ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON; //In the case of a separate-MPT multimode base station



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


ADD DLFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, SWITCH=BW_SHAPING_ONOFF_TOGGLE, FAIRSWTICH=ENABLE;

//If the bearer network supports two queues


ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=OFF;

//Adding an HSDPA flow control parameter in the case of a separate-MPT multimode basestation

ADD DLFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, SWITCH= NO_BW_SHAPING;

//Adding an HSDPA flow control parameter in the case of a co-MPT multimode base station

ADD DLFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, SWITCH= NO_BW_SHAPING, FAIRSWTICH=ENABLE;





54



SN MO NE

1 a TRMMAP RNC

b ADJMAP RNC

2 a DIFPRI NodeB

b DIFPRI eNodeB

c UDTPARAGRP eNodeB

3 a ULFLOWCTRLPARA

NodeB

b DLFLOWCTRLPARA

NodeB

7.4.8 Initial Configuration (Unlimited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)

Using MML Commands









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



55

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

3. Run the SET DIFPRI command to set the mapping between DSCP values and data fromthe CP of an eNodeB.

4. Run the MOD UDTPARAGRP command to set the mapping between DSCP values anddata from the UP of an eNodeB.




----End














SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=OML, DSCP=48;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=RSL, DSCP=48;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=EML, DSCP=18;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE=ESL, DSCP=48;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSVOICE, DSCP=46;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= CSDATA, DSCP=34;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= PSHIGHPRI, DSCP=34;



56

SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= PSLOWPRI, DSCP=26;SET BTSVLAN: IDTYPE=BYID, BTSID=1, SERVICETYPE= OTHERDATA, DSCP=46;



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







//If the bearer network supports three or more queues


ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP,PT=ETH, PN=0, BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;

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















57





SN MO NE

1 a TRMMAP BSC

b TRMMAP RNC

c BSCABISPRIMAP BSC

d ADJMAP BSC

e ADJMAP RNC


b DIFPRI NodeB

c DIFPRI eNodeB

d UDTPARAGRP eNodeB

3 a ULFLOWCTRLPARA

NodeB

b DLFLOWCTRLPARA

NodeB

7.4.9 Initial Configuration (Limited Access Bandwidth for GUDual-Mode Base Stations)

Using MML Commands

Step 1 Configure traffic limiting and shaping on the co-transmission port.

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

l Run the SET LR command to configure traffic limiting and shaping if a co-MPT multimodebase station provides a co-transmission port.

Step 2 Configure logical ports on the base station controller side.

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

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



58

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

l For a GBTS, you can run the SET BTSIP command to bind an IP logical port and aGBTS.

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

l For an eGBTS, you can run the ADD ADJLOGICPORTBIND command to bind anadjacent node and an IP logical port if the peer end is a BSC6910.

4. Bind a user-plane link and an IP logical port on the Iub interface.

l If the transmission resource pool feature is not implemented on the Iub interface, you canrun the ADD IPPATH command to bind an IP path and an IP logical port.

l If the transmission resource pool feature is implemented on the Iub interface, you can runthe ADD ADJLOGICPORTBIND command to bind an adjacent node and an IP logicalport.









Configure a TRM table for the GBTS/eGBTS and NodeB, respectively. For details, see section4.2.2 Transmission Resource Management Strategies.






----End



59

MML Command Examples//Configuring traffic limiting and shaping on the co-transmission port

//Configuring traffic limiting and shaping if the eGBTS side of a separate-MPT multimode basestation provides a co-transmission port

SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000, EBS=0;

//Configuring traffic limiting and shaping if the NodeB side of a separate-MPT multimode basestation provides a co-transmission port


//Configuring traffic limiting and shaping if a co-MPT multimode base station provides a co-transmission port


//Configuring logical ports on the base station controller side

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

ADD IPLOGICPORT: SRN=1, SN=24, BT=GOUc, LPNTYPE=Leaf, LPN=1, CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=157, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;

//In the preceding script, the unit of bandwidth configured on a logical port is 64 kbit/s. Therefore,the CIR value 157 means that the configured bandwidth is 10,048 kbit/s.


ADD IPLOGICPORT: SRN=1, SN=24, BT=GOUc, LPNTYPE=Leaf, FLOWCTRLSWITCH=ON, CIR=157, LPN=1, CARRYT=IPPOOL, IPADDR="172.16.140.140";//In the preceding script, the unit of bandwidth configured on a logical port is 64 kbit/s. Therefore, the CIR value 157 means that the configured bandwidth is 10,048 kbit/s.

//Adding a logical port on the Iub interface

ADD IPLOGICPORT: SRN=1, SN=26, BT=GOUc, LPNTYPE=Leaf, LPN=1, CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=313, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;

//In the preceding script, the unit of bandwidth configured on a logical port is 64 kbit/s. Therefore,the CIR value 313 means that the configured bandwidth is 20,032 kbit/s.

//For a GBTS, binding an IP logical port and a GBTS on the Abis interface

SET BTSIP: IDTYPE=BYID, BTSID=1, BTSCOMTYPE=LOGICIP, BTSIP="16.16.90.201", BSCIP="172.16.140.140", CFGFLAG=IPLGCPORT, SN=24, LPN=1;

//In the preceding script, the base station is identified by its base station index.

//For an eGBTS, binding an IP path and an IP logical port on the Abis interface if the peer endis a BSC6900

ADD IPPATH: ANI=3, PATHID=0, ITFT=ABIS, ISLOGICALBTS=No, PATHT=QoS, TXBW=10000, RXBW=10000, VLANFlAG=DISABLE, PATHCHK=DISABLED, AbisLnkBKFLAG=OFF;

//For an eGBTS, binding an adjacent node and an IP logical port on the Abis interface if the peerend is a BSC6910

ADD ADJLOGICPORTBIND: ANI=3, SRN=1, SN=24, LPN=1;



60

//Binding an IP path and an IP logical port if the transmission resource pool feature is notimplemented on the Iub interface

ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS, IPADDR="172.16.100.140", PEERIPADDR="16.16.70.201", TXBW=20000, RXBW=20000, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;

//Binding an adjacent node and an IP logical port if the transmission resource pool feature isimplemented on the Iub interface


//Configuring a TRM table on the base station controller side












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


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


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




61

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


ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;







SN MO NE

1 a LR/LR/LR eGBTS, NodeB, orco-MPT multimodebase stations

2 a IPLOGICPORT BSC and RNC

b BTSIP/IPPATH/ADJLOGICPORTBIND

BSC

c IPPATH/ADJLOGICPORTBIND

RNC

3 a TRMMAP BSC and RNC

b BSCABISPRIMAP BSC

c ADJMAP BSC and RNC


b DIFPRI NodeB

5 a ULFLOWCTRLPARA

NodeB

b DLFLOWCTRLPARA

NodeB



62

7.4.10 Initial Configuration (Limited Access Bandwidth for GL/GT/GLT Multimode Base Stations)

Using MML Commands

Step 1 Configure traffic limiting and shaping on the co-transmission port.l Run the SET LR command to configure traffic limiting and shaping if the eGBTS or eNodeB

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

base station provides a co-transmission port.


1. Run the ADD IPLOGICPORT command to add an IP logical port on the Abis interface.2. Bind a user-plane link and an IP logical port on the Abis interface.

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

port if the peer end is a BSC6900.l For an eGBTS, you can run the ADD ADJLOGICPORTBIND command to bind an

adjacent node and an IP logical port if the peer end is a BSC6910.


Configure a TRM table for the BSC. For details, see section 4.2.2 Transmission ResourceManagement Strategies.





Configure a TRM table for the GBTS/eGBTS and eNodeB, respectively. For details, see section4.2.2 Transmission Resource Management Strategies.




----End




63



//Configuring traffic limiting and shaping if the eNodeB side of a separate-MPT multimode basestation provides a co-transmission port






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


ADD IPLOGICPORT: SRN=1, SN=24, BT=GOUc, LPNTYPE=Leaf, FLOWCTRLSWITCH=ON, CIR=157, LPN=1, CARRYT=IPPOOL, IPADDR="172.16.140.140";//In the preceding script, the unit of bandwidth configured on a logical port is 64 kbit/s. Therefore, the CIR value 157 means that the configured bandwidth is 10,048 kbit/s.


SET BTSIP: IDTYPE=BYID, BTSID=1, BTSCOMTYPE=LOGICIP, BTSIP="16.16.90.201", BSCIP="172.16.140.140", CFGFLAG=IPLGCPORT, SN=24, LPN=1;//In the preceding script, the base station is identified by its base station index.













64















SN MO NE

1 a LR/LR/LR eGBTS, eNodeB, orco-MPT multimodebase stations

2 a IPLOGICPORT BSC


BSC

3 a TRMMAP BSC



65

SN MO NE

b BSCABISPRIMAP BSC

c ADJMAP BSC


b DIFPRI eNodeB

c UDTPARAGRP eNodeB

7.4.11 Initial Configuration (Limited Access Bandwidth for UL/UT/ULT Multimode Base Stations)

Using MML Commands


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





l If the transmission resource pool feature is not implemented on the Iub interface, you canrun the ADD IPPATH command to bind an IP path and an IP logical port on the Iub interface.

l If the transmission resource pool feature is implemented on the Iub interface, you can runthe ADD ADJLOGICPORTBIND command to bind an adjacent node and an IP logicalport on the Iub interface.










66





Step 6 Disable the traffic control switch of the default transport resource group configured on the co-transmission port.

If the NodeB or eNodeB side of a separate-MPT multimode base station provides a co-transmission port and co-transmission is implemented through panel interconnection, the trafficcontrol switch for a transport resource group must be disabled on the co-transmission port.Otherwise, when transmission resources become congested, passing data will preemptbandwidth from the local data. This deteriorates user experience.

1. Run the ADD RSCGRP command to configure a default transport resource group on theco-transmission port.

2. Run the SET RSCGRPALG command to disable the traffic control switch of the defaulttransport resource group you have configured.

----End










ADD IPLOGICPORT: SRN=1, SN=26, BT=GOUc, LPNTYPE=Leaf, LPN=1, CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=313, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;//In the preceding script, the unit of bandwidth configured on a logical port is 64 kbit/s. Therefore, the CIR value 313 means that the configured bandwidth is 20,032 kbit/s.




67

























68











//Disabling the traffic control switch of the default transport resource group configured on theco-transmission port

//Configuring a default transport resource group on the co-transmission port in a separate-MPTmultimode base station where co-transmission is implemented through panel interconnection

ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT, RU=KBPS;

//Disabling the traffic control switch on the default transport resource group you have configured

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





SN MO NE

1 a LR/LR/LR NodeB, eNodeB, orco-MPT multimodebase stations

2 a IPLOGICPORT RNC

b IPPATH/ADJLOGICPORTBIND

RNC



69

SN MO NE

3 a TRMMAP RNC

b ADJMAP RNC

4 a DIFPRI NodeB

b DIFPRI eNodeB

c UDTPARAGRP eNodeB

5 a ULFLOWCTRLPARA

NodeB

b DLFLOWCTRLPARA

NodeB

6 a RSCGRP NodeB, eNodeB, ormultimode basestations

b RSCGRPALG NodeB, eNodeB, ormultimode basestations

7.4.12 Initial Configuration (Limited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)

Using MML Commands


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



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


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

l For a GBTS, you can run the SET BTSIP command to bind an IP logical port and aGBTS.

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

l For an eGBTS, you can run the ADD ADJLOGICPORTBIND command to bind anadjacent node and an IP logical port if the peer end is a BSC6910.




70

l If the transmission resource pool feature is not implemented on the Iub interface, you canrun the ADD IPPATH command to bind an IP path and an IP logical port.

l If the transmission resource pool feature is implemented on the Iub interface, you can runthe ADD ADJLOGICPORTBIND command to bind an adjacent node and an IP logicalport.


Configure a TRM table for the RNC and BSC, respectively. For details, see 4.2.2 TransmissionResource Management Strategies.















If the NodeB or eNodeB side of a separate-MPT multimode base station provides a co-transmission port and co-transmission is implemented through panel interconnection, the trafficcontrol switch for a transport resource group must be disabled on the co-transmission port.Otherwise, when transmission resources become congested, passing data will preemptbandwidth from the local data. This deteriorates user experience.

1. Run the ADD RSCGRP command to configure a default transport resource group on theco-transmission port.



71

2. Run the SET RSCGRPALG command to disable the traffic control switch of the defaulttransport resource group you have configured.

----End












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


ADD IPLOGICPORT: SRN=1, SN=24, BT=GOUc, LPNTYPE=Leaf, FLOWCTRLSWITCH=ON, CIR=157, LPN=1, CARRYT=IPPOOL, IPADDR="172.16.140.140";//In the preceding script, the unit of bandwidth configured on a logical port is 64 kbit/s. Therefore, the CIR value 157 means that the configured bandwidth is 10048 kbit/s.


ADD IPLOGICPORT: SRN=1, SN=26, BT=GOUc, LPNTYPE=Leaf, LPN=1, CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=313, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;//In the preceding script, the unit of bandwidth configured on a logical port is 64 kbit/s. Therefore, the CIR value 313 means that the configured bandwidth is 20,032 kbit/s.


SET BTSIP: IDTYPE=BYID, BTSID=1, BTSCOMTYPE=LOGICIP, BTSIP="16.16.90.201", BSCIP="172.16.140.140", CFGFLAG=IPLGCPORT, SN=24, LPN=1;//In the preceding script, the base station is identified by its base station index.




72
























73










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


ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON; In the case of a separate-MPT multimode base station
















74


ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT, RU=KBPS;

//Disabling the traffic control switch on the default transport resource group you have configured

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





SN MO NE

1 a LR/LR/LR/LR eGBTS, NodeB,eNodeB, or co-MPTmultimode basestations

2 a IPLOGICPORT BSC and RNC


BSC

c IPPATH/ADJLOGICPORTBIND

RNC

3 a TRMMAP BSC

b TRMMAP RNC

c BSCABISPRIMAP BSC

d ADJMAP BSC

e ADJMAP RNC


b DIFPRI NodeB

c DIFPRI eNodeB

d UDTPARAGRP eNodeB

5 a ULFLOWCTRLPARA

NodeB



75

SN MO NE

b DLFLOWCTRLPARA

NodeB

6 a RSCGRP eGBTS, NodeB,eNodeB, or co-MPTmultimode basestations

b RSCGRPALG eGBTS, NodeB,eNodeB, or co-MPTmultimode basestations

7.4.13 Initial Configuration (Limited Access Bandwidth for EachOperator in a UL/UT Dual-Mode Base Station in RAN SharingScenarios)

Using MML Commands


l Scenario 1: The NodeB side of a separate-MPT multimode base station provides a co-transmission port.

1. Run the ADD RSCGRP command to configure a transport resource group.

2. Bind a user-plane link for transmitting local data and the configured transport resourcegroup on the base station side.

NOTE

A user-plane link can be configured either in link mode or in end-point mode. In link mode, usersconfigure an IP path. In end-point mode, users configure an end point group that includes the IPaddresses of the local and peer ends.

l If you use link mode to configure a user-plane link:

a. Run the ADD IPPATH command to add an IP path and bind this IP path and theconfigured transport resource group.

b. Run the ADD NODEBPATH command to bind a NodeB and the added IP path.

l If you use end-point mode to configure a user-plane link:

a. Run the ADD EPGROUP command to add an end point group on the base stationside.

b. Run the ADD USERPLANEHOST command to add a user-plane host on the basestation side.

c. Run the ADD USERPLANEPEER command to add a user-plane peer on the basestation side.

d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host andthe added end point group on the base station side.



76

e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer andthe added end point group on the base station side.f. Run the ADD EP2RSCGRP command to bind the added end point group and theconfigured transport resource group.

3. Run the ADD IP2RSCGRP command to bind a user-plane link for transmitting passingdata and a transport resource group on the base station side.

l Scenario 2: The eNodeB side of a separate-MPT multimode base station provides a co-transmission port.

1. Run the ADD RSCGRP command to configure a transport resource group.2. Bind a user-plane link for transmitting local data and the configured transport resource

group on the base station side.l If you use link mode to configure a user-plane link:

a. Run the ADD IPPATH command to add an IP path and bind this IP path and theconfigured transport resource group.b. Run the ADD ENODEBPATH command to bind an eNodeB and the added IP path.

l If you use end-point mode to configure a user-plane link:a. Run the ADD EPGROUP command to add an end point group on the base stationside.b. Run the ADD USERPLANEHOST command to add a user-plane host on the basestation side.c. Run the ADD USERPLANEPEER command to add a user-plane peer on the basestation side.d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host andthe added end point group on the base station side.e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer andthe added end point group on the base station side.f. Run the ADD EP2RSCGRP command to bind the added end point group and theconfigured transport resource group.

3. Run the ADD IP2RSCGRP command to bind a user-plane link for transmitting passingdata and a transport resource group on the base station side.

l Scenario 3: A co-MPT multimode base station provides a co-transmission port.

1. Run the ADD RSCGRP command to configure a transport resource group.2. Bind a user-plane link and the configured transport resource group on the base station side.

l If you use link mode to configure a user-plane link:a. Run the ADD IPPATH command to add an IP path and bind this IP path and theconfigured transport resource group. In this step, set Peer IP to the RNC IP address.b. Run the ADD NODEBPATH command to bind a NodeB and the added IP path.c. Run the ADD IPPATH command to bind the added IP path and the configuredtransport resource group. In this step, set Peer IP to the SeGW IP address.d. Run the ADD ENODEBPATH command to bind an eNodeB and the added IP path.

l If you use end-point mode to configure a user-plane link:a. Run the ADD EPGROUP command to add an end point group on the base stationside.



77

b. Run the ADD USERPLANEHOST command to add a user-plane host on the basestation side.

c. Run the ADD USERPLANEPEER command to add a user-plane peer on the basestation side.

d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host andthe added end point group on the base station side.

e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer andthe added end point group on the base station side.

f. Run the ADD EP2RSCGRP command to bind the added end point group and theconfigured transport resource group.



2. Run the ADD IPPATH command to bind a user-plane link and an IP logical port on theIub interface on the base station controller side.













If the NodeB or eNodeB side of a separate-MPT multimode base station provides a co-transmission port and co-transmission is implemented through panel interconnection, the trafficcontrol switch for a transport resource group must be disabled on the co-transmission port.Otherwise, when transmission resources become congested, passing data will preemptbandwidth from the local data. This deteriorates user experience. Run the SET RSCGRPALG



78

command to disable the traffic control switch of the default transport resource group you haveconfigured.

----End

MML Command Examples

//Two operators share one multimode base station

//Configuring traffic limiting and shaping on the co-transmission port

//If the NodeB side of a separate-MPT multimode base station provides a co-transmission port

//Configuring a transport resource group

ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=1, RU=KBPS, TXBW=10000, RXBW=10000, TXCBS=20000, TXEBS=64, OID=0, WEIGHT=100, TXCIR=10000, RXCIR=10000, TXPIR=10000, RXPIR=10000, TXPBS=20000;ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=2, RU=KBPS, TXBW=10000, RXBW=10000, TXCBS=20000, TXEBS=64, OID=1, WEIGHT=100, TXCIR=10000, RXCIR=10000, TXPIR=10000, RXPIR=10000, TXPBS=20000;

//If you use link mode to configure a user-plane link

//Binding an IP path and the configured transport resource group

ADD IPPATH: PATHID=1, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=1, LOCALIP="16.16.70.201", PEERIP="172.16.90.140", PATHTYPE=ANY;ADD NODEBPATH: PATHID=1;ADD IPPATH: PATHID=2, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=2, LOCALIP="16.16.60.201", PEERIP="172.16.80.140", PATHTYPE=ANY;ADD NODEBPATH: PATHID=2;

//If you use end-point mode to configure a user-plane link

//Binding an end point group and the configured transport resource group

ADD EPGROUP: EPGROUPID=0;ADD EPGROUP: EPGROUPID=1;ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="16.16.70.201";ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="16.16.60.201";ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, LOCIPV4="172.16.90.140";ADD USERPLANEPEER: UPPEERID=1, IPVERSION=IPv4, LOCIPV4="172.16.80.140";ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0;ADD UPPEER2EPGRP: EPGROUPID=1, UPPEERID=1;ADD EP2RSCGRP: ENDPOINTID=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1;ADD EP2RSCGRP: ENDPOINTID=1, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2;

//Binding the passing data and the configured transport resource group

ADD IP2RSCGRP: SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1, DSTIP="172.15.90.140", DSTMASK="255.255.255.255";ADD IP2RSCGRP: SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2, DSTIP="172.15.80.140", DSTMASK="255.255.255.255";

//If the eNodeB side of a separate-MPT multimode base station provides a co-transmission port


ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=1, RU=KBPS, TXBW=10000, RXBW=10000, TXCBS=20000, TXEBS=64, OID=0, WEIGHT=100, TXCIR=10000, RXCIR=10000, TXPIR=10000, RXPIR=10000, TXPBS=10000;



79

ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=2, RU=KBPS, TXBW=10000, RXBW=10000, TXCBS=20000, TXEBS=64, OID=1, WEIGHT=100, TXCIR=10000, RXCIR=10000, TXPIR=10000, RXPIR=10000, TXPBS=10000;



ADD IPPATH: PATHID=1, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=1, LOCALIP="16.15.70.201", PEERIP="172.15.90.140", PATHTYPE=ANY;ADD ENODEBPATH: IpPathId=1, AppType=S1, S1InterfaceId=0;ADD IPPATH: PATHID=2, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=2, LOCALIP="16.15.60.201", PEERIP="172.15.80.140", PATHTYPE=ANY;ADD ENODEBPATH: IpPathId=2, AppType=S1, S1InterfaceId=0;



ADD EPGROUP: EPGROUPID=0;ADD EPGROUP: EPGROUPID=1;ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="16.15.70.201";ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="16.15.60.201";ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, LOCIPV4="172.15.90.140";ADD USERPLANEPEER: UPPEERID=1, IPVERSION=IPv4, LOCIPV4="172.15.80.140";ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0;ADD UPPEER2EPGRP: EPGROUPID=1, UPPEERID=1;ADD EP2RSCGRP: ENDPOINTID=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1;ADD EP2RSCGRP: ENDPOINTID=1, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2;

//Binding the passing data and the configured transport resource group

ADD IP2RSCGRP: SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1, DSTIP="172.16.90.140", DSTMASK="255.255.255.255";ADD IP2RSCGRP: SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2, DSTIP="172.16.80.140", DSTMASK="255.255.255.255";

//If a co-MPT multimode base station provides a co-transmission port


ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=1, RU=KBPS, TXBW=10000, RXBW=10000, TXCBS=20000, TXEBS=64, OID=0, WEIGHT=100, TXCIR=10000, RXCIR=10000, TXPIR=10000, RXPIR=10000, TXPBS=10000;ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=2, RU=KBPS, TXBW=10000, RXBW=10000, TXCBS=20000, TXEBS=64, OID=1, WEIGHT=100, TXCIR=10000, RXCIR=10000, TXPIR=10000, RXPIR=10000, TXPBS=10000;



ADD IPPATH: PATHID=1, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=1, LOCALIP="16.16.70.201", PEERIP="172.16.90.140", PATHTYPE=ANY;ADD NODEBPATH: PATHID=1;ADD IPPATH: PATHID=2, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=2, LOCALIP="16.16.60.201", PEERIP="172.16.80.140", PATHTYPE=ANY;ADD NODEBPATH: PATHID=2;ADD IPPATH: PATHID=3, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=1, LOCALIP="16.15.70.201", PEERIP="172.15.90.140", PATHTYPE=ANY;ADD ENODEBPATH: IpPathId=3, AppType=S1, S1InterfaceId=0;ADD IPPATH: PATHID=4, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=2, LOCALIP="16.15.60.201", PEERIP="172.15.80.140", PATHTYPE=ANY;ADD ENODEBPATH: IpPathId=4, AppType=S1, S1InterfaceId=1;



80



ADD EPGROUP: EPGROUPID=0;ADD EPGROUP: EPGROUPID=1;ADD EPGROUP: EPGROUPID=2;ADD EPGROUP: EPGROUPID=3;ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="16.16.70.201";ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="16.16.60.201";ADD USERPLANEHOST: UPHOSTID=2, IPVERSION=IPv4, LOCIPV4="16.15.70.201";ADD USERPLANEHOST: UPHOSTID=3, IPVERSION=IPv4, LOCIPV4="16.15.60.201";ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, LOCIPV4="172.16.90.140";ADD USERPLANEPEER: UPPEERID=1, IPVERSION=IPv4, LOCIPV4="172.16.80.140";ADD USERPLANEPEER: UPPEERID=2, IPVERSION=IPv4, LOCIPV4="172.15.90.140";ADD USERPLANEPEER: UPPEERID=3, IPVERSION=IPv4, LOCIPV4="172.15.80.140";ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;ADD UPHOST2EPGRP: EPGROUPID=2, UPHOSTID=2;ADD UPHOST2EPGRP: EPGROUPID=3, UPHOSTID=3;ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0;ADD UPPEER2EPGRP: EPGROUPID=1, UPPEERID=1;ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=2;ADD UPPEER2EPGRP: EPGROUPID=1, UPPEERID=3;ADD EP2RSCGRP: ENDPOINTID=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1;ADD EP2RSCGRP: ENDPOINTID=2, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1;ADD EP2RSCGRP: ENDPOINTID=1, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2;ADD EP2RSCGRP: ENDPOINTID=3, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2;



ADD IPLOGICPORT: SRN=1, SN=26, BT=GOUc, LPNTYPE=Leaf, LPN=1, CARRYT=ETHER, PN=0, RSCMNGMODE=EXCLUSIVE, BWADJ=OFF, CIR=157, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;//In the preceding script, the unit of bandwidth configured on a logical port is 64 kbit/s. Therefore, the CIR value 157 means that the configured bandwidth is 10,048 kbit/s.ADD IPLOGICPORT: SRN=1, SN=26, BT=GOUc, LPNTYPE=Leaf, LPN=2, CARRYT=ETHER, PN=0, RSCMNGMODE=EXCLUSIVE, BWADJ=OFF, CIR=157, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF;//In the preceding script, the unit of bandwidth configured on a logical port is 64 kbit/s. Therefore, the CIR value 157 means that the configured bandwidth is 10,048 kbit/s.

//Binding an IP path and the logical port you have added on the Iub interface

ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS, IPADDR="172.16.90.140", PEERIPADDR="16.16.70.201", TXBW=10000, RXBW=10000, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;ADD IPPATH: ANI=10, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=QoS, IPADDR="172.16.80.140", PEERIPADDR="16.16.60.201", TXBW=10000, RXBW=10000, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;







81




























82



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





SN MO NE

1 a RSCGRP NodeB, eNodeB, orco-MPT multimodebase stations

b IPPATH NodeB, eNodeB, orco-MPT multimodebase stations

c NODEBPATH NodeB or co-MPTmultimode basestations

d ENODEBPATH eNodeB or co-MPTmultimode basestations

e IP2RSCGRP NodeB or eNodeB

2 a IPLOGICPORT RNC

b IPPATH/ADJLOGICPORTBIND

RNC

3 a TRMMAP RNC

b ADJMAP RNC

4 a DIFPRI NodeB

b DIFPRI eNodeB

c UDTPARAGRP eNodeB



83

SN MO NE

5 a ULFLOWCTRLPARA

NodeB

b DLFLOWCTRLPARA

NodeB

6 a RSCGRPALG NodeB, eNodeB, ormultimode basestations

7.4.14 Activation Observation (Unlimited Access Bandwidth forMultimode Base Stations)

After the Bandwidth Sharing of Multimode Base Station Co-Transmission feature is activated,check whether UEs can properly process CS and PS services when transmission resources arecongested and whether the DSCP value of each packet is configured as expected.

l If yes to both, this feature has been activated.l If no to either, this feature has not been activated.

Perform the following steps to determine whether this feature has been activated:

l Separate-MPT multimode base station

Step 1 Start IP or MAC tracing on the LMT.l If the eGBTS provides a co-transmission port, start IP or MAC tracing on the eGBTS LMT.

For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace.For MAC tracing: Choose Trace > Common Services > MAC Trace.

l If the NodeB provides a co-transmission port, start IP or MAC tracing on the NodeB LMT.For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace.For MAC tracing: Choose Trace > Common Services > MAC Trace.

l If the eNodeB provides a co-transmission port, start IP or MAC tracing on the eNodeB LMT.For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace.For MAC tracing: Choose Trace > Common Services > MAC Trace.

Step 2 For IP tracing: In the displayed IP Layer Protocol Trace dialog box, specify Local IPAddress and Peer IP Address of the packets to be traced.

For MAC tracing: In the displayed MAC Trace dialog box, specify Local MAC Address andPeer MAC Address of the packets to be traced.

Step 3 Use the TrafficReview tool to check the TOS (type of service) field in the Layer 3 IP packetheader or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOSfield indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities arethe same as DSCP values or VLAN priorities planned, this feature has been activated.

----End



84

l Co-MPT multimode base station

Step 1 Start IP or MAC tracing on the LMT.l If GSM services are initiated, start IP or MAC tracing on the LMT of the co-MPT multimode

base station.For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace.For MAC tracing: Choose Trace > Common Services > MAC Trace.

l If UMTS services are initiated, start IP or MAC tracing on the LMT of the co-MPT multimodebase station.For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace.For MAC tracing: Choose Trace > Common Services > MAC Trace.

l If LTE services are initiated, start IP or MAC tracing on the LMT of the co-MPT multimodebase station.For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace.For MAC tracing: Choose Trace > Common Services > MAC Trace.

Step 2 For IP tracing: In the displayed IP Layer Protocol Trace dialog box, specify Local IPAddress and Peer IP Address of the packets to be traced.

For MAC tracing: In the displayed MAC Trace dialog box, specify Local MAC Address andPeer MAC Address of the packets to be traced.

Step 3 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLANPriority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate theDSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCPvalues or VLAN priorities planned, this feature has been activated.

----End

7.4.15 Activation Observation (Limited Access Bandwidth forMultimode Base Stations)

If you do not need to check whether the configured service priority has taken effect, perform thefollowing steps to check whether the feature has been activated:

Step 1 Run the LST RSCGRP command on the base station that provides the co-transmission port tocheck whether a transport resource group has been configured for the co-transmission port. Ifnot, go to method 2.

Step 2 Initiate a UMTS or LTE PS service and set the maximum data rate to a value greater than theCIR to simulate transmission resource congestion.

Step 3 Query the value of the VS.RscGroup.FlowOverloadTime counter for the co-transmission port.If the value is greater than 0, this feature has been activated.

----End

If you need to check whether the configured service priority has taken effect, perform thefollowing steps to check whether the feature has been activated:

l The eGBTS side of a separate-MPT multimode base station provides a co-transmissionport.



85

Step 1 Initiate a UMTS or LTE PS service and set the maximum data rate higher than the CIR valueto simulate transmission resource congestion.

Step 2 Start transport link flux monitoring on the eGBTS LMT. Choose Monitor > RealtimePerformance Monitoring > Transport Link Flux Monitoring.

Step 3 Initiate a GSM or UMTS CS service if the traffic flux approaches the bandwidth available forthe bearer network.

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

Step 5 Initiate a GSM PS service, connect a personal computer (PC) to the multimode base station, anduse the DU Meter on the PC to check whether the GSM PS service is successfully set up andthe data rate is stable.

l If yes to both, this feature has been activated.

l If no to either, this feature has not been activated.

Step 6 Start IP or MAC tracing on the eGBTS LMT.

For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayedIP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of thepackets to be traced.

For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MACTrace dialog box, specify Local MAC Address and Peer MAC Address of the packets to betraced.


----End

l The NodeB side of a separate-MPT multimode base station provides a co-transmission port.

Step 1 Initiate a UMTS PS service and set the maximum data rate higher than the CIR value to simulatetransmission resource congestion.

Step 2 Start transport link flux monitoring on the NodeB LMT. Choose Monitor > RealtimePerformance Monitoring > Transport Link Flux Monitoring.


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

Step 5 Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meteron the PC to check whether the GSM PS service is successfully set up and the data rate is stable.

l If yes, this feature has been activated.

l If no, this feature has not been activated.

NOTE

Step 5 is performed only in a separate-MPT GU dual-mode base station or a separate-MPT GUL triple-mode base station.



86

Step 6 Start IP or MAC tracing on the NodeB LMT.


For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MACTrace dialog box, specify Local MAC Address and Peer MAC Address of the packets to betraced.


----End

l The eNodeB side of a separate-MPT multimode base station provides a co-transmissionport.

Step 1 Initiate an LTE PS service and set the maximum data rate higher than the CIR value to simulatetransmission resource congestion.

Step 2 Start transport link flux monitoring on the eNodeB LMT. Choose Monitor > RealtimePerformance Monitoring > Transport Link Flux Monitoring.


Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant.Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meteron the PC to check whether the GSM PS service is successfully set up and the data rate is stable.



NOTE

Step 4 is performed only in a separate-MPT GL dual-mode base station or a separate-MPT GUL triple-mode base station.

Step 5 Start IP or MAC tracing on the eNodeB LMT.


For MAC tracing:Choose Trace > Common Services > MAC Trace. In the displayed MACTrace dialog box, specify Local MAC Address and Peer MAC Address of the packets to betraced.


----End



87

l A co-MPT multimode base station provides a co-transmission port.

Step 1 Initiate a UMTS or LTE PS service and set the maximum data rate higher than the CIR valueto simulate transmission resource congestion.

Step 2 Start transport link flux monitoring on the LMT.

l If UMTS services are initiated, start transport link flux monitoring on the LMT. ChooseMonitor > Realtime Performance Monitoring > Transport Link Flux Monitoring.

l If LTE services are initiated, start transport link flux monitoring on the LMT. ChooseMonitor > Realtime Performance Monitoring > Transport Link Flux Monitoring.


Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant.Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meteron the PC to check whether the GSM PS service is successfully set up and the data rate is stable.



NOTE

Step 4 is performed only in a separate-MPT GU/GL dual-mode base station or a separate-MPT GUL triple-mode base station.

Step 5 Start IP or MAC tracing on the LMT.

l If GSM services are initiated, start IP or MAC tracing on the LMT.

For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In thedisplayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IPAddress of the packets to be traced.

For MAC tracing:Choose Trace > Common Services > MAC Trace. In the displayed MACTrace dialog box,specify Local MAC Address and Peer MAC Address of the packets tobe traced.

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


For MAC tracing:Choose Trace > Common Services > MAC Trace. In the displayed MACTrace dialog box, specify Local MAC Address and Peer MAC Address of the packets tobe traced.

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


For MAC tracing:Choose Trace > Common Services > MAC Trace. In the displayed MACTrace dialog box, specify Local MAC Address and Peer MAC Address of the packets tobe traced.

Step 6 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLANPriority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the



88

DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCPvalues or VLAN priorities planned, this feature has been activated.

----End

7.4.16 Activation Observation (Limited Access Bandwidth for EachOperator in RAN Sharing Scenarios)

If you do not need to check whether the configured service priority has taken effect, perform thefollowing steps to check whether the feature has been activated:

Step 1 Run the LST RSCGRP command on the base station that provides the co-transmission port tocheck whether a transport resource group has been configured for the co-transmission port. Ifnot, go to method 2.

Step 2 Initiate a UMTS or LTE PS service for an operator and set the maximum data rate to a valuegreater than the TXBW value to simulate transmission resource congestion.

Step 3 Query the value of the VS.RscGroup.FlowOverloadTime counter for the co-transmission port.If the value is greater than 0, this feature has been activated.

----End

If you need to check whether the configured service priority has taken effect, perform thefollowing steps to check whether the feature has been activated:

l Separate-MPT multimode base station

Step 1 Initiate a UMTS or LTE PS service for operator A and set the maximum data rate higher thanthe TXBW value to simulate transmission resource congestion.


l If the NodeB side of a separate-MPT multimode base station provides a co-transmission port,start transport link flux monitoring on the NodeB LMT. Choose Monitor > RealtimePerformance Monitoring > Transport Link Flux Monitoring.

l If the eNodeB side of a separate-MPT multimode base station provides a co-transmissionport, start transport link flux monitoring on the eNodeB LMT. Choose Monitor > RealtimePerformance Monitoring > Transport Link Flux Monitoring.

Step 3 Initiate a UMTS CS service for operator A if the traffic flux approaches the bandwidth availablefor the bearer network. Terminate the CS service if the call is successfully set up and the voiceis clear and constant.

Step 4 Perform the first three steps to verify services of other operators.


l Start IP or MAC tracing on the NodeB LMT.


For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayedMAC Trace dialog box, specify Local MAC Address and Peer MAC Address of thepackets to be traced.



89

l Start IP or MAC tracing on the eNodeB LMT.




----End

l Co-MPT multimode base station

Step 1 Initiate a UMTS or LTE PS service for operator A and set the maximum data rate higher thanthe TXBW value to simulate transmission resource congestion.


l If UMTS services are initiated, start transport link flux monitoring on the NodeB LMT.Choose Monitor > Realtime Performance Monitoring > Transport Link FluxMonitoring.

l If LTE services are initiated, start transport link flux monitoring on the eNodeB LMT. ChooseMonitor > Realtime Performance Monitoring > Transport Link Flux Monitoring.

Step 3 Initiate a UMTS CS service for operator A if the traffic flux approaches the bandwidth availablefor the bearer network. Terminate the CS service if the call is successfully set up and the voiceis clear and constant.

Step 4 Perform the first three steps to verify services of other operators.


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



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



Step 6 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLANPriority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the



90

DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCPvalues or VLAN priorities planned, this feature has been activated.

----End

7.5 Performance MonitoringTransmission resource congestion in a base station is indicated by the congestion duration oftransport resource groups calculated by the VS.RscGroup.FlowOverloadTime counter.

7.6 Parameter OptimizationNone

7.7 TroubleshootingIf bandwidth resources across all modes of a multimode base station are inappropriatelyallocated, reallocate the bandwidth resources based on the traffic model.



91

8 Parameters

Table 8-1 Parameter description

Parameter ID NE MMLCommand

Feature ID Feature Name Description

CIR BTS3900,BTS3900WCDMA,BTS3900 LTE

SET LRLST LR

WRFD-01061010

HSDPA FlowControl

Meaning:Indi-cates the ULcommittedinformation rateafter ratelimitation isconfigured at aport. Theprecision of theUL committedinformation ratesupported by theUMPTb is 64Kbit/s, theprecisionsupported by theother board is 32Kbit/s. If theconfigured ULcommittedinformation rateis not a multipleof the precision,the ULcommittedinformation rateis rounded up.GUI ValueRange:32~1000000Unit:Kbit/s

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


92



Actual ValueRange:32~1000000DefaultValue:None



93



TXBW BTS3900,BTS3900WCDMA,BTS3900 LTE

ADD RSCGRPMOD RSCGRPDSP RSCGRPLST RSCGRP

WRFD-02130406

TransmissionRecourseSharing on Iub/Iur Interface

Meaning:Indi-cates themaximumuplinkbandwidth of atransmissionresource groupat the MAClayer when thetransmissionresource groupis carried overIP. Thisparameter valueis used as theuplink transportadmissionbandwidth andTX trafficshapingbandwidth.TheLMPT can beconfigured witha maximum of360 Mbit/s TXbandwidth.TheWMPT can beconfigured witha maximum of300 Mbit/s TXbandwidth.TheUMPT can beconfigured witha maximum of 1Gbit/s TXbandwidth.Thevalue of TXbandwidth is setto the maximumvalue of TXbandwidthsupported by theboard when itbigger than themaximum one.



94



GUI ValueRange:32~1000000Unit:NoneActual ValueRange:32~1000000DefaultValue:None

CIR BSC6900 ADDIPLOGICPORTMODIPLOGICPORT

WRFD-050408WRFD-140208WRFD-021311WRFD-140207

Overbooking onIP TransmissionIubTransmissionResource Poolin RNCMOCNIntroductionPackageIu/IurTransmissionResource Poolin RNC

Meaning:Band-width of thelogical portGUI ValueRange:1~1562Unit:64kbit/sActual ValueRange:64~64000(FG2a/GOUa/UOIa(IP)),256~100000(FG2c/GOUc/POUc(IP)/PEUc(IP)/GOUe)DefaultValue:None

CIR BSC6910 ADDIPLOGICPORTMODIPLOGICPORT

WRFD-050408 Overbooking onIP Transmission

Meaning:Band-width of thelogical port.GUI ValueRange:4~1562Unit:64kbit/sActual ValueRange:256~100000DefaultValue:None



95



TNLCONGCTRLSWITCH

BTS3900,BTS3900WCDMA

ADDULFLOWCTRLPARASETULFLOWCTRLPARALSTULFLOWCTRLPARA

None None Meaning:Indi-cates whether toperformcongestioncontrol. Whenthis switch isturned on, theBS lowers theTX rate if the BSdetects that linksexperiencetransmissiondelay or packetloss.It isrecommendedthat this switchbe turned off ifUMTS and LTEservices areconfigured inthe sametransmissionresource group.The purpose is toprevent UMTSflow controlfrom affectingLTE services.GUI ValueRange:OFF(Off), ON(On)Unit:NoneActual ValueRange:OFF, ONDefaultValue:ON(On)



96



TCSW BTS3900,BTS3900WCDMA,BTS3900 LTE

SETRSCGRPALGLSTRSCGRPALG

LOFD-00301101 /TDLOFD-00301101LOFD-00301102 /TDLOFD-00301102

TransportOverbookingTransportDifferentiatedFlow Control

Meaning:Indi-cates whether toenable thebackpressurealgorithm of atransmissionresource group.The BSmonitors thedata buffered inthe queues ofeachtransmissionresource group,determineswhether thetransmissionresource groupis congested,and transmitsthe backpressuresignals (numberand congestionstatus of thetransmissionresource group)to each flowcontrol service.If the number ofdata packets inthe buffer of anybackpressurequeue exceeds75% of thequeue capacity,the BS regardsthistransmissionresource groupas congested andtransmitscongestionsignals. If thebuffered back-pressure packetsare less than50% of the totalbuffer capacity,



97



the BS decidesthat thetransmissionresource groupis not congested.In this situation,no congestionsignal orcongestionrelease signal istransmitted.When thisparameter is setto ENABLE,both intra-modeand inter-modetraffic controlsare supported.The inter-modetraffic controlfor transmissionresource groupsapplies only toseparate-MPTbase stationswith co-transmissionimplementedthroughbackplaneinterconnection.However, it doesnot apply tocascaded basestations, basestations with co-transmissionimplementedthrough panelinterconnection,or base stationsenabled withroute loadsharing. Whenthe inter-modetraffic controlfunction isenabled for a



98



separate-MPTbase station withco-transmissionimplementedthroughbackplaneinterconnection,the Tunnel Typeparameter mustbe set to DL(DL)for the tunnel ofthe modeprovidingtransmissionports and mustbe set to UL(UL)for the tunnel ofthe modeproviding notransmissionport.GUI ValueRange:DISABLE(Disable),ENABLE(Enable)Unit:NoneActual ValueRange:DISABLE, ENABLEDefaultValue:ENABLE(Enable)



99



SWITCH BTS3900,BTS3900WCDMA

ADDDLFLOWCTRLPARASETDLFLOWCTRLPARALSTDLFLOWCTRLPARA

WRFD-01061010

HSDPA FlowControl

Meaning:Indi-cates the switchfor the DL flowcontrolalgorithm. If thisparameter is settoDYNAMIC_BW_SHAPING,flow allocationfor HSDPAusers isperformedaccording to thedelay and packetloss of thetransmissioninterface boardinSTATIC_BW_SHAPINGmode. Thisfunctionrequires thenetworkcontroller usingthe switch of the3GPP R6protocol.Therefore, youare advised touse this functionwith the RNCthat complieswith the 3GPPR6 protocol. Ifthis parameter isset toNO_BW_SHAPING, the BSdoes not allocatebandwidthaccording to theconfigurationand delay of thetransmissioninterface board.The BS reports



100



the air interfaceconditions to thecontroller, andthen thecontrollerallocatesbandwidth.When thisparameter is settoNO_BW_SHAPING, thebackpressurefunction must beenabled on thecontroller side.If this parameteris set toBW_SHAPING_ONOFF_TOGGLE, the BSautomaticallyselects eitherDYNAMIC_BW_SHAPINGorNO_BW_SHAPING during aflow congestiondetection on aport. That is,DYNAMIC_BW_SHAPING isselected ifcongestion isdetected;NO_BW_SHAPING is selectedif congestion isnot detected fora certain periodof time.GUI ValueRange:STATIC_BW_SHAPING(STATIC_BW_



101



SHAPING),DYNAMIC_BW_SHAPING(DYNAMIC_BW_SHAPING),NO_BW_SHAPING(NO_BW_SHAPING),BW_SHAPING_ONOFF_TOGGLE(BW_SHAPING_ONOFF_TOGGLE)Unit:NoneActual ValueRange:STATIC_BW_SHAPING,DYNAMIC_BW_SHAPING,NO_BW_SHAPING,BW_SHAPING_ONOFF_TOGGLEDefaultValue:BW_SHAPING_ONOFF_TOGGLE(BW_SHAPING_ONOFF_TOGGLE)



102



FAIRSWITCH BTS3900,BTS3900WCDMA

ADDDLFLOWCTRLPARASETDLFLOWCTRLPARALSTDLFLOWCTRLPARA

WRFD-01061010

HSDPA FlowControl

Meaning:Indi-cates the switchcontrollingdownlinkfairness flowcontrol. Whenmultiple modessharetransmissionbandwidth andcongestionoccurs, theUMTS data ratemay decreasedue to downlinkflow control andthe LTE datarate mayincrease due tobandwidthpreemption.When thefairness flowcontrol switch isturned on, thesystemguarantees theminimumdownlinktransmissionbandwidth of theUMTSmode.Thisswitch onlysupport ETH(Ethernet Port)and ETHTRK(EthernetTrunk) andLOOPINT(LoopInterface) , theloopint's actualinterface is ETHor ETHTRK.



103



GUI ValueRange:OFF(Off), ON(On)Unit:NoneActual ValueRange:OFF, ONDefaultValue:OFF(Off)

CBS BTS3900,BTS3900WCDMA,BTS3900 LTE

SET LRLST LR

WRFD-050402 IP TransmissionIntroduction onIub Interface

Meaning:Indi-cates theCommittedBurst Size(CBS) after ratelimitation isconfigured at aport.Theminimum ratesupported by theUMPTb is 64Kbit/s.GUI ValueRange:32~1000000Unit:KbitActual ValueRange:32~1000000DefaultValue:None



104



EBS BTS3900,BTS3900WCDMA,BTS3900 LTE

SET LRLST LR


Meaning:Indi-cates the ExcessBurst Size(EBS) after ratelimitation isconfigured at aport.GUI ValueRange:0~1000000Unit:KbitActual ValueRange:0~1000000DefaultValue:None



105



TXCBS BTS3900,BTS3900WCDMA,BTS3900 LTE

ADD RSCGRPMOD RSCGRPLST RSCGRP

WRFD-02130406


Meaning:Indi-cates the TXcommitted burstsize of atransmissionresourcegroup.TheLMPT can beconfigured witha maximum of400 Mbit/s TXcommitted burstsize.The WMPTcan beconfigured witha maximum of600 Mbit/s TXcommitted burstsize.The WMPTcan beconfigured witha maximum of600 Mbit/s TXcommitted burstsize.The UMPTcan beconfigured witha maximum of 1Gbit/s TXcommitted burstsize.The valueof TXcommitted burstsize is set to themaximum valueof TXcommitted burstsize supportedby the boardwhen it biggerthan themaximum one.GUI ValueRange:64~1000000Unit:Kbit



106



Actual ValueRange:64~1000000Default Value:64



107



TXEBS BTS3900,BTS3900WCDMA,BTS3900 LTE

ADD RSCGRPMOD RSCGRPLST RSCGRP

WRFD-02130406


Meaning:Indi-cates the TXexcessive burstsize of atransmissionresourcegroup.TheLMPT can beconfigured witha maximum of450 Mbit/s TXexcessive burstsize.The WMPTcan beconfigured witha maximum of600 Mbit/s TXexcessive burstsize.The UMPTcan beconfigured witha maximum of 1Gbit/s TXexcessive burstsize.The valueof TX excessiveburst size is setto the maximumvalue of TXexcessive burstsize supportedby the boardwhen it biggerthan themaximum one.GUI ValueRange:64~1000000Unit:KbitActual ValueRange:64~1000000Default Value:1000000



108



LPN BSC6900 ADDIPLOGICPORTMODIPLOGICPORTRMVIPLOGICPORT

WRFD-140208WRFD-140207

IubTransmissionResource Poolin RNCIu/IurTransmissionResource Poolin RNC

Meaning:Logical port number. Itis uniquelynumberedwithin theactive/standbyboards.GUI ValueRange:0~988;1024~1535Unit:NoneActual ValueRange:0~119(FG2a/GOUa/UOIa(IP));0~489, 512~767(FG2c); 0~499,512~767(GOUc/GOUe);0~988,1024~1535(POUc(IP));0~127,1024~1087(PEUc(IP))DefaultValue:None

LPN BSC6910 ADDIPLOGICPORTMODIPLOGICPORTRMVIPLOGICPORT

None None Meaning:Logical port number.GUI ValueRange:0~2047Unit:NoneActual ValueRange:0~489(FG2c, GOUc,GOUe),512~767(FG2c,GOUc, GOUe);0~1499(EXOUa),1536~2047(EXOUa)DefaultValue:None



109



PRIRULE BTS3900,BTS3900WCDMA,BTS3900 LTE

SET DIFPRILST DIFPRI


Meaning:Indi-cates the rule forprioritizingtraffic to meetservicerequirements. Ifthis parameter isset toIPPRECEDENCE, the protocolstack of theearlier version isadopted, whichfirstly converts aType of Service(TOS) to aDSCP and thenprioritizestraffic.GUI ValueRange:IPPRECEDENCE(IPPrecedence),DSCP(DSCP)Unit:NoneActual ValueRange:IPPRECEDENCE,DSCPDefaultValue:DSCP(DSCP)



110



SIGPRI BTS3900,BTS3900WCDMA,BTS3900 LTE



Meaning:Indi-cates the priorityof signaling. Thepriority has apositivecorrelation withthe value of thisparameter.GUI ValueRange:0~63Unit:NoneActual ValueRange:0~63Default Value:48

OMHIGHPRI BTS3900,BTS3900WCDMA,BTS3900 LTE



Meaning:Indi-cates the priorityof the high-levelOM data. Thepriority has apositivecorrelation withthe value of thisparameter.GUI ValueRange:0~63Unit:NoneActual ValueRange:0~63Default Value:46



111



OMLOWPRI BTS3900,BTS3900WCDMA,BTS3900 LTE



Meaning:Indi-cates the priorityof the low-levelOM data, suchas the data to beuploaded ordownloaded.The priority hasa positivecorrelation withthe value of thisparameter. Thelow-level OMdata includes thepackets relatedto File TransferProtocol (FTP).GUI ValueRange:0~63Unit:NoneActual ValueRange:0~63Default Value:18



112



IPCLKPRI BTS3900,BTS3900WCDMA,BTS3900 LTE


None None Meaning:Indi-cates the priorityof the IP clock. Ifthe IP clock thatfollows thePrecision TimeProtocol (PTP)is used, set thisparameter to theDSCP of thePTP packets. Ifthe IP clock thatfollows theHuaweiproprietaryprotocol is used,set thisparameter to theDSCP of thesepackets thatfollow theHuaweiproprietaryprotocol.GUI ValueRange:0~63Unit:NoneActual ValueRange:0~63Default Value:46



113



CCHPRIPATH BSC6900 ADDTRMMAPMODTRMMAP

WRFD-050406 ATM QoSIntroduction onHub Node B(Overbookingon Hub Node BTransmission)

Meaning:Primary path thatcarries thecommonchannelservices.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,



114



LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFDefaultValue:None



115



SIPPRIPATH BSC6900 ADDTRMMAPMODTRMMAP


Meaning:Thisparameter isused to set IMSSRB primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,



116



LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFDefaultValue:None



117



SRBPRIPATH BSC6900 ADDTRMMAPMODTRMMAP


Meaning:Signaling servicebearer primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



118



LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFDefaultValue:None



119



VOICEPRIPATH

BSC6900 ADDTRMMAPMODTRMMAP


Meaning:AMRvoice servicebearer primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



120






121



CSCONVPRIPATH



Meaning:R99CSconversationalservice primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,



122






123



CSSTRMPRIPATH



Meaning:R99CS streamingservice bearerprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



124






125



PSCONVPRIPATH



Meaning:R99PSconversationalservice primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,



126






127



PSSTRMPRIPATH



Meaning:R99PS streamingservice bearerprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



128






129



PSINTHGHPRIPATH



Meaning:R99PS high PRIinteractiveprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



130






131



PSINTMIDPRIPATH



Meaning:R99PS middle PRIinteractiveprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



132






133



PSINTLOWPRIPATH



Meaning:R99PS low PRIinteractiveprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



134






135



PSBKGPRIPATH



Meaning:R99PS backgroundservice bearerprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



136






137



HDSRBPRIPATH



Meaning:HSDPA signalingbearer primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



138






139



HDSIPPRIPATH



Meaning:HSDPA IMS signalingbearer primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



140






141



HDVOICEPRIPATH



Meaning:HSDPA voice servicebearer primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



142






143



HDCONVPRIPATH



Meaning:HSDPAconversationalservice bearerprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,



144






145



HDSTRMPRIPATH



Meaning:HSDPA streamingservice bearerprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



146






147



HDINTHGHPRIPATH



Meaning:HSDPA high PRIinteractiveprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



148






149



HDINTMIDPRIPATH



Meaning:HSDPA middle PRIinteractiveprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



150






151



HDINTLOWPRIPATH



Meaning:HSDPA low PRIinteractiveprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



152






153



HDBKGPRIPATH



Meaning:HSDPA backgroundservice bearerprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



154






155



HUSRBPRIPATH



Meaning:HSUPA signalingbearer primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



156






157



HUSIPPRIPATH



Meaning:HSUPA IMS signalingbearer primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



158






159



HUVOICEPRIPATH



Meaning:HSUPA voice servicebearer primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



160






161



HUCONVPRIPATH



Meaning:HSUPAconversationalservice primarypath.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,



162






163



HUSTRMPRIPATH



Meaning:HSUPA streamingservice bearerprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



164






165



HUINTHGHPRIPATH



Meaning:HSUPA high PRIinteractiveprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



166






167



HUINTMIDPRIPATH



Meaning:HSUPA middle PRIinteractiveprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



168






169



HUINTLOWPRIPATH



Meaning:HSUPA low PRIinteractiveprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



170






171



HUBKGPRIPATH



Meaning:HSUPA backgroundservice bearerprimary path.GUI ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,LQAF31,LQAF32,LQAF33,LQAF41,LQAF42,LQAF43, LQEFUnit:NoneActual ValueRange:CBR,RT_VBR,NRT_VBR,UBR, BE,AF11, AF12,AF13, AF21,AF22, AF23,AF31, AF32,AF33, AF41,AF42, AF43,EF, LQBE,LQAF11,LQAF12,LQAF13,LQAF21,LQAF22,LQAF23,



172






173

9 Counters

Table 9-1 Counter description

Counter ID Counter Name CounterDescription

NE Feature ID Feature Name

1542455378 VS.RscGroup.TxFlowOverload-Time

Congestionduration oftransmit data inthe resourcegroup

NodeB Multi-mode:MRFD-211505MRFD-221505MRFD-231505MRFD-241505GSM: NoneUMTS: NoneLTE: None

Bandwidthsharing ofMBTS Multi-mode Co-Transmission(GBTS)Bandwidthsharing ofMBTS Multi-mode Co-Transmission(NodeB)Bandwidthsharing ofMBTS Multi-mode Co-Transmission(eNodeB)Bandwidthsharing ofMBTS Multi-mode Co-Transmission(LTE TDD)

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


174

10 Glossary

For the acronyms, abbreviations, terms, and definitions, see the Glossary.

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


175

11 Reference Documents

1. Transmission Resource Management Feature Parameter Description for GBSS and RAN2. Transport Resource Management Feature Parameter Description for eRAN3. Common Transmission Feature Parameter Description for SingleRAN

SingleRANBandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description 11 Reference Documents


176

bandwidth sharing of multimode base station co-transmission(sran9.0_draft a)

Documents

huawei trademarks

huawei proprietary

huawei industrial basebantian

thepurchase scope

usage scope

trade names

respective holders

application networking