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

SingleRAN

Bandwidth Sharing of Multimode Base Station Co-Transmission Feature Parameter Description Issue

02

Date

2014-12-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 02 (2014-12-30)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

SingleRAN Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description

Contents

Contents 1 About This Document..................................................................................................................1 1.1 Scope..............................................................................................................................................................................1 1.2 Intended Audience..........................................................................................................................................................1 1.3 Change History...............................................................................................................................................................2 1.4 Differences Between Base Station Types.......................................................................................................................3

2 Overview.........................................................................................................................................5 2.1 Introduction....................................................................................................................................................................5 2.2 Benefits...........................................................................................................................................................................5 2.3 Application Networking.................................................................................................................................................6

3 Technical Description...................................................................................................................8 3.1 Introduction....................................................................................................................................................................8 3.2 Transmission Priorities...................................................................................................................................................9 3.3 Traffic Limiting and Shaping.......................................................................................................................................12 3.4 Load Control.................................................................................................................................................................14 3.5 Flow Control.................................................................................................................................................................14

4 Application Scenarios.................................................................................................................18 4.1 Unlimited Access Bandwidth for Multimode Base Stations........................................................................................18 4.1.1 Introduction...............................................................................................................................................................18 4.1.2 Transmission Resource Management Strategies.......................................................................................................19 4.2 Limited Access Bandwidth for Multimode Base Stations............................................................................................23 4.2.1 Introduction...............................................................................................................................................................23 4.2.2 Transmission Resource Management Strategies.......................................................................................................24 4.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios.................................................................30 4.3.1 Introduction...............................................................................................................................................................30 4.3.2 Transmission Resource Management Strategies.......................................................................................................31

5 Related Features...........................................................................................................................36 5.1 Prerequisite Features.....................................................................................................................................................36 5.2 Mutually Exclusive Features........................................................................................................................................36 5.3 Impacted Features.........................................................................................................................................................36

6 Network Impact...........................................................................................................................37 Issue 02 (2014-12-30)


ii


Contents

6.1 System Capacity...........................................................................................................................................................37 6.2 Network Performance...................................................................................................................................................37

7 Engineering Guidelines.............................................................................................................38 7.1 When to Use Bandwidth Sharing of Multimode Base Station Co-Transmission.........................................................38 7.2 Required Information...................................................................................................................................................38 7.3 Planning........................................................................................................................................................................38 7.4 Deployment..................................................................................................................................................................39 7.4.1 Requirements.............................................................................................................................................................39 7.4.2 Data Preparation........................................................................................................................................................40 7.4.3 Precautions.................................................................................................................................................................50 7.4.4 Hardware Adjustment................................................................................................................................................50 7.4.5 Initial Configuration (Unlimited Access Bandwidth for GU Dual-Mode Base Stations).........................................50 7.4.6 Initial Configuration (Unlimited Access Bandwidth for GL/GT Dual-Mode Base Stations)...................................53 7.4.7 Initial Configuration (Unlimited Access Bandwidth for UL/UT/ULT Multimode Base Stations)...........................55 7.4.8 Initial Configuration (Unlimited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)..................57 7.4.9 Initial Configuration (Limited Access Bandwidth for GU Dual-Mode Base Stations).............................................60 7.4.10 Initial Configuration (Limited Access Bandwidth for GL/GT/GLT Multimode Base Stations)............................65 7.4.11 Initial Configuration (Limited Access Bandwidth for UL/UT/ULT Multimode Base Stations)............................68 7.4.12 Initial Configuration (Limited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations)....................72 7.4.13 Initial Configuration (Limited Access Bandwidth for Each Operator in a UL/UT Dual-Mode Base Station in RAN Sharing Scenarios)..............................................................................................................................................................78 7.4.14 Activation Observation (Unlimited Access Bandwidth for Multimode Base Stations)..........................................86 7.4.15 Activation Observation (Limited Access Bandwidth for Multimode Base Stations)..............................................87 7.4.16 Activation Observation (Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios)...................91 7.5 Performance Monitoring...............................................................................................................................................93 7.6 Parameter Optimization................................................................................................................................................93 7.7 Troubleshooting............................................................................................................................................................93

8 Parameters.....................................................................................................................................94 9 Counters......................................................................................................................................100 10 Glossary.....................................................................................................................................101 11 Reference Documents.............................................................................................................102

Issue 02 (2014-12-30)


iii


1 About This Document

1

About This Document

1.1 Scope This document describes the Bandwidth Sharing of Multimode Base Station Co-Transmission feature, including the bandwidth sharing mechanism, recommended transmission configuration strategies, application scenarios, related features, network impact, and engineering guidelines. This feature applies to GSM/UMTS, GSM/LTE, UMTS/LTE, and GSM/UMTS/LTE multimode base stations in co-transmission scenarios. This document describes the following optional features: l

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

l

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

l

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

l

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

In this document, the following naming conventions apply for LTE terms. Includes FDD and TDD

Includes FDD Only

Includes TDD Only

LTE

LTE FDD

LTE TDD

eNodeB

LTE FDD eNodeB

LTE TDD eNodeB

eRAN

LTE FDD eRAN

LTE TDD eRAN

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

1.2 Intended Audience This document is intended for personnel who: l Issue 02 (2014-12-30)

Need to understand the features described herein Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

1


l


Work with Huawei products

1.3 Change History This section provides information about the changes in different document versions. There are two types of changes, which are defined as follows: l

Feature change Changes in features of a specific product version

l

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

SRAN9.0 02 (2014-12-30) This issue includes the following changes. Change Type

Change Description

Parameter Change

Feature change

None.

None.

Editorial change

Optimized the document description of chapter 4 Application Scenarios.

None.

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

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

Change Description

Parameter Change

Feature change

l Added the descriptions of the LTE(TDD) mode support for Bandwidth Sharing of Multimode Base Station Co-Transmission feature.

None.

l Modified the flow control policy for a separateMPT multimode base station where co-transmission is implemented through backplane interconnection. Editorial change

Issue 02 (2014-12-30)

Added activation observation methods. For details, see 7.4.15 Activation Observation (Limited Access Bandwidth for Multimode Base Stations) and 7.4.16 Activation Observation (Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios).


None.

2



1.4 Differences Between Base Station Types Definition The macro base stations described in this document refer to 3900 series base stations. These base stations work in GSM, UMTS, or LTE mode, as listed in Table 1-1. The LampSite base stations described in this document refer to distributed base stations that provide indoor coverage. These base stations work in UMTS or LTE mode but not in GSM mode. The micro base stations described in this document refer to all integrated entities that work in UMTS or LTE mode but not in GSM mode. Descriptions of boards, cabinets, subracks, slots, and RRUs do not apply to micro base stations. The following table defines the types of micro base stations. Base Station Model

RAT

BTS3803E

UMTS

BTS3902E

UMTS

BTS3202E

LTE FDD

BTS3203E

LTE FDD

NOTE

The co-MPT and separate-MPT applications are irrelevant to single-mode micro base stations.

Feature Support by Macro, Micro, and LampSite Base Stations

Issue 02 (2014-12-30)

Feature ID

Feature Name

Support ed by Macro Base Stations

Supporte d by Micro Base Stations

Supporte d by LampSite Base Stations

MRFD-211505

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

Yes

No

No

MRFD-221505

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

Yes

N

Yes

MRFD-231505

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

Yes

N

Yes


3



Feature ID

Feature Name

Support ed by Macro Base Stations

Supporte d by Micro Base Stations

Supporte d by LampSite Base Stations

MRFD-241505

Bandwidth sharing of MBTS Multi-mode Co-Transmission (LTE TDD)

Yes

No

No

Function Implementation in Macro, Micro, and LampSite Base Stations None.

Issue 02 (2014-12-30)


4


2 Overview

2

Overview

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

2.2 Benefits The Bandwidth Sharing of Multimode Base Station Co-Transmission feature provides the following benefits: l

Saved transmission resources

GSM, UMTS, and LTE services have different peak hours. Therefore, the transmission resources of one mode (for example, GSM) can be multiplexed by the other modes (for example, UMTS and LTE) if GSM is not experiencing a traffic peak. For a multimode base station in cotransmission scenarios, transmission resources can be shared by GSM, UMTS, and LTE. This promotes resource utilization and ultimately uses fewer transmission resources. As GSM services continuously shrink, the released GSM bandwidth is gradually occupied by UMTS and LTE services, which promotes transmission resource utilization. l

Issue 02 (2014-12-30)

Guaranteed service quality and user experience


5


2 Overview

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

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

MME: mobility management entity S-GW: serving gateway MPT: main processing and transmission unit

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

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

Issue 02 (2014-12-30)


6


2 Overview

NOTE

l In this document, a multimode base station can be a GU/GL/GT/UL/UT/LT dual-mode base station, a GUL/GLT/ULT/GUT triple-mode base station, or a GULT quadruple-mode base station. l GBTS or eGBTS refers to the GSM side of a multimode base station. NodeB refers to the UMTS side of a multimode base station. eNodeB refers to the LTE side of a multimode base station. LTE can be LTE FDD, LTE TDD, or LTE FDD<E TDD. l Multimode base stations are classified into co-MPT and separate-MPT multimode base stations, both introduced in SRAN8.0. In a co-MPT multimode base station, different modes share one main control board and one O&M channel. In a separate-MPT multimode base station, each mode has its own main control board and its own O&M channel. The GSM side of a separate-MPT multimode base station can be either an eGBTS or a GBTS. The GSM side of a co-MPT multimode base station must be an eGBTS. l The GBTS is not recommended for providing a co-transmission port to a separate-MPT multimode base station. This scenario is not covered in this document.

Issue 02 (2014-12-30)


7


3 Technical Description

3

Technical Description

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

For a separate-MPT multimode base station in co-transmission scenarios, the cotransmission port transmits and receives the local data and the passing data. In this case, the co-transmission port centrally schedules and manages the data of multiple modes.

l

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

l Differentiation: Transmission differentiation is used when transmission bandwidth is limited. Transmission differentiation prioritizes bandwidth use, with real-time services taking precedence over non-real-time services. l Fairness: If transmission congestion occurs, service differentiation ensures that real-time services are preferentially processed. As a result, non-real-time services may experience packet losses, which affects fairness among non-real-time services. The transmission flow control function enables each type of service or each mode to be allocated a certain amount of bandwidth. This eliminates the possibility that a certain service or a certain mode experiences service interruptions because of lack of transmission bandwidth.

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

Issue 02 (2014-12-30)

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.


8



Base Station Name

Definition

NodeB

NodeB refers to a base station deployed with WMPT or UMPT_U.

eNodeB

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

Co-MPT Multimode Base Station

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

Separate-MPT Multimode Base Station

Separate-MPT multimode base station refers to a base station on which different modes use different main control boards. For example, base stations deployed with GTMU and WMPT are called separate-MPT GSM/UMTS dual-mode base station.

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

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

DSCP DSCP is a field in an IP packet header to indicate the QoS requirements. Each node implements DiffServ based on the DSCP value. A multimode base station or base station controller sets the DSCP value for each IP packet based on the QoS requirements of each service type. From the DSCP value, transmission devices identify the traffic class and related QoS requirements of the service and perform per-hop Issue 02 (2014-12-30)


9



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

Command

Description

GBTS

SET BTSVLAN

Used to set the mapping between DSCP values and data from the O&M plane, control plane (CP), and user plane (UP) on the GBTS side.

eGBTS and

SET DIFPRI

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

ADD TRMMAP and SET PHBMAP

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

SET DIFPRI

Used to set the mapping between DSCP values and data from the O&M plane and CP plane on the eNodeB side.

MOD UDTPARAGRP

Used to set the mapping between DSCP values and data from the UP on the eNodeB side.

NodeB

eNodeB

Pay attention to the following when mapping traffic classes to DSCP values: l

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

l

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

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

VLAN Priority The VLAN tag defines an IP packet's VLAN priority. Based on the VLAN priority, Layer 2 devices can implement DiffServ. VLAN priorities of packets with different traffic classes can be determined by DSCP values. Table 3-3 provides the default mapping between DSCP values and VLAN priorities on the multimode base station side. Issue 02 (2014-12-30)


10



Table 3-3 Default mapping between DSCP values and VLAN priorities DSCP Value

VLAN Priority

0–7

0

8–15

1

16–23

2

24–31

3

32–39

4

40–47

5

48–55

6

56–63

7

Queue Priority Queue priority defines the scheduling priority of a queue. Each Ethernet port or Point-to-Point Protocol (PPP) link supports eight queues: PQ1, PQ2, PQ3, and WRR (which includes WFQ4 through WFQ8). The queues are displayed in descending order of scheduling priority. A multimode base station puts packets with different traffic classes into different queues to implement DiffServ. NOTE

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

Queue priorities are determined by the mapping between DSCP values and queue priorities, as listed in Table 3-4 and Table 3-5. You are not advised to modify the default mapping between DSCP values and queue priorities. Table 3-4 Default mapping between DSCP values and queue priorities for the GBTS

Issue 02 (2014-12-30)

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


11



DSCP Value

Queue

Queue Priority

0–7

WFQ8

3

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

Queue

Queue Priority

48–63

PQ1

0

40–47

PQ2

1

32–39

PQ3

2

24–31

WFQ4

3

16–23

WFQ5

3

8–15

WFQ6

3

0–7

WFQ7

3

3.3 Traffic Limiting and Shaping When transmission resources are limited, transmission devices may be incapable of receiving excess packets that arrive at the co-transmission port in a multimode base station. To prevent transmission devices from discarding packets, the traffic limiting function is introduced. PS services have unstable data rates due to unexpected traffic bursts. The traffic shaping function is introduced to ensure stable rates in a multimode base station. The traffic limiting and shaping functions use the Generic Traffic Shaping (GTS) technology, which shapes irregular data flows to balance the bandwidth between upstream and downstream nodes. These functions minimize packet discarding and congestion caused by traffic bursts. Figure 3-1 shows the working principles of rate limitation and traffic shaping.

Issue 02 (2014-12-30)


12



Figure 3-1 Working principles of rate limitation and traffic shaping W ith o u t r a te lim ita tio n D a ta tra ffic

S p e c ifie d b a T h e s p e c ifie d b a n d w id th m u s t b e g re a te r th a n th e p e a k d a ta tra ffic v o lu m e .

0

T im e W ith r a te lim ita tio n

D a ta tra ffic

If th e s p e c ifie d b a n d w id th is e x c e e d e d , e x c e s s p a c k e ts a re d ire c tly d is c a rd e d .

S p e c ifie d b a

0

T im e W ith r a te lim ita tio n a n d tr a ffic s h a p in g

D a ta tra ffic

If th e s p e c ifie d b a n d w id th is e x c e e d e d , e x c e s s p a c k e ts a re b u ffe re d .

S p e c ifie d b a W h e n th e d a ta tra ffic v o lu m e is le s s th a n th e s p e c ifie d b a n d w id th , th e b u ffe re d p a c k e ts a re tra n s m itte d . 0

T im e

The traffic limiting and shaping functions apply only to non-real-time services. NOTE

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

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

Base-station-level traffic limiting and shaping – Separate-MPT multimode base station If the eGBTS, NodeB, or eNodeB provides a co-transmission port, you can run the SET LR command and specify the CIR parameter to set the bandwidth after rate limitation for a base station. – Co-MPT multimode base station You can run the SET LR command and specify the CIR parameter to set the bandwidth after rate limitation for a base station.

l

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

Issue 02 (2014-12-30)


13



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

Multimode base station controller You can run the ADD IPLOGICPORT command and specify the CIR parameter to set the bandwidth after rate limitation for a logical port. NOTE

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

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

Admission control: ensures quality of the admitted services by preventing excessive admissions.

l

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

l

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

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

3.5 Flow Control When transmission bandwidth dynamically changes, the bandwidth available for the bottleneck nodes may be smaller than the bandwidth after rate limitation on the shared port. If the base station keeps transmitting data at the bandwidth after rate limitation, the transport network may Issue 02 (2014-12-30)


14



be congested. To prevent transport network congestion, the flow control algorithm is introduced. This algorithm first estimates the bottleneck bandwidth based on the transmission quality test and then dynamically adjusts the transmit bandwidth to ensure that the transmit bandwidth does not exceed the bottleneck bandwidth. Table 3-6 lists whether GSM, UMTS, and LTE support the flow control algorithm. Table 3-6 Whether GSM, UMTS, and LTE support the flow control algorithm Mode

NE

Support Flow Control

Remarks

GSM

GBTS/eGBTS and BSC

No

None

UMTS

NodeB and RNC

Yes

The flow control algorithm is also called the dynamic flow control algorithm.

LTE

eNodeB

Yes

The flow control algorithm is disabled by default.

The flow control algorithm on a NodeB calculates the transmission delay, the number of discarded packets, and bandwidth resources available and then performs traffic shaping. In this way, packet discarding caused by Iub interface congestion is prevented. This algorithm takes effect only on HSDPA and HSUPA services. The NodeB dynamic flow control algorithm is classified into two types, as listed in Table 3-7. Table 3-7 Classification of the NodeB dynamic flow control algorithm NodeB Dynamic Flow Control Algorithm

Control Switch

Reference Document

NodeB uplink bandwidth adaptive adjustment algorithm

l Congestion control switch: TNLCONGCTRLSWITCH

Transmission Resource Management Feature Parameter Description for RAN

NodeB HSDPA adaptive flow control algorithm

Flow control switch: SWITCH

l Back pressure algorithm switch: TCSW

For a co-MPT UL or GUL multimode base station in co-transmission scenarios, if UMTS HSDPA services are undergoing flow control, the released UMTS bandwidth may be occupied by LTE services. Consequently, bandwidth available for UMTS services may decrease considerably. To protect UMTS bandwidth, enable the fair flow control switch (FAIRSWITCH) on the NodeB side. The fair switch ensures that at least 30% of the actual receive bandwidth is retained for UMTS HSDPA services. For example, if the total bandwidth Issue 02 (2014-12-30)


15



for UMTS HSDPA services decreases to 30% of the actual receive bandwidth, data rates for UMTS HSDPA services will not be reduced. It is recommended that the FAIRRATIO parameter be set to a value between 30% and 70%. If this parameter is set to a value less than 30% or greater than 70%, the actual bandwidth of the UMTS HSDPA services may be inconsistent with the guard bandwidth configured for fair flow control. The default value of the FAIRRATIO parameter is equal to 30% of the actual receive bandwidth of the base station. That is, when the total bandwidth of the UMTS HSDPA services decreases to 30% of the actual receive bandwidth of the base station, rate reduction will no longer be performed on these services. The fair flow control switch can be configured either on a physical port of a co-MPT UL dualmode base station or on the corresponding loopback interface (also called logical port) of the physical port, with the physical port preferred. When configured on the loopback interface, the fair flow control switch for co-MPT base stations applies only to the following scenarios: l

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

l

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

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

Issue 02 (2014-12-30)


16



NOTE

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

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

Issue 02 (2014-12-30)


17


4 Application Scenarios

4

Application Scenarios

4.1 Unlimited Access Bandwidth for Multimode Base Stations 4.1.1 Introduction Unlimited access bandwidth for multimode base stations refers to scenarios in which: l

The operator cannot or has not planned access bandwidth for each multimode base station.

l

The bandwidth of the converging device, which converges the data of multimode base stations, is either limited or unlimited.

For example, in Figure 4-1, the access bandwidth for the three multimode base stations is the maximum bandwidth 100 Mbit/s and bandwidth for intermediate transmission devices is also the maximum bandwidth 100 Mbit/s. Figure 4-1 Unlimited access bandwidth for multimode base stations

Issue 02 (2014-12-30)


18



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

(Optional) Configuring Traffic Limiting and Shaping on the Base Station Controller Side Traffic limiting and shaping can be configured on the base station controller side if the operator can dimension transmission bandwidth required by a base station based on the traffic model. The bandwidth after rate limitation is calculated based on the service model.

Configuring the Mapping Between Traffic Classes and Transmission Priorities Table 4-1 lists recommended transmission priorities for different traffic classes. For details about the mapping between DSCP values and traffic classes, see descriptions about DSCP in chapter 3 Technical Description. Table 4-1 Recommended transmission priorities for different traffic classes if access bandwidth is unlimited for multimode base stations NE

Traffic Class

PHB

DSCP Value

VLAN Priority

GBTS

ESL/OML/RSL

CS6

48

6

CS Voice

EF

46

5

CS Data/PS High PRI

AF41

34

4

PS Low PRI

AF31

26

3

IP Clock

EF

46

5

EML

AF21

18

2

SCTP

CS6

48

6

CS Voice

EF

46

5

CS Data/PS High PRI

AF41

34

4

PS Low PRI

AF31

26

3

OM High

EF

46

5

OM Low

AF21

18

2

IP Clock

EF

46

5

SCTP

CS6

48

6

CCH&SRB&AMR

EF

46

5

eGBTS

NodeB

Issue 02 (2014-12-30)


19


NE

eNodeB


Traffic Class

PHB

DSCP Value

VLAN Priority

Conversational&Strea ming

AF41

34

4

R99 interactive&background

AF21

18

2

HSxPA interactive&background

AF11

10

1

OM High

EF

46

5

OM Low

AF21

18

2

IP Clock

EF

46

5

SCTP

CS6

48

6

QCI1

EF

46

5

QCI2

AF41

34

4

QCI3

AF41

34

4

QCI4

AF41

34

4

QCI5

EF

46

5

QCI6

AF21

18

2

QCI7

AF21

18

2

QCI8

AF21

18

2

QCI9

BE

0

0

OM High

EF

46

5

OM Low

AF21

18

2

IP Clock

EF

46

5

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

Issue 02 (2014-12-30)


20



Table 4-2 Recommended transmission priority combining strategies if access bandwidth is unlimited for multimode base stations Number of Queues

DSCP Value Combining Strategy

VLAN Priority Combing Strategy

6

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

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

5

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

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

4

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

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

3

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

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

NOTE

If there are only two queues, obtain from Huawei technical support personnel the method of combining DSCP values.

Configuring the Flow Control Algorithm Table 4-3 provides recommended settings for the NodeB dynamic flow control algorithm and the HSDPA fair flow control switch. Table 4-3 Recommended settings for the NodeB flow control algorithm and the HSDPA fair flow control switch if access bandwidth is unlimited for multimode base stations Base Station Type

Setting of the HSUPA Congestion Control Switch

Setting of the HSDPA Adaptive Flow Control Algorithm Switch

Setting of the HSDPA Fair Flow Control Switch

Separate-MPT GU dual-mode base station

ON(On) (default value)

BW_SHAPING_O NOFF_TOGGLE (BW_SHAPING_O NOFF_TOGGLE) (default value)

N/A

N/A

N/A

N/A

Co-MPT GU dualmode base station Separate-MPT GL dual-mode base station

Issue 02 (2014-12-30)


21


Base Station Type





OFF(Off)

l BW_SHAPING _ONOFF_TOG GLE (BW_SHAPING _ONOFF_TOG GLE) (default value): if the bearer network supports three or more queues

N/A

Co-MPT GL dualmode base station Separate-MPT UL dual-mode base station

l NO_BW_SHAP ING (NO_BW_SHA PING): if the bearer network supports only two queues Co-MPT UL dualmode base station

OFF(Off)


ENABLE(Enable)

l NO_BW_SHAP ING (NO_BW_SHA PING): if the bearer network supports only two queues

Issue 02 (2014-12-30)


22



Base Station Type




Separate-MPT GUL triple-mode base station

OFF(Off)


N/A

l NO_BW_SHAP ING (NO_BW_SHA PING): if the bearer network supports only two queues Co-MPT GUL triplemode base station

OFF(Off)


ENABLE(Enable)

l NO_BW_SHAP ING (NO_BW_SHA PING): if the bearer network supports only two queues

4.2 Limited Access Bandwidth for Multimode Base Stations 4.2.1 Introduction Limited access bandwidth for multimode base stations refers to scenarios in which:

Issue 02 (2014-12-30)


23



l

The maximum data rate for each multimode base station must not exceed the planned bandwidth.

l

The bandwidth of intermediate transmission devices is either limited or unlimited.

The access bandwidth for a base station is limited if the bearer network is leased or if the base station uses satellite, microwave, or xPON to receive data. For example, in Figure 4-2, the access bandwidth for the three multimode base stations is limited to 10 Mbit/s. Figure 4-2 Limited access bandwidth for multimode base stations

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

Configuring Traffic Limiting and Shaping on the Base Station Controller Side Set the bandwidth after rate limitation to the access bandwidth planned by the operator for a multimode base station.

Configuring Traffic Limiting and Shaping on the Co-Transmission Port of the Base Station Side Set the bandwidth after rate limitation to the access bandwidth planned by the operator for a multimode base station.

Issue 02 (2014-12-30)


24



Configuring the Mapping Between Traffic Classes and DSCP Values Table 4-4 lists recommended transmission priorities for different traffic classes. Table 4-4 Recommended transmission priorities for different traffic classes if access bandwidth is limited for multimode base stations NE

Traffic Class

PHB

DSCP Value

VLAN Priority

GBTS

ESL/OML/RSL

CS6

48

6

CS Voice

EF

46

5

CS Data/PS High PRI

AF41

34

4

PS Low PRI

AF31

26

3

IP Clock

CS6

46

6

EML

AF21

18

2

SCTP

CS6

48

6

CS Voice

EF

46

5

CS Data/PS High PRI

AF41

34

4

PS Low PRI

AF31

26

3

OM High

EF

46

5

OM Low

AF21

18

2

IP Clock

CS6

46

6

SCTP

CS6

48

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

IP Clock

EF

46

5

SCTP

CS6

48

6

QCI1

EF

46

5

eGBTS

NodeB

eNodeB

Issue 02 (2014-12-30)


25


NE


Traffic Class

PHB

DSCP Value

VLAN Priority

QCI2

AF41

34

4

QCI3

AF41

34

4

QCI4

AF41

34

4

QCI5

EF

46

5

QCI6

AF21

18

2

QCI7

AF21

18

2

QCI8

AF21

18

2

QCI9

BE

0

0

OM High

EF

46

5

OM Low

AF21

18

2

IP Clock

EF

46

5

In most cases, transmission devices support queue scheduling. Layer 3 and Layer 2 transmission devices support eight queues. However, if transmission devices in the bearer network support less than eight queues, transmission priority combining strategies listed in Table 4-5 are recommended. You can combine packets with different DSCP values into one queue and combine packets with different VLAN priorities into one queue. For example, if the transmission devices support six queues, packets whose DSCP values are 48 and 46 can be put into one queue. Accordingly, packets whose VLAN priorities are 6 and 5 can be put into one queue. This queue has the highest transmission priority. Table 4-5 Recommended transmission priority combining strategies if access bandwidth is limited for multimode base stations

Issue 02 (2014-12-30)

Number of Queues



6



5

DSCP values for the five queues VLAN priorities for the five are (48+46), (34+26), 18, 10, and queues are (6+5), 4, 3, 2, (1+0), 0, respectively. respectively.

4




26



Number of Queues



3

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


NOTE


Configuring the Flow Control Algorithm Table 4-6 provides recommended settings for the NodeB dynamic flow control algorithm and the HSDPA fair flow control switch. Table 4-6 Recommended settings for the NodeB flow control algorithm and the HSDPA fair flow control switch if access bandwidth is limited for multimode base stations Base Station Type

Setting of the Traffic Control Switch




SeparateMPT GU dual-mode base station

ENABLE(Enable) (default value)

ON(On) (default value)

BW_SHAPING_ON OFF_TOGGLE (BW_SHAPING_ON OFF_TOGGLE) (default value)

N/A


N/A

N/A

N/A

Co-MPT GU dual-mode base station SeparateMPT GL dual-mode base station Co-MPT GL dual-mode base station

Issue 02 (2014-12-30)


27



Base Station Type





SeparateMPT UL dual-mode base station

l ENABLE (Enable) (default value): if cotransmission is implemented through backplane interconnection

OFF(Off)

l BW_SHAPING_ ONOFF_TOGGL E (BW_SHAPING_ ONOFF_TOGGL E) (default value): if the bearer network supports three or more queues

N/A

l DISABLE (Disable):if cotransmission is implemented through panel interconnection Co-MPT UL dual-mode base station


l NO_BW_SHAPI NG (NO_BW_SHAPI NG): if the bearer network supports only two queues OFF(Off)


ENABLE (Enable)

l NO_BW_SHAPI NG (NO_BW_SHAPI NG): if the bearer network supports only two queues

Issue 02 (2014-12-30)


28



Base Station Type





SeparateMPT GUL triple-mode base station


OFF(Off)


N/A

l DISABLE (Disable):if cotransmission is implemented through panel interconnection Co-MPT GUL triplemode base station


l NO_BW_SHAPI NG (NO_BW_SHAPI NG): if the bearer network supports only two queues OFF(Off)


ENABLE (Enable)

l NO_BW_SHAPI NG (NO_BW_SHAPI NG): if the bearer network supports only two queues

Issue 02 (2014-12-30)


29



NOTE

l TCSW is set to ENABLE by default. If you want to set TCSW to DISABLE, first run the ADD RSCGRP command to add a default transmission resource group to the co-transmission port with RSCGRPID set to DEFAULTPORT. Then set TCSW to DISABLE for the default transmission resource group you have added. l If a separate-MPT multimode base station uses backplane interconnection to implement cotransmission, the tunnel type (TUNNELTYPE) of the main control board that provides the cotransmission port must be set to DL and that of the main control board that does not provide the cotransmission port must be set to UL. If the tunnel type is incorrect, the traffic control function cannot work properly. For details about tunnel type configuration, see Common Transmission Feature Parameter Description for SingleRAN.

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

4.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios 4.3.1 Introduction Limited access bandwidth for each operator in radio access network (RAN) sharing scenarios refer to scenarios in which: l

Multiple operators share one multimode base station.

l

Access bandwidth of one operator is not shared by other operators.

l

Access bandwidth of one operator is shared among services of each mode run by this operator.

l

Access bandwidth for each operator is limited.

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

Issue 02 (2014-12-30)


30



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

4.3.2 Transmission Resource Management Strategies This section describes how to configure transmission resource management strategies in this scenario.

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

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

Configuring the Mapping Between Traffic Classes and DSCP Values Table 4-7 lists recommended transmission priorities for different traffic classes. Table 4-7 Recommended transmission priorities for different traffic classes if access bandwidth is limited for each operator in RAN sharing scenarios

Issue 02 (2014-12-30)

NE

Traffic Class

PHB

DSCP Value

VLAN Priority

NodeB

SCTP

CS6

48

6

CCH&SRB&AMR

EF

46

5


AF41

34

4


31


NE

eNodeB


Traffic Class

PHB

DSCP Value

VLAN Priority


AF21

18

2


AF11

10

1

OM High

EF

46

5

OM Low

AF21

18

2

IP Clock

EF

46

5

SCTP

CS6

48

6

QCI1

EF

46

5

QCI2

AF41

34

4

QCI3

AF41

34

4

QCI4

AF41

34

4

QCI5

EF

46

5

QCI6

AF21

18

2

QCI7

AF21

18

2

QCI8

AF21

18

2

QCI9

BE

0

0

OM High

EF

46

5

OM Low

AF21

18

2

IP Clock

EF

46

5

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

Issue 02 (2014-12-30)


32



Table 4-8 Recommended transmission priority combining strategies if access bandwidth is limited for each operator in RAN sharing scenarios Number of Queues



6



5

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

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

4



3

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


NOTE


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

Issue 02 (2014-12-30)


33



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





SeparateMPT UL dual-mode base station


OFF(Off):

l BW_SHAPING_ ONOFF_TOGG LE (BW_SHAPING _ONOFF_TOGG LE) (default value): if the bearer network supports three or more queues

N/A

l DISABLE (Disable):if cotransmission is implemented through panel interconnection Co-MPT UL dual-mode base station


l NO_BW_SHAPI NG (NO_BW_SHAP ING): if the bearer network supports only two queues OFF(Off)

l BW_SHAPING_ ONOFF_TOGG LE (BW_SHAPING _ONOFF_TOGG LE) (default value): if the bearer network supports three or more queues

ENABLE (Enable)

l NO_BW_SHAPI NG (NO_BW_SHAP ING): if the bearer network supports only two queues

Issue 02 (2014-12-30)


34



NOTE

l TCSW is set to ENABLE by default. If you want to set TCSW to DISABLE, first run the ADD RSCGRP command to add a default transmission resource group to the co-transmission port with RSCGRPID set to DEFAULTPORT. Then set TCSW to DISABLE for the default transmission resource group you have added. l If a separate-MPT multimode base station uses backplane interconnection to implement cotransmission, the tunnel type (TUNNELTYPE) of the main control board that provides the cotransmission port must be set to DL and that of the main control board that does not provide the cotransmission port must be set to UL. If the tunnel type is incorrect, the traffic control function cannot work properly. For details about tunnel type configuration, see Common Transmission Feature Parameter Description for SingleRAN.

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

Issue 02 (2014-12-30)


35


5 Related Features

5

Related Features

5.1 Prerequisite Features l

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

l

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

l

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

l

MRFD-241501 IP-Based Multi-mode Co-Transmission on BS side(LTE TDD)

5.2 Mutually Exclusive Features None

5.3 Impacted Features None

Issue 02 (2014-12-30)


36


6 Network Impact

6

Network Impact

6.1 System Capacity No impact.

6.2 Network Performance If the settings of inter-RAT parameters, such as inter-RAT bandwidth allocation and inter-RAT QoS planning, are inappropriate, activating this feature will have the following impacts: l

Increased service congestion rates

l

Reduced data rates of low-priority services, for example, best effort (BE) services

l

Increased packet loss rates of low-priority services

Issue 02 (2014-12-30)


37


7

7 Engineering Guidelines

Engineering Guidelines

7.1 When to Use Bandwidth Sharing of Multimode Base Station Co-Transmission It is recommended that the Bandwidth Sharing of Multimode Base Station Co-Transmission feature be activated for a multimode base station where IP-based co-transmission is applied.

7.2 Required Information To provide guide on how to plan transmission bandwidth and transmission priorities for multimode base stations and multimode base station controllers, you need to know the network topology and transmission bandwidth plan, which include transmission bandwidth available in the bearer network and the queues available on transmission devices.

7.3 Planning This section describes planning activities you need to complete before you implement the feature.

RF Planning N/A

Network Planning l

Transmission bandwidth plan for radio services Make a transmission bandwidth plan each for the GBTS/eGBTS, NodeB, and eNodeB of a multimode base station based on the service plan and the corresponding bandwidth requirements.

l

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

Issue 02 (2014-12-30)


38



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

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

l

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

l

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

Hardware Planning N/A

7.4 Deployment This section describes how to deploy the Bandwidth Sharing of Multimode Base Station CoTransmission feature.

7.4.1 Requirements l

Transmission devices To implement the Bandwidth Sharing of Multimode Base Station Co-Transmission feature, the bearer network must support QoS management. Otherwise, this feature becomes invalid when the bearer network is congested. QoS management includes the following aspects: – Layer 3 devices support DSCP-priority-based QoS management. – Layer 2 devices support VLAN-priority-based QoS management. – Transmission devices support the PQ+WRR queue scheduling function, and at least two PQ queues are supported. (WRR stands for weighted round robin.)

l

Other features – If the GBTS provides a co-transmission port, the MRFD-211501 IP-Based Multi-mode Co-Transmission on BS side(GBTS) feature must be activated on the BTS. – If the NodeB provides a co-transmission port, the MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side(NodeB) feature must be activated on the NodeB. – If the eNodeB provides a co-transmission port, the MRFD-231501 IP-Based Multimode Co-Transmission on BS side(eNodeB) feature must be activated on the eNodeB.

Issue 02 (2014-12-30)


39



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

License The license for the Bandwidth Sharing of Multimode Base Station Co-Transmission feature has been activated. Table 7-1 License control items Featu re ID

Feature Name

License Control Item ID

License Control Item

NE

Sales Unit

MRFD -21150 5

Bandwidth sharing of MBTS Multi-mode CoTransmission (GBTS)

LGMIBSMCT

Bandwidth sharing of MBTS Multimode CoTransmission (GBTS)

BSC

per BTS

MRFD -22150 5

Bandwidth sharing of MBTS Multi-mode CoTransmission (NodeB)

LQW9BSMCT0 1

Bandwidth sharing of MBTS Multimode CoTransmission (NodeB)

NodeB

per NodeB

MRFD -23150 5

Bandwidth sharing of MBTS Multi-mode CoTransmission (eNodeB)

LT1S0COMBS0 0

Bandwidth sharing of MBTS Multimode CoTransmission (FDD)

eNode B

per eNodeB

MRFD -24150 5

Bandwidth sharing of MBTS Multi-mode CoTransmission (LTE TDD)

LT1SBSMMCT0 0

Bandwidth sharing of MBTS Multimode CoTransmission (LTE TDD)

eNode B

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 shaping must be prepared on the base station side that provides a co-transmission port. Table 7-2 lists the data to prepare for configuring traffic limiting and shaping.

Issue 02 (2014-12-30)


40



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

Parameter Name

Parameter ID

Setting Notes

Data Source

LR

UL Committed Information Rate

CIR

Set this parameter to the access bandwidth planned by the operator.

Network plan

Committed Burst Size

CBS

Network plan

Excessive Burst Size

EBS

l If the CIR value is smaller than 500 Mbit/s, set CBS to the CIR value multiplied by 2 and set EBS to 0 Mbit/s.

Network plan

l If the CIR value is greater than 500 Mbit/s, set CBS to 1000 Mbit/s to ensure that the sum of CBS and EBS is twice the CIR value.

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

Parameter Name

Parameter ID

Setting Notes

Data Source

RSCGRP

Tx Bandwidth

TXBW

Set this parameter to the access bandwidth planned by the operator.

Network plan

TX Committed Burst Size

TXCBS

Network plan l If the TXBW value is smaller than 500 Mbit/ s, set TXCBS to the TXBW value multiplied by 2 and set TXEBS to 0 Mbit/s. l If the TXBW value is greater

Issue 02 (2014-12-30)


41


MO


Parameter Name

Parameter ID

TX Excessive Burst Size

TXEBS

Setting Notes

Data Source

than 500 Mbit/ s, set TXCBS to 1000 Mbit/s to ensure that the sum of TXCBS and TXEBS is twice the TXBW value.

Network plan

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

Issue 02 (2014-12-30)

MO

Parameter Name

Parameter ID

Setting Notes

Data Source

IPLOGICPORT

Logic Port No.

LPN

Set this parameter to the number of the BSC/RNC logical port.

Network plan


42


MO


Parameter Name

Parameter ID

Setting Notes

Data Source

Bandwidth

CIR

Set this parameter to the access bandwidth planned by the operator or bandwidth calculated by the traffic model. When the access bandwidth is limited for each operator in RAN sharing scenarios, set this parameter to the access bandwidth planned by each operator.

Network plan

Transport QoS l

Transport QoS for GSM services – Table 7-5 lists the data to prepare for configuring the mapping between DSCP values and data from the O&M plane, CP, and UP of a GBTS. – Table 7-6 lists the data to prepare for configuring the mapping between DSCP values and data from the O&M plane and CP of an eGBTS. – Table 7-8 lists the data to prepare for configuring the mapping between DSCP values and data from the O&M plane and CP of a BSC. Table 7-9 lists the data to prepare for configuring the mapping between DSCP values and data from the UP of a BSC.

l

Transport QoS for UMTS services – Table 7-6 lists the data to prepare for configuring the mapping between DSCP values and data from the O&M plane and CP of a NodeB. – Table 7-10 lists the data to prepare for configuring the mapping between DSCP values and data from the O&M plane, CP, and UP of an RNC.

l

Transport QoS for LTE services – Table 7-6 lists the data to prepare for configuring the mapping between DSCP values and data from the O&M plane and CP of an eNodeB. – Table 7-7 lists the data to prepare for configuring the mapping between DSCP values and data from the UP of an eNodeB.

Issue 02 (2014-12-30)


43



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

Parameter Name

Parameter ID

Setting Notes

Data Source

BTSVLAN

Service Type

SERVICETYP E

Network plan

DSCP

DSCP

See the recommended parameter configurations in chapter 4 Application Scenarios.

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

Issue 02 (2014-12-30)

MO

Parameter Name

Parameter ID

Setting Notes

Data Source

DIFPRI

Priority Rule

PRIRULE

Set this parameter to the DSCP value.

Network plan

Signaling Priority

SIGPRI

OM High Priority

OMHIGHPRI

OM Low Priority

OMLOWPRI


IP Clock Priority

IPCLKPRI


44



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

Parameter Name

Parameter ID

Setting Notes

Data Source

UDTPARAGR P

User Data Type Transfer Parameter Group ID

UDTPARAGR PID

Set this parameter to 40–48. This value corresponds to the value of the User Data Type (1–9) by default.

Network plan

Priority

PRI


Network plan

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

Parameter Name

Parameter ID

Setting Notes

Data Source

BSCABISPRI MAP

OML DSCP

OMLDSCP

Network plan

RSL DSCP

RSLDSCP

EML DSCP

EMLDSCP

ESL DSCP

ESLDSCP


Network plan Network plan Network plan

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

Issue 02 (2014-12-30)

MO

Parameter Name

Parameter ID

Setting Notes

Data Source

TRMMAP

CS voice path

CSVOICEPAT H

Network plan

CS data path

CSDATAPAT H

See the recommended parameter configurations in chapter 4


Network plan

45


MO


Parameter Name

Parameter ID

Setting Notes

Data Source

PS high PRI data path

PSHPRIDATA PATH

Application Scenarios.

Network plan

PS low PRI data path

PSLPRIDATA PATH

Network plan

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

Issue 02 (2014-12-30)

MO

Parameter Name

Parameter ID

Setting Notes

Data Source

TRMMAP

Common channel primary path

CCHPRIPATH

Network plan

IMS SRB primary path

SIPPRIPATH

SRB primary path

SRBPRIPATH


AMR voice primary path

VOICEPRIPA TH

Network plan

R99 CS conversational primary path

CSCONVPRIP ATH

Network plan

R99 CS streaming primary path

CSSTRMPRIP ATH

Network plan

R99 PS conversational primary path

PSCONVPRIP ATH

Network plan

R99 PS streaming primary path

PSSTRMPRIP ATH

Network plan

R99 PS high PRI interactive primary path

PSINTHGHPR IPATH

Network plan

R99 PS middle PRI interactive primary path

PSINTMIDPR IPATH

Network plan


Network plan Network plan

46


MO

Issue 02 (2014-12-30)


Parameter Name

Parameter ID

Setting Notes

R99 PS low PRI interactive primary path

PSINTLOWPR IPATH

Network plan

R99 PS background primary path

PSBKGPRIPA TH

Network plan

HSDPA Signal primary path

HDSRBPRIPA TH

Network plan

HSDPA IMS Signal primary path

HDSIPPRIPA TH

Network plan

HSDPA Voice primary path

HDVOICEPRI PATH

Network plan

HSDPA conversational primary path

HDCONVPRI PATH

Network plan

HSDPA streaming primary path

HDSTRMPRIP ATH

Network plan

HSDPA high PRI interactive primary path

HDINTHGHP RIPATH

Network plan

HSDPA middle PRI interactive primary path

HDINTMIDPR IPATH

Network plan

HSDPA low PRI interactive primary path

HDINTLOWP RIPATH

Network plan

HSDPA background primary path

HDBKGPRIPA TH

Network plan

HSUPA Signal primary path

HUSRBPRIPA TH

Network plan

HSUPA IMS Signal primary path

HUSIPPRIPA TH

Network plan

HSUPA Voice primary path

HUVOICEPRI PATH

Network plan


Data Source

47


MO


Parameter Name

Parameter ID

Setting Notes

Data Source

HSUPA conversational primary path

HUCONVPRI PATH

Network plan

HSUPA streaming primary path

HUSTRMPRIP ATH

Network plan

HSUPA high PRI interactive primary path

HUINTHGHP RIPATH

Network plan

HSUPA middle PRI interactive primary path

HUINTMIDPR IPATH

Network plan

HSUPA low PRI interactive primary path

HUINTLOWP RIPATH

Network plan

HSUPA background secondary path

HUBKGPRIPA TH

Network plan

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

Issue 02 (2014-12-30)

MO

Parameter Name

Parameter ID

Setting Description

Data Source

RSCGRPALG

Traffic Control Switch

TCSW


Negotiated by the peer end

ULFLOWCTR LPARA

Congestion Ctrl Switch

TNLCONGCT RLSWITCH

Negotiated by the peer end

DLFLOWCTR LPARA

Flow Control Switch

SWITCH

Fair Switch

FAIRSWITCH



48



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

Sample Value

Remarks

Limited access bandwidth for a base station

20 Mbit/s

This data specifies the uplink and downlink limited access bandwidth for a base station.

Downlink bandwidth on the logical port of the RNC

20 Mbit/s

This data item specifies the downlink limited access bandwidth for a base station.

Downlink bandwidth on the logical port of the BSC

10 Mbit/s

Calculates the bandwidth for this port based on the traffic model of the multimode base station.

BTS index

1

None

Logical IP address of the BTS

16.16.90.201

None

Port IP address of the BSC

172.16.140.140

None

Logical IP address of the NodeB

16.16.70.201

None

IP address of an Iub port on the RNC side

172.16.100.140

None

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

Issue 02 (2014-12-30)

Data Item

Sample Value

Remarks

Limited access bandwidth for operator A

10 Mbit/s

This data specifies the uplink and downlink limited access bandwidth for operator A.

Limited access bandwidth for operator B

10 Mbit/s

This data specifies the uplink and downlink limited access bandwidth for operator B.

Logical IP address of the NodeB (for operator A)

16.16.70.201

None


49



Data Item

Sample Value

Remarks

Logical IP address of the NodeB (for operator B)

16.16.60.201

None

Logical IP address of the eNodeB (for operator A)

16.15.70.201

None

Logical IP address of the eNodeB (for operator B)

16.15.60.201

None

Logical IP address of an Iub port on the RNC side (for operator A)

172.16.90.140

None

Logical IP address of an Iub port on the RNC side (for operator B)

172.16.80.140

None

Logical IP address of the serving gateway (S-GW) (for operator A)

172.15.90.140

None

Logical IP address of the serving gateway (S-GW) (for operator B)

172.15.80.140

None

7.4.3 Precautions None

7.4.4 Hardware Adjustment N/A

7.4.5 Initial Configuration (Unlimited Access Bandwidth for GU Dual-Mode Base Stations) Using MML Commands Step 1 Configure a transport resource mapping (TRM) table on the base station controller side. Configure a TRM table for the RNC and BSC, respectively. For details, see section 4.1.2 Transmission Resource Management Strategies. 1.

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

2.

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

Issue 02 (2014-12-30)


50



3.

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

4.

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

5.

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

Step 2 Configure a TRM table on the base station side. Configure a TRM table for the GBTS/eGBTS and NodeB, respectively. For details, see section 4.1.2 Transmission Resource Management Strategies. 1.

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

2.

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

Step 3 Configure the dynamic flow control algorithm for the NodeB. 1.

Run the ADD ULFLOWCTRLPARA command to add an HSUPA flow control parameter to set the uplink bandwidth adaptive flow control switch.

2.

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

----End

MML Command Examples //Configuring a TRM table on the base station controller side //Setting the mapping between DSCP values and data from the CP and UP on the Iub interface ADD TRMMAP:TMI=110,ITFT=IUB,TRANST=IP,CCHPRIPATH=EF,SIPPRIPATH=EF,SRBPRIPATH=EF,VOICEP RIPATH=EF,CSCONVPRIPATH=AF41,CSSTRMPRIPATH=AF41,PSCONVPRIPATH=AF41,PSSTRMPRIPATH=A F41,PSINTHGHPRIPATH=AF21,PSINTLOWPRIPATH=AF21,PSBKGPRIPATH=AF21,HDSRBPRIPATH=EF,HD SIPPRIPATH=EF,HDVOICEPRIPATH=EF,HDCONVPRIPATH=AF41,HDSTRMPRIPATH=AF41,HDINTHGHPRIP ATH=AF11,HDINTMIDPRIPATH=AF11,HDINTLOWPRIPATH=AF11,HDBKGPRIPATH=AF11,HUSRBPRIPATH= EF,HUSIPPRIPATH=EF,HUVOICEPRIPATH=EF,HUCONVPRIPATH=AF41,HUSTRMPRIPATH=AF41,HUINTHG HPRIPATH=AF11,HUINTMIDPRIPATH=AF11,HUINTLOWPRIPATH=AF11,HUBKGPRIPATH=AF11;

//Setting the mapping between DSCP values and data from the UP on the Abis interface ADD TRMMAP:TMI=111,ITFT=ABIS,TRANST=IP,CSVOICEPATH=EF,CSDATAPATH=AF41,PSHPRIDATAPATH=A F41,PSLPRIDATAPATH=AF31;

//Setting the mapping between DSCP values and data from the CP on the Abis interface SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=1, TRANSTYPE=IP, OMLDSCP=48, RSLDSCP=48, EMLDSCP=18, ESLDSCP=48;

//Adding the mapping from the Iub interface to the TRMMAP index ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110, TMIBRZ=110, FTI=1;

//Adding the mapping from the Abis interface to the TRMMAP index ADD ADJMAP: ANI=3, ITFT=ABIS, TMIGLD=111, FTI=1;

Issue 02 (2014-12-30)


51



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

BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN:

IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID,

BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1,

SERVICETYPE=OML, DSCP=48; SERVICETYPE=RSL, DSCP=48; SERVICETYPE=EML, DSCP=18; SERVICETYPE=ESL, DSCP=48; SERVICETYPE= CSVOICE, DSCP=46; SERVICETYPE= CSDATA, DSCP=34; SERVICETYPE= PSHIGHPRI, DSCP=34; SERVICETYPE= PSLOWPRI, DSCP=26; SERVICETYPE= OTHERDATA, DSCP=46;

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 SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;

//Configuring the uplink bandwidth adaptive flow control switch and HSDPA flow control switch on the NodeB side //Adding an HSUPA flow control parameter ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;

//Adding an HSDPA flow control parameter ADD DLFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, SWITCH=BW_SHAPING_ONOFF_TOGGLE;

Single Configuration Using the CME The parameters related to this feature cannot be modified in batches. This section only describes how to use the CME to perform a single configuration. Set parameters on the CME configuration interface according to the operation sequence described in Table 7-14. For instructions on how to perform the CME single configuration, see CME Single Configuration Operation Guide. Table 7-14 MOs related to this feature SN 1

2

3

Issue 02 (2014-12-30)

MO

NE

a

TRMMAP

BSC and RNC

b

BSCABISPRIMAP

BSC

c

ADJMAP

BSC and RNC

a

BTSVLAN/DIFPRI

GBTS or eGBTS

b

DIFPRI

NodeB

a

ULFLOWCTRLPA RA

NodeB


52


SN b


MO

NE

DLFLOWCTRLPA RA

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 Resource Management Strategies. 1.


2.


3.


Step 2 Configure a TRM table on the base station side. Configure a TRM table for the GBTS/eGBTS and eNodeB, respectively. For details, see section 4.1.2 Transmission Resource Management Strategies. 1.

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

2.

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

3.

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

----End

MML Command Examples //Configuring a TRM table on the base station controller side //Setting the mapping between DSCP values and data from the UP on the Abis interface ADD TRMMAP:TMI=111,ITFT=ABIS,TRANST=IP,CSVOICEPATH=EF,CSDATAPATH=AF41,PSHPRIDATAPATH=A F41,PSLPRIDATAPATH=AF31;


//Adding the mapping from the Abis interface to the TRMMAP index Issue 02 (2014-12-30)


53



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

//Configuring a TRM table on the base station side //Setting the mapping between DSCP values and data from the CP and UP of a GBTS SET SET SET SET SET SET SET SET SET





//Setting the mapping between DSCP values and data from the CP of an eGBTS SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;

//Setting the mapping between DSCP values and data from the CP of an eNodeB SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;

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

UDTPARAGRP: UDTPARAGRP: UDTPARAGRP: UDTPARAGRP: UDTPARAGRP: UDTPARAGRP: UDTPARAGRP: UDTPARAGRP: UDTPARAGRP:

UDTPARAGRPID=40, UDTPARAGRPID=41, UDTPARAGRPID=42, UDTPARAGRPID=43, UDTPARAGRPID=44, UDTPARAGRPID=45, UDTPARAGRPID=46, UDTPARAGRPID=47, UDTPARAGRPID=48,

PRIRULE=DSCP, PRIRULE=DSCP, PRIRULE=DSCP, PRIRULE=DSCP, PRI=46; PRI=18; PRI=18; PRI=18; PRI=0;

PRI=46, PRI=26, PRI=34, PRI=26,

ACTFACTOR=100; ACTFACTOR=100; ACTFACTOR=100; ACTFACTOR=100;


2

Issue 02 (2014-12-30)

MO

NE

a

TRMMAP

BSC

b

BSCABISPRIMAP

BSC

c

ADJMAP

BSC

a

BTSVLAN/DIFPRI

GBTS or eGBTS

b

DIFPRI

eNodeB

c

UDTPARAGRP

eNodeB


54



7.4.7 Initial Configuration (Unlimited Access Bandwidth for UL/ UT/ULT Multimode Base Stations) Using MML Commands Step 1 Configure a TRM table on the base station controller side. Configure a TRM table for the RNC. For details, see section 4.1.2 Transmission Resource Management Strategies. 1.


2.


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

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

2.

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

3.

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



2.


----End



//Configuring a TRM table on the base station side //Setting the mapping between DSCP values and data from the CP of the NodeB Issue 02 (2014-12-30)


55



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

//Setting the mapping between DSCP values and data from the CP of the eNodeB SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;

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




PRI=46, PRI=26, PRI=34, PRI=26,


//Configuring the dynamic flow control algorithm for the NodeB //If the bearer network supports three or more queues //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; //In the case of a separate-MPT multimode base station

//In the case of a separate-MPT multimode base station //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;

//In the case of a co-MPT multimode base station //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, FAIRSWTICH=ENABLE;

//If the bearer network supports two queues //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=OFF;

//Adding an HSDPA flow control parameter in the case of a separate-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;

//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;

Single Configuration Using the CME The parameters related to this feature cannot be modified in batches. This section only describes how to use the CME to perform a single configuration. Issue 02 (2014-12-30)


56



Set parameters on the CME configuration interface according to the operation sequence described in Table 7-16. For instructions on how to perform the CME single configuration, see CME Single Configuration Operation Guide. Table 7-16 MOs related to this feature SN 1

2

3

MO

NE

a

TRMMAP

RNC

b

ADJMAP

RNC

a

DIFPRI

NodeB

b

DIFPRI

eNodeB

c

UDTPARAGRP

eNodeB

a

ULFLOWCTRLPA RA

NodeB

b

DLFLOWCTRLPA RA

NodeB

7.4.8 Initial Configuration (Unlimited Access Bandwidth for GUL/ GUT/GULT Multimode Base Stations) Using MML Commands Step 1 Configure a TRM table on the base station controller side. Configure a TRM table for the RNC and BSC, respectively. For details, see section 4.1.2 Transmission Resource Management Strategies. 1.


2.


3.


4.


5.



Issue 02 (2014-12-30)

Run the SET BTSVLAN command to set the mapping between DSCP values and data from the CP and UP of a GBTS. Run the SET DIFPRI command to set the mapping between DSCP values and data from the CP of an eGBTS. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

57



2.

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

3.

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

4.

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



2.


----End






//Configuring a TRM table on the base station side //Setting the mapping between DSCP values and data from the CP and UP of a GBTS SET SET SET SET SET SET SET

Issue 02 (2014-12-30)

BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN: BTSVLAN:

IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID, IDTYPE=BYID,

BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1,

SERVICETYPE=OML, DSCP=48; SERVICETYPE=RSL, DSCP=48; SERVICETYPE=EML, DSCP=18; SERVICETYPE=ESL, DSCP=48; SERVICETYPE= CSVOICE, DSCP=46; SERVICETYPE= CSDATA, DSCP=34; SERVICETYPE= PSHIGHPRI, DSCP=34;


58



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 SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;






PRI=46, PRI=26, PRI=34, PRI=26,


//Configuring the dynamic flow control algorithm for the NodeB //If the bearer network supports three or more queues //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; //In the case of a separate-MPT multimode base station //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;





Issue 02 (2014-12-30)


59




2

3

MO

NE

a

TRMMAP

BSC

b

TRMMAP

RNC

c

BSCABISPRIMAP

BSC

d

ADJMAP

BSC

e

ADJMAP

RNC

a

BTSVLAN/DIFPRI

GBTS or eGBTS

b

DIFPRI

NodeB

c

DIFPRI

eNodeB

d

UDTPARAGRP

eNodeB

a

ULFLOWCTRLPA RA

NodeB

b

DLFLOWCTRLPA RA

NodeB

7.4.9 Initial Configuration (Limited Access Bandwidth for GU Dual-Mode Base Stations) Using MML Commands Step 1 Configure traffic limiting and shaping on the co-transmission port. l Run the SET LR command to configure traffic limiting and shaping if the eGBTS or NodeB side of a separate-MPT multimode base station provides a co-transmission port. l Run the SET LR command to configure traffic limiting and shaping if a co-MPT multimode base station provides a co-transmission port. Step 2 Configure logical ports on the base station controller side. 1.

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

2.

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

Issue 02 (2014-12-30)


60


3.


Bind a user-plane link and an IP logical port on the Abis interface. l For a GBTS, you can run the SET BTSIP command to bind an IP logical port and a GBTS. l For an eGBTS, you can run the ADD IPPATH command to bind an IP path and an IP logical port if the peer end is a BSC6900. l For an eGBTS, you can run the ADD ADJLOGICPORTBIND command to bind an adjacent node and an IP logical port if the peer end is a BSC6910.

4.

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

l If the transmission resource pool feature is not implemented on the Iub interface, you can run the ADD IPPATH command to bind an IP path and an IP logical port. l If the transmission resource pool feature is implemented on the Iub interface, you can run the ADD ADJLOGICPORTBIND command to bind an adjacent node and an IP logical port. Step 3 Configure a TRM table on the base station controller side. Configure a TRM table for the RNC and BSC, respectively. For details, see section 4.2.2 Transmission Resource Management Strategies. 1.


2.


3.


4.


5.


Step 4 Configure a TRM table on the base station side. Configure a TRM table for the GBTS/eGBTS and NodeB, respectively. For details, see section 4.2.2 Transmission Resource Management Strategies. 1.

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

2.




2.


----End Issue 02 (2014-12-30)


61



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 base station provides a co-transmission port SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000, EBS=0;

//Configuring traffic limiting and shaping if the NodeB side of a separate-MPT multimode base station provides a co-transmission port SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000, EBS=0;

//Configuring traffic limiting and shaping if a co-MPT multimode base station provides a cotransmission 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 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. //Adding a logical port on the Abis interface (BSC6910) 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 end is a BSC6900 ADD IPPATH: ANI=3, PATHID=0, ITFT=ABIS, ISEGBTS=Yes, PATHT=QoS, IPADDR="172.16.140.140", PEERIPADDR="16.16.90.201", TXBW=10000, RXBW=10000, CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=1, VLANFLAG=DISABLE, PATHCHK=DISABLED, AbisLnkBKFLAG=OFF;

//For an eGBTS, binding an adjacent node and an IP logical port on the Abis interface if the peer end is a BSC6910 Issue 02 (2014-12-30)


62



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

//Binding an IP path and an IP logical port if the transmission resource pool feature is not implemented on the Iub interface ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS, 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 is implemented on the Iub interface ADD ADJLOGICPORTBIND: ANI=10, SRN=1, SN=26, LPN=1;

//Configuring a TRM table on the base station controller side //Setting the mapping between DSCP values and data from the CP and UP on the Iub interface ADD TRMMAP:TMI=110,ITFT=IUB,TRANST=IP,CCHPRIPATH=EF,SIPPRIPATH=EF,SRBPRIPATH=EF,VOICEP RIPATH=EF,CSCONVPRIPATH=AF41,CSSTRMPRIPATH=AF41,PSCONVPRIPATH=AF41,PSSTRMPRIPATH=A F41,PSINTHGHPRIPATH=AF21,PSINTLOWPRIPATH=AF21,PSBKGPRIPATH=AF21,HDSRBPRIPATH=EF,HD SIPPRIPATH=EF,HDVOICEPRIPATH=EF,HDCONVPRIPATH=AF41,HDSTRMPRIPATH=AF41,HDINTHGHPRIP ATH=AF11,HDINTMIDPRIPATH=AF11,HDINTLOWPRIPATH=AF11,HDBKGPRIPATH=AF11,HUSRBPRIPATH= EF,HUSIPPRIPATH=EF,HUVOICEPRIPATH=EF,HUCONVPRIPATH=AF41,HUSTRMPRIPATH=AF41,HUINTHG HPRIPATH=AF11,HUINTMIDPRIPATH=AF11,HUINTLOWPRIPATH=AF11,HUBKGPRIPATH=AF11;





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





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 Issue 02 (2014-12-30)


63



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

//Configuring the uplink bandwidth adaptive flow control switch and HSDPA flow control switch on the NodeB side //Adding an HSUPA flow control parameter ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0, BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;


Single Configuration Using the CME The parameters related to this feature cannot be modified in batches. This section only describes how to use the CME to perform a single configuration. Set parameters on the CME configuration interface according to the operation sequence described in Table 7-18. For instructions on how to perform the CME single configuration, see CME Single Configuration Operation Guide. Table 7-18 MOs related to this feature SN

NE

1

a

LR/LR/LR

eGBTS, NodeB, or co-MPT multimode base stations

2

a

IPLOGICPORT

BSC and RNC

b

BTSIP/IPPATH/ ADJLOGICPORTBIND

BSC

c

IPPATH/ ADJLOGICPORTBIND

RNC

a

TRMMAP

BSC and RNC

b

BSCABISPRIMAP

BSC

c

ADJMAP

BSC and RNC

a

BTSVLAN/DIFPRI

GBTS or eGBTS

b

DIFPRI

NodeB

a

ULFLOWCTRLPARA

NodeB

b

DLFLOWCTRLPARA

NodeB

3

4

5

Issue 02 (2014-12-30)

MO


64



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. Step 2 Configure logical ports on the base station controller side. 1.


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. Step 3 Configure a TRM table on the base station controller side. Configure a TRM table for the BSC. For details, see section 4.2.2 Transmission Resource Management Strategies. 1.


2.


3.


Step 4 Configure a TRM table on the base station side. Configure a TRM table for the GBTS/eGBTS and eNodeB, respectively. For details, see section 4.2.2 Transmission Resource Management Strategies. 1.


2.


3.


----End

MML Command Examples //Configuring traffic limiting and shaping on the co-transmission port Issue 02 (2014-12-30)


65



//Configuring traffic limiting and shaping if the eGBTS side of a separate-MPT multimode base station provides a co-transmission port SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000, EBS=0;

//Configuring traffic limiting and shaping if the eNodeB side of a separate-MPT multimode base station provides a co-transmission port SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000, EBS=0;


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

//Adding a logical port on the Abis interface (BSC6910) 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.

//For a GBTS, binding an IP logical port and a GBTS on the Abis interface SET BTSIP: IDTYPE=BYID, BTSID=1, BTSCOMTYPE=LOGICIP, BTSIP="16.16.90.201", BSCIP="172.16.140.140", CFGFLAG=IPLGCPORT, SN=24, LPN=1; //In the preceding script, the base station is identified by its base station index.

//For an eGBTS, binding an IP path and an IP logical port on the Abis interface if the peer end is a BSC6900 ADD IPPATH: ANI=3, PATHID=0, ITFT=ABIS, ISEGBTS=Yes, PATHT=QoS, IPADDR="172.16.140.140", PEERIPADDR="16.16.90.201", TXBW=10000, RXBW=10000, CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=1, VLANFLAG=DISABLE, PATHCHK=DISABLED, AbisLnkBKFLAG=OFF;

//For an eGBTS, binding an adjacent node and an IP logical port on the Abis interface if the peer end is a BSC6910 ADD ADJLOGICPORTBIND: ANI=3, SRN=1, SN=24, LPN=1;

//Configuring a TRM table on the base station controller side //Setting the mapping between DSCP values and data from the UP on the Abis interface ADD TRMMAP:TMI=111,ITFT=ABIS,TRANST=IP,CSVOICEPATH=EF,CSDATAPATH=AF41,PSHPRIDATAPATH=A F41,PSLPRIDATAPATH=AF31;

//Setting the mapping between DSCP values and data from the CP on the Abis interface Issue 02 (2014-12-30)


66



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


//Configuring a TRM table on the base station side //Setting the mapping between DSCP values and data from the CP and UP of a GBTS SET SET SET SET SET SET SET SET SET











PRI=46, PRI=26, PRI=34, PRI=26,



Issue 02 (2014-12-30)

MO

NE

1

a

LR/LR/LR

eGBTS, eNodeB, or co-MPT multimode base stations

2

a

IPLOGICPORT

BSC


67


SN

3

4


MO

NE

b

BTSIP/IPPATH/ ADJLOGICPORTB IND

BSC

a

TRMMAP

BSC

b

BSCABISPRIMAP

BSC

c

ADJMAP

BSC

a

BTSVLAN/DIFPRI

GBTS or eGBTS

b

DIFPRI

eNodeB

c

UDTPARAGRP

eNodeB

7.4.11 Initial Configuration (Limited Access Bandwidth for UL/UT/ ULT 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 NodeB 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. Step 2 Configure logical ports on the base station controller side. 1.


2.


l If the transmission resource pool feature is not implemented on the Iub interface, you can run the ADD IPPATH command to bind an IP path and an IP logical port on the Iub interface. l If the transmission resource pool feature is implemented on the Iub interface, you can run the ADD ADJLOGICPORTBIND command to bind an adjacent node and an IP logical port on the Iub interface. Step 3 Configure a TRM table on the base station controller side. Configure a TRM table for the RNC. For details, see section 4.2.2 Transmission Resource Management Strategies. 1.


2.


Step 4 Configure a TRM table on the base station side. Issue 02 (2014-12-30)


68



1.


2.


3.




2.


Step 6 Disable the traffic control switch of the default transport resource group configured on the cotransmission port. If the NodeB or eNodeB side of a separate-MPT multimode base station provides a cotransmission port and co-transmission is implemented through panel interconnection, the traffic control switch for a transport resource group must be disabled on the co-transmission port. Otherwise, when transmission resources become congested, passing data will preempt bandwidth from the local data. This deteriorates user experience. 1.

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

2.

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

----End

MML Command Examples //Configuring traffic limiting and shaping on the co-transmission port //Configuring traffic limiting and shaping if the NodeB side of a separate-MPT multimode base station provides a co-transmission port SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000, EBS=0;



//Configuring logical ports on the base station controller side //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;

Issue 02 (2014-12-30)


69



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





//Configuring a TRM table on the base station side //Setting the mapping between DSCP values and data from the CP of a NodeB SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;






PRI=46, PRI=26, PRI=34, PRI=26,


//Configuring the dynamic flow control algorithm for the NodeB //If the bearer network supports three or more queues //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;

//In the case of a separate-MPT multimode base station Issue 02 (2014-12-30)


70








//Disabling the traffic control switch of the default transport resource group configured on the co-transmission port //Configuring a default transport resource group on the co-transmission port in a separate-MPT multimode base station where co-transmission is implemented through panel interconnection ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT, RU=KBPS;

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


Issue 02 (2014-12-30)

MO

NE

1

a

LR/LR/LR

NodeB, eNodeB, or co-MPT multimode base stations

2

a

IPLOGICPORT

RNC


71


SN

3

4

5

6


MO

NE

b

IPPATH/ ADJLOGICPORTB IND

RNC

a

TRMMAP

RNC

b

ADJMAP

RNC

a

DIFPRI

NodeB

b

DIFPRI

eNodeB

c

UDTPARAGRP

eNodeB

a

ULFLOWCTRLPA RA

NodeB

b

DLFLOWCTRLPA RA

NodeB

a

RSCGRP

NodeB, eNodeB, or multimode base stations

b

RSCGRPALG


7.4.12 Initial Configuration (Limited Access Bandwidth for GUL/ GUT/GULT 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, NodeB, 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. Step 2 Configure logical ports on the base station controller side. 1.


2.


3.

Bind a user-plane link and an IP logical port on the Abis interface. l For a GBTS, you can run the SET BTSIP command to bind an IP logical port and a GBTS. l For an eGBTS, you can run the ADD IPPATH command to bind an IP path and an IP logical port if the peer end is a BSC6900.

Issue 02 (2014-12-30)


72



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


l If the transmission resource pool feature is not implemented on the Iub interface, you can run the ADD IPPATH command to bind an IP path and an IP logical port. l If the transmission resource pool feature is implemented on the Iub interface, you can run the ADD ADJLOGICPORTBIND command to bind an adjacent node and an IP logical port. Step 3 Configure a TRM table on the base station controller side. Configure a TRM table for the RNC and BSC, respectively. For details, see 4.2.2 Transmission Resource Management Strategies. 1.


2.


3.


4.


5.




2.


3.


4.




2.


Step 6 Disable the traffic control switch of the default transport resource group configured on the cotransmission port. If the NodeB or eNodeB side of a separate-MPT multimode base station provides a cotransmission port and co-transmission is implemented through panel interconnection, the traffic control switch for a transport resource group must be disabled on the co-transmission port. Otherwise, when transmission resources become congested, passing data will preempt bandwidth from the local data. This deteriorates user experience. Issue 02 (2014-12-30)


73



1.

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

2.

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

----End

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 base station provides a co-transmission port SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000, EBS=0;

//Configuring traffic limiting and shaping if the NodeB side of a separate-MPT multimode base station provides a co-transmission port SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=20000, CBS=40000, EBS=0;



//Configuring 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 10048 kbit/s.

//Adding a logical port on the Abis interface (BSC6910) 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.

//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 Issue 02 (2014-12-30)


74



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

//For an eGBTS, binding an IP path and an IP logical port on the Abis interface if the peer end is a BSC6900 ADD IPPATH: ANI=3, PATHID=0, ITFT=ABIS, ISEGBTS=Yes, PATHT=QoS, IPADDR="172.16.140.140", PEERIPADDR="16.16.90.201", TXBW=10000, RXBW=10000, CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=1, VLANFLAG=DISABLE, PATHCHK=DISABLED, AbisLnkBKFLAG=OFF;

//For an eGBTS, binding an adjacent node and an IP logical port on the Abis interface if the peer end is a BSC6910 ADD ADJLOGICPORTBIND: ANI=3, SRN=1, SN=24, LPN=1;








//Configuring a TRM table on the base station side //Setting the mapping between DSCP values and data from the CP and UP of a GBTS Issue 02 (2014-12-30)


75

SingleRAN Bandwidth Sharing of Multimode Base Station CoTransmission Feature Parameter Description SET SET SET SET SET SET SET SET SET



7 Engineering Guidelines BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1, BTSID=1,



//Setting the mapping between DSCP values and data from the CP of a NodeB SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;






PRI=46, PRI=26, PRI=34, PRI=26,






//Adding an HSDPA flow control parameter in the case of a separate-MPT multimode base station Issue 02 (2014-12-30)


76



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


//Disabling the traffic control switch of the default transport resource group configured on the co-transmission port //Configuring a default transport resource group on the co-transmission port in a separate-MPT multimode base station where co-transmission is implemented through panel interconnection ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT, RU=KBPS;

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


NE

1

a

LR/LR/LR/LR

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

2

a

IPLOGICPORT

BSC and RNC

b

BTSIP/IPPATH/ ADJLOGICPORTB IND

BSC

c

IPPATH/ ADJLOGICPORTB IND

RNC

a

TRMMAP

BSC

b

TRMMAP

RNC

c

BSCABISPRIMAP

BSC

d

ADJMAP

BSC

e

ADJMAP

RNC

3

Issue 02 (2014-12-30)

MO


77


SN 4

5

6


MO

NE

a

BTSVLAN/DIFPRI

GBTS or eGBTS

b

DIFPRI

NodeB

c

DIFPRI

eNodeB

d

UDTPARAGRP

eNodeB

a

ULFLOWCTRLPA RA

NodeB

b

DLFLOWCTRLPA RA

NodeB

a

RSCGRP


b

RSCGRPALG


7.4.13 Initial Configuration (Limited Access Bandwidth for Each Operator in a UL/UT Dual-Mode Base Station in RAN Sharing Scenarios) Using MML Commands Step 1 Configure traffic limiting and shaping on the co-transmission port. l Scenario 1: The NodeB side of a separate-MPT multimode base station provides a cotransmission port. 1.

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

2.

Bind a user-plane link for transmitting local data and the configured transport resource group on the base station side. NOTE

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

l If you use link mode to configure a user-plane link: a. Run the ADD IPPATH command to add an IP path and bind this IP path and the configured transport resource group. b. Run the ADD NODEBPATH command to bind a NodeB and the added IP path. l If you use end-point mode to configure a user-plane link: Issue 02 (2014-12-30)


78



a. Run the ADD EPGROUP command to add an end point group on the base station side. b. Run the ADD USERPLANEHOST command to add a user-plane host on the base station side. c. Run the ADD USERPLANEPEER command to add a user-plane peer on the base station side. d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host and the added end point group on the base station side. e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer and the added end point group on the base station side. f. Run the ADD EP2RSCGRP command to bind the added end point group and the configured transport resource group. 3.

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

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


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 the configured 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 station side. b. Run the ADD USERPLANEHOST command to add a user-plane host on the base station side. c. Run the ADD USERPLANEPEER command to add a user-plane peer on the base station side. d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host and the added end point group on the base station side. e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer and the added end point group on the base station side. f. Run the ADD EP2RSCGRP command to bind the added end point group and the configured transport resource group.

3.

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

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


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 the configured transport resource group. In this step, set Peer IP to the RNC IP address.

Issue 02 (2014-12-30)


79



b. Run the ADD NODEBPATH command to bind a NodeB and the added IP path. l If you use end-point mode to configure a user-plane link: a. Run the ADD EPGROUP command to add an end point group on the base station side. b. Run the ADD USERPLANEHOST command to add a user-plane host on the base station side. c. Run the ADD USERPLANEPEER command to add a user-plane peer on the base station side. d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host and the added end point group on the base station side. e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer and the added end point group on the base station side. f. Run the ADD EP2RSCGRP command to bind the added end point group and the configured transport resource group. Step 2 Configure logical ports on the base station controller side. 1.


2.

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

Step 3 Configure a TRM table on the base station controller side. Configure a TRM table for the RNC. For details, see section 4.3.2 Transmission Resource Management Strategies. 1.


2.




2.


3.




2.


Step 6 Disable the traffic control switch of the default transport resource group configured on the cotransmission port. If the NodeB or eNodeB side of a separate-MPT multimode base station provides a cotransmission port and co-transmission is implemented through panel interconnection, the traffic control switch for a transport resource group must be disabled on the co-transmission port. Issue 02 (2014-12-30)


80



Otherwise, when transmission resources become congested, passing data will preempt bandwidth from the local data. This deteriorates user experience. Run the SET RSCGRPALG command to disable the traffic control switch of the default transport resource group you have configured. ----End

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

EPGROUP: EPGROUPID=0; EPGROUP: EPGROUPID=1; USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="16.16.70.201"; USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="16.16.60.201"; USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, LOCIPV4="172.16.90.140"; USERPLANEPEER: UPPEERID=1, IPVERSION=IPv4, LOCIPV4="172.16.80.140"; UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0; UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1; UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0; UPPEER2EPGRP: EPGROUPID=1, UPPEERID=1; EP2RSCGRP: ENDPOINTID=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1; 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 //Configuring a transport resource group Issue 02 (2014-12-30)


81



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;

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

//If you use end-point mode to configure a user-plane link //Binding an end point group and the configured transport resource group ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD

EPGROUP: EPGROUPID=0; EPGROUP: EPGROUPID=1; USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="16.15.70.201"; USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="16.15.60.201"; USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, LOCIPV4="172.15.90.140"; USERPLANEPEER: UPPEERID=1, IPVERSION=IPv4, LOCIPV4="172.15.80.140"; UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0; UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1; UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0; UPPEER2EPGRP: EPGROUPID=1, UPPEERID=1; EP2RSCGRP: ENDPOINTID=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1; 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 //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=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;

//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; 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;

Issue 02 (2014-12-30)


82



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;

//If you use end-point mode to configure a user-plane link //Binding an end point group and the configured transport resource group ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD

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

//Configuring logical ports on the base station controller side //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=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;

//Configuring a TRM table on the base station controller side //Setting the mapping between DSCP values and data from the CP and UP on the Iub interface ADD TRMMAP:TMI=110,ITFT=IUB,TRANST=IP,CCHPRIPATH=EF,SIPPRIPATH=EF,SRBPRIPATH=EF,VOICEP RIPATH=EF,CSCONVPRIPATH=AF41,CSSTRMPRIPATH=AF41,PSCONVPRIPATH=AF41,PSSTRMPRIPATH=A F41,PSINTHGHPRIPATH=AF21,PSINTLOWPRIPATH=AF21,PSBKGPRIPATH=AF21,HDSRBPRIPATH=EF,HD SIPPRIPATH=EF,HDVOICEPRIPATH=EF,HDCONVPRIPATH=AF41,HDSTRMPRIPATH=AF41,HDINTHGHPRIP ATH=AF11,HDINTMIDPRIPATH=AF11,HDINTLOWPRIPATH=AF11,HDBKGPRIPATH=AF11,HUSRBPRIPATH=

Issue 02 (2014-12-30)


83



EF,HUSIPPRIPATH=EF,HUVOICEPRIPATH=EF,HUCONVPRIPATH=AF41,HUSTRMPRIPATH=AF41,HUINTHG HPRIPATH=AF11,HUINTMIDPRIPATH=AF11,HUINTLOWPRIPATH=AF11,HUBKGPRIPATH=AF11;


//Configuring a TRM table on the base station side //Setting the mapping between DSCP values and data from the CP of a NodeB SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;






PRI=46, PRI=26, PRI=34, PRI=26,







//Adding an HSDPA flow control parameter in the case of a co-MPT multimode base station Issue 02 (2014-12-30)


84



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

//Disabling the traffic control switch of the default transport resource group configured on the co-transmission port //Configuring a default transport resource group on the co-transmission port in a separate-MPT multimode base station where co-transmission is implemented through panel interconnection 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;


2

3

4

5

Issue 02 (2014-12-30)

MO

NE

a

RSCGRP


b

IPPATH


c

NODEBPATH

NodeB or co-MPT multimode base stations

d

ENODEBPATH

eNodeB or co-MPT multimode base stations

e

IP2RSCGRP

NodeB or eNodeB

a

IPLOGICPORT

RNC

b

IPPATH/ ADJLOGICPORTBI ND

RNC

a

TRMMAP

RNC

b

ADJMAP

RNC

a

DIFPRI

NodeB

b

DIFPRI

eNodeB

c

UDTPARAGRP

eNodeB

a

ULFLOWCTRLPA RA

NodeB


85


SN

6


MO

NE

b

DLFLOWCTRLPA RA

NodeB

a

RSCGRPALG


7.4.14 Activation Observation (Unlimited Access Bandwidth for Multimode Base Stations) After the Bandwidth Sharing of Multimode Base Station Co-Transmission feature is activated, check whether UEs can properly process CS and PS services when transmission resources are congested and whether the DSCP value of each packet is configured as expected. l

If yes to both, this feature has been activated.

l

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

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

Separate-MPT multimode base station

Step 1 Start IP or MAC tracing on the LMT. l If the eGBTS provides a co-transmission port, start IP or MAC tracing on the eGBTS LMT. For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. For MAC tracing: Choose Trace > Common Services > MAC Trace. l If the NodeB provides a co-transmission port, start IP or MAC tracing on the NodeB LMT. 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 IP Address and Peer IP Address of the packets to be traced. For MAC tracing: In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. Step 3 Use the TrafficReview tool to check the TOS (type of service) field in the Layer 3 IP packet header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCP values or VLAN priorities planned, this feature has been activated. ----End l

Co-MPT multimode base station

Step 1 Start IP or MAC tracing on the LMT. Issue 02 (2014-12-30)


86



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 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 LTE 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. Step 2 For IP tracing: In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing: In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. Step 3 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCP values or VLAN priorities planned, this feature has been activated. ----End

7.4.15 Activation Observation (Limited Access Bandwidth for Multimode Base Stations) If you do not need to check whether the configured service priority has taken effect, perform the following steps to check whether the feature has been activated: Step 1 Run the LST RSCGRP command on the base station that provides the co-transmission port to check whether a transport resource group has been configured for the co-transmission port. If not, go to method 2. Step 2 Initiate a UMTS or LTE PS service and set the maximum data rate to a value greater than the CIR to simulate transmission resource congestion. Step 3 Query the value of the VS.RscGroup.FlowOverloadTime counter for the co-transmission port. If the value is greater than 0, this feature has been activated. ----End If you need to check whether the configured service priority has taken effect, perform the following steps to check whether the feature has been activated: l

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

Step 1 Initiate a UMTS or LTE PS service and set the maximum data rate higher than the CIR value to simulate transmission resource congestion. Issue 02 (2014-12-30)


87



Step 2 Start transport link flux monitoring on the eGBTS LMT. Choose Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring. Step 3 Initiate a GSM or UMTS CS service if the traffic flux approaches the bandwidth available for the bearer network. Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant. Step 5 Initiate a GSM PS service, connect a personal computer (PC) to the multimode base station, and use the DU Meter on the PC to check whether the GSM PS service is successfully set up and the data rate is stable. l If yes to both, this feature has been activated. l If no to either, this feature has not been activated. Step 6 Start IP or MAC tracing on the eGBTS LMT. For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. Step 7 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCP values or VLAN priorities planned, this feature has been activated. ----End l

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

Step 1 Initiate a UMTS PS service and set the maximum data rate higher than the CIR value to simulate transmission resource congestion. Step 2 Start transport link flux monitoring on the NodeB LMT. Choose Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring. Step 3 Initiate a GSM or UMTS CS service if the traffic flux approaches the bandwidth available for the bearer network. Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant. Step 5 Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meter on the PC to check whether the GSM PS service is successfully set up and the data rate is stable. l If yes, this feature has been activated. 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 triplemode base station.

Step 6 Start IP or MAC tracing on the NodeB LMT. Issue 02 (2014-12-30)


88



For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. Step 7 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCP values or VLAN priorities planned, this feature has been activated. ----End l

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

Step 1 Initiate an LTE PS service and set the maximum data rate higher than the CIR value to simulate transmission resource congestion. Step 2 Start transport link flux monitoring on the eNodeB LMT. Choose Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring. Step 3 Initiate a GSM or UMTS CS service if the traffic flux approaches the bandwidth available for the bearer network. Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant. Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meter on the PC to check whether the GSM PS service is successfully set up and the data rate is stable. l If yes, this feature has been activated. l If no, this feature has not been activated. NOTE

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

Step 5 Start IP or MAC tracing on the eNodeB LMT. For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing:Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. Step 6 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCP values or VLAN priorities planned, this feature has been activated. ----End l Issue 02 (2014-12-30)

A co-MPT multimode base station provides a co-transmission port. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

89



Step 1 Initiate a UMTS or LTE PS service and set the maximum data rate higher than the CIR value to simulate transmission resource congestion. Step 2 Start transport link flux monitoring on the LMT. l If UMTS services are initiated, start transport link flux monitoring on the LMT. Choose Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring. l If LTE services are initiated, start transport link flux monitoring on the LMT. Choose Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring. Step 3 Initiate a GSM or UMTS CS service if the traffic flux approaches the bandwidth available for the bearer network. Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant. Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meter on the PC to check whether the GSM PS service is successfully set up and the data rate is stable. l If yes, this feature has been activated. l If no, this feature has not been activated. NOTE

Step 4 is performed only in a separate-MPT GU/GL dual-mode base station or a separate-MPT GUL triplemode 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 the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. l If UMTS services are initiated, start IP or MAC tracing on the LMT. For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. l If LTE services are initiated, start IP or MAC tracing on the LMT. For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. Step 6 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCP values or VLAN priorities planned, this feature has been activated. ----End Issue 02 (2014-12-30)


90



7.4.16 Activation Observation (Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios) If you do not need to check whether the configured service priority has taken effect, perform the following steps to check whether the feature has been activated: Step 1 Run the LST RSCGRP command on the base station that provides the co-transmission port to check whether a transport resource group has been configured for the co-transmission port. If not, go to method 2. Step 2 Initiate a UMTS or LTE PS service for an operator and set the maximum data rate to a value greater than the TXBW value to simulate transmission resource congestion. Step 3 Query the value of the VS.RscGroup.FlowOverloadTime counter for the co-transmission port. If the value is greater than 0, this feature has been activated. ----End If you need to check whether the configured service priority has taken effect, perform the following 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 than the TXBW value to simulate transmission resource congestion. Step 2 Start transport link flux monitoring on the LMT. l If the NodeB side of a separate-MPT multimode base station provides a co-transmission port, start transport link flux monitoring on the NodeB LMT. Choose Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring. l If the eNodeB side of a separate-MPT multimode base station provides a co-transmission port, start transport link flux monitoring on the eNodeB LMT. Choose Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring. Step 3 Initiate a UMTS CS service for operator A if the traffic flux approaches the bandwidth available for the bearer network. Terminate the CS service if the call is successfully set up and the voice is clear and constant. Step 4 Perform the first three steps to verify services of other operators. Step 5 Start IP or MAC tracing on the LMT. l Start IP or MAC tracing on the NodeB LMT. For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. l Start IP or MAC tracing on the eNodeB LMT. For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. Issue 02 (2014-12-30)


91



For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. Step 6 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCP values or VLAN priorities planned, this feature has been activated. ----End l

Co-MPT multimode base station

Step 1 Initiate a UMTS or LTE PS service for operator A and set the maximum data rate higher than the TXBW value to simulate transmission resource congestion. Step 2 Start transport link flux monitoring on the LMT. l If UMTS services are initiated, start transport link flux monitoring on the NodeB LMT. Choose Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring. l If LTE services are initiated, start transport link flux monitoring on the eNodeB LMT. Choose Monitor > Realtime Performance Monitoring > Transport Link Flux Monitoring. Step 3 Initiate a UMTS CS service for operator A if the traffic flux approaches the bandwidth available for the bearer network. Terminate the CS service if the call is successfully set up and the voice is clear and constant. Step 4 Perform the first three steps to verify services of other operators. Step 5 Start IP or MAC tracing on the LMT. l If UMTS services are initiated, start IP or MAC tracing on the NodeB LMT. For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. l If LTE services are initiated, start IP or MAC tracing on the eNodeB LMT. For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace. In the displayed IP Layer Protocol Trace dialog box, specify Local IP Address and Peer IP Address of the packets to be traced. For MAC tracing: Choose Trace > Common Services > MAC Trace. In the displayed MAC Trace dialog box, specify Local MAC Address and Peer MAC Address of the packets to be traced. Step 6 Use the TrafficReview tool to check the TOS field in the Layer 3 IP packet header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN priorities are the same as DSCP values or VLAN priorities planned, this feature has been activated. ----End Issue 02 (2014-12-30)


92



7.5 Performance Monitoring Transmission resource congestion in a base station is indicated by the congestion duration of transport resource groups calculated by the VS.RscGroup.FlowOverloadTime counter.

7.6 Parameter Optimization None

7.7 Troubleshooting If bandwidth resources across all modes of a multimode base station are inappropriately allocated, reallocate the bandwidth resources based on the traffic model.

Issue 02 (2014-12-30)


93


8 Parameters

8

Parameters

Table 8-1 Parameter description MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

LR

CIR

SET LR

WRFD0106101 0

HSDPA Flow Control

LOFD-0 0301101 / TDLOF D-00301 101

Transpo rt Overboo king Transpo rt Differen tiated Flow Control

Meaning: Indicates the UL committed information rate after rate limitation is configured at a port. The precision of the UL committed information rate supported by the UMPTb is 64 Kbit/s, the precision supported by the other board is 32 Kbit/s. If the configured UL committed information rate is not a multiple of the precision, the UL committed information rate is rounded up.

LST LR

LOFD-0 0301102 / TDLOF D-00301 102

GUI Value Range: 32~1000000 Unit: Kbit/s Actual Value Range: 32~1000000 Default Value: None

Abis over IP

GBFD-1 18601

Issue 02 (2014-12-30)


94


8 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

RSCGR P

TXBW

ADD RSCGR P

WRFD0213040 6

MOD RSCGR P

LOFD-0 03011 / TDLOF D-00301 1

Transmi ssion Recours e Sharing on Iub/ Iur Interface Enhance d Transmi ssion QoS Manage ment

Meaning: Indicates the maximum uplink bandwidth of a transmission resource group at the MAC layer when the transmission resource group is carried over IP. This parameter value is used as the uplink transport admission bandwidth and TX traffic shaping bandwidth.The LMPT can be configured with a maximum of 360 Mbit/s TX bandwidth.The WMPT can be configured with a maximum of 300 Mbit/s TX bandwidth.The UMPT or UTRPc can be configured with a maximum of 1 Gbit/s TX bandwidth.The value of TX bandwidth is set to the maximum value of TX bandwidth supported by the board when it bigger than the maximum one. For a WMPT and a UTRP (excluding UTRPa), this parameter does not specify the TX traffic shaping bandwidth of the transmission resource group that is carried on the PPP link.

IP QOS

GUI Value Range: 32~1000000

DSP RSCGR P LST RSCGR P

GBFD-1 18605

Unit: None Actual Value Range: 32~1000000 Default Value: None LR

CBS

SET LR LST LR

WRFD050402 LOFD-0 0301101 / TDLOF D-00301 101 LOFD-0 0301102 / TDLOF D-00301 102 GBFD-1 18601

IP Transmi ssion Introduc tion on Iub Interface

Meaning: Indicates the Committed Burst Size (CBS) after rate limitation is configured at a port.The minimum rate supported by the UMPTb is 64 Kbit/s.

Transpo rt Overboo king Transpo rt Differen tiated Flow Control

Default Value: None

GUI Value Range: 32~1000000 Unit: Kbit Actual Value Range: 32~1000000

Abis over IP

Issue 02 (2014-12-30)


95


8 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

LR

EBS

SET LR

WRFD050402


Meaning: Indicates the Excess Burst Size (EBS) after rate limitation is configured at a port.

LST LR

LOFD-0 0301101 / TDLOF D-00301 101 LOFD-0 0301102 / TDLOF D-00301 102 GBFD-1 18601

GUI Value Range: 0~1000000 Unit: Kbit Actual Value Range: 0~1000000 Default Value: None

Transpo rt Overboo king Transpo rt Differen tiated Flow Control Abis over IP

RSCGR P

TXCBS

ADD RSCGR P

WRFD0213040 6

MOD RSCGR P

LOFD-0 03011 / TDLOF D-00301 1

LST RSCGR P

GBFD-1 18605

Transmi ssion Recours e Sharing on Iub/ Iur Interface Enhance d Transmi ssion QoS Manage ment IP QOS

Issue 02 (2014-12-30)

Meaning: Indicates the TX committed burst size of a transmission resource group.The LMPT can be configured with a maximum of 400 Mbit/s TX committed burst size.The WMPT can be configured with a maximum of 600 Mbit/s TX committed burst size.The WMPT can be configured with a maximum of 600 Mbit/s TX committed burst size.The UMPT or UTRPc can be configured with a maximum of 1 Gbit/s TX committed burst size.The value of TX committed burst size is set to the maximum value of TX committed burst size supported by the board when it bigger than the maximum one. GUI Value Range: 64~1000000 Unit: Kbit Actual Value Range: 64~1000000 Default Value: 64


96


8 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

RSCGR P

TXEBS

ADD RSCGR P

WRFD0213040 6

MOD RSCGR P

LOFD-0 03011 / TDLOF D-00301 1

Transmi ssion Recours e Sharing on Iub/ Iur Interface

Meaning: Indicates the TX excessive burst size of a transmission resource group.The LMPT can be configured with a maximum of 450 Mbit/s TX excessive burst size.The WMPT can be configured with a maximum of 600 Mbit/s TX excessive burst size.The UMPTor UTRPc can be configured with a maximum of 1 Gbit/s TX excessive burst size.The value of TX excessive burst size is set to the maximum value of TX excessive burst size supported by the board when it bigger than the maximum one.

LST RSCGR P

GBFD-1 18605

Enhance d Transmi ssion QoS Manage ment

GUI Value Range: 64~1000000 Unit: Kbit Actual Value Range: 64~1000000 Default Value: 1000000

IP QOS DIFPRI

PRIRUL E

SET DIFPRI

WRFD050402

LST DIFPRI

LBFD-0 0300201 / TDLBF D-00300 201 GBFD-1 18605


Meaning: Indicates the rule for prioritizing traffic to meet service requirements. If this parameter is set to IPPRECEDENCE, the protocol stack of the earlier version is adopted, which firstly converts a Type of Service (TOS) to a DSCP and then prioritizes traffic.

DiffServ QoS Support

Unit: None

GUI Value Range: IPPRECEDENCE(IP Precedence), DSCP(DSCP) Actual Value Range: IPPRECEDENCE, DSCP Default Value: DSCP(DSCP)

IP QOS DIFPRI

SIGPRI

SET DIFPRI

WRFD050402

LST DIFPRI

LBFD-0 0300201 / TDLBF D-00300 201 GBFD-1 18605


Meaning: Indicates the priority of signaling. The priority has a positive correlation with the value of this parameter.


Default Value: 48

GUI Value Range: 0~63 Unit: None Actual Value Range: 0~63

IP QOS

Issue 02 (2014-12-30)


97


8 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

DIFPRI

OMHIG HPRI

SET DIFPRI

WRFD050402

LST DIFPRI

LBFD-0 0300201 / TDLBF D-00300 201


Meaning: Indicates the priority of the high-level OM data. The priority has a positive correlation with the value of this parameter.


Default Value: 46

GBFD-1 18605

GUI Value Range: 0~63 Unit: None Actual Value Range: 0~63

IP QOS DIFPRI

OMLO WPRI

SET DIFPRI

WRFD050402

LST DIFPRI

LBFD-0 0300201 / TDLBF D-00300 201 GBFD-1 18605


Meaning: Indicates the priority of the low-level OM data, such as the data to be uploaded or downloaded. The priority has a positive correlation with the value of this parameter. The low-level OM data includes the packets related to File Transfer Protocol (FTP).


Actual Value Range: 0~63

GUI Value Range: 0~63 Unit: None Default Value: 18

IP QOS DIFPRI

IPCLKP RI

SET DIFPRI LST DIFPRI

None

None

Meaning: Indicates the priority of the IP clock. If the IP clock that follows the Precision Time Protocol (PTP) is used, set this parameter to the DSCP of the PTP packets. If the IP clock that follows the Huawei proprietary protocol is used, set this parameter to the DSCP of these packets that follow the Huawei proprietary protocol. GUI Value Range: 0~63 Unit: None Actual Value Range: 0~63 Default Value: 46

Issue 02 (2014-12-30)


98


8 Parameters

MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

UDTPA RAGRP

UDTPA RAGRP ID

ADD UDTPA RAGRP

None

None

Meaning: Indicates the ID of the transport parameter group related to the service that corresponds to the QCI. It uniquely identifies a transport parameter group.User data type numbers 1~9 correspond to user data type transfer parameter group IDs 40~48, which are automatically configured by the BS.

LST UDTPA RAGRP

UDTPA RAGRP

PRI

MOD UDTPA RAGRP

GUI Value Range: 0~48

RMV UDTPA RAGRP

Default Value: None

ADD UDTPA RAGRP MOD UDTPA RAGRP LST UDTPA RAGRP

Issue 02 (2014-12-30)

Unit: None Actual Value Range: 0~48

None

None

Meaning: Indicates the priority of the service data, which is identified by a DSCP value. The priority of the service data has a positive correlation with the DSCP value. GUI Value Range: 0~63 Unit: None Actual Value Range: 0~63 Default Value: None


99


9 Counters

9

Counters

Table 9-1 Counter description Counter ID

Counter Name

Counter Description

Feature ID

Feature Name

1542455378

VS.RscGroup.TxFl owOverloadTime

Congestion duration of transmit data in the resource group

Multi-mode: MRFD-211505

Bandwidth sharing of MBTS Multimode CoTransmission (GBTS)

MRFD-221505 MRFD-231505 MRFD-241505 GSM: None UMTS: None LTE: None

Bandwidth sharing of MBTS Multimode CoTransmission (NodeB) Bandwidth sharing of MBTS Multimode CoTransmission (eNodeB) Bandwidth sharing of MBTS Multimode CoTransmission (LTE TDD)

Issue 02 (2014-12-30)


100


10 Glossary

10

Glossary

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

Issue 02 (2014-12-30)


101


11

11 Reference Documents

Reference Documents

1.

Transmission Resource Management Feature Parameter Description for GBSS and RAN

2.

Transport Resource Management Feature Parameter Description for eRAN

3.

Common Transmission Feature Parameter Description for SingleRAN

Issue 02 (2014-12-30)


102

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

Recommend Documents